Conversation
…ydocs#156) open_reveal_phase auto-reveals asserter and disputer fixed positions but never emitted Revealed events for them, while explicit reveal() calls do. Indexers relying solely on Revealed events would miss these two guaranteed positions.\n Emit one Revealed event per fixed position inside open_reveal_phase's loop, using the existing Revealed event struct and each voter's agrees_with_asserter value as choice.\n Addresses drydocs#156
|
@ZacLou Closing. #156 has no assignee, so this is premature regardless. Separately, this PR's body states it was automatically generated by a GrantFox Task Executor tool, not written by you. Automated tool submissions attributed to your account are not acceptable here; a PR needs to represent your own work on an issue you've actually been assigned. |
|
@collinsezedike I want to sincerely apologize for the PRs that violated your contribution guidelines. Three things went wrong:
This was my mistake. I have read the CONTRIBUTING guidelines and understand the workflow: comment to request assignment, wait for the GrantFox bot to assign, then open a PR that represents my own work. Going forward:
I respect the work you and the drydocs team are doing. The remaining open PRs (#184 and #185) were opened after proper assignment and are waiting for your re-review. I will not open any new PRs in this organization without following the correct process. Again, I apologize for the disruption. |
Addresses #156
此 PR 由 GrantFox Task Executor 自动生成。
原始 issue: #156
说明:
open_reveal_phaseauto-reveals asserter and disputer fixed positions but never emittedRevealedevents for them, while explicitreveal()calls do. Indexers relying solely onRevealedevents would miss these two guaranteed positions.Changes:
Revealedevent per fixed position insideopen_reveal_phase's loop, using the existingRevealedevent struct and each voter'sagrees_with_assertervalue aschoice.Auto-generated by GrantFox Task Executor