Make the plugin work with multiple packages that share different dependencies' version

Disclaimer: I know this has already been discussed in https://github.com/invertase/dart_custom_lint/issues/104, and addressed partly by https://github.com/invertase/dart_custom_lint/pull/128, but I feel like the trade-off is still too painful to not do anything about it.
Is your feature request related to a problem? Please describe.
When working on medium to big size mono repo, the plugin won't start if some of the projects inside the mono repo have dependencies which resolves to different versions after a pub get.
Describe the solution you'd like
The plugin runs even if the resolved versions are not exactly the same.
Describe alternatives you've considered
In the workspace.dart file, instead of throwing if there are conflictual versions, the plugin could try to resolve each package to a single version by taking the minimum one for example. An example: If package A and package B depends on meta with resolved version 1.8.0 and 1.9.1, the plugin would choose to keep the 1.8.0 instead of throwing.
I know there are other alternatives like opening each package separately when working on them, but I think this damages the devX too much. Aligning the versions isn't a good alternative either, because it would mean adding 'useless' lines to the pubspec of some packages (like a meta:1.8.0 when the package actually has really an implicit meta:^1.7.0 constraint which will almost always resolve to 1.9.1.)
Additional context
I understand you didn't choose this path for a reason, but while testing it locally, I didn't run into any problem as long as the version gap is only between the minor/patch numbers (thank you semantic versioning).
My understanding of the main dart analyzer is that it works similarly as what I describe, as it can run on some old flutter code even when using the latest analyzer version. I understand it can create inaccuracies when analyzing code which uses different versions of the analyzer's, but I think it's fine to have those inaccuracies and to work around them (and I prefer that rather than no analyzer at all).
Why did you pick this solution, is there something I don't see which prevents the plugin to work like this?

In the workspace.dart file, instead of throwing if there are conflictual versions, the plugin could try to resolve each package to a single version by taking the minimum one for example. An example: If package A and package B depends on meta with resolved version 1.8.0 and 1.9.1, the plugin would choose to keep the 1.8.0 instead of throwing.

The behavior would be unreliable.
There's no telling whether the resulting code would compile or not with such an approach, and if it doesn't compile, the error would be extremely cryptic.
This could also make it very difficult for plugin authors to debug possible problems if any. Running custom_lint on one specific project could have a different behavior than running it on a mono-repo since the dependencies picked-up could be different. That would be very confusing.
It's effectively the equivalent of praying to god that things will work out.
That's not sane for the ecosystem.

I understand, but isn't what the main dart analyzer does ?

No it doesn't.
The analyzer doesn't rely on whatever package you have installed. It comes already fully pre-installed with the Dart SDK.
It doesn't uses plugins. All lint rules provided by the analyzer are implemented within Dart itself and do not rely on anything from pub.dev.
So there's never a version conflict.
Whereas with custom_lint that's the opposite. Who knows when starting the custom_lint command what the command will need to work? It has to dynamically load the source code of the various plugins you've installed in different projects, and make sure they are all compatible with each other.

Thanks a lot for these explanations 🙏
Do you tend to agree that it has a negative impact on the devX though? I'd love to help to find a solution to this, but if you don't see it as a problem, or if you think it's unsolvable with the current constraints of the analyzer, then I think we can close this issue.
What do you think?

Of course it has a negative impact.
I'm just very careful about what we do here, because a badly designed solution could have dire consequences.
For now the current solution is a bit inconvenient, but fairly safe.

Sure, you're right to be cautious.
Thank you for taking the time to explain, the problem is easier to understand now. I have another question/solution idea if you don't mind.
Let's take a practical example with three packages, my_custom_lint, my_dart_package, and my_flutter_package.
Let's assume they have some dependencies but the only conflicting one is meta, as my_flutter_package is bound to use meta:1.8.0.
Here are the constraints:
my_custom_lint:
  dependencies:
    meta: ^1.7.0 // resolved to 1.9.1

my_dart_package:
  dependencies:
    meta: ^1.7.0 // resolved to 1.9.1

  devDependencies:
    my_custom_lint:

my_flutter_package:
  dependencies:
    meta: 1.8.0 // resolved to 1.8.0

  devDependencies:
    my_custom_lint:

In this scenario, opening the three project in an IDE will make custom_lint throw because the resolved versions are different.
But actually there is a set of versions which make all those constraints work, right? If the custom_lint_client dependency to meta was resolved to 1.8.0, it would match all the constraints. I'm not saying to take the lowest bound as before because that will create bugs, but trying to resolve the constraints a like what pub get does, would create a safe configuration for custom_lint which would work with more flexibility than the current setup, at least in my understanding.
Does it seem reasonable? Sorry if I miss some important points, my knowledge of the analyzer still is very light.

This works, yes.
But as you might expect, there are many tricky situations.
Say you have:
# package A
dependencies:
   meta: ">=1.6.0 <1.9.0" # resolved with 1.7.0

# package B
dependencies:
   meta: ^1.8.0 # resolved with 1.9.0

Then even though the constraints are compatible, locally only 1.7.0 and 1.9.0 are available. But neither of them are compatible with both constraints at once. Only >=1.8.0<1.9.0 is, but we don't have a matching version for this. So it'll fail
The algorithm for the package resolution would also likely be quite complex.
Maybe pub get --offline would work. Although I'm a bit skeptical about running it. It's both a bit slow to spawn a process for this and could possibly be confusing.
If someone edits the source code of a dependency in the pub cache directory directly, they could be confused about why their changes aren't applied.
We'd also have to be very careful to make sure dependency_overrides are considered (and pubspec_overrides.yaml too).
And there's the possible concern of folks using third-party tools such as melos for resolving packages with a version different from what the pubspec.yaml mentions.
If we run pub get, that would break those tools. Although melos 3.0 should be fine now as it relies on pubspec_overrides.
It's a bit tricky as you can see.

Thanks, @MaximeRougieux for brining attention to this issue 💙 . I fully agree with:

still too painful to not do anything about it

As a user of custom_lint I would be willing to use a less "safe" version if this painpoint is removed. Perhaps the CLI can have parameters to choose between the desire behaviour?

Closing in favor of https://github.com/invertase/dart_custom_lint/issues/156.


Ability to run project with docker-compose

Hi,
similarly to forest project I prepared the same manual for docker-compose here on nutella project as we agreed on.
Please check.

Thanks :-)


Ability to provide default implementations on service traits

I'm using a crate (https://github.com/dapr/rust-sdk) uses prost to generate code for developers to build out their dapr service.
One thing I am finding frustrating is having to implement all trait methods (from the proto service) when I only need one or two at a time.
I was wondering if it is possible to generate default trait methods so the developer only has to override the ones they are interested in?
Dapr SDK Proto: https://github.com/dapr/rust-sdk/blob/b69e1f84b04858f72de4c70793cc353fcbf08529/dapr/proto/runtime/v1/appcallback.proto#L30-L48
Example implementation (which only need to implement one method): https://github.com/dapr/rust-sdk/blob/b69e1f84b04858f72de4c70793cc353fcbf08529/examples/invoke/grpc/server.rs#L60-L90
It appears to me that all generated return types from services and message fields impl Default, so this should be doable in some form (and I can imagine not always desirable, so perhaps an opt-in thing).

Expand to see a snippet of generated code showing impl Default for message types
// impl Default for rpc return type
// proto-src: https://github.com/dapr/rust-sdk/blob/ecc0e4e813af0c87b749ad14f57320cf3f8f9368/dapr/proto/runtime/v1/appcallback.proto#L245-L249
                    impl ::core::default::Default for ListTopicSubscriptionsResponse {
                        fn default() -> Self {
                            ListTopicSubscriptionsResponse {
                                subscriptions: ::core::default::Default::default(),
                            }
                        }
                    }

// impl Default for message used in the above message
// proto-src: https://github.com/dapr/rust-sdk/blob/ecc0e4e813af0c87b749ad14f57320cf3f8f9368/dapr/proto/runtime/v1/appcallback.proto#L251-L271
                    impl ::core::default::Default for TopicSubscription {
                        fn default() -> Self {
                            TopicSubscription {
                                pubsub_name: ::prost::alloc::string::String::new(),
                                topic: ::prost::alloc::string::String::new(),
                                metadata: ::core::default::Default::default(),
                                routes: ::core::default::Default::default(),
                                dead_letter_topic: ::prost::alloc::string::String::new(),
                                bulk_subscribe: ::core::default::Default::default(),
                            }
                        }
                    }

There won't always be a clear default to return, but I can see it coming down to two:

Ok (with default response)
Err (suggesting the method is not implemented)

In my particular case, I would want the defaults for listing subscriptions and bindings to be:
Ok(Response::new(T::default())) // where type T = ListInputBindingsResponse, for example

and for handlers that haven't been overridden to return the "unimplemented" Status:
Err(Status::unimplemented("x not implemented")) // where x could be on_invoke, for example

I'm unsure if it is frowned upon to encode this in the proto files, but perhaps something like:
service AppCallback {
  // Invokes service method with InvokeRequest.
  // @default(unimplemented)
  rpc OnInvoke (common.v1.InvokeRequest) returns (common.v1.InvokeResponse) {}

  // Lists all topics subscribed by this app.
  // @default(default)
  rpc ListTopicSubscriptions(google.protobuf.Empty) returns (ListTopicSubscriptionsResponse) {}

  // Subscribes events from Pubsub
  // @default(unimplemented)
  rpc OnTopicEvent(TopicEventRequest) returns (TopicEventResponse) {}

  // Lists all input bindings subscribed by this app.
  // @default(default)
  rpc ListInputBindings(google.protobuf.Empty) returns (ListInputBindingsResponse) {}

  // Listens events from the input bindings
  //
  // User application can save the states or send the events to the output
  // bindings optionally by returning BindingEventResponse.
  // @default(unimplemented)
  rpc OnBindingEvent(BindingEventRequest) returns (BindingEventResponse) {}
}

Though this is probably not great for cross-language usage of proto file. Maybe a prost specific tag so others can ignore it, or define their own._
It doesn't help my current case, because the proto files are sourced/updated from another repository occasionally, and are made for many languages.

Otherwise, perhaps it could be configured in the prost Builder, eg:
tonic_build::configure()
    .build_server(true)
    .override_returns!(
        "AppCallback.on_invoke" => "Err(Status::unimplemented("on_invoke not implemented"))",
        "AppCallback.list_topic_subscriptions" => "Ok(Response::new(T::default()))",
        // any others not defined here will require explicit implementation by the developer
    )
    .compile(
        &[...],
        &["."],
    )?;

I did it as a macro_rule style for readability, but you could imagine a HashMap or similar.
The map key would need parsing, eg: <Service>.<method>, while the map value would be inserted as plain text and let the compiler check for correctness - unless a macro does some fancy stuff to validate it and give more helpful errors.

Perhaps this is the purpose of the ServiceGenerator trait, and that we need to make our own one for the dapr/rust-sdk?:
https://github.com/tokio-rs/prost/blob/6b5516aff83a331628f1e040f71fad6dfce23e4b/prost-build/src/lib.rs#L161-L175

... and it looks like I'm needing to be over in https://github.com/hyperium/tonic.
Their implementation of ServiceGenerator: https://github.com/hyperium/tonic/blob/65d909e85050e0cbbf50455e0b3531a0d08eff8d/tonic-build/src/prost.rs#L165-L220
I'll close this issue and open one over there after a little more digging.


Feature/python tooling update

@kmhernan Some notes on the dev flow changes:
Python deps defined at top of setup.py
Use make requirements to rebuild requirements.txt
Use make init to install pre-commit (make init-hooks) and pip requirements (make init-pip)
Use make build to build python package and Docker image.
Use make test to run unit tests locally.
Use make test-docker to run unit tests within the docker image.


Figure out how to get label data from prometheus

Two approaches could work here:

Scrape all the data from this API https://prometheus.io/docs/prometheus/latest/querying/api/#querying-target-metadata and somehow store it in a searchable data structure.

Use the APIs described in the aforementioned page and request data from prometheus on demand.

The second one seems like the better idea for now.

There appears to be a lib for that: https://github.com/prometheus/client_golang/blob/333f01cef0d61f9ef05ada3d94e00e69c8d5cdda/api/prometheus/v1/api.go#L692


fix(Documentation): Remove Misleading Doxygen Comment for I2C Init (Doesn't Set Speed)

Description
Closes #752
None of our I2C init functions actually set the I2C frequency.
Checklist Before Requesting Review

[x] PR Title follows correct guidelines.
[x] Description of changes and all other relevant information.
[x] (Optional) Link any related GitHub issues using a keyword
[x] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

Merge from main, should fix the Verify Register/SVD workflow.


Composer fix reusable

reusable was forced to true

@stephomi maybe this line should be fixed too
https://github.com/cedricpinson/osgjs/blob/2ba20789bd2c8b2cad99843d80213d29997be015/sources/osgUtil/ComposerPostProcess.js#L835
I think it's better to have true or false in this variable but not undefined


[Breadth Coverage] Onboard CustomProviders Commands

Spec Link
https://microsoft.sharepoint.com/:w:/t/AzureManagementExperience/Eea4hlXnO9pEjdvll9fxJ8ABfwn3NXpSo3Eo21KQYy3qIQ?e=9EcrDd
ADO Work Item Link
https://dev.azure.com/azure-mgmt-ex/Onboarding/_workitems/edit/150
Resource Provider
What is the Azure resource provider your feature is part of?
Microsoft.CustomProviders
Description of Feature or Work Requested
Support Azure CLI commands for CustomProviders
Minimum API Version Required
Microsoft.CustomProviders 2018-09-01-preview
Swagger Link
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/customproviders/resource-manager/Microsoft.CustomProviders/preview/2018-09-01-preview/customproviders.json
Python SDK Link
Not ready (already submitted SDK release request on OpenAPI Hub)
Target Date
03/31/2020
Addtional context
We'll use autorest.az from code gen team to auto-generate the code first and may need update some code manually if the generated code doesn't meet your requirements.

add to S167.


[Bug]: Nested codable type

With the current implementation is impossible to encode/decode nested codable struct.
It is due to the runtime conformance of Dictionary and Array to URLEncodedFormDataConvertible.
I suspect that the following could somehow fix this issue, but the runtime conditional conformance check is not going to be available until Swift 4.2.
extension Dictionary: URLEncodedFormDataConvertible where Value: URLEncodedFormDataConvertible ...
extension Array: URLEncodedFormDataConvertible where Element: URLEncodedFormDataConvertible ...

I believe that https://github.com/vapor/url-encoded-form/issues/10 and https://github.com/vapor/url-encoded-form/issues/11 are somehow related to this issue.
This pull request adds a failing test to shows the issue and possibly should help fixing it.
@tanner0101 @LoganWright
-- Edit:
The dictionary and array extensions are not needed as the encoder/decoder should loop recursively until they are able to find a primitive value of type URLEncodedFormDataConvertible.
Those two extensions look more like an hack to allow 1-nested-level to work.
Removing those two extensions should make the tests pass straight away, but there is a bug in the Core module:
NestedData.swift line: 43 it has to be replaced with the one below because the previous implementation doesn't allow the lookup of arrays.
public func get(at path: [CodingKey]) -> Self? {
        var child = self
        for seg in path {
            var c: Self?
            if let dictionary = child.dictionary {
                c = dictionary[seg.stringValue]
            } else if let array = child.array, let index = seg.intValue {
                c = array[index]
            }

            guard let someC = c else {
                return nil
            }

            child = someC
        }
        return child
    }

Thanks @valeriomazzeo! Closing in favor of https://github.com/vapor/url-encoded-form/pull/16 which has a local branch.


is there a simple way to pipe input < to the script?

I like the python script.py < input.txt style on occasion
Obvious alternative: work the input file in as an argument,
just thought it might be obvious/doable itself :))
doesn't seem to work with 'livepython script.py < input.txt' just as a mention, it opens and steps through to the line with input() but the in isn't ... putting

not an answer - but the electron may support this  need to dig into piping data for electron
https://stackoverflow.com/questions/28946904/piping-data-from-child-to-parent-in-nodejs
ar args = process.argv.slice(2)

if (!args.length) {
  console.log("Usage: livepython [program] [..args]")
  process.exit()
}

args.unshift(__dirname + "/../tracer.py")

@roydhenderson created this code - looks like it's piping something to electron app .
https://github.com/mrdoomits/superluminous/blob/ad08321b463b6b31730873b08418ee2f2cd6cb28/electron_app/gulpfile.js
(no idea what gulp is)


how to change the selected link  of color based on color button  ?

I have a one button of color i want if i select link and change color of that link based on selected color on button.

I have a one button of color i want if i select link and change color of that link based on selected color on button.

You could look at adding a class on the connection object. But you would have to add the class to the SVG as well.
Connections in drawflow have limitations.


Elasticsearch must be provisioned in a VPC.

  - id: ELASTICSEARCH_VPC
    message: Elasticsearch domain must be in a VPC
    resource: aws_elasticsearch_domain
    severity: FAILURE
    assertions:
      - key: vpc_options
        op: present
    tags:
      - elasticsearch


Add new options properties and classes

Add AppendTo property to AnnotationsImage class
Add AppendTo property to AnnotationsText class
Add BorderRadius property to Label class
Add Width property to AnnotationsYAxis class
Add RedrawOnWindowResize property to Chart class
Add Class property to ToolCustomIcon class
Add ColorStops property to FillGradient class
Add CustomHTML property to LegendMarkers class
Add DataLabels property to PlotOptionsTreemap class Add ZScaling property to PlotOptionsBubble class
Add Formatter property to DonutLabelName class
Add Formatter property to DonutLabelValue class
Add Formatter property to AxisTooltip class
Add Spokes property to PlotOptionsPolarArea class
Add Width property to Track class
Add Width property to AxisBorder class
Add OverwriteCategories property to XAxis class
Add Align property to YAxisLabels class
Add LogBase property to YAxis class
Add FillGradientStops class
Add TreemapDataLabels class
Add PolarAreaSpokes class
Add YAxisTooltip class
Fix data type on PurplePolygons.StrokeWidth property Update properties not in JavaScript documentation to be Obsolete Update various XML comments to include additional details

Hi @joadan,
For the most part, the commit notes above detail the changes, there are two items to note.
First, as noted, there is a fix, which will require anyone implementing PolarAreaSpokes.StrokeWidth to update their code.
Second, while I have added the YAxisTooltip class, I did not implement it. This was to avoid breaking changes, but it is accurate as per the JavaScript documentation; whereas the current implementation of AxisTooltip is not.

Hello,
Thank you so much for this. I'm sorry for the delay but now I'm on it.

No worries, I appreciate all the effort you have put into creating such a great library and completely understand how difficult it can be to make time to maintain projects like this.


#4916

move menu items (elapsed time, sequence no) from output to input section
hide dropdown menu items without name/label

please give your PR a descriptive title
the items should only be moved if the output is not visible.  eg if you evaluate the python code ```
import time
time.sleep(5)

then there is no output, and so the menus should be moved.  but python code like ```
23+34

the menus should not be moved.

kick jenkins


Fix failing [Nexus] tests

Fixes #4903. Tests were failing because v2.11.0.rc1 does not match /^v\d+(\.\d+)*([-+~].*)?$/.
I've changed the test data rather than the regex. Unless I'm missing an obvious trick, the latter would be quite hard to change without making validation significantly looser. The obvious solution, /^v\d+(\.\d+)*([-+~.].*)?$/ (extra dot in the allowed char list) would start validating strings such as v2.11.0€rc1, as it would capture from the previous dot - it would be pretty much equivalent to /^v\d+(\.\d+)*(.*)?$/.
Versions in the v2.11.0.rc1 format are quite rare anyway, I figured there was little value in changing the validator for such an edge-case, but I can change things if you disagree!

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @PyvesB!

  Generated by :no_entry_sign: dangerJS against d07cc3536a96901712ed5adfa5107b50a2a575f1

I don't want to bikeshed on this too much since the most important thing is that we get the tests working again, but is there any reason we can't use the same validator in the tests that the service class does?
I recall there being some complexity in the Nexus schemas so is this a case where the the service class is very relaxed (a Joi.string())?

I recall there being some complexity in the Nexus schemas so is this a case where the the service class is very relaxed (a Joi.string()) but we want something a bit more strict in the tests?

Yes, I think it's one of those, the service class uses version: Joi.string()

Added the label to have ranger go ahead and merge this. We can revisit if and when any issue actually recurs


Poorly formed version fails install with private index

[x] I am on the latest Poetry version.

[x] I have searched the issues of this repo and believe that this is not a duplicate.

[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: OSX Mojave

Poetry version: 0.12.11

Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/DanCardin/e5676dfdcd7c39aba776b1e769128c7a

Issue
None of the below appears to apply when installing without first routing through the private index.
When installing "yamlreader" through a private (artifactory) index, where the index's page for yamlreader contains:
yamlreader-3-py2-none-any.whl
yamlreader-3-py2.7.egg
yamlreader-3.0.0-py2-none-any.whl
yamlreader-3.0.0-py2.7.egg
yamlreader-3.0.0.tar.gz
yamlreader-3.0.1-py2-none-any.whl
yamlreader-3.0.1-py2.7.egg
yamlreader-3.0.1.tar.gz
yamlreader-3.0.2.tar.gz
yamlreader-3.0.3.tar.gz
yamlreader-3.0.4.tar.gz
yamlreader-3.tar.gz

Specifically yamlreader-3.tar.gz appears to fail to parse correctly and returns expected string or bytes-like object, even if I'm attempting to install 3.0.4
It seems like https://github.com/sdispater/poetry/pull/818/files it could be solving the same problem but its not clear to me as a layman whether ParseVersionError will just cause a slightly nicer user error (which doesn't help) or actually cause it to skip that version (which is what would be fine for me, since i want 3.0.4, which is correctly formed).

@sdispater I've been locally running https://github.com/sdispater/poetry/pull/818/files (with my comment in that PR applied, which deletes the original line), and its has fixed the issue and I haven't noticed any other weirdness.
I'm not sure how to work around this issue other than by running a released version which I can't leak outside my own computer.
Is there something I can do to help get something like that PR merged/released? I could submit a 2nd PR with my suggested change; and probably a basic test.


[Web] Uncaught Error: FormatException: SyntaxError: JSON.parse: expected property name or '}' at line 1 column 2 of the JSON data on Safari and Firefox web browsers

On debug mode everything works fine but when I create a build for the web with flutter build web and deploy I get the JSON.parse: expected property name or '}' error.
flutter doctor -v

[✓] Flutter (Channel stable, 3.7.3, on macOS 13.1 22C65 darwin-arm64, locale en-NG)
    • Flutter version 3.7.3 on channel stable at /Users/binemmanuel/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (8 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/binemmanuel/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /Users/binemmanuel/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.75.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 102.0.5005.61

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@binemmanuel
Can you please look at the "Network" tab in the browser devtools and confirm what kind of response the app gets from the server? This would explain the different error observed. If valid JSON is served but JSON.parse still produces an error, then it would be a bug in the JSON parser. Otherwise, it might be a misconfiguration of the server or something else.

@darshankawar  On the Network Tab on Safari and Firefox it doesn't even show that a request was made to the endpoint but on the Console Tap, there is an error which should only show up after a request to the endpoint.
I cleared cache on both browsers and it magically works fine.

Does that mean the error doesn't occur anymore ?

@darshankawar Yes, the error is completely gone.

@binemmanuel Based on your comment, closing the issue as solved. Thanks!


Implemented Prime Number in Go

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Implemented Prime Number in Go.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #4982

Please make an issue here and raise a PR, for an article as part of our Docs repository: https://github.com/TesseractCoding/NeoAlgo-Docs
It would be much appreciated. Thanks!


GitHub Copilot could not connect to server. Extension activation failed: "Unexpected token 'N', "Not Found" is not valid JSON"

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

VS Code Version: version: 1.78.2 (Universal)
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:44:45.204Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.2.0
Sandbox: Yes
OS Version: 13.1 (22C65)

Steps to Reproduce:

install plugin GitHub Copilot

open vscode.
report GitHub Copilot could not connect to server. Extension activation failed: "Unexpected token 'N', "Not Found" is not valid JSON"

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

already latest version

Looks like an issue with the copilot extension, please open an issue at https://github.com/orgs/community/discussions, thanks


More informative errors for HMR

See #1346

take a look for additional cases of common MDSVEX errors
styling proposal in #1364

Closed by #1346


Does it supports mathematical equations ?

I just want to know if this ml kit does support mathematical equations to latex conversation ?

Hi @gulabsagevadiya ,
As far as i know , The ML kit does not support mathematical equations to latex conversation right now .

Is there any free solution for image to latex like mathpix ? For simpler math equations?

Well Unfortunately I couldn't find any free solution for image to latex for android . But since it is about simpler math equations , One temporary solution could be to use text recognition in ML kit to extract text from an image and then maybe convert that extracted string into latex , Although This isn't the best solution because most of the time the text recognition seems to fail in recognizing math symbols which could be problematic .

@AndroidDeveloperLB  the official documentation says that this ML kit can recognise text across latin-based languages . Here is a link to the documentation -  https://developers.google.com/ml-kit/vision/text-recognition
But if you want to teach it some other language . You can train your own model by providing some sample data here -
https://teachablemachine.withgoogle.com/
And then use the generated ML model in your android app .

@krishnachaitanya0107 Oh sorry for this. Still I was talking about something similar.
Is it a hard thing to teach and use it?
I've noticed that even on the sample, it often fails to recognize English letters well.
Did you teach it, or was it Google?

Hey I have one question about this technology.
I already have so many LaTeX code. And I can generate their mathematical equations images with some android library.
So can I train model to convert image to LaTeX code with teachablemachine?

@AndroidDeveloperLB in the sample i actually used a pre-trained model by Google , and yeah it fails to recognise text properly sometimes. I brought up the teachable machine part only because you wanted a way to recognise non English letters.
The teachable machine by Google isn't actually hard to use , you just need to have enough training data to train the model . The more the data you provide it , the more accurate the model will be .

@gulabsagevadiya  If you have data to train the model , then you can go ahead and give it a try .


pkg/k8s: add pod IP event change

This is a follow up of 6bd98ad7e443 ("handle IP addresses modification in running nodes and CEPs")
for more information read the commit description of that commit.
Signed-off-by: André Martins<EMAIL_ADDRESS>Accidentally fixes https://github.com/cilium/cilium/issues/13136

test-me-please

test-me-please

test-me-please

@aanm I took a look at the gke failure. I don't see a hostPort service entry being created, as a result, the test fails. This is the code relevant to this PR - https://github.com/cilium/cilium/blob/master/pkg/k8s/watchers/pod.go#L641.
Also, I see a few occurrences of this error log - "Unable to update ipcache map entry on pod update". AFAIU, this is supposed to be a red herring, but with this change we'll return an error, skipping processing of labels/annotations, etc.

test-me-please

test-1.19-5.4

test-1.21-4.9

test-1.21-4.9

LGTM, except for the defer optimization we discussed offline. Also, I'm not able to add a comment on the unchanged parts, but consider using multi errors reporting package (https://github.com/hashicorp/go-multierror) for -
	}) {
		errs = append(errs, fmt.Sprintf("ipcache entry for podIP %s: %s", podIP, err))
	}
	if len(errs) != 0 {
		return errors.New(strings.Join(errs, ", "))
	}

test-me-please

test-1.21-4.9: hit https://github.com/cilium/cilium/issues/16237
test-1.20-4.19: https://github.com/cilium/cilium/issues/15572
test-1.16-netnext: https://github.com/cilium/cilium/issues/16399

FYI, I removed this PR from the v1.9 backport PR because it was causing CI failures.


Add support for draft-js-plugins

It'd be super rad if I could do
const renderer = {
  plugins: [mentionsPlugin]
}

or something to that effect. That way I basically wouldn't have to change anything about my setup between rendering a DraftJS plugins editor and redraft!
/cc @juliankrispel @nikgraf

Not so sure it should be part of redraft or maybe just a component with redraft as a dependency. It would accept plugins and other settings as props and would call redraft. Bit like this: https://github.com/draft-js-plugins/draft-js-plugins/blob/master/draft-js-plugins-editor/src/Editor/index.js
Still redraft would need to handle all those options ie the case from #33

I think redraft could actually handle these fairly well in core, because most of the plugins functionalities are really irrelevant for rendering. (they're only used for editing experience changes)
The only thing redraft would need to handle is nested definitions of five methods:

decorators
customStyleMap
blockRendererMap
blockStyleFn
blockRendererFn

decorators
These are already handled fairly well, it would just need to be extended to handle an array of a mixture of normal and complex decorators. See #33.
customStyleMap
This is almost the same thing as redrafts inline option, that should just also support style objects: (maybe it already does?)
const renderer = {
  inline: {
    'BOLD': {
      fontWeight: 400,
    }
  }
}

blockRendererMap
This is almost the same thing as redrafts blocks option, that should just also support the blockRendererMap notation:
const renderer = {
  blocks: {
    'unstyled': {
        element: 'div',
        aliasedElements: ['p'],
        wrapper: <ul />
    }
  }
}

blockRendererFn and blockStyleFn are the only two I'm not sure how to handle since the provided methods might use the Immutable API under the hood, which redraft doesn't ship. Any ideas for those?

Exports for plugins would be super nice. I was thinking either to champion/recommend one of the exporters or build our own. I would like to avoid building our own :)

The problem is supporting same api that draft-js does, possibly while not adding it as a dependency.
The blockRendererFn and blockStyleFn both accept ContentBlock as an argument. While redraft already includes some basic stub for ContentBlock it would probably have to suport all of its methods to handle any plugin.
This is probably what would need to be ported from draft:
https://github.com/facebook/draft-js/blob/master/src/model/immutable/ContentBlock.js
https://github.com/facebook/draft-js/blob/master/src/model/immutable/findRangesImmutable.js
https://github.com/facebook/draft-js/blob/master/src/model/immutable/CharacterMetadata.js
My ideas so far:

A wrapper around redraft not to bloat its current api and size (though some changes might still be required).
Add Immutable.js, port whole ContentBlock and it's dependencies from draft-js
Add some better error handling for missing methods in the ContentBlock stub and require users to pass a createContentBlock to redraft if any of the plugins require those methods.

Any other ideas?

I'd hate anything that requires Immutable by default, to be completely honest, but I definitely see the value in letting users choose to do so if they don't mind it.
What about having two different "modes" with two different sets of tradeoffs? Something like this:

Slim/default mode: No createContentBlock method is provided, so the blockRenderFn and blockStyleFn of all plugins are ignored. Downside is that users might have to reimplement some parts of the plugins they use themselves, but that's still much better than having to basically rebuild all your plugins from scratch for rendering.
Draft mode: A createContentBlock method is provided, so the blockRenderFn and blockStyleFn of plugins are used. Downside is you ship Draft and Immutable and bloat your bundle, but you can just your plugins as is.

 Use Draft mode.  Use default mode.

Yeah ignoring the blockRenderFn and blockStyleFn sounds much better than calling them with a partial stub.
As for the rest:

decorators - fixing #33 should probably do
customStyleMap - that's mostly done will probably still require to provide a wrapper
blockRendererMap - probably needs to be similar to customStyleMap to allow a cb (ie. React.createElement) if we want to prevent shipping and coupling with React.


Is there way to add silence to end of source to make it a certain length?

As per the title. I am building a small audio looping application, for which it is very crucial to be able to make sounds play in cycles of some duration, often longer than their own length. Example: play a 2 second sound effect every 15 minutes. Is there a convenient way in which I can add silence to the end of a source to fill it to a certain duration?
I am already using take_duration, which can be used if the desired loop has a length shorter than the source length (loop the first 5 mins of a 10 min source), but it does not add silence to the end if the entered duration is longer than the length of the source.
I am essentially looking for the combined behavior that does both of these with a single parameter: when the cycle should end. Does something like that exist?

I will answer my own question:
let silence: Zero<i16> = Zero::new(decoder.channels(), decoder.sample_rate());
let decoder_padded = decoder.mix(silence);
let decoder = decoder_padded.take_duration(my_duration);

Closing this as the question is answered. If you disagree, please write.


Opening new tab should focus in address bar

The address bar should receive focus when the user opens a new, empty tab (i.e. via command+t), otherwise the user must manually hit the address bar to navigate away from the default location.

This is now working


Processor Groups Need Memory Affinities to the Same Set of Memories as their Constituent Processors

Right now processor groups don't report any affinities for memories which they should be able to see.  As a result the high-level runtime is throwing warnings for tasks which try to map to memories which should be visible from the processor group, but appear to not be visible due to the missing affinities.

I should comment that in extreme cases this can result in unnecessary failed mappings.  I've put in a work around for now in the high-level runtime, but it eliminates an important safety check to guarantee that mapping decisions have no impact on correctness.

This wasn't an oversight - it was a conscious design choice, but one we can change if we choose to.  Processor Groups in their current form are not "discoverable" via the Machine API, and instead behave more like other user-creatable objects in Realm - the way you "discover" it is that some other task tells you about it, and it is presumed that it told you why it told you about it.  For example, it is currently up to the creator of a Processor Group to intersect the affinities of the member Processors and remember that if it chooses to.
The dynamic machine model we're moving to would allow us to treat Processor Groups the same as Processors - i.e. have them show up in Machine::get_all_processors() and have their affinities be queryable.  I'm on the fence as to whether this is desirable and worth the overhead - some amount of broadcasting would need to be added to ensure the machine reaches an (even eventually) consistent state.
Passing the discussion baton back to Mike...

Mike, any thoughts on this?

I'm not sure at the moment.  I'm kind of curious as to what your plan is going to be for a processor group that has a processor go down.  Does that invalidate the processor group or does it change it?  Does Realm report this in some way to the client?  It can't be done with event poisoning the way other things can.

With the current treatment of processor groups as application-controlled entities, Realm wouldn't do anything special if a processor that goes down is in a group.  It'd be up to the creator of the group to pay attention to the state changes for any of the processors it put into the group and take a possibly-app-specific action in response.
A task launch to a processor group for which all of the processors are down will be similar to a task launch to a single processor that's down - the task launch will fail, it will be reported via the profiling interface, and the task's finish event will be poisoned.

I'd like to close this, keeping the current semantics that processor groups are not part of the machine model.  @lightsighter , are you ok with this?

Is there a way to get the set of processors in a processor group back from Realm? I feel like I should still not be issuing warnings in this case. I'll need to check that each of the processors has affinity to each of the memories individually.

Yes, you can get the members of a group with this method:
https://github.com/StanfordLegion/legion/blob/master/runtime/realm/processor.h#L73
although this currently only works on the node that created the group.  If you need it to work on other nodes, let me know.

Commit d401afd should fix this and I don't think we will need the group members on a node different from where the group is created.  However, we may make the group on a node that is different from where the processors exist (e.g. remote mapping of a task onto a set of processors on a different node). If that works then we can close the issue. Assigning back to @streichler to confirm this is alright and then close the issue.

Ok, seems like we cannot create or query processor groups from remote nodes for now, but we will notice it if someone tries to do it. The issue with the views has been resolved so that we will perform the affinity test against the right set of processors.


Doc push job is failing

https://github.com/pytorch/vision/actions/runs/5889758887/job/15973803875
Writing objects: 100% (674/674), 1.07 MiB | 5.91 MiB/s, done.
Total 674 (delta 626), reused 3 (delta 1), pack-reused 0
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 5 was reset
  File "/home/ec2-user/actions-runner/_work/vision/vision/test-infra/.github/scripts/run_docker_with_env_secrets.py", line 95, in <module>
    main()
  File "/home/ec2-user/actions-runner/_work/vision/vision/test-infra/.github/scripts/run_docker_with_env_secrets.py", line 91, in main
    run_cmd_or_die(f"docker exec -t {container_name} /exec")
  File "/home/ec2-user/actions-runner/_work/vision/vision/test-infra/.github/scripts/run_docker_with_env_secrets.py", line 37, in run_cmd_or_die
    raise RuntimeError(f"Command {cmd} failed with exit code {exit_code}")
RuntimeError: Command docker exec -t c0fe4b46085cfd9762eebedfbeea06ff0177f327680b27fad198db09426f49d3 /exec failed with exit code 1
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
Error: Process completed with exit code 1.

@atalman @osalpekar do you think this is atest-infra issue?
cc @seemethere

Likely just https://stackoverflow.com/questions/15240815/git-fatal-the-remote-end-hung-up-unexpectedly. I'll have a look.

Error seems to have changed to
Starting download for docs
Directory structure has been setup for the artifact
Total number of files that will be downloaded: 1256
node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: EACCES: permission denied, open '/home/ec2-user/actions-runner/_work/_temp/artifacts/html/.buildinfo'
Emitted 'error' event on WriteStream instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -13,
  code: 'EACCES',
  syscall: 'open',
  path: '/home/ec2-user/actions-runner/_work/_temp/artifacts/html/.buildinfo'
}```

https://github.com/pytorch/vision/actions/runs/5892600348/job/15982535636

Closing, it's working now. Thanks a lot for https://github.com/pytorch/vision/pull/7851 @pmeier


Cannot register macro with same name

The current design limits the extensibility of the package, and I argue that no macro should be given special treatment. While I'm not sure if this is an issue when a user depends on a package registering the same name, the predefined behavior intended for Distributed.@everywhere, Turing.@model, and MacroTools.@capture prevents anyone else from registering their own macro under one of those names. This applies to the Base and Core macros too, but one could argue that users shouldn't be shadowing those names anyways. While admittedly an edge case, this issue could increase in severity as DispatchDoctor.jl becomes more widely used or even moved to Core #40.
Possible solutions
I am personally in favor of #1 or #2, maybe #4, but not #3.
1. Compare macro equality at run-time (EDIT: or compile-time?)
I think that this can be implemented by storing both the module and name of each macro in MACRO_BEHAVIOR and returning an expression from get_macro_behavior and _stabilize_all. The expression would contain an if-statement for the union of behaviors of a given name in MACRO_BEHAVIOR and the default behavior.
EDIT: This might be able to be done at compile-time (at least, in the same way that LLVM can optimize it away), since macros have unique types.
Pros:

Retains support for macros
Increases extensibility
Performance concerns are mitigated by using either @unstable or @stable default_mode = "disable"
Fixes #42

Cons:

Small increase in compile-time

Many macro expressions are small and the IncompatibleMacro case does not generate a new expression anyways

Small increase in run-time

At most an if-statement with three branches

2. Treat all macros as incompatible
Pros:

No macro is given special treatment
No need to handle the complexity of determining macro behaviors
Users can, in some cases, use @stable within macros

Macros don't compose

Small decrease in compile-time
Fixes #42

Cons:

Doesn't support docstrings
Handling macros is a useful feature
Increased false-negatives if a user writes unstable code in the macro

3. Make macro behavior opt-in only
The MACRO_BEHAVIOR dictionary would be empty by default, requiring users to register macros as needed.
Pros:

Same as #2 for macros that would otherwise be registered

Cons:

Extra work for users

Determining the behavior for macros

This may be done incorrectly, resulting in more bugs

Repeating macro registration across projects

If users share the same MACRO_BEHAVIOR as their dependencies (and I don't know if this is the case), then this can still result in non-extensibility

4. Make macro behavior toggle-able or customizable with preferences

Can be combined with previous options, and would share their respective pros and cons.

I just realized #2 wouldn't support docstrings, oops!
@stable begin
""" foo() """
foo() = 1

For 1, would this mean having an if statement over all macros, at every occurrence of a macro, which only gets evaluated at runtime?

Maybe another option is to allow a per-module register_macro!? This is done in DynamicQuantities to allow per-module unit symbol mapping

Maybe another option is to allow a per-module register_macro!? This is done in DynamicQuantities to allow per-module unit symbol mapping

For 1, would this mean having an if statement over all macros — at every occurrence of a macro — which only gets evaluated at runtime?

Unfortunately it might, but I'm not sure and am hoping to get it to compile away. I'm still working on a prototype, which is admittedly difficult. Returning an expression like I mentioned doesn't work. My next idea is to use downward callback functions to simulate modifying the expression without actually touching it so that the branch requiring the run-time macro can do it's thing without interfering. I believe this approach is similar to how Haskell handles impure functions by pretending to do work but evaluating it later.

Maybe another option is to allow a per-module register_macro!? This is done in DynamicQuantities to allow per-module unit symbol mapping

So the preferences file would additionally store the module and the macro would pass in __module__? Seems like a good idea!

Assuming the modules can be recognized, we might be able to dispatch on the macro (getproperty(parent_module, name)) itself, which is unique per module, and then I think the compiler can just toss out the unneeded methods?

By the way, I’m not sure Preferences.jl makes sense here, because Preferences is more for compiler flag-like stuff. But declaring incompatible macros seems like it should be a constant and thus live in the code.

@ven-k how is @register_unit in DynamicQuantities able to only affect the local module? I never really understood why that works. I'd like to do something similar here with a @register_macro.

Am I doing this incorrectly? Maybe it could be done by having the macro check whether the table already exists in the current module and define it if not?
julia> module A
       using DynamicQuantities
       @register_unit MyVolt 1u"V"
       end;

julia> module B
       using DynamicQuantities
       @register_unit MyVolt 2u"V"
       end;
ERROR: LoadError: Unit `MyVolt` is already defined as `1.0 m² kg s⁻³ A⁻¹`

I'm working on #1; still working on fixing tests but it might be viable.
julia> Base.remove_linenums!(@macroexpand @stable @show 1)
┌ Warning: `@stable` found no compatible functions to stabilize
│   source_info = :(#= REPL[30]:1 =#)
│   calling_module = Main
└ @ DispatchDoctor._Stabilization ~/Documents/programming/forks/DispatchDoctor.jl/src/stabilization.jl:40
quote
    var"##435"(::DispatchDoctor._Interactions.IncompatibleMacro) = begin
            begin
                Base.println("1 = ", Base.repr(begin
                            local var"#196#value" = 1
                        end))
                var"#196#value"
            end
        end
    var"##435"(::DispatchDoctor._Interactions.CompatibleMacro) = begin
            begin
                Base.println("1 = ", Base.repr(begin
                            local var"#197#value" = 1
                        end))
                var"#197#value"
            end
        end
    var"##435"(::DispatchDoctor._Interactions.DontPropagateMacro) = begin
            1
        end
    var"##435"(DispatchDoctor._Interactions.CompatibleMacro())
end

Option #1 only works for the return value of expressions, which is a pretty big limitation. But it was fun to try it out at least

Simple way to get this working: see https://github.com/MilesCranmer/DispatchDoctor.jl/blob/50faa812aec95da232467af4e03d82e28ca408bf/src/macro_interactions.jl#L57.
Maybe what we need is a 2-arg method with both the module and the macro symbol, so a user’s registered macro would only have an effect if used within that same calling module.

I think the best API would be:
@register_macro DontPropagateMacro @doc

Because @register_macro is a macro, it can access the module name where it is used.
We want the @doc macro (as an example) to go at the end, so that Julia doesn't parse it as applying to the other argument.
Then, get_macro_behavior takes an additional argument: the module it is used. Then, the MACRO_BEHAVIORS list can be something like:
const MACRO_BEHAVIOR = (;
    table=Dict([
        Symbol("@stable") => [(Main, IncompatibleMacro)],
        Symbol("@unstable") => [(Main, IncompatibleMacro)],
        Symbol("@doc") => [(Main, DontPropagateMacro)],
        Symbol("@assume_effects") => [(Main, IncompatibleMacro)],
    ]),
    lock=Threads.SpinLock()
)

Basically, the program will look up a macro symbol, and loop through the list of behaviors, and find the most specific behavior for the current module (where Main is the most generic).
So, if you have
module A
module mymacro(arg)
    return esc(arg)
end
@register_macro DontPropagateMacro @mymacro
end

Then it will create (or push to) the symbol in the macro table:
behaviors = get!(MACRO_BEHAVIOR.table, Symbol("@mymacro"), Tuple{Module,MacroBehavior}[])
# ^ This will automatically create the array if it does not exist

push!(behaviors, (A, DontPropagateMacro))

And so whenever @stable is used within A, it will prefer macro symbols defined in the table with that context.

However, I do feel like this is a bit complicated, and it would be better to take @ven-k's approach. I still don't quite understand how it works though and if it's possible to use it here.

Maybe what we need is a 2-arg method with both the module and the macro symbol, so a user’s registered macro would only have an effect if used within that same calling module.

This fixes the problems I had trying to compare macros by identity! It is a bit more limited such that an external package cannot register defaults for arbitrary modules though.

Ah, my non-org notifications are sent to an inactive mail; almost missed this thread.
So in an external package like ExternalUnitRegistration.jl the imported collections like ALL_SYMBOLS, UNIT_SYMBOLS are mutated by pushing the new registrations to it (Ex: MyWb).
These new values can be accessed and worked with within the scope of ExternalUnitReg module. This allows to work with u"MyWb" syntax and work just like other DynamicQ units. However, as these are imported collections, the changes don't live outside this module's scope.
But we can still use that MyWb as a variable, because a new variable is explicitly declared in the "ExternalUnitRegistration" module here. As it is of the same DEFAULT_QUANTITY_TYPE type, the unit-arithmetic just works.
(While anything that depends on looking up the UNIT_SYMBOLS etc (ex: @u_str) don't work)


Disable flaky test test_operator.test_dropout (v1.3.x)

Description
Disable flaky test test_operator.test_dropout which is failing on the v.1.3.x branch:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/v1.3.x/97/pipeline
======================================================================
FAIL: test_operator.test_dropout
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Anaconda3\envs\py3\lib\site-packages\nose\case.py", line 197, in runTest
    self.test(*self.arg)
  File "C:\jenkins_slave\workspace\ut-python-gpu\tests\python\unittest\common.py", line 173, in test_new
    orig_test(*args, **kwargs)
  File "C:\jenkins_slave\workspace\ut-python-gpu\tests\python\unittest\test_operator.py", line 5853, in test_dropout
    check_dropout_ratio(0.0, shape)
  File "C:\jenkins_slave\workspace\ut-python-gpu\tests\python\unittest\test_operator.py", line 5797, in check_dropout_ratio
    assert exe.outputs[0].asnumpy().min() == min_value
AssertionError:
-------------------- >> begin captured logging << --------------------
common: INFO: Setting test np/mx/python random seeds, use MXNET_TEST_SEED=428273587 to reproduce.
--------------------- >> end captured logging << ---------------------

Issue tracked here: https://github.com/apache/incubator-mxnet/issues/12329
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@nswamy @szha

@mxnet-label-bot [pr-awaiting-review]

merging as the test that failed is unrelated to this PR.


[BUG] Type definitions of ‘SentinelHandle.degradeRuleCount’ and 'Sentinel DegradeRule.count ' are inconsistent.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When the DegradeRule grade is ‘EXCEPTION_RATIO’, its value cannot be set to the corresponding ratio value.When the DegradeRule grade is ‘EXCEPTION_RATIO’, its value cannot be set to the corresponding ratio value.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s): 2.4.1

Debug logs
No response
Anything else?
No response

can you fix it，

OK, I'll try.


Fix pandas-2.1 futurewarnings

Codecov Report
Patch coverage: 68.42% and project coverage change: +0.09% :tada:

Comparison is base (19c4214) 77.40% compared to head (14b7dde) 77.50%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #40      +/-   ##
==========================================
+ Coverage   77.40%   77.50%   +0.09%
==========================================
  Files           9        9
  Lines         708      720      +12
  Branches      189      164      -25
==========================================
+ Hits          548      558      +10
- Misses        132      133       +1
- Partials       28       29       +1

Files Changed
Coverage Δ

src/pandas_indexing/units.py
63.88% <20.00%> (-2.46%)
:arrow_down:

src/pandas_indexing/core.py
84.79% <85.71%> (+1.11%)
:arrow_up:

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


GET request with body

I know it's not standard practice, but it's allowed and makes sense in certain situations.
Would this be something to consider?
http://stackoverflow.com/questions/978061/http-get-with-request-body

Hmm. In which situation would it make sense?

Good question. I had a pretty GET call with quite a few params from one
backend service to the other. I figured there was a max size to the url
length (and therefore I needed to pass them along in the body). Actually,
that's just a browser limitation (if I'm not mistaken), so I implemented it
as query params anyways.
You can close this issue :)

Cool, thanks man.


AnalyticsWithoutAdIdSupport framework download

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5
Firebase SDK version: 8.1.0
Installation method: Zip file  (select one)
Firebase Component: Core (Auth, Core, Database, Firestore, Messaging, Storage, etc)

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Download the framework but could not know how to use AnalyticsWithoutAdIdSupport
This is not really a bug, I am not use cocapod but manual download the framework. But I am not find the AnalyticsWithoutAdIdSupport.framework to use in my project

@dzungpv Thanks for the report. AnalyticsWithoutAdIdSupport is not currently supported from the zip distribution or Carthage.  A workaround is to replace GoogleAppMeasurement.xcframework with the GoogleAppMeasurementWithoutAdIdSupport.xcframework specified in the CocoaPods podspec.

This is tracked internally at b/190006205


Internal error occurred: failed calling webhook

Description
Observed Behavior:
{"level":"ERROR","time":"2023-07-28T15:32:59.986Z","logger":"controller","message":"Reconciler error","commit":"5b469b8-dirty","controller":"awsnodetemplate","controllerGroup":"karpenter.k8s.aws","controllerKind":"AWSNodeTemplate","AWSNodeTemplate":{"name":"default"},"namespace":"","name":"default","reconcileID":"02565d5d-e127-4fa1-a26b-765e1f594c87","error":"Internal error occurred: failed calling webhook \"defaulting.webhook.karpenter.k8s.aws\": failed to call webhook: Post \"https://karpenter.karpenter.svc:8443/default/karpenter.k8s.aws?timeout=10s\": context deadline exceeded"}

Expected Behavior:
I would expect to be able to reach the webhook
Reproduction Steps (Please include YAML):

Run Linkerd and inject all pods in this namespace

    dnsPolicy: ClusterFirst
    serviceAccount:
      annotations:
        eks.amazonaws.com/role-arn: "arn:aws-us-gov:iam::xxxx:role/karpenter-qa-karpenter"
    nodeSelector:
      kubernetes.io/os: linux
      dedicated: "true"
    tolerations:
      - key: CriticalAddonsOnly
        operator: Exists
      - operator: Exists
    serviceMonitor:
      enabled: true
      additionalLabels:
        release: kube-prometheus-stack
    replicas: 2
    logLevel: info
    logEncoding: json
    controller:
      resources:
        requests:
          cpu: 100m
          memory: 256M
    settings:
      batchMaxDuration: 15s
      batchIdleDuration: 2s
      aws:
        defaultInstanceProfile: "karpenter-qa-karpenter"
        clusterName: "eks-qa-cluster"
        clusterEndpoint: "https://xxxx.gr7.us-gov-west-1.eks.amazonaws.com"
        interruptionQueueName: "karpenter-qa-karpenter"
      featureGates:
        driftEnabled: true

Versions:

Chart Version:  v0.29.2
Kubernetes Version (kubectl version):  1.27

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Can you confirm that your webhooks are working correctly?

@engedaam
If you can tell me how one would tell you that, i can do it.
Thanks.

maybe you should upgrade aws-alb-controller?

Can you try enabling debug logging for the webhook? By default the webhook is using loglevel.webhook: error
https://karpenter.sh/docs/troubleshooting/#enable-debug-logging.
Additionally, there are some instructions here https://karpenter.sh/docs/troubleshooting/#failed-calling-webhook-validationwebhookprovisionerskarpentersh

Hello @ellistarn
The problem was fixed.
The issue was related with wrong security group, I cırrected the security group and the problem disappeared.
Thanks & Regards

@ellistarn
Can we reopen this? This issue is not fixed for us.

Apologies for the confusion. I was a bit confused with how security groups were related. Did you get a chance to try any of the trouble shooting steps above?

Hello,
Sorry, I think I confused things. I faced with cpl of problems during the installation; changing security group is one of them but as you indicated, it maybe the solution of something else.
I had to upgrade aws-load-balancer controller.
Regards

Hello,
Sorry, I think I confused things. I faced with cpl of problems during the installation; changing security group is one of them but as you indicated, it maybe the solution of something else.
I had to upgrade aws-load-balancer controller.
Regards

Hello,
Sorry, I think I confused things. I faced with cpl of problems during the installation; changing security group is one of them but as you indicated, it maybe the solution of something else.
I had to upgrade aws-load-balancer controller.
Regards

Hello,
Sorry, I think I confused things. I faced with cpl of problems during the installation; changing security group is one of them but as you indicated, it maybe the solution of something else.
I had to upgrade aws-load-balancer controller.
Regards

For any confused readers, there was a comment above by adm-mkarakas suggesting the issue was resolved and led to the issue being closed, but the comment was deleted.

I'll be able to touch this tomorrow. Been on vacation


Remove table cell view focusedRecycleCallback

Pull Request
🤨 Rationale
#2202
👩💻 Implementation

Remove TableCellView focusedRecycleCallback() and TableRow closeOpenActionMenus() (both were called on virtualizer updates).

KeyboardNavigationManager focuses the active cell on scroll in handleChange(), which has the same effect.

Update column HLD template to remove section about focus recycling

🧪 Testing

Manually tested table action menus and anchor + menu button columns with scrolling, ensured behavior is the same as before
Tests were already present to ensure that interactive cell content (e.g. anchor) is blurred on scroll, and that menu buttons in cells are closed on scroll.
Added new tests to ensure cell action menus are still closed after a scroll.

✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@mollykreis can you buddy this PR?


Refactor max font size code to improve maintainability / extensibility

This PR refactors the code that enforces a maximum font size when drawing shield text.  The previous code included a bunch of math that I figured out on the back of a napkin that's essentially incomprehensible.  I removed this in favor of a more-understandable Math.min() function to limit the font size.  This is a needed step to support additional text layout improvements including vertical alignment and half-elliptical layout constraints, which will improve the text layout appearance of half-rounded shields such interstate and Virginia state route shields.
This PR should have no impact on rendering or performance.

Found a bug, will re-post as a comprehensive fix for #114


How to handle non-prod environments?

Do I need to create a separate app definition for prod, staging, and local dev?

👋  You currently have to create a new app definition. Development environments/stages are currently not supported for apps.


Speed up compilation

Right now, we compile all sources separately for each extension. That's pretty slow and unnecessary, since there is a lot of duplication: many extensions use the same basic sources multiple times. We should set up Meson in such a way that these shared items are compiled only once, and then linked once into the actual extensions.

This SO question might be helpful. We have the exact same problem. I'm tinkering with this a bit now.

This should be possible, but we need to be careful to avoid linking errors. It's probably not worth figuring all this out right now, since it's typically 'fast enough'.

Solved in #58 already.


Atom interface is corrupted on macOS 10.11.6 on versions > 1.19.2

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom interface is completely corrupted (graphical glitches) after update to 1.19.3, 1.19.4 or 1.19.5.
--safe mode make no changes. Atom < 1.19.3 has no issues.

Steps to Reproduce

Update Atom to 1.19.3+.
Run Atom.
As soon as the application starts interface graphics is completely corrupted.

Expected behavior: [What you expect to happen]
Interface without graphical glitches.
Actual behavior: [What actually happens]
Interface is completely corrupted - not possible to use.
Reproduces how often: [What percentage of the time does it reproduce?]
100% - each time I launch Atom > 1.19.2.
Versions
Atom    : 1.19.5
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0

Thanks for reaching out!

Do you see any errors in the developer tools console?
Have you tried clearing saved state or resetting to factory defaults as mentioned in the flight-manual?

Unfortunately, the whole interface is corrupted - I can see nothing inside Atom window (check a screen when I toggle Dev tools inside Atom).

Yes, I've done atom --clear-window-state. No changes in behaviour.
Installing 1.19.2 back fixes the issue.
In macOS Console I see these messages:

9/5/17 13:46:15.360 Atom Helper[5204]: <<<< VTVideoEncoderSelection >>>> VTSelectAndCreateVideoEncoderInstanceInternal: no video encoder found for 'avc1' 9/5/17 13:46:15.360 Atom Helper[5204]: [13:46:15.360] VTSelectAndCreateVideoEncoderInstanceInternal signalled err=-12908 (err) (Video encoder not available) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.207/Sources/VideoToolbox/VTVideoEncoderSelection.c line 1308 9/5/17 13:46:15.360 Atom Helper[5204]: [13:46:15.360] VTCompressionSessionCreate signalled err=-12908 (err) (Could not select and open encoder instance) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.207/Sources/VideoToolbox/VTCompressionSession.c line 1003

@mrdc Thank you for the additional information :bowing_man: Can you run atom --foreground and see if there is any additional output?

Here you go:
atom --foreground
[9056:0905/145902.547433:INFO:CONSOLE(70096)] "Failed to require the main module of 'platformio-ide-terminal' because it requires one or more incompatible native modules (bin, bin, bin, bin, bin, bin, bin, bin).
Run apm rebuild in the package directory and restart Atom to resolve.", source:  (70096)

@mrdc I have some more questions, if you could answer them that would be great, thanks 🙇
The error you are seeing when running Atom in the foreground can be fixed by running apm rebuild inside the ~/.atom/packages/platformio-ide-terminal folder. Can you try doing this to see if that changes anything? See the commands you need to run below:
cd ~/.atom/packages/platformio-ide-terminal
apm rebuild

How did you install Atom?
From where did you download Atom?
In what directory is Atom installed?
Can you verify that you tried resetting to factory defaults? When I first asked about this you only answered that you tried to clear window state.
Is there something unique about your system/hardware that you can tell us about?

cd ~/.atom/packages/platformio-ide-terminal
app rebuild
No changes - the same issue.
Long time ago from zip from the Atom website. Was updating via auto-update.
See above.
/Applications.
Yes, I have tried resetting to factory defaults - see screenshot:

Yes, it's macOS running on Sony laptop :) Other software works fine - as Atom did before 1.19.3.

Thanks @mrdc - was taking a look at this issue too and just so I'm on the same page, can you copy and paste from Terminal a transcript of running these commands and their full output?  Thanks for bearing with us :v:
cd ~/.atom/packages/platformio-ide-terminal
apm rebuild
atom --clear-window-state

Lastly, if you have any other Electron apps installed (e.g. Slack, VS Code, etc.) can you check if you see any similar problems?  And the same with Chrome?

Lastly, if you have any other Electron apps installed (e.g. Slack, VS Code, etc.) can you check if you >see any similar problems? And the same with Chrome?
Yes, the same issue with Slack - "Reset app data" helps for a while, then it's again becomes corrupted.

Thanks @mrdc :+1:

Yes, the same issue with Slack

Oh interesting, so it seems like this is maybe an Electron issue rather than an Atom issue yeah @Ben3eeE?

I had this problem today after update on a mac.  This is a similar problem I had with Chrome a while back. To fix run  "atom --disable-gpu" in the terminal that should clear it up

Electron issue rather than an Atom issue yeah @Ben3eeE?

Yeah it does sound like an Electron issue.

To fix run "atom --disable-gpu"

That was what I was going to recommend after learning that it is an Electron issue :+1:
@mrdc Does atom --disable-gpu work for you?

@ekajmada

To fix run "atom --disable-gpu" in the terminal that should clear it up

Thanks! It fixed the issue.
@Ben3eeE

Yeah it does sound like an Electron issue.

Electron wasn't updated - 1.6.9 has worked fine for Atom < 1.19.3.

Atom 1.21.0 - the same issue :(


Removes 3.6 classifier

Dear @gaborbernat,
thanks a stack for conceiving and maintaining this excellent package.
Following up on GH-106, we would like to point out https://github.com/panodata/verlib2/pull/8, where a recent version of pyproject-fmt removes the Python 3.6 classifier. We know it is EOL, but some packages still want to support it.
With kind regards,
Andreas.

We do respect the value set in pyproject.toml https://github.com/tox-dev/pyproject-fmt/blob/main/src/pyproject_fmt/formatter/project.py#L67C5-L67C13 so it really shouldn't. PR welcome if the bug is on our side.

PR welcome if the bug is on our side.

Thank you. While not 100% correct, GH-138 fixes the issue for us.

To elaborate a bit why the fix is not 100% solid, other than what has been outlined in the PR description:

The default value of _PY_MIN_VERSION is already used at L67.
Then, it is also used at L76, which is probably not intended. Instead, it should be derived from the parsed SpecifierSet in specifiers, which already resolved the requires-python setting, but differently than it is done right now, also considering "minimum versions" instead of just resolving the max_version_specifier.

I cannot accept an incorrect solution though 🤔

I am sharing your sentiment. There is clearly a flaw in the logic, and the test suite does not catch it, just to outline that it is not a special case, and will trip in other situations as well.

Oh, the test suite actually fails, demonstrating that my fix makes it worse. It looks like I am having a very bad day, apologies Bernát.

The patch GH-138 has been amended according to your suggestions to do it in the right way. Thanks for your patience.


data-parsley-excluded form attribute is not working

data-parsley-excluded doesn't work when trying to set it explicitly for different forms.
(parsley.js 069a721fafd9a76388dca8023ea37043fb9dab07)
In Parsley init() function parsleyFormInstance.options paremeter is not taken into account  when creating new ParsleyOptionsFactory (ln:68). Therefor the parsley input options don't have correct selector for excluded elements (ln:76). ParsleyDefaults can be overriden only by setting ParsleyConfig globally or by setting the options when initializing Parsley on forms separately.
parsleyFormInstance.options should be taken into account when creating new ParsleyOptionsFactory.

I believe this was fixed by #809 :smile:
Let me know if that's not the case...

thank you @vellotis, I had to use this setup as well:
window.ParsleyConfig = {
  errorsWrapper: '

',
  errorTemplate: '',
  excluded:
     // Defaults
    'input[type=button],' +
    'input[type=submit],' +
    'input[type=reset],'  +
    'input[type=hidden],' +
    '[disabled],'         +
    ':hidden,'            +
     // -- Additional attributes to look --
    '[data-parsley-disabled],' +  // Exclude specific input/select/radio/checkbox/etc
    '[data-parsley-disabled] *'   // Exclude all nesting inputs/selects/radios/checkboxes/etc
};

to make sure disabled fields i.e.
          div[class="signin-remember-me"]
            = f.check_box(:remember_me, class: "large text-field", id: "signin-remember-me", "data-parsley-disabled" => "")
            label[for="signin-remember-me" class="signin-remember-me-label"]

were not validated.

still broken. does not validate hidden fields even if options are set.
http://stackoverflow.com/questions/25162059/parsley-js-2-x-how-do-you-validate-hidden-fields/38122501#38122501

@bnomel please provide an working example, for example starting from http://codepen.io/marcandre/pen/jqbzyN?editors=101

i am sorry. it works in a simple example. so it must be my error somewhere. maybe 200 forms on one page are not a good idea. ;-)
http://codepen.io/anon/pen/XKRyqG


Revert "Adding an Anyball item to the release config"

Reverts PokemonGoF/PokemonGo-Bot#2140, because it is causing error:
Traceback (most recent call last):
  File "./pokecli.py", line 465, in <module>
    main()
  File "./pokecli.py", line 70, in main
    bot.tick()
  File "/root/testen/dev-ptc2/pokemongo_bot/__init__.py", line 86, in tick
    if worker.work() == WorkerResult.RUNNING:
  File "/root/testen/dev-ptc2/pokemongo_bot/cell_workers/recycle_items.py", line 18, in work
    self.recycle_pokeballs()
  File "/root/testen/dev-ptc2/pokemongo_bot/cell_workers/recycle_items.py", line 72, in recycle_pokeballs
    recycle_amount = total_amount_of_balls - number_of_balls_to_keep
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'```

Ensuring that the required key was added to the item filter in config.json fixed this error for me.
ie,
     "item_filter": {
                "Pokeball":       { "keep" : 100 },
                 // etc

The key shouldn't be required, though. :)


Too high performances??? Am i doing it right?

Hi all!! i'm using one of the examples (neon_cnn) to test the performances of NEON. I've been using  F32 Datatype and these are the results i get. To me, they seem way too good, what do you think about it?

Hi @GAnto85,
Performances are platform specifics, so it is very difficult for us to confirm or not without knowing where you run the code.
Anyway I think the best way for you would be to compare the outputs with a reference implementation that you trust.
Best,
Manuel

Thanks for you reply!


Better docs or video

It was pointed out to me that at the moment only a small sliver of the Angular community has touched all the right pieces of tooling, for this example repo to make any sense.
Therefore, TODO, make more comprehensive doc or video explaining it.

Some feedback I got internally:

Make it more obvious that the intro to the project, the "many to many to many" connection between features, applications, and backend technologies.
The ideas were trying to communicate here will be more clear once more of the backend stuff is wired up.
Specifically make it more obvious that this is intended to illustrate that one enterprise application suite is likely to use all of REST, GraphSQL, MQTTs, whatever...  not to just pick one winner, but to grow over time to include a variety of technologies.
Some kind of "map" to find examples of various ideas. We could use this when we teach Angular Boot Camp as well.


test: add validation tests for embedded

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows conventional commit format
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #141
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Handle path parameters for arrays correctly

The parameters for serialized arrays was using the same deserialization check.
There are different formats for header, query and path. Split up the validation of arrays into two different sets to allow different validation for path and header/query parameters.
The changes will validate path parameters for arrays but not objects which is still not working.
Because of objects within path parameter is probably the most unused things in the specs these have been left out intentionally.

Thanks @tjcambio !


Incorrect example for SelfManagedAuthentication

When we follow example from the README:

we get:

We're using the latest (8.5.0) version of the TaskList Client. From the looks of it we'll have to specify an IdentityConfig as well?

Hi @jancalvef,
Thanks for raising the issue. The authentication mechanism is coming from https://github.com/camunda-community-hub/spring-zeebe/tree/main/camunda-sdk-java/java-common and may change without this README being update :/
To make it easier, I've change the README to promote the helpers we introduced in the client builder and that encapsulate the "auth soup".
Thanks again!


Path field doesn't maintain Regular expression checking. It accepts any sequence of characters

Update: This would be tested once Path element is implemented.
@tulir @xylix keep this issue in your mind when implementing the path element.

Closing in favor of #171.


Clarify preferred "props default to true" expr

The current text is ambiguous without reading further into the paragraph -- until I re-read this text, I was trying to avoid both types of syntax because it seemed to imply that it wans't recommended (eg "props default to true" --> "we don't recommend using this").
If your PR references an existing issue, please add the issue number below:
https://github.com/facebook/react/pull/10777

Actually, we do suggest the latter form, not the former. The 'this' is referring to the heading "If you pass no value for a prop". I tweaked your PR to be clearer. Thank you for the effort!

“We don’t recommend not passing” is awkward. “We recommend always passing the value explicitly” would be better. :-)


Volume bug fix #2202

Onhidden function was resetting volume to 1.0 in case volume is not defined. In case volume is not defined, means that onShown has not been called and hence volume should be same as  current volume.

Awesome, thanks for fixing that!


Remove _computedBindings from can.Map

Per @justinbmeyer, _computedBindings was added to support can.compute's being defined on a can.Map's prototype. Like this...
var SpecialMap = can.Map.extend({
  firstName: 'Chris',
  lastName: 'Gomez'
  fullName: can.compute(function () {
    return this.attr('firstName') + ' ' + this.attr('lastName');
  })
});

Now that we have the Define plugin, and especially the type: 'compute' (added in #1470), there's no/less(?) of need for _computedBindings anymore.
From what I can tell we should be able to use .isComputed to detect computes and track the number of bindings on a can.Map's property in bind and unbind alone without having to do things like this and this.
Here are the instances I found post #1470.
totes:canjs akagomez$ grep -rn "_computedBindings" --exclude=./build\* --exclude=./dist\* --exclude=./test\* .
./list/list.js:91:				this._computedBindings = {};
./map/define/define.js:309:				this._computedBindings[attr] = {
./map/lazy/lazy.js:17:			this._computedBindings = {};
./map/map.js:277:				this._computedBindings = {};
./map/map.js:314:				this._computedBindings[prop] = {
./map/map.js:454:					if (this._computedBindings[attr]) {
./map/map.js:534:				if ( this._computedBindings[prop] ) {
./map/map.js:541:				if ( typeof this.constructor.prototype[prop] !== 'function' && !this._computedBindings[prop] ) {
./map/map.js:547:				var computedBinding = this._computedBindings && this._computedBindings[eventName];
./map/map.js:576:				var computedBinding = this._computedBindings && this._computedBindings[eventName];
./map/map_test.js:223:		equal(map._computedBindings.name.count, 2, '2 handlers listening to computed property');
./map/map_test.js:226:		equal(map._computedBindings.name.count, 0, '0 handlers listening to computed property');
./map/map_test.js:227:		ok(!map._computedBindings.name.handler, 'computed property handler removed');

I'm not so sure about this.  I think this is a useful flag to tell if a value is not directly on the map.

computedBindings is still useful, but we've removed trackCompute. Closing.


New windows should be maximized when opened

Issue Type: Feature Request
Why make millions of developers hit a button every time they open a new window?
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:09:06.581Z)
OS version: Darwin x64 18.7.0
Restricted Mode: No

Did you try out the window.newWindowDimensions setting?

That worked, thanks! Seems like maximized should be the default.


Add sphinx-autobuild

Summary
I added sphinx-autobuild to dependencies.
You can automatically build the docs by running
sphinx-autobuild docs docs/_build/html

Codecov Report
Base: 96.05% // Head: 96.09% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (0c00ff3) compared to base (74204f1).
Patch coverage: 95.23% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #157      +/-   ##
===========================================
+ Coverage    96.05%   96.09%   +0.04%
===========================================
  Files           22       22
  Lines         2510     2511       +1
===========================================
+ Hits          2411     2413       +2
+ Misses          99       98       -1

Impacted Files
Coverage Δ

ssspy/bss/_solve_permutation.py
94.44% <50.00%> (+2.33%)
:arrow_up:

ssspy/bss/_flooring.py
100.00% <100.00%> (ø)

ssspy/bss/_update_spatial_model.py
98.73% <100.00%> (-0.02%)
:arrow_down:

ssspy/bss/fdica.py
91.86% <100.00%> (ø)

ssspy/bss/ica.py
92.79% <100.00%> (+0.03%)
:arrow_up:

ssspy/bss/ilrma.py
97.18% <100.00%> (ø)

ssspy/bss/iva.py
95.85% <100.00%> (+0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Cannot see Brand accounts in Android

Cannot see Brand accounts in Android. But this can be seen in iOS.
Steps to create brand account:

SignIn on Youtube and create multiple channels in settings.

Now try signIn on iOS brand accounts are listed once you login with main credentials.
But this cannot be seen on Android. @devfd Please check.

Duplicated #346


Implement a Engine::run method

Draft: needs more doc, tests, maybe a trait.
Implement a Engine::run method
Make Engine::update private
This makes the Engine a bit more foolproof, preventing anyone from forgetting to call Engine::update.

Hey, @pierre-l, thanks so much for this PR!
I really like the direction you're going with here, and I think this is definitely going to be something we eventually move towards - probably something similar to Bevy's App API.
 What I'm really trying to do with Hotham is make it emerge as a result of building games. I'm still yet to build a game with Hotham (YET!) so I haven't got much of a feel for how the API is going to work, but I really want to make sure our future work on the project is shaped by these kinds of real world experiences.
I hope this hasn't dissuaded you (or anyone else!) from contributing to the project - I just want to emphasise again how happy it makes me to wake up in the morning and see this kind of PR.

Hey @kanerogers, all good! That's pretty much the reason it was unfinished: it felt nice but maybe premature.

Thanks for the feedback!


add certs branch

If you decide to use python, you may even try to validate if the domain names:

no duplicate domain names
domain names follows standard domain name regex


BufferUnderflowException is thrown if UserFlags D and/or H in KerbValidationInfo is set, but the actual pointers are NULL

The following exception can be observed:
2024-09-29T16:21:23.581 SCHWERWIEGEND [https-openssl-apr-8444-exec-29] org.apache.catalina.core.StandardHostValve.invoke Exception Processing [/foo]
    java.nio.BufferUnderflowException
        at java.nio.Buffer.nextGetIndex(Buffer.java:532)
        at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:366)
        at net.sf.michaelo.tomcat.pac.PacDataBuffer.getUnsignedInt(PacDataBuffer.java:84)
        at net.sf.michaelo.tomcat.pac.KerbValidationInfo.<init>(KerbValidationInfo.java:231)
        at net.sf.michaelo.tomcat.pac.Pac.<init>(Pac.java:147)
        at net.sf.michaelo.tomcat.realm.PacDataActiveDirectoryRealm.getPrincipal(PacDataActiveDirectoryRealm.java:157)
        at org.apache.catalina.realm.RealmBase.authenticate(RealmBase.java:495)
        at net.sf.michaelo.tomcat.authenticator.SpnegoAuthenticator.doAuthenticate(SpnegoAuthenticator.java:158)

It turns out that in some cases (which are unclear) extraSidsPointer is 0 (NULL), but EXTRA_SIDS_USER_FLAG (flag D) is set in UserFlags. We need extra checks here.

The actual issue should not happen IMHO. If you look at https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-pac/69e86ccc-85e3-41b9-b514-7d969cd0ed73 it is expected that if the flags are set the pointers should not be NULL. At least Samba's code makes it sure:

https://github.com/samba-team/samba/blob/f749330ddaba04cdae20570a9e842327715f3594/auth/auth_sam_reply.c#L399-L404
https://github.com/samba-team/samba/blob/f749330ddaba04cdae20570a9e842327715f3594/python/samba/tests/krb5/raw_testcase.py#L4195-L4214

Will inquire with the Samba team for their opinion.

This is sets the flag no matter what: https://github.com/samba-team/samba/blob/f749330ddaba04cdae20570a9e842327715f3594/source3/auth/server_info.c#L599-L613


Publish Maps Notebook 24 - Datapane - Invalid version 'unknown'

Thanks for these lessons and videos. A great resource.
Environment Information

geemap version: 0.8.14
Python version: 3.9.2
Operating System: macOS 10.15.7

Description
I am trying to run the Example notebook 24 Publish Maps https://github.com/giswqs/geemap/blob/master/examples/notebooks/24_publish_maps.ipynb
What I Did
I signed up and created a Datapane account and followed all the cells from your notebook.
To confirm datapane is set up I ran:
import datapane as dp
dp.ping()

Response:
Connected successfully to https://datapane.com as {username}

Where it breaks is here:
Map.publish(name='gee_folium_map', headline='Terrain Visualization', visibility='PUBLIC', overwrite=True)

Response:
Invalid version: 'unknown'

Thanks for reporting. The recent datapane release changes the API and some parameters for the publish functions are no longer valid. This bug has been fixed. Please update geemap using geemap.update_package() and try the following.
https://github.com/giswqs/geemap/blob/master/examples/notebooks/24_publish_maps.ipynb
Map.publish(name='Terrain Visualization', description='A folium map with Earth Engine data layers', visibility='PUBLIC')

hello,Mr.wu.
It seem that i got the similar problem in the 24_publish_maps.ipynb which is shown in the following.
env
geemap version: 0.9.4
Python version: 3.9.7
Operating System:Ubuntu 20.04.3 LTS
run and  got


Splitting out examples to a separate repository?

The pantilt_bot_description and open_manipulator_x_description example packages are great, but I think it would be better split them out into a separate repository for two reasons.

When building from source, I often use rosdep to install package dependencies. If I want to use the dynamixel_hardware package only, I still have to clone the other two packages add an AMENT_IGNORE file to the example packages to prevent unnecessary dependencies getting installed (eg. realsense2_description is not available in rolling) and getting built. If the repositories were separate, I wouldn't have to do this.
When releasing the package, bloom will usually release all packages in the repository together. I'm not sure if you intend to release pantilt_bot_description and open_manipulator_x_description. The version numbers of all package numbers must be increased together.

I don't know if I can get around to doing this, but want to hear your thoughts @youtalk.

It's a nice idea. I'm going to do it.

Done. https://github.com/dynamixel-community/dynamixel_hardware_examples


[API][PUT/user/profile]Response status is shown 200 OK instead 400 after an invalid parameter was entered in the "name" field

Environment: Windows 10, Postman
Reproducible: always
Build found: 02.12.2023
Preconditions
The user is logged in, and the token is gotten.
Steps to reproduce

Send the request PUT https://greencity-user.greencity.social/user/profile. In the body of the request fill in"name": "88888888888". All other parameters are valid.
Body:

{
  "coordinates": {
    "latitude": 50.4501,
    "longitude": 30.5234
  },
  "name": "88888888888",
  "showEcoPlace": true,
  "showLocation": true,
  "showShoppingList": true,
  "socialNetworks": [
    "https://www.instagram.com/mostlycamomile/",
    "https://m.youtube.com/watch?v=NuXdxMEbYeQ",
     "https://rozetka.com.ua/ua/",
     "https://www.tiktok.com/@mostlycamomile_?_t=8homYQ0MFoU&_r=1"

  ],
  "userCredo": "***********************************"
}

Pay attention to the status code.

Actual result
The status code is 200 OK.
Expected result
The status code is 400 (Bad request). The user shall see the error message "name must contain only "ЁёІіЇїҐґЄєА-Яа-яA-Za-z-'0-9 .", dot can only be in the center of the name, numbers cannot be at the start"
User story and test case links
E.g.: "User story https://github.com/ita-social-projects/GreenCity/issues/4277
Labels to be added
"Bug", Priority ("pri: Medium"), Severity ("severity:Minor"), "API" (for back-end bugs).

It is 200


Bugfix: cleanup didn't unswizzle classes that had already been swizzled

This would happen when using other code that itself swizzles classes (i.e. ReactiveCocoa). For example, if a rac_signalForSelector was called on an object then later an aspect hook was installed and further removed, we would end up in a situation where Aspect's class swizzling (in-place swizzling of -forwardInvocation:) would never be ununstalled when the last hook was removed, later wrecking havoc with RAC's own use of -forwardInvocation.
In short, this pull request fixes hair-pulling crashes.

To make things crystal clear, this fixes properly reverts the -forwardInvocation swizzling done by:
https://github.com/steipete/Aspects/blob/master/Aspects.m#L358

lgtm - thanks!


[release] Add a flag to auto-config releases to disable checksums

Checksums are always enabled. Add a flag to disable generating checksums.

🎉 This issue has been resolved in v1.7.0 (Release Notes)


/eth/v1/beacon/pool/attestations not aligned with current spec

https://github.com/ethereum/eth2.0-APIs/pull/102 changed the body type of /eth/v1/beacon/pool/attestations from an object to an array, to allow for more efficient submission of attestations.  It appears that Teku does not yet support this.  Will this be implemented prior to mainnet release?

Thanks for raising this. I'll have a look at it today, our intent would be to support it prior to mainnet release.


Fixed filenames containing trailing spaces

When saving with some of the new options introduced in here, the resulting filename contains spaces at the end. This can be easily seen by executing the name = ... statements on console.

Oh you're absolutely right, that's better. Thank you so much for noticing it, also for fixing the whitespace in the output ile name


Fix Group::copyToConduitNode so that it handles lists correctly

Summary

This PR is a bug fix
It does the following (modify list as needed):

Modifies Group::copyToConduitNode to handle Groups using the list format.j
Fixes #928

This method had the assumption that all child items have a name.  This fix adds handling of unnamed items held in a list, and creates lists of unnamed child Nodes in the conduit output.

I need to add a suitable test before merging.