|
|
|
|
@@ -2,10 +2,57 @@
|
|
|
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / DASHBOARD / KPI
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
|
|
|
|
|
|
TODO: NEW CLIENT UPDATE ISSUES
|
|
|
|
|
NOTE: This might all be due to package.json needing to have it's version updated
|
|
|
|
|
it might be pulling that into the serviceworker for pwa or consulting it
|
|
|
|
|
NOPE, doesn't make any difference setting package.json version
|
|
|
|
|
|
|
|
|
|
Right now it doesn't always refresh, have to manually do so, it should reload and ditch the cache on update, not sure why it isn't to be honest
|
|
|
|
|
Try a test of it here locally and with release build, check network traffic, is it in fact actually updating and it's just the login page that isn't or...?
|
|
|
|
|
|
|
|
|
|
have an url that opens automatically or a notification and link to one after a new version has been detected just
|
|
|
|
|
like visual studio does in order to show what is new in this version
|
|
|
|
|
maybe ideally it opens to a new document page "whats new in version x.xx"
|
|
|
|
|
this way no need to go beyond the local server or hit our site unnecessarily
|
|
|
|
|
|
|
|
|
|
todo: Client is *NOT* automatically updating no matter what version numbers are set
|
|
|
|
|
Need to look into this and fix it for certain as it will be a huge issue when beta / release generally
|
|
|
|
|
Find the notes already about this, maybe there is a link about serviceworkers etc
|
|
|
|
|
|
|
|
|
|
https://medium.com/@dougallrich/give-users-control-over-app-updates-in-vue-cli-3-pwas-20453aedc1f2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### SMALL QUICK ITEMS #####
|
|
|
|
|
|
|
|
|
|
todo: make our logo smaller or move it when a biz logo is displaying on the login form
|
|
|
|
|
todo: can't delete second report template
|
|
|
|
|
FYI - still getting same server log error when try to delete report templates - CAN NOT DELETE more than one report template per loaded instance of servers
|
|
|
|
|
|
|
|
|
|
1. via Administration -> Report Templates -> open a report template, select menu delete.
|
|
|
|
|
2. First instance of selecting to delete since server was loaded - DOES delete.
|
|
|
|
|
3. BUT if servers have been up since last deleted, when attempting to delete a second report template () will get the error message and rpot is not deleted.
|
|
|
|
|
3.b only way to delete rpt template is to shut down servers, reload, then perform the above steps to delete. THEN have to shut down servers again, load again, then can delete third rpt. And so on. - CAN NOT DELETE more than one report template per loaded instance of servers
|
|
|
|
|
|
|
|
|
|
xo
|
|
|
|
|
|
|
|
|
|
2020-09-28 11:15:48.9309|ERROR|NotifyEventProcessor|Ops problem notification: "Server API internal error, see log for more details"=>System.InvalidOperationException: A second operation started on this context before a previous operation completed. This is usually caused by different threads using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.
|
|
|
|
|
at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()
|
|
|
|
|
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
|
|
|
|
|
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(DbContext _, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
|
|
|
|
|
at Npgsql.EntityFrameworkCore.PostgreSQL.Storage.Internal.NpgsqlExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
|
|
|
|
|
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
|
|
|
|
|
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
|
|
|
|
|
at AyaNova.Biz.ReportBiz.DeleteAsync(Int64 id) in C:\data\code\raven\server\AyaNova\biz\ReportBiz.cs:line 213
|
|
|
|
|
at AyaNova.Api.Controllers.ReportController.DeleteReport(Int64 id) in C:\data\code\raven\server\AyaNova\Controllers\ReportController.cs:line 153
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Logged|12_1(ControllerActionInvoker invoker)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
|
|
|
|
|
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
todo: Direct report view URL doesn't work if already logged in due to code only being in login form
|
|
|
|
|
need to hijack the router before navigation to intercept special urls
|
|
|
|
|
@@ -42,22 +89,7 @@ todo: v7 items .net final version update to if possible and feature request for
|
|
|
|
|
|
|
|
|
|
### MEDIUM ITEMS #######
|
|
|
|
|
|
|
|
|
|
TODO: NEW CLIENT UPDATE ISSUES
|
|
|
|
|
NOTE: This might all be due to package.json needing to have it's version updated
|
|
|
|
|
it might be pulling that into the serviceworker for pwa or consulting it
|
|
|
|
|
NOPE, doesn't make any difference setting package.json version
|
|
|
|
|
|
|
|
|
|
Right now it doesn't always refresh, have to manually do so, it should reload and ditch the cache on update, not sure why it isn't to be honest
|
|
|
|
|
Try a test of it here locally and with release build, check network traffic, is it in fact actually updating and it's just the login page that isn't or...?
|
|
|
|
|
|
|
|
|
|
have an url that opens automatically or a notification and link to one after a new version has been detected just
|
|
|
|
|
like visual studio does in order to show what is new in this version
|
|
|
|
|
maybe ideally it opens to a new document page "whats new in version x.xx"
|
|
|
|
|
this way no need to go beyond the local server or hit our site unnecessarily
|
|
|
|
|
|
|
|
|
|
todo: Client is *NOT* automatically updating no matter what version numbers are set
|
|
|
|
|
Need to look into this and fix it for certain as it will be a huge issue when beta / release generally
|
|
|
|
|
Find the notes already about this, maybe there is a link about serviceworkers etc
|
|
|
|
|
|
|
|
|
|
todo: chunk-vendors has fa-brands in it which is fucking huge, what else is in there I don't need?
|
|
|
|
|
eradicate fa-brands!
|
|
|
|
|
|
