Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency ava to v6 #374

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ava (source) ^5.1.1 -> ^6.0.0 age adoption passing confidence

Release Notes

avajs/ava (ava)

v6.1.0

Compare Source

What's Changed

Full Changelog: avajs/ava@v6.0.1...v6.1.0

v6.0.1

Compare Source

What's Changed

Full Changelog: avajs/ava@v6.0.0...v6.0.1

v6.0.0

Compare Source

Breaking Changes
  • AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #​3251 #​3216

  • When tests finish, worker threads or child processes are no longer exited through proces.exit(). If your test file does not exit on its own, the test run will time out. #​3260

  • Changes to watch mode #​3218:

    • Watch mode can no longer be started via the ava.config.* or package.json configuration.
    • The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
    • Watch mode now uses the built-in fs.watch() in recursive mode. This is supported on Linux in Node.js 20 or newer, and MacOS and Windows in Node.js 18 as well. There are caveats to keep in mind.
  • Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #​3246

  • Only native errors are now considered errors by the t.throws() and t.throwsAsync() assertions. Object.create(Error.prototype) is not a native error. #​3229

  • Changes to modules loaded through the require configuration #​3184:

    • If such modules export a default function, this function is now invoked.
    • Local files are loaded through @ava/typescript if necessary.
Improvements
Rewritten watcher

The watcher has been rewritten. It’s now built on fs.watch() in recursive mode.

@vercel/nft is used to perform static dependency analysis, supporting ESM and CJS imports for JavaScript & TypeScript source files. This is a huge improvement over the previous runtime tracking of CJS imports, which did not support ESM.

Integration with @ava/typescript has been improved. The watcher can now detect a change to a TypeScript source file, then wait for the corresponding build output to change before re-running tests.

The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.

See #​3218 and #​3257.

Failed assertions now throw

Assertions now throw a TestFailure error when they fail. This error is not exported or documented and should not be used or thrown manually. You cannot catch this error in order to recover from a failure, use t.try() instead.

All assertions except for t.throws() and t.throwsAsync() now return true when they pass. This is useful for some of the assertions in TypeScript where they can be used as a type guard.

Committing a failed t.try() result now also throws.

See #​3246.

t.throws() and t.throwsAsync() can now expect any error

By default, the thrown error (or rejection reason) must be a native error. You can change the assertion to expect any kind of error by setting any: true in the expectation object:

t.throws(() => { throw 'error' }, {any: true})

See #​3245 by @​adiSuper94.

The require configuration is now more powerful

It now loads ES modules.

Local files are loaded through @ava/typescript if necessary, so you can also write these in TypeScript.

If there is a default export function, it is invoked after loading. The function is awaited so it can do asynchronous setup before further modules are loaded. Arguments from the configuration can be passed to the function (as a [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone)).

See #​3184 by @​sculpt0r.

Other changes worth noting
  • Internal events can now be observed (experimentally). See #​3247 by @​codetheweb. It’s experimental and undocumented.
  • You can now use t.timeout.clear() to restore a previous t.timeout(). #​3221
  • Code coverage is flushed to disk at opportune moments. #​3220
New Contributors

Full Changelog: avajs/ava@v5.3.1...v6.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

🚨 Rust Panic Audit: 123 Potential Panic Points Detected 🚨

Crate: federation_query_planner

📊 Total Usages: 50

  • 🎁 unwrap usages: 29
  • 🔢 array_index usages: 10
  • 🔎 expect usages: 8
  • 🚨 panic usages: 3

Crate: jwt_auth

📊 Total Usages: 45

  • 🎁 unwrap usages: 43
  • 🔢 array_index usages: 2

📌 Expected Annotations

  •     let client = wasm_polyfills::create_http_client().build().unwrap();: // @expected: if initiating an http client fails, then we have to exit.
    

Crate: engine

📊 Total Usages: 12

  • 🔎 expect usages: 1
  • 🎁 unwrap usages: 8
  • 🚨 panic usages: 3

📌 Expected Annotations

  •     panic!(: // @expected: without a fetcher, there's no executor, without an executor, there's no gateway.
    
  •         panic!("Failed while initializing the executor's fetcher for Federation source");: // @expected: without a fetcher, there's no executor, without an executor, there's no gateway.
    
  •     panic!("Failed while initializing the executor's fetcher for Federation source");: // @expected: without a fetcher, there's no executor, without an executor, there's no gateway.
    
  •     Err(e) => panic!("failed to construct endpoint: {:?}", e),: // @expected: if we are unable to construct the endpoints and attach them onto the gateway's http server, we have to exit
    
  • ConductorGateway::execute(request, &gw.routes[0].route_data).await: // @expected: we can safely index here, it's inside a test with constant defined fixtures.
    

Crate: telemetry

📊 Total Usages: 5

  • 🎁 unwrap usages: 2
  • 🔢 array_index usages: 3

Crate: conductor

📊 Total Usages: 3

  • 🔎 expect usages: 1
  • 🎁 unwrap usages: 1
  • 🚨 panic usages: 1

📌 Expected Annotations

  •   tracing::subscriber::set_global_default(subscriber).expect("failed to set up tracing");: // @expected: we need to exit the process, if the logger can't be correctly set.
    
  •   panic!("Failed to initialize gateway: {:?}", e);: // @expected: we need to exit the process, if the provided configuration file is incorrect.
    

Crate: vrl

📊 Total Usages: 3

  • 🔢 array_index usages: 3

📌 Expected Annotations

  •     panic!("failed to compile vrl program");: // @expected: if the provided VRL code in the config file can't compile, we have to exit.
    
  •   .expect("can't merge states when `states` is an empty vector!"): // @expected: `states` is a non-user provided variable
    

Crate: tracing

📊 Total Usages: 3

  • 🎁 unwrap usages: 3

Crate: cloudflare_worker

📊 Total Usages: 1

  • 🚨 panic usages: 1

Crate: config

📊 Total Usages: 1

  • 🚨 panic usages: 1

📌 Expected Annotations

  • .expect("Failed to serialize json schema for config file!");: // @expected: part of development docgen CLI
    
  • .expect("Failed to write the json schema to the file system!");: // @expected: part of development docgen CLI
    
  • .unwrap();: // @expected: statically defined regex pattern, we know it works ;)
  •   panic!("Failed to interpolate config file, please resolve the above errors");: // @expected: 👇
    
  •   parse_config_from_json(&config_string).expect("Failed to parse JSON config file"): // @expected: 👇
    
  •   parse_config_from_yaml(&config_string).expect("Failed to parse YAML config file"): // @expected: 👇
    
  •     _ => panic!("Unsupported config file extension"),: // @expected: 👇
    
  •   None => panic!("Config file has no extension"),: // @expected: 👇
    

Crate: graphiql

📊 Total Usages: 0

Crate: trusted_documents

📊 Total Usages: 0

Crate: disable_introspection

📊 Total Usages: 0

📌 Expected Annotations

  •       panic!("failed to compile vrl program for disable_introspection plugin");: // @expected: we need to exit the process if our provided VRL condition has incorrect syntax.
    

Crate: test-server

📊 Total Usages: 0

Crate: match_content_type

📊 Total Usages: 0

Crate: http_get

📊 Total Usages: 0

Crate: logger

📊 Total Usages: 0

Crate: common

📊 Total Usages: 0

📌 Expected Annotations

  • .unwrap(): // @expected: we're parsing a statically defined constant, we know it works ;)
    

Crate: napi

📊 Total Usages: 0

📌 Expected Annotations

  • panic!("Exited process!"): // @expected: we need this

Crate: wasm_polyfills

📊 Total Usages: 0

Crate: cors

📊 Total Usages: 0

Crate: minitrace_reqwest

📊 Total Usages: 0

Copy link

🐋 This PR was built and pushed to the following Docker images:

Docker Bake metadata
{
"conductor": {
  "containerimage.config.digest": "sha256:5e18aa97eff68006d438a0aedd9c79b1eec3f3a780ec3d682eb622c58de6ed21",
  "containerimage.descriptor": {
    "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
    "digest": "sha256:17e7ac4d707963286a2aee638cb6aef91ad8572a46d3ef2ce949a6bed07b6b17",
    "size": 902,
    "platform": {
      "architecture": "amd64",
      "os": "linux"
    }
  },
  "containerimage.digest": "sha256:17e7ac4d707963286a2aee638cb6aef91ad8572a46d3ef2ce949a6bed07b6b17",
  "image.name": "ghcr.io/the-guild-org/conductor/conductor:05220df2658d41fb41c147e186ef17e38788e943"
}
}

Copy link

✅ Benchmark Results

     data_received..................: 13 MB   221 kB/s
     data_sent......................: 22 MB   363 kB/s
     http_req_blocked...............: min=831ns    avg=2.76µs   med=2.1µs    max=941.59µs p(95)=3.04µs   p(99)=9.85µs  
     http_req_connecting............: min=0s       avg=350ns    med=0s       max=817.17µs p(95)=0s       p(99)=0s      
     http_req_duration..............: min=310.86µs avg=400.84µs med=377.89µs max=16.56ms  p(95)=465.76µs p(99)=541.58µs
       { expected_response:true }...: min=310.86µs avg=400.84µs med=377.89µs max=16.56ms  p(95)=465.76µs p(99)=541.58µs
     ✓ { scenario:rps_1000 }........: min=310.86µs avg=400.84µs med=377.89µs max=16.56ms  p(95)=465.76µs p(99)=541.58µs
     http_req_failed................: 0.00%   ✓ 0          ✗ 60002
     ✓ { scenario:rps_1000 }........: 0.00%   ✓ 0          ✗ 60002
     http_req_receiving.............: min=10.75µs  avg=25.65µs  med=25.2µs   max=2.16ms   p(95)=33.41µs  p(99)=40.78µs 
     http_req_sending...............: min=6.25µs   avg=15.23µs  med=13.71µs  max=1.28ms   p(95)=26.15µs  p(99)=34.1µs  
     http_req_tls_handshaking.......: min=0s       avg=0s       med=0s       max=0s       p(95)=0s       p(99)=0s      
     http_req_waiting...............: min=271.03µs avg=359.95µs med=337.54µs max=16.47ms  p(95)=425.48µs p(99)=494.33µs
     http_reqs......................: 60002   1000.00515/s
     ✓ { scenario:rps_1000 }........: 60002   1000.00515/s
     iteration_duration.............: min=381.59µs avg=488.18µs med=463.78µs max=16.79ms  p(95)=558.44µs p(99)=692.85µs
     iterations.....................: 60002   1000.00515/s
     ✓ { scenario:rps_1000 }........: 60002   1000.00515/s
     valid_graphql_response.........: 100.00% ✓ 60002      ✗ 0    
     ✓ { scenario:rps_1000 }........: 100.00% ✓ 60002      ✗ 0    
     valid_http_code................: 100.00% ✓ 60002      ✗ 0    
     ✓ { scenario:rps_1000 }........: 100.00% ✓ 60002      ✗ 0    
     vus............................: 2       min=0        max=2  
     vus_max........................: 200     min=200      max=200

Copy link
Contributor Author

renovate bot commented Feb 15, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/ava-6.x branch February 15, 2024 05:57
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