How to set receive_timeout, connect_timeout and send_timeout while connecting using ODBC.

How to set receive_timeout, connect_timeout and send_timeout while connecting using ODBC. I am getting this error message while querying the clickhouse using ODBC.
ERROR:  HY000:Timeout:

You can just provide needed parameters in the connection string
# ~/.odbc.ini

[ClickHouse]

url = http://default:password@localhost:8123/query?database=default&receive_timeout=1234567&connect_timeout=567890

OR: you change the setting for the profile used by the database user (in users.xml on the server).
BTW: ODBC works via HTTP protocol so probably you need to change http_connection_timeout / http_send_timeout / http_receive_timeout (unless you're trying to agjust some interserver in-cluster timeouts).

I used this connection string
Driver={/usr/lib/libclickhouseodbc.so};
url=http://:@
<IP_ADDRESS>:8123/query?database=db&max_result_bytes=14000000&buffer_size=3000000;http_connection_timeout=10000;http_send_timeout=10000;http_receive_timeout=10000
But still getting the same timeout error.
On Wed, May 29, 2019 at 7:26 AM filimonov<EMAIL_ADDRESS>wrote:

You can just provide needed parameters in the connection string
~/.odbc.ini
[ClickHouse]
url = http://default:password@localhost:8123/query?database=default&receive_timeout=1234567&connect_timeout=567890
OR: you change the setting for the profile used by the database user
(in users.xml on the server).
BTW: ODBC works via HTTP protocol so probably you need to change
http_connection_timeout / http_send_timeout / http_receive_timeout
(unless you're trying to agjust some interserver in-cluster timeouts).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yandex/clickhouse-odbc/issues/175?email_source=notifications&email_token=AA3NF4T2MYFJQNLBCTSXH7TPXZZAFA5CNFSM4HOULWL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWPFBVI#issuecomment-496914645,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3NF4XFM4U3NBELZE3DFJTPXZZAFANCNFSM4HOULWLQ
.

--
Ibrar Ahmed

Please try like that:

http://default:@<IP_ADDRESS>:8123/query?database=db&max_result_bytes=14000000&buffer_size=3000000&http_connection_timeout=10000&http_send_timeout=10000&http_receive_timeout=10000

Can you give more details? Can we reproduce the problem for example with isql?

ODBC config have one option for all timeouts used in http connection to clickhouse server:
timeout=123
Sample updated: https://github.com/yandex/clickhouse-odbc/blob/master/driver/odbc.ini#L30
http_connection_* options passed in url will be used by clickhouse server for other http connections, but not for driver<->clickhouse connection.

Hi,
This timeout error is random, here is the isql example.
SQL> SELECT l_orderkey, l_extendedprice, l_discount FROM db.lineitem WHERE
((l_shipdate > '1995-03-22'));
[S1000]Timeout:
[ISQL]ERROR: Could not SQLExecute
SQL>
After the second run.
SQL> SELECT l_orderkey, l_extendedprice, l_discount FROM db.lineitem WHERE
((l_shipdate > '1995-03-22'));
...
...
...
| 36868     | 26148          | 0.04      |
| 36868     | 9494.95        | 0         |
+-----------+----------------+-----------+
SQLRowCount returns 32084
32084 rows fetched
SQL> select count(*) from db.lineitem;
+--------+
| count()|
+--------+
| 60175  |
+--------+
SQLRowCount returns 1
1 rows fetched
CREATE TABLE lineitem (
    l_orderkey BIGINT,

    l_partkey INTEGER,

    l_suppkey INTEGER,

    l_linenumber INTEGER,

    l_quantity float,

    l_extendedprice float,

    l_discount float,

    l_tax float,

    l_returnflag VARCHAR,

    l_linestatus VARCHAR,

    l_shipdate DATE,

    l_commitdate DATE,

    l_receiptdate DATE,

    l_shipinstruct VARCHAR,

    l_shipmode VARCHAR,

    l_comment VARCHAR

) ENGINE = MergeTree PARTITION BY l_orderkey ORDER BY tuple();
On Thu, May 30, 2019 at 1:26 AM filimonov<EMAIL_ADDRESS>wrote:

Please try like that:

http://default:@<IP_ADDRESS>:8123/query?database=db&max_result_bytes=14000000&buffer_size=3000000&http_connection_timeout=10000&http_send_timeout=10000&http_receive_timeout=10000

Can you give more details? Can we reproduce the problem for example
with isql?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yandex/clickhouse-odbc/issues/175?email_source=notifications&email_token=AA3NF4SDLSOZDKXOBYKZQBDPX3RGXA5CNFSM4HOULWL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQRLDQ#issuecomment-497096078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3NF4XHQMETIZ6FHDLOZ2DPX3RGXANCNFSM4HOULWLQ
.

--
Ibrar Ahmed

I Still get timeout error when using php-odbc and this driver.
The problem is that when query response time is more than 30 seconds. It get timeout erro or in case of isql from unix-odbc we  get HTTP status code: 400
I does not have any problem with loer response times..
Please help. This is a blocking issue that prevents using odbc driver

@dashtimehran clickhouse have MySQL wire protocol support
https://clickhouse.tech/docs/en/operations/server-configuration-parameters/settings/#server_configuration_parameters-mysql_port
so you can try to switch from php-odbc to  PDO / MySQL / mysqli extension


Fix localization issues second attempt

@CGNonofr awesome, when do you sleep? I have one further request: Can you export interfaces AvailableLanguage and LocalizationOptions from @codingame/monaco-vscode-localization-service-override because this is part of the exposed getServiceOverride, but you can't import the type. I externalized the "default" function and it is nicer if it can have a specific type. Thank you.

@CGNonofr awesome, when do you sleep? I have one further request: Can you export interfaces AvailableLanguage and LocalizationOptions from @codingame/monaco-vscode-localization-service-override because this is part of the exposed getServiceOverride, but one can't import the type. I externalized the "default" function and it is nicer if it can have a specific type. Thank you.

sure! 87a8fa6e987ae8a01240a01ff20d21f7e4434866


Light entity update rate

HA Client version: [Main menu -> About HA Client] 0.8.4
Home Assistant version: 0.108.6
Device name: SM-G955F
Android version: 9
Description
I have few of Yeelight RGB bulbs. These are known to have an update rate limit at 60 per minut.
It looks like this app updates new state even while dragging the sliders for brightness and white temperature, so if I move the slider slowly from left to right to increase the brightness or temperature to my desired value, it updates the state too quickly, causing the bulb to become unavailable.
I would recommend to update the state only once after the slider is released at the desired position.
Screenshots
[Replace with screenshots]

Thanks for the report. I noticed this issue but didn't know it will cause such a big issue.

No problem, thanks for your support. Yea, I guess for most other lights this won't be an issue, since HA can handle it just fine, unfortunatelly these Yeelights present an issue with a lot of other things aswell in HA.

Fixed in 0.8.5


write method not found

Code snippet:

The code snippet shown above returns the following error:

open returns a Result, you need to handle the potential error or call unwrap on it. I suggest giving the Rust book a read it you haven't already.


HBASE-24574 Procedure V2 - Distributed WAL Splitting => LOGGING

hbase-server/src/main/java/org/apache/hadoop/hbase/master/SplitLogManager.java
Don't register as a chore on construction if no coordination state
manager instance (there is no instance when procv2 WAL splitter).
hbase-server/src/main/java/org/apache/hadoop/hbase/master/SplitWALManager.java
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
Edit logs.
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/RegionRemoteProcedureBase.java
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/RegionTransitionProcedure.java
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/SplitWALProcedure.java
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/SplitWALRemoteProcedure.java
Add proc name rather than rely on default behavior. Add detail to the
toString.
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
Factoring
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/AbstractFSWAL.java
Print the maxLogs... we don't do it any where.
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WAL.java
Utility method to strip prefix from wal path.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 13s
branch-2 passed

+1 :green_heart:
checkstyle
1m 19s
branch-2 passed

+1 :green_heart:
spotbugs
2m 14s
branch-2 passed

_ Patch Compile Tests _

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

-0 :warning:
checkstyle
1m 19s
hbase-server: The patch generated 1 new + 90 unchanged - 2 fixed = 91 total (was 92)

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

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

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

_ Other Tests _

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

38m 26s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / c49df36e85

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

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

modules
C: hbase-server U: hbase-server

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

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

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
branch-2 passed

+1 :green_heart:
compile
1m  5s
branch-2 passed

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

-0 :warning:
javadoc
0m 41s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
123m 41s
hbase-server in the patch passed.

149m 35s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / c49df36e85

Default Java
2020-01-14

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

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 10s
branch-2 passed

+1 :green_heart:
compile
1m  2s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 38s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
201m  6s
hbase-server in the patch passed.

225m 50s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / c49df36e85

Default Java
1.8.0_232

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 13s
branch-2 passed

+1 :green_heart:
checkstyle
1m 25s
branch-2 passed

+1 :green_heart:
spotbugs
2m 32s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
checkstyle
1m 25s
hbase-server: The patch generated 0 new + 85 unchanged - 2 fixed = 85 total (was 87)

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

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

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

_ Other Tests _

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

37m 14s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e202c98fb0

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

modules
C: hbase-server U: hbase-server

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

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

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 11s
branch-2 passed

+1 :green_heart:
compile
1m  4s
branch-2 passed

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

-0 :warning:
javadoc
0m 42s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
122m 11s
hbase-server in the patch passed.

148m  9s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e202c98fb0

Default Java
2020-01-14

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

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 37s
branch-2 passed

+1 :green_heart:
compile
0m 55s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 38s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
132m 12s
hbase-server in the patch passed.

154m 58s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e202c98fb0

Default Java
1.8.0_232

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 40s
branch-2 passed

+1 :green_heart:
checkstyle
1m 11s
branch-2 passed

+1 :green_heart:
spotbugs
1m 56s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
checkstyle
1m  8s
hbase-server: The patch generated 0 new + 85 unchanged - 2 fixed = 85 total (was 87)

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

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

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

_ Other Tests _

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

32m 56s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 812d1e2bb5

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

modules
C: hbase-server U: hbase-server

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

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

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
branch-2 passed

+1 :green_heart:
compile
0m 59s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 39s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

237m 34s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 812d1e2bb5

Default Java
1.8.0_232

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


Add depsolving and package search to cloudapi

This pull request includes:

[X] adequate testing for the new functionality or fixed issue
[x] adequate documentation informing people about the change such as

[ ] submit a PR for the READMEs listed here
[ ] submit a PR for the osbuild.org website repository if this PR changed any behavior not covered by the automatically updated READMEs

Note, this builds on the depsolving PR so I've closed it in favor of this one. Last 2 commits are package search and the previous ones lay the groundwork and implement depsolve.

So, the correct approach should be for the server to enqueue the DepsolveJob and use its result.

What's the benefit of doing that? We already have the solver available in the server.

So, the correct approach should be for the server to enqueue the DepsolveJob and use its result.

What's the benefit of doing that? We already have the solver available in the server.

I can think of these:

To maintain reasonable architecture of Cloud API and not taint it with how things used to be done in Weldr API (which made a lot of assumptions of everything running on the same host).
To enable the SaaS version, eventually take advantage of any functionality you'll add (e.g., the package search).
The fact that the solver and the worker are on the same host as the API server in the on-prem scenario is an implementation detail in this case.


The pole extraction

Dear Alexander,
Recently, I have been working with your code, "Long-Term Urban Vehicle Localization Using Pole Landmarks Extracted from 3-D Lidar Scans." While running python ncltpole.py, I visualized the pole detection results and noticed that there are a considerable number of redundant and inaccurate bounding boxes.
Where do you think the issue might be? Do you have any suggestions for improving the results?
Looking forward to hearing from you. Thank you so much!
Best regards,

I solved this issue with the torch-CPU version.

I used the wrong cuda.


How to get a pending tx id

Hi @cffls, i'm able to run the example to create and send a tx via blockfrost but I'd like the txid to be returned from context submit_tx. I naively tried tx = context.submit_tx(signed_tx.to_cbor()) but returns None
I made a pr assuming it's that simple but didn't test. please advise if there's a way already.

Hey there, that's a great question!
It turns out that on Cardano you can already calculate the Tx ID directly from the signed transaction!
@cffls has conveniently implemented this for us. Once you've signed the tx you can get the resulting transaction ID as a string simply with tx_id = str(signed_tx.id), even before you've submitted it.
Let me know if that ends up working for you.

Thanks Jarred @astrojarred ! I also answered the question in @34r7h 's pull request: https://github.com/cffls/pycardano/pull/12#issuecomment-1048127334

Oh great! Did not see the PR 😄

thanks, tx_id = str(signed_tx.id) works as suggested


Add support for Forgero Gems

The Forgero Gems are explained in Forgero Gems
Todo:

[x] #18
[ ] #19
[x] #20
[ ] Add Damage enhancing gem
[ ] Add mining speed enhancing gem
[ ] Add durability enhancing gem

Requirements for proper gem support:
Tests:
All of these requires an in-game and/or unit test.
Damage gem

[ ] Applying a level 1 damage gem to a tool part should increase the damage of the tool by the amount specified by the gem.
[ ] Test all levels of gems with a weapon and a mob
[ ] Increasing the level of a gem should multiply the effect of the gem by its level.

Durability gem

[ ] Applying a level 1 mining speed gem to a tool part should increase the mining speed of the tool by the amount specified by the gem.
[ ] Increasing the level of a gem should multiply the effect of the gem by its level.

Mining speed gem

[ ] Applying a level 1 durability gem to a tool part should increase the durability of the tool by the amount specified by the gem.
[ ] Increasing the level of a gem should multiply the effect of the gem by its level.
General:

General

[ ] Verify that all gems have been registered into the game
[ ]

Crafting/creating

[ ] Verify all gems can be upgraded to its maximum value
[ ] Verify NBT's are properly created and that the nbt correspond to the gem's level
[ ] Test that Gems can be properly added to tool parts
[ ]

Possible gems to be added:

[ ] Nether star
[ ] Ender pearl


New prop 'defaultValue' for Select

Summary:

New prop defaultValue added to Select component. It has been documented and tested.
Submit value now doesn't have empty spaces between selected options when it is multiple.
Documentation examples updated.

Submit value now doesn't have empty spaces between selected options when it is multiple.

Beware that this change could be patch or major change.

Submit value now doesn't have empty spaces between selected options when it is multiple.

Beware that this change could be patch or major change.

After some research on how form components work in the submit event, empty spaces are not common in how they send their value with the component's name. I agree it may be a Major, but as it stands, the component is in an alpha state, so this type of changes should be expected.

After some research on how form components work in the submit event, empty spaces are not common in how they send their value with the component's name. I agree it may be a Major, but as it stands, the component is in an alpha state, so this type of changes should be expected.

Have we documented this? I think is very important... 🤔

Yes! It's already documented in the prop name. We didn't specify anything about spaces, only separate by commas, so that's another reason for changing it, since it was differing.

I agree, but I was asking wheter we have documented that an alpha component should expect major changes.


Data modeling: each column should have a default value.

{"id":81,"transferType":-1,"amount":100,"note":null,"date":"2020-06-12T02:58:15.594Z","accountID":1,"toAccountID":null,"categoryID":1,"payeeID":null,"createdAt":"2020-06-12T02:59:01.377Z","updatedAt":"2020-06-12T02:59:01.377Z"},
Took the above response from API for example.
This response will cause a bug or needs more work from front-end.

@kekakuka
This is the root cause of the note.text.length.

no, this will no solve the problem.
if default value is set to ''

null.test.length will throw error
''.text.length will throw error too

back-end is not a good place to fix this, the problem is this note.text.length which is not robust.
the solution should be note && note.text ? note.text.length : 0 I believe Sanshi did this update this week.
Besides,
an attribute should be null or a default value?
from business side,
I think if it is optional, it can be null.
from dev side,
it has to be null, for example, toAccoundID is optional, you cannot set a default value to it. 0 or -1 is are not a really good solution.
above all, this issue should be created in front-end repo, the solution is to make the codes more robust, and I strongly disagree with set all attributes with a default value.


Missing dataset / incomplete ipynb

Hi @MalihehIzadi ,
Hope you are all well !
I wanted to test your SoftwareTagRecommender but it sounds like the notebooks are incomplete and the main dataset is missing.
Can you push it so I can test your great work ?
Cheers,
X

Hi @x0rzkov,
Thanks for your interest. Our work is currently under review.
We will include the remaining material when it is accepted for publication which I hope will be soon!


Paramerising "FROM" in Dockerfile

It's alow to build Verdaccio image on custom Node version.

I would prefer this under my control. Otherwise open the door to issues unrelated with Verdaccio. We transpile the code based in some Node.js range. What would be the benefit of allowing this from your point of view?


Request for Safari extension

Please make a Safari version of the Newtube extension, thank you very much!

This has already mention in discord

But I'm trying to figure it.


update MKR address after token upgrade

blog post about token upgrade: https://medium.com/@MakerDAO/mkr-token-upgrade-and-oasis-redeployment-2445482437d6
etherscan link: https://etherscan.io/token/Maker

Great, thanks.  Good point, I'll come back once I have a logo for that.


cataclysm-dda: update locale path patch

Description of changes
The previous sed patch no longer applies; this replaces it with a patch file.
Both of these are solutions for the fact that Nixpkgs Darwin build of CDDA outputs locale files to $out/share/locale, but the game assumes that the locale files are elsewhere on OSX.
This patch applies only to stable, since the patch does not apply on cataclysm-dda's master, and cataclysm-dda-git is broken on Darwin right now.
This is intended as a fix to #186304, but I have no Darwin machine to test it on, so would appreciate someone checking that.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Thank, The patch works in stable version!
But i don't know why git version make broken in darwin, i overrde the latest commit, works, but only english, same as stable.
I don't know how to apply the patch in master, I don't know cpp, can you give me some advice?
https://github.com/CleverRaven/Cataclysm-DDA/blob/master/src/translations.cpp#L62-L71

There are several issues with building the current CDDA master via the Nixpkgs cataclysm-dda-git derivation:

Upstream makefile currently does not install locale files, at least on Linux. I a PR to fix this upstream.

cataclysm-dda-git was failing to build on x86_64-darwin some time ago, so it was marked as broken. I don't know if it builds with current Nixpkgs master.

I don't know if upstream makefile currently installs CDDA properly on Darwin when built via Nixpkgs. There have been some changes.

If all of the above are fixed, and the output tree on Darwin still looks the same, then we might need a patch like this:

patch
diff --git a/src/translations.cpp b/src/translations.cpp
index 875338921e..a70d19b6bb 100644
--- a/src/translations.cpp
+++ b/src/translations.cpp
@@ -59,13 +59,11 @@ std::string locale_dir()
{
 std::string loc_dir = PATH_INFO::langdir();
#if defined(LOCALIZE)
-#if !defined(__ANDROID__) && ((defined(__linux__) || defined(BSD) || (defined(MACOSX) && !defined(TILES))))
 if( !PATH_INFO::base_path().empty() ) {
     loc_dir = PATH_INFO::base_path() + "share/locale";
 } else {
     loc_dir = PATH_INFO::langdir();
 }
-#endif
#endif // LOCALIZE
 return loc_dir;
}

@DeeUnderscore Thank you, in upstream latest commit(07d8e668ff783ab53cfc36239927d81bbb5f1a1e) works！
When all PR merged, we can update  cataclysm-dda-git to latest commit, darwin can unbroken.

On Darwin, I run nix-shell -p nixpkgs-review --run "nixpkgs-review pr 186521" and it looks good for me.


Performance tests ctransformers

@hippalectryon-0 introduced HF text embeddings with #45.
May you - if it fits you well - elaborate how this performs?
Edit: missing embeddings port

Not sure what the benchmark would be though ?

lacking understanding here but this should be seen as a llamacpp port competitor ig... the repo was created a few hours ago so there's still missing a huge chunk. also might support mosaic in the future

Implemented in #transfor.
However there are several drawbacks:

No stop word for now https://github.com/marella/ctransformers/issues/3 leading to very long generated messages
No streaming, therefore we don't see anything until the end of the generation

streaming added now https://github.com/marella/ctransformers/releases/tag/v0.1.2


Add in tutorial and recipes for sparse transfer learning with Ultralytics YOLOv3

Mark, should we also include the new tutorial under the Tutorials section in this README page?
https://github.com/neuralmagic/sparseml/tree/main/integrations/ultralytics-yolov3/README.md

Yes, definitely, good catch Dan


Push plugin does not work on Android 24

Hi,
NativeScript CLI 2.3.0 is going to support Android Build Tools 24.
Currently, if you try to run the sample app with this setup it will crash:
08-29 10:03:51.140  3557  3581 E AndroidRuntime: FATAL EXCEPTION: Thread-193
08-29 10:03:51.140  3557  3581 E AndroidRuntime: Process: org.nativescript.allsdk, PID: 3557
08-29 10:03:51.140  3557  3581 E AndroidRuntime: java.lang.IncompatibleClassChangeError: The method 'java.io.File android.support.v4.content.ContextCompat.getNoBackupFilesDir(android.content.Context)' was expected to be of type virtual but instead was found to be of type direct (declaration of 'com.google.android.gms.iid.zzd' appears in /data/app/org.nativescript.allsdk-1/base.apk)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.google.android.gms.iid.zzd.zzeb(Unknown Source)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.google.android.gms.iid.zzd.<init>(Unknown Source)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.google.android.gms.iid.zzd.<init>(Unknown Source)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.google.android.gms.iid.InstanceID.zza(Unknown Source)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.google.android.gms.iid.InstanceID.getInstance(Unknown Source)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.telerik.pushplugin.ObtainTokenThread.getTokenFromGCM(ObtainTokenThread.java:39)
08-29 10:03:51.140  3557  3581 E AndroidRuntime: 	at com.telerik.pushplugin.ObtainTokenThread.run(ObtainTokenThread.java:31)
08-29 10:03:51.143  1534  2673 W ActivityManager:   Force finishing activity org.nativescript.allsdk/com.tns.NativeScriptActivity
08-29 10:03:51.152  1193  1193 D gralloc : Registering a buffer in the process that created it. This may cause memory ordering problems.

Possible solution - Update Android Support Library from v4 to v7:
https://github.com/NativeScript/push-plugin/tree/master/native-src/android/libs
CC: @AntonDobrev.

Any updates on this @vchimev and @AntonDobrev ? Experiencing this issue myself.

@bnussey A workaround for now is to uninstall the Android Build Tools for level 24 and use a lower version of them.

@AntonDobrev Nothing else we could do about?
I've had removed the build tools for level 24, but that doesn't make any difference at all. The sample app still crashes with the error message. This is what I have installed from the Android SDK:

My TNS configuration:
┌──────────────────┬─────────────────┬────────────────┬───────────────┐ │ Component        │ Current version │ Latest version │ Information   │ │ nativescript     │ 2.3.0           │ 2.3.0          │ Up to date    │ │ tns-core-modules │ 2.3.0           │ 2.3.0          │ Up to date    │ │ tns-android      │ 2.3.0           │ 2.3.0          │ Up to date    │ │ tns-ios          │                 │ 2.3.0          │ Not installed │ └──────────────────┴─────────────────┴────────────────┴───────────────┘
I really need to add this plugin, but I don't want to mess around with my development environment in order to get it running. What about the possible solution (updating the Android Support Library from v4 to v7) mentioned by @vchimev ?

@svzi I believe you need to remove the android platform from the NS project and add it again after the change. You are correct, the workaround is not convenient. I escalated the issue to the plugin collaborators so stay tuned.

@AntonDobrev Damn it, I was so sure that I did that as well, but I just did it again and at least the sample app is working. Thanks for that, I will take some more looks now.

Is error below related to this ticket?
java.lang.IncompatibleClassChangeError: The method 'java.io.File android.support.v4.content.ContextCompat.getNoBackupFilesDir(android.content.Context)' was expected to be of type virtual but instead was found to be of type direct (declaration of 'com.google.android.gms.iid.zzd' appears in /data/app/com.SlateUp.Plunk-1/base.apk)
at com.google.android.gms.iid.zzd.zzeb(Unknown Source)
at com.google.android.gms.iid.zzd.<init>(Unknown Source)
at com.google.android.gms.iid.zzd.<init>(Unknown Source)
at com.google.android.gms.iid.InstanceID.zza(Unknown Source)
at com.google.android.gms.iid.InstanceID.getInstance(Unknown Source)
at com.telerik.pushplugin.ObtainTokenThread.getTokenFromGCM(ObtainTokenThread.java:39)
at com.telerik.pushplugin.ObtainTokenThread.run(ObtainTokenThread.java:31)

Hi, I'm having the same problem, any update on this ticket??

@yairvillarp Uninstalling build tools 24 didn't work for me, I did some patches here https://github.com/manojdcoder/push-plugin made it working. You may give it a try.

Fixed in 0.0.17  just released. Thanks to @manojdcoder for the provided ideas.
If needed:

pull the npm package
in your project: tns platform remove android and then tns platform add android
build


Where is the file 'train.json'

Where is the file 'train.json'

We provide the document for data processing and corresponding scripts on the folder data/, rather than processed data file.
Please download and process the datasets according to the document.
If there are further questions about data processing, please feel free to discuss with us.


enhance(plugin-core): fill in current hierarchy for Move Header

Related to #2238
I wasn't sure about the tests - I couldn't get the integration tests for the MoveHeader.test.ts to progress - it seems like it fails at an assertion that seems to take time and is repeated on the CI until it passes? Is this related to using the old testing utils?
EDIT: I noticed that the tests are failing for the plugin on the CI, I'll have to take a look at that too.
If there are any pointers on how to get this to work, I can have a go at writing a test for this.
https://user-images.githubusercontent.com/9913851/186452753-232d5a03-a904-4f4e-b438-da1c5ed40526.mp4
Commit

[x] make sure your branch names adhere to our branch style
[x] make sure the commit message follows Dendron's commit style
[x] if this pull request is addressing an existing issue, make sure to link this PR to the issue that it is resolving.

NOTE: make sure to read Addressing open issues

Code

[x] code should follow Code Conventions
[x] sticking to existing conventions instead of creating new ones

Tests

[ ] Write Tests
[ ] Confirm existing tests pass
[ ] Confirm manual testing
[ ] Common cases tested
[ ] 1-2 Edge cases tested
[ ] If your tests changes an existing snapshot

[ ] Update the Snapshot

Docs

[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR (NOTE: submit the PR against the dev branch of the dendron-site repo)
[ ] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages

Related to #2238
I wasn't sure about the tests - I couldn't get the integration tests for the MoveHeader.test.ts to progress - it seems like it fails at an assertion that seems to take time and is repeated on the CI until it passes? Is this related to using the old testing utils?
EDIT: I noticed that the tests are failing for the plugin on the CI, I'll have to take a look at that too.
If there are any pointers on how to get this to work, I can have a go at writing a test for this.
Kapture.2022-08-20.at.17.43.05.mp4
Commit
* [x]  make sure your branch names adhere to our [branch style](https://docs.dendron.so/notes/adc39825-77a6-46cf-9c49-2642fcb4248e)

* [x]  make sure the commit message follows Dendron's [commit style](https://docs.dendron.so/notes/QN46JTSWpEkDkr94TJ85w)

* [x]  if this pull request is addressing an existing issue, make sure to link this PR to the issue that it is resolving.

  * NOTE: make sure to read [Addressing open issues](https://docs.dendron.so/notes/adc39825-77a6-46cf-9c49-2642fcb4248e)

Code
* [x]  code should follow [Code Conventions](https://docs.dendron.so/notes/773e0b5a-510f-4c21-acf4-2d1ab3ed741e)

* [x]  sticking to existing conventions instead of creating new ones

Tests
* [ ]  [Write Tests](https://docs.dendron.so/notes/99q7A73uGmCwu2KvSHZro)

* [ ]  [Confirm existing tests pass](https://docs.dendron.so/notes/99q7A73uGmCwu2KvSHZro)

* [ ]  [Confirm manual testing](https://docs.dendron.so/notes/99q7A73uGmCwu2KvSHZro)

* [ ]  Common cases tested

* [ ]  1-2 Edge cases tested

* [ ]  If your tests changes an existing [snapshot](https://docs.dendron.so/notes/99q7A73uGmCwu2KvSHZro)

  * [ ]  [Update the Snapshot](https://docs.dendron.so/notes/u7utw5w8gyacuh3ok9ehi8j)

Docs
* ~[ ] if your change reflects documentation changes, also submit a PR to [dendron-site](https://github.com/dendronhq/dendron-site) and mention the doc PR link in your current PR (NOTE: submit the PR against the `dev` branch of the dendron-site repo)~

* ~[ ] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in [Development](https://wiki.dendron.so/notes/ce9b9b29-d85b-492b-b76d-5e0c5dc52b03) or [Packages](https://wiki.dendron.so/notes/ok9ifke0zsfxnnh7xog79z5)~

yeah, this is due to moveheader being on the old test harness. the easiest way to fix the error is to stub getInitialValueFromOpenEditor
see stubs
[[dendron://dendron.docs/dev.process.qa.test.cook.stubbing]]
notePickerStub = sinon.stub(NotePickerUtils, 'getInitialValueFromOpenEditor')

you should be able to test that this is set correctly using the spy interface
expect(notePickerStub.calledWith(...)).toBeTruthy()

Thanks, I'll try and take a look some time this week

Thanks for the tip! I ended up removing the initialValue property from CommandInputas it should be no longer used as the initialValue is taken from the open editor. It has been removed from the tests in favour of stubbing the values instead.
I did think it was a bit strange to be checking based on initial value, whereas it would probably be ideal if the tests were also able to input new characters for the destination instead... but I couldn't figure out a way to do this easily.
I've just realised that I didn't write an explicit test for the new behaviour, so I'll work on that next chance I get.
Any feedback on the changes so far would be appreciated if you happen to have the time to look 🙇

Thanks for the tip! I ended up removing the initialValue property from CommandInputas it should be no longer used as the initialValue is taken from the open editor. It has been removed from the tests in favour of stubbing the values instead.
I did think it was a bit strange to be checking based on initial value, whereas it would probably be ideal if the tests were also able to input new characters for the destination instead... but I couldn't figure out a way to do this easily.
I've just realised that I didn't write an explicit test for the new behaviour, so I'll work on that next chance I get. Any feedback on the changes so far would be appreciated if you happen to have the time to look 🙇

this looks good. for testing this case without stubbing, you can open the current note by following the example here

The code was already opening the origin note in the onInitFuncdefined in the "WHEN header is selected" describe block's beforeEach function.
I've updated this to use WSUtilsV2 instead of the previous deprecated version. I've used this to check that the new test will be prefilled with the origin note's fname when MoveHeaderCommand's gatherInputs is called.
However, I was wondering for the other tests, is there a way to open the prompt and then type in the new text for the destination? I thought that would be a more accurate representation for the flow a user would go through when using the command. I couldn't quite figure out how to achieve this, though.
Or is this something that we don't use within the integration tests? If not, then maybe the PR is ready to have a look at in its current state (if the CI tests pass).

got i

Thanks, the code was already opening the origin note in the onInitFunc defined in the "WHEN header is selected" describe block's beforeEach function.
I've updated this to use WSUtilsV2 instead of the previous deprecated version. I've used this to check that the new test will be prefilled with the origin note's fname when MoveHeaderCommand's gatherInputs is called.
However, I was wondering for the other tests, is there a way to open the prompt and then type in the new text for the destination? I thought that would be a more accurate representation for the flow a user would go through when using the command. I couldn't quite figure out how to achieve this, though.
Or is this something that we don't use within the integration tests? If not, then maybe the PR is ready to have a look at in its current state (if the CI tests pass).
EDIT: The integration tests and other tests pass locally (on MacOS, node v16.15.1), so I'm not sure what's happening with the CI tests - is this normal?

got it - you're good then! we currently have a few flaky tests that @jonathanyeung will be squashing the coming weeks so your code is good to merge! thanks for PR :)


⚠ Samsung has degraded performance

In 90b0133, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2456 ms

Resolved: Samsung performance has improved in 0969186.


[ko] Fix wrong link in assign-pod-node.md

This is a Bug Report

Problem: In scheduling-eviction/assign-pod-node korean page, there is worng link related to labels-annotations-taints.
Proposed Solution:
Change link [잘 알려진 레이블, 어노테이션 및 테인트](/docs/reference/labels-annotations-taints/) to [잘 알려진 레이블, 어노테이션 및 테인트](/ko/docs/reference/labels-annotations-taints/) on assign-pod-node.md
Page to Update:
https://kubernetes.io/ko/docs/concepts/scheduling-eviction/assign-pod-node

Note
Set base brach Korean Team working branch!

Currently the working branch of Korean Team is dev-1.21-ko.7.

/language ko

/triage accepted

/assign

Is anyone working on it? If no, then I would like to work on it.

/assign


[CI] check genesis blob in commit verify

Motivation
Check the genensis blob consistenchy as part of commit verify.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
To be canaried in CricleCI commit verify flow.

I like it even though its draft, feel free to use r=andll when you choose to land it
@bors-libra delegate+

:v: @sausagee can now approve this pull request

@bors-libra  r=andll

:pushpin: Commit 01bed09 has been approved by andll

:hourglass: Testing commit 01bed096f0403abd800edb3a0049ea8689cdb187 with merge 357ca5bc9239900d08f7dfac2ae61c57574bc234...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: andll
Pushing 357ca5bc9239900d08f7dfac2ae61c57574bc234 to master...


add AES-GCM and the various AES-CBC algorithms to KeyVault Keys

These seem to be only supported in Managed HSM

Looks like this is already done via #13092