René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"No way to configure CODEQL_THREADS with an environment variable","articleBody":"The source says this action respects both CODEQL_RAM and CODEQL_THREADS\n\nhttps://github.com/github/codeql-action/blob/5eb3ed6614230b1931d5c08df9e096e4ba524f21/lib/init-action.js#L315C12-L319\n\nthis is true for CODEQL_RAM\n\nhttps://github.com/github/codeql-action/blob/5eb3ed6614230b1931d5c08df9e096e4ba524f21/lib/init-action.js#L320\n\nbut not true for CODEQL_THREADS\n\nhttps://github.com/github/codeql-action/blob/5eb3ed6614230b1931d5c08df9e096e4ba524f21/lib/init-action.js#L322\n\nIs this an oversight or is there a good reason for this?\n\nMy use case is I'm running this on a big 48 core kubernetes but the codeql runner pod is only allowed to use 16 cores. The autodetection is not factoring in the pod limits, it's looking at the node's available resources. I want to hint to codeql that it only has 16 threads available via the CODEQL_THREADS env var.","author":{"url":"https://github.com/austinpray-mixpanel","@type":"Person","name":"austinpray-mixpanel"},"datePublished":"2025-05-06T02:26:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/2890/codeql-action/issues/2890"}