Rust Lang - Fix Rust Data Misassignment Glitch [PT-BR | EN]
Budget: $30 – $250 USD
PESSOAS DO BRASIL TERÃO PRIORIDADES !
Rust Debugging Project: Misassigned futures_ask Data
Overview
This project aims to identify and fix a critical bug in a Rust application that processes real-time market data from the Gate.io exchange via WebSocket. The issue involves data intended for one field (futures_ask) being incorrectly saved into another field — causing inconsistencies in the application's behavior.
Context
The application consumes live order book updates using Gate's WebSocket API.
Internally, the parsed data is mapped into Rust structs for further processing.
However, futures_ask data appears to be assigned or stored in the wrong field, suggesting a potential bug in deserialization or mapping logic.
Objective
The goal is to debug and trace the flow of incoming WebSocket data:
Understand how and where futures_ask is being set.
Identify why the value ends up in the wrong struct field.
Propose and implement a fix.
Requirements
Solid experience in Rust.
Familiarity with asynchronous code, serde, and data parsing.
Experience with WebSockets is a plus, but prior experience with Gate.io is not required.
Tasks Involved
Analyze the relevant data structures (structs) and their mappings.
Review deserialization logic (serde, manual parsing, etc.).
Investigate how incoming data is routed and stored.
Create minimal reproducible examples if needed.
Suggest and implement a correction.
Tools & Tech
Rust (async ecosystem: tokio, futures, etc.)
serde_json
WebSocket client (likely tokio-tungstenite or similar)
log/tracing for diagnostics
Rust Debugging Project: Misassigned futures_ask Data
Overview
This project aims to identify and fix a critical bug in a Rust application that processes real-time market data from the Gate.io exchange via WebSocket. The issue involves data intended for one field (futures_ask) being incorrectly saved into another field — causing inconsistencies in the application's behavior.
Context
The application consumes live order book updates using Gate's WebSocket API.
Internally, the parsed data is mapped into Rust structs for further processing.
However, futures_ask data appears to be assigned or stored in the wrong field, suggesting a potential bug in deserialization or mapping logic.
Objective
The goal is to debug and trace the flow of incoming WebSocket data:
Understand how and where futures_ask is being set.
Identify why the value ends up in the wrong struct field.
Propose and implement a fix.
Requirements
Solid experience in Rust.
Familiarity with asynchronous code, serde, and data parsing.
Experience with WebSockets is a plus, but prior experience with Gate.io is not required.
Tasks Involved
Analyze the relevant data structures (structs) and their mappings.
Review deserialization logic (serde, manual parsing, etc.).
Investigate how incoming data is routed and stored.
Create minimal reproducible examples if needed.
Suggest and implement a correction.
Tools & Tech
Rust (async ecosystem: tokio, futures, etc.)
serde_json
WebSocket client (likely tokio-tungstenite or similar)
log/tracing for diagnostics