The error message on hitting a rate limit helpfully provides a suggestion of restarting while skipping the first few issues. Unfortunately, the count provided there is inaccurate, resulting in duplicate issues being created. Suggested resolutions:
Provide accurate results
(even better) Check for exact duplicate issues before posting an issue
(even better) Provide an option to have the tool automatically retry after the lockout
For example, in the below case, You can see that issues 765-778 are duplicates of 782-795. Oddly the lists diverge after that.
% ietf-comments review.md -g mlswg/mls-protocol -a
Document: draft-ietf-mls-protocol
Revision: 15
CC: @paulwouters
* Created issue 762 in mlswg/mls-protocol: Interaction of MLS and application
* Created issue 763 in mlswg/mls-protocol: Security against malicious members?
* Created issue 764 in mlswg/mls-protocol: Should B receive its own Commit back?
* Created issue 765 in mlswg/mls-protocol: Section 6.3 use of "member"
* Created issue 766 in mlswg/mls-protocol: ENUMs limited to 1 octet?
* Created issue 767 in mlswg/mls-protocol: Epoch rollover?
* Created issue 768 in mlswg/mls-protocol: Padding with zeros
* Created issue 769 in mlswg/mls-protocol: XOR guard
* Created issue 770 in mlswg/mls-protocol: KDF.Nh
* Created issue 771 in mlswg/mls-protocol: Time is not on our side?
* Created issue 772 in mlswg/mls-protocol: lifetime field
* Created issue 773 in mlswg/mls-protocol: Section 8.4
* Created issue 774 in mlswg/mls-protocol: Section 13/14 Race conditions ?
* Created issue 775 in mlswg/mls-protocol: Section 15.1
* Created issue 776 in mlswg/mls-protocol: NOOPs ?
* Created issue 777 in mlswg/mls-protocol: Section 17
* Created issue 778 in mlswg/mls-protocol: Section 17.6
* Created issue 779 in mlswg/mls-protocol: memberlist unavailble before joining
* Created issue 780 in mlswg/mls-protocol: Prospective member or member ?
* Created issue 781 in mlswg/mls-protocol: "server" is ambiguous here
Github Issue Creation Error: You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later. - restart with --start=4
% ietf-comments review.md -g mlswg/mls-protocol -a --start=4
Document: draft-ietf-mls-protocol
Revision: 15
CC: @paulwouters
* Created issue 782 in mlswg/mls-protocol: Section 6.3 use of "member"
* Created issue 783 in mlswg/mls-protocol: ENUMs limited to 1 octet?
* Created issue 784 in mlswg/mls-protocol: Epoch rollover?
* Created issue 785 in mlswg/mls-protocol: Padding with zeros
* Created issue 786 in mlswg/mls-protocol: XOR guard
* Created issue 787 in mlswg/mls-protocol: KDF.Nh
* Created issue 788 in mlswg/mls-protocol: Time is not on our side?
* Created issue 789 in mlswg/mls-protocol: lifetime field
* Created issue 790 in mlswg/mls-protocol: Section 8.4
* Created issue 791 in mlswg/mls-protocol: Section 13/14 Race conditions ?
* Created issue 792 in mlswg/mls-protocol: Section 15.1
* Created issue 793 in mlswg/mls-protocol: NOOPs ?
* Created issue 794 in mlswg/mls-protocol: Section 17
* Created issue 795 in mlswg/mls-protocol: Section 17.6
* Created issue 796 in mlswg/mls-protocol: Can?
* Created issue 797 in mlswg/mls-protocol: May implement correctly :-)
* Created issue 798 in mlswg/mls-protocol: 7 or 8 members
* Created issue 799 in mlswg/mls-protocol: Setion 8.7 MAY
* Created issue 800 in mlswg/mls-protocol: Section 9.5 MLS Exporter
* Created issue 801 in mlswg/mls-protocol: Section 10.1 encryption size
Github Issue Creation Error: You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later. - restart with --start=10
The error message on hitting a rate limit helpfully provides a suggestion of restarting while skipping the first few issues. Unfortunately, the count provided there is inaccurate, resulting in duplicate issues being created. Suggested resolutions:
For example, in the below case, You can see that issues 765-778 are duplicates of 782-795. Oddly the lists diverge after that.