_ Patch Compile Tests _

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

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

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

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

_ Other Tests _

-1 :x:
unit
4m 54s
root in the patch failed.

17m 23s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux a6b28896dd1b 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 / 1164531d5a

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

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

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

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/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-2279/1/testReport/

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.

:broken_heart: -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 42s
master passed

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

_ Patch Compile Tests _

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

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

+1 :green_heart:
javadoc
2m 30s
the patch passed

_ Other Tests _

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

19m 42s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux 58492a9f9555 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 / 1164531d5a

Default Java
1.8.0_232

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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-2279/1/testReport/

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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 31s
Docker mode activated.

_ Prechecks _

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

+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 38s
master passed

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

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
3m 41s
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.

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

_ Other Tests _

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

21m 33s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense refguide xml

uname
Linux 67dd6e4c2434 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 / 1164531d5a

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

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

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.

hbase-default.xml changes are included by mistake?

hbase-default.xml changes are included by mistake?

Oh, yeah, sorry.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+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
4m 12s
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.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 31s
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.

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

_ Other Tests _

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

32m 15s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense refguide xml

uname
Linux d22fdd822b40 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1164531d5a

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

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

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

modules
C: hbase-common . U: .

_ Patch Compile Tests _

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

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

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

-0 :warning:
javadoc
0m 17s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
253m 56s
root in the patch passed.

275m 24s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux bf49bf202268 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1164531d5a

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

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

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

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

_ Patch Compile Tests _

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

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

+1 :green_heart:
javadoc
2m 25s
the patch passed

_ Other Tests _

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

342m  8s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux a8f468326957 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 / 1164531d5a

Default Java
1.8.0_232

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/2/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-2279/2/testReport/

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.

We have this condition:
  private static boolean isValidHour(int hour) {
    return 0 <= hour && hour <= 23;
  }

which means 0 and 23 are inclusive only right? Am I missing something?

It only means we can set number which between 0 and 23, but the later number not be treated as offpeak hour.

The related logic shows below.

@Override
public boolean isOffPeakHour(int targetHour) {
  if (startHour <= endHour) {
    return startHour <= targetHour && targetHour < endHour;
  }
  return targetHour < endHour || startHour <= targetHour;
}

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 49s
Docker mode activated.

_ Prechecks _

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

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

_ master Compile Tests _

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

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

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

_ Patch Compile Tests _

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

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

+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  3s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

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

22m 28s

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-2279/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac refguide xml

uname
Linux 70baefdb09a6 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 / a0864ed3bc

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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 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 18s
Maven dependency ordering for branch

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

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

_ Patch Compile Tests _

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

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

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

_ Other Tests _

+1 :green_heart:
unit
207m 23s
root in the patch passed.

234m 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-2279/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux 60d7641ec5e4 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a0864ed3bc

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

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

_ Patch Compile Tests _

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

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

+1 :green_heart:
javadoc
2m 33s
the patch passed

_ Other Tests _

-1 :x:
unit
394m 48s
root in the patch failed.

416m 44s

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-2279/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit

uname
Linux 9b26b70e2d80 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 / a0864ed3bc

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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-2279/1/testReport/

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

modules
C: hbase-common . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2279/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.


pull request for e2e test at 02/02/2017 05:56:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Signal names starting with an underscore after a dash are not mapped correctly

According to the documentation of the Attribute Plugins the following definition of a signal should result in the same signal:

But instead two different signals are created:
{
  "-_foo": 1,
  "_foo": "2",
}

The same behaviour occurs with data-indicator-*. It is possible to see both behaviours with the following example:
<!DOCTYPE html>


BAU: Add callback URL for the IPV stub instance

What?
Add the callback URL of the stub RP in the IPV PaaS space.
Why?
The IPV team are running a copy of this service in our PaaS. We are trying to not have too much special config and where practical to keep it in this repo. This addition seems to fit the criteria.

Looks fine to me


Poor tracking performance given uncertainty.

❓ Issue

performance in an uncertain environment is much worse than without uncertainty.

plot
🤔 Possible solutions

uncertainty curriculum
investigate the effectiveness of different parameters.

🔧 Trail
🧰 Method: track only task performance

remove object and only control the drone.
mainly verify the feasibility of L1 attitude rate controller.

👀 Results

😃 Tracking error 10cm Robust RMA
😢 Expert performance has no difference with the robust.

🔧 Trail
🧰 Method: Uncertainty-level curriculum

start from 0.0/0.3 -> full uncertainty (1.0)

👀 Results

😢 cannot adapt at all.

🤗  Conclusion

Lower-level drone control is okay
Current setting does not utilize expert information.

🔧 Trail
🧰 Method: check rope modelling

move away from center for a little.

👀 Results

🤗  Conclusion

🔧 Trail
🧰 Method: update rope parameter

from 0.75 -> 1.05
disable hook displacement.

👀 Results

larger damping ratio: tracking error 45 cm. Unstable action still exists. video
disable hook displacement: unstable rope behavior. video
simulation slow motion

🤗  Conclusion

The sudden tightrope lead to an unstable simulation. (sudden velocity change + bouncing of the drone. )


[doc] Add example of component composition / data passing best practices

Suggested by a new user on discord.
We have https://lit.dev/docs/composition/component-composition/#passing-data-up-and-down-the-tree but it doesn't have any code examples.
We also have https://lit.dev/playground/#sample=examples/element-composition but doesn't have any data passing.
It would be good to add a playground example with data passing and link it from the doc above.

another related thread on discord: https://discord.com/channels/1012791295170859069/1166630986876997684/1166630986876997684


adding _blank to url in “Go to this webpage and view it. “

the url in “Go to this webpage and view it. “ should have a _blank so the user doesn't have to navigate back from https://webxr-workshop-lesson01b.glitch.me/ to the workshop

I'm not sure I can do that from Markdown.


Tekton Pipeline to build collection hub for development scenarios.

Is your feature request related to a problem? Please describe.
Want to demonstrate a development pipeline for the collection hub.
Describe the solution you'd like
The build collection hub pipeline should be a precursor to a GitHub webhook which could help automate the process of building collections.  The experience for Champ should be similar to Jane's in that we have discrete pipelines for Building and Testing and publishing and activating.  This epic is to move the rock forward, by working on this pipeline we can start to uncover concrete design issues we need to solve in doing collection hub development.
Of primary demonstration, we'd like to show in a few milestones, the ability for Champ to update a collection with new maintenance, primarily security-related, and that with the right testing automation the new maintenance can be rolled out automatically.

@stephenkinder If we have a Tekton pipeline to do the build, how would you expect Champ test the build of a new Collection locally or does he just do it via the pipeline?

@groeges @kilnerm @kvijai82 @tseelbach we decided to close this specific issue for now until we decide on the best way to approach moving forward to champ lifecycle.  There is a proposal to extract the appsody stack and build configuration from the collection hub and point at the appsody stack from kabanero.  If we separate concerns, it is likely we will have different build processes.


Text alignment is offset in a list

In the example I'm about to show you, if you notice the first two blue arrows the text is correctly placed. However, the 3rd blue arrow the text has shifted to the left. The same can be said for the bullets. Initially the first bullet (identified by the red arrow) is in the correct place, however, if you look at the 2nd bullet highlighted by the red arrow it has shifted to the left.
Maybe caused by spanning multi pages? Maybe caused by stopping a bullet list and writing new text not in a bullet list and then adding another bullet list?
code:
. Once the disks have been initialized, prior to activating the disks to the cluster, the following workarounds to the Red Hat Enterprise Linux OpenStack Platform 6 are required.
+
The two workarounds include:

* https://bugzilla.redhat.com/show_bug.cgi?id=1212580[Red Hat Bugzilla 1212580] which states that the OSP parameter `osd_mount_options_xfs` should not have a `-o` prefix
+
WARNING: Failure to remove the `-o` prefix from the Red Hat Enterprise Linux Installer causes the activation of disks to fail.

+
* The default amount of ports enabled for Ceph is only ten. For the Ceph OSD nodes, at least 3 TCP ports for every OSD disk per OSD server are required.

To remove the `-o` prefix, follow the steps below.

* Login to the RHEL OpenStack Installer Dashboard.
* Hover over the _Hosts_ tab and select _All hosts_.
* Click on the Ceph Host group, i.e. _Ceph Storage Node (OSD)_
* Click on the _Parameters_ tab
* Scroll to the `osd_mount_options_xfs` option and click the _override_ button
* Scroll to the `ports` option and click the _override_ button.

Output:

Closing issue as the mistake was on my part. I did not have a '+' after the bullet stating 'The default amount of ports....' hence it aligned the text different as it wasn't included in the list.


stale constraint

I got this, which looks like an internal error: “stale constraint 'Int ⤷ %350'” by running this (incorrect) val code with the tip of my test-generation branch:
//- compileAndRun expecting: success

fun factorial(_ n: Int) -> Int {
  if n < 2 { 1 } else { n * factorial(n - 1) }
}

fun assert(_ b: Bool) {
  if !b + 2 {
    let _ = fatal_error()
  }
}

public fun main() {
  let r = factorial(6)
  assert(r == 720)
}

(I get the same result after merging main into my branch)

FYI, "stale" constraints occur when the solver is given an underspecified constraint system and doesn't know how to diagnose the situation. They should only occur when we're trying to type check illegal Val code.
One way to investigate what happens is to pass --trace-inference path/to/source.val:123 (where 123 is the line at which the expression occurs). For your test case, here's what we get:
Inferring type of '!b + 2' at test.val:8:6
---
fresh:
- "%138.infix+ == [{self: remote let %138}] (%139) let -> %140"
- "Int ⤷ %139"
- "([{self: remote let Bool}] () let -> Bool)() -> %138"
- "%137 <: Bool"
- "%140 == %137"
stale:
steps:
- solve: "%140 == %137"
  actions:
  - assume: "%140 = %137"
  - success
- solve: "%137 <: Bool"
  actions:
  - assume: "%137 = Bool"
  - success
- solve: "([{self: remote let Bool}] () let -> Bool)() -> %138"
  actions:
  - schedule: "Bool == %138"
  - break
- solve: "Bool == %138"
  actions:
  - assume: "%138 = Bool"
  - success
- solve: "Int ⤷ %139"
  actions:
  - defer
- solve: "Bool.infix+ == [{self: remote let %138}] (%139) let -> %140"
  actions:
  - failure
- failure

That should be enough to help me fix the issue.

I started working on this issue (see https://github.com/val-lang/val/pull/641) but hit a roadblock.
In this specific test case, here's the constraint system that gets generated for !b + 2:

(%139)(Int) -> %140
%138.infix+ == %139 (%138 has a member infix+ that has type %139)
"([{self: remote let Bool}] () let -> Bool)() -> %138"
"%137 <: Bool"
"%140 == %137"

Note: (F)(A1, ..., An) -> R means "calling a value of type F with arguments A1, ..., An returns an instance of R" and A.m == B means "A has a member m of type B".
The system is unsat because we eventually %138.infix+ == %139 becomes Bool.infix+ == %139 and Bool doesn't have an infix + operator. Because this constraint fails, the solver never gets to know the type of %139 and so it cannot solve (%139)(Int) -> %140. As a result, it gives up and declares that constraint to be stale. At the user level, we get the following diagnostics:
test.val:8.6-12: error: stale constraint '(%139)(Int) -> Bool'
  if !b + 2 {
     ~~~~~~
test.val:8.9-10: error: type 'Bool' has no member 'infix+'
  if !b + 2 {
        ^

Handling stale constraints is a problem about which I have been thinking a long time but haven't found a good solution. The main challenge is to decide what to do with open variables without causing non-determinism.
Perhaps one solution might be to ignore stale constraints if we already issued another kind of diagnostic. That way the user isn't presented with a seemingly internal-error. This idea is based on the fact that if a system has no fresh constraint left to explore, then there's nothing we can do. So we should have gathered diagnostics already.
@dabrahams, do you have an opinion on this problem and its solution(s)?

I like your proposed solution, /provided/ that a user-level diagnostic is really the right way to handle stale constraints… but I doubt that it is. It seems to me that if we've determined that there's a type error, stale constraints are to be expected, but when there's no type error but there is a stale constraint, that's a compiler bug(?) and should trigger an assertion.

Sure, I meant to say "ignore stale constraints if (and only if) we already issued another kind of diagnostic". If we don't have another diagnostic, then it is very likely a bug, indeed.


Great idea. Would it not be possible to launch this for the flipper device?

Impossible, not the same HW.


SPO course, security review needed

The content currently in the stake pool course needs a security review on best practices when it comes to key-related things.
We should not write content like "in the testnet, you can do it like this" - no, stake pool operators should learn how to do things the right away from the beginning.
Please also see this related issue: https://github.com/cardano-foundation/developer-portal/issues/43

In trying to answer https://github.com/cardano-foundation/developer-portal/issues/43 I had to do a complete security review.  After a few days I have the results outlined & will get to work now on modifying the doc pages, and post it as a PR ASAP in the next few days.  Here are the main changes:

first, a new Air Gap Environment page in the Get Started section (not the SPO Course, since it's also needed for Devs to work with their keys).  As necessary, particular notes about working with keys & data will point back to this document.
interjections into several each of the Dev and SPO pages highlighting how to keep & work with the keys, rather than keeping them (as per the testnet oriented instructions) by default assumption on a node or Internet connected machine.
create another page (before Builder Tools, "Using keys on application servers") with some general cautions about keeping payment keys on live servers if & when necessary to use those particular tools, which have wallet passphrases & private keys in the cleartext code in several places through this section of the Dev Portal.
... This page would probably be just a stub for now because the problem of key management on servers doing automatic transaction process is more general & complicated than the problem of user key management which needs to be addressed first.  Some application oriented devs can help fill out this page later (?).
the "Integrate Cardano" section is now written as a series of testnet tutorials, so to avoid ripping all that documentation apart I would add a final "Working on the Mainnet" page in that section of mainnet equivalents if they exist (not for everything: there's no "faucet", you can't give yourself funds so no point creating an extra CLI wallet, etc.)
... to avoid duplication of effort the Mainnet page will insist that the reader complete the Testnet tutorials and then return here for an explanation of how to do these things in production.
... since "Build with transaction metadata" and "Discover Native Tokens" are also introduced with testnet commands, each of these sections will need to be concluded with their own "Working on the Mainnet" page.
The Stake Pool Course (particularly the SPO Handbook; the Lessons are all video) needs the same treatment but has some missing & redundant sections as well:
... The KES key instructions are incorrect (only appropriate to testnet) as well as insecure (missing any standard for working with these or any other private keys) and in the wrong place (instead of before generating the op cert, they're in an appendix of "Assignments" for the testnet).
... Obviously the "KES periods" information for testnet is all wrong & instructions need to be updated for mainnet.  I believe there's no point keeping a "KES testnet" page around (even if it didn't cause confusion) because the rest of the instructions for creating a pool on testnet are on video, not text pages.
... this is fixed by moving KES / VRF key instructions into the latter of 2 duplicate pages ( "Create stake pool keys" / "Creating keys and address") and making sure that page is before the instructions for KES periods & op certs.
Then there needs to be one more page ("Key Security") in the SPO Handbook, immediately before the page "Creating keys and addresses which lists all the keys mentioned later (in "Register a Stake Pool with Metadata"), indicating which keys should never leave the Air Gap, and which ones will need to be carefully installed on the block producer.
Finally the Air Gap semantics for the rest of the SPO Handbook pages should not be too hard to add, because it will apply the same transaction semantics over & over again (gather information on your node, build transaction in air gap, copy signed Tx back to your node).

This is the minimum modification that I think will do it.  It will at least update the incorrect information in the documentation so it won't be necessary for all readers to look for other resources beyond the Dev Portal to complete their stake pool.  I'll get that PR posted ASAP, but even after discussion continues there please feel free to use this as a checklist.

We should not write content like "in the testnet, you can do it like this"

@katomm while the SPO section itself is being reorganised please let me know what you think of the 2 proposed pages in https://github.com/cardano-foundation/developer-portal/pull/665 (the testnet transaction model updated for a secure workflow on mainnet nodes + an air gap building procedure).

I think that is very good and I am glad that someone is stepping up to address this. I would love  to see you as a reviewer in the developer portal in case you are interested @rphair

sure, I'm interested ... feel free to PM me in Discord  😎

Awesome. Invite sent, I also wrote you on Discord.


URLSearchParams does not exist in IE11

#74 included URLSearchParams, without a fallback for browsers (IE11) that don't support it, causing GTM to fail.

Have same issue -- app not loading at all at IE11 - error - : 'URLSearchParams' is undefined.

I've created PR with fix for this. https://github.com/mib200/vue-gtm/pull/83 @simon-tma you can check fix in my fork


Added Link to Google Speech API

Ah sorry, totally missed this PR. The link isn't quite correct; the cloud API in that link is in very limited preview, so we can't use it until we actually get access to work on it.
The current recognize_google functionality actually uses the same API that a lot of browsers use to implement Web Speech. Check out this page for details.


Great Guardian Missing Permanently

The guardian does not appear when I have guardian stones in the inventory. I uninstalled the plugin and the guardian is still missing.
I made sure the plugin had been removed from the plugins folder. Still gone. Cleared cache, reinstalled Runelite, still gone.
Runelite for Intel Mac

I didn't have membership to mess with this at the time, But I just started playing again and its working for me. You might of had a conflicting plugin. It could be something completely unrelated or more likely someone has added similar functionality to hide the guardian in a rune crafting plugin.


fix(init): fix link and npm install

Currently, ng new proj --link-cli breaks the linked angular-cli install due to https://github.com/npm/npm/issues/10343.
This PR changes our init process to link after install, which takes longer but doesn't break dependencies. It also does not use local npm and instead uses the global npm since it's what we already use for other commands.
/cc @hansl

Lgtm

This is already merged and needs no further look, but I just wanted to say, congratulations and thank you for moving away from the extra local install of in PM. That is a nice initial step toward paring back the dependency count and size.


This adds a mechanism for the unittests to be run with the TreadleBac…

This PR introduces a dependency on Treadle for backend testing.
Looking for comments on implementation and concept.
Type of change: Testing enhancement
Impact: no functional change to chisel
This could enable running unit tests to go much faster, probably about 10x.
This also helps make sure Treadle has a high fidelity to verilator.
Development Phase: implementation
Release Notes
Chisel test suite tests can now be run using Treadle (manually).
This PR presents a use case for the Issue on global settings
Release Notes
The is the first part of a facility for running the chisel tests much faster using the Treadle backend.
Verilator remains the standard backend.

It may make sense to sneak https://github.com/freechipsproject/chisel3/pull/1481 in before this (which I was intending to backport to 3.3.x). That cleans up the TesterDriver.execute method to be more stage-like and may help simplify the logic of switching backends.


Update to latest version

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Also merged in AnacondaRecipes changes

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

cc @conda-forge/core I've updated this one to get built again.  Seems we did not have run_exports on here so we may need a migration

LGTM - need @mingwandroid to approve

This isn't currently globally pinned so the bot isn't really set up to do a migration at the moment.


consul: cluster encryption key ends up in world-readable /nix/store

Consul's configuration has the field encrypt where an encryption key can be given (upstream documentation). This key can be given in configuration.nix as services.consul.extraConfig.encrypt, but this causes the key to end up in the /nix/store, as described in great detail in #24288. Following the mitigation suggested in there, there should be an option (e.g. services.consul.encryptionKeyFile) which allows to store the secret key in a not-world-readable file.

You might be better off using services.consul.extraConfigFiles. AFAICT from looking at the service module, it can be used at the same time as services.consul.extraConfig

Using extraConfigFiles is in fact the correct solution.

Here is an example using agenix.
create file
echo "{\"encrypt\": \"$(nix run nixpkgs#consul keygen)\"}" | ragenix --identity $AGE_IDENTITY_FILE --editor - --edit roles/grid/consul-gossip-encrypt.age

enable extraConfigFiles:
age.secrets."consul-gossip-encrypt.json" = {
  file = ./consul-gossip-encrypt.age;
  owner = "consul";
};

services.consul = {
  enable = true;

  extraConfigFiles = [
    config.age.secrets."consul-gossip-encrypt.json".path
  ];
};


Watcher perf regression

Running time ./tests/scripts/run_pre_post_commit_regressions_fast_dispatch.sh on my local VM (same specs as CI runner):
real    99m43.799s
user    288m37.736s
sys     59m16.770s
With watcher enabled (TT_METAL_WATCHER=30), this takes much longer. I cancelled my run after 6h or so.
We currently use watcher in the stress test pipeline and 1 iteration of this script takes ~12h right now. We used to be able to get through 10+ iterations of post-commit in a 24h span.

PR https://github.com/tenstorrent-metal/tt-metal/pull/5795 implements the fix for this. See comments there for more details.


Yes direction left

I have this code
st=>start: Start
op1=>operation: Check if item exists
cond1=>condition: Item exists?
op2=>operation: Set ID
op3=>operation: Create item and set ID
e=>end

st->op1->cond1
cond1(yes, left)->op2->e
cond1(no, right)->op3->e

I've created this Fiddle -> http://jsfiddle.net/vecyrh5u
The Fiddle is using:
http://cdnjs.cloudflare.com/ajax/libs/raphael/2.2.0/raphael-min.js
http://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.2/jquery.min.js
http://flowchart.js.org/flowchart-latest.js
For cond1 I would the like to make the Yes alternative to point left. Is that possible?

not possible with the current algorithm... https://github.com/adrai/flowchart.js/issues/15#issuecomment-37029886


Update CHANGELOG.md

Follow-up to https://github.com/apple/swift/pull/24080

Cc: @slavapestov

Oops, apparently I’m really bad at this. Thanks for fixing up my mess.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux

@jckarter @slavapestov I've resolved a conflict, and added another missing reference.

@swift-ci Please smoke test

@swift-ci Please smoke test macOS


Create hyperlink from selected text

Describe the bug
Text not chenging for hyperlink
To Reproduce
Steps to reproduce the behavior:

Switch to the WYSIWYG editor mode
Write the text "This is an example of a text link".
Select the text "link" and click on the hyperlink
Change the text to "new hyperlink" and add the url
Click OK

Expected behavior
The link text should change to "new hyperlink".
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser Mozilla Firefox
Version 127.0.2

@MooWeek I openend a PR that fixes this: #3269


Include attributes for consume-mode & media_type (if possible)

Hey, it is me again :) still messing around with your integration to see what I can do.
Today I wanted to make Lovelace react to the media_type that is playing (local:track:, youtube:video:, http:, ect.) I know it is part of media_content_id but it turned out to be a pain in the b*tt to just do a simple trim on a string within lovelace to get a proper value, so it would be very handy for those 2 people on earth who would want that without the clutter.
Having feedback in Home Assistant for the state of the consume_mode would be nice as well :)

Not quite sure what you aim to do with the media_content_id.
If you could provide an example that would make things clearer.
I'm not sure on how to add consume_mode to the entity, but it makes sense. I will dig in a bit

Not quite sure what you aim to do with the media_content_id.

It's value contains the media-type (or rather media source), I wish to see what the media-source is in lovelace. I could try to split the string in jinja or java (costum:button-card) to get unique strings that will work as conditions.
I can see that this might be not worth the effort to implement, depending on how much work it would take

I will dig in a bit

Thank you :) Are there limitations to mopidy's media-player-entity?

I found a way to extract the music-source from media_content_id, those 2 example strings show how.
As Template: state_attr('media_player.server_integration_media_player', 'media_content_id').split(':')[0]
In costum:button-card: states:['media_player.mopidy'].attributes.media_content_id.split(':')[0]
Causes a bit of clutter, but it's not too bad :D

Aha... I think I understand. You would like to have the source (eg local, spotify, tunein, tidal,...) separately
That is doable. I could add an attribute called source_extension

Something like this (line 23 in the screenshot)
mopidy_extension

Something like this

exactly!

In an effort to provide some more newer Home Assistant features, I've refactored all my code. The above can be found in my development branch for v2 called feature/compat.
If you want, you can give it a spin.

Nice! I am working with v2 since yesterday and it's working fine :) thank you!
I noticed that some services are not available, turn_on turn_off & toggle. I think because of that it is impossible to stop playback with the default media-player-card/info-panel. Personally I don't mind that since I don't use it and calling the media_player.stop-service does turn off the player but I can imagine some people might get bothered by that.

Thanks for the feedback!
I did indeed remove the turn_on and turn_off capability, as after reading a bit on the topic it means you have a real toggle to turn on or off the device, which is not the case.
Both the default media card and the mini-media-card can pause what you are playing. Stopping it from any of these cards seems not to have been implemented.
Personally I prefer not having the turn on/off functionality, as it hides too much stuff when turning it off.
I also asked feedback in my home assistant thread, so I'll see what happens...

Makes sense, I am not sure but I though Mopidy keeps sending audio when paused, this could waste some of the host machines resources, as long as you don't remove stop button I am happy :)
Did you notice my edit in the last post? Most of my implementations rely on playlists, please help :D

It must have crossed posts. I did not intentionally remove media_playlist, so I will definitely restore its functionality.
Wrt signal being sent out when not turned off, how can I reproduce this? What are the steps you took, so I can investigate a bit more?

media_playlist should be available now

fixed with #37

Yesterday I finally found time to check out your changes. I noticed you included the capability to add songs to the queue, which wasn't possible before (or I didn't see it), that's great :)
I did some testing and things work very well! There is only 2 minor things I noticed:

Sometimes when changing the song the entity doesn't report that it is still playing for a second or two (might be a mopidy thing tough)
Long response-times in general when sending commands. For example when I skip songs from within Home Assistant, sometimes the entity gets updated 2 seconds after the song started playing.

Nonetheless this update is great and much appreciated. Thank you!!!

Many thanks for testing.
The lag you are experiencing is because of the home assistant component update schedule. it is a fixed time interval (of about 10 seconds).
I believe I would be able to do it using async methods, but I need to look into this.
I am not a coder, so these things tend to take some time for me to understand how to properly code.

I feel you, I just created my first home assistant add-on with only knowing a thing or two about shell script and had to learn everything from scratch on my way (it is a mopidy-add-on with extras btw.).
It would be a nice addition to have a more responsive interface but it's not a deal-breaker if it isn't. Controlling the music in my whole flat with Home Assistant is already so cool & practical within itself :) I love it!


Way to replace an address node with an amenity

In some countries addresses reference entrances. So when an entrance is for a shop or amenity, it seems natural to not create a second node, but to replace the entrance address node with the shop, adding the address to it.
Currently one can create an amenity (tagging the address) and then delete the nearby address node, but that means the location of the address would be altered. One can also edit the address node and change its type to an amenity, but this feels weird, and possibly the address might be reset.
See this changesets and surrounding area for an example.
Related to #616: a shop may take up an entire building, and in this case tags might better go on the building contour.
Feels like it should be a checkbox somewhere — maybe between regular and extended field lists, and only for amenities.

Personally, I find this way of tagging very confusing. It also makes it easy to make errors.
IMO in most cases the amenity should not be merged with the address. Once the shop is gone, it might get deleted but the address should stay. It is not a problem to have one address multiple times, each has it's own purpose. There are edge cases, of course, but those are special and not too often.
Good cases are IMO
A:

house-area tagged as house
entrance tagged as entrance, no address
address-node inside house-shape
amenity notes inside house-shape with duplicated address

B:

house-area tagged as house
entrance tagged as entrance with address on node (disadvantage: bad visibility in editors)
amenity notes inside house-shape with duplicated address

C:

house-area tagged as house with address on it
amenity notes inside house-shape with duplicated address

D:

house-area tagged as house with address on it and amenity on it

Merging the amenity/shop with entrance and address only makes sense to me in Case D where there is one building, all is this shop, all is this address. In this case, one might as well put it on the house-area.

In Berlin we have (A) and (B) depending on where you are, sometimes (C) and (D) when one shape is only one thing.

I support making this possible, especially the case from #616. An example I recently came across a few times is adding power=substation tagging to a service building. This is a case when adding the tags to the outline seems even more natural than for a shop that takes up the entire building, but has been made even more difficult since #616 (you have to use the tag editor to manually add power=substation, then you can switch to micromapping mode to add more details).


Nested
 tags break render

Describe the bug
If my Solid template contains nested
 tags, content won't be rendered:
import { render } from "solid-js/web";

function Hello() {
  return (

This should say 'hello':

Hello

  );
}

render(() => <Hello />, document.getElementById("app")!);

In a sandbox this produces an empty render. In Solid Start it produces a console error, Uncaught The browser resolved template HTML does not match JSX input.
Your Example Website or App
https://playground.solidjs.com/anonymous/39f50ef5-3851-4d0c-b04d-ff9fce0ab86a
Steps to Reproduce the Bug or Issue
Put a
 inside another
.
Expected behavior
It renders. Or at least doesn't crash.
Screenshots or Videos
No response
Platform

OS: Linux
Browser: Brave
Version: Version 1.46.153 Chromium: 108.0.5359.128 (Official Build) (64-bit)

Additional context
Technically trying this is in violation of the HTML spec, which says paragraphs may only contain "phrasing content", but
 is flow content.
However, browsers support it regardless, and I've never seen anything barf on it so I'm surprised Solid does.
Normally I wouldn't write HTML like this. I just stumbled on it while experimenting with Solid Start and it took me a while to diagnose why my renders broke.

Solid doesn't do anything special here. Just generates the strings. What I expect is that the client is erroring out but the playground is squashing it for some reason(@modderme123). This might be worth looking into but we do a template check on startup that throws if the templates we generate don't match the browser which is the error you see in SolidStart. The reason we through is this is pretty much unrecoverable and by throwing we at least know what causes it. Whereas the errors you'd get otherwise would be really obscure.
Some more details that might help because sometimes we don't detect these issues during SSR. First browser only corrects at parsing time. Solid (and libraries like Lit) create nodes from parsing HTML strings and cloning them. This is different from VDOM libraries (and Svelte) which create them one by one. It has much better performance but your HTML needs to be well formed within a template. You can technically through inserting do something illegal and the browser won't correct it.
However for SSR where the finally output is a string the browser will correct even across template boundaries. This is much more difficult for us to account for. It can't be detected at compile time and especially with things like streaming where parts may be delivered at different times. Luckily this isn't your case and it is just a matter of the browser "fixing" stuff for us. There is an open issue in DOM Expressions tracking improvements here to detection. But it won't be fullproof I think: https://github.com/ryansolid/dom-expressions/issues/105

Ahhh, I see.
If I open DevTools and run
temp1.innerHTML = `<p><p>Hello</p></p>`

I get this even more malformed DOM:

Hello

Whereas temp1.appendChild(...) created what I expected.
If Solid is handing the browser HTML strings under the hood, then this behavior / "limitation" makes sense, and I'll close in favor of https://github.com/ryansolid/dom-expressions/issues/105
Thanks!


Remove redundant column decorator

Waiting on merge of https://github.com/Marvell-Consulting/statswales-backend/pull/13 and then I'll rebase

Looks like this was done in #13


Implement certificate store and certificate verification.

Closing in favor of https://github.com/fobnail/fobnail/pull/10


TypeError from MaxPool2DLayer

Thanks for the well-commented example! Just wanted to bring it up in case someone else got a similar error.
I'm running Lasagne==0.1.dev and Theano==0.7.0.
The error is from MaxPool2DLayer:
    Traceback (most recent call last):
      File "conv.py", line 61, in <module>
        l_pool1 = lasagne.layers.MaxPool2DLayer(l_conv1, ds=(2, 2))
    TypeError: __init__() takes at least 3 arguments (2 given)

Changing ds to pool_size as specified in lasagne.pool.MaxPool2DLayer will fix this error.

Thanks! Fixed in https://github.com/enlitic/lasagne4newbs/pull/2


Retrying setup: 'NoneType' object is not iterable

The problem
Bug issue
I recently updated easee_hass from 0.9.44 to 0.9.48 and I am now getting an error from the integrations:
"Retrying setup: 'NoneType' object is not iterable". My entities are not available anymore. I have tried to remove the integration and reinstall and re-login after the update to 0.9.48 in HACS. If I try to configure the integration by pressing "Configure" I get this error message: "Error Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble"
If I downgrade the easee_hass to version 0.9.44 it's working again. There is something going on from version 0.9.44 to 0.9.45 that makes this bug appear.
From the logs using version 0.9.45:
2023-02-26 21:19:17.826 WARNING (MainThread) [homeassistant.config_entries] Config entry<EMAIL_ADDRESS>for easee integration not ready yet: 'NoneType' object is not iterable; Retrying in background 2023-02-26 21:19:18.449 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.monthly_cost_hjem (<class 'homeassistant.components.tibber.sensor.TibberDataSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tibber%22 2023-02-26 21:19:46.825 WARNING (MainThread) [homeassistant.config_entries] Config entry<EMAIL_ADDRESS>for easee integration not ready yet: 'NoneType' object is not iterable; Retrying in background
More info about system:
arch: amd64 channel: stable docker: 20.10.22 hassos: "9.5" homeassistant core: 2023.2.5 operating_system: Home Assistant OS 9.5 supervisor: 2023.01.1
Version of Easee integration having the issue?
easee-0.9.45
Version of Home Assistant Core having the issue?
2023.2.5
Anything in the logs that might be useful for us?
No response
Additional information

Hmm, is there nothing more in the logs?
I would assume the 'NoneType' object is not iterable would generate an exception in the code and therefore a log message pinpointing the line of code that generated the error?
If you can ont find anything more useful, perhaps if you enable more debug logging for the easee component?
´´´
logger:
default: info
logs:
pyeasee: debug
custom_components.easee: debug
´´´

I'm uploading two sets of logs. One with version 0.9.44 - which is visually working properly, and one log file with version 0.9.48 - which does not work.
What I find odd is that there are more errors with tracebacks in log file from the visually working version (0.9.44).
Also uploading an image from settings meny with version 0.9.48 (not working).

not working - 0.9.48.txt
working - 0.9.44.txt

We did do some changes lately in the way we retrieve what equalizers and chargers are available at a site.
We changed it to make sure that we do not retrieve more than the chargers that are actually accessible by the logged in user in larger installations.
In your logs it looks like it fails to find the charger in your installations which is kind of an indication that it is not correctly installed somehow. I.e. Easee cloud does not consider you to be the owner of it for some reason.
With 0.9.44 you can see how it finds the charger:
2023-02-27 21:49:38.622 DEBUG (MainThread) [custom_components.easee.controller] Found site (monitored): *****
2023-02-27 21:49:38.622 DEBUG (MainThread) [custom_components.easee.controller] Found equalizer: ******
2023-02-27 21:49:38.622 DEBUG (MainThread) [custom_components.easee.controller] Found circuit: ****** Elbillader
2023-02-27 21:49:38.622 DEBUG (MainThread) [custom_components.easee.controller] Found charger: ****** Garasje
With 0.9.48 you can see how it does not find any chargers at all:
023-02-27 22:01:19.925 DEBUG (MainThread) [custom_components.easee.controller] Found site (monitored): ****
2023-02-27 22:01:19.925 DEBUG (MainThread) [custom_components.easee.controller] Found equalizer: **** Easee Equalizer Home 7302
2023-02-27 22:01:19.925 DEBUG (MainThread) [custom_components.easee.controller] Found circuit: **** Elbillader
2023-02-27 22:01:19.925 DEBUG (MainThread) [custom_components.easee.controller] Easee server failure 'NoneType' object is not iterable
2023-02-27 22:01:19.926 WARNING (MainThread) [homeassistant.config_entries] Config entry<EMAIL_ADDRESS>for easee integration not ready yet: 'NoneType' object is not iterable; Retrying in background
2023-02-27 22:01:19.928 DEBUG (MainThread) [custom_components.easee.controller] Controller deleted
I think we have seen this before and it was somehow related to an install process not being completed correctly.
Like some last step was not completed.
My memory is a bit vague on this unfortunately...
I need to look through the old issues to see if I can find something...

Perhaps we can get something useful if you go to the integration card and press the 3 dots and select download diagnostics.
You need to have the working 0.9.44 version installed for that...

We did some tweaks to handle API changes from Easee in v 0.9.45. However, there has been a couple of thousands of downloads without complaints, so there must be something in your setup that triggers these errors.
We would appreciate the unredacted logs from both versions and the diagnostic download from the last working version to further understand what is going on. Please mail me directly at<EMAIL_ADDRESS>.
And one question: Have you tried to remove the integration and install it again? Sometimes it helps!

I have sent files as instructed by @astrandb by email.
Thanks for looking further into this.

I discussed this issue with Easee, their feedback is that you should look in the Easee app and see if you can see the charger there. If do not see it there, you need to add it.
You do this by navigating to the hamburger menu / Products / Clicking the add button then the "Locate site" button at the bottom of the page. That should list out the sites you have access to and the products. You should then be able to add the charger to the app.
After that it should show up in the Easee integration again, and the integration should be able to start.
In later versions of the integration we use an API that only lists the chargers/equalizers that has been added to the app since in large installations it would otherwise potentially list tens/hundreds of chargers.
If this helps, we should add something about this in the installation instructions, so that we remember this the next time someone has similar problems.
Also, we should consider adding some more helpful error message.

Thank you guys for your dedication to this issue. The issue was solved today by @olalid suggestion. For some reason the charger was added in the web interface, but not in the app. I added the charger in to the app, and voila! 👍
Thanks. Problem solved, case closed.


AndroidX Issue

the app doesnt work when am using AndroidX... is there any one who had this issues...Plz help me out!!!!

so am I

I have the same error, someone managed to run


Configurator integration nfp dir change

Changed dir to nfp retaining the old nsf dir
Resolved import errors and API changes
Tested path of 4 APIs of generic config and 3 APIs of Fwaas without service VM

Changes looks fine.


EventDataProvider should show names when x-axis is artifact

What is it?
Right now it shows the id

Done here
https://github.com/opensource-observer/oso/pull/453


ci: Pin buildx action version to fix release workflow

This fixes the release workflow:
docker.io/***/workflow-controller:latest-linux-arm64 is a manifest list

https://github.com/argoproj/argo-workflows/actions/runs/4077164697/jobs/7026848613
Co-authored-by: Jesse Suen<EMAIL_ADDRESS>Signed-off-by: Yuan Tang<EMAIL_ADDRESS>

cc @alexec @sarabala1979

It should be possible to use the latest buildx version and overriding the --provenance flag, introduced in buildx 0.10 (~2 weeks ago) with a default of true, which as this comment explains, builds an OCI-compliant multi-platform image, and hence results in a fat manifest (docker.io/***/workflow-controller:latest-linux-arm64 is a manifest list).
This is better long-term than pinning buildx indefinitely.

Thanks. Would you like to submit a PR to upgrade it?

Will give it a go if someone doesn't beat me to it :)


There is an error for the attached database whose database name contains special characters

OS: All
Build Version: 20210729.6
Repro steps:

Create a PostgreSQL Flexible server in VS Code -> Configure firewall to connect to it -> Successfully add firewall rule for IP to the server.
Create a database whose name contains special characters, e.g. "data@" -> There is no error under the database "data@".
Right click the database -> Copy Connection string -> Attach the PostgreSQL Flexible server with the copied connection string postgres://…@....com:5432?ssl=ture.
Expand the attached PostgreSQL Flexible server -> Database "data@".
Check whether there is no error.

Expect:
There is no error under the database "data@".
Actual:
There is an error under the database "data@".

More Info:

This issue also reproduces for other characters, like below:

This issue doesn't reproduce for other characters, like below:

3.This issue also reproduces for PostgreSQL Single server.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


provide post-build hook capability prior to creating .tar.gz

There are several cases I can imagine for this.  In my case, I have a very common one.
We have the well-known issue where the bundled urllib leverages the bundled openssl which comes with no certificate file, and thus cannot verify any certificates out of the box.
With a post-build hook, we could export a cacert.pem file from the system or from another location and bundle it with the .tar.gz.  That would also require us patching some source somewhere to instruct the bundled openssl to use it. There are a few options for that part.
Obviously, we can un-tar, modify, and re-tar, but I don't want to do that.
Another common case I can imagine would be to do  pip install of some extra packages prior to bundling (I'm not sure if that can actually work or not, but I believe so.).
Alternatively, if you'd prefer to provide some first-class mechanism for solving the "lack of a bundled cacert" problem, that would help us with the immediate issue so that would be great as well.
Anyway, feedback welcome.

That's a good idea, thank you for the suggestion! I haven't had time to give some love to this project, I'll do this when I get around to working back on it


Docker Image

It'd be really great if setup_image.sh could be run by one of the RPI members, and packaged as a Docker image.  This would make it easier for other users to at least get it up and running :)

We provided a VM image in the initial release. See the [release](https://github.com/RPISEC/MBE/releases
https://github.com/RPISEC/MBE/releases/download/v1.0_release/MBE_VM.vmdk.gz

Reopened because I think this is worth exploring.

@Manouchehri: No. The only kernel stuff is for lab 10, which isn't included in this image.

Thanks, should make it easier.


Change dataSet axis dependency

Hi.
I want to render two lines on a LineChart. One dataSet dependent on leftAxis. The other dependent on rightAxis.
However, Xcode tell me "axisDependency" is a get-only property when I change the "axisDependency" property of the second dataSet.
So, how can i do this?
Thank you!

use dataSet.axisDependency = AxisDependencyRight;


[Feature] Quick Import & Export

Implement import and export feature

[x] Implement import
[x] Implement export
[x] Test on Windows
[ ] Test on MacOS
[ ] Test on Linux

Added import and export feature for Trackermon data.
Note that we have yet to test the features implemented on Unix operating systems.
While they currently work on Windows, I have not been able to implement one that works on MacOS.
The main issue behind this is believed to be a a threading issue, in which calling thread.join() causes the File Explorer used in Import and Export to crash.


Automatic Python environment activation does not select the correct environment with a multiproject workspace

Environment data

VS Code version:  1.32.1
Extension version (available under the Extensions sidebar):  1.32.1
OS and version: OSX: 10.14.3
Python version (& distribution if applicable, e.g. Anaconda): 3.7.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: XXX

Expected behaviour
Opening a terminal for a multiproject workspace should also set the python environment activation for the project selected.
Actual behaviour
When opening a terminal on a multiproject workspace, the terminal always defaults the source to the virtualenv of the first project in the workspace tree.
Ie.
Projects:
/project1/ -> venv path ..virtualenvs/project1/bin/activate
/project2/ -> venv path ..virtualenvs/project2/bin/activate
When opening a new terminal and selecting project2, the terminal behaviour is as follows
cd /project2/
source virtualenvs/project1/bin/activate

Steps to reproduce:

Add multiple python projects to workspace
Configure environment python paths for each project
Open an integrated terminal for any python project and it will use the python path for the first project in the tree

Duplicate of #3325


Reels randomly getting muted

I am scrolling through instagram reels but it randomly mutes them. I tried to find a pattern but no success yet. I scroll both with "down arrow" and "mouse scroll-wheel", idk if that has anything to do with this. Sometimes audio plays for 2-3 seconds and then mutes and sometimes fully muted from start.
I am on Chromium / Ubuntu 22.04.

I was able to reproduce it in Firefox when scrolling down fast while the Reels are loading. But it is not consistent.
Once you scroll to a new Reel I sometimes receive a mute event by Instagram. I guess since we never enable audio using the Instagram UI, Instagram thinks all videos should be muted on start. When the extension receives an audio change it assumes it comes from the user and stores these values for all upcoming videos.
There is a workaround for this already in place: After a video was started the extension ignores all volume changes for 10ms. However, this is very janky and won't work every time. I'll try to implement a better solution.

What about manually enabling audio by clicking on the Instagram reels UI audio button every time a reel loads using
document.querySelector("svg[aria-label='Audio is muted']").parentElement.click()

So, the suggestion is to unmute every time a reel loads instead of a delay. What do you say about this approach? 😶

I was avoiding finding the button via label texts, since they depend on your Instagram / Browser language. But I run some tests with this.
I'm currently trying to figure out why this only happens some times.

Spend the last two days debugging compiled React code and scrolling through an endless stream of Reels. While losing my brain capacity in the process, I discovered a way to communicate with the React components. But it is super complicated.
Instead of doing this now, I'll commit a quick workaround to release a fix soon: #34

Spend the last two days debugging compiled React code and scrolling through an endless stream of Reels. While losing my brain capacity in the process, I discovered a way to communicate with the React components. But it is super complicated.
Instead of doing this now, I'll commit a quick workaround to release a fix soon: #34

I appreciate the effort. Fr, debugging would include watching hundreds of reels cause there was no pattern lol. Also, Communicating with react components? So basically you can now have more control over Instagram or other react app cause you can communicate with other components also in the app. I will check the commit out of curiosity 🙂. We learn something new everyday after all.
Again, Thanks for the hard work. 👍


Put the PyCon UK Society constitution (back!) on the website

The document can be found here (via Wayback):
https://web.archive.org/web/20110720143450/http://www.pyconuk.org/pdfs/pyconuk_constitution.pdf
/cc @zeth @ntoll

On 06/08/15 19:12, Sarah Mount wrote:

The document can be found here (via Wayback):
https://web.archive.org/web/20110720143450/http://www.pyconuk.org/pdfs/pyconuk_constitution.pdf
/cc @zeth https://github.com/zeth @ntoll https://github.com/ntoll
—
Reply to this email directly or view it on GitHub
https://github.com/PyconUK/pyconuk.org/issues/104.

Awesomeness on stilts!
N.

OK... I've downloaded that file and put it into a branch. Just the PDF in a static location. I'll add a page about the society tomorrow.

Having now read the damn thing... it all looks eminently sensible. I'll make a proposal for changes relating to openness and anti-bus-number-1 in the appropriate way.

@snim2 / @ntoll -- now that we've got https://github.com/PyconUK/PyConUKSociety, is there anything else that needs doing here?

Since #105 has been merged I think we can safely say this Issue is resolved.


Work better with cloud sync

I'm gonna break this up a bit; expect a couple new PRs soon.

I haven't actually seen the bad that I was expecting when middlewares were in the wrong order -- maybe this isn't necessary? But it seems like it should be...


Microsoft SandBox Verification Problem

Describe the bug
Microsoft SandBox Verification Problem . It asks for verification with phone number, and giving error
What happened?
When i entered a phone number in the verification for sandbox. It gives me an error We can't continue with the signup process for the following reason:
Your phone number did not pass security checks.
MS-CorrelationId: 00000000-01cb-40ce-b1c7-93f2eb7a7b9b
Code: 40315

I
What did you expect to happen?
The phone number should be verified
How would you reproduce the bug?

Go to Microsoft Developer Account
Join the Microsoft Developer account
Select Microsoft 365 E5 instant sandbox

Did this happen via Desktop and/or Smartphone?
Desktop
Operating System
Windows 11
What browsers are you seeing the problem on?
Chrome
Version
No response
Device
No response
What is your current role?
Student Ambassador
What technical topic is this bug related to?
AI/Data Science/Machine Learning, Developer Tools
Relevant log output
No response

This was addressed at #206

Hey @AnthonyByansi  yes but that look like technical issues. Here error are different so i address with new issue.

Is there an update on this issue? It's been 5 months.

Hi, anyone able to resolve this issue? I am ready to buy the subscription but that also is not straightforward. Need to talk to sales.

Same issue i have faced, are the MS support team not able resolve 5 months old issue, then kindly put the disclaimer on the Microsoft 365 Developer Program page.

Hi @codewithrashid
thank you for bringing your concerns to our attention. we understand the frustration caused by the prolonged resolution time for the issue you've encountered with the Microsoft 365 Developer Program.
We sincerely apologize for any inconvenience this has caused. it has been addressed to our support team.

@AnthonyByansi Please look that India is no longer in list to get their number verified, like +91 country code is not listed anymore please look to it and share some comment why it is so?


Windows: Fix registry filepath and location

Signed-off-by: jhowardmsft<EMAIL_ADDRESS>@swernli
This PR is part of the proposal described in issue 10662 to port the docker daemon to Windows. It fixes the use of path vs filepath in registry.go, and also uses a different path under Windows (where /etc/ does not exist).

Rebased

@jhowardmsft What's up here? I see that you wanted to try something.

@tiborvass @LK4D4 Sorry, totally forgot about that comment. Changed the filepath.Join to a single line as per Tibors suggestion. No idea why that didn't seem to work for me the first time I tried it, but there you go! Fixed now.

Carried in #13328 to save you a rebase.


Doesn't support IE 9?

Doesn't support IE 9?

Version 2.3.4 does not support IE9 because IE9 does not fully support the Performance Web API. You can use versions prior to 2.3.4 on IE9 or, if you would like to use version 2.3.4 on IE9, you can use the following polyfill before including the jQuery Clock script in your page:
<script>
(function (global) {

var
startTime = Date.now();

if (!global.performance) {
    global.performance = {};
}

global.performance.now = function () {
    return Date.now() - startTime;
};

}(this));
</script>


[Bug]:  Label text goes missing on edit mode when reducing width on radio group widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Attached screen shot :

Steps To Reproduce

Drag and drop radio group widget
Add tool tip to the label text
Set label text in bold style
Now reduce the width and observe label text goes missing
Now deploy the app or preview the app label text displays

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Appsmith v1.9.34-SNAPSHOT

Hii @ghost @pranavkanade , I would like to work on this ticket , can you assign this to me !!

@Nikhil-Nandagopal is this available for contribution? If available our team can work on this. Please confirm.

Hii @Nikhil-Nandagopal  , I have can see that the issue is still reproduceable.

thank you.

@Naveen-Goud this is a non issue so I closed it. I don't want to invest time fixing this


typescript-axios cancellation support

Hi there,
How does cancellation work with typescript-axios? I found this:
https://github.com/acacode/swagger-typescript-api/issues/96
But this seems either outdated, or not working for the typescript-axios version.
As it requires a CancelToken, and Api does not expose a abortRequest either.
What is the way to handle cancellations?
Thanks!

Figured it out, for anyone else who needs it, just send the canceltoken with the params object:

Hello, could you please ellaborate? I want to use this library for our application. But I cannot seem to cancel a request. Could you show a visual example also? Thank you in advance.


Write a debug tool for Istio developers to troubleshooting mTLS issues

Istio provide mTLS, and sometimes it causes problems for us and customers. As an Istio developer, I want these things can be managed can tell me what is wrong. What's going on, unexpected ALPN? Failed at SAN validation? Invalid cert?
However, several things can make debugging even harder

ALPN = "istio" and PERMISSIVE mode
SNI Routing on Gateway, we use this for multi cluster and mesh expansion.
Upcoming SDS key/cert provisioning, we might not able to do xxcmd -key /etc/certs/key -cert /etc/certs/cert-chain.pem in upcoming release.

A cmd tool with these things set to simulate an Istio sidecar will be very helpful.

@PiotrSikora @wattli thoughts? Anything we can turned to borrow or reference directly?

Ideally, any issues should be visible in the logs, and we should be able to tell exactly why they are happening, without the need to run any CLI tool from the affected pod.
Note that most of the SSL errors have dedicated stats, see: https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/stats
(same ssl.* stats for clusters), so you could infer a lot from those and other stats.

I was working on a PoC tool (#11091) for this purpose but get distracted for 1.1 and other stuff later, hopefully I can get the first version out next week.
The tool basically reads and parses envoy config directly to output mTLS config on each ip/port in both listeners and clusters. I'm hoping this could help in the debugging mTLS (JWT, RBAC in the future) as the envoy config should give us the most accurate information to understand the behavior of the proxy.
There could be a lot reasons that the mTLS goes wrong. The most common reason so far is wrong configurations, like missing destination rule on client side while mTLS is enabled on server side. Sometime it could be very subtle and very hard to troubleshoot, like https://github.com/istio/istio/issues/10062

ALPN = "istio" and PERMISSIVE mode

Not sure what additional troubles are you trying to refer to?

SNI Routing on Gateway, we use this for multi cluster and mesh expansion.

I think this could cause additional troubles as it's more easier to make mistake in the networking/authentication/mTLS config.

Upcoming SDS key/cert provisioning, we might not able to do xxcmd -key /etc/certs/key -cert /etc/certs/cert-chain.pem in upcoming release.

Envoy outputs the cert information in the admin page, so I think we could leverage/enhance this page to get the same information.

I have an idea for how to expose this through istioctl.  Please comment at https://docs.google.com/document/d/1yoq1RLJbfljXfRmbaV4HAVoog1LzHgeHkbbR9wdKRW8/edit
I currently test manually with kubectl exec $(kubectl get pod --selector app=myclient --output jsonpath='{.items[0].metadata.name}') -c istio-proxy -- curl -v https://myserver.default.svc.cluster.local:80/ --resolve "myserver.default.svc.cluster.local:80:$(kubectl get endpoints myserver -o jsonpath='{.subsets[0].addresses[0].ip}')" --key /etc/certs/key.pem --cert /etc/certs/cert-chain.pem --cacert /etc/certs/root-cert.pem --insecure.
That technique doesn't work if the ALPN must be "istio".  I can set the ALPN with openssl s_client but I can't pass --insecure which seems to be needed.  If anyone has openssl tips for debugging Istio let's collaborate on a tool or blog post.

@esnible why --insecure is needed?
openssl s_client -connect httpbin:8000/ip -CAfile /etc/certs/root.cert -key /etc/certs/key.pem -cert /etc/cert/cert-chain.pem -alpn "istio"

Success one ends up with connected client, failing one ends up error. I still haven't fully studied the output format yet.
CONNECTED(00000003)
depth=1 O = cluster.local
verify return:1
depth=0
verify return:1
---
Certificate chain
 0 s:
   i:/O=cluster.local
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIDUDCCAjigAwIBAgIRANNhJEOcxWVFA9X01OE+CPIwDQYJKoZIhvcNAQELBQAw
GDEWMBQGA1UEChMNY2x1c3Rlci5sb2NhbDAeFw0xOTAzMTUwNTI0MzRaFw0xOTA2
MTMwNTI0MzRaMAAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDOrEK2
Hn8ICLt1p2ryO8NDVR52K+13t3RD/5F8npzzg56gZ6yml6efdncgqlZn9bnp6G6i
O4d8uxftIJ6ptLQBZAroZDNU61ofqTr2/H7bj/n56UJ9w1UyJsI69dBrIxbFDe48
xdMrRz67864/yZz46epL5Y7kFB9B2Z1ixuTJlA5F7lv/5zHdS9XtE+1lhohvjFig
G7gvxNSYb/qPt2Wax5j93DJPvuJjftH7BKuKg9EqwOXKfYc1osj2aZ7V7AZ5K8Hq
9M3W3CK1FPmEJTsunbmazeOhkZKsYBRIQPZEKz7slrBGWdRgebo9gh0fH64w6PAa
Q9fQhqgcT328ukyrAgMBAAGjgawwgakwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQW
MBQGCCsGAQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAAMGoGA1UdEQRjMGGG
RXNwaWZmZTovL2NsdXN0ZXIubG9jYWwvbnMvaXN0aW8tc3lzdGVtL3NhL2lzdGlv
LXBpbG90LXNlcnZpY2UtYWNjb3VudIIYaXN0aW8tcGlsb3QuaXN0aW8tc3lzdGVt
MA0GCSqGSIb3DQEBCwUAA4IBAQCnDrofH60wQ+SSygNx0IfOxTyocx9aE9dakEfm
VfTdMjbZ5j7sjvxVF0BT3bPHGFTAHlLSqmmeQf7S2g1iQQlCcNxEcyqPVCaUGQNV
PiJLFHoqAYry6wP/2a3+vbCIf0NKheKCUcQXn4rcJIK3iX9vwod1CRhsmGHjFdxH
6bEaH86HrDKTZ6ns1Wd9oCEwdVr+O+IWLjcCwk58R7xMWaAj8dcosqxez0/CdgMg
ONdb9kQ57YwgTm2XDdXxWrtRPrRm7YJpQunjLhuFF6q8JWn+eVtP/AJQIoUvt2vY
M2TpY9r7LlVBWv68+Hkll+FFc73RGkoUDflW6SDhteMiRI47
-----END CERTIFICATE-----
subject=
issuer=/O=cluster.local
---
Acceptable client certificate CA names
/O=cluster.local
Client Certificate Types: RSA sign, ECDSA sign
Requested Signature Algorithms: ECDSA+SHA256:0x04+0x08:RSA+SHA256:ECDSA+SHA384:0x05+0x08:RSA+SHA384:0x06+0x08:RSA+SHA512:RSA+SHA1
Shared Requested Signature Algorithms: ECDSA+SHA256:RSA+SHA256:ECDSA+SHA384:RSA+SHA384:RSA+SHA512:RSA+SHA1
Peer signing digest: SHA256
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3150 bytes and written 2266 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: 2862C0544E4926234DD702F8B6E48324B4F0C9DC3F4BF169FDEE00DBE28A456D
    Session-ID-ctx:
    Master-Key: CC6E96BAEC68C1E4D6AB02EA16D7D758E6DA15C543CFC4AA1967657B03C320D3B86304E8CB68A470AB2C20AF52189D87
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 7200 (seconds)

@incfly I suspect -insecure is needed because Istio checks only part of the certificate.
To reproduce, install Bookinfo.  Then:
MYCLIENT=productpage
MYSERVER=details
HPATH=details/0
PORT=9080
kubectl exec $(kubectl get pod --selector app=$MYCLIENT --output jsonpath='{.items[0].metadata.name}') -c istio-proxy -- curl -v https://$MYSERVER.default.svc.cluster.local:$PORT/$HPATH --resolve "$MYSERVER.default.svc.cluster.local:$PORT:$(kubectl get endpoints $MYSERVER -o jsonpath='{.subsets[0].addresses[0].ip}')" --key /etc/certs/key.pem --cert /etc/certs/cert-chain.pem --cacert /etc/certs/root-cert.pem --insecure

The output will be as expected.  But leave off --insecure, and you will see
curl: (51) SSL: certificate subject name () does not match target host name 'details.default.svc.cluster.local'
command terminated with exit code 51

@incfly Where is the proposal for SDS key/cert provisioning?
I looked at the source code for curl a few months ago.  It would be a one line change to add the Istio ALPN.  I don't want to deal with getting a custom curl to our customers however.
OpenSSL lets us supply the ALPN but I haven't figured out how to run it if the hostname doesn't match the subject name.  Does anyone know if that is possible?  @elevran
Would it be possible to have istio as a possible ALPN but not the only one?  Always ["istio", "h2"] instead of just ["istio"] in the Envoy configuration?  That would make my life much easier....

@esnible The more severe trouble for the debugging is that you don't have access to the cert/key on the file system anymore once SDS key/cert provisioning is enabled, they will only exist in Envoy's memory. This is considered one of the key benefits of SDS key/cert provisioning, the other benefit is Envoy doesn't need to restart for any cert rotation. cc @wattli

@yangminzhu Perhaps we don't need the key on the filesystem?  I want to automate what I do now using curl.  (See https://docs.google.com/document/d/1yoq1RLJbfljXfRmbaV4HAVoog1LzHgeHkbbR9wdKRW8/edit ).  Perhaps instead of --key /etc/certs/key.pem we can do something like --key <(kubectl get secret istio.default -o jsonpath='{.data.key\.pem}' | base64 --decode)?

@esnible
In case of mTLS, you will need the client cert in order to issue a request to the server, and this client cert is not on the file system or k8s secret. So you cannot use kubectl get secret ... to get it.

I would suggest us to add a util to get key cert for workload by following the same CSR flow as Envoy does via kubectl exec into workload pod.

@incfly do you mean reuse SDS against the local nodeagent from the Envoy pod or a CSR to Citadel?

@JimmyCYJ Is this covered in our code mauve effort?

Closing because istioctl x describe now performs this function.


Mouse tooltip item value color does not match ground item value color

Describe the bug
When hovering over an item on the ground, the color of the mouse tooltip name of the item does not match the color of the text of the ground item. This only seems to happen on untradable items from my small amount of testing with feathers and cannonballs, though it is a small sample size.
Screenshots

My ground item settings for reference:

Environment:

OS: Windows 10
RuneLite version: <IP_ADDRESS>
Launcher version: 1.6.0

Based on my observation I believe there are two underlying problems:

When the GE price is 0 (untradeable items) the GroundItemPlugin used the store price, not the HA price (which is the store price multiplied by 0.6). So the 1 brimstone key has a storeprice of 80.000, which explains the blue color for that medium value
For non-stackable untradeable items the relevant code didn't handle the quantities correctly, e.g. dropping two raw lava eels returned a quantity of 1 and a wrong price, which lead to the wrong color

The pull request https://github.com/runelite/runelite/pull/11304/ fixes both issues

There is still some issue with stackable items:
... I need to analyze this.

Now it works for stackable and non-stackable, tradeable and non-tradeable items. Also the default item color is now used when items' prices don't match any value threshold. I'll continue using this version and see if anything acts up, but the last few hours looked fine to me.


Cannot create property 'isRootInsert' on string with slots syntax.

Hi, I want to implement dynamic component which generates template as per passed Props using component interpolation approach.
https://kazupon.github.io/vue-i18n/guide/interpolation.html#slots-syntax-usage
The issue I am having is that if you load the example page directly (webpage.com/example), it works, however if you navigate to it from example.com or any other page it triggers errors:

TypeError: Cannot create property 'isRootInsert' on string
[Vue warn]: Error in nextTick: "TypeError: Cannot create property 'isRootInsert' on string

Been trying to use approach described in this issue #945 , but no luck.
Error:

Working example when page is loaded directly or reloaded:

Package.json:

Module config:

Component and translation JSON object:

Some additional info:

Did not work with functional components, nor without property decorators. In all cases same errors.

Been stuck on this for a day now, without any idea what might be causing this behaviour.  Any help will be appreciated and thanks for looking into this! :)

I'm not really sure what this is about but it's not strictly related to this module. Maybe a weird interaction between vue-i18n and Vue.
Maybe try to wrap the i18n element in an extra node?
Or google the error and see if you can figure out the problem from there. I see that there are some existing problems like that but generally should be fixed in recent Vue versions so maybe your project is pulling older versions somehow.
Won't be able to help more without a reproduction repo.

I'm not really sure what this is about but it's not strictly related to this module. Maybe a weird interaction between vue-i18n and Vue.
Maybe try to wrap the i18n element in an extra node?
Or google the error and see if you can figure out the problem from there. I see that there are some existing problems like that but generally should be fixed in recent Vue versions so maybe your project is pulling older versions somehow.
Won't be able to help more without a reproduction repo.

@rchl thanks for quick answer.
Wrapping i18n element with another node still causes an error.

@rchl thanks for quick answer.
Wrapping i18n element with another node still causes an error.

Have the same issue after migrating codebase to typescript (nuxt-property-decorator).
I guess it can be related to named slots and functional components  + TS: https://github.com/vuejs/vue/issues/4589
Or this one: https://github.com/vuejs/vue/issues/9372

@Gmiliuta I understood what the problem is.
When you navigate to another page, event routeChanged is fired, which under normal circumstances is fired from the root component.

If it is called from another component, it may indicate that this component is without a decorator @Component.
@rchl So, it seems the issue has been resolved


Upgrade Maven wrapper

This PR is to fix issue #404
Files are created by following command, leaving Maven version (3.5.4) unchanged for minimum unexpected side-effects.
mvn -N io.takari:maven:wrapper -Dmaven=3.5.4

After that, the wrapper works well with spaces in quotes.
[sechs@Yans-MBP:~/Work/spring-petclinic] (master)
$> ./mvnw dependency:tree -DoutputFile="/tmp/my folder/tree.log"
[INFO] Scanning for projects...
[INFO]
[INFO] ------------< org.springframework.samples:spring-petclinic >------------
[INFO] Building petclinic 2.1.0.BUILD-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ spring-petclinic ---
[INFO] Wrote dependency tree to: /tmp/my folder/tree.log
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.869 s
[INFO] Finished at: 2019-03-28T10:50:47+08:00
[INFO] ------------------------------------------------------------------------

@Eskibear thank you very much for making your first contribution to Spring Petclinic. This has been merged to master.


baseURL is not working

Hi guys! I am currently working with strapi v4 and we have implemented this CKEditor which has great features. However I am facing a problem with this baseURL configuration which is not working properly IMO. Or I am doing something wrong.
So I provided changes according to your documentation:

My config/api.js
module.exports = ({ env }) => ({
  baseURL: env('PUBLIC_URL', 'http://localhost:1337'),
});

The result:

So after adding adding baseURL to config/api.js nothing is happening and sources for uploaded images inside text editor are not prefixed with provided URL.
Is there any possible solution for that issue?

@ajankowy035 did you find a fix for this? Im also having issues

no, I didn't find a fix for that. We found another way - using nginx on frontend - we created a redirection to the strapi app when it's calling /uploads

Does anyone know the solution to this?

@hypong  Maybe you could try to transform the response with controller in strapi? controllers

If anyone is wondering, adding a "url" property to the module under server.js (./config/server.js) in the Strapi folder did the trick, here is what the config looks like:
module.exports = ({ env }) => ({
  host: env("HOST", "<IP_ADDRESS>"),
  port: env.int("PORT", 1337),
  url: env("PUBLIC_URL", "http://localhost:1337"), // <- ADDING THIS LINE TO THE CONFIG
  app: {
    keys: env.array("APP_KEYS"),
  },
});

I tried both methods, and adding the baseURL property to the .config/api.js file did nothing. You could use process.env in a ternary condition if you want to have the url adjusted based on the server environment.


[prim_prince] Annotate some arrays to avoid UNOPTFLAT warnings

Verilator's block scheduler isn't particularly clever, and it needs a
bit of hand-holding when you have an array which updates like this:
foo[0] = 123;
foo[1] = f(foo[0]);

Without the help, it sees foo depending on itself, which triggers an
UNOPTFLAT warning (and slow simulation!)

i don't have any particular problems with this change..but i wish there were a way to do this more globally (assuming there isn't a huge performance impact).

I think the problem is that the simulator needs to be super clever to work this out in general, but a human editor can easily give it helpful hints. I'd be very pleased to find out I was wrong!

Not for this PR, but I wonder if making data_state an unpacked array would help.

I don't think making it unpacked helps. For example, in prim_prince.sv, I tried this definition:
  logic [DataWidth-1:0] data_state [NumRoundsHalf*2+1:0];

(I think the accesses end up the same) and still got
%Warning-UNOPTFLAT: ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:116:25: Signal unoptimizable: Feedback to clock or circular logic: 'rom_ctrl.u_rom.u_prince.data_state'
  116 |   logic [DataWidth-1:0] data_state [NumRoundsHalf*2+1:0];
      |                         ^~~~~~~~~~
                    ... Use "/* verilator lint_off UNOPTFLAT */" and lint_on around source to disable this message.
                    ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:116:25:      Example path: rom_ctrl.u_rom.u_prince.data_state
                    ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:129:7:      Example path: ALWAYS
                    ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:127:27:      Example path: rom_ctrl.u_rom.u_prince.gen_fwd_pass[1].data_state_round
                    ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:150:29:      Example path: ASSIGNW
                    ../src/lowrisc_prim_lw_cipher_0/rtl/prim_prince.sv:116:25:      Example path: rom_ctrl.u_rom.u_prince.data_state

Thanks for trying @rswarbrick!


[svg] Migrate Security icons from meshery-cloud

SVG Icons

[ ] Key
[ ] Keychain
[ ] Security
[ ] Session
[ ] Token

Contributor Guide

🎨 Wireframes and designs for Layer5 site in Figma (open invite)

A preview of some of the icons I am working on from Meshery Cloud


Supporting SSL Endpoint certificates?

Hi @dmathieu. Would you be open to supporting Heroku's legacy SSL Endpoint certificates?
The Heroku API has endpoints for this purpose, and I'm happy to at least attempt a pull request (though my Go skills are almost non-existent). I have one app that's still on the old endpoint, and while I'd love to migrate it, it actually is the main API for a Heroku Add-on, and thus I have customers using old versions of Ruby that annoyingly don't play nicely with the SNI approach.
Just pondering whether it's worth my effort to understand enough of the Go code to make a contribution, and whether it would be merged (if I have to maintain a fork myself, it's probably a better use of my time to just pay the yearly fee for a non-letsencrypt certificate).

Nope. This gem is not receiving any changes anymore.
Also, why would you want to use the SSL endpoint certificates? They cost $20/month, and will be entirely removed at some point.
Also, https://blog.heroku.com/announcing-automated-certificate-management


Adding username to intervals/annotation/badchannels

I see that there's now a username field in the CSV file that's saved, but where would that be specified? Perhaps just a dialog box when asking to save to an external file?
Would it be simple to add a user to the badchannels selection as well?

@jrliu95 when you create a new interval type, there is a field for 'user name'. I realize now that there's no such option if the user just goes directly adding the already existing 'invalid' type. There are some ways to do it, let me know which one you prefer:
1- For every interval added, it prompts a dialog to enter user_name. This sounds counter-productive, if you're doing it several times
2- User_name is created when interval type is created, like it is now. This is problematic because it can't be changed later, or we would create an option for 'editing' interval types, which sounds like a lot of branching options for the user and, again, counter-productive
3- We create a session option, with user_name argument initially, on which every alteration will be associated with. The session name would be displayed in the window title, e.g. "ecogVIS - EC122_B22 - session: Luiz" and there would be a button to change it. Every object added would carry the session info with it.
'Intervals' and 'Annotations' are objects, which makes it intuitive to carry a value such as user_name, or session, or anything similar. 'bad_channels' is a boolean array corresponding to all the channels in the electrodes group, it is an electrode property. This would mean associating an user_name to each electrode, which might end up being confusing. What do you think? Is it an important feature for you?

The 3rd option sounds perfect. This way it's not too much extra work for the user.

The annotations/intervals are much more user specific so that's why it'd be good to have the user information with those.

session is now in place, annotations and intervals added are now associated with the current session. Users can change sessions name ate File-> session


Update build.gradle

Fixes # .
updated assertj-core version to 3.5.1
Did you remember to?

[ ] Add test case(s)
[ ] Update CHANGES.txt

updated version for assertj-core

@pandareen - Looks like the newer version of assertj core (3.5.1) requires JDK1.8 [see here ]  . TestNG is yet to move to JDK8 [ see here ]

Closing per @krmahadevan's observation.

Thank you


dev -> master

Web app was deployed to IPFS:

Private Gateway: ipfs.kira.network/ipfs/bafybeibm3uvpkdpo7usi7dpfoflfwkl6tgzszjg7rdegro6sw4yclwvtge
Public Gateway: ipfs.io/ipfs/bafybeibm3uvpkdpo7usi7dpfoflfwkl6tgzszjg7rdegro6sw4yclwvtge

This PR is obsolete, dev branch is ahead of your branch.