platform · inferred from evidence
GitHub
A platform for hosting and collaborating on code repositories.
- TaskingAI fails to start with ConnectionRefusedError on port 8002
When I started the TaskingAI app, I got a ConnectionRefusedError with Errno 10061 Connect call failed (loopback, 8002). I was running the code directly, not via Docker. The maintainer asked for a docker ps screenshot and then gave the answe
- ssl_verify parameter for IndexAsyncio does not work against Pinecone Local
When connecting to a local Pinecone instance (Pinecone Local on the local server, port 5081) using `pc.IndexAsyncio`, SSL verification failed even though the `ssl_verify` parameter was set. The typical pattern of passing the host from `pc.d
- 1Password Connect op connect server create Couldn't issue the token can't grant access to the vault
Following the 1Password Connect README, running `op connect server create Connect --vaults [vault]` fails with: Couldn't issue the token ("can't grant access to the vault: You do not have the requested access to vault", even with proper vau
- Wrong port in redirect_uri with Docker port mapping (FusionAuth 1.37+, fixed in 1.46.0)
Running FusionAuth in Docker with a port mapping like 2222:9011, the Identity Provider login redirect_uri contained the wrong (internal) port from FusionAuth 1.37 through 1.45.x, so the IdP callback went to an unreachable URL and login fail
- zendesk_api gem pins Faraday below 2.0, blocking Faraday 2.x upgrades
Faraday 2.x is out, but the zendesk_api gemspec pins Faraday to `< 2.0.0`. I am using Faraday elsewhere in my app and need to upgrade everything to Faraday 2 — the Zendesk gem is blocking me. Is Faraday 2.x support planned?
- Integer values in whylogs frequent_items show as floats (1.000000)
Logging a pandas DataFrame with an int64 column via why.log, then reading `frequent_items/frequent_strings`, returns values like '1.000000' instead of '1'. The column dtype is int64; the stringified frequent items show floats.
- Embedded Typeform leaks previous answers between users via localStorage; how to reset
My app embeds a Typeform survey that users take repeatedly (e.g. weekly). The embedded form stores partial progress in localStorage under the typeform domain, which my JavaScript cannot clear. If a user abandons the survey and logs out, the
- Tinybird flock.js: rows quarantined for missing session_id
Using the Tinybird web analytics tracker (flock.js) in a Next.js app, about a third of tracked rows ended up in quarantine instead of being ingested. The quarantine error was `Strict type checking failed. Object does not have column 'sessio
- Unable to install windows-amd64 binary of SurrealDB (installer script error)
I tried installing SurrealDB on Windows 10 with iwr https://windows.surrealdb.com -useb | iex and the installer script threw an error before it even created the directory. The thread is from September 2022. The maintainer tobiemh worked thr
- Self-hosted Supabase: uploads over 6MB fail with "tus: failed to resume upload"
On a self-hosted Supabase instance, uploading any file over about 6MB through the dashboard fails with: Failed to upload a file: tus: failed to resume upload, caused by [object ProgressEvent], originated from request (method: HEAD, url: htt
- Storj node will not start: system clock is out of sync with all trusted satellites
A Storj storage node refuses to start on FreeBSD with: system clock is out of sync with all trusted satellites. Despite the message, the clock was fine. Debugging showed the preflight check received zero satellites, so the time check could
- Fix Snowflake connector NotSupportedError on Apple M1
On M1 Macs, older snowflake-connector-python wheels shipped x86_64-only C extensions, so importing or fetching results raised `snowflake.connector.errors.NotSupportedError: Unknown error` (the Arrow C extension could not load). The maintain
- SingleStore Spark connector: SSL read fails on multi-node clusters ("Failed load keyStore" / "Wrong value...
On a multi-node Spark cluster, reading from SingleStore with SSL fails with `java.sql.SQLException: Cannot create PoolableConnectionFactory ((conn=...) Failed load keyStore)` / `java.io.IOException: Wrong value for option 'serverSslCert'`.
- TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' when Recurly...
On recurly-client-python 3.x (3.4.2, python 3.8), hitting the API rate limit crashed the client instead of raising a proper rate-limit error. The traceback ended at `self.rate_limit = int(self.__headers.get("X-RateLimit-Limit"))` in respons
- Puppet apt repo GPG key expired 2025-04-06, apt-get update fails on noble
Installing puppet on Ubuntu 24.04 (noble) failed at apt-get update with a GPG error on the apt.puppet.com repo: the Puppet release key (D6811ED3ADEEB8441AF5AA8F4528B6CD9E61EF26) expired on 2025-04-06, so every InRelease signature check fail
- No test event for HubSpot trigger New Deal Property Change
The HubSpot New Deal Property Change trigger never produced test events. The source was not paginating through deals, so anyone with more than 50 deals had events silently missed.
- OPAL cannot clone private repo with non-default main branch (fixed in 0.1.16)
OPAL server failed to clone a private policy repo when OPAL_POLICY_REPO_MAIN_BRANCH was set to a non-default branch (e.g. dev), with errors like did not find main branch. Cloning worked when the default branch was used, but a configured non
- Plugin did not respond during terraform import with the Orca provider
terraform import with the Orca provider dies with a Plugin did not respond crash. The actual cause was a typo in the provider block: the config used the wrong attribute name or a non-regional endpoint for api_endpoint.
- oci os object put from stdin creates 0-byte object in Cloud Shell (silent data loss)
oci os object put --bucket-name BUCKET --name NAME --file - with stdin in OCI Cloud Shell uploaded a 0-byte object with no error, silently discarding the data. The Oracle CLI team reproduced it (it was Cloud Shell specific) and issued a tem
- Nx 21.4.0: node processes linger at 100% CPU after ending the session
On Nx 21.4.0, after shutting down the dev stack, node processes linger and keep consuming 100% CPU; nx reset --only-daemon kills some but not all of them. Over a day of up/down cycles this leaves multiple node processes spinning and grinds