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

Investigate import failure of LUCENE-1498 #14

Closed
mocobeta opened this issue Jul 3, 2022 · 3 comments
Closed

Investigate import failure of LUCENE-1498 #14

mocobeta opened this issue Jul 3, 2022 · 3 comments
Assignees
Labels

Comments

@mocobeta
Copy link
Contributor

mocobeta commented Jul 3, 2022

https://issues.apache.org/jira/browse/LUCENE-1498 won't be imported.

[2022-06-26 18:38:25,394] ERROR:import_github_issues: Import GitHub issue /mnt/hdd/repo/sandbox-lucene-10557/migration/github-import-data/GH-LUCENE-1498.json was failed. status=failed, errors=[{'location': '/issue', 'resource': 'Issue', 'field': None, 'value': None, 'code': 'error'}]

Maybe the body contains character sequences that are not acceptable to GitHub?

@mocobeta
Copy link
Contributor Author

The root cause is unclear (the issue description may be too large for importing). It can be manually recovered afterward.

  1. set a dummy text to issue's "body" field when importing via API
  2. after importing, update the issue body from the web GUI. (confirmed that it's possible to set the original text from GUI.)

@mocobeta
Copy link
Contributor Author

mocobeta commented Jul 10, 2022

The same as https://issues.apache.org/jira/browse/LUCENE-5612.

[2022-06-27 02:28:25,450] ERROR:github_issues_util: Failed to import issue LockStressTest fails always with NativeFSLockFactory [LUCENE-5612]; status_code=413, message={"message":"Payload too big: 1048576 bytes are allowed, 1468832 bytes were posted.","documentation_url":"https://docs.github.com/rest"}

=> It is not possible to set the original text (long comment) from GUI.
Screenshot from 2022-07-10 12-34-16

As a workaround, I'd paste a permanent link to the original comment in Jira.

@mocobeta mocobeta self-assigned this Jul 10, 2022
@mocobeta
Copy link
Contributor Author

The quick workaround (manual recovering) should work. I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant