scaffolding command fail

hello i'm trying to use scaffolding feature but unfortunatelly something goes wrong:
scenario:
trying scaffolding from database SqlExpress on MVC6  web site
installed package
"EntityFramework.SqlServer": "7.0.0-beta7",
"EntityFramework.Commands": "7.0.0-beta7",
"EntityFramework.SqlServer.Design": "7.0.0-beta7"
command from powershell
dnx ef dbcontext scaffold "Data Source=.\sqlexpress;Initial Catalog=FT360.DB;Integrated Security=False;User ID=sa;Password=xxx;Connect Timeout=60;Encrypt=False;TrustServerCertificate=False;ApplicationIntent=ReadWrite;MultiSubnetFailover=False" EntityFramework.SqlServer
Error:
[ERROR] dnx : System.InvalidOperationException: Instance failure.
[ERROR] At line:1 char:1
[ERROR] + dnx ef dbcontext scaffold "Data Source=.\sqlexpress;Initial Catalog= ...
[ERROR] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ERROR]     + CategoryInfo          : NotSpecified: (System.InvalidO...stance failure.:String) [], RemoteException
[ERROR]     + FullyQualifiedErrorId : NativeCommandError
[ERROR]
[ERROR]    at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean
[ERROR] ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boole
[ERROR] an integratedSecurity, Boolean withFailover, SqlAuthenticationMethod authType)
[ERROR]    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword,
[ERROR] SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
[ERROR]    at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword,
[ERROR] SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions,
[ERROR] SqlCredential credential, TimeoutTimer timeout)
[ERROR]    at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString
[ERROR] connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean
[ERROR] redirectedUserInstance)
[ERROR]    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString
[ERROR] connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString
[ERROR] newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData
[ERROR] reconnectSessionData, DbConnectionPool pool, String accessToken)
[ERROR]    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey
[ERROR] poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions
[ERROR] userOptions)
[ERROR]    at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection
[ERROR] owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
[ERROR]    at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions
[ERROR] userOptions, DbConnectionInternal oldConnection)
[ERROR]    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions
[ERROR] userOptions, DbConnectionInternal oldConnection)
[ERROR]    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32
[ERROR] waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions
[ERROR] userOptions, DbConnectionInternal& connection)
[ERROR]    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1  [ERROR] retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) [ERROR]    at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection,  [ERROR] TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection,
[ERROR] DbConnectionInternal& connection)
[ERROR]    at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection,
[ERROR] DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) [ERROR]    at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection,  [ERROR] DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
[ERROR]    at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry) [ERROR]    at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry)
[ERROR]    at System.Data.SqlClient.SqlConnection.Open()
[ERROR]    at Microsoft.Data.Entity.SqlServer.Design.ReverseEngineering.SqlServerMetadataModelProvider.LoadMetadataFromData
[ERROR] base(String connectionString)
[ERROR]    at Microsoft.Data.Entity.SqlServer.Design.ReverseEngineering.SqlServerMetadataModelProvider.ConstructRelationalM
[ERROR] odel(String connectionString)
[ERROR]    at Microsoft.Data.Entity.Relational.Design.ReverseEngineering.ReverseEngineeringMetadataModelProvider.GenerateMe
[ERROR] tadataModel(String connectionString)
[ERROR]    at Microsoft.Data.Entity.Relational.Design.ReverseEngineering.ReverseEngineeringGenerator.GetMetadataModel(IData
[ERROR] baseMetadataModelProvider provider, ReverseEngineeringConfiguration configuration)
[ERROR]    at Microsoft.Data.Entity.Relational.Design.ReverseEngineering.ReverseEngineeringGenerator.d__25.M
[ERROR] oveNext()
[ERROR] --- End of stack trace from previous location where exc
[ERROR] eption was thrown ---
[ERROR]    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[ERROR]    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[ERROR]    at Microsoft.Data.Entity.Commands.Program.d__16.MoveNext()
[ERROR] --- End of stack trace from previous location where exception was thrown ---
[ERROR]    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[ERROR]    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[ERROR]    at Microsoft.Data.Entity.Commands.Program.<>c__DisplayClass9_4.<b__11>d.MoveNext()
[ERROR]

Afaik an Instance Failure normally means it can't connect to your database. Make sure your connection string is correct.

@lucadibiagio was it an invalid connection string?

Only register proposer... To me, works changes "\" on string connection to "":
EG
<add name="DefaultConnection" connectionString="Server=localhost\SQLEXPRESS...
rather then
<add name="DefaultConnection" connectionString="Server=localhost\SQLEXPRESS...
Source: https://stackoverflow.com/questions/36084770/entity-framework-core-use-windows-service


fix: rollup watch crash on Windows

Description
Potential fix for #13234. We may not be able to apply this fix until Vite 5 though. Credits go to @sapphi-red for discovering the issue.

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Could the fix be in here instead to skip public files?
https://github.com/vitejs/vite/blob/e3db7712657232fbb9ea2499a2c6f277d2bb96a3/packages/vite/src/node/plugins/ensureWatch.ts#L7-L17

I was going to check if this is an intended behavior to rollup and forgot to do that 😅
I made it now: https://github.com/rollup/rollup/issues/5013

Lukas said this may be fixed in Rollup, so we should check before releasing Vite 5 if we should revert this change: https://github.com/rollup/rollup/issues/5013#issuecomment-1585483765

Hello,
I'm checking with Vite v5.0.0 beta 2 if the error has been fixed but still i see it.
As mentioned in the issues, it is still throwing the error -4082. The fastest way to make it thrown is to create a folder/file in C:.
Do you have the same behavior?


On Spark, Hive, and Small Files: An In-Depth Look at Spark Partitioning Strategies /  Zachary Ennenga @ Airbnb Engineering Blog

URL: https://medium.com/airbnb-engineering/on-spark-hive-and-small-files-an-in-depth-look-at-spark-partitioning-strategies-a9a364f908
Review (1-2 sentences): Millions of small files in HDFS or almost all you want to know about spark partitioning. At least for a start :)

Published in Digest #11


Initial work to switch to tracing

Resolves #2177
cc @taylor1791 (Sorry for the slight delay. Forgot it was Halloween weekend)
This is the initial work to switch from log to tracing
Roadbumps

Tracing does not support dynamic levels or targets for the event!() and enabled!() macros which led to some ugly macros
I couldn't find a proper way for tracing to detect the log level set in log world (e.g. RUST_LOG=debug with env_logger), so both tracing and log are checked for dynamic bits

Worth noting that the log feature of tracing pulls in log anyways, so it doesn't add any extra deps

Future Work
It would probably be worthwhile to have some spans setup for tracking calls throughout the library, but I'll leave that to someone else since life is getting busy again

Does your work include emitting traces that follow the OpenTelemetry db convention? https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/database/
That would just be awesome.

@CosmicHorrorDev do you mind rebasing this please?

@gitmalong I doubt it. I kept the messages as is since the focus of this PR is just to switch the logging framework from log to tracing

@abonander Finished rebasing. Should be good for a review

This looks good! I remember looking into tracing and being annoyed that the level of an event had to be a constant, I'm glad you found a workaround.

log_statements requires log::LevelFilter, maybe a tracing_statements, built-in enum, int, or re-exported enum so an additional dependency isn't required for a single type

From the PR description

I couldn't find a proper way for tracing to detect the log level set in log world (e.g. RUST_LOG=debug with env_logger), so both tracing and log are checked for dynamic bits

Worth noting that the log feature of tracing pulls in log anyways, so it doesn't add any extra deps

I would leave a comment on #2177 instead since that's the pseudo tracking issue for the tracing switch


Refactoring Build pipeline

Continuing https://github.com/actions-runner-controller/actions-runner-controller/pull/1018 here
CI

[x] Use GHA cache for docker buildx cache
[x] Update Makefile if require

Controller container image

[x] Ues tonistiigi/xx for go build
[x] Maintain UPXed slim container image

Others

[ ] Update docs if require

@pratikbalar Hey! Thanks for creating this. I'm not yet convinced to maintain upx variant of our images so if you'd want #1018 to be more likely to be merged I'd suggest you to separate it.

Okay, Will create non UPXed branch separately

https://github.com/actions-runner-controller/actions-runner-controller/pull/1041 non upx dockerfile


fix(interchange): fix unit test to accomodate for quotes

Was seeing issues with executing the test suite - found the regex wasn't accommodating for the quotes.

Hmm, strange was seeing this issue (before my fix) on master:


Bug and conversion error when specifying Initial

Two issues regarding specifying initial. I have already fixed and verified the issue on my computer. Will create a PR soon.

When --initial is specified, a conversion error is thrown.

After fixing issue 1, --probe-initial should be set to false by default. By setting it to true by default, even when the user specifies --initial, the program does not register it and goes ahead with bruteforcing possible initial values.

Thank you very much for fixing this issue!


When deploying a Guaranteed QoS in k8s, Envoy occasionally restarts

my k8s version is 1.28.9，I tried using Envoy versions from 1.17.4 to 1.27.1, but encountered the error "Caught Segmentation fault" in all cases.
The detailed error is as follows:
[2024-12-10 02:10:43.598][180][critical][backtrace] [./source/server/backtrace.h:104] Caught Segmentation fault, suspect faulting address 0x0
2024-12-10T10:10:43.599081709+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
2024-12-10T10:10:43.599087228+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 6637fd1bab315774420f3c3d97488fedb7fc710f/1.27.2/Clean/RELEASE/BoringSSL
[2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #0: [0x7f27578f7320]
2024-12-10T10:10:43.599445995+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x556b85fa1888]
2024-12-10T10:10:43.599467253+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #2: [0x556b86f81087]
2024-12-10T10:10:43.599491208+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #3: [0x556b879b487a]
[2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #4: [0x556b879b3491]
2024-12-10T10:10:43.599539289+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #5: [0x556b85fc4b2b]
2024-12-10T10:10:43.599554492+08:00 [2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #6: [0x556b879e9563]
[2024-12-10 02:10:43.599][180][critical][backtrace] [./source/server/backtrace.h:98] #7: [0x7f275794249a]
I noticed that Envoy retrieves the number of cores from the host machine when starting, which may conflict with Kubernetes' Guaranteed QoS. Could this be the cause of the issue?
I might be able to control the number of worker threads at startup by setting --concurrency, but logically, it would still conflict with Kubernetes.

Hi @hushuai1559, this looks like an Envoy question rather than Emissary-ingress.  Can you pls clarify?

yes,I have moved on to the issues with Envoy, this can be closed.


Issue #51 + #52 + Misc

Fixed Issues #51 and #52 but further styling might be necessary.
Fixed a bug that @pantharshit00 found but got lost in the merge conflict.
The images in cards are now <img> tags instead of the background of a <div>.
Removed whitespace at the top of a printed document.

Thanks @SebastianCApostolescu !


Add IAM user creation script for 1.13+

Script contributed by @timaa2k: https://github.com/dcos/dcos/commit/c5d20500af61e9b0597c3d982760934c051fe383
High-level description
Prior to DC/OS version 1.13 a user could directly be created in ZooKeeper by
utilizing a script dcos_add_user.py
This script is intended to enable the same functionality for DC/OS 1.13+.
This script uses legacy user management to create a user in the IAM service.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
https://jira.mesosphere.com/browse/DCOS-45284
Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ x ] Read the DC/OS contributing guidelines
[ x ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label Ready For Review

@timaa2k thank you for contributing the script. Could you also review this PR please?

Thank you for your comment @jgehrcke ! I have addressed the issues you have pointed out, PTAL.

@jongiddy @jgehrcke @timaa2k PTAL


Upgrade to the latest build system standards

I haven't used this in a long time. Run the tests and examples and figure out what we need to do to upgrade this project to the latest available versions of CMake and Qt6. Most notably, ensure that we are not using any obsolete or deprecated functions and are using the most optimized generation possible.

Conan2 is not letting us do conditional requirements anymore via cmake_find_package. I don't even know if Snake should support Conan anymore. I feel like it would be better to just focus on Qt libraries and deployment.


Cypress doesn't see header with application status in standalone UI

I'm porting Cypress tests to the standalone issue but I'm stuck with our check application block code.
In this block, we check header to make sure application is running:
 cy.get('header').should('contain', appName).and('contain', 'Running');
The thing is that with standalone UI, this header doesn't show up when the test is executed by Cypress.
However it shows up when I use my web browser directly.
With Cypress:

With my web browser:

And this is what I can see in the console:

I use exactly same tools versions with Rancher UI and all is ok. However I've tried with different versions of  Cypress, nodejs, typescript and I still face the issue.
One funny test was to trigger a cypress test targeting rancher UI and when the test is done, I use the cypress session so I navigated to the standalone UI and this time, I was able to see the header with application's status.
I'm not a web dev at all but I can see some location calls in the rancher dashboard code whereas I can not see any call in epinio/backend-ui.
I also tried to add wait calls in my Cypress code but it didn't change something.
It happens on all web browsers ( Electron, Firefox, Chrome).

I just gave it another try with all components in their main version and it stills failing but with another error message:
TypeError: e.self is undefined

As a reminder, I got this message when I click on an application name to go into its details page.

just to mention this issue is a blocker to me, I can not progress on e2e tests for the standalone UI.

Tested successfully with ghcr.io/epinio/epinio-ui:v0.7.1-0.0.2
Cypress can see the header in application details page.
Thanks a lot @richard-cox !


Find in Files extension searching should search project extensions

The Windows front-end has now implemented https://github.com/ganelson/inform-evolution/blob/main/proposals/0017-apps-and-extensions.md, which makes per-project extensions the primary way to use extensions. However, at the moment the Find in Files dialog just searches the (now legacy) shared extensions area under "My Documents\Inform\Extensions".
The Find in Files dialog will be changed to instead search extension sources in the project's extensions, under the project's materials directory.
In addition, there will be a new option to search the generated extension documentation for the project. This will be a new checkox "Extensions" under "Where to look / Documentation".

As of commit af8c3ca9b088050f42a6d12a46493660ba33efcb, the first part of this has been done, in that when searching extensions, all extensions are searched: built-in ones, legacy folder ones, and those in the project's materials folder.


[FEEDBACK] Widgets: DateTime and Weather

For DateTime widget, can we change the name of city?
For example, although I'm using the America/New_York time zone, I do not live in New York. I would like to put the city I live in, but it doesn't have a formal TZ name. Same with America/Chicago, but I would like to be following the time for people living in San Antonio since they have the same time zone. I don't want to change them all; I just want the option (ex. my "Tokyo" tz is fine as-is).
Weather
The daily forecast terms are inconsistently cased. The words visibility, wind, and clouds are not title cased.

Also, thank you so much for the creation of widgets. With this, Dashy has reached basically all my criteria for the perfect dash 😄

Thanks for raising the non-capitalized weather info, I'll get that fixed :)

So with the time zone place names, it's a bit more complicated. I'm currently doing it like this:
I get the time zone, either from what you've specified under options.timeZone, or using your browsers local time zone, like:
getTimeZone() {
  if (this.options.timeZone) return this.options.timeZone;
  return Intl.DateTimeFormat().resolvedOptions().timeZone;
},

which returns something like: Europe/London
Then, to get the city name, I'm just using the time zone name, like:
getCity(timeZone) {
  return timeZone.split('/')[1].replaceAll('_', ' ');
},

The problem is, that there is no way to natively determine a time zone from an arbitrary city, like  San Antonio.
I did look into using a package like kevinroberts/city-timezones, but that would involve either deploying the API and making a network request, or adding 1MB into the bundle size. Both seem a bit over-kill for the simple task.
I guess another option would be to let the user specify a time zone, as well as an arbitrary display name for city.
You can also set hideDate: true, which will hide the top row (both the date and city name). Or if the clock is in it's own section, just setting the section name to your city name.
Anyway, let me know your thoughts, or if you have any other suggestions about a non-complicated implementation

I'd personally like to be able to specify a timezone and then define any other specific value
Something like
timeZone: Europe/London title: *Custom Name Here*

Cool, okay so that's the option I'll go for :)

Since this is still open, I'd like to add another problem (please tell me if I should create a new issue):

The Tokyo time doesn't switch to the next day after midnight.

Sure, thank you, I'll add a fix  to the current branch :)
Am away from home at the moment, so might be a few days, sorry about that.

Forgot to say, but all of the above issues have now been fixed, merged and released in #425 - V 1.9.8 :)

Weather labels are correctly capitalized
Date will update at midnight on the clock
You can set customCityName on the clock


make toggleAttribute match with native signature

Fixes #5364, again.
This solution is needed instead of #5371 as that would break TS definitions for consumers using TS <3.1.
I had to use arguments (unfortunately) because otherwise the function signature does not match the JSDoc, which seems more confusing than a a little arguments check.
This produces correct types which are identical to the native toggleAttribute, while still supporting our third argument behind the scenes in JS.
cc @TimvdLippe
Supersedes and closes #5371

This seems fine to me. @azakus you think this will be okay for internal users?

Any chance we can get this merged?
Also, does anyone know what the plan is for next release so i have a rough idea of when we'll get this? (the next time we tag & npm publish it)

cc @rictic @aomarks do you think this will be okay for internal users?


Write an Expression does not work under Araay of Choices on Multi-Choice

When offering the user a multi-choice question, there seems to be an issue with the '=Write an expression' function. When I select the option next to 'Array of Choices', the window in which to type disappears. It is therefore not possible to write an expression. See attachment for image.

@BellaDunnett Can you include what version of Composer on which platform you are using? Please fill in the provided bug template.

@BellaDunnett Thank you for reporting this issue. We recently merged PR https://github.com/microsoft/BotFramework-Composer/pull/6906 which resolves this issue, and it should be included in our upcoming release.


Removing aura-added classes on ui:button

The ui:button adds unspecified CSS classes. How can I remove them?
My app's source:
<ui:button buttonTitle="Login" label="Login" class="btn btn-link" press="{!c.loginToSf}"/>

Generated HTML source;
<button class="btn btn-link default uiBlock uiButton" title="Login" accesskey="" type="button" data-aura-rendered-by="25:2.a">Login</button>

I don't want the default uiBlock uiButton classes on that button. How can get rid of them?
It looks like this is directly added in the button's source. Can we add an attribute to ui:button which disables the appending these extra classes? Perhaps call that attribute "addThemeClasses" which defaults to "true"?
ui:button source:
<button type="{!v.buttonType}" aura:id="button" class="{!v.class +' '+v.theme+' uiBlock'}" o

I am trying to apply Bootstrap to ui:button, but it is getting overridden withuiButton class.
Is there any way to achieve this?


Move pymcubes to an optional dependency.

Before submitting a pull request (PR), please read the contributing guide.
Please fill out as much of this template as you can, but if you have any problems or questions, just leave a comment and we will help out :)
Description
What is this PR

[ ] Bug fix
[ ] Addition of a new feature
[x] Other

Why is this PR needed?
PyMCubes is a dependency that is only required during atlas generation, and currently doesn't have an ARM package on conda-forge.
Forcing it to be a core dependency results in failed builds when installing via conda-forge, and since it's not needed for registration, we have decided to move it to an optional atlasgen dependency that users will not obtain by default.
After this, we'll need a new PyPI release and then to fix the corresponding conda-forge feedstock PR that will be created.
What does this PR do?
Moves PyMCubes (and other altas-generation only) dependencies to an optional atlasgen dependency group.
References
https://github.com/brainglobe/brainreg/issues/206
How has this PR been tested?
Local pip install -e ..
Is this a breaking change?
Does this PR require an update to the documentation?
Checklist:

[ ] The code has been tested locally
[ ] Tests have been added to cover all new functionality (unit & integration)
[ ] The documentation has been updated to reflect any changes
[ ] The code has been formatted with pre-commit

Should we add other packages that aren't needed for the atlasAPI? Maybe ITK is one?

A quick search of this repo indicates that the following packages are only used in the atlas_generation/ submodule:

loguru
PyMCubes
SimpleITK
tqdm
vedo
xmltodict

Also, we seem to be fetching scikit-image but never actually importing it... so I guess it can just go?

https://github.com/brainglobe/brainglobe.github.io/issues/203


changed the jenkinsfile for telemetry

I just copied the middleware build job. You can monitor the PR build here.
http://<IP_ADDRESS>:8080/job/ULP/job/build/job/telemetry/view/change-requests/job/PR-1/

I'm not getting it
will you please help me in that
and also want to see the Jenkins job setup
On Thu, Feb 23, 2023 at 12:04 AM Tushar @.***> wrote:

I just copied the middleware build job. You can monitor the PR build here.
http://<IP_ADDRESS>:8080/job/ULP/job/build/job/telemetry/view/change-requests/job/PR-1/
—
Reply to this email directly, view it on GitHub
https://github.com/Unified-Learner-Passbook/Telemetry/pull/1#issuecomment-1440582640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5SL2YLKBYSEDMKDSX34HILWYZL3VANCNFSM6AAAAAAVECP5LA
.
You are receiving this because you authored the thread.Message ID:
@.***>


New Release

Could we please have a new release, the current release Android.xml isn't been built correctly, this has been fixed in the master branch.

https://github.com/salesforce-ux/theo/releases/tag/v8.0.0-beta.1


Refactor codebase to async/await - m365 purview retentionlabel until m365 purview threatassessment, Closes #4998

Refactor codebase to async/await - m365 purview auditlog until m365 purview retentioneventtype

m365 purview retentionlabel add
m365 purview retentionlabel get
m365 purview retentionlabel list
m365 purview retentionlabel remove
m365 purview retentionlabel set
m365 purview sensitivitylabel get
m365 purview sensitivitylabel list
m365 purview sensitivitylabel policysettings list
m365 purview threatassessment get

Closes #4998

Thank you for this enhancement! We'll try to review it ASAP!

Looks great @MathijsVerbeeck! Will merge it soon!

Right... i stand corrected @nicodecleyre.
By the way: I've changed one of the error fakes to:
sinon.stub(request, 'delete').rejects(new Error('An error has occurred'));

This is also the way Mathijs does it by the way.

Merged manually, thank you! 👏


Possible problem with type narrowing in react-query version 5.0.0

Describe the bug
I'm testing the new version 5 of react-query and it seems as if the type narrowing of the data is no longer working as expected. Before version 4 the following example would have used TypeScript type narrowing and result in data to be of type string but after upgrading to version 5 it is still string or undefined:
import {useQuery} from '@tanstack/react-query';

const foo = (): string => {
    const {data, isLoading, isError} = useQuery({queryKey: ['foo'], queryFn: () => Promise.resolve('foo')});

    if (isLoading) {
	    return '';
    }

    if (isError) {
	    return '';
    }

    return data;
};

Your minimal, reproducible example
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbwK4GcCmBFJaoE8C+cAZlBCHAOQACMAhgHYp0DGA1gPRRq3MwC0AR2x4KAbgCwAKCnMIjeEQgQ4AXjgAKAJQAuOEyjB6Ac1UA+RFLhW4s+YgAmtOgBo4wFABkIte4aOv3AFEoUihCNVRMYVx1BCEcXABpNFxdAG0KRQgKAF1XeLwAMXpdLTM4AAVSEHc0ADouFAgAGwA3NHVMpQpNfE0JaUlrNyINdy8fP00LSQBIYa4YJCh6SjFLa3wpDatgUfUgkOhphCl560Xl1Yp1oc3tu6tLlbhHOgH8AaA
Steps to reproduce
TypeScript does show a type error when returning data
Expected behavior
data should have type narrowed down to string
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
macOS
Tanstack Query adapter
react-query
TanStack Query version
5.0.0
TypeScript version
5.2.2
Additional context
No response

that's because isLoading now no longer derived from a status, but a derived flag, so this is on purpose. The 3 main states that discriminate data are:

status === 'pending`` or isPending` - we have no data yet
status === 'success' or isSuccess- we have data
status === 'error' or isError- we have an error

in v5, isLoading is the same as isInitialLoading was in v4 - a derived flag that describes that you can display a loader, meaning the query is pending and the fetchStatus is fetching. There are cases where you are in pending state but are not fetching, mainly when the query is enabled: false. It was the most critiqued thing in v4 that a query is "loading" when its disabled, so it's not really "loading".
If you use isPending as the migration guide suggests, you get proper narrowing:
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbwK4GcCmBFJaoE8C+cAZlBCHAOQACMAhgHYp0DGA1gPRRq3MwC0AR2x4KAbgCwAKCnMIjeEQgQ4AXjgAKAJQAuOEyjB6Ac1UA+RFLhW4s+YgAmtOgBo4wFAAU09e4aOv3AFEoUihCNVRMYVx1BCEcXABpNFxdAG0KRQgKAF1XeLwAMXpdLTM4D1IQdzQAOi4UCAAbADc0dUylCk18TQlpSWs3Ig13Lx8-TQtJAEghrhgkKHpKMUtrfCl1q2AR9SCQ6CmEKTnrBaWVijXBja3bqwvluEc6fvx+oA


Feature Request: New Report: Sankeymatic data

It would be cool to (at a minimum) have an exportable, or copyable report that supports graphs like this: https://www.reddit.com/r/ynab/comments/bq7m1i/my_monthly_income_breakdown_used_data_from_ynab/
Chart produced by:  http://sankeymatic.com/build/
The data format is very simple and the info is already available.  I don't think you would be able to put the whole chart in which is why I am requesting the data format instead.  :)
It would be nice to have all the time window options you already support.
The data format is "From/[Amount]/To".
Inflow 1 [$000] Income
Inflow 2 [$000] Income
Inflow N [$000] Income
Income [$000] Category Group 1
Income [$000] Category Group 2
Income [$000] Category Group N
Category Group 1 [$000] Category 1
Category Group 1 [$000] Category 2
Category Group 1 [$000] Category N
Category Group 2 [$000] Category 1
Category Group 2 [$000] Category 2
Category Group 2 [$000] Category N
Category Group N [$000] Category 1
Category Group N [$000] Category 2
Category Group N [$000] Category N
Thank you for considering this.

The current chart library used does support Sankey diagrams: https://www.highcharts.com/demo/sankey-diagram
I did try to fiddle with this before, because I also like to use it. If I have time I will try this again since I have some more insight in YNAB now.

I would try to help but JS is not my language.  :(
If it were C# I would be jumping right in.  I work on backend and API systems, not the UI much at all.

@KeithBarrows This is in the latest release! Enjoy!

Looks realy good.  Was trying to figure out a couple entries and I think I have it now:

Net Gain: More Inflow than Outflow - adds to net worth
Overdraft: More Outflow than Inflow - reduces net worth


chore: update codeowners

Summary of Changes
updates OWNERS.md and adds new codeowners
Tests
n/a
Documentation
n/a
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

cc @dorianj @allisonsuarez for input on CODEOWNERS.md


Results with 3DPW train

Hi, Thanks for the nice project. Is there by any chance you have results/model trained on 3DPW too?

Hi, thanks for your interest! I haven't used 3DPW for training. I think that kind of protocol is now discouraged by the 3DPW authors and the whole dataset should be used for testing.

Hi, yes that makes complete sense. The whole HPE is riddled with models trained on different datasets and different evaluation techniques(for ex: full 3dpw test shows better results than only test set); so its a bit hard to gauge what actually makes a method work. But nonetheless you have a very nice approach.

Hi @isarandi, sorry but one more question. Do you have the MPJPE/PA-MPJPE for 3DHP and MuPoTS for the current models? the paper has it but I guess, it was not trained on the large dataset for them.

I have some new, better models trained on even more datasets. The corresponding paper is already accepted for WACV'23, I'm finalizing the camera ready version.
I can share any type of eval results you need. As there are so many different datasets, eval protocols, eval measures, subsets (like actions), model configurations (backbone, striding, test-time augmentation) etc. it's hard to provide all the numbers, so that page here on Github is just a selection...

Congratulations!!! I'll wait for your paper.


moduleId  is undefined in firefox

I am experiencing this very strange issue: on occasion some modules are not passed through system.setModuleId function and threfore view location failes to load their respective views based on __moduleId__ property. This issue is only relavant to Firefox. In Chrome there's no such issue.

Closing since Durandal has been superseded by Aurelia just shy of four years ago.


Code linter and format with Black and Flake8

Please describe your pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. When linking to an issue, please use refs #... in the description of the pull request.
This PR add python-black as code formatter and flake8 as linter. This resolves issue #40.
Please provide enough information so that others can review your pull request:
As we are all starting working in the app and adding more code, is easier start from the beginning using the same code style and format. As consequence, this will be very useful when reviewing PR's, making git diff's cleaners as well.
Explain the details for making this change. What existing problem does the pull request solve?
To force format style, black was added to the git actions workflow to ensure the format style. As addition, flake8 as added as well as linter to ensure max line length and avoid some errors like syntax error and undefined names. It will run automatically black and flake8 in each PR, and if the new code isn't in agreement with this set of rules will be rejected.

@francescarpi how should we proceed?

This PR is marked as draft because is missing some extra info about how to install and use black during local dev. This information could be add to a wiki or contribution guide?
I would like to have the opinion from @https://github.com/ytturi as well.

Yeah we have yet to decide how to keep the documentation ... so let's wait for it 👍

Hi! Amazing PR!
So I propose to use the wiki to define the style guideline.
https://github.com/GeeksCAT/anem-per-feina/wiki
Feel free to edit it and add the guideline section.
Really good job!

Hi! Amazing PR!
So I propose to use the wiki to define the style guideline.
https://github.com/GeeksCAT/anem-per-feina/wiki
Feel free to edit it and add the guideline section.
Although the contrib file could be a good place, as well.
What do you think @XaviTorello ?
Good job!

I think we could start by adding it to the contribution guide, as a last step before submit the PR. What do you think @francescarpi ?

¨Ñ

Hi! Amazing PR!
So I propose to use the wiki to define the style guideline.
https://github.com/GeeksCAT/anem-per-feina/wiki
Feel free to edit it and add the guideline section.
Although the contrib file could be a good place, as well.
What do you think @XaviTorello ?
Good job!

I think we could start by adding it to the contribution guide, as a last step before submit the PR. What do you think @francescarpi ?

It's ok for me.

@francescarpi May you check my last changes: https://github.com/GeeksCAT/anem-per-feina/pull/51/commits/afdd9cc870bee7ded53a9e5247cf5c4d9008187b
If is not so clear I'm happy to add more information, or fell free to submit changes

@francescarpi May you check my last changes: afdd9cc
If is not so clear I'm happy to add more information, or fell free to submit changes

It looks fine for me

To make things easier to check if code is well formatted before pushing commits, we can now use pre-commit. In one simple command pre-commit run --all, we can run all static analysis and check if code is well formatted. Also we can add more tools if necessary.
As suggested by @ytturi, there is a new file requirements-test.txt which holds the dependencies necessaries only for testing or analyzing the source code. Maybe only a temporary solution as there is the possibility to use poetry, as suggested by @jbagot.
I will make it ready to review. This is only a starting point, which can easily be modified to add more tools or change the current configurations as we move on. What do you think @francescarpi ?

Interesting discussion.
The original flake8 had 120 because Pycharm use this configuration by default. But... black use 88... each editor/library use a custom value...
I prefer 120, because 79.... I understand in the past the monitors had small widht, but today...
If we want to respect PEP8 at 100%, of course we must to use 80. Maybe we can create a poll in slack...

@francescarpi we can create a poll as you suggest. Here is PEP8 documentation about line length: https://pep8.org/#maximum-line-length

@francescarpi we can create a poll as you suggest. Here is PEP8 documentation about line length: https://pep8.org/#maximum-line-length

In the past, when I developed with vim (in terminal) I ever used 80 characters and I had discussions with my company mates. Finally, my company decided to use 120... I know that we should to accomplish the PEP8.
I prefer long lines, so think 100 would the best decisions.
Some teams strongly prefer a longer line length. For code maintained exclusively or primarily by a team that can reach agreement on this issue, it is okay to increase the nominal line length from 80 to 100 characters (effectively increasing the maximum length to 99 characters), provided that comments and docstrings are still wrapped at 72 characters.

@francescarpi For me if perfect set 100 as line length limit. Do you still want do the pool on the slack channel or we go with 100?

@francescarpi For me is fine set 100 as line length limit. Do you still want do the pool on the slack channel or we go with 100?

Hello! I sent the survey and most probably we will apply 100. We wait until tomorrow for fix to 100 and accept the PR. I want to unlock ASAP.
Thanks!


issue converting HEIF grid/overlay to webp

Possible bug
Hello,
I'm facing an issue when trying to convert grid/overlay HEIF images. Not sure if it is a bug or a missing feature or if I'm missing an option.
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
    OS: Linux 5.15 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 18.68 GB / 30.99 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.7.0 - ~/.nvm/versions/node/v18.7.0/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v18.7.0/bin/npm
  npmPackages:
    sharp: ^0.30.7 => 0.30.7

What are the steps to reproduce?
Run the code snippet and see output of grid.webp and overlay.webp
What is the expected behaviour?

Overlay

Grid

Current output

Overlay

Grid

Or an animated webp when using pages: 4. if pages: -1 is used sharp crashes.

Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
const sharp = require('sharp');
const fs = require('fs');

const grid = fs.readFileSync('grid_960x640.heic');
const overlay = fs.readFileSync('overlay_1000x680.heic');

sharp(grid).webp().toFile('grid.webp');
sharp(grid, { pages: 4 }).webp().toFile('grid-animated.webp');
sharp(overlay).webp().toFile('overlay.webp');

// Input buffer has corrupt header: source: bad seek to 97350
// sharp(grid, { pages: -1 }).webp().toFile('grid-animated.webp');

Executing vips copy grid_960x640.heic grid-vips.webp returns the the correct grid image
Executing vips copy overlay_1000x680.heic overlay-vips.webp returns the the correct overlay image
The width/height returned by sharp(grid).metadata() and vipsheader -a grid_960x640.heic is also different.
sharp
{
  format: 'heif',
  width: 480,
  height: 320,
  space: 'srgb',
  channels: 3,
  depth: 'uchar',
  isProgressive: false,
  pages: 5,
  pagePrimary: 4,
  compression: 'hevc',
  hasProfile: false,
  hasAlpha: false
}

vipsheader
width: 960
height: 640
bands: 3
format: uchar
coding: none
interpretation: srgb
xoffset: 0
yoffset: 0
xres: 1
yres: 1
filename: grid_960x640.heic
vips-loader: heifload
heif-primary: 4
n-pages: 5
heif-compression: hevc
heif-bitdepth: 8
vips-sequential: 1

I'm using vips-8.13.0
Please provide sample image(s) that help explain this problem

grid.heif
overlay.heif

Reference: https://nokiatech.github.io/heif/examples.html

Extracting multiple pages/frames from this image is not supported by any version of libvips, due to their differing dimensions.
I see a heifload: not all pages are the same size error when attempting to do this, either via sharp or using vips at the command line.
https://github.com/libvips/libvips/blob/d27dfbe55d9ea571ce5bf3fd4948d3804e3ebacc/libvips/foreign/heifload.c#L794-L809

Extracting multiple pages/frames from this image is not supported by any version of libvips, due to their differing dimensions

libvips supports it, at least partially through vips copy, which outputs the expected result.

These appear to be 5 page images, with pages 0-3 being 480x320 and page 4 being 960x640:
$ heif-info grid_960x640.heic
MIME type: image/heif
main brand: mif1
compatible brands: mif1, heic

image: 480x320 (id=1002)
  color profile: no
  alpha channel: no
  depth channel: no
image: 480x320 (id=1005)
  color profile: no
  alpha channel: no
  depth channel: no
image: 480x320 (id=1008)
  color profile: no
  alpha channel: no
  depth channel: no
image: 480x320 (id=1011)
  color profile: no
  alpha channel: no
  depth channel: no
image: 960x640 (id=1012), primary
  color profile: no
  alpha channel: no
  depth channel: no

vipsheader and vips copy ... are using page 4 by default, whereas sharp uses page 0 by default, so perhaps try:
sharp(grid, { page: 4 }).webp().toFile('grid.webp');

The equivalent of:
sharp(grid, { pages: -1 }).webp().toFile('grid-animated.webp');

is:
$ vips copy grid_960x640.heic[n=-1] grid-animated.webp

which I'd expect to also fail.

sharp(grid, { page: 4 }).webp().toFile('grid.webp');

worked perfectly, so it seems the page that needs to be used by default for heif files is the one in pagePrimary.
$ vips copy grid_960x640.heic[n=-1] grid-animated.webp

Yes, that command fails as well.
Thank you!

Thanks for the update, I've added a note to the documentation about this via commit https://github.com/lovell/sharp/commit/0e3bd46ca36ef10fa708caddfe477f19923fc964


deps: use native url over fast-url-parser

Native url module has seen many improvements since fast-url-parser was selected.
Fixes: https://github.com/Brightspace/node-landlord-client/issues/4

Coverage remained the same at 40.613% when pulling 46a5a7a75134d515e867cfc425268053f564d5a7 on omsmith:use-native-url into 8d0467893e362bb86ffb6502b56a23e3d323d3f6 on Brightspace:master.


[Task] Support for Kubernetes Service Discovery

Description
Background
Apache ShenYu is a Java native API Gateway for service proxy, protocol conversion and API governance. Currently, ShenYu has good usability and performance in microservice scenarios. However, ShenYu's support for Kubernetes is still relatively weak.
Tasks

Support the registration of microservices deployed in K8s Pod to shenyu-admin and use K8s as the register center.
Discuss with mentors, and complete the requirements design and technical design of Shenyu K8s Register Center.
Complete the initial version of Shenyu K8s Register Center.
Complete the CI test of Shenyu K8s Register Center, verify the correctness of the code.
Write the necessary documentation, deployment guides, and instructions for users to connect microservices running inside the K8s Pod to ShenYu

Relevant Skills

Know the use of Apache ShenYu, especially the register center
Familiar with Java and Golang
Familiar with Kubernetes and can use Java or Golang to develop

Task List
No response

I'm very interested in this IDEA! I implemented ShenYu Helm Chart from zero to one in GLCC, making ShenYu simple to deploy in Kubernetes. I'm really looking forward to progressing with ShenYu on the cloud-native side, from deploying ShenYu itself to supporting Kubernetes services. 🚀

Same isue. I'm just using Kubernetes Service to dispath request to some pod, not using any register service like nacos, consul, eureka etc. When I start bootstrap service in Kubernetes, it failed with error "Parameter 0 of method nacosDiscoveryHealthIndicator in com.alibaba.cloud.nacos.endpoint.NacosDiscoveryEndpointAutoConfiguration required a bean of type 'com.alibaba.cloud.nacos.NacosServiceManager' that could not be found.", I've already disabled spring.cloud.discovery.
configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: $APP_NAME
data:
  application.yml: |
    server:
      port: 9195
      address: <IP_ADDRESS>
    logging:
      level:
        root: info
        org.springframework.boot: info
        org.apache.ibatis: info
        org.apache.shenyu.bonuspoint: info
        org.apache.shenyu.lottery: info
        org.apache.shenyu: info
    spring:
      application:
        name: opengateway
      main:
        allow-bean-definition-overriding: true
        allow-circular-references: true
      codec:
        max-in-memory-size: 2MB
      cloud:
        discovery:
          enabled: false
    management:
      endpoints:
        web:
          exposure:
            include: "health,metrics,prometheus"
      # 非 Kubernetes 环境也开启健康探针，以便本地调试
      endpoint:
        health:
          probes:
            enabled: true
      # 只对 Kubernetes 环境有效
      health:
        readinessstate:
          enabled: true
        livenessstate:
          enabled: true
      metrics:
        tags:
          application: basicai-opengateway
    shenyu:
      sync:
        websocket:
          urls: ws://opengateway-admin:9095/websocket
          allowOrigin: ws://opengateway:9195

deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  name: $APP_NAME
spec:
  replicas: 2
  selector:
    matchLabels:
      app.kubernetes.io/name: basicai
      app.kubernetes.io/instance: basicai
      app.kubernetes.io/component: $APP_NAME
  template:
    metadata:
      labels:
        app.kubernetes.io/name: basicai
        app.kubernetes.io/instance: basicai
        app.kubernetes.io/component: $APP_NAME
    spec:
      nodeSelector:
        dedicated: app
      # 提前准备好拉取镜像的凭证
      imagePullSecrets:
      - name: basicai-registry
      containers:
      - name: $APP_NAME
        image: $IMAGE
        resources:
          requests:
            memory: 200Mi
            cpu: 10m
          limits:
            memory: 2Gi
            cpu: 1
        ports:
        - name: http
          containerPort: 9195
        # 启动探针，会尝试多次，如果失败将重启服务
        startupProbe:
          httpGet:
            path: /actuator/health/liveness
            port: 9195
          periodSeconds: 10
          failureThreshold: 6
        # 存活探针，会尝试多次，如果失败将重启服务
        livenessProbe:
          httpGet:
            path: /actuator/health/liveness
            port: 9195
          periodSeconds: 10
          failureThreshold: 3
        # 就绪探针，如果失败将拒绝服务
        readinessProbe:
          httpGet:
            path: /actuator/health/readiness
            port: 9195
          initialDelaySeconds: 10
          periodSeconds: 10
        volumeMounts:
          - name: config
            subPath: application.yml
            mountPath: /opt/shenyu-bootstrap/conf/application.yml
      volumes:
        - name: config
          configMap:
            name: $APP_NAME
---
apiVersion: v1
kind: Service
metadata:
  name: $APP_NAME
spec:
  selector:
    app.kubernetes.io/name: basicai
    app.kubernetes.io/instance: basicai
    app.kubernetes.io/component: $APP_NAME
  ports:
    - name: http
      port: 80
      targetPort: 9195
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
  name: $APP_NAME
spec:
  ingressClassName: nginx
  rules:
    - host: open.alidev.beisai.com
      http:
        paths:
          - backend:
              service:
                name: $APP_NAME
                port:
                  number: 80
            path: /api(/|$)(.*)
            pathType: Prefix
  tls:
  - hosts:
    - open.alidev.beisai.com
    secretName: alidev.beisai.com

logs
Use default jvm options:  -server -Xmx2g -Xms2g -Xmn1g -Xss512k -XX:+DisableExplicitGC   -XX:LargePageSizeInBytes=128m -XX:+UseFastAccessorMethods  -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseCMSInitiatingOccupancyOnly  -XX:CMSInitiatingOccupancyFraction=70
Starting the Apache ShenYu Bootstrap ...
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/shenyu-bootstrap/lib/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/shenyu-bootstrap/lib/tencentcloud-cls-sdk-java-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
08:43:56,035 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
08:43:56,035 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/opt/shenyu-bootstrap/conf/logback.xml]
08:43:56,308 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
08:43:56,310 |-INFO in ch.qos.logback.core.joran.action.ShutdownHookAction - About to instantiate shutdown hook of type [ch.qos.logback.core.hook.DelayingShutdownHook]
08:43:56,323 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener]
08:43:56,420 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
08:43:56,426 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
08:43:56,435 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
08:43:56,531 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
08:43:56,534 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNC_STDOUT]
08:43:56,536 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT]
08:43:56,536 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Attaching appender named [STDOUT] to AsyncAppender.
08:43:56,537 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Setting discardingThreshold to 0
08:43:56,538 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
08:43:56,538 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNC_STDOUT] to Logger[ROOT]
08:43:56,539 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
08:43:56,540 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@1efee8e7 - Registering current configuration as safe fallback point
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
08:43:58,500 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Worker thread will flush remaining events before exiting.
08:43:58,501 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Queue flush finished successfully within timeout.
08:43:58,511 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
08:43:58,512 |-INFO in ch.qos.logback.core.joran.action.ShutdownHookAction - About to instantiate shutdown hook of type [ch.qos.logback.core.hook.DelayingShutdownHook]
08:43:58,512 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener]
08:43:58,512 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
08:43:58,512 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
08:43:58,513 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
08:43:58,514 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
08:43:58,514 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNC_STDOUT]
08:43:58,515 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT]
08:43:58,515 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Attaching appender named [STDOUT] to AsyncAppender.
08:43:58,515 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC_STDOUT] - Setting discardingThreshold to 0
08:43:58,515 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
08:43:58,516 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[ROOT] onto the JUL framework
08:43:58,517 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNC_STDOUT] to Logger[ROOT]
08:43:58,517 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
08:43:58,517 |-INFO in org.springframework.boot.logging.logback.SpringBootJoranConfigurator@3adcc812 - Registering current configuration as safe fallback point
08:43:58,607 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[org.springframework.boot] onto the JUL framework
08:43:58,608 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[org.apache.ibatis] onto the JUL framework
08:43:58,608 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[org.apache.shenyu.bonuspoint] onto the JUL framework
08:43:58,608 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[org.apache.shenyu.lottery] onto the JUL framework
08:43:58,608 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@66c61024 - Propagating INFO level on Logger[org.apache.shenyu] onto the JUL framework
2023-04-27 08:43:58 [main] INFO  org.apache.shenyu.web.logo.ShenyuLogo -

   _____ _
  / ____| |
 | (___ | |__   ___ _ __  _   _ _   _
  \___ \| '_ \ / _ \ '_ \| | | | | | |
  ____) | | | |  __/ | | | |_| | |_| |
 |_____/|_| |_|\___|_| |_|\__, |\__,_|
                           __/ |
                          |___/
 :: Shenyu :: (v2.5.1)

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.6.8)

2023-04-27 08:43:59 [main] INFO  org.apache.shenyu.bootstrap.ShenyuBootstrapApplication - Starting ShenyuBootstrapApplication v2.5.1 using Java 1.8.0_212 on opengateway-88cd7bb46-fdb8x with PID 1 (/opt/shenyu-bootstrap/lib/shenyu-bootstrap-2.5.1.jar started by root in /opt/shenyu-bootstrap)
2023-04-27 08:43:59 [main] INFO  org.apache.shenyu.bootstrap.ShenyuBootstrapApplication - No active profile set, falling back to 1 default profile: "default"
2023-04-27 08:44:03 [main] INFO  org.springframework.data.repository.config.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
2023-04-27 08:44:03 [main] INFO  org.springframework.data.repository.config.RepositoryConfigurationDelegate - Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2023-04-27 08:44:03 [main] INFO  org.springframework.data.repository.config.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 12 ms. Found 0 Redis repository interfaces.
2023-04-27 08:44:05 [main] INFO  org.springframework.cloud.context.scope.GenericScope - BeanFactory id=ee8f65ba-1d25-3ea6-ae2a-db7fefcf8a8d
2023-04-27 08:44:05 [main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'com.baidu.cloud.starlight.springcloud.client.StarlightClientAutoConfiguration' of type [com.baidu.cloud.starlight.springcloud.client.StarlightClientAutoConfiguration$$EnhancerBySpringCGLIB$$d4b4e3df] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-27 08:44:05 [main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-27 08:44:05 [main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-27 08:44:05 [main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'reactorDeferringLoadBalancerExchangeFilterFunction' of type [org.springframework.cloud.client.loadbalancer.reactive.DeferringLoadBalancerExchangeFilterFunction] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-27 08:44:10 [main] WARN  com.netflix.config.sources.URLConfigurationSource - No URLs will be polled as dynamic configuration sources.
2023-04-27 08:44:10 [main] INFO  com.netflix.config.sources.URLConfigurationSource - To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2023-04-27 08:44:10 [main] WARN  com.netflix.config.sources.URLConfigurationSource - No URLs will be polled as dynamic configuration sources.
2023-04-27 08:44:10 [main] INFO  com.netflix.config.sources.URLConfigurationSource - To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2023-04-27 08:44:11 [main] WARN  org.springframework.boot.web.reactive.context.AnnotationConfigReactiveWebServerApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webHandler' defined in class path resource [org/apache/shenyu/springboot/starter/gateway/ShenyuConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.shenyu.web.handler.ShenyuWebHandler]: Factory method 'shenyuWebHandler' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'redirectPlugin' defined in class path resource [org/apache/shenyu/springboot/starter/plugin/redirect/RedirectPluginConfiguration.class]: Unsatisfied dependency expressed through method 'redirectPlugin' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dispatcherHandler' defined in class path resource [org/apache/shenyu/springboot/starter/gateway/ShenyuConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthEndpointWebFluxHandlerMapping' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointReactiveWebExtensionConfiguration$WebFluxAdditionalHealthEndpointPathsConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.reactive.AdditionalHealthEndpointPathsWebFluxHandlerMapping]: Factory method 'healthEndpointWebFluxHandlerMapping' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Unsatisfied dependency expressed through method 'healthEndpoint' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthContributorRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthContributorRegistry]: Factory method 'healthContributorRegistry' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'nacosDiscoveryHealthIndicator' defined in class path resource [com/alibaba/cloud/nacos/endpoint/NacosDiscoveryEndpointAutoConfiguration.class]: Unsatisfied dependency expressed through method 'nacosDiscoveryHealthIndicator' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.alibaba.cloud.nacos.NacosServiceManager' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
2023-04-27 08:44:11 [main] INFO  org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener -

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2023-04-27 08:44:12 [main] ERROR org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method nacosDiscoveryHealthIndicator in com.alibaba.cloud.nacos.endpoint.NacosDiscoveryEndpointAutoConfiguration required a bean of type 'com.alibaba.cloud.nacos.NacosServiceManager' that could not be found.

Action:

Consider defining a bean of type 'com.alibaba.cloud.nacos.NacosServiceManager' in your configuration.

alreay support ～


Stringify path error

We want to know what the object path is here.

Let's see if we can swap it or not.


Mutants in controller functions mapped by swagger-express-mw always survive

Summary
The package swagger-express-mw adds a middleware to an express app with an OpenAPI specification (swagger.yml), which allows to map operations to controller functions inside the swagger file.
These may be successfully tested in an integration test with Mocha using the package supertest. However, even though tests succeed and fail as expected when mutating the source manually, Stryker always reports all mutants inside the controller as survived.
Expected Behavior
The mutant StringLiteral deleting the value in the object sent in the response to the get request in controller.js should be killed. Mutation score for controller.js is greater than 0.
Observed Behavior
Mutation score for controller.js is 0.
Reproduction Repo
repo on github
Stryker config
module.exports = function(config) {
  config.set({
    mutator: "javascript",
    mutate: [
      'express-app.js',
      'api/controllers/controller.js'
    ],
    packageManager: "npm",
    reporters: ["html"],
    testRunner: "mocha",
    transpilers: [],
    testFramework: "mocha",
    coverageAnalysis: "off"
  });
};

Test runner config
module.exports = {
    spec: ['*.test.js']
}

Stryker environment

<EMAIL_ADDRESS>/home/dev/stryker-issue-reproduction-repo
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
│ ├──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped

+--<EMAIL_ADDRESS>
Test runner environment
# Test command
mocha

Your Environment

software
version(s)

node
13.6.0

npm
6.13.4

Operating System
Ubuntu MATE 1.20.1

Add stryker.log

stryker.log

Thanks for opening this issue. Could you please add a small example project that reproduces this issue? That would be very helpful. Can be a link to a git repo, or a zip file. Thanks in advance

Sure, it's linked in the post above.

Hi @jzeinert-sap! It seems like the module that you use app-root-path is causing some issues. It registers the root of your repo as the current root instead of the sandbox folder. This causes your umutated sourcecode to be executed instead of the mutated code


KAFKA-10343: Add IBP based ApiVersion tests

Per requirement from KIP-590, we need to add IBP as part of the ApiVersionResponse consideration. All redirected RPCs need to take IBP into consideration when getting a future bump. This PR ensures to remind the developer by doing a hard-coded ApiVersion test to check for any recent RPC version bump.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Merged with https://github.com/apache/kafka/pull/9103


fix a private method name: s/NoExtraBytes/ExtraByte/

Codecov Report

Merging #133 into master will not change coverage.
The diff coverage is 80.00%.

@@           Coverage Diff           @@
##           master     #133   +/-   ##
=======================================
  Coverage   98.29%   98.29%
=======================================
  Files          15       15
  Lines         938      938
  Branches      205      205
=======================================
  Hits          922      922
  Misses         16       16

Impacted Files
Coverage Δ

src/Decoder.ts
99.14% <80.00%> (ø)

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 6d2c4bc...606710e. Read the comment docs.


Installation

Is there a ruby gem for this theme that can be used to install it?
Thanks for your work on this; it's exactly what I was hoping to find.  :)

Hi @kmckee, thanks for your interest to the theme :)
Unfortunately, there is no a ruby gem for it. If you create one I would be glad to promote it in this repo! Cheers


Could not find a version that satisfies the requirement tensorflow==2.11.1 (from versions: 2.13.0rc0)

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
v2.13.0-rc0-0-g525da8a93ec 2.13.0-rc0
Custom Code
Yes
OS Platform and Distribution
MacOS 13.3.1
Mobile device
No response
Python version
Python 3.11.3
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
I need to install an older version of tensorflow to use with other libraries, but it appears none are available except for " 2.13.0rc0" - is this because I am on Apple Silicon?
$ pip3 install tensorflow==2.11.1
ERROR: Could not find a version that satisfies the requirement tensorflow==2.11.1 (from versions: 2.13.0rc0)
ERROR: No matching distribution found for tensorflow==2.11.1

From the output, the only versions I can choose from is just "2.13.0rc0"
Standalone code to reproduce the issue
$ pip3 install tensorflow==2.11.1

### Relevant log output

_No response_</details>

That is correct. Compare platforms supported in 2.11.1 and those supported in 2.13.0-rc0