Plugin attempts to set volume when AVR is off

Seem to be seeing a few of these errors in my HA logs at the moment:
Logger: aiopioneer.pioneer_avr
Source: custom_components/pioneer_async/media_player.py:412
Integration: Pioneer AVR ([documentation](https://github.com/crowbarz/ha-pioneer_async))
First occurred: 16 August 2022 at 22:32:33 (8 occurrences)
Last logged: 21 August 2022 at 20:37:53

AVR command 073VL returned error: E02

It appears that this happens when the AVR is switched off which according to the docs that I have:
E02<CR+LF> | NOT AVAILABLE   NOW | Detected   the Command line which could not work now. |
-- | -- | -- | --
Perhaps a check needs to be added to ensure that the AVR is powered on?

Yes, this is expected behaviour, though the HA UI guards against being able to send volume up/down/set service calls to media players when they are off. HA does not however prevent service calls from being directly made to a media player that is off, for any media player. So it would be useful to understand what else was happening on your system (eg. scripts, automations, external events) immediately before the volume set command.
As far as I can see in the code, volume set is only ever sent to the AVR if requested via a service call.

My apologies, was tired when I posted this... indeed it is an automation lol.
Thank you for having a look :)


improve autozooming on non-gpx background data layers

The original implementation only worked for Points and LineStrings, but GeoJSON and KML can contain any geometry.
Aso, d3 is a bit special when working with GeoJSON Polygons: it does require clockwise winding, but typical GeoJSON uses either counterclockwise winding (RFC7946) or "winding doesn't matter" mode (old geojson.org spec). When inputing such GeoJSON (or KML) input, iD would zoom out all the way, which is not the intended behavior.

Also, d3 is a bit special when working with GeoJSON Polygons: it does require clockwise winding,

Whoa I did not know this, good catch.. All the GeoJSONs I tried this with contained LineStrings..


Report errors for unproductive nonterminals (GH issue #1)

Hi @linkrope, tried to solve the issue #1.
First real D programming! :smile:
I added a new option --ignore-nonproductive to force the code generation even if there are non-productive non-terminals for mimic the behavior we had before.
Not sure, whether it is better to pass Arguments as argument down as Analyze() or only the boolean value of the option. Please advice.
I also renamed the Warning() method as now it covers the determination of unreachable non-terminals only.

@linkrope, do you have an idea, why the build fails?

@linkrope, do you have an idea, why the build fails? I just checked, I have it in my local environment too but cannot explain it to me...

The test runner is a separate mainfunction, so it's necessary to exclude the module with the real main function:

Excluding main source file src/epsilon/main.d from test.

But your import epsilon.main : Arguments; will then result in unresolved references.
Two options:

extract Arguments in a different module - I don't like this, because Arguments kind of documents the usage of main
use Settings - what's only relevant for main stays hidden in the main module

BTW:  "ignore-nonproductive" is very specific; there could be (too) many similar options.
What's the purpose of this option: does not make sense to let the compiler fail...

Thanks for the hint. Had already the assumption it is caused by the import.
I guess, I would go with the Settings solution.

BTW: "ignore-nonproductive" is very specific; there could be (too) many similar options.
What's the purpose of this option: does not make sense to let the compiler fail...

You mean, we could skip the option at all?
I'm wondering a little bit why it did not cause an error with Modual-2 at Epsilon. I guess, I just would like to repeat the Epsilon behavior from the past with that option.
But there is no way around the D compile problem, right? So we should let the generator just fail in that case, isn't it?

That would be worth an experiment: what happens if you declare all nonterminals productive, even if they are not? If some nonterminals are not productive, no code is generated for them, so that the compiler detects errors afterwards. What if code is generated anyway? (Which must somehow fail at runtime because the nonterminal is just not productive).
I think the option is indeed questionable. With the VS Code Plugin the situation can occur that nonterminals are not (yet) productive. But for the compiler generation, both ways are possible: I abort, because the result makes no sense, or I generate code for non-productive nonterminals, because I warned that you use the compiler at your own risk...

Considering your comment at the issue #1, it would make sense to let the generator fail with an error if the start symbol is not productive. For other non-terminals a warning is sufficient.
This would also work well for the VS code extension as it intended to be permanently in the situation of unfinished specifications as long as work is ongoing.
I will change the PR code for that.

@linkrope, I changed the PR implementation such that the generator fails only if the start symbol is unproductive. For all other unproductive nonterminals a warning is issued as before.
This works also well with the VS code plugin while having uncompleted specifications. With the warning for an unproductive non-terminal some other additional warnings appear (from the ELL1 parser generator):
warn: generated compiler contains corrupt code for non-productive nonterminals
warn: generated compiler contains corrupt code for non-productive nonterminals

Unfortunately, the VS code plugin seems to have an issue to list warnings, if only warnings have occurred.
I know, this PR has a branch conflict.
I guess, I will close this PR and reopen a new one as resolving this conflict with git in VS code is beyond my current capabilities.
If possible, I would very appreciate, if you could take a look on  the commit 5d9ef8c. I have adapted dub.json to allow issue tests running separately from example tests. Is that OK, from DUB configuration point of view?

I'm going to close this PR as it has a conflict and is replaced by the more concise and conflict free PR #13.


PIVPN stopped after no changes - cant't explain it

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[] I have read and understood the contributors guide.
[] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
Have you searched for similar issues and solutions?
(yes/no / which issues?)

Console output of      curl -L install.pivpn.io | bash
  Output Here

Console output of      pivpn add or pivpn add nopass
  Output Here

Console output of      pivpn debug
  Output Here

Have you taken any steps towards solving your issue?
  which?

I've been using PIVPN here in the UK and my place in Spain, no problem for a year or more.  Currently both are on PI4 and have been for weweks. The onl odd circumstances are broadband issues here for the same amount of time. 3 days ago PIVPN here stopped working or rather my Pocophone could not connect to it, neither could/can my wife's phone.
Today the Vodaphone broadband is working just fine, so with that out of the way I tried again. No joy, so rather than mess about I read your instructions here. https://github.com/pivpn/pivpn/wiki/Upgrading
I uninstalled PVPN and reinstalled... I the ncleared the client file fom my phone and made a new one. I am of course running th phone on lonly mobile data, not the house Internet. My Voda router has port redirects to the relevant (none standard but very close) port number. I tried to connect the phone and the result shos that PiVPN is SEEING the phone - but won; connect.
Nov 11 16:37:21 ukpi4 ovpn-server[746]: <IP_ADDRESS>:30655 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 16:37:19 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 16:37:21 ukpi4 ovpn-server[746]: <IP_ADDRESS>:30655 TLS Error: incoming packet authentication failed from [AF_INET]<IP_ADDRESS>:30655
HELP...

Please fill the issue template first (replace Output Here with the output of the requested commands).

The install was done months ago - and works a treat in one property and has worked every day for months in this property without fail - until last week when Vodafone broadband started giving me trouble - the broadband has ben ok dince yesterday but still no VPN, no other changes that I can think of - and it cannot be my mobile phone client as the OTHER VPN is working just fine. AFTER this I did a full re-install of PIVPN exactly as your recommendation - and it makes no difference. I checked, the Vodafone people did not disable port redirections.  I've tested both UDP and TCP now, neither will let the client connect. Any thoughts?
Here is the output just now of PIVPN DEBUG
pivpn debug
::: Generating Debug Output
::::            PiVPN debug              ::::
::::            Latest commit            ::::
commit d0c10db6ec391961b7201fb564055c1176ca73e3
Author: 4s3ti<EMAIL_ADDRESS>Date:   Tue Sep 3 10:09:48 2019 +0200
install.sh: apt-get with , uninstall.sh: added var PKG_MANAGER and replaced apt-get with

=============================================
::::        Installation settings        ::::
/etc/pivpn/DET_PLATFORM -> Raspbian
/etc/pivpn/FORWARD_CHAIN_EDITED -> 0
/etc/pivpn/HELP_SHOWN ->
/etc/pivpn/INPUT_CHAIN_EDITED -> 0
/etc/pivpn/INSTALL_PORT -> 1195
/etc/pivpn/INSTALL_PROTO -> udp
/etc/pivpn/INSTALL_USER -> pi
/etc/pivpn/NO_UFW -> 1
/etc/pivpn/pivpnINTERFACE -> eth0
::::    setupVars file shown below       ::::
INSTALL_USER=pi
UNATTUPG=unattended-upgrades
pivpnInterface=eth0
IPv4dns=
IPv4addr=<IP_ADDRESS>
IPv4gw=<IP_ADDRESS>
pivpnProto=udp
PORT=1195
ENCRYPT=2048
APPLY_TWO_POINT_FOUR=false
DOWNLOAD_DH_PARAM=false
PUBLICDNS=
OVPNDNS1=<IP_ADDRESS>
OVPNDNS2=<IP_ADDRESS>
::::  Server configuration shown below   ::::
dev tun
proto udp
port 1195
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b.crt
key /etc/openvpn/easy-rsa/pki/private/ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b.key
dh /etc/openvpn/easy-rsa/pki/dh2048.pem
topology subnet
server <IP_ADDRESS> <IP_ADDRESS>
Set your primary domain name server address for clients
push "dhcp-option DNS <IP_ADDRESS>"
push "dhcp-option DNS <IP_ADDRESS>"
Prevent DNS leaks on Windows
push "block-outside-dns"
Override the Client default gateway by using <IP_ADDRESS>/1 and
<IP_ADDRESS>/1 rather than <IP_ADDRESS>/0. This has the benefit of
overriding but not wiping out the original default gateway.
push "redirect-gateway def1"
client-to-client
keepalive 1800 3600
remote-cert-tls client
tls-version-min 1.2
tls-auth /etc/openvpn/easy-rsa/pki/ta.key 0
cipher AES-256-CBC
auth SHA256
user nobody
group nogroup
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
syslog
verb 3
#DuplicateCNs allow access control on a less-granular, per user basis.
#Remove # if you will manage access by user instead of device.
#duplicate-cn
Generated for use by PiVPN.io
=============================================
::::  Client template file shown below   ::::
client
dev tun
proto udp
remote REMOTE 1195
resolv-retry infinite
nobind
persist-key
persist-tun
key-direction 1
remote-cert-tls server
tls-version-min 1.2
verify-x509-name ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
::::    Recursive list of files in       ::::
::: /etc/openvpn/easy-rsa/pki shows below :::
/etc/openvpn/easy-rsa/pki/:
ca.crt
crl.pem
Default.txt
dh2048.pem
extensions.temp
index.txt
index.txt.attr
index.txt.attr.old
index.txt.old
issued
openssl-easyrsa.cnf
private
renewed
revoked
safessl-easyrsa.cnf
serial
serial.old
ta.key
ukpi4.ovpn
/etc/openvpn/easy-rsa/pki/issued:
ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b.crt
ukpi4.crt
/etc/openvpn/easy-rsa/pki/private:
ca.key
ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b.key
ukpi4.key
/etc/openvpn/easy-rsa/pki/renewed:
private_by_serial
reqs_by_serial
/etc/openvpn/easy-rsa/pki/renewed/private_by_serial:
/etc/openvpn/easy-rsa/pki/renewed/reqs_by_serial:
/etc/openvpn/easy-rsa/pki/revoked:
private_by_serial
reqs_by_serial
/etc/openvpn/easy-rsa/pki/revoked/private_by_serial:
/etc/openvpn/easy-rsa/pki/revoked/reqs_by_serial:
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] OpenVPN is running
:: [OK] OpenVPN is enabled (it will automatically start on reboot)
:: [OK] OpenVPN is listening on port 1195/udp
::::      Snippet of the server log      ::::
Nov 11 22:37:11 ukpi4 ovpn-server[746]: REDACTED:15001 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 22:37:05 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 22:37:11 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: incoming packet authentication failed from [AF_INET]REDACTED:15001
Nov 11 22:37:12 ukpi4 ovpn-server[746]: REDACTED:15001 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 22:37:05 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 22:37:12 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: incoming packet authentication failed from [AF_INET]REDACTED:15001
Nov 11 22:37:13 ukpi4 ovpn-server[746]: REDACTED:15001 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 22:37:05 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 22:37:13 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: incoming packet authentication failed from [AF_INET]REDACTED:15001
Nov 11 22:37:14 ukpi4 ovpn-server[746]: REDACTED:15001 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 22:37:05 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 22:37:14 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: incoming packet authentication failed from [AF_INET]REDACTED:15001
Nov 11 22:37:15 ukpi4 ovpn-server[746]: REDACTED:9266 TLS: Initial packet from [AF_INET]REDACTED:9266, sid=27fabd9e 22da0379
Nov 11 22:37:16 ukpi4 ovpn-server[746]: REDACTED:9266 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time =<PHONE_NUMBER>) Mon Nov 11 22:37:15 2019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Nov 11 22:37:16 ukpi4 ovpn-server[746]: REDACTED:9266 TLS Error: incoming packet authentication failed from [AF_INET]REDACTED:9266
Nov 11 22:37:49 ukpi4 ovpn-server[746]: REDACTED:1024 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Nov 11 22:37:49 ukpi4 ovpn-server[746]: REDACTED:1024 TLS Error: TLS handshake failed
Nov 11 22:37:49 ukpi4 ovpn-server[746]: REDACTED:1024 SIGUSR1[soft,tls-error] received, client-instance restarting
Nov 11 22:38:05 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Nov 11 22:38:05 ukpi4 ovpn-server[746]: REDACTED:15001 TLS Error: TLS handshake failed
Nov 11 22:38:05 ukpi4 ovpn-server[746]: REDACTED:15001 SIGUSR1[soft,tls-error] received, client-instance restarting
Nov 11 22:38:15 ukpi4 ovpn-server[746]: REDACTED:9266 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Nov 11 22:38:15 ukpi4 ovpn-server[746]: REDACTED:9266 TLS Error: TLS handshake failed
Nov 11 22:38:15 ukpi4 ovpn-server[746]: REDACTED:9266 SIGUSR1[soft,tls-error] received, client-instance restarting
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.txt

Jeez @scargill  .. it was hard to read!!
Edited your comment to get the debug output in a code block

Output of grep tls /etc/openvpn/easy-rsa/pki/ukpi4.ovpn?

Here, meanwhile a pal of mine is on - remotely from his home and he cannot get in but again on debug(good tip) I can see him try and fail... so port redirection is definitely still working.
sudo grep tls /etc/openvpn/easy-rsa/pki/ukpi4.ovpn
remote-cert-tls server
tls-version-min 1.2

I updated the comment, try the new one

Not sure what that was about...

Clearly I and a collage can get to the PIVPN from our moile phones (which contact my Spanish PIVPN no prolem and talked to THIS one until Vodaphone remoted into my modem at the weekend - but as you can see, TLS negotation (I know little about that) fails in a previously perfectly working setup. I have to speak to Vodaphone tomorrow so any insights would be GREATLY appreciated. The port redirection still works or the server would not see the mobiles trying to connect....

I updated the comment, try the new one

Not sure what that was about...

Output of grep 'tls\|direction' /home/pi/ovpns/ukpi4.ovpn?

Meaning: grep for tls or direction and post the results.

Clearly I and a colleague can get to the PIVPN from our mobile phones (which contact my Spanish PIVPN no prolem and talked to THIS one until Vodaphone remoted into my modem at the weekend

Better ask Vodafone what they changed first.

TLS negotation (I know little about that) fails in a previously perfectly working (for msny months) PIVPN setup.

I usually get those TLS error when there is a poor connection between the client and the server. From the output I think your mobile tries to contact the PiVPN but it doesn’t receive an answer from the server, so it resends the packet (replay error).

The port redirection still works or the server would not see the mobiles trying to connect....

Yes for sure.

Here it is, TinCanTech
grep 'tls|direction' /home/pi/ovpns/ukpi4.ovpn
key-direction 1
remote-cert-tls server
tls-version-min 1.2

@scargill Do you have a <tls-auth> section inside the .ovpn file you use to connect (ukpi4 i think)?

Hi
Before the CERTinfo, this is what the client file has..
client
dev tun
proto udp
remote <IP_ADDRESS> 1195
resolv-retry infinite
nobind
persist-key
persist-tun
key-direction 1
remote-cert-tls server
tls-version-min 1.2
verify-x509-name ukpi4_2c4c30a8-071a-4ab3-a316-95dfb87fac4b name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3

I know but it’s not what I asked for, I asked whether your client file has a  block at the end, like this one:

Do not post the content, just confirm.

Hi
Right - confirming - it DOES... pretty much like that but the "key direction 1" i s much higher up the file...

FTR:
Authenticate/Decrypt packet error: bad packet ID (may be a replay)
This is a non-fatal error and for the most part can be ignored.
(Further information about replays is available in the OpenVPN manual)
TLS Error: incoming packet authentication failed
This is a fatal error.
However, when the packet fails authentication due to incorrect --tls-auth the message would normally include HMAC, which is the purpose of --tls-auth.
This is definately a problem originating from OpenVPN itself but here are some things we (OpenVPN) tend to recommend to people:
Client config generally should not include:
persist-tun
persist-key

These are option intended for use by the server (PiVPN should take this into account in future).
keepalive 1800 3600

This completely defeats the purpose of --keepalive because almost all router/firewalls UPD port will timeout within 30 seconds. --keepalive 15 120 maybe more suitable. Also, be aware --pings are not sent while the VPN passes data (PiVPN should take this into account in future).
However, these simple changes may not be the cause of your issue and in such cases we (OpenVPN) recommend that the user try using --proto tcp (Server and client, obviously).

i
This install I have them in 2 properties, one is working, the other worked for months until last week. I used PIVPN and understand VERY little about the inner workings...
I've just tsken a copy of the client file, renamed and removed persist-run and persist-key from the file before importing it into my phone. Made no difference.  I don;t know how to make changes at the server (Raspberry Pi) end but I CAN use NANO. HELP??
Pete

@scargill I know that correlation does not imply causality but since everything worked before Vodafone made the change I’d suggest that that’s the cause, expecially since you had two identical setups? Does the phone you use to (attempt to) connect to the faulty pivpn work with the other pivpn?

@scargill - Try rebooting your server before you try the problem client.

@scargill - Try rebooting your server before you try the problem client.
Hi Orazioedoardo and TinCanTech...   I've not only rebooted he server, I've tried ininstalling and reinstalling PIVPN. Yes, the client(s) connect just fine to my other site - and TRY to connect to this site (the server knows they tried) but there is a TLS failure.

It gets worse, after the Vodafone tech guy supposedly "adjusted the noise floor" on my router remotely, he promised an engineer would be there within 72 hours.  I then contacted Voda and was promised at night (by a female called "Ankita" - all logged) that I could talk to their dedicated VPN team during the day so I contacted them the next day and the tech support guy insisted that Vodafone do not have a VPN support team - and won't take responsibility for VPN issues. That started a chain of complaints currently in progress.
So, I've tried my phone, my wife's phone, my colleague's computer (several miles North). In each case the Raspberry Pi running PiVPN sees them attempting to come in - but there's a TLS failure and won't let them in.

@TinCanTech
Actually keepalive was 10 120 in the past but someone sent a pull request to change that. Makes sense to me: 1800 seconds between ping is way bigger that the typical NAT timeout so the connection will expire before the client and the server have a chance to ping each other. However, since we are tunnelling everything, empirically (especially for a mobile phone), it's unlikely that no packets will be exchanged for 1800 seconds (DNS common).
Regarding persist-key and persist-tun, it's not clear from the manual that they are meant for the server side, in fact it's suggested in the client config too [here](https://github.com/OpenVPN/openvpn/blob/master/sample/sample-config-files/client.conf
@scargill
Try the suggested changes, edit the server configuration with sudo nano /etc/openvpn/server.conf and change keepalive 1800 3600 to keepalive 10 120, then restart the server with sudo systemctl restart openvpn.
If it still doesn't work, edit the server configuration again and replace proto udp with proto tcp, then restart the server. Make the same change in the client config as well.

Orazio - do you have ANY idea how happy you have made me? The keepalive changes made no difference, but that and the move to TCP FIXED the problem.  On Tuesday an Indian woman told me to get onto the Vodafone "dedicated vpn team during the day, so YESTERDAY I rang them and the tech support guy insisted they don't HAVE a VPN team.  As this has worked for months until their guy remoted into my router at the weekend, was that a coincidence or is there something I can do at the router end (as Vodafone clearly don;t know now to) to restore UDP. I have opened the port for both TCP and UDP access. THANK YOU and others who have provided feedback.

@orazioedoardo

--keepalive
The problem with the current --keepalive is that the VPN will not detect any issues (timeout etc) for at least 1 hour.  Maybe this is something which does not often effect your users but it is not something I would do.  PiVPN's choice though ..
--persist-*
The --persist-* settings are only useful when the process drops privileges, eg. --user nobody, --group nobody, which is only commonly done on the server. PiVPN's choice though .. However, we have seen that using these settings in the client can sometimes disturb reconnects, especially true when certain keys go out of sync, unfortunately, the cause is not really clear. (The sample files are meant only as a guide)

@scargill If TCP works but UDP does not make very sure that the client configs have the right keys etc. Also, make sure your firewall is setup correctly. Otherwise, sorry I cannot really help any more than that. Maybe it is Vodaphone have done something wrong .. curious ..

@TinCanTech Thanks for the insights! I will submit a pull request with those changes providing your rationale.

FYI: I have been active in the openvpn community for around 8 years and have been actively participating in openvpn devel for much of that time.

@scargill - Try rebooting your server before you try the problem client.

Hi Orazioedoardo and TinCanTech...   I've not only rebooted he server, I've tried ininstalling and reinstalling PIVPN.

I just want to ensure here that you have updated the client to the newly re-installed server PKI, I presume that all certificates and keys were recreated ?

Guess this can be closed now.
reopen if i am wrong.

All working - thanks
From: 4s3ti<EMAIL_ADDRESS>Sent: 03 February 2020 11:52
To: pivpn/pivpn<EMAIL_ADDRESS>Cc: Peter Scargill<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [pivpn/pivpn] PIVPN stopped after no changes - cant't explain it (#864)
Guess this can be closed now.
reopen if i am wrong.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pivpn/pivpn/issues/864?email_source=notifications&email_token=AAONJA273JVQA66O67ZMNATRBAAPLA5CNFSM4JLX75SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKTSARY#issuecomment-581378119 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAONJAYIN7K6I4K2P5TD2TDRBAAPLANCNFSM4JLX75SA .  https://github.com/notifications/beacon/AAONJA32SPJ4RMO5MS6ASDLRBAAPLA5CNFSM4JLX75SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKTSARY.gif


Parser config doesn't persist when change options, saves when ruleset not saved

1- Edit a ruleset
2- Select a different parser and then the original (don't save)
3- original parser config gone
1- Edit a ruleset
2- Select a different parser
3- go back to ruleset list without saving
4- edit ruleset again
The parser has changed even though ruleset wasn't saved

Can no longer change the parser.


When will the chat data release? Thanks!

Hi @REIGN12 ,
Thanks for your attention!
We will release the pre-training data within one week, including both instruction and conversation data.
Please stay tuned. :-)
Best,
Zhihong

Hi @REIGN12,
We have released the data for training Phoenix and Chimera. Thanks for your attention!
Best,
Zhihong


Policies incompatible with Terraform

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: all
azure provider: all
module: all
Description
Due to the way the azurerm provider works, the following Policy Definitions are incompatible with Terraform:

Deny-Subnet-Without-NSG
Deny-Subnet-Without-UDR

Steps to Reproduce

Create a deployment where these policies are assigned at a specific scope.
Place a Subscription under this scope.
Try to create a Virtual Network with Subnets missing NSG and UDR configurations (note that even if you add these using the approach available by Terraform, the deployment fails)

Screenshots

Additional context

Considering the option to set these to "Audit" as default effect in the Terraform module.
Does anyone have thoughts on how best to approach this?
Also thinking this could be developed alongside updating the module to simplify the approach for controlling whether DINE policies are enabled or not, in alignment with the guidance recently published by @jtracey93: Adopt policy-driven guardrails

We did set these to "Audit" to workaround this issue.
To do this we used a custom archetype_extension and set the required parameter:
File lib/archetype_extension_es_landing_zones.tmpl.json
{
  "extend_es_landing_zones": {
    "policy_assignments": [],
    "policy_definitions": [],
    "policy_set_definitions": [],
    "role_definitions": [],
    "archetype_config": {
      "parameters": {
        "Deny-Subnet-Without-Nsg": {
          "effect": "Audit"
        }
      },
      "access_control": {}
    }
  }
}

Probably we could set this parameter as default in the archetype_definition here?
In addition a mention in the docs?
Then it would be easy for users to customize the effect again ...
But this would be rather a patch than your proposed changes from the linked CAF article.
Did you asked how to fix the root cause? Sry I'm no help here.

Thanks @nikolai-fraport for sharing your insights here, that's certainly a good way to do this 👍
Myself & @krowlandson have just been discussing this and have agreed that we will provide guidance similar to what you have shared above in a Wiki docs page, adding to what we say here already https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/[User-Guide]-Getting-Started#additional-considerations-when-deploying-landing-zone-resources-with-terraform
Likely this section will become a new Wiki page on its own and the "Getting Started" page will be left as just that.
We will also be bringing this back up with the relevant engineering teams internally to work out a better approach than effectively changing the policies desired effect.

Trigger ADO Sync


Bug: Scroll not working

Is there any existing issue for this?

[X] I have searched the existing issues

Description
When we are trying to hold to scroller and trying to pull it down it not going down the onto
Screenshots
[BUG] git_opener.webm
Any additional information?
No response
What browser are you seeing the problem on?
Chrome

Do you want to fix this issue?

Do you want to fix this issue?

Sure !
I will give it a try 💯

but it's working now.
https://user-images.githubusercontent.com/88102392/226159418-834a99c0-1c8d-4e30-8473-5101eafe698e.mp4

but it's working now.

It is still not working in my browser

but it's working now.

It is still not working in my browser

ok ok. Currently, I'm using Brave. Try to restart your browser

yes it's working now
thanks for helping out


Added support for table slides

Wanted to use this gem to create a deck with table slides, so I added Presentation#add_table_slide and relevant code

Thanks @wbutler1331 for your contribution. Sorry for the delay, I have been out for a while.
Can you please resolve the conflicts with master branch and resubmit your pull request?


In dark mode, the font of lists in the Notes tab is not readable.

There is obviously no notation for the font color.

Fixed with e84e8a3.


⚠ Secret Website 3 has degraded performance

In df7a584, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 28632 ms

Resolved: Secret Website 3 performance has improved in 050a482.


Fix Bug294 for Hi Haddock

This makes Haddock not crash on Bug294 (or html-test in general). The output looks correct, although with the usual extra kind annotations Hi Haddock sprinkles all over the place.
/cc @sjakobi

This is fantastic! :) Thanks a bunch, Alec!


Gripper of Pincher Arm differs from reality

I've freshly cloned & built the turtlebot_arm & the arbotix repository (I had to remove the object_manipulation folder to get my build done, but I don't use it anyway). My physical Pincher Arm is connected to /dev/ttyUSB0. In order to move it around with MoveIt & Rviz, I had to change in the turtlebot_arm_moveit_config/demo.launch file the simulation arg for the arm bringup launch file to false as shown here:
<include file="$(find turtlebot_arm_bringup)/launch/arm.launch">      <arg name="simulation" value="false"/>   </include>
When I now start the MoveIt demo with roslaunch turtlebot_arm_moveit_config demo.launch  I can plan & execute and the pincher arm moves to the goal. But if I change the Planning Group in Rviz to "gripper" instead of "arm" (under "Planning Request" in Rviz), I can still plan & execute, the gripper moves in Rviz and the logging says the Gripper Controller succeeded. But my real robot gripper doesn't move a bit, even with various different positions.
Every second I also get a log like this:
[ WARN] [1524497161.302061425]: The complete state of the robot is not yet known.  Missing gripper_joint
I suspect my error has something to do with this. Also in Rviz, only one of the two gripper parts can be moved, while on the real pincher robot arm, it is a parallel gripper where both parts move symmetrically.
Edit:
Right after opening this issue I found a solution to the first part: I had to use this arbotix_ros repository instead of the one mentioned above, then my gripper could move! Even though the logging tells a different story:

[ INFO] [1524498261.159729581]: Planning adapters have added states at index positions: [ 0 ]
[ INFO] [1524498266.793112394]: Execution request received for ExecuteTrajectory action.
[INFO] [1524498266.841353]: Gripper controller action goal recieved:0.014877 m
[INFO] [1524498266.841908]: Gripper publish servo goal: -1.4771 rad
[ERROR] [1524498267.674998461]: Controller is taking too long to execute trajectory (the expected upper bound for the trajectory execution was 0.841428 seconds). Stopping trajectory.
[ INFO] [1524498267.675095360]: Cancelling execution for gripper_controller
[WARN] [1524498267.677588]: Gripper Controller: Preempted.
[ INFO] [1524498267.741294827]: Execution completed: TIMED_OUT
[ INFO] [1524498267.771785352]: ABORTED: Timeout reached

This doesn't always happen though.
But the gripper in Rviz of course still isn't symmetrical, so any suggestions on how to fix this difference between simulation & real world is still welcome.
Can someone help me with this? Thank you!
Cheers

As I mentioned, the gripper of the Pincher arm differs from the real robot. In addiditon, I had to modify the turtlebot_arm_moveit_config/config/pincher_arm.srdf file in order to get my pincher arm (and gripper) move around (in Gazebo):

add a <passive_joint name="gripper_link_joint" />
rename the base_link of the kinematic chain of the planning group arm from base_link to arm_base_link (as it is in the turtlebot_arm.srdf file), so the whole group tag looks like this:

<group name="arm">         <chain base_link="arm_base_link" tip_link="gripper_link" />     </group>
I don't know if this is necessary or not, but maybe someone finds this difference from the pincher_arm.srdf to the turtlebot_arm.srdf file interesting/useful.
Note that I didn't have to do this when moving the real pincher arm, but rather to move it around in Gazebo. I currently can do the latter only with a self-written control-package and not with the arbotix controllers, so maybe this modifications aren't necessary when using the arbotix controllers.

Hi!
For the first point, there's a PR opened ages ago to make arbotix work with the pitcher. So would be great if you can put it up-to-date and ping arbotix maintainers to merge it so it makes it way to the next release!
I'm re-reading my documentation and it says: To use the PhantomX Pincher .... You will need arbotix_ros version 0.11.0 What is funny cause last released version is 0.10.0. So I suppose this means that you need a for integrating the above mentioned PR.
For the malformed gripper, please try this PR. By using it. the gripper appears in RViz in the right place. But I cannot tell if it works because I don't have a real Pitcher nor works on Gazebo (as you explained). I didn't merge the PR cause used to conflict somehow with kobuki plugin (read my comments), but it seems to work now with Gazebo9. So if you try it and works, I will merge.

Hi!
I'm already using the pull request version of arbotix_ros 0.11.0 you mentioned, otherwise I couldn't move the real pincher arm.
Regarding the other PR, I've adapted my files according to the changes suggested in the PR, including the mechanicalReduction set to 2 in the transmission-tag for the gripper_joint. I can see an improvement when planning & executing gripper positions (grip_open, grip_closed etc.) in Rviz: both fingers are now moved when selecting a goal state, even though the gri_open position seems too wide:

When looking at it in Gazebo, sometimes opening/closing the gripper works for one finger (the gripper_active_link), but the other one (gripper_active2_link) stands still like before integrating the PR:

On other occasions, the execution fails with the error message

Controller is taking too long to execute trajectory (the expected upper bound for the trajectory execution was 0.985854 seconds). Stopping trajectory.

Additionally, the gripper_active_link doesn't seem to be correctly attached, as it glitches away from the gripper ground plane, mostly after moving the arm:

I have to mention here that I currently don't use any arbotix controllers at all when simulating the arm in Gazebo (only when moving the real arm, which I don't have problems with anymore), because I couldn't get it to work yet. Instead, I'm using a tinkered control-package (can be found here) and I had to slightly modify the turtlebot_arm_moveit_config/config/controllers.yaml file (see here), so maybe some of my issues come from this rather ugly workaround.
This malformed gripper isn't that much of an issue for my project, as long as I can move the arm in Gazebo, but it would still be nice to have a "correct" gripper in gazebo.

Hey @joellutz, most probably this comes too late, but I just noticed that these people are using the Pincher arm and have their own repo. As they are selling the arm,  I would expect that the description is correct,


feature: pass network info to onReady

FYI in my PR here #31, I removed the direct dependency to web3. We'll see, your PR is probably gonna be merged first so I'll just fix it when it does.


python311Packages.meshtastic: 2.2.7 -> 2.2.8

Diff: https://github.com/meshtastic/Meshtastic-python/compare/refs/tags/2.2.7...2.2.8
Changelog: https://github.com/meshtastic/python/releases/tag/2.2.8
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.meshtastic
python310Packages.meshtastic.dist
python311Packages.meshtastic
python311Packages.meshtastic.dist


Support for Windows Home edition yes/no?

This page mentions the following: https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure
When looking at the following page though: https://www.microsoft.com/en-us/windowsforbusiness/compare, we see no support mentioned for Home edition?
So my questions would be:
a) Is Home edition supported or not supported for targetign WIP?
Thanks in advance,
Kenneth van Surksum
[Enter feedback here]

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

ID: c1ad3f92-24de-5eb5-8454-c72d85737183
Version Independent ID: 900125eb-31ea-faf3-ac30-7c3d7b30f611
Content: Create a Windows Information Protection (WIP) policy with MDM using the Azure portal for Microsoft Intune (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
Product: w10
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

@kennethvs . I think Professional , education and enterprise editions are supported

@kennethvs : https://www.microsoft.com/en-us/windowsforbusiness/compare is correct, Windows 10 Home is not supported.
Which part of the referenced MS Docs page causes confusion in this regard? The "Applies to:" section?
Please note that unless specified, the Microsoft Docs pages for Windows 10 are specifically targeting IT Pros, as showcased here:

https://docs.microsoft.com/en-us/windows/windows-10/ (Windows 10 resources and documentation for IT Pros)

Please also note that the majority of the pages are intended for Enterprise use, so there are cases where not even Windows 10 Pro is supported.

@kennethvs
It seems that the question has been answered by the community,  and thus the issue is being marked as resolved.
Please note that the issues section of the repository is intended for corrections in technical documentation.
Should you need to ask a similar question again, consider asking the question via the Windows 10 Support channel.
Thank you.

@e0i: My comment was referring to the https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure page which mentions support for WIP-WE on Windows Home.
Also related to the "intended for enterprise use" remark, Even though the OS is Home, the application (Office 365) is targeted towards Enterprise.
If it's still not supported I will log an issue on the page mentioned above and ask them to remove the reference to Windows Home.
/Kenneth


Automated cherry pick of #8116: umount nfs on detach storage

Cherry pick of #8116 on release/3.4.
#8116: umount nfs on detach storage

/lgtm
/approve


Apple Watch support?

Hi, I changed nothing and iOS app reporting working since 2x days. I want to say thank you, your effort was really helpful!!
One more question, is it possible to include glucose level to Apple Watch ? I would prefer to see it all time as "widget"
Hope you had an idea

@iDustbin
Would be beneficial, when you closed this ticket, that you at least post the solution to your issue :)


Docker error exec /usr/local/bin/docker-entrypoint.sh: exec format error

Hi,
I am trying to make it work with docker but I keep getting following error
exec /usr/local/bin/docker-entrypoint.sh: exec format error

It kinda sounds like it might be a problem with docker. The best advice I can give is to maybe try reinstalling docker.
Otherwise, you could consider cloning the repo and running the code outside of the docker container. That requires just a little bit more setup though.

Thank you for responding.
I was able to make it work on a PI device by by rebuilding docker image by changing Dockerfile to use buster image
FROM node:16-buster-slim

Great! Glad you got it working

FROM node:16-buster-slim

Can you please elaborate for a noob? Where do I put this? Thanks!


DataObject accept arrays or stdClass

The constructor of DataObject can take an array or stdClass for $record.
However, it is access as an array here and here
This pull request ensures $record is an array after validation

Hmm, good point.
I think we should just be accepting arrays, to be honest. I can't see the benefit in accepting a stdClass.

stdClass support was added intentionally in #917, I’m not sure how this wasn’t picked up then!

As we intentionally added support for this we should fix it, though I agree we should probably remove this support and only accept arrays. Added tests and merged in https://github.com/silverstripe/silverstripe-framework/commit/599c054d4fd7c2ef9a97abd5491585511c3edb1b. Thanks @russellshome!


SmartThings Poweron/off error command

api/smartthings.py changes:
Change lines #439 and #433 to prepend _command before async send
#439
await self._async_send_command(_command(COMMAND_POWER_OFF))
instead of
_await self.async_send_command(COMMAND_POWER_OFF)
#443
await self._async_send_command(_command(COMMAND_POWER_ON))
instead of
_await self.async_send_command(COMMAND_POWER_ON)

@mariomazon we are already merging ollo69's fork in a different branch
@ollo69 i presume this PR was made without ur knowledge? should we close it in favor of the branch we're working on?

I see this PR just now.
Of course we need to go ahead with dedicated branch and merge in master only when we will be ready. I created just now a PR in the dedicated branch for the issue in SmartThings power commands.


nuxt 3 dark mode refresh page broken

TuSimple/naive-ui version (版本)
2.33.3
Vue version (Vue 版本)
3.2.39
Browser and its version (浏览器及其版本)
Version 105.0.5195.125 (Official Build) (64-bit)
System and its version (系统及其版本)
ubuntu 22
Node version (Node 版本)
16
Reappearance link (重现链接)
https://github.com/productdevbook/oku-nuxt3-template
Reappearance steps (重现步骤)
yarn install
yarn dev
open -> http://localhost:3000/naive
dark mode select
refresh page
Expected results (期望的结果)
dark mode working
Actual results (实际的结果)
half dark half white mode
Remarks (补充说明)

and white this problem

In SSR Mode. color.preference is always white. It results in the SSR output using light theme variables & causes the style glitch.
If you want SSR page output correct result. You need to make theme a param of URL.

I don't really care if the SSR output respects the client's color scheme, but I'd at least like it to hydrate properly once rendered client side. This doesn't always seem to work as expected for some naive-ui components.

As you can see here, the SSR NButton is rendered with the light theme, while the Client Only NButton is rendered with dark (wrapped in ClientOnly tag). In my experience, the only naive-ui components that are hydrated correctly are those that are forced to load/reload client side (e.g. relying on async data or wrapped in ClientOnly tag).
I'm sure there's a far better method for getting around this, but my simple hack was adding a plugin to hook into the page:finish lifecycle hook, and then simply toggle dark mode off and on (only if already enabled):
// plugins/setTheme.client.ts

export default defineNuxtPlugin((nuxtApp) => {

    const isDark = useDark()

    // SSR is causing dark mode hydration issues with naive-ui
    // This fix quickly toggles dark mode on 'page:finish' hook
    nuxtApp.hook('page:finish', () => {
        setTimeout(() => {
            const prefersDark = usePreferredDark()
            isDark.value = false

            setTimeout(() => {
                isDark.value = prefersDark.value
            }, 0)
        }, 0)
    })

    return {
        provide: {
            isDark
        }
    }

})

<!-- app.vue -->

<template>
<div>
    <nuxt-layout>
        <n-config-provider :theme="$isDark ? darkTheme : lightTheme">
            <n-message-provider>
                <n-dialog-provider>
                    <nuxt-page />
                </n-dialog-provider>
            </n-message-provider>
        </n-config-provider>
    </nuxt-layout>
</div>
</template>

<script lang="ts" setup>
import { NMessageProvider, NConfigProvider, NDialogProvider } from 'naive-ui';
import { darkTheme, lightTheme } from 'naive-ui';

const { $isDark } = useNuxtApp()

</script>

I think this is still a bug. When the server renders, and then sends it to the client to render as well, the client actually gets the color pattern responsively and passes the prop to the NConfigProvider component accordingly, but the components don't respond to the change correctly.

Alternative workaround:
<NConfigProvider :theme>
  <!-- your code here -->
</NConfigProvider>

import { darkTheme } from "naive-ui"

const theme = ref(null)
watchPostEffect(
  () => theme.value = colorMode.value === "dark" ? darkTheme : null
)

The trick is the delayed theme change by watchPostEffect.


Adding "resume" lifecycle event

Just a thought: Would it not be nice to have a "resume" lifecycle in vue-router? So adding an event callback by jumping back to a visited component?

Ok. Cool.


DSC meta configuration

PR Summary
Fix #282
This PR adds settings/policy JSON files support.
A particular dsc setting value (e.g. dsc resource search path) can be specified in any of the locations below.
Override order:

policy file. Writable only by Admins, but readable by everyone:

on WIndows: $env:ProgramData+"\dsc\settings.dsc.json"
on Linux: "/etc/dsc/settings.dsc.json"

command-line parameters. e.g.  --trace-level  or --trace-format
main active settings file: settings.dsc.json in dsc executable directory
default settings file: default_settings.v1.dsc.json in dsc executable directory. Should not be modified by user and intended to be used in dsc upgrade scenarios as well as reset settings to defaults scenario. Version in the filename is a version of setting schema to support possible future breaking changes in settings schema.

Format and defaults for policy/settings currently look like this and described in detail in the spec:
{
  "resource_path": {
    "allow_env_override": true,
    "append_env_path": true,
    "directories": []
  },
  "tracing": {
    "level": "WARN",
    "format": "Default",
    "allow_override": true
  }
}

To clarify, the scope of this initial PR is just to get DSC working with the settings/policy files, correct? The CLI / resource for getting and defining the values will follow in a future PR?

To clarify, the scope of this initial PR is just to get DSC working with the settings/policy files, correct? The CLI / resource for getting and defining the values will follow in a future PR?

Yes and Yes.


Use with Heltec Wifi Kit 32

https://robotzero.one/heltec-wifi-kit-32/
This looks like a great little board for the metriful. Comes with a handy little display. It uses the same esp32 chips as the Arduino Nano 33 IoT.
Will this work with the Heltec wifi 32?

This Heltec board should be hardware compatible with the Metriful MS430 (it is the correct voltage and has an I2C port). So it should work OK, as long as you can adapt/create the software yourself.
If you want to use the software examples on this repository, you will need to add a section to host_pin_definitions.h
It probably uses the Wire library for I2C, just like the Arduinos. The WiFi commands/setup may need editing but are probably similar to the ones for the NodeMCU/ESP8266.


Fix attempts for Ubuntu 20.04 Focal

Integrated changes suggested in https://github.com/rsnk96/Ubuntu-Setup-Scripts/issues/87 along with some minor updates

Changed shutter to Flamehot, keeping shortcut of Ctrl+Shift+P the same
Atom installation method updated
Changed tmux-copy mode to be on by default
Force-usage of gcc-8 for opencv compilation
Travis builds for 20.04

@rajat2004  any idea why a travis build didn't get triggered with this PR?

It got triggered, but the build did not start since there was an indentation err in the .yml file. Request can be seen by going to  More Options -> Requests

The matrix build isn't working and from the scarce info I can get from some Github issues, we'll need to specify each job separately. I've updated the travis.yml file to use SCRIPT env variable to distinguish between which script/s to run, and a single place for all of them. The last commit also removes running of opencv test in gdb, this is the same as https://github.com/rsnk96/Ubuntu-Setup-Scripts/pull/86 which needs to be looked into

Looks like Tensorflow is also having similar problems, probably with the updated GCC. But it seems like a pain to be able to change this: https://github.com/bazelbuild/bazel/issues/4077
Assuming we can't figure out a fix for this, I think we should just leave the tensorflow installation in Build-ML.sh with the error (the TF team should hopefully fix it soon). What's your take?
3,398 / 3,405] 2 actions running
    Compiling tensorflow/core/distributed_runtime/graph_mgr.cc; 7s local
    Compiling tensorflow/core/kernels/concat_lib_gpu.cc; 5s local
ERROR: /home/travis/.cache/bazel/_bazel_travis/2792edddbcfba0186411ea8a4b7952f1/external/grpc/BUILD:507:1: C++ compilation of rule '@grpc//:gpr_base' failed (Exit 1)
[3,400 / 3,406] Compiling .../core/distributed_runtime/graph_mgr.cc; 7s local
biguating new declaration of 'long int gettid()'
   43 | static long gettid(void) { return syscall(__NR_gettid); }
      |             ^~~~~~
In file included from /usr/include/unistd.h:1170,
                 from external/grpc/src/core/lib/gpr/log_linux.cc:41:
/usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: old declaration '__pid_t gettid()'
   34 | extern __pid_t gettid (void) __THROW;
      |                ^~~~~~
[3,400 / 3,406] Compiling .../core/distributed_runtime/graph_mgr.cc; 7s local
[3,401 / 3,406] checking cached actions
mand lines of failed build steps.
[3,401 / 3,406] checking cached actions
INFO: Elapsed time: 3632.308s, Critical Path: 106.11s
[3,401 / 3,406] checking cached actions
INFO: 3143 processes: 3143 local.
[3,401 / 3,406] checking cached actions
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully


Fix warning in rustc 1.29.0-nightly

This PR removes the following warning in rustc 1.29.0-nightly.
4 | #[derive(Message)]
|          ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= note: #[warn(proc_macro_derive_resolution_fallback)] on by default
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 <https://github.com/rust-lang/rust/issues/50504>

Yes, super:: is appropriate here :)
Thank you for heads up on warning

@DoumanAsh could you make new release

@fafhrd91 I'm not sure if I can publish actix crates on crates.io but if you're busy I think we're fine with time as rustc 1.29 is still far

@DoumanAsh I was mentioned in rustc issue :)


”Vânătorii Mici” is listed in the drop-down menu

Description:
"Vânătorii Mici" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Vânătorii Mici" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Vânătorii Mici, GIURGIU".


📃:  Loan Repayment Prediction

:red_circle: Title :  Loan Repayment Prediction
:red_circle: Aim : Predict the Repayment of Loan
:red_circle: Brief Explanation : Use Machine Learning Algorithms to predict if a person would be able to repay his loans or not
Screenshots 📷
 N/A

:white_check_mark: To be Mentioned while taking the issue :

Full name :  Aviral Garg
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.) SSOC Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@aviralgarg05 go ahead.


Getting: Error response from daemon: Container  is not running

This error message is being returned when I try and submit a spark job to a newly created cluster. Cluster created with:
aztk spark cluster create --id sparky --vm-size standard_a2 --size 1 --docker-repo aztk/python:spark2.2.0-python3.6.2-base
Job submit:
aztk spark cluster submit --id sparky --name pythonpi pi.py
I'm at commit:
commit 1d9d9cabb90ad1b896b40972e27d2bd55429d1ff
Bug: fix loading local spark config (#282)

This error means that somewhere along the way the container exited, so no submits will work.
If the cluster is still around,  you should be able to log onto the host to get the docker logs. From there debugging should be a little easier.
To get those logs, you would need to run:
aztk spark cluster ssh --id <cluster-id> --username <username> --host
If you don't have a user, you can create one with:
aztk spark cluster add-user --id <cluster-id> --username <username>
Then, once you are ssh'ed into the node, you can get logs by running:
sudo docker logs spark

Here is the log output:
sudo docker logs spark Starting setup using Docker Collecting azure-batch==3.0.0 (from -r /batch/startup/wd/requirements.txt (line 1))   Downloading azure_batch-3.0.0-py2.py3-none-any.whl (281kB) Collecting pyyaml==3.12 (from -r /batch/startup/wd/requirements.txt (line 2))   Downloading PyYAML-3.12.tar.gz (253kB) Collecting azure-nspkg>=2.0.0 (from azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading azure_nspkg-2.0.0-py2.py3-none-any.whl Collecting msrestazure~=0.4.7 (from azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading msrestazure-0.4.19-py2.py3-none-any.whl Collecting azure-common~=1.1.5 (from azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading azure_common-1.1.8-py2.py3-none-any.whl Collecting msrest~=0.4.17 (from msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading msrest-0.4.22-py2.py3-none-any.whl Collecting adal~=0.4.0 (from msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading adal-0.4.7-py2.py3-none-any.whl (49kB) Collecting keyring>=5.6 (from msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading keyring-10.5.1-py2.py3-none-any.whl Collecting requests-oauthlib>=0.5.0 (from msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading requests_oauthlib-0.8.0-py2.py3-none-any.whl Collecting isodate>=0.5.4 (from msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading isodate-0.6.0-py2.py3-none-any.whl (45kB) Collecting requests~=2.14 (from msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading requests-2.18.4-py2.py3-none-any.whl (88kB) Collecting certifi>=2017.4.17 (from msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading certifi-2017.11.5-py2.py3-none-any.whl (330kB) Collecting PyJWT>=1.0.0 (from adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading PyJWT-1.5.3-py2.py3-none-any.whl Collecting python-dateutil>=2.1.0 (from adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading python_dateutil-2.6.1-py2.py3-none-any.whl (194kB) Collecting cryptography>=1.1.0 (from adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading cryptography-2.1.4-cp35-cp35m-manylinux1_x86_64.whl (2.2MB) Collecting secretstorage; sys_platform == "linux2" or sys_platform == "linux" (from keyring>=5.6->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading SecretStorage-2.3.1.tar.gz Collecting oauthlib>=0.6.2 (from requests-oauthlib>=0.5.0->msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading oauthlib-2.0.6.tar.gz (127kB) Collecting six (from isodate>=0.5.4->msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading six-1.11.0-py2.py3-none-any.whl Collecting urllib3<1.23,>=1.21.1 (from requests~=2.14->msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading urllib3-1.22-py2.py3-none-any.whl (132kB) Collecting idna<2.7,>=2.5 (from requests~=2.14->msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading idna-2.6-py2.py3-none-any.whl (56kB) Collecting chardet<3.1.0,>=3.0.2 (from requests~=2.14->msrest~=0.4.17->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading chardet-3.0.4-py2.py3-none-any.whl (133kB) Collecting cffi>=1.7; platform_python_implementation != "PyPy" (from cryptography>=1.1.0->adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading cffi-1.11.2-cp35-cp35m-manylinux1_x86_64.whl (419kB) Collecting asn1crypto>=0.21.0 (from cryptography>=1.1.0->adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading asn1crypto-0.24.0-py2.py3-none-any.whl (101kB) Collecting pycparser (from cffi>=1.7; platform_python_implementation != "PyPy"->cryptography>=1.1.0->adal~=0.4.0->msrestazure~=0.4.7->azure-batch==3.0.0->-r /batch/startup/wd/requirements.txt (line 1))   Downloading pycparser-2.18.tar.gz (245kB) Installing collected packages: azure-nspkg, oauthlib, certifi, urllib3, idna, chardet, requests, requests-oauthlib, six, isodate, msrest, PyJWT, python-dateutil, pycparser, cffi, asn1crypto, cryptography, adal, secretstorage, keyring, msrestazure, azure-common, azure-batch, pyyaml   Running setup.py install for oauthlib: started     Running setup.py install for oauthlib: finished with status 'done'   Running setup.py install for pycparser: started     Running setup.py install for pycparser: finished with status 'done'   Running setup.py install for secretstorage: started     Running setup.py install for secretstorage: finished with status 'done'   Running setup.py install for pyyaml: started     Running setup.py install for pyyaml: finished with status 'done' Successfully installed PyJWT-1.5.3 adal-0.4.7 asn1crypto-0.24.0 azure-batch-3.0.0 azure-common-1.1.8 azure-nspkg-2.0.0 certifi-2017.11.5 cffi-1.11.2 chardet-3.0.4 cryptography-2.1.4 idna-2.6 isodate-0.6.0 keyring-10.5.1 msrest-0.4.22 msrestazure-0.4.19 oauthlib-2.0.6 pycparser-2.18 python-dateutil-2.6.1 pyyaml-3.12 requests-2.18.4 requests-oauthlib-0.8.0 secretstorage-2.3.1 six-1.11.0 urllib3-1.22 Running main.py script starting org.apache.spark.deploy.master.Master, logging to /home/spark-current/logs/spark--org.apache.spark.deploy.master.Master-1-b0ae1a9494814effa269d0d13e8f7e39000000.out failed to launch: nice -n 0 /home/spark-current/bin/spark-class org.apache.spark.deploy.master.Master --host b0ae1a9494814effa269d0d13e8f7e39000000.0fn24to4wihuvlujvgxdb32sab.fx.internal.cloudapp.net --port 7077 --webui-port 8080 -h <IP_ADDRESS> --webui-port 8080 full log in /home/spark-current/logs/spark--org.apache.spark.deploy.master.Master-1-b0ae1a9494814effa269d0d13e8f7e39000000.out Failed to copy /batch/startup/wd/conf/spark-env.sh [Errno 2] No such file or directory: '/batch/startup/wd/conf/spark-env.sh' Failed to copy /batch/startup/wd/conf/core-site.xml [Errno 2] No such file or directory: '/batch/startup/wd/conf/core-site.xml' Failed to copy /batch/startup/wd/conf/spark-defaults.conf [Errno 2] No such file or directory: '/batch/startup/wd/conf/spark-defaults.conf' copy /batch/startup/wd/jars/azure-storage-2.0.0.jar to /home/spark-current/jars/azure-storage-2.0.0.jar copy /batch/startup/wd/jars/hadoop-azure-datalake-3.0.0-alpha2.jar to /home/spark-current/jars/hadoop-azure-datalake-3.0.0-alpha2.jar copy /batch/startup/wd/jars/hadoop-azure-2.7.3.jar to /home/spark-current/jars/hadoop-azure-2.7.3.jar copy /batch/startup/wd/jars/azure-data-lake-store-sdk-2.0.11.jar to /home/spark-current/jars/azure-data-lake-store-sdk-2.0.11.jar Pool has no master. Trying to assign itself! (1/5) Assignment was successfull! Node tvm-171039672_2-20171217t133653z is the new master. Setting up as master.  I'm going to push a fix for this momentarily.

Hi Will, I just merged a change that should fix this issue. Could pull the latest changes and let me know that this has been resolved?

Closing, fixed in #288


only two ok

output:
$ python -V
Python 3.10.4
$ pip -V
pip 22.1.2 from /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pip (python 3.10)
$ ruby -v
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21]
$ pip install pyyaml
Requirement already satisfied: pyyaml in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (6.0)
$ pip install numpy
Requirement already satisfied: numpy in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (1.23.0)
$ python run_tests.py

Looking for "ruby", "py2rb/builtins/module.rb", "py2rb/builtins/require.rb" [3]:
..                                                               [OK]
tests/test_builtins.rb [1]: .                                    [OK]
tests/algorithms/sqrt.py [4]: .                                [FAIL]
tests/algorithms/triangulation.py [4]: .                       [FAIL]
tests/basic/assert.py [4]: .                                   [FAIL]
tests/basic/assign.py [4]: .                                   [FAIL]
tests/basic/assign_slice.py [4]: .                             [FAIL]
tests/basic/augassign.py [4]: .                                [FAIL]
tests/basic/augassign2.py [4]: .                               [FAIL]
tests/basic/binaryops.py [4]: .                                [FAIL]
tests/basic/break.py [4]: .                                    [FAIL]
tests/basic/class.py [4]: .                                    [FAIL]
tests/basic/class2.py [4]: .                                   [FAIL]
tests/basic/class3.py [4]: .                                   [FAIL]
tests/basic/class4.py [4]: .                                   [FAIL]
tests/basic/class5.py [4]: .                                   [FAIL]
tests/basic/class6.py [4]: .                                   [FAIL]
tests/basic/closure.py [4]: .                                  [FAIL]
tests/basic/closure_in_class.py [4]: .                         [FAIL]
tests/basic/continue.py [4]: .                                 [FAIL]
tests/basic/del_array.py [4]: .                                [FAIL]
tests/basic/del_attr.py [4]: .                                 [FAIL]
tests/basic/del_dict.py [4]: .                                 [FAIL]
tests/basic/del_slice.py [4]: .                                [FAIL]
tests/basic/dictcomp1.py [4]: .                                [FAIL]
tests/basic/dictcomp2.py [4]: .                                [FAIL]
tests/basic/dictionary.py [4]: .                               [FAIL]
tests/basic/dictionary2.py [4]: .                              [FAIL]
tests/basic/dictionary3.py [4]: .                              [FAIL]
tests/basic/docstring.py [4]: .                                [FAIL]
tests/basic/embedding.py [4]: .                                [FAIL]
tests/basic/fib.py [4]: .                                      [FAIL]
tests/basic/float2int.py [4]: .                                [FAIL]
tests/basic/for_in.py [4]: .                                   [FAIL]
tests/basic/for_range1.py [4]: .                               [FAIL]
tests/basic/for_range2.py [4]: .                               [FAIL]
tests/basic/for_step.py [4]: .                                 [FAIL]
tests/basic/getattr.py [4]: .                                  [FAIL]
tests/basic/globalvar.py [4]: .                                [FAIL]
tests/basic/hasattr1.py [4]: .                                 [FAIL]
tests/basic/helloworld.py [4]: .                               [FAIL]
tests/basic/ifelse.py [4]:                                     [FAIL]
tests/basic/ifs.py [4]: .                                      [FAIL]
tests/basic/ifs2.py [4]: .                                     [FAIL]
tests/basic/keys.py [4]: .                                     [FAIL]
tests/basic/kwargs.py [4]: .                                   [FAIL]
tests/basic/kwargs2.py [4]:                                    [FAIL]
tests/basic/kwargs3.py [4]: .                                  [FAIL]
tests/basic/lambda.py [4]: .                                   [FAIL]
tests/basic/lambda2.py [4]:                                    [FAIL]
tests/basic/lambda3.py [4]:                                    [FAIL]
tests/basic/lambda_map.py [4]: .                               [FAIL]
tests/basic/list.py [4]: .                                     [FAIL]
tests/basic/list2.py [4]: .                                    [FAIL]
tests/basic/list3.py [4]: .                                    [FAIL]
tests/basic/listcomp1.py [4]:                                  [FAIL]
tests/basic/literals.py [4]: .                                 [FAIL]
tests/basic/logicalops.py [4]: .                               [FAIL]
tests/basic/loops.py [4]: .                                    [FAIL]
tests/basic/multiassign.py [4]: .                              [FAIL]
tests/basic/none.py [4]: .                                     [FAIL]
tests/basic/numeric.py [4]: .                                  [FAIL]
tests/basic/oo.py [4]: .                                       [FAIL]
tests/basic/oo_attributes.py [4]: .                            [FAIL]
tests/basic/oo_inherit.py [4]: .                               [FAIL]
tests/basic/oo_inherit2.py [4]: .                              [FAIL]
tests/basic/oo_inherit3.py [4]: .                              [FAIL]
tests/basic/oo_inherit_simple.py [4]: .                        [FAIL]
tests/basic/oo_inherit_simple_super1.py [4]: .                 [FAIL]
tests/basic/oo_inherit_simple_super2.py [4]: .                 [FAIL]
tests/basic/oo_inherit_simple_super3.py [4]:                   [FAIL]
tests/basic/oo_static_inherit.py [4]: .                        [FAIL]
tests/basic/pass.py [4]: .                                     [FAIL]
tests/basic/print.py [4]: .                                    [FAIL]
tests/basic/raise.py [4]: .                                    [FAIL]
tests/basic/raise2.py [4]: .                                   [FAIL]
tests/basic/scope.py [4]: .                                    [FAIL]
tests/basic/set.py [4]: .                                      [FAIL]
tests/basic/str1.py [4]: .                                     [FAIL]
tests/basic/str_endswith.py [4]: .                             [FAIL]
tests/basic/sumcomp.py [4]: .                                  [FAIL]
tests/basic/super1.py [4]: .                                   [FAIL]
tests/basic/super2.py [4]: .                                   [FAIL]
tests/basic/trueorfalse.py [4]: .                              [FAIL]
tests/basic/try.py [4]: .                                      [FAIL]
tests/basic/tuple.py [4]: .                                    [FAIL]
tests/basic/tuple2.py [4]: .                                   [FAIL]
tests/basic/vargs.py [4]: .                                    [FAIL]
tests/basic/while.py [4]: .                                    [FAIL]
tests/basic/with.py [4]: .                                     [FAIL]
tests/collections/ordered_dict.py [4]: .                       [FAIL]
tests/decorator/function1.py [4]: .                            [FAIL]
tests/decorator/function2.py [4]: .                            [FAIL]
tests/decorator/function3.py [4]: .                            [FAIL]
tests/decorator/property.py [4]: .                             [FAIL]
tests/decorator/setter.py [4]: .                               [FAIL]
tests/deep-learning-from-scratch/and_gate.py [4]:              [FAIL]
tests/deep-learning-from-scratch/relu.py [4]:                  [FAIL]
tests/deep-learning-from-scratch/sigmoid.py [4]:               [FAIL]
tests/deep-learning-from-scratch/step_function.py [4]:         [FAIL]
tests/errors/py_collision.py [4]: .                            [FAIL]
tests/functions/and.py [4]: .                                  [FAIL]
tests/functions/append.py [4]: .                               [FAIL]
tests/functions/aug.py [4]: .                                  [FAIL]
tests/functions/bitand.py [4]: .                               [FAIL]
tests/functions/bitor.py [4]: .                                [FAIL]
tests/functions/bitxor.py [4]: .                               [FAIL]
tests/functions/divfloor.py [4]: .                             [FAIL]
tests/functions/float.py [4]: .                                [FAIL]
tests/functions/floatdiv.py [4]: .                             [FAIL]
tests/functions/gtge.py [4]: .                                 [FAIL]
tests/functions/in.py [4]: .                                   [FAIL]
tests/functions/int.py [4]: .                                  [FAIL]
tests/functions/isinstance.py [4]: .                           [FAIL]
tests/functions/len.py [4]: .                                  [FAIL]
tests/functions/lshift.py [4]: .                               [FAIL]
tests/functions/ltle.py [4]: .                                 [FAIL]
tests/functions/ne.py [4]: .                                   [FAIL]
tests/functions/or.py [4]: .                                   [FAIL]
tests/functions/pop.py [4]: .                                  [FAIL]
tests/functions/rshift.py [4]: .                               [FAIL]
tests/functions/sort.py [4]: .                                 [FAIL]
tests/functions/str.py [4]: .                                  [FAIL]
tests/functions/ubitcomp.py [4]: .                             [FAIL]
tests/functions/uminus.py [4]: .                               [FAIL]
tests/functions/uplus.py [4]: .                                [FAIL]
tests/lists/all.py [4]: .                                      [FAIL]
tests/lists/any.py [4]: .                                      [FAIL]
tests/lists/extend.py [4]: .                                   [FAIL]
tests/lists/filter.py [4]: .                                   [FAIL]
tests/lists/in.py [4]: .                                       [FAIL]
tests/lists/insert.py [4]: .                                   [FAIL]
tests/lists/map.py [4]: .                                      [FAIL]
tests/lists/max.py [4]: .                                      [FAIL]
tests/lists/min.py [4]: .                                      [FAIL]
tests/lists/reverse.py [4]: .                                  [FAIL]
tests/lists/subclass.py [4]: .                                 [FAIL]
tests/lists/subclass2.py [4]: .                                [FAIL]
tests/lists/subclass3.py [4]: .                                [FAIL]
tests/lists/sum.py [4]: .                                      [FAIL]
tests/lists/sum2.py [4]: .                                     [FAIL]
tests/lists/xrange.py [4]: .                                   [FAIL]
tests/lists/zip.py [4]: .                                      [FAIL]
tests/modules/classname.py [4]: .                              [FAIL]
tests/modules/from_import.py [4]: .                            [FAIL]
tests/modules/from_import_as_module.py [4]: .                  [FAIL]
tests/modules/import.py [4]: .                                 [FAIL]
tests/modules/import_alias.py [4]: .                           [FAIL]
tests/modules/import_as_module.py [4]: .                       [FAIL]
tests/modules/import_class.py [4]: .                           [FAIL]
tests/modules/import_global.py [4]: .                          [FAIL]
tests/modules/import_init.py [4]:                              [FAIL]
tests/modules/import_multi.py [4]: .                           [FAIL]
tests/numpy/abs.py [4]:                                        [FAIL]
tests/numpy/all.py [4]:                                        [FAIL]
tests/numpy/any.py [4]:                                        [FAIL]
tests/numpy/arange.py [4]:                                     [FAIL]
tests/numpy/array2string.py [4]:                               [FAIL]
tests/numpy/asarray.py [4]:                                    [FAIL]
tests/numpy/ellipsis.py [4]:                                   [FAIL]
tests/numpy/empty.py [4]:                                      [FAIL]
tests/numpy/ext_slice.py [4]:                                  [FAIL]
tests/numpy/full.py [4]:                                       [FAIL]
tests/numpy/insert.py [4]:                                     [FAIL]
tests/numpy/like.py [4]:                                       [FAIL]
tests/numpy/linspace.py [4]:                                   [FAIL]
tests/numpy/max_min.py [4]:                                    [FAIL]
tests/numpy/maximum_minimum.py [4]:                            [FAIL]
tests/numpy/ndarray.py [4]:                                    [FAIL]
tests/numpy/ndarray2.py [4]:                                   [FAIL]
tests/numpy/ndarray3.py [4]:                                   [FAIL]
tests/numpy/not_like.py [4]:                                   [FAIL]
tests/numpy/np_copy.py [4]:                                    [FAIL]
tests/numpy/product.py [4]:                                    [FAIL]
tests/numpy/random_rand.py [4]:                                [FAIL]
tests/numpy/random_randint.py [4]:                             [FAIL]
tests/numpy/random_random.py [4]:                              [FAIL]
tests/numpy/random_uniform.py [4]:                             [FAIL]
tests/numpy/special_values.py [4]:                             [FAIL]
tests/numpy/sqrt.py [4]:                                       [FAIL]
tests/numpy/sum.py [4]:                                        [FAIL]
tests/numpy/trigonometric_funcitons.py [4]:                    [FAIL]
tests/numpy/type.py [4]:                                       [FAIL]
tests/os/path_basename.py [4]: .                               [FAIL]
tests/os/path_dirname.py [4]: .                                [FAIL]
tests/os/path_join.py [4]: .                                   [FAIL]
tests/os/walk.py [4]: .                                        [FAIL]
tests/random/random_random.py [4]: .                           [FAIL]
tests/six/integer_types.py [4]: .                              [FAIL]
tests/six/iteritems.py [4]: .                                  [FAIL]
tests/six/itervalues.py [4]: .                                 [FAIL]
tests/six/moves.range.py [4]: .                                [FAIL]
tests/six/py23.py [4]: .                                       [FAIL]
tests/strings/count.py [4]: .                                  [FAIL]
tests/strings/find.py [4]: .                                   [FAIL]
tests/strings/join.py [4]: .                                   [FAIL]
tests/strings/lstrip0.py [4]: .                                [FAIL]
tests/strings/lstrip1.py [4]: .                                [FAIL]
tests/strings/replace.py [4]: .                                [FAIL]
tests/strings/rfind.py [4]: .                                  [FAIL]
tests/strings/rstrip0.py [4]: .                                [FAIL]
tests/strings/rstrip1.py [4]: .                                [FAIL]
tests/strings/split.py [4]: .                                  [FAIL]
tests/strings/splitlines.py [4]: .                             [FAIL]
tests/strings/string_format_combined_simple.py [4]: .          [FAIL]
tests/strings/string_format_d.py [4]: .                        [FAIL]
tests/strings/string_format_d_simple.py [4]: .                 [FAIL]
tests/strings/string_format_f_simple.py [4]: .                 [FAIL]
tests/strings/string_format_i.py [4]: .                        [FAIL]
tests/strings/string_format_s_simple.py [4]: .                 [FAIL]
tests/strings/string_format_u.py [4]: .                        [FAIL]
tests/strings/strings_in_strings.py [4]: .                     [FAIL]
tests/strings/strip.py [4]: .                                  [FAIL]
tests/strings/strip1.py [4]: .                                 [FAIL]
tests/strings/ulcase.py [4]: .                                 [FAIL]
tests/strings/zipstring.py [4]: .                              [FAIL]
tests/unittest/assertAlmostEqual.py [4]: .                     [FAIL]
tests/unittest/assertEqual.py [4]: .                           [FAIL]
tests/unittest/assertIn.py [4]: .                              [FAIL]
tests/unittest/assertIs.py [4]: .                              [FAIL]
tests/unittest/assertIsInstance.py [4]: .                      [FAIL]
tests/unittest/assertRaises.py [4]: .                          [FAIL]
tests/unittest/assertTrue.py [4]: .                            [FAIL]
tests/unittest/class.py [4]: .                                 [FAIL]
Ran 224 tests in 14.336s

FAILED (failures=222)

This repo has gone stale and i've forked it here https://github.com/nanobowers/py2rb for use with newer rubies/pythons and fixed some additional bugs. Can you try that out and if it doesn't work submit an issue over there?


file with special characters breaks terminal output

I have a file on disk named â€œGroupMembers.csvâ€  (where the last 3 chars are e2 80 9d in hex), when I list the directory contents with dir this stops terminal output and waits for input. Happens with powershell, command prompt. Ubuntu ls behaves slightly differently, lists the file as â€œGroupMembers.csvâ€\302\235, but completes successfully.
A regular cmd.exe dir works fine in this directory.

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #10310 for more discussion.
/dup #10310


[SYSRST_CTRL] No interrupt is raised when combo detect bat_disable action is set

The combo interrupt status register reads 0 when the combo detect bat_disable action is set. This register gets updated only when the  COM_OUT_CTL_0.interrupt_0 action is set. Below is the piece of code which shows the register is updated only when interrupt to opentitan action is set:
assign combo_bat_disable_pulse = cfg_bat_disable_en_i & combo_det_pulse;
assign combo_ec_rst_pulse      = cfg_ec_rst_en_i & combo_det_pulse;
assign combo_gsc_pulse         = cfg_rst_req_en_i & combo_det_pulse;
assign combo_intr_pulse_o      = cfg_intr_en_i & combo_det_pulse;
assign {combo_intr_status_o.combo3_h2l.de,
combo_intr_status_o.combo2_h2l.de,
combo_intr_status_o.combo1_h2l.de,
combo_intr_status_o.combo0_h2l.de} = combo_intr_pulse;
assign sysrst_ctrl_combo_intr_o = |combo_intr_pulse;
This also applies when ec_rst, rst_req actions are set.

Command to run the test
./util/dvsim/dvsim.py hw/ip/sysrst_ctrl/dv/sysrst_ctrl_sim_cfg.hjson -i sysrst_ctrl_combo_detect --waves --tool xcelium --fixed-seed<PHONE_NUMBER>
PR9586 can be used to generate the scenario.

Indeed, I believe this is not a bug but intended behavior. I.e., if the interrupt is not configured as a combo action, the interrupt status register will not be updated.

Ok got it. In order to check if the other combo action is raised when interrupt is not configured as a combo action can we use below signals from top level:

aon_bat_disable_hw  - To check if bat_disable action is raised after detecting the combos
aon_ec_rst_l_hw - To check ec_rst action
aon_sysrst_ctrl_rst_req_o - To check rst_req action
combo_status_register - To check interrupt action

Indeed, signals 1. - 3. can be used to check whether the associated action is triggered or not.
Note however that 1. and 2. go through the output override module - so their value depends on whether the outputs are overridden or inverted.
As for 4.: these CSRs are only set if the interrupt combo action is configured, as far as I can tell from RTL.

I just noticed signals 1 and 2 are local signals to combo detect modules, so we can't use them to check in the tb as these are not brought up at the top level. Is there any other register/signals from the top level which can tell us that bat_disable or ec_rst combo action is set?
For 4. Can we add this point to specification document?

Hey @patel-madhuri,
aon_bat_disable_hw, aon_ec_rst_l_hw are indeed internal, but they are observable at the sysrst_ctrl output as well. I.e., these internal signals go through the override logic and inverter blocks, and are then output via cio_bat_disable_o and cio_ec_rst_l_o, see below:

As for 4., yes I can add it to the CSR description: #9824


Install texlive-core in gh-page workflow

The current documentation is broken since m.css is not able to find latex
https://github.com/ami-iit/bipedal-locomotion-framework/runs/4235942651?check_suite_focus=true#step:6:3407
This should fix it. Before merging it I will check the artifact updated by the action

I don't know why but the action called gh-page is not running anymore 😭


Amazon Linux Checksum failing S3 hosted JDK Chef::Exceptions::ChecksumMismatch

I have the JDK 7 file on an S3 bucket; and have the recipe attributes over-ridden by the role used to run the Java recipe:
{
    "name": "java-appserver",
    "default_attributes": {},
    "override_attributes": {
        "java": {
            "jdk": {
                "7": {
                    "x86_64": {
                        "url": "https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz"
                    }
                }
            },
            "oracle": {
                "accept_oracle_download_terms": true
            }
        }
    },
    "json_class": "Chef::Role",
    "chef_type": "role",
    "run_list": [
        "recipe[java]"
    ]
}

However; I'm unable to get this working as the gz never downloads to /var/chef/cache/jdk-7u75-linux-x64.tar.gz. When I do a client run with debug; chef downloads the file to a /tmp location but it never ends up in the chef cache. Therefore the checksum fails.
[2015-03-26T00:07:10+00:00] DEBUG: downloading tarball from an unofficial repository

    * remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] action create_if_missing[2015-03-26T00:07:10+00:00] INFO: Processing remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] action create_if_missing (/var/chef/cache/cookbooks/java/providers/ark.rb line 128)
[2015-03-26T00:07:10+00:00] DEBUG: remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] checking for changes
[2015-03-26T00:07:10+00:00] DEBUG: turning gzip compression off due to filename ending in gz
[2015-03-26T00:07:10+00:00] DEBUG: Cache control headers: {}
[2015-03-26T00:07:10+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
[2015-03-26T00:07:10+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
[2015-03-26T00:07:10+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
[2015-03-26T00:07:10+00:00] DEBUG: Initiating GET to https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz
[2015-03-26T00:07:10+00:00] DEBUG: ---- HTTP Request Header Data: ----
[2015-03-26T00:07:10+00:00] DEBUG: ---- End HTTP Request Header Data ----
[2015-03-26T00:07:10+00:00] DEBUG: ---- HTTP Status and Header Data: ----
[2015-03-26T00:07:10+00:00] DEBUG: HTTP 1.1 200 OK
[2015-03-26T00:07:10+00:00] DEBUG: x-amz-id-2: DZ1HkwFDKoQP0RZpDgPiCcImRPySzMTU+7M2dDrr/we9osc3FQhxOqyal03069Jv
[2015-03-26T00:07:10+00:00] DEBUG: x-amz-request-id: 0A7F8F1A32132E05
[2015-03-26T00:07:10+00:00] DEBUG: date: Thu, 26 Mar 2015 00:07:11 GMT
[2015-03-26T00:07:10+00:00] DEBUG: last-modified: Wed, 25 Mar 2015 23:39:49 GMT
[2015-03-26T00:07:10+00:00] DEBUG: etag: "6259b6b6a732e590d9c20ced0a340638-3"
[2015-03-26T00:07:10+00:00] DEBUG: accept-ranges: bytes
[2015-03-26T00:07:10+00:00] DEBUG: content-type: application/x-gzip
[2015-03-26T00:07:10+00:00] DEBUG: content-length: 142245547
[2015-03-26T00:07:10+00:00] DEBUG: server: AmazonS3
[2015-03-26T00:07:10+00:00] DEBUG: connection: close
[2015-03-26T00:07:10+00:00] DEBUG: ---- End HTTP Status/Header Data ----
[2015-03-26T00:07:10+00:00] DEBUG: Streaming download from https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz to tempfile /tmp/chef-rest20150326-9426-12ck2b0
[2015-03-26T00:07:10+00:00] DEBUG: disable_gzip is set.             Not using              and initializing noop stream deflator.
[2015-03-26T00:07:10+00:00] DEBUG: Chef::HTTP::StreamHandler calling Chef::HTTP::ValidateContentLength::ContentLengthCounter#handle_chunk
[2015-03-26T00:07:10+00:00] DEBUG: Chef::HTTP::StreamHandler calling Chef::HTTP::Decompressor::NoopInflater#handle_chunk
<snip>
[2015-03-26T00:07:20+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_stream_complete
[2015-03-26T00:07:20+00:00] DEBUG: Content-Length validated correctly.
[2015-03-26T00:07:20+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_stream_complete
[2015-03-26T00:07:20+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_stream_complete
      ================================================================================
      Error executing action `create_if_missing` on resource 'remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz]'
      ================================================================================

      Chef::Exceptions::ChecksumMismatch
      ----------------------------------
      Checksum on resource (6f1f81) does not match checksum on content (460959)

I thought this may be like other Amazon Linux issues with S3 having the Content-Encoding set incorrectly https://github.com/agileorbit-cookbooks/java/issues/225 ; but it seems not. In the case of Issue 225 the tarball is put in the chef cache; but there are issues with the gzip handling on S3.
Curl for me doesn't show a gzip Content-Encoding header:
[root@ip-172-21-1-4 tmp]# curl --header 'Accept: application/x-gzip' -I -vvv https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz
*   Trying <IP_ADDRESS>...
* Connected to s3-ap-southeast-2.amazonaws.com (<IP_ADDRESS>) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
* Server certificate:
* 	subject: CN=*.s3-ap-southeast-2.amazonaws.com,O="Amazon.com, Inc.",L=Seattle,ST=Washington,C=US
* 	start date: Oct 02 00:00:00 2014 GMT
* 	expire date: Sep 12 23:59:59 2015 GMT
* 	common name: *.s3-ap-southeast-2.amazonaws.com
* 	issuer: CN=VeriSign Class 3 Secure Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US
> HEAD /seek-simian-army/build/jdk-7u75-linux-x64.tar.gz HTTP/1.1
> User-Agent: curl/7.40.0
> Host: s3-ap-southeast-2.amazonaws.com
> Accept: application/x-gzip
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< x-amz-id-2: v8BwQQpssmKP821UNXTqELlNMImAtkBZ6kbeIFjSMyiGyIHCy+3rurVlklhHSanj
x-amz-id-2: v8BwQQpssmKP821UNXTqELlNMImAtkBZ6kbeIFjSMyiGyIHCy+3rurVlklhHSanj
< x-amz-request-id: A4DDF21BB45BB05B
x-amz-request-id: A4DDF21BB45BB05B
< Date: Thu, 26 Mar 2015 00:12:52 GMT
Date: Thu, 26 Mar 2015 00:12:52 GMT
< Last-Modified: Wed, 25 Mar 2015 23:39:49 GMT
Last-Modified: Wed, 25 Mar 2015 23:39:49 GMT
< ETag: "6259b6b6a732e590d9c20ced0a340638-3"
ETag: "6259b6b6a732e590d9c20ced0a340638-3"
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Content-Type: application/x-gzip
Content-Type: application/x-gzip
< Content-Length: 142245547
Content-Length: 142245547
< Server: AmazonS3
Server: AmazonS3

<
* Connection #0 to host s3-ap-southeast-2.amazonaws.com left intact

Full failure:
Recipe: java::oracle
  * java_ark[jdk] action install
    * remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] action create_if_missing

      ================================================================================
      Error executing action `create_if_missing` on resource 'remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz]'
      ================================================================================

      Chef::Exceptions::ChecksumMismatch
      ----------------------------------
      Checksum on resource (6f1f81) does not match checksum on content (460959)

      Cookbook Trace:
      ---------------
      /var/chef/cache/cookbooks/java/providers/ark.rb:137:in `block in class_from_file'

      Resource Declaration:
      ---------------------
      # In /var/chef/cache/cookbooks/java/providers/ark.rb

      128:       r = remote_file "#{Chef::Config[:file_cache_path]}/#{tarball_name}" do
      129:         source new_resource.url
      130:         checksum new_resource.checksum
      131:         retries new_resource.retries
      132:         retry_delay new_resource.retry_delay
      133:         mode 0755
      134:         action :nothing
      135:       end
      136:       #no converge by on run_action remote_file takes care of it.

      Compiled Resource:
      ------------------
      # Declared in /var/chef/cache/cookbooks/java/providers/ark.rb:128:in `block in class_from_file'

      remote_file("/var/chef/cache/jdk-7u75-linux-x64.tar.gz") do
        provider Chef::Provider::RemoteFile
        action [:nothing]
        retries 0
        retry_delay 2
        default_guard_interpreter :default
        path "/var/chef/cache/jdk-7u75-linux-x64.tar.gz"
        backup 5
        atomic_update true
        source ["https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz"]
        use_etag true
        use_last_modified true
        declared_type :remote_file
        cookbook_name "java"
        checksum "6f1f81030a34f7a9c987f8b68a24d139"
        mode 493
      end

    ================================================================================
    Error executing action `install` on resource 'java_ark[jdk]'
    ================================================================================

    Chef::Exceptions::ChecksumMismatch
    ----------------------------------
    remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] (/var/chef/cache/cookbooks/java/providers/ark.rb line 128) had an error: Chef::Exceptions::ChecksumMismatch: Checksum on resource (6f1f81) does not match checksum on content (460959)

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/java/providers/ark.rb:137:in `block in class_from_file'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/java/recipes/oracle.rb

     53: java_ark "jdk" do
     54:   url tarball_url
     55:   default node['java']['set_default']
     56:   checksum tarball_checksum
     57:   app_home java_home
     58:   bin_cmds bin_cmds
     59:   alternatives_priority node['java']['alternatives_priority']
     60:   retries node['java']['ark_retries']
     61:   retry_delay node['java']['ark_retry_delay']
     62:   connect_timeout node['java']['ark_timeout']
     63:   action :install
     64: end
     65:

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/java/recipes/oracle.rb:53:in `from_file'

    java_ark("jdk") do
      action [:install]
      supports {:report=>true, :exception=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      declared_type :java_ark
      cookbook_name "java"
      recipe_name "oracle"
      url "https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz"
      default true
      checksum "6f1f81030a34f7a9c987f8b68a24d139"
      app_home "/usr/lib/jvm/java"
      bin_cmds ["appletviewer", "apt", "ControlPanel", "extcheck", "idlj", "jar", "jarsigner", "java", "javac", "javadoc", "javafxpackager", "javah", "javap", "javaws", "jcmd", "jconsole", "jcontrol", "jdb", "jhat", "jinfo", "jmap", "jps", "jrunscript", "jsadebugd", "jstack", "jstat", "jstatd", "jvisualvm", "keytool", "native2ascii", "orbd", "pack200", "policytool", "rmic", "rmid", "rmiregistry", "schemagen", "serialver", "servertool", "tnameserv", "unpack200", "wsgen", "wsimport", "xjc"]
      alternatives_priority 1062
      connect_timeout 600
      owner "root"
    end

My workaround for now is to manually use curl to download the gz into /var/chef/cache/jdk-7u75-linux-x64.tar.gz:
[root@ip-172-21-1-4 tmp]# curl https://s3-ap-southeast-2.amazonaws.com/seek-simian-army/build/jdk-7u75-linux-x64.tar.gz -o /var/chef/cache/jdk-7u75-linux-x64.tar.gz
[root@ip-172-21-1-4 tmp]# ls -l /var/chef/cache/jdk-7u75-linux-x64.tar.gz
-rw-r--r-- 1 root root 142245547 Mar 26 00:15 /var/chef/cache/jdk-7u75-linux-x64.tar.gz

After that the recipe works:
Recipe: java::oracle
  * java_ark[jdk] action install
    * remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] action create_if_missing (up to date)
    - extract compressed data into Chef file cache path and
                        move extracted data to /usr/lib/jvm/jdk1.7.0_75
    - Symlink /usr/lib/jvm/jdk1.7.0_75 to /usr/lib/jvm/java
  * remote_file[/var/chef/cache/jdk-7u75-linux-x64.tar.gz] action nothing (skipped due to action :nothing)

Yesterday i stumbled into the same issue.
My workaround was to use sha256sum as checksum - amazon use this per default.
Have a look at your error:
Checksum on resource (6f1f81) does not match checksum on content (460959)

and the output from
sha256sum jdk-7u75-linux-x64.tar.gz
460959219b534dc23e34d77abc306e180b364069b9fc2b2265d964fa2c281610  jdk-7u75-linux-x64.tar.gz

I was wondering where this sum was coming from :) I'll try it out.

Thanks dzabel. The documentation says ['checksum'] can be either sha256 or checksum. I faced the same issue , however adding md5sum value to 'checksum'  attribute solved the issue.
I used md5sum  to generate the MD5 value.


Can't reproduce Figure 3e

Hi,
Thank you for developing this fantastic tool! I am trying to reproduce Figure 3e. I used the "parallel_inference.py" script from the /scripts/inference_motif_deletions folder to predict the motif effect after mutating all matching sites for GATA1 (motif #10 in the motif table). Using the code in /notebooks/figure3/Figure3.ipynb, I successfully reproduced the predictions for the reference sequences. However, my results for the mutated sequences differ from the example in the notebook. Do you have any suggestions for debugging this issue?
Thanks so much!

Hi!
Good catch, there was indeed a small mistake in the script that meant that the model never saw the alternative sequences. We fixed it now, let us know if it works for you!
Best,
Laura

Hi Lulu,
It should now be fixed, sorry for that. After our refactoring, we accidentally had incoherent settings for reference and motif deleted sequences. We also increased the cache_size argument which should lead to a significant speedup for the motif deletions.
Hope that helps!
Best,
Laura & Johannes