Marc Hörsken
Marc Hörsken
I am getting the follow error messages from a Windows agent: ``` http error: Unable to write JSON response (err=write tcp 192.168.137.30:1337->192.168.137.31:54478: wsasend: An existing connection was forcibly closed by...
Improve error handling within the current implementation of feature/issue #2.
The WIA microdriver currently handles those issues by always falling back to the user-supplied values. Those input values are basically set in stone, since most implementations of WIA user-interfaces do...
The device management application (devsane.exe) should be enhanced to provide the following functionality: - Provide a GUI selection of options if called without parameters (probably using a Task Dialog) -...
At the moment various types of error handling code flows and error code types are used, e.g.: - HRESULT - LSTATUS - Win32 error code - Boolean
Since the device installation wizard already provides the functionality to specify username and password that are then stored within the device registry key, the following missing pieces need to be...
This needs to be analyzed and evaluated during a proof-of-concept first. Since the WIA microdriver interface itself is not using asynchronous I/O operations the correct type of implementation still needs...
This is in preparation of adding trigger excludes to Azure Pipelines.
Not to be merged. Previous example failure: https://github.com/curl/curl/runs/8285644244
### I did this Let's tackle the remaining flakiness on Windows one-by-one. One of the most prominent examples is the randomly missing QUIT at the end of FTP protocol tests,...