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

Release v0.34.2 Wishlist #4178

Closed
3 of 7 tasks
alexanderbez opened this issue Apr 23, 2019 · 11 comments
Closed
3 of 7 tasks

Release v0.34.2 Wishlist #4178

alexanderbez opened this issue Apr 23, 2019 · 11 comments

Comments

@alexanderbez
Copy link
Contributor

alexanderbez commented Apr 23, 2019

(non-state-machine breaking) Items that are desired to be included in the v0.34.2 patch release:

Once the above are merged, PRs using the release/v0.34.2 branch will be opened up against develop and master. During the merge to develop, some pending log entries will have to be removed.

/cc @jackzampolin @zmanian


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@jackzampolin
Copy link
Member

jackzampolin commented Apr 24, 2019

Does this want to include: #4172?

Looks good otherwise!

@fedekunze
Copy link
Collaborator

agree, we should definitely include #4172

@alexanderbez
Copy link
Contributor Author

#4172 is already fixed by #4135.

@faboweb
Copy link
Contributor

faboweb commented Apr 24, 2019

When is the release scheduled? If not today, could you do a release with #4135 and release more changes with another patch?

@alexanderbez
Copy link
Contributor Author

@faboweb yes, #4135 is already in this wishlist. The patch release will be out this week.

@faboweb
Copy link
Contributor

faboweb commented Apr 24, 2019

Hm ok. Just saying that in the meantime users can't delegate with Lunie.

@alexanderbez
Copy link
Contributor Author

alexanderbez commented Apr 24, 2019

I see no need to rush just for that. In fact, the issue you're running into w/ Lunie is because you're sending txs with mode=block which btw is not recommended -- they should be sent with mode=sync and have the tx hash displayed, where eventually it shows if the tx is included in a block or fails (eg. how etherscan.io works).

@gamarin2
Copy link
Contributor

I think a querier for total supply is really needed

@alexanderbez
Copy link
Contributor Author

alexanderbez commented Apr 24, 2019

@gamarin2 sure, but the purpose of this patch release is to only include what is necessary. Total supply would be a great addition, but (1) it's still a WIP, (2) could potentially be state-machine-breaking, and (3) would hinder the timely release of this as it would need to be thoroughly tested.

@gamarin2
Copy link
Contributor

Ok sure! Just saying that if we can get that in a non-breaking release, we should do it as soon as possible! :)

@fedekunze
Copy link
Collaborator

fedekunze commented Apr 24, 2019

they should be sent with mode=sync and have the tx hash displayed, where eventually it shows if the tx is included in a block or fails (eg. how etherscan.io works).

@faboweb @jbibla can you double check if this solution works? If it doesn't, I'm in favor of releasing a patch with #4135

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

No branches or pull requests

5 participants