chore: upgrade vitepress

This PR includes:

update vitepress to latest version 0.15.6: changed all core stuff on docs since vitepress has breaking changes from 0.14.1.
update all repo deps to major except workbox: 6.2.2 version has breaking changes, I keep it on 6.1.5 version, upgrade to latest version will go on its own separate PR.
docs home page: added title and features (done by antfu on master).
docs: correct wording and rephrasing some entries (see commits).
package.json: added keywords and funding entries.
examples: update vite pwa configurations and some changes on vue examples.

@antfu: should we release a new 0.11.0 version or wait to update workbox to 6.2.2?

Don't merge yet, Ineed to change master to main .references.

Don't merge yet, I need to change workbox version (missing ^).

It is ok.

Do you update your local repo?
Where is this commit? Peer dependencies gone:
https://github.com/antfu/vite-plugin-pwa/commit/796422b98f1e4f46bfc32cdbc7e24476b3e34de4#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

ok, when updting using taze removed from peer deps, I'm fixing rig now...

Don't merge, finishing testing migration to workbox 6.2.2.

@antfu PR ready to review.
There is a breaking change since new injectManifestOptions don't have mode property, seems to be deleted.: I have left commented out on modules.ts on generateInjectManifest (line 66).

@antfu should we update again all deps to major?

taze -r output
vite-plugin-pwa package.json

  tsup                          dev    ~12d         ^4.13.1  →         ^4.14.0  ⩽1d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  vue                           dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  rollup                                ~8d         ^2.56.1  →         ^2.56.2  ~6d
  workbox-build                        ~10d          ^6.2.2  →          ^6.2.4  ~5d
  workbox-window                       ~10d          ^6.2.2  →          ^6.2.4  ~5d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  rollup                        dev     ~8d         ^2.56.1  →         ^2.56.2  ~6d

  3 minor, 5 patch updates

vite-plugin-pwa-docs docs/package.json

  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @iconify/json                 dev     ~7d        ^1.1.385  →        ^1.1.388  ⩽1d

  2 minor, 1 patch updates

example-react-basic examples/react-basic/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 2 patch updates

example-react-basic-inject-manifest examples/react-basic-inject-manifest/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 3 patch updates

example-react-router examples/react-router/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 2 patch updates

example-svelte-basic examples/svelte-basic/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 prerelease updates

example-svelte-basic-inject-manifest examples/svelte-basic-inject-manifest/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 patch, 1 prerelease updates

example-svelte-routify examples/svelte-routify/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 prerelease updates

example-vue-basic examples/vue-basic-cdn/package.json

  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  3 minor updates

example-vue-basic examples/vue-basic/package.json

  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  3 minor updates

example-vue-basic-inject-manifest examples/vue-basic-inject-manifest/package.json

  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  3 minor, 1 patch updates

example-vue-router examples/vue-router/package.json

  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  3 minor updates

taze -r major output

vite-plugin-pwa package.json

  tsup                          dev    ~12d         ^4.13.1  →         ^4.14.0  ⩽1d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  vue                           dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  rollup                                ~8d         ^2.56.1  →         ^2.56.2  ~6d
  workbox-build                        ~10d          ^6.2.2  →          ^6.2.4  ~5d
  workbox-window                       ~10d          ^6.2.2  →          ^6.2.4  ~5d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  rollup                        dev     ~8d         ^2.56.1  →         ^2.56.2  ~6d

  3 minor, 5 patch updates

vite-plugin-pwa-docs docs/package.json

  @vueuse/core                          ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  @vueuse/core                  dev     ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  esbuild-register              dev    ~2mo          ^2.6.0  →          ^3.0.0  ~3d
  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  vitepress                     dev    ~2mo         ^0.15.6  →         ^0.16.1  ~5d
  @iconify/json                 dev     ~7d        ^1.1.385  →        ^1.1.388  ⩽1d

  3 major, 3 minor, 1 patch updates

example-react-basic examples/react-basic/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 2 patch updates

example-react-basic-inject-manifest examples/react-basic-inject-manifest/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 3 patch updates

example-svelte-basic examples/svelte-basic/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 prerelease updates

example-react-router examples/react-router/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @types/react                  dev    ~10d        ^17.0.16  →        ^17.0.18  ~2d
  workbox-window                dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 minor, 2 patch updates

example-svelte-basic-inject-manifest examples/svelte-basic-inject-manifest/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 patch, 1 prerelease updates

example-svelte-routify examples/svelte-routify/package.json

  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  @sveltejs/vite-plugin-svelte  dev    ~18d  ^1.0.0-next.15  →  ^1.0.0-next.17  ~4d

  1 minor, 1 prerelease updates

example-vue-basic examples/vue-basic/package.json

  @vueuse/core                  dev     ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  1 major, 3 minor updates

example-vue-basic examples/vue-basic-cdn/package.json

  @vueuse/core                  dev     ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  1 major, 3 minor updates

example-vue-basic-inject-manifest examples/vue-basic-inject-manifest/package.json

  @vueuse/core                  dev     ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d
  workbox-precaching            dev    ~10d          ^6.2.2  →          ^6.2.4  ~5d

  1 major, 3 minor, 1 patch updates

example-vue-router examples/vue-router/package.json

  @vueuse/core                  dev     ~7d          ^5.3.0  →          ^6.0.0  ⩽1d
  vue                                  ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  @vue/compiler-sfc             dev    ~1mo          ^3.1.5  →          ^3.2.2  ~5d
  vite                          dev    ~20d          ^2.4.4  →          ^2.5.0  ⩽1d

  1 major, 3 minor updates


Add link to medium articles

Apparently documentation is not enough and finding those articles is not that easy. I am pushing this intentionally to master branch as that's what people will see when coming to repo.

We have witnessed several people coming to stampit Gitter chat asking basic questions. This PR is a good move. It might help people to get started faster.
I'd love to merge this. Although, I need to tweak the article before merging. Namely, as @unstoppablecarl suggested, add the TOC to the top of the article(s). Will do that today.

Couple grammar tweaks.

Check out Fun with Stamps, a series of articles explaining the basics of stamps along with some advanced topics.

Thanks @troutowicz, I've applied your tweak :)


feat: Escape vertical-bar when Creating markdown table

ref. #79
WHAT I CHANGED

Escape vertical-bar character  when Creating markdown table
Add test case for testing escape character

HOW IMPLEMENTED
| is another way to represent vertical lines in html. It can therefore be implemented by replacing characters during markdown generation.
ADDITIONAL INFO

WhatIs.com vertical bar

Thanks a lot for taking the time to contribute this! Really appreciate it. I will publish a release later today.

My pleasure!! Thank you as well for the wonderful CI workflow.
As I have some time to contribute during my summer vacation, I might be able to contribute to other issues as well.


modular multiplication runs out of gas

Trying this code to calculate modular exponentiation, however in the below code prepare_modexp modular exponentiation works with the values x and p, but modmul modular multiplication runs out of gas.
pragma solidity >=0.4.20 <0.6;

import "./BigNumber.sol";

/*

 */

contract testmod {
  using BigNumber for *;

  function test() public returns(bytes memory,bool,uint){
    BigNumber.instance memory g;
    BigNumber.instance memory p;
    BigNumber.instance memory x;

    g.val = hex"04";
    g.neg = false;
    g.bitlen = BigNumber.get_bit_length(g.val);

    p.val = hex"0800";
    p.neg = false;
    p.bitlen = BigNumber.get_bit_length(p.val);

    x.val = hex"03";
    x.neg = false;
    x.bitlen = BigNumber.get_bit_length(x.val);

    //BigNumber.instance memory res = g.modmul(x,p);
    BigNumber.instance memory res = g.prepare_modexp(x,p);

    return (res.val, res.neg, res.bitlen);
  }

I think the issue is with the for loop on line 140 in bn_add(), but not sure how to fix it:
https://github.com/zcoinofficial/solidity-BigNumber/blob/db0d6d298cee2d8974cb6ffa76659d96f3454150/contracts/BigNumber.sol#L140-L168

Any update? I am experiencing the exact same issue

I'm not an expert for that library, but the inline comments say you shouldn't instantiate the struct directly. However, if you want to get it running that way, this should work:
g.val = hex"0000000000000000000000000000000000000000000000000000000000000004";
p.val = hex"0000000000000000000000000000000000000000000000000000000000000800";
x.val = hex"0000000000000000000000000000000000000000000000000000000000000003";

Or you can use the BigNumber._new(val, neg, copy) function instead (abi.encodePacked(...) converts the values to bytes):
function test() public returns(bytes memory,bool,uint){
  BigNumber.instance memory g = BigNumber._new(abi.encodePacked(uint256(0x04)), false, false);
  BigNumber.instance memory p = BigNumber._new(abi.encodePacked(uint256(0x0800)), false, false);
  BigNumber.instance memory x = BigNumber._new(abi.encodePacked(uint256(0x03)), false, false);

  BigNumber.instance memory res = g.modmul(x, p);

  return (res.val, res.neg, res.bitlen);
}

Result of (4 * 3) mod 2048:
value: 0x000000000000000000000000000000000000000000000000000000000000000c (12)
negative: false
bitlen: 4

@robmuth i'm using the same code and still getting an error on solidity v0.8
however, it works with solidity v0.5.17,

@robmuth both of those snippets produce an error on solidity v0.8
however, it works with solidity v0.5.17.

to fix on solidity v0.8, wrap first loop of right_shift in an unchecked{} block

Hi, a test case has been added for this particular case: https://github.com/firoorg/solidity-BigNumber/blob/master/test/BigNumbers.t.sol#L267


Resource list additions

Hi everyone! 👋  @synthead and I would like your help getting requests for resources you think would be helpful.
Please comment resource requests, so things you'd like to learn or for us to talk about, links, etc.

Markdown Cheat Sheet 🥇 #5
https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Hello
thank you

https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf

Where my tacos at :taco:

[ ] Add Hacktoberfest information
[ ] Add git cheatsheet


New version: vim.vim.nightly version 9.1.0312

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @chrisbra,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 876.)

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-04-12 16:46:24.246 [FAIL] Installer failed security check. Url: https://github.com/vim/vim-win32-installer/releases/download/v9.1.0312/gvim_9.1.0312_x86.exe Result: 0x80004005

(Automated response - build 876.)

@wingetbot run

Possible duplicate package entry.
Similar installer SHA256 hash found in manifest:

InstallerSha256: d69390af71a289eb237010ae74e314154eab3a5836859cf542e8af88c25d2671

manifests\v\vim\vim\9.1.0312

InstallerSha256: 8d4619439ba718c5e739eb39cca6cc65c3ddd5619bbbe92c736da0d9aba7c4f9

manifests\v\vim\vim\9.1.0312

This nightly appears to have been released as a full version.


led strip

how can i use a ws2811 strip?

Don't use the Neopixel library. You can use the Arduino/ESP code from the SystematicLEDs package,
https://github.com/not-matt/Systematic-LEDs/tree/master/arduino/ws2812_controller
The format is slightly different, so (in addition to fixing the UDP port), you need to make sure that
audio-reactive-led-strip sends all the pixel's data each time, without an index. Here are my
changes to led.py
52,53c68,69
<     n_packets = 1 # len(idx) // MAX_PIXELS_PER_PACKET + 1

idx = [i for i in idx if not np.array_equal(p[:, i], _prev_pixels[:, i])]
n_packets = len(idx) // MAX_PIXELS_PER_PACKET + 1

55,57c71
<     if (p!=_prev_pixels).any():      # only send if something changed!
<       for packet_indices in idx:

for packet_indices in idx:

61,62c75
<                 m += chr(p[0][i]) + chr(p[1][i]) + chr(p[2][i])

            m += chr(i) + chr(p[0][i]) + chr(p[1][i]) + chr(p[2][i])

64c77
<                 # m.append(i)  # Index of pixel to change

            m.append(i)  # Index of pixel to change

Works just fine with my 2811 strips.
Best,     Stefan

Sorry about the formatting. The < lines are my code changes, the quoted code blocks are the original lines.

thks sir:) sorry for being this late i was on busy due school. i just came back to do some experiments with this kind of strips and i faced another issue, the ws2811 works with 12v but the esp with 3.3v. what do you do to feed both devices with the same power source? it would be very helpful men, thank u in advance

What esp module are you using?

nodemcu V3.0 i think is the esp-12e
El lun., 27 de mayo de 2019 21:30, Joey Babcock<EMAIL_ADDRESS>escribió:

What esp module are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scottlawsonbc/audio-reactive-led-strip/issues/206?email_source=notifications&email_token=ALHKYG7APXZLDMXMK2BE4EDPXSKNBA5CNFSM4HHIBIF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKZNLQ#issuecomment-496342702,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHKYG3NIHOF3OXJCRNMJC3PXSKNBANCNFSM4HHIBIFQ
.

Try using a logic level converter for that if its 12v or are you saying that you want to power the esp using the same supply as the LED strip? If that is the case, just use a converter.


Enable report on hardware executions

As pointed out by @agebbie, we need to be able to report on hardware executions generated from the Textbook.
The strategy could be similar to what was deployed to distinguish local jobs from jobs run in using Quantum Labs: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/qiskit/providers/ibmq/api/session.py#L227

Can we use the same header instrumentation used for jobs run in quantum labs so that when the binder is initialized we update the Qiskit provider header with learn.qiskit.org for both the scratchpad and for all code cells running on hardware?

@Tansito pointed out:

About the job it seems we are going to need to find a way to setup an environment variable in mybinder (probably using os.environ in the code-cell we will be able to do it, cc: @vabarbosa or @korgan00 for ideas here).

Pull requests:

[ ] https://github.com/Qiskit/platypus-binder/pull/15
[ ] https://github.com/Qiskit/platypus/pull/1360

@eddybrando what additional info is needed here?

@eddybrando what additional info is needed here? it has the needs information label, just want to make sure i am not missing anything?

I think it's now clarified with your comment. 🙂
We just needed to be sure about the way to proceed here.

after further discussion (in Slack), there are uses cases in the near future where option (1) would be preferred.
with that said, i propose doing both! having both would ensure if there are any issues with (1) or if there are any pages where (1) is not in added then it would default to (2).
2- https://github.com/Qiskit/platypus-binder/pull/15
1- https://github.com/Qiskit/platypus/pull/1359
and we can easily close out either PR is anyone has any strong opinion against both

This is working in staging! Excellent work everyone


Section 2.2 changes

Changes justified inline.

I also have a few questions regarding this section.

Section 2.2.1 mentions:

Pre-installed SDEs have two distinguishing characteristics:

* These keys may persist over a factory reset; and
* They may not be accessible to administrators.

The word "may" here seems to imply that these characteristics are not always applicable. Is that the intent?

Table 1 mentions from parsed or generated SDEs for the Provision service. Are SDEs implicitly generated as part of this service? There doesn't seem to be any other conceptual service that does the generation.
Section 2.2.4 distinguishes between pre-provisioned/pre-installed (OB.P_SDO) and transient SDOs (OB.T_SDO). What type of object would SDOs be when stored internally to the DSC, persistent across reboots, but not pre-installed by the manufacturer? Would they fall under OB.P_SDO or OB.T_SDO?
Are all DSCs expected to assign all SDO.* attributes to all SDOs?
Regarding OP.Import, the document says The Admin may also give the DSC Authorization Data. What does this refer to? Wouldn't all CApps be able to supply Authorization Data to the DSC, for authentication purposes? Or is this referring to default Authorization Data or Authorization Data for other Users?

Section 2.2.1 mentions:
Pre-installed SDEs have two distinguishing characteristics:

These keys may persist over a factory reset; and
They may not be accessible to administrators.
The word "may" here seems to imply that these characteristics are not always applicable. Is that the intent?
[SP: Yes, that is the intent.  There are some factory resets that intentionally erase important public firmware verification keys that intentionally brick the device.  But that is an unusual circumstance.]

Table 1 mentions from parsed or generated SDEs for the Provision service. Are SDEs implicitly generated as part of this service? There doesn't seem to be any other conceptual service that does the generation.
[SP: SDEs may be implicitly generated, but it's not required.]
Section 2.2.4 distinguishes between pre-provisioned/pre-installed (OB.P_SDO) and transient SDOs (OB.T_SDO). What type of object would SDOs be when stored internally to the DSC, persistent across reboots, but not pre-installed by the manufacturer? Would they fall under OB.P_SDO or OB.T_SDO?
[SP:  This sounds like they are persistent objects, so OB.P_SDO]
Are all DSCs expected to assign all SDO.* attributes to all SDOs?
[SP:  The SFRs are written that way.  The commercial vendors who were participating at the time didn't seem to have a problem with it, so we left it worded that way.]
Regarding OP.Import, the document says The Admin may also give the DSC Authorization Data. What does this refer to? Wouldn't all CApps be able to supply Authorization Data to the DSC, for authentication purposes? Or is this referring to default Authorization Data or Authorization Data for other Users?
[SP:  The first part of the paragraph refers to how the DSC receives objects from apps and external storage.  This phrase refers to what the DSC receives from Admins.  Inconsistent grammar.]


Logic error in new load test script cuts web clickstreams parquet output in half

Currently, we split the load test / parquet file generation for the web_clickstreams table into two stages and write to parquet for each stage. This causes the first half of the table to be overwritten, finishing with only 50% of the expected output.
Note that this script was not used to generate the SF1K and SF10K data we've been using to benchmark, but would be used going forward. This means all existing benchmark times are still accurate.
We'll need to update this to make sure we don't accidentally create incorrect tables.

We also need to update this to use the new tpcxbb_argparser. Looks like this slipped through the cracks


Add highlighting on preview elements click

Current dependencies on/for this PR:

main

PR #113   👈

This comment was auto-generated by Graphite.


Ever increasing js heap

Firstly, thanks for the fantastic library! I just wanted you to take a look at this recording of js heap size.

My understanding is probably wrong, but I would have expected on each garbage collection the js heap to be brought down to it's initial size. It is only the forced gc right at the end of the recording that does that. I just wondered what is happening here, why, and if it is expected?

As long as the memory usage does return to a base value when forcing the GC, there shouldn't be any memory leaks.
But memory is something I'm always paying attention to and complicated to manage, so I might be wrong.

Here's another recording, this time with 5 separate similar animations running simultaneously - so way more happening.

This one more regularly makes it down close to the initial size.


nRF52: add support for PPI peripheral

Summary
Add support for PPI peripheral in nRF52
Impact
Add new feature
Testing
Used PPI and works as expected.

If it is no problem I would prefer to leave them. I'm upstreaming parts of my ongoing work by cherry picking to a separate branch to later rebase my feature branch on top of master. If I squash rebase will fail to identify same commits. I'm still trying to find a way to handle this as I always have this problem.


Cant authorize my ip

Everytime i try to acces the page it says my ip isnt authorized i added it multiple times and also deleted the entire allowed ip's part but it just doesnt work

Issue has been solved but now i got a different problem. When i upload a file using ShareX it will make the url: http://(mydomain).xyz/release/release/u/(FileName) it ads 1 extra /release for no reason and ive been messing arround wit the config for some time but i cant seem to fix it.

Issue has been solved but now i got a different problem. When i upload a file using ShareX it will make the url: http://(mydomain).xyz/release/release/u/(FileName) it ads 1 extra /release for no reason and ive been messing arround wit the config for some time but i cant seem to fix it.

@IamN4m3l3ss What is your base URL set to?

@IamN4m3l3ss What is your base URL set to?


Fix USE_ITEM using correct item. Fix SPAWN_OBJECT velocity.

This still does not fix the arrows, but we're closer now!

You're using if (data > 0) this does not seem correct See http://wiki.vg/Object_Data
Also brackets look a bit off, might just be github web :) (same line please <3)

I'm sorry for my brackets, I'm used to using them like that, but I'll try to keep it to your markup.
For The data > 0< it's from the minecraft 1.8 source code:
this.a = paramPacketDataSerializer.e();
this.j = paramPacketDataSerializer.readByte();
this.b = paramPacketDataSerializer.readInt();
this.c = paramPacketDataSerializer.readInt();
this.d = paramPacketDataSerializer.readInt();
this.h = paramPacketDataSerializer.readByte();
this.i = paramPacketDataSerializer.readByte();
this.k = paramPacketDataSerializer.readInt();
if (this.k > 0)
{
  this.e = paramPacketDataSerializer.readShort();
  this.f = paramPacketDataSerializer.readShort();
  this.g = paramPacketDataSerializer.readShort();
}

This is the processing for the PacketPlayOutSpawnEntity in 1.8, but in 1.9 the 3 shorts for velocity are always written to the packet, independent of the data.
So If you receive a packet from 1.8, it may or may not contain the last 3 shorts.


Issue regarding popping pages

Thanks for this package, however i face an issue here, i have an app with a signup screen after which the screen with custom Scaffold appears(with the bottom Navbar), in there in my bottom Navbar i have four items, if i am currently in the first screen i.e., the HomePage(corresponding to the first item in Navbar) and i navigate to some other screen on pressing a button(say) which is in the HomePage , the bottom Navbar works perfectly and it remains in the navigated screen, but if i use my androids back button it will go directly to the signup page and not to the HomePage as it should, however if i use the backbutton in the appbar it will go to Homepage as intended, i dont know if everyone is facing this issue or i am the only one??

ok thanks!

ok here's how i solved the same issue using this CustomNavigator and WillPopScope.
you can checkout this medium article  ------> by Andrea Bizzotto
_https://medium.com/coding-with-flutter/flutter-case-study-multiple-navigators-with-bottomnavigationbar-90eb6caa6dbf_
bonus: using this method also preserves the page state--- meaning when you navigate to page 1 and you open page1 detail page, then you go to say page 2... it ensures the detail page of page 1 remain as you left it (The detail page still opened)
`
class MyHomePage extends StatefulWidget {
final String title;
const MyHomePage({Key key, this.title}) : super(key: key);
@override
_MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
int _currentIndex = 0;
@override
Widget build(BuildContext context) {
return WillPopScope(
onWillPop: () async {
final isFirstRouteInCurrentTab =
!await navigatorKeys[_currentIndex].currentState.maybePop();
if (isFirstRouteInCurrentTab) {
// if not on the 'main' tab
if (_currentIndex != 0) {
// select 'main' tab
setState(() {
_currentIndex = 0;
});
// back button handled by app
return false;
}
}
// let system handle back button if we're on the first route
return isFirstRouteInCurrentTab;
},
child: Scaffold(
bottomNavigationBar: BottomNavigationBar(
items: _items,
onTap: (index) {
setState(() {
_currentIndex = index;
});
print(index);
},
currentIndex: _currentIndex,
),
body: Stack(
children: [
_buildPageOneOffstage(navigatorKeys[0], 0),
_buildPageTwoOffstage(navigatorKeys[1], 1),
_buildPageThreeOffstage(navigatorKeys[2], 2),
],
)),
);
}
Widget _buildPageOneOffstage(GlobalKey key, int index) {
return Offstage(
offstage: _currentIndex != index,
child: CustomNavigator(
navigatorKey: key,
home: Page(title: 'Page $index'),
pageRoute: PageRoutes.materialPageRoute,
),
);
}
Widget _buildPageTwoOffstage(GlobalKey key, int index) {
return Offstage(
offstage: _currentIndex != index,
child: CustomNavigator(
navigatorKey: key,
home: Page(
title: 'Page $index',
),
pageRoute: PageRoutes.materialPageRoute,
),
);
}
Widget _buildPageThreeOffstage(GlobalKey key, int index) {
return Offstage(
offstage: _currentIndex != index,
child: CustomNavigator(
navigatorKey: key,
home: Page(title: 'Page $index'),
pageRoute: PageRoutes.materialPageRoute,
),
);
}
final navigatorKeys = [
GlobalKey(),
GlobalKey(),
GlobalKey(),
];
final _items = [
BottomNavigationBarItem(icon: Icon(Icons.home), title: Text('home')),
BottomNavigationBarItem(icon: Icon(Icons.event), title: Text('events')),
BottomNavigationBarItem(
icon: Icon(Icons.save_alt), title: Text('downloads')),
];
}
`

@IMEF-FEMI  Thank you so much!! It works perfect now


Trying to access incomplete dataset will crash instead of displaying error

Delete Katrina_data/data/U10 folder
Open Katrina
Add renderer and select U10
Segfault

I've created a branch, issue_731, and fixed the problem for the 2D data and partially fixed the Barb renderer. Other renderers and tools still do not recover from a missing variable. I'm kicking this over to Sam and Stas to address the following:
Sam: Statistics
Sam: Plot
Stas: Contour
Stas: Barbs
Note: all renderers/tools should generate an appropriate error message when a selected variable is not present AND recover and work correctly if the offending variable is subsequently changed to a valid variable (Barbs does the former, but not latter).
Note: The is a Renderer::VariableExists() method that can be used to check to see if selected variable(s) are present. Note also, the return from GetGrids() should always be checked for a valid (non-NULL) return.

Update 4/30/2018:
I've updated the branch to improve on Plot and Statistics tools with a series of commits till d4fb2f1.

2D data is not fixed @clyne:

Open Katrina with V10 removed
Add and enable TwoDData renderer
Select V10

Vapor may crash immediately or after performing some actions.

@StasJ 2DData is working fine for me. However, both contour and barbs renders are still problematic. Following the same instructions for reproducing, and enabling the contour renderer results in an immediate crash.
The Barb renderer doesn't crash, but it can't recover either: if you change the invalid variable to a valid one (e.g. set both X & Y components to U10) the app continues to generate error messages

Hmm maybe there is something wrong with my build elsewhere. I didn't push
my changes for barbs and contours yet. I'll try a clean build but if that
doesn't help I'll show you what's is happening.
On Wed, May 2, 2018 at 8:18 AM clyne<EMAIL_ADDRESS>wrote:

@StasJ https://github.com/StasJ 2DData is working fine for me. However,
both contour and barbs renders are still problematic. Following the same
instructions for reproducing, and enabling the contour renderer results in
an immediate crash.
The Barb renderer doesn't crash, but it can't recover either: if you
change the invalid variable to a valid one (e.g. set both X & Y components
to U10) the app continues to generate error messages
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/VAPOR/issues/731#issuecomment-385993523, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACpOzxRVcvaOQ_FhAfBitjPG0-arbrYlks5tucAbgaJpZM4TkO-N
.

TFWidget::getRange does not check if the returned Grid is valid @clyne

Problem with ErrorReporter has been fixed (the dialog box was made modal to suspend the event loop).
One problem still remains: Barbs don’t recover after an invalid variable has been selected. If you change the offending variable to a valid one you will continue to get OpenGL errors.

Vapor is still crashing for me upon the following procedure :(

Open Katrina with V10 removed
Add and enable TwoDData renderer
Select V10

When I run this on my Mac it does not crash. However, the ErrorReporter is printing an error message to the terminal:
Uknown Messagebox role -1
@StasJ please take a look at this.

I changed the popup logic to run on the gui thread. This should fix it. @clyne


@astrojs/vercel/static or @astrojs/vercel/server make jampack unusable

Hello,
I have this error when I build my website : Failed to create _jampack folder.
I use the last version of Jampack and you can fork my project to execute the error here
Tell me ifI can help to fix this with more information

Hi!
When jampack runs on your folder, it creates a _jampack folder and optimizes all content.
You should not try to run jampack twice on the same folder.
Recommendation is: always run jampack on a freshly build output.
I will update the error message to: "static website already optimised with jampack" or something like this.

Message updated in 0.24.4

Okay, but I delete the folder locally, and when I deploy it on vercel, I have the same message.
Please don't close my issue, it's not completed

So, like I said, with the last update, I delete the jampack folder from my target, I build and it's failing with the error "Folder _jampack is present in target folder. This means that jampack has already processed this folder. You should always run jampack on clean build of the static website.".

Looking at your package.json https://github.com/No1ceTea/no1cekeebs/blob/47-vercel-web-analytics-doesnt-work/package.json#L7
I guess npm build is called multiple times in the process.
astro check and astro build are fine to work incrementally but not jampack.
To make sure you always jampack a clean build you can do:
"build": "rm -fr ./dist && astro check && astro build && jampack ./dist"
But I don't know if you want to run jampack on every build.
Maybe you should only run jampack on deploy only.
I'm not familiar enough with @astro/vercel deployment process to recommend something else.


HTTP/2 conformance - h2spec failures

I'm using the h2spec program (https://github.com/summerwind/h2spec) and running the following command:
./h2spec -S -t -h caddyserver.com -p 443

This shows the following results:
146 tests, 137 passed, 0 skipped, 9 failed

The actual failures are given below. Now to be fair most of these tests are about how to handle bad client requests and give the correct error response. So not super critical TBH. In an ideal world clients shouldn't send these types of requests and so there is no issue. Of course we don't live in an idle world...
Anyway thought it worth raising in case you wanted to fix.
Failures:

Hypertext Transfer Protocol Version 2 (HTTP/2)
  4. HTTP Frames
    4.2. Frame Size
      × 3: Sends a large size HEADERS frame that exceeds the SETTINGS_MAX_FRAME_SIZE
        -> The endpoint MUST respond with a connection error of type FRAME_SIZE_ERROR.
           Expected: GOAWAY Frame (Error Code: FRAME_SIZE_ERROR)
                     Connection closed
             Actual: DATA Frame (length:0, flags:0x01, stream_id:1)

  5. Streams and Multiplexing
    5.1. Stream States
      × 11: closed: Sends a DATA frame
        -> The endpoint MUST treat this as a connection error of type STREAM_CLOSED.
           Expected: GOAWAY Frame (Error Code: STREAM_CLOSED)
                     Connection closed
             Actual: RST_STREAM Frame (length:4, flags:0x00, stream_id:1)

  6. Frame Definitions
    6.9. WINDOW_UPDATE
      6.9.1. The Flow-Control Window
        × 3: Sends multiple WINDOW_UPDATE frames increasing the flow control window to above 2^31-1 on a stream
          -> The endpoint MUST sends a RST_STREAM frame with a FLOW_CONTROL_ERROR code.
             Expected: RST_STREAM Frame (Error Code: FLOW_CONTROL_ERROR)
               Actual: RST_STREAM Frame (length:4, flags:0x00, stream_id:1)

      6.9.2. Initial Flow-Control Window Size
        × 2: Sends a SETTINGS frame for window size to be negative
          -> The endpoint MUST track the negative flow-control window.
             Expected: DATA Frame (length:1, flags:0x00, stream_id:1)
               Actual: Timeout

  8. HTTP Message Exchanges
    8.1. HTTP Request/Response Exchange
      8.1.2. HTTP Header Fields
        <IP_ADDRESS>. Connection-Specific Header Fields
          × 1: Sends a HEADERS frame that contains the connection-specific header field
            -> The endpoint MUST respond with a stream error of type PROTOCOL_ERROR.
               Expected: GOAWAY Frame (Error Code: PROTOCOL_ERROR)
                         RST_STREAM Frame (Error Code: PROTOCOL_ERROR)
                         Connection closed
                 Actual: DATA Frame (length:51, flags:0x01, stream_id:1)
          × 2: Sends a HEADERS frame that contains the TE header field with any value other than "trailers"
            -> The endpoint MUST respond with a stream error of type PROTOCOL_ERROR.
               Expected: GOAWAY Frame (Error Code: PROTOCOL_ERROR)
                         RST_STREAM Frame (Error Code: PROTOCOL_ERROR)
                         Connection closed
                 Actual: DATA Frame (length:53, flags:0x01, stream_id:1)

        <IP_ADDRESS>. Malformed Requests and Responses
          × 1: Sends a HEADERS frame with the "content-length" header field which does not equal the DATA frame payload length
            -> The endpoint MUST treat this as a stream error of type PROTOCOL_ERROR.
               Expected: GOAWAY Frame (Error Code: PROTOCOL_ERROR)
                         RST_STREAM Frame (Error Code: PROTOCOL_ERROR)
                         Connection closed
                 Actual: Timeout
          × 2: Sends a HEADERS frame with the "content-length" header field which does not equal the sum of the multiple DATA frames payload length
            -> The endpoint MUST treat this as a stream error of type PROTOCOL_ERROR.
               Expected: GOAWAY Frame (Error Code: PROTOCOL_ERROR)
                         RST_STREAM Frame (Error Code: PROTOCOL_ERROR)
                         Connection closed
                 Actual: WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:0)

HPACK: Header Compression for HTTP/2
  4. Dynamic Table Management
    4.2. Maximum Table Size
      × 1: Sends a dynamic table size update at the end of header block
        -> The endpoint MUST treat this as a decoding error.
           Expected: GOAWAY Frame (Error Code: COMPRESSION_ERROR)
                     Connection closed
             Actual: DATA Frame (length:0, flags:0x01, stream_id:1)

Thanks! I think most of these will need to be fixed upstream in the Go standard library. This is a TODO. (If anyone wants to tackle these, go for it!)

Going to close this since there's not much we can do about it in Caddy.

FYI: I just got bitten by this.
For some weird reason using https://github.com/GoogleChromeLabs/simplehttp2server as development server seems to have worked for me.

It's been mostly fixed upstream, and will be available in Go 1.11 later this month.


Manually set assembly info attribute

Fixes #31862
@roby70 please review.

Internal previews

📄 File
🔗 Preview link

aspnetcore/security/app-secrets.md
Safe storage of app secrets in development in ASP.NET Core

@tdykstra I would also suggest using the same user secret id that VS / dotnet CLI generates when you set up the secrets to ensure consistency.
Otherwise, there could be discrepancies in the developer experience. For instance, when working from VS or the CLI, the file secret.json found in the folder %APPDATA%\Microsoft\UserSecrets\<id from the .csproj tag> is used. However, during debug, the program reads the secrets from the file in %APPDATA%\Microsoft\UserSecrets\<id from the UserSecretIdAttribute>. So if the developer work with the Manage user secrets from Visual Studio, the result is that it works on the wrong file.
This behavior can lead to confusion, as seen in the example on Visual Studio generating new user secrets file even though one is given in assembly attribute.
Thanks for your support

Thanks for reporting this and for assisting with the fix for it, @roby70.


i18n(de): Update editor-setup.mdx

Description (required)

update editor-setup.mdx

Related issues & labels (optional)

#6532
#8238
#8563
#9073

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

de/editor-setup.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Zig 0.13.0 migration

Thanks, but the PR is huge and mixes code changes with fmt, making it difficult to review.
But you're right..so.
There's now a zig-0.13 branch which will work with Zig 0.13.  And both that branch as well as master now have zig fmt applied.


Updated README.md

Removed some links which were not responding correctly.

I have updated README.md and removd some links which were not working properly!!

@danishanwar, I'm sorry I can't accept this pull request. We already have a pull request to fix those links
https://github.com/Roshanjossey/first-contributions/pull/845


Could you list the differents between you codes and official faster rcnn?

Hi ,your project is cool.
I plan to write a faster rcnn project with gluon.
I want to use your code for reference,could you list the differents between you codes and official faster rcnn?

Get the same question here.

Thank you for your attention! I am sorry that I was too busy last month and reply so late.
The major difference is that I use gluon rather than caffe.
Some tricks to improve the performance are ignored. For example, multiply the regression term to 10 times in RCNN branch. It is just a project for fun, but not a serious re-implementation.


Create project landing page

Create Landing page
This landing page doesn't necessarily need to be for RH6. But it should contain some information about the project, in some form or fashion.


Adds Localistico

Thank you! Can you add a company profile? Merging this as-is, however.

Sure, done!


Update ubpf and address breaking change

Description
uBPF had a breaking change in ubpf_register. This picks up the latest version of uBPF and resolves the breaking change.
Testing
CI/CD
Documentation
No.
Installation
No.

Blocked on https://github.com/iovisor/ubpf/issues/418


DO NOT MERGE! Fast Forward stable to 45918c70b5beed5c2b68dd828b76279d21918e88.

This PR will be merged automatically once checks are successful.

This change is

Jenkins job mixer/postsubmit passed

Jenkins job mixer/postsubmit passed

Jenkins job mixer/e2e-suite passed


SteamVr Crashing on connection to headset

When I launch the latest version of alvr and try to connect to steamVR, it says that an unexpected fatal error has occurred, and when I restart steamVR, it blocks the alvr server addon. Another thing with the older versions of alvr is that they either have the ringing audio, or wont launch on the headset.

Also, how do i limit a G635 to using only 2 channels?


⚠ Bofrost.at has degraded performance

In 1c85da6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1590 ms

Resolved: Bofrost.at performance has improved in 4d3cc0c.


Automatically-generated passwords don't show up anywhere?

If you get an automatically-generated password for the admin account by leaving out the "-p" flag in "canasta create", the password that's generated doesn't seem to appear anywhere - so as far as I know it's lost forever. (If it does get stored somewhere, it would be good to know where - so that this can be noted in the documentation, and probably the CLI output as well.)

The automatically-generated password for the admin account is currently not accessible anywhere. The only way to access them is if one opt to use verbose mode when running the create command. It does print out the password when running the “maintenance/install.php” as an argument.
What could be a good option, just to print it on the terminal or to save it into a file?

Yeah, saving it in a file seems good.
The CLI use the "maintenance/install.php" to setup the Wiki. The full command would look like
php maintenance/install.php --dbserver=db  --confpath=/mediawiki/config/ --scriptpath=/w	--server='https://localhost' --dbuser='root' --dbpass='mysql' --pass='wikipassword' 'My Wiki' 'admin'

https://www.mediawiki.org/wiki/Manual:Install.

Oh, now I understand what you mean - the password is the argument.

Is this documented? Where should the feature be documented?
If you choose to have Canasta generate an admin password for you, you will find it in a file named .admin-password

Its not documented yet. It could be documented at Canasta-Documentation/setup.md

If you choose to have Canasta generate an admin password for you, you will find it in a file named .admin-password

Yes, you are right.


HIVE-16391: Add a new classifier for hive-exec to be used by Spark

This fix adding a new classifier for hive-exec artifact (core-spark), which is specifically used for Spark. Details in SPARK-20202.
This is because  original hive-exec packages many transitive dependencies into shaded jar without relocation, this makes conflicts in Spark. Spark only needs to relocate protobuf and kryo jar. So here propose to add a new classifier to generate a new artifact only for Spark.

CC @steveloughran

I think we also had to change the kryo version used to get bits of the API it in sync with what twitter's chill depended on. has that been fixed in spark now?

I'm not clearly sure about your mentioned issues, can you please explain more and point me to the JIRA?

SPARK-8064 was the big troublespot, but SPARK-14435 implies that spark 2 & hive may be in sync with kryo versions, so that bit of the fork isn't needed any more. Which means that the diff between spark's hive JAR and the ASF one is now down to shading, not the version of Kryo which hive was built with


How to make an interactable continuous slider

Create a slider that is like a volume control that can be slid between certain limits to control a float value.

https://www.youtube.com/watch?v=cKpXwxFQGT4


Interact with mail app using URI.

For example when trying to create an event or send an email.

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

ID: f98f38c4-4a00-19b4-e813-bee6ffe03a9b
Version Independent ID: 9a9770aa-8255-eeb8-7351-63b6ec712ada
Content: Launch an app with a URI - Windows UWP applications
Content Source: windows-apps-src/launch-resume/launch-app-with-uri.md
Product: uwp
GitHub Login: @eliotcowley
Microsoft Alias: elcowle

Thanks for the comment, and sorry for the delay in addressing it. We do read bugs as they come in, but may not add comments immediately, which gives a poor impression - I apologize.
In this case, your comment wasn't immediately clear and so it wasn't assigned to an owner for them to address. Is there a specific problem with the docs we can fix?  thank you
-John

In the meantime, here is a link that might help: https://docs.microsoft.com/en-us/windows/uwp/launch-resume/launch-default-app
Please reopen the bug is something else is required. thanks!


Node positioning problem fix

During node creation there was a problem of positioning created node. It spawned node at the mouse position at the time of creation.
Fixed that by spawning new node at context menu position.
Changes: Added variable Vector2 contextMenuPos that holds mouse position at the moment of creating context menu (only when clicked on the empty canvas).
Changed spawning position of new node to that position
PS Really sorry for bad English

Can you replace the indentation with tabs instead of spaces? It's the default of this project.

Visual Studio automatically puts spaces instead of tabs.
I replaced them, it should be fine now


Fix capitalization typo in release notes

TensorFLowInferenceInterface had an incorrectly capitalized "L" in it.
While doing it, I formatted a couple of package names as code (since others seem to be).

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Closing so I can reopen it while logged into the Google account which I have signed the Contributor License Agreement from.


Update check-uk-visa Taiwan transit outcome

PT story: https://www.pivotaltracker.com/n/projects/1270592/stories/106095812
I've split the "outcome_transit_taiwan" into two: one for visitors passing through UK Border Control and one for visitors not passing through UK Border Control. I've then made the requested changes to the outcome shown when visitors from Taiwan are transiting and passing through UK Border Control.
Factcheck

Taiwan - Transiting and passing through UK Border Control

Expected changes

URL on gov.uk

Multiple changes to "Transiting without a visa"

Before

After

I've just rebased on master and force-pushed now that PR #2100 has been merged.

I've rebased on master, resolved a couple of minor conflicts and force pushed.

I've asked @lutgendorff whether we've heard anything back from factcheck about this PR.

I've just rebased this with master and forced pushed, has been given the 'good to deploy' from fact check


Move to commons 0.8.0 and match parent pom version.

This transitively updates the c* and driver version's to 3.0.9 and 3.0.5, respectively.
@lucasponce It looks like we'll need to update to the latest commons to match Hservices infrastructure (c* driver version).  We'll probably need a release fairly soon, to allow for Hmetrics to do the same.  Either a 1.3.x or a 1.4.0 version, we can discuss which one we prefer.
cc @stefannegrea

+1

Either a 1.3.x or a 1.4.0 version, we can discuss which one we prefer.

Our original plan was to reach 1.0.0 with a feature completed and from 1.x to include small enhancements and focus on performance improvements which is where we are focus these days.
I'm more to bump into a 1.4.x version. I should consider performance enhancements as relevant as new features, we can leave the micro version for bugfixes only (I think).


Adding Dynamics On/Off

Thank you for developing this project.
I have a request reagrding the Dynamics of a channel.
Is it possible to trigger the On/Off Button from the Dynamics of a channel?
Something like: InCh/Dyna1/OnOff

Hello;
The commands available are the ones that Yamaha has implemented with their SCP protocol. If you don’t find the command you want, it’s because Yamaha didn’t implement it.
To do what you want, you should use the Yamaha-MIDI module, available in my custom companion build. You can download it from my web site: discourse.remotely-possible.com


translate-attr is not getting interpolated with translate-value-some-var directives

If you use the translate-value-something directive, your values don't get in to the translate-attr keys. Works fine with if you stick with translate-values, but we prefer the  translate-value-syntax, if we can use it.
Environment

version of angular-translate: v2.13
version of angular: v1.4.8
which browser and its version: Chrome 53 Mac

Steps to reproduce
Here's a simple plnkr to prove it: https://plnkr.co/edit/H72uqf
Expected behaviour
translate-value-something="{{ thatThing }}" should work exactly like
translate-values="{'something': thatThing}"
Actual behaviour
The interpolated values from translate-value-var are not available to the translate-attr directive.

I think I see how I might implement this but let me run it past you:
Within the translate-attr directive, you're watching the translateValues attr for updates.
If I did an Object.getOwnPropertyNames(attr) and started watching anything that started with translateValue I should be able to feed those values in.
Does that sound about right?
I've had no 👍  on this so I'm not sure its worth the effort, but I'd live to give a little back here so I may do it.

@jakefreeberg  Yeah, the directive angular-attr is missing support for the translate-value-xyz attributes. Overseen..

Maybe the internal should be adapted like in the translate directive..


In ObjectFilter.endsWith uses StartsWith instead of EndsWith

I think there is an issue withe the criterion endsWith.
At line 335 of ObjectFilter
return fieldValue.toString().startsWith(value.toString());
instead of
return fieldValue.toString().endsWith(value.toString());
Thanks

thanks

I will fix it.


Add babel-plugin-transform-exponentiation-operator

Motivation
React Native's babel preset should include support for the exponentiation operator (**).
The exponentiation operator is a stage 4 (accepted/finished) proposal,
it should be supported by default.
Currently React Native will give a very unhelpful error if any code includes the
exponentiation operator.

To make things worse the exponentiation operator is supported in chrome.
So what can happen is that people will test their code using remote debugging
ship it, and at some later point someone will notice it doesn't work on a device
or in the simulator with remote debugging disabled. Depending on how long ago
the merge was they may even have to do a git bisect.
See: https://github.com/facebook/react-native/issues/11371
Test Plan
Not sure if this should have tests since the rest of the babel plugins are not tested
within React Native.

LGTM
@lacker (or whoever is looking at issues next week) - could you merge this if it looks good to you and you have no reservations?

Mmmmm ok fine.

Anything I can do to move this along?
From what I understand babel-preset-react-native should be updated, published, and then updated in the dependencies of react-native.

Sorry about the delay. I tried importing this to the internal fb codebase where we use a yarn.lock file. It looks like this version of the transform adds additional versions of babel-runtime, babel-traverse and other modules we didn't use before. Is there a way to use a version that doesn't pull in more dependencies into RN?
Existing:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  version "6.21.0"
  resolved babel-traverse-6.21.0.tgz#69c6365804f1a4f69eb1213f85b00a818b8c21ad
  dependencies:
    babel-code-frame "^6.20.0"
    babel-messages "^6.8.0"
    babel-runtime "^6.20.0"
    babel-types "^6.21.0"
    babylon "^6.11.0"
    debug "^2.2.0"
    globals "^9.0.0"
    invariant "^2.2.0"
    lodash "^4.2.0"

Added with this PR:
<EMAIL_ADDRESS>  version "6.23.1"
  resolved babel-traverse-6.23.1.tgz#d3cb59010ecd06a97d81310065f966b699e14f48
  dependencies:
    babel-code-frame "^6.22.0"
    babel-messages "^6.23.0"
    babel-runtime "^6.22.0"
    babel-types "^6.23.0"
    babylon "^6.15.0"
    debug "^2.2.0"
    globals "^9.0.0"
    invariant "^2.2.0"
    lodash "^4.2.0"

Existing:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  version "6.20.0"
  resolved babel-runtime-6.20.0.tgz#87300bdcf4cd770f09bf0048c64204e17806d16f
  dependencies:
    core-js "^2.4.0"
    regenerator-runtime "^0.10.0"

With this PR:
<EMAIL_ADDRESS>  version "6.23.0"
  resolved babel-runtime-6.23.0.tgz#0a9489f144de70efb3ce4300accdb329e2fc543b
  dependencies:
    core-js "^2.4.0"
    regenerator-runtime "^0.10.0"

I'm not sure I understand how yarn works, and whether these changes in yarn.lock actually mean we pull in a new version of babel-runtime. Asked @bestander to comment here.

Possibly switching to use version 6.5.0 like the other babel transforms.

OK thanks for doing that!

Importing again.

This one hasn't landed due to the conflicts in babel-preset/configs/main.js.

I accidentally closed this somehow while resolving the conflict, didn't mean to do that. I put up another PR here with the original author on the commit and the merge conflict resolved: https://github.com/facebook/react-native/pull/16191


Create el.js

This is the translation in the Greek language

@pepelucci thank you a lot! 🤗
It's merged and deployed. You can test it either by coming to xroom.app with a Greek as default language of your browser or simply via https://xroom.app/?lang=el


Isn't working with the latest updates

@jonathan-bird Just started working with this packages, but doesn't seem to work with the latest updates from oseintow/laravel-shopify. The latest release of oseintow/laravel-shopify doesn't include the changes for multiple apps

He just needs to release the current dev master branch to a tag and it'll
work. I sent him a message.
On 14 May 2017 6:01 am, "Abishek R Srikaanth"<EMAIL_ADDRESS>wrote:

@jonathan-bird https://github.com/jonathan-bird Just started working
with this packages, but doesn't seem to work with the latest updates from
oseintow/laravel-shopify.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/culturekings/shopify-app-auth-laravel/issues/1, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABcKcSf4l-maCeUG7DdgM1WMYuwsXK2Rks5r5gwOgaJpZM4NaLWl
.

Thank you, in the meantime, I am using the forked build till this is solved.


how to set authentication (non admin) on attached MongoDB

Hi,
I try to connect to a remote MongoDB, I configure the url as mongodb://<hostname>:<port> and the db is listed but I see
not authorized on admin to execute command { listDatabases: 1 }

And that it expected, because I should use an dedicated account "username:password".
I tried mongodb://<username>:password@<hostname>:<port> without success.
How can define the authentication to use for connection ?
(Sorry I didn't find the response during search in the issues)

Hi @davidB , this looks like a permissions issue on the remote DB.  Do you know if the remote DB is configured to allow your account to query?  "listDatabases" is one of the rights that can be assigned so the error suggests you don't have this right.
If you haven't already, try to connect via the mongo CLI.

I'm allowed to connect  with a dedicated user with access only on my db, but I'm not allowed to connect as "admin" without password.
My question is own to define the username and password to use for connection.
(I used this account from my code, and an other client)

it works when I define the only db I can see.
mongodb://<username>:password@<hostname>:<port>/<db>

Sorry for noise, Thanks for your time

Excellent!  I think that might be because your user is defined on that DB.  Do you know if your configuration is using an authorization DB?  For instance, my admin DB is used as the authorization source so my mongo DB URL looks like this:
mongodb://<username>:<password>@<host>:<port>/?authSource=<auth_db_name>
This allows me to specify the authentication DB in the URL so the driver knows how to authenticate me.  Useful when you want to maintain users and roles in one place.

The user/password is not defined into an authorization DB.
On Thu, Jun 7, 2018 at 9:21 PM Troy High<EMAIL_ADDRESS>wrote:

Excellent! I think that might be because your user is defined on that DB.
Do you know if your configuration is using an authorization DB? For
instance, my admin DB is used as the authorization source so my mongo DB
URL looks like this:
mongodb://:@:/?authSource=<auth_db_name>
This allows me to specify the authentication DB in the URL so the driver
knows how to authenticate me. Useful when you want to maintain users and
roles in one place.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-cosmosdb/issues/668#issuecomment-395535415,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAps285pKKau3VSnCuP28sBa1qLsRScks5t6X0qgaJpZM4UeX2F
.


Publish releases on crates.io

See #59
Pipeline code taken from https://github.com/EmbarkStudios/tryhard/blob/main/.github/workflows/rust-ci.yml

Have you thought about syncing git tag with Cargo crate version in Cargo.toml?
My worry is that the tags and version in Cargo.toml can get out of sync. At the very least, we should check if they are in sync before publishing.

Have you thought about syncing git tag with Cargo crate version in Cargo.toml?

Nope, but it's a great idea. Not sure how to do this, though. Are there any other projects that do that already that we can learn from?

Not sure how to do this, though. Are there any other projects that do that already that we can learn from?

I can do some research into it. Not a blocker for this PR though.

Thanks, then I'll merge it.
I think I'll add support for binary releases to Github, too and then cut a new 0.4.0 release.


Update and add missing info and pages to the docs

Tutorial
Status: Already exists, needs updated
Link: https://github.com/grommet/grommet-starter-new-app

remove use of normalize color (we don't want to encourage people to use util functions we don't document)
not critical but would be nice to upgrade to the latest version of packages (the project is using react 16 and grommet 2.0.1)

Theming
Status: Already exists, needs updated
Link: https://github.com/grommet/grommet/wiki/Grommet-v2-theming-documentation
We should include information on the following:

Dark and Light mode
How to extend the theme
Styled components info
How to use ThemeContext

Need to update the following:

Change the format of the global theme properties, currently they are laid out in a chart with the entry, purpose, type, default value, and affected components. This chart is out of date, is difficult to maintain, and I think we can find a more effective way to share info about the available global theme properties.

Color properties
Status: Already exists, needs updated
Link: https://github.com/grommet/grommet/wiki/Color-Properties

remove 'new' headings
I think the information on this page could be more concise to increase readability.

Responsive behavior
Status: Doc doesn't exist

Explanation on breakpoints

Internationalization
Status: Doc doesn't exist
We should include explanations on the following:

RTL
messages

Looks great, I like the direction it is heading.
I've seen some questions about how to use styled components with grommet and it might be nice to share some best practices and examples on how the two works side by side.
I'm also thinking maybe an Accessibility focus page that can contain the grommet's best practices for accessibility or the grommet's roadmap for accessibility improvements. It can demonstrate our strong intent on improving accessibility.
One last thing that comes to my head is Testing, and maybe we'd like to add a page that lists our current testing mechanisms (snapshots jest/chromatic, axe-tests, ts testing...) most importantly list any current gaps in testing that will be open to ideas or contributions, areas such as Keyboard navigation, in-depth functional testing, any tsx gaps and more...

I've seen some questions about how to use styled components with grommet and it might be nice to share some best practices and examples on how the two works side by side.

Yes I agree. Right now I have styled components info organized under the theming page. But I considering if styled components should be a separate page.

I'm also thinking maybe an Accessibility focus page that can contain the grommet's best practices for accessibility or the grommet's roadmap for accessibility improvements. It can demonstrate our strong intent on improving accessibility.

Love this idea! I think it would be great to give a little info on accessibility within grommet, and possibly link to some external accessibility sources.

One last thing that comes to my head is Testing, and maybe we'd like to add a page that lists our current testing mechanisms (snapshots jest/chromatic, axe-tests, ts testing...) most importantly list any current gaps in testing that will be open to ideas or contributions, areas such as Keyboard navigation, in-depth functional testing, any tsx gaps and more...

I'm wondering if we should just add more to the testing section in the contributing guide? Or do you see value in having a separate page for testing?


YARN-11198. clean up numa resources from statestore

Description of PR
YARN-11198
How was this patch tested?
created and tested in emr
For code changes:

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

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m  6s

trunk passed

+1 :green_heart:
compile
1m 43s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 36s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
1m  0s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 48s

trunk passed

+1 :green_heart:
shadedclient
23m 50s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 41s

the patch passed

+1 :green_heart:
compile
1m 31s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 31s

the patch passed

+1 :green_heart:
compile
1m 25s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 25s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 44s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 36s

the patch passed

+1 :green_heart:
shadedclient
23m 37s

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

_ Other Tests _

+1 :green_heart:
unit
23m 22s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

129m  2s

Subsystem
Report/Notes

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

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

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

uname
Linux 795ade98c67f 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2a9226a9cd956669b0f7fa9674472edb5364dcb5

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 18s

trunk passed

+1 :green_heart:
compile
1m 43s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 37s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 51s

trunk passed

+1 :green_heart:
shadedclient
24m 21s

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

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 29s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch failed.

-1 :x:
compile
0m 33s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-server-nodemanager in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

-1 :x:
javac
0m 33s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-server-nodemanager in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

-1 :x:
compile
0m 30s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-server-nodemanager in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

-1 :x:
javac
0m 30s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-server-nodemanager in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 30s

the patch passed

-1 :x:
mvnsite
0m 32s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch failed.

+1 :green_heart:
javadoc
0m 36s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
0m 30s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch failed.

-1 :x:
shadedclient
12m 54s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 33s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch failed.

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

89m 14s

Subsystem
Report/Notes

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

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

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

uname
Linux 9d4588f4ab9d 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 36927ea4546e191d7da5c3b1490777f8a6c33b76

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 32s

trunk passed

+1 :green_heart:
compile
1m 43s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 38s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
1m  0s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 48s

trunk passed

+1 :green_heart:
shadedclient
23m 53s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 43s

the patch passed

+1 :green_heart:
compile
1m 33s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 33s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 30s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager: The patch generated 2 new + 75 unchanged - 0 fixed = 77 total (was 75)

+1 :green_heart:
mvnsite
0m 43s

the patch passed

+1 :green_heart:
javadoc
0m 36s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javadoc
0m 33s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 196 unchanged - 0 fixed = 197 total (was 196)

+1 :green_heart:
spotbugs
1m 34s

the patch passed

+1 :green_heart:
shadedclient
23m 31s

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

_ Other Tests _

+1 :green_heart:
unit
23m 26s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

129m 18s

Subsystem
Report/Notes

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

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

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

uname
Linux ac82db4ad302 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 78bf96aea773eca34045d88338771d3a5d754162

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 13s

trunk passed

+1 :green_heart:
compile
1m 41s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 36s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 50s

trunk passed

+1 :green_heart:
mvnsite
0m 58s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 48s

trunk passed

+1 :green_heart:
shadedclient
26m 58s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
1m 31s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 31s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 44s

the patch passed

+1 :green_heart:
javadoc
0m 36s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 35s

the patch passed

+1 :green_heart:
shadedclient
23m 24s

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

_ Other Tests _

+1 :green_heart:
unit
23m 27s

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

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

131m 49s

Subsystem
Report/Notes

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

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

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

uname
Linux 8e5318eb5ab2 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7e064cf5e38b167a684ff3d89472b5fb11022b1f

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Latest patch looks good, +1.
Will commit it after Jenkins report +1

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 10s

trunk passed

+1 :green_heart:
compile
1m 43s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 37s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
0m 58s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 55s

trunk passed

+1 :green_heart:
shadedclient
24m 35s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 43s

the patch passed

+1 :green_heart:
compile
1m 36s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 36s

the patch passed

+1 :green_heart:
compile
1m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 42s

the patch passed

-1 :x:
javadoc
0m 37s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 98 unchanged - 1 fixed = 99 total (was 99)

-1 :x:
javadoc
0m 33s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 2 new + 196 unchanged - 0 fixed = 198 total (was 196)

+1 :green_heart:
spotbugs
1m 34s

the patch passed

+1 :green_heart:
shadedclient
23m 36s

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

_ Other Tests _

+1 :green_heart:
unit
23m 26s

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

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

129m 51s

Subsystem
Report/Notes

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

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

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

uname
Linux e2c7c0a14363 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9f480066a94d5d928970b8dcb62a4fcc8f3f33e7

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 44s

trunk passed

+1 :green_heart:
compile
1m 43s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 38s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 50s

trunk passed

+1 :green_heart:
mvnsite
0m 59s

trunk passed

+1 :green_heart:
javadoc
0m 58s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 51s

trunk passed

+1 :green_heart:
shadedclient
23m 50s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
1m 29s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 29s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 44s

the patch passed

+1 :green_heart:
javadoc
0m 36s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 34s

the patch passed

+1 :green_heart:
shadedclient
23m 44s

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

_ Other Tests _

+1 :green_heart:
unit
23m 43s

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

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

128m 57s

Subsystem
Report/Notes

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

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

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

uname
Linux 793fcbd36582 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0c2e66d84131a5de684250307c67345bb7514ff6

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
43m 12s

trunk passed

+1 :green_heart:
compile
2m  2s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 56s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m  6s

trunk passed

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m  4s

trunk passed

+1 :green_heart:
shadedclient
26m 49s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
1m 49s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 49s

the patch passed

+1 :green_heart:
compile
1m 39s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 38s

the patch passed

+1 :green_heart:
mvnsite
0m 51s

the patch passed

+1 :green_heart:
javadoc
0m 42s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 39s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 45s

the patch passed

+1 :green_heart:
shadedclient
26m 21s

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

_ Other Tests _

+1 :green_heart:
unit
24m 34s

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

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

141m 51s

Subsystem
Report/Notes

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

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

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

uname
Linux cb7fc6fe8966 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2e8df60c564080017abfd73efd3f465d48e051e6

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.


Add ability to change HelpButtonImage from loader

I FINALLY LEARNED HOW TO DO TWO COMMITS IN ONE REQUEST!
Based on skyy's change but not taken from it

yos

yes

have you confirmed this actually works considering you aren't grabbing the HelpButton setting from the server anywhere?

eh?

hello god Davey_Bones.

<@81901953285623808>
get pinged

Smol problem, the default setting needs to be changed too, if someone is using an old loader without the setting in the loader but with a new module then the helpbutton will not display altogether

yes you are le idot

why