8000 [FW][FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals. by fw-bot-adhoc · Pull Request #349 · ingadhoc/uruguay · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[FW][FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals. #349

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: 17.0
Choose a base branch
from
Open

[FW][FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals. #349

wants to merge 1 commit into from
+52 −0

Conversation

fw-bot-adhoc
Copy link
Contributor

Ticket: 87804
El campo restrict_mode_hash_table en True en 18 no permite que se validen facturas de cliente electrónicas en localización uruguaya. Esto ya fue reportado a Odoo. Lo mantenemos invisible en 16 para que no haya problemas al migrar a 18.

Forward-Port-Of: #299

@pablohmontenegro @jue-adhoc
[FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electr…
8b23c5f 
…onic journals.

Ticket: 87804
El campo restrict_mode_hash_table en True en 18 no permite que se validen facturas de cliente electrónicas en localización uruguaya. Esto ya fue reportado a Odoo. Lo mantenemos invisible en 16 para que no haya problemas al migrar a 18.

X-original-commit: 20c72be
@roboadhoc
Copy link
Contributor

Pull request status dashboard.

@fw-bot-adhoc
Copy link
Contributor Author

@pablohmontenegro @zaoral cherrypicking of pull request #299 failed.

stdout:

CONFLICT (file location): l10n_uy_edi/views/account_journal_view.xml added in fb2651c ([FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals.) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to l10n_uy_ux/views/account_journal_view.xml.
CONFLICT (modify/delete): l10n_uy_edi/__manifest__.py deleted in HEAD and modified in fb2651c ([FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals.). Version fb2651c ([FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals.) of l10n_uy_edi/__manifest__.py left in tree.

stderr:

13:02:43.153421 git.c:444               trace: built-in: git cherry-pick fb2651ca91a06562ef08d8cdcabf502118542c29
error: could not apply fb2651c... [FIX] l10n_uy_edi: "Lock Posted Entries with Hash" field on uy electronic journals.
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
conflict forwardport
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@fw-bot-adhoc @roboadhoc @pablohmontenegro
0