StevenMaude
Repos
74
Followers
65
Following
4

:satellite::watch: Update expired Extended Prediction Orbit (EPO) GPS data for Garmin devices, e.g. Forerunner watches. Spend less time waiting for a GPS fix before a run or cycle *without* Garmin's software!

8
0

:mailbox_with_mail: Display the latest mail from a temporary nada email address, at the command line. Useful for getting throwaway confirmation email links, without needing to visit the nada site in browser.

2
0

A Python package that downloads BBC radio programme tracklists; ideal for use with get_iplayer

11
2

:radio::spiral_notepad: Unofficial Python API and command-line client for retrieving BBC Radio programme schedules.

1
1

Events

Docker error messages are not surfaced when jobs fail to execute

(Yes, it's most likely that the underlying problem which highlighted this issue was due to rootless Docker.)

The relevant code hasn't changed since I opened the issue, so it's still an open feature request, unless it's deemed not useful.

The relevant exception raised is a subprocess.CalledProcessError. This has stdout and stderr available as attributes, but these aren't displayed, only the exception itself, which gives you the non-specific exit code failure: …returned non-zero exit status 125.

Exit code 125 in itself isn't too helpful. All it tells you is that docker run failed due to a Docker daemon problem. The full error message would have been more helpful to me in this case. It may therefore be useful to help in other cases where people experience Docker issues.

Created at 1 day ago
issue comment
Clarify Docker installation

The caveat here is that I haven't got a Windows install to test WSL2 with. I assume it works because it's the recommended default for Docker Desktop on Windows, and I don't believe we're doing anything particularly exotic in Windows.

One thing is that Windows 10 doesn't support GUI apps via WSL2 (Windows 11 does), but I don't think that is likely to affect us.

If it is, I can reword to still just suggesting Hyper-V.

Created at 6 days ago
pull request opened
Clarify Docker installation

And also fix some trailing whitespace.

We previously recommended a Docker Desktop installation with Hyper-V.

This is presumably because:

  • Docker Toolbox was not as polished
  • WSL2 was still new, at the time of writing (late 2020)

Advantages to the changes here:

  • we remove the mention of Docker Toolbox, which is now deprecated
  • WSL2 works on Windows Home editions
  • there's no confusion over our guidance saying "use Hyper-V" and Docker Desktop's installer saying "use WSL2"
Created at 6 days ago
create branch
StevenMaude create branch steve/clarify-docker-installation
Created at 6 days ago

Update databuilder docs from f4af635ccb3d689b001c27affa1bd1377e602df2

Merge pull request #1037 from opensafely/autoupdate-databuilder-docs

Update databuilder docs

Created at 6 days ago
delete branch
StevenMaude delete branch autoupdate-databuilder-docs
Created at 6 days ago
pull request closed
Update databuilder docs
Created at 6 days ago
Document creation of dummy data
Created at 6 days ago
pull request closed
Update databuilder docs
Created at 1 week ago

Update databuilder docs from f4de0209887331b6d069cc70193f2d8011525aea

Merge pull request #1032 from opensafely/autoupdate-databuilder-docs

Update databuilder docs

Created at 1 week ago
delete branch
StevenMaude delete branch autoupdate-databuilder-docs
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
issue comment
Surface Deletions Better

As a related question, does this behaviour mean that sensitive data persists via pythonhosted URLs, when that data has been published in a PyPI package?

For example, see this PR where someone requested removal of a package entry from the pypi-data repository, after they also deleted the associated package which contained AWS access keys.[^1]

The PR contains pythonhosted URLs in that PR and these URLs are still accessible for me. That behaviour is in line with @dstufft's comment here:

deletions don't actually delete the underlying file from our blob storage, and files.pythonhosted.org doesn't consult the database, it just goes direct to the blob storage.

It's surprising — and I'm not sure if it's documented somewhere where users might read[^2] — behaviour to me that deleting the package from PyPI does not delete the underlying data.

[^1]: The blog post by the repository owner gives more context. That repository owner deactivated the AWS key themselves, so in this particular case, the details should not longer be sensitive, although do remain an embarrassment :flushed: [^2]: It's not mentioned in the prompt that users see when deleting a package. If there are real legal issues for deletion, then it might also be necessary to make that data entirely inaccessible. (Deletion is often a tricky problem!)

Created at 1 week ago
delete branch
StevenMaude delete branch dependabot/pip/pip-tools-6.10.0
Created at 1 week ago

Bump pip-tools from 6.9.0 to 6.10.0

Bumps pip-tools from 6.9.0 to 6.10.0.


updated-dependencies:

  • dependency-name: pip-tools dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #52 from StevenMaude/dependabot/pip/pip-tools-6.10.0

Bump pip-tools from 6.9.0 to 6.10.0

Created at 1 week ago
pull request closed
Bump pip-tools from 6.9.0 to 6.10.0

Bumps pip-tools from 6.9.0 to 6.10.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 1 week ago
issue comment
Correct capitalisation of "GitHub Pages"

Thanks mate, could you please fix docs/user-guide/writing-your-docs.md as well then?

@ultrabug: thanks for taking a look and spotting I'd missed that one!

There were similar references in one of the Python source files too, so now updated.

The only remaining "GitHub pages" reference I can find is in the release notes, but that's already been published, so leaving as is.

Created at 1 week ago

Correct "GitHub pages" in writing-your-docs.md

Correct "GitHub pages" in gh_deploy.py

Created at 1 week ago
pull request closed
Update databuilder docs
Created at 1 week ago
delete branch
StevenMaude delete branch autoupdate-databuilder-docs
Created at 1 week ago

Update databuilder docs from 57897b61a011227077985e8629c1e29b2cdecdca

Update databuilder docs from 600b2bc9024e48b5f91e84f04e59501fed8dde94

Merge pull request #1024 from opensafely/autoupdate-databuilder-docs

Update databuilder docs

Created at 1 week ago
StevenMaude delete branch dependabot/pip/pip-tools-6.10.0
Created at 1 week ago

Bump pip-tools from 6.9.0 to 6.10.0

Bumps pip-tools from 6.9.0 to 6.10.0.


updated-dependencies:

  • dependency-name: pip-tools dependency-type: direct:development update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #53 from opensafely-core/dependabot/pip/pip-tools-6.10.0

Bump pip-tools from 6.9.0 to 6.10.0

Created at 1 week ago
Bump pip-tools from 6.9.0 to 6.10.0

Bumps pip-tools from 6.9.0 to 6.10.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 1 week ago