"Optimize" the interaction with Pathfinder.

Even though we moved the routing classes into an own independent package (which in the future might potentially be replaceable with a different router implementation) we still have some sort of coupling between Adroit and Pathfinder. Even worse, because we are talking about an indirect coupling between both components. Let me go into details:
In Pathfinder we store the target (aka actionToken as we call it in Adroit) in the Request attributes. The ContainerAwareActionResolver of Adroit reads the target from the Request attributes and tries to look it up in the supplied DIC. Luckily the name of the used Request attribute is configurable right now but a developer needs to be aware of this. I would call this implicit coupling as Adroit depends on a Request attribute which needs to be stored first by a different component.
I`d like to see a change in the code of Adroit and Pathfinder to achieve a better de-coupling of both components.

Closed with #22


Ruby installation fails on Ubuntu 2004

Ubuntu 2004 fails at the same spots when run from  2 different computers.
I cannot troubleshoot this as my linux skills aren't that great.
Bug

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for jmespath-1.4.0
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-partitions-1.451.0
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-partitions-1.451.0
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-eventstream-1.1.1
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-eventstream-1.1.1
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-sigv4-1.2.3
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-sigv4-1.2.3
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-sdk-core-3.114.0
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-sdk-core-3.114.0
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-sdk-kms-1.43.0
2021/05/04 14:07:06 packer.exe plugin: [ERROR] Remote command exited with '1': sudo sh -c 'DEBIAN_FRONTEND='noninteractive' HELPER_SCRIPTS='/imagegeneration/helpers' INSTALLER_SCRIPT_FOLDER='/imagegeneration/installers' PACKER_BUILDER_TYPE='azure-arm' PACKER_BUILD_NAME='azure-arm'  /tmp/script_5240.sh'
2021/05/04 14:07:06 packer.exe plugin: [INFO] RPC endpoint: Communicator ended with: 1
2021/05/04 14:07:06 [INFO] 6032 bytes written for 'stderr'
2021/05/04 14:07:06 [INFO] 35783 bytes written for 'stdout'
2021/05/04 14:07:06 [INFO] RPC client: Communicator ended with: 1
2021/05/04 14:07:06 [INFO] RPC endpoint: Communicator ended with: 1
2021/05/04 14:07:06 packer.exe plugin: [INFO] 35783 bytes written for 'stdout'
2021/05/04 14:07:06 packer.exe plugin: [INFO] 6032 bytes written for 'stderr'
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-sdk-kms-1.43.0
2021/05/04 14:07:06 packer.exe plugin: [INFO] RPC client: Communicator ended with: 1
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for aws-sdk-s3-1.94.0
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for aws-sdk-s3-1.94.0
2021/05/04 14:07:06 ui:     azure-arm: Parsing documentation for fastlane-2.181.0
2021/05/04 14:07:06 ui:     azure-arm: Installing ri documentation for fastlane-2.181.0
2021/05/04 14:07:06 [INFO] (telemetry) ending shell
2021/05/04 14:07:06 ui error: ==> azure-arm: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]
2021/05/04 14:07:06 ui: ==> azure-arm: Step "StepProvision" failed
2021/05/04 14:07:06 ui: ask: ==> azure-arm: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)?
2021/05/04 14:15:22 ui: ==> azure-arm: Provisioning step had errors: Running the cleanup provisioner, if present...
2021/05/04 14:15:23 ui: ==> azure-arm:

@AHuusom thanks for reporting! We've already started the investigation a few hours ago. It seems that the root cause is in the updated rdoc gem  (6.3.0->6.3.1), which is used for fastlane.

The issue in the Fastlane repo
https://github.com/fastlane/fastlane/issues/18642

@AHuusom we've made a workaround https://github.com/actions/virtual-environments/pull/3308. Please pull the latest main and try one more time.

Hi @miketimofeev.
This workaround seems to be working.
Thanks 👍


Responsive scaling

Is there a plan to implement responsive scaling?
Any quick solutions on how to implement it?

Has anyone found a solution?

The only workaround I found is:
window.onresize=function(){location.href=location.href}


【错误反馈】ws服务器连不上

运行环境
nonebot2.2, centos7, python3.9
NB插件及版本号
最新
MC插件及版本号
minecraft在另一台window服务器上，paper1.20.2
错误描述
ws服务器连不上，
MC日志

nonebot日志

报错日志（如果有）
No response

当我安装它的时候提示
Successfully installed nonebot-adapter-minecraft-1.0.7
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Task exception was never retrieved
future: <Task finished name='Task-9' coro=<load_module_data.._request() done, defined at /root/training/Python-3.9.10/lib/python3.9/site-packages/nb_cli/handlers/store.py:61> exception=ConnectError('All connection attempts failed')>
anyio._backends._asyncio.ExceptionGroup: 0 exceptions were raised in the task group:
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_exceptions.py", line 8, in map_exceptions
yield
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/asyncio.py", line 109, in connect_tcp
stream: anyio.abc.ByteStream = await anyio.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/anyio/_core/_sockets.py", line 225, in connect_tcp
raise OSError("All connection attempts failed") from cause
OSError: All connection attempts failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
yield
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection_pool.py", line 253, in handle_async_request
raise exc
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection_pool.py", line 237, in handle_async_request
response = await connection.handle_async_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 86, in handle_async_request
raise exc
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 63, in handle_async_request
stream = await self._connect(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 111, in _connect
stream = await self._network_backend.connect_tcp(**kwargs)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/auto.py", line 29, in connect_tcp
return await self._backend.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/asyncio.py", line 109, in connect_tcp
stream: anyio.abc.ByteStream = await anyio.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/contextlib.py", line 137, in exit
self.gen.throw(typ, value, traceback)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_exceptions.py", line 12, in map_exceptions
raise to_exc(exc)
httpcore.ConnectError: All connection attempts failed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/nb_cli/handlers/store.py", line 63, in _request
return await client.get(url)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1757, in get
return await self.request(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1533, in request
return await self.send(request, auth=auth, follow_redirects=follow_redirects)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1620, in send
response = await self._send_handling_auth(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1648, in _send_handling_auth
response = await self._send_handling_redirects(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1685, in _send_handling_redirects
response = await self._send_single_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1722, in _send_single_request
response = await transport.handle_async_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/root/training/Python-3.9.10/lib/python3.9/contextlib.py", line 137, in exit
self.gen.throw(typ, value, traceback)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ConnectError: All connection attempts failed
Task exception was never retrieved
future: <Task finished name='Task-8' coro=<load_module_data.._request() done, defined at /root/training/Python-3.9.10/lib/python3.9/site-packages/nb_cli/handlers/store.py:61> exception=ConnectError('All connection attempts failed')>
anyio._backends._asyncio.ExceptionGroup: 0 exceptions were raised in the task group:
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_exceptions.py", line 8, in map_exceptions
yield
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/asyncio.py", line 109, in connect_tcp
stream: anyio.abc.ByteStream = await anyio.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/anyio/_core/_sockets.py", line 225, in connect_tcp
raise OSError("All connection attempts failed") from cause
OSError: All connection attempts failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
yield
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection_pool.py", line 253, in handle_async_request
raise exc
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection_pool.py", line 237, in handle_async_request
response = await connection.handle_async_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 86, in handle_async_request
raise exc
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 63, in handle_async_request
stream = await self._connect(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 111, in _connect
stream = await self._network_backend.connect_tcp(**kwargs)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/auto.py", line 29, in connect_tcp
return await self._backend.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/backends/asyncio.py", line 109, in connect_tcp
stream: anyio.abc.ByteStream = await anyio.connect_tcp(
File "/root/training/Python-3.9.10/lib/python3.9/contextlib.py", line 137, in exit
self.gen.throw(typ, value, traceback)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpcore/_exceptions.py", line 12, in map_exceptions
raise to_exc(exc)
httpcore.ConnectError: All connection attempts failed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/nb_cli/handlers/store.py", line 63, in _request
return await client.get(url)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1757, in get
return await self.request(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1533, in request
return await self.send(request, auth=auth, follow_redirects=follow_redirects)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1620, in send
response = await self._send_handling_auth(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1648, in _send_handling_auth
response = await self._send_handling_redirects(
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1685, in _send_handling_redirects
response = await self._send_single_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1722, in _send_single_request
response = await transport.handle_async_request(request)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/root/training/Python-3.9.10/lib/python3.9/contextlib.py", line 137, in exit
self.gen.throw(typ, value, traceback)
File "/root/training/Python-3.9.10/lib/python3.9/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ConnectError: All connection attempts failed

感谢指导，现在有另一个小问题，当我在服务器中发消息时，他能够转发到群，但是会再次将bot的话转到服务器。

感谢指导，现在有另一个小问题，当我在服务器中发消息时，他能够转发到群，但是会再次将bot的话转到服务器。

你的机器人是上报了自己的消息吗？
如果是的话，我没有做这个过滤

好的，感谢，我尝试先自行修改一点代码实现吧

已在 mcqq-tool v1.1.4 修复

403你需要查看你mc那边的连接地址是否配置正确 同时你需要检查mc适配器成功加载

我使用的nonebot是ATRI，安装插件后启动没有看到Minecraft适配器加载的信息，当然最后mc服务器也连接不上onebot

如果没有更详细的日志，我无法看出什么问题。另外我没有用过ATRI，这类问题应该自行解决。


Terminal Configuration in Settings Fails on Preview with Canary and Stable Installed

First off, great job with this app. Very beautifully designed, even the public test build is rock solid. Looking forward to seeing where XPipe goes!
Issue:
Using Terminal Canary side loaded with Terminal Stable.
Ran the terminal config in settings for Terminal preview (as I figured closest to my highest/most used version). Failed with Java exception due to not finding the path.
Tried the Terminal Stable option and command runs. Also works on cmd.
Let me know if you need me to send any additional logs or files! Happy to help!
Details:
java.io.IOException: Unable to launch terminal Windows Terminal Preview: Process returned exit code 3:
The system cannot find the path specified.
at io.xpipe.app.util.TerminalLauncher.open(TerminalLauncher.java:73)
at io.xpipe.app.util.TerminalLauncher.open(TerminalLauncher.java:43)
at io.xpipe.app.prefs.TerminalCategory.lambda$create$0(TerminalCategory.java:43)
at io.xpipe.app.util.ThreadHelper.lambda$runFailableAsync$1(ThreadHelper.java:42)
at io.xpipe.app.util.ThreadHelper.lambda$wrap$0(ThreadHelper.java:19)
at java.lang.VirtualThread.run(VirtualThread.java:309)
Caused by: io.xpipe.core.process.ProcessOutputException: Process returned exit code 3:
The system cannot find the path specified.
at io.xpipe.core.process.ProcessOutputException.of(ProcessOutputException.java:53)
at io.xpipe.ext.proc.a.a(SourceFile:432)
at io.xpipe.ext.proc.a.discardOrThrow(SourceFile:252)
at io.xpipe.core.process.ShellControl.executeSimpleCommand(ShellControl.java:139)
at io.xpipe.app.terminal.WindowsTerminalType$Preview.launch(WindowsTerminalType.java:77)
at io.xpipe.app.util.TerminalLauncher.open(TerminalLauncher.java:69)
... 5 more

Environment:
Windows 11 Pro Insider Preview
Evaluation copy. Build 26212.ge_prerelease.240503-1218
Windows Terminal Canary
Version: 1.22.1341.0
"C:\Program Files\WindowsApps\Microsoft.WindowsTerminalCanary_1.22.1341.0_x64__8wekyb3d8bbwe"
Windows Terminal
Version: 1.20.11271.0
"C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.20.11271.0_x64__8wekyb3d8bbwe"
Windows 11 Insider Program on Latest Canary - 26212.ge_prerelease
XPipe Community 10.0

I didn't even know that there was a canary build. I can add support for that, shouldn't be too different from the other windows terminal implementations.

This is now added in https://github.com/xpipe-io/xpipe/releases/tag/9.3


add decays to make const value_type compile

fixing #726 and #725
@ukoethe can you review this PR?

Looks good to me.


Adding IoT section

First PR on new IoT section.  NOTE: I did NOT update the README.md index to add the links for the new IoT section yet.

@ThanosBaskous and other IoT experts might want to do a final pass too.
@ThanosBaskous note I think we can do the markdownfmt consistency once we are caught up on PRs to minimize conflicts. (But go ahead and argue w me if you disagree.)

@jlevy Good note regarding markdown consistency - I'll ease up on nitpicky markdown formatting issues.

I believe I have updated to include all of both of your change requests.

LGTM now, with just two details:

The gotchas are missing the emoji yellow🔸 or ❗
There is a line in https://github.com/open-guides/og-aws#which-services-to-use

⛓IoT: Manage bidirectional communication over HTTP, WebSockets, and MQTT between AWS and clients (often but not necessarily “things” like appliances or sensors)
Could we change the link there to be to #iot now, and are you good with that summary too btw?

💥 Awesome! Thanks for this fantastic addition @lynnlangit!

👍 👍 👍 Merged last changes in (and moved section to final place).
Awesome. Thank you @lynnlangit !


Add server side connections, pending responses metrics

Because currently our service does not shutdown gracefully, want to know about pendings. Do we have any other metrics that is useful to investigate this?

Because currently our service does not shutdown gracefully, want to know about pendings. Do we have any other metrics that is useful to investigate this?

A gauge for 'time taken since graceful shutdown started'?

A gauge for 'time taken since graceful shutdown started'?

Ah, sounds useful to me. Let me keep this PR as is and will open another PR to add the gauge.

Thanks, @imasahiro !


config/v1/types_cluster_operator: "the kube ecosystem" -> "the Kubernetes ecosystem"

The abbreviated wording was originally from 898d7e3b7c (#127).  But using the full name in these docs gives readers one less abbreviation to recognize.

/lgtm


shadowland after 35, I would like to know if it is possible?

can you configure the bot for shadowland to do after 35? because I realized that he is only able to go up to 35 then to.

I'll add it to the list - just pushed out new update FYI.

thanks :)


Update ocp branch references

Now that we've graduated the operator to v1.0 and we have a specific
branch for that version called ocp-1.0, we should update those
references in the Makefile and documentation so the automation continues
to do what it should for Compliance Operator builds.

I found this while doing the v1.1.0 release, but we don't have to merge this before continuing with that release.

/hold

@rhmdnd do you want this PR to be merged before PR #353 and have 353 rebased atop this one?

@rhmdnd do you want this PR to be merged before PR #353 and have 353 rebased atop this one?

This isn't required for the 1.1.0 release. I had to push the ocp-1.0 branch changes manually anyway. If the CO 1.1.0 release looks good and doesn't need another respin, then I'm OK having this merge after and we'll just take advantage of it in future releases.

/hold cancel
thanks for the info

Test failed getting a cluster.

/test e2e-aws-serial


Update modular efforts to faster settings.

Before:
Encoding [Modular, lossless, effort: 7]
Compressed to 137.9 kB (9.629 bpp).
444 x 258, geomean: 0.370 MP/s [0.35, 0.52], 20 reps, 72 threads.
7.69user 3.43system 0:06.12elapsed 181%CPU (0avgtext+0avgdata 96460maxresident)k

Encoding [Modular, lossless, effort: 8]
Compressed to 137.6 kB (9.606 bpp).
444 x 258, geomean: 0.148 MP/s [0.15, 0.15], 5 reps, 72 threads.
4.05user 0.87system 0:03.84elapsed 128%CPU (0avgtext+0avgdata 36848maxresident)k

Encoding [Modular, lossless, effort: 9]
Compressed to 137.3 kB (9.586 bpp).
444 x 258, geomean: 0.038 MP/s [0.04, 0.04], 5 reps, 72 threads.
15.46user 0.88system 0:14.99elapsed 109%CPU (0avgtext+0avgdata 67496maxresident)k

Encoding [Modular, lossless, effort: 7]
Compressed to 47974.1 kB (9.827 bpp).
7216 x 5412, geomean: 0.255 MP/s [0.25, 0.26], 5 reps, 72 threads.
847.79user 141.99system 12:48.70elapsed 128%CPU (0avgtext+0avgdata 7066772maxresident)k

Encoding [Modular, lossless, effort: 8]
Compressed to 47582.7 kB (9.747 bpp).
7216 x 5412, second: 0.141 MP/s [0.14, 0.14], 2 reps, 72 threads.
655.49user 37.07system 9:18.64elapsed 123%CPU (0avgtext+0avgdata 5266892maxresident)k

Encoding [Modular, lossless, effort: 9]
Compressed to 47531.4 kB (9.737 bpp).
7216 x 5412, second: 0.039 MP/s [0.04, 0.04], 2 reps, 72 threads.
2206.83user 36.33system 33:36.39elapsed 111%CPU (0avgtext+0avgdata 6862308maxresident)k

After:
Encoding [Modular, lossless, effort: 7]
Compressed to 138.0 kB (9.637 bpp).
444 x 258, geomean: 0.516 MP/s [0.42, 0.61], 20 reps, 72 threads.
7.84user 3.47system 0:04.56elapsed 248%CPU (0avgtext+0avgdata 51700maxresident)k

Encoding [Modular, lossless, effort: 8]
Compressed to 137.9 kB (9.631 bpp).
444 x 258, geomean: 0.411 MP/s [0.39, 0.60], 5 reps, 72 threads.
2.30user 0.81system 0:01.33elapsed 234%CPU (0avgtext+0avgdata 35928maxresident)k

Encoding [Modular, lossless, effort: 9]
Compressed to 137.8 kB (9.621 bpp).
444 x 258, geomean: 0.073 MP/s [0.07, 0.07], 5 reps, 72 threads.
13.81user 0.64system 0:07.89elapsed 183%CPU (0avgtext+0avgdata 55336maxresident)k

Encoding [Modular, lossless, effort: 7]
Compressed to 48235.9 kB (9.881 bpp).
7216 x 5412, geomean: 10.826 MP/s [10.47, 11.02], 5 reps, 72 threads.
609.18user 138.46system 0:19.57elapsed 3819%CPU (0avgtext+0avgdata 1003488maxresident)k

Encoding [Modular, lossless, effort: 8]
Compressed to 47937.9 kB (9.820 bpp).
7216 x 5412, second: 6.096 MP/s [6.04, 6.10], 2 reps, 72 threads.
363.07user 28.97system 0:14.32elapsed 2737%CPU (0avgtext+0avgdata 4934312maxresident)k

Encoding [Modular, lossless, effort: 9]
Compressed to 47811.7 kB (9.794 bpp).
7216 x 5412, second: 2.333 MP/s [2.33, 2.34], 2 reps, 72 threads.
1747.88user 31.96system 0:34.88elapsed 5102%CPU (0avgtext+0avgdata 5146160maxresident)k

This only changes things to use local trees instead of global ones also in the default non-streaming case, right?
So it still applies Patch detection and global palettes the same way as before?
(for photo you can probably get away with defaulting to streaming encode, which cannot do those global things, but for non-photo those coding tools can be useful)

This only changes things to use local trees instead of global ones also in the default non-streaming case, right?
So it still applies Patch detection and global palettes the same way as before? (for photo you can probably get away with defaulting to streaming encode, which cannot do those global things, but for non-photo those coding tools can be useful)

It also enables streaming mode in cjxl by default, which I believe will disable patches. Perhaps that's not the best solution...

I know the streaming modular implementation is still in progress, but just in case this was missed:
After this PR, the switch case at the following link is missing kGlacier, resulting in it being faster and less dense (at least when doing this part of the encoding) than kTortoise because it uses the values in the default case.
Link to Code

I know the streaming modular implementation is still in progress, but just in case this was missed:
After this PR, the switch case at the following link is missing kGlacier, resulting in it being faster and less dense (at least when doing this part of the encoding) than kTortoise because it uses the values in the default case. Link to Code

Thanks for catching this!


"The Windows App SDK (Experimental)" extension does not work with VS 2022

Describe the bug
I've learned offline that the 2022 and Experimental extensions can coexist, both can be used to create apps. The problem comes from the change WinAppSDK packaging. That change breaks upgrading to the lates in the NuGet package manager; hand-edit the .vcxproj and remove the unneeded packages.
I mistakenly installed the VS Extension for WinAppSDK on my VS 2022 install. Instead, experts told me, I should have added that optional feature from the VS installer (an optional feature that needs to be selected).
After doing this I created a VS app from the template. this worked, builds and runs.
Then I used the NuGet package manager to update packages to the latest version. This resulted in conflicting .prop file <Import>'s, e.g. Microsoft.WindowsAppSDK.1.0.3 and Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1
From the owners, I learned this extension should not be used.
Steps to reproduce the bug

In a VS 2020 session, use the VS extension manger to install The Windows App SDK (Experimental)
File.New Project...Win App SDK C++ App
build, run.
Project.Manage nuget packages..
go to the updates tab
select the newer packages, "install"
F5 to build. see errors below

1>------ Build started: Project: WinAppSdk2, Configuration: Debug x64 ------
1>C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.props(25,3): warning MSB4011: "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.UI.Xaml.Markup.Compiler.props" cannot be imported again. It was already imported at "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.WinUI.props (25,3)". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\WinAppSdk2.vcxproj]
1>C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.WinUI.targets(77,3): warning MSB4011: "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.References.targets" cannot be imported again. It was already imported at "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.targets (76,3)". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\WinAppSdk2.vcxproj]
1>C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.WinUI.targets(78,3): warning MSB4011: "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.AppX.targets" cannot be imported again. It was already imported at "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.targets (77,3)". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\WinAppSdk2.vcxproj]
1>C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.WinUI.targets(80,3): warning MSB4011: "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.UI.Xaml.Markup.Compiler.targets" cannot be imported again. It was already imported at "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.targets (79,3)". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\WinAppSdk2.vcxproj]
1>C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.1.0.3\build\Microsoft.WinUI.targets(82,3): warning MSB4011: "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.Build.Msix.targets" cannot be imported again. It was already imported at "C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\packages\Microsoft.WindowsAppSDK.WinUI.1.0.0-experimental1\build\Microsoft.WinUI.targets (81,3)". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\WinAppSdk2.vcxproj]
1>64 bit MIDLRT Processing C:\Users\chrisg.NTDEV\source\repos\WinAppSdk2\App.idl

Expected behavior
it builds
Screenshots
No response
NuGet package version
No response
Packaging type
No response
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2022
Additional context
No response

This isn’t an issue with the experimental VSIX. There’s nothing stopping the experimental extension from peacefully coexisting with the preview/stable VSIX.
Instead, this is an incompatibility between how the <= 1.0.0-experimental1 NuGet packages were structured, and how the >=1.0.0-preview1 NuGet packages work.
Starting with 1.0.0-preview1, all of Window App SDK is in a single NuGet package. But prior to that, the main NuGet package was a mere wrapper/hook metapackage to bring in several other dependencies that had all the actual implementation (e.g. Microsoft.WindowsAppSDK.Foundation, Microsoft.WindowsAppSDK.WinUI, etc…). See the 1.0.0-experimental1 package’s dependencies tab NuGet Gallery | Microsoft.WindowsAppSDK 1.0.0-experimental1.
Apparently, when you use the NuGet package manager to upgrade a package, it doesn’t remove dependencies that are no longer needed. So when it leaves these separate dependencies around they now conflict with the logic in the “new” monolithic package.
It’s perfectly fine if you want to tinker with the experimental extension/NuGet. But if you create a project using “experimental” hoping to update it into using “preview/stable”, that’s not something we’re actively trying to support, and some degree of friction like this may occur.
There might be the option of using the NuGet package manager console to do a reinstall and ignore dependencies (Reinstalling and Updating NuGet Packages | Microsoft Docs), but I haven’t tested it to know if that would yield non-breaking behavior. Uninstalling the package and its dependencies and then reinstalling the newer version is probably safer.

Given that Microsoft has deviated from its release cadence/channel plans perhaps it's time to rethink the VSIX situation. That is, perhaps you'll be better off deleting all experimental-channel VSIX packages to reduce confusion/clutter.

@riverar Yes, we're currently revamping the Downloads page to remove now unsupported standalone VSIX packages (including experimental).

@Scottj1s Sounds good!


:sparkles: Add More Parameter Function Parameters

Bug: Typing.composer: method should be __call__, not compose

Make ResolutionError, CompositionError and PreparationError expect a Parameter argument and generate a nice message for free

Make compose and resolve methods in parameters @staticmethods if they can be

Remove .models.Client from __init__

Move .decorators out of .composition. If I'm a user, I expect to be able to import decorators using:
from fastclient.decorators import ...

Remove Supplier, Consumer and Function from .typing?

Add an __all__ to .types and remove anything that doesn't need to be there

Move parse_obj_as to utils?

Reduce code duplication in .parameters, e.g. for all parameters expecting a non-None alias

Rename .operations to .operation

Import httpx types into .models and then export them?
E.g:
from fastclient.models import QueryParams, Headers

I believe .models.ClientOptions.is_default is no longer needed

Is .models.ClientOptions.from_client used? If not, should it be in the future?

Rename .enums.HttpMethod to .enums.HTTPMethod? What does Java (spring) do?

Use tuples for __all__ and type annotate using Sequence

Implement custom QueryParams, Headers etc. which perform conversion using fastclient types?

Make ResolutionError, CompositionError and PreparationError expect a Parameter argument and generate a nice message for free (NOTE: Might cause a cyclic dependency)

Not attempting this due to the cyclic dependency it will cause at this stage

Import httpx types into .models and then export them? E.g:
from fastclient.models import QueryParams, Headers

Not doing at this stage, will cut a separate issue

Make compose and resolve methods in parameters @staticmethods if they can be?

Not doing at this stage as not super important

.models.ClientOptions.from_client isn't used. Should it be?

ClientOptions was removed from the codebase for now as it was not being used


refactor Travis with hererocks

note: YAML supports multiple lines with the | notation. So, all external scripts could be embedded in .travis.yml.

Coverage remained the same at 82.666% when pulling 596427d115a60bc919123fc959799a604698ca5d on fperrad:ci into 9657d5a0ec052380a43b119b8b4f5086e6662075 on sailorproject:master.

nice! thanks 💃


Per-page reload opt-out

TLDR; If the attribute data-server-no-reload is found on the <body> tag, commands to reload the page are ignored.
At the moment, all browser windows are reloaded when there is a source change, regardless of whether the source change affects them. This is a robust, base logic.
However, there are instances where one wants to prevent a page from being reloaded by changes. Eg, if a.html opens up a connection to a media device, a change in b.html will cause a.html to be perhaps unnecessarily reloaded. This requires a manual re-starting of the stream, and other state may be lost.
This addition changes the injection script to check for the presence of an attribute on the BODY element. If it's there, the reload requests are ignored, and the page will have to be manually reloaded. The user can explicitly opt out of automatic reloading for pages they want manual control over, which otherwise is not currently possible.
It uses the same attribute name as Five Server so the behaviour is identical regardless of which extension is used.
(Some other minor formatting changes happened applying the repo's eslint rules)

Fantastic, thank you!


DSi Downgrade question

I'd like to restore its original NNID on 3DS#2 and my original NNID on 3DS#1 while keeping cfw.
In order to do the first (original NNID on 3DS#2) I know the only way to change a NNID is to system format, but this will remove CFW, right?
So my plan is:

Do the DSi Downgrade on 3DS#2
Format 3DS#2 while in downgraded firmware
Log back in with original NNID on 3DS#2
Log back in with my NNID in 3DS#1
Restore NANDmin.bin on 3DS#1 and dumped mii/miiplaza/extdata on 3DS#2 using browserhax/hb

My questions are:

Will I still be able to continue the guide to the following steps on 3DS#2
Will 3DS#1 allow me to login and have the CFW?
What does it mean "Go to the settings and attempt sign back into your initial NNID, then call Nintendo and ask about the error you get"?
What error should I get and what can Nintendo do about it?

Question 3 is what bugs me the most, it's very unclear ^^
Thanks.

Well first of all if you have A9LH system formatting won't remove CFW. Needless to say, the DSiWare downgrade is a whole lot less of a headache if 3DS #1 has an A9LH sysNAND.

It is not a good idea to format your console when you have just downgraded your firmware for the sake of linking a NNID.  Any restoring of the NNID on 3DS #2 should be once A9LH is installed on the console. Also a quick note: if you softbrick after the 9.2 downgrade, you will always softbrick until you perform a system format. I recommend trying the downgrade without formatting first. If you softbrick and you have to update back to 11.1, that's ok since you will still have Fieldrunners and the hacked save. Then, downgrade your firmware with the hacked save and then system format. Then, get into HBL and attempt the 9.2 downgrade again.

Thanks. Then I guess I'll have to just wait a week or  "Go to the settings and attempt sign back into your initial NNID, then call Nintendo and ask about the error you get"

What kind of system transfer are you doing (old to old, old to new, new to new)?

Simply new to new, so I can just transfer back after a week I guess. My only concern is with saved data, MIIs and MII Plaza games.

Yeah, your question about the calling Nintendo step doesn't apply to you, so don'5 worry about that. That is only if you are doing an old to new transfer or if you don't system transfer back for some reason.

Mii data is tied to your NNID. Mii Plaza data cannot be backed up in userland, so that will be lost when you systen format. However, once you have A9LH you are able to back up Mii Plaza savedata and then you can use a save editor program to customize your save to pretty much what it was before the format. I think streetpass data is actually tied to your NNID, so stuff like Find Mii progress and such is the only thing you lose. Also, if you have digital games, you need to back the saves for those up using JKSM through HBL because those will be lost in the format.


merge-commit from release-3.42 into master

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

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

Comparison is base (2e12760) 63.91% compared to head (f4c6cf9) 44.58%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #643       +/-   ##
===========================================
- Coverage   63.91%   44.58%   -19.34%
===========================================
  Files         226      152       -74
  Lines       21794    15621     -6173
===========================================
- Hits        13930     6964     -6966
- Misses       7142     8336     +1194
+ Partials      722      321      -401

Flag
Coverage Δ

1.16.x
44.23% <ø> (-19.20%)
:arrow_down:

1.19.x
?

1.20.x
44.61% <ø> (-18.85%)
:arrow_down:

insecure
?

integration
?

macOS-latest
44.61% <ø> (+0.07%)
:arrow_up:

secure
?

ubuntu-latest
44.23% <ø> (-19.65%)
:arrow_down:

unit
44.58% <ø> (-0.10%)
:arrow_down:

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

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


Support for HTML in options

Is it possible to use HTML when adding options? For instance, a <br> for multi-line labels?

Hi @haggen,
Could you give me an example of how you envisage doing this?
Thanks

I know this is closed, but one example are superscript tags. We need to have a registered symbol superscripted but at the minute it's being stripped out of the option.


Configure CodeQL workflow

It is not clear to us what this code does, it seems like it is trying to scan the code without building?

It is not clear to us what this code does, it seems like it is trying to scan the code without building?

Hi Ben, this PR is in Work In Progress state, because I am learning how to properly configure workflows for this project. I will add people for review once it is finished, ready to review and merge.
The CodeQL workflow will be removed, because configuring it through the Security tab (GitHub UI) should be sufficient. I was only testing its capabilities here.


update blockbreaker.py and the associated schemas to have consistent/…

…universal handling of numbers/number ranges/list of number ranges

for example, these would all be treated similarly no matter where they are being specified:
1
1-3
1-3+5-7

lgtm
unrelated catch that comes from the original design: output-* files that are streams and not JSON should not have .json extension (although they are inside JSON/ dir)

Good point, I agree, I will fix.


Fortran compatibility

We should probably explicitly state which Fortran standards we support.
Ideally, we might test against different standards, if that's possible (maybe via the -std gfortran compile flag - if so, we may want to open a separate issue, and keep this one focused on documentation)?

My thoughts here are can we write something to test this automatically?
Like a workflow that iterates over the various standards and builds FTorch with different flags?

Discussion with @TomMelt We will set FTorch to require Fortran 2008 in the documentation.
See comments on #145 for further development.


Sometimes empty results cached for valid addresses

Branching off discussion started here…
It appears that the Google Geocoding API will sometimes reply with an empty result set for an otherwise good address (one that would normally produce one or more results). Since this empty set is cached by the gem, future geocoding requests for this same address will also show no results.
One such address that we saw in production was 5302 W Argyle St, Chicago, IL, United States. I don't believe there is anything special with this address; it just happened to be one where we noticed this issue. (What led to discovery was a user saying our system couldn't find this address while google maps found it with no problem. Purging the cache (or just spelling the address slightly differently) resolved the error, indicating that our geocoder cache contained an empty result.)
Because the gem should only cache a valid_response? …it would seem that Google will occasionally return an OK or ZERO_RESULTS status in spite of an errant empty result set.
Not sure how to recreate the issue so tricky to diagnose a root cause. One solution that treats the symptom would be an ability to set a short expiration time on cached items with empty result sets.

@rdlugosz Have you learned any more about this since implementing your own API interaction?
If not, I'm tempted to close the issue, because it seems too complicated (out of scope of the gem) to address. If Google is returning incorrect response codes, hopefully it's a temporary condition of the API. Setting expiration times for certain types of results would be a possible solution, but expiration is not something the Geocoder's generalized cache interface can really handle, given that every underlying cache mechanism handles expiration differently.
Hope that makes sense. I am still very interested in dealing with #1089.

Not really; I'll occasionally see a failure where the exception looks like this:
HTTParty::ResponseError: Code 500 - { "results" : [], "status" : "UNKNOWN_ERROR" }
...but it's pretty uncommon and often resolves itself with future queries. Unsure if this is related to the issue I was seeing; I would think the gem would not store the results in the face of a 500 error, but maybe it would?
You're welcome to close the issue as it sounds like neither of us are able to put a lot of time into this one for now.

A response with a 500 status from Google would definitely not be cached. It's the responses that are 500s in content but (incorrectly) have a non-500 status that I'm worried about. But, again, I think it's too difficult to test and solve for Google's bugs.


Local

with these 2 patches, i can run with bootrr scripts installed in /usr/bin, with
/usr/bin/arrow,apq8096-db820c
or I can also directly run them without installing them, directly from the git tree, using:
export PATH=$PWD/helpers:$PATH
./boards/arrow,apq8096-db820c
which is really convenient
It's also convenient to not have to worry about lava-test-case..

Verified on db820c and db410c


Add namespace check between pod and multi-networkpolicy

Pull Request Test Coverage Report for Build 780675755

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 48.246%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/server/server.go
0
5
0.0%

Totals

Change from base Build 656684464:
-0.1%

Covered Lines:
784

Relevant Lines:
1625

💛  - Coveralls


[CELEBORN-1097] Optimize the retrieval of configuration in the internalCreateClient

What changes were proposed in this pull request?
Optimize the retrieval of configuration in the internalCreateClient
Why are the changes needed?
Directly accessing configuration information through 'conf.xx' in 'internalCreateClient' is time-consuming.

Does this PR introduce any user-facing change?
How was this patch tested?

We can refactor the initializeMemoryAllocator function to eliminate its dependency on the member variable TransportClientFactory#conf. This will allow us to safely remove the TransportClientFactory#conf member variable, to prevent performance degradation resulting from erroneous TransportClientFactory#conf utilization.

We can refactor the initializeMemoryAllocator function to eliminate its dependency on the member variable TransportClientFactory#conf. This will allow us to safely remove the TransportClientFactory#conf member variable, to prevent performance degradation resulting from erroneous TransportClientFactory#conf utilization.

@cfmcgrady Currently, it appears that the 'TransportClientFactory#conf' is mainly used during the initialization of 'TransportClientFactory' and is called only once. Therefore, there is no additional overhead from multiple invocations.

there is no additional overhead from multiple invocations.

You're correct. I mean we can remove the TransportClientFactory#conf variable, as it is only used within the function initializeMemoryAllocator when the TransportClientFactory is initialized.
https://github.com/apache/incubator-celeborn/blob/70366edb7cef59ff27bdde888b747a897b1f0a2c/common/src/main/java/org/apache/celeborn/common/network/client/TransportClientFactory.java#L71

thanks, merging to main(v0.4.0)/branch-0.3(v0.3.2).


[]Doc Improvement][Update provision in cloud resources][2668619]

Interchanged Use an existing Azure AD app for your bot to Use an existing Azure AD app for your Teams app. and
Use an existing Azure AD app for your Teams app to  Use an existing Azure AD app for your bot.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/provision.md
94
63
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 5d7224e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/provision.md
94
63
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 75c25f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 410cd0f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Make end-to-end demo on Raspberry Pi simpler and more descriptive

What this PR does / why we need it:
Update end-to-end demo on Raspberry Pi with changes to normal end-to-end-demo in https://github.com/deislabs/akri/pull/191.

Our end-to-end demos are Ubuntu specific. Should we add instructions for cloning the v4l2loopback repo and building in the case when someone is using a different Linux distro, such as Alpine Linux in this issue.

Our end-to-end demos are Ubuntu specific. Should we add instructions for cloning the v4l2loopback repo and building in the case when someone is using a different Linux distro, such as Alpine Linux in this issue.


tests/network: drop references to tests.BashHelloScript

tests.BashHelloScript is an internal implementation glitch, needed to
get Cirros VMs boot faster. It should not spread to any test.
NONE

/approve


bundled build flags

According to #65 , I found out that the released asset from duckdb repo is different from our bundled release, as they might use different flags. eg. windows
It will make some of the features not supported in our bundled build, for example, test_insert_duplicate succeed using the released asset, but failed in bundled version when build from source.
We may need to set the flags same to the released version of duckdb, in build.rs

@Michael-F-Bryan If you are using bundled version, you may also need pay attention to this. It related to the ignored tests

Do you think we could enable the setting of optional flags in build.rs through Rust feature flags by guarding some code blocks with them?
I might give that a try.

I'll do that, thanks


Bigtable: 10. Implementation: integrate ReadRows

This builds on PR #2914 by creating the ReadRows callable chain.
@kevinsi4508 can you take a look at this when you have a moment?

Ok, all feedback should now be addressed. Please merge when ready

LGTM!


Update Hasher.php

Options are not used for this method.
Also see:
https://github.com/laravel/framework/pull/17443

Other implementations may use the options though. Also, breaking changes like this are not suitable for 5.3.


Please use license consistently in the release jar files

readme.md says that project license is BSD-3-Clause.
Please propagate that to the release jars, otherwise it is very hard to comply with hamcrest-date license terms.

Please add Bundle-License: BSD-3-Clause manifest entry (where BSD-3-Clause is SPDX identifier, see https://osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.module-bundle-license )
Well, current pom.xml tags are quite obvious (even though you might want to replace <licence><name> with SPDX id of BSD-3-Clause), however adding explicit Bundle-License is much more important.

Please add LICENSE file to the produced jar file as /META-INF/LICENSE  (and probably to the source repository as /LICENSE).
The thing is the license requires re-distributions to reproduce copyright notice, however it is really hard to do that in an automatic way, taking into account hamcrest-date.jar is often taken from Maven Central. The jar file just misses LICENSE file, so it is really hard to reproduce copyright notice and track it for all version upgrades upgrades.

The suggested file locations is META-INF/LICENSE
PS I'm implementing an automatic license analysis for Apache JMeter, and I noticed LICENSE is not distributed by hamcrest-date.

This has now been fixed in master and will be release shortly


Log the backtrace for timeout errors

Currently it's hard to tell where exactly the timeout errors are
coming from. So log the backtrace when this happens, as this is the
least worst way of doing this that I could find.

I think I've found a better way https://github.com/alphagov/smart-answers/pull/3796


[vim9script] Regression: E1180: Variable arguments type must be a list: any

Steps to reproduce
Source this script:
vim9script

def F(X: func(...any): any)
enddef

This results in E1180. It used to compile before 3ec6c1fe3bb1b366b710d3e7226f7eed3be1801a.
Expected behaviour
Vararg function with type any should compile.
Version of Vim
9.0.2059
Environment
macOS 14.0
Apple Terminal
xterm-256color
ZSH 5.9
Logs and stack traces
No response

Vararg function with type any should compile.

I agree. AFAICT, the proper syntax is
def F(X: func(...list<any>): any)

The PR you mention is a bug fix, incorrect syntax was not detected. Could you take a look at https://github.com/vim/vim/pull/13397#issue-1955273280 and comment with that in mind.

A key comment there might be

Since no other tests failed with this change; I'm assuming that in a funcref
...string is not magic shorthand for something.

At the end of :help type-checking in a release with this PR, there's an example of declaring a func that accepts any arguments.

def F(X: func(...any): any)
enddef

Is this acutally valid? According to the help, we will always require a list-type:
Variable arguments are defined as the last argument, with a name and have a
list type, similar to TypeScript.  For example, a list of numbers: >
	def MyFunc(...itemlist: list<number>)
	   for item in itemlist

I see now that I was relying on the looser type checking in one of my libraries. I had typed a function as:
def F(G: func(...any): any)

and it was accepting both F1(...list<any>): any and F2(any): any. Now, after fixing the type signature, the latter are not compatible any longer and I obviously need to update their argument's type.
Thanks for clarifying! You may close this. Just one thing: maybe, in :h vim9-func-declaration the following two type declarations:
func(...{type})
func({type}, ?{type}, ...{type}: {type}

should be changed to:
func(...list<{type}>)
func({type}, ?{type}, ...list<{type}>: {type}

?

maybe, in :h vim9-func-declaration the following two type declarations:
func(...{type})
func({type}, ?{type}, ...{type}): {type}

should be changed to:
func(...list<{type}>)
func({type}, ?{type}, ...list<{type}>): {type}

I was wondering about that myself. I think I had a crazy thought that {type} is what the code in the function sees (type would be list<{type}>) but that reasoning is convoluted.
The description says
- type of variable number of arguments

How about
- type of list for variable number of arguments

(seems better than `type of variable number of arguments' list)
Please comment on what is easiest to read/understand. And I'll make some changes if there are no objections.

typoe of list sounds good, but to make it really clear, I'd also change it to this here (so confirm to @lifepillar opinions)
func(...list<{type}>)
func({type}, ?{type}, ...list<{type}>): {type}


chore: update code owners

Summary of Changes
Update code owners.

:tada: This PR is included in version 0.29.0 :tada:
The release is available on:

v0.29.0
GitHub release

Your semantic-release bot :package::rocket:


no sound button in firefox/ button with visible toggle in safari

exchanged the toggle with a custom coded button


Update README.md

What kind of change does this PR introduce?
The Html Logo was not showing. So , I changed the URL for the Html 5.
Before  Changing the URL:

After updating the URL:

Did you add tests for your changes?
Does this PR introduce a breaking change?
-No, It does not include any breaking changes.
What needs to be documented once your changes are merged?
-Also, the line number 18 & 19 in Readme.md file ,both anchor tag and img. src are not working. I tried to solve it but I was not able to solve it.
-So, can you help me with this issue. I would be happy to contribute.

Sorry for delay, already fixed in master, anyway thank you


link on subscribe feed button is incorrect

I assume this will be changed when moved over?

Fixed- http://testmozilla.wpengine.com/hacks/ now uses the wordpress feed helper so should point to the right place.


Array#groupBy...) should take (value, index, array) as parameters

In order to be consistent with all the other array methods, there will be use cases where we want to use the item's index, or look at other items in order to decide the return value for this item.
const numbers = [1, 2, 3, 4];
numbers.groupBy((num, index, arr) => {
  return num % 2 === 0 ? 'even' : 'odd';
});

Also, here's a similar functionality that I'm relying on heavily in my projects which groups an array of objects that have a similar field:
import _ from 'lodash';
import * as Objects from './helpers/objects.js';

const { get } = _;

/**
 * groups by one or multiple fields
 *
 * @param {Array} items - The array of items to be grouped.
 * @param {Array<String>} fields - The array of fields to group items by.
 */
function groupBy (items, fields) {
  const groups = {};

  items.forEach((object) => {
    const groupValues = fields.map(field => get(object, field));
    const groupKey = Objects.safeJSONStringify(groupValues);

    groups[groupKey] = groups[groupKey] || [];

    groups[groupKey].push(object);
  });

  return Object.values(groups);
}

export default groupBy;

What do you mean? I'm not sure that I understood your examples, but .groupBy already accept (value, index, array) as the callback parameters:

In order to be consistent with all the other array methods, there will be use cases where we want to use the item's index, or look at other items in order to decide the return value for this item.

We already pass value, index, array parameters, precisely to make it consistent with other Array iteration methods.

My bad, I assumed that it was the item's index because in the code example in README called the variable i.
I changed that in #25.


Epic / Planning Ticket for Agent Scenario Management

The purpose of this ticket is to identify and work through challenges as it relates to the agent scenario management that we want to do. It is not dissimilar to https://github.com/Sifchain/sa-eliza/issues/8 in that we expect it to contain many different posts and be iterated on extensively. Out of it, specific tickets for implementation or execution will pop out.
All of the tickets below will, in one way or another, be addressed on this planning ticket.
Here is the first LLM message on the subject
Scenario Planning, Testing, and Integration Testing for Eliza Agents:
Your goal is to establish a robust and reliable testing framework for Eliza agents, enabling you to:

Validate agent behavior in various scenarios: Ensure agents perform as expected in different situations and conversations.
Identify and fix bugs early:  Catch and address errors during development, before they impact users or the live system.
Facilitate continuous deployment:  Confidently deploy new code and features, knowing that they have been thoroughly tested.
Evaluate agent decision-making:  Assess the quality of agent choices and actions within realistic scenarios.

Current Status and Challenges:

Initial Success: You've successfully achieved a working "hello world" setup with the Chronis character, a critical first step in setting up a testing environment.
.env File Management:  You've identified the need for individual .env files for each developer to avoid conflicts and enable independent work.  This requires clear documentation and a streamlined setup process.
Centralized Test Execution:  A centralized system is needed for running tests consistently, ideally triggered by pull requests and merge events.  The nature of .env files might necessitate a closed/dedicated system for test execution rather than a standard CI/CD pipeline.
Development Environment Consistency:  Clear documentation and procedures are required to ensure consistency in development and testing environments across the team. This includes specifying OS requirements, software versions, and any necessary setup steps.
Single Source of Truth for Resources:  A separate, Sifchain-owned repository is recommended for managing character files, setup instructions, and other project-specific resources.  This establishes a single source of truth and simplifies version control.
Git Workflow Policy: A clear git workflow policy, likely based on a forking model, is essential for managing contributions, staying in sync with the upstream Eliza project, and separating concerns effectively.
Remaining Runtime Errors:  Existing runtime errors need to be resolved before focusing on new plugin development. This prioritizes stability and reliability of the core framework.

Action Items and Next Steps:

Documentation for Development/Testing Environment Setup:  Create comprehensive documentation that outlines the steps for setting up a consistent development and testing environment.  This should include:

Required software (Node.js, pnpm, etc.) with specific versions.
OS requirements and recommendations (including WSL2 for Windows users).
Steps for creating and configuring individual .env files.
Instructions for cloning and setting up the project from the Sifchain-owned repository.
Explanation of the chosen Git workflow and branching strategy.

Implement Centralized Testing System:  Set up a dedicated system for centralized test execution, triggered by pull requests and merges.  Determine the best approach for managing .env files within this system (e.g., secure environment variables, encrypted files).  Ensure that the test execution procedure is identical for both local development and CI/CD (even if run in a closed system).  Consider using a containerized environment (Docker) for consistency and reproducibility.

Create Sifchain-Owned Repository for Resources:  Create a dedicated repository for managing character files, setup instructions, scripts, and other project-specific resources.  Update the documentation to reference this repository as the single source of truth.

Formalize Git Workflow Policy: Document the specific Git workflow and branching strategy for the project.  Train the team on the established procedures.  Ensure the policy aligns with the forking workflow and enables effective collaboration with the upstream Eliza project.

Prioritize and Resolve Runtime Errors:  Create specific tickets for each remaining runtime error and prioritize their resolution before proceeding with new plugin or feature development.

Develop Comprehensive Scenario Tests: Once the core framework is stable, shift focus to developing comprehensive scenario tests for agents.  This involves:

Identifying key scenarios and user stories to test.
Implementing test cases using a suitable testing framework (Jest).
Defining expected agent behavior and responses within each scenario.
Incorporating media, attachments, and other relevant data into test scenarios.
Regularly reviewing and updating scenario tests as new features are developed.

Agent Decision-Making Evaluation and Refinement: Develop methods for evaluating the quality of agent decisions in freeform scenarios using the OODA loop. This could involve:

Defining metrics for decision quality (e.g., alignment with goals, efficiency, risk avoidance).
Analyzing logs and conversation histories to identify patterns in decision-making.
Implementing mechanisms for providing feedback to the agent and refining its decision-making processes (e.g., reinforcement learning, supervised fine-tuning).

Long-Term Scenario Planning:

Develop a long-term strategy for agent scenario planning, considering the evolving needs of the project and the anticipated capabilities of future agents.
Explore more advanced testing methods, such as simulations and adversarial testing, to evaluate agent behavior in complex, dynamic environments.
Consider the role of lore and character development in shaping agent scenarios and goals.

By addressing these action items and prioritizing the development of a robust testing infrastructure, the Reality Spiral team can significantly improve the reliability and effectiveness of their Eliza agents and build a solid foundation for future innovation.

We can probably get a grant from various places for cheap or free hosting plus credits. We need to be forward-looking and imagine hosting our own models like Llama, etc. There's going to be a fair bit of forward thinking related to where we deploy. We can have a temporary home and then do some research and then move our home, but we at least need to keep in mind that there are incentives for AI projects from cloud providers.

We will Want to ask every service provider or whoever installed or added a plugin for a particular service provider to give us API keys for services that we can run on our testing environment. We'll need to provide a few ourselves.


IDToken now parses using nimbus-jose

See title

Upstream changes in MSAL needed to make this work in unit tests

@addev-ashish I wasn't planning on resolving the ClientInfo case as part of this PR. If you'd like to see that change here lmk, otherwise I'll stick with the simple IdToken parsing case

@addev-ashish Feedback addressed


Fixed wind speed not showing

Changed variable wind_average to windSpeed
windSpeed seems to be the variable name passed by most drivers into weewx for the current wind speed.
Was originally showing /... in the aprs wind speed data field with an Acurite station.

I've reached out to the developer. Not sure where they are, but I've forked and updated with all the other pull requests on this repo: https://github.com/savagebread/weewx-aprs


Shows in Telescope

After starting nvim and immediately starting telescope the virtual text is present in telescope.
It is not present after closing and reopening.

Where does modname: string come from?

strange. not reproduce. Could you record a short clip? also, the way you trigger telescope if you using customised keymap in insert mode.

I think it's due to the syntax being used here:
require "user.keymaps"
require "user.plugins"
require "user.autocommands"
require "user.colorscheme"
require "user.cmp"
require "user.navic"
require "user.lsp-inlayhints"
require "user.lsp"

If I include the parens the issue doesn't occur:
require("user.keymaps")
require("user.plugins")
require("user.autocommands")
require("user.colorscheme")
require("user.cmp")
require("user.navic")
require("user.lsp-inlayhints")
require("user.lsp")

well, this is really strange. Both should work fine.

@ChristianChiarulli
I disable the signature for Telescope file type. Could you check if it works for you? Thanks.


Merge multiple configuration files

Add configuration file path in /etc/uyuni/uyuni-tool.yaml and merge all configuration files we find. This would be needed for cloud version to define default images locations.

Discussion wrt. opensuse<EMAIL_ADDRESS>


Arbitrary arguments

This library looks fantastic, nice work @jakeheis!
Does it support the ability to parse arbitrary arguments? I'll give an example:
mint run jakeheis/ice ice add RxSwift

mint is the executable
run is a command in mint
jakeheis/ice is an argument in run
The rest are arbitrary arguments that will need to be parsed somehow for later use
If there's some way to do that, I'd love to integrate this

Thanks I appreciate it!
Yes it does through, collected parameters. It would look something like:
class Run: Command {
   let name = "run"

  let repo = Parameter()
  let remaining = OptionalCollectedParameter()

  func execute() throws {
    print(repo.value) // jakeheis/ice
    print(remaining.value) // [ice, add, RxSwift]
  }
}

Nice!

Ahh this is interesting. I wonder if perhaps commands with collected parameters should stop trying to recognize options once collection has begun. This would be a breaking change, but I think it would be a smart one to make in SwiftCLI 5.0.0. I can't really think of an instance where after a collected parameter has begun collecting the args that options should still be recognized


No output of InstructBLIP-vicuna

I run InstructBLIP successfully when LLM is flant5xl or flant5xxl, but when I switch LLM as vicuna-7b-v1.1, the output is a string of nothing(['']). Actually, when I use vicuna-7b-v0, there are some reasonable outputs (like 'the image features ...', 'in this image, there is ...' ), but sometimes repeated answer or '### Assistant: ....' happens.

Please use Vicuna v1.1 instead of v0.
Related issue #297


[select] grouped select headings overlap each other when there is a scroll involved

When we scroll in the grouped select dropdown, the group names overlap with each other.
The easiest solution would be to apply a solid color background to the headings. ( ListSubHeader )

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
It overlaps other headings when scrolled down.

Expected Behavior 🤔
I should not be transparent and overlap

I can create a PR to fix this, a background color needs to be applied to the ListSubHeader
Steps to Reproduce 🕹
create a grouped list item with enough options

Live example:
https://stackblitz.com/edit/gmyadm?file=demo.js
Steps:

create a grouped select
create a long enough link

Context 🔦
headings overlap in scroll in longer lists

Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 15.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.5.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 88.0.4324.182
    Edge: Spartan (44.19041.423.0), Chromium (88.0.705.74)
  npmPackages:
    @material-ui/core: ^4.9.7 => 4.11.2
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.57 => 4.0.0-alpha.57
    @material-ui/pickers: ^3.2.10 => 3.2.10
    @material-ui/styles:  4.11.2
    @material-ui/system:  4.11.2
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react:  17.0.0
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    styled-components: ^5.2.1 => 5.2.1
```
  Don't forget to mention which browser you used.
  Output from `npx @material-ui/envinfo` goes here.
```

another solution could be making ListSubheader non-transparent or adding some kind of " isTransparent " prop to it.

or just editing the docs and apply a background color to each ListSubHeader ...
I can work on either solutions

Duplicate of #18200

@oliviertassinari While this is a duplicate of the 2nd bug reported in #18200, that issue did only resolve the 1st bug but not the 2nd with stacking ListSubheader components.
I just experienced the same issue and I did not see any proposed solution in that issue.

I just ran into this overlapping issue of ListSubHeader and found out that you can disableSticky={true} as a prop to the ListSubheader component like so:
<ListSubheader disableSticky={true}>{customer?.text}</ListSubheader>


Change type of size from int to long.

PR Summary
There is a miniscule changeset, changing the type of $size from int to long in VSTeamGitRepository.ps1
PR Checklist

[-] Write Help
[-] Write Unit Test
[-] Update VSTeam.psd1
[x] Update CHANGELOG.md

Reviewing now. Thanks for the support.


Disable syncing to Maven Central for now

Enabling syncing creates a situation where the plugin needs to wait until publishing of the version finishes on Bintray, but that takes longer than the request timeout, so we get failed builds that look like https://travis-ci.org/openzipkin/zipkin/jobs/76344895
At the same time, re-enable uploading of "big" artifacts (tars, fat jars)

+1


Integrating prime vue component

So, in the page folder under the resources, we created the Vue app instance with primevue (for styling) in the body.html.
So the Vue components are rendering. But when we edit the Vue components after clicking submit button in the Edit dialog box the Vue instance or the javascript that is responsible for Vue components, it is not rendering. But I see my changes coming as a response from rootcontainer.html. I believe the Vue thing is not persisting after an edit submission, but we can see the changes after a refresh.
Is there any way or idea to implement Javascript (Vue) in WebSight so that the Vue thing remains after editing?
For referenece, we also raised the issue in Starter comuninty
https://github.com/websight-io/starter/discussions/78

Any examples? Links to code?

Can't we load Vue on document ready state changes?

Please refer to this issue. https://github.com/websight-io/starter/discussions/78 here you can find code samples.
I think we can only load the vue instance when creating the app for the first time.

I Checked that.
Sample code
document.onreadystatechange = () => {
    if (document.readyState === "complete") {
      initApplication();
    }
  };

This initApplication is only triggered the first time when clicking the submit button on the dialog nothing gets triggered, tried adding the consoles, but only for the first time, or when I refresh the page these get printed.


fix: don't disown replicas from faulted volumes and recreate faulted nexuses

fix: don't disown replicas from faulted volumes
Don't attempt to disown replicas if the replica volume is faulted.
Don't disown replicas if the volume target (nexus) contains the replica.
Update the replica owners on core-agent startup - we might get drop the replica nexus owners at
some point since we have obtain then from the nexus specs.
Resolves: CAS-1295

chore: don't trace reconciliation unless TRACE is set or there is work to do
For clusters with high number of volumes there are a lot of traces being sent that sometimes
seem to overwhelm the telemetry exporter.
During reconciliation we should not create spans needlessly unless we're on TRACE level or unless
the reconciler actually did work.
TODO: We need a generic strategy to cater for this

fix(nexus): recreate faulted nexuses when appropriate
When the healthy replicas of a faulted nexus are Online we should attempt to recreate said nexuses.
This is done by first destroying the faulted nexus. The missing nexus reconciler will then recreate
the nexus.
When no healthy children are available, the faulted nexus are left behind until such time the node
crashes or the volume is unpublished.
Resolves: CAS-1296

bors try


Dependency conflict with mkdocs-material

When using mkdocs-material-8.1.11+insiders.4.8.3 and installing mkdocs-markmap (version 2.2.0) I get this:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
mkdocs-markmap 2.2.0 requires requests==2.25.1, but you have requests 2.27.1 which is incompatible.

requests dependency was changed to <3. Also, this issue is rather related to pip usage, not the project itself.
Retry with v2.2.2


Start hg38 branch

Started the feature branch for the hg38 reference genome. This only contains small changes from the Beagle feature branch with changes to the major config file and the artifacts file.

Unfortunately, all these changes make it hard to change back to hs37d5. The workflow will have to run on different assemblies. Or how do you see that, @GWarsow ?
One option to avoid this is to have hg19 and hg38 specific configuration values and refer to them in the actual configuration values used in the workflow. A pattern that is already used throughout multiple Roddy workflows.
Another option maybe assembly-specific configuration values in an assembly-specific configuration files. Something like the following, where assembly-specific configurations import a "common" configuration. The assembly-specific configurations then only contain the "cvalue"s needed for that assembly.
hs37d5 configuration:
<configuration name='copyNumberEstimationAnalysisHs37d5'
                       description='CNV Calling for NGS data -- hs37d5.'
                       configurationType='analysis'
                       ...
                      imports="copyNumberEstimationAnalysisCommon"
	              ...>

GRCh38 configuration:
<configuration name='copyNumberEstimationAnalysisGRCh38'
                       description='CNV Calling for NGS data -- GRCh38.'
                       configurationType='analysis'
                       ...
                      imports="copyNumberEstimationAnalysisCommon"
	              ...>

common configuration:
<configuration name='copyNumberEstimationAnalysisCommon' description='Common parameters for CNV Calling for NGS data.'
                      configurationType='project'
                       ...
                      imports="commonCOWorkflowsSettings"
	              ...>

When setting up an analysis, e.g. the ` has to be used.


adding hash creation separately

Fixes #2

I put a wrapper function around crypto to create a hash ./sha1.js
I put a wrapper function around sha.js (which imports only sha.js/sha1) to create a hash ./browser/sha1.js
standard!

It goes from 106k to 63K - however this is still a lot for such a library - do we really need sha?

The sha is part of the algorithm, so we need it. But jsonld.js contains a small sha1 implementation for the browser. I removed it in rdf-normalize, because I thought jsonld.js just uses it to avoid a browserify build step.
I had already gitter chat with @dlongley. He want's to restructure jsonld.js. The normalize part could become a separate module. So we would have to solve this only once. That would be the long term solution.

The commit contains also many changes in jsonld-normalize.js, beside the sha1 module import. That's all from the standard format, right? I should have added a comment. The code is based on jsonld.js. I tried to avoid any unneeded changes to simplify importing related patches from that project in the future.

ok I can revert standard - but leave the import properly - this change is needed - even if it is a temporary fix

Once I've refactored the RDF Dataset Normalization stuff into its own module, we'll split things up further as needed (that includes SHA-1 and SHA-256, etc.)

fixed in #4


Ambiguity in content

"Private Link service can be accessed from approved private endpoints in any public region. The private endpoint can be reached from the same virtual network and regionally peered virtual networks. The private endpoint can be reached from globally peered virtual networks and on premises using private VPN or ExpressRoute connections."
"The private endpoint can be reached from... on premises"
It sounds very much like you are using "the private endpoint" to refer to the private link and not to "approved private endpoints". If that's so, this is very confusing. If not, why would I want to reach an approved private endpoint" from on-premises.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fb4b8145-27ae-8817-6d85-969aa85e601d
Version Independent ID: 00f897cd-5c20-cb3b-9c17-5f75eddd1715
Content: What is Azure Private Link service?
Content Source: articles/private-link/private-link-service-overview.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

@degrover-cn
Thanks for your feedback! We will investigate and update as appropriate.

Actually, on reading further I misunderstood. Communications do go through the PE to the PL.
I appreciate your time, and apologize.
--Russell

From: Naveenommi-MSFT @.>
Sent: Wednesday, February 14, 2024 10:14 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Russell H. DeGrove @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Ambiguity in content (Issue #119856)
@degrover-cnhttps://github.com/degrover-cn
Thanks for your feedback! We will investigate and update as appropriate.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/119856#issuecomment-1945297900, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM2X5S2OHISX4QAYFOAW74DYTV4TDAVCNFSM6AAAAABDI4WDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVGI4TOOJQGA.
You are receiving this because you were mentioned.Message ID: @.***>

@degrover-cn
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation


Custom WAFFLE_FLAG_MODEL not working after 0.15

I have added a custom waffle flag which inherits from the AbstractBaseFlag and doesn't have a users field. After upgrading waffle to a newer version I get the following error during startup:
Traceback (most recent call last):
  File "manage.py", line 30, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 377, in execute
    django.setup()
  File "/usr/local/lib/python3.8/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/local/lib/python3.8/site-packages/django/apps/registry.py", line 122, in populate
    app_config.ready()
  File "/usr/local/lib/python3.8/site-packages/waffle/apps.py", line 9, in ready
    import waffle.signals  # noqa: F401
  File "/usr/local/lib/python3.8/site-packages/waffle/signals.py", line 7, in <module>
    @receiver(m2m_changed, sender=get_waffle_flag_model().users.through)
AttributeError: type object 'Flag' has no attribute 'users'

The docs say that the Flag needs to be a subclass of AbstractBaseFlag yet the signal receiver is accessing the users field which is only found in AbstractUserFlag. I'm guessing this is the breaking commit: afb2660449d. How should I go about this problem?

My current workaround to get the app running:
class Flag(AbstractBaseFlag):
    class MockM2MRelation:
        through = None

    users = MockM2MRelation()
    groups = MockM2MRelation()
    # ...


Remove help override in ScholarSphere for collection

Remove the oveeride once this ticket is closed: projecthydra/sufia#1057

Checked this with 6.3.0  Either we have additional overrides, or the sufia implementation is incorrect.

remove bccb0fb86596fe1af5fefed40293b799479b7b08

backported in projecthydra/sufia#1525


Create User table and database

[x] #16
[ ] Add Quiz table
[ ] Table/column to store user's scores

I created a new branch based on main for working on the user-table database. Only worked on the User class and a controller to populate the table with OAuthentication info (current @getmapping and return are just placeholders). I'm not sure if the token properties in class will be necessary.

Outdated. Design changed for Admin view and Users table


Running binary with only the argument tla causes panic instead of giving warning to user.

Bug:
Running binary ./modelator tla panics.
Expected:
./modelator --help gives
SUBCOMMANDS:
    apalache    Generate TLA+ traces using Apalache
    tla         Generate TLA+ test cases and parse TLA+ traces
    tlc         Generate TLA+ traces using TLC

so it is expected that a user will try to pass only tla arg.
Log:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', modelator/src/cli/mod.rs:29:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Additional info:
Tested on release in versions 0.2.0 and (06ed539eb) latest

Fixed by https://github.com/informalsystems/modelator/commit/e4a94f9c9b448fea305ff1f33a65ea5463e3bbe3; closing


fix(ingestion/mongodb): MongoDB source unable to parse datetimes with years > 9999

… years > 9999
Closes #10079
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Looks like CI is failing
FAILED tests/integration/mongodb/test_mongodb.py::test_mongodb_ingest - datahub.ingestion.run.pipeline.PipelineInitError: Failed to configure the source (mongodb): Unknown option codec_options


Daijiho  demanding retroarch plus but it can't be installed on my phone

I have two samsung phones, on the newer one, s21fe daijisho works fine, but on the older one s10, it opens google pay store and obviously wants me to install retroarch plus, but play store says it can not be installed because it was built for an older version or android...i'm not sure why this is happening, i've installed retroarch on both devices from retroarch website(nightly build), and it's enough for s21fe, but not good for s10....

RetroArch Plus isn't required or even recommended. Use the builds available in the buildbot. Then switch player within the platform page if needed


Added support for string interpolation. Fixes #20

This PR provides a mechanism for support printf-like formatting. Strings have been formatted with util.format().
Fixes #18 , #20

Awesome PR!

@novddd A couple of tweaks and it will be good to go 🚀

Soon I will do requested changes.

Awesome work! Huge thank you for all your time and effort! 🎉


controller/ home routes(candidates' votes, one candidate profile, create candidate)

get candidates' votes, get one candidate profile, vote for a candidate, create candidate,


Fix handling of paths on Linux and Mac (issue #54)

Linux and Mac use a forward slash instead of a backslash to separate
directories. This change makes use of the Path.DirectorySeparatorChar
instead of hardcoding backslash. This allows to use the same code on
all platforms.
This change also adjusts the WindowsNameTransform tests so that they
also work cross-platform.
Incorporated in this PR is #52.

What's the status of this PR? Is it likely to be accepted soon?

Bump.  Any update on this getting merged?

WindowsNameTransform was never intended to be generic a clue being the name including Windows but this works fine.  It would be good to rename the class but this itself causes issues.

My Contribution is licensed under the MIT License.


Add daemonset support to Kubernetes Entrypoint init-container

This commit adds support for daemonsets to the Kubernetes-Entrypoint init-container.
It also makes two other changes:

Moves the entrypoint container manifest snippet to its own file to reducle loading on the _funcs.tpl file
changes dep-check-init-cont to dep_check_init_cont to match the formatting of other defines used in OpenStack Helm

This change is

Superceeded by https://github.com/att-comdev/openstack-helm/pull/137


Add clean up logic for version and connection-info reconcilers

Description
In previous refactors we added a few TODOs about cleaning up after ourselves.
Here, I added/improved the cleanup for 2 reconcilers + 1:

version
connection-info
+1, kubesystemUUID now is only set once per DynaKube as it should never change, this way we save a request per reconcile

The improvement is not final as:

ActiveGate conditions are missing, as they are added in https://github.com/Dynatrace/dynatrace-operator/pull/2923

So the AG connection info clean-up is not as "clean" as the OA connection-info (only ping the API if there is actually something to clean up)

Istio reconciler still needs to be updated
authToken reconciler still needs to be updated (it also will have its own condition, and might make sense to fix the cleanup in that PR)

I think this is a big enough change for now, further improvements will have separate PRs.

(easier to review, and if we want a different "style" of doing this, I would prefer to not have to rework everything 😅 )

How can this be tested?
Deploy dynakubes, and turn on/off OA and AG. See that the related conditions and secrets are removed/created.

only version, and connection-info related stuff should be affected

Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
Attention: Patch coverage is 63.82979% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 67.16%. Comparing base (f0ac5fe) to head (fc7b866).
 Consider uploading reports for the commit 6eb3d62 to get more accurate results

Files
Patch %
Lines

pkg/util/kubeobjects/secret/secret.go
0.00%
7 Missing :warning:

pkg/controllers/dynakube/activegate/reconciler.go
42.85%
2 Missing and 2 partials :warning:

...ers/dynakube/connectioninfo/oneagent/reconciler.go
50.00%
2 Missing and 2 partials :warning:

...s/dynakube/connectioninfo/activegate/reconciler.go
71.42%
1 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2942      +/-   ##
==========================================
- Coverage   67.23%   67.16%   -0.07%
==========================================
  Files         262      262
  Lines       14190    14218      +28
==========================================
+ Hits         9540     9549       +9
- Misses       3837     3852      +15
- Partials      813      817       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Environments

Not sure what the right value of process.env.WEB_ENV is, but something like this to toggle staging/prod

Added in 2e075bb50552725ca7d4b9774f74861c8a63e91e
<a target="_blank" href={`https://${process.env.NEXT_PUBLIC_DEV_MODE == 'true' ? 'staging' : 'payments'}.branta.pro/v1/verify/${invoiceInfo.invoice}`}>


Preview pane should be much taller.

Fixed, issue was caused because Chrome needs a specific height for nested flexboxes while Firefox does not.


⚠ Bofrost.gr has degraded performance

In a3387e2, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 2423 ms

Resolved: Bofrost.gr performance has improved in 4a17aae.


Inline and hover mouse intellisense is not working in the editing area when python debuging

VSCode Version: 1.47.3
OS Version: win10 1909

Steps to Reproduce:

Debugger: python
Debug Inline value is true.
As shown in the figure below, there is a bug that the prompt arrow disappears in the editing area and the mouse is hovered to the variable without any prompt.

Does this issue occur when all extensions are disabled?: Yes/No
No

/extPython


feat: YouTube Music Desktop App Integration

Prerequisites

[X] I have read and understand the CONTRIBUTING guide
[X] The commit message follows the [conventional commits][cc] guidelines
[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)

Description
Shows the currently playing song in the YouTube Music Desktop App.
Sample Configuration:
{
  "type": "ytm",
  "style": "powerline",
  "powerline_symbol": "\uE0B0",
  "foreground": "#ffffff",
  "background": "#FF0000",
  "properties": {
    "prefix": "\uF16A ",
    "playing_icon": "\uE602 ",
    "paused_icon": "\uF8E3 ",
    "stopped_icon": "\uF04D ",
    "track_separator" : " - "
  }
}

Closes #170

Closes #174

I'm going to review asap. Thanks for doing this 🙏🏻

@KyleCrowley are you still interested in finishing this?

@KyleCrowley are you still interested in finishing this?

Yes. Apologies, haven't had a chance to work on this yet.

No pressure, take your time. Just wanted to know. We're not in a rush.

@KyleCrowley you can find the update version of this in my new PR #206 ;-)


server: limit metastore checkpoint starvation

Are you still working on this @LucioFranco ? If not, please close the PR.


Add tests for mixing signals and coroutines

We run two coroutines, one sending signals to current process, and one
receiving them from a signal pipe. A signal handler is feeding received
signals into the pipe. To make the tests little harder, we create new
coroutines for each signal.
Submitted under MIT license.
Signed-off-by: Nir Soffer<EMAIL_ADDRESS>

Merged. Testing it on FreeBSD now...

Tests pass!


Added Sematext to the list of monitoring tools

We have integrations for both metrics and logs, so I added both links.

@radu-gheorghe Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@radu-gheorghe Thank you for signing the Contributor License Agreement!

Thank you!


Add custom uid gid

Added two environmentflags: PUID/PGID for setting the UID/GID of the created user. This is a nice to have feature, making config and data files (exposed volume) readable by a desired host user, based on uid/gid.

Hi, I am using https://github.com/docker-library/ghost/blob/3332df18c9d6a11ba0d227b667ba27733a44fafe/3/alpine/Dockerfile  and it seems that id have been removed.


[docs] add runtime abstraction layer doc

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.kevin.zwy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


TransformerTorchEncoder index error

encode.yml:-
!TransformerTorchEncoder
with:
  pooling_strategy: cls
  pretrained_model_name_or_path: distilbert-base-cased
metas:
  on_gpu: true

Hey @Kavan72,
can u check if u have these versions?
transformers==4.0.1
torch==1.7.1

even after installing same version still not working

can u share a minimum example with the list of versions (jina, transformers, etc...) so that we can reproduce?

https://github.com/Kavan72/jina_test check this

Hey @Kavan72 ,
I have been able to reproduce the issue.
There is a problem with dimensions when batch_size is 1. As a workaround to serve your purpose, I recommend that you can increase the batch_size > 1

@JoanFM thank for you time and it's working with >1 batch_size

Hey @Kavan72 , #1501 should also fix for batch_size 1

Closed by #1501

thank you


docs: update changelog to include link to migration guide

Give changelog a link to migration guide. Also, update dev dependency so it plays better with the new TS version.

:tada: This PR is included in version 4.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add visual differences to new and edit taxon pages

It is not clear if we are creating or editing a taxon from a user perspective.
This commit makes sure we have callout divs on the page with color and text
indications, making sure we differentiate between the 2 pages.
Trello: https://trello.com/c/CMul4Ru3/112-improve-how-we-differentiate-between-the-new-taxon-and-edit-taxon-forms-s
The new page looks like this:

The edit page looks like this:

Looks good, some minor naming-related feedback. 👍

Come to think of it, I think this PR is pending some further updated following a chat with Mark Hurrell. Will speak to @carvil about this tomorrow when he's back from leave.

@mobaig thanks for your comments. I've fixed the naming issues and updated the screenshots (they were old and didn't reflect other stuff that went into master). Please let me know what you think.

👍


Vault rename command

Please Select if your Request is Either something new or an Enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[x] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
Renaming a vault today is cumbersome - you have to change it in multiple places and it's not guaranteed to work.
Describe the solution you'd like
A vault rename command that updates it in all required places (yml, code-workspace) and reloads the window so it's all in one step.

This issue is featured in this week's round of CROP voting on Dendron's Discord server.