certbot error and codiusd not running

Hi i run a check on errors and below are the status and errors found. how do i resolve this ? My certificate have not expired yet.
[WARN] : It's look like codius is not running as expected ...
[+] Start Debuging ...
........................................
. Checking required installed packages .
........................................
------------------------------------------
PACKAGE              STATUS
------------------------------------------
node                 ✔
npm                  ✔
hyperd               ✔
hyperctl             ✔
moneyd               ✔
codiusd              ✔
certbot              ✘
......................................
. Checking required running services .
......................................
------------------------------------------
SERVICE              STATUS
------------------------------------------
hyperd               ✔
moneyd               ✔
codiusd              ✘
nginx                ✔
[?] Creating full services log file ?
[WARN] : With this action all codius services will be restart for debuging

Do you want to continue ? [y/N]: y

[!] Stoping services...
[!] Execute services and commands in debug mode ...
[*] This will take some time ...
[!] Killing debug proccess ...
[+] Starting services...
=============================================================================================================================================
[!] The Debuging Proccess is done .

[-] Please check /tmp/codius_debug-2018-07-12.15-46 for full log output

Hey please sent the content of the log file included in /tmp/codius_debug-2018-07-12.15-46
you can use code tag for better display

How do I retrieve it ? I was prompted permission denied

run
sudo cat /tmp/codius_debug-2018-07-12.15-46 | nc termbin.com 9999
in the end it's gives you a link , send it here

==================================
node -v ; npm -v ; yarn -v
v10.6.0
6.1.0
1.7.0
==================================
hyperd run -t test /bin/sh
time="2018-07-12T15:46:51Z" level=warning msg="devmapper: Usage of
loopback devices is strongly discouraged for production use. Please
use --storage-opt dm.thinpooldev or use man docker to refer to
dm.thinpooldev section."
time="2018-07-12T15:46:51Z" level=warning msg="devmapper: Base device
already exists and has filesystem xfs on it. User specified filesystem
will be ignored."
time="2018-07-12T15:46:51Z" level=info msg="[graphdriver] using prior
storage driver "devicemapper""
time="2018-07-12T15:46:51Z" level=info msg="Graph migration to
content-addressability took 0.00 seconds"
time="2018-07-12T15:46:51Z" level=info msg="Firewalld running: true"
==================================
hyperctl info
Images: 3
Containers: 0
PODs: 0
Storage Driver: devicemapper
Pool Name: docker-8:1-677388-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 1.1 GB
Data Space Total: 107.4 GB
Data Space Available: 4.989 GB
Metadata Space Used: 2.146 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.145 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/hyper/devicemapper/devicemapper/data
Metadata loop file: /var/lib/hyper/devicemapper/devicemapper/metadata
Library Version: 1.02.146-RHEL7 (2018-01-22)
Hyper Root Dir: /var/lib/hyper
Index Server Address: https://index.docker.io/v1/
Execution Driver:
Total Memory: 3.623 MB
Operating System: CentOS Linux 7 (Core)
==================================
hyperctl list
POD ID              POD Name            VM name             Status
==================================
moneyd xrp:start
                                                                       88
                                                                       88
                                                                       88

88,dPYba,,adPYba,   ,adPPYba,  8b,dPPYba,   ,adPPYba, 8b       d8  ,adPPYb,88
88P'   "88"    "8a a8"     "8a 88P'   "8a a8P_____88 8b     d8' a8"    Y88 88      88      88 8b       d8 88       88 8PP"""""""  8b   d8'  8b       88
88      88      88 "8a,   ,a8" 88       88 "8b,   ,aa   8b,d8'   "8a,   ,d88 88      88      88  "YbbdP"'  88       88  "Ybbd8"'     Y88'     "8bbdP"Y8
d8'
d8'
starting moneyd
2018-07-12T15:47:22.133Z connector:route-broadcaster info generated
random routing secret.
2018-07-12T15:47:22.139Z connector:accounts info add account. accountId=parent
2018-07-12T15:47:22.142Z connector:accounts warn DEPRECATED: plugin
accessed deprecated _log property. accountId=parent
2018-07-12T15:47:22.142Z connector:accounts info add account. accountId=local
2018-07-12T15:47:22.162Z connector:accounts warn DEPRECATED: plugin
accessed deprecated _log property. accountId=local
2018-07-12T15:47:22.162Z connector:accounts warn DEPRECATED: plugin
accessed deprecated _store property. accountId=local
2018-07-12T15:47:22.162Z connector:accounts warn DEPRECATED: plugin
accessed deprecated _store property. accountId=local
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:23.236Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 1)
(node:22311) [DEP0018] DeprecationWarning: Unhandled promise
rejections are deprecated. In the future, promise rejections that are
not handled will terminate the Node.js process with a non-zero exit
code.
2018-07-12T15:47:23.559Z connector:app error Error: connection aborted
at Plugin.once
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:277:21)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:351:19)
at Plugin._emitDisconnect
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:539:12)
at WebSocketReconnector._ws.on
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:270:39)
at WebSocketReconnector.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:351:19)
at WebSocketReconnector._reconnect
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/ws-reconnect.ts:58:10)
at WebSocket._instance.on
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/ws-reconnect.ts:34:71)
at WebSocket.emit (events.js:182:13)
at WebSocket.emitClose
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/node_modules/ws/lib/WebSocket.js:211:10)
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:29.311Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 2)
==================================
moneyd xrp:info
fetching channels...
connecting to xrp ledger...
account: r3QRXAy2YqoZ8su8E8kzPJgyRWLnoxqnEZ
balance: 166.942231 XRP
index  destination                         amount (drops)  balance
(drops)  expiry
0      rK6g2UYc4GpQH8DYdPG7wywyQbxkJpQTTN  10000000        60000
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:35.374Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 3)
==================================
codiusd
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:41.446Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 4)
2018-07-12T15:47:41.709Z codiusd:App info starting codiusd...
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:47.515Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 5)
==================================
netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address
State       PID/Program name
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*
LISTEN      1099/sshd
tcp        0      0 <IP_ADDRESS>:25            <IP_ADDRESS>:*
LISTEN      1109/master
tcp6       0      0 :::22                   :::*
LISTEN      1099/sshd
tcp6       0      0 ::1:25                  :::*
LISTEN      1109/master
udp        0      0 <IP_ADDRESS>:323           <IP_ADDRESS>:*
322/chronyd
udp        0      0 <IP_ADDRESS>:68              <IP_ADDRESS>:*
573/dhclient
udp6       0      0 ::1:323                 :::*
322/chronyd
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:53.583Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 6)
(node:22311) UnhandledPromiseRejectionWarning: Error:
{"code":"F00","name":"NotAcceptedError","triggeredAt":"2018-07-12T15:47:59.654Z","data":"cannot
connect to blocked account. reconfigure your uplink to connect with a
new payment channel.","protocolData":[]}
at Plugin.callback
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:448:20)
at Plugin.listener
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:483:14)
at Generator.next ()
at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
at new Promise ()
at __awaiter
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
at Plugin._handleIncomingBtpPacket
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:336:16)
at Plugin.
(/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:336:18)
(node:22311) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 7)
codius-install.sh: line 992: 22311 Killed                  bash -c
'moneyd xrp:start'
codius-install.sh: line 992: 22358 Killed                  bash -c 'codiusd'
codius-install.sh: line 992: 22178 Killed                  bash -c
'hyperd run -t test /bin/sh'
On Fri, Jul 13, 2018 at 1:02 AM, N3TC4T<EMAIL_ADDRESS>wrote:

run
sudo cat /tmp/codius_debug-2018-07-12.15-46 | nc termbin.com 9999
in the end it's gives you a link , send it here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xrp-community/codius-install/issues/16#issuecomment-404581334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmzhkQa0ZlqzWEr5DR2ExGZHT9nnK2D7ks5uF4EfgaJpZM4VNRzO
.

It's look like there is a problem with moneyd

Stop all services

systemctl stop nginx moneyd-xrp codiusd hyperd

cleanup channel by running

moneyd xrp:cleanup

remove ~/.moneyd.json file

rm ~/.moneyd.json

reconfigure moneyd by running

moneyd xrp:configure

start all services again

systemctl restart nginx moneyd-xrp codiusd hyperd

also if this step dosen't help please post status of codiusd service as well
systemctl status codiusd -l

good luck

Check hostname on your shell. It should be identical to actual Codius-hostname. If they are, "[WARN] : It's look like codius is not running as expected ..." wll go away
hostnamectl set-hostname Your-Host-Name-Here

Hi
Problem can only resolve doing a fresh install.
Now codius server is running fine now version 1.1.3
On Fri, 13 Jul 2018 at 4:39 AM, Jon Nilsen<EMAIL_ADDRESS>wrote:

Check hostname on your shell. It should be identical to actual
Codius-hostname. If they are, "[WARN] : It's look like codius is not
running as expected ..." wll go away
hostnamectl set-hostname Your-Host-Name-Here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xrp-community/codius-install/issues/16#issuecomment-404643183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmzhkQdc3oQP36HTmIZuciuiuCIzwA7Pks5uF7P4gaJpZM4VNRzO
.


Roll Flutter Engine from ff471881e90a to 67a81550a48f (1 revision)

https://github.com/flutter/engine/compare/ff471881e90a...67a81550a48f
2024-04-19<EMAIL_ADDRESS>Add a dependency on package:web_socket in pkg_demo_test (flutter/engine#52239)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Update api-doc for channel.go

I hope my understanding is correct, especially the reason why argument checking is omitted.

@hachi8833 well actually we don't have any particular reason to avoiding argument check on #receive, just didn't put the checking logic 😅

Thank you for checking this!
I'd update them to add argument checking after merging this

@hachi8833 I think you can take this as a reference: https://tour.golang.org/concurrency/4


Any plan for v.8?

First of all: Awesome project! Thanks.
A note: the latest documentation is all about version 8, but the generator build a v6.
For example, some variables listed in http://trykickoff.com/learn/checklist.html aren't present.
Also, the workflow is builded around grunt and doc refer to gulp.
Users can become confused.
Can i help?

Hi @RobDesideri – We are currently working on updating the generator so that it is updated in line with v8 of the main repo – @mrmartineau has updated it to gulp and webpack (in the repo, but not published) and I need to update the generator to the latest version of Statix and then we should be able to publish it.
I’ll put together a list of tasks outstanding when I get chance this week, and that way if there’s anything you’re free to help with, more than welcome to help out with that – usually having help testing the generator is very useful.

Good. I look forward.

Just a small update on this issue – the v4 update on Statix is now complete.  We’ll be making sure these are reflected properly in the generator and then should be able to get the new version released.  Hoping to get this done this week, time allowing.


perf(dockerfile): xtrem awesome container size optimization

Hi @anthonyfok,
i just ask myself:

Few days before we talked about size matters and how to optimize it in #3730.
We started with 428M and optimized it to 277M.
What would you say to make it even a little bit smaller and give you a 27M Container without waiting for any Docker releases and just do it the good old way?

cheers maik

hi @anthonyfok,
#9ed48c1 thats the spirit!
you really squeezed the last bits out for the optimization - great!
hey what do you guys think about making a official repo for hugo?
would be nice to have some official hugo container on dockerhub.
like mentioned before i could help with the setup and maintain the docker things.
to be able to start doing that i guess i need at least be part of the team with read permission for the repo to create a automatic build. i have on my local machine quite some other useful things hacked together with docker-compose.yml which could be helpful for others as well (for example bring hugo server up, automatic compile sass with a super simple setup ...), so maybe create a docker repo for hugo with useful starter could be an option as well.
i maintain the Bash-it docker repo and there we moved the docker stuff to its own repo for example ...
but anyway, its up to you guys.
you can discuss about if you like the idea or not and ping me when you came up with a solution ...
cheers maiky


FSharp.Compiler.Tools should choose bundled .net core runtime for fsc

A .net core sdk can bundle different .net core runtimes, so fsc must run with the runtime bundled with sdk.
It doesnt matter for mono/.net (yet) because we expect net40 to beenough to run fsc.exe.
With .net core sdk 1.0, both runtimes (1.0 and 1.1) are bundled, but in some os just 1.1 is bundled (because FCT package just embedd netcoreapp1.0, it doesnt work for some os, ref https://github.com/dotnet/netcorecli-fsc/issues/76 )
Atm with .net core sdk 2.0, only the 2.0 .net core runtime is bundled.
So we need to:

get a fsc built for netcoreapp2.0 and embeed it in build/netcoreapp2.0 (ref https://github.com/dotnet/netcorecli-fsc/issues/92 )
understand how to choose the right version (this issue)

Atm if msbuild runtime is Core -> use build/netcoreapp1.0 (ref FSharp.Compiler.Tools.props#L37-L44, but that's not enough because bundled runtime can be 1.0, 1,1 or 2.0.
With sdk 2.0, we can use some new msbuild property to discriminate bundled runtime.
BundledNETCoreAppPackageVersion = 2.0.0-preview1-002101-00
BundledNETCoreAppTargetFrameworkVersion = 2.0
BundledNETStandardPackageVersion = 2.0.0-preview1-25227-01
BundledNETStandardTargetFrameworkVersion = 2.0

So probably BundledNETCoreAppTargetFrameworkVersion is enough.
@livarcocc @dsplaisted @eerhardt Any feedback on this ?
/cc @dsyme @cartermp
As a note, also DotnetCliToolTargetFramework = netcoreapp2.0 exists, but is maybe MSBuildRuntimeType = Core and BundledNETCoreAppTargetFrameworkVersion is better

How does fsc get invoked?  Is it through a CLI tool?  Or is it some other mechanism?
I think using BundledNETCoreAppTargetFrameworkVersion should be fine - this is pretty much what this property was designed to do - figure out the runtime that came with the SDK and is guaranteed to be there.
BTW - in 2.0, DotnetCliToolTargetFramework gets defaulted from BundledNETCoreAppTargetFrameworkVersion.
https://github.com/dotnet/sdk/blob/release/2.0.0/src/Tasks/Microsoft.NET.Build.Tasks/build/Microsoft.NET.Sdk.Common.targets#L31-L34
/cc @nguerrera to see if he has any dissenting opinions on using these properties.

@eerhardt fsc is published as FDD console app, and bundled inside package, so in build/netcoreapp1.0 for 1.0, in tools for net40 (backward compatibilkity otherwise was in build/net40).
And we use msbuild props to default the right fsc to use.
yes, i think too BundledNETCoreAppTargetFrameworkVersion is enough, i just want to know if here to stay for long term :D

But how is it invoked?
Where is the dotnet host retrieved from?
What are the arguments passed in?  Do you say dotnet fsc or do you say dotnet /path/to/fsc.dll?

the dotnet (for dotnet /path/to/fsc.dll ) is resolved as relative from Sdks here as
<_DotNetHostExecutableDirectory>$(MSBuildSDKsPath)/../../..</_DotNetHostExecutableDirectory>

for msbuild and mono, we just /path/to/fsc.exe and mono /path/to/fsc.exe so dotnet doesnt matter, we use fsc built for .net framework.
@eerhardt i already added https://github.com/Microsoft/msbuild/issues/1669 to ask about it, but no progress afaik.

I'm fine with using BundledNETCoreAppTargetFrameworkVersion. It is designed to be available to extenders.

@enricosada I think we can close this now, correct, given that the F# support is directly in .NET SDK 2.0?  I think FSHarp.Compiler.Tools is now only being used for .NET Framework/Mono execution of the compiler?


Add showIcons and maxSuggestionsToShow settings

Fixes https://github.com/Microsoft/vscode/issues/68557
/cc @jrieken

lgtm - I have pushed one more commit that simplifies the applying of styles. Using the toggleClass util. Thanks, this is ready to merge. We might revisit the name of maxSuggestionsToShow, depends on team feedback.

@jrieken Thank you very much!


[HUDI-3838] Move getPartitionColumns call out of executor to the driver

What is the purpose of the pull request
Minor improvement based on PR comment
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Closing in favor of https://github.com/apache/hudi/pull/5303


[Evaluated]: ZIP load model

Specify the model/test case you evaluated

[X] Model
[ ] Testcase

Name the model/test case ID, you would like to evaluate
141
What is the impact to the model or testcase?

[X] minor
[ ] moderate
[ ] major

Briefly describe your opinion about the model/testcase
I would remove this sentence: "The model does not take into account the time-response performance of the load, therefore it is not useful for dynamic studies."

Merged the changes into the main branch


consider GitHub language detection to ignore docs

Right now GitHub thinks that Nunjucks is the primary language. Technically not wrong, but a little misleading to glance at.
Reference: Instructions on overriding language detection

after adding all the remaining elements for v0.2.0 javascript is now the primary language on GitHub.


Multiple tasks and parallelism in runme run

In a discreet PR let's make it possible to run multiple commands optionally sequential and parallel available.
The rough idea is runme run one two three -p four five six -s seven eight nine (please note the presence of runme run as a subcommand for now).

cc @mxsdev. In the meantime, I will review the other suggested concepts, including relaxing the file-centricity @christian-bromann.

@christian-bromann
For implementation I think we should introduce two new functions which take the Runner interface  (internal/runner/client/client.go). Probably the most idiomatic way to do this is to introduce a struct, let's call it MultiRunner, which encapsulates some internal runner(s), and then to define methods on that. You create a multirunner by passing a []RunnerOption list, and each command run gets its own Runner instance.
The first function will be RunBlocksSerial. The implementation here is straight-forward: run each command one after the other, and exit if one of these commands fails.
The second function will be RunBlocksParallel. This implementation is less straight forward. Each call to RunBlock should have its own context and run in its own goroutine. We can use a WaitGroup here to wait for all goroutines to finish, and you'll also need to introduce a channel to pipe command results if you want to summarize them at the end.
It will also be absolutely critical that each execution has it's own stdin and stdout objects. You can accomplish this by connecting an io.Pipe() to the assigned stdout, stderr, and stdin. (This also gives us the opportunity to prefix each stdout line with the associated command's name, if we so wish)
You will also have to modify the Runner interface to allow "transformation" of the stdin/out objects - some method like WithTransformStdout which passes the current stdout and assigns the result would be a nice functional way of doing this in a way compatible with the RunnerOption paradigm. Then for each runner, you can create a new pipe and push/pull the necessary changes through that pipe, and all that logic could happen in the transform callback.
As for the command parsing, it would be very nice to keep manual parsing to an absolute minimum, ideally with everything being handled by cobra. I don't personally know all the limits of that library, but I implore you to read as much of the docs as possible before resorting to manual parsing.
I also anticipate some very complicated issues regarding stdin. You'll need to modify the current behavior of the runner clients in such a way that the multirunner cancels the stdin not once a single command finishes, but after they all finish.


	C:/Users/mattn/go/src/github.com/tensorflow/tensorflow/tensorflow/go/graph.go:153
main.main()
	C:/Users/mattn/go/src/github.com/mattn/go-object-detect-from-image/main.go:159 +0x577 fp=0xc00007ff60 sp=0xc00007fb98 pc=0x5ac4d7
runtime.main()
	C:/dev/go/src/runtime/proc.go:203 +0x21e fp=0xc00007ffe0 sp=0xc00007ff60 pc=0x43281e
runtime.goexit()
	C:/dev/go/src/runtime/asm_amd64.s:1375 +0x1 fp=0xc00007ffe8 sp=0xc00007ffe0 pc=0x45b4e1

This pull-request fix to not use memcpy. cc: @mdempsky

FY, the original panic isn't because of the new unsafe.Pointer checking that I added for Go 1.14. I suspect it's simply because of a mismatch between your installed versions of cmd/cgo and package runtime (the ABI changed in golang/go@e85ffec7). If you're still getting fatal error: can't happen errors after running make.bash, please file an issue at golang.org/issue/new.
That said, the current revision of the PR looks correct to me, and I think is a worthwhile improvement/simplification anyway.


Null Safety

Hi!
Thanks for this package, do you plan to migrate it to null safety?
Thanks
Best regards

I would also like to know this? Thanks!

I am already working on this. Thanks for your concern.


Implement Ignore attribute

When Ignore attribute is added to object's property it shouldn't be read or written.

Implemented as Skip attribute to avoid conflict with CSV library I'm using.


Use DSL inside actual DS python sample code

Hello,
I'm very happy that I passed through this amazing repo, thank you for your contributions.
I am already working with deepstream python samples, and have my application, but sometimes I need to use features as rtsp reconnecting or msgbroker, my question is do you know if I could build the pipeline with DS samples but use one or more features from your code ?
Or this is no applicable and I should build the pipeline itself from the beginning with DSL ?

@ayanasser it could be challenging to mix, in most cases, as DSL aims to the abstract the use of GStreamer. That said, anywork you've done to process the batch metadata in DS could be reused in a DSL custom Pad Probe Handler.
I'm hopeful that you will find DSL much easier to work with than DS and GStreamer and that converting to DSL should be somewhat straight forward.

Thank you ^^


100% test coverage

need to make sure every function is completely error free and provide regression protection.

This has been achieved and library is 100% unit test covered


#45 integrate pytest

ref: #45

@yegor256 take a look
I noticed that tests.yml not run in github actions

@yegor256

I noticed that tests.yml not run in github actions

Change condition to on: [ "push", "pull_request" ]

@blablatdinov thanks!


How is "Enterprise Application Owner" supposed to work in practice?

When I make someone a "Enterprise Application Owner", and they try go to portal.azure.com to manage the one application I made them an owner of, they get "Access Denied" when they try navigate to the "Enterprise Apps" blade. This user has no AAD Admin Role. How are they supposed to administer the app that I have made them an owner of?

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

ID: dbd0f810-d394-dbb1-67ef-4cd6fb5c2560
Version Independent ID: e5e33946-6510-cafb-4018-15b201143a7a
Content: Understand admin role delegation - Azure Active Directory
Content Source: articles/active-directory/users-groups-roles/roles-concept-delegation.md
Service: active-directory
GitHub Login: @curtand
Microsoft Alias: curtand

@jaffadog
Thanks for your feedback! We will investigate and update as appropriate.

@jaffadog
Thank you for bringing this to our notice. We are also able to see the same issue/error on our end. We are investigating it and would update soon.

@jaffadog
We were able to see the same issue for a Guest Invited User as you suggested. However for a Native User of the tenant it was working as suggested.
Now, to get it to work again for a Guest User - You have to change the External User Settings.
Go to the Portal. Select Azure Active Directory. Then go to User Settings - under External Users, click on Manage external collaboration settings. Then for the option of "Guest user permissions are limited - select "No" and save he settings.
Now it should work for the invited users in your tenant.

@jaffadog
Let us know if this helped or if you need further assistance.

@neeleshray thanks for investigating this issue.
I am encountering this issue when I (user1) make a fellow "member" user (user2) the owner of an enterprise app. i.e. neither account is a "guest" in the AAD tenant.
When user2 logs into portal.azure.com, they are unable to open the enterprise app blade. They get an "access denied" error.
User1 is a "member" account who has the Global Admin AAD role.
User2 is a "member" account who has no AAD roles assigned. This user's "source" is "Windows Server AD" (i.e. synched from my on-prem AD environment).
I would not expect the "External collaboration settings" > "Guest users permissions are limited" setting to have any affect here, as user2 is not actually a "guest". I had set this setting to "Yes" because I do have a lot of "guest" users, and I really do need to limit their access. Following your suggestion, I tested setting this to "No", and it did have the desired affect on my user2 - they were now able to access the enterprise apps blade and modify the one enterprise app i had made them owner of. However, I really do need to keep this setting set to "Yes" in order to limit true "guest" users' access (e.g. data privacy concerns). Is this actually a bug? Any plan to separate these concerns ("guest" access versus "enterprise application owner" access by a "member")?

@jaffadog
Try this command on the User affected.
Connect-MsolService
Get-MsolUser -UserPrincipalName<EMAIL_ADDRESS>-UserType Member
This command is ideally to convert a Guest User to a Member of the tenant. However, as you say that the affected user is not a Guest User. Try the command just to ensure the same.
After this if you still face the same issue, I would suggest you opening a Support Case for us to take a closer look on the issue.
We would close this thread for now. If the issue persists, suggest you to open a Support Case or a Azure AD Forum Thread.

The case isn't about guests @neeleshray , I don't know why you keep bringing it up.
If a user does not have an admin role assigned, and "Restrict access to Azure AD administration portal" is enabled, users will not be able to access and administer enterprise applications when they are assigned as owners of the app.
Nor is possible with a custom role, even when scoping to specific applications.
There should be a role that enables non-admins to access applications that they are owner of.

Has anyone figured this out? We are moving more apps to Azure that I have non-Admin users that need access. I don't want them to have access to every app either.


Enable Open Lineage for the Dbt Operators

Working on this -- related OpenLineage issue.
Basically we need dbt-ol to be able to parse and dynamically create dbt sources instead of refs to upstream datasets. Then we also need to create an operator in cosmos for the dbt docs command. We also need switch on the operators to use the dbt-ol executable path when dbt-ol is installed, and, of course, the dbt-ol project as an installable in Cosmos.


Joingravity.com domain has expired

Our domain Joingravity.com has been expired, suggest some new domain names.
My suggestion joingravity.net as. Com is not available.

Fixed the issue by changing domain.


Update heredoc discussion

Rakudo issue #4539 illuminated doc problems with the implication
a heredoc could have its terminator following a block. Such is not
the intent as @jnthn noted.
Rakudo has been changed per @jnthn's suggestion and the docs
need a bit more detail (with examples) about intended and proper
use.

Okay, I did find more info on the situation and will visit the PR again.
Thanks!

I'm happy with the Rakudo PR (which is consistent and corrects existing code per existing Synopses) and have asked @jnthn to review it. If approved, I will start working on adding more detail (with examples) for the docs.

@jnthn approved the PR and it's been merged.


Made alfa. part as optional in the URL

Example URL this change can handle now: http://www.lnkgo.lt/visi-video/aktualai-pratesimas/ziurek-putka-trys-klausimai
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x ] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x ] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x ] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Adds handling of different URL format.

Have you even tested your changes?

I did not add a new tox test for my change. Manually checked that both existing urls in LnkGoIE._TESTS are downloaded OK, and my new URL works too.

Wrong. http://www.lnkgo.lt/visi-video/aktualai-pratesimas/ziurek-putka-trys-klausimai is not matched.

Sorry, Sergey, you're right. Will fix.


Matrix multiplication default value is incorrect for cases where the value exceeds 1000000

for example
int arr[] = {1,1000001,1};
for matrix chain multiplication java,
I have raised a pull request as a fix for the same
https://github.com/mission-peace/interview/pull/195

see for example
https://ideone.com/ABa3zJ
expected output is 1000001 and existing code result is 1000000


Change for #27

Added package.json with graphcool-lib dependency and updated instructions

PR Ready

Thanks, will look at this tomorrow 👍 @petrvlcek, can you chime in as well?

@petrvlcek I have updated the README.

Changed the part about module dependencies based on input from @dervos in https://github.com/graphcool-examples/functions/pull/29. @petrvlcek Can you re-review?

Thanks 👍


Optimization of Config File Path Handling with Environment Variable S…

Hello! I've noticed that the current project has some limitations in managing the paths of configuration files, especially across different environments. To enhance the flexibility and maintainability of the project, I propose a small but significant improvement as follows:
I've introduced a new WAS_CONFIGS_DIR parameter, designated for storing various .json configuration files.
WAS_CONFIGS_DIR first attempts to retrieve its value from the system environment variable WAS_CONFIGS_DIR. If the environment variable is not set, it defaults to using WAS_SUITE_ROOT as the directory for configuration files.
The advantage of this change is that it offers users greater flexibility to define the location of their configuration files as per their requirements. Moreover, this modification is backward compatible—if users have not set any environment variable, the project will continue to use WAS_SUITE_ROOT as the storage path for configuration files as before. This means that this change will not affect the normal usage of existing users.
I kindly ask you to consider accepting this modification. I believe that it will make the project more flexible and powerful in its future development. Should there be any questions or further discussions needed, please feel free to contact me.
Thank you once again for your hard work and dedication to this project!

Thanks for your evaluation, and consideration of multi-env systems. This seems like an appropriate change imo, and I will merge it.

Good idea! It's a bit weird to call it WAS_CONFIGS_DIR when it's actually a WAS_CONFIG_DIR though. There's only one config in that dir. Not plural.

Good idea! It's a bit weird to call it WAS_CONFIGS_DIR when it's actually a WAS_CONFIG_DIR though. There's only one config in that dir. Not plural.

Thank you all for your engagement and insightful feedback regarding this recent submission, particularly addressing Arcitec's comments. I'd like to delve deeper into some crucial aspects:
Anticipating Future Configuration Needs: While our current project setup involves just a single configuration file, the evolving nature of our project, especially with the integration of custom nodes, could necessitate splitting configurations into multiple files. Adopting the plural WAS_CONFIGS_DIR provides the necessary foresight for potential future expansions.
Containerization Strategy: My predominant deployment strategy involves Docker-based containerization. In this context, mounting directories from the host into the container has proven to be a more common and robust approach compared to single file mounts. This directory-based approach significantly enhances our flexibility in managing read/write permissions and overall system stability.
Configuration File Management within Containers: Consider the scenario of initializing a custom node for the first time, which requires generating a default configuration file. This process is straightforward with directory mounts, as it allows for dynamic creation and modification of configuration files within the container. Conversely, single file mounts necessitate pre-configuration on the host side, a process that complicates initial setup and subsequent modifications.
Handling Unanticipated Challenges: Practical deployment often throws up a range of read/write and permission challenges, particularly in a containerized environment. Opting for directory mounts over single file mounts offers a more adaptable and robust solution to these challenges, thereby enhancing operational flexibility and system reliability.
These clarifications highlight the thought process behind proposing WAS_CONFIGS_DIR and its potential benefits as our project evolves. I sincerely appreciate the opportunity to contribute and look forward to the ongoing collaborative efforts to enhance our project.

@DigitalIO Hi Michael. I understand your concerns, but that is only the variable for WAS (WAS Node Suite) configuration, which is one configuration per directory. That is why the variable name should be singular.
You can of course have other ComfyUI nodes that also use other configuration directories, and those might work differently. But WAS is "1 dir = 1 config". :)

I think you have me confused for someone else

@DigitalIO Yeah, sorry about that. Typing @ and then "Ico" (the first letters of OP's username) brings up your name instead, and I didn't double check.
The previous message was for @lcolok.

You pointed out that using the singular form for naming WAS_CONFIG_DIR is more appropriate, and I now agree with this perspective. Indeed, in the current state of the project, the singular form seems more direct and accurately reflects the fact that there is only one configuration file in each directory. However, since the current PR has already been merged, the need to change from a plural to a singular form can be addressed in another PR. Considering your clear understanding and suggestion on this matter, I believe it would be a good idea for you to initiate a new PR to adjust the naming. Such a correction will help improve the accuracy and standardization of our code. Promptly making this change is beneficial. As it stands, the impact of this modification should be within a manageable range and will not affect many users. 😁

I think he already fixed it to singular in a PR after yours: https://github.com/WASasquatch/was-node-suite-comfyui/pull/307/commits/426b3715ae1e88517bf61f8c6365beac7669e9fd

I think he already fixed it to singular in a PR after yours.

Correct. And it was merged about an hour after this PR, so all is good. :)


add slot hashes to sysvar cache defaults

Problem
SolFuzz-Agave has a setup step for the sysvar cache to add any missing entries, especially those which may have not been provided in the input accounts. However, the SlotHashes sysvar is not covered.
Summary of Changes
Add SlotHashes to the call to fill_missing_entries.

test vectors is failing, try rebasing with agave-v2.1.0?

test vectors is failing, try rebasing with agave-v2.1.0?

I think this one might not work, since a bunch of fixtures are expecting UnsupportedSysvar, and when I add it as a default, all of those fail.


Reader positioning in STJ converters

Fixes #18763
Fixes #21147

Thanks for the review! I'm using code style there to prevent Stack from being localized and to avoid the open angle bracket from being interpreted as the start of an HTML tag.


Enable Azure Communication SMS from and to European Countries

Hi, as a finance institution I rely on SMS daily to communicate my customers on charges on their accounts and other services. It would be great to be able to transport current solution to Azure. Are there plan to be able to send SMS from and to European countries such as The Netherlands. Thanks!

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

ID: 8ee82481-bb51-5071-b10d-03b5cc380290
Version Independent ID: b6821da7-323a-3e1c-64ec-962cce97dc4d
Content: Pricing scenarios for Calling (Voice/Video) and Chat - An Azure Communication Services concept document
Content Source: articles/communication-services/concepts/pricing.md
Service: azure-communication-services
GitHub Login: @nmurav
Microsoft Alias: nmurav

Also created this:
https://feedback.azure.com/forums/934536-azure-communication-services/suggestions/43043007-sms-communication-service-to-europe-netherlands

@vitorbencini Can you please confirm which document you are referring to. Docs feedback is related to a particular document to provide you correct help. Please help with the same to route it correctly.

@vitorbencini Please convey the document that you are referring to for this feedback.

Absolutely. here is the article.
https://docs.microsoft.com/en-gb/azure/communication-services/concepts/pricing
if you go the the end of it you should read:

@vitorbencini Thanks for the question. For telephony solutions, we are working to expand the geographic availability but don’t have any specific timelines to share for Europe – though it is something we are actively looking into. Updates will be available in the Azure blog.
You can view more info about our current and future plans on our GitHub Roadmap
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hi Bryan, thanks for the reply! Its so sad to not see it there. Its definitely one service that my company would use. I will keep looking on the blog and roadmap for sure.

I have the same ask, for the same country. Doesn't necessarily have to be a Dutch phone number, just allow us to send to the Netherlands ;)

Relevant Azure Feedback item in the new Azure feedback portal, for reference:
https://feedback.azure.com/d365community/idea/9d165250-0c25-ec11-b6e6-000d3a4f0858


Split-Horizon EDS multicluster does not send the ingress gateway of the local cluster to the remote cluster as an endpoint

The pilot does not send the ingress gateway of the local cluster to a remote cluster as an endpoint, so connectivity from the remote cluster into the local one is currently not possible.

cc @costinm

The code of EndpointsByNetworkFilter does not send the local gateway to the remote sidecars.
Proposed solution: define the local network as "default". If the sidecar does not specify its network, treat it as "default". If the endpoint doesn't have network metadata, treat it as "default". Allow defining "default" network in the MeshNetworks with its gateways to send to remote sidecars.

We were able to solve this without any code changes - though a docs update would be good.
This is our config:
  meshNetworks:
    "":
      gateways:
      - address: <IP_ADDRESS>
        port: 443
    network2:
      endpoints:
      - fromRegistry: n2
      gateways:
      - address: <IP_ADDRESS>
        port: 443

It turned out to be sufficient to add a gateway config for "" - as that's already the hardcoded default

Did you set the meta network name on the remote cluster?

Yes, we have. Though since we're also explicitly setting fromRegistry I think it might be redundant? Eh, followed the guide and it worked :)

@mikebryant I see, but it is a hack. I propose to use some dedicated name instead of "", e.g. default.

Yeah, I'm not opposed to some special name. Thought it would be helpful to share how to make it work right now though. (as we actually need this to work, so we're ploughing ahead)

@mikebryant yes, it helps, thank you for sharing!

We were able to solve this without any code changes - though a docs update would be good.
This is our config:
  meshNetworks:
    "":
      gateways:
      - address: <IP_ADDRESS>
        port: 443
    network2:
      endpoints:
      - fromRegistry: n2
      gateways:
      - address: <IP_ADDRESS>
        port: 443

It turned out to be sufficient to add a gateway config for "" - as that's already the hardcoded default

Thanks. So if we create a service end point in cluster1, it will never show up in cluster2, whether is a cluster  having control plane installed or not, right?
I checked the endpoints of 2 clusters, they only have end points in their local service endpoints.

We were able to solve this without any code changes - though a docs update would be good.
This is our config:
  meshNetworks:
    "":
      gateways:
      - address: <IP_ADDRESS>
        port: 443
    network2:
      endpoints:
      - fromRegistry: n2
      gateways:
      - address: <IP_ADDRESS>
        port: 443

It turned out to be sufficient to add a gateway config for "" - as that's already the hardcoded default

So the - address: <IP_ADDRESS> is the local cluster  gateway ip addr and - address: <IP_ADDRESS> is the remote  cluster gateway ip addr, right?

Yes, that's right on the ip addresses.
With this config we have the istioctl proxy-config endpoints command showing both local endpoints and the other cluster gateway endpoint (if the same services has endpoints in the other cluster)

Yes, that's right on the ip addresses.
With this config we have the istioctl proxy-config endpoints command showing both local endpoints and the other cluster gateway endpoint (if the same services has endpoints in the other cluster)

I'm using istioctl 1.1.3 the latest version and run "istioctl proxy-config endpoints sleep-88ddbcfdd-bhstf.sample --context=$CTX_CLUSTER1 | grep helloworld" following the instruction@https://istio.io/docs/examples/multicluster/split-horizon-eds/#split-horizon-eds-in-action
And I got
:5000       HEALTHY     outbound|5000||helloworld.sample.svc.cluster.local
:443          HEALTHY     outbound|5000||helloworld.sample.svc.cluster.local
Then I ran $ kubectl exec --context=$CTX_CLUSTER1 -it -n sample -c sleep $(kubectl get pod --context=$CTX_CLUSTER1 -n sample -l app=sleep -o jsonpath='{.items[0].metadata.name}') -- curl helloworld.sample:5000/hello
And it always returned the service deployed in the local cluster services.  Any idea?

  meshNetworks:
    network1:  #This name can be specified，when installing primary cluster  --set global.network="network1"
      endpoints:
      - fromRegistry: kubernetes  #This is fixed cluster registry for primary cluster
      gateways:
      - address: <IP_ADDRESS>
        port: 443
    network2:
      endpoints:
      - fromRegistry: n2
      gateways:
      - address: <IP_ADDRESS>
        port: 443

Can use the above config. Btw , the official doc for cluster-aware ,multicluster install guide is not complete.

@hzxuzhonghu Cool, thank you! I did not know how to specify the "fromRegistry" in this case.


Problem With looking for targets option

What version of fleet are you using (fleet version --full)?
The latest version of both the docker and the fleet
What did you do?
I updated the fleet and now when I try to add a new query and add new targets the target bar doesn't let me search for names or ips it just lets me see the first options.
But when I reverse it to the old fleet binary it works just fine and let me search for targets.
What did you expect to see?
To be able to search for targets by ip or hostname
What did you see instead?
Nothing really, can't search cause the search bar ain't working.

What do you see in the network inspector in your browser when you type into the targets box?
What do you see in the Fleet server logs?

Absent further details, this issue cannot be investigated. Closing.


Add Scoop (unofficial) installation method

Summary of the Pull Request
This adds an (unofficial) installation method for Scoop package manager users. Many developers using Windows (me included) use and love Scoop, so this would be a nifty addition to the Readme.

PR Checklist

[ ] Documentation updated.

Detailed Description of the Pull Request
Made changes to README.md file.

The (awesome) thing about the installation process of Scoop is that the problem almost never arises (if it arises) due to Scoop itself. Anything and everything is maintained in a manifest, see this https://github.com/lukesampson/scoop-extras/blob/master/bucket/windows-terminal.json. It's just merely using the release archives of microsoft/terminal repository. If at all there's a problem, an issue can be raised in the repository where this manifest is maintained, and that is lukesampson/scoop-extras.

I can add an extra line here mentioning that the installation-specific issues can be reported in the aforementioned repository, if required.

That would be preferred, thanks!


[Explicit Module Builds] Re-use external build artifacts to avoid redundant Swift moduel re-scan

In contexts where SwiftDriver is used to plan a multi-module build (e.g. SwiftPM), use the ModuleInfoMap containing results of prior scans to avoid further redundant re-scanning.
All previously-seen Swift modules are treated as potential placeholder dependencies during subsequent dependency-scanning actions. This causes the dependency scanner, upon encountering an import of such module, to not: search for its interface, parse it, and build a full dependency tree yet again.
The dependency scanner output, on subsequent re-scans, is therefore a much shallower graph with many placeholders, which get resolved in the client (SwiftDriver) using the external ModuleInfoMap provided by the build system.
For planning the build of SwiftPM with Explicit Modules, this change reduces the build-planning time by ~2x.
This PR adds:

Serialize all previously-seen Swift modules, not just ones corresponding to build targets, as placeholder inputs to the dependency-scanning action.
Adds resolve logic for additional, non-target Swift modules found in the initial inter-module dependency graph.
Renames ExplicitModuleBuildHandler to ExplicitDependencyBuildPlanner.
Modify testModuleDependencyWithExternalCommandGeneration to exercise non-target placeholder resolution.

@swift-ci please test

Thanks, Xi.
DNM, for now, this depends on: https://github.com/apple/swift/pull/34545 being merged first.

@swift-ci please test

@swift-ci please test

@swift-ci please test


fix(transformer): create new scopes for new blocks in TS transform

#3908  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Docker build fail on RaspberryPi

Attached log. This was a fresh download of Hypriot's Docker for RaspberryPi which includes the latest docker version. Maybe the base docker image is missing some compile tools/libraries?
docker_fail_log.txt

Yea, I've seen this before on some NAS devices.
It could be worked around, but really the best solution is for us to roll our own docker images that have everything pre-built.
I've been toying with the idea anyway as it would drastically reduce startup time.
If you really want to get it working you can add RUN or CMD commands before the pip stuff run. You probably need to install at the least gcc-g++, I'm not sure what distro or package manager it uses.
Ping me on Slack if you want to work through it.

@utdrmac Can we close this, it's out of our control really.

I've made a fix for this @utdrmac can you test it?


Renaming remove_temp_files to remove_temp_dir_on_exit

Close #1387 by renaming remove_temp_files to remove_temp_dir_on_exit which I believe it is more accurate and self descriptive.
I have also implemented a warning.

The option stack_level is useful to make the warning shows in the main process and also to:

This makes the warning refer to deprecation()’s caller, rather than to the source of deprecation() itself (since the latter would defeat the purpose of the warning message).

Reference: https://docs.python.org/3/library/warnings.html#warnings.warn

The option stack_level is useful to make the warning shows in the main process and also to:

This makes the warning refer to deprecation()’s caller, rather than to the source of deprecation() itself (since the latter would defeat the purpose of the warning message).

Reference: https://docs.python.org/3/library/warnings.html#warnings.warn

Pinging @pyansys/pyansys-core FYI.


redis-cli --bigkeys doesn't work

redis-cli --bigkeys
returns "Couldn't determine DBSIZE!" error.
any idea why it happens?

Hi @mehdymohajery
what version of Redis are you running?
If you execute redis-cli.exe and then call the DBSIZE command what is the result?

it's OK,
if you don't pass -a password, it doesn't show authentication error.
with passing auth key it works just fine.


[Validator] Node ending near other highway

cc. @geohacker @batpad @maning

Progress:

branch nodeendingnearhighway
result
@maning Can you take a look  on result.

@maning : new result is this: https://gist.github.com/anonymous/6e34347bb93203d7e55f, I've improved to avoid many false positive.

This is tricky. Notes below:

How updated is your, test mbtiles? I'm seeing recently fixed nodes ( ~ 2 days ago) that were detected.
3.2 meter might be large, I'm seeing false positives beyond 1.2 meters.  Can we decrease the buffer size <= 1 meter and then make it bigger later on if we see false negatives?
Can we standardize units? I prefer we use SI instead of imperial.

@maning

How updated is your, test mbtiles? I'm seeing recently fixed nodes ( ~ 2 days ago) that were detected.

my peru.mbtiles was old, I've updated the latest.

3.2 meter might be large, I'm seeing false positives beyond 1.2 meters. Can we decrease the buffer size <= 1 meter and then make it bigger later on if we see false negatives?

I think  2 meter is fine.  in size <=1 many of the errors are avoided.

Can we standardize units? I prefer we use SI instead of imperial.

we will use meters units.
new results: https://gist.github.com/anonymous/2308bdc52d1ecf741cba

@Rub21 results looks OK!

merge on master!


Givens of zero vector and non strict stopping criterion

Givens of a zero vector created NaN values and the strict stopping criterion was never true for exact zeroes.

#113 solved

Sorry, I am still missing the test cases, which prove #113 is solved. Could not verify that in my copy.

#113 inacurracy also fixed


AudioStreamPlayer (And AudioStreamPlayer2D) do not obey Volume settings when called from an AnimationPlayer being controlled by an AnimationTree

Godot version
4.0 beta 7 official
System information
Win 10
Issue description
Volume settings in inspector are not used, and the audio plays at full volume if the animation with an audio playback is managed by an AnimationTree with a StateMachine root node. The preview in the Animation Player is affected correctly, but in game audio is not.
AudioStreams on autoplay seem fine as well, as does ticking the "Playing" check box in the inspector.
Steps to reproduce
Add an AudioStreamPlayer or AudioStreamPlayer2D
Adjust volume or pitch to -20dB or so for notable difference
Create Animation Player, Add an animation, add an audio playback track, insert a key and pick a sound the sound file.
Test the animation in the animation player to hear the reduced volume.
Code the animation to run using $AnimationPlayer.play("Animation Name") in script, hear the reduced volume in game
Add an animation Tree, set the Animation Player from before as its player.
Add a statemachine root node
Add the animation in the statemachine.
Test the animation in the player to hear the reduced volume
Remove the $AnimationPlayer.play() code
Call "$AnimationTree.travel("Animation Name") in script instead, hear NON reduced volume.
Minimal reproduction project
Two projects, only change is whether used .play or .travel in AnimationPlayer or AnimationTree respectively. Both set to -15dB. Both should be same volume, but are not. Headphone warning, original sound is kind of loud.
Audio Animation Bug PLAYER.zip
Audio Animation Bug TREE.zip

The workaround is to use the Method track. Well, I too would like to see this fixed as soon as possible. Maybe later 4.1? @reduz

I've already hit a separate bug in that one, call method doesn't always get hit when spammed if under 0.4 seconds~ long

Ah I remember that your issue #69382. And I still think that is probably a StateMachine issue and not a MethodTrack issue!


Reduce to minimal alpine image

Reduce to minimal alpine image reduces image size
from 450MB to 80MB and potential attack surface.

Signed-off-by: Kennelly, Martin<EMAIL_ADDRESS>

@zshi-redhat Could you take a look at this patch?

/lgtm

@ahalim-intel @martinkennelly I don't have merge permission to this repo, would one of you merge it?


Add Features scatter plot

As discussed in #19 , the PR proposes to add a widget for making scatter plots from a layer's FeatureTable. In napari, annotation layers (i.e., labels, shapes, and points) have a layer.features table, which provides annotations for each data item (e.g., each point in the case of points). This features table can be accessed like a pandas dataframe.
A few notes:

This currently mirrors the current behavior which selects which layer to plot from via the layer list selection.
I exposed a few parameters that were hard coded (e.g., alpha, whether or not to allow displaying large data as a heat map) as properties. It looks like there is some discussion to allow for style sheets (#2, #36), so maybe that's a better route in the future.
I added a ScatterBaseWidget that holds most of the code for plotting, etc. Implementations of this base class need to provide a _get_data() method that retrieves the relevant data for plotting. My goal here was primarily to start separating the plotting code (which can be re-used by many types of scatter plots) from the data loading code.
After playing around with the code a bit, I think it would be nice to further separate the plotting code from the data loading code. I could imaging having a DataSource class and a ScatterPlot class where the ScatterPlot class is
I didn't add a table widget, but I think that can be a follow up PR (e.g., by @jo-mueller ;) )

Here's how it looks for now:
https://user-images.githubusercontent.com/1120672/167254408-2f82286d-5696-411c-b318-36ff8cc2f604.mov

Thanks for the quick review, @dstansby ! Based on you feedback, I've made a few changes:

made the marker_alpha and _histogram_for_large_data private properties.
I added an additional private property _threshold_to_switch_to_histogram to set the threshold for switching from scatter to histogram plotting.
Finally, I've exposed the FeaturesScatterWidget as a plugin.

This looks good now - it looks like there's a confict since I merged another PR, would you be able to rebase this on to the current main branch?

Thanks for the review @dstansby ! I've fixed the merge conflict.


installation issue

I am trying to install it on a backup system. the original Modbus integration had been disabled. I was able to install, but unable to configure the integration. I am using a 3 phase MPII 5000/48, cerbo GC, Pylontech LiFePO4 battery, 2x Fronius inverter (Symo 3 Phase), 1x MPPT 450/100, 1x MPPT 250/60. The Yaml integration had been disabled. Any idea?

Is your Modbus/TCP under "Settings -> Services" enabled and further under " -> Modbus/TCP -> Available Services" are your devices in the list?

In another instance of HA my modbus connection is workin flawlessly. This is a test of the integration after removing all Modbus stuff from yaml

Maybe I need to shutdown the other instance...

I think, I got it: enter http:// before the IP address :-)


[Issue]:  Local LLM and Loacl embedding error?

Describe the issue
Use vllm to launch a local large model, in the style of openai，but it won't work
Steps to reproduce
step1:python -m vllm.entrypoints.openai.api_server --max-model-len 6144 --gpu-memory-utilization 0.95 --disable-log-stats --served-model-name Qwen2-7B-Instruct --model /mnt/workspace/Qwen2-7B-Instruct
step2: start embedding
import os
from contextlib import asynccontextmanager
from typing import List, Union
import tiktoken
import torch
import uvicorn
from fastapi import FastAPI
from fastapi.middleware.cors import CORSMiddleware
from pydantic import BaseModel
from sentence_transformers import SentenceTransformer
from sse_starlette.sse import EventSourceResponse
Set up limit request time
EventSourceResponse.DEFAULT_PING_INTERVAL = 1000
EMBEDDING_PATH = os.environ.get('EMBEDDING_PATH', '/mnt/workspace/m3e-base')
@asynccontextmanager
async def lifespan(app: FastAPI):
yield
if torch.cuda.is_available():
torch.cuda.empty_cache()
torch.cuda.ipc_collect()
app = FastAPI(lifespan=lifespan)
app.add_middleware(
CORSMiddleware,
allow_origins=[""],
allow_credentials=True,
allow_methods=[""],
allow_headers=["*"],
)
class CompletionUsage(BaseModel):
prompt_tokens: int
completion_tokens: int
total_tokens: int
class EmbeddingResponse(BaseModel):
data: list
model: str
object: str
usage: CompletionUsage
class EmbeddingRequest(BaseModel):
input: Union[List[str], str]
model: str
@app.post("/v1/embeddings", response_model=EmbeddingResponse)
async def get_embeddings(request: EmbeddingRequest):
if isinstance(request.input, str):
embeddings = [embedding_model.encode(request.input)]
else:
embeddings = [embedding_model.encode(text) for text in request.input]
embeddings = [embedding.tolist() for embedding in embeddings]
def num_tokens_from_string(string: str) -> int:
    encoding = tiktoken.get_encoding('cl100k_base')
    num_tokens = len(encoding.encode(string))
    return num_tokens

response = {
    "data": [
        {
            "object": "embedding",
            "embedding": embedding,
            "index": index
        }
        for index, embedding in enumerate(embeddings)
    ],
    "model": request.model,
    "object": "list",
    "usage": CompletionUsage(
        prompt_tokens=sum(len(text.split()) for text in request.input),
        completion_tokens=0,
        total_tokens=sum(num_tokens_from_string(text) for text in request.input),
    )
}
return response

if name == "main":
# load Embedding
embedding_model = SentenceTransformer(EMBEDDING_PATH, device="cuda")
uvicorn.run(app, host='<IP_ADDRESS>', port=8001, workers=1)
step3:pip install graphrag
step4:mkdir -p ./ragtest/input
step5:curl https://www.gutenberg.org/cache/epub/24022/pg24022.txt > ./ragtest/input/book.txt
step6:python -m graphrag.index --init --root ./ragtest
step7: Modify the yml file
GraphRAG Config Used
No response
Logs and screenshots
encoding_model: cl100k_base
skip_workflows: []
llm:
api_key: ${GRAPHRAG_API_KEY}
type: openai_chat # or azure_openai_chat
model: Qwen2-7B-Instruct
model_supports_json: false # recommended if this is available for your model.
max_tokens: 2000
request_timeout: 180.0
api_base: http://localhost:8000/v1/
api_version: 2024-02-15-preview
organization: <organization_id>
deployment_name: <azure_model_deployment_name>
tokens_per_minute: 150_000 # set a leaky bucket throttle
requests_per_minute: 10_000 # set a leaky bucket throttle
max_retries: 10
max_retry_wait: 10.0
sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
concurrent_requests: 25 # the number of parallel inflight requests that may be made
parallelization:
stagger: 0.3
num_threads: 50 # the number of threads to use for parallel processing
async_mode: threaded # or asyncio
embeddings:
parallelization: override the global parallelization settings for embeddings
async_mode: threaded # or asyncio
llm:
api_key: ${GRAPHRAG_API_KEY}
type: openai_embedding # or azure_openai_embedding
model: m3e-base
api_base: http://localhost:8001/v1/
# api_version: 2024-02-15-preview
# organization: <organization_id>
# deployment_name: <azure_model_deployment_name>
# tokens_per_minute: 150_000 # set a leaky bucket throttle
# requests_per_minute: 10_000 # set a leaky bucket throttle
# max_retries: 10
# max_retry_wait: 10.0
# sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
# concurrent_requests: 25 # the number of parallel inflight requests that may be made
# batch_size: 16 # the number of documents to send in a single request
# batch_max_tokens: 8191 # the maximum number of tokens to send in a single request
# target: required # or optional
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

The local search with embeddings from Ollama now works.
You can read full guide here:
<EMAIL_ADDRESS>Here is the link to the repo:
https://github.com/karthik-codex/autogen_graphRAG

你 端口号是不是错了？

If you want to use open-source models, I've created a repository for deploying Hugging Face models to local endpoints, offering functionality similar to OpenAI APIs. You can find the repo here: https://github.com/rushizirpe/open-llm-server
Also, I've prepared a Colab notebook for the Graphrag Demo. You might want to take a look: https://colab.research.google.com/drive/1uhFDnih1WKrSRQHisU-L6xw6coapgR51?usp=sharing.
If you don't have access to GPUs like the A100, you'll need a GROQ_API_KEY (which is free with certain limitations), you can obtain it from: https://console.groq.com/keys

You might want to take a look: https://colab.research.google.com/drive/1uhFDnih1WKrSRQHisU-L6xw6coapgR51?usp=sharing.
If you don't have access to higher-end GPUs, you'll need a GROQ_API_KEY (Free with certain limitations).

Consolidating alternate model issues here: https://github.com/microsoft/graphrag/issues/657


Add unzip command

Based on this file:
https://github.com/actions/toolkit/blob/main/packages/tool-cache/src/tool-cache.ts
The github actions expect to have the unzip command but is not installed in this docker image

Fixed in #31


Change wording

~I dislike it without at least a tooltip explaining that given projects are not listed on the main page thus not mentioned here under used by~

The tooltip on the detailed page summary header should say "There are no scaling projects listed on L2BEAT that use this DA layer", without "and bridge"

@sdlyy the wrong tooltip was updated 😃

I meant the one in the top summary that's for the layer only, not the table

Went for unified one aka 'solution'


3d registration tutorial on my own dataset

Hello,
I am trying to follow your 3D registration tutorial. I tested on lungs dataset and it is working fine.
But Yesterday I wanted to apply to my own dataset liver. I created the same pipeline and structured data but I got an error
ValueError("the data to aggregate must be PyTorch Tensor.")
MONAI version: 1.1.0
Numpy version: 1.21.5
Pytorch version: 1.13.1+cu117
MONAI flags: HAS_EXT = False, USE_COMPILED = False, USE_META_DICT = False
MONAI rev id: a2ec3752f54bfc3b40e7952234fbeb5452ed63e3
MONAI file: /home/.local/lib/python3.9/site-packages/monai/init.py
Optional dependencies:
Pytorch Ignite version: 0.4.11
Nibabel version: 5.0.0
scikit-image version: 0.19.2
Pillow version: 9.2.0
Tensorboard version: 2.12.0
gdown version: 4.6.3
TorchVision version: 0.14.1+cu117
tqdm version: 4.64.1
lmdb version: 1.4.0
psutil version: 5.9.0
pandas version: 1.4.4
einops version: 0.6.0
transformers version: 4.26.1
mlflow version: 2.1.1
pynrrd version: 1.0.0
For details about installing the optional dependencies, please visit:
https://docs.monai.io/en/latest/installation.html#installing-the-recommended-dependencies
/projects/test_monai_registration/MONAI_DATA_DIRECTORY
moving_image shape: torch.Size([96, 96, 104]), moving_label shape: torch.Size([96, 96, 104])
fixed_image shape: torch.Size([96, 96, 104]), fixed_label shape: torch.Size([96, 96, 104])
Loading dataset:   0%|          | 0/4 [00:00<?, ?it/s]
Loading dataset:  25%|â–ˆâ–ˆâ–Œ       | 1/4 [01:57<05:51, 117.31s/it]
Loading dataset: 100%|â–ˆâ–ˆâ–ˆâ–ˆâ–ˆâ–ˆâ–ˆâ–ˆâ–ˆâ–ˆ| 4/4 [01:57<00:00, 29.33s/it]
/home//.local/lib/python3.9/site-packages/torch/utils/data/dataloader.py:554: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 2, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
warnings.warn(_create_warning_msg(
/home/.local/lib/python3.9/site-packages/monai/networks/blocks/warp.py:66: UserWarning: monai.networks.blocks.Warp: Using PyTorch native grid_sample.
warnings.warn("monai.networks.blocks.Warp: Using PyTorch native grid_sample.")
Traceback (most recent call last):
File "/projects/test_monai_registration/monai_image_registration_liver.py", line 219, in
metric = dice_metric.aggregate().item()
File "/home/.local/lib/python3.9/site-packages/monai/metrics/meandice.py", line 99, in aggregate
raise ValueError("the data to aggregate must be PyTorch Tensor.")
ValueError: the data to aggregate must be PyTorch Tensor.
How could I fixed this ?
What can be a problem ? Could you help me please ?

Hi @agatadefr, could you please check the type of dice_metric(y_pred=val_pred_label, y=val_fixed_label)? From the error message seems the type before the aggregate is wrong.
Thanks!

came across a similar issue recently -- make sure the validation set inputs are not empty

There is definitely something going wrong in your code, have you double-checked if the normalisation and data prep are as expected? That's a common source of error

Hi @rekalantar, which tutorial did you refer to?


Validation feedback icon is hidden while  in input group is focused

I'm not sure this is normal behavior or this is a bug, but in the official docs in chapter "Validation states" → "With optional icons" try to check any "Input group with success" example.
The problem:

when <input> element get focus, feedback icon is hidden.
when <input> element lost focus, feedback icon is shown again.
in other examples (wthout input group) feedback icon is always visible regardless of focus

This affected only on bootstrap v3 (no impact on v4) only on input groups (with an .input-group-addon or .input-group-btn) in latest Chrome, Firefox (other browsers not tested).
This can be important, for example if using a live validation as you type with javascript when <input> is constantly in focus. In this case, the feedback icon element is not able to indicate of validation state via icon.
See /less/forms.less:
// Feedback icon (requires .glyphicon classes)
.form-control-feedback {
  position: absolute;
  top: 0;
  right: 0;
  z-index: 2; // Ensure icon is above input groups
  ...

If you increase the z-index to 3, it will be fixed.
P.S.: There are no similar examples of input groups with feedback icons in the v4 docs . I'm confused!

Thanks for this topic. I found the same issue on my project, with feedback icons but also with this plugin:
http://labs.abeautifulsite.net/jquery-minicolors/
which stops to work well after Bootstrap updating.
Thanks too for the z-index 3 temporary solution until v3.3.7, it works fine :)

Hello,
Can be fixed properly into input-groups.less line 33 :
&:focus {
&,
+ .form-control-feedback{
z-index: 3;
}
}
Instead of :
&:focus {
z-index: 3;
}
Loïc

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


.editorconfig missing quote_type = single for formatting of typescript files

I'm submitting a...

[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Question

Current behavior

Using prettier as formatter in VSCode, format whole .ts typescript file makes all single-quote (') as double quotes (")

Expected behavior

Expected is that when organizing imports and formatting document all quotes should be single

Minimal reproduction of the problem with instructions

Environment

ngX-Rocket: 9.1.0
Node.js: v15.2.1
Npm: 7.0.8
OS: darwin x64 20.2.0

Generated project options:
{
  "generator-addon-firebase": {
    "firebaseDeploy": true,
    "version": "3.0.1",
    "props": {
      "firebaseDeploy": true,
      "appName": "tursido-app",
      "projectName": "tursido-app",
      "packageManager": "npm",
      "location": "path",
      "strict": false,
      "skipInstall": false,
      "skipQuickstart": false,
      "initGit": true,
      "usePrefix": true,
      "target": [
        "web"
      ],
      "pwa": true,
      "ui": "ionic",
      "layout": "tabs",
      "auth": true,
      "lazy": true,
      "angulartics": false,
      "languages": [
        "en-US"
      ],
      "tools": [],
      "utility": [
        "lodash"
      ],
      "deploy": "firebase",
      "mobile": [],
      "desktop": []
    }
  },
  "generator-ngx-rocket": {
    "version": "9.1.0",
    "props": {
      "location": "path",
      "strict": false,
      "skipInstall": false,
      "skipQuickstart": false,
      "initGit": true,
      "usePrefix": true,
      "appName": "tursido-app",
      "target": [
        "web"
      ],
      "pwa": true,
      "ui": "ionic",
      "layout": "tabs",
      "auth": true,
      "lazy": true,
      "angulartics": false,
      "languages": [
        "en-US"
      ],
      "tools": [],
      "utility": [
        "lodash"
      ],
      "deploy": "firebase",
      "projectName": "tursido-app",
      "packageManager": "npm",
      "mobile": [],
      "desktop": []
    }
  }
}

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 10.1.7
Node: 15.2.1
OS: darwin x64

Angular: 10.2.4
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.5
@angular-devkit/build-angular   0.1001.7
@angular-devkit/core            11.0.5
@angular-devkit/schematics      10.1.7
@angular/cdk                    10.2.7
@angular/cli                    10.1.7
@angular/fire                   6.1.4
@angular/flex-layout            10.0.0-beta.32
@schematics/angular             10.1.7
@schematics/update              0.1001.7
rxjs                            6.6.3
typescript                      4.0.5

Others:

ℹ WORKAROUND

Update .editorconfig with

[*.ts]
quote_type = single

I think as a fix, this manual change to .editorconfig should be included in the boilerplate/generated code by ngx since in previous versions single quote is used by default (I think by prettier in package.json)(that's what I get used, unless this changed). So this might be a regression issue.

This may be an issue with the prettier VS Code extension or your config, as in the generated project there's already a setting in package.json for prettier with "singleQuote": true. You can verify that it works fine by running npm run prettier from the command line.
It would be ok to enforce the quote_type property in editorconfig, but at the moment it's a proposal and not an "officially" supported property (see https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties).
I also tried with a freshly generated project where I enabled the "prettier" option and the formatting is fine, using the settings from package.json (single quotes).
Are you sure you enabled the "prettier" option when generating your project, and you're using this extension for formatting?

This may be an issue with the prettier VS Code extension or your config, as in the generated project there's already a setting in package.json for prettier with "singleQuote": true. You can verify that it works fine by running npm run prettier from the command line.
It would be ok to enforce the quote_type property in editorconfig, but at the moment it's a proposal and not an "officially" supported property (see https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties).
I also tried with a freshly generated project where I enabled the "prettier" option and the formatting is fine, using the settings from package.json (single quotes).
Are you sure you enabled the "prettier" option when generating your project, and you're using this extension for formatting?

I just saw that quote_type = single was added to the default ng11 generated app, so I wouldn't hurt to also add it.

I just saw that quote_type = single was added to the default ng11 generated app, so I wouldn't hurt to also add it.


only first html() call is rendered

I have two cases where I get unexpected results when running .html()
I am using jspdf v2.1.1
Case1:
const myDoc = new jsPDF();
const options =  {
    x: 10,
    y: 10,
    callback: function (doc) {
        let options2 =  {
            x: 10,
            y: 20,
             callback: function (doc2) {
                 doc2.save();
               }
        };
        doc.html("Test2", options2);
    }
};
myDoc.html("Test1", options);

What I expect here is to see 1 pdf file with two lines:
Test1
Test2
But what I get is only 1 line Test1, where did Test2 go?
Case2:
const myDoc1 = new jsPDF();
const options1 =  {
    x: 10,
    y: 10,
     callback: function (doc) {
          doc.save();
       }
};
myDoc1.html("Test1", options1);

const myDoc2 = new jsPDF();
const options2 =  {
    x: 10,
    y: 10,
     callback: function (doc) {
          doc.save();
       }
};
myDoc2.html("Test2", options2);

What I expect here is to see 2 pdf files, one with Test1 and second with Test2. But instead I get one empty file and another file with Test1.
Can someone confirm if they get same behaviour? What is going on?

That's interesting. Seems like multiple consecutive calls to the html function are broken.

Hi @HackbrettXXX. I can see you are an active contributor to the repo. Any estimate on how long it would take to fix and release new version? Thanks

I'm currently quite busy, so if I have to implement the fix myself it will probably take weeks if not months. If you or someone else provides a pull request, I will merge and release it in a timely manner.

Could also be the same as #3204.

I have the same issue and I think it is not related to #3204. Only first call to html is rendered regardless of Y offset. I will try to fix this and provide a PR if I can.


ProtocolError is neither Send nor Sync

I am not sure if this is intentional or not, but xcb::ProtocolError is neither Send nor Sync which makes working with this crate in a multithreaded environment pretty tedious. This appears to be due to each of the variants containing a type called Error which all eventually boil down to a *mut xcb_generic_error_t. Obviously it's unsound to send raw pointers between threads in the general case, but each of these error types seem to be freeing the pointer on drop, which suggests that this is an owning pointer, and thus safe to send between threads.

XCB is thread safe and Error types do nothing but access data held behind the pointer, and eventually free it.
Would there be a risk to double Drop if it were Send and Sync?
ProtocolError cannot be cloned. Could it be Send but not Sync?
Note that same would apply to Event types.

As per the documentation of Sync, a type T is Sync if and only if &T is Send. Basically the only things in the language that aren't Send are raw pointers, and the only things that aren't Sync are types with non-thread-safe interior mutability. If the the pointer held by the error and event types is unique, then the type should certainly be Send, and as long as it has no interior mutability then it should also be Sync.


Address some OpenSSF scorecard issues

https://securityscorecards.dev/viewer/?uri=github.com/geopm/geopm
Address "Token-Permissions" issues.
Address "CI-Tests" issues.  This will require follow-up in the GH repo configuration for geopm/geopm to block PR's based on the new name for these checks (i.e. "build" was replaced with "test").
Begin to address "Pinned-Dependencies" issues.  Follow-up needed here on specifying all python dependencies by hash in the requirements.txt files and anything pip installed in the CI workflow files.
Relates to #3345

Looks like maybe we need to relax the merge requirements for this PR?  Otherwise LGTM


Nox Fails : 'Python Interpreter 3.6 not found', but Python version is present.

Hi everyone,
I just now found about nox and started learning about it. I created a simple package and tried automating some tests with nox. I have two Python versions - 2.7.10 and 3.6.5 . I've installed nox in Python 3.6.5 . On trying to run nox for both these versions, I'm getting a warning saying 'Python Interpreter 3.6 is not found'. Here is my nox code :
import nox

@nox.session(python=["3.6", "2.7"], reuse_venv=True)
def pytest(session):
    session.install("numpy")
    session.install("pytest")
    session.run("python", "setup.py", "develop")
    session.run("pytest", "-v", "tests")

and this is the result :

But I have Python 3.6.5 in my laptop :

But when I run with only python 3.6, it is working. I'm unable to figure out why this is so. I even tried removing Python 2.7 from the environment PATH variable. Can someone please help me figure out what I'm doing wrong?

This is quite surprising. Can you run py, py -3 and py -3.6 from the command prompt? Also, when you are within a Python interpreter can you import sys; print(sys.executable)?

Hi @dhermes, I've run the commands you've mentioned. This is the result I'm getting :

I don't understand. Why am I getting Python 3 and Python 3.6 not found, even though the Interpreter is present?

I'm not sure why the py launcher can't find your install. I'd imagine it has to do with how it was installed. Did you personally install it or is your machine administered by someone else (e.g. an IT org)? If you did install it, do you recall how you did it? Could you re-install from a python.org installer?

I personally installed it.  I downloaded python-3.6.5-amd64.exe from python.org and followed the installation steps mentioned in the installer. I'll try uninstalling both the versions and try re-installing again. Before running py launcher, I set PYLAUNCH_DEBUG=1 and found this :

Solved Issue. It seems there was some problem during the installation of Python 3.6.5 . I uninstalled all python versions and re-installed everything. Now it's working 👍 . Thanks, @dhermes  for your help.

Sure thing


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2023-03-06)
Features

性能优化、添加哈士奇 (df16be1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/future-front-end/releases/tag/v1.1.0 :sunflower:


Synbiopython on PyPI

Hi everyone - I went ahead and pushed the synbiopython projet on PyPI to reserve the name:
https://pypi.org/project/synbiopython/0.0.1/
It would be nice if the PyPI package's ownership was shared between accounts from different froundries to ensure every team can easily update the repo if necessary (right now it's only EdinburghGenomeFoundry). Let us know your PyPI username and we'll add you.

Please respond if you have a PyPI account.
If not, could one or two people volunteer to act as co-owner for the project on PyPI? So far the co-owners are me and the Edinburgh group - we could do with more.


SU_Volcanic: file path and protection for missing file

Degassing file path is corrected. Additionally, a safeguard has been implemented to halt model execution if the specified volcanic file does not exist for the requested date.

@jrjoshi1 I don't think we can do this. Your change does stop the model:
 Error: file not found
 ExtData/chemistry/CARN/v202401/explosive/so2_explosive_volcanic_emissions_CARN_
 v202401.20000414.rc

but we don't want that. We just want to model to handle a missing date gracefully. For example, your code means the model cannot run save on 19 days in the year 2000.
I think we just don't need the else bit. Just if the file exists, read it. If not, it should just avoid the volcano codes.

@mathomp4 I anticipated that concern! Without the 'Else and stop,' the model might continue running, leading users to believe that all volcanic files were utilized for the simulation period, while some files, like those for 2000, may not be included. If we're confident that no files are/(will be) missing for any year except 2000, we could consider removing the 'Else/stop' part; however, users should still be aware of the issue. Just my thoughts!
Don't know what @pcolarco and others would think.

@mathomp4 I see your point now, and I think we should remove the 'else/stop' part. Unless there are any other opinions, I’ll go ahead and make that change tomorrow. Thanks.

This seems to work for me. I'll approve since it's it is a pretty important bugfix.


fix(BFormCheckbox): Handle contextual state === false correctly (Fixes #2017)

Describe the PR
Checkbox state === false was resolving to undefined (which is effectively the null state) if there was no parent. Instead of using the parent value for all falsey values, I'm checking that the direct prop is true or false and only falling back to the parent if it's not.
Small replication
See #2017
PR checklist

What kind of change does this PR introduce? (check at least one)

[x] Bugfix :bug: - fix(...)
[ ] Feature - feat(...)
[ ] ARIA accessibility - fix(...)
[ ] Documentation update - docs(...)
[ ] Other (please describe)

The PR fulfills these requirements:

[x] Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

When props === false and parent === undefined, props.state ?? parentData?.state.value ?? null evaluates to null, we want it to evaluate to false (that's what this bug is about)
So, if we did props.state ?? parentData?.state.value ?? false, that would catch the case that the bug is about, but if props.state === null, then we have the same problem (we get false when we want null)
Semantically, I think what we want to say is that if props.state is a boolean, use that, otherwise, use parentData.state and fall back to null if parentData doesn't exist. I don't see a cleaner way to state that, but I'm open to suggestions.


Despite code to support settings.toml it fail for me

I encountered a few MagTag and MatrixPortal projects that failed on me except if I create the proper secrets.py. And this even if I create a file settings.toml.
Initially I believed those library were not updated, but I found code here to support both the old and the new way is define in the code, but despite that I fail to make it work and I always get secrets.py related message.
Could someone have a look?
I know my settings.toml is OK because using the todbot trick below, I have the expected result: my IP addr: <IP_ADDRESS>
https://github.com/todbot/circuitpython-tricks#what-the-heck-is-settingstoml
import os, wifi
print("connecting...")
wifi.radio.connect(ssid=os.getenv('CIRCUITPY_WIFI_SSID'),
                   password=os.getenv('CIRCUITPY_WIFI_PASSWORD'))
print("my IP addr:", wifi.radio.ipv4_address)

Update... with 9.0.0-a-5 it works with only the file settings.toml without any secrets.py. (it also works with only secrets.py.
So the problem would only be with the 8.x family. Still os.getenv("") seems to work in 8.x, so I do not really understand what is going on.

I think the frozen libraries in the 8.2.x branch have not been updated in a long time.