Shares messages (from me) doesn't have the volume_id of the subtree/node_id

Bug #610702 reported by Guillermo Gonzalez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One storage protocol
Fix Released
High
Unassigned
ubuntuone-storage-protocol (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Shares and NotifyShare messages doesn't have a field for the volume_id of the shared subtree/node.

In order to map a share "from_me" to the node, we need the volume_id since we have multiple volumes (UDFVolumes and the RootVolume).

Related branches

Changed in ubuntuone-storage-protocol:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ubuntu One Ops+ team (ubuntuone-ops+)
Changed in ubuntuone-storage-protocol (Ubuntu):
status: New → Confirmed
importance: Undecided → High
tags: added: chicharra chicharra-maverick
Revision history for this message
John O'Brien (jdobrien) wrote : Re: [Bug 610702] [NEW] Shares messages (from me) doesn't have the volume_id of the subtree/node_id

Before changing share notifications, we should discuss these notifications, who gets them, and what the client does with
them.

Changed in ubuntuone-storage-protocol:
status: Confirmed → In Progress
Changed in ubuntuone-storage-protocol:
status: In Progress → Fix Committed
Changed in ubuntuone-storage-protocol:
status: Fix Committed → Fix Released
Changed in ubuntuone-storage-protocol (Ubuntu):
assignee: nobody → Ubuntu One Ops+ team (ubuntuone-ops+)
status: Confirmed → Fix Released
status: Fix Released → Confirmed
dobey (dobey)
Changed in ubuntuone-storage-protocol (Ubuntu):
status: Confirmed → Fix Released
Curtis Hovey (sinzui)
Changed in ubuntuone-storage-protocol:
assignee: Registry Administrators (registry) → nobody
Changed in ubuntuone-storage-protocol (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.