Opened 9 years ago

Closed 9 years ago

#193 closed defect (fixed)

msgq: real type data isn't encoded and decoded properly

Reported by: zhanglikun Owned by: jelte
Priority: medium Milestone:
Component: ~msgq (obsolete) Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: Add Hours to Ticket:
Total Hours: Internal?:

Description

msgq doesn't encode and decode real type data properly, just use the default encoding/decoding. Create this ticket for record this issue, Jelte has created one patch for it.
As the plan(see ticket 172), msgq will use json, so maybe the patch don't need to be applied. Jelte said on jabber: ": that would be nice, but doing that is the kind of load i want to see a ticket for (and if that ticket is made and assigned to me, i'll mark it wontfix, see ticket #whatever the JSON ticket is)"

Subtickets

Attachments (1)

bind10_encoding_real.patch (1.6 KB) - added by zhanglikun 9 years ago.
The patch for ticket 193(Fix real type data encode/decode problem)

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by zhanglikun

The patch for ticket 193(Fix real type data encode/decode problem)

comment:1 Changed 9 years ago by jelte

Actually, I think this patch should be applied, but since there don't seem to be any tests for this whole class I'd rather put the time in converting to JSON (and making tests for that) than to make them for this and throw them away the moment they're done.

comment:2 Changed 9 years ago by jelte

  • Resolution set to fixed
  • Status changed from new to closed

The patch is going in with ticket #201, so i'm closing it here.

Note: See TracTickets for help on using tickets.