Circleci/slack@4.4.2 and exit code 100

Build Environment
1

Looks like I have a problem using the slack orb and I don’t know how to get out it. The problem is that when I send the slack notification I get the dreaded exit code 100 error.

Posting Status
Checking For JQ + CURL: Debian
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'

Exited with code exit status 100
CircleCI received exit code 100

I suspect the problem is related to temporarily testing a forked repo of slack orb before rolling back to vanilla. I have a number of projects all of which work using this orb except this one project. Does circleci cache executors or somesuch?

2

@frey This is due to changes Debian made last week. You can work around this by adding the following as a step prior to any apt commands:

sudo apt-get --allow-releaseinfo-change-suite update

Also, if you are using any legacy circleci images, please update these to the cimg CircleCI convenience images as described here:

https://circleci.com/docs/2.0/circleci-images/
https://circleci.com/developer/images

The newer convenience images should not present this error.

Let me know if you continue to see this issue!

3

Thank you. I solved this by using a vanilla cimg rather than our custom docker.