Summary
dws event consume cannot start its local event bus on Windows 10. Authentication and ordinary DWS read/write operations work, but personal IM event consumption fails before a consumer is started. This blocks a local, event-driven workflow for DingTalk @ mentions and selected conversations.
Environment
- DWS:
v1.0.52 (open edition, commit 4e59f9a)
- OS: Windows 10 Pro 64-bit, version
10.0.19045 (build 19045)
- Installation: local Windows executable
- Event tested:
user_im_message_receive_at
Steps to reproduce
-
Log in successfully with DWS on Windows.
-
Start an event consumer for the supported personal @-mention event:
dws event consume user_im_message_receive_at --format json
-
Observe the startup failure.
Expected behavior
The command starts the local event bus and produces NDJSON event records when the user is mentioned.
Actual behavior
The consumer fails during local bus startup. Retrying once with verbose diagnostics produces the same result.
consume: discover bus: busctl: spawn bus: busctl: start C:\\Users\\<redacted>\\.local\\bin\\dws.exe: fork/exec C:\\Users\\<redacted>\\.local\\bin\\dws.exe: not supported by windows
After the failure, dws event status --event user_im_message_receive_at --format json reports no active holder process and no subscriptions, so there is no lingering consumer/subscription.
Scope and impact
- DWS authentication is successful.
- Normal DingTalk access through DWS works.
- The failure is specific to the Windows local event-consume path.
- This prevents personal real-time workflows such as immediate handling of @ mentions or designated conversation messages. Scheduled/history-based reporting is still possible, but is not an equivalent substitute for event-driven handling.
Regression / version note
The currently installed stable version is v1.0.52. The newer v1.0.53-beta.4 changelog expands personal event subscriptions and changes structured event output, but does not state that this Windows local-bus startup error is fixed. I have therefore not upgraded production use to the beta only to test this failure.
Request
Please confirm whether Windows is a supported runtime for dws event consume in v1.0.52, and whether there is a planned fix or a supported Windows-specific workaround for the local bus launcher.
Security / privacy note
No organization ID, user ID, access token, message content, or webhook URL is included in this report.
Summary
dws event consumecannot start its local event bus on Windows 10. Authentication and ordinary DWS read/write operations work, but personal IM event consumption fails before a consumer is started. This blocks a local, event-driven workflow for DingTalk @ mentions and selected conversations.Environment
v1.0.52(open edition, commit4e59f9a)10.0.19045(build19045)user_im_message_receive_atSteps to reproduce
Log in successfully with DWS on Windows.
Start an event consumer for the supported personal @-mention event:
Observe the startup failure.
Expected behavior
The command starts the local event bus and produces NDJSON event records when the user is mentioned.
Actual behavior
The consumer fails during local bus startup. Retrying once with verbose diagnostics produces the same result.
After the failure,
dws event status --event user_im_message_receive_at --format jsonreports no active holder process and no subscriptions, so there is no lingering consumer/subscription.Scope and impact
Regression / version note
The currently installed stable version is
v1.0.52. The newerv1.0.53-beta.4changelog expands personal event subscriptions and changes structured event output, but does not state that this Windows local-bus startup error is fixed. I have therefore not upgraded production use to the beta only to test this failure.Request
Please confirm whether Windows is a supported runtime for
dws event consumein v1.0.52, and whether there is a planned fix or a supported Windows-specific workaround for the local bus launcher.Security / privacy note
No organization ID, user ID, access token, message content, or webhook URL is included in this report.