[SPE-1074] Support java publishing

Adds support for java publishing. Tested as a standalone job, has not been tested as part of the full workflow

@TristanSpeakEasy I'm unsure of the best way to test this. I got it working originally by just having the publish action as a standalone thing in a test repo. I got it working there, but not sure how to test as part of the full generation flow

@TristanSpeakEasy I'm unsure of the best way to test this. I got it working originally by just having the publish action as a standalone thing in a test repo. I got it working there, but not sure how to test as part of the full generation flow

so yeah testing of this prior to getting it merged isn't really possible (at least I haven't figured out how yet), so we just need to get it in, set it up on our own https://github.com/speakeasy-api/speakeasy-client-sdk-java repo and iterate until it works.

So there are some missing changes here to update the releases.md with the publish java package information.
I will actually have a PR up myself soon showing the work required for PHP publishing that you can use as a template for updating this

Here is the PR https://github.com/speakeasy-api/sdk-generation-action/pull/8 I am going to get this in, tested and released which should answer all the questions of what you need to do to complete this PR

@TristanSpeakEasy I'm unsure of the best way to test this. I got it working originally by just having the publish action as a standalone thing in a test repo. I got it working there, but not sure how to test as part of the full generation flow

so yeah testing of this prior to getting it merged isn't really possible (at least I haven't figured out how yet), so we just need to get it in, set it up on our own https://github.com/speakeasy-api/speakeasy-client-sdk-java repo and iterate until it works.

okay after going through some iteration myself we possibly don't need to republish the package each time we make a change as you can link to a git commit sha from workflows. I will try this out and report back on its success

@TristanSpeakEasy I'm unsure of the best way to test this. I got it working originally by just having the publish action as a standalone thing in a test repo. I got it working there, but not sure how to test as part of the full generation flow

so yeah testing of this prior to getting it merged isn't really possible (at least I haven't figured out how yet), so we just need to get it in, set it up on our own https://github.com/speakeasy-api/speakeasy-client-sdk-java repo and iterate until it works.

okay after going through some iteration myself we possibly don't need to republish the package each time we make a change as you can link to a git commit sha from workflows. I will try this out and report back on its success

nope not possible yet :( the action is currently intrinsically linked to the release tag

@TristanSpeakEasy I'm unsure of the best way to test this. I got it working originally by just having the publish action as a standalone thing in a test repo. I got it working there, but not sure how to test as part of the full generation flow

so yeah testing of this prior to getting it merged isn't really possible (at least I haven't figured out how yet), so we just need to get it in, set it up on our own https://github.com/speakeasy-api/speakeasy-client-sdk-java repo and iterate until it works.

okay after going through some iteration myself we possibly don't need to republish the package each time we make a change as you can link to a git commit sha from workflows. I will try this out and report back on its success

nope not possible yet :( the action is currently intrinsically linked to the release tag

@chase-crumbaugh I think I will just have to show you the workflow as its a bit bonkers

@chase-crumbaugh what is the status of this? I will have a PR today as well and it will need to bump the version number, if this is merged in first then I will use the next version number but if mine goes in first you will need to bump the version number in this again

Ok if we merge this ? Have got some customers banging down the doors for java publishing 😂


Matomo

This installs Matomo if no pre-existing database exists.  The company that made matomo specifically doesn't want you to do non-interactive installs (they offer it as a service i think).  So this is the "accepted practice"... dumping an existing db and passing it around :vomiting_face: So yeah... I template out a sql file and import it.  Just avert your :eyes:  FWIW it's what we're doing in the playbook, too.
Other than that, there were a few gotchas.  I'm adding a X-Forwarded-Uri header with traefik so things work out ok with Matomo behind the proxy.  I also changed the "front porch" url to islandora.localhost, and gave Traefik and alias of islandora.localhost so the backend services can still reference each other using their public urls.  We could've just kept going with drupal.localhost, but there is a difference between the drupal service and "islandora itself", so I thought it'd be better to be explicit.
Testing Instructions

Pull in this PR
./gradlew build
docker-compose up -d
visit islandora.localhost/matomo/ and you should be routed to matomo's login
login with admin/password
you got a matomo site!
go visit islandora.localhost and do some stuff
go back to islandora.localhost/matomo/ and now you should see your visit in the dashboard

On a quick review this looks good to me, I'll test in the morning and if all is well, I'll merge it.

Works locally, I needed to destroy my existing volumes but that's fine.


Support the graphics APIs

Currently the OpenXR OpenGL/D3D/Vulkan/... functions are excluded entirely.

Calling this done with stubs:

D3D11
D3D12
Vulkan

OpenGL can be added similarly, and more detailed trace information can be added by expanding the macros at the bottom of https://github.com/fredemmott/OpenXR-Tracing/commit/9fd61148814135fc148baf3947df474810824dfd - these macros should expand to comma-separated TraceLoggingValue() macros


Supporting additional macros from spec

The official cel-spec has some additional macros / functions that might be useful for some of our use cases like: exists or exists_one.
Unfortunately I am not able to implement them by myself because: Context.clone() is pub(crate) and not pub:
https://github.com/clarkmcc/cel-rust/blob/f4fa854f7b2ed0e9b41a9f1c477dc8d30dbdbeb6/interpreter/src/context.rs#L115
Am I missing something or wouldn't it be useful to provide the clone functionality and context shadowing also for custom extension functions?

Hi! Yes, it definitely makes sense to expose that. I'll get a fix released. Thanks!

Fixed. Using the main branch you should be able to clone the context now. I created a new issue #32  for the missing macros.


Eyes keypoints accurate

Hello, sorry to borther you again.  Are there some tricks to improve the accurate of eyes keypoints

Hi, it depends. Is the model you trained has similar NME as ours? We provide trained model for data_300W_CELEBA, does it also have the same accuracy problem?
For the trick, if you are OK with a slower model, then you could simply increase the image size during training and testing, to 384x384 or 512x512.

Hi, it depends. Is the model you trained has similar NME as ours? We provide trained model for data_300W_CELEBA, does it also have the same accuracy problem? For the trick, if you are OK with a slower model, then you could simply increase the image size during training and testing, to 384x384 or 512x512.

Below is my NME, because in 300W, some images is side face, norm is 0. Your trained model is very good, the test video is videos/007.avi

300W nme: inf
COFW nme: 0.04915398603548267
WFLW nme: 0.07814149089329324

Since your result on COFW and WFLW is not good, something is wrong for the training.
To see whether the problem is from CelebA, you may first run on data_300W_COFW_WFLW to see if the result is normal. If the result is stiil not as good as in the paper, try using an older version of pytorch.

Since your result on COFW and WFLW is not good, something is wrong for the training. To see whether the problem is from CelebA, you may first run on data_300W_COFW_WFLW to see if the result is normal. If the result is stiil not as good as in the paper, try using an older version of pytorch.

今天看了你的文章，大神你应该是中国人吧。之前的问题的确是训练数据问题，因为我在中国大陆，不能通过官网下载data_300W，你懂的，所以我在国内的其他地方下载的数据，国内的这批数据跟原始的data_300W有些不一样，导致训练出问题，现在拿到原始的data_300W数据训练后，效果还是非常棒的，谢谢了。下面是我的NME，是不是依然有点高

300W nme: 0.03289449954576623                                                                                │
COFW nme: 0.042309520156777115                                                                                │
WFLW nme: 0.07441956483481409

Since your result on COFW and WFLW is not good, something is wrong for the training. To see whether the problem is from CelebA, you may first run on data_300W_COFW_WFLW to see if the result is normal. If the result is stiil not as good as in the paper, try using an older version of pytorch.

今天看了你的文章，大神你应该是中国人吧。之前的问题的确是训练数据问题，因为我在中国大陆，不能通过官网下载data_300W，你懂的，所以我在国内的其他地方下载的数据，国内的这批数据跟原始的data_300W有些不一样，导致训练出问题，现在拿到原始的data_300W数据训练后，效果还是非常棒的，谢谢了。下面是我的NME，是不是依然有点高

300W nme: 0.03289449954576623                                                                                │
COFW nme: 0.042309520156777115                                                                                │
WFLW nme: 0.07441956483481409

谢谢你的肯定，大神不敢当。你现在的结果应该是正常了，因为随机种子没有固定，会有一些波动，但不影响实际使用。


Hacky attempt to navigate to the file line number

Use applescript to tell XCode to go to the line number required. (Silently ignoring errors in current implementation)

I don't know... this sort of works, mostly. AppleScript is slow to run, so it kind of makes for a not-so-clean UX implementation wise. For eg. if the user ends up typing something midway of the AppleScript running, the characters get typed into the active file in XCode. There are other edge cases where this can fail.
That being said, when it works, it works great!

It is indeed a bit hacky. :) I can probably come up with a way to do this without Apple scripts involved. Let me have a closer look over the weekend.

Made a more proper fix just now. It works when new files are selected but there is still an issue if the selected file is already opened.


 They allow a subscriber to match on published messages. That is to say, publishing on task.* simply publishes to a literal topic called task.* and nothing else.
To do what you want, you would probably need two subscriptions: one for the cluster and one for the individual host. Note that's essentially what you're already doing here by publishing on task.* and then on task.hostnameA, you just need to reverse the responsibilities—subscribers determine message matching, not publishers.

Thanks for you answers.
I just want to do this more easier.I think this feature is very useful.

It is useful, but publishing on a wildcard is not supported, only subscribing on one.

As @tylertreat said, you simply need to have 2 subscriptions nc.Subscribe("task.all", ...) and nc.Subscribe("task.hostnameA", ...) on server A (same for server B) and then publish on either task.all for all servers or task.hostnameA for server A.


Template for documentation

What kind of change does this PR introduce?
Adds documentation at
https://supabase.github.io/supautils/
Built with mkdocs


Missing Feature: Adding Grass and Trees in a simple way

This editor would become much more powerful if one could add grass and trees in a very simple way. For example it would be useful if one could just "spraypaint" grass and trees onto the terrain. This feature is available in many other editors. Looking at those might give some ideas how this could be done.

This Feature seems to be implemented now, right?

I think you can use the "models spawn" tool to make grass and forest. :)

Yeah! Thank you so much for implementing that!


Test-Milestone5

Test-Milestone5

added backport-needed/1.0.4 issue: #111.

added backport-needed/1.1.0 issue: #112.


Enabling MTLS between Nginx Ingress Controller and Istio

Bug description
This is similar to Issue #18176
To illustrate what i am trying to achieve, you can check out a simple context diagram i have drawn.

As you can see, i am able to enable and successfully encrypt traffics within the mesh, but interestingly, i will get some ssl error between nginx controller to the service after enforcing mTLS STRICT mode on namespace : alpha.
This may not be technically a bug, but what i observe is that Nginx controller pod, despite being injected with Envoy's side car, is unable to forward "X-Forwarded-Client-Cert"  header to the upstream service.
Is there some work around for this?
I was attempting this based on https://www.tetrate.io/blog/using-istio-with-other-ingress-proxies/ too, but i wonder if its still applicable for Istio 1.6.x and onwards.
[X] Configuration Infrastructure
[X] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[X] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior

Nginx Controller pod should auto inject the client certificate towards the upstream service.

Steps to reproduce the bug

Create a EKS cluster

Install Nginx-ingress controller and Istio 1.6.1

Install sleep/httpbin test services into foo namespace

Install sleep into ingress-nginx namespace

Apply Peer Authentication Policy to foo namespace and set MODE as STRICT

TCP Dump on httpbin service
 kubectl exec -nfoo "$(kubectl get pod -nfoo -lapp=httpbin -ojsonpath={.items..metadata.name})" -c istio-proxy -it -- sudo tcpdump dst port 80  -A

Testing the service

a. Make a request from external browser (You may need to set up AWS ALB and nodeports based on your test env)
b. Make a request from sleep service in  foo namespace to httpbin service
c. Make a request from sleep service in  ingress-nginx namespace  httpbin service
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
Kubernetes Version : 1.16
Istio Version : 1.6.1
nginx-ingress-controller: 0.30.0
How was Istio installed?
istioctl install --set meshConfig.outboundTrafficPolicy.mode=REGISTRY_ONLY --set meshConfig.enableAutoMtls=true   --set values.global.proxy.privileged=true --set profile=default

Environment where bug was observed (cloud vendor, OS, etc)

AWS EKS

dump.txt

@robincher
Hi,
I am facing similar issue. I too have nginx pod inside istio mesh which receives external traffic, but fails with 503 error to forward to request to another service inside mesh which is in MTLS strict mode. My nginx has proxy.conf to upgrade connection, modify header, to rewrite uri etc. The url nginx proxy.conf is points to kubernetes external name type service which has destination service full url. I applied destination rule with istio-mutual to this external name type service, but no luck

@robincher
If I change proxy_set header as below, then it works. Got clue from here - https://github.com/istio/istio/issues/14450#issuecomment-498771781
current rule
proxy_set_header Host $http_host;
changed to
proxy_set_header Host clusterIP service name : port number; e.g. foo-service:8080

Hi @satishmane thanks!
You set this at the ingress controller i presumed? Or at individual ingress object.

I am not using kubernetes nginx ingress controller or ingress object. I have nginx docker image which is deployed as pod with istio sidecar with rules defined in proxy.conf

I have/had exactly the same problem - getting mTLS to work from ingress-nginx with Istio. I added these ingress-nginx annotations and it seems to have fixed it (my main use case is getting authorisation rules to work for segregation)
nginx.ingress.kubernetes.io/service-upstream: "true"
nginx.ingress.kubernetes.io/upstream-vhost: your-app.the-namespace.svc.cluster.local

Seems this is resolved based on the comments above https://github.com/istio/istio/issues/14450#issuecomment-498771781.
There is a feature tracked that would make this work OOTB but its not likely to be implemented soon. Tracking in https://github.com/istio/istio/issues/23494


[Bug]: [Notebook] Accepting an import suggestion within a function adds the import within the function

Description
$title.
Steps to Reproduce

Accepting this adds
function fn() {
    file
import ballerina/file;
}

Affected Version(s)
2201.3.2
OS, DB, other environment details and versions
No response
Related area
-> Other Area
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Moved to https://github.com/wso2/ballerina-plugin-vscode/issues/447.


[6.0] Use bearer auth for binaryTarget or packages from a package registry

Explanation:  Use bearer auth when pulling binary targets or a package from a package registry and the user is token. The issue is that package-registry and binaryArtifact have an auth logic that behaves differently.
Scope: Authorization Header generation when pulling dependencies
Original PR: #7662
Risk: Users named token can't use basic auth anymore
Testing: Unit Test for testing correct Auth Header is generated
Reviewer: @MaxDesiatov

@pwallrich On a second glance, would you be able to point out a place in either the registry spec or any bearer auth specs that specify that token user should work this way? At a glance I'm unable to find supporting documentation for this.

I assume it's this registry auth SE subsection, but waiting for a review from the SE author on the original PR to confirm that the behavior is correct.

So the token as a username comes from  swift package-registry login {{url}} --token {{access-token}} which creates a keychain or netrc entry that uses token as the user.
i.E
machine {{url}} login token password {{access-token}}

Fetching packages from the package-registry works, since the package-registry uses the configuration to decide whether Bearer or Basic Auth should be used.
If you try to pull a binaryTarget from the same server that your package-registry is on it won't work since it uses basic auth with the username token and there's no way to specify that bearer auth should be used afaik.
So basically the issue is that package-registry and binaryArtifact have an auth logic that behaves differently.
Sidenote:
What  makes it even harder to test is that xcodebuild -resolvePackageDependencies seems to have a bug and ignores the type of auth from the package-registry completely and just uses basic auth.

I think I've merged the original PR on main too soon, I would like your input in comments for that https://github.com/apple/swift-package-manager/pull/7662. If we don't get a clarification, we might need to revert it on main to restore the status quo in an abundance of caution.

Closing, as this is reverted on main until a better solution is found: https://github.com/swiftlang/swift-package-manager/pull/7811


Non-latin email addresses aren’t supported

Inspired by this article, I decided to check whether any of the following email addresses work with zod@next’s email string validator. Unfortunately, none of the addresses below are marked as valid, even though Gmail already supports non-latin addresses like:
"josé.arrañoça"@domain
"сайт"@domain
"💩"@domain
"🍺🕺🎉"@domain
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

PR welcome
god knows I'm not gonna try to write that regex

Okay I dug into this and the problem isn't latin characters. They're actually fully supported by the current regex. The problem is the dotless domain. I don't think dotless domains should be supported even if they're technically valid.
But there are some other problems:

the slowness issue you pointed out in #378
the lack of support for emoji/unicode

I've switched over to a new regex that solves these problems in alpha.39.

// from https://stackoverflow.com/a/46181/1550155
// old version: too slow, didn't support unicode
const emailRegexOld = /^((([a-z]|\d|[!#\$%&'\*\+\-\/=\?\^_`{\|}~]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])+(\.([a-z]|\d|[!#\$%&'\*\+\-\/=\?\^_`{\|}~]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])+)*)|((\x22)((((\x20|\x09)*(\x0d\x0a))?(\x20|\x09)+)?(([\x01-\x08\x0b\x0c\x0e-\x1f\x7f]|\x21|[\x23-\x5b]|[\x5d-\x7e]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])|(\\([\x01-\x09\x0b\x0c\x0d-\x7f]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF]))))*(((\x20|\x09)*(\x0d\x0a))?(\x20|\x09)+)?(\x22)))@((([a-z]|\d|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])|(([a-z]|\d|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])([a-z]|\d|-|\.|_|~|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])*([a-z]|\d|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])))\.)+(([a-z]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])|(([a-z]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])([a-z]|\d|-|\.|_|~|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])*([a-z]|[\u00A0-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF])))$/i;
// new
const emailRegex = /^(([^<>()[\]\.,;:\s@\"]+(\.[^<>()[\]\.,;:\s@\"]+)*)|(\".+\"))@(([^<>()[\]\.,;:\s@\"]+\.)+[^<>()[\]\.,;:\s@\"]{2,})$/i;


Machine learning Issue #588 1.3: Central Limit Theorem(D)

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #588

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[x] Machine Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Please create a fresh PR @prishita-s and merge the files in the machine learning branch.

that's what I tried to do. I'm not sure about what needs to be done

@prishita-s create a fresh PR in the Machine Learning branch, do not create it in the main branch. That's all you have to do.

that's what I tried to do. I'm not sure about what needs to be done

Clone the Machine_Learning branch in your local.
use this : git clone -b Machine_Learning https://github.com/girlscript/winter-of-contributing.git
then add the files and create PR.
You can dm me on discord incase it is still not clear to you.


Add compiler support to disable function hoisting

Search Terms
Espruino Typescript, disable function hoisting in typescript
Suggestion
Add compiler support for disabling function hoisting currently transpiled code use a lot of function hoisting features , i know its normal javascript implementation but i have been trying to use typescript in my IOT projects using Espruino , and esprunio interpretter doesn't support function hoisting, so i have to manually change my transpiled code , like __extends , __generator etc
Use Cases
We would be able to use Typescript in Espruino projects
Example
By adding another compileroption flag in tsconfig.json
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Supporting runtimes that aren't JavaScript is outside the scope of our project. It seems like something like this could be detected with a lint rule


Add german translation

Thanks @jamal2362.  Can you push this to gerrit.aospa.co?  We can't merge pull requests because the gerrit sync is only one-way.

Hey Jake
I have never worked with Gerrit before. So I wouldn't know how to open a pull-request there. If you want you can also add it to gerrit.
I always get a permission issue on from gerrit when I push the change.

remote: Resolving deltas: 100% (2/2)
remote: error: branch refs/heads/topaz:
remote: Push to refs/for/topaz to create a review, or get 'Push' rights to update the branch.
remote: User: jamal2362
remote: Contact an administrator to fix the permissions
remote: Processing changes: refs: 1, done
To ssh://gerrit.aospa.co:29418/AOSPA/android_packages_apps_ParanoidGlyph
! [remote rejected] HEAD -> topaz (prohibited by Gerrit: not permitted: update)
error: Error sending some references after 'ssh://gerrit.aospa.co:29418/AOSPA/android_packages_apps_ParanoidGlyph'


3.0.0

Address #75

Codecov Report

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

@@           Coverage Diff           @@
##           master      #76   +/-   ##
=======================================
  Coverage   96.66%   96.66%
=======================================
  Files          36       36
  Lines        1201     1201
=======================================
  Hits         1161     1161
  Misses         40       40

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 493eba1...3ea5917. Read the comment docs.

@tylermilner Good catches - all should be fixed.


config: loosen up BaseDomain and ServerURL checks

Requirements here:

OK:
server_url: headscale.com, base: clients.headscale.com
server_url: headscale.com, base: headscale.net
Not OK:
server_url: server.headscale.com, base: headscale.com
Essentially we have to prevent the possibility where the headscale
server has a URL which can also be assigned to a node.
So for the Not OK scenario:
if the server is: server.headscale.com, and a node joins with the name
server, it will be assigned server.headscale.com and that will break
the connection for nodes which will now try to connect to that node
instead of the headscale server.

Fixes https://github.com/juanfont/headscale/issues/2210

[x] have read the CONTRIBUTING.md file
[x] raised a GitHub issue or discussed it on the projects chat beforehand
[x] added unit tests
[ ] added integration tests
[ ] updated documentation if needed
[x] updated CHANGELOG.md

@kradalby since we're here, I would appreciate if you could stamp my NixOS backport. :) https://github.com/NixOS/nixpkgs/pull/357969


missing labels for logs of container running in gcp / gke

using:
<dependency>
	<groupId>org.springframework.cloud</groupId>
	<artifactId>spring-cloud-gcp-logging</artifactId>
</dependency>

in my spring boot app with all the settings mentioned in https://github.com/spring-cloud/spring-cloud-gcp/tree/master/spring-cloud-gcp-logging the logs of the app have almost no labels for filter them out correcltly. See the following log entry:
{
	insertId: "abc"
	labels: {
		levelName: "INFO"
		levelValue: "20000"
	}
	logName: "projects/<project-id>/logs/<app-name>"
	receiveTimestamp: "2018-02-23T11:34:20.947913720Z"
	resource: {
		labels: {
			cluster_name: ""
			container_name: ""
			instance_id: ""
			namespace_id: ""
			pod_id: ""
			project_id: "<project-id>"
			zone: "europe-west3-b"
		}
		type: "container"
	}
	severity: "INFO"
	textPayload: "message"
	timestamp: "2018-02-23T11:34:20.865Z"
}

The app ist deployed to gcp / gke as a docker image. Additionally the trace Id of spring-cloud-gcp-traceis also not present in the log  entry.
I also tried using
<dependency>
	<groupId>com.google.cloud</groupId>
	<artifactId>google-cloud-logging</artifactId>
	<version>1.17.0</version>
</dependency>

without any improvement in the logs.

What's your logging configuration? Which logging library and appender are you using?

I used logback with the settings from the readme:
<configuration scan="true" scanPeriod="1 minutes">
	<jmxConfigurator/>
	<include resource="org/springframework/cloud/gcp/logging/logback-appender.xml"/>

	<logger name="com.kiwigrid" level="DEBUG"/>

	<root level="INFO">
		<appender-ref ref="STACKDRIVER"/>
	</root>

</configuration>

so com.google.cloud.logging.logback.LoggingAppender is used

This suggests a problem in the google-cloud-logging library. I suspect this class MonitoredResourceUtil is not handling all the labels for GKE correctly. In fact, I see a related issue in their tracker: https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2912.

OK, so we need to stay with logging to the std.out. Is there a way to get the traceId logged correctly, so that the logs gets connected to the traces (recorded via spring-cloud-gcp-starter-trace)
I tried it by logging in json fromat but the relevant labels (labels."appengine.googleapis.com/trace_id") are not present. There will be only the fields X-B3-SpanId and X-B3-TraceIdfrom the MDC in the jsonPayload:
{
	insertId:  "xxxx"
	jsonPayload: {
		@timestamp:  "2018-02-22T18:07:46.631+00:00"
		@version:  1
		X-B3-SpanId:  "xxxxx"
		X-B3-TraceId:  "xxxxx"
		X-Span-Export:  "true"
		level:  "INFO"
		level_value:  20000
		logger_name:  "com.xxxx"
		message:  "msg"
		thread_name:  "registrationTask1"
	}
	labels: {
		compute.googleapis.com/resource_name:  "fluentd-gcp-v2.0.9-mgljq"
		container.googleapis.com/namespace_name:  "xxx"
		container.googleapis.com/pod_name:  "xxx"
		container.googleapis.com/stream:  "stdout"
	}
	logName:  "projects/xxx/logs/xx"
	receiveTimestamp:  "2018-02-22T18:07:50.893906523Z"
	resource: {
		labels: {
			cluster_name:  "xxx"
			container_name:  "xxx"
			instance_id:  "xxx"
			namespace_id:  "xxx"
			pod_id:  "xxx"
			project_id:  "xxx"
			zone:  "europe-west3-b"
		}
		type:  "container"
	}
	severity:  "INFO"
	timestamp:  "2018-02-22T18:07:46Z"
}

I think that in the JSON payload, you need to include the trace field. Can you  give that a try?
The code that processes the JSON is here.
@igorpeshansky Do we have docs for this?

No public docs yet, but they're coming. FWIW, the default value of the trace key is "logging.googleapis.com/trace", so you should use that name for the field in your JSON.

@igorpeshansky I've tried to use the field logging.googleapis.com/trace. This only resulted in:
{
	insertId:  "xxxx"
	jsonPayload: {
		@timestamp:  "2018-02-22T18:07:46.631+00:00"
		@version:  1
		X-B3-SpanId:  "xxxxx"
		X-B3-TraceId:  "xxxxx"
		X-Span-Export:  "true"
		level:  "INFO"
		level_value:  20000
		logger_name:  "com.xxxx"
		message:  "msg"
		thread_name:  "registrationTask1"
	}
	labels: {
		compute.googleapis.com/resource_name:  "fluentd-gcp-v2.0.9-mgljq"
		container.googleapis.com/namespace_name:  "xxx"
		container.googleapis.com/pod_name:  "xxx"
		container.googleapis.com/stream:  "stdout"
	}
	logName:  "projects/xxx/logs/xx"
	receiveTimestamp:  "2018-02-22T18:07:50.893906523Z"
	resource: {
		labels: {
			cluster_name:  "xxx"
			container_name:  "xxx"
			instance_id:  "xxx"
			namespace_id:  "xxx"
			pod_id:  "xxx"
			project_id:  "xxx"
			zone:  "europe-west3-b"
		}
		type:  "container"
	}
	severity:  "INFO"
	timestamp:  "2018-02-22T18:07:46Z"
	trace: "xxx"
}

However, the link to display logs from the stack driver trace page expects the trace id to be under labels."appengine.googleapis.com/trace_id".

@draffensperger to comment on the trace field and the logs link.

@igorpeshansky / @draffensperger I have already figured out how to log so that stackdriver can find the logs linked to a traceId too. See PR #454

Fixed by #454


Automerge error for name

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

Our token name was originally rejected for using a symbol. We submitted another PR with updated name which was auto-closed just now - can it be reopened and merged? it is here ---> Adding JFICall token #19755

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

this was automerged and is in main now:

$ grep etCPUaMghWobVwxug5Vgxb6r3A7DEBdLKUywrnDrJeZ solana.tokenlist.json
      "address": "etCPUaMghWobVwxug5Vgxb6r3A7DEBdLKUywrnDrJeZ",
      "logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/etCPUaMghWobVwxug5Vgxb6r3A7DEBdLKUywrnDrJeZ/logo.png",


Simplify kube-proxy refresh once the kube-proxy ConfigMap is updated

Description
Once the kube-proxy ConfigMap has been updated, we need to restart the kube-proxy pods.
Instead of using two kubectl commands, we can do this in one go.

Issue

Closes: #

/lgtm

/retitle Simplify kube-proxy refresh once the kube-proxy ConfigMap is updated
/approve


Force Node 8.14 in Alpine 3.9

Alpine 3.9 supports only Node 10.14 AFAICT.
This is a problem.
There is a very very popular package, ursa, which does not support this Node version.
This completely breaks our build pipeline on Alpine.
At the same time, Alpine 3.9 provides other required tools, that are not available on Alpine 3.8. e.g. Go 1.11 and OpenSSL 1.1.1...
Is there any way to install Node 8.14 on Alpine 3.9? This will allow us to both restore our pipeline and upgrade the other tools.

Looks like you are not the only one with this problem: https://github.com/JoshKaufman/ursa/issues/167
It also looks like they have fixed it with this pull request: https://github.com/JoshKaufman/ursa/pull/169
Maybe ask ursa to tag a new release? There haven't been any release for 3 years now.

I have tried... no response...
Is it not possible to provide 8x as well for Alpine 3.9? 8.x is still a valdi version of Node to use for some time.

Everything is possible. The impossible just take a little more time. I will ask if some one is willing to maintain a nodejs8 package.

Does nodejs8 support openssl 1.1?

Good question... :/

I was able to build a nodejs8 package but I don't know if we want take responsibility to support it. We will have to push security fixes for 3 different version for every single security vulnerability (nodejs-current, nodejs and now also nodejs8).


List index out of range

when i put the url https://open.spotify.com/playlist/649OfpVgIVrppB0zRV7kAJ it showed the error list index out of range. and when i tried only putting the spotify playlist id 649OfpVgIVrppB0zRV7kAJ there was the same list index out of range error..
full error as follows :-
 Enter the spotify URL link: https://open.spotify.com/playlist/649OfpVgIVrppB0zRV7kAJ Traceback (most recent call last):   File "d:\Durgesh Files\Programming\spotify2mp3\spotify2mp3\run.py", line 296, in <module>     main()   File "d:\Durgesh Files\Programming\spotify2mp3\spotify2mp3\run.py", line 281, in main     playlist_name = html.fromstring(page.content).xpath('/html/body/div/div/div/div/div[1]/div/div[2]/h1')[0].text_content().strip() IndexError: list index out of range
and when i tried putting only the id :-
Enter the spotify URL link: 649OfpVgIVrppB0zRV7kAJ Traceback (most recent call last):   File "d:\Durgesh Files\Programming\spotify2mp3\spotify2mp3\run.py", line 296, in <module>     main()   File "d:\Durgesh Files\Programming\spotify2mp3\spotify2mp3\run.py", line 281, in main     playlist_name = html.fromstring(page.content).xpath('/html/body/div/div/div/div/div[1]/div/div[2]/h1')[0].text_content().strip() IndexError: list index out of range

@DurgeshKavate003 You should now be asked to enter text, if a playlist name couldn't be found.
Please let me know if this solves your issue.
Thanks!

Thanks a lot... I will try and let you know as soon as possible...


Update the exception handling support to the current proposal

The exception handling has changed. The follow simple example should work but produce errors with the current version. V8 already use the new exception handling.
(module
  (event (param externref))
  (func $test
    try
	catch 0
	  drop
	end
  )
)

This should be fixed as of e39784268d9b98bd8af535a08bdfb523d51f756c.


Attempt to add JNI_CreateJavaVM()

Thanks!

Do you plan a new release in the nextish time?
I know this small addition alone would not justif it. But it would let me get rid of my own function declaration - which also would not be much except for nice to have.

Done!

Thanks.


[Card] Initial component (do not merge)

Description

Add Card, CardActions, CardBlock, CardImage, and CardTitle components (and also a non-exported CardRow)
Add demos for each of the above
Add color_black, color_white, and spacing_triple to mineralTheme

Motivation and context

All the cool kids have a Card component.
Screenshots or videos, if appropriate

How has this been tested?

Not yet...
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[ ] Renders and functions properly in all supported browsers
[ ] Automated tests written and passing
[x] Accessibility and inclusivity considered
[x] Rendering performance (initial load time & 60fps) and perceived performance considered
[ ] Documentation created or updated

How does this PR make you feel?

Please note that this is built off of the branch for #170.


.Net Core 3.1.4 is still in Base-Image

Description
Hi Microsoft,
I am wondering why the base image of Microsoft still includes version 3.1.4:
.NET Core Runtime
Location: C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App
3.1.4 3.1.6 3.1.20 3.1.23 5.0.4 5.0.9 5.0.15
Location: C:\Program Files\dotnet\shared\Microsoft.NETCore.App
3.1.4 3.1.6 3.1.20 3.1.23 5.0.4 5.0.9 5.0.15
Location: C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App
3.1.4 3.1.6 3.1.20 3.1.23 5.0.4 5.0.9 5.0.15
Version 3.1.4 still has vulnerablities:
https://www.cvedetails.com/vulnerability-list/vendor_id-26/product_id-43007/version_id-637952/Microsoft-.net-Core-3.1.html
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md
Is it regression?
No response
Expected behavior
No response
Actual behavior
No response
Repro steps
Installing image without 3.1.4

@Chaouki-Tiouassiouine as per our software guidelines we support 2 latest LTS versions and 1 latest version. For each feature version, only the latest patch is installed.
I'm afraid we can't remove the version as it will break some customers who still use it. We will remove all the 3.1 set when it is reached end of life.


Dynamically hide unimportant parts of the Confirm Install text

Geode Version
3.8.1
Related Problem
You get thrown everything at you at once, while in the below case, half of the present information (2/5 of the presented numbers) is actually important:

that 1 mod will be installed
and that it's incompatible with 2 enabled mods.

Your Solution
Only show info with non-zero values, e.g. in the above case show the popup with:
1 mods will be installed.
2 mods will be force-disabled, as they are incompatible: (non-empty list)

Additional Information
For quick reference, this is where the popup text is constructed
https://github.com/geode-sdk/geode/blob/9e82cee2bfb467842163629cf9c52b26fb2d0695/loader/src/ui/mods/popups/ConfirmInstall.cpp#L107-L114

This seems like a good idea, will try and implement 👍


Question about AnyRes calculations: bug or intended?

Hello LLaVa-NeXT team!
I want to clarify some points about the AnyRes technique and how the image feature is unpadded in modeling forward.
As this issue shows, seems like a get_anyres_image_grid_shape function is returning height and width swapped, which in turn results in the shortest edge after unpadding being less than 24.
For more info, below is the code in transformers we adopted from your repo. Function get_anyres_image_grid_shape returns height as first element, but later it's mapped to num_patch_width. In this scenario if we have an image of 2x1 aspect ratio, the final image_feature after unpadding gets size (4096, 24, smth-smaller than 24) which seems incorrect. The question is: if it's a bug or intended behavior?
Btw, I tried inference both ways, by swapping height and width back. Didn't see actual difference as the chosen images prob were too easy, and the model was attending more to the base-image features
def get_anyres_image_grid_shape(image_size, grid_pinpoints, patch_size):
    height, width = select_best_resolution(image_size, grid_pinpoints)
    return height // patch_size, width // patch_size

# later in modeling code (same as in https://github.com/LLaVA-VL/LLaVA-NeXT/blob/6944062b9bb2e61c48436f1a65c3ea339095ec91/llava/model/llava_arch.py#L200-L201)
num_patch_width, num_patch_height = get_anyres_image_grid_shape(
    image_size,
    image_grid_pinpoints,
    vision_config.image_size,
)
image_feature = image_feature.view(num_patch_height, num_patch_width, height, width, -1)
image_feature = image_feature.permute(4, 0, 2, 1, 3).contiguous()
image_feature = image_feature.flatten(1, 2).flatten(2, 3)
image_feature = unpad_image(image_feature, image_sizes[image_idx])

resolved!

Sorry, not resolved. The issue is that in LLaVa-VL during pre-processing it's assumed image is (width, height) in size which aligns  with another assumption, that best-resolutions are also (width, height). But then in modeling, the size of an image embedding is assumed to be height-first, thus causing confusion and incorrect upadding.
image_feature = image_feature.view(num_patch_height, num_patch_width, height, width, -1)
So, let me know if it's a bug or intended please :)


not working with JsonResource::withoutWrapping();

If the laravel application is using JsonResource::withoutWrapping(); the whole translation ui won't work.
after a little of checking looks like in the translations main page the code is accessing the translations as follows translations.data which is in case of JsonResource::withoutWrapping(); It will be just translations.
tried to do this change as PR but as the package only have the compiled JS code it'll be so hard to do so

after another look it looks like this affecting every page in the ui not only the main page

This should be fixed in the latest release.


Add grunt chatter about killed squadmates

This restores a small detail that Grunts speaks when their squadmates dies in multiplayer matches.

I would like to add that grunts have a LOT of voice lines that could be used but aren't, maybe add to issues list?
E.G. "Hostile titan spotted, run to that building"

I would like to add that grunts have a LOT of voice lines that could be used but aren't, maybe add to issues list?
E.G. "Hostile titan spotted, run to that building"

I'm aware of that but lots of their voicelines are restricted to the Campaign. Multiplayer can only access the ones avaliable in the grunt_chatter_mp datatable. I don't remember if the building speech is one of the avaliable ones, i haven't heard grunts use that one on vanilla, although they still flee to buildings when they see enemy titans.

I'll refactor this PR since @ASpoonPlaysGames pointed me some chatter functions that have better implementation.


Set a list  of certs for static configuration

Rolling cert support for static config
(created a new PR to trigger a new build)

Hi @johnkors, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Hey,
sorry - it's been a while.
So I really think this feature is not complete - you would need to able to configure all the other things statically as well - also X509 is just one option here - it could be also raw RSA keys.
Do you want to extend that to support more config - or is it not that important?

No worries, it was just a thought :)
Ok, I just thought that since the remote version using the discovery doc fetches a list of jwks, maybe the static one could include a list as well as opposed to a single cert. Did not consider any other aspects than X509s.


Add files via upload

@imharryz The first verification stage is complete: the official domain for  Lancing College is www.lancingcollege.co.uk, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.lancingcollege.co.uk/lancing-society-ol-club/contact-us

@philipto
Proof of a course related to computer science thats more than 1 year long below - Page 9
https://www.lancingcollege.co.uk/sites/default/files/inline-files/SixthFormChoice/Lancing_College_Sixth_Form_Choices_2024_WEB.pdf

@imharryz The first verification stage is complete: the official domain for  Lancing College is www.lancingcollege.co.uk, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.lancingcollege.co.uk/lancing-society-ol-club/contact-us

@imharryz Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Title and menu location takes up too much vertical space

Testing #183532
This may not be related to TPI. But I noticed this since I was looking at menus and tabs more closely.
Actual (linux): (Title and Menu are on different lines)

IT looks right on windows:

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

This is because custom title is not enabled by default on Linux. I have suggested numerous times that we should really change the default.
//cc @sbatten


Fix "Pad" signatures with more honest nullable annotations

This PR adds to #803. Where a TSource is defaulted for padding, the signature now clearly says TSource?.

Idle curiosity on NRT handling: I wonder if passing a Func<int, T> will return an IEnumerable<T> or IEnumerable<T?>.

Will return based on whatever T is for the instantiation.

Looks good regardless

Almost. Had one the overloads wrong but hopefully fixed with 58ca7f95c771f762b68fea37ef689895a2506844.

Without the Defaultable<T>, it complains? Is it better to add the Defaultable<T> or to just ! it away? Seems like a lot of work to avoid a single character.

Without the Defaultable<T>, it complains?

Yes.

Is it better to add the Defaultable<T> or to just ! it away?

I'll admit I'm being sneaky with the compiler, but I am toying with the idea and wanted to throw it here to get reactions from reviewers so thank you for yours!

Seems like a lot of work to avoid a single character.

JIT should optimise Defaultable<T> away 100% so it should have zero runtime impact. Putting that technical detail aside, my goal here was not to save on the single character, but:

not having to default! at all every call site (usually less important).
making it obvious in the (always private) method signature that the argument may be defaulted due to mutual exclusion with some other argument.
quickly find all references of Defaultable<T> at some point in the future for code analysis.

While it might seem extreme for Pad, I am hoping it will help in other cases like FallbackIfEmpty. If it ends up being a bad or an over-the-top idea then one can find all references (3) and revert.


Add -d/--directory-only option.

Fixes #190, and:

Moves the decision about which metas to display out of the display module.
Re-uses or clones Meta structs when possible instead of using Meta::from_path which incurs a system call or two.
Avoids calling read_dir() twice for the same path.

I'm really happy to pair-review this live with someone, if that would help. It's a larger change than you might have expected for this feature, but I think/hope I can justify it :-) Some of the diff is change created by rustfmt – I can unwind that too if you would prefer.

Hey @allenap , sorry that it took a little while to review the PR.
Looks good to me, could you rebase it with the master branch?

Looks good to me, could you rebase it with the master branch?

@meain Rebased and pushed, with some additional updates from println! to eprintln!. Thanks!


Fix CodeCov

Description
What is the current behavior?
Currently, the codecov is broken since we have a mono repo since the base commit that is selected to compare the current commit can be from any sub-project. What we need is for the base commit to being chosen from the correct sub-project, this will give the correct code coverage to an individual sub-project.
What is the new behavior?
codecov has a feature of flags to handle the monorepo use case - Flags.
Does this introduce a breaking change?
Nope
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Didn't work, closing it.

@pankajkoti added complete description, please check.


feat: Hide sensitive attributes by default

(Note that most of this code is because a whole bunch of stuff has changed in Ash since migrations were last generated for the demo app, so it wanted to generate a new one and do a whole bunch of stuff. I just let it do its thing)
Adds a new SensitiveAttribute live component for rendering sensitive attributes on the index/show pages for a resource. Each live component tracks whether it has been viewed, and toggles between the following displays:
https://github.com/ash-project/ash_admin/assets/543859/e5be905f-6021-431a-87cc-b4800b92a3f9
The default slot for the SensitiveAttribute component is the revealed content, so it can be configured per-usage.
Closes #48

🚀 Thank you for your contribution! 🚀


The note title should be optional

blew md content cann't be convert to admonition html(because the note title is missing).
!!! note
    the note body.

But blew md can be convert to html good(note title is exist).
!!! note note title
    the note body.

@YukerZeng  resolved, thank you for your feedback


Update _proximity_forest.py Contribution

Removing some useless code and params for this contrib classifier

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

hi, changing this file has raised a world of docstring issues not addressed in previous docstring pushes. I completely understand if you don't want to address these, it is a thankless task. If you want to leave it, could you close this PR and I will sort out the docstrings? thanks. Tony


Full script for getting LEGO SSL certificate for rpxy

Thanks for making rust-rpxy. I am using rust-rpxy & it is working blazing fast with my self signed certificate.  Now I want to use actual ssl certificate through letenscrypt with the help of LEGO. As  rpxy use rust format key(PK8) & letenscrypt give key in PK1. It should be very good if some expert person make a bash file which combined the  LEGO commands for ssl certificate & convert key file into rust key format.  Basically i want to merge creation of key & converting into rust format in one script.
https://go-acme.github.io/lego/usage/cli/obtain-a-certificate/
if some expert make this type of bash script file then we can run that file periodically by Linux Cron job.
thanks

also want to add request like put if command so that the core work of renewal process only initiate  if time for renewal is within last 30 days of total 60days. meaning cron command may be run daily but request will go on 60th day for renewal & then overwrite the existing PK8 key file to new values.

<EMAIL_ADDRESS>\
CLOUDFLARE_API_KEY=XXXXXXXXXXXXXX \
lego --email<EMAIL_ADDRESS>--dns cloudflare --domains my.example.org run

% openssl pkcs8 -topk8 -nocrypt \
    -in yoru_domain_from_le.key \
    -inform PEM \
    -out your_domain_pkcs8.key.pem \
    -outform PEM% openssl pkcs8 -topk8 -nocrypt \
    -in yoru_domain_from_le.key \
    -inform PEM \
    -out your_domain_pkcs8.key.pem \
    -outform PEM

I am not stick with LEGO, i just need any working way to use SSL certificate & rust-rpxy in any script for using as mentioned in another post,
https://github.com/instant-labs/instant-acme?tab=readme-ov-file

I have copy paste few bash script from online media, please somebody fine tune it for rust-rpxy.  still it is broken.
#!/usr/bin/env bash

# Load the Hetzner API key
export HETZNER_API_KEY_FILE=/home/your_username/.lego/hetzer-api-key

<EMAIL_ADDRESS>LEGO_PATH="/home/your_username/.lego"
LEGO_CERTIFICATES_PATH="${LEGO_PATH}/certificates"
LEGO_RENEW_DAYS=10
LEGO_DNS_PROVIDER=hetzner

CERTIFICATE_RENEWED=False

for LEGO_CERTIFICATE_NAME in `/usr/bin/lego --path ${LEGO_PATH} list --names`
    do
        original=$(date -r "${LEGO_CERTIFICATES_PATH}/${LEGO_CERTIFICATE_NAME}.crt")

        /usr/bin/lego \
            --path ${LEGO_PATH} \
            --email ${LEGO_ACCOUNT_EMAIL} \
            --accept-tos \
            --dns ${LEGO_DNS_PROVIDER} \
            --domains ${LEGO_CERTIFICATE_NAME} \
            renew --days ${LEGO_RENEW_DAYS}

        actual=$(date -r "${LEGO_CERTIFICATES_PATH}/${LEGO_CERTIFICATE_NAME}.crt")

        if [ "${original}" != "${actual}" ]
            then
                CERTIFICATE_RENEWED=True
        fi
    done

if [ ${CERTIFICATE_RENEWED} == True ]
    then
        systemctl stop rpxy.service
        % openssl pkcs8 -topk8 -nocrypt \
          -in yoru_domain_from_le.key \
          -inform PEM \
          -out your_domain_pkcs8.key.pem \
          -outform PEM% openssl pkcs8 -topk8 -nocrypt \
          -in yoru_domain_from_le.key \
          -inform PEM \
          -out your_domain_pkcs8.key.pem \
          -outform PEM
        systemctl start rpxy.service
fi
exit $?

I made one bash file, it should be working, PK1 key creation default way & this bash file generate pk8 file if any change in pk1 & pk8 last modification date.
#!/bin/bash

pk1=$(date "+%Y/%m/%d" -r "/mnt/userdata/rpxy/certificates/_.XXX.ZZZ.key")
pk8=$(date "+%Y/%m/%d" -r "/mnt/userdata/rpxy/certificates/_.XXX.ZZZ.key.pem")
if ! diff -q <( printf $pk1 ) <( printf $pk8 )>/dev/null 2>&1
then
  echo "Different certificate, updating..."
  cd /mnt/userdata/rpxy/certificates
  openssl pkcs8 -topk8 -nocrypt \
      -in _.XXX.ZZZ.key \
      -inform PEM \
      -out _.XXX.ZZZ.key.pem \
      -outform PEM
   sudo systemctl restart rpxy.service
else
  echo "Same certificate, No change needed"
fi


Awesome Frontity page

https://github.com/sindresorhus/awesome
https://github.com/unicodeveloper/awesome-nextjs

It could be an external Github repository

This Issue is kind of solved with the "Resources" sections of the Community Forum


Add blacklist option to Ansible watches.yaml

With the addition of this feature, users will be able to prevent the
creation of watches for secondary resources by specifying a blacklist
of GVKs.
TODO:

Docs
Changelog
Audit log levels

@camilamacedo86, I originally planned to do what you suggested, but the blacklisted watches would be created anyway by the proxy as a side effect of owner reference injection and caching.


[BiliBili]unable to download from bilibili.com

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.03.03
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

 youtube-dl -v https://www.bilibili.com/video/BV1qb4y1X7ML
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://www.bilibili.com/video/BV1qb4y1X7ML']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.03.03
[debug] Python version 2.7.16 (CPython) - Darwin-20.3.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[BiliBili] 1qb4y1X7ML: Downloading webpage
[BiliBili] 1qb4y1X7ML: Downloading video info page
WARNING: Unable to download JSON metadata: HTTP Error 412: Precondition Failed
[BiliBili] 1qb4y1X7ML: Downloading video info page
ERROR: Unable to download JSON metadata: HTTP Error 412: Precondition Failed (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 632, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2275, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 435, in open
    response = meth(req, response)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 548, in http_response
    'http', request, response, code, msg, hdrs)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 473, in error
    return self._call_chain(*args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 556, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Description

youtube-dl is unable to download all bilibili.com video.

Duplicate of #28341

thank you. This issue is close.


feat: add kernel-bazzite to cache

Early draft PR for adding kernel-bazzite to kernel-cache. Waiting for Kyle to comment for it. Kind of untested.

really did not like that json passthrough. Switched to a tag and hardcoded the links

Should be optional and empty if unset, let me fix it.


Fix for negative values of ebi_v in assancao_rate smoother function

Hello! Please make sure to check all these boxes before submitting a Pull Request
(PR). Once you have checked the boxes, feel free to remove all text except the
justification in point 5.

[X] You have run tests on this submission, either by using Travis Continuous Integration testing testing or running nosetests on your changes?
[X] This pull request is directed to the pysal/dev branch.
[X] This pull introduces new functionality covered by
docstrings and
unittests?
[ ] You have assigned a
reviewer and added relevant labels
[X] The justification for this PR is: According to #909, the Assuncao rate smoother function does not work correctly for negative values of ebi_v. This PR implements a fix suggested in the issue, by setting ebi_v = ebi_b / b for negative values of ebi_v instead of ebi_a + ebi_b/ b.

@ljwolf @darribas , I checked the build, and the checks are failing because I am supposed to use ebi_v.any() or ebi_v.all() while checking if ebi_v is less than 0, because I'd need to check an array of booleans. Which of these am I supposed to use, or do I need to change my approach to the problem?

According to the issue you refer to, it needs to be done on an element-by-element basis. I'd use a boolean masked assignment.
Also, I'm not read up on this particular issue, so possibly referring to the paper would clear up the suggestion in #909.

Coverage increased (+0.005%) to 83.061% when pulling c76092190128b5db2edeb4796a91c621b6c68460 on Omarkhursheed:Err909 into fa1e8116dabdbbcfb33e31ce5aa9cbf330a91569 on pysal:dev.


[GLUTEN-1457][CH] A uniform api to generate output schema for a specified plan node

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: #1457
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
unit tests
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Run Gluten Clickhouse CI

cc @rui-mo @zzcclp will you review this pr?

could not reproduce the problem in https://github.com/oap-project/gluten/pull/1456 after this

@baibaichen Do you have time to review this ?

Overriding the output will break the reused exchange node.


Error in Downloading Packages: Multiple packages link to with SDL2

Got this error when trying to cargo run --release
error: multiple packages link to native library SDL2, but a native library can be linked only once
package sdl2-sys v0.31.0
... which is depended on by sdl2 v0.31.0
... which is depended on by gfx_window_sdl v0.8.0
... which is depended on by ggez v0.4.4
... which is depended on by solitaire v0.2.0 (/home/pintert3/solitaire-0.2.0)
links to native library SDL2
package sdl2-sys v0.34.3
... which is depended on by sdl2 v0.34.3
... which is depended on by solitaire v0.2.0 (/home/pintert3/solitaire-0.2.0)
also links to native library SDL2

Thank you for reporting this issue!
It will take me a few days to look into this.
Meanwhile, can you let me know which version of Cargo you are using?

This should be fixed by updating to ggez 5.0, which no longer depends on SDL.
Could you please try if the ggez-5 branch works for you?

That fixed it. It now works fine, thanks!
And just in case it matters, I'm using cargo 1.46.0

Perfect. Thank you for the help!


[BUG]Connect-PnPOnline has a memory leak

Expected behavior
I should be able to run Connect-PnPOnline thousands of times in a row for different SPO URLs without a System.OutOfMemoryException.
Actual behavior
After about 900 to 1,000 times of calling Connect-PnPOnline, I get a System.OutOfMemoryException.
Steps to reproduce behavior
-Create a loop that iterates through 1,000+ valid SPO URLs. (You may be able to cycle through repeat URLs if you don't have 1,000)
-Connect-PnpOnline to each one of the URLs. For me, I am using certificatePath -ClientId -CertificatePassword along with -Tenant and -Url properties.
-Your loop doesn't have to do anything else, but connect. I also tried using Disconnect-PnPOnline afterwards with no luck. Based off of this article (https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/disconnect-pnponline?view=sharepoint-ps), that shouldn't be needed anyway.
What is the version of the Cmdlet module you are running?
1.7.0
Which operating system/environment are you running PnP PowerShell on?

[ ] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[X] Azure Functions
[ ] Other : please specify

Hi @Ambergahill - can you please try with the latest PnP PowerShell 1.8.0 ? There were some auth related changes , maybe it can help you.

@Ambergahill - Please try with the latest version 1.9.0 and reopen if the issue persists.

I'm still seing this with pnp version 1.9.0  running standard mcr powershell linux container  (psh v7.2.1  / Linux 5.4.81-microsoft-standard #1 SMP )  looping through sharepoint sites only using connect-pnponline with a certificate as credential.

Thank you @gbordier. I am also still seeing the issue in 1.9.0. @veronicageek , please reopen the the issue.

simple repro without even changing the URL (does not repro on windows)
$cert=@"
MIIJ ------ Base64 encoded Pfx Content Here -------- EtNO
"@
$tenant="xxxx"
$AppID="AppID for AAD app with PNP rigts"
new-object System.Security.Cryptography.X509Certificates.X509Certificate2 -ArgumentList @([System.Convert]::FromBase64String( $cert),"")
for($i=0;$i -lt 100000 ; $i++) {
Connect-PnPOnline -Url "https://$tenant-admin.sharepoint.com"  -CertificateBase64Encoded $s -ClientId $AppID -Tenant $tenant.onmicrosoft.com
if ($i % 1000 -eq 0) {
write-host $i
}
}

Looks like the issue might be in the Authentication Manager . I get the same mem usage and eventually OOM (especially VIRT growing up to 64GB) I have repro this with certificate, secret and accesstoken . I have dumps to share if usefull

looks like I can narrow this down to the Telemetry part.
Telemetry does not get disabled only with PNPPOWERSHELL_DISABLETELEMETRY=true because of a logic bug in InitializeTelemetry (we need the .pnppowershelltelemetry in the users home folder present and empty  to really disable telemetry)
I'll be submiting a PR for this.
the leak seems to be in the Telemetry activation code I'll try to narrow it further down.

@veronicageek  can someone have a look on the InitializeTelemetry method, should the ApplicationInsights member be static to avoid creating one for each connect-pnponline command issued ?

I'll tag @gautamdsheth and @KoenZomers if they have any insights

it looks like it is a known issue with TelemetryClient that it should be implemented as a singleton, but I would welcome insights before submitting such a change : ) ref : https://briancaos.wordpress.com/2020/05/07/c-azure-telemetryclient-will-leak-memory-if-not-implemented-as-a-singleton/

@gbordier  - thanks for looking into this. Looks like you are right, could you please submit a PR, we can check the implementation, much appreciated :)

Closing this issue as the PR has been merged.  You can get it via the latest nightly builds.
Feel free to submit a separate PR to improve the app insights TelemetryClient.
Thanks again @gbordier   for investigation and submitting the PR, much appreciated 🙏😊

the merged PR was about help disabling telemetry with the env variable but not implementing the singleton pattern for TelemetryClient I believe. I would keep this one open for now.

Yeah go ahead

Sure, go for it. Please ensure that your dev fork is up to date with our dev fork as I submitted changes to that same code yesterday. Otherwise we might end in in a code merge disaster.


Refactor TestRunner: move jobID/runID/testAttempt from TestRunner

Fix: https://github.com/linuxboot/contest/issues/40

Codecov Report

Merging #45 (b4c849d) into main (4de747d) will decrease coverage by 1.44%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
- Coverage   66.27%   64.82%   -1.45%
==========================================
  Files         155      150       -5
  Lines        9274     8708     -566
==========================================
- Hits         6146     5645     -501
- Misses       2476     2479       +3
+ Partials      652      584      -68

Flag
Coverage Δ

e2e
?

integration
57.43% <100.00%> (+0.04%)
:arrow_up:

unittests
47.19% <100.00%> (+0.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/runner/job_runner.go
78.83% <100.00%> (+2.06%)
:arrow_up:

pkg/runner/test_runner.go
89.09% <100.00%> (-3.55%)
:arrow_down:

pkg/xcontext/logger/log_level.go
0.00% <0.00%> (-100.00%)
:arrow_down:

plugins/reporters/noop/noop.go
12.50% <0.00%> (-87.50%)
:arrow_down:

plugins/teststeps/sleep/sleep.go
4.08% <0.00%> (-69.39%)
:arrow_down:

pkg/config/jobdescriptor.go
0.00% <0.00%> (-53.34%)
:arrow_down:

pkg/transport/http/http.go
0.00% <0.00%> (-50.48%)
:arrow_down:

pkg/jobmanager/options.go
68.42% <0.00%> (-31.58%)
:arrow_down:

tests/common/get_events.go
56.66% <0.00%> (-20.00%)
:arrow_down:

plugins/storage/rdbms/report.go
51.48% <0.00%> (-16.84%)
:arrow_down:

... and 16 more

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 4de747d...b4c849d. Read the comment docs.

Rebase and also refactored some unit tests to get rid of global storage variable

accepting but there's still an open question above

Merged PR is it doesn't contain destructive changes.
Remaining open question will fix in a separate PR


Clean up magika assets managment

Currently, models and other assets such as KB lives in the python/magika/models dir, with the rust (and js?) codebases pulling things from there. This is not ideal as we may want to decouple the various codebases (and we may want to upgrade one model for python at a different time than for rust). Also, we often work with .onnx format, but for some other stuff we may want the .h5 or the tfjs version... I could store them all in python/magika/models, but they don't belong there... at the moment, whatever is in python/magika/ gets packaged with the pip package, which is not good.
My proposal: I update my code from the training side of things / internal repo to export assets (models + content types KB + whatever else) somewhere like <root_github_repo_dir>/assets/*. Then, the various codebases (python, rust, go, js, etc.) can pick from that folder whatever they want/need (in an automated or manual fashion).
Thoughts?
CC @invernizzi @ia0

I also think this is a better design. So all green on my side to proceed. Once you do the base layout, I can update the Rust side of things. Just ping me on the PR.

#643 stores assets in assets/, which is the first step. Then, we need to clean up the assets_generation/ script.

Closing this one as we actually cleaned up /assets. Opened #684 to track what we need to clean about /assets_generation.


 Unfortunately there isn't a modern, secure browser available. Every one I've tried including Thorium complain they're not compatible with Mac OS El Capitan 10.11.6 which is  the most modern MacOS that runs on this old lady.
Currently I'm running old unsupported Safari and Firefox. Old Chrome based browsers won't even load.
Any hope for Thorium to become retro?

Not directly related to Thorium, but the Chromium-Legacy Project backports up-to-date Chromium to Mac OS X 10.7-macOS 10.12: https://github.com/blueboxd/chromium-legacy

@panabike @Jazzzny Yeah, this is not something I'm gonna do because it requires extensive reworking of Chromium. I would try what @Jazzzny said if you wanna run chromium on old macos versions.


[Diffusers] Regression of CPU memory usage

Issue
We were able to run SDXL artifacts compiled with inf2.8xlarge on inf2.xLarge (as stated in the blog). However, we recently found that SDXL's CPU memory usage increased, leading to OOM during the inference on inf2.xlarge. In this issue, we will note down some experiment results to trace where the regression was introduced.
Tasks

[ ] Latest Optimum Neuron (0.0.26) on Neuron SDK 2.15.0
[ ] Other Neuron SDK versions
[ ] Pytorch version 1.13.1 v.s 2.1?

Reproduction (minimal, reproducible, runnable)
optimum-cli export neuron --model stabilityai/stable-diffusion-xl-base-1.0  --batch_size 1 --height 1024 --width 1024 --num_images_per_prompt 4 --auto_cast matmul --auto_cast_type bf16 sd_neuron_xl/

Expected behavior
Being able to fit into inf2.xlarge after being compiled with inf2.8xlarge.

Experiment 2: Neuron sdk 2.16.1 + Optimum Neuron 0.0.18

Compiled artifacts
Inference failed with

Experiment 2: Neuron sdk 2.16.1 + Optimum Neuron 0.0.13

Compiled artifacts: https://huggingface.co/Jingya/sdxl_on_0.0.13_neuron_2.16.1/tree/main
Inference: succeeded
-> the regression was introduced between Optimum Neuron 0.0.13 - 0.0.18

Optimum Neuron v0.0.14 + Neuron SDK 2.16.1 ✔

Optimum Neuron v0.0.15 + Neuron SDK 2.16.1 👎
Jingya/sd_neuron_xl_2.16.1_0.0.15
Loading only U-Net into both Neuron Cores...
Killed

The regression shall has been introduced between v0.0.14 -> v0.0.15

The regression comes from the change of order in loading submodels, we need to load the unet first otherwise we get CPU OOM when loading the UNet if other models(VAE, text encoders) are already loaded.
This regression was already corrected during the diffusion pipeline refactoring: #711 and included since Optimum Neuron v0.0.26 release. Besides, a PR is opened to enhance the loading order: #742.
Close this issue as solved.


Soft lock when selecting ignore on the kit preset equip screen

General information:
Project issue is for:
3.8.0 BE
Expected result:
I'm not sure. I haven't used the kit preset in live
Actual result:
Soft freeze. No buttons work except for the messages button
If you don't have all the items for a kit preset and you hit ignore on the equip screen you get soft locked
How to reproduce:

try to load a kit preset that you don't have everything for
click equip button
select ingore on the parts screen that pops up

Log files:
Server: https://codepaste.sp-tarkov.com/?fbbe6e671c4a4715#9vKQirq6AKFq8wfYAv8EBUqG4LRoqv376apVCkHyRsKx
BepinEx: https://codepaste.sp-tarkov.com/?510c6cd5d2769e88#4ZbniYebEToKFujiDtoQR7kjs4nDuD1YggQRMDyvG61i
Client: https://codepaste.sp-tarkov.com/?ddef421e6e5ce9ee#4QekoHLbYbphFxeRz6H6rF9UNs6DxN1y1PVVABmkhCFy
Profile:
https://codepaste.sp-tarkov.com/?1af76040764602e3#7GUUPpbswsMKcdvdkXjGrRLoXaBq9JrwErKTWfWtyyyU
Screenshots:
(Optional, only add them if you think it adds value)

Originally written by Burgunfaust

Was able to replicate this with profile provided and one self made.
From what ive been able to see its something to do with having ammo in the chamber of the saved loadout.
Seems to softlock before even talking to the server. maybe a BSG Bug?

Originally written by Kaeno

Attaching profile as the codepaste expires tomorrow

Attachments

65c557450002fb34f9852310.zip (110 KiB)

Originally written by DrakiaXYZ


VideoCapture{0}

I need to use this VideoCapture. I am using  cap = cv.VideoCapture{0}
I am getting this error.
...e/kushal/torch/install/share/lua/5.2/cv/videoio/init.lua:52:`` NYI: call return type stack traceback: 	/home/kushal/torch/install/share/lua/5.2/trepl/init.lua:506: in function </home/kushal/torch/install/share/lua/5.2/trepl/init.lua:499> 	[C]: in function '__index' 	...e/kushal/torch/install/share/lua/5.2/cv/videoio/init.lua:52: in function '__init' 	/home/kushal/torch/install/share/lua/5.2/torch/init.lua:91: in function </home/kushal/torch/install/share/lua/5.2/torch/init.lua:87> 	[C]: in function 'VideoCapture' 	[string "local cap = cv.VideoCapture{0}"]:1: in main chunk 	[C]: in function 'xpcall' 	/home/kushal/torch/install/share/lua/5.2/trepl/init.lua:679: in function 'repl' 	...shal/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:204: in main chunk 	[C]: in ?
I am able to use cv2.VideoCapture(0) in python and its working fine. Is there any way to solve this?

Hi. This can happen if you compile Torch with Lua 5.x instead of LuaJIT. See #123, #143, #189.


[Question]: Can I deploy RagFlow without Docker in an environment that is already a Docker container?

Describe your problem
I’m using a cloud service where my machine is essentially a Docker container itself, making it difficult to spin up another Docker container inside it. The official RagFlow instructions rely on Docker Compose. What are my options for deploying RagFlow without Docker, or are there best practices for running Docker within Docker in this scenario?

This might help.


Fails while running prepdocs.py from Azure Cloud Shell

Please provide us with the following information:

This issue is for a: (mark with an 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
Run azd up command. It will provision all required services; however it will fail while running prepdocs.py consistently.
Any log messages given by the failure
Running "prepdocs.py"
AzureDeveloperCliCredential.get_token failed: {"type":"consoleMessage","timestamp":"2023-09-13T18:17:14.557034123Z","data":{"message":"fetching token: invalid CloudShell token API response code: 400, content: {"error":{"code":"AudienceNotSupported","message":"Audience https://cognitiveservices.azure.com is not a supported MSI token audience. Supported audiences: https://management.core.windows.net/,https://management.azure.com/,https://graph.windows.net/,https://vault.azure.net,https://datalake.azure.net/,https://outlook.office365.com/,https://graph.microsoft.com/,https://batch.core.windows.net/,https://analysis.windows.net/powerbi/api,https://storage.azure.com/,https://rest.media.azure.net,https://api.loganalytics.io,https://ossrdbms-aad.database.windows.net,https://www.yammer.com,https://digitaltwins.azure.net,0b07f429-9f4b-4714-9392-cc5e8e80c8b0,822c8694-ad95-4735-9c55-256f7db2f9b4,https://dev.azuresynapse.net,https://database.windows.net,https://quantum.microsoft.com,https://iothubs.azure.net,2ff814a6-3304-4ab8-85cb-cd0e6f879c1d,https://azuredatabricks.net/,ce34e7e5-485f-4d76-964f-b3d2b16d1e4f,https://azure-devices-provisioning.net,https://managedhsm.azure.net,499b84ac-1321-427f-aa17-267ca6975798,https://api.adu.microsoft.com/,https://purview.azure.net/,6dae42f8-4368-4678-94ff-3960e28e3630"}}\n"}}
Traceback (most recent call last):
File "/home/linesh/azure-search-openai-demo/scripts/.venv/lib/python3.9/site-packages/azure/identity/_credentials/azd_cli.py", line 191, in _run_command
return subprocess.check_output(args, **kwargs)
File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/bin/sh', '-c', 'azd auth token --output json --scope https://cognitiveservices.azure.com/.default --tenant-id 16b3c013-d300-468d-ac64-7eda0820b6d3']' returned non-zero exit status 1.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/linesh/azure-search-openai-demo/./scripts/prepdocs.py", line 385, in
openai.api_key = azd_credential.get_token("https://cognitiveservices.azure.com/.default").token
File "/home/linesh/azure-search-openai-demo/scripts/.venv/lib/python3.9/site-packages/azure/identity/_internal/decorators.py", line 32, in wrapper
token = fn(*args, **kwargs)
File "/home/linesh/azure-search-openai-demo/scripts/.venv/lib/python3.9/site-packages/azure/identity/_credentials/azd_cli.py", line 122, in get_token
output = _run_command(command, self._process_timeout)
File "/home/linesh/azure-search-openai-demo/scripts/.venv/lib/python3.9/site-packages/azure/identity/_credentials/azd_cli.py", line 205, in _run_command
raise ClientAuthenticationError(message=message)
azure.core.exceptions.ClientAuthenticationError: {"type":"consoleMessage","timestamp":"2023-09-13T18:17:14.557034123Z","data":{"message":"fetching token: invalid CloudShell token API response code: 400, content: {"error":{"code":"AudienceNotSupported","message":"Audience https://cognitiveservices.azure.com is not a supported MSI token audience. Supported audiences: https://management.core.windows.net/,https://management.azure.com/,https://graph.windows.net/,https://vault.azure.net,https://datalake.azure.net/,https://outlook.office365.com/,https://graph.microsoft.com/,https://batch.core.windows.net/,https://analysis.windows.net/powerbi/api,https://storage.azure.com/,https://rest.media.azure.net,https://api.loganalytics.io,https://ossrdbms-aad.database.windows.net,https://www.yammer.com,https://digitaltwins.azure.net,0b07f429-9f4b-4714-9392-cc5e8e80c8b0,822c8694-ad95-4735-9c55-256f7db2f9b4,https://dev.azuresynapse.net,https://database.windows.net,https://quantum.microsoft.com,https://iothubs.azure.net,2ff814a6-3304-4ab8-85cb-cd0e6f879c1d,https://azuredatabricks.net/,ce34e7e5-485f-4d76-964f-b3d2b16d1e4f,https://azure-devices-provisioning.net,https://managedhsm.azure.net,499b84ac-1321-427f-aa17-267ca6975798,https://api.adu.microsoft.com/,https://purview.azure.net/,6dae42f8-4368-4678-94ff-3960e28e3630"}}\n"}}
ERROR: failed running post hooks: 'postprovision' hook failed with exit code: '1', Path: './scripts/prepdocs.sh'. : exit code: 1
Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

related to: https://github.com/Azure/azure-dev/issues/2410#issuecomment-1595336078

Thanks for filing, @lineshgajerams. I'm able to reproduce this locally and we think this behavior is happening in Cloud Shell.
One can use azd itself to get the same error output:
azd auth token --output json --scope https://cognitiveservices.azure.com

Which works out to a request to fetch an access token using the Cloud Shell metadata API. The minimal repro is:
curl http://localhost:50342/oauth2/token --data "resource=https://cognitiveservices.azure.com" -H Metadata:true -s

I'm in communication with the Cloud Shell team about this to find a way forward.
I'm also checking on some possible workarounds.

@lineshgajerams -- I also have a workaround that you can use in the short term while we dig in on the issue with Cloud Shell:
In this case, use device-code authentication:
azd auth login --use-device-code

The azd up command will succeed end to end.

@danieljurek Thank you for the work around. I will try today and see if it works from Azure Cloud Shell. I already have a customer engagement to enable Azure Cognitive Seach with OpenAI integration and I want to use this accelerator. I have been doing hands on to make sure It works in customer subscription

@danieljurek
After successfully completed the login with device code, getting following error. I replaced my subscription with *****
Cloud Shell is automatically authenticated under the initial account used to sign in. Run 'azd auth login' only if you need to use a different account.
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code EJVYJ8N5G to authenticate.
Device code authentication completed.
Logged in to Azure.
PS /home/linesh/azure-search-openai-demo> azd up
(✓) Done: Retrieving locations...
ERROR: listing locations: failed retrieving Azure location for account '': failed to resolve user access to subscription with ID '***'. If you recently gained access to this subscription, run azd auth login again to reload subscriptions.
Otherwise, visit this subscription in Azure Portal using the browser, then run azd auth login

Do we have any workaround for this?


Rate limit + lots of pull requests == inaccessible Jenkins

I saw a failure yesterday where the Jenkins HTTP interface became inaccessible.  What appears to have happened is that a thread hit the GIthub rate limit while handling the pull request hook.  This caused a sleep timer to fire in the call stack and the thread waited around.  While that was waiting, more requests came in (some from the same PR, some from others) and also hit the rate limit.  Each thread blocked and then HTTP handler queue filled up and the whole thing ground to a halt.

"Handling POST /ghprbhook/ from <IP_ADDRESS> : RequestHandlerThread[#1109]" daemon prio=10 tid=0x00007fe200393800 nid=0x5c92 waiting on condition [0x00007fe1591cd000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.kohsuke.github.RateLimitHandler$1.onError(RateLimitHandler.java:38)
at org.kohsuke.github.Requester.handleApiError(Requester.java:518)
at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:418)
at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:389)
at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44)
at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32)
at org.kohsuke.github.PagedIterable.asList(PagedIterable.java:42)
at org.kohsuke.github.GHIssue.getComments(GHIssue.java:200)
at org.jenkinsci.plugins.ghprb.GhprbPullRequest.checkComments(GhprbPullRequest.java:395)
at org.jenkinsci.plugins.ghprb.GhprbPullRequest.updatePR(GhprbPullRequest.java:215)
at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:155)

I am working on a fix, where once we decide to keep the event and send it to the triggers we start a new thread.  I am having issues getting it to work at the moment though, but I will work on it some more tonight.

One way to work around this, btw, is to increase the number of handler threads so that it's less likely to clog up the HTTP queue. The default is pretty low (I think it's 32)


Bad serialization of anti-slash in regexps with /.../ syntax

Using version 1.2.0
import jsonpath

jp = jsonpath.compile(r"$[?@ =~ /\d/]")
assert jp.findall(["", "1", "10"]) == ["1"]  # OK

assert str(jp) == r"$[?@ =~ /\d/]"  # NOK: "\d" --> "d"

jp_from_str = jsonpath.compile(str(jp))
assert jp.findall(["", "1", "10"]) == ["1"]  # NOK

Note that behavior is OK with r"$[?match(@, '\\d')]" (but anti-slash needs to be escaped).

Thank you, @emaheuxPEREN, for reporting this issue.
Should be fixed in version 1.2.1. Now released.


white blank space between feed and sidebar on ubuntu

on discovery, the main feed and even the login screen there's a big white space on the left hand side.
i uploaded to imgur a image of it:

i'm using xfce on ubuntu 16.04

Duplicate of #125


Fix #91

Fixes #91 by appending to queues only if the environment variable is not empty.

Ooops! Thanks for the fix! 🙇🏼♂


Monitor the app - steps different for Amazon Linux 2 instance?

The command sudo systemctl enable ... yields 'systemctl command not found'.
The instructions want the new .service file under the /etc/systemd/... directory, but this directory doesn't exist on my ec2 instance (Amazon Linux 2).  Should I simply create it?  Or am I missing core software that I need to install first?

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

ID: cfd9a1f0-c1b6-4443-0700-4c5beafeed03
Version Independent ID: c22ca7a0-d1d4-200d-fc36-a9798d350c6e
Content: Host ASP.NET Core on Linux with Apache
Content Source: aspnetcore/host-and-deploy/linux-apache.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @guardrex
Microsoft Alias: shboyer

They advertise it prominently ...

Amazon Linux 2 includes the widely adopted systemd init system which is used to bootstrap the user space as well as manage system processes.

Seems like a configuration issue on the distro-side. Given how 🏃😵 the engineers are getting 3.0 out, we can't ping them at this time. Ask on a support forum, such as Stack Overflow, or a support chat, such as Slack or Gitter.

ASP.NET Core Slack Team (self-signup) - not official
ASP.NET Gitter - official


python310Packages.aioambient: 2021.12.0 -> 2022.10.0

Description of changes
https://github.com/bachya/aioambient/releases/tag/2022.10.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 198559 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.ambient_station
python310Packages.aioambient
python39Packages.aioambient


📝 Add-Quote: one quote from @sanju2728

Description

Additional context

What is the purpose of this pull request?

[x] Add quotes
[ ] Bug fix
[ ] New Feature
[ ] Add more tests
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123 or closes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thank you for fixing it lol
On Mon, 3 Oct, 2022, 10:07 pm Anil Seervi, @.***> wrote:

@.**** approved this pull request.
Thanks for contributing to this project @sanju2728
https://github.com/sanju2728
Happy hacktoberfest! 🎉
—
Reply to this email directly, view it on GitHub
https://github.com/AnilSeervi/inspirational-quotes/pull/12#pullrequestreview-1128701166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXW5UWLTFZSL2DBYYD3NFW3WBMDUPANCNFSM6AAAAAAQ3Q42YI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for fixing it lol
…

No Problem.
And congrats on your first PR.🎉


Edited iPhone screenshots are not grouped properly

When importing an iPhone screenshot consisting of IMG_1234.PNG, IMG_1234.AAE, and IMG_E1234.jpeg, osxphotos decides that the AAE file is not an Apple Photos file and ungroups the files. The root cause is that the screenshot editor sets the AAE file's "adjustmentFormatIdentifier" to "ScreenshotServices".
Here is an example: IMG_6743.zip

@all-contributors please add @arthurward for bug

Thanks for the test data. Will work to get this incorporated when I have time. This should be an easy fix. The check for import is done in a single function that can be modified:
https://github.com/RhetTbull/osxphotos/blob/23e3c995f81eb849f69dc241b6c1d0486f599334/osxphotos/image_file_utils.py#L118-L123


[Feature Request] Add measurement tracking in all 3 viewports of MPR

What feature or change would you like to see made?

Be able to track measurements in the sagittal viewport in MPR mode.
Be able tot rack measurements in the coronal viewport in MPR mode.

Why should we prioritize this feature?
This would allow more flexibility to take measurements and then export those measurements so they can be used by medical teams to design surgical devices. The goal is also to eventually be able to track measurements in oblique views of a study.
I can implement the feature but I'd need some guidance to approximately learn what files/classes to modify.

Second this

when we say tracking we mean you can export it. In MPR we only have support for SR export for acquisition, although user can draw on others, i think we should show them as untracked in the panel

Non-tracked annotations (on reconstruction views) should be rendered in the additional findings section. The JSON download should export them, but the DICOM SR should not include them.

We released OHIF 3.9 which address this issue


Exit Codes for VM

Ensure that our exit codes match Lotus

Low priority for now, but will get back to this when focusing on interop.


[Feature Request] add icon highlight support

Reference the vim-clap. Maybe it's better for telescope. that we should have add icon highlight support.

I think I have added in a8e7807


[Question]: My Question is how do i fix this?

What is your question?

More Details
whenever i try to use it, it gives me this error and how do i get the assistant api key?

What is the main subject of your question?
No response
Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

looks like you might need to add more credit into your account:
https://platform.openai.com/account/billing/overview


consider allowing to specify parameters for a test case as a dictionary

could be nice for testing functions with a higher number of parameters

will do this. it's going to depend on what the adapter module is capable of. will need to have separate cases for whether user has passed in an iterable or a dict for parameters, and use * or ** accordingly to pass the params to the function itself

will be implemented along with #8


Option to turn off snippets

A feature request.
It would be really cool to have an option to turn off snippets built into extension. They always get into my way, and modifying "csharp.json" file in "Snippets" folder of the extension is only working until VSCode relaunch (then extension files regenerate).
I don't know if it's possible to do though.

Does modifying "editor.snippetSuggestions" setting works for you?

Unfortunately, it doesn't. I have a few of my own snippets that I do want to see "inline"-d, but C# extension's snippets get in the way.

@Taugeshtu I'm not sure this is something we can address from the C# extension. The extension model requires us to declare our snippets file in our package.json (https://code.visualstudio.com/docs/extensions/themes-snippets-colorizers#_add-to-your-language-support-extension) which causes VS Code to always load them. I would recommend refiling this issue against https://github.com/Microsoft/vscode.
I'm going to close this issue but feel free to add further comments if you think there's something we can do on our side. Thanks!


Fix travis tests errors partially

With this in, we at least can execute more tests on travis unti the CI fails.
It fails at the protocol.Proxy tests, which fail for a reason. I doubt that we have finished the work on that class.

Merging this without review, as it is at least a step in the right direction.


Migrate mnist dataset from np.frombuffer

Accordingly to pytorch/pytorch#59077 this PR migrates from np.frombuffer to pytorch.frombuffer and closes #4552
This PR is closing the last piece with mnist dataset.
So far I tested all mnist tests:

cc @pmeier @datumbox

Thanks for the PR @lc0!
This looks like a good improvement to me but I'll let @pmeier to make the last call as he knows the datasets domain much better than me. Note that the linter is currently failing, could you please fix?

good point, somehow on the first format run - I've got a lot of changes. Seems like after rebasing it's all good now. So sorry for the inconvenience 🙈

Could you test this against the original data? IIRC, there was something about the byte order, which is why I implemented the same in the new prototype like this:
https://github.com/pytorch/vision/blob/c790216ad47fb379b2a158fe8e3602865b26e09f/torchvision/prototype/datasets/_builtin/mnist.py#L79
If this works with torch.frombuffer I'm all in favor of removing the  numpy dependency. I'm on PTO right now, so it will take me some time to test this properly.

@pmeier We are happy to wait until you are back from PTO to allow for more thorough tests. Would you mind marking this with "Request changes" so that it's not accidentally merged?

It seems to work just fine, but if we use it, we are getting an "old" warning back:
UserWarning: The given buffer is not writable, and PyTorch does not support non-writable tensors. This means you can write to the underlying (supposedly non-writable) buffer using the tensor. You may want to copy the buffer to protect its data or make it writable before converting it to a tensor. This type of warning will be suppressed for the rest of this program. (Triggered internally at  ../torch/csrc/autograd/python_torch_functions_manual.cpp:489.)
  parsed = torch.frombuffer(data, dtype=torch_type, offset=(4 * (nd + 1)))

This was only removed only recently in #4184. Maybe we can send a patch upstream to fix it, but the warning seems justified to me.

According to the docs of torch.frombuffer:

The returned tensor and buffer share the same memory. Modifications to
the tensor will be reflected in the buffer and vice versa. The returned
tensor is not resizable

so I'm not sure we can avoid the warning if we switch to torch.frombuffer, unless we copy the buffer beforehand.
I would suggest to either:

if we really want to use torch.frombuffer, just silence the warning by wrapping the call in a context manager. For this specific buffer, I really doubt the "writeable tensor on a read-only buffer" will ever cause a problem (FWIW, we used to ignore the warning before we started making a copy in  #4184)
not care about all this and keep the code as-is (i.e. not merge this PR). The code-quality improvement is pretty marginal anyway.

@pmeier Apologies, I misread the previous comment. TBH I would prefer to merge the PR because it removes the extra code of juggling between numpy and pytorch. Concerning fixing the warning, we could either call clone() or suppress it. Copying doesn't sound too bad given the dataset is tiny and can avoid issues with in-place modifications. It will also align the behaviour with #4578 but no strong opinions.

Concerning fixing the warning, we could either call clone() or suppress it.

Sorry to be pedantic here, but we need to suppress and clone. torch.frombuffer emits the warning unconditionally. After we loaded the buffer we can then clone to avoid problems with inplace modifications. For example:
with suppress_read_only_warning():
    data = torch.from_buffer(buffer, dtype=dtype).clone()

This issues did not arise before, because numpy can either deal with read-only buffers or simply doesn't warn you about it.

I might be missing something here but why can't we copy the buffer and make it mutable?
Something like the following should work because the bytearray:
parsed = torch.frombuffer(bytearray(data), dtype=torch_type, offset=(4 * (nd + 1)))

We do copy but we don't have to suppress warnings etc.

I like torch.from_buffer(bytearray(buffer), dtype=dtype) best, because it is quite concise and we avoid to write extra functionality to suppress a warning that we can't control directly. Thanks @datumbox for the suggestion.

Hi @pmeier it's a good point. It feels that we are maintaining two implementations of dataset API. Does it make sense somehow abstract it away and do not implement/maintain it twice? :)
Also, if this is broken currently, I guess it's subtle enough to be useful enough to cover with a test. What do you think?