# random - Cycle.io Community | Cycle.io

Canonical URL: https://cycle.io/community/categories/random

## Were you impacted by GitHub stability issues lately?

random

Hi all. I'm Heiðar, the new Developer Advocate at cycle and I have a question for the community.

With there seeming to be no end to the stability issues GitHub have been dealing with lately I wonder if any of you have been impacted?

I have years of experience operating and maintaining a private GitLab server and was for years pushing for that company to move to either GitLab.com or GitHub - but I'm now revising my stance on the topic. When critical parts of your SDLC have worse uptime and availability than the product that results from that delivery pipeline - it makes sense for business continuity to take back control.

What do you think?

<https://cycle.io/community/threads/6a845dee162f6183c817c5c3/were-you-impacted-by-github-stability-issues-lately>

## Gotcha with redis and IPv6

random

Just a heads up for those who might run into the same issue:

I have an environment with a `redis` container named `redis`. In another container in the same environment, I had a nodejs server trying to connect to the redis server via the `ioredis` library. Basically I had a file like

Copy

```javascript
import { Redis } from "ioredis";
export const redis = new Redis("redis://redis:6379");
```

On server start, I was seeing a stream of errors along the lines of

Copy

```plain
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
    at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
    at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
    at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
```

This was very strange as the two containers were on the same network and `redis` should have been (and turns out, was) a valid hostname. Furthermore I was able to run via SSH on the node server instance:

Copy

```plain
# redis-cli -h redis PING
PONG
```

So the hostname was valid. What was going on?

After some discussion with the cycle team (thanks!!), it turns out the issue is that the internal networking within the environment is all done via IPv6, and by default, the `ioredis` client doesn't allow DNS resolution into IPv6. For whatever reason 🤷🏻‍♂️. But the fix was very simple. This works:

Copy

```javascript
import { Redis } from "ioredis";
export const redis = new Redis({ host: "redis", family: 6 });
```

Explicitly tell the client to use IPv6, and it will.

Perhaps this will come in handy for someone later 😄 again, thanks to the cycle team for finding the solution to this!

<https://cycle.io/community/threads/6837b669c09c5118b34d9be3/gotcha-with-redis-and-ipv6>

## Debian slim-bookworm - intermittent DNS failures

random

Just a friendly note to the community after talking it through with the support guys - slim-bookworm is having intermittent DNS resolver issues. We've narrowed one of our stack issues down to the actual image itself having issues and wanted to warn the community to save yourself a bit of aggravation. If you were debating moving everything to Alpine; let this be a final kick in that direction.

<https://cycle.io/community/threads/6826a66d595054782840e3a2/debian-slim-bookworm-intermittent-dns-failures>

## Should I remove this from quarantine?

random

What's the worst that could happen?

![04333303b7ac6dce90c4cc193f35e04f.png](https://cycle.io/community/_cdn/community-59a7eef0-04333303b7ac6dce90c4cc193f35e04f-360x211-webp.webp)

<https://cycle.io/community/threads/6807ee595020a11d3df00825/should-i-remove-this-from-quarantine>

## DNS Service Throttle

random

My team recently encountered an issue with the Discovery Service where we received the following error in the console:

\`\`\`\[Resolver Throttle\] <ip here> has hit the max hit limit (250) and is being throttled.\`\`\`

After investigating, we discovered that our API was sending an excessive number of requests to a third-party service, which triggered the throttle in the Discovery Service. This throttling then impacted other API requests in our environment.

The Cycle team explained that the throttle is in place "to prevent getting banned from lookup services like Google's domain servers or other public nameservers." The throttle limit resets every five minutes.

We’ve since resolved the issue on our end, but I wanted to share this experience in case anyone else encounters a similar problem. Hopefully, this helps someone avoid the same situation.

<https://cycle.io/community/threads/66edbf21747fbf121f86604f/dns-service-throttle>

## YAML is one of my least favorite things.

random

I've never liked YAML ... probably for the same reason I've never liked python. Indent-sensitive configs? Gross.

... but I know so many of you love YAML. :(

![93228339ef29b635db58f3b5ebcdf1a0.jpeg](https://cycle.io/community/_cdn/community-9855b142-93228339ef29b635db58f3b5ebcdf1a0-512x738-webp.webp)

<https://cycle.io/community/threads/66bd9430a22d7d3991510f30/yaml-is-one-of-my-least-favorite-things>

You've reached the end

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
