~samwhited

Atlanta, GA

https://blog.samwhited.com

Trackers

~samwhited/soquee

Last active a month ago

~samwhited/draft-whited-kitten-password-storage

Last active a month ago

~samwhited/blogsync

Last active 4 months ago

~samwhited/terraform-provider-sourcehut

Last active 1 year, 2 months ago

#214 Updating ticket by status and resolution via API does not work 2 days ago

Comment by ~samwhited on ~sircmpwn/todo.sr.ht

I have not heard anything, but I think the author is working on a new version of the API so this may be low priority. That's just a guess though.

#212 Delete tracker listed twice in API docs 20 days ago

on ~sircmpwn/todo.sr.ht

REPORTED RESOLVED FIXED

#214 Updating ticket by status and resolution via API does not work 21 days ago

Comment by ~samwhited on ~sircmpwn/todo.sr.ht

Amusingly, that is exactly what I was doing when I found this issue :) https://git.sr.ht/~samwhited/sourcehut-go

#280 Request: add title or build file name to build page 23 days ago

Comment by ~samwhited on ~sircmpwn/builds.sr.ht

I don't do python, sorry. Just wanted to make the suggestion, and I hope to see it one day. Thanks for your consideration!

#280 Request: add title or build file name to build page 23 days ago

Ticket created by ~samwhited on ~sircmpwn/builds.sr.ht

Hi,

I have to builds that get run when I push, a set of unit tests and a set of integration tests. Right now when I push the SSH output comes up, I sometimes click both links, then tab over to my browser. However, I can't tell at a glance which tab is the unit tests and which the integration tests without waiting for output and trying to remember which of the tests that are running were one type or the other.

This is a request to add some sort of information to the build pages that identifies what file and repo they were created from (the project is visible only as a hash that you have to click through to make sense of). This might be the repo name / build file path, or a new title attribute in the build that lets me set a name for the pipeline like MyProject Integration Tests, etc.

Thanks for your time!

#23 Sources redirect directly to repo if there's only one 24 days ago

Comment by ~samwhited on ~sircmpwn/hub.sr.ht

Personally I don't love this idea. I think consistency of behavior is more important than saving a click. I don't have a good argument for why it should or should not be done though other than if I expect to see a list I should see the list all of the time, not just some of the time which is more just a weakly held opinion.

#212 Delete tracker listed twice in API docs 25 days ago

Comment by ~samwhited on ~sircmpwn/todo.sr.ht

#214 Updating ticket by status and resolution via API does not work 26 days ago

Comment by ~samwhited on ~sircmpwn/todo.sr.ht

The error appears to come from srht/validation.py:118. I don't understand what's going on well enough to know why things work this way, but the IntFlag class (which TicketStatus is) is a subclass of Enum so thsi branch is being selected even though value ends up being a string value which cannot be created with the IntFlag constructor. I should note that I haven't been able to get srht working locally to test this, I just made a python file taht creates a class and does the logic from this branch to see if the ValueError was hit.

#214 Updating ticket by status and resolution via API does not work 26 days ago

Ticket created by ~samwhited on ~sircmpwn/todo.sr.ht

I am trying to update a ticket per the API docs by sending a PUT request to https://todo.sr.ht/api/user/~samwhited/trackers/mellium/tickets/3 which matches this API endpoint.

The body of my request contains:

{"status":"resolved","resolution":"fixed"}

The status and resolution fields are defined as specified on that API endpoint, however, I get multiple errors returned:

{Field:"status", Reason:"resolved is not a valid TicketStatus", statusCode:400}
{Field:"resolution", Reason:"fixed is not a valid TicketResolution", statusCode:400}

(err format is a Go struct the JSON was unmarshaled to, it should be obvious how it maps to the JSON fields but let me know if there's something missing you need and I'll find a way to bypass this SDK and get at the underlying JSON)

#213 Empty description works in web UI but not in API 26 days ago

Ticket created by ~samwhited on ~sircmpwn/todo.sr.ht

If I submit a ticket with no description in the web UI, it works as expected. If I submit it via the API, I get an error, description is required.

I could see the behavior going either way, but it would be nice if it were consistent, and personally I would prefer empty issues to be allowed for a few reasons:

I am importing issues from GitHub, several of which were created by users without descriptions, or by email using the [EOM] convention indicating that the subject contains all the relevant information. On personal projects I also have a tracker where I keep notes to myself using only the subject and labels as a sort of TODO list. It would be nice to be able to import these via the API.