-
Implement a feature in the app to automatically capture the origin and destination data when a user encounters an error. This will help identify and resolve issues more efficiently.
-
### Description
Currently, WebViews, RN and native layers keep their own traceId. We could enhance the debugging experience by sharing trace across the hybrid applications layers.
Examples
- RN…
-
### Is your feature request related to a problem?
The following workflow is becoming more and more common in modern applications:
The use case involves extracting and storing database changes …
-
Hi, your excellent work insipire me a lot. I collect some real data via the way used in the paper, however, could you please tell me the specific depth map resolution the kinnect take? Thanks a lot.
-
Now I can capture and parse CSI data on beacon frame(frame control field 0x8000) and block ack frame(0x9400). However I am not able to capture data frame (0x8842 or QoS Data) which can be captured on …
y-x-c updated
6 years ago
-
-
It seems like the user is live, and the package is supposed to provide event data. However, after some time, the event data capture stops, and an error is generated below-
![image](https://github.com…
-
### The problem
There are cases where collect-snmp-data.php does capture all SNMP data queried by SNMP.
For example executing the following will not capture `OSPF-MIB::ospfGeneralGroup` into the…
vhuk updated
5 months ago
-
## Current Behavior
1. **Cookie Capture:** Currently, Jitsu captures the __fbc, __fbp, and __ga cookies and places them under “clientIds” in the JSON event data. However, gclid and fbclid are not c…
-