Fix TUS tests

[Cadons]

Description: During the TUS tests on Windows, there are issues with test file generation and upload. The application crashes intermittently while using CURL, sometimes before and sometimes after the requests are made. Additionally, the cancel and retry operations cause a crash due to a socket exception.

Interestingly, when uploading a regular file (not the test-generated file), everything works fine, suggesting that the problem may be tied to how the test file is handled or generated.

Steps to Reproduce:

1. Generate a test file during the TUS test on a Windows environment.
2. Attempt to upload the test file using CURL.
3. Observe that CURL crashes either before or after the request is sent.
4. Perform a cancel and retry operation.
5. Observe the crash caused by a socket exception during these operations.

Expected Behavior:

• The test file should be generated and uploaded without crashes.
• Cancel and retry operations should not result in socket exceptions or crashes.
• Tests works in the same way in whole platforms

Actual Behavior:

• CURL crashes intermittently during the upload of the test-generated file.
• Cancel and retry operations cause a socket exception and crash.
• MacOS's tests sometimes crashes with strange behaviors on stop operations; for example it upload 10/140 chunks and it complete the upload , making the test fail

Additional Information:

• Uploading a regular file (not generated during the test) works correctly.
• The issue needs further investigation to identify the root cause and implement a fix.
• This issue will not block the Windows release, but the final decision will be made after testing the library in real test applications and conducting performance tests.

Priority: Medium – Not blocking Windows release but requires attention before final performance and application testing.

[Fahad-Ali-Khan-ca]

Hi, I would like to take look at this issue.

[Cadons]

Hi, I would like to take look at this issue.

Sure, every contribution is welcome

[Cadons]

This is the docker-compose for the test enviroment with docker, i will push on the main branch when I finish my issue.

version: "3.0"

services:
  mockoon:
    image: mockoon/cli
    container_name: mockoon
    volumes:
      - ./mockoon-data.json:/data/mockoon-data.json
    environment:
      - MOCKOON_DATA=/data/mockoon-data.json
    command: --data /data/mockoon-data.json
    ports:
      - "3000:3000"

  tusd:
    image: tusproject/tusd
    container_name: tusd
    ports:
      - "8080:8080"
    command: |
      -host=0.0.0.0 \
      -port=8080 \
      -upload-dir=/data
    volumes:
      - ./data:/data`

[Cadons]

can you also fix the fact that sometimes upload is too fast and the tests can't get the correct status of the upload. I tried to put a parrallel check, but it is not always working. It happens on runner mac, on my mac it lawys works.

[Fahad-Ali-Khan-ca]

Hi , thanks for the additional details! I’ll look into the issues with the intermittent crashes and the fast uploads causing status checks to fail. I’ll test in the provided Docker environment and try to replicate the issue on a Mac runner to understand the differences. I’ll keep you updated on my progress!

[Cadons]

You could check if there aren't initialization or other strange things, because tests always pass on linux, but on mac os now they crash, the upload behavior is very strange because after 10 chunks it complete the upload. I will investigate this also, I will update if I find the issue and the solution

[Cadons]

You could check if there aren't initialization or other strange things, because tests always pass on linux, but on mac os now they crash, the upload behavior is very strange because after 10 chunks it complete the upload. I will investigate this also, I will update if I find the issue and the solution

I have fixed the pause, sometimes it seems there are some issue yet, if you find something wrong fix it, i have added an abort all in the pause call