Intermittent routing freeze-ups to the auth enabled Dashboard route

[JoshuaVSherman]

I'm submitting a bug report

• Aurelia Skeleton Version

skeleton-esnext-webpack

• Framework Version:
  same as in this skeleton

Please tell us about your environment:

• Operating System:
  Ubuntu 16.04 LTS

• Node Version:
  7.9.0

• NPM Version:
  4.2.0

Webpack same as in this skeleton

• Browser:
  Chrome Version 57.0.2987.133 (64-bit)

• Language:
  ESNext

Current behavior:
Intermittent freeze to the /dashboard route after login. I am using the Aurelia-Auth plugin
There was no issue before I upgraded to the latest version of this skeleton, and there is no way to debug this issue that I am aware of. Myself and another developer have tried everything we could think of for the past day, but were unsuccessful in resolving this bug. i am open to using a different plugin or front end package for auth if that is the only solution.

Expected/desired behavior:
After login, the user gets routed to the /dashboard successfully without any freeze-ups

link to repo:
https://github.com/WebJamApps/combined-front/tree/dev/src

[JoshuaVSherman]

i'm not sure if I fixed it, but i'm not able to reproduce this issue at this time, so closing this

[JoshuaVSherman]

This seems to only occur intermittently and when i'm running the app locally using the webpack development server, also I have push-state enabled in routing

[JoshuaVSherman]

unable to reproduce at this time

[JoshuaVSherman]

steps to reproduce:

• clear browser history (chrome)
• open console
• npm start (starts webpack dev server)
• login to google
• post to google succeeds in backend, but Aurelia-Auth fails to process the response back from google,
  browser says Processing Request ...
  never stops processing

[jods4]

Is this the right place for this issue?

It seems related with aurelia-auth more than the skeletons.

[JoshuaVSherman]

closing with this issue posted to aurelia-auth
paulvanbladel/aurelia-auth#178

[JoshuaVSherman]

could this be an issue with using the aurelia-webpack-plugin
and how we needed to do this in the main.js
aurelia.use.plugin(PLATFORM.moduleName('aurelia-auth/auth-filter'));
aurelia.use.plugin(PLATFORM.moduleName('aurelia-auth'), (baseConfig)=>{
baseConfig.configure(config);
});

[jods4]

Any reason why it would?
That code ensures Webpack includes the required modules in the bundle and compiles to:

aurelia.use.plugin('aurelia-auth/auth-filter');
aurelia.use.plugin('aurelia-auth', baseConfig=>baseConfig.configure(config));

[JoshuaVSherman]

I don't recall needing the auth filter line in the old skeleton On Apr 24, 2017 4:19 PM, "jods" <[email protected]> wrote: Any reason why it would? That code ensures Webpack includes the required modules in the bundle and compiles to: aurelia.use.plugin('aurelia-auth/auth-filter');aurelia.use.plugin('aurelia-auth', baseConfig=>baseConfig.configure(config)); — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#805 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMuN2JtyWc4D1a9ks2JkFcErMQXJYeAiks5rzQPrgaJpZM4NCSwR> .

[JoshuaVSherman]

This just happened from production, so it is not the webpack dev server
https://www.web-jam.com/dashboard

please provide any recommendations

[JoshuaVSherman]

https://github.com/aurelia/framework/blob/master/doc/article/en-US/securing-your-app.md
https://gist.github.com/martonsagi/b70a094db52e0cc34fd7c44de550f046
https://www.npmjs.com/package/aurelia-oauth
https://aurelia-authentication.spoonx.org/Quick%20start.html
http://stackoverflow.com/questions/37076484/aurelia-js-authorization

[jods4]

My recommandation is to look for support with aurelia-auth.
aurelia-auth is not even in the skeleton so I don't think you'll get much help here.

[JoshuaVSherman]

ok fair enough i'm not seeing much being done with that project anymore, so I might have to refactor the way I am handling auth in the frontend then it is just strange that these problems only occurred after I moved to the latest skeleton

…

On Tue, Apr 25, 2017 at 1:21 PM, jods ***@***.***> wrote: My recommandation is to look for support with aurelia-auth. aurelia-auth is not even in the skeleton so I don't think you'll get much help here. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#805 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMuN2B8mgqODbl2lgzCitNohTpiiVPJjks5rzit-gaJpZM4NCSwR> .

-- Josh Sherman www.joshandmariamusic.com

[JoshuaVSherman]

could this be the reason?
SpoonX/aurelia-authentication#347

I know this is not the same plugin i'm using, but it seems similarly an issue

[JoshuaVSherman]

This might have been a good thing to mention up front in your readme file for the differences between the old and new skeleton webpack esnext
https://github.com/aurelia/webpack-plugin/wiki/Managing-dependencies

[jods4]

How is that issue even remotely related?

You say that you have intermittent freezes with aurelia-auth.

That issue is about a consistent crash for a missing module with message:
Unable to find module with ID: aurelia-authentication/authFilterValueConverter
when using aurelia-authentication...

[JoshuaVSherman]

read on down, the proposed solution was to use the

plugins: [
new AureliaPlugin(),
new ModuleDependenciesPlugin({
'aurelia-auth': ['./auth-filter'],
'aurelia-polymer': ['./au-select-custom-attribute'],
'au-table': ['./au-table', './au-table-select', './au-table-sort']
}),

so far I have not been able to reproduce the freezeup. This was my main.js before:

//aurelia.use.plugin(PLATFORM.moduleName('aurelia-auth/auth-filter'));
aurelia.use.plugin(PLATFORM.moduleName('aurelia-auth'), (baseConfig)=>{
baseConfig.configure(config);
});

[JoshuaVSherman]

in the old skeleton, we didn't use this PLATFORM.moduleName thing so that seems to be a difference here

[jods4]

Please, this is not a support forum.

Issues in this repository are meant to report bugs in the skeletons, or suggest improvements (to the skeletons).

If you need help with integrating a library, Gitter or StackOverflows are better venues.

If you encounter bugs with 3rd party libraries like aurelia-auth not responding, their issue tracker is where you should report them.

You seem to be fishing in the dark here and I really can't help you with that.
As I told you before, using ModuleDependencingPlugin or PLATFORM.moduleName ends up in exactly the same result.
If you don't reproduce the issue it's most likely because it's sporadic. It's not the first time you say that you can't reproduce it... until it eventually happens again.

I won't read down that other issue because I know exactly what it is (trust me, I wrote the Webpack plugin) and it has absolutely nothing in common with yours (based on your description).

The way you describe your issue looks like a bug in aurelia-auth.
Webpack generates a deterministic bundle with synchronously resolved dependencies. It works or it does not.
aurelia-webpack-plugin doesn't do much more than registering dynamic dependencies in Webpack.
If your library has a race condition somewhere we won't be able to fix it here.

[JoshuaVSherman]

I understand, I won't bother you again