Skip to content

Commit 50c092c

Browse files
committed
chore(docs/decisions-log.md): mention about a container's timezone
[skip ci]
1 parent 399946e commit 50c092c

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docs/decisions-log.md

+1
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@
1616
| 07.02.2020 Workaround | [php-coder/mystamps#1248](https://github.com/php-coder/mystamps/issues/1248): **wiremock** logs warnings for static resources when there is no stub mapping. Workaround: create mappings for such resources. Bug: [tomakehurst/wiremock#1247](https://github.com/tomakehurst/wiremock/issues/1247) Commits: [0018ad4](https://github.com/php-coder/mystamps/commit/0018ad44a21379b8179f94e954795c66b6d50bbc) |
1717
| ~~24.11.2019 Workaround~~ | ~~[php-coder/mystamps#1156](https://github.com/php-coder/mystamps/issues/1156) After updating **html5validator** to 0.3.2, the `--ignore-re` has stopped to work. Workaround: revert and pin the version to 0.3.1 Bug: [svenkreiss/html5validator#64](https://github.com/svenkreiss/html5validator/issues/64) Commits: [9a0d695](https://github.com/php-coder/mystamps/commit/9a0d695ccac1deeba0c4280779bbac11ebf3ac4d)~~<br/> UPDATE(22.12.2020): in [61c97a4f](https://github.com/php-coder/mystamps/commit/61c97a4f2435e7cdf17c0ad6866f7b99cb640e3b) ([#1169](https://github.com/php-coder/mystamps/issues/1169)) html5validator has been updated to 0.3.3 that fixed the issue |
1818
| 23.12.2018 Decision | [php-coder/mystamps#967](https://github.com/php-coder/mystamps/issues/967) "Show similar series" feature has been added with the following notes:<br/>- there is no limit for a number of series that will be displayed. I thought about limiting to 3 but I decided to leave it as-is for now<br/>- the order of the series isn't defined. In the initial idea, I thought about showing only 3 series in a random order but it's hard to implement in a database-agnostic way<br/>Commits: [054f826e](https://github.com/php-coder/mystamps/commit/054f826ef6706f82b4a7c04d73715d161d0c1a28) |
19+
| 14.10.2018 Workaround | [php-coder/mystamps#76](https://github.com/php-coder/mystamps/issues/76) Because our existing infrastructure lives in Moscow time and data is stored in this format, I've configured **Docker container** to use `Europe/Moscow` timezone instead of UTC that was used by default. Commits: [8c4e9db2](https://github.com/php-coder/mystamps/commit/8c4e9db272b103818d74c94a68ba95d1b082d3a4) |
1920
| 29.09.2018 Workaround | After [upgrade of **mysql-connector-java** to 5.1.47](https://github.com/php-coder/mystamps/commit/21e3a7a361990d6059cb7668c1217f653bd0ae8f), the bug that [causes NullPointerException](https://travis-ci.org/php-coder/mystamps/jobs/435000067) was revealed. I reverted the version back to 5.1.46 Issue: https://bugs.mysql.com/bug.php?id=92089 Commits: [3cb0dac9](https://github.com/php-coder/mystamps/commit/3cb0dac9fb62bbc12331b7ea1378f3b56746714d) |
2021
| 30.12.2017 Workaround | [php-coder/mystamps#772](https://github.com/php-coder/mystamps/issues/772) Because **Travis CI** has **MySQL** version 5.6.43, we can't have a unique index on a column that has a length that exceeds 767 bytes. Our production server is running on 5.7.20 that doesn't have such limitation. In order to be able to run migrations on all the environments, I set type of the `series_import_requests.url` column to `VARCHAR(767)` (instead of `VARCHAR(768)` or `VARCHAR(1024)` as I wanted before). Commits: [33dd9025](https://github.com/php-coder/mystamps/commit/33dd902500501d3fdc3a744229ad921982adbc01) |
2122
| 20.07.2017 Decision | [php-coder/mystamps#423](https://github.com/php-coder/mystamps/issues/423) Most of our **checks on CI** now get executed only when files of a certain type were modified. This should give us a faster feedback loop. Checks are also being run when their configuration has been changed. If check performed by a maven plugin, it will be always run when `pom.xml` is modified. The same logic applies to the tools that are being installed from the `.travis.yml` file. Unfortunately, we have to unconditionally run checks even if a change in a file wasn't related to the plugin/tool configuration. Also there is no way to disable skipping logic and if you need to run a specific check there is no way to force its execution. I was thinking about introducing an environment variable or using a special magic comment from a commit message but I decided to leave it as-is for a now (although it can be added later). Commits: [7da91a53](https://github.com/php-coder/mystamps/commit/7da91a53a1d7f43670d67adfce359814fa7ee27a) |

0 commit comments

Comments
 (0)