Comment by ~xenrox on ~emersion/hut
This bug is fixed with this commit. We actually don't need an additional nil check since the query only uses non-nullable fields.
REPORTED
RESOLVED FIXED~xenrox assigned ~xenrox to #21 on ~emersion/hut
bug added by ~xenrox on ~emersion/hut
Comment by ~xenrox on ~emersion/hut
Thanks for your report!
This is caused by an out-of-date core-go dependency of builds.sr.ht. I have submitted a patch to fix this and will further add a nil check in hut.
Ticket created by ~xenrox on ~sircmpwn/todo.sr.ht
The submitComment mutations fails with:
pq: missing FROM-clause entry for table ""event""
Example query
mutation { submitComment(trackerId: 8263, ticketId: 1, input: { text: "test" }) { ticket { subject } } }
Comment by ~xenrox on ~emersion/hut
Indeed that looks good and seems to fix my problem.
Comment by ~xenrox on ~emersion/hut
I wanted to align
hut todo ticket list
output and noticed one problem:tabwriter does not handle coloured output very well. It counts the length of the formatting string as if it were displayed in the terminal. I worked around it by making all format strings the same length and while that worked for
hut lists patchset list
, we have a varying amount of coloured labels for each ticket. Right now I see 2-3 options how we could handle this:
- Iterate over all tickets, check which one has the most labels and pad the rest with with "invisible" formatting strings
- Put labels towards the end of the output
- Fork tabwriter and adjust the code as necessary (it is frozen)
Comment by ~xenrox on ~sircmpwn/todo.sr.ht
With the current GraphQL implementation users can always generate such a ticket by setting the timestamp to the zero value (default in go). So there needs to be at least a validation that would forbid such tickets from being created ever again.
Ticket created by ~xenrox on ~sircmpwn/todo.sr.ht
True permissions get returned as false by the GraphQL API. Example query:
query { me { trackers { results { name defaultACL { browse } } } } }
Ticket created by ~xenrox on ~sircmpwn/todo.sr.ht
With such a timestamp it is no longer possible to query the "created" field on tickets. The API will return the error "must not be null". Example query:
query { trackerByOwner(owner: "~emersion", tracker: "hut") { tickets { results { id created } } } }