glusterfs: 7.0 -> 7.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/glusterfs/versions.
meta.description for glusterfs is: '"Distributed storage system"'.
meta.homepage for glusterfs is: '"https://www.gluster.org"
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 7.1 with grep in /nix/store/bk4kdv0hgbfj9pd3jb1xm05ydw8z0zwm-glusterfs-7.1

directory tree listing: https://gist.github.com/8d51425332499d86c92416ea68fb93f0

du listing: https://gist.github.com/2afba0459ab9dd14a312b5e74536c278

Rebuild report (if merged into master) (click to expand)

69 total rebuild path(s)
30 package rebuild(s)
30 x86_64-linux rebuild(s)
16 i686-linux rebuild(s)
7 x86_64-darwin rebuild(s)
16 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
bareos
glusterfs
gnome3.gnome-boxes
libguestfs
libguestfs-with-appliance
libvmi
python27Packages.guestfs
python37Packages.guestfs
python38Packages.guestfs
qemu_xen
qemu_xen_4_10
qemu_xen_4_8
qubes-core-vchan-xen
samba4Full
sambaFull
vagrant
xen
xen-slim
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_10-slim
xenPackages.xen_4_10-vanilla
xenPackages.xen_4_5-slim
xenPackages.xen_4_5-vanilla
xenPackages.xen_4_8-slim
xenPackages.xen_4_8-vanilla
xen_4_10
xen_4_10-slim
xen_4_8
xen_4_8-slim

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bk4kdv0hgbfj9pd3jb1xm05ydw8z0zwm-glusterfs-7.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A glusterfs https://github.com/r-ryantm/nixpkgs/archive/d1d2c4dce09b27527e83f37006156c5a0cf6d0dd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bk4kdv0hgbfj9pd3jb1xm05ydw8z0zwm-glusterfs-7.1
ls -la /nix/store/bk4kdv0hgbfj9pd3jb1xm05ydw8z0zwm-glusterfs-7.1/bin

cc @7c6f434c for testing.

Funny that homepage doesn't list the release yet (there goes my hope to read the release notes·)


feat: add connectionBufferSizeMB field in order to specify support mb values

In the connectionBufferSize config on primary and metadata buckets, we got raw bytes value as connectionBufferSize: 20971520 it's really hard to read and understand the exact value.
To get mb related value from users like 5mb, 15mb, 1.5mb, 2.5mb etc. I have added a new field called connectionBufferSizeMB . Via this field, users can easily determine
metadata:
  config:
    bucket: cbes-checkpoint-ProductCenter
    connectionBufferSizeMB: 5mb

dcp:
  connectionTimeout: 10s
  connectionBufferSizeMB: 20mb

etc.
Currently, I try to support connectionBufferSize in not order to break compatibility. I signed this field as deprecated on README.

No required to keep open this PR, I have opened more expanded version of it: https://github.com/Trendyol/go-dcp/pull/71


Cypress/E2E: Fix intermittent failing tests at common commands

Summary

Fix intermittent failing tests at common commands
separate invite and groupmsg into its own spec files to easily run test in isolation, and promote/demote particular test

Ticket Link
none, failing in daily Cypress run
Test run - https://mm-cypress-report.s3.amazonaws.com/1034-common-commands-master/mochawesome.html

Changes look good to me but they are failing locally for me and it looks like the #postListContent is taking longer to load in at least 2 test files, invite_commands_spec and common_command_spec even though the timeout side considerably high. But it if passed for Joseph, I can approve it.

Yeah, let's observe it again next time. And I suspect it might also happen to other similar test.

Should we demote it from prod then?

I suggest no. I'll take care of it once I wrapped for a week. The one you're seeing can potentially happen to other test. Also, it might depend on local setup as well. Let's see how it run in CI.

fyi, this prod report includes the changes from here.


Application Filtering Feature Request

hello
is there any idea to add App filtering ( for example block telegram or adobe Flash player or any other things in opnsense)
i think deep packet inspection needs for this module

Yep ... I'm planning to integrate a sort of this via Suricata rules but it needs some time. Pipeline is full of projects.

also i think it can be done with nDPI package

This is in beta stage .. it's more or less complete but need some tweaks.
I can post you a patch to apply it if you like ...

thanks mimugmail

@fichtner was not that in the latest release?

It was.


DynamoDB - DeleteBackup - Add AccessDeniedException handling.

access denied typically relates to iam policy issues of the custodian execution role, ie there's no embedded resource policy on dynamodb, so i'm not sure we should be catching this, as it its a persistent error that needs correction.

I think in this case specifically, we can either act on all DynamoDB Backups or we can not.  I don't believe there is fine grained access to backups.  We can probably close this PR


gdx-controllers: Add windows XBox mapping, accept XBox One controllers

Adds XBox controller mappings on windows, and accepts an XBox One controller. All mappings were done with an XBox One controller, as I don't have a 360 controller. However I did confirm that the existing Linux mappings for the controller were correct with the XBox One controller.

This is only lwjgl3 tested?On 26 Apr 2018 01:21, WickedShell<EMAIL_ADDRESS>wrote:Adds XBox controller mappings on windows, and accepts an XBox One controller. All mappings were done with an XBox One controller, as I don't have a 360 controller. However I did confirm that the existing Linux mappings for the controller were correct with the XBox One controller.
You can view, comment on, or merge this pull request online at:
  https://github.com/libgdx/libgdx/pull/5194
Commit Summary
gdx-controllers: Add windows XBox mapping, accept XBox One controllers
File Changes
M
extensions/gdx-controllers/gdx-controllers/src/com/badlogic/gdx/controllers/mappings/Xbox.java
(34)

Patch Links:
https://github.com/libgdx/libgdx/pull/5194.patchhttps://github.com/libgdx/libgdx/pull/5194.diff
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

Correct. I don't have any other backends set up at the moment

It's the same mapping as in #5090 minus the LWJGL2 definitions.

@Zomby2D Sorry I hadn't seen yours! I'm fine with accepting yours as the solution. (Although the L/R trigger problem makes it very hard to usefully use the mapping on both of those :( ) As long as we have something that works (soon) I'd be happy! (Although using equalsIngoreCase() instead of making a new string object is probably worth it)

@Tom-Ski Any chance of this or #5090 being merged?

@Tom-Ski thanks!


Model-caching: Finish branch from jakob

See branch

See also https://github.com/mboecker/mlrmbo-webservice/pull/20


Rephrase Regexp to regular expression

RegExp is the name of the object in JavaScript. The word "regex" is more generic and a shorthand for "regular expression".

Alright, done.
I found the word custom to be superfluous.


VCF file reported to be missing although it is provided

Thank you for creating this pipeline. I've installed all the necessary components and I'm currently attempting a test run to demultiplex a single pool of 10X multiome data, which includes four multiplexed patients. Despite providing the VCF file with imputed SNPs, I encountered the following error message:
Dry run
Using profile config/ for setting default command line arguments.
Building DAG of jobs...
MissingInputException in rule vireo in file /omics/groups/OE0130/internal/Mislav/AML_multiome_Freiburg/CellDemux/CellDemux/dmx.smk, line 637:
Missing input files for rule vireo:
output: /omics/groups/OE0130/internal/Mislav/AML_multiome_Freiburg/CellDemux/resultsPool2/rna/vireo/donor_ids.tsv
wildcards: sample=Pool2
affected files:
/omics/groups/OE0130/internal/Mislav/AML_multiome_Freiburg/CellDemux/resultsPool2/inputfiles/refvcf.vcf

Hi @m571c ,
Sorry for this (very) late answer. Wondering whether you managed to solve this?
Any other rules are running / completed already? Files are softlinked correctly to an input directory?
Best,
Martijn


GitHub Actions prevalence-merge.yml fails periodically

The 'Merge prevalence updates' GitHub action occasionally misses its cue and fails to merge the actual prevalence update PR.  It seems to have happened in the past:

https://github.com/microCOVID/microCOVID/pull/1058
https://github.com/microCOVID/microCOVID/pull/1265

But has happened more recently, more frequently I think. I've fixed up two of them, but here's an example of one that was never merged:

https://github.com/microCOVID/microCOVID/pull/1660

I think this may potentially be related to adding a new mandatory check from https://about.codecov.io/
Background
We have a few GitHub actions and other checks which are involved in daily prevalence updates:

'Prevalence'

https://github.com/microCOVID/microCOVID/blob/main/.github/workflows/prevalence.yml - Runs at 14:00 UTC and runs "yarn prevalence"
https://github.com/microCOVID/microCOVID/blob/main/package.json#L50 - 'yarn prevalence' runs 'scripts/prevalence_helper.sh
https://github.com/microCOVID/microCOVID/blob/main/scripts/prevalence_helper.sh

runs update_prevalence.py
Creates feature branch
Opens GitHub PR

'CI'

https://github.com/microCOVID/microCOVID/blob/main/.github/workflows/ci.yml - runs on every branch
After running tests, runs the uploader for codecov.io

codecov.io

This is an external service that investigates code coverage output files and ensures any code changed on a PR has been tested.

Netlify

Creates a version of the site for the feature branch that you can use for testing.

'Merge prevalence updates'

https://github.com/microCOVID/microCOVID/blob/main/.github/workflows/prevalence-merge.yml - runs on various PR event types ("labeled, unlabeled, opened, edited, reopened, synchronize") for prevalence updates and hits the virtual merge button on it.

As an aside, I noticed that adding a new label to the stuck prevalence PRs causes prevalence-merge.yml to notice it and merge it.

GitHub (now?) has an auto-merge button.  Wonder if we could skip the 'Merge prevalence updates' thing entirely by teaching prevalence_helper.sh to press it...

It looks to me as if https://github.com/microCOVID/microCOVID/blob/01cf9613adc5cc4a13cc163fef7ebcdcfccc7d7c/scripts/prevalence_helper.sh#L118 would already automerge the PR, if the AUTOMERGE variable is set to 1. This would obsolete the separate automerge action.

@blanchardjeremy: I wonder why https://github.com/microCOVID/microCOVID/pull/1067 both added this code and also turned it off by default.
@deraffe: Barring an answer on that, seems worth trying.  Maybe whatever reason is overcome by events.

Another failure: https://github.com/microCOVID/microCOVID/pull/1717


Current pagination buttons not at a static position (at the bottom of the page ) on the patient list view

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #266
Type
Choose one: Bug fix
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Coverage increased (+2.3%) to 61.247% when pulling 3e9c98f1fb11a0b891cf368adfa3b5f88c0afda9 on issue-266 into 8dfac4bff339b0eef0c365378e2d0f351b81cef8 on main.


Add configuration option for TOC shortcode

This PR is aimed to fix Issue #153

I am unable to see the error thrown in vercel, is there a way of receiving this feedback?


Add option to switch orientation

:+1: You could also add a simple test for the new methods in the PHP class. :white_check_mark:

LGTM


Rewrite, TypeScript, some API additions

This is the everything PR, since developertown is the only one using this fork.
There is too much going on / needing to happen to incrementally upstream stuff back to exivity. :-\
This PR Contains:

Typescript conversion
Rewrite using Context API
Relationship Helpers
Remote-assigned ID Helpers

This will try its best to maintain backwards compatibility with the upstream, but probably will be published under a different name.
Note: This PR will be too big to effectively review :(

Merged. there is only one failing test on scriptoria's main branch and it's likely that the test is incorrect, but also the interactor doesn't have enough assertions to discern what is happening. it's a 4-5 invocation-long chain


Follow up - Remove 2nd Layer - L2 - Navigation part 2

After the L2 navigation is removed, these are items to address that were not a blocker to removing the L2 but we should consider for follow up.

Analyze  Get Started button click traffic to see if we can improve getting developers directly to where they really might want go. For example there are a lot of referrals to that link from the Framework install pages. Do they just want to start their downloads?  The hypothesis may require some testing over time.
Verify if there’s any relevant place to add the about link
Check where there’s high traffic to the download pages and move the link to an action button above the fold if too low. Example of one above the fold

Please accept my apology for forgetting I had this follow up issue on the dotnet/core repo.

About link was provided in an update to the Hub pages.  I forgot it was mentioned as a tracking item here as well.  That was fixed some time ago.
Download link was added as the very first top left item on the .NET hub.  It receives the top traffic, with the .NET Core Overview 2nd and the C# Intro (interactive) as 3rd.  Traffic seems to be routing from there fine.

The download link also represented above the fold in:

All What's new in .NET Core topics
The Install .NET Core topics for Linux, macOS and Windows
Intro to .NET Core topics.
.NET Core SDK overview
.NET Core CLI overview
Getting started tutorials such as:  Create a console app for VS, and for VS Code and Visual Studio for Mac.

Remaining item, which is being fixed right now:
There was no download link on .NET Core Overview so I am adding one to that.


Work out the A/V setup for streaming presentations in a How-To

We need to have a repeatable setup for streaming presentations at meetings and meetups. These usually involve a speaker with a presentation laptop, a host doing the recording and streaming with a controlling laptop, a smartphone recording video, a microphone for the speaker, and audio amplification for the audience. Objective: write a How-To.

The quality of the audio is more important than that of the video, especially for remote viewers.

The Video Production group can help with this.
We have a channel called livestreams. I have linked from there to this issue number.
use /dig a to see the channel procedures
(Video Production Group)(https://chat.divvydao.net/video-team/channels/live-streams)

Great! I added "Objective: write a How-To" to the description and title.

Setting
Room with audience of 80 people watching a presentation on screen and amplified audio.
Online Zoom-webinar with panellists and attendees
Direct live stream to Youtube
Hardware setup.
Apple MacBook Pro (Mac)
Iphone as panellist that is the camera
Samson Stage PXD1 (wireless mic that plugs in with receiver into Mac usb port)
Samson Expedition XP106 (karaoke box that receives in mp3 port an aux cable from Mac's headphone port)
Philips PicoPix (beamer that receives mini HDMI from Mac's HDMI port)
Apple MacBook Pro (Mac)

Samson Stage PXD1 (wireless mic that plugs in with receiver into Mac usb port)

Samson Expedition XP106 (karaoke box that receives in mp3 port an aux cable from Mac's headphone port)

Philips PicoPix (beamer that receives mini HDMI from Mac's HDMI port)

Mac audio settings:
Device for sound output is: Headphones
Device for sound input: Samson RXD wireless receiver

Device for sound output is: Headphones

Device for sound input: Samson RXD wireless receiver
Quicktime
In order to allow sound output, start QuickTime: File new Audio recording. Slide the volume bar to the right.

Zoom setup
Browse to Zoom

Tick on My Webinars and then start your webinar.

Tick on broadcast for letting people to join your webinar as panellists. That means that they can participate in your webinar. Attendees can only listen.
Now start your live stream to YouTube. Tick more and and tick Live on Youtube.
Choose your google account.
Type the title of your webinar
Tick Go Live!

Screen configuration of Zoom between Mac and Screen
Untick Mirror Displays

Choose a small screen to share, i.e. Chrome browser or presentation.
Drag it to the presentation screen.

Tick full screen green button
On youtube you can see what viewers will see of your webinar.

A note for people trying this: HJ had everything working and I was helping with testing the mic. Then, a few minutes before the Meetup started, it seemed like Zoom ran out of memory or something. Zoom started dropping aspects, like the microphone, behaving like it does when the Internet connection is too slow and it stops updating the video. After a quit and relaunch everything worked again. It might be wise to get everything setup and working and then quit and relaunch 10 minutes before an event starts.


improve computed isGrid to native function

left a comment but still +1

@stefanpenner updated, added readOnly

@stefanpenner totally off topic, but I always assumed that Ember.computed.* properties were readOnly. Other than causing an error if you try to set it, are there any other advantages to marking a property as readOnly?


Missing System Property error when switching workspaces

Launch Worthwhile product
Go to File -> Switch Workspace -> Other...
Try to open another existing workspace, the currently active workspace or a new workspace
"Missing System Property: Unable to relaunch the platform because the eclipse.vm property has not been set"

Wrong issue number in commit, amended to 0f0e53b and force-pushed.

I can reproduce it in the version launched from Eclipse, but not in the (exported) standalone version.
From what I’ve googled so far, Eclipse is looking for a [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/launcher_ini.html](configuration file) which it does not find in the Eclipse-launched version. I didn’t find a workaround either.
Since this seems to be a development-related issue that does not occur in production, I feel like I can safely close it.


feat(rpc): get_account

This PR adds the rpc endpoint get_account.
Makes use of the hashed_storage_root method from the StateRootProvider and passes an empty HashedStorage in order to only get the storage root of the current state for the provided account.

I couldn't find a place to add tests to this, would it be something we would want? Can also add in another PR


318 simple ship regions

closes #318
closes #113

Ok, this one is ready to go. I've uninstalled select2 from NPM, so we are completely self-hosting it. Another alternative would be to fork the repo and then we could reference the forked repo in NPM... but I think this is probably ok for now.


don't need all example datasets from libpysal for testing

Even though we only need the "Guerry" and "Rio Grande do Sul" example data, libpysal is pulling all datasets. This should be resolved with pysal/libpysal#486.

Can confirm this works with bleeding edge libpysal


Correcting the bug when looking up for summoners spell by id

I used to API for my League application and had to use the SummonersSpell by id's but it wasn't working.
So I checked your code and found a this tiny bug :)
Here is the correction !
Thanks a lot for this project it's helping me a lot !
Have a good one.

Thanks for the catch!


Application keep crashing in ios7

My application keep crashing in ios 7 on below line
static let rv = UIApplication.sharedApplication().keyWindow?.subviews.first as! UIView
when i have printed UIApplication.sharedApplication().keyWindow then it is showing nil.
Please help.

I just tested SwiftNotice on iOS 7 simulator with Xcode 6.4, it's OK.

I am working with swift and xcode 6.4 and it is crashing still
I have called  [window makeKeyAndVisible]  before not after

forget to say that I tested https://github.com/johnlui/SwiftNotice/releases/tag/v3.1


LSF system, stdout/stderr always goes to my email

I am on the LSF system. I have a job file like this:
job_begin
name jobA
time 1h
memory 500m
queue normal
project CompBio
sge_options -A swang -e example2.jobA.e.txt -o example2.jobA.o.txt
cmd echo "hello from job jobA"
job_end
job_begin
name jobB
time 30m
memory 1g
queue normal
project CompBio
cmd echo "hello from job jobB";
job_end
order jobB after jobA
log_dir /home/iiiit/app/SJM/doc/log
regardless of how i do, the "-e example2.jobA.e.txt -o example2.jobA.o.txt" or "log_dir /home/iiiit/app/SJM/doc/log" is not effective. all notifications goes to my email (for jobA and jobB)
Can you help?
Thanks,

Hi,
I haven't used SJM on LSF, but based on my knowledge of how things work on SGE, I should say that you shouldn't be getting any emails unless you specified the --mail option when running SJM on the command-line, or unless you specify the -M option in sge_options in your SJM file.
Also, I don't believe it will work as you expect if you are setting both log_dir and the -e and -o sge_options. When setting log_dir, all output goes in that directory, including the jobs stdout and stderr files, and those log files will have the default names of job_name.ejob_id and job_name.ojob_id.
Also note that if you don't specify an absolute directory path when using -e and -o (which I suggest doing), then (if log_dir isn't specified) the stdout and stderr job files will be written in your home directory.

Thanks much.
I think getting emails is something enforced by our LSF system under the condition that -e -o is not specified. Looks like in my case these parameters were not passed to the job submit system -- i don't know i am just guessing.
Regard the log_dir, it will always be empty independent of how i run sjm or how my job looks like.
I even tried the sched_options for -e and -o, which did not work for me as well.
I am getting our HPCF support involved and hopefully work out something.
Shuoguo

Hey Shuoguo,
I may know what the issue is. Please try sched_options instead of sge_options. sched_options is what's given in the MANUAL document, and even though sge_options does work for SGE, it likely shouldn't be used with LSF. I'm thinking that sched_options is universal with either LSF or SGE.
Please try that and let me know if it works or not.

Thanks for the suggestion.
I actually tried sched_options before I started the thread. I will continue to figure out a solution though.

hi iiiir
I met the same problem, did you get a solution to solve the problem and could you please share you solution?

Hi HuanYuu,
It was fixed by adding a projectName to src/lsf.cc at line 95:
if (!job.project().empty()) {
    req.options |= SUB_PROJECT_NAME;
string projectName("sjmProject");
    req.projectName = const_cast<char *>(job.project().c_str());
}
replaced this line:
req.resReq = const_cast<char *>(resReq.c_str());
with:
char* resString = new char[255];
std::fill(resString, resString + 255, 0);
resReq.copy(resString, resReq.size());
req.resReq = resString;
Hope this helps.
Shuoguo

we can redirect in cmd part, like this:
...
cmd_begin
    COMMAND  1> /path/to/log_dir/xxx.o.log 2> /path/to/log_dir/xxx.e.log
cmd_end
...

PS: need mkdir /path/to/log_dir firstly


[DISCUSSION] [PLUGIN API] Notes from the Rust world

Here are some notes I made while working on the Falco Plugin Rust SDK. Please note that they're not blockers for the Rust SDK itself (everything here has a workaround, better or worse). I hope that they can drive future API evolution and make it safer and easier to use. Please consider all suggestions with an implied "if it doesn't make life for other SDKs or the plugin framework too hard".
Strings without an explicit owner
There are a few strings that I found that do not have a specific struct as their owner, preventing usage of instance fields for the underlying storage. Basically, every API method that returns a pointer but does not take a pointer as an argument is potentially problematic.
The following lists the uglier cases I've found so far.
plugin_get_fields and plugin_get_init_schema
The issue here is that it's tempting to generate the resulting string automatically (writing JSON by hand is not exactly my definition of fun) and we do need to store the result somewhere.
It may be possible to generate these at compile time but it would require procedural macros which are fairly magical and opaque. My goal is to avoid proc macros so that the whole API can be discovered and autocompleted by the IDE and the compiler.
Proposed solution
Split allocation and initialization of the plugin into two phases and introduce a ss_plugin_t* parameter to all methods that do not take one now (it's less problematic for things like plugin_get_name since it's easier to hardcode their value at compile time, but we should do it for consistency anyway). So instead of:

plugin_get_name
plugin_get_foo
etc.
if anything is wrong, just return
plugin_init
use the plugin
plugin_destroy

the workflow would be:

plugin_alloc
plugin_get_foo
if anything is wrong, plugin_destroy before returning
plugin_init
use the plugin
plugin_destroy

plugin_get_last_error
The situation is somewhat different here as we do have an instance pointer, but it can be potentially accessed from multiple threads (given there are API methods that both take a ss_plugin_t* and allow multithreaded access).
Assuming that plugin_get_last_error is used for all error reporting, this implies that multiple threads can share the same ss_plugin_t* and its error message buffer, which requires a Mutex to prevent multiple threads from writing to the buffer concurrently.
More importantly, since we cannot return a reference with a lifetime attached, we cannot unlock the mutex whenever the caller is done with the error string. This means that the returned pointer must remain valid even after the mutex is unlocked. As a consequence, we may never reallocate the buffer, so we're forced to use a fixed-length array.
Now, to make sure a catastrophe won't happen with multiple threads reading and writing the error buffer, we need to zero-fill it before every write, so that it's always NUL-terminated, even while we're writing to it (note that non-Rust code in a different thread can easily read the error buffer via a pointer obtained whenever, ignoring the mutex completely).
Proposed solution
I feel it would be best to drop the whole concept of a plugin instance as a separate entity. If you want multiple plugin instances, just allocate multiple ss_plugin_t* instances. Then it's clear that every thread has its own error message buffer and can use it freely without locking.
ss_plugin_t* not safely accessible from ss_instance_t* methods
This again ties into thread safety and the Rust model of memory safety. A non-const pointer naturally maps to a &mut reference, but that is instant UB in multi-threaded Rust: multiple mutable references cannot even exist (unused) without causing UB and actually accessing an object through multiple mutable references from different threads is a recipe
for disaster (including the worst case where everything works fine--for now).
Passing shared references to the plugin to instance methods doesn't help all that much: all other methods would need to take shared references as well, with all the overhead that it brings (every mutable field hidden behind a mutex, resulting in abysmal developer experience and performance penalty). So in the Rust SDK, I chose not to expose the ss_plugin_t* parameter to ss_instance_t* methods--the instance can pull in all the data in wants from the main plugin e.g. by Arc<T>
(for read-only data) or Arc<Mutex<T>> (for mutable data).
Proposed solution
Again, kill the ss_instance_t* concept and just use multiple ss_plugin_t* instances.
Unclear thread-related lifetime rules
Is there a guarantee that whichever thread allocates a plugin or instance is responsible for freeing it later, or can allocations
and frees happen in different threads (for the same object)?
Can a particular object be accessed from multiple threads? Sequentially? Concurrently?
This has consequences for the trait bounds for the plugin implementations that would e.g. disallow thread-local storage or other non-thread-safe constructs.
Proposed solution
Clarify the rules. It feels okay to guarantee that a particular object will only ever be accessed by the thread that created it,
except for the unfortunate "instance accessing plugin" case (which the Rust SDK disallows).
If we dropped ss_instance_t* and accepted this rule, thread safety would become much simpler IMHO in the API: it would become entirely single-threaded for any particular object and any threading issues become internal to the plugin itself.
Unclear lifetime rules for strings (pointers) passed to plugins
For any pointer passed from the plugin API to the plugin, it would be nice to know how long it remains valid; basically: can I store the pointer or do I need to copy the pointee. The two obvious answers (different ones for different pointers) would be:

it's pointing to static storage and will remain valid for the lifetime of the plugin
it's pointing to an ephemeral variable (maybe stack-allocated) and will only remain valid during the call

Proposed solution
Document the lifetime rules for all pointers.
Inconsistent support for data types
There are a few different uses for the various PT_*-described types:

event fields (the original use case)
table keys
table values
values for extracted fields

The documentation suggests that table keys and values support different sets of types (involving the ss_plugin_field_t enum), but the method signatures themselves say that keys and values can use the same data types (basically: whatever is convertible to ss_plugin_state_data).
Values for extracted fields are set in ss_plugin_extract_field.res, which is a union nearly identical to ss_plugin_state_data*.
I realized that to support a data type we need two sets of conversion functions:

to/from a sequence of bytes (in events)
to/from a C data type (in tables and field extraction)

but the second conversion is ever so slightly different between table access and field extraction.
Proposed solution
Make ss_plugin_extract_field.res a pointer to ss_plugin_state_data.
Maybe we also want to make ss_plugin_state_data a tagged union (i.e. a struct that contains an enum describing which union variant is live and the union itself).
Note that we need something tricky for the v4/v6 combined fields as currently there's no way to extract a list of addresses due to their variable length. We can give up and use a pointer to a separately allocated struct but that introduces unnecessary allocations. Alternatively, we can use a fixed-size struct that would fit both address types, like:
struct v4_or_v6_addr
{
    uint32_t family; // AF_INET or AF_INET6
    union
    {
        uint32_t ipv4;
        uint8_t ipv6[16];
    };
}

Unclear endianness rules
I realize this is not an issue with the plugin API per se, but the endianness of values is not specified anywhere. x86-64 and aarch64 are both little-endian AFAIK but not all architectures are.
This creates its own version of hell when trying to deal with cross-endianness captures, so we might at least try to avoid issues
with plugins and specify e.g. that all numeric fields in events are little-endian.
Note: I honestly have no idea how IP addresses are stored in events: native byte order? network byte order?
Proposed solution
Sit down and think very hard about endianness across the whole stack.
Alternatives
Leave the API as is.

cc @jasondellaluce @Andreagit97

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

uhh, I missed that sorry!
These are all valid points, i faced some of them while trying to implement a simple Rust SDK, not sure when/how we want to tackle them, but for sure this is something we need to keep in consideration in future plugin API reworks

/remove-lifecycle stale

I would also reconsider the multithread approach built by default inside the plugin API considering pros and cons:

code complexity
performance
real-world usages

@Andreagit97 I was confused about the source plugin <-> instance relationship (it's always 1:1 it seems), so at a glance it feels like a threading rule being tl;dr "every object is always accessed from the thread that created it" would pretty much describe the current state.
Vaguely related, we could use some clarification around tables:

can we even think of accessing tables from async plugins (or, in general, other threads)? it would be massively useful if so but it's a whole new can of worms
we probably need a rule saying ss_table_entry pointers can never be stored across an API function call (they're effectively iterators that get invalidated whenever you look at the underlying table hard enough)

I have Ideas :tm: about extending the table support with a few methods that would let us factor just about anything inside sinsp into plugins but that's way ut of scope here ;)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.


/var/run/nologin prevents SSH login

Hello @geerlingguy,
Thanks for this container !
I notice that when running docker-centos7-ansible like this:
docker run --detach --privileged  geerlingguy/docker-centos7-ansible:latest

/var/run/nologin is present and prevents SSH login. Is it voluntary ?

https://github.com/CentOS/sig-cloud-instance-images/issues/60

To my knowledge /var/run/nologin is not part of the official centos:7 Docker image, nor of geerlingguy/docker-centos7-ansible.
I played a bit with Dockerfiles and it seems to have to do with the official instructions to enable systemd, found here: https://hub.docker.com/_/centos/

This Dockerfile deletes a number of unit files which might cause issues.

Something with that change seems to create (and not clean up?) /var/run/nologin preventing SSH login for non-root users.

Hello @IceBear2k,
I discover this unexpected behavior when using test-kitchen with this container. If I use centos:7 in place, I didn't got this behavior.
Easy reproductible with https://github.com/nqb/hello-doc-ng/blob/master/kitchen.yml

Yes, @nqb, that is my use case as well. I've made the same observation. (https://github.com/KrautIT/ansible-role-base/blob/master/.kitchen.yml)
You can also see that it's working properly by creating a Docker image from https://github.com/geerlingguy/docker-centos7-ansible/blob/master/Dockerfile but remove the whole systemd block between lines 7 and 16. SSH will work fine.

I don't plan on supporting SSH on my docker images (though you're free to fork/build on top of to do it)... haven't had any reason to use it.


Introduce formatting guidelines and documentation; add a new editorconfig file for use with IDEs

Description
I often see comments on pull requests from people asking to not change the whitespace in files etc. Basically, there is no standardized practice contributors are expected to follow and so some files have space while others have tabs.
This change introduces guidelines for styling and applies these guidelines to all files in the code base.  It also adds a security.editorconfig file which can be used with IntelliJ or VS Code to import the standardized settings to the IDE.
The rules being added are:
## Common Practice

Please visit [security.editorconfig](./security.editorconfig) to download the complete formatting settings.
Use with IntelliJ is natively supported, while Visual Studio Code supports use through the EditorConfig Extension.

### Whitespace

* Indentations should use 1 tab (of size 4 spaces) in Java files
* Indentations should be 2 spaces in YAML files
* There should be a preceding space before all 'if', 'for', 'while', 'switch', 'try', 'catch', and 'synchronized'
  parentheses
* There should be a preceding space before all non-unary operators

### Imports

* Imports should use single class names (no wildcards)
* JavaDocs should use fully qualified class names
* Java.* imports should be placed at the top, followed by Javax.*, then all other imports, and finally static imports.

If any other specifications should be met, please leave a comment and I will update the requirements.
Check List

[ ] ~New functionality includes testing~
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @cwperks, yeah I am trying to see what it is doing now. I need to look at the code I think since it complains even when you enforce java imports first so not sure what the specific requirements are. I will make that part of this change as well.

@scrawfor99 I removed the output of running spotlessApply these changes show how to setup the formatting.gradle: https://github.com/opensearch-project/security/compare/main...cwperks:configure-spotless-plain?expand=1

@scrawfor99 certainly :+1: for Spotless (no formatting wars :D), but I think:

you should exclude build files (build.gradle)
you should exclude .github folder and *.MD (markdown) files

Hi @peternied,
Thank you for following up.
I will go ahead and make a more incremental rollout process like you suggested.
I will also swap the line breaks in the markdowns. I will also followup on the comments you left regarding the license headers. Because of how the formatting works, it can be hard to tell what is being changes as you mentioned. I don't believe the changes from the other repos are meant to swap the headers so I will double check to make sure that everything is correct. I will make a tracking issue and link the related PRs so that it is easier to tell what is being changed. I will then refactor by package instead of having the IDE refactor everything at once.


Fails to evaluate wait-k model on SimulEval if sequence is shorter than k

I've got an error while evaluating the wait-k model following the instruction of README.md.
2021-04-03 10:36:28 | INFO     | simuleval.scorer | Evaluating on text
2021-04-03 10:36:28 | INFO     | simuleval.scorer | Source: /userdir/iwslt17.test0.en
2021-04-03 10:36:28 | INFO     | simuleval.scorer | Target: /userdir/iwslt17.test0.ja
2021-04-03 10:36:28 | INFO     | simuleval.scorer | Number of sentences: 1549
2021-04-03 10:36:28 | INFO     | simuleval.server | Evaluation Server Started (process id 132622). Listening to port 12321
2021-04-03 10:36:31 | WARNING  | simuleval.scorer | Resetting scorer
2021-04-03 10:36:31 | INFO     | simuleval.cli    | Output dir: /userdir/iwslt17.test0
2021-04-03 10:36:31 | INFO     | simuleval.cli    | Start data writer (process id 132639)
2021-04-03 10:36:31 | INFO     | simuleval.cli    | Evaluating SimulTransTextAgentJA (process id 132556) on instances from 0 to 1548
2021-04-03 10:36:31 | INFO     | fairseq.tasks.translation | [en] dictionary: 16004 types
2021-04-03 10:36:31 | INFO     | fairseq.tasks.translation | [ja] dictionary: 16004 types
Traceback (most recent call last):
  File "/userdir/.venv/bin/simuleval", line 11, in <module>
    load_entry_point('simuleval', 'console_scripts', 'simuleval')()
  File "/userdir/SimulEval/simuleval/cli.py", line 165, in main
    _main(args.client_only)
  File "/userdir/SimulEval/simuleval/cli.py", line 192, in _main
    evaluate(args, client, server_process)
  File "/userdir/SimulEval/simuleval/cli.py", line 145, in evaluate
    decode(args, client, result_queue, indices)
  File "/userdir/SimulEval/simuleval/cli.py", line 108, in decode
    action = agent.policy(states)
  File "/userdir/fairseq-v0.10.2/examples/simultaneous_translation/eval/agents/simul_t2t_enja.py", line 196, in policy
    x, outputs = self.model.decoder.forward(
  File "/userdir/fairseq-v0.10.2/fairseq/models/transformer.py", line 817, in forward
    x, extra = self.extract_features(
  File "/userdir/fairseq-v0.10.2/examples/simultaneous_translation/models/transformer_monotonic_attention.py", line 219, in extract_features
    x, attn, _ = layer(
  File "/userdir/.venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/userdir/fairseq-v0.10.2/examples/simultaneous_translation/modules/monotonic_transformer_layer.py", line 160, in forward
    x, attn = self.encoder_attn(
  File "/userdir/.venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/userdir/fairseq-v0.10.2/examples/simultaneous_translation/modules/monotonic_multihead_attention.py", line 667, in forward
    alpha = self.expected_alignment_infer(
  File "/userdir/fairseq-v0.10.2/examples/simultaneous_translation/modules/monotonic_multihead_attention.py", line 528, in expected_alignment_infer
    assert tgt_len == 1
AssertionError

This problem occurs when the sequence is shorter than k.
Environment

fairseq Version: 0.10.2 (commit 14807a361202ba34dbbd3a533899db57a0ebda19)
SimulEval Version: latest (commit<PHONE_NUMBER>f989ea3b79fdf5a21b96089a002f36)

I will write a solution to this.
You input this code
        if p_choose.numel() != bsz*self.num_heads*tgt_len*src_len:             p_choose = p_choose[:, 1]
between monotonic_multihead_attention.py#L693 and monotonic_multihead_attention.py#L694.

Finally, you add wait-k algorithm into policy on your agent.
I will pull-request for this.


Conformance results for v1.20/kubermatic

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] If this is a new entry, have you submitted a signed participation form?
[x] Did you include the product/project logo in SVG, EPS or AI format?
[x] Does your logo clearly state the name of the product/project and follow the other logo guidelines?
[x] If your product/project is open source, did you include the repo_url?
[x] Did you copy and paste the installation and configuration instructions into the README.md file in addition to linking to them?

Found v1.20 in logs

This conformance request failed to include all of the required tests for v1.20

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

Found v1.20 in logs

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

This conformance request failed to include all of the required tests for v1.20

Found v1.20 in logs

This conformance request failed to include all of the required tests for v1.20

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

Found v1.20 in logs

This conformance request failed to include all of the required tests for v1.20

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

Automatically verified as having all required tests present and passed

Automatically verified as having all required tests present and passed

Found v1.20 in logs

Found v1.20 in logs

Automatically verified as having all required tests present and passed

Automatically verified as having all required tests present and passed

11 of 13 requirements have passed. Please review the following:

[FAIL] it appears that URL(s) in the PRODUCT.yaml don't resolve to the correct data type

URL field 'product_logo_url' in PRODUCT.yaml resolving content type 'text/html; charset=UTF-8' must be (image/svg, or application/postscript)

[FAIL] the Kubenetes release version in this pull request does not qualify for conformance submission anymore (https://github.com/cncf/k8s-conformance/blob/master/terms-conditions/Certified_Kubernetes_Terms.md#qualifying-offerings-and-self-testing)

unable to use version 'v1.20' because it is older than the last currently supported release (v1.21)

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.

11 of 13 requirements have passed. Please review the following:

[FAIL] it appears that URL(s) in the PRODUCT.yaml don't resolve to the correct data type

URL field 'product_logo_url' in PRODUCT.yaml resolving content type 'text/html' must be (image/svg, or application/postscript)

[FAIL] the Kubenetes release version in this pull request does not qualify for conformance submission anymore (https://github.com/cncf/k8s-conformance/blob/master/terms-conditions/Certified_Kubernetes_Terms.md#qualifying-offerings-and-self-testing)

unable to use version 'v1.20' because it is older than the last currently supported release (v1.21)

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.

11 of 13 requirements have passed. Please review the following:

[FAIL] it appears that URL(s) in the PRODUCT.yaml don't resolve to the correct data type

URL field 'product_logo_url' in PRODUCT.yaml resolving content type 'text/html; charset=UTF-8' must be (image/svg, or application/postscript)

[FAIL] the Kubenetes release version in this pull request does not qualify for conformance submission anymore (https://github.com/cncf/k8s-conformance/blob/master/terms-conditions/Certified_Kubernetes_Terms.md#qualifying-offerings-and-self-testing)

unable to use version 'v1.20' because it is older than the last currently supported release (v1.21)

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.

12 of 14 requirements have passed. Please review the following:

[FAIL] it appears that URL(s) in the PRODUCT.yaml don't resolve to the correct data type

URL field 'product_logo_url' in PRODUCT.yaml resolving content type 'text/html; charset=UTF-8' must be (image/svg, or application/postscript)

[FAIL] the Kubenetes release version in this pull request does not qualify for conformance submission anymore (https://github.com/cncf/k8s-conformance/blob/master/terms-conditions/Certified_Kubernetes_Terms.md#qualifying-offerings-and-self-testing)

unable to use version 'v1.20' because it is older than the last currently supported release (v1.21)

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.

12 of 14 requirements have passed. Please review the following:

[FAIL] it appears that URL(s) in the PRODUCT.yaml don't resolve to the correct data type

URL field 'product_logo_url' in PRODUCT.yaml resolving content type 'text/html; charset=UTF-8' must be (image/svg, or application/postscript)

[FAIL] the Kubenetes release version in this pull request does not qualify for conformance submission anymore (https://github.com/cncf/k8s-conformance/blob/master/terms-conditions/Certified_Kubernetes_Terms.md#qualifying-offerings-and-self-testing)

unable to use version 'v1.20' because it is older than the last currently supported release (v1.21)

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.


running git-it server should open a browser window

Running git-it server should automatically open a new browser window/tab and show you the page, so you don't have to manually enter the localhost URL. Some people have never done this before, and everything is so much easier with a browser that starts automatically.
At a later date we could even make the whole thing a "Single page application" - that way it wouldn't even matter if the server got killed (we could kill it ourselves even) - the browser would still have the page (whole site) in memory!

I actually started out by having it open a browser window, but this doesn't work the same across platforms so I decided to opt out of it entirely figuring it wouldn't be that hard to copy the link.
Most of the time now I just recommend the web version of the guide since they have to be online anyways to use Git-it. The one that ships with Git-it can then just be there if they need it offline sometime.
Not clear what you're thinking re: single page app. I've thought about how it would be cool to have the app and website respond to each other or be in the same thing, but it would be pretty complicated since we need to access Git and such.

Good point that users need to be online anyway, so they may as well use the hosted version of the guide.
So could we do as suggested in https://github.com/jlord/git-it/issues/82 - point them First at the hosted version, and second at the local copy?
ie.
first recommend they go to
http://jlord.us/git-it/
And the fallback to:
/usr/local/lib/node_modules/git-it/guide/index.html
Instead of first recommending
To launch the guide, run: git-it server`
And falling back to:
/usr/local/lib/node_modules/git-it/guide/index.html
as it currently does:

Lastly, if we do this, can we remove the server from the repo entirely? To simplify it and make it easier to understand and work with?
Thanks!

Oh, and regarding the single page app - I just meant that we could have all 9 sets of instructions in one server request, and use javascript to show different 'pages'.
Would mean you could start the server, boot chrome and show the page, and immediately kill the server again - all 9 pages would be loaded into Chrome by then.
But would prefer to remove the server entirely if at all possible...!

Maybe an option could be opener https://www.npmjs.com/package/opener if you want to get into this discussion again

I don't know how I missed the rest of the Jan. comments here—sorry!
At some point since then I've updated what it says at the bottom of each challenge to first suggest the web view and then to print out the location of the static files in the user's system. They can paste that in their browser if they are offline. This resolves needing to worry about a server.
Also! I'm in the process of porting Git-it over to Electron, which will make it a desktop app so basically the guide will become an app and this will definitely no longer be an issue :sparkles:
If you update your version of Git-it you should should see the latest footer about the Guide. I think we can close this here.


How to connect Cardano-wallet to a remote Cardano node instead of spawning a local node ??

I am using this script https://github.com/TheDevKnight/cardano-sl-wallet/blob/master/connect-to-mainnet to create a wallet.
The thing is because of some security issues I do not want to start the node in the same machine where I keep the wallet.
I still want to use the wallet apis (create account, publish transactions) but I don't want to keep it in the same machine.

I moved this to a separate issue tracker. There's currently no way to connect the wallet server itself to a remote node. As of today, the underlying node and the wallet server have be on the same host machine (though the node itself can connect to a remote peer).


Fix MongoDB Scaler.

Signed-off-by: Shubham Kuchhal<EMAIL_ADDRESS>Refactoring the MongoDB scaler code(mongo_scaler.go)
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated

Fixes #1776

@tomkerkhove @zroubalik  @ahmelsayed
Could you Please take a look!


Added method getDate() getTitle() getAuthor() in models/Article class

previous method's (date.setText(news.getDate(); title.setText(news.getText(); author.setText(author.getText())))) in IngegneriaAdapter get some errors.

I think you just need to install Lombok plugin
https://plugins.jetbrains.com/plugin/6317
I think this PR is not necessary.

It's ok so i'll download and install the suggested plugin.


Add support for nesting a Fn::Not

I ran into a case where I needed to do something like: Fn::And(Fn::Not(Fn::Equal), Fn:Equal). This wasn't currently supported. I'm guessing we just missed it with https://github.com/MonsantoCo/cloudformation-template-generator/issues/60 and https://github.com/MonsantoCo/cloudformation-template-generator/pull/66 . I don't think this should have any affect on legacy code.

Coverage remained the same at 52.88% when pulling a80e5b4884637bb74591bedf4cd4d51f25962e37 on nestable-not into b2b0998ebc3baf6ef53f52add9da7b07484e29f1 on master.

Looks good to me.  Merging.


Current version with latest libraries fails to compile

Using a WeMos D1 mini getting the following compile errors.
Only change made was to comment out USETFT as I don't have a screen.
// #define USETFT
Looks like ESPAsyncTCP was updated yesterday to "Fix compilation errors	a day ago"
Maybe this has broken it, maybe someone can attach a working version of the library?
Any other ideas?
C:\Users\Uksa007\Documents\Arduino\libraries\ESPAsyncTCP-master\src\ESPAsyncTCP.cpp: In constructor 'AsyncClient::AsyncClient(tcp_pcb*)':
C:\Users\Uksa007\Documents\Arduino\libraries\ESPAsyncTCP-master\src\ESPAsyncTCP.cpp:77:28: error: invalid conversion from 'long int ()(void, tcp_pcb*, pbuf*, long int)' to 'tcp_recv_fn {aka signed char ()(void, tcp_pcb*, pbuf*, signed char)}' [-fpermissive]
 tcp_recv(_pcb, &_s_recv);

                        ^

In file included from C:\Users\Uksa007\Documents\Arduino\libraries\ESPAsyncTCP-master\src\ESPAsyncTCP.cpp:27:0:
C:\Users\Uksa007\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0/tools/sdk/lwip/include/lwip/tcp.h:318:18: error:   initializing argument 2 of 'void tcp_recv(tcp_pcb*, tcp_recv_fn)' [-fpermissive]
void             tcp_recv    (struct tcp_pcb *pcb, tcp_recv_fn recv) ICACHE_FLASH_ATTR;
              ^

C:\Users\Uksa007\Documents\Arduino\libraries\ESPAsyncTCP-master\src\ESPAsyncTCP.cpp:78:28: error: invalid conversion from 'long int ()(void, tcp_pcb*, uint16_t) {aka long int ()(void, tcp_pcb*, short unsigned int)}' to 'tcp_sent_fn {aka signed char ()(void, tcp_pcb*, short unsigned int)}' [-fpermissive]
 tcp_sent(_pcb, &_s_sent);

                        ^

many more errors removed
exit status 1
Error compiling for board WeMos D1 R2 & mini.

To answer my own question, this issuse was the library,
I have changed the library.json back to commit 9b0cc37 but still had error found I need to implement c2d4c16 to resolve.
Why are they committing PR for 2.4_RC when they don't work with the current production release is beyone me !

I am facing this issue with NodeMCU and PlatformIO. I am using esp8266_stage.
.piolibdeps\ESPAsyncTCP_ID305\src\ESPAsyncTCP.cpp:839:30: error: invalid conversion from 'int8_t ()(void, tcp_pcb*, int8_t) {
aka signed char ()(void, tcp_pcb*, signed char)}' to 'tcp_accept_fn {aka long int ()(void, tcp_pcb*, long int)}' [-fpermiss
ive]
tcp_accept(pcb, &s_accept);
^
In file included from .piolibdeps\ESPAsyncTCP_ID305\src\ESPAsyncTCP.cpp:27:0:
C:\Users\verizon.platformio\packages\framework-arduinoespressif8266@src-31d658a59f41540201fc3726a1394910\tools\sdk\lwip\include/lwip/tcp.h:317:18: error: initializing argument 2 of 'void tcp_accept(tcp_pcb*, tcp_accept_fn)' [-fpermissive]
void tcp_accept (struct tcp_pcb *pcb, tcp_accept_fn accept) ICACHE_FLASH_ATTR;
^
*** [.pioenvs\nossl\lib\ESPAsyncTCP_ID305\ESPAsyncTCP.o] Error 1

Did you check  https://github.com/me-no-dev/ESPAsyncTCP/issues/60 ?

I saw it but I don't understand what to do to resolve the issue? I am using platformio ide.

I used this to correct it.


Expanding on hover animated Footer

Description
Add a responsive footer in which social media sections expand on hover, reference image given below
Screenshots

Additional information
No response

Can I work on this issue (SWOC-P)

If this issue is still open...can I work on this? @nandini7637

@Im-Abhi updates?

It's almost done soon enough will be creating the PR for same.


Updated SortBy to not do switch each iteration

Seems good, I've checked it, merging. Thanks for the contribution 👍


[1.12] Metadata for catalyst

I can't seem to find a way to specify the metadata for a catalyst item...
I've tried a few:
"catalyst": "appliedenergistics2:material:23"
"catalyst": { "id": "appliedenergistics2:material", "meta": 23 }

Oh, but digging in the code I found that there's a key called "catalyst-meta" 👍

Jupp, sorry, I should document this better.


Allow switchdev+externallyManged configs in webhook

Current implementation supports this combination.
NIC should be already in switchdev mode and have enough VFs to pass checks in the operator.
cc @e0ne @zeeke @SchSeba

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 38.434%

Files with Coverage Reduction
New Missed Lines
%

controllers/drain_controller.go
1
70.36%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
4815

Relevant Lines:
12528

💛  - Coveralls

can you please add one or two unit tests to cover a validation case switch dev but no vf, the other way around (both failed ) and one that pass the validation

thanks @SchSeba,
I pushed some tests to validate this behavior

@SchSeba I rebased the PR and added some tests. PTAL
Thanks


regression-test add log for malforamt response of stream load

Proposed changes
Issue Number: close #xxx
Problem summary
When some of stream load failed, the response msg may not be in json format, causing:
java.lang.IllegalArgumentException: Text must not be null or empty
  at groovy.json.JsonSlurper.parseText(JsonSlurper.java:202)
  at groovy.json.JsonSlurper$parseText.call(Unknown Source)
  at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
  at groovy.json.JsonSlurper$parseText.call(Unknown Source)
  at org.apache.doris.regression.action.StreamLoadAction.waitForPublishOrFailure(StreamLoadAction.groovy:338)
  at org.apache.doris.regression.action.StreamLoadAction.checkResult(StreamLoadAction.groovy:290)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Which is not good for debug.
This PR print the response msg when encounter error
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


"Bordei Verde" is listed in the drop-down menu

Description:
"Bordei Verde" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Bordei Verde" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bordei Verde, Brăila (Bordei Verde)".


Provide ability to define state variables as secret

At present, state variables are resolved at runtime and written to the console, e.g.
scripts:
   testSecret:
      - sh: echo "${{SOME_SECRET}}"
...
states:
   SOME_SECRET: mySecretPassword!!

Would output the following;
12:19:48.046 testSecret@server:echo "mySecretPassword!!"
mySecretPassword!!

Users should be able to denote that a state variable is a secret, and should not be written to the console
e.g.
scripts:
   testSecret:
      - sh: echo "${{SOME_SECRET}}"
...
states:
   *SOME_SECRET: mySecretPassword!!

Would output;
12:19:48.046 testSecret@server:echo "****"
****

Secrets could be passed into qDup via the command line, e.g.
$ java -jar qDup.jar -B /tmp/run /path/to/qdup.yaml -S SOME_SECRET=p4ssw0rd!

I think this is a good idea. Lets think about the details. State values can come from several locations:

yaml states:
command line arguments -S state=value
set-state:
regex: (?<newState>.+)
js: (input,state)=>{...}

Do we think we need to support secrets in regex, set-state and js?
They support scope prefixes (RUN.name or HOST.name). We would probably want to use *RUN.name if we wanted secrets in command patterns.
If we focus on only yaml and command line then *name would be sufficient because they do not support scope prefixes. If we want to be able to load secrets from files we would need to support regex but would not be able to suppress the string in logs before it is identified as a secret.
Filtering output:
I think the easiest solution would be to add all secrets to a list and use String.replaceAll before any log message is sent to file. We would also need to check all the JsonServer endpoints and run.json.
This could potentially "leak" the secrets if a command outputs a random substring that happens to match a secret. Is that a problem?
Preventing the ******** from appearing when the substring is random would require tracking when a secret variable name is referenced when populating a pattern (and patterns can use recursive variable reference) then using String.relaceAll when a secret is referenced. We could probably make that work by adding a boolean usedSecret() to the custom Mapcreated for populating the pattern but then how do we prevent the next command from leaking the secret if it acts on the real output of the command and not the sanitized output?

I pushed an implementation to master that uses _ as the secret prefix because * is already a yaml prefix. It works for set-state regex and the states: yaml section. SecretFilterTest will need another test to make sure it works for js: (input,state)=>{...} and I'm not sure how to create a test for the jar's -S arguments


Apply workaround to Chroma query

This fix helps with the issue mentioned here:
https://github.com/mariochavez/chroma/issues/29
message=Client error response code=400 body={"error":"InvalidArgumentError","message":"Expected where to have exactly one operator, got {}"} (InvalidArgumentError (Chroma::APIError)

@justi This is great, thank you!

There is a new release of Chroma gem that updates the API change for this.


Brugada Criteria SVT vs VT: copyedits

Revised references for expert peer review
I'm torn whether I like EPRs in the Cards.
Fixed ALiEM blog post link

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   50.32%   50.32%
=======================================
  Files          14       14
  Lines         155      155
  Branches       43       43
=======================================
  Hits           78       78
  Misses         77       77

Continue to review full report at Codecov.

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


ENH Let unit tests manipulate the DB before loading fixtures

Description

Fixtures in unit tests can be set up using an explicit table name - but there's no way (that I can see) to actually create the table in the time between the test DB being created and fixtures being loaded.
This PR adds a way for tests to do that.
See https://github.com/silverstripe/silverstripe-linkfield/pull/253 for an example of how this works.
Issues

https://github.com/silverstripe/silverstripe-linkfield/issues/229

Pull request checklist

[x] The target branch is correct

See picking the right version

[x] All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)

Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.

[x] The commit messages follow our commit message guidelines
[x] The PR follows our contribution guidelines
[x] Code changes follow our coding conventions
[x] This change is covered with tests (or tests aren't necessary for this change)
[x] Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
[x] CI is green

Added a note that it is intended to be overridden by subclasses.

rebased so the installer CI run was happy (see link in issue)

Merge when needed.


Vertex returns incorrect bulge value in some cases

A vertex with a start and end width defined, but a bulge value of 0 returns a non-zero bulge.
I think there is a missing "break" statement after case 40 and case 41 in the vertex parser. Case 41 is hit for the end width, which falls through to case 42. Since the end width is nonzero (curr.value != 0) evaluates to true and the bulge is set to the end width. When the bulge is parsed, and case 42 is hit again, the bulge is actually 0, which then fails to zero or remove the bulge property.
Adding a "break" to case 41 fixes the issue.
If you need, I can try and figure out how to submit a pull request!

Here's a link to the relevant code.
I think you explanation makes sense.

Ah yes. I work with a lot of Visual Basic legacy code and case statements don't fall through in that language. I seem to have forgotten this when committing this code.


Add links to source code in docs

Summary
This PR adds links pointing to the relevant source code to most types/methods/properties/etc. in the documentation. This will generally link to the branch that's being built, unless the current commit is tagged, in which case it'll use that tag instead. As a fallback, the commit hash is used.
Figuring out the current branch on readthedocs is surprisingly difficult, since they checkout the branch ref which results in a detached HEAD state. git name-rev seems to work fine, but I'd love to hear about better solutions, maybe I'm missing something obvious.
Example:
https://disnake-test-1.readthedocs.io/en/feature-docs-link-source/api.html#disnake.Client.application_flags
(note that the links don't work in that build, as the branch doesn't exist in the main repo - just replace feature/docs-link-source with master)
Checklist

[ ] If code changes were made then they have been tested

[ ] I have updated the documentation to reflect the changes
[x] I have formatted the code properly by running black .

[ ] This PR fixes an issue
[x] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, ...)

The logic looks correct, but I don't understand how linkcode_resolve is going to be used, does sphinx.ext.linkcode reference it automatically?

It does, see https://www.sphinx-doc.org/en/master/usage/extensions/linkcode.html.


Events don't create the end part when using drag and drop

Critical information: I think it only works when i click the choice or condition event on the right and not when I drag and drop the event
https://user-images.githubusercontent.com/104588917/178756771-15b9f5e4-bc7c-4d0a-ae3f-53b30f8b0983.mp4
I think the source of the bug is from the drag and drop or something close to it.
hope this helps you solve the bug and thank you and your team for the wonderful addon
Originally posted by @M7mdKady14 in https://github.com/coppolaemilio/dialogic/discussions/1002#discussioncomment-3138138

Should be fixed by #1006


[Question] DataLoader with AsyncVectorEnv

Question
Hello! I am working with an environment where it loads time series data from a torch dataloader. When the environment resets I would like to change the time series interval and get a new sample from the dataloader.
Since it uses multiprocessing I am guessing that passing a shared dataloader object is not a good idea? Can I use a multiprocessing Queue that I fill with samples and pass that to the environment when using gymnasium.vector.make?
Thank you for taking the time to read this

Yes, it is possible to pass keywords to all of the sub-environments
Therefore, you should be able to do, gym.vector.make("CustomEnv", dataloader=shared_dataloader)


large syncs, getting many "User Rate Limit Exceeded" errors

Hey all -
I'm using drive on Ubuntu 16.04 LTS to sync some (huge) local folders - over 600gb in total size. The files inside are various - some are large movies, others are sequences of small text files. It seems to be succesful about 98% of the time, but I am getting some errors (in verbose mode):
googleapi: Error 403: User Rate Limit Exceeded, userRateLimitExceeded
This seems to happen a lot of with the smaller files, though it has happened on a larger file or two. It seems to happen when the comparison is made.
Any advice?
Thanks!
-Mike

Hello there @tk421storm, thank you for the report and welcome to drive!
Interesting but unfortunate that it doesn't work 100% of the time and encounters userRateLimitExceeded.
Thank you for highlighting the scenario in which this happens, it's going to be a great thing to do as well throttling any file comparisons.
I'll mark this for fix for the next release.

I'll add here that this happened to me on a recent push. The specific error was
push: /<file> err: googleapi: Error 403: User rate limit exceeded, userRateLimitExceeded

about 20 or 30 times. Interestingly, the push did finish completely.
The push specs were
Deletion count 609 dest: 4.52MB
Addition count 1 src: 6.13MB

So seconding @tk421storm on the fact that it happens with large amounts of small files.

I've seen this when the push consists of deleting lots (hundreds) of files.

drive Version <IP_ADDRESS>
This is happening to me on every push for the past week. I have to do each push 2 or 3 times. It's for adding and deleting 20 - 40 very small files. Because of the way that Gnucash works, it creates many of these small files to be added and deleted on every push. It's ridiculous that I have to do more than one push for this kind of thing. I'm on a a gigabit fiber connection to the internet.


Expanding the contribution guide, especially including instructions to add a new DataPipe

Stack from ghstack:

-> #354

Expanding the contribution guide, especially including instructions to add a new DataPipe

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


dbeaver/dbeaver-ee#1771 add child types for sqlite

As it was found out, SQLite uses generic child types even though it has its own. This fix will allow editing diagrams in edit mode for SQLite
Linked pr: https://github.com/dbeaver/dbeaver-ee/pull/1920
Linked issue: https://github.com/dbeaver/dbeaver-ee/issues/1771

Verified


dependency-submissoin fails job even with upgraded dependencies

We are running into a situation where the dependency submission is failing, even though the gradle dependencies map shows that the package in question has automatically been replaced with a later version.
As an example:
+--- org.apache.avro:avro:1.11.3
|    +--- com.fasterxml.jackson.core:jackson-core:2.14.2 -> 2.15.4 (*)
|    +--- com.fasterxml.jackson.core:jackson-databind:2.14.2 -> 2.15.4 (*)
|    +--- org.apache.commons:commons-compress:1.22 -> 1.26.1
|    |    +--- commons-codec:commons-codec:1.16.1
|    |    +--- commons-io:commons-io:2.15.1
|    |    \--- org.apache.commons:commons-lang3:3.14.0 -> 3.13.0
|    \--- org.slf4j:slf4j-api:1.7.36 -> 2.0.13

Although there is a vulnerable dependency in commons-compress:1.22, it has been replaced with 1.26.1. However, the build step still fails.
is this intentional behavior? If so, is there a workaround?

Can you please explain what you mean by "the build step still fails"?
Does

The dependency submission action fail, indicating a problem with the action itself, or
Do you have some sort of failure due to the dependency vulnerability?

If the answer is 2, then please check if commons-compress:1.22 is present in the Dependency Graph for your repository. If it appears in the dependency graph then it is very likely that the version is still being resolved in your build.
Please check out this FAQ and the documentation on how to resolve this.

@bigdaz The issue is that it is failing due to a dependency vulnerability and the dependency graph seems to think that org.apache.commons:commons-compress:1.22 is still available whereas it is not.
When we generate the graph via gradle locally we see the following:
org.apache.commons:commons-compress:1.22 -> 1.26.1

This is stating that the transitive dependency has been upgraded from 1.22 to 1.26.1 which is the desired behavior to avoid the vulnerability.
When inspecting at the actual dependencies the project has pulled locally we no longer see 1.22 present at all.
We follow the official gradle documentation to achieve this by adding a constraint as so:
https://docs.gradle.org/current/userguide/dependency_constraints.html
implementation("org.apache.avro:avro:1.11.3")
constraints {
    implementation("org.apache.commons:commons-compress:1.26.1") {
        because("previous versions impacted by: https://github.com/advisories/GHSA-4265-ccf5-phj5")
    }
}

Unless I am missing something the dependency graph seems to ignore this which is the issue at hand.

Please check if commons-compress:1.22 is present in the Dependency Graph for your repository. If it appears in the dependency graph then it is very likely that the version is still being resolved in your build.
Please check out this FAQ and the documentation on how to resolve this.

@ccureau @agsimeonov If you're unable to provide evidence that the action is submitting dependencies that are not being resolved by your build, I'll close this issue.
Please review the docs I linked and provide log output, build scan or something that shows the wrong dependencies are being submitted.


#130 - Add Predicate Search in ACL Page

This change is

Let's use the new style components for new code -- component as function + React hooks for state / redux.

Sure, will do. What benefits do this new style bring? Is it just easier to switch to Redux in the future?

instead of this whole constructor in modern JS you can simply write (constructor):

Thanks, this is good to know.

can we move this outer div to the PredicateSearchBar

Sure, will do. I'm guessing in the future you ideally want all components to hold their own styling?

I've rewritten the PredicateSearchBar as a function based component, moved the html wrapper inside, changed the constructor and fixed a bug related to this feature. Let me know if you want anything else changed.


bitwig-studio: 5.2.5 -> 5.2.7, fix Onset and Beat detection

Update Bitwig to latest stable release 5.2.7.
I also noticed that Onset and Beat detection got broken in the 5.2-series. The fix is a wrapper script that launches Bitwig in a Bubblewrap environment. This is also part of this PR. All the details as to why this is required are in this discourse thread: https://discourse.nixos.org/t/fixing-permissions-when-program-copies-out-of-nix-store/56705
I've contacted the manufacturer but the interest was rather limited after I mentioned not using Ubuntu. Still, if this ever gets fixed upstream, we can just remove the wrapper again.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Many thanks! I did not have time to look into that issue yet, but it is a great relief to see it fixed!

Thanks!

This change appears to have broken MIDI input for me. I'll take a look and see what I can find!

It's definitely bubblewrap and not the upgrade, because running the -unwrapped version makes MIDI work again.
It seems I can add --dev-bind /dev /dev to the bwrap invocation to make MIDI work. I'll get a PR ready.


Retrain fails after switching checkpoint

On a project with existing checkpoints, I'm not able to retrain right after changing to another checkpoint. It only works if I run a prediction after the switch, before retraining.
Error logs:

Checkpoint switch

Retrain request:

Retrain failure:

cc @ingalls @geohacker @LanesGood

This seems fixed, thanks @ingalls


snd: 18.1 -> 18.2

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/snd/versions.
These checks were done:

built on NixOS
ran /nix/store/caxkfgbcv6kplihpx8gbivz6l5sisnv5-snd-18.2/bin/snd --help got 0 exit code
ran /nix/store/caxkfgbcv6kplihpx8gbivz6l5sisnv5-snd-18.2/bin/snd --version and found version 18.2
ran /nix/store/caxkfgbcv6kplihpx8gbivz6l5sisnv5-snd-18.2/bin/snd --help and found version 18.2
found 18.2 with grep in /nix/store/caxkfgbcv6kplihpx8gbivz6l5sisnv5-snd-18.2
directory tree listing: https://gist.github.com/549e1eef8a929e09d72499dc97a47aa2

cc @fuuzetsu for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: snd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: snd
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2
shrinking /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2/bin/snd
gzipping man pages under /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2/bin
patching script interpreter paths in /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2
checking for references to /tmp/nix-build-snd-18.2.drv-0 in /nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2...
/nix/store/n3g291i2cgd7qnf5zz78k4399n6vglhj-snd-18.2

Failure on aarch64-linux (full log)
Attempted: snd
Partial log (click to expand)
make[3]: *** [Makefile:751: test-suite.log] Error 1
make[3]: Leaving directory '/build/gsl-2.4/linalg'
make[2]: *** [Makefile:859: check-TESTS] Error 2
make[2]: Leaving directory '/build/gsl-2.4/linalg'
make[1]: *** [Makefile:930: check-am] Error 2
make[1]: Leaving directory '/build/gsl-2.4/linalg'
make: *** [Makefile:961: check-recursive] Error 1
builder for '/nix/store/p65sz85d0d9aikhiy7fkbk7jrqj0592i-gsl-2.4.drv' failed with exit code 2
cannot build derivation '/nix/store/a05vl7nvl15bmy84qyli86ffrkccrzwq-snd-18.2.drv': 1 dependencies couldn't be built
error: build of '/nix/store/a05vl7nvl15bmy84qyli86ffrkccrzwq-snd-18.2.drv' failed


Use Cookies in Resource Protector

Is your feature request related to a problem? Please describe.
There does not seem to be a way to use the ResourceProtector with the web application flow (login + redirect) because it uses the Authorization header.
Describe the solution you'd like
I would like to be able to use a ResourceProtector to decorate views that are authed using a web app flow.
Ideally the ResourceProtector would look in the request cookies as well as the Authorization header.
(possibly with extra validators to be registered as needed)
Describe alternatives you've considered
Subclassing the ResourceProtector to get the Cookie if the Authorization header is missing.
Additional context

I don't quite understand your question. The OAuth spec has no definition for handling the cookies. I think you've already known your answers, you can always subclass ResourceProtector to define your own way of authentication.

I see, but I don't see how to use the resource protector with the login web application flow. The provider returns the token that the client should then store, but the resource protector always looks in the headers? Do I need to subclass the resource protector for this flow to work?


How to use Huginn to post job to selected job board upon creating a job post on my job board?

Upon creating a job post on my job board, I want an agent that post the same job post to a number of selected free job boards.

That sounds somewhat complex, but if they all have APIs, you should be able to do it with PostAgents and WebsiteAgents.

Thank you. I will see how I can. It's a task I have never tried.

I'm going to close this issue. Please reopen if you have further questions.


Update shift.rst

Seems like the explanation for the -pct flag in the shift documentation was incorreclty transfered from the slop command.

Thank you for catching this!


Fixed Babel warning message & Updated installation process

Good call on 9e6dbdd.
Regarding 043c761, since we're running the final script through Uglify the compact option doesn't really do much. Seems fine to turn it off, and suppressing that notice is a plus.
Thanks!


New Users not getting Reviewer access in Prod environment

When a new user to Formsflow.ai receives a new submission from his/her employee to review a new telework agreement, the user is not able to access the submitted form and is prompted with an "UnAuthorized" error.
The form can be seen in the tasks tab for the new user, however, it has no info filled out and the managers' section is not visible, screenshots below

The form has the following issues-

"unauthorized" error
No pre-population
None of the fields have any data according to the submission made
The manager section is not visible.

Iman suggested this might not be a bug, it might be a tool feature we have not used yet.

Issue
New users onboarding to the PROD is assigned the "Client" role. At this point, assigning other roles including "Reviewer" would require a manual role assignment through the Keycloak dashboard.
Goal
This ticket goal is to automate this process so that Tool automatically assigns the "Reviewer" role to the supervisor.
Decide on the solution to fix
The important question for the team is to define when the "Reviewer" role is assigned to the supervisor?
Some possibilities come to mind:

Based on the info of the user's IDIR login (e.g., name, email, idir), decide to assign the "Reviewer" role to that logged-in user?
Whoever clicked on the supervisor email (e.g., https://digital-journeys-dev.apps.silver.devops.gov.bc.ca/task/3e254d12-e5a1-11ec-8eda-0a580a618dca) that is sent in the workflow, will be a "Reviewer" and can review the assigned tasks?

After a discussion with @Stella-Archer, I was to look into the possibility of adding the "Reviewer" role to all new users in the PROD. With that regard, I looked into the permissions associated with the "Reviewer" role and compared that to the "Client" role.
Clients can only see their own submitted forms under the "Application" and "Task" tabs. They cannot sign off a submission even if it is assigned to them.
Reviewers can see their own and other submitted forms under the "Application" and "Task" tabs. They are only able to sign off the submissions that are assigned to them.

Please see comment on #308 for details on different roles access level and let me know if want to change access-levels for each role.

@HasanSifat @Stella-Archer
In terms of the next steps for this ticket, should I go ahead with this comment from Hasan from #308?

Expected behaviour-
By default, users in the following environment need to get these roles-
DEV
client
reviewer
designer
TEST
client
reviewer* only able to review forms assigned to them for approval/denial
PROD
client
reviewer* only able to review forms assigned to them for approval/denial

@iman-jamali-fw,  I would recommend going ahead with this proposed setting and after that, we can test to see how the use cases are functioning. You mentioned having a conversation with Stella and Meghan this week in a previous comment. If my proposed configuration meets those discussed requirements, we should be good to go.

TEST and PROD now assign client and reviewer roles -- by default to the new users.

Reviewer access to Prod Environment has been solved. New users going into prod only have reviewer/client access confirmed.

Accessibility and privacy-related issue that was identified is that clients coming to the "forms" tab have now only two options for each form available to them: "Submit new" or "View Submissions"
When clicking on "View submissions" the client sees all historical submissions made by anyone/everyone. Screenshot below:

Acceptance Criteria:
Clients should only see their own submissions made for each form. So ideally, if a certain client has made 1 submission they should be able to see only 1 submission history when going into "View Submissions"

@HasanSifat I logged in as a new user on both PROD and TEST and only see one button under Form for submitting a new form. Can you help me reproduce the situation when a new user can see "View Submissions"?

I opened a PR to fix this issue.
https://github.com/bcgov/digital-journeys/pull/317

@iman-jamali-fw Hi Iman! I tested this out one more time with a new user in test and they are not getting the "review submissions" button anymore. Moving this to QA again as this issue seems to have been solved. We'll do a final round of testing before closing this issue.
Thanks for all the help! :)


Integrate Aer benchmarks into Qiskit metapackage

Summary
Integrate Aer benchmarks
Major changes are:

Created aer and terra directories and move corresponding benchmarks there.
Updated utils.py to add more common code.
Homogenize circuit build function names.
Renamed terra benchmark files for consistency.
Removed asv.conf.json and created two different config files for aer and terra respectively.

Details and comments
With the goal in mind of having all regression benchmarks in one central point, all
of the AER benchmarks have been moved away from Aer repo to the Qiskit metapackage
repository, where Terra benchmarks reside at the moment. Because there's a lot of
code in common between Terra and Aer benchmarks, I have refactored a bit of code
as part of the integration to gain in clarity and consistency.
Aer benchmarks will run in their own baremetal instance though, to not interfere
with Terra benchmarks, but the results of the benchmark should be published in the
same place, although this is addressed in the PR, it's the script running the benchmarks the one that needs to be updated to do so.
The way to launch each of the benchmarks is now:
$ asv run --config <asv.aer.conf.json|asv.terra.conf.json> run ...

TODO

[x] Test that everything works as expected with Aer benchmarks
[x] Test that everything works as expected with Terra benchmarks

Terra benchmarks are failing with this error:
virtualenv: error: unrecognized arguments: --no-site-packages

Will investigate further tomorrow.

Fixed

So I haven't had a chance to look at everything in depth yet. But from a high level my biggest concern is implicit versioning and the long term history. Asv by default uses a hash of the source for the benchmark as the version: https://asv.readthedocs.io/en/stable/writing_benchmarks.html#benchmark-versioning so by changing the code even if just to update paths or function names we're going to be invalidating the historical data for previous runs. At least for me when I weigh that against unifying the code I think it's more important to keep the historical data than de-duplicating and integrating the benchmark suites. What do you think?

Can we hard code the existing hash or maybe this can coincide with moving benchmarking hardware?

There's a trade-off here between historical data and project organization.
It all depends on how important is the historical data for us.
I'm leaning towards project organization (thus easier maintainability) just because I think the main point of performance regressions benchmarks, is to detect near-term problems in the code being introduced, so only a small portion of the historical data is actually relevant. I don't think comparing with how Qiskit was performing, let's say, 4 releases ago would give us any insights that we haven't knew already.
I have a question though. Does it mean that we need to chose since when we want to restart the benchmarks? ... because running everything since the beginning is non-go situation for me.

@atilag Are you still working on this PR?

Oh no. I'm closing this :)


ionic.bundle.min.js broken in master

was trying to update ionic master to latest to get the ios9 fixes:
the minified ionic.bundle.min.js from release: v1.1.0-nightly-1558 is broken and results in app not starting
worked fine in v1.1.0-nightly-1533
maybe because of this? https://github.com/driftyco/ionic/commit/c145945f5b5dfb6171677204225efa2d8592fe0b#commitcomment-13235350
Uncaught Error: [$injector:modulerr] http://errors.angularjs.org/1.4.3/$injector/modulerr?p0=testapp&p1=Error…ttp%3A%2F%2Flocalhost%3A8100%2Fjs%2Fionic%2Fionic.bundle.min.js%3A50%3A339)
(anonymous function) @ ionic.bundle.min.js:37
(anonymous function) @ ionic.bundle.min.js:69
m @ ionic.bundle.min.js:38
g @ ionic.bundle.min.js:68
eb @ ionic.bundle.min.js:71
d @ ionic.bundle.min.js:50
Ac @ ionic.bundle.min.js:51
(anonymous function) @ (index):287
n.Callbacks.j @ jquery.js:3099
n.Callbacks.k.fireWith @ jquery.js:3211
n.extend.ready @ jquery.js:3417
I @ jquery.js:3433

Greetings @bymodude!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Hey @bymodude, that's entirely possible. We don't see that in our example apps, can you share an example that reproduces this?

it seems the fix would be simply this: https://gist.github.com/IgorMinar/863acd413e3925bf282c#gistcomment-1574927

'doh!

fixed in 861297a99a82c60921a6faa2dffd6cbe573c2564


The customizing-the-parse-and-display-formats link does not work

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The #customizing-the-parse-and-display-formats link should redirect to the relevant content
What is the current behavior?
Clicking on the link redirects to the home page with URL:
https://material.angular.io/#customizing-the-parse-and-display-formats
What are the steps to reproduce?

Navigate to: https://material.angular.io/components/datepicker/overview
Click on the 'Customizing the parse and display formats' link

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All browsers

I think the link you mean is,
https://material.angular.io/components/datepicker/overview#customizing-the-parse-and-display-formats
I do vaguely recall this being an issue once before, and you may be running a cached version of the docs site. Try hard reloading.

Visit chrome://serviceworker-internals/ and unregister the worker for material.angular.io. This will clear the service worker cache, which persists through hard refresh.

@jelbourn - Tried unregistering the material.angular.io service worker, and;
@willshowell - Yea I think that's probably the right URL, didn't know what the right one was, but did try clearing the cache, even reinstalled a new version of Chrome on a colleagues new laptop, can still reproduce

I can't reproduce as well. The issue should have been fixed by this commit, which introduced the headerLink component for the doc-viewer.
Although there is still an issue with the documentation related to the same problem. See https://github.com/angular/material2/issues/8503. This can be fixed by https://github.com/angular/material.angular.io/pull/329


Update chart grafana to 8.4.1

This PR contains the following updates:

Package
Update
Change

grafana (source)
patch
8.4.0 -> 8.4.1

Release Notes

grafana/helm-charts (grafana)
v8.4.1
Compare Source
The leading tool for querying and visualizing time series and metrics.
What's Changed

[grafana] Update appVersion to 11.1.3 by @terop in https://github.com/grafana/helm-charts/pull/3253

Full Changelog: https://github.com/grafana/helm-charts/compare/k8s-monitoring-1.4.4...grafana-8.4.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


[FEAT] Create strategy for supporting different platform versions

:bulb: Feature request
Feature Name

Create strategy for supporting different platform versions
The Desired Behavior

The following questions need answers:

When a new version of a platform is released and we update the driver, what happens to the previous version?
What should the migration path be for apps that upgrade to the new platform version?
What should the migration path be for apps that don't upgrade to the new platform version but upgrade to a new daffodil version?

An interesting solution is having a separate installable library that tracks platform versions instead of daffodil versions. Daffodil could introduce breaking changes but only by changing the driver interface. This would allow apps to upgrade platform drivers and daffodil separately.


How can i get the final request.url?

the resource:
export const Account = Vue.resource(API_ROOT + '/accounts{/id}')
the interceptors
Vue.http.interceptors.push((request, next) => {
  var key = request.url.replace(API_ROOT, '')
  console.log(key, request, data[key])
  next(request.respondWith(data[key], {
    status: '200',
    ok: true
  }))
})

request.url is /accounts{/id} but i expect get /accounts/me

got it from source code! use request.getUrl()