Adding is intersecting check skips over initial load calls on full page infinite scroll

Not sure if this is still active, but by adding a check if the component is intersecting, stops the initial calls on render if the infinite scroll is a full page.

@SveNord This might be heavily specific to my issue with trying to utilize this for a school project. When I added this to a full page infinite scroll of postings, it pulled down the first 4 pages of content due to the component trigger being visible on initial render - so in order to fix that, I added
window.Observer = {
    observer: null,
    Initialize: function (component, observerTargetId) {
        this.observer = new IntersectionObserver(e => {
            // Check here
            if (e[0].isIntersecting) {
                component.invokeMethodAsync('OnIntersection');
            }
        });

        let element = document.getElementById(observerTargetId);
        if (element == null) throw new Error("The observable target was not found");
        this.observer.observe(element);
    }
};

Since this is a school project I did not test this outside my specific use case; but wanted to share!

window.Observer = {
observer: null,
Initialize: function (component, observerTargetId) {
this.observer = new IntersectionObserver(e => {
// Check here
if (e[0].isIntersecting) {
component.invokeMethodAsync('OnIntersection');
}
});
    let element = document.getElementById(observerTargetId);
    if (element == null) throw new Error("The observable target was not found");
    this.observer.observe(element);
}

};

Experienced the same issue. Your code fixed it, thanks


Codeunit 1550 "Record Restriction Mgt." - OnAllowRecordUsageOnBeforeDeleteRecords

Can you please add the OnAllowRecordUsageOnBeforeDeleteRecords event to AllowRecordUsage procedure in "Record Restriction Mgt." codeunit (1550)?
Actual Code:
procedure AllowRecordUsage(RecVar: Variant)
var
    RestrictedRecord: Record "Restricted Record";
    RecRef: RecordRef;
begin
    RecRef.GetTable(RecVar);
    if RecRef.IsTemporary then
        exit;
    if RestrictedRecord.IsEmpty() then
        exit;

    RestrictedRecord.SetRange("Record ID", RecRef.RecordId);
    RestrictedRecord.LockTable(true);
    RestrictedRecord.DeleteAll(true);
end;

Suggestion:
procedure AllowRecordUsage(RecVar: Variant)
var
    RestrictedRecord: Record "Restricted Record";
    RecRef: RecordRef;
begin
    RecRef.GetTable(RecVar);
    if RecRef.IsTemporary then
        exit;
    if RestrictedRecord.IsEmpty() then
        exit;

    OnAllowRecordUsageOnBeforeDeleteRecords(RestrictedRecord, RecRef)
    RestrictedRecord.SetRange("Record ID", RecRef.RecordId);
    RestrictedRecord.LockTable(true);
    RestrictedRecord.DeleteAll(true);
end;

[IntegrationEvent(false, false)]
local procedure OnAllowRecordUsageOnBeforeDeleteRecords (var RestrictedRecord: Record "Restricted Record"; RecRef: RecordRef)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52887.


[Bug] Kubelet executor fail to send SIGKILL to pid=1 process

Summary
In container, pid=1 process would not catch SIGKILL by default, so kubelet executor always has problem to stop workflow.
Diagnostics
What Kubernetes provider are you using?
Bare-metal v1.13.12
What version of Argo Workflows are you running?
v2.11.3
You could create the workflow below and try to stop it.
Paste a workflow that reproduces the bug, including status:

> kubectl get wf workflow-58bd2f40bf694a7d964e9d72a8f9e66a -n workflow-test -o yaml

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  creationTimestamp: "2020-10-15T13:50:32Z"
  generation: 5
  labels:
    bucket-id: "23"
    capos_id: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
    workflows.argoproj.io/phase: Running
    workload: argo-workflow
  name: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
  namespace: workflow-test
  resourceVersion: "50440562"
  selfLink: /apis/argoproj.io/v1alpha1/namespaces/workflow-test/workflows/workflow-58bd2f40bf694a7d964e9d72a8f9e66a
  uid: 649ee5aa-0eed-11eb-b36d-02623cf324c8
spec:
  arguments: {}
  entrypoint: main
  serviceAccountName: workflow
  templates:
  - arguments: {}
    container:
      command:
      - /bin/sh
      - -c
      - sleep 86400
      env:
      - name: CAPOS_ID
        value: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
      - name: NAMESPACE
        value: workflow-test
      image: docker.io/zcy19941015/pytest:v0.2
      name: main
      resources: {}
    inputs: {}
    metadata:
      annotations:
        cluster-autoscaler.kubernetes.io/safe-to-evict: "false"
        instance-name: las-mesos-agent-s083_511d4d23655f418e824b443ae368fae5
      labels:
        bucket-id: "23"
        capos_id: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
        pod-relates-workflow: "true"
    name: main
    outputs: {}
  ttlStrategy:
    secondsAfterFailure: 604800
    secondsAfterSuccess: 86400
status:
  finishedAt: null
  nodes:
    workflow-58bd2f40bf694a7d964e9d72a8f9e66a:
      displayName: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
      finishedAt: null
      hostNodeName: ip-10-49-147-150.us-west-2.compute.internal
      id: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
      name: workflow-58bd2f40bf694a7d964e9d72a8f9e66a
      phase: Running
      startedAt: "2020-10-15T13:50:32Z"
      templateName: main
      templateScope: local/workflow-58bd2f40bf694a7d964e9d72a8f9e66a
      type: Pod
  phase: Running
  startedAt: "2020-10-15T13:50:32Z"

Paste the logs from the kubelet executor:
> kubectl logs workflow-58bd2f40bf694a7d964e9d72a8f9e66a wait -n workflow-test

time="2020-10-15T13:50:33.812Z" level=info msg="Starting annotations monitor"
time="2020-10-15T13:50:33.815Z" level=info msg="Starting to wait completion of containerID 699fa6e92cddf16bee6edf39cd07bd4a7ee2be4c2b815c7069b939967b379693 ..."
time="2020-10-15T13:50:33.815Z" level=info msg="Starting deadline monitor"
time="2020-10-15T13:53:40.319Z" level=info msg="Received update signal. Reloading annotations from API"
time="2020-10-15T13:53:40.845Z" level=info msg="Execution control set from API: {0001-01-01 00:00:00 +0000 UTC false}"
time="2020-10-15T13:53:41.380Z" level=info msg="Received update signal. Reloading annotations from API"
time="2020-10-15T13:53:41.838Z" level=info msg=terminated
time="2020-10-15T13:53:41.841Z" level=info msg="Execution control set from API: {0001-01-01 00:00:00 +0000 UTC false}"
time="2020-10-15T13:53:41.844Z" level=info msg="Killing main container"
time="2020-10-15T13:53:41.844Z" level=info msg="SIGTERM containerID \"699fa6e92cddf16bee6edf39cd07bd4a7ee2be4c2b815c7069b939967b379693\": terminated"
time="2020-10-15T13:53:41.858Z" level=info msg="Starting to wait completion of containerID 699fa6e92cddf16bee6edf39cd07bd4a7ee2be4c2b815c7069b939967b379693 ..."
time="2020-10-15T13:53:42.971Z" level=info msg="Received update signal. Reloading annotations from API"
time="2020-10-15T13:54:11.869Z" level=info msg="SIGKILL containerID \"699fa6e92cddf16bee6edf39cd07bd4a7ee2be4c2b815c7069b939967b379693\": killed"
time="2020-10-15T13:54:11.883Z" level=info msg="Starting to wait completion of containerID 699fa6e92cddf16bee6edf39cd07bd4a7ee2be4c2b815c7069b939967b379693 ..."
time="2020-10-15T13:54:41.894Z" level=warning msg="Failed to kill main container: timeout after 30s"

From https://man7.org/linux/man-pages/man2/kill.2.html
       The only signals that can be sent to process ID 1, the init process,
       are those for which init has explicitly installed signal handlers.
       This is done to assure the system is not brought down accidentally.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

BTW, it seems the bug could also happen in Kubernetes API (k8sapi) executor, since k8sapi executor also use pod.exec kill -9 1

Let me see if I understand - we cannot kill the process because SIGKILL cannot be handled by PID 1.
Could we do this?
https://stackoverflow.com/questions/46123457/restart-container-within-pod

Let me see if I understand - we cannot kill the process because SIGKILL cannot be handled by PID 1.
Could we do this?
https://stackoverflow.com/questions/46123457/restart-container-within-pod

Hi @alexec , according to my test:

docker kill worked for me. Since dockerd is running in host pid namespace, and in that namespace, the container init process doesn't have signal protection. That's why docker executor doesn't have such bug.
/sbin/killall5 worked for me too, but I don't think it's the right way, since some containers may not have /sbin/killall5.
pns executor worked for me too. Since container init process is not pid=1 in that case, so it doesn't have signal protection.

So it seems hard to kill a container only with kubelet api / pod exec. Hope your team and other contributors could have some discussion about this issue!
My pid tree inside container:
# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 00:42 ?        00:00:00 /bin/sh -c sleep 86400
root        11     1  0 00:42 ?        00:00:00 sleep 86400
root        12     0  0 00:43 pts/0    00:00:00 /bin/sh
root        17    12  0 00:43 pts/0    00:00:00 ps -ef

A process running as PID 1 inside a container is treated specially by Linux: it ignores any signal with the default action. As a result, the process will not terminate on SIGINT or SIGTERM unless it is coded to do so.

https://docs.docker.com/engine/reference/run/#foreground

According to my investigation, stop main container by killing the pid=1 process could have some edge cases, for example:

The docker image is based on scratch so it doesn't support kill command.
The init process of container ignores SIGTERM.

So I believe the best solution of this issue is to implement a cri executor. I'll create a proposal about that.


 Conceive and design the Skill Tree

Description
Skill trees will be used throughout the game to give players a variety of different skill upgrades. This can include movement, attack, utility. Players can gain skill points by leveling up to unlock new skills. Different characters have different unique skills that can bring different gameplay experiences to the player.
Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.

[x] Put forward the idea (Sep. 4)
[x] Began to draw (Sep. 6)
[ ] User testing (Aug. 8)
[ ] To complete the work (Aug. 10)

Members

YongzhiZHOU(@45229848 ) (YONGZHI ZHOU)

finish step 1

finished

finished

fin


🛡 Eliminate static token for promtail

How to categorize this PR?

/area security
/kind enhancement
/merge squash
What this PR does / why we need it:
Similar to #5121, this PR eliminates the static token for the promtail in favor of a token managed by the TokenRequestor controller in gardener-resource-manager.
The basic idea is similar to what cloud-config-downloader does: The shoot access token maintained in the kube-system namespace of the shoot cluster is regularly downloaded and stored on the disk. In order to download it, the cloud-config-downloader's token is used for communication with the API server.
Which issue(s) this PR fixes:
Part of #4661
Part of #4878
Special notes for your reviewer:
/invite @vlvasilev @BeckerMax

✅ ~Based on #5121 which needs to be merged (hence, PR is in "draft" state and verify step is failing)~

Release note:

`promtail` does no longer use a static token but an auto-rotated `ServiceAccount` token which is only valid for `12h`.

This PR is now
/ready
/invite @danielfoehrKn

/assign

This PR still needs to be reviewed.
/unassign @BeckerMax since he's not available

/assign


Correctly account for remaining target elements while unlocking scrolling

Fixes https://github.com/willmcpo/body-scroll-lock/issues/64

is anything blocking this?

Hi @LarsDenBakker - are you able to pull master and resolve conflicts?
Otherwise, your fix looks good, thanks.

@willmcpo I've resolved the conflicts. I noticed you gave me merge rights, should I go ahead and merge this?

Nice thanks heaps. I'll publish a beta version first before pushing a new minor update.

@LarsDenBakker published<EMAIL_ADDRESS>- if you have no issues with it, I'll aim to publish before the end of the week

Thanks! I've been using my branch without issues for a while.


Got errors on fresh npm install

Failed to compile.
Error in ./src/connected-intl-provider.jsx
Module not found: ./../translations/app-translations.json in /Users/Apple/RAILS_PROJECTS/spree-on-react/src
@ ./src/connected-intl-provider.jsx 11:23-73
After running npm run build:langs got following errors
<EMAIL_ADDRESS>build:langs /Users/Apple/RAILS_PROJECTS/spree-on-react

babel-node scripts/translate.js

/Users/Apple/RAILS_PROJECTS/spree-on-react/node_modules/babel-register/node_modules/babel-core/lib/transformation/file/options/option-manager.js:328
throw e;
^
Error: Using babel-preset-react-app requires that you specify NODE_ENV or BABEL_ENV environment variables. Valid values are "development", "test", and "production". Instead, received: undefined. (While processing preset: "/Users/Apple/RAILS_PROJECTS/spree-on-react/node_modules/babel-preset-react-app/index.js")
at Object. (/Users/Apple/RAILS_PROJECTS/spree-on-react/node_modules/babel-preset-react-app/index.js:49:9)
at Module._compile (module.js:571:32)
at Module._extensions..js (module.js:580:10)
at Object.require.extensions.(anonymous function) [as .js] (/Users/Apple/RAILS_PROJECTS/spree-on-react/node_modules/babel-register/lib/node.js:152:7)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at /Users/Apple/RAILS_PROJECTS/spree-on-react/node_modules/babel-register/node_modules/babel-core/lib/transformation/file/options/option-manager.js:296:17
npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build:langs"
npm ERR! node v7.3.0
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build:langs: babel-node scripts/translate.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build:langs script 'babel-node scripts/translate.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the spree-on-react package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node scripts/translate.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs spree-on-react
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls spree-on-react
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Apple/RAILS_PROJECTS/spree-on-react/npm-debug.log

I think I managed to resolve the same issue inside Ubuntu 16.04.2 Virtual Image (VBox).
I just did 1. "export NODE_ENV=development" in BASH and 2. "npm run build:langs".
After these steps FE is running ok in Development mode. Didn't test it in Production. Hope it'll work.
PS: @OmSolution MANY THANKS FOR "build:langs"

@OmSolution I somehow got unsubscribed from the notifications from this repo, causing the delay in reply. Thanks for reporting the issue. I was able to replicate the issue. I have updated the Readme. Thanks @homoluden for the suggestion.


openhantek6022: 3.3.1 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/OpenHantek/OpenHantek6022/releases.
meta.description for openhantek6022 is: Free software for Hantek and compatible (Voltcraft/Darkwire/Protek/Acetech) USB digital signal oscilloscopes
meta.homepage for openhantek6022 is: https://github.com/OpenHantek/OpenHantek6022
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/w9yyh5rq5ch62hbi8h7z3p82ichyljrs-openhantek6022-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/w9yyh5rq5ch62hbi8h7z3p82ichyljrs-openhantek6022-<IP_ADDRESS>

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
openhantek6022

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w9yyh5rq5ch62hbi8h7z3p82ichyljrs-openhantek6022-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A openhantek6022 https://github.com/r-ryantm/nixpkgs/archive/56ab60896aa96001c0ca21ce27e02e08d485cf58.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/w9yyh5rq5ch62hbi8h7z3p82ichyljrs-openhantek6022-<IP_ADDRESS>
ls -la /nix/store/w9yyh5rq5ch62hbi8h7z3p82ichyljrs-openhantek6022-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

openhantek6022

Maintainer pings
cc @baracoder for testing.

@ofborg build openhantek6022 openhantek6022.passthru.tests


[Bug]: users cannot escape from binding mode if binding fails

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
When I am working with a query, there is a nice flow to directly bind a widget to a query response by clicking the "Connect Widget --> Select Widget" button.
However, in case the binding fails, it looks like there is no way for the user to abort the operation, other than to click away in the entity explorer
Uploading Screen Recording 2021-12-04 at 9.04.56 PM.mov…
.
Why should this be worked on?
not super important, but it takes care of one branch of the flow.

Hey @rohan-arthur  I was testing this out, and it seems that you can hit escape to leave binding mode. Do you feel that this solves the issue?

Stats

Stat
Values

Reach
40

Effort (months)
0.5


Zip file not contain source code

Zip file from this link not have src directory inside the zip. it only has README.md and LICENSE files

yep

new release out


Restart Video List Update when switched back to online

The Video download progress of a downloading video was not getting displayed when user switched from Online -> Offline -> Online mode on Video Listing. This has been fixed.
Please review - @aleffert @rohan-dhamal-clarice
JIRA: https://openedx.atlassian.net/browse/MOB-1564

:+1:


fbp-generator: write to a file only if the generation suceed

Before this patch, we were appending to the file piece by piece,
at the risk of generating the file by half if the generation fails
at some part.
Now we're creating an unnamed temporary file and when the generation
ends, we link this unnamed temporary file to a filepath that the
user provide us.
Signed-off-by: Ricardo de Almeida Gonzaga<EMAIL_ADDRESS>

Thanks for the comments, I'll send a v2!


Interface panels are not getting refreshed after selecting value from interface dropdown variable.

Describe the bug
Interface panels are not getting refreshed after selecting value from interface dropdown variable.
Expected behavior
if I am selecting one value from the interface dropdown. w.r.t panel should get refreshed and show the selected value metrixs. But current its showing all devices metrixs
Screenshots

Network data
Raw data :
Request :
POST /api/ds/query HTTP/1.1
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Content-Length: 1012
Cookie: _ga=GA1.2.613469710.1691601670; ajs_anonymous_id=f872fab0-97cf-461b-8af7-3937f6e27a85; grafana_session=XXXXXXX; grafana_session_expiry=1697210494
Host: XXXXXXX
Origin: XXXXXXX
Referer: https://XXXXXXXX/d/ade4846b-687c-4189-95f4-569c46de1003333/testing-firewall?orgId=1&var-Group=XXXXX (Ashburn) [t]&var-Host=ABS%23CNFASH&var-Interface=Interface x2
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
accept: application/json, text/plain, /
content-type: application/json
sec-ch-ua: "Chromium";v="118", "Google Chrome";v="118", "Not=A?Brand";v="99"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
x-grafana-org-id: 1
Response :
HTTP/1.1 200 OK
Cache-Control: no-store
Content-Type: application/json
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Fri, 13 Oct 2023 15:26:54 GMT
Transfer-Encoding: chunked
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

10.0.1
5.4.10
4.4.1

The issue is resolved, reconfiguring the interface variable.


Service deleted some QueryString on the url

For example, if you store this url by API
https://www.arvandkala.org/پرداخت/order-pay/326089/?pay_for_order=true&key=wc_order_18Sbh4A18GUvJ
The query string "&key=wc_order_18Sbh4A18GUvJ" is removed by service and converted to:
https://www.arvandkala.org/پرداخت/order-pay/326089/?pay_for_order=true
And here is the example created with yours api service:
http://arvd.link/o

As stated in the doc, you need to properly escape the URL when using the API


No support for testing multiple Python versions on OS X in Travis continuous integration

Currently, there is no official Python support for OS X on Travis.  For full details, see the GitHub issue #2312.
There are hacks to run multiple Python versions on OS X in Travis continuous integration.  For example, one can use utilities here.  But it makes the build more complicated.
For simplicity, we get around the lack of Python official support by using Homebrew to install the latest Python 3 in a virtualenv as described here.  This only works for a single version of Python.
If there is time later, we might try supporting multiple Python versions.

We can also test the latest Python 2 on OS X in Travis.  So that covers both the latest versions of Python 2 (v2.7) and Python 3 (v3.6), though not the earlier versions of Python 3.  (For Linux, we also test Python 3.4 and 3.5)

Unless something breaks and we need to use an older version of Python, we probably don't need to test on older versions.  Testing on the latest Python 2 and Python 3 should be sufficient.  As of now, we won't work on this issue further.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-31-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4823

Questions ?
Please refer to the Backport tool documentation


Generate new Client certificate pair for each certificate source

In #46 we introduced certificates generation, but we're writing same client certificate to all Secrets provided in the EtcdStorage resource Spec.
This PR changes the behavior, so new client certificate pair is generated for each Secret provided in the EtcdStorage Spec.

minor comments, but they should be fixed.  lgtm otherwise.


Homepage search improve

Improved design of Search section, in agreement with @emelysalmeron 🙂
Yet I didn't position the dropdown-menu (they are dropped down to the left while should be to the right). Maybe it's up for js to fix 🤔
PS. it's NOT responsive! 😄

@katsmamina here is an example how to format the code so it works the way you describe.. https://getbootstrap.com/docs/4.0/components/dropdowns/#single-button-dropdowns

@danielhalasz I changed the code and removed extra buttons. It looks more neat now. Take a look please :)

nice 🎉

Looks good


fix: update node within Dockerfile

Node.js will release a security patch today (27tn Nov)
This PR will update the Docker image base to the latest version available.
⚠  https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/

https://nodejs.org/en/download/ node 10.0.14 was released, but the alpine node tag is not yet available, waiting for it for next release.


issue #237 spin fix.

This PR addresses GitHub issue: #237
Briefly describe the changes proposed in this PR:

Fixed spin bug

Make sure you've followed the Contributor Guidelines. In particular (please tick to indicate you've taken care of it):

[x] RDF4J code formatting has been applied
[x] tests are included
[x] all tests succeed

Signed-off-by: Mark Hale<EMAIL_ADDRESS>

Can anyone help with the conflicts, I don't understand what the problem is.

BTW, is there any reason why travis is not being used?

@pulquero I'm not sure why you ask about Travis. We have a Hudson CI in place at https://hudson.eclipse.org/rdf4j/ - I thought you knew?

All fixed, my remotes werent setup properly.
Travis can build pull requests which isnt the same thing.

I'm not really familiar with Travis but if you feel it would be useful, flick an e-mail to rdf4j-dev so we can discuss it.

Anyway, approved, merging.


Add macros to construct libcnb-data newtypes from literal strings

Problem Statement
With the use of newtypes to enforce correct values for CNB defined types also comes a drawback: we no longer cannot use string literals in places where the a literal value is needed. This forces the user to put .unwrap calls in these cases:
let process = Process::new(
    "web".parse().unwrap(),
    "bundle",
    vec!["exec", "ruby", "app.rb"],
    false,
    true,
);

Currently, this is not too bad as we only have this case with ProcessType really, usually once per buildpack if at all. But as soon as we implement #101, we will have this for every layer. I still think having newtypes for these scenarios is great but we need a solution for literal values and this is where this PR comes in.
Solution
This PR extends the libcnb_newtype! macro introduced in #162 so that it generates another macro for every newtype that allows us to create literal newtype values that are checked at compile time! The previous example becomes:
let process = Process::new(
    process_type!("web"),
    "bundle",
    vec!["exec", "ruby", "app.rb"],
    false,
    true,
);

Should the string not be a valid ProcessType, the buildpack will not compile:
Compiling example-02-ruby-sample v0.1.0 (/Users/manuel.fuchs/projects/libcnb.rs/libcnb/examples/example-02-ruby-sample)
error: "wörker" is not a valid ProcessType value!
  --> libcnb/examples/example-02-ruby-sample/src/main.rs:56:25
   |
56 |                         process_type!("wörker"),
   |                         ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `process_type` (in Nightly builds, run with -Z macro-backtrace for more info)

Since these are regular compile errors, the error nicely propagates into IDEs out of the box:

Implementation Notes
Regex
The implementation is very generic since we can validate all our newtype values via regular expressions. This allows us to compile the regular expression at compile time and use it against the literal string passed to the macro. As soon as we need to use arbitrary Rust code to validate these, the current approach with automatically generated macros is no longer feasible, unless we write a Rust interpreter or use a scripting language for the validation logic.
To extend the cases where regular expressions can be used, I replaced the regex crate with fancy_regex to allow for look-around expression which cannot be implemented in a NFA regex implementation. This means our regular expressions are no longer guaranteed to run in linear time. I think this is a fine trade-off for us, since we're only using it with very simple expressions that are entirely controlled by us and only used in a very limited use-case.
See: Catastrophic Backtracking
Removal of extra predicates
See above, we cannot use arbitrary Rust code to do the validation at compile time since we would have no way to execute it. We can implement allow- and blocklists via regex just fine and don't need extra predicates at this point.
New crate: libcnb-proc-macros
This feature can only be implemented via procedural macros. By design, procedural macros cannot be used in the crate they're defined it and need a special crate type. Therefore, we have a new crate for the proc macro required by this PR and potential future ones.
Testing Strategy
Testing code that, by design, should not compile is hard. Rust currently provides no way to test non-compiling code in unit tests. This limits the tests to only test the positive cases. I would like to test the negative code path as well. There is compiletest-rs which seems overkill in our-case.
To keep things simpler, I'd fine to not test the negative path for now. Note that the string will still be validated at runtime as well, the worst-case scenario would be that code with an illegal newtype value compiles, but fails at runtime as if these macros would not exist. I'm happy to be convinced otherwise. :)

Thank you for doing this! I much prefer the idea of compile time validation :-)


How to do tiling as a consumer

We discussed tiling today at the Hackathon (related to #13).
It would probably make sense to have similar strategies in Python and Java.
Which input can be tiled?

an input can be tiled if there is a dimension with step > 0

How to run the model on a subset of an input?

output node halo describes the margin around a tile
a subset has to have size min + n*step
a subset has to be at position ? (we discussed that there might be a limitation here that is not clear how it is defined yet)

If it helps, in DeepImageJ we thought about facing it as follows:

If the task is image classification, then there is no tiling (this could be extended to not image to image network)
else we always do the tiling of the entire image by calculating the optimal value of n that covers the entire image, taking into account the halo and the min + n*step condition.

Closed in favor of #227


Captcha: Could not load the image.

What steps will reproduce the problem?
Controller
class SiteController extends Controller
{
    ...
    public function actions()
    {
        return [
            'error' => [
                'class' => 'yii\web\ErrorAction',
            ],
            'captcha' => [
                'class' => 'yii\captcha\CaptchaAction',
                'fixedVerifyCode' => YII_ENV_TEST ? 'testme' : null,
            ],
        ];
    }
    ...
}

Model
class SignupForm extends Model
{
    public $username;
    public $email;
    public $password;
    public $captcha;

    /**
     * @inheritdoc
     */
    public function rules()
    {
        return [
        ...
            ['captcha', 'captcha']
        ...
        ];
    }
}

View
<?= $form->field($model, 'captcha')->widget(\yii\captcha\Captcha::classname(), [
    // configure additional widget properties here
]) ?>

What is the expected result?
Load the image.
What do you get instead?
In my program, Captcha can be displayed properly on some computers, but there are some computers can not be loaded properly, and the browser will appear "Could not load the image".

The same computer, download and install "Yii 2 Basic Application Template"  can be displayed, but not in my program.
Additional info
I searched the Internet. If  the output buffer is not empty, you can not load the image.The solution is to empty the output buffer before output captcha.
For example, in [[\yii\captcha\CaptchaAction::run()]]
        } else {
            ob_clean();  //Add this line, can solve this problem. Or add in other suitable places
            $this->setHttpHeaders();
            Yii::$app->response->format = Response::FORMAT_RAW;
            return $this->renderImage($this->getVerifyCode());
        }

Q
A

Yii version
2.0.x

PHP version
7.0.4-7ubuntu2.1

Operating system
ubuntu 16.04

Is it a bug?

Do you know how to reproduce the issue?

On those machine that you can't load the image, please check if the user that is runnig the php have the right permission on the directory sessions.save_path or try to save the session on database

some times may be due to "enableStrictParsing" is set to true and you don't have any url rule for captcha

I see no way to reproduce it so we can't fix it. Closing.

I had same issue and ob_clean() solved it.

I had same issue and ob_clean() solved it. Thanks @shi-yang.

@shannlove any idea how to reproduce it?

Very good @shi-yang, its working for me.
i was tired but now relax.
thank you again.

@samatic  @nageennayak11
Where did you put ob_clean() to solve the problem?

@daliha look at @shi-yang comment above

@nageennayak11 Thank you

It was working for a long time to me, but suddenly it let to work, and the solution given here is not working in my case.
I set ob_clean() in CaptchaAction and not worked.
It happened just after run composer update.
I run both in my own PC and in AWS Elastic Beanstalk. In both was working, but just today it failed.

Super weird, but I faced the same issue on one of my servers on PHP 7.1. Adding ob_clean() to the CaptchaAction class solved the issue. Yii version is 2.0.14. Checked all the permissions for sessions. PHP-FPM can write session files. No errors and warnings in the logs too.

@samdark the issue can be reproduce by follwing step:

run composer create-project --prefer-dist --stability=dev yiisoft/yii2-app-basic basic to install yii2-app-basic project.

add a blank line on config/db.php as below:

<?php
return [
    'class' => 'yii\db\Connection',
    'dsn' => 'mysql:host=localhost;dbname=test',
    'username' => 'root',
    'password' => '123456',
    'charset' => 'utf8'
];

Note: There is a blank line at the beginning of the file

Access the application through the following URL:

http://localhost/basic/web/index.php?r=site/contact

Well, that is expected. PHP files should never start with blank lines or BOM else you'll have broken HTTP headers and unexpected input.

I had same issue  but I set ob_clean() in CaptchaAction and not worked.
because i don't have permission to write  session file

I had same issue and ob_clean() solved it. Thanks @shi-yang.

I just extended the class and add ob_clean() works fine


Never loads....

Used your hyperlink and no luck.  Blank window and nothing came up on the developer console.  Downloaded the zip and opened index.htm in FireFox.  What is required to get his to run?

Open the dev logs and check the network status. That will let you know if it's still downloading. A lot of the content cannot be included in this project because of copyright reasons.

The website load is too heavy for web server to handle now, and this game is not playable because audio and images are deleted from project, cannot upload those stuff to github.
You can contact me in private via email or something else

I see.  Yeah, I didn't see that part about downloading.  Thought that the link would take me to a playable version.  OK, if I can find that download I will give it another try this weekend.  Thanks in advance, really looking forward to playing this.  I love home made games!!!  We need to see more game projects!


[zh] text optimization: automated-tasks-with-cron-jobs.md

Optimized some text and added title tags:
The source path is: content/en/docs/tasks/job/automated-tasks-with-cron-jobs
The preview link is: https://deploy-preview-34467--kubernetes-io-main-staging.netlify.app/zh-cn/docs/tasks/job/automated-tasks-with-cron-jobs/

@howieyuen my god, you caused so many PRs need rebase, I hate you..... What can I do ....

/label tide/merge-method-squash

@howieyuen my god, you caused so many PRs need rebase, I hate you..... What can I do ....

The huge effort of changing 'zh' to 'zh-cn' has to be done some day. Conflicts with existing PRs seem inevitable to me. Please understand that such churns don't happen everyday.

@howieyuen my god, you caused so many PRs need rebase, I hate you..... What can I do ....

sorry...my friend, please understand conflicts are absolutely not my original intention.

lol, take it easy, guys and masters, all are solved :)


allow predicate_mlp_classifier_max_itr to depend on the dataset size

we need this for the interactive learning approach. it will be good if we can implement this in a way that suggests a general pattern, in case we want to vary other hyperparameters later on too

is this out of date or still something we want to do?

We still may want it, but it's low priority.


[Bug]: unit test apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_fail_early_bad_schema fails locally

What happened?
test_row_coder_fail_early_bad_schema fails when run test suites in non-parallel way:
$ pytest -v apache_beam/coders/row_coder_test.py::RowCoderTest

apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_fail_early_bad_schema FAILED                                                             [ 60%]

E     AssertionError: "type_with_no_typeinfo" does not match "Encountered a type that is not currently supported by RowCoder: "

but successes when run with pytes -n flag, or run independently:
$ pytest -v -n 2 apache_beam/coders/row_coder_test.py::RowCoderTest

[gw0] [ 53%] PASSED apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_cloud_object_schema
apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_fail_early_bad_schema

or
$ pytest -v apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_fail_early_bad_schema

apache_beam/coders/row_coder_test.py::RowCoderTest::test_row_coder_fail_early_bad_schema PASSED                                                             [100%]

Reproduced with python3.8 on both macOS and windows 10.
Issue Priority
Priority: 3
Issue Component
Component: sdk-py-core

The difference happens to the caused by the branching here
If running pytest with the single test, user_type is None, and the try in the if clause raises with schema printed, which passed the assertion.
If running pytest with the whole RowCoderTest, user_type is not None and the next if clause is not executed. typing_from_runner_api returned successfully and the Exception is raised much later, in here, without schema printed.

.take-issue


Change LargeTransactionTestObject to be initialized by a builder

The constructor on this object has become quite bloated now that we have pushed so much functionality into it. Writing all these different implementations into one class is also getting out of hand, but we will need to add functionality to it in the near future to support interleaved inserts, deletes and sequential scans.
The first step to cleaning this up is to change the way we initialize the test object to be via the Builder Pattern, cutting down the code clutter. Declare a LargeTransactionTestBuilder object where we can set these parameters via method (preferably self-reference return type for chaining). Pick reasonable default values for things we don't always care about.
Once this is done, it also becomes easy for us to actually return different dynamic types in the builder depending on the initialization parameters, making it possible to separate some code out from the current class.

@tanujnay112 You can take a look at this.


CondaPkg dependency for Extension package

I'm hoping to add a python dependency to an extension package, and it wasn't clear to me how this should be done.
Any tips?
x/ref https://github.com/EnzymeAD/Reactant.jl/issues/354 https://github.com/EnzymeAD/Reactant.jl/pull/407
cc @mofeing @avik-pal

i guess that just adding CondaPkg.toml suffices? https://github.com/JuliaPy/PythonPlot.jl/blob/main/CondaPkg.toml

yeah the problem is we don't want to add the condapkg.toml on Reactant itself, but only when the PythonCall extension is loaded....and that....I have no idea how to do

i guess that it'll still work? like CondaPkg.toml will only be checked when CondaPkg is loaded (or precompiled?)


ADD content/zh/docs/reference/setup-tools/kubeadm/kubeadm-init.md

dev-1.13分支上pr时已审阅。请直接合并。
Already Pass Review，Merge Directly.

please

double check if release-1.12 has anything different from dev-1.13, and
rebase your PR to new release-1.12

please

double check if release-1.12 has anything different from dev-1.13, and
rebase your PR to new release-1.12

Hi~

Already Checked the diff between 1.12 and 1.13 on the original language/en md file. They are the same.
I just re-forked the official repository just few days ago，my pr is base release-1.12 already. did i need do something else?

@YouthLab Your PR is from a branch named 'release-1.12', this is dangerous. It means you won't be able to commit two PRs at the same time for review.  What I will do is something like follows, suppose I have a fork of  the kubernetes/website repo (one remote called upstream pointing to the upstream):
git checkout master
git fetch upstream
# switch to the HEAD of the branch I want to propose against
git checkout release-1.12
# make sure my origin/release-1.12 is in sync with the upstream
git rebase upstream/release-1.12
git push
# now create a branch for work
git checkout -b trans-kubeadm-init
... (working on this branch locally)

git add .
git commit
# push my local branch to my local repo because I don't have privilege to push to the upstream
# and I'm not supposed to do so even I do have such a permission
git push -u origin trans-kubeadm-init

Now on my fork of website, I got a branch named trans-kubeadm-init. I will use github web UI to propose a PR against the release-1.12 branch in the upstream.
When I found conflicts I will go back to my local repo and do:
git fetch upstream
git checkout release-1.12
git rebase upstream/release-1.12
git push
git checkout trans-kubeadm-init
git rebase release-1.12
# there could be conflicts in the previous step.
# Now reuse the same commit ID and do a commit
git commit --amend
# force push to my local repo, with will automatically trigger an update to my PR
git push -f

There are many helps you can browse, e.g. https://help.github.com/articles/creating-a-pull-request-from-a-fork/

@YouthLab Your PR is from a branch named 'release-1.12', this is dangerous. It means you won't be able to commit two PRs at the same time for review. What I will do is something like follows, suppose I have a fork of the kubernetes/website repo (one remote called upstream pointing to the upstream):
git checkout master
git fetch upstream
# switch to the HEAD of the branch I want to propose against
git checkout release-1.12
# make sure my origin/release-1.12 is in sync with the upstream
git rebase upstream/release-1.12
git push
# now create a branch for work
git checkout -b trans-kubeadm-init
... (working on this branch locally)

git add .
git commit
# push my local branch to my local repo because I don't have privilege to push to the upstream
# and I'm not supposed to do so even I do have such a permission
git push -u origin trans-kubeadm-init

Now on my fork of website, I got a branch named trans-kubeadm-init. I will use github web UI to propose a PR against the release-1.12 branch in the upstream.
When I found conflicts I will go back to my local repo and do:
git fetch upstream
git checkout release-1.12
git rebase upstream/release-1.12
git push
git checkout trans-kubeadm-init
git rebase release-1.12
# there could be conflicts in the previous step.
# Now reuse the same commit ID and do a commit
git commit --amend
# force push to my local repo, with will automatically trigger an update to my PR
git push -f

There are many helps you can browse, e.g. https://help.github.com/articles/creating-a-pull-request-from-a-fork/

Thank You for your friendly and patient reply! (*￣︶￣)

Duplicate of #11377


Add no-danger to README

This rule was added by 0c132f5559 but was not added to the README, so it
was difficult to discover.

Thanks!


[WIP] feat(Button): add loading prop

To be defined...

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


monitor.isDragging issue

I have a problem with applying sortable example to my application.
I can't make the "opacity" to follow my drag.

When I initially pick the element up opacity is applied.

But when I move it up to change the position opacity is still applied to the original DOM element(?).
State is changed accordingly, columns in a table associated with this state are being reordered. So apart of opacity everything else is working fine.
The only difference in my app is the state which is managed via redux.
Could my problem be related to the last line from hover function?(its a copy and paste from the example app)
const columnTarget = {
  hover(props, monitor, component) {
    const dragIndex = monitor.getItem().index;
    const hoverIndex = props.index;
    if (dragIndex === hoverIndex) {
      return;
    }
    const hoverBoundingRect = findDOMNode(component).getBoundingClientRect();
    const hoverMiddleY = (hoverBoundingRect.bottom - hoverBoundingRect.top) / 2;
    const clientOffset = monitor.getClientOffset();
    const hoverClientY = clientOffset.y - hoverBoundingRect.top;
    if (dragIndex < hoverIndex && hoverClientY < hoverMiddleY) {
      return;
    }
    if (dragIndex > hoverIndex && hoverClientY > hoverMiddleY) {
      return;
    }
    props.moveColumn(dragIndex, hoverIndex); // this is action that hits reducer
    monitor.getItem().index = hoverIndex; // could this be it? I don't understand what is this line doing
  }
};

I can add more code if you will think problem might be somewhere else. I just don't want to spam this issue with a lot of unnecessary code.

State before:

Action:

State after:

OK I finally sorted it.
There was a problem with a key value I have passed in from a parent component.
I used to base that key on the index which was changing with the element.
Thats how I used to do it:
const columnTags = columns.map(
  (column, index) =>
    <SortableColumnEntry
    key={index}
    index={index}
    column={column} />)

When I changed it to stay unique and associated to the state:
const columnTags = columns.map(
  (column, index) =>
    <SortableColumnEntry
      key={column}
      index={index}
      column={column} />)

It all started to work. At the moment the columns values are unique and associated with a single entry - later on it would be good to add id field to the state.


accept exceptions kill just the accept loop thread

We should recover if possible or kill the server (and thus the node).

Fixed in #1262


Signing with PKCS#11 keypair that has no X.509 certificate

Hi,
I'm using the latest P11 functionality in 1.3.0 and noticed this issue.  Note that I do not run into this issue if the P11 keypair has an associated X.509 certificate
cosign sign --key "pkcs11:token=Remote%20Token;slot-id=0;id=%43%6f%73%69%67%6e%2d%6b%65%79%70%61%69%72%2d%63%6f%73%69%67%6e%2d%65%63%64%73%61;object=mykeypair?module-path=/usr/local/lib/myhsm.so&pin-value=1234" xxx/yyy:0.1 -d

Error: signing [xxx/yyy:0.1]: getting signer: nil certificate provided
main.go:48: error during command execution: signing [xxx/yyy:0.1]: getting signer: nil certificate provided

Hi @zosocanuck. I think this is due to this check
https://github.com/garantir-km/cosign/blob/84c94b6361848bfac9e083483b66f41e55c3d613/cmd/cosign/cli/sign/sign.go#L345
We should check for certFromPKCS11 being nil instead. Can you please try with this branch ?

@garantir-km This resolved the issue. Thanks.


Another possible solution in Calendar Scheduling

Hi Authors,
First, thank you for sharing this useful data and benchmark. While testing the Calendar Scheduling dataset, I discovered that another possible solution to certain exemplars might exist.
One example I found is calendar_scheduling_example_98:
"You are an expert at scheduling meetings. You are given a few constraints on the existing schedule of each participant, the meeting duration, and possibly some preferences on the meeting time. Note there exists a solution that works with existing schedule of every participant. Here are a few example tasks and solutions: TASK: You need to schedule a meeting for Juan, Marilyn and Ronald for half an hour between the work hours of 9:00 to 17:00 on Monday. Here are the existing schedules for everyone during the day: Juan is busy on Monday during 9:00 to 10:30, 15:30 to 16:00; Marilyn has blocked their calendar on Monday during 11:00 to 11:30, 12:30 to 13:00; Ronald has blocked their calendar on Monday during 9:00 to 10:30, 12:00 to 12:30, 13:00 to 13:30, 14:00 to 16:30; Juan can not meet on Monday after 16:00. Find a time that works for everyone's schedule and constraints. SOLUTION: "
where the golden plan is:
"Here is the proposed time: Monday, 13:30 - 14:00 "
However, according to the given constraints, I think 10:30 - 11:00 would also meet the conditions.
Could you review this question and check if there is anything I misunderstood in this dataset?
Thank you!

I also find this issue in the dataset. I look into around 50 data points and find around 10% of them actually have multiple solutions.  I wonder whether it is possible to add these solutions to the dataset.


Improve: MD editor whitespace operators

Replace tabs with 4 spaces, strip whitespace from end of lines, add newline to end of file.

done!


Require activity description

A description is now required to create a new activity
Closes #334

Other than the HTML thing it looks good, just needs the merge conflict addressed!


Picovoice Documentation Issue (/docs/tips/syntax-cheat-sheet/)

I am unable to find information on whether or not the Rhino Speech-to-Intent model allows to have a "throwaway" parameter to use in case I want to have undefined variables inside the sentence (such as the name of a city, or the name of a person) but I don't want the model to not recognize the command because I told him "Call a waiter for Simone" insted of "Call a waiter for"

Rhino doesn't have this feature, currently.


CB-10083 Remove Kafka templates from the TP release because those are…

… not tested
See detailed description in the commit message.

+11


Replace "unix" by "http+unix" for PROTOCOL

Fixes #9318

Is this really worth doing?
I'd prefer if we could get host and port merged in to an ADDRESS value and then we'd be able to detect if we need to use a unix or a tcp port by the ADDRESS. Then protocol can drop all of the unix variants.

I may be missing something, but a ADDRESS value wouldn't be sufficient, as you still need to specify if that's FCGI or HTTP (or a future protocol), no ?

Yes you would still need the protocol field but the weird +unix variants would be unnecessary

Yeah, I agree, this would be better. having each potential protocol being double is not elegant and would make doc more complex quite fast if a new protocol is added (eg, something to replace FastCGI).

Keep note thathttps+unix is certainly also a possibility.

This change is fine to me.
zeripath's suggestion about "get host and port merged in to an ADDRESS" is pretty good.
So should we wait for the new work about unified ADDRESS, or get this PR merged first?
(I marked this PR as wip temporarily)

I feel that the ADDRESS change would requires a longer design discussion.

I rebased, but I think it requires a quick re-review

@zeripath @techknowlogick how do you think?

Bump. If still no objection in 2 days, maybe we can get this PR merged.

yeah I think we should merge as is and address the address issue at another point.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f7094c8). Click here to learn what that means.
The diff coverage is 12.50%.

@@           Coverage Diff           @@
##             main   #17771   +/-   ##
=======================================
  Coverage        ?   45.32%
=======================================
  Files           ?      815
  Lines           ?    90695
  Branches        ?        0
=======================================
  Hits            ?    41107
  Misses          ?    43025
  Partials        ?     6563

Impacted Files
Coverage Δ

cmd/web.go
0.00% <0.00%> (ø)

modules/private/internal.go
56.00% <0.00%> (ø)

modules/setting/setting.go
49.07% <16.66%> (ø)

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 f7094c8...9974986. Read the comment docs.

Bump. If still no objection in 2 days, maybe we can get this PR merged.

So do you want to remove the wip label?


Kafka source oauth implementation

Description

Implemented the OAuth functionality

Issues Resolved

Github issue https://github.com/opensearch-project/data-prepper/issues/254

Check List

[ ] Implemented the functionality including testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

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.

Closing this PR because we have raised another PR#2858 using the Kafka built in libraries for the oauth implementation.


Include "Metal3: Kubernetes Native Bare Metal Cluster Management" talk as content

I suggest to add @maelk  talk at Cloud Native Nordics meetup as content in our blog:

Prepare a blog post which includes Youtube link, demo's showns as videos (@maelk already has the asciinema) and elaborated content.
Add a link in the same blog post to the slides presented. Probably a link to a public repository (gdrive or similar) or depending on the size, we could consider add it in this repo or metal3-docs. This is open to discussion.

work in progress

closed by https://github.com/metal3-io/metal3-io.github.io/pull/143


[ILLA App idea] Create a CRUD App via ILLA Cloud and use PostgreSQL as data resources

Description
Create a CRUD App via ILLA Cloud and use PostgreSQL as data resources
Additional Information
Create a CRUD App via ILLA Cloud and use PostgreSQL as data resources.

Hi I would like to work on this can you assign this task to me
Thanks

Hi @Dhoni77 .
Here is a helpful link to self assign this issue to you.
Self Assign an Illa Issue
I hope this helps.  Happy Hacking.


Replace nugget with got

Electron Forge is currently using nugget for something.  See:
└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>While it currently works, nugget was last updated five years ago.  Currently there is a package that nugget depends on that needs updating (trim-newlines) and at some point request will need to be removed from the tree.
I'm not familiar with the code that uses nugget, but I'm just throwing it out there that maybe "got" could be used to do the same thing?

This is pretty low priority for me, unless I get more time via sponsorship. nugget is different from got in that it also has a UI-specific element of showing the progress of the download.

It would be great if you could somehow replace nugget. The package trim-newlines that nugget depends on contains a major security issue https://github.com/advisories/GHSA-7p7h-4mm5-852v. Even this should not be a big issue for electron-forge, some people and companies won't use electron-forge anymore because of compliance policies.

It would be great if you could somehow replace nugget. The package trim-newlines that nugget depends on contains a major security issue https://github.com/advisories/GHSA-7p7h-4mm5-852v. Even this should not be a big issue for electron-forge, some people and companies won't use electron-forge anymore because of compliance policies.

This is not a good reason in this case, see https://github.com/electron-userland/electron-forge/issues/2377#issuecomment-879584816 for details.


Using chips inside an edittext

Is it possible to use chips inside an edittext?
If so, could you please give me a clue how to use it?
Thanks in advance.

Have you the answer ?
I have the same problem.

Hi @maelfosso,
I haven't tried this library. Decided to use another one, so I don't have an answer, sorry :(

Hi @hannayurkevich
Which one are you using ?

@maelfosso, I'm using this one - https://github.com/splitwise/TokenAutoComplete. And it proved to be quite OK (at least for my purpose).
Have you tried some chips library?

Hi @maelfosso and @hannayurkevich and sorry for the delay
This is not possible to use it in an EditText because the View itself is a ViewGroup
I don't have currently the time to update it so any help is appreciated :)


insecureSkipVerify: true not being applied (v2)

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?

enabled serversTransport.insecureSkipVerify: true
What did you expect to see?
Plex works over https (with cloudflare)
What did you see instead?
502 gateway error from cloudflare
This is because plex, emby, and other apps use a self signed cert over https and there's no way to stop that. So in 1.7, insecureSkipVerify=true solves the self signed cert issue on the backend.
Output of traefik version: (What version of Traefik are you using?)

Version:      2.0.0-beta1
Codename:     faisselle
Go version:   go1.12.7
Built:        2019-07-19T16:04:34Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
global:
  checkNewVersion: true
  sendAnonymousUsage: false
serversTransport:
  insecureSkipVerify: true
providers:
  docker:
    endpoint: "unix:///var/run/docker.sock"
    exposedByDefault: false
entryPoints:
  websecure:
    address: ":443"
certificatesResolvers:
  cloudflare:
    acme:
      email: "xxx"
      storage: "/etc/traefik/acme.json"
      dnsChallenge:
        provider: cloudflare

docker labels:
      - "traefik.enable=true"
      - "traefik.http.routers.plex.rule=Host(`plex.${TLD}`)"
      - "traefik.http.routers.plex.entrypoints=websecure"
      - "traefik.http.routers.plex.tls.options=default@file"
      - "traefik.http.routers.plex.tls.certresolver=cloudflare"

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
Issue templates help us help you by providing all necessary information.
Please edit your issue and use the available templates:

Feature request
Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny :heart: :rabbit: :heart:

Hi @robertbaker, could you provide more information (see below) to help us reproduce and evaluate if it is a bug or a misconfiguration:

Reproducible case or full configuration (how is Traefik deployed? And Plex? With which option?)
The logs, as requested by the issue template

I'm confused by the label "traefik.http.routers.plex.tls.options=default@file" as we do not see any tls.options directive on your Traefik configuration.

I only provided what I thought was relevant and minimal and missed that line stripping it down.
I was mistaken. turning on debug mode showed hidden errors that it traefik was connecting to 1900 and not 32400 (first exposed in dockerfile).
I've been reading the services page over and over and there was 2 problems. It wasn't clear to me how to do traefik.port in v2. Also it didn't jump out that it was a loadbalancer setting, since I don't use more than 1 instance.
This is what I needed:
```yaml tab="Docker"
# Sets the port traefik will use to connect to the container
labels:
- "traefik.http.services.my-service.loadbalancer.server.port=12345"
```

So I made a PR to improve the docs! https://github.com/containous/traefik/pull/5224

Thanks @robertbaker for closing the issue with a clear feedback and contribution proposal!


GraphQL support

Hi Nestjs Community!
As I'm still discovering the Nestjs framework and its awesome community, I've found this very nice little package :)
It is very convenient and it allowed me to implement quite easily some ABAC control on the API I'm working on.
Nevertheless, the only Access Control guard it offers (ACGuard) is not compatible with the context request used within GraphQL resolvers.
So I was wondering if you were thinking about implementing either an additional guard or even making the actual one compatible with both classical and graphql requests.
Actually, I think the implementation would be quite straightforward and I would gladly participate in.
Have a nice day!

Hi, since this PR landed https://github.com/nestjs-community/nest-access-control/pull/7
You will be able to customize the ACGuard with your needs.
Wait for new version with also some docs.

Thank you! That's awesome if the PR offers such a feature!

@shekohex I've seen you merged the PR and that the master branch is now up-to-date with the new guard.
When do you plan on updating the package on npm so we can have the last version available right in the project ?

Hi @LandazuriPaul  Sorry for the late publish, i was so busy.
I just published it and it's available from v1.0.1 .

@shekohex For sure there is no rush :) Thank you for your work and have a nice day!


runtime: disable seccomp

Some docker images are started as an unprivileged user and use file
capabilities to gain privileges like listening on a low port.
This doesn't work in rkt because, due to a systemd bug (WIP fix [1]),
enabling seccomp implies no_new_privs [2].
As a workaround, let's disable seccomp for now.

It's unfortunate that we cannot disable seccomp only for the problematic images, because when we start the sandbox, we don't know yet what images it will contain.
LGTM
Could you file a follow-up issue to remember to remove this when the systemd PR is merged and used in rkt?

https://github.com/kubernetes-incubator/rktlet/issues/120

I'm dubious here. Aren't we passing the default seccomp profile (all permitted?) to each app?

What's passed in the cri is an annotation (or in new versions of k8s an option in SecurityContext) and we don't do anything with it in rktlet so we'll go with rkt's default (enabling the default seccomp filter). Also, in rkt we force no_new_privileges if UID != 0 (even if the seccomp filter is empty).
So to make it work we'd need to remove/change forceNoNewPrivileges from rkt and handle the annotations similar to here https://github.com/kubernetes/kubernetes/blob/v1.7.5/pkg/kubelet/dockershim/helpers.go#L205

I was misunderstanding rkt's code, there's no changes needed there.
I implemented forwarding of the seccomp policy in https://github.com/kubernetes-incubator/rktlet/pull/125. I think we can close this and continue there.


OpenVPN Instance : Client Specific Overrides not applied

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
On OPNsense 23.7.2 Client Specific Overrides are not applied with an OpenVPN (new) instance (no mention to CSC in log, and /var/etc/openvpn-csc/3/ stays empty) despite checking the instance in the CSO  "Servers" field.
After applying commit d3af50a and manually creating directory /var/etc/openvpn-csc/961988-0461-4-8933-779744/ CSO are now created in /var/etc/openvpn-csc/961988-0461-4-8933-779744/ but instance configuration file still mention client-config-dir /var/etc/openvpn-csc/3 instead of /var/etc/openvpn-csc/961988-0461-4-8933-779744/
Followup forum thread : https://forum.opnsense.org/index.php?topic=35447.0
To Reproduce
Steps to reproduce the behavior: Try to use CSO in 23.7.2 with or without patch d3af50a
Environment
OPNsense 23.7.2 + patch d3af50a

In my attempt to server both new (mvc) id's and legacy id's (which are used for the device naming), I missed a spot it seems. Can you try https://github.com/opnsense/core/commit/78d49d85fea6141191e8382496b44766fe262480 on top? It should preserve the usual numbering in the /var/etc/openvpn-csc/ path.

It is working for both d3af50a and 78d49d8 ! Thanks !

@pfoo thanks for confirming, we'll aim to include this in our next minor release.


[Event Hubs] Eventhubs livetest fix

Use try ... finally or with statement to make sure client is closed if assertion has errors.
This can avoid segmentation fault error.

/azp run python - eventhubs - tests

This is weird.. why using the context manager could avoid the seg fault?


Quality handling for TM and TS

Is your feature request related to a problem? Please describe.
Another feature described in the Connx loss and GI failure handling documentation is the management of initial validity for all TS/TM as well as their outdated status.
Describe the solution you'd like
Complete the HNZ south module with the following featrues to cover the behaviors described on the wiki:

Allow the creation of "quality reading". Those are regular data_object readings except they do not have a do_value attribute.
When the plugin starts:

Create a quality reading for each TM with do_an="TMA" and do_valid=1.
Create a quality reading for each TS with do_cg=0 and do_valid=1.

Add a new attribute do_outdated to all TM and TS readings (0 = up to date, 1 = outdated).
Whenever the connection to the HNZ device is lost start a timer of 500ms.
If this timer has expired and the connection is still lost:

Create and send a quality reading for all TM with do_an="TMA" and do_outdated=1.
Create and send a quality reading for all TS with do_cg=0 and do_outdated=1.

At the end of a CG, for any TS that was not received, create and send a TS quality reading with do_cg=0 and do_valid=1.

Updated wiki documentation to reflect this change: https://wiki.lfenergy.org/pages/viewpage.action?pageId=65821805


Separate callbacks into a separate Python package

We may consider cleaving callbacks from bluesky in the general sense. Callbacks are useful outside the context of data acquisition (I personally feel that any data analysis system down stream should support them).
Expected Behavior
Callbacks are their own library
Current Behavior
They are not their own library
Possible Solution
Make a new library
Context
I'm writing a data analysis workflow and would like to use callbacks but don't want the RunEngine (as pretty and nice as it is @tacaswell) or the other acquisition logic.

Expanded from #719

@stuartcampbell, @tacaswell, and I discussed this over lunch on Friday, and I'll summarize here.
Separating callbacks from the rest of the package has a certain attractive purity. The callbacks are useful without the RunEngine and the plans. The RunEngine and plans aren't so useful without at least some callbacks available to test and/or use, so it seems like a separate callbacks package would become a required dependency of bluesky.
Given that there would be a one-way dependency, what's the practical advantage of separating the packages? Is it helpful to be able to install the callbacks without the RunEngine and the plans? Notice that the RunEninge and the plans don't add heavy dependencies. Specifically, looking at requirements.txt:
cycler
event-model
historydict
jsonschema
matplotlib
numpy
super_state_machine  # not heavily used, may be factored out in the future
toolz
traitlets  # will be removed in the upcoming release

All of the dependencies are small, pure Python packages that are cheap and easy to install, except for the ones that a callbacks package would need anyway (numpy, matplotlib).

This will happen organically as new work on things that consume documents happen in separate repos.


Fix volume creates blocked by stale cache entries

When a conflict is found in the volume cache, check with the driver if that volume still actually exists. If the volume doesn't exist, purge it from the cache and allow the create to happen.
 DCO is properly signed on said commit Signed-off-by: Wentao Zhang<EMAIL_ADDRESS>

@cpuguy83 Everything is fine except that any driver should be allowed to re-create the volume. The condition fails if the same volume driver tries to create the volume again.
I have made the changes. Please review #27177 if it is fine.

@cpuguy83 The fix needs to allow the same volume driver to re-create the volume with the same name.

Ok, this is all fixed up.

@anusha-ragunathan could you have a look at this one?

LGTM

Updated

LGTM


Credit Calculation | View Fuel Classes |3|

Story:
As a TFRS user, I want to be able to view the different fuel classes so that I can understand how current and future credits will be calculated.

This card is to build a table in both the back-end and front-end to track to view the different fuel classes used in the calculation of credits (section 6 of the Act).
The fuel classes are defined in section 1 of the Act and consist of "gasoline class" and "diesel class".

Scenario 1:
GIVEN that I am an IDIR user
AND I am on the Administration tab
WHEN I click on the "Compliance Reporting" sub-tab
THEN I am taken to the Compliance Reporting sub-tab within the Administration tab
AND I can view the Fuel Classes
Forward looking usage:

We will be using/pulling these values when we implement compliance reporting as they are used in the calculation of credits/debits. https://trello.com/c/eqw7vn7Q/897-credit-calculation-view-fuel-classes-3

 Credit Calculation | View Fuel Classes |3|


LSP's using zx to install fails on `replaceAll('\', '\\')

Software installed

Ubuntu-20.04 LTS
Neovim 0.5 (nightly, or app image)
Latest nvim-lsp-installer plugin

Description
Firstly, thanks for writing this installer. It has simplified my neovim setup immensely!
The issue occurs when I try to install lsps that rely on the zx package. Specifically terraform-ls and clangd. When running :LspInstall, I get the following error:
file:///home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/zx/index.mjs:244
      .replaceAll('\\', '\\\\')
       ^

TypeError: arg.replaceAll is not a function
    at Function.quote (file:///home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/zx/index.mjs:244:8)
    at $ (file:///home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/zx/index.mjs:39:13)
    at file:///home/issafalcon/.local/share/nvim/site/pack/packer/start/nvim-lsp-installer/lua/nvim-lsp-installer/servers/clangd/install.mjs:15:8
    at ModuleJob.run (internal/modules/esm/module_job.js:170:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async importPath (file:///home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/zx/zx.mjs:130:3)
    at async file:///home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/zx/zx.mjs:49:5

[Process exited 1]

I tried for clojure_lsp also, which has the same issue, but sumneko_lua works fine. For now, I am installing manually and using my own configuration for these servers, but thought I would raise this in case others are finding the same problem, and it's not just an issue on my own machine setup.

Hey! What Node version are you running node --version? It seems like zx snuck in a bump in required Node version this July, going from 14 (LTS) to 15 (String.prototype.replaceAll was added in Node.js 15).

Ah, thanks! I was running on 14.7. I updated to 15.14.0, which seemed to get me further to this point:
/bin/bash: /home/issafalcon/.local/share/nvim/lsp_servers/.zx/node_modules/.bin/zx: No such file or directory

Hmm, interesting. Did you restart neovim after upgrading Node? It caches zx installations per neovim session which might be causing some issues

Seems killing and restarting my tmux session was also necessary for it to work! Thanks for your help! I'll close this out.

:+1: cool. I've asked if they could backport the fix to the v1 release branch, in which case Node 14 (LTS) should work just fine again!


Increase majc priority for tablets over file size threshold

CompactionManager.mainLoop runs in the TabletServer looking for tablets that need to be compacted. It ends up calling CompactionService.submitCompaction at some interval for each hosted Tablet. CompactionService.getCompactionPlan will make a CompactionPlan for the tablet and log a warning if no CompactionPlan is created but the number of files is larger than TSERV_SCAN_MAX_OPENFILES. When there are no compactions running for the tablet and no plan is calculated, then DefaultCompactionPlanner.makePlan takes into account TABLE_FILE_MAX and TSERV_SCAN_MAX_OPENFILES and will create a system compaction that considers all of the files and calculates which ones need to be compacted to get below the limit. Finally, a priority is calculated by calling CompactionJobPrioritizer.createPriority. However, given that this compaction is a SYSTEM compaction it will have a lower priority than all current USER compactions and it's priority will still be based on the total number of files. Given that the TABLE_FILE_MAX is per-table it's possible to have two tablets from different tables and the tablet that is over the size threshold has a lower priority than the tablet that is not over the size threshold. This change modifies
CompactionJobPrioritizer.createPriority to take into account whether or not the tablet is over the threshold to give it a higher priority.
Closes #4610

May still want to leave #4610 open after merging this.  This change is nice in that it helps compactions run faster for tablets over the threshold.  There is still the problem that scan servers cache the file list.  So if a scan server caches the list of files of a tablet w/ too many files for 5 mins then that tablet can not be scanned for that 5 min period even if it does compact.  Not sure of the best way to handle this, scan servers could possibly poll the tablets files a bit more frequently when a tablet is in this condition.

@keith-turner  - I think I addressed all of your suggestions in the latest commit.


Add basic documentation

Codecov Report

Merging #87 (f5acbed) into main (8f8c8be) will decrease coverage by 9.43413%.
The diff coverage is 65.78947%.

@@                 Coverage Diff                 @@
##                main         #87         +/-   ##
===================================================
- Coverage   88.59779%   79.16366%   -9.43413%
===================================================
  Files             64          65          +1
  Lines           2710        2774         +64
===================================================
- Hits            2401        2196        -205
- Misses           309         578        +269

Impacted Files
Coverage Δ

frouros/common/update.py
50.00000% <ø> (-30.00000%)
:arrow_down:

frouros/datasets/real.py
100.00000% <ø> (ø)

frouros/datasets/synthetic.py
96.55172% <ø> (+20.68965%)
:arrow_up:

frouros/metrics/base.py
92.00000% <ø> (ø)

frouros/metrics/prequential_error/base.py
94.44444% <ø> (ø)

frouros/metrics/prequential_error/fading_factor.py
93.75000% <ø> (ø)

...ros/metrics/prequential_error/prequential_error.py
100.00000% <ø> (ø)

...ouros/semi_supervised/margin_density_based/base.py
83.33333% <ø> (-5.20834%)
:arrow_down:

...rouros/semi_supervised/margin_density_based/md3.py
96.10390% <ø> (ø)

frouros/supervised/utils.py
0.00000% <ø> (-80.00000%)
:arrow_down:

... and 41 more


fix/user_attrbutes_null

Code reviewers

[ ] @loqimean

Summary of issue
Change user's first_name and last_name null to false
Summary of change

changed null:false in db
added columns in admin's users table
fix test

CHECK LIST

[ ]  СI passed
[ ]  Сode coverage >=95%
[ ]  PR is reviewed manually again (to make sure you have 100% ready code)
[ ]  All reviewers agreed to merge the PR
[ ]  I've checked new feature as logged in and logged out user if needed
[ ]  PR meets all conventions

Done


Fix productProcessor emtpy request with using graphql

Since ProcessorFactory.getAdapter in src/processor/factory.js was updated with extra params it causes an error with using Graphql adapter

Thanks, that makes perfect sense

Hi @yuriboyko please just fix the CI error and this is ready to be merged in:
/home/travis/build/DivanteLtd/vue-storefront-api/src/graphql/elasticsearch/catalog/resolver.js
  31:31  error  'req' is not defined  no-undef

@pkarw  Fixed


Vulnerability in a pug dependency

The version of clean-css used by a pug dependency, is resolved to the version 3.4.28 but there is a vulnerability in versions below 4.1.11 (https://github.com/jakubpawlowicz/clean-css/commit/2929bafbf8cdf7dccb24e0949c70833764fa87e3).

Per this we need to go from https://github.com/auth0/webtask-tools/blob/3da48e198bec7b0c017267932d59c20db7881252/package.json#L29 to 2.0.3.

I didn't see this part in the README => https://github.com/auth0/webtask-tools#issue-reporting , I don't know if what I reported fit this section but I would suggest to add an issue template for future case like this to warn anyone wanting to report a vulnerability

@antham oh yeah, I didn't notice that either 😬
Oh well. I assume that this one is fine, since anyone doing an npm audit would see the vulnerability (i.e. this issue isn't really disclosing anything).

FYI I also pinged Auth0 support and they said:

Thank you for contacting Auth0 support. And thank you for submitting the PR. I am escalating this ticket to our engineering team to review and merge the changes. I will respond back to you as soon as I get a response back from them.

🤞


nandland_go: reorder 7-segment displays

The schematics of the Nandland Go number the 7-segment displays from left to right as 1 and 2, and the original commit introducing the Nandland Go numbers the 7-segment displays from left to right. However, the DE10 Lite board numbers the 7-segment displays from right to left. We should probably be sticking to one of the two orders and avoid introducing inconsistencies between boards like this. The right to left ordering probably makes the most sense, as the very first display would be used to display the least-significant nibble. So this pull request changes the order of the 7-segment displays for the Nandland Go to follow the same order as used for the DE10 Lite.
If we instead prefer left to right ordering, then that is fine with me too. I can have a look at the other boards that feature 7-segment displays to ensure the ordering is consistent at least.

I would argue for left-to-right ordering, for one reason: while for purely numeric displays this makes sense, 7-segment displays are also used to display a subset of letters, and 14-segment displays the full set of them. It would be particularly inconsistent to have 7-segment and 14-segment display resources to use a different ordering.

Fair enough, then I will just fix the DE10 Lite :+1:.


Fix StringExtensions.GetOrigin throws for malformed URI #3065

What issue does this PR address?
#3065
Does this PR introduce a breaking change?
No

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Crokus sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


Register fails when account receives funds in v0.4.0

Error: Account wallet not found
    at b (index.browser.min.js?fb75:2:1062725)
    at t.assertRegistrationAccount (index.browser.min.js?fb75:2:1061452)
    at t.AccountData.register (index.browser.min.js?fb75:2:1057193)
    at _callee$ (index.tsx?4f07:64:31)
    at tryCatch (runtime.js?ecd4:45:16)
    at Generator.invoke [as _invoke] (runtime.js?ecd4:274:1)
    at prototype.<computed> [as next] (runtime.js?ecd4:97:1)
    at asyncGeneratorStep (_async_to_generator.mjs?1752:3:1)
    at _next (_async_to_generator.mjs?1752:25:1)
    at eval (_async_to_generator.mjs?1752:32:1)
    at new Promise (<anonymous>)
    at eval (_async_to_generator.mjs?1752:21:1)
    at register (index.tsx?4f07:61:17)
    at _callee$ (index.tsx?4f07:34:11)
    at tryCatch (runtime.js?ecd4:45:16)
    at Generator.invoke [as _invoke] (runtime.js?ecd4:274:1)
    at prototype.<computed> [as next] (runtime.js?ecd4:97:1)
    at asyncGeneratorStep (_async_to_generator.mjs?1752:3:1)
    at _next (_async_to_generator.mjs?1752:25:1)

Error: Account wallet not found
    at b (index.browser.min.js?fb75:2:1062725)
    at t.assertRegistrationAccount (index.browser.min.js?fb75:2:1061452)
    at t.AccountData.register (index.browser.min.js?fb75:2:1057193)
    at _callee$ (index.tsx?4f07:64:31)
    at tryCatch (runtime.js?ecd4:45:16)
    at Generator.invoke [as _invoke] (runtime.js?ecd4:274:1)
    at prototype.<computed> [as next] (runtime.js?ecd4:97:1)
    at asyncGeneratorStep (_async_to_generator.mjs?1752:3:1)
    at _next (_async_to_generator.mjs?1752:25:1)
    at eval (_async_to_generator.mjs?1752:32:1)
    at new Promise (<anonymous>)
    at eval (_async_to_generator.mjs?1752:21:1)
    at register (index.tsx?4f07:61:17)
    at _callee$ (index.tsx?4f07:34:11)
    at tryCatch (runtime.js?ecd4:45:16)
    at Generator.invoke [as _invoke] (runtime.js?ecd4:274:1)
    at prototype.<computed> [as next] (runtime.js?ecd4:97:1)
    at asyncGeneratorStep (_async_to_generator.mjs?1752:3:1)
    at _next (_async_to_generator.mjs?1752:25:1)

Which method call caused this error?

fixed. using setAccountFromMnemonic before register, thanks


Pod sometimes stuck with first init container

Pods by default get a check-dns init container. Sometimes a new pod doesn't get past that first init container and hangs:
NAME                                                   READY     STATUS     RESTARTS   AGE
example-sensu-cluster-gzwbrntcd6                       0/2       Init:0/3   0          4m

Example description (kubectl describe pod ...):
Init Containers:
  check-dns:
    Container ID:  docker://5a1629435ad0067359b80ff5c82c8f058aa90f8a03cd36bd835751eb6da34340
    Image:         busybox:1.28.0-glibc
    Image ID:      docker-pullable://busybox@sha256:0b55a30394294ab23b9afd58fab94e61a923f5834fba7ddbae7f8e0c11ba85e6
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c

          TIMEOUT_READY=0
          while ( ! nslookup example-sensu-cluster-gzwbrntcd6.example-sensu-cluster.default.svc )
          do
            # If TIMEOUT_READY is 0 we should never time out and exit
            TIMEOUT_READY=$(( TIMEOUT_READY-1 ))
                        if [ $TIMEOUT_READY -eq 0 ];
                                  then
                                      echo "Timed out waiting for DNS entry"
                                      exit 1
                                  fi
                              sleep 1
                            done
    State:          Running
      Started:      Wed, 18 Jul 2018 14:06:05 +0200
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:         <none>

The response from kube-dns is NXDOMAIN but that's also the case for a successful setup and nslookup still returns 0 then:
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>:53

** server can't find example-sensu-cluster-gzwbrntcd6.example-sensu-cluster.default.svc: NXDOMAIN

*** Can't find example-sensu-cluster-gzwbrntcd6.example-sensu-cluster.default.svc: No answer

I see the issue happening for example after creating a new cluster and doing a restore:
kubectl apply -f example/example-sensu-cluster.yaml
./example/restore-operator/restore-backup --cluster-name=example-sensu-cluster --aws-bucket-name=sensu-backup-test --backup-name=sensu-cluster-backup-1531893564

If the pod gets stuck, I redo the restore operation and it usually works then:
kubectl delete sensurestore example-sensu-cluster
./example/restore-operator/restore-backup --cluster-name=example-sensu-cluster --aws-bucket-name=sensu-backup-test --backup-name=sensu-cluster-backup-1531893564

Have you tried using -type=a like suggested in https://bugs.busybox.net/show_bug.cgi?id=11161#c4? Maybe it's worth it?

No I haven't. I meant to say: https://github.com/docker-library/busybox/issues/48 is not an issue for us, since we use an older image, so I don't think we should need the -type=a workaround.

I haven't managed to reproduce the bug yet today in a few attempts.


Allow for rectangular matrices in QR, QL, RQ, LQ factorizations.

This allows for non-square matrices in these routines, e.g.
MAGICL> (qr (rand '(4 2)))
#<MATRIX/DOUBLE-FLOAT (4x2):
   0.551     0.151
   0.137     0.808
   0.659     0.122
   0.493    -0.556>
#<MATRIX/DOUBLE-FLOAT (2x2):
   1.310     1.189
   0.000     0.857>

This also addresses #78. The previous order business was a bit too confusing imo. The key thing that's needed for working with LAPACK is to extract upper/lower square submatrices. If we had slices, I would have used those, but for now I've just added a :square flag. This follows the LAPACK convention: when enabled, upper-triangular takes the upper rightmost square submatrix, and lower-triangular takes the lower leftmost, e.g.
MAGICL> (from-list '(1 2 3 4 5 6) '(2 3))
#<MATRIX/INT32 (2x3):
    1      2      3
    4      5      6>
MAGICL> (upper-triangular (from-list '(1 2 3 4 5 6) '(2 3)))
#<MATRIX/INT32 (2x3):
    1      2      3
    0      5      6>
MAGICL> (upper-triangular (from-list '(1 2 3 4 5 6) '(2 3)) :square t)
#<MATRIX/INT32 (2x2):
    2      3
    0      6>

@stylewarning @notmgsk someone w/ authority
if you review this PR i'll make another


Javascript chart not showing

Hey There,
I have a project called "Cepat Sembuh", the project use bootstrap and material design framework,
The problem is...
I try to use Chart.js by @nnick,
But the chart is not showing
The code is live at https://github.com/christoga/cepatsembuh
And the problem is at royal.html on www/ folder
Thanks!

Please use StackOverflow for support. This tracker is only for direct problems with the code provided by MDL.


Ignore empty driver build failure files

Description
When compiling a large number of drivers, sometimes some BPF drivers for kernels that don't support it are reported as failed to build, even though the actual build shows a message stating that it is being skipped. Since we redirect stderr to this file, an empty file would be the same as no error, so we should be ok to ignore it.
I suspect when the driver is skipped there might be some timing issue with the subshell being spawned to run tee, making it so we attempt to delete the file before it is actually created and then the subshell comes up and creates the empty file.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed

[x] Run with no-cache label should result in a green check for the driver build check step

Holding off on this, since it works on GHA but fails on OSCI. We can merge it once we drop OSCI.


Why lombok is not used?

Not really an issue, but its really upsetting to write all the getters, setters and other boilers that lombok knows how to handle.
Why there is no use of it?

Are you asking why morphia isn't using lombok?  I'm not entirely sure what you're looking for.  If you can post something to the mail mailing list, we can try to answer you questions.


of defects in Codeflaws.

In the readme of Codeflaws repo, it has been said that the Codeflaws contains 4085 defects (twice). However, I found only 3902 defects in http://www.comp.nus.edu.sg/~release/codeflaws/codeflaws.tar.gz file.
Has Codeflaws evolved?

Hi, thank you for pointing out the inconsistencies. Yes, the number of defects in the README.md is outdated. It should be 3902 defects as stated in the website (https://codeflaws.github.io/) and descriptions of this repository.

Has Codeflaws evolved
The number of defects is updated because some defects are removed as they are irreproducible.


'EntsogPandasClient' object has no attribute 'query_operational_point_data'

Hi,
Thanks for the package. I'm trying to use the function query_operational_point_data as you do in the description but I get an error saying that it does not exist. I look in the class and it seems that the function does exist. Do you know what's going on? I have installed the package as you describe in the description.
Best.

Solved, sorry.


[lit-html] Finalize public Part API

We've created the PartInfo interface as a common interface between client-side and server-side Parts. Now we need to finalize the client-side only public interface, especially __value and __setValue.
__value is currently used by live() in order to bypass the dirty-checking of __setValue(). We thought we might not need __setValue() because we can return values from directives now, but it's used by repeat() to set item part values, and it'll be needed by any action-at-a-distance directive that doesn't integrate with a host element, like until(), asyncReplace(), and some localization directives. Without it those are unimplementable, possibly hindering upgrade paths even if we don't include them in core anymore.

A couple other notes I've made for things we should be sure to work out as part of finalizing the API:

_$litType$ used by cache to determine if value is TemplateResult - need some sort of value type helper API?
The meaning of "value": If we're going to keep around a public API for the "value" instance field (currently __value / getPartValue), I would love to call it something different.  The values you pass to update/setValue have a different meaning than __value, so they should have different names IMO. The value stored in __value is after any transformations during commit (resolving directive, turning TemplateResult into TemplateInstance...), and is used for dirty-checking. Maybe committedValue or resolvedValue?
Is value.strings === undefined going to be our official API for non-interpolated/full-width attribute bindings?
Do we want to stick with long-ish PROPERTY_PART, etc. constants as the public API for differentiating part.type?
Should getLiveValue be on AttributePart interface or a part helper function? Any other uses for that outside of live?
Are we going to support async directives? This is possible for NodePart (given setPartValue helper), but not for AttributePart. Should we update setPartValue to do a good thing for AttributePart (or add an attribute-specific setter helper)?

These are more around directives, but might as well include here since they're inter-related:

update / render - some directives have unused render - how should we/users test that (styleMap currently pulls off result._$litDirective and subclasses the directive class to actually use render)?
Nested directives - in or out?

Another need for a replacement for instanceof TemplateResult: https://github.com/open-wc/open-wc/pull/1851/files#r493625677

A few more:

Move Directive and directive() from core to a directive.ts module?
Combine directive.ts module with parts.ts helpers into one module?
Make setDirectiveValue an instance method on Directive?


✨  Added global key option

Description
A global option for key is added which can be used to have a consistent naming convention for all the store modules persisting data in an app. Example can be to always prefix the key names
Linked Issues
https://github.com/prazdevs/pinia-plugin-persistedstate/issues/131
Additional context

Hey, i took the decision to "reimplement" this and keeping everything contained is the option normalization part.
here's the PR https://github.com/prazdevs/pinia-plugin-persistedstate/pull/137
I wanted you to confirm this would satisfy the issue and solve it. tyvm!

I think your solution makes more sense and keeps things simpler.


feat: add simple donors pool

added a simple donors pool to have a starting point for dao
I had to disable @eydbk contract because it wasn't compiling

Merging this pr tested and looks good


[FR] - CLI - Metadata in transactions

Present in the node.  Still needs to be added to the tx construction CLI command.

Merged but could do with testing and feedback.