Comment ID changing on comment.refresh()
See original GitHub issueIssue Description
I do believe this is a bug:
print(ancestor.id)
ancestor.refresh()
print(ancestor.id)
does not always print the same ID.
For example, I have a log entry which has:
item id BEFORE already_responded: dm6wi3q # (code which is outside the scope)
dm6wi3q
dm6vozp
item id AFTER already_responded: dm6vozp # (code which is outside the scope)
I have not yet figured out the exact reproducible steps.
System Information
PRAW Version: 5.0.1 Python Version: 3.6 Operating System: Debian Testing
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Refresh comments section [closed] - php - Stack Overflow
I have put together a JQuery script that when entering a comment, it goes to a database and pulls the result back and...
Read more >Comment — PRAW 7.6.1 documentation
Name Gild Type Cost
Silver gid_1 100
Gold gid_2 500
Platinum gid_3 1800
Read more >submission.comments.list() does not contains all ... - GitHub
I'm unable to get a full list of comments without inspecting the replies of every comment. Sample code. reddit = praw.Reddit() submission =...
Read more >Update the last modified date when there is a new case ...
To update the last modified date on the Case from new Case Comments, follow the below steps: Create a Date/Time field on your...
Read more >wp_update_comment() | Function
The return values for an invalid comment or post ID were changed to false instead of 0. 4.9.0, Add updating comment meta during...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d recommend ignoring the comment if the second refresh fails.
@bboe Awesome. Nice find that doing a second
refresh
is the solution.