npm install fails on node16?

Running: npm install
Fails with error:
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp -- install --update-binary --fallback-to-build=false || npm run build -- --release
npm ERR! 403 status code downloading tarball https://x-tech-npm-binaries.s3-us-west-2.amazonaws.com/lingua-node/v0.3.0/Release/lingua-node-linux-x64-node-v93.tar.gz
npm ERR!
npm ERR! ><EMAIL_ADDRESS>build
npm ERR! > neon build "--release"
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>| linux | x64
npm ERR! node-pre-gyp WARN Using needle for node-pre-gyp https download
npm ERR! node-pre-gyp info check checked for "/home/leonard/workspace/tinyld/node_modules/lingua-node/native/index.node" (not found)
npm ERR! node-pre-gyp http GET https://x-tech-npm-binaries.s3-us-west-2.amazonaws.com/lingua-node/v0.3.0/Release/lingua-node-linux-x64-node-v93.tar.gz
npm ERR! node-pre-gyp http 403 https://x-tech-npm-binaries.s3-us-west-2.amazonaws.com/lingua-node/v0.3.0/Release/lingua-node-linux-x64-node-v93.tar.gz
npm ERR! node-pre-gyp ERR! install error
npm ERR! node-pre-gyp ERR! stack Error: 403 status code downloading tarball https://x-tech-npm-binaries.s3-us-west-2.amazonaws.com/lingua-node/v0.3.0/Release/lingua-node-linux-x64-node-v93.tar.gz
https://github.com/botisan-ai/lingua-node
has new version addressing build failure on node16.
I try to upgrade and will create a PR if successful.

ha yes, I noticed that recently, the dev-dependencies only install <= node14
the benchmark process is the culprit (and the need to install bunch of other third party libs to test them)
Some of them have native dependencies and can cause lot of install problems.
I already created an issue for that, moved them in a sub project and dockerize them, but I have started to work on it yet https://github.com/komodojp/tinyld/issues/6
One of the workaround for the moment is to manually remove problematic dependencies from package.json
"cld": "^2.7.0",
"lingua-node": "^0.3.0",

It should install and you should be able to run normal commands like yarn test, yarn build

Indeed I confirm that after upgrading to<EMAIL_ADDRESS>it install on node16.
Updated that 👍

I just went out for grocery shopping, but it seems you fixed it all already.


[Windows][Linux] Support of '*' CSP rules for applications

This patch enables manifest CSP rules containing '' such as:
'http:///' or 'https://*.example.com'.
BUG=XWALK-6745

@darktears PTAL

LGTM


Add a toggle for AKS Cluster

If env var E2E_ON_AKS_CLUSTER is true, it is running on
an AKS cluster. Skip all tests and enable them gradually.
Signed-off-by: Zhecheng Li<EMAIL_ADDRESS>
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.702%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
15377

Relevant Lines:
19293

💛  - Coveralls


Changing UI for sketch

Moving the current pannel completely to the right so that it doesn't feel like the complete copy.

Hello @anushbhatia , I am a GSSOC'21 participant and I would like to work on this issue , Can you assign it to me ?
Thanks in advance.

Hello @anushbhatia , I am a GSSOC'21 participant and I would like to work on this issue , Can you assign it to me ?
Thanks in advance.

Check out the interface of Canva. Similar to that we wish everything to be on the left panel.
Assigned for 5 days

@smaranjitghose What is Canva? I understand that I should make it as a block like "Fill" div for example, and put it under the "Fill" div. or am I mistaken?

@smaranjitghose What is Canva? I understand that I should make it as a block like "Fill" div for example, and put it under the "Fill" div. or am I mistaken?

Please Google stuff by yourself. Atleast till some extent. . I don't mind helping out with doubts but these are really trivial ones.
Canva

Dear @smaranjitghose  thank you for the clarification, I have already reached that yesterday but wanted to make sure that you mean the same thing.

So I should do something like blocks on the left and put the shape icons in a new "Shape" block and add the line and arrow icons in the "Stroke Style" block?

Dear @smaranjitghose thank you for the clarification, I have already googled it but wanted to make sure you mean the same thing.

So, Should I do something like that in the left of the photo and put the shapes icons in a new "Shapes" block and add the line and arrow icons in the "Stroke Style" block?

Currently, just add all of them together in the left panel add a heading of shapes to all of them.

@smaranjitghose @anushbhatia I would like to work on this as a part of GSSOC'21. Please assign it to me.

@smaranjitghose @anushbhatia I would like to work on this as a part of GSSOC'21. Please assign it to me.

The recent PR has majorly messed up the sketch page w.r.t scroll option, edge mode, background color, etc.
Those need to be fixed first before handling the UI further. Do you wish to take up issues on those bugs?

I can continue working on the issue, I have just fixed the scroll option and re-added the canvas color option.

I can continue working on the issue, I have just fixed the scroll option and re-added the canvas color option.

Cool. Do give separate PRs for each bug so that it is easier for us to review and we can reward you the points accordingly

Okay Great, Do you want me to change the UI of shapes or is it okay ? and for the Edge mode , Is it working fine and just doesn't appear on the toolbox or what is exactly the problem with it?


Link configuration for reporter.testId and reporter.issue API's

Hey everybody!
I run into a little problem and I hope you can help me solve it.
FRAMEWORK:
WDIO
MOCHA
CHAI
WDIO-ALLURE-REPORTER
When I'm trying to assign test case ID (via reporter.testId(999)) or issue ID (via reporter.issue(111)) the reporter successfully adds corresponding information to Allure report. But when I click the link it navigates me to Allure server IP. Link looks like the folloing example:
http://<IP_ADDRESS>:24240/999  (for reporter.testId(999))
It it very clear for that there should be config property somewhere, intended to regulate this, but I didn't managed to find any information.
Please assist!

And againg it is not about wdio-reporter :)

I didn't managed to find any information.
It is in allure docs. See https://docs.qameta.io/allure/#_links

@BorisOsipov
Thanks!
Okay, I am about to went to bug smb on Allure side)
One more little question. that pattern - related staff. Is it supported by wdio allure reporter? Or this is something to be handled on allure core side?
it appears to me that there should be somkind of API in reporter objet allowing set pattern.

it appears to me that there should be somkind of API in reporter objet allowing set pattern.

@baev can you assist? rigth now reporter just add <label name='issue' value='gh-1212'/> to testcase. How can we pass issue\link pattern?

You can create allure.properties file in results directory and use properties allure.issues.tracker.pattern and allure.tests.management.pattern for patterns, for example:
allure.issues.tracker.pattern: https://example.org/issue/%s
allure.tests.management.pattern: https://example.org/tms/%s

Or you can use full links directly (providing label <label name='issue' value='https://github.com/some/repo/1212'/>).
This is only applied for results in Allure 1 XML format. In new model we moved pattren resolution logic to adaptor side (it is easier for users to configure and in that case each result file can be processed individually that required for realtime reporting)

@baev @BorisOsipov
Thanks guys! It works.
But from my perspective it would be nice if only we could manage these properties from reporter config or something.
Anyway, thanks!

But from my perspective it would be nice if only we could manage these properties from reporter config or something.

Yep, I agree. We are already working on new JS integrations https://github.com/allure-framework/allure-js/


I cannot use beta version.

I ran yarn add react-native-agora@beta , and import from react-native-agora
I got error this
error
[fatal][tid:main]
Metro has encountered an error: While trying to resolve module `react-native-agora` from file
`/Users/yamaguchikeiichi/Downloads/TowerWord/src/component/OgiriPlayer.tsx`, the package
`/Users/yamaguchikeiichi/Downloads/TowerWord/node_modules/react-native-
agora/package.json` was successfully found. However, this package itself specifies a `main`
module field that could not be resolved
(`/Users/yamaguchikeiichi/Downloads/TowerWord/node_modules/react-native-agora/lib/index.js`. Indeed, none of these files exist:

this is react-native-agora directory from node_module. Correct???

fixed in 3.0.1-beta.5


Possible use cases of GROBID without service instance?

I'm trying to use this for a side-project and setting up a server dedicated to GROBID is too computationally expensive for very few use cases. Is it possible to use GROBID TEI extractor as an isolated function which we'd only call when needed, so that is without an instance of GROBID service running?
Thank you!

Hello @yassinetb !
See https://github.com/kermitt2/grobid#demo

Hello @yassinetb !
See https://github.com/kermitt2/grobid#demo

Thank you @kermitt2 for your quick response. I am aware of the demo and have used it for testing purposes. I should have made it clear in my comment that this is for production code, so using the demo is not really feasible. The reason I said "very rare use" is because I am realistic about how many people will actually use my app 😅😅😅

Ah I see !
Well the batch call would be very likely a terrible solution for a case by case usage, because it takes 30s to load the model...
Maybe on a machine with plenty of swap memory, the service could remain in memory, but in practice in the swap... calling the service would be slower but still much faster than an external command call to the batch?


Decode error

Description:
I am attempting to perform a TLS handshake using a PSK cipher (TLS_PSK_WITH_AES_256_CBC_SHA), and I’m encountering issues where the OpenSSL server sends a "Decode Error" alert at the end of the handshake. Additionally, when trying to decrypt the captured trace in Wireshark, only the "Finished" message from the OpenSSL server is being decrypted successfully.
Scenario:
TLS-Attacker Client Command:
java -jar apps/TLS-Client.jar -connect <IP_ADDRESS>:4433 -version TLS12 -config client_config.xml -cipher TLS_PSK_WITH_AES_256_CBC_SHA -debug
OpenSSL Server Command:
openssl s_server -tls1_2 -accept 4433 -nocert -psk<PHONE_NUMBER>63346435653666 -psk_identity Client_Identity -cipher PSK-AES256-CBC-SHA -keylogfile /tmp/.ssl-key.log -no_ticket
client_config.xml

server_config.xml

Observations:

The handshake is initiated successfully, but at the end, the OpenSSL server sends an Alert(Decode Error).

When trying to decrypt the trace in Wireshark, it is only able to decrypt the "Finished" message sent by the OpenSSL server.

Similar behavior is observed when using both TLS-Attacker’s client and server: despite not receiving the Decode Error, none of the Finished messages are decrypted in Wireshark.

In addition, in Wireshark it appears the Decrypted TLS tag and the packet seems to be fine:

Any guidance or support would be greatly appreciated. Thank you!

Hey,
according to your TLS-Attacker command, you are not defining a custom workflow trace. In this case, TLS-Client will only perform a handshake and immediately terminate the connection after receiving the server's Finished message.  The decode error you are observing is likely the result of the improperly terminated TLS session.
To test if you can actually transmit application data you can use the following trace:
<workflowTrace>
    <Send>
        <configuredMessages>
            <ClientHello>
            <extensions>
                <ECPointFormat/>
                <EllipticCurves/>
                <SignatureAndHashAlgorithmsExtension/>
                <RenegotiationInfoExtension/>
                <ExtendedMasterSecretExtension/>
                <EncryptThenMacExtension/>
            </extensions>
            </ClientHello>
        </configuredMessages>
    </Send>
    <ReceiveTill>
        <ServerHelloDone/>
    </ReceiveTill>
    <SendDynamicClientKeyExchange/>
    <Send>
        <configuredMessages>
            <ChangeCipherSpec/>
            <Finished/>
        </configuredMessages>
    </Send>
    <ReceiveTill>
        <Finished/>
    </ReceiveTill>
    <Send>
        <configuredMessages>
            <Application>
                <dataConfig>0A0A546869732069732061206D6573736167652066726F6D20544C532D41747461636B65720A0A</dataConfig>
            </Application>
        </configuredMessages>
    </Send>
</workflowTrace>

You can pass this xml file to TLS-Client.jar with -workflow_input <path to xml>.
You should then see the text This is a message from TLS-Attacker in OpenSSL's CLI output. Note that the connection is still not properly closed. Hence, there should still be an error message below this line and OpenSSL should still issue a decode error alert.

That wasn't my main problem.
I used your workflow adding a close connection alert
<workflowTrace>
    <Send>
        <configuredMessages>
            <ClientHello>
            <extensions>
                <ECPointFormat/>
                <EllipticCurves/>
                <SignatureAndHashAlgorithmsExtension/>
                <RenegotiationInfoExtension/>
                <ExtendedMasterSecretExtension/>
                <EncryptThenMacExtension/>
            </extensions>
            </ClientHello>
        </configuredMessages>
    </Send>
    <ReceiveTill>
        <ServerHelloDone/>
    </ReceiveTill>
    <SendDynamicClientKeyExchange/>
    <Send>
        <configuredMessages>
            <ChangeCipherSpec/>
            <Finished/>
        </configuredMessages>
    </Send>
    <ReceiveTill>
        <Finished/>
    </ReceiveTill>
    <Send>
        <configuredMessages>
            <Application>
                <dataConfig>0A0A546869732069732061206D6573736167652066726F6D20544C532D41747461636B65720A0A</dataConfig>
            </Application>
        </configuredMessages>
    </Send>
        <Send>
        <configuredMessages>
            <Alert>
                <level>warning</level>
                <description>close_notify</description>
            </Alert>
        </configuredMessages>
    </Send>
    <ReceiveTill>
        <Alert>
            <level>warning</level>
            <description>close_notify</description>
        </Alert>
    </ReceiveTill>
</workflowTrace>

And now i don't get the Decode Error, but I still only manage to properly decrypt one Finished Message

I assume this is an issue in Wireshark as OpenSSL is able to process our message correctly. Does it work if you use both OpenSSL s_client and s_server with PSK?


Need to replace Jmeter wget with new path in Module3_FOSS_Java_Manual - Reference_Application_Performance_Tests job

In the jenkins job Reference_Application_Performance_Tests under Module3_FOSS_Java_Manual / Java_Reference_Application path to the Jmeter library needs to be changed as below
Jmeter is currently at 3.3 as per http://jmeter.apache.org/download_jmeter.cgi
and the 2.13 which is used in our jobs are moved to archives https://archive.apache.org/dist/jmeter/binaries/
wget http://www.apache.org/dist/jmeter/binaries/apache-jmeter-2.13.tgz
to
wget http://archive.apache.org/dist/jmeter/binaries/apache-jmeter-2.13.tgz

Hi Sachin
After checking this, could see that the fix should be in the groovy script present in https://github.com/Accenture/adop-cartridge-doa-m3/blob/master/jenkins/jobs/dsl/java_reference_application_jobs.groovy
There already exits a pull request which has the necessary modification
https://github.com/Accenture/adop-cartridge-doa-m3/pull/1
Could you please review that and merge.

Thanks @uptownaravi this has now been merged.


Mistake in "The quick brown fox ..."

The first image should say "The quick brown fox jumps over the lazy dog", otherwise you're missing the "s" ;)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f94d411c-212f-d301-5ed2-4b5cb3e9b897
Version Independent ID: bc4d9a15-03d1-cbc4-1dff-0d44dd1c2b35
Content: Typography in Windows 11 - Windows apps
Content Source: hub/apps/design/signature-experiences/typography.md
Product: uwp
Technology: apps
GitHub Login: @hickeys
Microsoft Alias: hickeys

Either that, or "the quick brown fox jumped over the lazy dog's back"

The designers agree that we should update this image, but it's relatively low priority. It's being tracked internally so I'm going to close this issue even though I haven't actually updated the image. Not really the resolution anyone was hoping for, but there's only so much I can do.


Creating & Playing Single Audio From Multiple Assets

Hi,
I have multiple sound files in assets folder. Currently, I can play them by creating a Timer object.
I will give a concrete example to explain it more clearly. Let's say I have A, B, C, D, E and F asset files. And assume I am playing some of these audio files at 1 second interval using the Dart's Timer.periodic function.
An example schedule:
0 sec: Play A, C, D simultaneously
1 sec: None (Silence)
2 sec: Play B, F simultaneously
3 sec: Play B, E simultaneously
4 sec: None (Silence)
5 sec: Play A, C simultaneously
...
Currently, I am using separate AudioPlayer instances for each sound but I don't want this. I know in advance what sounds to play and when.
So, I want to create a single combined audio programmatically beforehand. Then I will play that combined audio playback with using single AudioPlayer instance. I don't have much of a performance problem with "low latency" mode at the moment, but the playbacks I've created will become much more complex. So, it is better for me to construct a single audio.
As far as I investigated the library, this might be possible by creating a single Uint8List from bytes of multiple sounds. But I couldn't figure out

how can I combine byte arrays of sounds playing at the same time and
how can I create a 1 second long silence data programmatically.

Could you help me on this case? Other than this, I would like to know if there are other methods to do it.

I think this is out of scope of this library. You either have to use multiple instances of AudioPlayers or generate your own source.
I found this maybe you can transfer it to dart somehow:
https://stackoverflow.com/a/33913403/5164462
I close this, as it's not the task of audioplayers to generate sounds :)


Fix test in 2.12.2

The p25 test of EulerTests seems not to compile anymore in 2.12.2 (haven't investigated why... - changes in the typer?). This PR fixes it, and makes the CI use 2.12.2.

Flaky flake is flakey


Ingress not working when rbac.namespaced=true

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
10.3.4
What version of Traefik are you using?
2.5.1
What did you do?
We deployed latest helm chart and traefik version on kubernetes 1.22 with rbac.namespaced: true
helm install traefik traefik/traefik --set rbac.namespaced=true

What did you see instead?
We got an error in traefik log:
E0921 14:07:54.739657       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.0/tools/cache/reflector.go:167: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s │
│ .io is forbidden: User "system:serviceaccount:default:traefik" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope

Routing does not work.
What is your environment & configuration?
We tested on KinD with kubernetes 1.22.1
Additional Information
We also tested with traefik 2.5.3 with same result.

Rightm I did notice this a while ago, and package that fix into a PR that was meant for something else ...
https://github.com/traefik/traefik-helm-chart/pull/337
You're looking for this:
https://github.com/traefik/traefik-helm-chart/pull/337/files#diff-f4430485e5002c71e33daa985c34e0fe4e4738a271c697ba0b1aaaba1718e041
And that one.
https://github.com/traefik/traefik-helm-chart/pull/337/files#diff-7999c32e3d6ec3ed70ac9537b6b3b8d3d298fbf21f50609f9377b4ecc2de7ce3

Perfect, that's exactly what I'm looking for. Thanks for your feedback.
While looking deeper in the problem we also found, that the current k8s client api (or k8s api ?) didn't provide the possibility to watch incressClass on namespace level (https://github.com/kubernetes/client-go/issues/987) and therefore traefik (and other IC) have to watch them on cluster level which requires ClusterRole + ClusterRoleBinding, regardless of a namespaced flag.

IngressClass are cluster scoped objects.
When issuing a command (get/list/watch/create/...), you do need those permissions at the cluster level. This is not a bug.
Same goes for all cluster scoped objects: StorageClasses, PersistentVolumes, APIServices, ValidatingWebhookConfigurations, ...

IngressClass are cluster scoped objects. When issuing a command (get/list/watch/create/...), you do need those permissions at the cluster level. This is not a bug. Same goes for all cluster scoped objects: StorageClasses, PersistentVolumes, APIServices, ValidatingWebhookConfigurations, ...

So what's the purpose of rbac.namespaced=true? Is there a scenario where it can be used?

what's the purpose of rbac.namespaced=true?
Limits the scope of Ingresses that a given Traefik controller may use/write.
Limit the scope of Services that a given controller may expose/communicate with.

if controller needs to read cluster scoped objects ... You need to grant that access, with a ClusterRoleBinding. Which is fixed by that PR.
Doesn't have any impact on namespace-scoped resources.

Is there a scenario where it can be used?
Is there a scenario where it can't?
With or without ingress classes, you can scope Traefik to a given namespace.
Or you could deploy a single Traefik for your whole cluster.

if controller needs to read cluster scoped objects ... You need to grant that access, with a ClusterRoleBinding. Which is fixed by that PR.

So I'm missing something here...according to the PR you linked, with rbac.namespaced=true the ClusterRole and ClusterRoleBinding are created so that traefik can read the cluster-wide IngressClass objects, so everything should work? Because I just tried with the 10.7.1 helm chart and if I use rbac.namespaced=true I still get the OP error. Is the change still not merged?


PSR2 compliance.

Looks good.

I haven't setup the travis build to do phpcs checks on test folder as it still has lot of failure which require manual fixing and personally I don't want to spend time right now fixing them.


010 editor expiry

The evaluation period seems to be 30 days any way to extend it?

Hi @RyanNgCT, FLARE-VM do not offer a free version of 010 editor. We only provide a trial version. You can purchase a license from their official website here: https://www.sweetscape.com/010editor/


Win shared gs api

This is a follow up from https://github.com/grpc/grpc/pull/35248
I've retained the changes to the CMakeLists.txt template file which make the macro definitions for import/export more reliable, but it turns out no further annotations are needed to get this to compile if I fall back to the slightly less efficient non-explicit DLL binding for client code.
Note that as before these changes do not affect the way the non-Windows, non-shared builds work.

@yashykt are you able to approve this change?


Fix create genesis

Adds commit:
Fix genesis sections #958

@zxcat  you can merge
and you should merge if you see it :)


Map is not Loading after once it is loading partially not displaying full map.

ng-map zoom="8"
center="{{vm.TownshipBoundaryPoints[1]}}"
map-type-id="TERRAIN"
style="width:1200px;height:600px;"
shape name="polygon"
path="{{vm.TownshipBoundaryPoints}}"
geodesic="true"
stroke-color="#FF0000"
stroke-opacity="1.0"
stroke-weight="2"
fill-color="#FF0000"
fill-opacity="0.35"
shape
ng-map
function _getTownshipBoundaryPointById(StateId,TownshipId) {
debugger;
townshipService.getTownshipBoundaryPointById(StateId,TownshipId).then(function (response) {
var arr = [];
response.data.forEach(function (element) {
                var array = [];
                array.push( element.Latitude,element.Longitude);
                arr.push(array);
            });
            vm.TownshipBoundaryPoints=arr;
        }, function (error) {
        });
    }

==================================================
This is my code first part is how i am displaying in html
Second part is my method for getting all the points from service
I don't know how to update the view after getting the response from service. Is there a way to reload the map again.
Can any one help to How to implement properly Map.

Closing

Could you follow the question properly
Duplicate of https://github.com/allenhwkim/angularjs-google-maps/issues/82


URL to send the video "recordings" via Telegram

Hi,
I cannot retrieve the video "recordings" to be sent via telegram.
Before with the clips I used this code:
date:
video:
- url:> -
http://192.168.1.xxx:5000/clips/ {{
trigger.payload_json ['after'] ['camera']}} - {{
trigger.payload_json ['after'] ['id']}}. mp4
Has anyone managed to find the solution?
Thanks

Use http://192.168.1.xxx:5000/api/events/{{trigger.payload_json ['after'] ['id']}}/clip.mp4


[zh] Add a blog: 2024-12-17-api-streaming/

Add zh text to this blog:
content/zh-cn/blog/_posts/2024-12-17-api-streaming/index.md

See preview

The original is not a draft now. This PR has updated the date involved in title, pr-desc, and commit.
/unhold

/lgtm


[Data] Add ability to calculate and capture data distribution

Is your feature request related to a problem? Please describe.
For certain scenarios, e.g. classification models, the distribution of the data is important as it may greatly affect the model performance.
Describe the solution you'd like
It would be cool if we could have the ability to calculate and track the data distribution of an IDataView (e.g. number of unique values in each column).

@aslotte , Should this be performed as part of LogData for each column in DataView or a seperate operation after LogData for columns that required to be investigated?

Given that this may only make sense for certain ML tasks, e.g. classification etc, let's add it as a separate method LogDataDistribution. E.g. for regression and forecasting tasks we probably don't care too much about doing this, while for classification it's super important.

@aslotte , I am thinking of a separate entity for DataDistribution and will be  part of the DataColumn as a property
public List Distribution { get; set; } = new List();
which will store each unique value for the column along with count of that value. Do you think if that's ok ?
     public Guid DataColumnId { get; set; }

    public string Value { get; set; }

    public int Count { get; set; }

I think you're on the right track @AnoojNair, I can't think of a better solution :)


Remove version: NumeRe.NumeRe version 1.1.3

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/numere/files/Stable Release/numere-win-v113.exe/download
Status Code: 200
(Automated message - build 896)

Close with reason: Package still available.;


[Tracking Issue] Hardware enablement policies in nixpkgs

Issue description
We have https://github.com/NixOS/nixos-hardware/ which is a repo where everyone dumps pieces of configurations they find to make their computer do better in their view.
In the past, that repo was merged inside nixpkgs, then reverted, in the context of https://github.com/NixOS/nixpkgs/pull/91160.
Furthermore, nixos-generate-config is not always aware of potential hardware profiles to apply, see https://github.com/NixOS/nixos-hardware/issues/49 for ideas, which impedes the discoverability sometimes.
We discussed on Matrix at https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$2Tu2fydLwl5XTeuHQxOrqGa0TAn0F6ft4e6fdylQaAU?via=lossy.network&via=matrix.org&via=nixos.dev "what if we merged the repo again" and we came to the conclusion very quickly this was not an option.
Here's a summary of the discussion:

Kernel maintainers in nixpkgs are not super comfortable with forked kernels inside of nixpkgs: @alyssais, @K900 and I prefer a hard rule "no forked kernel" even if it had permitted hardware enablement.

A code owner of hardware/, even multiples to ensure a high quality level, on par with Jovian or Asahi

For something to be present in hardware/, the intention of their vendor/author is that it should be upstreamed as soon as possible

Explicit traces of good maintenance from the midstream (Asahi/Collabora/Jovian) must be apparent

We also mentioned that CI in nixos-hardware is lacking and a better separation of packages/modules would help

@alyssais is against ideally any forked project for hardware enablement

The previous points do not cover things like just tweaking a configuration with existing packages even if the configuration could be upstreamed and thus no tweak would be required

Open questions are also how to reconcile diverging outcomes and whether we should have NixOS module code to handle things like "I want to optimize my HW for power", "I want to optimize my HW for performance", etc.

Raito's proposal
My proposal would be to formalize better a policy in Nixpkgs about the hardware enablement here, take ownership of that repo and start to look if some stuff makes sense to move over from nixos-hardware to here.
In parallel, we can help the nixos-hardware project to get CI and help with the structure.
Finally, I'd like to try to close the "auto generate" profile issue with nixos-generate-config, during the conversation: https://git.numtide.com/numtide/nixos-generate-facts was mentioned.
cc @samueldr @zimbatm

Reading trough the lines, the problem you want to solve is to improve the quality of nixos-generate-config. Is that correct?

Reading trough the lines, the problem you want to solve is to improve the quality of nixos-generate-config. Is that correct?

Not really, this is about hardware enablement policies in general, nixos-generate-config improvements would be a step / sub-issue of this one, yes.
At least, having ngc able to add more known profiles/tweaks based on nixpkgs and maybe... nixos-hardware with a warning this comes from a community source with less quality standards, etc.

I definitely agree with the sentiment of moving some things from nixos-hardware to nixpkgs, maybe a first good candidate would be the Framework module? It seems pretty well written, also how would the structure of this work? Could nixos-generate-config automatically determine which computer the user has and install that specific profile for their machine?

I personally didn't want to enable everything suggested in nixos-hardware/ automatically. Instead I went through all the options manually and copied the ones I wanted.
An idea I wanted to explore was to automatically generate the merged configuration from all files for the particular hardware I'm interested in so I didn't have to follow all the includes.
Maybe we can apply that here as the first step: Automatically deploy a website based on the repo where all suggested configuration for each hardware profile will be available to the users with search.  nixos-generate-config can then have a comment at the end linking to this website saying: "search for your hardware here for more relevant config options".

I personally didn't want to enable everything suggested in nixos-hardware/ automatically. Instead I went through all the options manually and copied the ones I wanted.
An idea I wanted to explore was to automatically generate the merged configuration from all files for the particular hardware I'm interested in so I didn't have to follow all the includes.
Maybe we can apply that here as the first step: Automatically deploy a website based on the repo where all suggested configuration for each hardware profile will be available to the users with search. nixos-generate-config can then have a comment at the end linking to this website saying: "search for your hardware here for more relevant config options".

I mean that can be fixed, nixos-hardware can be the "staging" repo before merging stuff into nixpkgs, that way we can make sure everything is unopinionated, and then optimally we would have those more opinionated things as an opt-in somehow.

Kernel maintainers in nixpkgs are not super comfortable with forked kernels inside of nixpkgs: @alyssais, @K900 and I prefer a hard rule "no forked kernel" even if it had permitted hardware enablement.

A code owner of hardware/, even multiples to ensure a high quality level, on par with Jovian or Asahi

Would Asahi support be included? Imo, it would be great and I would even be willing to maintain that inside of Nixpkgs. However, in Asahi's current state, their kernel is a hard requirement. Would there be exceptions to the forked kernel rule?

Asahi would be included under nixos-hardware, but not as an "official package".

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/make-nixos-hardware-more-prominent/46657/7


Extract declaring a sort alias into a pub fn

This PR is another follow-up to #56  and #62, which extract the behavior to name a sort, like (sort StringSet (Map Var i64)). The function declare_sort was already taken, to add a user-defined sort, so I wasn't sure what to call this. Happy to rename if you have other suggestions.

Perhaps combine it with declare_sort? It could take an option Expr or something.

@mwillsey Sounds good. I also added error handling for it not finding a presort and changed the declare_sort to re-use the  add_arcsort method which duplicates some of the logic there. I moved the error handling into add_arcsort to support this.
Let me know how this looks!


[Market] check the weight for place storage order

looks fine. Need to refine the weight for calculate reward


Feature: Reorder tabs on contributor profile to Contributions, Recommendations, and Highlights

Suggested solution
Change the order

Closed by https://github.com/open-sauced/app/pull/3709


setting web config to no-log, cf h

This PR stops the role from outputting potentially sensitive configuration at the cli where Ansible is run from. (I generally log this output, and don't want e.g. public-user password appearing in log files).
Tested on https://github.com/openmicroscopy/management_tools/pull/352#issuecomment-291193765 and previous runs of this role for ns-web.
You can review the output of https://github.com/openmicroscopy/management_tools/files/890668/ns-web-provision_20170403-160536Z.txt (linked to on the pr linked above) to see that despite the command ansible-playbook --diff being run,  the web config changed, but no diff is recorded:
RUNNING HANDLER [openmicroscopy.omero-web : omero-web rewrite omero-web configuration] ***
changed: [ns-web.openmicroscopy.org]

RUNNING HANDLER [openmicroscopy.omero-web : omero-web restart omero-web] *******
changed: [ns-web.openmicroscopy.org]

cf
https://dantehranian.wordpress.com/2015/07/24/managing-secrets-with-ansible-vault-the-missing-guide-part-1-of-2/
Note: ansible-role-omero-server could probably do with this as well.

As mentioned in slack I think this should not be part of the role since it's going to hide all config changes. I reckon you should either avoid using verbose/diff, or create a separate config file in an independent playbook task.

Not sure, @manics. I personally err on the side of caution - this way we know sensitive data won't be leaked to logs / terminals, and we can be sure it's set up like that for consumers of this role.
If someone reuses this, and logs ansible output like I do, they may inadvertently end up with config on local disk or leaked somewhere they weren't expecting it, hence it's my preference to add no_log for this.
Of course, it's up to others to decide how the openmicroscopy version of the role works. Would it be feasible for the openmicroscopy version to include an extra no_log task for any sensitive key/value pairs as you suggest I do?

And making it configurable?
# (v)joshuas-mbp:tmp jamoore$ ansible-playbook -i localhost play.yml
 [WARNING]: Host file not found: localhost

 [WARNING]: provided hosts list is empty, only localhost is available

PLAY [localhost] ***************************************************************

TASK [setup] *******************************************************************
Tuesday 04 April 2017  07:02:04 -0400 (0:00:00.019)       0:00:00.019 *********
ok: [localhost]

TASK [test] ********************************************************************
Tuesday 04 April 2017  07:02:04 -0400 (0:00:00.423)       0:00:00.443 *********
ok: [localhost] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0

Tuesday 04 April 2017  07:02:04 -0400 (0:00:00.018)       0:00:00.462 *********
===============================================================================
setup ------------------------------------------------------------------- 0.42s
test -------------------------------------------------------------------- 0.02s
(v)joshuas-mbp:tmp jamoore$ ansible-playbook -i localhost play.yml   -e "disable_log=false"
 [WARNING]: Host file not found: localhost

 [WARNING]: provided hosts list is empty, only localhost is available

PLAY [localhost] ***************************************************************

TASK [setup] *******************************************************************
Tuesday 04 April 2017  07:02:15 -0400 (0:00:00.028)       0:00:00.028 *********
ok: [localhost]

TASK [test] ********************************************************************
Tuesday 04 April 2017  07:02:16 -0400 (0:00:00.442)       0:00:00.471 *********
ok: [localhost] => {
    "msg": "test"
}

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0

Tuesday 04 April 2017  07:02:16 -0400 (0:00:00.042)       0:00:00.513 *********
===============================================================================
setup ------------------------------------------------------------------- 0.44s
test -------------------------------------------------------------------- 0.04s
# (v)joshuas-mbp:tmp jamoorecat play.yml
---
- hosts: localhost
  vars:
      - disable_log: true

  tasks:
      - name: test
        no_log: "{{ disable_log }}"
        debug:
            msg: test

There's no easy way to disable logging for single keys/values. It could be made configurable, but:

it increases the complexity in the role. Part of the idea behind adding the config/ dir was to reduce complexity in the role by allowing users to manage configuration independently of this role.
what benefit does the combination of enabling diff but disabling output offer in this role?

what benefit does the combination of enabling diff but disabling output offer in this role?
Who knows - that is a standard command-line I'd use to execute ansible-playbook now you taught me the option exists. I don't mean to suggest it's specific to this playbook or role.

Would adding no-log at the playbook level work instead? If not make it configurable here.

Can this be closed?

Perhaps to be included in another PR when it's made configurable.


Fix conflict count on non top-level directory

There may be better solutions for this but this one does the trick anyways :)
Fixes #150

As soon as you said the cause, I can't believe I did not notice the pattern. I spend a lot of time nested in directories of a monorepo.
Thanks for this!


Introduce GRAPH.DELETE

Similar to FalkorDB-py add API for deleting a graph.

Sorry, haven't noticed that this functionality already exists.


Remove locked option in std_cargo_args if CPU.arch is arm64

There are lots of errors in formulae depending rust on arm64
because homebrew installs older dependent cargo packages.
It is because std_cargo_args uses locked option and Cargo.lock.
https://github.com/Homebrew/homebrew-core/pull/68089

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
 If so, then I don't think this is acceptable. Taking out the --locked flag means that cargo build can use any dependency it wants, and I don't think we like that in Homebrew. It also makes builds non-reproducible.

Doesn't the --locked flag require that cargo build use the dependencies declared in Cargo.lock? If so, then I don't think this is acceptable. Taking out the --locked flag means that cargo build can use any dependency it wants, and I don't think we like that in Homebrew. It also makes builds non-reproducible.

Doesn't the --locked flag require that cargo build use the dependencies declared in Cargo.lock?

Yes. cargo install *std_cargo_args will use Cargo.lock because using locked flag.
But will Homebrew require all formulae depending rust (about 120 formulae) to update Cargo.lock if this PR is not accepted?

Doesn't the --locked flag require that cargo build use the dependencies declared in Cargo.lock?

Yes. cargo install *std_cargo_args will use Cargo.lock because using locked flag.
But will Homebrew require all formulae depending rust (about 120 formulae) to update Cargo.lock if this PR is not accepted?

Do we know that all of them fail due to stale Cargo.lock files? If these files are stale, they should be cutting new releases anyway. Happy to help with filing issues where we need to, though.
That said, I'm open to hearing others' opinions on this.

Do we know that all of them fail due to stale Cargo.lock files? If these files are stale, they should be cutting new releases anyway. Happy to help with filing issues where we need to, though.
That said, I'm open to hearing others' opinions on this.

If these files are stale, they should be cutting new releases anyway.

This is my view as well. If the build is failing on ARM due to older dependencies, then affected users should create an issue upstream (making them aware).
As @carlocab mentioned, the --locked flag ensures our builds are reproducible and this is desirable within the context of Homebrew. If the build fails because of Cargo dependencies, it's upstream's responsibility to fix it (though we can always create issues/PRs to help them along).
For what it's worth, I pushed to add the --locked flag to Rust formulae (#46025) in the past and I feel the reasoning there still applies.

If these files are stale, they should be cutting new releases anyway.

This is my view as well. If the build is failing on ARM due to older dependencies, then affected users should create an issue upstream (making them aware).
As @carlocab mentioned, the --locked flag ensures our builds are reproducible and this is desirable within the context of Homebrew. If the build fails because of Cargo dependencies, it's upstream's responsibility to fix it (though we can always create issues/PRs to help them along).
For what it's worth, I pushed to add the --locked flag to Rust formulae (#46025) in the past and I feel the reasoning there still applies.

Do we know that all of them fail due to stale Cargo.lock files?

No. I confirmed some errors in formulae was because of Cargo.lock but not all.

Do we know that all of them fail due to stale Cargo.lock files?

No. I confirmed some errors in formulae was because of Cargo.lock but not all.

we have to create Issues/PRs divide by hands

Yes, I agree that we need an intelligent way of dividing the work on this. I think we could try to enlist user help by opening an issue asking for help to check if cargo build works on a Rust-based formula without the --locked flag but doesn't work with it.
Not sure how to give those users a version of Rust to test with other than asking them to compile the version of the formula in your PR, which would be a pretty big barrier to getting help. Will the above idea work if someone installed a version of a Rust compiler using rustup instead?

we have to create Issues/PRs divide by hands

Yes, I agree that we need an intelligent way of dividing the work on this. I think we could try to enlist user help by opening an issue asking for help to check if cargo build works on a Rust-based formula without the --locked flag but doesn't work with it.
Not sure how to give those users a version of Rust to test with other than asking them to compile the version of the formula in your PR, which would be a pretty big barrier to getting help. Will the above idea work if someone installed a version of a Rust compiler using rustup instead?

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM. Then, we compare the CI run from this to the one before this change and see which formulae have been fixed by dropping the --locked flag.
I think this should identify the formulae with state lock files. We can then use that information to open the appropriate upstream issues.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM. Then, we compare the CI run from this to the one before this change and see which formulae have been fixed by dropping the --locked flag.
I think this should identify the formulae with state lock files. We can then use that information to open the appropriate upstream issues.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Just to be clear, I believe this suggestion was only intended as a way of identifying formulae that fail to build due to the dependencies in the Cargo.lock file. I don't believe @carlocab is suggesting that we disable the --locked flag as a workaround for ARM formulae with related build issues.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Just to be clear, I believe this suggestion was only intended as a way of identifying formulae that fail to build due to the dependencies in the Cargo.lock file. I don't believe @carlocab is suggesting that we disable the --locked flag as a workaround for ARM formulae with related build issues.

Oh, I don't mean it as a work-around, since I don't think formulae that need the --locked flag dropped should be merged. I just intended it as a way of identifying formulae with stale lock files.

Oh, I don't mean it as a work-around, since I don't think formulae that need the --locked flag dropped should be merged. I just intended it as a way of identifying formulae with stale lock files.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Just to be clear, I believe this suggestion was only intended as a way of identifying formulae that fail to build due to the dependencies in the Cargo.lock file. I don't believe @carlocab is suggesting that we disable the --locked flag as a workaround for formulae with related build issues on ARM.

yeah, I am the same page of not disabling --locked, in fact, I did insist to include --locked flag into the rust CI action a while ago.

Alternatively, we could script replacing std_cargo_args in all Rust-based formulae to something that leaves out the --locked flag on ARM

yeah, we can do that as workaround or submit patches to the upstream.

Just to be clear, I believe this suggestion was only intended as a way of identifying formulae that fail to build due to the dependencies in the Cargo.lock file. I don't believe @carlocab is suggesting that we disable the --locked flag as a workaround for formulae with related build issues on ARM.

yeah, I am the same page of not disabling --locked, in fact, I did insist to include --locked flag into the rust CI action a while ago.

We definitely want to keep dependencies pinned, for rust like for everything else in homebrew. Reproducible builds are important.

We definitely want to keep dependencies pinned, for rust like for everything else in homebrew. Reproducible builds are important.

Thank you for your replying.
I will fix scripts replacing std_cargo_args in all Rust-based formulae.
https://github.com/Homebrew/brew/pull/10205#issuecomment-753526545

Thank you for your replying.
I will fix scripts replacing std_cargo_args in all Rust-based formulae.
https://github.com/Homebrew/brew/pull/10205#issuecomment-753526545

@shigemk2 the actual solution is for these formulas to ship a new release with up-to-date dependencies. If we remove the lock files, we might be shipping things that aren't working, or will break, and we have no control. Each upstream should determine what they want as dependencies, and if those aren't compatible with Apple Silicon, then it's simply not supported on Apple Silicon.

@shigemk2 the actual solution is for these formulas to ship a new release with up-to-date dependencies. If we remove the lock files, we might be shipping things that aren't working, or will break, and we have no control. Each upstream should determine what they want as dependencies, and if those aren't compatible with Apple Silicon, then it's simply not supported on Apple Silicon.

@fxcoudert don't worry, that's just a temporary change in order to identify the rust-based formulae with stale lock files.
See https://github.com/Homebrew/brew/pull/10205#issuecomment-753526545

@fxcoudert don't worry, that's just a temporary change in order to identify the rust-based formulae with stale lock files.
See https://github.com/Homebrew/brew/pull/10205#issuecomment-753526545


[BUG] Docker image on demo web apps does not get refreshed despite successful publish

Willingness to contribute
Yes. I can contribute a fix for this bug independently.
Feathr version
0.7.0
System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.0):
Python version:
Spark version, if reporting runtime issue:

Describe the problem
The docker image version on webapps does not get updated despite a successful nightly push and pointing to dockerhub image.
Tracking information
No response
Code to reproduce bug
No response
What component(s) does this bug affect?

[ ] Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
[ ] Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
[ ] Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
[ ] Feature Registry Web UI: The Web UI for feature registry. Written in React

Manually verified that docker tag is the latest from dockerhub on demo apps.


next_time of Continuous Target Rate is None when on

Describe the bug
When on, the next_time attribute of a Continuous Target Rate binary sensor entity is None.
Target Rate configuration:
Hours: 1.5
Mode: Continuous
Minimum start time: 06:00
Maximum end time: 17:30
Reproduction steps

Add target rate sensor with above configuration
Wait until the binary sensor entity turns on
Note that the next_time attribute of the binary sensor entity is None

Expected behaviour
That the next_time attribute is populated with the next cheapest period start time.
Tariff Code
E-1R-AGILE-FLEX-22-11-25-C
Integration Version
9.1.0
Home Assistant Version
2023.11.2
Fresh Install?
Fresh install
Home Assistant Logs
Log at 06:00 when sensor was on:
2023-12-05 06:00:58.769 DEBUG (MainThread) [custom_components.octopus_energy.target_rates.target_rate] Updating OctopusEnergyTargetRate dishwasher_early
2023-12-05 06:00:58.770 DEBUG (MainThread) [custom_components.octopus_energy.target_rates.target_rate] calculated: True

Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Hello. This is by design as per the docs, this is only populated if there are further periods for the current 24 hour period. Because you have a continuous sensor target rate all periods will be a single block and therefore this will not be set when on.
It will only be set if 1) the target rate sensor has yet to come on during the 24 hour period or 2) you have an intermittent sensor and have not entered the final period.

Apologies, I missed a rather important detail -
Re-evaluate multiple times a day: True

Given this setting, I expected that there would be additional periods in the day (and you can see there are in the above screenshot).

I'ev updated the docs. Even in this case, it won't be populated until the target times have been re-evaluated.

I think it would also be worth clarifying this behaviour in the Rolling Target / Re-evaluate multiple times a day doc section as well. It's not obvious that "rolling" / re-evaluation only occurs after the next cheapest period has passed.

I will update the docs


Add AlibiGhazi to Contributors list

@AlibiGhazi-dev, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


React-Native 0.54.4 Problem

Hello.
We've worked with this plugin perfectly for the past months with my App in React Native 53.3 or lower. Recently, we have had to upgrade our React-Native version, so, we've upgraded version per version for testability and stability (f.e. 53.3 to 54.0, 54.0 to 54.4, 54.4 to 55 and so on).
However, we are currently stuck on React Native 54 because we've encountered Runtime errors preventing the App from executing correctly on Android as it crashes as soon it gets past the Splash screen. The error preventing the App from executing seems to be related to this plugin and it is:
ReactClassInterface: You are attempting to define 'UNSAFE_componentWillMount' on your component more than once. This conflict may be due to a mixin.
The problem occurs only on Android, when the line is present in any Container/Component and it does not matter if we've use the NestedScrollView component in the render:
import NestedScrollView from 'react-native-nested-scroll-view';
Our environment as right now is:
"react": "^16.3.0-alpha.1",
"react-native": "0.54.4",
"react-native-nested-scroll-view": "6.0.1"
Like you can see we are using the 6.0.1 version recommended for React Native versions lower than 0.56. Also, we've followed carefully the installation steps provided in the README.
Thank you for any help.

Hi,
I am still not sure what is causing it, but it seems related to the react 16.3 version due its new lifecycle API, or an alpha release of react that you are using
see https://reactjs.org/blog/2018/03/29/react-v-16-3.html
In fact the 6.0.1 was released in January 7 and react 16.3 was only relased at the end of the march, so i wasn't be able to supported that at the time of course.
I know that there are required react versions to work with react-native, but i don't know which versions is been required now, but i don't think you should use an alpha release of react 16.3.0,
This is supposed to mostly occurs on ios as well.

Hi,
In iOS the plugin reverts back to ScrollView, so it's not supposed to have this error, right? For us, it is working properly.
I'll try to update the React version and see what happens. I'll let you know what I find out.

I literally forgot this project is android only, sorry 😂
Let me know if you got it.

Hi,
I followed your advice and updated my version of React to 16.3.0 and 16.5.0. Sadly, none solved the problem.
I investigated a little bit more about the issue and the problem comes when the creating the React class for ScrollView on the lib/NestedScrollView.js file, because of importing the mixins of the ScrollResponder. I tried to remove the mixins import and try to rewrite each used function in the ScrollView class that is in the process of creating, but it got way complicated.
Is there something else you would advice doing? Aside from keep updating our version of ReactNative (we will definitely do it, just have to go version by version and test each one).
Thanks in advance.

The NestedScrollView.js is just a fork from the original ScrollView.js, which uses that mixin
https://github.com/facebook/react-native/blob/master/Libraries/Components/ScrollView/ScrollView.js#L553
The mixing is required to make the ScrollView work, does the original ScrollView also gives you that error as well?

Hi, sorry for the delay.
We're still having the issue and we're giving up on the update to React Native 0.54.4. We're trying to update to 0.56 where the ReactNative ScrollView works as we want and, in worst case scenario, your plugin will work too.
To answer your question, the original ScrollView from ReactNative 0.54.4 does not give any errors whatsoever, I don't get it.
Thanks for everything


Save execution namespace in system metadata

TL;DR
Save execution namespace in system metadata
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
N/A see summary
Tracking Issue
fixes https://github.com/flyteorg/flyte/issues/3705
Follow-up issue
NA

PTAL @pmahindrakar-oss


Failed attempts on macOS

Hi,
i tried two read-only files from a qcow2-formatted QEMU-file.
(1) tried your server component ::
./server --size 1000 /Volumes/backup/Downloads/qemu/raspios-bookworm-armhf-lite.img
Since on OSX i can't sudo modprobe nbd or i don't know what to do instead - since you mention that your server runs on macOS (true) and your client can connect to it (great, but how ? Pls provide a example).
(2) tried the qemu-nbd-server to provide the image via a file-socket (qemu-nbd -c on macOS does not support /dev/nbd), so i tried ::
qemu-nbd --fork --persistent --shared=5 --socket=/Users/asc/sock --read-only --format=qcow2 /Volumes/backup/Downloads/qemu/rpi/bookworm.qcow2
Both did not work. I could try to convert the image into the vmpk-format and then mount/access it using maybe VMWare or VirtualBox. Any ideas what i'm missing here ?
regards, Andreas

This project is intended more as a demo of nbd than anything else, so I'm not sure it will help you.
As far as (1) goes, the README might be a bit misleading. There is no kernel support for nbd on macOS, which is what the client binary needs to work. What you should be able to do (but there are no examples or even tests in this project) is run the server and write a Rust program that interacts with it from userspace. This doesn't create a block device - it just gives you a Rust struct Client whose methods interact with the server. I can't think of a good reason to do this other than to test the client and server.
I've never used qemu-nbd but it also can't provide a block device on macOS because there's simply no kernel feature for it.


Fixed link to SPDX identifiers

The currently URL in 3.1.0 is broken, and this looks like the closest guess at what it should link to now.

Although this actually updates a deployed specification, I believe we have precedent to allow these kind of updates because they do not change the semantics of specification.


How to label "unknown faces" with DeepFace.find(...)

Hi!
I'm testing this library on face recognition with a database of two people (100 image for each), I used this method:
df = DeepFace.find(img_path=target, db_path="database", enforce_detection=False, model_name="VGG-Face",
                       model=model, distance_metric="cosine")

and it works well when I use people known to the database as target.
But, if I use a face of a person that is not in the database, how can I label it as "unknown"?
I've tried to implement an if condition with a threshold: if the distance is greater than x mark the face as unknown.
There is a better way to do this?
How can I know that the target face is not in the database?
btw awesome library! 👍

if the returned data frame has size of 0, then no matches
if df.shape[0] > 0:
   print("matched found: ", df.head())
else:
   print("no matches")

if the returned data frame has size of 0, then no matches
if df.shape[0] > 0:
   print("matched found: ", df.head())
else:
   print("no matches")

if the returned data frame has size of 0, then no matches
if df.shape[0] > 0:
   print("matched found: ", df.head())
else:
   print("no matches")

Yes.., I've figured that out later... thank you for your reply! 💯

if the returned data frame has size of 0, then no matches
if df.shape[0] > 0:
   print("matched found: ", df.head())
else:
   print("no matches")

Yes.., I've figured that out later... thank you for your reply! 💯


Get mkdocs working in our Travis environment

@mfelsche yeah this is definitely very busted at this moment. :(

For some reason, Travis is using Python 2.7.3. MkDocs 1.0 requires Python 2.7.9 or >=3.4.
We should use Python 3 to build mkdocs with Travis.

The following changes seem to work for me:
diff --git a/.travis_commands.bash b/.travis_commands.bash
index d0181eb0..a032a071 100644
--- a/.travis_commands.bash
+++ b/.travis_commands.bash
@@ -204,9 +204,15 @@ ponyc-build-packages(){
   make CC="$CC1" CXX="$CXX1" verbose=1 arch=x86-64 tune=intel package_name="ponyc" package_base_version="$(cat VERSION)" deploy
 }

+install-python3(){
+  echo "Installing Python 3 and pip..."
+  sudo apt-get update
+  sudo apt-get install -y python3-pip
+}
+
 ponyc-build-docs(){
   echo "Installing mkdocs and offical theme..."
-  sudo -H pip install mkdocs-ponylang
+  sudo -H pip3 install mkdocs-ponylang

   echo "Building ponyc docs..."
   make CC="$CC1" CXX="$CXX1" docs-online
diff --git a/.travis_script.bash b/.travis_script.bash
index 3a7a494b..fe14ff8f 100644
--- a/.travis_script.bash
+++ b/.travis_script.bash
@@ -57,6 +57,7 @@ case "${TRAVIS_OS_NAME}" in
     if [[ "$TRAVIS_BRANCH" == "master" && "$RELEASE_DEBS" != "" && ( "$TRAVIS_EVENT_TYPE" == "cron" || "$TRAVIS_EVENT_TYPE" == "api" ) ]]
     then
       # verify docs build first
+      install-python3
       ponyc-build-docs
       # now the packaging
       "ponyc-build-debs-$RELEASE_DEBS" master
@@ -105,6 +106,7 @@ case "${TRAVIS_OS_NAME}" in
       build_appimage "$(cat VERSION)"
       ponyc-kickoff-copr
       ponyc-build-packages
+      install-python3
       ponyc-build-docs
       ponyc-upload-docs
     fi

I have this working with Python 2...
however...
Building ponyc docs...
// -> Makefile:263: *** No LLVM installation found!.  Stop.

@mfelsche @winksaville @sylvanc it looks like the LLVM change we merged breaks building on Travis?

Interesting. Only the 3.9.1 release build gets broken.
This comes up in the other builds though...
Makefile:316: WARNING: Unsupported LLVM version: 5.0.0git-929163d
Makefile:317: Please use LLVM 3.9.1

@EpicEric ya i eventually realized the 1.0.4 needs python version greater than what trusty has by default.

I will try around today using python3 as @EpicEric suggested, sorry for the confusion this caused.


Cannot generate thumbnails from a Url.

A user is not able to generate thumbnails from a video file URL.
Error:
Access to video at 'https://xyz.com/file_example_MP4_640_3MG.mp4' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Acceptance criteria
It should generate thumbnails from a video file URL

setting "crossorigin" attribute with "anonymous" to video element may help.
reference: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/crossorigin


A missing space in a shell_out command in install_via_gem_command

The install_via_gem_command method is missing a space and causing failures when a specific version of a gem is requested.  This adds that space.

Whoa - I'm going to look at these test failures.  Sorry.

Does this actually fix anything?  If it does, could you include a test for it.
It looks like src and opts always are either nil, or have a leading space.  That gets the spaces right and doesn't leave a trailing space when they're both nil like in your last 3 tests.

So I'm proxying this fix from a customer.  In their environment they were using a combination of arguments that triggered this line of code and it was failing for them.  So they went in to their local copy of the client, added this space and it worked where it wasn't working before.
And like you, it baffled me, because while it's kinda hidden, there is a space prepended to the src variable even though it doesn't readily look like there is.
I have some meeting time with the customer today, I'll reaffirm they've still got this patch on their local systems.  Thanks @lamont-granquist.

Sounds like voodoo debugging, this probably wasn't what actually fixed the issue.

That's entirely possible @coderanger, there are lots of moving parts in play here.  But based on my history with the customer I trust their debugging skills in a locked down environment that triggered the use of this line of code that most people won't encounter.

If we do in fact need a space, we need to know how to reproduce this so we can add a test that explicitly ensures we have the space. Otherwise we'll lose it in the future when someone presumes the extra spaces are cruft.
It looks like there's been a double space there since almost when the feature was added. 0759ce215d54e115ca83ac923b7244ee1262b67d had a single space and a month later it became a double space without explanation in 6179d4dc7796626baf0f0563515925636be829da. Looks like cruft still.
I spent some time testing and ensuring I hit that particular call to shell_out_with_timeout! and I couldn't cause anything other than success. Something like this:
gem_package "bob" do
  source "https://rubygems.org"
  version "0.5.0"
  gem_binary "/Users/btm/.rvm/rubies/ruby-2.1.4/bin/gem"
end

calls this:
/Users/btm/.rvm/rubies/ruby-2.1.4/bin/gem install bob -q --no-rdoc --no-ri -v "0.5.0" --source=https://rubygems.org --source=https://rubygems.org

With no source you get:
/Users/btm/.rvm/rubies/ruby-2.1.4/bin/gem install bob -q --no-rdoc --no-ri -v "0.5.0"

So looks fine still.

Should probably just use something like this:
https://github.com/chef/chef/blob/lcg/dpkg-multipackage/lib/chef/provider/package.rb#L523-L531
That hasn't been merged yet, though, and I might try to just push it directly into shell_out_with_timeout if I can...

That got merged (and is now 404'ing) the API to use is here:
https://github.com/chef/chef/blob/6be47e6db1513824af52524b4d8bc83c32849d4a/lib/chef/provider/package.rb#L554-L562

Well the contact at the customer has moved jobs and they're not complaining about the issue.  They had monkey patched it locally anyways and no one else seems to be complaining about this issue so I will close this.
I think filing away this example in our brains in case anyone else encounters this potential edge case in the future is the best I can do at the moment.
Thanks everyone.

yeah at some point i'll a_to_s those which will fix any edge cases the right way

(although if anyone finds this and wants to leap in and fix them, feel free to submit a PR...)


Access the BM25 implementation

Good morning;
I need to my experiments to access the implementation of the BM25 model because I have to perform some changes to my model, please, how can I get access to the BM25 implementation in order to make my experiments, or call the function making the BM25 ?
Thanks

I added an example on how to do this here:
https://github.com/cvangysel/pyndri/blob/master/examples/query_environments.py
Be sure to check the Indri documentation for the exact flavour of TFIDF/BM25 you are getting.
Good luck!

Thanks :)

i succes in running simple code
import pyndri

index = pyndri.Index('/home/opiq/indri/runquery/alfatihah_indeks')

# Queries the index with 'hello world' and returns the first 1000 results.
results = index.query('#wsum (2.0 #1(bismil))', results_requested=1000)

for int_document_id, score in results:
    ext_document_id, _ = index.document(int_document_id)
    print(ext_document_id, score)

and get result just like this
doc_1  -3.357361315536498
then,i try to run query again with example query_environments.py
with this code
import pyndri
import sys

if len(sys.argv) <= 1:
    print('Usage: python {0} </home/opiq/indri/runquery/alfatihah_indeks>'.format(sys.argv[0]))

    sys.exit(0)

with pyndri.open(sys.argv[1]) as index:
    # Constructs a QueryEnvironment that uses a
    # language model with Dirichlet smoothing.
    lm_query_env = pyndri.QueryEnvironment(
        index, rules=('method:dirichlet,mu:5000',))
    print(lm_query_env.query('bismil'))

    # Constructs a QueryEnvironment that uses the TF-IDF retrieval model.
    #
    # See "Baseline (non-LM) retrieval"
    # (https://lemurproject.org/doxygen/lemur/html/IndriRunQuery.html)
    tfidf_query_env = pyndri.TFIDFQueryEnvironment(index)
    print(tfidf_query_env.query('bismil'))

    # Constructs a QueryEnvironment that uses the Okapi BM25 retrieval model.
    #
    # See "Baseline (non-LM) retrieval"
    # (https://lemurproject.org/doxygen/lemur/html/IndriRunQuery.html)
    bm25_query_env = pyndri.OkapiQueryEnvironment(index)
    print(bm25_query_env.query('bismil'))

and get result like this

Usage:python query_environments.py </home/opiq/indri/runquery/alfatihah_indeks>

How can i get such results simple code but with parameter like query_environments.py


Create Keystore - Streamline process for main use cases

Again, without metrics, I would guess that most people using your service will be on the ETH platform and this should be your happy path to usage.
I would recommend compartmentalizing functions to:
Basic
*Name
*Password
*Confirm Password
Advanced
Select Neworks (where a user can decline ETH, and select any other network)
Select Ethereum Tokens (Selecting this would also select ETH network)
Select Kovan Tokens (Selecting this would also select Kovan testnet)
Select Ethereum Classic Tokens (Selecting this would also select ETC network)
Override crypto +encryption values

Agree with moving the networks selection into advanced
💸 x 3


Change chat1 protocol to support multiple preview assets

This changes the local message protocol to support multiple previews of an asset.
The service interface to posting/download attachments, previews is untouched.  When design settles on what they want, we can add to the service interface to support their needs.

@mmaxim and I discussed this and think it's best to hold off merging this until we know exactly what frontend needs.  I imagine they will need some way to specify which preview is which, for example.
There is ticket CORE-4381 to figure it all out.
But, as a proof of concept of bumping the protocol versions, it was a success!  I'll keep the branch alive until after 4381.
cc @maxtaco

This isn't needed anymore.  Changes made elsewhere.


[OneExplorer] Show .circle.log file

This commit shows .circle.log file under the cfg file.
ONE-vscode-DCO-1.0-Signed-off-by: dayo09<EMAIL_ADDRESS>

To me, it seems to have both refactoring and showing the file.

So it makes reviewers hard to review, IHMO.

Questions about artifact
There are the following files

.tflite
.circle
.circle.log

To me, artifact could be one and include all of the above files. However, this PR show 3 artifacts to me.
What do I miss? Could you describe it?

So it makes reviewers hard to review, IHMO.

Sure.. I will separate theem.

Hold until #1006 is merged

@Samsung/one-vscode PTAL :-D

@one-vscode PTAL :-D

ping @llFreetimell


Use fresh class instances for each packed asset

Previously a call to the register_asset_builders function was required when using the asset packer to register all the asset tools with the packer, these were then passed into an AssetSource instance where they were used to handle the build process of a single asset by "guessing" the appropriate tool.
Rather than faff around passing these from __init__ all the way down to where they're used, this change defines the builders inside the AssetSource class. An instance is only created for a specific builder if it's used during a source build.
To make this change possible I've elminated the need to pass in a parser argument to Tools. IIRC the parser - which is used to set up argparse for handling tool arguments - is not used at all when invoking tools via the AssetBuilder.
This is a monster change which might break something... but - fingers crossed - the tests pass and 32blit-beta still builds.

Pull Request Test Coverage Report for Build 372617188

0 of 0   changed or added relevant lines in 0 files are covered.
69 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.2%) to 67.831%

Files with Coverage Reduction
New Missed Lines
%

ttblit/core/assetbuilder.py
5
92.41%

ttblit/core/tool.py
5
81.25%

ttblit/init.py
6
21.95%

ttblit/tool/packer.py
14
82.89%

ttblit/asset/font.py
39
27.45%

Totals

Change from base Build 367944836:
0.2%

Covered Lines:
738

Relevant Lines:
1088

💛  - Coveralls


Provide more info in /api/history for deep linking and richer UI interactions

To allow more elegant implementation of https://github.com/weaveworks/service-ui/issues/117 (vs. regex parsing text).
History entry wishlist: (are these possible?)

serviceId (to link to a service page)
imageId (to link to image / issue re-release)
imageSource (to link to quay.io UI)
releaseId (possible?, to show more info about a release)
status (success|fail) for some nice green/red coloring.

I'd suggest something like this for a release event, (forgive the go syntax):
type Event struct {
	ID string `json:"id"`

	// usually "Release" for now, but could be other things later
	Type string `json:"type"`

	// instance affected by this event
	InstanceID string `json:"instanceID"`

	// What time the event was started.
	StartedAt time.Time `json:"startedAt"`

	// If the event had a duration, how long did it last?
	EndedAt time.Time `json:"endedAt"`

	// success|fail, or maybe `debug|info|warn|error`, like log-levels?
	Status string `json:"status"`

	// Maybe a pre-formatted info string for errors, and ?other-stuff? ?
	// or, maybe this is unnecessary given the metadata below...
	Message  string `json:"message,omitempty"`

	// EventType-specific metadata here. for example, for a release:
	Metadata map[string]interface{}{

		// Maybe this is just the same as the event id? maybe not?
		ReleaseID  string

		// Might be a bunch of services affected by a single release
		ServiceIDs []string

		// likewise for images, can include repository/etc in each image
		ImageIDs   []image

		// could also include stuff like "triggering user" in here.
	}
}

You could see how other events could fit into this, such as "Service Automated", "Service Locked", "New Image Discovered", etc...

You could see how other events could fit into this, such as "Service Automated", "Service Locked",

I don't have interpretations of startedAt, endedAt for these events (although I'm not sure the events belong in the log anyway ..)

For automated/locked events startedAt/EndedAt would likely be the same.


[WIP] Debugging flaky tests

Still seeing some flakes caused by timeouts, maybe we should merge this?


chore: remove react-hot-loader

we don't use it...
Testing

Trade-offs

Dependencies

Screenshots

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


Support additional block production times

Some applications do not require blocks to be produced every 500 ms which is the current default block production rate.  It is desirable to some applications to not have to bear the data storage load that producing blocks at this rate implies.  Some applications also do not require block production to occur at a regular rate, instead they could be produced only when needed, so called sparse block production.
Allow the possibility to configure the block production rate as a chain parameter defined at genesis.
Slack internal discussion: https://blockone.slack.com/archives/CN12Z81RU/p1604412637205300

Slack internal discussion: https://blockone.slack.com/archives/CN12Z81RU/p1604412637205300

+1 for configurable block times or sparse production.


fix: rename addressvalidation module to maps-addressvalidation

https://github.com/googleapis/google-cloud-java/pull/8850 should have used maps-addressvalidation as the api-short-name / module name to follow  maps-routing convention.

I see Git recognizes these changes as renames. Good.


No Option to center a map after adding marker

Hi,
I want to center a map view after adding the marker but there is no easy way to center a map view. Please advise how I can do this.
Thank you.
Regards,
Muhammad Adil

This function would be very useful to me, too.

It will jump on it, during change detection.
Also as @tylerablake said. one must store a reference to the map.
so you can manipulate it later on.
ps: don't forget that you have to update your properties inside the "zone". otherwise change detection won't happen.
Cheers.


Fix incorrect conditional compilation symbol.

Oh, wow. Fast. I was half making notes for me for later, but thanks for this!


Java Integration

I am trying to use usaddress in Java. Jython cannot handle .so files (_pysrfsuite.so). Is there any way I can still do it

No. You can use our web api: https://parserator.datamade.us/usaddress


:bug: Terminate kcp process if controller installation fails

Summary
As per discussions on Slack (https://kubernetes.slack.com/archives/C021U8WSAFK/p1730131234224829), it makes sense to let the kcp process crash when it wins a leader election but then fails to install controllers. If this happens, it might hold onto the leader election lock but no controllers are actually running to reconcile objects. By making it crash, we make a new leader election possible.
The leader election package unfortunately doesn't have a "native" way to handle such failures.
Related issue(s)
Fixes #
Release Notes

Purposefully crash if leader election was won but controllers failed to install, allowing another instance to take leadership

/lgtm
/approve


Giveaways

Giveaways will be a custom command which is similar to how Polls operate. Giveaways will be stored in its own table, with finish time. Users will enter the giveaway, and be associated with the giveaway. A newly scheduled thread will run every n minutes scanning for completed giveaways. Upon completion, the bot will randomly select a Discord User from the entered list and announce the winner.

Completed and merged


Adding XOOPS CMS

[https://github.com/XOOPS/awesome-xoops]
[A curated list of awesome XOOPS CMS modules, themes, tutorials & other useful resources]
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Has the Awesome badge on the right side of the list heading,
Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

Each link description starts with an uppercase character and ends with a period.Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

There's almost no content in that list and it seems there's not a big community around the project yet. Closing for now.

You never stated anywhere that you need certain minimum number of lines of content, the only requirement I was aware of, was the 30 days.
I was not going to put everything at once, just wanted to start the list, get approved, and start adding once we have time available. I can easily dump into content all our

modules (https://github.com/XoopsModules25x)
themes (https://github.com/XoopsThemes, https://github.com/XoopsThemes25xArchive-3col, https://github.com/XoopsThemes25xArchive-2col), and
tutorials (https://github.com/XoopsDocs)

You also didn't state anywhere that there is some kind of "big community" required. How do you measure this? By number of contributors, likes? We are in process of transitioning of our community to GitHub, so logically not everybody feels yet comfortable with GitHub.
If you are not familiar with XOOPS, you might read more about XOOPS in these recent articles on TechRepublic:
http://www.techrepublic.com/article/the-common-problem-with-drupal-joomla-and-xoops/
http://www.techrepublic.com/article/one-on-one-on-one-with-xoops/

You never stated anywhere that you need certain minimum number of lines of content

It's not just about the amount of content. The list looked very unfinished. See:

It's the result of hard work and the best I could possibly produce.

just wanted to start the list, get approved, and start adding once we have time available.

That's just not how this list works. This project is a showcase of great lists. Work on it some more and try again in a couple of months.

I can easily dump into content all our

No, don't do that. An awesome list is a curation.

You also didn't state anywhere that there is some kind of "big community" required.

I can't possibly list everything, and why would I really, I have yet to get a contribution that have read all the points in the current list. It doesn't require a big community, but it does require some, or rather it has to be big enough for a good amount of people to be interested in the project/theme. I can't add every little obscure project/theme though. But point taken, XOOPS is a big community.


PayPal Billing Agreements

In this branch, we introduce a new Payment Gateway: PayPal Billing Agreements aka PayPal Reference transactions. This allows existing customers to use an existing PayPal account without entering their details again.
We use WooCommerce's Tokenization API to allow customers to use their existing PayPal account or to enter new details. Technically, we set the customer_is_present parameter to no if a Payment Token exists and submit the customer id (as customerid) on every request.
This branch is based on our refactoring branch (see #8) which should be merged first.

Reviewable after merge of #8
Following commit are interesting for this pull request:
https://github.com/PAYONE-GmbH/woocommerce-3/pull/9/commits/fec9632131371abb6b5db396180ed556f296c286
https://github.com/PAYONE-GmbH/woocommerce-3/pull/9/commits/46a7c97bce63e98604684567e22600f97d6701a8
https://github.com/PAYONE-GmbH/woocommerce-3/pull/9/commits/9d001d003482915b908994edbef79f6e703ab650
https://github.com/PAYONE-GmbH/woocommerce-3/pull/9/commits/6c3420f78e212e913f23ead24c8dad28006099aa


Outlook: Add column in the Network activity log to track why resources are not loaded from DiskCache when ServiceWorker is present

We don't have a lot of intuitive insight into ServiceWorkers and whether Network activity is ultimately serviced from Disk or Network.
It would be great if we could instrument the cache-fail points in network requests (e.g., you can imagine that the browser internally checks Cache header, ETag header, Expires header, etc. etc.. We can't get into Service Worker logic of course (since that's script-managed) but we could create a new panel (even a column) that indicates that we were appropriately serviced by the cache.
It would also be excellent to know why it's not coming from DiskCache when a ServiceWorker is present!

Interesting. Let me double-check my understanding.
On a typical webpage (not using a service worker), the Network tool does provide the information you're looking for in the Size column, as seen below:

However on a PWA, with a service worker, the Network tool only says if a request was handled by the worker, as seen here in the Size column:

So what you're saying is that it'd be really good if the tool would provide more information than this for service worker-handled requests, right? Maybe something like replacing the (ServiceWorker) string with (ServiceWorker - DiskCache) and (ServiceWorker - Network)?
How about this: if you go to about:serviceworker-internals, find your service worker in the list, and then click Inspect, you'll get a DevTools instance just for the worker. In this instance, you can also use the Network tool and there, you should only see the requests that are made to the network. Everything else that hits the cache will not be displayed.
Does that help?

This is not currently a PWA, so we're talking about the first experience rather than the second one. The main question is in the failure case - where have a service worker, and we expect it to service from the DiskCache, but we still see network activity. We'd like better visibility into why we're hitting the network. Was something out of date, or did we install the service worker correctly, etc.?

@dicaryl did you get a chance to take a look at the new Fulfilled by column in the Network tool? Does this help?


Update editorial_collection_rail test name/outcomes

Renames outcomes from boolean 0/1 to control/experiment
Renames test to editorial_collection_rail (no s) to prevent duplicate cookies

Decided to use a different implementation, closing.


[ENH] no x_label or y_label found in the plotting functions

fixed in 9feca0c78cedbfae6b3037994e0d3606fa075dc7

The plot functions have data_label but no axis_labels

fixed in a1307da88111a55c08f640b745d6c281559d0aee


About Port

I am using Gosafe G3A GPS Device. I am unable to see the device on map, when i check the log i get this hex. I am sending the data on port 5078
2a475330322c3335353233333035343639383931332c434c4c3a3030303030303030303030303b3430343b32323b31303133353b313233312c5354543a34303b302c4144433a303b31312e393b313b34342e303b323b342e323b333b302e3023

Any input on this will be highly appreciated. Thanks

Your device doesn't send any GPS info. Possibly it doesn't have a GPS fix.


bug in getConnectionName

I am using it with newer version of node and facing problem with following code of getConnectionName function in index.js.
name = host.host + ':' + host.port + ':' + (host.localAddress ? (host.localAddress + ':') : ':')
Why appending 2 colons after port number when localAddress is not present.
name getting created for my following host object is "abcd.com:80::"
{ path: undefined,
port: 80,
host: 'abcd.com',
minSockets: 10,
maxSockets: 100,
servername: 'abcd.com',
_agentKey: 'abcd.com:80:',
encoding: null
}

+1


Setting background image in new theme file?

Hi,
I'm writing a new theme file and want to use page_background_image where the image is in a directory called images which is subdirectory of the directory where my theme.yml file is. Is this possible?
theme.yml:
page:
  layout: portrait
  margin: [0mm, 0mm, 0mm, 0mm]
  size: A4
  background-image: image:test.png[]

Creation of pdf:
$ asciidoctor-pdf  -a pdf-style='./theme.yml' -a imagesdir='./images' test.adoc

This doesn't work though as I get this:
asciidoctor: WARNING: page background image not found or readable: /usr/local/lib/ruby/gems/2.4.0/gems/asciidoctor-pdf-1.5.0.alpha.16/data/themes/test.png

Is there a way to tell the theme file that my test.png is relative to theme.yml ?

To answer my own question, I should have read the Applying Your Theme section better!


Editing OffsetFrame properties do not update its axes in the GUI

Steps to reproduce

Load the attached model.
pendulumIMU.osim
Select  link_imu_offset  from Bodies->link, right click to Show Axes
Edit the link_imu_offset's properties in the Property editor. E.g. set the Translation to (0 0 0.05).

Expected result
The link_imu_offset and the link_imu geometery are drawn at the new location (near origin of the link).
Actual result
The the link_imu geometry is drawn at the new location (near origin of the link), but the  link_imu_offset' axes are still drawn its original location (at ground).

Environment and GUI version
Windows, on both:
OpenSim-558d3e9f-2018-06-04, &
OpenSim-0ac2967b-2018-06-08

Ran into this issue again during model building demo for webinar practice.

Can this be closed as verified?


windowchef: init at 0.5.0

Motivation for this change
Windowchef is a stacking window manager similar to 2bwm, but more modular in its approach.
Things done

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

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

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/marketing-team-can-we-present-nix-nixos-better/6249/52

I folllowed your steps exactly because it seems like this pull request is stuck. However, now I think there are a lot of issues.  Any help?

Please follow CONTRIBUTING.md and manual#submitting-changes-making-patches  and squash the commits.
This can be done with:
git reset HEAD~7
git add -- pkgs/
git commit --amend --no-edit
git push ... ... --force

I will try again.  However, the documentation on how to do this seems very poor.

I think you had other commits on top of it, my assumption was that you were at the HEAD of the PR branch

@jonringer  no problem, sorry for the bad attitude earlier.  I think this commit could be cleaned up anyway and this helps me understand git better.


Travis.CI tests not running on PRs and in master

Since this commit the Travis.CI builds are not running any more in master. They work fine if triggered manually, but get not triggered automatically any more.
The commit in question did not change anything (was a documentation change only), so something in the Tracis configuration must have been changed.

The builds are actually running, they just don't show up in GitHub. There has been a recent issue in the Travis forum - added a respective question in that thread.

@jmcgeheeiv - I just switched the repo off and on again in the Travis configuration for my own fork, and it started to work again, Can you please try to do the same in your Travis settings?

I tried it and it worked. Looks good.

Thanks - whatever the reason was, it is fixed now!


503 when adding new frames

Setup the docker container, and tried to add my first frame only to receive a 503, how does one enable debug logging?

Apologies about that. This now works in the latest version.

Thanks it's working awesome now!


UBQ: hdPath selection fix

Fixes hdPath selection for Ledger when UBQ node is selected.
closes issues #1030 & #1212
Note: Layout of radios has been changed slightly as it made sense to do so.

Second commit adds ADD_Ledger_2_Exp & ADD_Ledger_2_Ubq to translation files.
Some additional ng-if's are added so ledger instructions say correct application name based on selected node.


Vim-like selection with shift + v

I checked man and issues on gh, but didn't found multiselect. Wonder if it's implemented or not?

 Then move up or down and you'll see the selection.

Not sure where that 0.99 version number came from, but that commit hash points to this, which is the (very) old C++ version, and is actually part of the 0.42 line.
So the answer is yes, it's implemented. It's at least implemented in the current version, but I don't remember if it exists in the 0.42 branch.


partition leader should be even after restore cluster

Please check the FAQ documentation before raising an issue

Describe the bug (required)
Balanace leader not executed after restore cluster, the load of each storaged node will uneven.

Your Environments (required)

OS: uname -a
Commit id (e.g. a3ffc7d8)

How To Reproduce(required)
Steps to reproduce the behavior:

Step 1
Step 2
Step 3

Expected behavior

Additional context

https://github.com/vesoft-inc/nebula-operator/pull/504


Deprecate and remove all legacy common functionality that has already been replaced in the new system

Context
Ref: https://github.com/backstage/backstage/issues/24493
To prepare for the stable backend release, we will deprecate the backend-common package.
Description
Make sure that all factories, handlers, loaders, routers and other utilities that where mapped to the new system gets deprecated in the backend common package.
Here is a list of things to deprecate:

[!Note]
Since this list was created while reviewing the common API reports for the backend, make sure you revisit it when working on this task.

Alpha api-report:

[ ] Context

Index api-report:

[x] getRootLogger
[x] getVoidLogger
[x] createRootLogger
[ ] createServiceBuilder
[ ] loadBackendConfig
[ ] errorHandler
[ ] requestLoggingHandler
[ ] HostDiscovery
[ ] LegacyCreateRouter

Pull request deprecating the loggers part: https://github.com/backstage/backstage/pull/24804

Pull request deprecating the service builder: https://github.com/backstage/backstage/pull/24814