-
-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16.0]connector: Migration 16.0 #447
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise the auto api docs are not generated
Because the check uses a fast-path for the connector so it does not reach the cache.
This code is never reached when we check the installation state with the high-level function is_module_installed for the module 'connector' because it directly looks for a model in the registry to check the installation state
This column appears often in the where clauses with the old workers.
This adds a retry pattern for queue jobs. see OCA/connector-magento#26
Sort the retry dict by key ( the retry count ) instead of by value
It avoids to copy and to store the pattern for every job when all jobs of one function will probably share the same pattern.
So that the last count is repeated indefinitely. For the following pattern: {1: 10*60, 5: 20*60, 10: 60*60} The retries 1 to 4 will be postponed 10 minutes later. The retries 5 to 9 will be postponed 20 minutes later. The retries 10 to infinite will be postponed 1 hour later.
Does not do particular checks to see if each "step" is a valid m2o field, relies on the standard and familiar Odoo recordset errors instead.
The job function, channel and worker fields are too large for a 6 column layout. Job function and channel make the fields overflow of the form and the worker fields is wrapped over 3 lines
…cified (to avoid timedelta error when seconds is None) in job.py.
Hey @bizzappdev, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
bizzappdev
force-pushed
the
16.0-mig-connecto-RUS-BAD
branch
5 times, most recently
from
October 10, 2022 12:50
b3361f1
to
60d25a5
Compare
bizzappdev
changed the title
[WIP][16.0]connector: Migration 16.0
[16.0]connector: Migration 16.0
Nov 1, 2022
bizzappdev
force-pushed
the
16.0-mig-connecto-RUS-BAD
branch
from
December 6, 2022 10:52
60d25a5
to
780c7b3
Compare
There's already a migration here #442 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.