NoSuchBucket exception when playing with Path.resolve method

[FredPraca]

Bug Description

When using resolve on a S3Path representing a root location, the URI doesn't get changed accordingly.

I use the following code to initialize a Path object to the bucket

rootLocation = s3fs.getPath("/" + bucketName);

Every call received uses a path relative to this root contained in the filePath variable below

Path newPath = s3fs.getPath(dateTimeFormatter.format(LocalDateTime.now()));
// First we create if need the directory for the current time
Path directoryPath = this.rootLocation.resolve(newPath).normalize().toAbsolutePath();

Path destinationFile = directoryPath.resolve(filePath).normalize().toAbsolutePath();

According to toString() method, The directoryPath variable above is formed with something like /bucketname/202502121846/.
But the uri member of the path contains /202502121846 stripping the bucket name.

This leads to a NoSuchBucket exception when trying to write or read the data.

Expected Behavior

The uri should also contain the root directory we are resolving to.

As a note, it was working on the 1.0.6 version but fails on 2.0.0 and 3.0.0.

Environment

• s3fs-nio version: 3.0.0
• OS: Linux
• JDK: 21
• S3 backend: Minio

[steve-todorov]

Hey @FredPraca ,

Thanks for reporting this and sorry for the slightly delayed reply.

I was not able to reproduce the problem you are talking about.

Here's the test I came up based on your explanation:

@Test
void ticket880() throws IOException
{
    final DateTimeFormatter dateTimeFormatter = DateTimeFormatter.ofPattern("yyyy-MM-dd-HHmmss");
    final LocalDateTime now = LocalDateTime.now();
    final String formattedNow = dateTimeFormatter.format(now);
    final String bucket = EnvironmentBuilder.getRealEnv().get(EnvironmentBuilder.BUCKET_NAME_KEY).toString();
    final String expectedPath = bucket + "/" + formattedNow + "/my-file.txt";

    Path rootPath = fileSystemAmazon.getPath(bucket);

    Path newPath = rootPath.resolve(formattedNow).normalize().toAbsolutePath();
    Files.createDirectories(newPath);

    Path directoryPath = rootPath.resolve(newPath).normalize().toAbsolutePath();
    Path destinationFile = directoryPath.resolve("my-file.txt").normalize().toAbsolutePath();

    assertThat(destinationFile.toAbsolutePath().toString()).isEqualTo(expectedPath);
}

We also have a few more unit tests which cover different resolve scenarios:

• ResolveTest
• ResolveSiblingTest
• S3PathTest

If you could create a reproducible test using the example code from above -- we'd be happy to continue investigating this.