-
Notifications
You must be signed in to change notification settings - Fork 11
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
[Feature] Overwrite test by URI during QTI import #2491
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
9baafd9
feat: overwrite test by URI during QTI import
shpran 1bdcdee
chore: rollback old parameter to avoid breaking changes
shpran 589f77a
chore: translation location
shpran 2fa9935
chore: change classes to subfolder at the beginning, rename props
shpran 78db3dc
chore: fix CI, simplify code
shpran 8f6a918
chore: remove unnecessary parameter
shpran 3d5d769
chore: rename props, return null
shpran b1e7ae0
Merge branch 'develop' of https://github.com/oat-sa/extension-tao-tes…
shpran d50a809
chore: add custom packageLabel param
shpran f6c647f
chore: update swagger, add exception log
shpran File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shpran would it be asking too much if we could make sure that the exceptions caught here have logs with:
Maybe we already have something on
returnFailure
implementation?I am asking, cause generally this logs with only exception message do not help at all as we have no idea where it happened. This is a critical process for the whole ingestion process, so I think it is useful to have this logs
Wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one doesn't relate to my changes (just fixed FQN), but sure I will improve these logs 😎
Thanks for suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shpran I know this is not part of your changes, but today is a bit of a pain to track errors when we are generating translations. Could you please add logs for that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked
returnFailuer
implementation and found, that we use Advanced Logger feature there, so message, file, line and trace should be logged: