Skip to content

Bug/cite 229 - Checking access of an upload in progress should be possible with the upload id. #294

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

Open
wants to merge 13 commits into
base: develop
Choose a base branch
from

Conversation

PradnyaC11
Copy link
Contributor

@PradnyaC11 PradnyaC11 commented Jan 21, 2025

Guidelines for Pull Requests

If you haven't yet read our code review guidelines, please do so, You can find them here.

Please confirm the following by adding an x for each item (turn [ ] into [x]).

  • I have removed all code style changes that are not necessary (e.g. changing blanks across the whole file that don’t need to be changed, adding empty lines in parts other than your own code)
  • I am not making any changes to files that don’t have any effect (e.g. imports added that don’t need to be added)
  • I do not have any sysout statements in my code or commented out code that isn’t needed anymore
  • I am not reformatting any files in the wrong format or without cause.
  • I am not changing file encoding or line endings to something else than UTF-8, LF
  • My pull request does not show an insane amount of files being changed although my ticket only requires a few files being changed
  • I have added Javadoc/documentation where appropriate
  • I have added test cases where appropriate
  • I have explained any part of my code/implementation decisions that is not be self-explanatory

Please provide a brief description of your ticket

Checking access of an upload in progress should be possible with the upload id.

... Put ticket description here and add link to ticket ...
Right now, you need the documentId of a finished uploaded document or a progress id to check if a user has access to a giles upload. Citesphere, when checking the progress of an upload, needs to store the upload id (after the initial submission, there is just a progress id). And then in the CheckAccessController, it needs to also be possible to send the Upload Id.
(this is for the API endpoint)

https://diging.atlassian.net/browse/CITE-229

Are there any other pull requests that this one depends on?

diging/citesphere-model#56

Anything else the reviewer needs to know?

... describe here ...

@diging-jenkins
Copy link

Can one of the admins verify this patch?

@PradnyaC11 PradnyaC11 requested a review from jdamerow January 21, 2025 22:33
this.documentIds = documentIds;
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a reason for this change?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this still

@jdamerow jdamerow closed this Apr 29, 2025
@PradnyaC11 PradnyaC11 reopened this May 1, 2025
continue;
ObjectMapper mapper = new ObjectMapper();
String jsonBody = response.getBody();
GilesCheckUploadResponse processed = new GilesCheckUploadResponse();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this does not need to be initialized here does it? it either is set in line 147 or processed will never be used?

@@ -153,6 +168,7 @@ public void checkUploads() {
logger.error("Could not deserialize response.", e);
upload.setDocumentStatus(GilesStatus.FAILED);
checkedUploads.add(upload);
continue;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is added here, then processed does not need to be initialized in line 164, does it?

this.documentIds = documentIds;
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this still

@jdamerow jdamerow closed this May 6, 2025
@PradnyaC11 PradnyaC11 reopened this May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants