Some network traffic is not reported in warp_network.log
Dupe Check
- [X] I have searched Warp bugs and there are no duplicates
Describe the bug
Hi Warp team,
I was using Wireshark to monitor the traffic coming to/from Warp's servers, and I noticed that there's a constant stream of traffic coming to/from Warp's servers that isn't being reported in warp_network.log. I'm almost certain that this is the just the heartbeat Warp uses to test and see if it has internet connection, so this isn't a scandal or anything.
Is this intended behavior or is this accidental? It might be a good idea to omit those network requests from the network log because it would make it harder to read the actually important log messages.
I suggest trying to remove your periodic network calls altogether. I feel network activity should only happen when users purposefully interact with Warp's features --- not when the terminal is just idling.
To reproduce
- Open Warp
- Watch
warp_network.logusing tail. It will be silent most of the time - Observe network traffic to/from
app.warp.devusing some network monitor. You'll see it exchange a small packet once every second.
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
MacOS 15
Shell Version
fish, version 3.7.1
Current Warp version
v0.2024.10.15.08.02.stable_03
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None