Add device filter conditions for application scheduling and service states.

These two conditions function like any other condition:
type Condition struct {
	Type   ConditionType          `json:"type"`
	Params map[string]interface{} `json:"params"`
}

Querying by application existence
To get devices based on whether an application is running on them, use:
const ApplicationExistenceCondition = ConditionType("ApplicationExistenceCondition")
type ApplicationExistenceConditionParams struct {
	ApplicationID string   `json:"applicationId"`
	Operator      Operator `json:"operator"`
}

Where operator is either:
OperatorExists    = Operator("exists")
OperatorNotExists = Operator("does not exist")

An example query using this condition is:
"[{\"type\":\"ApplicationExistenceCondition\",\"params\":{\"operator\":\"exists\",\"applicationId\":\"app_1YJdqxzJW0kxuNqYiqiKE54gou3\"}}]"

Querying by service state
To get devices based on whether a service has a given state, use:
const ServiceStateCondition         = ConditionType("ServiceStateCondition")
type ServiceStateConditionParams struct {
	ApplicationID string       `json:"applicationId"`
	Service       string       `json:"service"`
	Operator      Operator     `json:"operator"`
	ServiceState  ServiceState `json:"serviceState"`
}

Where operator is either:
OperatorIs    = Operator("is")
OperatorIsNot = Operator("is not")

And service state (also in pkg/models) is one of:
const (
	ServiceStateUnknown                   ServiceState = "unknown"
	ServiceStatePullingImage              ServiceState = "pulling image"
	ServiceStateCreatingContainer         ServiceState = "creating container"
	ServiceStateStoppingPreviousContainer ServiceState = "stopping previous container"
	ServiceStateRemovingPreviousContainer ServiceState = "removing previous container"
	ServiceStateStartingContainer         ServiceState = "starting container"
	ServiceStateRunning                   ServiceState = "running"
	ServiceStateExited                    ServiceState = "exited"
)

An example query using this condition is:
"[{\"type\":\"ServiceStateCondition\",\"params\":{\"operator\":\"is not\",\"service\":\"demo-go\",\"serviceState\":\"running\",\"applicationID\":\"app_1YJdqxzJW0kxuNqYiqiKE54gou3\"}}]"

Application existence isn't too different from the filters we have for scheduling rules.
Maybe "ApplicationStatusCondition" is what we want? It would have an argument for release number, and then operators equals / not equals.
This could power this part of the UI. Imagine "show devices not running this release" / "show devices running this release".

Everything about service state conditions seems spot on!


Fix: Reword unempathetic sentence

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #17579.
Description

Thanks for the PR @Vimal-Raghubir
Personally, I don't think this change reads naturally in English.
IMO I would change it from accessible to the people who are deaf to accessible to people who are deaf (i.e. removing the word the ).

:+1: :+1: Awesome! Everything LGTM :+1: :+1:
Thank you for your PR to fix this issue, @Vimal-Raghubir. We look forward to your next contribution.


Support setting the security context for MinIO and Milvus components

For security reasons, we use Kyverno's admission controller on our cluster to ensure that certain Linux capabilities are dropped and that containers run as non-root, along with other policies. While we can change the security contexts of the components using the Bitnami Helm charts (etcd, Kafka, etc.)  we are unable to do this for MinIO and the Milvus components.
This is a feature request to expose these through the Milvus CRD.

In milvus-operator we can support this for Milvus components.
By default milvus-operator uses minio chart in https://github.com/zilliztech/milvus-helm/tree/master/charts/minio. So we also need a patch for milvus-helm.  Or does bitnami provide a helm chart for MinIO, too?

Hi @bcbrockway, I just talked a previous maintainer. There're some bug fixes added to this chart , that're not merged by bitnami at that time, so they decided to maintain a fork by themselves.

Thanks @haorenfsa. Should I raise an issue there for the MinIO changes?
Also, FYI, I also added Pod Topology Spread Constraints as a request to this ticket since it's a very similar type of change for the same components.


refactor Player and get unique ID automatically

I've removed references like uniqueId and userId in favor of playerId. They were ambiguous/inconsistent, and i think userId actually makes more sense but it's more important to be consistent
refactored things into the players class. I didn't think the mainactivity should be responsible for eg retrieving from the db. this allerviates that responsibility of the mainactivity. Downside is now player needs a context to operate with (for example, MainActivity subclasses Context, so you can pass this to the player to initialize it). I don't think this should be too much of an issue because we'll always have some activity close by to use for the context
expanded on shortened names like pI and qL to be consistent

didn't do:

flatten the Player/PlayerInfo classes, i think this should be considered as I don't see the benefit of two classes right now

Looks good here.


added FelixClassLoaderHandler

@elrufaie thanks for this pull request! I created a modification in #106 that does not add external dependencies (sorry, I was trying to push those changes here, but I don't know how to do that in github!). Can you please test that the version in #106 works?
Also, are you sure that Bundle-Classpath is always split with a comma? Is it possible that classpath elements could be split by File.pathSeparator, e.g. the : character?

Thank you Luke. I will test your changes and get back to you. As far as the
bundle-classpath question, I have it working the comma.
On Thu, Feb 2, 2017 at 12:34 AM, Luke Hutchison<EMAIL_ADDRESS>wrote:

@elrufaie https://github.com/elrufaie thanks for this pull request! I
created a modification in #106
https://github.com/lukehutch/fast-classpath-scanner/pull/106 that does
not add external dependencies (sorry, I was trying to push those changes
here, but I don't know how to do that in github!). Can you please test that
the version in #106
https://github.com/lukehutch/fast-classpath-scanner/pull/106 works?
Also, are you sure that Bundle-Classpath is always split with a comma? Is
it possible that classpath elements could be split by File.pathSeparator,
e.g. the : character?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/pull/105#issuecomment-276897385,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsMsffHAZXbnuWL3pU-1N4qC0NvEOGTks5rYZUtgaJpZM4L0z3g
.

--
Harith Elrufaie

done with the recommended changes. thanks

Merged, thanks so much for contributing this code!

PS @elrufaie I added an MIT license header, corresponding to the rest of the project. Can I get your approval to have this licensed under the MIT license, please?

of course. thanks to you!

Released in version 2.0.14.


Should we rename this repo to mimi-page-2009.jl?

close this? @davidanthoff

The pattern we used for all other Mimi models now is to have one repo for each major version we replicate. So we should rename this repo here to mimi-page-2009.jl, I think. Or mimi-page09.jl?

I think it depends on whether we are thinking about this as a point-replication of PAGE, or as the site of future development of PAGE.  In the latter case, it should stay mimi-page (or even just page), to match the principal that Mimi's FUND isn't mimi-fund-3.7.2.
That said, until we get buy-in from Chris, it's not our call to make, and I think we should see what demand there is after the paper.  Until then, mimi-page-2009 seems fine to me.

Alright, this is renamed now.


Domain building fix

added missing realmBuilder.build() (Realm map does not contain mapping for default realm)
Identity: handling exceptions with getMessage() = null (prevent ModelNode.add(null))

I have some changes already on the way for this one - sorry got a little delayed completing the rest of the SSL config before getting ready to merge.


Fix deprecations: remove the old std.string.removechars

I also removed the PokemanException catching style - constructBinary can't be nothrow currently anyways as node.as!string throws ...

This is good. The CI failure will happen a day or another, even if this PR is not merged. I'll open an issue after merging.


k8s: support vm cluster and misc fix

这个 PR 实现什么功能/修复什么问题:

climc 支持 vm 部署 k8s cluster
存储　userdata 时压缩
修复一些 bug

是否需要 backport 到之前的 release 分支:

NONE
/cc @swordqiu @wanyaoqi @yousong
/area climc region

Codecov Report

Merging #882 into master will increase coverage by <.01%.
The diff coverage is 25.64%.

@@            Coverage Diff            @@
##           master    #882      +/-   ##
=========================================
+ Coverage    7.61%   7.61%   +<.01%
=========================================
  Files         353     345       -8
  Lines       54938   53703    -1235
=========================================
- Hits         4184    4091      -93
+ Misses      50360   49227    -1133
+ Partials      394     385       -9

Flag
Coverage Δ

#aFlag
7.61% <25.64%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.66% <0%> (-0.01%)
:arrow_down:

pkg/compute/models/guestdrivers.go
18.18% <0%> (ø)
:arrow_up:

pkg/compute/models/guest_actions.go
0% <0%> (ø)
:arrow_up:

pkg/cloudcommon/userdata/userdata.go
34.48% <34.48%> (ø)

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

pkg/cloudcommon/policy/policy.go
1.25% <0%> (-0.75%)
:arrow_down:

pkg/compute/guestdrivers/azure.go
7.14% <0%> (-0.32%)
:arrow_down:

pkg/cloudcommon/db/db_dispatcher.go
0% <0%> (ø)
:arrow_up:

... and 51 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 2d4779d...749c11a. Read the comment docs.

/lgtm
/approve


[MAUI] BottomTabItem imageicon filled by color

For ios BottomTabItem, if you are putting a png file and when it is selected, the whole image icon will be filled by the selectable color.
If you set the selectablecolor to transparent, the whole icon will shown transparent.
No problem on Android.

sorry didn't get that


Fix markdown links in installation instructions.

I was passing through and noticed some incomplete markdown links. I assumed that they were still intended to be links and added back the references from a previous commit.
Thanks!

Thank you!


print object in console

try to type po (and variable)
virtual filesystem overlay file '/Users/mikhail/Library/Developer/Xcode/DerivedData/GetID-SDK-cchayjietrubkpaayguzfzftyfyx/Build/Intermediates.noindex/GetID-SDK.build/Release-iphonesimulator/GetID.build/all-product-headers.yaml' not found

Hi @VictorAmelin. We'll try to fix it in the next release.
For now, please use the following workaround:
Press ⌘N, select "Cocoa Touch Class", pick Objective-C language, name the class "Empty", let it be a subclass of NSObject. Then confirm when Xcode asks about the Bridging Header. That's all.

Hi @VictorAmelin. We'll try to fix it in the next release.
For now, please use the following workaround:
Press ⌘N, select "Cocoa Touch Class", pick Objective-C language, name the class "Empty", let it be a subclass of NSObject. Then confirm when Xcode asks about the Bridging Header. That's all.

The issue was fixed in newer versions.


Inform user of replaced organizations

The feature
Occasionally, organizations do get replaced. If a user is trying to go to a page for an organization that has been replaced, today they will get a 404 error as the page is missing. Instead, the user could be informed that it has been replaced, and be presented with a link to the new organization.
Why?
This would be helpful for users who find the Govdirectory through old links.
It would possibly also make us have less 404 errors on the site.
Examples and inspiration
In Wikidata, this is stored in replaced by (P1366).

merged into (P7888) can also be used for this purpose.


RESTAPI (v2) - Missing Apply Virtual IP

Describe the bug
After creating a new virtual IP (/api/v2/firewall/virtual_ip) I see no way too "Apply" it.
To Reproduce
Steps to reproduce the behavior:

Create new virtual IP (/api/v2/firewall/virtual_ip)
Browse to /firewall_virtual_ip.php and you will see the Apply Changes button.

Expected behavior
Based on the other REST Apply calls it looks like this is just missing.
pfSense Version & Package Version:

pfSense Version: pfSense 2.7.2
Package Version: v2.0.0-dev-3982522

Affected Endpoints:

URL: /api/v2/firewall/virtual_ip/apply

Additional context
I searched the included docs for apply and could not see anything for virtual ips, I did try the interface apply but that had no effect.

I searched the repo and in v1 these are applied on create and edit, but in v2 I had a harder time finding it. I did find it here:
https://github.com/jaredhendrickson13/pfsense-api/blob/1bd5e5a19be7b2adffe5bfa7af6817f4eeb9a6e7/pfSense-pkg-RESTAPI/files/usr/local/pkg/RESTAPI/Models/VirtualIP.inc#L207
but I could see where it was being used. I could be just missing something here.

Hmm. You're right, we're missing the apply endpoint for virtual IPs. Not sure if I just overlooked this or if the intent was for the behavior to match v1 where virtual IPs were always applied immediately after the API call. Either way, I'll get working on an apply endpoint for virtual IPs.
In the meantime, you can immediately apply virtual IPs by setting the apply control parameter to true in your request.
Thanks for bringing this up!

Thanks for the apply control parameter, that does the job.

/api/v2/firewall/virtual_ip/apply endpoint was added in https://github.com/jaredhendrickson13/pfsense-api/releases/tag/v2.0.0-dev-f207e6f


Added embedded messages, gifs, etc to hug, party and wavy commands

@albrtyng honestly I got too busy with work to work on this right now. feel free to merge as you will and have @nikogrobles deploy to production

I say ship it if it works :shipit:


Content Security Policy with Android Native WebView

I am seeing a strange issue manifesting itself with Android M Native WebView.  No matter how I set the Content Security Policy, when attempting to get a media stream, I end up with the following error:
Refused to load media from 'blob:file%3A///8b0456e0-6888-4a08-8872-b0282c41c672' because it violates the following Content Security Policy directive: "media-src *".
I have tried setting my media-src directive any number of ways without success.  This same code works fine with crosswalk.
Anyone else ran into this?

Certainly sounds like a webview bug. Probably the best way to get the bug filed with the team would be to provide a small test page that reproduces the issue. If you're able to do that, I can file a bug on crbug.com


VSCode 1.94 Debian package can not be installed on Debian 11 anymore (uses unknown compression for member 'control.tar.zst', giving up)

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.94
OS Version: Debian 11 (bullseye)

Steps to Reproduce:

Try to install the Debian package.
Observe:

dpkg-deb: error: archive '/var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up
dpkg: error processing archive /var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Last working package was version 1.93.1.

I was able to install it without problems in debian

I can reproduce this issue and I'm running Debian 11.

I am seeing the same thing. Trying to upgrade on a Raspberry Pi running the equivalent of Debian 11 and it fails with the following:
dpkg-deb: error: archive '/var/cache/apt/archives/code_1.94.0-1727877189_arm64.deb' uses unknown compression for member 'control.tar.zst', giving up

dpkg < 1.28 does not support ZSTD compression, hence Debian 11 Bullseye and older are impacted.
Cf. Debian bug #892664
Since M$ code repository does not match a specific distribution, I see no way of segmenting different releases of a distribution, packages-wise.
Maybe would it be time to set that up?

Since M$ code repository does not match a specific distribution, I see no way of segmenting different releases of a distribution, packages-wise.
Maybe would it be time to set that up?

Either that, or reverting the change, as it does not appear to save any noticeable space anyways (of course zstd is faster to decompress):

code_1.93.1-1726079302_amd64.deb                                                                    12-Sep-2024 18:02  102.7 MB
code_1.94.0-1727878498_amd64.deb                                                                    03-Oct-2024 17:02  108.3 MB

Sorry for this unintended change, this seems to have been impacted by our CI changes last milestone https://github.com/microsoft/vscode/commit/ab30106acd98dc3b118ab4c56acbccf746882662 that bumped the version of dpkg-deb, not sure if the default compression changed with newer versions. I will check and prepare a candidate fix.

Yeah seems to be the case, in the ubuntu version of the deb tools zstd seems to be default compressor for dpkg-deb. Whereas in the upstream repo it is still xz.
We can use -Zxz to revert the compression, which I will make as a candidate fix.

We can use -Zxz to revert the compression, which I will make as a candidate fix.

Thanks for hunting this down!
In the long term, it might also be interesting to add a "try to install deb package" step into the CI, which tries to install the deb for common distros (e.g. Debian, Ubuntu in supported versions) so incompatibilities can be captured by the CI?

Fair point, out team does sanity testing of build bits before releasing but the issue is that we haven't covered a good array of distros to ensure these types of issues are catched. I will work on improving our sanity testing process.

Issue will be fixed in tomorrow's insider and will also be fixed in stable 1.94.2 release early next week.

https://unix.stackexchange.com/a/723014/580693 offers a work-around that looks plausible, and pretty simple, though I haven't tried it myself.  Or, if you're feeling ambitious, upgrade to current Debian.
Personally, I'll just wait for the fix so thoughtfully provided by @deepak1556.

Fair point, our team does sanity testing of build bits before releasing but the issue is that we haven't covered a good array of distros to ensure these types of issues are catched. I will work on improving our sanity testing process.

This problem would only be caught by testing against old versions of Debian.  Debian 11 is currently oldstable .  While it's still under LTS, it is technically EOL as of a couple of months ago.  See this guide.
Since I, and apparently others, are still using the old version, I'm all for such testing, but I just wanted to point out it's a little more ambitious than just testing against the current releases.

Fair point, our team does sanity testing of build bits before releasing but the issue is that we haven't covered a good array of distros to ensure these types of issues are catched. I will work on improving our sanity testing process.

This problem would only be caught by testing against old versions of Debian. Debian 11 is currently oldstable . While it's still under LTS, it is technically EOL as of a couple of months ago. See this guide.

Yes Debian 11 is still supported as "oldstable" and will be supported with security patches until August 31st, 2026. Debian 10 was "oldoldstable" and just went off support effective July 1, 2024.

Since the VS Code system requirements still state Debian 10 is supported, I was not expecting to see any issues with Debian 11 myself 😇

I have the same problem, I have Debian 11 installed on my personal computer.
dpkg-deb: error: el archivo /var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb' contiene un miembro de datos contro
l.tar.zst' ininteligible, abandono
dpkg: error al procesar el archivo /var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb (--unpack):
el subproceso dpkg-deb --control devolvió el código de salida de error 2
Se encontraron errores al procesar:
/var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

https://unix.stackexchange.com/a/723014/580693 offers a work-around that looks plausible, and pretty simple, though I haven't tried it myself. Or, if you're feeling ambitious, upgrade to current Debian.
Personally, I'll just wait for the fix so thoughtfully provided by @deepak1556.

Tried this workaround on my Raspberry Pi running Debian 11 aarch64, VSCode 1.94 was installed without any issues, thanks!
If you need the deb file ready for arm64, I temporarily uploaded it here.

got the same issue
dpkg-deb: erreur: l'archive « /var/cache/apt/archives/code_1.94.0-1727878498_amd64.deb » utilise un procédé de compression inconnu pour le membre « control.tar.zst ». Abandon.
on bullseye

I kindly suggest to people tempted to comment in here to star by reading previous comments, in order to avoid comments with no additional value.

dpkg < 1.28 does not support ZSTD compression, hence Debian 11 Bullseye and older are impacted.
Cf. Debian bug #892664

Same issue. Hope this can be released ASAP

Same issue for code_1.94.1-1728111316_amd64.deb

Closing for verification.
Steps:

Run the following docker run -e COMMIT="7b878f5a39c027a8c4368125ba2165679705d60f" -it --rm --platform linux/amd64 debian:11 /bin/sh -c 'apt update && apt install -y wget libasound2 libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libcairo2 libcurl3-gnutls libdbus-1-3 libdrm2 libexpat1 libgbm1 libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libx11-6 libxcb1 libxcomposite1 libxdamage1 libxext6 libxfixes3 libxkbcommon0 libxkbfile1 libxrandr2 xdg-utils gpg && wget "https://update.code.visualstudio.com/commit:$COMMIT/linux-deb-x64/stable" -O code_1.94.2_amd64.deb && dpkg -i code_1.94.2_amd64.deb'
Follow the prompts and confirm the installation exits without the failure in https://github.com/microsoft/vscode/issues/230418#issue-2564672671

I don't have docker on my Raspberry Pi ... besides it does not have enough space or horsepower to install and run it.
Is that not another solution?

Closing for verification.

Wouldn't it be better to close an issue after positive verification of the problem at hand being solved?

Steps:
1. Run the following `docker run -e COMMIT="7b878f5a39c027a8c4368125ba2165679705d60f" -it --rm --platform linux/amd64 debian:11 /bin/sh -c 'apt update && apt install -y wget libasound2 libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libcairo2 libcurl3-gnutls libdbus-1-3 libdrm2 libexpat1 libgbm1 libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libx11-6 libxcb1 libxcomposite1 libxdamage1 libxext6 libxfixes3 libxkbcommon0 libxkbfile1 libxrandr2 xdg-utils gpg && wget "https://update.code.visualstudio.com/commit:$COMMIT/linux-deb-x64/stable" -O code_1.94.2_amd64.deb && dpkg -i code_1.94.2_amd64.deb'`

2. Follow the prompts and confirm the installation exits without the failure in [VSCode 1.94 Debian package can not be installed on Debian 11 anymore (uses unknown compression for member 'control.tar.zst', giving up) #230418 (comment)](https://github.com/microsoft/vscode/issues/230418#issue-2564672671)

A simpler verification mechanism would be:

Download the https://update.code.visualstudio.com/commit:7b878f5a39c027a8c4368125ba2165679705d60f/linux-deb-x64/stable package
file <package>
If zst compression is mentioned, run away screaming

Just tested on this URL, got redirected to a code_1.94.1-1728111316_amd64.deb package, and xz compression is mentioned, which means it seems you are on the right track.
I would however have waited that package to land in the public repository before closing the current issue, as it is technically not resolved in production yet…

"Closing for verification" means "closing to signal to team members that the issue is ready to verify".
This procedure occurs as part of our endgame.
If pre-release verification fails, the issue gets re-opened again.

Problem solved with 1.94.2-1728494015 from the public repository.
Now would have been a good time to solve the issue.
If you wish so, try to address odd processes at M$ 😉

I'm also "just a user" of VS Code, while I understand the reasoning of some other users here, I think it's also good to think about the perspective of the developers/maintainers of VS Code. GitHub issues is the issue tracking system that the developers use to track what issues need to be worked on. If this issue with the compression with the .deb (for Debian 11) is fixed in the main branch, it is fixed (from a dev perspective); even if it is not yet available as a general release. Maybe there should be a clearer separation between whether issues are resolved for a user perspective vs a developer perspective, but just being aware of this difference is I think useful.
But specifically for this one, it was explained that this should be resolved as part of 1.94.2


Remove version: BlenderFoundation.Blender.LTS version 3.3.4

Old package
Microsoft Reviewers: Open in CodeFlow

URL: https://download.blender.org/release/Blender3.3/blender-3.3.4-windows-x64.msi
OK
(Automated message - build 888)


Fixed patching scriptfor windows

Problem
patch script didn't work for windows
Solution
script is fixed, the fix is tested on windows laptop
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@aderende, how did you test this solution? I have just created new workflow to build project in Windows runner, and it fails on patching error (you can see full output here https://github.com/aws/language-servers/actions/runs/9550009740/job/26320974932?pr=307). I tried to setup project from scratch on my Windows laptop, and the same error occurred, so it's not specific to the runner.
npm error code 1
npm error path D:\a\language-servers\language-servers\server\aws-lsp-yaml
npm error command failed
npm error command C:\Windows\system32\cmd.exe /d /s /c node patchYamlPackage.js
npm error error: patch failed: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js:16
npm error error: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js: patch does not apply
npm error node:child_process:929
npm error     throw err;
npm error     ^
npm error
npm error Error: Command failed: git apply D:\a\language-servers\language-servers\server\aws-lsp-yaml/patches/markdown/yamlHover.esm.patch
npm error error: patch failed: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js:16
npm error error: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js: patch does not apply
npm error
npm error     at checkExecSyncError (node:child_process:890:11)
npm error     at execFileSync (node:child_process:926:15)
npm error     at getPatchProcCommand (D:\a\language-servers\language-servers\server\aws-lsp-yaml\patchYamlPackage.js:[43](https://github.com/aws/language-servers/actions/runs/9550009740/job/26320974932?pr=307#step:4:44):16)
npm error     at applyPatch (D:\a\language-servers\language-servers\server\aws-lsp-yaml\patchYamlPackage.js:59:27)
npm error     at D:\a\language-servers\language-servers\server\aws-lsp-yaml\patchYamlPackage.js:74:9
npm error     at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) {
npm error   status: 1,
npm error   signal: null,
npm error   output: [
npm error     null,
npm error     '',
npm error     'error: patch failed: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js:16\n' +
npm error       'error: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js: patch does not apply\n'
npm error   ],
npm error   pid: 1860,
npm error   stdout: '',
npm error   stderr: 'error: patch failed: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js:16\n' +
npm error     'error: node_modules/yaml-language-server/lib/esm/languageservice/services/yamlHover.js: patch does not apply\n'
npm error }
npm error
npm error Node.js v18.20.3


Help!

Hi,
I am a new Home Assistant user before i used Homebridge and node red, a lot off my lights are controlled via the Loxone mini server i now have setup your integration with hacs but only my switches and sensors are showing up the lights with light controllers are not showing in home assistant can someone help me how to configure these. The Loxone lights group is empty in home assistant and i have a notification that says:The following integrations and platforms could not be set up: loxone.light please check your config
configuration.yaml file:
#Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
#Text to speech
tts:

platform: google_translate

alexa:
smart_home:
loxone:
port: 80
host: <IP_ADDRESS>
username: ***
password: ***
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

First of all make sure that all light and light controllers are visible in the loxone app. Define for all entities a group and a room. Update to the latest pyloxone version if not already done.
Pyloxone supports only the light controller V2 not the v1. So convert it if you have the old version. It should be easy in the loxone config software.
Then you can temporarily change your log messages like I showed in https://github.com/JoDehli/PyLoxone/issues/27

Is it fixed? Than I can close this issue?

It is fixed thank you.


Appointment form is executed while editing the patient details

When the midwife is editting/updating the girl's details , the appointment form is executed after and yet it shouldnt.
It should only be executed during mapping.
Is there a way we can stop it from executing during updating?

Workflow.
For New Patient:(Click Map girl button)
Execute mapping form + Appointment Note
For Existing Patient.(Click View/Edit Girls Button-->Select Girl--> Select Update)
Execute mapping form only (with existing girls info).
Appointment Note shouldnt be executed.
To record medical info:
Select-->View/Edit All Girls-->Select Girl-->Select Update--> Select Appointment Note

Thanks @donrukanga1


[epic] Support for large queries from data API

When querying the data API I want to be able to make queries and get results with 100k or 1m+ results and download them so that I can extract the data I want even if larger
Acceptance

[ ] Design the solution

[ ] Consider authorization considerations

[ ] Write to storage approach

[ ] Choose storage backend
[ ] Stream to storage from data API (or trigger background job)
[ ] Return download URL

[ ] Setup switch from "streaming" to write to storage

Analysis
There are 2 approaches:

Stream the whole result
Extract the query results to storage and give storage url to the user

One can also have hybrid e.g. do the former up to some number of results and then switch to 2.
There are several advantages of option 2:

You have a natural cache structure on disk so that the same query may not need to be recomputed (you can expire exported results after some time period)
If your download/stream is interrupted you can resume it from storage (rather than re-running the query)
You give the end user the option to share the file for a certain period of time with other users

The disadvantages (at least the small data sizes):

It's more complex / more work on backend
Slower (greater latency)
More complex for user: they have 2 steps where there was one (get query result, extract download url and download)

@rufuspollock
The current implementation Streams the results, we are testing the performance in some testing (but distributed) environments.


[App]: wandb.log is not successful

Current Behavior
I run wandb.log(dict) to store a python dict, and use  wandb.finish() to synchronize the dict. But it reports a bug, what should I do?
If I do not use wandb.finish() the dict will not be synchronized to the website UI either.
valuating: self._logger.finish() did not finish after 3.00 seconds.
This may mean a number of things:
- This evaluation is really slow and this is expected.
    In this case it's possible to silence this error by raising the timeout, setting the
    PYDEVD_WARN_EVALUATION_TIMEOUT environment variable to a bigger value.

- The evaluation may need other threads running while it's running:
    In this case, it's possible to set the PYDEVD_UNBLOCK_THREADS_TIMEOUT
    environment variable so that if after a given timeout an evaluation doesn't finish,
    other threads are unblocked or you can manually resume all threads.

    Alternatively, it's also possible to skip breaking on a particular thread by setting a
    `pydev_do_not_trace = True` attribute in the related threading.Thread instance
    (if some thread should always be running and no breakpoints are expected to be hit in it).

- The evaluation is deadlocked:
    In this case you may set the PYDEVD_THREAD_DUMP_ON_WARN_EVALUATION_TIMEOUT
    environment variable to true so that a thread dump is shown along with this message and
    optionally, set the PYDEVD_INTERRUPT_THREAD_TIMEOUT to some value so that the debugger
    tries to interrupt the evaluation (if possible) when this happens.

Expected Behavior
No response
Steps To Reproduce
No response
Screenshots
No response
Environment
OS: Ubuntu20
Browsers: Chrome
Version: Latest
Additional Context
No response

I can somehow understand the reason. After calling wandb.finish(), I use wandb.init() again, but still the server cannot immediately initialize again, so it causes some problem.


Make OpenSSL work with POSITION_INDEPENDENT_CODE

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2662
https://travis-ci.org/ingenue/hunter/builds/293833058?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2663
https://travis-ci.org/ingenue/hunter/builds/293898774?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.19.138


AreScopesValidAsync

[ ] I read and understood how to enable logging

Issue / Steps to reproduce the problem
Relevant parts of the log file
2017-11-08 16:19:53.883 +04:00 [Fatal] Unhandled exception: "System.NullReferenceException: Object reference not set to an instance of an object.
   at IdentityServer4.Validation.ScopeValidator.<>c__DisplayClass19_0.<AreScopesValidAsync>b__1(IdentityResource x)
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Func`2 predicate, Boolean& found)
   at IdentityServer4.Validation.ScopeValidator.<AreScopesValidAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Validation.AuthorizeRequestValidator.<ValidateScopeAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Validation.AuthorizeRequestValidator.<ValidateAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Endpoints.AuthorizeEndpointBase.<ProcessAuthorizeRequestAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Endpoints.AuthorizeEndpoint.<ProcessAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext()"
2017-11-08 16:19:53.889 +04:00 [Error] Connection id ""0HL96KC1T9G3F"", Request id ""0HL96KC1T9G3F:00000001"": An unhandled exception was thrown by the application.
System.NullReferenceException: Object reference not set to an instance of an object.
   at IdentityServer4.Validation.ScopeValidator.<>c__DisplayClass19_0.<AreScopesValidAsync>b__1(IdentityResource x)
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Func`2 predicate, Boolean& found)
   at IdentityServer4.Validation.ScopeValidator.<AreScopesValidAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Validation.AuthorizeRequestValidator.<ValidateScopeAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Validation.AuthorizeRequestValidator.<ValidateAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Endpoints.AuthorizeEndpointBase.<ProcessAuthorizeRequestAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Endpoints.AuthorizeEndpoint.<ProcessAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.BaseUrlMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.<ProcessRequestsAsync>d__2.MoveNext()

hello i use custome db. I can not understand this problem. identityserver4 version is 2.0.2

...


Module stops with error message "userAgent must be a string"

Hi.
I just installed a clean new version of MagicMirror, added this module (from the greenkeeper/hafas-client-5.1.1 branch) modified the example configuration with my own station ID and started MM.
But the module crashes with the following message:
[17:46:00.564] [ERROR]  TypeError: userAgent must be a string
at createClient (/home/pi/MagicMirror/modules/MMM-PublicTransportHafas/node_modules/hafas-client/index.js:31:9)
at new HafasFetcher (/home/pi/MagicMirror/modules/MMM-PublicTransportHafas/core/HafasFetcher.js:29:24)
at Class.createFetcher (/home/pi/MagicMirror/modules/MMM-PublicTransportHafas/node_helper.js:31:17)
at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-PublicTransportHafas/node_helper.js:17:14)
at Socket. (/home/pi/MagicMirror/js/node_helper.js:113:11)
at Socket.emit (events.js:198:13)
at /home/pi/MagicMirror/node_modules/socket.io/lib/socket.js:528:12
at process._tickCallback (internal/process/next_tick.js:61:11)
^Cevents.js:174
throw er; // Unhandled 'error' event
^
A can find the reason. The code seems to be ok. (hands over a static string to the method)
My configuration:
{
module: "MMM-PublicTransportHafas",
position: "bottom_right",
config: {
stationID: "00903736",                   // Replace with your stationID!
stationName: "Holzwickede Bahnhof",   // Replace with your station name
direction: "",                    // Show only departures heading to this station. (A station ID.)
ignoredLines: [],                 // Which lines should be ignored? (comma-separated list of line names)
excludedTransportationTypes: ["bus"],  //  (comma-separated list of types) possible values: StN for tram, BuN for bus, s for suburban
timeToStation: 8,                // How long do you need to walk to the next Station?
timeInFuture: 60,
showColoredLineSymbols: true,     // Want colored line symbols?
useColorForRealtimeInfo: true,    // Want colored real time information (timeToStation, early)?
showTableHeadersAsSymbols: true,  // Table Headers as symbols or text?
maxUnreachableDepartures: 0,      // How many unreachable departures should be shown?
maxReachableDepartures: 7,        // How many reachable departures should be shown?
customLineStyles: "",             // Prefix for the name of the custom css file. ex: Leipzig-lines.css (case sensitive)
showOnlyLineNumbers: false        // Display only the line number instead of the complete name, i. e. "11" instead of "STR 11"
}
},
I did the following:
git clone ....
git checkout greenkeeper/hafas-client-5.1.1
npm install
Master didn't compile with version conflicts.
When i disable the module MM starts and runs normally.
Any idea?
Thanks in advance.

I really don't know what the problem was.
Just deleted and reinstalled the module. Didn't change anything else.
Now it runs like a charm.
Thanks for coding it.

Author of hafas-client, the library used by MMM-PublicTransportHafas, here.
hafas-client@5 has breaking changes over the currently used hafas-client@2. This means that you cannot upgrade from hafas-client@2 to hafas-client@5 without adapting the MMM-PublicTransportHafas code. This is why it complains about a missing userAgent argument.
The greenkeeper/hafas-client-5.1.1 branch has been created by a bot, which did obviously not adapt the MMM-PublicTransportHafas code to hafas-client@5. For a German discussion on upgrading hafas-client, check #67. This repo doesn't seem to be maintained though.


Installed KFServing SDK 0.4 but getting import error while running the custom built image

/kind bug
What steps did you take and what happened:
Run a custom built image with KFServing SDK 0.4.
Traceback (most recent call last):
  File "/python3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/python3/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/job/blambda-function/image_transformer_v2/__main__.py", line 15, in <module>
    import kfserving
  File "/python3/lib/python3.7/site-packages/kfserving/__init__.py", line 18, in <module>
    from .storage import Storage
  File "/python3/lib/python3.7/site-packages/kfserving/storage.py", line 23, in <module>
    from google.cloud import storage
  File "/python3/lib/python3.7/site-packages/google/cloud/storage/__init__.py", line 39, in <module>
    from google.cloud.storage.batch import Batch
  File "/python3/lib/python3.7/site-packages/google/cloud/storage/batch.py", line 31, in <module>
    from google.cloud.storage._http import Connection
  File "/python3/lib/python3.7/site-packages/google/cloud/storage/_http.py", line 17, in <module>
    from google.cloud import _http
  File "/python3/lib/python3.7/site-packages/google/cloud/_http.py", line 22, in <module>
    from six.moves import collections_abc
ImportError: cannot import name 'collections_abc' from 'six.moves' (unknown location)

What did you expect to happen:
Anything else you would like to add:
We have fixed this in master branch but looks like we need to patch the setup.py in 0.4 branch and release a new minor version
Environment:

Istio Version:
Knative Version:
KFServing Version:
Kubeflow version:
Kfdef:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

fixed in KFServing SDK 0.4.1


There are two more sitemap index files

robots.txt is supposed to list all the sitemap index files; there are now two more

Ping?


Multi projects not working

Description:

Look I've already successfully performed the configuration for just one project. (Both in the local environment and in the production environment).
But now I need the configuration for multiple projects.
I performed the patent configuration at the link https://laradock.io/getting-started/#B, and it worked perfectly on the local env, but when I upload the settings to production. Both projects fall into error 404.
I thank you for your help.
Project configuration

-laradock
-project1
-project2

Nginx Config

laradock/nginx/sites/default.conf

server {

    listen 80 default_server;
    listen [::]:80 default_server;

    # For https
    listen 443 ssl default_server;
    listen [::]:443 ssl default_server; # dont add ipv6only=on
    ssl_certificate /etc/nginx/ssl/default.crt;
    ssl_certificate_key /etc/nginx/ssl/default.key;

    server_name domain.com www.domain.com;
    root /var/www/project1/public;
    index index.php index.html index.htm;

    location / {
         try_files $uri $uri/ /index.php$is_args$args;
    }

    location ~ \.php$ {
        try_files $uri /index.php =404;
        fastcgi_pass php-upstream;
        fastcgi_index index.php;
        fastcgi_buffers 16 16k;
        fastcgi_buffer_size 32k;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        #fixes timeouts
        fastcgi_read_timeout 600;
        include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }

    location /.well-known/acme-challenge/ {
        root /var/www/letsencrypt/;
        log_not_found off;
    }

    error_log /var/log/nginx/laravel_error.log;
    access_log /var/log/nginx/laravel_access.log;
}

laradock/nginx/sites/site.conf

     server {
....
          server_name domain2.com www.domain2.com;
          root /var/www/project2/public;
....
     }

cp laravel.conf.example laravel-project1.conf
cp laravel.conf.example laravel-project2.conf

update new *.conf sever_name and root

@bestlong I have done that, still dont work.

check log first. docker-compose logs -f nginx
There may be important informationㄡ

It Just shows:
Attaching to laradock_nginx_1

It Just shows:
        Attaching to laradock_nginx_1

Try to compose up without -d flag and see what's happening with your nginx.
I don't thing the file naming is a real cause of your problem.

It’s not a file name issue. I suggest that every project will create a new profile.
after docker-compose logs -f nginx to see log, also need open browser Will show 404 related messages

I could not solve this using one nginx container to serve two apps, instead i used traefik and created two nginx instances each one for an app.
Its working, but now i wonder if this is a good approach for solving this issue, since this approach forced me to run for each app another related container. I.E
For app1
nginx1,
workspace1,
php-fpm1,
php-worker1

For app2
nginx2,
workspace2,
php-fpm2,
php-worker2


Feature - included question for tests in PR template

What type of PR is this?
To help drive tests into the PR process.
/kind cleanup
What this PR does / why we need it:
As the project is growing, it helps communicate to the PR's contributors require automated tests.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?
NONE
NONE

/hold

/hold

/lgtm

@saschagrunert Is the hold still required on the PR?

/lgtm

@saschagrunert Is the hold still required on the PR?

/hold cancel
forgot about that, sorry

/hold cancel
forgot about that, sorry

/hold cancel
forgot about that, sorry

Thanks 😄

/hold cancel
forgot about that, sorry

Thanks 😄


Cannot install achilles in OSGI environment (Servicemix 5.4.0) due to duplicate package info.archinnov.achilles.type

The package info.archinnov.achilles.type is exported by achilles-cores AND achilles-model. See the Export-package property in the MANIFEST.MF in both jars.
When starting the achilles-core bundle, the error is :
Error executing command: Error starting bundles:
Unable to start bundle 1021: Uses constraint violation. Unable to resolve bundle revision info.archinnov.achilles-core [1021.0] because it exports package 'info.archinnov.achilles.type' and is also exposed to it from bundle revision info.archinnov.achilles-model [1023.0] via the following dependency chain:
info.archinnov.achilles-core [1021.0]
import: (&(osgi.wiring.package=info.archinnov.achilles.exception)(version>=3.2.0)(!(version>=4.0.0)))
|
export: osgi.wiring.package=info.archinnov.achilles.exception; uses:=info.archinnov.achilles.type
export: osgi.wiring.package=info.archinnov.achilles.type
info.archinnov.achilles-model [1023.0]

Ok I got it.
Indeed the package info.archinnov.achilles.type is present both in achilles-model and achilles-core. Why ?
The package info.archinnov.achilles.type is supposed to contain public Java classes exposed by Achilles, like InsertStrategy, Counter...
Why can't we merge them in one module rather than in 2 different modules ? Because the classes in module achilles-core are dependent on the java driver classes whereas classes in the module achilles-model has 0 external dependency (that was the purpose of this module)
Solution ? Move the current classes in the achilles-core module to the achilles-model module:

Empty
IndexCondition
IndexRelation

Rename the existing info.archinnov.achilles.type package in the achilles-core module to info.archinnov.achilles.options
Again, it'll be done in the release next week

Fixed in Achilles 3.2.2


added many ways to prints hello world in js

Hi, thanks for the effort but a program in javascript has already been accepted. You can try out any new language which you don't know much about!


Loading animation for the Registry

@smurthas I emailed a new one to you.

@merc3po I set it load only show if loading takes more than 1000ms because it was pretty fast and mostly only showed
"l   o"
and then flashed away.
registry is faster enough that this almost never shows now, but will show in the event that the registry gets bogged down.

That sounds ideal! Thanks, homie!


About dataset preparation

The link https://maitreyapatel.com/CRIPP-VQA/#dataset is the precessed data or raw data? The script in dataset/ cannot run.

@dxbdxx the link https://maitreyapatel.com/CRIPP-VQA/#dataset contains the raw annotations. Plus it also contains the MaskRCNN extracted features. Script inside dataset can only generate video from the annotation files.
If possible, feel free to share the detailed error. I will try to help you out.

Thanks for your reply. Now I can understand and conduct the data preparation process after modifying the script. In fact, the script image_generation.sh only shows the foundamental steps and cannot run directly. The python file is recreate.py instead of recreation_v3.py. And I also need to modify the script to process all downloaded annotations.

I'm glad it is working for you. And thanks for pointing out this problem.
Feel free to create a pull request or I will update the repo to resolve this issue as soon as possible.


Arrow or cursor control

I have all the Apps listed and working, but to me is kind of useless.
I might not know how to use it, but there is no way of selecting what I want to watch on Netflix, youtube, etc through the app.
If you could add the arrows as there is on the remote and on Smartthing it would be perfect.

Key Codes
service: media_player.play_media
data: {
  "entity_id": "media_player.living_room_tv",
  "media_content_type": "send_key",
  "media_content_id": "KEY_DOWN",
}


Add learning resources creator to beta staging

An attempt to expose the application added by https://github.com/RedHatInsights/learning-resources/pull/54.
I'm not sure how exactly I should be doing this, so this is probably wrong?

It's indeed correct.


Add content-base-pro image builds

Adds a build-pro make target. All pro images are built FROM the existing content-base images for each distro (bionic, right now obviously)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Just to make sure I understood this feedback correctly:

Update the base path for the new pro images to be content-base/bionic-pro
Add a new github action that is a dependency of the content-base/bionic build

My intent for building FROM the existing content-base images was to avoid all the duplication in the dockerfile and to use the build cache to speed up the build. Is there an alternative approach for these pro images that's preferred?

That sounds good to me! The other thing we could do is create a path called content-pro/bionic.
I like the pattern of using the FROM to reduce duplication, etc. It's just a bit tricky to set up the builds properly for that. I think the pattern you describe is perfect and will get that to happen properly 😄 I'm not sure how to optimize that type of dependency tree - on one hand, for testing, we could probably run concurrently, but for building and publishing images, we definitely want them to be a dependency 🙈

I think I agree on all points. How does this sound?

content-base and content-pro for the image names
reorg the folder structure (and rename content to connect-content):

connect-content

base/bionic
pro/bionic

rename .github/build-content-base.yaml to .github/build-connect-content.yaml

I like that a lot!! With the one small caveat that I lean towards stripping connect out, since the hope (long term) is that these images could be used to back content in the IDE (i.e. if we can mount in the IDE bits), or outside of Connect too!


[Tracking Issue] Relax Training M0

There has been increased interest from the community in using TVM for training. Relax, the next generation graph level IR of TVM, also faces the demand of training model.
We are building a training workflow on Relax, including:

an automatic differentiation tool based on source code transformation
an optimizer abstraction and common optimizers
a loss function abstraction and common loss functions
Trainer API that integrates them together, and is easy to use

The training APIs can serve many needs. You will be able to:

train a model from scratch. You can use the compilation advantages of TVM to speed up the training process.
fine-tune a model on device based on TVM.
deploy the process of training models to various devices that TVM supports, such as FPGA and Raspberry PI.

This work is mainly done by @SiriusNEO and @Ubospica, with the help from @tqchen @junrushao @MasterJH5574 @Hzfengsy @spectrometerHBH et al.
Further introduction of our work:
A jupyter notebook tutorial of the training APIs can be found here.
Detailed explanation of the AD pass, and its limitations can be found here.
Currently a large part of our work has been merged into the mlc repo. Now our work is tracked at this issue.
The APIs are still changing. We will update the tutorial within a period of time after the API is modified.

I would be curious to hear about the plans for further developing AD in Relax. We should be able to support all of the language's features by building up the "tape" within Relax (this could be accomplished through PackedFuncs).
We could consider using the approach in Relay's general-purpose AD pass, where the "tape" is built up using a closure: https://github.com/apache/tvm/blob/main/src/relay/transforms/higher_order_gradient.cc (I think we should aim to make AD as general as we can, as this would allow us to target all manner of diverse models for training).


Request logging support

How do you see this working differently to something like:
[:any (ratpack.handling.RequestLogger/ncsa)]

I'd be more than happy to take a stab at it, if you outline what you're imagining.

Ho @moea
The main idea of this issue is provide a "clojury" api for it, one just wrap the ratpack.handling.RequestLogger/ncsa and other providing some kind of api for allow the user log in different logger or provide more information.
I imagine something like:
(require '[catacumba.handlers.logging :as logging])

[:any (logging/handler)]

;; and

(defn my-logger-fn
  [logger-context]
  (println (:method logger-context) "-" (:path logger-context))))

[:any (logging/handler my-logger-fn)]

The logger-context may be a hash-map with limited set of usefull keys generated from http://ratpack.io/manual/current/api/ratpack/handling/RequestOutcome.html


Add new utl() mixin.

Closes #33861
First proof-of-concept attempt to implement the mixin idea in #33861.
What's missing
We need to boil down where everything should go (file location) and how everything should be named (variables, mixins, functions).
Also I would like to add tests, but I have no idea how to do that for SASS.

Coming in #35465!


chore: run npm audit

Description
Run npm audit to fix 85 vulnerabilities (1 moderate, 83 high, 1 critical)
Checklist

[x] All tests passing
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary
[x] Commits and PR follow conventions

@yfr hi!
Robert gave me your contact.
Could you please take a look at the PR?


Singleton custom list

When CCSpan find frequent singleton sequences, it should put the singleton sequence into a CustomEqualsList to ensure that comparisons are done using structural equivalence.

Codecov Report

Merging #282 into master will increase coverage by 0.83%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #282      +/-   ##
============================================
+ Coverage     80.22%   81.06%   +0.83%
- Complexity      511      550      +39
============================================
  Files            66       66
  Lines          1502     1600      +98
  Branches        232      269      +37
============================================
+ Hits           1205     1297      +92
- Misses          206      214       +8
+ Partials         91       89       -2

Impacted Files
Coverage Δ
Complexity Δ

...pi/miningpipeline/patterndetector/ccspan/CCSpan.kt
100% <100%> (+2.38%)
50 <0> (+15)
:arrow_up:

.../cafejojo/schaapi/miningpipeline/MiningPipeline.kt
64.44% <0%> (-9.92%)
5% <0%> (ø)

.../projectcompiler/javajar/JavaJarProjectCompiler.kt
88.88% <0%> (-2.78%)
10% <0%> (+4%)

...tionpipeline/githubtestreporter/WebHookReceiver.kt
87.5% <0%> (+0.83%)
12% <0%> (+3%)
:arrow_up:

...raryusagegraph/jimple/GeneralizedNodeComparator.kt
85.29% <0%> (+1.29%)
21% <0%> (+3%)
:arrow_up:

...ine/testgenerator/jimpleevosuite/ClassGenerator.kt
95.27% <0%> (+2.88%)
57% <0%> (+11%)
:arrow_up:

.../validationpipeline/testrunner/junit/TestRunner.kt
88.37% <0%> (+3.07%)
23% <0%> (+3%)
:arrow_up:

...aryusagegraph/jimple/SootNameEquivalenceChanger.kt
80% <0%> (+5%)
2% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Issue with k8s.io/docs/tasks/tools/install-minikube/

The install doc prescribe to use "sudo install minikube /usr/local/bin/" but it is wrong.
Proposed Solution:
Please change "sudo install minikube /usr/local/bin/" to "sudo mv minikube /usr/local/bin/"
Page to Update:
https://kubernetes.io/docs/tasks/tools/install-minikube/

I think the command is valid. There is an install command that your machine may not have - https://linux.die.net/man/1/install

@prasadkatti Apologies for having very short description of the issue. Updated it to include more context.


Pong Game in Python

Please assign me so I can make a Pong game using Python

Assign to you @DebdattaRay

Hey, please assign it to me.
I want to contribute.


[Integration tests] WebIDE test

It should be possible introduce a new step after Wait XSK Kyma Startup in the nightly build, to migrate project containing XS specific artefacts like:

*.xsjs
*.hdbtable
*.calculationview
etc.

Note: To be able to execute the test multiple times, it should be possible to Unpublish (drop) the database artefacts like *.hdbtable, *.hdi, *.hdbdd, etc.
Related to:

https://github.com/SAP/xsk/issues/750
https://github.com/SAP/xsk/issues/540

Create Selenium Test to:

Login
Open migration perspective
Migrate from ZIP
Import products sample zip --> https://github.com/sap/xsk/releases/download//products.zip --> PRODUCTS_XSC.zip
Execute migration
Validate content is as expected --> compare with downloaded products.zip

As these steps seems like a lot of effort to be implemented with commands in the GitHub action (and will be also hard to maintain) it would be best to be implemented as an external program e.g. Node.js/Dirigible app.

This issue is closed as the project is no longer maintained


Date prediction tables have epoch seconds in some fields

Example:

This ticket is a duplication of https://github.com/Metaculus/metaculus/issues/348
As mentioned in comment here, Luke already fixed this: https://github.com/Metaculus/metaculus/issues/348#issuecomment-2343321329
It works fine on dev: https://dev.metaculus.com/questions/3479/

Sorry, I should have checked on dev.


Password issue

Hello,
After initial login i can't log back.
Can you please offer me what is the fastest way to reset rocket chat to initial run to set an admin account?
I have Ubuntu 16.04  and latest version of rocket chat.
Thank you in advance.

Closing because this seems like a Rocket.Chat config issue, not the adapter. Please comment with more detail to reopen if required.


Refactor adding of vertices

Changed can_build to return True
Factored out -1 bone index check (still treats it as unsigned)
Factored out adding each vertex to the surface
Add vertices without indices and then let SurfaceTool generate
indices

Tested on Windows with some other changes to get it to compile that I
haven't included. Appears to be exactly as broken as the original, but it should be a bit faster and use less GPU memory since it only adds each vertex once per index and then reindexes instead of adding all vertexes to each surface.

Superseded by: https://github.com/V-Sekai/godot-pmx/pull/2


Adjust z-index of site-header to allow native ad to be clicked

 CPG Next: Top Enticement Link Change


streaming support for upsert not supported

Issue in ./help/profile/tutorials/add-profile-data.md
the doc refers to streaming support for upsert, but streaming is not currently supported.
"This can be done through batch or streaming ingestion and requires a Profile-enabled dataset configured with an upsert tag. For more information on how to configure a dataset for attribute updates, please refer to the tutorial for enabling a dataset for Profile and upsert."

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-118173.

@nhecht the documentation team has verified this information, and the documentation is correct.
Upsert can be used for streaming, but users don't need to enable this at the dataset level. It depends on the type of message you pass along that determines whether its a patch or a put operation. Patch in streaming has been in a place for a very long time.
Closing this ticket.

@vfalon  - understood streaming is supported. But I do not believe the method described in the article does support streaming upsert and I could not find anywhere in the docs that described how to format the payload for streaming upsert, is there are reference for that somewhere?


Made pretender._handlerFor public

Reasoning:
Many complex test suites use this library to mock their backend server, and these tests and route handlers can get very complex. When we write e2e tests it is useful to override route handlers make server respond with error. However in such scenarios it would be also useful to test that user can fix their errors when server goes online/behaves correctly while staying on the same page with the error. Thus a developer would like to override the overridden route with historical route handling logic, instead of overriding with custom logic twice:
test('testing form submit error', function(assert) {
  // Saving previous handler to variable:
  let previousHandler = this.server.pretender.handlerFor('POST', '/users', () => {}).handler;

  // mocking the endpoint for error:
  this.server.post(`/users`, () => {
     assert.step('api-call-error');

     return new Response(500, {}, {});
   });

  // click()

  // assert error case

  // Override the overridden route with the initial handler, so no more extra mocking needed:
  this.server.post('/users', previousHandler);

  // click()

  // assert success case
});

This change encourages developers to use this pattern, which makes tests behave slightly more like their backend, if their backend is mocked correctly, and makes the test easier to debug since there are less versions of mocking of the same endpoint in the entire test suite.
Additional details:

In a separate commit, prettier config which matches the source code added to package.json.
In a separte commit, phantomjs removed since it isn't relevant anymore and breaks yarn install for contributing.

Hi @xg-wang , we need this functionality in a large mirage codebase for various use-cases, so let me know if you have further questions. Otherwise we would like this to be merged.

Hi @izelnakri, in your example, this.server.post(${notifierBaseURL}/v1/rules, previousHandler); is it supposed to be this.server.post(/users, previousHandler);?
Looks like you want to toggle the handler's behavior in a test by retrieving the handler for the route and verb combination, which you can do:

const originalHandler = server.get(/* ... */);
the handler access a variable that can be toggled in the test to change response.

Is the need here about not able to access the originally defined handler therefore you need to read it from within your test?

yes :facepalm: its is this.server.post('/users', previousHandler); again. Updated the Issue description.

Interesting, the calls return the handler? I'll try this out and get back to you!

@izelnakri no problem! Let me know if that works for you. I can update the README later

ok I just found one more issue with your proposed solutions:
1- This is interesting for few test cases I will try.
2- In a big application with many route handlers your second solution would mean exporting the route handler as ES module function export, currently routes can be registered without separating the handler, and its more readable this way. We already kind of put a symbolic reference by calling the http method and declaring a route string:
this.get('/users') so we should be able to lookup a registry by providing this info I think, thus we dont need to refactor all our route handlers to make them overridable with the same route handler default.

Hi @xg-wang , I hope the arguments I made above are convincing for this pull request to be merged, as it is just a removal of the _ in the method name and making it public, without this small change in a large codebase I had objections of using a private API, although this shouldnt be a private API based on my reasonings above, including your suggestions. Thus, for the benefit of everyone we should have this method private.
There was a reason why this method was needed internally in the library in the first place, and very good reasons to be made public.

@izelnakri I think we need

test and documentation to cover what the new public API support, and what is the returned value (route-recognizer result https://github.com/tildeio/route-recognizer/blob/master/README.md#usage)
https://github.com/pretenderjs/pretender/blob/v3.4.3/src/index.ts#L232-L240 what happens when trying to get from URL / verb never registered, simply creating a new one doesn't look great.
Also I haven't investigated, what are scenarios matches have more than one entry? https://github.com/pretenderjs/pretender/blob/v3.4.3/src/index.ts#L236
Can we get better name? It's really returning the route-recognizer matched result.
What is the last param request supposed to do?

I'm also not sure what is a public way to re-register a route handler for route-recognizer. That said, providing an easy way to retrieve the registered handler you've registered in pretender is fine. The current way to retrieve them from readme is not great const handler = server.handlers[0];
Sorry I do not currently have time for my own thoughts here, but wanted to share with you what I think is needed to make the API public.
To unblock yourself from the objections it looks like you can do it with public APIs
    let registry = pretender.hosts.forURL(url)[verb];
    let matches = registry.recognize(pretender.parseURL(url).fullpath);

    let match = matches ? matches[0] : null;

    return match;

Awesome, Ill read the points in detail. Thank you for your detailed answer, and looking into this in depth 👍


SSL verification is Running - [BRIEF DESCRIPTION]

App Id: d2hyvve40idtc2
Region: eu-central-1
Step: SSL verification
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
The process is still running after 8hours.
Error message
We validated that the CNAME record exists in your DNS file. We will now verify ownership of the domain. If this takes longer than 8 hours, please create an issue in our GitHub issue tracker.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Hi @oelegeirnaert,
By any chance, was the domain transferred to Route53 from elsewhere? If that's the case, you have to make sure to point the NS records in your domain registrar to the ones found in Route53, and try again.

Hi @oelegeirnaert are you still facing this issue?


babel.Transformer is not a function

error
node: v4.2.2
npm: v1.4.9

C:\Users\mnzt\~code\ava-test\node_modules\ava\node_modules\babel-plugin-espower\create.js:6
    return new babel.Transformer('babel-plugin-espower', createEspowerVisitor(babel, options));
           ^

TypeError: babel.Transformer is not a function
    at createEspowerPlugin (C:\MEDIA\~code\Binaries\node_modules\ava\node_modules\babel-plugin-espower\create.js:6:12)
    at Object.<anonymous> (C:\MEDIA\~code\Binaries\node_modules\ava\lib\babel.js:21:3)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

package.json
  "devDependencies": {
    "ava": "^0.4.2"
  },

My bad, there was a stray babel package in node_modules

@mnzt
I have the same issue, how can you solve it ?

@scarletsky
Go into your own node_modules and remove babel packages, then remove them from your package.json. After that, npm install - -save-dev ava should get it working.
I think there may still be an issue with ava using local babel packages, I'll do some bug testing tonight and see if that's the case.

@mnzt
Which babel version are you using? 5 or 6 ?

@scarletsky I'm not running any babel packages in the project, due to those causing the error.
Can you try removing your local babel packages in your project, and see if that temp-fixes things? If so, then I'll reopen this issue and we can provide extra debug info.

@mnzt
after removing babel packages with rm -rf node_modules/babel*, I run tests again.
// test.js
import test from 'ava'
test('foo', t => {
    t.pass();
    t.end()
});

$ ava test.js

Uncaught Exception:  /Users/scarlex/Projects/v1/test.js
  TypeError: (0 , _ava2.default) is not a function
    at Object.<anonymous> (/Users/scarlex/Projects/v1/test.js:9:22)

Uncaught Exception:  /Users/scarlex/Projects/v1/test.js
  TypeError: (0 , _ava2.default) is not a function
    at Object.<anonymous> (/Users/scarlex/Projects/v1/test.js:9:22)

Error: Never got test results from: /Users/scarlex/Projects/v1/test.js
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/ava/lib/fork.js:61:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
From previous event:
    at module.exports (/usr/local/lib/node_modules/ava/lib/fork.js:25:16)
    at run (/usr/local/lib/node_modules/ava/cli.js:120:9)
    at Array.map (native)
    at /usr/local/lib/node_modules/ava/cli.js:206:22
From previous event:
    at init (/usr/local/lib/node_modules/ava/cli.js:198:4)
    at Object.<anonymous> (/usr/local/lib/node_modules/ava/cli.js:243:2)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

@scarletsky well removing babel packages clears up the original issue, I'll put in a merge request later to fix if no one else does first.
Unfortunately I can't debug your issue from mobile, hopefully some one else can help out in the mean time. It might be worth opening a separate issue for it.

@sindresorhus was this fixed in 0.5.0?

No, in fact, I am using 0.5.0...

@scarletsky I had this problem (TypeError: (0 , _ava2.default) is not a function) and was tinkering around trying to fix. Deleted my node_modules folder and accidentally ran ava and it worked. Apparently if you have a local copy of ava and a global copy of ava, it gives you the error you had above.

@hellsan631 seems very variable, similar sort of issue with the original error with local modules interfering with ava's.

I get this error too. This package doesn't seem to be compatible with babel v6.

Ava should really be using absolute paths for it's packages.

We are not Babel v6 ready. #221 is in progress, but until some blocking issues get resolved - v6 is not an option. It will happen soon.

  TypeError: (0 , _ava2.default) is not a function

This is a known issue in Babel v6: https://phabricator.babeljs.io/T6644
This is the primary blocker for AVA upgrading to Babel.

I wasn't using babel v6 when TypeError: (0 , _ava2.default) is not a function happened. Still using babel v5, both locally and globally.

Oops - the actual error confirmed to be Babel6 is:
(0 , _typeof3.default) is not a function.

I copy and pasted without noticing the difference.
That said, I suspect you have a babel 6 dependency hanging out.
Assuming you are not on windows, can you run the following from your project directory:
$ npm ls --depth=0 | grep babel

And paste the contents here.

I don't think so. I am on windows, but I have cygwin installed, so grep still works.
Here are my versions
NPM: 3.3.12
Node: 4.2.2
$ npm ls | grep babel

Brought up nothing in the local repo. Going for global:
$ npm ls -g | grep babel

│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>
<EMAIL_ADDRESS>didn't get babel 6 until<EMAIL_ADDRESS>

Is ava only installed globally?

Yep. It works when its installed only globally.
When ava is installed only locally, the ava command doesn't work.
When ava is installed only globally, ava works fine
However in the guide, you recommend one of the first steps being ava --init, which installed ava as a dev-dependency. So ava is installed then both globally and locally. ava then triggers the type error above when I try and run it

Try reinstalling locally and running as follows:
./node_modules/.bin/ava, that will execute the locally installed version.
Still, the global one should work, as long as it is the same version as your local install.
You may want to also try the following, just to ensure you are not working off a corrupted install:
npm cache clean && npm rm -g ava && npm rm ava && npm i -g ava && npm i -D ava

I get various errors when trying to run it locally using the path to bin instead.
SyntaxError: Unexpected token case
...
SyntaxError: Unexpected token ILLEGAL

Tried the cache clean and still no dice. My full error is here as follows:
Uncaught Exception:  C:\Users\HellsAn631\Zend\workspaces\Pippo\test\reader.test.js
  TypeError: (0 , _ava2.default) is not a function

Uncaught Exception:  C:\Users\HellsAn631\Zend\workspaces\Pippo\test\reader.test.js
  TypeError: (0 , _ava2.default) is not a function

Error: Never got test results from: C:\Users\HellsAn631\Zend\workspaces\Pippo\test\reader.test.js
    at ChildProcess.<anonymous> (C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\lib\fork.js:61:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
From previous event:
    at module.exports (C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\lib\fork.js:25:16)
    at run (C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\cli.js:120:9)
    at Array.map (native)
    at C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\cli.js:206:22
From previous event:
    at init (C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\cli.js:198:4)
    at Object.<anonymous> (C:\Users\HellsAn631\AppData\Roaming\npm\node_modules\ava\cli.js:243:2)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

That looks like a stack trace from running globally. What happens with a local run ./node_modules/.bin/ava

./node_modules/.bin/ava

Well, that worked. hmm. Weird, because just a second ago i tried it and got some syntax erros (listed above). but now, after uninstalling it and reinstalling it it works

You probably got those because we had you delete babel in earlier steps.
If you put the following in package.json:
{
  "scripts" : {
    "test": "ava"
  }
}

Then you can run npm test, and it will use the local version every time.

Is this to be kept the same, @sindresorhus?
I personally feel a user should be able to run ava globally and for the tests to run; it feels much more natural, at least to me.

Really wish the readme clearly stated ava doesn't work with babel 6. I use babel 6 to write my app with es6, but that means it's impossible to use ava to test my app until this issue is resolved. Spent way too long trying to figure this out.
Maybe I'm not understanding things, but this really seems flawed. So if I want to use ava, I'll have to make sure the version of babel used by ava stays in sync with the version I use for my app?

@joshuajabbour when trying to run your tests, are you using ava foo/bar.js or are you using `npm test' after initialising Ava?

@mnzt - This issue is caused by installing babel 6 locally, not local vs global ava cli execution.
FYI:
As of 0.7.0, the ava command will always run the local version of ava if available. Even if invoked globally. That release contains a number of breaking changes, so read the changelog before upgrading.
It should be safe to install 0.7.0 globally, even if your project depends on an earlier version locally. As long as you have run nmp install and the older ava dependency exists locally it should be used.
$ npm install --global ava@latest

Really wish the readme clearly stated ava doesn't work with babel 6.

That is a good point - I will fix that immediately.

Maybe I'm not understanding things, but this really seems flawed.

I agree. Unfortunately a solution that allows you to use whatever version of Babel you want is not trivial. We are waiting on a few blocking issues in Babel 6, and will transition at that time.

@mnzt Does it matter? Both give me the same error, the one you posted in the original issue.

@mnzt To be more clear, my issue is definitely that I have babel 6 installed and ava doesn't understand how to use it. It sounds like a flaw in the design of ava, because I'm using babel 6 to write my application code. ava should be able to use whatever babel I prefer to parse the test files.

@joshuajabbour Ideally, yes, but Babel 6 broke all the things. Babel 6 was also super broken when released with a gadzillion regressions, hence why it has taken us some time to move to it.

Given the discussion in #292 I'm not sure AVA even needs to use the Babel that's in user's projects. AVA should ship with its own Babel dependency for compiling test files. If users want different behavior they should be able to override test file compilation, which will enable them to use any Babel version they want.

@novemberborn Yes, with the Babel 6 change we're not going to use the users Babel, but instead just tell users to use npm@3 if they want to enforce a version as npm will deduplicate it for the user.

@sindresorhus npm won't be able to dedupe if the user depends on a version outside of the SemVer range of AVA's dependencies. Which is effectively where we are with Babel 5 at the moment. Babel 6 is incompatible and shouldn't be used. In the future a user won't be able to force Babel 7 either.
My understanding of #292 is that AVA provides certain transformations of the test source. If different transformations are required the best way to achieve that is by swapping out AVA's transform process entirely.
If that's the way to go then AVA already shouldn't be pulling in the Babel dependency from the user's project.

https://github.com/sindresorhus/ava/pull/221#discussion_r46668343

Which is effectively where we are with Babel 5 at the moment. Babel 6 is incompatible and shouldn't be used. In the future a user won't be able to force Babel 7 either.

That's the whole point. The user would then be able to use Babel 5 themselves, even if we only support Babel 6+, or inverse.

My understanding of #292 is that AVA provides certain transformations of the test source. If different transformations are required the best way to achieve that is by swapping out AVA's transform process entirely.

Yes, but the above will work for most.

The solution discussed in https://github.com/bcoe/nyc/issues/70 could become of use to us in this situation as well.

Wanted to switch from tape to ava, but I am locked into babel 6 :+1:

AVA uses Babel 6 now, and if necessary should work with Babel 5 source projects.


paket restore exited with code 1 with msbuild

C:\Builds\Main\src.paket\paket.targets (39): The command "C:\Builds\Main\src.paket\paket.exe" restore --references-files "C:\Builds\Main\src\Algorithms\paket.references"" exited with code 1.
Is there a minimum required msbuild version? I'm using msbuild v4.0.30319.

When/where is this happening?

Nevermind. It was an permission issue to get one of the nuget packages. Closing the issue.

renangms. Please let us know how to solve this problem.

So how did you solve it??? Why do you just close it without actually telling us how to solve it. Come on.

A path exceeded a limit on characters in my case. Moving the solution to a directory higher up solved the issue. Identified by running the  restore command (similar to op's) in Command Prompt.


Copy over JVM folder from referer

using https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/

closing as done


about gen_train_json.py file

I want to know that whether the selected classes is missing JPG classes, and I thint it may cause the problems that missing data

this part


fix: change icon for navToggle

Motivation
Fix #1230 , to change icon for navToggle to a more traditional one.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Changed the navToggle icon. This is before:

This is after:

Related PRs

@yangshun thanks! Looking forward to contribute more in the future.


[TUTORIAL] Add operator update

Description
Updated Add-Opererator.md document detailing the process of adding missing operator & autograd operator as well as custom node.
Checklist

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

cc @awslabs/raf-reviewer @zachzzc

thanks @anadeem2


Install Another Version... show some double entries for the C# extension only

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.64.2 portable zip version
OS Version: Windows 10 Enterprise, Version 20H2, OS Build 19042.1526

Steps to Reproduce:
i've noticed that among the all extensions i've installed, the C# one is the only one has this issue. Go to the Extensions view. Click Install Another Version... on the menu for the C# extension. Observe that there are double entries on the list showing up since 1.23.17.

I cannot repro it on Mac, will see if I can repro it in windows

Please verify this on Windows


Revamped the Educational Courses project

Title and Issue number
Add functionality and revamp the Educational Courses Project #2709
Made many changes:-

Added Testimonial
Linked the navbar to it's pages
Revamped the about page section

Close #2709
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

@MohitGupta121 Please check out

@pranjay-poddar @TusharKesarwani @MohitGupta121 can this be merged please


weird mica effect on PowerToys run

Microsoft PowerToys version
0.77.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
How I got the issue
OS build used: Windows 11 build 22635.3130
PowerToys version: 0.77.0
Run Powertoys run without battery savers and with transparency effects on. c)
✔ Expected Behavior
The line should not be a thing

❌ Actual Behavior
There is a titlebar-like line with the Windows 11 Mica effect that should not be there.

Other Software
StartAllBack v3.7.3

I'm experiencing this as well on 0.78.

/dup #31008

@david

/dup #31008

I'm uncertain whether this is actually a duplicate of #31008; I just experimented a little more - this bug only seems to manifest when the Mica effect does load properly.

/dup #31008

I'm uncertain whether this is actually a duplicate of #31008; I just experimented a little more - this bug only seems to manifest when the Mica effect does load properly.

My bad, this is actually a duplicate of #30206


bug: pipeline tables not rendered correctly

Neovim version (nvim -v)
0.10
Operating system
Arch Linux
Terminal emulator / GUI
Kitty
Describe the bug
pandoc's pipeline tables are rendered with the colons after the header.
Moreover, if the table is the first thing in the document, its horizontal line above the header is not rendered at all.
Example:
| **Holiday n. 1** |            |
|:-----------------|:-----------|
| Start            | 2024-06-03 |
| End              | 2024-06-18 |
| Accounting       | 2024-06-25 |

| **Holiday n. 2** |            |
|:-----------------|:-----------|
| Start            | 2024-06-03 |
| End              | 2024-06-18 |
| Accounting       | 2024-06-25 |

Screenshot:

Expected behavior
Tables should be rendered without the colons that describe the alignment (and correct alignment of the columns) and the first table should be rendered with the first line above its header
Healthcheck output (:checkhealth render-markdown)
render-markdown: require("render-markdown.health").check()
markdown.nvim [neovim version] ~

OK Version >= 0.10

markdown.nvim [configuration] ~

OK valid

markdown.nvim [nvim-treesitter] ~

OK installed
OK markdown: parser installed
OK markdown_inline: parser installed
OK latex: parser installed
OK highlights enabled

markdown.nvim [executables] ~

OK latex2text: installed

Additional information
No response

Automatic column alignment will not be done by this plugin.

I mean only visually of course.
The colons signal the column alignment.

I am aware of what the colon signals.
If you want this plugin to take a left aligned column and align it to the right because the colon for the column is on the right side, even "only visually" that will not happen.

Alignment indicators added in this commit: https://github.com/MeanderingProgrammer/markdown.nvim/commit/a27303384570b85ee4538fa5f30eb418fef01ec7, which replace the colons.
Have a todo to maybe handle column alignment but I'll track separately.
Please update and LMK what ya think.

Interesting, here is the new rendering of the example for reference:


ng* pass through attributes don't seem to be working

I have a basic sign up page with AngularFaces, BootsFaces and Primefaces in a jsf application. I am trying to use the ng-show/hide attributes to manipulate visibility of page elements based on values in others however even with simplest form (ng-show="false") this is not working. All elements are still being rendered. Auto labels are working. My setup process was to edit pom.xml to add AngularFaces dependencies, edit web.xml to add context-param as instructed and then try ng-show in page. Adding ng-app attribute to html element does not help.

Is this working for anyone else? Would want a working case to help in troubleshooting my setup

First of all, I'm sorry for answering late. I suppose you added the AngularTagDecorator to the web.xml? If you, you might try to set a breakpoint in line 322. Is the if block ever reached? It is responsible for making the ng-show/hide attribute a pass-through attribute.
			if (a.getLocalName().startsWith("ng-")) {
				// make AngularJS attributes pass-through attributes
				modifiedAttribute = TagAttributeUtilities.createTagAttribute(a.getLocation(), PASS_THROUGH_NAMESPACE,
						a.getLocalName(), a.getLocalName(), modifiedValue);
				hasChanges = true;
			} ```

It does hit that line. Tracing it through further eventually get's me to here generateTagIfNecessary and it hits the else branch of the If statement there. I'm mentioning this because I notice the first 2 conditions call generatePuiHtml which in turn has a reference to the constant PASS_THROUGH_NAMESPACE, while the else doesn't. Not sure if this could be it as I am really not an expert here.

You might be up to something. BTW, thanks for taking the time and debugging! I guess this is the else path you're referring to?
return new Tag(tag.getLocation(), tag.getNamespace(), tag.getLocalName(), tag.getQName(),
						modifiedAttributes);

In theory, this should work, because the namespace has been encoded in the modifiedAttributes attribute, but maybe this is a wrong assumption. It may also depend on your server. Which application server do you use? And which libraries? In particular, do you use MyFaces or Mojarra?

Yep,that's the else line. I'm using myfaces on Websphere Application Server Liberty profile 8.5. I also have Bootsfaces and Primefaces in there.

Using BootsFaces is always a good idea :).

Maybe it's a Websphere problem. A couple of days ago, I've learned that Websphere does a couple of thing differently from, say, Tomcat. Maybe that's the same story here. Currently, I don't have a Websphere server at hand, but maybe I can have a glance at it this week-end.
Until then, I suggest you work-around the problem by using JSF 2.2 pass-through attributes. I've designed AngularFaces to be a more developer-friendly alternative, but at least the verbose standard-approach works :).

OK. Will try that. From what i gather, Tomcat is a few pieces shy of a full J2EE app server and Liberty has the pros of loading only the components you need to support your app so you don't have to roll out a full stack J2EE compliant server to run an app that only needs a subset of the features. The con seems to be that you get some quirky behavior at times from IBM stuff. Any recommendations for a good and lightweight J2EE app server?

TomEE? Wildfly? But truth to tell, as far as I know there's nothing wrong with WAS Liberty. Quite the contrary, I like the OSGI concept it's built upon. It's just that these innovative concepts make it difficult to provide frameworks compatible to every application server :).

I looked up doing the JSF pass through. Getting the following error. Can't find facelet tag library for uri http://java.sun.com/jsf/passthrough

I've been thinking all day about this. I believe something's wrong with out project setup. I've tried to investigate which version of JSF IBM WAS liberty 8.5 supports. By the look of it, it's JSF 2.0 - but not JSF 2.2. That's why AngularFaces doesn't work properly. See http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_config_jsf22.html on how to update to JSF 2.2.

I'm using the webProfile-7.0 feature which includes jsf 2.2. See link below.
https://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.wlp.doc/ae/rwlp_feature_webProfile-7.0.html
Deron Spencer
On Fri, Feb 19, 2016 at 2:46 PM, Stephan Rauh<EMAIL_ADDRESS>wrote:

I've been thinking all day about this. I believe something's wrong with
out project setup. I've tried to investigate which version of JSF IBM WAS
liberty 8.5 supports. By the look of it, it's JSF 2.0 - but not JSF 2.2.
That's why AngularFaces doesn't work properly. See
http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_config_jsf22.html
on how to update to JSF 2.2.
—
Reply to this email directly or view it on GitHub
https://github.com/stephanrauh/AngularFaces/issues/68#issuecomment-186374345
.

OK. I've installed a IBM WAS liberty server in my Eclipse. Would you mind to upload your project (i.e. on GitHub) or send me a zip file of your project so I can easily reproduce your issue?
Thanks in advance
Stephan

Can send you a zip file. Let me know where to send it.
Thanks

Hi Globalyst,
Please send it to webmaster1 at beyondjava.de (the " at " being an @ - I don't like spam :) ).
Cheers
Stephan

Am 19.02.2016 um 23:49 schrieb theglobalyst<EMAIL_ADDRESS>Can send you a zip file. Let me know where to send it.
Thanks
—
Reply to this email directly or view it on GitHub.

As it turns out, the error was caused by a missing ng-controller declaration. I'll add the need to improve the documentation into the backlog of the project, and consider the ticket closed.


Increase min-version of react/http

[x] Bug fix?
[ ] New feature?
[x] BC breaks?
[ ] Tests added?
[ ] Docs added?

Deployer\Executor\Server uses React\Http\HttpServer, but that class is only available in react/http:^1.5, therefore I changed the min-requirement

Looks like .lock file is out of sync.
Updated myself. Thanks!

Sorry, did edit the composer.json directly here in github ... Thanks for fixing!


Temporarily disable testFCMAutoInitEnabled

This should be disabled to make Travis pass.
Tracked in #4198

This is out of date and passing on master, closing.


[Action Group | Action Button] Focus ring issues.

Description

Focus ring is improperly shaped when Action Button is used within a Compact Action Group.
Steps to reproduce

Go to https://opensource.adobe.com/spectrum-css/actiongroup.html#horizontalcompact
Tab through the compact action group.
See rounded corners on the Action Buttons in the middle of the group that have square corners.
Make one of the buttons "emphasized"
See this persists in the "distant" focus ring.

Expected behavior
The focus ring's border radius should relate to that of the item under focus.

Fixed in https://github.com/adobe/spectrum-css/pull/1368 and released with<EMAIL_ADDRESS>