Improve setting of base_uri / usage of APIS_BASE_URI

While trying to document the usage of APIS_BASE_URI, I found that many APIS apps contain lines like the one below (some even in more than one place – potentially redundantly?):
base_uri = getattr(settings, "APIS_BASE_URI", "http://apis.info")

if base_uri.endswith('/'):
    base_uri = base_uri[:-1]

There are several problems with this code:

APIS_BASE_URI is not documented, so users won't know:

they should set it in their Ontologies app's server_settings.py file in the first place – and what to, or what for
the variable should be overridden for local development in local_settings.py

whatever APIS_BASE_URI is set to does not get validated, which very easily results in non-sensical URLs – whether due to a non-URL or incorrectly formatted URL provided by a dev or because some APIS apps propagate nonsensical values like APIS_BASE_URI = "TO CHANGE" to child apps
http://apis.info is not a valid website, so it's weird/confusing/pointless to use it as fallback. It seems to me it'd be best if the app errored out if the user didn't explicitly set APIS_BASE_URI because I can't think of a case where we'd want non-functional links to be created. (?!) If there is a good reason, I suggest that instead of hardcoding this value everywhere, a new key-value pair to hold some default address is added to PROJECT_METADATA (which is retrieved/set right before base_uri in most cases).
I believe the variables APIS_BASE_URI and base_uri should be renamed for clarity in any case because it appears to me they are always meant to refer to web addresses/actual domain names for projects (except when used for local development). The current naming also isn't consistent – I've seen both base_uri  and base_uri_web.

In one instance, PROJECT_NAME seems to be used in unhelpful ways when base_uri could (potentially) have been used: In one template, it's used to construct the web address https://{{ PROJECT_NAME }}.acdh.oeaw.ac.at in a note displayed to devs to highlight they are looking at a development version (to link to the live version of a project; which is not useful for projects with more than one website, e.g. a production version vs. a dev/staging version).

A solution to the lack of URL validation could look like this:
https://github.com/acdh-oeaw/apis-core-rdf/compare/kk/exp/validate_base_uri

Update half a year later:
For local development, APIS_BASE_URI is actually best not set to anything but the empty string. The linked example demoing URL validation would need to be updated accordingly.
You'll want to set the variable to something to override whichever nonsensical default you'd inherit otherwise, but not hardcode a domain/domain+port combo for localhost either for maximum flexibility. A setting of  APIS_BASE_URI = "" will only save entities' paths for Uris, e.g. /entity/43/, which results in clickable, functional links to the individual resources in the API.

closing this as there is #315 which should resolve most of the problems


How to resume training?

Hello,
I was training and my training stop because of some reason but now I want to continue.

you can save the checkpoint every epoch.

Thank you.


Request for API Gateway with Custom Domain

Would love to see an example similar to that generated by sam init, but with the creation of an API Gateway API with a custom domain name.  If this is already doable, how can I update the following to accomplish this?
    Api:
      Type: AWS::Serverless::Api
      Properties:
        StageName: prod
        EndpointConfiguration: "EDGE"
        DefinitionBody:
          swagger: "2.0"
          info:
            title: "TestAPI"
            version: "0"
          paths:
            /hello:
              get:
                x-amazon-apigateway-integration:
                  uri:
                    Fn::Sub: "arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${HelloWorldFunction.Arn}/invocations"
                  httpMethod: "POST"
                  responses: {}
                  type: "aws_proxy"

@holtc and @Haughar There is currently an RFC out on the SAM Spec for this support: https://github.com/awslabs/serverless-application-model/issues/783.
This also links to other issues where you can see how to wire up Custom Domains to the AWS::Serverless::Api in the mean time.
Closing as SAM already has issues/RFCs for this and this is for the SAM Spec not the cli.


TransitionGroup does not take into account CSS scale

Vue version
3.3.4
Link to minimal reproduction
https://play.vuejs.org/#eNp9U01v2zAM/SucgKEJ4Nheil48t9gHimE7bMPWw4bIB82hMzWyZEiymyLIfx8lJ5k3FM0lIt8j+fgk79nbrkuHHlnBSldb2Xlw6PsOlNCba8684+yGa9l2xnrYg8UGDtBY08IFlV285prr2mjnQVgL14EwW+UJvEpgWc0D2vS69tJocA+im81hzzXAitjpIFSPq7xKQu0xWlYVdZnAy3/gvKpo5IHrMhvlkjgKPLadEh4pAijXcgDnHxWGBazQrjG2LcDVQuFsOYeYC/Qfs6v85ST+GeO4MdCvvAuADOI/WEOmbPGRWvbqzCCOkjAsaAABkmSA1EEuZ1CM7JCkaFh43PlzfFNmSp7GZP/NOeV/9d6Tb29qJestlQYDqTT8vSizER03zmhlOpXZxAgKowm0t+lwTZl0WLRmwCSeUHu0C0FXc8ooFAMeM+MtRWOirmI8ByMhT68coHB4vokwhvqzhN4LPYZGbtJ7ZzQ9qtiGs9q0nVRov3ShGb2pYhwQMKGUefgUc972QcuYr39jvX0if+92IcfZV4sO7YCcnTEv7Ab9CN9+/0yOT8DWrHtF7GfAb+iM6oPGkfau12uSPeFFtR/j5yD15s7d7jySR8elgtDAPEQ+Z/SJvH9m9b9yL9PLWEeOssMfB+8zGQ==
Steps to reproduce

Click the button

What is expected?
No jumps in the transition animation
What is actually happening?
Jump at the very start, because CSS scale is not being taken into account, so the distances are off by a factor of .
System Info
No response
Any additional comments?
See also #6387.
Should probably be tested with and without scale() on the child elements too.
This SO post indicates that element.getBoundingClientRect().width / element.offsetWidth should be enough to figure out the scale:
https://stackoverflow.com/questions/5603615/how-to-get-the-scale-value-of-an-html-element-using-javascript-or-jquery
However, getBoundingClientRect may be expensive - although it should only need to be called when the transitions start, but if it is too expensive then a way to opt-in would be fine too

It seems like TransitionGroup is already doing getBoundingClientRect():
https://github.com/vuejs/core/blob/1c525f75a3d17a6356d5f66765623c0ae7c0ebcc/packages/runtime-dom/src/components/TransitionGroup.ts#L175-L177
So there should be no problem with the / element.offsetWidth approach, at least

duplicate of #6105


Level up the template headers

The issue
When I try to open/view issues or pull requests, I found it a littile bit difficult to distinguish issue/pr headers from their content, since level ##### is too similar with the contents.  Maybe it is better to level up the headers.
Well it is a little bit opinionated, but I still would like to share my thoughts. 😄
The fix
Update github templates' header level to ###.
The checklist

[ ] Associated issue
[ ] A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

By the way, the CI failes because pipenv is using the latest pip version. Maybe it is better to pin specific pip version in CI to have a stable and repeatable tests.

Can you provide a screenshot of the new level? I’ve been thinking about changing this, but never got myself to compare various settings to decide which is best.

This is the new level.

This is the old level.

Acutally I've already using the new template in this PR 😃
Personally, I prefer the new level, since it makes much easier to distinguish between different sections, such as The issue``, The fix``` and etc.

Yeah this looks good to me. I read GitHub’s CSS and it seems h4 is quite similar to h5, so h3 is probably the best to go.


How to create a rich text editor that returns html results in Flutter?

My goal is to create a rich text editor that returns html results. I am using the package flutter_quill. It can only return plain text using _controller.document.toPlainText() and json using _controller.document.toDelta().toJson(). Are there any other rich text editors that can return html results or any way to return html results in flutter_quill? Appreciate if someone can advise. Thank you in advance!

I finally found a solution!
I am using the following code to return html results:
final convertedValue = jsonEncode(delta.toJson());
final markdown = deltaToMarkdown(convertedValue);
final html = markdownToHtml(markdown);

what library to use deltaToMarkdown and so?

@mycar98765 @dragongesa https://pub.dev/packages/vsc_quill_delta_to_html provides a robust delta to HTML conversion.


[CARBONDATA-1088] Minimize the driver side block index.

retest this please

retest this please

Closed as this is refactored in new PR https://github.com/apache/carbondata/pull/958


hapi unit tests are flaky

While running tests for a PR that is unrelated to hapi, its unit tests are frequently failing.

Addendum -- this isn't related to hapi itself, just that we test so many versions of it (8 - 16)


[META] Set OpenSearch 3.0.0 baseline JDK version to JDK-21

Please describe the end goal of this project
Currently, the 3.0.0 baseline JDK version is set to JDK-11. The Apache Lucene 10 is going to require JDK-21 and it would make sense to align the OpenSearch JDK baseline requirements with that.
In order to make the migration as painless as possible, the suggestion is to start from dependent components (plugins, clients, extensions, libraries) and finish up with core, for the following reasons:

if we change core to JDK-21 baseline (bytecode), it will break all and every dependent component
however, because we always build core with JDK-21 (and bundle it in as well with JDK-21), there won't be any issues dealing the dependent components that are on JDK-21 baseline

Supporting References
Please see https://github.com/opensearch-project/OpenSearch/issues/10745
Issues

[ ] #14010
[ ] https://github.com/opensearch-project/common-utils/issues/668
[ ] https://github.com/opensearch-project/security/issues/4407
[ ] https://github.com/opensearch-project/job-scheduler/issues/636
[ ] https://github.com/opensearch-project/reporting/issues/1002
[ ] https://github.com/opensearch-project/observability/issues/1830
[ ] https://github.com/opensearch-project/sql/issues/2713
[ ] https://github.com/opensearch-project/security-analytics/issues/1056
[ ] https://github.com/opensearch-project/data-prepper/issues/4605
[ ] https://github.com/opensearch-project/anomaly-detection/issues/1223
[ ] https://github.com/opensearch-project/k-NN/issues/1729
[ ] https://github.com/opensearch-project/opensearch-plugin-template-java/issues/70
[ ] https://github.com/opensearch-project/alerting/issues/1565
[ ] https://github.com/opensearch-project/performance-analyzer-commons/issues/75
[ ] https://github.com/opensearch-project/ml-commons/issues/2503
[ ] https://github.com/opensearch-project/cross-cluster-replication/issues/1393
[ ] https://github.com/opensearch-project/neural-search/issues/775
[x] https://github.com/opensearch-project/flow-framework/issues/729
[x] https://github.com/opensearch-project/opensearch-sdk-java/issues/998
[ ] https://github.com/opensearch-project/performance-analyzer-rca/issues/555
[ ] https://github.com/opensearch-project/opensearch-hadoop/issues/472
[ ] https://github.com/opensearch-project/search-processor/issues/225
[x] https://github.com/opensearch-project/custom-codecs/issues/153
[x] https://github.com/opensearch-project/asynchronous-search/issues/581
[ ] https://github.com/opensearch-project/opensearch-learning-to-rank-base/issues/36
[ ] https://github.com/opensearch-project/geospatial/issues/659
[ ] https://github.com/opensearch-project/opensearch-oci-object-storage/issues/60
[ ] https://github.com/opensearch-project/notifications/issues/924
[ ] https://github.com/opensearch-project/index-management/issues/1181
[ ] https://github.com/opensearch-project/performance-analyzer/issues/659

Related component
Build

@msfroh @andrross @dblock @getsaurabh02 fyi folks :) kicking off the campaign ...

@reta Quick question on this.
In response to this campaign, I updated our compatibility from JDK 11 to JDK 21 like this:
java {
    targetCompatibility = JavaVersion.VERSION_21
    sourceCompatibility = JavaVersion.VERSION_21
}

Our normal development flow is to merge to main and backport to 2.x, which still supports earlier JDK's.   I can see the potential for someone introducing code from a JDK between 12 and 20 (logically, 17) such as text blocks, switch expressions, records, and my new favorite stream operator, toList().   They'd pass muster on all our main branch CI but fail the backport and require substituting alternate code.   Currently we limit this just to a very few differences to keep backporting simple.
I'm curious what the best approach here is.  Can we keep targetCompatibility as 21 to address this campaign while still requiring sourceCompatibility of 11 to make sure backporting goes smoothly and doesn't diverge too much?
Or if we're keeping both, it seems this style may be more broadly applicable and recommended here. Thoughts?
tasks.withType(JavaCompile) {
    options.release.set(21)
}

@dbwiddis See some more discussion here: https://github.com/opensearch-project/custom-codecs/pull/154#discussion_r1629998769
The risk is that some new language features will be exposed by a library using JDK21 as a baseline (i.e. Lucene) and that won't work smoothly if your source compatibility is lower than that. I'm not totally sure what those risks look like in practice though.

The risk is that some new language features will be exposed by a library using JDK21 as a baseline (i.e. Lucene) and that won't work smoothly if your source compatibility is lower than that. I'm not totally sure what those risks look like in practice though.

Agreed that it's not clear what the risks are.   I think there are other options (e.g., ForbiddenAPIs) for enforcing lower-JDK source standards, so I'll look into those to address the risk of "dang, my backport failed".  And evaluate whether it's more effort to prevent it than to just fix it when it breaks...

I'm curious what the best approach here is. Can we keep targetCompatibility as 21 to address this campaign while still requiring sourceCompatibility of 11 to make sure backporting goes smoothly and doesn't diverge too much?

Thank you @dbwiddis , additionally to what @andrross said, I think the benefits of using new language features (as well as standard library) outweigh the inconvenience of manual backports (otherwise the legacy will always hold us back). Surely, there is also an option to use baseline constructs  (JDK-11) without lowering the source compatibility levels.


Refactor code for better readability and memory consumption

[ ] Add unwrap_or_default for conditional statements which unwrap to a boolean
[ ] Reduce clones and object ownership transfers like PermissionHandler::fetch_and_store(.. try using references
[ ] Reduce clone for appId, method references in CallContext like ctx.clone().app_id replace it with ctx.app_id.to_owned

All of these issues have been address in the linked PR


sql endpoint for grad school

Fixes #585
Still waiting for full confirmation from Matt, but I wanted to get this out for review as we're nearing the end of the etda cycle.
Proposed agreement is that we will make a json export available of all graduate data & Matt will filter it programmatically on their end to get the relevant access ids with possible reevaluation of this down the road.
Small detail but I was also considering renaming ExportCsv to ExportReport since this is exporting json instead. Thoughts?

Fixes #585
Still waiting for full confirmation from Matt, but I wanted to get this out for review as we're nearing the end of the etda cycle. Proposed agreement is that we will make a json export available of all graduate data & Matt will filter it programmatically on their end to get the relevant access ids with possible reevaluation of this down the road.
Small detail but I was also considering renaming ExportCsv to ExportReport since this is exporting json instead. Thoughts?

I support renaming ExportCsv to ExportReport


Rollout discovery and execution for pytest and unittest behind experiment

Once debugging is working correctly on the rewrite then the rewrite should be put behind an experiment and slowly rolled out to users to gather feedback.

closed by https://github.com/microsoft/vscode-python/pull/21258


Extensions.DependencyInjection: Existing services in container are cleared when registering in host

The use case is creating a container and registering components before registering it with the host. The naming sub-system is replaced, and all existing components are cleared.
The following example fails:
public interface IFileSystem
{
}

public class FileSystem : IFileSystem
{
}

public interface ICustomFileWriter
{
}

public class CustomFileWriter : ICustomFileWriter
{
	public CustomFileWriter(IFileSystem fileSystem)
	{
	}
}

public class Startup
{
	public void Configure(IApplicationBuilder app, ICustomFileWriter writer)
	{
            // ICustomFileWriter fails to resolve
	}
}

public class Program
{
	public static void Main(string[] args)
	{
		var container = new WindsorContainer();
		container.Register(Component.For<IFileSystem>().ImplementedBy<FileSystem>());

		Host
			.CreateDefaultBuilder()
                        // Register our own container
			.UseWindsorContainerServiceProvider(container)
			.ConfigureServices(x => x.AddSingleton<ICustomFileWriter, CustomFileWriter>())
			.ConfigureWebHostDefaults(x => x.UseStartup<Startup>())
			.Build()
			.Run();
	}
}

@robertcoltheart the changes I made to the WindsorServiceProviderFactory opened up for a base, and hence you can substitute.
In this base, you can override the AddSubSystemToContainer.
Would this not help you. I.e. you make your own WindsorServiceProviderFactory implementation. One could argue that resetting the container makes it "conforming".

Yes, there are definitely ways around this. My point is that if you are using the IHostBuilder extensions, namely UseWindsorContainerServiceProvider(this IHostBuilder hostBuilder, IWindsorContainer container), then the implication is that you can use your ready-built container in the ASP.NET Host.
What actually happens, however, is that all your components are are wiped out because the naming subsystem is replaced. If there is a cleaner or better way to make this more obvious, or work around for this, I'm happy to submit another PR.

Hi @robertcoltheart
Yes i know they get wiped. This is why I fought to get the container exposed.
So before there wasn't even a work around for it..
I like your change, if @jonorossi thinks it is good, it will also solve issues for me!

@robertcoltheart when i got the container exposed in the service provider factory this was the only workaround i could get implemented:
I think your fix might be better...

I have a viable workaround, which is to create the container, and immediately create a WindsorServiceProviderFactory, which sets the naming subsystem. After that I can configure my container, and finally add it to the host builder. So I'm happy with this approach for now. Someone that may know the inner workings of Windsor better than me might be able to attempt to solve this without using a new naming subsystem.


Add eeue56/elm-html-test to whitelist

@evancz @eeue56 per our discussion this morning

Things to think about:
The end goal of stringify

stringify is used so that we can get a string to pass to the decoder found here
this allows us to turn the JS objects used by the virtual-dom implementation into pure Elm constructs, allowing for testing

Notes on the dangerous of stringify

Json.stringify on a function returns undefined. Not a problem for this package since we limit it to Html a, and that works with Nodes, Custom, and Text - it's not possible to get undefined as a root value.
Functions get stripped out from objects with stringify. We could use identity : Html msg -> Json.Value, but that would preserve the functions inside Html - hence why using stringify instead.
Stripping functions is important to ensure the JSON data is actually JSON

I don't fully get why it's important to turn the functions into undefined, which is also not in the JSON specification. Either way, I do not think you should be handing out anything that comes from this conversion. That should all be internal (since it is 100% not a public API!) and any JSON you produce should be stuff you make.
Anyway, it should be possible to publish now!

I don't fully get why it's important to turn the functions into undefined, which is also not in the JSON specification.

There was some edge cases I found where it could end up with bad things happening by accident - but I don't remember them off the top of my head. If I remember I think I'll make issues against core, because it was a problem with decoding/encoding.
Thanks for merging! This is great.


Fix FloatingPanelBehavior.swift typos

Hi @SCENEE, thank you so much to keep improving this library 😍.
I'm still playing with it, and I just spotted a couple more typos, so here's the fix 😊

Thank you, @zntfdr!


information about organizing elements?

It seems by default that in all the examples I see, you can only stack elements one on top of the others. Is there a way to flow things side-by-side? Is the expected idea that you nest containers and each container only has vertically stacked content within itself, so you'd do two nested containers in a parent container to get side-by-side content?
This is a bit unclear and not demonstrated as far as I've noticed. Lots of the documentation gives the vibe that there's some sense of content flowing, but I still am unsure how that is supposed to work and it hasn't worked exactly as expected.

I went ahead and inferred stuff from some examples and made some guesses and have found that using child gui-flex-container wit flex-direction as row allows putting horizontal elements, while putting flex-direction for the outer gui-flex-container as column allows stacking the rows. Should have an example of this in the main demo and info in the docs, but working fairly intuitively.

I went ahead and inferred stuff from some examples and made some guesses and have found that using child gui-flex-container wit flex-direction as row allows putting horizontal elements, while putting flex-direction for the outer gui-flex-container as column allows stacking the rows. Should have an example of this in the main demo and info in the docs, but working fairly intuitively.


OAuth 2 Plugin: Does not support HTTP GET for authorize/token endpoints.

Summary
It appears that the OAuth plugin doesn't support  GET for the authorize/token endpoints.  I can successfully use POST, but when I attempt something similar to this:
curl -G https://kongsvr:8443/api/myapi/oauth2/authorize \
      -d "client_id=890cd79ec574458d923111f11fd6f29c" \
      -d "response_type=code" -d "scope=email"     \
      -d "provision_key=723e091e9dc8467187d5cf71449b8d59"  \
      -d "authenticated_userid=userid123"  --insecure

I get the following error:
{"error_description":"The access token is missing","error":"invalid_request"}

I see a similar response when using GET and the token endpoint.
As I understand it, the OAuth2 spec implies that authorize and token must support GET and can optionally support POST.
Steps To Reproduce

Configure OAuth plugin for API and Consumer
Issue a GET to the authorize endpoint per the description.
Verify that the call fails with "Access Token is Missing"

Additional Details & Logs

Kong Version: 0.8.3
CentOS 6

0.9 has quite some oauth fixes, can you try whether your problem still exists with the latest RC?

The two methods are intentionally only available with POST because GET requests with credentials are insecure since they log parameters in log files. Also I personally prefer to use POST to create new entities like authorization codes or access tokens (GET shouldn't change the DB state as per the HTTP best practices).

The reason why /authorize is not GET it's because it's a slightly different method that makes the Kong OAuth 2.0 possible, so it's not 1:1 compliant to the spec. We had an internal talk to change the name from /authorize to something else (suggested by @nikz).

@thefosk I missed the token endpoint being POST only.  Is it possible to have the documentation updated then to highlight the reasoning (Kong logs params) and the difference (provision_key) between Kong's authorize and the spec's approach?  I think if the docs were clarified, it would be helpful.

Also, I'd add that I have no problem with keeping the authorize name.  I've seen other implementations of OAuth authorize that include custom params such as provision_key.

@tbrownMT yes - I will keep this issue open as a reminder to write some more docs around it.

Fixed by https://github.com/Kong/kong/pull/6594, where we added support for GET requests


Populate Inspector-ready components

Will start populating with components that would do well from the Inspector (i.e., have an immediate visual effect that don't need to be composed with other components).

[ ] ocean
[ ] particle-system
[ ] physics

There are other great components that function better from code/HTML...we can perhaps add those after.

I've pulled physics into its own repo, aframe-physics-system (better ideas on naming?), with the exception of kinematic-body.  I'm going to put kinematic-body into aframe-extras.misc instead, to discourage it more actively for VR apps.

That sounds good, want to do the honors of updating the registry?


Add Shandong University of Science and Technology

website: www.sdust.edu.cn

@rizaust Pull request merged. Thank you!


feat: ✨ add healthcheck ingressRoute

What does this PR do?

This PR introduces an IngressRoute for health checks, addressing the specific requirements of running in a constrained environment. The proposed changes are in alignment with the project guidelines and seamlessly integrate with the existing codebase. By incorporating this IngressRoute.
Motivation

I'm Deploying private clusters that are behind an Application gateway that has backend probes to check the health of the LoadBalancer (internal load balancers in azure), due to constraints and personally wanting to make it easier for me and everyone to easily get a healthCheck up and running on the desired entryPoint (in the values.yaml I left the entryPoint as traefik so the healthCheck isn't exposed externally).
More

[x] Yes, I updated the tests accordingly
[x] Yes, I ran make test and all the tests passed

Hello @muandane,
Thanks for this PR.
FTM, I have two questions:

Why do you think it should be enabled by default ?
Why did you not use extraObjects ?

Hello @mloiseleur,
Yes it's not enabled by default since it has the same value capabilities as the Traefik dashboard but also has the same easy way to create an ingressRoute for a healthCheck exposed on whatever entryPoint you need as for the second question tbh i didn't check the extraObjects part since i'm using Ansible tasks to deploy Traefik sometimes it gets constraining on what values i can deploy.
btw the AKS cluster is a private one.


Uploading a layer with an unsupported version number should alert the user

If the user uploads a layer file with a version number that is not the current layer version expected by the ATT&CK Navigator, an alert should display which states that some of the layer configurations may not be restored and that the default value will be used in those fields.

An alert is now present upon loading a layer with a version that isn't equal to the version the Navigator used. Pushed to develop.


Create programming-books-my.md

Added an option for Malaysian
Added programming books that can be bought by Malaysians!

Could you also rename the file from programming-books-my.md to free-programming-books-my.md so it's consistent with the rest of the repository?

Added programming books that can be bought by Malaysians!

Just comprehended this actually!
Sorry, this repository is just for free programming books! Not for books that people can buy.
If you can find an official or first party source for any of the books, you're more than welcome to add them. But please don't add books where users have to pay, or are required to have a working email address.
You can get more guidance on the formatting and conventions in this repository by checking out the contribution guide (CONTRIBUTING.md).


fix(cli): fix entrypoint validation when running with npx on some packages with alpha API.

Fix an unsupported corner case that prevented the entrypoint validation to run in the export-dynamic-plugin CLI command for backend plugins with the new embed-as-dependencies option.

/lgtm
/approve


[JOSS review] Improvement to automated tests

Automated tests are provided covering input checking. All of these appear to be 'negative tests' i.e. based on expect_error().

[x] I'd suggest that the authors also implement tests that check the code provides correct output when provided with correct inputs.

This issue is part of JOSS review https://github.com/openjournals/joss-reviews/issues/634

Dear @pboesu
Thanks for the comments on tests. I added some positive tests on the correct output by expect_true()
Best
Fei


[#27712] PowerToys New+ v0.1

Summary of the Pull Request
This PR contains the first very early version of New+ (#27712)
New+ is a new PowerToys for the File Explorer that enables users to create files and folders from a personalized set of templates.
Issue:
https://github.com/microsoft/PowerToys/issues/27712
Spec:
https://1drv.ms/w/s!AgfnseFPEL1w2NklIIJb2hDgHkz6MQ?e=b8rSuL
This PR includes:
• Early version of New+
• New+ Windows 11 File Explorer support
• Dark and Light System Theme support
• Logging + Trace
• New+ GPO settings
• New+ Settings page
• New+ What's new page
• New+ example templaes
• New+ uninstall support

[ ] Closes: #27712
This doesn’t close #27712 yet

[X] Communication: I've discussed this with core contributors already.

[X] Tests: Added/updated and all pass

[X] Localization: All end user facing strings can be localized

[ X] Dev docs: Added/updated

See also https://github.com/MicrosoftDocs/windows-dev-docs/pull/5065

[X] New binaries: Added on the required places

[X] JSON for signing for new binaries
[X] WXS for installer for new binaries and localization folder
[X] YML for CI pipeline for new test projects

No new test projects yet

[ ] YML for signed pipeline

Don't think any changes are required

[X] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #5065

See also https://github.com/MicrosoftDocs/windows-dev-docs/pull/5065

Detailed Description of the Pull Request / Additional comments
• Added System Theme to ThemeHelper.h/.cpp and renamed AppTheme enum to Theme

Validation Steps Performed
• Ran all unit tests except for UITests-FancyZones, UITests-FancyZonesEditor
• Removed all default settings
• Tested that defaults are same via Settings or just via invoking File Extension for the first time
• Removed new+ template folder
• Removed all items in new+ template folder
• Changed template folder location via settings
• Changed hide extension via settings
• Changed dark and light system themes
• Basic test of Keyboard manager with different app theme
• Basic test of PowerRename with different app theme
• Toggling New+ via GPO settings
• Installing and uninstalling
• Uninstall only uninstalls example templates, does not uninstall user created templates

@microsoft-github-policy-service agree

You can't just extend the normal new menu by added custom types with ShellNew registry entries? The ShellNew key let's you fill the file with data automatically, run custom commands etc.
Even the original classic TweakUI PowerToy let's you customize the new menu...

You can't just extend the normal new menu by adding custom types with ShellNew registry entries? The ShellNew key lets you fill the file with data automatically, run custom commands etc.
Even the original classic TweakUI PowerToy lets you customize the new menu to remove items you don't want and to add new templates.

Thank you @whindsaks for the comments.
Yes, I too remember the classic TweakUI PowerToy :-)
New+ is an attempt at making customizing file and folder creation even easier, while adding a few features along the way.
I've just added an incomplete FAQ to the New+ spec:
https://1drv.ms/w/s!AgfnseFPEL1w2NklIIJb2hDgHkz6MQ?e=dLdjxK
(spec also contains incomplete ideas on what we should be made better in the future)
Love your thoughts and ideas on:

Features of New that you use all the time that you think isn't accounted for?
Example templates that we should include by default to help inspire users?
Other ideas that we should do to make the context menus in Windows more powerful?

Anything else

Thanks!

If you tweak the registry you can make the new items look like anything you want to emulate multiple txt files etc.. If you use the FileName value, that file is copied from CSIDL_TEMPLATES and that directory is already roaming. To populate a new folder you would have to use the undocumented COM handler however.

If you tweak the registry you can make the new items look like anything you want to emulate multiple txt files etc. If you use the FileName value, that file is copied from CSIDL_TEMPLATES and that directory is already roaming. To populate a new folder you would have to use the undocumented COM handler however.

That's super interesting. Thank you for sharing. Definitely something to explore further. Do you by chance have any pointers to info on the "undocumented COM handler" that you'd recommend?

Handler:REG_SZ:"{CLSID}" and the shell will QueryInterface you for IObjectWithSite and some GUID I don't remember off the top of my head but if you Google it you will find the interface definition.

Merged in latest main.

What is required to get this in? Waiting for it.

Trying to get the branch to build again so we can re-review :)

I've pushed a commit to fix spellcheck entries that seemed unneeded. https://github.com/microsoft/PowerToys/pull/33136/commits/a5403e6a797ab42ca1bae41e0cbdc4e2fe59f6a2

I've pushed a commit to fix an issue I've found while testing: if all templates were folders, the samples would be copied again. https://github.com/microsoft/PowerToys/pull/33136/commits/2e072562067cc39a01ab16f4c19c607ea6545c42

I've pushed a commit so that Bug Report doesn't send the user templates inside the PowerToys settings folder, in case the user is still using the default location and might not want to link his teamplates. https://github.com/microsoft/PowerToys/pull/33136/commits/c69d94bdfc0846870bc05b542a382187d5aa9cef

I've pushed a commit to show a warning on Windows 10.  https://github.com/microsoft/PowerToys/pull/33136/commits/bcfbac2c8737c1fcbecafb075974247036f3be2d

I've added a infobox to inform users that Backup and Restore won't work with templates: https://github.com/microsoft/PowerToys/pull/33136/commits/56610a5dbf57bbffa3ec731a6be7f9960919dfa0

I've added a infobox to inform users that Backup and Restore won't work with templates: https://github.com/microsoft/PowerToys/pull/33136/commits/56610a5dbf57bbffa3ec731a6be7f9960919dfa0

I've added a commit with more specific telemetry names: https://github.com/microsoft/PowerToys/pull/33136/commits/dda6cec4c1d9a09e80bff0950dd8c57671bbc7b7

@cgaarden congrats on getting this merged! I'm super stoked to see this get released.


issue #614 : Console Federate command broken by log level debug

This PR addresses GitHub issue: #614 .
Briefly describe the changes proposed in this PR:

The Console Federate command was using log level for control flow, resulting in federation failing to occur if the log level was debug or finer.

Debugging this involved updating Mockito to 2.2.0 and Logback to 1.1.7, but those changes don't seem to be related to the solution so they have been backed out due to the close release time.
Debugging also involved refactoring SetParametersTest to reuse AbstractCommandTest as designed, and included refactoring to use MockitoRule, @Mock and @InjectMocks to verify they were not related and can be maintained in future.
There is now a known baseline log level of debug setup for both FederateTest and SetParametersTest, based on their need to consistently verify console IO messages that may be affected by the log level and should function properly even at the debug log level. This is reset after each test so the global base logging level will still be able to be manipulated through a configuration file as necessary for other tests.
Fixes #614
Signed-off-by: Peter Ansell<EMAIL_ADDRESS>

I am running the full testsuite locally to verify that the changes didn't break anything else but that is unlikely given that the version bumps have been backed out now.

All tests are passing for me after these changes, where the FederateTest was failing for me previously.


Add rebase scripts

Change-type: patch
Signed-off-by: Giovanni Garufi<EMAIL_ADDRESS>

@wrboyce good catch man, I didn't even notice as yq will just work on json. Updated the PR with a commit that fixes this, I'd rather be consistent and use jq only for json

I didn't even notice as yq will just work on json.

I had no idea! TIL.


[WIP] Add a tutorial for the ParameterEventHandler class

This tutorial depends on the following functionality https://github.com/ros2/rclcpp/pull/829, which must be integrated before this PR.
Signed-off-by: Michael Jeronimo<EMAIL_ADDRESS>

CI is failing because there is a bunch of trailing whitespace in the tutorial.
Also, is it safe to say that this tutorial is only going to work in Galactic?  If that's the case, we need to make very sure it says it at the top, otherwise we'll get people confused if they are using Foxy or earlier.
Finally, would you mind pushing this branch to your own fork and opening the PR from there?  I'm trying to cleanup the branches on this repository.

Yes, Galactic only; I'll add that. I'm remove the whitespace, push to a fork, and re-submit.

Closing now that #1123 is open.


Change s_enclaveProviders to ConcurrentDictionary

Fixes #1444

Could you include a test?

Could you include a test?

Any suggestions on how to consistently force concurrent access to s_enclaveProviders?

My suggestion here is to provide the race condition by sending parallel requests to s_enclaveProviders blended with delay and async call.

My suggestion here is to provide the race condition by sending parallel requests to s_enclaveProviders blended with delay and async call.

Again, that doesn't consistently force concurrent access. I think the use case for a test should be reproducible on every run. I don't mind adding it but it wouldn't add any value imo. Essentially the test would just be verifying whether a ConcurrentDictionary is actually thread-safe.

In this case it could be a candidate for stress testing.
Just to be more precise, the extension methods thread safety hasn't been guaranteed.


Allow deleting classes from transformers

This can be useful for a couple of reasons:

Removing redundant class files between common / platform code (not ideal)
Removing unnecessary template files from the shadowed common code

I have tested these changes using a modified version of the Gradle plugin to support the new refactor for 5.0. I can confirm that everything is working as expected, The only downside of course is that you can't remove classes after they've been loaded. Only before.
An alternative solution is to not ignore when the ClassEditTransformer returns null and instead remove the file. I am of course open to discussion on this issue and can make any changes needed to meet your expectations.

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

Looks like the build failed due to permissions.
Received status code 401 from server: Unauthorized

Anything I can do about that?

I would instead want ClassEditTransformer support deleting it instead, or make ClassDeleteTransformer use the same node to avoid reading it twice

And by support it, you mean allow returning null? I can make that change tonight.

Yes that or make the delete transformer not read the class the second time

That should be pretty straightforward. I'll give that a try in just a bit.

I have updated the transformer handler to only read classes a single time each. I also took the liberty of refactoring the class and cleaning it up quite a bit to facilitate that. Hope that's okay. This should solve both of the problems we were discussing earlier.


Wrong placing of -Xmx option  in console.sh

The setting of the -Xmx option in the SSL_OPTS inside console.sh is  problematic:
because this is overriding any other option set in the JAVA_OPTS variable
p.s
Also, could you just stick with reserving the ORIENTDB_OPTS_MEMORY or any ORIENTDB_OPTS variable in all your .sh scripts for the user to set.
I've found an incoherent use of those variables, which range from ORIENTDB_OPTS_MEMORY,  JAVA_OPTIONS and JAVA_OPTS, depending on the script among console.sh, server.sh and gremlin.sh.
Thanks

Thank you for this issues, we need a cleanup of the scripts.
If you want, feel free to provide a PR on the develop branch.

Current console.sh is:
#JAVA_OPTS=-Xmx1024m
SSL_OPTS="-Xmx512m -Dclient.ssl.enabled=false "
exec "$JAVA" -client $JAVA_OPTS $ORIENTDB_SETTINGS $SSL_OPTS \
I suppose that a simple fix would be:
JAVA_OPTS=-Xmx512m
SSL_OPTS="-Dclient.ssl.enabled=false "
exec "$JAVA" -client $JAVA_OPTS $ORIENTDB_SETTINGS $SSL_OPTS \

@cmassi not really, one should at lease check whether $JAVA_OPTS is already set before overwriting

memory settings split on dedicated variable


Adding installcredprovider.ps1 to MicroBuild signing targeted files.

This PR should result in installcredprovider.ps1 being signed by MicroBuild during the credential provider build process. The primary benefit of this is the signature of the script can be checked before installation.

/azp run


[Release-1.0] Design and build comments section

General
Grüvee will be utilizing commenting per song. This is outlined in the MVP and has designs setup for it. Currently there are sketch designs that have been created. This issue is to finalize the design and develop the ui/ux for Android and iOS.
Tasks

[ ] Finalize UI/UX in Sketch
[ ] Generate a component that can handle the comments
[ ] Setup an action to open and close comments section and/or pop an overlay for comments
[ ] Verify design is functional on both Android and iOS

Screenshots
Here are the current ideas for the comments section:

Spent most of today trying to deal with the height issue when adding the comments section to our songitem. A lot of things going on here, but basically we need to set the height on the SwipeRow component. This seems to have some implications for the playlist list view that we will also need to look into.
There is also potentially a bug in the SwipeRow library we are using, but with the method listed above we can get around it

We are having a lot of issues with nested scroll views. TL;DR can't scroll a FlatList inside another FlatList which is essentially what we have. There is a solution here: https://github.com/facebook/react-native/issues/1966
There is also another option to change how we render the comments sections. We can push out to a new view or even set an overlay. This might be the preferred option.

Alrighty, decided to go to a completely different view for comments. In the process of designing the flatlist view and adding in the proper actions

Make sure to hide delete action if the comment was not written by you
Fix delete action not being fully hidden
Setup proper state

Next things needed here are:

Add comment section
Update state for newly added comments
MAYBE add ability to like comments / ability to reply to specific comments

COMMENTS ARE LIVE. Checking to make sure this works on Android is next and then we can MOVE ONE.

WE DONE FAM.


embed: document go.mod exclusion

We have a use case for serving example go projects via go:embed. This is particularly important as alternatives to go:embed have less maintenance now that they are obviated. The problems is that the file go.mod is special cased and prevents serving a directory that contains it.
@opennota did research here and found this behavior to be intentional, notable "stopping at module boundaries" https://github.com/golang/go/issues/41191#issuecomment-805431807
When serving static assets, module boundaries may not be important and in fact be a surprising limitation, as surprising as files outside the directory or via symbolic links might be. Right now, the latter constraints like symbolic links are documented, but go.mod, and why it doesn't work is not entirely obvious.
Ideally, there could be a way to allow go projects to serve go projects as static assets via go:embed. Until then, it would be handy to change the documentation to note this surprising constraint explicitly, as it would save folks time and head scratching.
Ex a line like this "Matches for a directory containing "go.mod" is invalid and fail to build".
What version of Go are you using (go version)?
1.16.2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
amd64 darwin
What did you do?
//go:embed /path/to/goproject/*
var exfs embed.FS

What did you expect to see?
I expected to have go build not fail
What did you see instead?
An error like "pattern X: cannot embed directory Y in different module"

Note that the primary distribution mechanism of modules are zip-files, which will only include the files that are considered part of the module. As I understand it, the zip you download from the module proxy (as opposed to using the repo) won't contain the nested module. So, module boundaries are very important - you can't embed a file that isn't there.
A workaround for your case is to name the file differently - e.g. go.mod_ - and rename it after the fact by wrapping the embed.FS.

Name rewriting seems to come up a fair amount as a workaround for edge case problems with embedding. Someone should write a module to wrap an io.FS in a name rewriter. I volunteer to click the star button on Github and then link to it in comments when someone brings up an issue solved by rewriting, when someone else creates it.

/cc @rsc

one problem with the rename go.mod to go.mod_ approach is that running go mod tidy in the root, ends up importing whatever is in go.mod_. I'm not sure how to work around this, but it is annoying.
It would be nice to have a clean way to allow go:embed to opt-out of interpreting go.mod...

It would be nice to have a clean way to allow go:embed to opt-out of interpreting go.mod...

That can't work. It would mean your module can't be build from the zip-file uploaded to the mirror. Third-party embedding solutions don't have this problem only because they generate code which is compiled in - so they effectively create a copy (but in Go syntax) of the files from the nested module in the current module, so it's not a problem if the nested module isn't distributed.
This really can't be solved on the //go:embed side, as far as I can tell. It might be possible to add a way to distribute subdirectories with a go.mod without interpreting them as a module - I don't know. But as long as the files are not part of the module, //go:embed can't use them, full stop.

great explanation, @Merovius. I didn't quite get it last time, but I do now, both the what and the why. awesome!

I ran into this and decided to use go:generate to tar the embedded module and then include the tape-archived file. It worked. https://github.com/crhntr/disaster-recovery-acceptance-tests/blob/embed-fixtures/fixtures/fixtures.go#L22-L28

For the record, there are zip and txtar fs.FS implementations.

My use-case is that I'm building a server (in Go ofc) that serves Go projects as downloadable zip files. I have a workspace structure like this:
go.work
go.mod
main.go
projects/
  project-1/
    go.mod
    main.go

I want the top-level main.go to be able to embed nested project directories so I can zip them up at runtime and serve them over the wire. The reason it's convenient to keep the nested file named go.mod is because the go.work file at the top of the repo makes it easy to make updates to those nested projects without breaking tooling.
Are there any simple solutions for what I'm trying to do here? It would be so nice if there was a directive that allowed nested modules to be embedded (esp because they aren't a part of the package embedding them, they are essentially flat files)

it really is interesting, you can embed any kind of code (python, rust, c#, ...)
but you can't embed go code, and to be precise, you can embed go code, but not if you use go.mod
my solution (and it is a bad solution) is to have a makefile that

rename go.mod to go.mod.embed (then internally while serving i rename it back) - then you can embed it
do a go build with embedded go files
rename go.mod.embed back to go.mod
purely because only go code projects are making problems (to repeat again, all other languages you can embed)

ziping it seems awkward although a bit easier to to.
newly added gonew tool is also not a good solution (but it is a good option) because does not support air-gapped environment

While I'm sure the documentation could be improved, this is already documented.  The docs already say "Patterns must not match files outside the package's module".  If a subdirectory has a go.mod file, then it is by definition in a different module.

In go 1.18, the prefix "all:" has been added for the embed directive, to include dotFiles (for instance). However, go.mod directories are still not included. Maybe the "all:" prefix could also include these files too.

as explained above, modules inherently cannot contain other modules.

One thing which makes it weird is that AIUI the contents of testdata directories are not compiled so they should not be considered modules, but they still are.
/
/go.mod
/demo.go
/testdata
/testdata/go.mod
/testdata/other.go

In this layout, testdata is skipped by ./... patterns like go list ./... but if demo.go tries to embed testdata/ it is still considered as another module although it is not handled as code.

"Not being compiled" is not the same as "not being part of the module". They are still used in tests and tests can be run on downloaded modules, so testdata needs to be included in the module zip.

the last referenced CL will close this out to my satisfaction. thanks!


This change fixes incorrect behavior of stack elements cache.

Change of data structure from Stack to Deque (LIFO to FIFO) in this commit https://github.com/apache/logging-log4j2/commit/97f3153b73ab071a69c2e61e0130fd0104d45407 broke cache logic. This bug causes a major performance regression.

I created a small local project to reproduce the issue. I can attach it if needed.
P.S. I signed ICLA and got a confirmation, but haven't got any response to my request to create a JIRA account, so can't create a bug.

StackLocator is a complex feature with several different paths, so maybe I'll add a cheatsheet for the unity tests:

the StackLocator#getCurrentStackTrace version in log4j-api-java9 is used when running Java 9+. The tests are in the same module.
the StackLocator#getCurrentStackTrace version in log4j-api is used when running Java 8. It uses two implementations:

the fast path provided by PrivateSecurityManagerStackTraceUtil needs to be tested in the log4j-api-test module (in a "normal" *Test class),
the slow path requires running the test with a security manager enabled. The test should be in the log4j-api-test module and be named *IT. The reason behind this is that "normal" tests in log4j-api-test run in parallel. Setting a security manager is a very disruptive operation, so we have a second test execution that runs *IT classes with a JVM-per-test configuration.

I had quite hard time developing unit test for this class as it contains only static and private static methods. Final test verifies items in cache after executing "toExtendedStackTrace" method. Please provide your feedback and ideas.
I will work on integration test for StackLocator

@alex-dubrouski,
Feel free to change private methods to package access. I think that we just need to test that StackLocatorUtil#getCurrentStackTrace() returns a Deque that has the calling class as first element.

Are you sure calling class should be the first? Screenshots from test project I attached before have calling class as the last element (index 26)

Yes, I would expect the class that called StackLocatorUtil at the lowest index (or at least near the top), while the class that initiated execution on the thread (JUnit?) at the end.

Yes, I would expect the class that called StackLocatorUtil at the lowest index (or at least near the top), while the class that initiated execution on the thread (JUnit?) at the end.

Java9 StackLocator uses "add" method which is for ArrayDeque equals to addLast, so it works as expected. Plus it has a unit test that verifies order of elements already (https://github.com/apache/logging-log4j2/blob/release-2.x/log4j-api-java9/src/test/java/org/apache/logging/log4j/util/java9/StackLocatorTest.java#L60). It also uses WALKER by default as "PrivateSecurityManagerStackTraceUtil.isEnabled()" always returns False. I assume it means we can skip additional tests for Java9 code

Hi @ppkarwasz
I am sorry for bothering, is it possible to merge this PR and release a new patch version? We would like to upgrade our applications.

Hi maintainer team, we are blocked on the availability of new log4j version with this patch for our service upgrade due to transitive dependency on slf4j-api 2.0.6 (slf4j-api 2.0 is released in Aug 2022, and hence should require log4j > 2.18 to work, and notice that we have recent log4j patches from January to accommodate slf4j). Do you know when the next log4j version release would be available for consumption?

@jitheshtr,
You should ask on the log4j-user mailing list.
As far as SLF4J-to-Log4j2 API support goes, nothing relevant happened since the release of 2.19.0. SLF4J-560 should be of no concern to end users.

@alex-dubrouski,
Thanks for your contribution. Our snapshots are generated after every CI run on https://repository.apache.org/content/groups/snapshots/. Can you check if 2.19.1-SNAPSHOT solves your problem?

@ppkarwasz,
We ran JMH benchmarks and results are promising, but we can't use snapshots in Production applications. That's why we have to wait till next GA release.
Thanks

@alex-dubrouski,
Sure, I was just double-checking that the next release will fix the problem.
We are currently in the process of wrapping version 2.20.0 up, so that we can concentrate on rendering StackLocator obsolete (see apache/logging-log4j-transform#1) and replace it with compile-time weaving. That should boost performance even further.

Hey @alex-dubrouski - Great job on this!  Thank you.


mapStreamM

The following function is useful (i have used it a few times):
mapStreamM :: Monad m => (a -> Stream (Of b) m x) -> Stream (Of a) m r -> Stream (Of b) m r
mapStreamM f = S.concats . S.mapsM (\(a :> s) -> return (f a >> return s)

Do people think this would be a good addition
Is there a better implementation
Is there a better name

What's the difference with for? They have somewhat similar signatures.


Fix gpg key checking warings after f588f26

Use the full fingerprint for all keys to silence the warning.

How did we miss this :dizzy_face:. Sorry!

thanks @paroga !


[Feature][Engine Starter] update SeaTunnel Starter and change -e to -m

Purpose of this pull request
refer to https://github.com/apache/incubator-seatunnel/issues/3674

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

Sorry, I accidentally made a mistake.

Sorry, I accidentally made a mistake.

It's no matter, thank you for your review.

@FWLamb Hi, Please fix ci problem. Thanks

@FWLamb Hi, Please fix ci problem. Thanks

I'll fix it later. Thanks!


No configuration available for Fibaro FGRM222

1.6
Build/Run method
Zwave2MQTT Addon on Home Assistant
Describe the bug
No configuration option available for the FIBARO FGRM222 whereas the device exists on openzwave database (checked id and type).
Other devices are ok, except the ZWave Stick from Aeotec with no configuration
Additional context
the only difference I can see betwen the FIBARO FGRM222 and othe devices is that the code display in decimal is only 3 digits long (same for the zwave stick), maybe a problem with conversion ? (sorry it's just a guess, i'm not a programmer...)
Other information, it worked before (I can't say on which version unfortunately) and in the device list the type is not display for these devices (others are all ok)
Thank you for your help

I don't know which Z2M/OZW specific version the addon is using

it uses Zwave2Mqtt v3.0.2 in its last release.

Did you enabled the zwave setting to auto update devices db?
Did you try to send a refresh node info against that node?

Yes I tried. Auto update db is on and the refresh node info does nothing.
I have 10 FGRM222 and I just saw that the two last one I added recently have the configuration.
I guess I will have to exclude/include the others again (that's a nightmare as I can add them one by one only)
Except if there's something to solve it without include them again, let's close the point !
thank you  Roberts for the answers (and everything else)

@Oohcalme Unfortunally this kind of issues are something related to devices and I have no power with them, you should try to open this issue on OZW repo if you cannot make it work, sorry


⚠ Bofrost.hr has degraded performance

In 7b5e616, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 4446 ms

Resolved: Bofrost.hr performance has improved in 457e497 after 7 minutes.


Split components into "base" class for functionality, and "MWC" class for styling

Splitting the component classes apart this way will help with theming. If someone wants to theme an MWC component differently, or override part of the theming, they can extend the base class and only have to implement renderStyle()
The base class must not register itself as a custom element, and leave that up to the extending class.
Example:
mwc-switch-base.ts:
export class SwitchBase extends BaseComponent {
  renderStyle() {}
  render() {
    return html`${this.renderStyle()}...`;
  }
}

mwc-switch.ts:
import {SwitchBase} from './mwc-switch-base.js';
import {style} from './mwc-switch-css.js';

@customElement('mwc-switch')
export class Switch extends SwitchBase {
  renderStyle() {
    return style;
  }
}

Fixed with #290


Add instance variable which holds line in which errors happen

This PR simply adds the Line number as an instance variable. The test coverage piggy backs from existing tests to show the line numbers are correct.
Using a set ensures no line errors are repeated even if multiple validators find errors in the same line.
Would you like to add the line number to the error log? If so, where do you consider is the best place to be added if at all?

Hi! Thanks for the PR. Looks like the Travis CI integration no longer works, would you be able to resolve #75?

I don't believe I have the permissions to do so and I haven't used github actions before but I could give it a try

Let's keep these as separate PRs

@santilytics Thanks! Released in https://pypi.org/project/vladiate/0.0.24/


⚠ Fortnite has degraded performance

In 8e745ef, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1641 ms

Resolved: Fortnite performance has improved in 40df890.


[WIP] feat: Integrate codespan for error reporting

Got a few changes for codespan itself which I will make a PR for as well before this is working.

Wooo! Will have to publish to crates.io at some stage too.


E2E: Generic workflow_dispatch main default SLSA3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2492706718
Workflow name: Generic workflow_dispatch main default SLSA3
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Jun 14 04:11:37 UTC 2022

Same cause as #289

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2499656372
Workflow name: .github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Jun 15 04:01:38 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2506590505
Workflow name: .github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Jun 16 03:57:48 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2513211589
Workflow name: .github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Fri Jun 17 04:00:11 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2519116946
Workflow name: .github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sat Jun 18 03:49:25 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2522672605
Workflow name: .github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sun Jun 19 03:59:32 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2532909222
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Jun 21 04:01:54 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2539743601
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Jun 22 03:59:14 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2546903496
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Jun 23 05:24:03 UTC 2022
Tests are passing now. Closing this issue.


Parallelize project maxwellian on GPUs utilizing thread parallelism per quadrature point instead of per cell

Right now project Maxwellian on basis parallelizes over cells on GPUs, with each GPU thread handling a single cell and that thread doing the relevant quadrature point evaluations and summation to produce the solution.
Because every quadrature point is doing the same operation (evaluating n, u, T, and the Maxwellian function), we could launch a number of threads equal to the number of quadrature points and then, similar to the moments, have an atomicAdd for the final reduction per cell to produce the modal expansion (or perhaps some other construction of the final modal expansion that is thread safe).
Such a rewrite would increase the parallelism and GPU saturation by a significant factor (in 3x2v we would be launching an additional factor of 48x threads for p=1 since each phase space cell has 48 quadrature points), likely sizably increasing the performance of the project Maxwellian updater on GPUs. There may also be further gains to be had in this case from coalesced memory.

This enhancement was addressed with https://github.com/ammarhakim/gkylzero/pull/429


Filter's missing values settings are not properly synced between different tabs/views

Case 1:

Open a table, e.g. SPGI
Add another view in the same table
Open filters in both views
View 1: add numerical column, and set one of the following options:
'filter out missing values'
'show only missing values'
View 2: add the same numerical column to filters
Expected results: Adding the same column to filters in another view should not change filters state.
Actual results: missing values settings are reset:
If 'show only missing values' was selected > filter is reset completely.
If 'filter out missing values' was selected > only range set is kept, missing values are not filtered out anymore.

Case 2:

Two views are opened
Same numerical filter is present in both views
Filter is switched from 'show only missing values' to 'Keep missing values' on one of the views
Expected results: filter is updated in the 2nd view too.
Actual results: in some cases, the range filter is not updated in another view if the setting was changed from 'show only missing values' to 'Keep missing values' on one of the views

Reopened because the first case was not fixed


How can I edit markup in editor?

Hi,
I'd like to tweak the markup of the react-quill editor after a user hits the enter key.  Specifically, I'd like to add a span tag inside of the last sentence a user has entered.
I tried using the method dangerouslySetInnerHTML(), but it doesn't work.  The react-quill component strips out any markup I specifically try to inject into the editor.
Is there any way for me to override this?

Hello,
you should avoid modifying values imperatively or in-place when working with React.
Instead, do it the declarative way. Find where the newline has been added, edit your copy of the value accordingly, and pass it to the editor as a prop.
You can find where the newline has been entered by parsing the delta object that is sent during onChange, or by keeping track of the cursor in onSelectionChange and waiting for Enter during onKeyUp.

Assuming this is solved. Feel free to re-open otherwise.


What about docs?

What's the deal with documentation on this project? @StephPeets

Cool beans. Documentation

[ ] Create a new index.md document
[ ] Turn on GH pages
[ ] Createdocs folder
[ ] Decide if we want more complex documentation


[DOC] Restructures Dashboards TOC

Signed-off-by: vagimeli<EMAIL_ADDRESS>Description
Restructures Dashboards TOC
Issues Resolved
#2621
Checklist

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

Proposed TOC structure

Thanks! I agree with your suggestion.


Compile away hooks

Purely an idea, but something been thinking about a lot. One of the biggest missing DX features of Mitosis is custom hooks
Interestingly, some ppl have been exploring making hooks libraries across frameworks
If you think of someone building an app in Mitosis vs a framework like Qwik directly, you miss out on one of the main composability benefits, custom hooks. Such as a react-query like hook (called Resource in Qwik and Solids) etc. I can't see people loving building with Qwik without this key feature nearly all modern frameworks have (react, vue, svelte, qwik, solid) that Mitosis doesn't
I realized I think we can implement this for all hooks-oriented frameworks. We may even be able to implement it for frameworks without first class hooks support.
We could do it, for instance, with another convention just like we have .lite.tsx for components, and .context.tsx for context, we could make a .hook.tsx
// ./use-fetch.hook.tsx
import { useState, onMount } from<EMAIL_ADDRESS>
export default function useFetch(url: string) {
  const [value, setValue] = useState(null)
  const [error, setError] = useState(null)
  const [loading, setLoading] = useState(false)

  onMount(async () => {
     setLoading(true);
     try {
       const data = await fetch(url).then(res => res.json())
     }  catch (error) {
        setError(error)
     } finally {
       setLoading(false)
     }
     setValue(data)
  })

  return { value, loading, error };
}

which would compile to other frameworks just like you see in mitosis components name
I think translating hooks like this is pretty straightforward to everywhere that supports hooks. the big question is what about frameworks, like Angular, that don't. I have some crazy ideas for that but need to think on a little more

this as a feature could be useful standalone to those like tanstack too, to make hooks that support all hooks-oriented frameworks that you write once and it compiles out to all. and of course benefits mitosis components and libraries too

Fully agree, providing some form of "hooks" support is probably a critical next feature for Mitosis. It's been on my mind...folks need a way to encapsulate complex logic and reuse it across components. https://zagjs.com/ Does somewhat of the same thing as Tanstack (hooks lib tailored for finite state machines, with framework-specific bindings for React/Vue/Solid)

I think translating hooks like this is pretty straightforward to everywhere that supports hooks. the big question is what about frameworks, like Angular, that don't. I have some crazy ideas for that but need to think on a little more

Yeah, I'd want to lay out a rough plan outlining what this would look like in the most "important"/"relevant" 5-6 frameworks to ensure it would work in enough places (Vue/React/Svelte/Solid/Qwik). I see it working with none/very little work for react/svelte/solid, but also need to think a tiny bit about Vue. They have 2 different API styles now, there could be some quirks:

https://vuejs.org/guide/introduction.html#api-styles
https://vuejs.org/api/reactivity-core.html

Composition API is also Vue3 only I believe, so that's another thing to keep in mind.
Also concerned about how much additional scaffolding would need to go into making hooks work in webcomponents/html, which could lead to us potentially implementing a full web framework's features to get them to work.

Agree w/ all of that. And also currently don't think this is any level of priority but I have some vague ideas on how to support webcomponents/html/angularetc. Perhaps a little library could/would be needed. I could see that as an interesting project in general - framework agnostic simple hooks system that can plug into any framework that doesn't currently support it. This is a bit like how mobx works (and solidjs reactivity, etc). Not sure what tanstack and others do, I am assuming they just manually implement across but maybe they have a helper system we can draw inspiration from
But perhaps a little helper library one day is the ultimate solution. Support hooks for frameworks that support hooks (via direct compilation, no lib needed), and at some point someone can create a framework agnostic hooks primitive library that this could output to as well
Interesting to think of how a small library could bring hooks to angular and other frameworks. Could be interesting to those communities

Composition API is also Vue3 only I believe, so that's another thing to keep in mind.

FYI Vue 2.x supports the Composition API natively since 2.7 (released weeks ago). For earlier releases, you need the @vue/composition-api plugin.
Vue 2.7 Composition API works like Vue 3 Composition API, except when otherwise noted.

@leopiccionia Thanks a lot for sharing, that's very valuable information!

Imagine VueUse working in all frameworks. That would be really nice.

I think it is very important to talk about what we are translating here.  For a lot of internal and external functions in frameworks have similar features that overlap, so let's get as precise as possible.
I am trying to find the simplest, most direct equivalents, as some items on here can do all of these.

Passing data from parent to child

React props
Angular @Input
Vue props
Svelte export

These generally are just passing the data, no binding.

Passing data from parent to X grandchild

React - useContext
Angular - InjectionToken with provider
Vue - provide
Svelte - setContext with getContext

Passing data from child to parent

React - useState with props
Angular - @Output with EventEmitter
Vue - $emit
Svelte - createEventDispatcher

Basically the same thing for grandchildren:

Passing data from X grandchild to grandparent

React - useState with useContext
Angular - @Output with EventEmitter
Vue - $emit
Svelte - createEventDispatcher

Sharing data with ANY component

React - Context.Provider at the top level with useContext
Angular - providers at top level (modules or since v14 components), aka services (although not only type)
Vue - provide and inject
Svelte - stores

What are we really talking about here?

Shared State - Providing a shared function / class at the top-level component whether it be a provider in a module / component or a context function that can be called from child to keep state.  Child components may need to evoke an emitter to push the DOM changes if necessary
Caching computation - some functions like React's useCallback or useMemo can help with speed
Subscribing to changes - useState (React), rxjs observables (all Javascript but mainly Angular), or stores (Svelte)

There is really a weird combination of all three of these things in our frameworks, but I must say they are by far the easiest to work with using Svelte Stores and Angular Services along with RXJS Observables.

Other things to consider for this project:

Could be cool to have a framework that could build an APP in any framework
Routing would be perhaps the only other core feature left to translate
Everything should be translated to TypeScript. Don't make me get into this debate. It just should. Period.
Everything should be SSR ready. Don't access the DOM directly.

It would be cool to build a basic app to see how similar and exact you could get a todo app for example.
J


Publishing your results

Hello sir,
I could not find your email, so I am posting my question here; sorry for the inconvenience. You may delete this issue after reading it.
I am a bachelor student, and I'm trying to publish a paper; I was trying to train this dataset with CenterMask2, but It didn't go so well, and I could not get a reasonable result to publish a paper; I want to know if you are interested in sharing your result as a paper? I can do all work, and you just approve them, and we can send it to a  journal. If this is not something you are interested in, I totally understand. If you have any suggestions, I'll be more than happy to hear.
Best regards,
Mahdi Darvish<EMAIL_ADDRESS>

Replied on email


Issue-A0A6-I12 Publishing error in Blogs

Reference issue link: Publishing error in Blogs
On studio staging, the publish button is disabled on the post, author, and category document types even when changes are made.

Kindly verify merged changes on studio staging branch. Thanks!


Batch read query

How can I perform a Dynamo batch read?
I tried creating a query, findAllById(List<String> id), but this always returns an empty response.
Then I created another query, findByIdIn(List<String> id), and it gives the expected result. Is this query performing a Dynamo batch read?
I am using the version 4.5.7 of the library

@ankit-mandhani I think findByIdIn(List id) performs a scan on the table.
I am looking for a method which will do a query on the table for a given list of ids on a secondary index, instead of doing a scan as the one above does.


feat: ITV-55 update manager comments db

ITV-55 update manager comments db
What?
This PR updates the manager comments schema and db initialisation as well as updating both the closed-review and manager-review pages. This functionality is directly taken from https://github.com/LBHackney-IT/mat-process-thc/pull/859
For the db initialisation I essentially "reset" the app to what it should be if there were no schema migrations needed. This will need to be done for Home Check as well, but not THC.
Why?
All the Manage a Tenancy apps should have as similar functionality as possible.

I think I understand. Be good to go through this tomorrow.

I won't merge until we've reviewed it together then


How to configure the service account name with operator-sdk and OLM

Bug Report

What did you do?
I followed the instruction to create the go-lang based operator:
https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/
What did you expect to see?
I want to generate the csv file.
I expect to see the option for me to change the serviceaccount from the default to any name I like.
What did you see instead? Under which circumstances?
There is no option for me to change the service account name. I tried to manually change it in the yamls under config/rbac, but it did not work when I ran make bundle to generate the csv file.
Environment
Operator type:

Kubernetes cluster type:

$ operator-sdk version
1.4.2

$ go version (if language is Go)
go1.15.5 darwin/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"9f2892aab98fe339f3bd70e3c470144299398ace", GitTreeState:"clean", BuildDate:"2020-08-13T16:04:18Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution

Additional context

Duplicate of #4468


Feature Request - Apache Kafka topic connector

Team,
It would be great if there is a connector using which ArangoDB can pull messages from Apache Kafka. This will very much reduce lot of services to be written for pushing messages to database.  Also the recovery of messages will be automatic when db comes up after a restart or crash.
Regards,
Sajeev

I got one here - https://github.com/sanjuthomas/kafka-connect-arangodb

Closing as solved.
Thanks @sanjuthomas


Add exclude parameter for select

As a user, I wish I could use Woodwork to selectively exclude specific types of data.

Code Example

# get all non float columns
X.ww.select(exclude=['double'])

@angela97lin, we're going through the Woodwork backlog right now. Is this something that EvalML would benefit from? Is it high/low priority?

@tyler3991 We would benefit, but definitely low priority.
@tamargrey I think this could also be addressed by pandas accessor as pandas natively handles this, right? So maybe not necessary with new changes 🤷

@angela97lin If you wanted to go through select_dtypes that'd work, right? I think if you wanted to just use Woodwork's select, we'd still need to add the exclude parameter

@tamargrey Yup, that'd work as a workaround, we're trying to not use pandas dtypes so we'd rather do something like exclude='numeric' rather than list out the different dtypes that numeric falls under.

Do we want to allow only specification of include or exclude, but not both in a single call? Or do we want to allow something like
new_df = df.ww.select(include='category', exclude=CountryCode)

My initial thought is that we would allow only one at at time so we don't have to worry about which value takes precedence in the event of conflicts, and users could make separate calls based on their preferred priority like this:
new_df = df.ww.select(include='category').ww.select(exclude=CountryCode)

@angela97lin tagging for question above.

I think either is fine! I agree that if it's more clear to implement the second, then let's go for that, since it gets the job done and would probably require less checking logic for conflicts.
Also, I don't think there are any benefits to the former that the latter doesn't allow for?

Also, I don't think there are any benefits to the former that the latter doesn't allow for?

@angela97lin I think the only (minor) benefit to the first is that it only requires one call to select, but aside from that I don't think it offers any benefits.


[Bug]: Switch error - Failed to call service switch/turn_on. Detected that custom integration 'loxone - 240515' calls async_fire ...

Describe the bug
PyLoxone has been running until about 2 weeks ago. I have narrowed it down to Switch: Turn On action, which I note has been reported as an issue by other users.
I have read this could be a version issue.  I can confirm Loxone, Home Assistant, PyLoxone are all on the latest versions.
I get this error per below.
Firmware of your Miniserver
15.05.11
HomeAssistant install method
VM on Proxmox
Version of HomeAssistant
Core 2024.5.3
Supervisor 2024.05.1
Operating System 12.3
Frontend 20240501.1
Version of Pyloxone
0.6.9 (latest)
Manually installed
Update pyloxone
Yes
Log
Failed to call service switch/turn_on. Detected that custom integration 'loxone - 240515' calls async_fire from a thread at custom_components/loxone - 240515/switch.py, line 253: self.hass.bus.async_fire(. Please report it to the author of the 'loxone - 240515' custom integration.

@DSew20 this can not be correct. In your log is a code which is not in the newest version. So please delete everything and install pyloxone over hacs.

Thanks.
So, remove folders:
/custom_components/loxone
/www
And set up fresh from HACS?  Will all of the entities be preserver?

OK. Thats fixed it. No idea why it was not showing the latest version with the files manually copied.

Thank you


The Python example is not running

Bug Description
I have copied the example from the repository. I copied te python program and try to run it with python visdom_example.py. And I received the error where connection failed.
Reproduction Steps
Enter steps to reproduce the behavior:

Go to https://github.com/facebookresearch/visdom/blob/master/example/demo.py

Click on Raw

Press Ctrl+S to save the file with the name as visdom_example.py.

Run python visdom_example.py

See the console log part where the error is mentioned in detail.

Expected behavior
The program must run on given server.
Screenshots
A console log is available. No snapshot.
Client logs:
python visdom_example.py
WARNING:root:Setting up a new session...
Exception in user code:
------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Python35\lib\site-packages\urllib3\connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "C:\Python35\lib\site-packages\urllib3\util\connection.py", line 83, in create_connection
    raise err
  File "C:\Python35\lib\site-packages\urllib3\util\connection.py", line 73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Python35\lib\site-packages\urllib3\connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "C:\Python35\lib\site-packages\urllib3\connectionpool.py", line 357, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "C:\Python35\lib\http\client.py", line 1083, in request
    self._send_request(method, url, body, headers)
  File "C:\Python35\lib\http\client.py", line 1128, in _send_request
    self.endheaders(body)
  File "C:\Python35\lib\http\client.py", line 1079, in endheaders
    self._send_output(message_body)
  File "C:\Python35\lib\http\client.py", line 911, in _send_output
    self.send(msg)
  File "C:\Python35\lib\http\client.py", line 854, in send
    self.connect()
  File "C:\Python35\lib\site-packages\urllib3\connection.py", line 166, in connect
    conn = self._new_conn()
  File "C:\Python35\lib\site-packages\urllib3\connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x000002251DFBFB70>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Python35\lib\site-packages\requests\adapters.py", line 440, in send
    timeout=timeout
  File "C:\Python35\lib\site-packages\urllib3\connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "C:\Python35\lib\site-packages\urllib3\util\retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=8097): Max retries exceeded with url: /env/main (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x000002251DFBFB70>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Python35\lib\site-packages\visdom\__init__.py", line 548, in _send
    data=json.dumps(msg),
  File "C:\Python35\lib\site-packages\requests\sessions.py", line 555, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "C:\Python35\lib\site-packages\requests\sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "C:\Python35\lib\site-packages\requests\sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "C:\Python35\lib\site-packages\requests\adapters.py", line 508, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8097): Max retries exceeded with url: /env/main (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x000002251DFBFB70>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it',))
ERROR:visdom:[WinError 10061] No connection could be made because the target machine actively refused it
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
The visdom experienced an exception while running: AssertionError('No connection could be formed quickly',)
The demo displays up-to-date functionality with the GitHub version, which may not yet be pushed to pip. Please upgrade using `pip install -e .` or `easy_install .`
If this does not resolve the problem, please open an issue on our GitHub.

Server logs:
No server log yet as the application didn't worked.
Additional context
Python version===> Python 3.5.0
Pip version ==> pip 18.1 from c:\python35\lib\site-packages\pip (python 3.5)
visdom version ==> '<IP_ADDRESS>'
OS ==> Window 10 Home
Windows version ====> 10
Websocket library version ===> '0.47.0'

I have more or less the same problem. Running the demo I get this error:

WARNING:root:Setting up a new session...
ERROR:visdom:[Errno -2] Name or service not known
ERROR:visdom:[Errno -2] Name or service not known
ERROR:visdom:[Errno -2] Name or service not known
WARNING:visdom:Visdom python client failed to establish socket to get messages from the server. This feature is optional and can be disabled by initializing Visdom with use_incoming_socket=False, which will prevent waiting for this request to timeout.
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
waiting
ERROR:visdom:[Errno -2] Name or service not known
waiting
waiting
waiting
waiting
waiting
The visdom experienced an exception while running: AssertionError('No connection could be formed quickly',)
The demo displays up-to-date functionality with the GitHub version, which may not yet be pushed to pip. Please upgrade using pip install -e . or easy_install .
If this does not resolve the problem, please open an issue on our GitHub.

The connection is active on another terminal and the blue page is appeared in my browser.  Do you have any idea?

Can you try creating a visdom instance within a python session manually and fill the hostname and port arguments manually?


Flash Encryption example project build problem (IDFGH-4014)

Environment

Development Kit:      [ESP32-DevKitC]
Kit version (DevKitC): [v4]
Module or chip used: 32-WROVER-B
IDF version (run git describe --tags to find it):
v4.1
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
(crosstool-NG esp-2020r2) 8.2.0
Operating System:     [Windows]
(Windows only) environment type: ESP Command Prompt
Using an IDE?: [vs code]
Power Supply:         [USB]

Problem Description
i just try the example project securtiy/flash encryption and i followed instructions
Ensure Bootloader log verbosity is Info
Enable the flash encryption mode Development
Change the partition table offset to 0x9000
but i gave  error something like this
raise InputError("CSV Error: First partition offset 0x%x overlaps end of partition table 0x%x"
gen_esp32part.InputError: CSV Error: First partition offset 0x9000 overlaps end of partition table 0xa000

Thanks for reporting, we have a fix under internal reviewing, will update once the fix is available on GitHub. Thanks.

Hi @tayph !
This issue resolved on the master 5e8795eebed3f7a93e5c906f0ffc074a3b158193 but not published yet. This will be backported to v4.1 as well.
You can fix this issue. The partition table.csv file should be without offsets in it:
# Name,   Type, SubType, Offset,  Size, Flags
nvs,        data, nvs,      ,  0x6000,
# Extra partition to demonstrate reading/writing of encrypted flash
storage,    data, 0xff,     ,  0x1000, encrypted
factory,    app,  factory,  , 1M,

Thanks.

thanks @KonstantinKondrashov it's work it.
By the way normal build command (idf.py -p PORT encrypted-flash monitor) did  encrypted flash.
i mean i didn't need use idf.py -p PORT encrypted-flash monitor.


SelectBox is missing title

DEBUG selectBox, when hover over, can't see title.
Checked with latest insider build, has the same issue.
While in version

There is title

May be caused be https://github.com/microsoft/vscode/commit/6bab1c3ee1f5c580ac14579be88b2da09064cd57

@cleidigh do you have time to look into this?

@YurongHe do you see this for other dropdowns as well. For example the terminal dropdown, or the output channel name dropdown?

Terminal dropdown has no title either.

Ok, so it is a general select box issue. Let's see if @cleidigh has time to look into this

@isidorn
Absolutely.  I've been a bit awol...
Will look at this tomorrow.


Add OData Migration docs

Docs Build status updates of commit c587577:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

Odata-docs/migration/odata-migration.md
:x:Error

Details

Odata-docs/migration/prerequisites.md
:x:Error

Details

Odata-docs/migration/setup.md
:x:Error

Details

Odata-docs/migration/odata-migration.md

[Error] Cannot resolve '../../includes/appliesto-odatalib-v7.md' relative to 'migration/odata-migration.md'.

Odata-docs/migration/prerequisites.md

[Error] Cannot resolve '../../includes/appliesto-odatalib-v7.md' relative to 'migration/prerequisites.md'.

Odata-docs/migration/setup.md

[Error] Cannot resolve '../../includes/appliesto-odatalib-v7.md' relative to 'migration/setup.md'.

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.

Docs Build status updates of commit 7ba41d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/migration/odata-migration.md
:white_check_mark:Succeeded
View

Odata-docs/migration/prerequisites.md
:white_check_mark:Succeeded
View

Odata-docs/migration/setup.md
:white_check_mark:Succeeded
View

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.


Feature request: Add 'clear' option to the .type() function

Function concerned : .type - api here
Basically, add a boolean clear into the options so we specify if we want to clear the field before typing.
page.type('#myinput', 'toto', {clear: true})
This would clear any existing input into #myinput then it would type toto.

As per discussion with @JoelEinbinder, we should allow to select elements with page.setSelection.
Once it's done, this will be addressed like this:
await page.setSelection('#myinput');
await page.keyboard.type('toto')

We might come with a sugar for this
await page.type('#myinput', 'toto', {preselect: true});

@aslushnikov setSelection might be interesting in some use cases, but what the user/dev wants in the end is to clear the field - if it's done through CTRL+backspace, CTRL+A (selection)+typing or direct modification of the HTML element, that's just implementation details.
I was thinking of something simple like in protractor : .clear()

@HRK44 page.clear() is reasonable, thanks.

I just made my own little function. Pretty easy to use.
`
async function clear(page, selector) {
await page.evaluate(selector => {
document.querySelector(selector).value = "";
}, selector);
}
(async () => {
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.com');
await page.type("input.search","hello");
await clear(page,"input.search");
await browser.close();
})();
`

Made my own little function, pretty easy to use.
  await page.evaluate(selector => {
    document.querySelector(selector).value = "";
  }, selector);
}

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto('https://example.com');
  await page.type("input.search","hello");
  await clear(page,"input.search");

  await browser.close();
})();```

await page.type('#myinput', 'toto', {preselect: true});

@samfultonschool thanks! it's very useful!

Functionality is a good idea!

Also love this!

@nicoandmee Agreed, I would love to see this come standard with puppeteer.
@aslushnikov Are there any plans for implementing page.clear() or page.clearInput()?

I'm baffled by how this hasn't been implemented.
Workaround that seems to work without requiring the use of evaluate:
// From https://evanhalley.dev/post/clearing-input-field-puppeteer/
await searchInput.click({clickCount: 3});
await searchInput.press('Backspace');

I'm baffled by how this hasn't been implemented.

Probably because the volunteer maintainer(s) had something come up with a higher priority (maybe family, paid work, rest). Reference your PR with the fix here so they'll see it.

@bitwombat this has been dismissed by the maintainers, see https://github.com/puppeteer/puppeteer/pull/3180#issuecomment-418204987

                // clear the input field
                await page.evaluate(selector => {
                    document.querySelector(selector).value = ""
                }, your_selector);

                await element.type(whatever);

I'm baffled by how this hasn't been implemented.
Workaround that seems to work without requiring the use of evaluate:
// From https://evanhalley.dev/post/clearing-input-field-puppeteer/
await searchInput.click({clickCount: 3});
await searchInput.press('Backspace');

this works as I expected https://evanhalley.dev/post/clearing-input-field-puppeteer/  thanks so much @Crashdoom