Bit of confusion I ran into: I did tg issue comment then tg issue close (both returned success), but tg issue view kept showing the issue as open with no comments for over a minute, while the tangled.org web UI already showed it closed with the comment. So the write clearly landed, the read just hadn't caught up (appview indexing lag on api.tangled.org, I think).
Not sure if that's tg's to fix or the appview's, but from the CLI it looks like the command silently didn't work. A read-your-writes path after a mutation, or even just a note in the docs about eventual consistency, would save some head-scratching.
(on tg built from master, appview api.tangled.org)
yeah, this is fundamentally the same as #4
it's on the appview unfortunately, and it lags hard.