Skip to content
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

F Prime GDS - Commanding locks up when resending a command from the history. #2473

Closed
timcanham opened this issue Jan 8, 2024 · 0 comments · Fixed by nasa/fprime-gds#159
Closed
Assignees
Labels
bug F´ GDS Issues pertaining to the F´ GDS
Projects

Comments

@timcanham
Copy link
Collaborator

F´ Version v3.4.1, commit 8a1612c
Affected Component n/a

Problem Description

When trying to resend a command with a numerical argument from the history, the command send button no longer functions. Looking at the dev console, the following error is sent:

TypeError: argument.value.startsWith is not a function
    squashify_argument http://127.0.0.1:5000/addons/commanding/arguments.js:123
    serialize_arg http://127.0.0.1:5000/addons/commanding/command-input.js:56
    sendCommand http://127.0.0.1:5000/addons/commanding/command-input.js:161

Opening a new connection in another tab clears the problem, but only until a command with a numerical argument is resent from the history again.

How to Reproduce

  1. Find a command with a numerical argument
  2. Send the command
  3. Double click on the command from the history and see the behavior

Expected Behavior

User should be able to always send a command from the history.

@timcanham timcanham added the bug label Jan 8, 2024
@timcanham timcanham added this to CCB in Gecko via automation Jan 9, 2024
@thomas-bc thomas-bc added the F´ GDS Issues pertaining to the F´ GDS label Jan 10, 2024
Gecko automation moved this from CCB to Complete Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug F´ GDS Issues pertaining to the F´ GDS
Projects
Gecko
Complete
Development

Successfully merging a pull request may close this issue.

2 participants