ncmpc: 0.30 -> 0.31

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ncmpc/versions.
meta.description for ncmpc is: '"Curses-based interface for MPD (music player daemon)"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31/bin/ncmpc passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.31 with grep in /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31
directory tree listing: https://gist.github.com/c971940495dba0283f1c77bb9279bcf1
du listing: https://gist.github.com/adc5f5277b78091961551bc267b48a5e

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/7c4b2196f85b6d2ec807759d5a67db74d4868950.tar.gz -p ncmpc
ls -la /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31

cc @fpletz for testing.

Success on x86_64-linux (full log)
Attempted: ncmpc
Partial log (click to expand)
Running custom install script '/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/bin/python3.6m /nix/store/0wrv6cips8sfzk04ca67w6vlsgy4lb3z-meson-0.46.1/bin/meson --internal gettext install --subdir=po --localedir=share/locale --pkgname=ncmpc'
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31
shrinking /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31/bin/ncmpc
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31/bin
patching script interpreter paths in /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31
checking for references to /build in /nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31...
/nix/store/mf57js2n48rjzdmwkin3qpr1w4m0lhy1-ncmpc-0.31


How to remove PWA ?

Hello,
I am using Vercel to deploy my app. I previously added this plugin but I can't remove it since the changes do not apply on the client-side. What I mean is, when I remove this plugin the client-side website doesn't update at all.
Please let me know how can I resolve this issue.
Thanks!

Once the service worker is registered on client side the user should remove it or you can include a script in your index.html, then once removed your new version will not register and use the service worker.
You can check the service worker is not registered on your app openningyour app in private window.
For more info, check https://medium.com/@nekrtemplar/self-destroying-serviceworker-73d62921d717
navigator.serviceWorker.getRegistrations().then(function(registrations) {
  for(let registration of registrations) {
    registration.unregister();
  }
});

@userquin Thanks! It worked.


PHOENIX-6125 : Disable region split for SYSTEM.TASK

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

+1 :green_heart:
javac
0m 55s
the patch passed

-1 :x:
checkstyle
1m 18s
phoenix-core: The patch generated 11 new + 2241 unchanged - 1 fixed = 2252 total (was 2242)

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

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

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

_ Other Tests _

-1 :x:
unit
96m 19s
phoenix-core in the patch failed.

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

183m 28s

Reason
Tests

Failed junit tests
phoenix.end2end.SystemTablesCreationOnConnectionIT

Subsystem
Report/Notes

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

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / fe7c46c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

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

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

modules
C: phoenix-core U: phoenix-core

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

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

-1 :x:
mvninstall
32m 50s
root in the patch failed.

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

+1 :green_heart:
javac
0m 52s
the patch passed

-1 :x:
checkstyle
1m 23s
phoenix-core: The patch generated 1 new + 2241 unchanged - 1 fixed = 2242 total (was 2242)

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

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

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

_ Other Tests _

-1 :x:
unit
96m 33s
phoenix-core in the patch failed.

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

182m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 628fa0d

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/testReport/

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

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/3/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

Added some comments. Also, the test failure seems related since it is complaining about TableNotFoundException for SYSTEM.TASK

Thanks @ChinmaySKulkarni . Addressed concerns and updated PR accordingly. Test failure is also taken care of.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

-1 :x:
mvninstall
36m 22s
root in master failed.

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

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

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

+0 :ok:
spotbugs
2m 55s
phoenix-core in master has 973 extant spotbugs warnings.

_ Patch Compile Tests _

-1 :x:
mvninstall
32m 23s
root in the patch failed.

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

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

-1 :x:
checkstyle
1m 37s
phoenix-core: The patch generated 34 new + 2543 unchanged - 33 fixed = 2577 total (was 2576)

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

-1 :x:
whitespace
0m  0s
The patch 1 line(s) with tabs.

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

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

_ Other Tests _

-1 :x:
unit
94m 19s
phoenix-core in the patch failed.

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

179m  1s

Subsystem
Report/Notes

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

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 92687e421e34 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/phoenix-personality.sh

git revision
master / 628fa0d

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/whitespace-eol.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/whitespace-tabs.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/4/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

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

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

modules
C: phoenix-core U: phoenix-core

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

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

-1 :x:
mvninstall
36m  0s
root in master failed.

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

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

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

+0 :ok:
spotbugs
2m 49s
phoenix-core in master has 973 extant spotbugs warnings.

_ Patch Compile Tests _

-1 :x:
mvninstall
32m 35s
root in the patch failed.

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

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

-1 :x:
checkstyle
1m 34s
phoenix-core: The patch generated 34 new + 2542 unchanged - 33 fixed = 2576 total (was 2575)

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

-1 :x:
whitespace
0m  0s
The patch 1 line(s) with tabs.

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

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

_ Other Tests _

-1 :x:
unit
95m  6s
phoenix-core in the patch failed.

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

179m 37s

Subsystem
Report/Notes

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

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 628fa0d

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/whitespace-eol.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/whitespace-tabs.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/6/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

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

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

modules
C: phoenix-core U: phoenix-core

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

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

-1 :x:
mvninstall
3m 40s
root in master failed.

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

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

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

+0 :ok:
spotbugs
2m 51s
phoenix-core in master has 973 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

+1 :green_heart:
javac
0m 51s
the patch passed

-1 :x:
checkstyle
1m 50s
phoenix-core: The patch generated 41 new + 3120 unchanged - 35 fixed = 3161 total (was 3155)

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

-1 :x:
whitespace
0m  0s
The patch 1 line(s) with tabs.

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

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

_ Other Tests _

-1 :x:
unit
96m 58s
phoenix-core in the patch failed.

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

117m 58s

Subsystem
Report/Notes

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

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / f0e5f05

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/whitespace-eol.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/whitespace-tabs.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/7/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

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

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

modules
C: phoenix-core U: phoenix-core

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

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
36m 16s
master passed

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

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

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

+0 :ok:
spotbugs
2m 54s
phoenix-core in master has 973 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

+1 :green_heart:
javac
0m 52s
the patch passed

-1 :x:
checkstyle
1m 51s
phoenix-core: The patch generated 10 new + 3151 unchanged - 4 fixed = 3161 total (was 3155)

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

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

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

_ Other Tests _

-1 :x:
unit
95m 18s
phoenix-core in the patch failed.

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

180m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/9/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/923

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 5b58d9b

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/9/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/9/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/9/testReport/

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

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-923/9/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

@virajjasani the master patch doesn't apply cleanly to 4.x so please put up a patch/PR for 4.x, thanks

Done, uploaded patch on Jira. Thanks for the review @ChinmaySKulkarni


feat(branch): Moving the function to be exported and used in other pl…

Allowing branch tracking to work on the promotions block and also enabling the function to be imported and called anywhere if necessary.
Test URL:
https://meta_promotion_fix--express-website--webistry-development.hlx3.page/express/learn/express-your-brand?cgen=C4SZ2R6X&mv=other#watch-now

I believe done!


Need an example of metric calculation on custom video pair

It would be great to have a sample on how to calculate metric on custom video pair. I tried to adopt it from test sample but got negative values. What is the expected range for metric?

Hi Kepnu4,
At present, our method does not have a defined range for the metric. In our experiments, we compared the rank of our scores with the rank of human scores, resulting in the possibility of negative scores.
I plan to fine-tune a version that constrains the score range to [0, 1] within the next few days.
Thank you for your understanding.
Best regards,
Qiqi

Hi,
I am also getting negative values even for reasonably good video pairs, which strikes me as weird because the results in the LDM-VFI paper are all positive and also close to 100. Do you happen to have any update about the fine-tuned version you mentioned?
Thanks in advance!

Hi,
Sorry. I forgot this issue. @basilevh No, we have not updated our metrics yet. For the LDM-VFI, you might need to contact the authors of LDM-VFI for the details. To evaluate their method, they need to repeatedly interpolate their results and other operations.
Thank you!

Hi @hqqxyy, I am consistently observing that the better the quality of my predicted video (including that of baselines), the closer the result of VFIPS is to -100. It is almost always negative (between 0 and -100). Would you mind confirming that this is expected? Thanks again.

@basilevh  Yes. Our metric should get lower scores when the predicted video has a higher perceptual quality.


Lucky Number | Java

Creating lucky number program in Java

Please assign me to do this,I made a new issue


Vendor in requirementslib==2.0.0 & drop pip-shims & revert sysconfig patch w/ safer setuptools usage

Vendor in requirementslib==2.0.0 and drop pip-shims entirely.
Some systems have patched sysconfig differently, and from this discussion (https://github.com/pypa/setuptools/discussions/3544) it would appear that importing setuptools packages is problematic

We still need to fix the merge conflicts @matteius

@oz123 I had merged main into this branch and resolved them, squash and merge did not show any conflicts so I went ahead and merged, thanks for your review!


Duration checks in consumer

Description
Duration checks in consumer
Type of change

New feature (non-breaking change which adds functionality)

Testing steps
N/A

Codecov Report

Merging #172 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #172   +/-   ##
======================================
  Coverage    2.11%   2.11%
======================================
  Files          12      12
  Lines         520     520
======================================
  Hits           11      11
  Misses        509     509

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 186b4c5...ac18668. Read the comment docs.


Stoped working win10 update ver 2004

Wonderful app, don't want to be without it.
After windows update to version 2004 it said it was not compatible and would not start up anymore, so I reset the app under the apps and features and it then disappeared from installed app list.
I can no longer install it from the win store, the install fails around 90%. It is almost of there is some bits off the app left somewhere on the machine that it can not replace. I Dont know where to clean or check.
Works fine on my on my other 4 machines after update to latest version 2004.

Hi, try to find it with this link: https://www.microsoft.com/en-us/store/p/powerplanswitcher/9nblggh556l3
Or try do find it in store with the name altogether: powerplanswitcher
I nave updated to Win10 to 2004 and here is working,
Hope I can help.
Regards.

Thanks for responding.
I have noticed that the nvidia drivers on one of my other pc's complained that powerplanswitcher is preventing it from upgrading its drivers and had to be stopped first.
I then went back to this problem pc which now did not have powerplan on and upgraded the nvidia drivers which could also not upgrade, so I uninstalled the Nvidia Gforce expierience completely and downloaded the latest version and installed it, it needed to reboot to uninstall because uninstall failed.
After new version was installed the install of the powerplanswitcher automatically succeeded because it was still stuck in the store as trying to install and everything is working again.
I have seen this before on all my nvidia pc's that it requests to stop the powerplan when upgrading so they must share some resources, but i would not normally relate the powerplan to video card drivers and I could not remember this because I only upgrade roughly once a year.
Thanks it is working fine again.


How to handle unreachable code?

mkdocstrings version: [0.10.3]

Hi ,
I would like do to document a project that makes heavy use of external libraries where I don't have access to the sources.  Does mkdocstrings offer something similar to mocks in sphinxs/autodoc
autodoc_mock_imports = ["django","td"]
Thanks in advance

Hi! There is no mocking ability in mkdocstrings, no, but I agree this can be extremely useful. I'll transform this issue into a feature request :slightly_smiling_face:
At the same time, if you have any suggestion on how this could be implemented, or links to code for inspiration, please share!


Shitpost

Interior designer ML-demo

Sketch the toilet

data source -> scrape yung website

magkakaroon ng iba't ibang angles

Where does your toilet fall in this multivariate

diet of average person


Change mimxrt1060_evk and mimxrt1050_evk to use variants for qspi/hyperflash instead of revisions

Change mimxrt1060_evk and mimxrt1050_evk to use variants for qspi/hyperflash instead of revisions
Also for the mimxrt1060_evk, change evkb to a revision.

@nordicjm let's discuss if we should adjust the intention with initial design of HWMv2 variants that requires the base board target to always be valid.

Conclusion from offline discussion is to allow the use of variants (for example: mimxrt1050_evk/mimxrt1052/qspi) where the baseline mimxrt1050_evk/mimxrt1052 cannot build. This requires an extension to current hardware model.
Untilsuch extension is ready then a manual check in CMake and proper error message must be raised by the board if building for an invalid board target.
@decsny please add a check that ensures that building for mimxrt1050_evk/mimxrt1052 fails at the CMake stage with a proper error, and include known valid board targets for the user to choose from.
Alternatively ensure that mimxrt1050_evk/mimxrt1052 builds and runs succecfully.

@tejlmand I've updated the PR to add that check, but what I think would be optimal in this case is actually to have a default variant, but it looks like that's not possible. The reason is because for example on the rt1060, the qspi is set up out of box, and to switch to hyperflash requires soldering a board rework

found it: https://github.com/zephyrproject-rtos/zephyr/pull/69264#issuecomment-1959508476
seems like that PR also contained a proposal to use variants :laughing:

but what I think would be optimal in this case is actually to have a default variant, but it looks like that's not possible.

not atm, no.

update: fixed rt1050 board overlay names

rebased and added documentation of board target strings

@nordicjm there is some tinycrypt related ci issues blocking this PR but in the meantime can you check if your block was addressed

This change should be documented in the migration guide.

I don't think that's what the migration guide is for. AFAIK the migration guide is supposed to be a guide for users to know how to migrate their apps to newer versions of zephyr, and i don't see how changing the board target string for an in tree sample EVK affects that. @kartben is this something that should go in the migration guide or not

@decsny hey you can't just drop board names without notice, they go through deprecation process. Please add entries to boards/deprecated.cmake that associate what used to be the default variant to the new corresponding target name. If you could submit as a hotfix for test currently failing in mail that's be great :) https://github.com/zephyrproject-rtos/zephyr/actions/runs/12439056759/job/34732166695#step:11:1231
This is a fix that needs to be done anyway, and will be quicker/simpler to deploy than updating https://github.com/zephyrproject-rtos/mcuboot/blob/f5454f16358225f69ff729301c8e56d8a580f81a/boot/zephyr/sample.yaml#L4 and pulling through a manifest update on Zephyr side. Thanks!

@decsny hey you can't just drop board names without notice, they go through deprecation process. Please add entries to boards/deprecated.cmake that associate what used to be the default variant to the new corresponding target name. If you could submit as a hotfix for test currently failing in mail that'd be great :) zephyrproject-rtos/zephyr/actions/runs/12439056759/job/34732166695#step:11:1231 This is a fix that needs to be done anyway, and will be quicker/simpler to deploy than updating<EMAIL_ADDRESS>and pulling through a manifest update on Zephyr side. Thanks!

@kartben technically we are not deprecating the boards. We are modifying the names so we can use variants instead of revisions. @decsny asked you in response to a comment from Mahesh about using the migration guide to highlight the change, although he didn't believe it needed to be there.

@decsny hey you can't just drop board names without notice, they go through deprecation process. Please add entries to boards/deprecated.cmake that associate what used to be the default variant to the new corresponding target name. If you could submit as a hotfix for test currently failing in mail that'd be great :) zephyrproject-rtos/zephyr/actions/runs/12439056759/job/34732166695#step:11:1231 This is a fix that needs to be done anyway, and will be quicker/simpler to deploy than updating<EMAIL_ADDRESS>and pulling through a manifest update on Zephyr side. Thanks!

@kartben technically we are not deprecating the boards. We are modifying the names so we can use variants instead of revisions. @decsny asked you in response to a comment from Mahesh about using the migration guide to highlight the change, although he didn't believe it needed to be there.

The old board name is being deprecated, and that's what the file I pointed out is meant for. https://github.com/zephyrproject-rtos/zephyr/blob/e8c5405609e355cf9483debffbd09844e4c92900/boards/deprecated.cmake#L3
This will break downstream users, exactly like we're seeing in CI right now with "downstream-ish" mcuboot, so the old name needs to be preserved.
I missed the comment from @mmahadevan108 and then @decsny, sorry about that. The right course of action would be no migration guide entry needed because old board name should just be deprecated for now (and that should be called out in release notes to make sure folks get the memo, as the deprecated name will be dropped in two releases)

And just to make it clearer why randomly renaming a board is not a good idea, just imagine if we just decide that good ol' frdm_k64f is now freedom_k64f and how many things and users this would break all over the place :)

I'll be submitting the hotfix shortly


Date and filesize of a mediafile is not correctly displayed

I think the date of a mediafile is given in seconds but in the client accepted as ms. The filesize is not in a "human readable" format displayed.

Additions - the problem is present in the file list view, but not in the upload.
Solution
client/src/app/site/mediafiles/components/mediafile-list/mediafile-list.component.html

            {{ getDateFromTimestamp(mediafile.create_timestamp) }} · {{ mediafile.filesize }}

this needs either a pipe (framework terminology) example mediafile.size | h... or h(file.size)
Except we already have that in another part of the application
client/src/app/shared/components/media-upload-content/media-upload-content.component.html
            <mat-icon [inline]="true">data_usage</mat-icon>
            {{ getReadableSize(file.mediafile.size) }}

client/src/app/shared/components/media-upload-content/media-upload-content.component.ts
/**
 * Converts a file size in byte into human readable format
 *
 * @param bytes file size in bytes
 * @returns a readable file size representation
 */
public getReadableSize(bytes: number): string {
    if (bytes === 0) {
        return `0 B`;
    }
    const unitLevel = Math.floor(Math.log(bytes) / Math.log(1024));
    bytes = +(bytes / Math.pow(1024, unitLevel)).toFixed(2);
    return `${bytes} ${[`B`, `kB`, `MB`, `GB`, `TB`][unitLevel]}`;
}

pr #872 solves half the problem
the current view being
x/x/1970, 2:x:x AM · 35.xx kB

Once this pr is merged the next steps would be :

Removing the local function from the upload view, using the general pipe there
Doing the date thing

openslides-client/client/src/app/site/mediafiles/models/view-mediafile.ts
public get timestamp(): string {
    return this.mediafile.create_timestamp ? this.mediafile.create_timestamp : null;
}

openslides-client/client/src/app/site/mediafiles/components/mediafile-list/mediafile-list.component.ts
I'm leaving my debugging notes here :+1:
public getDateFromTimestamp(timestamp: string): string {
return new Date(timestamp).toLocaleString(this.translate.currentLang);
}
"JavaScript stores dates as number of milliseconds since January 01, 1970, 00:00:00 UTC"
Solution
public getDateFromTimestamp(timestamp: string): string {
    let timestamp2 = String(Number(timestamp)*1000);
    let timestamp3 = new Date(timestamp2);
    let timestamp4 = timestamp3.toString();
    // return timestamp;<PHONE_NUMBER>
    // return timestamp2;<PHONE_NUMBER>000
    // Date(1645722502000)  Sat Feb 26 2022 ...
    // return timestamp4;   Invalid date
    return timestamp4;
}

Now it's an issue of data type conversion, or maybe something else.


Dynamic reloading of config file not always reliable

This new feature in v0.15: "Add support for dynamic reloading of config file when watching" (commit bccf957) is a welcomed addition, but may not work reliably for all OSs or text editors.  See spf13/viper#142 and go-fsnotify/fsnotify#80.

Related issues:

Issue #1053: File change watcher is not working in TextMate2 on Mac
go-fsnotify/fsnotify#17: Atomic saves in text editors cause havoc, unable to watch individual files

Once this is merged we can close this:
https://github.com/go-fsnotify/fsnotify/pull/111

Also related: #1840 Duplicate pages created


Feature request: Parallel extrude along path

The existing “extrude along path” feature extrudes perpendicular to the path, like the red image. It would be useful to allow parallel extrusion along a path, like the blue image.

Thanks for the suggestion - I'm just looking into this now, but I've found some bugs in the current implementation and I'm having a bit of trouble recreating either of these shapes. Do you happen to have a snippet of ShapeScript code to produce the left hand shape that I can use for testing?

This gives a rough approximation of the perpendicular vs parallel extrude along paths.
detail 99

define sweepPoints (
    (1.000157 0.002094)
    (0.998642 0.002569)
    (0.994106 0.003984)
    (0.986575 0.006316)
    (0.976089 0.009524)
    (0.962709 0.013555)
    (0.946509 0.018343)
    (0.927582 0.023810)
    (0.906037 0.029875)
    (0.881997 0.036445)
    (0.855603 0.043428)
    (0.827009 0.050725)
    (0.796385 0.058239)
    (0.763914 0.065870)
    (0.729788 0.073517)
    (0.694216 0.081078)
    (0.657412 0.088451)
    (0.619601 0.095532)
    (0.581016 0.102217)
    (0.541894 0.108401)
    (0.502481 0.113980)
    (0.463021 0.118853)
    (0.423763 0.122921)
    (0.384955 0.126093)
    (0.346846 0.128290)
    (0.309677 0.129441)
    (0.273687 0.129495)
    (0.239109 0.128415)
    (0.206162 0.126188)
    (0.171835 0.122326)
    (0.139362 0.116037)
    (0.109873 0.107670)
    (0.083605 0.097631)
    (0.060740 0.086326)
    (0.041395 0.074153)
    (0.025636 0.061477)
    (0.013484 0.048626)
    (0.004914 0.035872)
    (-0.000128 0.023429)
    (-0.001729 0.011445)
    (0.000000 0.000000)
)

define sweepPath path {
    for i in sweepPoints {
        point i
    }
}

define star {
    path {
        for 1 to 5 {
            point 0 -0.05
            rotate 1 / 5
            point 0 -0.1
            rotate 1 / 5
        }
        point 0 -0.05
    }
}

// Perpendicular
extrude {
    position 0 0.5 0
    star
    along sweepPath
}

// Parallel
group {
    loft {
        orientation 0 -0.5 0

        for i in sweepPoints {
            translate 0 i.y i.x
            star
            translate 0 -i.y -i.x
        }
    }
}

@jaikdean this is implemented in the latest version. Use axisAligned true per the example here: https://shapescript.info/mac/builders.html#extrude


Add func params count checker

Coverage increased (+0.2%) to 62.59% when pulling 814dd08c28b7cac0752e6ab9e3b2b79a3cac6e7f on add-func-params-count-checker into 2568ac30c0b48b0281359686304f7593b751f0cb on master.

I don't know how to name a checker that checks both parameters and returned values. I prefer to keep it separate for now. There isn't a big gain in merging them.


Speed Calculation explanation

Thanks for your explanation, can you please explain how you are calculating the speed in this block ?
Because I can't understand some of the transformations like scale_real_length, scale_real_time_passed, speed = speed/6*40 and scale = 1
please elaborate a bit.

I will perform code cleanup and then prepare detailed documentation about the source code, soon.

in speed_prediction.py,

you used the following function to calculate real time:
scale_real_time_passed = total_time_passed * 24
which i think it should be:
scale_real_time_passed = total_time_passed / 24
speed = speed/6*40 # use reference constant to get vehicle speed prediction in kilometer unit
how to get the reference constant?

thanks

Hello,
Any update, please.

Hi everyone,
in speed_prediction.py file. When i remove line if scale_real_time_passed != 0:
so when i run project, i have an issue that :
speed = scale_real_length / scale_real_time_passed/ scale_constant  # performing manual scaling because we have not performed camera calibration
ZeroDivisionError: float division by zero.
Can anyone explain that for me.
Thanks!!

Anyone here understood how it works?

he every one
check this link is very helpful to know how  can calculating the speed of vehicle : https://www.researchgate.net/publication/317312246_Speed_Estimation_On_Moving_Vehicle_Based_On_Digital_Image_Processing
i think if you want calculate speed you need know  a lot of stuff about camera like( FOV and size of image and fps , and perpendicular distance between the camera and  street )
please if any one  have a update of code with exact calculate  speed vehicle  put it here

hi every one
check this link is very helpful to know how can calculating the speed of vehicle : https://www.researchgate.net/publication/317312246_Speed_Estimation_On_Moving_Vehicle_Based_On_Digital_Image_Processing
i think if you want calculate speed you need know a lot of stuff about camera like( FOV and size of image and fps , and perpendicular distance between the camera and street )
please if any one have a update of code with exact calculate speed vehicle put it here


feat: use existing distribution policies when provided

Closes #194

Thanks, @onhate. Sorry to nitpick here, but I prefer simpler if statements as I laid out in previous PR instead of custom Mutable type (although that's a cool trick) with casting. I think if statements are simpler to understand what's going on and more approachable for new devs to the codebase. Do you agree?

in this one I will disagree, I see this as simpler solution because you avoid creating the extra overhead of the let variables that overrides the overrides, see.
return {
      ...this.commonBehaviorOptions,
      origin,
      allowedMethods: cloudfront.AllowedMethods.ALLOW_ALL,
      originRequestPolicy: cloudfront.OriginRequestPolicy.ALL_VIEWER_EXCEPT_HOST_HEADER,
      cachePolicy, // overrides the overrides
      edgeLambdas: this.edgeLambdas.length ? this.edgeLambdas : undefined,
      functionAssociations: this.createCloudFrontFnAssociations(),
      responseHeadersPolicy, // // overrides the overrides
      ...this.props.overrides?.serverBehaviorOptions, // if those properties are being set isn't it confusing that this is overriding all?
    };
    ```

    The 'mutable' approach is more like, try the defaults, if something is missing, then fallback.

    But it's ok, I can change it for keeping the standards

I see this as simpler solution because you avoid creating the extra overhead of the let variables that overrides the overrides

I see your point. But IMO, less code does not alway mean simpler. I think less code is often better, but not at cost of simplicity. Extreme example, but this is why we don't use minified code as source code :) Appreciate your flexibility.


Can we remove PASSWD required for .env?

Can everything just be done by editing dockerfile instead of using sudo?

 DEVELOP: DevContainer for CodePraise

 https://github.com/codepraise/codepraise-devcontainer/issues/9

 ISSUE: Remove PASSWD #DevContainer

Still leave sudo but remove the password for using sudo. it's a safety mechanism to alert the user that this behavior requires the highest privilege from the root; it might affect the system.


Can't use function for heading numbering if level is greater than 1

Description
This is ok:
#heading(numbering: it => it)[]
#heading(level: 1, numbering: it => it)[]

Compiler error:
#heading(level: 2, numbering: it => it)[]

I've checked the documentation and I don't see any warnings that this wouldn't work. Either add a note about this, or this is a bug.

I was using it like this: #heading(numbering: it => none)[] and wanted to pass a level, but suddenly got an error. Then I've checked, and I can actually pass none directly and therefore don't need to decrease heading counter. But this removes the nested indent in outline (with it => none the indent is present, but the number is missing, which is what I want).
Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

This is a bit of a quirk due to the fact that numberings use varargs arguments.
Look at the numbering function:
numbering("1.", 3)   // 3.
numbering("1.", 3, 7)  // 3.7.

Your custom numbering function must also accept a variable amount of arguments. This is done like this:
#set heading(numbering: (..n) => {
  // use n.pos().at(x) to access level x+1
}

If the level is fixed like in your example you can also accept a fixed number of arguments like this:
#heading(level: 2, numbering: (n1, n2) => none)[]

https://typst.app/docs/reference/meta/outline/:

How to indent the outline's entries.
auto: Indents the numbering of the nested entry with the title of its parent entry. This only has an effect if the entries are numbered (e.g., via heading numbering).

Ok, I've found everything that I wanted, including that I used true instead of auto. But now the question is what is auto exactly? The documentation doesn't say that.
But I've found a solution to my problem:
#set outline(indent: it => for _ in range(it) { h(1em) }) // I'm guessing `auto` is an alias for `1em`
#let unnumbered-heading(name, ..args) = {
  heading(numbering: none, name, ..args)
}

@freundTech, I guess it is kinda understanding, if I dig deep:
https://typst.app/docs/reference/meta/heading/#parameters-numbering:

https://typst.app/docs/reference/meta/numbering/:

But the problem is more to do with the error:
error: unexpected argument
   ┌─ /file.typ:42:21
   │
42 │   heading(numbering: it => it, name, ..args)
   │                      ^^

Like, what does it say? How it is unexpected, when with level: 1 everything works? The function has to get some arguments, right? So maybe change the error to be more user-friendly?

It's unexpected because the way it's written you can receive only a single argument.

The diagnostic is bad, you can open a separate issue about that.


Automate the updating of the cf cli under windows

A customer is asking for an automated way to keep their IT Self Service application up to date with the windows CF CLI.
Is there a way to automate the updating of the cf cli under windows?

Hi @MarcPaquette
There is a CLI plugin that allows users to update their CLI to the latest in-place. It's not automatic - you have to run the plugin command - but at least you don't need to visit our download page or write a download script:
https://github.com/rakutentech/cf-plugin-update-cli
A year ago we explored having such a self-update function in the cf CLI, but for various reasons decided to drop that idea and take advantage of existing methodologies and user workflows to support this use case.
This resulted in the APT and YUM repositories, allowing users to keep their cf CLI up to date in a fashion familiar to them.
For Windows users we don't have a solution yet. At the time I saw activities in the Windows world for there to be a Windows package manager (possibly based on Chocolatey?) so I figured we'd wait to see if that became widely accepted.
In the meantime, I see a drive from Microsoft to incorporate more Linux support, both on people's desktops and in the Azure environment, with them now even providing the (Linux) cf CLI pre-installed in customers' Azure environments.
Regards,
Dies Koper
CF CLI PM

My 5 cents to this topic: update-cli plugin does not work on Windows environment (tested 2 days ago)

@ibakirov Why not submit an issue to its tracker?

I will do it but as I see that plugin's development shows no activity for a long time...

No feature requests, no bug reports - there was no need to? ;)

rakutentech/cf-plugin-update-cli#3 for fyi

Closing as I believe the original question is answered. Feel free to reopen or submit a new issue if you have more questions on this.


removed repeat normalize, fixed #219

fixes #219 by removing normalize added in #200
cc: @anka-213

@anka-213 Do you have any thoughts on this? Do you remember the rationale for the removed code in this PR?

Without it, only the latter is fast with my bugfix. (At least I believe so, I haven't tested it.)

All right. I'm going to merge this for now and cut a new release since it passes CI. @anka-213 If there are more tweaks you'd like to make, that would be OK, since we now have a regression test from @debris.

Thanks @debris! Much appreciated!

docopt 0.8.1 is on crates.io with this patch!


Missing verification caused index out of bounds

I was having an index out of bounds error pointing to this line let classname_candidate = classname_parts[-1] looking at the code the same check that is made in the other places the same code is used is missing. I am a real noob in VimL but I think this makes sense and I also tested it for some time and everything seems fine.

This change is

I will re-open this PR when(if) I get more detail about what is causing this issue. Closing for now.

I have more information about this issue. Here is an example when this happens
class A
{
// nothing on purpose
}

class B
{
    public function somefunc()
    {
        $a = new A();
        $c = $a->something();
        $c->  // the error happens here
    }
}

It seems to happen when the function does not exists but I also have seen it when it cannot find the class as well. I should return no result but not an error


Copy from Phar doesn't works.

ie: "skeleton/.router.php".
Should use Phar::extractTo?

Phar::extractTo is not a solution because extracted files are deleted from Phar archive... In fact the problem is we can't use relative path (ie: "../") when we request a file from a Phar archive.
The best way is to use the absolutre path from the root of the Phar file.


Update get in touch options and merge info with contributing

Update the information in get-in-touch with contact information as currently on https://cucumber.io/support
Merge the information that was in get-in-touch with contributing.
Add link to https://cucumber.io/blog/2017/10/03/invest-in-cucumber

Thanks @olleolleolle !


how to support offline messages ?

Hi, I'm a javascripter
I don't konw how does offline-messages work!
As far as I can understand, connected the host, and subscribe a topic, then can receive the messages that host published.
Then disconnected the host, can I receive the messages when connected ? the answer is no.
I must connect and subscribe first.
so how does offline-messages mean ?

MQTT protocol supports 'clean session' flag.  If the 'clean session' is set to false, the broker will keep a session to receive messages when the client is disconnected.

If you are using npm mqtt module. You can use this code:
var uniqueid = "some-unique-id";
var client  = mqtt.connect('mqtt://host-name/', {
  protocolId: 'MQIsdp',
  protocolVersion: 3,
  clientId: 'id_' + uniqueid,
  clean: false
});
client.subscribe('topic', {qos: 2});
client.publish('topic', 'Hello ' + friendphone, {qos:2});

Keeping a clientId will maintain a session in server.
clean(session) = false will not clean session if client disconnect
whatever message you publish or subscribe, do it with qos=1 or 2


[bug]: Doubt about correction

Describe the bug
I have this same problem using the another_flushbar package that when you swipe and the screen gets stuck and it was said to have been fixed, using the flutter documentation I saw that it doesn't crash but when swiping the snack bar ends up going to the previous screen too and it does not close. Is there no way to close it?
To reproduce

click on the function to appear the snackBar
Swipe to the previous screen
the snack bar continues to appear on the screen

Expected behavior
No response
Screenshots
No response
Additional Context
No response

The snackbar would need to be swipeable. This is not how default snackbars work so you would have to implement that yourself.
There are packages that allow for swipable snackbars, Stacked used the built in snack from scaffold which does not allow that.


Renovate/monaco editor

#@@Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX
<!-- Feel free to add any additional description of changes below this line --https://www.facebook.com/shamiaw2

Hi there,
This pull request appears to have been opened by accident. As such, we are going to close it.
We welcome future contributions from you and encourage you to review our contributing guidelines.


Updated deprecated links in incoming-webhooks _index.md

Summary
Updated deprecated links in incoming-webhooks _index.md
Ticket Link

NA

Hello @Rutam21,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@cwarnermm Please review and suggest changes if any and also add the appropriate labels for Docathon.


Strawberry shake client overrides nested collection

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Strawberry shake client have some issue here. I have a query that for the same set of parameters returns collection with two items, but client has only one:

Steps to reproduce

I'm using https://crystallize.com/ e-commerce on GraphQL

Relevant log output
No response
Additional Context?
No response
Product
Strawberry Shake
Version
12.15.0

It looks odd...
https://github.com/mattszmigiel/wrong-collections
There is a object MeteredVariables that is overriden by the object from last entity...
https://github.com/mattszmigiel/wrong-collections - demo repo, send me PM and I'll send you tokens so you can validate the problem

And my last thought: the MeteredVariable objects look similar (eg. the same Id property), but there is a difference only in tiers property

I am at the moment on Hollidays, will get back to you when I am back.

I've reworked my demo repo and there is a GraphQlServer project that serves data causing problems.

It works as I want if I remove


sort() broken in several ways

x cannot sort among dimension of size 1 (effectively a no-op except returning an indices list filled with 1s)
x cannot deal with non-contiguous previously allocated indices/sorted results (via torch.sort())
x something seriously broke along the way from initial implementation somehow. Everywhere something like this occurs:
    TensorInfo<unsigned int> sortedInfo(state, sorted, dim);
    sortedInfo.collapseDims();

needs to be instead:
    TensorInfo<unsigned int> sortedInfo(state, sorted, dim);
    sortedInfo.sizes[dim] = 1;
    sortedInfo.collapseDims(dim);

(there's a ghost of prior code with a reference to "dropDim" that this is about, but is no longer in the code)
x Thrust fallback sort should check not only that the sorting dimension is contiguous, but that the indices dimension is contiguous. e.g., t = torch.CudaTensor(2, 50000):normal():transpose(1, 2):sort(1) is broken.
One can do segmented sorts in Thrust with some finagling, and I think you can get the iterators to handle strides. I tried a segmented sort before in the THCSort code, but for small sizes it was slower than the bitonic thing.
Thus, I think it is possible to fix the Thrust fallback issue, and actually make cutorch sort work for all inputs, regardless of size, dims or stride.
Fixes for the other issues coming soon.

fixed now


putContainerArchive() (and PutContainerArchive) should not have string type hint for inputStream

All of the http client message factories that create requests turn bodies into Psr StreamInterface objects if they aren't one already.  The string type hint on the this API call forces the dev to read the entire (potentially large) archive into memory as a string before calling the putContainerArchive() method, only for the message factories to turn it into a stream anyway.  In 1.24, a string, file resource or StreamInterface object could be passed instead of a string.

With the change in https://github.com/moby/moby/pull/39248 applied to the spec file when generating the PHP code, the result is as expected.
@joelwurtz Is there any chance that this change is backported to docker-php-api? It looks like you currently have no time to maintain docker-php-api... maybe it would make sense to have one (or even more) additional maintainer. WDYT?


How to count eye blinking while capturing image?

I want to count eye blinking while capturing images as it helps to distinguish between a real face and an image. Any way out to achieve that?

Hi @NabanilC since we use OpenCV and you get every camera frame (so basically a video), you can search for ways to implement it using OpenCV. You can find some implementations online in python or C++.


JsonReaderException from dispatch create

Information:

Tools Libraries: dispatcher
Libraries' Versions:
OS: Windows

Issue Description:
dispatcher throws an exception when I enter the same LUIS app twice
Commands Example:

C:\test\botness>dispatch add -type luis -name TravelBooker -id d833c549-33f7-4c6c-9be0-1ebd41cc191d -key 97274b8102ac4c29830480182bd3f475
LUIS app id:d833c549-33f7-4c6c-9be0-1ebd41cc191d, name:TravelBooker, authoring key:97274b8102ac4c29830480182bd3f475, version:0.1 added to TravelD.dispatch

C:\test\botness>dispatch add -type luis -name TravelBooker -id c1e8e209-ea3c-44ba-a2e1-3ed7f4f60256 -key 97274b8102ac4c29830480182bd3f475
LUIS app id:c1e8e209-ea3c-44ba-a2e1-3ed7f4f60256, name:TravelBooker, authoring key:97274b8102ac4c29830480182bd3f475, version:0.1 added to TravelD.dispatch

C:\test\botness>dispatch create

Expected Behavior:
Either success or error (note the name of the app TravelBooker in the second command is wrong)
Actual Results:
Exporting services for dispatch...
Exporting TravelBooker LUIS application...
Exporting TravelBooker LUIS application...
Creating dispatch LUIS model json...
[2018-05-01T14:08:27][MergeAggregateLuisApplicationsOnPhraseLists,211,D:\a\1\s\AugmentLuisModel\UtilityLuisModelJsonAppManager.cs]The input LUIS App "C:\test\botness\data\_L_TravelBooker.json" cannot be validated, EXCEPTION=Newtonsoft.Json.JsonReaderException: Additional text encountered after finished reading JSON content: ". Path '', line 70, position 6.
   at Newtonsoft.Json.JsonTextReader.Read()
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
   at AugmentLuisModel.UtilityLuisModelJsonAppManager.MergeAggregateLuisApplicationsOnPhraseLists(JsonAppObject mergedLuisModelInJson, String luisModelInJsonTextAndOtherSourceSetting, ISet`1 nonInterchangeableFeatures, IList`1 interchangeableFeatureSets), luisModelInJsonString="{
  "luis_schema_version": "3.0.0",
  "versionId": "0.1",
  "name": "Spain",
  "desc": "Facts about Spain",
  "culture": "en-us",
  "intents": [
    {
      "name": "None"
    },
    {
      "name": "ShowCapital"
    },
    {
      "name": "ShowLocation"
    }
  ],
  "entities": [],
  "composites": [],
  "closedLists": [],
  "patternAnyEntities": [],
  "regex_entities": [],
  "prebuiltEntities": [],
  "model_features": [],
  "regex_features": [],
  "patterns": [],
  "utterances": [
    {
      "text": "the main city",
      "intent": "ShowCapital",
      "entities": []
    },
    {
      "text": "what is the capital",
      "intent": "ShowCapital",
      "entities": []
    },
    {
      "text": "where does the government sit",
      "intent": "ShowCapital",
      "entities": []
    },
    {
      "text": "where is andalusia",
      "intent": "ShowLocation",
      "entities": []
    },
    {
      "text": "where is barcelona",
      "intent": "ShowLocation",
      "entities": []
    },
    {
      "text": "where is basque country",
      "intent": "ShowLocation",
      "entities": []
    },
    {
      "text": "where is galicia",
      "intent": "ShowLocation",
      "entities": []
    },
    {
      "text": "where is prime minister",
      "intent": "ShowCapital",
      "entities": []
    }
  ]
}
      "intent": "OrderHotel",
      "entities": []
    }
  ]
}"

ERROR
Additional text encountered after finished reading JSON content: ". Path '', line 70, position 6.

------
CREATE
Usage: dispatch create [options]
Usage: dispatch create [.bot file]

Create/retrain and publish a LUIS application for dispatch

Options:

   -bot                    [Optional] Path to .bot file or bot services json file
   -dispatch               [Optional] Path to .dispatch file
   -hierarchical           [Optional] Default to true.  If false, existing intents from source LUIS model(s) will be available as the dispatch intents.    -dataFolder             [Optional] Working directory for the tool

Fixed.  The second add will not be allowed to go through since app name is unique in LUIS (with the same authoring key)

:clap:


[SPARK-15249][SQL] Use FunctionResource instead of (String, String) in CreateFunction and CatalogFunction for resource

What changes were proposed in this pull request?
Use FunctionResource instead of (String, String) in CreateFunction and CatalogFunction for resource
see: TODO's here
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala#L36
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/command/functions.scala#L42
How was this patch tested?
Existing tests

cc: @yhuai

Test build #58227 has started for PR 13024 at commit 8c2f33c.

Test build #58227 has finished for PR 13024 at commit 8c2f33c.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58227/
Test FAILed.

Test build #58230 has started for PR 13024 at commit 0de5f84.

Test build #58230 has finished for PR 13024 at commit 0de5f84.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58230/
Test PASSed.

Just minor comments. LGTM overall.

Test build #58259 has started for PR 13024 at commit f3842f2.

Test build #58259 has finished for PR 13024 at commit f3842f2.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class FunctionResourceType(val resourceType: String)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58259/
Test PASSed.

Thanks, merging into master 2.0.


Add new getFirstRow() / getLastRow() methods to FileSKVIterator or rename getFirstKey / getLastKey()

While working on more FencedFileSKVIterator tests as part of #3766 I noticed that getFirstKey() and getLastKey() are not consistent with what is returned for fenced files.
Normally the first or last key in the RFile that is returned is the actual first or last key in the file so it includes the entire key (row, cf, cq, etc). However, for fenced files if there is a range set that is after first key or before last key then only a row is returned. For example, if the start of the range that is set on the fenced reader is after the first key in the file then when getFirstKey() is called we just return the start of the range which is only a row and of course not the actual key in the file.
In order to return the actual start key for a fenced file we would need to seek to the first key in the range but this would be a performance hit as normally the first/last key are part of the index. It is also seems to be unnecessary because looking at the code base it appears that the only place these methods are actually used are places where we only care about the row and nothing else (really just splits).
So we should make this consistent behavior. We could either create new methods called getFirstRow() and getLastRow() that just return the row part of the key or we could rename getFirstKey() and getLastKey() since they don't seem to be used anywhere that needs the full key.  If we created new methods then we would likely need to updated the fencing iterator to seek to find the real first and last key for the old methods and then update the split code to use getFirstRow() and getLastRow() instead. If we go with the rename option we need to double check and verify we don't actually need the full key because I only took a quick glance and could have missed something.

@keith-turner - When you get time can you take a look and let me know your thoughts on this and which direction to go?


fix typo

LGTM

One problem I found is the username [taokelu], it’s better to use your github username, otherwise github can’t record your contributions


MATLAB CI - Pilot

Just to give you heads up, our trial period for the MATLAB cloud CI has started. I've added minimal configuration in the matlab_CI branch, which will be the testbed of the pilot application.
MATLAB tests does not run on Travis, but the repo is registered to their cloud and each time we make a request, whole repo is copied to the mathworks side, scripts are run, then a response is returned. Here is the list of some restrictions:

The MathWorks Cloud only runs the latest version of MATLAB with the Ubuntu 16.04 Linux operating system.
A single job may only run for up to 15 minutes and use up to 250MB of disk space and 1.5 GB of RAM.
A maximum of 35MB may be transferred to and from the MathWorks Cloud for each job.

First build fails, but not sure if our repo has been registered yet, I completed the paperwork. Let's wait and see what matworks has to offer :)
Edit: Response from mw

Yes – sorry about that. Once Justin has the license ready and you accept the click through, we’ll add qMRLab to a whitelist of repos which can call the service.

Seems that cloud CI is easily running out of space after test is run for charmed and proceeds to dti, you can see the log. TBH 250MB disk space is really low, just the repo itself may be occupying a significant portion of it, given that when we do git clone it is massive. On the other hand, idk how our repo is copied to their server.
Another downside is that we are not able to use the coverage generation framework we are normally using.
One option is that we can remove after finishing run with OSF file before going to the next one.

Good news from the Mathworks team!

We rolled out the next iteration of the MathWorks CI pilot. It includes:

Streaming logs
Improved stability
5GB max transfer size (up from 35MB)
5GB of disk space (up from 250MB)
7.5GB of RAM (up from 1.5GB)
MATLAB R2019a

Inactive.


checkout --tar: mtime=0 is problematic for some software

See original issue on GitLab
In GitLab by [Gitlab user @aevri] on Feb 14, 2019, 11:40
Summary
Creating tar archives with bst artifact checkout --tar ... results in an
archive where all the mtimes are set to zero.
There is more than one example where files with an mtime of zero are treated as
non-existant by other software. e.g.

This issue on ninja, "Files with zero mtime are treated as nonexistent"
This code in Template Toolkit.

Steps to reproduce
    # Make our archive and get any file out of it:
    bst artifact checkout --integrate --deps build --tar sysroot.tar target.bst
    tar xf sysroot.tar ./any_file.txt

    stat ./any_file.txt | grep Modify
    # Modify: 1970-01-01 00:00:00.000000000 +0000

    stat --format '%n mtime: %Y' ./any_file.txt
    # ./some_file.txt mtime: 0

What is the current bug behavior?
All the mtimes are zero.
What is the expected correct behavior?
If all the mtimes are set to a specific value, it is non-zero.
Possible fixes
Change the default arguments of export_to_tar from mtime=0 to mtime=1.
Other relevant information
The OSTree project
project seems to have an intention to move to an mtime of '1':

For this reason, OSTree acts as though all timestamps are set to time_t 0, so
that comparisons will be considered up-to-date. Note that for a few releases,
OSTree used 1 to fix warnings such as GNU Tar emitting "implausibly old time
stamp" with 0; however, until we have a mechanism to transition cleanly to 1,
for compatibilty OSTree is reverted to use zero again.

BuildStream version affected: /milestone %BuildStream_v1.2

In GitLab by [Gitlab user @aevri] on Feb 14, 2019, 11:42
mentioned in commit 7bc6d70c4b37f25ebf113df3d315dc18b8fd0194

In GitLab by [Gitlab user @aevri] on Feb 14, 2019, 11:43
mentioned in merge request !1149

In GitLab by [Gitlab user @sstriker] on Feb 14, 2019, 11:47
Is there a reason we are not using SOURCE_DATE_EPOCH?
https://reproducible-builds.org/docs/timestamps/

In GitLab by [Gitlab user @tristanvb] on Feb 14, 2019, 11:52
[Gitlab user @sstriker] I believe that we are: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/data/projectconfig.yaml#L68

In GitLab by [Gitlab user @aevri] on Feb 14, 2019, 14:44
mentioned in commit ed49da18bcb21a87475d75f84fdfa317a2ea7667

In GitLab by [Gitlab user @aevri] on Feb 15, 2019, 10:27
mentioned in commit 55a2e5bc70f2123b7c512806a4c9c719c94e1c78

In GitLab by [Gitlab user @aevri] on Feb 15, 2019, 11:10
mentioned in commit 39febfda560fdc0d4ab3a2440f173f5718752d5b

In GitLab by [Gitlab user @aevri] on Feb 15, 2019, 12:25
closed via merge request !1149

In GitLab by [Gitlab user @aevri] on Feb 15, 2019, 12:25
mentioned in commit 8b34e3568a753a8d5774b91f2b4701aea7f9baf9

In GitLab by [Gitlab user @aevri] on Aug 7, 2020, 10:24
mentioned in commit 563fc7dd1ab8b62b7e58e8756e3aef376dad19fb


Error: Failed to build SQLite for a executable swift package

Build Information

Xcode v11.3.1
macOS 10.15.4

General guidelines

steps

$ mkdir SQLiteDemoExecutable
$ cd SQLiteDemoExecutable
$ swift package init --type executable
$ swift run

[3/3] Linking SQLiteDemoExecutable
Hello, world!

add .package(url: "https://github.com/stephencelis/SQLite.swift.git", from: "0.12.0") to Package.swift
add target dependencies: ["SQLite"]),

$ swift run

I got : 3 warnings and 16 errors generated.
The executable can not be built!

Error Messages:

sunwrt@localhost SQLiteDemoExecutable % swift run
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:126:9: warning: 'SQLITE_SOURCE_ID' macro redefined [-Wmacro-redefined]
#define SQLITE_SOURCE_ID      "2017-03-28 18:48:43 424a0d380332858ee55bdebc4af3789f74e70a2b3ba1cf29d84b9b4bcf3e2e37"
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:141:9: note: previous definition is here
#define SQLITE_SOURCE_ID      "2019-04-15 14:49:49 378230ae7f4b721c8b8d83c8ceb891449685cd23b1702a57841f1be40b5daapl"
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:654:8: error: redefinition of 'sqlite3_file'
struct sqlite3_file {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:691:8: note: previous definition is here
struct sqlite3_file {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:752:8: error: redefinition of 'sqlite3_io_methods'
struct sqlite3_io_methods {
^
:8: note: previous definition is here
struct sqlite3_io_methods {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:1234:8: error: redefinition of 'sqlite3_vfs'
struct sqlite3_vfs {
^
note: previous definition is here
struct sqlite3_vfs {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:1531:8: error: redefinition of 'sqlite3_mem_methods'
struct sqlite3_mem_methods {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:1651:8: note: previous definition is here
struct sqlite3_mem_methods {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:3708:20: error: typedef redefinition with different types ('struct Mem' vs 'struct sqlite3_value')
typedef struct Mem sqlite3_value;
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:3980:30: note: previous definition is here
typedef struct sqlite3_value sqlite3_value;
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:5848:8: error: redefinition of 'sqlite3_module'
struct sqlite3_module {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:6225:8: note: previous definition is here
struct sqlite3_module {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:5979:8: error: redefinition of 'sqlite3_index_info'
struct sqlite3_index_info {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:6359:8: note: previous definition is here
struct sqlite3_index_info {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
:5982:10: error: redefinition of 'sqlite3_index_constraint'
struct sqlite3_index_constraint {
^
struct sqlite3_index_constraint {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
27:
struct sqlite3_index_orderby {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:6369:10: note: previous definition is here
struct sqlite3_index_orderby {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
:
/usr/local/include/sqlite3.h:5994:10: error: redefinition of 'sqlite3_index_constraint_usage'
struct sqlite3_index_constraint_usage {
^
10: note: previous definition is here
struct sqlite3_index_constraint_usage {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:6092:8: error: redefinition of 'sqlite3_vtab'
   ^

/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:6482:8: note: previous definition is here
struct sqlite3_vtab {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
:27:
struct sqlite3_vtab_cursor {
^
6506:8: note: previous definition is here
struct sqlite3_vtab_cursor {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:6621:8: error: redefinition of 'sqlite3_mutex_methods'
struct sqlite3_mutex_methods {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:7010:8: note: previous definition is here
struct sqlite3_mutex_methods {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:6794:9: warning: 'SQLITE_TESTCTRL_LAST' macro redefined [-Wmacro-redefined]
#define SQLITE_TESTCTRL_LAST                    25
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:7159:9: note: previous definition is here
#define SQLITE_TESTCTRL_LAST                    26  /* Largest TESTCTRL /
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:7064:9: warning: 'SQLITE_DBSTATUS_MAX' macro redefined [-Wmacro-redefined]
#define SQLITE_DBSTATUS_MAX                 11   / Largest defined DBSTATUS /
^
: note: previous definition is here
#define SQLITE_DBSTATUS_MAX                 12   / Largest defined DBSTATUS */
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
7159:8: error: redefinition of 'sqlite3_pcache_page'
struct sqlite3_pcache_page {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:7746:8: note: previous definition is here
struct sqlite3_pcache_page {
^
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
27:
/usr/local/include/sqlite3.h:7324:8: error: redefinition of 'sqlite3_pcache_methods2'
struct sqlite3_pcache_methods2 {
^
previous definition is here
   ^

In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/SQLiteObjc.m:26:
In file included from /Users/sunwrt/test/SQLiteDemoExecutable/.build/checkouts/SQLite.swift/Sources/SQLiteObjc/fts3_tokenizer.h:27:
/usr/local/include/sqlite3.h:7347:8: error: redefinition of 'sqlite3_pcache_methods'
struct sqlite3_pcache_methods {
^
/Applications/Xcode11.3.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/sqlite3.h:7934:8: note: previous definition is here
struct sqlite3_pcache_methods {
^
3 warnings and 16 errors generated.
[0/2] Compiling SQLiteObjc SQLiteObjc.m

I was experiencing the same issue.
No such module 'SQLite' when archiving. cocapods

I have the same issue

I encounter this issue in Xcode 12 Beta 6. Is there any workaround about this?

Same here

Same here with Xcode 12 Xcode 12 GM seed any solutions?

Try with the 0.13.0 we just released, it should fix the problem.


Image Request: Fluent-Bit for s390x

Software Name
fluent-bit
Software Version
2.1.8
Software Value
Fluent Bit is an open-source, pluggable, lightweight log collector and forwarder.
Becoming a preferred option in Kubernetes/OpenShift containerized environments.
How to build and install:
https://docs.fluentbit.io/manual/installation/sources/build-and-install
Available Docker images:
https://docs.fluentbit.io/manual/installation/docker
Note:  s390x is currently not available
How to build Docker images (for x86 arch):
https://github.com/fluent/fluent-bit-docker-image/blob/master/Dockerfile.x86_64
Requestors Role
Will self-support
Please Note
Requests made to this repo do not guarantee eventual inclusion in ICR. Each image will be evaluated for value, ease of currency and security concerns before a final decision is made.

fluent-bit has been added :)


[4.2] Derive Equatable & Hashable for uninhabited types

Explanation: Previously, the compiler wouldn't derive Equatable and Hashable for enums with no cases. This adds support. Cherry-picks #17756.
Scope: Enables derivation for enums with no cases, which was disabled before.
Risk: Low. This is enabling new functionality, so it would not affect any existing code. Because the types are uninhabited, there's no runtime code to worry about.
Testing: The test case was updated to verify that these compile without issue.

@swift-ci Please test


Add the Julia Language as an interested Org

Looking forward to submitting our GSoD Application!

@googlebot I signed it!

@googlebot I signed it!


Improve logging

Currently logging to console is hardcoded:
                runCatching {
                    val mappedEntity = deserialize<T>(message.body)

                    rabbitDeliverCallback.invoke(consumerTag, mappedEntity)
                }.getOrElse {
                    it.printStackTrace()
                }

It should be possible to plug whatever logger is used in the system instead.

I'll look into it. 😄


add missing character code in KeyRelease

got some ./apothecary update glfw build errors, tracked it down to this

Looks like this was fixed in https://github.com/arturoc/glfw/commit/09e8e92592c336592a7dffb8e1c42ff11239073d


Unicode ZWSP (zero-width space) put on clipboard with code snippet

Description
Found a code snippet in an example (e.g., here https://docs.hedera.com/hedera/getting-started/create-an-account, the "Import Modules" section). Clicked the little overlapped rectangles to copy it to the clipboard.  Went to an open IntelliJ editor window and pasted it in, found the following:

That "ZWSP" unicode character in there shouldn't be.  Causes a build error too:

(This is MacOS 12.6.1, IntelliJ 2022.3.1 build #IU-223.8214.52)
Steps to reproduce
As described above.
Additional context
No response
Hedera network
other
Version
v2.19.0
Operating system
macOS

Don't know whether it is just this one code snippet, or more.

Thanks for flagging this. Will open up an issue with GitBook to see how to resolve this as it seems it is present in other code snippets.

Emailed GitBook on 3/9/23 regarding this issue. Waiting to hear back from the support team.

Removed the blank unicode character from the code snippet to fix this issue.
From GitBook:

I noticed in the specific code block in your example that there is indeed a blank unicode character. However, I wasn't able to find other instances of this issue.
Given that, I'm thinking this was a small mistake in copying content into GitBook that copied a blank character in the middle. It should be as simple as removing that character from that specific code block - erasing it and adding the empty line again - and this won't continue to happen.


Add contributing guidelines

Here they are 🎉 Please let me know if you need me to change anything.

I'm going to try to create 1 contributing guidelines based on all the pull requests, so I'm going to close this but add your name to the contributors list and some of the content from your commits to the contributing guidelines. Thanks for helping out :D


Ignore / learn

Sometimes the tool gets it wrong and I want to ignore what the tool is telling me. Would be great to have an ignore option.

There is an ignore option, but it doesn't work for me. When a misspelled work is selected, type "Alt+." and you have the option to ignore a word.  Selecting this, however, has not effect for me. The word still shows as misspelled.

That's right you can add to the dictionary either manually (in the spell.json settings file) or via the Alt+. command @DaleKoetke mentions.
There is a limitation here however - in that to effectively check the document I do some pre-processing of the text file.  That pre-processing removes things like hyphens.  So any I can only reliably ignore words that don't include punctuation in them.
Dale I think that sis likely the issue you are running into.  I'd love to work around the issue but have found no valuable solution unfortunately.
Sean


Adding a user to an organization's team forces him/her to watch all repositories in the team repository list

Gitea version (or commit ref): 1.7.1
Git version: 2.10.2.windows.1
Operating system: Windows 2008R2 Server
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

Description

Create an organization called Organization_Test

Create, in this organization, a team called Contributors that has write acces to issues

Create the repository repo1 in this organization and add it to the Contributors repository list

Add the user pagaltier2 to the organization and to the Contributors team

Sign out and sign-in as pagaltier2

The repository repo1 is under watching and, as pagaltier2, I'll receive all new issues notification

I think there should be an option to subscribe (or not) new users to repositories they have write access.

Yes currently that is expected behavior

For 1.8 there is a config option to disable the behaviour:
https://github.com/go-gitea/gitea/pull/5852


Missing element in left and right dropdown menus

One menu is missing a < the other a >

Fixed with new UI.
https://user-images.githubusercontent.com/344310/114296321-e382f500-9ae9-11eb-9763-2c7a68659eec.mp4

Thank you, the new UI is great!


Feat/#218 add ai generation to markdown cells

Moved Prompt section ui  to separate file src/components/ai-prompt-input.tsx for reuseablity
Added ai generation functionality to markdown
mentioned issue https://github.com/srcbookdev/srcbook/issues/218

Thank you for this @Aswanth-c
I pulled down the branch and am trying it out locally. Extracting the AI prompt looks like a good change, but the functionality does not seem to work as I would expect. The goal here is for the AI to generate markdown but the prompts submitted to the models are prompts that instruct the AI to write code. The result is that it seems to mostly generate code in the markdown cell which is not intended -- we want it to write markdown.
I believe we will need a new prompt for this PR.

Thank you for this @Aswanth-c
I pulled down the branch and am trying it out locally. Extracting the AI prompt looks like a good change, but the functionality does not seem to work as I would expect. The goal here is for the AI to generate markdown but the prompts submitted to the models are prompts that instruct the AI to write code. The result is that it seems to mostly generate code in the markdown cell which is not intended -- we want it to write markdown.
I believe we will need a new prompt for this PR.

Gotcha, I will update the pr with new prompt

Thank you for this @Aswanth-c

I pulled down the branch and am trying it out locally. Extracting the AI prompt looks like a good change, but the functionality does not seem to work as I would expect. The goal here is for the AI to generate markdown but the prompts submitted to the models are prompts that instruct the AI to write code. The result is that it seems to mostly generate code in the markdown cell which is not intended -- we want it to write markdown.

I believe we will need a new prompt for this PR.

Thank you for this @Aswanth-c

I pulled down the branch and am trying it out locally. Extracting the AI prompt looks like a good change, but the functionality does not seem to work as I would expect. The goal here is for the AI to generate markdown but the prompts submitted to the models are prompts that instruct the AI to write code. The result is that it seems to mostly generate code in the markdown cell which is not intended -- we want it to write markdown.

I believe we will need a new prompt for this PR.

Gotcha, I will update the pr with new prompt

Update: i have added prompt,
will do through testing
Expect the pull request to be ready for review  by tommorow


Unscope select to avoid PG::UndefinedFunction

Having a default_scope with a select breaks since acts_as_list 0.9.5.  The error type is discussed here:
https://github.com/rails/rails/issues/19146
Unscoping the select scope fixes the problem.

@donv Thanks for contributing. Can you please add a failing test case to demonstrate the problem?

Hi @donv, should we be using count(:all) instead?

Yes, using count(:all) is probably a better solution, but it was a bigger change, so I tried for the smallest change I could see 😄 .

Thanks @donv, I think count(:all) is probably the best way forward. What do you think @swanandp?
If you could switch to that method and provide a failing test that would be great :D

Hi @donv, would you mind doing that fix with the test? :)

Hi @brendon !
No, I don't mind 😄 .  Will put it on my plan for next week or the week after.  Lots of things to do 😅 .

Thanks @donv, we really appreciate it :)

@donv: ping! :D

Thanks for the ping.  My plan has slipped :)  Will get to it.

Starting on this now.

I have added a failing test that becomes green with the current change.

I am trying to implement the count(:all) idea we had, but it proves complex since we expect to have the position_column available in many places.  Having a default scope with a select results in the position column not being present in the resulting records.
I have tried a few ways to add the position_column to the query, but then we mess up the default select of all columns.
I now think my original idea is the best, to just unscope :select.
What do you think?

Unscoping a default :select seems like an ok solution. As you say, it's unworkable not to have the position column selected. No damage can be done by unscoping the :select? There were side effects to unscoping a default :order which is why we now only unscope the :where.
@swanandp, did you have any feedback? :)

@donv, someone has proposed the unscope :select solution in a seperate pull request so I think we'll merge this one. Can you update from master just so we can get a green suite then we should be good to go :)

@brendon Rebased and green tests.


Re-add Omnibox Steady State Height Option From Flags In 126-Future Updates

Omnibox Steady State Height is flag option that it will turn bigger omnibox into small one, just like any old chrome versions before, but starting to 126, the option in flags it's gone, and it cannot change omnibox to small one as before, if is posible, can you please add that option of omnibox steady state height to flags.
Before Update To 126 [Running 124]:

After Update To 126:

--compact-ui remains available in the meantime, but I'll return this as well.

Related: https://github.com/win32ss/supermium/issues/821#issuecomment-2308444344

Actually, if one temporarily "unexpires" M124+M125 flags, the flag is there, but even when Disabled and browser relaunched, it has currently NO effect :cry: :

@win32ss I also wonder, what happened to the Chrome Refresh 2023 Design flag? Why did it get removed? I know your main proiority is dealing with the ongoing removal of classic Chrome theming, but I hope you can get this flag back in the future.

I also wonder, what happened to the Chrome Refresh 2023 Design flag? Why did it get removed?

Someone opened (and then hastily closed) an issue about this :wink: ; from what I understood so far, Google have permanently imposed CR23 by default now in M126, removing most, if not all, code that supported the previous design, hence providing a flag that would disable CR23 and restore the old one is now a moot point...
What has been done already in Sm-126-pre is, I think, that most of CR23 parts have been removed and most parts of the previous design have been shoehorned into their place:
c42e8cd (and relevant comments :wink: )
9d138ac
6679d59b9a727bbb03ffa41a0b564b33ecaf4d77
Keeping both the (complete) old and CR23 GUI together in the same branch would be a coding challenge, I suppose... If there is high demand for keeping CR23 in Sm (by newer WinOSes users, no doubt), perhaps a separate 126 branch could be created and compiled? But this would create extra maintenance burdens on the author's shoulders :wink: ...

If I were to keep only Chrome 2023 refresh ui or the pre 2023 one I would keep the refreshed version because:

2023 refresh tabs look much better with Aero transparent background as it's filling space around inactive tabs.

It emphasizes that Supermium is based on the current Chromium, not look the same outdated 109 version which is good for the PR of both the browser and old Windows versions

I also wonder, what happened to the Chrome Refresh 2023 Design flag? Why did it get removed?

Someone opened (and then hastily closed) an issue about this 😉 ; from what I understood so far, Google have permanently imposed CR23 by default now in M126, removing most, if not all, code that supported the previous design, hence them providing a flag that would disable CR23 and restore the old one is now a moot point...
What has been done already in Sm-126-pre is, I think, that most of CR23 parts have been removed and most parts of the previous design have been shoehorned into their place:
c42e8cd (and relevant comments 😉 )
9d138ac
6679d59
... thus providing a flag that would enable/return CR23 is now quite difficult 😉 ...
Keeping both the (complete) old and CR23 GUI together in the same branch would be a coding challenge, I suppose... If there is high demand for keeping CR23 in Sm (by newer WinOSes users, no doubt), perhaps a separate 126 branch could be created and compiled? But this would create extra maintenance burdens on the author's shoulders 😉 ...

The feature for Chrome Refresh 2023 is still there (--enable-features=ChromeRefresh2023), but I will readd the flag for it as well.

Thank you I'm going to reupdate my devices to the latest version of supermium

I also wonder, what happened to the Chrome Refresh 2023 Design flag? Why did it get removed?

Someone opened (and then hastily closed) an issue about this 😉 ; from what I understood so far, Google have permanently imposed CR23 by default now in M126, removing most, if not all, code that supported the previous design, hence them providing a flag that would disable CR23 and restore the old one is now a moot point...
What has been done already in Sm-126-pre is, I think, that most of CR23 parts have been removed and most parts of the previous design have been shoehorned into their place:
c42e8cd (and relevant comments 😉 )
9d138ac
6679d59
... thus providing a flag that would enable/return CR23 is now quite difficult 😉 ...
Keeping both the (complete) old and CR23 GUI together in the same branch would be a coding challenge, I suppose... If there is high demand for keeping CR23 in Sm (by newer WinOSes users, no doubt), perhaps a separate 126 branch could be created and compiled? But this would create extra maintenance burdens on the author's shoulders 😉 ...

The feature for Chrome Refresh 2023 is still there (--enable-features=ChromeRefresh2023), but I will readd the flag for it as well.

My marvelous thanks to you!

Edit: also one thing can you add in the new chrome themes in this flag?

Yeah, there are some missing themes there.

hope they get added back and change depending on what mode you have on supermium like with this

The feature for Chrome Refresh 2023 is still there (--enable-features=ChromeRefresh2023), but I will readd the flag for it as
well

hope It will be added back soon

but I'll return this as well.

... Apologies for bumping this, but I'm still missing a functioning Disabled chrome://flags/#omnibox-gm3-steady-state-height GUI pref in the latest Sm-v126-r4 :sob: :

(As I wrote above, the flag can be brought back to Sm-126, but currently is non-functional) ; --compact-ui is not an option for me, because it just "squashes" the tab-bar too much for my taste :wink: ...