Skip to content

ReadData and DataBlockCodec#4

Merged
mkitti merged 6 commits intoJaneliaSciComp:mainfrom
tpietzsch:readdata
May 16, 2025
Merged

ReadData and DataBlockCodec#4
mkitti merged 6 commits intoJaneliaSciComp:mainfrom
tpietzsch:readdata

Conversation

@tpietzsch
Copy link
Copy Markdown
Collaborator

follow changes in saalfeldlab/n5#137

@tpietzsch tpietzsch changed the title SplittableReadData ReadData and DataBlockCodec Feb 19, 2025
@mkitti
Copy link
Copy Markdown
Collaborator

mkitti commented Mar 5, 2025

@tpietzsch do we need to wait for saalfeldlab/n5#137 before we merge this?


@Override
public OutputStream getOutputStream(OutputStream out) throws IOException {
OutputStream getOutputStream(OutputStream out) throws IOException {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should this be explicitly private as well?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

probably, yes

@tpietzsch
Copy link
Copy Markdown
Collaborator Author

@tpietzsch do we need to wait for saalfeldlab/n5#137 before we merge this?

Yes, please. We are still iterating over that PR as well. This one is just to keep everything building with the SNAPSHOTs. I will also remove the unrelated formatting changes. Maybe best ignore it for now...

@tpietzsch tpietzsch marked this pull request as draft March 5, 2025 19:39
@tpietzsch
Copy link
Copy Markdown
Collaborator Author

I converted it to Draft PR now. Sorry for that oversight...

@tpietzsch tpietzsch marked this pull request as ready for review May 16, 2025 14:33
@tpietzsch
Copy link
Copy Markdown
Collaborator Author

@mkitti it would be cool if you could merge this and release n5-zstandard-2.0.0-alpha-1

@mkitti
Copy link
Copy Markdown
Collaborator

mkitti commented May 16, 2025

ok, merging

@mkitti mkitti merged commit 113d851 into JaneliaSciComp:main May 16, 2025
1 check passed
@mkitti
Copy link
Copy Markdown
Collaborator

mkitti commented May 16, 2025

I tried running scijava-scripts/release-version.sh to version 2.0.0-alpha-1 but I have no idea if it worked.

@ctrueden ?

@ctrueden
Copy link
Copy Markdown
Collaborator

ctrueden commented May 17, 2025

@mkitti Unfortunately, it appears that the release build failed.

From the log:

Failed to deploy artifacts: Could not transfer artifact org.janelia:n5-zstandard:pom:2.0.0-alpha1 from/to scijava.releases (dav:https://maven.scijava.org/content/repositories/releases): Failed to transfer file: https://maven.scijava.org/content/repositories/releases/org/janelia/n5-zstandard/2.0.0-alpha1/n5-zstandard-2.0.0-alpha1.pom. Return code is: 401

Which indicates that the configured deployment credentials for maven.scijava.org are incorrect.

In February 2024, I had a video call with Don Olbris where we got the credentials added to at least one relevant repository. I vaguely remember that he did not want to set things up the normal SciJava way of adding the credentials to the org as a whole, but rather wanted to add them to one repository at a time. Don has a copy of the credentials and can configure them as needed. I can also meet with you and/or Don again as needed to double check the validity of the credentials.

@tpietzsch
Copy link
Copy Markdown
Collaborator Author

I can also meet with you and/or Don again as needed to double check the validity of the credentials.

Same here.
You could also make me admin of the repository (temporarily) and I can try to take care of it.

@mkitti
Copy link
Copy Markdown
Collaborator

mkitti commented May 17, 2025

You are both admins on the repository now:
image

@ctrueden
Copy link
Copy Markdown
Collaborator

When I logged in to check it, I noticed that this repository had a copy of the secrets added 2 years ago, which was overriding the same secrets added to the entire org 1 year ago. I deleted the (presumably outdated) repository-specific copy of the secrets, in favor of the org-wide ones, reran the release, and got this error instead:

== Configuring Maven ==
  Performing deployment checks
  ==> FAILED: EXIT CODE 1
  No deploy -- could not extract ciManagement URL
  Output of failed attempt follows:
  Error:  Error executing Maven.
  Error:  character 11 is not allowed in output
  Error: en-gpg-plugin version OK: [ERROR] Error executing Maven.
  Error:  character 11 is not allowed in output
  
  == Building the artifact locally only ==
  Error:  Error executing Maven.
  Error:  character 11 is not allowed in output
  ==> FAILED: EXIT CODE 1

I then re-added the secrets to this repository specifically, reran the release again, and this time it worked. ✔️

It seems likely there is something wrong with the repository-wide secrets. I would suggest deleting or updating them.

@tpietzsch
Copy link
Copy Markdown
Collaborator Author

Thank you @ctrueden !

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