~samwhited

Atlanta, GA

https://blog.samwhited.com

Trackers

~samwhited/blogsync

Last active 12 days ago

~samwhited/soquee

Last active a month ago

~samwhited/terraform-provider-sourcehut

Last active 9 months ago

#201 Markdown is generating some escaped HTML 11 days ago

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

Screenshot: https://i.imgur.com/LUnQT0X.png

#201 Markdown is generating some escaped HTML 11 days ago

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

In a bug report over on builds.sr.ht I wrote the following (let's see if it happens again then I'll add a screenshot):


The message when you connect to a build VM is something along the lines of Connected to build job #123 (failed): https://builds.sr.ht/jobs/~samwhited/123

However, this URL is wrong and will give you a 404. The correct URL would be https://builds.sr.ht/~samwhited/job/123

#257 URL in SSH message is wrong 11 days ago

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

I'm not sure where I'd file it, but I'll dump a screenshot somewhere in case it's only happening for me. This bug report looks all messed up and has some raw HTML in it for me.

#257 URL in SSH message is wrong 11 days ago

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

Further bug report: I have no idea where any of that extra text (the raw HTML) is coming from, maybe some auto linking code int he markdown thing is misbehaving?

#257 URL in SSH message is wrong 11 days ago

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

The message when you connect to a build VM is something along the lines of Connected to build job #123 (failed): https://builds.sr.ht/jobs/~samwhited/123

However, this URL is wrong and will give you a 404. The correct URL would be https://builds.sr.ht/~samwhited/job/123

#256 SSHing into build VM a second time stalls then panics 11 days ago

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

I recently SSHed into a buildvm running Arch and tried to start a service (Docker). It stalled, so I attempted to create a second SSH connection so that I could tail the logs and see what was going on. The second session gives me the text about the VM terminating 4 hours from now, but then never gives me a shell. If I send a SIGINT and try to cancel connecting, it panics with:

^CTraceback (most recent call last):
  File "/usr/bin/buildsrht-shell", line 111, in <module>
    connect(job_id, info)
  File "/usr/bin/buildsrht-shell", line 77, in connect
    "build@localhost", "bash"
  File "/usr/lib/python3.7/subprocess.py", line 341, in call
    return p.wait(timeout=timeout)
  File "/usr/lib/python3.7/subprocess.py", line 1019, in wait
    return self._wait(timeout=timeout)
  File "/usr/lib/python3.7/subprocess.py", line 1653, in _wait
    (pid, sts) = self._try_wait(0)
  File "/usr/lib/python3.7/subprocess.py", line 1611, in _try_wait
    (pid, sts) = os.waitpid(self.pid, wait_flags)
KeyboardInterrupt
Connection to azusa.runners.sr.ht closed.

If multiple connections aren't supported, I would expect it to tell me instead of panicing. If they are supported and the shell can't be launched because of my process eating file descriptors or some other thing that's my fault, I would still not expect to get a panic dumped to me.

#11 Add linter system 12 days ago

Ticket created by ~samwhited on ~samwhited/blogsync

When running convert or publish add some sort of system to run basic lints and let us know about possible problems that can't be fixed. An example might be to detect the use of Hugo shortcodes in blogs we try to convert and warn us that they exist and that we don't inline them.

#10 Support Hugo config files in convert 12 days ago

Ticket created by ~samwhited on ~samwhited/blogsync

In the convert command, support loading Hugo config files and making the minor tweaks we need.

Off the top of my head this includes:

  • rename baseURL to BaseURL
  • add an empty Collection
  • rename defaultContentLanguage to Language
  • rename title to Title
  • rename contentDir to Content

#9 Add draft and future flags to publish/preview 12 days ago

Ticket created by ~samwhited on ~samwhited/blogsync

Add flags to the publish and preview commands to publish draft and future dated blog posts. These will mostly be useful for debugging or publishing to a staging or private dev version of your blog.

#8 Add markdown flag to convert command 12 days ago

Ticket created by ~samwhited on ~samwhited/blogsync

Add a flag (-md or -markdown, maybe?) to the convert flag that also converts Markdown bodies in place to write.as flavored markdown. Make it clear in the documentation that this is not advised and is mostly for debugging.