Editor freeze

Platform: openSUSE 13.1 x86_64, XFCE
After starting Brackets, loading a file, and waiting for a while (probably 10 minutes or so?), Brackets-Git will cause the editor to freeze for a few minutes:

I have no idea what is causing this, or whether the opened file is relevant, but this was the file that was open at the time, named pkgs/games/red-eclipse/default.nix with JavaScript selected as highlighting language (due to its syntax similarity):
{ fetchurl, stdenv, SDL, SDL_image, SDL_mixer, zlib, ed }:

let
  mods = {
    base = "94b0475c7c161d4fdb59a9ebe0d740ec07b1934abf348d78d4f127f369d912f8";
    acerspyro = "18718286a72298b0a016d147524bc53094c4ad3897859ec8422131b5acc9bd3f";
    actors = "34825b5bb7f79bf9518e5e48f01ecb720cc559bb969575b93da05b5305c209cb";
    appleflap = "05c5aae92779ef8b6feb74ee396d27001aa8692610c35b33421419dd0d0bc4b2";
    blendbrush = "c0fb3257fd4a9b425bfa015ff0126807af85dbada89223765689e618ad7d4b72";
    caustics = "25b0366b0e434049d382fdeda0b62e38a7fdadf398d714713d829908f10dbb3f";
    crosshairs = "732e0a874ad39d4ee329e4b82badd8e3b513ad4a5a6f7ea5c5c2d30a42839e6e";
    elyvisions = "29d8554151789578cbce17718d911c36e3453ee3b700b96b4ca0b9d4f2391468";
    fonts = "b88246a3a194afd0e3928d447d9e49c8869ce157c005dca2ad7610479344f62a";
    freezurbern = "9669ca25a3cdffaf6172829a1e04dad51f43bf4bd98b794d1574a18dded0c078";
    john = "8d02259d0878b91c2c16b8c323f2bbf8fba521a5694f9bb160ca5f7c32b0bcd2";
    jojo = "a97b45a1e095c11f1b9b5c34ed2f28e6427a784c56fc0a143288638a59cc036a";
    jwin = "539873a19cbafd10499959619199791ebc6feabcde20c4db1e9298dea14c85e4";
    luckystrike = "21516564ba832507ecb93f05d03e662bd4dc0944d7bc800bc1127c96d941b823";
    maps = "71a79ec665e99268637952bd883afcda02345c9944494822fe96b45511c410b8";
    mayhem = "95a9ce7bfa8bc4e38da8197ef85e530e312ba040cf772bae99e84745cc95c9c2";
    mikeplus64 = "57a92abff536d459e413d424e8a948c2951a7f476dbb00831bf54ddfedff42ce";
    misc = "aec506cf659452a717430fe6104e0624eac5bd59f22c64ca5033d65cb4fc15de";
    nobiax = "159e98527ea953e1af8f49808ad61f34d08189b720e070463ff88a4a044b3622";
    particles = "759b46e2d8edc2ac893dd8fce8820b208789d9bc2c63679db35366b88d1e8d71";
    philipk = "ea4daa2e02c13bbb8d0ba18ad7d3dfdc0f39355dccc36c556bbaec88aeaa13e8";
    projectiles = "d2beb17e7b7928718d5c4d9697238027523ddd6a2f168d900b8d599d93ceb075";
    props = "79f474367f808faa7293e73851e0331a354760db0dd0b8d061f1d74b921a70e9";
    skyboxes = "f17df31c857abd7106159e82ba92b252db8ce68df21a893023d3017d8d2ac943";
    sounds = "ebcc960b5e3ecee80e04aec8335554ffdb36ecc030791666903a85cad469dede";
    textures = "a59c604d134bf0e82d31340878c4790060dc82f7a4417ada1d7782da09b3ae3f";
    torley = "4607d60be7080b0ac5c6ef801f158d2ba6e79982e9861eecdd15698a5c2d31b3";
    trak = "78e9bb131fe144b516ce29be6c9f64f2991731e49935576caa3ed999ca2fd377";
    ulukai = "638fb7ac0e0d8eb1f13c7a01d00d31ce7844c06d8907ad2a20ea571b094b3b7e";
    unnamed = "bd7da14d9e715d6dcc2687921f668739d0ba45a9f01350c1b5347e956648a242";
    vanities = "bcd9a0f22314c0bb98fc193f18f04a3cc9f1aa6b83c70a02de34b779cc166ce1";
    vegetation = "c076f3f50caac5bec5889fc8e11028882b7a39cee8560684918c3a0eb847228d";
    weapons = "23d70fb68fe34ba9c952f74b2ec6ca30b9dda8664248db10f5b434cb9c3516be";
    wicked = "0fc5a75c6b0a2a9c90a664e2b9ec958928b3059f03e90228cca547f376532b61";
  };

  createModItem = version: modName: {
    name = modName;
    value = fetchurl {
      name = "${modName}-${version}.tar.gz";
      url = "https://github.com/red-eclipse/${modName}/archive/v${version}.tar.gz";
      sha256 = builtins.getAttr modName mods;
    };
  };

  makeModList = version:
    let
      modNames = builtins.attrNames mods;
      modList = builtins.map
        (createModItem version)
        modNames;
    in
      builtins.listToAttrs modList;

  sources = version: makeModList version;
in
  stdenv.mkDerivation rec {
    name = "red-eclipse-${version}";
    version = "1.5.3";

    sourceRoot = "base-${version}";

    srcs = builtins.attrValues (sources version);

    buildInputs = [SDL SDL_image SDL_mixer zlib ed];

    preBuild = ''
      for i in \
        acerspyro actors appleflap blendbrush caustics crosshairs elyvisions \
        fonts freezurbern john jojo jwin luckystrike maps mayhem mikeplus64 misc \
        nobiax particles philipk projectiles props skyboxes sounds textures \
        torley trak ulukai unnamed vanities vegetation weapons wicked
      do
        rmdir "data/$i"
        mv "../$i-${version}" "data/$i"
      done
    '';

    buildPhase = ''
      runHook preBuild;
      make ''${enableParallelBuilding:+-j''${NIX_BUILD_CORES} -l''${NIX_BUILD_CORES}} -C src/ DESTDIR="$out" prefix=/usr system-install
    '';

    installPhase = ''
      install -Dm 0644 "doc/license.txt" "$out/usr/share/licenses/redeclipse/license.txt"
      install -Dm 0644 "doc/all-licenses.txt" "$out/usr/share/licenses/redeclipse/all-licenses.txt"
    ''
  }

The repository in question is this repository. I'm not sure how to reproduce it reliably, but the issue does not occur when Brackets-Git is disabled. I've not seen this behaviour before the most recent update.

Can you try to put "findInFiles.nodeSearch": false in your brackets preferences to see if it solves your problem?

Are there any large files inside the project (log files, binary files)?
What's the number of files in the project?


templates: Add optional fs arg.

Replace rglob with exact matching. Fixes potential bug from using rglob({template_name}*)
Per https://github.com/iterative/studio/pull/4504

Tested it by replacing in https://github.com/iterative/studio/pull/4504, Works perfectly. Thanks !


[feat] Browser extension

Describe the problem
Redux DevTools
React Developer Tools
........
Describe the solution you'd like
....
Alternatives considered
No response
Additional context
No response

This is nothing we can control. This needs to be implemented in the webview itself, this already rules out macos and linux and last time i checked Microsoft is either working on it or only considering it.
For now you have to use the standalone dev tools. I don't know about redux, but react offers a standalone version.


NETFoundation.WixToolset version 3.11.2

[x] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Note: The installer requires .NET Framework 3.5 enabled. Not sure if this can be indicated in the manifest somehow, or if this is a blocker?

I just noticed this was already submitted (twice) before in PR #895 (and #23647 stale). Closing this one.


Metadata package out of date requirements check

Added check in analyze step to verify metadata package out of date requirements

Can one of the admins verify this patch?

/azp run python - applicationinsights - ci


HBASE-24408 Introduce a general 'local region' to store data on master

The implementation is not perfect, as it initialize the store in RegionProcedureStore, and also the HFilePrinter and WALPrinter can not handle more than 1 family correctly.
But anyway, it is enough for shipping with 2.3.0, later when we want to store more data in the region, we can refactor the code, maybe in HBASE-24388.

Another benefit for this patch is that, now HFile will be stored on the root file system instead of wal filesystem, so we can reuse the HFileCleaner instead of creating a new one by our own. And it is also a good news if later we want to implement WAL on a system other than file system.
Added a UT called TestLocalRegionOnTwoFileSystems to confirm it.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 45s
master passed

+1 :green_heart:
compile
1m 21s
master passed

+1 :green_heart:
shadedjars
5m 26s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 29s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
shadedjars
5m 28s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 24s
hbase-common in the patch passed.

-1 :x:
unit
6m 39s
hbase-server in the patch failed.

33m 35s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 170b972deca9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8724e8120

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/testReport/

Max. process+thread count
776 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 30s
the patch passed

+1 :green_heart:
compile
1m 30s
the patch passed

+1 :green_heart:
javac
1m 30s
the patch passed

+1 :green_heart:
shadedjars
5m 53s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 18s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 41s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 36s
hbase-common in the patch passed.

-1 :x:
unit
6m 59s
hbase-server in the patch failed.

38m 32s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2208f381d759 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8724e8120

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/testReport/

Max. process+thread count
1172 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 22s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 41s
master passed

+1 :green_heart:
checkstyle
1m 36s
master passed

+0 :ok:
refguide
4m 43s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
2m 51s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 29s
the patch passed

-0 :warning:
checkstyle
1m  5s
hbase-server: The patch generated 2 new + 113 unchanged - 4 fixed = 115 total (was 117)

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
4m 47s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
12m 56s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

47m 42s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
dupname asflicense refguide xml spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux d55408bde2d9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8724e8120

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-general-check/output/branch-site/book.html

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-general-check/output/whitespace-eol.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  0s
master passed

+1 :green_heart:
checkstyle
1m 37s
master passed

+0 :ok:
refguide
5m 34s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
2m 53s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 43s
the patch passed

+1 :green_heart:
checkstyle
0m 23s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
1m 12s
hbase-server: The patch generated 0 new + 113 unchanged - 4 fixed = 113 total (was 117)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
5m 19s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
12m 10s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 22s
The patch does not generate ASF License warnings.

55m 20s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
dupname asflicense refguide xml spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux fd0f3d545e7c 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80b64ef4dc

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 41s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 15s
master passed

+1 :green_heart:
compile
1m 26s
master passed

+1 :green_heart:
shadedjars
6m 18s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  2s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 58s
the patch passed

+1 :green_heart:
compile
1m 22s
the patch passed

+1 :green_heart:
javac
1m 22s
the patch passed

+1 :green_heart:
shadedjars
6m 12s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 33s
hbase-common in the patch passed.

-1 :x:
unit
223m 13s
hbase-server in the patch failed.

254m 39s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 32ca988acb72 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80b64ef4dc

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/testReport/

Max. process+thread count
2976 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

Looks great. Some questions.
Another question is those who have deployed tests on branch-2.3 will have to shutdown these tests, remove the procedure store dir and then restart w/ a later version of 2.3 that has this in it? i.e. how to migrate existing 2.3s? A shutdown, remove, and restart seems fine since no 2.3 release as yet.
Good stuff.

Leaving it there or removing it are both fine, if you want to keep the data then just follow the new naming to rename the old directory. We do not change the data format of the region.

Let me check the failed UTs.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
35m 29s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 27s
master passed

+1 :green_heart:
checkstyle
1m 30s
master passed

+0 :ok:
refguide
4m 36s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
2m 42s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 22s
the patch passed

+1 :green_heart:
checkstyle
0m 24s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
1m  7s
hbase-server: The patch generated 0 new + 112 unchanged - 4 fixed = 112 total (was 116)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
4m 47s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
14m 29s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s
The patch does not generate ASF License warnings.

88m 47s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
dupname asflicense refguide xml spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux a9386332d7f3 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80b64ef4dc

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  0s
the patch passed

+1 :green_heart:
compile
1m 29s
the patch passed

+1 :green_heart:
javac
1m 29s
the patch passed

+1 :green_heart:
shadedjars
5m 45s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 18s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 34s
hbase-common in the patch passed.

+1 :green_heart:
unit
124m 47s
hbase-server in the patch passed.

160m 23s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5c81751c28be 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80b64ef4dc

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/testReport/

Max. process+thread count
4106 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
35m 31s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 25s
master passed

+1 :green_heart:
compile
1m 21s
master passed

+1 :green_heart:
shadedjars
5m 36s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 25s
the patch passed

+1 :green_heart:
compile
1m 18s
the patch passed

+1 :green_heart:
javac
1m 18s
the patch passed

+1 :green_heart:
shadedjars
5m 26s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 23s
hbase-common in the patch passed.

+1 :green_heart:
unit
133m 57s
hbase-server in the patch passed.

198m 40s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8ada82254c8f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80b64ef4dc

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/testReport/

Max. process+thread count
4695 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
2m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 46s
master passed

+1 :green_heart:
checkstyle
1m 46s
master passed

+0 :ok:
refguide
5m 22s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
3m 15s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 45s
the patch passed

+1 :green_heart:
checkstyle
0m 23s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-procedure

+1 :green_heart:
checkstyle
1m 11s
hbase-server: The patch generated 0 new + 112 unchanged - 4 fixed = 112 total (was 116)

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
5m 26s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
12m 14s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 49s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

55m 34s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
dupname asflicense refguide xml spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 53f7c81eb506 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e1d7dc82ea

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-general-check/output/branch-site/book.html

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-general-check/output/whitespace-eol.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  2s
the patch passed

+1 :green_heart:
compile
1m 53s
the patch passed

+1 :green_heart:
javac
1m 53s
the patch passed

+1 :green_heart:
shadedjars
6m 20s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 16s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 18s
hbase-procedure in the patch failed.

-0 :warning:
javadoc
0m 41s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 39s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m 43s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
128m 32s
hbase-server in the patch passed.

167m 42s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 764b5499b0d6 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e1d7dc82ea

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-procedure.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-procedure.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/testReport/

Max. process+thread count
4553 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
4m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 57s
master passed

+1 :green_heart:
compile
1m 48s
master passed

+1 :green_heart:
shadedjars
6m 12s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  9s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 48s
the patch passed

+1 :green_heart:
compile
1m 38s
the patch passed

+1 :green_heart:
javac
1m 38s
the patch passed

+1 :green_heart:
shadedjars
6m 24s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 32s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m 56s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
199m 23s
hbase-server in the patch passed.

238m 53s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4f1cc6932ce3 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e1d7dc82ea

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/testReport/

Max. process+thread count
2741 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 31s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 58s
master passed

+1 :green_heart:
checkstyle
1m 55s
master passed

+0 :ok:
refguide
5m 46s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
3m 42s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 10s
the patch passed

+1 :green_heart:
checkstyle
0m 26s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
0m 15s
The patch passed checkstyle in hbase-procedure

+1 :green_heart:
checkstyle
1m 17s
hbase-server: The patch generated 0 new + 112 unchanged - 4 fixed = 112 total (was 116)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
5m 46s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
11m 41s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
4m 46s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

53m 55s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
dupname asflicense refguide xml spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 23735650a418 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2b894dc100

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
95 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 23s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 39s
master passed

+1 :green_heart:
compile
1m 37s
master passed

+1 :green_heart:
shadedjars
5m 36s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 16s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 25s
the patch passed

+1 :green_heart:
compile
1m 39s
the patch passed

+1 :green_heart:
javac
1m 39s
the patch passed

+1 :green_heart:
shadedjars
5m 29s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 12s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 14s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m 51s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
134m 31s
hbase-server in the patch passed.

165m 27s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4c19d795e8ef 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2b894dc100

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/testReport/

Max. process+thread count
3972 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m  5s
the patch passed

+1 :green_heart:
compile
2m 19s
the patch passed

+1 :green_heart:
javac
2m 19s
the patch passed

+1 :green_heart:
shadedjars
7m 10s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 20s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 20s
hbase-procedure in the patch failed.

-0 :warning:
javadoc
0m 45s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 42s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m 45s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
131m 24s
hbase-server in the patch passed.

170m 53s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1753

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1f1b6b0d5307 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2b894dc100

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-procedure.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-procedure.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/testReport/

Max. process+thread count
4367 (vs. ulimit of 12500)

modules
C: hbase-common hbase-procedure hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1753/5/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


ci: update jobs and restore 3.6

This restores 3.6 (temporarily till the next release? etc.), switches to the official nox action, and updates the checkout action.

Thanks, I have used my own fork of the nox action, due to the problem with the official one, and it stayed that way. I'm not sure if I like to keep using older ubuntu version, but it is OK for now, and later I can create another matrix to run some older python versions against the older ubuntu.

I assume eventually, you will drop 3.6, but it’s nicer to drop it on your schedule them to be forced by a CI change.
nox itself started started supporting actions for setup fairly recently, the old setup-nox action has also finally been fixed, but it was broken for a while. Both of them are now built on composite actions, which is a lot nicer and more stable than forking setup-python’s JavaScript action.


End-to-end UX of deploying Conjur OSS with the helm chart and running apps in K8s is reviewed

More details TBA
We would like to perform XA using the draft updated documentation (link TBA) for Kubernetes authentication to run through the end-to-end experience of using Conjur OSS with Kubernetes-deployed applications.

I created some applications on a GKE cluster using a modified version of the conjurdemos/kubernetes-conjur-demo scripts, and reviewed the Conjur documentation re. authn-k8s.
Summary / Key Takeaways

Documentation is in good shape, only a couple of changes suggested.
However, documentation is scattered. So someone playing the roles of both security admin and app developer
will need to jump between Conjur documentation (e.g. for enabling authn-k8s and configuring policies)
and documentation for setting up applications e.g. for setting up a Secretless broker sidecar or for setting up
Summon. So it's important to have some good demos/examples for how to configure all-the-things on an existing
Conjur-OSS deployment.
Biggest potential pitfall: See Item #1 in Findings/Action Items section below.
Best solution is to integrate the creation of a Conjur account into the Conjur OSS helm chart, maybe as a
post-install Helm hook.
Another big pain point is that we need a good troubleshooting guide for Conjur authn-k8s.
There's an existing issue file... I need to find the number.

Findings/Action Items

Conjur OSS Helm Chart Documentation: Chart Value account MUST match Conjur Account That you Expect to Create
This needs to be documented!!! Let's say you deploy a Conjur OSS server, using either an explicit setting
for chart value account or using the default value of "default"). If you later create a Conjur account
on this server, then you will need to either:

Use the same value for Conjur account as you used for the chart value account, or...
Do a Helm upgrade after you've created a Conjur account to update the chart value account to
match the Conjur account value.

Failing to do this will cause Kubernetes authn-k8s authentication to fail.
Perhaps a better alternative would be to add an option to have the Conjur OSS Helm chart to create an
account as a post-install hook.

Conjur Documentation Should Use "identity" Instead of "host" in Some Places
For example, in https://docs.conjur.org/latest/en/Content/Integrations/Kubernetes_AppIdentity.htm?tocpath=Integrations|OpenShift%252C Kubernetes|_____2#ApplicationIdentityinOpenShiftKubernetes

This line:
The following are the Kubernetes resources that you can define as hosts:
should be:
The following are the Kubernetes resources that you can define as authentication identities:

This line:
We recommend using this option as a transition, and move towards using the Kubernetes Deployment and StatefulSet resources as hosts.
Should be:
We recommend using this option as a transition, and move towards using the Kubernetes Deployment and StatefulSet resources as authentication identities.

This line:
Define Kubernetes Resources as Conjur hosts
Should be:
Define Kubernetes Resources as Conjur Identities

Inconsistent use of ClusterRole vs Role
I believe Role (which is namespace scoped) is preferred?

Role used in docs.conjur.org:
https://docs.conjur.org/latest/en/Content/Get Started/scl_using-conjur-OSS.htm#conjur-authenticator-role.yml
ClusterRole used in docs.cyberark.com:
https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/Latest/en/Content/Integrations/Kubernetes_deploySecretlessSidecar.htm#grant-the-dap-follower-access-to-pods-in-the-namespace

Secretless Getting Started Doc uses Old Style /service_account/ as host
Should be change to be consistent with other examples that use the application name as host?
A service account host is defined here:
https://docs.secretless.io/Latest/en/Content/Get Started/using-dap.htm#EnabletheKubernetesauthenticatorforyourapplication
  - !host
  id: APP_NAMESPACE/service_account/APP_SERVICE_ACCOUNT
  annotations:
    kubernetes/authentication-container-name: secretless
    kubernetes: "true"
  # grant membership to the conjur/authn-k8s/AUTHENTICATOR_NAME/apps layer
- !grant
  role: !layer
  member: !host APP_NAMESPACE/service_account/APP_SERVICE_ACCOUNT

The corresponding CONJUR_AUTHN_LOGIN is defined here:
https://docs.secretless.io/Latest/en/Content/Get Started/using-dap.htm#AddSecretlesstoyourappdeploymentmanifest
 	    - name: CONJUR_AUTHN_LOGIN
   value: "host/conjur/authn-k8s/AUTHENTICATOR_NAME/apps/APP_NAMESPACE/service_account/APP_SERVICE_ACCOUNT"

Conjur OSS Helm Chart Documentation Should Provide Examples Showing authn-k8s Authentication

We can point to conjurdemos/kubernetes-conjur-demo scripts.
I have some changes to this repo which should allow the scripts to run directly on a Conjur-OSS
cluster that has been deployed via Conjur OSS Helm chart.

Conjur OSS Helm Chart Documentation Needs to Show How to Enable Debug Mode

Trouble Shooting Wiki Needs to Include a Step-by-Step Guide to Debugging authn-k8s

There is a blog post that walks through the e2e experience of deploying & configuring Conjur OSS and deploying apps to Kubernetes

@diverdane were follow-up issues filed for all of these items and put in the epic #74? If that's the case, then I think this issue can be closed now


Chinese characters or emoji's doesn't diplay in TextPresenter

example text:
Chinese: 表意文字. Japanese: 和製漢字 emoji: ☚
example xaml:
    <Border BorderThickness="2" BorderBrush="Black" HorizontalAlignment="Left" Padding="5">
      <StackPanel>
        <TextBlock Text="TextBlock: Chinese: 表意文字. Japanese: 和製漢字 emoji: ☚" />
        <TextPresenter Text="TextPresenter: Chinese: 表意文字. Japanese: 和製漢字 emoji: ☚" />
      </StackPanel>
    </Border>

result (TextBlock is working fine):

Workaround:

You need to use a font that has Chinese characters. https://github.com/anthonyfok/fonts-wqy-microhei is a good one
WenQuanYiMicroHei-01.ttf.zip
Place it into Assets, add as AvaloniaResource and add something like
<Style Selector="TextBlock">
   <Setter Property="FontFamily" Value="avares://YourAssemblyName/Assets/Fonts#WenQuanYi Micro Hei" />
</Style>

to your App.xaml after the theme

Fixed in current master


Image licensing

[x ] No discrepancies across browsers. Eg. chrome vs safari
[ x] Pages pass W3C Validation for HTML (https://validator.w3.org)
[x ] CSS (https://jigsaw.w3.org/css-validator/)
[x ] Google sign-in is operational
[ x] Accessibility functions
[ x] Pages can scale without distorting page
[ x] No dead links
[ x] Navbar is consistent across the site
[ x] Pages are screen-reader accessible
[ x] Contrast meets standards for accessibility
[x ] Pages are keyboard accessible
[x ] Passes WAVE Evaluation Tool chrome extension

Looks good! great job getting the licenses for everything we needed it! :)


Virualizer admin integration

The first step has been finished. Now the virtualizer is running with the chassis of OMAGServerApplication.

I took the PR to try out as I'm keen to get virtualizer running.
However when I run OMAGApplication whilst I see many services available I couldn't see any reference to the virtualizer?

I took the PR to try out as I'm keen to get virtualizer running.
However when I run OMAGApplication whilst I see many services available I couldn't see any reference to the virtualizer?

Hi,
This PR is the first step for the integration of admin service. I created some properties for virtualiser in the corresponding directory. The full integration will be finished after the Xmas and new year holiday. Please leave it here and I will ask for reviewing and merging after the full integration.
Have a nice holiday!
Regards,
Yue Feng


DSC Resource for managing W2K12+ File Server Resource Manager (FSRM)

I have created a DSC Resource Module for managing Windows Server 2012+ File Server Resource Manager (FSRM): https://github.com/PlagueHO/cFSRM
It contains MOF based resources for the following:

cFSRMSettings configures FSRM settings.
cFSRMClassification configures FSRM Classification settings.
cFSRMClassificationProperty configures FSRM Classification Property Definitions.
cFSRMClassificationPropertyValue configures FSRM Classification Property Definition Values. This resource only needs to be used if the Description of a Classification Property Definition Value must be set.
cFSRMClassificationRule configures FSRM Classification Rules.
cFSRMFileScreen configures FSRM File Screen.
cFSRMFileScreenAction configures FSRM File Screen Actions for File Screens.
cFSRMFileScreenTemplate configures FSRM File Screen Templates.
cFSRMFileScreenTemplateAction configures FSRM File Screen Template Actions for File Screen Templates.
cFSRMFileScreenExclusion configures FSRM File Screen Exclusions.
cFSRMFileGroup configures FSRM File Groups.
cFSRMQuota configures FSRM Quotas.
cFSRMQuotaAction configures FSRM Quota Actions for Quotas.
cFSRMQuotaTemplate configures FSRM Quota Templates.
cFSRMQuotaTemplateAction configures FSRM Quota Template Actions for Quota Templates.
cFSRMAutoQuota configures FSRM Auto Quotas.

It contains Unit and Integration tests for all resources, using the DSCResource.Test\TestHelper.psm1 functions.
Note about tests: Tests require Windows Server 2012 (or above) to pass because required File Server Resource Manager feature to be installed. Tests pass on AppVeyor because AppVeyor.yml is configured to ensure the FSRM feature is installed before invoking pester.
The module doesn't have resources for managing File Tasks and File Reports, but I do plan on getting to those at some point when I have more time.
Would there be interest in moving this module over to the community module library here?
If so, I'd need to convert the resources over from BMD_ to MSFT_ and other updates to the .PSD1,AppVeyor.yml etc before transferring the repo.
Thanks!

That would be great@PlagueHO!
I briefly went over that module and it looks great. Let me know when all tasks on your side are ready and we will start our review process to bring it under PowerShell org.

Awesome! I'll get it done and let you know when it's ready to transfer and you can eyeball it before I transfer. :+1:

All changes done and ready to transfer over. Module is now currently available in this repo:
https://github.com/PlagueHO/xFSRM
Just take a look whenever - there is no rush at all on this. Just let me know if you're happy with it and I'll transfer it over.
Cheers and have a great Chrismas/New Year.

@KarolKaczmarek: Just want to confirm you're not waiting on anything from me on this one?

No, sorry for the delay, I was trying to get someone to review it, but the whole team is pretty swamped with work right now and it's pretty large module. We will get to it though, thank you for your patience!

@KarolKaczmarek: Oh no problem at all - completely understand. :smile:

@kwirkykat - these are the DSC resource modules I was meaning when I asked the status of the reviews :smile:
There are a few others from myself and a few more from other contributors. I've also got a few more in the pipeline but I don't want to overload your team even more!

@PlagueHO I just posted a new guide on submitting new resource modules.
Can you please open a PR to an empty branch in your repo so that reviewers can make comments?
This module looks good to me so far :+1:

Thanks @kwirkykat - Should I convert the naming of this DSC Reosurce over to the HQRM naming scheme or leave it as xFSRM?

@PlagueHO Yes. Convert to ____Dsc Format please.

@kwirkykat  - I've finished updating this module to HQRM format:
https://github.com/PlagueHO/FSRMDsc
Once I've worked out how to perform steps 4 and 5 of the new guide I'll link the PR to the empty branch.
Thanks!

This PR is ready for full review:
https://github.com/PlagueHO/FSRMDsc/pull/2

Module submission progess:

[x] 1. Separate public repository created
[x] 2. Review pull request open
[ ] 3. 1st reviewer approved (Katie)
[ ] 4. 2nd reviewer approved
[ ] 5. 3rd reviewer approved
[ ] 6. Tests passing
[ ] 7. Repository transferred
[ ] 8. Module released

Closing this one! :grin:


Using lark to search lines of source code?

Can/should I use lark to match text?
Specifically, I am trying to analyze how various functionalities are used in a set of source code files. I.e., what arguments are passed to a given function, or what kind of regular expressions are used?
Ex 1: Find arguments passed to the my_function function. Ans: [None, None, "abc"] for each line respectively.
function foo():
    bar()
    result = my_function("abc") // comment

Ex 2: What regular expressions are found in this snippet? Ans: %$
    ...
    value = parseFloat(value, 10) / (/%$/.test(value) ? 100 : 1);
    ...

I've been using regular expressions + additional logic to handle this so far. But as my project grows, accuracy and maintainability is suffering. I figured I might be able to write a grammar in lark to handle most of the work.
I've used lark in other aspects of my project without any issues, but I keep getting difficult errors and would really appreciate some help in the matter. I figure the grammar for Ex 1 should look something like this:
start   : [JUNK] "my_function(" ARG ")" [JUNK]
JUNK    : /.+/
ARG     : /[^ ]+/

In my mind, the above grammar should be able to handle my_function("abc"), in reality:
Traceback (most recent call last):
  File "...sample.py", line 80, in <module>
    print parser.parse('my_function("abc")')
  File "...Library/Python/2.7/lib/python/site-packages/lark/lark.py", line 561, in parse
    return self.parser.parse(text, start=start, on_error=on_error)
  File "...Library/Python/2.7/lib/python/site-packages/lark/parser_frontends.py", line 107, in parse
    return self.parser.parse(stream, start, **kw)
  File "...Library/Python/2.7/lib/python/site-packages/lark/parsers/earley.py", line 306, in parse
    raise UnexpectedEOF(expected_terminals, state=frozenset(i.s for i in to_scan))
lark.exceptions.UnexpectedEOF: Unexpected end-of-input. Expected one of:
        * __ANON_0
        * RPAR
        * __ANON_0
        * RPAR

Am I totally misguided? Am I missing something here?
Either way, thanks for the awesome project - it's working splendidly in other parts of my project.

Lark isn't really that good at searching in a text. It would be better if you can define a full grammar for everything (If the text might contain error, you can try to play around with error callbacks). Otherwise pyparsing has scanString, which might be a better fit.
Although @erezsh: Shouldn't it be somewhat easy to build a search function the uses some kind of cached (contextual) lexer to try to parse at a lot of places and sees how much progress it does? Might be worth adding to lark, since this isn't the first time we get this request.

If you're trying to search for Python code, you're probably better off with something like Red Baron

Lark might be able to do it, if you use parser="earley" and lexer="dynamic_complete".
But it would be very inefficient!
You're better off starting you parse at different points in the text. Like
for i in range(text):
   try:
        res = lark_instance.parse(text[i:])
		// do something with result
   except LarkError:
       pass

And if that's too slow, you can find all the likely points with a regexp, and then use Lark to validate your findings. But that's just a thought. Lark definitely wasn't designed for that.

@MegaIng I'd be willing to consider such a PR if it works well, but I'm not sure it would be as simple as you suggest.

Thanks everyone for your assistance. It seems my current solution (regex + additional logic) is better than anything lark is meant to provide.
I’ll close this since my question has been answered. 😄


provide a way to pass in an optional ResizeObserver ponyfill

Right now we just bake a ResizeObserver ponyfill right into snabby, which increases it's size by about 8kb.
It would be nice to make this optional as something that could be passed in. In larger projects there is likely already a ResizeObserver ponyfill being used and this would de-duplicate a bit.

Another option is to just wait for ResizeObserver to become more prevalent (like 95% + of browsers) and just remove it.


PR FHEM Adapter 1.3.0 latest

sorry, stable not latest

ääähm .. nope ... npm is 1.2.1 only ... so first of all I would bring 1.3.0 to latest ... ok?

Yes, of course.New PR 1.3.0 stable after 1.3.0 latest?Sorry, my first time....Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------Von: Ingo Fischer<EMAIL_ADDRESS>Datum: 22.07.19  12:31  (GMT+01:00) An: "ioBroker/ioBroker.repositories"<EMAIL_ADDRESS>Cc: LausiD<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [ioBroker/ioBroker.repositories] PR FHEM Adapter 1.3.0 latest
  (#451) ääähm .. nope ... npm is 1.2.1 only ... so first of all I would bring 1.3.0 to latest ... ok?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/ioBroker/ioBroker.repositories/pull/451?email_source=notifications\u0026email_token=AJHJS22YVCW6YK47NKV7NOLQAWEBZA5CNFSM4IFR5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PP76I#issuecomment-513736697",
"url": "https://github.com/ioBroker/ioBroker.repositories/pull/451?email_source=notifications\u0026email_token=AJHJS22YVCW6YK47NKV7NOLQAWEBZA5CNFSM4IFR5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PP76I#issuecomment-513736697",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

1.3.0 on npm now, latest soon


[Backport 2.11] Backport #788 to 2.11

Manual backport to 2.11

Fix duplicate ecs mappings which returns incorrect log index field in mapping view API (#786) #788

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

closing in favor of #931


Update vmware-physical-mobility-service-overview.md

Adding parentheses to the correct command
Hi, I am currently doing these steps, in a VMWARE replication project and the correct syntax for the command is: .\Microsoft-ASR_UAWindowsrelease.exe /q /x:"C:\Program Files (x86)\Microsoft Azure Site Recovery"
And by the way, an important detail for Windows does not work * (Microsoft-ASR_UAWindows*release.exe) only the full name.
If you approve it, I would be happy to make a command that according to this command grabs the file.
Thanks .
shoval astamker

@ankitaduttaMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

hi, can you approve my merging?
or something is wrong ?


Prevent expensive queries with query analysis + max depth

Is there any way of preventing a malicious or erroneous query from being run?
I worry that by allowing including associated resources, which in turn can include more resources, could potentially allow for extremely large DB queries and result sets.  This is especially true since all included resources are not paginated; not arguing that they should be, just saying that it allows for unbounded results.
From the graphql community I have seen people:

Set a max inclusion depth.
Perform query analysis by summing the fields and associations, with weightings, and supplying a cutoff number.
Only allow specific queries, and then call them by name.
Be very careful on what can and cannot be included
Disallow including (not graphql, but jsonapi solution)
Stop worrying because this is an internal api with trusted clients.

Right now I'm living with solution 4, but I know that eventually something will sneak in.  Mostly just wondering what other people are doing and if there is a sanctioned why to do it in this library.
thanks again for a great library.

I have this same concern as I'm considering different API implementations. Any word on this?

I have the same concerns. I'm currently considering the best way(s) to handle this.
Without any new features to the project you could implement some of your options:

Set a max inclusion depth.

You could override the apply_includes method on your resource to check the depth of the requested includes.

Perform query analysis by summing the fields and associations, with weightings, and supplying a cutoff number.

Override find_records on your resource to perform the query analysis to check against a threshold complexity.

Disallow including (not graphql, but jsonapi solution)

You can omit the included relationships by removing them from fields. Not a complete solution, but it might be workable in some cases.

Stop worrying because this is an internal api with trusted clients.

Nothing could go wrong with this :wink:

Thanks for the suggested solutions - they definitely seems like the way to go in the short term.
I know you're still considering next steps for an official solution, but for now I'll leave this issue open in case others want to chime in.


Why HardSourceWebpackPlugin is commented?

HardSourceWebpackPlugin will reduce build time but it's commented. is there any reason for that?

When I used it, it was buggy.

I will give it a try and see if I can solve the bugs

FYI: twista enabled it few months ago but it's working well.

I don't get any problem in the building process

So I tested it in dev mode and production mode too but there was no error. Maybe it has something to do with the OS (I am on windows) it will be great if someone can confirm this.


Latest version seems to break if more then only a few values are requsted

Did you read the instructions?

[X] I have read the README.

The problem
I request these values from 602:

Flow
Heat Energy (E1)
Power
Temp1
Temp1xm3
Temp2
Temp2xm3
Tempdiff
Volume
HourCounter
Infoevent

With version 2.0.2 all is working fine.
After update to version 2.1.0 i've got no values anymore.
Then i pried to remove the addon and reinstall. Now it's working with the 2-3 default values.
After enabling the values mentioned above, i've got no updates anymore and this error:
Logger: custom_components.kamstrup_403
Source: custom_components/kamstrup_403/init.py:83
Integration: Kamstrup 403 (documentation, issues)
First occurred: 17:33:50 (5 occurrences)
Last logged: 17:49:23
Error reading multiple [60, 80, 86, 87, 89, 74, 68, 97, 110, 113, 1004] Exception: bytearray index out of range
Finished update, No readings from the meter. Please check the IR connection
What version of this integration has the issue?
2.1.0
What version of Home Assistant Core has the issue?
core-2023.1.4
Home Assistant log
No response
Diagnostics
No response
Additional information
No response

Please attach loge and diagnostic file

This the only kamstrup 403 related part from debug log:
2023-01-15 21:18:02.556 ERROR (MainThread) [custom_components.kamstrup_403] Error reading multiple [60, 80, 86, 87, 89, 74, 68, 97, 110, 113, 1004]  Exception: bytearray index out of range 2023-01-15 21:18:02.560 WARNING (MainThread) [homeassistant.config_entries] Config entry '/dev/ttyUSB1' for kamstrup_403 integration not ready yet; Retrying in background
diagnostic file is attached:
config_entry-kamstrup_403-beb8cec9d4d8aeec4e8f1219236a5f15.json.txt

Please enable all logs for this component and restart: https://github.com/golles/ha-kamstrup_403#collect-logs
This should give more logging

removed most of the not kamstrup related stuff.
You will find all related stuff here:
`
2023-01-15 21:34:41.383 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration kamstrup_403 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-15 21:34:41.449 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2023-01-15 21:34:41.449 INFO (MainThread) [homeassistant.bootstrap] Setting up frontend: {'frontend'}
2023-01-15 21:34:41.457 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2023-01-15 21:34:41.458 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
2023-01-15 21:34:41.496 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2023-01-15 21:34:41.498 INFO (MainThread) [homeassistant.setup] Setting up http
2023-01-15 21:34:41.502 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds
2023-01-15 21:34:41.513 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds
2023-01-15 21:34:41.517 INFO (MainThread) [homeassistant.setup] Setting up api
2023-01-15 21:34:41.520 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds
2023-01-15 21:34:41.520 INFO (MainThread) [homeassistant.setup] Setting up auth
2023-01-15 21:34:41.522 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds
2023-01-15 21:34:41.524 INFO (MainThread) [homeassistant.setup] Setting up config
2023-01-15 21:34:41.528 INFO (MainThread) [homeassistant.setup] Setting up diagnostics
2023-01-15 21:34:41.532 INFO (MainThread) [homeassistant.setup] Setting up repairs
2023-01-15 21:34:41.533 INFO (MainThread) [homeassistant.setup] Setup of domain repairs took 0.0 seconds
2023-01-15 21:34:41.690 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.2 seconds
2023-01-15 21:34:41.691 INFO (MainThread) [homeassistant.setup] Setup of domain diagnostics took 0.2 seconds
2023-01-15 21:34:41.699 INFO (MainThread) [homeassistant.setup] Setting up file_upload
2023-01-15 21:34:41.699 INFO (MainThread) [homeassistant.setup] Setup of domain file_upload took 0.0 seconds
2023-01-15 21:34:41.724 INFO (MainThread) [homeassistant.setup] Setting up image_upload
2023-01-15 21:34:41.725 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2023-01-15 21:34:41.726 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds
2023-01-15 21:34:41.743 INFO (MainThread) [homeassistant.setup] Setting up search
2023-01-15 21:34:41.743 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.0 seconds
2023-01-15 21:34:42.333 INFO (MainThread) [homeassistant.setup] Setting up analytics
2023-01-15 21:34:42.353 INFO (MainThread) [homeassistant.setup] Setup of domain image_upload took 0.6 seconds
2023-01-15 21:34:42.355 INFO (MainThread) [homeassistant.setup] Setting up person
2023-01-15 21:34:42.356 INFO (MainThread) [homeassistant.setup] Setup of domain analytics took 0.0 seconds
2023-01-15 21:34:42.371 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.0 seconds
2023-01-15 21:34:42.373 INFO (SyncWorker_8) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2023-01-15 21:34:42.377 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2023-01-15 21:34:42.378 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds
2023-01-15 21:34:42.390 INFO (MainThread) [homeassistant.setup] Setting up frontend
2023-01-15 21:34:42.395 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds
2023-01-15 21:34:42.396 INFO (MainThread) [homeassistant.bootstrap] Setting up recorder: {'recorder'}
2023-01-15 21:34:42.397 INFO (MainThread) [homeassistant.setup] Setting up recorder
2023-01-15 21:34:42.405 INFO (MainThread) [homeassistant.components.http] Now listening on port 8123
2023-01-15 21:34:42.434 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.0 seconds
2023-01-15 21:34:42.435 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'cloud', 'webhook', 'bluetooth', 'api', 'ssdp', 'http', 'dhcp', 'usb', 'network', 'websocket_api', 'zeroconf'}
2023-01-15 21:34:42.439 INFO (MainThread) [homeassistant.setup] Setting up webhook
2023-01-15 21:34:42.440 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds
2023-01-15 21:34:42.584 INFO (MainThread) [homeassistant.setup] Setting up dhcp
2023-01-15 21:34:42.585 INFO (MainThread) [homeassistant.setup] Setup of domain dhcp took 0.0 seconds
2023-01-15 21:34:42.600 INFO (MainThread) [homeassistant.setup] Setting up usb
2023-01-15 21:34:42.600 INFO (MainThread) [homeassistant.setup] Setup of domain usb took 0.0 seconds
2023-01-15 21:34:42.602 INFO (MainThread) [homeassistant.setup] Setting up network
2023-01-15 21:34:42.605 INFO (MainThread) [homeassistant.setup] Setup of domain network took 0.0 seconds
2023-01-15 21:34:42.615 INFO (SyncWorker_10) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
2023-01-15 21:34:42.616 INFO (SyncWorker_1) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2023-01-15 21:34:42.690 INFO (MainThread) [homeassistant.setup] Setting up bluetooth
2023-01-15 21:34:42.771 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2023-01-15 21:34:42.805 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2023-01-15 21:34:42.807 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.0 seconds
2023-01-15 21:34:43.258 INFO (MainThread) [homeassistant.setup] Setting up cloud
2023-01-15 21:34:43.294 INFO (MainThread) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2023-01-15 21:34:43.316 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth took 0.6 seconds
2023-01-15 21:34:43.334 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.1 seconds
2023-01-15 21:34:43.353 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.5 seconds
2023-01-15 21:34:43.364 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'logbook', 'system_health', 'scene', 'deconz', 'search', 'counter', 'tag', 'hacs', 'panel_custom', 'auto_backup', 'default_config', 'tasmota', 'webrtc', 'group', 'alert', 'application_credentials', 'alarm_control_panel', 'input_datetime', 'forecast_solar', 'co2signal', 'ios', 'timer', 'input_text', 'powercalc', 'utility_meter', 'auth', 'device_automation', 'wemo', 'my', 'input_number', 'scheduler', 'intent_script', 'ui_lovelace_minimalist', 'light', 'diagnostics', 'influxdb', 'repairs', 'schedule', 'automation', 'template', 'homeassistant_alerts', 'energy', 'person', 'nina', 'switch', 'media_source', 'mqtt', 'media_player', 'switch_as_x', 'google', 'dlna_dmr', 'owntracks', 'zwave_js', 'alexa_media', 'cupertino', 'unifi', 'radio_browser', 'input_button', 'pyscript', 'alarmo', 'notify', 'unifiprotect', 'input_select', 'apple_tv', 'device_tracker', 'garmin_connect', 'met', 'kamstrup_403', 'map', 'stream', 'mobile_app', 'onboarding', 'ffmpeg', 'denonavr', 'tod', 'panasonic_viera', 'synology_dsm', 'blueprint', 'file_upload', 'trace', 'alexa', 'sensor', 'ipp', 'config', 'proximity', 'cover', 'input_boolean', 'heos', 'persistent_notification', 'analytics', 'shelly', 'tts', 'select', 'binary_sensor', 'hardware', 'nuki_ng', 'sun', 'tado', 'lovelace', 'eufy_security', 'none', 'history', 'script', 'image_upload', 'browser_mod', 'zone', 'xiaomi_aqara', 'esphome', 'lifx', 'min_max'}
2023-01-15 21:34:43.375 INFO (MainThread) [homeassistant.setup] Setting up scene
2023-01-15 21:34:43.376 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2023-01-15 21:34:43.383 INFO (MainThread) [homeassistant.setup] Setting up counter
2023-01-15 21:34:43.385 INFO (MainThread) [homeassistant.setup] Setting up tag
2023-01-15 21:34:43.386 INFO (MainThread) [homeassistant.setup] Setting up panel_custom
2023-01-15 21:34:43.386 INFO (MainThread) [homeassistant.setup] Setup of domain panel_custom took 0.0 seconds
2023-01-15 21:34:43.388 INFO (MainThread) [homeassistant.setup] Setting up group
2023-01-15 21:34:43.392 INFO (SyncWorker_9) [homeassistant.loader] Loaded manual from homeassistant.components.manual
2023-01-15 21:34:43.392 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2023-01-15 21:34:43.393 INFO (MainThread) [homeassistant.setup] Setting up timer
2023-01-15 21:34:43.397 INFO (MainThread) [homeassistant.setup] Setting up input_text
2023-01-15 21:34:43.398 INFO (MainThread) [homeassistant.setup] Setting up input_number
2023-01-15 21:34:43.400 INFO (MainThread) [homeassistant.setup] Setting up intent_script
2023-01-15 21:34:43.401 INFO (MainThread) [homeassistant.setup] Setup of domain intent_script took 0.0 seconds
2023-01-15 21:34:43.402 INFO (MainThread) [homeassistant.setup] Setting up light
2023-01-15 21:34:43.408 INFO (MainThread) [homeassistant.setup] Setting up schedule
2023-01-15 21:34:43.411 INFO (MainThread) [homeassistant.setup] Setting up homeassistant_alerts
2023-01-15 21:34:43.412 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant_alerts took 0.0 seconds
2023-01-15 21:34:43.427 INFO (MainThread) [homeassistant.setup] Setting up kamstrup_403
2023-01-15 21:34:43.427 INFO (MainThread) [homeassistant.setup] Setup of domain kamstrup_403 took 0.0 seconds
2023-01-15 21:34:43.492 DEBUG (MainThread) [custom_components.kamstrup_403] Set up entry, with scan_interval of 3600 seconds and timeout of 1.0 seconds
2023-01-15 21:35:05.292 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 60
2023-01-15 21:35:05.292 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 80
2023-01-15 21:35:05.292 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 86
2023-01-15 21:35:05.293 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 87
2023-01-15 21:35:05.293 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 89
2023-01-15 21:35:05.294 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 74
2023-01-15 21:35:05.294 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 68
2023-01-15 21:35:05.297 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 97
2023-01-15 21:35:05.298 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 110
2023-01-15 21:35:05.298 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 113
2023-01-15 21:35:05.299 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 1004
2023-01-15 21:35:07.104 ERROR (MainThread) [custom_components.kamstrup_403] Error reading multiple [60, 80, 86, 87, 89, 74, 68, 97, 110, 113, 1004]
Exception: bytearray index out of range
2023-01-15 21:35:07.106 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 1.051 seconds (success: False)
2023-01-15 21:35:07.108 WARNING (MainThread) [homeassistant.config_entries] Config entry '/dev/ttyUSB1' for kamstrup_403 integration not ready yet; Retrying in background
2023-01-15 21:35:47.062 DEBUG (MainThread) [custom_components.kamstrup_403] Set up entry, with scan_interval of 3600 seconds and timeout of 1.0 seconds
2023-01-15 21:35:47.078 INFO (MainThread) [custom_components.hacs] Loading removed repositories
2023-01-15 21:35:47.085 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry /dev/ttyUSB1 for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 573, in async_setup_entry
return await component.async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 166, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2023-01-15 21:35:47.567 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-01-15 21:35:47.693 ERROR (MainThread) [custom_components.kamstrup_403] Finished update, No readings from the meter. Please check the IR connection
2023-01-15 21:35:47.706 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.139 seconds (success: True)
`

Are you sure your serial device is on /dev/ttyUSB1?
It is really not recommended to use these devices, please have a look at https://github.com/golles/ha-kamstrup_403#configuration-is-done-in-the-ui

I'm using the your add-on NOW with version 2.0.2 and /dev/ttyUSB1 like i've done for months before the latest update.
And it's working fine with 2.0.2 again.

I am guessing the 602 (and possibly other types) return a maximum of N (to be determined?) values per request. Or perhaps it returns in two or more responses, when more than N values are requested.

Good Idea @StevenLooman. I will try to find the magic number.
With only the default activated properties it worked fine.

Ok, had a quick test:
6 sensors and 2 properties on diag are working fine.
If i have 7 sensors (and the 2 diag props) enabled, it fails.
And after disabling one of the diag properties and can use one sensor more.
I would like to say that @StevenLooman is right.
It fails on requesting more then 8 sensors or response changes in this case.

Found this from documetation, so 8 is max.

Found this from documetation, so 8 is max.

Thanks, I haven't had time to fix it yet but this helps!

My spare time was a bit sparse, but I did just manage to quickly draft something working (in my prod HA). Would anyone be able to test this branch? @lexusburn maybe, as you reported the issue?
PR: #66
Branch: 60-latest-version-seems-to-break-if-more-then-only-a-few-values-are-requsted

@golles your fix works find for me.
I've tried it and had enabled 18 different values for a test and it works fine. :-)

Awesome and thanks for the swift feedback :-)
If you don't mind, I'd like to keep the ticket open until the PR has been merged, I want to improve the code a little bit and see if I can get the coverage check to pass as well. Shouldn't be more than a couple of days.

Found this from documetation, so 8 is max.

Where can we find this documentation?

Sorry, i thought that i added link. Multical 601 KMP

Sorry, i thought that i added link. Multical 601 KMP

Thank you!


red badge on main view is not fullly visible if value >= 100

probably depends on screen width. Problem occurrs with simulator, device Pixel 3a.

Changed it so it will now display a star instead of the number. Seems to be a restriction of the leading action of the app bar.


Lots of "Error executing query: (sqlite3.OperationalError) database is locked (Background on this error at: http://sqlalche.me/e/e3q8)"

Home Assistant release with the issue:
0.105.5
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio on docker over RPi3
Component/platform:
Description of problem:
Seeing a lot of "Error executing query: (sqlite3.OperationalError) database is locked (Background on this error at: http://sqlalche.me/e/e3q8)" since upgrading to 0.81.1

Please fill out the issue template, you can find it by clicking on New Issue and then selecting Report a bug with Home Assistant. Copy and paste the provided template into this already created issue, click preview to take a look at the empty template and then fill out as much as you can. Any additional information can be helpful!
Thanks for understanding :)


agrifood - cspell found spelling errors

Spell check scanning of agrifood detected spelling errors. This service directory is opted out of PR spell checking in PR #17142 to keep merges unblocked.
What to do

Ensure Node.js is installed (https://nodejs.org/en/download/). This will include npx
Delete the service's entry in .vscode/cspell.json's ignorePaths field. It will look like: sdk/agrifood/**/*. You need to do this to enable checking the files.
From the root of the repo run spell check using npx cspell lint --config '.vscode/cspell.json' --no-must-find-files "sdk/agrifood/**"
Fix detections according to http://aka.ms/azsdk/engsys/spellcheck use the "False positives" section to fix false positives
Check in changes (including the change to .vscode/cspell.json where the ignorePaths is updated to remove the entry for this service.). You may need to run git add -f .vscode/cspell.json to force adding the changes to the file in git.

Spell checking output
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/karma.conf.js:77:18 - Unknown word (lcovonly)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/karma.conf.js:77:49 - Unknown word (lcov)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/package.json:64:67 - Unknown word (prettierrc)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/package.json:67:38 - Unknown word (mkdirp)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/package.json:68:52 - Unknown word (prettierrc)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/package.json:123:6 - Unknown word (mkdirp)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/README.md:84:112 - Unknown word (NDVI)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/review/agrifood-farming.api.md:605:40 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/review/agrifood-farming.api.md:698:124 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/review/agrifood-farming.api.md:1602:109 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/review/agrifood-farming.api.md:1614:35 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/review/agrifood-farming.api.md:2999:5 - Unknown word (ndvi)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/farmBeats.ts:126:25 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/farmBeats.ts:184:20 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/farmBeats.ts:199:21 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/farmBeats.ts:384:74 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/models.ts:821:17 - Unknown word (NDVI)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/models.ts:822:3 - Unknown word (ndvi)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/responses.ts:183:40 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/responses.ts:527:35 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/src/responses.ts:616:36 - Unknown word (Iddefault)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/test/public/farmHeirarchy.spec.ts:15:16 - Unknown word (jhjob)
/home/djurek/azure-sdk-for-js/sdk/agrifood/agrifood-farming-rest/test/public/farmHeirarchy.spec.ts:16:21 - Unknown word (jhboundary)
/home/djurek/azure-sdk-for-js/sdk/agrifood/ci.yml:30:19 - Unknown word (azurerestagrifoodfarming)

Closing this as we will re-open issues per-package and according to feedback in https://github.com/Azure/azure-sdk-for-js/pull/17142


Feature/support forkjoinpool

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[ ] Update the documentation to include this new feature.

[ ] Tests(including UT, IT, E2E) are added to verify the new feature.

[ ] If it's UI related, attach the screenshots below.

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. https://github.com/apache/skywalking/issues/10680

[x] Update the CHANGES log.

This doc should be updated, https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/bootstrap-plugins/
And as a new plugin is being added, you should update supported-list and plugin-list, otherwise, CI would fail.

ok

Notice, the code format should be fixed.
  Error:  /home/runner/work/skywalking-java/skywalking-java/test/plugin/scenarios/jdk-forkjoinpool-scenario/src/main/java/org/apache/skywalking/apm/testcase/jdk/forkjoinpool/controller/CaseController.java:44:5: 'VARIABLE_DEF' has more than 1 empty lines before. [EmptyLineSeparator]
  Audit done.
  [INFO] There is 1 error reported by Checkstyle 8.38 with /home/runner/work/skywalking-java/skywalking-java/apm-checkstyle/checkStyle.xml ruleset.
  Error:  scenarios/jdk-forkjoinpool-scenario/src/main/java/org/apache/skywalking/apm/testcase/jdk/forkjoinpool/controller/CaseController.java:[44,5] (whitespace) EmptyLineSeparator: 'VARIABLE_DEF' has more than 1 empty lines before.

not report this in my loacl when execute the test, it seems not check test code style


Moving tns_modules inside app folder.

Ping @Fatme @atanasovg @dtopuzov

Since this is a breaking change for the CI builds and the CLI we'd like to receive confirmation of acknowledgement before we move forward with merging it.
This also means that the CI build for this patch will fail (as it has), even though this is a good patch.

Changed to be backwards compatible so it can be merged now.

:+1:


Error with line magic while trying to import jar

Hello, love IJava so far.
I was following the 3rd Party Dependencies in an IJava Notebook on the binder jupyter lab, and was trying to use the following
List<String> added = %jars /usr/share/java/*.jar
I have put my jar file in the notebook that I am using. Here is the file

When I do the following
List<String> added = %jars jaw-2.0/lib/*.jar
I get this error:

When I wanted to check this issue out at io.github.spencerpark.ijava.runtime.Magics.lineMagic(Magics.java:19) I could only find https://github.com/SpencerPark/IJava/blob/master/src/main/java/io/github/spencerpark/ijava/runtime/Magics.java but no https://github.com/SpencerPark/IJava/blob/master/src/main/java/io/github/spencerpark/ijava/runtime/Magics/lineMagic.java that might correspond with the error.
Any ideas what's going on/what I'm missing?

Thanks for the detailed report @IzzyIllari. This is indeed a bug. It's coming from the glob parser when the pattern contains a *. I would consider this error message a bug as well for how poorly it conveys the problem.
Until that is patched you can use List<String> added = %jars jaw-2.0/lib/ which will add all jars from that folder.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: JonathanCalvoObando sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Project link broken - opensource.wartner.io

Redirects to https://blog.hoodpacker.de/, SSL cert is mismatched if the redirect is intentional

Thank you! I was about to create this site. In the meantime I updated the url to my website.


Fix row limit config, add row limit support to DuckDB.

Fixes a couple issues:

The logic to pass updated options to the worker was looking at changes to connection configs, but row limit is a malloy level config option.
The logic to retrieve the row limit was never added to duckdb connections, so it was always defaulting to 10.

If you merge main, this should work now.


MenuItem - Overriding background color of selected menu items is not honored in some common cases

[X] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The background color of "selected" menu items should reflect the provided override.
Current Behavior

Overriding the background color of selected menu items only works if you use "linear" or if you add "!important". This happens both when using classes overrides or global template overrides.
Steps to Reproduce (for bugs)

See this snippet https://stackblitz.com/edit/react-yqpcez - this shows the global template override, but the issue also happens when using the "classes" override per component.
Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.38

React
Latest

browser
Chrome lastest

etc

Pasting the stackblitz code here too just in case:
import React, {Component} from 'react';
import {render} from 'react-dom';
import {MuiThemeProvider, createMuiTheme} from 'material-ui/styles';
import {MenuItem} from 'material-ui/Menu';

const theme = createMuiTheme({
  overrides: {
    MuiMenuItem: {
      selected: {
        // Does not work:
        // background: 'red',

        // Does not work:
        // backgroundColor: 'red',

        // Works (without the need for !important)
        background: 'linear-gradient(45deg, red 30%, orange 90%)',

        // Works (must use !important):
        // backgroundColor: 'red !important',

        // Works (must use !important):
        // background: 'red !important',
      },
    },
  },
});

function App() {
  return (
    <MuiThemeProvider theme={theme}>
      <MenuItem selected>123</MenuItem>
    </MuiThemeProvider>
  );
}

render(<App />, document.getElementById('root'));

@lirbank Here is the style of the MenuItem component:
https://github.com/mui-org/material-ui/blob/4664708aad5cc15a17505909103b7bbb2de4f7db/src/Menu/MenuItem.js#L10-L24
As you can see, the selected is empty. You need to increase the specificity.
The following diff makes it work:
const theme = createMuiTheme({
  overrides: {
    MuiMenuItem: {
-     selected: {
-       backgroundColor: 'orange',
+     root: {
+       '&$selected': {
+         backgroundColor: 'orange',
+       },
      },
    },
  },
});

This "way" of writing styles isn't generalized yet, but I plan on doing so before the stable release of v1 as it's documented in the ROADMAP: https://material-ui-next.com/discover-more/roadmap/#breaking-changes-before-v1.

Why this issue is closed?
I exactly did this:

The following diff makes it work:
const theme = createMuiTheme({
  overrides: {
    MuiMenuItem: {
-     selected: {
-       backgroundColor: 'orange',
+     root: {
+       '&$selected': {
+         backgroundColor: 'orange',
+       },
      },
    },
  },
});

But still doesn't really work, rather give me a weird behavior. If I double click another Menu Item and hold it, that's the only time the before-selected item chenged its color to orange.

@Bouncue Please open a separate issue and follow the template. It seems to work fine. You need to consider that e.g. hover+selected has higher specificity.

@lirbank Here is the style of the MenuItem component:
https://github.com/mui-org/material-ui/blob/4664708aad5cc15a17505909103b7bbb2de4f7db/src/Menu/MenuItem.js#L10-L24
As you can see, the selected is empty. You need to increase the specificity.
The following diff makes it work:
const theme = createMuiTheme({
  overrides: {
    MuiMenuItem: {
-     selected: {
-       backgroundColor: 'orange',
+     root: {
+       '&$selected': {
+         backgroundColor: 'orange',
+       },
      },
    },
  },
});

This "way" of writing styles isn't generalized yet, but I plan on doing so before the stable release of v1 as it's documented in the ROADMAP: https://material-ui-next.com/discover-more/roadmap/#breaking-changes-before-v1.

You saved my life! had been trying to figure this out for 3 days.

Why this issue is closed?
I exactly did this:

const theme = createMuiTheme({
  overrides: {
    MuiMenuItem: {
-     selected: {
-       backgroundColor: 'orange',
+     root: {
+       '&$selected': {
+         backgroundColor: 'orange',
+       },
      },
    },
  },
});

But still doesn't really work, rather give me a weird behavior. If I double click another Menu Item and hold it, that's the only time the before-selected item chenged its color to orange.

It works perfectly fine. Maybe u need to override the backgroungColor for the selected MenuItem like this:-
const styles = makeStyles(theme => ({
  root:{
    '&$selected': {
      backgroundColor: 'rgba(0,0,0,0)',
    },
    backgroundColor: 'rgba(0,0,0,0)',

  },
  selected:{
    extend:'root',
  }
}));


[Doc] Add processing guarantee for connector

Fix https://github.com/apache/pulsar/issues/5015

@tuteng could you please help review? Thank you

run java8 tests


Discord channel

Hi,
I have some general questions/discussions that aren't really suitable for Github issues. Would you consider starting a discord server dedicated to Whim?
Feel free to add me (marpe357)

Sure, I've created one at https://discord.gg/gEFq9wr7jb, and invited you.


Upgrade to Postgres 17 and libpg_query 6.0.0

Needs version bump and changelog entry, otherwise good to ship!


Discord account is always online

When using mx-puppet-discord with user token, and also when using it with a bot, the Discord account or bot constantly appears online. It would be nice if the status switched between "online" and "invisible" depending on what's going on on Matrix!

This requires https://github.com/matrix-org/matrix-doc/pull/2409

So for bridging anything besides messages, we need that PR?

basically, yes

It's surprising Matrix doesn't have that since a long time ago; since it was designed with bridges in mind

added in https://github.com/matrix-discord/mx-puppet-discord/commit/0a21bb8ad5b9c41ad346de99df5a38d384d9c9ef


fix(install): install packages before starting services

Which issue(s) this PR fixes:

On SLES OS, the iSCSI package is not installed by default, so longhornctl should install the package before starting the iSCSI service.
Issue longhorn/longhorn#9182
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x


More examples

Great project, but hard to figure out the code.
Could you please add some more examples and documentation.
Examples from this repository do not match the documentation. Where are Driver and Evaluator? The examples from the DeepCFR project are too complicated.
How to use each component of framework?
How can they be used in interactive mode?

The code is well documented and released for free. Where do examples not match the docs? Many people managed to figure it out and use the repository and at least one research team based a paper on it. Show some gratitude man, this is 100s of hours of work released for free. I'm not helping you this way.