dpoll — Creating A Poll With Lengthy Answer Encounters 500 Response
The open source decentralized polling app dpoll allows users to pose questions to fellow Steemians and record the survey results on the Steem blockchain. The increasingly popular application is fairly new, born at the Utopian Hackathon in 2018. This post discusses a problem that occurs if a user tries to post a poll where one or more of the answers is a long string.
Project Information
- Repository: https://github.com/emre/dpoll.xyz
- Project Name: dpoll
- Publisher (if applicable): @emrebeyler, et al.
Expected behavior
- A user is able to create a poll with one or more lengthy answers
- If there is a limit to the length of answers and a new poll exceeds it:
- The user is informed and the attempt fails gracefully
- Ideally, the length of the answer is validated client side and the user may be informed before attempting to submit
Actual behavior
- If a poll is created with at least one very long answer a partially broken poll is created:
- The user encounters a 500 response upon submitting the poll
- The user encounters a 500 response if attempting to edit the poll
- The poll may appear to the creating user on dpoll.xyz, but not on Steemit, steemd, etc.
- On dpoll.xyz any shorter answers will be listed on the poll, but the lengthy answer will not appear
How to reproduce
- Create a new poll.
- Add Question and Description.
- Add some brief answers (e.g. Yes, No, Maybe)
- Add a lengthy answer option. (e.g. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin a molestie lectus, vel scelerisque velit. Nunc ultricies, turpis in ullamcorper lobortis, augue mauris viverra velit, vitae rhoncus metus nisl vel purus. In non auctor lacus, eget finibus orci. Donec a viverra dui. Nunc nec neque lectus. Praesent in ipsum at.)
- Submit the poll
Recording Of The Bug
.
Report(s) to Maintainer
- @tdre opened this as issue #82 in the dpoll repository here.
- The problem was mentioned to the developers' #bug-reports channel on discord.
As a note to the Utopian reviewer(s) it's clear from the exchange above the @emrebeyler intended to whitelist this project. It may be that PO's are not yet broadly aware that the bug-hunt policy has evolved to expect explicit whitelisting.
Also, @knowledges had conveyed in #general chat that "due to very few reports to the bug-hunting category, we decided to open the category to other projects outside the whitelist. To avoid spam, the report should be acknowledged by any of the project maintainers." I believe this requirement has been met by the foregoing exchange.
HI @tdre, thanks for making this contribution.
I can see the PO has self-assigned the issue. Hopefully, there is a fix in the works.
I appreciate that you first opened this issue on github and waited for the acknowledgment of the bug from the PO before posting to Utopian.
Are you aware that you can include in your report an analysis of what caused the bug? You can also propose or suggest a possible fix. Doing this will earn you extra points on the questionnaire. Well, you can give it a try in your next contribution :)
In regards to this
I am not aware of this being made official. However, since the PO has acknowledged the bug in the ticket you opened with a promise to look into it, then it must be of value and Utopian is about adding value to the open source community.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Chat with us on Discord.
[utopian-moderator]
Thanks for the helpful feedback @fego. Yes, sometimes I do include a suggested fix. It depends how much time I have. In this instance I also was still getting familiar with the code so I figured the PO would have a faster track to the best answer.
I appreciate your comments. Keep up the great work.
Thank you for your review, @fego! Keep up the good work!
Thanks for contributing to the dPoll content.
You have been upvoted from our community curation account (@dpoll.curation) in courtesy of This Guy... @bluerobo.
Come, join our community at dPoll discord server.
If you want to support dPoll curation, you can also delegate some steem power. Quick steem connect links to delegate:
50SP | 100SP | 250SP | 500SP
By the way @bluerobo I usually spell it dpoll, taking my cue from the readme file on github. But I noticed in the curation comment it's dPoll.
Does the team have a preference?
We mostly use dPoll. As long as you don't say "pool", you are golden ;)
Posted using Partiko Android
Congratulations! This post has been upvoted from the communal account, @minnowsupport, by tdre from the Minnow Support Project. It's a witness project run by aggroed, ausbitbank, teamsteem, someguy123, neoxian, followbtcnews, and netuoso. The goal is to help Steemit grow by supporting Minnows. Please find us at the Peace, Abundance, and Liberty Network (PALnet) Discord Channel. It's a completely public and open space to all members of the Steemit community who voluntarily choose to be there.
If you would like to delegate to the Minnow Support Project you can do so by clicking on the following links: 50SP, 100SP, 250SP, 500SP, 1000SP, 5000SP.
Be sure to leave at least 50SP undelegated on your account.
img credz: pixabay.com
Nice, you got an awesome upgoat, thanks to @tdre
Want a boost? Minnowbooster's got your back!
Hi @tdre!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @tdre!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!