mirror of
https://github.com/openobserve/openobserve.git
synced 2026-11-05 00:09:35 +00:00
Neha PandClaude Opus 4.7
cc5ce31836
## Problem CI job **Pipelines-Regression** consistently fails on: > `[chromium] › pipeline-regression.spec.js:73 › should validate scheduled pipeline SQL query with metrics stream type` with `FetchError: Invalid response body … Premature close` on every attempt. PR #12793 added `fetchWithRetry` to handle transient network errors, but the underlying cause — **node-fetch v2 keep-alive pooling + gzip decompression** — can survive retries when every connection attempt picks up the same dead socket from the pool. ## Root cause `node-fetch` v2 defaults: - `compress: true` → sends `Accept-Encoding: gzip` and pipes response through `Gunzip` - Implicit HTTP agent with `keepAlive: true` → reuses connections across requests When the server closes a pooled connection before the response body is fully read, `Gunzip` throws "Premature close." Because the bad connection stays in the pool, retries can hit the same socket and fail identically. ## Fix - Use `keepAlive: false` agent → every fetch gets a fresh connection - Set `compress: false` → bypass the `Gunzip` stream where the error originates - Keep the retry wrapper as a safety net for any remaining transient faults ## Test plan - [ ] CI: `Pipelines-Regression` job passes (especially the metrics stream type test) - [ ] Full `pipeline-regression.spec.js` suite passes locally 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
zinc-observe-ui-automation
Playwright UI Testing
Installation
npm install
Running Tests
Using Playwright Runner UI (Recommended)
cd playwright-runner
npm start
Then open http://localhost:3000 to access the test runner interface.
Using Command Line
# Run all tests
npx playwright test
# Run specific test by tag
npx playwright test -g @alertsImportExport
# Run in headed mode
npx playwright test --headed
# Run specific test file
npx playwright test Alerts/alerts-import.spec.js
Environment Configuration
Tests can be configured using:
- Playwright Runner UI - Set environment variables through the web interface
- Environment Variables - Set variables in terminal or .env file