Skip to content
Snippets Groups Projects
Select Git revision
  • 118-borg-backup-not-running-as-it-should
  • 125.dont-set-static-datasource-uids
  • 125.silence-broken-backup-alerts
  • 133.give-access-to-prod-infra
  • 149.fix-bootloader
  • 157.authorize-new-hro-key
  • 162.flexible-grafana-module
  • 163.jp-to-ben-for-prod
  • 164.grafana-alert-rules
  • 190-our-regular-updates-fill-up-the-servers-boot-partitions
  • 207.payment-server-exception-reporting
  • 287.publish-tahoe-error-rate
  • 300.monitor-payment-server
  • 352.cachix
  • 42.update-nixpkgs
  • 445.update-zkapauthorizer
  • 62.openssl-111k
  • 67.rationalize-morph-names.2
  • 87.qemu-local-grid
  • 87.test-local-grid
20 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.025Mar262522171512823Feb161514Jan1223Sep222116151441Jul25Jun23221917111098543130May29529Apr8720Mar26Feb2Dec26Nov201987654131Oct3029282625242321181611427Sep262524232016965429Aug28127614Jun13Take another shot at cryptography upgrademaybe it is pkgsmaybe I can get it from hereand so the tapestry begins to unravel...don't look at meOops, I mean this hash.And get the hash rightOh, it had no effect because we actually use Python 3 for docspromote the pyopenssl overlay to the very topSee if latest pyOpenSSL release fixes test failures against 1.1.1kFix privatestorageops issue 278minor maintainability improvements to the testPropagate overlays to the shell environmentdemonstrate that we have the new opensslThis may actually use the right openssl source.try to override `openssl` tooTry to upgrade OpenSSL to 1.1.1k with an overlayPoint at the locally available <nixpkgs> instead of the upstream locationAttempt a smarter nixpkgs pinAdd deployment environment names so GitLabMerge branch '81.vulnerability-scan' into 'develop'Summarize it toonope - that's ultimate onlyAttempt to trick GitLab into parsing and displaying the reportokay fix this not-arbitrary byte stringtry this expose_as thingRepeat Yourselfemit json instead of textHack our logic into the script insteadJust cannot use exit_codes, it is too new a featureless wrong way to propagate errors maybeAllow the vulnix pipeline to fail but propagate the codeJust ignore vulnix errors entirely?Avoid confusing morph and vulnix errorsSee how this more specific config faresTry to allow the failure through GitLabMerge remote-tracking branch 'origin/develop' into 81.vulnerability-scanMerge branch '61.default-token-count-config' into 'develop'Update ZKAPAuthorizerMerge remote-tracking branch 'whetstone/master'