Linux Dockerfile produces container image that produces errors when being run in OpenShift

When using the proposed Dockerfile to create a container image, this image throws an error when being run within an OpenShift environment. The reason is that the container is by default write-protected in OpenShift (compare: https://stackoverflow.com/a/58474145/1426535). This can be solved by adding this into the Dockerfile:
RUN chgrp -R 0 /azp && \
    chmod -R g=u /azp

The complete docker file would then be the following:
FROM ubuntu:latest
RUN DEBIAN_FRONTEND=noninteractive apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get upgrade -y

RUN DEBIAN_FRONTEND=noninteractive apt-get install -y -qq --no-install-recommends \
    apt-transport-https \
    apt-utils \
    ca-certificates \
    curl \
    git \
    iputils-ping \
    jq \
    lsb-release \
    software-properties-common

RUN curl -sL https://aka.ms/InstallAzureCLIDeb | bash

# Can be 'linux-x64', 'linux-arm64', 'linux-arm', 'rhel.6-x64'.
ENV TARGETARCH=linux-x64

WORKDIR /azp

COPY ./start.sh .
RUN chmod +x start.sh

# https://stackoverflow.com/a/58474145/1426535
RUN chgrp -R 0 /azp && \
    chmod -R g=u /azp

ENTRYPOINT ["./start.sh"]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b31d4f6c-d16d-2ba1-1294-6aa94e328046
Version Independent ID: 88aec599-4410-697d-1002-1c41b1c17bb6
Content: Run a self-hosted agent in Docker - Azure Pipelines
Content Source: docs/pipelines/agents/docker.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

I continued working on this problem and my proposed change is not fully fixing the issue in OpenShift. If someone has knowledge about OpenShift I'd appreciate support to get it running and then update the documentation.

@RufusJWB -- Rufus, thank you for your detailed feedback and follow-up.  This repo is solely for documentation issues, and this seems implementation- and product-related.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

cc @steved0x for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


PHP inconsistency in collection sort between PHP 5.6.30 and 7.1.4

Laravel Version: 5.3.*
PHP Version: 5.6.30
Database Driver & Version: MySql - 10.1.21-MariaDB

Description:
Using the function sortBy of a collections, will get different results in PHP 5.6.30 rather then PHP 7.1.4.
Steps To Reproduce:
I have made an array like this:
$quizzes['scores'] = [     [         'user_id' => 1,         'score' => 50,         'timespan' => 5000     ],  [         'user_id' => 2,         'score' => 70,         'timespan' => 6000     ] ];
But when i run this code:
$quizzes['scores'] = collect($quizzes['scores'])->sortBy('score')->toArray();
what I get on PHP 5.6.30 is:

User id 2, score, 70, timespan 5000
User id 1, score 50, timespan 6000

but what I get on PHP 7.1.4 is:

User id 1, score 50, timespan 6000
User id 2, score, 70, timespan 5000
This one should be the correct, since if I run sortByDesc i get them in descendant sequence.

Testing on both versions the results are the same as your PHP 7.1 example.
Closing since it doesn't look like a bug in the framework, also please upgrade your application since laravel 5.3 is not supported anymore.


Omnicore-cli "Error -32601: Method not found"

I'm running Omnicored
omni@server:~$ omnicore/omnicored --version
Omni Core daemon version v<IP_ADDRESS>-fe66360

Omni-related RPC commands aren't working with the cli tool:
omni@server:~$ omnicore/omnicore-cli "omni_getbalance", "address" 3
error: {"code":-32601,"message":"Method not found"}

My bad, since I was running Bitcoin core on port 8332, I have to specify the different port when using the CLI tool:
omnicore-cli -rpcport=8032 -rpcuser=user rpcpassword=pass "omni_getbalance", "address" 4

Your command has extra comma after omni_getbalance


Package native library files in Maven release

Category
Other
Describe the feature you'd like to request
It would be nice if we packaged native library files in the Maven release so people don't have to download them from github.
Describe the solution you'd like
It looks like we could follow https://stackoverflow.com/a/10071519 to include the native libraries in the Maven release.
Describe alternatives you've considered
Current system.
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

@andrewmwells-amazon I am interested in adding native library bundling to cedar-java, and I would be glad to put together a pull request if that would be helpful.
In terms of supported operating systems and architectures, what should be prioritized for initial implementation? Starting with Linux and x86_64/amd64 seems like a minimum requirement. The popularity of macOS and aarch64/arm64 is also worth considering. Should supporting Windows be included in the initial scope?
As far as runtime implementation, the Stack Overflow discussion has a helpful example of direct code that reads JVM System properties and loads the library from a preset path in the JAR. The Fizzed Java Native Environment library also seems worth considering, as it is licensed under Apache-2.0, only depends on SLF4J API, and provides a simple API with convention-based storage of libraries to be loaded. Is there a preferred approach in terms of direct implementation versus such a library?
The last major question relates to the build approach itself. Regardless of the build strategy, the end result requires bundling the platform-specific binaries from a common location. GitHub Actions provides runners for Linux, macOS, and Windows, and just recently introduced macOS 14 with M1 processors, which would allow building for aarch64. It seems like it would be helpful to have a build process that also works a local machine, provided certain required components are installed. This could be implemented through a shell script, or integrated more directly as a task in the Gradle build. Part of the challenge includes how to orchestrate the multi-platform builds for the native Rust library.
To help move this forward, I created a branch with that uses the Fizzed JNE library and builds a JAR that contains both Linux x86_64 and macOS aarch64 binaries using Maven to execute Cargo build commands, running on a GitHub workflow with macOS 14. The following commit contains the initial set of changes:
https://github.com/exceptionfactory/cedar-java/commit/be785ca7e672463f9b511f571035cfb26bde826a
I used Maven to avoid changes to the Gradle build configuration, but the Cargo build execution could be handled just as easily in Gradle, or perhaps a preparatory shell script. I replaced the separate System.load() calls with a shared NativeLibraryLoader utility that calls the JNE.loadLibrary() method. For compatibility, it also checks for the currently-defined environment variable, which would provide a workaround for platforms that are not bundled in the JAR itself.
I am not very familiar with all of the build options for Rust, but after evaluating cross and its Docker-based approach, I went with cargo-zigbuild to build the Linux x86_64 binary on the macOS 14 runner.
With this background, I would be glad to know what approach would be preferred so that this could be turned into a pull request for review.

@khieta Thanks for the recent reviews of several pull requests.
Do you have any initial feedback on a preferred way forward for native library bundling in the cedar-java JAR?
If it would be helpful to consider this in the context of a pull request, I can look at putting something together that integrates with the current Gradle build.

Thanks for reaching out @exceptionfactory! I've pinged some of our collaborators who have more Java expertise than myself. I'll ask them to take a look 🙂

Thanks for the helpful reply @lucajone!
I agree with you about the size concern for bundling platform-specific libraries. Use of the classifier approach is a good solution that would allow integrating services to decide on which architectures are required, while keeping the bundle small. The conscrypt library is one example that produces both platform-specific JAR files and an uber JAR that bundles all supported platforms. Adoption of the uber JAR seems more common as it just works in most common environments.
Although the uncompressed size of each native library is 9 or 10 MB, the compression ratio for those files in pretty good. For example, the cedar-java package I published for testing includes an 8 MB native library for macOS ARM and a 13 MB native library for Linux x86-64, but resulting JAR file is only 6.6 MB. That is not small, but it means a JAR for the most commons platforms should be closer to 20 MB than 50 MB.
I agree with you that running integration tests on the native platforms would be ideal. GitHub Action workflows should be able to support this approach, so it is really just an orchestration question. One approach could be building the cross-compiled JAR on one runner, and then having runners with each OS (Linux, macOS, and Windows) pull the JAR and run tests. The cross-compilation options for Rust open up various possibilities, so it really just seems to be a better of deciding on the build host environment, and then structuring the rest of the build accordingly. If the goal is to provide the greatest amount of flexibility, Gradle tasks could be implemented to call the appropriate commands based on the OS running the build.
I will take a closer look at putting together a pull request soon to keep the discussion moving forward.

The conscrypt approach looks like exactly what I was hoping for, and from what you're saying it sounds like it is fairly straightforward for us to vend platform-specific JARs and a bundled JAR. Excellent! I had completely forgotten about compression; 20MB is much more reasonable, and seems pretty feasible to offer as a convenience if we've also got the option to publish per-platform artifacts as well.
Presuming the cross-compilation is stable enough, I think the suggestion to build in one place and just test in others makes sense since it saves us a step at the end to build the final JAR. But it's much of a muchness – I think to begin with, having some Gradle targets to build JARs with the libraries included (cross- or native-compiled) would be a good place to start and we can iterate on the different combinations as they become useful.

Is this issue resolved? #105 is merged and it looks like the 3.1.2 maven release includes cedar-java-3.1.2-uber.jar

I think this is resolved, primarily by #104.  I'm going to go ahead and close this; if there are any remaining tasks or things not yet done, let's open separate issues for those.


Added activity recognition and privileged phone state permissions for Android Q

Summary
This PR is to add ACTIVITY_RECOGNITION and READ_PRIVILEGED_PHONE_STATE,  the new permissions added as part of Android Q
This fixes https://github.com/facebook/react-native/issues/28231
Changelog
[Android] [Changed] - add ACTIVITY_RECOGNITION, READ_PRIVILEGED_PHONE_STATE to PermissionsAndroid and NativePermissionsAndroid
Test Plan
Test Plan:
PermissionsAndroid.ACTIVITY_RECOGNITION === 'android.permission.ACTIVITY_RECOGNITION'
PermissionsAndroid.READ_PRIVILEGED_PHONE_STATE === 'android.permission.READ_PRIVILEGED_PHONE_STATE'

READ_PRIVILEGED_PHONE_STATE is not a run time permission that a 3rd party app can request for. Can you please remove the same?

READ_PRIVILEGED_PHONE_STATE is not a run time permission that a 3rd party app can request for. Can you please remove the same?

My bad. Didn't realise that READ_PRIVILEGED_PHONE_STATE is only for whitelisted apps. I have changed it now.

Any take on this, this permission must be added to PermissionAndroid. It is still not there ACTIVITY_RECOGNITION

@jeswinsimon Do you know how it will become part of the react native package later. Will there be a new candidate release

Closing as not needed anymore:
https://github.com/alanjhughes/react-native/blob/a2d2696e433154b030b4f5206e86d899d12a19cd/packages/react-native/Libraries/PermissionsAndroid/NativePermissionsAndroid.js#L57


Document the new options of /packit test command and job labels

Document the work done in https://github.com/packit/packit-service/pull/2079, https://github.com/packit/packit/pull/1988 and https://github.com/packit/packit-service/pull/2088.

The i--identifier functionality is covered by #659

Since these features are really awesome, what about:

[ ] updating the documentation
[ ] creating a short blog post with a few screenshots

[ ] share to Mastodon

[ ] recording a demo

[ ] share on Mastodon

I would like to also collect some data on how many resources this can save...;)


Microsoft Cloud App Security

Please note MCAS is only part of M365 E5.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bab2c963-204e-0e1d-8b1e-5909f7ef4d7d
Version Independent ID: 3229ebe7-858c-76e2-40c6-c98387f4a685
Content: Top 12 tasks for security teams to support working from home
Content Source: microsoft-365/security/top-security-tasks-for-remote-work.md
Service: o365-seccomp
GitHub Login: @BrendaCarter
Microsoft Alias: bcarter

I too would comment on this. While it may be included in M365 E3 in addition to E5 and certain other addon plans, I would especially think that it is not included in the "all Office 365 enterprise plans." Am I correct on that?

This is fixed. Thank you for the feedback!
https://docs.microsoft.com/en-us/microsoft-365/security/top-security-tasks-for-remote-work?view=o365-worldwide


Added test IMAP001 - Check status of IMAP services

This test performs a simple service status check to add an Info item to the report, same as the POP service status check.

This change is

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

Tests/IMAP001.ps1, line 23 [r1] (raw file):

        try
        {
            #This test won't return StartupType. Need to replace with a WMI query once the WMI framework

Can you file a bug against this to track this?

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

Tests/IMAP001.ps1, line 23 [r1] (raw file):
Previously, bdesmond (Brian Desmond) wrote…
> Can you file a bug against this to track this?
Issue #165 raised to track this.

Comments from Reviewable

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


Can applications detect screen mirroring?

for example I use scrcpy to screen mirror multiple netflix/ youtube premium/or any application with mobile then cast it to a monitor or multiple monitors for multiple people, it is not allowed and is against the rules, but question is could they detect it anyway?
I've tried researching and all I've seen is they can't detect it but they can disable the possibility of being mirrored.
Can applications really detect screen mirroring?, any possible ways applications could do so?

Yes. Appx tyhat implement DRM will not display. See issue 4023..


Timers are not always stopped on disconnect()

https://github.com/nrkno/tv-automation-atem-connection/blob/f35250d6eb46287d3295c27a772b4a8c17c09181/src/lib/atemSocketChild.ts#L74
(In disconnect) The timers should be stopped even if the connection has not been established. The clearing of timers should be moved to above the "if (this._connectionState === ConnectionState.Established)" check. ( or in the else if you want :P )
If I run disconnect() on the instance that has not connected, because I am going to delete the instance, there will be freerunning timers that I have no way to stop.

Let's not move them in to the else, because then we would not clear them out when we did establish a connection ;)

haha, yes. copy to the else :P


[<IP_ADDRESS>] Analyze Response Email

Issue Details
Description
This sub issue is for me to analyze the client's response to our follow-up email #1, to have a better understanding of our Client's POV and also to rectify any ambiguous requirements.
Note: This Issue can only be started IF the Client responded to our Email
Goals
I will analyze and summarize the Client's response. Afterwards I will share this information with my group mates to rectify any issues that my group has with the current requirements.
Success or Completion Criteria
Have a summary of the key points that was gathered by the Client's response.
Allocated Time
2 Days
Start Date: When the Client Respond.
End Date: 2 Days after the Client Respond.

Description: Client generally okay with any proposed NFR as long as it is reasonable. The focus shouldn't be too much on the security but rather the functionality.
Changes to success or completion criteria? Y/N (if yes, describe): Yes
Start Date: 18/09/23, 1800
End Date: 18/09/23, 2359

Issue Comments
Description
Client did not emailed back to us.
Changes to success or completion criteria? y/n (if y, describe)
Yes, changed issue to backlog as this issue is not completed.
Start Date: 19/09/23, 0900
End Date: 19/09/23, 1500


URL's not working correctly

Hi ralsina,
I just build markterm and it works fine, so thanks!
However when clicking on the shown URL's in the terminal, I get a 404, this is because there is a ">" added, when I remove this, I get the correct page.
E.g. https://github.com/charmbracelet/glow>
Regards,
kees

Thanksfor the report, I'll take a look!

They seem to be working for me right now, maybe I fixed it at some point :-D
Could you check with the latest code from main? If that works I will make another release.

I did a git pull origin main to update the source directory, but make
gave an error, so I tried a new clone after removing the old directory, but
with the same result:
markterm on  main is 📦 v0.3.0 via 🔮 v1.13.1
❯ make
shards build -Dstrict_multi_assign -Dno_number_autocast
Resolving dependencies
Fetching https://github.com/ralsina/tartrazine.git
Fetching https://github.com/ralsina/sixteen.git
Fetching https://github.com/icyleaf/markd.git
Fetching https://github.com/chenkovsky/docopt.cr.git
Fetching https://github.com/schovi/baked_file_system.git
Fetching https://github.com/crystal-china/base58.cr.git
Installing markd (0.5.0)
Installing baked_file_system (0.10.0)
Installing base58 (0.1.0 at 2b0564a)
Installing sixteen (0.3.0)
Installing docopt (0.2.0 at 620fce4)
Installing tartrazine (0.6.1)
Writing shard.lock
Building: markterm
Error target markterm failed to compile:
Showing last frame. Use --error-trace for full trace.
In src/terminal.cr:100:30
100 | formatter.format(source, lexer)
^----
Error: expected argument #2 to 'Tartrazine::Ansi#format' to be
Tartrazine::Lexer, not Tartrazine::BaseLexer
Overloads are:

Tartrazine::Ansi#format(text : String, lexer : BaseLexer, outp : IO)
Tartrazine::Ansi#format(text : String, lexer : Lexer)
Tartrazine::Formatter#format(text : String, lexer : Lexer)

make: *** [Makefile:2: build] Error 1
Op ma 26 aug 2024 om 17:34 schreef Roberto Alsina @.***

:

They seem to be working for me right now, maybe I fixed it at some point
:-D
Could you check with the latest code from main? If that works I will make
another release.
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2310498273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKTDLORFUPRKHQMMEZR2DTZTNDHXAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJQGQ4TQMRXGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, pushed a new release of tartrazine and a new commit in markterm, this combination should work :-)

Unfortunately not
markterm on  main is 📦 v0.3.0 via 🔮 v1.13.2 took 2m31s
❯ git pull origin main
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 3 (delta 2), reused 3 (delta 2), pack-reused 0 (from 0)
Unpacking objects: 100% (3/3), 333 bytes | 333.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch            main       -> FETCH_HEAD
f69a123..7d5a142  main       -> origin/main
Updating f69a123..7d5a142
Fast-forward
shard.yml | 1 +
1 file changed, 1 insertion(+)

markterm on  main is 📦 v0.3.0 via 🔮 v1.13.2
❯ make
shards build -Dstrict_multi_assign -Dno_number_autocast
Resolving dependencies
Fetching https://github.com/icyleaf/markd.git
Fetching https://github.com/chenkovsky/docopt.cr.git
Fetching https://github.com/ralsina/tartrazine.git
Fetching https://github.com/ralsina/sixteen.git
Fetching https://github.com/schovi/baked_file_system.git
Fetching https://github.com/crystal-china/base58.cr.git
Unable to satisfy the following requirements:

sixteen (branch main) required by shard.yml
sixteen (0.3.0) required by shard.lock
sixteen (*) required by tartrazine 0.6.1
Failed to resolve dependencies
make: *** [Makefile:2: build] Fout 1

remove your lib/ and shard.lock first

And sorry about all the complications, but hey, you are AFAIK the second person to try this :-D

Removing the shard.lock did it, I could build.
However from the terminal I am using Hyper gave the same problem, I then tried Warp, that worked!
Tried the standard Linux Mint Terminal, that gave errors, also Terminator, appearingly they do not support links
markterm on  main is 📦 v0.3.0 via 🔮 v1.13.2
❯ bin/markterm README.md
Unhandled exception: Missing ENV key: "TERM_PROGRAM" (KeyError)
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/env.cr:57:7 in 'fetch'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/env.cr:22:5 in '[]'
from src/terminal.cr:8:8 in 'supports_links?'
from src/markterm.cr:183:14 in 'text'
from lib/markd/src/markd/renderer.cr:92:13 in 'render'
from src/markterm.cr:203:7 in 'render'
from src/markterm.cr:212:5 in 'to_term:theme:code_theme'
from src/main.cr:21:8 in 'main'
from src/main.cr:32:1 in '__crystal_main'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:118:5 in 'main_user_code'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:104:7 in 'main'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:130:3 in 'main'
from /lib/x86_64-linux-gnu/libc.so.6 in '??'
from /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
from bin/markterm in '_start'
from ???

Ok, the support for html-style links in different terminals is ... spotty?
I tried it in kitty and alacritty, will check on a few of the ones you mentioned.

I tried hyper. Markterm is not even trying to do links in it!
What hyper does is recognize URL patterns but it reads https://foo.com as a link to "https://foo.com>" which is different from any other terminal.
For terminator (and probably other VTE based terminals) it´s a bug in markterm I can fix tonight
You have been really helpful dude!

Fixed in master for terminator (and probbaly for mint too)
For hyper I created an issue because it looks like a bug: https://github.com/vercel/hyper/issues/8031
If you find any other weird behaviour just open another issue.

A shard version issue with tartrazine (I did remove shard.lock)
markterm on  main is 📦 v0.3.0 via 🔮 v1.13.2
❯ git pull origin main
remote: Enumerating objects: 27, done.
remote: Counting objects: 100% (27/27), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 21 (delta 12), reused 20 (delta 11), pack-reused 0 (from 0)
Unpacking objects: 100% (21/21), 3.56 KiB | 145.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch            main       -> FETCH_HEAD
7d5a142..c4617e3  main       -> origin/main
Updating 7d5a142..c4617e3
Fast-forward
.pre-commit-config.yaml | 35 +++++++++++++++++++++++++++++++++++
CHANGELOG.md            |  5 +++++
Makefile                | 16 ++++++++++++++++
README.md               |  9 ++++-----
cliff.toml              | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
shard.yml               |  2 +-
src/terminal.cr         |  2 +-
7 files changed, 141 insertions(+), 7 deletions(-)
create mode 100644 .pre-commit-config.yaml
create mode 100644 CHANGELOG.md
create mode 100644 cliff.toml

markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ make
shards build -Dstrict_multi_assign -Dno_number_autocast
Resolving dependencies
Fetching https://github.com/chenkovsky/docopt.cr.git
Fetching https://github.com/ralsina/tartrazine.git
Fetching https://github.com/ralsina/sixteen.git
Fetching https://github.com/icyleaf/markd.git
Fetching https://github.com/ralsina/baked_file_system.git
Fetching https://github.com/crystal-china/base58.cr.git
Shard "tartrazine" version (0.6.1) doesn't match tag version (0.6.3)
Using markd (0.5.0)
Using baked_file_system (0.10.0 at beb3731)
Using base58 (0.1.0 at 2b0564a)
Installing sixteen (0.3.0 at b133e02)
Using docopt (0.2.0 at 620fce4)
Using tartrazine (0.6.3)
Writing shard.lock
Building: markterm
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2 took 12s
❯ ll bin
totaal 8128
drwxrwxr-x 2 kees kees       0 aug 27 16:39 .
drwxrwxr-x 7 kees kees       0 aug 27 16:38 ..
-rwxrwxr-x 1 kees kees 6420160 aug 27 16:39 markterm
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ bin/markterm README.md
Unhandled exception: Unknown lexer: docopt (Exception)
from lib/tartrazine/src/lexer.cr:30:5 in 'lexer_by_name'
from lib/tartrazine/src/lexer.cr:13:12 in 'lexer'
from src/terminal.cr:99:13 in 'highlight'
from src/markterm.cr:63:16 in 'code_block'
from lib/markd/src/markd/renderer.cr:70:13 in 'render'
from src/markterm.cr:203:7 in 'render'
from src/markterm.cr:212:5 in 'to_term:theme:code_theme'
from src/main.cr:21:8 in 'main'
from src/main.cr:32:1 in '__crystal_main'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:118:5 in 'main_user_code'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:104:7 in 'main'
from /home/kees/.asdf/installs/crystal/1.13.2/share/crystal/src/crystal/main.cr:130:3 in 'main'
from /lib/x86_64-linux-gnu/libc.so.6 in '??'
from /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
from bin/markterm in '_start'
from ???

The warning is harmless.
I'll do a fix for the error tonight.

Version 0.3.2 with the fix is now out.

I did a pull and the Makefile disappeared!
Copied it from an old directory and could build.
The build indeed worked in the Mint Terminal and Terminator with Ctrl+Left mouse button, like you wrote not in Hyper
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ git pull origin main
remote: Enumerating objects: 36, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 28 (delta 17), reused 27 (delta 16), pack-reused 0 (from 0)
Unpacking objects: 100% (28/28), 3.56 KiB | 113.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch            main       -> FETCH_HEAD
c4617e3..8b88a5c  main       -> origin/main
Updating c4617e3..8b88a5c
Fast-forward
.gitignore      |  1 +
CHANGELOG.md    | 22 ++++++++++++++++++++++
Hacefile.yml    | 91 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Makefile        | 23 -----------------------
README.md       |  1 +
build_static.sh |  4 ++--
do_release.sh   | 15 +++++++++++++++
shard.yml       |  6 +++++-
src/terminal.cr |  6 +++++-
9 files changed, 142 insertions(+), 27 deletions(-)
create mode 100644 Hacefile.yml
delete mode 100644 Makefile
create mode 100755 do_release.sh

I am migrating from Makefiles to a different tool. You can always build
using "shards build" anyway. I just updated the build instructions to say
that.
On Tue, Aug 27, 2024 at 6:37 PM Kees @.***> wrote:

I did a pull and the Makefile disappeared!
Copied it from an old directory and could build.
The build indeed worked in the Mint Terminal and Terminator with Ctrl+Left
mouse button, like you wrote not in Hyper
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ git pull origin main
remote: Enumerating objects: 36, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 28 (delta 17), reused 27 (delta 16), pack-reused 0 (from 0)
Unpacking objects: 100% (28/28), 3.56 KiB | 113.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch main -> FETCH_HEAD
c4617e3
https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e
..8b88a5c
https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512
main -> origin/main
Updating c4617e3
https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e
..8b88a5c
https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512
Fast-forward
.gitignore | 1 +
CHANGELOG.md | 22 ++++++++++++++++++++++
Hacefile.yml | 91
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Makefile | 23 -----------------------
README.md | 1 +
build_static.sh | 4 ++--
do_release.sh | 15 +++++++++++++++
shard.yml | 6 +++++-
src/terminal.cr | 6 +++++-
9 files changed, 142 insertions(+), 27 deletions(-)
create mode 100644 Hacefile.yml
delete mode 100644 Makefile
create mode 100755 do_release.sh

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2313623857,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMKZ2KRBCJ6QUH5CURF3ZTTWR3AVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGYZDGOBVG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi Robert,
I did a new git clone and a shards build, that worked fine, only I
still got:
Shard "tartrazine" version (0.6.1) doesn't match tag version (0.6.3)
Should you change the version number in lib/tartrzine/shards.yml from 0.6.1
to 0.6.3?
P.s. I have a feature request: paging
When I page the output throught less, I lose the colors, so if you can
build in some form of paging, that would be great!
Regards,
Kees
Op di 27 aug 2024 om 23:40 schreef Roberto Alsina @.***

:

I am migrating from Makefiles to a different tool. You can always build
using "shards build" anyway. I just updated the build instructions to say
that.
On Tue, Aug 27, 2024 at 6:37 PM Kees @.***> wrote:

I did a pull and the Makefile disappeared!
Copied it from an old directory and could build.
The build indeed worked in the Mint Terminal and Terminator with
Ctrl+Left
mouse button, like you wrote not in Hyper
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ git pull origin main
remote: Enumerating objects: 36, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 28 (delta 17), reused 27 (delta 16), pack-reused 0 (from

Unpacking objects: 100% (28/28), 3.56 KiB | 113.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch main -> FETCH_HEAD
c4617e3
<
https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e>

..8b88a5c
<
https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512>

main -> origin/main
Updating c4617e3
<
https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e>

..8b88a5c
<
https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512>

Fast-forward
.gitignore | 1 +
CHANGELOG.md | 22 ++++++++++++++++++++++
Hacefile.yml | 91

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Makefile | 23 -----------------------
README.md | 1 +
build_static.sh | 4 ++--
do_release.sh | 15 +++++++++++++++
shard.yml | 6 +++++-
src/terminal.cr | 6 +++++-
9 files changed, 142 insertions(+), 27 deletions(-)
create mode 100644 Hacefile.yml
delete mode 100644 Makefile
create mode 100755 do_release.sh
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2313623857,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAAMKZ2KRBCJ6QUH5CURF3ZTTWR3AVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGYZDGOBVG4>

.
You are receiving this because you modified the open/close state.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2313627566,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKTDLIFBZJFSEN2GAIWVVTZTTW3PAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGYZDONJWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

On Wed, Aug 28, 2024 at 4:21 PM Kees @.***> wrote:

Hi Robert,
I did a new git clone and a shards build, that worked fine, only I
still got:
Shard "tartrazine" version (0.6.1) doesn't match tag version (0.6.3)
Should you change the version number in lib/tartrzine/shards.yml from
0.6.1
to 0.6.3?
It's already changed, no worries, it will settle on a future release.

P.s. I have a feature request: paging
When I page the output throught less, I lose the colors, so if you can
build in some form of paging, that would be great!

Using less -R should work but doesn't because of something I can fix.
Next version will work.

Regards,
Kees
Op di 27 aug 2024 om 23:40 schreef Roberto Alsina @.***

:

I am migrating from Makefiles to a different tool. You can always build
using "shards build" anyway. I just updated the build instructions to
say
that.
On Tue, Aug 27, 2024 at 6:37 PM Kees @.***> wrote:

I did a pull and the Makefile disappeared!
Copied it from an old directory and could build.
The build indeed worked in the Mint Terminal and Terminator with
Ctrl+Left
mouse button, like you wrote not in Hyper
markterm on  main is 📦 v0.3.1 via 🔮 v1.13.2
❯ git pull origin main
remote: Enumerating objects: 36, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 28 (delta 17), reused 27 (delta 16), pack-reused 0 (from

Unpacking objects: 100% (28/28), 3.56 KiB | 113.00 KiB/s, done.
From https://github.com/ralsina/markterm

branch main -> FETCH_HEAD
c4617e3
<

https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e>

..8b88a5c
<

https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512>

main -> origin/main
Updating c4617e3
<

https://github.com/ralsina/markterm/commit/c4617e39859d3f349674a7d80a71f51f5d3e661e>

..8b88a5c
<

https://github.com/ralsina/markterm/commit/8b88a5c765487f88927b6068799cbe3183047512>

Fast-forward
.gitignore | 1 +
CHANGELOG.md | 22 ++++++++++++++++++++++
Hacefile.yml | 91

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Makefile | 23 -----------------------
README.md | 1 +
build_static.sh | 4 ++--
do_release.sh | 15 +++++++++++++++
shard.yml | 6 +++++-
src/terminal.cr | 6 +++++-
9 files changed, 142 insertions(+), 27 deletions(-)
create mode 100644 Hacefile.yml
delete mode 100644 Makefile
create mode 100755 do_release.sh
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2313623857,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAAMKZ2KRBCJ6QUH5CURF3ZTTWR3AVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGYZDGOBVG4>

.
You are receiving this because you modified the open/close
state.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2313627566,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AEKTDLIFBZJFSEN2GAIWVVTZTTW3PAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGYZDONJWGY>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2316087415,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMK353SLXWJKW7F6ZPCDZTYPKJAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGA4DONBRGU
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

It was a one-liner and I have automated releases, so just did a quick one now, remember to use less -R so it shows color.

less -R does not show any colors, except the tick-boxes, at my system on
all different terminals
Op wo 28 aug 2024 om 22:35 schreef Roberto Alsina @.***

:

It was a one-liner and I have automated releases, so just did a quick one
now, remember to use less -R so it shows color.
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2316204351,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKTDLOLS7EBD2K33DOP77LZTYX7XAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGIYDIMZVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

It does with the latest version :-)
[image: image.png]
On Fri, Aug 30, 2024 at 6:13 AM Kees @.***> wrote:

less -R does not show any colors, except the tick-boxes, at my system on
all different terminals
Op wo 28 aug 2024 om 22:35 schreef Roberto Alsina @.***

:

It was a one-liner and I have automated releases, so just did a quick
one
now, remember to use less -R so it shows color.
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2316204351,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AEKTDLOLS7EBD2K33DOP77LZTYX7XAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGIYDIMZVGE>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2320600361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMK3TQXO3SMO2EI76KZ3ZUAZTHAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGYYDAMZWGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Yes, see my reply on the Forum.
Thanks!
Met vriendelijke groeten,
Kees Serier
30 aug. 2024 13:07:38 Roberto Alsina @.***>:

It does with the latest version :-)
[image: image.png]
On Fri, Aug 30, 2024 at 6:13 AM Kees @.***> wrote:

less -R does not show any colors, except the tick-boxes, at my system on
all different terminals
Op wo 28 aug 2024 om 22:35 schreef Roberto Alsina @.***

:

It was a one-liner and I have automated releases, so just did a quick
one
now, remember to use less -R so it shows color.
—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2316204351,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AEKTDLOLS7EBD2K33DOP77LZTYX7XAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGIYDIMZVGE>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ralsina/markterm/issues/1#issuecomment-2320600361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMK3TQXO3SMO2EI76KZ3ZUAZTHAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGYYDAMZWGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub[https://github.com/ralsina/markterm/issues/1#issuecomment-2320871094], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AEKTDLN2CAZGBCA5F5BASG3ZUBG7VAVCNFSM6AAAAABL5ZWKHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQHA3TCMBZGQ].
You are receiving this because you authored the thread.
[Tracking afbeelding][https://github.com/notifications/beacon/AEKTDLOLDB5DGEJXRWLZKV3ZUBG7VA5CNFSM6AAAAABL5ZWKHGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUKKWXLM.gif]


Update Query

I should have checked for this before making the previous pull request. Sorry for that!
However, here I have added isAnimationStudio to Studios.
It's useful when you want the studio that animated the anime. Otherwise, sometimes even a licensor is sometimes returned as the first Object in Studio.

Looks good. Thanks for the pull request!


Investigate using readability to get a page's content

https://github.com/mozilla/readability

More context: not only would we like to show reader mode versions of pages, but we'd also like to index the text of pages, and reader mode might make that easier to extract.

dd3ed2e


WIP/RFC: Add template for frontend-app MFEs

Not ready for broad review.
Description:
Re-implement the frontend-template-app repo as a cookiecutter template.
https://github.com/edx/frontend-template-application
Use
Assuming the branch is checked out to ~/src/cookiecutters:
cd ~/src/cookiecutters
make requirements
cookiecutter -o /tmp cookiecutter-frontend-app

Merge checklist:

[ ] All reviewers approved
[x] CI build is green
[ ] Changelog record added
[ ] Documentation updated (not only docstrings)
[ ] Commits are squashed

Post merge:

[ ] Delete working branch (if not needed anymore)

When I've mentioned this possibility (a cookiecutter for fedx) in the past, there was concern about asking fedx people to use Python-native tooling.  Are people on-board with this being the cookiecutter for the future?

Are people on-board with this being the cookiecutter for the future?

This has intentionally not been discussed yet, hence the WIP prefix and the disclaimer:

Not ready for broad review.

I intend to make an impassioned plea :)
Related: https://github.com/edx/edx-cookiecutters/pull/30#discussion_r432638166

you can rebase from master and run the CI checks manually from Actions

To the extent that we have existing code that knows how to fill in templatized strings and directory names and such, I don't see why we should re-invent the wheel.  While I think it's a virtue to keep projects in tooling from their ecosystem, that we already know how to make cookie cutters using this repo seems like a fine reason to add them here.
Put another way, so long as nothing about using Python tooling for project generation is going to preclude us from using tooling from the JavaScript ecosystem in the actual project, seems fine.

A few other thoughts:

there have also been a number of commits to the template application since this PR was created, so it should be updated.
I believe our documentation currently points folks at frontend-template-application when creating new apps.  We should update it.
The old frontend-template-application repo should be DEPR'd, archived, and moved to edx-unsupported if this repo doesn't depend on it for frontend project generation.

This is long out of date, and front end devs don't seem interested in using cookiecutter for this.

Although this pull request is already closed,  I'm still watching it for updates.
There is nothing you have to do. No action is needed from your side.  Thanks.


[BUG] Invalid server address returned by "def ngrok_address"

OS: Windows 11 Insider Preview
Python version: 3.9.6
Steps to reproduce
py hoaxshell.py -ng -i
hoaxshell> payload
...

When creating a tunnel,  t=2022-10-12T21:37:19-0600 lvl=info msg="started tunnel" obj=tunnels name="command_line (http)" addr=http://localhost:8080 url=http://x-x-x-x-x.ngrok.io appears to be a "Valid address"

Then, running the payload on victim's machine, fails because of it (Invalid address)

The problem is, that ngrok's output doesn't have https:// in it,
so, using this regex:
 (url = re.compile(r".*url=(http|https):\/\/(.*)").findall()[0][1])

Doesn't throw an error and runs the reverse shell with the expected behavior

Btw sorry for my typos, i don't speak english natively :p

@t3l3machus connection with ngrok dont work, please fix this

@davidcenoura can you update hoaxshell and try ngrok again? tell me if it works now


HDFS-17642. Add target node list, exclude source node list, and exclude target node list parameters to balancer

Description of PR
Backport https://github.com/apache/hadoop/commit/96572764921706b1fecaf064490457d36d73ea6e
How was this patch tested?
na
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
3m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
35m  9s

branch-3.3 passed

+1 :green_heart:
compile
0m 49s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 33s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 56s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 10s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 54s

branch-3.3 passed

+1 :green_heart:
shadedclient
22m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 16s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
compile
0m 16s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javac
0m 16s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 11s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
The patch fails to run checkstyle in hadoop-hdfs

-1 :x:
mvnsite
0m 17s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javadoc
0m 16s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 15s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
shadedclient
7m 14s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 17s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
asflicense
0m 22s

The patch does not generate ASF License warnings.

75m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 49309e643ce6 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 976ea3c9c6e44c45827a57c47510ba0ac96c7e21

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/1/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
5m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
48m 37s

branch-3.3 passed

+1 :green_heart:
compile
1m 21s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 55s

branch-3.3 passed

+1 :green_heart:
mvnsite
1m 28s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 36s

branch-3.3 passed

+1 :green_heart:
spotbugs
3m 30s

branch-3.3 passed

+1 :green_heart:
shadedclient
36m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m  9s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
compile
1m  8s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javac
1m  8s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 42s

the patch passed

-1 :x:
mvnsite
1m 16s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
javadoc
1m 25s

the patch passed

-1 :x:
spotbugs
1m 11s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
shadedclient
16m 14s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m 14s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

119m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux fa11455585ec 5.15.0-119-generic #129-Ubuntu SMP Fri Aug 2 19:25:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 8b6b3c4876e4456a9d3744fa8589df3c6e232061

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/2/testReport/

Max. process+thread count
551 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/2/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
51m 21s

branch-3.3 passed

+1 :green_heart:
compile
1m 20s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 58s

branch-3.3 passed

+1 :green_heart:
mvnsite
1m 33s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 41s

branch-3.3 passed

+1 :green_heart:
spotbugs
3m 34s

branch-3.3 passed

+1 :green_heart:
shadedclient
37m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 20s

the patch passed

+1 :green_heart:
compile
1m 12s

the patch passed

+1 :green_heart:
javac
1m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 41s

the patch passed

+1 :green_heart:
mvnsite
1m 20s

the patch passed

+1 :green_heart:
javadoc
1m 27s

the patch passed

+1 :green_heart:
spotbugs
3m 21s

the patch passed

+1 :green_heart:
shadedclient
38m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
197m 56s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

348m 15s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.namenode.ha.TestDFSUpgradeWithHA

hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.server.balancer.TestBalancerRPCDelay

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ebf3da57c9f4 5.15.0-119-generic #129-Ubuntu SMP Fri Aug 2 19:25:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 8ddd8fcd29764944b740f0d4f85c48795aac2561

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/3/testReport/

Max. process+thread count
4056 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/3/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
35m 28s

branch-3.3 passed

+1 :green_heart:
compile
0m 47s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 33s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 55s

branch-3.3 passed

+1 :green_heart:
javadoc
1m  8s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 50s

branch-3.3 passed

+1 :green_heart:
shadedclient
23m  0s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 50s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 48s

the patch passed

+1 :green_heart:
javadoc
0m 58s

the patch passed

+1 :green_heart:
spotbugs
1m 51s

the patch passed

+1 :green_heart:
shadedclient
22m 22s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
173m 20s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

264m 56s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.protocol.TestBlockListAsLongs

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 3420f8d8dfad 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 4e34732fc66be5924b96172bc2ae323f1ba231ca

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/4/testReport/

Max. process+thread count
4320 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/4/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 19s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
35m  1s

branch-3.3 passed

+1 :green_heart:
compile
0m 51s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 34s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 55s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 10s

branch-3.3 passed

+1 :green_heart:
spotbugs
2m  0s

branch-3.3 passed

+1 :green_heart:
shadedclient
22m 37s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 47s

the patch passed

+1 :green_heart:
compile
0m 43s

the patch passed

+1 :green_heart:
javac
0m 43s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 22s

the patch passed

+1 :green_heart:
mvnsite
0m 47s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed

+1 :green_heart:
spotbugs
1m 51s

the patch passed

+1 :green_heart:
shadedclient
22m 28s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
174m 45s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 32s

The patch does not generate ASF License warnings.

265m 38s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.server.datanode.TestDataNodeMetrics

hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 602e92443b4e 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / fd170344f4c0ceeff3bf5487701d78b5e69d7b75

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/5/testReport/

Max. process+thread count
3725 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/5/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
4m  2s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
34m 25s

branch-3.3 passed

+1 :green_heart:
compile
0m 49s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 33s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 54s

branch-3.3 passed

+1 :green_heart:
javadoc
1m  6s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 53s

branch-3.3 passed

+1 :green_heart:
shadedclient
22m 38s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 25s

the patch passed

+1 :green_heart:
mvnsite
0m 50s

the patch passed

+1 :green_heart:
javadoc
0m 57s

the patch passed

+1 :green_heart:
spotbugs
1m 57s

the patch passed

+1 :green_heart:
shadedclient
22m 29s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
176m 10s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

270m  9s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics

hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 84152662ed43 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / fe514bc84bbadf851d3a296d70efcffe179eb9a5

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/6/testReport/

Max. process+thread count
4330 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/6/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 23s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
34m  6s

branch-3.3 passed

+1 :green_heart:
compile
0m 50s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 34s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 54s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 11s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 52s

branch-3.3 passed

+1 :green_heart:
shadedclient
22m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed

+1 :green_heart:
javac
0m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 49s

the patch passed

+1 :green_heart:
javadoc
0m 56s

the patch passed

+1 :green_heart:
spotbugs
1m 49s

the patch passed

+1 :green_heart:
shadedclient
22m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
175m 36s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

265m  6s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d93c783bceec 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / f4073403a7c0990c2e9fa64beaaf851890110fc3

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/7/testReport/

Max. process+thread count
4752 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/7/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m 16s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
29m 17s

branch-3.3 passed

-1 :x:
compile
3m 35s
/branch-compile-root.txt
root in branch-3.3 failed.

+1 :green_heart:
checkstyle
1m 36s

branch-3.3 passed

-1 :x:
mvnsite
0m 25s
/branch-mvnsite-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
mvnsite
0m 12s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
mvnsite
0m 27s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
mvnsite
0m 24s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
javadoc
0m 16s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
javadoc
0m 24s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

+0 :ok:
spotbugs
0m 21s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

-1 :x:
shadedclient
20m  6s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
compile
0m 21s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
0m 21s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/buildtool-patch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvnsite
0m 21s
/patch-mvnsite-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvnsite
0m 14s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
javadoc
0m 23s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

+1 :green_heart:
shadedclient
7m 34s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 22s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
unit
0m 26s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
unit
0m 10s
/patch-unit-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

+0 :ok:
asflicense
0m 22s

ASF License check generated no output?

87m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 71e85e4b4201 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 6952623a229c8faf2bf8ecd8c1e1438af395f317

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/8/testReport/

Max. process+thread count
179 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/8/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for branch

-1 :x:
mvninstall
0m 20s
/branch-mvninstall-root.txt
root in branch-3.3 failed.

-1 :x:
compile
0m 21s
/branch-compile-root.txt
root in branch-3.3 failed.

-0 :warning:
checkstyle
0m 18s
/buildtool-branch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 20s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
mvnsite
0m 20s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
mvnsite
0m 20s
/branch-mvnsite-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
mvnsite
0m 20s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

-1 :x:
javadoc
0m 20s
/branch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
javadoc
0m 20s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
javadoc
0m 20s
/branch-javadoc-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
javadoc
0m 20s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

-1 :x:
spotbugs
0m 21s
/branch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
spotbugs
0m 32s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
spotbugs
0m  7s
/branch-spotbugs-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
spotbugs
0m 20s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

+1 :green_heart:
shadedclient
4m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 20s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvninstall
0m 20s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvninstall
0m 20s
/patch-mvninstall-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvninstall
0m 20s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
compile
0m 20s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
0m 20s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/buildtool-patch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 20s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
spotbugs
0m 20s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

+1 :green_heart:
shadedclient
6m 17s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 21s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
unit
0m 20s
/patch-unit-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
unit
0m 17s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

+0 :ok:
asflicense
0m 22s

ASF License check generated no output?

17m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux cfa2d2faf382 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / b890a557310b45209a6b729274ce103816fe9a0f

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/9/testReport/

Max. process+thread count
51 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/9/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for branch

-1 :x:
mvninstall
0m 20s
/branch-mvninstall-root.txt
root in branch-3.3 failed.

-1 :x:
compile
0m 22s
/branch-compile-root.txt
root in branch-3.3 failed.

-0 :warning:
checkstyle
0m 19s
/buildtool-branch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 22s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
mvnsite
0m 21s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
mvnsite
0m 21s
/branch-mvnsite-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
mvnsite
0m 21s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

-1 :x:
spotbugs
0m 23s
/branch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in branch-3.3 failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in branch-3.3 failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-project.txt
hadoop-project in branch-3.3 failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in branch-3.3 failed.

+1 :green_heart:
shadedclient
5m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvninstall
0m 21s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvninstall
0m 21s
/patch-mvninstall-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvninstall
0m 21s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
compile
0m 21s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
0m 21s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 19s
/buildtool-patch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
shadedclient
6m 12s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 21s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
unit
0m 21s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
unit
0m 20s
/patch-unit-hadoop-project.txt
hadoop-project in the patch failed.

-1 :x:
unit
0m 21s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

+0 :ok:
asflicense
0m 21s

ASF License check generated no output?

18m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/10/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 28d5032741f4 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 2543b6c58154823385f2097def9304dae8c12338

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/10/testReport/

Max. process+thread count
46 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/10/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m  7s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 31s

branch-3.3 passed

+1 :green_heart:
compile
11m 31s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 34s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 18s

branch-3.3 passed

+1 :green_heart:
javadoc
2m 48s

branch-3.3 passed

+0 :ok:
spotbugs
0m 33s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
22m 10s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  2s

the patch passed

+1 :green_heart:
compile
11m  0s

the patch passed

+1 :green_heart:
javac
11m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 29s

the patch passed

+1 :green_heart:
mvnsite
3m 16s

the patch passed

+1 :green_heart:
javadoc
2m 48s

the patch passed

+0 :ok:
spotbugs
0m 26s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
22m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 25s

hadoop-project in the patch passed.

+1 :green_heart:
unit
15m 28s

hadoop-common in the patch passed.

-1 :x:
unit
170m 36s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
1m  1s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

322m  9s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 833bd510a185 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / e3d149d74740ee487e9c5a14628dbd080df04163

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/11/testReport/

Max. process+thread count
3803 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7152/11/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


[DO NOT MERGE] fix: Use one way to get subject DID

This is a workaround to provide manual labeling

looks good to me MERGE IT

No branch protections - closing.