<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>8148</bug_id>
          
          <creation_ts>2015-08-11 10:29:44 +0000</creation_ts>
          <short_desc>Sorting the content of the Layer/Machines table doesn&apos;t work</short_desc>
          <delta_ts>2015-12-14 12:01:50 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Toaster</product>
          <component>toaster</component>
          <version>1.9</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>2.1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Cristina Agurida">cristina-danielax.agurida</reporter>
          <assigned_to name="Michael Wood">michael.g.wood</assigned_to>
          <cc>alexandru.costinx.roman</cc>
    
    <cc>alexandru.damian</cc>
    
    <cc>belen.barros.pena</cc>
    
    <cc>cristiana.voicu</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>stanciux.mihail</cc>
          
          <qa_contact name="Alexandru Roman">alexandru.costinx.roman</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>Regression (Used to work)</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>52986</commentid>
    <comment_count>0</comment_count>
    <who name="Cristina Agurida">cristina-danielax.agurida</who>
    <bug_when>2015-08-11 10:29:44 +0000</bug_when>
    <thetext>STATUS: FAILED
BUILD: 1.9_M2.rc2: c75cefe8a382a63f625123c156137782db118f64
ENVIRONMENT: Ubuntu 15.04 x86_64

STEPS TO REPRODUCE:

1. Open Toaster in managed mode.
2. Create a project.
3. Go to Layers page.
4. Try to sort Layer column.

Expected results:

Sorting should work as expected.

Actual results:

Sorting does not work.
This issue can be seen also in Machines page.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>52987</commentid>
    <comment_count>1</comment_count>
    <who name="Mihail Stanciu">stanciux.mihail</who>
    <bug_when>2015-08-11 10:35:53 +0000</bug_when>
    <thetext>An observation on this:

It looks like the link on the column head (the one that should have been setting the ordering) would reset somehow so that it would point to the same kind of ordering as the one that was being used.

So the link would go &quot;...&amp;orderby=name&quot; instead of going to &quot;...&amp;orderby=-name&quot;.

I hope I was clear in my explanation.

Mihai</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53110</commentid>
    <comment_count>2</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2015-08-14 08:47:21 +0000</bug_when>
    <thetext>Sorting works for me on master:a533776d6ff83b6e3e830137455b8382d002768b

Could you check and if fixed marked as resolved?

Thanks!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53139</commentid>
    <comment_count>3</comment_count>
    <who name="Cristina Agurida">cristina-danielax.agurida</who>
    <bug_when>2015-08-17 08:27:10 +0000</bug_when>
    <thetext>The issue is also present on commit a533776d6ff83b6e3e830137455b8382d002768b,
but is not 100% reproducible.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54754</commentid>
    <comment_count>4</comment_count>
    <who name="Michael Wood">michael.g.wood</who>
    <bug_when>2015-09-28 17:55:44 +0000</bug_when>
    <thetext>Sounds like this may have been a caching issue, I can&apos;t recreate this problem. Are there any further instructions on how to go about this? Or has it been fixed in current master?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>55056</commentid>
    <comment_count>5</comment_count>
    <who name="Mihail Stanciu">stanciux.mihail</who>
    <bug_when>2015-10-08 08:11:30 +0000</bug_when>
    <thetext>This still happens in master: eac61f37e36099f74485dab398b57f3812826d17

Here&apos;s how I managed to reproduce this every time:

Normally, when you click on the column head, you get a quick refresh of the entire page (or at least that&apos;s what it looks like when i do it).
However, there is a small delay between when you click on the table head and when the refresh starts. This issue seems to only happen if you click on the table head twice, once to initialise the refresh and another time before the refresh action &quot;goes through&quot;.

Hope this helps to reproduce the issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>56415</commentid>
    <comment_count>6</comment_count>
    <who name="Michael Wood">michael.g.wood</who>
    <bug_when>2015-11-12 11:56:11 +0000</bug_when>
    <thetext>Still not able to reproduce this problem. I tried throttling the network speed to see if there was a race condition on pressing order-by multiple times but it all worked as expected. You shouldn&apos;t be seeing any page refreshes when pressing order-by on the recipes table. I wonder if you&apos;re talking about the built recipes table rather than the recipes table?

/toastergui/project/2/softwarerecipes/ and 
/toastergui/project/2/machines/

/toastergui/build/2/recipes/

?

Please make sure to include the URL in reports so we know we&apos;re talking about the page.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>56461</commentid>
    <comment_count>7</comment_count>
    <who name="Michael Wood">michael.g.wood</who>
    <bug_when>2015-11-13 12:16:22 +0000</bug_when>
    <thetext>set to needinfo</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>56462</commentid>
    <comment_count>8</comment_count>
    <who name="Mihail Stanciu">stanciux.mihail</who>
    <bug_when>2015-11-13 12:23:27 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; Still not able to reproduce this problem. I tried throttling the network
&gt; speed to see if there was a race condition on pressing order-by multiple
&gt; times but it all worked as expected. You shouldn&apos;t be seeing any page
&gt; refreshes when pressing order-by on the recipes table. I wonder if you&apos;re
&gt; talking about the built recipes table rather than the recipes table?
&gt; 
&gt; /toastergui/project/2/softwarerecipes/ and 
&gt; /toastergui/project/2/machines/
&gt; 
&gt; /toastergui/build/2/recipes/
&gt; 
&gt; ?
&gt; 
&gt; Please make sure to include the URL in reports so we know we&apos;re talking
&gt; about the page.

Hi Michael,

I&apos;ve just tested this and it happens on:

toastergui/project/2/layers/
toastergui/project/2/softwarerecipes/
toastergui/project/2/machines/
toastergui/project/2/images/</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57099</commentid>
    <comment_count>9</comment_count>
    <who name="Michael Wood">michael.g.wood</who>
    <bug_when>2015-12-07 17:11:41 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b90a8dca99656c5f4dead0e092c7e1c0e27fe640</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57244</commentid>
    <comment_count>10</comment_count>
    <who name="Alexandru Roman">alexandru.costinx.roman</who>
    <bug_when>2015-12-14 12:01:50 +0000</bug_when>
    <thetext>Verified on master 2.1_M1_RC1: 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>