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

Continued account prefix fixes #46

Merged
merged 2 commits into from
Mar 23, 2020
Merged

Continued account prefix fixes #46

merged 2 commits into from
Mar 23, 2020

Conversation

jackzampolin
Copy link
Member

ref: #43

@jackzampolin
Copy link
Member Author

This is working for me! Looks like we have this issue fixed for the moment.

@jackzampolin jackzampolin merged commit e387fa1 into master Mar 23, 2020
@jackzampolin jackzampolin deleted the jack/addr branch March 23, 2020 00:52
This was referenced Mar 23, 2020
@zmanian
Copy link
Member

zmanian commented Mar 23, 2020

This whole thing is just a race condition waiting to happen.

We need to find a way that doesn't relay on global state.

@zmanian
Copy link
Member

zmanian commented Mar 23, 2020

More specifically, inside at the function call boundary, if running inside a goroutine, the go scheduler can context switch.

There may be a way to prevent this using something that prevents the go scheduler from context switching until the function returns.

go routine safety doesn't generally matter in the SDK because it's largely single threaded. But it will probably end up mattering the in the relayer.

@jackzampolin
Copy link
Member Author

@zmanian the global we are relying on is in the SDK. We would need to fix this issue there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants