Azure Key Vault component: map has no entry for key "SECRETS_VAULTURI"

Is there an existing issue for this?

[x] I have searched the existing issues

Describe the bug
In what appears to be very similar to this discussion I've attempted to deploy a .NET 8 application running the latest Aspire versions with an Azure Key Vault deployment.
Each deployment of "azd deploy" fails with:

ERROR: failed deploying service 'abc123': failed executing template file: template: manifest template: 27:23: expected "manifest template" at <.Env.SECRETS_VAULTURI>: map has no entry for key "SECRETS_VAULTURI".

It doesn't seem to matter if I set the Vault URI in my appsettings.json or not, all deployments with the AzureKeyVault reference on my singular service appear to fail in the same way.
Expected Behavior
I expected the solution to deploy without error.
Steps To Reproduce

Add  to AppHost
Add  to client app
Update program.cs on client app:

var builder = WebApplication.CreateBuilder(args);
builder.AddAzureKeyVaultClient("secrets");

Update program.cs on app host:

const string azureKeyVaultRef = "secrets";
var secrets = builder.ExecutionContext.IsPublishMode
    ? builder.AddAzureKeyVault(azureKeyVaultRef)
    : builder.AddConnectionString(azureKeyVaultRef);

builder.AddProject<Projects.MyProject>("myproject")
  .WithReference(secrets);

Attempt an azd deploy and observe it fail.
Exceptions (if any)
ERROR: failed deploying service 'abc123': failed executing template file: template: manifest template: 27:23: expected "manifest template" at <.Env.SECRETS_VAULTURI>: map has no entry for key "SECRETS_VAULTURI".
.NET Version info
.NET SDKs installed:
8.0.303 [C:\Program Files\dotnet\sdk]
9.0.100-rc.2.24474.11 [C:\Program Files\dotnet\sdk]
9.0.100 [C:\Program Files\dotnet\sdk]
Anything else?
No response

@WhitWaldo did you run azd provision first?

I tried and then it wanted me to provide a secret value for something and didn't like anything I typed in. I wound up just creating a brand new .NET 9 Aspire project and migrating everything over and it worked like a charm, so it was something about migrating between the two it just didn't care for.


Q: can it help here https://github.com/oracle/graal/issues/1476?

I'm getting Spring Boot native image building exception.
Is it the case?

I find 19.1 has a problem that causes spring boot issues - they have fixed https://github.com/oracle/graal/issues/1462 but I am waiting for a release with it in before moving to 19.1 (presumably 19.1.1).  For now you are better off using 19.0.2 and this feature - if you app is doing the kind of things found in the samples folder then it may work but there is a way to go before things generally work.


Feature #33

Pr contains two recipes for issue #33 and covers the vanilla salesforce part of it. One of the recipes contains Account, Contact, and multiple opps related to the account and contact created and another recipe contains a salesforce lead example ( might not be part of the issue, just created it since there is no lead example in the repo)

Updated the PR by removing the geolocation fields as suggested


Fix style inheritance

:tada: This PR is included in version 4.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HBASE-26553 OAuth Bearer authentication mech plugin for SASL

Initial commit for JWT authentication.
Details are in the Jira: https://issues.apache.org/jira/browse/HBASE-26553

: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
0m 27s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
10m 57s
master passed

+1 :green_heart:
checkstyle
2m 26s
master passed

+1 :green_heart:
spotbugs
19m  1s
master passed

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
11m  4s
the patch passed

-0 :warning:
javac
11m  4s
root generated 34 new + 1632 unchanged - 0 fixed = 1666 total (was 1632)

-0 :warning:
checkstyle
2m 26s
root: The patch generated 12 new + 17 unchanged - 0 fixed = 29 total (was 17)

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

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

+1 :green_heart:
hadoopcheck
23m 50s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

+1 :green_heart:
spotbugs
20m 25s
the patch passed

_ Other Tests _

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

114m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile xml

uname
Linux 4a0ed75e831f 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b5cf3cdc5c

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-general-check/output/diff-compile-javac-root.txt

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-general-check/output/diff-checkstyle-root.txt

Max. process+thread count
126 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 27s
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 25s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
2m 49s
master passed

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

+1 :green_heart:
javadoc
4m  6s
master passed

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 22s
hbase-common generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-0 :warning:
javadoc
2m 14s
root generated 2 new + 54 unchanged - 0 fixed = 56 total (was 54)

_ Other Tests _

-1 :x:
unit
285m 45s
root in the patch failed.

328m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 48f73397b479 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 / b5cf3cdc5c

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/testReport/

Max. process+thread count
4488 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m  1s
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 17s
Maven dependency ordering for branch

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

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

+1 :green_heart:
checkstyle
2m  0s
master passed

+1 :green_heart:
spotbugs
14m 41s
master passed

-0 :warning:
patch
2m 52s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
9m  0s
the patch passed

-0 :warning:
javac
9m  0s
root generated 11 new + 1628 unchanged - 0 fixed = 1639 total (was 1628)

-0 :warning:
checkstyle
2m  0s
root: The patch generated 2 new + 17 unchanged - 0 fixed = 19 total (was 17)

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

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

+1 :green_heart:
hadoopcheck
19m 48s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

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

_ Other Tests _

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

96m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile xml

uname
Linux 190f6f2c74a8 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 / e96df8bf40

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-general-check/output/diff-compile-javac-root.txt

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-general-check/output/diff-checkstyle-root.txt

Max. process+thread count
141 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
3m 14s
the patch passed

+1 :green_heart:
javac
3m 14s
the patch passed

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

+1 :green_heart:
javadoc
4m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
190m 50s
root in the patch passed.

240m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e4a26493b416 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 / e96df8bf40

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/testReport/

Max. process+thread count
7037 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  6s
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 47s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
3m  7s
master passed

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

+1 :green_heart:
javadoc
4m 22s
master passed

-0 :warning:
patch
14m 40s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 21s
hbase-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
javadoc
2m 47s
root generated 1 new + 57 unchanged - 0 fixed = 58 total (was 57)

_ Other Tests _

-1 :x:
unit
447m 52s
root in the patch failed.

497m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 02f8d6c7992b 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e96df8bf40

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/testReport/

Max. process+thread count
4412 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/4/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 19s
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 26s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
9m  7s
master passed

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

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

-0 :warning:
patch
2m 55s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
9m  7s
the patch passed

-0 :warning:
javac
9m  7s
root generated 3 new + 1628 unchanged - 0 fixed = 1631 total (was 1628)

+1 :green_heart:
checkstyle
2m  1s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
19m 50s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

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

_ Other Tests _

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

94m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile xml

uname
Linux c6c6a188993e 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 70cb9b0ba9

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-general-check/output/diff-compile-javac-root.txt

Max. process+thread count
141 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
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 24s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
3m 12s
master passed

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

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

-0 :warning:
patch
14m 26s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
3m 16s
the patch passed

+1 :green_heart:
javac
3m 16s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
194m 42s
root in the patch passed.

242m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ae9d3a0d81b7 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 / 70cb9b0ba9

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/testReport/

Max. process+thread count
6963 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
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
4m 21s
master passed

+1 :green_heart:
compile
3m  0s
master passed

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

+1 :green_heart:
javadoc
4m  7s
master passed

-0 :warning:
patch
14m  0s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 20s
hbase-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
javadoc
2m 18s
root generated 1 new + 57 unchanged - 0 fixed = 58 total (was 57)

_ Other Tests _

-1 :x:
unit
427m 24s
root in the patch failed.

473m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux be5b43feb684 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 70cb9b0ba9

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/testReport/

Max. process+thread count
4502 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/5/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
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  1s
The patch does not contain any @author tags.

_ master Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
2m  0s
master passed

+1 :green_heart:
spotbugs
14m 52s
master passed

-0 :warning:
patch
2m 52s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
8m 57s
the patch passed

-0 :warning:
javac
8m 57s
root generated 3 new + 1628 unchanged - 0 fixed = 1631 total (was 1628)

+1 :green_heart:
checkstyle
1m 57s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
19m 28s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

+1 :green_heart:
spotbugs
15m 47s
the patch passed

_ Other Tests _

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

92m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile xml

uname
Linux a8ee68066013 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / baeb51ff8a

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-general-check/output/diff-compile-javac-root.txt

Max. process+thread count
141 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
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 36s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
3m 13s
master passed

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

+1 :green_heart:
javadoc
4m 56s
master passed

-0 :warning:
patch
14m 18s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
3m 15s
the patch passed

+1 :green_heart:
javac
3m 15s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
191m 38s
root in the patch passed.

239m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3c7f2bd4a469 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 / baeb51ff8a

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/testReport/

Max. process+thread count
7035 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 12s
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 36s
Maven dependency ordering for branch

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

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

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

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

-0 :warning:
patch
16m 17s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
3m 24s
the patch passed

+1 :green_heart:
javac
3m 24s
the patch passed

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

-0 :warning:
javadoc
0m 26s
hbase-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
javadoc
3m  2s
root generated 1 new + 57 unchanged - 0 fixed = 58 total (was 57)

_ Other Tests _

+1 :green_heart:
unit
446m  4s
root in the patch passed.

499m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f6b45885180d 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / baeb51ff8a

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/testReport/

Max. process+thread count
4510 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/6/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 26s
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 33s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
10m  5s
master passed

+1 :green_heart:
checkstyle
2m 22s
master passed

+1 :green_heart:
spotbugs
18m  1s
master passed

-0 :warning:
patch
13m 33s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

-0 :warning:
javac
11m 18s
root generated 1 new + 1628 unchanged - 0 fixed = 1629 total (was 1628)

+1 :green_heart:
checkstyle
2m 57s
root: The patch generated 0 new + 17 unchanged - 1 fixed = 17 total (was 18)

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

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

+1 :green_heart:
hadoopcheck
25m 52s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

+1 :green_heart:
spotbugs
22m 43s
the patch passed

_ Other Tests _

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

118m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile xml

uname
Linux a1e770168d8c 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7972b2ebbb

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-general-check/output/diff-compile-javac-root.txt

Max. process+thread count
126 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  4s
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 26s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
3m 18s
master passed

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

+1 :green_heart:
javadoc
5m 24s
master passed

-0 :warning:
patch
14m 43s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
3m 16s
the patch passed

+1 :green_heart:
javac
3m 16s
the patch passed

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

+1 :green_heart:
javadoc
5m 54s
the patch passed

_ Other Tests _

-1 :x:
unit
172m 14s
root in the patch failed.

221m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux cc204cba9dc5 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 / 7972b2ebbb

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/testReport/

Max. process+thread count
3785 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
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 25s
Maven dependency ordering for branch

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

+1 :green_heart:
compile
2m 47s
master passed

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

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

-0 :warning:
patch
13m 25s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 21s
hbase-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
javadoc
2m 13s
root generated 1 new + 57 unchanged - 0 fixed = 58 total (was 57)

_ Other Tests _

-1 :x:
unit
382m 56s
root in the patch failed.

426m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4df5c30cde57 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 / 7972b2ebbb

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/testReport/

Max. process+thread count
5178 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-resource-bundle hbase-server hbase-examples . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3934/7/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Alright! I was actually able to test this out today using Knox. I think there are a couple of high level things we need to figure out

HBase clients will expect that renewals transparently happen. Either, we need a renewer thread in hbase to get a new bearer token before it expires (I think this is possible, but we'd have to know where to get the new one from). Otherwise, we'd have to think about usign the bearer token to get an hbase delegation token (which seems like too many tokens, tbh)
How will users provide the bearer token into their HBase client? Environment variable? Well-known file?
I tried enabling the RPC encryption from HBASE-16414 but regrettably can still see plaintext data going over the wire. Maybe that's just a bug in this patch, or maybe it's a bigger HBase SASL issue. Either way, we need encryption if we enable this auth'n feature.
I would like to see a standalone (no external service dependency) test included in hbase-examples, rather than just a client. However, I don't know of a JWT-providing server we could easily embedded into a test. Maybe knox could do this, or maybe nimbus has some testing server?
Need to get some additions to the hbase book.

Now, given how big this patch is already, I think I'd suggest we work through these on a feature branch rather than try to do them in a single commit. WDYT, Andor? I think this approach would let us do some iteration more easily.

Closing this PR due to feature branch request.

Follow-up PR https://github.com/anmolnar/hbase/pull/1


Attach latest console errors

https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/onerror
This looks like it would let us locally keep track of errors and attach them to reports.

window.onerror() and adding an event listener for errors do not seem to catch ANY errors outside physically calling window.onerror... I'll keep looking.

In regards to error handling, it doesn't look like we can do much without some extensive patching. Basically the main problem is that window.onerror() callbacks are only called when there is no error handler in place already. This means that if a dev actually uses try and catch blocks, then we don't receive the errors. There are also numerous problems with sync/async execution and calling window.onerror(). I'm not saying it's impossible, but it appears to be fairly intensive work (and way beyond my 4 month old knowledge of JS). At least, that's my understanding.

Left a message in the Leagues Discord which some of you saw. I remember struggling to handle uncaught errors / promise rejections in initial prototyping of a catch all error handler. I'm sure I tried onError first and perhaps a few other things, but they didn't work.. This did work, so give it a try:
window.addEventListener('error', event => { s_ERROR_HANDLER(event.error, event); });
window.addEventListener('unhandledrejection', event => { s_ERROR_HANDLER(event.reason, event); });

Im

Left a message in the Leagues Discord which some of you saw. I remember struggling to handle uncaught errors / promise rejections in initial prototyping of a catch all error handler. I'm sure I tried onError first and perhaps a few other things, but they didn't work.. This did work, so give it a try:
window.addEventListener('error', event => { s_ERROR_HANDLER(event.error, event); });
window.addEventListener('unhandledrejection', event => { s_ERROR_HANDLER(event.reason, event); });

Im affraid it wont solve the issue if someone using a try...catch block in the code. In this case window.onerror will not be called.

As mentioned on Discord there is no practical reason to do anything with caught errors / handled rejections in someone's code as that is intentional control flow. What makes sense is to capture / record uncaught errors / unhandled rejections and then intuit the source of the error to Foundry or specific modules / systems by filtering the stack trace. The above code snipped should work vs onerror.

@IamWarHead
I agree that handled errors don't need to be included in this initially. If we want to support that we would have to provide some logging function to module devs like you've suggested in the past, but that's an alright short-fall right now.
Using the eventListeners for unhandledrejections and errors is already going to be useful and will provide a proof of concept for more functionality later. That's a great lead, thanks @typhonrt

+1 for this
Since we can't easily ask the user to check their console for errors as they may not follow the issue created, some reports can never be investigated.


Fix some mappings

When retrieving a leaderboard, we would sometimes get an AutoMapper exception for any run that does not have a video. This is because we are missing a null-check on "source" in the VideosConverter. Handling "source is null" fixed the problem for SOME affected runs... but I did find some edge cases where, for some reason, source was NOT null, but source.Links was. Adding the additional null check fixes those additional problems.
When searching games and embedding categories, we would sometimes get an AutoMapper exception for any categories that allow "up to" a certain number of players (rather than requiring an exact number). This is because we were not using the PlayersTypeConverter for this embed. This likely went unnoticed because there are only two options for the PlayersType enum: "exactly" and "up-to". If the SRC API reports a value of "exactly" (by far the more common value among SRC categories), then AutoMapper's default behavior of Enum.TryParse gives us the correct value. It is only when SRC reports a value of "up-to" that we would get an error. Using the PlayersTypeConverter fixes this problem.

Thanks for the pull request for these bug fixes - definitely a couple oversights on my side.  I'll get a new nuget package out with these fixes shortly.

Thanks for the merge, and for making this library in the first place! I've used it for a few personal projects with great success, and I'm grateful that it exists and is clean and easy to use. Cheers!

I'm happy to hear you're using it!  I have a new version in the works where I actually pull out AutoMapper since it's a little overkill I think, and removing it should cut back on memory use.  I'm also working on adding some attributes to help improve the debugging experience when working with the library.  Also, please let me know if there's anything you'd like to see added to the library.


Add option to remove currently open file from GoTo file menu

Whe using the "Go To File..." shortcut, the files listed are in sorted by most recently opened. That means the current file is the one on top (because it's most recent), which means if I hit Enter immediately, VS Code does nothing (because I'm already in the file).
I want the file I was in previously to be the one at the top so I can use it similar to how Ctrl-Tab functions. I don't want to use Ctrl-Tab because the menu requires holding Ctrl to stay open and only lists open files.
The option would be

enabled (default): current file is displayed at the top of the "Go To File..." menu
disabled: current file is not display in the drop down, but is displayed when searching

There is a command workbench.action.quickOpenPreviousEditor you can bind that keybinding to which will do that.


chore: release v0.3.7

:robot: I have created a release beep boop
0.3.7 (2024-04-07)
What's Changed

Revert "fix(exec): quote arguments passed to shell (#102)" by @coffeebeats in https://github.com/coffeebeats/gdbuild/pull/103
feat(ci): define an action to run the template command by @coffeebeats in https://github.com/coffeebeats/gdbuild/pull/104

Full Changelog: https://github.com/coffeebeats/gdbuild/compare/v0.3.6...v0.3.7

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/coffeebeats/gdbuild/releases/tag/v0.3.7 :sunflower:


Build fails with CS9057 error due to analyzer version compiler conflict

Describe the bug
We have an internal scaffolder template we use to create new .NET applications. This template regularly updates the versions of its dependencies it uses and when a new application is scaffolded it dynamically takes the latest AWS SDK patch versions from NuGet.
This morning as part of a dependabot update and subsequent test of the generator for .NET 6, the build now fails with the following error:
    CSC : error CS9057: The analyzer assembly '/home/runner/.nuget/packages/awssdk.securitytoken/<IP_ADDRESS>/analyzers/dotnet/cs/AWSSDK.SecurityToken.CodeAnalysis.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'. [/tmp/984e20373103b72103fd4a0204e8acfd3d668ba2/src/MyApp/MyApp.csproj]
    CSC : error CS9057: The analyzer assembly '/home/runner/.nuget/packages/awssdk.simplesystemsmanagement/<IP_ADDRESS>/analyzers/dotnet/cs/AWSSDK.SimpleSystemsManagement.CodeAnalysis.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'. [/tmp/984e20373103b72103fd4a0204e8acfd3d668ba2/src/MyApp/MyApp.csproj]

I've not seen this in applications targeting .NET 7 (or at least, not yet).
The last successful CI was 20 hours ago, suggesting the versions published overnight have introduced this issue.
Expected Behavior
The application compiles.
Current Behavior
The application does not compile.
Reproduction Steps
Compile an application targeting .NET 6 with the 6.0.411 SDK which references the AWSSDK.SecurityToken and AWSSDK.SimpleSystemsManagement NuGet packages.
Possible Solution
Downgrade the dependency used to build the .CodeAnalysis packages to be compatible with the C# compiler that ships with the .NET 6 SDK.
Additional Information/Context
No response
AWS .NET SDK and/or Package version used

AWSSDK.SecurityToken <IP_ADDRESS>
AWSSDK.SimpleSystemsManagement <IP_ADDRESS>

Targeted .NET Platform
.NET SDK 6.0.411 and net6.0
Operating System and version
Linux

Confirmed not an issue with the following package versions:

AWSSDK.SecurityToken <IP_ADDRESS>
AWSSDK.SimpleSystemsManagement <IP_ADDRESS>

Same issue here, our automatic minor/patch version updates for NuGet packages triggered the following error in our builds:
CSC : error CS9057: The analyzer assembly '/root/.nuget/packages/awssdk.sqs/<IP_ADDRESS>/analyzers/dotnet/cs/AWSSDK.SQS.CodeAnalysis.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'

Same error here in
AWSSDK.ApiGatewayManagementApi.CodeAnalysis.dll
AWSSDK.DynamoDBv2.CodeAnalysis.dll
AWSSDK.S3.CodeAnalysis.dll
AWSSDK.SecretsManager.CodeAnalysis.dll
AWSSDK.SimpleSystemsManagement.CodeAnalysis.dll
AWSSDK.SQS.CodeAnalysis.dll
AWSSDK.StepFunctions.CodeAnalysis.dll

I think the recent upgrading of Microsoft.CodeAnalysis is a bit too restrictive in terms of the versions of the compiler tooling that it supports. I think the maintainers will want to target a version as low as feasibly possible.
Here's a mapping of the versions to VS versions to give an idea of where best to target:
https://learn.microsoft.com/en-us/visualstudio/extensibility/roslyn-version-support?view=vs-2022

Last week I changed the code analysis projects to target netstandard2.0 (from net45 - the commit @slang25 referenced), but on my tests I only used a net7.0 application.
While we work on a fix (selecting the minimal version that works with netstandard), the workaround is using SDK packages released before Jun 30.

Update: I have an internal PR downgrading the Microsoft.CodeAnalysis dependency to version 2.10.0. Here's my test on CodeBuild (using Ubuntu and .NET 6):
Before:
$ dotnet new console
$ dotnet add package AWSSDK.SageMaker --version 3.7.142
$ dotnet build
CSC : warning CS9057: The analyzer assembly '/root/.nuget/packages/awssdk.sagemaker/3.7.141/analyzers/dotnet/cs/AWSSDK.SageMaker.CodeAnalysis.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'. [/codebuild/output/src4008071538/src/testbefore/testbefore.csproj]
    1 Warning(s)
    0 Error(s)
Time Elapsed 00:00:07.23

After (temppkg is a local source with the modified package - as it's not available on NuGet yet):
$ cd testafter
$ cat testafter.csproj
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <RestoreSources>$(RestoreSources);../temppkg;https://api.nuget.org/v3/index.json</RestoreSources>
  </PropertyGroup>
</Project>
$ dotnet add package AWSSDK.SageMaker --version 3.7.143
$ dotnet build
  Determining projects to restore...
  All projects are up-to-date for restore.
  testafter -> /codebuild/output/src4008071538/src/testafter/bin/Debug/net6.0/testafter.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:01.30

Most of our team was off today due to the 4th of July, I'll follow up in the morning so that we can get this released as soon as possible.

Last week I changed the code analysis projects to target netstandard2.0 (from net45 - the commit @slang25 referenced), but on my tests I only used a net7.0 application (in VS2022).
While we work on a fix (selecting the minimal version of Microsoft.CodeAnalysis that works with netstandard), the workaround is using SDK packages released before Jun 30.

And these would be patch versions. These kinds of changes would indicate a new minor version. We've been impacted twice in the last week  by AWSSDK changes released as prerelease/patch changes that should arguably have been minor versions. Worth keeping an eye on

After talking to the team this morning, we decided to revert that previous commit (https://github.com/aws/aws-sdk-net/commit/20ca9691fe619209bd1a4cee16b974149f1862d6) to prevent further impact (and to make sure there are no framework / analyzer combinations we missed). We'll revisit this change soon (we're going trough updating the build internals used by the SDK), but will coordinate better by making it visible in the changelog and updating the package versions appropriately.
I ran the same test I mentioned in my comment yesterday with the new version, CS9057 does not appear anymore (and all service packages have been updated and pushed to NuGet):
$ dotnet new console
$ dotnet add package AWSSDK.SecurityToken --version <IP_ADDRESS>
$ dotnet build /warnaserror
MSBuild version 17.3.2+561848881 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
  testapp -> /codebuild/output/src3140019177/src/testapp/bin/Debug/net6.0/testapp.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:08.95

Apologies again for the inconvenience.

@oshea00 That's a good call out, this change should've been at least mentioned in the changelog (which we are doing for the fix).
What were the other changes that impacted you?

@dscpinheiro Thank you. Actually that other issue was related to a patch change in the java SDK for DynamoDb that was posted 1.12.498. In this case the change resulted in an error added to check AWS credential format where none had previously existed. This broke code using that dependency - as dummy credential slugs with underscores  "CHANGE_TO_MY_AWSCREDS" were suddenly non-conforming. Adding a new error to working code s/b a minor release change.

@oshea00 I asked the Java team and they recommended opening a new issue in their repo: https://github.com/aws/aws-sdk-java/issues/new/choose
Could you do that? They'll take a look.


Promote Teamnado 4242 to main-stable

Codecov Report
Base: 95.26% // Head: 95.76% // Increases project coverage by +0.49% :tada:

Coverage data is based on head (6c6164a) compared to base (dd47efa).
 Consider uploading reports for the commit 2ee137a to get more accurate results

Additional details and impacted files
@@               Coverage Diff               @@
##           main-stable      #84      +/-   ##
===============================================
+ Coverage        95.26%   95.76%   +0.49%
===============================================
  Files               31       31
  Lines              401      401
  Branches            97       97
===============================================
+ Hits               382      384       +2
+ Misses              16       14       -2
  Partials             3        3

Impacted Files
Coverage Δ

...components/SubscriptionTable/SubscriptionTable.tsx
87.95% <0.00%> (+1.20%)
:arrow_up:

src/components/ProductsTable/ProductsTable.tsx
100.00% <0.00%> (+1.40%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add fioctl place holder

Our release tooling will download fioctl and generate these docs
with fioctl gen-rst ./source/reference/fioctl/
Signed-off-by: Andy Doan<EMAIL_ADDRESS>

Docs for f8f63e5ac1d8699a56fdff82678e402ece4e53b5 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/547/docs/artifacts/html/index.html

@MatthewCroughan  - you should be able to take this PR and https://github.com/foundriesio/fioctl/pull/55 and produce the documentation for fioctl.
There will be a separate change I'll make in our release tooling that will do this when we publish our release documentation.

@MatthewCroughan - ping. are we ready to move forward on this?

Yeah, I have mentioned it in #90. Basically, I've written a bunch of stuff that I'm pushing up to #88 that I want to get merged and reviewed first. Once that is merged, I can begin putting everything I've done in that PR in its correct location.

Additionally, I did not notice this was wanted in master and not refactor. I will pull this into refactor when ready.


Added possibility to show minutes and seconds as the remaining time

I have added the possibility to choose between two modes via a Boolean variable called "useMinutesAndSecondsRepresentation" which is per default false. If the user decides to set this variable to true the timer will show the remaining time as minutes and seconds (rather than just seconds as before). I have also added a commented line to the example which the user can uncomment in order to see this new feature working.

Hello! Sorry for such a long waiting and thank you for the contribution!
You request has been merged, I will deploy the new version to cocoapods tonight.


Add ability to set the ACL in the Maven configuration

Though compilation respects ACLs present in the ODP, in practice it would be nice to be able to specify that in the pom.xml and not worry about whether a developer's individual copy of the app has its ACL in order.

Duplicate of https://github.com/OpenNTF/org.openntf.nsfodp/issues/42


Fix outgoingStream createTrack media type

outputStream::createTrack() track id assigned to media type. Please confirm expected behavior
const outputTrack = outputStream.createTrack({
   id: inputTrack.getId(),
   media: inputTrack.getMedia()
   });

There is an error in the PR, i will close this and merge the part of the change which is good.


Add New CLI Flag for Input Values Directory: --values-directory

What this PR does / why we need it
Motivation is #10416 reported by @tculp. This PR closes #10416.
Changes

New CLI flag  --values-directory (or) -d for loading directory name which has the values YAML files.
Test coverage for modified method MergeValues() and for the newly added internal function lsFiles().

Edit 1 (10-Feb-2023 in UTC): As discussed on #10416:

No changes to --values/-f 's behavior.
No default/sample values directory in helm create. Neither does the helm create --help includes the values directory in the tree structure.

Edit 2 (28-Feb-2023 in UTC): -d/--values-directory reads all YAML files recursively in the specified directory.
Edit 3 (28-Feb-2023 in UTC):

Precedence order swap for -d/--values-directory and -f/--values. A higher rank type of input when inputted later than lower or same precedence can override values.
Eg.: helm -d values.d -f values.yaml will override values from values.yaml with that of values.d if there are common keys.
Precedence order highest to least as follows:
Earlier: --set-file > --set-string > --set > --set-json > -d/--values-directory > -f/--values
Now: --set-file > --set-string > --set > --set-json > -f/--values > -d/--values-directory

Summary
In addition to 5 existing flag-based input methods (--values, --set, --set-file, --set-json & --set-string), the --values-directory, (or) -d in short, will load a directory with values YAML files recursively to the helm. Similar to the existing flags, this flag can be used with 3 sub-commands of the helm: install, lint & upgrade. The flag -d/--values-directory is least in precedence and so, values inputted using it can be overridden by any type of the input types in case of common keys and are specified later than -d/--values-directory in helm command.

Could we also consider the values.d capability for defining default values in the chart itself?  This would be very useful as the default values.yaml file in some charts can get quite large and unwieldy.
my-chart/
  Chart.yaml
  templates/
  values.d/
    foo.yaml
    bar.yaml

@sirianni That makes sense. Can you go thru #10416 where we are discussing the approaches on this? You can help by giving your thoughts on it.

Hi @sabre1041, this is the PR we talked about at KubeCon today.
Thanks in advance

Hi @Bhargav-InfraCloud,
I added a PR to your branch to support directories directly with the --values flag instead of the created --values-dir as I suggested in the Issue 10416

Should I create a new PR directly with the helm repo with the modifications I added in the PR to @Bhargav-InfraCloud's repo ?

Hey @Syst3m1cAn0maly, my apologies. I couldn't reply any sooner. I agree, adding this new behavior to the existing flag --values wouldn't break anything. But it is still a changed behavior of one of the most used flags. I think keeping the functionalities separated isn't a bad idea either (at least for now).
We had this as one of the approaches previously discussed in comment.
It's your call if you want to create a separate PR for helm directly. But I had to suggest, my suggestion to you would be to do it for helm v4 instead, regardless of the merge status of this current PR. More details about helm 4 are here.

No problem @Bhargav-InfraCloud ;)
Thank you for the explanations, I think I will create a PR for helm 4 as suggested unless there is a change of heart on the maintainers'side

FYI: Refactored my old changes and did a clean-up of tests.
Please review the PR.

@Bhargav-InfraCloud Not really qualified to review, but do have some usability questions.  It appears that the intent is to have separate values files which dont contradict each other within the directory.  but take something like grafana/loki where they have different values files(distributed & simple scalable) they may publish depending on the scale at which the admin wishes to operate.  How do you see this solution allowing that to happen?  Each of these values files would go into a different subdirectory?
What about if multiple files within the directory do happen to use the same object defined?  I see that this should be predictable at least in that its using Walk which follows lexical order, but this could lead to confusion if people arent aware of this.
My use case would be similar to the grafana one where we want to be able to include various values files within the helm chart from a packaging perspective and then be able to mix and match them as we see fit.  It would appear that in order to achieve that behavior with this, each file would need to go into a distinct subdir with its own file and then just reference the subdirs via -d like we would via -f if they were locally available.

Hi @ryan-dyer-sp,
The actual use case: if the values file grows too big to manage, split it into multiple files and group them in a directory, so that managing becomes easier. This is similar to how Linux groups configs (eg. /etc/sysctl.d).
Hence the --values-directory for the helm to recursively read all the .yaml files in the specified directory.

My use case would be similar to the grafana one where we want to be able to include various values files within the helm chart from a packaging perspective and then be able to mix and match them as we see fit. It would appear that in order to achieve that behavior with this, each file would need to go into a distinct subdir with its own file and then just reference the subdirs via -d like we would via -f if they were locally available.

Yes, you can specify each directory or file "in the order" so that the latter can replace the former. Multiple sub-directories should also work as long as they are organized in the lexical order.
Note: Values from all other values setting flags (--values, --set-json, --set, --set-string, --set-file, --set-literal) can override the ones from --values-directory if matching.

What about if multiple files within the directory do happen to use the same object defined? I see that this should be predictable at least in that its using Walk which follows lexical order, but this could lead to confusion if people arent aware of this.

Yes, it follows the lexical order. I think it would've been more confusing if it hadn't followed the lexical order 😄 But I agree, it is better to add that detail. Updated the flag description. Thanks for pointing it out.


fatal error: string_view: No such file or directory

I follow this guide:
$ git clone --depth 1 --branch quic-latest https://github.com/apache/trafficserver
$ cd trafficserver
$ autoreconf -if
$ ./configure --prefix=/PATH/TO/THE/ATS --with-openssl=/PATH/TO/THE/OPENSSL --enable-debug

That last line is exactly:
delia@delia-VirtualBox:~/trafficserver$ ./configure --prefix=/home/delia/trafficserver/build --with-openssl=/home/delia/openssl/build --enable-debug
When I make:
$ make
The output is:
make[3]: Entering directory '/home/delia/trafficserver/lib/ts'
  CXX      Arena.lo
In file included from Arena.cc:25:0:
../../lib/ts/ink_memory.h:30:23: fatal error: string_view: No such file or directory
compilation terminated.
Makefile:1382: recipe for target 'Arena.lo' failed
make[3]: *** [Arena.lo] Error 1
make[3]: Leaving directory '/home/delia/trafficserver/lib/ts'
Makefile:610: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/delia/trafficserver/lib'
Makefile:549: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/delia/trafficserver/lib'
Makefile:853: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

And I can't perform make successfully. I'm using Ubuntu 16.04 and I have installed everything recommended in readme.
Edit: gcc version is 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)

@purplehorse You will need to have gcc 7 to compile ATS now.  We moved to require C++17 and it is not fully supported until gcc 7.  There are updated instructions under "ATS v8.0" here:
https://cwiki.apache.org/confluence/display/TS/Ubuntu

solved!


patch(return types): union return type with undefined.

React query data is in union with undefined by default.
Previously, we were overriding the default data type of react query.
This causes the issue where the default return type was never marked as undefined.
It should always be possible for the default data to be undefined.
Now we union with undefined.
Exporting the default return type, closes #32
Re-did some of the typings to make it easier to change types.
Added to the example showing how to override the return type for the data, which was addressed in #29
Now, the generator passes the open API descriptions as JSDoc comments to the generated hooks and marks the methods as depreciated if marked in the spec. This closes: #18
Showing undefined listed in union on return type (as react query would do)

New JSDoc:

With deprecated indicator:

Exporting helper types for consumers if they need:

@seriouslag Thank you for the PR! Everything looks good 👍🏼


How to configure load balancing of HTTP2?

Some details
I tried to find in documentation how should we configure the Round-robin Load balancing of HTTP2. We are using IHttpForwarder but each time the connection is established all the requests are going to the one instance of the service which has multiple instances.
Since we use Kubernetes, we noticed that on the GRPC client for .NET there is the possibility to set a DNS-based Round-Robin load balancer based on Kubernetes Headless service.
Can I somehow configure this using YARP, I tried searching the documentation but I didn't find anything about it?
How many backends are in your application?

[X] 1-2
[ ] 3-5
[ ] 6-10
[ ] 10+

How do you host your application?

[X] Kubernetes
[ ] Azure App Service
[ ] Azure VMs
[ ] Other Cloud Provider (please include details below)
[ ] Other Hosting model (please include details below)

Hi @MihaZupan,
I definitely want to reuse the Http2 connection for multiple requests but in a way so that I keep a Pool of opened connections based on DNS record and then always round-robin requests between those connections.
Docs for implementation of this in GRPC client is here:
https://docs.microsoft.com/en-us/aspnet/core/grpc/loadbalancing?view=aspnetcore-6.0#dnsresolverfactory

Your best option right now is to do the DNS lookup before IHttpForwarder and put the IP directly in the destination url. That way you can manually round robin between IPs.

@Tratcher  I expected this to already be implemented behind IHttpForwarder as an option since in GRPC Dotnet library this is not a few lines of code, it's very hard logic with a lot of knowledge behind it. Also, I see that YARP users would benefit having this feature.

There is no built-in DNS round-robin in .NET after Framework. This is the issue discussing adding support for it: https://github.com/dotnet/runtime/issues/68967
Even with that, doing per-request round-robin over a list of HTTP/2 connections is not something HttpClient supports. If there is sufficient load to warrant having multiple H2 connections open, it will still use connections to their allowed maximum.
We haven't seen this as an issue since given a sufficient amount of load, different connections will eventually end up being used at approximately the same rate.

I'm not sure I'd want to build this directly into SocketsHttpHandler, but could be created as a wrapper layer around it/HttpClient:

When a URL is requested see if there is already a dns cache for that hostname. If not, or if the cache has timed out do a DNS lookup, and cache the results based on the hostname.
Pick an IP from the cache based on an algorithm - random or if being more sophisticated least loaded of 2 random results.
Modify the URL to be IP based, but use a host header to indicate the correct DNS name
Make the call via SocketsHttpHandler - let it manage the connection cache.
If the connection fails, then force a new DNS lookup and use the results of that for subsequent requests.

Dns round-robin is definitely something you can do. I have an implementation here that effectively does what you describe and plugs into ConnectCallback: https://github.com/MihaZupan/DnsRoundRobin
The only thing you mentioned it doesn't do is picking IPs based on load - it's always just round-robin.
What I think does belong inside SocketsHttpHandler is how available HTTP/2 connections are selected for each request (at least until we let the user plug in their own connection pooling).

@MihaZupan I tried your NuGet package but I getting log:
Connected to <IP_ADDRESS>:8080

Only on the first call, and after that it is keeping to use only single IP address from DNS results

Enabling DnsRoundRobin means that if we end up opening multiple connections, you would see that those go to different IPs[^1].
The second part of the problem is whether we will open multiple connections or not. By default, SocketsHttpHandler will only open one HTTP/2 connection per host (see https://github.com/microsoft/reverse-proxy/issues/1726#issuecomment-1129895775).
If you set handler.EnableMultipleHttp2Connections = true, you will see multiple connections being opened if the number of requests is too much for the single connection to handle (over 100 concurrent requests by default).
So you would see the desired behavior if:

You use DnsRoundRobin
Enable EnableMultipleHttp2Connections
Generate enough load to warrant opening multiple connections

For nr. 3, there is currently no way to force the handler to be more aggressive in opening connections if it doesn't think it needs them.
As a temporary workaround, you can create multiple handlers yourself and cycle between them to get the effect of multiple connections being opened.

I understood from your example that I need to create SockerHttpHandler per each request?

No, the handler should be created once and reused.
[^1]: If connection attempts don't happen often enough, the DnsRoundRobin implementation will clean up the cached state and the next connection will start with the first IP again. By default that's 1/min.

@MihaZupan I misunderstood it then. If I have to generate "enough load" then I don't need a DNS load balancer then.

We implemented gRPC load balancing @JamesNK might be able to share some experience here.

Triage: It is worth revisiting the BCL feature for HttpClient built-in load-balancing. This is 3rd customers / scenario -- gRPC, YARP and YARP via IHttpForwarder.
Let's keep this in YARP backlog and let's resurrect the idea in Runtime repo - @samsp-msft will file new issue.

gRPC load balancing resolves an address (e.g. an-example-dns-host) to a list of IPs (e.g. <IP_ADDRESS>, <IP_ADDRESS>, etc). Then gRPC calls are load balanced across those IP addresses based on configuration, e.g. use first healthy address, or round-robin across all healthy addresses. Because the request address is sent directly to the IP address then HttpClient has a different connection for each.
Relying on EnableMultipleHttp2Connections to create multiple connections, and then have those connections be load balanced (L4 load balancing) isn't a good solution. All requests will go to one endpoint, leaving others idle, unless you have over 100 requests in flight at once.

Hey @vasicvuk I think the problem you are having is because of k8s as described here gRPC Load Balancing on Kubernetes without Tears. We solved it by forwarding every outgoing gRPC call through an Envoy sidecar (The article suggests Linkerd though).
If I understand correctly, if we want to solve this problem using YARP (HttpClient) we would need to integrate with the k8s API?

If I understand correctly, if we want to solve this problem using YARP (HttpClient) we would need to integrate with the k8s API?
To make this work efficiently, you will need YARP to have destinations configured for the number of destinations that exist within the k8s cluster. YARP will load balance against each of the destinations that are supplied. They can be specified by IP address, not just domain name.

The obvious way to do this is with the k8s API, this is being worked on as part of #1254.
A more hacky solution would be to use DNS to query for the hosts for the cluster, which would enumerate them, but can run into issues with DNS caching as the TTL isn't exposed via the DNS APIs. You can probably rely on the passive health checks to remove dead entries pretty quickly, and use polling to determine when new entries need to be added to configuration.


spirv-as: Silently accepts and ignores --target-env=spv1.2

The option is supposed to be supplied without the equal.

Cc: @sheredom


nmonmerge and NmonVisualizer

Hello:
I have a lot of questions, but one is very important.
We use nmonmerge to join daily files. NmonVisualizer can parse the file and some graphics works like a charm. But other doesn't.
The main reason for use nmonmerge is that we get a better performance vs parse each individual daily file.
For example in the GUI: Hostname->VM before the second day the graphics are break.
The situation is the same with:
Paging Amount
Page Faults
That are derived from all VM data. Do you have knowledge about this situation?

How much worse is the performance processing the files in NMONVisualizer? It could be related to garbage collection. Try setting the heap size larger (maybe -Xmx2048M, assuming you are on a 64 bit JVM). See if that helps. Also, how often do you have nmon collecting data - for a whole day of data, every 30 seconds is probably enough.
Regardless, can you post a screenshot of what the charts look like? Do you see the same issues when parsing the files in NMONVisuzalizer, without nmonmerge first?


2nd alternative fix: allow to change or delete a relyingPartySecret on IdP

Alternative to PR: https://github.com/cloudfoundry/uaa/pull/2882, https://github.com/cloudfoundry/uaa/pull/2887
and PR: https://github.com/cloudfoundry/uaa/pull/2885
Only one call in backend, but more input on client side.
authMethod is used to make this change non-breakable.
Because before the update prevented the removal of the relyingPartySecret.
No if authMethod is not client_secret_basic or client_secret_post, then the relyingPartySecret can be overwritten with null.

sonar fixes
https://sonarcloud.io/summary/new_code?id=cloudfoundry-identity-parent&pullRequest=2896


Remove the override of GOMAXPROCS

From Go 1.5, the default setting of GOMAXPROCS is the number of
CPUs available. we might as well remove this so people can set
GOMAXPROCS to a custom value using environment variables.

https://golang.org/doc/go1.5#runtime

Signed-off-by: kun<EMAIL_ADDRESS>

Coverage remained the same at 100.0% when pulling a99c488bdc75d380f302d146a903a4d73573948b on oiooj:pr-maxprocs into fcbd21078ab7ed03682964c187452778242d3423 on jaegertracing:master.

thanks!


Add clang-tidy 16

Switch to ubuntu lunar.
Versions 11 and 12 are not available.
In this version, installing pip packages outside of a venv are disabled by default.
Fixes  #88

In this version, installing pip packages outside of a venv are disabled by default.

This worries me a little bit as people might be installing pip packages for their build. I guess we can wait to see if anyone screams, and then fix it, either by remove the magic file, adding something to the pip config file, or just creating and enabling a venv by default.

Please could you also update the readme and action.yml with the available versions?

I thought I did. Guess I forgot to push


Hope to support bidirectional link redirection and image embedding display

What is slightly disappointing 🥹is that Markline can only redirect website links now, and other links are not supported😭. I hope Markline can be more powerful💪.
Also, is there any other way for me to contact with you, such as QQ or WeChat🥹

get, I will do this feature as soon as possible.

May I ask if the latest version supports this feature

@WinHex89 1.2.2

Furthermore, can it support a small window preview when the mouse hovers over the link


optimize check snapshot range debug logging.

What have you changed?
Change to optimize check snapshot range debug statement containing region_ranges .
region_ranges contains range info in a TiKV instance and causing performance regression,  as debug logs are always evaluated since Slog does filtering after log is generated (due to concept of Drain).
What is the type of the changes?

Improvement (a change which is an improvement to an existing feature)

How is the PR tested?
Unit tests
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No
Refer to a related PR or issue link (optional)
https://github.com/tikv/tikv/issues/5122

Thanks @jadireddi
Please sign off your all commits. See https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md#signing-off-the-commit
If you have already pushed some commits before, you can use git rebase -i master --signoff to resign them off.

Thank you @siddontang for the help. Missed this message and deleted the previous commits.
Taking this change as part of https://github.com/tikv/tikv/pull/5402


ScanImage session start time display

Generate a fresh ScanImage SinglePlane SingleChannel testing pipeline and navigate to the file metadata page
The session start time field will be correctly yellow (it is found within the ScanImage header) but the value is not displayed in the datetime selector, making it seem as if it is unknown

So the reason is that the value for this is 2022-08-08T16:44:29.124000, though JavaScript date-time selectors only allow for 2022-08-08T16:44:29. What is that last trailing bit?

We can either fix this so it isn't passed from NeuroConv, truncate the misformatted string so it's valid, or throw an error indicating it isn't valid.
Is there one you'd prefer?

What is that last trailing bit?

Precision to the microsecond; these originate as Python datetime, and that's what it reads. It's often stored that way on the acquisition systems and their storage formats too, such as unix time
Ideally we wouldn't lose that precision here

Got it. I'll make sure the raw value is stored while the truncated value is displayed.
Is that sufficient as a solution? There's no way to select to the microsecond manually.

Sure thing

I could see a future user desiring more precision if it's something they have documented externally and is important for cross-file reasons, but that's an edge case that we can wait to hear a request on before adding it

There's no way to select to the microsecond manually.

Not from that selector, but you can always add an extra field next to it if need be; I agree for now that would look awkward though


persian number

Hi,
i want to know is there any way to write numbers in persian, for example show ۲ instead of 2

#45

could u please put it in your README.md?

hi
Please refer to the font that contains Persian numbers.
؟

Ok I will.

These two font are awesome
vazir
iransans

it also can be fixed with loadPersian() method which is missed on your jalali-moment library
for example, this is another library for cast Georgian date to Jalali which has that method and it also famous (more than 7K dl on last month) but because of your nice and useful date-picker and also for avoiding of several library for casting date I prefer to use your library for casting my dates.
could u add this method to your library?

Hi
yes I have removed it because it makes some problem when we want to reproduce the moment object from the string it has generated by its format method.
for example the following code doesn't work.
var a = moment();
a.loadPersian();
moment(a.format('jYYYY/jMM/jDD'), 'jYYYY/jMM/jDD');

you could use another library or this code to have persian numbers


Add option to compare Certificates

From what I understand HTTPS transfers are secured using a self signed cert. Is there any way to check if the same cert is being used by both parties? If the reciever or sender accept any random cert it seems like this could be open to a MITM attack.

I am not a security expert but before you accept the request, you can verify if the alias and hashtag (IP) match. Especially the IP address is difficult to modify (afaik).
I can add an option to allow users to compare their certs though, even if this will be rarely used

The certificate fingerprint could be put into a QR code to then be checked using the camera (similarly to what whatsapp does with contacts). If a device persists its certificate used for transfers to it, the QR code could be scanned only the first time. There are other more involved options like CAs (certificate autorities) if you want to still use temporary certs for each transfer.

before you accept the request, you can verify if the alias and hashtag (IP) match. Especially the IP address is difficult to modify (afaik).

Unfortunately, in local area networks, the connection can be easily intercepted using ARP spoofing or other techniques. If the connection is not authenticated, then the attacker can replace the users certificates with their own and decrypt or modify all the exchanged traffic, without any users noticing it. This is why TLS is usually used with a PKI.
From what I understand from the protocol documentation, certificates are already hashed and provided as a fingerprint to the others devices on the network. If this fingerprint was displayed to the users, or even better, used to deterministically derive the device alias, the app would only have to verify at the connection time that both the HTTPS server and the client provide certificates that actually match the advertised fingerprints. That way, users would only need to compare the fingerprints displayed on both device (or derived alias) to ensure the connection is secure (no risk of MITM attack).
To improve UX, you could allow users to remember devices along with their fingerprint and mark them as trusted. Thus, future connections to saved trusted devices would not need to be authenticated again.


Optimize Linux license server - RTMaps is automatically installed

RTMaps are automatically installed using user data
Download link is configurable using terraform variable

Just a few suggestions from my side:

I would call rtMaps var something like rtMaps_link
commit/PR messages could be more descriptive :-) (makes it easier to understand what was done, without going through the code)

Otherwise, LGTM, we verified it together to be working, already.

updated according to review comments


Selecting a visualization for a column should not require clicking the check box

When I choose a different visualization for a column, I see a preview of that immediately in lineup.
When I then click on the lineup view to make the menu disappear, the column reverts to the old visualization.
To confirm a visualization, I have to click a small check mark at the bottom:

Expected behavior
When I click away, the state of the preview is retain. That means, "apply" is the default action, not "cancel".
I don't think we need an undo button here. The undo button also doesn't do an expected "undo", but resets to the initial state. I can just as well cancel.
This should use proper buttons with suggested action highlight.

We unified all dialogs and added the live preview feature with PR #265. Hence, you need to confirm the changes with the tickmark at the bottom. If we want to change this behavior (again), we should asses it for all dialogs to avoid specific dialogs behaviors again.

I think this is all fine, but I do think that the default should be accept, not reject the changes. Or why should it not be like that? Can you give me an example where this is odd?

I think this is all fine, but I do think that the default should be accept, not reject the changes. Or why should it not be like that? Can you give me an example where this is odd?

Yes, makes sense. Should be just changing the default value here: https://github.com/lineupjs/lineupjs/blob/5af9d9b9c3a9f6b68b105c545cf0509267d8dbac/src/ui/dialogs/ADialog.ts#L238

And how is reset useful?
Take a histogram filter of a numeric column. Instead of fiddling around to drag the left and right handlers to it's position, you can just click on the reset button. Same goes for data mapping editor.

Re 1 - yes.
Re 2 - ok. Not sure how much better this is than just cancelling the whole operation and re-opening the dialog, especially given that it's not an "undo" as the button suggests but a "reset". Maybe in an ideal world, we would be able to do proper undo?
And if we want to keep it, we should distinguish between simple dialogs that don't need that (like view specification) and more complex ones where it might make sense.

Maybe the icon is missleading and we need a "reset" icon? Because the tooltip states clearly that it resets all values.


Title: New Game Classing Pong Game

Which pre-existing JavaScript project will you be working on?
"Pong Game" is a two-player arcade game where each player controls a paddle. The players move their paddles vertically to hit a ball back and forth. The objective is to score points by getting the ball past the opponent's paddle.
Describe your enhancement/improvement
Features

Responsive controls: Each player can move their paddle up and down using designated keys.
Ball movement: The ball moves across the screen, bouncing off the paddles and walls.
Scoring system: Players earn points when the ball passes their opponent's paddle.
Game over condition: The game ends when one player reaches a predetermined score.

Anything you need to say to the Reviewers
There is a similar game, but it is for a single player, and it is more like Block Breaker game, rather than the classic Pong game.
Add any other context or relevant screenshots about the enhancement here.
My game will look like this:

@VijaySamant4368 Thank you for providing your insight but it is not required as of now


Investigate generating module interface from .swiftinterface and .swiftdoc files

For jump to definition of symbols in stdlib or Foundation sourcekit-lsp returns a .swiftinterface file. We should look into generating a user readable swift interface from the .swiftinterface file and it's related .swiftdoc file.

It seems sourcekitd has a request which will return the generated interface for a swift module from a .swiftmodule folder. Below is a possible route to implementing jump to interface
Before we start we should setup a textDocumentProvider for scheme "swiftmodule". This will send a custom request to SK-LSP to return a module interface based on the swiftmodule path sent to it and use the response as the documents contents.

Go to definition request is sent to SK-LSP
SK-LSP generates module interface text, works out position in generated text for definition and caches the text for later use.
SK-LSP returns swiftmodule path and position inside module interface text in response
VSCode Language client has middleware which catches this response and edits the file name to use scheme "swiftmodule"
Now we are using "swiftmodule" scheme the textDocumentProvider created above will trigger and send request to SK-LSP for the module interface
Given we have cached the module interface earlier in stage 2 this should be a simple returning the contents of the cache.

That sounds like good scheme to me. 👍

This is now merged in sourcekit-lsp https://github.com/apple/sourcekit-lsp/pull/747
And vscode support is done here https://github.com/swift-server/vscode-swift/pull/538