Replacing Slot Image at my vm

Hi, this has never worked and have tried asking many a time in the discord Nadeko server, to no effect.  I've run the Nadeko self-hosted bot for quite a long while now, but this issue has never been fixed. I've also tried countless amount of times to 'search the Nadeko Support server' the latest fix I found I printed below.  As it was not directed at me - still not sure how to work with that.
Today with suggestions from the Nadeko server - I uploaded a new pic without the spaces as suggested, then the latest command used was sudo mv LLAPnadekoSlots.png ~/NadekoBot/src/NadekoBot/bin/Release/netcoreapp2.0/data/images/slots/background.png Also ran the .reloadimages cmd.
TIA,
Sasha
Would really appreciate a fix, as it's been a long while, and never use the slot because of it.
this person seemed to know how to fix:

斜視-眼 - 04/12/2018
I know how
You need selfhost though
【NCBP】Potato - 04/12/2018
NadekoBot/src/NadekoBot/_strings/ResponseStrings.en-US.json
斜視-眼 - 04/12/2018
Go to the Images file
And then to slots
skymanplay - 04/12/2018
no
斜視-眼 - 04/12/2018
Then edit the image
Do NOT replace the image
skymanplay - 04/12/2018
default png slot image
斜視-眼 - 04/12/2018
Unless you want to fuck up your images.json
skymanplay - 04/12/2018
have someone?
斜視-眼 - 04/12/2018
Im telling you how
There is background.png
And background2.png
【NCBP】Potato - 04/12/2018
NadekoBot/src/NadekoBot/_strings/ResponseStrings.en-US.json @斜視-眼
skymanplay - 04/12/2018
i know
斜視-眼 - 04/12/2018

That is how you get this
Ty Potato
【NCBP】Hedgehog :Think: - 04/12/2018
@skymanplay you want the

default?

Not 100% sure why, but yes I do need to use sudo with a lot of things.. it's only me that interacts with it tho.  In the example where it shows my 'last command'.. at least it did seem to 'move the file', but did not show up in server using the slot command.
Which is why I think it may also need changing at background2.png (that's what I noticed in the above 'solution' by someone) Really just need to replace all 'copies' of the original nadeko one you'd think.. but don't know how.

Worked for me. Also, the command is .imagesreload now. I had to look that up real quick.

Works for me too. There are btw two locations where i post the images.
/NadekoBot/src/NadekoBot/data/images/slots
/NadekoBot/src/NadekoBot/bin/Release/netcoreapp2.0/data/images/slots
If you however, want to LOCK a file from being changed. You can use this command.
chattr +i /root/.pm2/dump.pm2
To unlock it, you do this:
chattr -i /root/.pm2/dump.pm2
I don't recommand this, because somewhere something goes wrong. But for the sake of fixing the issue for you, this would be a good workaround.

So happy it works for everyone else.. lol I've had a few people 'try'..  and I have used 'imagesreload' as well still no effect.
Will get to your information soon thanks @Macley-Kun  I'm also not getting an email for any updates here - so will fix that as well.

Btw you do stop the bot before you replace the images right?
Because that’s how I always do it.
The line I made of chattr is for Linux, but you can just navigate to the file you want to lock, do ‘pwd’ And copy that path with the full file name behind it in that command. It then locks the correct file.
but don’t use that unless everything else doesn’t seem to work

I don't want to lock anythng, I don't think.. Just need to get my Nadeko Slot image in the right place, but no, I've never 'stopped' by bot first as the guidance so far has been from the Nadeko support server and that was never mentioned. (my vm is ubuntu/linux)

Stop bot
Put your photos with the exact same name on these places
/NadekoBot/src/NadekoBot/data/images/slots
/NadekoBot/src/NadekoBot/bin/Release/netcoreapp2.0/data/images/slots
Then start bot. That’s all to it.

Would you mean to 'replace' the images with the same name (I don't use winscp, as I know that would be easier - but that's never connected / worked either) - so that makes working with my vm a lot trickier.. so, I have to use the (google cloud) ssh 'shell'.. popout thing (looks like a command window) so I remember to get the last image 'moved' it had to be
sudo mv (something)

yeh i mean replace.
you indeed use mv to move something. like mv /root/myimage.png /root/newfolder/
With Winscp, i would try to get it to work, you don't have to but i would recommand getting that to work. Kinda strange if a mayor tech company wouldn't let users connect with ftp to their paid virtualmachines...
I'm not really sure, but is it possible to like.. Open a photo image with notepad locally, copy the content, and past that in a new file with the extention corresponding to the original photo image?

I'll have a fiddle in a minute, I do appreciate the help.. the winscp just kept mucking up and not 'working' with the keys, I swear I did everything correctly - I have a computer 'tech' guy that I will get to work it out, if following your idea doesn't help me
I am intending to get the guy's help in connecting via the winscp, but have been putting it off.
Thanks again
I'll let you know if/when fixed

np,
Btw if you would use putty to connect to your vm, winscp would import those settings. You could try (but then you should not be having a ssh session) use port 22. But again i'm not sure if that would work... Because normally i would expect google to keep things simple.

putty or no, the metakeys didn't work, kept stuffing up.

Don't you mean the private key didn't work..?
To login you normally put (when creating a vm) a public key from puttygen (for example).
And use the private key you saved from puttygen to login automaticlly. But that's how i always do it. Maybe metakeys is some other methode..

nvm

When I did the replacement on mine, I didn't stop the bot. Just reloaded the images and it still worked. But that's besides the point.
I don't have FTP working on my server (something I have to fix still, just lazy), so I had to upload it to something else to download from. This is what I did step-by-step:

I upload the image temporarily somewhere.
I downloaded it to my Debian tower via SSH using PuTTY. (I use a username/password login, I haven't really bothered setting up my SSH key to it because its pretty locked down anyway)
mv background.png ./Bots/Discord/NadekoBot/src/NadekoBot/data/images/slots/background_n.png (I did the same with background2.png because at the time of testing, I didn't really check which was being used, but only background2.png is used anyway)
cd Bots/Discord/NadekoBot/src/NadekoBot/data/images/slots/
mv background.png background_old.png && mv background2.png background2_old.png (I kept the old ones as backup so I didn't delete them)
mv background_n.png background.png (same for the other)
Go into Discord (I used a private channel for this), issue .imagesreload, tested with a .slot 5 and it worked.

My method probably was a little bit longer than necessary, but you get the idea. Also, note that none of my commands issued ever used sudo. It is best to not to use sudo unless absolutely necessary for things on any Linux install as no process should be running as root except for system-level stuff. Something like this should always remain at the user level:

Now, I don't know how yours is set up. I'm just going on the assumption basing on previous commands used which I can neither confirm nor deny if its just a simple permission issue that the bot can't read the file because of the fact its under a different user/group entirely.

Thank you, thank you, thank you, thank you!!!! @TwinDragon It worked like a dream, have put up with the wrong image (default) for soooo long!
Have an Awesome Day!!

@Sashasonic if it's sorted out, you should close the GitHub issue. 😉


Hi All im using capistrano 3.3.5

Hi All ,
Im new to this capistrano , rails project .
I have one issue . while deploy rails code with capistrano i can able to see the logs in terminal .
But unable to print into a file ...
i have tried linux native method
cmd  > output.log not working
cmd  2>&1 | tee also not working...
Which is the best way to capture capistrano stadard output & error redirect into an file
Thanks in advance .

Closing because I’m not sure this is an issue, if you are convinced that this is really a bug, please feel free to re-open the issue and add more information (your versions (Ruby, Cap, etc), your Capfile, your logs, and relevant sections out of your Gemfile)
Otherwise support is done via the mailing list (https://groups.google.com/forum/#!forum/capistrano) or at StackOverflow (http://stackoverflow.com/questions/tagged/capistrano) with questions tagged capistrano.

ruby version = ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]
cap version =  Capistrano Version: 3.3.5 (Rake Version: 10.4.2)
os -= centos 6.5 64bit
gem version = 2.4.5
=============================================
Capfile pasted below
Load DSL and set up stages
require 'capistrano/setup'
Include default deployment tasks
require 'capistrano/deploy'
set :rbenv_type, :exptest
set :rbenv_ruby, '2.1.5'
Include tasks from other gems included in your Gemfile

For documentation on these, see for example:

https://github.com/capistrano/rvm
https://github.com/capistrano/rbenv
https://github.com/capistrano/chruby
https://github.com/capistrano/bundler
https://github.com/capistrano/rails
https://github.com/capistrano/passenger

require 'capistrano/rbenv'
require 'capistrano/bundler'
require 'capistrano/rails/migrations'
require 'capistrano/passenger'
Load custom tasks from `lib/capistrano/tasks' if you have any defined
Dir.glob('lib/capistrano/tasks/*.rake').each { |r| import r }
=================================================================
runcap.sh
#!/bin/bash
main()
{
setupenv
archivelogs
printenv
echo -e "\033[104m Server: \033[1m hostname \033[21m"
echo -e " Environment: \033[1m $capenv \033[21m \033[0m"
echo -e "\033[7m Please verify the values above. \033[5m [Enter to Continue]\033[0m"
read
warnenv
read -p "Ready to run task $captask [yY]? " readytorun
if [ x$readytorun = 'xy' -o x$readytorun = 'xY' ]
	then
	echo Running cap $capenv $captask ..
	runcaptask $capenv $captask
else
	echo Come back when ready..
fi

}
archivelogs(){
if  ls $CAPDIR/cap_run.txt &> /dev/null; then
ts=date +"%d%b%Y"
mkdir -p $CAPDIR/logs
(cd $CAPDIR  && tar --remove-files -czf logs/$ts.tgz cap_run.txt)
#(cd $CAPDIR && mv cap_run.txt /tmp)
echo "INFO: Archived logs to logs/$ts.tgz"
fi
}
setupenv()
{
CAPDIR="/home/testuser/apps"
CAPEXE="/home/testuser/.rbenv/versions/2.1.5/bin/cap"
<EMAIL_ADDRESS>export CAPDIR CAPEXE MAILRECIP
}
emaillogs()
{
test -p sock || mkfifo sock
(echo 'set realname="Capistrano QA Buildserver"'; echo 'set<EMAIL_ADDRESS>echo 'set use_from=yes') > sock &
mutt -x -F sock  "$MAILRECIP" -a "$2"  -s "Cap $3 from $1 date '+%Y/%m/%d %H:%M'"  <<-EOF
EOF
}
readtag()
{
echo
read -p "Enter BRANCH value or leave blank to use trunk as repository: " BRANCH
export BRANCH
echo
}
printenv()
{
echo "Select Target environment"
echo "1). Development"
echo "2). Staging"
echo "3). Production"
read -p 'Enter target environment number [1,2]: ' capenv
case $capenv in
1) export capenv=development
warnenv 'dev';;
2) export capenv=staging
warnenv 'qa';;
3) export capenv=production
warnenv 'prod';;
*)
echo Invalid environment.. exiting..
exit 1
;;
esac
printmenu
}
warnenv(){
if [ -n "$1" ] && [ expr match ${HOSTNAME} $1 -ne 0 ]; then
true
else
echo -e "\033[104m Selected environment does not match server naming convention, please
verify. \033[0m"
read "Enter any key continue or CTRL+C to exit"
fi
}
printmenu()
{
echo -e '\nSelect Cap Task'
echo "1). deploy (Idempotent - Cold + Incremental)"
echo "2). deploy:restart"
read -p 'Enter Cap Task number [1-2]: ' captask
case $captask in
1)
export captask="deploy"
readtag
;;
2) export captask="deploy:restart";;
*)
echo Invalid Cap Task.. exiting..
exit 1
;;
esac
}
runcaptask()
{
if [ -d $CAPDIR ]
then
cd $CAPDIR
CAPERRFILE=$1_cap_run_error.txt
CAPOUTFILE=$1_cap_run_out.txt
test -f $CAPERRFILE && rm -f $CAPERRFILE
test -f $CAPOUTFILE && rm -f $CAPOUTFILE
$CAPEXE $1 $2 1>&2 | tee >( grep -v '** [err ::' > $CAPOUTFILE ) >( egrep "** [err ::|rolling back|Not a valid URL" > $CAPERRFILE)
sleep 2
if [ -s $CAPERRFILE ]
then
echo -e "\n === Errors encountered during the load, error file will be emailed.. ====\n"
emaillogs $1 "$CAPERRFILE" "Error log"
fi
sed -i 's/--username.*--no-auth-cache/--no-auth-cache/g' "$CAPOUTFILE"
emaillogs $1 "$CAPOUTFILE" "Output log"
else
echo capdir "$CAPDIR" does not exist.. exiting 1
exit 1
fi
}
main


Feature/multi backend

This PR is a major refactor of SELF that leverages OO Fortran to define method concretizations for specific architectures.

@garrettbyrd  - Please resolve any outstanding comments or provide additional feedback if I need to take care of anything else. If all looks good, please approve the changes so we can merge into main.


Optimize TopicPolicies#replicationClusters with HierarchyTopicPolicies

Motivation
This is one of the serial topic policy optimization with HierarchyTopicPolicies.
Update topic policy with HierarchyTopicPolicies comes with these benefits:

All topic policy related settings will goes into AbstractTopic#topicPolicies, easier to understand, check, review, and modify.
Unify policy update to AbstractTopic. And easier to find which policy is not applied to non-persistent topic yet. And we can easily add support for it.
Unify policy value with 3 level settings (topic/namespace/broker), and priority with topic > namespace > broker.  And it's easier to find which level settings is missing.
All values are updated at creation or by trigger. We can save some resource to update it or recalculate each time we use it.
etc.

Modifications
Add new field replicationClusters in org.apache.pulsar.broker.service.AbstractTopic#topicPolicies.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as

PersistentTopicTest

Some checklist for updating topic policy with HierarchyTopicPolicies.

[x] Broker level value set (no broker level value).
[x] Namespace level value updated.
[x] Topic level value updated.
[x] Pre-existing unit test covers this change and updated to verify this change.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[x] no-need-doc

Code optimization.

/pulsarbot run-failure-checks


fix: demo library README is still rst

Follow up to #587

CI/CD was failing - demo library is still in rst format, we shouldn't have changed it there.


MINOR: increase RocksDb parallelism

cc @mjsax @dguy @guozhangwang
(Pardon the extra merges, I had a mistake in trunk, the actual line change is just 1)

LGTM! Merged to trunk and cherry-picked to 0.10.2.


Splash screen missing version number

When opening the application it shows version 0.0.0

Thanks @MartLeib


Added correct parameters for create

This PR

Updates the Documentation

Describe the changes below:
Added correct parameters to TextureManager.create, source can take an either a HtmlIamgeElement, or an array.
Width and height are optional.

Good catch. Can also take a canvas element or array of them! Will update for that locally.


cxxopts: Add limits header

needed for numeric_limits
Upstream-Status: Pending
Signed-off-by: Khem Raj<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

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

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

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

Can you please open a Jira and explain what error did you encounter following the format of other commits on the project?

Can you please open a Jira and explain what error did you encounter following the format of other commits on the project?

I dont have JIRA account etc. and I am not a regular contributor/developer for this component. this was more for awareness for the devs to fix this if the pull is not sufficient, feel free to ignore it.

thank you for your contribution, I have created a jira issue to track this problem MINIFICPP-1523

@kraj : please fix the linter error:
/Users/runner/work/nifi-minifi-cpp/nifi-minifi-cpp/libminifi/src//utils/StringUtils.cpp:22:  Found C++ system header after other header. Should be: StringUtils.h, c system, c++ system, other.  [build/include_order] [4]

You can verify by running "make linter"

@kraj : thanks for fixing this!
You can subscribe to nifi dev list ( https://nifi.apache.org/mailing_lists.html ) and request contributor access there.
After doing so, you can create and assign tickets to yourself.


proposal: role based authorization

background
usually you have at least 4 groups of persons accessing a tool like that:

global admins (full access to everything, everywhere)
project admins (full access to a project - only)
project users (specific action permissions in a project, e.g ability to click the build button but not modding an inventory etc)
readonly users (no action permissions, never)

what I currently see in semaphore is 1. and partly 2 with some kind of non-admin access which basically is not what I would expect when thinking of a "non-admin" user.
Semaphore already has the ability to choose team members for a project which is great and should "just" ;) be extended to a more specific role / group based system. I have not looked into LDAP yet but when implementing that it should match LDAP groups/netgroups in order to make use these here, too (e.g. LDAP group "semaphore_projectadmin_abc" will become a project admin of project "abc" in semaphore).
Permissions
global admin permissions

like the current admin user
all permissions of a project admin but for every project (see next topic)

project admin permissions
basically this is what an admin and even a non-admin user (when added as a team member) can do already except the user management part, of course.
when a user is added to a project and having project admin rights he should have the permission to:

add/remove other team members
set/unset a team member as project admin
set/unset a team member as project user

set/unset a project user permissions: allow edit inventories/repos/..., allow to build/rebuild, ..

set/unset a team member as readonly user
full access to everything in that project, i.e. add/remove inventories, tasks, etc and do actions (build,rebuild etc)

project user permissions

whatever has been set by an admin or project admin (see above)

readonly user permissions

basically view / show everything where that user is member of - without any ability to modify
optionally it would be nice to block changes of the own account (password, mail,..) so one can share that account with a wider audience

conclusion
I strongly believe that enterprise users require the above and that prevents them for actually using semaphore or at least offer it to their users. I would really appreciate seeing the above or at least parts of it in semaphore as actually atm I cannot share it with others  without these changes..  I would love to contribute but absolute zero experience with Go - while I really love the look & feel & idea of semaphore..
for a first run I would be more then happy if we could have a readonly user permission and a simple project user permission where everything is blocked but actions like build/rebuild are allowed. The rest would be step 2..N then :)
refs:

https://github.com/ansible-semaphore/semaphore/pull/405
https://github.com/ansible-semaphore/semaphore/pull/413
https://github.com/ansible-semaphore/semaphore/issues/368
https://github.com/ansible-semaphore/semaphore/pull/310

This makes a lot of sense. Currently, we cannot give access to semaphore to developers or analysts because that would give them too much permissions (easy to break something by mistake).
The roles mentioned make sense, devs would be project users, analysts readonly users.
As for the LDAP, I would suggest adding an external id field to the project. If a user is in a group that matches that id, it is added to the project's team (kind of what exists in bookstack).

Does this PR allow for per-task permissions?
i.e. I need to allow a user to run a specific task (but not all tasks) belonging to a project.

One additional note: the implementation also should handle access tokens (see https://github.com/ansible-semaphore/semaphore/issues/1391)

Hi @steadfasterX do you still use Semaphore?

Every day 👍😎

@steadfasterX Glad to hear that :) Do you have any wishes or suggestions for improving the Semaphore?

@steadfasterX Glad to hear that :) Do you have any wishes or suggestions for improving the Semaphore?

yesss.. :)
there is one major pain point atm (1344):

sharing tasks between different projects
exporting & importing tasks (incl all dependencies like env, inventory) with other semaphore instances
exporting & importing a view (incl all tasks and its dependencies like env, inventory, etc within)

and an important regression - importing a project backup has issues:

the survey variables do not get imported at all (while they exist in the backup)
the cron gets imported but never fire - deleting the cron entry, saving, re-add works though

and some other regressions (from high to low prio ;) ):

when using the task editor to add a survey variable you can only choose between "string" and integer but I often need "boolean" instead. the reason is that "string" will place it with quotes forcing ansible to use it as string and integer does not allow to input a string.. this makes it harder to do stuff like when: myvar within ansible (when: myvar | bool is a workaround but that is annoying to do on tons of existing stuff)
no proper time display
admin permissions required for the API (should be part of the RBAC so you can choose e.g. to allow starting a task ir just readonly etc)
especially the environment screen is very hard to use when you have multiple envs and want to find the edit button for it on big screen monitors..
tasks which produces a LOT of output (hundreds of lines) will totally mess-up the whole output


Enterprise watermark is shown even when enable_enterprise_modules is not set to True

In version 0.3.3, even when enable_enterprise_modules is not set to True, the grid shows the enterprise watermark saying "for trial use only".
(in lower right corner, for a couple seconds, and fades way)
It doesn't happen when running locally (localhost), but it does in production (when Streamlit is running behind a reverse proxy, etc.)
I checked version 0.3.2, and it's ok (no enterprise message in that same conditions, as expected).
This problem is in version 0.3.3 only.

Never mind. It turns out that enable_enterprise_modules is True by default now (in version 0.3.3).
My mistake. =)
I think it would be better to be set to False by default in this case, though.
(community/free software license, if not told otherwise)


Does not detect keyboard

The program does not detect my Lenovo Thinkpad X270's integrated keyboard as a device which can turn the backlight back on after it has been turned off. All mice devices lights it up correctly.
In the help menu it says:
-i ignore an input device
This device does not re enable keyboard backlight.
Separate multiple device by space.
Default: use all mice and keyboard.
So I assume that it should use keyboard pressing as a trigger too, right?

That's correct could you post he output of  ls /dev/input/by-path

Here you go:
$ ls -l /dev/input/by-path/
total 0
lrwxrwxrwx 1 root root 10 Apr 29 17:52 pci-0000:00:14.0-usb-0:8:1.0-event -> ../event19
lrwxrwxrwx 1 root root  9 Apr 29 17:52 platform-pcspkr-event-spkr -> ../event8
lrwxrwxrwx 1 root root  9 Apr 29 18:06 platform-thinkpad_acpi-event -> ../event7

I'm guessing the internal keyboard is missing from there because according /proc/bus/input/devices the internal keyboard is event0 under /dev/input/
# cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd leds event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I'm using openSUSE Leap 15.2 Beta, kernel: 5.3.18-lp152.11-default

That's the problem. I think it's a great idea to read the devices from   /proc/bus/input/devices I'll implement this in the next couple days

Also one question (I don't think a separate issue is needed): If my keyboard backlight is off and I start the keyboard_backlight and then turn on the backlight manually after that (by hitting fn+space). Then the keyboard_backlight does not turn off the keyboard backlight after X seconds/idle timeout I've set. It only works if the keyboard light is turned on before starting the keyboard_backlight.
Is this intentional feature? I think the keyboard_backlight should always turn off the keyboard backlight if it's turned on after the idle timeout, right? (even if the user has changed the keyboard backlight status manually while keyboard_backlight is running)

That's another bug I'd say but an easy to fix one :)

I'm trying to build the latest git version now but the compiled executable seg faults when I'm trying to start it:
localhost:~/x270/keyboard-backlight/build # export CC=/usr/bin/gcc-8
localhost:~/x270/keyboard-backlight/build # export CXX=/usr/bin/g++-8
localhost:~/x270/keyboard-backlight/build # cmake ../ && make
-- The C compiler identification is GNU 8.2.1
-- The CXX compiler identification is GNU 8.2.1
-- Check for working C compiler: /usr/bin/gcc-8
-- Check for working C compiler: /usr/bin/gcc-8 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++-8
-- Check for working CXX compiler: /usr/bin/g++-8 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /root/x270/keyboard-backlight/build
Scanning dependencies of target keyboard_backlight
[ 50%] Building CXX object CMakeFiles/keyboard_backlight.dir/kbd_backlight.cpp.o
/root/x270/keyboard-backlight/kbd_backlight.cpp: In function ‘void parse_opts(int, char* const*, std::vector<std::__cxx11::basic_string<char> >&, long unsigned int&, MOUSE_MODE&, std::__cxx11::string&, bool&, long int&)’:
/root/x270/keyboard-backlight/kbd_backlight.cpp:274:24: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]
   if ((MOUSE_MODE::ALL > mode) | (MOUSE_MODE::NONE < mode)) {
        ~~~~~~~~~~~~~~~~^~~~~~
[100%] Linking CXX executable keyboard_backlight
[100%] Built target keyboard_backlight

localhost:~/x270/keyboard-backlight/build # ./keyboard_backlight
Segmentation fault (core dumped)

I've set the environment variables to use gcc/g++ v8(.2.1) because if I use the openSUSE Leap 15.2 default gcc/g++ version (7.5.0) it does not recognize "#include " and if I try with "#include <experimental/filesystem>" the compilation fails even it finds the filesystem's headers.
Is there some possiblity to use debug build or something else to detect what exactly causes the seg fault here?

I wasn't able to build the project with gcc8 at all. I've added the necessary lib to enable building with gcc8 properly. I might be possible that this lead to segfault too.
You can check out the lastest dev version and build it with cmake -DCMAKE_BUILD_TYPE=Debug .. to enable debug logs.

Thanks, now the dev branch built OK and doesn't seg fault anymore. And now the keyboard backlight lights up even I change the status of the backlight manually (fn+space). And it detects now my keyboard correctly too!
The only misbehaviour I found now is that if I disable the backlight manually (fn+space) and after the idle timeout I move mouse / use keyboard the program lights up the backlight (even I was manually turned it off). So there's no possibility to turn off the backlight if the program is running (the program will turn it on always).

This only happened if you turn the lights off and afterwards do not move the mouse or press another key before the timeout is over. Should be fixed in the latest commit. Thanks for reporting it.

Thank you very much! Now it's perfect (re-compiled your dev branch once again and everything works) :)
You can close this issue now if you want to.


Declaration of SepaQr\SepaQr::getWriter must be compatible...

First of all, thanks very much for creating SepaQR!
This is the error I'm getting though:
Fatal error: Declaration of SepaQr\SepaQr::getWriter($name = NULL) must be compatible with Endroid\QrCode\QrCode::getWriter(?string $name = NULL): Endroid\QrCode\Writer\WriterInterface in ..SepaQr/SepaQr.php on line 11
I do manage to create QR codes using: https://github.com/endroid/qr-code - but something goes wrong when I try to use SepaQR. Not sure what I'm doing wrong !
I'm not really sure how to adjust the functions without keeping on getting errors.
Can anyone help me please?

I assume you're using version 2.3.0 of this library?
Can you check your composer.lock file to see which version of endroid/qr-code you're using? It should be >=2, <3.

Yes, that's correct!
 "name": "smhg/sepa-qr",
- "version": "v2.3.0",

and
 endroid/qr-code
 "endroid/qr-code": "^2.5",
 "php": ">=5.6"

Update: sorry you can remove this topic - I cleared all files & just started again and it seems to work now :-)
sorry for waisting your time!!

No problem! Thanks for the update!


Allow explicitely requesting upsert for documents

ODM automatically decides whether a document should be inserted or upserted based on whether or not it has an identifier. The logic requires that the identifier is set manually before persist is called. This does not work when using custom ID generators. This is illustrated in #1422.
The best way would be to specify a storage strategy at the document level, specifying whether a document should be written using insert (default) or upsert. This would also allow supporting the $setOnInsert operator that was added in MongoDB 2.4.
Note: this is currently scheduled for the 2.0.0 milestone due to the required cleanup of collection strategies, as some strategies would not play nice when doing upserts.

as some strategies would not play nice when doing upserts.

I was also thinking to allow changing collection's strategy for the upsert only, namely to use atomisSetArray during normal flush and utilize for instace addToSet during upsert.

I would love to see this too, upsert with $setOnInsert

@alcaeus is it expected behavior then that calling persist on a new document with ID set beforehand will be upserted to MongoDB?
I'm asking to know should I rely on this in my code since I'm using it for updating multiple already existing documents without loading them (they represent a state snapshot for a given time for grouped data).

Yes, that is the expected behavior at this time. We will not changing this for 2.0 either.

is there any clean workaround to this issue ?

@g13013 if you are not relying on $setOnInsert, then assigning an identifier when the entity is created will work to force an upsert. If you want to use $setOnInsert, you'll have to insert data manually using the query builder.

@alcaeus I fixed the issue using the @PrePersist @PreUpdate hooks by calling the generator manually


archaeopteryx.js version 2.0.3a2

Updating Archaeopteryx.js to version 2.0.3a2 (relevant files archaeopteryx.js and forester.js).
SARS-CoV-2 reference tree for December 2023

I just noticed this change was made against master; it should have been against alpha. If you can please resubmit a PR against the BV-BRC-Web alpha branch instead of master.
Thanks!

Good point.
I made a PR against alpha: https://github.com/BV-BRC/BV-BRC-Web/pull/744
-Christian


request help: cannot attach domain automatically (external-dns)?

Issue description
Hi.
I've install APISIX with Ingress controller on GKE Autopilot Cluster.
External-DNS is DNS Record updater for assign Public IP to specific sub-domain.
I need automatic assign & update records, but It does not work.
I create Ingress and waiting few minute until appear Ingress's Public IP, but is not appeared.
I think it's the reason of external-dns failure.
I confirmed Ingress functionality via Public IP of LoadBalancer Service.
Ingress YAML
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: httpserver-ingress
spec:
  ingressClassName: apisix
  rules:
  - host: apisix.dev.test.com # Example
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: httpbin
            port:
              number: 80

Result: Empty Address
NAME                 CLASS    HOSTS                     ADDRESS   PORTS   AGE
httpserver-ingress   apisix   apisix.dev.test.com             80      8s

It's a design? or I can implement this function by other way?
Thank you.
Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
Version: 1.4.1
Git SHA: no-git-module
Go Version: go1.16.15
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64

your Kubernetes cluster version (output of kubectl version):
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.10-gke.600", GitCommit:"2c921d7b040ed9c5a3a1f9407fb109b74d72d0a4", GitTreeState:"clean", BuildDate:"2022-06-02T09:20:24Z", GoVersion:"go1.16.15b7", Compiler:"gc", Platform:"linux/amd64"}

if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

You should add a configuration.
Refer to https://github.com/apache/apisix-ingress-controller/blob/0b999ec1d3087f7bf0037acbe2d398eaa0efab2a/conf/config-default.yaml#L40

@tao12345666333 Thanks Again! It many helps!

You're welcome, so has this issue been resolved?

Yes!
I have re-install apisix/apisix Helm chart with --set ingress-controller.config.ingressPublishService=ingress-apisix/apisix-gateway parameter.
After that, the Ingress start displaying correct Public IP and External-DNS create a A record perfectly!

This should be in to documentation. Thanks @choryuidentify !


⚠ SceneTime has degraded performance

In 2886e41, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 4458 ms

Resolved: SceneTime performance has improved in 4867f64 after 7 minutes.


Add number_as_str field to Order model

I want to merge this change, because for bulkOrderCreate mutation (RFC), user needs to be able importing order number as a string value.

Impact

[x] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Decided to not change Order.number field


Removed warning about NUnit3 Support

With the release of Xamarin.UITest v3.0, it now has NUnit 3 support:
https://www.nuget.org/packages/Xamarin.UITest/

@brminnick yep, we pulled that from the docs yesterday, I'll check to see why that didn't publish.


.Net: Delete / implement remaining [Obsolete] APIs from feature-api-v1.0

Deleted most of the remaining ones, but for the HuggingFaceTextCompletion streaming implementation, rather than throwing, implemented it in terms of the non-streaming implementation so that it "just works".

Will close and re-open against main once https://github.com/microsoft/semantic-kernel/pull/3543 lands.


Fix #2089: StringReader.ready returns always true or throws.

LGTM

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2551/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3295/
Test PASSed.


Undeprecate log2Up and log2Down

They should not be deprecated until zero-width wires actually work. See https://github.com/freechipsproject/firrtl/pull/530.
Obviously the better solution is to make zero-width wires fully work but it's been a year and it hasn't happened. Lots of people are using chisel3 now and are pretty annoyed by the deprecation warnings when they really can't switch to log2Ceil and log2Floor yet.

Related issue:
People have reported problems with this https://github.com/freechipsproject/chisel3/issues/652 and more have complained to me directly.

Type of change: other enhancement

Impact: no functional change

Development Phase: implementation
Release Notes
Undo the deprecation of log2Up and log2Down until zero-width wires work.

Also maybe include a link to a tracking issue for zero width wires, so we can understand why these were undeprecated in the future, when we want to re-deprecate them?

Yeah I think that is sensible, I'll file a meta tracking issue and add a link to it to the comments added here


Updates german language

some lines shortened / same intelligibility

@At1768 great job! I added you to contributors :+1:
Just one thing, use the future tense ("Updates german" not "Update german") or ("Adds feature" not "Added feature") like explained in PR template or  in Contributing guidelines. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.
welcome

@grm34 Wow thank you very much! Of course, I will follow your advice and I am also happy about it so that I do it correctly. I have just activated the notification (bell) (was off by default) and now I notice everything much faster. ;)


build: only deploy for 1 node version

fixes #2

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


links parsing fails

Hi, I currently have an issue with links (I might missuse typst so), in this example the first link is correctly parsed, but the next two give shortened urls (to the dash) :
#show link: underline

#link("https://domain.name/a-page.html")

https://domain.name/a-page.html

[text](https://domain.name/a-page.html)

If that's a real issue and you have no time to spend on that, I might be able to solve this issue if someone could give me some hints on how to start diving into the code :)

I think the issue is just that URL parsing is very complex, so the automatic detection of URLs was written conservatively to avoid false positives. See here. But since you can always explicitly use #link, I don't think it's a big deal.

That's right, sorry for missing that issue. I'll continue with #link then :)


Alter assertion of flaky test

Goal
The test case assumed that the job would not complete after the latch was released, but internally BackgroundWorker calls shutdown which allows completion of tasks that are already executing.
My fix is to increase the number of latches required to 2 so the Runnable never completes. I've added an assertion to check the latch was counted down instead.

Merge activity

Sep 20, 12:30 PM EDT: Graphite rebased this pull request as part of a merge.


support for .fernignore when generating locally Fixes fern-api/fern#1780

I added support for .fernignore file in the generated directory when fern generate is run locally i.e with --local option. This prevents modification of files not intending to be regenerated.

@SlamChillz would you be up to add a test in generate.test.ts https://github.com/fern-api/fern/blob/c91a4ba9028abd704d6de698510507d751e1ba7b/packages/cli/ete-tests/src/tests/generate/generate.test.ts#L8-L16
I imagine in the test you
1/ init fern
2/ add a .fernignore and some files that are ignored
3/ locally generate
4/ assert the fernignored files continue to exist

@SlamChillz would you be up to add a test in generate.test.ts
https://github.com/fern-api/fern/blob/c91a4ba9028abd704d6de698510507d751e1ba7b/packages/cli/ete-tests/src/tests/generate/generate.test.ts#L8-L16
I imagine in the test you 1/ init fern 2/ add a .fernignore and some files that are ignored 3/ locally generate 4/ assert the fernignored files continue to exist

Oh! A big YES. I sure will.

@dsinghvi, please kindly review. I have implemented the suggested changes and added tests.

@dsinghvi please kindly review.


[FEATURE REQUEST] Change the styling of the Power of knowledge Blogs page to match the Theme of the website

Description
Is your feature request related to a problem? Please describe.
The color scheme of the Power of knowledge Blogs page doesn't match the main color schemes of the website. The buttons are having unnecessary gray gradient effect, while the color theme is different.
Describe the solution you'd like
Match the color schemes of the Knowledge of Blogs page with the Moksh's main theme color
Additional Information
Context

Priority (optional)
High
Program
Gssoc 24

@akshitagupta15june Kindly assign this issue to me, I will fix it in a small amount of time and make the website look magical

go for it!

Thanks @akshitagupta15june

I will create another pull request without merge conflicts @akshitagupta15june

@akshitagupta15june I have raised the new Pull request #1595 and it has no conflicts now.

I want to work in this issue. Please assign me this task.

@Mahimatestgithub it's already done, please checkout for another issue

@akshitagupta15june kindly merge the pr, I have resolved all the conflicts


feat: sitemap

Closes #6

[x] code
[x] todos
[x] conflicts
[x] getDefaultLocalePlaceholder
[x] update demo
[x] docs

[x] configuration
[x] known issues
[x] getDefaultLocalePlaceholder
[x] new recipe

[x] lint
[x] changeset

To be more precise, I'm not fan of having to call the sitemap inside the loop to get the data so if you have some ideas of how the algorithm part could be improved, that would help quite a lot! Otherwise no worries, the integration is still wip so nwtwwhb!


Try Digit == Never by default

It might be possible to get rid of the underscored @_disfavoredOverload by defaulting the Digit type to something like Never rather than Self because then there is no situation where Digit == Self (other than Never). The reason the digit type is itself by default is so that it can propagate from [U]Int throughout ANKFullWidth. This can, however, also be achieved with a Proxy that forwards Self and Digit to a shared implementation.

Hm. While it may work, removing @_disfavoredOverload will make integer literals ambiguous.


Replace the timeout popup with a more descriptive one

The current timeout popup seems a bit off and it gives the feel of a "soft crash" while the world is still being loaded in the background.

This is the proposal for a new popup. Figma

@RominaMarchetti could you attach the final design for this issue, please?

@JorgeDecentraland the design is attached above. I've included it in Pato's comment :)


Fix scrollback issues

@keybase/react-hackers
The old code took the pagination value from the cached phase. Before we plumbed through 'last' and the paginationKey. Turns out the last value from cached can be incorrect (set to true) even though there are more values.
The new code takes the paginationKey from full and cached callbacks, but in the full one (where last is correct) it can blow away the paginationKey if last is true
Additionally we no longer expose last to the rest of the app. if last is true we just remove the paginationKey

We'll do a hotfix build off of this branch (there will be a couple of prs on top of this). Once that's in we can merge it into master


Migrate azure-storage-blob-nio to Test Proxy

Description
Migrates azure-storage-blob-nio to Test Proxy. As part of the migration azure-storage-blob-nio now uses JUnit 5 instead of Groovy/Spock.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Ensure profile, modules, libraries directories exist

This is a fix for https://github.com/phase2/grunt-drupal-tasks/issues/304.  In Drupal 8.2 it requires the existence of the modules, libraries, profiles folders.  If there isn't any corresponding folder in /src, these top level folders were not getting created.

To be clear, the goal here is to make sure /modules, /libraries, and /profiles is created? I raised the question on profiles in #304, but I'm also confused why modules directory needs to be created.

Yes, just making sure all the normally required directories are created.  For example, what if /src doesn't have any custom modules, so /src/modules is missing?  Similar to what is happening for /src/profiles being missing.  Just trying to cover all the required directories since it doesn't hurt to ensure they are created until Drupal is fixed to not require them.


Re-judge submissions after changing test data

I'd like to re-judge the submissions to a certain problem after changing its test data.
Unfortunately this seems to be impossible. May I ask whether there is a way to do so?

It's easy to do, you can submit a new task to judge and the result will be updated
https://github.com/QingdaoU/OnlineJudge/blob/b33e2db7e9bab08f4581dc20d487e9a50dc12490/submission/views/admin.py#L8


Large negative cdf for values near tau

@kiante-fernandez, I noticed that cdf returns a large negative value for values near tau. Do you know if this is an expected edge case or perhaps a bug? I suspect it might be an edge case, but I don't know for certain.
using SequentialSamplingModels
dist = DDM(ν=2.0, α = 1.5, z = .5, τ = .30)
cdf(dist, 1, 0.305)

I was looking at the supplementary material for the Blurton et al., 2012 paper.
I went ahead and tried the source implementation (in R) to check for edge case. It didn't occur, but it made me think that our implementation might benefit from defining a new variable that represents "t - τ" instead of subtracting non-decision time each time in the implementation. Maybe that could help us identify the bug?
# Calculates exp(a) * pnorm(b) using an approximation by Kiani et al. (2008)
exp_pnorm = function(a, b)
{
  r = exp(a) * pnorm(b)
  d = is.nan(r) & b < -5.5
  r[d] = 1/sqrt(2) * exp(a - b[d]*b[d]/2) * (0.5641882/b[d]/b[d]/b[d] - 1/b[d]/sqrt(pi))
  r
}
# Number of terms required for large time representation
K_large = function(t, v, a, w, epsilon)
{
  sqrtL1 = sqrt(1/t) * a/pi
  sqrtL2 = sqrt(pmax(1, -2/t*a*a/pi/pi * (log(epsilon*pi*t/2 * (v*v + pi*pi/a/a)) + v*a*w + v*v*t/2)))
  ceiling(pmax(sqrtL1, sqrtL2))
}
# Number of terms required for small time representation
K_small = function(t, v, a, w, epsilon)
{
  if(abs(v) < sqrt(.Machine$double.eps)) # zero drift case
    return(ceiling(pmax(0, w/2 - sqrt(t)/2/a * qnorm(pmax(0, pmin(1, epsilon/(2-2*w)))))))
  if(v > 0) # positive drift
    return(K_small(t, -v, a, w, exp(-2*a*w*v)*epsilon))
  S2 = w - 1 + 1/2/v/a * log(epsilon/2 * (1-exp(2*v*a)))
  S3 = (0.535 * sqrt(2*t) + v*t + a*w)/2/a
  S4 = w/2 - sqrt(t)/2/a * qnorm(pmax(0, pmin(1, epsilon * a / 0.3 / sqrt(2*pi*t) * exp(v*v*t/2 + v*a*w))))
  ceiling(pmax(S2, S3, S4, 0))
}
# Probability for absorption at upper barrier
Pu = function(v, a, w)
{
  e = exp(-2 * v * a * (1-w))
  if(e == Inf)
    return(1)
  if(abs(e - 1) < sqrt(.Machine$double.eps)) # drift near zero or w near 1
    return(1 - w)
  (1 - e) / (exp(2*v*a*w) - e) # standard case
}
# Large time representation of lower subdistribution
Fl_lower = function(t, v, a, w, K)
{
  F = numeric(length(t))
  for(k in K:1)
    F = F - k / (v*v + k*k*pi*pi/a/a) * exp(-v*a*w - 1/2*v*v*t - 1/2*k*k*pi*pi/a/a*t) * sin(pi*k*w)
  Pu(v, a, w) + 2*pi/a/a * F
}
#Online supplementary material for Blurton et al.
# Small time representation of the upper subdistribution
Fs_lower = function(t, v, a, w, K)
{
  if(abs(v) < sqrt(.Machine$double.eps)) # zero drift case
    return(Fs0_lower(t, a, w, K))
  S1 = S2 = numeric(length(t))
  sqt = sqrt(t)
  for(k in K:1)
  {
    S1 = S1 + exp_pnorm(2*v*a*k, -sign(v)*(2*a*k+a*w+v*t)/sqt) -
      exp_pnorm(-2*v*a*k - 2*v*a*w, sign(v)*(2*a*k+a*w-v*t)/sqt)
    S2 = S2 + exp_pnorm(-2*v*a*k, sign(v)*(2*a*k-a*w-v*t)/sqt) -
      exp_pnorm(2*v*a*k - 2*v*a*w, -sign(v)*(2*a*k-a*w+v*t)/sqt)
  }
  Pu(v, a, w) + sign(v) * ((pnorm(-sign(v) * (a*w+v*t)/sqt) -
                              exp_pnorm(-2*v*a*w, sign(v) * (a*w-v*t)/sqt)) + S1 + S2)
}
# Zero drift version
Fs0_lower = function(t, a, w, K)
{
  F = numeric(length(t))
  for(k in K:0)
    F = F - pnorm((-2*k - 2 + w)*a/sqrt(t)) + pnorm((-2*k - w)*a/sqrt(t))
  2*F
}
# Lower subdistribution
F_lower = function(t, v, a, w, sigma2, epsilon)
{
  a = a / sqrt(sigma2)
  v = v / sqrt(sigma2)
  K_l = K_large(t, v, a, w, epsilon)
  K_s = K_small(t, v, a, w, epsilon)
  F = numeric(length(t))
  i = (K_l < 10*K_s)
  if(any(i)) F[i] = Fl_lower(t[i], v, a, w, max(K_l[i]))
  if(any(!i)) F[!i] = Fs_lower(t[!i], v, a, w, max(K_s[!i]))
  F
}
# Upper subdistribution
F_upper = function(t, v, a, w, sigma2, epsilon)
{
  F_lower(t, -v, a, 1-w, sigma2, epsilon)
}

F_lower(t = 0.305, v = 2.0, a = 1.5, w = .5, sigma2 = 1,  epsilon = 1.0e-12)

Thanks @kiante-fernandez. This is helpful. I think the best approach is to define unit tests which target the helper functions above. In the process of setting up the tests, I found one issue. The following test disagrees with the R code (assuming it is the ground truth):
test_val2 = _K_large(DDM(;ν=1.5, α=.50, z=.25, τ=.50), .501; ϵ = 1e-10)
 @test test_val2 ≈ 36

which is based on K_large(.001, 1.5, .5, .25, 1e-10)
The Julia code returns 37. I have not had time yet to diagnose the problem, but it could potentially be related to the negative value.  I'll continue adding unit tests to the ddm_cdf branch as time permits.

I'm also not finding F_upper in the Julia code. I thought maybe it is integrated into another function, but I'm not seeing it.

I found three errors in the function _Fs_lower. cdf tests now work with t near tau. Another issue is that the for loop in this function does not work for K=0. I"m not sure if that is ever a value that is used.
@kiante-fernandez, would you like to look into the issue with _K_large?

I'm also not finding F_upper and F_lower in the Julia code. I thought maybe they are integrated into another function, but I'm not seeing them.

They are the cdf in our case.

I found three errors in the function _Fs_lower. cdf tests now work with t near tau. Another issue is that the for loop in this function does not work for K=0. I"m not sure if that is ever a value that is used.
@kiante-fernandez, would you like to look into the issue with _K_large?

Yep I can take a look today!

@kiante-fernandez, I wanted to follow up in case you didn't see my chat message at ICCM. What a nice surprise! I won't be going to the in person event due to a knee injury unfortunately. It was nice running into you.

Ah, I just realized I missed it. My internet connection was quite bad. It was a pleasant surprise to run into you. It's nice to know we are involved in similar circles :)

I found three errors in the function _Fs_lower. cdf tests now work with t near tau. Another issue is that the for loop in this function does not work for K=0. I"m not sure if that is ever a value that is used.
@kiante-fernandez, would you like to look into the issue with _K_large?

F_lower(t = 0.005, v = 2.0, a = 1.5, w = .5, sigma2 = 1,  epsilon = 1.0e-12)

will also return a negative value. looks like a special case.
I ran the test for the _K_large function. The only difference in results between the R and Julia _K_large functions was the misplacement of a (). I will pass the test with the next pull request. I rewrote it to more explicitly follow the R implementation.
I also found some bugs in _Fs_lower. Also fixed.
I will put the PR once I do some final checks on the rest of the functions.

Hi Kiante,
Thanks for looking into that. On Sunday,  I did fix some bugs in _Fs_lower and write some tests on branch ddm_cdf (see above). I went ahead and merged those changes into master. Can you pull those changes and resolve with your PR?

I think we can close this now.

Yup. Thanks for the reminder.
By the way, I think you can do something like closes #issue_number, to automatically close the issue once the PR is merged.


Update scope first and meteor on background.

My angular app create controls on a canvas and we can move it with keyboard arrow.
I create link between my angular model and meteor. After that, moving is very slow.
I think view is update after meteor mongo server.
There is a bouncing  solution ?
Before meteor

After meteor

GroundDB I thought could help me, but it changes nothing.

This seems like an interesting case @simonbonjean.
What do you mean by creating a link between angular model and meteor? Have you used $meteorObject? What parameters have you given it?
If you can share your code, that would be great.

closing as there wasn't a response.
Also, we significantly changed our API in Angular Meteor 1.3 so it won't be an Angular specific problem


Update akka-stream, akka-stream-testkit to 2.6.16

Updates

com.typesafe.akka:akka-stream
com.typesafe.akka:akka-stream-testkit

from 2.6.15 to 2.6.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch

Superseded by #231.


[test/recipes] Split test_fuzz into separate recipes

Continuing on the great work done by @DDvO in the previous episodes, this PR tries to improve the execution time of the test suite on platforms that can leverage high level of parallelism.
Suggestion for reviewers: review the diff commit by commit, as the one moving the fuzz corpora is massive but did not change anything other than moving files into the new 16 subdirectories.
Commits breakout
The individual commit messages contain the following descriptions, I am just summarizing them up here for the sake of describing what the PR does overall.
[test/recipes] Split test_fuzz into separate recipes
When using HARNESS_JOBS to run the tests in parallel, no matter the
level of parallelism that can be used, the monolithic test_fuzz takes
a long time to run, conditioning the duration of the whole build.
This commit splits the single test_fuzz recipe into separate recipes
for each fuzzer.
The previous mechanism to select individual fuzz tests using the
FUZZ_TESTS environment variable is also dropped (and documentation
updated).
[test/recipes] Split asn1 fuzzer recipe into 16 subgroups
NOTE: this commit is intentionally incomplete, leaving the renaming of corpora files to the following squash! commit for ease of review.
Even after separating the "very slow" fuzz tests into their own recipes,
the asn1 recipe took considerably longer than any other to run.
This commit further splits the original asn1 test_fuzz target into
16 individual subgroups, numbered from 0 to f.

To run all the asn1 fuzz tests sequentially one could run
make TESTS='test_fuzz_asn1_*' test

To selectively run only some asn1 fuzz test subgroups (e.g., 9 and
b):
make TESTS='test_fuzz_asn1_9 test_fuzz_asn1_b' test

To run all the fuzz tests:
make TESTS='test_fuzz_*' test

squash! [test/recipes] Split asn1 fuzzer recipe into 16 subgroups
This just moves around the existing corpora files like this:
for i ({0..9} {a..f}) ; do
 mkdir -p fuzz/corpora/$i
 git mv ${i}[0-9a-f]* fuzz/corpora/$i/
done

Performance evaluation
Before this PR:
; make HARNESS_JOBS=64 test
All tests successful.
Files=230, Tests=3582, 181 wallclock secs ( 9.33 usr  0.54 sys + 791.95 cusr 190.37 csys = 992.19 CPU)
Result: PASS

After the first commit of this PR, splitting the monolithic test_fuzz recipe into individual recipes:
; make HARNESS_JOBS=64 test
All tests successful.
Files=223, Tests=3593, 132 wallclock secs ( 8.24 usr  0.53 sys + 790.32 cusr 181.24 csys = 980.33 CPU)
Result: PASS

After the last commit of this PR, further splitting test_fuzz_asn1 into 16 subgroups:
; make HARNESS_JOBS=64 test
All tests successful.
Files=238, Tests=3623, 91 wallclock secs ( 7.88 usr  0.56 sys + 828.43 cusr 183.56 csys = 1020.43 CPU)
Result: PASS

Original description
Commits breakout
The individual commit messages contain the following descriptions, I am just summarizing them up here for the sake of describing what the PR does overall.
Dedicated runs for asn1, client and server fuzzers
When using HARNESS_JOBS to run the tests in parallel, no matter the
level of parallelism that can be used, the monolithic test_fuzz takes a
long time to run, conditioning the duration of the whole build.
This commit splits the three longest running fuzz tests into their own
individual test runs (disabled if FUZZ_TESTS is set, in which case only
the main test_fuzz recipe is run).
Split asn1 fuzzer recipe into 16 subgroups
Even after separating the "very slow" fuzz tests into their own recipes,
the asn1 recipe took considerably longer than any other to run.
This commit further splits the original asn1 test_fuzz target into 16
individual subgroups, numbered from 0 to f.

To run all the asn1 fuzz tests sequentially one could run
make FUZZ_TESTS='asn1/*' TESTS=test_fuzz test

To selectively run only some asn1 fuzz test subgroups (e.g., 9 and b):
make TESTS='test_fuzz_asn1_9 test_fuzz_asn1_b' test

To run all the fuzz tests sequentially:
make FUZZ_TESTS='all' TESTS=test_fuzz test

The last 2 commits
The last 2 commits are meant to be dropped: they are there for reviewers to test the performance difference between the 3 different versions ("before this PR", "splitting the very slow targets (and asn1 in subgroups)", "splitting the very slow targets (but keep asn1 monolithic)").
Execution time of the test suite
I ran the test suite on a rig with 64 logical cores, the build itself is a debug build with -O0 and sanitizers to compare the gains obtained by splitting test_fuzz for frequent/repeated builds.
; make HARNESS_JOBS=64 FUZZ_TESTS=all VF=1 test # runs the FUZZ_TESTS sequentially like before this PR
All tests successful.
Files=230, Tests=3582, 181 wallclock secs ( 9.33 usr  0.54 sys + 791.95 cusr 190.37 csys = 992.19 CPU)
Result: PASS

; make HARNESS_JOBS=64 VF=1 test # client, server, and asn1 are split (but asn1 is monolithic)
All tests successful.
Files=215, Tests=3585, 139 wallclock secs ( 8.66 usr  0.56 sys + 795.51 cusr 181.91 csys = 986.64 CPU)
Result: PASS

; make HARNESS_JOBS=64 VF=1 test # client, server, and asn1_* are split
All tests successful.
Files=230, Tests=3615, 88 wallclock secs ( 8.46 usr  0.51 sys + 819.46 cusr 182.74 csys = 1011.17 CPU)
Result: PASS

(force pushed to fix some typos in the commit messages and to split the massive fuzz/copora/asn1/* move into its own squash! commit to ease review)

As usual I am not hyperconfident on my perl-fu, so please @levitte and @DDvO check that I did not write something that makes little sense and that could be improved stylistically or in any other way that is obvious to perl pros!

https://github.com/google/oss-fuzz/blob/master/projects/openssl/build.sh needs to be patched if this PR is merged:
zip -j $OUT/${fuzzer}_seed_corpus.zip fuzz/corpora/${fuzzer}/*

assumes that the corpora for each fuzzer has no subdirectories, and this PR changes that.
@kroeckx I see you are the last author on that file: do you know enough about the project to be able to say if this patch would be the correct solution?
diff --git a/projects/openssl/build.sh b/projects/openssl/build.sh
index 14768c97..7def4f9a 100755
--- a/projects/openssl/build.sh
+++ b/projects/openssl/build.sh
@@ -25,11 +25,12 @@ fi

 make -j$(nproc) LDCMD="$CXX $CXXFLAGS"

+OUT=$(realpath -e ${OUT})
 fuzzers=$(find fuzz -executable -type f '!' -name \*.py '!' -name \*-test '!' -name \*.pl)
 for f in $fuzzers; do
        fuzzer=$(basename $f)
        cp $f $OUT/
-       zip -j $OUT/${fuzzer}_seed_corpus.zip fuzz/corpora/${fuzzer}/*
+    ( cd fuzz/corpora/${fuzzer}; zip -j $OUT/${fuzzer}_seed_corpus.zip ./* )
 done

 cp $SRC/*.options $OUT/

This PR does not really do anything for Travis builds apparently, so its benefits are limited to builds on platforms that can leverage more parallelism.

Github refuses to show me everything...  I only get to see the first 3000 changed files, so yeah, a lot of corpora renames.  That makes this really hard to review.
It might be better to have one PR for each fuzzing test you're breaking out

@levitte in the review tab you can select to show the changes commit by commit, that should do the trick!

CI's are relevant I suspect.

If you're going to split it all according to what was possible to say with FUZZ_TESTS, why not just drop that environment variable and use the recipe names for selection?
This is said with the assumption that you have read test/README.md, and in particular, https://github.com/openssl/openssl/blob/master/test/README.md#running-selected-tests

I did not split all of them: only the slowest ones (client, server, asn1)
have separate recipes, most of the fuzzing still happens within the main
test_fuzz (which keeps being the one serving the FUZZ_TESTS functionality).
Is the suggestion to drop FUZZ_TESTS all together and just have individual
recipes for each task in test_fuzz?
On Wed, Nov 4, 2020, 11:44 Richard Levitte<EMAIL_ADDRESS>wrote:

If you're going to split it all according to what was possible to say with
FUZZ_TESTS, why not just drop that environment variable and use the
recipe names for selection?
This is said with the assumption that you have read test/README.md, and
in particular,
https://github.com/openssl/openssl/blob/master/test/README.md#running-selected-tests
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/pull/13307#issuecomment-721626298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACST4QIN7NL6FRHNXSQTRDSOEPBHANCNFSM4TJLLQBQ
.

Is the suggestion to drop FUZZ_TESTS all together and just have individual recipes for each task in test_fuzz?

That is my suggestion, yes.  It will make each of them more visible in the non-verbose test, and we get back to one test selection mechanism instead of two that work almost, but not quite the same.

Is the suggestion to drop FUZZ_TESTS all together and just have individual recipes for each task in test_fuzz?

That is my suggestion, yes. It will make each of them more visible in the non-verbose test, and we get back to one test selection mechanism instead of two that work almost, but not quite the same.

Force pushed with the suggested change, FUZZ_TESTS is no more, and I should have edited all the various README to reflect this.

CI's are relevant I suspect.

@paulidale I only saw a failure due to https://github.com/openssl/openssl/pull/13307#issuecomment-721439557 , which is external: am I missing something else?

(updated the description to sync up with the current version)

@levitte when I mentioned the GitHub feature to see subset of the changes for reviewing, I meant this:

@levitte when I mentioned the GitHub feature to see subset of the changes for reviewing, I meant this:

.... so essentially the same thing I ended up doing, to go through the "Commits" tab :wink:

Essentially yes, but doing it from the review tab additionally allows to use all the review tools, leaving comments on specific hunks and marking things as already reviewed!

If I understand the change properly, one of the things you want to do split the corpus in 16, based on the first character of the filename. I'm not sure if this is for asn1 only or not. In theory this makes using the corpus harder, because, as far as I know, I have to undo that change to be able to use the corpus for fuzzing, and at least the instructions in fuzz/README.md then look outdated.
I currently fail to see why oss-fuzz would require any change, because the -j option already removes the path.

@kroeckx said:

If I understand the change properly, one of the things you want to do split the corpus in 16, based on the first character of the filename.

Hmmm...  @romen, I believe you could use fuzz_test arguments like 'asn1/0*' and get away with it, and thereby not have to move any files around...

Hmmm...  @romen, I believe you could use fuzz_test arguments like 'asn1/0*' and get away with it, and thereby not have to move any files around...

I was thinking something like that too, but you're likely to run
into max arguments on some platforms. I guess "xargs" is not
something we can rely on. Does perl have something that can call
the fuzzer multiple times with a correct maximum arguments count?

@kroeckx says:

I was thinking something like that too, but you're likely to run into max arguments on some platforms. I guess "xargs" is not something we can rely on. Does perl have something that can call the fuzzer multiple times with a correct maximum arguments count?

I have no idea what you're talking about.  fuzz_test is a perl function, and it does this with each argument (this is from the new that @romen has worked together):
glob(srctop_file('fuzz', 'corpora', @tokens));

So with @tokens = ( 'asn1', '0*'), glob() should be able to return as big a list as memory allows.

Each platform has a combination of how many arguments you can call
a program with and how big that array might be. If you use xargs,
like "find . -name *.c | xargs grep foo", grep might get called 1
or multiple times, depending on the platforms limits.
If you just use 0*, the list of arguments will be too large for
some platforms. Windows for instance has a limit of 8191
characters for the arguments, and it looks like we'll need
8527 bytes for the current asn1 corpus split in 16.
So the question was, does perl have something that takes those
platform specific limits into account, so that it can be called
multiple times?
Note that we currently don't have such a problem, because we pass
a directory to fuzz program, and it will open the files itself. An
other solution is that we modify that program to have an argument
that says what the first character of the file should be.

@kroeckx said:

If I understand the change properly, one of the things you want to do split the corpus in 16, based on the first character of the filename.

Hmmm... @romen, I believe you could use fuzz_test arguments like 'asn1/0*' and get away with it, and thereby not have to move any files around...

This is a great idea! Perl surprises me every time!!
Thanks!
I just pushed fixup commits and a revert for the big rename.

No, I didn't, I made a mess!

Ok, I accidentally deleted the branch, but I restored it and reopened the PR.
Thansk to @levitte idea and Perl superpowers there is no need to change the structure of the the fuzz/corpora/asn1/ contents, so this should please @kroeckx and also keep the external CI happy!
Thanks @levitte for the feedback so far, it was a nice trip inside Perl!
I believe I addressed all your requests now!
Keep them coming!

Unfortunately I currently do not have time for properly reviewing this.
Just one immediate general comment:
It is not advisable to have many new files test/recipes/99-test_fuzz_*.t that are mostly identical. It should be possible to factor out their common behavior.
I solved a similar issue in https://github.com/openssl/openssl/pull/12359/files by introducing a Perl 'library' file test/recipes/fuzz.pl.

So, originally I kept this structure and only forked out the slowest ones as per the comments you left (plus splitting asn1 that was still too slow in its monolithic version).
@levitte feedback was what triggered the splitting in many separate recipes which simplifies usage at the expense of authorship.
But I believe the authorship cost can be minimized using templating to generate the committed test recipes (or at least that is what I did, so I edited only 3 master files from which I regenerated all the actual recipes).

Please at least use extended tests, so your changes actually get tried in the CI. To do that, you need to have a line with "[extended tests]" in your last commit message.
I'm not convinced this is going to work on all platforms.

Extended tests have been broken for a long time now independently of this PR, but ok, I'll push a commit to trigger them!

It is not advisable to have many new files...

I'm not sure why not? More smaller tests are more visible than one large that takes a long time, and are better for parallelism. Yeahok, that also means a lot of code duplication, which I dislike, but I think the benefits outweigh my distaste in this case.

It is not advisable to have many new files...

I'm not sure why not? More smaller tests are more visible than one large that takes a long time, and are better for parallelism. Yeahok, that also means a lot of code duplication, which I dislike, but I think the benefits outweigh my distaste in this case.

My point was not a multitude of files, but the high redundancy of many mostly identical ones.
As I wrote, It should be possible to move all the redundant code to a Perl lib file holding all generic code,
as done for instance in #12539 with test/recipes/fuzz.pl.

As I wrote, It should be possible to move all the redundant code to a Perl lib file holding all generic code,

You're talking about moving stuff to test/recipes/fuzz.pl (which isn't removed here), but we also need a balance, where it should be easy enough to just look at a recipe and be able to see what it tests, especially for simple ones.  What @romen has done now is to reduce them to something that's still readable in Test::More terms, i.e.:
plan tests => 2;

require_ok('path/to/fuzz.pl');
subtest "Fuzzer whatever" => \&fuzz_test, 'whatever';

If all you know (apart from basic perl) is Test::More, you see immediately that two tests are being done, and at least superficially what they do, and if they want to know more, they can go look in fuzz.pl.  The only real difference compared with the previous fuzz.pl is that the subtest statement to the recipe itself.  That was intentional when I suggested it, in the interest of being able to see immediately what's going on, at least on a superficial level.
Sure, @romen has one or two variables to avoid having to repeat "whatever", but so what?

The macos Travis failure is relevant, seems like $f appears as uninitialized on the version of perl in that platform.
@levitte can you help me understand what I messed up?

@levitte can you help me understand what I messed up?

I gotta confess that I can't currently see how you messed up...  and especially when that only happens on MacOS, it's at least not a obvious perl-level mess...  I'll dig a little more

Nope, can't figure it out by just looking...  I suggest this diff to try and find out what's going on:
diff --git a/test/recipes/fuzz.pl b/test/recipes/fuzz.pl
index 38af4518e8..f3fcc91f61 100644
--- a/test/recipes/fuzz.pl
+++ b/test/recipes/fuzz.pl
@@ -10,6 +10,7 @@ use warnings;

 use OpenSSL::Glob;
 use OpenSSL::Test qw/:DEFAULT srctop_file/;
+use Data::Dumper;

 sub fuzz_test {
     die "Too many arguments" if scalar @_ > 1;
@@ -22,6 +23,10 @@ sub fuzz_test {
     plan tests => scalar @dir;

     my $f = $tokens[0];
+    unless ($f) {
+        diag(Data::Dumper->Dump([   $d, [ @tokens ], $f ],
+                                [qw( d     tokens     f)]));
+    }
     foreach (@dir) {
         ok(run(fuzz(["$f-test", $_])));
     }

You also need this to be able to see the diag output:
diff --git a/.travis.yml b/.travis.yml
index 174e9b182f..1201e7b986 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -239,6 +239,10 @@ script:
               echo -e '\052\052 FAILED -- MAKE TEST';
               travis_terminate 1;
           fi;
+          if ! travis_wait 60 make _tests V=1 TESTS=test_fuzz_asn1_0; then
+              echo -e '\052\052 FAILED -- MAKE TEST asn1-fuzz';
+              travis_terminate 1;
+          fi;
       else
           if ! $make build_tests >~/build.log 2>&1; then
               echo -e '\052\052 FAILED -- MAKE BUILD_TESTS';

This should go into a temporary commit.

As I wrote, It should be possible to move all the redundant code to a Perl lib file holding all generic code,

You're talking about moving stuff to test/recipes/fuzz.pl

I mentioned fuzz.pl just as an example of factoring out code. Likely there is even more elegant ways of doing that.
Currently each of the 27 new .t files contain (besides the unavoidable copyright header and empty lines) 9 actual lines of code, where most of them are identical in each file, and if anything needs to be changed with them, all 27 files need to be adapted consistently.
I still believe this is needless redundancy and think it should be possible to reduce this to 2 actual code lines, something like the following:
use OpenSSL::Test::<whatever_really_needed_here>

do_2_tests_in_fuzz_test_group("asn1", "0");

@levitte 2a51d1c should do the work for having the extra debug info

@DDvO, the example you made there tips the balance to "too much hiding" in my view.  The slippery slope is that all test recipes become library functions, and that's taking things much too far in my view.

@levitte https://travis-ci.com/github/openssl/openssl/jobs/428518435 makes no sense to me :(

Hmmm, you might want to add a die "No arguments?" if scalar @_ == 0; at the beginning of sub fuzz_test for good measure (that should become a permanent change).

Hmmm, you might want to add a die "No arguments?" if scalar @_ == 0; at the beginning of sub fuzz_test for good measure (that should become a permanent change).

Done in 861df50 , but... can you see any reason why that version of perl is passing no argument?

but... can you see any reason why that version of perl is passing no argument?

None whatsoever, it's a real mystery.  I wish I had a Mac handy to figure it out...  unfortunately, I don't.

Aaaargh, it is a version issue.
From https://github.com/Test-More/test-more/blob/master/Changes:

Test-Simple 1.001004_001 2014-May-10 08:39-08:00 PST
    * Doc updates
    * Subtests accept args
    * Outdent subtest diag

(Test-Simple is related to Test::More, they have matching version numbers as far as I know)
A quick check with corelist...
This tells us what to expect from perl 5.18.2 (the version used on MacOS):
$ corelist -v 5.18.2 Test::More
Test::More 0.98

Mystery resolved!  But yeah, that means that you'll have to go back to the less elegant subtest call for now, i.e.:
fuzz_test($fuzzer);

and you'll have to implement fuzz_test like this:
sub fuzz_test {
    die "No arguments?" if scalar @_ == 0;
    die "Too many arguments" if scalar @_ > 1;

    my $d = $_[0];
    my @tokens = split(/\//, $d);
    my @dir = glob(srctop_dir('fuzz', 'corpora', @tokens));
    my $f = $tokens[0];

    subtest "Fuzzing $d" => sub {
        plan skip_all => "No directory fuzz/corpora/$d" unless @dir;
        plan tests => scalar @dir; # likely 1

        foreach (@dir) {
            ok(run(fuzz(["$f-test", $_])));
        }
    };
}

Force pushed, I am abandoning the attempt to split the asn1 corpus into subfolders to make it parallelizable, it's a pity because it really takes a long time, but my understanding is that splitting it into subdirs makes things too hard for @kroeckx when he updates the corpora.
So here it is, the latest version is just splitting the monolithic test_fuzz.t into separate files for each fuzzer and removing the FUZZ_TEST mechanism.

I just updated the description to match the current content of the PR.
I am still not completely surrendering the idea of splitting test_fuzz_asn1 into smaller units, because it really takes too long compared to any other test, but I will leave that effort to another PR and another less busy time!

So Travis failures seem related:
https://travis-ci.com/github/openssl/openssl/jobs/429652020#L4960 (OSX build)
https://travis-ci.com/github/openssl/openssl/jobs/429652017#L5022 (Linux build)
# No directory ../../../../_srcdist/fuzz/corpora/asn1parse
not ok 2 - Fuzzing asn1parse
[repeated for the other fuzzers as well]

It seems to affect only this builds which have in common the environment: CONFIG_OPTS="" DESTDIR="_install"
I'm failing to see why this is the case with the current set of changes. @levitte do you have idea?

I'm failing to see why this is the case with the current set of changes. @levitte do you have idea?

I do.  Before this PR, we simply skipped if the directory isn't there, now we fail instead.  The quick fix is to replace this:
    diag("No directory $d");
    return 0;

with:
    info("No directory $d");
    return 1;

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

But how is the directory missing?

But how is the directory missing?

Our tarballs don't include the fuzz corpora.  That was a choice we made a long time ago, partly because it's a really slow set of tests, and partly because they are tests that should be fixed before releasing, so we don't expect them to ever fail in the releases.

But how is the directory missing?

Our tarballs don't include the fuzz corpora. That was a choice we made a long time ago, partly because it's a really slow set of tests, and partly because they are tests that should be fixed before releasing, so we don't expect them to ever fail in the releases.

Oh, I see!!
I did not make the connection between the DESTDIR env var in Travis and the fact that those jobs are testing a tarball equivalent of the commit.
I preferred to edit the recipe fail to add a plan skip all to mark the test as skipped rather than passing, as it seems more appropriate to me.
Hopefully the CI should give green light this time: @levitte could you check my latest fixup commit and either reapprove or give more feedback?

All tests are passing and @levitte reapproved the PR 11h ago.
I will wait until 2020-10-10 12:00 AM EET before merging this, so that the 24h grace period will have officially expired.

Merged to master with a7da4d488d55f68de50a96bd3027cd9fc650d444
Thanks!


"Failed to Acquire Kernel Access" ...

Using Soundhax on the latest FBI/FastHax combo on my 2DS, I am getting the Failed To Acquire Kernel Access error. I want to install a couple CIA's I've downloaded.

Soundhax gets you into HBL. You need to run fasthax after that before running FBI.


Revise core structures docs

Add a diagram
Discuss Transformations and Measurements in parallel, but highlight where they differ.
Transformation first, then Measurement, since that's the usual flow.

Considered done after being moved to the docs-IN-PROGRESS branch


Fix Beards for helmets

Beards for items such as coifs, med helmets should be fixed now

Can you do the 317 one as well? We're still supporting 317 for a bit, but 377 is just going to be the default.


Refactor to sqlalchemy v2 code style

There are some bugs in the test file, might need another PR to fix.


Fix argparse for python3.10

Closes #29

As soon as python3.10 is available in actions and the release is done, python3.10 should be added to setup.py and tests.yml


OCPNODE-1499: Add support for must-gather collection script

This change introduces a specific must-gather collection script for this operator within the operator image itself, so that it can be used directly in the Openshift' must-gather process.

Checklist

[ x] Commits are signed with Developer Certificate of Origin (DCO)

As this repo is a fork of upstream https://github.com/kedacore/keda-olm-operator, we want our OpenShift-specific changes to be minimal so that we don't have to worry as much about merge conflicts, etc. when we do our periodic upstream rebase operations.
At a miniumum, the cma-verify-history will require that your commit(s) be prefixed with UPSTREAM: <carry>: so that we don't accidentally drop them on the next rebase.
The dockerfile changes should be reverted, and re-applied to our gitlab CPAAS midstream repo (https://gitlab.cee.redhat.com/custom-metrics-autoscaler/cpaas-midstream/-/blob/ocma-2-rhel-8/distgit/containers/custom-metrics-autoscaler-operator/Dockerfile.in)
I am having a hard time deciding whether it's worth updating the root README.md given the doctoc issue you identified. Either way, we'll certainly ask @mburke5678 to change the OpenShift product docs to include this info. What do you think?

This is looking good. I'm ready to give lgtm once the fixup commits are squashed.

This is looking good. I'm ready to give lgtm once the fixup commits are squashed.

Thanks @joelsmith . I squashed the commits and updated the PR. PTAL
The dockerfile changes are captured in the midstream MR.

/CC @mburke5678
For docs updates.

Pushed an update to generate the must-gather version file based on the information provided by the packagemanifest.

/lgtm
/approve
Thanks!

CMA is single stream, hence no backports are needed.


Videos not visible on ios

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
3.0.5

Plugin version
5.4.3+7

iOS version
15

Xcode version
13.4.1

Device information: All ios
Description
Expected behavior:
Go to e.g. https://www.rtlboulevard.nl/video/tv-fragmenten/video/5328092/snelle-reageert-koeltjes-op-verrassing-komt-misschien-niet or https://www.rtlboulevard.nl/video/tv-fragmenten/video/5328092/snelle-reageert-koeltjes-op-verrassing-komt-misschien-niet
Current behavior:
No video shown
It can be a special situation on this site, but in other apps using the sfsafaribrowser view, it works normally. But not in this plugin or the webview_flutter plugin (also filed there https://github.com/flutter/flutter/issues/109939 )
Steps to reproduce

import 'package:flutter/material.dart';
import 'package:flutter_inappwebview/flutter_inappwebview.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatefulWidget {
const MyApp({Key? key}) : super(key: key);
@override
State createState() => _MyAppState();
}
class _MyAppState extends State {
late InAppWebViewController webViewController;
InAppWebViewGroupOptions options = InAppWebViewGroupOptions(
crossPlatform: InAppWebViewOptions(
useShouldOverrideUrlLoading: true,
mediaPlaybackRequiresUserGesture: false,
),
android: AndroidInAppWebViewOptions(
useHybridComposition: true,
),
ios: IOSInAppWebViewOptions(
allowsInlineMediaPlayback: true,
));
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
bottomSheet: Row(children: [
TextButton(
child: const Text('rtlnieuws'),
onPressed: () {
webViewController.loadUrl(
urlRequest: URLRequest(
url: Uri.parse(
'https://www.rtlnieuws.nl/nieuws/video/video/5328094/spannende-minuten-kinderen-vast-attractie-hellendoorn')));
}),
TextButton(
child: const Text('rtlblv'),
onPressed: () => webViewController.loadUrl(
urlRequest: URLRequest(
url: Uri.parse(
'https://www.rtlboulevard.nl/video/tv-fragmenten/video/5328092/snelle-reageert-koeltjes-op-verrassing-komt-misschien-niet'))),
),
]),
body: InAppWebView(
onWebViewCreated: (InAppWebViewController controller) {
webViewController = controller;
},
)));
}
}
Images

Stacktrace/Logcat

By the way, this also happens with Twitter embeds on websites! That's quite something. No video in Flutter Webview for this url: https://www.vrt.be/vrtnws/nl/2022/09/26/protest-dagestan/
In the Swift app, it just works

@woutervanwijk
I am experiencing the very same issue! To me, it happens for youtube videos as well if I embed them into my website. Example: https://www.youtube.com/embed/-r2FX7E_b-Q?controls=1&loop=0&showinfo=0&modestbranding=1&rel=0&modestbranding=1&disablekb=1&autoplay=1&playsinline=0
Have you found a workaround?

An update to 5.4.4+2 hasn't led to any better results.

Have you found a workaround?
Nope!

Here is the same issue for webview_flutter btw: https://github.com/flutter/flutter/issues/109939


Bug in Rally Logic

When deploying a 100 node cluster, I ended up with a 66, a 32 and 2 missing nodes.  Two nodes were marked as rally, so something is wrong in that logic.
I'm not sure what happened to the missing two nodes.

Need to check that the ASG has the desired number of nodes before picking the rally.  This is going to be more complicated for MDS....

I'm pretty sure this is being caused by this: https://github.com/couchbase-partners/amazon-cloud-formation-couchbase/issues/39


Chore : fixed image in List View

Description

Fixed image display in List View of resources page.

Related Issues

Closes #1388

Screenshots / videos (if applicable)

Amazing work @lade6501

Thanks @mdazfar2.


Key 'usageBytes' not found

I am trying to upload a document to a vector store and receive the following error message:
dataCouldNotBeReadMissingData(description: "Key \'usageBytes\' not found: No value associated with key CodingKeys(stringValue: \"usageBytes\", intValue: nil) (\"usageBytes\").codingPath: []")
The vector store was newly created and usage bytes does not seem to get set. The files are correctly uploaded to the OpenAI platform and can be found in the storage.

Can you please share:

your request as curl.
Which API are you using.

The more details the fastest I can solve this, thanks.

I am using the regular OpenAI API.
Unfortunately, I do not know how to get the cURL, but I can share my code.

`class OpenAIService {
func createVectorStore(named name: String) async throws -> VectorStoreObject {
let service = OpenAIServiceFactory.service(apiKey: apiKey)
let storeParameters = VectorStoreParameter(name: name)
return try await service.createVectorStore(parameters: storeParameters)
}
func retrieveVectorStore(id: String) async throws -> VectorStoreObject {
    let service = OpenAIServiceFactory.service(apiKey: apiKey)
    return try await service.retrieveVectorStore(id: id)
}

func uploadFile(_ file: Data, named name: String, toVectorStore vectorStoreID: String) async throws -> VectorStoreFileObject {
    let service = OpenAIServiceFactory.service(apiKey: apiKey)
    let fileParameters = FileParameters(fileName: name, file: file, purpose: "assistants")
    let uploadedFile = try await service.uploadFile(parameters: fileParameters)
    let storeFileParameters = VectorStoreFileParameter(fileID: uploadedFile.id)
    return try await service.createVectorStoreFile(vectorStoreID: vectorStoreID, parameters: storeFileParameters)
}

}`
 let vectorStore = try await openAI.createVectorStore(named: "test") var files: [VectorStoreFileObject] = [] for document in documents {     if let name = document.key, let data = document.value {       let file = try await openAI.uploadFile(data, named: name, toVectorStore: vectorStore.id)       files.append(file)     } }


docs(typo in CONTRIBUTING.md): comitted was changed to committed

in CONTRIBUTING.md @ line:39, comitted was changed to committed

What:

Why:

How:

closed due to merge conflicts


Problem with users using Hide My Email

Hi,
When I hide Email and sign in with Apple, new account created in keycloak with email<EMAIL_ADDRESS>How to get the user's real email? Or is there a way to force users to enter their real email when signing in with Apple?

Hi @tungboom,
Unfortunately, there's no way to get the real email address of the user.
The user decides upon registration whether he wants to share a hidden or his real email address.
I guess, as long as Apple cares about privacy of users, they won't change this behavior.
At least from a developer point of view, there's nothing you can do. It's about the user that signs in to your app.


BED-4570: Resolve panics with IngestibleRelationship

Description

Moved to an initializer for ein.IngestibleRelationship, and refactored all current uses to that initializer.
Fixes some cases where we explicitly created empty ein.IngestibleRelationship structs, which would contain a nil map
Fixed issues with some make([]IngestibleRelationship...) to ensure that the slice length is set to 0 even if the capacity was set to another number, removing the chance of having empty IngestibleRelationship structs in those slices.

Motivation and Context
This PR addresses: BED-4570 | #695
Why is this change required? What problem does it solve?
Removes chances for panics when invalid data is ingested
How Has This Been Tested?
Local testing with reproduction steps from original GitHub issue
Types of changes

Chore (a change that does not modify the application functionality)
Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have met the contributing prerequisites

Assigned myself to this PR
Added the appropriate labels
Associated an issue: https://github.com/SpecterOps/BloodHound/issues/672
Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing

[x] I have ensured that related documentation is up-to-date

Open API docs
Code comments (GoDocs / JSDocs)

[x] I have followed proper test practices

Added/updated tests to cover my changes
All new and existing tests passed

Solid cleanup. Nothing stands out to me.


How to use with passport module

Can anyone show me example how to use passport with restify? I don't have any error but I don't see cookie is set by passport.

Restify is mainly to build stateless api-s - so when using restify, you should not need it


Expose audit feature in kubewarden controller helm charts

Acceptance criteria:
On kubewarden/audit-scanner:

Make the contents of config/ part of GH releases

On kubewarden/helm-charts:

Create CronJob template
Consume new CRDs with spec.backgroundAudit, CronJob, from audit-scanner
Add "rancher annotations" that specify the new dependency on PolicyReports CRD.
Provide Helm values to enable & disable the audit feature, configure the interval of scan
By default the audit feature is enabled
By default the scan interval is: 60 minutes

I suppose this should end in a feature branch for now.

missing making use of GetSeverity(), GetCategory(), etc, and leaving those unset in PolicyReportResults when they are not present.

Closing this as done!


[BugBash] Can reset password and replace AAD with MSA

Scenario 7, per @anangaur

linked my account to AAD
Now I cannot link it to MSA which...
...
Replaces my AAD with MSA

AFAIK this is intentional unless you are
a) in an organization
b) an admin

I am fine with condition a) but not b).
I think we always wanted to do this but due to lack of time, we chose to just block changing the auth from AAD to MSA. This is the behavior from the "Account settings" page. Should be the same for this user flow too.


Uwee docs update

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


build(deps): bump chrono from 0.4.19 to 0.4.20

Motivation
chrono has fixed rust security advisory:
https://rustsec.org/advisories/RUSTSEC-2020-0159
It has also fixed some panic bugs.
Solution

Bump chrono to 0.4.20

Related build / security fixes:

Drop old time crate dependency from chrono

Related clippy fixes:

Fix clippy::assign_op_pattern
Update deprecated constant names

Review
Zebra isn't actually vulnerable to this security issue in our direct use of chrono, but tracing might be, so we should get this merged before the next release.
Reviewer Checklist

[ ] Existing tests pass

We're seeing panics in Zebra, so this is now a high priority.

@mergifyio update

@mergifyio update

@mergifyio update

@mergifyio update