Project

General

Profile

Actions
Copy link

Bug #24783

open

Pending nodes history has JS errors in console and prevents node deletion

Added by Clark ANDRIANASOLO 11 months ago. Updated 8 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
8.2.6
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
77
Name check:
To do
Fix check:
To do
Regression:
No

Description

When I open the history tab which is has one node that I have previously accepted, and I click on the node to see its content, I see multiple errors in the browser console :


Uncaught TypeError: Elm.Score is undefined
Uncaught TypeError: Elm.ComplianceScore is undefined
Uncaught TypeError: Elm.SystemUpdateScore is undefined
Uncaught TypeError: Elm.Node is undefined

Uncaught TypeError: this._config is undefined
    _initializeBackDrop modal.js:160
    On modal.js:71
    getOrCreateInstance base-component.js:65
    <anonymous> modal.js:365
    n event-handler.js:118
    S event-handler.js:184
    on event-handler.js:216
    <anonymous> modal.js:339
    <anonymous> bootstrap.bundle.min.js:6
    <anonymous> bootstrap.bundle.min.js:6

(stack trace are omitted except for the last one).

Also, I can't delete a node with the Delete button, which does nothing.

Related issues 1 (1 open — 0 closed)

Related to Rudder - Bug #26500: Unexpected JS popup alert message in 8.3 when viewing pending nodesNewActions
Actions
Copy link
 #1

Updated by Clark ANDRIANASOLO 11 months ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 8.1.2 to 8.1.3
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.3 to 8.1.4
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.4 to 8.1.5
  • Priority changed from 91 to 90
Actions
Copy link
 #5

Updated by Nicolas CHARLES 9 months ago

This is still the case

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.1.5 to 8.1.6
  • Priority changed from 90 to 89
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 8.1.6 to 8.1.7
  • Priority changed from 89 to 88
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.1.7 to 8.1.8
  • Priority changed from 88 to 86
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.8 to 8.1.9
  • Priority changed from 86 to 84
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.1.9 to 8.1.10
  • Priority changed from 84 to 83
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.1.10 to 8.1.11
  • Priority changed from 83 to 82
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.11 to 8.1.12
  • Priority changed from 82 to 81
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.12 to 8.1.13
  • Priority changed from 81 to 78
Actions
Copy link
 #14

Updated by Clark ANDRIANASOLO 8 days ago · Edited

  • Subject changed from Pending nodes history prevents node deletion and has JS errors in console to Pending nodes history has JS errors in console and prevents node deletion
  • Target version changed from 8.1.13 to 8.2.6
  • Priority changed from 78 to 77

This is still the case, on all versions of Rudder now.

It does not seem to prevent anything else, but maybe it is related to #26500

Actions
Copy link
 #15

Updated by Clark ANDRIANASOLO 8 days ago

  • Related to Bug #26500: Unexpected JS popup alert message in 8.3 when viewing pending nodes added
Actions
Copy link

Also available in: Atom PDF