Skip to content

fix(azure): normalize GPT-5 chat completion parameters - #2809

Open
royanrosyad85 wants to merge 22 commits into
decolua:masterfrom
royanrosyad85:fix/azure-custom-endpoint
Open

royanrosyad85 wants to merge 22 commits into
decolua:masterfrom
royanrosyad85:fix/azure-custom-endpoint

Conversation

@royanrosyad85

Copy link
Copy Markdown

Summary

  • normalize max_tokens to max_completion_tokens for GPT-5.5 series and reasoning deployments
  • preserve explicit max_completion_tokens without mutating the source request
  • omit unsupported custom temperature values
  • remove incompatible reasoning_effort values for function-tool Chat Completions
  • preserve tools, tool choice, and existing GPT-4 behavior
  • add generic Azure endpoint and deployment unit coverage

Problem

Some OpenAI-compatible coding clients send request parameters that Azure GPT-5 and reasoning deployments reject on /chat/completions, including:

  • max_tokens
  • custom temperature values
  • reasoning_effort together with function tools

These combinations can cause HTTP 400 responses.

Tests

  • Azure executor tests: 7/7 passed
  • Relevant executor and parameter tests: 18/18 passed
  • npm run build: passed

Scope

This PR only updates Azure Chat Completions compatibility.

It does not:

  • add Responses API translation
  • include endpoint-specific logic
  • modify local workflow scripts
  • change GPT-4 behavior

askidmobile added a commit to askidmobile/9router that referenced this pull request Aug 5, 2026
golamrabbi696 added a commit to golamrabbi696/EzRouter that referenced this pull request Aug 12, 2026
royanrosyad85 and others added 17 commits August 31, 2026 10:57
…k fail-open

- killCloudflared: only set intentionalKill when a process was actually killed
  so fresh children keep real exit diagnostics
- probeUrlAlive: resolve via public DNS (1.1.1.1/8.8.8.8) + force IPv4; local
  resolvers filtering *.trycloudflare.com made healthy tunnels probe dead
- enableTunnel: short-link worker registration fails open, never takes down a
  live quick tunnel
- package.json: allowScripts for better-sqlite3 native build
- add unit tests for tunnel healthcheck
Sync master with fix/azure-custom-endpoint (tunnel fixes, Azure executor)
One-command update for non-primary environments: preflight checks (clean
tree, no local divergence), DB backup, ff-only pull from origin, deps,
smoke tests, build, service restart, and live-version verification via
/api/version. Never merges upstream and refuses non-fast-forwards.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant