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.
