Skip to content
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

[13.0] Add delivery_postlogistics_dangerous_goods #367

Conversation

mmequignon
Copy link
Member

@mmequignon mmequignon commented May 11, 2021

This modules overrides Postlogistics Shipping to declare dangerous goods
during postlogistics label generation.

Based on:

Supersedes:

@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from 0278821 to 0758137 Compare June 11, 2021 09:26
@simahawk simahawk changed the title 13.0 delivery postlogistics dangerous goods new [13.0] Add delivery_postlogistics_dangerous_goods Jun 11, 2021
@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from 0758137 to ce84dd1 Compare June 11, 2021 12:46
],
"website": "https://github.com/OCA/delivery-carrier",
"installable": True,
"auto_install": False,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

auto_install False is the default, so not really needed, here.
But does it not make sense to have it set to True ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I don't know in what case we should enable auto-install or not

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With auto_install set to True your module will be automatically installed when both its dependencies are installed. Which in my opinion makes sense in this case.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes sense to set it to True as this module doesn't break the base PostLogistics module.

Copy link
Contributor

@simahawk simahawk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG, one comment by @TDu needs answer

],
"website": "https://github.com/OCA/delivery-carrier",
"installable": True,
"auto_install": False,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@dreispt
Copy link
Member

dreispt commented Jul 3, 2021

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 13.0-ocabot-merge-pr-367-by-dreispt-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Jul 3, 2021
Signed-off-by dreispt
@OCA-git-bot
Copy link
Contributor

@dreispt your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-367-by-dreispt-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from ce84dd1 to 1565b8a Compare July 5, 2021 08:44
@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from 1565b8a to 6c61162 Compare September 15, 2021 07:50
@grindtildeath
Copy link
Contributor

@mmequignon Can you please fix the CI ?

@sebalix sebalix force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from 6c61162 to 2e5d1f0 Compare October 11, 2021 13:35
@sebalix
Copy link
Contributor

sebalix commented Oct 11, 2021

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 13.0-ocabot-merge-pr-367-by-sebalix-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Oct 11, 2021
Signed-off-by sebalix
@OCA-git-bot
Copy link
Contributor

@sebalix your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-367-by-sebalix-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@sebalix
Copy link
Contributor

sebalix commented Oct 11, 2021

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 13.0-ocabot-merge-pr-367-by-sebalix-bump-nobump, awaiting test results.

@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from dda5608 to 939ed46 Compare October 14, 2021 12:44
@mmequignon mmequignon force-pushed the 13.0-delivery-postlogistics-dangerous-goods_new branch from 939ed46 to 7eabbca Compare October 14, 2021 14:11
@sebalix
Copy link
Contributor

sebalix commented Oct 14, 2021

Let's try again...
/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 13.0-ocabot-merge-pr-367-by-sebalix-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Oct 14, 2021
Signed-off-by sebalix
@OCA-git-bot
Copy link
Contributor

@sebalix your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-367-by-sebalix-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@yvaucher
Copy link
Member

Is it intended to have that kind of output? It seems too verbose and not giving significant informations. The label binary gives a lot of noise.
It could reach some limit of the output or something like that.

Travis is still unhappy.

https://app.travis-ci.com/github/OCA/delivery-carrier/jobs/543251740#L1416

@nilshamerlinck
Copy link
Contributor

Hi @mmequignon we faced this issue before and a workaround was to mute vcr logger for the case involving the big response; I tried it here, seems to work

@dreispt
Copy link
Member

dreispt commented Nov 26, 2021

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 13.0-ocabot-merge-pr-367-by-dreispt-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Nov 26, 2021
Signed-off-by dreispt
@mmequignon
Copy link
Member Author

@dreispt thanks Daniel, but I think there's some action to do on my side before trying.
I have no time right now, but will fine to find some.
Sorry about that…

@OCA-git-bot
Copy link
Contributor

@dreispt your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-367-by-dreispt-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 10, 2022
@simahawk simahawk added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Apr 12, 2022
@rousseldenis
Copy link
Contributor

@mmequignon No news on this ?

@simahawk
Copy link
Contributor

@mmequignon ping

@simahawk
Copy link
Contributor

we keep only v14 OCA/wms#334

@simahawk simahawk closed this Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved needs fixing no stale Use this label to prevent the automated stale action from closing this PR/Issue. ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants