Callback 'onComplete' does not fire on Chrome

Type of issue

[x] Bug report
[ ] Feature request
[ ] Support request

Uploader type

[x] Traditional
[ ] S3
[ ] Azure

When trying to fire a callback in Chrome, doesn't work, but in Mozilla Firefox it works.
Bug Report
What do I have to change to fire the callback in  Chrome.
Fine Uploader version
{example: 5.11.10}
Browsers where the bug is reproducible
{Chrome Versión 56.0.2924.87 (64-bit)}
Operating systems where the bug is reproducible
{example: "Windows 7"}
Exact steps required to reproduce the issue
For example:

Select a file
Click on a button to execute the function uploader.uploadStoredFiles()
onComplete callback save data of the file uploaded to a database.

All relevant Fine Uploader-related code that you have written
uploader = new qq.FineUploader({
  element: document.getElementById("uploader"),
  autoUpload: false,
  request: {
      endpoint: './uploads/endpoint.php'
  },
  deleteFile: {
      enabled: true,
      endpoint: './uploads/endpoint.php'
  },
  retry: {
     enableAuto: true
  },
  validation: {
    allowedExtensions: ['pdf'],
    sizeLimit: 15360000, // 5 MB = 50000 * 1024 bytes, Archivos mas grandes no son permitidos
    itemLimit: 1
  },
  callbacks: {
    onComplete:function(id, name, result, xhr){
        //uploader.reset();
        archivos = uploader.getUploads();
        //alert(JSON.stringify(archivos));
        $.ajax({
            type: "POST",
            url: "./modelo/mngr_postventa.php",
            data:{act: 'carga_docs', ent: 'general', idvivienda: data[0],archivos,tipodoc: 1},
            dataType: 'json',
            cache: false,
            error: function (xhr, ajaxOptions, thrownError) {
                alert(xhr.responseText);
                console.log(thrownError,xhr,ajaxOptions);
            }
        }).done(function (data) {
            if(data['OK']){
                $('#docs').attr('data-id_doc',data['id_doc']);
                //console.log('cyka',data['qry'],data['id_doc']);
                tk_log_documentos_propietario('docs',$('#docs').attr('data-action'));
            }
        });
      },
  },
  //multiple: false,
  showMessage: function(message) {
    alert(message);
    $('#btnupload').css('overflow','');
  }
});

in another function I store the files:
uploader.uploadStoredFiles();

Your Fine Uploader template markup (if using Fine Uploader UI and the issue is UI-related)

Detailed explanation of the problem
The fineuploader upload the file but doesn´t fire the callback "onComplete" in Chrome, it work perfectly in Firefox.

Feature Request
Feature request details
{why is this feature important, not just for you, but for many others?}

Support Request
Fine Uploader version
{example: 5.5.1}
Question
{ask your support question here & be as detailed and clear as possible}
Related code
{post any code related to your question here}

Unclear as to what the issue is exactly, or how to reproduce. Are you saying onComplete never fires in Chrome for any or the 3 completed files after following the steps in your report? If this is indeed a Chrome-only issue, perhaps there is some issue with an installed browser extension on your end?

I updated the issue, sorry for my bad explanation. Yes, the callback onComplete doesn't fire in Chrome, but in Firefox works fine.

Still unclear on the steps to reproduce. If I select 1 file and upload it in Chrome, are you saying that onComplete is not called when the upload request completes?

Yes that's the problem

Ok - please set the debug option to true and include all console logs in your description when reproducing the issue.

[Fine Uploader 5.11.10] Parsing template
util.js:236 [Fine Uploader 5.11.10] Template parsing complete
util.js:236 [Fine Uploader 5.11.10] Rendering template in DOM.
util.js:236 [Fine Uploader 5.11.10] Template rendering complete
util.js:236 [Fine Uploader 5.11.10] Received 1 files.
util.js:236 [Fine Uploader 5.11.10] Attempting to validate image.
util.js:236 [Fine Uploader 5.11.10] Generating new thumbnail for 0
util.js:236 [Fine Uploader 5.11.10] Attempting to draw client-side image preview.
util.js:236 [Fine Uploader 5.11.10] Attempting to determine if prueba.pdf can be rendered in this browser
util.js:236 [Fine Uploader 5.11.10] First pass: check type attribute of blob object.
util.js:236 [Fine Uploader 5.11.10] prueba.pdf is not previewable in this browser per the blob's type attr
util.js:236 [Fine Uploader 5.11.10] Not previewable
util.js:236 [Fine Uploader 5.11.10] Sending simple upload request for 0
util.js:236 [Fine Uploader 5.11.10] Resetting uploader...
util.js:236 [Fine Uploader 5.11.10] Resetting upload handler
util.js:236 [Fine Uploader 5.11.10] Cancelling 0
util.js:236 [Fine Uploader 5.11.10] Rendering template in DOM.
util.js:236 [Fine Uploader 5.11.10] Template rendering complete

Looks like something on your end is cancelling the upload. That would explain why onComplete is never called.

But I get from the endpoint this response {"success":true,"uuid":"documentos","uploadName":"51950.pdf"} , thats mean that the file was uploaded right?

according to the logs, the uploader is reset before the upload completes

Ok, thanks so much for the help.

sure thing. may i ask why you are calling reset at all?

I call it because I had the uploader in jquery ui-dialog modal, and every time the dialog is called I reset the uploader.


Blank window after loading icon

Operating system: Mac OS 10.12.5 Beta (16F43c)
Messenger for Desktop version: 2.0.9 stable

DEBUG [2017-04-03 23:24:45.689] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:main cli args parsed {"_":[],"os-startup":false,"osStartup":false,"portable":false,"debug":true,"console-logs":false,"consoleLogs":false,"repl":false,"mas":false,"version":false,"v":false,"squirrel-install":false,"squirrelInstall":false,"squirrel-uninstall":false,"squirrelUninstall":false,"squirrel-updated":false,"squirrelUpdated":false,"squirrel-obsolete":false,"squirrelObsolete":false,"squirrel-firstrun":false,"squirrelFirstrun":false,"help":false,"h":false,"repl-port":3499,"replPort":3499,"$0":"Applications/Messenger for Desktop.app/Contents/MacOS/Messenger for Desktop --debug"}
DEBUG [2017-04-03 23:24:45.692] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:main running in debug mode
DEBUG [2017-04-03 23:24:45.694] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:utils:prefs prefs data restored
DEBUG [2017-04-03 23:24:45.744] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:main ready
DEBUG [2017-04-03 23:24:45.745] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:main intercepting protocol http
DEBUG [2017-04-03 23:24:45.750] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:main launching app
DEBUG [2017-04-03 23:24:45.852] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:main-window-manager creating main window
DEBUG [2017-04-03 23:24:45.935] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:auto-update-manager starting auto updater
DEBUG [2017-04-03 23:24:45.935] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:auto-update-manager updater feed url: https://updates.messengerfordesktop.com/update/stable/darwin?version=2.0.9
DEBUG [2017-04-03 23:24:45.940] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:auto-update-manager scheduling update checks every 14400000 ms
DEBUG [2017-04-03 23:24:45.941] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:auto-update-manager checking for update...
DEBUG [2017-04-03 23:24:45.975] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:common:utils:files:browser dictionaries in /Applications/Messenger for Desktop.app/Contents/Resources/app.asar/dicts found: ["de","es","fr","hu","ro_RO","ru"]
DEBUG [2017-04-03 23:24:45.975] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:common:utils:files:browser dictionaries in /Applications/Messenger for Desktop.app/Contents/Resources/app.asar/node_modules/spellchecker/vendor/hunspell_dictionaries found: ["en_US"]
DEBUG [2017-04-03 23:24:45.997] Mon, 03 Apr 2017 23:24:45 GMT messengerfordesktop:browser:managers:main-menu-manager app menu created
DEBUG [2017-04-03 23:24:46.000] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:managers:main-menu-manager app menu set
DEBUG [2017-04-03 23:24:46.277] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: checking-for-update params:
DEBUG [2017-04-03 23:24:46.291] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file://<app>/html/app.html
DEBUG [2017-04-03 23:24:46.368] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file://<app>/styles/app.css
DEBUG [2017-04-03 23:24:46.368] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file://<app>/styles/loader.css
DEBUG [2017-04-03 23:24:46.368] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file://<app>/scripts/renderer/index.js
DEBUG [2017-04-03 23:24:46.398] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:renderer:webview:index loading https://www.messenger.com/login
DEBUG [2017-04-03 23:24:46.430] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:renderer:services:piwik setting up piwik
DEBUG [2017-04-03 23:24:46.517] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:renderer:components:keymap binding keyboard shortcuts
DEBUG [2017-04-03 23:24:46.543] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:renderer:webview:listeners document DOMContentLoaded
DEBUG [2017-04-03 23:24:46.550] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:managers:main-window-manager ready-to-show
DEBUG [2017-04-03 23:24:46.627] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-03 23:24:46.659] Mon, 03 Apr 2017 23:24:46 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-03 23:24:49.045] Mon, 03 Apr 2017 23:24:49 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: update-not-available params:
DEBUG [2017-04-03 23:25:10.923] Mon, 03 Apr 2017 23:25:10 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-03 23:25:23.702] Mon, 03 Apr 2017 23:25:23 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-03 23:25:24.259] Mon, 03 Apr 2017 23:25:24 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-03 23:25:24.262] Mon, 03 Apr 2017 23:25:24 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":471,"y":100,"width":920,"height":654}
DEBUG [2017-04-03 23:25:25.614] Mon, 03 Apr 2017 23:25:25 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-03 23:25:25.615] Mon, 03 Apr 2017 23:25:25 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":250,"y":152,"width":920,"height":654}
DEBUG [2017-04-03 23:25:30.632] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file://<app>/html/app.html
DEBUG [2017-04-03 23:25:30.808] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file://<app>/styles/app.css
DEBUG [2017-04-03 23:25:30.808] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file://<app>/styles/loader.css
DEBUG [2017-04-03 23:25:30.809] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file://<app>/scripts/renderer/index.js
DEBUG [2017-04-03 23:25:30.824] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file://<app>/html/app.html
DEBUG [2017-04-03 23:25:30.891] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file://<app>/styles/app.css
DEBUG [2017-04-03 23:25:30.891] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file://<app>/styles/loader.css
DEBUG [2017-04-03 23:25:30.891] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file://<app>/scripts/renderer/index.js
DEBUG [2017-04-03 23:25:30.938] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:renderer:webview:index loading https://www.messenger.com/login
DEBUG [2017-04-03 23:25:30.971] Mon, 03 Apr 2017 23:25:30 GMT messengerfordesktop:renderer:services:piwik setting up piwik
DEBUG [2017-04-03 23:25:31.057] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:components:keymap binding keyboard shortcuts
DEBUG [2017-04-03 23:25:31.067] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:webview:listeners document DOMContentLoaded
DEBUG [2017-04-03 23:25:31.201] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file://<app>/html/app.html
DEBUG [2017-04-03 23:25:31.273] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file://<app>/styles/app.css
DEBUG [2017-04-03 23:25:31.273] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file://<app>/styles/loader.css
DEBUG [2017-04-03 23:25:31.275] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file://<app>/scripts/renderer/index.js
DEBUG [2017-04-03 23:25:31.331] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:webview:index loading https://www.messenger.com/login
DEBUG [2017-04-03 23:25:31.360] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:services:piwik setting up piwik
DEBUG [2017-04-03 23:25:31.452] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:components:keymap binding keyboard shortcuts
DEBUG [2017-04-03 23:25:31.462] Mon, 03 Apr 2017 23:25:31 GMT messengerfordesktop:renderer:webview:listeners document DOMContentLoaded
DEBUG [2017-04-03 23:25:43.003] Mon, 03 Apr 2017 23:25:43 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-03 23:25:58.066] Mon, 03 Apr 2017 23:25:58 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-03 23:25:59.172] Mon, 03 Apr 2017 23:25:59 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-03 23:26:30.965] Mon, 03 Apr 2017 23:26:30 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-03 23:26:34.560] Mon, 03 Apr 2017 23:26:34 GMT messengerfordesktop:browser:menus:expressions:expr-click opening log file with default app /Users/Jim/Library/Application Support/Messenger for Desktop/logs/1491261885690.txt
DEBUG [2017-04-03 23:26:34.684] Mon, 03 Apr 2017 23:26:34 GMT messengerfordesktop:browser:managers:main-window-manager onBlur

I'm having the same issue.

DEBUG [2017-04-05 02:28:36.489] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:main cli args parsed {"_":[],"os-startup":false,"osStartup":false,"portable":false,"debug":true,"console-logs":false,"consoleLogs":false,"repl":false,"mas":false,"version":false,"v":false,"squirrel-install":false,"squirrelInstall":false,"squirrel-uninstall":false,"squirrelUninstall":false,"squirrel-updated":false,"squirrelUpdated":false,"squirrel-obsolete":false,"squirrelObsolete":false,"squirrel-firstrun":false,"squirrelFirstrun":false,"help":false,"h":false,"repl-port":3499,"replPort":3499,"$0":"Applications/Messenger for Desktop.app/Contents/MacOS/Messenger for Desktop --debug"}
DEBUG [2017-04-05 02:28:36.493] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:main running in debug mode
DEBUG [2017-04-05 02:28:36.494] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:utils:prefs prefs data restored
DEBUG [2017-04-05 02:28:36.554] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:main ready
DEBUG [2017-04-05 02:28:36.555] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:main intercepting protocol http
DEBUG [2017-04-05 02:28:36.561] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:main launching app
DEBUG [2017-04-05 02:28:36.679] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:main-window-manager creating main window
DEBUG [2017-04-05 02:28:36.764] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:auto-update-manager starting auto updater
DEBUG [2017-04-05 02:28:36.765] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:auto-update-manager updater feed url: https://updates.messengerfordesktop.com/update/stable/darwin?version=2.0.9
DEBUG [2017-04-05 02:28:36.770] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:auto-update-manager scheduling update checks every 14400000 ms
DEBUG [2017-04-05 02:28:36.771] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:auto-update-manager checking for update...
DEBUG [2017-04-05 02:28:36.810] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:common:utils:files:browser dictionaries in /Applications/Messenger for Desktop.app/Contents/Resources/app.asar/dicts found: ["de","es","fr","hu","ro_RO","ru"]
DEBUG [2017-04-05 02:28:36.810] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:common:utils:files:browser dictionaries in /Applications/Messenger for Desktop.app/Contents/Resources/app.asar/node_modules/spellchecker/vendor/hunspell_dictionaries found: ["en_US"]
DEBUG [2017-04-05 02:28:36.838] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:main-menu-manager app menu created
DEBUG [2017-04-05 02:28:36.841] Wed, 05 Apr 2017 02:28:36 GMT messengerfordesktop:browser:managers:main-menu-manager app menu set
DEBUG [2017-04-05 02:28:37.181] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: checking-for-update params:
DEBUG [2017-04-05 02:28:37.195] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file:///html/app.html
DEBUG [2017-04-05 02:28:37.281] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file:///styles/app.css
DEBUG [2017-04-05 02:28:37.282] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file:///styles/loader.css
DEBUG [2017-04-05 02:28:37.282] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file:///scripts/renderer/index.js
DEBUG [2017-04-05 02:28:37.317] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:renderer:webview:index loading https://www.messenger.com/login
DEBUG [2017-04-05 02:28:37.355] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:renderer:services:piwik setting up piwik
DEBUG [2017-04-05 02:28:37.459] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:renderer:components:keymap binding keyboard shortcuts
DEBUG [2017-04-05 02:28:37.519] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:renderer:webview:listeners document DOMContentLoaded
DEBUG [2017-04-05 02:28:37.537] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:managers:main-window-manager ready-to-show
DEBUG [2017-04-05 02:28:37.626] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-05 02:28:37.650] Wed, 05 Apr 2017 02:28:37 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-05 02:28:38.939] Wed, 05 Apr 2017 02:28:38 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-05 02:28:38.945] Wed, 05 Apr 2017 02:28:38 GMT messengerfordesktop:browser:managers:main-window-manager onHide
DEBUG [2017-04-05 02:28:39.455] Wed, 05 Apr 2017 02:28:39 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: update-not-available params:
DEBUG [2017-04-05 02:29:17.869] Wed, 05 Apr 2017 02:29:17 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-05 02:29:17.887] Wed, 05 Apr 2017 02:29:17 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-05 02:29:18.836] Wed, 05 Apr 2017 02:29:18 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-05 02:29:18.887] Wed, 05 Apr 2017 02:29:18 GMT messengerfordesktop:browser:managers:main-window-manager onHide
DEBUG [2017-04-05 02:30:10.054] Wed, 05 Apr 2017 02:30:10 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-05 02:30:10.073] Wed, 05 Apr 2017 02:30:10 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-05 02:30:11.745] Wed, 05 Apr 2017 02:30:11 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-05 02:30:11.795] Wed, 05 Apr 2017 02:30:11 GMT messengerfordesktop:browser:managers:main-window-manager onHide
DEBUG [2017-04-05 02:30:12.324] Wed, 05 Apr 2017 02:30:12 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-05 02:30:12.341] Wed, 05 Apr 2017 02:30:12 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-05 02:30:13.784] Wed, 05 Apr 2017 02:30:13 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-05 02:30:13.787] Wed, 05 Apr 2017 02:30:13 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":260,"y":88,"width":920,"height":610}
DEBUG [2017-04-05 02:30:22.250] Wed, 05 Apr 2017 02:30:22 GMT messengerfordesktop:browser:managers:auto-update-manager checking for update...
DEBUG [2017-04-05 02:30:22.361] Wed, 05 Apr 2017 02:30:22 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: checking-for-update params:
DEBUG [2017-04-05 02:30:24.013] Wed, 05 Apr 2017 02:30:24 GMT messengerfordesktop:browser:menus:expressions:expr-click opening log file with default app /Users/zomars/Library/Application Support/Messenger for Desktop/logs/1491359316490.txt
DEBUG [2017-04-05 02:30:24.119] Wed, 05 Apr 2017 02:30:24 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-05 02:30:24.125] Wed, 05 Apr 2017 02:30:24 GMT messengerfordesktop:browser:managers:main-window-manager onHide
DEBUG [2017-04-05 02:30:24.587] Wed, 05 Apr 2017 02:30:24 GMT messengerfordesktop:browser:managers:main-menu-manager auto updater on: update-not-available params:
DEBUG [2017-04-05 02:30:24.588] Wed, 05 Apr 2017 02:30:24 GMT messengerfordesktop:browser:managers:auto-update-manager onCheckUpdateNotAvailable
DEBUG [2017-04-05 02:30:35.132] Wed, 05 Apr 2017 02:30:35 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-05 02:30:35.175] Wed, 05 Apr 2017 02:30:35 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-05 02:30:37.445] Wed, 05 Apr 2017 02:30:37 GMT messengerfordesktop:browser:managers:main-window-manager onBlur

I'm having a similar issue, albeit somewhat different.
The loading animation disappeared in a few seconds after app launch, leaving user with a blank page.
However, if you wait long enough (in my case 5 minutes), the app would finish loading and function as normal.
Version: 2.0.9 stable
OS: Windows 7 Professional SP1
Log messages: (the app finish loading at 03:13:50
DEBUG [2017-04-06 03:08:48.357] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main cli args parsed {"_":[],"os-startup":false,"osStartup":false,"portable":false,"debug":true,"console-logs":false,"consoleLogs":false,"repl":false,"mas":false,"version":false,"v":false,"squirrel-install":false,"squirrelInstall":false,"squirrel-uninstall":false,"squirrelUninstall":false,"squirrel-updated":false,"squirrelUpdated":false,"squirrel-obsolete":false,"squirrelObsolete":false,"squirrel-firstrun":false,"squirrelFirstrun":false,"help":false,"h":false,"repl-port":3499,"replPort":3499,"$0":"Messenger for Desktop.exe --debug"}
DEBUG [2017-04-06 03:08:48.363] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main running in debug mode
DEBUG [2017-04-06 03:08:48.467] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:utils:prefs prefs data restored
DEBUG [2017-04-06 03:08:48.495] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main ready
DEBUG [2017-04-06 03:08:48.496] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main intercepting protocol http
DEBUG [2017-04-06 03:08:48.504] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main launching app
DEBUG [2017-04-06 03:08:48.610] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:managers:main-window-manager creating main window
DEBUG [2017-04-06 03:08:48.682] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:common:utils:files:browser dictionaries in C:\Users\leebooker\AppData\Local\messengerfordesktop\app-2.0.9\resources\app.asar\dicts found: ["de","es","fr","hu","ro_RO","ru"]
DEBUG [2017-04-06 03:08:48.683] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:common:utils:files:browser dictionaries in C:\Users\leebooker\AppData\Local\messengerfordesktop\app-2.0.9\resources\app.asar\node_modules\spellchecker\vendor\hunspell_dictionaries found: ["en_US"]
DEBUG [2017-04-06 03:08:48.726] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:managers:main-menu-manager app menu created
DEBUG [2017-04-06 03:08:48.735] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:managers:main-menu-manager app menu set
DEBUG [2017-04-06 03:08:48.771] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:managers:tray-manager tray menu created
DEBUG [2017-04-06 03:08:48.778] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:utils:prefs saved window-full-screen = false
DEBUG [2017-04-06 03:08:48.814] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/html/app.html => file://<app>/html/app.html
DEBUG [2017-04-06 03:08:48.976] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/app.css => file://<app>/styles/app.css
DEBUG [2017-04-06 03:08:48.976] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/styles/loader.css => file://<app>/styles/loader.css
DEBUG [2017-04-06 03:08:48.976] Thu, 06 Apr 2017 03:08:48 GMT messengerfordesktop:browser:main intercepted http GET http://app.messengerfordesktop.com/scripts/renderer/index.js => file://<app>/scripts/renderer/index.js
DEBUG [2017-04-06 03:08:49.053] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:renderer:webview:index loading https://www.messenger.com/login
DEBUG [2017-04-06 03:08:49.142] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:renderer:services:piwik setting up piwik
DEBUG [2017-04-06 03:08:49.231] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-06 03:08:49.237] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":90,"y":205,"width":952,"height":725}
DEBUG [2017-04-06 03:08:49.408] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:renderer:components:keymap binding keyboard shortcuts
DEBUG [2017-04-06 03:08:49.435] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:renderer:webview:listeners document DOMContentLoaded
DEBUG [2017-04-06 03:08:49.439] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:managers:main-window-manager ready-to-show
DEBUG [2017-04-06 03:08:49.447] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:managers:main-window-manager onShow
DEBUG [2017-04-06 03:08:49.450] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:08:49.947] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-06 03:08:49.949] Thu, 06 Apr 2017 03:08:49 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":90,"y":205,"width":952,"height":725}
DEBUG [2017-04-06 03:09:06.960] Thu, 06 Apr 2017 03:09:06 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:09:54.552] Thu, 06 Apr 2017 03:09:54 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:09:55.908] Thu, 06 Apr 2017 03:09:55 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:10:15.572] Thu, 06 Apr 2017 03:10:15 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:10:17.751] Thu, 06 Apr 2017 03:10:17 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:10:47.736] Thu, 06 Apr 2017 03:10:47 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:10:48.360] Thu, 06 Apr 2017 03:10:48 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:11:14.300] Thu, 06 Apr 2017 03:11:14 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:11:16.221] Thu, 06 Apr 2017 03:11:16 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:11:25.579] Thu, 06 Apr 2017 03:11:25 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:11:29.309] Thu, 06 Apr 2017 03:11:29 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-06 03:11:29.318] Thu, 06 Apr 2017 03:11:29 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":1979,"y":513,"width":952,"height":725}
DEBUG [2017-04-06 03:11:30.927] Thu, 06 Apr 2017 03:11:30 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:11:32.265] Thu, 06 Apr 2017 03:11:32 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:11:33.181] Thu, 06 Apr 2017 03:11:33 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:12:27.627] Thu, 06 Apr 2017 03:12:27 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:12:28.981] Thu, 06 Apr 2017 03:12:28 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:13:48.259] Thu, 06 Apr 2017 03:13:48 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:13:49.863] Thu, 06 Apr 2017 03:13:49 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:13:50.610] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:services:piwik piwik analytics instance created
DEBUG [2017-04-06 03:13:50.702] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:preload:notification extending HTML5 Notification
DEBUG [2017-04-06 03:13:50.719] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:webview:listeners webview page-title-updated
DEBUG [2017-04-06 03:13:50.730] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:webview:listeners notifying window of notif-count  null
DEBUG [2017-04-06 03:13:50.945] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:webview:listeners webview dom-ready
DEBUG [2017-04-06 03:13:50.949] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:webview:listeners restoring theme default
DEBUG [2017-04-06 03:13:50.952] Thu, 06 Apr 2017 03:13:50 GMT messengerfordesktop:renderer:webview:listeners restoring webview css override default
DEBUG [2017-04-06 03:13:51.660] Thu, 06 Apr 2017 03:13:51 GMT messengerfordesktop:renderer:webview:listeners webview did-finish-load
DEBUG [2017-04-06 03:14:11.181] Thu, 06 Apr 2017 03:14:11 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:14:19.839] Thu, 06 Apr 2017 03:14:19 GMT messengerfordesktop:renderer:preload:notification extending HTML5 Notification
DEBUG [2017-04-06 03:14:19.849] Thu, 06 Apr 2017 03:14:19 GMT messengerfordesktop:renderer:webview:listeners webview page-title-updated
DEBUG [2017-04-06 03:14:19.850] Thu, 06 Apr 2017 03:14:19 GMT messengerfordesktop:renderer:webview:listeners notifying window of notif-count  null
DEBUG [2017-04-06 03:14:20.268] Thu, 06 Apr 2017 03:14:20 GMT messengerfordesktop:renderer:webview:listeners webview dom-ready
DEBUG [2017-04-06 03:14:20.269] Thu, 06 Apr 2017 03:14:20 GMT messengerfordesktop:renderer:webview:listeners restoring theme default
DEBUG [2017-04-06 03:14:20.270] Thu, 06 Apr 2017 03:14:20 GMT messengerfordesktop:renderer:webview:listeners restoring webview css override default
DEBUG [2017-04-06 03:14:23.345] Thu, 06 Apr 2017 03:14:23 GMT messengerfordesktop:renderer:webview:listeners webview did-finish-load
DEBUG [2017-04-06 03:14:23.622] Thu, 06 Apr 2017 03:14:23 GMT messengerfordesktop:browser:managers:main-window-manager saving bounds
DEBUG [2017-04-06 03:14:23.629] Thu, 06 Apr 2017 03:14:23 GMT messengerfordesktop:browser:utils:prefs saved window-bounds = {"x":196,"y":220,"width":952,"height":725}
DEBUG [2017-04-06 03:14:26.997] Thu, 06 Apr 2017 03:14:26 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:15:03.156] Thu, 06 Apr 2017 03:15:03 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:15:04.983] Thu, 06 Apr 2017 03:15:04 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:21:00.175] Thu, 06 Apr 2017 03:21:00 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:21:01.393] Thu, 06 Apr 2017 03:21:01 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:21:45.312] Thu, 06 Apr 2017 03:21:45 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:21:49.768] Thu, 06 Apr 2017 03:21:49 GMT messengerfordesktop:browser:managers:main-window-manager onBlur
DEBUG [2017-04-06 03:21:52.020] Thu, 06 Apr 2017 03:21:52 GMT messengerfordesktop:browser:managers:main-window-manager onFocus
DEBUG [2017-04-06 03:22:02.988] Thu, 06 Apr 2017 03:22:02 GMT messengerfordesktop:browser:managers:app-listeners-manager before quit
DEBUG [2017-04-06 03:22:02.988] Thu, 06 Apr 2017 03:22:02 GMT messengerfordesktop:browser:managers:main-window-manager onClose forceClose=true
DEBUG [2017-04-06 03:22:02.993] Thu, 06 Apr 2017 03:22:02 GMT messengerfordesktop:browser:managers:app-listeners-manager will quit
process exited with code 0

Yes, after a long time it will finish the blank screen and function as normal.


Fixed inconsistency in tutorial runserver command

In the Hello World tutorial for Django, fixed an inconsistency in Step 17 where the instructions said to use 'python' to run the server, not 'python3' like the rest of the tutorial.

Great catch. Thanks again @misczak


feat: Support generating data for Open API request payloads with wildcard media types

Resolves #1526

Codecov Report

Merging #1527 (3548f33) into master (1b0cd65) will decrease coverage by 0.27%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1527      +/-   ##
==========================================
- Coverage   98.93%   98.66%   -0.28%
==========================================
  Files          91       91
  Lines        7057     7017      -40
  Branches     1248     1220      -28
==========================================
- Hits         6982     6923      -59
- Misses         47       58      +11
- Partials       28       36       +8

Impacted Files
Coverage Δ

src/schemathesis/exceptions.py
100.00% <100.00%> (ø)

src/schemathesis/models.py
99.08% <100.00%> (-0.02%)
:arrow_down:

src/schemathesis/serializers.py
98.36% <100.00%> (+0.07%)
:arrow_up:

src/schemathesis/specs/openapi/_hypothesis.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/validation.py
76.47% <0.00%> (-11.77%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
95.58% <0.00%> (-4.42%)
:arrow_down:

src/schemathesis/runner/impl/threadpool.py
98.23% <0.00%> (-1.77%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.62% <0.00%> (-1.38%)
:arrow_down:

src/schemathesis/specs/openapi/loaders.py
98.31% <0.00%> (-0.85%)
:arrow_down:

...c/schemathesis/specs/openapi/negative/mutations.py
98.75% <0.00%> (-0.84%)
:arrow_down:

... and 23 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b0cd65...3548f33. Read the comment docs.


Version 0.2.0

Please create a release for version 0.2.0.
TA-aurora-0.2.0.tar.gz

The new version was released on 27.09


Fixed workflow detail page UX bugs

Description

Reduced padding between panels
Added border radius to the panels
Decreased empty space at the bottom below panels.
Fixed header as previous workflow title is some part cut at the top.
Removed unwanted margins present for panels in  workflow detail page

screen-capture (25).webm
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ohltyler, please take a look.
@kamingleung, please take a look at the screen recorder above and track any more bugs observed in the UX for both Old and New look. Thank you.

Failing test will be fixed with https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/1612

@saimedhi this is great! One question, I see the overall margins on the edge of the window is different on the workflow list and the workflow details page - should these be consistent?
screen-capture (13).webm

@saimedhi this is great! One question, I see the overall margins on the edge of the window is different on the workflow list and the workflow details page - should these be consistent?
screen-capture.13.webm

Yes, Tyler I notice that too. But in workflow detail Page, UX team suggested to have Same Appearance as discover page.(less padding around panels). I will reconnect with UX today and show both New Look and Old look and request them to track if any further changes needed.

@ohltyler The visual designer is considered a "full-screen" application, similar to Discover. Therefore, UX would recommend follow the same spacing pattern as the new Discover to maximize workable space.

@saimedhi

Looks like the Preview and Inspector panels have width padding inside the panels. Can you make sure they are consistent with the left panel?


Alternatives for asyncio.create_subprocess_exec method for nuitka.

Nuitka Version
1.3rc9
Commercial: None
Python: 3.8.8 (tags/v3.8.8:024d805, Feb 19 2021, 13:18:16) [MSC v.1928 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Soultion-Applications\d-test\.venv\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30037\bin\HostX64\x64\cl.exe (cl 14.2).

Packages
Nuitka==1.3rc9
orderedset==2.0.3

Nutika command used
python -m nuitka --standalone main.py

main.py
import asyncio
import sys
from pathlib import Path

async def main():
    this_source_file = Path(__file__)
    main_dir = this_source_file.parent
    runner_main_file = main_dir / "subproc.py"
    if not runner_main_file.is_file():
        raise RuntimeError(
            "Unable to find the file./n"
            f"Expecting to find '{runner_main_file}'."
        )
    args = [str(runner_main_file)]

    process = await asyncio.create_subprocess_exec(
        sys.executable,
        *args,
        stdout=asyncio.subprocess.PIPE,
        stderr=asyncio.subprocess.PIPE,
    )

    stdout, stderr = await process.communicate()

    print(f'[{process.returncode}]')
    if stdout:
        print(f'[stdout] {stdout.decode()}')
    if stderr:
        print(f'[stderr] {stderr.decode()}')

asyncio.run(main())

subproc.py
import time

time.sleep(3)
print('Hello from subproc.py after 3 seconds')

Issue

Is there a way to run whatever is inside subproc.py without having to create a subproc.exe and then calling it? subproc.py has circular dependency on some methods inside modules which calls main.py. So this option cannot be used.
subproc.py should also be obfuscated. So cannot have subproc.py in the dist.

You will have to wait for the so called multidist feature, which is on the roadmap. It will allow combining arbitrarily many programs into a single binary.

Multidist has been implemented and release with I think 1.4 already. Give it a shot.


RuntimeException when performing nested calls

We have an issue where Peer.remove or Peer.put throw a RuntimeExceptions if performing nested calls.
java.lang.RuntimeException: cannot block here
	at net.tomp2p.connection.ConnectionReservation.reserve(ConnectionReservation.java:104)
	at net.tomp2p.connection.ConnectionReservation.reserve(ConnectionReservation.java:83)
	at net.tomp2p.p2p.Peer.remove(Peer.java:1321)
	at net.tomp2p.p2p.Peer.remove(Peer.java:1295)

I am creating a pull request for a test case which illustrates the issue.

If I comment out the following block in ConnectionReservation the test passes:
19b40b3bf2bf2e867e542072677b618e2f4fcfba
Note, you might find it helpful to include the thread name your RuntimeException message.

I modified the testcase in order to make the nested calls work. The RuntimeException is required because the reservation is a blocking call and if this is nested called, it might deadlock in a Netty I/O operation (http://docs.jboss.org/netty/3.2/api/org/jboss/netty/channel/ChannelFuture.html). Reservations are necessary because with no reservations you run into "too many open files in system".


Do not compiling source code it self when incorporates other build processes like Gralde, Maven.

I like the format of gauge specification.
But when I try to implement my step using Geb. I found that Gauge Java try to do everything by it self. From source code compiling to spec executing...
Gauge provides Gralde and Maven plugins. However, they all looks like gauge executable invokers. And will not use all existing and de-facto build process. Reflections works on class files, but I just cannot use the Step implementation compiled by Gradle / Maven, because of my source code is not ending with .java? :hushed:
Rename gauge-java to gauge-jvm just like https://github.com/cucumber/cucumber-jvm maybe a good start?

@tan9
Glad to know that you like Gauge spec format.
We haven't tried using Gauge with Geb. But, you can refer our Gauge example project with Groovy support.
If you want to direct Gauge to use already existing class files, you can set custom build path in env/default/java.properties. This will not re-compile your source files.
# Use the below property if you need to override the build path
gauge_custom_build_path = <path>

@apoorvam
Thank you for the groovy example, I will try it out later this week.

@tan9 Do you get time to try out the groovy example?

@mahendrakariya , sorry, we later change to development our product using front-end technologies, and adopt the test tools in the box from https://github.com/AngularClass/angular2-webpack-starter .

Cool. I will close the issue.


[Bug]: Validation Error if @URL is required for the NeXus definition

Contact Details
@RonHildebrandt
What happened?
This was found for NXraman here
Thats, as far as I know, the only NeXus defnition, which has @url required as attribute.
Though, this is written attribute is written automatically written afterwards. At some point, the check is done before this automatic writing of the @URL attribute for the definition.
This results in a warning, which is bad for CI/CD or similar.
Relevant log output
(.py39) ron@hlp135:~/2_pynxtools/2_make_multiformat_raman_reader/pynxtools-raman/src/pynxtools_raman_multiformat$ dataconverter eln_data.yaml Si-wafer-Raman-Spectrum-1.txt config_file.json --reader raman_multi --nxdl NXraman --output output_raman.nxs
Using raman_multi reader to convert the given files:
• eln_data.yaml
• Si-wafer-Raman-Spectrum-1.txt
• config_file.json
Config file already set. Replaced by the new file config_file.json.
Config file already set. Replaced by the new file config_file.json.
WARNING: Missing attribute: "/ENTRY[entry]/definition/@URL"
The output file generated: output_raman.nxs.

I think this is related to the uppercase nature of @URL. In NXentry, that should be set to have nameType="specified" to indicate that it always has to be URL and not be namefitted.
The problem comes here where it checks that URL is not already a direct child and it fails because we try to namefit URL with uppercase URL and this is not allowed.
So the solution is to change the nameType of  definition/@URL in NXentry and eventuall in NXoptical_spectroscopy to nameType="specified". I added to the respective issue in the NIAC repo here.


Incorrect display of sample data in the JSON area for test creation

The following sentence is followed by a code box with sample code for integrating the test toolkit into the extension project.
Import symbols for the Test framework.
We do this by adding a test setting to the app.json file with the minimum supported value, for example: "test" : "<IP_ADDRESS>".
The text in the box starts as follows:
Machine generated alternative text:
However, this example cannot be used because it is gibberish. Something's completely broken. It's not possible to use anything else here. Please correct accordingly.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bc7f2151-4fef-e6ab-bbc1-5b3e1b8c5b17
Version Independent ID: 20ffa998-58d3-c843-87d5-3533e2fa7765
Content: Testing the Advanced Sample Extension - Business Central
Content Source: dev-itpro/developer/devenv-extension-advanced-example-test.md
Service: dynamics365-business-central
GitHub Login: @solsen
Microsoft Alias: SusanneWindfeldPedersen

Thanks for the feedback. You're right - this text was broken unfortunately. The topic is fixed with the next refresh of the docs. The machine generated alternative text looks like this:
"screenshots": [],
"platform": "<IP_ADDRESS>",
"application": "<IP_ADDRESS>",
"test": "<IP_ADDRESS>",
"idRange": {
"from": 50100,
"to": 50149}
Thanks again!


provision: Add cd /srv/zulip to profile.

I didn't bump the provision version on this change, as it
won't break anything if somebody fails to make this change.

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, after fixing the missing mypy annotation on the new function, thanks @showell!


Are there any future plans to migrate hystrix from java 6 to java 8 (sourceCompatibility) ?

I have seen that hystrix uses JDK 6 platform. Are there any plans to change the platform to JDK 8
and there by updating all other old dependencies like updating servlet-api from 2.5 to 3.0 and many others like these?

jdk 8 and the servlet api aren't related are they?

Sorry for my vague question.
I see that the jetty implementation of servlet api 3.1 are build for java 7 or higher and we use jetty 9. And so I thought that we could not use it for java 6.
But as the travis build uses jdk 8, I don't think there would be an issue. But I think as the gradle checks for source compatibility of java 6, we would not be able to use java 8 features like lambdas or stream. Or could we?
My actual intension of the question is:
I see we are using web.xml in web apps. If we could change the servlet specs to 3.1 or more than we can use annotations on top of servlet classes or filter classes instead of these configuration files. I wanted to implement these. Can I do that?
Thanks!

There was a decent amount of pushback from Hystrix users in updating from JDK 1.6 -> 1.8 within the Hystrix 1 series.
As far as Servlet 3.1 goes, what specific bits of Hystrix relate to servlets?


One key AES encryption added

Messages are encrypted and decrypted via secret_key provided by userinfo.json or default key.
Features:

Encryption/Decryption exclusively on the client side.
Uses salting to protect from Rainbow Table Attacks

Another future upgrade options

End-to-end encryption: Much harder to implement

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

the secret.key needs to be placed on server or client side ? sorry for the dumb question

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

the secret.key needs to be placed on server or client side ? sorry for the dumb question

It will be in the client side.
Currently it is working like this:

Client tries to get the secretkey from userinfo.json,
If it fails or the userinfo doesn't have the key, then it will load the default key from client/security.py line 7

So if you don't want to customize it, you can safely remove from userinfo.json, but either way, everything i added is exclusively on client side.

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

the secret.key needs to be placed on server or client side ? sorry for the dumb question

It will be in the client side.
Currently it is working like this:
* Client tries to get the secretkey from **userinfo.json**,

* If it fails or the userinfo doesn't have the key, then it will load the default key from **client/security.py line 7**

So if you don't want to customize it, you can safely remove from userinfo.json, but either way, everything i added is exclusively on client side.

alright that works , one last question is that every user having different secret.key would effect the encryption right ?

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

the secret.key needs to be placed on server or client side ? sorry for the dumb question

It will be in the client side.
Currently it is working like this:
* Client tries to get the secretkey from **userinfo.json**,

* If it fails or the userinfo doesn't have the key, then it will load the default key from **client/security.py line 7**

So if you don't want to customize it, you can safely remove from userinfo.json, but either way, everything i added is exclusively on client side.

alright that works , one last question is that every user having different secret.key would effect the encryption right ?

Yes, the user can only read the messages that were encrypted with the same key that is currently used.
If a group needs to communicate each other, then all member need to have the same secret key.
Also if you need anything else to make this PR easier to be integrated to the app, let me know, and i update it.

If you need to generate your own secret key, you can use the following example:
from client.security import aes_to_base64,  generate_aes_key

print(aes_to_base64(generate_aes_key()))

the secret.key needs to be placed on server or client side ? sorry for the dumb question

It will be in the client side.
Currently it is working like this:
* Client tries to get the secretkey from **userinfo.json**,

* If it fails or the userinfo doesn't have the key, then it will load the default key from **client/security.py line 7**

So if you don't want to customize it, you can safely remove from userinfo.json, but either way, everything i added is exclusively on client side.

alright that works , one last question is that every user having different secret.key would effect the encryption right ?

Yes, the user can only read the messages that were encrypted with the same key that is currently used.
If a group needs to communicate each other, then all member need to have the same secret key.
Also if you need anything else to make this PR easier to be integrated to the app, let me know, and i update it.

Sure i will make a separate issue for it. Thanks for the PR, will merge as soon as i test it

@Reterics 'MAC check failed`
steps to reproduce:

run server at one place and copy paste client and change userinfo ( usernames of all three and secret key of only one )
error pops up
change it back to correct secret key
cant send messages anymore , no one is able to
also unable to create new room on reopening client if one user on server has altered and then restored to original secret key

possible fixes : display error with bad security key to the person at fault when joining the room and let other users keep chatting
it works great when the same copy is ran without any changes ( only  username change )

It is not the best solution, but i made the following:
If the client fails to decrypt one or more message, it sends the information to the server, and the server stores it in an error list.
When we request the message list, we will receive the error list as well, so we will know if someone could not decrypt our message.

It is not the best solution, but i made the following:
If the client fails to decrypt one or more message, it sends the information to the server, and the server stores it in an error list.
When we request the message list, we will receive the error list as well, so we will know if someone could not decrypt our message.

looks good , will test and merge if no issues

@Reterics when the server is stopped in between and restarted , the cient is unable to send messages , and also on restarting client, rooms are not visible and not being able to create new ones too
everything is working fine before server restart tho

I added a reconnection config to the socketio.Client along with error handling. and restarted both client and server several times, it seems to be working.
SocketIO config:
sio = socketio.Client(reconnection=True, reconnection_attempts=5, reconnection_delay=2)
For this I needed to move user_list and message_list polling into the on_connect function.
Client side logs:

Can you make a try with this update?

I added a reconnection config to the socketio.Client along with error handling. and restarted both client and server several times, it seems to be working.
SocketIO config:
sio = socketio.Client(reconnection=True, reconnection_attempts=5, reconnection_delay=2)
For this I needed to move user_list and message_list polling into the on_connect function.
Client side logs:

Can you make a try with this update?

Will check and report , might take time as I don't have my laptop today

I added a reconnection config to the socketio.Client along with error handling. and restarted both client and server several times, it seems to be working.
SocketIO config:
sio = socketio.Client(reconnection=True, reconnection_attempts=5, reconnection_delay=2)
For this I needed to move user_list and message_list polling into the on_connect function.
Client side logs:

Can you make a try with this update?

Will check and report , might take time as I don't have my laptop today

It's okay, let me know if you need anything else.

I added a reconnection config to the socketio.Client along with error handling. and restarted both client and server several times, it seems to be working.
SocketIO config:
sio = socketio.Client(reconnection=True, reconnection_attempts=5, reconnection_delay=2)
For this I needed to move user_list and message_list polling into the on_connect function.
Client side logs:

Can you make a try with this update?

Will check and report , might take time as I don't have my laptop today

It's okay, let me know if you need anything else.

ok i tested it and its unable to create rooms , could you look into it

@Reterics the rooms are being added to the json file but the client isn't showing them

@Reterics the rooms are being added to the json file but the client isn't showing them

I added 2 new rooms while i kept open the client. First one empty, second one is assigned a user. The updating and communication is working on start and restart.

Since the room handling functionality is not changed in this PR, I verified this with origin/main branch, and it works the same.
The current behavior is expected or it has the bug by default and we need to show all of the rooms regardless of the current user being in any of them?

shows all rooms right now , select rooms and search implemented in future

I uploaded the changes, you should se all the rooms

I uploaded the changes, you should see all the rooms

will check and let you know

works perfect now, thanks for the PR. Also do look out for future issues if you would like to contribute more.
Happy coding and thanks for answering my questions and taking out the time to fix the code continously

works perfect now, thanks for the PR. Also do look out for future issues if you would like to contribute more.
Happy coding and thanks for answering my questions and taking out the time to fix the code continously

Thank you, anytime! I'm glad it works, and I may check other issues as well in the future.
Happy coding for you too


File not found

The zip referenced in data-science-on-gcp/10_realtime/install_quickstart.sh does not exist (403 error)

Found it at https://github.com/GoogleCloudPlatform/cloud-bigtable-examples/blob/master/quickstart/quickstart.sh

thanks, updated


Added RedisAccessPolicies and RedisAccessPolicyAssignment resources

Description of your changes
Fixes #700
I have:

[X] Read and followed Crossplane's [contribution process].
[X] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested
Setup kind with the new resources
make run
Create the resources manualy
Crossplane successfully created the resources in Azure, and status is good
knutejoh@:~/code/provider-upjet-azure$ kubectl get rediscacheaccesspolicyassignment.cache.azure.upbound.io/example
NAME      SYNCED   READY   EXTERNAL-NAME   AGE
example   True     True    example         107s
knutejoh@:~/code/provider-upjet-azure$ kubectl get rediscacheaccesspolicy.cache.azure.upbound.io/examplepolicy
NAME            SYNCED   READY   EXTERNAL-NAME   AGE
examplepolicy   True     True    examplepolicy   8m17s

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicy.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

@knutejoh e2e tests is still in a update loop, however the problems related to external name seems to be resolved.
This time, the diff is only on the permissions.
The manifest  specifies permissions: +@read +@connection +cluster|info but the current state at the azure API seems to be permissions: +@read +@connection +cluster|info allkeys. The update calls seem to be successful without errors, but seem to have no effect, as the next cycle detects the same diff.
I don't know how this particular Azure API is working internally, but I suggest to check whether permissions have some kind of defaulting/mutation at the Azure API side, or some external entity managing it.
There is either a race, or the updates are rejected/is no-op without an error. Also, maybe try to run the e2e's one by one, waiting for one to finish.

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

@erhancagirici I've updated the examples to match the automatically added "allkeys" value, but now it looks like the test either fails or times out when deleting the RedisCache. i see that the original RedisCache tests has the manual-intervention label on them, but it refers to an issue which I can't find anymore,
upjet.upbound.io/manual-intervention: "https://github.com/upbound/official-providers/issues/625"
Perhaps I should just add this to my tests as well?

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

Not sure how to proceed here. Any input @erhancagirici @ulucinar @sergenyalcin @turkenf ?

@knutejoh seems like the e2e's are actually running fine. Creations succeed, and deletions are initiated correctly. However, I can see that the deletions for the Caches are stuck at the Azure side, all are in "Deleting" state in the console.
Could not see any meaningful log or error message at the Azure. Could be a bug on azure side. I am not an Azure expert, so I am unable to debug further on Azure side.
@knutejoh Were you able to delete the RedisCaches too, when you were doing local testing? I wonder whether the "access policies" you introduced somehow prevent deletion?

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicy.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicy.yaml"

/test-examples="examples/cache/v1beta1/rediscacheaccesspolicyassignment.yaml"


Porting examples for Advanced Data

Actual Behaviour
There is only one example under Advanced Data

Expected Behaviour
Port other examples from the processing website.

Would you like to work on the issue?
Yes.

Can I work on transferring the "Array List Class" example?

Not all Processing examples make sense in p5.js because Processing (Java) and Javascript are very different languages. We don't aim to port every single examples from Processing to Javascript mainly for this reason.
Array List and Int List would not make sense in Javascript as they would just be regular arrays. Load Save Table should still be possible though.

Do I need to make a separate issue if I want to try transferring Load Save Table?

@sm7515 No need to open another issue, I'll assign this one to you for adding Load Save Table.

Hi, I have finished adding this example but I don't have permission to push the changes.

@sm7515 You should be pushing your changes to your own fork of the repository then create a pull request for us to accept the code changes on this repository. For more detailed instructions you can see here. If you still need more help with this, just let us know.


Support for swapping into LBC

Issue

Closes 5503: Add support for swapping into LBC
Requires https://github.com/lbryio/lbry-redux/pull/389

Status (2021-03-14)
Reviewable.  Pending items:

API issues

[ ] Real swap testing put on hold. Been told that the production wallet is being changed.
[ ] The actual error messages aren't being relayed to Lbryio.call ... catch(error).  I always get internal_apis_down, so I can't really tell the user what's wrong.
[ ] Entering "20 BTC" gives the maximum LBC you can convert in a single transaction is %!g(int64=5855543). I think the given lbc_satoshi_requested of<PHONE_NUMBER>28163 should be correct?
[ ] On Desktop, if I initiated a swap while logged in, and later initiate another swap while logged out, I get "error": "model: unable to insert into address: Error 1062: Duplicate entry 'bXDu5BdX8avgWpumHJHBtFEueD7s1rtCjv' for key 'address.wallet_address_idx'".  I'm guessing it thinks I'm using another person's wallet?  Getting a new address fixes it, but I think the error shouldn't happen in the first place.

App-side

[ ] What should be the min and max BTC values?  I currently set to 1 sat and 21M, respectively, but I think these values don't make sense.
[ ] The API goes into HTTP 429 Too Many Requests state pretty quick.   I currently poll the status every minute.  Given that BTC transfers can take a while, the page (when left alone) will eventually go into the error state when the request limit is hit.  Should we disable the polling?
[ ] Test actual swap.

@tiger5226 is adding an endpoint for swap caps.

Update

Rebased to latest master
Changed btcAddresses to btc_addresses to match the rest
"Bitcoin":  use FormField's label instead of another div.