chouette-core/config/initializers/sidekiq.rb, branch 5609_slug_format Chouette manage transport static data Merge branch 'master' into 0000-docker 2018-02-19T10:04:29+00:00 Luc Donnet 2018-02-19T10:04:29+00:00 7b17deff51545358009cb417cbb9d796565e7540 






default sidekiq redis  URL to localhost for devs, and make Docker image defaut envvar value to redis host
2018-02-16T13:23:48+00:00

Florent Peyraud

2018-02-16T13:23:48+00:00

63d162bbe7018e00dadc57b911d742fe8b2b0149












Merge pull request #212 from af83/5495-deactivate-Sidekiq-retry-for-WorkbenchImports
2018-01-09T15:53:16+00:00

Luc Donnet

2018-01-09T15:53:16+00:00

7e152ed43030c939a719be5949b71a5179c3dcd7

initializers/sidekiq: Disable retries on Sidekiq jobs




initializers/sidekiq: Disable retries on Sidekiq jobs






initializers/sidekiq: Disable retries on Sidekiq jobs
2018-01-08T17:06:39+00:00

Teddy Wing

2018-01-08T15:13:37+00:00

3487ce6f34ef187a2a8daf170440f51f659c46b7

Alban recommended disabling retries on all Sidekiq jobs. In theory, none
of our jobs should be automatically retried (except maybe the
Reflex/Codifligne sync tasks).

Another way of doing this also exists
(https://stackoverflow.com/questions/28412913/disable-automatic-retry-with-activejob-used-with-sidekiq/28427385#28427385),
but this appeared to work, looking at the job's JSON parameters in the
Sidekiq console.

This came about because a timeout from Faraday caused a
`WorkbenchImport` job to fail and presumably get retried by Sidekiq. The
retry caused a second, duplicate `Referential` to be created.

Refs #5495





Alban recommended disabling retries on all Sidekiq jobs. In theory, none
of our jobs should be automatically retried (except maybe the
Reflex/Codifligne sync tasks).

Another way of doing this also exists
(https://stackoverflow.com/questions/28412913/disable-automatic-retry-with-activejob-used-with-sidekiq/28427385#28427385),
but this appeared to work, looking at the job's JSON parameters in the
Sidekiq console.

This came about because a timeout from Faraday caused a
`WorkbenchImport` job to fail and presumably get retried by Sidekiq. The
retry caused a second, duplicate `Referential` to be created.

Refs #5495







Use localhost instead of redis host in sidekiq initializer (good default and avoid Rails.env test)
2018-01-08T16:15:37+00:00

Alban Peignier

2018-01-08T15:51:38+00:00

417465bb1c147ed1e58008516ba2f9fb7515e7a9












initializers/sidekiq: Don't set Redis URL in development or test
2018-01-08T13:46:18+00:00

Teddy Wing

2018-01-08T13:38:55+00:00

3f59e3bd14cdefd4270233ed784a5704a8486e83

Don't set this configuration in development and test environments to
enable Sidekiq to connect to the default Redis server by default without
setting the environment variable.





Don't set this configuration in development and test environments to
enable Sidekiq to connect to the default Redis server by default without
setting the environment variable.







docker first commit
2018-01-07T22:22:19+00:00

Florent Peyraud

2017-12-17T14:39:07+00:00

1d100b42b9a47c73dc7723775407308b19b14f54












docker first commit
2017-12-17T14:39:07+00:00

Florent Peyraud

2017-12-17T14:39:07+00:00

cd45b0d8eeb5c49b05c8e318ffc760f997e991fc












Add condition on reset of LineReferentialSyncs/StopAreaReferentialSyncs by sidekiq initializer
2017-08-29T09:51:08+00:00

Xinhui

2017-08-29T09:51:08+00:00

a64bf1115eedf12af4effc5556042a3cfd9493bb

Refs #4314





Refs #4314







Fix sidekiq initializer should not require LineReferential/StopAreaReferential
2017-08-29T09:38:05+00:00

Xinhui

2017-08-29T09:38:05+00:00

f8ec55f2f708b3e463a3167eab336af010af00a4

Refs #4313





Refs #4313