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

InvalidInputException: This state does not have any interaction specified. #20224

Open
kevintab95 opened this issue Apr 26, 2024 · 0 comments
Open
Labels
bug Label to indicate an issue is a regression server errors

Comments

@kevintab95
Copy link
Member

This error occurred recently in production:

Traceback (most recent call last):
  File "/workspace/core/controllers/editor.py", line 581, in _publish_exploration
    exploration.validate(strict=True)
  File "/workspace/core/domain/exp_domain.py", line 1682, in validate
    state.validate(
  File "/workspace/core/domain/state_domain.py", line 3738, in validate
    raise utils.ValidationError(
core.utils.ValidationError: This state does not have any interaction specified.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/layers/google.python.pip/pip/lib/python3.8/site-packages/webapp2.py", line 604, in dispatch
    return method(*args, **kwargs)
  File "/workspace/core/controllers/acl_decorators.py", line 2361, in test_can_publish
    return handler(self, exploration_id, *args, **kwargs)
  File "/workspace/core/controllers/editor.py", line 600, in put
    self._publish_exploration(exploration_id)
  File "/workspace/core/controllers/editor.py", line 583, in _publish_exploration
    raise self.InvalidInputException(e)
core.controllers.base.UserFacingExceptions.InvalidInputException: This state does not have any interaction specified.

Where did the error occur? Add the page the error occurred on.
/createhandler/status/XXX

Which release did the error occur in? Add the Oppia release version associated with the error.
3.3.7

Frequency of occurrence Add details about how many times the error occurred within a given time period (e.g. the last week, the last 30 days, etc.). This helps issue triagers establish severity.
2 times in 24 days.

General instructions for contributors
In general, the procedure for fixing server errors should be the following:

  • Analyze the code in the file where the error occurred and come up with a hypothesis for the reason.
  • Based on your hypothesis, determine a list of steps that reliably reproduce the issue (or confirm any repro instructions that have been provided). For example, if your hypothesis is that the issue arises due to a delay in a response from the backend server, try to change the code so that the backend server always has a delay, and see if the error then shows up 100% of the time on your local machine.
  • Explain your proposed fix, the logic behind it, and any other findings/context you have on this thread. You can also link to a debugging doc if you prefer.
  • Get your approach validated by an Oppia team member.
  • Make a PR that fixes the issue.
@kevintab95 kevintab95 added triage needed server errors bug Label to indicate an issue is a regression labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Label to indicate an issue is a regression server errors
Projects
Status: Todo
Development

No branches or pull requests

2 participants