Support tuple IP in URIs

If you pass an #uri{} as a 'to'/'from'/'ruri' meta to nksip_uac functions, you get a cryptic error message like this one:
[error] gen_server <0.374.0> terminated with reason: bad argument in call to erlang:list_to_binary([<<>>,60,<<"sip">>,58,[<<"xxx">>,64],{172,31,0,18},[58,"5060"],<<>>,[],[],62,[[59,<<"tag">>,...]],...]) in nklib_unparse:header/1 line 89
The reason is that domain part of the URI is assumed to be a binary or a string and is used as is. Now I'm forced to use nklib_util:to_host/1 before passing the IP address to a sending function, while it looks like it's better to allow tuple typed IPs as an input and pass them through nklib_util:to_host/1 internally.
PS I'm using the current master branch.

Hi,
It could make sense, butit is not so easy. The #uri{} structure is used extensively in many projects, and the host part is supposed to be a binary. I would need to modify thousands of lines of code to supported tuples there.

I see. May be putting this into the #uri{} documentation would be enough.


Cannot send NEO/GAS from multisig address on testnet

Current behavior

version: 0.7.8
Cannot send NEO/GAS from multisig address with the following command:
send GAS AZ7toUBAnFki1Amv2ZRNu2bPh7Bvqwhnmq 5000 --from-addr=AMC2wLX59UdatQQ5jUJGeAMYV9FK4xoQUS
Output always returns Veryfiying tx result... failed
Screenshot

Printed tx:

{
    "txid": "0xb00355a845f6bec3280157456867cb6916eeade4f99f87007b5c90d24aafb3bf",
    "size": 238,
    "type": "ContractTransaction",
    "version": 0,
    "attributes": [],
    "vout": [
        {
            "n": 0,
            "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
            "value": "5000",
            "address": "AZ7toUBAnFki1Amv2ZRNu2bPh7Bvqwhnmq"
        }
    ],
    "vin": [
        {
            "txid": "0x65a97acef06d845fe873312970c97998994271ec0b314f10b215158198ad8707",
            "vout": 0
        }
    ],
    "sys_fee": "0",
    "net_fee": "0",
    "scripts": [
        {
            "invocation": "40f31fb72d73960f4cc21ab03d5bb2b039fda1d541a582a5c90a0abe0e14a87f4c4f07228829f98e3b9729277a8a7d12538ae65b374d9511a19c22d13328b9d71d",
            "verification": "512103373b1e567885bcd84de14f7cbfb89cdf54d4e22a53cc5ce5008c7a56451ec3dd21037fc87f6db91256fe6d0624feeddc1f4d5a2f698bdc5c453b55d1645134c7143b52ae"
        }
    ]
}

Nodes:

Total Connected: 5
Peer IPv4Address(type='TCP', host='<IP_ADDRESS>', port=20333) - IO: 0.014142 MB in / 0.003667 MB out
Peer IPv4Address(type='TCP', host='<IP_ADDRESS>', port=20333) - IO: 0.013898 MB in / 0.003725 MB out
Peer IPv4Address(type='TCP', host='<IP_ADDRESS>', port=20333) - IO: 0.012731 MB in / 0.00352 MB out
Peer IPv4Address(type='TCP', host='<IP_ADDRESS>', port=20333) - IO: 0.014204 MB in / 0.003667 MB out
Peer IPv4Address(type='TCP', host='<IP_ADDRESS>', port=20333) - IO: 0.011526 MB in / 0.00352 MB out

Expected behavior

Transaction should be relayed and asset can be sent to targeted address

How to reproduce

Request NEO/GAS from https://neo.org/Testnet/Create and wait until receiving an email which contents pub-key from<EMAIL_ADDRESS>Open prompt by using the following command: PYTHONPATH='.' python3 neo/bin/prompt.py
Wait until everything synced
Follow the instruction of the following url: https://neo-python.readthedocs.io/en/latest/prompt.html#transfering-the-funds-to-your-own-address

My environment

OS: OSX 10.13.6
neo-python v0.7.8
Python 3.6.6

The message shows Veryfiying tx result... failed therefore it must be failed at this line
https://github.com/CityOfZion/neo-python/blob/978f77922247d2d85c63dfe8db66e856fcb56582/neo/Network/NodeLeader.py#L343

Recommended trying wallet rebuild based on previous comment in Discord from @metachris . Waiting on wallet to finishing syncing now.

@jseagrave21 it doesn't work

I am debugging it and found that it fails at this
https://github.com/CityOfZion/neo-python/blob/master/neo/Core/Helper.py#L185
where engine.EvaluationStack.Count = 5 instead of 1

@DNK90 please show what command you used to import (omit a small part of the keys if you feel that's necessary) the multi signature address

@ixje
import multisig_addr 03373b1e567885bcd84de14f7cbfb89cdf54d4e22a53cc5ce5008c7a56451ec3dd 1 03373b1e567885bcd84de14f7cbfb89cdf54d4e22a53cc5ce5008c7a56451ec3dd 037fc87f6db91256fe6d0624feeddc1f4d5a2f698bdc5c453b55d16xxxxxxxxxxx

@ilkericyuz this is not an error. The notification means that the multisig address requires more than one signature which is specified when it is created see
https://github.com/CityOfZion/neo-python/blob/e3780126f9cf8175f9f3c7ad27f36f2baae20508/neo/bin/prompt.py#L121
In order to relay the tx you initiated the other signing wallets need to sign the tx with sign <json tx>

Closing due to inactivity. If you think this issue still persists comment here and we can re-open the discussion


[5.9] Include signing entity in version metadata

Clients who are asking for metadata prior to download an archive from the registry may still want to display information from the signature which is non-trivial to extract. This includes it if possible.
(cherry picked from commit 638cc86af08296bc3da65bbed1117c0287d82054)

@swift-ci please smoke test


RKE2/K3s v1.24 Kubernetes versions incorrectly appear as experimental verions

Setup

Rancher version: v2.6-head https://github.com/rancher/rancher/commit/240554b59c83b2dca36684098abc5a8e63893dde
Browser type & version: Chrome

Describe the bug

On the latest v2.6-head, when you navigate to Cluster Management > Create for RKE2/K3s clusters, you see the following when viewing the Kubernetes versions:

This is an issue as 1.24 is not supposed to be in experimental; this behavior is not see in 2.6.10, so this appears to be a regression.
To Reproduce

Navigate to Cluster Management > Create.

Make sure you toggle RKE2/K3s, if not already.

In the Cluster Configuration > Basic section, click the Kubernetes version dropdown and view that v1.24 for RKE2 and K3s appear as experimental.

Result
v1.24 appears as experimental for RKE2/K3s.
Expected Result

v1.24 should not appear as experimental for RKE2/K3s.

@nwmac , thank you for looking into it.
These settings are calculated in runtime based on versions coming from KDM and unfortunately there seems to be a bug in the code where versions are sorted lexicographically as strings vs. being sorted as proper semvers so v1.24.9+rke2r2 is seen as a higher version than v1.24.10+rke2r1.
Ref: https://github.com/rancher/rancher/blob/a1abea50e0f47a5e38a77c72bbab77556805c870/pkg/channelserver/channelserver.go#L188
This needs to be fixed for both release/v2.6 and release/v2.7 even though the immediate issue is not currently reproducible on v2.7-head because the default there is v1.25.x and the latest x is <9.
It's also worth noting that the ideal fix should by a hybrid of semver and lexicographic comparison in sense that for k3s / RKE2 releases metadata is used for r2, r3, ... releases that should be considered higher versions than r1, i.e. v1.24.9+rke2r2 > v1.24.9+rke2r1 and v1.24.9+k3s2 > v1.24.9+k3s1 (per strict semver comparisons there is no precedence in each of these pairs).
The fix to the immediate problem can be simple semver comparison though.

Can be validated in the lastest v2.7-head

Validated that this is addressed on v2.6-head https://github.com/rancher/rancher/commit/6f7aebc479d83f0b458ce5dfe59ddde8fe933155. See details below:
ENVIRONMENT DETAILS

Rancher install: Docker
Rancher version: v2.6-head https://github.com/rancher/rancher/commit/6f7aebc479d83f0b458ce5dfe59ddde8fe933155
Browser: Chrome

TEST RESULT

Scenario
Test Case
Result

1
Validate that RKE2/K3s do not list v1.24 as an experimental Kubernetes version
:white_check_mark:

Scenario 1

Navigated to Rancher > Cluster Management > Create.
Validated that v1.24 no longer shows as experimental:

note; this is effecting v2.7.1 but as noted above and in the last linked PR, will be fixed in the next 2.7 release of rancher


Update Replication of mysql_secure_installation script for current versions of mariadb-server.

Update Replication of mysql_secure_installation script for current versions of mariadb-server.

I used the current mysql_secure_instillation script from the latest mariadb-server code.
Newer versions of mariadb-server were failing for me due to depreciated commands in the current script.
I am rusty with git, so will have to look how best to tidy things up.


opentelemetry-collector: 0.31.0 -> 0.33.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector-contrib/releases.
meta.description for opentelemetry-collector is: "OpenTelemetry Collector"
meta.homepage for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector"
meta.changelog for opentelemetry-collector is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0/bin/otelcontribcol 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.33.0 with grep in /nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0

found 0.33.0 in filename of file in /nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0

directory tree listing: https://gist.github.com/dad6082140a4cbc888981286aeadd904

du listing: https://gist.github.com/1e93f92a6d0f6325cd49715cd6ee55c6

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
opentelemetry-collector

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A opentelemetry-collector https://github.com/r-ryantm/nixpkgs/archive/71f3892be7d403bd0c0954d686370e4565e7d1ea.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0
ls -la /nix/store/lfz2l8lyzrj0yqya3gbd0n8md4bf2f1i-opentelemetry-collector-0.33.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

opentelemetry-collector

Maintainer pings
cc @uri-canva @kalbasit for testing.

Can't build it on darwin:
# github.com/open-telemetry/opentelemetry-collector-contrib/cmd/otelcontribcol
/nix/store/5psc6givws1ww94hbvr8411mb59nqqy4-go-1.16.7/share/go/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
duplicate symbol '_readdrivestat' in:
    /private/tmp/nix-build-opentelemetry-collector-0.33.0.drv-0/go-link-390201380/000029.o
    /private/tmp/nix-build-opentelemetry-collector-0.33.0.drv-0/go-link-390201380/000032.o
ld: 1 duplicate symbol for architecture x86_64
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
builder for '/nix/store/34057slahhipnfp1y3qyji0512yyhz5i-opentelemetry-collector-0.33.0.drv' failed with exit code 1
error: build of '/nix/store/34057slahhipnfp1y3qyji0512yyhz5i-opentelemetry-collector-0.33.0.drv' failed

Will wait for ofborg: https://github.com/NixOS/nixpkgs/pull/135243/checks?check_run_id=3392948661

It is just failing for darwin. We could ignore that because the error seems strange for me.

I don't think we should ignore it, it's a regression, the current version works on darwin.

I don't think we should ignore it, it's a regression, the current version works on darwin.

sure, but do you have a darwin machine and know how to fix it? I don't and darwin is a 2nd class citizen because of those weird breakages and that it is harder to test for people.

I think any change is hard to test on hardware you don't own, but we shouldn't merge in changes that break a system just because of that, and ofborg is there to catch unintentional breakages.
One can test changes on hardware they don't have access to using vms. A cursory search for macos vms shows up https://github.com/myspaghetti/macos-virtualbox for example. Can't vouch whether it's any good or not, I do have a darwin machine, so I have only needed to set up linux vms.

darwin is a 2nd class citizen

I don't think it is, the set of packages on it is definitely smaller than on linux, but I see it as just as supported as any non-nixos linux.

This seems to be related: https://groups.google.com/g/golang-nuts/c/sh4bxSnfY3w.

Related discussion on whether darwin breakages should block updates and how darwin maintainers might not be able to handle the load of reviewing / addressing darwin specific issues: https://github.com/NixOS/rfcs/pull/112

Sorry after more discussion in https://github.com/NixOS/rfcs/pull/112 I've realised I was wrong to block this PR because of darwin compatibility, it is ok to proceed by marking darwin as broken.

Preparing a new PR to bump to 0.38.0, will try disabling CGO.

New PR up, supersedes this one: https://github.com/NixOS/nixpkgs/pull/145283.


[BugFix] Fix multiple be export empty file to oss without broker bug

Signed-off-by: xyz<EMAIL_ADDRESS>What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #9999
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

If there are 3 BE, and only 1 BE has data, export will generate 2 empty temp file and 1 temp file with data on remote export path.
Howerver, in current implementation, for empty file, S3OutputStream will skip it, and finally only generate 1 temp file with data, which leads to moveTmpFiles() in FE can not find the temp file.

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 0 / 13 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/ExportJob.java
0
1
00.00%
[651]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
11
00.00%
[139, 233, 234, 235, 236, 237, 246, 247, 248, 249, 250]

:large_blue_circle:
com/starrocks/fs/hdfs/HdfsFsManager.java
0
1
00.00%
[854]

run starrocks_be_build

run starrocks_fe_unittest

run starrocks_admit_test

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 0 / 13 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/ExportJob.java
0
1
00.00%
[651]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
11
00.00%
[139, 233, 234, 235, 236, 237, 246, 247, 248, 249, 250]

:large_blue_circle:
com/starrocks/fs/hdfs/HdfsFsManager.java
0
1
00.00%
[854]


for coverage

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 52

0 of 0   changed or added relevant lines in 0 files are covered.
85 unchanged lines in 20 files lost coverage.
Overall coverage increased (+0.6%) to 64.654%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/sql/execute/result/DistinctQueryResult.java
1
98.0%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/sql/execute/result/MemoryQueryResult.java
1
97.83%

sharding-core/sharding-core-optimize/src/main/java/org/apache/shardingsphere/core/optimize/sharding/statement/dml/ShardingInsertOptimizedStatement.java
1
76.92%

sharding-core/sharding-core-parse/sharding-core-parse-common/src/main/java/org/apache/shardingsphere/core/parse/sql/segment/dml/expr/complex/CommonExpressionSegment.java
1
0.0%

sharding-core/sharding-core-parse/sharding-core-parse-common/src/main/java/org/apache/shardingsphere/core/parse/sql/segment/dml/expr/complex/SubquerySegment.java
1
0.0%

sharding-core/sharding-core-parse/sharding-core-parse-common/src/main/java/org/apache/shardingsphere/core/parse/sql/segment/dml/expr/simple/LiteralExpressionSegment.java
1
0.0%

sharding-core/sharding-core-parse/sharding-core-parse-common/src/main/java/org/apache/shardingsphere/core/parse/sql/segment/dml/expr/simple/ParameterMarkerExpressionSegment.java
1
0.0%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/InsertCipherNameTokenGenerator.java
1
93.75%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/InsertQueryAndPlainNamesTokenGenerator.java
1
96.77%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/WhereEncryptColumnTokenGenerator.java
1
97.5%

Totals

Change from base Build 9105:
0.6%

Covered Lines:
9100

Relevant Lines:
14075

💛  - Coveralls


macOS Open AppData dir broken

Clicking the "Open AppData directory" button does nothing on macOs Big Sur (and previous versions as well).
Should open finder at $HOME/Library/Application Support/chatterino

Can reproduce on macOS Catalina 10.15.5 with chatterino 2.2.3-beta2 (commit 6499c7c12).
Cache folder link works correctly.

Happy to pick this one up as I have a working macOS environment.


Light High Contrast (experimental): internal terminal

Issue Type: Bug
terminal.selectionBackground seems to be white and the selection is not visible.
VS Code version: Code 1.65.0 (b5205cc8eb4fbaa726835538cd82372cc0222d43, 2022-03-02T11:11:20.886Z)
OS version: Darwin x64 21.3.0
Restricted Mode: No

/duplicate of #144500


mod crashes when i load into save 1.20.1

I'm experiencing a crash when using Slayer's Beasts in combination with Biomes We've Gone. The crash report indicates a "Feature order cycle found," which seems to be related to biome generation conflicts between the two mods. I've ensured both mods are up to date, but the issue persists. Is there a known compatibility fix or a recommended configuration adjustment to resolve this? Any help would be appreciated. Here's the crash report for reference: [Insert link to the crash report if possible]. plz help me fix
crash-2024-09-01_22.58.00-server.txt
2024-09-01-4.log.gz
latest.log
latest.log
this

This should be a fairly easy fix, when I have some time I'll put out a new version.


meta/badger: update BadgerDB to v3.2103.5

close #3289

Codecov Report
Patch coverage has no change and project coverage change: -0.03 :warning:

Comparison is base (7540bea) 55.42% compared to head (90a82d9) 55.39%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3309      +/-   ##
==========================================
- Coverage   55.42%   55.39%   -0.03%
==========================================
  Files         142      142
  Lines       33881    33881
==========================================
- Hits        18779    18770       -9
- Misses      13105    13111       +6
- Partials     1997     2000       +3

Impacted Files
Coverage Δ

pkg/chunk/disk_cache.go
72.81% <0.00%> (-0.73%)
:arrow_down:

pkg/meta/sql.go
59.39% <0.00%> (-0.14%)
:arrow_down:

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

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


Instruction substitution help

I encountered an operation to print a string, so I needed to use the LA instruction. The specific code is shown in the figure below. Is there any alternative solution?

And str1 is defined as str1: .asciiz "Target is found at ".
Thx in advance.

The problem is that I only used the hex screen component of logisim for data display, so the CPU only supports syscall where $v0 is either 34 or 10 (for printing integers and halting, see this).
If you'd like, you can try to add the support for displaying strings (I think there's full-fledged screen in logisim?). Basically you need to add support for la instruction and also add support for proper decoding in Syscall Decoding component in the cpu to generate proper signals to display strings on the full-fledged screen.

If supporting la is too laborious, a quick hack can be writing a loop to read each byte from the string, but again you still need make syscall decoder to support a more advanced screen.

Okay, thank you very much, I am ready to give it a try.

I have done as you said, and there is no problem with the code now. However, when I was using the pipeline circuit simulation on Logisim, I encountered a problem. The LED display could not display my calculation results correctly.
The result is supposed to be 000006 and I have checked it on Mars.

my code:
# Created by Deardeer on 2021/5/2
# binary_search.asm - a program for binary search

# C++ code
# int nums[] = {1,2,3,4,5,6,7};
# int target = 6;
# int l = 0, r = 6, m;
# while(l <= r) {
#     m = (l + r) / 2;
#     if(nums[m] == target) {
#         cout << ans + 1; // index of target in nums (indexed from 1)
#         return 0;
#     }
#     else if(nums[m] > target) r = m - 1;
#     else l = m + 1;
# }
# cout << "-1";
# return 0;

.data
.text
main:
    # data init
    addi $s0,$0, 1           # current generated value
    addi $s1,$0,0            # nums array's address

    sw $s0,0($s1)            # nums[0] = 1
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[1] = 2
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[2] = 3
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[3] = 4
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[4] = 5
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[5] = 6
    addi $s0,$s0,1
    addi $s1,$s1,4
    sw $s0,0($s1)            # nums[6] = 7

    # search init
    add $s3, $zero, $zero    # l = 0
    addi $s4, $zero, 6       # r = 6
    addi $s1, $zero, 0       # s1 points to nums header address
    add $t1, $zero, 6        # target = 6
while:
    slt $t2, $s4, $s3        # (r < l) ? 1 : 0
    bne $t2, $zero, not_found# judge l <= r

    # m = (l + r) / 2
    addu $t2, $s3, $s4
    srl $t2, $t2, 1          # get m : sum / 2

    sll $s0, $t2, 2          # get offset: m * 4
    add $s0, $s0, $s1        # convert index to address
    lw $s0, ($s0)            # nums[m]

    # compare nums[m] with target
    bne $s0, $t1, not_equal
    jal found                # nums[m] = target, found target

not_equal:
    slt $t3, $s0, $t1        # (nums[m] < target) ? 1 : 0
    bne $t3, $zero, right    # nums[m] < target, find in right
    beq $t3, $zero, left     # nums[m] > target, find in left

right:
    # l = m + 1
    addi $s3, $t2, 1
    b while                  # continue finding

left:
    # r = m - 1
    addi $s4, $t2, -1
    b while                  # cotinue finding

not_found:
    addi $v0, $zero, 34      # print integer on LED display
    addi $a0, $zero, -1      # target not found, return -1
    syscall                  # display on the screen

    addi $v0, $zero, 10      # exit
    syscall

found:
    addi $v0, $zero, 34      # print integer on LED display
    addi $a0, $t2, 1         # target found, return m + 1
    syscall                  # display on the screen

    add $v0, $zero, 10       # exit
    syscall

Then I used another code to test the light display and the results were displayed correctly. I do not understand.

another light display test code:
.data
.text
main:
    addi $v0, $zero, 34
    addi $a0, $zero, 1
    syscall
    addi $v0, $zero, 34
    addi $a0, $zero, 2
    syscall
    addi $v0, $zero, 34
    addi $a0, $zero, 3
    syscall

Looks like it hits the not_found block, displaying -1 (0xFFFFFFFF)
not_found:
    addi $v0, $zero, 34      # print integer on LED display
    addi $a0, $zero, -1      # target not found, return -1
    syscall                  # display on the screen

It may be a bug in the CPU, does it work on single cycle cpu? if it succeeds in single cycle cpu, then the bug might be related to hazards.
Logisim can run one tick at a time, and Mars shows the data for each register. I remember when I was debugging the CPU I would run the instruction one by one and check if the registers (regfile circuit) are in line with what Mars says, and see how instruction / data flows in the pipelines.
I currently don't have the time to do this myself, if you're interested, you're welcome to test which particular instruction diverges from Mars simulator. I can provide some high-level description of what each component does.

I just tried it on single cycle cpu, but I get the same result “FFFFFFFF” as the pipeline CPU. I am going to try to single-step debug the CPU in Logisim. BTW, I have one more question, why is it that every time I export a HEX file from Mars, I can't use it directly in Logisim. When I choose to load image, Logisim tells me “Image file has invalid format header”. Then I compared my HEX file with yours and the first line "V2.0 RAW" was missing. I have to manually add the first line in my hex file such that I can use it in Logisim. And it does, I can load the image normally after adding. Was there a problem with my selection when exporting in Mars?
selection in Mars when exporting:

open error when load image in Logisim

I would say it's a requirement from logisim, and I honestly don't know the reason. I had to add that line to any file Mars generates, too. It's just a magic "number" that logisim expects to find at the start of assembly file..

And you're right about the wrong result "FFFFFFFF". I changed the "not_found"  return value to "1", then tried agagin in Logisim. I found that whatever the target value is, the result is always 1. I don't know if there is a bug in my code  or something.

Mars should the the authority here, if Mars runs fine the code probably should be fine. The reason could be that you're using instructions not supported by the CPU. A second glance through your generated assembly code shows that you're using b instruction (unconditional branch), which is not implemented (see list of supported instructions here). You could try changing the b instructions to j (unconditional jump).

Mars should the the authority here, if Mars runs fine the code probably should be fine. The reason could be that you're using instructions not supported by the CPU. A second glance through your generated assembly code shows that you're using b instruction (unconditional branch), which is not implemented (see list of supported instructions here). You could try changing the b instructions to j (unconditional jump).
It works!!! It's my fault. I didn't notice that you didn't implement the B instruction. Thank you for spending so much time helping me!


Support to TP-Link TL-WDR4300 and TL-WDR3600

Hello Péter, thank you once again for the package for the Linksys. It is working very well and without any issues.
Could you please assist me in generating the package for these two routers? Thank you.
https://openwrt.org/toh/tp-link/tl-wdr4300_v1
https://openwrt.org/toh/tp-link/tl-wdr3600_v1
Thanks :)

Librespot only works on arm or x86. These have mips chips. I don’t think it will work…
Anyway:

find the right sdk image (tag) on docker hub - https://hub.docker.com/r/openwrt/sdk/tags
add the tag to the build.yml
run the github action

Thank you for the clarification. Unfortunately, support for this processor is not available.


Product picture is not being displayed in RTL

Hi there,
First, i'd like to thank everyone contributing to this project. I'm working on a website that use both english and arabic, I'm running:
WordPress 4.7.4
WooCommerce 3.0.5
Polylang 2.1.3
Hyyan WooCommerce Polylang Integration 0.29.1
SiteOrigin North Theme.
The problem is that the products picture is not being displayed on the arabic product page. So everything is displayed properly on the category and sub category pages, but it’s not displayed when you go to any individual product page.
Someone tried to help me at WordPress forums, but he told me that Hyyan WooCommerce Polylang Integration <IP_ADDRESS> doesn't work with WooCommerce Version 3.0.5, but somehow it worked for me, he also suggested changing those options for Polylang:
– I have unchecked featured image synchronised translation.
– Deactivated Media activated that enables different pictures for different languages.
Still no luck after changing this. I would really appreciate any help or assistance.
Thanks!

I don't know if your problem is related buy try to download and install an updated version of the plugin from the following repository:
https://github.com/Jon007/woo-poly-integration
It's updated to work with WooCommerce 3.0.

thanks theleemon, it's true we can't offer advice and support on PragmaticTurtle's setup because we already know it can't work, however:
@PragmaticTurtle
"– I have unchecked featured image synchronised translation.":

This option needs to be ON, it must be checked if you want the featured image to be synchronised.  Turn it on and check again.
This is a Polylang option, not a woo-poly-integration option, so it doesn't belong in this forum and is independent of versions of woocommerce and  woo-poly-integration.


Implement OPTIONS http method

This is a pretty common http method when using javascript's fetch api with CORS enabled. I think Tide should probably be able to automatically be able to handle this based on what routes are set and what corresponding methods are available.

Just a remark on this (and also to the related PR at https://github.com/rustasync/tide/pull/104), it seems that Tide currently stores routes as a HashMap keyed on HTTP method, with values being the routers that contain endpoints with the given HTTP method (and accessed through the URL path).
This is just my idea, but one naive way of adding automatic support for OPTIONS is probably to just key on every available HTTP endpoint (GET/POST/PUT/DELETE/etc.) and see if the route exists at that particular resource. It seems a little inefficient, since in the end we're making a total of at least 9 calls as per all of them, but maybe there's a more efficient way of doing this?

Another similar problem involving with the same design choice of routing aforementioned. :
From the perspective of the semantics of HTTP methods, 405 Method Not Allowed is a better choice over 404 Not Found when there is an endpoint on a specific route path but request methods are not matched.
For example, https://github.com/rustasync/tide/blob/279e0f05a0a24fba9fc192f1d7956ad60fa0cf24/examples/messages.rs#L69
registers POST method on /message. It is supposed to response with 405 Method Not Allowed HTTP status which clearly indicates that the request method is unexpected but the resource (path) is valid.
This behaviour is adhered by most matured Web framework in other programming languages. But it seems that many of the famous used Web frameworks in Rust prefer to take the contrary way. There would be some performance penalty to be compliant, but I think it is worth discussing.

Any progress on this? It's on the 0.1 milestone, but we're already at 0.6... I'm willing to help out if you point me in the right direction.

Note from triage: We handle CORS through the CorsMiddleware; OPTIONS is handled inside the Tide router. We should add docs for this though.
We're unsure however if simplify specifying the middleware also setups the options endpoint; it's been a while. We should make it so that we can enable that. One way to get there is by enabling middleware to run before the router, which is something we may want to do for other reasons as well.


UserMenu has wrong icon color in dark theme

Describe the bug
UserMenu hardcodes the icon color default to gray[500]:
https://github.com/pxblue/react-native-component-library/blob/dev/components/src/core/user-menu/user-menu.tsx#L54
What is the expected behavior?
Dark themes should use black[200] as the default
What are the steps to reproduce?

Open the demo
Switch to dark theme
Observe the items in the bottomsheet of the UserMenu

Screenshots or links to minimum reproduction example

Environment

Anything else to add?
Discovered in the Auth Workflow example

Change https://github.com/pxblue/react-native-component-library/blob/dev/components/src/core/user-menu/user-menu.tsx#L54 to be conditional based on the theme


fix(v2): use require.resolve for all webpack presets and plugins

Motivation
Issue #2576 shows that docusaurus v2 doesn't work with Yarn v2 with pnp enabled.
This diff doesn't try to resolve the issue of the plugin system caused by the incompatibility: it can be solved by using the pnpLoose mode for now. Instead, it will fix some of the webpack plugin loading issue related to yarn pnp.
Inside the webpack config file, it refers to presets and plugins by strings, like '@babel/plugin-transform-runtime'. This setup happens to work with the traditional package managers' behavior on node_modules, which tries to hoist @babel/plugin-transform-runtime to the top-level node_modules if it can. However, it won't work under pnp, which expects that all dependencies are explictly declared.
In this case, since it's declared in a string form, it's webpack instead of @docusaurus/core that will resolve this module to an absolute path. Since webpack doesn't declare @babel/plugin-transform-runtime as dependency, the resolution failed. By using require.resolve, we ensure that @docusaurus/core will resolve the path. Since @docusaurus/core declared @babel/plugin-transform-runtime as a dependency, the resolution will succeed and results in a correct absolute path for webpack to consume.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
I have setup a repo to show that these are the minimal changes necessary to make docusaurus work under pnpMode: loose.
Also, all the tests still passes and deploy preview still works.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Can we cut a new @next release with this commit @SamChou19815  @yangshun?
I'm using pnpMode: loose but I'm blocked on this

Can we cut a new @next release with this commit @SamChou19815 @yangshun?
I'm using pnpMode: loose but I'm blocked on this

@pranaygp  I tested on my local machine with various docusaurus packages unplugged and with my changes manually applied, and it can run in pnp loose mode. However I do not control the release process.

We'll cut a new release within the next few days.

@SamChou19815 I followed the instruction on your repo and it worked like a charm. It's rather annoying to have to use pnpify (I haven't needed it for anything else so far) but I'm glad it works for now

@SamChou19815 would the plugin normal syntax still work at all? If not we will have to update the docs asap to prevent more reports like #2825

@SamChou19815 would the previous plugin import syntax still work at all? If not we will have to update the docs asap to prevent more reports like #2825.
I'm wondering whether we should change the default template's docusaurus.config.js as well. Please advise!

docusaurus.config.js doesn't need to use require.resolve since I already use createRequire in #2789. In that specific issue, it might be the case that they are using a version that's too old. There might be some misconfiguration since both yarn and pnp doesn't install the latest version of those plugins.

docusaurus.config.js doesn't need to use require.resolve since I already use createRequire in #2789.

Ahh I forgot about that. Thanks for the reminder.

Managed to reproduce. Working on a fix. createRequire appears to be used in a slightly wrong way, and weirdly this problem is not caught in this repo probably due to the yarn workspace setup.

Got it, thank you!


feat: added receiver address to generic swap facet

I used the receiver also for excess tokens, please make sure it's ok

Updated.


model not defined on ModelNotFoundException

Hi, when I use the firstOrFail method on a hasManyThrough relation, ModelNotFoundException has not defined the model attribute.
I think the error is in src/Illuminate/Database/Eloquent/Relations/HasManyThrough.php:247 and can be fixed replacing this:
    public function firstOrFail($columns = ['*'])
    {
        if (! is_null($model = $this->first($columns))) {
            return $model;
        }

        throw new ModelNotFoundException;
    }

with this:
    public function firstOrFail($columns = ['*'])
    {
        if (! is_null($model = $this->first($columns))) {
            return $model;
        }

        throw (new ModelNotFoundException)->setModel(get_class($this->related));
    }

I checked a little more the HasManyThrough class and found in the findOrFail method a similar error.
In this case the parent is being setted as the model in HasManyThrough:307
    public function findOrFail($id, $columns = ['*'])
    {
        $result = $this->find($id, $columns);

        if (is_array($id)) {
            if (count($result) == count(array_unique($id))) {
                return $result;
            }
        } elseif (! is_null($result)) {
            return $result;
        }

        throw (new ModelNotFoundException)->setModel(get_class($this->parent)); // <-- THERE
    }


Support Secp256k1 signature verification for PublicKey

I hope Publickey can support the verification of secp256 publickey signature
https://github.com/informalsystems/tendermint-rs/blob/master/tendermint/src/public_key.rs#L151
I think the issue: https://github.com/informalsystems/ibc-rs/issues/1155  is related to this
When some chains use secp256k1 as the consensus PublicKey type, the tendermint-light-client will not be able to verify the signature of the light block, such as bandchain.

Hey @thanethomson, is it possible to have an update on this? It is currently blocking informalsystems/ibc-rs#1155 which actually makes it impossible to communicate with some chains like Band Protocol

@RiccardoM I have a WIP branch which adds support for ECDSA Secp256k1 signatures. Will try to include in the next Hermes release.

Happy to help review PRs for this


Maximized bool broken?

private void Maximize()
{
	App.MainWindow.SetMaximized(!App.MainWindow.Maximized);
}

This should be a simple toggle function. However, the Maximized bool always returns false, hence the window going into maximized mode, and never back.
OS: Manjaro KDE Linux (all updates installed)
Hardware: Thinkpad T14, intel iris xe, intel i7, 32gb ram.

Thanks for the report. We've actually encountered this on Linux and will look into it. We've been putting in hours on several new features and bug fixes and will try to resolve this.

This should be fixed in the latest versions of Photino. Please re-open if this is still an issue.


Bug when compiled with optimization?

If you compile thpool.c with optimization it seems to hang.
To see this, edit tests/threadpool and change the line
gcc src/conc_increment.c ../thpool.c -pthread -o test
to
gcc -g -O src/conc_increment.c ../thpool.c -pthread -o test
Then when you run ./threadpool, it hangs at
$ gdb -p 22284 ./test
0x00000000004011c5 in thpool_init (num_threads=4) at ../thpool.c:150
150		while (thpool_p->num_threads_alive != num_threads) {}
(gdb) p thpool_p->num_threads_alive
$1 = 4
(gdb) p num_threads
$2 = 4
This is with gcc-4.8.3.
If I change thpool.c, adding "volatile",
typedef struct thpool_{
	thread**   threads;                  /* pointer to threads        */
	volatile int num_threads_alive;        /* threads currently alive   */
	volatile int num_threads_working;      /* threads currently working */
	pthread_mutex_t  thcount_lock;       /* used for thread count etc */
	jobqueue*  jobqueue_p;               /* pointer to the job queue  */
} thpool_;

That seems to fix it, though it might be worth compiling the other tests with optimization to see if everything still works ok.

Thank you for your input and the fixes! I re-factored the tests now so all tests can be run with our without optimization. You can run all tests with an optimized binary by running ./optimized_compile.sh. I ran the tests and your fix seems to work nice for all test cases.
Thanks again :)


Implement HTML id parsing proposal

See #206 / https://github.com/microformats/microformats2-parsing/issues/44

Can add the test cases. Agreed id="" shouldn't be in the result - id "must contain at least one character". Will update the spec text proposal to reflect this.

I'd suggest trim($e->getAttribute('id')) !== '' to cover any authoring whitespace mistakes like id=" ". Otherwise LGTM!

I went ahead and merged this. As I had already completely forgotten about it… Letting reviewed patches sit and get stale seems wrong.


db pull error

Hi Prisma Team! The following command just crashed.
Command
db pull
Versions

Name
Version

Platform
windows

Node
v16.18.1

Prisma CLI
4.8.1

Engine
d6e67a83f971b175a593ccc12e15c4a757f93ffe

Error
Error: [libs\sql-schema-describer\src\mssql.rs:290:33] called `Result::unwrap()` on an `Err` value: "Getting namespace from Resultrow ResultRow { columns: [\"column_name\", \"data_type\", \"character_maximum_length\", \"column_default\", \"is_nullable\", \"is_identity\", \"table_name\", \"constraint_name\", \"numeric_precision\", \"numeric_scale\", \"namespace\"], values: [Text(Some(\"ID\")), Text(Some(\"bigint\")), Int32(None), Text(None), Boolean(Some(false)), Int32(None), Text(None), Text(None), Int32(Some(19)), Int32(Some(0)), Text(None)] } as String failed"

Hey @sg-maqib, It would make our life easier to reproduce (and then fix) if you could possibly share your db schema with us and which database/version you are using.
Thanks

Hey @sg-maqib, could you please share your Prisma schema and your database kind and version? Otherwise, we won't be able to investigate this issue. Thanks!

 We would need more info to investigate this issue.


begin end

https://github.com/JSQLParser/JSqlParser/blob/6cff161dacc1e6feeccce709ca08220e576836be/src/main/java/net/sf/jsqlparser/statement/Block.java#L31
in oracle 19c
‘begin end;‘ its needs the semicolon otherwise oracle showed the error code “pls-00103”.
Is there an option to provide.

Greetings!
Thanks for the information, I would implement this accordingly.

Closed, since no further question has been asked.


store GET handler for the end user

This adds a store GET handler for the end user.
It can be accessed with a URL like the following:
http://localhost:8101/store/1
The frontend/src/pug/store_id.pug template might need some further updates.
This is for #14.

LGTM!


Error running server

The server is starting fine and says
vite v2.9.5 dev server running at:

Local: http://localhost:3309/
Network: use --host to expose

But when I go to the page I get:
This localhost page can’t be foundNo web page was found for the web address: http://localhost:3309/
HTTP ERROR 404
On Mac - OS Monterey 12.4
Any ideas?

@andyjamesn this is a chrome extension template, so you need to use the extension to debug your app, not the localhost env

@andyjamesn checkout the usage part

@xiaoluoboding Thank you but I am a little confused, the usage part does not provide any clearer information.
So I run pnpm build from my terminal and it starts the server
Then when I load the Extension into chrome using "Load unpacked" and choose the "dev" folder.
If I try use the extension it pops up saying "vite server did not start"
https://share.cleanshot.com/q8JNfC
Do I need something else?

Maybe you need change the Chrome version #1


peazip: use system compression programs

Description of changes

Updated peazip to 9.5.0.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

superseding #262788

Moving the binaries into PATH didn't break anything but I've been testing if all those compression algorithms and archive formats actually work

[x] zip
[x] brotli
[x] zstd
[x] xz
[x] bzip2
[x] gzip
[x] iso
[x] zpaq
[x] wim
[x] tar
[] deb (somehow fails at extracting, but can open in file manager)
[x] 7z
[x] split

not tested

sfx
ACE
ARJ
CAB
CHM
CPIO
JAR
LHA/LZH
NSIS
OOo
PEA
RAR (creating not tested, but extracting)
RPM
ZIPX

these are all listed in the about of it's repository. The website says that it can handle more than 200 archive and compression formats but I couldn't find a list of all of them. For lots of these, I also don't have the option to create create new compressed files or archives.

peazip has plugins, I'm wondering if they should come with this package.

hmm, the only relevant plugin seems to be the additional formats one. the other 2 plugins have security issues or are now obsolete because 7zip got support for the formats they added.
the plugins are really just more executables installed into res/bin. for nixpkgs, all those executables would have to be packaged for in nixpkgs first.

putting this into https://github.com/NixOS/nixpkgs/pull/299800 now


APIKA: On changing language to Suomi in "Add API" page, related fields and lifecycle statuses don't get translated

@bajiat Verified on nightly.apinf.io. It isn't reproduced. Can be closed

This is reproducible in APIKA. That's why i reported this. Editing the title to reflect this.

@Nazarah Since the fix is in nightly, it will get to the next release. I'm closing the issue now.


CloudWatch Sink

For those in AWS land, would be cool if there was a sink that could leverage an IAM role or something to write Metrics to CloudWatch as a backend. CloudWatch Dashboard and such could be the visualization layer.
Just an initial thought - open to suggestions.

We need this as well. I'd be willing to help build it if I knew anything at all about how to get started building a sink ( as in-- a doc that describes what interfaces I need to write.  I'm sure that would be obvious if I knew go really well, but i do not ).

CloudWatch sink would be nice, might be useful to me.
@dcowden --
Looks like a new sink would need instance functions Name(), Stop(), ExportEvents(batch *core.EventBatch). Also the function CreateMySinkType() to create a new sink instance seems to be a convention, though not required. The EventSink interface is defined in events/core/types.go. You'd also need to update events/sinks/factory.go when adding a new sink type.
You can take a look at events/sinks/log/log_sink.go for a simple implementation of a sink.
That's all pretty straightforward, the AWS-side of the sink code might be more complex. Found this project https://github.com/a3linux/go-aws-mon which logs metrics to CloudWatch using Amazon's Go SDK (which is rather ugly). Note that it seems to be unmaintained so one of the project forks might be a better reference than the original.
Hope this helps!

@wizzu  Thanks, that helps, especially the go-aws-mon link.
This is on our k8s implementation list. Hopefully we can knock something out.

@dcowden This is good to hear. We have limited resources, but if you aim for the repo to be open to start, definitely let me know here. It would be great to have a fully integrated AWS solution for monitoring and its possible we could dedicate some cycles in the future.

@wizzu that is the plan for sure.

@dcowden I'm just an interested observer, I guess you mis-attributed the previous comment. :)
I just came by to note that there's a separate cloudwatch metrics Go lib, https://gowalker.org/github.com/crowdmob/goamz/cloudwatch (part of https://github.com/goamz/goamz) - it might be easier to use something like that than the official AWS SDK. At least, that's my experience from using other AWS services with Go. YMMV.

Has there been any movement on this?

Bump!
If needed, I can take a look at writing the sink.

Definitely if you have time.
I recently haven't had time to think about it :-(
Thanks,
Kevin Kuhl
DevOps - WayBlazer Engineering
<EMAIL_ADDRESS>On Jan 30, 2017, 4:48 PM -0600, Pavel Sadikov<EMAIL_ADDRESS>wrote:

Bump!
If needed, I can take a look at writing the sink.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/kubernetes/heapster/issues/1142#issuecomment-276216942), or mute the thread (https://github.com/notifications/unsubscribe-auth/ABqrPTexhpWdHc8ywwtbgzrgzqq8F4X3ks5rXmiagaJpZM4IPcvY).

It seems neither Amazon, nor Google has any interest in first-class AWS support of Kubernetes...

Would be interested in seeing this. Also interested in EKS but it's still in preview and not publicly available, thus I'm between a rock and a hard place on running with kops + something in-cluster (would have loved to see a CloudWatch integration) vs. waiting for EKS.

I think this would still be useful. Commenting to avoid avoid-close, hopefully - no idea how else to affect it.

Agreed would like to see this
On Sun, May 13, 2018 at 4:39 PM Mikko Hänninen<EMAIL_ADDRESS>wrote:

I think this would still be useful. Commenting to avoid avoid-close,
hopefully - no idea how else to affect it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/heapster/issues/1142#issuecomment-388654395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABPq3J9_UQ4oUja6h-XGreOBKt8Vxboks5tyJnvgaJpZM4IPcvY
.

--
Sent from Gmail Mobile

/remove-lifecycle rotten


gitoxide: Install shell completions.

Description of changes
gix has a subcommand to generate shell completions.
These are now installed in the prefixup phase.
I took the logic from how rg installs their completions as that's a rust project using clap as well.
The second binary ein does not (yet, I've opened a PR about this in the upstream repo as well: https://github.com/Byron/gitoxide/pull/1296) have the ability to generate completions, in the version on nixpkgs but will use the same commands (except for the name of course).
That should be the case with the next release I suppose.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I just realised, that my commit b9c5c429f6d7169e48cf287cefd1afec57f38b18 contained more than just the move of the buildInputs.
I removed it again because the completions for ein are not available for gitoxide v0.33.0.
But gitoxide v0.34.0 contains completions for ein as well, so I'll open another PR which would upgrade the version and add the completions for ein.


control.matlab.freqresp is missing in 0.9.0

Based on a discussion in #550, I think we should add the function fresp into the MATLAB compatibility module and make its usage consistent with MATLAB.  This function was removed in PR #449 and replaced with __call__, which is a good solution for the main package.  But MATLAB users may call freqresp (and evalfr) and so we should provide that functionality for people using that package.
Also, as pointed out in issue #550, the v0.8.4 freqresp function returns magnitude, phase, and frequency instead of the complex frequency response.  If we add control.matlab.freqresp back into the MATLAB compatibility module, then it should be compatible (perhaps consistent is the right word) with MATLAB.
See discussion in PR #449 and issue #434.

Looking through the code, it looks like the freqresp function, which is in the lti module, gets imported correctly in the matlab module.  (Am not at my computer so haven’t tested this yet). The sys.freqresp method, on the other hand, is deprecated in favor ofsys.frequency_response. So I think the problem might only be that it returns the results in the wrong form (mag and phase rather than complex).

Agh.  I must have been looking at some different version.  I think the problem is not that the function is missing, but that it is inconsistent with MATLAB.  Re-editing title and description.  Sorry for the confusion.

Hi, I update the control to version 0.9.0. LTI system can be callable. But I want to caculate the freqresp of a FRD system to get the complex frequency response. If there any solution?

Use H.eval(omega*1j) or H.eval(omega) where H is an FRD function.  If you want to evaluate at frequencies other than those that define the frequency response, you need to create a smooth FRD object (use frd(d, w, smooth=True)).


Remove meta stuff from private test-fixture path

Remove meta stuff from private test-fixture path.
meta elements for open graph and favicon aren't needed on private path for on-demand components.
Removals

open graph meta.
description meta.
favicon.

Review

@jimmynotjim
@sebworks

👍

👍


Windows version unable to migrate to secondary drive

Hi,
I have a Windows 10 PC with small primary SSD and larger secondary HDD. I configured Windows to install new software on the secondary drive before installing Julia from the Store. It appears that the configuration choice wasn't followed, because when I looked in apps settings it showed it was still installed on the C: drive. I chose the option to Move the app to the D: drive and it did, but (perhaps unsurprisingly) broke the internal linkage so that juliaup failed with path errors.
It would be nice if I could install Julia on D: as my system SSD is quite close to full
I can understand that this is probably not supported yet by design, so whether this issue is marked as a bug or a feature request is up to the developers.

What error do you get when you write "It broke the internal linkage"?


Invalid error code return when using malformed request to create scim2 bulk users

Description - Using a malformed request to provision bulk users return invalid status code as 200 where 400 is expected.
Tested Environement
IS 5.8.0-m6
DB - H2
JDK - 8
Ubuntu 15.10
Steps to Reproduce

Start the IS server
Send the following request to create multiple users using scim2 API (https://localhost:9443/scim2/Bulk)

{
   "failOnErrors":1,
   "schemas":[
      "urn:ietf:params:scim:api:messages:2.0:BulkRequest"
   ],
   "Operations":[
      {
         "method":"POST",
         "path":"/Users",
         "bulkId":"qwerty",
         "data":{
            "schemas":[
               "urn:ietf:params:scim:schemas:core:2.0:User"
            ],
            "Name":"Kris100",
            "password":"krispass"
         }
      },
      {
         "method":"POST",
         "path":"/Users",
         "bulkId":"qwerty",
         "data":{
            "schemas":[
               "urn:ietf:params:scim:schemas:core:2.0:User"
            ],
            "userName":"Kris101",
            "password":"krispass"
         }
      }
   ]
}

Response

{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:BulkResponse"
    ],
    "Operations": [
        {
            "bulkId": "qwerty",
            "method": "POST",
            "response": "{\"schemas\":[\"urn:ietf:params:scim:api:messages:2.0:Error\"],\"scimType\":\"invalidValue\",\"detail\":\"Required attribute userName is missing in the SCIM Object.\",\"status\":\"400\"}",
            "status": {
                "code": 400
            }
        }
    ]
}

Expected Results
Expected to get the 400 Bad Request

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


can betterarray sort descending?

can betterarray sort descending?
First use betterarray.sort， then use betterarray.Reverse
am i right？ Thank you again.

Hi @winner106
Yeah I may look at adding descending - would be easy enough to add, but the reason I don't at the moment is that .Reverse() is a fairly cheap operation to perform, so there would not be much to be gained in performance from sorting in descending in the first place vs sorting ascending and then reversing.

Hi @winner106
Yeah I may look at adding descending - would be easy enough to add, but the reason I don't at the moment is that .Reverse() is a fairly cheap operation to perform, so there would not be much to be gained in performance from sorting in descending in the first place vs sorting ascending and then reversing.

Cool,Thank you for your guidance

Cool,Thank you for your guidance


Fix/laravel module support

After the default install of Laravel package.json switched to modules in v10.2.6, a fresh install of this package is broken.
ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/Users/chrisarter/Documents/projects/CypressExample/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

Versions:

Laravel v10.10
Cypress v12.17.4
Node v20
laracasts/cypress 3.0

Changes

Change stubs to use ES modules to support new Laravel installs.

I also ran into this issue, I think it would be smart to create a flag for the cypress:boilerplate command and that it will then just change the extension of the config file to .cjs.
Or make this the new default and add a flag when using an older Cypress implementation.

I am running into ReferenceError: require is not defined. What do I need to do, to fix this?

Thanks @christopherarter, I used the code from this PR to fix the same issue on my environment.

Thx @christopherarter. Also used the changes in the PR to fix my environment.


Fix/social link

To ensure medium social link works well, I had to:

Modify the medium link at _data/social_media.yml
Modified the _config.yaml by removing @ so it builds correctly

You could just add @your_username in the config. Works for me at dev.aadibajpai.me

I was confused by the @ usually being specified in the config rather than profile_url_prefix at first, but I believe it is actually necessary since some Medium accounts do not contain the @.
https://medium.com/ycombinator

You could just add @your_username in the config. Works for me at https://dev.aadibajpai.me

Thanks for your feedback, this didn't work for me though. Also validation with http://www.yamllint.com gives an error where the @ is specified within _config.yaml

I was confused by the @ usually being specified in the config rather than profile_url_prefix at first, but some Medium accounts do not contain the @.
https://medium.com/ycombinator

Awesome, just saw that 💯  However, it's safer with the @ since  https://medium.com/@ycombinator still works but  https://medium.com/timtech4u (my account uses @ ) doesn't work.

In addition, this PR contains a guide I which explains how to use github.dev, see here

@Timtech4u what happens when you set your medium username in the config to @timtech4u?

@Timtech4u what happens when you set your medium username in the config to @Timtech4u?

It doesn't build, I get the following error:

Hi @aadibajpai @PatMyron , tried this ?

@Timtech4u do you have a link to that commit on Github?

@Timtech4u do you have a link to that commit on Github?

Yes! I triggered that now again by reverting to the previous implementation.
Link to commit here
If you noticed, I changed the first topic from EcmaScript6 to JavaScript, however this doesn't reflect on my personal website due to the failed build.
Attached is also an error message from my inbox.

@aadibajpai I think yours works because you added quotes:
https://github.com/aadibajpai/aadibajpai.github.io/blob/0a7005aefbd5c73587710bbf8d9b6172f429810c/_config.yml#L34

@aadibajpai I think yours works because you added quotes:
https://github.com/aadibajpai/aadibajpai.github.io/blob/0a7005aefbd5c73587710bbf8d9b6172f429810c/_config.yml#L34

Yeah, think so too. Would you recommend that for other users too?

I see, I wanted them to be a string by default. That explains why the @ might be giving an error without the quotes.

I had the same issue, fixed it by wraping my medium username with quotes so that you enforce the @ to be part of the string:
social_media:
  medium: "@LaGuitteMH"

Builds fine without any changes to the code, and the links works

I had the same issue, fixed it by wraping my medium username with quotes so that you enforce the @ to be part of the string:
social_media:
  medium: "@LaGuitteMH"

Builds fine without any changes to the code, and the link works

Thanks for this!
@aadibajpai @PatMyron I could open a new PR to update the instructions for using ""

@Timtech4u yes, wrapping the username in quotes should be enough.

@Timtech4u yes, wrapping the username in quotes should be enough.

Done! Also added some detailed instructions

@brandonrosage  Kindly take a look 👍


[BUG] Error message not appropriate

I'm playing with Openshift Route, and I'm getting the following error message after starting an experiment.
  - lastTransitionTime: "2021-06-09T15:30:38Z"
    message: Specification weightObjectRef invalid
    reason: InvalidExperiment
    status: "True"
    type: Failed

This most likely is due to me not setting up RBAC correctly for iter8 controller's service account to modify Openshift route for traffic shifting, but the error message seems to be not relevant. Looking at the code, the error message seems to be hard coded. Can we use the error message K8s API server gave? It should show more clearly why the K8s client API call failed.
I will need to verify whether or not this issue is due to RBAC, but just wanted to paste the error message here before I lose it.

Could you post your experiment yaml here?

OTOH, @huang195 Its nice to know that you're running the new Iter8 on OpenShift :-)

@sriumcp after creating the necessary RBAC rules, Iter8 experiment runs  to completion, so the failure message is indeed not appropriate. You can recreate this problem on a K8s cluster by removing the rolebinding for iter8-controller service account so it can't update Istio VS.

OTOH, @huang195 Its nice to know that you're running Iter8 on OpenShift :-)

Indeed, the flexibility added in the new architecture made switching from Istio VS to Openshift Route pretty straight forward.


feat: add multiple theme support

https://sovryn.monday.com/boards/2218344956/views/63221561/pulses/3015316510

It looks good but deployment is failing, pls fix it @Rickk137 .


An actual language server 📡

A big ol' language server upgrade.
Hooks up https://github.com/salsa-rs/salsa and https://github.com/ebkalderon/tower-lsp.
Gets the ball rolling with partial parsing (#123). Makes document formatting more granular.
A chonker of a PR but worth it.

Okay, having played with this for a bit it's definitely buggy. But I'ma merge this and tackle the bugs individually, rather than let this branch get any chonky-er.


fisher search fails to retrieve information about local plugins that are not git repos

This is a bug introduced in the last release where search fails to check whether there is a Git repo in the path currently being processed when local paths are installed using the fisher install <path>.

https://github.com/fisherman/fisherman/releases/tag/0.3.1


About training and evaluating in a single view setting when using Volumetric Triangulation

Hi,
Thanks for your great work!
I'm trying to reproduce the 49.9mm in case of a single view setting. Your paper said, "To check the monocular performance we have done a separate experiment with training using a random number of cameras from 1 to 4.". Does this mean that you trained your model with multi-view while evaluating in a single-view? Could you please show me more details about how to train?
Also, I've set the [config.dataset.train.*] in "human36m_vol_softmax.yaml" like this (batch-size: 4)
.
But when I run the code (I've pre-processed the H36M dataset correctly and same as yours), I got this error,

where I cannot understand what code line 200-213 in train.py are doing?

Is it because I trained with a single-view? Could you please help me if you are available?
Thank you! @karfly
Shirley

Hi, @ShirleyMaxx!

Yes, to get 49.9 score in single-view setup we train our model on 1 – 4 views simultaneously.
In single-view setup we don't predict the global coordinates of the skeleton, we predict coordinates, relative to the base joint (pelvis). Lines 200-213 in train.py do the calculation of the relative positions of the skeleton.

Hi, @ShirleyMaxx!

Yes, to get 49.9 score in single-view setup we train our model on 1 – 4 views simultaneously.
In single-view setup we don't predict the global coordinates of the skeleton, we predict coordinates, relative to the base joint (pelvis). Lines 200-213 in train.py do the calculation of the relative positions of the skeleton.

WoW, thanks for your kind and quick reply!!
Now I've figured out what 200-213 lines meant. But I'm still confused about the 'yaml' file you used when you got 49.9 score.
I mean, when I use this modified 'yaml' to train (batch-size:2, while keeping the other settings same as human36m_vol_softmax.yaml)

it stuck at Line 208, where you're transforming the coordinates to a relative one, showing that

File "train.py", line 208, in one_epoch
keypoints_3d_gt_transformed[:, torch.arange(n_joints) != base_joint] -= keypoints_3d_gt_transformed[:, base_joint:base_joint + 1]
IndexError: The shape of the mask [3] at index 0 does not match the shape of the indexed tensor [2, 17, 3] at index 1

So, I'm wondering whether the configuration in my 'yaml' is wrong. Because I've already run successfully with your default configuration (human36m_vol_softmax.yaml), where randomize_n_views=false, meaning that it doesn't need to execute the transformation. However, when I set randomize_n_views=true, the code stuck at the transformation. So maybe line 208 has something wrong? Or maybe I misunderstand the single-view setting? Thus, could you please show me your config file when getting the 49.9 score?
Thank you sooooo much!!

@ShirleyMaxx, yes, the configuration is correct.

OK, it's running well now :D Thanks again!! 👍 @karfly


design time webapi - question

Nice work, thanks for your project.
Could you provide DesignTime example of webapi template generating something?
Im trying but its not yet succesfully.

Hi, I pushed a new sample on the repo, check it out:https://github.com/ZeekoZhu/TextTemplatingCore/blob/dev/samples/DesignTimeSample/Crud.tt
And a problem in the parser has been fix just now, you can download a new version later

here is a new version: https://www.myget.org/feed/zeekoget/package/nuget/TextTemplating.Tools

Great, thanks for new version.
In that example I was interested how do you read all existing controllers, using reflection or apiexplorer to generate methods with parameters, let say easy example in json?

I use ApiExplorer in the runtime templating example, but I don't think it is very useful. I guess the way that https://github.com/domaindrivendev/Swashbuckle uses is better, so I will update that example when I have more time.

Thanks.
Swagger seems quite complex.
Some time ago I came across https://gist.github.com/Gordon-Beeming/11166590
which I modified for my use with signalr in .net core..
So I was wondering how to do it analogically with webapi.
Integrated your excellent library in .net core. But for webapi seems not so many t4 examples out there.
Thanks for your effort.

Actually, I have a plan to write a design time template to generate http client code with angular http, axios, jQuery ajax, that is why I port T4 to dotnet core

Yeah, I was there also but went from js to ts and vue.js as effective elegant solution with .net core...

Im on way creating one template using reflection. Might be later in my repo. Closing this one.


Fix Juliet test

The test run_large_volume_test_with_default_values_10_channels fails on the error-log branch (see e.g. this CI run)

A subset Fraser's changes sufficient to fix the issue has been merged in https://github.com/casper-network/juliet/pull/8, and subsequently juliet 0.3 was released.


Blazor WebApp .NET 8

Hi,
I'm trying to use this library with the new Blazor WebApp with the following configuration:
Server:
builder.Services.AddServerSideJsonLocalization(builder =>
{
    builder.UseEmbeddedJson(options =>
    {
        options.ResourcesPath = "Resources";
    });

    builder.EnableLogger(true);
});

WebAsssembly:
builder.Services.AddWebAssemblyJsonLocalization(localbuilder =>
{
    localbuilder.UseHttpHostedJson(options =>
    {
        options.ResourcesPath = "Resources";
        options.NamingPolicy = (basePath, cultureName) =>
        {
            return new Uri(
                $"{basePath.Replace("_content/Blazor.Client/", builder.HostEnvironment.BaseAddress)}.{cultureName}.json",
                UriKind.Absolute
            );
        };
    });
    localbuilder.EnableLogger(true);
});

I have both files Global.en-US.json and Global.fr-FR.json under the Server Project in wwwroot/Resources/.
I get the following errors:
warn: SoloX.BlazorJsonLocalization.Services.Impl.EmbeddedJsonLocalizationExtensionService[7]
Embedded File Resources\Global.en-US.json does not exist
warn: SoloX.BlazorJsonLocalization.Services.Impl.EmbeddedJsonLocalizationExtensionService[7]
Embedded File Resources\Global.en.json does not exist
warn: SoloX.BlazorJsonLocalization.Services.Impl.EmbeddedJsonLocalizationExtensionService[7]
Embedded File Resources\Global.json does not exist
fail: SoloX.BlazorJsonLocalization.Core.Impl.JsonStringLocalizerFactory[14]
Unable to load localization data for Blazor.Client.Global in assembly Blazor.Client, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null with culture en-US
I've tried playing around with the file location. If I put them in the Client Project, then Server Mode works but WebAssembly mode stops working and I get the error:
"Failed to find a valid digest in the 'integrity' attribute for resource"
Any ideas?

Hello,
What version of the library do you use?
Why do you use HttpHosted in client side and Embedded on server? Why don't you use same on both? its simpler if you use same on both. Otherwise you may need to do additional setup on server side. (There are examples in the repository where it is done)

In the case where you want to use Embedded, your files must be in your project folder like this:
{poject folder}\Resources\Global.xx-XX.json
and make sure that the files are embedded in the assembly and that the satellite assembly are generated.
When you want to use HttpHosted you have to put your files in your wwwroot:
{poject folder}\wwwroot\Resources\Global.xx-XX.json

If you use the version 2.0.0, you don't need to setup NamingPolicy, it is already define the way you name your files.
I will try to add an example using .Net 8.
Hope this helps, let me know.

Hello,
I am using version 2.0.0. I was initially using Embedded Resource only but I wasn't getting any luck with it at all so started looking at other solutions.
Must be something wrong with my solution, will have to check on Monday but I created a quick example showing it working here:
https://github.com/LunaWanderer1/BlazorLocalization
Worked pretty much right away with just the Embedded files

Yes I see, it's working fine with Embedded!
I have done the exercise to change it in order to work with Http hosted Json... (I can push a PR if you want....)
To make it work you need to do those steps:

Add SoloX.BlazorJsonLocalization.ServerSide PackageReference in Blazor.csproj
Add SoloX.BlazorJsonLocalization.WebAssembly PackageReference in Blazor.Client.csproj
Move the Resources/Global.xx-XX.json files to the wwwroot in Blazor.Client project
Remove the json file from EmbeddedResource in Blazor.Client.csproj
In Program.cs (from Blazor project) change the AddJsonLocalization like this:

builder.Services.AddServerSideJsonLocalization(
    builder => builder
        .EnableLogger(true) // If you want to see the logs
        .UseHttpHostedJson(options =>
        {
            options.ResourcesPath = "Resources";
            options.ApplicationAssembly = typeof(Global).Assembly;
        }));

In Program.cs (from Blazor.Client project) add HttpClient injection support:

builder.Services.AddScoped(sp =>
    new HttpClient
    {
        BaseAddress = new Uri(builder.HostEnvironment.BaseAddress)
    });

In Program.cs (from Blazor.Client project) change the AddJsonLocalization like this:

builder.Services.AddWebAssemblyJsonLocalization(
    builder => builder
        .EnableLogger(true) // If you want to see the logs
        .UseHttpHostedJson(options =>
        {
            options.ResourcesPath = "Resources";
            options.ApplicationAssembly = typeof(Global).Assembly;
        }));

And finally since this is asynchronous loading files you can also add in your _Imports.razor file (In Blazor.Client):
@using SoloX.BlazorJsonLocalization
And in Home.razor

    protected override async Task OnInitializedAsync()
    {
        await Loc.LoadAsync();
        await base.OnInitializedAsync();
    }

Hope this helps!


List line too long

In the new material design lite list component, whether we use two line or one three lines options, the first span is only limited to one line. If more than one line in first span, the subtext will float to left below the icon or avatar.
Example:
253 Mulberry Lane Fall River,
MA 02720   <-- this line is too long
Address <-- this line will float to left below icon/ avatar

     place
     <?php echo $address ?>
   Address

So far, the best workaround i come up with is by wrapping the lines with div block element and set overflow:hidden to it. :

    place

     <?php echo $address ?>
   Address

Not sure how material design or MDL tackle this issue, just my suggestion.

Can you give us a CodePen that reproduces that issue? We have a working example in the docs, that is wrapping text over three lines.

http://codepen.io/vince8864/pen/jWJqKd
Refer to above link.
In example 1 and 2, it shows that whether it is 2 lines or 3 lines, it will mess up if the first line actually occupies two lines of space. Example 3 is simple solution that support dynamic contents. It will always wrap nicely regardless of how many lines (as long as it is within line height). By the way, why use fixed line and height anyway. I understand that list is meant for use as link so long text can get truncated. Another function is to use list to display read only content like contact page. Thing like address is dynamic and not fixed by number of line.

http://codepen.io/vince8864/pen/adrKVM
Here is a simple list that is flexible for showing information and not as entry point/link to deeper level.
As for for fixed line with fixed height which is meant to used as entry point, there should be a hyphen to clip long text. For example, in the mdl 3 lines example, try to expand the text to fourth and fifth lines and you will see the list behave wrongly. hyphen support is limited in browser. So perhaps a javascript solution is required. Hope you can somehow add the hyphen to better simulate the material design. Thanks

@vince8864 Please see the second comment in the PR [#1563] also the List specification
In the primary-content when the text of a list item overflows its container you'd need to substitute it with an ellipsis and take the appropriate action. As you mentioned above.
In a three-line list item however, text is limited to a maximum of three lines. according to the spec.

I see, so it is up to us to include the ellipsis function. ok then.
For second question, please help me clear my doubt. In the list usage, it stated: If more than three lines of text need to be shown in list tiles, use cards instead, so i'm guessing even if i use element which resembles a list but inside a card. It is considered to be a card and is not restricted by the list specification. Like the previous http://codepen.io/vince8864/pen/adrKVM example, this is a card not list, even it looks like a list, so it supports different line numbers without breaking any of the list spec. Plus all example i see in list are geared toward list being used to display links to deeper area and not display read only information. Can i assume like this?


Areas' Replace-Combine space overrides don't work right in 3.2.3-rc6

Godot version:
Official 3.2.3-rc6 build
OS/device including version:
Ubuntu Linux 16.04, 64-bit
GeForce GTX 970 with NVIDIA 384.130 driver
GLES3 backend
Bullet Physics
Issue description:
The behavior of Area Replace-Combine space overrides has changed in 3.2.3. I noted this originally in #41743 but I think it has a separate underlying cause since it appears to be new to 3.2.3.
Steps to reproduce:

Run the attached project in 3.2.3-rc6
Observe the RigidBody cube falls straight through the blue Areas (the script teleports it back to the top once it passes a certain threshold):

The expected behavior, observed in 3.2.2 and earlier is for the blue Areas to slow the RigidBody's descent and gradually float it to the top by replacing gravity:

Minimal reproduction project:
AreaReplaceCombine.zip

cc @madmiraal

The regression happened between 3.2.2-stable and 3.2.3-beta1.
Changelog: https://github.com/godotengine/godot/compare/3.2.2-stable...89f57ae12244f3269c9e3fe4684e16ec1fd2c989

The behavior in 3.2.3 RC 6 seems to be consistent between Bullet and GodotPhysics (though to test the MRP with GodotPhysics the _process method should be changed to _physics_process, otherwise the RID is invalid), so it might actually be a compat breaking bugfix and not a regression per se.
The change was caused by #39084 (reverting it restores the original behavior from 3.2.2-stable).
Most likely what's needed here is more damping now that Bullet damping is no longer way too strong.

#39084 fixed two issues in 3.2 with damping in Bullet physics: #19182 and #30991, but it also fixed how SpaceOverrides work.
This has had two effects on the MRP:

The two areas use Replace-Combine which replaces the gravity and damping settings with this Area's settings, but allows further processing to continue. With #39084, this now correctly includes combining the world gravity (the lowest priority) and hence the large gravity seen.
The two areas use a damping of 0.99. With #39084, damping is now equivalent to deceleration. This makes damping more intuitive at the cost of being less physically accurate. It also makes damping between 0.9 and 1.0 less severe; so if damping was high it will be noticeably lower than before.

I've created the following table to help make converting the damping values easier:

Damping
Old Bullet Deceleration
Godot and Fixed Bullet Deceleration

0.1
-0.11
-0.1

0.2
-0.22
-0.2

0.3
-0.36
-0.3

0.4
-0.51
-0.4

0.5
-0.69
-0.5

0.6
-0.91
-0.6

0.7
-1.19
-0.7

0.8
-1.59
-0.8

0.9
-2.26
-0.9

0.99
-4.43
-0.99

0.999
-6.52
-0.999

0.9999
-8.54
-0.9999

0.99999
-10.48
-0.99999

1.0
-60
-1.0

2
-60
-2

5
-60
-5

10
-60
-10

15
-60
-15

20
-60
-20

25
-60
-25

30
-60
-30

35
-60
-35

45
-60
-45

50
-60
-50

60
-60
-60

To modify the MRP to behave like it did before requires three things:

Set the Areas' SpaceOverride settings to Replace. This ensures that within an Area only that Area's settings apply and the world's settings are not added.
Modify the priorities of the Areas so that the second Area which is required to override the first is higher.
Modify the linear damping to around 5; so it's equivalent to what it was before.
I've attached a modified MRP for convenience:
AreaReplaceCombine-Updated.zip

Thanks, that makes sense. After making the suggested changes to my project, everything appears to behave correctly. Since this is not a bug I think the issue could be closed?

Yes, thanks for confirming that it works for you. I linked this discussion in the release blog post for other users who might need to do similar adjustments.


[BUG] TestTabWithColorBox test fails on macos terminal

Describe the bug
When running the test especially on TestTabWithColorBox, it crashes (specifically an out-of-bounds crash)
To Reproduce
Steps to reproduce the behavior:

Test go test -v .
See error

Expected behavior
Successful test
Screenshots / Logs

Versions (please complete the following information, if relevant):

Software version: dev branch
OS: Mac OS 11.6
Golang version: 1.19
Terminal using and Version: MacOS Terminal 2.11

Additional context
Debugging the text and the separator in runes shows the following results:
color.ClearCode(topBar): [9484 32 66 111 120 32 32 32 32 32 67 76 73 32 32 32 32 32 77 97 107 101 114 32 32 32 128230 32 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9472 9488]
color.ClearCode(title): [66 111 120 32 32 32 67 76 73 32 32 32 32 32 77 97 107 101 114 32 32 32 128230]

the title text in the topbar in []runes (the color.clearCode(topBar)) is 66 111 120 32 32 32 32 32 67 76 73 32 32 32 32 32 77 97 107 101 114 32 32 32 128230
while the separator (the color.clearCode(title)) is 66 111 120 32 32 32 67 76 73 32 32 32 32 32 77 97 107 101 114 32 32 32 128230
if you look at it closely on the first set of 32s the text has 5 32s while the separator has only 3 32s
probably an issue with the ClearCode method

This is quite an interesting issue.

hi @nedpals can provide the topBar and title string.

I can confirm that this test works on iterm2

hi @nedpals can provide the topBar and title string.

here are the values (i'll just paste them as []rune as turning them to strings might lose info)
topBar := []rune{9484, 32, 66, 111, 120, 32, 32, 32, 32, 32, 67, 76, 73, 32, 32, 32, 32, 32, 77, 97, 107, 101, 114, 32, 32, 32, 128230, 32, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9472, 9488}

title := []rune{66, 111, 120, 32, 32, 32, 67, 76, 73, 32, 32, 32, 32, 32, 77, 97, 107, 101, 114, 32, 32, 32, 128230}

there are runes is after call color.ClearCode() ?
can provide them on before call func ClearCode()

there are runes is after call color.ClearCode() ? can provide them on before call func ClearCode()

There are the runes before ClearCode function call.
color.ClearCode(topBar) has []rune{66, 111, 120, 32, 32, 32, 32, 32, 67, 76, 73, 32, 32, 32, 32, 32, 77, 97, 107, 101, 114, 32, 32, 32, 128230}
color.ClearCode(title) has []rune{66, 111, 120, 32, 32, 32, 67, 76, 73, 32, 32, 32, 32, 32, 77, 97, 107, 101, 114, 32, 32, 32, 128230}

@inhere Can you work on solving this?

@Delta456 xstrings.ExpandTabs maybe has error
see:

@Delta456 xstrings.ExpandTabs maybe has error
see:

This seems to work on iterm2 and the rest terminals except iterm. Can you check what should be the tab size for iterm? I will add a workaround for it.

hi @Delta456  I am running the test directly in MacOS GoLand

hi @Delta456 I am running the test directly in MacOS GoLand

I see. I really wonder why it fails on iterm.

I don't think you can even run iterm in the newer versions of MacOS. Couldn't repro this issue in MacOS Terminal 2.12.7 or Iterm2 v3.4.16 in MacOS v12.6


Personal/yli3/add istio service

Add functionalities of fetch Istio CVEs, converting Istio CVEs to responses and handling Istio CVE get requests.

curl "https://localhost:8443/v1/orchestrator/istio/vulnerabilities/1.13.6" -k
{"scannerVersion":"2.26.x-15-g341eca297c","vulnerabilities":[{"name":"ISTIO-SECURITY-2022-006","description":"Ill-formed headers sent to Envoy in certain configurations can lead to unexpected memory access resulting in undefined behavior or crashing","link":"https://istio.io/latest/news/security/istio-security-2022-006/","metadataV2":{"publishedDateTime":"2022-07-26T00:00Z","lastModifiedDateTime":"","cvssV2":null,"cvssV3":{"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","score":5.9,"exploitabilityScore":2.2,"impactScore":3.6}},"fixedBy":"1.13.7","severity":"Moderate"}]}

I notice that we didn't need to worry about scanning CVEs by version list because in Stackrox central/cve/fetcher/orchestrator.go, it is scanning by looping through all versions in a versionToClusters map. We just need to make sure version => cluster map been updated correctly. @RTann

for version := range versionToClusters {
		vulns, err := m.Scan(version, cveType)
		if err != nil {
			return err
		}
		for _, vuln := range vulns {
			if _, ok := embeddedCVEIDToClusters[vuln.GetCve()]; !ok {
				allEmbeddedCVEs = append(allEmbeddedCVEs, vuln)
			}
			embeddedCVEIDToClusters[vuln.GetCve()] = append(embeddedCVEIDToClusters[vuln.GetCve()], versionToClusters[version]...)
}


What happened to the blog posts?

You mean these https://github.com/HigherOrderCO/Kind1/tree/master/blog ?
We moved the repository for the old version of Kind there

@algebraic-sofia I think it's safe to close this one


Request for Original Data and Guidance on Running Commands

I am inquiring whether you still have the original data for Figure C. I am interested in understanding the benefits of test set augmentation, and for that purpose, I would like to access the original data for the bar labeled "with RSMILES. No test aug" in Figure C.
Additionally, if I wish to perform inference using the checkpoint you provided with the specific settings "with RSMILES, No test aug," could you please guide me on how to organize my running command for this setup?
Your assistance with these requests would be greatly appreciated, and I am looking forward to your response.

yeah, I am also interested in the performance of 'No test aug' and wanna quote it in my future work.

Thanks for your attention to our work.
The original data of top1-top10 in figure C are:
51.19
67.786
75.085
79.124
81.104
81.804
82.324
82.663
82.863
82.923
if you'd perform inference with the specific settings "with RSMILES, No test aug," you coud set the 'augmentation' as 1 and set 'test_only' as true for generate_PtoR_data.py


Improve WUnderground config validation

Description:
WUndergroud sensor platform doesn't check monitored_conditions config array length. If empty or not set, defaults to empty list and platform silently don't create sensors.
Related issue (if applicable): fixes #10452
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: wunderground
    api_key: <user_defined>
    monitored_conditions:

Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Thank you for review. Fixed indentation (I hope correctly) and changed title.

Close-open to restart Travis


Send Qt key event return in searchfield

Post a return key event when return is pressed, so the widget behaves like Qt widgets.
Few notes:

I've added some test code I used, but I'm not sure if you really need it: we playing with the gallery, I guess this can annoying
I used C++11 override keyword because I'm used to write C++11 code, but it causes a warning (but no compilation error). I can remove it if you want, or you can just keep it in case you plan to migrate to C++11 one day :-)

I've done something similar for Key_Up/Down key events; I will submit it in a separate pull request.

One query but otherwise :+1:. I'm happy with C++11 being used as long as CI is green :grinning:

Update done.
Hope it looks OK now :-)

Thanks for the PR :sparkles:!


Allow dart protos to be sent through sendports (and therefore to other isolates)

Decoded protos in Dart are represented in memory as instances of
GeneratedMessage subclasses. The GeneratedMessage stores the field
state in a _FieldSet and UnknownFieldSet.
The _FieldSet._meta field points to a BuilderInfo object, which
represents the metadata of the proto message.
Having this reference to BuilderInfo makes it hard to send dart
protos to other isolates, because
a) BuilderInfo hangs on to non-static closures, which cannot
be sent to to other isolates atm
b) Sending a transitive copy would copy the BuilderInfo object (and
it's transitive closure). That can cause big waste of memory
since an isolate would have this metadata possibly many times.
To avoid these two issues, this CL does the following:

We replace _FieldSet._meta with a getter that accesses the
BuilderInfo via the _FieldSet._message.info_ getter. This getter
is implemented in GeneratedMessage subclasses and reads from a
static field.
=> We effectively replace a load of the _meta field with load +
interface call + static field load.

To avoid performance regressions we avoid accessing the new
_FieldSet._meta getter in the hot decoding loops. Instead we
obtain this metadata once and pass it down to various methods that
are part of decoding.

For similar reasons, we remove the PbMap._entryBuilderInfo
field - which also refers to a BuilderInfo. Instead we obtain the
neccessary map-specific BuilderInfo in the main decoder loop.

This CL has to remove the 2 year long deprecated PbMap.add() function.
Closes https://github.com/dart-lang/protobuf/issues/167

I had written something similar earlier - but gave up because it caused the benchmarks to get slower.
Did you try this in the golem benchmarks?

I had written something similar earlier - but gave up because it caused the benchmarks to get slower.
Did you try this in the golem benchmarks?

Yes, I started out with your change https://github.com/dart-lang/protobuf/pull/212/files. The main performance regression for that change was caused by calling the class _FieldSet { BuilderInfo get _meta => _message.info_; } getter inside the inner decoding loop. That means we replaced a load field with a load field + interface call + static field load for each loop iteration in the decoder.
I've tried to hoist this load of _FieldSet._meta out of the loop (which makes this such a big CL), similarly the original PR kept it for maps, for which I tried to do the same, hoisting it out until the BuilderInfo is no longer necessary in PbMap.
The only downside is that I had to remove this deprecated PbMap.add() method (IIRC)

The only downside is that I had to remove this deprecated PbMap.add() method (IIRC)

Not sure that's really a downside :)

@iinozemtsev Could you give this change a trial run in g3 to see if it causes any issues?

@sigurdm made me aware that it might be better to base this off the null-safety branch, here's the PR: https://github.com/dart-lang/protobuf/pull/452

Closing this PR since we only want critical bugfixes to land on master. Active development should happen on null-safety branch which will eventually become master.


Astro 4.0 and Invalid hook call?

Toast works fine locally but I get the error regardless of how I modify.  And production builds fail. Would appreciate any tips, or tricks.  Thanks in advance.

Never mind.  Some issues with Astro upgrade and react 19.  Reverting back to 18 fixed it.


Make this loop not overuse CPU core

This is a reason why your sysmodule is slowing down system. Never make a possibly infinite loop without adding some kind of sleep logic.

Hi, thanks for the patch. Sorry if I’m completely disappeared but I’m
dealing with some personal problems. This weekend I’ll surely merge your
pull request and I hope I can come back in 2 week to fix other things
Il giorno mer 9 ott 2024 alle 10:44 MasaGratoR @.***>
ha scritto:

This is a reason why your sysmodule is slowing down system.
You can view, comment on, or merge this pull request online at:
https://github.com/Zathawo/libfancontrol/pull/1
Commit Summary

b777b36
https://github.com/Zathawo/libfancontrol/pull/1/commits/b777b362080f24497e26dc323626e4443ce5d4d8
We don't need this loop to constantly work

File Changes
(1 file https://github.com/Zathawo/libfancontrol/pull/1/files)

M source/fancontrol.c
https://github.com/Zathawo/libfancontrol/pull/1/files#diff-e0804e6fe1bc3c2b9926eac0e2cb28e95461e55e1bbb77a3b1b9f3dfe9e3ea05
(3)

Patch Links:

https://github.com/Zathawo/libfancontrol/pull/1.patch
https://github.com/Zathawo/libfancontrol/pull/1.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Zathawo/libfancontrol/pull/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZPPPKGHLTBAKLK4K7ZGCLZ2TUITAVCNFSM6AAAAABPT74YEKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TKMRTGUYDQNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, thanks for the patch. Sorry if I’m completely disappeared but I’m
dealing with some personal problems. This weekend I’ll surely merge your
pull request and I hope I can come back in 2 week to fix other things


os: RemoveAll failures with EPERM on OpenBSD

#!watchflakes
post <- goos == "openbsd" && `unlinkat .*: operation not permitted`

Saw a trybot failure in TestMemProfileCheck: https://storage.googleapis.com/go-build-log/f46e4835/openbsd-amd64-68_61f03b52.log
Maybe not a real issue, and since it seems like the problem is when invoking the system ld, I'm inclined to believe this isn't our problem.
CC @thanm

I looked at the testpoint in question -- it's not using the system "ld" as far as I can tell.  Looks more like the test built a small Go program, ran it, and the resulting binary crashed (or did an early exit) without emitting any output.

Looks like this may be another one of those "bad things happen on freebsd/openbsd" problems.

It does indeed seem to be specific to openbsd/386 these days, but now we have output from the failing command:
--- FAIL: TestMemProfileCheck (0.00s)
    --- FAIL: TestMemProfileCheck/with_memprofile (1.15s)
        ld_test.go:340: got "524288\ngo: failed to remove work dir: unlinkat /tmp/workdir/tmp/go-build3492844359/b001: operation not permitted"; want "524288"
FAIL
FAIL	cmd/link/internal/ld	15.002s

greplogs --dashboard -md -l -e 'FAIL: TestMemProfileCheck ' --since=2021-11-25
2022-02-07T18:09:07-fa04846/openbsd-386-70
2022-01-13T23:35:37-e550c30/openbsd-386-70
2021-12-22T18:43:55-0f3becf/openbsd-386-68

Just looking for the unlinkat … operation not permitted error string gives some additional failures.
greplogs --dashboard -md -l -E 'unlinkat .*: operation not permitted' --since=2021-01-01
2022-02-07T18:09:07-fa04846/openbsd-386-70
2022-01-13T23:35:37-e550c30/openbsd-386-70
2021-12-22T18:43:55-0f3becf/openbsd-386-68
2021-12-10T18:20:08-c473ca0/openbsd-386-70
2021-11-25T04:02:39-45bae64/openbsd-amd64-70-n1
2021-11-24T20:59:14-67dd9ee/openbsd-amd64-70-n1
2021-11-23T21:59:51-1ac45e0/openbsd-amd64-68
2021-11-10T18:24:14-6406e09/openbsd-386-68
2021-11-09T19:01:06-81f37a7/openbsd-386-68
2021-11-08T21:28:37-ccea0b2/openbsd-386-68
2021-11-04T21:52:36-8ad0a7e/openbsd-386-68
From the variety of failures — and the fact that some are on openbsd-amd64-n1, which was not believed to be affected by the memory-corruption bug — this looks like a bug in os.RemoveAll on OpenBSD.

That leaves commit 3c6a5cdb as the most recent failure on the main branch, and that was almost a year ago. I suspect this may be fixed at head.