1.8rc1: Filter by node broken in Chromium - angular errors in java script console

Bug #1461256 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Blake Rouse

Bug Description

I was trying to filter by node name name and it wasn't returning any result. The filter was originally for "sirrush". Then I checked java script console. This was in the output:

10.245.0.10/:7 Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: node in tabs.nodes.filtered_items = (nodes | nodesFilter:tabs.nodes.search | orderBy:tabs.nodes.predicate:tabs.nodes.reverse) track by node.system_id, Duplicate key: node-cb70a76c-f8bd-11e3-a5f6-00163eca07b6
http://errors.angularjs.org/1.2.11/ngRepeat/dupes?p0=node%20in%20tabs.nodes…20track%20by%20node.system_id&p1=node-cb70a76c-f8bd-11e3-a5f6-00163eca07b6
    at 10.245.0.10/:6
    at 10.245.0.10/:9
    at Object.h [as fn] (10.245.0.10/:7)
    at u.$digest (10.245.0.10/:7)
    at u.$apply (10.245.0.10/:7)
    at HTMLInputElement.Si.a (10.245.0.10/:8)
    at HTMLInputElement.jQuery.event.dispatch (10.245.0.10/:3333)
    at HTMLInputElement.elemData.handle.eventHandle (10.245.0.10/:2942)
10.245.0.10/:7 Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: node in tabs.nodes.filtered_items = (nodes | nodesFilter:tabs.nodes.search | orderBy:tabs.nodes.predicate:tabs.nodes.reverse) track by node.system_id, Duplicate key: node-a3208c24-c4cd-11e3-8102-00163efc5068
http://errors.angularjs.org/1.2.11/ngRepeat/dupes?p0=node%20in%20tabs.nodes…20track%20by%20node.system_id&p1=node-a3208c24-c4cd-11e3-8102-00163efc5068
    at 10.245.0.10/:6
    at 10.245.0.10/:9
    at Object.h [as fn] (10.245.0.10/:7)
    at u.$digest (10.245.0.10/:7)
    at u.$apply (10.245.0.10/:7)
    at HTMLInputElement.Si.a (10.245.0.10/:8)
    at HTMLInputElement.jQuery.event.dispatch (10.245.0.10/:3333)
    at HTMLInputElement.elemData.handle.eventHandle (10.245.0.10/:2942)

I have attached complete log. F5 clears this issue.

Tags: oil

Related branches

Revision history for this message
Larry Michel (lmic) wrote :
Larry Michel (lmic)
description: updated
Revision history for this message
Raphaël Badin (rvb) wrote :

"F5 clears this issue." : do you mean that after a reload you were able to put the exact same filter and that is worked?

Is this repeatable? Can you provide a list of steps to reproduce this if it is?

Changed in maas:
status: New → Incomplete
importance: Undecided → Critical
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This has nothing to due with the browser it has to do with the server sending a create action on the same object more than once. It is possible for this to occur in some weird race on how the triggers are fired from postgres and how they are processes by the region.

Easiest way and safest way to handle this is client side and check that the item does not already exist in the items array.

Changed in maas:
status: Incomplete → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
milestone: none → 1.8.0
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.