[ADP-3272] WIP: Rough sketch of UTxO handling simplification.

🏗 This PR does not compile -- it's just a rough sketch of a potential simplification of balanceTransaction.
TODO:

[ ] Specify the difference in the specification.
[ ] PartialTxWithUTxO -- specify what will happen to this.
[ ]

Issue
ADP-3272

Closing this as it's outdated and does not compile. Will revisit later.


Tabs deep linking + no scroll not working (5.2.1)

The docs state the following options for tabs:
data-options="deep_linking:true"
data-options="scroll_to_content: false"
But there doesn't seem to be a way to have deep linking and yet NOT scroll the page. I've tried the following with and without a semicolon on the end:
data-options="deep_linking:true;scroll_to_content:false;"

We added this to our "known issues" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites

If you can get the event on click of your href="tabId" inside your list tab-title, then e.preventDefault() and the browser will not scroll. But then the url dont change to toto.com/#tabId.
You can also just 'return false' in the click handler, but it will prevent event propagation.
See https://developer.mozilla.org/en-US/docs/Web/API/Event/preventDefault

Any news since then? This problem still goes on. I have 5.5.3
TypeError: g.default_tab_hashes[0] is undefined

No sorry, Ive just been resorting to bootstrap for all my styling now :p
On Sat, Mar 26, 2016 at 2:50 AM, tarpanpatel<EMAIL_ADDRESS>wrote:

Any news since then? This problem still goes on. I have 5.5.3
TypeError: g.default_tab_hashes[0] is undefined
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zurb/foundation-sites/issues/4791#issuecomment-201749237


Fix/75 enable constant identifier names

#75

Codecov Report

Merging #76 (cf15de8) into develop (71ff203) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop      #76   +/-   ##
========================================
  Coverage    98.14%   98.14%
========================================
  Files           27       27
  Lines          486      486
========================================
  Hits           477      477
  Misses           9        9

Flag
Coverage Δ

unittests
98.14% <100.00%> (ø)

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

Impacted Files
Coverage Δ

lib/presentation/pages/repo/repo_view_page.dart
100.00% <ø> (ø)

...sentation/widgets/repo/repo_search_text_field.dart
100.00% <ø> (ø)

lib/repositories/repo_repository.dart
100.00% <ø> (ø)

...tion/widgets/repo/repo_detail_view_controller.dart
100.00% <100.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 71ff203...cf15de8. Read the comment docs.


Disconnected client record subscriptions are not removed

I have a scenario where a a client incorrectly subscribed to 100:s of records. After killing it's connection I've noticed that deepstream still considers all the records subscribed, so even when I restart a listener service, it will start listening to those 100:s of records that no one is actually using...
The only way to recover is to restart the deepstream server.

That's pretty severe. Can you replicate that with a very basic test case?

Could you please let us know if you call close()? By design it keeps
subscriptions during a connection loss so that it can resubscribe them once
the connection comes back.
On 7 Aug 2016 11:37 a.m., "Yasser Fadl"<EMAIL_ADDRESS>wrote:
That's pretty severe. Can you replicate that with a very basic test case?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/319#issuecomment-238072962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbx5QyiqQz8b3IIxKFspqf1mlnHVwPJks5qdac9gaJpZM4JeX_G
.

@WolframHempel: `close´ is not called, the client is "killed" through a page reload.

Looking at the code I can't see handling of a non-graceful client disconnect.

To me it looks like https://github.com/deepstreamIO/deepstream.io/blob/master/src/message/socket-wrapper.js never emits 'close'.

It's not the socketWrapper that emit's close, it's the socket itself. For the TCP socket this happens here, for engine.io it happens from within its socket. The subscription registry listens for that event here and calls unsubscribe for everthing the socket was subscribed to on close. Once the last subscription is removed, it will notify subscriptionListeners here.  The listener-registry is such a SubscriptionListener and should be notified here. Generally, subscriptions were cleared up reliably on disconnect. It would be good to know if there's another factor that might play into it that creates the problem

@WolframHempel: Yeap, makes total sense. I'm going to see and try to reproduce today. I'll get back with more information if/once I have it.

thanks, much appreciated :-)

Update:
I been working a bit on the provider side on the client and I noticed this behavior happen as well.
What I noticed though was it didn't happen consistently, and it appears the the server doesn't get told immediately when the socket closes if I forced close ( in this case my java app). This ties in to what Wolfram said.
Thinking once we implement heart beats this might be able to fix the issue of noticing "dead" clients, but I'm not sure how much we can do now since its all on an os/network layer level.
Summary, the functionality works as expected, but listeners aren't called as optimistically quick as we would hope.

Maybe a heartbeat implemented through the socket wrapper?

Looking at node-nats they don't trust the socket close either and implement a "PING/PONG" heartbeat to detect connectivity.
This also has the advantage of the client being able to fail-over from a non-responsive server, i.e. where there connection is open but the server is non-responsive.

Yeah, we have a whole heartbeat story for clients and servers ( for inter deepstream clustering ).
Yeah, we discussed heartbeats as part of listening, but we wanted to keep it separate as should touch multiple other aspect.

To be sure: engine.io already provides heartbeats, for TCP connections we rely on setKeepAlive() - @ronag  do you experience the lack of disconnect detection with a engine.io or TCP client?

@WolframHempel: I'm getting more unsure. I have a quite complex setup with clients of both types. So it's a bit hard to re-produce consistently.

@WolframHempel: That's a good start. But it doesn't say whether the deepstream server instance is running properly or not, only that the connection itself is intact.

Agreed, which is why we're looking into more substantial heartbeat / health check scenarios as @yasserf mentioned. This is increasingly becoming a requirement, especially for more sophisticated load balancing scenarios. Health checks might extend as far as cache/database interaction.

Can I close this issue, since it isn't really an issue as much as platform timing until clients are registered as disconnected?

Taking that as a yes!


Add integration tests

Create a testdata/{{template-name}}.golden directory that includes the expected output of a felix init run. The concept of a golden file, having an expected file output using the .golden postfix, is used in go fmt tests. I heard about it from this Gophercon talk

LGTM. We should think about how we would remake the golend dir if something changes. I'd like to see a make task perhaps? We can do that in a new pr. Merging.


removed deprecated "--name" arg && moved "create-from-import" subcomm…

…and from "sites" to functional "site import"

@okoslow are you still working on this PR?

I gave up on fixing/restructuring the old 'import' and 'create-from-import'
commands and am currently working on the new ones.  I know Sara has done
some work on the old 'import' command if you're looking to use it.

@okoslow ok. I think some of the issues with imports may have been platform issues and not actually Terminus issues. I know the methods can be cleaned up and some of the Workflow logic should probably be better encapsulated within the workflow (e.g. the workflow should have a declarative 'isFinished()' method, rather than manually having to check properties).
I'll close out this PR and feel free to continue the conversation. Thanks for taking a stab at this.


Toggle readonly option

I can't find any documentation that would let me toggle the readonly option. Is there such a thing?

:1: should be made clear in the doc

http://quilljs.com/docs/configuration/

Yes found the page already but no mention of editor.editor.enable or
editor.editor.disable
Le 17 juil. 2015 21:07, "Jason Chen"<EMAIL_ADDRESS>a écrit :

http://quilljs.com/docs/configuration/
—
Reply to this email directly or view it on GitHub
https://github.com/quilljs/quill/issues/119#issuecomment-122375621.

Hello, it doen't work for me, has this changed? ´_this.quill.editor.disable is not a function´

disable()  is not exactly like a readOnly. disable() prevents the user to select the text. While readonly allows it.

Any updates on how to toggle Readonly?

Is there any function to toggle display the toolbar also?

Or any way to dynamically(maybe on button clicks) change the editor's 'modules' property?


Resource configuration - ignore a controller

There are times when you want to ignore an Api Controller; such as when you are obeying a different standard for authentication. In this case, I want to be able to ignore by:
var configBuilder = new ConfigurationBuilder();
configBuilder.Ignore<AssessmentController>()
.Build();

This is no longer required as NJsonApiCore will only work on those controllers that have been registered.


Merge all open pull requests.

Since nothing seems to be happening here for a while and I needed a version with all improvements included, I merged all open PRs in my fork (except the one from @d42f because it is missing tests).
Of course, I only did the merge work, all credit goes to the original contributors for their changes
Feel free to close this PR and merge the original PRs, but maybe someone will find it useful coming here and also needing the improvements merged in one repo.
I am happy to help out with maintaining this project if you need someone, btw. :-)

No problem, I'm happy to see that the project will go on. Let me know if you need my help. We are using my fork for some time now and everything seems to work (at least everything we use).

Ok. I don't have any rights on the repository, maybe it's time to move it and split it into a more general project like:

translation-extractor (node lib)
grunt-translation-extractor & gulp-translation-extractor

With some regex templates (as plugin maybe) to have angular-translate and so on.
What do you think about that ?

Makes sense to me, but we should not over-generalize it. Extracting translations from something other than angular will not be required in the near future. But we already have different output formats (YAML and POT), so this should be extensible. I also like your idea to provide separate integrations for grunt and gulp.

So what do you think about three new project as you proposed but renaming translation-extractor to angular-translate-extractor?

Thanks a lot @SKoschnicke and again ... All my excuses :ok_hand:

@SKoschnicke
New repositories will be hosted on https://github.com/Boulangerie which is an organisation to carry our openSource projects (friends & mine).
angular-translate-extractor: Node Lib to extract translations
grunt-angular-translate: Grunt wrapper
gulp-angular-translate: Grunt wrapper
I'll bump grunt package to 1.0.0 once everything will be setup (included travis testing and so on...)

:+1:  Any

Yes, but I just wait that https://github.com/angular-translate/angular-translate-extractor/issues/3 remove the npm package angular-translate-extractor.
If no response, I'll refactor angular-translate-extractor into angular-translate-extract or any other suggestions are welcome :)


Commafeed won't refresh feeds

I have more than a 100 google alerts set up on commafeed, however they have not refreshed four the past four days, despite repeated clicking the refresh button. What could be wrong?

I have the same issue - for 4 days now.

I have the same issue - for 4 days now.

I had a look at why the database was underperforming and I found some long-running queries that were not supposed to run for so long.
I made some changes that should help with this issue:
https://github.com/Athou/commafeed/commit/015a60f998f244d51c381f151ade08b877bf2ff7
https://github.com/Athou/commafeed/commit/eec6f7d168c108aeba26e72095a8a85bbc3bc0d5
CommaFeed should refresh feeds faster, please allow for a couple of hours while the backend catches up with the backlog.

I had a look at why the database was underperforming and I found some long-running queries that were not supposed to run for so long.
I made some changes that should help with this issue:
https://github.com/Athou/commafeed/commit/015a60f998f244d51c381f151ade08b877bf2ff7
https://github.com/Athou/commafeed/commit/eec6f7d168c108aeba26e72095a8a85bbc3bc0d5
CommaFeed should refresh feeds faster, please allow for a couple of hours while the backend catches up with the backlog.

Amazing. Thank you!

Amazing. Thank you!

I can confirm that my feed is suddenly flooded with content :D
Thank you.

I can confirm that my feed is suddenly flooded with content :D
Thank you.

Thank you very much for resolving the issue!
From: Jérémie Panzer<EMAIL_ADDRESS>Reply to: Athou/commafeed<EMAIL_ADDRESS>Date: Monday, 1 February 2021 at 2:50 PM
To: Athou/commafeed<EMAIL_ADDRESS>Cc: Sarah Hussain<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Athou/commafeed] Commafeed won't refresh feeds (#955)
Closed #955https://github.com/Athou/commafeed/issues/955.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Athou/commafeed/issues/955#event-4271817259, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASURM26GM24FF2XCKDX3NYDS4ZFKBANCNFSM4WYFJOPQ.


Flaky test

Sometimes test "select will emit in chunks sized equal to statement pageSize" just fails
[info] *************FAILURES**************
[info] com.ringcentral.cassandra4io.Cassandra4IOTests
[error] - select will emit in chunks sized equal to statement pageSize 478ms
[error]   assertion failed (src/it/scala/com/ringcentral/cassandra4io/CassandraSessionSuite.scala:93)
[error]
[error]   } yield expect(result.nonEmpty && result.map(_.size).forall(_ == 2))
[error]                  |      |        |  |      |     |     |        |
[error]                  |      true     |  |      |     |     false    com.ringcentral.cassandra4io.CassandraSessionSuite$$Lambda$1443/0x00000008009c8040@33f6e111
[error]                  |               |  |      |     com.ringcentral.cassandra4io.CassandraSessionSuite$$Lambda$1442/0x00000008009bb040@121fee95
[error]                  |               |  |      List(2, 2, 1)
[error]                  |               |  List(Chunk(two, three), Chunk(null, null), Chunk(one))
[error]                  |               false
[error]                  List(Chunk(two, three), Chunk(null, null), Chunk(one))
[error]

I'd suggest changing forall(_ == 2) to forall(_ <= 2)

Or even delete this test. From datastax:

Note that setting a fetch size doesn’t mean that Cassandra will always return the exact number of rows, it is possible that it returns slightly more or less results.


Apollo's getDataFromTree does not fetch data for a Loadable component's children queries

💬 Questions and Help
I'm using @loadable/component along with react-apollo. For SSR, I have used @neoziro's SSR middleware solution in issue  https://github.com/smooth-code/loadable-components/issues/30 and it works great.
However, I'm encountering an issue while trying to preload pages for client-side navigation.
When navigating, we call react-apollo's getDataFromTree function on client side to preload all the data from GraphQL queries in the tree. getDataFromTree does not know to wait for loadable-components, though, so it immediately renders a loading screen instead of keeping the user on the initial page until all the loadable-components and their children queries have finished loading.
Here's a more concrete example:

User clicks a link on the Home page to a Profile page, which starts a client-side navigation.
getDataFromTree begins walking the Profile page React tree and fetching data for Query components
Eventually, getDataFromTree tries to render a loadable-component, which immediately renders a loading component while the loadable chunk is asynchronously loaded in.
Once all other queries have fetched data, getDataFromTree resolves without waiting for the js chunk to load in.
Once the JS chunk loads in, loadable-component will render its component. Any children queries within the loadable-component now start to fetch their data.

Expected: User clicks Profile page link, Profile page loads in with all data already fetched.
Actual: User clicks Profile page link, sees loading screen while Profile chunk loads in, then sees additional loading screen while Profile chunks' Queries are loaded, then finally sees Profile page with all data.
How can I get around this problem?
My initial thought was to pass the InnerLoadableComponent's this.promise to getDataFromTree via a wrapper component, but I don't have access to the InnerLoadable due to Ref Forwarding.
Any other thoughts, solutions, or discussion would be greatly appreciated. Thanks!

Hi @neoziro
You said that

The collectChunks will take care of loading all modules.

How can I gather the data to load server side before calling ReactDOMServer.renderToString ?
Can I somehow rely on collectChunks ?

@neoziro Thx for the clarification

Hello @jdmoody, You must run jsx = extractor.collectChunks(), then getDataFromTree(jsx). The collectChunks will take care of loading all modules.

not work for me!

Just update to the latest version. That's all you have to do.


Relicense from LGPL-3 to BSD-3

All the code in this repo comes from contributors who have either signed the new CLA or are employees of the Met Office. The new CLA enables us to relicense to BSD-3.
This PR add ta BSD-3 LICENSE file (to replace the old COPYING* files)
I've created a draft PR as I just need to check the year in the LICENSE file is correct

Thanks for reviewing @bjlittle !
I have addressed your review comments. I also ran a grep search for all other mentions of "(L)GPL" and "COPYING" and found that the headers needed updating as well. I believe that should have caught everything now!

@lbdreyer LGTM :+1:
As an additional though, we should also update the associated conda-forge recipe :+1:


Better chain configs

Alternative to https://github.com/sentinel-hub/eo-grow/pull/303
The change is a bit larger, but now the pipeline chain config can store remote execution parameters

I was thinking of using pipeline_process_resources and worker_resources instead of the ray_remote_kwargs etc.
Sure we'll have pipeline_process_resources: {"resources: {"A": 1}} but in general it will be more intuitive?

forgot to mention, if this does not get merged, we need to port the fix for eogrow-ray + CLI variables over

I'll try to squeeze in a test as well, never a bad thing

I'll try to squeeze in a test as well, never a bad thing

the tests i added are rather simplistic, but it's still better than nothing IMO

just remembered that the docs need to be updated as well, doing that


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3415

Questions ?
Please refer to the Backport tool documentation


Only fix launch in snap mode, not add package

Fixes #{issue number here}
Not launching browser in snap package
Changes proposed in this pull request:

Check if in snap, then open Browser

As talked about here: #4484


CFP: add a simple Service LoadBalancer node ipam

Cilium Feature Proposal
Is your proposed feature related to a problem?
In a context of  a Kubernetes cluster deployed on a "uncontrolled" network (i.e.: rented servers/vms where you don't have an equivalent to a "VPC" of some kinds) you could be in a context where you cannot use either  L2 or BGP Cilium features and thus you will not be able to use a Service of type LoadBalancer.
Describe the feature you'd like
This should work quite similarly to k3s ServiceLB (https://docs.k3s.io/networking#service-load-balancer) and fetch the selected pods and then get the Node addresses where the pods run at and "advertising" those into the service status. Using a Service of LoadBalancer type can be quite useful when using other controller that is using those, for instance ExternalDNS.
(Optional) Describe your proposed solution
The proposal would be to add a new load balancer class called io.cilium/node to activate this feature. And also like k3s Service LB use .spec.ipFamilies to determine the type of addresses and then it would use preferably ExternalIP type addresses if any or InternalIP addresses otherwise. I don't plan to implement an equivalent to the labels svccontroller.k3s.cattle.io/lbpool and svccontroller.k3s.cattle.io/enablelb though.

I don't plan to implement an equivalent to the labels svccontroller.k3s.cattle.io/lbpool and svccontroller.k3s.cattle.io/enablelb though.
But why?

I don't plan to implement an equivalent to the labels svccontroller.k3s.cattle.io/lbpool and svccontroller.k3s.cattle.io/enablelb though.

But why?

I don't have this use case and I believe most people who would use this feature too + not implementing it simplify the initial implementation and its review. But feel free to give it a shot an implement those features, I may do it in a few months but have other priorities atm.


Add Formatting standard

Many C++ Repos have a certain coding format convention (like Clang-format). Maybe this could be added to bingocpp.

Thanks for the suggestion,  are you imagining something more than the .astylerc that is already in the repo?

Thanks for the suggestion,  are you imagining something more than the .astylerc that is already in the repo?

Ah, sorry. Didn't know that was a formatter hehe


mqtt-swift3

So I made this PR so you can review how API is looking, in case you might have any feedback at this stage:
ToDos:

Testing using Sample (In-Progress)
Support for message send dup, retain, raw data
Support for received message's dup, retain other props
Possibly add support SSL Cert to Config*
Test with extending config or Default Provider
Unit Test Cases (Socket Stub)
Update Documentation / Read Me
Watch OS Support
APNS full flow

This is just for reviewing!!!


Error on compilation of the solution

The following error message was received while compiling the solution:

Severity	Code	Description	Project	File	Line	Suppression State
Error	MC3072	The property 'AutomationProperties.HeadingLevel' does not exist in XML namespace 'http://schemas.microsoft.com/winfx/2006/xaml/presentation'. Line 32 Position 80.	EditingExaminerDemo

Hi @ekleiman22,
New properties have been added to the WPF Framework for the .NET 6.0 release.  The WPF Samples 'main' branch now requires the most recent version of the WPF SDK to build.
The 6.0 version of the SDK (RC2 or GA) can be downloaded here:  https://github.com/dotnet/installer
@microsoft/wpf-developers:  We need to update the readme to describe the requirements for each branch ('main', which should be for 7.0, 'release/6.0', 'release/5.0', and 'release/3.1'.)

That should say 'the most recent .NET 6.0' SDK.

But on this page

is written

Visual Studio support
Visual Studio 2022 (v17.0 latest preview)
Visual Studio 2019 for Mac (v8.10)
and I use Visual Studio 2019 for Windows.  May be it will be better to wait when stable version of Visual Studio 2022 will be released?

I also had to install VS2022 (of itself, not a problem) in order to compile.
Also the WPF designer failed with the message "the designer is disabled due to a mismatch between the build configuration and the 64-bit assembly"

@ekleiman22 Changes have been merged, please verify.


Aspect ratio

Some conferences explicitly require submission of posters of 16:9 or 4:3 aspect ratio. This question is not directly related. If you do not think it is un-related, you can close it. How can we ensure that the poster generated is of a certain aspect ratio ?

See here: https://github.com/anishathalye/gemini/issues/12#issuecomment-553486213

Thank you very much.


Need SVG Icon

I made the frontendship logo as svg in Figma.  Shall I send this directly?

Can you please add description to this issue?

Can you please add description to this issue?

I fixed it.

I have submitted #40 PR for SVG Icon.


Implement did:ion Recover Operation

Implement support for the creation and submission of Recover operations for ION DIDs.
Sidetree Spec Reference: https://identity.foundation/sidetree/spec/#recover
Definition of done:

New method(s) implemented in DidIonMethod class:

recover()

New method(s) implemented in DidManager class:

recover()

DidKeyMethod will likely need to be updated since DID Key does not have an Recover operation.  In other words, calling didManager.update() with a did:key DID should result in an error.
Code adheres to the project's coding standards and guidelines.
Test coverage for all new/modified code >= 90% and tests pass.
Inline TSDoc for all added methods/utility functions.
Code has been reviewed by at least one other codeowner and all comments have been addressed.
Code has been successfully merged into the main development branch without conflicts.

completed here https://github.com/TBD54566975/web5-kt/issues/2


ruby: no Ruby script found in input (LoadError) when passing ruby -S a shim

I've discovered a weird issue with seeing_is_believing gem and what I believe to be rbenv shims.
Theres some testing over at https://github.com/JoshCheek/atom-seeing-is-believing/issues/5

running seeing_is_believing on it's own works
passing the true path works (ruby -S $(rbenv which seeing_is_believing))
passing the gem to ruby does not work (ruby -S seeing_is_believing)

Here is my env setup https://gist.github.com/deiga/a929c06a6831404aff28

This happened to me on a completely clean ruby and rbenv install. Not sure why. I ran this for all gems across all rubies with:
for version in $(rbenv versions --bare); do
  RBENV_VERSION=$version gem pristine --all --only-executables
done


[Docker] Fixes security enabled logic to execute demo config only if security plugin is enabled

Description
The current docker entrypoint executes the demo security config setup script regardless of whether security plugin is enabled. Then it checks whether security plugin is enabled. I'm not sure why this design was implemented but I feel like this is wrong. This PR restructures the logic to install demo config only if security plugin is enabled.
Issues Resolved

Resolves https://github.com/opensearch-project/opensearch-build/issues/4445

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

 Expand to see working logs:
➜  opensearch git:(fix-security-enable-check) docker pull opensearchstaging/opensearch:<IP_ADDRESS>99 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" -v "<custom-path>/opensearch-docker-entrypoint.sh:/usr/share/opensearch/opensearch-docker-entrypoint.sh" opensearchstaging/opensearch:<IP_ADDRESS>99
<IP_ADDRESS>99: Pulling from opensearchstaging/opensearch
Digest: sha256:87b2c2bed78237714aea05572b71757470b9b0622867615dde14c1ac3e2eeb27
Status: Image is up to date for opensearchstaging/opensearch:<IP_ADDRESS>99
docker.io/opensearchstaging/opensearch:<IP_ADDRESS>99

What's Next?
  1. Sign in to your Docker account → docker login
  2. View a summary of image vulnerabilities and recommendations → docker scout quickview opensearchstaging/opensearch:<IP_ADDRESS>99
Disabling OpenSearch Security Plugin
Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
WARNING: Using incubator modules: jdk.incubator.vector
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.OpenSearch (file:/usr/share/opensearch/lib/opensearch-2.12.0.jar)
WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.OpenSearch
WARNING: System::setSecurityManager will be removed in a future release
Feb 13, 2024 6:19:58 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
WARNING: COMPAT locale provider will be removed in a future release
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.Security (file:/usr/share/opensearch/lib/opensearch-2.12.0.jar)
WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.Security
WARNING: System::setSecurityManager will be removed in a future release
[2024-02-13T18:19:59,033][INFO ][o.o.n.Node               ] [01d3ab2017b1] version[2.12.0], pid[10], build[tar/a9c03c2d08051dc3f8e5f8c7920473e53d0d2752/2024-02-13T00:08:43.386451404Z], OS[Linux/6.6.12-linuxkit/aarch64], JVM[Eclipse Adoptium/OpenJDK 64-Bit Server VM/21.0.2/21.0.2+13-LTS]
[2024-02-13T18:19:59,034][INFO ][o.o.n.Node               ] [01d3ab2017b1] JVM home [/usr/share/opensearch/jdk], using bundled JDK/JRE [true]
[2024-02-13T18:19:59,034][INFO ][o.o.n.Node               ] [01d3ab2017b1] JVM arguments [-Xshare:auto, -Dopensearch.networkaddress.cache.ttl=60, -Dopensearch.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -XX:+ShowCodeDetailsInExceptionMessages, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.security.manager=allow, -Djava.locale.providers=SPI,COMPAT, -Xms1g, -Xmx1g, -XX:+UseG1GC, -XX:G1ReservePercent=25, -XX:InitiatingHeapOccupancyPercent=30, -Djava.io.tmpdir=/tmp/opensearch-17431464996054885810, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.security.manager=allow, --add-modules=jdk.incubator.vector, -Djava.util.concurrent.ForkJoinPool.common.threadFactory=org.opensearch.secure_sm.SecuredForkJoinWorkerThreadFactory, -Dclk.tck=100, -Djdk.attach.allowAttachSelf=true, -Djava.security.policy=/usr/share/opensearch/config/opensearch-performance-analyzer/opensearch_security.policy, --add-opens=jdk.attach/sun.tools.attach=ALL-UNNAMED, -Dopensearch.cgroups.hierarchy.override=/, -XX:MaxDirectMemorySize=536870912, -Dopensearch.path.home=/usr/share/opensearch, -Dopensearch.path.conf=/usr/share/opensearch/config, -Dopensearch.distribution.type=tar, -Dopensearch.bundled_jdk=true]
[2024-02-13T18:20:00,314][INFO ][o.o.s.s.t.SSLConfig      ] [01d3ab2017b1] SSL dual mode is disabled
[2024-02-13T18:20:00,315][WARN ][o.o.s.OpenSearchSecurityPlugin] [01d3ab2017b1] OpenSearch Security plugin installed but disabled. This can expose your configuration (including passwords) to the public.
[2024-02-13T18:20:00,916][INFO ][o.o.p.c.c.PluginSettings ] [01d3ab2017b1] Config: metricsLocation: /dev/shm/performanceanalyzer/, metricsDeletionInterval: 1, httpsEnabled: false, cleanup-metrics-db-files: true, batch-metrics-retention-period-minutes: 7, rpc-port: 9650, webservice-port 9600
[2024-02-13T18:20:01,519][INFO ][o.o.i.r.ReindexPlugin    ] [01d3ab2017b1] ReindexPlugin reloadSPI called
[2024-02-13T18:20:01,521][INFO ][o.o.i.r.ReindexPlugin    ] [01d3ab2017b1] Unable to find any implementation for RemoteReindexExtension
[2024-02-13T18:20:01,580][INFO ][o.o.j.JobSchedulerPlugin ] [01d3ab2017b1] Loaded scheduler extension: opendistro_anomaly_detector, index: .opendistro-anomaly-detector-jobs
[2024-02-13T18:20:01,630][INFO ][o.o.j.JobSchedulerPlugin ] [01d3ab2017b1] Loaded scheduler extension: reports-scheduler, index: .opendistro-reports-definitions
[2024-02-13T18:20:01,632][INFO ][o.o.j.JobSchedulerPlugin ] [01d3ab2017b1] Loaded scheduler extension: opendistro-index-management, index: .opendistro-ism-config
[2024-02-13T18:20:01,633][INFO ][o.o.j.JobSchedulerPlugin ] [01d3ab2017b1] Loaded scheduler extension: scheduler_geospatial_ip2geo_datasource, index: .scheduler-geospatial-ip2geo-datasource
[2024-02-13T18:20:01,634][INFO ][o.o.j.JobSchedulerPlugin ] [01d3ab2017b1] Loaded scheduler extension: opensearch_sap_job, index: .opensearch-sap--job
[2024-02-13T18:20:01,662][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [aggs-matrix-stats]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [analysis-common]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [geo]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [ingest-common]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [ingest-geoip]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [ingest-user-agent]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [lang-expression]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [lang-mustache]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [lang-painless]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [mapper-extras]
[2024-02-13T18:20:01,663][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [opensearch-dashboards]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [parent-join]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [percolator]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [rank-eval]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [reindex]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [repository-url]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [search-pipeline-common]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [systemd]
[2024-02-13T18:20:01,664][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded module [transport-netty4]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-alerting]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-anomaly-detection]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-asynchronous-search]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-cross-cluster-replication]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-custom-codecs]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-flow-framework]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-geospatial]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-index-management]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-job-scheduler]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-knn]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-ml]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-neural-search]
[2024-02-13T18:20:01,665][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-notifications]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-notifications-core]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-observability]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-performance-analyzer]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-reports-scheduler]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-security]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-security-analytics]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-skills]
[2024-02-13T18:20:01,666][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] loaded plugin [opensearch-sql]
[2024-02-13T18:20:01,728][INFO ][o.o.e.ExtensionsManager  ] [01d3ab2017b1] ExtensionsManager initialized
[2024-02-13T18:20:01,736][INFO ][o.a.l.s.MemorySegmentIndexInputProvider] [01d3ab2017b1] Using MemorySegmentIndexInput with Java 21; to disable start with -Dorg.apache.lucene.store.MMapDirectory.enableMemorySegments=false
[2024-02-13T18:20:01,743][INFO ][o.o.e.NodeEnvironment    ] [01d3ab2017b1] using [1] data paths, mounts [[/ (overlay)]], net usable_space [37.5gb], net total_space [58.3gb], types [overlay]
[2024-02-13T18:20:01,743][INFO ][o.o.e.NodeEnvironment    ] [01d3ab2017b1] heap size [1gb], compressed ordinary object pointers [true]
[2024-02-13T18:20:01,780][INFO ][o.o.n.Node               ] [01d3ab2017b1] node name [01d3ab2017b1], node ID [DDsYEDe8RcOp6Zn0kFWt_w], cluster name [docker-cluster], roles [ingest, remote_cluster_client, data, cluster_manager]
[2024-02-13T18:20:03,345][DEPRECATION][o.o.d.c.s.Settings       ] [01d3ab2017b1] [index.store.hybrid.mmap.extensions] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version.
[2024-02-13T18:20:03,678][INFO ][o.o.n.p.NeuralSearch     ] [01d3ab2017b1] Registering hybrid query phase searcher with feature flag [plugins.neural_search.hybrid_search_disabled]
[2024-02-13T18:20:04,316][INFO ][o.o.a.b.ADCircuitBreakerService] [01d3ab2017b1] Registered memory breaker.
[2024-02-13T18:20:04,566][INFO ][o.o.m.b.MLCircuitBreakerService] [01d3ab2017b1] Registered ML memory breaker.
[2024-02-13T18:20:04,566][INFO ][o.o.m.b.MLCircuitBreakerService] [01d3ab2017b1] Registered ML disk breaker.
[2024-02-13T18:20:04,566][INFO ][o.o.m.b.MLCircuitBreakerService] [01d3ab2017b1] Registered ML native memory breaker.
[2024-02-13T18:20:04,641][INFO ][o.r.Reflections          ] [01d3ab2017b1] Reflections took 32 ms to scan 1 urls, producing 22 keys and 60 values
[2024-02-13T18:20:04,705][WARN ][o.o.s.p.SQLPlugin        ] [01d3ab2017b1] Master key is a required config for using create and update datasource APIs. Please set plugins.query.datasources.encryption.masterkey config in opensearch.yml in all the cluster nodes.  Ignoring.
[2024-02-13T18:20:06,455][INFO ][o.o.d.PeerFinder         ] [01d3ab2017b1] setting findPeersInterval to [1s] as node commission status = [true] for local node [{01d3ab2017b1}{DDsYEDe8RcOp6Zn0kFWt_w}{GinUnOsoReSbsue9rKRKsA}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dimr}{shard_indexing_pressure_enabled=true}]
[2024-02-13T18:20:06,458][INFO ][o.o.h.AbstractHttpServerTransport] [01d3ab2017b1] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
[2024-02-13T18:20:06,459][INFO ][o.o.n.Node               ] [01d3ab2017b1] started
[2024-02-13T18:20:06,459][INFO ][o.o.s.OpenSearchSecurityPlugin] [01d3ab2017b1] Node started
[2024-02-13T18:20:06,460][INFO ][o.o.s.OpenSearchSecurityPlugin] [01d3ab2017b1] 0 OpenSearch Security modules loaded so far: []
[2024-02-13T18:20:06,471][INFO ][o.o.a.c.HashRing         ] [01d3ab2017b1] Node added: [DDsYEDe8RcOp6Zn0kFWt_w]
[2024-02-13T18:20:06,472][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,473][INFO ][o.o.a.c.HashRing         ] [01d3ab2017b1] Add data node to AD version hash ring: DDsYEDe8RcOp6Zn0kFWt_w
[2024-02-13T18:20:06,474][INFO ][o.o.a.c.HashRing         ] [01d3ab2017b1] All nodes with known AD version: {DDsYEDe8RcOp6Zn0kFWt_w=ADNodeInfo{version=2.12.0, isEligibleDataNode=true}}
[2024-02-13T18:20:06,475][INFO ][o.o.a.c.HashRing         ] [01d3ab2017b1] Rebuild AD hash ring for realtime AD with cooldown, nodeChangeEvents size 0
[2024-02-13T18:20:06,475][INFO ][o.o.a.c.HashRing         ] [01d3ab2017b1] Build AD version hash ring successfully
[2024-02-13T18:20:06,476][INFO ][o.o.a.c.ADDataMigrator   ] [01d3ab2017b1] Start migrating AD data
[2024-02-13T18:20:06,476][INFO ][o.o.a.c.ADDataMigrator   ] [01d3ab2017b1] AD job index doesn't exist, no need to migrate
[2024-02-13T18:20:06,476][INFO ][o.o.a.c.ADClusterEventListener] [01d3ab2017b1] Init AD version hash ring successfully
[2024-02-13T18:20:06,487][INFO ][o.o.g.GatewayService     ] [01d3ab2017b1] recovered [0] indices into cluster_state
[2024-02-13T18:20:06,501][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg]
[2024-02-13T18:20:06,584][INFO ][o.o.c.m.MetadataCreateIndexService] [01d3ab2017b1] [.opensearch-sap-log-types-config] creating index, cause [auto(sap-logtype api)], templates [], shards [1]/[1]
[2024-02-13T18:20:06,591][INFO ][o.o.c.r.a.AllocationService] [01d3ab2017b1] updating number_of_replicas to [0] for indices [.opensearch-sap-log-types-config]
[2024-02-13T18:20:06,624][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg]
[2024-02-13T18:20:06,670][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,675][DEPRECATION][o.o.d.c.m.MetadataCreateIndexService] [01d3ab2017b1] index name [.opensearch-observability] starts with a dot '.', in the next major version, index names starting with a dot are reserved for hidden indices and system indices
[2024-02-13T18:20:06,676][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-observability/A-LmoQ4pRG-e1USMtNAgEw]
[2024-02-13T18:20:06,689][INFO ][o.o.c.m.MetadataCreateIndexService] [01d3ab2017b1] [.opensearch-observability] creating index, cause [api], templates [], shards [1]/[0]
[2024-02-13T18:20:06,708][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-observability/A-LmoQ4pRG-e1USMtNAgEw]
[2024-02-13T18:20:06,719][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,790][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,791][INFO ][o.o.o.i.ObservabilityIndex] [01d3ab2017b1] observability:Index .opensearch-observability creation Acknowledged
[2024-02-13T18:20:06,793][INFO ][o.o.c.r.a.AllocationService] [01d3ab2017b1] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.opensearch-sap-log-types-config][0]]]).
[2024-02-13T18:20:06,812][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,813][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Loading builtin types!
[2024-02-13T18:20:06,816][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Indexing [429] fieldMappingDocs from logTypes: 24
[2024-02-13T18:20:06,867][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Indexing [429] fieldMappingDocs
[2024-02-13T18:20:06,903][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg]
[2024-02-13T18:20:06,909][INFO ][o.o.c.m.MetadataMappingService] [01d3ab2017b1] [.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg] update_mapping [_doc]
[2024-02-13T18:20:06,927][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:06,953][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg]
[2024-02-13T18:20:06,958][INFO ][o.o.c.m.MetadataMappingService] [01d3ab2017b1] [.opensearch-sap-log-types-config/DhvcoME6RP-weJzY-mfXLg] update_mapping [_doc]
[2024-02-13T18:20:06,972][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:07,155][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Loaded [429] field mapping docs successfully!
[2024-02-13T18:20:07,170][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Indexing [23] customLogTypes
[2024-02-13T18:20:07,194][INFO ][o.o.s.l.LogTypeService   ] [01d3ab2017b1] Loaded [23] customLogType docs successfully!
[2024-02-13T18:20:07,194][INFO ][o.o.s.SecurityAnalyticsPlugin] [01d3ab2017b1] LogType config index successfully created and builtin log types loaded
[2024-02-13T18:20:07,466][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] info deleteOldIndices
[2024-02-13T18:20:07,472][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] No Old Correlation Indices to delete
[2024-02-13T18:20:07,562][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] info deleteOldIndices
[2024-02-13T18:20:07,562][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] info deleteOldIndices
[2024-02-13T18:20:07,563][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] No Old Finding Indices to delete
[2024-02-13T18:20:07,563][INFO ][o.o.s.i.DetectorIndexManagementService] [01d3ab2017b1] No Old Alert Indices to delete
[2024-02-13T18:20:16,455][INFO ][o.o.m.a.MLModelAutoReDeployer] [01d3ab2017b1] Index not found, not performing auto reloading!
[2024-02-13T18:20:16,456][INFO ][o.o.m.c.MLCommonsClusterManagerEventListener] [01d3ab2017b1] Starting ML sync up job...
[2024-02-13T18:20:26,482][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.plugins-ml-config/lCGsIrDLSg-nlxvWOtaNYQ]
[2024-02-13T18:20:26,502][INFO ][o.o.c.m.MetadataCreateIndexService] [01d3ab2017b1] [.plugins-ml-config] creating index, cause [api], templates [], shards [1]/[1]
[2024-02-13T18:20:26,504][INFO ][o.o.c.r.a.AllocationService] [01d3ab2017b1] updating number_of_replicas to [0] for indices [.plugins-ml-config]
[2024-02-13T18:20:26,540][INFO ][o.o.p.PluginsService     ] [01d3ab2017b1] PluginService:onIndexModule index:[.plugins-ml-config/lCGsIrDLSg-nlxvWOtaNYQ]
[2024-02-13T18:20:26,559][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:26,582][INFO ][o.o.c.r.a.AllocationService] [01d3ab2017b1] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-config][0]]]).
[2024-02-13T18:20:26,600][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [01d3ab2017b1] Detected cluster change event for destination migration
[2024-02-13T18:20:26,600][INFO ][o.o.m.e.i.MLIndicesHandler] [01d3ab2017b1] create index:.plugins-ml-config
[2024-02-13T18:20:26,630][INFO ][o.o.m.c.MLSyncUpCron     ] [01d3ab2017b1] ML configuration initialized successfully

➜  ~ curl http://localhost:9200
{
  "name" : "01d3ab2017b1",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "IXFA6QcCQcSDXBh_0sqFFw",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.12.0",
    "build_type" : "tar",
    "build_hash" : "a9c03c2d08051dc3f8e5f8c7920473e53d0d2752",
    "build_date" : "2024-02-13T00:08:43.386451404Z",
    "build_snapshot" : false,
    "lucene_version" : "9.9.2",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}
➜  ~


it is posible doing open and close in node ?

Sorry , May i know in graphview it is possible to doing open and close function on node ?

close the parent and all children node is gone

@williamwong9090, at the moment this is not possible and we will probably not implement it in the near future. In the meantime, you have to do it yourself by playing with the visibilities.


License unspecified

You may want to include a license. Excluding one altogether may deter some potential contributors and/or future users.

Added.  Thanks.


Update guide-to-sharepoint-modern-experience.md

Fix for #649

@LoreenLa changes look correct, can this be merged?


[docs] adding agent memory troubleshooting 101 guide

What does this PR do?
Adds a basic 101 guide for agent memory behavior/leak troubleshooting.
Motivation
Better developer docs when dealing with memory issues.
Other
Rendered

Do you think it could be useful to move this to the documentation repository as a Guide in the Agent section ? It will benefit from the documentation website visibility and design.

Did a mass edit to fit within editorial guidelines (header retitling, tone, removal of emojis, etc.) Feel free to review again and I can do one final batch of edits before merge. 👍


How does this package store things on the Phone locally?

I am confused as to where and how this stores things on the phone. usually i would need a pathprovider and whatnot to store things locally, but this just does final _storage = FlutterSecureStorage(); and _storage.write which seems suspiciously simple, hence the question. Will this store things permanently and as long as the app is installed without doing anything else?

I believe that it depends on the platform but basically it encrypts the data then uses shared preferences to store it, hence the data doesn't persist after uninstall unless it got backed up somehow

Please check the description of the plugin and the source code for the details


CosmosDB 'MongoTopologyClosedError: Topology is Closed

Hello,
I am trying to use this package on an Azure CosmosDB that is essentially MongoDB API.
I get an error when I try to run any commands really:

I am not quite sure what that means, or how to troubleshoot it.
Does this support Azure CosmosDB?

Nevermind, I had to check the box for TLS then it succeeded.


"Object mapping operation" bug when using dynamic mapper with CoreData

Relationships are not connected when using dynamic mapping with CoreData. Object mapping is returned in RKObjectMappingOperation object instead of RKManagedObjectMappingOperation even if dynamic mapper has RKManagedObjectMapping.
I've made a quick fix on fork but I think it should be checked in a different way.
https://github.com/appunite/RestKit/commit/bfa62313fb6c21566e6ffa7f1d5b4b86bb5e4404

Thanks, will take a look
2011/12/6 Paweł Smoczyk <
<EMAIL_ADDRESS>

Relationships are not connected when using dynamic mapping with CoreData.
Object mapping is returned in RKObjectMappingOperation object instead of
RKManagedObjectMappingOperation even if dynamic mapper has
RKManagedObjectMapping.
I've made a quick fix on fork but I think it should be checked in a
different way.
https://github.com/appunite/RestKit/commit/bfa62313fb6c21566e6ffa7f1d5b4b86bb5e4404

Reply to this email directly or view it on GitHub:
https://github.com/RestKit/RestKit/issues/457

I am unable to reproduce the issue from the limited information in the ticket. I've added a test to cover what I believe was stated as the original problem, but the test passes without issue. Closing in the absence of a failing test case or more detail on the original issue.


Slides and website configuration build script

TODO: link on the slide with the overview what to do in the morning is not working correctly (not pointing to the header)


moment - add(period, number) is deprecated

Moment has changes how you call the add method (line 16)
Please change this:
expiration = lifetime ? (moment().add('seconds', lifetime).toDate()).getTime() : undefined;
into
expiration = lifetime ? (moment().add(lifetime, 's').toDate()).getTime() : undefined;

perhaps because i used an old version of moment, sorry i'm not so familiar with nodejs...


Organization type is now required on registration

We do not need this validation on API. It only needs on front end.


Need a method to convert struct to FixedDataGrid type

I could not find a direct way to convert my struct into FixedDataGrid data type to predict and train the model. I have to save them in csv file then only I am able to train my model.

Yeah, this could be a bit more streamlined. I wonder if it's possible to use go generate to add the appropriate base.DenseInstances methods?


Eloquent model having 2 relations to another eloquent model

Hi I was wondering how you could implement 2 relations to the same model,
as an example take a package that's being send to and from a location. your package will have 2 properties (foreign_keys) named send_to_location_id and send_from_location_id. Is there any way how you can define this inside the routes and resource (Adapter, Schema & Validator)?

Hi. Yes, you would just represent it as two relations on your JSON API resource. E.g. your packages resource would have send-to and send-from relations (just as your Eloquent model would have two relations, one for each foreign key).
So in the routes and the adapter you would need to define two resource relationships. The docs have all the information on how to define relationships in routes, adapter etc.

Closing this as I think I've answered the question. Feel free to re-open if you're still stuck.


fix comment

this comment make me a little confused, I'm not sure about my english......

Coverage remained the same at 93.191% when pulling 01114a6f8c23ed48f4c12c42a85d18cf7c6c0495 on zhaohehe:fix-comment into 052952c72df50fbe251c9853d4e61f7ecaf027a4 on slimphp:3.x.

Thanks!


"create-a-fork-of-a-parent-repository" example does not work

I opened a bug for this issue, https://github.com/MicrosoftDocs/feedback/issues/2037
I got exception ""innerException":null,"message":"The guid specified for parameter repositoryId must not be Guid.Empty.\r\nParameter name: repositoryId","
The problem is that for "parentRepository", the name property is not enough, id property should be provided as well.

Hello @dylanw-oss sorry this repository is generated so we don't really accept contributions as they would get overwritten. I will notify the team owning this sample to have a look at it.


Making website PWA

Please review the PR.

@Kerveyfelix thanks for contributing. But according to the rules & regulations we can't accept a single PR for two different issues.
Moreover, the share widget needs to be updated as I showed over here. Similar design inspirations are also welcome!
And last but not the least, the service worker is invalid. Returns fetch errors. I've gone through your PR commit & it's quite distinct that the service worker has wrong scopes assigned to it with invalid param routes.
Kindly check & re-raise the PR.
Make sure to follow this. If getting stuck, feel free to discuss your issue on the Anyxz Gitter channel.

@Neilblaze Thanks for the feedback. I will have different pull requests for different issues.
Currently working on share buttons better design.
Will need some time to debug the errors of the service worker.

Sure, take your time!


tech-conferences-operator to 0.0.8

Promote tech-conferences-operator to version 0.0.8

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ScrollView scroll indicators set to always on are not adjusting layout

If ScrollView scroll indicators are set to always be shown (System Preferences > General > Show scroll bars: Always) layout is happening as if the view port is the size of the ScrollView if no scroll indicators are present which results in the scroll indicators always showing something outside of the viewport.
(internal https://office.visualstudio.com/DefaultCollection/APEX/_workitems/edit/3972121)

Resolved with PR https://github.com/microsoft/react-native/pull/262


chore: remove unused dependencies

/e2e --tests=sdk,substrafl

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --tests=sdk,substrafl

End to end tests: :hourglass_flowing_sand: STARTING

watchdog provides watchmedo, which is used when settings: is different than prod

for skaffold, right?
do we want to keep it in requirements.txt or should it be in dev-requirements.txt?

/e2e --tests=sdk,substrafl

End to end tests: :hourglass_flowing_sand: STARTING

watchdog provides watchmedo, which is used when settings: is different than prod

for skaffold, right? do we want to keep it in requirements.txt or should it be in dev-requirements.txt?

OK, it's actually used in the CI so I think it won't work if it's in the dev requirements. Reverted the change, thanks for the review 👍

/e2e --tests=sdk,substrafl

End to end tests: :hourglass_flowing_sand: STARTING


[WIP] License Picker Resurrected

Purpose
There were some outstanding issues with the License Picker that needed to be resolved (following up on: https://github.com/CenterForOpenScience/osf.io/pull/4027)
Changes

revert revert of #4027
Make NodeLicense and NodeLicenseRecord collections
Update list-of-license to output a JSON file
Update backend and frontend where necessary
Update and add tests where necessary

Side Effects
None

I get an error when trying to install list-of-licenses:
npm install
npm WARN package.json<EMAIL_ADDRESS>No license field.

><EMAIL_ADDRESS>install /Users/sloria/projects/cos-projects/osf/node_modules/list-of-licenses
> node ./index.js

fs.js:60
      throw err;  // Forgot a callback but don't know where? Use NODE_DEBUG=fs
      ^

Error: ENOENT: no such file or directory, open 'dist/list-of-licenses.json'
    at Error (native)
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/Cellar/node/4.2.1/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node ./index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node ./index.js'.
npm ERR! This is most likely a problem with the list-of-licenses package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./index.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls list-of-licenses
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/sloria/projects/cos-projects/osf/npm-debug.log

Pass finished.

Minor: Validation error messages are displayed upon changing the license in the select box, even if the user hasn't entered any text input:

Pass finished.


Include resource type as part of the violation message

https://github.com/forseti-security/config-validator/blob/237d9245bc417f4afcaabd363f8367d5233f4f6e/api/validator.proto#L46
It's hard to determine whether or not a violation is a resource violation / iam violation since the resource name is identical in both cases but the data that's being scanned are different data.

The full resource is now included in the metadata.


add createdAt for blockSigner

Pull Request Test Coverage Report for Build 287

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 82.979%

Totals

Change from base Build 286:
0.0%

Covered Lines:
91

Relevant Lines:
99

💛  - Coveralls


GrpcRetryer fails without retrying request if "getServiceCapabilities" request fails

Expected Behavior
Request to temporal service is retried according to RpcRetryOptions
Actual Behavior
https://github.com/temporalio/sdk-java/blob/2b05f073e4b45a79cb447fdeae6ef8f704ee1423/temporal-serviceclient/src/main/java/io/temporal/internal/retryer/GrpcRetryer.java#L60
If serviceCapabilities.get() fails (not initialized yet + network issue or whatever) actual request under retry is not getting retried according to retry policies, but fails immediately instead.
Steps to Reproduce the Problem

Create brand new WorkflowClient to temporal server that returns an error upon system info request (i.e. HTTP 503). Basically any response that is not successful or UNIMPLEMENTED in grpc terms
Send any command
Request fails immediately without retrying

Specifications
temporal-sdk

Version: 1.22.3

it is weird though. If you track down usage it only affects error case and result of this call is only used to read "differentiate internal errors" flag. However, failure in this request prevents real request from getting retried in a good way that would have been retried and recovered otherwise.

It makes sense that it is a health/connectivity check, but my point is that even if service is temporarily unhealthy (perfectly normal in real world of networking/pod restarts/whatever) it is expected that workflow client call is retried according to the rpc retry options. I.e. I know it could be temporarily down and I want workflow start call to be retried for a minute before giving up. Connectivity check failure basically prevents it making retry options useless.

it is expected that workflow client call is retried according to the rpc retry options

Correct, that call should but connection doesn't retry based on those options, and this call is part of connecting. I think this may be due to lazy connectivity. If you want to separate the connection from the first call with a client, you can use WorkflowServiceStubs.newConnectedServiceStubs. This will guarantee that your workflow client calls don't lazily attempt connectivity (which is not a retryable thing).

Sure, this would have solved my narrow issue. But now it creates inconsistent behavior where eagerly created WorkflowServiceStubs.newConnectedServiceStubs are getting retried on instantiation vs lazy ones are just yolo'ing system info requests once and give up

WorkflowServiceStubs.newConnectedServiceStubs are getting retried on instantiation

From what I understand, they aren't getting retried on instantiation. I don't believe connection (which is connect + get-system-info) is ever retried, only the post-connection RPC calls. This just shifts where connection happens, but the behavior is the same. We want connection to succeed or fail immediately without retry, regardless of whether it's eager or lazy. Sorry if I am misunderstanding.

the purpose of configuring retries is to make WorkflowClient service calls reliable. Presumably - it is to mitigate intermittent issues that might occur during RPC request to temporal. Is it correct understanding?

Yes

If so - failures might occur if target temporal instance is temporarily unreachable/unhealthy and thus they would be automatically retried according to RpcRetryOptions to overcome an issue, right?

For the actual RPC call, not for first connection to the actual service though (which includes the get-system-info). But for connection failure of an already established client, definitely.

However, what really happens when service is temporarily unreachable/unhealthy is request failure due to pre-connection health request failure. Which makes no sense as service being temporary unreachable/unhealthy is exactly the problem that RPC retry is supposed to solve.

Only if you chose to combine RPC calls with initial connection. If you already made initial connection, then RPC calls are just RPC calls. RPC retry is only for RPC calls, not for initial connection. Initial connection in this case is defined as "open TCP + get-system-info call".

Following is IMO: it should not matter whether pre-conneciton or post-connection part of request is failing - from the usage perspective those are inseparable and should be treated as such when retry operation is applied.

It is unreasonable for many users to not eagerly fail when initially connecting (for host unreachable, auth fail, etc). Imagine writing a Java CLI that takes several seconds to fail for an unreachable host because initial connection is retried. But what you say makes perfect sense on failure after initial connection.
The retry applies to the gRPC request the client invokes, not the entire high-level client call that may lazy connection. If you want the gRPC request to be 1:1 with the high-level client call (and therefore retry to apply to the high-level client call), eagerly connect thereby ensuring there is no conn+get-system-info call done lazily.

Imagine writing a Java CLI
Funny you said that as it is exactly the thing I am solving for. My CLI app is run as a part of longer pipeline and is meant to connect to temporal, send command (start workflow) and exit. If temporal server is unavailable - it is going to fail "lazy" request. So, it looks like, the only real option for CLI apps is to always use eager connection with decent timeout as alternative is just not reliable.

So, it looks like, the only real option for CLI apps is to always use eager connection with decent timeout as alternative is just not reliable.

Definitely. In fact, I would always suggest using eager connection (and in every one of our SDKs besides Java that is strongly preferred). This will help you differentiate between connection failure and RPC failure.
Also note that for connection-already-established clients that have some form of connection failure, connection is often reestablished internally by gRPC as part of the RPC call so from the RPC caller POV it does perform standard retries. It's just the very first connection that does not retry.

This call is now retried


chat bot updated

I have updated the chatbot using bot press plug-in
https://github.com/Suchitra-Sahoo/AgriLearnNetwork/assets/112798996/7dccbbcf-5f54-433d-bb65-1727eb7dd3e4
https://github.com/Suchitra-Sahoo/AgriLearnNetwork/assets/112798996/dfca9884-e438-47e3-97a5-6b1c5b1d3f07
The above videos show the working of the chatbot
Thanks @Suchitra-Sahoo for giving me this oppurtunity

This repo have no conflicts at the time of pulling this request

@nagamukesh the functioning part of the bot is fine. But if you go and click on the website link given in the repo you will see it has a yellow and green theme. Also the closing option is visible and is not hidden by the navbar and insteas of B the bot has A which represents agribot.

I have changed the color code

now, this is how the bot looks like

now, the close button is also visible
suggest any potential changes. If not, merge this request
thank you

There are conflicts in this branch. I can't merge your PR before you solve it.

you have accepted/merged a pull request where someone else added a chatbot which is again not working, which is why it is conflicting.
I request to revert those changes as soon as possible so that I can make sure my changes do not conflict

I request to look into this pull request and please revert those changes done to chat bot which are causing conflicts with my pull request

You may pull the changes from origin and raise another PR. Attach a video to showcase how your bot is functioning better as compared to current bot. Based on that your PR will be merged.


[DROPDOWN] - Set the default selected value for dropdown that use Remote (API).

I have a question about the dropdown that uses remote (API). I selected some items and save it to my database. Then if I want to edit the data, I want to it shows the selected item that I select it before. How it make it works? Because I can't put the selected:true on the API response because the item just shows 10 item that best matches with the query keyword.
Thanks!

Have you tried making a request on page load to get a list of the selected items and setting the dropdown values to these and setting them as selected?

same question, there's a way to set up selected value from api response?


No Man's Sky on Arch

Hi there,
I've been trying to get this to work on No Man's Sky on Arch to no avail.
I'm not sure what info would be useful or if you can even do something about it. My guess is that it just simply doesn't work?
I have a Nvidia 3060 and I installed the game through Steam. I am using fgmod in the launch options as advised by the tool.
Am I supposed to be forcing a specific version of Proton? (Or any version to begin with)
When I open it, it just opens in a window that shows nothing (It's frozen with whatever was in the background, then nothing seems to happen)

NMS is currently the only Vulkan game that uses Streamline so there are some growing pains. Nukem made FSR FG somewhat work on Nvidia but DLSS Enabler, especially on AMD, has even more issues.
Can you share dlss-enabler.log and dlssg_to_fsr3.log? Just zip them

Where would they be created? I've checked both fgmod and NMS's Binaries folder and I can't find them there.

Yes it should be in the Binaries folder. Could you do two thing:

confirm that dxgi.dll and dlss-enabler.dll are actually in this folder
remove the SETTINGS/graphicsettings.mxml file, a member of the discord server that uses nvidia always had to delete that file

Both of the .dll files are there.
I tried removing that file, then launching the game again, and the behaviour was the same. No log files have been created either. This is most likely normal, but just in case, the file you asked me to delete gets recreated.
Sorry to ask again, but, should I be using Proton? If so, is any version favoured? I've tried both with and without with no perceptible difference.
In case it helps, here's a screenshot of the Binaries folder:

Tomorrow I will try and see if I can find something on Steam/NMS logs.

I use Proton Experimental Bleeding Edge. It would seem as if streamline doesn't load dxgi.dll for you.
Try following steps:

Remove /home/user/fgmod/fgmod from the launch options
Add WINEDLLOVERRIDES=winmm=n,b to the launch options
Remove dxgi.dll from the game folder
Rename dlss-enabler.dll to winmm.dll

And launch the game again

logs.tar.gz
That did the trick, finally manage to get logs going.
When I opened the game, it initially seemed to run, it showed the Hello Games logo, then the visuals froze, but I could here what I can only assume was the main menu through my headphones.

So you probably have the exact same issue as me. If you use a shortcut to make the game exist fullscreen it should run again for a few frame and freeze and just repeat it.
It's not in a good state but I also don't fully understand what's going on here. I just make a hopefully useful installer :)

It's alright. At least the game runs fine without it anyways.

similar problem currently with amd-card on deb.

also wd legions does currently not work

It will be best to create a separate issue for that. Please add all log files from the game folder into it when you do.

Do you plan to include both in the future?

NMS is mostly broken in the mod that my installer installs so I'm at the mercy of that mod. Tho I can tell you that there were many attempts to fixing it, both by Nukem and by nitec but after many failures the motivation to making Vulkan Streamline work is quite low.


Build newer versions[FEATURE]

8.1.42, 8.1, latest - Latest stable release from the 8.1.x branch as of 5-29-24
Setup so that this will auto build the latest stable version.
Review and look to move container to run under Ignition users instead of root.
Update MS SQL JRE to version 12.6.2 from 9.x.x or specifically to mssql-jdbc-12.6.2.jre11.jar

Our team needs 8.1.42 and it would be ideal if this could be completed by 6-28-2024


Visibility of URL-related information in displayed Nutshell content

Hi,
I haven't seen this previously: the display of URL-related information in the Red Box in the screenshot below:
Is that something new ? Will it display like this in the published web page ?

Can one turn that off ?
Cheers.
Howard

That was always there!  It only shows up if you're embedding from a different page.
To remove it, you can add an extra line of CSS (like in this comment https://github.com/ncase/nutshell/issues/25#issuecomment-1412473980 ).  The extra CSS to add is this one line:
.nutshell-bubble-from{ display:none; }
Cheers!

P.S: To clarify, that means the total CSS you'd need to add is these two lines, to remove the share-link & from-link:
.nutshell-heading-embed{ display:none; }
.nutshell-bubble-from{ display:none; }

It's important they're on TWO different lines, otherwise the CSS won't work.

That works!
I'm going to enjoy using Nutshell.
Thanks again.


PLANNER-537: Workbench Solver Editor: remove bendable types from solver score configuration

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

+1

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

@psiroky can you add @mcimbora to our github org so his PRs don't have to be verified? thanks.

@csadilek way ahead of you :) (added him ~30 mins back)


Fix status log_out

When we click on button sign out, it's not work, maybe wrong route path

DONE


Expand notes about flashing USB disk image with dd

Explained what "/dev/sdX" means.
Me not knowing what disk numbering means, I flashed the image to partition instead of disk, so it slowed me down for some time until I found out why it does not boot. This note would have helped me to save time, so it may help someone else.

Probably "partition ID" or other things can be reworded by the reviewer, since chatgpt consulted me that
"partition number" is the more accurate term and is what is commonly used in documentation and discussions related to Unix-like file systems.

Changed "ID" to "number" myself.

@mindaugas147 thank you for your contribution. Would you be able to resolve any issues related to pre-commit? I would be glad to merge this PR if all checks would be green. Otherwise, it would have to wait for someone to fix it to meet our quality criteria.

@pietrushnic thank you for patience :) I am in the process of learning how things work. It looks that checks have passed now.

@mindaugas147 thank you.


Update MD file on new branch 2017-12-04_15-31-04

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


DatePicker ValueChanged return wrong date

code:

void OnChangeDate(DateTime ?D2)
{
}

returned date is selected date -1 day :-(
ex: select 10/08/2019 return 09/08/2019

not a bug.
need convert date to locale

doesn't work:
<MatDatePicker@bind-Value="@PikDate"></MatDatePicker>

date: @PikDate.Value.ToString("dd MMMM yyyy", CultureInfo.GetCultureInfo("en-US"))

@code {
   public DateTime? PikDate { get; set; }
}

I think that .ToLocalTime() should resolve this problem for all. And it's works in Server side Blazor, but I found that in Client Side Blazor this not works. So, problem is really exists.
So, fixing is in progress.

I had the same issue so I used this package , till it's gets fixed in mono (wasm).
https://github.com/jsakamoto/Toolbelt.Blazor.TimeZoneKit
https://github.com/aspnet/Blazor/issues/1166

In my case this package did not help.  I still have this bug.

.ToLocalTime() doesnt work in server-side blazor, still shows UTC. is there anyway to convert utc times to user browser timezone in SSB?

@kaanlab

In my case this package did not help. I still have this bug.

This show work , needs to use to ToLocalTime()
example
DateTime.Now.ToLocalTime() // should return local time

@iAmBipinPaul  packege +.ToLocalTime() doesn't work in client-side blazor (webassembly)

Hi @kaanlab
It does work  in my case and my timezone is Asia/Kathmandu
in startup.cs
 public void Configure(IComponentsApplicationBuilder app)
        {
            app.UseLocalTimeZone();
            app.AddComponent<App>("app");
        }

Then
DateTime.Now.ToLocalTime() // should return local time

It return local time.
Try changing your system time zone to some other timezone. May be, your timezone may not be supported by this package,


Firefox Flash Plugin version typo?

Issue description
Using unstable, I get a 404 on Firefox's Flash plugin.
Steps to reproduce
Firefox.enableAdobeFlash = true;
nixos-rebuild
these derivations will be built:
  /nix/store/8j41swhfz47fs0nz6lq5i70zf9pz7ynj-flash_player_npapi_linux.x86_64.tar.gz.drv
  /nix/store/q5vn719lmhxcjlic12mzk860ddd6nsps-flashplayer-<IP_ADDRESS>.drv
  /nix/store/hyfnkbxmqibc5vbjgxqkqxav7kj45qy0-firefox-53.0.3.drv
  /nix/store/rs5ig5bc5lljk62jkx78wf5vj6ma3q7b-system-path.drv
  /nix/store/1pfwassrwqy5yajnvwvkf161bcw1nzwc-dbus-1.drv
  /nix/store/8694msij660km1yj8fxlxrif6l8vq1h9-unit-polkit.service.drv
  /nix/store/9rlyafq8887y5dpj9q1zchiaq69p3q4y-unit-dbus.service.drv
  /nix/store/q4c35j92afv6smwa4zq3s1gs7yhbyrqf-unit-systemd-fsck-.service.drv
  /nix/store/5l2mmgcqhh3162418wb87vrb6p9whf4j-system-units.drv
  /nix/store/fd94xsy1n4ldh9yp687j2wcz8zr3y1ns-user-units.drv
  /nix/store/x0z8pc7mj3ljrfwbwffwdl20v99x0715-etc.drv
  /nix/store/dcpn6g4y97s12q97jckdsp54k4qvsx4d-nixos-system-zero-17.03.1316.412b0a17aa.drv
building path(s) ‘/nix/store/xkk9gqm70la86myin3213b82f63vdw6y-flash_player_npapi_linux.x86_64.tar.gz’

trying https://fpdownload.adobe.com/get/flashplayer/pdc/<IP_ADDRESS>/flash_player_npapi_linux.x86_64.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download flash_player_npapi_linux.x86_64.tar.gz from any mirror

It looks like it is trying to get version <IP_ADDRESS> instead of <IP_ADDRESS> (the most recent one.) Where does Firefox get the version number for Flash?
Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...) NixOS: 17.03.1316.412b0a17aa (Gorilla)
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) "17.03.1316.412b0a17aa"
Sandboxing enabled: (run grep build-use-sandbox /etc/nix/nix.conf) false

It seems the package was updated a while back: https://github.com/NixOS/nixpkgs/pull/26568

We have to upgrade flashplugin to version <IP_ADDRESS>, I think.

We did in #31660

Is this issue still reproducible?


[AKS] az aks create: add enable-encryption-at-host parameter

Description

az aks create: add enable-encryption-at-host parameter
Testing Guide

docker run -v ${HOME}:/root -it andyzhangx/azure-cli:2.22.1
az aks create -g $RESOURCE_GROUP_NAME -n $CLUSTER_NAME --node-count 1 --node-vm-size Standard_DS2_v2 --generate-ssh-keys --kubernetes-version 1.20.2 --enable-encryption-at-host
az aks nodepool add --name nodepool2 --cluster-name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --enable-encryption-at-host

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

2021-04-22T03:48:24.7236220Z -  FAIL - HIGH severity: option_length_too_long
2021-04-22T03:48:24.7237497Z     Parameter: aks create, `enable_encryption_at_host` - The lengths of all options ['--enable-encryption-at-host'] are longer than threshold 22. Argument enable_encryption_at_host must have a short abbreviation.
2021-04-22T03:48:24.7238773Z     Parameter: aks nodepool add, `enable_encryption_at_host` - The lengths of all options ['--enable-encryption-at-host'] are longer than threshold 22. Argument enable_encryption_at_host must have a short abbreviation.

I already added exception rules in linter_exclusions.yml, not sure why it still failed:
2021-04-22T03:48:24.7236220Z -  FAIL - HIGH severity: option_length_too_long
2021-04-22T03:48:24.7237497Z     Parameter: aks create, `enable_encryption_at_host` - The lengths of all options ['--enable-encryption-at-host'] are longer than threshold 22. Argument enable_encryption_at_host must have a short abbreviation.
2021-04-22T03:48:24.7238773Z     Parameter: aks nodepool add, `enable_encryption_at_host` - The lengths of all options ['--enable-encryption-at-host'] are longer than threshold 22. Argument enable_encryption_at_host must have a short abbreviation.

@fengzhou-msft would you help review? thanks.

@qwordy could you help review? thanks.

@qwordy can you merge this PR? thanks.


Update post.md

I added some basic info missing in the first draft (such as Base URL, authorization, endpoints, and status codes).

By delete - I mean close


Make sure titles always sanitized before passing over conpty

Summary of the Pull Request
When title updates are forwarded from the host to the client terminal,
they're passed over conpty in an OSC 0 sequence. If there are any
control characters embedded in that title text it's essential they be
filtered out, otherwise they are likely to be misinterpreted by the VT
parser on the other side. This PR fixes a case where that sanitization
step was missed for titles initialized at startup.
PR Checklist

[x] Closes #12206
[x] CLA signed.
[ ] Tests added/passed
[ ] Documentation updated.
[ ] Schema updated.
[x] I've discussed this with core contributors already. Issue number where discussion took place: #12206

Detailed Description of the Pull Request / Additional comments
Originally the sanitization step was handled in DoSrvSetConsoleTitleW,
which catches title changes made via VT escape sequences, or through the
console API, but missed the title initialization at startup. I've now
moved that sanitization code into the CONSOLE_INFORMATION::SetTitle
method, which should cover all cases.
This sanitization is only meant to occur when in "pty mode", though,
which we were originally establishing with an IsInVtIoMode call.
However, IsInVtIoMode does not return the correct result when the
title is set at startup, since the VT I/O thread is not initialized at
that point. So I've instead had to change that to an InConptyMode
call, which determines the conpty state from the launch args.
Validation Steps Performed
I've manually confirmed the test case described in issue #12206 is now
working correctly.
However, the change to using InConptyMode caused some of the unit
tests to fail, because there isn't a real conpty connection when
testing. Fortunately there are some EnableConptyModeForTests methods
used by the unit tests to fake the appearance of a conpty connection,
and I just needed to add some additional state in one of those methods
to trigger the correct InConptyMode response.

I sure am glad I can click "rerun failed jobs" and it only takes six minutes


isolate uts namespace for hostnetwork pods

For pods in host-network mode,  there's no specification whether pods should share uts namespace with host in kubernetes community. It's commonly believed that the namespaces of containers are isolated from host, and docker containers with hostnetwork mode indeed don't share uts namespace with host.  Thus this pr is proposed to change the default uts namespace mode for pods in host-network mode.
I've searched for a while, but I did not find valuable notes about this, hoping someone can explain why pods in host network mode use host uts namespace.

Fwiw if we look at other cri runtimes (and if I'm reading cri-o correctly that is) they only remove the netns when requesting host-network: https://github.com/cri-o/cri-o/blob/6adc9a4f25b3d03295894a00e9ad9c0d01431621/internal/factory/container/namespaces.go#L26


fix: added missing translations for italian it-IT

Pull Request Checklist

[x] Target branch: Pull requests should target the dev branch.
[x] Description: Briefly describe the changes in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for the changes?

Description
Added missing translations for it-IT in src/lib/i18n/locales/it-IT/translation.json

Changelog Entry
Fixed

Added missing translations for it-IT in src/lib/i18n/locales/it-IT/translation.json

Changed

Added missing translations for it-IT in src/lib/i18n/locales/it-IT/translation.json

Thanks!


Finding Images

The ability to insert images and then specify using markdown where those images should appear in the finding. The report generator should then place those images where specified in the markdown.

@aaronweaver jay has pushed an update

Great work! Can't wait to start using the feature.


Fix workflow conditional

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (633773d) 43.80% compared to head (4f4a7ce) 43.74%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #437      +/-   ##
==========================================
- Coverage   43.80%   43.74%   -0.07%
==========================================
  Files          59       59
  Lines        4917     4917
==========================================
- Hits         2154     2151       -3
- Misses       2629     2631       +2
- Partials      134      135       +1

Flag
Coverage Δ

unittests
43.74% <ø> (-0.07%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix ovos containers and refactoring

Comprehensive Refactoring and Enhancement of Build Scripts

Refactored the EEPROM firmware path handling in the makefile to support specific Raspberry Pi models (bcm2711 for Pi 4 and bcm2712 for Pi 5) with error handling for unsupported models.
Streamlined various bash scripts for improved readability and structure. Encapsulated key functionalities into functions, such as creating SWU files and writing OS release and machine info, enhancing modularity and maintainability.
Reorganized file listings and conditional statements for clarity, particularly in container image scripts, ensuring ease of understanding and modification.
Adopted consistent formatting and commenting across all scripts, facilitating better readability and comprehension for future development and review.
Implemented robust error checking and handling mechanisms, including cleanup operations and validation checks, to ensure script reliability and stability.

These changes collectively enhance the codebase's clarity, organization, and robustness, paving the way for more efficient future development and maintenance.

NICE !
Will go through.

after aligning with the dev branch I see some problems with the socket
Jan 08 00:05:02 OpenVoiceOS-0822a6 systemd[514]: Started OpenVoiceOS Messagebus Service.
Jan 08 00:05:02 OpenVoiceOS-0822a6 ovos_messagebus[1332]: 4975f78a10b3d89ddb67e9541908a81da434cfcb19af2b5f921815593725a27e
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]: 2024-01-08 00:05:08.170 - bus - ovos_messagebus.__main__:main:46 - INFO - Starting message bus service...
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]: 2024-01-08 00:05:08.179 - bus - ovos_messagebus.load_config:load_message_bus_config:33 - INFO - Loading message bus configs
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]: Traceback (most recent call last):
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:   File "/home/ovos/.venv/bin/ovos-messagebus", line 8, in <module>
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:     sys.exit(main())
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:              ^^^^^^
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:   File "/home/ovos/.venv/lib/python3.11/site-packages/ovos_messagebus/__main__.py", line 50, in main
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:     application.listen(config.port, config.host)
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:   File "/home/ovos/.venv/lib/python3.11/site-packages/tornado/web.py", line 2211, in listen
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:     server.listen(
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:   File "/home/ovos/.venv/lib/python3.11/site-packages/tornado/tcpserver.py", line 183, in listen
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:     sockets = bind_sockets(
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:               ^^^^^^^^^^^^^
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:   File "/home/ovos/.venv/lib/python3.11/site-packages/tornado/netutil.py", line 162, in bind_sockets
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]:     sock.bind(sockaddr)
Jan 08 00:05:08 OpenVoiceOS-0822a6 ovos_messagebus[1346]: OSError: [Errno 98] Address already in use
Jan 08 00:05:09 OpenVoiceOS-0822a6 podman[1353]: 2024-01-08 00:05:09.076834037 +0000 UTC m=+0.332663982 container died 4975f78a10b3d89ddb67e9541908a81da434cfcb19af2b5f921815593725a27e (image=docker.io/smartgic/ovos-messagebus:alpha, name=ovos_messagebus, org.opencontainers.image.title=Open Voice OS OCI message bus image, org.opencontainers.image.documentation=https://openvoiceos.github.io/community-docs, io.containers.autoupdate=registry, org.opencontainers.image.source=https://github.com/OpenVoiceOS/ovos-docker, org.opencontainers.image.created=2024-01-05T03:40:36Z, org.opencontainers.image.description=Message bus service, the nervous system of OpenVoiceOS (Python implementation), org.opencontainers.image.vendor=Open Voice OS, PODMAN_SYSTEMD_UNIT=ovos_messagebus.service, org.opencontainers.image.version=0.0.8a)

It looks like I broke something.

No I did. I am in the middle of changing the messagebus over to the C++ WAY faster one, but forgot a few systemd service files which still has some dependencies to the old one.
Will see if I can get to it today.
Anyhow, would it be possible for you tp split up this PR into three parts?

The buildroot scripting work
The rpi-eeprom package work
The ovos-containers work.

The last one being the one with the least priority as I will have to make some changes there as well.

Anyhow, would it be possible for you tp split up this PR into three parts?
Done, I will close this PR

Thx, will go through the others as we speak.
I might hold of the ovos-containers one for a little bit as I am reworking that one myself as well. We will see.


Add ffxiv_typedecl

It's just #469 on a separate file.

Deemed not necessary due to recent updates to CExporter


Current version of among us editor

Ill keep adding the new stuff. you can fix anything and then make it runable

This pull request is filled with uncompilable Java code.
The creator has simply changed things in a way that isn't usable, however I do appreciate the effort.
Closing this for now, please re-open if you end up updating the editor properly.


Permissions - Ability to create a group chat that only has two members and cannot have additional members added (Medium)

1:1 chats don’t need custom permissions IMO. All 1:1 chats should work the same way.
We should be able to use our existing permissions framework to enable 1:1. We’d just define a default permission set required on all 1:1 chats.
We may want to spend a bit of time making sure we don’t need to upgrade our permission system to support this permission set. Maybe there are some additional fields we can add now, even if they’re unused, to make room for 1:1. For example, an optional list of allowed_members on the ImmutableMetadata to restrict the group to 2 people.

[ ] New permission type to identify a 1to1 conversations
[ ] Way to handle adding just one person to the group after create (possibly and immutable list called allowed_members)
[ ] Validation

[ ] 1to1 Group should not be able to be named
[ ] You cannot leave a 1to1 Group
[ ] Should not see a group membership change codec on first send

Related PR - https://github.com/xmtp/libxmtp/pull/901


App not opening on Windows 11

I downloaded the app from both the Microsoft store, as well as the manual .zip installation. It is not opening from either place. My cursor  shows the blue circle loading icon for about half a second and then nothing happens. I am not able to replicate this issue on any Windows 10 machines.

Did you download the 2023 beta version? This sounds like a duplicate of #117 which is fixed.

I am using 2023.0.1 pathplanner lib, but only 2023.0.0 is working. 2023.0.1 doesn't work still

wait nvm it works now sry mb.


Create a Vector3 class.

Create a vector 3 class that has support for all the operations that a vector should have, these being:

Vector addition.
Vector subtraction.
Scalar multiplication.
Dot product.
Cross product.
Vector multiplication (a.k.a component wise multiplication with a vector).
Not only that, but this class should have support for some other functionalities, such as:
Getting the vector's length.
Returning a normalized vector.
Have a string representation for it to be printed (which could be useful for debugging).

And maybe other functionalities in the future.

This class will extend from the Point class as detailed in issue #6.


[#28543][prism] Garbage collect side inputs.

Until now, side inputs were handled separately from most of the data handling, leading to
them remaining un-garbage-collected, leading to a memory leak for long running streaming pipelines. This PR resolves that by moving Side Input Data handling into the elementmanager, which allows the data to be GCd once the output watermark for a stage has moved beyond where a given window's side input could be referenced.
As a refresher: A transform T with a side input S, can only access data from S that is in the Same Window W as a given Element. This is what gives the "blocking" behavior of side inputs for consumers. On the other side, the side input can thus be cleaned up if there's no data that remains to be processed by T, that can be projected onto W.
Necessary precursor to add state and timers in #28543, which has the same garbage collection behavior WRT a stages watermark.
Bonus changes:

Annotated some coder look up errors in the SDK's execution bundle translation, to clarify what was actually failing. The issue that needed this debugging was due to removing the calls that added the coders to the bundle's components.
Removed some extra map nesting around side inputs.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Run Go Prism Precommit

Thanks! Holding off on merging this for a bit while I'm sorting out prism stability. Very likely not hurt or helped by this PR, but prudence.

Scratch that. My client has extra println... so that "stability" bit was just the Examples failing. whoops.


Showcase Submission for challenges/30-phyllotaxis

Thank you Russell Hunter for your contribution! A member of the Coding Train team will review it shortly.

Blurry Phyllotaxis spinny thing
Russell Hunter

Lovely!


Create dependabot.yml

Codecov Report
Patch and project coverage have no change.

Comparison is base (4be4c28) 100.00% compared to head (e4330f5) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #216   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          313       313
  Lines         9679      9679
  Branches       949       949
=========================================
  Hits          9679      9679

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.