Merge pull request #263 from c410-f3r/misc

Fix #244

.gitignore

@@ -4,7 +4,6 @@
 **/curl
 **/hpack-test-case
 **/profile.json
-**/proptest-regressions
 **/rustc-ice-*.txt
 **/target
 mdbook-target

.scripts/internal-tests-0.sh

@@ -5,7 +5,7 @@
 $rt rustfmt
 $rt clippy -Aclippy::little-endian-bytes,-Aclippy::panic-in-result-fn
 
-cargo miri test --features http2,postgres,web-socket -p wtx
+cargo miri test --features http2,postgres,web-socket -p wtx two_sta
 
 # WTX
 
@@ -36,7 +36,6 @@ $rt test-with-features wtx matchit
 $rt test-with-features wtx memchr
 $rt test-with-features wtx pool
 $rt test-with-features wtx postgres
-$rt test-with-features wtx proptest
 $rt test-with-features wtx quick-protobuf
 $rt test-with-features wtx rand_chacha
 $rt test-with-features wtx ring
@@ -49,7 +48,6 @@ $rt test-with-features wtx sha1
 $rt test-with-features wtx sha2
 $rt test-with-features wtx simdutf8
 $rt test-with-features wtx std
-$rt test-with-features wtx test-strategy
 $rt test-with-features wtx tokio
 $rt test-with-features wtx tokio-rustls
 $rt test-with-features wtx tracing
@@ -61,7 +59,6 @@ $rt test-with-features wtx x509-certificate
 $rt test-with-features wtx _async-tests
 $rt test-with-features wtx _bench
 $rt test-with-features wtx _integration-tests
-$rt test-with-features wtx _proptest
 $rt test-with-features wtx _tracing-tree
 
 # WTX Macros

.scripts/podman-start.sh

@@ -5,7 +5,7 @@ podman run \
     -e POSTGRES_PASSWORD=wtx \
     -p 5432:5432 \
     -v ./.test-utils/postgres.sh:/docker-entrypoint-initdb.d/setup.sh \
-    docker.io/library/postgres:16
+    docker.io/library/postgres:17
 
 # Utils
 

.test-utils/docker-compose.yml

@@ -5,7 +5,7 @@ services:
         environment:
             POSTGRES_DB: wtx
             POSTGRES_PASSWORD: wtx
-        image: postgres:16
+        image: postgres:17
         ports:
             - 5432:5432
         volumes:

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-Before submitting a PR, you should probably run `./scripts/internal-tests-all.sh` and/or `./scripts/intergration-tests.sh` to make sure everything is fine.
+Before submitting a PR, you should probably run `./scripts/internal-tests.sh` and/or `./scripts/intergration-tests.sh` to make sure everything is fine.
 
 Integration tests interact with external programs like `podman` or require an internet connection, therefore, they usually aren't good candidates for offline development. On the other hand, internal tests are composed by unit tests, code formatting, `clippy` lints and fuzzing targets.