profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/colinscape/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Colin Ross colinscape @float Cambridgeshire, UK https://colinscape.com Engineering Manager at Float by day. Striving to create additional joy through software by night.

colinscape/google-suggest 4

Use Google Suggest to complete a query.

colinscape/buffer-api 3

Node wrapper for the Buffer API.

colinscape/male 3

Utility to provide male forename.

colinscape/nonogram 3

Utility to solve nonograms.

colinscape/earley-parser 2

An Earley parser.

colinscape/logically 2

Solve logic puzzles

colinscape/articles 1

Various materials related to articles.

colinscape/bbc-daily-stories 1

Retrieve BBC news stories from a specific day.

colinscape/bbc-news-archive 1

BBC news articles by day

colinscape/censorasaurus 1

Chrome extension to replace disagreeable words with dinosaurs.

push eventbufferapp/buffer-publish

Colin Ross

commit sha 142a638033e23ed013abb2ef61f433ec01c35f04

Update bufflog version

view details

Colin Ross

commit sha d03167bf89542dde13b80124ea8e47342ca24ad7

Bufflog v0.3.1

view details

Colin Ross

commit sha b66229e78d0238a60bb60c2282e970166571792d

Merge pull request #1844 from bufferapp/fix/bump-bufflog-version Fix/bump bufflog version

view details

push time in 2 months

delete branch bufferapp/buffer-publish

delete branch : fix/bump-bufflog-version

delete time in 2 months

PR merged bufferapp/buffer-publish

Reviewers
Fix/bump bufflog version

Description

Update bufflog just like previous attempt, but this time the package should work.

Context & Notes

Related to issues discussed in Slack: https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

Screenshots (if appropriate)

Best Practices Checklist

  • [X] My code follows the code style and guidelines of this project. <!--- eslint -->
  • [X] I have added tests to cover my changes.
  • [X] I have tested different user stories.
  • [X] I have identified similar or related features and tested they are still working.
  • [X] I have performed a self-review of my own code.
  • [X] I have tested my changes/additions in the latest Chrome, Firefox, and Safari.
  • [X] I have commented my code, particularly in hard-to-understand areas.
  • [X] I kept accessibility in mind by following the a11y checklist.
  • [X] I have considered security, abuse & compliance implications of my changes.

⚠️ Pre-deploy Checklist

  • [X] I have manually loaded the URL of the staging deployment and confirmed it's working (see below**)
  • [X] I have confirmed that the Cypress E2E test is passing (Note: we have a known issue where it doesn't run on some PRs. Hopefully this will be fixed soon.)
  • [X] I have confirmed that all other tests are passing.

** To visit the URL of the staging deployment, please vlick the link in the bot comment, or look under checks at the bottom of this PR and click "Details" next to bufferbotbrains/cicd-buffer-publish image

+58 -93

1 comment

2 changed files

colinscape

pr closed time in 2 months

PR opened bufferapp/buffer-publish

Reviewers
Fix/bump bufflog version

Description

Update bufflog just like previous attempt, but this time the package should work.

Context & Notes

Related to issues discussed in Slack: https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

Screenshots (if appropriate)

Best Practices Checklist

  • [ ] My code follows the code style and guidelines of this project. <!--- eslint -->
  • [ ] I have added tests to cover my changes.
  • [ ] I have tested different user stories.
  • [ ] I have identified similar or related features and tested they are still working.
  • [ ] I have performed a self-review of my own code.
  • [ ] I have tested my changes/additions in the latest Chrome, Firefox, and Safari.
  • [ ] I have commented my code, particularly in hard-to-understand areas.
  • [ ] I kept accessibility in mind by following the a11y checklist.
  • [ ] I have considered security, abuse & compliance implications of my changes.

⚠️ Pre-deploy Checklist

  • [ ] I have manually loaded the URL of the staging deployment and confirmed it's working (see below**)
  • [ ] I have confirmed that the Cypress E2E test is passing (Note: we have a known issue where it doesn't run on some PRs. Hopefully this will be fixed soon.)
  • [ ] I have confirmed that all other tests are passing.

** To visit the URL of the staging deployment, please vlick the link in the bot comment, or look under checks at the bottom of this PR and click "Details" next to bufferbotbrains/cicd-buffer-publish image

+58 -93

0 comment

2 changed files

pr created time in 2 months

PR closed bufferapp/buffer-publish

Reviewers
Update bufflog version

Description

Updated bufflog version following problems and discussion: https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

Context & Notes

buffer-publish pods were going into a crash loop state. Tracked it down to some overly verbose logs and probably the pino-http library which was updated a few hours ago.

Screenshots (if appropriate)

Best Practices Checklist

  • [ ] My code follows the code style and guidelines of this project. <!--- eslint -->
  • [ ] I have added tests to cover my changes.
  • [ ] I have tested different user stories.
  • [ ] I have identified similar or related features and tested they are still working.
  • [ ] I have performed a self-review of my own code.
  • [ ] I have tested my changes/additions in the latest Chrome, Firefox, and Safari.
  • [ ] I have commented my code, particularly in hard-to-understand areas.
  • [ ] I kept accessibility in mind by following the a11y checklist.
  • [ ] I have considered security, abuse & compliance implications of my changes.

⚠️ Pre-deploy Checklist

  • [ ] I have manually loaded the URL of the staging deployment and confirmed it's working (see below**)
  • [ ] I have confirmed that the Cypress E2E test is passing (Note: we have a known issue where it doesn't run on some PRs. Hopefully this will be fixed soon.)
  • [ ] I have confirmed that all other tests are passing.

** To visit the URL of the staging deployment, please vlick the link in the bot comment, or look under checks at the bottom of this PR and click "Details" next to bufferbotbrains/cicd-buffer-publish image

+58 -93

1 comment

2 changed files

colinscape

pr closed time in 2 months

create barnchbufferapp/buffer-publish

branch : fix/bump-bufflog-version

created branch time in 2 months

push eventbufferapp/js-bufflog

Colin Ross

commit sha 6bafda768999748936328f11556637d96648e768

Bump version

view details

Colin Ross

commit sha 4fcc4d72d6c7828809fcbb70d3281f1fcd77f9a8

Merge pull request #19 from bufferapp/fix/publish-correctly Bump version

view details

push time in 2 months

delete branch bufferapp/js-bufflog

delete branch : fix/publish-correctly

delete time in 2 months

PR merged bufferapp/js-bufflog

Bump version

v0.3.1

+1 -1

0 comment

1 changed file

colinscape

pr closed time in 2 months

PR opened bufferapp/js-bufflog

Bump version

v0.3.1

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchbufferapp/js-bufflog

branch : fix/publish-correctly

created branch time in 2 months

PR opened bufferapp/buffer-publish

Update bufflog version

Description

Updated bufflog version following problems and discussion: https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

Context & Notes

buffer-publish pods were going into a crash loop state. Tracked it down to some overly verbose logs and probably the pino-http library which was updated a few hours ago.

Screenshots (if appropriate)

Best Practices Checklist

  • [ ] My code follows the code style and guidelines of this project. <!--- eslint -->
  • [ ] I have added tests to cover my changes.
  • [ ] I have tested different user stories.
  • [ ] I have identified similar or related features and tested they are still working.
  • [ ] I have performed a self-review of my own code.
  • [ ] I have tested my changes/additions in the latest Chrome, Firefox, and Safari.
  • [ ] I have commented my code, particularly in hard-to-understand areas.
  • [ ] I kept accessibility in mind by following the a11y checklist.
  • [ ] I have considered security, abuse & compliance implications of my changes.

⚠️ Pre-deploy Checklist

  • [ ] I have manually loaded the URL of the staging deployment and confirmed it's working (see below**)
  • [ ] I have confirmed that the Cypress E2E test is passing (Note: we have a known issue where it doesn't run on some PRs. Hopefully this will be fixed soon.)
  • [ ] I have confirmed that all other tests are passing.

** To visit the URL of the staging deployment, please vlick the link in the bot comment, or look under checks at the bottom of this PR and click "Details" next to bufferbotbrains/cicd-buffer-publish image

+58 -93

0 comment

2 changed files

pr created time in 2 months

create barnchbufferapp/buffer-publish

branch : task/update-bufflog

created branch time in 2 months

delete branch bufferapp/js-bufflog

delete branch : task/lock-down-pino-http-dependency

delete time in 2 months

push eventbufferapp/js-bufflog

Colin Ross

commit sha 8e2a8738d166c2df0501cadf79965415a96cfbc4

Lock down pino-http

view details

Colin Ross

commit sha ed4d7034713fcf7ea90458d451f8b983779712f6

Merge pull request #18 from bufferapp/task/lock-down-pino-http-dependency Lock down pino-http - v0.3.0

view details

push time in 2 months

PR merged bufferapp/js-bufflog

Reviewers
Lock down pino-http - v0.3.0

Based on discussion around some crashing of the buffer-publish pods. https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

We narrowed the problem down to seemingly be the 5.6.0 version of pino-http which is coming in via bufflog.

This PR tweaks the dependencies to not grab minor versions based on semantic versioning (and https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/ in particular!).

Has not been published to npm yet.

+132 -1398

1 comment

2 changed files

colinscape

pr closed time in 2 months

PR opened bufferapp/js-bufflog

Reviewers
Lock down pino-http - v0.3.0

Based on discussion around some crashing of the buffer-publish pods. https://buffer.slack.com/archives/C151RRDL1/p1626956553095000

We narrowed the problem down to seemingly be the 5.6.0 version of pino-http which is coming in via bufflog.

This PR tweaks the dependencies to not grab minor versions based on semantic versioning (and https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/ in particular!).

Has not been published to npm yet.

+132 -1398

0 comment

2 changed files

pr created time in 2 months

create barnchbufferapp/js-bufflog

branch : task/lock-down-pino-http-dependency

created branch time in 2 months

startedredwoodjs/redwood

started time in 3 months