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

Conflicting message IDs for node and verification #1956

Closed
3 of 6 tasks
jstsddg opened this issue Nov 15, 2021 · 5 comments · Fixed by #1973
Closed
3 of 6 tasks

Conflicting message IDs for node and verification #1956

jstsddg opened this issue Nov 15, 2021 · 5 comments · Fixed by #1973
Labels
bug Something is not working.

Comments

@jstsddg
Copy link

jstsddg commented Nov 15, 2021

Preflight checklist

Describe the bug

The message IDs in the files text/message_verification.go and text/message_node.go start at the same ID 1070000, hence there are conflicting IDs. This causes a problem when implementing custom translations in the self-service UI, because messages can not identified uniquely.

See:

Reproducing the bug

No specific steps are needed.

Relevant log output

No response

Relevant configuration

No response

Version

v0.8.0-alpha.3 (master)

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

No response

@jstsddg jstsddg added the bug Something is not working. label Nov 15, 2021
@aeneasr
Copy link
Member

aeneasr commented Nov 17, 2021

Nice find, would you be open for a fix?

@jstsddg
Copy link
Author

jstsddg commented Nov 17, 2021

Yes I can do that, I would suggest updating text/message_node.go to 1080000 as this ID range seems to be unused. Do you know of any side effects this change could have? Or can the starting ID simply be updated?

@aeneasr
Copy link
Member

aeneasr commented Nov 19, 2021

It can be updated, but we will need to document this as a breaking change!

@zepatrik
Copy link
Member

The referenced commit does not actually solve this problem but a different one with duplicate IDs.

@zepatrik zepatrik reopened this Nov 22, 2021
@aeneasr
Copy link
Member

aeneasr commented Nov 22, 2021

my bad

peturgeorgievv pushed a commit to senteca/kratos-fork that referenced this issue Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants