Unable to create .ovpn

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

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

Can not create .ovpn file
Have you searched for similar issues and solutions?
yes, unsuccessfully

Console output of      curl -L install.pivpn.io | bash
 root@raspberrypi:/# sudo curl -L https://install.pivpn.io | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0     33      0  0:00:05  0:00:05 --:--:--    37
100 58448  100 58448    0     0  10050      0  0:00:05  0:00:05 --:--:--  157k
:::
::: You are root.
::: Verifying free disk space...
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
::: Static IP already configured.
::: Using User: pi
:::
::: Checking for existing base files...
:::    Checking /etc/.pivpn is a repo...:::    Cloning https://github.com/pivpn/pivpn.git                                                                  into /etc/.pivpn... done!
:::
::: Stopping OpenVPN service... done.
:::
::: Installing scripts to /opt/pivpn... done.
::: Using protocol: udp
set_var EASYRSA_ALGO       ec
set_var EASYRSA_CURVE      prime256v1
::: Building CA...
read EC key
writing EC key

::: CA Complete.

Note: using Easy-RSA configuration from: ./vars

Using SSL: openssl OpenSSL 1.1.0k  28 May 2019
Generating an EC private key
writing new private key to '/etc/openvpn/easy-rsa/pki/private/raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key.pxR6XFLUA1'
-----
Using configuration from /etc/openvpn/easy-rsa/pki/safessl-easyrsa.cnf
Can't open /etc/openvpn/easy-rsa/pki/index.txt.attr for reading, No such file or director                                                                 y
1996156928:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bs                                                                 s_file.c:74:fopen('/etc/openvpn/easy-rsa/pki/index.txt.attr','r')
1996156928:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c                                                                 :81:
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
Certificate is to be certified until Aug 31 04:37:43 2029 GMT (3650 days)

Write out database with 1 new entries
Data Base Updated

Note: using Easy-RSA configuration from: ./vars

Using SSL: openssl OpenSSL 1.1.0k  28 May 2019
Using configuration from /etc/openvpn/easy-rsa/pki/safessl-easyrsa.cnf

An updated CRL has been created.
CRL file: /etc/openvpn/easy-rsa/pki/crl.pem

net.ipv4.ip_forward = 1
run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables save
run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables save
cp: cannot stat '/tmp/OLD_UFW': No such file or directory
sleep 0.1
::: Install Complete...
::: Restarting services...
Synchronizing state of openvpn.service with SysV service script with /lib/systemd/systemd                                                                 -sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable openvpn
::: Flushing writes to disk...
::: done.

Rebooting system...

Console output of      pivpn add or pivpn add nopass
root@raspberrypi:/opt/pivpn# pivpn -a
Enter a Name for the Client:  pixel
How many days should the certificate last?  2000
Enter the password for the client:
Enter the password again to verify:
/opt/pivpn/makeOVPN.sh: line 162:  1518 Segmentation fault      expect  <<EOF
    set timeout -1
    set env(EASYRSA_CERT_EXPIRE) "${DAYS}"
    spawn ./easyrsa build-client-full "${NAME}"
    expect "Enter PEM pass phrase" { send -- "${PASSWD}\r" }
    expect "Verifying - Enter PEM pass phrase" { send -- "${PASSWD}\r" }
    expect eof
EOF

[ERROR]: Client Public Key Certificate not found: pixel.crt

Console output of      pivpn debug
 pivpn -d
::: Generating Debug Output
::::            PiVPN debug              ::::
=============================================
::::            Latest commit            ::::
commit 510979ae90682c4ca11eb59d763c91930ffb5847
Author: cfcolaco<EMAIL_ADDRESS>Date:   Mon Sep 2 14:27:10 2019 +0200

    removing bitwarden installation from script
=============================================
::::        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 -> 1172
/etc/pivpn/INSTALL_PROTO -> udp
/etc/pivpn/INSTALL_USER -> pi
/etc/pivpn/NO_UFW -> 1
/etc/pivpn/pivpnINTERFACE -> wlan0
/etc/pivpn/TWO_POINT_FOUR ->
=============================================
::::    setupVars file shown below       ::::
INSTALL_USER=pi
UNATTUPG=unattended-upgrades
pivpnInterface=wlan0
IPv4dns=<IP_ADDRESS>
IPv4addr=<IP_ADDRESS>
IPv4gw=<IP_ADDRESS>
pivpnProto=udp
PORT=1172
ENCRYPT=256
APPLY_TWO_POINT_FOUR=true
DOWNLOAD_DH_PARAM=false
PUBLICDNS=REMOTE
OVPNDNS1=<IP_ADDRESS>
OVPNDNS2=
=============================================
::::  Server configuration shown below   ::::
dev tun
proto udp
port 1172
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.crt
key /etc/openvpn/easy-rsa/pki/private/raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key
dh none
topology subnet
server <IP_ADDRESS> <IP_ADDRESS>
# Set your primary domain name server address for clients
push "dhcp-option DNS <IP_ADDRESS>"
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-crypt /etc/openvpn/easy-rsa/pki/ta.key
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 1172
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 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
ecparams
extensions.temp
index.txt
index.txt.attr
index.txt.old
issued
openssl-easyrsa.cnf
private
renewed
revoked
safessl-easyrsa.cnf
serial
serial.old
ta.key

/etc/openvpn/easy-rsa/pki/ecparams:
prime256v1.pem

/etc/openvpn/easy-rsa/pki/issued:
raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.crt

/etc/openvpn/easy-rsa/pki/private:
ca.key
raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.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 1172/udp
=============================================
::::      Snippet of the server log      ::::
=============================================
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.txt
:::

Have you taken any steps towards solving your issue?
I had pivpn working before with no issues. This is a fresh reinstall which  can't generate .ovpn
I was able to execute './easyrsa build-client-full' successfully but my understanding is when this command is invoked by the pivpn -add script it fails.
I have uninstalled and reinstalled pivpn with all dependencies several times to no avail

Edit /opt/pivpn/makeOVPN.sh, add this line: set -x after INSTALL_HOME=${INSTALL_HOME%/} # remove possible trailing slash, then post the output of pivpn -a. This will enable "verbose" mode in Bash.

@orazioedoardo a bit off-topic ... what you think about what you think about adding some system information to pivpn debug .. for example /etc/os-release and uname -a ..
I think it might give us a bit more info about the system where it is running and possibly help track down this weird issues

Verbose makeOVPN:

root@raspberrypi:/opt/pivpn# ./makeOVPN.sh

'[' '!' -f /etc/pivpn/HELP_SHOWN ']'

test 0 -gt 0

'[' '!' -d /home/pi/ovpns ']'

[[ '' =~ 2 ]]

'[' -z '' ']'

printf 'Enter a Name for the Client:  '
Enter a Name for the Client:  + read -r NAME
XXXXXXXX

[[ p == . ]]

[[ p == - ]]

[[ pics =~ [^a-zA-Z0-9.@_-] ]]

[[ -z pics ]]

read -r line
++ echo 'V<PHONE_NUMBER>43Z           E3AF40EFBC749DF8ADB39A16418C52E8        unknown /CN=raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
++ awk '{print $1}'

STATUS=V

'[' V == V ']'
++ echo 'V<PHONE_NUMBER>43Z           E3AF40EFBC749DF8ADB39A16418C52E8        unknown /CN=raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
++ sed -e 's:.*/CN=::'

CERT=raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

'[' raspberrypi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx == pics ']'

read -r line

'[' -n '' ']'

'[' '' == 1 ']'

'[' pics == ta ']'

'[' pics == server ']'

'[' pics == ca ']'

'[' -z '' ']'

read -r -e -p 'How many days should the certificate last?  ' -i 1080 DAYS
How many days should the certificate last?  1080

[[ ! 1080 =~ ^[0-9]+$ ]]

'[' 1080 -lt 1 ']'

'[' 1080 -gt 3650 ']'

cd /etc/openvpn/easy-rsa

[[ '' =~ 1 ]]

keyPASS

[[ -z '' ]]

stty -echo

true

printf 'Enter the password for the client:  '
Enter the password for the client:  + read -r PASSWD

printf '\n'

printf 'Enter the password again to verify:  '
Enter the password again to verify:  + read -r PASSWD2

printf '\n'

'[' xxxxxxx = xxxxxxx']'

break

stty echo

[[ -z xxxxxxxx ]]

'[' 7 -lt 4 ']'

'[' 7 -gt 1024 ']'
++ echo -n xxxxxxx
++ sed -e 's/\/\\/g' -e 's///\//g' -e 's/$/\$/g' -e 's/!/\!/g' -e 's/./\./g' -e 's/'''/\'''/g' -e 's/"/\"/g' -e 's/*/\*/g' -e 's/@/\@/g' -e 's/#/\#/g' -e 's/£/\£/g' -e 's/%/\%/g' -e 's/^/\^/g' -e 's/&/\&/g' -e 's/(/\(/g' -e 's/)/\)/g' -e 's/-/\-/g' -e 's//\/g' -e 's/+/\+/g' -e 's/=/\=/g' -e 's/[/\[/g' -e 's/]/\]/g' -e 's/;/\;/g' -e 's/:/\:/g' -e 's/|/\|/g' -e 's/</\</g' -e 's/>/\>/g' -e 's/,/\,/g' -e 's/?/\?/g' -e 's/~/\~/g' -e 's/{/\{/g' -e 's/}/\}/g'

PASSWD=xxxxxxxx

expect
./makeOVPN.sh: line 163:  3536 Segmentation fault      expect  <<EOF
set timeout -1
set env(EASYRSA_CERT_EXPIRE) "${DAYS}"
spawn ./easyrsa build-client-full "${NAME}"
expect "Enter PEM pass phrase" { send -- "${PASSWD}\r" }
expect "Verifying - Enter PEM pass phrase" { send -- "${PASSWD}\r" }
expect eof
EOF

cd pki

'[' '!' -f issued/pics.crt ']'

echo '[ERROR]: Client Public Key Certificate not found: pics.crt'
[ERROR]: Client Public Key Certificate not found: pics.crt

exit

uname -a
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

What if you replace this: https://github.com/pivpn/pivpn/blob/d0c10db6ec391961b7201fb564055c1176ca73e3/scripts/makeOVPN.sh#L196-L203
With this:
EASYRSA_CERT_EXPIRE=1080 ./easyrsa build-client-full
Do you still get segmentation fault?
@4s3ti agree, we could add $OSCN and $PLAT. Actually i was thinking of simplifying the script. See, we have both individual files in /etc/pivpn containing setting as long as setupvars.conf. I think we could merge everything into setupvars.conf and just source the file when we need vars in other scripts like makeovpn.sh. This could also be coupled with an option to compress the /etc/openvpn folder to backup the config. Restoring would be something like pivpn restore vars.conf backup.tar.gz.
However i need to understand what’s the role of the “Update” option, that relies on setupvars.conf: basically it redownloads all scripts from github and perform an unattended install sourcing most vars from setupvars.conf. Then it proceeds rebuilding the server (new certificates, keys) so it doesn’t really seem an update to me.

@orazioedoardo agree  there is plenty of room for simplifying the script is getting quite big xD
about the update .. considering pivpn structure and what it does .. to update pivpn it would be more an update of /opt/pivpn  other than anything else .. as all other stuff is updated via apt ...

Sorry guys, I couldn't wait for a solution as I needed a working VPN.
Formatted the card and reinstalled everything anew. Now it works

@Drzet well i actually asked you to test this EASYRSA_CERT_EXPIRE=1080 ./easyrsa build-client-full. By the I'm speculating that a segmentation fault on expect could be caused by sd card corruption. You might want to check from time to time dmesg | grep ext4 for file system errors, in case this happens again.

Thank you, will do.


video overlay implementation

Greetings. Please consider implementation of video overlays such as on top of pre-rendered frames to allow for animations like those in Myst/Riven.

Hi. Could you please provide an example of what you mean, and clarify how you think it should tie in with the Escoria framework, so that I might have a better understanding of what you're asking for.

Good idea. I'm keeping this for Escoria rewrite. However it will probably not be done very soon.
Could you please provide a sample video I can use for implementing this feature? Thanks in advance.

After a rewrite from scratch, Escoria will be re-released in the coming weeks. Because of this, we're closing this issue, because it relates to the old code. If the issue also regards the rewritten code, please feel free to reopen it.
Thanks

Sorry for the late reply. I've since used a different framework for my project. To best describe the scenario: A static image or backdrop, but a portion of it overlayed with video for fluid animation, such as a door opening, switch toggling, water flowing, etc.

Thanks for the reply, @JstCruzn86. This is already possible in different ways in Godot Core:

Using an AnimatedSprite and playing its animation
Using a Sprite or TextureRect with an AnimatedTexture
Using a Sprite or TextureRect together with AnimationPlayer2D to control the animation

You can even put it in a CanvasLayer with a higher layer to make it appear in front of the characters.


Schnorr signature with specific nonce?

I am working on a dlc oracle project and to do so I need to create a signature with a specific nonce / k value. However, the only functions that are exposed are ones that use random data to compute the signature's nonce.
We had this functionality in the past for bitcoin-s, has the been removed or not ported to rust?

You can do this by using the FFI functions from secp256k1-sys directly. I don't think we've ever exposed this functionality directly.
If you were willing to PR to rust-secp adding an interface to provide a custom nonce function for schnorr signatures, I'd be happy to accept that.
Schnorr signatures are also part of rust-secp256k1, not rust-secp256k1-zkp. Though possibly many years ago this was different.


Finished loading results but never shows them

EDIT: This is in an Intel Mac running OSX 11.6
Freshly downloaded Visual Studio Code Insider today, followed instructions, ran extension, opened project in extension window, confirmed inline suggestions are enabled, attempted several search strings in a blank document and the suggestions never appear.  The status bar shows them loading and then shows captainstack finished loading xx results, but I never see the suggestions appear.  Someone else had this issue here but it was closed with no notes; how do I fix this?
https://github.com/hieunc229/copilot-clone/issues/53

I followed the suggested video tutorial in Discord here https://www.youtube.com/watch?v=crcpfLjNOgE on a fresh Windows 10 v21H2 computer and got the exact same results.  CaptainStack: Finished loading XX results but nothing ever shows up as suggestions.  Confirmed the inline suggestion setting is checked as well as tried the process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; workaround in src/utils/fetchPageContent.ts on line 2, I never see any error notifications when I try to search, not sure how to proceed.
I can provide any further troubleshooting information needed.  I've attached a more detailed screenshot showing both windows running on the mac

The code structure so you can see I've got the root folder correct.  Trying to think of what else might be helpful to post, let me know if I can retrieve any info or logs or run commands to extract data for this.  Thank you!

I forgot to mention the initial issue was seen on an Intel Mac running OSX 11.6, but it appears on a fresh Windows installation as well.  I've ensured I had all the prerequisites installed and working on both machines, such as npm, npx, git, etc... I made sure to install any dependencies that npm said were missing when I ran npm install, if any showed up.

I have tested this myself, it is definitely not working. It compiles to my surprise, but it does not do anything except say that the results loaded.
From testing I think that the problem lies in the usage of the new update of vs code insiders. They most likely changed something the postinstall script needs. @hieunc229 that was your part and it would be nice if you could check it out.

it should still work fine on older versions of vs code is my guess.

aha, that's a good thought!  I'll look into how to get my hands on an older vs code insider.  Or will this work on plain vs code of a certain version?  That will work just fine for me for the moment, I don't need the latest for any other reason :)

It will not work on the stable branch of vscode since the inlineCompletions feature is part of the proposed API of the insider versions.

This bug was caused by the recent changes from the VSCode official API. I made an update that should fix this issue.
Feel free to reopen or open a new thread for further discussion


case reader clean up tasks

In fact this involves changes in core and parametric packages

update the case file path argument in parametric's CaseReader usage (remove h5 prefix)
remove import of parametric's CaseReader in except block
remove parametric's CaseReader
bump the core and parametric versions

Can lispy.py also be removed from parametric? It does not have any other usages, locally - not sure if has linked usage, that's why checking. If that's the case then the entire filereader.py can be removed along with the 2 related tests.

@prmukherj yes lispy.py can also be removed from parametric


How to kill an activity by pressing any button in React-Native using Router-Flux????

For Example:->
Flow Direction
Splash -> Home
I want ,when the backbutton pressed is not going to home -> spalsh but its should closed the app
and i already use  Actions.onExit(); but its not working.
please resolve these issue

Use the BackButton listener or just a listener, there's already closed issues about it, have a look please.

Hi Blapi
Thanks for your reply It is working for android.But in ios there are no back button ,there are some issue with sliding view.
so can i resolved it?

I don't understand your point here..
Now you're talking about exiting your app when you're on your Home page and on iOS right ? I'm not sure about the iOS experience here, but why would you kill the app if this is on iOS? What does your Home page look like ?
And what's the issue with sliding view you're talking about ?


Can not query apps installed by trollstore.

Can not query apps installed by trollstore.

I was going to report this issue too

I’ve spoken to the dev of trollstore about it. It’s an issue that extends to jitstreamer and Xcode itself. Trollstore installed apps cannot be debugged. Need to find out why.

I just installed JITstreamer and I can now run Flycast installed with TrollStore ☺

It seems apps can enable jit by themselves. Such as PojavLauncher
https://github.com/PojavLauncherTeam/PojavLauncher_iOS

For iOS 14.0-15.5beta4 on compatible devices, TrollStore is recommended to keep PojavLauncher permanently signed and have JIT automatically enabled.

Fixed in https://github.com/osy/Jitterbug/commit/e110cc8afe87c1094c490b91cc47312f7f4da138


Set minimum OSX deployment version

I'm using this script for my MacOS project.
My target's deployment is set to 10.14 and currently I'm having hundreds of warnings -
object file (/Users/username/Developer/Project/OpenSSL/lib/libcrypto.a(aes_cbc.o)) was built for newer macOS version (11.0) than being linked (10.14)
I understand the following flag needs to be set in the script somewhere but I'm unsure where..
-mmacosx-version-min=
edit:
I've tried updating every line in openssl-build-phase1.sh with the line CFLAGS=" -O2 -mmacosx-version-min to set this to my minimum deployment version, but this doesn't seem to work.

Hi Joey, thanks for raising this. I suspect there are some Apple Silicon updates that are forcing a 11.0 build.  I'll take a look.  In the meantime, you should be able to pull the previous build script here:
https://github.com/jasonacox/Build-OpenSSL-cURL/releases/tag/v7.72.0
I would be interested to know if that version works for you.

Hi Joey, thanks for raising this. I suspect there are some Apple Silicon updates that are forcing a 11.0 build.  I'll take a look.  In the meantime, you should be able to pull the previous build script here:
https://github.com/jasonacox/Build-OpenSSL-cURL/releases/tag/v7.72.0
I would be interested to know if that version works for you.

Thanks for jumping on this so quick @jasonacox !
I tried your suggestion and attempted a build from that previous release, but unfortunately it didn't work for me.
Please let me know if there's anything else I can try.
My machine is an Intel i7 running Big Sur

Thanks for jumping on this so quick @jasonacox !
I tried your suggestion and attempted a build from that previous release, but unfortunately it didn't work for me.
Please let me know if there's anything else I can try.
My machine is an Intel i7 running Big Sur

That's correct.  Big Sur is going to build 11.x images.  For MacOS images, the build is set to use the default build.
One suggestion - we could edit the buildMac() section to target a 10.14 macos image.  In the openssl-build-phase1.sh file, find this section and see the added CFLAG for x86_64 builds on a x86_64 host:
buildMac()
{
	ARCH=$1

	echo -e "${subbold}Building ${OPENSSL_VERSION} for ${archbold}${ARCH}${dim}"

	TARGET="darwin-i386-cc"
	BUILD_MACHINE=`uname -m`

	if [[ $ARCH == "x86_64" ]]; then
		if [ ${BUILD_MACHINE} == 'arm64' ]; then
   			# Apple ARM Silicon Build Machine Detected - cross compile
			TARGET="darwin64-x86_64-cc"
			export CC="clang"
			export CXX="clang"
			export CFLAGS=" -O2 -mmacosx-version-min=11.0 -arch x86_64 "
			export LDFLAGS=" -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk "
			export CPPFLAGS=" -I.. -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk "
			# ./Configure shared enable-rc5 zlib darwin64-arm64-cc
		else
			# Apple x86_64 Build Machine Detected
			TARGET="darwin64-x86_64-cc"
			#
			# SET target platform version
			#
			export CFLAGS=" -O2 -mmacosx-version-min=10.14 -arch x86_64 "
		fi
	fi

I'm able to get it to build doing that but would love to see if this works with your project.  If so, I'll leave a comment in there for other to use or add a flag to let people set target versions less than the build host.

That's correct.  Big Sur is going to build 11.x images.  For MacOS images, the build is set to use the default build.
One suggestion - we could edit the buildMac() section to target a 10.14 macos image.  In the openssl-build-phase1.sh file, find this section and see the added CFLAG for x86_64 builds on a x86_64 host:
buildMac()
{
	ARCH=$1

	echo -e "${subbold}Building ${OPENSSL_VERSION} for ${archbold}${ARCH}${dim}"

	TARGET="darwin-i386-cc"
	BUILD_MACHINE=`uname -m`

	if [[ $ARCH == "x86_64" ]]; then
		if [ ${BUILD_MACHINE} == 'arm64' ]; then
   			# Apple ARM Silicon Build Machine Detected - cross compile
			TARGET="darwin64-x86_64-cc"
			export CC="clang"
			export CXX="clang"
			export CFLAGS=" -O2 -mmacosx-version-min=11.0 -arch x86_64 "
			export LDFLAGS=" -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk "
			export CPPFLAGS=" -I.. -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk "
			# ./Configure shared enable-rc5 zlib darwin64-arm64-cc
		else
			# Apple x86_64 Build Machine Detected
			TARGET="darwin64-x86_64-cc"
			#
			# SET target platform version
			#
			export CFLAGS=" -O2 -mmacosx-version-min=10.14 -arch x86_64 "
		fi
	fi

I'm able to get it to build doing that but would love to see if this works with your project.  If so, I'll leave a comment in there for other to use or add a flag to let people set target versions less than the build host.

Yess that worked.  All the warnings are gone.  Thank you very much! 🙏

If so, I'll leave a comment in there for other to use or add a flag to let people set target versions less than the build host.

Yes - I think this is a very good idea.  Especially for people like me that aren't very good with scripts 😅

Yess that worked.  All the warnings are gone.  Thank you very much! 🙏

If so, I'll leave a comment in there for other to use or add a flag to let people set target versions less than the build host.

Yes - I think this is a very good idea.  Especially for people like me that aren't very good with scripts 😅


WIP: Openstack4j

@mavlyutov, I started experimenting with openstack4j basing the effort on jclouds 1.9 effort to take advantage of singlemodule project.
Marat, I would like you to look at following thing: There do not seem to be a way to list configured regions using openstack4j. What does it do actually? Can you point it to correct region using different keystone api url? For now, I have removed that completely but it will be possible to add it back (without the available region completion).

Hi!
I looked at o4j about year ago and it was pretty green. Let's see what's for now.
Let me a few days to try it. But I like the main idea - to get rid of monstrous jclouds and use smth neat and singlemodule.
As for regions - we have really big openstack system with http-balancer atop of keystone. And our devops team kindly asks using that balancer instead of direct region-based keystone urls. So yes, we need it, with listing or without it.

@mavlyutov, thanks. Can you have a look on ee38148 and 6b579b1, the feature seems to be removed some time ago.

Btw, are there any users of blobstore?

Btw, are there any users of blobstore?
not me

github says "This branch is up-to-date with the base branch", but jenkins build fails with error of automatic merging. Why is that?

@pupssman, this PR contains the refactorization from miltimodule to singlemodule maven project that does not merge cleanly back to master. To merge this PR I will use "our merge" (throw away all the changes on the master and pretend it is merged) that would require to go through all recent changes on master and cherry-pick it here so it will merge cleanly as safely (IOW, it should be me who is responsible to make sure this is mergeble, not the maintainer). The build fails because of one conflicting file as my master was outdated when I oursmerged.
Fixed: https://jenkins.ci.cloudbees.com/job/plugins/job/openstack-cloud-plugin/87/console

Oh, nice! Keep up the good job)

There seems to be a limitation of openstack4j as it is not able to set ssh/pwd credentials (jclouds executes scripts over ssh to get the job done). Running ATH against 1.8 it seems, it never actually created user accounts but perhaps it is able to populate those accounts with credentials.
As users usually want both, the logic has to be separated between cloud-init creating the account and a plugin populating it with credentials. I understand this is a breaking change for some deployments, but how about making all this a responsibility of cloud-init (openstack populates default account with key identified by key-name)? We do not have to rely on fragile shell scripts messing with the system and it will help us getting closer to windows support. WDYT?

I have deployed this to production and it seems to be working fine. I will go through the commits that landed in master since this branch was forked and cherry-pick them here.
As this is quite complex change, I would like to release this as 2.0(-beta).

Finally, 2.0 beta is out (should be in experimental update center in a minute): http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/openstack-cloud/2.0-beta/
@mavlyutov, @pupssman, can you give it a try?

Thanks for your work on this @olivergondza it works nicely. Would be awesome to see support for V3 keystone with domains.


Why TestStringifiedDAGs works?

So, this class tests serialisation and deserialisation of DAGs. But... the test DAGs include:
https://github.com/apache/airflow/blob/b2e06d0edcdbcfbe65e5135554bd45b3e2d76cd0/tests/dags/test_dag_serialization.py#L65-L84
As you know, those DAGs has been moved to core and renamed. I dunno why this is not failing on CI. There is a subprocess which I think may be killed by test timeout (?) and in case of nose the test will success:
root@6ac5c8d515b1:/opt/airflow# nosetests tests/dags
/usr/local/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
  """)
/opt/airflow/airflow/contrib/operators/qubole_operator.py:172: PendingDeprecationWarning: Invalid arguments were passed to QuboleOperator (task_id: hive_s3_location). Support for passing such arguments will be dropped in Airflow 2.0. Invalid arguments were:
*args: ()
**kwargs: {'notfiy': True}
  super().__init__(*args, **filtered_base_kwargs)
/opt/airflow/airflow/contrib/operators/qubole_operator.py:172: PendingDeprecationWarning: Invalid arguments were passed to QuboleOperator (task_id: db_import). Support for passing such arguments will be dropped in Airflow 2.0. Invalid arguments were:
*args: ()
**kwargs: {'db_parallelism': 2}
  super().__init__(*args, **filtered_base_kwargs)
Process Process-1:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/local/lib/python3.6/multiprocessing/process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/airflow/tests/dags/test_dag_serialization.py", line 210, in serialize_subprocess
    dags = collect_dags()
  File "/opt/airflow/tests/dags/test_dag_serialization.py", line 204, in collect_dags
    dags.update(make_example_dags(contrib_example_dags, CONTRIB_EXAMPLE_DAGS))
  File "/opt/airflow/tests/dags/test_dag_serialization.py", line 156, in make_example_dags
    return {k: dagbag.dags[k] for k in dag_ids}
  File "/opt/airflow/tests/dags/test_dag_serialization.py", line 156, in <dictcomp>
    return {k: dagbag.dags[k] for k in dag_ids}
KeyError: 'example_gcp_bigtable_operators'
^C
----------------------------------------------------------------------
Ran 1 test in 9.148s

OK

Any ideas @mik-laj @potiuk ?

Seems to be solved:
https://apache-airflow.slack.com/archives/CLV191AKH/p1569514621011300


Empty Bookmarks View Controller Needs Some Sort of Message

Expected behavior
If you don't have any bookmarks set, then there should be a "No Bookmarks" message that appears inline on the view controller.
Actual behavior
It's just blank and looks broken.
Steps to reproduce the behavior
Launch a simulator that doesn't have any bookmarks and tap the bookmarks tab.
Screenshot of the issue (if applicable)

App Version/Hardware
current builds of 2.5.0

https://github.com/dzenbot/DZNEmptyDataSet ?

Here's what it ended up looking like:


GEODE-4126: Remove *geode.test.golden

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[n/a] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

As best as I can tell, this package represents a testing framework and parser tester that has long since been antiquated by JUnit integration into our build.  Moveover, this package represents much of the tight coupling that blocks / makes very difficult any progress on GEODE-5803.

I always forget to check the examples!
Well, this might be the fastest I've ever opened, gotten feedback, and closed a ticket.
My main concern is that having one module's test source set depend on other module's active test source set is a serious anti-pattern in gradle.  Moving this to geode-junit:main would be the other solution.


Create a matplotlib projection for stereogram plots

Stereogram plots, often used in geology and structural geology, help visualize 3D orientation data (e.g., planes, lines, or stress directions) on a 2D plane. Creating a custom Matplotlib projection for stereogram plots allows accurate representation of angular data, which we need to represent directions. Tutorial available here.

Task List

Switch to Matplotlib Projection

[ ] Implement a projection in Matplotlib to facilitate grid drawing, setting ticks, etc. Refer to the Matplotlib Projections API for guidance.

Add Matplotlib as a Dependency

[ ] Add Matplotlib as a runtime dependency in pyproject.toml.
[ ] Determine the minimum required version, choosing a minor release from at least two years ago.
[ ] Consult the Matplotlib changelog to confirm an appropriate version.

Set Up Testing with pytest-mpl

[ ] Add pytest-mpl to the environment.yml file.
[ ] Also add pytest-mpl to env/requirements-test.txt.


Make linter for stable sorting

Background
We should make a simple linter to just check for instances of sort.Slice, and replacing it with sort.SliceStable, and sort.Sort -> sort.Stable.
(The application of this change is breaking)
Unstable sort behavior can (validly) change between golang minor releases, so should never be relied upon. Pretty basic issue to get eliminated from our concern list. cref #3762
Ideally this could be in our golangci-linter. If thats hard for whatever reason we can add a custom golang linting step.
Suggested Design
Some basic regex to handle these.
Acceptance Criteria
We have a linter warning for any unstable sort usage.

@ValarDragon - I can pick this up

Couldn't find a convenient linter for golang that bans certain regex expressions. So to do this, I think we should:

[ ] Find the list of golang sorts that are not stable from https://pkg.go.dev/sort
[ ] Make a grep or simple CLI command that will return any usage of these, across all go files in the repo
[ ] Require as a step in make lint running this command, ensuring there are 0 such usages.
[ ] Check in CI that this is failing in our repo, and fix the failures.

Can I pick this up ?

@ValarDragon I think we need AST for this as grep Slice and Sort will not be sufficient. What do you think ?


Update/arctasks

Get base site running with arctasks.

I've gotta go to class but I'll work more on this today if I get a chance.

Would it be possible to squash this into just one or two commits? It seems to me that there's one commit for fixing the convert script and there's another for switching to arctasks.

I was planning on rebasing them all into one or two commits once I get the tests to pass.

See d7844e57c803ff7bb012243851d550d2ae74e16a to 347c31f27c720f24b13e05e0652301ad240aed12


Moving all POMs off snapshot versions

The snapshot versions should not be configured into the POMs. This is
causing problems for new builds

Thanks for fixing this.


add option for seperate log file "suffix" location type to replace original image extension

currently if i download an image with .txt suffix, the txt file will be saved as etcetc.jpg.txt, but i want it to save as just .txt.

Makes sense, although note that they would overlap if you download files with the same path but a different extension 👍

yes, particularly ive realized the %num% option (when used for filenames atleast) can give the same number to an image with a different extensions. so you can have 2.jpg and 2.png end up in the same folder and its very annoying, it would be much more useful if it just game a unique number to every image regardless of extension.


Create Remove-TeamsApp.md

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: joeyglocke sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Docs Build status updates of commit cb3df8b:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit cb3df8b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Remove-TeamsApp.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Adding Linux Support

Dear all, It might be worth adding out-of-the-box Linux support.
This should not be too difficult to implement, given that mac support is present

It has a docker-compose so it seems to be linux first? https://github.com/KruxAI/ragbuilder/blob/main/docker-compose.yml

Docker image support both x86 (AMD64) and ARM64 architectures hence it should work in linux. Let us know if you face any issues

@AlessandroZavoli - did you get a chance to check this?


Updated whitesource configuration

Problem Statement

Problem statement

This repository needs to be scanned for license compliance
Design

For Bug, Describe the fix here.
For Feature, Post the link for design

Details are described in this JIRA Ticket -> https://jts.seagate.com/browse/CORTX-28935
Coding
Checklist for Author

[X] Coding conventions are followed and code is consistent

Testing
Checklist for Author

[X] Unit and System Tests are added
[X] Test Cases cover Happy Path, Non-Happy Path and Scalability - Not applicable
[X] Testing was performed with RPM - Not applicable

Changes are made after discussion with whitesource support team.
Scan will be executed as part of PR process
Impact Analysis
Checklist for Author/Reviewer/GateKeeper

[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)

Review Checklist
Checklist for Author

[X] JIRA number/GitHub Issue added to PR
[X] PR is self reviewed
[X] Jira and state/status is updated and JIRA is updated with PR link
[X] Check if the description is clear and explained

https://jts.seagate.com/browse/CORTX-28935
Documentation
Checklist for Author

[ ] Changes done to WIKI / Confluence page / Quick Start Guide

Not applicable.

Closing as an obsolete


Update 1.0-1.1-api-diff_System.Runtime.CompilerServices.md to show ref returns

Fix unsafe API changes that return a ref.

@terrajobst , PTAL

@terrajobst , can you take a look?

@terrajobst , does this diff look correct?

@Petermarcu you can see this for yourself at:
https://github.com/dotnet/corefx/blob/master/src/System.Runtime.CompilerServices.Unsafe/src/System.Runtime.CompilerServices.Unsafe.il#L242
https://github.com/dotnet/corefx/blob/master/src/System.Runtime.CompilerServices.Unsafe/src/System.Runtime.CompilerServices.Unsafe.il#L234
https://github.com/dotnet/corefx/blob/master/src/System.Runtime.CompilerServices.Unsafe/src/System.Runtime.CompilerServices.Unsafe.il#L277
Return is "!!T&", I assume this might be due to a tool, generating these diffs, that does not support ref returns.

The diff looks correct, although we need to fix our tools /cc @weshaggard. Otherwise, the next time we run an export ref returns will disappear again.

Agreed. I filed https://github.com/dotnet/buildtools/issues/1376 to track getting the tools to understand ref returns (PR's welcome :)).

PR's welcome :)

Review welcome ;-)
https://github.com/dotnet/buildtools/pull/1377


fix build gates failing with pytorch errors due to old torchvision install and pin matplotlib

Description
The build gates started failing recently with the error:
/usr/share/miniconda/envs/test/lib/python3.7/site-packages/torchvision/models/inception.py:195: in Inception3
    @torch.jit.unused
E   AttributeError: module 'torch.jit' has no attribute 'unused'

This is due to an old version of torchvision getting installed and may be related to the recent pytorch 2.0.0 release.
This PR fixes the issue by using the "strict-channel-priority" flag in conda install to ensure we are installing torchvision package from the pytorch channel.
Update: after the fix above, a new version of matplotlib was getting installed, but captum would fail as it still does not support latest matplotlib.  Please see issue:
https://github.com/pytorch/captum/issues/1114
Also, the typehint in the code started failing when I did upgrade to latest matplotlib, so I am also pre-emptively adding an import fix for the typehint when captum does start supporting the latest matplotlib in the future.
Another update: I've also rotated the carton image because sometimes the fasterrcnn model with pretrained weights would fail to find objects on some OSs (I think it might be a flaky/inconsistent issue?).
Checklist

[ ] I have added tests for all changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #22 (b0c2734) into main (13d73f0) will increase coverage by 0.10%.
The diff coverage is 100.00%.

:exclamation: Current head b0c2734 differs from pull request most recent head 7fcce34. Consider uploading reports for the commit 7fcce34 to get more accurate results

@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
+ Coverage   93.28%   93.38%   +0.10%
==========================================
  Files           6        6
  Lines         253      257       +4
==========================================
+ Hits          236      240       +4
  Misses         17       17

Flag
Coverage Δ

unittests
93.38% <100.00%> (+0.10%)
:arrow_up:

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

Impacted Files
Coverage Δ

python/vision_explanation_methods/DRISE_runner.py
92.23% <100.00%> (+0.31%)
:arrow_up:

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

Thanks for fixing this! I had noticed an error with matplotlib and the Axis attribute but I wasn't sure the best way to pin the dependencies. Looks great!!


bump »Spring Boot« to 2.2.1 (w/ »Spring Framework« 5.2.1)

Please ensure all items are complete before opening.

[x] Tick to sign-off your agreement to the IBM Contributor License Agreement
[x] You have updated the CHANGES.md

Thanks for that.


Check and fix grub for net.ifnames=0

By submitting pull requests to this repo, I agree to the Contributor License Agreement which can be found at: https://github.com/cpanel/elevate/blob/main/docs/cPanel-CLA.pdf

We shouldn't be doing this unless the new kernel has this option on it.


allow prefix and suffix to be passed in

https://github.com/99xt/serverless-dynamodb-local/issues/42

Thanks @gwincr11


the script can't find: "gnome-software-packagekit-plugin"

Describe the bug
installation fails because the installer cannot find gnome-software-packagekit-plugin
To Reproduce
Steps to reproduce the behavior:

Run the desktop.sh script per the instructions in the readme
"Proceed with the installation"
Error occurs during installation

The error:
error: target not found: gnome-software-packagekit-plugin
ERROR: Failed to install packages to new root
Additional context
I checked the Arch Repositories and there is no package in the repos named "gnome-software-packagekit-plugin"
I do see that there is an AUR package called "gnome-software-packagekit-plugin.git"

Update 2:
Removing gnome-software-packagekit-plugin from line 216 (the pacstrap step) resolves this problem. But I believe this means gnome-software will have no integration with packagekit

I will remove gnome-software


Fix uploaded file mime content type verification in the sw-media-upload-v2 administration component

Fix uploaded file mime content type verification in the sw-media-upload-v2 administration component

1. Why is this change necessary?
The uploaded content type is checked with a forEach in the accepted types. But the foreach never break so eventually only the last accepted format is verified. So it is impossible to attach a pdf file with the template editor because the last accepted mime type tested is image/*.
There is a second problem. Accepted formats are retrieved with a split on a string that contains a comma-separated list. But this does not take into account the spaces after the commas that must be trimmed.
2. What does this change do, exactly?
This change replace the forEach by the some method, so as soon as a content type matches an accepted format the check stops. The accepted formats recovered with a split are trimmed.
3. Describe each step to reproduce the issue or behaviour.
Try to upload a pdf file attachment with the administration email template editor.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Duplicate of #2713.
@dimiceli I will adopt your solution regarding the whitespace after the comma in my pull request.

Thanks @fk-bitsandlikes for the hint to your PR :+1:
@dimiceli can you confirm that your problems will also be solved by https://github.com/shopware/platform/pull/2713? Then we should close this PR in favor of https://github.com/shopware/platform/pull/2713

Hello thank you @fk-bitsandlikes @keulinho yes the PR #2713 seems to fix my problem.

Thanks for your verification @dimiceli, so i'm closing this PR for now and we will proceed with https://github.com/shopware/platform/pull/2713.
If after that one is merged there are still some missing points or issues feel free to open up a new PR.


登陆页面卡死！

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[ ] Read the docs.
[ ] Make sure the code is up to date. (Some bugs have been fixed in the latest code)
[x] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
A clear and concise description of what the bug is..
Reproduction
Please describe the steps of the problem in detail to ensure that we can restore the correct problem
System Info

Operating System:
Node version:
Package manager (npm/yarn/pnpm) and version:

我也遇到了，新拉的代码有问题

同样也登录卡死

我也遇到

不知道啥时候能解决

@xachary #3592 提交的问题


WIP: Xcode updates + Persian C style loop fix.

Mostly automatic updates from Xcode.

@bugKrusha looks good to me. I had to make a bunch of changes to fix some stuff that went awry with the upstream changes and this. That's all been done here, if you want to look them over and then merge the PR when you're done (or let me know if there's any changes you want me to make).

@aranasaurus looks good to me so ima merge. Thanks for taking care of this 🙌


Happy new year 2016

OMG! That was super outdated!
Thanks @samsonasik ;-)

OMG! That was super outdated!
Thanks @samsonasik ;-)

@acelaya yes ;), you're welcome ;)

@acelaya yes ;), you're welcome ;)


Godot was supposed to have no jokes

Godot version
All versions
System information
All systems
Issue description
When I found out that my printer can't throw ERR_PRINTER_ON_FIRE I was going to report it, however, I was told that the error message is just a joke. But in this twitter thread, lead developer Reduz said that no jokes is best, so I don't think it's intentional.
Steps to reproduce

Set a printer on fire
Try to access the printer and notice that ERR_PRINTER_ON_FIRE is not thrown.

/parody
Minimal reproduction project
the steps are trivial
(sorry if this is disrespectful, I just thought we could celebrate this milestone with a small laugh!)

you waited for this

It's 1:30 AM. Worth it

i was about to make a issue lol, i got #69421

Joke requests should be made in the Godot Probrosals repository. Specifically, you should open a discussion in the proposals rejokitory.
This space is for bug regerts only.

you should open a discussion

Wouldn't it be a discursion?

To cite LICENSE.txt:

https://github.com/godotengine/godot/blob/fe52458154c64fb1b741df4f7bd10106395f7cbd/LICENSE.txt#L14-20

Henceforth, you cannot sue Godot Foundation, neither W4Games or the authors for damages to your printer.

I would support removing the error code. I'm not against easter eggs, but when there is a note "(This is an easter egg, no engine methods return this error code.)", then 1. it's not so funny anymore; 2. the question arises whether this joke is appropriate if it needs to be explained. "This APT has Super Cow Powers", without "(This is just a joke, there is no super power in APT actually.)".

This error should be displayed when you print too much

Definitely agree, this note should be removed while keeping only the "printer on fire" part. Even if people were to take this seriously, it would do no harm.

I want a PR for that issue to be resolved!

Can someone please resolve this issue?
I rely on Godot telling me the status of my printers at my print farm (corporate contract to print this immage over 80085 times) and if one of my printers chatches fire and I wouldn't be notified in time, it would be a huge problem.

Here's a branch that implements one possible fix to this issue https://github.com/aaronfranke/godot/tree/printer-on-fire

dammit tried to reproduce and my house burnt down


Prevent minification on a JSON definition

Hello all, can't seem to wrap my head around this one.
Let's assume I can only launch my compiled program (with advanced optimizations) if I pass a configuration in JSON:
{
    module_foo: {
        smth: 54,
        othr: 'hello'
    },
    bar: true
}

So when launching, I'll get something like that:
function init(json) {
    var foo = json.module_foo;
    var bar = json.bar;
    ...
}

The problem is at compilation, I will obtain something like :
function a(a){var b=a.c,d=a.d;}

Is there a way to prevent the minification of these properties name, without using the classic ["prop"] notation, as I still want typechecking ? I tried specifying my entire JSON with a @typedef, as I thought it wouldn't collapse the properties name, but it failed.
Thanks in advance.

Questions are best asked on the google group or stackoverflow. We reserve the issue tracker for actual bugs and feature work.
You would need to specify your typedef in an extern file and annotate your init function with that type.

Thanks, will do, sorry about that !


Alternative backup location

Copy backups to user specified directory outside of pluginConfigs / app data.

This introduces complexity, and edge cases, and likely will not be supported by future versions of Dalamud when they lock down permissions. Marking as won't fix.


Add custom properties to element object

Hi, is there a way to add more data to a node object?

We’ll need more information before we can answer your question.
like what would this extra data look like when it is rendered?
please consider providing a visual mock-up and/or a TypeScript interface for your proposal.
before you do, please look at the interface to see if it’s possible. There is a render function that likely does what you need.

Basically, i want to add more optional data to my node when generating the data tree so i can do conditional styling/behaviour.

Is there a way to preserve the same node ids when generating a tree using the flattenTree helper function instead of autoincremental ids.

This isn’t a scenario that I or my team has needed so the only answer I can give is “I don’t know.”
I will share that there is a nodeRenderer function on the component for which you can do a lookup within and then conditionally style each node. The lookup (by name or by ID) will allow you to get everything you need.
I don’t have time to code that out right now.
I think it might be best to keep “how to” questions to StackOverflow as issues are for bug fixes or feature requests. And in full transparency, we won’t be taking on feature requests unless they are accessibility related since the current API is flexible enough for almost anything.


Deploy

👷 Deploy Preview for mskangg processing.

Name
Link

🔨 Latest commit
daa72ab0f04e329410775280064a2db50876c0eb

🔍 Latest deploy log
https://app.netlify.com/sites/mskangg/deploys/63289a81f4719800083c7ce4


QFT_demo

Title: Basic arithmetic with QFT
Summary: Demo
Possible Drawbacks: Update with pennylane 0.24

Thank you very much for all the comments @alvaro-at-xanadu 😊! It has been a very complete and easy review to do thanks to your suggestions! 🚀
PS: The last graph will not give good results now, we will have to wait for pennylane version 0.25.

Thanks @ikurecic , corrected! I put the commas outside the math part.


from_state_dict is too lenient

I was checking #1261 and found this pattern:
with open(model_file, "rb") as state_f:
  state = from_bytes(AwesomeModel, state_f.read())

However setting target to a regular Module subclass type in from_bytes just results in no checks being performed as state is returned as is for unregistered types:
https://github.com/google/flax/blob/6fd24460e88c833fa481228582937c692e9c182c/flax/serialization.py#L63-L64
Using an unregistered type just gives a false sense of security that validation is happening, it would be more correct to accept target=None as a way of opting-out of this check but anything else should require the type to be registered.

Agree

cc @patrickvonplaten

Proved more complex than expected to try to fix from_state_dict it feels as if there are two possible versions for this function, one which is lenient and is used extensively through the code base to check structures, another one which could be made more strict and could be targeted towards adding safety for end users when de-serializing. There is no easy way to reconcile both modes without significant changes, therefore I'll be closing this issue.


Don't generate setup.py by default.

Autogenerating setup.py was a workaround to let pip install from source before PEP 517. pip supports PEP 517 since 19.0 (January 2019). Of course it supports installing wheels since much earlier (2013), and this is the default installation method. So I'm gradually moving towards getting rid of the generated setup.py file.
In Flit 3.4 (2021-10-10), I added a message saying that the default would change, and adding a (no-op) --setup-py option.  This PR will make --no-setup-py the default behaviour, and update the message accordingly.
I haven't decided when to merge this yet. The flit command line tool is meant as a developer tool, so I think it's reasonable to do changes like this relatively quickly (unlike in the lower-level flit_core package). But the purpose of adding the message in 3.4 is to give people a chance to be aware of the change coming and react to it.

This seems to be causing problems as there still aren't alternatives to python setup.py build AFAIK for PEP 517(maybe I missed how one is supposed to do a regular build here).
I was trying to package a python package without a setup.py for buildroot which uses separate build and install stages but I haven't manged to figure out how to do a build without an install without the generated setup.py.

The generic answer is the build package, which should be able to invoke the build backend for any Python project, based on the information specified in its pyproject.toml (falling back to setuptools & setup.py if nothing else is specified).
Python packaging is also moving towards separate build & install stages, with the wheel package format as the boundary between them, so build will give you a wheel. The installer package is intended to be the low-level counterpart to build, which takes a wheel and installs it, but it doesn't have a CLI yet (there's a PR at https://github.com/pradyunsg/installer/pull/66). You can write a Python script to call it, or use pip for now to install from a wheel.

The generic answer is the build package, which should be able to invoke the build backend for any Python project, based on the information specified in its pyproject.toml (falling back to setuptools & setup.py if nothing else is specified).

So to clarify we're not trying to build a package like a sdist or a wheel, we pull in the sdist and are trying to do a basic build in place like python setup.py build does.

Python packaging is also moving towards separate build & install stages

Hmm, I wonder why it's unclear how to do this when it used to be straight forward with distutils/setuptools. Wheel is used for distributing pre-built packages on sites like pypi which is not what we're trying to do. We're just trying to do the compile/build stage from the existing sdist which comes before the install, this would be the stage say where any c extensions would get built but before the package is installed into the target site-packages. This works fine with setuptools and distutils at least but it's unclear how to do this with PEP-517.

The installer package is intended to be the low-level counterpart to build, which takes a wheel and installs it, but it doesn't have a CLI yet (there's a PR at pradyunsg/installer#66).

Well we're not trying to use wheels at all so I'm not sure that would be right, we're basically trying to do a standard in tree build of the sdist in preparation for install, we're only trying to do a build, we're not trying to create artifacts for distribution outside of buildroot.

You can write a Python script to call it, or use pip for now to install from a wheel.

Hmm, it's unclear what we should actually be calling, and pip doesn't seem to provide a build(without packaging) option either from what I can tell, we've always had to directly invoke it from distutils/setuptools in the past. We don't even support pip for builds due to it not being cross compilation friendly last I checked.

Wheel is used for distributing pre-built packages on sites like pypi which is not what we're trying to do. We're just trying to do the compile/build stage from the existing sdist which comes before the install, this would be the stage say where any c extensions would get built but before the package is installed into the target site-packages.

The scheme Python packaging has been working towards for the last few years is to use the wheel as the standard interface between the build step and the install step. So whatever build system the project uses - such as Flit - produces a wheel with the interface in PEP 517, and that defines what is to be installed.
I.e. the wheel is the concrete representation of the stage you describe after building C extensions etc. but before the package is installed. The wheel represents all the files that should be installed, without the build tool having to know anything about the install location(s).

So whatever build system the project uses - such as Flit - produces a wheel with the interface in PEP 517, and that defines what is to be installed.

So I guess it's expected that distros round trip the stdists through wheels for all package builds I guess? I did come across this which seems similar to how we normally do builds.

The wheel represents all the files that should be installed, without the build tool having to know anything about the install location(s).

Hmm, I thought using wheels caused issues with cross compilation unless they are pure python(and even then I think pip didn't play nice in general with cross compilation), although things may have changed. I guess I probably need to wait for the installer cli interface though, any idea if installer has been tested in cross compilation scenarios?
Historically we've had to hack up the internals to get python's build systems to place nice with cross compilation in general as cross compilation seems to not get a lot of testing in that area from most python packaging related projects.

So I guess it's expected that distros round trip the stdists through wheels for all package builds I guess?

That's the idea, yes. :slightly_smiling_face:

I did come across [build_editable] which seems similar to how we normally do builds.

I think that's a red herring. 'Editable' installs are meant for development: instead of installing the package files, you install a little shim which adds the source location to the import path, so you can change the source and use it without having to reinstall it. As part of that, it can do an in-place build if there's anything that needs building.
It's possible you could figure out some way to use that for downstream packaging, but it's quite different from the intended use case, so you'd be swimming against the stream. The build_editable hook is also optional for backends, whereas build_wheel in PEP 517 is required.

I thought using wheels caused issues with cross compilation unless they are pure python(and even then I think pip didn't play nice in general with cross compilation),

Pure Python wheels, where the filename ends like -none-any.whl (no ABI requirement, any platform) should be fine - you can build them on one platform and install on another.  For packages with compiled parts... I don't really know, to be honest. You're quite right, this is not something Python packaging is adapted for. Our normal expectation is that if something needs to be specifically built for a given platform, you build it on that platform. https://www.piwheels.org/ builds many thousands of packages on Raspberry Pis, for instance.

any idea if installer has been tested in cross compilation scenarios?

The install is the easy bit - the wheels already contain the compiled libraries for a specific platform, and installing is just a matter of unpacking them to the right locations (plus generating some script wrappers and fiddling with a bit of metadata). Any complexity involved in cross-compilation is on the build side, to get the wheel.

That's the idea, yes. 🙂

Seems a bit odd to me but I suppose it's possible it could work, the how part is just not all that obvious for cross compilation scenarios like this.

Pure Python wheels, where the filename ends like -none-any.whl (no ABI requirement, any platform) should be fine - you can build them on one platform and install on another.

Yeah, I don't think those are that big an issue. We just don't use them currently at all since we prefer using sdists.

For packages with compiled parts... I don't really know, to be honest. You're quite right, this is not something Python packaging is adapted for. Our normal expectation is that if something needs to be specifically built for a given platform, you build it on that platform. https://www.piwheels.org/ builds many thousands of packages on Raspberry Pis, for instance.

Yeah, which is an obviously wrong assumption, but it has unfortunately managed to get baked into a lot of python's packaging/build tooling.

The install is the easy bit - the wheels already contain the compiled libraries for a specific platform, and installing is just a matter of unpacking them to the right locations (plus generating some script wrappers and fiddling with a bit of metadata). Any complexity involved in cross-compilation is on the build side, to get the wheel.

Well install is often much less simple with cross-compilation than one would often assume since the install location(site-packages for the target python interpreter) also differs from that used by the running python interpreter(the host python interpreter). There's a good bit of complexity on both sides here I think.
By the way would it be possible to provide setup.py's for bootstrapping flit and tomli? Right now it's kinda a PITA to install them due to the recursive dependency issue.

Yeah, which [build on the appropriate platform] is an obviously wrong assumption, but it has unfortunately managed to get baked into a lot of python's packaging/build tooling.

TBF, from a Python packaging point of view, it's not obviously wrong. I'd estimate that ~90-95% of packages on PyPI are pure Python, where we don't have to worry about cross compilation at all. And for the packages that do need compilation, 'build it on the relevant platform' generally works well enough for ~95% of what the people we hear from are interested in.
If you're interested in discussing how Python packaging can improve on this, then the Packaging category on the Python Discourse forum is probably the place to do so.

Well install is often much less simple with cross-compilation than one would often assume since the install location(site-packages for the target python interpreter)

Sure, but so long as you know what the right target directories are, it's just a matter of specifying them in the right place. installer can deal with this - it takes a 'scheme' dictionary of directories to install to.

By the way would it be possible to provide setup.py's for bootstrapping flit and tomli? Right now it's kinda a PITA to install them due to the recursive dependency issue.

I'm sorry about this difficulty, and I've done my best to document how to deal with it:
https://flit.readthedocs.io/en/latest/bootstrap.html
I hope that one day, there will be a TOML parser in the Python standard library. Until then, it's hard to avoid needing a bit of a manual workaround. There's more discussion about this in #462.
I'm afraid I'm not prepared to reintroduce setup.py - we've done a lot of work in the last few years to build packaging infrastructure on a solid base of specifications, rather than 'whatever setuptools does'. The author of tomli may choose to, but so far (in #462), he seems to be on board with the idea of bootstrapping without setuptools. Of course you can patch in setup.py to either project if that's what you need to build them in your setup.

I'm sorry about this difficulty, and I've done my best to document how to deal with it:

Reading that it says flit is itself packed with flit, so wouldn't that mean you just need to set --setup-py during the flit and tomli build process? Obviously this would need to be done for the sdist generation as we wouldn't be able to do it downstream due to the chicken and egg problem(we also don't support pip so we can't just use a prebuilt whl either).

Until then, it's hard to avoid needing a bit of a manual workaround.

I don't see how it's hard to avoid, seems setting --setup-py is all that's needed for flit and tomli sdist builds.

You could also just copy flit_core from the source directory

This is the only thing that seemed to work without a setup.py(since we don't have whl infrastructure bootstrapped already), but it's very brittle and not ideal for bootstrapping.

There are several reasons that I don't want to do that.
The most obvious & least important is that setup.py generation is in the higher-level flit package, which shouldn't be involved in building flit_core at all. That's unimportant, because the relevant code could be moved to flit_core, but it's not just a matter of turning the switch on.
Next, for the dependency cycle between flit_core & tomli, having a setup.py with flit_core doesn't actually solve it. flit_core can already build itself without tomli - I've taken care to ensure this is possible. But it has a runtime dependency on tomli, so you need tomli to build tomli. Having a setup.py with tomli would be a workaround for that (but not the only one).
Finally, I want to have Flit & the ecosystem of newer tools & standards we've developed standing firmly on their own feet, not propped up by setuptools right at the base. The --setup-py option, and the code in flit to support it, is a temporary measure which will eventually go away.  It's already gone from always-on to opt-out to opt-in, and that trajectory is going to continue. I don't like the signal that releasing flit_core with a setup.py would send. And if I add it temporarily, people will rely on it, and this discussion will happen all over again when I remove it.
Again, though, if you want to add a setup.py as a patch in your own packaging, that's fine. I know that some workaround is needed for bootstrapping, and while that's not the one I'd pick, I won't fault you if you want to. It can probably be pretty simple and need only minimal maintenance. But whatever decisions & maintenance it does require is on you (your project, not you personally).
Some other resources you might find interesting:

https://github.com/FFY00/python-bootstrap (I just saw this recently)
A talk on how Fedora is dealing with the new world of PEP 517: https://www.youtube.com/watch?v=pJlqB-PA96E

This is the only thing that seemed to work without a setup.py(since we don't have whl infrastructure bootstrapped already)

For simple packages like flit_core & tomli (pure Python, no scripts), installing the whl is just a matter of unzipping it to the site-packages directory. This is how I'd approach bootstrapping.

But it has a runtime dependency on tomli, so you need tomli to build tomli. Having a setup.py with tomli would be a workaround for that (but not the only one).

I was working on fixing that as well....why not bundle tomli with flit like pip does?

Finally, I want to have Flit & the ecosystem of newer tools & standards we've developed standing firmly on their own feet, not propped up by setuptools right at the base.

So make migration/bootstrapping as difficult as possible? That seems rather counterproductive....

I don't like the signal that releasing flit_core with a setup.py would send. And if I add it temporarily, people will rely on it, and this discussion will happen all over again when I remove it.

I don't get this...you want people to migrate but you want it to also be as painful as possible by making even a simple installation super difficult for anyone that has custom distro tooling(by creating recursive dependency issues)?
I did manage to hack something together temporarily but it's really not ideal.

I was working on fixing that as well....why not bundle tomli with flit like pip does?

My experience with Linux distros is that the people who care most about this kind of bootstrapping also insist on unbundling dependencies, so bundling makes more work for downstreams, not less. I might revisit that if there are more downstream ecosystems that are fine with bundling... but if I did that, I'd expect pushback from the ecosystems that I know dislike bundling. :shrug:

So make migration/bootstrapping as difficult as possible?

I appreciate that not having a setup.py file makes your life more difficult, but I don't think this is 'as difficult as possible'. I've thought about bootstrapping, written docs, and offered suggestions here. Once more, this is how I would suggest downstreams deal with the tomli <-> flit_core dependency cycle:

Package flit_core

Use its build_dists.py script to get a wheel. This doesn't require anything except Python. Then use unzip or pip to unpack that to site_packages. I could even add a bootstrap install script that can do this if you like.
Alternatively, copy the package directory to site-packages manually (but be aware pip won't know it's installed without the metadata from the wheel).
Alternative 2, add a setup.py yourself and run that.

Package tomli

Install the flit_core package from the previous step
Make tomli importable from source (e.g. by setting PYTHONPATH)
Call the Python function flit_core.buildapi.build_wheel(some_tmp_dir) to make a wheel
Use unzip or pip to install the wheel.

I feel like your responses are gradually edging towards irritated grumbling that I won't do what you want, rather than having a productive discussion. I won't lock the thread yet, but please, if you're frustrated about this, go and do something else for a few hours rather than writing a fast, grumpy reply.

My experience with Linux distros is that the people who care most about this kind of bootstrapping also insist on unbundling dependencies, so bundling makes more work for downstreams, not less. I might revisit that if there are more downstream ecosystems that are fine with bundling... but if I did that, I'd expect pushback from the ecosystems that I know dislike bundling. 🤷

I'd say while this is true for applications it's more often the opposite for build systems(good ones at least), the popular cross-language python based build system meson(used for building apps like systemd on all modern distros) has a very strict rule when it comes to dependencies which I agree with a lot:

There have been many Python programs that are difficult to maintain on multiple platforms. The reasons come mostly from dependencies. The program may use dependencies that are hard to compile on certain platforms, are outdated, conflict with other dependencies, not available on a given Python version and so on.
Meson avoids dependency problems with one simple rule: Meson is not allowed to have any dependencies outside the Python basic library. The only thing you need is Python 3 (and possibly Ninja).

I appreciate that not having a setup.py file makes your life more difficult, but I don't think this is 'as difficult as possible'. I've thought about bootstrapping, written docs, and offered suggestions here. Once more, this is how I would suggest downstreams deal with the tomli <-> flit_core dependency cycle:

Yeah, thanks for the suggestions, I've actually been experimenting a bunch, I'm mostly trying to see if I can find a more maintainable solution for buildroot than that pile of ugly hacks I came up with, ideally something that has a more incremental migration path.

Package flit_core
Use its build_dists.py script to get a wheel. This doesn't require anything except Python. Then use unzip or pip to unpack that to site_packages. I could even add a bootstrap install script that can do this if you like.
Alternatively, copy the package directory to site-packages manually (but be aware pip won't know it's installed without the metadata from the wheel).
Alternative 2, add a setup.py yourself and run that.
Package tomli
Install the flit_core package from the previous step
Make tomli importable from source (e.g. by setting PYTHONPATH)
Call the Python function flit_core.buildapi.build_wheel(some_tmp_dir) to make a wheel
Use unzip or pip to install the wheel.

I've made a few attempts at something along these lines but keep getting bogged down in dependency hell fairly quickly.

I feel like your responses are gradually edging towards irritated grumbling that I won't do what you want, rather than having a productive discussion. I won't lock the thread yet, but please, if you're frustrated about this, go and do something else for a few hours rather than writing a fast, grumpy reply.

Sorry, I'm really just trying to bounce ideas around to see what I'm missing and what might be missing on on the pep-517 build system side of things.
I'm usually pretty good with build systems in general(I help maintain a lot of packages in buildroot) but none of the approaches I've tried so far appeared to be all that maintainable when it comes to the integration with buildroot(which to be fair is a bit weird when it comes to python stuff).
It's not out of the norm for features we need for cross compilation, or features needed due to our distro tooling being a bit weird to be missing entirely from newer build systems(and it's not out of the norm to have features we need missing on older widely used build systems like meson either), sometimes it just takes a good bit of back and forth to find a good maintainable solution(which is what I'm trying to do).


Querying dynamic virtual table

Hello there,
not sure if this is the right place instead of StackOverflow, however I think that this could be an useful discussion here. Here's some context.
I have a simple table to track existing appointments:
  field :user_id, :integer
  field :duration, Ecto.Postgres.Tsrange # this one is a custom type that handles PG's tsrange

I want to get the available slots based on duration, user and date, so I wrote this raw SQL query:
    WITH slots AS (
      SELECT UPPER (duration) AS start_at,
        LEAD ( LOWER (duration), 1, UPPER (duration) )
        OVER (ORDER BY duration) - UPPER (duration) AS available_time,
        user_id AS user_id
      FROM (
        SELECT user_id, duration
        FROM appointments
        WHERE user_id = #{user_id}
        UNION ALL
        VALUES
          (#{user_id}, '[#{opens.beginning_of_day}, #{opens.open_at})'::tsrange),
          (#{user_id}, '[#{opens.close_at}, #{opens.end_of_day})'::tsrange)
      ) AS _
    )

    SELECT * FROM slots
    WHERE available_time >= '#{duration} minutes'::INTERVAL
    ORDER BY start_at ASC

It works as expected, however I have to run it through Ecto.Adapters.SQL.query and then wrap/parse raw results into a proper struct (or a list of it).
So my question: is there a way to use Ecto.Query.API to avoid wrapping/parsing of raw results?
Thanks in advance :-)

The Repo.load/2 function was created exactly for loading raw results into structs with proper type casting.
An example from the docs
iex> result = Ecto.Adapters.SQL.query!(MyRepo, "SELECT * FROM users", [])
iex> Enum.map(result.rows, &MyRepo.load(User, {result.columns, &1}))
[%User{...}, ...]

Thanks for the reply, that's what I've already did :-P I was wondering if there was another way ;-)
Thanks again!


Remove workaround for fixing #11

Fix #11

Did you double check if this is actually working? I did not, even if I guess it should work.


reassemble the content into sentences which could be well comprehended by LLM

Describe your problem
In the readme of deepdoc, it is mentioned that tables will be converted into natural language sentences that are easy to handle by LLM. How is it implemented, or in which parts of the code?

In deepdoc/vision/table_structure_recognizer.py, it's coperated with deepdoc/parser/pdf_parser.py

Where will this part of the effect be output? I saw in the web demo that the table is output in HTML format


error in tag of docker

I just download latest release <IP_ADDRESS>-docker, and try to do compose the docker, with docker-compose up -d && docker-compose logs -f
I got this error:
[+] Running 1/1
 ✘ cardano-db-sync Error                                                                                1.5s
Error response from daemon: manifest for inputoutput/cardano-db-sync:<IP_ADDRESS> not found: manifest unknown: manifest unknown

I went in the hub of input output: https://hub.docker.com/r/inputoutput/cardano-db-sync/tags
And the tag for the image needed in the docker compose file: inputoutput/cardano-db-sync:<IP_ADDRESS>  does not exist.
Exist instead: inputoutput/cardano-db-sync:<IP_ADDRESS>-docker
I just replace it in docker-compose.yml file and I was able to compose the Docker

I think this is fixed, as docker compose now mentions, <IP_ADDRESS>


Is it possible to make a function that will work when the animation of the object ends?

if getProperty ("sandsundertaleholyshit.animation.curAnim.finished")
end
something like this


dart:ffi will pass non-Instances to Dart code

I noticed that ffi/regress_jump_to_frame_test fails when using the incremental kernel compiler (such as when running with --observe). This is because the incremental kernel compiler is missing metadata that normally causes some type checks to be skipped. These type checks run against an UnhandledException, which is not an Instance. More generally, I can from Dart try to print or otherwise interact with the result of alwaysThrow and crash in various places in the runtime. In the compiler, I notice that code for marshaling from C to Dart will unwrap any Dart_Handle, but only Instances can be handled by Dart.
The Dart code implementing mirrors has a similar issue in referencing Libraries, Classes, Functions, etc, which are all non-Instances. In these cases, the mirrors implement keeps these references in an opaque MirrorReference, which is an Instance but whose referent can only be accessed by the C++ part of the mirrors implementation. This might be useful for marshaling non-Instances to Dart in the FFI.
For the special case of Error, it might make sense to throw/Dart_PropogateError when an Error is returned from C to Dart.
@dcharkes

Duplicate of #44315

I should have referenced the bug from the test, sorry.


Feature/cce 588 detail1 starter page update

@like-me1  - when i click on the upload button, nothing happens. when i click on the delete button, the image cat image gets replaced with a spinner and the upload image dialog opens. Not sure if this is the right interaction?

@saadmhybris I fixed the issue, please don't forget to run gulp less command before running the server. The loading process and hidden buttons on click were not described in the task. It's just a logical outcome from my side.


Support "Paste" & "Paste and Indent"

In the Sublime Text we have ctrl + v/ctrl + shift + v for paste/paste and indent.
Could code support this?
It'll be even better to make paste and indent as default pasting behavior.

There is "editor.formatOnPaste": true. Does that cover this case?

Closing until more details are provided


Deal with spurious callback exceptions.

Exceptions were appearing in strange places with lazyFail=False.
On investigation, two unexpected things were happening. Each of the two commits on this branch fixes one of those things:

handle_update was throwing an exception in the case on a non-lazy fail, rather than returning. In general, it doesn't make sense for a callback to throw an exception as there is no where for the exception to go. One commit on this branch replaces that explicit raise with a return.

EXCEPT:

if a callback fires straight away when added to a future, and that callback throws an exception, then (sometimes?) the exception propagates to up through add_done_callback call and out into the code containing that. That gives a race condition where sometimes a failing task (if it fails fast enough) will cause an exception there, and sometimes not (if it fails too slowly); in the latter case, the exception disappears into the void.

The second commit on this branch puts explicit try/catch-log-discard blocks round places where handle_update is called, to give "exceptions in callback handles don't come out of add_done_callback calls" behaviour (as I thought was originally happening).
Either of these commits would be sufficient to solve the specific problem I was experiencing with lazy fail exceptions, but both together make things a bit more resilient in general.

this hung in  parsl/tests/test_checkpointing/test_regression_233.py  on python 3.6. Unclear to me if that is related to PR or something else.

 It hung once in many hundreds. I also ran master, and it hung 0 times in many hundreds.
My gut feeling is that that the test hung due to some other race condition, but other PRs exist that peturb our race condition ecosystem, so I think we should merge this (and them) and move on.

crossref #1257 discussion

Perhaps another option would be to add a @callback decorator that ensures that exceptions thrown by the wrapped method are very clearly reported.
I think that deadlocks and failure to make progress are notoriously hard to troubleshoot. In an async system, like parsl, in which progress relies on the correct functioning of callbacks, failure of callbacks is a clear source of problems. Ensuring that such faults are reported and, perhaps, integrated with tests such that callback faults cause tests to fail, should be something we strive for.

I think that approach would also have value where threads/processes are launched and exceptions can fall out the top of those too - that has been a problem in parsl too.


Applications Categories

Change the reply message to get it from english.json

If you need change something do it. ❤


932230<PHONE_NUMBER>60<PHONE_NUMBER>39 932237 False positive with words environment and performance

Description
I've found additional false positives with 932236 with the words environment and performance, the env and perf are being matched.
The env FP is simlar to set, it will return the system's current environment variables if executed without any arguments, I've handled it in the same way by adding @.
The perf command is completely harmless without specifying any arguments, it just returns a help page, I've also resolved this by adding an @.
I've opened a pull request here: https://github.com/coreruleset/coreruleset/pull/3477
How to reproduce the misbehavior (-> curl call)
curl -H "x-crs-paranoia-level: 2" -H "x-format-output: txt-matched-rules" https://sandbox.coreruleset.org/?test=environment

curl -H "x-crs-paranoia-level: 2" -H "x-format-output: txt-matched-rules" https://sandbox.coreruleset.org/?test=performance

Logs
2024/01/11 17:59:01 [info] 1380524#1380524: *136968 ModSecurity: Warning. Matched "Operator `Rx' with parameter `(?i)(?:(?:^|=)[\s\v]*(?:t[\"'\)\[-\x5c]*(?:(?:(?:\|\||&&)[\s\v]*)?\$[!#\(\*\-0-9\?-@_a-\{]*)?\x5c?i[\"'\)\[-\x5c]*(?:(?:(?:\|\||&&)[\s\v]*)?\$[!#\(\*\-0-9\?-@_a-\{]*)?\x5c?m[\"'\)\[-\x5c]*(?:(?:(?:\|\ (5963 characters omitted)' against variable `ARGS:test' (Value: `environment' ) [file "/etc/nginx/modsecurity/coreruleset/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "1345"] [id "932236"] [rev ""] [msg "Remote Command Execution: Unix Command Injection (command without evasion)"] [data "Matched Data: env found within ARGS:test: environment"] [severity "2"] [ver "OWASP_CRS/4.0.0-rc2"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "<IP_ADDRESS>"] [uri "/"] [unique_id "170495634156.172522"] [ref "o0,3v16,11"], client: <IP_ADDRESS>, server: <IP_ADDRESS>, request: "GET /?test=environment HTTP/2.0", host: "<IP_ADDRESS>"
2024/01/11 17:59:21 [info] 1380524#1380524: *136968 ModSecurity: Warning. Matched "Operator `Rx' with parameter `(?i)(?:(?:^|=)[\s\v]*(?:t[\"'\)\[-\x5c]*(?:(?:(?:\|\||&&)[\s\v]*)?\$[!#\(\*\-0-9\?-@_a-\{]*)?\x5c?i[\"'\)\[-\x5c]*(?:(?:(?:\|\||&&)[\s\v]*)?\$[!#\(\*\-0-9\?-@_a-\{]*)?\x5c?m[\"'\)\[-\x5c]*(?:(?:(?:\|\ (5963 characters omitted)' against variable `ARGS:test' (Value: `performance' ) [file "/etc/nginx/modsecurity/coreruleset/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "1345"] [id "932236"] [rev ""] [msg "Remote Command Execution: Unix Command Injection (command without evasion)"] [data "Matched Data: perf found within ARGS:test: performance"] [severity "2"] [ver "OWASP_CRS/4.0.0-rc2"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "<IP_ADDRESS>"] [uri "/"] [unique_id "170495636129.686283"] [ref "o0,4v16,11"], client: <IP_ADDRESS>, server: <IP_ADDRESS>, request: "GET /?test=performance HTTP/2.0", host: "<IP_ADDRESS>"
Your Environment

CRS version (e.g., v3.3.4): CRSv4 RC-2
Paranoia level setting (e.g. PL1) : 2
ModSecurity version (e.g., 2.9.6): 3.0.11
Web Server and version or cloud provider / CDN (e.g., Apache httpd 2.4.54): Nginx
Operating System and version: Ubuntu

Confirmation
[x] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

Thank you for reporting - and fixing on top!


Excessive Size of Compiled EXE on Windows Example Code

The compiled exe file from the example code on Windows is too large. I think it's a bit unreasonable to be that big.

The debug build sizes are very bad in all operating systems, release builds are a better, and it does not affect performance and memory use, so this issue does not affect distribution at least.
As for why it is so large I'm at a loss, if you review the build features I implemented a "debug_default" that enables dynamic dispatch in many otherwise generic functions, an attempt to reduce code bloat, but its still bad. I'm hoping the Rust 2024 "impl trait use bounds" will show some improvements too.

调试版本大小在所有操作系统中都非常糟糕，发布版本更好，并且不会影响性能和内存使用，因此此问题至少不会影响分发。
至于为什么它这么大我不知所措，如果你回顾一下我实现的构建功能，它在许多通用函数中启用动态调度，这是为了减少代码膨胀，但它仍然很糟糕。我希望 Rust 2024 的“impl trait use bounds”也能显示出一些改进。"debug_default"
编辑：实际上我也看到了示例的大型发布版本，这一定是来自过去两个月的更新，我会调查一下。

Compiling the following code in release mode results in 80MB, which is shocking, especially since it's only a dozen lines of code. It's even larger than using Bevy or other game engines.
use zng::prelude::*;
fn main() {
zng::env::init!();
APP.defaults().run_window(async {
let size = var(layout::Size::new(800, 600));
Window! {
title = size.map(|s| formatx!("Button Example - {s}"));
size;
child_align = Align::CENTER;
child = Button! {
on_click = hn!(|_| {
println!("Button clicked!");
});
text::font_size = 28;
child = Text!("Click Me!");
}
}
})
}


Add shotgun.live information

This PR adds information on how to delete a shotgun.live account

Thanks for your contribution!


How do I close all logs?

How do I close all logs?:(
All this.:(

I tried to download the source code and annotate all the LOG logs, but I failed to package it into a jar.

Please have a lock at https://htmlunit.sourceforge.io/logging.html.

Have you solved that? Can i close this issue?

Will close this, feel free to open a new one if you need more support regarding this.

sorry, i have not been informed of this answer...
I haven't solved it yet.
I have added restrictions according to the document, but a print log will appear.
I open a new to u,need ur help...


Update sentry version and use custom fork of ember-cli-sentry.

Updates Raven to use 1.1.19 (see changelog for list of bugfixes), and uses master of ember-cli-sentry to take advantage of upstream Ember plugin fixes.
Adds a monkey patch to Raven.captureMessage to add a stacktrace so that we can track down the source of the [object Object] errors.

Addresses https://github.com/aptible/dashboard.aptible.com/issues/346.

:+1: !

Just updated to add a monkey patch to Raven.captureMessage to add a stacktrace so that we can track down the source of the [object Object] errors.
@sandersonet - I'd like to land this, and get it deployed (to at least staging) and see if we can trigger the errors in question.  Any objection?

Merge at will and it should hit staging shortly thereafter.  Also looks like a minor test failure.

Whoops, fixed JSHint error and pushed an update.  Will merge once green...


[Bug]: the model_type field is fixed parameter "image2text" when using ollama to add a chat model on the webUI

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
265a7a283ae1a29a4827d2a973d62cad14c41dc5
Other environment information
No response
Actual behavior
the model_type field is fixed parameter "image2text" when using ollama to add a chat model on the webUI，lead to I can not add a chat model
Expected behavior
No response
Steps to reproduce
1. using ollama to deploy a chat model
2. using ollama add a chat model on the webUI
3. model_type select "chat" and add other paramters
4. click ok，then it is failed

Additional information

Sorry, can't reproduce that. Maybe upgrade the system?

Cannot reproduce.


Cannot pass command with va_list to specific node

If I understand correctly, current API does not provide redisClustervCommandToNode() or something similar.
Therefore passing variadic commands to specific node is currently done using dirty hacks in code and duplication of parts of library code.
Is there any possibility of adding this API to hiredis-cluster? Thanks.

Sure! A PR is welcomed.

Ok, will cook something up on the weekend. Thanks.


Typo in wiki

Streaming Music
Out of the box Koel supports two so-called “streaming methods”: using native PHP readfile() and via Apache’s mod_xsendfile. When the former works, the latter is wayyy faster and much, much, much more stable, thus highly recommended. I can’t stress this enough:

should be:

Streaming Music
Out of the box Koel supports two so-called “streaming methods”: using native PHP readfile() and via Apache’s mod_xsendfile. While the former works, the latter is wayyy faster and much, much, much more stable, thus highly recommended. I can’t stress this enough:

:+1: Thanks! And sorry for my bad Engrish.

:) that's hilarious


Repo sync for protected CLA branch

The pull request is created from main638062418905945299sync_temp to main to fix git push error for protected CLA branch

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


Maintenance/Update MOM6

This PR adjusts CMakeLists.txt to be able to work with updates from this  PR.
Specifically, it adds following to the list of files that are to be built: src/parameterizations/lateral/MOM_self_attr_load.F90.
In GEOS default setting, answers are preserved.
To do:

[x] @sanAkel: https://github.com/mom-ocean/MOM6/pull/1616 once has been merged submit this PR.
[x] @mathomp4 and/or @tclune: https://github.com/orgs/GEOS-ESM/teams/cmake-team please review this PR.
[x] @mathomp4: please update our fork: https://github.com/GEOS-ESM/MOM6

Hmm. the "update MOM6" is checked and yet I don't think I've done that recently. Shall I?

Hmm. the "update MOM6" is checked and yet I don't think I've done that recently. Shall I?

Sorry @mathomp4 maybe pushing these from my phone messed it up. I just unchecked those boxes. Once PR 1616 at mom-ocean gets merged, let's get it done at our end.

@mathomp4 would you please review this PR. Thanks!

Superpowering in as this needs a new MOM6


What is the advantage to convert SMPL format to 263 dim vector for training?

Hi, thanks for a serious of nice works for the text2motion area.
I am very confused why I have to convert the SMPL format to 263 dim vectors for training. I read all your article on the subject and found no relevant instructions.
The vector in dimension 263 contains root_rot_velocity, root_linear_velocity, local_joint_postion, local_joint_rotation, local_joint_velocity, what is the reason for the rot_velocity and the linear_velociy are necessary?
I would appreciate it if you could answer or give me some references!

I think it helps capture the motion’s dynamics better, making transitions between poses smoother. Velocities are key for creating fluid, natural animations, and combining it with foot contacts makes it more realistic in physics-based simulations. By providing the model with more explicit information, it is expected to generate motions that follow the same physical rules.


create HTTP tests

a lot of development happened here the last weeks, but no tests have been added. This repo is so far only tested by API tests run in https://github.com/owncloud/ocis/pull/409

something similar to https://github.com/owncloud/ocis-hello/blob/6e81d7766fd6026cab3bb1d8db157be974b30759/pkg/proto/v0/hello.pb.web_test.go

basic example to start with https://gist.github.com/individual-it/54d78db4d987663f1a0288894dd0253a

HTTP tests endpoints
from: https://github.com/owncloud/ocis-ocs/blob/master/pkg/service/v0/service.go#L40
OCS api versions

[ ] - v1
[ ] - v2

Formats

[ ] - xml
[ ] - json

Endpoints
add v1.php/v2.php in the beginning and ?format=xml/?format=json in the end

[ ] - /apps/filesharing/api/v1 [Not Implemented]
[ ] - /apps/notifications/api/v1 [Not Implemented]
[ ] - /cloud

[ ] - GET /capabilities
[ ] -  /user

[ ] - GET /
[ ] - GET /signing-key

[ ] - /users

[ ] - GET /
[ ] - POST /
[ ] - GET /{userid}
[ ] - PUT /{userid}
[ ] - DELETE /{userid}
[ ] - /groups

[ ] - GET /
[ ] - POST /
[ ] - DELETE /

[ ] - /groups

[ ] GET /
[ ] POST /
[ ] DELETE /{groupid}
[ ] GET /{groupid}

[ ] - GET /config

@individual-it the tests for basic user's API is done. Do we keep this issue open till apps/filesharing/ and apps/notifications get implemented or close this issue for now.

maybe better to close this one and open new issues for the missing tests or add a checkbox if there are issues to implement the features themself