Minor update of run_everything.sh jobsub script + python script to fully automate the job submission

Update run_everything.sh jobsub script to allow for non-integer off-axis positions.
Also added RHC gsimple outdir structure to mirror the one that existed for FHC.

This shouldn't be merged until @CiaranH1997 has given the green light on the first test file of 100 events made:
/pnfs/dune/scratch/users/abooth/Production/ND_CAFMaker/nd_offaxis/v7/testing/CAF/1.75m/00/FHC.2750000.CAF.root
Also added a new python script launch_ndcafmaker_campaign.py which with the help of a configuration file (example launch_ndcafmaker_campaign_220620.cfg also committed) will completely automate an off-axis campaign. It will:

Interpret which horn currents and total POTs you would like at each position you specify.
Split these into bite size chunks of your choosing.
Build the jobsub_submit command automatically.
Query the grid conditions automatically before submitting another batch of jobs to check they are suitable (where suitable is definable by the user).

For example:
$ python launch_ndcafmaker_campaign.py -c launch_ndcafmaker_campaign_220620.cfg --print_only

Produces the following log:
$ cat launch_ndcafmaker_campaign.log
2022-06-20 09:56:47,387 INFO There will be 3 submissions for FHC at 1.75.
2022-06-20 09:56:49,059 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:49,060 INFO That's fine, will go ahead with submission
2022-06-20 09:56:49,060 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 1.75 dk2nu
2022-06-20 09:56:49,837 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:49,837 INFO That's fine, will go ahead with submission
2022-06-20 09:56:49,837 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 1.75 dk2nu
2022-06-20 09:56:50,564 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:50,564 INFO That's fine, will go ahead with submission
2022-06-20 09:56:50,564 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 1.75 dk2nu
2022-06-20 09:56:50,564 INFO There will be 3 submissions for FHC at 5.75.
2022-06-20 09:56:52,027 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:52,027 INFO That's fine, will go ahead with submission
2022-06-20 09:56:52,027 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 5.75 dk2nu
2022-06-20 09:56:52,815 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:52,815 INFO That's fine, will go ahead with submission
2022-06-20 09:56:52,815 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 5.75 dk2nu
2022-06-20 09:56:53,554 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:53,554 INFO That's fine, will go ahead with submission
2022-06-20 09:56:53,554 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 5.75 dk2nu
2022-06-20 09:56:53,554 INFO There will be 3 submissions for FHC at 9.75.
2022-06-20 09:56:54,296 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:54,297 INFO That's fine, will go ahead with submission
2022-06-20 09:56:54,297 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 9.75 dk2nu
2022-06-20 09:56:55,066 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:55,066 INFO That's fine, will go ahead with submission
2022-06-20 09:56:55,066 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 9.75 dk2nu
2022-06-20 09:56:55,866 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:55,867 INFO That's fine, will go ahead with submission
2022-06-20 09:56:55,867 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 9.75 dk2nu
2022-06-20 09:56:55,867 INFO There will be 3 submissions for FHC at 13.75.
2022-06-20 09:56:56,679 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:56,680 INFO That's fine, will go ahead with submission
2022-06-20 09:56:56,680 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 13.75 dk2nu
2022-06-20 09:56:57,466 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:57,466 INFO That's fine, will go ahead with submission
2022-06-20 09:56:57,466 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 13.75 dk2nu
2022-06-20 09:56:58,229 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:58,229 INFO That's fine, will go ahead with submission
2022-06-20 09:56:58,229 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 13.75 dk2nu
2022-06-20 09:56:58,229 INFO There will be 3 submissions for FHC at 17.75.
2022-06-20 09:56:59,005 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:59,005 INFO That's fine, will go ahead with submission
2022-06-20 09:56:59,005 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 17.75 dk2nu
2022-06-20 09:56:59,814 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:56:59,814 INFO That's fine, will go ahead with submission
2022-06-20 09:56:59,815 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 17.75 dk2nu
2022-06-20 09:57:01,583 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:01,583 INFO That's fine, will go ahead with submission
2022-06-20 09:57:01,583 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 17.75 dk2nu
2022-06-20 09:57:01,583 INFO There will be 3 submissions for FHC at 21.75.
2022-06-20 09:57:03,332 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:03,332 INFO That's fine, will go ahead with submission
2022-06-20 09:57:03,332 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 21.75 dk2nu
2022-06-20 09:57:04,278 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:04,278 INFO That's fine, will go ahead with submission
2022-06-20 09:57:04,278 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 21.75 dk2nu
2022-06-20 09:57:05,021 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:05,021 INFO That's fine, will go ahead with submission
2022-06-20 09:57:05,021 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 21.75 dk2nu
2022-06-20 09:57:05,022 INFO There will be 3 submissions for FHC at 25.75.
2022-06-20 09:57:05,756 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:05,757 INFO That's fine, will go ahead with submission
2022-06-20 09:57:05,757 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 25.75 dk2nu
2022-06-20 09:57:06,525 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:06,526 INFO That's fine, will go ahead with submission
2022-06-20 09:57:06,526 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 25.75 dk2nu
2022-06-20 09:57:07,275 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:07,276 INFO That's fine, will go ahead with submission
2022-06-20 09:57:07,276 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 25.75 dk2nu
2022-06-20 09:57:07,276 INFO There will be 3 submissions for FHC at 26.25.
2022-06-20 09:57:08,043 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:08,043 INFO That's fine, will go ahead with submission
2022-06-20 09:57:08,043 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 26.25 dk2nu
2022-06-20 09:57:08,791 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:08,792 INFO That's fine, will go ahead with submission
2022-06-20 09:57:08,792 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 26.25 dk2nu
2022-06-20 09:57:09,549 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:09,549 INFO That's fine, will go ahead with submission
2022-06-20 09:57:09,549 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 26.25 dk2nu
2022-06-20 09:57:09,549 INFO There will be 3 submissions for FHC at 28.5.
2022-06-20 09:57:10,325 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:10,325 INFO That's fine, will go ahead with submission
2022-06-20 09:57:10,326 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 0 1e16 28.5 dk2nu
2022-06-20 09:57:11,104 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:11,104 INFO That's fine, will go ahead with submission
2022-06-20 09:57:11,104 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 10000 1e16 28.5 dk2nu
2022-06-20 09:57:11,869 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:11,869 INFO That's fine, will go ahead with submission
2022-06-20 09:57:11,869 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh FHC 20000 1e16 28.5 dk2nu
2022-06-20 09:57:11,869 INFO There will be 3 submissions for RHC at 1.75.
2022-06-20 09:57:13,530 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:13,530 INFO That's fine, will go ahead with submission
2022-06-20 09:57:13,530 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 1.75 dk2nu
2022-06-20 09:57:14,325 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:14,325 INFO That's fine, will go ahead with submission
2022-06-20 09:57:14,325 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 1.75 dk2nu
2022-06-20 09:57:16,413 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:16,413 INFO That's fine, will go ahead with submission
2022-06-20 09:57:16,413 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 1.75 dk2nu
2022-06-20 09:57:16,413 INFO There will be 3 submissions for RHC at 5.75.
2022-06-20 09:57:17,139 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:17,139 INFO That's fine, will go ahead with submission
2022-06-20 09:57:17,139 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 5.75 dk2nu
2022-06-20 09:57:17,897 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:17,897 INFO That's fine, will go ahead with submission
2022-06-20 09:57:17,897 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 5.75 dk2nu
2022-06-20 09:57:18,662 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:18,663 INFO That's fine, will go ahead with submission
2022-06-20 09:57:18,663 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 5.75 dk2nu
2022-06-20 09:57:18,663 INFO There will be 3 submissions for RHC at 9.75.
2022-06-20 09:57:19,433 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:19,433 INFO That's fine, will go ahead with submission
2022-06-20 09:57:19,433 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 9.75 dk2nu
2022-06-20 09:57:20,210 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:20,211 INFO That's fine, will go ahead with submission
2022-06-20 09:57:20,211 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 9.75 dk2nu
2022-06-20 09:57:20,974 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:20,975 INFO That's fine, will go ahead with submission
2022-06-20 09:57:20,975 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 9.75 dk2nu
2022-06-20 09:57:20,975 INFO There will be 3 submissions for RHC at 13.75.
2022-06-20 09:57:21,736 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:21,736 INFO That's fine, will go ahead with submission
2022-06-20 09:57:21,736 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 13.75 dk2nu
2022-06-20 09:57:22,560 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:22,561 INFO That's fine, will go ahead with submission
2022-06-20 09:57:22,561 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 13.75 dk2nu
2022-06-20 09:57:23,312 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:23,313 INFO That's fine, will go ahead with submission
2022-06-20 09:57:23,313 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 13.75 dk2nu
2022-06-20 09:57:23,313 INFO There will be 3 submissions for RHC at 17.75.
2022-06-20 09:57:24,919 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:24,919 INFO That's fine, will go ahead with submission
2022-06-20 09:57:24,919 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 17.75 dk2nu
2022-06-20 09:57:25,696 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:25,696 INFO That's fine, will go ahead with submission
2022-06-20 09:57:25,696 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 17.75 dk2nu
2022-06-20 09:57:26,477 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:26,477 INFO That's fine, will go ahead with submission
2022-06-20 09:57:26,477 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 17.75 dk2nu
2022-06-20 09:57:26,477 INFO There will be 3 submissions for RHC at 21.75.
2022-06-20 09:57:28,240 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:28,240 INFO That's fine, will go ahead with submission
2022-06-20 09:57:28,241 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 21.75 dk2nu
2022-06-20 09:57:29,009 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:29,009 INFO That's fine, will go ahead with submission
2022-06-20 09:57:29,009 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 21.75 dk2nu
2022-06-20 09:57:29,782 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:29,782 INFO That's fine, will go ahead with submission
2022-06-20 09:57:29,782 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 21.75 dk2nu
2022-06-20 09:57:29,782 INFO There will be 3 submissions for RHC at 25.75.
2022-06-20 09:57:30,557 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:30,557 INFO That's fine, will go ahead with submission
2022-06-20 09:57:30,557 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 25.75 dk2nu
2022-06-20 09:57:31,324 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:31,324 INFO That's fine, will go ahead with submission
2022-06-20 09:57:31,324 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 25.75 dk2nu
2022-06-20 09:57:32,091 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:32,091 INFO That's fine, will go ahead with submission
2022-06-20 09:57:32,091 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 25.75 dk2nu
2022-06-20 09:57:32,091 INFO There will be 3 submissions for RHC at 26.25.
2022-06-20 09:57:32,840 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:32,840 INFO That's fine, will go ahead with submission
2022-06-20 09:57:32,840 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 26.25 dk2nu
2022-06-20 09:57:33,582 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:33,582 INFO That's fine, will go ahead with submission
2022-06-20 09:57:33,582 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 26.25 dk2nu
2022-06-20 09:57:35,177 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:35,178 INFO That's fine, will go ahead with submission
2022-06-20 09:57:35,178 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 26.25 dk2nu
2022-06-20 09:57:35,178 INFO There will be 3 submissions for RHC at 28.5.
2022-06-20 09:57:35,982 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:35,982 INFO That's fine, will go ahead with submission
2022-06-20 09:57:35,982 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 0 1e16 28.5 dk2nu
2022-06-20 09:57:36,716 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:36,716 INFO That's fine, will go ahead with submission
2022-06-20 09:57:36,716 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 10000 1e16 28.5 dk2nu
2022-06-20 09:57:37,484 INFO There are currently 0 jobs under abooth user...
2022-06-20 09:57:37,484 INFO That's fine, will go ahead with submission
2022-06-20 09:57:37,484 INFO Running in --print_only but would have executed:
jobsub_submit --group dune --role=Analysis -N 10000 --maxConcurrent 2000 --OS=SL7 --expected-lifetime=24h --memory=4000MB file://run_everything.sh RHC 20000 1e16 28.5 dk2nu
2022-06-20 09:57:37,484 INFO launch_ndcafmaker_campaign.py finished!

@CiaranH1997 confirmed that the first test file looks OK. Now running a small test of the automation. Will merge after see that this is successful.


Security Overwrite - Oauth 1.0

Implement the support to overwrite the security settings for Oauth 1.0
Example collection: https://github.com/postmanlabs/newman/blob/2a57036bc96c6e06289238cb4ef3fe70c1f9f338/test/integration/oauth1-var-in-url-params.postman_collection.json

Linked to #272

We just released version 1.15.0 of Portman, where this new feature is included.


Text in database table edit dialog is not readable

Summary
Text in database table edit dialog is not readable.
Expected
Text color must be light (white?)
Actual behavior
Text is black, so is the background.
Steps to reproduce (if needed)

Create a data source in database view.
Connect to a sample database with some tables.
List the database's tables
Choose any table, right click and in the context menu choose Modify table (Ctrl + F6)
Dialog will open and the table's column names are not readable.

Environment
Color blind filter is turned off
IntelliJ IDEA 2017.2.5
Build #IU-172.4343.14, built on September 26, 2017
Licensed to milan
JRE: 1.8.0_152-release-915-b12 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.13.4-200.fc26.x86_64

Oh and for the curious eyes, the DB design is not mine, I wouldn't make such a mess. I'm actually migrating it :laughing:

You aren't using the Material Color Scheme apparently.


[BUG] emojule integration not correctly autocompleting

Describe the bug
When selecting a emojule suggestion using the arrow keys and then enter it sometimes does not correctly replace the word, but prepends it.
Screenshots/GIFs/Videos

Fixed in emojule


Update requests to 2.31.0

Update requests to 2.31.0
https://github.com/home-assistant/core/pull/93363
fix https://github.com/jjbankert/hass_chatgpt/issues/6

Change fixed the issue

Looks like it does fix it...
The original issue with HA 2023.6.0:

I've had this working for a few weeks now, but now Home Assistant does not like the confuration.yaml entry at all.
If I remove it I can reboot HAOS with no issues, but if I put it back (the way it worked before) I get an invalid config entry error and cannot restart Home Assistant.

Whoops!
Will the updated version still work with 2023.5 after this change? I would expect something like requests>=2.28.2 to be more robust

Thanks for finding the root of the problem. Made my life very easy :)


Wiki contributor license agreement link points to old url

The CLA on this page points to the old url: https://github.com/MSOpenTech/redis/wiki/Contribute
Change it from: https://cla.msopentech.com/
To: https://cla2.msopentech.com/

@laurencee,
fixed, thank you.


feat: support content-raw-[...]

Signed-off-by: xhe<EMAIL_ADDRESS>close #1713

how about this #1716

@sudongyuer Nice!


💡[FEATURE]: Footer can be changed

Is your feature request related to a problem? Please describe.
Footer can be changed.
Describe the solution you'd like
Footer style can be changed and more content can be added in the footer.
Describe alternatives you've considered
Footer can be aligned properly.
Additional context
Add any other context or screenshots about the feature request here.

Something like this can be implemented on a dark background

I would like to work on this issue , please assign this to me.
@akshitagupta15june


[JS] Communication Common | Renaming field name in Microsoft Teams App Identifier Serializer

Packages impacted by this PR
communication-common
Describe the problem that is addressed by this PR
Renaming field teamsAppId to appId to match REST specification.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/communication-common


[PUBDEV-5666] Allow Synchronous and Asynchronous Scala Cells in H2O Flow

@michal-raska I know that Sparkling Water is a bit off-topic but just another pair of eyes on this code can help. Even just from the coffeescript point of view.
The code was tested and works as expected - demonstrated on the video in #dev-sparkling-water Slack channel
thanks for help!

Looks good to me, thanks @jakubhava.


Correct usage of  SqlDatabaseResource.GetMetrics

Library name and version
Azure.ResourceManager.Sql 1.3.0-beta.5
Query/Question
I'm trying to use the following code :
                var metrics = databaseResource.GetMetrics($"name/value eq 'dtu_consumption_percent' and timeGrain eq duration'PT5M' and startTime eq '{startDateUTC.ToString("O")}' and endTime eq '{endDateUTC.ToString("O")}");
                var dtus = new List<string>();
                foreach (var met in metrics.AsPages())
                {
                    foreach (var item in met.Values)
                    {
                        foreach(var metricValue in item.MetricValues)
                        {
                            results.Add(new PerformanceReport()
                            {
                                StartTimeUTC = TimeZoneInfo.ConvertTime(metricValue.Timestamp.Value.UtcDateTime, args.TimeZone, TimeZoneInfo.Utc),
                                AverageDTUPercentage = metricValue.Average.GetValueOrDefault(),
                                MaximumDTUPercentage = metricValue.Maximum.GetValueOrDefault(),
                            }) ;
                        }
                    }
                }

My issue is that no mater when I try the values for
AverageDTUPercentage = metricValue.Average.GetValueOrDefault(),
MaximumDTUPercentage = metricValue.Maximum.GetValueOrDefault(),

Are always the same, this is equally true for Minimum and Total.
Is there a way I can get these metric in different aggregations?
Environment
Azure AppService
.NET 6.0

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @Fungusware , It's about the delicate usage of the specific function. It would be better go find help from the azure service team.
But I will give you some advice from my view below. Hope it would solve your confusion.
If you always got the same average and maximum value from the dtu_comsumption_percent, it's due to the timerGrain Parameter in your GetMetrics method.
In your case, it's set to PT5M which means the data is aggregated every 5 minutes. If the average and maximum value is the same, it could mean the metric value doesn't change during 5-minutes intervals.
So you can increase the aggregation Period Time from 5 to like 30, then you may get some different aggregations.

Hi @Fungusware ,  I can not see the picture.

I have edited my previous post.

Hey @Fungusware , thank you for reaching out to us about the Azure SDK for .NET. Unfortunately, this issue is related to the service side and not the SDK side, so we are not able to help you with it. Therefore, we are closing this issue for now. If you need more assistance, please open an Azure support request. We apologize for any inconvenience this may cause you.
We value your feedback and we want to make sure that your problem is solved. If you think that we have misunderstood your issue or closed it incorrectly, please feel free to comment on this thread and reopen the issue. We will be happy to assist you further. Thank you for your understanding and cooperation.


FEATURE REQUEST: Ability to make a single relationship type selection for a collection of elements dragged into an other element for nesting

Expected Behaviour
When dragging a larger collection of elements onto an other element for nesting, one has the option to make a single relationship type selection for the whole collection.
Actual Behaviour
When dragging a larger collection of elements onto an other element for nesting, one has to make a relationship type selection for each and every element that is nested which can be quite cumbersome.
Suggested Behaviour

Select the collection and drag it onto an other element
Tick the check box for a single relationship type selection for the whole collection
Choose one out of the available relationship types that work for the whole collection
Press ok.

If you hold the Ctrl key down when making a selection from the combo box and click on an empty area the selection applies to all (if it is a valid relation).
I'm not going to change the current behaviour as it can be quite flexible.

If you hold the Ctrl key down when making a selection from the combo box and click on an empty area the selection applies to all (if it is a valid relation).
I'm not going to change the current behaviour as it can be quite flexible.

? I didn't know this trick. That's really cool (and useful). Thank you!

Page 40 ;-)

Page 40 ;-)

The point is that I must be one of the few who really did read the manual (and at least twice), but this is the kind of things I did not noticed of maybe even understood at that time.
Now, the next time someone told me this is too long to change all values I will say: "Hey, this is a simple trick, did you ever read the Fu?#!&& manual?" ;-)


[GEN-1481] Update case selection scripts to pull from a main genie consortium release

Problem:
Currently the case selection script pulls from the main GENIE clinical patient and sample databases. We need to link this to a certain main GENIE clinical files for a given release version for the sake of release tracking.
Solution:

Add the get_main_genie_clinical_id function to pull synapse id for data_clinical.txt file for a given release
Add release parameter to related scripts allowing specify main GENIE release version when implementing the case selection.

@rxu17 I added the test scripts. Please take a look.


Fix withProps #105

Fix this https://github.com/acdlite/recompose/issues/105#issuecomment-213607329

@istarkov thanks for your work. This version of withProps is like what I proposed in #105 but much more concise, good job!

👍

Thanks, @istarkov!
Any idea when this might get published?


ci: Automerge toolchain updates

I don't think #3621 is auto-merged because GitHub Actions doesn't trigger another Action.

Thanks! Adjusted in #3624...


Can not work on Open Layer 7.2.2

It does not run and does not work in version Open Layer 7.2.2
If you have a sample for this version, send it

I've done a quick and dirty update to ol3-sidebar used by the ol-layerswitcher examples to support OpenLayers 7: walkermatt/ol-layerswitcher/tree/master/examples/ol-sidebar. I'd be happy for someone to contribute this back to this repo.

Hello,
I also tried to use ol-sidebar with OpenLayers v7.4.0 but it doesn't work on my side.


Failed to enable second display on AMD iGPU

Running a Ryzen 7950x CPU with integrated graphics (AMD ATI 17:00.0 Raphael) and a Radeon 6600 discrete GPU. When using 2 monitors, one connected to the discrete GPU, the other to the iGPU, the discrete head works, while the iGPU doesn't.
When testing with Qtile wayland (also wlroots based), both heads work as expected.
Log snippet:
[LOG] Instance Signature: 6867831a1b7f42033c2f326db5e63f95fda6084c_1675567926
[LOG] Hyprland PID: 780
[LOG] ===== SYSTEM INFO: =====
[LOG] System name: Linux
[LOG] Node name: matte
[LOG] Release: 6.1.9-arch1-1
[LOG] Version: #1 SMP PREEMPT_DYNAMIC Wed, 01 Feb 2023 17:07:39 +0000
[LOG] GPU information:
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller])
17:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller])
[LOG] os-release:
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
[LOG] ========================
[INFO] If you are crashing, or encounter any bugs, please consult https://wiki.hyprland.org/Crashes-and-Bugs/
[LOG]
Current splash: Some legends are told, some turn to dust or to gold
[LOG] Hyprland init finished.
[LOG] Creating the KeybindManager!
[LOG] Creating the AnimationManager!
[LOG] Created a bezier curve, baked 200 points, mem usage: 3.20kB, time to bake: 286.03µs. Estimated average calc time: 0.00µs.
[LOG] Creating the LayoutManager!
[LOG] Creating the ConfigManager!
[LOG] Creating the CHyprError!
[LOG] Creating the ThreadManager!
[LOG] Reloading the config!
[LOG] Created a bezier curve, baked 200 points, mem usage: 3.20kB, time to bake: 3.90µs. Estimated average calc time: 0.00µs.
[LOG] Created a bezier curve, baked 200 points, mem usage: 3.20kB, time to bake: 3.99µs. Estimated average calc time: 0.00µs.
[LOG] Registered dynamic var "$mainMod" -> SUPER
[LOG] Hypr socket started at /tmp/hypr/6867831a1b7f42033c2f326db5e63f95fda6084c_1675567926/.socket.sock
[LOG] Creating the InputManager!
[LOG] Creating the CHyprOpenGLImpl!
[LOG] Creating the Hypr OpenGL Renderer!
[LOG] Using: OpenGL ES 3.2 Mesa 22.3.4
[LOG] Vendor: AMD
[LOG] Renderer: AMD Radeon RX 6600 (navi23, LLVM 15.0.7, DRM 3.49, 6.1.9-arch1-1)
[LOG] Supported extensions size: 149
[LOG] Creating the HyprRenderer!
[LOG] Creating the XWaylandManager!
[LOG] Registered signal for owner 16513160: 165131a0 -> 13ab6e20 (owner: XWayland Manager)
[LOG] Registered signal for owner 16513160: 165131b0 -> 13ab6e00 (owner: XWayland Manager)
[LOG] CHyprXWaylandManager started on display :0
[LOG] Creating the ProtocolManager!
[LOG] ToplevelExportManager started successfully!
[LOG] FractionalScaleManager started successfully!
[LOG] Creating the EventManager!
[LOG] Creating the HyprDebugOverlay!
[LOG] Registered signal for owner 158c3760: 158c3788 -> 13ab6d00 (owner: Backend)
[LOG] Registered signal for owner 1642cb30: 1642cb80 -> 13ab6ca0 (owner: XDG Shell)
[LOG] Registered signal for owner 1642cc00: 1642cc18 -> 13ab6c60 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc28 -> 13ab6c40 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc38 -> 13ab6c20 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc48 -> 13ab6c00 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc58 -> 13ab6be0 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc68 -> 13ab69c0 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc78 -> 13ab6980 (owner: WLRCursor)
[LOG] Hypr socket 2 started at /tmp/hypr/6867831a1b7f42033c2f326db5e63f95fda6084c_1675567926/.socket2.sock
[LOG] Registered signal for owner 1642cc00: 1642cc88 -> 13ab69a0 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cc98 -> 13ab6960 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cca8 -> 13ab6940 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642ccb8 -> 13ab6920 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642ccf8 -> 13ab6880 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cce8 -> 13ab6860 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cd08 -> 13ab6840 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642cd28 -> 13ab6820 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642ccc8 -> 13ab6800 (owner: WLRCursor)
[LOG] Registered signal for owner 1642cc00: 1642ccd8 -> 13ab67e0 (owner: WLRCursor)
[LOG] Registered signal for owner 158c3760: 158c3778 -> 13ab6bc0 (owner: Backend)
[LOG] Registered signal for owner 158c2568: 1645e798 -> 13ab6b60 (owner: Seat)
[LOG] Registered signal for owner 158c2568: 1645e7a8 -> 13ab6b40 (owner: Seat)
[LOG] Registered signal for owner 158c2568: 1645e7e8 -> 13ab6ac0 (owner: Seat)
[LOG] Registered signal for owner 158c2568: 1645e7f8 -> 13ab6aa0 (owner: Seat)
[LOG] Registered signal for owner 158c2568: 1645e7a8 -> 13ab6b40 (owner: Seat)
[LOG] Registered signal for owner 158c2568: 1645e7c8 -> 13ab6b20 (owner: Seat)
[LOG] Registered signal for owner 1645ea50: 1645ea70 -> 13ab6cc0 (owner: LayerShell)
[LOG] Registered signal for owner 1642c8e0: 1642c900 -> 13ab6d20 (owner: OutputLayout)
[LOG] Registered signal for owner 16421860: 16421898 -> 13ab6b00 (owner: OutputMgr)
[LOG] Registered signal for owner 16421860: 164218a8 -> 13ab6ae0 (owner: OutputMgr)
[LOG] Registered signal for owner 1642ce90: 1642cec0 -> 13ab6a80 (owner: InhibitMgr)
[LOG] Registered signal for owner 1642ce90: 1642ced0 -> 13ab6a60 (owner: InhibitMgr)
[LOG] Registered signal for owner 1642d0d0: 1642d0e8 -> 13ab6b80 (owner: PointerConstraints)
[LOG] Registered signal for owner 1645ebc0: 1645ebf0 -> 13ab6a40 (owner: XDGDecoMgr)
[LOG] Registered signal for owner 1642d2d0: 1642d300 -> 13ab6ba0 (owner: VirtPtrMgr)
[LOG] Registered signal for owner 1642d220: 1642d250 -> 13ab68a0 (owner: VKeyboardMgr)
[LOG] Registered signal for owner 16348480: 16348480 -> 13ab6a20 (owner: WLRRenderer)
[LOG] Registered signal for owner 1642d780: 1642d7b0 -> 13ab6a00 (owner: WLRIdleInhibitMgr)
[LOG] Registered signal for owner 1642c930: 1642c960 -> 13ab6900 (owner: PowerMgr)
[LOG] Registered signal for owner 1642dc00: 1642dc30 -> 13ab68e0 (owner: IMEMgr)
[LOG] Registered signal for owner 1642db50: 1642db80 -> 13ab68c0 (owner: TextInputMgr)
[LOG] Registered signal for owner 1642dcb0: 1642dcd8 -> 13ab6c80 (owner: ActivationV1)
[LOG] Registered signal for owner 158c22c0: 1642d470 -> 13ab6ce0 (owner: DRM)
[LOG] Registered signal for owner 158c37f0: 158c3950 -> 13ab69e0 (owner: Session)
[LOG] wl_display_add_socket for wayland-1 succeeded with 0
[LOG] Running on WAYLAND_DISPLAY: wayland-1
[LOG] Attached a keyboard with name Power Button
[LOG] Registered signal for owner 165ce7a0: 165bb100 -> 165ce7a8 (owner: Keyboard)
[LOG] Registered signal for owner 165ce7a0: 165bb0f0 -> 165ce810 (owner: Keyboard)
[LOG] Registered signal for owner 165ce7a0: 165bafd0 -> 165ce8e0 (owner: Keyboard)
[LOG] Registered signal for owner 165ce7a0: 165bb110 -> 165ce878 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "power-button", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Power Button"
[LOG] New keyboard created, pointers Hypr: 165ce7a0 and WLR: 165bafb8
[LOG] Attached a keyboard with name Video Bus
[LOG] Registered signal for owner 16596d40: 16599650 -> 16596d48 (owner: Keyboard)
[LOG] Registered signal for owner 16596d40: 16599640 -> 16596db0 (owner: Keyboard)
[LOG] Registered signal for owner 16596d40: 16599520 -> 16596e80 (owner: Keyboard)
[LOG] Registered signal for owner 16596d40: 16599660 -> 16596e18 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "video-bus", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Video Bus"
[LOG] New keyboard created, pointers Hypr: 16596d40 and WLR: 16599508
[LOG] Attached a keyboard with name Power Button
[LOG] Registered signal for owner 165c1e40: 165a8ea0 -> 165c1e48 (owner: Keyboard)
[LOG] Registered signal for owner 165c1e40: 165a8e90 -> 165c1eb0 (owner: Keyboard)
[LOG] Registered signal for owner 165c1e40: 165a8d70 -> 165c1f80 (owner: Keyboard)
[LOG] Registered signal for owner 165c1e40: 165a8eb0 -> 165c1f18 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "power-button-1", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Power Button"
[LOG] New keyboard created, pointers Hypr: 165c1e40 and WLR: 165a8d58
[LOG] Attached a keyboard with name USB Camera: USB Camera
[LOG] Registered signal for owner 165a7400: 16695390 -> 165a7408 (owner: Keyboard)
[LOG] Registered signal for owner 165a7400: 16695380 -> 165a7470 (owner: Keyboard)
[LOG] Registered signal for owner 165a7400: 16695260 -> 165a7540 (owner: Keyboard)
[LOG] Registered signal for owner 165a7400: 166953a0 -> 165a74d8 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "usb-camera:-usb-camera", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "USB Camera: USB Camera"
[LOG] New keyboard created, pointers Hypr: 165a7400 and WLR: 16695248
[LOG] Attached a keyboard with name Logitech Gaming Keyboard G610
[LOG] Registered signal for owner 164e8dd0: 166d0d40 -> 164e8dd8 (owner: Keyboard)
[LOG] Registered signal for owner 164e8dd0: 166d0d30 -> 164e8e40 (owner: Keyboard)
[LOG] Registered signal for owner 164e8dd0: 166d0c10 -> 164e8f10 (owner: Keyboard)
[LOG] Registered signal for owner 164e8dd0: 166d0d50 -> 164e8ea8 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "logitech-gaming-keyboard-g610", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Logitech Gaming Keyboard G610"
[LOG] New keyboard created, pointers Hypr: 164e8dd0 and WLR: 166d0bf8
[LOG] Attached a keyboard with name Logitech Gaming Keyboard G610 Keyboard
[LOG] Registered signal for owner 1670a8f0: 1670a500 -> 1670a8f8 (owner: Keyboard)
[LOG] Registered signal for owner 1670a8f0: 1670a4f0 -> 1670a960 (owner: Keyboard)
[LOG] Registered signal for owner 1670a8f0: 1670a3d0 -> 1670aa30 (owner: Keyboard)
[LOG] Registered signal for owner 1670a8f0: 1670a510 -> 1670a9c8 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "logitech-gaming-keyboard-g610-keyboard", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Logitech Gaming Keyboard G610 Keyboard"
[LOG] New keyboard created, pointers Hypr: 1670a8f0 and WLR: 1670a3b8
[LOG] Attached a mouse with name Logitech G502 HERO Gaming Mouse
[LOG] New mouse has libinput sens 0.00 (0.00) with accel profile 2 (2)
[LOG] Applied config to mouse logitech-g502-hero-gaming-mouse, sens 0.00
[LOG] Registered signal for owner 16595260: 16743bf0 -> 16595320 (owner: Mouse)
[LOG] New mouse created, pointer WLR: 16743bd8
[LOG] Attached a keyboard with name Logitech G502 HERO Gaming Mouse Keyboard
[LOG] Registered signal for owner 16744730: 16744340 -> 16744738 (owner: Keyboard)
[LOG] Registered signal for owner 16744730: 16744330 -> 167447a0 (owner: Keyboard)
[LOG] Registered signal for owner 16744730: 16744210 -> 16744870 (owner: Keyboard)
[LOG] Registered signal for owner 16744730: 16744350 -> 16744808 (owner: Keyboard)
[LOG] ApplyConfigToKeyboard for "logitech-g502-hero-gaming-mouse-keyboard", hasconfig: 0
[LOG] Attempting to create a keymap for layout us with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to us and variant to  for keyboard "Logitech G502 HERO Gaming Mouse Keyboard"
[LOG] New keyboard created, pointers Hypr: 16744730 and WLR: 167441f8
[LOG] Attached a mouse with name Logitech G502 HERO Gaming Mouse Keyboard
[LOG] New mouse has libinput sens 0.00 (0.00) with accel profile 0 (0)
[LOG] Applied config to mouse logitech-g502-hero-gaming-mouse, sens 0.00
[LOG] Applied config to mouse logitech-g502-hero-gaming-mouse-keyboard-1, sens 0.00
[LOG] Registered signal for owner 16598420: 16744390 -> 165984e0 (owner: Mouse)
[LOG] New mouse created, pointer WLR: 16744378
[LOG] Adding completely new monitor.
[LOG] Registered signal for owner 1677f1f0: 1677ebc0 -> 1677f340 (owner: )
[LOG] Registered signal for owner 1677f1f0: 1677ec50 -> 1677f3a8 (owner: )
[LOG] Registered signal for owner 1677f1f0: 1677ec40 -> 1677f410 (owner: )
[LOG] Applying monitor rule for HDMI-A-1
[LOG] Setting preferred mode for HDMI-A-1
[LOG] Monitor HDMI-A-1 -> destroyed all render data
[LOG] Monitor HDMI-A-1 layers arranged: reserved: 0.000000 0.000000 0.000000 0.000000
[LOG] Monitor HDMI-A-1 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 0, pos 1080x770, 10b 0
[LOG] Added new monitor with name HDMI-A-1 at 1080,770 with size 1920x1080, pointer 1677ea80
[LOG] New monitor: WORKSPACEID 1, exists: 0
[LOG] Monitor HDMI-A-1 layers arranged: reserved: 0.000000 0.000000 0.000000 0.000000
[LOG] Adding completely new monitor.
[LOG] Registered signal for owner 167d0540: 167cf510 -> 167d0690 (owner: )
[LOG] Registered signal for owner 167d0540: 167cf5a0 -> 167d06f8 (owner: )
[LOG] Registered signal for owner 167d0540: 167cf590 -> 167d0760 (owner: )
[LOG] Applying monitor rule for HDMI-A-3
[LOG] Setting preferred mode for HDMI-A-3
[ERR] Couldn't commit output named HDMI-A-3
[LOG] Monitor HDMI-A-3 -> destroyed all render data
[LOG] Monitor HDMI-A-3 layers arranged: reserved: 0.000000 0.000000 0.000000 0.000000
[LOG] Monitor HDMI-A-3 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 3, pos 0x0, 10b 0
[LOG] Added new monitor with name HDMI-A-3 at 0,0 with size 1920x1080, pointer 167cf3d0
[LOG] New monitor: WORKSPACEID 2, exists: 0
[LOG] Monitor HDMI-A-3 layers arranged: reserved: 0.000000 0.000000 0.000000 0.000000
[LOG] Hyprland is ready, running the event loop!

[ERR] Couldn't commit output named HDMI-A-3

XD
can you try setting an explicite rule for that display? otherwise, it seems like wlroots is at fault

Here are my current monitor rules:
monitor=HDMI-A-1,preferred,1080x770,1
monitor=HDMI-A-3,preferred,0x0,1
monitor=HDMI-A-3,transform,3
After further investigation, I believe it is related to the wlroots bug as described in the FAQ, which I initially dismissed since I am not using a laptop, and the bug mentions the iGPU display working, with the external displays not working, which is the opposite of my problem. However, the bug author said it worked as expected on wlroots 0.15, which is what Qtile uses, and explains why it works there and not on Hyprland.

Setting that environment variable worked for me, I now feel very silly.


Refactor historical / current log collection

This refactoring is required so we can post things other than historical and current logs such as automate dialogs, domains/models, etc.
https://bugzilla.redhat.com/show_bug.cgi?id=1535179
Note, the tests are going to be moved and refactored in a followup PR when I need to add the automate dialogs/domains posting.

I'll fix up the cops in a followup PR.  Many are from the original code and I'd rather not refactor and appease rubocop here.


nx angular project can't compile prisma auto generated types

Bug description
when I import prisma generated types in my angular project it doesn't compile properly, I get this error:
Error: node_modules/.prisma/client/index.d.ts:11:117 - error TS1005: '(' expected.
11   [K in keyof Tuple]: K extends ${number} ? Tuple[K] extends PrismaPromise ? X : UnwrapPromise<Tuple[K]> : UnwrapPromise<Tuple[K]>
i'm using version:
prisma: 2.18.0
@angular/cli: 11.0.0
@nrwl/cli: 11.5.1
eslint: 7.10.0
basicly i use the default configurations generated by nx cli for .eslintrc.json and tsconfig.json.

How to reproduce

Expected behavior

Prisma information

Environment & setup

OS:
Database:
Node.js version:
Prisma version:

I believe the version of Prisma that you have requires at least TypeScript version 4.1.5, so you could try updating that in your package.json. I had the same (or very similar) issue and that fixed it for me!

I was using typescript version 4.0.3 because the nx cli generated the project with that version.
Updating typescript to version 4.1.5 resolved the issue.
Thank you @kraglalbert.

Next release of Prisma will provide a runtime check for the required Typescript version to surface this to you - sorry we only added this recently.


micrologger: print value of "stack" as JSON object if possible

Towards https://github.com/giantswarm/giantswarm/issues/7021.
Before the change output would look something like this:
{
        "caller": "github.com/giantswarm/opsctl/command/deploy/command.go:121",
        "level": "error",
        "stack": "{\"kind\":\"unknown\",\"annotation\":\"POST https://api.github.com/repos/giantswarm/i-do-not-exist/deployments: 404 Not Found []\",\"stack\":[{\"file\":\"/Users/kopiczko/go/src/github.com/giantswarm/opsctl/service/github/github.go\",\"line\":143},{\"file\":\"/Users/kopiczko/go/src/github.com/giantswarm/opsctl/service/github/github.go\",\"line\":114},{\"file\":\"/Users/kopiczko/go/src/github.com/giantswarm/opsctl/pkg/cmd/deploy/githubdeploy/deployer.go\",\"line\":41},{\"file\":\"/Users/kopiczko/go/src/github.com/giantswarm/opsctl/command/deploy/command.go\",\"line\":226},{\"file\":\"/Users/kopiczko/go/pkg/mod/github.com/giantswarm/backoff@v0.0.0-20190913091243-4dd491125192/retry.go\",\"line\":23},{\"file\":\"/Users/kopiczko/go/src/github.com/giantswarm/opsctl/command/deploy/command.go\",\"line\":253}]}",
        "time": "2019-10-08T11:48:57.136204+00:00",
        "verbosity": 0
}

After the Change:
{
        "baz": "zap",
        "caller": "github.com/giantswarm/micrologger/logger_test.go:99",
        "foo": "bar",
        "stack": {
                "annotation": "POST https://api.github.com/repos/giantswarm/i-do-not-exist/deployments: 404 Not Found []",
                "kind": "unknown",
                "stack": [
                        {
                                "file": "/Users/kopiczko/go/src/github.com/giantswarm/opsctl/service/github/github.go",
                                "line": 143
                        },
                        {
                                "file": "/Users/kopiczko/go/src/github.com/giantswarm/opsctl/service/github/github.go",
                                "line": 114
                        },
                        {
                                "file": "/Users/kopiczko/go/src/github.com/giantswarm/opsctl/pkg/cmd/deploy/githubdeploy/deployer.go",
                                "line": 41
                        },
                        {
                                "file": "/Users/kopiczko/go/src/github.com/giantswarm/opsctl/command/deploy/command.go",
                                "line": 226
                        },
                        {
                                "file"<EMAIL_ADDRESS>                                "line": 23
                        },
                        {
                                "file": "/Users/kopiczko/go/src/github.com/giantswarm/opsctl/command/deploy/command.go",
                                "line": 253
                        }
                ]
        },
        "time": "2019-10-08T20:04:13.490819+00:00"
}

The CI doesn't work because of:
#!/bin/bash -eo pipefail
wget -q $(curl -sS -H "Authorization: token $RELEASE_TOKEN" https://api.github.com/repos/giantswarm/architect/releases/latest | grep browser_download_url | head -n 1 | cut -d '"' -f 4)
chmod +x ./architect
./architect version
wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.
Exited with code 1

Hopefully resolves itself after a while.

CI green.


Review/update "Installation Troubleshooting" information

The Installation Troubleshooting page (https://keptn.sh/docs/1.0.x/install/troubleshooting/ ) should be reviewed for accuracy, relevance, and completeness.  At a minimum, check the sample commands to be sure that they are correct.
Feel free to just provide information in this issue and assign it to me if that is easier for you than doing a doc PR.

Keptn V1 has reached EOL on December 22nd, 2023, so this issue has been closed.


Ability to output junit format to a file and retain default output to standard out.

We attempt to use the same Makefile for both our dev environments and our CI pipelines.  We would like junit reporting for the CI pipelines but its not particularly human readable.  We have been able to configure other linters  to emit a file in junit while having the stdout still be human readable.  Effective this would change the output-format setting to a list and allow setting a file with the formatter.  An Example of how this is handled in pylint is output-format="text,junit:build/junit-pylint.xml
I am new to rust but it looks like a bulk of the change would be in printer.rs
This would make our ci pipeline a lot cleaner, the only alternative right now seems to be to run ruff twice.

Hi @martinka
I think this is the same as https://github.com/astral-sh/ruff/issues/2388

Yes it is.. I missed that when looking at the issues.  you can close this I will follow that.


retriable: export Auth helpers

Coverage decreased (-0.05%) to 86.077% when pulling a329f09cdf36deede7c38850eea6f853b8f6b76c on dissoupov into 3f25c6e94df57641046a863194b76bbe5c589d52 on main.


Add resolve lock implementations

What this PR do

finish resolve locks and add tests
fix a bug of TiRegion.count disobey its meanings
fix a bug of several pd tso request returns the same value
Decoupling the client api and sender api for better modularity
refresh the region and continue instead of throwing requests for region errors

What the PR lefts

batch get multilevel implementations -> like what tidb does
streaming coprocessor error handling and resolve locks
modular implementation for batchGet and Scan

/run-all-tests

/run-all-tests

/run-all-tests

./run-all-tests

./run-all-tests

@zhexuany @birdstorm @ilovesoup
Hi all, I have pushed the test and change the documentation.

./run-all-tests

./run-all-tests

./run-all-tests

./run-all-tests

@ilovesoup @zhexuany @birdstorm

@ilovesoup PTAL

PTAL @ilovesoup


state wasn't being saved

Tasks were not being marked as skipped (they were hitting the set_state line though).
Not sure why I had to remove @provide_session - without it I received this stack trace:
[2016-01-15 14:37:59,460] {jobs.py:634} ERROR - set_state() got multiple values
for argument 'session'
Traceback (most recent call last):
  File "/opt/airflow/lib/python3.4/site-packages/airflow/jobs.py", line 631, in
_execute
    self.process_dag(dag, executor)
  File "/opt/airflow/lib/python3.4/site-packages/airflow/jobs.py", line 482, in
process_dag
    elif ti.is_runnable(flag_upstream_failed=True):
  File "/opt/airflow/lib/python3.4/site-packages/airflow/models.py", line 740, i
n is_runnable
    return self.is_queueable(flag_upstream_failed) and not self.pool_full()
  File "/opt/airflow/lib/python3.4/site-packages/airflow/models.py", line 730, i
n is_queueable
    flag_upstream_failed=flag_upstream_failed)):
  File "/opt/airflow/lib/python3.4/site-packages/airflow/models.py", line 859, i
n are_dependencies_met
    self.set_state(State.SKIPPED, session)
  File "/opt/airflow/lib/python3.4/site-packages/airflow/utils.py", line 142, in
 wrapper
    result = func(*args, **kwargs)
TypeError: set_state() got multiple values for argument 'session'

Thanks for the fix!


GUI Activation

Using ctrl + space momentarily opens GUI, but it vanishes almost immediately afterwards. In certain cases, the GUI will stay open if I use the shortcut directly after running the app, but if I change windows, etc., the shortcut fails. Usually I can open the GUI by clicking on the menu bar icon.

What context is this glitch happening in? Is it in a fullscreen application? Moving to windowed borderless might fix the problem. Let us know! 🙂

Having this issue as well (Windows 10, Python 3.8.3) Ctrl + space will open the GUI for 0.5-1.5 seconds before it auto-closes (independent of running application). I can force it to stay open by clicking into it while it's on the screen. Same issue if I click the tray icon (haven't checked the source but it seems like the tray icon just simulates a Ctrl + space press).
No debug in console to pass along. Basically just seems like Windows redirects focus from the app to whatever is currently in the foreground on its next GUI update.

Able to replicate issue on MacOS High Sierra version 10.13.6, using Python 3.7.7. Ctrl + space doesn't activate GUI, access from the system tray can be flaky. Actively seeking a work around for this.

GUI prints out ```

CLI prints out the following when trying to press the shortcut keys:
Error occurred removing key from pressed_keys

This is linked to

Solution: https://github.com/spotlightify/spotlightify/issues/13

Hey guys, I was able to come to a resolution. PR submitted: https://github.com/spotlightify/spotlightify/pull/47, this was verified on 1280 x 800 resolution screen.

@petergmurphy  this should be closed, as we concluded that click to 'focus' was not feasible, as it is not possible on Windows for security reasons.


Build FreeBSD 13 on FreeBSD 13

This works around our ncurses issue short of a better fix.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Busted


Remove elixir_sense from deps to fix VSCode ElixirLS crashing

Contributor checklist

[X] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

This fixes #4

oh, I'm sorry I didn't see this PR and just pushed up the fix. My apologies :(


Enable Dashboard HTTPS w/ self-signed certificate

Description
Currently, the Arkime Cluster dashboard is reachable over HTTP rather than HTTPS.  This is obviously not good.  Ideally, users would be able to use their own supplied domain and/or certs for the Dashboard URL.  However, providing a good and easy experience for that appears fairly complex.  As a stop-gap measure, and to enable users to spin up an Arkime Cluster for testing or other non-production usecases more easily, we should add HTTPS to the dashboard using self-signed certificates.  These will raise a browser warning due to not being verifiable, but result in traffic to the viewer process being encrypted.
Acceptance Criteria

HTTPS traffic to the Viewer Nodes is supported
It's acceptable for browsers to warn that the certificate doesn't chain up to a reputable certificate authority

After some investigation and discussion w/ @awick, it seems the approach we can take here is to create/upload a self-signed wildcard cert for something like *.us-east-2.elb.amazonaws.com into ACM as part of the pre-CDK create-cluster code, store the certificate ARN in SSM, and pass it into CDK with context.  CDK will create a handle to the ACM Cert using the ARN and supply it to a new HTTPS Listener on our Viewer Nodes' ELB.  We'll need to tear down the cert and the SSM param during destroy-cluster.  One advantage of using a self-signed cert is we don't have to bother with domain verification.
Some sample code to generate the certificate:
from cryptography import x509
from cryptography.x509.oid import NameOID, ExtensionOID
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives.asymmetric import rsa
from cryptography.hazmat.primitives import serialization
import datetime

# Generate a private key
private_key = rsa.generate_private_key(
    public_exponent=65537,
    key_size=2048,
)

# Prepare the certificate subject and issuer
subject = issuer = x509.Name([
    x509.NameAttribute(NameOID.COMMON_NAME, '*.us-east-2.elb.amazonaws.com'),
])

# Build the certificate
cert_builder = x509.CertificateBuilder()
cert_builder = cert_builder.subject_name(subject)
cert_builder = cert_builder.issuer_name(issuer)
cert_builder = cert_builder.public_key(private_key.public_key())
cert_builder = cert_builder.serial_number(x509.random_serial_number())
cert_builder = cert_builder.not_valid_before(datetime.datetime.utcnow())
cert_builder = cert_builder.not_valid_after(
    datetime.datetime.utcnow() + datetime.timedelta(days=365)
)

# Add a wildcard SAN extension
san = x509.SubjectAlternativeName([
    x509.DNSName('*.us-east-2.elb.amazonaws.com')
])
cert_builder = cert_builder.add_extension(san, critical=False)

# Sign the certificate with the private key
certificate = cert_builder.sign(private_key, hashes.SHA256())

# Serialize the certificate in PEM format
certificate_pem = certificate.public_bytes(serialization.Encoding.PEM)

# Serialize the private key in PEM format (unencrypted)
private_key_pem = private_key.private_bytes(
    encoding=serialization.Encoding.PEM,
    format=serialization.PrivateFormat.PKCS8,
    encryption_algorithm=serialization.NoEncryption(),
)

print("Self-signed certificate in PEM format:")
print(certificate_pem.decode('utf-8'))
print("Unencrypted private key in PEM format:")
print(private_key_pem.decode('utf-8'))

Some sample CDK:
    // Create an Application Load Balancer
    const alb = new elbv2.ApplicationLoadBalancer(this, 'MyALB', {
      vpc,
      internetFacing: true,
    });

    // Import the ACM Certificate using its ARN
    const certificateArn = 'arn:aws:acm:us-east-1:123456789012:certificate/your-certificate-arn';
    const certificate = acm.Certificate.fromCertificateArn(this, 'MyImportedCertificate', certificateArn);

    // Add an HTTPS listener to the Application Load Balancer
    alb.addListener('MyHttpsListener', {
      port: 443,
      protocol: elbv2.ApplicationProtocol.HTTPS,
      certificates: [certificate],
    });

HTTPS ended up being pretty easy to set up.  See: https://github.com/arkime/cloud-demo/pull/51

Code merged; resolving task.


Add API to create m3 color scheme from dynamic colors

Now that https://github.com/flutter/flutter/pull/93427  has landed

There is an unofficial dynamic_colorscheme package for this, but it has pretty rough implatemtation:
import 'package:flutter/material.dart';
import 'package:material_color_utilities/material_color_utilities.dart';

abstract class DynamicColorScheme {
  /// this method is to be used inside [DynamicColorBuilder] from the official Material package, dynamic_color.
  /// explanation is in example.
  static ColorScheme generate(CorePalette palette, {bool? dark}) {
    final result = _generateM3Scheme(palette, dark ?? false);
    return result;
  }
}

ColorScheme _generateM3Scheme(CorePalette palette, bool dark) {
  /// refer to https://m3.material.io/styles/color/the-color-system/tokens for detailed explanation
  /// lines commented out are colors defined in the link above, but undefined in [ColorScheme].
  /// tertiary and inverse colors also ignored due to the same reason.

  final bool d = dark;

  final primaries = palette.primary;
  final secondaries = palette.secondary;
  final neutrals = palette.neutral;

  final Color primary = Color(primaries.get(d ? 80 : 40));
  final Color primaryContainer = Color(primaries.get(d ? 30 : 90));
  final Color secondary = Color(secondaries.get(d ? 80 : 40));
  final Color secondaryContainer = Color(secondaries.get(d ? 30 : 90));
  final Color error = Color(palette.error.get(d ? 80 : 40));
  // final Color errorContainer = Color(palette.error.get(d ? 30 : 90));

  final Color background = Color(neutrals.get(d ? 10 : 99));
  final Color surface = background;

  final Color onPrimary = Color(primaries.get(d ? 20 : 100));
  final Color onSecondary = Color(secondaries.get(d ? 20 : 100));
  // final Color onPrimaryContainer = Color(primaries.get(d ? 90 : 10));
  // final Color onSecondaryContainer = Color(secondaries.get(d ? 90 : 10));
  final Color onError = Color(palette.error.get(d ? 20 : 100));
  // final Color onErrorContainer = Color(palette.error.get(d ? 80 : 10));

  final Color onBackground = Color(neutrals.get(d ? 90 : 10));
  final Color onSurface = onBackground;

  final ColorScheme result = ColorScheme(
      primary: primary,
      primaryVariant: primaryContainer,
      secondary: secondary,
      secondaryVariant: secondaryContainer,
      surface: surface,
      background: background,
      error: error,
      onPrimary: onPrimary,
      onSecondary: onSecondary,
      onSurface: onSurface,
      onBackground: onBackground,
      onError: onError,
      brightness: d ? Brightness.dark : Brightness.light);

  return result;
}

It would be great to have an official and correct implementation to use with Flutter.

I was thinking about creating a PR to this package, but in a few minutes just found that Flutter already has code to construct Flutter ColorScheme from CorePalette in ColorScheme.fromSeed method.
Unfortunately, this method just uses CorePalette class internally and there is no way to use this code by passing ColorPalette into this method.
So I think we still need ability to construct ColorScheme from CorePalette, but now I am unsure where and how to implement this functionality.
If we already have almost all code in Flutter itself, I think it is not a good idea to duplicate it here... @guidezpl - any thoughts on this?..

I did some further research and now see that just 6 days ago required functionality was commited into material_color_utilities package.
So as I understand, there is nothing to do here to resolve this issue and we should just wait for material_color_utilities new release.

I just tried to temporarily copy-paste material_color_utilities mapping code into my project until it is not published and still had to write some trivial helper code which constructs ColorScheme instance from Scheme instance like this:
ColorScheme createColorScheme(Scheme scheme, Brightness brightness) =>
    ColorScheme(
      brightness: brightness,
      primary: Color(scheme.primary),
      onPrimary: Color(scheme.onPrimary),
      primaryContainer: Color(scheme.primaryContainer),
      onPrimaryContainer: Color(scheme.onPrimaryContainer),
      secondary: Color(scheme.secondary),
      onSecondary: Color(scheme.onSecondary),
      secondaryContainer: Color(scheme.secondaryContainer),
      onSecondaryContainer: Color(scheme.onSecondaryContainer),
      tertiary: Color(scheme.tertiary),
      onTertiary: Color(scheme.onTertiary),
      tertiaryContainer: Color(scheme.tertiaryContainer),
      onTertiaryContainer: Color(scheme.onTertiaryContainer),
      error: Color(scheme.error),
      onError: Color(scheme.onError),
      errorContainer: Color(scheme.errorContainer),
      onErrorContainer: Color(scheme.onErrorContainer),
      background: Color(scheme.background),
      onBackground: Color(scheme.onBackground),
      surface: Color(scheme.surface),
      onSurface: Color(scheme.onSurface),
      surfaceVariant: Color(scheme.surfaceVariant),
      onSurfaceVariant: Color(scheme.onSurfaceVariant),
      outline: Color(scheme.outline),
      shadow: Color(scheme.shadow),
      inverseSurface: Color(scheme.inverseSurface),
      onInverseSurface: Color(scheme.inverseOnSurface),
      inversePrimary: Color(scheme.inversePrimary),
    );

I am not sure where such code should live, but I think this is the last step required to construct Flutter ColorScheme from CorePalette...

This is a side-effect of this library having intentionally no dependencies. Maybe we should provide a simple Scheme → ColorScheme function like the one above in the material library @darrenaustin WDYT?
Can publish the next version after this

The main problem I see with this is that we would be exposing Scheme in the public Flutter API. It might be confusing to have ColorScheme, and also Scheme that essentially do the same thing. Scheme also seems like a very generic term that doesn't necessarily denote something to do with colors.
That said, is there another API for dynamic color generation in material_color_utilities that we could wrap? Similar to the fromSeed methods we added earlier?

We could do this with an extension method Scheme.toColorScheme, which I don't think exposes Scheme.

That said, is there another API for dynamic color generation in material_color_utilities that we could wrap? Similar to the fromSeed methods we added earlier?

Alternatively, I made lightFromCorePalette and darkFromCorePalette available so this would be possible. Something like:
ColorScheme.fromCorePalette(CorePalette palette, Brightness brightness) => brightness == Brightness.light ? lightFromCorePalette(palette) : darkFromCorePalette(palette);

Yeah, I thought the spec should change to onInverseSurface (because it's the color that appears on the inverseSurface color but it was decided not to, hence the difference.


Unknown error when using spin new native <name>

Thanks in advance to anyone that takes a look at this one.
I'm getting an exception + stack trace when trying to create a new native project. I coped the terminal output I'm seeing below.
$ spin new native letsgo
📡  Updating official templates.
Done!

😱  Ooops, an unknown error occured. You can file a bug reports at https://github.com/tmattio/spin.
Here is the stack trace in case it helps:

spin: internal error, uncaught exception:
      (Of_sexp_error
        "lib/config_file/config_file_doc.re.cst_of_sexp: unexpected sum tag"
        (invalid_sexp
          (command
            ((name "esy install")
              (description "Download and lock the dependencies.")))))
      Raised at file "sexp_conv.ml", line 203, characters 30-72
      Called from file "src/list.ml", line 376, characters 13-17
      Called from file "src/list.ml" (inlined), line 387, characters 15-31
      Called from file "lib/config_file/config_file.re" (inlined), line 40, characters 7-33
      Called from file "lib/config_file/config_file.re", line 38, characters 4-74
      Called from file "src/list.ml", line 368, characters 13-17
      Called from file "lib/source.re", line 36, characters 20-43
      Called from file "bin/commands/cmd_new.re", line 13, characters 15-41
      Called from file "lib/errors.re", line 18, characters 5-11
      Re-raised at file "lib/errors.re", line 107, characters 4-15
      Called from file "bin/commands/cmd_new.re", line 49, characters 4-84
      Called from file "cmdliner_term.ml", line 25, characters 19-24
      Called from file "cmdliner.ml", line 117, characters 32-39

As for the versions of things I have - they are here.
$ spin --version
0.5.0
$ which spin
/Users/liam/.nvm/versions/node/v12.14.1/bin/spin
$ ocaml --version
The OCaml toplevel, version 4.08.1

Let me know if I can provide some more information! ❤

Hi @liamgriffiths, thanks for reporting this.
This is the same issue as #58. I merged the dependence in spin-template, so you should be able to generate projects with 0.5.0 now.
I'm going to close this and keep #58 to track the remaining work related to it.


Update Proto field numbers in uprotocol_options.proto

The following change allows implementations to include both the open source protos from Eclipse and the older proprietary definitions (protos).

Hi @neelam-kushwah, I'm a bit out of the loop (and not great at Protobuf haha). What is this change in support of?

@stevenhartley what is the status of this PR?


Address #6 and be more specific about inviting contributors

This should make the text somewhat friendlier.
Fixes: #6

cc @somtochiama

cc @somtochiama

I think these changes are great!

I think these changes are great!


When the app is in the stage manager and the width is very small on iPad OS, popup cannot be displayed

.popup(isPresented: $showSendBox) {
                Text("test")
} customize: {
    $0.backgroundColor(.black.opacity(0.3))
        .closeOnTapOutside(true)
}

@paulpaulzhang But how would you like the popup to be displayed if the width is too small? Maybe I didn't get it right, could you please attach a picture?

@paulpaulzhang But how would you like the popup to be displayed if the width is too small? Maybe I didn't get it right, could you please attach a picture?

like this

sorry, I accidentally mistakenly clicked!
this is image

I made an adjustment - for non opaque popups I use the size of presenting window - not the screen size. I think it should fix your problem, could you please try version 2.5.3?

I made an adjustment - for non opaque popups I use the size of presenting window - not the screen size. I think it should fix your problem, could you please try version 2.5.3?

Thank you for responding so quickly! but after testing, I found that there were still issues:

When the keyboard pops up in non opaque mode, the view is blocked by the keyboard because it does not move up
When creating a popupview using the following code, the pop-up view will first appear in the top left corner of the screen (for a moment), and then appear from the bottom up, this phenomenon may not occur every time.

$0.popup(isPresented: $showSendBox) {
    Text("test")
        .frame(width: 300, height: 200)
        .background(.black)
} customize: {
    $0
   .closeOnTapOutside(true)
        .closeOnTap(false)
        .dragToDismiss(false)
        .backgroundColor(.black.opacity(0.25))
        .animation(.linear(duration: 0.2))
        .position(.bottom)
        .type(.toast)
}

Also, can you use presenting window to calculate size in opaque mode?

The point of opaque mode is to be on top of navbar (it is unobviously super complicated to achieve for some reason). And if I use presenting window size it will not account for navbar size. So this I can not do. But why would you need opaque popup if not to be independent from presenting view at all? I will look into issues you mentioned as soon as I can. Have a great day!

The point of opaque mode is to be on top of navbar (it is unobviously super complicated to achieve for some reason). And if I use presenting window size it will not account for navbar size. So this I can not do. But why would you need opaque popup if not to be independent from presenting view at all? I will look into issues you mentioned as soon as I can. Have a great day!

Thanks! I need opaque mode just because I need use closeOnTapOutside option

Hey @paulpaulzhang, please check out version 2.5.6, both issues should be fixed there. Have a great day!


DG_{AP} in Eq. 8

Is there any guarantee that DG_{AP} is non-negative?
For example, we have two batches:

Batch 1: red < red < green < green < green
Batch 2: red < green < green < green < red

The AP of Batch 1 is 1.0, and the AP of Batch 2 is 0.64. The average AP over such two batches is 0.82.
If these two batches form a dataset like this: red < red < red < green < green < green < red < green < green < green,
then the AP over the dataset is 0.915, and DG_{AP} here is -0.095, right?
Could you help me understand this part? Please let me know if I misunderstood something. Thanks. @elias-ramzi

Hi !
Sorry for the late response, I was not at work.
Thank you for your question.
You are right, DG_{AP} can be negative.
Note that in Eqs. 8 & 9 we assume that the AP per batch is 1, in this case DG_{AP} > 0. Indeed the mean AP per batch is 1 and the global AP has a maximum value of 1.
In your example, where this assumption is not correct, the SupAP loss would still optimize on batch 1 (as the AP loss on this batch is not 0).
I hope this will help you !

Hi @elias-ramzi, thanks a lot for your answer. It makes sense to me now. This assumption was not clear to me from the paper. I was confused at the beginning since it seems like the upper bound is proposed in a general setting.
Under the assumption that the AP per batch is 1, this upper bound should hold. Thanks again for your work.


/docs/ redirect should work correctly

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
N/A
Steps to Reproduce

Go to https://docusaurus.io/docs/

Expected Behavior
Should redirect to https://docusaurus.io/docs/{lang}/installation.html  ({lang} defaults to en)
Actual Behavior
404
Reproducible Demo
N/A

To be fair, https://docusaurus.io/docs/en/ does not work either.
Is there the concept of a default docs page ATM, as the header and landing page link is just a link to a specific page?

hi! can i try to work on this?

Sure. Knock yourself out. I don’t really have time to work on stuff outside work at the moment

On 9 Mar 2018, at 04:29, ashley teoh<EMAIL_ADDRESS>wrote:
hi! can i try to work on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ashleytqy Thank you!

Sorry. Was a bit short. Thanks for helping out. Let me know if you have any questions. :)
Sent from my iPhone

On 9 Mar 2018, at 15:49, Joel Marcey<EMAIL_ADDRESS>wrote:
@ashleytqy Thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ashleytqy, are you still working on this?
@joelmarcey, actually i am not really sure on the right behavior of this bug.
Should it be redirected to  https://docusaurus.io/docs/{lang}/installation.html?
What determines the default docs page (I believe that there is no concept of default docs page in Docusaurus) ?
What if its in another site (not docusaurus).
How about redirecting it to landing page ? ☺
#goodfirstissue

Hi, sorry I’m no longer working on this!

Is this issue fixed or not? Otherwise you will find here a solution.


Route transitions are always played, even without using appear

Reproduction
https://play.vuejs.org/#eNqNVltv2zYU/iun6gA7WCS5btcHTXXTFcWyYZeiDfYy7YGWji02EqmRlOPA8H/fIambXacYijTiuXznOxce5hDUjIvoiw6SgNeNVAYOkCtkBt81DRxho2QNs12Ls0x0Bkq2BlWniWJ/HNXWr9expom8byYG1Dn9XGUCIGo1zr27P9eyFWY+e05us6vgOujciVtqsG4q8l9Zw7R8sbrFqpI22LM0pqMTN+4XfWijpNiu3rdKoegYQ8NMmaRxp4PDAb5zimjTVtVHUsLx6GBij5MKtusBPzmWv3FxD0a+yYI4C1Y/S/qGW1ljGo/6Jz3YmiSD2zt7+sovjfuYqe3LKdZfHB9gF+pKGsI7wHtJBRc2vyPBelMyfhaGcFcirNstcA0bvscCWs3FFkxJAi60QVZck4EBbmYahKSPusaCU4GrR5DrHZethjA8RU3vFBOaGy4F8eAbYjFwyAIQrEYSbViBdKplYU/EPOSC+J2gTYC+7dV7kE8+pJtwfRY6HqHjEbsvX1dlW7+uyl1x03gyVjRvfhYv3obfsZbq8ZZrQ7+uO6HHnd6ScLgNw32wA+Ja11+KXtDdjP7a2IE4sRsk4xWS1Ds/zRrewN82mYOfa5jFM6LV1yQZwx6vT83cHJ7ajrGt8T9noRSFmuY7P1hAGiVbiuRSfeZXLqYnSp9Hut6ZwL1LtMANa6sem6o+rYe96jpXvDHUkTMHF7ZGU8pCJ/4EsJV30tGfX/UicHMe+cutoqbV5bxP2+0Z6Gpi/6cbTyuhj0iH00VT8GEFlMtVz5Q2zrIX0y0yNMY3ecXzexrLgdD5VfeG3QB63Mn8UR1O+j0WAjSa1m6kcSKpc5RacXk9H+iy+05dD19PzuhZmwf7ORVqopuorKbXaWQqL+14dIz8aGxx0g1F7JXwMNG/LarHqHN7+xZmRKLvBqU595rR13dQIdUox/kBnD/1vo98BDtahOBn7P93cqj1tJUVW2M1bJLPLkQCKReUGy08u5uqyCheU5s9Abux2L5CsTUlCZeLYWWl8Yh2ud2+XWHNGlo4UlDDXdZZp9BZMAx5Foxts+IsKI1pdBLHrWjutxGVPx4tbl5FL6MFxdRmIo1Q1+FayQftNlwWuKJb7BsyigvcGSkrHbKGPxXiK8Ob19Hr6EVc8XVM6DEXBe4ddt8TStNompUN354laSeGV6j+bOymPk2W0cv+8KuTGdXiQDQvMb+/IP+i957yR4WU3Y4ekkFnmKJx9OoPn//APX0PSupoW5H1N5SfUMuqtRy92U+tKIj2xM6x/cX1jN7YO/1hb5AeoC4pS3SccddI+3A9lfpI92X0alJFbR4r1FGu7dNEfyNc09xx4f3WUhWoElg2eyCyvIDni8XiR7ctCY6LcC1p9dQJvFg0eydvWFEQ2UFCUTJBsLACBt/Tj9+13rvCDb0RU8tyOY08wo8E8jyfEEhgQf+WE4TIvvchPT7kznLDd7abXlgh22En9GHM8KInIBuWc/MIi+gHDcg0XkK0q+4Mj/aww+r8iZF1DI7/AQj3tSs=
Steps to reproduce the bug
Load the playground page, and notice how the initial route fades in.
Expected behavior
Since I'm not using the appear property in the transition, I didn't expect the initial route to animate.
Actual behavior
The initial page fades in, it shouldn't play the animation given that I'm not using appear in the transition.
Additional information
I have investigated this issue, and I could see why the bug is happening. The first time the page is loaded, the Component provided in the v-slot of the RouterView is undefined, so the Transition component is loaded without any component first. Then, the route component is loaded and the enter transition is triggered.
Keeping that in mind, this issue can be fixed doing the following (adding v-if="Component" to the example in the docs):
<router-view v-slot="{ Component }">
  <transition v-if="Component" name="fade">
    <component :is="Component" />
  </transition>
</router-view>

However, I think it's very unintuitive. Maybe the RouterView component should avoid rendering anything inside of the slot until the router bootstrapping has been completed?
Otherwise, if you don't think this is a bug, I think we should at least add a warning note in the documentation mentioning this (I can open a PR myself if you want).

Your investigation is correct. You can avoid it by awaiting router.isReady() before mounting.
Feel free to open a PR or comment in the discussion about docs!


Set 'log: true' while calling 'Fastlane::Actions.sh' if CLI option --verbose

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I found it difficult to troubleshoot errors like:
ERROR [2016-11-06 03:34:20.16]: Shell command exited with exit status 48 instead of 0.
which are returned while running action e.g. create_keychain
Currently, shell command is called like this:
Fastlane::Actions.sh("security create-keychain -p #{escaped_password} #{escaped_name}", log: false)
Would you agree to set log: true if command line option --verbose is specified?
Or do you prefer another way for setting the log: true?
Please may you let me know so I can submit a pull request?

Yeah, I like the idea of having log being true if not specified otherwise 👍
Do you think there will be any side-effects?

For actions like the keychain, we can't just print the output, as it also contains the password. This shouldn't show up in build logs, even for verbose mode

how about adding --troubleshoot - wich enforces true on the sh action and also sets verbose - so you can manually choose it.

I like the --troubleshoot option.
If even more safety was desired, we could impose interactive user confirmation asking the user whether they really desire to display sensitive info, like the confirmation required in case of match nuke.
Also, the --troubleshoot option might be ignored if is_ci is true.

If even more safety was desired, we could impose interactive user confirmation asking the user whether they really desire to display sensitive info, like the confirmation required in case of match nuke.

Yes, I very much agree. Some users might not realize, enable it on CI (or wherever) and leak information. There's also the issue of people wanting to be helpful and copying the output with --troubleshoot to their issue/PR.

When running on CI, I wouldn't ignore the option, but fail and let the user know that this option needs to be disabled on CI
Otherwise there should be an interactive confirmation telling the user not to copy/paste the output anywhere w/o double checking and removing all passwords from the text and wether they are sure they really want to run with --troubleshoot

Solved via #6889.


traefik dashboard 404

traefik dashboard does not work according to the instructions in k3s (Kubernetes) - error 404, I read on the Internet this is a massive problem, maybe it's worth making the instructions better?
links to instructions and procedure :
1 - curl -sfL https://get.k3s.io | sh -
2 - https://doc.traefik.io/traefik/operations/dashboard/#dashboard-router-rule
k3s kubectl apply -f dashboard.yaml
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
name: dashboard
spec:
entryPoints:
- web
routes:
- match: Host(domains.com) && (PathPrefix(/dashboard) || PathPrefix(/api))
kind: Rule
services:
- name: api@internal
kind: TraefikService
3 - domains.com = 404
I tried a lot of options that I found on the web - it didn't work out
therefore, I wrote here the simplest and described instructions and it also does not work

After install K3S,  Traefik automatically creates an IngressRoute resource to access Traefik DashBoard.
You can edit the resource named traefik-dashboard.
kubectl edit ingressroute/traefik-dashboard -oyaml -n kube-system

Then modify the content in the spec, as shown below
spec:
  entryPoints:
  - web
  routes:
  - kind: Rule
    match: Host(`domains.com`)
    services:
    - kind: TraefikService
      name: api@internal

Finally, save it and exit editing. You can access it through domains.com

thank you very much
I also thought that if you use, or rather I read that it is more reliable to use - this option
The dashboard can be accessed on http://traefik.example.com/dashboard/
rule = "Host(traefik.example.com) && Path Prefix(/api, /dashboard)"
it doesn't work
and if
The dashboard can be accessed on http://traefik.example.com/dashboard/
rule = "Host(traefik.example.com)"
it worked right away, by the way, I did so in docker and also did not encounter any problems

Finally, save it and exit editing. You can access it through domains.com
@cctomato, will everything reset after the restart?

@Xilosof yes these changes to the IngressRoute get wiped out every time you modify the config. related to traefik here on k3s /var/lib/rancher/k3s/server/manifests/traefik.yaml, specifically you're not suppose to touch that file, so I make changes in an override file in the same subdirectory, /var/lib/rancher/k3s/server/manifests/traefik-override-config.yaml.


[FEATURE] Don't query user to save if outstanding edits, but a pipeline is running on data

If you run a pipeline on data (which is currently running and unfinished), but then the user makes some edits (or has some outstanding edits they haven't saved) to data and tries to leave the page (e.g. go to jobs panel) it will ask the user if he/she wants to save the outstanding edits, though my concern is that the pipeline runner will (and should) displace those changes so the save is redundant, and also if the save happens after pipeline execution finish, would it over-write the pipeline results?

might want to take a look at this test branch I did when messing around with the job notification update PR. https://github.com/Kitware/dive/tree/pipeline-job-running

I feel as if we need to properly implement ReadOnly Mode where it disables items in the interface and explains why.  Disabling stuff like deleting/adding new tracks.
I think that as a consequence of that we may need a new wrapper for buttons/icons that enable a disable state while also including a tooltip reason as to why items are disabled.

That's what I did for the above demo, it's just that once a button becomes disabled it removes tooltips because the v-on doesn't trigger properly.  So you have a button disabled with no indication as to why the button is disabled.  I would have to wrap the button to make it styled as disabled.  I could also wrap each button in a span tag so the v-on still triggers to display the tooltip but the button is truly disabled..

I guess I forgot to say the rest of my thought: a red or yellow banner across the top of the viewport with information like "you are in read-only mode" followed by an indication of how to get out of that mode might cover all cases. Then you wouldn't need to add redundant info to every single disabled control, and there would be a central way to understand what's happening. (I'm definitely following the excalibur idea here of displaying in text the "mode" information).

I like it.  I think the only thing I'd add is a link directly to the pipeline logs (in girder) from the "A pipeline is running" dialog.
There is one other issue:  Cancelling.
Pipelines can get stuck in the cancelling state because VIAME doesn't respond to signals, so the pipeline will continue to run to completion, then the whole job will fail because of an invalid state transition (Can't move from canceling to uploading data).
In order to merge this in, we probably need to first make sure that the cancel button always works.  I think we found some python OS function a while ago to force kill a whole PID tree, but I dont' remember.

So I added in a Read Only Mode Display with a tooltip explaining that it is read-only mode.
I also added in a View Running Job which will link to the Jobs page on desktop and will open the girder/#job/{jobID} page on the web version.
Also fixed the overflow issues with long dataset names

This looks really nice!

@faiza-a, could you give some quick feedback on Bryon's design here? Just a sanity check for any obvious improvements we could make (with a more comprehensive review of the full UI happening more slowly, as it already is). Thanks!

I think it's looking good and serving the purpose.
Adding an info icon would make it more prominent for user that the 'chip' is hoverable.

May also use the horizontal space to make more information visible. (but this could also look more crowded)

@BryonLewis, I think the info icon addition is a good idea--do you agree?
Displaying more info using the horizontal space is generally a nice idea but I think we need to better understand the effect of doing so on the UI, so let's hold off on that idea for now.

Yup, I had a ? icon in there at one point and it didn't feel right.  The info icon looks much better.  I'll ad it in.


RT-342: Implement changes to current/changed completion date display in monthly update forms

…g or revised timing pages.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@e091b59). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #120   +/-   ##
=======================================
  Coverage        ?   97.47%
=======================================
  Files           ?       63
  Lines           ?     4310
  Branches        ?        0
=======================================
  Hits            ?     4201
  Misses          ?      109
  Partials        ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e091b59...7b23f07. Read the comment docs.


Karabiner fails to build from source

The following is the error that I get when I try to build from scratch. Any advice on how to get this working? The error is not coming up in google. Any advice would be appreciated.

OS X version: 10.11.4
Karabiner version: 10.18.0
(You can confirm the version in "Misc & Uninstall" tab in Karabiner Preferences.)
Your Mac hardware: MacBook Pro
Your keyboard hardware: Razer BlackWidow (Probably not relevant)

/Applications/Xcode.app/Contents/Developer/usr/bin/make -C server

pod install --no-repo-update

Re-creating CocoaPods due to major version update.

Analyzing dependencies

[!] The dependency `Sparkle` is not used in any concrete target.

make[4]: *** [all] Error 1

make[3]: *** [all] Error 2

make[2]: *** [all] Error 2

make[1]: *** [build] Error 2

make: *** [all] Error 2

The master branch does not depend on CocoaPods.
Please clone master branch.