[Bug]: React warning about trimValue on input in dev console

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks

Fix it.

index.js:1 Warning: React does not recognize the `trimValue` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `trimvalue` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
    in input (at TextInput.tsx:158)
    in Unknown (created by TextInput__StyledInput)
    in TextInput__StyledInput (at TextInput.tsx:401)
    in div (created by TextInput__InputWrapper)
    in TextInput__InputWrapper (at TextInput.tsx:369)
    in TextInput (created by WithTheme(TextInput))
    in WithTheme(TextInput) (at UserGitProfileSettings/index.tsx:211)
    in div (created by UserGitProfileSettings__InputContainer)
    in UserGitProfileSettings__InputContainer (at UserGitProfileSettings/index.tsx:210)
    in div (created by UserGitProfileSettings__MainContainer)
    in UserGitProfileSettings__MainContainer (at UserGitProfileSettings/index.tsx:182)
    in UserGitProfileSettings (at GitConnection.tsx:469)
    in div (created by GitConnection__Container)
    in GitConnection__Container (at GitConnection.tsx:379)
    in GitConnection (at GitSyncModal.tsx:146)
    in div (created by GitSyncModal__BodyContainer)
    in GitSyncModal__BodyContainer (at GitSyncModal.tsx:145)
    in div (created by GitSyncModal__Container)
    in GitSyncModal__Container (at GitSyncModal.tsx:126)
    in div (at DialogComponent.tsx:178)
    in div (created by Blueprint3.Dialog)
    in div (created by Blueprint3.Dialog)
    in Transition (created by CSSTransition)
    in CSSTransition (created by Blueprint3.Overlay)
    in div (created by TransitionGroup)
    in TransitionGroup (created by Blueprint3.Overlay)
    in Blueprint3.Portal (created by Blueprint3.Overlay)
    in Blueprint3.Overlay (created by Blueprint3.Dialog)
    in Blueprint3.Dialog (created by DialogComponent__StyledDialog)
    in DialogComponent__StyledDialog (at DialogComponent.tsx:162)
    in DialogComponent (at GitSyncModal.tsx:117)
    in GitSyncModal (at Editor/index.tsx:224)
    in div (at GlobalHotKeys.tsx:400)
    in HotkeysTarget(GlobalHotKeys) (created by Connect(HotkeysTarget(GlobalHotKeys)))
    in Connect(HotkeysTarget(GlobalHotKeys)) (at Editor/index.tsx:220)
    in div (at Editor/index.tsx:213)
    in Unknown (at Editor/index.tsx:207)
    in Be (at Editor/index.tsx:206)
    in Editor (created by profiler(Editor))
    in Profiler (created by profiler(Editor))
    in profiler(Editor) (created by Connect(profiler(Editor)))
    in Connect(profiler(Editor)) (created by Context.Consumer)
    in withRouter(Connect(profiler(Editor))) (at loader.tsx:23)
    in EditorLoader (created by Context.Consumer)
    in Route (created by sentryRoute(Route))
    in sentryRoute(Route) (at AppRouter.tsx:137)
    in Switch (at AppRouter.tsx:113)
    in Suspense (at AppRouter.tsx:104)
    in Router (at AppRouter.tsx:103)
    in AppRouter (created by Connect(AppRouter))
    in Connect(AppRouter) (at src/index.tsx:64)
    in AppErrorBoundary (at src/index.tsx:63)
    in Be (at src/index.tsx:53)
    in ThemedApp (created by Connect(ThemedApp))
    in Connect(ThemedApp) (at src/index.tsx:35)
    in Provider (at src/index.tsx:33)
    in ErrorBoundary (at src/index.tsx:32)
    in App (at src/index.tsx:84)

Cannot reproduce anymore.


self-update: should resolve pixi binary from channel

Problem description
now self update command parse the result from github api. it is better to resolve self via a fixed (forge) channel, then it will take the advantage of the mirror global configuration. Now the micromamba does like this.

This is doable but I suspect there are differences between binaries published on GitHub release and conda-forge, the one on conda-forge does not have codesigning at least.

This is doable but I suspect there are differences between binaries published on GitHub release and conda-forge, the one on conda-forge does not have codesigning at least.

How about a -c flag to imply resolve via channel? Then the default action is still resolving version via github api.

I think using the binary from github is better since this is also the binary that's being end-to-end tested in CI.
Also, the version from conda-forge has additional dependencies that the unknown-linux-musl version from github doesn't have: https://conda-metadata-app.streamlit.app/?q=conda-forge%2Flinux-64%2Fpixi-0.17.1-h614bb76_1.conda (namely openssl and libgcc-ng).
I strongly believe that you shouldn't require a package manager to set up a package manager. This is imo one of the biggest flaws of mamba (and also conda with its complicated setup) currently. A plain binary should be all that's needed.
If you are inside of a corporate environment where you need mirror configuration, you should think about a different way than pixi self-update of updating pixi imo.
You managed to get pixi in this environment in some way; just do that again.

An alternative that wouldn't be as horrible as getting it from conda-forge would be able to provide a URL: pixi self-update --url https://my.private.server/pixi/0.17.1/pixi-unknown-linux-musl
setup-pixi has a similar option to specify a URL instead of a version: https://github.com/prefix-dev/setup-pixi/blob/2e317cc221abec0d45bcf385189f7d97d0744e15/action.yml#L9-L12

An alternative that wouldn't be as complicated as getting it from conda-forge would be able to provide a URL: pixi self-update --url https://my.private.server/pixi/0.17.1/pixi-unknown-linux-musl
setup-pixi has a similar option to specify a URL instead of a version: https://github.com/prefix-dev/setup-pixi/blob/2e317cc221abec0d45bcf385189f7d97d0744e15/action.yml#L9-L12

@pavelzw the url can resolve the inner-corp problems.

I strongly believe that you shouldn't require a package manager to set up a package manager.

@pavelzw The package manager resolving method by pixi itself would honor the running host limit or upper bond patch or the yank info to avoid downloading an unusable version.
How about a flag of pixi self-update to select resolving method, github-release or bootstrap; when set to github-release, we can also specify the url or use the mirror configuration for github release. The github-release way can also be a fallback of bootstrap.

What should bootstrap do?

What should bootstrap do?

here i use bootstrap to mean resolving pixi itself within an official channel with normal resolving lib, and add additional pkg requirements if needed.

As explained above, there are a number of reasons why this is a bad idea.
IMO the conda-forge distribution is „just another package manager“ providing pixi. The official (and ideally single) source of truth should lie in this GitHub repository.

As explained above, there are a number of reasons why this is a bad idea, the main one being that it just won’t work because conda-forge provides a dynamic build instead of a static like here. IMO the conda-forge distribution is „just another package manager“ providing pixi. The official (and ideally single) source of truth should lie in this GitHub repository.

then the only left way is a custom url option for github api and github release.

@pavelzw's --url option sounds good to me!
PR's are welcome!


Bug Fix: Map Search Field Not Clickable

This PR addresses two bugs where you could not click into the map's search field and you could not click the map tooltip. It fixes the bugs by adding `pointer-events: bounding-box' to globals.css for the classes for each of those features:

maplibregl-ctrl-top-right
maplibregl-ctrl-bottom-left

I've also added setSearchedProperty({...searchedProperty, address: "" }) to the map handleClick function.  Without that, if the map is clicked on a non-vacant property, the map changes the popup tooltip to the last searched property.
This closes issue #582

Thanks @jgrimes86! @all-contributors, please add @jgrimes86 for code


78 collect stats for usage and health

Description
Collecting stats about requests in total, requests with errors and cache usage.
Issues Resolved
https://github.com/opensearch-project/opensearch-learning-to-rank-base/issues/78
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ylwu-amzn
@jngz-es


track internal links to do not open track pane

Eg, clicking this link does not load the track pane:
https://2023.ipfs-thing.io/#IPFS-on-the-Web

Added with PR #174


Swagger UI integration issue

swagger-ui version v2.1.4
a swagger file reproducing the issue -index.html

Brief description for problem.
I am using swagger.io's  swagger-jaxrs - 1.5.9
I am trying to integrate Swagger UI for Rest easy API. I am able to see swagger.json at http://localhost:8080/SwaggerRestAPI/rest/swagger.json. I have copied dist folder in WEB-INF folder and changed the url in index.html to http://localhost:8080/SwaggerRestAPI/rest/swagger.json and tried to fetch UI by using URL http://localhost:8080/SwaggerRestAPI but it is returning 404 response. Can anybody help me?

I think this belongs in swagger-ui.


feat: Selective auth

Resolves #1708
TODO:

[x] Disallow value + regex together in the same filter
[ ] Add mapping interface to OperationDefinition (for convenience)
[ ] Allow multiple auth providers per storage and take the first one matched
[ ] Document auth - examples, corner cases, possible errors, uppercasing method
[ ] More docstrings
[ ] Tests for using multiple auths
[x] Tests with compiler regex with custom flags
[ ] requests auth support

Codecov Report

Merging #1709 (f4909ae) into master (2aaedf7) will decrease coverage by 0.29%.
The diff coverage is 91.08%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master    #1709      +/-   ##
==========================================
- Coverage   98.94%   98.66%   -0.29%
==========================================
  Files          97       98       +1
  Lines        7801     7938     +137
  Branches     1618     1343     -275
==========================================
+ Hits         7719     7832     +113
- Misses         49       68      +19
- Partials       33       38       +5

Impacted Files
Coverage Δ

src/schemathesis/auths.py
89.85% <74.07%> (-10.15%)
:arrow_down:

src/schemathesis/filters.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/validation.py
76.47% <0.00%> (-11.77%)
:arrow_down:

src/schemathesis/_compat.py
73.17% <0.00%> (-4.88%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.84% <0.00%> (-1.16%)
:arrow_down:

src/schemathesis/cli/cassettes.py
98.89% <0.00%> (-1.11%)
:arrow_down:

src/schemathesis/utils.py
97.02% <0.00%> (-0.75%)
:arrow_down:

src/schemathesis/cli/output/default.py
99.16% <0.00%> (-0.01%)
:arrow_down:

src/schemathesis/service/report.py
100.00% <0.00%> (ø)

src/schemathesis/runner/impl/threadpool.py
100.00% <0.00%> (ø)

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


automatically generate op convenience overloads?

Should we extend the code generation for ops to automatically generate convenience overloads? This would help reduce the gap between Python notation and Java notation.
As an example of where we stand now, here's some Python code (keras/metrics.py, around line 2203):
    dp = p[:self.num_thresholds - 1] - p[1:]

And here's the corresponding Java code (AUC.java, around line 809):
    Operand<T> dP =
        tf.math.sub(
            tf.slice(
                p, tf.constant(new int[] {0}), tf.constant(new int[] {getNumThresholds() - 1})),
            tf.slice(p, tf.constant(new int[] {1}), tf.constant(new int[] {-1})));

Here's another example a little further down in the same code.
Python:
math_ops.maximum(dp, 0)

Java:
tf.math.maximum(dP, tf.dtypes.cast(tf.constant(0), dP.type()))

The slicing can be cleaned up a bit with the new stridedSlice api.  And while I'm not sure auto-casting is a good idea as it makes runtime errors very easy, a method like Operand<T>.castToType(x: Operand<*>) could be helpful (although it needs a clearer name).
One potential generation strategy for ops like maximum is to look at the supported types for the arguments, and if it supports all of TNumber, generate an overload like maximum(Operand<T>, Operand<TNumber>) that cases, although it would have to be named something else (maximumCasting?).
More generally though, this is something I'd really like to do, especially for axis type parameters on reduction ops and things like reshape and permute that usually are constants, not tensors.
However, generating these isn't really possible, since they aren't specified anywhere in the op defs.  All we know for say ArgMax is that dimension is an int, not that it's a scalar.  Even looking for Tidx doesn't work, as it's just a name and is used for both single indices and lists of indices.
If we want to do something like this, it would have to be done manually.  I still think it's worth doing at some point, and we can clean up some of the other api idiosyncrasies at the same time (like permute being done via transpose), but we'd need to create a curated api like tf.experimental.numpy.

One simple way to manually curate an API would be to start now, choosing the location and pattern, and fill it out as we code. We could choose a pattern that would be relatively amenable to being completed at a later time, such as by organizing the methods in such a way that one of us could eventually sweep through the whole list of ops and fill in the blanks.

Alternatively, we could advocate into the main TensorFlow project that we add enough information to the protobuf files to generate high-usability statically typed APIs? I wouldn't expect this challenge to be unique to Java.

Or, another alternative, we could create our own set of protobuf files that add this information, and then gradually populate those as we code. Over time, we could advocate pushing that information upstream into the main protobuf files.

I like the protobuf options more, since it's a lot easier to generate Kotlin wrappers off of it.  Even just optional scalar and vector tags for inputs would go a long way, and wouldn't be hard to add defaults to.  Dynamic defaults (i.e. setting axes to be 0..x.rank) is much harder to express in something like protobuf and would probably have to be done manually.
If we do end up doing our own version, I'd want to heavily use annotations to mark things like parameters that should be receivers so that I can generate matching idiomatic Kotlin APIs without having to maintain 2 curated APIs.

My leaning is that the sooner we start this, the less painful it will be, because we have an opportunity to do it -- and tweak it -- as we write our own code. Combining that with @rnett's point about preferring protobuf to hand-code, perhaps the best starting point would be adding our own protobuf files that augment (1 for 1) main tensorflow's files, and that allow us to better tune our codegen to Java and Kotlin?
I expect we'd eventually want to advocate for pushing (some or all of) our new metadata upstream, but that would be a slower process and might make more sense once we had goodness to demonstrate?

Agreed about starting soon.
I'm reconsidering the "protobuf is better" a bit though.  There's non-straightforward things like transpose vs permute and reduction methods default axes being all of them that I think is to hard to encode, so even if we did do protobuf for most things, we'd still need a Java layer for some, and at that point we might as well just do everything in Java.

We may want to consider combining this with #255 in some way, as they are a bit similar.

Wow, I'm increasingly appreciating that this is a large design space with lots of conflicting goals and constraints. Would it make the most sense for someone to draft a design document? One approach could be doing this as a .md file in the repo, so we can hash it out through PRs.

#264 is an excellent motivating example.  See transpose being under linalg (but not in python?), no permute, and no transpose without specifying the permutation (i.e. the default argument).
I think a design doc would make sense.  Could do it as an issue like I did for functions if we don't want to start adding docs, but I do like the idea of being able to PR it.  I don't have the time to work on that at the moment, but I can look it over and make sure it would work with the Kotlin generation.


Issue Publishing Bot Framework Composer to Azure

When I try publishing the bot to Azure, I get the error

@Intelliteckai Could you follow the issue template we currently have indicating the version of Composer, OS etc.

@srinaath I thought i was following the issues template on here as i used the "other" template. i didn't think the bug or feature request templates were appropriate. Do you have a particular one in mind?
The version of the composer is 2.0.0, the operating system is mac os.
When you ask for the publishing profile, do you mean the .json file?

{
"name": "smartdesk1",
"environment": "Azure DevTest",
"tenantId": "ba3c42f4-8aa0-47e6-a3d2-81faec4e7f4b",
"hostname": "smartdesk1",
"runtimeIdentifier": "win-x64",
"resourceGroup": "virtualDesk-RG",
"botName": "smartdesk1",
"subscriptionId": "4e81d975-8fdc-4321-a0fd-f7669f448db7",
"region": "UK South",
"appServiceOperatingSystem": "windows",
"scmHostDomain": "",
"luisResource": "smartdesk-PredictionResource",
"settings": {
"applicationInsights": {
"InstrumentationKey": "83d31d31-f927-4c9e-8774-0c7518886f51",
"connectionString": "InstrumentationKey=83d31d31-f927-4c9e-8774-0c7518886f51;IngestionEndpoint=https://uksouth-1.in.applicationinsights.azure.com/"
},
"cosmosDb": {
"cosmosDBEndpoint": "",
"authKey": "",
"databaseId": "botstate-db",
"containerId": "botstate-container"
},
"blobStorage": {
"connectionString": "",
"container": ""
},
"luis": {
"authoringKey": "04c6185c939e4c8aa4122f6907463c30",
"authoringEndpoint": "https://westeurope.api.cognitive.microsoft.com/",
"endpointKey": "b8e7284f0182469fa9f5bb851a9ca833",
"endpoint": "https://westeurope.api.cognitive.microsoft.com/",
"region": "westeurope"
},
"qna": {
"subscriptionKey": "",
"endpoint": ""
},
"MicrosoftAppId": "25b7394b-e09e-461c-920c-c058aa6fb0b6",
"MicrosoftAppPassword": ""
}
}

@Intelliteckai I just deleted your previous comment due to sensitive info exposed in a public github repo.

So, wht you had pasted was the appsettings.json. The publishing profile is in this view when hit "Edit". Its basically the data that is required to publish to azure. If you can "redact" sensitive data and paste the profile we could see what properties are missing in the profile. Another step to try is what is documented here https://github.com/microsoft/BotFramework-Composer/issues/8489. Basically checking the logs to get us a bit more information.

can you please be specific about what you need. I am not too familiar with the bot composer or azure bot service itself.
there isn't any useful information from the diagram above.
on clicking edit i get 3 options; create new resources, import existing resources or hand off to admin. I already have a bot in azure so i am using the import existing resource, so when i click next i get the json file. That's why i thought you want the  json file.
So please which of the options should i follow?

@Intelliteckai, to get to the publishing profile:

Click the 'Edit' button shown in the image above.
Select 'Import existing resources' and click 'Next'
Click into the frame that is housing the JSON
Copy and paste the JSON here ("redact" any sensitive data)

@Intelliteckai, I see that the "region" value is showing UK South when it should be uksouth. Can you update the profile and try and again to see if this is the source of the issue?

hi @stevkan i made this suggested change with your colleague Georgiana yesterday morning and the result it the same.
As this is a development environment and bot, I have decided to trash the build and start again.
It has taken too much time and I am under time pressures.
I have removed the bot and all related cognitive services, please close this ticket.


WIP Adding BGPCommunity CR API, controller, template and controller unit-test

Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>BGPCommunity Config Sample
BGP Full sample config
What this PR contains:

[x] update README with BGPCommunity object
[x] BGPCommunity API, controller and controller unit-test
[x] BGPCommunity template
[x] Add BGPAdvertisements to AddressPool CR
[x] BGP Full sample config
[x] update Bundle Manifest with BGPCommunity object and config

the plan not to use CR for BGPCommunities


Update code snippet in streaming-improve-page-performance.mdx

Description (required)
This pull request includes a small change to src/content/docs/en/recipes/streaming-improve-page-performance.mdx file. The change updated the code to personData.results[0].name.first to correctly access the first name of the first item within the results array. This change aligns with the actual structure of the returned data, allowing the code to work as intended.
This link shows both the current approach and the proposed one:

src/pages/index.astro contains the proposed working code.
src/pages/current.astro contains the current/original code throwing an error.

I checked all the other code snippets in this page and they all work fine.
Related issues & labels (optional)

Closes #
I could not find any.

Suggested label:
"code snippet update"

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
recipes/streaming-improve-page-performance.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Thank you so much! @fprotazio Nice catch!

I wonder if it would be necessary/beneficial to test those code snippets. Is there something already in practice?


FIX: _set_comp_prop() does not accept any argument.

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

Project coverage is 82.69%. Comparing base (0ee121c) to head (864a995).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #958   +/-   ##
=======================================
  Coverage   82.69%   82.69%
=======================================
  Files         160      160
  Lines       21117    21117
=======================================
  Hits        17462    17462
  Misses       3655     3655


[core][client] Stop importing URL from url

Made the changes requested in issue #15933
[core][client] Stop importing URL from "url"
Now that we're not trying for node 8 compatibility, we can simply use URL and URLSearchParams directly, eliminating the need for a browser and node version of this import.
Steps followed

Set up environment
created branch named stop-importing-from-url
Found instances of  from 'url' in core-client API
Removed imports and files url.ts, url.browser.ts
Updated package.json by removing url.browser.js entry
Ran rushx test:node and successfully passed all tests (trace below)

Found configuration in /home/suyash/open-source/azure-sdk-for-js/rush.json
Rush Multi-Project Build Tool 5.51.1 - https://rushjs.io
Node.js version is 10.19.0 (LTS)
Found configuration in /home/suyash/open-source/azure-sdk-for-js/rush.json
Executing: "npm run clean && tsc -p . && npm run unit-test:node && npm run integration-test:node"

<EMAIL_ADDRESS>clean /home/suyash/open-source/azure-sdk-for-js/sdk/core/core-client
rimraf dist dist-* temp types *.tgz *.log

<EMAIL_ADDRESS>unit-test:node /home/suyash/open-source/azure-sdk-for-js/sdk/core/core-client
cross-env TS_NODE_FILES=true mocha -r esm -r ts-node/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 50000 --full-trace  --exclude "test//browser/*.spec.ts" "test//*.spec.ts"

deserializationPolicy
✓ should not modify a request that has no request body mapper
✓ should parse a JSON response body
✓ should parse a JSON response body with a charset specified in Content-Type
✓ should parse a JSON response body with an uppercase Content-Type
✓ should parse a JSON response body with a missing Content-Type
parse(HttpOperationResponse)
✓ with no response headers or body
✓ with xml response body, application/xml content-type, but no operation spec
✓ with xml response body with child element with attributes and value, application/xml content-type, but no operation spec
✓ with xml response body, application/xml content-type, and operation spec for only String value
✓ with xml response body, application/xml content-type, and operation spec for only number value
✓ with xml response body, application/xml content-type, and operation spec for only headers
✓ with xml response body, application/atom+xml content-type, but no operation spec
✓ with xml property with attribute and value, application/atom+xml content-type, but no operation spec
✓ with xml property with attribute and value, my/weird-xml content-type, but no operation spec
✓ with service bus response body, application/atom+xml content-type, and no operationSpec
✓ should deserialize underscore xml element with custom xml char key
✓ with custom xml char key
✓ with default response headers
✓ with non default error response headers
✓ should throw when the response code is not defined in the operationSpec
✓ with non default complex error response
✓ with default error response body
serializationPolicy
serializeRequestBody()
✓ should serialize additional properties when the mapper is refd by className
✓ should serialize a JSON false request body
✓ should serialize a JSON null request body
✓ should serialize a JSON String request body
✓ should serialize a JSON String request body with namespace, ignoring namespace
✓ should serialize a JSON ByteArray request body
✓ should serialize a JSON ByteArray request body, ignoring xml properties
✓ should serialize a JSON Stream request body
✓ should serialize a JSON Stream request body
✓ should serialize an XML String request body
✓ should serialize an XML String request body, with namespace
✓ should serialize an XML ByteArray request body
✓ should serialize an XML Stream request body
✓ should serialize an XML Stream request body, with namespace
✓ should serialize an XML ByteArray request body with namespace and prefix
✓ should serialize an XML Composite request body
✓ should serialize a JSON Composite request body, ignoring XML metadata
✓ should serialize an XML Array request body with namespace and prefix
✓ should serialize a JSON Array request body, ignoring XML metadata
✓ should serialize an XML Array of composite elements, namespace and prefix
✓ should serialize an XML Composite request body with namespace and prefix
✓ should serialize an XML Dictionary request body
✓ should serialize an XML Dictionary request body, with namespace and prefix
✓ should serialize a JSON Dictionary request body, ignoring xml metadata
✓ should serialize an XML request body with custom xml char key
✓ should serialize a string send to a text/plain endpoint as just a string
✓ should serialize a string send with the mediaType 'text' as just a string
serializeHeaders()
✓ should respect customHeaders
Serializer
serialize
✓ should correctly serialize flattened properties
✓ should correctly serialize flattened properties when flattened constant is defined first
✓ should correctly serialize a string if the type is 'any'
✓ should correctly serialize an array if the type is 'any'
✓ should correctly serialize a string
✓ should correctly serialize a uuid
✓ should throw an error if the value is not a valid Uuid
✓ should correctly serialize a number
✓ should correctly serialize a boolean
✓ should correctly serialize an Enum
✓ should throw an error if the value is not valid for an Enum
✓ should correctly serialize a ByteArray Object
✓ should correctly serialize a Date Object
✓ should correctly serialize a Date object with max value
✓ should correctly serialize a Date object with max value and format UnixTime
✓ should correctly serialize a string in DateTimeRfc1123
✓ should correctly serialize an ISO 8601 duration
✓ should throw an error when given an invalid ISO 8601 duration
✓ should correctly serialize an array of primitives
✓ should correctly serialize an array of array of primitives
✓ should correctly serialize an array of array of object types
✓ should fail while serializing an array of array of "object" types when a null value is provided
✓ should correctly serialize an array of dictionary of primitives
✓ should correctly serialize a dictionary of primitives
✓ should correctly serialize a dictionary of array of primitives
✓ should correctly serialize a dictionary of dictionary of primitives
✓ should correctly serialize a composite type
✓ should correctly serialize object version of polymorphic discriminator
✓ should correctly serialize additionalProperties when the mapper knows that additional properties are allowed
✓ should allow null when required: true and nullable: true
✓ should not allow undefined when required: true and nullable: true
✓ should not allow null when required: true and nullable: false
✓ should not allow undefined when required: true and nullable: false
✓ should not allow null when required: true and nullable is undefined
✓ should not allow undefined when required: true and nullable is undefined
✓ should allow null when required: false and nullable: true
✓ should not allow null when required: false and nullable: false
✓ should allow null when required: false and nullable is undefined
✓ should allow undefined when required: false and nullable: true
✓ should allow undefined when required: false and nullable: false
✓ should allow undefined when required: false and nullable is undefined
deserialize
✓ should correctly deserialize a Date if the type is 'any'
✓ should correctly deserialize an array if the type is 'any'
✓ should correctly deserialize a uuid
✓ should correctly deserialize a composite type
✓ should correctly deserialize a pageable type without nextLink
✓ should correctly deserialize a pageable type with nextLink  first in mapper
✓ should correctly deserialize a pageable type with nextLink
✓ should correctly deserialize object version of polymorphic discriminator
✓ should correctly deserialize an array of array of object types
✓ should correctly deserialize without failing when encountering unrecognized discriminator
✓ should correctly deserialize additionalProperties when the mapper knows that additional properties are allowed
✓ should deserialize headerCollectionPrefix
composite type
✓ should be deserialized properly when polymorphicDiscriminator specified
✓ should be deserialized properly when polymorphicDiscriminator specified in nested property
✓ should be deserialized properly when polymorphicDiscriminator specified in the parent
✓ should be deserialized properly when responseBody is an empty string
✓ should be deserialized properly when item list wrapper is an empty string
polymorphic composite type array
✓ should be deserialized with child properties
✓ should be serialized with child properties
ServiceClient
✓ should serialize headerCollectionPrefix
✓ should call rawResponseCallback with the full response
✓ should serialize collection:csv query parameters
✓ should serialize collection:csv query parameters with commas & skipEncoding true
✓ should serialize collection:csv query parameters with commas
✓ should serialize collection:csv query parameters with undefined and null
✓ should serialize collection:tsv query parameters with undefined and null
✓ should serialize collection:ssv query parameters with undefined and null
✓ should serialize collection:multi query parameters
✓ should deserialize response bodies
✓ should deserialize array response as null if it is empty and nullable
✓ should deserialize array response as empty array if it is empty and not nullable
✓ should deserialize dictionary response as null if it is empty and nullable
✓ should deserialize dictionary response as empty if it is empty and not nullable
✓ should deserialize object response as null if it is empty and nullable
✓ should deserialize object response as empty if it is empty and not nullable
✓ should deserialize primitive response as null if it is empty and nullable
✓ should deserialize primitive response as undefined if it is empty and not nullable
✓ should deserialize a head request with no body even if the mapper says the body is nullable
✓ should deserialize error response headers
✓ should deserialize non-streaming default response
✓ should re-use the common instance of DefaultHttpClient
✓ should not allow insecure connection by default
✓ should allow insecure connection if configured via client options
✓ should allow insecure connection if configured via request options
✓ should wrap body when bodyWrapper is specified
✓ should catch the mandatory parameter missing error
✓ should catch the mandatory parameter missing error in the query
Auth scopes
✓ should throw if scopes contain an invalid url
✓ should throw is no scope or baseUri are defined
✓ should use baseUrl to build scope
✓ should use the provided scope
getOperationArgumentValueFromParameter()
✓ should return undefined when the parameter path isn't found in the operation arguments or service client
✓ should return undefined when the parameter path is found in the operation arguments but is undefined and doesn't have a default value
✓ should return null when the parameter path is null in the operation arguments but is undefined and doesn't have a default value
✓ should return the operation argument value when the parameter path is found in the operation arguments
✓ should return the service client value when the parameter path is found in the service client
✓ should return the operation argument value when the parameter path is found in both the operation arguments and the service client
✓ should return the default value when it is a constant and the parameter path doesn't exist in other places
✓ should return the default value when it is a constant and the parameter path exists in other places
✓ should return undefined when the parameter path isn't found in the operation arguments or the service client, the parameter is optional, and it has a default value
✓ should return the default value when the parameter path isn't found in the operation arguments or the service client, the parameter is required, and it has a default value
✓ should return the default value when the parameter path is partially found in the operation arguments, the parameter is required, and it has a default value
✓ should return undefined when the parameter path is partially found in the operation arguments, the parameter is optional, and it has a default value
✓ should return the default value when the parameter path is not found in the options operation arguments and it has a default value
✓ should return undefined when the parameter path is not found as a property on a parameter within the options operation arguments and it has a default value
✓ should return null when the parameter path is null in the operation arguments but is undefined and it has a default value
✓ should return the service client value when the parameter path is found in the service client and it has a default value
getRequestUrl
✓ should handle nested replacements
✓ should handle query parameters on the base url
✓ should not modify needlessly encoded query parameters
✓ should allow empty query parameter value
✓ should work with replacement having both path and search part
✓ should create url when there is no existing value
✓ should create url when the existing value is an array and the new value is not an array
✓ should create url when the existing value is an array and the new value is also the same array
✓ should create url when the existing value is an array and the new value is a different array
✓ should create url when the existing value is not an array and the new value is the same value
✓ should create url when the existing value is not an array and the new value is a different value
✓ should create url when the existing value is not an array and the new value is an array
170 passing (201ms)

<EMAIL_ADDRESS>integration-test:node /home/suyash/open-source/azure-sdk-for-js/sdk/core/core-client
echo skipped

skipped

Hi @deyaaeldeen, I fixed the linting issue, but now some tests are failing, more info here
As this is my first time contributing, I'm not sure what to do when a test fails because of dependency

Thank you for the contribution @SuyashSonawane!

Thanks, @ramya-rao-a, @deyaaeldeen for reviewing and merging my PR 🙌


Query:count must return int instead of string

QueryInterface::count declare integer result:
@return int number of records.

But Query::count implementation return string instead:
@return int|string number of records.

So, when using, PhpStorm says that type cast is redudant here:
function getCount(): int
{
    return (int)$this-query->count();
}

but without typecast result is Error:
Return value must be of type int, string returned
| ---------------- | ---
| Yii version      | <IP_ADDRESS>
| PHP version      |  8.0

OK, then return type of QueryInterface::count must be changed to actual int|string instead of int.

Yes, it should be compatible.

Is there any conditions, when Query::count return int ? :) Or it always return string, not just when big integer values. In MySQL never see there int values :)

In MySQL it's always string apparently, yes. I think in PostgreSQL it's int for example.

created pull request https://github.com/yiisoft/yii2/pull/18713

Closed via https://github.com/yiisoft/yii2/commit/e2b90b5f3eb6395f404112d115c285a6fde7d0e1


Fix remaining package/dir problems

There was some remaining package names/source file locations which was missed in previous PR's

looks like there are some issues in build.sbt

looks like there are some issues in build.sbt

Just fixed them


Android: The route is not created and is zoomed out by default on launch.

Great work! It seems to be working well on iOS, but I'm encountering the following issue with the example app on Android:
The route isn't being created between the source and destination, and the map is zoomed out by default. I've attached a screen recording for reference.
Is there anything additional that needs to be done beyond what's in the installation guide?

what react native version you are using and android studio version for android

what react native version you are using and android studio version for android

I'm running the example app of the project using React Native version 0.74.3.
For Android development, I'm using Android Studio Jellyfish | 2023.3.1 Patch 1, with the following details:
Build: #AI-233.14808.21.2331.11842104, built on May 14, 2024
Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
OS: macOS 14.5
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Metal Rendering: ON
Registry setting: ide.experimental.ui=true

Fixed in Release 0.4.1


T1 Completion

Please refer to the attached files.

confirmed:T1
account1:4RQVoXPui4aae9cA4pFVoPQNs667CCgJgG6nzP11HoF4BC8Y73
account2:3kvPnGZRfEj1VnnrpmGFQMXBDGtoveehsbRi8TQfinHaFKiNB3
DeviceDetails:verified

confirmed:T1
account1:4RQVoXPui4aae9cA4pFVoPQNs667CCgJgG6nzP11HoF4BC8Y73
account2:3kvPnGZRfEj1VnnrpmGFQMXBDGtoveehsbRi8TQfinHaFKiNB3
DeviceDetails:verified


da.compress fails when using cupy for condition array

da.compress fails when using  cupy for the condition array.
In [1]: import cupy as cp
import
In [2]: import dask.array as da

In [3]: rs = da.random.RandomState(RandomState=cp.random.RandomState)

In [4]: x = rs.randint(0, 3, size=(10, 10),
   ...:                chunks=(20, 5), dtype="uint8")

In [5]: da.compress(cp.asarray([True]), x, axis=0).compute()
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-5-89fea14f2e31> in <module>
----> 1 da.compress(cp.asarray([True]), x, axis=0).compute()

/datasets/bzaitlen/miniconda3/envs/20200501/lib/python3.7/site-packages/dask/array/routines.py in compress(condition, a, axis)
   1106
   1107     # Use `condition` to select along 1 dimension
-> 1108     a = a[tuple(condition if i == axis else slice(None) for i in range(a.ndim))]
   1109
   1110     return a

/datasets/bzaitlen/miniconda3/envs/20200501/lib/python3.7/site-packages/dask/array/core.py in __getitem__(self, index)
   1532         )
   1533
-> 1534         index2 = normalize_index(index, self.shape)
   1535
   1536         dependencies = {self.name}

/datasets/bzaitlen/miniconda3/envs/20200501/lib/python3.7/site-packages/dask/array/slicing.py in normalize_index(idx, shape)
    813     for i, d in zip(idx, none_shape):
    814         if d is not None:
--> 815             check_index(i, d)
    816     idx = tuple(map(sanitize_index, idx))
    817     idx = tuple(map(normalize_slice, idx, none_shape))

/datasets/bzaitlen/miniconda3/envs/20200501/lib/python3.7/site-packages/dask/array/slicing.py in check_index(ind, dimension)
    882     elif ind >= dimension:
    883         raise IndexError(
--> 884             "Index is not smaller than dimension %d >= %d" % (ind, dimension)
    885         )
    886

IndexError: Index is not smaller than dimension 1 >= 1

However,  da.compress succeeds if condition array is a list/numpy array
In [6]: da.compress([True], x, axis=0).compute()
Out[6]: array([[2, 0, 2, 2, 2, 0, 1, 0, 1, 2]], dtype=uint8)

Fix is probably changing a bit of logic in the check_index function around array_like behavior:
https://github.com/dask/dask/blob/666b53affac3ba475bd94c7ff4d29752bfa133de/dask/array/slicing.py#L865

Thanks @quasiben!

Fix is probably changing a bit of logic in the check_index function around array_like behavior

That seems like a good start to me : )

I started going down this path but there is a fair amount of np.asanyarray throughout the slicing code base.  This currently fails on CuPy objects -- I believe because of NEP 18 issues

@quasiben , do you think this will be fixed on the cupy side?

@quasiben , do you think this will be fixed on the cupy side?

No, but I think NEP35 can help here or some other type checking in the slicing code.
cc @pentschev

For awareness, this now works with https://github.com/dask/dask/pull/6738 and NumPy 1.20 (current dev branch):
In [1]: import cupy as cp, dask.array as da

In [2]: rs = da.random.RandomState(RandomState=cp.random.RandomState)

In [3]: x = rs.randint(0, 3, size=(10, 10), chunks=(20, 5), dtype="uint8")

In [4]: da.compress(cp.asarray([True]), x, axis=0).compute()
Out[4]: array([[0, 1, 2, 0, 0, 0, 0, 2, 2, 1]], dtype=uint8)

Fixed in #6738, this can be closed now.


*: tests, README on environment variables in etcdctl v3

For https://github.com/coreos/etcd/issues/6645.
etcdctl v3 does support environment variables to set flags.
We just need more tests and docs around it.
/cc  @xiang90 @heyitsanthony @bhouse

@xiang90 PTAL.
Fix map update issue. Works now.
Thanks!

lgtm

Thanks. Merging in greens.


A type word fix

Incorrectly change by refactoring of IDEA.

/run e2e

/run e2e

The e2e failed due to the missing docker command in Jenkins node H14, I'll ask the infra folks for help in Slack

Sure. This PR is easy, We could ignore for now.


GROOVY-4636: AST Browser does not show object initializer statements

+1, this looks good. Worth merging into 2_4_X before I cut the next release?

+1, this looks good. Worth merging into 2_4_X before I cut the next release?

Thanks for reviewing Paul.  I don't think it's worth trying to merge into 2_4_X before the release since it's just a minor improvement and not worth the risk of introducing any problems.

Thanks for reviewing Paul.  I don't think it's worth trying to merge into 2_4_X before the release since it's just a minor improvement and not worth the risk of introducing any problems.

With this script:
import java.util.concurrent.ConcurrentLinkedQueue

class Test extends GroovyTestCase {
    void test() {
        def ti = new TestInterceptor()
        ti.matchAll()
        println ti.matchers
    }
}

trait Interceptor {
    final Collection<String> matchers = new ConcurrentLinkedQueue<>()
    void matchAll() {
        matchers << 'foo'
    }
}

class TestInterceptor implements Interceptor {
}

I get this error when attempting to view the AST:
General error during canonicalization: Cannot cast object 'org.codehaus.groovy.ast.stmt.ExpressionStatement@52ae4578[expression:org.codehaus.groovy.ast.expr.MethodCallExpression@4f0a6b91[object: org.codehaus.groovy.ast.expr.ClassExpression@519179d9[type: Interceptor$Trait$Helper] method: ConstantExpression[$init$] arguments: org.codehaus.groovy.ast.expr.ArgumentListExpression@4b1cfd47[org.codehaus.groovy.ast.expr.VariableExpression@6b39f4d9[variable: this]]]]' with class 'org.codehaus.groovy.ast.stmt.ExpressionStatement' to class 'org.codehaus.groovy.ast.stmt.BlockStatement'

Should be fixed by PR #477.


Make icons in the installation section for the KA Lite page clickable

Quoted from a user who was installing KA Lite in our office: "I don't want to read, I just want to do it"
A gentleman who stopped by with me and @jamalex wanted to see the platform logo icons become clickable to start downloading the appropriate installer, as it was noticed that the first thing he did was try to click the platform logos:

Here are the current steps to install KA Lite:
Click this from the KA Lite page:

Then be directed to the documentation page for the various installer options:

And then be presented with instructions, and the actual link for downloading is embedded, not very apparent from the start:

One proposed solution by @jamalex was to add a wizard-like installation process that walks through, and more directly to the point of "doing" installation, rather than reading about it in the documentation.

The download page for Kolibri is currently being designed.  cc @khangmach some relevant info related to factor in.


hi,can you provide me with pointnet2_ cuda's source file?

I always fail to install with PIP in the same environment. As a result, I can't reproduce your experiment. I don't know you can provide a copy of pointnet2_ cuda's source file, thank you very much

Did you encounter any errors when installing pointnet2 by running
cd fpconv/pointnet2
python setup.py install
cd ../

Thank you for your reply. I did try this instruction according to readme at that time. It shows that VC 14.0 is missing, but I have already installed VC 2015. For pointnet2, this large package is already available on GitHub, but the pointnet2-cuda package invoked in pointnet2-untils can never be found. I see that you seem to have compiled this package in C. I don't know if you have Python compiled source files

Sorry, we have not tested the environment on Windows yet. If you are insterested in this package, you could refer to this repo sshaoshuai/Pointnet2.Pytorch for solution.

I will try to run this experiment on Linux . Thank you very much for your answer


Make ExpressionType.LITERAL as default for expression in decision's fluent API.

I partially did this in writer branch

@stlhrt I'm adding a reference to the pull request where partially has been done https://github.com/powerflows/powerflows-dmn/pull/64/files

Additional set default expression if not set by a user.


Refactor to use local vars for rank, world_size, group.

This is a simple refactor for the parameter partitioning code to use local vars instead of self.* variants.

Can one of the admins verify this patch?


How to avoid being subsumed into the mainline DHT?

If a mainline DHT node talks to us, we'll join that network.

Here's an idea: You could reject connections to nodes that don't use a certain prefix in their ID. You can control the node id in bittorrent-dht with the nodeId property.


role filtering not working

I'm using capistrano v3
I have 2 servers, one of them has two repositories to deploy and other has only one. So I set up capistrano for deployment by filtering roles
My staging.rb file has this configuration
# server-based syntax
# ======================
server '<IP_ADDRESS>', user: 'vagrant', roles: %w{api}
server '<IP_ADDRESS>', user: 'vagrant', roles: %w{admin}
server '<IP_ADDRESS>', user: 'vagrant', roles: %w{apg}

# role-based syntax
# ==================
role :api<EMAIL_ADDRESS>role :admin<EMAIL_ADDRESS>role :apg<EMAIL_ADDRESS>
# Custom SSH Options
# ==================
# You may pass any option but keep in mind that net/ssh understands a
# limited set of options, consult the Net::SSH documentation.
# http://net-ssh.github.io/net-ssh/classes/Net/SSH.html#method-c-start
#
# Global options
# --------------
 set :ssh_options, {
   keys: %w(/home/anyname/.ssh/id_rsa),
   forward_agent: true,
   auth_methods: %w(publickey),
   user: 'vagrant'
  }

I have added this task in deploy.rb
# config valid only for current version of Capistrano
lock '3.4.0'

set :branch, 'master'
# Default branch is :master
# ask :branch, `git rev-parse --abbrev-ref HEAD`.chomp

# Default deploy_to directory is /var/www/my_app_name
#set :deploy_to, '/var/www/{fetch(:application)}'
#ser :repo_path, ':Q'
# Default value for :scm is :git
set :scm, :git

# Default value for :format is :pretty
set :format, :pretty

# Default value for :log_level is :debug
# set :log_level, :debug

# Default value for :pty is false
set :pty, true

# Default value for :linked_files is []
#set :linked_files, fetch(:linked_files, []).push('composer.lock')

# Default value for linked_dirs is []
#set :linked_dirs, fetch(:linked_dirs, []).push('vendor')

# Default value for default_env is {}
# set :default_env, { path: "/opt/ruby/bin:$PATH" }

# Default value for keep_releases is 5
set :keep_releases, 5

namespace :deploy do

  after :restart, :clear_cache do
    on roles(:web), in: :groups, limit: 3, wait: 10 do
    # Here we can do anything such as:
    # within release_path do
    #   execute :rake, 'cache:clear'
    # end
   end
 end

  desc "select git url"
  task :select_repo do
    on roles(:all) do |host|
      if host.roles.include?(:apg)
        set :repo_url, 'git@bitbucket.org:something/repo1.git'
        set :application, 'webartists'
      elsif host.roles.include?(:api)
        set :repo_url, 'git@bitbucket.org:something/repo2.git'
        set :application, 'webapi'
        set :linked_files, fetch(:linked_files, []).push('composer.lock')
        set :linked_dirs, fetch(:linked_dirs, []).push('vendor')
      elsif host.roles.include?(:admin)
        set :repo_url, 'git@bitbucket.org:something/repo3.git'
        set :application, 'webadmin'
      end
    end
  end
  before :deploy, "deploy:select_repo"
end

when I run
$cap --roles=api staging deploy
$cap --roles=apg staging deploy
it successfully deploys repo in both cases
but when i run
$cap --roles=admin staging deploy
it starts to run api's role and start to deploy that instead of admin's.

I haven't had time to dig into this yet, but on first glance, I notice that you are declaring each of your servers twice, once using server and then again using role. Both syntaxes have the same effect; choose one or the other.
Not sure if that's related to your filtering problem, though.
Also, you've declared vagrant already in the server definitions, so no point in repeating that in ssh_options.

I had tried that way also, but same problem.

host.roles.include?(:api) will always return true for the <IP_ADDRESS> server, no matter what filter you use. The --roles filter just affects what hosts are executed; it doesn't actually remove any roles for those hosts.
Roles filtering is working fine; I don't consider this issue to be a bug.
--
GitHub issues is for feature requests or bug reports. Since this is more of a how-to question, I am closing this issue. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.

@mattbrictson the documentation at https://capistranorb.com/documentation/advanced-features/role-filtering/ clearly says that For example, if you filtered for servers with the web role, and a server had both the web and db role, only the web role would be executed on it..
But per our observations, when server has 2 roles (role1, role2) and we are using cap deploy ROLES=role1 on that server, both tasks for role1 and role2 will be executed.
Maybe that should be reflected in docs?

Hey, @neanton thanks for pointing this out! From my reading (this isn't a part of Capistrano I use often), what you just said is consistent with Matt's understanding.
Would you be willing to open a docs PR fixing the wording? The change would be here: https://github.com/capistrano/capistrano/blob/master/docs/documentation/advanced-features/role-filtering/index.markdown
Feel free to tag me in the PR so I notice it.
Thanks!


Update copy for tickets to reflect the education rate now includes teachers.

Hmm there are more references to Students Tickets down below though. Would you mind changing them too?

@hypha doh... will do. More haste, less speed. ;-)

See #24


Compile error: higher-ranked lifetime error, mismatched types,

Problem
Compile Error on recent rustc nightly
error: higher-ranked lifetime error par-stream-0.10.2/src/builder/mod.rs:232:13
error[E0308]: mismatched types par-stream-0.10.2/src/functions.rs:153:13
error: higher-ranked lifetime error /par-stream-0.10.2/src/functions.rs:575:13
Steps to reproduce
cargo new par-stream-bug
cd par-stream-bug
cargo add par-stream
cargo build
Expected Result
Expected to compile or print a message indicating a configuration problem
Environment
rustc -V
rustc 1.68.0-nightly (bdb07a8ec 2022-12-11
uname -a
Darwin andy-mac-m1.local 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101 arm64
Build Output
out.log

Hi,
Looks like it was an error with the nightly compiler I used.
On rustc 1.69.0-nightly (fdbc4329c 2023-02-22) it works without a problem.
So this issue can be closed


Update logs tests to match the new API subscribe behaviour

Fixes #569
Change-type: patch
Signed-off-by: Tim Perry<EMAIL_ADDRESS>

How about also cherrypicking the typing changes from https://github.com/resin-io/resin-sdk/pull/568 to get that in sooner than later?

@thgreasi Sure, done


[Theme request] Light Table

I've always been a fan of the Light Table theme and there are outdated themes inspired by it. (bubbleberry, noctilux) Would be nice to bring it back. :)

I took the time to create the Lighttable theme for doom. Check out the reddit post here.


Road to v1

What all needs to happen before the v1 milestone? I'd like to compile a list here (edit this comment), so that any contributors can have a list of tasks to choose from if they'd like to help. Perhaps the airbnb folks can get a project set up under the projects tab to track this better?

[ ] Document all teh things
[ ] Revisit installation steps, try to be dependency manager agnostic (#57, #57)
[ ] ... much more

@benkraus did you duplicate #57 on purpose? 😜
Could you provide some extra details regarding "much more"?
Are you already using the open source version of native-navigation in Airbnb already?
Thanks 😃

Is this still a priority for airbnb?


Game settings left panel height is off/wrong

Game settings left panel height is off/wrong

Fixed!


Plugin model for stacks

We should probably move to a plugin model  with hooky hooks for detect / get,  build and such... and only expose commands that are available in the context (no drush for symfony)

Not really a CLI issue, and superseded by other conversations