Viewing a response to: @gregorypravda/re-lukestokes-re-jamesbrown-how-does-one-get-around-the-following-error-comment-lastpayout-fc-timepointsec-min-20160814t171744885z
The payout window is based off a 12 hour window (which can change based on if a large SP account votes it up, which adds more time to the payout window). Once that window closes (regardless of the payout amount), that's it for editing.
| author | lukestokes |
|---|---|
| permlink | re-gregorypravda-re-lukestokes-re-jamesbrown-how-does-one-get-around-the-following-error-comment-lastpayout-fc-timepointsec-min-20160814t222348489z |
| category | tech |
| json_metadata | {"tags":["tech"]} |
| created | 2016-08-14 22:23:48 |
| last_update | 2016-08-14 22:23:48 |
| depth | 3 |
| children | 2 |
| last_payout | 2016-08-22 07:04:18 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 235 |
| author_reputation | 556,640,380,599,219 |
| root_title | "How Does One Get Around the Following Error?: comment.last_payout == fc::time_point_sec::min()" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 806,098 |
| net_rshares | 0 |
But what if the payout still says it's $0.00 4 weeks from now? At the very least, that error message needs to be improved, because I really did not get "Sorry it's been more than 12 hours" from "comment.last_payout == fc::time_point_sec::min():"
| author | geotrope |
|---|---|
| permlink | re-lukestokes-re-gregorypravda-re-lukestokes-re-jamesbrown-how-does-one-get-around-the-following-error-comment-lastpayout-fc-timepointsec-min-20160816t021230729z |
| category | tech |
| json_metadata | {"tags":["tech"]} |
| created | 2016-08-16 02:12:24 |
| last_update | 2016-08-16 02:12:24 |
| depth | 4 |
| children | 1 |
| last_payout | 2016-08-22 07:04:18 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 245 |
| author_reputation | 337,799,235 |
| root_title | "How Does One Get Around the Following Error?: comment.last_payout == fc::time_point_sec::min()" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 827,692 |
| net_rshares | 0 |
I think the payout window has been updated to 24 hours as of today. All of this is beta, so I wouldn't count on user-friendly error messages any time soon. If you want to contribute, the code is open source on github. Maybe you could work through the code and find error messages which get shown in the UI and provide more human-friendly wording instead.
| author | lukestokes |
|---|---|
| permlink | re-geotrope-re-lukestokes-re-gregorypravda-re-lukestokes-re-jamesbrown-how-does-one-get-around-the-following-error-comment-lastpayout-fc-timepointsec-min-20160816t022021638z |
| category | tech |
| json_metadata | {"tags":["tech"]} |
| created | 2016-08-16 02:20:21 |
| last_update | 2016-08-16 02:20:21 |
| depth | 5 |
| children | 0 |
| last_payout | 2016-08-22 07:04:18 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 354 |
| author_reputation | 556,640,380,599,219 |
| root_title | "How Does One Get Around the Following Error?: comment.last_payout == fc::time_point_sec::min()" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 827,776 |
| net_rshares | 0 |
hiveblocks