-
-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Application error: Uncaught (in promise): TypeError: e.replace is not a functionNS #1069
Comments
👋🏾Thanks for opening your first issue here! Be sure to follow the issue template! ✌🏾 |
Hey, this only happens with the history? |
It actually happens at start up, but I guess it's because it tries to read the type from history. The history entries are not usable if they have a date (they just say |
This looks to be the same error reported in #1052. Unfortunately it is not enough information to debug it. A couple of questions that should help:
Considering the source of the error (ngx-codemirror), this component is used in 7 places (environment manager, pre request editor, query editor, query result, settings, subscription connection params, variables editor). This means the source of the error has to be coming from one or more of these places. Does any of them sound like the likely cause of the error? |
Error message: Uncaught (in promise): TypeError: e.replace is not a function
NS@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:2795292
zUnb/HS</e.prototype.writeValue@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:2797745
ne/</<@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1802959
gIcY/ye</t.prototype.setValue/<@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1813270
gIcY/ye</t.prototype.setValue@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1813243
gIcY/Le</t.prototype._updateValue/<@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1830148
0TWp/</</s</e.prototype.invoke@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:7509
onInvoke@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1048214
0TWp/</</s</e.prototype.invoke@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:7449
0TWp/</</a</t.prototype.run@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:2712
R/<@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:14688
0TWp/</</s</e.prototype.invokeTask@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:8193
onInvokeTask@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/main.649f735f13b1c272333d.js:1:1048126
0TWp/</</s</e.prototype.invokeTask@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:8114
0TWp/</</a</t.prototype.runTask@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:3375
g@moz-extension://75779467-f5b9-4ac2-8dd3-63b29e401f60/polyfills.72b889dd8c5039bf7f7f.js:1:10460
Error stack:
Additional information:
This has only been observed when using our in-house scalar type
DateTime
, as input argument. I haven't tried with other custom scalar types.This is the query:
It happens even if I set the date as a variable in the
variables
field.What happens:
Altair throws an exception (the one above) when opening or loading from history, and deletes all text in whichever field that contains the DateTime string. So if the string is in
variables
, everything invaribles
is deleted and ditto for thequery
field.Addiotionally, the history says "Invalid Date" for queries containing dates. The date is not invalid in our system, and the system accepts it when the query is fired.
I hope that was enough to troubleshoot.
Happy debugging. :)
The text was updated successfully, but these errors were encountered: