Trouble with GitHub image
Dev tooling4 posts from 4 people4d active+00 posts in the last 7 days, 2 the 7 days before (fading)
Posts per day
The posts behind it
4, newest first[GR-80623] [Native Image] Seg fault starting layered Quarkus on `GenScavengeAllocationSupport.slowNewInstance`...have more information beyond the output above. I've tried to add debug info but that is failing with a different error on startup (filling up a bug shortly). ### Using the latest version of GraalVM can resolve many issues. - [ ] I tried with the [latest...oracle/graal · galderz2 repliesOpen ↗Invalid `type` value for `image_pull_secrets` config### Bug summary Using example from [here](https://docs.prefect.io/v3/advanced/customize-base-job-templates#image-pull-secrets) I'm getting the following error: According to [K8S...PrefectHQ/prefect · rjafarauOpen ↗[Native Image] Analysis fails when an unused permitted subclass of a sealed class is missing### Describe the Issue Native Image fails during analysis when a sealed class names a permitted subclass that is absent from the application JAR, even though that subclass is unused and the application runs successfully on the JVM. The [standalone...oracle/graal · zakkak1 reactions, 2 repliesOpen ↗Git Sync PR images return "Error Fetching Resource" although image renderer succeeds...to what Camo would use: and the endpoint still returns: However, GitHub Camo returns an error when fetching the same resource Purging the Camo URL does not resolve the issue. ### What did you expect to happen? I expected the dashboard screenshots generated by...grafana/grafana · SeanGaluzziOpen ↗
Companies and products named
About this problem
Evidence
4 posts from 4 people in 3 places, about 2 a week over 9 days. Mostly on oracle/graal, grafana/grafana, PrefectHQ/prefect. Tools named alongside: Kubernetes, Grafana, Prefect.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about GitHub with no known issue, sharing the word "image". First post Oct 5, 2026, latest Oct 13, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other GitHub problems
Trouble with GitHub terminalTrouble with GitHub nextGitHub dependency conflicts break installsTrouble with GitHub checkGitHub outages and slowdowns disrupt workMigrating to or off GitHub is slow and riskyGitHub rate limits and usage caps block workRAG on GitHub returns irrelevant or missing contextTrouble with GitHub testGitHub lock-in makes switching costlyTrouble with GitHub proxyGitHub vulnerabilities are hard to triage and patch
History
steady to fading
fading to steady
steady to fading
unverified to corroborated
new to steady
Trouble with GitHub image (2 posts)