Implement the node API without referencing wallet-new

Description
This PR implements the handlers for the node information and settings API. The update API handlers have not been implemented yet.
Linked issue

Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

I want to visit & know for about NASA if you help me  or support me please...??? Thank you many more ...!!!

Hi @robahub, this isn't the right website. You may want https://www.nasa.gov/

I'll cleanup the dependencies in a new PR


GPII-2077:  Remove local copies of transforms now in infusion...

See GPII-2077 for details.

Just to comment on priorities: this should be reviewed once FLUID-5971 is merged.

FYI, the tests fail at the moment because they explicitly confirm that model deletions are relayed, which they do not seem to be.

Could we fix up the tests to lighten the dependency on testem? It's no longer possible to start them without it

Sorry, please ignore previous comment

Sorry, please unignore the comment :)

Hi, @amb26.  Just to document our chat and the results here:

We discussed the hard requirement on testem.
I updated the package to move the instrumentation and reporting out of the testem component.

This left us with the requirement to instrument the code before opening the test fixtures.  I tried adding this as a postinstall step, but typically enough, even though this is only an npm run call, it only works within the package itself.  The failure blocks installing gpii-binder as a dependency.  I have removed the postinstall step and updated the README to indicate that npm run instrument must be run before you can use the tests outside of testem.  I hope this will be enough.

Not sure I get it - isn't the postinstall step only required in order to build instrumentation for test fixtures? Why would the absence of this block installing gpii-binder as a dependency? We should try hard to make sure that all projects conform to standard expectations that "npm install" will bring them into a condition where tests can be run immediately

You may like to consult a strategy applied by @cindyli in order to get a postinstall "browserify" step to run, following the pattern you suggested for the in-browser DataSources: https://github.com/cindyli/universal/blob/GPII-1274/scripts/browserifyTestDependency.js#L34

Also, your "instrumentation by default" strategy makes the resulting test cases impossible to debug - please consult attached screenshot:

OK, now I squint at it a bit more, "impossible" seems a bit strong ...

In other packages, I can cheat by mounting different content at the same path.  I can see the "instrumented by default" strategy is problematic.  I plan to make a parallel test file and move the instrumentation to "pretest", which is more appropriate.

I was able to come up with a strategy that avoids creating separate files.  Basically, we can remap /src to /instrumented within the testem configuration using their "routes" mechanism.  Thus the files can be opened directly and will also collect coverage data during the test runs.

The new approach is in place, which will hopefully make it easier to look into the deletion relaying concerns (thanks for your help there).

I collapsed the two previous tests into a single "apply a change once, check the results in two places" pattern.  @amb26 is working on the deletion relay fix.

Although I can verify the tests are working, I am seeing spurious test failures with browser disconnects when running testem.  I could use help investigating.  My notes to date:

Happens in yarn and npm, but fails more quickly in npm.
Fails whether or not we use the all-tests page.
Fails whether or not we use the “standard” caseHolder.
All tests fail/hang individually when they are the only thing run, at least using all-tests.

I could use help in confirming whether this is unique to my setup (browser versions, etc.) and continuing the investigation.  My current running theories are that either there is an outright bug in newer versions of testem, or that their QUnit harness has finally moved past the point where it can work with our version of QUnit.

I looked through the commit history to see what version(s) we had before.  I can avoid the disconnects by downgrading to testem 1.9.1, but then the tests hang at the very end after the last line of output.

This (closed) issue in testem's issue tracking seems relevant, at least in giving ideas for tracking it down further.

@amb26, as discussed, we need to confirm whether the intermittent testem failures occur on vagrant and agree (for now) whether having the tests pass in vagrant is adequate to merge this, or whether more research is needed.

I figured out the cause of the "browser undefined disconnected errors".  See GPII-2264 for details.  @amb26, this should be ready for review.


Recast.markWalkableTriangles,

I have found a problem with recast that I cannot seem to figure out how to overcome. I am passing multiple meshes to the Recast.markWalkableTriangles method from a list.
Heres where I found the problem, in Recast.markWalkableTriangles,
https://github.com/ppiastucki/recast4j/blob/cbeaf92ad1b40f23c1b47d5c102f658bcfcac857/recast/src/main/java/org/recast4j/recast/Recast.java#L69
This is calling,
https://github.com/ppiastucki/recast4j/blob/cbeaf92ad1b40f23c1b47d5c102f658bcfcac857/recast/src/main/java/org/recast4j/recast/Recast.java#L77
The problem is that these variables are not the same as those being passed to it from markWalkableTriangles.
int v0, int v1, int v2

They are still set to the previous meshes parameters.
I cant see how this can be. The calling method shows the correct parameters, but then its fragged in the actual method.

Pictures may help.
Prior to method call.
https://imgur.com/a/0KgrWON
After method call.
https://imgur.com/a/tc4L61P

My mistake. Sorry for post.


Add "quickstart" samples.

BigQuery

[x] - sample
[x] - test

Datastore

[x] - sample
[x] - test

Logging

[x] - sample
[x] - test

Pub/Sub

[x] - sample
[x] - test

Storage

[x] - sample
[x] - test

Translate

[x] - sample
[x] - test

For reference:

GoogleCloudPlatform/python-docs-samples#547
GoogleCloudPlatform/ruby-docs-samples#77

How do you want these quickstart.php files organized? I've just been putting them into their own quickstart folder within each product folder, e.g.:
bigquery/
  quickstart/
    composer.json
    composer.lock
    quickstart.php

@tmatsuo PTAL

The quickstarts should follow the same rules as the samples, and rely on the implicitly set project ID, rather than setting it explicitly, as this should be handled by the Client Libraries page.

These sample are for the Client Libraries page, therefore, can you bring back the explicit project IDs? These quickstart samples (which will only be shown on the Client Libraries pages) should be the only ones that use an explicit project ID. All other samples (as in, everything but the quickstart samples) should infer project ID.
p.s. Thanks for writing the tests!
Also, the various quickstart samples (Node.js, Ruby, Python) are nearly identical in terms of variable names, number of executable statement, comments in the code, etc., so if possible, it would be best to keep these PHP versions of those quickstart samples as close to the Node.js, Python, Ruby quickstart samples as possible.
We have specific requests from UX/PM for these samples to look a certain way, use certain comments, etc. I think it's okay for the quickstart samples to be "quirky" (they're only for the Client Libraries pages), meaning they don't follow the exact same conventions as the rest of your samples.
For example:
Node.js
// Your Google Cloud Platform project ID
const projectId = 'YOUR_PROJECT_ID';

// Instantiates a client
const bigqueryClient = BigQuery({ projectId: projectId });

Python
# Your Google Cloud Platform project ID
project_id = 'YOUR_PROJECT_ID'

# Instantiates a client
bigquery_client = BigQuery.Client(project=project_id)

Ruby
# Your Google Cloud Platform project ID
project_id = "YOUR_PROJECT_ID"

# Instantiates a client
gcloud = Google::Cloud new project_id
bigquery_client = gcloud.bigquery

PHP
# Your Google Cloud Platform project ID
$projectId = 'YOUR_PROJECT_ID';

# Instantiates a client
$bigqueryClient = new BigQueryClient([
    'projectId' => $projectId
]);

Yes, they're harder to test with an explicit project ID, but there shouldn't be too many of these types of sample.

Maybe "quickstart" was the wrong label for these samples?

Yeah technically it's still testable with the replace hack...
What's the rationale of having projectIds?

What's the rationale of having projectIds?

@omaray?

My understanding is we would show both with and without the project ID being set, e.g. in the docs:
To instantiate the [PRODUCT] client:

If you need to explicitly set the project ID, you can pass it in like this:

If we do it this way (which I prefer), we can create another quickstart sample for each one create_client_with_project_id.php or something.

We, will just not on the same page. The quickstart samples, shown on Client Libraries pages, will use the explicit project ID. Everywhere else in the docs (the vast majority of samples) will use an implicit project ID.

Hmm, seems strange to recommend doing it two different ways. The docs can cover explicitly setting the project ID, but they should explain when this would be done (when application default credentials span multiple projects) and why.

As for using $bigqueryClient vs $bigquery, this is something we also want to be consistent with our other samples. I can't speak to the other languages, but I think it's more important to be consistent within the language docs than across languages.

I believe this guy is ready for a final look!

LGTM except for one thing. The PHP Cloud Client library does not yet support auto-detecting the project ID, meaning that the user must set the GCLOUD_PROJECT environment variable for these samples to work. The docs will expect that all the user needs to do is gcloud beta auth application-default login. Is much work to make them all use an explicit project ID until the library supports auto-detecting the project ID?

Are composer.lock supposed to be committed to version control?
Also, I'm now seeing a number of files in this PR with changes (or being renamed or something) that are unrelated to the quickstart samples, was that intentional?

@jmdobry
composer.lock is committed to projects but not to dependencies. So this library should contain composer.lock (so the dependencies don't change w/o an explicit update) whereas a dependent library like google-cloud-php should never contain composer.lock
The renames had to happen for the organization of having quickstart not clutter up another sample application. I.e. logging/* became logging/api/* so that the logging sample code is clearly separated.

@tmatsuo PTAL

Can we please keep the branch around until I can update the docs? We don't want them to 404.

@jmdobry should just take a second to update these. I have the change in flight.


NETSDK1094 errors in tests when using .NET 8 RC1 SDK

The following error occurs, for all languages, when running the source-build smoke tests with a .NET 8 RC1 source-built SDK:
Error Message:
System.InvalidOperationException : Failed to execute /vmr/test/Microsoft.DotNet.SourceBuild.SmokeTests/bin/Release/net8.0/.dotnet/dotnet publish --self-contained true -r linux-x64 /p:PublishTrimmed=true /p:PublishReadyToRun=true /bl:/vmr/test/Microsoft.DotNet.SourceBuild.SmokeTests/bin/Release/net8.0/logs/BasicScenarioTests_Console_CSharp-publish-self-contained-linux-x64-trimmed-R2R.binlog -o /vmr/test/Microsoft.DotNet.SourceBuild.SmokeTests/bin/Release/net8.0/projects-202308111856352233/BasicScenarioTests_Console_CSharp/bin/publish
Exit code: 1
MSBuild version 17.8.0-preview-23409-01+a998492eb for .NET
  Determining projects to restore...
/vmr/test/Microsoft.DotNet.SourceBuild.SmokeTests/bin/Release/net8.0/.dotnet/sdk/8.0.100-rc.1.23411.1/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): error NETSDK1094: Unable to optimize assemblies for performance: a valid runtime package was not found. Either set the PublishReadyToRun property to false, or use a supported runtime identifier when publishing. When targeting .NET 6 or higher, make sure to restore packages with the PublishReadyToRun property set to true. [/vmr/test/Microsoft.DotNet.SourceBuild.SmokeTests/bin/Release/net8.0/projects-202308111856352233/BasicScenarioTests_Console_CSharp/BasicScenarioTests_Console_CSharp.csproj]

Stack Trace:
Microsoft.DotNet.SourceBuild.SmokeTests.ExecuteHelper.ValidateExitCode(ValueTuple`3 result, Int32 expectedExitCode)
Microsoft.DotNet.SourceBuild.SmokeTests.DotNetHelper.ExecuteCmd(String args, String workingDirectory, Action`1 processConfigCallback, Nullable`1 expectedExitCode, Int32 millisecondTimeout)
Microsoft.DotNet.SourceBuild.SmokeTests.DotNetHelper.ExecutePublish(String projectName, DotNetTemplate template, Nullable`1 selfContained, String rid, Boolean trimmed, Boolean readyToRun)
Microsoft.DotNet.SourceBuild.SmokeTests.TestScenario.Execute(DotNetHelper dotNetHelper)
Microsoft.DotNet.SourceBuild.SmokeTests.BasicScenarioTests.VerifyScenario(TestScenario scenario)
InvokeStub_BasicScenarioTests.VerifyScenario(Object, Span`1)
System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

This seems related to the changes in https://github.com/dotnet/sdk/pull/34429.
@sbomer - Can you provide some info on this? What's wrong with the way the test is invoking this? It's specifying a valid RID (linux-x64).

Actually, it seems more likely that this is caused by https://github.com/dotnet/sdk/pull/34430.
@TheFrank, @jkotas - The scenario here is that we're building the SDK from source with a non-portable RID: centos.8-x64. We then use that SDK to publish a .NET project with ready-to-run, targeting a RID of linux-x64. That fails with: error NETSDK1094: Unable to optimize assemblies for performance: a valid runtime package was not found. Either set the PublishReadyToRun property to false, or use a supported runtime identifier when publishing. When targeting .NET 6 or higher, make sure to restore packages with the PublishReadyToRun property set to true.
Is this a bug or is it intentional that this no longer works?
This originally repro'd in https://github.com/dotnet/installer/pull/17118. I had to work around it by disabling the tests at https://github.com/dotnet/installer/pull/17118/files#diff-aa29a7c9a653ceed0c4a6c62a2fa3ebd9b854c48ce58bd489b49bfab183ef72aL37-R38. That change would need to be reverted to repro.

Actually, it seems more likely that this is caused by https://github.com/dotnet/sdk/pull/34430.

This changed was coded very defensively to avoid changing any behaviors for non-portable RIDs. I think it is very unlikely that it introduced this issue.

The scenario here is that we're building the SDK from source with a non-portable RID: centos.8-x64. We then use that SDK to publish a .NET project with ready-to-run, targeting a RID of linux-x64.

Can this be related to https://github.com/dotnet/sdk/pull/34279? After this change, there is no association between linux-x64 RID and non-portable RIDs like centos.8-x64 by default. Do the distro builds include any overrides for this default?

Can this be related to dotnet/sdk#34279? After this change, there is no association between linux-x64 RID and non-portable RIDs like centos.8-x64 by default. Do the distro builds include any overrides for this default?

Good find. Yes, that looks to be the cause. Looks like there's some changes that are necessary for source-build.

so https://github.com/dotnet/source-build/issues/3584

@mthalman - Has this issue been resolved now?

@mthalman - Has this issue been resolved now?

Yep. This was essentially a duplicate of https://github.com/dotnet/source-build/issues/3584.


[GHSA-rpr3-cw39-3pxh] jackson-databind before <IP_ADDRESS> vulnerable to unsafe deserialization

Updates

Affected products

👋 This pull request has been marked as stale because it has been open with no activity.  If you do nothing this pull request will be closed eventually by the stale bot. Please see CONTRIBUTING.md for more policy details.


Cythonize cupy

#399

I mistook the issue number . Correctly it is # 399.

I was definitely the issue number . Correctly it is # 399 .

I was definitely the issue number . Correctly it is #399.

Please fix gitignore to ignore compiled files.


feature-gates: update state for 1.26

Signed-off-by: Peter Hunt<EMAIL_ADDRESS>

Since this is for 1.26, please target the dev-1.26 branch
Thank you

/approve

/retitle Tweak documentation for Pod & container stats from CRI

@haircommander is this a PR relevant for this KEP ?

/milestone 1.26

@haircommander is this a PR relevant for this KEP ?

No this is relevant to this one though

Hi @haircommander! This PR needs a doc review by Mon Nov 28th to get this into the release. Please reach out to required SIGs to get their review. Thank you!

@sftim it's not clear to me whether your note is blocking. I could update the docs in the future but I won't have time this evening.

Whenever there is behavior that end users might want to know about it - and this includes alpha features - we should document the behavior. It's rarely enough just to mention the behavior on the feature gates page.
I don't have enough context to be able to say "no end users would want to know about the behavior here"; if that is the case, please explain why and then we can merge this without documenting any behavior.

The reason I filed https://github.com/kubernetes/website/issues/33509 was because the behavior for this aspect of Kubernetes didn't seem to be documented.


Link all talks of a speaker on every of their talks

This can be closed since #87 was merged manually.


feat: add suggestions of reviewers

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


openjpeg_1: disable tests

Motivation for this change
3e5ccd43003c59fd61fd060ab1e4e5839d832e7f broke tests for openjpeg_1 since tests are only properly supported for openjpeg_2 but enabled in versions 1 and 2.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

CC @codyopel @risicle

fixes #65420

Well caught @petabyteboy - WFM, non-nixos x86_64.
Looking back at the original PR, I added this because the list of reverse dependencies for openjpeg was so huge as to make nox-review impractical to run. Which is why I didn't check it. Irony of ironies.

someone already pushed a fix to master https://github.com/NixOS/nixpkgs/commit/fdf08ce5fbffef35971b002e4548fee38da4be43


[BEAM-3750] Remove TestPipeline.covnertToArgs from integration tests

Fix potential integration test failure when using TestPipeline.convertToArgs if type of the option is List or more complex structure.
Instead of fixing the converToArgs function with more magic, we probably want to get this step removed from integration test to make testing clean, understandable and more clear. This results in refactoring few example pipelines.
Changes includes:

In the example pipelines, extract pipeline related code to single function.
Remove TestPipeline.convertToArgs from all integration test. Instead, pass options to pipeline code directly.

Affected ITs:

WordCountIT
WindowedWordCountIT
DebuggingWordCountTest
BigqueryTornadoesIT
WordCountTest (for Apex runner)

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand:

[ ] What the pull request does
[ ] Why it does it
[ ] How it does it
[ ] Why this approach

[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Run Java PostCommit

+R: @lukecwik @alanmyrvold

This is ready for review.
Precommit failed in org.apache.beam.fn.harness.logging.BeamFnLoggingClientTest.testWhenServerHangsUpEarlyThatClientIsAbleCleanup which should not related to the changes in this PR. I'll rebase the branch once before merge.


Unable to load substrate.dev caused by clipboard.min.js in China

the whole site fails to load?
I can download the file and upload it directly, but I would want to understand better what you see on your screen.

@shawntabrizi The site is loaded after fetching script is failed.


Where do I find language data files for 3.02 version

https://github.com/tesseract-ocr/tessdata/releases/tag/3.04.00
On Wed, 21 Dec 2016, 19:04 Suman Dandala<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/charlesw/tesseract/issues/303, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPzyLMBE8213BtOKylilJSeIsX5eFA5ks5rKN1ygaJpZM4LSrOf
.

https://github.com/tesseract-ocr/tesseract/wiki/Data-Files#data-files-for-version-302
https://sourceforge.net/projects/tesseract-ocr-alt/files

All data files .


Timeout waiting for snapshot

Had to throw enough (large) initial query requests to trigger it.
In my case 10 init requests for issue table with 100000 issues.
14:15:31.813 [error] GenServer #PID<0.593.0> terminating
** (stop) exited in: GenServer.call(Electric.ShapeCache, {:wait_for_snapshot, "50159385-1722604526811"}, 5000)
    ** (EXIT) time out
    (elixir 1.17.2) lib/gen_server.ex:1128: GenServer.call/3
    (electric 0.2.4) lib/electric/shapes.ex:16: Electric.Shapes.get_snapshot/2
    (electric 0.2.4) lib/electric/plug/serve_shape_plug.ex:275: Electric.Plug.ServeShapePlug.serve_log_or_snapshot/2
    (electric 0.2.4) lib/electric/plug/serve_shape_plug.ex:1: Electric.Plug.ServeShapePlug.plug_builder_call/2
    (electric 0.2.4) deps/plug/lib/plug/router.ex:246: anonymous fn/4 in Electric.Plug.Router.dispatch/2
    (telemetry 1.2.1) /Users/vbalegas/workspace/electric-next/packages/sync-service/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
    (electric 0.2.4) deps/plug/lib/plug/router.ex:242: Electric.Plug.Router.dispatch/2
    (electric 0.2.4) lib/electric/plug/router.ex:1: Electric.Plug.Router.plug_builder_call/2
    (bandit 1.5.5) lib/bandit/pipeline.ex:124: Bandit.Pipeline.call_plug!/2
    (bandit 1.5.5) lib/bandit/pipeline.ex:36: Bandit.Pipeline.run/4
    (bandit 1.5.5) lib/bandit/http1/handler.ex:12: Bandit.HTTP1.Handler.handle_data/3
    (bandit 1.5.5) lib/bandit/delegating_handler.ex:18: Bandit.DelegatingHandler.handle_data/3
    (bandit 1.5.5) /Users/vbalegas/workspace/electric-next/packages/sync-service/deps/thousand_island/lib/thousand_island/handler.ex:411: Bandit.DelegatingHandler.handle_continue/2
    (stdlib 6.0.1) gen_server.erl:2163: :gen_server.try_handle_continue/3
    (stdlib 6.0.1) gen_server.erl:2072: :gen_server.loop/7
    (stdlib 6.0.1) proc_lib.erl:329: :proc_lib.init_p_do_apply/3
Last message: {:continue, :handle_connection}
State: {%ThousandIsland.Socket{socket: #Port<0.31>, transport_module: ThousandIsland.Transports.TCP, read_timeout: 60000, silent_terminate_on_error: false, span: %ThousandIsland.Telemetry{span_name: :connection, telemetry_span_context: #Reference<0.2444882864.3121348609.34537>, start_time: -576459997808452298, start_metadata: %{telemetry_span_context: #Reference<0.2444882864.3121348609.34537>, parent_telemetry_span_context: #Reference<0.2444882864.3121086471.156515>, remote_address: {127, 0, 0, 1}, remote_port: 50380}}}, %{opts: %{http: [], http_1: [], http_2: [], websocket: []}, plug: {Electric.Plug.Router, [storage: {Electric.ShapeCache.CubDbStorage, %{file_path: "./shapes", db: :shape_db}}, registry: Registry.ShapeChanges, shape_cache: {Electric.ShapeCache, []}, inspector: {Electric.Postgres.Inspector.EtsInspector, [server: Electric.Postgres.Inspector.EtsInspector]}, long_poll_timeout: 20000, max_age: 1, stale_age: 3, allow_shape_deletion: true]}, handler_module: Bandit.InitialHandler, http_1_enabled: true, http_2_enabled: true}}

@robacourt would be nice to produce some graphs after yours new streaming approach.

Before PR:

After PR:

Overall:

way better time-to-first-byte
slightly better overall time-to-transfer, because were essentially pipelining writing into reading.


caravel: catch only ImportError when loading config

As you may want to see the exception raised on at leasts SyntaxError

Coverage remained the same at 82.035% when pulling 497229dd13a29ca2027ad1e1791f938775153b97 on xrmx:nocatchallconfig into 3ee9a68c09750317f20eedd3968e9f36f6da10a1 on airbnb:master.


Security vulnerability [CVE-2021-3918]

Dependency tree:
<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>CVE-2021-3918
I guess it's present<EMAIL_ADDRESS>and<EMAIL_ADDRESS>as well.

thanks for the issue.
I believe node-sass directly requires request*^2.88.0
If the aforementioned request package is the same as this (repo), its been deprecated for the better part of a year and should thus be dropped altogether to solve this problem. In an ideal world.  I'm not familiar enough with these packages myself to know how easy/feasible this would be.

Moving away from request is an option already implemented in node-gyp v8 here - i.e. the clearest success path for node-sass to me looks like upgrading node-gyp from v7 plus any direct usages here in node-sass (as it is also in dependencies at the moment).
However, another option is suggested here too, so it's possible it might get resolved upstream too.

It also looks like others would like to move away from requests: https://github.com/sass/node-sass/issues/3200

is this project still being actively maintained?

Anyone still looking into this issue?
I am also facing the same issue. Latest version of json-schema (0.4.0) is available which has some vulnerability fixes but due to node-sass dependency couldn't upgrade.

is it viable to uninstall node-sass and use sass instead?

for what it's worth, I replaced node-sass with sass, which appears to be more actively maintained, and it "just worked" as a drop in solution:
yarn remove node-sass
yarn add sass
# run your rebuild

is it viable to uninstall node-sass and use sass instead?

@arderyp Yes: https://sass-lang.com/documentation/js-api

yup @pzrq, I already took care of it and it was a breeze :)

Should be resolved when https://github.com/sass/node-sass/pull/3209 is released.

Fixed in 7.0.1.


Identified step 4 in the stars demo

The identification of step 4 was missing.  The step was there, but it
was not called out as a distinct step.

LGTM - Thanks!


Couldn't load lang file

Building from https://github.com/nwg-piotr/nwg-look/commit/8f63328faa3bb83c546b63fa91c7e89c0163bafb
INFO[0000] >>> Loading preferences
INFO[0000] lang: en_AU
ERRO[0000] Couldn't load the basic lang file

Perhaps fallback to C.UTF-8 if en_UK, en_AU et al. are not found?

The "basic lang file" is /usr/share/nwg-look/langs/en_US.json.


e2e flake: TestSuites/Exhaustive/Deploy-cephfs/Subscr/Failover fails

This fails very regularly, so not really a flake, but sticking to the keyword flake.
Failure log looks like so:
--- FAIL: TestSuites/Exhaustive/Deploy-cephfs (0.00s)
  --- FAIL: TestSuites/Exhaustive/Deploy-cephfs/Subscr (852.06s)
    --- PASS: TestSuites/Exhaustive/Deploy-cephfs/Subscr/Deploy (35.59s)
    --- PASS: TestSuites/Exhaustive/Deploy-cephfs/Subscr/Enable (210.49s)
    --- FAIL: TestSuites/Exhaustive/Deploy-cephfs/Subscr/Failover (605.99s)

The failure seems to stem from failover cluster not reporting DataReady, such that the workload can be deployed to the cluster. This happens as per the following logs usually:
2024-09-12T13:14:56.851Z        INFO    controllers.VolumeReplicationGroup      volsync/vshandler.go:385        PVC is not in use by ready pod, not creating RS yet ...   {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "rsSpec": {"protectedPVC":{"namespace":"subscr-deploy-cephfs-busybox","name":"busybox-pvc","protectedByVolSync":true,"storageID":{"id":""},"replicationID":{"id":""},"storageClassName":"rook-cephfs","annotations":{"apps.open-cluster-management.io/hosting-subscription":"subscr-deploy-cephfs-busybox/subscr-deploy-cephfs-busybox","apps.open-cluster-management.io/reconcile-option":"merge"},"labels":{"app":"subscr-deploy-cephfs-busybox","app.kubernetes.io/part-of":"subscr-deploy-cephfs-busybox","appname":"busybox"},"accessModes":["ReadWriteMany"],"resources":{"requests":{"storage":"1Gi"}}}}, "runFinalSync": false}
2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/vrg_volsync.go:121   Not all ReplicationSources completed setup. We'll retry...        {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8b93b-70966f46932e", "State": "primary"}

2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/vrg_volsync.go:480   VolSync PVsRestored is not complete yet for PVC busybox-pvc       {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "State": "primary"}
2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/vrg_volsync.go:480   VolSync ReplicationSourceSetup is not complete yet for PVC busybox-pvc    {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "State": "primary"}
2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/vrg_volsync.go:418   VolSync RS hasn't been setup yet for PVC busybox-pvc      {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "State": "primary"}
2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/volumereplicationgroup_controller.go:1354    Marking VRG ready with replicating reason {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "State": "primary", "reason": "Unused"}
2024-09-12T13:14:56.852Z        INFO    controllers.VolumeReplicationGroup.vrginstance  controller/volumereplicationgroup_controller.go:1320    DataReady {"VolumeReplicationGroup": {"name":"subscr-deploy-cephfs-busybox","namespace":"subscr-deploy-cephfs-busybox"}, "rid": "4745ce1e-01a4-41c8-b93b-70966f46932e", "State": "primary", "subconditions": [{"type":"DataReady","status":"False","observedGeneration":3,"lastTransitionTime":null,"reason":"Progressing","message":"Not all VolSync PVCs are ready"},{"type":"DataReady","status":"True","observedGeneration":3,"lastTransitionTime":null,"reason":"Unused","message":"No PVCs are protected using VolumeReplication scheme"}]}

RS not being setup till there is a pod is fine, but should not get to vote into DataReady. Need to root cause this in the code to understand the behavior and correct the same.
Instances:

https://github.com/RamenDR/ramen/actions/runs/11558180380/job/32169931076
https://github.com/RamenDR/ramen/actions/runs/11558537089/job/32171141061

In this instance:
https://github.com/RamenDR/ramen/actions/runs/11558180380
We have a ceph core dump:
% ls -lh gather.11558180380-1/rdr-dr2/addons/rook/logs/rdr-dr2/core.12
-rw-------@ 1 nsoffer  staff   1.5G Oct 28 18:33 gather.11558180380-1/rdr-dr2/addons/rook/logs/rdr-dr2/core.12

2024-10-28T16:33:13.231+0000 7ffb02ebc640 -1 /home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos
9/MACHINE_SIZE/gigantic/release/19.2.0/rpm/el9/BUILD/ceph-19.2.0/src/common/RefCountedObj.cc: In function 'virtual ceph::common::RefCountedObject::~RefCountedOb
ject()' thread 7ffb02ebc640 time 2024-10-28T16:33:13.224069+0000
/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/19.2.0/rpm/el9/BUILD/ceph-19.2.0/src/common/RefCountedObj.cc: 14: FAILED ceph_assert(nref == 0)

 ceph version 19.2.0 (16063ff2022298c9300e49a547a16ffda59baf13) squid (stable)
 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x12e) [0x7ffb445d2d86]
 2: /usr/lib64/ceph/libceph-common.so.2(+0x182f44) [0x7ffb445d2f44]
 3: /usr/lib64/ceph/libceph-common.so.2(+0x279259) [0x7ffb446c9259]
 4: /usr/lib64/ceph/libceph-common.so.2(+0x3e69cb) [0x7ffb448369cb]
 5: (ceph::common::RefCountedObject::put() const+0x1b2) [0x7ffb446cb182]
 6: ceph-mgr(+0x19da74) [0x559b6ab47a74]
 7: (OpHistoryServiceThread::entry()+0x124) [0x559b6abafa84]
 8: /lib64/libc.so.6(+0x89d22) [0x7ffb43fb0d22]
 9: /lib64/libc.so.6(+0x10ed40) [0x7ffb44035d40]

2024-10-28T16:33:13.235+0000 7ffb02ebc640 -1 *** Caught signal (Aborted) **
 in thread 7ffb02ebc640 thread_name:OpHistorySvc

 ceph version 19.2.0 (16063ff2022298c9300e49a547a16ffda59baf13) squid (stable)
 1: /lib64/libc.so.6(+0x3e730) [0x7ffb43f65730]
 2: /lib64/libc.so.6(+0x8ba6c) [0x7ffb43fb2a6c]
 3: raise()
 4: abort()
 5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x188) [0x7ffb445d2de0]
 6: /usr/lib64/ceph/libceph-common.so.2(+0x182f44) [0x7ffb445d2f44]
 7: /usr/lib64/ceph/libceph-common.so.2(+0x279259) [0x7ffb446c9259]
 8: /usr/lib64/ceph/libceph-common.so.2(+0x3e69cb) [0x7ffb448369cb]
 9: (ceph::common::RefCountedObject::put() const+0x1b2) [0x7ffb446cb182]
 10: ceph-mgr(+0x19da74) [0x559b6ab47a74]
 11: (OpHistoryServiceThread::entry()+0x124) [0x559b6abafa84]
 12: /lib64/libc.so.6(+0x89d22) [0x7ffb43fb0d22]
 13: /lib64/libc.so.6(+0x10ed40) [0x7ffb44035d40]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

I don't see these failures recently, maybe this was a temporary issue with Ceph and fixed in rook by upgrade ceph image.


fix: Remove CVE-2022-21680 vulnerability

Fixes #4684
Description
This PR updates the version of the package gulp and gulp-exec to ^5.0.0 and avoids the CVE-2019-10744 vulnerability with lodash.
Specific Changes

Updated  gulp and gulp-exec to ^5.0.0  in tools.

Testing
The following image shows the lodash version installed after the update.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 84.075%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
20343

Relevant Lines:
22900

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.431%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
20425

Relevant Lines:
22900

💛  - Coveralls


[PowerRename] Fix AltGr input

Summary of the Pull Request
What is this about:
Details here: https://github.com/microsoft/microsoft-ui-xaml/issues/6217#issuecomment-989335005
What is include in the PR:
How does someone test / validate:

Confirm that PowerRename allows AltGr symbols input (e.g. German keyboard layout and AltGr + Q should produce @)
Check that tab navigation is still working

Quality Checklist

[X] Linked issue: #14099
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

/azp run


Use smaller outbox to limit heap usage

With SDK 3.6, we support 8K app messages, which is great for fast file transfers. However, we don't need that large of a buffer for our outgoing URL messages, so limit that to 512 bytes.

Looks good. Thanks for pushing this.


Example of Python code for 2.0?

I wrote a Python script to automate the analysis of sample but since the upgrade to the latest floss PIP module, my script does not work anymore!? Who can share a sample of Python code?
It fails to load to import:
from floss import identification_manager as id_man
from floss import main
from floss import stackstrings
from floss import strings as static

Tx in advance!

Thanks for raising this issue @xme
It looks like FLOSS is in a bit of broken state right now:

vivisect yanked their v0.1.0 release from PyPI so FLOSS v1.7.0 can no longer be installed from there. I'm not sure why this was the case. Any insight @rakuy0?
the master branch on github is in active development, so its not a great idea to install from here.

I will work this week to do another release, probably v1.7.1 that uses a newer version of vivsect thats available on PyPI. Then we can triage your script errors. Will that work for you?

I'm confused. Unless PyPI is doing something weird, I haven't yanked any releases out from PyPI ever. And I can see the release here: https://pypi.org/project/vivisect/0.1.0/, along with the last of the python-2 line (0.2.1) here: https://pypi.org/project/vivisect/0.2.1/. How are you trying to install vivisect and on what python version?
Because I have noticed that pypi will only list the versions of a package that match your current python version. So I tried pip install vivisect==0.1.0 on a python38 instance, and it told me the only options were in the 1.0.x line. But when I switch to a python2 version, then the opposite happens and it tells me only the 0.x.x line is available if I try to pip install 1.0.0.
That being said, installing 0.1.0 via a pip install vivisect==0.1.0 worked on a local python2 instance for me. So a general pip workflow seemed to work? But I also haven't looked at how floss handles vivisect or any of it's versioning.
But in case you can't get to it from PyPI due to pip shenanigans, I do also tag most of the releases on github, so you should be able to git clone the main vivisect repo and checkout the v0.1.0 tag or the v0.2.0 tag.
Or have I missed the mark and you think there's something else going on.

ahh, i bet its because i ran this from py3 so it didn't recognize the py2 releases. PEBKAC. sorry!

@xme  can you share the details of the errors you're encountering?

Tx for the replies...
I can't just load the module...
Ex:
>>> from floss import stackstrings
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'stackstrings' from 'floss' (/opt/fame/env/lib/python3.8/site-packages/floss/__init__.py)

Thanks for raising this issue @xme
It looks like FLOSS is in a bit of broken state right now:

vivisect yanked their v0.1.0 release from PyPI so FLOSS v1.7.0 can no longer be installed from there. I'm not sure why this was the case. Any insight @rakuy0?
the master branch on github is in active development, so its not a great idea to install from here.

I will work this week to do another release, probably v1.7.1 that uses a newer version of vivsect thats available on PyPI. Then we can triage your script errors. Will that work for you?

Tx! Appreciated!

I had the same issue, but I realized that I used pip install floss instead of pip install flare-floss. Both packages import with import floss and at least on my machine floss will be imported instead of flare-floss if both are installed. Installing flare-floss and uninstalling floss fixed my issue.
floss seems to be an empty module.


(iroh-cli)!: Improve cli and configuration file

Description
The configuration file behaviour is improved:

Unknown fields will now cause an error rather than be silently ignored.

Make it possible to express GcPolicy in the TOML config file.  This
was not possible before.  It was possible to disable it before, but
it was disabled by default so that was rather moot.

The --help output is improved:

Update header of iroh.
Directly point to config file docs.
Use consistent style.

Breaking Changes

Unknown fields in the configuration file will now cause an error.

Configuring the GC Policy in the configuration file has changed.

Notes & open questions

Change checklist

[ ] Self-review.
[x] Documentation updates following the style guide, if relevant.
[x] Tests if relevant.
[x] All breaking changes documented.

I'm confused by the PR title. Is it missing a feat or fix prefix?

I'm confused by the PR title. Is it missing a feat or fix prefix?

lol, i forgot how to write PR titles


Implement checkbox input

Hi, I've added checkbox input, check this gif to see how it works

 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.


Shorten import boilerplates by renaming leolib and its files

See Issue #1.

Change leolib to just lib
Remove the lib_ prepend from all of these files

I don't have any formal tests, not even sure how I would do that with a language that has to be run in-game, but I did run through a takeoff routine which makes use of a few of these libraries so I think this is good.


Manage working hours for other users

Delete, add and edit working hours for the users you have workhours management permissions for.
Also, don't show the request button on a user profile if you have create-permissions. The CRUD views should be used instead.

Do we really want to offer edit and delete views for workinghours? not sure if there is a usecase for that as they have to be confirmed anyways

Do we really want to offer edit and delete views for workinghours? not sure if there is a usecase for that as they have to be confirmed anyways

These are meant for people with permissions to manage working hours, not your regular unprivileged user.

Do we really want to offer edit and delete views for workinghours? not sure if there is a usecase for that as they have to be confirmed anyways

These are meant for people with permissions to manage working hours, not your regular unprivileged user.

that's how I understood it anyways. Was just not sure if there is the need for such views, because as a manager, I'd need to grant every workinghour before it is credited. so if there is a misstake or I don't want it, I can simply reject it. not sure in which case I'd want to delete it afterwards


poc

Just to test the zip file conversion.

Thanks @ddvk!
Could you share the .zip or PDF you're using to (not) see the issue?

Thanks! Closing per https://github.com/juruen/rmapi/issues/201


bug: Lots of APIs missing HMR updates

Sphere of influence

useFrontmatter (.md update invalid)
useConfig (needs to be refreshed)
useThemeConfig (reboot required)
usePostList (reboot required)
useCategory (reboot required)
useTag (reboot required)

Now, it works. Will released in v0.13.9.
https://user-images.githubusercontent.com/25154432/214910461-f1419edf-9bc9-47e5-8bbb-368e3f6d2046.mov


Code errors encountered during eval

After training the CMA model, during eval, an error message appeared stating that the file could not be found. I would like to inquire if there are any missing files in the code
FileNotFoundError: [Errno 2] No such file or directory: 'data/connectivity_graphs.pkl'

Hi there,I'd like to ask if you have resolved the problem?I met the same error today.

I have found 'data/connectivity_graphs.pkl' in https://github.com/jacobkrantz/VLN-CE/
Thanks to https://github.com/MarSaKi/ETPNav/issues/11


Update webkit detection, for removing deprecation warning in Chrome.

There are some annoying deprecation warning messages in Chrome. I update some webkit-related checking to avoid this warning messages.

Good change.  But may want to also consider updating the DetectRTC project too, so they don't get out of sync.  Some of the same code is in both.
https://github.com/muaz-khan/DetectRTC


Setting up an environment to work with Google Phishlets

Installation Steps
Update Package Lists
Begin by updating your system’s package lists to ensure you have the latest information on the newest versions of packages and their dependencies.
sudo apt-get update
Install xrandr
xrandr is a utility for managing screen resolutions and display settings.
-- Use this option if you want to run Playwright with Xserver (for example, in MobaXterm) so you can view the browser live.
-- If use "Headless: playwright.Bool(true)," do no need this to install.
sudo apt-get install x11-xserver-utils
Install Google Chrome
-- Use Chrome only if you choose not to use the browsers included in the Playwright app. In the source you received, you don’t need these installations.
Download and install the latest stable version of Google Chrome.
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt-get install -f # Install any missing dependencies
Install Go Programming Language
-- You will need to install the Go language, as the source code is in Go, and to compile it in Linux, you need Go installed.
Go is essential for running Playwright-Go.
wget https://golang.org/dl/go1.20.7.linux-amd64.tar.gz
sudo rm -rf /usr/local/go
sudo tar -C /usr/local -xzf go1.20.7.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin
go version
Install Playwright-Go and Dependencies
-- You need to install the Playwright Go library, as the Evilginx version for Google uses a module called EvilPlaywright. This module controls a real browser behind the reverse proxy to obtain certain tokens that otherwise cannot be retrieved correctly due to the different host in the reverse proxy or due to Google detecting browser incompatibilities with video versions, fonts, etc.
Set up Playwright-Go, which is required for browser automation.
go get -u github.com/playwright-community/playwright-go
go run github.com/playwright-community/playwright-go/cmd/playwright@latest install --with-deps
go install github.com/playwright-community/playwright-go/cmd/playwright@latest
playwright install --with-dep

Warning: This individual is suspected of being a scammer. Do not make any purchases from them without using a secure escrow service or obtaining solid proof that they own the code they are offering for sale.
Please be careful when writing my name on Telegram. Many scammers create profiles similar to mine by altering letters in the username. My only official Telegram profile is https://t.me/blackdatabase. Always double-check the spelling: @B L A C K D A T A B A S E. If the spelling differs, it's not me.
The real developer of this project is [Insert Real Developer's Name or Alias], and they can be contacted directly at [Insert Developer's Contact Info, e.g., email or Telegram handle].
Stay vigilant to avoid fraud, and if you are unsure, confirm the identity before proceeding with any transactions.

Installation Steps
Update Package Lists Begin by updating your system’s package lists to ensure you have the latest information on the newest versions of packages and their dependencies.
sudo apt-get update Install xrandr
xrandr is a utility for managing screen resolutions and display settings.
-- Use this option if you want to run Playwright with Xserver (for example, in MobaXterm) so you can view the browser live. -- If use "Headless: playwright.Bool(true)," do no need this to install.
sudo apt-get install x11-xserver-utils Install Google Chrome
-- Use Chrome only if you choose not to use the browsers included in the Playwright app. In the source you received, you don’t need these installations.
Download and install the latest stable version of Google Chrome.
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo dpkg -i google-chrome-stable_current_amd64.deb sudo apt-get install -f # Install any missing dependencies Install Go Programming Language
-- You will need to install the Go language, as the source code is in Go, and to compile it in Linux, you need Go installed.
Go is essential for running Playwright-Go.
wget https://golang.org/dl/go1.20.7.linux-amd64.tar.gz sudo rm -rf /usr/local/go sudo tar -C /usr/local -xzf go1.20.7.linux-amd64.tar.gz export PATH=$PATH:/usr/local/go/bin go version Install Playwright-Go and Dependencies
-- You need to install the Playwright Go library, as the Evilginx version for Google uses a module called EvilPlaywright. This module controls a real browser behind the reverse proxy to obtain certain tokens that otherwise cannot be retrieved correctly due to the different host in the reverse proxy or due to Google detecting browser incompatibilities with video versions, fonts, etc.
Set up Playwright-Go, which is required for browser automation.
go get -u github.com/playwright-community/playwright-go go run github.com/playwright-community/playwright-go/cmd/playwright@latest install --with-deps go install github.com/playwright-community/playwright-go/cmd/playwright@latest playwright install --with-dep

strange, but I'm not selling this 😂 but I'll post a whole post about you in a couple of hours, mister scammer) I provide everything for free)

Warning: This individual is suspected of being a scammer. Do not make any purchases from them without using a secure escrow service or obtaining solid proof that they own the code they are offering for sale.
Please be careful when writing my name on Telegram. Many scammers create profiles similar to mine by altering letters in the username. My only official Telegram profile is https://t.me/blackdatabase. Always double-check the spelling: @b L A C K D A T A B A S E. If the spelling differs, it's not me.
The real developer of this project is [Insert Real Developer's Name or Alias], and they can be contacted directly at [Insert Developer's Contact Info, e.g., email or Telegram handle].
Stay vigilant to avoid fraud, and if you are unsure, confirm the identity before proceeding with any transactions.

strange, but I'm not selling this 😂 but I'll post a whole post about you in a couple of hours, mister scammer) I provide everything for free)

Installation Steps
Update Package ListsBegin by updating your system’s package lists to ensure you have the latest information on the newest versions of packages and their dependencies.
sudo apt-get update Install xrandr
xrandr is a utility for managing screen resolutions and display settings.
-- Use this option if you want to run Playwright with Xserver (for example, in MobaXterm) so you can view the browser live. -- If use "Headless: playwright.Bool(true)," do no need this to install.
sudo apt-get install x11-xserver-utils Install Google Chrome
-- Use Chrome only if you choose not to use the browsers included in the Playwright app. In the source you received, you don’t need these installations.
Download and install the latest stable version of Google Chrome.
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo dpkg -i google-chrome-stable_current_amd64.deb sudo apt-get install -f # Install any missing dependencies Install Go Programming Language
-- You will need to install the Go language, as the source code is in Go, and to compile it in Linux, you need Go installed.
Go is essential for running Playwright-Go.
wget https://golang.org/dl/go1.20.7.linux-amd64.tar.gz sudo rm -rf /usr/local/go sudo tar -C /usr/local -xzf go1.20.7.linux-amd64.tar.gz export PATH=$PATH:/usr/local/go/bin go version Install Playwright-Go and Dependencies
-- You need to install the Playwright Go library, as the Evilginx version for Google uses a module called EvilPlaywright. This module controls a real browser behind the reverse proxy to obtain certain tokens that otherwise cannot be retrieved correctly due to the different host in the reverse proxy or due to Google detecting browser incompatibilities with video versions, fonts, etc.
Set up Playwright-Go, which is required for browser automation.
go get -u github.com/playwright-community/playwright-go go run github.com/playwright-community/playwright-go/cmd/playwright@latest install --with-deps go install github.com/playwright-community/playwright-go/cmd/playwright@latest playwright install --with-dep

can you elaborate more?

So, my dear bench. It's your time to be a Star. You're accusing me of cheating, don't even buy anything from me, lol. You're funny.   And who are you?! You're just a scammer.

Check out this little boy who uses only offensive words in any dialogue. I was sent information about you that you are blacklisted on top Internet forums. For what?!! you want to ask, for selling your phishlets that don't work.

I have already read the arbitration of your complaints. And the status of a fraudster is exposed to you. Therefore, friends, do not make mistakes, do not contact this character, because then you will simply find yourself blocked in the telegram.

As this character explained, he can create a bunch of new accounts and start selling) in general, be careful. As I said, we do not take money for this project, it was created only on a voluntary basis, so that people would not fall for scammers. He won 't pay for it ! You can do it yourself, there's nothing complicated about writing phishlets or installing a tool.

modified evilginx with gmail available
https://youtu.be/CpR9lA81NzM?si=xy9HFmAg1Z0FTE5z

I have updated my repo with google phishlet, check it out

On Sun, Dec 22, 2024 at 10:04 Evi1Grey5 @.***> wrote:

Closed #1140 https://github.com/kgretzky/evilginx2/issues/1140 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/kgretzky/evilginx2/issues/1140#event-15741240349, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXCOPDBN7ZAIXSRINUQQ4L2G2FB3AVCNFSM6AAAAABR2UB2RKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVG42DCMRUGAZTIOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks so much for the update


candle: init at 1.1

Motivation for this change
I've added an application for controlling GRBL machines, its source can be found at https://github.com/Denvi/Candle
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS v18.09
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@matti-kariluoma, I just realized that this is your first PR here, so I'd like to say thank you for this!
If you need anything clarified, feel free to ask.

I removed candle from my system, made the requested changes then reinstalled. All working!

Looks good - as the last thing, can I get you to squash the commits so we end up with one commit adding you to the maintainer list and another that has all the changes for the actual software?

Looks like I can't resolve the last change request, probably due to the rebase... Do I need to create a new pull request?

Alright, that should be all of the requsted changes. Squashed down to two commits as well

Looks great! Thank you.


Maybe time to drop object-assign?

All modern node versions have Object.assign and/or object spread now.
Apparently since node 4.x.
A quick win could be to finally drop the redundant object-assign dependency and use the native Object.assign. This'd probably mean increasing the minimum node version but 4 is still very old.

Right now the official express middlewares try to target the same Node.js versions as mainline Express.

which is what? still 0.x?
is there a plan anywhere for express to ever move off such old, unsupported versions?

Yes & yes

Don't suppose there's a tracking issue for that? Thanks for the info too.
Hopefully it happens soon


replace redis-async with redis crate

Hi, I've replaced redis-async with redis crate what simplifies some parts of the code and gives new features like Unix socket connection, redis authentication and db selection.
Regards :)
Resolves issues #29, #15 and prs #19, #17.

The change includes breaking changes. cc: @actix/core

i am planing to rewrite actix-redis with service architecture. i am not sure if it is good idea to switch to redis crate

I am not insisting on merging this PR. I did it because I need such functionalities and thought that maybe you will be interested :)
Thx for this crate :)

Hey, we've been migrating this repository into https://github.com/actix/actix-extras so could you re-open this there? Closing for being archived.


History Backup file not found/created?

I don't know if I should put this in requested features or not. I just felt like resetting my smartphone and started creating backups. Despite there being a backup option for this app, seems like it is not doing what I expected, which is creating a history Backup file. Would love it if u can fix/implement? it.

Sorry, found the backup file.
/storage/emulated/0/Download/QN_Backup_{$date}.json


Kotlin MD Builders

Hey there!
I wrote some MD Builders using your library.
I thought that I can add this to your project.
https://github.com/IlyasYOY/kotlin-markdown
Thank you for your work!

Hello! Should I consider preparing a PR or it's a bad idea to add Kotlin Builders in this project?

Hey, sorry for not getting back to you. I checked out your repo when you created the issue, and was a little bit confused to be honest. Maybe that's because I don't use Kotlin myself, but I thought that you could use Java libraries just fine from Kotlin code (without requiring a wrapper like the one you created).
Anyhow, if you feel like this adds value for Kotlin users, please feel free to provide it as a library from your own repo. I would prefer not to include any Kotlin code in my library for simplicity.


Added support for different icons - take 2

Specifically, I wanted to be able to use the fa-twitter-square icon. So added support to just specify the name of the icon. If missing from the configuration, the default is fa-twitter.

Ping...?

Sorry @adi-miller, I layed sick in bed all week. I will review your PR now, thanks for the contribution!

Submitting a new PR with fixes.


Fix column ip_address in table gcp_compute_forwarding_rule for IPv6 CIDR values

Example query results

Results
> select name, ip_address from gcp_compute_forwarding_rule
+------------------------------------+---------------------------------+
| name                               | ip_address                      |
+------------------------------------+---------------------------------+
| gke-cluster-1-e7df1409-95479c15-pe | <IP_ADDRESS>                     |
| test-fr                            | 2600:1900:4000:45f3:8000:1::/96 |
+------------------------------------+---------------------------------+

@karanpopat do other tables with IP address column types need an update?

@misraved i checked, we have one in this table as well - gcp_compute_global_forwarding_rule


[Summer 2021] Implement models and stubs for PyMySQL

Implement stubs and models for MySQL library: PyMySQL
Information on how to add models to Pysa can be found at: https://pyre-check.org/docs/pysa-basics
This might require addition of stubs: https://pyre-check.org/docs/pysa-tips/#stubs

Closed via https://github.com/facebook/pyre-check/commit/a4c40967e61d9196865a7c508cbcac5cb48e7336


Refactor me.rs

Coverage increased (+1.6%) to 82.413% when pulling e64cac4cb5fc605b1dfdf9203cb2d59d54b95863 on KyleSiefring:refactor_me1_review into df5817668c5d72210225c22e6191bf7a2bbec6ca on xiph:master.


11.0 -> 12.0 (auto)

This is auto merge from fedoranvar:12.0-automerge-cbd9d524650b9618b101957b827c3e8bf5f3291a to 12.0

I approve to merge it now


Generic typing for Features, Inputs, and Outputs

Implements generic typing for Features.
Currently, the dynamic typing for Features, Inputs, and Outputs doesn't work well with pyright. There are many # type: ignores in the codebase, such as shown below, to address this. However, a solution that works with pyright is generic typing. With this PR, you can remove these comments and the type checker is still happy. The API for interacting with Features, Inputs, and Outputs remains unchanged,
https://github.com/experimental-design/bofire/blob/0efb4685ce72c163a44e0f1fdc325ce191dda31d/bofire/data_models/strategies/predictives/botorch.py#L198

Ah, this didn't go well. Will fix this!


Fix

https://github.com/mpv-player/mpv/issues/7410

For me mpv -wid %WID was needed.
See https://github.com/ghostlexly/gpu-video-wallpaper/issues/29#issuecomment-1627630701.

I have merged this commit.


OPSEXP-1197 Refactor localhost integration stage config

OPSEXP-1197

I will try to migrate these stages to be driven by molecule only and remove the entire custom code handling in master


feat(core): add JSON scalar support

This is the result of an investigation into how we could implement out of the box JSON scalar support in Graphback.
Things to note:
It works very well in all cases EXCEPT we would only be able to offer very minimal field filtering capabilities on it (in Postgres anyway)
Knex.js does not have an operator for comparing values in a JSON column. Using the query mapper to do so throws an error like this:
select \"id\", \"testObj\" from \"comment\" where \"testObj\" = $1 - operator does not exist: json = unknown.
We could offer very limited filtering on JSON objects:
input GraphbackJSONInput {
   null: Boolean
}

Or else don't give any filtering capabilities on this field. The same idea can be replicated for embedded types also.
Using
To use the JSON scalar, simply add a JSON scalar to your data model:
""" @model """
type Comment {
  id: ID!
  text: String
  description: String
  test: JSON
}

scalar JSON

 createComment(input: {test: {
    some:"some"
    random:"random",
    props:"props"
  }}) {
    test
  }

I've done this quick spike in between issues
Basically we can add JSON scalars easily but there will be problems with filtering (but we can disable filtering on that field or limit it).
Not going to add tests or anything for this yet.

Basically we can add JSON scalars easily but there will be problems with filtering (but we can disable filtering on that field or limit it).

For JSON scalars filtering makes no sense for me. I would expect every scalar work on field level.
Can you propose list of the operations possible on JSON scalar - it could be seen as string right?

Do you plan to use JSONObject scalar as well?

I checked OVP and I think that this stuff is redundant.
First, is feature where we are at code freeze and doing mostly docs and bugfixes.
In all sample apps we already using JSON scalars and they work + filtering is generated automatically.
Tell me like I'm 5 - is that only convenience method - because if it is it might backfire with people getting their JSON scalars (commonly JSONObject) being swapped and getting some issues with arrays.

Can you propose list of the operations possible on JSON scalar - it could be seen as string right?

You would like to be able to to return all items where a JSON field is null/not null.

Are you sure filtering works on JSON fields? I believe the filter will not work.

I can do eq and not eq with full value on Mongo. Kinda leaving postgress at the moment.
If we see this way this is actually an bug - generated filter types for scalars do not work, but I would love to chat about it on issue to see how this spreads across mongo/pg etc.

generated filter types for scalars do not work

I think it is really only for JSON scalars and should work for simpler scalars like BigInt etc.

Also, that is only 2 filter fields for the generated filter type - the others will not work so it is not appropriate to generate these extra filters like lt, gt etc. We need to take control of the JSON scalar.

100% agree. Thanks for explaining

Do you plan to use JSONObject scalar as well?

I did not want to fully implement this yet as this PR is mainly from investigation into how we can add some default scalars. I had checked AppSync though and they only have a AWSJSON scalar:
https://docs.aws.amazon.com/appsync/latest/devguide/scalars.html

I checked this morning how well it would play by naming this scalar GraphbackJSON and also adding a JSON scalar from the template.
""" @model """
type Comment {
  id: ID!
  text: String
  description: String
  test1: JSON
  test: GraphbackJSON
}

scalar GraphbackJSON
scalar JSON # from graphql-scalars

Since both scalars have a real name of "JSON", Graphback will assign them to the single scalar JSON in the generated schema:
type Comment {
  id: ID!
  text: String
  description: String
  test1: JSON
  test: JSON
  note: Note
}

And will use the single scalar in the filters:
input MutateCommentInput {
  id: ID!
  text: String
  description: String
  test1: JSON
  test: JSON
  noteId: ID
}

While in theory both scalars are different implementations of the same result, there could be a divergence in the future, but also there is a greater chance of difference in other scalars like DateTime which is less straightforward.
I see two options:

Bring the code from graphql-type-json (or whichever we decide to use) to gain full control over the scalar. This is actually not a bad idea because we can control changes to its design in the future - but it means more maintenance on us.
Try to rename the scalar dynamically using graphql-compose.

I prefer option 2: it should be straightforward and reduce our maintenance cost.

Vote nr2. Also I wote to use graphql/scalars package as we will need ObjectID exposed as well

Vote nr2. Also I vote to use graphql/scalars package as we will need ObjectID exposed as well

+100

Using graphql-scalars now as of 82504a0f41226e55ebf0f2501c1776ef1f6ebbc6
Although I don't see any difference between JSON and JSONObject right now (in input/output)

I am leaving this in draft, as it is far from final, but is facilitating good discussion and foundations into how we can add default Graphback scalars.

TL;DR JSONObject: {} , JSON: []

TL;DR JSONObject: {} , JSON: []

I know what they are supposed to represent but I am able to insert an array into JSONObject

ROFL :D

I can do eq and not eq with full value on Mongo. Kinda leaving postgress at the moment.

@wtrocki Did you stringify the full value before applying it to the filter?

Closing and can be reopened at a later date if we decide to follow up.


Component Sourcemaps using @import do not sourcemap correctly

Versions
_                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
/ ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
|___/

Angular CLI: 1.7.0-beta.0
Node: 6.11.1
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.1.0
@angular/cli: 1.7.0-beta.0
@angular/material: 5.1.0
@angular-devkit/build-optimizer: 0.0.38
@angular-devkit/core: 0.0.25
@angular-devkit/schematics: 0.0.48
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.10.0-beta.0
@schematics/angular: 0.1.13
@schematics/schematics: 0.0.13
typescript: 2.4.2
webpack: 3.10.0

Repro steps

Step 1 Clone https://github.com/narthur157/sourcemap-bug
Step 2 npm install, then ng serve -sm
Step 3 Inspect the red text
Step 4 Notice how there is a color: red coming from _theming.scss
Step 5: Observe src/app/app.component.scss (where this style comes from)

@import '../variables.scss';

form > p {
    color: red;
}

Step 6: Try removing @import '../variables.scss';
Step 7: Notice how the sourcemap now correctly points to app.component.scss
Observed behavior
Sourcemap points to the imports instead of the actual file.
Desired behavior
Working sourcemap
Mention any other details that might be useful (optional)
This may be an angular bug, but I'm not really sure and, in any case, it affects the user's of angular-cli. I've tried this with different versions of angular-cli with no difference in results. All other sourcemapping tests I tried seem to work, but this quite-common case fails quite often.
Basically I don't have enough knowledge in how exactly the sourcemapping is done to know how to go about fixing this. Also I find the resulting URL odd:

It appends the path to the material import on to the path to the folder of the correct style file

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


feat: LSDV-4832: New Ranker tag [internal PR]

Hi @hlomzik!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/1292

/git merge develop


Have separate examples for create-time variables and deploy-time variables

Is your feature request related to a problem? Please describe.
I was trying to give a tutorial on deploy-time variables and tried to use the package-variables example in this repo to do it, but it was confusing to the person I was giving the tutorial to because I had to use create-time variables at the same time (i.e. zarf package create --set ACTION=template --set CONFIG_MAP=simple-configmap.yaml) because of the way the example is set up.
Describe the solution you'd like
2 examples exist:

One that only uses create-time variables
One that only uses deploy-time variables

I believe this will be addressed by https://github.com/defenseunicorns/zarf/pull/1474


Coverity issue seen with CID: 178060

In File: /subsys/net/lib/coap/coap.c
Category: Null pointer dereferences
Function: coap_packet_parse
Component: Networking
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

@rveerama1 Is this code also present in ZoAP? If so, the fix must appear in the next 1.9 point release.

It's not present in ZoAP, I will provide a fix for this.

#4507 should fix this.

I've closed #4497 in favor of #4507.


feat: add option for using shorter CPU model name

As discussed, here's a potential feature, shorter CPU model name.
Now, this could be too fragile of an implementation - let me know if you have better suggestions, or otherwise I understand if you want to forego this one entirely. I personally really like the shortened versions though:

AMD Ryzen 7 7800X3D 8-Core Processor (8) -> AMD Ryzen 7 7800X3D (8)
Intel® Core™ i5-6500 CPU @ 3.20GHz (4) -> Intel® Core™ i5-6500 (4)

I included a comment with a list of CPU model names I found from people's screenshots in the issues on this repo, as I only have the 2 CPUs above available to me personally.
The choice for G as the shorthand was because in my branch I had done a shortened GPU name first as g so it made sense to relate the options. Just let me know if you want it changed though.
I can update the changelog etc. if you this is indeed a feature you'd be interested in.

Hi Rolv,
Thanks for working on this, I'll give this a spin on three of my personal machines to see how well it performs.

Great, let me know how it goes

Hey @grtcdr, had a chance to check this out?


Question: Date Picker component with Range type is not firing the onChange handler

If I define a Date Picker component of range type and register an onChange handler, the onChange handler isn't fired if I select the range using the Calendar, only if I type directly in the field.  How am I supposed to capture the start and end date range from this widget in a react-like way, I can go grab from the document id, but I'd really prefer not to? snippet below.  onChange never fires if you pick the range using the UI selector
            <DatePicker id="date-picker" datePickerType="range">
              <DatePickerInput
                labelText="Start date"
                placeholder="mm/dd/yyyy"
                onClick={() => console.log('clicked')}
                onChange={() => console.log('startDateChanged')}
                id="date-picker-input-id"
              />
              <DatePickerInput
                labelText="End date"
                placeholder="mm/dd/yyyy"
                onClick={() => console.log('clicked')}
                onChange={() => console.log('endDateChanged')}
                id="date-picker-id-2"
              />
            </DatePicker>

More strangeness here, when I edit the dates, if I click on the start field, the calendar shows the end date, not the start date.  I would expect the opposite.    Frankly I would prefer to not pop the underlying calendar interface for ranges unless it's specifically requested by clicking the calendar icon.
Also if I am in the first field and I type a date, and press tab, instead of accepting the date and tabbing me to the end date field, it clears the start date field and shows the calendar underneath approximately in the time range that I typed.  How can I get to the end date field using the tab key.  Thanks!

Hi @swiftfoot , thanks for pointing this out. I'll take a look tomorrow and keep you updated!

So I'm able to reproduce all the bugs you discovered and I'll try to fix most of it this week - however, I'm not completely sure how long it is going to take yet. I also noticed that flatpickr has released a new version of the range calendar that supports two input fields, so I am also going to update this and I hope that this will fix a lot of the issues. I'll keep you updated on the progress, thanks!

While developing the react app with carbon-components, we faced some issues when we  dynamically add date picker. We resolved issue by using package 'carbon-components-react'.
Do we need to use package 'carbon-components-react' instead of 'carbon-components'.? What is the standard procedure using carbon design in react?

Hi 👋 if you are using Carbon in a React app, you'd use carbon-components-react. Was that your question?

yes.  so we must carbon-components-react in react


Add Cell Count - distinctFunctionsOfPlasmablasts

Make sure Cell Count is both in Ingest and Staging area
Add cell count and export
https://contribute.data.humancellatlas.org/projects/detail?uuid=74493e98-44fc-48b0-a58f-cc7e77268b59
Acceptance criteria for the task:
Cell count is present in ingest and the staging area

[ ] Ingest
[ ] Staging area

Closing as UCSC is already looking into it


Configuring the file hierarchy in a module/feature based application

What should i do if i want to create module/feature based application that is organized like below:
/Features
	/Feature1
		/Controllers
			/ControllerA.cs
		/Views
			/View1OfControllerA.cshtml
		/Scripts
			Script1.js
			...
		/css
			css1.css
			...
	...
	and many other features

I have managed view localization with custom DynamicViewLocationExpander that creates view locations based on namespace of controller, but now i am stuck with configuration of static files.

This issue was moved to aspnet/Home#2451


New version: ZeroTier.ZeroTierOne version 1.8.6

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 324
Microsoft Reviewers: Open in CodeFlow

@wingetbot help

/AzurePipelines run

@wingetbot run

MSI (s) (C0:C8) [07:57:23:414]: Product: ZeroTier One -- Error 1920. Service 'ZeroTier One' (ZeroTierOneService) failed to start.  Verify that you have sufficient privileges to start system services.

Error 1920. Service 'ZeroTier One' (ZeroTierOneService) failed to start.  Verify that you have sufficient privileges to start system services.

Do services have issues starting in the validation VM?

.


Helm lint does not report api deprecations in k8s 1.21+

Output of helm version: 3.6 / 3.7
helm 3.7 compiled against client-go 1.22
helm 3.6 compiled against client-go 1.21
Linting a chart with a policy/v1 PodDisruptionBudget or a PodSecurityPolicy (both deprecated in 1.21) should trigger a deprecation warning. But it doesn't...
After some digging through the code I believe the issue is the following:
The k8s version used to run k8s.io/apiserver/pkg/endpoints/deprecation is supplied as const. Overriding const values with ldflags is not possible and silently fails / does nothing (golang issue). Hence the deprecation check is always performed against k8s 1.20, and not the expected client-go version defined with ldflags.

re-opening as per https://github.com/helm/helm/pull/10325#issuecomment-973020514

I think this issue can be closed, fixed in: https://github.com/helm/helm/pull/10370 ?

Yes, thank you.


Add an option to prevent terraform.tfvars deletion

There are cases which deleting terraform.tfvars when facing an error in the cluster is something we would like to prevent -
for example, when we have negative scenarios, we would like the original vars to exists and not get deleted by the test.
The PR opened as a solution for one of the tests described in this PR

/test rosa-sts-advanced-critical-high-presubmit

/test rosa-sts-advanced-critical-high-presubmit

/approve


GO:0005324 long-chain fatty acid transporter activity

Based on the definition, "GO:0005324 long-chain fatty acid transporter activity" should have the following changes:

[x] change name to "long-chain fatty acid transmembrane transporter activity"
[ ] add parent of "GO:0015245 fatty acid transmembrane transporter activity"
[x] add RHEA:39283 xref

id: GO:0005324
name: long-chain fatty acid transporter activity
namespace: molecular_function
alt_id: GO:0005325
alt_id: GO:0008562
def: "Enables the transfer of a long-chain fatty acid from one side of a membrane to the other. A long-chain fatty acid has an aliphatic tail containing 13 to 22 carbons." [ISBN:0198506732]
comment: While there is not universal consensus on the lengths of short-, medium-, long- and very-long-chain fatty acids, the GO uses the definitions in ChEBI (see CHEBI:26666, CHEBI:59554, CHEBI:15904 and CHEBI:27283).
intersection_of: GO:0005215 ! transporter activity
intersection_of: has_primary_input CHEBI:57560 ! long-chain fatty acid anion
relationship: part_of GO:0015909 ! long-chain fatty acid transport
property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/26445" xsd:anyURI

add parent of "GO:0015245 fatty acid transmembrane transporter activity"

Should that be asserted or inferred?

Ideally, everything should be inferred from the logical definitions. Let me know if you need help with this.

I'm not sure what needs to change about the logical definition to fix the parentage, so I do need some guidance here please!
The similar term 'short-chain fatty acid transmembrane transporter activity' (GO:0015636) term seems to classify correctly, so we can maybe copy aspects of that term?

I added the RHEA xref, and it looks like the name change has already happened.
As for the parentage issue, I now see the correct inferred parentage in Protege, so that has got magically fixed. :-)

Ah. I see some changes to GO:0005324 in #14793


aligned data resiliency,capacity and performance cards

Pull Request Test Coverage Report for Build 1224

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.333%

Totals

Change from base Build 1223:
0.0%

Covered Lines:
3345

Relevant Lines:
3671

💛  - Coveralls

why does the performance need to be the same height in the first place?  Also, if you want the resiliency and capacity the same height, you should put them in the same card and fix them with css (they can still look like two cards).

, you should put them in the same card grid

please see Health & Compliance in ClusterOverview for inspiration

, you should put them in the same card grid

please see Health & Compliance in ClusterOverview for inspiration

Looping in @yuvalgalanti. I wasn't a part of these discussions, but I believe the group decided to visually separate the Health and Data Resiliency cards to not imply any connection between the two. The combined Health/Compliance card of the Cluster Dashboard can stay as-is for now.

Looping @matthewcarleton in since he is now enhancing the styles to make sure it is in line with his work.

the group decided to visually separate the Health and Data Resiliency cards to not imply any connection between the two.

I wasn't suggesting that.  I just mentioned Health & Compliance as an example how to do the layout.

should I close this PR since for now alignment is not possible ..in feedback somebody suggested but on setting that recovery rate is cutting...

@suomiy Ah, I misunderstood, thank you for clarifying.

@afreen23 I think we can close this now. I've updated the layout to just use a grid gap which helps with the spacing.


update MagSetWindowFilterList flag notes

FILTERMODE_INCLUDE isn't work for me on Win10
Other people have said the same thing. Can we either get confirmation from MS that its unsupported, or can we get support for it?

#sign-off