Files
nats-server/server
Tomasz Pietrek 8732022d26 Fix JWT claims update if headers are passed in request
Claims update message requires only payload to be passed,
but passing headers should not fail the request.
This change ensures we extract payload from raw message
before decoding it.
Before this change, passing claims update with headers
would return cryptic `expected x chunks` error.

Signed-off-by: Tomasz Pietrek <tomasz@nats.io>
2023-02-28 11:09:18 +01:00
..
2023-01-27 10:43:30 +08:00
2022-07-05 09:33:12 +01:00
2022-01-21 11:03:19 -08:00
2023-01-12 10:31:32 +09:00
2022-09-08 11:28:23 -06:00
2023-02-22 19:54:13 -08:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2022-11-14 08:28:19 -08:00
2023-01-12 10:31:32 +09:00
2022-04-01 17:55:33 -06:00
2021-11-15 17:23:08 -07:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:33:12 +01:00
2021-09-01 14:55:26 -07:00
2022-07-05 09:28:00 +01:00
2022-03-25 12:11:55 -06:00

Tests

Tests that run on Travis have been split into jobs that run in their own VM in parallel. This reduces the overall running time but also is allowing recycling of a job when we get a flapper as opposed to have to recycle the whole test suite.

JetStream Tests

For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.

The script runTestsOnTravis.sh will run a given job based on the definition found in ".travis.yml".

As for the naming convention:

  • All JetStream tests name should start with TestJetStream
  • Cluster tests should go into jetstream_cluster_test.go and start with TestJetStreamCluster
  • Super-cluster tests should go into jetstream_super_cluster_test.go and start with TestJetStreamSuperCluster

Not following this convention means that some tests may not be executed on Travis.