General questions regarding hyper parameter.

Hello,
Thank you for your great paper!
During application of your software some questions arose to me:

Have you tried tuning the gamma parameter of the SVM? (paper only mentions C)
2)The paper recommends 1500-2000 optimization steps, however, what if my dataset has 40k time series
2.1) Any recommendation on how to set/tune the number of optimization steps?
In the paper representations of length 80-160 were trained, however, to me that seems a quite long, given that many datasets in UCR have time series shorter than that.
3.1) Have you done any test with 16-32 dimensional representations?
3.2) Have you examined the correlation between performance and underlying dataset avg. time series length?
3.3) Any recommendations on lower bound on dimensionality?

Any insight is highly appreciated!

Hi, thank you for your interest in our work!
You questions mainly deal with the hyperparameters that we chose for our unsupervised method. Since we were working with this fully unsupervised encoding method on a large number of datasets, most of them being quite small, we wanted to make sure that these hyperparameters could fit most of them, explaining these choices.
More specifically:

We did not extensively tune most of the SVM parameters. We kept gamma to its default value on scikit-learn v0.20.0.
Note that, when K (the number of negative samples in the loss) is equal to 10, 2000 optimization steps corresponds to approximately 20k samples seen by the network, so it could cover half of your dataset. Your dataset being significantly larger than most, if not all, datasets that we study in our article, you might indeed want to increase the number of optimization steps. A good way to choose it, if you have a validation task (e.g., regression or classification), would be to evaluate its performance with respect to the number of optimization steps.
Indeed, some UCR datasets have time series which are shorter than our representations. However, these static representations should capture diverse temporal information such as short and long-term dependencies, which might require a large number of dimensions. We chose a representation size that we believe to be large enough for most studied datasets, but you may probably reduce it without significant performance decrease. We did not run a lot of tests regarding the size of the representations, so it is unfortunately difficult to answer your questions precisely. We are of course welcoming any feedback!

I hope this answers your questions. Let us know if you have any other one!

Your response answers all my questions, and is consistent with what I understood from you paper.
Thank you for taking the time, it's highly appreciated!

I might post some insights here regarding representation dimensionality given avg. time series length & number of optimisation steps given dataset size should I get some.


break beta div into two computations

From microbiomeComputations created by asizemore: VEuPathDB/microbiomeComputations#21
When revisiting how the app works, break up the compute into two very clear distinct parts. Prep for in the future when we might have only the first part of the current beta div app running

I'm working with beta div right now and am a little frustrated about only getting the pcoa outputs.
Did we have plans for how this would work? Some ideas in no particular order

Extra arg to the beta div function that says give me distances or pcoa output
Actually separate beta div into a beta div computation and a dimensionality reduction option
Return both pcoa and distance matrix in the compute result. Distance matrix could go in stats i s'pose, similar to the correlation output.

those arent mutually exclusive. my suggestion, do all of the following:

add a distanceMatrix method
refactor the existing betaDiv method so it calls distanceMatrix
add an arg to betaDiv so that it can optionally, additionally return distance matrix data in the stats slot

(how to organize it on the site, should we ever decide to let ppl plot the distance matrix directly, is less clear)


💥(core) first step to k8s migration

Purpose
We want to deploy arnold apps on Kubernetes instead of Openshift.
Arnold core needs to be modified to remove everything that is related to Openshift and replace it with K8S equivalent.
Proposal

[x] use kubectl instead of oc (Openshift client) in arnold CLI
[x] use k3d instead of oc cluster to setup a development cluster
[x] replace OKD specific entities with K8s equivalent in core tasks
[x] use cert-manager instead of openshift-acme
[x] update hello app to be compatible with k8s

Remaining work to be done

[ ] Create network policy to isolate the namespace during project initialization
[ ] Update the Changelog !
[ ] Test all ansible base tasks

Important notes
About K8S authentication
The authentication mechanism is sligthly different with kubectl, because the commands oc login and oc whoami -t do not exist with kubectl.
Arnold CLI has been updated to discover authentication information in k8s configuration and service account secrets, as explained here
Note that it is now mandatory to authenticate through a service account to use arnold. Authenticating with a regular user is not possible anymore, because it can be done in multiple ways (e.g. with OpenID, via a kubectl plugin that need user interaction) and this cannot be executed inside the docker container.
About TLS certificates generation (acme core_app)
We use cert-manager instead of openshift-acme controller.
We assume that cert-manager is already installed on the target K8S cluster.
Since it is strongly recommended to install only one cert-manager instance on a K8S cluster, the acme core_app is now just generating one ACME Issuer per namespace (i.e. one letsencrypt account per arnold project).
About ansible tasks and k8s templates / entities
Route(s) have been replaces with Ingress(es).
The route*.yml.j2 template files are now ignored and should be named ingress*.yml.j2
DeploymentConfig(s) have been replaced with Deployment(s).
The dc*.yml.j2 template files are now ignored and should be named deploy*.yml.j2
How to test
Requirements

install kubectl and k3d on your workstation

Bootstrap the arnold cluster

make cluster

You have a working k3d cluster running on your computer.
You can interract with it with kubectl (the context name of this new cluster is k3d-arnold).
The Ingress HTTPS port will be bound to your host 8443.
Deploy the hello app

ANSIBLE_VAULT_PASSWORD=arnold bin/arnold -a hello -c eugene -d -e development bootstrap

Curl it !
curl -kv "https://next.hello.development-eugene.$(hostname -I | awk '{print $1}').nip.io:8443/"

Looks really cool :clap: Documentation is gold, I think it might be nice to keep a copy of your narrative in the project's documentation. WDYT?

Looks really cool  Documentation is gold, I think it might be nice to keep a copy of your narrative in the project's documentation. WDYT?

@jmaupetit Thanks!
Yes, we'll have to take time to document this. I imagined this in a PR dedicated to the documentation update.
In the meantime, in order not to forget anything, I try to list everything that is important to document in PR descriptions and commit messages.

In the meantime, in order not to forget anything, I try to list everything that is important to document in PR descriptions and commit messages.

Yes and that's really cool :muscle:

@sampaccoud @jmaupetit Thank you very much for your reviews!
I adressed all your feedbacks, may I ask you a final review :pray: ?


upgrading version of vault in existing cluster not behaving as expected

Describe the bug
I have an existing bankvault cluster. I'm running Vault version 0.10.4. If I update the cr-etc-ha.yaml file to have a newer version of Vault (0.11.0) and deploy it, my pods are not updated to the new version. I have to manually delete my pods and when they are recreated they have the new version of Vault.
To Reproduce
Steps to reproduce the behavior:

update https://github.com/banzaicloud/bank-vaults/blob/master/operator/deploy/cr-etcd-ha.yaml#L7 to have a different version of Vault than you already have deployed.
kubectl apply -f cr_etcd_ha.yaml
kubectl -n  describe pod vault-0  ( or vault-1)
See Image is not the version of Vault specified in the update cr-etcd-ha.yaml file:

Containers:
  vault:
    Container ID:  docker://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Image:         vault:0.10.4

running:  kubectl -n  delete pod vault-0 will cause the pod to get recreated and it will have the correct/expect Image version
Expected behavior
If I update the cr-etcd-ha.yaml file with a new version of Vault and deploy it, my pods perform a rolling update to the new version.

Hi @eisjcormier, which Kubernetes version are you using? I can't reproduce this on my version 1.10 cluster.

this is how my StatefulSet looks like after the update from 0.11.0 to 0.11.1 Vault:
Name:               vault
Namespace:          default
CreationTimestamp:  Wed, 12 Sep 2018 20:05:59 +0200
Selector:           app=vault,vault_cr=vault
Labels:             <none>
Annotations:        <none>
Replicas:           1 desired | 1 total
Update Strategy:    RollingUpdate
Pods Status:        1 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:       app=vault
                vault_cr=vault
  Annotations:  prometheus.io/path=/metrics
                prometheus.io/port=9102
                prometheus.io/scrape=true
  Containers:
   vault:
    Image:       vault:0.11.1
    Ports:       8200/TCP, 8201/TCP
    Host Ports:  0/TCP, 0/TCP

Hi. Thanks for looking into my issue.
I am running on AWS EKS. K8S version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:16:17Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:13:43Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
kubectl describe sts vault
Name:               vault
Namespace:          XXXXX
CreationTimestamp:  Thu, 06 Sep 2018 20:29:24 +0000
Selector:           app=vault,vault_cr=vault
Labels:
Annotations:
Replicas:           2 desired | 2 total
Pods Status:        2 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
Labels:       app=vault
vault_cr=vault
Annotations:  prometheus.io/path=/metrics
prometheus.io/port=9102
prometheus.io/scrape=true
Containers:
vault:
Image:       vault:0.11.0
Ports:       8200/TCP, 8201/TCP
Host Ports:  0/TCP, 0/TCP
but if you look at the pods, 0.10.4 is what is still running:
kubectl describe pod vault-0
Name:           vault-0
Namespace:      XXXXX
Node:           XXXXXXXXXXXXXXXXXXXXXXXXXX
Start Time:     Wed, 12 Sep 2018 19:10:39 +0000
Labels:         app=vault
controller-revision-hash=vault-69687f66bc
statefulset.kubernetes.io/pod-name=vault-0
vault_cr=vault
Annotations:    prometheus.io/path=/metrics
prometheus.io/port=9102
prometheus.io/scrape=true
Status:         Running
IP:             XXXXXXXXXXXXX
Controlled By:  StatefulSet/vault
Containers:
vault:
Container ID:  docker://e4e4fb266ab25078bc45493445b64cfd131c42c2973f3c2fd085fd80d1f92bef
Image:         vault:0.10.4
You'll notice my output of 'describe sts vault' doesn't have any Update Strategy specified. Where does that get defined? Is this not set by default?

Very interesting since the default Strategy is RollingUpgrade: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
Probably this is an EKS thing, but specifying the strategy explicitly should't hurt, so I will push a fox for this.

thank you

This seems to be an issue with our current ReadinessProbe setup, which makes sure that only the active Vault instance gets traffic, and the pod is not in Ready state. I'm investigating how we could work around this.

Let me know if you want me to test anything

@eisjcormier I have pushed a fix in #157 for this issue.

@eisjcormier  Although the Kubernetes bug report attached referencing broken stage this actually applies to not ready pods as well. The rolling upgrade does upgrade all the pods in any other state than the ready one - and unluckily it leaves that out from the upgrade. The workaround is to let rolling upgrades all the not ready pods in the StatefulSet then switch to an upgraded one (ready moves to not ready) - the controller than kicks on to upgrade the old ready one as well.
Hope this was clear enough ...

Thanks guys. Appreciate the quick turnaround.

@eisjcormier You are welcome, let us know how it works out for you. Hopefully, the StatefulSet issue will be fixed in the forthcoming K8s version so this will work as it supposed to (without the fix). Thanks for reporting it.

The fix has been released in https://github.com/banzaicloud/bank-vaults/releases/tag/0.2.23.


KV assets doesn't upload for Workers Sites

I tried to use Workers Sites with your example on this repo wrangler2/packages/example-sites-app and doesn't works.
It fails to upload assets to KV for dev and publish commands.
Is pending work or you will deprecate Workers Sites in favor of Pages?

I get this email after trying to publish like ten times. 😳

Hi,
You have exceeded the daily Cloudflare Workers KV free tier limit of 1000 Workers KV list operations.
Requests to list values from the Workers KV API will return 429 errors and list operations within a Worker will fail until the limit resets at 2022-01-31 at 00:00:00 UTC.
You can restore service by upgrading your account (Mondraco) to Workers Bundled on the plans page. It has a minimum monthly billing amount of $5, which includes 10 million read operations and 1 million each of write, delete, and list operations.
Best,
The Cloudflare Workers Team

Extremely sorry about this. We had a bug with Sites that was fixed in https://github.com/cloudflare/wrangler2/pull/335, but wasn't released to the beta channel. I just did a beta release right now (0.0.15), so it should be resolved now.
We are going to be supporting Sites for a while longer, until we have a better solution (which will potentially be an ad hoc Pages solution, but we haven't made any plans concrete just yet. We don't expect to ship any new features for Sites. The implementation is close to feature complete (pending landing https://github.com/cloudflare/wrangler2/pull/338, and anything else we missed).
I'm going to close this issue, but let me know if you face any further problems.

Starting a discussion re: Sites and other options to serve static assets here - https://github.com/cloudflare/wrangler2/issues/346

Thank you for fixing the assets upload!
But I can't use wrangler2 with KV assets with ES Modules worker.
Is it possible?
I understand that should be working because you have the option documented on cloudflare/kv-asset-handler repo. Maybe I didn't understand.

That's surprising, it should work. I'll reopen this and investigate soon.

With<EMAIL_ADDRESS>it's working properly. 😁


Auto-update address definitions

@Eeems suggested on Discord to make rm2fb automatically fetch the address definitions from a remote server when they are missing. This would make adapting rm2fb to new OS releases easier, since we’d just need to update the remote file and we wouldn’t need to publish new releases/package versions.

As a user this idea makes me feel a bit uncomfortable, although I understand the reasoning behind it. Is it possible to create a setting to disable the auto-fetch feature for those that don't want it?

As a user this idea makes me feel a bit uncomfortable, although I understand the reasoning behind it. Is it possible to create a setting to disable the auto-fetch feature for those that don't want it?

Yes it would be possible to disable it.
Ideally we'd have to put together some type of signing mechanism to ensure that it's only pulling down signature definitions that are known to be trusted. That said, due to the type of data being used here and the validation being done on the data I'd assume that it's less of a security risk.

Would a package that is just data definitions be possible?  If it's just additive, it could be easy to fast track release in Toltec possibly?  I don't know how often they update things, but like tzdata, it could be pushed regularly without much testing?

We would want a solution that works for both installs in Toltec, as well as users who install manually.

It would probably make sense to just try to pull down the address definition for the specific OS version, instead of the full list each time. This would also need to have a version number gate on it to have it gracefully quit if the version of rm2fb doesn't support the address definitions required.


Can pyspark version < 3.2.0 for raydp 0.4.0?

I want to read hudi using raydp, but hudi doesn't support pyspark 3.2.0 for now

no

Thanks for the feedback. It should not be very difficult for RayDP to support multiple Spark versions. We will consider adding it.


RTL tags are ignored by the plugin

Suppose you have this task :

This is the result in the card board:

Despite two LTR tags that are identified by the cardboard, the RTL tag (persian language) is not identified.

Interesting - thank you.  Not even thought about RTL languages so am not totally surprised that you have found an issue.
Will take a look :)

Hi @aliamini87 -> this is actually happening as Cardboard is only recognizing the characters A-Z, a-z, 0-9, _, -, / as being valid content for tags...
With that in mind, I'm going to change this from bug to enhancement as supporting both non-ascii tags and RTL are more additional features (that I would like to support) than issues with the current implementation.  With that in mind, could I ask a couple of questions on how obsidian works with RTL tags:

I presume that obsidian itself recognises the example you gave as a tag (just checking as I want to mirror obsidian's behavior if it is correct and I can).
is the # still on the left of the tag text in RTL markdown source (i.e: is the markdown content #rtl_tag rather than rtl_tag#)
How do #tags/subtags work in RTL in obsidian - are they the same way around as in LTR with the root tag on the left or is it reversed?

Many thanks in advance - look forward to getting this working for you

Hi

yes. obsidian considers them as tags.
your second question is a little complicated. because something that appears is different from something that suggested. see the pictures below: (sorry print screen doesn't work in this situation)

As you see suggestion is different from what appeared in the text.
and this is in reading mode :

about subtags:

In reading mode:

interesting - and thank you so much.
If possible, could attach an example markdown file containing some example RTL tasks with  tags (including with subtags), as this will make it clearer what the source looks like.  Then I will have some examples to test my parsing against - which will hopefully get me reading the tasks properly.
For the subtag example, is:

The parent part, and

the sub part?
Thank you again

This is a simple note with both tags and subtag.
Tell me if you need something else.
2022-10-29.md

fabulous - thank you that's great.  Loaded into my test vault.
I'm just finishing off my "other-plugin-compatibility" work then I will get on to this as it is going to be an interesting one to tackle and it's a pretty fundamental requirement to be able to properly support other languages! (Persian looks so beautiful)
I will have more questions as I get stuck in :)

Hi @aliamini87, I've got the first bit of this done.  The latest release (0.6.5) recognises RTL characters (in fact any Unicode characters) in tags, so Persian language tags (e.g. #تگ/زیرتگ) should now be picked up.
I realise that this isn't full RTL support and I would like to support better, so what else could/should I do to improve things?
My current plans are to check if RTL is selected in the obsidian editor settings and if it is:

place the '#' on the right for tags which are in RTL script
put the card check-boxes on the right and generally right align the card contents

Do let me know if there is anything else you feel I should try to get working.  Many thanks :)

Thank you very much.

It's really usable now.
If I find something, I will make an issue for that.
For now, the only minor thing that I see is that the checkboxes location in the RTL lines should be in the right.
Thanks again and good luck.

Thank you - I've added a new issue to track the general improvement for better RTL support: #113

Hiya - I've just pushed a new version 0.6.6 that I hope supports the obsidian RTL setting in a sensible way.  If you use this setting and could have a look and see how it looks/works that would be great.
Any feedback/suggestions would be gratefully received!


My championify is not running

Hello, the app opens with the background image but this is it, i don't see the others features in it, thank you for your answer.

You haven't upgraded yet I'm assuming? See breaking changes. https://github.com/dustinblackman/Championify/releases/tag/2.0.0


how to retrieve all data in this structure?

all projects with following attributes:
project name, project ID, countr (ies), company (ies).
let`s discuss

Please provide link for this one.
d

link: http://staging.resourceprojects.org/all-projects

it times out/maxes out at 150 records for me, at letter B:
http://www.resourceprojects.org/all-projects
Can you check it?

I need access to the prod to do proper debugging. Please share it.

This works well. thanks!


Package ClinvArbitration results

The process so far is to run this workflow for usage internally, then I localise all the component pieces, zip them up, and attach the data bundle to the ClinvArbitration releases
This is a mild pain, so this change adds an extra stage on the end to pre-package this data for release into a tarball/
The added benefit is that instead of gcloud cp'ing the two Hail tables during Talos runs we can instead copy in a single TARchive and unpack it in the image. Makes the whole process easier.

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

Project coverage is 26.62%. Comparing base (1f684ea) to head (ef3486e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1003   +/-   ##
=======================================
  Coverage   26.62%   26.62%
=======================================
  Files           9        9
  Lines        1705     1705
=======================================
  Hits          454      454
  Misses       1251     1251

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Transform Feedback Not Supported By Device - Log Spam...

Fedora 28
DXVK 0.90
GeForce GTX 1070:
Driver: 410.73.0
Vulkan: 1.1.82
I have been playing Quake Champions and can confirm that everything is fixed. I can now play on all maps with all characters without crashes :)
I did notice that the d3d11.log file was being spammed by "Transform Feedback Not Supported By Device" errors even though everything is working perfectly? After an hours play the log is over 6MB.
Sure its not really excessive but I suspect there is a bug around the conditions for logging this error to file.
Added bonus: The error contains a typo:
err:   D3D11: CreateGeometryShaderWithStreamOutput:
Transform feedback not supoorted by device

@7oxicshadow driver  Driver: 410.73.0 not work in  StreamOutput
work in 396.54.09 driver.

NVIDIA UPDATE DRIVERS TO StreamOutput!!!!
:(

talk your problem in to https://github.com/doitsujin/dxvk/issues/695

The Vulkan beta driver (396.54.09) supports transform feedback.


Links on front-page don't point to the correct path

Most of the links at the start of the page don't point to correct paths, instead point to correct_path + '.html' extension.

wow, odd. for me locally jekyll serve generates .html urls but on github it does / urls. And I can't find any way to force that locally. Any hints?

looks like my setup had a jekyll v2 something, while github is running a jekyll v3 and that version does paths differently. fixed it.


Countries joining odd factions

Many of the factions are specific to a region or story purpose. Sometimes countries elsewehere will join these factions, sometimes escalating the various wars strangely.

AI strats should be able to fix this, most simply by toning down joining a faction


peer-2-peer week 5

1, good job Abdelaziz so far but I would suggest you use transparent images for the logo and also for the partner's logos so that they blend with the page more.
2, on the main program section, add some padding to make it similar to the template design. and also make the link below the boxes visiible
3,

thank you.


fixed display message for the LineOverflow error

In the LineOverflow error message, the found and max values were switched. In the diff below, the max is 100 and 140 is what got found:
 fn foo() {
-    let file_name =
-        format!("{}", self.testpaths.file.display())
-        .replace(r"\", "/"); // on windows, translate all '\' path separators to '/'
+    let file_name = format!("{}", self.testpaths.file.display()).replace(r"\", "/"); // on windows, translate all '\' path separators to '/'
 }

internal error: line formatted, but exceeded maximum width (maximum: 140 (see `max_width` option), found: 100)

Thank you!


close #23 ir remoter screen design

@theacheng  FYI: The image above the buttons, I use (.png) because (.svg ) not support even I use the packages.

We may update it later and use custom paint instead, but this already great!


Spree Commerce Provider

Demo: https://spree.vercel.app/

Hi @lfades @okbel 👋
Could you take a look at this PR and propose the next steps to merge this into the main branch?
Thanks in advance!

Hi @damianlegawiec, thanks for doing this provider! We recently merged partial support for custom checkout (this PR https://github.com/vercel/commerce/pull/487/files) and some extra files are needed on the providers (you can check those files in the PR), can you update the branch to be up to date? Thanks!

Hi @goncy 👋 ,
We synced our integration with the main NextJS Commerce branch. For the time being, we'd like to keep showing the Checkout not yet implemented message. We are thinking of integrating with the new checkout sidebar. Thanks for working on it. Looks nice already. We're pleasantly surprised by the amount of progress in this area in NJC. 💪
Some details about the update to the integration (https://github.com/spree/nextjs-commerce/pull/2):
We used a no-op for submitCheckout in framework/spree/api/endpoints/checkout/index.ts and hooked the placeholder checkout page to getCheckout instead as submitCheckout allows only POST as defined in framework/commerce/api/endpoints/checkout.ts. Hope that works for you.
Can't wait for your review :)
T.

CC @damianlegawiec

Hi @goncy 👋 ,
We synced our integration with the main NextJS Commerce branch. For the time being, we'd like to keep showing the Checkout not yet implemented message. We are thinking of integrating with the new checkout sidebar. Thanks for working on it. Looks nice already. We're pleasantly surprised by the amount of progress in this area in NJC. 💪
Some details about the update to the integration (spree#2):
We used a no-op for submitCheckout in framework/spree/api/endpoints/checkout/index.ts and hooked the placeholder checkout page to getCheckout instead as submitCheckout allows only POST as defined in framework/commerce/api/endpoints/checkout.ts. Hope that works for you.
Can't wait for your review :)
T.

Hi @tniezg! You are right, this morning we have been working on a PR to allow providers to use get-checkout for that again https://github.com/vercel/commerce/pull/502/files will be merged in the next few days so you can get back to use get-checkout (sorry about that), I will continue with the review then, thanks 🙌

@tniezg the PR has been merged, you can get back to get-checkout, I will start with the review soon!

Hi @goncy,
The PR is up to date with the latest changes in main.

Merged latest changes in NJC's main branch.

Hey @tniezg, we are back to reviewing PRs, i noticed there are a bunch of changes to components and files outside the provider folder. Those changes should be avoided and in case of a bug being found or a feature to be implemented, that should be done in another PR and merged before this. Let me know if you need more info, thanks 🙌

Hi @goncy 👋
Thanks for reaching out. We've been hard at work adding features to our integration 🙂  The current version adds support for static pages, accounts and wishlists. 🎉 No more major changes are planned in the near future.
We separated changes to core components into #578 and #577. These PRs are not critical for the integration to work. We're especially interested in merging #578. If not possible, we'll create a workaround in our integration.
We had to include our Spree SDK in package-lock.json and package.json so they're part of this PR. Hope that's ok.
Cheers,
T.
CC @damianlegawiec

Great @tniezg ! I will try to get #578 merged soon and continue with the review soon, thanks!

Thanks so much for the review. We'll address all the issues soon. Have a good weekend!

@tniezg Can I get some demo env variables at<EMAIL_ADDRESS>so I test it on my local? Thanks!

Hi @goncy 👋
I sent an email to you titled "Testing setup for the NJC x Spree integration" with instructions.

Hi @gbibeaul,
Thanks for the comments. Resolved and responded to all. Let us know if there's anything else you'd like to discuss. 💪

Hey @tniezg we are almost ready, I modified the description of the PR, can you please update on what is done and missing just to have a record, not all points are required. I will do a final review today 🙌

Hi @goncy,
That's great news :) Thanks for all the help so far.
Regarding the list in the PR's description - we checked the items which are added to the integration.
There are multiple "Hook - Add Item", "Hook - Remove Item" and "Hook - Update Item" in NJC. We implemented the hooks for cart and wishlist features.
"Schema & TS types" - The word "schema" often relates to GraphQL in NJC. Spree uses JSON:API. That being said, we do include TS types for operations performed in Spree. They're either added directly to the integration or imported from Spree SDK.
Not sure about "API Operations - Get all collections". It seems collections are related to product categories. We do fetch categories inside framework/spree/api/operations/get-site-info.ts.
Cheers 🎉

Hey @tniezg! I have finished the review and we are almost ready to merge, I will contact you by email so we can own credentials for setting up the deploy on our side

Sure 👍

@goncy Links updated. Thanks for CRs.

Hi @goncy,
Thanks for reporting. We replaced @framework with relative imports.
For future reference: Use "typescript.preferences.importModuleSpecifier": "relative" in VSCode. Otherwise, VSCode uses whatever is shorter 🙂

🎉 🕺


Demos Don't Seem to Be Working

I'm using Chrome.  When I try to interact with any of the demos on this page, no matter what section (breadcrumbs, pills, whatever) it jumps to Home and anchors me to the top..so I don't actually see anything working in the demos
http://ink.sapo.pt/ui-elements/navigation/#

Hi @dschinkel,
All of the navigation interaction os based on hovering elements, so no clicking is required to see things work.
On another note the way we implemented the navigation documentation with these "fake" links is wrong and should be corrected, even if only to not take the page back to the top, which is pretty annoying.

ok makes sense.  I guess I figured clicking on some of those menus and links should do something but yea you're just talking about hover effects only there...


⚠ Bofrost.de has degraded performance

In bf68044, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1284 ms

Resolved: Bofrost.de performance has improved in 58f9bdb.


Allow complex regular expressions with Naming Conversion

Currently it is not possible to use "." And "+" when Naming Convention is set.
If this issue is accepted, please assign me.
Create a PR.

Colons are also not accepted, which effects a utility namespace of mine, where I save different time formats to storage using keys like "hh:mm:ss" to illustrate the format of the value.

Naming Conversion applies only to team, tag, nbtkey, objective, the characters allowed in these should be a-zA-Z._ +-

How about expanding the format of NamingConvention to support either a default template (camelCase, snake_case, whatever), a regular expression (a JSON string enclosed by slashes /, e.g. "/\\d\\d:\\d\\d:\\d\\d/"), or a complex object?
e.g. To allow an NBT key like hh:mm:ss:
"namingOfNbtKey": "/\\d\\d:\\d\\d:\\d\\d/"

To allow a score holder (fake player) name like $foo_bar:
"namingOfScoreHolder": {
	"prefix": "$",
	"words": ["lowercase"],
	"sep": ["_"]
}

To allow an objective name like namespace.camelCaseName:
"namingOfObjective": {
	"words": ["lowercase", "lowercase", "Camel"], // The first two words should be all lowercased, other words should be Camel style.
	"sep": [".", ""] // The first two words are separated by a dot (.), other words shouldn't be separated by any symbols.
}

:tada: This issue has been resolved in version 3.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to install mmdetection on pp64cle(IBM POWER8)?

Describe the bug
I follow the install method, and the error happens:
Installed /opt/anaconda/envs/wmlce/lib/python3.7/site-packages/mmcv-0.4.4-py3.7-linux-ppc64le.egg
Searching for opencv-python>=3
Reading https://pypi.org/simple/opencv-python/
No local packages or working download links found for opencv-python>=3
error: Could not find suitable distribution for Requirement.parse('opencv-python>=3')

Environment
Linux version 4.15.0-76-generic (buildd@bos02-ppc64el-028) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #86-Ubuntu SMP Fri Jan 17 17:24:13 UTC 2020

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

PyTorch 1.3.1

The reason is the lack of opencv-python, which may not support pp64cle. you may install opencv and the python api in other ways.

Thanks for your answer.
I have searched for some time, but I can't  find a good solution for this problem.
Can you share one?

Sorry that we do not have a power8 server, and cannot provide further help.


Add isExternal prop to SubdomainNavBar.Link component

Summary
Adds isExternal prop to SubdomainNavBar.Link component. If true, it renders a link-external icon after the link text.
List of notable changes:

Added isExternal prop to SubdomainNavBar.Link component.

What should reviewers focus on?

Make sure you're happy with the spacing around the icons

Steps to test:
Link to Storybook (TODO)
Supporting resources (related issues, external links, etc):

https://github.com/github/primer/issues/3517?reload=1?reload%3D1

Contributor checklist:

[x] All new and existing CI checks pass
[x] Tests prove that the feature works and covers both happy and unhappy paths
[x] Any drop in coverage, breaking changes or regressions have been documented above
[x] New visual snapshots have been generated / updated for any UI changes
[x] All developer debugging and non-functional logging has been removed
[x] Related issues have been referenced in the PR description

Reviewer checklist:

[ ] Check that pull request and proposed changes adhere to our contribution guidelines and code of conduct
[ ] Check that tests prove the feature works and covers both happy and unhappy paths
[ ] Check that there aren't other open Pull Requests for the same update/change

Screenshots:

cc. @danielguillan for design 👀


Migration to .Net Standard

This issue is to track the library migration to .Net Standard target.
This will allow devs to use library cross platform and in both .Net Core and .Net Framework projects.

Here is an early version: https://github.com/zerodhatech/dotnetkiteconnect/tree/netstandard
Tested only in Linux at the moment. Will release once tests are fine in macOS and Windows.

Is it released?

Not yet. Waiting for #27 to merge.

@ajinasokan - Is it possible to move it to .Net Core 3.1 LTS or .Net Core 2.1 LTS since .Net Core 2.0 is EOL?

@blueelvis Library is targeting netstandard20. It should be compatible with .Net Core 2.0+ and .Net Framework 4.6.1+. More info here. We didn't want to support only .Net Core because most of our users are on .Net Framework.

An alpha build is available in releases. You can either use the DLL file or the nuget package. You can add this to your .Net Core and .Net Framework projects.

Sure. Thanks! I will check it out shortly and let you know how it works.
On Mon 20 Jul, 2020, 11:56 AM Ajin Asokan<EMAIL_ADDRESS>wrote:

An alpha build is available in releases
https://github.com/zerodhatech/dotnetkiteconnect/releases/tag/v3.0.5-alpha.
You can either use the DLL file or the nuget package. You can add this to
your .Net Core and .Net Framework projects.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zerodhatech/dotnetkiteconnect/issues/25#issuecomment-660830080,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVJQI6O4ACWZHCMDUF6MMLR4PPQVANCNFSM4M3HM7FA
.

This has been merged in #28


Forbid invalid relabel configurations

This produces an empty label name
# config
relabel_configs:
- source_labels: [__address__]

# result
node_boot_time{="localhost:9100",instance="localhost:9100",job="node"}

I guess a configuration with either just source_labels or just target_label or any other config not having the minimum set of attributes set should be rejected.

@grobie I'm not an expert in relabeling, all my knowledge comes from @brian-brazil PromCon talk. I've implemented a draft of this fix based on https://prometheus.io/docs/operating/configuration/#<relabel_config>:

source_labels must be defined
target_label must be defined if action is replace or hashmod

However I found some counterexamples in conf.good.yml which is good by definition, right?

https://github.com/prometheus/prometheus/blob/master/config/testdata/conf.good.yml#L49
https://github.com/prometheus/prometheus/blob/master/config/testdata/conf.good.yml#L87

Am I missing something?

It is valid to not have source labels.

@brian-brazil in any case or in some particular? In https://prometheus.io/docs/operating/configuration/#<relabel_config> only labelmap looks unclear to me, the rest should require source labels

Replace doesn't require source_labels either.

That's useful for target relabelling, as you might want to add something static that's not from SD.


v2 CLI: themes are dropped into the /lib directory instead of project root

Current Behavior
Currently when generating a new v2 Skeleton project using the CLI, themes (maybe only custom themes?) are dropped into th e /src/lib directory.
Expected Behavior
Themes should reside in the root of the project, as they're only ever referenced or imported by the tailwind.config
Steps To Reproduce

Create a new v2 Skeleton project using the CLI
Select either a preset or custom theme options
The theme will be inserted into the /src/lib directory

Link to Reproduction / Stackblitz
No response
More Information
Not high priority, but would be a worthwhile change before we sunset Skeleton's v2 CLI.

@niktek let me know if you're interested in jumping on this, or feel free to self assing!


[bug]:  ClientCtrl.provider().request receive {"context": "client"} Missing or invalid. request() chainId: eip155:97

Description
I want switch Wallet network so I use ClientCtrl.provider() send a request  for 'wallet_addEthereumChain', and receive a error

[Error: Missing or invalid. request() chainId: eip155:97]

so  what is right way for reqeust ' wallet_addEthereumChain'  method.
WalletConnect Modal SDK version
v1.0.0-rc.5
Output of npx react-native info
System:
OS: macOS 13.3.1
CPU: (12) arm64 Apple M2 Pro
Memory: 56.38 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.20.0 - ~/.nvm/versions/node/v16.20.0/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.19.4 - ~/.nvm/versions/node/v16.20.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /Users/dingc/.rvm/gems/ruby-3.2.0/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
API Levels: 31, 33
Build Tools: 30.0.3, 31.0.0, 33.0.2
System Images: android-28 | Google APIs ARM 64 v8a, android-29 | Google APIs ARM 64 v8a, android-30 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.10121639
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
Languages:
Java: javac 20 - /Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.1.0 => 18.1.0
react-native: 0.70.4 => 0.70.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
debug Checking for a newer version of React Native
debug Current version: 0.70.4
debug Cached release version: 0.72.1
debug Cached release is still recent, skipping remote check
Expo Version (if applies)
No response
Steps to reproduce

connect wallet to metamask ,and current chain is Goerli, and sessionParams's chains only has  'eip155:1', when I set more than one, connect wallet will failed

    const sessionParams = {
        namespaces: {
            eip155: {
                methods: REQUIRED_METHODS,
                chains: ['eip155:1'],
                events: REQUIRED_EVENTS,
                rpcMap: PRC_LISTs,
            },
        },
        optionalNamespaces: {
            eip155: {
                methods: REQUIRED_METHODS,
                chains: ['eip155:5', 'eip155:97'],
                events: REQUIRED_EVENTS,
                rpcMap: PRC_LISTs,
            },
        },
    }

set default chainId to 97, and then read the Contract from chainId 97 successfully.
reset app , the default chainId is still 97, but in @walletconnect/react-native-dapp  will get connected wallet current network.
request request 'wallet_addEthereumChain' method, then receive error

Snack, code example, screenshot, or link to a repository

@ignaciosantise
I read the web3Modal's code , that connector's provider used @walletconnect/ethereum-provider.
In @walletconnect/modal-react-native, the connector's provider used @walletconnect/universal-provider.
what's different between @walletconnect/ethereum-provider  and @walletconnect/universal-provider ?
so is there any plan @walletconnect/modal-react-native use wagmi ?

Hey @dingcxx 👋 im not sure if i fully understand your issue, but i've tested this with MetaMask and it's working with their latest version (iOS 7.2.0-1142)

Session params only include eip155:1

export const sessionParams = {
  namespaces: {
    eip155: {
      methods: [
        'eth_sendTransaction',
        'eth_signTransaction',
        'eth_sign',
        'personal_sign',
        'eth_signTypedData',
        'wallet_addEthereumChain',
      ],
      chains: ['eip155:1'],
      events: ['chainChanged', 'accountsChanged'],
      rpcMap: {},
    },
  },
};

Connect with MetaMask
Call wallet_AddEthereumChain

provider.request({
      method: 'wallet_addEthereumChain',
      params: [
        {
          chainId: '0x89',
          chainName: 'Polygon Mainnet',
          rpcUrls: ['https://polygon.llamarpc.com'],
        },
      ],
    });

Approve request in MetaMask
Default chain is now Polygon

const chainId = await provider?.request({
      method: 'eth_chainId',
    });
    console.log('chainjId', chainId); //it logs `137` -> Polygon Mainnet

Tested personal_sign and it works as expected.

Regarding wagmi/ethereum-provider usage, we are currently discussing possibilities

Hey @dingcxx 👋 im not sure if i fully understand your issue, but i've tested this with MetaMask and it's working with their latest version (iOS 7.2.0-1142)

Session params only include eip155:1

export const sessionParams = {
  namespaces: {
    eip155: {
      methods: [
        'eth_sendTransaction',
        'eth_signTransaction',
        'eth_sign',
        'personal_sign',
        'eth_signTypedData',
        'wallet_addEthereumChain',
      ],
      chains: ['eip155:1'],
      events: ['chainChanged', 'accountsChanged'],
      rpcMap: {},
    },
  },
};

Connect with MetaMask
Call wallet_AddEthereumChain

provider.request({
      method: 'wallet_addEthereumChain',
      params: [
        {
          chainId: '0x89',
          chainName: 'Polygon Mainnet',
          rpcUrls: ['https://polygon.llamarpc.com'],
        },
      ],
    });

Approve request in MetaMask
Default chain is now Polygon

const chainId = await provider?.request({
      method: 'eth_chainId',
    });
    console.log('chainjId', chainId); //it logs `137` -> Polygon Mainnet

Tested personal_sign and it works as expected.

thanks for your reply， I will retry this case and reply to you.
I have some different steps with you:
fristly, I set the optionalNamespaces in sessionParams, I don't know what impact it is
secondly，before reuest 'wallet_addEthereumChain' method, I set the provider's defaultchain to 97 for read the Contract, maybe set defaultchain will impact the request
at last, maybe getchain could be a available interface in modal or provider is better
thanks again

Hey @dingcxx 👋 im not sure if i fully understand your issue, but i've tested this with MetaMask and it's working with their latest version (iOS 7.2.0-1142)

Session params only include eip155:1

export const sessionParams = {
  namespaces: {
    eip155: {
      methods: [
        'eth_sendTransaction',
        'eth_signTransaction',
        'eth_sign',
        'personal_sign',
        'eth_signTypedData',
        'wallet_addEthereumChain',
      ],
      chains: ['eip155:1'],
      events: ['chainChanged', 'accountsChanged'],
      rpcMap: {},
    },
  },
};

Connect with MetaMask
Call wallet_AddEthereumChain

provider.request({
      method: 'wallet_addEthereumChain',
      params: [
        {
          chainId: '0x89',
          chainName: 'Polygon Mainnet',
          rpcUrls: ['https://polygon.llamarpc.com'],
        },
      ],
    });

Approve request in MetaMask
Default chain is now Polygon

const chainId = await provider?.request({
      method: 'eth_chainId',
    });
    console.log('chainjId', chainId); //it logs `137` -> Polygon Mainnet

Tested personal_sign and it works as expected.

I retry this case, before reuest 'wallet_addEthereumChain' method, Idid not set the provider's defaultchain to a new chainid.
wallet_addEthereumChain work fine

mostly issue maybe was cased by session create.
I also receive wrong chainid by  request eth_chainId
steps below

change metamask network to goerli
call eth_chainId receive 5
call wallet_addEthereumChain method to 97
jump to metamask and then blocked, switch network not suceeess
back to my app
call eth_chainId receive 97 ,but current wallet network is goerli

Can you check if that same flow works in Trust? This are mostly MM issues

👌 let me try it

Can you check if that same flow works in Trust? This are mostly MM issues

trust wallet call 'wallet_addEthereumChain' method not working, if I use default

r
2ainbow can't connect wallet

maybe sessionParams is managed by universal-provider self ？
It is hard to user manage it.
https://github.com/WalletConnect/walletconnect-monorepo/blob/v2.0/providers/ethereum-provider/src/constants/rpc.ts

my current sessionParams code was changed to this

export const MethodName = {
    addNet: 'wallet_addEthereumChain',
    switchNet: 'wallet_switchEthereumChain',
    sign: 'eth_sign',
    getChain: 'eth_chainId',
    sendTransaction: 'eth_sendTransaction',
    // signTransaction: 'eth_signTransaction',
    // signTypedData: 'eth_signTypedData',
    personalSign: 'personal_sign',
}

export const SUPPORT_NETs = [BSC, ETH, Goerli, TESTNET_BSC, zkSync_testnet, zkSync_mainnet]

    const OPTION_CHAINS = SUPPORT_NETs.filter((value) => value.networkId !== 1).map(
        (value) => `eip155:${value.networkId}`,
    )

    const OPTION_METHODS = [...Object.values(MethodName)]
    const REQUIRED_METHODS = ['eth_sendTransaction', 'personal_sign']
    const REQUIRED_EVENTS = ['chainChanged', 'accountsChanged']
    const sessionParams = {
        namespaces: {
            eip155: {
                methods: REQUIRED_METHODS,
                chains: ['eip155:1'],
                events: REQUIRED_EVENTS,
                rpcMap:{},
            },
        },
        optionalNamespaces: {
            eip155: {
                methods: OPTION_METHODS,
                chains: OPTION_CHAINS,
                events: REQUIRED_EVENTS,
                rpcMap: PRC_LISTs,
            },
        },
    }

now, I was update modal SDK to  v1.0.0-rc.6, and MetaMask there are some something wrongs.
1. request wallet_addEthereumChain method in I'm Token(v<IP_ADDRESS>20), will receive error {"code": -32000, "message": "Unsupported methods."}
// request payload is here
{"method":"wallet_addEthereumChain","params":[{"chainId":"0x61","chainName":"Binance Smart Chain Testnet","nativeCurrency":{"name":"tBNB","symbol":"tBNB","decimals":18},"rpcUrls":["https://data-seed-prebsc-1-s3.binance.org:8545"],"blockExplorerUrls":["https://testnet.bscscan.com"]}]} {"code": -32000, "message": "Unsupported methods."}

2. change chain net not receive messge in I'm Token(v<IP_ADDRESS>20), and request eth_chainId method will get wrong chain net
3. request wallet_addEthereumChain method in MetaMask(v7.2.0 (1142)), will change chain net success, but when back to my app not receive request's Promise resolve and reject. it can receive chainChanged message.
4. connected  wallet and then reload app, and request personal_sign method in MetaMask(v7.2.0 (1142)),can jump into wallet but no modal show in wallet, long time after, back to my app will receive a error, but no any message
ERROR {"context": "client"}

5. use Web3Provider request eth_accounts method in Rainbow(1.8.23 (20)),  will receive empty accounts. and wallet_addEthereumChain also failed. In this wallet I can't the way add a custom chain net. so I don't test a sign message and other method.
6.  request wallet_addEthereumChain method in TrustWallet(1.8.23 (20)),  can't show a modal in wallet, and also can't the way add a custom chain net. so I don't test a sign message and other method.
These are the problems I have encountered so far, I have no idea how to deal them
I read the EthereumProvider code , EthereumProvider also used by IUniversalProvider, as same as modal-react-native , I will try to find the difference between the two at present,  I'll let you know if I find anything.

similar issue

Is this still happening? Can you check with the latest version of Metamask?

Closing until we have more info


Add get table base methods

Adds get_table and get_base to Api, Base, and Table classes.

Codecov Report

Merging #127 (1ddf655) into main (2ded552) will decrease coverage by 1.58%.
The diff coverage is 81.48%.

@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
- Coverage   84.14%   82.55%   -1.59%
==========================================
  Files          13       13
  Lines         555      579      +24
==========================================
+ Hits          467      478      +11
- Misses         88      101      +13

Impacted Files
Coverage Δ

pyairtable/api/base.py
52.77% <66.66%> (+1.26%)
:arrow_up:

pyairtable/api/table.py
97.56% <66.66%> (-2.44%)
:arrow_down:

pyairtable/api/api.py
89.09% <85.71%> (-0.71%)
:arrow_down:

pyairtable/api/auth.py
0.00% <0.00%> (-100.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Unclear default value for the Hamming Distance cut-off

Hi @grst!
I think it is not clear from the API documentation of the HammingDistanceCalculator whether the default of the cutoff parameter is None or 2:

Good catch! Actually both is true -- cutoff=None is the default value, but if cutoff is None, a default of 2 is selected.
Clearly the documentation needs to be improved.


Important: lighten up the docker image

Currently the image weights over 3 GB because of all the CUDA drivers for FAISS in multiarchitechtural build, this needs to be fixed

Possible solution: https://stackoverflow.com/questions/77205123/how-do-i-slim-down-sberts-sentencer-transformer-library


(WIP) Add udx packetsDroppedByKernel

Draft because I think the binding is bugged, so I wrote a test illustrating it


SX1309 should have the option to exclude checking private readonly fields

SX1309 currently examines fields that are:

private
Instance (not static)
Not const

Can we add "Not readonly" to that list (or provide a setting that would)?

I'm undecided on this one, but only when using a settings to control the behavior. Always excluding readonly will result in collection fields that are declared read only (a common practice) to be flagged, while they are still instance fields and should therefore start with an underscore.


Unable to delta_scan for delta lake on GCS

What happens?
delta_scan tried to access S3 bucket and failed even if I give GCS bucket file path.
To Reproduce
Insert GCS HMAC key https://duckdb.org/docs/guides/network_cloud_storage/gcs_import.html
$ INSERT INTO duckdb.secrets (type, key_id, secret)
  VALUES ('GCS', 'xx'x, 'yyy');
INSERT 0 1

# SELECT * FROM  delta_scan ('gs://databricks-xxx-unitycatalog/yyy') AS (color text,  price numeric);
ERROR:  (PGDuckDB/CreatePlan) Prepared query returned an error: 'IO Error: Hit DeltaKernel FFI error
(from: While trying to read from delta table: 'gs://databricks-xxx-unitycatalog/yyy/'): Hit error: 8 (ObjectStoreError)
with message (Error interacting with object store: Generic S3 error: Error after 10 retries in 2.43329041s,
max_retries:10, retry_timeout:180s, source:error sending request for url (https://s3..amazonaws.com/databricks-xxxx-unitycatalog/yyy/_delta_log/_last_checkpoint))

OS:
MacOS
pg_duckdb Version (if built from source use commit hash):
0.2.0
Postgres Version (if built from source use commit hash):
16
Hardware:
No response
Full Name:
Yohei
Affiliation:
Onishi
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - I cannot share the data sets because they are confidential
Did you include all code required to reproduce the issue?

[X] Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?

[X] Yes, I have

Hi @yohei1126! Thanks for the report. Just to double check, does the same work on vanilla DuckDB? (using the CLI for example?) Thanks!

@Y--  Hi, delta_scan work on vanilla DuckDB
https://duckdb.org/docs/extensions/delta.html


cgroups v1 cpus

initial, will add tests shortly. pretty sure this is on the right track let me know if it looks wrong so far.
Solves part of #9.

@reynn
nice work!  Could you please refer to this PR and add the corresponding integration tests in the same way? This is optional, but it would be great if you could add unit tests as well.
https://github.com/utam0k/youki/pull/16

Thanks @tsturzl this isn't yet complete, will work on it tonight and do the corrections and add testing.

hey @utam0k and @tsturzl sorry but I dont have time to finish this for at least a few weeks, work has gotten a bit crazy.


How to use? install?

So this is obviously a noob question.....How do I install and use this?  I don't see any instructions in the readme.  I'm sure I'm missing something completely obvious, but I appreciate any help here!  :)

Hey there @obcocav, you can find the download here - https://github.com/featherbear/NDI-Telestrator/releases
Please note that this project was a test exploration though, and I don't really have any future intentions of updating it or making changes (unless there becomes a personal need to)

Does this run on the PC then? I was looking for something that would run on my Android tablet, taking the NDI feed of a video, letting me draw over it and then sending that back to OBS via NDI. Something like we see in this video

Yeah this runs on the PC.
From that video (is that an iPad?) it seems like he is using some remote software to control a PC.
In theory this could be a native Android application, as NDI 5 supports both decode and encode of streams


ctr: move signals, resolver utility functions to commands package

move platform-specific signalMaps to commands package --> signals_linux.go, signals_windows.go, signals_unix.go
move signals-related functions to commands/signals.go
move resolver-related functions to commands/resolver.go
added 2 TODOs for later PR (after commands are moved)

Codecov Report

Merging #1689 into master will increase coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1689      +/-   ##
==========================================
+ Coverage   48.79%   48.99%   +0.19%
==========================================
  Files          27       27
  Lines        4070     4070
==========================================
+ Hits         1986     1994       +8
+ Misses       1666     1662       -4
+ Partials      418      414       -4

Impacted Files
Coverage Δ

metadata/snapshot.go
50.28% <0%> (+0.93%)
:arrow_up:

metadata/db.go
67% <0%> (+1.5%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


typo

Two comments:
"url – The url of the link to add" shout be "... to remove" on the "Remove a navigation link" verb.
Please explain how to remove the Dutch version of Pages what is translated to "Pagina's".
Just using the title "Pagina's" does not work. Probably because of the '
What is the escape character?
[Enter feedback here]

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

ID: 68267476-ee8d-7b95-446b-711ddb683da2
Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
Content: Site design JSON schema
Content Source: docs/declarative-customization/site-design-json-schema.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Hi,
This is fixed in pull request 3918
@andrewconnell , @VesaJuvonen , @IstvanYbema
Please review. Thank you!


Chapter 6, Basic Interactor isn't compiling

I imagine something has changed in the API, I'm getting these two errors now.  But it's only in the Chapter 6 file.  When I comment out this class, things seem to work.
BTW, XR Interaction Toolkit is very close to actual release!
Assets_UWVRP3Assets\Chapter06\Scripts\BasicInteractor.cs(8,49): error CS0115: 'BasicInteractor.ValidTargets': no suitable method found to override
Assets_UWVRP3Assets\Chapter06\Scripts\BasicInteractor.cs(4,14): error CS0534: 'BasicInteractor' does not implement inherited abstract member 'XRBaseControllerInteractor.validTargets.get'
using System.Collections.Generic;
using UnityEngine.XR.Interaction.Toolkit;

public class BasicInteractor : XRBaseControllerInteractor
{
    public override void GetValidTargets(List<XRBaseInteractable> validTargets) { }

    protected override List<XRBaseInteractable> ValidTargets { get; }
}

Yes, I should have avoided putting that kind of dependency into a book! For an alternative solution to gaze based interactions (e.g. for Google Cardboard) you can see the article i wrote last year and corresponding GitHub repository https://medium.com/@linojon/an-xr-cardboard-interactor-for-unity-eec6270be2e9. I will publish an addendum and update the GitHub projects after XR Interaction Toolkit 1.0 is officially released.

Yes, I should have avoided putting that kind of dependency into a book! For an alternative solution to gaze based interactions (e.g. for Google Cardboard) you can see the article i wrote last year and corresponding GitHub repository https://medium.com/@linojon/an-xr-cardboard-interactor-for-unity-eec6270be2e9. I will publish an addendum and update the GitHub projects after XR Interaction Toolkit 1.0 is officially released.


Import-DbaCsv - ensure consistency in the error handling

Type of Change

[x] Bug fix (non-breaking change, fixes #7122 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Updating the error handling for consistency reasons as mentioned in #7122
Commands to test

The integration tests cover this scenario.

Awesome, thank you!


Migrations: modify(column, type, null: false) generates wrong SQL syntax

We don't allow null nor default in modify for now.

Then the documentation needs to reflect that
On Tuesday, January 27, 2015, José Valim<EMAIL_ADDRESS>wrote:

Closed #409 https://github.com/elixir-lang/ecto/issues/409.
—
Reply to this email directly or view it on GitHub
https://github.com/elixir-lang/ecto/issues/409#event-225300253.

--
Y.
My company is hiring: https://trustatom.com/jobs

It has been updated too.


Specs not found in version 0.0.4

Following error appears in version nuvlabox/mqtt-fiware-bridge:0.0.4 :
mqtt-to-dataclay_1  |     super(MQTTtoDataClayBridge, self).__init__(**kwargs)
mqtt-to-dataclay_1  |   File "/opt/nuvlabox/mqtt_fiware_bridge/MFB.py", line 50, in __init__
mqtt-to-dataclay_1  |     self.fiware_models = self.map_all_fiware_models(self.pkg_fiware_specs)
mqtt-to-dataclay_1  |   File "/opt/nuvlabox/mqtt_fiware_bridge/MFB.py", line 94, in map_all_fiware_models
mqtt-to-dataclay_1  |     listed_under = pkg_resources.resource_listdir(self.this_package_name, search_at)
mqtt-to-dataclay_1  |   File "/usr/local/lib/python3.9/site-packages/pkg_resources/__init__.py", line 1148, in resource_listdir
mqtt-to-dataclay_1  |     return get_provider(package_or_requirement).resource_listdir(
mqtt-to-dataclay_1  |   File "/usr/local/lib/python3.9/site-packages/pkg_resources/__init__.py", line 1426, in resource_listdir
mqtt-to-dataclay_1  |     return self._listdir(self._fn(self.module_path, resource_name))
mqtt-to-dataclay_1  |   File "/usr/local/lib/python3.9/site-packages/pkg_resources/__init__.py", line 1605, in _listdir
mqtt-to-dataclay_1  |     return os.listdir(path)
mqtt-to-dataclay_1  | FileNotFoundError: [Errno 2] No such file or directory: '/opt/nuvlabox/mqtt_fiware_bridge/fiware/specs'

If I go inside the image via docker run -it --entrypoint /bin/sh nuvlabox/mqtt-fiware-bridge:0.0.4 and I type :
# ls /opt/nuvlabox/mqtt_fiware_bridge/fiware/specs
ls: cannot access '/opt/nuvlabox/mqtt_fiware_bridge/fiware/specs': No such file or directory

However if go inside version 0.0.1 via docker run -it --entrypoint /bin/sh nuvlabox/mqtt-fiware-bridge:0.0.4:
# ls /opt/nuvlabox/mqtt_fiware_bridge/fiware/specs
AgriFood     Building  Environment		Parking		    PointOfInterest  Transportation  WasteManagement  guidelines.md  index.md
Alert	     Device    IssueTracking		ParksAndGardens     README.md	     UrbanMobility   Weather	      howto.md	     ngsi-ld_faq.md
Aquaculture  Energy    KeyPerformanceIndicator	PointOfInteraction  StreetLighting   User	     gsma.md	      img	     ngsi-ld_howto.md

Originally posted by @dgasull in https://github.com/nuvlabox/mqtt-fiware-bridge/issues/2#issuecomment-831920175

thanks for noticing that.
I've changed the CI engine and on the new one (Github actions), the fiware submodule was not being recursively pulled during the build.
Should be fixed now in tag 0.0.5. Please check again ;)

Still not working in version 0.0.5 :(
 $ docker run -it --entrypoint /bin/sh nuvlabox/mqtt-fiware-bridge:0.0.5
 ls /opt/nuvlabox/mqtt_fiware_bridge/fiware/specs
ls: cannot access '/opt/nuvlabox/mqtt_fiware_bridge/fiware/specs': No such file or directory

And:
mqtt-to-dataclay_1  |   File "/usr/local/lib/python3.9/site-packages/pkg_resources/__init__.py", line 1605, in _listdir
mqtt-to-dataclay_1  |     return os.listdir(path)
mqtt-to-dataclay_1  | FileNotFoundError: [Errno 2] No such file or directory: '/opt/nuvlabox/mqtt_fiware_bridge/fiware/specs'

Maybe it's because fiware specs changed? They've deprecated some files and created new standards one month ago.

sorry, the tag was not up to date. should be fine now


[Equalizer] equalizeOnStack not working

How can we reproduce this bug?
docs Equalizer
equalizeOnStack not used in plugin equalizer
https://github.com/zurb/foundation-sites/issues/7223

This is all fixed up on the 6.1 branch, so i'll close this out. Thanks for always reporting issues and submitting PRs, @designerno1!


JWKs parse issue when using non standard exponent (not 3 or 65537)

As raised in https://github.com/istio/istio/issues/41729
If a JWK has an exponent different from 65537 or 3, the parsing fails with the following error:
"Jwks RSA [n] or [e] field is missing or has a parse error"
For example, parsing will fail for the following valid JWK:
{
 "keys": [
  {
      "n": "q9hO0xKd6KfjXRxzAzLYnV-o4wm7aRMSr27ajF2bDedVFMJ-G6Y01lRsSn0zTusBCbax10dEOMg1g_GEWWqG_hYYq2eQ0RAWHAEfUUZHacu1MrGUFFcmbRYlR_Q1lM-e-831yFFbDPZAIUpyN_8qZuVL1fN2cGRXNcAyVzrDqu2h1pdjQykyMGPKr9X3xxMZ-IHDhbnZjdeYBHJPvwic2G-_Wp1ZrHxBhUykZuAVS3RMFDH-pV6-_W0rOENv3tZmxBTTSGIGNHYGaMg_qrnVDZuNOv3XGv_McqlD0RFifqtCO5QQtCQAdwMXHxmv2SxC04LsFL3GgSh_G3otGhwItQ",
      "e": "Iw",
      "kty": "RSA",
      "alg": "RS256",
      "kid": "1u-zN2fkExpEMumSNIYBfV8XPjFPHalL8IM6mO285yE"
  }
 ]
}

I couldn't find any reference that the exponent must be 65537 or 3, even though 65537 is commonly used.
opened PR https://github.com/google/jwt_verify_lib/pull/95, which should fix the JWK validation. I'd appreciate if you could review it.

This is something I'm not familiar with. Let me try pulling in some crypto experts.
Based on https://crypto.stackexchange.com/a/3113

Only the Fermat primes 3,5,17,257,65537
have both properties, and all are common choices of 𝑒

Are you sure e can be any non-negative number?

In theory, e can be any non-negative number that is coprime to the Euler totient of n. In practice, the exponent should always be 65537, and even 3 should be discouraged, given Coppersmith attacks, and I don't think allowing different exponents is a good idea.

I agree that 65537 is the best practice. But this library is used for JWT validation, and I think it should accept all the valid exponent values (even if they are not the best practice/not secured enough).
In my case, the Idp service (external provider) uses different values for the exponent, which prevents us from using istio authentication. As the exponent is not 65537 or 3, we get the following error:
Jwks RSA [n] or [e] field is missing or has a parse error.

Supporting arbitrary values of e is also a DoS risk. BoringSSL won't accept any e over 33 bits for this reason. We're stuck being a bit more permissive than just 3 and 65537, but the constraints in this library are sound. I don't think it makes sense to change it.
Were RSA standardized correctly, we'd have just picked the one value of e as part of a parameter set and moved on with life.


Create resource from unsatisfied link

When referencing a non-existing object in my resource I would like an action to create that object - for example if I add a configMap reference to a Deployment to a configMap that doesn't yet exist - I would see the reference marked as an invalid link and should also have a "Create..." action that would open the "Create New Resource" dialog prefilled with the selected name, type of object, etc..

there could be other actions - for example "Select existing..." - perhaps we can have a generic UI for "intention actions" - in line with

This should be relatively easy using the right click (context) menu for unresolved links.

https://ant.design/components/dropdown/#components-dropdown-demo-context-menu


create-next-app (js): nix build Module parse failed: Unexpected token

Not sure if this is supposed to be supported or not.
nix shell "nixpkgs#nodejs"

npx create-next-app@latest test-next-dream

cd test-next-dream

rm -rf node_modules

nix flake init -t github:nix-community/dream2nix#simple

nix eval --impure --raw --expr 'builtins.currentSystem' > ./nix_systems && git add ./nix_systems

nix build -L

Output
test-next-dream> Failed to compile.
test-next-dream>
test-next-dream> ./pages/_app.js
test-next-dream> Module parse failed: Unexpected token (4:9)
test-next-dream> You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
test-next-dream> |
test-next-dream> | function MyApp({ Component, pageProps }) {
test-next-dream> >   return <Component {...pageProps} />
test-next-dream> | }
test-next-dream> |
test-next-dream> ./pages/index.js
test-next-dream> Module parse failed: Unexpected token (7:4)
test-next-dream> You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
test-next-dream> | export default function Home() {
test-next-dream> |   return (
test-next-dream> >     <div className={styles.container}>
test-next-dream> |       <Head>
test-next-dream> |         <title>Create Next App</title>
test-next-dream> > Build failed because of webpack errors
test-next-dream> npm ERR! code ELIFECYCLE
test-next-dream> npm ERR! errno 1
test-next-dream> npm ERR<EMAIL_ADDRESS>build: `next build`
test-next-dream> npm ERR! Exit status 1
test-next-dream> npm ERR!
test-next-dream> npm ERR! Failed at the<EMAIL_ADDRESS>build script.
test-next-dream> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
test-next-dream>
test-next-dream> npm ERR! A complete log of this run can be found in:
test-next-dream> npm ERR!     /build/.npm/_logs/2022-08-09T23_06_58_979Z-debug.log
test-next-dream>
error: builder for '/nix/store/hwgmill09lczncwrairvhy40sdl1ra6a-test-next-dream-0.1.0.drv' failed with exit code 1;
       last 10 log lines:
       > npm ERR! errno 1
       > npm ERR<EMAIL_ADDRESS>build: `next build`
       > npm ERR! Exit status 1
       > npm ERR!
       > npm ERR! Failed at the<EMAIL_ADDRESS>build script.
       > npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
       >
       > npm ERR! A complete log of this run can be found in:
       > npm ERR!     /build/.npm/_logs/2022-08-09T23_06_58_979Z-debug.log
       >
       For full logs, run 'nix log /nix/store/hwgmill09lczncwrairvhy40sdl1ra6a-test-next-dream-0.1.0.drv'.

I think this should definitely be supported. It seems like some loader dependency is missing. Do you know which one? For some reason the problem does not exist in the devShell using next dev.

I'm getting exactly same behaviour, seems related to webpack error. Sadly i can not share source repo because is an unreleased project.
But I can give you some context:

Original repo with package.json and yarn.lock. FAIL.
If I generate a package-lock.json then builds OK.

I think this should definitely be supported. It seems like some loader dependency is missing. Do you know which one?

I wonder if it's a css loader. the strace has:
[...]
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/favicon.ico", {st_mode=S_IFREG|0644, st_size=25931, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/favicon.ico", {st_mode=S_IFREG|0644, st_size=25931, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 openat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/favicon.ico", O_RDONLY|O_CLOEXEC) = 4
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/vercel.svg", {st_mode=S_IFREG|0644, st_size=1101, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/vercel.svg", {st_mode=S_IFREG|0644, st_size=1101, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 openat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/public/vercel.svg", O_RDONLY|O_CLOEXEC) = 4
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles", {st_mode=S_IFDIR|0755, st_size=52, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles", {st_mode=S_IFDIR|0755, st_size=52, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 openat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 4
422583 newfstatat(4, "", {st_mode=S_IFDIR|0755, st_size=52, ...}, AT_EMPTY_PATH) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/Home.module.css", {st_mode=S_IFREG|0644, st_size=1865, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/Home.module.css", {st_mode=S_IFREG|0644, st_size=1865, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 openat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/Home.module.css", O_RDONLY|O_CLOEXEC) = 4
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/globals.css", {st_mode=S_IFREG|0644, st_size=407, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 newfstatat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/globals.css", {st_mode=S_IFREG|0644, st_size=407, ...}, AT_SYMLINK_NOFOLLOW) = 0
422583 openat(AT_FDCWD, "/home/bbigras/dev/test-next-dream/styles/globals.css", O_RDONLY|O_CLOEXEC) = 4
422595 +++ exited with 0 +++
[...]

❯ npm ls
<EMAIL_ADDRESS>/home/bbigras/dev/test-next-dream
├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>└── UNMET DEPENDENCY<EMAIL_ADDRESS>
npm ERR! code ELSPROBLEMS
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/bbigras/.npm/_logs/2022-08-13T14_39_11_582Z-debug-0.log

# I did something here. Not sure what

$ npm ls
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
<EMAIL_ADDRESS>/home/bbigras/dev/test-next-dream
├─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>│ ├─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│ │ └── UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│ │ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ │ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ │ └── UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ └── UNMET DEPENDENCY<EMAIL_ADDRESS>├─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│ └─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│   └── UNMET DEPENDENCY<EMAIL_ADDRESS>├─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│ ├── UNMET DEPENDENCY<EMAIL_ADDRESS>│ └─┬ UNMET DEPENDENCY<EMAIL_ADDRESS>│   └── UNMET DEPENDENCY<EMAIL_ADDRESS>└── UNMET DEPENDENCY<EMAIL_ADDRESS>
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! extraneous<EMAIL_ADDRESS>/home/bbigras/dev/test-next-dream/node_modules/typescript
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>

tried it with my own next-js project (setup: next + typescript + material ui)
Ran into the same error. Replaced the build script in package.json with:
npm ls && next build
the first error that comes up is:
+--  extraneous error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>
see also last lines here:
build.log

fixed by https://github.com/nix-community/dream2nix/pull/337

Thanks!!


vague, manual requirements

It isn't clear which versions of the required libraries to install. I'd appreciate a requirements.txt to help me create an appropriate environment.
After making a clean virtualenv with python 2.7.12 and then running "pip install theano" and "pip install keras" I get this output from "python train.py":
Using TensorFlow backend.
Traceback (most recent call last):
  File "train.py", line 27, in <module>
    from lib.net import Net
  File "/home/mungojelly/code/from-github/soundcube/lib/net.py", line 15, in <module>
    import keras.models
  File "/home/mungojelly/.virtualenvs/soundcube2/lib/python2.7/site-packages/keras/__init__.py", line 2, in <module>
    from . import backend
  File "/home/mungojelly/.virtualenvs/soundcube2/lib/python2.7/site-packages/keras/backend/__init__.py", line 67, in <module>
    from .tensorflow_backend import *
  File "/home/mungojelly/.virtualenvs/soundcube2/lib/python2.7/site-packages/keras/backend/tensorflow_backend.py", line 1, in <module>
    import tensorflow as tf
ImportError: No module named tensorflow

After then saying "pip install tensorflow" I get this error instead:
Using TensorFlow backend.
Traceback (most recent call last):
  File "train.py", line 50, in <module>
    main()
  File "train.py", line 31, in main
    net = Net(Net.TRAIN, autosave=True)
  File "/home/mungojelly/code/from-github/soundcube/lib/net.py", line 64, in __init__
    self.data = utils.load_data(split=self.val_split)
  File "/home/mungojelly/code/from-github/soundcube/lib/utils.py", line 373, in load_data
    return load_all(target_dir, split)[-4:]
  File "/home/mungojelly/code/from-github/soundcube/lib/utils.py", line 355, in load_all
    z = normalize(z)
  File "/home/mungojelly/code/from-github/soundcube/lib/utils.py", line 402, in normalize
    s = s.reshape(shape[0], -1)
ValueError: cannot reshape array of size 0 into shape (0,newaxis)

This project looks interesting, I'm looking forward to trying it out, thanks!

Yes your problem I believe is with your ~/.keras/keras.json (or analogous file), which probably has "tensorflow" where it should say "theano." (And I would personally stick with Theano—TensorFlow works, but last I checked required a little fiddling—see http://stackoverflow.com/questions/40046619/keras-tensorflow-gives-the-error-no-attribute-control-flow-ops.) Anyway "theano" was the default when I first wrote that, but they changed it at some point. Which, yes, should probably be documented somewhere. This issue aside though I think it should work with any version of Keras >= 1.0.
Glad to see you are interested in it though FYI if you don't have a GPU and CUDA installed you are in for a slow, slow process.


version 2.0 - update docs and tag

I'm seeing that the pypi page is showing a 2.0 version, but the latest tag is 1.1.2 and also the docs say 1.1.2.
I'm looking at the latest commits but find no reference for this 2.0 version. Is the version jump legit? if so, please update the code and docs to show and specify any breaking or non backwards-compatible changes.

Thanks! Are there any major or breaking changes we should be aware of?

@newearthmartin  https://django-paypal.readthedocs.io/en/stable/release_notes.html


--port ignored on windows

On Windows 10 Aniversary Update (1607):
> jumpsuit watch --port 8800
     _                       _ _
    |_|_ _ _____ ___ ___ _ _|_| |_
    | | | |     | . |_ -| | | |  _|
   _| |___|_|_|_|  _|___|___|_|_|
  |___|         |_|

▸   running at http://localhost:8000
✓ (19ms)
▸   building... ✓ (518ms)

and it doesn't listen on port 8800 as requested (ie. not just a message issue)
Behaves the same way in both powershell and cmd

@thorerik It looks like we're having problems on Windows. Are you coming across the same issues we're talking about in https://github.com/jumpsuit/jumpsuit/issues/26?

Yep, that as well, but generating the app.js from ubuntu userland and starting with jumpsuit serve works, but --port is ignored here as well.

the serve command gets the argv but does nothing with them, just takes the CONFIG and uses that to start the server.

Should be fixed via https://github.com/jumpsuit/jumpsuit/pull/40. We'll release this soon, let us know if the problem persists and we can reopen this issue.


Latest Version 0.4 just loaded with HACS and not working in HA 117.6

I saw that there was a new version of homeassistant _ecowitt in HACS so loaded it and this is the result.
Previous version of this worked on HA117.6

I tried rolling back but it's still broken.
I rebooted my NUC... Still broken
I rebooted my Ecowitt station...  Partial reporting after few minutes

You are using 0.4?  With hass 0.117.6?   You didn't accidentally get the conflig_flow branch did you?
Thats confusing, I'm running 0.117.5 with the 0.4...  What version were you running before?

This morning I updated to 117.6 then I saw that there was a HACS update for ECOWITT so did that
Since then I have uninstalled and reinstalled ECOWITT

What does restored mean?

Can you grep for "ecowitt" from your homeassistant log and paste everything here.  It would be especially helpful if you have the logging set to at least info.

This is the error I have:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line 272, in handler
weather_data = self.convert_units(data_copy)
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line 165, in convert_units
data["windspdkmh_avg10m"] = float(data["windspdmph_avg10m"]
TypeError: float expected at most 1 argument, got 2

I found the same.
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py",
line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line
272, in handler
weather_data = self.convert_units(data_copy)
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line
165, in convert_units
data["windspdkmh_avg10m"] = float(data["windspdmph_avg10m"]
I also would like to have explained the "restored" flags.  I read where
other have had problems with this flag being set when data is not available
and then never being able to get it again
On Mon, 16 Nov 2020 at 02:22, cpuks<EMAIL_ADDRESS>wrote:

This is the error I have:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py",
line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line
272, in handler
weather_data = self.convert_units(data_copy)
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line
165, in convert_units
data["windspdkmh_avg10m"] = float(data["windspdmph_avg10m"]
TypeError: float expected at most 1 argument, got 2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/garbled1/homeassistant_ecowitt/issues/28#issuecomment-727596257,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFUCPVST47JPRRHQGMUMYDSP7555ANCNFSM4TVZZQRQ
.

--
CheersRT

Had to revert to 0.2 and apply necessary changes. Hopefully this will be sorted :-) Thanks for this integration :-)

ok.. hrmm..  I must be reading this value incorrectly...
I don't suppose you could run a tcpdump -A port 4199 on your controller and capture a line of the ecowitt sending data?  Mine doesn't produce that value, but if you give me the raw data it's sending, I can plug it into my simulator, and test directly.
There is also a main.py in pyecowitt that can be run as a simple listener if you shut hass down for a few minutes to capture one.  Basically I just need to see one line of raw data so I can duplicate the issue.

Hi,
I have the same issue since Nov 14th (I believe). Must have been after upgrading to v0.4.
`Logger: aiohttp.server
Source: /usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py:355
First occurred: November 14, 2020, 9:29:42 PM (1926 occurrences)
Last logged: 4:06:12 PM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line 272, in handler
weather_data = self.convert_units(data_copy)
File "/usr/local/lib/python3.8/site-packages/pyecowitt/ecowitt.py", line 165, in convert_units
data["windspdkmh_avg10m"] = float(data["windspdmph_avg10m"]
TypeError: float expected at most 1 argument, got 2`
HomeAssistant is v0.117.6
Running in Docker on unraid
WeatherStation is a Froggit HP1000SE
configuration.yaml:
ecowitt:  port: 4199  barounit: metric  windunit: metric  rainunit: metric  windchillunit: hybrid
Anything I can do to help?

16:30:27.116104 IP sonoff-5129.unifi.localdomain.23996 > homeassistant.unifi.localdomain.4199: Flags [S], seq 383605278, win 5840, options [mss 1460], length 0
<EMAIL_ADDRESS>..X...Xf]..g..Z.....`...o.........
16:30:27.116137 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [S.], seq<PHONE_NUMBER>, ack 383605279, win 64240, options [mss 1460], length 0
E<EMAIL_ADDRESS>16:30:27.125755 IP sonoff-5129.unifi.localdomain.23996 > homeassistant.unifi.localdomain.4199: Flags [P.], seq 1:677, ack 1, win 5840, length 676
<EMAIL_ADDRESS>/data/report/ HTTP/1.1
HOST: <IP_ADDRESS>
Connection: Close
Content-Type: application/x-www-form-urlencoded
Content-Length: 534

PASSKEY=9AE62FC9C0C5AB338AD9DA094196FFF1&stationtype=EasyWeatherV1.5.4&dateutc=2020-11-16+15:30:24&tempinf=68.7&humidityin=52&baromrelin=29.785&baromabsin=29.785&tempf=46.4&humidity=94&winddir=260&winddir_avg10m=260&windspeedmph=0.0&windspdmph_avg10m=0.0&windgustmph=0.0&maxdailygust=6.9&rainratein=0.000&eventrainin=0.118&hourlyrainin=0.000&dailyrainin=0.118&weeklyrainin=0.118&monthlyrainin=0.378&yearlyrainin=6.268&solarradiation=0.00&uv=0&soilmoisture1=0&wh65batt=0&wh25batt=0&soilbatt1=1.5&freq=868M&model=HP1000SE-PRO_Pro_V1.6.0
16:30:27.125790 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [.], ack 677, win 63564, length 0
E..(.U@.@..(..Xf..X..g].......\.P..L2m..
16:30:27.127905 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [P.], seq 1:170, ack 677, win 63564, length 169
E....V<EMAIL_ADDRESS>200 OK
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Date: Mon, 16 Nov 2020 15:30:27 GMT
Server: Python/3.8 aiohttp/3.6.2
Connection: close

16:30:27.128074 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [P.], seq 170:172, ack 677, win 63564, length 2
E..*.W<EMAIL_ADDRESS>16:30:27.129996 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [F.], seq 172, ack 677, win 63564, length 0
E..(.X<EMAIL_ADDRESS>16:30:27.130904 IP sonoff-5129.unifi.localdomain.23996 > homeassistant.unifi.localdomain.4199: Flags [.], ack 172, win 5669, length 0
E..(.Z@...."..X...Xf]..g..\....^P..%j:........
16:30:27.132065 IP sonoff-5129.unifi.localdomain.23996 > homeassistant.unifi.localdomain.4199: Flags [F.], seq 677, ack 173, win 5668, length 0
E..(.[@....!..X...Xf]..g..\...._P..$j9........
16:30:27.132085 IP homeassistant.unifi.localdomain.4199 > sonoff-5129.unifi.localdomain.23996: Flags [.], ack 678, win 63564, length 0
E..(.Y<EMAIL_ADDRESS>

thank you!  I'll plug this data into my simulator and fire it against a test instance hopefully tonight..

I pushed an untested fix to pyecowitt which should resolve this.. will test later.

In theory, if you update pyecowitt to 0.11 manually, it will fix this issue.

@garbled1 , I don't quite follow, could you a bit more specific?

You need to update the python library pyecowitt to 0.11.  I'm not sure how one would do this with docker or any of the other methods.. I only use a venv...  You might be able to force it by changing the manifest.json in your custom_components/ecowitt directory to state it needs 0.11..  right now it should be set to 0.10.  When I do the testing later I'll publish a new version to hacs, but for now, I think this fix will work if you just want to try or want it working quicker.  :)

thanks, changing it in the manifest.json worked. Thanks 👍

Cheers for digging out the problem - manifest does the job as pax85 already mentioned.

Oh good, I'll have to remember that.  Let me know if the fix works.  In theory 0.4 with pyecowitt 0.11 should function correctly.

Yes  I made this change as pax85 suggested and now mine works as well.
[image: image.png]
On Tue, 17 Nov 2020 at 10:29, Tim Rightnour<EMAIL_ADDRESS>wrote:

Closed #28 https://github.com/garbled1/homeassistant_ecowitt/issues/28
via 6b43a20
https://github.com/garbled1/homeassistant_ecowitt/commit/6b43a20932fea5da0bd0c4e230c1cc116caa727c
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/garbled1/homeassistant_ecowitt/issues/28#event-4002940854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFUCPV63TSM4YVDYFHHEGLSQG7VHANCNFSM4TVZZQRQ
.

--
CheersRT

I released 0.4.1 that has this fix builtin.


Facebook failed with error 500

Error message: Failed to submit captcha response back to Facebook
Query string: action=display&bridge=Facebook&u=medialysephotography&media_type=all&format=Html

Duplicate of #573


Support BERTModel (first encoder-only embedding model)

SUMMARY:

built on top of https://github.com/vllm-project/vllm/pull/5447 (co-author: laishzh)
introduces Encoder-Only models (BERT - tested with https://huggingface.co/BAAI/bge-base-en-v1.5 to match sentence-transformers implementation)
introduces Encoder-Only attention for XFORMERS backend.

Note: this PR requires setting the VLLM_ATTENTION_BACKEND=XFORMERS variable to run. We throw a loud error if it is not set.
TODO:

add end-to-end testing with MTEB
test tp>1

FOLLOW UPS:

refactor to extract some of logic out of XFORMERS. The logic is very complex right now.
support other attention backend

FIX #5179
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

I see both #5179 and this PR are being worked on. Which one should we review?

We need a follow up to clean up the XFormersAttention

I can't say to the implementation of the model (don't have time to compare it against HF), but nothing really jumps out at me from a brief look. If the tests pass then it's probably fine.

I have a test that compares against the hf implementation (via sentence-transformers)

Is it intentional to not include this on the docs yet?

Is it intentional to not include this on the docs yet?

Yes I think we should get #9388 in before we advertise this


multi root

Issue created from code comment with imdone.io

TODO @Ben multi root id:27
src/vs/code/electron-main/windows.ts:769
@imdone - Fast and easy task management for programmers. imdone.io

Issue closed by removing a comment.

TODO @Ben multi root id:27 gh:43
src/vs/code/electron-main/windows.ts:769
@imdone - Fast and easy task management for programmers. imdone.io