Failed Install 10.9.5

Hi-  I ran the pkg installer suid scan 1.1.1.pkg.  It failed the install.  There are no log files for suid in /var/log/  Looking at the read me, My periodic plist is in the correct place.  Next section:
Logout Scan
To run a script on logout, move edu.utah.scl.suid_scan.login.plist and edu.utah.scl.suid_scan.logout.plist to /Library/LaunchAgents/, and the simple shell script suid_scan.logout_wrapper.sh to /usr/local/bin/.
Check and Check all there..... so I took a peek at the periodic plist to see if there was anything I could configure....and I noticed that there was a string that might not be correct, or I don't have that path shown below.  The last string....should it be /usr/local/bin/suid_scan.py ?
dict>
Label
edu.utah.scl.suid_scan.periodic
ProcessType
Background
ProgramArguments

/usr/bin/python
/usr/local/sbin/suid_scan.py

Hey, terribly sorry about that. I'm looking into it now and I'll post back when I've found what's going on.

Hello Dan:
Sorry, about the issue. It would be helpful getting detailed installer logs to debug this issue.
The GUI installer allows you to enable displaying the logs. See “Window” menu, “Installer Log” command. Then select “Show All Logs”/
<EMAIL_ADDRESS><EMAIL_ADDRESS>If you are installer via command line:
-dumplog
Detailed log information is always sent to syslog using the LOG_INSTALL facility (and will wind
up in /var/log/install.log).  -dumplog additionally writes this log to standard error output.
Thanks:
Richard Glaser
University of Utah, Marriott Library ITS
richard.glaser<EMAIL_ADDRESS>On May 21, 2015, at 9:41 AM, Dan De Rusha <notifications<EMAIL_ADDRESS>wrote:
Hi- I ran the pkg installer suid scan 1.1.1.pkg. It failed the install. There are no log files for suid in /var/log/ Looking at the read me, My periodic plist is in the correct place. Next section:
Logout Scan
To run a script on logout, move edu.utah.scl.suid_scan.login.plist and edu.utah.scl.suid_scan.logout.plist to /Library/LaunchAgents/, and the simple shell script suid_scan.logout_wrapper.sh to /usr/local/bin/.
Check and Check all there..... so I took a peek at the periodic plist to see if there was anything I could configure....and I noticed that there was a string that might not be correct, or I don't have that path shown below. The last string....should it be /usr/local/bin/suid_scan.py ?
dict>
Label
edu.utah.scl.suid_scan.periodic
ProcessType
Background
ProgramArguments

/usr/bin/python
/usr/local/sbin/suid_scan.py
—
Reply to this email directly or view it on GitHubhttps://github.com/univ-of-utah-marriott-library-apple/suid_scan/issues/2.

here is the log.  thank you
https://dl.dropboxusercontent.com/u/46279907/Installer Log 21-May-2015.txt.zip

I just tried it on a 10.10.3 mac, the results were the same as 10.9.5 mac. same errors in the log.

wrong button..

Hello Dan:
Thanks for the logs and info. We will troubleshoot the issue and get back to you.
On May 21, 2015, at 10:51 AM, Dan De Rusha <notifications<EMAIL_ADDRESS>wrote:
I just tried it on a 10.10.3 mac, the results were the same as 10.9.5 mac. same errors in the log.
—
Reply to this email directly or view it on GitHubhttps://github.com/univ-of-utah-marriott-library-apple/suid_scan/issues/2#issuecomment-104353093.
Thanks:
Richard Glaser
University of Utah, Marriott Library ITS
richard.glaser<EMAIL_ADDRESS>

Hi @dderusha,
This was my first time working with customized installer packages and I thought I had it working, but clearly I did not. I think I've got the issue fixed now, but for the moment I'm leaving the changes in the dev branch. Try downloading the package installer from the dev branch and let me know if that works better.
Thanks for using our code and providing feedback! I always love to hear back from people.
Regards,
Pierce

No worries I'll try it out thanks!!!
Dan De Rusha

On May 22, 2015, at 5:04 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:
Hi @dderusha,
This was my first time working with customized installer packages and I thought I had it working, but clearly I did not. I think I've got the issue fixed now, but for the moment I'm leaving the changes in the dev branch. Try downloading the package installer from the dev branch and let me know if that works better.
Thanks for using our code and providing feedback! I always love to hear back from people.
Regards,
Pierce
—
Reply to this email directly or view it on GitHub.

Pierce-
I tried to run the uninstaller and it failed.
I'm currently on 10.9.5
May 26 11:38:03 9001-0856ML.local launchservicesd[80]: Application App:"Installer" asn:0x0-6d06d pid:8452 refs=7 @ 0x7fc398c5d9c0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6e06e pid=8461 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
that was when it first started to install.
and this was the end
May 26 11:38:49 9001-0856ML.local Installer[8452]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Let me know what you think.
thanks
Dan
On May 22, 2015, at 5:08 PM, Gmail<EMAIL_ADDRESS>wrote:

No worries I'll try it out thanks!!!
Dan De Rusha
On May 22, 2015, at 5:04 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Hi @dderusha,
This was my first time working with customized installer packages and I thought I had it working, but clearly I did not. I think I've got the issue fixed now, but for the moment I'm leaving the changes in the dev branch. Try downloading the package installer from the dev branch and let me know if that works better.
Thanks for using our code and providing feedback! I always love to hear back from people.
Regards,
Pierce
—
Reply to this email directly or view it on GitHub.

Hello Dan:
So, the new installer worked?
On May 26, 2015, at 10:40 AM, Dan De Rusha <notifications<EMAIL_ADDRESS>wrote:
Pierce-
I tried to run the uninstaller and it failed.
I'm currently on 10.9.5
May 26 11:38:03 9001-0856ML.local launchservicesd[80]: Application App:"Installer" asn:0x0-6d06d pid:8452 refs=7 @ 0x7fc398c5d9c0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6e06e pid=8461 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
that was when it first started to install.
and this was the end
May 26 11:38:49 9001-0856ML.local Installer[8452]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Let me know what you think.
thanks
Dan
On May 22, 2015, at 5:08 PM, Gmail <dderusha<EMAIL_ADDRESS>wrote:

No worries I'll try it out thanks!!!
Dan De Rusha
On May 22, 2015, at 5:04 PM, Pierce Darragh <notifications<EMAIL_ADDRESS>wrote:

Hi @dderusha,
This was my first time working with customized installer packages and I thought I had it working, but clearly I did not. I think I've got the issue fixed now, but for the moment I'm leaving the changes in the dev branch. Try downloading the package installer from the dev branch and let me know if that works better.
Thanks for using our code and providing feedback! I always love to hear back from people.
Regards,
Pierce
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com/univ-of-utah-marriott-library-apple/suid_scan/issues/2#issuecomment-105597383.
Thanks:
Richard Glaser
University of Utah, Marriott Library ITS
richard.glaser<EMAIL_ADDRESS>

were having captive portal issues today so my connectivity to the outside world is not reliable.
I'll test it when I'm at home tonight
the remover failed, I removed the files by hand....ran the installer and it failed...but I suspect that it was because of my network issues in the office.
I'll let you know later.
thanks
dd
On May 26, 2015, at 12:48 PM, Richard Glaser<EMAIL_ADDRESS>wrote:

Hello Dan:
So, the new installer worked?
On May 26, 2015, at 10:40 AM, Dan De Rusha <notifications<EMAIL_ADDRESS>wrote:
Pierce-
I tried to run the uninstaller and it failed.
I'm currently on 10.9.5
May 26 11:38:03 9001-0856ML.local launchservicesd[80]: Application App:"Installer" asn:0x0-6d06d pid:8452 refs=7 @ 0x7fc398c5d9c0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6e06e pid=8461 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
that was when it first started to install.
and this was the end
May 26 11:38:49 9001-0856ML.local Installer[8452]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Let me know what you think.
thanks
Dan
On May 22, 2015, at 5:08 PM, Gmail <dderusha<EMAIL_ADDRESS>wrote:

No worries I'll try it out thanks!!!
Dan De Rusha
On May 22, 2015, at 5:04 PM, Pierce Darragh <notifications<EMAIL_ADDRESS>wrote:

Hi @dderusha,
This was my first time working with customized installer packages and I thought I had it working, but clearly I did not. I think I've got the issue fixed now, but for the moment I'm leaving the changes in the dev branch. Try downloading the package installer from the dev branch and let me know if that works better.
Thanks for using our code and providing feedback! I always love to hear back from people.
Regards,
Pierce
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com/univ-of-utah-marriott-library-apple/suid_scan/issues/2#issuecomment-105597383.
Thanks:
Richard Glaser
University of Utah, Marriott Library ITS
richard.glaser<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub.

@dderusha,
I've used the new installer successfully, and I've just now got a new uninstaller to work properly. Both are accessible from: https://github.com/univ-of-utah-marriott-library-apple/suid_scan/tree/dev/pkg
(Note that this is in the dev branch; once we've got these working I'll merge them to master.)
Let me know how it goes whenever you get some time. Thanks again!
Pierce

Actually @dderusha, it looks like there's something going wrong in the upload process to GitHub. When I attempt to use the .pkg files from another computer, they both have issues. (The uninstaller fails and the installer claims it's corrupted.) I will continue to investigate.

it looks like it wants three packages and they are not there.....
May 26 17:44:31 9001-0856ML.local Installer[13541]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/var/folders/6f/lj3sb5xd5c3b4k_2j9mmwjpr0000gp/T/97BE178F-9BF7-4365-A888-5B90AAB8E972/pkg/SUID%20Scan.pkg
May 26 17:44:31 9001-0856ML.local Installer[13541]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/var/folders/6f/lj3sb5xd5c3b4k_2j9mmwjpr0000gp/T/97BE178F-9BF7-4365-A888-5B90AAB8E972/pkg/Periodic.pkg
May 26 17:44:31 9001-0856ML.local Installer[13541]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/var/folders/6f/lj3sb5xd5c3b4k_2j9mmwjpr0000gp/T/97BE178F-9BF7-4365-A888-5B90AAB8E972/pkg/Logout.pkg
are those additional packages that are called during install?
dd
On May 26, 2015, at 5:21 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Actually @dderusha, it looks like there's something going wrong in the upload process to GitHub. When I attempt to use the .pkg files from another computer, they both have issues. (The uninstaller fails and the installer claims it's corrupted.) I will continue to investigate.
—
Reply to this email directly or view it on GitHub.

Pierce-
sorry thought this sent yesterday
from the logs it looks like the installer is looking for additional packages.
May 26 17:08:45 9001-0856ML.local Installer[1205]: LSExceptions [0x6080000aea00] loaded
May 26 17:08:45 9001-0856ML.local Installer[1205]: @(#)PROGRAM:Install  PROJECT:Install-846
May 26 17:08:45 9001-0856ML.local Installer[1205]: @(#)PROGRAM:Installer  PROJECT:Installer-721
May 26 17:08:45 9001-0856ML.local Installer[1205]: Hardware: MacBookPro10,1 @ 2.40 GHz (x 8), 16384 MB RAM
May 26 17:08:45 9001-0856ML.local Installer[1205]: Running OS Build: Mac OS X 10.9.5 (13F1077)
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: TMPDIR=/var/folders/6f/lj3sb5xd5c3b4k_2j9mmwjpr0000gp/T/
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: SHELL=/bin/bash
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: HOME=/Users/dderusha
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: USER=dderusha
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: LOGNAME=dderusha
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: SSH_AUTH_SOCK=/tmp/launch-aqtPCk/Listeners
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: Apple_PubSub_Socket_Render=/tmp/launch-sQtF27/Render
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: __CF_USER_TEXT_ENCODING=0x1F6:0:0
May 26 17:08:45 9001-0856ML.local Installer[1205]: Env: __CHECKFIX1436934=1
May 26 17:08:45 9001-0856ML.local Installer[1205]: SUID Scan  Installation Log
May 26 17:08:45 9001-0856ML.local Installer[1205]: Opened from: /Users/dderusha/Documents/Casper Test Push/SUID Scan [1.1.1].pkg
May 26 17:08:45 9001-0856ML.local Installer[1205]: Product archive /Users/dderusha/Documents/Casper Test Push/SUID Scan [1.1.1].pkg trustLevel=202
May 26 17:08:45 9001-0856ML.local Installer[1205]: External component packages (3) trustLevel=100
May 26 17:08:55 9001-0856ML.local Installer[1205]: LSExceptions [0x6080000aea00] unloaded
May 26 17:09:44 9001-0856ML.local Installer[1205]: InstallerStatusNotifications plugin loaded
May 26 17:09:50 9001-0856ML.local Installer[1205]: ================================================================================
May 26 17:09:50 9001-0856ML.local Installer[1205]: User picked Custom Install
May 26 17:09:50 9001-0856ML.local Installer[1205]: Choices selected for installation:
May 26 17:09:50 9001-0856ML.local Installer[1205]: 	Install: "SUID Scan"
May 26 17:09:50 9001-0856ML.local Installer[1205]: 	Install: "SUID Scan Script"
May 26 17:09:50 9001-0856ML.local Installer[1205]: 		SUID Scan.pkg : edu.utah.scl.suid_scan : 1.1.1
May 26 17:09:50 9001-0856ML.local Installer[1205]: 	Install: "Periodic Scan LaunchDaemon"
May 26 17:09:50 9001-0856ML.local Installer[1205]: 		Periodic.pkg : edu.utah.scl.suid_scan.periodic : 0.1
May 26 17:09:50 9001-0856ML.local Installer[1205]: 	Install: "User Logout Scan LaunchAgent"
May 26 17:09:50 9001-0856ML.local Installer[1205]: 		Logout.pkg : edu.utah.scl.suid_scan.logout : 0.1
May 26 17:09:50 9001-0856ML.local Installer[1205]: ================================================================================
May 26 17:09:50 9001-0856ML.local Installer[1205]: It took 0.00 seconds to summarize the package selections.
May 26 17:10:13 9001-0856ML.local Installer[1205]: ================================================================================
May 26 17:10:13 9001-0856ML.local Installer[1205]: User picked Standard Install
May 26 17:10:13 9001-0856ML.local Installer[1205]: Choices selected for installation:
May 26 17:10:13 9001-0856ML.local Installer[1205]: 	Install: "SUID Scan"
May 26 17:10:13 9001-0856ML.local Installer[1205]: 	Install: "SUID Scan Script"
May 26 17:10:13 9001-0856ML.local Installer[1205]: 		SUID Scan.pkg : edu.utah.scl.suid_scan : 1.1.1
May 26 17:10:13 9001-0856ML.local Installer[1205]: 	Install: "Periodic Scan LaunchDaemon"
May 26 17:10:13 9001-0856ML.local Installer[1205]: 		Periodic.pkg : edu.utah.scl.suid_scan.periodic : 0.1
May 26 17:10:13 9001-0856ML.local Installer[1205]: 	Install: "User Logout Scan LaunchAgent"
May 26 17:10:13 9001-0856ML.local Installer[1205]: 		Logout.pkg : edu.utah.scl.suid_scan.logout : 0.1
May 26 17:10:13 9001-0856ML.local Installer[1205]: ================================================================================
May 26 17:10:13 9001-0856ML.local Installer[1205]: It took 0.00 seconds to summarize the package selections.
May 26 17:10:13 9001-0856ML.local Installer[1205]: -[IFDInstallController(Private) _buildInstallPlan]: location = file://localhost
May 26 17:10:13 9001-0856ML.local Installer[1205]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Users/dderusha/Documents/Casper%20Test%20Push/SUID%20Scan.pkg
May 26 17:10:13 9001-0856ML.local Installer[1205]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Users/dderusha/Documents/Casper%20Test%20Push/Periodic.pkg
May 26 17:10:13 9001-0856ML.local Installer[1205]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Users/dderusha/Documents/Casper%20Test%20Push/Logout.pkg
May 26 17:10:13 9001-0856ML.local Installer[1205]: Failed to locate package at path /Users/dderusha/Documents/Casper Test Push/SUID Scan.pkg (SUID%20Scan.pkg -- file://localhost/Users/dderusha/Documents/Casper%20Test%20Push/SUID%20Scan%20%5B1.1.1%5D.pkg)
May 26 17:10:13 9001-0856ML.local Installer[1205]: Install failed: The Installer can’t locate the data it needs to install the software. Check your install media or Internet connection and try again, or contact the software manufacturer for assistance.
May 26 17:10:14 9001-0856ML.local Installer[1205]: IFDInstallController 17240 state = 8
May 26 17:10:14 9001-0856ML.local Installer[1205]: Displaying 'Install Failed' UI.
May 26 17:10:14 9001-0856ML.local Installer[1205]: 'Install Failed' UI displayed message:'The Installer can’t locate the data it needs to install the software. Check your install media or Internet connection and try again, or contact the software manufacturer for assistance.'.
On May 26, 2015, at 4:56 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

@dderusha,
I've used the new installer successfully, and I've just now got a new uninstaller to work properly. Both are accessible from: https://github.com/univ-of-utah-marriott-library-apple/suid_scan/tree/dev/pkg
(Note that this is in the dev branch; once we've got these working I'll merge them to master.)
Let me know how it goes whenever you get some time. Thanks again!
Pierce
—
Reply to this email directly or view it on GitHub.

Oh! Wow. So I apparently forgot to use the --package-path option when I was building the installer package. It worked fine on my machine but not others.
I've updated it again so that it includes the extra packages, and I've tested on separate machines so I'm fairly confident it'll work. I also fixed the uninstaller package so that should work too.
Thanks for helping me debug all of this! Sorry for the problems though.
Pierce

no worries....it helps me learn too.
and when your getting free code, gotta chip in somewhere!!!
I'll test it again shortly
dd
On May 27, 2015, at 12:04 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Oh! Wow. So I apparently forgot to use the --package-path option when I was building the installer package. It worked fine on my machine but not others.
I've updated it again so that it includes the extra packages, and I've tested on separate machines so I'm fairly confident it'll work. I also fixed the uninstaller package so that should work too.
Thanks for helping me debug all of this! Sorry for the problems though.
Pierce
—
Reply to this email directly or view it on GitHub.

Pierce-
on my 10.9.5 system, I hand removed the old stuff, and ran the new installer
installed!!!!!
but running the script isn't yielding any results.....
I fired it off over 40 min ago and hasn't finished...
sudo /usr/local/bin/suid_scan.py --output ~/Documents/SUID_Scans/test1.txt
I pointed it at a file I touched to my documents and --output /to/my/docs
the file is still 0 k
my terminal is just hanging......
so I tried to install it on my test mac....which had some krufties left over from the last install soI thought it would be a good test for the un-installer....
no dice, and failed.
then tried to run the installer....failed....manually removed the files and still would not install...
this was a 10.10.3 mac.
I'm going to re-image it and reinstall fresh and see what happens..
on the good install, I still don't have any log files that are being generated in /var/log/
Thanks
dd
On May 27, 2015, at 12:11 PM, Dan DeRusha<EMAIL_ADDRESS>wrote:

no worries....it helps me learn too.
and when your getting free code, gotta chip in somewhere!!!
I'll test it again shortly
dd
On May 27, 2015, at 12:04 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Oh! Wow. So I apparently forgot to use the --package-path option when I was building the installer package. It worked fine on my machine but not others.
I've updated it again so that it includes the extra packages, and I've tested on separate machines so I'm fairly confident it'll work. I also fixed the uninstaller package so that should work too.
Thanks for helping me debug all of this! Sorry for the problems though.
Pierce
—
Reply to this email directly or view it on GitHub.

Hi-
my terminal just outputted this
find: /Volumes/MobileBackups/Backups.backupdb/9001-0856ML/2015-05-27-100421/HD1/Users/dderusha/Documents/SUID Scan/Installer Log 21-May-2015.txt: No such file or directory
where did it comeup with that as the path for my output file?
thanks
dd
On May 27, 2015, at 2:35 PM, Dan DeRusha<EMAIL_ADDRESS>wrote:

Pierce-
on my 10.9.5 system, I hand removed the old stuff, and ran the new installer
installed!!!!!
but running the script isn't yielding any results.....
I fired it off over 40 min ago and hasn't finished...
sudo /usr/local/bin/suid_scan.py --output ~/Documents/SUID_Scans/test1.txt
I pointed it at a file I touched to my documents and --output /to/my/docs
the file is still 0 k
my terminal is just hanging......
so I tried to install it on my test mac....which had some krufties left over from the last install soI thought it would be a good test for the un-installer....
no dice, and failed.
then tried to run the installer....failed....manually removed the files and still would not install...
this was a 10.10.3 mac.
I'm going to re-image it and reinstall fresh and see what happens..
on the good install, I still don't have any log files that are being generated in /var/log/
Thanks
dd
On May 27, 2015, at 12:11 PM, Dan DeRusha<EMAIL_ADDRESS>wrote:

no worries....it helps me learn too.
and when your getting free code, gotta chip in somewhere!!!
I'll test it again shortly
dd
On May 27, 2015, at 12:04 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Oh! Wow. So I apparently forgot to use the --package-path option when I was building the installer package. It worked fine on my machine but not others.
I've updated it again so that it includes the extra packages, and I've tested on separate machines so I'm fairly confident it'll work. I also fixed the uninstaller package so that should work too.
Thanks for helping me debug all of this! Sorry for the problems though.
Pierce
—
Reply to this email directly or view it on GitHub.

Wow, that's incredibly odd. I just ran effectively the same test on 10.9.5 and it worked fine first try, maybe 10 minutes.
Ah, on further inspection the issue is likely with the MobileBackups, and I thought I had explicitly skipped those but I guess not. From my earlier tests it seemed that the find command doesn't handle Time Machine folders very well, so I set it to skip the Time Machine volume. I'll try and find a way to not check in the MobileBackups directories.
So what you're looking at there is find attempted to poll the system about that file (which incidentally is in the SUID Scan directory) and the file stopped existing between when find asked and when the system received the request. I'm not sure why that file existed at all, to be honest, but I think it's something to do with the installation process and your local Time Machine.

aah ok, that file was there, I deleted it.....had the log scan in that dir with no space and renamed it so I could direct the output there...
I also disconnected the timemachine BU but its still running....
also re-imaged that mac and the installer ran....so I'll let you know what happens there....
what about making the installer have the uninstall checks builtin?
just in case someone downloaded the original files and run into issues....or was a hack and tried to put the files into the right places....the installer
should clean anything out that pre-existed....  ??
I'll let you know how the clean system works out!
dd
On May 27, 2015, at 2:51 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Wow, that's incredibly odd. I just ran effectively the same test on 10.9.5 and it worked fine first try, maybe 10 minutes.
Ah, on further inspection the issue is likely with the MobileBackups, and I thought I had explicitly skipped those but I guess not. From my earlier tests it seemed that the find command doesn't handle Time Machine folders very well, so I set it to skip the Time Machine volume. I'll try and find a way to not check in the MobileBackups directories.
So what you're looking at there is find attempted to poll the system about that file (which incidentally is in the SUID Scan directory) and the file stopped existing between when find asked and when the system received the request. I'm not sure why that file existed at all, to be honest, but I think it's something to do with the installation process and your local Time Machine.
—
Reply to this email directly or view it on GitHub.

on the clean 10.10 mac......installed, scanned in minutes!
Total dangerous items 32...... time to peek at the logs..
On May 27, 2015, at 3:49 PM, Dan DeRusha<EMAIL_ADDRESS>wrote:

aah ok, that file was there, I deleted it.....had the log scan in that dir with no space and renamed it so I could direct the output there...
I also disconnected the timemachine BU but its still running....
also re-imaged that mac and the installer ran....so I'll let you know what happens there....
what about making the installer have the uninstall checks builtin?
just in case someone downloaded the original files and run into issues....or was a hack and tried to put the files into the right places....the installer
should clean anything out that pre-existed....
On May 27, 2015, at 2:51 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Wow, that's incredibly odd. I just ran effectively the same test on 10.9.5 and it worked fine first try, maybe 10 minutes.
Ah, on further inspection the issue is likely with the MobileBackups, and I thought I had explicitly skipped those but I guess not. From my earlier tests it seemed that the find command doesn't handle Time Machine folders very well, so I set it to skip the Time Machine volume. I'll try and find a way to not check in the MobileBackups directories.
So what you're looking at there is find attempted to poll the system about that file (which incidentally is in the SUID Scan directory) and the file stopped existing between when find asked and when the system received the request. I'm not sure why that file existed at all, to be honest, but I think it's something to do with the installation process and your local Time Machine.
—
Reply to this email directly or view it on GitHub.

Hey, glad to hear that it finally worked! Keep in mind that some Apple-supplied files are considered "dangerous" just because they have the SUID or SGID bit set, so it may not be worth being concerned over.
I will definitely incorporate the pre-install clean idea you suggested! Definitely a useful thing to do.
Thanks again for all the help with debugging!
Pierce

heh heh...after we cracked the file open that makes sense....we would use this as the "master" per say to compare other outputs to.
if anything changed in the hashes we know something is up.
No problem helping out, it was fun!
dd
On May 27, 2015, at 4:03 PM, Pierce Darragh<EMAIL_ADDRESS>wrote:

Hey, glad to hear that it finally worked! Keep in mind that some Apple-supplied files are considered "dangerous" just because they have the SUID or SGID bit set, so it may not be worth being concerned over.
I will definitely incorporate the pre-install clean idea you suggested! Definitely a useful thing to do.
Thanks again for all the help with debugging!
Pierce
—
Reply to this email directly or view it on GitHub.


Examples don't work with Vite.

When I move the code over from the first codesandbox example into a new vite project I'm only left with a button to reset.
I've recreated the issue on the vite-react-ts stackblitz template here
https://stackblitz.com/edit/vitejs-vite-u9qzur
when i inspect the element i found that the issue is a css height set to 0px here:

Thanks for reading

Looks like you just needed to import App.css within App.tsx using import ./App.css - might be some differences with how codesandbox (which I believe is webpack) and StackBlitz (with Vite) work.
Forked example here


Port 443 doesn't work (i.e. https://local.example.com/ does not work)

Describe the bug
With port: 443 in the Vite config, The vite command errors with EACCES: permission denied <IP_ADDRESS>:443. This means we're forced to use an explicit port such as 5173. Oddly when using http-server there is no such issue. This means https://local.example.com/ does not work.
Reproduction
N/A only reproduces locally
Steps to reproduce
Run yarn create vite
Run
brew install mkcert
mkcert -install
mkcert local.example.com # run from the project folder

Change the config to:
import fs from 'fs'
import { defineConfig } from 'vite'
export default defineConfig({
  server: {
    host: 'local.example.com',
    port: 443,
    https: {
      key: fs.readFileSync('./local.example.com-key.pem'),
      cert: fs.readFileSync('./local.example.com.pem'),
    },
  },
})

Run yarn start
System Info
System:
    OS: macOS 12.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 6.31 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v16.13.2/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 108.0.5359.98
    Safari: 15.6.1
  npmPackages:
    vite: ^4.0.0 => 4.0.0

Used Package Manager
yarn
Logs
error when starting dev server:
Error: listen EACCES: permission denied <IP_ADDRESS>:443
    at Http2SecureServer.setupListenHandle [as _listen2] (node:net:1317:21)
    at listenInCluster (node:net:1382:12)
    at GetAddrInfoReqWrap.doListen [as callback] (node:net:1520:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@gaberogan

Oddly when using http-server there is no such issue.

Would you write the actual command?
Does npx http-server -a local.example.com -p 443 --tls work?

That command looks for cert.pem, but it actually reproduces the error as well once I specify the certs:
npx http-server -a local.audacy.com -p 443 --tls -C local.audacy.com.pem -K local.audacy.com-key.pem

I get EACCES: permission denied <IP_ADDRESS>:443
But this is the command that does work:
npx http-server . -S -C local.audacy.com.pem -K local.audacy.com-key.pem -p 443

The root cause seems to have something to do with the difference between those two commands.

It seems to be the -a or host flag. Perhaps I am missing something but what does it mean to listen on an IP other than <IP_ADDRESS>?
https://www.w3schools.com/nodejs/met_server_listen.asp

When -a is not set, Node.js listens to <IP_ADDRESS>.
If you change, server.host to true, I guess it works without the permission denied error.
Closing as it's not a bug.
Showing the domain host in output when host: true + https is tracked in #8200.

Thanks! This works:
import fs from 'fs'
import { defineConfig } from 'vite'
export default defineConfig({
  server: {
    host: '<IP_ADDRESS>', // or true
    port: 443,
    https: {
      key: fs.readFileSync('./local.example.com-key.pem'),
      cert: fs.readFileSync('./local.example.com.pem'),
    },
  },
})

I would still like to understand why vite defaults to localhost, as this issue's solution is not very intuitive. Is it a security thing (link for anyone reading to understand the difference)? I think it's worth considering why Node.js http-server defaults to <IP_ADDRESS> and asking why Vite thinks localhost/<IP_ADDRESS> is better. @sapphi-red

Vite does behave the same with Node.js and http-server. As you see http-server errors with -a option.
About host defaulting to localhost instead of <IP_ADDRESS>, which is not related to this issue, it is a security thing.
When you pass -a local.example.com, Node.js listens to <IP_ADDRESS> because DNS resolves local.example.com to <IP_ADDRESS>.


Amendments to Exercise downloads page

As an admin
I want to be able to only upload the relevant files for my exercise
So that the correct ones display to candidates
There are a couple of amendments to this page:

[ ] Please change the logic so that the only "required" files are:  Job description, terms and conditions, independent assessor and candidate assessment

[ ] Please add logic so that "Pensions note" and "welsh translations" are optional uploads

[ ] Please add a "save and continue anyway option" in the error summary if not all files are uploaded at the same time on the page.  The "required" ones must be in place before the exercise is approved for launch.

We should consider re-building the exercise downloads page. It can be simplified a lot and made more reliable.

Can we avoid having 'required' files and allow everything to be optional. Some exercises don't have T&Cs, some don't require independent assessors etc. There is no 'one size fits all' therefore flexibility is key


add instruction how to install

Closes #2

Add instruction how to install package using github.

@MoOx or @DCKT

I will try to push the package on npm soon with other. Sorry for the delay but if I merge this I will forget to change it back when this will be online for sure 😂

Pushed!


Stop using mergify merge queue feature

Summary
Due to recent changes in the mergify configuration/service the merge queue feature of mergify is no longer working as expected. It's not clear if this just a temporary bug in mergify, a longer term change in behavior (which requires all PR authors to be registered on mergify), or some incompatibility between the github api and mergify. However, because we're no longer able to rely on it we've moved to using github's native merge queue feature [1][2] instead. Since this new merge queue would conflict with mergify's this commit removes the merge queue configuration from the mergify configuration. The configuration for stable backporting is left in place because github doesn't natively offer that feature and it appears to still work fine.
Details and comments
[1] https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/
[2] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.0008%) to 85.377%

Files with Coverage Reduction
New Missed Lines
%

crates/accelerate/src/vf2_layout.rs
8
86.44%

Totals

Change from base Build<PHONE_NUMBER>:
0.0008%

Covered Lines:
68110

Relevant Lines:
79776

💛  - Coveralls

Now that #9809 has merged, we've found a pattern for using azure pipelines with github's merge queue. So we no longer will be using mergify's merge queue (but will still retain it's use for automatic backport).


Allow zapping without funds or an account

This is something I've been wanting to do for awhile.
It'd be nice to allow lurkers to zap and allow stackers to zap arbitrary amounts even if their wallet doesn't have enough sats.

I think this needs more explanation. How should this work? Like "likes" on nostr?

I think this needs more explanation. How should this work? Like "likes" on nostr?

My bad. Basically it means: present the person an invoice in a modal when they don't have enough funds to zap or are logged out.

You could also check for webLN support in the browser for zapping/refill using alby/joule or mobile a wallet browser instead of QR code modal.

Those would definitely be nice to have in addition to a qr.

Should this be limited to zaps or also allow posting and anything else that costs sats on SN?
I would only allow zaps in the first iteration but wanted to ask if the scope should become larger further down the road

Yes, we'd like to eventually allow posting/commenting without accounts too.
We might want to make those more expensive than usual but tbd.


Updated TOC

Fixed article names, regroup to JBoss EAP and RHEL, and cross-linked two JBoss EAP articles

Wrong repo


Latest image uses arm64 instead of amd64

Issue: The current Docker image was released using arm64 instead of amd64.
Fix: Release a new latest tag with amd64 arch.

Done, https://hub.docker.com/repository/docker/projectdiscovery/proxify


Fix project detection failed: #116

This PR made the following changes:

About #116 , This bug is caused by not catching the FileNotFoundError error, see line 147 of the script services/orchest-webserver/app/app/core/projects.py.   shutil.rmtree(full_project_path)
Set projects_dir as a configuration property, such as: app.config["USER_DIR"], because this variable is frequently combined in the code

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Great fix, LGTM!

Great fix, LGTM!


Include user creation in ddl-resource.sql

In #378 there was a changed proposed to the installation flow. Instead of having the user provide the user and database for KubeArchive, the ddl-resource.sql should create the user and database instead.

I think a problem with this approach is that it assumes that the database user our user is provided has the permissions to create users and databases. I don't think that would be the case. However we can go with this approach and see if we need to change it later.

a problem with this approach is that it assumes that the database user our user is provided has the permissions to create users and databases

I am not following here, so we are saying that we the KubeArchive, instead of:

Create a DB user for kubearchive
Create a database for kubearchive inside of the postgres
Apply the given DDL

Just do:

Apply the given DDL

The one that applies the DDL would be the same that creates a DB user and the DB, so I think it's a good idea to merge all the steps in just one.
I do not see the problem though (maybe I get lost with the different users of the sentence) can you rephrase it?

The only problem I see here is that the default password of the kubearchive user will be in the DDL too so the user will potentially need to change it in several places (secret and DDL)

I do not see the problem though (maybe I get lost with the different users of the sentence) can you rephrase it?

The problem I see is that the database user that executes the SQL may not have permissions to create databases and other users.

The one that applies the DDL would be the same that creates a DB user and the DB

I think this is incorrect: the one that needs to apply the DDL should be the KubeArchive Database User. One of the statements inside the DDL fail when applied by the admin user. See #384 .

so we are saying that we the KubeArchive, instead of:

Just to be a little bit more specific, we are not executing the SQL. This is a SQL script meant to be run by the one who installs KubeArchive.

I think this is incorrect: the one that needs to apply the DDL should be the KubeArchive Database User. One of the statements inside the DDL fail when applied by the admin user. See https://github.com/kubearchive/kubearchive/issues/384 .

I've reopened that issue and added a comment, PTAL.

Just to be a little bit more specific, we are not executing the SQL. This is a SQL script meant to be run by the one who installs KubeArchive.

Yes we were on the same page here but I wasn't very clear so appreaciated the puntualization

I think this is incorrect: the one that needs to apply the DDL should be the KubeArchive Database User.

No, this is incorrect.  All the statements in the DDL file should be executed by a database administrator.  This user should have all the permissions.

As I have been doing some tests around this, I will pick this issue and propose a PR so we could discuss the changes over there

I am going to propose a radical rewrite of this SQL.
First, I don't see any advantage to having our own schema. It just adds complexity. We can just stay in the public schema.
We are trying to write SQL when there's no need for it, and it's causing problems. We should use pg_dump to generate this script.  That means the database is created in postgres as we want it, then we can dump it and have a perfectly generated script that will recreate it.  It's much less error prone.
I have taken our script, created the database, and then run pg_dump to generate the script. Here's the command:
pg_dump -U postgres -d kubearchive -C -c --if-exists -s

This created this script:
--
-- PostgreSQL database dump
--

-- Dumped from database version 16.1
-- Dumped by pg_dump version 16.1

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;

DROP DATABASE IF EXISTS kubearchive;

DROP ROLE IF EXISTS kubearchive;
CREATE USER kubearchive WITH ENCRYPTED PASSWORD 'P0stgr3sdbP@ssword';
--
-- Name: kubearchive; Type: DATABASE; Schema: -; Owner: kubearchive
--

CREATE DATABASE kubearchive WITH TEMPLATE = template0 ENCODING = 'UTF8' LOCALE_PROVIDER = libc LOCALE = 'en_US.UTF-8';

ALTER DATABASE kubearchive OWNER TO kubearchive;

\connect kubearchive

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;

--
-- Name: trigger_set_timestamp(); Type: FUNCTION; Schema: public; Owner: kubearchive
--

CREATE FUNCTION public.trigger_set_timestamp() RETURNS trigger
    LANGUAGE plpgsql
    AS $$
BEGIN
	  NEW.updated_at = NOW();
RETURN NEW;
END;
	$$;

ALTER FUNCTION public.trigger_set_timestamp() OWNER TO kubearchive;

SET default_tablespace = '';

SET default_table_access_method = heap;

--
-- Name: resource; Type: TABLE; Schema: public; Owner: kubearchive
--

CREATE TABLE public.resource (
    uuid uuid NOT NULL,
    api_version character varying NOT NULL,
    kind character varying NOT NULL,
    name character varying NOT NULL,
    namespace character varying NOT NULL,
    resource_version character varying,
    created_at timestamp without time zone DEFAULT now() NOT NULL,
    updated_at timestamp without time zone DEFAULT now() NOT NULL,
    cluster_deleted_ts timestamp without time zone,
    data jsonb NOT NULL
);

ALTER TABLE public.resource OWNER TO kubearchive;

--
-- Name: resource resource_pkey; Type: CONSTRAINT; Schema: public; Owner: kubearchive
--

ALTER TABLE ONLY public.resource
    ADD CONSTRAINT resource_pkey PRIMARY KEY (uuid);

--
-- Name: resource set_timestamp; Type: TRIGGER; Schema: public; Owner: kubearchive
--

CREATE TRIGGER set_timestamp BEFORE UPDATE ON public.resource FOR EACH ROW EXECUTE FUNCTION public.trigger_set_timestamp();

--
-- PostgreSQL database dump complete
--

The only think I added were the two command to DROP and CREATE the user after the database was dropped.
I think this is much cleaner and we should use this method going forward.
Another advantage is that you can just keep re-running this script over and over.  Since it drops everything first, everything gets recreated fresh.

This created this script:

I personally prefer having less boilerplate, shorter DDL that we know what is doing, but I guess that is a matter of preference and maybe the rest prefer having this autogenerated DDL.

Another advantage is that you can just keep re-running this script over and over. Since it drops everything first, everything gets recreated fresh.

I don't like this. Say that you already have a running version of kubearchive, and then, new version releases with an updated DDL file.
I don't think that we want to DROP the database, I think it's better to just create it if it isn't there.
I know that for that we should go through a different path regarding migrations, but for some changes (like adding a trigger) migration isn't needed and just rerunning the DDL could nicely work.
Also, I've tested it and the current DDL can be rerun again and again without failing.

I personally prefer having less boilerplate, shorter DDL that we know what is doing, but I guess that is a matter of preference and maybe the rest prefer having this autogenerated DDL.

Look at the time that has just been spent on errors in this file.  It's a waste, and totally unnecessary since we can have it created for us.
Can you really not read this file and understand what it is doing?  All the same commands are in there.

Say that you already have a running version of kubearchive, and then, new version releases with an updated DDL file.

In that case I wouldn't apply this file, nor the existing one.  That's a migration which is different.

I don't think that we want to DROP the database, I think it's better to just create it if it isn't there.

But what if the table schema has changed?  You won't get those changes.

Also, I've tested it and the current DDL can be rerun again and again without failing.

I believe you can do this if you run it when you are connected to the right database.  But you have to be connected to it, or your table will be created in a database that you don't expect or want.
And I don't believe this is true. There is no check that the table exists, and if you try to create it when it already exists you will get an error.

I just ran the existing DDL script twice:
Password for user postgres:
CREATE TABLE
CREATE FUNCTION
CREATE TRIGGER
ALTER TABLE
GRANT
ALTER FUNCTION
GRANT
GRANT
[gallen@gallen-thinkpadp1gen5 kubearchive] (upstream-main)$ psql -U postgres < database/ddl-resource.sql
Password for user postgres:
NOTICE:  relation "resource" already exists, skipping
CREATE TABLE
CREATE FUNCTION
ERROR:  trigger "set_timestamp" for relation "resource" already exists
ALTER TABLE
GRANT
ALTER FUNCTION
GRANT
GRANT
[gallen@gallen-thinkpadp1gen5 kubearchive] (upstream-main)$

I guess it succeeed, but it does say ERROR.
And to further test, I added a new column to the resource table and ran it again. The table creation really was skipped, and afterward my new column wasn't there.

Look at the time that has just been spent on errors in this file. It's a waste, and totally unnecessary since we can have it created for us.

I don't think that there is that much time, I think that we have been spending time on thinking how the usability of the database would be, what should we do and don't, how should we provide it for testing and development... but specifically to that file, I don't think that much.

Can you really not read this file and understand what it is doing? All the same commands are in there.

I understand it yes, but there are more variables in there that I think we don't need, it's not a big deal and that's why I say that if the rest think that they prefer the autogenerated that's ok.

And to further test, I added a new column to the resource table and ran it again. The table creation really was skipped, and afterward my new column wasn't there.

Yes, that's why I said this  before:

I know that for that we should go through a different path regarding migrations, but for some changes (like adding a trigger) migration isn't needed and just rerunning the DDL could nicely work.

adding a column is a clear example of needing migrations, something that I think we should address separately, which you also mentioned in here:

In that case I wouldn't apply this file, nor the existing one. That's a migration which is different.

and I agree. I am refering to things like adding a new resource like a function or a trigger, or an index.

I guess it succeeed, but it does say ERROR.

It succeeded yes, if the ERROR annoys you it's something we can address, but the script is doing what we expect
I think we can just defer this discussion to the Monday meeting

We are trying to write SQL when there's no need for it, and it's causing problems. We should use pg_dump to generate this script. That means the database is created in postgres as we want it, then we can dump it and have a perfectly generated script that will recreate it. It's much less error prone.

I agree with this. @ggallen the current ddl-resource.sql was created using the DLL tool from DBeaver, that tool set less default values than pg_dump. I'm ok, if we agreed, to use pg_dump.

I don't think that there is that much time

https://github.com/kubearchive/kubearchive/issues/384
https://github.com/kubearchive/kubearchive/issues/381
https://github.com/kubearchive/kubearchive/issues/85
https://github.com/kubearchive/kubearchive/pull/393
https://github.com/kubearchive/kubearchive/pull/391

Four of these were created within the last 10 hours.  All deal, either directly or indirectly, with problems in the DDL file.
And it's not just one person, this has been a multi-person discussion. And then there will be reviews on the PRs, which again involve multiple people. Then comments and re-reviews.
So I agree in one sense - it's not a lot of time in the grand scheme of things. But it is time, and it's more than likely to reoccur in the future, multiple times.

the current ddl-resource.sql was created using the DLL tool from DBeaver

@mafh314 , thanks. I did not realize thatt, nd I doubt @maruiz93 did either.  But we've been modifying the file manually (see the PRs in the previous comment), which causes other problems. If we make changes manually, then we can never use the regenerated version again, unless we then go back an apply all the changes.  That's a nightmare.
I would opt for pg_dump just because it's from postgres and should always work.  As for the other pg_dump settings, I think it's good to have those in there.  It insures that the database created for KubeArchive is always the same.
And yes, I know I am proposing that this file be edited to add the CREATE USER command. That's just to include those two lines and have everything in one file.  It should always be the same, it it's the only manual change that should be made.  We could create a script that would insert them if that makes life easier.

@ggallen is correct I wasn't aware that the current DDL file were created through an automation, so I will close the current PR and leave the issue unassigned again.
@mafh314 or @ggallen feel free to pick it as you were already involved in these automation.
For the CREATE USER part, if you want to keep it reusable (the IF NOT EXISTS part), feel free to take a look at that part of my current PR.

Four of these were created within the last 10 hours

You are mixing issues and their PRs in that list, that's a little unfair.
There are only two PRs, and one of them is a bug of not adding the database in one of the resources that made the resource unreachable if not executed from it, a one-word fix... I think this discussion is the only one that has drain a little time from us.
The issue that doesn't have a PR on it, is not directly affecting the DDL, just how to apply it, so the automation doesn't affect it.
Anyway, there is no need to keep on this discussion, as I said before, I tend to avoid autogenerated code because there usually are more things than needed but it's not that much the difference and we were already using an automation so I'm ok with it.
Regarding doing DROP/CREATE instead of the equivalent of CREATE IF NOT EXISTS, I prefer the conservative approach, but it will probably be ok as for migrations we won't be reapplying the DDL.
Related to use the public schema, I haven't mentioned anything earlier but that's because I'm ok with that change, I actually don't have any argument against using public schema and in fact I don't really get the advantage of having different schemas in the database, I guess that I'm not used to work with them.

This issue was addressed in https://github.com/kubearchive/kubearchive/pull/417


api: force migrate v3alpha -> v3

Also adjust wip status for some things that are known to be used in
production.
Fixes https://github.com/envoyproxy/envoy/issues/17920
Risk Level: High (for code, low, but there will be unhappy v3alpha users surely.)
Testing: Existing tests
Docs Changes: N/A
Release Notes: Added
Platform Specific Features: N/A

cc @envoyproxy/api-shepherds

I think risk should be "high"

Updated

/lgtm api


Verify compatibility with Jekyll 4.0.0

Apparently there's a new version of jekyll coming out -
https://jekyllrb.com/news/2019/03/18/jekyll-4-0-0-pre-alpha1-released/
Will need to try it out, with j-p-t!

Hi @rbuchberger,
Any update on this ? Would love to use this plugin alongside Jekyll 4 :)
BR,
Kyle

Hey!
I don't know that it doesn't work. I haven't tested at all, you're welcome to do so and report back!
I'm super busy with other projects. I feel bad that JPT is a bit neglected lately, but it will probably be another month or two becore I can put real time into it.

Hey! Thanks for the reply! I might have time to test shortly and will report back if I get round to it :) :100:


Update autofill to 6.5.1

Task/Issue URL: https://app.asana.com/0/1204538113123465/1204538113123465
Autofill Release: https://github.com/duckduckgo/duckduckgo-autofill/releases/tag/6.5.1
Description
Updates Autofill to version 6.5.1.
Autofill 6.5.1 release notes
What's Changed

Disable pixel for all platforms but extension by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/309
Fix release script for BSK by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/310

Included in 6.5.0:

Improve debugging by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/293
Reduce the calls on check position when there are many mutations by @alistairjcbrown in https://github.com/duckduckgo/duckduckgo-autofill/pull/288
Window release fetch tags before checkout by @alistairjcbrown in https://github.com/duckduckgo/duckduckgo-autofill/pull/296
Autofill compare generated test suites by @greyivy in https://github.com/duckduckgo/duckduckgo-autofill/pull/283
Update release scripts with latest Apple tooling by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/299
Add temporary incontext_eligible pixel by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/304
Fix double-click issue by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/306
Fix a whole bunch of existing failing test cases by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/308

Full Changelog: https://github.com/duckduckgo/duckduckgo-autofill/compare/6.5.0...6.5.1
Steps to test
This release has been tested during autofill development. For smoke test steps see this task.

Task/Issue URL: https://app.asana.com/0/1204538113123465/1204538113123465
Autofill Release: https://github.com/duckduckgo/duckduckgo-autofill/releases/tag/6.5.1
Description
Updates Autofill to version 6.5.1.


update style-loader to 0.21.0

What kind of change does this PR introduce?
Updates the style-loader package to the latest version (0.21.0).
Did you add tests for your changes?
n/a
Summary
I'd like to be able to target an iframe with the insertInto option of style-loader (using preact.config.js). This allows your styles to be inserted into the iframe's head (see https://github.com/webpack-contrib/style-loader/pull/248). The current version of style-loader used by preact-cli (0.18.2) doesn't have this feature - it was introduced in 0.19.0.
The reason I need this is that I'm building an embeddable Preact widget that'll be rendered into the body of a sourceless iframe, and so that's where I'd like my styles to be inserted.
Does this PR introduce a breaking change?
It shouldn't - I couldn't find any breaking changes in the style-loader changelog.

@shanecav Tests failing. Maybe try merging in latest master?

We're going to be upgrading this by default in the next branch. Closing since 3.0 is soon. :)


Support Chai 3

This was causing a lot of install warnings/errors.
Fixes #18

Any status on accepting this?

+1


Radar Chart circular border

Sorry for the silly question, But I couldn't find color parameter for the circular border around the whole radar chart
I'm trying to make it transparent color, or find a way to remove it

@payam-zahedi Can you check it out?

@Mohdx you can use the radarBorderData field in RadarChartData chart class.
The sample code for that would look something like this:
RadarChartData(
                dataSets: showingDataSets(),
                radarBorderData: const BorderSide(color: Colors.transparent),
                ...
            ),

@Mohdx you can use the radarBorderData field in RadarChartData chart class.
The sample code for that would look something like this:
RadarChartData(
                dataSets: showingDataSets(),
                radarBorderData: const BorderSide(color: Colors.transparent),
                ...
            ),

Yeah its there  radarBorderData: const BorderSide(color: Colors.transparent), . But the border still visible, not transparent 👀

you are right @Mohdx, I checked out the source code and found that we had some changes in the drawing radar chart.
@imaNNeoFighT  I will create a PR for this issue ASAP.

Any update on when this will get merged?

@Mohdx Feel free to close this issue

Thank you all. Appreciate it


Add support for Space and Plus keywords

It seems that the eventToHotkeyString function returns " " for a spacebar keystroke, as described in the key values docs. But the expandHotkeyToEdges function also uses the space character to split hotkey combinations.
So how might one define a single hotkey or hotkey combination containing a space?
We might consider a slight deviation from the key values docs in this instance to add the Space shorthand as an alias for " " when defining a hotkey via the data-hotkey attribute or install function. Thank you! 💛

Maybe we could use "Space" as a way to distinguish space as a separator of key sequences (" "), and the literal space key as a shortcut ("Space").
So for example the shortcut key to open Spotlight / Alfred / Raycast on a Mac would be "Meta+Space".

This actually relates to https://github.com/github/hotkey/issues/54#issuecomment-992997472 where I suggest we match on event.code rather than event.key. The event.key for space is " ": the event.code is "Space", so making that breaking change would also resolve this issue.
If we don't make that change, then this would require some special code.

Updated this issue to also cover Plus (because Mod++ isn't great).

Typo prevented this from properly closing when it was merged.


[WIKI] Changed function of client.api()

I don't know where to write this here or Forum.
You should note on the new doc the client.api returns a json object now.
Did take me some minutes to figure that out, why the api is return a json

Thanks for pointing that out @keving91, I updated the new documentation :+1:


confirmation windows works

Added confirmation modal windows for edit/delete actions and guards +confirmation windows when the user wants to leave the creation-pages (application, workshops, children)


PHPCS 3.3.2: add XSD schema to the rulesets

Dependency Version
When the PHP_CodeSniffer dependency is at least version 3.3.2 (not yet released at the time of writing), then take the actions below.
Action checklist

[ ] Add the XSD schema attributes to the various rulesets, like so:<ruleset name="My Project"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/squizlabs/PHP_CodeSniffer/master/phpcs.xsd">

Note: we can not use a relative schema location like ../vendor/squizlabs/php_codesniffer/phpcs.xsd as people are not required to install WPCS with Composer, let alone for it to be a project-based install, so we cannot rely on the xsd to be available in that location.
[ ] Validate the current rulesets against the schema and update them to comply if necessary.
[ ] Verify whether the Travis XML validation checks will take the newly added schema into account and if not, adjust them so they will.

Rationale:
An XSD schema definition file defines the expected format of an XML file. It defines the elements and attributes which can be used in the XML file and in which order those can be used.
Adding an XSD schema reference to an XML file will allow for stricter validation of the file to ensure it is valid for the purpose for which it is intended to be used, in this case: that it is a valid ruleset for use with PHPCS.
References:

The XSD schema file was added in PHPCS 3.2.0 via PR https://github.com/squizlabs/PHP_CodeSniffer/pull/1433
The new array format for properties was introduced in PHPCS 3.3.0 / PR https://github.com/squizlabs/PHP_CodeSniffer/pull/1665
The XSD was updated to allow for the new array format in PHPCS 3.3.2 via https://github.com/squizlabs/PHP_CodeSniffer/issues/2151

For an example of how to implement this: https://github.com/squizlabs/PHP_CodeSniffer/pull/2187


PartialEq for Rng

I would like to include an Rng inside a struct which derives PartialEq, but it's not implemented now.  Could that be added, plus other standard helpful traits?

I would accept a PR to implement PartialEq and Eq for Rng.


Title: Adding Background Changer Project

Is your feature request related to a problem? Please describe.
A simple background color changer which will help developers to pick the colors for the projects.
Describe the solution you'd like.
I will provide the simple solution with simple UI user will be able to pick the color and his color code will be available to user for further use.
Describe alternatives you've considered.
Simple clean UI which will help user to pick the colors for their pojects.
Add any other context or screenshots about the feature request here.
Screenshot of working model :

@Pranav0606 Thank you for providing your insight but it is not required as of now


Enable documentation for v1 and v2

We need to set up our documentation so that it is easy for users to discover v1 and v2 of bUnit.

Seems like v3 of docfx could help us out: https://github.com/dotnet/docfx/blob/v3/docs/designs/conceptual-versioning.md
But: that would also mean we would have to move the docs into their own repository to make that work (like dotnet does). Currently the cool version toggle one can find on the MS sites, is closed source and will come with v3.
The big problem: No one knows when v3 is coming. (See https://github.com/dotnet/docfx/issues/2299)

There is a way of making that work at least for the articles. Nodatime does the same: https://github.dev/nodatime/nodatime.org/build/docfx/docfx-web.json
So the general idea might be:

Have a new repository that is kind of a meta-repository for the docs
It has main and v2 (and later main and v1) as git submodules
We build v1 and v2 normally like today to get all the documents under _site
We add a new docfx.json that does the mapping of versions. (see nodatime.org stuff)
We use the newly generated stuff to push our docs to bunit.dev.


Fix Layout in Header/Footer

[ ] Font Size Website
[ ] margins left/right of header Footer
[ ] align Logo/Spenden
[ ] align copyright/Datenschutz
[ ] Dropdown menu - linebreaks & animation
[ ] Charts on city page overlap with footer
[ ] background color

@kleins05 Please add if anything's missing.
Not sure what you meant with "margins left/right of header Footer". Will take a closer look today.

Could not reproduce "Charts on city page overlap with footer" any longer. Could have been a sideeffect of the menu isssue.


Only amd64 container images

Would like to have a multi-arch container image for all the architectures available so I can use the container with the same behavior in different architectures.

Created PR #86


Create howto-use-mermaid-graphic-tool.md

Creation of an howto to use the mermaid graphic tool

LGTM, asking @alv67 to have a look as well.


Use resolve_manifest_path from spin-common

Depends on https://github.com/fermyon/spin/pull/1584

cc/ @kate-goldenring ready for review now!


Add -Werror mode and use it for testing

Fix #417

@JohanMabille this one is ready for review!

Not really because of the else part of the #ifdef

Ha indeed, I didn't see it in the diff since it has not changed.


Drop-down Inputs on I/O Tab

Hi JT,
Per your request I've broken out some of my questions/issues into separate reports.
There are only 5 active drop-down Inputs on the I/O tab (0-4).
Inputs 5-15 and all of 16-31 are grayed out and I cannot enter values into them.

The firmware sets how many I/O is available to use. Additional I/O will have to be freed up by reducing the number of step/dir, encoder or PWM functions. This also is a work in progress and would need to be somehow tied to the GPIO tab.

Do the inputs on the I/O tab just coordinate with the Pins tab in the order listed in the firmware?  Any way that they can match?


Adding support for SSL dual mode (#712)

Adding SSL dual mode support for SSLOnly

(cherry picked from commit 27f33fb)
Co-authored-by: Vengadanathan Srinivasan<EMAIL_ADDRESS>By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It needs to be part of the commit message, not PR description.


Transfer "dies" for no reason

I shared a file on instant.io, then tried to transfer in my client using webtorrent-hybrid in nodejs.
I was the only one sharing the file and, my client was the only one downloading it.
For some reason, the upload "stopped" after 2 mb transfered, and the transfer didn't "move on" anymore.
I reloaded the page in instant.io, selected the file again and the transfer ran for more 15mb and stopped again. The connection simply got "Lost", I'm now trying to find why this is happening.
I tried to enable debug to check where the problem is, but I didn't locate..
How can I try to dectect where the problem is?
PS.: If there's more than 1 seeder, this doesn't happen, only when there's one seeder.
(sorry, bad English)

That's weird. No idea why that would be happening. If you get any more info about how to reliably reproduce this, please share!

If you can, run webtorrent-hybrid with the environment set to DEBUG=*,-bittorrent-dht and run it until the disconnect happens, then post the log here.

@Stiveknx Was the seeder in node or in the browser?
If the seeder was in node, I think that this may be caused by https://github.com/feross/webtorrent/issues/375

Seeder was runing in browser (directly from instant.io).

@Stiveknx Can you try this out again on https://instant.io?
If you have a flaky connection to the internet, the webrtc conncections to peers can be lost and would need to be re-established. I just pushed an improvement to the tracker module, so we now try to look for new peers every 30 seconds on the already-established WebSocket connection to the tracker.
This should make things better. Please test it out and let me know if things are better.

Hi.
So, I did a quick test and apparently the problem has been solved.
I shared the same file I did before and the file started and downloaded without stop.
I'll mark it as closed, but later I'll try to test with more and larger files!
Ps.: Thanks for the amazing project

Awesome!

Opening it again ..
sometimes, when I'm almosting finishing the download, it stops when 20 pieces or more are pending ...
Check  the debug:
http://pastebin.com/raw.php?i=jcTNZb5D
I've notice that, after "webtorrent:torrent error getting piece", if I have too much of these errors, I got stuck in last pieces.
When the transfer finishes successfully, I don't see much of there messages ...

Here's another debug:
http://pastebin.com/raw.php?i=Q6s515Rf
This time, I was seding from my computer to another one ...
I was the only seeder.

This issue is super old. I'm going to close and assume that it's fixed now. If this is not the case, feel free to open a new issue.


Vitest Failed to resolve entry for package "@azure/communication-react"

Describe the bug; what happened?
I updated the "@azure/communication-react" to version 1.21.0. Before, tests worked fine with version 1.18.1. However, I also updated Vite to v6 and Vitest to 2.1.6.
When trying to run the tests with Vitest, I get this error:
7:24:47 AM [vite] (client) Pre-transform error: Failed to resolve entry for package "@azure/communication-react". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "@azure/communication-react" package
  Plugin: vite:import-analysis
  File: /Users/trycycle-dercilio/repos.nosync/elm/src/hooks/useCreateChatAdapter.ts:5:85
  1  |  import { useEffect, useMemo, useState } from "react";
  2  |  import { createAzureCommunicationChatAdapter, fromFlatCommunicationIdentifier } from "@azure/communication-react";
     |                                                                                ^

The build and app works fine.
I couldn't figure out how to solve it. Could it be a problem with how the package package.json is configured?
I checked the package in this tool, and it suggests some changes. Could it help?
https://publint.dev/<EMAIL_ADDRESS>However, it could also be some configuration with Vitest and Vite to fix it. Could you guys give some advice about that?
What are the steps to reproduce the issue?
Probably a new project with Vite, Vitest and @azure/communication-react to test it.
What behavior did you expect?
To resolve the import properly
If applicable, provide screenshots:
In what environment did you see the issue?
"@azure/communication-chat": "^1.5.4",
"@azure/communication-common": "^2.3.1",
"@azure/communication-react": "^1.21.0",
"react": "^18.3.1",
"typescript": "^5.7.2",
"vite": "^6.0.1",
"vitest": "^2.1.6"

OS & Device: macOS 15.1.1
Node 22

Is there any additional information?

I could make it work with this Vitest config pointing to cjs.
    test: {
      globals: true,
      environment: 'jsdom',
      setupFiles: 'src/setupTests.ts',
      alias: {
        '@azure/communication-react': path.resolve(
          __dirname,
<EMAIL_ADDRESS>        ),
      },
    },
  });

Hi @DercilioFontes, thanks for filing this issue. I will have a discussion with my team about this and let you know.

@DercilioFontes  Could you share your typescript config? You need to be using certain resolver to pick up the entry points. Just to note, VItest seems to work better with node.js environment

Hi @mgamis-msft
Sure.

tsconfig.json

{
  "compilerOptions": {
    "target": "ES2022",
    "lib": ["DOM", "DOM.Iterable", "ESNext"],
    "module": "ESNext",
    "skipLibCheck": true,
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "strict": true,
    "noUnusedLocals": true,
    "noFallthroughCasesInSwitch": true,
    "sourceMap": true,
    "types": ["vitest/globals"]
  },
  "include": ["src", "types", "types/i18next.d.ts"],
  "references": [{ "path": "./tsconfig.node.json" }]
}

tsconfig.node.json

{
  "compilerOptions": {
    "composite": true,
    "skipLibCheck": true,
    "module": "ESNext",
    "moduleResolution": "bundler",
    "allowSyntheticDefaultImports": true
  },
  "include": ["vite.config.ts"]
}

Awesome @DercilioFontes! Thank you for sharing your fix.


fix: forallMetaTelescope shouldn't reduce after maxMVars

At least it doesn't seem like it should. The following test illustrates the issue: https://github.com/dselsam/lean4/blob/forallMetaTelescope/tests/lean/forallMetaTelescopeBounded.lean Without this PR, the resultType will have unfolded Set, exposing an arrow. With the PR, it simply prints Set ?_uniq.1. Context: the old behavior was complicating isDefEq queries inside pp.analyze: what I would have expected were trivial Set ?x =?= Set x queries became not-quite-as-trivial ?x -> Prop =?= Set x queries.

Thanks for finding this problem, and suggesting a fix and test. I will submit a fix soon.


Dynamic font sizing no longer truly dynamic

Describe the bug
Since the implementation of custom schema, and the change to non-react uiRender files, we have lost the benefit of optimized React rendered components.
As a result, schema rendering now replaces the entire content when re-rendered, and to avoid how heavy this is we are now only re-rendering with an onChange event for when the editing has finished.
This is a regression in user experience for the text schema, especially when using dynamic text sizing. Previously this would adjust as you type to fit the available space (as per Google Docs, etc):
https://github.com/pdfme/pdfme/assets/7068515/4614533d-9552-4fd9-b0aa-31b727fd1c28
This no longer happens, the sizing of text is only applied once editing has finished and you leave the editor window:
https://github.com/pdfme/pdfme/assets/7068515/970d5705-804b-4157-82ec-26186e936414
I have tried changing the event listener to be onKeyPress, but without the use of React this is far too janky because it rerenders and calculates every aspect of the component on every keypress. There were delays of up to 20 seconds to update the display when I typed for a few seconds with lots of text. There were also issues with focus() in doing this if you are typing in the middle of the textbox it will move focus to the end.
To Reproduce
Type into a text schema
Expected behavior
Ideally, we would be able to leverage React to support some dynamic updates to the visual display of the schema.
Your Environment
- pdfme package: @pdfme/ui
- pdfme version: latest main
- Operating system: OSX
- Node.js version or Browser name & version: Chrome latest

Your Error Log
-

Additional context
I don't know if this is easy to resolve.
Would it be possible to allow React components as an alternative to the basic implementations we have of the uiRender file?
It would be shame to lose the user experience that we used to have.

Hey @peteward ,

Would it be possible to allow React components as an alternative to the basic implementations we have of the uiRender file?

I don't think it's a good idea to allow external React components. We would need to ensure that the React version used by pdfme matches the user's runtime, which complicates things. I believe it's simpler to have it written in vanilla JavaScript.
Couldn't we revert to the original UX by re-executing calculateDynamicFontSize within the callback of onChange mentioned below?
https://github.com/pdfme/pdfme/blob/67439652affbdd70b187a4583283c2cb3bb8b311/packages/schemas/src/text/uiRender.ts#L143

Fix Dynamic font sizing no longer truly dynamic #357
ref: https://github.com/pdfme/pdfme/pull/359

fixed by https://github.com/pdfme/pdfme/pull/359


Do not call "bash -c" unnecessarily as entry points

Closes: OSPRH-680

@booxter @karelyatin @slawqo I think this patch is ready for review, thanks in advance.

@ralonsoh LGTM for the changes done here, but the linked but also mentions about bash usage in ovncontroller but i don't see any changes/comment for that either in PR or in Jira and also the comment says Closes Jira.

@ralonsoh LGTM for the changes done here, but the linked but also mentions about bash usage in ovncontroller but i don't see any changes/comment for that either in PR or in Jira and also the comment says Closes Jira.

@karelyatin when the ovn-controller command [1] is executed outside the bash call, it always returns an error with the socket file. Also when dumb-init is used. The directory /run/openvswitch exists. E.g.:
ospng@r7rhoso:~/ovn-operator$ oc logs pods/$p -n kuttl3
[dumb-init] ovn-controller --pidfile unix:/run/openvswitch/db.sock: No such file or directory

[1]https://github.com/openstack-k8s-operators/ovn-operator/blob/9bdb826b7218c51a029b8c213850022a70cea4fd/pkg/ovncontroller/daemonset.go#L39C4-L39C18

@ralonsoh LGTM for the changes done here, but the linked but also mentions about bash usage in ovncontroller but i don't see any changes/comment for that either in PR or in Jira and also the comment says Closes Jira.

@karelyatin when the ovn-controller command [1] is executed outside the bash call, it always returns an error with the socket file. Also when dumb-init is used. The directory /run/openvswitch exists. E.g.:
ospng@r7rhoso:~/ovn-operator$ oc logs pods/$p -n kuttl3
[dumb-init] ovn-controller --pidfile unix:/run/openvswitch/db.sock: No such file or directory

[1]https://github.com/openstack-k8s-operators/ovn-operator/blob/9bdb826b7218c51a029b8c213850022a70cea4fd/pkg/ovncontroller/daemonset.go#L39C4-L39C18

@ralonsoh but dumb-init shouldn't be needed just for this, i did tried locally removing bash and seems to work.
diff --git a/pkg/ovncontroller/daemonset.go b/pkg/ovncontroller/daemonset.go
index 09ce8e3..0b5491d 100644
--- a/pkg/ovncontroller/daemonset.go
+++ b/pkg/ovncontroller/daemonset.go
@@ -14,7 +14,6 @@ package ovncontroller
import (
"fmt"

  "strings"

  "github.com/openstack-k8s-operators/lib-common/modules/common/env"
  "github.com/openstack-k8s-operators/lib-common/modules/common/tls"

@@ -35,8 +34,8 @@ func CreateOVNDaemonSet(
volumes := GetOVNControllerVolumes(instance.Name, instance.Namespace)
mounts := GetOVNControllerVolumeMounts()

  args := []string{

          "ovn-controller --pidfile unix:/run/openvswitch/db.sock",

  cmd := []string{

          "ovn-controller", "--pidfile", "unix:/run/openvswitch/db.sock",
  }

  // add OVN dbs cert and CA

@@ -56,7 +55,7 @@ func CreateOVNDaemonSet(
mounts = append(mounts, instance.Spec.TLS.CreateVolumeMounts(nil)...)
}

          args = append(args, []string{

          cmd = append(cmd, []string{
                  fmt.Sprintf("--certificate=%s", ovn_common.OVNDbCertPath),
                  fmt.Sprintf("--private-key=%s", ovn_common.OVNDbKeyPath),
                  fmt.Sprintf("--ca-cert=%s", ovn_common.OVNDbCaCertPath),

@@ -72,8 +71,8 @@ func CreateOVNDaemonSet(
containers := []corev1.Container{
{
Name:    "ovn-controller",

                  Command: []string{"/bin/bash", "-c"},

                  Args:    []string{strings.Join(args, " ")},

                  Command: cmd,

                  //Args:    []string{strings.Join(cmd, " ")},
                  Lifecycle: &corev1.Lifecycle{
                          PreStop: &corev1.LifecycleHandler{
                                  Exec: &corev1.ExecAction{

@ralonsoh but dumb-init shouldn't be needed just for this, i did tried locally removing bash and seems to work. https://paste.opendev.org/show/bcDn2u4DRCaMbNqnJvfk/

I did something similar some PS ago [1] and it wasn't working. The problem was to divide the command string... Thanks for your help.
[1]https://github.com/openstack-k8s-operators/ovn-operator/commit/40f649e0d2ea6070e1901301cfc9b168fcf5c2da#diff-853730e1a0e56623824bb603929544f54d838010a75b27a62b285ae738064744

/retest-required

Ok, I think now is ready (again).

/lgtm Thanks looks good now

/approve

Not sure why it didn't create lgtm label before while Yatin put /lgtm in the comment. But it's all good now, should merge now.

Not sure why it didn't create lgtm label before while Yatin put /lgtm in the comment. But it's all good now, should merge now.

I recall seeing something similar in past where bot didn't add the label. Readding helped, but don't know about root cause. thx for noticing it.

/retest-required

         --- FAIL: kuttl/harness/ovn_db_delete (234.92s)

It may be worth understanding why this failed before merging. It may be not related to this patch, but if so, it would be nice to understand what other issue triggers it, and to make sure there's a Jira issue for this.

Yes it's unrelated, As seen in [1] pod-0 got deleted first, pod-1/pod-2 stuck Terminating as waiting for cluster leave. We have a ticket for this [2] and that have a related FDP issue
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_ovn-operator/249/pull-ci-openstack-k8s-operators-ovn-operator-main-ovn-operator-build-deploy-kuttl/1839362702133170176/artifacts/ovn-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-3d1f620ae3617fbd6371f55aa948b34e9daf31a461d3c557cf1a7c2db38d0385/namespaces/ovn-kuttl-tests/all_resources.log
[2] https://issues.redhat.com/browse/OSPRH-7626

/test ovn-operator-build-deploy-kuttl

         --- FAIL: kuttl/harness/ovn_db_delete (234.92s)

It may be worth understanding why this failed before merging. It may be not related to this patch, but if so, it would be nice to understand what other issue triggers it, and to make sure there's a Jira issue for this.

Yes it's unrelated, As seen in [1] pod-0 got deleted first, pod-1/pod-2 stuck Terminating as waiting for cluster leave. We have a ticket for this [2] and that have a related FDP issue
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_ovn-operator/249/pull-ci-openstack-k8s-operators-ovn-operator-main-ovn-operator-build-deploy-kuttl/1839362702133170176/artifacts/ovn-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-3d1f620ae3617fbd6371f55aa948b34e9daf31a461d3c557cf1a7c2db38d0385/namespaces/ovn-kuttl-tests/all_resources.log [2] https://issues.redhat.com/browse/OSPRH-7626

pushed a workaround https://github.com/openstack-k8s-operators/ovn-operator/pull/356


[MINOR] Remove unused versions from gradle.properties

What changes were proposed in this pull request?
This PR aims to remove unused versions from gradle.properties.
Why are the changes needed?
To clean up the misleading unused versions. We can see that there is no usage like the following.
$ git grep commonsLang3Version
gradle.properties:commonsLang3Version=3.16.0

$ git grep commonsIOVersion
gradle.properties:commonsIOVersion=2.16.1

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @viirya

Thank you, @viirya . Merged to main.


I-Clicked-On-New-Issue

I am using write tab to write this.

seems I had to reopen to comment. now comment  is enabled .

seems I can now close and comment,

reopened.

this to close and comment.

seems I must comment. here.


Can't modify bitwise

Just installed Webmin 1.762 on Debian 8 and I received the error when I open the filemin module.
Error - Perl execution failed
Can't modify bitwise and (&) in scalar assignment at ./filemin-lib.pl line 197, near """;"
Compilation failed in require at /usr/share/webmin/filemin/index.cgi line 5.

Did you install release version or cloned git repository?

Release from Webmin

Oooops, I think they pushed latest git repo to Webmin bundle that contains some not tested commits.
Remove Filemin module through Webmin interface and install latest stable release from here https://github.com/Real-Gecko/filemin/raw/master/distrib/filemin-0.9.5.linux.wbm.gz

When I install the downloaded module into Webmin it works fine.

OK then, I will notify Jamie about that. Hope next release of Webmin will have workable Filemin version.

I was really inattentive and only now noticed that 1.762 is dev release of Webmin. So when it'll come to stable release I think they'll inlcude stable Filemin version there.
Nothing to worry about I think, so I'm closing the issue.


add validations in @armResourceOperations

So in general, we would like to establish a standard in new management typespec that the operations belong to the same resource, should come in one same interface, such as:
interface VirtualMachines
{
	get is ArmResourceRead<VirtualMachine>;
	createOrUpdate is ArmResourceCreateOrUpdate<VirtualMachine>;
}

and we should be trying to avoid this case:
interface VirtualMachines
{
	get is ArmResourceRead<VirtualMachine>;
	createOrUpdate is ArmResourceCreateOrUpdate<VirtualMachineScaleSet>; // this should go to its own interface `VirtualMachineScaleSets`
}

Therefore could we add some validations in the decorator @armResourceOperations(Model) to let it validate if all the operations in the same interface to have the same Resource argument?

I think this might fit better as a linting rule, then we would not require the extra verbiage in the @armResourceOperations decorator.


UI Select scroll to active works wrong for first click

When clicking on select field and active choice is way down it not scrolls completely to it, after closing and opening again it works good.
Workaround: set timeout to _ensureHighlightVisible();

Can you post a reproduction in Plunker?

I found why this happens. when every row height is not equal. For example
some text breaks in some option, then first auto scroll to selected item
not works. When i make text-overflow hack not to break text to another
line, it works ok.
On Monday, 28 March 2016, Wesley Cho<EMAIL_ADDRESS>wrote:

Can you post a reproduction in Plunker?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/ui-select/issues/1290#issuecomment-202219121

--
Pagarbiai Rokas Kučiauskas


Sphinx theme

The default theme is quite horrible. Can we change to a more readable html theme? the "nature" theme is very similar to the numpy/scipy website

sure, I think it is the one by default in readthedocs, but I do agree that
the one of scipy is better. I don't know how it will appear on
arte.readthedocs.org though
Il giorno sab 18 apr 2020 alle ore 10:02 Alfio Puglisi <
<EMAIL_ADDRESS>ha scritto:

The default theme is quite horrible. Can we change to a more readable html
theme? the "nature" theme is very similar to the numpy/scipy website
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArcetriAdaptiveOptics/arte/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB544W4ETIISP733G75GPCDRNFM77ANCNFSM4MLIBSZQ
.

Very nice Nature theme committed in 0df1b4df2147931a306cfa55e91fae516673d26e, much nicer than the old one!! It is rendered correctly on readthedocs as well


Add VxFS magic number, fixes #14847

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>Fixes #14847
@amoalsale   This may can fix your problem.

The vxfs magic number is here http://mirrors.neusoft.edu.cn/rpi-kernel/fs/freevxfs/vxfs.h

LGTM

LGTM

LGTM, thanks @coolljt0725 !


Underline before actual error position

The underline is placed between the beginning of the line and where the error/warning actually begins. See the screenshot:

Running Atom 1.5.3 on Mac OS X 10.11.3
<EMAIL_ADDRESS><EMAIL_ADDRESS>

This is a bug in linter-js-standard, please re-open this issue there :)

Thanks @steelbrain! Will do.


Implement Admin Portal for Educator Verification

This issue proposes the development of an admin portal within our educational website. This portal will allow  administrators to verify the credentials and qualify  of educator's content requesting access to create and manage courses .
Currently, there's no dedicated system to verify educator legitimacy. An admin portal will ensure the quality and credibility of our educational content by verifying educator expertise. Verified educators will also inspire greater trust among learners.

Develop a secure admin portal accessible only to authorized Admin  with appropriate access levels.

Assign this to me i will start working imediately for that @BipulRahi

Working on this, please assign it to me.

can you assign me this issue under gssoc 24.


[release] 2.53.0 Website Updates

Adds 2.53.0 release information to the beam website. DO NOT MERGE until release is approved

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damccorm


Zephyr Integration

All,
The Zephyr RTOS project just has merged a glue logic layer integrating lvgl v5.2 with Zephyr.
The glue logic layer provides:

Configuration of the majority of the lv_conf flags through KConfig
Integration with Zephyr memory management model (kernell, user space & dedicated memory pool)
Integration with Zephyr FS API
Integration with  Zephyr Display API.
This includes a simulation port of Zephyr, with SDL based display driver, that runs on linux
Integration of lvgl log messages into Zephyr log framework

Further a development environment is available as a docker container which can exposes the SDL based simulation display through a VNC server.

@kisvegabor sorry for the delay I would like to take up job on writing a step-by-step guide once zephyr reaches 1.14, this release will be a long term support release and includes a major overhaul of the preferred tooling, as such I would like to wait for this release and write the blog once.
Zephyr PR: https://github.com/zephyrproject-rtos/zephyr/pull/6826#

Awesome! Do you know what is the schedule for 1.14?
I mark the issue as "pinned" to be not closed automatically if no activity.

Full overview of the road map can be found at https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
Currently release is planned for 05-April-19 but feature merge window closes this week so that looks like a good starting point.

I see, thank you!

Any updates?


[WIP] Caching

resolves #11

This PR is stale and got a bit too clever to be taken seriously; should rewrite with something less flashy


SPFx authorization error on calling graph api with graphClient

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version: Edge: Version 92.0.902.78, Chrome: Version 92.0.4515.159
SPFx version: 1.11
Node.js version: 10.16

Describe the bug / error
Starting from today the authorization flow is broken for SPFX web part while calling graph api. I cannot get any graph token with my SPFx web part. The behavior is the same on all platforms, in SP as a web part, in teams as a tab or personal app. The moment I call the graph api with the client ( graphClient.api(xxxx).get() ) in the code, I am seeing the following error messages in the console

At the moment I am seeing this behavior only on my DEV tenant, which is a targeted release tenant.
Steps to reproduce

call graphClient.api(xxxx).get() in the code (ex: https://graph.microsoft.com/v1.0/me)

Expected behavior
I need to be able to call the graph api from a SPFX web part.

We are having the exact same problem.  It started yesterday morning and doesn't affect all users.

Same here!

We are seeing the same thing!

This issue has now been resolved.

@GrahamMcMynn was a bit on the point and indeed - issue has been fixed. Let me elaborate this a bit and thank everyone for providing details on this issue, so that we get the right level of attention on this internally.
Cause of the issue was a regression caused by future development topics related on the auth model, impacting unfortunately also SharePoint Framework auth models (MSAL), impacting specifically scenarios in the Microsoft Teams model. Super unfortunate mistake caused by change done by a developer without realizing the implications within the dependency pipeline.
Thanks everyone for reporting this and for adding additional comments and details on the issue. Issue has been now resolved by rolling back the change, which was impacting this. Persons who caused the issue are award and are now one regression more experienced on avoiding similar issues in future.


Autocomplete doesn't work inside JSX attribute callback function body

Flow version: 0.126.0
Expected behavior
Given the code
// @flow
import React from 'react'

const obj = {foo: ''}

const el =
  <button onClick={() => {
    obj
  }} />

When adding . to the obj, Flow should be able to suggest foo and possibly other properties of the obj object.
Actual behavior
Flow does not provide any suggestions

This happens both with flow autocomplete command and with LSP, which responds to editor's textDocument/completion request with
Received response 'textDocument/completion - (411)' in 7ms.
Result: {
    "isIncomplete": false,
    "items": []
}

flow check works fine. "Go to definition" and other LSP operations work.
If I move the obj. expression outside of the callback, like to line 5 or inside the children of the button element, autocomplete works normally.

Link to Try-Flow or Github repo: https://github.com/noppa/flow-lsp-jsx-callback-issue-repro

It seems that this has been fixed in some recent version. I can no longer repro this in version 0.139.


Not found pages haven't response status code 404

All not existing pages should return a 404 status code on response to allow to search engines and any request to deno.land to manage this errors as 404 errors and not as 200 success. For example, obsolete modules:
Download<EMAIL_ADDRESS>error: Uncaught (in promise) TypeError: An unsupported media type was attempted to be imported as a module.
  Specifier: https://deno.land/deno/postcss-deno-import/deno/mod.js
  MediaType: Unknown

statusCode={404} was removed on PR Custom 404 page 🦕 https://github.com/denoland/deno_website2/pull/1570

#1654

#1654

Created PR for that, fingers crossed 😄

Created PR for that, fingers crossed 😄

Since we switched to fresh, we provide 404 status with the caveat of https://github.com/denoland/dotland/issues/2258


chore(CPlusPlus): add binary power

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

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

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hey, I am new to github. Please let me know if there are some changes to be made in this PR.

Hi @angshudas,
This is duplicated pull request #810


fix(datasets): Fix spark tests

Description
Spark tests are failing randomly. This could be due that spark sessions are not properly closed, so some tests are using the one that do not correspond. See #755
Development notes
I replaced all SparkSession.builder.getOrCreate() calls for the fixture spark session, so we can control which spark session is used. Additionally, in the tear down of the spark session fixtures I added spark._instantiatedContext = None, which allegedly ensure that another spark session is created after (see here).
I am not 100% sure that this is going to fix the issue. Maybe we can rerun the actions a few time just to be sure.
Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

Hey @felipemonroy, first of all, thank you so much for taking this on! 🙏🏾
I re-ran the unit tests and it failed with the same errors for the spark tests https://github.com/kedro-org/kedro-plugins/actions/runs/10023089947/job/27738930808
If you need any help, let us know

Should we add .enableHiveSupport(), like it's done in another fixture?


Refactor repository API

Coverage increased (+0.009%) to 55.961% when pulling eed64ba64544fd7907d339e3a0e3aeeb2b68836d on ywk253100:170509_repo_api into c3c7b540f15771dc6ed633bb125d557a4fffad12 on vmware:master.

Coverage increased (+0.002%) to 55.955% when pulling 06ba7e0de03a791ff6a2253ac943d2be420a14cd on ywk253100:170509_repo_api into c3c7b540f15771dc6ed633bb125d557a4fffad12 on vmware:master.

Coverage increased (+0.04%) to 55.992% when pulling f1f302ec293522bd27c2f7864f6d7dea6e8b6866 on ywk253100:170509_repo_api into c3c7b540f15771dc6ed633bb125d557a4fffad12 on vmware:master.

Coverage increased (+0.04%) to 55.992% when pulling 0cf2ef8a2bc3a80f30461d87d12582d1d04b8604 on ywk253100:170509_repo_api into c3c7b540f15771dc6ed633bb125d557a4fffad12 on vmware:master.