M1芯片的Mac启动ResourceManager失败

请问有可能的解决思路吗，日志没有看到报错，尝试手动安装hadoop启动也同样失败，应该不是脚本之类的问题

这是启动后的集群节点情况

./run-wordcount.sh 3.3.1
运行测试脚本一直报错
m1芯片 按照标准的方式安装的
http://localhost:8088/ web也连接不上
大佬有解决方案吗
2022-10-10 13:49:26,978 INFO client.DefaultNoHARMFailoverProxyProvider: Connecting to ResourceManager at hadoop-slave2/<IP_ADDRESS>:8032
2022-10-10 13:49:28,136 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:29,138 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:30,143 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:31,146 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:32,153 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:33,158 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:34,160 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:35,166 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:36,169 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:37,173 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:38,190 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:39,194 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:40,199 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:41,201 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:42,205 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:43,207 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:44,208 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:45,210 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:46,215 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:47,216 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2022-10-10 13:49:47,219 INFO retry.RetryInvocationHandler: java.net.ConnectException: Call From hadoop-master/<IP_ADDRESS> to hadoop-slave2:8032 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused, while invoking ApplicationClientProtocolPBClientImpl.getNewApplication over null after 1 failover attempts. Trying to failover after sleeping for 24469ms.
^C
input file1.txt:
Hello Hadoop
input file2.txt:
Hello Docker
wordcount output:

已经修复了，是配置文件yarn-site.xml出了问题，你再试试看

感谢～调试通过了。问题原因确实是出在内存不够，将reourcemanager、namenode、secondarynamenode放在不同节点要好一些。另外还有一个原因是我本地docker的安装环境是用colima代替docker for desktop，colima划分内存默认是2G，不足以支持hadoop集群，使用 colima --memory 4g start 命令重新启动后就没问题了

./run-wordcount.sh 3.3.1 运行测试脚本一直报错
m1芯片 按照标准的方式安装的
http://localhost:8088/ web也连接不上 大佬有解决方案吗
2022-10-10 13:49:26,978 INFO client.DefaultNoHARMFailoverProxyProvider: Connecting to ResourceManager at hadoop-slave2/<IP_ADDRESS>:8032 2022-10-10 13:49:28,136 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:29,138 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:30,143 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:31,146 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:32,153 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:33,158 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:34,160 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:35,166 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:36,169 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:37,173 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:38,190 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:39,194 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:40,199 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:41,201 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:42,205 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:43,207 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:44,208 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:45,210 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:46,215 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:47,216 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:47,219 INFO retry.RetryInvocationHandler: java.net.ConnectException: Call From hadoop-master/<IP_ADDRESS> to hadoop-slave2:8032 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused, while invoking ApplicationClientProtocolPBClientImpl.getNewApplication over null after 1 failover attempts. Trying to failover after sleeping for 24469ms. ^C input file1.txt: Hello Hadoop
input file2.txt: Hello Docker
wordcount output:

你好，如果集群运行正常的话不妨看一下是不是因为 mac 本身限制与docker桥接模式访问的原因，这个问题的解决方法我在我填坑博客的 #bug3 也有记录，有兴趣可以看下

./run-wordcount.sh 3.3.1 运行测试脚本一直报错
m1芯片 按照标准的方式安装的
http://localhost:8088/ web也连接不上 大佬有解决方案吗
2022-10-10 13:49:26,978 INFO client.DefaultNoHARMFailoverProxyProvider: Connecting to ResourceManager at hadoop-slave2/<IP_ADDRESS>:8032 2022-10-10 13:49:28,136 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:29,138 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:30,143 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:31,146 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:32,153 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:33,158 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:34,160 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:35,166 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:36,169 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:37,173 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:38,190 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:39,194 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:40,199 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:41,201 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:42,205 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:43,207 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:44,208 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:45,210 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:46,215 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:47,216 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 2022-10-10 13:49:47,219 INFO retry.RetryInvocationHandler: java.net.ConnectException: Call From hadoop-master/<IP_ADDRESS> to hadoop-slave2:8032 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused, while invoking ApplicationClientProtocolPBClientImpl.getNewApplication over null after 1 failover attempts. Trying to failover after sleeping for 24469ms. ^C input file1.txt: Hello Hadoop
input file2.txt: Hello Docker
wordcount output:

你好，如果集群运行正常的话不妨看一下是不是因为 mac 本身限制与docker桥接模式访问的原因，这个问题的解决方法我在我填坑博客的 #bug3 也有记录，有兴趣可以看下

您好，我的报错也是类似，已经根据您说的正确配置了，也能ping通<IP_ADDRESS>，但是还是不行，我看了下jps服务，请问您是如何解决的？我看了下我用的也是最新的xml
ifconfig
eth0      Link encap:Ethernet  HWaddr 02:42:ac:12:00:04
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7733 (7.7 KB)  TX bytes:6899 (6.8 KB)
lo        Link encap:Local Loopback
inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1650 (1.6 KB)  TX bytes:1650 (1.6 KB)
jps
96 DataNode
321 Jps
223 NodeManager

2023-03-21 04:24:43,689 INFO client.DefaultNoHARMFailoverProxyProvider: Connecting to ResourceManager at hadoop-slave2/<IP_ADDRESS>:8032
2023-03-21 04:24:44,839 INFO ipc.Client: Retrying connect to server: hadoop-slave2/<IP_ADDRESS>:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)

到slave2再运行一次start把没开的服务打开就好了，但是不知道为什么启动的时候没有一起开呢？
root@hadoop-slave2:~# ./start-hadoop.sh Starting namenodes on [hadoop-master] hadoop-master: namenode is running as process 255.  Stop it first and ensure /tmp/hadoop-root-namenode.pid file is empty before retry. Starting datanodes hadoop-master: datanode is running as process 423.  Stop it first and ensure /tmp/hadoop-root-datanode.pid file is empty before retry. hadoop-slave1: datanode is running as process 96.  Stop it first and ensure /tmp/hadoop-root-datanode.pid file is empty before retry. hadoop-slave2: datanode is running as process 95.  Stop it first and ensure /tmp/hadoop-root-datanode.pid file is empty before retry. Starting secondary namenodes [hadoop-slave2] Starting resourcemanager Starting nodemanagers hadoop-master: nodemanager is running as process 1019.  Stop it first and ensure /tmp/hadoop-root-nodemanager.pid file is empty before retry. hadoop-slave1: nodemanager is running as process 215.  Stop it first and ensure /tmp/hadoop-root-nodemanager.pid file is empty before retry. hadoop-slave2: nodemanager is running as process 214.  Stop it first and ensure /tmp/hadoop-root-nodemanager.pid file is empty before retry.

可以看一下机器的内存情况，可能内存不够，导致节点进程关闭，建议使用 16G 内存的设备
…

M1pro 16GB,也没有开其他高负荷的程序，我再看看是不是有其他问题，感谢


Javascript File Inference problem with Telerik Kendo files

This is one example of files from Telerik Kendo that results in a "javascript inference problem". This file was included in another file, and not even opened by me, when the error showed up in Brackets.
It's a local file on my computer, but I guess you can find them at Teleriks site. The error message from Bracket asks me to provide a copy of the file, but only image files are allowed to attach here. I tried to add the javascript.

@andreas1974 I downloaded Kendo version 2014.3.1316, opened the whole 'js' folder in Brackets, and then opened the file above -- didn't get any error message.  That suggests this may be a false alarm.  If your system was bogged down with other tasks at the time, processing this file could have taken long enough to trigger the timeout warning even with nothing wrong.
Does it happen every time you're working on this project?  If so, try increasing the jscodehints.inferenceTimeout preference (default is 30000, i.e. 30 seconds).  If you raise the limit to 60 or 90 seconds, does the error go away?

I'm no longer using Brackets.
But thanks for trying to help.


[Feature] Add nodejs game lib

The game lib will hold properties and utilities to handle logic related to the game itself. It will be used to handle re-usable back-end and front-end lib logic and will be shared in any possible libs later.
update
Here are some key properties in regards to general game properties:

How many planes are flying at a time?

4, 1 from each of the 4 squadrons

How many planes on each side?

6 in total between the 2 squadrons on 1 side.

How many cards?

Normal plane = 4
“Ace” = 6
“Double Ace” = 8

How to move?

2 dice rolls, 1 for each plane “in flight”.

How big is the board?

12x12 (90% sure about this)
The 4 corners are not available, as its where the "hanger" is on the board.

Partially added with #6


Create example code in Node.js for reading DynamoDB Streams

Create one ore more example files of reading items off a DynamoDB Streams. Place the files in:
Node.js/WorkingWithStreams directory

Issue is closed


Make override list not look horrible

Took at stab at this over at https://github.com/peschkaj/multirust-rs/commit/eb4c973a7444259dd094bde2ab1ebca9ea9c99fd
To speed up review, current output looks like this on Windows:
TOOLCHAIN               TARGET
--------------------    ----------------------------------------
nightly-x86_64-msvc     \\?\D:\src\peschkaj\coreutils
nightly-x86_64-msvc     \\?\D:\src\peschkaj\flaker
nightly-x86_64-msvc     \\?\D:\src\peschkaj\multirust-rs
nightly-x86_64-msvc     \\?\D:\src\peschkaj\todo
stable-msvc             \\?\D:\src\test-rustup

The \\?\ isn't the prettiest thing on earth, but I wanted to get a :+1: or :-1: on the general output before attempting to format the string.

Thanks for taking this @peschkaj.
It looks great. I think though that I expect the paths to be in the first column, the toolchain in the second. Is that easy to do?
Also can you rename TARGET to PATH since 'target' already means 'target triple'?
My only reservation here is about the column headers. None of the other list commands have that (they also only have one column).
If you tackle fixing the display paths on windows you might grep the source for the two occurrances of of the word UNC where I've noted this same problem and fix them all.

I think though that I expect the paths to be in the first column, the toolchain in the second. Is that easy to do?

Very easy and I'll get on it.

Also can you rename TARGET to PATH since 'target' already means 'target triple'?
My only reservation here is about the column headers. None of the other list commands have that (they also only have one column).

Changing TARGET to PATH is easy enough to do. But in light of your second statement, I'll remove the header altogether. If we opt to add a header later, it's an easy enough change to make down the road.
I'll create a separate issue to clean up UNC paths just so there's a clean history.

Fixed. Thanks @peschkaj!


Remove transactions from db.saveEvent

Description
The private method persistence.saveEvent should not run in a transaction since it's usually run from within a transaction because transactions cannot be nested in MySQL, so either we are commiting too early or golang is just ignore the nest.
The public method persistence.SaveEvent should have the transaction instead.
AC

[ ] Remove transaction from persistence.saveEvent
[ ] Add transaction to persistence.saveEvent
[ ] Update unit tests.

Was done


Branding: Different assets for icon and presplash

Pass icon foreground and background assets to p4a so an adaptive icon is
created.
Also adjust the presplash background color to Endless orange.
https://phabricator.endlessm.com/T33593

@danigm thanks for the review. Next time please use the "merge & squash" option in github so we keep our git history clean.


Phpiredis support

It would be great to have a phpiredis support out of the box.
You can override ConnectionFactory and use phpiredis adapters, but the ConnectionFactory class overrides only if logger is enabled.

Has anything happened with this one? Is there a solution for using phpiredis with snc_redis?
I expected to find a connections configuration as in predis's documentation:
$client = new Predis\Client('tcp://<IP_ADDRESS>', array(
    'connections' => array(
        'tcp'  => 'Predis\Connection\PhpiredisStreamConnection',
        'unix' => 'Predis\Connection\PhpiredisSocketConnection',
    ),
));

But the current configuration doesn't support changing the connection.

I never used phpiredis, is the performance better than phpredis?

@zaiddabaeen you can override connection_factory
class ConnectionFactory extends BaseConnectionFactory
{
    public function __construct()
    {
        if (extension_loaded('phpiredis')) {
            $this->schemes = [
                'tcp' => 'Predis\Connection\PhpiredisStreamConnection',
                'unix' => 'Predis\Connection\PhpiredisStreamConnection',
                'redis' => 'Predis\Connection\PhpiredisStreamConnection',
                'http' => 'Predis\Connection\WebdisConnection',
            ];
        }
    }
}

in config.yaml
snc_redis:
    class:
        connection_factory: AppBundle\Predis\ConnectionFactory

@snc yes, it is. phpiredis uses C client for parsing/serialization

Thanks @enleur I'll try it out.
@snc Check out this performance guide: https://github.com/nrk/predis/blob/master/FAQ.md#speaking-about-performances


nanomq: 0.20.8 → 0.21

Description of changes
https://github.com/nanomq/nanomq/releases
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] 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/)
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.

Result of nixpkgs-review pr 284345 run on x86_64-linux 1

1 package built:

nanomq

Result of nixpkgs-review pr 284345 run on x86_64-darwin 1

1 package built:

nanomq

Result of nixpkgs-review pr 284345 run on x86_64-linux 1

1 package built:

nanomq

I have no idea why local builds is OK on linux/darwin, but CI fails.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3676

0.21.8 addresses CVE-2024-25767
A "pre-release" 0.21.9 also addresses CVE-2024-31040 & CVE-2024-31041, but it's unclear how they treat "pre-releases". Might be better to add a patch for those?

I think the tests might need paho-mqtt 2.x which there are attempts to bump to @ #288219

It does actually look like websocket support might be properly broken - even given an updated paho-mqtt , the websocket functional tests give "connection refused" for everything.
We're going to have to decide whether we want to bump to a possibly partially broken nanomq or mark this with knownVunerabilties


Close method in current-routed-modal service failed on parameterized route

Adding the model of the currentController to the url generation on closing the modal via service fixed the error, which occurred on closing a route with dynamic segments.

@dbbk can you give me any feedback?

Hi @CMH-Benny, thanks for submitting this! I've actually just pushed a release that uses the official routing service and its urlFor method, rather than the private generateURL method. Could you verify if this is still an issue for you?

Hi @dbbk, thanks for the info!
I tried it out and it seems like 0.5.0 is fixing the issue.
Pretty Awesome 👍


Solr API temporary error - Question

A USAID developer reported on March 11 that he received SolrCore 'activity' is not available due to init failure: could not load conf for core activity.. error for multiple Solr API calls. By the time he contacted the IATI Tech Team the API was working.
According to him, this error might be due to backend config changes, I would like to understand why this error occurred, was it due to a deployment?

Not sure, could have been the case, can not replicate atm. Closing.


release 0.2.1 including the new custom interface, pre-processing functions, utility functions

@fabiocat93 - if you want to trigger releases using auto, i think it the auto workflow needs a major, minor, or patch label in addition to release. it may be that this will require another PR merge to actually make a release.


Add .gitignore for large AWS reserved instance offering file

This keeps the file awsreservationofferings.json out of git, but you still need to add it yourself to the ./configs directory.
Required for https://github.com/kubecost/kubecost-cost-model/pull/539

Do you need this to build and run the application though? I think we should leave this in for build automation and simplicity even if it increases the size of the git repo?

The file is too big, so GH won't let me push it.

We either need to do this (https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage) or, preferably, thin out all the stuff we don't need from that file and compress it so that we can just add to git.

@nikovacevic I think for now we can roll a compressed version. I'm retaining a master file with data for all of the offering permutations, but since the current implementation of RI recommendations disregards tenancy type, offering class, and a bunch of other things, I built a version that's just a bunch of key:value pairs of:
{ "<region>/<instanceType>": lowestHourlyCostReservationForThatRegionAndInstanceTypePair }
Still something to thing about because ofc as we start leveraging more information in the recommendation, the data needed will grow.

Closing this because the file size was reduced and file is added in https://github.com/kubecost/cost-model/pull/949


Morse decoder

Hi @lucascomamala and @dialite,
While you made a great effort in this project, I cannot proceed to review your code.
Invalid Code Review Request
Your PR has no description and your readme is not descriptive. Kindly update your readme using the template.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


tests: drivers: uart: uart_async_api: Rework to allow testing of multiple instances

Test is using a single instance but Nordic has SoCs which has UART instances that are a bit different and we would like to test multiple of them in the test.
Reworked the test to have an array of DUT instances with only one currently added.
Due to userspace setup test is using the approach where each test is in separate suite so it is not that obvious how to may it mutli-instance and maybe there is a better way than I took.

We can also add additional overlays for each UART instance we want to test, and keep the test suite simple, building and running for just one UART. This way, for boards which require a physical connection between RX and TX can reuse the same pins for each UART instance.

@bjarki-andreasen yes we can keep approach with dedicated overlay and configuration in testcase.yaml, but then we are spoiling testcase.yaml and increasing unique files (overlays) that must be maintained. This approach requires also multiple tests to be build&run on same target (impact CI time). We already took that approach here: https://github.com/zephyrproject-rtos/zephyr/blob/ac52bd629d705811858c8bb38ca7a43e4e81182b/tests/drivers/spi/spi_loopback/testcase.yaml#L181 where test for special SPIM120 (fast) was added. A configuration was added for nrf54h20dk/nrf54h20/cpuapp. I don't like this because we would like to test that also on other cores in nrf54h20, nrf54l15 also has fast SPI, maybe more cores in the future will need that. We can end up with dozens of custom overlays and configurations. With multi-instance approach you can still do single-instance + custom overlay if you want to reuse pins. In that particular case (fast peripherals on nrf54h) pins cannot be reused multi-instance approach can be used.

@bjarki-andreasen I will be on 2 weeks vacation and I'll get back to that after that. I've added it here https://github.com/zephyrproject-rtos/zephyr/pull/75462/commits/8d9b93bbcaab03acbcfb24dedea6bceb9784e989 which is a draft PR.

ok, enjoy your vacation :)

I've added an example for using multi-instance test. For nrf54h20dk//cpuapp uart137 and uart120 are tested.
PR contains one commit from #81273 which is needed to make uart120 work without device runtime PM.


[Enhancement] change the order of show materialized view

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

The rows column should be put before the text, because the text usually is pretty long to display.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[x] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_admit_test

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 8 / 9 (88.89%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
1
2
50.00%
[544]

:large_blue_circle:
com/starrocks/sql/ast/ShowMaterializedViewsStmt.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/SchemaTable.java
3
3
100.00%
[]

@Mergifyio backport branch-3.0


New Docker Image gdb-multiarch

Hi,
Not sure this is the place to add this comment but I think the new docker image is missing gdb-multiarch install. I'm not super experienced with Docker but the output of the "latest" tag currently has nothing in "/usr/bin/gdg-multiarch".
Thanks for putting together these tools they've been super helpful!

Hi,
I'm very glad you use these tools and they are helpful to you ☺.
I wanted to keep the SDK container image as small as possible. That's why I threw everything that's not needed for building out of the container. gdb-multiarch is installed in devcontainer which can be used for development.
If you don't use vscode you can create your own image based on raspberry-pi-pico-sdk or modify existing Dockerfile and rebuild image. (instruction here)


Adds flip/mirror slides feature.

This commit adds full support for a new OpenSeaDragon(OSD) feature - Mirror/Flip.
In order to fully support this new feature, the following OSD objects had to be modified:
- drawer.js:
- navigator
- openseadragon
- strings
- tiledImage
- viewer
Additionally, a new flip button was created (similar to the existing ones).
Flip Logic
Whenever the state is flip button is pressed, flip state is toogled, inverting all the controls and displays (the rotation direction is inverted as well).
This means that all viewer coordinates (including user inputs) must me inverted too.
Summary of modifications
- drawer.js: modified _offsetForRotation to invert rotation angle on flipped state. Added a _flip method to scale/mirror canvas context.
- navigator.js: adds full flip support and inverts nagivator inputs.
- openseadragon.js: new buttons, flip state variable and showFlipControl variable.
- strings.js: flip tool help tips.
- tiledImage.js: flips the actual drawing canvas.
- viewer.js: Added keyboardshortcuts to rotate 90degrees (r/R) and flip image (f/F). flip button state is stored here and flip order is set.
The flipped state is stored on viewer object.

Maybe the "flipped" setting should be stored in the viewport, along with the rotation degrees? Any thoughts about viewport vs. viewer on that?

About store flip state on viewport instead of the viewer, I will study its impact later.

Whoops! Sorry I was unclear... I like flipped as the property name. I was just saying that the key handler should just call the doFlip() function, since it's just a copy of the same code.

Just a note: we'll want to update http://openseadragon.github.io/examples/ui-keyboard-navigation/ with the new key commands. The code for that is in the site-build project: https://github.com/openseadragon/site-build/blob/master/www/ui-keyboard-navigation.html

Also, the icon looks a little soft on the button... the anti aliasing is nice, but could it be a little crisper?

Another thought: the flip is only a flip horizontal, not a flip vertical. Looks like you can achieve flip vertical by flipping and then rotating 180, so we probably only need the one flip (better than adding a bunch of special case flip vertical code). Perhaps we should have a flip vertical button, though? What do you think?

@iangilman , a new pull request was submitted on "site-build" with the demanded feature.

@iangilman I think there is no need for another kind of flip. As you said, it can be achieved by flipping and rotating the image but I'm open-mind about that.

Besides the onFlip thing, I think everything's looking good. I'm still interested in your thoughts on storing the value in the viewport so it matches what we're doing in rotation.
I'd also like to hear if you have any thoughts on tests for this new functionality.
Thank you for putting this all together... It's a major new feature!

@iangilman, the flip state is now stored on viewport objects :)
Later, the code can be improved to flip an image with a viewport method like:
this.viewer.viewport.Flip()
A closer look must be taken on controls and keyboard events to study the viability of doing that.
I saw you are currently using QUnit framework to test your code. I will check that out :)

Now that you mention it, yes, this isn't really complete without the ability to flip programmatically! It should basically be the same format as Viewport.setRotation. You can have onFlip in the viewer just call that.
For that matter, it looks like both the button and key version of onFlip take this afterall, so you don't really need onButtonFlip.
Thank you for moving the property into the viewport... I think that's better organization. :)

@iangilman , I think it has finally achieved a production state. Code is much better now =D

As for Viewer having a flipped property, I was thinking we would do something similar to degrees, how you can pass it in when you create the viewer, to give it an initial value. After that, the viewer version is ignored.
To use it, it would look like this:
var viewer = OpenSeadragon({
  flipped: true,
  // More options...
});

console.log(viewer.viewport.getFlip()); // true

Adding this to the code is easy; anything passed into the constructor is automatically added to the viewer. You just need to pass it to the viewport like so:
https://github.com/openseadragon/openseadragon/blob/master/src/viewer.js#L369
...and document its existence like so:
https://github.com/openseadragon/openseadragon/blob/master/src/openseadragon.js#L206
That's what I meant by my comment about documenting the flipped option, by the way, not that showFlipControl needed any more documentation. Sorry I wasn't clear about that!

Theresa is only missing the documentation

I guess it's done :)

What tester error are you finding? The automatic test run seems to have been successful:
https://travis-ci.org/openseadragon/openseadragon/builds/365721957
Did you look into writing tests for this new feature, by the way? It's not required if you don't want to, but it could be good.

Everything else is looking great, by the way, except for that one area. Thank you for your perseverance!

I would like to take a look on that. I never used QUnit or PhantomJS but I can try it.
Which test do you think it should run?

@iangilman, yesterday it was failing due to PhantomJs timeout but this morning it was ok =S
The same happened right now.
>> PhantomJS timed out, possibly due to:
>> - QUnit is not loaded correctly.
>> - A missing QUnit start() call.
>> - Or, a misconfiguration of this task.
Warning: 1 tests completed with 1 failed, 0 skipped, and 0 todo.
0 assertions (in 0ms), passed: 0, failed: 0 Use --force to continue.
Aborted due to warnings.
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.

Great, I'm glad you will look at the tests. I figure you can add your test to the viewport test module:
https://github.com/openseadragon/openseadragon/blob/master/test/modules/viewport.js
Hmm... I'm seeing that test failure as well with the automatic build. Too bad it's not giving more information! We do have some known intermittent test failures: #1373, #1372, #1260. I don't know if it's one of those or something new. You might try isolating the failure to at least see which module it's happening in. One thing to try is running the tests in a browser to compare.

I ran grunt locally and it ended successfully =S

It might be one of those intermittent failures then... as long as we're not introducing new failures with this patch.
The new setFlip looks good, so I think the code is all set. Are you still looking into writing a test for it?

It just passed the test with no new commits o.O

Yes, I restarted the build, and it looks like it's an intermittent failure, so that time it just worked.
The rotation refactoring looks good, and the new tests look good. I think a worthwhile additional test would have to do with the actual math involved... Like if you flip, do things end up in the right locations?

@iangilman I will delay this issue for a few days, maybe 2/3 weeks due to work causes but then I will finish tests.

@nelsonn3c OK, thanks for the update, and thank you for sticking with this (as time allows)! It's a major new feature :-)

@nelsonn3c How's it going? Have you had a chance to take a look at the tests?

Hello @iangilman , I didn't have time for that yet. Just finishing some projects and then I can work on this again :)

OK, sounds good!

I just made a new commit. Please check it for me just to straighten up some logic deviations. Later I will continue.

I also noticed that the expected/result inputs on test conditions are misplaced in a few tests.

@nelsonn3c Looks like you're off to a great start! I think things like expectedCenters are just pre-computed constants that we know to be correct. One approach would be to do the flip and print out what the results are and use those.
I love that you have added flipped versions of tests for all of the test permutations. That said, I'm concerned that including them directly in those tests makes them overly complicated. What would you think about adding separate flipped versions of those tests next to the originals?

@iangilman I was trying to simplify and reuse code but it's not a problem to put that in a separate test.

Do you think there is the need to make some more tests?

@nelsonn3c No, I think this is perfect! I think we're done here... This is an epic patch, with a great new feature! Thank you so much for seeing it through and getting all the details right!

I've announced it (though it won't be released for a bit): https://twitter.com/openseadragon/status/1004770575061929985
Thank you again! 🎉

Thank you too. It is pleasant to help =)

Nice feature! Extremely helpful and wanted!!! Thanks!

It seems like that they are not flipped, when rotation = 0, but they are also flipped, when rotation != 0.

@jetic83 Oh no! Good catch.
@nelsonn3c Is this something you could take a look at?

Hello guys,
I'm in a middle of a important milestone. I can take a look only after 8th July.
Is that ok for you? =)

@nelsonn3c Sure, no problem. Anytime you can get to it would be great!
@jetic83 That said, if you want to tackle it sooner, that works too. Meanwhile, would you mind filing a fresh issue for it so it doesn't get lost?

Hello @iangilman and @jetic83 , it was created a new branch for this?

As far as I know nothing has been done on this new issue. You can create a new pull request for it if you're ready!

I've never user openseadragon in that mode. How do I reproduce this issue?

I think @jetic83 is referring to something like this:
var highsmith = {
    Image: {
        xmlns: "http://schemas.microsoft.com/deepzoom/2008",
        Url: "//openseadragon.github.io/example-images/highsmith/highsmith_files/",
        Format: "jpg",
        Overlap: "2",
        TileSize: "256",
        Size: {
            Width:  "7026",
            Height: "9221"
        }
    }
};

var duomo = {
    Image: {
        xmlns: "http://schemas.microsoft.com/deepzoom/2008",
        Url: "//openseadragon.github.io/example-images/duomo/duomo_files/",
        Format: "jpg",
        Overlap: "2",
        TileSize: "256",
        Size: {
            Width:  "13920",
            Height: "10200"
        }
    }
};

var viewer = OpenSeadragon({
    id: "seadragon-viewer",
    prefixUrl: "//openseadragon.github.io/openseadragon/images/",
    tileSources: [
        {
            x: 0,
            y: 0,
            opacity: 0.5,
            tileSource: duomo
        },
        {
            x: 0,
            y: 0,
            opacity: 0.5,
            tileSource: highsmith
        }
    ]
});

... Which is a little like the Flickr example, but not as complicated. Let me know if you need more pointers.
@jetic83 Are you referring to world rotation or image rotation?

Yes, @iangilman , this is what I mean. Several tilesources overlayed over each other (semi transparent, of course).
When I mean rotation, I mean:
viewer.viewport.setRotation(0);
All degrees exect of 0 flip the overlayed image as well. At 0 degree, the underlying image is flipped, the overlayed image is not.

@jetic83 Excellent, thank you!
@nelsonn3c Hopefully that gives you the info you need?

@nelsonn3c Sounds good :)
BTW, just so I don't forget, the issue filed for this is https://github.com/openseadragon/openseadragon/issues/1498 .

Hello everyone :)
I was looking on this and I thought that, maybe, flipped option should be passed to the TiledImage object instead of the viewport. What do you think @iangilman ?
When we have multiple images, with different flipped states, only images should be flipped, not  the entire viewport and its control inputs.

We currently support rotating either the viewport or the individual images (or both). Seems reasonable that we could do the same for flipping and just add flipping support for images (since it already exists for the viewport). What do you think?

Yes, it seems to be the correct path to take.

I saw now that the opacity prop is causing this problem. If you only use opacity in one of them, you can see it working properly (in the other without opacity). I will look further sooner when time allows.

@nelsonn3c  great, thank you!

Hi @iangilman
Is the mirroring/flipping supported or not yet? How can i mirror my image ?
Thanks in advance

Hi @AsmaAq
It's been in since 2.4.0 I believe...
See
OpenSeadragon.Options.flipped
OpenSeadragon.Options.showFlipControl
Viewport.getFlip()
Viewport.setFlip()
Viewport.toggleFlip()

Yes, OSD supports this already. Unfortunately some plugins do not (e.g. fabricjs overlay).

Great!
Thank you

Here below the code I used to fitBounds to a drawn rectangle on the image but it didnt work when image is ROTATED or FLIPPED.
var viewportPoint = viewer.viewport.pointFromPixel(webPoint);
imagePoint = viewer.viewport.viewportToImageCoordinates(viewportPoint);
var zoomArea = viewer.viewport.imageToViewportRectangle(imagePoint.x, imagePoint.y, width, height);
viewer.viewport.fitBounds(zoomArea);
Note: I think the issue is in imagePoint not in width/height because the code keeps taking the point coordinates when converted according to the main image (not the flipped/rotated one)
Thanks in Advance.
Asma

Yeah, you may need to do some of the conversion yourself. I'm a little unclear on which of those functions take rotation/flipping into account.
It does seem like it's reasonable to expect imageToViewportRectangle to take rotation/flipping into account, so this might be a bug/enhancement, in which case it would be worth filing as a fresh issue.
Any thoughts, @avandecreme, @nelsonn3c?


Ability to Export currently installed packages

Using a simple PersistenceService, i.e. Open/Save Dialog
Provide option to export the current list of installed packages to a packages.config file

@RichiCoder1 can I get you to case your eyes over this? Thanks!

@RichiCoder1 okay, made some changes based on your feedback, let me know what you think

Looks good.

What are your thoughts on something like this:
http://www.c-sharpcorner.com/UploadFile/mahesh/wpf-dropdownbutton-control/
I thought the export button could be overridable, i.e. default would be to create a packages.config file, but it could be selected to export to boxstarter script, or boxstarter url, or chocolatey package.
This would be a future enhancement, not for now, but just something to think about.

I'd be cool with that.

:+1:


Use assertInstanceOf

[x] Is this related to quality assurance?

Use assertInstanceOf instead of assertTrue(is_a()) to provide a better error message and use dedicate assertions.

@Ocramius Something going strange with tests, gonna look closer :(

Yup - https://travis-ci.org/zendframework/zend-expressive/jobs/354261883#L802-L803
@webimpress interesting - that looks totally broken tho

@webimpress Oh, thanks, I didn't notice that :(

Closing as invalid


HELP - How to add relationship with many tables and show the joined tables in datatable

Summary of problem or feature request
I am following the docs but there are no samples on joining two or more tables and display it in datatable. In the query method I use this one
Code snippet of problem
$employments = Employment::join('users', 'employments.user_id', '=', 'users.id')
            ->select(['employments.salary_id', 'users.firstname']);

        return $this->applyScopes($employments);

But gives me an error. I am trying to combine three tables: Users, Employments, Positions

The code looks fine. Maybe try inspecting the ajax response to get a hint on what causes the issue.

@yajra this is my code in EmploymentDataTable.php
<?php

namespace App\DataTables;

use App\User;
use Yajra\DataTables\Services\DataTable;

class EmploymentDataTable extends DataTable
{
    /**
     * Build DataTable class.
     *
     * @return \Yajra\Datatables\Engines\BaseEngine
     */
    public function dataTable()
    {
        return datatables()
            ->eloquent($this->query())
            ->addColumn('action', 'eloquent.tables.users-action');
    }

    /**
     * Get the query object to be processed by dataTables.
     *
     * @return mixed
     */
    public function query()
    {
        //$query = User::has('jobs');
         $employments = Employment::join('users', 'employments.user_id', '=', 'users.id')
            ->select(['employments.salary_id', 'users.firstname']);

        return $this->applyScopes($employments);
    }

    /**
     * Optional method if you want to use html builder.
     *
     * @return \Yajra\Datatables\Html\Builder
     */
    public function html()
    {
        return $this->builder()
                    ->columns($this->getColumns())
                    ->ajax('')
                    ->parameters([
                        'dom'     => 'Bfrtip',
                        'buttons'      => ['export', 'print', 'reset', 'reload'],
                    ]);
    }

    /**
     * Get columns.
     *
     * @return array
     */
    protected function getColumns()
    {
        /*return [
            'user_id',
            'employeer_id',
            'position_id',
            'salary_id',
            'is_first_job',
            'is_course_related',
        ];*/
        return [
            'employments.salary_id',
            'users.firstname',
        ];
    }

    /**
     * Get filename for export.
     *
     * @return string
     */
    protected function filename()
    {
        return 'employments_' . time();
    }
}

and I got this error

my bad. I did not add the namespace of Employment model from the above code but I added it now and got this different error.


ci: Main branch health failure logs

I noticed that we've been having some failures on the Main Branch Health job but the test logs aren't being saved.

Adds the failure() condition so that the save steps are still run when the job fails
Adds pagination tests (not sure why these weren't in here, maybe just forgot when the pagination lib was added)
Some clean up

🛠 Docs Preview Building...

Configuration
{
  "repoOverrides": {
    "apollographql/apollo-ios-dev@main": {
      "remote": {
        "owner": "apollographql",
        "repo": "apollo-ios-dev",
        "branch": "ci/main-branch-health"
      }
    }
  }
}

b4cb12e972ff69ede951d08b3c593dbfaecdb336

Merging without review since this change only affects a nightly build action.


Set CATTLE_URL in start-env also

Corresponding cattle PR for https://github.com/rancher/python-agent/pull/164

LGTM


Make vaults interaction possible

Maybe I'm just missing something...
I'm creating a Vault Extension that is using an "app_secret" token to talk to the network to fetch the secrets. I'd like to be able to store this token locally, and Microsoft.PowerShell.SecretStore looks like a very good candidate for this.
I'm using the following line to get the app_secret (from the module script):
$appSecret = Microsoft.PowerShell.SecretManagement\Get-Secret -Name appSecret -Vault Microsoft.PowerShell.SecretStore
This works when I invoke this code from the cmdlet of my module, but fails to retrieve the secret when it is invoked from the  extension's methods (Get-Secret, GetSecretInfo)
Is this a known issue? Can anybody suggest a workaround?

This is not supported.  You cannot call SecretManagement commands from within an extension vault command that is currently being invoked by SecretManagement.
But if you wanted to use SecretStore, you could call its extension vault commands directly (and not through a recursive SecretManagement call).  For example you could create a function like this:
function Get-SecretTokenFromStore
{
    param (
        [string] $SecretName
    )

    $moduleInstance = Import-Module -Name Microsoft.PowerShell.SecretStore -PassThru
    # Run SecretStore extension vault command using module scope
    & $moduleInstance { Get-Secret -Name $SecretName }
}

The SecretStore extension vault Get-Secret command returns the secret as the same type it was stored as (it does not do any conversions like SecretManagement/Get-Secret command does).  So if the secret was stored as a String type it is returned as that type.
But I am not sure if this is the best way to store your token.  If SecretStore is configured to require and prompt for a password, then it will do that when Get-Secret command is called.  Not sure if that is what you want.  If you turn SecretStore password requirement off, then it is less secure.

Thanks, this is exactly what I was looking for - we want to give our users flexibility, they can make their own decision on where they have to store the root secret for our vault and if they need to protect it with a password.
Using this approach, users are not even limited to storing the root secret in the SecretStore, they can use any other SecretManagement extension.

Though, the answer is not 100% correct, I figured it out, but I see something that I still do not understand. Basically,
`    $moduleInstance = Import-Module -Name Microsoft.PowerShell.SecretStore -PassThru
# Run SecretStore extension vault command using module scope
# The $SecretName is MySecret
$secret = & $moduleInstance { Get-Secret -Name $SecretName }
Write-Host $secret # writes empty string
$secret = & $moduleInstance { Get-Secret -Name MySecret }
Write-Host $secret # writes secret
$secret = & $moduleInstance Get-Secret -Name $SecretName
Write-Host $secret # writes secret

`
What do the brackets around the instance command mean and where I can read on that aspect?

Though, the answer is not 100% correct, I figured it out, but I see something that I still do not understand. Basically,
       # The $SecretName is MySecret         $secret = & $moduleInstance { Get-Secret -Name $SecretName }         Write-Host $secret # writes empty string         $secret = & $moduleInstance { Get-Secret -Name MySecret }         Write-Host $secret # writes secret          $secret = & $moduleInstance Get-Secret -Name $SecretName         Write-Host $secret # writes secret
What do the brackets around the instance command mean and where I can read on that aspect?

All three cases above are essentially the same.  This syntax runs a script block or command in the $moduleInstance scope using the & call operator.  In the first two cases the script block (script between the two brackets) are run in the module scope.  In the last case it is the Get-Secret command that is being run in the module scope.  Since the script block just runs the Get-Secret command, all three versions to the same thing.
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_operators?view=powershell-7.1
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scopes?view=powershell-7.1


Dropdown menu remains open

Bug Report
Steps
Use the Dropdown component.
Expected Result
The dropdown should close.
Actual Result
The drop down menu remains open. Inspection of the source code shows that display: block !important makes up the value of the style attribute when the issue happens.

Version
0.83.0

@phlfvry can you please add more steps and codesandbox example? Then ping me and I will reopen the issue.
For now, I'm going to close it because it's not clear how we can reproduce it.


Additions to the spec

See commit messages for details.

Started work on minimum balance computation. Very much WIP at the moment.
@adinapoli-iohk Will rename the commits before declaring this ready to merge :)

Rebased on develop.

@dcoutts I think this is ready to be merged now, pending your review obviously. @adinapoli-iohk you'll be happy to know I squished all the comments and renamed the single "final boss" commit to include the name of the YouTrack issue.


Experiment Metrics Advisor (developer driven evolution)

As an experiment to confirm that DPG can grow to a meaningful SDK, we want to experiment on Metrics Advisor:

Generate DPG of Metrics Advisor
Grow the SDK to feature equivalence to the current SDK. To confirm feature equivalence, the testsuite needs to be runnable in live.

You may decide to merge this work (as a refactoring), or to keep this work as an experiment that we don't merge.
Expected work is to take the latest Swagger and rebuild the corresponding release.

Start with raw swagger without customization and directives. Assume the swagger is fully reviewed and approved.
Apply customization to converge to existing lib.
Some customization in current lib is not allowed as it is breaking change, we will document it but not do the customization. (e.g. break 1 client to 2 clients after GA is not allowed as it breaks)

Not all REST API is to be covered, target is demonstration and documentation of customization, as well as which is allowed and not allowed in Java.

I checked the APIs of Metrics Advisor and selected some APIs that need to be covered, proposed in below table. My selection is based on below reason. Please take a look and feel free to add/remove the APIs from below table.

Contains APIs in both MetricsAdvisorAdministrationAsyncClient and MetricsAdvisorAsyncClient
Contains all the four methods appeared in swagger:  GET, POST, DELETE, PATCH
Contains create, delete, update and get operations.
Contains both paging and non-paging operation. (I checked there is no long running operation in MetricsAdvisor）

API
Client
Path
Method
Return value

getAlertsByAnomalyAlertingConfiguration
MetricsAdvisorAsyncClient
/enrichment/anomalyDetection/configurations/{configurationId}/anomalies/query
POST
PagedFlux

getAnomalyDetectionConfiguration
MetricsAdvisorAsyncClient
/enrichment/anomalyDetection/configurations/{configurationId}
GET
Mono

updateAnomalyDetectionConfiguration
MetricsAdvisorAsyncClient
/enrichment/anomalyDetection/configurations/{configurationId}
PATCH
Mono

deleteAnomalyDetectionConfiguration
MetricsAdvisorAsyncClient
/enrichment/anomalyDetection/configurations/{configurationId}
DELETE
Mono

createDataSourceCredential
MetricsAdvisorAdministrationAsyncClient
/credentials
POST
Mono

getDataFeed
MetricsAdvisorAdministrationAsyncClient
/dataFeeds/{dataFeedId}
GET
Mono

A quick update on this issue about what are done and TODOs:
What are done:

Swagger README configuration
I removed unused directives now, only directives to support POST on next page remains. (also remain one model MetricsAdvisorErrorCode because next page operation refer to this schema to avoid codegen failure)

Testing the set of APIs in the table.
I reused the existing unit test to verify our grow-up code since we keep the public method signature. I tried for PLAYBACK and LIVE, both tests passed.

Customized Authentication
Authentication part is also verified in LIVE test.

Model Conversion for PagedFlux and Mono
I used the PagedConverter Util rather than the deprecated .mapPage(), because deprecated method has some wrong behavior when iterating PagedIterable and breaks before iteration finished, it can't break in the middle of iteration.
PagedFlux
Mono
Model Conversion is verified using the unit tests as well.

Exception Conversion
Since azure-core already has exception type HttpResponseException with ResponseError, those two types provide more information than MA's customized types. I removed the customized exception conversion in code now. Previously I tried map to customized error for Mono and PagedFlux which proves that if the customer wants to do exception conversion, it's also doable.
But I have not investigate on map error for SyncPoller and PollerFlux. Please let me know if I need to investigate this.

Two client issue
We agreed that modifying swagger is the correct way to generate two clients. For now I did not spend time to modify swagger to update operation_id because we know for sure that updating operation_id can generate two clients. I think this is not our first priority. Our purpose is to test grow up stories for different APIs. So I just create MetricsAdvisorAdministrationClient and related Builder manually and move the APIs we want to test into MetricsAdvisorAdministrationClient.
From @srnagar's comment, it's worthwhile to update swagger, so I will update operation_id in swagger and regenerate again.

I added a README in my experimental project to explain the codes.
https://github.com/haolingdong-msft/metrics-advisor-poc/blob/b6cb5e5f5cfbd5ce60e810fb5b6ee5185c3eb18a/README.md

Add a doc about the process of the experiment: https://github.com/haolingdong-msft/metrics-advisor-poc/blob/master/developer.md

Todo:
Document the grow up story - WIP
Test LRO APIs on other RP
Model convert for SyncPoller and PollerFlux
Test more MA APIs if needed
Add operation_id to swagger to generate two clients - WIP
Customized Exception convert for SyncPoller and PollerFlux?
Adding model conversion utils for PagedFlux/PagedIterable/SyncPoller/PollerFlux in core? -> this one needs to be followed up.

done and reviewed by SDK arch board https://github.com/Azure/autorest.java/blob/main/docs/developer/2022-05-18-dpg-archboard-review.md


Controller 'uiGrid', required by directive 'uiGrid', can't be found!

i updated the ui-grid from
! ui-grid - v3.0.0-RC.18 - 2014-12-09  to  * ui-grid - v3.0.0-rc.19 - 2015-02-11
and i got the error
Error: [$compile:ctreq] Controller 'uiGrid', required by directive 'uiGrid', can't be found!
what am i missing ?

How are you referencing ui-grid? Did you install it with bower?
Check your Network tab, is ui-grid.js being loaded? Can you run angular.module('ui.grid'); successfully?

1.) yes i am refering to ui-grid.
2.) yes i install it with bower.
3.) i can see the ui-grid in the current version in the dev tools
4.) angular.module('ui.grid') run successfully
the only change i did in my project is updating ui-grid version from .18 to .19
i did some tests , and it seems that in fresh project it's work with no problem... i guess i have some conflicts between plugins.

+1
I experience this problem as well. I have a nested grid and I believe this is generated by the directive "uiGrid" in the ui.grid.expandable module.
If I comment the following line (line 13724 in ui-grid.js) the error is gone, the nested grid is shown but I get many other errors along the way.
require: '^uiGrid'

Yea that should probably be ?^uiGrid and it should bails if no parent grid is found. This may be a breaking change from 1.2.x to 1.3.x, possibly.

Try Firefox. The plunker you linked works fine in IE but dies in FF.

I've found setting the priority: of the ui.grid.expandable "uiGrid" directive to a negative number on line 284 of expandable.js is a viable workaround.
The idea being to force angular to run that directive it after the "uiGrid" directive from ui.grid, it seems to solve the problem for Firefox, IE, and Chrome.

Any updates on this, it happens if i used a ng-if tag on a div containing the ui-grid directive.

@devakone Strange, the plunker forks fine for me in FF as well. I'm using v36.0.4. Can you check on your version?

I fixed it by setting the ng-if directive on a parent div!

OK, but I guess what I'm saying is that I'm not finding it necessary to do that to get that plunker to work...

I concur that I can no longer reproduce it on the original plunkr, but @devakone  is right about ng-if breaking it.
Here's a fork of your plunkr with no change other than an ng-if on the div: http://plnkr.co/edit/Xy9o9tXqwu2dQKwIFmCF?p=preview
Breaks on FF 36.0.4 for me; will recheck with addons off and update this post.

Thanks @drmoose, @c0bra that's indeed the behavior I am experiencing.

OK I found it. ngIf runs with priority 600 and the expandable features stacks uiGrid with a directive that runs at 1000: https://github.com/angular-ui/ng-grid/blob/master/src/features/expandable/js/expandable.js#L284


MF-1654 - Fix Topic Parsing in RabbitMQ Broker

What does this do?
Fixes topic parsed when using rabbitmq message broker
Which issue(s) does this PR fix/relate to?
Resolves #1654
List any changes that modify/break current functionality

Instead of using direct exchange in rabbitmq this change implements topic based routing of messages
Parses NATS topic to rabbitmq understandable topic

Have you included tests for your changes?
Yes
Did you document any new/modified functionality?
No
Notes
Possible issue was topic structure difference between NATS and RabbitMQ. The system was initially built with NATS topic configuration. RabbitMQ accepts # as wildcard to match more words (e.g., a routing pattern of "channels.<channel_id>.#" matches any routing keys beginning with "channels.<channel_id>.messages" and "channels.<channel_id>.<any_other_subtopic>").
With this problem I would suggest to change to Topic exchange rather than Direct exchange as currently used. This is because with topic exchange we can even poll messages from all subtopics.
This now brings a challenge when using different brokers based on the wild cards of each broker. This is because nats and rabbitmq use different wildcard to match any topic for instance in nats it it > while in rabbitmq it is #. I suggest we have one main message format used by mainflux then the different brokers reformat the topic when publishing and subscribing or unsubscribing. Another way would be to have every broker have a way to format its message so that other services can call it. For instance during mqtt forwarding and also when parsing URL to topic and subtopic.

Codecov Report

Merging #1655 (468fe59) into master (8a4cc12) will increase coverage by 0.03%.
The diff coverage is 80.00%.

:exclamation: Current head 468fe59 differs from pull request most recent head baa49b6. Consider uploading reports for the commit baa49b6 to get more accurate results

@@            Coverage Diff             @@
##           master    #1655      +/-   ##
==========================================
+ Coverage   68.92%   68.96%   +0.03%
==========================================
  Files         143      138       -5
  Lines       11544    11354     -190
==========================================
- Hits         7957     7830     -127
+ Misses       2886     2830      -56
+ Partials      701      694       -7

Impacted Files
Coverage Δ

pkg/messaging/rabbitmq/pubsub.go
70.73% <50.00%> (ø)

pkg/messaging/rabbitmq/publisher.go
71.42% <87.50%> (+3.00%)
:arrow_up:

things/service.go
65.35% <0.00%> (-0.72%)
:arrow_down:

ws/api/transport.go

ws/api/logging.go

ws/api/endpoints.go

ws/adapter.go

ws/client.go

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adding option to set icmpvsrresponse parameter when creating new virt…

Provides fix for issue #37
Description
Adds ICMPVSResponse parameter which defaults to PASSIVE to match the Netscaler.
Related Issue
#37
How Has This Been Tested?
Tested locally by creating new virtual servers.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

…ual server

Thanks for the addition!


"Go To Tahli" graphics on Andra map are showing as white

When I click the map button in Andra, the "Go" image and the words "To Tahli" display incorrectly. Looks like the map image on the main Glitch site is missing it completely:
http://www.glitchthegame.com/locations/andra/

Fixed before fb1d239


[vcpkg ci] Check for deprecated license identifiers

Fixes https://github.com/microsoft/vcpkg/pull/22946#issuecomment-1030592217

@JackBoosY can you add the reviewed flag so it is seen by the other maintainers?

Ping @BillyONeal for review this PR.

This seems reasonable to me.
Could the message be combined with the one about "missing" licenses into an overall "you should check the license field in these files"?
Is there a good way to test this? I'm concerned about the last time I merged a change like this and put the bot on the floor for a while.

Is there a good way to test this? I'm concerned about the last time I merged a change like this and put the bot on the floor for a while.

Yes, we can change code to trigger the code paths. I one changes vcpkg/.github/workflows/trustedPR.yml one have the problem that you can not test the change

Ping @BillyONeal for reply.

Thanks for your contribution!


[sil-dead-function-elimination] Don't change the fragility of pre-specialized functions

The old code was changing the fragility of some pre-specialized symbols which made them invisible outside of their own object files, which resulted in linking errors.
Fixes radr://problem/28615847

@swift-ci Please smoke test


Updated User Guide and Developer Guide for milestone V1.3

Pull Request Test Coverage Report for Build 440

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.588%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/storage/CsvWriter.java
0
3
0.0%

Totals

Change from base Build 437:
0.0%

Covered Lines:
2865

Relevant Lines:
3387

💛  - Coveralls


Rename "checkpoint frequency" to "checkpoint interval"

"frequency" is the opposite of the intended meaning, so applied the following regular expression to entire code repo:
s/checkpoint( |-|_)frequency/checkpoint\1interval/g
The root 'pytest' and 'pytest test/system' checks pass as before.
Pull Request Checklist

[Y ] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[Y ] Unit tests pass (pytest)
[N ] Were system tests modified? If so did you run these at least 5 times to account for the variation across runs?
[Y ] System tests pass (pytest test/system)
[Y ] Passed code style checking (./style-check.sh)
[N ] You have considered writing a test
[N ] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[N ] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@tdomhan Apologies for the delay: I've changed it to accept either switch with identical behavior, but to print a deprecation warning for '--checkpoint-frequency'.

Looks like you've fallen behind master and will need to merge that in.

@tdomhan @mjpost OK, I believe this is all set: let me know if anything else is needed!

@fhieber How does this look?  It involves a new logger action subclass, but it's now 1) using argparse.SUPPRESS, 2) checking the actual argument object for the deprecated switch use, and 3) printing the warning via the logging system after it's been initialized.


pre-translate not working with github action (Couldn't find any files)

Describe the bug
I want to pre translate a specified Crowdin directory with my configured AI prompt.
The Github action exits with the error Couldn't find any files to Pre-Translate in the current project
To Reproduce
Github Workflow:
name: Crowdin Sync

on:
  push:
    branches: [ main ]

jobs:
  synchronize-with-crowdin:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: pre translate resources
        uses: crowdin/github-action@v2
        with:
          command: 'pre-translate'
          command_args: '--method ai --ai-prompt 37515 --translate-untranslated-only --directory "resources/lang/de"'
        env:
          CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}
          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}

crowdin.yml
files:
  - source: /resources/lang/de/*.php
    translation: /resources/lang/%two_letters_code%/%original_file_name%
  - source: /modules/Site/Resources/lang/de/*.php
    translation: /modules/Site/Resources/lang/%two_letters_code%/%original_file_name%
  - source: /modules/Import/Resources/lang/de/*.php
    translation: /modules/Import/Resources/lang/%two_letters_code%/%original_file_name%
  - source: /modules/Register/Resources/lang/de/*.php
    translation: /modules/Register/Resources/lang/%two_letters_code%/%original_file_name%
project_id_env: CROWDIN_PROJECT_ID
api_token_env: CROWDIN_PERSONAL_TOKEN
preserve_hierarchy: true

Action output:

But the same command is working using the crowdin cli localy

For testing purposes I have added the crowdin file list task to my github action, and it is listing all my files and directories as expected.
      - name: test
        uses: crowdin/github-action@v2
        with:
          command: 'file'
          command_args: 'list'
        env:
          CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}
          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}

Output:

Why do my pre-translate task doesn't find the files ?

Please try to specify the directory path without double quotes:
command_args: '--method ai --ai-prompt 37515 --translate-untranslated-only --directory resources/lang/de'

It works -.- thank you.


HDFS-17313. dfsadmin -reconfig option to start/query reconfig on all live namenodes.

Description of PR
JIRA: https://issues.apache.org/jira/browse/HDFS-17313
https://issues.apache.org/jira/browse/HDFS-16568 Support batch refreshing of datanode configurations.
There are several nn in the HA or Federated Cluster, and this ticket implements batch refreshing of nn configurations.
Implementation method

Use the DFSUtil.getNNServiceRpcAddressesForCluster method to parse the configuration and obtain the addresses of all nn's
Using two worker threads, currently does not support configuring the number of worker threads (will be implemented in other ticket if necessary)

How was this patch tested?
Add Unit Test.
Sample outputs
$ bin/hdfs dfsadmin -reconfig namenode livenodes start
Started reconfiguration task on node [localhost:50034].
Started reconfiguration task on node [localhost:50036].
Started reconfiguration task on node [localhost:50038].
Started reconfiguration task on node [localhost:50040].
Starting of reconfiguration task successful on 4 nodes, failed on 0 nodes.

$ bin/hdfs dfsadmin -reconfig namenode livenodes status
Reconfiguring status for node [localhost:50034]
SUCCESS: Changed property dfs.heartbeat.interval
	From: "5"
	To: "3"
Reconfiguring status for node [localhost:50036]
SUCCESS: Changed property dfs.heartbeat.interval
	From: "5"
	To: "3"
Reconfiguring status for node [localhost:50038]
SUCCESS: Changed property dfs.heartbeat.interval
	From: "5"
	To: "3"
Reconfiguring status for node [localhost:50040]
SUCCESS: Changed property dfs.heartbeat.interval
	From: "5"
	To: "3"
Retrieval of reconfiguration status successful on 4 nodes, failed on 0 nodes.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 18s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 38s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
1m 43s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
20m 19s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 30s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 1 new + 122 unchanged - 0 fixed = 123 total (was 122)

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 47s

the patch passed

+1 :green_heart:
shadedclient
20m 25s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
188m  3s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

273m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6395

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 5e869ee57c37 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7ff5e9b6f3eb6cb3d336a031fa090dc890b93fbd

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/1/testReport/

Max. process+thread count
3921 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 43s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 40s

trunk passed

+1 :green_heart:
javadoc
0m 39s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
1m 43s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
20m 10s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 28s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 41s

the patch passed

+1 :green_heart:
shadedclient
20m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
181m 20s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 27s

The patch does not generate ASF License warnings.

266m 56s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6395

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux fd1f8eb29208 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk /<PHONE_NUMBER>7937edefa3cdec8508842796bc7039

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/2/testReport/

Max. process+thread count
4749 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Hi @ayushtkn @tasanuma @tomscut @slfan1989 @virajjasani  If you have time, please help me review the code.

Hi @ayushtkn @tasanuma @tomscut @slfan1989 @virajjasani  If you have time, please help me review the code.

Hi @tomscut @virajjasani If you have time, please help me review the code.

Hi @tomscut @virajjasani Sorry to bother you again, do you have time to review this PR?

@huangzhaobo99 sorry for the delay in the reply. @tomscut is quite experienced and has helped with the review of the similar changes in the past. Let's wait for his response :)
Sorry that i cannot be of much help.

@huangzhaobo99 sorry for the delay in the reply. @tomscut is quite experienced and has helped with the review of the similar changes in the past. Let's wait for his response :) Sorry that i cannot be of much help.

@virajjasani Thanks for your reply, Let's wait for @tomscut response.

@goiri If you have time, Can you also help me review this? At that time, there was a batch refresh of the DN, but the relevant reviewers have not replied to me. This update is for the batch refresh mechanism of nn. Thx.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 12s

trunk passed

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 37s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 38s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 44s

trunk passed

+1 :green_heart:
shadedclient
20m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 27s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 56s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 40s

the patch passed

+1 :green_heart:
shadedclient
20m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
199m 18s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 28s

The patch does not generate ASF License warnings.

286m  6s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6395

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 5776a89e43ed 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7844442e03f2e2b1f2e75d0651882534785afb43

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/3/testReport/

Max. process+thread count
4656 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 43s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 44s

trunk passed

+1 :green_heart:
shadedclient
20m 31s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 30s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 57s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 47s

the patch passed

+1 :green_heart:
shadedclient
20m 28s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
202m  5s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 28s

The patch does not generate ASF License warnings.

288m 28s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestReconstructStripedFileWithRandomECPolicy

hadoop.hdfs.TestReconstructStripedFile

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6395

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 70430c8282b7 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / de03ab52df924d4a260c8e892a21ee02e6484bb6

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/4/testReport/

Max. process+thread count
4856 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6395/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Hi @slfan1989 @zhtttylz, Could you also review it for me? It's similar to HDFS-17146. Thanks.


When compiled with library evolution turned on, the resulting .swiftinterface file is not compiling.

Describe the bug
This is probably a Swift compiler limitation/bug, which can be easily overcome with a simple workaround - see below.
To Reproduce
To compile with library evolution, you use the following command line:
xcrun xcodebuild -workspace "./.swiftpm/xcode/package.xcworkspace" -scheme "combine-schedulers" -configuration Debug -destination "generic/platform=iOS Simulator" -sdk iphonesimulator BUILD_LIBRARY_FOR_DISTRIBUTION=YES SKIP_INSTALL=NO CLANG_ENABLE_CODE_COVERAGE=NO GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO SWIFT_SERIALIZE_DEBUGGING_OPTIONS=NO "OTHER_SWIFT_FLAGS=-Xfrontend -no-serialize-debugging-options"

You can then inspect the resulting .swiftinterface file by looking in the PRODUCTS folder, in CombineSchedulers.swiftmodule
There you will see files like arm64-apple-ios-simulator.swiftinterface or x86_64-apple-ios-simulator.swiftinterface
The gist of the problem is the following line (235) in the file Timer.swift:
public func receive<S: Subscriber>(subscriber: S)
      where Failure == S.Failure, Output == S.Input {

The compiler gets confused because the generic parameter 'S' in the receive function has the same name as the generic parameter 'S' in
public final class Timer<S: Scheduler>: ConnectablePublisher
(see line 83)
The Swift compiler gets confused because inside the .swiftinterface file nested types get fully qualified, so for receive you will get something like this:
    final public func receive<S>(subscriber: S) where S : Combine.Subscriber, S.SchedulerTimeType == S.Input, S.Failure == Swift.Never

And this is definitely confusing for the compiler.
The way to fix it is to rename the parameter 'S' in the receive to something else, e.g. 'SC':
public func receive<SC: Subscriber>(subscriber: SC)
      where Failure == SC.Failure, Output == SC.Input

In that case the resulting .swiftinterface will get this:
final public func receive<SC>(subscriber: SC) where SC : Combine.Subscriber, S.SchedulerTimeType == SC.Input, SC.Failure == Swift.Never

Since it's a very easy fix, I would greatly appreciate if it's done in a following minor/patch release.

Hi @flockoffiles, this does seem like a Swift bug, and I think we would happily take a PR that changes the generic name for receive. One recommendation is to name it Subscriber instead of SC to be more explicit. Want to give that a shot?

Sure. I can make a PR, but the type name Subscriber is already taken by Combine, which may also be confusing, no?