Add Clang 15

Clang 15 was missing in the Docker images, but was now added, see https://github.com/silkeh/docker-clang/issues/23.

Coverage remained the same at 100.0% when pulling 6e45edc2c0da0e2091684d6795e530df375e5690 on clang_15 into a3e6e26dc83a726b292f5be0492fcc408663ce55 on develop.


Move task completion listener registration to after variables are initialized

Discovered during the analysis of #8473.  This fixes some potential NPEs by registering a task completion listener before the variables referenced by the completion listener are initialized.  If an exception is thrown after the listener is registered but before the variables are initialized, the completion listener callback can dereference a null member variable.

build


Add 0.6 release announce

Signed-off-by: Jian Qiu<EMAIL_ADDRESS>

/hold
still waiting for more input.

So many great enhancements!
Are there docs for the new features beyond the repo READMEs (for the cluster proxy and ManagedServiceAccount)? Would it be helpful to link to those docs/getting started pages if they exist?

@mdelder the doc for cluster-proxy and managed-serviceaccount is already available at:
https://open-cluster-management.io/getting-started/integration/cluster-proxy/
https://open-cluster-management.io/getting-started/integration/managed-serviceaccount/
additionally there's a tutorial for plumbing up these addons together:
https://open-cluster-management.io/scenarios/pushing-kube-api-requests/

So many great enhancements!
Are there docs for the new features beyond the repo READMEs (for the cluster proxy and ManagedServiceAccount)? Would it be helpful to link to those docs/getting started pages if they exist?

Thanks, added some overview with each key feature and the links to relating docs/examples.

/lgtm

/unhod

/unhold


Tag overview

Codecov Report

Merging #39 into master will increase coverage by 2.21%.
The diff coverage is 76.81%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
+ Coverage   78.85%   81.07%   +2.21%
==========================================
  Files          40       43       +3
  Lines         700      766      +66
  Branches       69       75       +6
==========================================
+ Hits          552      621      +69
+ Misses        117      111       -6
- Partials       31       34       +3

Impacted Files
Coverage Δ

...ta/rendering/pages/pojos/DetailPageCollection.java
100% <ø> (ø)
:arrow_up:

...java/com/trivago/rta/constants/PluginSettings.java
0% <ø> (ø)
:arrow_up:

...trivago/rta/rendering/pages/StartPageRenderer.java
71.87% <100%> (-0.63%)
:arrow_down:

...vago/rta/rendering/pages/pojos/PageCollection.java
100% <100%> (ø)

...rta/rendering/pages/pojos/StartPageCollection.java
83.33% <100%> (-1.52%)
:arrow_down:

...m/trivago/rta/rendering/TemplateConfiguration.java
85.71% <100%> (+1.09%)
:arrow_up:

...ava/com/trivago/rta/rendering/ReportGenerator.java
100% <100%> (ø)
:arrow_up:

...n/java/com/trivago/rta/CluecumberReportPlugin.java
77.14% <100%> (ø)

...ivago/rta/rendering/pages/pojos/ReportDetails.java
100% <100%> (ø)
:arrow_up:

...endering/pages/pojos/TagSummaryPageCollection.java
33.33% <33.33%> (ø)

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec2f647...c3a0f8a. Read the comment docs.


pkg/orchestrator(ticdc): add timeout before remove capture

What problem does this PR solve?

Issue Number: ref #9344
What is changed and how it works?

Wait CaptureSessionTTL/2 seconds before removing a capture from GlobalReactorState.

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`Fix a bug that could result in double writes after a CDC node disconnects from etcd.`.

/test all

/retest

/retest

/test all

/retest

/retest


Issue in integrating multiselect field into schema form

Enhancement
Adding a new input field into schema form
Expected behaviour
onDropdownHide should be triggered on close of dropdown
Actual behaviour
It actually ...onDropdownHide not getting triggered
Gist/Plunker/Demo
http://plnkr.co/edit/ZapAPvU2dwM0lM9Q5IDx?p=preview
@json-schema-form/angular-schema-form-lead

working plunker
http://plnkr.co/edit/ZapAPvU2dwM0lM9Q5IDx?p=preview

Ok, so is your goal here to build an add-on to use the external component Bootstrap Multiselect in ASF? Good stuff!
If so, first take a look on the angular-schema-form-add-ons repo, you should consider the naming of you project.
Then, this is a very complicated question that requires people to basically learn your project, and no offence, but that won't happen, so you need to be more specific.
That aside, I could not find that onDropdownHide is called anywhere by your add-on? And neither that it is presented to the multiselect anywhere?

Due to a month without response I am closing.
Please re-open if you do not feel the question has been answered sufficiently.


Docker image returning error

I tried provided docker image but it is returning error on execution.
import: unable to open X server ' @ error/import.c/ImportImageCommand/364.
import: unable to open X server ' @ error/import.c/ImportImageCommand/364. /usr/local/bin/slack-cleaner: line 7: from: command not found /usr/local/bin/slack-cleaner: slack-cleaner: line 10: syntax error near unexpected token ('
/usr/local/bin/slack-cleaner: slack-cleaner: line 10:    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])'

should be fixed with https://github.com/sgratzl/slack-cleaner/commit/8eb2db260b40b89a2ca2fd461c3ee2c1ac3eed4a. Please pull the image in a few minutes and try again.


Flash-crowd behavior

It's been observed in my cluster that the following scenario occurs:
I have a non-reduce pipeline with the degree of parallelism set to N.  An input commit comes in.  The input commit contains a number of large files, each of which contains more than N blocks.
Now, the way we assign inputs to jobs, the n-th job will get the n-th block to every file.  So the first job gets the first block to every file, the second job gets the second block to every file, etc.
Since each file contains more than N blocks, each job essentially sees the same files, i.e. all files.
What happens next is that, each job starts processing the same file, i.e. the first file in the input directory.  Since we shard traffic by file path, all these jobs start reading file from the same server.  So even though we'd ideally want traffic to spread across the cluster, we in fact get a flash-crowd behavior where all jobs talk to the same server.

Few clarifications here, we assign inputs to jobs just by hashing the name of the block. So I don't think there's any guarantee about the nth block going to the nth job. However this does mean that with large files we can expect each job to see each file. Having each job see a piece of each file is generally a good thing, but doing them all in the same order.
I think this issue ultimately comes down to a question of what order ListFiles returns it's FileInfos in. Right now there's no guarantees because it reads them out of a map and although golang maps aren't guaranteed to be in order they're also not guaranteed to be out of order. In fact they normally iterate in the same order. We should add a randomization step to ReduceFileInfos and I think this issue will go away.

@jdoliner actually, I found that ListFiles is already returning files in a random order.  It's just that my jobs, by using golang's ioutil.ReadDir, are implicitly sorting files by filename.  So I'm guessing this is a non-issue after all.  Our user just needs to be smart and process files in random order.
I guess the only thing we can do about this issue is to talk about it somewhere in our upcoming documents, so our users know how to avoid this flash-crowd behavior.

Yeah, not much we can do if the user is lexicographically sorting the filenames after the fact. Documenting is a great idea though.


Target button for popover loses focus when clicked away but doesn't close the pop over.

components: popovers
reactstrap version 8.9.0

What is happening?
When i visit "popover" component on https://reactstrap.github.io/components/popovers/
I observed a behaviour.

Click on Launch popover [first example]
Once the pop over is open, click off of the button. [to remove the focus from the button]
The button has lost its focus but the tooltip still remains open

What should be happening?

The tooltip should have closed when you click away from button.

Steps to reproduce issue

Click on Launch popover [first example]
Once the pop over is open, click off of the button. [to remove the focus from the button]
Now though the button has no focus, the tooltip remains open

@clisterdmello This is the intended behaviour of Popover.


Chore: Bump Kubernetes dependencies to 1.30.3

What this PR does / why we need it:
The current dependencies are very old.
Special notes for your reviewer:
Release note:

NONE

/gtm
/approve


Add Y-Offset for Island Templates

Describe your idea
Island generation can be offset on the X and Z axes already. The ability to offset templates by some Y-value would allow for islands with different template heights to have the same ground level.

For example, I've built these two islands for my pack:

They both have different total heights, but I want them to both generate with the ground level at y=63.

Your idea is a template specific y offset, right? So, a bit different compared to X/Z offset.

Yeah, template-specific y-offsets are what I meant.


Developer Authentication

Hi .. has developer authentication been removed by LinkedIn? I noticed today I had a number of failing calls with OAUTH errors and I went to check my developer keys and there is now no option to refresh them.
Has this been removed or is it now only available for partners?
If so might be good to add a note to the page documentation here or remove the developer authentication notes and endpoint.

I only have client ID and Client Secret ...

@pg1671 yeah it looks like it has been removed. linkedin.LinkedInAuthentication() will be the way to go now.


Keyboard Disabled is not working on fly..

Hi,
I have to implement the functionality in which i have to disable keyboard event on plyr.
I am setting below property false on fly but these changes are not reflecting on player.
this.player.config.keyboard.focused = false;
this.player.config.keyboard.global = false;
Although same property is working during first time when player is being instantiatiing:
like :
var player = new Plyr('.js-player', { controls, captions: { active: true }, keyboard: { focused: false, global:false, });
Can you please help me to sort out this issues. So that i can change keyboard enabled/disabled functionality on fly.
Thanks,
Nitin Kesarwani

anyone can help me on this?


Pymotif/tests

PR Type
Tests and bugfixes for pymotif
Detailed Description

Tests for pymotif can be run with pytest -v from the test folder, see README for more details
Some bugfixes:

CSV import now works with a file that just has source and target cols
Networkx import also works for a graph with only source and target cols
Neo4j import now works if there are no node labels specified in the db

Does this PR introduce breaking change?

No

You'll deploy the updated version to PyPI?

yes, along with other fixes and enhancements to Motif. I will sync it with the github releases i.e. every github release = npm release + pypi


Problem with dataset download

Hi,
I am trying to download the dataset, however, the instruction link is not working.
Thanks

Hi,
I just updated the link
Thank you

Thanks


DPG: ContinuationToken and maxPage size should be surfaced through Pageable

Current generated code:
public virtual Pageable(string testId, string continuationToken = null, RequestContext context = null);
public virtual Pageable (string orderby = null, string search = null, DateTimeOffset? lastModifiedStartTime = null, DateTimeOffset? lastModifiedEndTime = null, string continuationToken = null, int? maxpagesize = null, RequestContext context = null);
Based on the comments for archboard:  https://apiview.dev/Assemblies/Review/4200a804f382479bb4d2bb4a3323b8c7
We need to config it to be part of Pageable similarly in second one maxpagesize is part of method, we also wanted it to part of Pageable.
Source Swagger:   https://github.com/Azure/azure-rest-api-specs/blob/main/specification/loadtestservice/data-plane/Microsoft.LoadTestService/stable/2022-11-01/loadtestservice.json

It is not codegen issue. Codgen generate the correct code according to the swagger definition.
Need to update the swagger to surface those two paramters.

This is an issue with the code generation.
maxpagesize is a standard Azure query parameter as described at https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#query-options.  This should not be surfaced as a method parameter, but rather via Pageable<T>'s GetPages(pageSizeHint: 30) method at https://learn.microsoft.com/en-us/dotnet/api/azure.pageable-1.aspages?view=azure-dotnet.


chore: change 'dyn io::Read' and 'trim_left_matches' deprecated code

When compiling with rust 1.43, there are some warnings because of deprecated code. This PR only updates simple deprecations. There is try!() deprecation that I don't know how to update yet.
warning: use of deprecated item 'try': use the `?` operator instead
   --> src/main.rs:134:1
    |
134 | dyon_obj!{InputEvent { kind, code, value, device_idx }}
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `#[warn(deprecated)]` on by default
    = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated item 'try': use the `?` operator instead
   --> src/main.rs:136:1
    |
136 | / dyon_fn!{fn device_name(obj: RustObject) -> String {
137 | |     let mut guard = obj.lock().expect(".lock()");
138 | |     let dev = guard.downcast_mut::<Device>().expect(".downcast_mut()");
139 | |     let name = std::str::from_utf8(dev.name().to_bytes()).expect("from_utf8()").to_owned();
140 | |     name
141 | | }}
    | |__^
    |
    = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated item 'try': use the `?` operator instead
   --> src/main.rs:143:1
    |
143 | / dyon_fn!{fn next_events(arr: Vec<Variable>) -> Vec<InputEvent> {
144 | |     loop {
145 | |         let mut pfds = arr.iter().map(|var| PollFd::new(
146 | |                 with_unwrapped_device!(var, |dev : &mut Device| dev.fd()), EventFlags::POLLIN)).collect::<Vec<_>>();
...   |
158 | |     }
159 | | }}
    | |__^
    |
    = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated item 'try': use the `?` operator instead
   --> src/main.rs:161:1
    |
161 | / dyon_fn!{fn emit_event(obj: RustObject, evt_v: Variable) -> bool {
162 | |     let mut guard = obj.lock().expect(".lock()");
163 | |     let dev = guard.downcast_mut::<uinput::Device>().expect(".downcast_mut()");
164 | |     if let Variable::Object(evt) = evt_v {
...   |
182 | |     }
183 | | }}
    | |__^
    |
    = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated item 'try': use the `?` operator instead
   --> src/main.rs:161:1
    |
161 | / dyon_fn!{fn emit_event(obj: RustObject, evt_v: Variable) -> bool {
162 | |     let mut guard = obj.lock().expect(".lock()");
163 | |     let dev = guard.downcast_mut::<uinput::Device>().expect(".downcast_mut()");
164 | |     if let Variable::Object(evt) = evt_v {
...   |
182 | |     }
183 | | }}
    | |__^
    |
    = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

    Finished release [optimized] target(s) in 0.15s

There is try!() deprecation

Well they're coming from dyon's macros, so not our fault.


Load several json files

@bhowes-tt, I got the Edmonton project and managed to export the structure. However, the skin and the bowl are linked files in Revit. I have discussed two options with @nmundell-tt:
-A) Merge (copy+paste) the three models into one in Revit. This is tedious and will probably create a really heavy json file
-B) Allow the viewer to take more than one json file. This seems to be a really good way to collaborate with others, since json files will most likely come from different models (architecture, structure, etc).
I feel that option B is a better approach that we could really benefit from in future projects. What's your take on this? Thanks!

Let's wait for this one... We are trying to get this project out the door this week.
Nice idea though!

This has been brought up again by Hiram under a different problem. He is trying to view a Revit file of a section of a stadium that becomes a 60 MB json file that crashes Chrome.
Approaching this issue by telling the user, on the Revit side, that the file size is too big and asking them if they'd like to create separate json files per Revit category seems a good solution. Then, add the possibility to select several json files on the web interface and/or add new ones as needed, like they do in the three.js editor:

I'd like to take a stab at this in the next couple of weeks, since I did this for the custom website I'm currently working on. @bhowes-tt what do you think?


Help to understand sub-scene and modals

I'm trying to get Modal's and sub-routing to work correctly and although I "kind of" have it working, I don't think it's right.  Below I have the configuration I am using (actually) and what I (expected) it to be based on my understanding of the documentation.
Required work-flow
LOGIN -> HOME (wrapped within a drawer) -> POPUP (displayed vertically like an iOS modal from the bottom within the HOME scene)
As you can see from the below example, I can't get the POPUP to work when within the HOME Scene (like a sub-scene). It only works when it's outside the drawer.  This caused problems, since I cannot user Actions.Pop({ refresh: { someData: 1 } })  (Pop works but I don't get the props updating in the caller (parent) when I do Actions.popUp() from home.
What I Expected it to be
Note: Look at the key="popUp"
import { Scene, Actions, Modal } from 'react-native-router-flux';
...

<Provider store={store}>
   <Scene key="modal" component={Modal} >
      <Scene key="root">
         <Scene key="login" component={Login} title="LOGIN" />

         <Scene key="drawer" component={Drawer} open={false}>
            <Scene key="main" tabs={true} >
               <Scene key="home" component={Home} title="HOME" >
                  <Scene key="popUp" component={MyPopup} hideNavBar={false} title="MY POPUP" />
               </Scene>
            </Scene>
      </Scene>
   </Scene>
</Provider>

What I am Actually doing
Note: Look at the key="popUp"
import { Scene, Actions, Modal } from 'react-native-router-flux';
...

<Provider store={store}>
   <Scene key="modal" component={Modal} >
      <Scene key="root">
         <Scene key="login" component={Login} title="LOGIN" />
         <Scene key="popUp" component={MyPopup} hideNavBar={false} title="MY POPUP" direction="vertical" />

         <Scene key="drawer" component={Drawer} open={false}>
            <Scene key="main" tabs={true} >
               <Scene key="home" component={Home} title="HOME" ></Scene>
            </Scene>
      </Scene>
   </Scene>
</Provider>

Version

react-native-router-flux v3.36.0
react-native v0.35.0

Ok I've solved this myself.
It looks like a parent Scene cannot contain a component but instead house sub-scenes with components which makes sense


Add Management API and Pro tier

This PR adds a Management API, a public API for CRUDing organizations, setup URLs, SAML connections, and SCIM directories.
The Management API is gated behind a Stripe entitlement. With database access, one can bypass this by updating the entitled_management_api column on app_organizations.

^ This is me testing. Validation errors make Sentry upset, that's an internal triage issue.


Update the DevTest Labs FAQ about VM limits

@gxy001,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@gxy001 : Thanks for your contribution to the Azure documentation! The author, @tomarcher, has been notified to review your proposed change.

#sign-off

@TomArcher
Thanks for the review. I'm merging this pull request. At your convenience, in the private repository, please update the author value in the topic's metadata to your GitHub alias. Values are case sensitive. This will help automation to do the right thing when it encounters the content.


Can O' Spam: Watch themoviesz.com

Can O' Spam requests the watch of the watch_keyword themoviesz\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ

themoviesz\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


New Gmail UI in franz

It would be great if we can get the new Gmail UI in a small upgrade. It seems pretty cool It'd be great if we can have it.

Simply open the Gmail settings overlay from the gear icon at the upper right of the Gmail service and select "Try the new Gmail".


dotnet test does not use the correct .NET Framework runtime - report false test failures

From @TalAloni on Saturday, March 21, 2020 4:16:42 PM
I have created a minimal xUnit test project demonstrating the problem (the test project use the SDK-style csproj, and target net472).
VSTest.Console works as expected.
when running the test with dotnet test, it will throw the following exception:
System.ArgumentException : The specified value is not valid in the 'SslProtocolType' enumeration.
This exception is not thrown by .NET Framework 4.7.2
dotnet SDK version: 3.1.200
Test Execution Command Line Tool Version 16.5.0
Project demonstrating the problem:
https://github.com/TalAloni/dotnettest-xunit
Copied from original issue: dotnet/sdk#10956

From @TalAloni on Sunday, March 22, 2020 7:36:14 PM
Update: This problem does not reproduce with MS Test v2, seems to be limited to xUnit

Thanks, I've already opened issue #2376

duplicate of the bug mentioned ^^^


Add ChatAction constants for Easier Access

Hi! I think it's good idea to add ChatAction constants like models.ParseModeHTML.
https://core.telegram.org/bots/api#sendchataction
const (
	ChatActionTyping          = "typing"
	ChatActionUploadPhoto     = "upload_photo"
	ChatActionRecordVideo     = "record_video"
	ChatActionUploadVideo     = "upload_video"
	ChatActionRecordVoice     = "record_voice"
	ChatActionUploadVoice     = "upload_voice"
	ChatActionUploadDocument  = "upload_document"
	ChatActionChooseSticker   = "choose_sticker"
	ChatActionFindLocation    = "find_location"
	ChatActionRecordVideoNote = "record_video_note"
	ChatActionUploadVideoNote = "upload_video_note"
)

Released v0.7.10, thanks!


Define environment variables for running pypi_update.yml workflow

In the Settings -> Environments -> New environment, create an environment named pypi and create 2 environment secrets named:

PYPI_USERNAME
PYPI_PASSWORD

The values for these secrets are your PyPi credentials that will be used to automatically publish new releases using #2.

ok


Vulnerability roundup 85: postgresql-9.6.17: 2 advisories [8.8]

search, files

[ ] CVE-2018-1058 CVSSv3=8.8 (nixos-20.03)
[ ] CVE-2019-9193 CVSSv3=7.2 (nixos-20.03)

Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.
Cc @danbst
Cc @globin
Cc @ocharles
Cc @thoughtpolice

See also: #88383

It's at 9.6.19
Closing.


Property naming strategy for Jackson integration does not work

Description

I am trying to deserialize json with snake case json properties to entity views with lower camel case properties. I have tried to add the strategy to both the jackson object mapper builder and the entity view aware object mapper without success. It works for regular classes and interfaces but not entity views. Am I missing something here or is this a bug?
Expected behavior

Properties like "created_at" should deserialize to "createdAt".
Actual behavior

Properties does not get set and end up being null.
Steps to reproduce

    @Bean
    fun jsonCustomizer(): Jackson2ObjectMapperBuilderCustomizer =
        Jackson2ObjectMapperBuilderCustomizer { it
            .serializers(LifeCycleStatusSerializer())
            .propertyNamingStrategy(PropertyNamingStrategies.SNAKE_CASE)
        }

    @Bean
    fun evaObjectMapper(evm: EntityViewManager, mapper: ObjectMapper): EntityViewAwareObjectMapper {
        mapper.propertyNamingStrategy = PropertyNamingStrategies.SNAKE_CASE
        return EntityViewAwareObjectMapper(evm, mapper)
    }

Environment

Version: 1.6.11
JPA-Provider: Spring Data JPA
DBMS: MySQL
Application Server: Spring Boot

This should work. Blaze-Persistence delegates the serialization process to Jackson after it created the object. Can you please share the exception that you're getting and an example?

The serialization part works, but "de"-serialization does not. I don't get an error, the properties just deserializes to null.
This also goes when adding custom to the object mapper builder. If I do something like this, the serializers works but the overridden function for deserializers is never called.
@Bean
fun jsonCustomizer(): Jackson2ObjectMapperBuilderCustomizer =
    Jackson2ObjectMapperBuilderCustomizer { it
        .serializers(LifeCycleStatusSerializer())
        .deserializers(LifeCycleStatusDeserializer())
        .propertyNamingStrategy(PropertyNamingStrategies.SNAKE_CASE)
    }

internal class LifeCycleStatusSerializer : StdSerializer<LifeCycleStatus>(LifeCycleStatus::class.java) {
    override fun serialize(status: LifeCycleStatus, generator: JsonGenerator, provider: SerializerProvider) {
        generator.writeNumber(status.value)
    }
}

internal class LifeCycleStatusDeserializer : StdDeserializer<LifeCycleStatus>(LifeCycleStatus::class.java) {
    override fun deserialize(jsonParser: JsonParser, context: DeserializationContext): LifeCycleStatus {
        val node: JsonNode = jsonParser.codec.readTree(jsonParser)
        return LifeCycleStatus.valueOf(node["life_cycle_status_id"].asInt())
    }
}

Ok, let me correct this

Blaze-Persistence delegates the serialization and deserialization process to Jackson after it created the object.

Can you maybe provide a reproducer for this in this test class? https://github.com/Blazebit/blaze-persistence/blob/main/integration/jackson/src/test/java/com/blazebit/persistence/integration/jackson/EntityViewAwareObjectMapperTest.java


Fixed Bing TTS link

Thanks Drout :slightly_smiling_face:
You've also been added to our list of excellent humans!


📖 :book: icon in Bitbucket

Hello! Seems to be the 📖 :book: icon don't render in Bitbucket:

I wonder If I can replace it somehow?

Sure, its probably in a template somewhere 👍🏻

Seems to be it's Bitbucket problem. Couldn't find easy solution for change that icon.
So, let it be 😔

I'll leave it open because it is a real bug and someone is welcome to fix it 👍🏻

Looks https://github.com/danger/danger/pull/1326 solved this issue.
Let me close this issue and feel free to reopen this one if you have any trouble.


[engsys] Global Sanitizers inconsistently sanitize storage account names, recordings unreplayable

Describe the bug
https://github.com/Azure/azure-sdk-for-python/pull/35196 introduced a collection of "global" sanitizers that scrub secrets from recordings as they are written to disk.
I'm currently writing a test, where the code path involves:

Fetching details about a storage account

Usage those details to build the uri for the next request

This sanitizer will redact the storage account name in the recording from the response in Step 1.
https://github.com/Azure/azure-sdk-for-python/blob/511aef315bf6919f52c90adb1803a3b9079cbb05/tools/azure-sdk-tools/devtools_testutils/proxy_startup.py#L379
There is no "global" sanitizer that sanitizes storage account names from request urls.
This leaves my recording un-replayable.
In recording mode, the code receives the sanitized request and tries to send a subsequent request to a URL it builds with the sanitized values: https://sanitized.blob.core.windows.net. But the recording stored an unsanitized URL for that subsequent request, https://account-name.blob.core.windows.net, so the proxy is unable to find a match.
To Reproduce
Steps to reproduce the behavior:

Succesfully record a test in live mode that:

Fetches some response with details about a storage account

// Example response
{
        "id": "/subscriptions/00000000-0000-0000-0000-000000000/resourceGroups/00000/providers/Microsoft.MachineLearningServices/workspaces/00000/datastores/workspaceblobstore",
        "name": "workspaceblobstore",
        "type": "Microsoft.MachineLearningServices/workspaces/datastores",
        "properties": {
          ...,
          "subscriptionId": "00000000-0000-0000-0000-000000000",
          "resourceGroup": "resource-group",
          "datastoreType": "AzureBlob",
          "accountName": "account-name",
          "containerName": "d49eda6a-ab96-4d00-b108-33768a3d0aee-azureml-blobstore",
          "endpoint": "core.windows.net",
          "protocol": "https",
          "serviceDataAccessAuthIdentity": "WorkspaceSystemAssignedIdentity"
        },
        "systemData": {
            ...
        }

}

Uses that response to build the URL for a subsequent request

https://account-name.blob.core.windows.net/d49eda6a-ab96-4d00-b108-33768a3d0aee-azureml-blobstore/path/to/files

Attempt to re-run the test in recording mode

Expected behavior
The test should run off the recording, and pass
Actual behavior
The test fails
ERROR    root:proxy_fixtures.py:312

-----Test proxy playback error:-----

Unable to find a record for the request PUT https://sanitized.blob.core.windows.net/d49eda6a-ab96-4d00-b108-33768a3d0aee-azureml-blobstore/LocalUpload/0e7abff4dcb2ddd489d3e72fa2039bf6/README.md?sv=2021-10-04&si=azureml-system-datastore-policy&sr=c&sig=Sanitized
Method doesn't match, request <PUT> record <HEAD>
Uri doesn't match:
    request <https://sanitized.blob.core.windows.net/d49eda6a-ab96-4d00-b108-33768a3d0aee-azureml-blobstore/LocalUpload/0e7abff4dcb2ddd489d3e72fa2039bf6/README.md?sv=2021-10-04&si=azureml-system-datastore-policy&sr=c&sig=Sanitized>
    record  <https://account-name.blob.core.windows.net/d49eda6a-ab96-4d00-b108-33768a3d0aee-azureml-blobstore/LocalUpload/0e7abff4dcb2ddd489d3e72fa2039bf6/README.md?sv=2021-10-04&si=azureml-system-datastore-policy&sr=c&sig=Sanitized>

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @kdestin, I have good news: Paul merged an update to our tooling that adds the ability to remove sanitizers (https://github.com/Azure/azure-sdk-for-python/pull/35385), so there should now be a better solution than your current workaround.
Some sanitizers were already disabled for ML as part of the update: https://github.com/Azure/azure-sdk-for-python/blob/a61a8e2a934c75648a974b458a67e954436b8011/sdk/ml/azure-ai-ml/tests/conftest.py#L134-L138
If you do the same with the accountName body key sanitizer, you should be able to remove the additional sanitizer you added as a workaround. The ID for the central sanitizer is "AZSDK3478"; here's where it's registered by the test proxy.

Awesome, thank you so much. I'll close this issue


 Also fixed a couple toilet paper tubes by the bucket that were floating.
SFCP_Issue_520.zip


ionic emulate ios -lc

I cant do the Live paramter. Any advice? I need to debug it.

You can use the following guides to see how to debug on real devices:
Remote Debugging on Android with Chrome
https://developer.chrome.com/devtools/docs/remote-debugging
Remote Debugging on iOS with Safari
http://www.jasenlew.com/2014/07/28/web-inspect-an-ionic-app-on-your-iphone-ios-6/


Add config for easier command line usage

You can now run:
code_sync --register <project> # prompts for configuration and saves to config file
code_sync <project>
code_sync --list # lists registered projects
You can also still run code_sync the old way, specifying the local_dir, remote_dir, etc manually.

Hi @togop- Would you like to respond to my replies to your comments, or should I go ahead and merge this as is?


Failure my XFP not involved

I'm new to Sparrow (previously using Electrum to facilitate airgapped coldcard signing). I rarely do any transactions in BTC and my background is in wellness (not computers) so I thank you in advance for your patience and assistance.
I need to move my keys (on MK3) to an MK4 with a new seed.
I tried sending from Coldcard MK3 to my MK4 using Sparrow airgapped.
I clicked on "save transaction" button in sparrow -- and saved to the MicroSD
When clicked "ready to sign" on MK4, I get error:
Failure My XFP not involved
Other info:
Single Sig wallet
MK4 Script type and MK3 script type = native segwit (P2WPKH)
MK4 Version 5.40
Number of inputs/outputs: I believe it's just 1 input and 1 output
I do not have a passphrase (25th seed word) on my coldcard
I followed your instructions in closed post #1087 to create a new wallet in Sparrow and reimport the Coldcard via the Generic JSON export as described in the documentation.
The same error occurred.
Any suggestions?

Got it to work with a third "reimport".


Debug/Run with terminal integratedTerminal not working anymore

Today I just stumbled across python debugging/running when using "integratedTerminal" is not working anymore. As far as I remind, last week it worked without an an issue. I alos upgrade to most recent version today now but the problem still exists
Environment data

VS Code version: 1.39.2
Extension version (available under the Extensions sidebar): 2019.10.44104
OS and version: Linux x64 4.14.11-amd64
Python version (& distribution if applicable, e.g. Anaconda): Devuan/Debian 2.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): N/A

Expected behaviour
Python script is started and executes
Actual behaviour
I can see the "Python Debug Console" flash up show some printouts and immediately closes. The debug bar at top of screen vanishes after some seconds and error popup "error launching..." is displayed.
Steps to reproduce:

Press [F5] or [CTRL]+ [F5]

Logs
N/A
Files
launch.json (not working)
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Python: Run testcase file",
      "type": "python",
      "request": "launch",
      "program": "${file}",
      "console": "integratedTerminal",
      "env" : {
        "PYTHONPATH" : "${workspaceFolder}"
      }
    }
  ]
}

launch.json (working)
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Python: Run testcase file",
      "type": "python",
      "request": "launch",
      "program": "${file}",
      "console": "internalConsole",
      "env" : {
        "PYTHONPATH" : "${workspaceFolder}"
      }
    }
  ]
}

settings.json
{
    "workbench.colorTheme": "Solarized Light",
    "telemetry.enableCrashReporter": false,
    "telemetry.enableTelemetry": false,
    "editor.renderWhitespace": "all",
    "files.trimTrailingWhitespace": true,
    "window.zoomLevel": 1,

    "terminal.integrated.shell.linux": "/usr/bin/env",
    "terminal.integrated.shellArgs.linux": [
        "LANG=de_DE@utf-8",
        "/bin/bash"
    ],
}

@amesser Do you see any error in the terminal? Or in the output panel for Python.

Unfortunately not. In error case, I see VS code console switches for a very short time to "Python Debug Console" but immediately closes it again. The console seems to be filled with some output which looks like environment variable assignments, but I'm not fully sure. There is neither an error output in a terminal from which I started VS code nor in the other console windows in VS code.
Can I set something in VS code which makes it to not close the console or to produce more debug output to stdout/stderr? It looks to me that VS code always forks to background when starting from a terminal?

@amesser Can you share the output of this panel? You may have to scroll all the way to the top to see this:

Will do later. (Have no access to the machine at the moment)

@karthiknadig Here we go
Output/Python
> conda --version
> pyenv root
> python3.7 -c "import sys;print(sys.executable)"
> python3.6 -c "import sys;print(sys.executable)"
> python3 -c "import sys;print(sys.executable)"
> python2 -c "import sys;print(sys.executable)"
> python -c "import sys;print(sys.executable)"
> /usr/bin/python -c "import sys;print(sys.executable)"
> conda info --json
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2.7 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2.7 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3.5 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3.5 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2.7 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2.7 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3.5 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3.5 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python2 ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles/interpreterInfo.py
Starting Jedi Python language engine.
> /usr/bin/python -m pylint --disable=all --enable=F,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,unused-wildcard-import,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode,E0001,E0011,E0012,E0100,E0101,E0102,E0103,E0104,E0105,E0107,E0108,E0110,E0111,E0112,E0113,E0114,E0115,E0116,E0117,E0118,E0202,E0203,E0211,E0213,E0236,E0237,E0238,E0239,E0240,E0241,E0301,E0302,E0303,E0401,E0402,E0601,E0602,E0603,E0604,E0611,E0632,E0633,E0701,E0702,E0703,E0704,E0710,E0711,E0712,E1003,E1101,E1102,E1111,E1120,E1121,E1123,E1124,E1125,E1126,E1127,E1128,E1129,E1130,E1131,E1132,E1133,E1134,E1135,E1136,E1137,E1138,E1139,E1200,E1201,E1205,E1206,E1300,E1301,E1302,E1303,E1304,E1305,E1306,E1310,E1700,E1701 --msg-template='{line},{column},{category},{symbol}:{msg}' --reports=n --output-format=text "~/Arbeit/Shared/Profinet Tests/Shared/DataExchange.py"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -m pylint --disable=all --enable=F,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,unused-wildcard-import,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode,E0001,E0011,E0012,E0100,E0101,E0102,E0103,E0104,E0105,E0107,E0108,E0110,E0111,E0112,E0113,E0114,E0115,E0116,E0117,E0118,E0202,E0203,E0211,E0213,E0236,E0237,E0238,E0239,E0240,E0241,E0301,E0302,E0303,E0401,E0402,E0601,E0602,E0603,E0604,E0611,E0632,E0633,E0701,E0702,E0703,E0704,E0710,E0711,E0712,E1003,E1101,E1102,E1111,E1120,E1121,E1123,E1124,E1125,E1126,E1127,E1128,E1129,E1130,E1131,E1132,E1133,E1134,E1135,E1136,E1137,E1138,E1139,E1200,E1201,E1205,E1206,E1300,E1301,E1302,E1303,E1304,E1305,E1306,E1310,E1700,E1701 --msg-template='{line},{column},{category},{symbol}:{msg}' --reports=n --output-format=text "~/Arbeit/Shared/Profinet Tests/Shared/DataExchange.py"
cwd: ~/Arbeit/Shared/Profinet Tests
> conda info --json
> conda --version
> /usr/bin/python -c "import pylint"
> /usr/bin/python -c "import pylint"
> /usr/bin/python -c "import pylint"
> /usr/bin/python -c "import pylint"

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
> /usr/bin/python -c "import sys;print(sys.prefix)"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -c "import sys;print(sys.prefix)"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -c "import sys;print(sys.executable)"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -c "import sys;print(sys.executable)"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())"
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -m site --user-site
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python -m site --user-site
cwd: ~/Arbeit/Shared/Profinet Tests
> /usr/bin/python completion.py
cwd: ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles
> /usr/bin/python completion.py
cwd: ~/.vscode/extensions/ms-python.python-2019.10.44104/pythonFiles

and Output/Log(Window), seems to be more promising:
[2019-11-06 20:57:50.496] [renderer1] [error] Error: [File Watcher (chokidar)] Inotify limit reached (ENOSPC)
[2019-11-06 20:57:50.504] [renderer1] [error] [File Watcher (chokidar)] Inotify limit reached (ENOSPC)
[2019-11-06 20:58:04.889] [renderer1] [error] File not found (/USB/TCP): Error: File not found (/USB/TCP)
    at v.resolve (file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1535:605)
[2019-11-06 20:58:32.944] [renderer1] [error] ioctl(2) failed, EBADF: Error: ioctl(2) failed, EBADF
    at UnixTerminal.resize (/usr/share/code/resources/app/node_modules.asar/node-pty/lib/unixTerminal.js:227:13)
    at S.resize (file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:2888:940)
    at w.setDimensions (file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4077:437)
    at _processManager.ptyProcessReady.then (file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4103:111)

Later log let me think it might be a more general problem and not related to vs python?

@amesser  Looks like this is https://github.com/microsoft/node-pty/issues/220


Find a better pattern for implementing control and target keywords and us for control gates.

Currently CXPowGate has a special override of on which allows one to pass in control and target when turning into a GateOperation.  It seems like we never followed up to do this for any other gates, and if we are going to do this we shouldn't do it in a one off manner.

At the very least the code can be simplified to def on(self, target, control) instead of the args/kwargs stuff that's there.
I'm fine with deprecating it.

discussed at Cirq Cync: vote was to keep it, but to do it in a way that is not adding this code to every gate.

Discussion from cirq cync: cut this.


[BEAM-7783] BeamIOSourceRel using custom BeamStatistics

These are some remaining changes from BEAM-7783. BeamSourceIORel was supposed to return the rate instead of row count if the table is unbounded. I have also added test to guard that for the future.

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

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @akedin

Run JavaPortabilityApi PreCommit

Run JavaPortabilityApi PreCommit

Run Java Postcommit


python3Packages: get rid of uses of nose

nose is abandoned upstream and has caused us untold headaches recently (admittedly mostly unrelated to the code itself). We’ve stopped the bleeding by getting https://github.com/NixOS/nixpkgs/pull/325968 into staging thanks to the incredible work of @jchv, but it’s still broken on master and we ought to do some tidying up so we’re not dragging this around forever and perhaps even to unblock some stuff on master while the staging cycle progresses. Many packages don’t actually need nose any more, despite us including it in our dependency lists. Active upstreams should have already moved to pytest or something else. Some packages will have patches available; if we’re really feeling generous we could send patches to upstream ourselves. Others may be completely unmaintained packages that we could think about dropping.
Please make sure to migrate packages to pyproject = true; when working on them. Additionally, if the upstream is unmaintained, there are no significant reverse dependencies in‐tree or on Wheelodex, and it requires patching or there is no particular reason to imagine we’d want to keep it, consider just dropping the package. For the same reasons we want to get rid of nose, we should take this as an opportunity to reduce future maintenance burden and drop broken, unused, or long‐obsolete packages.
@dotlambda has already done some great work on this – see https://github.com/NixOS/nixpkgs/pull/325847, https://github.com/NixOS/nixpkgs/pull/325872, https://github.com/NixOS/nixpkgs/pull/325885, and https://github.com/NixOS/nixpkgs/pull/326164 – but I thought it’d be good to have a master list of all affected packages so we can tackle it collectively. If you open a PR for one of these, please edit this issue to link it beside the relevant package(s).

[x] adafruit-nrfutil https://github.com/NixOS/nixpkgs/pull/327199
[x] aws-google-auth https://github.com/NixOS/nixpkgs/pull/331352
[ ] caffe
[x] cmake-lint https://github.com/NixOS/nixpkgs/pull/327220
[x] docker-compose_1 https://github.com/NixOS/nixpkgs/pull/330907
[x] gixy https://github.com/NixOS/nixpkgs/pull/330741
[x] grin https://github.com/NixOS/nixpkgs/pull/330741
[ ] hydrus
[x] ledger-autosync https://github.com/NixOS/nixpkgs/pull/334202
[x] mackup https://github.com/NixOS/nixpkgs/pull/327240
[ ] mbutil
[ ] onboard
[x] openlp https://github.com/NixOS/nixpkgs/pull/330855
[x] python3Packages.actdiag https://github.com/NixOS/nixpkgs/pull/330396
[x] python3Packages.androguard https://github.com/NixOS/nixpkgs/pull/330535
[ ] python3Packages.apricot-select
[x] python3Packages.beaker https://github.com/NixOS/nixpkgs/pull/327530
[x] python3Packages.biopandas https://github.com/NixOS/nixpkgs/pull/330740
[ ] python3Packages.blessings
[x] python3Packages.blockdiag https://github.com/NixOS/nixpkgs/pull/330396
[ ] python3Packages.boto
[x] python3Packages.braintree https://github.com/NixOS/nixpkgs/pull/330290
[x] python3Packages.bx-python https://github.com/NixOS/nixpkgs/pull/330744
[x] python3Packages.cassandra-driver https://github.com/NixOS/nixpkgs/pull/330760
[x] python3Packages.cgroup-utils https://github.com/NixOS/nixpkgs/pull/330287
[x] python3Packages.changefinder https://github.com/NixOS/nixpkgs/pull/330311
[x] python3Packages.chart-studio https://github.com/NixOS/nixpkgs/pull/330248
[x] python3Packages.citeproc-py https://github.com/NixOS/nixpkgs/pull/330237
[ ] python3Packages.clickhouse-driver https://github.com/NixOS/nixpkgs/pull/330959
[ ] python3Packages.clustershell
[x] python3Packages.deform https://github.com/NixOS/nixpkgs/pull/328917
[ ] python3Packages.django-crontab
[ ] python3Packages.dm-control
[x] python3Packages.dodgy https://github.com/NixOS/nixpkgs/pull/330761
[x] python3Packages.envs https://github.com/NixOS/nixpkgs/pull/330762
[x] python3Packages.expiringdict https://github.com/NixOS/nixpkgs/pull/326665
[x] python3Packages.flask-restful https://github.com/NixOS/nixpkgs/pull/330876
[x] python3Packages.gocardless-pro https://github.com/NixOS/nixpkgs/pull/326766
[x] python3Packages.habanero https://github.com/NixOS/nixpkgs/pull/330768
[ ] python3Packages.hkdf https://github.com/NixOS/nixpkgs/pull/330769
[x] python3Packages.http-ece https://github.com/NixOS/nixpkgs/pull/330771
[ ] python3Packages.inotify https://github.com/NixOS/nixpkgs/pull/330776
[x] python3Packages.isbnlib https://github.com/NixOS/nixpkgs/pull/330773
[x] python3Packages.jsonable https://github.com/NixOS/nixpkgs/pull/330777
[ ] python3Packages.jupyter-contrib-nbextensions
[x] python3Packages.libgpuarray https://github.com/NixOS/nixpkgs/pull/331841
[x] python3Packages.locationsharinglib https://github.com/NixOS/nixpkgs/pull/330786
[ ] python3Packages.lockfile
[ ] python3Packages.mhcflurry
[x] python3Packages.mkl-service https://github.com/NixOS/nixpkgs/pull/324729
[x] python3Packages.mohawk https://github.com/NixOS/nixpkgs/pull/331838
[ ] python3Packages.mongoengine
[x] python3Packages.mwtypes https://github.com/NixOS/nixpkgs/pull/330805
[x] python3Packages.mwxml https://github.com/NixOS/nixpkgs/pull/330805
[ ] python3Packages.mygpoclient
[ ] python3Packages.nbmerge
[x] python3Packages.neo https://github.com/NixOS/nixpkgs/pull/330882
[x] python3Packages.nose-pattern-exclude https://github.com/NixOS/nixpkgs/pull/330439
[x] python3Packages.nose-timer https://github.com/NixOS/nixpkgs/pull/330535
[x] python3Packages.nose-warnings-filters https://github.com/NixOS/nixpkgs/pull/330439
[x] python3Packages.nose-xunitmp https://github.com/NixOS/nixpkgs/pull/330869
[x] python3Packages.nwdiag https://github.com/NixOS/nixpkgs/pull/330396
[x] python3Packages.ofxhome https://github.com/NixOS/nixpkgs/pull/327239
[x] python3Packages.ofxtools https://github.com/NixOS/nixpkgs/pull/330866
[x] python3Packages.para https://github.com/NixOS/nixpkgs/pull/330229
[ ] python3Packages.paramz https://github.com/NixOS/nixpkgs/pull/330865
[x] python3Packages.pastescript https://github.com/NixOS/nixpkgs/pull/327246
[x] python3Packages.paver https://github.com/NixOS/nixpkgs/pull/330858
[ ] python3Packages.pid https://github.com/NixOS/nixpkgs/pull/327372
[x] python3Packages.pkutils https://github.com/NixOS/nixpkgs/pull/330741
[x] python3Packages.pprintpp https://github.com/NixOS/nixpkgs/pull/330705
[x] python3Packages.preggy https://github.com/NixOS/nixpkgs/pull/329978
[ ] python3Packages.premailer https://github.com/NixOS/nixpkgs/pull/330702
[x] python3Packages.prison https://github.com/NixOS/nixpkgs/pull/330700
[x] python3Packages.prox-tv https://github.com/NixOS/nixpkgs/pull/330699
[x] python3Packages.ptable https://github.com/NixOS/nixpkgs/pull/330696
[x] python3Packages.pycdio https://github.com/NixOS/nixpkgs/pull/330695
[x] python3Packages.pycontracts https://github.com/NixOS/nixpkgs/pull/330791
[ ] python3Packages.pydy
[x] python3Packages.pyexcel-ods https://github.com/NixOS/nixpkgs/pull/330758
[x] python3Packages.pyexcel-xls https://github.com/NixOS/nixpkgs/pull/330758
[x] python3Packages.pygatt https://github.com/NixOS/nixpkgs/pull/332660 https://github.com/NixOS/nixpkgs/pull/330688
[ ] python3Packages.pygeoip https://github.com/NixOS/nixpkgs/pull/330509
[x] python3Packages.pygogo https://github.com/NixOS/nixpkgs/pull/329989
[x] python3Packages.pygtfs https://github.com/NixOS/nixpkgs/pull/330504
[x] python3Packages.pylacrosse https://github.com/NixOS/nixpkgs/pull/330500
[x] python3Packages.pypass https://github.com/NixOS/nixpkgs/pull/330222
[x] python3Packages.pypillowfight https://github.com/NixOS/nixpkgs/pull/327214
[x] python3Packages.pyquaternion https://github.com/NixOS/nixpkgs/pull/330459
[x] python3Packages.pyrfc3339 https://github.com/NixOS/nixpkgs/pull/330496
[x] python3Packages.pysrt https://github.com/NixOS/nixpkgs/pull/330441
[x] python3Packages.pytest https://github.com/NixOS/nixpkgs/pull/326541
[x] python3Packages.python-etcd https://github.com/NixOS/nixpkgs/pull/330438
[x] python3Packages.python-fedora https://github.com/NixOS/nixpkgs/pull/327169
[x] python3Packages.python-hglib https://github.com/NixOS/nixpkgs/pull/330739
[x] python3Packages.python-mapnik https://github.com/NixOS/nixpkgs/pull/330432
[x] python3Packages.pytimeparse https://github.com/NixOS/nixpkgs/pull/330421
[x] python3Packages.pyutilib https://github.com/NixOS/nixpkgs/pull/330759
[x] python3Packages.rauth https://github.com/NixOS/nixpkgs/pull/330417
[ ] python3Packages.rx
[x] python3Packages.safe https://github.com/NixOS/nixpkgs/pull/330404
[x] python3Packages.sampledata https://github.com/NixOS/nixpkgs/pull/330029
[ ] python3Packages.scales
[ ] python3Packages.scikit-fuzzy https://github.com/NixOS/nixpkgs/pull/330854
[x] python3Packages.selectors2 https://github.com/NixOS/nixpkgs/pull/330024
[x] python3Packages.seqdiag https://github.com/NixOS/nixpkgs/pull/330396
[ ] python3Packages.shap
[x] python3Packages.simplebayes https://github.com/NixOS/nixpkgs/pull/330018
[x] python3Packages.spark-parser https://github.com/NixOS/nixpkgs/pull/330001
[x] python3Packages.sphinx-rtd-dark-mode https://github.com/NixOS/nixpkgs/pull/330383
[x] python3Packages.sqlalchemy-mixins https://github.com/NixOS/nixpkgs/pull/330493
[ ] python3Packages.stytra
[x] python3Packages.sure https://github.com/NixOS/nixpkgs/pull/330012
[x] python3Packages.svgutils https://github.com/NixOS/nixpkgs/pull/330381
[x] python3Packages.telfhash https://github.com/NixOS/nixpkgs/pull/330005
[x] python3Packages.tempita https://github.com/NixOS/nixpkgs/pull/330855
[x] python3Packages.tissue https://github.com/NixOS/nixpkgs/pull/330376
[x] python3Packages.traittypes https://github.com/NixOS/nixpkgs/pull/330236
[ ] python3Packages.trfl https://github.com/NixOS/nixpkgs/pull/329976
[ ] python3Packages.uncompyle6
[x] python3Packages.unicode-slugify https://github.com/NixOS/nixpkgs/pull/329998
[ ] python3Packages.uvcclient
[x] python3Packages.vxi11 https://github.com/NixOS/nixpkgs/pull/329994
[ ] python3Packages.webassets
[x] python3Packages.webhelpers https://github.com/NixOS/nixpkgs/pull/330399
[x] python3Packages.weboob https://github.com/NixOS/nixpkgs/pull/330436
[ ] python3Packages.wsme
[x] python3Packages.xlwt https://github.com/NixOS/nixpkgs/pull/330217
[x] python3Packages.yanc https://github.com/NixOS/nixpkgs/pull/329978
[x] python3Packages.yarg https://github.com/NixOS/nixpkgs/pull/327170
[ ] sasview
[x] svtplay-dl https://github.com/NixOS/nixpkgs/pull/330741
[ ] tarsnapper
[x] zk-shell https://github.com/NixOS/nixpkgs/pull/333725

This was generated from staging commit 83881cb6e9b660cbca5241380c031ab2b69d6e1e with the following awful fish one‐liner: for pkg in (rg -l '\bnose3?\b' | rg -v '/(nose[23]?|cufflinks|enocean|jaconv|annoy|hdmedians|flaky|pycron|snapshottest|ssh-mitm|colour|influxdb)/|(python|cran)-(packages|aliases)\.nix' | sed 's|.*/\([^/]*\)/\([^/]*\)$|\1|'); rg "/$pkg"'[ \n{]' pkgs/top-level/python-packages.nix | awk '{print "python3Packages." $1}'; test $pipestatus[1] = 0 || rg "/$pkg"'[ \n{]' pkgs/top-level/all-packages.nix | awk '{print $1}'; test $pipestatus[1] = 0 || echo "$pkg"; end | sort -u | sed 's/^/* [ ] `/; s/$/`/'; feel free to edit to update the list.

python3Packages.biopandas has dropped pynose in v0.5.1.dev1 (not yet released). We should be able to check that off once the next version releases.

Hi, "paperwork" package  also depend on nose and raise error actually.

Seems like paperwork depends on pypillowfight, which has a build error due to nose not being supported. I'm investigating now!

ledger-autosync can stay broken for now, per https://github.com/egh/ledger-autosync/issues/143, upstream is working on getting a new release out, which should include all fixes for distutils, nose -> pytest, etc. I could also just update to the latest commit in the meantime if that's what's wanted.

sasview, while listed here, does not depend on nose.

@pyrox0 sasview has an xhtml2pdf.nix besides the default.nix which depends on nose.

I am not a package maintainer of any of the mentioned packages, may I still help?

@Sigmanificient yes you may! feel free to submit a PR for any listed package ^^

Yep, anyone can submit a PR for any package, as long as it follows guidelines; maintainership != exclusive ownership.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/error-nose-1-3-7-not-supported-for-interpreter-python3-12/48703/40

We should probably mark the packages we have discovered that still use nose so that we don't have to repeat each other's homework.

As in, the packages that would need patching to drop the dependency? Seems like a good idea; if anyone without permissions to edit the original post lists such packages here I’ll add a note to the list and hide the comment to avoid noise.

What should be done for trfl? It is marked as broken

Drop it? It hasn't seen activity in the 2 years since it was init'ed...

Drop it? It hasn't seen activity in the 2 years since it was init'ed...

Oh this is reassuring, I was about to do a drop pr, abut I noticed that it was marked as broken only 2 month ago.

styra was marked as broken 8 months ago: https://github.com/NixOS/nixpkgs/commits/master/pkgs/development/python-modules/stytra/default.nix

pyrfc3339 needs patching to drop nose. Last commit was 5 years ago. Python 3.2+ appears to have support for this natively (see here). Should we drop it?

Yes, let’s drop it. In general, anything that’s giving us trouble during the 3.12 migration and clearly has no maintenance is most likely going to cause us more trouble in future; the same reasons we want to get rid of nose apply to most of the packages that will make getting rid of nose a pain.
Of course, there are some packages that may be too popular or too irreplaceable for dropping them to be easy to stomach, but I do think that in the cases where upstream actually does depend on nose and doesn’t seem actively maintained enough for a PR to be worthwhile, we should lean towards just dropping the package by default. Those packages are going to fall out of the active Python ecosystem anyway because you won’t be able to use them on the latest Python version with the standard package managers; in the absence of a compelling reason to make an exception, it doesn’t do much good for us to keep them on life support only for users of Nixpkgs.
It’s easy to re‐add a removed package if people complain or if something that requires it gets added to Nixpkgs, but hard for us to actively keep broken packages working. We should think of this as an opportunity to tend our garden rather than just doing a bunch of labour for dead upstreams and no real benefit. As far as making the judgement call goes, in‐tree reverse dependencies are an obvious metric to use for libraries, but I also found a site called Wheelodex that indexes reverse dependencies for PyPI projects. That can help inform the judgement calls about whether to patch or drop.

Do you know an easy way to build an in-tree reverse dependency list for a given package?

Do you know an easy way to build an in-tree reverse dependency list for a given package? (As in the full tree, not just one level up)

No, I’ve just been grepping for immediate reverse dependencies and then repeating if anything looks likely to be used by anything else. I know there’s a script by @trofi that probably does a better job, and ofborg of course knows how to do it.
By the way, in the case of pyRFC3339, it looks like Certbot depends on it. Maybe that’s just a compatibility thing and it can use the standard library on newer versions, but if not we probably can’t drop it.

It calculates the number of rebuilds to tag by checking which output paths change. The ofborg-eval action output lists all of them.

Maybe this will come in handy for stuff we need to patch: https://github.com/pytest-dev/nose2pytest.

It calculates the number of rebuilds to tag by checking which output paths change. The ofborg-eval action output lists all of them.

yes but it gets the number of changed hydraJobs, it doesn't query for reverse deps (afaik)

Using https://github.com/trofi/nixpkgs-overlays/blob/main/lib/arevdeps.nix I got this list:

$ nix-instantiate --impure --read-write-mode --eval --strict ~/.config/nixpkgs/lib/arevdeps.nix --argstr attrName python311Packages.nose -I nixpkgs=$PWD --arg verbose 2 --arg depth 2
python311Packages.actdiag
python311Packages.biopandas
python311Packages.blockdiag
python311Packages.boto
python311Packages.braintree
python311Packages.bx-python
python311Packages.cassandra-driver
python311Packages.cgroup-utils
python311Packages.changefinder
python311Packages.chart-studio
python311Packages.dm-control
python311Packages.dodgy
python311Packages.envs
python311Packages.flask-restful
python311Packages.hkdf
python311Packages.http-ece
python311Packages.jsonable
python311Packages.libgpuarray
python311Packages.locationsharinglib
python311Packages.lockfile
python311Packages.mohawk
python311Packages.mwtypes
python311Packages.mwxml
python311Packages.neo
python311Packages.nose
python311Packages.nose-pattern-exclude
python311Packages.nose-timer
python311Packages.nose-warnings-filters
python311Packages.nose-xunitmp
python311Packages.nwdiag
python311Packages.ofxhome
python311Packages.ofxtools
python311Packages.para
python311Packages.paramz
python311Packages.paver
python311Packages.pid
python311Packages.pprintpp
python311Packages.preggy
python311Packages.premailer
python311Packages.prison
python311Packages.prox-tv
python311Packages.ptable
python311Packages.pycdio
python311Packages.pycontracts
python311Packages.pydy
python311Packages.pyexcel-ods
python311Packages.pyexcel-xls
python311Packages.pygatt
python311Packages.pygeoip
python311Packages.pygogo
python311Packages.pygtfs
python311Packages.pylacrosse
python311Packages.pypass
python311Packages.pyquaternion
python311Packages.pyrfc3339
python311Packages.pysrt
python311Packages.python-etcd
python311Packages.python-hglib
python311Packages.python-mapnik
python311Packages.pytimeparse
python311Packages.pyutilib
python311Packages.rauth
python311Packages.safe
python311Packages.sampledata
python311Packages.scikit-fuzzy
python311Packages.selectors2
python311Packages.seqdiag
python311Packages.sphinx-rtd-dark-mode
python311Packages.sqlalchemy-mixins
python311Packages.sure
python311Packages.svgutils
python311Packages.telfhash
python311Packages.tempita
python311Packages.tissue
python311Packages.traittypes
python311Packages.unicode-slugify
python311Packages.vxi11
python311Packages.webhelpers
python311Packages.weboob
python311Packages.xlwt

I'll try to keep a checklist up to date, based on @trofi's list:

[ ] python311Packages.actdiag
[ ] python311Packages.biopandas
[ ] python311Packages.blockdiag
[ ] python311Packages.boto
[X] python311Packages.braintree | #330290
[ ] python311Packages.bx-python
[ ] python311Packages.cassandra-driver
[X] python311Packages.citeproc-py | #330237
[ ] python311Packages.cgroup-utils | #330287
[ ] python311Packages.changefinder
[ ] python311Packages.chart-studio | #330248
[ ] python311Packages.dm-control
[ ] python311Packages.dodgy
[ ] python311Packages.envs
[ ] python311Packages.flask-restful
[ ] python311Packages.hkdf
[ ] python311Packages.http-ece
[ ] python311Packages.jsonable
[ ] python311Packages.libgpuarray
[ ] python311Packages.locationsharinglib
[ ] python311Packages.lockfile
[ ] python311Packages.mohawk
[ ] python311Packages.mwtypes
[ ] python311Packages.mwxml
[ ] python311Packages.neo
[ ] python311Packages.nose
[ ] python311Packages.nose-pattern-exclude
[ ] python311Packages.nose-timer
[ ] python311Packages.nose-warnings-filters
[ ] python311Packages.nose-xunitmp
[ ] python311Packages.nwdiag
[ ] python311Packages.ofxhome
[ ] python311Packages.ofxtools
[ ] python311Packages.para | #330229
[ ] python311Packages.paramz
[ ] python311Packages.paver
[ ] python311Packages.pid
[ ] python311Packages.pprintpp
[ ] python311Packages.preggy
[ ] python311Packages.premailer
[ ] python311Packages.prison
[ ] python311Packages.prox-tv
[ ] python311Packages.ptable
[ ] python311Packages.pycdio
[ ] python311Packages.pycontracts
[ ] python311Packages.pydy
[ ] python311Packages.pyexcel-ods
[ ] python311Packages.pyexcel-xls
[ ] python311Packages.pygatt
[ ] python311Packages.pygeoip
[ ] python311Packages.pygogo
[ ] python311Packages.pygtfs
[ ] python311Packages.pylacrosse
[ ] python311Packages.pypass
[ ] python311Packages.pyquaternion
[ ] python311Packages.pyrfc3339
[ ] python311Packages.pysrt
[ ] python311Packages.python-etcd
[ ] python311Packages.python-hglib
[ ] python311Packages.python-mapnik
[ ] python311Packages.pytimeparse
[ ] python311Packages.pyutilib
[ ] python311Packages.rauth
[ ] python311Packages.safe
[ ] python311Packages.sampledata
[ ] python311Packages.scikit-fuzzy
[ ] python311Packages.selectors2
[ ] python311Packages.seqdiag
[ ] python311Packages.sphinx-rtd-dark-mode
[ ] python311Packages.sqlalchemy-mixins
[ ] python311Packages.sure
[ ] python311Packages.svgutils
[ ] python311Packages.telfhash
[ ] python311Packages.tempita
[ ] python311Packages.tissue
[ ] python311Packages.traittypes
[ ] python311Packages.unicode-slugify
[ ] python311Packages.vxi11
[ ] python311Packages.webhelpers
[ ] python311Packages.weboob
[ ] python311Packages.xlwt

The list in my original issue is the relevant one. The packages present in @trofi’s list but not mine don’t depend directly on nose, so there’s nothing actionable to do with them. The reverse dependencies script is potentially useful when assessing whether to drop individual packages in my list.

Ah, sorry; I forgot that arevdeps.nix only does one level of reverse dependencies. So actually it’s relevant, and maybe some of the differences between the two might be due to the imprecision of my grep script.

Boto was archived 10 may 2024

Although boto is deprecated, a few things still depend on it, probably including out‐of‐tree projects. I’m not qualified to say if it’d be possible to do an immediate sweep of them, but I’d probably lean towards fixing it instead.

Seems like package weboob is a duplicate of woob?

webhelpers has doCheck = false due to broken code, but I cant access the source
Is is on my side, or repository is gone: https://bitbucket.org/bbangert/webhelpers

@Sigmanificient the source code should still be there on Pypi but yes, the original repo is gone.

I think it should be dropped, as it was not updated (release) from when it as been mode to pkgs/development/python-modules 6 years ago.
It dont have any reverse dependency

Seems like package weboob is a duplicate of woob?

Uhh, wow. The things you can find hiding in the corners of a repository this large. The one with a maintainer seems more polished and has a newer version and more current licence. But wow. We should definitely drop weboob; looks like upstream has used pytest since 2021, so it should be a pretty easy fix for the other one.

pylockfile is no longer maintained.

97 items: 32.99% done, 25.77% in progress, 40 waiting

[x] adafruit-nrfutil | #327199
[x] cmake-lint | #327220
[ ] mackup | #327240

python3Packages

[ ] actdiag | #330396
[x] beaker | #327530
[ ] biopandas
[ ] blockdiag | #330396
[ ] boto
[x] braintree | #330290
[ ] bx-python
[ ] cassandra-driver
[x] citeproc-py | #330237
[x] cgroup-utils | #330287
[ ] changefinder | #330311
[ ] chart-studio | #330248
[x] deform | #328917
[ ] dm-control
[ ] dodgy
[ ] envs
[x] expiringdict | #326665
[ ] flask-restful
[x] python311Packages.gocardless-pro | #326766
[ ] hkdf
[ ] http-ece
[ ] jsonable
[ ] libgpuarray
[ ] locationsharinglib
[ ] lockfile
[ ] mohawk
[ ] mwtypes
[ ] mwxml
[ ] neo
[ ] nose
[x] nose-pattern-exclude | #330439
[ ] nose-timer
[x] nose-warnings-filters | #330439
[ ] nose-xunitmp
[ ] nwdiag | #330396
[ ] ofxhome | #327239
[ ] ofxtools
[ ] pastescript | #327246
[ ] para | #330229
[ ] paramz
[ ] paver
[ ] pid | #327372
[ ] pprintpp
[x] preggy | #329978
[ ] premailer
[ ] prison
[ ] prox-tv
[ ] ptable
[ ] pycdio
[ ] pycontracts
[ ] pydy
[ ] pyexcel-ods
[ ] pyexcel-xls
[ ] pygatt
[ ] pygeoip
[x] pygogo | #329989
[ ] pygtfs
[ ] pylacrosse | #330500
[x] pypass | #330222
[x] pypillowfight | #327214
[ ] pyquaternion | #330459
[x] pyrfc3339 | #330496
[ ] pysrt | #330441
[x] pytest | #326541
[ ] python-etcd | #330438
[x] python-fedora | #327169
[ ] python-hglib
[ ] python-mapnik | #330432
[x] pytimeparse | #330421
[ ] pyutilib
[ ] rauth | #330417
[ ] safe | #330404
[x] sampledata | #330029
[ ] scikit-fuzzy
[x] selectors2 | #330024
[ ] seqdiag | #330396
[x] simplebayes | #330018
[x] spark-parser | #330001
[x] sphinx-rtd-dark-mode | #330383
[ ] sqlalchemy-mixins | #330493
[x] sure | #330012
[ ] svgutils | #330381
[x] telfhash | #330005
[ ] tempita | #330004
[x] tissue | #330376
[ ] traittypes | #330236
[ ] trfl | #329976
[x] unicode-slugify | #329998
[x] vxi11 | #329994
[ ] webhelpers | #330399
[ ] weboob | #330436
[x] xlwt | #330217
[x] yanc | #329978
[x] yarg | #327170

Maybe this will come in handy for stuff we need to patch: https://github.com/pytest-dev/nose2pytest.

I’ve packaged this in https://github.com/NixOS/nixpkgs/pull/330725 and am working on nose3 and its dependents.

I'm working on python-hglib, which has needed me to slightly redo the glean-sdk and glean-parser derivations. Should be submitting a PR as soon as nixpkgs-review finishes.

python3Packages.docker doesn't depend on nose, and hasn't for a while, should be good to check off.

Ah, that’s my script being bad. It’s docker-compose_1 in pkgs/applications/virtualization/docker/compose_1.nix. Which, uh, probably we could drop that?

97 items: 45.36% done, 16.49% in progress, 37 waiting

[x] adafruit-nrfutil | #327199
[x] cmake-lint | #327220
[x] mackup | #327240

python3Packages

[x] actdiag | #330396
[x] beaker | #327530
[x] biopandas | #330740
[x] blockdiag | #330396
[ ] boto
[x] braintree | #330290
[ ] bx-python | #330744
[ ] cassandra-driver | #330760
[x] citeproc-py | #330237
[x] cgroup-utils | #330287
[x] changefinder | #330311
[ ] chart-studio | #330248
[x] deform | #328917
[ ] dm-control
[x] dodgy | #330761
[ ] envs | #330762
[x] expiringdict | #326665
[ ] flask-restful
[x] gocardless-pro | #326766
[x] habanero | #330768
[x] hkdf | #330769
[ ] http-ece | #330771
[ ] isbnlib | #330773
[ ] inotify | #330776
[x] jsonable | #330777
[ ] libgpuarray
[ ] locationsharinglib | #330786
[ ] lockfile
[ ] mohawk
[ ] mwtypes | #330805
[ ] mwxml | #330805
[ ] neo
[ ] nose
[ ] nose3 | #330741
[x] nose-pattern-exclude | #330439
[x] nose-timer | #330535
[x] nose-warnings-filters | #330439
[ ] nose-xunitmp
[x] nwdiag | #330396
[x] ofxhome | #327239
[ ] ofxtools
[x] pastescript | #327246
[x] para | #330229
[ ] paramz
[ ] paver
[ ] pid | #327372
[ ] pprintpp | #330705
[x] preggy | #329978
[ ] premailer | #330702
[x] prison | #330700
[ ] prox-tv | #330699
[ ] ptable | #330696
[ ] pycdio | #330695
[ ] pycontracts | #330791
[ ] pydy
[x] pyexcel-ods | #330758
[x] pyexcel-xls | #330758
[ ] pygatt | #330688
[ ] pygeoip | #330509
[x] pygogo | #329989
[x] pygtfs | #330504
[x] pylacrosse | #330500
[x] pypass | #330222
[x] pypillowfight | #327214
[x] pyquaternion | #330459
[x] pyrfc3339 | #330496
[x] pysrt | #330441
[x] pytest | #326541
[x] python-etcd | #330438
[x] python-fedora | #327169
[ ] python-hglib | #330739
[x] python-mapnik | #330432
[x] pytimeparse | #330421
[x] pyutilib | #330759
[x] rauth | #330417
[ ] safe | #330404
[x] sampledata | #330029
[ ] scikit-fuzzy
[x] selectors2 | #330024
[x] seqdiag | #330396
[x] simplebayes | #330018
[x] spark-parser | #330001
[x] sphinx-rtd-dark-mode | #330383
[x] sqlalchemy-mixins | #330493
[x] sure | #330012
[ ] svgutils | #330381
[x] telfhash | #330005
[ ] tempita | #330004
[x] tissue | #330376
[x] traittypes | #330236
[ ] trfl | #329976
[x] unicode-slugify | #329998
[x] vxi11 | #329994
[x] webhelpers | #330399
[x] weboob | #330436
[x] xlwt | #330217
[x] yanc | #329978
[x] yarg | #327170

@emilazy python3Packages.mkl-service from the original list does not actually use nose. Guess we can get rid of it from the list.

Looks like I just missed https://github.com/NixOS/nixpkgs/pull/324729. Fixed!

lockfile is no longer maintained.

Apache airflow depends on it tho:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/servers/apache-airflow/python-package.nix

What are its reverse dependencies?

https://github.com/pydy/pydy/issues/490

aws-google-auth may be dead: https://github.com/cevoaustralia/aws-google-auth/issues/284

@emilazy in your list, candidates1 seems like a script error, i cant find it in nixpkgs

Uh, yeah I have no idea where that came from.

aws-google-auth may be dead: cevoaustralia/aws-google-auth#284

Probably just drop it, although we’re not running its tests anyway.

python3Packages.nbmerge was done in the following pr:

https://github.com/NixOS/nixpkgs/pull/324749

2 packages that have been already done @emilazy

#324749
#324734

24.05 uses Python 3.11 by default, so the packages here should mostly not be an issue. If you’re using Python 3.12, I would recommend using the unstable release until 24.11 is released.
(Also, most of these packages do already work with 3.12 on 24.11 as we have patched nose ourselves; we’re just trying to get them cleaned up.)

Interesting-- I was using nix-shell and for some reason my nix-channel was set to unstable so it was pulling from there and therefore using 3.12 i guess. I don't need 3.12 specifically, so updated the channel and all is well now. Thanks for taking the time to explain!

Up to date list:
114 items: 83.33% done, 14.91% in progress, 4 waiting

[x] adafruit-nrfutil | #327199
[x] aws-google-auth | #331352
[ ] caffe
[x] cmake-lint | #327220
[x] gixy | #330741
[x] grin | #330741
[ ] hydrus
[x] mackup | #327240
[x] mbutil | #334492
[ ] sasview
[x] svtplay-dl | #330741
[x] tarsnapper | #334462
[x] zk-shell | #333725

python2Packages

[ ] more-itertools

python3Packages

[x] actdiag | #330396
[ ] apricot-select
[x] androguard | #330535
[x] beaker | #327530
[x] biopandas | #330740
[x] blockdiag | #330396
[ ] blessings
[ ] boto
[x] braintree | #330290
[x] bx-python | #330744
[x] cassandra-driver | #330760
[x] citeproc-py | #330237
[x] cgroup-utils | #330287
[x] changefinder | #330311
[x] chart-studio | #330248
[ ] clickhouse-driver | #330959
[ ] clustershell
[x] deform | #328917
[x] dm-control | #330869
[x] dodgy | #330761
[ ] django-crontab
[x] envs | #330762
[x] expiringdict | #326665
[x] flask-restful | #330876
 | #333579
[x] gocardless-pro | #326766
[x] habanero | #330768
[ ] hkdf | #330769
[x] http-ece | #330771
[x] isbnlib | #330773
[ ] inotify | #330776
[x] jsonable | #330777
[ ] jupiter-contrib-nbextensions
[x] libgpuarray | #331841
[x] locationsharinglib | #330786
[ ] lockfile
[ ] mhcflurry
[x] mohawk | #331838
[x] mongoengine | #334487
[x] mwtypes | #330805
[x] mwxml | #330805
[x] neo | #330882
[ ] nose
[ ] nose2topytest
[x] nose3 | #330741
[x] nose-pattern-exclude | #330439
[x] nose-timer | #330535
[x] nose-warnings-filters | #330439
[x] nose-xunitmp | #330869
[x] nwdiag | #330396
[x] ofxhome | #327239
[x] ofxtools | #330866
[x] pastescript | #327246
[x] para | #330229
[x] paramz | #330865
[x] paver | #330858
[ ] pid | #327372
[x] pkutils | #330741
[x] pprintpp | #330705
[x] preggy | #329978
[ ] premailer | #330702
[x] prison | #330700
[x] prox-tv | #330699
[x] ptable | #330696
[x] pycdio | #330695
[x] pycontracts | #330791
[ ] pydy
[x] pyexcel-ods | #330758
[x] pyexcel-xls | #330758
[x] pygatt | #330688
| #332660
[ ] pygeoip | #330509
[x] pygogo | #329989
[x] pygtfs | #330504
[x] pylacrosse | #330500
[x] pypass | #330222
[x] pypillowfight | #327214
[x] pyquaternion | #330459
[x] pyrfc3339 | #330496
[x] pysrt | #330441
[x] pytest | #326541
[x] python-etcd | #330438
[x] python-fedora | #327169
[x] python-hglib | #330739
[x] python-mapnik | #330432
[x] pytimeparse | #330421
[x] pyutilib | #330759
[x] rauth | #330417
[ ] rx
[x] safe | #330404
[x] sampledata | #330029
[ ] scales | #334466
[ ] scikit-fuzzy | #330854
[x] selectors2 | #330024
[x] seqdiag | #330396
[ ] shap
[x] simplebayes | #330018
[x] spark-parser | #330001
[x] sphinx-rtd-dark-mode | #330383
[x] sqlalchemy-mixins | #330493
[ ] stytra
[x] sure | #330012
[x] svgutils | #330381
[x] telfhash | #330005
[x] tempita | #330855
[x] tissue | #330376
[x] traittypes | #330236
[ ] trfl | #329976
[ ] uncompyle6
[x] unicode-slugify | #329998
[x] vxi11 | #329994
[ ] webassets | #334483
[x] webhelpers | #330399
[x] weboob | #330436
[ ] wsme | #334472
[x] xlwt | #330217
[x] yanc | #329978
[x] yarg | #327170

umcompyle6 has doCheck = pythonOlder "3.9"; but when using nix-build -A python312.umcompyle6 tests are still being run, am I missing something @emilazy?

@emilazy should we drop more-itertools?

more-itertools

We can't, it is to widely used

Try removing it and see what breaks. I would be in support to drop eg https://github.com/NixOS/nixpkgs/blob/21576aba43e604a95cc45c25248f39f3989ebe36/pkgs/servers/neard/default.nix
but we need to keep gimp intact https://github.com/NixOS/nixpkgs/blob/21576aba43e604a95cc45c25248f39f3989ebe36/pkgs/applications/graphics/gimp/default.nix#L137
I didn't find anything else uses python2 packages on the fast but I didn't search for all variants.

Ignore Python 2; it is even more obsolete than nose. GIMP will be solved soon and I have plans for the rest of Python 2.

Sorry for my long absence from working on this. I’ve cleaned up the list in the first comment to be easier to follow now that most users have been dealt with, and left a few reviews. I hope we can get this done before 24.11!

PRs of my own in flight:

https://github.com/NixOS/nixpkgs/pull/343776
https://github.com/NixOS/nixpkgs/pull/343785
https://github.com/NixOS/nixpkgs/pull/343797
https://github.com/NixOS/nixpkgs/pull/343820

I’m looking at python3Packages.mhcflurry and python3Packages.uncompyle6, which are now almost the only remaining packages without an open PR.

Turns out I was wrong about Python 2.7 packages not mattering… https://github.com/NixOS/nixpkgs/pull/343822

@Sigmanificient Hi there, just checking if you plan to address the review comments on your pending PRs? No worries if not; I just want to make sure if you’d rather work more on them or would be happier for someone else to take over.

We’ve finally reached the end of the road!

https://github.com/NixOS/nixpkgs/pull/348699

Thanks again to everyone who helped out with this immense effort.

@Sigmanificient Hi there, just checking if you plan to address the review comments on your pending PRs? No worries if not; I just want to make sure if you’d rather work more on them or would be happier for someone else to take over.

Hey, sorry i don't have a lot of avalaible time currently :<

No worries! You played a huge part in this and I’m happy we’ve finally reached the finish line.


[WIP] Adding ProteoRE 'filter kw and values' tool - Version 2<IP_ADDRESS>

From ProteoRE team : as agreed after the Valentin's PR (see here)
https://github.com/galaxyproteomics/tools-galaxyp/pull/535
We now make the PR tool by tool.
This is the first one, there are 17 more to come ...
Thanks in advance for the review !

What is the version in the PR title refering to? Version 2<IP_ADDRESS>?
Do you intend to keep this https://github.com/vloux/ProteoRE/tree/master/tools/proteore_filter_keywords_values? Then I would prefer to make the proteore repo a proper python package released on pypi and bioconda which we could then use as requirement.

Hello Matthias,
the version in the PR is the version of the Galaxy wrapper.
We intend to "close" the repos for the Proteore tools as soon  as they have been transferred in Galaxy-P.


keras Sequential model get empty metrics_names

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Catalina 0.15.5
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): pip3 install --upgrade tensorflow
TensorFlow version (use command below): 2.3.0
Python version:

Python 3.7.5 (default, Oct 25 2019, 10:52:18)
[Clang 4.0.1 (tags/RELEASE_401/final)] :: Anaconda, Inc. on darwin

Bazel version (if compiling from source): NA
GCC/Compiler version (if compiling from source): NA
CUDA/cuDNN version: NA
GPU model and memory: NA

Describe the current behavior
def build_model():
    model = keras.Sequential()
    model.add(keras.layers.Embedding(vocab_size, 64))
    model.add(keras.layers.GlobalAveragePooling1D())
    model.add(keras.layers.Dense(128, activation='relu'))
    model.add(keras.layers.Dense(128, activation='relu'))
    model.add(keras.layers.Dense(64, activation='relu'))
    model.add(keras.layers.Dense(1))
    optimizer = tf.keras.optimizers.RMSprop(0.01)
    model.compile(loss='mse',
                  optimizer=optimizer,
                  metrics=['mae', 'mse'])
    return model

model = build_model()
print(model.metrics_names)  #  print []

Describe the expected behavior
should print out: ['loss', 'mae', 'mse']
tensorflow 2.1.0 print correct

@zishuaiz,
As per the documentation, metrics_names are available only after a keras.Model has been trained/evaluated on actual data.
Could you please check if you are facing the same issue after training the model? Thanks!


treewide: cleaning

treewide (cleaning): helpers.neovim-plugin -> lib.nixvim.neovim-plugin
treewide (cleaning): helpers.vim-plugin -> lib.nixvim.vim-plugin

@MattSturgeon @khaneliman the lib-test failure is interesting...

Think it's still helpers namespace in lib ?

@mergifyio queue


native: prohibit non-zero NEP-17 roundtrip with zero balance

Close #3190.
I'm struggling with the fact that we have updateAccBalance. It's the third time when I'm trying to fix roundtrips. We already have TestNEO_Roundtrip, TestNEO_TransferZeroWithNonZeroBalance and TestNEO_TransferZeroWithZeroBalance, and I'm still not sure that it works correctly. To be honest, I would love to rewrite TransferInternal and remove updateAccBalance at all, to match C# code perfectly, line-by-line.
Node sync is in progress to check that the bug is fixed.

Ref. https://github.com/nspcc-dev/neo-go/pull/2169.
🥳🎉👏🤝👍

match C# code perfectly, line-by-line

It'd be very ineffective.

I know, but at least we can be (almost) sure that our implementation matches. Although this bug is the last uncovered case (hope so).

Mainnet states up to 4377948 are OK:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ go run ./scripts/compare-states/compare-states.go http://seed1.neo.org:10332 http://localhost:10332
at 0: d34893828a2ddb99c87226a92f764ae2dfadd0d2dc53fb33ae425be83b8d30b4 vs d34893828a2ddb99c87226a92f764ae2dfadd0d2dc53fb33ae425be83b8d30b4
at 4377948: fe0fad999db0dc43ce58f6b3aab40dbf8e087e8809d85dca5aef3c6a51cebc7d vs fe0fad999db0dc43ce58f6b3aab40dbf8e087e8809d85dca5aef3c6a51cebc7d

Mentioned transaction application log also matches:
NeoGo's:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["0x97139d1cf3e96c400ce6988c19daf643df94c184afa2989e367ea4f6c1526543"] }' localhost:10332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   414  100   272  100   142  16000   8352 --:--:-- --:--:-- --:--:-- 25875
{
   "jsonrpc" : "2.0",
   "id" : 1,
   "result" : {
      "txid" : "0x97139d1cf3e96c400ce6988c19daf643df94c184afa2989e367ea4f6c1526543",
      "executions" : [
         {
            "stack" : [
               {
                  "value" : false,
                  "type" : "Boolean"
               }
            ],
            "trigger" : "Application",
            "gasconsumed" : "997775",
            "notifications" : [],
            "exception" : null,
            "vmstate" : "HALT"
         }
      ]
   }
}

NeoC#'s:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["0x97139d1cf3e96c400ce6988c19daf643df94c184afa2989e367ea4f6c1526543"] }' http://seed1.neo.org:10332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   413    0   271  100   142    357    187 --:--:-- --:--:-- --:--:--   543
{
   "jsonrpc" : "2.0",
   "result" : {
      "executions" : [
         {
            "gasconsumed" : "997775",
            "trigger" : "Application",
            "exception" : null,
            "stack" : [
               {
                  "value" : false,
                  "type" : "Boolean"
               }
            ],
            "notifications" : [],
            "vmstate" : "HALT"
         }
      ],
      "txid" : "0x97139d1cf3e96c400ce6988c19daf643df94c184afa2989e367ea4f6c1526543"
   },
   "id" : 1
}

Testnet states up to 2973685 are OK:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ go run scripts/compare-states/compare-states.go http://seed1t5.neo.org:20332 http://localhost:20332
at 0: ed359c92fd2e5d3fb6cc57c1599481b223b9eea82bcf940dd1a3db354a9b99d6 vs ed359c92fd2e5d3fb6cc57c1599481b223b9eea82bcf940dd1a3db354a9b99d6
at 2973685: 03ebed4fb630c66215aae040fe43b169f93238b722e7e0e2d1c16d6221384049 vs 03ebed4fb630c66215aae040fe43b169f93238b722e7e0e2d1c16d6221384049

Ready for review, merge and release.


ExtensionCallMarkLogic appends to content instead of replacing

The results of an ExtensionCallMarkLogic processor are appended to the flow file's content instead of replacing it. Replacing seems to be the standard action by most processors (including InvokeHTTP, which has similar functionality). When results are appended, they often become harder to read. For instance, when a JSON object is appended to a JSON object, the result is not valid JSON. That means that processors like EvaluateJsonPath cannot be used to work with the results.
Because that's how the processor works now (as of <IP_ADDRESS>), we have some flows that work around this. To maintain compatibility with existing flows, the behavior could be controlled by a new property with options "Append" and "Overwrite". "Append" could be the default to maintain backward compatibility.

@dmcassel Think there are a couple scenarios here:

If the incoming FlowFile has content, it seems that append would never be desired
For a new FlowFile, append would make sense when it's desirable that each "result" returned by the custom endpoint should be appended together.

I'm not sure of when 2 would be true though. I would guess that when a custom endpoint returns a sequence of items, those items are intended to be kept separate. Which makes me wonder if the correct behavior should be to return a new FlowFile for each item returned by the endpoint? I don't think that's what you're asking for, but it seems more correct and also solves the problem here? Or is there a valid use case for appending each returned item together as the body of a single FlowFile?

@rjrudin for scenario 2 -- looking at the code for ExtensionCallMarkLogic, I see that if !requiresInput and the flow file retrieved from the session is null, then it will create a new flow file. In that case, there's nothing to overwrite, so overwriting rather than appending makes sense.
Worth noting -- line 190 is using append. By all means, multiple results should be joined together, but I suggest that the combined result should overwrite whatever was previously in the flow file content, not be added to it.

@dmcassel Just to confirm - when the endpoint returns more than one item, the expectation is that all items will be "joined" together, and the result will overwrite the content of the FlowFile (regardless of whether it's new or existing)?

@rjrudin I just re-read this comment chain and I'm rethinking what I said about scenario 2 above.

If there is an incoming flow file and it has content, I think overwriting it would always be the sensible thing to do. There's a backwards-compatibility argument to keeping "overwrite" as the default behavior, but it's hard to imagine when that would be helpful.
If the processor will return a Sequence of more than one item, maybe the reasonable thing to do is clone the original flow file (so you still have the attributes) for each item in the Sequence and set the body to that item. That's how ExecuteScriptMarkLogic works. As with ExecuteScriptMarkLogic, if you want to return multiple values while sticking with one flow file, you can return an Array.

Approach 2 would be a change in how this processor works. The simpler thing to do is concatenate the results together and overwrite, but this feels like it would be more useful. If we wanted to take this approach, we could create relationships original and results that work like ExecuteScriptMarkLogic and keep the success relationship the same. Or we could drop the success relationship in favor of the new ones, which would simplify the code.
I can see a couple different approaches being useful here. The main thing to me is that the current approach creates an obstacle. Thoughts?

@dmcassel First, I think you meant a backwards-compatibility argument for "append" as the default behavior?
The current "append" approach does seem odd; I can't really think of a scenario where items in a returned sequence should be joined together as strings. Even e.g. lines of CSV would want newlines in between them.
I like how ExecuteScript works, creating a new cloned FlowFile per item in the returned sequence. That seems like the most expected behavior. So I think we should definitely support that. And original and results make a lot of sense. Really, the two processors are doing the same thing - i.e. invoking a pile of code in MarkLogic - they're just invoking the code in different ways. It makes sense that they would otherwise behave the same (though I'm not sure of the use case for "first result" and "last result" in ExecuteScript - I wouldn't want to incorporate that yet).
Perhaps for backwards compatibility - it would suffice to keep the "success" relationship but deprecate it? And, to avoid the performance cost of appending potentially a large amount of data for no purpose, the processor could include a new option for not writing to the success relationship. That would have to default to false for backwards compatibility, but it would be easy to set to true and just get the expected data on "original" and "results".

@dmcassel One other idea - I am now thinking that the processor should either do the current "append" behavior or do the new original/results behavior that ExecuteScript does. I can't think of a reason why a user would want both (particularly since I can't think of a reason why the user would ever want "append").
So I'm thinking the following:

A new "Append and Send to Success" boolean property that defaults to true (for backwards compatibility)
If the "Append" property is true, it'll do what happens today
If it's false, it will instead send the original FlowFile (including a brand new one per #142 ) to the new "Original" relationship and each item returned by the extension call will result in a cloned FlowFile with its content containing the item and sent to the new "Results" relationship.

@rjrudin that sounds great

@dmcassel An idea (from @BillFarber , who made a real stink if I didn't give him credit for it) - should we do a new processor here instead of having a boolean switch to control how it works? I'm not sure what we'd call it - ExtensionCall2MarkLogic?

That would be less confusing. "CallResourceMarkLogic"?

@dmcassel We were debating this internally - my concern was that the migration to a new processor is a bit of a pain:

You have to delete all the connections to the existing ExtensionCallML
You then delete ExtensionCallML
You then bring the new processor on and reconfigure it

Also, I think the name of a new processor would need something to imply that "Hey, you should really use this, not the other one". I'm not sure "CallResource" does that. Also worried that "Resource" is too generic, because technically ML calls e.g. /v1/documents a resource, whereas this is for calling "resource extensions" - in which case CallExtensionResourceML would probably be the way to go.
Actually, now I'm liking this rename because "ExtensionCall" is the only "NounVerb" processor we have - all the others are "Verb(optional Noun)".
We still have the migration, which is a pain in the neck no matter what we call it. Thoughts?

I think in the long run the migration is worth it. Having two very different ways to use the same processor would be confusing, as well as making the code more complex. While it would be some work to replace existing ExtensionCallMarkLogic processors, we've already accepted that we're looking at making new relationships. Personally, I'd find it worthwhile.

Also worried that "Resource" is too generic

Fair point. I was looking for an alternative to the "2".

CallExtensionResourceML would probably be the way to go

Works for me. Updating the description of the old processor (starting with "Deprecated - use CallExtensionResourceML") is important for the transition.

Thanks, that's good feedback on the migration - we'll go with a second processor.

CallRestExtensionML ?
It might be helpful to make it clear that it is a REST extension.

I think "CallRestExtension" works. The docs - https://docs.marklogic.com/REST/client/service-extension - call is a "resource service extension". And technically, there are other extensions to the REST API, such as transforms and search options. But I think "REST Extension" is commonly understood what we want it to mean here. And I think "Rest" is fine instead of "REST" as acronyms look funny in class names, and Spring does RestTemplate.

I wish it had "Rest" in there somewhere.
How about CallRestExtensionML
On Wed, Aug 24, 2022 at 4:42 PM David Cassel @.***>
wrote:

I think in the long run the migration is worth it. Having two very
different ways to use the same processor would be confusing, as well as
making the code more complex. While it would be some work to replace
existing ExtensionCallMarkLogic processors, we've already accepted that
we're looking at making new relationships. Personally, I'd find it
worthwhile.
Also worried that "Resource" is too generic
Fair point. I was looking for an alternative to the "2".
CallExtensionResourceML would probably be the way to go
Works for me. Updating the description of the old processor (starting with
"Deprecated - use CallExtensionResourceML") is important for the transition.
—
Reply to this email directly, view it on GitHub
https://github.com/marklogic/nifi/issues/132#issuecomment-1226297944,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM6EJPT7ILD27ZOFC7PPVLV22CMXANCNFSM5XN65MDA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I wish it had "Rest" in there somewhere.
How about CallRestExtensionML

I get the appeal of having "Rest" in there, but <opinion> think having "MarkLogic" in the name outweighs that</opinion>.


Where are the built files written to?

I'm looking at the webpack.config file and I see this block:
output: {
    path: './dist',
  },

However, when I build the project with npm start, although I am able to load the project in the browser I cannot find the dist directory. Where are the built files being written?

Same for me. I work with Win7. How to set in Production ?

If you run npm start in the project it will use webpack-dev-server, and all files server by it will by ran from the memory, so there will be no files created on the disk.
You can resolve it by using npm run watch and then server the files somewhere else.

@willyelm explanation covers what is going on during dev. For prod build see #17


🚀 feat(AutoComplete): flag to bypass options filtering

Description 📄
Added new shouldFilterOptions prop to AutoComplete to bypass filtering and sorting dropdown options.
Disclaimer: This prop will have a true default value so we can avoid breaking changes
Platforms 📲

[x] Web
[ ] Mobile

Type of change 🔍

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested? 🧪

[x] Unit Test
[ ] Snapshot Test

Checklist: 🔍

[x] My code follows the contribution guide of this project Contributing Guide
[ ] Layout matches design prototype: FIGMA
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Screenshots 📸
https://user-images.githubusercontent.com/26771441/228029604-9dc4794f-84f2-487d-8eaa-67e11c55744d.mov

@all-contributors please add @marinamsou for code


[CLI v1] Change flags format

At the moment, all flags are in the snake case format like --num_of_addresses and should be all changed to the standard one, ie --num-of-addresses

Closed by #728