Compile eBPF probe for custom kernel

Describe the bug
I need to support multiple OS and Kernels. Some of the kernels have been customized, when i try to install the falco the compiling of the probe fails
How to reproduce it
# ./falco-driver-loader bpf
* Running falco-driver-loader with: driver=bpf, compile=yes, download=yes
* Mounting debugfs
* Found kernel config at /proc/config.gz
* Trying to compile the eBPF probe<EMAIL_ADDRESS>make: *** /usr/src/@PROBE_NAME@-@PROBE_VERSION@/bpf: No such file or directory.  Stop.
mv: cannot stat ‘/usr/src/@PROBE_NAME@-<EMAIL_ADDRESS>No such file or directory
* Trying to download a prebuilt eBPF probe from @DRIVERS_REPO@/@PROBE_VERSION@/<EMAIL_ADDRESS>curl: (6) Could not resolve host: DRIVERS_REPO@; Unknown error
Download failed

Expected behaviour
The probe will be compiled, since the kernel is custom I dont expect it to be in the bintray directory
Environment

Falco version:
.26.1

System info:

Cloud provider or hardware configuration:
hardware

OS:

# cat /etc/os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.8 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.8"

Kernel:

Linux myhost 3.10.0-1127.10.1.el7.<CUST>.20200605.60.x86_64 #1 SMP Fri Jun 5 13:51:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Installation method:
Initially docker container but down to using loader script to test

Additional context

Hi @soopanova - Welcome to the Falco project!
It looks like you are using the falco-driver-loader from the source repo, the script changed at compile time when the variables @PROBE_NAME@, @DRIVERS_REPO@ and @PROBE_VERSION@ are interpolated.
To get a working one you need to look it up under your build folder build/scripts/falco-driver-loader
Feel free to ask if you have any doubt.

@soopanova: There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

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/test-infra repository.

Adding kind documentation since we can probably make this more clear - I bet other users are having the same problem

Tried the fix and still had an issue. To keep debugging I tried to use the official docker image, with a common Kernel and still got the same errors:

Kernel:

# uname -r
3.10.0-1127.19.1.el7.x86_64

Trying kernel module:
# docker run --rm -i -t     --privileged     -v /dev:/host/dev     -v /proc:/host/proc:ro     -v /boot:/host/boot:ro     -v /lib/modules:/host/lib/modules:ro     -v /usr:/host/usr:ro     -v /etc:/host/etc:ro     falcosecurity/falco:latest
* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* falco module still loaded, waited 5s (max wait 60s)
* falco module still loaded, waited 10s (max wait 60s)
* falco module still loaded, waited 15s (max wait 60s)
* falco module still loaded, waited 20s (max wait 60s)
* falco module still loaded, waited 25s (max wait 60s)
* falco module still loaded, waited 30s (max wait 60s)
* falco module still loaded, waited 35s (max wait 60s)
* falco module still loaded, waited 40s (max wait 60s)
* falco module still loaded, waited 45s (max wait 60s)
* falco module still loaded, waited 50s (max wait 60s)
* falco module still loaded, waited 55s (max wait 60s)
* falco module still loaded, waited 60s (max wait 60s)
* falco module seems to still be loaded, hoping the best
2020-10-22T04:10:43+0000: Falco version 0.26.1 (driver version 2aa88dcf6243982697811df4c1b484bcbe9488a2)
2020-10-22T04:10:43+0000: Falco initialized with configuration file /etc/falco/falco.yaml
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/falco_rules.local.yaml:
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/k8s_audit_rules.yaml:
2020-10-22T04:10:43+0000: Unable to load the driver.
2020-10-22T04:10:43+0000: Runtime error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco module is loaded.. Exiting.

Also tried the ebpf:
# docker run --rm -i -t \
>     --privileged \
>     -e FALCO_BPF_PROBE="" \
>     -v /dev:/host/dev \
>     -v /proc:/host/proc:ro \
>     -v /boot:/host/boot:ro \
>     -v /lib/modules:/host/lib/modules:ro \
>     -v /usr:/host/usr:ro \
>     -v /etc:/host/etc:ro \
>     falcosecurity/falco:latest
* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=bpf, compile=yes, download=yes
* Mounting debugfs
* Found kernel config at /host/boot/config-3.10.0-1127.19.1.el7.x86_64
* Trying to compile the eBPF probe (falco_centos_3.10.0-1127.19.1.el7.x86_64_1.o)
In file included from /usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/probe.c:9:
/usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/quirks.h:15:2: error: Kernel version must be >= 4.14
      with eBPF enabled
#error Kernel version must be >= 4.14 with eBPF enabled
 ^
In file included from /usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/probe.c:13:
In file included from include/linux/sched.h:33:
include/linux/signal.h:78:11: warning: array index 3 is past the end of the array (which contains 1 element)
      [-Warray-bounds]
                return (set->sig[3] | set->sig[2] |
./arch/x86/include/asm/signal.h:23:2: note: array 'sig' declared here
        unsigned long sig[_NSIG_WORDS];

****snip out errors ****

fatal error: too many errors emitted, stopping now [-ferror-limit=]
50 warnings and 20 errors generated.
make[2]: *** [/usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/Makefile:33: /usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/probe.o] Error 1
make[1]: *** [Makefile:1316: _module_/usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf] Error 2
make: *** [Makefile:18: all] Error 2
mv: cannot stat '/usr/src/falco-2aa88dcf6243982697811df4c1b484bcbe9488a2/bpf/probe.o': No such file or directory
* Trying to download a prebuilt eBPF probe from https://dl.bintray.com/falcosecurity/driver/2aa88dcf6243982697811df4c1b484bcbe9488a2/falco_centos_3.10.0-1127.19.1.el7.x86_64_1.o
curl: (22) The requested URL returned error: 404 Not Found
Download failed
2020-10-22T04:11:37+0000: Falco version 0.26.1 (driver version 2aa88dcf6243982697811df4c1b484bcbe9488a2)
2020-10-22T04:11:37+0000: Falco initialized with configuration file /etc/falco/falco.yaml
2020-10-22T04:11:37+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2020-10-22T04:11:37+0000: Loading rules from file /etc/falco/falco_rules.local.yaml:
2020-10-22T04:11:37+0000: Loading rules from file /etc/falco/k8s_audit_rules.yaml:
2020-10-22T04:11:38+0000: Unable to load the driver.
2020-10-22T04:11:38+0000: Runtime error: can't open BPF probe '/root/.falco/falco-bpf.o': Errno 2. Exiting.

Hello, eBPF can't build on that kernel. See line in the logs: Kernel version must be >= 4.14 with eBPF enabled.

Trying kernel module:
# docker run --rm -i -t     --privileged     -v /dev:/host/dev     -v /proc:/host/proc:ro     -v /boot:/host/boot:ro     -v /lib/modules:/host/lib/modules:ro     -v /usr:/host/usr:ro     -v /etc:/host/etc:ro     falcosecurity/falco:latest
* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* falco module still loaded, waited 5s (max wait 60s)
* falco module still loaded, waited 10s (max wait 60s)
* falco module still loaded, waited 15s (max wait 60s)
* falco module still loaded, waited 20s (max wait 60s)
* falco module still loaded, waited 25s (max wait 60s)
* falco module still loaded, waited 30s (max wait 60s)
* falco module still loaded, waited 35s (max wait 60s)
* falco module still loaded, waited 40s (max wait 60s)
* falco module still loaded, waited 45s (max wait 60s)
* falco module still loaded, waited 50s (max wait 60s)
* falco module still loaded, waited 55s (max wait 60s)
* falco module still loaded, waited 60s (max wait 60s)
* falco module seems to still be loaded, hoping the best
2020-10-22T04:10:43+0000: Falco version 0.26.1 (driver version 2aa88dcf6243982697811df4c1b484bcbe9488a2)
2020-10-22T04:10:43+0000: Falco initialized with configuration file /etc/falco/falco.yaml
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/falco_rules.local.yaml:
2020-10-22T04:10:43+0000: Loading rules from file /etc/falco/k8s_audit_rules.yaml:

What I suspect here is that the Falco container can't run properly because the kernel module driver is already loaded into your host. Could you retry ensuring that you removed it?
What's the output of cat /proc/modules | grep falco before running this container?

Anyways, other 3 options to try out come to my mind:
Tarballs
Have you tried to install Falco using this?
It contains the falco-driver-loader ready to be used, in your binary directory, after installation.
RPM
Alternatively, you could use our RPM. Instructions here.
Driverkit
Since you mentioned different kernels, some of them customized, you could give a try to driverkit.
It's a nice tool able to prebuild Falco drivers starting from a simple YAML configuration files. Its README contains a lot of examples for inspiration, and it also supports custom Kernel configs.

@leodido After more digging I went back to the kernel module. The reason it keeps thinking that the module is loaded is due to a grep statement in the falco-driver-loader hits on a similarly named module and thinks its loaded. After patching the script everyting installed correctly. I will take a look at the Driverkit documentation, i would rather use eBPF over Kernel Module. This issue can be closed.

Oh, gotcha!
Would you please indicate to us the exact line you're referring?
Maybe we can make it more solid... :)

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/test-infra repository.


Unlabeled multi-dimensional array cannot be used for indexing: lat

Please note
If you are reporting an installation or module import issue, please note that
this project only accepts reports about problems with packages downloaded from
the Python Package Index. Conda users should take issues to one of the
following trackers:

https://github.com/ContinuumIO/anaconda-issues/issues
https://github.com/conda-forge/shapely-feedstock

Expected behavior and actual behavior.
(For example: the area of my geometry is 1.417 when it should be 1.414.)
Steps to reproduce the problem.
(For example, a script with required data)
Operating system
(For example, Mac OS X 10.12.3)
Shapely version and provenance
(For example, 1.6b4 installed from PyPI using pip)

@Wangou666wang if you want to report a problem or ask a question, you will need to expand on that. For example showing a code example with the current output and explain why you expect something different (see also https://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports)

Closing as there is not enough information. @Wangou666wang if you update the question, we can certainly reopen the issue.


Exchange Rate Monitoring

Similar to https://github.com/OriginProtocol/origin-dollar/issues/310, we should alert ourselves if any of our oracles report prices outside of expected ranges. This is probably straightforward for the stablecoin exchange rates, but I'm not sure what we would consider to be unexpected for ETH movement. cc @DanielVF

Think I'd call this replaced by #417


Added run script.

It's a very simple bash script that makes the process of running Silvius a touch easer. Now, instead of doing the list-mics script, saving the index, etc. manually, the run.sh script will do that for you.
Not sure if it's in line with what you want for the repo, but this is basically an enhanced version of the script I use whenever I'm launching silvius myself anyhow, so here you go. Do what you will with it. :-)

Uses command-line parameters now.

Squashed and merged into master. Thanks!


Add required arguments as external params to start the pipeline

Description of feature
Currently, the pipeline requires the channels from --step panelprep to run the following modes. To start the pipeline simply from different steps (such as --step impute), some files are necessary depending on the tool used (such as chunks, posfile, bams and panel ). The bams and panel can be added via a csv with --input and --panel. We should add the other files as external params.
### Tasks
- [ ] https://github.com/nf-core/phaseimpute/issues/59
- [ ] https://github.com/nf-core/phaseimpute/issues/57
- [ ] Handle --posfile param for --step impute (all tools)
- [ ] design tests for each --step and --param
- [ ] https://github.com/nf-core/phaseimpute/issues/60
- [ ] hap_legend for quilt
- [ ] https://github.com/nf-core/phaseimpute/issues/63

For the other files to be added, should we set one per chromosome and add optional column to the panel samplesheet ?

I was thinking them to be samplesheets as well. For instance, --chunks samplesheet_chunks.csv where samplesheet_chunks.csv would look like:
chr, file
chr1, chunk_file_glimpse1.txt
chr2, chunk_file_glimpse1.txt

File could be a .txt or .bin.
Glimpse1 and QUILT use .txt and Glimpse2 could use .bin.

@LouisLeNezet Let's brainstorm potential structures of samplesheets starting from --steps impute:

--posfile posfile.csv

chr
file
sites vcf

chr1
chr1_posfile_stitch.txt
chr1_sites_glimpse.vcf

chr and file are mandatory for all pipelines using posfile,
sites vcf is only mandatory for glimpse1
What should the default structure of the .txt file be? Should the .txt file be glimpse1 or stitch posfile? What if the user wants to only use stitch?

--panel panel.csv (all tools except stitch)

panel
chr
file
index
hap
legend

1000G
chr1
chr1_phased_panel.vcf.gz
chr1_phased_panel.vcf.gz.tbi
chr1_phased_panel.hap
chr1_phased_panel.legend

hap and legend are only required in quilt.

--chunks chunks.csv

panel
chr
file

1000G
chr1
chr1_chunks_glimpse1.txt

Hi,
What you suggest is fine for me.
Considering the default structure of the posfile txt file the stitch format seems more appropriate as you suggested.
Also, isn't the .legend equivalent to the posfile ?

.legend: CHROM:POS_REF_ALT POS REF ALT
.posfile_stitch: CHROM POS REF ALT
We could simply reformat it, no ?


Prefixed Zephyr public headers with <zephyr/..> using scripts/utils/migrate_includes.py from the Zephyr repository

Added 'hpp' postfix to extension list in migrate_include.py see https://github.com/zephyrproject-rtos/zephyr/pull/53042
and https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v3.1.0 for details
it seems that include/zpp/error_code.hpp have had line ending changes done by the migrate_include.py script

Sorry for not noticing this pull request, I will try to merge it ASAP.

it seems that include/zpp/error_code.hpp have had line ending changes done by the migrate_include.py script

I'll fix that by hand, that shouldn't be a problem.

@anedergaard I merged your changes in master.

Great @lowlander, thanks!


feat: elastic tests

Issue being fixed or feature implemented

Smoke tests did not test the elastic logging cluster
What was done?

Write test for logs servers
How Has This Been Tested?

On testnet
Breaking Changes

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone

Yes, I want to be able to monitor the logs nodes on testnet. Smoke tests are currently not working on other networks for other reasons, so no point merging it there first.


Dependency on <IP_ADDRESS>

This is a copy of https://github.com/rht-labs/labs-ci-cd/issues/196.
@bit4man
TASK [openshift-applier/roles/openshift-applier : Create OpenShift objects based on template with params for 'projectrequest : ci-cd'] **********************************************************************
fatal: [projects-and-policies]: FAILED! => {"changed": true, "cmd": "oc process --local -f https://raw.githubusercontent.com/redhat-cop/cluster-lifecycle/v3.9.0/files/projectrequest/template.yml --param-file=/tmp/src/params/projectrequests/ci-cd | oc create -f - ", "delta": "0:00:01.311313", "end": "2018-06-20 00:51:09.078042", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2018-06-20 00:51:07.766729", "stderr": "Unable to connect to the server: dial tcp: lookup ose39-master1.rhdemo.net on <IP_ADDRESS>:53: no such host", "stderr_lines": ["Unable to connect to the server: dial tcp: lookup ose39-master1.rhdemo.net on <IP_ADDRESS>:53: no such host"], "stdout": "", "stdout_lines": []}

The DNS server that responds is a local DNS server, this dnsmasq instance is only listening to a virtual network address - localhost is not one of them. So a direct resolve only works when run from within the VM. The hosts are all in the /etc/hosts file which dnsmasq translates into dns entries - but from the host itself, that isn't happening.
Not sure where the <IP_ADDRESS> comes from - not using that here. But I can get past this issue by ensuring I run "run.sh" from a host that can use dns to resolve the master address.

The openshift-applier isn't involved with this aspect. This is strictly just calling oc process and oc create. Any issues related to this is beyond the openshift-appliers area of responsibility and is on the hosting systems configuration or operational environment.
Closing out this ticket as not-applicable.


✨ Added custom integrations - Content API Keys and "Site rebuild" webhooks

closes TryGhost/Ghost#9942

move custom integrations UI out from behind the developer experiments flag
put Admin API key and web hook secret fields behind the developer experiments flag
do not show "unsaved changes" modal when adding/editing a webhook
fixed all webhooks showing for each custom integration

Coverage increased (+0.005%) to 70.775% when pulling 7e438b8ada0874209da55d7d2d5dca5972e139b7 on kevinansfield:finalize-integrations into ea227d7c5cef207569f365001e6e4b21c5e33762 on TryGhost:master.


Base design doc for JUnit Platform support

Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[ ] Ensured that basic checks pass: ./gradlew quickCheck

For all non-trivial changes that modify the behavior or public API:

[x] Before submitting a pull request, I started a discussion on the Gradle developer list,
the forum or can reference a JIRA issue.
[x] I considered writing a design document. A design document can be
brief but explains the use case or problem you are trying to solve,
touches on the planned implementation approach as well as the test cases
that verify the behavior. Optimally, design documents should be submitted
as a separate pull request. Samples
can be found in the Gradle GitHub repository. Please let us know if you need help with
creating the design document. We are happy to help!
[ ] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
I ran a build on your local machine via the command
./gradlew quickCheck <impacted-subproject>:check.
[ ] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

Design doc covering the problem statement for JUnit Platform support
and the related infrastructure issues. This is meant to facilitate
discussion and agreement on what should be solved in the scope of
supporting the JUnit Platform.
Issue: #828

Thanks for the pull request and your thoughts. We are going to use the document as starting points for filling in the blanks.


LEAP: Is zone: us-central1-a correct, or should it be regional as zone: us-central1?

@yuvipanda did you migrate some clusters from zonal to regional recently?
I tried to use python deployer use-cluster-credentials leap recently but got an error that went away by updating the leap/cluster.yaml's zone to be a region instead of a zone.
https://github.com/2i2c-org/infrastructure/blob/45e51afe8335e9f8efc700e3a95f3c21dd2bf36a/config/clusters/leap/cluster.yaml#L7
Is there a change to be made here, and also, in other clusters about this?

I ran into this too. I believe it's https://github.com/2i2c-org/infrastructure/pull/1251 that changed the clusters and we should definitely merge that asap.
I just changed locally us-central1-c to us-central1 in https://github.com/2i2c-org/infrastructure/blob/45e51afe8335e9f8efc700e3a95f3c21dd2bf36a/config/clusters/leap/cluster.yaml#L7 to be able to run python deployer use-cluster-credentials leap and access the logs successfully.

I think this was resolved in #1251.


Grant the caselaw-unpublished-reader role to the editor user and the caselaw-admin role

The editor-ui user needs the ability to view unpublished judgments, so that if/when https://github.com/nationalarchives/ds-caselaw-custom-api-client/pull/75 is merged the editor application does not lose the ability to view them.
Additionally, grant the caselaw-admin role the ability to view unpublished judgments, as I believe this role should inherit that privilege.
I did consider granting the caselaw-writer role the ability to view unpublished judgments. However, I believe there may be a need for some users to be able to write published judgments, but not view/write unpublished ones, so it makes sense to keep them separate.
Question: Do we need a "write unpublished" permission separately as well?

I think moving to a caselaw-unpublished-writer and not adding a caselaw-writer role gives semantic accuracy whilst implying "this doesn't exist but there is space for it to exist if you need it to", I don't know how painful that'd be.


UTY-709 Implement base and tests for the component readers

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Redo of #126 (Sans EntityManager extensions, Logging changes)
Adds reader functionality:

Data through ECS entities
Authority through ECS entities
Callbacks:

AuthorityChanged
ComponentUpdated
Per field updates

Tests
Adds unit tests, tested locally
Documentation
Inline documentation for some methods
Primary reviewers
@jamiebrynes7 @MPeti01

hmm, the base change messed up the PR... will fix


Use index util funtions outside of crate.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.52%. Comparing base (496323f) to head (040e43b).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #719   +/-   ##
=======================================
  Coverage   90.52%   90.52%
=======================================
  Files          76       76
  Lines       10165    10165
  Branches    10165    10165
=======================================
  Hits         9202     9202
  Misses        881      881
  Partials       82       82

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Web development resource requires a major update

Could I please suggest some updates to the Web Development resource page?
I see that the list is not well structured. We can certainly do it better by structuring it well (In the order of increasing difficulties)
Also we need to point the visitors in the right direction.
Also how about improving the thumbnails? Say make it more responsive and interactive.
Please advice if I could work on the above?

Yes @alok-38, tell me when you're ready, you can work on this issue

I'm ready

Okay then I am assigning this issue to you

Hello @alok-38 , I've closed all the PR's which you raised because you've touched some sensitive files in which changes were not required, Create a new fork and start fresh again, And now only touch the files which I mention in the issue description

For this issue, you have to make changes only inside the Web-development-resources.md

Okay. I will do that.

@alok-38 any updates on this issue ?

@alok-38 ?


[Feature Request] Add form persistence

Motivation
We all use forms. But often it happens that we fill out the form not right away, but after some time. Or we are in the metro and the connection is not stable. Or maybe we accidentally (or purposefully) reload the page. It would be nice if fields in a form were saved in such cases. For this purpose, some local storages is perfect, for example - localStorage, sessionStorage or storing certain parameters in the URL.
Examples

Formik Persist
React Hook Form Persist
FormPersistence

Effector persistence libraries

Effector Storage

Usage
import {
  createArrayField,
  createField,
  createForm,
} from '@effector-reform/core';
import { sample, createEffect } from 'effector';
import { persist } from 'effector-storage/local';

const DEBOUNCE_TIME = 300;

const $form = createForm({
  schema: {
    name: createField('John'),
    age: 27,
  },
});

persist({
   store: $form,
   key: 'form',
   timeout: DEBOUNCE_TIME
});

form is a model, which can't be persistable by default. We have two possible ways to resolve this problem:

Create $persisted store (or with another name), which changes form values while writing and serializing into plain object while reading

persist({
   store: form.$persisted,
   key: 'form',
});

create persistForm which has similar mechanism but in separated function.

const persistedForm = persistForm(form);

persist({
   store: persistedForm,
   key: 'form',
});


USB devices attachment

Please browse the existing issues and filter by 'enhancement' to make sure this has not already been suggested!
Hi,
Are there any plans to introduce USB devices attachment ability in UTM? Such a feature is a must for virtualisation.

Duplicate of #46
check out 2.1.0 beta.

You duplicate issue talks about iOS version of UTM and I'm talking about Mac version of UTM.

Did you open 2.1.0 beta?

I'm considering it. Is it possible to install beta over normal version and then normal version over beta?


[core] Add a unit test for: https://github.com/Lilypad-Tech/lilypad/pull/175

Closed in favor of #401


Client closing the connection? Can't connect to UI.

I cannot connect the UI through http://localhost:443
This may have somthing to do with the message in the logs:
[Wed Feb 15 16:46:00 2017][837] openvassd 5.1.0 started
[Wed Feb 15 16:46:56 2017][1359] Client closed the communication
[Wed Feb 15 16:47:19 2017][837] Received the Terminated signal
[Tue Mar 28 13:47:30 2017][23] openvassd 5.1.0 started
[Tue Mar 28 13:48:17 2017][168] Client closed the communication

I have encountered this same issue on two machines. Please tell me what I am doing wrong.
Full logs attached below.
redis not yet ready
Redis ready.
Checking for empty volume
Restarting services
 * Restarting openvas-scanner openvassd
   ...done.
 * Restarting openvas-manager openvasmd
   ...done.
 * Restarting openvas-gsa gsad
   ...done.
Reloading NVTs
Rebuilding NVT cache... done.
Checking setup
openvas-check-setup 2.3.7
  Test completeness and readiness of OpenVAS-9

  Please report us any non-detected problems and
  help us to improve this check routine:
  http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

  Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.

  Use the parameter --server to skip checks for client tools
  like GSD and OpenVAS-CLI.

Step 1: Checking OpenVAS Scanner ...
        OK: OpenVAS Scanner is present in version 5.1.0.
        OK: redis-server is present in version v=3.0.6.
        OK: scanner (kb_location setting) is configured properly using the redis-server socket: /var/run/redis/redis.sock
        OK: redis-server is running and listening on socket: /var/run/redis/redis.sock.
        OK: redis-server configuration is OK and redis-server is running.
        OK: NVT collection in /var/lib/openvas/plugins contains 51943 NVTs.
        WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
        SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html).
        OK: The NVT cache in /var/cache/openvas contains 51943 files for 51943 NVTs.
Step 2: Checking OpenVAS Manager ...
        OK: OpenVAS Manager is present in version 7.0.0.
        OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
        OK: Access rights for the OpenVAS Manager database are correct.
        OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
        OK: OpenVAS Manager database is at revision 184.
        OK: OpenVAS Manager expects database at revision 184.
        OK: Database schema is up to date.
        OK: OpenVAS Manager database contains information about 51943 NVTs.
        OK: At least one user exists.
        OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db.
        OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db.
        OK: xsltproc found.
Step 3: Checking user configuration ...
        WARNING: Your password policy is empty.
        SUGGEST: Edit the /etc/openvas/pwpolicy.conf file to set a password policy.
Step 4: Checking Greenbone Security Assistant (GSA) ...
        OK: Greenbone Security Assistant is present in version 7.0.0.
        OK: Your OpenVAS certificate infrastructure passed validation.
Step 5: Checking OpenVAS CLI ...
        OK: OpenVAS CLI version 1.4.5.
Step 6: Checking Greenbone Security Desktop (GSD) ...
        SKIP: Skipping check for Greenbone Security Desktop.
Step 7: Checking if OpenVAS services are up and running ...
        OK: netstat found, extended checks of the OpenVAS services enabled.
        OK: OpenVAS Scanner is running and listening on a Unix domain socket.
        OK: OpenVAS Manager is running and listening on a Unix domain socket.
        OK: Greenbone Security Assistant is running and listening on all interfaces.
        WARNING: Greenbone Security Assistant is listening on port 4000, which is NOT the default port!
        SUGGEST: Ensure Greenbone Security Assistant is listening on one of the following ports: 80, 443, 9392.
Step 8: Checking nmap installation ...
        WARNING: Your version of nmap is not fully supported: 7.01
        SUGGEST: You should install nmap 5.51 if you plan to use the nmap NSE NVTs.
Step 10: Checking presence of optional tools ...
        OK: pdflatex found.
        OK: PDF generation successful. The PDF report format is likely to work.
        OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
        OK: rpm found, LSC credential package generation for RPM based targets is likely to work.
        OK: alien found, LSC credential package generation for DEB based targets is likely to work.
        OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.

It seems like your OpenVAS-9 installation is OK.

If you think it is not OK, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.

Tailing logs
==> /var/log/openvas/gsad.log <==
gsad main:MESSAGE:2017-02-15 16h41.02 utc:859: Starting GSAD version 7.0.0
gsad main:MESSAGE:2017-02-15 16h41.02 utc:859: main: Locale for gettext extensions set to "C", gettext translations are disabled.
gsad xslt:WARNING:2017-02-15 16h41.02 utc:859: init_language_lists: Failed to open locale directory "/usr/share/openvas/gsa/locale": No such file or directory
gsad main:MESSAGE:2017-03-28 13h46.16 utc:45: Starting GSAD version 7.0.0
gsad main:MESSAGE:2017-03-28 13h46.16 utc:45: main: Locale for gettext extensions set to "C", gettext translations are disabled.
gsad xslt:WARNING:2017-03-28 13h46.16 utc:45: init_language_lists: Failed to open locale directory "/usr/share/openvas/gsa/locale": No such file or directory

==> /var/log/openvas/openvasmd.log <==
base gpgme:MESSAGE:2017-03-28 13h47.19 utc:134: Setting GnuPG dir to '/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2017-03-28 13h47.20 utc:134: Using OpenPGP engine version '2.1.11'
md   main:   INFO:2017-03-28 13h47.21 utc:134:    Updating NVT cache.
md    otp:MESSAGE:2017-03-28 13h47.22 utc:134: Waiting for scanner to load NVTs: 45400 / 51943.
md   main:   INFO:2017-03-28 13h47.32 utc:151: update_or_rebuild_nvt_cache: Rebuilding NVT cache
base gpgme:MESSAGE:2017-03-28 13h47.32 utc:151: Setting GnuPG dir to '/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2017-03-28 13h47.33 utc:151: Using OpenPGP engine version '2.1.11'
md   main:   INFO:2017-03-28 13h47.33 utc:151:    Updating NVT cache.
md   main:MESSAGE:2017-03-28 13h51.19 utc:244:    OpenVAS Manager version 7.0.0 (DB revision 184)
md manage:   INFO:2017-03-28 13h51.19 utc:244:    Getting users.

==> /var/log/openvas/openvassd.dump <==

==> /var/log/openvas/openvassd.messages <==
[Wed Feb 15 16:46:00 2017][837] openvassd 5.1.0 started
[Wed Feb 15 16:46:56 2017][1359] Client closed the communication
[Wed Feb 15 16:47:19 2017][837] Received the Terminated signal
[Tue Mar 28 13:47:30 2017][23] openvassd 5.1.0 started
[Tue Mar 28 13:48:17 2017][168] Client closed the communication

Hi @DannyLee12, thanks for the details. Are you sure you tried the correct address? It serves only on https: https://localhost and on whatever port you forward.

I think so, running the container:
CONTAINER ID        IMAGE                COMMAND               CREATED             STATUS              PORTS                            NAMES
fcc96d1b3567        mikesplain/openvas   "/bin/sh -c /start"   2 hours ago         Up 2 hours          <IP_ADDRESS>:443->443/tcp, 4000/tcp   openvas

And trying to connect on https://<IP_ADDRESS>/ or https://localhost tells me the site cannot be reached.
Does everything else seem ok?


Hosting the tools used compute Hacktoberfest participation statistics for Jenkins

Repository URL
https://github.com/jmMeessen/jenkins-hacktoberfest-stats
New Repository Name
jenkins-infra/jenkins-hacktoberfest-stats
Description
The purpose of this repository is to host tooling (and future automation thereof) used to produce participation statistics for Hacktoberfest in the scope of the Jenkins project.
GitHub users to have commit permission
@jmMeessen
@gounthar
@MarkEWaite
Jenkins project users to have release permission
N/A
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that the security team was notified about the request and will soon participate in this issue to assist.
The team is usually starting by a quick superficial audit and if it's not sufficient, they are planning a deeper audit.
Commands
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-required => the superficial audit was not sufficient, a deeper look is necessary :mag:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/audit-review => the findings from the audits were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message)

/audit-skip

Hosted at https://github.com/jenkins-infra/jenkins-hacktoberfest-stats


Keybindings frozen when edit any shortcut on 1.11.0 - insider

Insider commit: 32942fd950cf2ffe19c44f944170014704b4fd2c
Date: 3/22/2017
Os: Windows 10 64 bit

@pixieaka Thanks for reporting the issue. While doing this can you provide following information

Open development tools Developer: Toggle Developer tools from command prompt
Repeat the same steps and see if there are errors?
Also, open the keybindings.json file and repeat the same steps and let me know if the edits are proper

Thanks

@sandy081

@sandy081
The problem is solved ;)

Thanks @pixieaka for above videos. I got the issue.

Default value while creating keybindings.json should be an array
When there are errors while editing
-- Show the errors and make the editor available again

Fixed it.


Update slotmap on error in ToNode (sync API)

With this change, an iteration over the nodes with a ToNode command to each node can now include a slotmap update which restarts the iteration. I guess it can be a little inconvenient. Is there anything we can do about it? At the very least, it can be worth mentioning in the release notes, but maybe we can do something better?
Possibilities for the node iterator when slotmap changes:

Restart iterator when slotmap has been updated (current behaviour). The user may get the same node multiple times. It may be confusing and can cause some problem. Why was this behaviour chosen?
Abort iterator when slotmap has been updated. The user may think all nodes have been covered, which is also a problem. If the user needs to send a command to all nodes, this will not work well.
Make the iterator resistant to slotmap changes somehow. We may need to use something other than a dict, let's say init iterator can retrieve a list of addresses (the keys in the dict) and store them in a separate list in the iterator. On slotmap update, we can modify this list in a way that causes the least surprise to the user.

WDYT?

Restart iterator when slotmap has been updated (current behaviour). The user may get the same node multiple times. It may be confusing and can cause some problem. Why was this behaviour chosen?

@bjosv you added this, right?

Maybe we should add something about this new behaviour in the README?
We have some mentions about the redirection case, so this might be good to have some notes about to.
https://github.com/Nordix/hiredis-cluster/blob/4dc5564c4356551327f480ffca5318fe59a61c73/README.md?plain=1#L274-L277

Restart iterator when slotmap has been updated (current behaviour). The user may get the same node multiple times. It may be confusing and can cause some problem. Why was this behaviour chosen?

If I remember correctly the aim was to be able to cover and iterate all node at least once mainly for commands that couldn't be sent via the slot-based routing. That's why it was added at the same time as ToNode() commands.
The alternative then was to stop/abort when the slotmap had changed, but I guess there wasn't a good way to know if the iteration was finished or not. The user would also have needed to reinit the iterator to make sure all nodes was covered.
Maybe an API to check if the route_version was changed or not during iteration could have solved this, not sure if that was up..

Make the iterator resistant to slotmap changes somehow. We may need to use something other than a dict, let's say init iterator can retrieve a list of addresses (the keys in the dict) and store them in a separate list in the iterator. On slotmap update, we can modify this list in a way that causes the least surprise to the user.

I see in the PR that this was briefly discussed, but the simplistic way to be able to stack allocate, like a hiredis dict, was choosen.

OK, thanks, so shall we stick with the current solution then?
We have the event callback for updated slotmap now, which can also be used in addition to checking if iterator.route_version != cc->route_version as is done in the test case. Maybe I should mention this too in the README. I'll see what I can come up with.


PMC ID attributes should be linked directly to pubmed's version of the article

Completed and deployed!


LSP shows "LspDiagnosticsSign" in the wrong line in Neovim

Describe the bug
While using the Lua Sumneko Server with Neovim's built-in LSP, if an Error, Warning, Information or Hint diagnostic comes up on the very first word of the line, the diagnostic sign will appear one line above where the actual diagnostic is supposed to be.
I reported this as a Neovim issue but it got closed right away and was told to report here.
To Reproduce
Open a Lua file in Neovim using the built-in LSP (nvim-lspconfig as the plugin for the LSP configuration) and purposefully fire a diagnostic at the very start of the line with the first word or character.
Expected behavior
The diagnostic sign should appear in the correct line.
Screenshots

For a video please check the link below:
Issue Opened with Neovim
Environment (please complete the following information):

OS: ArchLinux 5.12.15-arch1-1
Client: neovim

I cannot reproduce this, please check if it has been fixed in latest version.

Yes, I just checked with the newest version and it works! Thank you!


simple elk example

@aledsage notice you will need logstash.bom, kibana and possibly elasticsearch.bom

Hi @andreaturli - unfortunately this example fails for me when deployed to AWS (with the logstash.elasticsearch.host config key name fixed).

TL;DR: the host IP needs to be in double quotes in the config file.
My config file (/etc/logstash/conf.d/01-basic.conf) says:
input { file { path => "/home/users/aled/brooklyn-managed-processes/apps/vQFu0YPI/entities/Tomcat8Server_Fzw0b9NL/logs/catalina.out" start_position => "beginning" } }  output { elasticsearch { host => <IP_ADDRESS> protocol => "http" embedded => false } }
The log file (/var/log/logstash/logstash.log) says:
{:timestamp=>"2016-02-17T22:55:07.156000+0000", :message=>"Error: Expected one of #, } at line 1, column 208 (byte 208) after output { elasticsearch { host => 54.170"}
{:timestamp=>"2016-02-17T22:55:07.172000+0000", :message=>"You may be interested in the '--configtest' flag which you can\nuse to validate logstash's configuration before you choose\nto restart a running system."}
The logstash process is not running. When I try running the commands below, it fails after a couple of minutes with the same error:
CONFIG_DIR=/etc/logstash/conf.d/
VERSION=1.5.4
nohup /opt/logstash/logstash-${VERSION}/bin/logstash agent -f ${CONFIG_DIR} -l /var/log/logstash/logstash.log &

When I put the ip address in double quotes and tried starting it again, then it worked.


feat: add skipLuhnValidation to JS/React sdk

Description

feat: add skipLuhnValidation to JS/React sdk

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


test/recipes/02-err_errstr: skip errors that may not be loaded on Windows

Fixes #8091

Ping?

Merged.
master:
6e68f244f48bd7118b9262ff5905da1c3b15cae9 test/recipes/02-err_errstr: skip errors that may not be loaded on Windows
1.1.1:
0e1b0e510dfe078b3fb2586d987d7b49ff8ef0b2 test/recipes/02-err_errstr: skip errors that may not be loaded on Windows


single style to structure block (start-workflow.md)

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Tests pass?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/18723

One style example here https://www.yiiframework.com/doc/guide/2.0/en/start-workflow#application-structure
I reviewed many options, this one is more suitable

Have you tried text or plaintext? Or sh maybe? And if all fails as well there should be js for shorter alias hopefully.

Have you tried text or plaintext? Or sh maybe? And if all fails as well there should be js for shorter alias hopefully.

Tried this is the best option
And there is no short name, for hljs I checked on the library website

Which library is that? @samdark which library is used to generate it on the guide page?

Which library is that? @samdark which library is used to generate it on the guide page?

@bizley
from this repo https://github.com/yiisoft-contrib/yiiframework.com

and in composer

I can see there shell, also there is js alias for javascript.

shell is similar to this https://www.yiiframework.com/doc/guide/2.0/fr/start-workflow, and if you don't mind, I'll replace js next time (not critical), thanks
Main display is the same on all pages

Thank you


Prevent losing unsaved environment variable data when attempting to change env

Description

Addressing https://github.com/usebruno/bruno/issues/1997
When modifying environment variables, changing environments without clicking the "Save" button loses the user's progress. This can be frustrating as there are no warnings beforehand.
With this pull request, I fixed this bug by detecting if any field in a variable in the current environment is changed, or if environment variables were added or deleted. If so, it gives a warning and prevents the user from switching, creating, and improving environments without either first saving or reverting their changes. Their changes will not be unexpectedly lost.
https://github.com/usebruno/bruno/assets/86133477/ceba5a4a-16a2-4377-81fe-2155cde9bcb2
Contribution Checklist:

[X] The pull request only addresses one issue or adds one feature.
[X] The pull request does not introduce any breaking changes
[X] I have added screenshots or gifs to help explain the change if applicable.
[X] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

@AngelaSYuan I would argue that might not be great UX. For exaple, what if you don't care about the change and decide to simply discard it? You now HAVE to save. You did not show if you could close the dialog and discard the changes that way.
There is already an existing dialog that IMO has better UX and gives the user a choice:

Can you implement that dialog?

@VictorioBerra Right, I just wanted to ask that actually. Is there a way I download the Golden Edition for free as a developer, or is that not possible?

@AngelaSYuan You can just pay the $19 to support the project lol its not like you wont use it. But I have no control over licensing, maybe @sanjai0py can get you a license key.

@VictorioBerra True haha, thanks! I'm going to work on implementing this dialog for the environment switch.

I just added the functionalities for the dialog box! The PR should be updated @VictorioBerra @sanjai0py
https://github.com/usebruno/bruno/assets/86133477/404881b4-d385-4c76-82d1-301549b457d7

@AngelaSYuan I like it, hopefully they approve. Slight nitpick but is there a way to make other dialogs not open after it? For example when you clicked "+ Create" it prompted you with the save dialog, and when you dismissed it (either with dont save, cancel or save) it immediately threw up the new environment dialog. Is there a way to make it not do that?
Like i said nitpick I dont think that should make or break this PR since this is a big life saver we did not have before.

@VictorioBerra Thanks! And got it, are you saying when I clicked on "+ Create", after I hit "Save", the "Create Environment" dialog popped up immediately after? I had intended that to be a feature haha, so that the user didn't need to click on "+ Create" again after clicking save on the warning dialog.
But I can definitely have the screen return to just showing the variables (no immediately following dialog), if that's what you mean? I can see how it might not be UX friendly in some cases.

@AngelaSYuan Yeah I think it can be jarring to be bombarded with dialogs. I think just return the user to where they were before they tried to leave without saving. Obviously if they click "Dont Save" I would expect the changes to be reverted.

Just fixed, so that we don't immediately switch environments/pop up the other dialog, whether we click "Don't Save" or "Save." Let me know if you have any other suggestions/if it might be able to be merged! @sanjai0py @VictorioBerra
https://github.com/usebruno/bruno/assets/86133477/feca6d2d-86b6-460a-8556-b347432e1ca7

@Its-treason Thank you! I just fixed the confirm warning modal to be centered using CreatePortal, and got rid of the isModified state. I also removed comments and unused imports. Let me know how it looks!

@sanjai0py @helloanoop Hi, just curious if my PR is merge-ready? If not, what other steps do I need to take?

Hi @AngelaSYuan !
Thanks for working on this. I am onboard with the UX updates done.
I am worried about the formik logic moved to 2 levels up in the component tree.
Ideally, we would want the formik stuff to stay inside the component that renders the form.
Was this intentional or did you have to move it because you were not able to the make the close dialog stuff work with the formik staying inside the  EnvironmentVariables component ?

Hi @helloanoop, thank you! I would say it was both intentional in terms of the design, but also so that I could pass down the appropriate variables for the close dialog functionality (which wasn't possible with formik being in the EnvironmentVariables component.
Would this change be alright? I believe everything should work the same since these components are rendered together, and moving the formik would enable us to access the needed variables!

Hi @helloanoop! I just wanted to check in and see if this modification would be alright? For context, my school assignment on getting a PR merged with Bruno is due this Thursday, so I wanted to see if it's still possible to merge before then. I really appreciate your time!

Hi @AngelaSYuan
We need to figure out how this can be made possible with formik being in the EnvironmentVariables component.
I understand that the react way of passing data down the component tree makes this pattern difficult to implement, but we need to figure out a way.
One way to implement this might be to dispatch an action whenever an environment gets edited and add a property called 'dirty' as true inside the environment.
You can then use the dirty flag check before switching the environment

@helloanoop Got it! I just made changes to the PR. Now, formik is back in EnvironmentVariables and I use a dirty flag to track if the field has been modified. How does this update look to you?

Hey @AngelaSYuan Nice work!
Merged.


Fix wrong reference that was causing #16336

node.Attr[idx].Val is not the same as attr.Val, the latter is an independent object that won't change anything in the document. This fixes #16336, the issue was introduced in #16118.

Disclaimer: I have no idea what issue the second change that I made might fix, or which new issues it might introduce.
The code was last updated in https://github.com/zeripath/gitea/commit/55c3e48638a75e5137dbc9021960c42e63efbd9c, and originally introduced in https://github.com/zeripath/gitea/commit/9de1eb081cd41a20a0e66e6fb37dd17a583d6bde. Maybe @zeripath knows if that was intentional?

I think https://github.com/go-gitea/gitea/pull/16340 just do it

@moqmar thanks for digging into and the pull. Since it's already fixed an CI on your pull fail. ill close it. Feel free to reopen if you think there is more to look at


can't place option order

Seem like it doesn't work. Can someone help me please?

wb.place_option_order(optionId=1015778901, lmtPrice=1, action='SELL', orderType='LMT', enforce='DAY', quant=1)
Traceback (most recent call last):
File "", line 1, in
File "C:\Python37\lib\site-packages\webull\webull.py", line 530, in place_option_order
raise Exception('place_option_order failed', response.status_code, response.reason)
Exception: ('place_option_order failed', 500, '')

very weird but i found the solution. Webull wants request params to exact order like this
{"lmtPrice":"1","auxPrice":null,"orderType":"LMT","timeInForce":"DAY","orders":[{"quantity":2,"action":"SELL","tickerId":1015778901,"tickerType":"OPTION"}],"serialId":"57a14473-6a9c-4fdf-8d05-b5ea09f603ca"}

It's working here without changing the order of parameters.  Just make sure you pass in strings.

wb.place_option_order(optionId='1015778901', lmtPrice='0.01', action='BUY', orderType='LMT', enforce='DAY', quant='1')
True


Typo finder

Think about a way to recognize typos.

I have found a simple algorithm called "levenshtein". It's also called the distance between 2 strings
https://en.wikipedia.org/wiki/Levenshtein_distance.

I'm not sure I get it. Where could you have a typo? When creating a flashcard?
Although finding the edit distance is a start, you could leverage something more powerful, but at the cost of complexity, like everything else.

The idea is to get a measure of how wrong the answer is when we play the guess games. This way, if the user misspells a word by a small margin, we will not say "COMPLETLY WRONG" because it's annoying for the user when he knows he's got it almost right. So to make the games feel more fair we can put a margin of mistake. This algorithm does just that, it counts how many mistakes someone did.


How to handle incorrect difference between Times with different Kinds?

Ran into this issue in Crystal 0.19.1:
it "- computes correct span across different kinds" do
  local_now = Time.now
  utc_now = Time.now.to_utc
  utc_now.should be_close(local_now, Time::Span.new(0, 0, 1))
end

I'd expect this test to pass. However, the difference between utc_now and local_now comes to 07:00:00.0000010 for me (I'm in PDT, currently UTC-7). As a result, this test fails:
1) Time - computes correct span across different kinds
     Failure/Error: utc_now.should be_close(local_now, Time::Span.new(0, 0, 1))

       expected 2016-09-14 15:26:23 UTC to be within 00:00:01 of 2016-09-14 08:26:23 -0700

     # ./spec/std/time/time_spec.cr:626

I'm happy to work on this and open a PR later this week, but have two questions:

Time::Kind only appears to have three options; how could I reliably write this test (specify a specific timezone) so people where UTC == local time can still run this test as intended?
Perhaps this is "expected" behavior? If so, would it make sense to introduce something like Time::AbsoluteSpan that will represent a span between two points in time regardless of timezone?

Hmm... so you expect local time vs. UTC time to be one hour apart in every place on the Earth?

No, my intent is that they represent the same point in time, so the delta should be minimal. Time.now should be the "same" point in time, even if I get a new Time instance in a different timezone.
I thought the three-int constructor was HMS — expect them to be within 1s. Might've read the API wrong though …

My original "real-world" use case:
it "fills in the created_at field with a recent timestamp" do
  now = Time.now
  user =<EMAIL_ADDRESS>"password")
  fetched_user = User.get(user.id.as(Int32))
  fetched_user.created_at.not_null!.should be_close(now, Time::Span.new(0, 0, 1))
end

Oh, I see. I think Time#- doesn't take into account the kind of the times, this is probably a bug. In any case, Time will most surely change, I don't like the current design and all the different kind times. This was inspired by C#/Mono, but their Time doesn't support nanoseconds and dealing with kinds is a mess. Probably each time should have a location/time-offset. So instead of fixing this it's probably better to redesign this at some point.
For now the best thing to do would be to always do operation on UTC times.

(though maybe this can be fixed easily so in the meantime it's still useful, I'll try)

@feifanzhou I think it's fixed now.
By the way, nice use of be_close, I never though of using it with times, only with floats :-)

@asterite you, sir, are unbelievably fast :)
Chose to use be_close because technically the two times aren't identical, so it felt a bit wrong saying the difference should "equal" 0


sanitize_shenvname returns string with [0-9a-zA-Z_] characters

In docker logs for my application I'm getting a lot of noise like this:
/etc/profile.d/container_environment.sh: line 10: export: `LIVE.APPLICATION.DEV_PORT_22_TCP_PROTO=tcp': not a valid identifier
/etc/profile.d/container_environment.sh: line 14: export: `LIVE.APPLICATION.DEV_PORT_443_TCP_ADDR=<IP_ADDRESS>': not a valid identifier
/etc/profile.d/container_environment.sh: line 24: export: `LIVE.UXPIN.DEV_ENV_MODE=compose': not a valid identifier

because it's auto-generated from docker-compose.yml configuration
app:
    links:
        - balancer:live.application.dev

What do you think about restricting characters in env variable name only to the following set [0-9a-zA-Z_]  ?

While changing the regex is debatable, moving the code like you did introduces a performance penalty, as the regex is compiled every time it's called.

@hyperknot you're right. I moved regex pattern back to constant.

Did you test it with your problematic examples?

@hyperknot yes, I tested problematic cases
Image with warnings:

Docker image with updated /etc/my_init
I added to my Dockerfile (with sed I replaced regex pattern)
RUN sed -i '/SHENV_NAME_WHITELIST_REGEX =/s/.*/SHENV_NAME_WHITELIST_REGEX = re.compile("\\W")/' /sbin/my_init

As you can see there are no warnings with exports:

@hyperknot did you have a chance to take a look at screenshots? :)

sorry for not replying earlier, it looks good but I'll have a proper look
in a few hours
On 2017. Jul 7., Fri at 13:32, Przemysław Dąbek<EMAIL_ADDRESS>wrote:

@hyperknot https://github.com/hyperknot did you have a chance to take a
look at screenshots? :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/pull/423#issuecomment-313657445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKjyOh19sSDu-lFYq1AIULmDC4kverks5sLhcxgaJpZM4ODkPV
.

@hyperknot sorry for bothering you. Any updates on that? :)

Ah, sorry for not checking it, I'll try to do it today.
On 2017. Jul 17., Mon at 22:01, Przemysław Dąbek<EMAIL_ADDRESS>wrote:

@hyperknot https://github.com/hyperknot sorry for bothering you. Any
updates on that? :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/pull/423#issuecomment-315865978,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj73cbaFz8by_pME2h2W6IxleZFOpks5sO72DgaJpZM4ODkPV
.

OK, just checked the reference about what characters are allowed in environment variables and found it in this SO answer: https://stackoverflow.com/a/2821183/518169

Environment variable names used by the utilities in the Shell and Utilities volume of IEEE Std 1003.1-2001 consist solely of uppercase letters, digits, and the '_' (underscore) from the characters defined in Portable Character Set and do not begin with a digit.

So \W is good enough for us, checking for the "do not begin with a digit" part would be overly pedantic.

Thanks :)


fix: Jump links styles and browser fixes

Related issues

#1521
#1343
#1258
#1162
#1028

What has changed and why

Add support to pfe-accordion-header for slotted content to be read in and rendered (this allows us to use pfe-accordion inside another template and pass a slot into the pfe-accordion-header)
Add PfeAccordion to pfe-jump-links-nav as a dependency
Add support for the following events:

pfe-jump-links-panel:active-navItem: when a new item in the nav becomes active, this event is fired for analytics; this is no longer handled by the panel but the event name persists for backwards compatibility
pfe-jump-links-panel:change: fired when the panel or section elements change; used by the autobuilder; calls _panelChangedHandler
pfe-jump-links-nav:stuck
resize: on page resize, the rebuild method is called
scroll: handles updating the active states when the page is scrolled
keyup: this is a stub and needs to be addressed at a later date (@TODO open issue for this)

Added the following attributes to pfe-jump-links-nav:

offset: the manually set distance from the top of the viewport to the top of the navigation element; this is an override and does not account for pfe-navigation when used.
mobile-breakpoint: max-width for when to switch to the pfe-accordion for mobile rendering
accordion-collapse-timing: how long to wait after clicking a child element before collapsing the open accordion
stuck: represents the stickiness state
no-header: boolean attribute to allow you to opt-out of rendering the header section (header becomes screen-reader only)

Added the following attributes to pfe-jump-links-panel:

spacers: opt-in attribute for injecting the spacer elements; not recommended but allows backward compatibility

Going forward, the only required component to add to the page is pfe-jump-links-nav.  Panel is an optional wrapper to make targeting more efficient.  All functionality is being handled inside the nav element.  Panel and sections can be manually defined via JavaScript API call to the pfe-jump-links-nav component.
Test cases

[x] Initialization

URL
Validate that on page load, the standard heading is selected in the top horizontal navigation and the Section 1 region is selected in the first visible vertical jump links.

[x] Stickiness

URL
On scroll, the horizontal and vertical elements should stick to the top of the viewport while it's content is visible; it should account for the height of pfe-navigation if it exists and any horizontal sticky elements
Edge case: If 2 horizontal sticky elements are present, the one later in the DOM will overlap the other one.

[x] Active state

URL
On scroll, the active state in the navigation should update when the section scrolls close to the top of the viewport.

[x] Click event

URL
On clicking a navigation item on either horizontal or vertical nav, the page should smooth scroll to that section so that the top of the section is visible close to the top of the viewport (accounting for sticky elements) with at least a 20px breathing space (unless offset is manually set in the mark-up)
No in-between sections should show as active while the scroll is happening
Scroll controlled active states should resume after the scrolling event is complete

Browser requirements
Your component should work in all of the following environments:

[x] Latest 2 versions of Edge
[x] Internet Explorer 11 (should be useable, not pixel perfect)
[x] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[x] Firefox 78 (or latest version for Red Hat Enterprise Linux distribution)
[x] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[x] Latest 2 versions of Safari
[x] Android mobile device (such as the Galaxy S9)
[ ] Apple mobile device (such as the iPhone X)
[ ] Apple tablet device (such as the iPhone Pro)

Ready-for-merge Checklist

[x] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[ ] Tests have been updated to cover these changes. @TODO to return to this after code freeze
[ ] Browser testing passed.
[x] Changelog updated.
[x] Documentation (README.md, WHY.md, etc.) updated or added.
[ ] Link to the demo recording:
[ ] Approved by designer.

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

branch testing looks good 👍


Single Setpoint Mode

Add support for retrieving the correct setpoints when in single setpoint mode and for other system Modes.  Add units tests.

@hufman - please give this a review - these methods are used from the integration to retrieve the current setpoint, i also have some changes there that I will create a pull request for - that may not happen until tomorrow.

Also note, some formatting changes.  HA uses Black as their formatting standard, hence I've adopted that also for the API and the Integration.  End-goal is to put the integration into HA.

If this is only meant to view the set point, this looks great. I'd separately recommend making a set of getCoolSP and getHeatSP accessor functions to match the setCoolSP/setHeatSP setters (and then the integration can compare those for equality to toggle the HA feature flag for split setpoints), instead of needing the integration to reach directly into the zone.csp/hsp variable, but that's not related to this change :)

Just created a pull request for the HA component for the Read Side for Single Setpoints as well as resolving the other issue.
https://github.com/PeteRager/lennoxs30/pull/66

If this is only meant to view the set point, this looks great. I'd separately recommend making a set of getCoolSP and getHeatSP accessor functions to match the setCoolSP/setHeatSP setters (and then the integration can compare those for equality to toggle the HA feature flag for split setpoints), instead of needing the integration to reach directly into the zone.csp/hsp variable, but that's not related to this change :)

Yeah, that's a good point.  I'll make that change.


Create a Parquet copy of the eCR datastore whenever the delta table is updated

Description
In order to make it easier for LAC county folks to begin working with data in the eCR data directly we should provide them the dataset in a Parquet format instead of just a Delta Table.
Acceptance Criteria
GIVEN the Synapse notebook for updating the eCR datastore
WHEN the notebook is run
THEN the eCR datastore Delta Table is refreshed and a copy is exported as a parquet file stored in Azure blob storage.

Based on feedback from LAC we are going to produce a parquet file instead of CSV.


Allow additional constructor options to be provided

Can the functionality of this plugin be extended to allow the additional documented options to be passed to the Sequelize constructor?
For example, it would be nice to set the timestamps option globally, instead of for each model, like the Sequelize documentation allows:
http://sequelize.readthedocs.org/en/latest/docs/getting-started/#application-wide-model-options
In addition to model settings, it would also be convenient to be allowed to pass all the other Sequelize constructor options such options.logging, options.replication, etc

Could we also get host added to the list of options?  Currently, (unless I'm missing it somewhere), hapi-sequelized only allows for the default localhost to be passed through the options.

@tribou @wallance thanks for the heads up guys. I'll have this added asap

haven't tested yet but that should do it ^. I will test it out and add new options to the readme later


Support EXECUTE/CREATE...WITH RECOMPILE for stored procedures

Description
T-SQL supports EXECUTE  WITH RECOMPILE and CREATE PROCEDURE ... WITH RECOMPILE.
For EXECUTE WITH RECOMPILE, an ad-hoc plan is generated for that particular execution.
For CREATE PROCEDURE WITH RECOMPILE, an ad-hoc plan is generated for every execution of the procedure, also when the EXECUTE statement does not specify WITH RECOMPILE.
In both cases, the ad-hoc generated plan is discarded immediately afterwards.
In Babelfish, forcing ad-hoc plan generation is implemented by setting the GUC "plan_cache_mode" to "force_custom_plan" for the particular procedure execution.
For CREATE PROCEDURE WITH RECOMPILE, and additional status bit is used in the babelfish_function_ext.flag_values catalog field.
Currently, recompilation will not apply to non-parametrized queries since PG will not generate a custom plan for such queries.
Engine PR: https://github.com/babelfish-for-postgresql/postgresql_modified_for_babelfish/pull/360
Signed-off-by: Rob Verschoor<EMAIL_ADDRESS>Issues Resolved
BABEL-346 Support WITH RECOMPILE for Transact-SQL stored procedures
Test Scenarios Covered

Use case based - Yes

Boundary conditions - N/A

Arbitrary inputs - N/A

Negative test cases - N/A

Minor version upgrade tests - N/A

Major version upgrade tests - N/A

Performance tests - N/A

Tooling impact - N/A

Client tests - N/A

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the PostgreSQL license, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

47 of 53 (88.68%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 72.906%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/catalog.c
16
18
88.89%

contrib/babelfishpg_tsql/src/pl_exec-2.c
9
13
69.23%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
41947

Relevant Lines:
57536

💛  - Coveralls


Error executing command "ng generate component product-alert"

Describe the bug
Message Error: An unhandled exception occurred: Cannot set property global of # which has only a getter
See "/tmp/ng-HB3xaS/angular-errors.log" for further details.
Log: ==> /tmp/ng-HB3xaS/angular-errors.log <==
at Script.runInContext (https://zydcpr--run.w.staticblitz.com/blitz.60eafec8d3c353b6b62cb733670ec59f842c88b1.js:6:336277)
at Script.runInNewContext (https://zydcpr--run.w.staticblitz.com/blitz.60eafec8d3c353b6b62cb733670ec59f842c88b1.js:6:336385)
at wrap (/home/projects/zydcpr--run/node_modules/@angular/cli/models/schematic-engine-host.js:170:35)
at SchematicEngineHost._resolveReferenceString (/home/projects/zydcpr--run/node_modules/@angular/cli/models/schematic-engine-host.js:61:40)
at SchematicEngineHost.createSchematicDescription (/home/projects/zydcpr--run/node_modules/@angular-devkit/schematics/tools/file-system-engine-host-base.js:181:34)
at SchematicEngine.createSchematic (/home/projects/zydcpr--run/node_modules/@angular-devkit/schematics/src/engine/engine.js:228:38)
at CollectionImpl.createSchematic (/home/projects/zydcpr--run/node_modules/@angular-devkit/schematics/src/engine/engine.js:80:29)
at GenerateCommand.getSchematic (/home/projects/zydcpr--run/node_modules/@angular/cli/models/schematic-command.js:150:27)
at GenerateCommand.initialize (/home/projects/zydcpr--run/node_modules/@angular/cli/models/schematic-command.js:63:36)
Link to the blitz that caused the error
https://stackblitz.com/run?file=src/app/app.component.ts
Steps to reproduce
ng generate component product-alert
Expected behavior
I hope to generate a component
Parity with Local

[ ] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 98.0.4758.102
Major version = 98
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 87888006,
  "usedJSHeapSize": 84567750,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 60eafec8d3c353b6b62cb733670ec59f842c88b1

Additional context
No response

Duplicate of #604


Move to individual modules

Move to individual modules.
This library is very large when included in other projects because we're pulling in so many of the AWS SDKs and mostly we don't need them all.
This splits out the libraries into individual modules. The classes have  mostly been moved around and each module has its own client class.
They are all released together. I've done it this way to save time and because most of the updates we get for this project are dependency updates to cats which affects all of the modules anyway.

I've re-written the README a bit as it was a bit vague so there's a bit of structure to it now. I've got rid of the Jenkinsfiles as well.


Watch mode doesn't support debug command

/kind feature

Which functionality do you think we should add?
odo watch should be able to use debug kind commands
so the '--debug' flag and 'debug-command' parameter should be added to the odo watch command
Why is this needed?
Currently when doing odo watch you can't specify the debug command to use. Specifying the command as run-command is not working so we don't have a workaround.

/priority high

/priority high

Currently if the component was pushed in debug mode, odo watch will also run in debug mode
[mrinaldas@localhost project]$ odo push --debug

Validation
 ✓  Validating the devfile [64989ns]

Creating Kubernetes resources for component nodejs
 ✓  Waiting for component to start [8ms]

Applying URL changes
 ✓  URLs are synced with the cluster, no changes are required.

Syncing to component nodejs
 ✓  Checking file changes for pushing [588158ns]

Executing devfile commands for component nodejs
 ✓  Executing install command "npm install" [2s]
 ✓  Executing debug command "npm run debug" [1s]

Pushing devfile component nodejs
 ✓  Changes successfully pushed to component

[mrinaldas@localhost project]$ odo watch
Component is running in debug mode
Please start port-forwarding in a different terminal
Waiting for something to change in /home/mrinaldas/project

Currently if the component was pushed in debug mode, odo watch will also run in debug mode
[mrinaldas@localhost project]$ odo push --debug

Validation
 ✓  Validating the devfile [64989ns]

Creating Kubernetes resources for component nodejs
 ✓  Waiting for component to start [8ms]

Applying URL changes
 ✓  URLs are synced with the cluster, no changes are required.

Syncing to component nodejs
 ✓  Checking file changes for pushing [588158ns]

Executing devfile commands for component nodejs
 ✓  Executing install command "npm install" [2s]
 ✓  Executing debug command "npm run debug" [1s]

Pushing devfile component nodejs
 ✓  Changes successfully pushed to component

[mrinaldas@localhost project]$ odo watch
Component is running in debug mode
Please start port-forwarding in a different terminal
Waiting for something to change in /home/mrinaldas/project

Currently if the component was pushed in debug mode, odo watch will also run in debug mode

what if you need to specify a custom debug command? like odo push --debug-command my-other-debug?

Currently if the component was pushed in debug mode, odo watch will also run in debug mode

what if you need to specify a custom debug command? like odo push --debug-command my-other-debug?

what if you need to specify a custom debug command? like odo push --debug-command my-other-debug?

We currently can push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

what if you need to specify a custom debug command? like odo push --debug-command my-other-debug?

We currently can push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

Here's a older discussion regarding the flag https://github.com/openshift/odo/issues/3480

Here's a older discussion regarding the flag https://github.com/openshift/odo/issues/3480

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

I see. But from the user's point of view, this is a little bit confusing.
If you want to change run or build command for odo watch you do odo watch --run-command --build-command.

Running odo push --run-command run2  --build-command build and then odo watch results in watch using the default run and build commands not the ones specified in odo push command.
We should create a unified experience. What we are doing with debug command makes sense (odo push defines how it is supposed to be run, for both odo push and odo watch.
This means that we will have to remove --run-command and --build-command from odo watch make sure that odo watch executes the same commands as prvious odo push  did.

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

I see. But from the user's point of view, this is a little bit confusing.
If you want to change run or build command for odo watch you do odo watch --run-command --build-command.

Running odo push --run-command run2  --build-command build and then odo watch results in watch using the default run and build commands not the ones specified in odo push command.
We should create a unified experience. What we are doing with debug command makes sense (odo push defines how it is supposed to be run, for both odo push and odo watch.
This means that we will have to remove --run-command and --build-command from odo watch make sure that odo watch executes the same commands as prvious odo push  did.

Above all, we need more documentation to avoid confusion. Let's not simply rely on odo push -h and/or odo watch -h. I'd go one step further and request a documentation based on how things are right now. As far as I can see, there's no doc explaining how to use --run-command and --build-command in the repo. Correct me if I'm wrong.

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

I see. But from the user's point of view, this is a bit confusing.

Can you point what's confusing? I'm asking because the same steps have been documented on odo website, and I'd like to ensure we capture what needs to be improved to eliminate confusion.

Above all, we need more documentation to avoid confusion. Let's not simply rely on odo push -h and/or odo watch -h. I'd go one step further and request a documentation based on how things are right now. As far as I can see, there's no doc explaining how to use --run-command and --build-command in the repo. Correct me if I'm wrong.

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

I see. But from the user's point of view, this is a bit confusing.

Can you point what's confusing? I'm asking because the same steps have been documented on odo website, and I'd like to ensure we capture what needs to be improved to eliminate confusion.

As a user, I got confused by the fact that you can provide 'run-command' and 'build-command' with 'watch' but not 'debug-command'. So I was wondering how to debug with 'watch' on. The steps to debug on the odo website were useful, but they don't cover the watch mode.

As a user, I got confused by the fact that you can provide 'run-command' and 'build-command' with 'watch' but not 'debug-command'. So I was wondering how to debug with 'watch' on. The steps to debug on the odo website were useful, but they don't cover the watch mode.

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

My bad, odo watch doesn't use the previous used debug command during odo push and thus we should add --debug-command to odo watch for a unified experience.
But according to the discussion https://github.com/openshift/odo/issues/3480 we decided against adding --debug flag to odo watch. Currently odo watch runs in debug mode if the component was pushed using odo push --debug.

We can currently push with a custom debug command odo push --debug-command my-other-debug and odo watch will use the given debug command.

My bad, odo watch doesn't use the previous used debug command during odo push and thus we should add --debug-command to odo watch for a unified experience.
But according to the discussion https://github.com/openshift/odo/issues/3480 we decided against adding --debug flag to odo watch. Currently odo watch runs in debug mode if the component was pushed using odo push --debug.

@ehsavoie can you PTAL if odo watch with debug support looks more clear than it did earlier? Also, if you face any issues/confusion while following the docs (CLI docs or those on odo.dev website), please open an issue to let us know.

I will take a look next week


mapping context properties

OK, let there be a  boolean isDefined(property) then? What about properties removal?
Assume you want to put there something for a while and then detach it. What would you do?

Did you consider putting ValueProperty or Listeners there?

I hope you'd like https://github.com/JetBrains/jetpad-mapper/pull/64


warn about deregistering services that don't exist

The Consul API will return a 404 for this kind of request, so I think it makes sense to issue a warning for it.

Where are you seeing it return 404?
[chris@chris-control-01 ~]$ curl localhost:8500/v1/agent/service/deregister/unknownservice
[chris@chris-control-01 ~]$

Oh, the catalog endpoint returns a 404. Never mind, that one makes more sense!


TrueRange Factor

rebased version of: https://github.com/quantopian/zipline/pull/1251
I just rebased the pr and added the default inputs to the docstring. Thanks for the factor @ChrisPappalardo

Coverage decreased (-0.02%) to 83.537% when pulling 25474cf475e438cae022dc1cf6b20e0a012e85a0 on pycon2016_cap into 2fe94d0c2964ef8f0913e9c64ddd1299224537a1 on master.

Coverage decreased (-0.02%) to 83.537% when pulling 25474cf475e438cae022dc1cf6b20e0a012e85a0 on pycon2016_cap into 2fe94d0c2964ef8f0913e9c64ddd1299224537a1 on master.

Coverage decreased (-0.02%) to 83.537% when pulling 25474cf475e438cae022dc1cf6b20e0a012e85a0 on pycon2016_cap into 2fe94d0c2964ef8f0913e9c64ddd1299224537a1 on master.


Optimize eager loading when no keys to be loaded

Currently when eager loading relations that don't have any keys to be loaded Laravel will still execute the query:
Example:
class User {
   public function picture()
   {
      return $this->belongsTo(Picture::class);
   }
}

User::create(['picture_id' => null]),
User::create(['picture_id' => null])
$users = User::all()->load(['picture']);

The eager load will trigger a select on the database even though there is no model keys to be loaded.
It does this by replacing replacing the empty where in (...) with where 0 = 1:
select * from `pictures` where 0 = 1

This PR checks to see if there are not any model keys that can be loaded, and if so will implicitly return an empty collection - this prevents the unnecessary database query.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@taylorotwell Please could you elaborate more on why this wasn't accepted? In our app we have hundreds of impossible where calls to mysql due to this. It's an optimization that removes unnecessary calls to the database...
Would you be willing to accept a PR that at least makes it easier to add this as a custom package?


Add Keptn to Ortelius ArgoCD Application set

This has been added in the ortelius-kubernetes repo but waiting for @bradmccoydev to finish pull request for issue:  https://github.com/keptn/keptn/issues/5066

PR here: https://github.com/keptn/keptn/pull/5293

pull request done to add ingress, now waiting for next release


Unresolvable PURL in go-plus.json

I just noticed that the latest version of go-plus.json (or at least the latest one that we downloaded & processed) contains this version tag:
"version" : "http://purl.obolibrary.org/obo/go/releases/2018-02-18/extensions/go-plus.owl"
If, however, you try to follow the link, you get the following 404:
An Exception Has Occurred
Unknown location: /ontology-releases/2018-02-18/extensions/go-plus.owl
HTTP Response Status
404 Not Found

@kltm Is this still a problem ?

The earliest release in the new pipeline looks to be 2018-03-06. I think this may eventually be addressed by https://github.com/geneontology/go-site/issues/483. It seems like we could close this ticket as covered by that one.


boot.loader.raspberryPi: Add configurationLimit.

Motivation for this change
Most raspberry pis (mine included), have a fixed size boot partition.
This partition will fill up if too many system generations exist. By
adding a option to set a limit, this can be mitigated by only allowing a
fixed number of generations to be copied.
Things done
Tested by adding
boot.loader.raspberryPi.configurationLimit = 1;

to a raspberrypi4b configuration built off of this branch of nixos.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hmmm - I think something subtle doesn't work here - dropping for now.


Add genetic algorithm written in Rust

Community Contribution
Link to live project, video, or image:

https://medium.com/@mithi/genetic-algorithms-in-rust-for-autonomous-agents-an-introduction-ac182de32aee
https://github.com/mithi/rusty-genes

Sharing

[x] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
https://www.instagram.com/minimithi/

Great!

https://www.githubstatus.com/incidents/2y6v4ltq26g7

Thanks! @gruselhaus let me know how to make the checks successful so I can update the pull request as needed. I've also allowed edits from maintainers. Thanks again!

Merging now. I made sure that the yaml is correct.

Thanks for merging @gruselhaus !


ProxylessNASNets

Could you provide me with the code of ProxylessNASNets?I want to search a specific net with respect to my own datasets.Thanks,my email is<EMAIL_ADDRESS>

@czczup


upgrade finagle-mysql from 6.41.0 to 6.43.0

finagle-mysql from 6.41.0 -> 6.43.0 support

https://finagle.github.io/blog/2017/03/14/release-notes-6-43/
Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[x] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

thank you @kenchan0130!


[TODO] Add Development and User documentation

This project could use some development documentation.
I would prefer using the included wiki page here then link to it on the README.md which might make the README.md a bit cleaner.
Theres plenty of information on how to create the wiki page on GitHub

Initial documentation created.
Issue closed by the initial work located in: https://github.com/gbowne1/TwitchBot/wiki


Update app version

App version updated to v1.3.1

Codecov Report

Merging #182 (91535ae) into master (12ad07a) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master     #182   +/-   ##
=========================================
  Coverage     67.02%   67.02%
  Complexity      688      688
=========================================
  Files           122      122
  Lines          2311     2311
  Branches        280      280
=========================================
  Hits           1549     1549
  Misses          636      636
  Partials        126      126

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...in/java/seedu/address/model/order/DateChecker.java
75.00% <0.00%> (ø)

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 12ad07a...91535ae. Read the comment docs.


feat: re-throw error in default serviceErrorHandler

This makes errors bubble up to await CommandFactory.run(...); like they should.
Example code utilizing new behavior:
import { CommandFactory } from 'nest-commander';
import { CommanderModule } from './commander.module';

async function bootstrap() {
  try {
    await CommandFactory.run(CommanderModule, ['verbose', 'debug', 'log', 'warn', 'error']);
  } catch (e) {
    process.exit(1);
  }
}

bootstrap();

@SystemDisc can you resolve the conflicts and add a changeset by following pnpm changeset? This should be a patch. With that, I'll get this merged and released


Not openning, mac

I recently downloaded breach from breach.cc for mac os x 10.6.0 and it is not openning.
or atleast taking a long time to open
Please either respond here or email me at:
<EMAIL_ADDRESS>

From the OS X console.
2015-01-27 9:18:35.811 AM Breach[1516]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
2015-01-27 9:18:35.908 AM ExoBrowser Helper[1518]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
2015-01-27 9:18:36.718 AM ExoBrowser Helper[1519]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
2015-01-27 9:18:36.969 AM com.apple.xpc.launchd[1]: (org.breach.Breach.321804[1516]) Service exited with abnormal code: 1

I've sorted this out. No probs


Adds JsonSchemaResource, with tests

What this PR does:
Adds resource for JSON schema, with tests
Which issue(s) this PR fixes:
Fixes #1723
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

The gRPC side wasn't setting the comment on CqlTable object, when there was a comment on the table: https://github.com/stargate/stargate/pull/1867/files#diff-05905c1e89fbc25c7061f96f8e16c292a3e9f1f3c02c746cec8d7fc7051bee8cR157 eek
But now everything is working!