[promptflow][internal] Upgrade Swagger for retrieving Cosmos token

Description
This PR upgrades Swagger client for API to retrieve Cosmos token, also include trace operations in Azure PFClient
Current experience is: pf._traces._get_cosmos_db_token(container_name=<container-name>)
All Promptflow Contribution checklist:

[x] The pull request does not introduce [breaking changes].
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.
[ ] Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: suggested workflow.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

@microsoft-github-policy-service agree


Selector swallows errors

Describe the bug
Query selector swallows any and all errors (syntax, type, ...) occurring in selector body
To Reproduce
Declare query with selector fn
const query = useQuery(
    "todos",
    () => fetch("https://jsonplaceholder.typicode.com/posts").then((response) => response.json()),
    {
        select: (data) => {
            throw new Error("ooops");
        }
    }
);

Expected behavior
query.isError === true
// and related flags to reflect same

or at least console log to appear, giving some heads up what to fix.
Code
If applicable, add screenshots to help explain your problem.

okay, I debugged this a bit:
when an error is thrown in the select function, it is caught in query.ts:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/query.ts#L406-L413
and the query is put into error state. after that, we try to inform all the subscribers about this, which again triggers the select function, but this time, the errors will be propagated to the "next" catch (since we are already in a catch), which is this:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/queryObserver.ts#L269-L271
so the noop swallows the error. not really sure what a good way around this would be. another try/catch around the dispatch in the catch block in query.ts would probably work, as the important part is the error propagation:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/query.ts#L430-L431
if (!(isCancelledError(error) && error.silent)) {
+ try {
     this.dispatch({
       type: 'error',
       error,
     })
+ } catch { }
}

I quickly  tried this out, it seems to show the correct error in the console then:

I'd like to wait on some input from @tannerlinsley or @boschni though, since this would still swallow errors that happen in the error dispatch only.

okay, I debugged this a bit:
when an error is thrown in the select function, it is caught in query.ts:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/query.ts#L406-L413
and the query is put into error state. after that, we try to inform all the subscribers about this, which again triggers the select function, but this time, the errors will be propagated to the "next" catch (since we are already in a catch), which is this:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/queryObserver.ts#L269-L271
so the noop swallows the error. not really sure what a good way around this would be. another try/catch around the dispatch in the catch block in query.ts would probably work, as the important part is the error propagation:
https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/query.ts#L430-L431
if (!(isCancelledError(error) && error.silent)) {
+ try {
     this.dispatch({
       type: 'error',
       error,
     })
+ } catch { }
}

I quickly  tried this out, it seems to show the correct error in the console then:

I'd like to wait on some input from @tannerlinsley or @boschni though, since this would still swallow errors that happen in the error dispatch only.

Feel free to open a PR with a potential fix and we can discuss more there.

Feel free to open a PR with a potential fix and we can discuss more there.


Type error in 2.1.0

Update caused type error in the following function when using the example code from the readme. This works fine for me in 2.0.1.
function fileAccepted(file, accept) {
    var isAcceptable = file.type === 'application/x-moz-file' || accepts(file, accept);
    return [isAcceptable, isAcceptable ? null : getInvalidTypeRejectionErr(accept)];
}

accepts(file, accept) expects a function, should we be setting up the code with a callback?

I encountered the same issue, and after spending hours on it, I decided to compare the package-lock files from earlier commits.
And found one difference.
vue3-dropzone: ^2.0.1
Replaced version
"node_modules/vue3-dropzone": {
      "version": "2.1.0",
      "resolved": "https://registry.npmjs.org/vue3-dropzone/-/vue3-dropzone-2.1.0.tgz",
      "integrity": "sha512-UwVUgN5ckew72GlKqRKYHo4PkFyihONjxIIAkGFHj24pjrJmrRAz+9YnDTYaBmKuq9KH0YB5y31MtaETLahLOA==",
      "dependencies": {
        "attr-accept": "^2.2.2",
        "file-selector": "^0.2.4"
      },
      "peerDependencies": {
        "vue": ">=3"
      }
    },

With following:
  "node_modules/vue3-dropzone": {
    "version": "2.0.1",
    "resolved": "https://registry.npmjs.org/vue3-dropzone/-/vue3-dropzone-2.0.1.tgz",
    "integrity": "sha512-jY36ZhIpGCxyok6cKxFb2s9s15c1KXmLHxcHzHhjoPzZ5IHW7+2RrnYUenCdq88ym66KyknscNkJYJzh3C23hw==",
    "dependencies": {
      "attr-accept": "^2.2.2",
      "file-selector": "^0.2.4"
    },
    "peerDependencies": {
      "vue": ">=3"
    }
  },

This is a temporary solution, I will be waiting for the fix, thanks

@Cameron1818 Could you show me more details like sceenshot on ts error?
accepts(file, accept) is a function, which is imported from 'attr-accept' lib

@Yaxian I attached the error screenshot as well as my package.json & package-lock.json.
When I do an npm update & get dropzone 2.1.0, things start breaking, let me know if you need anything else?
Uncaught runtime errors:
ERROR
attr_accept__WEBPACK_IMPORTED_MODULE_3__ is not a function. (In 'attr_accept__WEBPACK_IMPORTED_MODULE_3__(file, accept)', 'attr_accept__WEBPACK_IMPORTED_MODULE_3__' is an instance of Object)
fileAccepted@
@
forEach@[native code]
@
![Skærmbillede 2023-08-22 kl  08 45 34](https://github.com/Yaxian/vue3-dropzone/assets/96175955/7510cc4b-28b6-45f4-917d-524a34506de5)
<img width="1434" alt="Skærmbillede 2023-08-22 kl  08 46 11" src="https://github.com/Yaxian/vue3-dropzone/assets/96175955/a74dc1d5-b889-48e5-998e-665e8d1e2c86">

@dbcoder14
Is there attr-accept lib in your node_modules?
Try rm -rf node_modules && yarn install to download attr-accept

#25

@Cameron1818  @dbcoder14
Thanks, please try<EMAIL_ADDRESS>to fix this problem


[Pilot] Adding support for config-backed service registry

Adding a new "Config" service registry that is backed by the provided
config store. The service registry will be updated via events for
ServiceEntry CRDs. This will allow the testing framework to eliminate
the dependency on k8s entirely and use the file-based config store as
the backend for the service registry.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm
On Tue, Jun 5, 2018 at 12:07 PM Jason Young<EMAIL_ADDRESS>wrote:

@ayj approved this pull request.
/lgtm
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/6038#pullrequestreview-126110550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJGIxheo8uc8aVFBA9ROkm5spTTx8vjIks5t5tbygaJpZM4UbYfJ
.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj, kyessenov, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj,kyessenov,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

With the service registry options, can I have multiple sources of information? For instance a file-based registry + a k8s registry?

/test istio-pilot-e2e-envoyv2-v1alpha3

/test e2e-bookInfoTests-v1alpha3

/test e2e-bookInfo-envoyv2-v1alpha3

@ayj @rshriram looks like I still need an lgtm ... you mind?

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj, kyessenov, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj,kyessenov,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Fixes #5974

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test e2e-simple

prow/istio-pilot-e2e.sh
bebc9738013b16338c21ebcb579768cea44d39e1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


FilterField and FilterValue not working

I can assign a dialog form field a lookup and have the drop-down display all the items correctly. When I add
this.form.Hmbs_Subscriber_Skey.filterField = "Hmbs_Issuer_Id";
this.form.Hmbs_Subscriber_Skey.filterValue = Hmbs_Issuer_Id; //value is correct prior to this statement
Q.reloadLookup("Settings.HmbsSubscriber");
to afterLoadEntity() for the dialog, the dialog displays no items although I know there is one that should be displayed. I'm not sure how else to filter this. Thank you!

I do not believe I can use a cascade because the item to cascade from is hidden and I get an error that an element with the id cannot be found...


TagHelper Intellisense not working in Area Views folder

Using Visual Studio 2017, TagHelper intellisense works in the default Views folder, but it does not work in the Vieuws folder in an Area. See also: http://stackoverflow.com/questions/43269184/areas-view-tag-helper-intellisense-no-use-in-asp-net-core-vs2017#

@svdoever - are you using VS2017 RTM, or do you have Update 1, Update 2, or Update 3 Preview 1 installed? If you could show what's in VS's "Help/About" dialog that would be helpful!
@NTaylorMullen @rynowak - any ideas?

No idea off the cuff, we need to try this out and see if we can reproduce it.

resolve is by just add this code at the top of the cshtml file:
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers

Don't know what changed, but the intellisense works now as advertised. Sorry for my mistake.

I have the same problem. Reading this post it means I have to add "@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers" to all my .cshtml files within the Areas folder? OMG!
(It comes already in _ViewImport.cshtml by default in ASP.Net Core 1.1).

@wgutierrezr I don't think that's the intended behavior, but there might be a bug that we fixed in that scenario that perhaps isn't available publicly yet.
@rynowak - thoughts?

If you have a _ViewImports.cshtml file within your Areas folder that has the @addTagHelper, that should work.

There should be no change here to how this behaves in 2.0.0. You need to have an @addTagHelper in scope in your views.
I'm going to close this issue again since it's not clear what exactly it's tracking. If anyone is having a similar problem please open a new issue and provide a clear description of what is happening.


Scale issue after after an upgrade

INFO    Update the object of StatefulSet {"controller": "risingwave", "controllerGroup": "risingwave.risingwavelabs.com",
"controllerKind": "RisingWave", "RisingWave": {"name":"sv-example","namespace":"default"},
"namespace": "default", "name": "sv-example", "reconcileID": "af3b8e50-83df-4d09-a973-921b2dde468a",
"generation": 4, "action": "SyncMetaStatefulSets", "component": "compactor", "group": "",
"object": {"namespace": "default", "name": "sv-example-meta"}, "generation": 4}

ERROR   Reconciler error {"controller": "risingwave", "controllerGroup": "risingwave.risingwavelabs.com",
"controllerKind": "RisingWave", "RisingWave": {"name":"sv-example","namespace":"default"},
"namespace": "default", "name": "sv-example", "reconcileID": "af3b8e50-83df-4d09-a973-921b2dde468a",
"error": "unable to sync object: StatefulSet.apps \"sv-example-meta\" is invalid: spec:
Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden"}]}

kubectl scale --replicas=2 rwsv/sv-example-frontend will cause this error after upgrading the operator and crds from v0.2.5 to the latest one.

The issue is caused by the breaking change brought in #344. There's no plan to fix it. If you encounter the same issue, please try to delete the meta StatefulSet manually, e.g.,
kubectl delete sts sv-example-meta

The operator will recreate one later.

How can we reproduce this locally? How can we test the PR by @Flpha0830 ?
Can we just create a RW tenant using an OP prior to https://github.com/risingwavelabs/risingwave-operator/pull/344 then upgrade the OP to the version provided by @Flpha0830 and then run kubectl scale --replicas=2 rwsv/sv-example-frontend?

How can we reproduce this locally?

make run local old version operator
kubectl apply rw
stop the old version operator and make run local a new version operator
update rw (eg. kubectl scale)

Can we just create a RW tenant using an OP prior to #344 then upgrade the OP to the version provided by @Flpha0830 and then run kubectl scale --replicas=2 rwsv/sv-example-frontend?

Please set EnableForceUpdate=true in the feature gates. Enabling this feature will recreate a new meta node. It should be the same as kubectl delete sts sv-example-meta

#387 makes it possible to fix the potential incompatibility by setting the EnableForceUpdate feature gate. Thanks a lot. I'll close the issue.


Update Project “cliniccases-law-school-case-management-software”

Automatically generated by Netlify CMS

👷 Deploy Preview for ninahorne processing.
🔨 Explore the source changes: 0fd8e26a2b4775f0b23ea65561a0be77a4e83954
🔍 Inspect the deploy log: https://app.netlify.com/sites/ninahorne/deploys/615b7d053331a00008d8d346


Consolidate Neptune and RDS backends

Despite being documented as two distinct services (with two distinct boto3 clients), the Neptune and RDS services share a single AWS backend (RDS).  This is reflected in the botocore service definition for Neptune, which lists rds as its endpoint.  Calling the DescribeDBClusters API method with either the neptune or rds boto3 client results in the exact same list of clusters--no filtering is done on the AWS backend.  Neptune clusters are commingled with Aurora clusters.
@bblommers I think this makes more sense than trying to separate these services (and it prevents a lot of code duplication), but I want to get your opinion since you originally implemented/split out the Neptune service. (As I continue to work on improving the RDS backend overall, I do plan to handle some of the if self.engine == "neptune conditionals in a more elegant way.)

@bpandola It is much cleaner like this, with RDS handling everything. If I remember correctly, I did try this approach first, but ran into some problems differentiating when a call came from Neptune and when from RDS. I don't remember exactly what went wrong, but based on this PR, it does work, so I'm more than happy to go ahead with this approach.

@bblommers

We would need to find a different approach for the implementation coverage script, to document that RDS coverage == Neptune coverage. That doesn't have to be now, or even as part of this PR, just noting it as an FYI.

Good catch.  I did push an additional commit to fix the implementation coverage script (it was failing before).  I think it should work fine now, with no additional work required.


No + for adding desired properties

Type of issue

[x ] Bug
[ ] New feature
[ ] Improvement

Description
The user should be able to add Desired properties, similar to how they add Tags.

Where is this happening?

Adding properties was indeed in scope as you mention Tim. Caitlin is updating the mocks now.
The way I am thinking about it is:

Simulated devices: you add a new property and that property turns into a reported property instantly.
Physical devices: you add a new property and that property shows up as “Synching” until the client application has been updated to reflect the change (same as when you change property values).  Typically we wouldn’t recommend doing this as the cleanest way to do it. IMHO what makes more sense in a production environment is different versions of a device model that change with the client app. For example, when you move from 0.1 to 0.2 version, the twin is updated in the solution the first time the client app sends that new version and new properties show up in the model.

I do think the value is mostly for simulation, but it’s worth it.


Invalid WebSocket requests cause 502 responses

In our production infrastructure, websocket requests that should result in an error (like a 404) end up returning a 502 Bad Gateway An example of such a request is an attempt to subscribe to a nonexistent subgraph id.
The 502 is ultimately caused by graph-node rather rudely closing the connection without producing any output. That in turn is caused by the old version of tungstenite (0.6.1) we are using. We need to update tungstenite to a version that has this fix in it.

Tungstenite was upgraded, this is fixed.


Could Ctrl-T override .gitignore when starting from an ignored path?

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
This is not a bug in fzf, but it's a non-optimal UX. I notice when I'm in my project root and I type
$ ls node_modules<Ctrl-T>my-node-module

I see no matches. If instead I do
$ cd node_modules; ls<Ctrl-T>my-node-module

I see the expected files. This is obviously because my FZF_CTRL_T_COMMAND is ag -g "", and ag is ignoring stuff in my .gitignore, which includes node_modules/.
Thing is, that's usually exactly what I want. But clearly when I type $ ls node_modules/ I do want to search in node_modules/. Is there any way this could be made to work, either with some fancier ag options (or a different command altogether), or by some modification to fzf (doing cd node_modules behind the scenes, perhaps)?

Try https://github.com/junegunn/fzf#fuzzy-completion-for-bash-and-zsh

It works! (In Bash; not in zsh using the oh-my-zsh fzf plugin, but that's a separate issue I'll have to look into.) So it seems like the fuzzy-completion is using the FZF_CTRL_T_COMMAND. I guess I'm a little confused why we have two different ways to do this (unless it's to solve this exact issue) -- is there more information on the difference between the two methods?
So the built-in fuzzy-completion has the same root issue, though; either the underlying command uses .gitignore and so can't ever see into node_modules/, or it doesn't and shows me results from node_modules/ when I don't want them. I can of course just remember to use **<Tab when I want to see all files and <Ctrl-T> otherwise.
But I'm a dreamer! I just added
[[ -d "${LBUFFER##* }" ]] && cd "${LBUFFER##* }"

to __fsel() in keybindings.zsh and it seems to do what I want, except that unsurprisingly it breaks on directory names with spaces. My zsh-fu is weak and I'm not sure if there's a way to fix that without doing some annoying parsing for quotes and backslashes.

I guess I'm a little confused why we have two different ways to do this (unless it's to solve this exact issue) -- is there more information on the difference between the two methods?

CTRL-T is the simpler one that works without any context information, so we can easily configure its behavior with a static $FZF_CTRL_T_COMMAND variable.
Fuzzy completion is a more generic version with much more complexity. Its behavior is determined by what you have typed so far on the command line and the position of your cursor; cd /foo/bar/**<tab> is different from ls /foo/bar/**<tab> or kill **<tab> or ssh **<tab> (CTRL-T would work the same in all cases). So we need to use functions to customize how it works: https://github.com/junegunn/fzf#settings

_fzf_compgen_path and fzf_compgen_dir for generating the candidate list for the basic file and directory completion
_fzf_comprun for using different options of fzf depending on the command
_fzf_complete_COMMANDNAME for custom completion for COMMANDNAME command

Gotcha. Looks like the magic sauce I was looking for to handle whitespace is in _fzf_extract_command in completion.zsh. However, I notice that this also doesn't seem to respect ;, &&, and ||, right? In other words, if I do
$ source ~/.zshrc; cd **<tab>

It thinks my command is source, not cd. Admittedly, a corner case. But should _fzf_extract_command be updated to parse only the rightmost command? (Using. e.g. echo "$LBUFFER" | rev | awk -F'\\|\\||&&|;' '{print $1}' | rev or some more robust zsh magic).
(This is getting slightly bit off-topic; I could open a separate issue for this if you agree.)

It's a known issue: #1981 #1992 #2130

OK, thanks. Will let those other issues sort out the command thing then.
Let's label this property, where $ ls root/some_gitignored_dir/** includes results under root/some_gitignored_dir but $ ls root/** does not, "directory-aware search". I would say this is a desirable property but some might disagree. Certainly it's what I personally expected to happen.
Some observations/questions:

The default _fzf_compgen_path() and _fzf_compgen_dir() do not exhibit directory-aware search; however, the examples from the README settings (e.g. fd --hidden --follow --exclude ".git" . "$1") actually do work. Obviously I can just make those changes locally. But would you consider a PR updating the default commands to also do directory-aware search?
It seems that completion is "better" than Ctrl-T because of the context-sensitive stuff. Is there something Ctrl-T has that completion doesn't? I can't think of use case where I would not prefer the context-sensitive search (given that it falls back to all files for an unknown command), but I'm assuming there's a good reason they work differently.
Given that completion seems superior in most respects, I'd rather use that (after replacing _fzf_compgen_(path|dir)() as above). But my fingers prefer <Ctrl-T> to **<Tab>. Is there any way I can locally hook up the keybinding ^T to the completion code instead?

The default _fzf_compgen_path() and _fzf_compgen_dir() do not exhibit directory-aware search

The prefix (e.g. ~/foo/ when you type vim ~/foo/bar**<tab>) is passed to the function as $1, so they use the information to only list files in that directory.

Is there something Ctrl-T has that completion doesn't?

Unlike on zsh, on bash, completion must be defined for each and every command. So if you have a new command and you haven't configured the fuzzy completion for it, foobar **<tab> simply will not work, while CTRL-T will always work.

Sometimes you don't want context-sensitivity. ssh **<tab> will list host names and IP addresses, but there are cases where you just want to grab a file path and CTRL-T comes in handy. ssh -i <CTRL-T>

And like I said above, it's easier to grasp and to configure. That's a big advantage for the new users and those who don't have time to learn how to configure fuzzy completion.

Is there any way I can locally hook up the keybinding ^T to the completion code instead?

https://github.com/junegunn/fzf/wiki/Configuring-fuzzy-completion#dedicated-completion-key (zsh only)


CHEBI:31867 wrong name, polymer ontology problem

The structure is the dihydrate, and I think it best just to change the name. However, in the entry it wrongly is_a polymer which probably happened because of usage of the brackets around the water in the structure? Please have a look at what got assigned under polymer just because of the brackets (examples):

CHEBI:3309 calcium gluconate
CHEBI:81711 Chlorhexidine acetate
CHEBI:31493 Dilazep dihydrochloride

Probably a solution would be to exclude all compounds where bracket indices are numeric and <10 or so.

All 4 ChEBI entries have now been fixed. Thanks


ENH: Filter zero-variance numerical columns from bioenv

Resolves #56
As this sits it just filters and alerts the user of what was removed. Should specifying optional categories be added to the functionality?

As this sits it just filters and alerts the user of what was removed. Should specifying optional categories be added to the functionality?

That sounds useful but probably worth adding that functionality in a separate PR. I don't think this is high priority for the upcoming workshop. Can you please create an issue so we can keep track of it?

Can you format the message so that the dict repr isn't displayed? For example, this is how the other plugins format the message:
https://forum-qiime2-org.s3-us-west-2.amazonaws.com/original/1X/6943c7495bcf8f9f4e8f1f30eacfaef096cbc783.png

Thanks @jairideout! Clarified the test assertions a bit, and added a no variance test as well!

Looks great, thanks @jakereps!! 👍 💯 👍


How to do a LIKE query with View

I need to know how to do a like query or match for a string with a View.
db.createView({
            name: "ProductName",
            revision: "1",
            map: (product: Product, emitter) => {
                if (product.docType == "Product") {
                    emitter.emit(product.name.toLowerCase(), null);
                }
            }
        });

getProducts(name: string = "", limit: number = 0, skip: number = 0) {
        let filter = { mapOnly: true, startKey: name, endKey: name, inclusiveEnd: true };
        if (limit != 0)
            (filter as any).limit = limit;
        if (skip != 0)
            (filter as any).skip = skip;
        let founded = db.queryView("ProductName", filter);
        console.dir(founded.getDocuments());
    }

and this retrieves an empty array.
Regards.

Hi guy!
If you want product starting with "pro" you have to set

start=proa
-end=proZ

It will retrieve all product starting with "pro"
Nabil MANSOURI

Le 10 août 2017 à 04:33, Isaac Hernandez<EMAIL_ADDRESS>a écrit :
I need to know how to do a like query or match for a string with a View.
db.createView({
name: "ProductoName",
revision: "1",
map: (product: Producto, emitter) => {
if (product.docType == "Producto") {
emitter.emit(product.name.toLowerCase(), null);
}
}
});
getProducts(name: string = "", limit: number = 0, skip: number = 0) {
let filter = { mapOnly: true, startKey: name, endKey: name, inclusiveEnd: true };
if (limit != 0)
(filter as any).limit = limit;
if (skip != 0)
(filter as any).skip = skip;
let founded = db.queryView("ProductoName", filter);
console.dir(founded.getDocuments());
}
and this retrieves an empty array.
Regards.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


lilToon 1.5.1 runs out of memory during Compilation Causing Shader Errors for any shader with transparency on Unity 2022

Enabling "[Debug] Optimize in Editor" appears to solve this however unity will crash if it is unselected.
`Shader error in 'Hidden/ltspass_transparent': Compilation failed (other error) 'out of memory during compilation
' at line 800 (on d3d11)
Compiling Subshader: 0, Pass: FORWARD_BACK, Fragment program with DIRECTIONAL LIGHTPROBE_SH
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PASS_FORWARDBASE UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: INSTANCING_ON SHADER_API_GLES30 SHADOWS_SCREEN UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING`
`Shader error in 'Hidden/ltspass_transparent': Compilation failed (other error) 'out of memory during compilation
' at line 951 (on d3d11)
Compiling Subshader: 0, Pass: FORWARD_ADD, Fragment program with DIRECTIONAL
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PASS_FORWARDADD UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: DIRECTIONAL_COOKIE INSTANCING_ON POINT POINT_COOKIE SHADER_API_GLES30 SPOT UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING
`
`Shader error in 'Hidden/ltspass_cutout': Compilation failed (other error) 'out of memory during compilation
' at line 767 (on d3d11)
Compiling Subshader: 0, Pass: FORWARD, Vertex program with DIRECTIONAL LIGHTPROBE_SH
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PASS_FORWARDBASE UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: FOG_EXP FOG_EXP2 FOG_LINEAR INSTANCING_ON SHADER_API_GLES30 SHADOWS_SCREEN UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING VERTEXLIGHT_ON`
`Shader error in 'Hidden/ltspass_cutout': Compilation failed (other error) 'out of memory during compilation
' at line 816 (on d3d11)
Compiling Subshader: 0, Pass: FORWARD_OUTLINE, Vertex program with DIRECTIONAL LIGHTPROBE_SH
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PASS_FORWARDBASE UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: FOG_EXP FOG_EXP2 FOG_LINEAR INSTANCING_ON SHADER_API_GLES30 SHADOWS_SCREEN UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING VERTEXLIGHT_ON
`
`Shader error in 'Hidden/ltspass_cutout': Compilation failed (other error) 'out of memory during compilation
' at line 869 (on d3d11)
Compiling Subshader: 0, Pass: FORWARD_ADD, Fragment program with DIRECTIONAL
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PASS_FORWARDADD UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: DIRECTIONAL_COOKIE INSTANCING_ON POINT POINT_COOKIE SHADER_API_GLES30 SPOT UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING
`

This is a problem that does not normally occur. It may be caused by cache corruption, and deleting the Library folder and restarting Unity may fix the problem.


Add status badges for global CI runs and nightlies to the README

I believe this is done, closing.


Automates duplicate tag fixing

Duplicate tags are currently patched by hand.  This PR automates that process.

Merging this to move ahead. The failing test is related to a missing generated file called FILES. I'm hoping the sync job may be able to clear this up after the merge.


refactor: Use the camelCase fieds in all proto files

Closes #1960

I'll restart the failed build later, now it's failed because of degraded performance for GitHub Packages.
error: failed to solve: ghcr.io/fluxcd/flux-cli:v0.24.1: pulling from host ghcr.io failed with status code [manifests v0.24.1]: 500 Internal Server Error
Error: buildx failed with: error: failed to solve: ghcr.io/fluxcd/flux-cli:v0.24.1: pulling from host ghcr.io failed with status code [manifests v0.24.1]: 500 Internal Server Error


[GHSA-wq5h-f9p5-q7fx] Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields

Updates

References

Comments
Adding the patch link for v2.11.7 (https://github.com/wagtail/wagtail/compare/v2.11.6...v2.11.7), it's the only commit related to the fix: https://github.com/wagtail/wagtail/commit/5c7a60977cba478f6a35390ba98cffc2bd41c8a4
Adding the patch link for v2.12.4: https://github.com/wagtail/wagtail/commit/915f6ed2bd7d53154103cc4424a0f18695cdad6c
The patch links contain the same workaround provided in the original advisory: adding check_url within the function link_entity.

Hi there @gasman! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


[Bug] Brackets not rendered as checkbox but disappear (Vue 3 + gfm)

Initial checklist

[X] I agree to follow the code of conduct
[X] I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected packages and versions
7.2.1
Link to runnable example
No response
Steps to reproduce
Code:

<template>
  <Milkdown />
</template>

Type this in the editor:
- [ ] Task 1
Expected behavior
Show bullet point with checkbox and text "Task 1"
Actual behavior
Brackets [ ] disappear immediately after hitting space after the brackets. There is no checkbox.
HTML rendering changes to this:

Task 1

Runtime
Chrome
OS
macOS
Build and bundle tools
Vite

It's by design, you need to write your own node view renderer like what we did in documentation website.

OK, thanks @Saul-Mirone. Could you point me to the right place in the documentation, please? I could not find this in the docs.

https://github.com/Milkdown/website/blob/main/src/components/playground-editor/editor-component/ListItem.tsx

https://github.com/Milkdown/vscode/blob/main/src/view/components/list-item.ts

Tried the provided code, nodeViewFactory is called, but nothing renders and the component passed is not in the DOM. Not sure what's up, using 7.2.4 for all deps.


[AutoPR search/resource-manager] Search new py path

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6109

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/3194


Anyone know how to set this up as module based?

I had it working with the instruction in #429.  Then I upgraded to the latest version and I can't use SELECT_DIRECTIVES (as expected).
I added SelectModule to my imports in the app.module.  I'm not sure what else to do.
Now I get this famliar error:
Can't bind to 'initData' since it isn't a known property of 'ng-select'.
1. If 'ng-select' is an Angular component and it has 'initData' input, then verify that it is part of this module.
...

That's usually because I don't have the module.
What else do I need to do?

It's "active" instead of "initData" now.

Thanks.  That fixed it.
Now I am at:

Error in ./SelectComponent class SelectComponent - inline template:106:19 caused by: value.match is not a function

But there are other threads for that.


can't get duration of this url

http://www.o-sense.com/Islamopedia/Albums/mrnabulsi/001fatiha/FATIHA1.mp3
can't get the duration of this link but playing song
So the problem is can't seek the audio, min-max value error in the slider, not get how long the audio is

@luanpotter I have tested, and even on the example Application the onDurationChanged is not firing events, do you think you can take a look on it?

I will check multiple URLs the duration is coming but in my url its not
working i will test and let you know.
On Tue, 28 May, 2019, 10:02 PM Erick<EMAIL_ADDRESS>wrote:

@luanpotter https://github.com/luanpotter I have tested, and even on
the example Application the onDurationChanged is not firing events, do
you think you can take a look on it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luanpotter/audioplayers/issues/177?email_source=notifications&email_token=AJVQU27CIOHC25EJB6Q6DUDPXVNBRA5CNFSM4HQAHEM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMWISQ#issuecomment-496591946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJVQU23TULVXZU5NDA77JNLPXVNBRANCNFSM4HQAHEMQ
.

Duration is not coming because it's a mono channel audio. Any one can provide solution for mono audio?

Fixed on 0.12.1

it's not working in Android.
On Wed, Jun 5, 2019 at 4:27 AM Luan Nico<EMAIL_ADDRESS>wrote:

Closed #177 https://github.com/luanpotter/audioplayers/issues/177.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luanpotter/audioplayers/issues/177?email_source=notifications&email_token=AJVQU262HKCXB5KTGNTM72TPY3XNZA5CNFSM4HQAHEM2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORZXZMDA#event-2389677580,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJVQU264CQYRBCPZ2VJTN6TPY3XNZANCNFSM4HQAHEMQ
.

--
Thanks & Regards,
https://www.oodlestechnologies.com/
[image: logo] https://www.oodlestechnologies.com/
Amit Kumar Mishra, AssociateConsultant- iOS Development, Oodles
Technologies Pvt Ltd
Phone:   +91-1166107221
Mobile:<PHONE_NUMBER>
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>Website:  http://www.oodlestechnologies.com/
Skype:     amit.mishra_29
Address: Unit No 951-955, Tower B1, Spaze I-Tech Park, Sector 49, Sohna
Road, Gurgaon, India, 122001
[image: Twitter] https://twitter.com/oodlestech [image: Facebook]
https://www.facebook.com/OodlesTech [image: Google +]
https://plus.google.com/+Oodlestechnologies/posts [image: LinkedIn]
https://www.linkedin.com/company/oodles-technologies-pvt-ltd


Add option to ignore failures on steps

Intended to implement #834
Adds ignore_failure to pipeline steps. When it's set to true, if the step fails the following steps continue to execute as if no failure had occurred.
First time working on a real Go project, so I hope the PR is ok :)

first impression looks good
lets let the ci run over itselve ;)
and then I'll have a look

with shell magic you normaly can ignore errors right now too ...
but plugins dont ... and this could be a simplification
In any case if we add it documentation is missing (https://github.com/woodpecker-ci/woodpecker/blob/master/docs/docs/20-usage/20-pipeline-syntax.md)

just exec make format and commit changes - we ensure proper code format via ci

with shell magic you normaly can ignore errors right now too ...

You're right, but at work we wanted a simple equivalent to Drone's failure: ignore, so I wanted to have a try at implementing it :smile:
If the addition is okay as-is I'll try to add the docs tomorrow morning (thanks for mentioning it!)

it does only add to pipeline config ... and dont move much code so why not
the only question would be: show error in UI and a ignored lable or not
not -> as is now
show in ui -> need bit more code (can be added later anyway)

Codecov Report
Base: 49.51% // Head: 49.45% // Decreases project coverage by -0.06% :warning:

Coverage data is based on head (8ce185f) compared to base (a39e8a0).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1219      +/-   ##
==========================================
- Coverage   49.51%   49.45%   -0.07%
==========================================
  Files          88       88
  Lines        6624     6624
==========================================
- Hits         3280     3276       -4
- Misses       3150     3153       +3
- Partials      194      195       +1

Impacted Files
Coverage Δ

server/queue/fifo.go
83.13% <0.00%> (-3.62%)
:arrow_down:

server/logging/log.go
54.65% <0.00%> (+5.81%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Looks great!

Hi Omar,
This looks familiar 👍  Great job with it!

Thanks. Your online course helped me a lot.


systemservices/_sources: problem with 'dep'

dep init doesn't work for the pkgs under systemservices/_sources because it has an underscore prefix.

mv _sources to sources?

@krhubert we had a conclusion of using an underscore for sources. Otherwise it'll look like a wrapper pkg. Maybe changing to sources_ is a better option and we should make research to see if there is a way of bypassing this limitation with dep.

I'm in favor of completely getting rid of underscore from the beginning because it also limits go tools for import path resolving. For now, I changed it with dash.


.groupby('column').sum() with parallel-pandas

can you show me how to convert below pandas code into parallel-pandas?
df[['column_1', 'column_2']].groupby('column_1').sum()

You can do it for several ways
The easiest way is to use the apply method with function:
def group_sum(gr):
     return gr.sum()

df.groupby(column_1).p_apply(group_sum)

I described the second possible way in this article
def chunk_group_sum(chunk):
    return chunk.groupby('gr').sum()
d.chunk_apply(chunk_group_sum, split_by_col='gr')

But I think that such an elementary function will be difficult to effectively parallelize
that is, you are unlikely to see acceleration of calculations, but rather the opposite


VS Code - Insiders will not update with latest version

vscode-inno-updater-1549974535.log
We have written the needed data into your clipboard because it was too large to send. Please paste.

I removed VS-Code insiders and reinstalled it but I am still getting the same error message when I close the application.

/duplicate #47841


Network issue: server_sock.bind(hostport), Windows10

I'm trying to write a tutorial for how to run this great project on Windows10, but am getting stuck myself :smile:
I think it's a network issue related to Windows.
The installation and everything works fine, I was able to run the server to import (and rescan) for a few addresses (so there is a connection between Bitcoin Core and the server). But when doing the final run I'm getting this error
INFO:2019-02-28 13:58:42,860: Starting electrum server
Traceback (most recent call last):
  File "c:\users\user1\appdata\local\programs\python\python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\user1\appdata\local\programs\python\python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\user1\AppData\Roaming\Python\Python37\Scripts\electrum-personal-server.exe\__main__.py", line 9, in <module>
  File "C:\Users\user1\AppData\Roaming\Python\Python37\site-packages\electrumpersonalserver\server\common.py", line 704, in main
    poll_interval_connected, certfile, keyfile)
  File "C:\Users\user1\AppData\Roaming\Python\Python37\site-packages\electrumpersonalserver\server\common.py", line 409, in run_electrum_server
    server_sock = create_server_socket(hostport)
  File "C:\Users\user1\AppData\Roaming\Python\Python37\site-packages\electrumpersonalserver\server\common.py", line 400, in create_server_socket
    server_sock.bind(hostport)
OSError: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions

A lot of searching and testing and I haven't been much wiser. What was suggested and what I've tried without luck:
Restart the computer, turn off firewall and antivirus, run as administrator, reset TCP connections and use
TCPView to monitor all connections to make sure that no other program uses the port the server is trying to use.
But nothing has worked so far. I do not know much about networks, but all I can see on related ports is that bitcoin-qt.exe is listening to port 8332 which I guess is expected?
The server is spinning up a lot of System processes that tries to connect to port 8332 but it fails.
I played around a bit with the code to try something else. If I changed line 400 in common.py to a hard-coded address
server_sock.bind(("<IP_ADDRESS>", 8332))
I got through to the message
Listening for Electrum Wallet on ('<IP_ADDRESS>', 50002)
But Electrum doesn't detect anything. I can see Electrum trying to make connections to remote port 50002 on localhost, but it fails because nothing is listening to that port. So I guess that only broke something. This only "worked" with <IP_ADDRESS> and not with <IP_ADDRESS>. Changing to <IP_ADDRESS> in the config-file didn't work.
Everything is on one machine. But to be sure, I've opened ports and disabled my VPN. Anyone with an idea?

Thanks for the issue, here are some thoughts.

The correct way to change the host and port is by editing config.cfg. You said editing didn't work, which is definitely a bug and should be fixed. I'll try running EPS on windows which I haven't done yet, and fixing it when I get time, or you could try adding print statements in places and seeing why it doesn't work. Other users have reported that changing to <IP_ADDRESS>. works correctly for them, but I think they were all using non-windows.

Don't use port 8332 because Bitcoin Core RPC uses that, perhaps try port 8000 (which is just a number I invented now)

When you change the bound port number, you also need to tell Electrum to connect to that port instead of 50002. So either by running command line --server localhost:8000:s or in the Electrum GUI going Tools -> Network -> Server and changing the port number to 8000.

I intend to eventually package up the project with pyinstaller so that it will be a single windows .exe file (see https://github.com/chris-belcher/electrum-personal-server/issues/63#issuecomment-435919552) After that installing on windows should be much easier, but I fear your tutorial may become out of date (Thought it looks like didn't have any trouble installing)

Thanks a lot for the help. Changing the port in the config-file did the trick (and it's able to run with localhost)!
[electrum-server]
# <IP_ADDRESS> to accept connections from any IP
#<IP_ADDRESS> to accept from only localhost
host = <IP_ADDRESS>
port = 8000

I tried to change it from 50002 to like 50000 before without success. So, your invented number was great! Might be because Windows use a lot of local ports with numbers randomly between 49000 and 65000 and that must've caused the issue even though I couldn't see that any process used them.
A single .exe file would be great and I'd happily update the tutorial when that is done (just want to see people running those full nodes). Feel free to hit me up if you need anything tested on Windows. Cheers

Feel free to hit me up if you need anything tested on Windows.

If this offer is still open, please have a look at issue #106


DOC: Wrong order and bad documentation clarity in contributing.md

What's wrong with the existing documentation
Keep the contribution part at the start then make another heading how to contribute and delete the getting started and how to create pull requests  part as it creates confusion.Under how to contribute keep star repo, fork repo, clone repo, cd  SwapReads, npm install  and then keep the same order of other commands that are under how to create pull request .
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@H1mang1 Assigned!


Eval framework asserts

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#714  👈
#713
#706 : 1 other dependent PR (#707 )
#705
#704
#702
#701
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spapinistarkware and the rest of your teammates on  Graphite

Codecov Report
Attention: Patch coverage is 92.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 89.90%. Comparing base (5c6bc7a) to head (05452dd).

Files
Patch %
Lines

crates/prover/src/builder/assert.rs
92.00%
3 Missing and 1 partial :warning:

Additional details and impacted files
@@                       Coverage Diff                       @@
##           eval_framework_point_domain     #714      +/-   ##
===============================================================
+ Coverage                        89.89%   89.90%   +0.01%
===============================================================
  Files                               79       80       +1
  Lines                            10202    10252      +50
  Branches                         10202    10252      +50
===============================================================
+ Hits                              9171     9217      +46
- Misses                             949      952       +3
- Partials                            82       83       +1

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

Merge activity

Jul 14, 8:06 AM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


Link to React Getting Started page

On this page (http://babeljs.io/docs/plugins/preset-react/#basic-setup-with-the-cli-), instead of linking to the React Getting Started page (https://facebook.github.io/react/docs/hello-world.html) which actually takes you to the Hello World example , this one (https://facebook.github.io/react/docs/installation.html) seems to be a better one to link to (as far as Babel is concerned).

It is also the target page on the React homepage.

Ok, I thought the intent to link to the React Getting Started page was more within the context of Babel and its installation with React etc. In that sense, I think this one is better. If the intent is for the user to just learn and know what is React, then the one that the React homepage points to is ok which starts with a Codepen example.

Yes, could I close the issue?

Sure, just did.


Implement Pagination for Tracks

Description:
This PR introduces pagination functionality for the Tracks component, ensuring that the content is properly paginated and displayed in a user-friendly way. The main objective was to display a set number of tracks per page (10 in this case) and provide pagination controls to navigate through different pages of content.
PR Fixes:

Pagination Logic:

Implemented pagination controls using the Pagination component from @repo/ui.
Each page displays 10 tracks (tracksPerPage = 10).
The PaginationPrevious, PaginationNext, and page numbers dynamically adjust based on the current page and the total number of tracks.

State Management:

Added state to handle the current page (currentPage), filtered tracks (filteredTracks), and visible tracks (visibleTracks).
Pagination re-renders the visible tracks based on the selected page.

Resolves #609, #651
Before
https://github.com/user-attachments/assets/17d7ff68-e537-49f3-9495-4036d188e68e
After
https://github.com/user-attachments/assets/a9c0f92b-a89d-468f-8f72-9eca247f12e2
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

In my view, implementing pagination on the frontend doesn’t add value or improve code efficiency. If pagination is required, it’s more efficient to handle it in the backend to optimize performance and manage resources effectively.

In my view, implementing pagination on the frontend doesn’t add value or improve code efficiency. If pagination is required, it’s more efficient to handle it in the backend to optimize performance and manage resources effectively.

I think if there were some problems then you would have been absolutely right but there are a lot of problems and they will keep getting added in the future if I am not wrong. And even now if you visit on the website you see lot of problems there, there is also a filter option so anyone can filter according to their need.


Update the roleAssignment.bicep module principalType property so that warnings do not occur

Benefit/Result/Outcome
So that deployments do not present warnings.
Description
Update the roleAssignment module's principalType to reflect the expected values:
Today's implementation:
https://github.com/Azure/missionlz/blob/6bdbf979621b74dcee701c824b3279c09e43b4c5/src/bicep/modules/roleAssignment.bicep#L4-L16
The expected values are one of ForeignGroup, Group, ServicePrincipal, User, null as reported by the Bicep warning below:
workspaces/missionlz/src/bicep/modules/roleAssignment.bicep(23,20) : Warning BCP036: The property "principalType" expected a value of type "'ForeignGroup' | 'Group' | 'ServicePrincipal' | 'User' | null" but the provided value is of type "'Application' | 'DirectoryObjectOrGroup' | 'DirectoryRoleTemplate' | 'Everyone' | 'ForeignGroup' | 'Group' | 'MSI' | 'ServicePrincipal' | 'Unknown' | 'User'".

Acceptance Criteria

Role assignments still occur when necessary for policy, but without warnings at deployment time

Instead of updating the list of allowed types, to include a null value - I think it might make more sense to remove the @allowed stanza. Preliminary tests of this approach are returning successful - doing some additional testing and gathering peer feedback.


Library name change request

Library repository URL
https://github.com/gobbolab/room-weather

Hi @RaptorGandalf. I am confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will close this issue when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager


[Oblique] Add /menu function

Master ticket for a larger implementation of a /servermenu, /menu or /playermenu option with proper functionality, including command prompts, warps, utilities and information display. Will link all tickets that relate to this.

Adding information in a 'give books' button (or cleaner) https://github.com/ObliqueNET/Server/issues/141

Adding information in a 'give books' button (or cleaner) https://github.com/ObliqueNET/Server/issues/141


Adapt the code to the new notation for I/O actions

Pull request input-output-hk/thorn-calculus#96 introduces a new notation for IO Sending and IO Receiving. We shall adapt the code in this repository to this notation change.

Apparently, the notation for I/O actions is nowhere used in this repository. Therefore, I’m closing this issue.


fix(shared): ensure invokeArrayFns handles undefined arguments

Close #10863.
Ensures invokeArrayFns in shared/src/general.ts handles undefined arguments properly.

Is it possible to include test cases for this fix?

Yes, I have updated the tests to cover this fix. Thank you for your suggestion!

/ecosystem-ci run


Import JSON data into Workspace

Once we have a working JSON input feature in the workspace, it would be good to be able to import from a .json file rather than need to copy and paste.

API endpoints all have JSON input fields, which is better than the JSON block in the Code Editor. The JSON block is likely going to be deprecated, so this is low priority.


Use compile-time generics instead of dyn dispatch for writers

Profiling revealed that some very small Writer functions, such as bit, were not being inlined. These functions were sometimes used within loops and therefore the inability to inline resulted in inefficient code. This inability to inline was due to the writers being passed as dynamic objects at runtime. Using generics to monomorphise the functions at compile-time allows the writer functions to be inlined and produces more optimized code.
Testing shows that this produces an overall speed increase of 1-2% at all speed levels.

With the current default settings in Cargo.toml, here is the size comparison for a stripped release build:
Before: 3565976 bytes
After: 3660184 bytes
So about 100kb increase.


Fixing alerts from lgtm.com

And adding a readme badge.
Trying to make the red line here go down to zero:
https://lgtm.com/projects/g/Netflix-Skunkworks/cloudaux/history/
Trying to get rid of the things on this list:
https://lgtm.com/projects/g/Netflix-Skunkworks/cloudaux/alerts/?mode=list
Hoping one day someone will install the LGTM app on this project to look at PRs.

Coverage decreased (-0.07%) to 34.115% when pulling 4ef55a2090b9d7788c137dc3dd82a2fc6cb26f5e on scriptsrc:lgtm_zero_issues into 9e2bdc1c690df9aa01ddf919d1d79bd77e5cb5e4 on Netflix-Skunkworks:master.


Release v2

It'll be great if you release v2.
If you are woried about back comatability then you can use gopkg.in service to provide access to the new version.

It will be released when it is done. See https://github.com/julienschmidt/httprouter/milestone/1 / https://github.com/julienschmidt/httprouter/projects/1. I'm currently lacking time for FLOSS development. I hope to consolidate my unreleased experiments into an experimental branch soon, however I really can't give any ETA.


Instaloader-reader

Has anyone considered writing an instaloader reader? I'm thinking about a lightweight PHP script that parses a directory of stored profiles and generates browsable layouts.

I actually was just wondering the exact same thing. I had a dog breeder that had an instagram account for the litter of puppies. They have since removed the account a few months after but I have it backed up. The other owners of the puppies have no such backup and wanted to see the photos. So for now I just uploaded all the photos on Google Photos but it lacks the captions to go with them which can be useful.
I have considered making a webpage but don't know if I have the time/motivation right now.

Bump

You might be looking for Bibliogram. Bibliogram intentionally does not save data to disk to protect the privacy of users, but I don't think it would be difficult to modify it to save photos and p reserve deleted accounts.
https://sr.ht/~cadence/bibliogram/

I'm probably going to build a simple node app to do this, with the capability to read off of google drive, since that's where i'm storing my archives.

I'm probably going to build a simple node app to do this, with the capability to read off of google drive, since that's where i'm storing my archives.


Configure at which row to initiate infinite scroll handler

Hi,
Is there a way I can configure when the infinite scrolling handler is triggered? That is, instead of a fetch request at last row, lets say I configure it to initiate fetch few rows earlier before the end. If not, is there a way I can disable auto initiation of the fetch request at last row, so I can just instead use the manual trigger?
Thanks.

@shuaib have you figured how to do it ?

HI @shuaib  have you find out way to call infinite scrolling handler is triggered request earlier ?

Would love to know what you guys ended up doing to cause this


Only Gauge definitions available within package_to_scan should be considered

Actual behavior
All the definitions in the project are considered.
Steps to replicate

Create a java_maven project with grp1 as the default package
Create another package one.level
Add a new step implementation to the new package
Add a custom Parser to the new package
Use the step in the example.spec with a custom parameter defined
Configure package_to_scan = grp1
Reload the project
Run the specifications

All the steps are successfully executed. But, the definitions outside grp1 should not be considered

Sample project - art2.zip

Version
Gauge version: 1.0.1.nightly-2018-06-19
Commit Hash: 583ef1d

Plugins
-------
java (0.6.9.nightly-2018-06-12)

Blocks #161

Fix should be available in nightly >= 28 June 2018

Only Custom Parameters defined within the package_to_scan should be considered. Currently it considers all definitions.
Steps to replicate
Same as the original issue.


Bilibili broken again

Version 2015.01.16 seemed to work a few days ago, although when tested with a 20-min video, youtude-dl only gets an 5-min clip (initial part of the video instead of the whole).
Now the entire extractor seems broken:
$ youtube-dl http://www.bilibili.com/video/av530528/index_11.html --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://www.bilibili.com/video/av530528/index_11.html', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.01.16
[debug] Python version 2.7.8 - Darwin-14.0.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[BiliBili] 530528: Downloading webpage
ERROR: Unable to extract video code; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/Users/shichao/envs/youtube-dl/lib/python2.7/site-packages/youtube_dl/YoutubeDL.py", line 600, in extract_info
    ie_result = ie.extract(url)
  File "/Users/shichao/envs/youtube-dl/lib/python2.7/site-packages/youtube_dl/extractor/common.py", line 260, in extract
    return self._real_extract(url)
  File "/Users/shichao/envs/youtube-dl/lib/python2.7/site-packages/youtube_dl/extractor/bilibili.py", line 34, in _real_extract
    r'(?s)
(.*?)
', webpage, 'video code')
  File "/Users/shichao/envs/youtube-dl/lib/python2.7/site-packages/youtube_dl/extractor/common.py", line 516, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video code; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Could you run it with --write-pages and upload *.dump files that will be created?

It seems it is working today (no broken problem), but still, only part of the whole video is downloaded. For the link above, the downloaded video (in flv format) is only 6 minutes long, though it should be approx 20 minutes.
I put the dump files in a single gist at https://gist.github.com/shichao-an/03e49eaf02fec307ad1a

The video you provide has multiple parts, and I've extend BiliBili extractor so that multipart videos can be downloaded correctly. (See  c4a21bc9db1868e8be114f496899f6786b9982ec) If you still encounter problems, feel free to open a new issue.


"Error displaying widget" happens

I have installed ipyvolume and other components for jupyterlab as recommended.
There was no error messages and I believe all processes were performed properly, however, I meet Error displaying widget message whenever I try ipyvolulme as shown below screenshot.

For easy comparison with tutorials, I run a few cells and pasted the results below.
MCMC example

https://github.com/maartenbreddels/ipyvolume/blob/master/docs/source/example_mcmc.ipynb

import pylab
import scipy.optimize as op
import emcee
import numpy as np
%matplotlib inline

# our 'blackbox' 3 parameter model which is highly degenerate
def f_model(x, a, b, c):
    return x * np.sqrt(a**2 +b**2 + c**2) + a*x**2 + b*x**3

N = 100
a_true, b_true, c_true = -1., 2., 1.5

# our input and output
x = np.random.rand(N)*0.5#+0.5
y = f_model(x, a_true, b_true, c_true)

# + some (known) gaussian noise
error = 0.2
y += np.random.normal(0, error, N)

# and plot our data
pylab.scatter(x, y);
pylab.xlabel("$x$")
pylab.ylabel("$y$")

Text(0, 0.5, '$y$')

# our likelihood
def lnlike(theta, x, y, error):
    a, b, c = theta
    model =  f_model(x, a, b, c)
    chisq = 0.5*(np.sum((y-model)**2/error**2))
    return -chisq
result = op.minimize(lambda *args: -lnlike(*args), [a_true, b_true, c_true], args=(x, y, error))
# find the max likelihood
a_ml, b_ml, c_ml = result["x"]
print("estimates", a_ml, b_ml, c_ml)
print("true values", a_true, b_true, c_true)
result["message"]

estimates 1.2820726223219492 -2.057163544162576 1.1601376256006772e-05
true values -1.0 2.0 1.5

'Optimization terminated successfully.'

# do the mcmc walk
ndim, nwalkers = 3, 100
pos = [result["x"] + np.random.randn(ndim)*0.1 for i in range(nwalkers)]
sampler = emcee.EnsembleSampler(nwalkers, ndim, lnlike, args=(x, y, error))
sampler.run_mcmc(pos, 1500);
samples = sampler.chain[:, 50:, :].reshape((-1, ndim))

# plot the 2d pdfs
import corner
fig = corner.corner(samples, labels=["$a$", "$b$", "$c$"],
                      truths=[a_true, b_true, c_true])

import vaex
import scipy.ndimage
import ipyvolume

ds = vaex.from_arrays(a=samples[...,0].copy(), b=samples[...,1].copy(), c=samples[...,2].copy())
# get 2d histogram
v = ds.count(binby=["a", "b", "c"], shape=64)
# smooth it for visual pleasure
v = scipy.ndimage.gaussian_filter(v, 2)

ipyvolume.quickvolshow(v, lighting=True)

/home/jehyun/anaconda3/lib/python3.7/site-packages/ipyvolume/serialize.py:81: RuntimeWarning: invalid value encountered in true_divide
  gradient = gradient / np.sqrt(gradient[0]**2 + gradient[1]**2 + gradient[2]**2)

VBox(children=(VBox(children=(HBox(children=(Label(value='levels:'), FloatSlider(value=0.1, max=1.0, step=0.00…

I have this same issue in JupyterLab 0.35.4.

I'm having a similar issue. I really can't figure out what's wrong. I've installed everything under one of my conda environments, but I can't seem to get ipywidgets working. I'd appreciate any help!

You could try for jupyter lab <1.0 to install an older version of ipyvolume's frontend code:
$ jupyter labextension install<EMAIL_ADDRESS>
But now that jupyter lab 1.0 is out I'd advise you to use that.

Please provide a screenshot of the javascript console, or the output of it, so I have more information.


Option "dns" causes domains in a "bypass" list not resolved remotely

In commands below, the first behaves as expected, while the second does not. The domains in /path/to/domains.txt are not resolved remotely in the second command.

gost -L=":1080" -F="foo.com:8080/?bypass=~/path/to/domains.txt"
gost -L=":1080?dns=<IP_ADDRESS>" -F="foo.com:8080/?bypass=~/path/to/domains.txt"

Some HTTP proxy may not support CONNECT method to a non-443 port, so in GOST HTTP proxy, if the last node in the proxy chain is also an HTTP proxy, all non CONNECT requests will be forwarded to the last proxy node by default. The forwarded requests can not use the DNS resolver.
In the next version, an option will be added to control the forward behavior manually. For now, you can use SOCKS5 mode to communicate with local proxy.

Thanks for your suggestion. But the domain names are resolved locally whether using SOCKS5 or HTTP mode to communicate with local proxy.

What is the GOST version do you use?
I have tested against the 2.6.1 version in SOCKS5 mode, and it works well.
Here is my local test case:
gost -L=:18080 -D

gost -L=:11080?dns=<IP_ADDRESS> -F=:18080?bypass=~github.com -D

curl --socks5-hostname localhost:11080 http://github.com

The resolver log will appear on server :11080:
resolver.go:139: [resolver] github.com via <IP_ADDRESS>:53/udp [<IP_ADDRESS> <IP_ADDRESS>]

And the :18080 server will receive a CONNECT request:
CONNECT <IP_ADDRESS>:80 HTTP/1.1
Host: <IP_ADDRESS>:80
Proxy-Connection: keep-alive
User-Agent: Chrome/60.0.3112.90

The resolver log will appear on server :11080:
This means the domain is resolved locally. It should be resolved on server :18080 IMO.

No, it is resolved by <IP_ADDRESS>:53. If no DNS resolvers specified, it will be resolved on :18080

I suppose the DNS option is just telling where to resolve domain names.
And the Bypass option should take precedence here.

What I intended in the first place is to resolve only bypassed name in the specified DNS server. Is there any way I can do this now?

The DNS resolver is independent of bypass, for now you can not control the rules.


[DFT] Fix MKLCPU const_cast for release DPC++

Description

A previous commit introduces const_cast to fix changes to nightly LLVM

This break builds with the DPC++ release compiler

This PR fixes the const casts.

Fixes https://github.com/oneapi-src/oneMKL/issues/355
Checklist
All Submissions

[ ] Do all unit tests pass locally? Attach a log.
[x] Have you formatted the code using clang-format?

Bug fixes

[N/A] Have you added relevant regression tests?
[See issue] Have you included information on how to reproduce the issue (either in a
GitHub issue or in this PR)?

Test log for the 2023.2.0 DPC++ release:
onemkl_release2023.2.0_test_log.txt

@anantsrivastava30 Can you test if this builds with the nightly compiler? I haven't worked out how to configure CMake correctly for it.

Intel(R) oneAPI DPC++/C++ Compiler 2024.0.0 (2<IP_ADDRESS>30713) - 0714, @hjabird this builds fine with the nightly compiler but I see a lot of warnings now.
/nfs/site/home/anantsri/devel/opensource/oneMKL_anantsri/src/dft/backends/mklcpu/backward.cpp:198:52: warning: 'get_pointer<sycl::access::target::global_buffer, void>' is deprecated: accessor::get_pointer() is deprecated, please use get_multi_ptr() [-Wdeprecated-declarations]
  198 |                 outre_acc.get_pointer(), outim_acc.get_pointer());
      |                                                    ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/accessor.hpp:2302:3: note: 'get_pointer<sycl::access::target::global_buffer, void>' has been explicitly marked deprecated here
 2302 |   __SYCL2020_DEPRECATED(
      |   ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/detail/defines_elementary.hpp:55:40: note: expanded from macro '__SYCL2020_DEPRECATED'
   55 | #define __SYCL2020_DEPRECATED(message) __SYCL_DEPRECATED(message)
      |                                        ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/detail/defines_elementary.hpp:46:38: note: expanded from macro '__SYCL_DEPRECATED'

Intel(R) oneAPI DPC++/C++ Compiler 2024.0.0 (2<IP_ADDRESS>30713) - 0714, @hjabird this builds fine with the nightly compiler but I see a lot of deprication warnings now.
/nfs/site/home/anantsri/devel/opensource/oneMKL_anantsri/src/dft/backends/mklcpu/backward.cpp:198:52: warning: 'get_pointer<sycl::access::target::global_buffer, void>' is deprecated: accessor::get_pointer() is deprecated, please use get_multi_ptr() [-Wdeprecated-declarations]
  198 |                 outre_acc.get_pointer(), outim_acc.get_pointer());
      |                                                    ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/accessor.hpp:2302:3: note: 'get_pointer<sycl::access::target::global_buffer, void>' has been explicitly marked deprecated here
 2302 |   __SYCL2020_DEPRECATED(
      |   ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/detail/defines_elementary.hpp:55:40: note: expanded from macro '__SYCL2020_DEPRECATED'
   55 | #define __SYCL2020_DEPRECATED(message) __SYCL_DEPRECATED(message)
      |                                        ^
/nfs/pdx/disks/mkl_mirror/NN/tools/dpc++/20230714_nightly/lnx/bin/compiler/../../include/sycl/detail/defines_elementary.hpp:46:38: note: expanded from macro '__SYCL_DEPRECATED'

That is a problem, but not an immediate one. It can be fixed in a seperate PR I think. I will rebase this PR, and rerun tests. I think the only changes should be formatting.

Log with 2023.2.0 after rebase: onemkl_release2023.2.0_test_log.txt

The above force push did not change anything from the previous one, but was required since the github interface didn't seem to be updating to include the rebase on PRs merged since this.


Space between tags

Hi,
Is it possible to change space between tags?
Looks like there is a FIELD_MARGIN_X constant here but it's not used anywhere in the code.
I've also searched for occurrences of VSPACE and tried to add HSPACE by analogue but with no success.

Oh, I didn't notice that TF has spaceBetweenTags property on it


Add overscroll-behaviour

Please would it be possible to add the overscroll-behaviour feature?
https://developers.google.com/web/updates/2017/11/overscroll-behavior?utm_source=CSS-Weekly&utm_campaign=Issue-290&utm_medium=email

Duplicate of #3725


Add additional fields to AWS::Events::Rule

Follow up to https://github.com/MonsantoCo/cloudformation-template-generator/pull/155, add remaining optional fields to AWS::Events::Rule
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-events-rule.html

Unless we want to cheat and just model EventPattern as a JsObject, we'll need to model this too:
http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatchEventsandEventPatterns.html


Removed sha256of function, made URL randomly generated.

In reference to the only open issue currently, #3, I removed the sha256of function and instead made the generated URL non-deterministic  instead so that the URL is different every time for the same input URL.

@petergeorgas thanks for the PR. please look a the comment on the issue and the slack channel. The issue was obsolete


Unable to resolve dependency in build.gradle

I tried adding the FAB  button dependency using gradle compile
'com.getbase:floatingactionbutton:1.10.0'
but it did not work.
I am using gradle 2.4 with Android Studio version 1.3.
It keeps on giving failure to resolve dependency error.
Please help.
Thanks

What's in the repositories section in your build.gradle?

Its jcenter(). Its an exported eclipse project.

Strange, everything works for me in this setup. Can you post your gradle
files as a gist?
On Aug 5, 2015 16:55, "Pavitra M Kansara"<EMAIL_ADDRESS>wrote:

Its jcenter(). Its an exported eclipse project.
—
Reply to this email directly or view it on GitHub
https://github.com/futuresimple/android-floating-action-button/issues/249#issuecomment-128025092
.

Here it is:
https://gist.github.com/pmk2429/975ba22efb70f42470ef

This section:
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.2.3'
    }
}

Specifies the repositories used for build script dependencies, i.e. where should the gradle look for android gradle plugin. You need to specify repositories for your app dependencies next to the dependencies section:
repositories {
  jcenter()
}

dependencies {
    compile fileTree(include: '*.jar', dir: 'libs')
    compile 'com.android.support:support-v4:21.0.3'
    compile 'com.google.android.gms:play-services:7.5.0'
    compile 'com.android.support:appcompat-v7:21.0.3'
    compile project(':fileChooser')
}

Let me know if this solves your problem.

Wow man. It did solve the problem. Super thanks!


Metadata doesn't have an attestationCertificateKeyIdentifiers field

Authenticator metadata published at https://github.com/LedgerHQ/app-security-key/blob/develop/conformance/prod-nanosp.json doesn't have an attestationCertificateKeyIdentifiers field. It has an aaguid field however.
As far as I understand, this model generates fido-u2f attestations, and which can be verified against a root trust anchor using the attestation certificate key identifier. This type of attestation were designed before aaguids were a thing, which is why I don't understand why there's an aaguid published in the metadata.
Am I getting something wrong?

This app supports FIDO2 and U2F (FIDO1) for retro compatibility purpose, though I doubt there are a lot of use case for this.
For FIDO2 authenticators need to expose a AAGUID and the root of thrust can be found in the attestationRootCertificates field of the metadata.
Note that certificates for U2f and FIDO differs, but you find some explanation of how it's handled for this app in the attestations/ folder.

Per https://medium.com/webauthnworks/verifying-fido-u2f-attestations-in-fido2-f83fab80c355:

If you are planing to support metadata service, then you can find attestationCertificateKeyIdentifier by calculating the SHA1 of the subjectKey structure as described in method 1 of the section <IP_ADDRESS> of the RFC5280.

my understanding is that when verifying a fido-u2f attestation (which is returned by this authenticator), there's no aaguid in theattested credential data, and therefore we need to check the acki instead :thinking:
What attestation formats are returned by this authenticator?

This authentificator is using the "packed" attestation format.
You can find more information on the specification of the attestation here: https://www.w3.org/TR/webauthn/#sctn-attestation.
Basically you can check that the "authData" have been properly signed by checking the attestation statement content (signature should be valid for the corresponding certificate and "authData").
And you can check the root of thrust by verifying that the certificate has been signed by the root certificate inside attestationRootCertificates field of the metadatas.

It looks like the Ledger Nano S Plus authenticator can return fido-u2f attestation statements as well.
This is actually what is written in the metadata: https://github.com/LedgerHQ/app-security-key/blob/develop/conformance/prod-nanosp.json#L67
Do you have u2f metadata statement as well, with attestation certificate key identifiers? cc @patatoid

@tanguilp I suspect the log you have is a log acquired during a registration using U2F. As you see in the metadata, the authentificator support both version of the protocol, and for example, Firefox on Linux only support U2F.
The expected metadata format is not clear to me when supporting both U2F and FIDO2 versions.
However, the root certificate is the same for both, and therefore attestationRootCertificates should be what your are looking for?

It looks like the metadata https://github.com/LedgerHQ/app-security-key/blob/develop/conformance/prod-nanosp.json refers to a root certificate for "Ledger FIDO Attestation CA" [1], but I have an attestation referring to another root certificate "Ledger FIDO Attestation CA 1" [2].
Can you please advise?
Cheers!
[1]
-----BEGIN CERTIFICATE-----
MIIBgTCCAScCFBlo0s5QYFdXbfusRdQeoLX6QenlMAoGCCqGSM49BAMCMEMxCzAJ
BgNVBAYTAkZSMQ8wDQYDVQQKDAZMZWRnZXIxIzAhBgNVBAMMGkxlZGdlciBGSURP
IEF0dGVzdGF0aW9uIENBMB4XDTIzMDIyMzEwMzMwOFoXDTMzMDIyMDEwMzMwOFow
QzELMAkGA1UEBhMCRlIxDzANBgNVBAoMBkxlZGdlcjEjMCEGA1UEAwwaTGVkZ2Vy
IEZJRE8gQXR0ZXN0YXRpb24gQ0EwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAATK
7nXyH4pgN3TMwCWSoMDRe4EV8Jl3XzuhicZ/2gvh+zz3WmW0OZ/EcRYEA8F26cee
uMcd21WQRRKWpjWD+JWiMAoGCCqGSM49BAMCA0gAMEUCIQCwcsHuL8ZFL3FNyU/D
OQn3bmx08lnn0O5RktLbOnoPHQIgOEi6ImAZ181q8RJiL0hbw7ZquuniRq6fjWjG
oBu1Moo=
-----END CERTIFICATE-----

[2]
-----BEGIN CERTIFICATE-----
MIIBVDCB+qADAgECAgEoMAoGCCqGSM49BAMCMCcxJTAjBgNVBAMMHExlZGdlciBG
SURPIEF0dGVzdGF0aW9uIENBIDEwHhcNMjIwMjA3MTUyNjQ4WhcNMzIwMTI2MTUy
NjQ4WjAnMSUwIwYDVQQDDBxMZWRnZXIgRklETyBBdHRlc3RhdGlvbiBDQSAxMFkw
EwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAnQWQZXDuQy+OvCWivTzYQi/oCGKzdr2
MyCtzqEON0+P1e8EO90yZpVZ3GNkGzBRen4EMQ3Ed1ihalZbcoX+dKMXMBUwEwYL
KwYBBAGC5RwCAQEEBAMCBSAwCgYIKoZIzj0EAwIDSQAwRgIhAI4Of1BPPfpn9lGa
GU2ottmmQ1NUhravSIYiO3gVx1d6AiEAzzgRmdUxwhms7iP6P/UlN9Pm5qKbxthu
QY314+5xCoE=
-----END CERTIFICATE-----

Hello,
The first one is indeed the prod CA certificate, which can be found here: https://github.com/LedgerHQ/app-security-key/blob/develop/attestations/data/prod/ca-cert.pem
Where does the second one comes from?

The second one comes from a fiduo-u2f attestation attestation by a Ledger Nano S Plus

Sorry but I don't see it in the logs? So I guess you computed it from something?
Also, Firefox now has CTAP2/FIDO2 capabilities, so this might be not relevant anymore?

Yes this comes from an attestation object given here. When decoding (sorry for unusual Elixir code!) we get the following certificate with the "Ledger FIDO Attestation CA 1" CN & issuer:
iex(9)> attestation = <<163, 99, 102, 109, 116, 104, 102, 105, 100, 111, 45,
...(9)>     117, 50, 102, 103, 97, 116, 116, 83, 116, 109, 116, 162, 99, 115, 105, 103,
...(9)>     88, 70, 48, 68, 2, 32, 103, 160, 121, 170, 246, 212, 126, 173, 208, 92, 35,
...(9)>     242, 25, 64, 6, 93, 177, 43, 54, 194, 120, 144, 141, 28, 249, 227, 240, 104,
...(9)>     113, 104, 249, 173, 2, 32, 21, 52, 206, 153, 171, 151, 19, 71, 15, 92, 212,
...(9)>     72, 110, 19, 143, 86, 4, 53, 100, 112, 88, 59, 66, 160, 115, 94, 126, 214,
...(9)>     68, 71, 97, 203, 99, 120, 53, 99, 129, 89, 1, 88, 48, 130, 1, 84, 48, 129,
...(9)>     250, 160, 3, 2, 1, 2, 2, 1, 40, 48, 10, 6, 8, 42, 134, 72, 206, 61, 4, 3, 2,
...(9)>     48, 39, 49, 37, 48, 35, 6, 3, 85, 4, 3, 12, 28, 76, 101, 100, 103, 101, 114,
...(9)>     32, 70, 73, 68, 79, 32, 65, 116, 116, 101, 115, 116, 97, 116, 105, 111, 110,
...(9)>     32, 67, 65, 32, 49, 48, 30, 23, 13, 50, 50, 48, 50, 48, 55, 49, 53, 50, 54,
...(9)>     52, 56, 90, 23, 13, 51, 50, 48, 49, 50, 54, 49, 53, 50, 54, 52, 56, 90, 48,
...(9)>     39, 49, 37, 48, 35, 6, 3, 85, 4, 3, 12, 28, 76, 101, 100, 103, 101, 114, 32,
...(9)>     70, 73, 68, 79, 32, 65, 116, 116, 101, 115, 116, 97, 116, 105, 111, 110, 32,
...(9)>     67, 65, 32, 49, 48, 89, 48, 19, 6, 7, 42, 134, 72, 206, 61, 2, 1, 6, 8, 42,
...(9)>     134, 72, 206, 61, 3, 1, 7, 3, 66, 0, 4, 2, 116, 22, 65, 149, 195, 185, 12,
...(9)>     190, 58, 240, 150, 138, 244, 243, 97, 8, 191, 160, 33, 138, 205, 218, 246,
...(9)>     51, 32, 173, 206, 161, 14, 55, 79, 143, 213, 239, 4, 59, 221, 50, 102, 149,
...(9)>     89, 220, 99, 100, 27, 48, 81, 122, 126, 4, 49, 13, 196, 119, 88, 161, 106,
...(9)>     86, 91, 114, 133, 254, 116, 163, 23, 48, 21, 48, 19, 6, 11, 43, 6, 1, 4, 1,
...(9)>     130, 229, 28, 2, 1, 1, 4, 4, 3, 2, 5, 32, 48, 10, 6, 8, 42, 134, 72, 206,
...(9)>     61, 4, 3, 2, 3, 73, 0, 48, 70, 2, 33, 0, 142, 14, 127, 80, 79, 61, 250, 103,
...(9)>     246, 81, 154, 25, 77, 168, 182, 217, 166, 67, 83, 84, 134, 182, 175, 72,
...(9)>     134, 34, 59, 120, 21, 199, 87, 122, 2, 33, 0, 207, 56, 17, 153, 213, 49,
...(9)>     194, 25, 172, 238, 35, 250, 63, 245, 37, 55, 211, 230, 230, 162, 155, 198,
...(9)>     216, 110, 65, 141, 245, 227, 238, 113, 10, 129, 104, 97, 117, 116, 104, 68,
...(9)>     97, 116, 97, 88, 196, 73, 150, 13, 229, 136, 14, 140, 104, 116, 52, 23, 15,
...(9)>     100, 118, 96, 91, 143, 228, 174, 185, 162, 134, 50, 199, 153, 92, 243, 186,
...(9)>     131, 29, 151, 99, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(9)>     0, 0, 0, 64, 196, 164, 239, 243, 184, 57, 52, 221, 100, 180, 160, 74, 51,
...(9)>     231, 130, 137, 44, 17, 65, 103, 228, 38, 119, 59, 161, 167, 6, 175, 223, 8,
...(9)>     69, 181, 234, 147, 92, 161, 237, 42, 229, 217, 189, 199, 206, 31, 153, 192,
...(9)>     172, 148, 198, 247, 22, 184, 243, 176, 136, 95, 109, 182, 132, 75, 125, 209,
...(9)>     207, 39, 165, 1, 2, 3, 38, 32, 1, 33, 88, 32, 171, 229, 131, 33, 251, 58,
...(9)>     104, 196, 55, 110, 12, 84, 87, 71, 229, 116, 150, 130, 200, 92, 52, 194,
...(9)>     229, 50, 73, 170, 124, 215, 93, 205, 20, 165, 34, 88, 32, 116, 121, 94, 167,
...(9)>     22, 144, 249, 244, 79, 22, 144, 37, 243, 15, 106, 196, 155, 14, 28, 147, 61,
...(9)>     138, 104, 109, 74, 80, 19, 32, 116, 32, 193, 136>>
<<163, 99, 102, 109, 116, 104, 102, 105, 100, 111, 45, 117, 50, 102, 103, 97,
  116, 116, 83, 116, 109, 116, 162, 99, 115, 105, 103, 88, 70, 48, 68, 2, 32,
  103, 160, 121, 170, 246, 212, 126, 173, 208, 92, 35, 242, 25, 64, 6, 93, 177,
  ...>>
iex(10)> attestation |> Wax.Utils.CBOR.decode() |> elem(1) |> get_in(["attStmt", "x5c"]) |> List.first() |> X509.Certificate.from_der
{:ok,
 {:OTPCertificate,
  {:OTPTBSCertificate, :v3, 40,
   {:SignatureAlgorithm, {1, 2, 840, 10045, 4, 3, 2}, :asn1_NOVALUE},
   {:rdnSequence,
    [
      [
        {:AttributeTypeAndValue, {2, 5, 4, 3},
         {:utf8String, "Ledger FIDO Attestation CA 1"}}
      ]
    ]}, {:Validity, {:utcTime, '220207152648Z'}, {:utcTime, '320126152648Z'}},
   {:rdnSequence,
    [
      [
        {:AttributeTypeAndValue, {2, 5, 4, 3},
         {:utf8String, "Ledger FIDO Attestation CA 1"}}
      ]
    ]},
   {:OTPSubjectPublicKeyInfo,
    {:PublicKeyAlgorithm, {1, 2, 840, 10045, 2, 1},
     {:namedCurve, {1, 2, 840, 10045, 3, 1, 7}}},
    {:ECPoint,
     <<4, 2, 116, 22, 65, 149, 195, 185, 12, 190, 58, 240, 150, 138, 244, 243,
       97, 8, 191, 160, 33, 138, 205, 218, 246, 51, 32, 173, 206, 161, 14, 55,
       79, ...>>}}, :asn1_NOVALUE, :asn1_NOVALUE,
   [{:Extension, {1, 3, 6, 1, 4, 1, 45724, 2, 1, 1}, false, <<3, 2, 5, 32>>}]},
  {:SignatureAlgorithm, {1, 2, 840, 10045, 4, 3, 2}, :asn1_NOVALUE},
  <<48, 70, 2, 33, 0, 142, 14, 127, 80, 79, 61, 250, 103, 246, 81, 154, 25, 77,
    168, 182, 217, 166, 67, 83, 84, 134, 182, 175, 72, 134, 34, 59, 120, 21,
    199, 87, 122, 2, 33, 0, 207, 56, 17, 153, ...>>}}

If it can help here is the base64-encoded payload of the attestation mentioned above: o2NmbXRoZmlkby11MmZnYXR0U3RtdKJjc2lnWEYwRAIgZ6B5qvbUfq3QXCPyGUAGXbErNsJ4kI0c+ePwaHFo+a0CIBU0zpmrlxNHD1zUSG4Tj1YENWRwWDtCoHNeftZER2HLY3g1Y4FZAVgwggFUMIH6oAMCAQICASgwCgYIKoZIzj0EAwIwJzElMCMGA1UEAwwcTGVkZ2VyIEZJRE8gQXR0ZXN0YXRpb24gQ0EgMTAeFw0yMjAyMDcxNTI2NDhaFw0zMjAxMjYxNTI2NDhaMCcxJTAjBgNVBAMMHExlZGdlciBGSURPIEF0dGVzdGF0aW9uIENBIDEwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAQCdBZBlcO5DL468JaK9PNhCL+gIYrN2vYzIK3OoQ43T4/V7wQ73TJmlVncY2QbMFF6fgQxDcR3WKFqVltyhf50oxcwFTATBgsrBgEEAYLlHAIBAQQEAwIFIDAKBggqhkjOPQQDAgNJADBGAiEAjg5/UE89+mf2UZoZTai22aZDU1SGtq9IhiI7eBXHV3oCIQDPOBGZ1THCGazuI/o/9SU30+bmopvG2G5BjfXj7nEKgWhhdXRoRGF0YVjESZYN5YgOjGh0NBcPZHZgW4/krrmihjLHmVzzuoMdl2NBAAAAAAAAAAAAAAAAAAAAAAAAAAAAQMSk7/O4OTTdZLSgSjPngoksEUFn5CZ3O6GnBq/fCEW16pNcoe0q5dm9x84fmcCslMb3FrjzsIhfbbaES33RzyelAQIDJiABIVggq+WDIfs6aMQ3bgxUV0fldJaCyFw0wuUySap8113NFKUiWCB0eV6nFpD59E8WkCXzD2rEmw4ckz2KaG1KUBMgdCDBiA==

Ok, regarding the attestationCertificateKeyIdentifiers field in metadata, this is a field that is (according to the conformance test tool):

mandatory for U2F authentificators
forbidden for FIDO2 authentificator

So regarding this point, I won't do anything.
This app support U2F, but it was mostly as a fallback for Firefox on Linux and Mac.
Now that Firefox now supports Fido2, I don't even know how to trigger U2F registration with an up to date OS + platform.

And I've also found the source of your attestation.
It is in fact an attestation from a Nano S Plus device running app-u2f application.
The corresponding certificate can be found here: https://github.com/LedgerHQ/app-u2f/blob/develop/attestations/data/prod/U2F/nanosp-cert.der
You can see a decoded version here: https://lapo.it/asn1js/#MIIBVDCB-qADAgECAgEoMAoGCCqGSM49BAMCMCcxJTAjBgNVBAMMHExlZGdlciBGSURPIEF0dGVzdGF0aW9uIENBIDEwHhcNMjIwMjA3MTUyNjQ4WhcNMzIwMTI2MTUyNjQ4WjAnMSUwIwYDVQQDDBxMZWRnZXIgRklETyBBdHRlc3RhdGlvbiBDQSAxMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAnQWQZXDuQy-OvCWivTzYQi_oCGKzdr2MyCtzqEON0-P1e8EO90yZpVZ3GNkGzBRen4EMQ3Ed1ihalZbcoX-dKMXMBUwEwYLKwYBBAGC5RwCAQEEBAMCBSAwCgYIKoZIzj0EAwIDSQAwRgIhAI4Of1BPPfpn9lGaGU2ottmmQ1NUhravSIYiO3gVx1d6AiEAzzgRmdUxwhms7iP6P_UlN9Pm5qKbxthuQY314-5xCoE
So you are comparing it against the wrong metadata.
Also note that the root Ca is not the same for the app, it can be find here: https://github.com/LedgerHQ/app-u2f/blob/develop/attestations/data/prod/ca-cert.pem
Eventually, as this app is deprecated, I won't take the time to create and commit a corresponding conformance metadata.
I hope that this answers your questions.
I'm closing this issue, let me know if I missed something.

I recently watched videos about the new Ledger products highlighting the passkey abilities of Ledger Flex. has this app been updated to be compliant since then?


Not able to configure a mesh

Hello,
with this role it is not possible to configure a mesh.
To configure a mesh each peer needs to know it's peers. The documentation says:

--mesh.peer value: initial peers (repeat flag for each additional peer)

so I need to be able to repeat the mesh.peer flag in the role var "alertmanager_cli_flags"
I tried
alertmanager_cli_flags:
  mesh.peer=123.456.789.1:6783
  mesh.peer=123.456.789.2:6783

but only the last "mesh.peer" is passed to the cli as parameter. I looked at the code and it seems that a dictionary/map is used which always overrides the the same key with another value. That's why only the last key is passed
A workaround I found is setting a default value and passing "more":
alertmanager_cli_flags:
  log.level: "info --mesh.peer=123.456.789.1:6783 --mesh.peer=123.456.789.2:6783"

It can be an issue with software version (python, ansible) or jinja template. I will try to catch it.

It's not an issue with software. Basically it comes down to 2 things:

design of alertmanager, which accepts multiple mesh.peer parameters on command line
defining alertmanager_cli_flags as dict, which in turn doesn't allow duplicate/multiple keys

I think we have two ways of fixing it:

change alertmanager_cli_flags to store a list of values
separate mesh configuration into another variable (ex. alertmanager_mesh) and concatenate it with alertmanager_cli_flags in service template.

For me second way is clearer and maybe will allow us better control, since we could write some preflight checks and notify user if he/she does sth wrong.

I totally agree with paul - this is a problem of the role.
I would also prefer the second way. Also this gives you more flexibility when the configuration of the mesh configuration changes (from the alert manager  side). Which most likely will, as it it under active development as described in the readme


ui5 appto cloud foundry

Hi I have created some local tiles from the UI5 html tiles and added to catalog and group and roles over night I see those tiles are duplicate meaning two tiles are showing up for each tile created and the original HTML tile that I copied from also updated with my name as creator and creation date as yesterday. even when i delete the duplicated tiles I cannot update the content its giving me error.
something like below do you guys have any suggestion. I dont even know what to make of this error log?
{"error":{"name":"FdcReplicateError","error":{"config":{"url":"https://ui5-flexibility-design-and-configuration.cfapps.us20.hana.ondemand.com/sap/bc/ui2/app_index/replicate","data":"{"instanceId":"623208e6-2b9a-4df7-842b-72acfa98c230","appHostIds":[],"boundAppHostIds":["530f5ba4-be28-449f-ad24-42759071ade6","93b62901-822a-46d6-b6d8-61b68888b3c8","0c9ff7e9-6038-4336-9b15-c0a4f594a039","bdee47ae-2916-43c7-8d99-d0081d22d9b5","b54587a6-52f5-49c5-82e0-c2002e2a9a7d","477e8e12-d912-41da-99d5-094e11e6eddd"],"contexts":{"a4ad10e5-13a1-4304-9014-

Can you please specify the title or URL of the tutorial in question?

@cjbernal might this be an issue with one of your tutorials?
https://developers.sap.com/tutorials/appstudio-sapui5-create.html

Hi @jmmargo based on the description -- an issue with tiles for UI5 apps -- I do not believe this is an issue with that tutorial or something related. That group has to do with developing an application only.
@adnan-siddiqu could you please provide the tutorial you followed to create the tile?

@adnan-siddiqu please reopen this issue if it is still relevant.


clientv3: fix panic message in OpPut

/cc @heyitsanthony @xiang90

lgtm

thanks. merging in greens.