dotnet-client: The local appium process does not stop with SIGINT or SIGTERM
Do I have the most recent component updates?
- I use the most recent available driver/plugin and server versions
Is the component officially supported by the Appium team?
- I have verified the component repository is present under the Appium organization in GitHub
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
During test run Appium generate huge amount of files *.response (like /private/var/folders/v6/fj6k1y_97yz990kh7rpjrvgm0000gp/T/8f1e5b3c-8bd6-44e6-8ddf-142f9e2537f3.response) and not deleted after. I have 240 tests which runs 3-5 times per day and on 3d day temp folder size more then 300GB. Screen shot attached after run 3 time by 1 test.
Expected Behavior
After finish test run should be option to delete it.
Minimal Reproducible Example
Run test
Environment
- Operating system:Mac OS 13.4.1 © (22F770820d)
- Appium server version (output of
appium --version
):2.0.0-rc.5 - Appium driver(s) and their version(s):- uiautomator2@2.29.2
- Appium plugin(s) and their version(s):
- Node.js version (output of
node --version
):v18.15.0 npm
version (output ofnpm --version
):9.6.3- Last component(s) version which did not exhibit the problem:
- Platform and version under test: Pixel 4a,5,5a Android 13
- Real device or emulator/simulator:Real device
Link to Appium Logs
https://gist.github.com/VitaliiPivtorak/36690410feb338a012142b14f610023a
Futher Information
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 29 (10 by maintainers)
yes, it is. The Express framework always transforms all headers to lowercase.
The file will be generated when you start a new session request, so start an appium process + send a new session request to the appium