fix: data passed to refreshInterval function is not latest

@hong24 Thank you! Could you add a test for this?

There is an issue when data is a dependency: refreshInterval will be called twice
one time when data is changed,
the other time when revalidating successfully

I have other questions：

The first call to refreshInterval is with undefined. In my understanding, It's supposed to call refreshinterval after the first fetch is resolved and with the resolved data.
When the key is nutl, the fetcher wil be not called, but ref reshInterval will be called over and over againAccording to the related source code, this problem may be expected but It's a little weird and unintuitive.
I'm currently just fixing the latest data, but for the above two issues, I don't have a good solution.

There is an issue when data is a dependency: refreshInterval will be called twice

Is this a problem? I think refreshInterval would be a pure function that returns an interval time, so it would be ok to be called twice. It seems to make sense to reset the timer when data has been changed.

I think this is a problem. Even a pure function called twice doesn't make sense, and the parameters of the refreshInterval call are different twice. Once with the latest data and once with the previous data.

I got hit by this issue today.
Additionally seems that there's another problem too: If the function passed to refreshInterval is staying unchanged between the useSWR calls, it seems to get called only once and that call is with the undefined data; but it won't get called  anymore after the data arrives. As a workaround I can define the refreshInterval as a lambda so that it'll change between successive useSWR calls.
Here's an example from my current code, which tries to keep data of a job up-to-date with the refreshInterval:
export function useJobInfo(jobId: JobId | null)  {
  return useSWR(
    jobId ? `/jobs/${jobId}` : null,
    fetcher,
    {
      dedupingInterval: 250,

      // This doesn't work, since function would be called only once:
      //refreshInterval: jobId ? getRefreshIntervalOfJob : 0,

      // This is the workaround:
      refreshInterval: jobId ? (jobInfo) => getRefreshIntervalOfJob(jobInfo) : 0,
    }
  );
}

function getRefreshIntervalOfJob(jobInfo: JobInfo | undefined): number {
  ...
}

Additionally seems that there's another problem too: If the function passed to refreshInterval is staying unchanged between the useSWR calls, it seems to get called only once and that call is with the undefined data; but it won't get called anymore after the data arrives.

Actually, now that I checked again, have to correct my statement: It will be called again, if I return non-zero value from the function when it's called for the first time (with the undefined value). However, all successive calls are still done with the undefined value, even if the data is already fetched.
Seems like that the next function has the data stored in the closure and it won't update when refreshInterval function is called with the timer. The fix in this PR seems to help in my case too.
Any plans to release this fix?


Add logging in operator controller

Please provide a description of this PR:
Adding additional log statements to troubleshoot unexpected issues during operator reconciliation.
In my case, authz errors were not printed when the ClusterRole was misconfigured and resulted in below error:
istiooperators.install.istio.io "istiod" is forbidden: User "system:serviceaccount:mesh-control-plane:istio-operator-rvfzv5kdwqktwvc" cannot update resource "istiooperators/status" in API group "install.istio.io" in the namespace "mesh-control-plane"

Hi @raakella. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

@raakella: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
543856cb5ca55a4b8b832abf30a631f87171d700
link
true
/test release-notes

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.


Better handling of empty (not missing) docstrings

What does this implement/fix?
Some python build tools/processes set docstrings to empty strings. (Not -OO). This can be beneficial to work around various libraries depending on docstrings existing but not caring about their value. Some places in scipy already work with empty string, this aligns some existing handling that wasn't consistent.
Additional information

Can you add some more info on what is the motivation for these changes? Does somebody/something really reach into the library and fiddle with __doc__ attributes?

Can you add some more info on what is the motivation for these changes? Does somebody/something really reach into the library and fiddle with __doc__ attributes?

At Dropbox we deploy a monolithic application. Setting docstrings to empty strings saves 5%+ from memory usage, but we do it selectively for modules (it's enabled for 99% of modules) Using -OO is not an option because we cannot enable it for all modules, and stripping assertions will break the application. Currently we are not stripping docstrings for scipy but would like to remove this exclusion from our list.

Thanks.
Could you rebase on master, to see if the CI failures go away.

At Dropbox we deploy a monolithic application. Setting docstrings to empty strings saves 5%+ from memory usage

Almost everything should work with __doc__ = None already. So is the main issue that you're using empty strings instead of None?

When editing the parsed AST, docstrings must be set to a string, not None. So yes, we set them to empty strings. (Another approach is to completely remove docstring nodes, but this is more complex cause then you need to insert pass statements).

The CI failures look real

FYI @dzbarsky in case you want to get this into 1.4.0, we are going to branch in under two weeks

@larsoner updated. The only failing test is https://github.com/scipy/scipy/blob/c437dc0e84d8b7c4942cdff6a1eb99430e47e134/scipy/linalg/tests/test_decomp.py#L2472-L2484 which I don't see how it's affected. Is it a flake? Could we retry/merge this PR if it passes? Hopefully it makes the 1.4 branch!

All green, in it goes. Thanks @dzbarsky.


Update welcome file to include how to add images from local computer

It's not very specified in the welcome file how to add images that are not stored on the local computer. I see that you can grab images from your google photos, but I do think that it should be mentioned in the welcome file if there is only one, or multiple ways to add an image.

My fork warehouse supports clipboard or drag and drop uploading of images.
StackEdit+ : https://stackedit.net
open source: https://github.com/mafgwo/stackedit-plus


Archive repository

Since the last commit was 9 years ago, and the package is deprecated, should the repo be listed as a public archive?

Will do.


API Gateway Gotcha: No support for Form data

For https://github.com/open-guides/og-aws#api-gateway-gotchas-and-limitations
This bit me hard, so it would be nice to see in the guide to help others lose time. Sorry, have not been able to find a more authoritative source than this stackoverflow answer. :/

Apex/Up has a nice form data wrapper and the only else worth noting is the API GW limits here:
http://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#api-gateway-limits


Docker Image

Hello, is it possible to get a docker image from this repo? Unfortunately I can not use python but would like to use the script over a rest api or similar.

I’d love a way to be able to use it - ideally via Node Red ?


Update Node.js Runtime stack

What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?

update schema to 2.2.0;
use https protocol for the nodejs devfile

Which issue(s) this PR fixes:
Link to github issue(s)
https://github.com/eclipse-che/che/issues/22869
PR acceptance criteria:

[ ] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[ ] Test automation
Does this repository's tests pass with your changes?
[ ] Documentation
Does any documentation need to be updated with your changes?
[ ] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:
https://workspaces.openshift.com/#https://raw.githubusercontent.com/azatsarynnyy/registry/patch-1/stacks/nodejs/2.2.0/devfile.yaml

/ok-to-test

As we are bumping up the schema version of the devfile I'd bump up also the version of the stack.

Done.
Thanks @thepetk and @ibuziuk for reviewing the PR!

@devfile/che-team could you please review this PR?

@BethGriggs @svor & @azatsarynnyy
once the tests pass I'll merge the PR

/retest
These failures doesn't look related to the changes.

/retest
These failures doesn't look related to the changes.

Need to try again later, there might be a problem with the CI environment right now.

/retest
These failures doesn't look related to the changes.

Need to try again later, there might be a problem with the CI environment right now.

@Jdubrick I feel is the same issue you're experiencing on https://github.com/devfile/registry/pull/414#issuecomment-2147414300

Confirmed that there is issues with the image builder in the CI environment that is causing the current failures, waiting for further updates.

/retest


feat: update scaling test results for the admission controller

This PR updates scaling test results for the admission controller.

/cherry-pick release-1-12-0

You'll need to manually pick this until 1.13.


Comma Character in URI Regex Incorrectly Parsed

Summary
Comma characters in URI regular expressions are not correctly parsed; Kong sees this character as an entity split, not part of the expression.
Steps To Reproduce

Add API object with regular expression containing comma

$ curl localhost:8001/apis -d name=test -d upstream_url=http://httpbin.org -d uris="/foo/\d{1,3}"
{"uris":"uri with value '3}' is invalid: must be prefixed with slash"}

Additional Details & Logs

Kong version ($ kong version)

0.11.0rc2

Kong debug-level startup logs ($ kong start --vv)

N/A

Kong error logs (<KONG_PREFIX>/logs/error.log)

N/A

Kong configuration (registered APIs/Plugins & configuration file)

No entities, no configuration changes.

Operating System

Trusty

Interesting. I gave this a bit of thought when I saw it during the weekend. This is trickier than it seems at first, for both UI and implementation reasons. For one, when one tries to do the obvious thing and quote the value in the curl call as in the example above:
$ curl localhost:8001/apis -d name=test -d upstream_url=http://httpbin.org -d uris="/foo/\d{1,3}"

...the quotes are consumed by the shell and the process gets it unquoted anyway, s:
$ function foo() { echo $1; }
$ foo uris=hello
uris=hello
$ foo uris="hello"
uris=hello

so even if we added support for quoted array arguments to protect the comma, the user would have to write it like this, which is awkward:
$ foo uris='"hello","world"'
uris="hello","world"

...and then we'd get to the point on how exactly to implement this, because of all of the corner cases in the grammar (e.g. how should uris="hello"hello,world parse?)
An alternative to quoting would be to require some form of escaping when using commas in regexps, and then the user would have to write something like uris=/foo/\d{1\,3} (and the implementation would still have to be smarter than Penlight's split), and we'd have to document that corner-case accordingly.
Usability-wise, if we only care about commas in the {n,m} case and not arbitrary commas in URIs (are they even allowed in URIs? since that never came up before, I suppose that was not a problem... or maybe people use %2c instead?), an alternative would be to make the parsing a bit more complicated and treat , inside {} as not an array separator for URI arrays. It's special-casey, but for the user's perspective, it's the approach were things "just work". With whatever solution we go with, the parsing will have to be smarter than split anyway, so that sounds reasonable to me.

Why not change the way the uris is accepted to a proper way. like in a json accept an array, and in form encoded do it like arrays are done in get params. uris[]="hello" uris[]="world".

@argentum47 Yes, that is our long-term plan, but we'll have to find an interim solution until then, we won't be changing the entire syntax of the Admin API just a few days before a major release :)

@thibaultcha okies. that makes sense.

This is now fixed thanks to #2794! @argentum47 #1391 is apparently the first issue tracking this non-compliant way of parsing arrays. We will eventually address that!


feat(addon-commerce): update currencies

Closes #6896
Added the following currency codes mentioned in the issue: 048, 203, 348, 498, 951, 985.
Code 742 in PR is ommited because it belongs to the old Turkish Lira which is now obsolete and its name can be confused with the new Turkish Lira, which has been officially called "Turkish lira" since 2009.

@AndreiBelokopytov Could you add also cherry-pick to v3.x, please


Added initial schema for spack.location.json file

Addition of a new schema that validates spack.location.json, which is generated during automated deployment of models using spack.
References https://github.com/ACCESS-NRI/build-cd/issues/33

Drafting because we may not be using md5hash after all (noted during a standup with @aidanheerdegen

It was becoming problematic trying to determine the paths to all the deployed executables. Also it probably makes more sense to use the spack build hash as the common key between builds and the executables used in an actual experiment (and the individual runs therein).
The spack hash is part of the exe file path and can be extracted from there.
It may still be worthwhile have a schema, thought it would be much simpler.

Replaced md5hash with spack_hash - we don't have to do any special extraction of the path to get the hash though, as we can just have spack find --format='{name}@{version} {prefix} {hash}' and then jq that result. More robust that way.

Tested this in the dev spack image - it looks like:
{
<EMAIL_ADDRESS>{
    "path": "/opt/release/linux-rocky8-x86_64/intel-2021.2.0/zstd-1.5.5-xlzd2wkffb2jozmkjoni7iu7vns6iejj",
    "spack_hash": "xlzd2wkffb2jozmkjoni7iu7vns6iejj"
  }
  # ...
}

We don't actually require the addition of hash to the spack.location.json - it is already found in the spack.lock file.

I don't think we need to have the hash in the spack.location.json because that information is already in the spack.lock - what do you think about that @aidanheerdegen ?

I don't think we need to have the hash in the spack.location.json because that information is already in the spack.lock - what do you think about that @aidanheerdegen ?

If they're in separate files don't we need the hash as a common key?

I don't think so. The spack.location.json and (of course) the spack.lock are both created in the context of the same environment. Since I'm pretty certain that we won't be installing multiple of the same exact package in the same environment (note that this isn't true for the global environment, but that isn't relevant here) we can have the spec as the common key (eg<EMAIL_ADDRESS>

I don't think so. The spack.location.json and (of course) the spack.lock are both created in the context of the same environment. Since I'm pretty certain that we won't be installing multiple of the same exact package in the same environment (note that this isn't true for the global environment, but that isn't relevant here) we can have the spec as the common key (eg<EMAIL_ADDRESS>
I didn't want to rely on the files just existing in proximity to link the information they contained.
I don't think the version spec is sufficient to uniquely identify the spack hash: it doesn't encode variants or other differences that would result in a different spack build hash. I understand that this is unlikely to happen in a single environment, but it feels like the right thing to do, and honestly pretty harmless.
If we wanted to get fancy we could make the spack hash the key and the other information the values.

On a call with @aidanheerdegen we decided that we'd replace the spec with the spack hash, like so:
{
  "ajshdbjasdbjasdbh": {
    "path": "/g/data/blah..."
  },
  "3h827y32r872our": {
    "path": "/g/data/blahblah..."
  }
}

we decided that we'd replace the spec with the spack hash, like so:

Just a follow up to note that this works with the spack.lock as we're effectively adding a field that is missing (the path) to the record that is indexed with the spack build hash.


Missing dependencies in install

i don't what is the error is but got an installation error
attack.go:8:2: cannot find package "github.com/pkg/errors" in any of:
/usr/lib/go-1.10/src/github.com/pkg/errors (from $GOROOT)
/home/mninr/go/src/github.com/pkg/errors (from $GOPATH)
attack.go:7:2: cannot find package "github.com/ullaakut/go-curl" in any of:
/usr/lib/go-1.10/src/github.com/ullaakut/go-curl (from $GOROOT)
/home/mninr/go/src/github.com/ullaakut/go-curl (from $GOPATH)
discover.go:6:2: cannot find package "github.com/ullaakut/nmap" in any of:
/usr/lib/go-1.10/src/github.com/ullaakut/nmap (from $GOROOT)
/home/mninr/go/src/github.com/ullaakut/nmap (from $GOPATH)
attack.go:9:2: cannot find package "gopkg.in/go-playground/validator.v9" in any of:
/usr/lib/go-1.10/src/gopkg.in/go-playground/validator.v9 (from $GOROOT)
/home/mninr/go/src/gopkg.in/go-playground/validator.v9 (from $GOPATH)

Hi @neetesshhr,
A few questions to try to help you out there:

Why are you trying to build Cameradar, when there is an available docker image that you can use from any OS without the need for any dependency?
Did you make sure to use an up to date version of go, like stated in the documentation? (version superior to 1.10)
Did you enable go modules by setting GOMODULE111=on in your environment?
What is the command you ran to get this output?

Any update, @neetesshhr? :)

yap i tired but i can't solve this problem not quite familiar to linux
enviroments
and thank you for your appreciable response sir
On Fri, May 24, 2019 at 12:15 PM Brendan Le Glaunec <
<EMAIL_ADDRESS>wrote:

Any update, @neetesshhr https://github.com/neetesshhr? :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Ullaakut/cameradar/issues/198?email_source=notifications&email_token=AHOTARZEB75JVG5NBYD7LETPW6DPZA5CNFSM4HMPQSAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEJB4Q#issuecomment-495489266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHOTARYXRB6SZPYMNGWYZXLPW6DPZANCNFSM4HMPQSAA
.

--
https://about.me/rijalboy?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb
nitesh rijal
about.me/rijalboy
https://about.me/rijalboy?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb

There is a confusion with low case and upper case of "Ullaakut" name.
For example, https://github.com/Ullaakut/cameradar/blob/master/scan.go#L6 calls "ullaakut/nmap" but it calls itself with upper case https://github.com/Ullaakut/nmap/blob/master/xml.go#L9.
I have tried to correct it, but it made travis unhappy:
https://github.com/Ullaakut/nmap/pull/13
Please make up your mind and fix it everywhere.

"nmap" is also mentioned twice in the https://github.com/Ullaakut/cameradar/blob/master/go.mod due to this bug.

Will fix during my lunch break 👍 Thanks @blshkv. It's not related to this issue though, so if you could, please open a new issue for this 🙏

hm.. sorry, it might be not related indeed. Ok, the pull request will be enough at this point

I think the original issue was due to not following the documentation properly, and since the OP didn't really give more information, I'll close this one. @neetesshhr feel free to reopen it if you have more information on your issue and want help with this.
Otherwise, you'll be happy to hear that today I added goreleaser support so you'll be able to directly download cameradar binaries for your OS at the next release! 🎉


[HUDI-5078] Fixing determination of table service for metadata calls

Change Logs
While applying commit metadata to metadata table, there is an argument "isTableService" to determine whether the triggering action is a table service or not. We mistakenly considered any replace commit as table service. Right fix is, only clustering is table service and other replace commits are not.
Impact
Metadata compaction will make progress with replace commit actions like INSERT_OVERRIDE after this patch.
Risk level (write none, low medium or high below)
low.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@xushiyan : feel free to take another look.

I did not want to introduce another overloaded method for
ClusteringUtils.getClusteringPlan(

So, have kept it just for that use-case. have removed elsehwere.

@xushiyan @danny0405 : addressed all reviews


[feat] Update to objkt.com v3 GraphQL API before January 30, 2023

Describe the problem
From objkt.com: "Earlier this month we released a new public API endpoint.
v2 will be shut down on January 30, 2023, roughly 3.5 months from now.
All public API users currently using https://data.objkt.com/v2/graphql will have to adapt their queries and migrate to https://data.objkt.com/v3/graphql before January 30, 2023.
To help with the migration here is an outline of the changes: https://data.objkt.com/docs/changes-v3.html"
Describe the solution you'd like
Update to objkt.com v3 API
Alternatives considered
No response
Additional context
No response

Afaik this will be handled by teztok anyway in our case in January. @xat

yes, shouldn't affect us.


Specify num_threads for searching

Dear developers!
Thank for all the work done in NGT.
Is there any way to also limit the number of threads for search?

NGT uses just one thread for each one query. Does this answer your question?

By default, there's a ThreadPool created of 32 threads. It would be nice to be able to change this value in python.

ThreadPool is used only for building an index. You can specified the size in these methods:  batch_insert, build_index.


x/tools/gopls: diagnostics not cleared after configuration change

When gopls receives a major configuration change (one that requires reloading), it does not explicitly purge diagnostics for all files. As a result, if the configuration change causes a file to no longer be considered part of the workspace, or if under the new configuration the file does not have diagnostics, gopls will not re-publish empty diagnostics.
Low priority, as configuration changes are rare, but this is wrong.

This may be fixed by #42814.

Closing as a dupe.


[Bug]: beam_PostCommit_Py_VR_Dataflow is failing in translations_test.TranslationsTest.test_run_packable_combine_{globally,limit}

What happened?
Failing tests:

apache_beam.runners.portability.fn_api_runner.translations_test.TranslationsTest.test_run_packable_combine_globally
apache_beam.runners.portability.fn_api_runner.translations_test.TranslationsTest.test_run_packable_combine_limit

First failure: https://ci-beam.apache.org/job/beam_PostCommit_Py_VR_Dataflow/9972/
I don't see an obvious culprit commit in that run
Issue Priority
Priority: 1
Issue Component
Component: runner-dataflow

@riteshghorse could you take a look at this?

Sure

Looks like the build is green again


Redirect to trade details when recnt trade item is selected

Fix #88
This PR implement redirect to the trade details page when a trade item is selected from the overview page.

on highlighting the card bg still remains white

the buttons after the order status does not show


Swift

Hi there,
Would it be possible for you to translate your documentation in Swift ? That'd be very much appreciated.
Thanks :)

Translating docs won’t help since LFHeatMap is in Obj-C, right?
Jann

On Apr 5, 2016, at 1:08 PM, Leonard Bonfils<EMAIL_ADDRESS>wrote:
Hi there,
Would it be possible for you to translate your documentation in Swift ? That'd be very much appreciated.
Thanks :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/gpolak/LFHeatMap/issues/8

Hello, @janngobble is correct, the code is ObjectiveC and would need to be ported to Swift. You could also use a bridging header to use this in your Swift code: https://developer.apple.com/library/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html

fyi - I came across this project https://github.com/shazlehu/SoilSampler/tree/Swift2/SoilSampler which includes a pure swift implementation of DTMHeatmap https://github.com/dataminr/DTMHeatmap.
(Side Note - it seems to be a line by line port - but swift is much slower to render. )

Thanks @johndpope, I've added a link to DTMHeatmap to the README.


Range Error

Sometimes this error happens randomly
index-Cah95BwU.js:86 Uncaught RangeError: Trying to find position for a DOM position outside of the document
    at N6.posFromDOM (index-Cah95BwU.js:86:47594)
    at Ye.posAtDOM (index-Cah95BwU.js:89:13133)
    at HTMLDocument.O (index-Cah95BwU.js:91:64965)

It might be to do with some of the hover interactions on the editor. Hopefully we could just wrap something in a try/catch and ignore the error.

Could be the same as https://github.com/vizhub-core/vzcode/issues/793


AN-246 Create prod pools with Batch API enabled

Follow-on to https://github.com/DataBiosphere/terra-resource-buffer/pull/367 and https://github.com/DataBiosphere/terra-resource-buffer/pull/368. Create prod pools with GCP Batch API enabled.
Also switches pool env used for integration testing from toolsalpha to buffertest.

Merging past test failures that are unrelated to these changes.

Closing and opening a new PR against this branch to get around GHA issues.


spoof call of duty mobile garena

this is not an issue , but for currently codm has updated their graphics to MAX and frame rate to 144fps in ULTRA option.
you may spoof the model as ROG Phone 8 which is AI2401_A

test with this
Game Unlocker.zip


Generalized the python code

[x] Generalize the Python code by removing Project specific parts.
[ ] Adapt and use the generalized package for the project.

In that way, the other projects can also use the code.

the code is very generic and lives at https://github.com/mess-nlesc/kunefe


GitHub: New repository

Required information:
Please create this as a private repository in https://github.com/catenax-ng

Details to your GitHub repository: product-federated-catalogue
Details to GitHub team to grant access: product-essential-services

validation / approved by: @MehranRoshandel

Hi @MehranRoshandel could verify this request and the upcomming repository names?
repo product-federated-catalogue
grant access to product-essential-services

Hi,
We do here only a poc with our team. There is no reason to make it public. Furthermore we put a copy of another public repo. If somebody need it, he can approach the original repo.

Hi @MehranRoshandel,

Furthermore we put a copy of another public repo.

Could you tell us which one do you want to copy in this private repo?
Thanks in advance.

Hi @MehranRoshandel and @adkumar1,
repository is now present
https://github.com/catenax-ng/product-federated-catalogue and gh-team product-essential-services
Please verify and close the issue, if your fine with the result.

would close the issue for you, please take care of your issue 😉


how can i solve Openai Error (500 Error)?

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

i am trying to re-deploy this demo locally, however, i keep having a under issue.
when i run this demo through terminal, then it works very well.

Any log messages given by the failure

ERROR:root:Exception in /chat
Traceback (most recent call last):
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\app.py", line 121, in chat
r = impl.run(request.json["history"], request.json.get("overrides") or {})
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\approaches\chatreadretrieveread.py", line 64, in run
completion = openai.Completion.create(
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\backend_env\lib\site-packages\openai\api_resources\completion.py", line 25, in create
return super().create(*args, **kwargs)
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\backend_env\lib\site-packages\openai\api_resources\abstract\engine_api_resource.py", line 153, in create
response, _, api_key = requestor.request(
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\backend_env\lib\site-packages\openai\api_requestor.py", line 227, in request
resp, got_stream = self._interpret_response(result, stream)
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\backend_env\lib\site-packages\openai\api_requestor.py", line 620, in _interpret_response
self._interpret_response_line(
File "C:\Users\funny\open_ai_demo_yg\azure-search-openai-demo\app\backend\backend_env\lib\site-packages\openai\api_requestor.py", line 680, in _interpret_response_line
raise self.handle_error_response(
openai.error.APIError: Unable to get resource information. {"error":{"code":"InternalServerError","message": "Unable to get resource information."}} 500 {'error': {'code': 'InternalServerError', 'message': 'Unable to get resource information.'}} {'Content-Length': '89', 'Content-Type': 'application/json', 'x-ms-client-request-id': 'Not-Set', 'apim-request-id': '615f2b8c-7ad6-4bd5-ab42-d2ceb0db7b7a', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains; preload', 'x-content-type-options': 'nosniff', 'Date': 'Tue, 04 Jul 2023 10:19:37 GMT'}
<IP_ADDRESS> - - [04/Jul/2023 19:19:38] "POST /chat HTTP/1.1" 500 -
INFO:werkzeug:<IP_ADDRESS> - - [04/Jul/2023 19:19:38] "POST /chat HTTP/1.1" 500 -

Expected/desired behavior

OS and Version?

Windows 11

azd version?

azd version 1.0.2

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Same error here.

@funny1853 Please, did you manage to solve the problem?

one more case here - same issue on :
M1 Air
Contributor role in Azure
prior to execution of start.sh I've ran az login to determine correct Azure subscription
Errors are 100% exact.

It seems like something isn't correct with the OpenAI instance.
One thing you could do is check .azure/YOUR-ENV-NAME/.env and inspect the OpenAI related variables. Here's what mine looks like:
AZURE_ENV_NAME="bothgpt"
AZURE_FORMRECOGNIZER_RESOURCE_GROUP="rg-bothgpt"
AZURE_FORMRECOGNIZER_SERVICE="cog-fr-xenf7xvucmwaw"
AZURE_LOCATION="eastus"
AZURE_OPENAI_CHATGPT_DEPLOYMENT="chat"
AZURE_OPENAI_GPT_DEPLOYMENT="davinci"
AZURE_OPENAI_RESOURCE_GROUP="rg-bothgpt"
AZURE_OPENAI_SERVICE="cog-xenf7xvucmwaw"
AZURE_RESOURCE_GROUP="rg-bothgpt"
AZURE_SEARCH_INDEX="gptkbindex"
AZURE_SEARCH_SERVICE="gptkb-xenf7xvucmwaw"
AZURE_SEARCH_SERVICE_RESOURCE_GROUP="rg-bothgpt"
AZURE_STORAGE_ACCOUNT="stxenf7xvucmwaw"
AZURE_STORAGE_CONTAINER="content"
AZURE_STORAGE_RESOURCE_GROUP="rg-bothgpt"

I can then go into Azure Portal for the "rg-bothgpt" resource group, confirm there's an OpenAI service named "cog-xenf7xvucmwaw" and that it has two deployments.

You can also inspect Access control to make sure "my access" includes an OpenAI role:

If all looks good at this point, I'd suggest going into OpenAI studio, using the playground, then generating code in the playground and seeing if it runs locally.

same problem here can run locally on some devices, but not on some other, using the same resource. Any progress?

@pamelafox thank you for responding, the region is east-us, the error is:
Error: Unable to get resource information. {"error":{"code":"InternalServerError","message": "Unable to get resource information."}} 500 {'error': {'code': 'InternalServerError', 'message': 'Unable to get resource information.'}} {'Content-Length': '89', 'Content-Type': 'application/json', 'x-ms-client-request-id': 'Not-Set', 'apim-request-id': 'edbe2b70-ae2d-44d5-b786-286e18f72e44', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains; preload', 'x-content-type-options': 'nosniff', 'Date': 'Tue, 01 Aug 2023 08:00:55 GMT'}
It worked on a friend's local environment with the same code, the same resources, and the same environment variable.

@Xiang-CH Hm. Which line of code is producing that error? Here's what I suggest for debugging it:

Isolate that line of code into a Python file and try running it on its own, with all the same settings you're using in app.py (i.e. AzureDefaultCredential)
Try using Azure OpenAI studio for the same deployment, and copy the generated Code from the studio. Run that locally and compare the results.

Usually if I do that, I can discover what's wrong with my local environment.

@Xiang-CH I ran into the same error today in fact, and I followed my suggested steps for debugging it, and I realized that openai.api_base was not set correctly. Another thing that helps is to enable debug-level logging of the app, as it will show you the request URLs and data sent to the openAI SDK.
logging.basicConfig(level=logging.DEBUG)

I am using macOS, and to simplify the startup script in start.sh, I started directly from bash with the ./backend_env/bin/python -m quart --app main:app run --port 50505 --reload command.
I got the exact same error.
Just before the error, I printed the values of the openai settings and found that the values set in openai.api_base were different.
print(openai.api_base, openai.api_version, openai.api_type, openai.api_key)
chat_completion = await openai.ChatCompletion.acreate(
...

Finally, it turned out that the cause was that I had not executed azd env get-values in the start.sh script, so I changed it to execute this command to load .azure/YOUR-ENV-NAME/.env into the environment variable and then start the backend server, and it worked fine.

For me it was because I was logged in to az cli with a different account. Switching to the account which had access to OpenAI deployment fixed the issue.

Closing as this issue seems obsolete.


Update tutorial.md for v0.9.3

I was just trying out the tutorial and found that the functions are moved out.

Thanks, I guess this is an improvement on the existing state of affairs. Really, it needs updating for 1.0 at some point.


Update dependency to resolve issues with php 8.0

It turns out that the other package
uses a reserved keyword, thus
making it impossible to use it.

Thank you for this.


Use plone.api instead of kitconcept.api

(This might require moving some features from kitconcept.api to plone.api, like extra parameters for api.user.create)

relates to #20 - Plone CLI does not use it

I would keep it here until we move the features to plone.api.

No, in an officially supported package we can not use company namespaces, sorry.

Moving any necessary features to plone.api is exactly what I was trying to say with this ticket.

We already have
https://docs.plone.org/develop/plone.api/docs/api/user.html#plone.api.user.create


Add version support to ltm profiles

Some profiles were not implemented in version 11.6.0. SDK needs to be able to check that

implemented in 0.1.7


Room profiles

Issue
It should be possible to store room description and image in profiles, similar to that of character profiles.
See discussions on Wolfery Forum:
https://forum.wolfery.com/t/feature-room-profiles/224/7
Notes

For starters, only description, and image is stored in room profiles.
To prevent command conflicts, commands should use the concatenated keyword roomprofile. Eg: create roomprofile winter = Winter landscape
 set roomprofile : name = Winter season
 update roomprofile winter
 delete roomprofile winter

Help category help build rooms is used for room profile commands.
A GUI, similar to that of Character profiles should be added as a modules:

pageRoomProfiles
pageEditRoomProfile
dialogCreateRoomProfile

Resolved in merge e6555efbe5080eee9c2863e4ca96bbd6b711ed17


[rv_dm dv] Add SBA TL access test

This commit prepares the JTAG DMI agent and adds a well randomized SBA access test via JTAG -> DTM -> DMI -> SBA. There is no checking at the moment, but the waves look promising. The extensive set of checks in the scoreboard will come in a future PR.

That looks great! Much better than the original jtag_riscv_agent!

Thanks but I did take inspiration from your agent so that was good work as well!


Review OpenStack Security Groups

I was just looking through the openstack security groups and noticed a few port-specific routes in the "default" group. Since this group gets applied to every machine instance, services such as web servers should have their own security group so that we can apply them only to the servers that need them.
I have created a new security group, allow-www-world that allows 80 and 443 on both IPv4 and IPv6. I would like to add this security group to the cantusdb-production instance, and remove the corresponding rules in the default group. However, it would be better if someone on the DDMAL admin team did this so that they could ensure it doesn't break anything in the process.
Additionally there are a number of SSH access IP addresses that should be moved from the default group. I reviewed some but left ones that looked like they were set up for a specific purpose. If nobody knows what they are, I will delete them.

I don't know what any of the ssh rules in the default group are for (I believe anyone in DDMAL takes advantage of one of the rules in the cantus-staging-access group for access). So maybe those are related to other instances on Jennifer's allocation?
In terms of making the switch to the allow-www-world the idea is just to make sure that someone is on hand to notice if something goes wrong on Cantus Database? It's the same rule, just in a different group, right?

It's the same rule, just in a different group, right?

Yep! In fact, I just added cantusdb-production to the new group. Since there are no objections, I'll remove the other rules and hope it doesn't break anything. (It shouldn't).

Done, and everything seems to work. Closing.


Trigger checks every week

Closes https://github.com/foundry-rs/starknet-foundry/issues/1039
Add schedule trigger to checks so they are run every week. This way we don't have to manually test this action for new releases since the checks will eventually run.
I did not implement triggering the checks explicitly by new Starknet Foundry releases because it would require setting a personal access token.

It doesn't solve the issue, the workflow uses fixed snforge version


codegen: Use _ instead of argN for unnamed arguments.

Less code, more fun.

 Warning

These commits modify unsafe code. Please review it carefully!

r? @fitzgen

Err, of course this isn't going to work for methods that have a body, like constructors, nvm.


Do you divide the LAION-Aesthetic-6.5+ dataset into a training set and a test set?

I do not see a test set in my LAION dataset, there are only images and their corresponding information in this dataset. How do you creat your test set?

I have the same question, may I ask have you solved this problem?

I also have the same question. I can't really find the so-called test set to evaluate the FID.


fix: timeout now passed from pool-manager

:tada: This PR is included in version 1.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed 500 errors in head requests - forwardauth

What does this PR do?

Possible fix for https://github.com/traefik/traefik/issues/6124
A Head-Request has no body and therefore this request runs on an error.
With the check if the request is a head request you can easily avoid this.
Motivation
Bugfix:docker push does not work with auth module
More

[ ] Added/updated documentation
[ ] Added/updated tests

Additional Notes

https://github.com/thomseddon/traefik-forward-auth/issues/156

Hello @volker-schukai,
Thanks for your contribution and interest on Traefik!
I've tried to reproduce the issue you are facing but without any success. In the Traefik code, we are only issuing GET requests to the configured fowardauth address so nothing could be related to a potential HEAD request bug on our side.
I think the issue is in the traefik-forward-auth project you are using. As described in https://github.com/thomseddon/traefik-forward-auth/issues/156 the log cause (Cause: context deadline exceeded (Client.Timeout or context cancellation while reading body)) seems to indicate that Traefik is waiting for a response body which never arrives.
As we think that it's not a Traefik issue, we will close this PR accordingly.


Temporarily documentation site till original one is fixed

You can decide whenever you want to change this temporarily or not - so people don't ask constantly why the docs aren't working.
-- You can also just change the A record to point to my VPS if you want to use the same domain (also an option)
Or you leave it like this without proper documentation right now

no longer needed


Feature request: add a Time formatting library

It would be great if there was also a Time.format which does the same thing, but for times (it would only need to replace hours, minutes and seconds in the format string).

That would be nice but it's not at the top of my priority list. I'll accept a PR.

Closed by #19 and released in 1.3.0.


Resizing of query result cells

Is your feature request related to a problem? Please describe.
As a user, I get frustrated when the results of my query are too large for the visible pane and I need to use scrollbars to access it.  If the rows are not near each other, I cannot visually compare the results side by side without scrolling.
Describe the solution you'd like
I would like the ability to drag and drop the edge of the results pane so I can resize it vertically and horizontally and view all of my results without scrolling (limited to the screen/browser size of course)
Describe alternatives you've considered
The sample notebooks provide a code snippet that allow horizontal resizing to 100% of the screen, but not vertical resizing.
Additional context

A --no-scroll option is now available in all query magics, this allows for resizing the vertical limit of the query results table to unrestricted length.


vendor/product/versions in container but not mentioned in README

The CISAADP container has the affected.vendor, affected.product, and affected.versions fields in at least several hundred CVE Records, but nothing in https://github.com/cisagov/vulnrichment/blob/034bc878aecbbc99cc211b0ceafa3fc53ddb5459/README.md mentions that this should be occurring. Also, in at least a few cases, the vendor/product/versions data is inaccurate relative to both the CNA container and the references. For example, here is an off-by-one error (for the version 24.0.1) caused by erroneous replacement of lessThanOrEqual with lessThan:
https://github.com/cisagov/vulnrichment/blob/4395c94d8d03a63ab67976dd9c820fb3c6152169/2024/20xxx/CVE-2024-20794.json#L18-L25
https://github.com/cisagov/vulnrichment/blob/4395c94d8d03a63ab67976dd9c820fb3c6152169/2024/20xxx/CVE-2024-20794.json#L139-L148
If enriching vendor/product/versions is currently less important than CVSS/CWE/CPE, then one might consider an alternative design of the affected property:
"affected": [
        {
          "cpes": [
            "cpe:2.3:a:a_legitimate_vendor_name:a_real_product_name:*:*:*:*:*:*:*:*"
            ],
          "collectionURL": "https://github.com/cisagov/vulnrichment/blob/develop/NULL-collection.md",
          "packageName": "NULL",
          "defaultStatus": "unknown"
        }
      ]

in which collectionURL/packageName/defaultStatus would be the same in all CISAADP containers that provide an affected property. Then, https://github.com/cisagov/vulnrichment/blob/develop/NULL-collection.md could offer a brief explanation that it is not really a collection, that CISA is not enriching vendor/product/versions in the initial production rollout, but (because of the current design of the CVE Record Format) JSON validation requires perfunctory non-blank values for collectionURL/packageName/defaultStatus.

This looks like it's blocked, or possibly just influenced by, this upstream issue in CPE-land: https://github.com/CVEProject/cve-schema/issues/321 . More cycles shall be spent on this to figure out how to best solve this issue for everyone, not just ADPs or CVEs.

An option is to document the behavior (in the README), at least until a more lasting solution or decision is in place.

Still blocked by https://github.com/CVEProject/cve-schema/issues/321 .

Currently being discussed at Quality Working Group in CVE.

Hi @ElectricNroff ! Is this actually resolved by #117?


FAILURE: fluttertoast:compileDebugJavaWithJavac

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':fluttertoast:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':fluttertoast:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: C:\Users\Micha\AppData\Local\Android\sdk\platforms\android-33\core-for-system-modules.jar.
         > jlink executable C:\Program Files\Android\Android Studio\jre\bin\jlink.exe does not exist.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2m 15s
Error: Gradle task assembleDebug failed with exit code 1

Exited (1).

I had the same problem.

I had to restart the device and VisualCode. Go to the terminal and from the terminal access your flutter project folder. Once inside the directory, perform a Flutter clean to clean the whole project and once that is done, open the project again and it should work.

Thanks for help ⭐🔥


smpl pose illustration when get embedding

Hello Sirui,
I was confused by the function _get_embeddings() in the file diffusion_smpl.py that you concatenate the body pose in both past and the future.
body_pose = torch.cat([frame['smplfit_params']['pose'][:, :66].unsqueeze(0) for frame in data['frames']], dim=0).float().to(device)
Why did you choose 66 here? I print out the original pose shape from behave dataset which was TxBx156. Could you illustrate a little bit here?
Best,
chrenx

I actually found out that 66 may be due to MANO which replaced smpl hand with mano model. 3 + 21 x 3 if we don't count the hand, this would be 66. Is this right?

Hello @chrenx,
Yes, you are correct. The number 66 is for the body pose other than hands. The reasons are:
The emphasis in this work is on the body parts other than the hands, which, despite their importance, are represented by fewer parameters in SMPL. And we find training without hand poses is helpful.
The BEHAVE dataset, at the time of our submission, did not offer detailed data on hand poses. I'm not sure if this has been released recently. So, our method just replicates the final hand pose from the past sequence for the generation.
Best regards,
Sirui


Add logo for custom network GOS

Support logo for custom network GOS follow up this guild:
https://swtch-labs.gitbook.io/grid-operating-systems-guide/gos-wallet/subwallet
Logo resources (Need resize 160x160 and  update to squirrel format):

@saltict this logo apply for GOS network GOST network and GOS/GOST token? Please confirm for me

@Sokol142196 native token of GOS is MGOS


FindShortestNoVidPath

Add the class FindShortestNoVidPath.
The class means that FindShortestPath when there is one vid does not exist.

@HarrisChu 79#PR was submitted before, but during the modification process, PR may be closed due to forced rollback on my computer. So I open the new PR. Thank you for your review.

@casualwind btw, we are setting up a special interest group and will launch a test program, and before the public publish, we would like to have an internal beta test, are you interested to join?
We will basically release some utils and procedures that we could easily generate some perf tests and report, which could be shared in the community.
我用中文说下哈，我们会搞一个测试的社区兴趣小组，小组里准备发起一个公开的社区活动：大家一起测试 NebulaGraph 的性能，会提供一些工具和手册，让大家在不同的环境里跑出来结果，分享给大家。我们准备在启动公开之前，开启内测。不知道你是否感兴趣哈？

@wey-gu I am interested in getting involved in the community🤭

@wey-gu I am interested in getting involved in the community🤭

Awesome! Would you mind mail me your wechat id via weyl.gu at gmail dot com?
We are about to have the internal discussion about this in this week :)

@wey-gu I am interested in getting involved in the community🤭

Awesome! Would you mind mail me your wechat id via weyl.gu at gmail dot com?
We are about to have the internal discussion about this in this week :)

I have try to contacted with you via wechat.


SliverCrossAxisGroup does not work with pinned SliverPersistentHeader

Putting a SliverPinnedPersistentHeader inside of SliverCrossAxisGroup has some weird behavior.
As the group scrolls out of view, the pinned header remains, overlapping content until the full extent of the group is scrolled away, after which point it disappears suddenly.
https://github.com/flutter/flutter/assets/16964204/86e600d1-1a5c-418b-bee5-e8309e695117
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: CustomScrollView(
          slivers: <Widget>[
            SliverCrossAxisGroup(
              slivers: <Widget>[
                SliverPersistentHeader(
                  pinned: true,
                  delegate: SimpleDelegate(Colors.pink)
                ),
                SliverList.builder(
                  itemCount: 20,
                  itemBuilder: (BuildContext context, int index) => Text('Item $index'),
                ),
              ],
            ),
            SliverPersistentHeader(
              delegate: SimpleDelegate(Colors.blue),
            ),
            SliverList.builder(
              itemCount: 100,
              itemBuilder: (BuildContext context, int index) => Text('Item $index'),
            ),
          ],
        ),
      )
    );
  }
}

class SimpleDelegate extends SliverPersistentHeaderDelegate {
  SimpleDelegate(this.color);

  final Color color;

  @override
  Widget build(BuildContext context, double shrinkOffset, bool overlapsContent) {
    return Container(color: color, child: const Center(child: Text(
      'Header',
      style: TextStyle(color: Colors.white),
    )));
  }

  @override
  double get maxExtent => 60;

  @override
  double get minExtent => maxExtent;

  @override
  bool shouldRebuild(covariant SliverPersistentHeaderDelegate oldDelegate) => true;
}

Flutter doctor
[✓] Flutter (Channel master, 3.11.0-6.0.pre.53, on macOS 13.3.1 22E772610a darwin-x64, locale en)
• Flutter version 3.11.0-6.0.pre.53 on channel master at /Users/katelovett/_github/flutter
• Upstream repository git@github.com:flutter/flutter.git
• Framework revision d132b724c5 (23 hours ago), 2023-05-15 17:49:52 -0500
• Engine revision c784d6d413
• Dart version 3.1.0 (build 3.1.0-102.0.dev)
• DevTools version 2.23.1
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc2)
• Android SDK at /Users/katelovett/Library/Android/sdk
• Platform android-33, build-tools 31.0.0-rc2
• Java binary at: /Applications/Android Studio with Blaze.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
• All Android licenses accepted.
[!] Xcode - develop for iOS and macOS (Xcode 13.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 13E500a
✗ Flutter requires Xcode 14 or higher.
Download the latest version or update via the Mac App Store.
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio
• Android Studio at /Applications/Android Studio with Blaze Beta.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.5-9884540)
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio with Blaze.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.3.3)
• IntelliJ at /Users/katelovett/Library/Application
Support/JetBrains/IntelliJUE_Base2022.3/IntelliJ IDEA.app
• Flutter plugin version 73.0.3
• Dart plugin version 223.8888
[✓] VS Code (version 1.78.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.64.0
[✓] Connected device (2 available)
• macOS (desktop) • macos  • darwin-x64     • macOS 13.3.1 22E772610a darwin-x64
• Chrome (web)    • chrome • web-javascript • Google Chrome 113.0.5672.126
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.

FYI @thkim1011


Suggested Peers at list not loading (503 in console)

Description
Suggested Peers at http://zap.jackmallers.com/api/v1/suggested-peers list not loading. Getting a 503 error in the console.

@mrfelton this can be closed ya?

yep, thanks!


Removing masks?

How do you remove/unset masks? Can't find it in issues or in the getting started guide
Thanks

You can do that with:
term.set_mask(false);

It seems that I need to add this to the documentation.

Thanks, do you know where I should put it in this code to ask for the password then once they have it remove it.
secret: function() {
            hashCode = function(s){
                return s.split("").reduce(function(a,b){a=((a<<5)-a)+b.charCodeAt(0);return a&a},0);
            }
            this.set_mask('*').read('Password: ').then(pass => hashCode(pass) == '-1152556145' ? this.echo('\n[[;green;]Access granted.]') : this.echo('\n[[;red;]Access denied.]'));
        },

Already tried some combinations but they always end up remove the mask before they put the password
Thanks

Thanks, do you know where I should put it in this code to ask for the password then once they have it remove it.
secret: function() {
            hashCode = function(s){
                return s.split("").reduce(function(a,b){a=((a<<5)-a)+b.charCodeAt(0);return a&a},0);
            }
            this.set_mask('*').read('Password: ').then(pass => hashCode(pass) == '-1152556145' ? this.echo('\n[[;green;]Access granted.]') : this.echo('\n[[;red;]Access denied.]'));
        },

It goes inside the .then handler which is called with the password when the user presses enter.
.then(pass => {
  this.set_mask(false);
  if (hashCode(pass) == '-1152556145') this.echo('\n[[;green;]Access granted.]')
  else this.echo('\n[[;red;]Access denied.]'));
});

Thanks so much!


Request: VR Platform and Store Additions

Store:
Oculus
Sidequest
Viveport
SteamVR ??
Platforms:
Vive
PSVR
Oculus Go
Oculus Rift/Rift S
Oculus Quest
Valve Index

This has my vote as well. I wish I could plop my oculus game list in.

SteamVR shouldn't really be considered a separate store or a platform really, it's just an API. Honestly it's more of a platform than a store. The thing missing right now in the integrations ID list are the three VR exclusive storefronts (Oculus, Viveport, Sidequest).
Better support for VR in general would be welcome (Eg, Steam labels with which headsets the game are compatible), but those changes would be a lot harder than adding the store IDs right now.

Agreed on Steam VR. As I have gotten more into VR it doesn’t make sense. However it would be nice to have a VR watermark on VR games in the steam store

I'd love full support for SteamVR as well.  It would be great to get Oculus, and also have an option on launch to use Revive for those of us not using an Oculus headset.  If you need a tester, please contact me.  Thanks.

Oculus support would be fantastic! To me, SteamVR works because Steam works well.  I just tag the VR games with a VR tag and added as a bookmark to the left nav.

Aggregated in mentioned task.


Add GH Action to weekly update i18n

To prevent weird strings in production when they are not extracted and compiled.
Fixes https://issues.redhat.com/browse/AAH-1123

(adding this to a few recently updated PRs…) We need CI in this repo that enforces this, but for now please:

Add a line to at least one of your commits that says Issue: AAH-#### (in the future it is best to be the first commit as it gets included in the initial PR description by default)
Ensure when merging that the Issue: AAH-#### is part of commit message via the “Squash ‘n’ Merge” description


Assuming role/user doesn't work in smart_open.open

Problem description
I'm using the smart_open.open method to stream items data from S3 to use in my code.
According to the docs, if I want to access the service with different credentials that the system user profile, this is how it's supposed to be done:
session = boto3.Session(
    aws_access_key_id=os.environ['AWS_ACCESS_KEY_ID'],
    aws_secret_access_key=os.environ['AWS_SECRET_ACCESS_KEY'])

path="mybucket/file.json"
with smart_open.open(f"s3://{path}", mode='r', transport_params={'client': session.client('s3')}) as file:
    for line in file:
        print(json.loads(line))

But that just throws the following error:
unable to access bucket: 'mybucket' key: 'file.json' version: None error: An error occurred (AccessDenied) when calling the GetObject operation: Access Denied

The user that owns these credentials has all the necessary permissions. I know that because when I have tried to set the system profile to that user it worked fine.
Does anyone know how to solve this?
Thanks
Steps/code to reproduce the problem

Create a user/role in AWS that has full control on S3 (for the sake of reproducing the problem)
Verify that the current AWS profile is different from the new role you set (run aws sts get-caller-identity)
Try to read the content of a file that is hosted on S3 bucket with smart_open.open (like shown above)

Versions
Windows-10-10.0.18362-SP0
Python 3.8.8 (default, Feb 24 2021, 15:54:32) [MSC v.1928 64 bit (AMD64)]
smart_open 3.0.0
Checklist
Before you create the issue, please make sure you have:

[v] Described the problem clearly
[v] Provided a minimal reproducible example, including any required data
[v] Provided the version numbers of the relevant software

So, I have a solution to this issue.
After digging into the library code, the docs are misleading (as far as I can tell).
Instead of passing the actual client, you need to pass the session. The following works:
session = boto3.Session(
    aws_access_key_id=os.environ['AWS_ACCESS_KEY_ID'],
    aws_secret_access_key=os.environ['AWS_SECRET_ACCESS_KEY'])

with smart_open.open(f"s3://{path}", mode='r', transport_params={'session': session}) as file:
    for line in file:
        print(json.loads(line))

The current version of smart_open is 5.0. You're using 3.0.

I see, thanks!


[New chain]: Hemi Mainnet

Chain Name
Hemi Mainnet
RPC URL
https://8deb9c0b.rpc.hemi.network/rpc
The chain must be added to https://chainlist.org/

[X] I confirm that the chain is added to chainlist

After creating the issue, a bot will estimate the required pre-fund and post it in the comments. Please check this checkbox after you send the pre-fund.

[ ] I sent the pre-fund in accordance with Github Action's comment

Relevant information
No response

@nlordell Above factory is deployed as predeploy. How can we add artifact for this factory?

@rokso you can follow the worldchain example https://github.com/safe-global/safe-singleton-factory/pull/705 and create a PR yourself

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

So how we go about deploying factory at 0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC. We need this factory to claim same safe address as on OP/Base.

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

So how we go about deploying factory at 0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC. We need this factory to claim same safe address as on OP/Base.

See this paragraph in the docs here: https://github.com/safe-global/safe-smart-account/tree/v1.3.0-libs.0?tab=readme-ov-file#replay-protection-eip-155
You'll most likely need to replace the @gnosis.pm/safe-singleton-factory package with @safe-global/safe-singleton-factory or add the deployment artifact manually to the node_modules folder or edit the hardhat config directly


Move splitTyping() from public to internal function

Codecov Report

Merging #68 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #68   +/-   ##
=======================================
  Coverage   86.93%   86.93%
=======================================
  Files           8        8
  Lines         352      352
=======================================
  Hits          306      306
  Misses         46       46

Impacted Files
Coverage Δ

R/splitTyping.R
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Improvement for supporting images where the image version is not recognized

Hi,
Today I discovered that using this image:
    "visStudio_2022_Pro_win11-m365-gen2": {
        "publisher": "microsoftvisualstudio",
        "offer": "visualstudioplustools",
        "sku": "vs-2022-pro-general-win11-m365-gen2",
        "version": "latest"
    }

Results in a date format not recognized by the Get-SHRLatestImageVersion.ps1. This is because the RegEx expects a year format of 24 instead of 2024. But the Image Version provided above results in 2024, resulting in an error when running the Function App.
So I changed this code:
if ($azImageVersion -match "\d+\.\d+\.(?<Year>\d{2})(?<Month>\d{2})(?<Day>\d{2})") {
    $azImageDate = Get-Date -Date ("20{0}-{1}-{2}" -f $Matches.Year, $Matches.Month, $Matches.Day)
    Write-PSFMessage -Level Host -Message "Image date is {0}" -StringValues $azImageDate
}
else {
    throw "Image version does not match expected format. Could not extract image date."
}

With this code:
if ($azImageVersion -match "^(?<Year>\d{2}|\d{4})\.(?<Month>\d{2})\.(?<Day>\d{2})$") {
    if ($Matches.Year.Length -eq 2) {
        $year = (Get-Date -Format "yyyy").Substring(0,2) + $Matches.Year
    } else {
        $year = $Matches.Year
    }
    $azImageDate = Get-Date -Date ("{0}-{1}-{2}" -f $year, $Matches.Month, $Matches.Day)
    Write-PSFMessage -Level Host -Message "Image date is {0}" -StringValues $azImageDate
} else {
    throw "Image version does not match expected format. Could not extract image date."
}

Perhaps you can use it in this project or provide me with feedback to even solve this in a better way?

Hey great find! I will review the rest of the images and try to include this in the next release. Stay tuned for the beta 🐣

Thanks, and thanks for having this project! Enjoying it!
I will stay tuned for the beta.


BitLocker docs missing BackupToAAD-BitLockerKeyProtector

The BitLocker documentation  covers every function in the BitLocker module except BackupToAAD-BitLockerKeyProtector.
There is some coverage of it in these docs:

https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises
https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq

It would be great to get some documentation on which version of Windows 10 support this cmdlet and some examples.
I had to write a wrapper script, because it was erroring out, even though it actually worked, so some more details would be nice. T
https://github.com/mardahl/PSBucket/blob/master/Invoke-EscrowBitlockerToAAD.ps1

It would be great to get some documentation on which version of Windows 10 support this cmdlet and some examples.
I had to write a wrapper script, because it was erroring out, even though it actually worked, so some more details would be nice. T
https://github.com/mardahl/PSBucket/blob/master/Invoke-EscrowBitlockerToAAD.ps1

I see that this issue has been fixed:
https://docs.microsoft.com/en-us/powershell/module/bitlocker/backuptoaad-bitlockerkeyprotector


Standardizing commands

I've extracted an interface called IdentifiableResults to mark all the commands that uses the OutIdentifier property to return a value.
In a different commit I've modify the SetGlobal Command to not use the out boolean and work in the same way at the other commands that uses the OutIdentifier. Notice that the out boolean was set True and no one else was using it.
This is the first step to improve and standardize the commands

Merged

Rather, I'm not seeing an implementation of the IdentifiableResult interface, and that puzzles me. :/


minor UI update on order-landing page

Hi @Shybymh
the hover state of the buttons on the Order Now, Order History, and Track Order cards, changes to white, visually this is not distinctive for those with visual impairments.
I would like to update the hover state, to give a darker salmon/orange color to assist those with visual impairments.
https://c4coderandcreator.github.io/Flavour-Fusion/#order-landing
Can I be assigned to this please

Hi @goobric  !! I just came to create that issue and found that you already had it, great though !! Give it a Go !!

There are lot more PR's approved to the repo, please pull the repo first to your local machine before you start working on this , (To avoid conflicts ) !!


refactor(plugin): simplify impl

此 PR 简化了 Plugin 相关类的实现，对齐了统一的 Interface 命名和使用规则（*Type）

Codecov Report
Base: 90.68% // Head: 91.75% // Increases project coverage by +1.06% :tada:

Coverage data is based on head (81aa6c8) compared to base (f71fa5a).
Patch coverage: 93.18% of modified lines in pull request are covered.

:exclamation: Current head 81aa6c8 differs from pull request most recent head 10de9d4. Consider uploading reports for the commit 10de9d4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #199      +/-   ##
==========================================
+ Coverage   90.68%   91.75%   +1.06%
==========================================
  Files          48       46       -2
  Lines        1106     1091      -15
  Branches      200      198       -2
==========================================
- Hits         1003     1001       -2
+ Misses        103       90      -13

Impacted Files
Coverage Δ

src/plugin/impl.ts
84.31% <89.65%> (+5.14%)
:arrow_up:

src/loader/impl/plugin_config.ts
96.15% <100.00%> (ø)

src/plugin/common.ts
100.00% <100.00%> (ø)

src/plugin/factory.ts
90.90% <100.00%> (+25.28%)
:arrow_up:

src/plugin/index.ts
100.00% <100.00%> (ø)

src/scanner/scan.ts
95.23% <100.00%> (ø)

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.


Updated demo.

Fixes #30.

Updated pod templates with new label prefix.
Minor changes to job scripts and readme.

We can wait on this till there is a resolution for #27.

@balajismaniam is this ok to review?

@ConnorDoyle Updated. PTAL.

/lgtm


finish drawing double click

[ ] I'm reporting a bug, not asking for help
[ X] I've looked at the documentation to make sure the behaviour is documented and expected
[ ] I'm sure this is a Leaflet Draw code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[ ] I've searched through the issues to make sure it's not yet reported

Polygon, line string can not finished when user double click.
It was working previous version. How can we do this behaviour for new version of drawing.
How to reproduce

Leaflet version I'm using: 1.0
Leaflet Draw version I'm using: 0.4.7
Browser (with version) I'm using: Chrome 55
OS/Platform (with version) I'm using: Windows
step 1 Start creating Polygon
step 2 single click for creating points
step 3 double click for finish polygon

What behaviour I'm expecting and which behaviour I'm seeing
Minimal example reproducing the issue

[ ] this example is as simple as possible
[ ] this example does not rely on any third party code

Using jsfiddle or another example site.

Hi @emreesirik,
This problem has been fixed in version 0.4.9. Get here: https://cdnjs.com/libraries/leaflet.draw.

I'm still seeing the same problem after upgrading to 0.4.9, however I'm using Leaflet version 1.0.2
https://jsfiddle.net/b6b232cj/

@Searlon, same thing here.

Still have this issue. 0.4.9, leaflet 1.0.3. It's something to do with Chrome registering as a touch browser, it works okay in Firefox.

Same issue here. Working as well in Safari but not in Chrome. Any workaround? Thanks!

Same issue here on 1.0.3 and 0.4.9.  Anyone know of a workaround or what needs to be fixed?

I fix it by preventing to add new marker when double click on last point.
I'm using leaflet 1.2.0, leaflet-draw 0.4.12 and Chrome 60
This is my code:
L.Draw.Polyline.prototype._calculateDistance = function (potentialLatLng, marker) {
  let lastPtDistance
  if (this._markers.length > 0) {
    const markerPoint = this._map.latLngToContainerPoint(marker.getLatLng())
    const potentialMarker = new L.Marker(potentialLatLng, {
      icon: this.options.icon,
      zIndexOffset: this.options.zIndexOffset * 2
    })

    const potentialMarkerPint = this._map.latLngToContainerPoint(potentialMarker.getLatLng())
    lastPtDistance = markerPoint.distanceTo(potentialMarkerPint)

    console.log(markerPoint, potentialMarkerPint, lastPtDistance)
  } else {
    lastPtDistance = Infinity
  }
  return lastPtDistance
}

const _endPoint = L.Draw.Polygon.prototype._endPoint
L.Draw.Polygon.prototype._endPoint = function (clientX, clientY, e) {
  if (this._markers.length > 2) {
    const dblClickPointDistance = this._calculateDistance(e.latlng, this._markers[this._markers.length - 1])
    if (dblClickPointDistance < 10 && L.Browser.touch) return
  }

  _endPoint.call(this, clientX, clientY, e)
}

anything new on this ?
I would love to see the distance indication on my desktop app

Thanks for the fix @vutrungduc7593
I added one more line to avoid issues when the repeatMode is enabled.
Without this the first click on the map after finishing to draw a polygon was not starting a new drawing.
`
L.Draw.Polyline.prototype._calculateDistance = function (potentialLatLng, marker) {
let lastPtDistance
if (this._markers.length > 0) {
const markerPoint = this._map.latLngToContainerPoint(marker.getLatLng())
const potentialMarker = new L.Marker(potentialLatLng, {
icon: this.options.icon,
zIndexOffset: this.options.zIndexOffset * 2
})
const potentialMarkerPint = this._map.latLngToContainerPoint(potentialMarker.getLatLng())
lastPtDistance = markerPoint.distanceTo(potentialMarkerPint)

console.log(markerPoint, potentialMarkerPint, lastPtDistance)

} else {
lastPtDistance = Infinity
}
return lastPtDistance
}
const _endPoint = L.Draw.Polygon.prototype._endPoint
L.Draw.Polygon.prototype._endPoint = function (clientX, clientY, e) {
if (this._markers.length > 2) {
const dblClickPointDistance = this._calculateDistance(e.latlng, this._markers[this._markers.length - 1])
if (dblClickPointDistance < 10 && L.Browser.touch) {
this._enableNewMarkers()
return
}
}
_endPoint.call(this, clientX, clientY, e)
}
`

Double-clicking to complete drawing a polygon appears to still be broken in the latest released versions of Leaflet (1.5.1) and Leaflet.draw (1.0.4) I created two examples on jsfiddle to show the behavior working in Leaflet 0.7.x but not in Leaflet 1.x.

Double-click to complete polygon working in Chrome and Firefox using Leaflet 0.7.7 + Leaflet.draw 1.0.4 https://jsfiddle.net/kbydqhp6/1/

Double-click to complete polygon broken in Chrome and Firefox using Leaflet 1.5.1 +  Leaflet.draw 1.0.4 https://jsfiddle.net/Lm24xnbw/

Apparently version 1.6.0 of leaflet works with 1.0.4 of draw: https://jsfiddle.net/10msdcon/2/


Bump max line length to 140 characters in Checkstyle rules

Title
Fixes #465 (Disabling LineLength Codacy check?)
Description
Changes the max line length defined in the Checkstyle rules to 140 characters. This value is used in our continuous integration. Per discussion in #465, it seems sensible to a higher max line length.
Tests performed
I checked with Travis CI and gradle checkstyle.

Codecov Report

Merging #1590 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1590   +/-   ##
======================================
  Coverage    3.86%   3.86%
======================================
  Files         149     149
  Lines        7576    7576
  Branches      721     721
======================================
  Hits          293     293
  Misses       7266    7266
  Partials       17      17

Continue to review full report at Codecov.

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


[Champ-Animation] Nami

Animations

[ ] Create animations for Q

[ ] Create animations for W

[ ] Create animations for E

[ ] Create animations for R

Controller

[ ] Create animation controller

R_cast.txt


Saved telescope positions in MC are "wrong"

The saved telescope positions are relative to the unweighted average of the 3 telescopes. This will result in positions which are not consistent with the reconstructed or true core positions stored event-wise. This is very confusing!
https://github.com/cta-observatory/magic-cta-pipe/blob/dbcb3442683b26d7a03fb3be72e375eb199d5e72/magicctapipe/scripts/lst1_magic/lst1_magic_mc_dl0_to_dl1.py#L411-L418

In the stereo reconstruction the saved telescope positions are used, both for reco and for later calculating impact, so there should be no problem. What cannot be done is comparing reconstructed core positions with true ones.
On the other hand, true_impact can be compared to the reco one - both should be "correct", just calculated in different coordinate frames.

Hi,
This seems to have been introduced back in Jan 2022
https://github.com/cta-observatory/magic-cta-pipe/commit/1b5de6c7c26d7057cf5adf7392fda2e3da10dec5#diff-c03540ef6e8c11788e815e8f9f45e8ca165091703d5e1180fe549160c928ef63
Maybe it was related with the first simulations of Yoshiki (maybe they were using the positions shifted w.r.t. COG)
@YoshikiOhtani can you comment?
I agree with Abelardo that it is confusing, even if it does not affect the rest of the chain.

Hi @moralejo and @jsitarek, apologies for a late response. Yes, I introduced these lines to transform the center of the coordinate to the "unweighted" average of the telescope positions. When I was developing this script, I was still using the old MCs (prod5 with 4LSTs+MAGIC) in which all the telescope Z positions were set to the height ~40 m higher than the observation level (= 2158 m). Since the core position is calculated at the height Z = 0, the true and reconstructed core positions looked a bit shifted and thus confusing at that time. In order to make the positions understandable, at least the reconstructed ones, I decided to transform the coordinate before reconstructing the stereo parameters.
However I agree with you that it is not needed now, since the all sky MCs are produced with a higher observation level so the core positions look already understandable. I can push a commit to get rid of this transformation, but I guess it would be better to change the version of the pipeline once I do so.

@jsitarek @moralejo is this still relevant? should we get rid of the corresponding lines? now with the changes from Elisa/Raniere it has also the 4 telescopes.
https://github.com/cta-observatory/magic-cta-pipe/blob/master/magicctapipe/scripts/lst1_magic/lst1_magic_mc_dl0_to_dl1.py#L399-L413

Since either way we had a bunch of breaking changes and still did not start with any massive processing it seems like a good idea to clean it up now.

Ok, I will open a PR later. I first want to understand why some tests fail...