No audio in rtsp stream on WebRTC Camera Card

As far as I understand audio and video should both be active when using the WebRTC Camera Card as both media types are standard, but there is no audio. When I open the stream in VLC I have both audio and video.
My config is very simple:
WebRTC Camera Card configuration:
type: custom:webrtc-camera
url: rtsp://user:pass@192.168.x.x:554/h264Preview_01_main

Also tried using the go2rtc.yaml route:
streams:
  reo_doorbell: rtsp://user:pass@192.168.x.x:554/h264Preview_01_main

with WebRTC Camera Card configuration:
type: custom:webrtc-camera
streams:
  - url: reo_doorbell
    media: video,audio

What am I missing?

https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#codecs-madness

Sweet, it works now. I'll document what I did here for other to see.
According to VLC in my stream AAC is used for audio, this can't be changed unfortunately. As far as I understand now audio doesn't work because this codec is not supported by 'Desktop Edge' which is what I'm using, so I need to transcode.
Changed my go2rtc.yaml to this:
streams:
  reo_doorbell:
    - rtsp://user:pass@192.168.x.x:554/h264Preview_01_main
    - ffmpeg:rtsp://user:pass@192.168.x.x:554/h264Preview_01_main#audio=opus

After restarting HA, audio works

AAC should works via MSE technology in all browsers

I had no luck with mse. Only a frozen image or completely black. Only webrtc works for me.

This is because you haven't read carefully
https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#source-rtsp
Sometimes Reolink RTSP is broken trash. MSE can't handle it.

I actually did see that, it doesn't mention anything specific about Reolink and MSE, just that RTSP on Reolink is unreliable, which we can agree on.
I'll sum up my experience:

RTSP HD + MSE works in HA app on my iPad, with flaky AAC sound

RTSP HD + MSE doesn't work in Edge on my Windows desktop. No sound, no video

RTSP HD + RTC works fine on both, but without sound.

RTSP HD + RTC works with sound on Edge, when transcoded opus (only one I tried)

RTMP with HD stream works, but very bad framerate

RTMP with SD stream works fine

All with same Reolink cam (Doorbell cam Wifi)

MSE can't handle broken stream from any camera brand

MSE can't handle broken stream from any camera brand.
I don't know why you have problems via MSE on edge. This can be because H265. But if RTC works for you, this mean you have H264.
RTMP also has problems on Reolink cameras. Better to use HTTP FLV.

Switching to Https/FLV with Opus audio did the trick for me with mode set to webrtc in webrtc custom card. Works flawlessly.

hello, I am desperate now. tried many different things (Home assistant addons). I hope someone could guide what I am missing. I have "Reolink doorbell wifi" which I was thinking to use without reolink app but with home assistant app.
Idealy I am aiming to use Frigate (sepparate proxmox container) with built-in go2rtc to capture streams and in Home Assistant (sepparate proxmox VM) use re-streams of those from Frigate.
In frigate I am able to setup that doorbell with combined stream of rtsp + flp (over https:1935) but when using frigate card I am unable to get two way audio working. Since this setup was having more layers for debugging I decided to go simple and at least establish reolink camera working in HA separately.
Here is my current setup.

Installed WebRTC Camera and configured with 'blank' go2rtc setup (self deployed)
on lovelace dashboard I have this config:

type: custom:webrtc-camera
streams:
  - url: rtsp://user:pass@IP:554/h264Preview_01_sub
    mode: webrtc
    media: video,audio,microphone

with this setup when trying to view the stream I am able to send audio via microphone but I cannot hear audio (probably due to webrtc is not supporting AAC).
if i switch to mode: mse then i am able to get audio but then microphone is not sending any audio to the doorbell.
is there a way to combine these two modes into one?
and of course if someone would be so kind to guide with the frigate setup that would be even better but I would be happy with any solution

@MaBeniu you need to open go2rtc (self deployed) WebUI. And add to config new stream with two sources - rtsp and ffmpeg with transcoding audio to opus. And use this source as url in the custom card.

When you using Frigate - all go2rtc config should be inside Frigate config.
Two way for Reolink should supported without any problems.

@MaBeniu could you share your go2rtc config and WebRTC Camera card? im in the same boat

here is my setup.
first you need to setup WebRTC Camera integration leaving blank input for go2rtc reference. make full reboot of HA.
next go2rtc.yaml (you can create it and modify via http://[Homeassistant IP]:1984 address
streams:
  reo_doorbell:
    - rtsp://user:pass@cameraIP:554/Preview_01_sub
    - ffmpeg:rtsp://user:pass@cameraIP:554/Preview_01_sub#audio=opus

make sure you keep audio recording on in the doorbell itself.
also accessing doorbell you have to use https address or in chrome browser you can set 'falgs' exception to allow in http. but in any case for homeassistant app you would need https anyway.
here is webrtc camera card yaml
type: custom:webrtc-camera
url: reo_doorbell
mode: webrtc
media: video,audio,microphone

the only difference to what you can find mostly in other threads people combine one rtsp stream + Https/FLV with Opus audio stream which in my case actually didn't worked. not sure why.

@MaBeniu your example has two connections to camera. This example will have only one:
streams:
  reo_doorbell:
    - rtsp://user:pass@cameraIP:554/Preview_01_sub
    - ffmpeg:reo_doorbell#audio=opus

so the above setup works with no problem just it makes additional connection to the camera if you use frigate in parallel for recordings and object detection. my bad was that I tried many different scenarios inconsistently which led I left some settings meant for different use cases.
so to sum up some setups i update and finally made it work on WebRTC card with restream from go2rtc in Frigate .
What I did I am not expert to say if that was the key but it helped for me so sorry if something doesnt make sense, just sharing my experience.

I removed tickbox in home assistant frigate integration configuration - "Enable WebRTC for camera streams" which I guess is meant for frigate card and maybe it conflicts if you want to use WebRTC Card integration to frigate streams.
make sure in frigate go2rtc config you have

  webrtc:
    candidates:
      - [homeassistantlocalIP]:8555
      - stun:8555

in my setup frigate runs on separate proxmox container using docker compose so I also made sure port openings are in place in frigate docker compose:

  ports:
      - "5000:5000"
      - "1984:1984"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp

with this setup I use WebRTC Card in homeassistant dashboard card with this yaml

type: custom:webrtc-camera
url: [camera name **from frigate go2rtc config**]
mode: webrtc
media: video,audio,microphone

as in some other threads mentioned home router port binding for webrtc port I am not using.
in go2rtc docs it was mentioned it doesnt work with cloudflare, while in my case I use homeassistant app with remote access that is setup with cloudflare so it does work for me.
last but super important when WebRTC Card + frigate configuration - homeassistant WebRTC card configuration has to be using go2rtc of frigate server which is done by providing http://[frigateIP]:1984 while configuring.
and of course full reboot of all components is required after all changes are in place.

I will continue testing flv stream maybe I will manage to make it work as rtsp stream is not so stable.
p.s. and for dummies also make sure to turn on the doorbell :D :D

thank you for configs
I do have two way audio working on Doorbell_main which runs video via rtsp, but no two way audio on Doorbell_main_flv. Audio coming from camera works in both streams, but audio to the camera only on rtsp.
Is it to be expected? or can I modify config to make it work?
streams:
    Doorbell_main:
        - rtsp://admin:qwert1234@<IP_ADDRESS>:554/h264Preview_01_main
        - ffmpeg:rtsp://admin:qwert1234@<IP_ADDRESS>:554/h264Preview_01_main#audio=opus
    Doorbell_main_flv:
        - http://<IP_ADDRESS>/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=qwert1234
        - ffmpeg:rtsp://admin:qwert1234@<IP_ADDRESS>:554/h264Preview_01_main#audio=opus


Experimental preprocessor using existing parsers

In the past day, I've put a small proof of concept of a refactor of this project to reuse the Svelte & Windi parsers. You can find it here grenierdev/svelte-windicss-preprocess.

stays

becomes

becomes

                    ^---------^------------------------- intact, author will need to add style
                                                         manually for all possible values of {a}
                                                         and {b}

becomes

                                                 ^------ intact, author will need to add style
                                                         manually for all possible values of {b}

<div class={`px-3 py-${c + 2 - 10} sm:(text-gray-${d} text-sm font-medium)`} />
becomes
<div class={`px-3 py-${c + 2 - 10} sm:text-gray-${d} sm:text-sm sm:font-medium`} />
                     ^--------------------------^------- intact, author will need to add style
                                                         manually for all possible values of
                                                         {c + 2 - 10} and {d}

All of which could be passed to something described in https://github.com/windicss/svelte-windicss-preprocess/issues/35#issuecomment-790940288 (using WindiCSS at runtime).
Still just a proof of concept and does not yet cover all the features, namely the class directive.
Could be worth discussing?

can you look at changes for v3.0.0. We are currently working on a rewrite of the parser! We can discuss your changes too.

Will sure look into the v3.0.0-beta.1 over the weekend!
If you look at my branch, it's a complete refactor in less than 100 lines. It reuses the built-in parsers of Svelte and WindiCSS to preprocess the markup. It's a simple design that seems to work and is less of a headache to maintain than regex search patterns.

I quickly scanned your Prototyp. I really like some implements but something might not work with everything we would like to support. So I suggest we will combine both experimental ideas and make something good. Can you say any about performance of the svelte ast parsing already?
I would only go this way if it is a super big performance improvement as it misses some features we are implementing with regex! Let discuss this further.

I've wrap the whole markup function with console.time/timeEnd.
On my simple project, here are the timings
client\views\Empty.svelte: 6.251ms
client\App.svelte: 14.022ms
client\Workbench.svelte: 4.612ms
client\Layout.svelte: 30.093ms

I did the same with v3.0.0-beta.1
client\views\Empty.svelte: 1.976ms
client\App.svelte: 8.723ms
client\Layout.svelte: 10.923ms

Regex will always be faster than parsing into an AST. I believe the tradeoff is worth it as regex can prove cumbersome to maintain.

We have to evaluate all trade-offs in detail, before doing changes in that scale. I will look into your prototype in more detail during the weekend. I still think a combination of both would be the best fit here, but I will check!

I worked a bit more on my branch. Added a few sanity tests but everything seems to be 100% compatible with the features supported by WindiCSS.
  Preprocessor
    ✓ warns if ignored class name sound like tailwind
    ✓ alters class attr and generates style tag
    ✓ alters class attr, generates style tag, leaves script untouched
    ✓ alters class attr, alters existing style tag
    ✓ alters class attr, alters existing style tag and leaves script untouched
    ✓ compiles @apply directive within style tag
    ✓ compiles @variants directive within style tag
    ✓ compiles @screen directive within style tag
    ✓ compiles nested directives within style tag

  WindiCSS
    ✓ basics
    ✓ ignores custom class
    ✓ ignores and unfolds custom class within group
    ✓ ignores mustache element
    ✓ ignores and unfolds mustache's element within group
    ✓ ignores template literal's expression
    ✓ ignores and unfolds template literal's expression within group

  16 passing (140ms)

Also added a test to figure out if the ignored class names contain Tailwind classes or not. When class names aren't recognized by WindiCSS, they are most probably user-defined or dynamic class names. In the latter case, I'd like to be warned that dynamic classes aren't supported and to use a runtime solution of WindiCSS.
To be fair, I don't think that this project should handle dynamic class names at all. This is a preprocessor and shouldn't add anything to the runtime of the app of the user without them knowing. Users should be free to choose the right solution for their needs, be it a Svelte Action like @munxar suggested or simply interpret class names in their script tag with WindiCSS. In either case, users will be knowingly adding a beefy 500kb dependency to their app.

@grenierdev thanks for your update. I found some time to look at it, and it matches all you said. I have to take some more time to evaluate on it!
But my biggest concern for now is that it is using the svelte AST..
This would drop support for this feature (https://windicss.netlify.app/guide/svelte.html#variant-attributes)
I know it is not native HTML, but it is a feature we do currently support, so I guess, the AST will not get this in its css parse.
Am I missing something here?
I still think we might be able to get the parser and this project down to around 150LOC with regex and the rewrite started in v3.0.0-beta.01, which will support all features currently available, and will be more open for the future.
I have not decided yet!

The AST phase is only building an abstract syntax tree from the markup. It won't validate the markup against a spec like HTML5. So custom attributes like sm="...", hover="..." or dark="..." are present in the AST. I'll try to piece something tomorrow that combines these variant attributes into the class.
Meanwhile, tonight I added a feature that prevents WindiCSS to override style in a Svelte component. If I place a style named .container { ... } in a component's stylesheet, WindiCSS treats it like if it's .container from Tailwind and compiles it as .windi-xxxxx. So now, every style defined in a component's stylesheet gets excluded from the preprocessor. It's left to the user to @apply container within the .container style in the component's stylesheet.

yeah they are present, but won't be interpreted in ast.css correct?
I will take a look later on, to check it more in detail and check for features as I said before

Got the chance to add support for variant attributes.
https://github.com/grenierdev/svelte-windicss-preprocess/blob/ceb2e1d6e636bf6f727a7e60aa3280c3da4cdd32/src/preprocessor.spec.ts#L220-L242
The next feature would be the class directive.

Class directives are now supported.

becomes
<div class={`windi-1pemjf1 ${true ? 'font-bold' : ''} ${func() ? 'text-indigo-600' : ''}`}   />

Encountered a bug with WindiCSS compiler discarding complex template literal element like text-gray-${func()}. Will check on that later this week.

thanks for the update. We have decided in the contributors team, that we will not adapt svelte AST. However, if that is good with you, we will adapt some of your ideas, in the new v3 parser

yeah thanks.  I will close up with an explanation behind our desicion in some days..


Meeting Search calls do not show in Reports section of the UI

Description

Meeting search calls sometimes show in the metrics chart portion of the reporting UI. In my testing, they work for the Capital Area, and do not work for North Dade Area.
Meeting search calls never show in the datatable portion of the UI. This is reproducible with both Capital Area and North Dade areas.

Reproduction
Capital Area
When someone calls the Capital Area number<PHONE_NUMBER>) and performs a meeting search:

I see hits to status.php in the logs, indicating status callbacks are configured.
I see some entires in the records table.
I see Meeting Search data in the metrics chart.
I DO NOT see Meeting Search data in the datatable.

North Dade Area
When someone calls the North Dade Area number<PHONE_NUMBER>) and performs a meeting search:

I see hits to status.php in the logs, indicating status callbacks are configured.
I see some entires in the records table.
I DO NOT see Meeting Search data in the metrics chart.
I DO NOT see Meeting Search data in the datatable.

ack... investigating.

I could repro.  The data is there, it’s a bug with the report query.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Danny Gershman @.>
Sent: Saturday, June 11, 2022 8:38:07 PM
To: bmlt-enabled/yap @.>
Cc: Danny Gershman @.>; Your activity @.>
Subject: Re: [bmlt-enabled/yap] BUG: Meeting Search calls do not show in Reports section of the UI (Issue #594)
ack... investigating.
—
Reply to this email directly, view it on GitHubhttps://github.com/bmlt-enabled/yap/issues/594#issuecomment-1153030697, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOD3O3LHKTHA72LAXAENVLVOUWO7ANCNFSM5YO3DCWQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

still refactoring

thx u 4 ur service

Fixed in yap 4.1.0-beta2

I still can't get meeting search calls to show up for the capital area number on the sezf server.
Number is 1-877-590-6262.
Call webhook is https://bmlt.sezf.org/zonal-yap/?override_service_body_id=95&override_sms_combine=true&override_jft_option=false.
Call status changes url is https://bmlt.sezf.org/zonal-yap/status.php?override_service_body_id=95&override_sms_combine=true.

You can disregard previous comment, it looks like SMS and Call meeting searches are now showing up in the UI

completed, released in 4.1.0


namespacing of Structured Annotation data?

I'm having a little trouble with how StructuredAnnotations are intended to be validated.
We have ome-tiffs with large Structured Annotation blocks that essentially are inlining other "arbitrary" xml as XMLAnnotations.  (In this case, Zeiss CZI metadata has been stashed in there...please do not judge just yet!)
I can call from_xml and the xml properly is converted to ome-types without error.   If I then call to_xml and from_xml again, I get an exception because of this:
Traceback (most recent call last):
  File "C:\Users\danielt\AppData\Local\Continuum\anaconda3\envs\cellbrowser-tools\lib\site-packages\xmlschema\validators\global_maps.py", line 127, in lookup
    obj = global_map[qname]
KeyError: '{http://www.openmicroscopy.org/Schemas/OME/2016-06}ImageDocument'

where I believe the OME schema namespace was added by ome-types.. Does that sound like what is going on here?
I'm honestly not sure whether the initial xml should fail to validate or not, but I believe the intent of the schema is to allow arbitrary (non-OME-schema) xml inside structured XMLannotations.

might need some input from @jmuhlich on this one.  i'm not sure but the issue might be right here where we use the OME namespace when encoding StructuredAnnotations?

I believe the intent of the schema is to allow arbitrary (non-OME-schema) xml inside structured XMLannotations.

totally agree.  we probably need to provide a hook for you to provide your custom namespaces when encoding back to xml... @jmuhlich?

I guess this is related to #66 , just adding a reference here.

I guess this is related to #66 , just adding a reference here.

@toloudis, can you maybe extract some XML for me use to repeat this issue?

Just pinging to say I haven't forgotten and hope to revisit this week.  I will try to repro and if I can, I'll put some xml here.

This repo  https://github.com/AllenCell/quilt-data-access-tutorials/tree/feature/test_validation  (specifically the branch feature/test_validation ) has some code in the Tutorial 3 notebook that shows a bit of trouble with Structured Annotations.  In the first test file downloaded, I get a validation error with respect to a structured annotation that has an Experiment node inside it.

Great thanks!  Will be helpful to have for testing

I think this can be closed.  I just ran from_tiff on every file in the dataset listed above, and they all generate OME objects without error (even though many of them are ill-formed)


Auto publishing feature

The audience should be aware of the auto publishing feature in the same article. I am not aware of the auto publishing feature because this feature is mentioned in another article, and there is no link to that article.
I am a MSFT employee, my alias is benyip. Please let me know if you have any questions

@BenoityipMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


Changing the font size causes the label's text to stretch out or compress

Originally, the label looks like this:

After setting the font size using:
label.font = UIFont.systemFontOfSize(16)

It becomes this:

The spacing between the characters are all messed up.

Fixed in https://github.com/lexrus/LTMorphingLabel/commit/624651164c63c61e16c810a856ef2f4f4bb8889a

Thanks :)


Key standardization and LineChart key bug fix

This pull request addressed two things.

LineChart was passing only the series.name as the key to each DataSeries rather than passing series.name + idx. This was causing possible duplicate key issues and has been fixed.
The value of key throughout the code was inconsistently generated (sometimes series.name, sometimes idx, and sometimes series.name + idx). Where possible, the key value has been standardized to series.name + idx

I also added two PropTypes checks, though many, many more are missing. I will add them in when I get a chance.

Not sure why the build failed - I double checked the code and it doesn't seem there are any changes that would cause a test failure. Is there any way to makes the tests more verbose?

Thanks for your PR.   I agree that we've used several different ways of generating keys and it would be nice to standardize whenever possible.  I was planning to standardize to just idx, which is guaranteed to be unique within the collection of child components (which is all the key needs to be).  The reason we need seriesName + '-' + idx in the id property is because we need those id's to be globally unique for the voronoi overlay (and we have to use a different prop other than key because React makes the key prop an essentially private property).
Your bar chart test failed because there are no default labels set yet you're depending on those labels to be present for the key.  Since they're undefined, when you concatenate that with an index, you get NaN, which is presumably not a valid key (and so the component fails to render).  The quick fix for that is just to use the index for the key, as I describe above.
Minor suggestion: could you leave the seriesName variable name as it is now in the child components?  I'd prefer to encourage more descriptive variable names whenever possible (in the parent component, it's clear what name refers to since it's a property of the series object).
And thanks for adding the missing prop types, I'm sure we're missing quite a few...

Ah, that makes sense regarding the BarChart test, thanks for the explanation. And sure, happy to use seriesName and just idx. I'll update soon.

lgtm


KAFKA-6560: Add docs for KIP-261

This should be part of the original PR but missing.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@bbejeck @dguy @vvcephei

Special note to @dguy: while writing the docs I realized the 1.1 upgrade section was not correct since we added a new function in readonly window store, and may affect users who have customized implementations.
Please include this PR in the 1.1 generated docs in the next RC.

Updated to address comments.

Also cherry-picked to 1.1 , cc @dguy


incomplete doc for Asset-Transfer-Basic as an external service

https://github.com/hyperledger/fabric-samples/blob/main/asset-transfer-basic/chaincode-external/README.md
when run this command, getting error
setGlobals 1
peer lifecycle chaincode install ../asset-transfer-basic/chaincode-external/asset-transfer-basic-external.tgz

Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: platform builder failed: Failed to generate a Dockerfile: Unknown chaincodeType: EXTERNAL

@hbakhtiyor
Based on the error, it seems that the expected external chaincode builder does not work correctly, and instead, the default internal  chaincode builder is being used.
You need to set up a Fabric network with the external-sample-builder according to the steps in the doc, and it's possible that this hasn't been done correctly.
Could you please recheck and rerun the instructions in Setting up the external builder and launcher?
This could resolve the issue.

@satota2 @hbakhtiyor
I am trying to implement the external chaincode builder using Asset-Transfer-Basic as an external service but I get the same error when I execute:
peer lifecycle chaincode install ../asset-transfer-basic/chaincode-external/asset-transfer-basic-external.tgz
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: platform builder failed: Failed to generate a Dockerfile: Unknown chaincodeType: EXTERNAL
I have follow step by step the tutorial guide but I am not able to implement the external builder

@juncaluriol
I've confirmed the situation.
It seems that fabric-samples/config/core.yaml is currently not being read by the Docker peer containers in the test-network. Please modify fabric-samples/test-network/compose/docker/peercfg/core.yaml instead.
As discussed in the following mailing list exchange, starting with Fabric v2.5, you need to change the scripts (detect, build, release, run) to start with #!/bin/bash instead of #!/bin/sh. Please modify files in chaincode-external/sampleBuilder/bin.
https://lists.hyperledger.org/g/fabric/topic/104464487
Please try these modifications and retry.
Additionally, I plan to submit a patch to fix the bugs in the procedures I've identified above.


Pretrained model examples?

I'm very interested in this paper, but before I dedicate a night of GPU time to this technique, I'd like to play around with a premade checkpoint. Would you consider sharing some of the checkpoints made from the example datasets?

Certainly. It'll take me about a week since I'm away from my computer right now, but I'll make sure to share some checkpoints once I'm back.


Custom Binarization of data

Description
I am very excited to use your tools on my data, and I have been playing with the Napari plug in with great success on my calcium data. The one issue I am having is that when I start using arcos4py tools, your methods for data binarization don't work great for me, and I would like to use my own scheme to binarize the data. Is it possible to directly pass the ARCOS initiation function with the binarization column premade? Eg.
measurement column is Calcium, binarization column is Calcium.bin
ts = ARCOS(df_filter_track, ["x", "y"], 'timepoint','track_id', 'Calcium','Calcium.bin')
I have been following the example from here:
https://arcos.gitbook.io/home/example-use-cases/detecting-collective-signalling-events-in-epithelial-cells
I am also having difficulty understanding how the binarization methods work. I can input data with long tracks (>50 timeframes) and the same cell ID is given back with only ~7 timepoints and different x and y positions etc. Is there some shuffling of the track_id when tracking collective events?

Hi, and first great that you are enjoying using the packages!
Sure, there are two ways you can pass your custom binarization column to arcos.

the ARCOS class has a class attribute "bin_col". You can construct the class as usual. The constructor creates the value for this class attribute by adding a ".bin" suffix to the name of the measurement column. So if your measurement column is "Calcium" and you have a "Calcium.bin" in your data you should be able to skip the binarization method entirely. Alternatively, you could create the arcos object with:
ts = ARCOS(df_filter_track, ["x", "y"], 'timepoint','track_id', 'Calcium') and then
ts.bin_meas = "your_binary_column"
and again skipping the binarization step.

The easier option for you however would be to directly use what the "trackCollev" method calls.

from arcos4py.tools import detectCollev
ts = detectCollev(args)
events_df = ts.run()

this allows you to directly pass in the binarized data to arcos.
here would be the documentation for this: https://bgraedel.github.io/arcos4py/api/#arcos4py.tools.detect_events
It is still very odd that there is some reshuffling with the tracked data. It sounds like a bug on my side. On which package version are you? I did fix some binarization issues with the latest release (0.1.4).
If you have this version installed and the issue persists could you (if that is ok with you) send me your data as a CSV so I could have a closer look at what might be going wrong?

Thanks for the quick reply @bgraedel.
I just plugged my binarization scheme into the ARCOS algorithm using method 1. It works beautifully, and I am excited to get to more of the downstream analysis as I get this working more.
The second issue I think was my fault. I was misunderstanding the output of the ARCOS after detectCollev was run. I will let you know if I run into any more issues, but right now things seem to be working really well.
Thank you for your guidance, I will let you know if I run into any more issues!


[controller][server] Reduce logging in controller, server

Reduce exception logging in push status collector in controller and SST file ingestion in Server

For stores without pushstatus system store, controller logs get flooded with full excception stacktrace. Also in server most of the time RMD file sst writer are empty, so do not print any warn log for it.
How was this PR tested?

Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

But today, every user store should have push status system store. If it is not, then it is not expected.

But today, every user store should have push status system store. If it is not, then it is not expected.

For oms stores it was not created and was flooding the controller logs. Also it will print the exception message instead of full stacktrace

But today, every user store should have push status system store. If it is not, then it is not expected.

For oms stores it was not created and was flooding the controller logs. Also it will print the exception message instead of full stacktrace

Ok, as long as e.getMessage() itself won't throw it should be fine..


C: hadoop-project hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-auth-examples hadoop-common-project/hadoop-common hadoop-common-project/hadoop-nfs hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs hadoop-hdfs-project/hadoop-hdfs-nfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-mapreduce-project/hadoop-mapreduce-client hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-server/hadoop-yarn-server-timelineservice-hbase-server-2 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-documentstore hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-client-modules/hadoop-client hadoop-tools/hadoop-azure hadoop-tools/hadoop-resourceestimator hadoop-client-modules/hadoop-client-runtime hadoop-client-modules/hadoop-client-check-invariants hadoop-client-modules/hadoop-client-minicluster hadoop-client-modules/hadoop-client-check-test-invariants hadoop-client-modules/hadoop-client-integration-tests hadoop-cloud-storage-project/hadoop-huaweicloud hadoop-cloud-storage-project/hadoop-cloud-storage U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7019/25/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2 shellcheck=0.7.0

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

This message was automatically generated.

@steveloughran
Thank you very much for reviewing this PR! Based on the recent compilation results, we have largely resolved the unit test errors, sputbug, and compilation issues (the latest issue seems unrelated to our changes. I appreciate your suggestions! I'm preparing a new version that will incorporate your feedback, continue to streamline some code, update the JAR package version, and document these changes in LICENSE-binary. I am optimistic about the impact of these changes on code stability, as most improvements focus on unit tests with minimal modifications to business logic. I hope we can smoothly complete this PR and merge it into both trunk and branch-3.4.

I was busy for the past two weeks due to some work-related matters. This week, I will continue to improve this PR.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  6s

No case conflicting files found.

+0 :ok:
codespell
0m  6s

codespell was not available.

+0 :ok:
detsecrets
0m  6s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  6s

Shelldocs was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
jsonlint
0m  0s

jsonlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
pathlen
0m  0s
/results-pathlen.txt
The patch appears to contain 1 files with names longer than 240

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 36s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
32m  5s

trunk passed

+1 :green_heart:
compile
17m 26s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
16m  2s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
4m 37s

trunk passed

+1 :green_heart:
mvnsite
40m  7s

trunk passed

+1 :green_heart:
javadoc
36m 45s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

-1 :x:
javadoc
0m 31s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-server_hadoop-yarn-server-timelineservice-hbase-server-2-jdkPrivateBuild-1.8.0_422-8u422-b05-1~20.04-b05.txt
hadoop-yarn-server-timelineservice-hbase-server-2 in trunk failed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+0 :ok:
spotbugs
0m 40s

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

+0 :ok:
spotbugs
0m 42s

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

+0 :ok:
spotbugs
0m 42s

branch/hadoop-client-modules/hadoop-client-runtime no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-check-invariants no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 42s

branch/hadoop-client-modules/hadoop-client-minicluster no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 42s

branch/hadoop-client-modules/hadoop-client-check-test-invariants no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-integration-tests no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

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

+1 :green_heart:
shadedclient
35m  9s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
1m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
40m 13s

the patch passed

+1 :green_heart:
compile
17m  9s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
17m  9s

the patch passed

+1 :green_heart:
compile
16m 15s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
16m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 34s

root: The patch generated 0 new + 1638 unchanged - 90 fixed = 1638 total (was 1728)

+1 :green_heart:
mvnsite
40m  5s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
0m 40s

hadoop-project in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 46s

hadoop-auth in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 42s

hadoop-auth-examples in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m 12s

hadoop-common in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 45s

hadoop-nfs in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-kms in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m  1s

hadoop-hdfs-client in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m 23s

hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 generated 0 new + 2957 unchanged - 159 fixed = 2957 total (was 3116)

+1 :green_heart:
javadoc
0m 47s

hadoop-hdfs-project_hadoop-hdfs-httpfs-jdkUbuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 generated 0 new + 53 unchanged - 2 fixed = 53 total (was 55)

+1 :green_heart:
javadoc
0m 44s

hadoop-hdfs-nfs in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 58s

hadoop-yarn-api in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m  4s

hadoop-yarn-common in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 55s

hadoop-yarn-server-common in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 47s

hadoop-yarn-server-applicationhistoryservice in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 46s

hadoop-yarn-server-timelineservice in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-web-proxy in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m  7s

hadoop-yarn-server-resourcemanager in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 57s

hadoop-yarn-server-nodemanager in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 47s

hadoop-yarn-client in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
1m 35s

hadoop-mapreduce-client in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-mapreduce-client-shuffle in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 48s

hadoop-mapreduce-client-app in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-mapreduce-client-hs in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 49s

hadoop-hdfs-rbf in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-timelineservice-hbase-server-2 in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 47s

hadoop-yarn-server-router in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-timelineservice-documentstore in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-yarn-server-globalpolicygenerator in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-applications-distributedshell in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-services-core in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-services-api in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-applications-catalog-webapp in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 45s

hadoop-yarn-csi in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-mapreduce-examples in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-client in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 50s

hadoop-azure in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 42s

hadoop-resourceestimator in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-runtime in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-check-invariants in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-minicluster in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 38s

hadoop-client-check-test-invariants in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-integration-tests in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 42s

hadoop-huaweicloud in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 38s

hadoop-cloud-storage in the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-project in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 41s

hadoop-auth in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 38s

hadoop-auth-examples in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 54s

hadoop-common in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 40s

hadoop-nfs in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 40s

hadoop-kms in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 54s

hadoop-hdfs-client in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
1m 58s

hadoop-hdfs in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 42s

hadoop-hdfs-project_hadoop-hdfs-httpfs-jdkPrivateBuild-1.8.0_422-8u422-b05-1~20.04-b05 with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05 generated 0 new + 53 unchanged - 2 fixed = 53 total (was 55)

+1 :green_heart:
javadoc
0m 41s

hadoop-hdfs-nfs in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 52s

hadoop-yarn-api in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
1m  1s

hadoop-yarn-common in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 51s

hadoop-yarn-server-common in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-server-applicationhistoryservice in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-server-timelineservice in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-server-web-proxy in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
1m  1s

hadoop-yarn-server-resourcemanager in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 53s

hadoop-yarn-server-nodemanager in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-client in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
1m 20s

hadoop-mapreduce-client in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 39s

hadoop-mapreduce-client-shuffle in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 44s

hadoop-mapreduce-client-app in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 41s

hadoop-mapreduce-client-hs in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 46s

hadoop-hdfs-rbf in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-server-timelineservice-hbase-server-2 in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 37s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-router in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-server-timelineservice-documentstore in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-server-globalpolicygenerator in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-applications-distributedshell in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-services-core in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 37s

hadoop-yarn-services-api in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 37s

hadoop-yarn-applications-catalog-webapp in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-csi in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 41s

hadoop-mapreduce-examples in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 37s

hadoop-client in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 47s

hadoop-azure in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 41s

hadoop-resourceestimator in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-runtime in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 35s

hadoop-client-check-invariants in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-minicluster in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 35s

hadoop-client-check-test-invariants in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 35s

hadoop-client-integration-tests in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 39s

hadoop-huaweicloud in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+1 :green_heart:
javadoc
0m 36s

hadoop-cloud-storage in the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05.

+0 :ok:
spotbugs
0m 35s

hadoop-project has no data from spotbugs

+0 :ok:
spotbugs
0m 43s

hadoop-client-modules/hadoop-client has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-runtime has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-check-invariants has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-minicluster has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-check-test-invariants has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-integration-tests has no data from spotbugs

+0 :ok:
spotbugs
0m 43s

hadoop-cloud-storage-project/hadoop-cloud-storage has no data from spotbugs

+1 :green_heart:
shadedclient
36m 13s

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

_ Other Tests _

+1 :green_heart:
unit
0m 40s

hadoop-project in the patch passed.

+1 :green_heart:
unit
3m 27s

hadoop-auth in the patch passed.

+1 :green_heart:
unit
0m 43s

hadoop-auth-examples in the patch passed.

+1 :green_heart:
unit
20m 33s

hadoop-common in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-nfs in the patch passed.

+1 :green_heart:
unit
3m 51s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
2m 47s

hadoop-hdfs-client in the patch passed.

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

+1 :green_heart:
unit
6m 28s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
unit
3m 42s

hadoop-hdfs-nfs in the patch passed.

+1 :green_heart:
unit
1m 28s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
6m  6s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
1m  5s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
4m 35s

hadoop-yarn-server-applicationhistoryservice in the patch passed.

+1 :green_heart:
unit
2m 15s

hadoop-yarn-server-timelineservice in the patch passed.

+1 :green_heart:
unit
1m 40s

hadoop-yarn-server-web-proxy in the patch passed.

+1 :green_heart:
unit
1m 23s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
2m  2s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
unit
0m 57s

hadoop-yarn-client in the patch passed.

+1 :green_heart:
unit
4m 20s

hadoop-mapreduce-client in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-mapreduce-client-shuffle in the patch passed.

+1 :green_heart:
unit
1m  0s

hadoop-mapreduce-client-app in the patch passed.

+1 :green_heart:
unit
0m 56s

hadoop-mapreduce-client-hs in the patch passed.

+1 :green_heart:
unit
35m 55s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
unit
1m  0s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-yarn-server-timelineservice-hbase-server-2 in the patch passed.

+1 :green_heart:
unit
0m 55s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed.

+1 :green_heart:
unit
0m 59s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-yarn-server-timelineservice-documentstore in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-yarn-applications-distributedshell in the patch passed.

+1 :green_heart:
unit
0m 59s

hadoop-yarn-services-core in the patch passed.

+1 :green_heart:
unit
2m 38s

hadoop-yarn-services-api in the patch passed.

+1 :green_heart:
unit
1m 23s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
unit
1m 10s

hadoop-yarn-csi in the patch passed.

+1 :green_heart:
unit
1m 21s

hadoop-mapreduce-examples in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-client in the patch passed.

+1 :green_heart:
unit
1m  6s

hadoop-azure in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-resourceestimator in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-client-runtime in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-client-check-invariants in the patch passed.

+1 :green_heart:
unit
0m 50s

hadoop-client-minicluster in the patch passed.

+1 :green_heart:
unit
0m 46s

hadoop-client-check-test-invariants in the patch passed.

+1 :green_heart:
unit
0m 47s

hadoop-client-integration-tests in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-huaweicloud in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-cloud-storage in the patch passed.

+1 :green_heart:
asflicense
1m 15s

The patch does not generate ASF License warnings.

985m 35s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommission

Subsystem
Report/Notes

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

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

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

uname
Linux e6f53bb20fa2 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
trunk / 1567fa402e22ee07b2ff7b6106b9bc290cdc6428

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7019/26/testReport/

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

modules
C: hadoop-project hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-auth-examples hadoop-common-project/hadoop-common hadoop-common-project/hadoop-nfs hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs hadoop-hdfs-project/hadoop-hdfs-nfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-mapreduce-project/hadoop-mapreduce-client hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-server/hadoop-yarn-server-timelineservice-hbase-server-2 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-documentstore hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-client-modules/hadoop-client hadoop-tools/hadoop-azure hadoop-tools/hadoop-resourceestimator hadoop-client-modules/hadoop-client-runtime hadoop-client-modules/hadoop-client-check-invariants hadoop-client-modules/hadoop-client-minicluster hadoop-client-modules/hadoop-client-check-test-invariants hadoop-client-modules/hadoop-client-integration-tests hadoop-cloud-storage-project/hadoop-huaweicloud hadoop-cloud-storage-project/hadoop-cloud-storage U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7019/26/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2 shellcheck=0.7.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m 32s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  6s

No case conflicting files found.

+0 :ok:
codespell
0m  6s

codespell was not available.

+0 :ok:
detsecrets
0m  6s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  6s

Shelldocs was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
jsonlint
0m  0s

jsonlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
pathlen
0m  0s
/results-pathlen.txt
The patch appears to contain 1 files with names longer than 240

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 54s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 27s

trunk passed

+1 :green_heart:
compile
16m 16s

trunk passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
15m  5s

trunk passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga

+1 :green_heart:
checkstyle
4m 30s

trunk passed

+1 :green_heart:
mvnsite
39m 10s

trunk passed

+1 :green_heart:
javadoc
35m 58s

trunk passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04

-1 :x:
javadoc
0m 30s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-server_hadoop-yarn-server-timelineservice-hbase-server-2-jdkPrivateBuild-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.txt
hadoop-yarn-server-timelineservice-hbase-server-2 in trunk failed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+0 :ok:
spotbugs
0m 43s

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

+0 :ok:
spotbugs
0m 42s

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

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-runtime no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 40s

branch/hadoop-client-modules/hadoop-client-check-invariants no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-minicluster no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-check-test-invariants no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

branch/hadoop-client-modules/hadoop-client-integration-tests no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 41s

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

+1 :green_heart:
shadedclient
33m 16s

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

-0 :warning:
patch
33m 43s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
1m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
39m 30s

the patch passed

+1 :green_heart:
compile
16m 35s

the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
16m 35s

the patch passed

+1 :green_heart:
compile
15m  6s

the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga

+1 :green_heart:
javac
15m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 24s

root: The patch generated 0 new + 1638 unchanged - 90 fixed = 1638 total (was 1728)

+1 :green_heart:
mvnsite
39m  7s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
0m 40s

hadoop-project in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 45s

hadoop-auth in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-auth-examples in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m 13s

hadoop-common in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 45s

hadoop-nfs in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-kms in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m  1s

hadoop-hdfs-client in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m 20s

hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04 with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04 generated 0 new + 2958 unchanged - 159 fixed = 2958 total (was 3117)

+1 :green_heart:
javadoc
0m 46s

hadoop-hdfs-project_hadoop-hdfs-httpfs-jdkUbuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04 with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04 generated 0 new + 53 unchanged - 2 fixed = 53 total (was 55)

+1 :green_heart:
javadoc
0m 44s

hadoop-hdfs-nfs in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 58s

hadoop-yarn-api in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m  2s

hadoop-yarn-common in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 54s

hadoop-yarn-server-common in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 47s

hadoop-yarn-server-applicationhistoryservice in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 46s

hadoop-yarn-server-timelineservice in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-web-proxy in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m  6s

hadoop-yarn-server-resourcemanager in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 57s

hadoop-yarn-server-nodemanager in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 46s

hadoop-yarn-client in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
1m 32s

hadoop-mapreduce-client in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-mapreduce-client-shuffle in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 46s

hadoop-mapreduce-client-app in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 45s

hadoop-mapreduce-client-hs in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 52s

hadoop-hdfs-rbf in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-server-timelineservice-hbase-server-2 in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-yarn-server-router in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-server-timelineservice-documentstore in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-server-globalpolicygenerator in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-applications-distributedshell in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-services-core in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-services-api in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-applications-catalog-webapp in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-yarn-csi in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 44s

hadoop-mapreduce-examples in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-client in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 49s

hadoop-azure in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 43s

hadoop-resourceestimator in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-runtime in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-check-invariants in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 38s

hadoop-client-minicluster in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-check-test-invariants in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 37s

hadoop-client-integration-tests in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 41s

hadoop-huaweicloud in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-cloud-storage in the patch passed with JDK Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-project in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-auth in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 38s

hadoop-auth-examples in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 52s

hadoop-common in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 40s

hadoop-nfs in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-kms in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 53s

hadoop-hdfs-client in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
1m 51s

hadoop-hdfs in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 43s

hadoop-hdfs-project_hadoop-hdfs-httpfs-jdkPrivateBuild-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga generated 0 new + 53 unchanged - 2 fixed = 53 total (was 55)

+1 :green_heart:
javadoc
0m 40s

hadoop-hdfs-nfs in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 49s

hadoop-yarn-api in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
1m  1s

hadoop-yarn-common in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 50s

hadoop-yarn-server-common in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 42s

hadoop-yarn-server-applicationhistoryservice in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-server-timelineservice in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-server-web-proxy in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
1m  0s

hadoop-yarn-server-resourcemanager in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 52s

hadoop-yarn-server-nodemanager in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-client in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
1m 12s

hadoop-mapreduce-client in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-mapreduce-client-shuffle in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 44s

hadoop-mapreduce-client-app in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 40s

hadoop-mapreduce-client-hs in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 46s

hadoop-hdfs-rbf in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

-1 :x:
javadoc
0m 31s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-server_hadoop-yarn-server-timelineservice-hbase-server-2-jdkPrivateBuild-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.txt
hadoop-yarn-server-timelineservice-hbase-server-2 in the patch failed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-server-router in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 40s

hadoop-yarn-server-timelineservice-documentstore in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 38s

hadoop-yarn-server-globalpolicygenerator in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-applications-distributedshell in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 37s

hadoop-yarn-services-core in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-services-api in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-applications-catalog-webapp in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-csi in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 41s

hadoop-mapreduce-examples in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-client in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 46s

hadoop-azure in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-resourceestimator in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-runtime in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 35s

hadoop-client-check-invariants in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-minicluster in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-check-test-invariants in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-client-integration-tests in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 39s

hadoop-huaweicloud in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+1 :green_heart:
javadoc
0m 36s

hadoop-cloud-storage in the patch passed with JDK Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga.

+0 :ok:
spotbugs
0m 35s

hadoop-project has no data from spotbugs

+0 :ok:
spotbugs
0m 43s

hadoop-client-modules/hadoop-client has no data from spotbugs

+0 :ok:
spotbugs
0m 45s

hadoop-client-modules/hadoop-client-runtime has no data from spotbugs

+0 :ok:
spotbugs
0m 43s

hadoop-client-modules/hadoop-client-check-invariants has no data from spotbugs

+0 :ok:
spotbugs
0m 43s

hadoop-client-modules/hadoop-client-minicluster has no data from spotbugs

+0 :ok:
spotbugs
0m 44s

hadoop-client-modules/hadoop-client-check-test-invariants has no data from spotbugs

+0 :ok:
spotbugs
0m 42s

hadoop-client-modules/hadoop-client-integration-tests has no data from spotbugs

+0 :ok:
spotbugs
0m 45s

hadoop-cloud-storage-project/hadoop-cloud-storage has no data from spotbugs

+1 :green_heart:
shadedclient
33m 56s

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

_ Other Tests _

+1 :green_heart:
unit
0m 38s

hadoop-project in the patch passed.

+1 :green_heart:
unit
3m 23s

hadoop-auth in the patch passed.

+1 :green_heart:
unit
0m 41s

hadoop-auth-examples in the patch passed.

+1 :green_heart:
unit
20m 27s

hadoop-common in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-nfs in the patch passed.

+1 :green_heart:
unit
3m 49s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
2m 43s

hadoop-hdfs-client in the patch passed.

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

+1 :green_heart:
unit
6m 17s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
unit
3m 47s

hadoop-hdfs-nfs in the patch passed.

+1 :green_heart:
unit
1m 26s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
6m 16s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
1m  1s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
4m 36s

hadoop-yarn-server-applicationhistoryservice in the patch passed.

+1 :green_heart:
unit
2m 15s

hadoop-yarn-server-timelineservice in the patch passed.

+1 :green_heart:
unit
1m 44s

hadoop-yarn-server-web-proxy in the patch passed.

+1 :green_heart:
unit
1m 21s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
1m 56s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
unit
0m 56s

hadoop-yarn-client in the patch passed.

+1 :green_heart:
unit
3m 56s

hadoop-mapreduce-client in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-mapreduce-client-shuffle in the patch passed.

+1 :green_heart:
unit
0m 58s

hadoop-mapreduce-client-app in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-mapreduce-client-hs in the patch passed.

-1 :x:
unit
35m 30s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
unit
1m  4s

hadoop-yarn-server-timelineservice-hbase-client in the patch passed.

+1 :green_heart:
unit
0m 50s

hadoop-yarn-server-timelineservice-hbase-server-2 in the patch passed.

+1 :green_heart:
unit
0m 55s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed.

+1 :green_heart:
unit
0m 56s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-yarn-server-timelineservice-documentstore in the patch passed.

+1 :green_heart:
unit
0m 51s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-yarn-applications-distributedshell in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-yarn-services-core in the patch passed.

+1 :green_heart:
unit
2m 33s

hadoop-yarn-services-api in the patch passed.

+1 :green_heart:
unit
1m 21s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
unit
1m  8s

hadoop-yarn-csi in the patch passed.

+1 :green_heart:
unit
1m 17s

hadoop-mapreduce-examples in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-client in the patch passed.

+1 :green_heart:
unit
1m  4s

hadoop-azure in the patch passed.

+1 :green_heart:
unit
0m 52s

hadoop-resourceestimator in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-client-runtime in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-client-check-invariants in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-client-minicluster in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-client-check-test-invariants in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-client-integration-tests in the patch passed.

+1 :green_heart:
unit
0m 53s

hadoop-huaweicloud in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-cloud-storage in the patch passed.

+1 :green_heart:
asflicense
1m 14s

The patch does not generate ASF License warnings.

965m  4s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommission

hadoop.hdfs.server.federation.router.TestRouterClientRejectOverload

Subsystem
Report/Notes

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

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

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

uname
Linux c6b335ae7d11 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
trunk / 86093dfb31ad575503c4b5455cba1b9817f131ab

Default Java
Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.25+9-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_432-8u432-ga~us1-0ubuntu2~20.04-ga

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7019/28/testReport/

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

modules
C: hadoop-project hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-auth-examples hadoop-common-project/hadoop-common hadoop-common-project/hadoop-nfs hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs hadoop-hdfs-project/hadoop-hdfs-nfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-mapreduce-project/hadoop-mapreduce-client hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-server/hadoop-yarn-server-timelineservice-hbase-server-2 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-documentstore hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-client-modules/hadoop-client hadoop-tools/hadoop-azure hadoop-tools/hadoop-resourceestimator hadoop-client-modules/hadoop-client-runtime hadoop-client-modules/hadoop-client-check-invariants hadoop-client-modules/hadoop-client-minicluster hadoop-client-modules/hadoop-client-check-test-invariants hadoop-client-modules/hadoop-client-integration-tests hadoop-cloud-storage-project/hadoop-huaweicloud hadoop-cloud-storage-project/hadoop-cloud-storage U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7019/28/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2 shellcheck=0.7.0

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

This message was automatically generated.


APT-notes samples pass

Hello, i asked several times for the password by twitter but no one replied me.

What is your Twitter handle?  I’ll DM you.

What is your Twitter handle? I’ll DM you.

hello, here is my profile https://twitter.com/W4nn4Die
thanks


feature: add promote resource attributes

closes #155

TESTS:

https://github.com/arukiidou/docker-otel-lgtm/pull/8

Acceptance Tests / acceptance-tests (push) passeed

Thanks!


Figure out a way to rename PageJson in OpenAPI

Currently, it's not possible to use @Schema(name="Page") because it will break generics in OpenAPI (a single Page object will be created instead of PageGame, PageGameWithFiles etc.).
Need to find a workaround for this.

Done as part of #8


Juggernaut error

I updated the redis
When i running redis
spritle@ubuntu:~/redis-2.4.4/src$ redis-server
15 Dec 12:32:42 * Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
15 Dec 12:32:42 - Server started, Redis version 1.2.0
15 Dec 12:32:42 * WARNING overcommit_memory is set to 0! Background save may fail under low condition memory. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
15 Dec 12:32:42 - The server is now ready to accept connections on port 6379
15 Dec 12:32:42 . 0 clients connected (0 slaves), 412114 bytes in use, 0 shared objects
....
...
....
....
After that i try to start juggernaut
I am getting the same error
spritle@ubuntu:~/Desktop/vino-tryouts/juggernaut$ juggernaut
info  - socket.io started
node_redis: no callback to send error: ERR unknown command 'subscribe'
node.js:205
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: ERR unknown command 'subscribe'
at RedisReplyParser. (/usr/local/lib/node_modules/juggernaut/node_modules/redis/index.js:78:27)
at RedisReplyParser.emit (events.js:67:17)
at RedisReplyParser.send_error (/usr/local/lib/node_modules/juggernaut/node_modules/redis/lib/parser/javascript.js:265:14)
at RedisReplyParser.execute (/usr/local/lib/node_modules/juggernaut/node_modules/redis/lib/parser/javascript.js:124:22)
at RedisClient.on_data (/usr/local/lib/node_modules/juggernaut/node_modules/redis/index.js:358:27)
at Socket. (/usr/local/lib/node_modules/juggernaut/node_modules/redis/index.js:93:14)
at Socket.emit (events.js:67:17)
at Socket._onReadable (net_legacy.js:684:14)
at IOWatcher.onReadable [as callback] (net_legacy.js:177:10)

You said that you have upgraded your redis server, but the output says you are running Redis 1.2.0.
Juggernaut uses Redis for communicating using SUBSCRIBE command, which is available since Redis 1.3.8. Make sure that you are using your new version of Redis.

Upgrade to Redis 3.3.12.

@maccman I thought the latest stable Redis was 2.4.4?

Yes, sorry, that's the one I mean - that'll work. Anything newer than 1.2.0 ;)

I downloaded redis from http://redis.io/download. After extraction of redis-2.4.4.tar.gz I am getting redis-2.4.4. After that I did the following
spritle@ubuntu:~$ cd Desktop/redis-2.4.4/
spritle@ubuntu:~/Desktop/redis-2.4.4$ make
cd src && make all
make[1]: Entering directory `/home/spritle/Desktop/redis-2.4.4/src'
MAKE hiredis
.....
....
....
Then next step
spritle@ubuntu:~/Desktop/redis-2.4.4$ cd src
spritle@ubuntu:~/Desktop/redis-2.4.4/src$ redis-server
Still i m getting the
16 Dec 11:29:27 * Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
16 Dec 11:29:27 - Server started, Redis version 1.2.0
16 Dec 11:29:27 * WARNING overcommit_memory is set to 0! Background save may fail under low condition memory. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
16 Dec 11:29:27 - The server is now ready to accept connections on port 6379
16 Dec 11:29:27 . 0 clients connected (0 slaves), 412114 bytes in use, 0 shared objects
May i did anything wrong

Hi I followed https://redistogo.com/documentation/introduction_to_redis. Download redis-2.0.0 and start the redis server
spritle@ubuntu:~/redis-2.0.0-rc1$ redis-server
[5312] 16 Dec 11:44:18 # Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
[5312] 16 Dec 11:44:18 * Server started, Redis version 1.3.14
[5312] 16 Dec 11:44:18 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
[5312] 16 Dec 11:44:18 * The server is now ready to accept connections on port 6379
[5312] 16 Dec 11:44:18 - 0 clients connected (0 slaves), 533436 bytes in use
[5312] 16 Dec 11:44:23 - 0 clients connected (0 slaves), 533436 bytes in use
[5312] 16 Dec 11:44:28 - 0 clients connected (0 slaves), 533436 bytes in use
And start the juggernaut
spritle@ubuntu:/usr/local/lib/node_modules/juggernaut$ juggernaut server.js
The "sys" module is now called "util". It should have a similar interface.
info  - socket.io started
debug - client authorized
info  - handshake authorized<PHONE_NUMBER>198808267
debug - setting request GET /socket.io/1/xhr-polling/1132868371198808267?t=1324016234129
debug - setting poll timeout
debug - client authorized for
debug - clearing poll timeout
debug - xhr-polling writing 1::
debug - set close timeout for client<PHONE_NUMBER>198808267
debug - xhr-polling received data packet 3:::{"type":"subscribe","channel":"/observer"}
Now i can able to connect juggernaut server.
Thank you so much for your guidelines.


Add support for 'client_body_timeout' and 'client_header_timeout'

Closes #1237.

This change is

Coverage increased (+0.04%) to 44.513% when pulling d57bc292c30386c47f0e38ee70fc8a96a97583b7 on danielfm:client-header-body-timeout into 02e20eb81ace3da9d5c8f3bc6af5465bd917457b on kubernetes:master.

/lgtm

@danielfm thanks!


The pre-training weights of Dual-Encoder Baseline (with TSF-B/L)

Thanks to the author for his contribution to the ego community. It's cool work! Would you mind releasing the pre-training weights of the Dual-Encoder Baseline (with TSF-B/L)?

Duplicate of #20 .


chore: add opacity utility

Add the opacity utility to the base preset.

Thank you @anubra266 ! 🔥


Split PII data away from general sample data

Motivation and Context
PII data needs to be treated differently.
What has changed
Split PII data away from main sample data.
How to test?
Run ATs etc.
Links
Trello: https://trello.com/c/CusPfR8A

 Generic Survey - Case management - PII (21)


npm installation error?

[root@localhost webrtc]# npm install uNetworking/uWebSockets.js#v18.8.0
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-16T01_06_35_073Z-debug.log

looks like you need to install git

I do have git installed.

i can do a git clone no, issues. just running npm it doesnt.

make sure it is in your Path. your error says git is not found https://stackoverflow.com/a/56990788


Update Docs: HamClock Configuration Notes

Using this issue to track some updates to README.md specific to configuring HamClock in Docker.

WiFi: Do not configure; this will use the Docker host network (see #10).
NTP: Configure time server to OS to skip time check (added in HamClock v3.05).

More in comments as I think of them.

I did test with the Synology integrated NTP server and it works instantly for me. I simply punched the IP address of the Synology and it sync instantly.

You can set the host to OS and it will use the host system time. That’ll be one of my notes. Of course if you have your own NTP server that’s fine, too.
I’m still thinking how much I want to write up, because I don’t want to duplicate the official manual or anything (and have to maintain it).

Understood, I was just reporting running your Docker on Synology NAS also connect to the integrated NTP service. I can only test under Synology Docker so this is why I just reported this. Thanks for your work !


Docs: improve shortcodes page [WIP]

See #1613

Is this still a WIP? Are you ready for us to merge/review it?

I've asked the same question in the corresponding issue #1613. @moorereason gave me feedback during the PR was in made. In my eyes everyhing should be fine as long as nobody has something to complain.

LGTM

Thank you all!
Merged as 2e3d5c2 (master) and edc8e82 (v0.15.docs)


markdown: implement exercise

Specification

I'm going to tackle this :) what could be a good function name for markdown to html conversion ? is "Convert(input string) string" clear enough ?

Render or Parse will work.
Remember that this exercise is a "re-factor". As well as the example.go, create a .go file which also passes the tests but needs refactoring.  There is at least one other re-factor exercise for reference.

mm I'm sure my example implementation needs refactoring :) If you agree I'll send a first PR just to have some feedback, then we can discuss on that


Subscription support

I added subscription support, minimally tests against an apollo server.
I plan to write a graphql-code-gen plugin later on and will test more then, but I could use a small code review before that.

Any ideas how to test that in a more thorough way in the unit tests?

I'm not a maintainer on this project, but based on what I saw, we would need to ensure at least these two functionalities:

handle responses from different subscriptions on the same subscription client (WebSocket)
a main cancelable context + a reconnect system
2.1. the main cancelable context would allow us to cancel a client, independently of which WebSocket request we have on going (actually, the subscriptions-transport-ws had issues with this for a long time, and it is easier to deal with it recurring to go contexts.
2.2. the reconnect procedure would allow we would reconnect it until the main context gets canceled


Invariant violated in step_phase.pony at line 215

Is this a bug, feature request, or feedback?
Bug
What is the current behavior?
Intermittently:
1574117391.247747,Invariant violation: received barrier CheckpointRollbackResumeBarrierToken(Rollback 74, Checkpoint 101) is greater than current barrier CheckpointRollbackBarrierToken(Rollback 74, Checkpoint 101) at Step<PHONE_NUMBER>13175559713113995589207764052
Invariant violated in /home/vagrant/wallaroo/lib/wallaroo/core/step/step_phase.pony at line 215

Full logs are at http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.1574117544.tar.gz
What is the expected behavior?
No crash
What OS and version of Wallaroo are you using?

Steps to reproduce?
$ export WALLAROO_TOP=/your/path/to/top/of/wallaroo/repo
$ cd $WALLAROO_TOP
$ dd if=$HOME/wallaroo/testing/data/market_spread/nbbo/r3k-symbols_nbbo-fixish.msg bs=1000000 count=1 | od -x | sed 's/^/T/' | sed -n
'1,/T3641060/p' | perl -ne 'print "\0\0\0"; print "1"; print' > /tmp/input-file.txt
$ cd testing/correctness/scripts/effectively-once
$ export WALLAROO_THRESHOLDS='*.8'
$ export WALLAROO_BIN=$WALLAROO_TOP/examples/pony/passthrough/passthrough
$ . ./sample-env-vars.sh
$ make -C ../../../..     PONYCFLAGS="--verbose=1 -d -Dresilience -Dtrace -Dcheckpoint_trace -Didentify_routing_ids"
build-examples-pony-passthrough build-testing-tools-external_sender     build-utils-cluster_shrinker build-utils-data_receiver
build-testing-tools-fixed_length_message_blaster
$ ./master-crasher.sh 2 crash0 crash1 crash-sink

NOTE: Without close examination, this problem can look very similar to #3037.

See http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.1574372334.tar.gz, which is based on the 3037-ideas debugging branch + additional printf spam.
1574372258.614181,Received msg on Control Channel: RecoveryInitiatedMsg
1574372258.614198,Recovery initiation attempted by worker1
1574372258.614208,RECOVERY: Received override recovery message during Reconnect Phase. Waiting to cede control until boundaries are reconnected.
1574372258.614214,!@ my reason: 200, their reason: 200, rollback_id: 95, _highest_rival_rollback_id: 0
1574372258.614219,!@ HIGHER THAN HIGHEST RIVAL

I've also observed this bug using ./master-crasher.sh 4 crash2 crash3 crash-sink.