Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #1
    Sencha User
    Join Date
    Oct 2011
    Posts
    4
    Vote Rating
    0
    dmsilva is on a distinguished road

      0  

    Default Possible bug in Ext.direct.RemotingProvider error callback

    Possible bug in Ext.direct.RemotingProvider error callback


    Hi, I'm using RemoteProvider, and when the request is cancelled by timeout (success =false), in the onData function I think there is a bug when it will get each transaction. It will pass as args to the getTransaction function the transaction instead the Ajax call info for a transaction.
    Thus, he tries to get each transaction, which will return null. So the callbacks are never executed.


    It is a BUG?

  2. #2
    Sencha - Ext JS Dev Team evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    16,989
    Vote Rating
    649
    evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute

      0  
    Evan Trimboli
    Sencha Developer
    Twitter - @evantrimboli
    Don't be afraid of the source code!

  3. #3
    Sencha User
    Join Date
    Oct 2011
    Posts
    4
    Vote Rating
    0
    dmsilva is on a distinguished road

      0  

    Default Possible bug in Ext.direct.RemotingProvider error callback

    Possible bug in Ext.direct.RemotingProvider error callback


    REQUIRED INFORMATIONExt version tested:
    • Ext 4.07
    Browser versions tested against:
    • Chrome
    • IE7,8,9
    DOCTYPE tested against:
    • ____
    Description:
    • I'm using RemoteProvider, and when the request is cancelled by timeout (success =false), in the onData function I think there is a bug when it will get each transaction. It will pass as args to the getTransaction function the transaction instead the Ajax call info for a transaction.
      Thus, he tries to get each transaction, which will return null. So the callbacks are never executed.
    Steps to reproduce the problem:
    • Make a request that takes longer than the timeout (Ext.Ajax.timeout), and checks if the callback function is called
    The result that was expected:
    • callback function should be called
    The result that occurs instead:
    • callback function is not called
    Test Case:
    Code:
        <<insert working code to reproduce the report >>
    HELPFUL INFORMATIONScreenshot or Video:
    • attached
    See this URL for live test case: http://Debugging already done:
    • none
    Possible fix:
    Code:
    OriginalCode
    onData : function (...){
      transactions = [].concat(options.transaction);
      for (len = transactions.length; i < len; ++i) {       
                       transaction = me.getTransaction(transactions[i]);
    …
    if (transaction) { // Always returns false because getTransaction always returns null (should not receive a transaction but transaction options instead)
    me.runCallback(transaction, event, false);
    Ext.direct.Manager.removeTransaction(transaction);
    }}
    
    PossibleFix
    else {
    transactions = [].concat(options.transaction);
                       for (len = transactions.length; i < len; ++i) {
                                  var opt = me.getCallData(transactions[i]);
                        transaction = me.getTransaction(opt);
    …
    if (transaction) {
    me.runCallback(transaction, event, false);
    Ext.direct.Manager.removeTransaction(transaction);
    }
    Additional CSS used:
    • only default ext-all.css
    Operating System:
    • Windows 7
    • Mac OS X

Thread Participants: 1