Updating an existing Application role doens't work

Using the following setup didn't work.
Configure existing Application Role to an application that runs in EC2 Instance with a policy with provided actions
module "firehose" {
  source                              = "fdmsantos/kinesis-firehose/aws"
  version                             = "x.x.x"
  name                                = "firehose-delivery-stream"
  destination                         = "s3" # or destination = "extended_s3"
  configure_existing_application_role = true
  application_role_name               = "application-role"
  create_application_role_policy      = true
  application_role_policy_actions     = [
    "firehose:PutRecord",
    "firehose:PutRecordBatch",
    "firehose:CreateDeliveryStream",
    "firehose:UpdateDestination"
  ]
}

I got an error name   = "${local.application_role_name}-policy" is null.

Thanks @schshmuel


main to live

Docs Build status updates of commit 9cd3411:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/bingads-13/guides/report-attributes-performance-statistics.md
:bulb:Suggestion

Details

Advertising/bingads-13/campaign-management-service/addadextensions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addadgroupcriterions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addadgroups.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addads.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addaudiences.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addbidstrategies.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addbudgets.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addcampaigncriterions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addcampaigns.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addconversiongoals.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addexperiments.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addimportjobs.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addkeywords.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addlabels.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addlistitemstosharedlist.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addnegativekeywordstoentities.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addsharedentity.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/adduettags.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/addvideos.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/appealeditorialrejections.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/applyofflineconversionadjustments.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/applyofflineconversions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/applyproductpartitionactions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/campaign-management-data-objects.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteadextensions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteadextensionsassociations.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteadgroupcriterions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteadgroups.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteads.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteaudiences.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletebidstrategies.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletebudgets.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletecampaigncriterions.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletecampaigns.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteexperiments.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deleteimportjobs.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletekeywords.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletelabelassociations.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletelabels.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletelistitemsfromsharedlist.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletemedia.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletenegativekeywordsfromentities.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletesharedentities.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletesharedentityassociations.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/deletevideos.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/getaccountproperties.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/getadextensionsassociations.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/getadextensionsbyids.md
:white_check_mark:Succeeded

Advertising/bingads-13/campaign-management-service/getadextensionseditorialreasons.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

Advertising/bingads-13/guides/report-attributes-performance-statistics.md

Line 191, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Following this article with VueJS (vue-CLI 3) doesn't work

After installing the NPM package and adding the script to my webpack entry point, when I run my website I get the following errors
ERROR  Failed to compile with 3 errors                                                                                9:23:50 PM
These dependencies were not found:

console in ./node_modules/diagnostic-channel-publishers/dist/src/console.pub.js
module in ./node_modules/diagnostic-channel/dist/src/channel.js, ./node_modules/diagnostic-channel/dist/src/patchRequire.js

To install them, you can run: npm install --save console module

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bc167975-264b-1130-76ad-594c8af26c25
Version Independent ID: 0d1e9d03-e326-fc03-a9ee-128bdc37da2d
Content: Monitor Node.js services with Azure Application Insights
Content Source: articles/application-insights/app-insights-nodejs.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@tommcclean Thanks for your feedback! We will investigate and update soon on it.

@tommcclean We were able to go through the steps mentioned in the documentation with Node.js and did not encounter any exceptions as such. The package dependencies could be due to a slight variation with Vue.js or the application config.
If you'd like to troubleshoot this further with us, please create a thread on MSDN:
https://social.msdn.microsoft.com/Forums/en-US/home?forum=ApplicationInsights&filter=alltypes&sort=lastpostdesc
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Updated the update of the login context to plain subscription ID

Description

Updated the update of the login context to plain subscription ID
The rational is that the current Get-AzContext only returns a maximum of 25 context objects. If an SP has access to more subscriptions, the login won't work and you may end up deploying into a subscription you did not intent to.

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change
Please delete options that are not relevant.

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

@SeSeicht


Document APIs using annotations instead of resource bundles

While the idea of managing API documentation using resource bundles has some advantages (most notably localization), it is not particularly convenient in practice. Maintaining code and documentation in separate files makes it difficult to keep them synchronized. This is compounded if multiple locales are supported.
Instead, a new Description annotation could be used to document APIs. This annotation would apply to service classes, methods, and parameters. The WebService class would be updated to look for occurrences of this annotation instead of resource bundle properties when generating API docs.
While it is possible to consider supporting localized descriptions using such an annotation, it is likely that most APIs (if they are documented at all) are using a single language to describe their endpoints. As such, multi-locale support would probably not be a priority for the initial implementation.

Additionally, this annotation could be used to describe data structures returned by a service, which is not currently supported by the properties-based approach.

This is done.


❓ Take raw photo without additional system effects

Question
Hi
I am going to develop an application that will take a photo to give some advices to clients using AI to make analization of photo. To implement this logic correctly I'll have to make raw photo without any system effects that improve the photos.
As I understood it's possible using native language (like Swift)
Is it possible to make the raw photos without any system effects using this library?
I'll really appreciate for you answer and explanation!!!
What I tried
No response
VisionCamera Version
2.15.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey do you want YUV, RGB or RAW (DNG) images?

Hi, thanks for you answer. I was on a vacation, so I couldn't answer before, but still this question is really important for me.
Right now I am not sure about an exact format of an image that we will use. If it's possible to get an image without any system optimizations and effects I will get this project to implement it using react native, that I really like
I would ask you to explain how can I get this image in RGB or RAW format of images. Or if it's possible to get it directly in JPEG format (without system effects)
I am grateful for your time and contribution for react native community!!!

Hey - yea I get what you're saying, but the only processing that's happening is in takePhoto() (RGB -> JPEG) and recordVideo() (YUV -> mp4/h264)
In a useFrameProcessor you get raw, unprocessed YUV frames in 4:2:0 8-bit format. Those are streamed in as the Camera is active.
Additionally, to take RAW (DNG) photos (takePhoto()), this should be possible soon with the new V3 API.

So as I understood right now it's possible to take a photo without any system effects and optimizations just using - takePhoto() to get it in JPEG format.
Okey, thank you for you answer! I wish a good trip through developing this amazing library)


SPIKE: Explore where to place crates with shared-use between HCCore and Networking.

[ ] CAS
[ ] EAV (metadata storage vs indexing)
[ ] Shared Types
[ ] libsodium
[ ] Logging
[ ] Lib3hProtocol

[ ] CAS

The CAS traits seem portable and abstract enough, as defined in holochain-rust/core_types/src/cas/*.
Holochain then has a cas_implementations crate which provides a file, in memory, and pickle db version. It would be straightforward to do one of the following:

move the traits and implementations into a XX crate, shared by holochain-rust and lib3h
move just the traits into XX crate, leave cas_implementations in core

then we pick one of the databases discussed here as an implementation. Probably one of rust-kv, sled, or sqlite3.

The XX crate can either be

a new, separate persistence crate available from crates.io (w/separate repo?)
embedded in existing lib3h repo as a module
embedded in existing lib3h repo  and a copy/fork of the code in holochain-rust, with decision of convergence or divergence from it deferred until a more strategic date

[ ] EAV (metadata storage vs indexing)

The EAV, as written currently, is not abstract enough for networking because the attribute is a enum very specific to subconscious metadata of holochain, such as links and crud. Also, the Value is typed as json string which may not be our best representation for networking.
The concept of an EAV however seems an appealing one and without some sort of meta layer on top of the CAS it is not terribly useful. Perhaps we implement an EAV trait more suitable to networking but possibly generalize/merge it in the future with holochain-core (for instance, we could just make the attribute and value generic type parameters with extensible serde requirements).
Will provide more thoughts and comments on this later- open to any suggestions in the meantime.


Updating the documentation

I added some features to help downloading the quiz and to run it easily.

Thanks for the features


Project Kanban

Kia Ora @RyleighStudy
Would you kindly set up the kanban board for the project and begin creating the tasks?

Has now been added


Commit in Gen. Journal Line give inconsistent payment import in the Journal.

We use the Gen. Journal a lot for import payments from the bank.
If the import stops with an Error the import will be commit and the import is inconsistent.
It is a risk the user posts the inconsistent journal.
It will be great if we had an opportunity to switch of the Commit temporary as SetSuppressCommit() for COD80 or COD90
This Code trigger the Commit in the Journal.

Debug stop with a Commit

Similar requests already completed

@AlexanderYakunin Hi Where can I find the Similar request that you closed this issue with?


Run Nexus IQ Scans Weekly and on Merges

Adds a job to run Nexus IQ scans each time code is merged, so that users
can investigate the reports and take action.
Signed-off-by: Trevor Bramwell<EMAIL_ADDRESS>

@bramwelt I note that the CLM pipelines are failing with this merge


ctlptl get takes a long time

When you have other entries in your kubeconfig which may no longer exist, ctlptl is taking a very long time to list the results.  We often have dirty kubeconfig files, so this is a bit of an odd user experience.
$ time ctlptl get
CURRENT   NAME                                               PRODUCT   AGE       REGISTRY
          foo   gke       unknown   none
          bar gke       unknown   none
          gca        gke       unknown   none
          tw    gke       unknown   none
*         kind-kind                                          kind      6m        localhost:56978
ctlptl get  0.13s user 0.15s system 0% cpu 1:00.46 total

I have four gke clusters in my kubeconfig, and I think two of them still exist.

thanks for the report! ya, i can repro, it looks like it just hangs if the cluster is dead... :(

@nicks I have not dug through the code, but I assume you are making a k8s API call?  What about just making an HTTP call to see if the endpoint is alive?  Real quick timeout?

ya, we're using the go k8s client. Want to figure out which HTTP call it's hanging on - in theory, it should already be doing that kind of check!

@nicks yes it does that check, but the HTTP client with client-go has a VERY long timeout, by default as design, you can override the timeout though.


Envoy only forwards raw JWT string instead of payload

I'm trying to forward the payload of a JWT token send through the Authorization header of a request. Below is the excerpt of my Envoy config in which I define the authorization rules.
http_filters:
  - name: envoy.filters.http.jwt_authn
    typed_config:
      "@type": "type.googleapis.com/envoy.extensions.filters.http.jwt_authn.v3.JwtAuthentication"
      providers:
        main_auth:
          forward_payload_header: "auth_user"
          forward: true
          from_headers:
            - name: Authorization
              value_prefix: "Bearer "
          issuer: example.com
          local_jwks:
            inline_string: '{"keys":[{"typ": "JWT", "kty":"oct","alg":"HS256","kid":"df","k":"<some-key>"}]}'
      rules:
        - match:
            prefix: /auth
        - match:
            prefix: /profile
          requires:
            provider_name: main_auth
  - name: envoy.filters.http.router

Expected Behavior
I expected the payload of the JWT to be forwarded because I set the forward_payload_header property to auth_user. But when I inspect the outgoing request after hitting the proxy the auth_user header does not hold the JWT payload but just the raw JWT string.
Below you can find the outgoing headers of a request after successfully validating the JWT with Envoy. The auth_user header hold just the raw JWT instead of it's payload.
{
  host: 'localhost:8000',
  authorization: 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0.gt0vMOBYVTGdl9yzrDtLNMid_Wtv6H8gD3cTfhG0EPA',
  'content-type': 'application/json',
  'user-agent': 'PostmanRuntime/7.28.4',
  accept: '*/*',
  'postman-token': 'b2cd1090-a515-41af-bc0f-bad69dbd338d',
  'accept-encoding': 'gzip, deflate, br',
  'content-length': '85',
  'x-forwarded-proto': 'http',
  'x-request-id': '913ce882-548d-4315-8f61-cdca5b152cce',
  auth_user: 'eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0',
  'x-envoy-expected-rq-timeout-ms': '15000',
  'x-envoy-original-path': '/profile/'
}

Logs
These are the logs of a request that pass the JWT validation but do not return the JWT payload:
[2021-12-10 23:13:44.422][21][debug][http] [source/common/http/conn_manager_impl.cc:274] [C1] new stream
[2021-12-10 23:13:44.422][21][debug][http] [source/common/http/conn_manager_impl.cc:867] [C1][S11017060318454850193] request headers complete (end_stream=false):

':authority', 'localhost:8000'
':path', '/profile/'
':method', 'PATCH'
'authorization', 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0.gt0vMOBYVTGdl9yzrDtLNMid_Wtv6H8gD3cTfhG0EPA'
'content-type', 'application/json'
'user-agent', 'PostmanRuntime/7.28.4'
'accept', '*/*'
'postman-token', '78b484c0-b2da-4e05-bd1a-c9fd3d42725b'
'accept-encoding', 'gzip, deflate, br'
'connection', 'keep-alive'
'content-length', '85'

[2021-12-10 23:13:44.422][21][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:158] Called Filter : setDecoderFilterCallbacks
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:53] Called Filter : decodeHeaders
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/matcher.cc:70] Prefix requirement '/profile' matched.
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/extractor.cc:249] extract authorizationBearer
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:133] main_auth: JWT authentication starts (allow_failed=false), tokens size=1
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:144] main_auth: startVerify: tokens size 1
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:157] main_auth: Parse Jwt eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0.gt0vMOBYVTGdl9yzrDtLNMid_Wtv6H8gD3cTfhG0EPA
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:167] main_auth: Verifying JWT token of issuer sessions.com
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:315] main_auth: JWT token verification completed with: OK
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:110] Jwt authentication completed with: OK
[2021-12-10 23:13:44.423][21][debug][router] [source/common/router/router.cc:457] [C1][S11017060318454850193] cluster 'profile' match for URL '/profile/'
[2021-12-10 23:13:44.423][21][debug][router] [source/common/router/router.cc:673] [C1][S11017060318454850193] router decoding headers:

':authority', 'localhost:8000'
':path', '/'
':method', 'PATCH'
':scheme', 'http'
'authorization', 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0.gt0vMOBYVTGdl9yzrDtLNMid_Wtv6H8gD3cTfhG0EPA'
'content-type', 'application/json'
'user-agent', 'PostmanRuntime/7.28.4'
'accept', '*/*'
'postman-token', '78b484c0-b2da-4e05-bd1a-c9fd3d42725b'
'accept-encoding', 'gzip, deflate, br'
'content-length', '85'
'x-forwarded-proto', 'http'
'x-request-id', '8e48f6a6-1b47-40e9-aab3-6e16d35649f9'
'auth_user', 'eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0'
'x-envoy-expected-rq-timeout-ms', '15000'
'x-envoy-original-path', '/profile/'

[2021-12-10 23:13:44.423][21][debug][pool] [source/common/http/conn_pool_base.cc:74] queueing stream due to no available connections
[2021-12-10 23:13:44.423][21][debug][pool] [source/common/conn_pool/conn_pool_base.cc:255] trying to create new connection
[2021-12-10 23:13:44.423][21][debug][pool] [source/common/conn_pool/conn_pool_base.cc:143] creating a new connection
[2021-12-10 23:13:44.423][21][debug][client] [source/common/http/codec_client.cc:60] [C5] connecting
[2021-12-10 23:13:44.423][21][debug][connection] [source/common/network/connection_impl.cc:890] [C5] connecting to <IP_ADDRESS>:3000
[2021-12-10 23:13:44.423][21][debug][connection] [source/common/network/connection_impl.cc:909] [C5] connection in progress
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:142] Called Filter : decodeData
[2021-12-10 23:13:44.423][21][debug][http] [source/common/http/filter_manager.cc:835] [C1][S11017060318454850193] request end stream
[2021-12-10 23:13:44.423][21][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:142] Called Filter : decodeData
[2021-12-10 23:13:44.423][21][debug][connection] [source/common/network/connection_impl.cc:672] [C5] connected
[2021-12-10 23:13:44.423][21][debug][client] [source/common/http/codec_client.cc:88] [C5] connected
[2021-12-10 23:13:44.423][21][debug][pool] [source/common/conn_pool/conn_pool_base.cc:293] [C5] attaching to next stream
[2021-12-10 23:13:44.423][21][debug][pool] [source/common/conn_pool/conn_pool_base.cc:176] [C5] creating stream
[2021-12-10 23:13:44.423][21][debug][router] [source/common/router/upstream_request.cc:416] [C1][S11017060318454850193] pool ready
[2021-12-10 23:13:44.647][21][debug][router] [source/common/router/router.cc:1285] [C1][S11017060318454850193] upstream headers complete: end_stream=false
[2021-12-10 23:13:44.647][21][debug][http] [source/common/http/conn_manager_impl.cc:1467] [C1][S11017060318454850193] encoding headers via codec (end_stream=false):

':status', '500'

'content-type', 'application/json; charset=utf-8'
'content-length', '114'
'date', 'Fri, 10 Dec 2021 23:13:44 GMT'
'x-envoy-upstream-service-time', '223'
'server', 'envoy'

[2021-12-10 23:13:44.647][21][debug][client] [source/common/http/codec_client.cc:129] [C5] response complete

Oh, I get it now. The payload is base64 encoded after validating the JWT.
eyJyb2xlIjoiVVNFUiIsImlzcyI6InNlc3Npb25zLmNvbSIsInN1YiI6IjYxYjNjNTJhNWQ0MGNkNjY2ZGFkYzcxZSIsImlhdCI6MTYzOTE3MTM3NX0 =
{"role":"USER","iss":"sessions.com","sub":"61b3c52a5d40cd666dadc71e","iat":1639171375}


pull request for e2e test at 01/07/2017 07:56:12

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


timing-support

Adding timing support. It will allow us to check how long each request takes to process.

Benchmark results (2x m4.xlarge machines, running with 4 server threads):
this branch
[ec2-user@ip-172-31-5-244 wrk]$ ./wrk -c 50 -t 50 -d 10s -s pipelined_get.lua  --latency http://<IP_ADDRESS>:8000 -- 64
Running 10s test @ http://<IP_ADDRESS>:8000
  50 threads and 50 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.63ms    1.92ms  45.18ms   72.67%
    Req/Sec    13.60k     3.79k   34.26k    71.63%
  Latency Distribution
     50%    2.61ms
     75%    4.03ms
     90%    6.82ms
     99%    0.00us
  6834322 requests in 10.10s, 1.12GB read
Requests/sec: 676703.33
Transfer/sec:    113.58MB
[ec2-user@ip-172-31-5-244 wrk]$ ./wrk -c 50 -t 50 -d 10s -s pipelined_get.lua  --latency http://<IP_ADDRESS>:8000 -- 64
unable to connect to <IP_ADDRESS>:8000 Connection refused
[ec2-user@ip-172-31-5-244 wrk]$ ./wrk -c 50 -t 50 -d 10s -s pipelined_get.lua  --latency http://<IP_ADDRESS>:8000 -- 64
Running 10s test @ http://<IP_ADDRESS>:8000
  50 threads and 50 connections

master
[ec2-user@ip-172-31-5-244 wrk]$ ./wrk -c 50 -t 50 -d 10s -s pipelined_get.lua  --latency http://<IP_ADDRESS>:8000 -- 64
Running 10s test @ http://<IP_ADDRESS>:8000
  50 threads and 50 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.42ms    1.49ms  40.74ms   59.96%
    Req/Sec    14.47k     4.59k   49.79k    71.03%
  Latency Distribution
     50%    2.50ms
     75%    4.04ms
     90%    5.65ms
     99%    0.00us
  7266080 requests in 10.10s, 1.19GB read
Requests/sec: 719523.29
Transfer/sec:    120.77MB

Yeah, I was concerned getting wallclock every request or 2x per request would be expensive. That was my motivation to writing the HTTP partial response cache to avoid having to call the wallclock every request to get the date/time header value.

This can be replaced by #96

Closing since #96 replaces this.


Dns

Dns changes for sync call

@kanchankanchan I can help you in fixing merge conflicts in following files,
src/mme-app/conf/mme.json
src/mme-app/json_config.c
src/mme-app/main.cpp
src/s11/handlers/create_session_handler.c
Let me know if you need any help. Would be good if this is fixed quickly.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I am closing the pull request and will raise new one soon.
Merge conflicts got resolved but somehow after taking pull of code compilation was break.

@kanchankanchan can you please fix the compilation and raise the request ?


chapter 15, how to change the matcher

I hope to not protect the / and /dashboard, but protect the /protected
and keep the login and logout.
It should change the follow:
matcher: ['/((?!api|_next/static|_next/image|.\.png$).)'],
as I hope to demo the basic function and not login at first.
``import NextAuth from 'next-auth';
import { authConfig } from './auth.config';
export default NextAuth(authConfig).auth;
export const config = {
// https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher
matcher: ['/((?!api|_next/static|_next/image|.\.png$).)'],
};

Hey @liwenz, so I understand, are you trying to protect other routes?


Lane IDs are now overridden, making 2.0.1 a BREAKING release

The release of 2.0.1 includes a breaking change: The id property is now overridden for new lanes, meaning we can't specific our own lane ids.
I think the change is on line 45, here:
https://github.com/rcdexta/react-trello/blob/65d8dae2e6189c52701b755bd4e41bcb850b4437/src/helpers/LaneHelper.js#L44-L47
However, I'm not sure why that's affecting lanes passed in by the data prop as of yet.
I can confirm however, that the specified lane ids are not present in version 2.0.1.
<ReactTrello
    draggable
    data={{
        lanes: [
            { id: 'my-first-lane' },
            { id: 'my-second-lane' },
            { id: 'my-third-lane' }
        ]
    }}

    handleLaneDragEnd={console.log}
/>

Resulting console output after dragging a lane:

Expected console output should be my-first-lane 2 [Object object]

Weirdly, handleDragEnd is unaffected, passing the ids I specified for the sourceLaneId & targetLaneId parameters.

@G-Rath I wonder if card IDs being overridden upon creation (see #117) is due to the same issue?

@CodyFitzpatrick The issue is relating to handleLaneDragEnd: It's now handleLaneDragEnd(removedIndex, addedIndex, payload) instead of handleLaneDragEnd(payload.id, addedIndex).
Give me a few minutes to refactor this issue, then we'll talk 😉

Sounds good! Looks like new card IDs are indeed being overwritten in react-trello/src/components/Lane.js with the same ID generator function. Here's a snippet of the culprit:

@G-Rath Sounds good! Looks like new card IDs are indeed also being overwritten in react-trello/src/components/Lane.js with the same ID generator function, uuidv1(). Here's a snippet of the culprit:
addNewCard = params => {
    const laneId = this.props.id
    const id = uuidv1()
    this.hideEditableCard()
    let card = {...params, id}
    this.props.actions.addCard({laneId, card})
    this.props.onCardAdd(card, laneId)
}

As I showed with the original snippet, this'll happen when adding new lanes too:
https://github.com/rcdexta/react-trello/blob/65d8dae2e6189c52701b755bd4e41bcb850b4437/src/helpers/LaneHelper.js#L44-L47
I'll create a new issue for lane ids. I think this library could gain a lot from a bit of clean up in regards to this sort of thing, but I'm just waiting for the authors feedback before spamming the repo with PRs :joy:
Depending on his response, I may start my own fork, as this package is a core dependency of a work project 😕

This is solved as of v2.0.3


2 separate Date-pickers without using Range

Expected behavior
Hi everyone, This is probably a noob question but I'm trying to use 2 separate date pickers, and when the startDatePicker's date is selected the endDatePicker should have a startDate option with the date of the selected startDatePicker and then same with endDate it should then limit the EndDate.
Datepicker version used
ex. 1.6.1.

Hi, You can easily do so with the beforeShowDay callback.
Here's a snippet: https://jsfiddle.net/azaret/25bqa6ho/


[BUG] Save button does not revert state to not editing for useEditableTable

Describe the bug
When using an editable table, the save button does not close the editing state of the row
Steps To Reproduce

Go to this example
Click edit
change the text field
click save
save button does not go away

Expected behavior
edit state should be reverted to false
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
No response

Hello, we will discuss with the core team the feasibility of automatically performing this task by "useEditableTable".
but meanwhile, you can manually close the row after the mutation is a success
useEditableTable({
        onMutationSuccess: () => {
            setEditId(undefined);
        },
});

full example: https://codesandbox.io/s/sweet-haibt-2y9zbj?file=/src/pages/posts/list.tsx:534-562

Hi @aidanlloydtucker, I opened PR for this bug https://github.com/refinedev/refine/pull/4278
Thanks for the issue 👍


Add key marker for paginated version info calls

Hello s3fs maintainers! I ran into the same issue raised in #330. It pops up when I try to use object_version_info for a prefix with more versions than can fit in a single API response. This change resolves that issue.
Long-time happy user / first-time contributor here... so let me know if you have any questions/comments/etc about the change. Thanks!

Thanks for the PR!
Do you know how many entries it would take to trigger the pagination - would it be reasonable to write a test against this?

Hmm, good call :). By default it's 1000, but we should be able to force a lower number for testing. At a glance, I'm thinking we can add something like fs.req_kw['MaxKeys'] = 1 inside the test? I'll take a look.

Ah sorry, scratch that. There's already a test listing 1200 versions of an object, but it seems to pass as-is because of differences between moto and s3. So without hitting a live s3 endpoint I'm not sure how to effectively test the change.

cc @mariusvniekerk

Yeah 1000 is the default limit


Use black and isort

Codecov Report

Merging #374 (c3ec63f) into develop (5e7652a) will not change coverage.
The diff coverage is 55.00%.

@@           Coverage Diff            @@
##           develop     #374   +/-   ##
========================================
  Coverage    80.59%   80.59%
========================================
  Files            6        6
  Lines          737      737
========================================
  Hits           594      594
  Misses         143      143

Impacted Files
Coverage Δ

argcomplete/_check_console_script.py
0.00% <0.00%> (ø)

argcomplete/completers.py
87.50% <ø> (ø)

argcomplete/__init__.py
91.28% <91.66%> (ø)

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


sqlite_master

Hi what is the best way to do queries on SQLite_master? I have tried the Query(...) but cant seem to get it to recognise SQLite_master as a table.
Many thanks

Hi, I'm sorry but I don't know.
Perhaps someone else does?

You can use
[Table("sqlite_master")]
public class SqliteSchemaObject
{
public string type { get; set; }
public string name { get; set; }
public string tbl_name { get; set; }
public int rootpage { get; set; }
public string sql { get; set; }
}
As the class that represents the schema objects (You can use the Column attribute to have a different naming convention)
Then you can get all the objects in the database using:
db.Table()


[Bug]: Can't Play Next an album

🔍 Have you ensured you are using the latest versions of Spotify, Spicetify, and the extension?

[X] I have confirmed that I am using the latest versions.

🔍 Have you checked for an existing issue?

[X] I have checked existing issues, both open and closed.

🔍 Have you reviewed pinned issues?

[X] I have reviewed the pinned issues.

Select the relevant extension for this bug report.
Play Next
ℹ System Information
Spotify for Windows <IP_ADDRESS>5.gcc39d911
Spicetify V2.38.4
Extensions: playNextwrapper.js, savePlaylistWrapper.js,volumePercentageWrapper.js, hidePodcasts.js, cacheCleaner.js, QueueTime.js
Custom Apps: marketplace, lyrics-plus

📝 Bug Description
As detailed on the title, before we could Play Next any album, but we can't anymore. Im reporting from both latest versions on Windows PC but, it's been happening for at least 2 months now.
📸 Screenshots

Should be fixed now @megatron008
Thanks for raising the issue!

Should be fixed now @megatron008 Thanks for raising the issue!

Yes it is fixed! I just checked. Thank you for your amazing extension!


revert back to us-eas1-1 region

rh-pre-commit.version: 2.1.0
rh-pre-commit.check-secrets: ENABLED

/retest

/retest

/test test-pipeline-service-upgrade-ocp-414


OraOperator incorrectly reporting Unhealthy status with <IP_ADDRESS>.05 on OKE

% kubectl get singleinstancedatabase/freedb-livelabs -n oracle-namespace
NAME              EDITION   STATUS      ROLE          VERSION       CONNECT STR   TCPS CONNECT STR   OEM EXPRESS URL
freedb-livelabs   Free      Unhealthy   Unavailable   Unavailable   Unavailable   Unavailable        Unavailable
% kubectl describe singleinstancedatabase/freedb-livelabs -n oracle-namespace
Events:
Type    Reason              Age                From                    Message

Normal  Database Pending    22m (x7 over 24m)  SingleInstanceDatabase  waiting for a pod to get to running state
Normal  Database Unhealthy  21m (x6 over 22m)  SingleInstanceDatabase  datafiles exists
% kubectl logs pods/freedb-livelabs-xfcba -n oracle-namespace
Defaulted container "freedb-livelabs" out of: freedb-livelabs, init-prebuiltdb (init)
Starting Oracle Net Listener.
Oracle Net Listener started.
Starting Oracle Database instance FREE.
Oracle Database instance FREE started.
The Oracle base remains unchanged with value /opt/oracle
SQL*Plus: Release <IP_ADDRESS>.0 - Production on Thu May 30 12:36:18 2024
Version <IP_ADDRESS>.05
SQL> Disconnected from Oracle Database 23ai Free Release <IP_ADDRESS>.0 - Develop, Learn, and Run for Free
Version <IP_ADDRESS>.05
The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
% kubectl exec -it pods/freedb-livelabs-xfcba -n oracle-namespace -- sqlplus system/LiveLabs1@FREE
Defaulted container "freedb-livelabs" out of: freedb-livelabs, init-prebuiltdb (init)
SQL*Plus: Release <IP_ADDRESS>.0 - Production on Thu May 30 13:12:04 2024
Version <IP_ADDRESS>.05
Copyright (c) 1982, 2024, Oracle.  All rights reserved.
Last Successful login time: Wed Apr 24 2024 21:23:00 +00:00
Connected to:
Oracle Database 23ai Free Release <IP_ADDRESS>.0 - Develop, Learn, and Run for Free
Version <IP_ADDRESS>.05
SQL> select INSTANCE_NAME, HOST_NAME, VERSION_FULL, EDITION from v$instance;
INSTANCE_NAME	 HOST_NAME							  VERSION_FULL	    EDITION

FREE		 freedb-livelabs-xfcba						  <IP_ADDRESS>.05	    FREE

@raekins have you applied the RBAC yamls in rbac/ folder?

Hi Yunus, I was using the cluster-role-binding.yaml to manage all namespaces, will try using a namespace scoped deployment.
Thanks

@raekins sure. But in either case SIDB needs
https://github.com/oracle/oracle-database-operator/blob/main/rbac/node-rbac.yaml

@raekins is the issue resolved once you apply https://github.com/oracle/oracle-database-operator/blob/main/rbac/node-rbac.yaml.
Note :- If you are using k8s native nodeport service for the singleinstancedatabase resource, it is mandatory to apply the above file.....because we need node ip for set the connect strings

Yes, all now resolved, was a fixed by applying dependencies.
rekins@rekins--Mac14 ~ % kubectl get singleinstancedatabase freedb-livelabs -n oracle23ai -o "jsonpath={.status.status}"
Healthy%

thanks you for your assistance


Gapless doesn't work

Due to what seems to be a huge download/load/buffer time for tracks, playing a gapless album (like Dark Side of the Moon) just doesn't work.
tidal-cli 2.0.4 (release version)
Ubuntu 18.04.1

I also love DSOTM and know that not being able to hear it as a whole thing isn't great, but I cannot think of any way I could load the next songs while the current plays, cause playback is on the side of mpv which, as I'm concerned, doesn't support it.


[SPARK-41256][CONNECT] Implement DataFrame.withColumn(s)

What changes were proposed in this pull request?

Implement DataFrame.withColumn(s).
Why are the changes needed?

API coverage
Does this PR introduce any user-facing change?

NO
How was this patch tested?

UT

@zhengruifeng @grundprinzip @cloud-fan @HyukjinKwon

I ended up with

Change WithColumns proto to use a list of name/columns.
I didn't choose to use Alias which is not that ideal for this case. I just use a small message to wrap the name/expression pair.
I follow current API to just throw exception when there are duplicated names.

@amaliujia why is using Alias not ideal for this case? It seems to fit the bill rather nicely.

@hvanhovell
Well the simple answer is WithColumn API's parameters are not named Alias.
But my longer thought is:
Alias has its defined semantics (including those fields). That semantics does not match what this PR looks for. Alias happens to have two fields that can help this PR (and Alias has one more field which is metadata for the its semantics).
I think it's a good to avoid using a message only because the fields type fit but the semantics does not match.  In principle,   The message semantics can evolve so over-using it will cause trouble. Just a bad example: one day we will decide that Alias should only accept an alias which type is float. Then those places that truly deal with Alias which makes sense. But our WithColumns will not be compatible because we happen to use Alias due to same field type but not match with its semantics.
So we re-use a message because of the matching semantics. If the semantics match but even there is a lack of capability, we can even extend the message by adding more fields etc. to help.  But it does not work vice verse.

@amaliujia the semantics of Alias and the name + expression are 100% the same. Both are named expressions, and at the end of the day withColumns will produce a Project using exactly those Alias expressions. The replacement/appending semantics of withColumn does not change anything here. Come to thing of it, having metadata here would actually make sense.
There is no way we are ever going to change Alias, this has been in databases for the last 50+ years. However, let's entertain the idea of us changing Alias, you can solve those problems with proper versioning and a breaking change process (we are going to need both at some point in the not so far away future). I am assuming you are changing Alias in the connect protocol, in that case such a breaking change probably means you will introduce a new expression.

@hvanhovell
I see you are thinking better now.
When I say different semantics, what I mean is at the DataFrame API surface (which is WithColumn). But if you say that at the end, in implementation those parameters are converted to Alias, which is right and at that moment the semantics match.
I don't have strong opinion here. Probably I will just change to use Alias.

I pushed a commit to use Alias but now I know why I have been having a sense of the different semantics:
  message Alias {
    Expression expr = 1;
    repeated string name = 2;
    // Alias metadata expressed as a JSON map.
    optional string metadata = 3;
  }

Alias has a list of name parts while WithColumn assumes one name part (a single string). Right now I just assume there is one name part passed from the Alias messages.

What is the reason for alias to have a multi part identifier? Does this actually make sense? Maybe we need to fix this as well.

hmm well @grundprinzip maybe you should tell us why it is repeated names :) https://github.com/apache/spark/commit/0f7eaeee6445aaf05310229bdec22f6953113f2e

By reading the commit https://github.com/apache/spark/commit/0f7eaeee6445aaf05310229bdec22f6953113f2e honestly I am not sure if Python side has a valid usage for Alias or not.
Maybe @cloud-fan do you recall we support multiple name parts for alias?

Good point! The reason for making it repeated was that if you have a function that you alias the function might produce multiple columns.
So I think the repeated is fine here and we should probably update the documentation of the proto to leave a trace so that we don't have to do a history search all the time.
The key part is that for scalar columns just one value is present.

My two cents:
In general, I agree with @amaliujia that we should not reuse a proto message with a mismatched semantic. But we should define the semantic by the proto message itself, not the DataFrame API. For a WithColumns operator, I think using Alias matches its semantic (add/replace columns with the provided expressions according to the provided names). The problem I see here is Alias can contain a list of alias names. We should either document it clearly that WithColumns can only use Alias with a single alias name, or introduce MultiAlias like what catalyst does.

I don't think anyone is disputing that reusing messages in different contexts just because the fields are identical is a bad idea.
One thing I'm wondering and I'm sorry that I didn't bring this up earlier is if we shouldn't implement WithColum using a Projection? The main difference I see is that to make projection work we have to resolve the schema to be able to append columns.
Maybe we can do Project[*, add columns]?

Maybe we can do Project[*, add columns]?

The semantic is different. df.withColumns can replace columns if the given name(s) conflict with the existing columns. Project[*, added columns] can't do it.

@cloud-fan thanks. I will stay on the Alias probably try to document it clearly for the WithColumn

Maybe we can do Project[*, add columns]?

The semantic is different. df.withColumns can replace columns if the given name(s) conflict with the existing columns. Project[*, added columns] can't do it.

Yes Project[*, added columns] cant do that, but you're able to replace the columns on the client side by resolving the schema first. What I'm trying to figure out is where we draw the line between adding another input relation type to avoid become a different Py4j.

Hmmmm it's a trade off between proto number and implementation complexity. I personally choose proto because there are more than 1 client. The implementation complexity will need to times N.

@grundprinzip IMO we should go for a server side implementation of withColumns for the following reasons:

Connect in its current form is lazy. Going the project route would violate that, because we would need to execute a RPC to get the schema. This in itself is not a problem, however when the schema of the table changes you might end up with missing columns or errors.
Code reuse. As @amaliujia mentioned, we are likely to have withColumns in multiple clients (scala will definitely have this as well). I want to drive home the point here that withColumns has some non-trivial name resolution logic (with name parsing and a bunch of other things), I think it is better to do it once, and have a consistent user experience.
Customers love to stack withColumns on top of each other (e.g. do analysis of all columns in a dataframe in a loop). I would love to move this into the analyzer at some point. That should make it quite a bit faster.

Taking a step back I think we need some decision framework on where to implement what. In this case the logic is non-trivial and I think it should belong on the sever.

Rebased and tried to address existing comments

Thanks for the good discussion and the clear commit message.

@amaliujia  It would be great if you can update the commit message with a bit more context on what proto fields were added and why it's implemented the way it is as a summary of our discussion here. So when someone goes through the history of the commits they can see the decision making process.

@grundprinzip the commit message eventually is the PR description so I updated there.
Maybe in the future we need a developer doc to explain some of our current proto design decisions.

thanks, merging to master!


Allow running session notebooks

Seperate command, as they will start a GDS session instance as part of the notebook.
Other notebooks take a neo4j instance with GDS installed as a setup.

 [🍓] Client documentation

 [🍓] Integration tests for Aura API


Handling of additional trainable params from Hub utils

@younesbelkada
Now that #39 has been merged, I wanted to focus on #44 and #45.
As you can see here, after wrapping a base model with LoraModel for image classification fine-tuning, I am still having to
for param in lora_model.classifier.parameters():
    param.requires_grad = True

I am aware that if we fix the internal task types of LoraConfig, we wouldn't need to do this. But on the other hand, this goes on to show the flexibility of PEFT, isn't it?
In this case, would the Hub utilities introduced in #39 take care of the additional trainable parameters?

Hello Sayak, that case isn't handled yet, it would require changes to the LoraConfig to accept modules_to_save param in which users can specify additional trainable layers apart from lora layers. Will raise PR for same in sometime

Yes, let's do that!

Hello, the above PR should resolve this issue.

Let me try to rework my example and see if everything works as expected.

Shared the example notebook offline with you


make nitro-cli fails on Ubuntu 18.04

When following the build instructions, I get an error.
I've isolated it to the .build_container target, and the error I get when I run make nitro-cli:
Step 23/27 : RUN  source $HOME/.cargo/env &&    cargo install cargo-audit --version ^0.12
 ---> Running in 02e0cbf2c49d
    Updating crates.io index
 Downloading crates ...
  Downloaded cargo-audit v0.12.1
  Installing cargo-audit v0.12.1
 Downloading crates ...
  Downloaded thiserror v1.0.23
  Downloaded rustsec v0.20.1
  Downloaded gumdrop v0.7.0
  Downloaded lazy_static v1.4.0
  Downloaded serde v1.0.123
  Downloaded home v0.5.3
  Downloaded smol_str v0.1.16
  Downloaded abscissa_core v0.5.2
  Downloaded serde_json v1.0.61
  Downloaded gumdrop_derive v0.7.0
  Downloaded chrono v0.4.19
  Downloaded thiserror-impl v1.0.23
  Downloaded serde_derive v1.0.123
  Downloaded toml v0.5.8
  Downloaded semver v0.9.0
  Downloaded cvss v1.0.1
  Downloaded platforms v0.2.1
  Downloaded semver-parser v0.9.0
  Downloaded cargo-lock v4.0.1
  Downloaded crates-index v0.14.3
  Downloaded git2 v0.13.17
  Downloaded num-traits v0.2.14
  Downloaded once_cell v1.5.2
  Downloaded canonical-path v2.0.2
  Downloaded signal-hook v0.1.17
  Downloaded secrecy v0.6.0
  Downloaded backtrace v0.3.56
  Downloaded libc v0.2.83
  Downloaded tracing v0.1.22
  Downloaded regex v1.4.3
  Downloaded semver-parser v0.7.0
  Downloaded ryu v1.0.5
  Downloaded termcolor v1.1.2
  Downloaded time v0.1.44
  Downloaded quote v1.0.8
  Downloaded proc-macro2 v1.0.24
  Downloaded syn v1.0.60
  Downloaded tracing-log v0.1.1
  Downloaded color-backtrace v0.3.0
  Downloaded itoa v0.4.7
  Downloaded tracing-subscriber v0.1.6
  Downloaded num-integer v0.1.44
  Downloaded wait-timeout v0.2.0
  Downloaded generational-arena v0.2.8
  Downloaded abscissa_derive v0.5.0
  Downloaded object v0.23.0
  Downloaded autocfg v1.0.1
  Downloaded zeroize v1.2.0
  Downloaded memchr v2.3.4
  Downloaded tracing-core v0.1.17
  Downloaded matchers v0.0.1
  Downloaded ansi_term v0.11.0
  Downloaded tracing-attributes v0.1.11
  Downloaded rustc-demangle v0.1.18
  Downloaded miniz_oxide v0.4.3
  Downloaded regex-syntax v0.6.22
  Downloaded pin-project-lite v0.2.4
  Downloaded error-chain v0.12.4
  Downloaded petgraph v0.5.1
  Downloaded owning_ref v0.4.1
  Downloaded glob v0.3.0
  Downloaded cfg-if v1.0.0
  Downloaded addr2line v0.14.1
  Downloaded signal-hook-registry v1.3.0
  Downloaded bitflags v1.2.1
  Downloaded libgit2-sys v0.12.18+1.1.0
  Downloaded log v0.4.14
  Downloaded smallvec v0.6.14
  Downloaded aho-corasick v0.7.15
  Downloaded thread_local v1.1.2
  Downloaded atty v0.2.14
  Downloaded unicode-xid v0.2.1
  Downloaded openssl-probe v0.1.2
  Downloaded openssl-sys v0.9.60
  Downloaded url v2.2.0
  Downloaded ident_case v1.0.1
  Downloaded stable_deref_trait v1.2.0
  Downloaded regex-automata v0.1.9
  Downloaded cc v1.0.66
  Downloaded version_check v0.9.2
  Downloaded cfg-if v0.1.10
  Downloaded gimli v0.23.0
  Downloaded pkg-config v0.3.19
  Downloaded libssh2-sys v0.2.20
  Downloaded indexmap v1.6.1
  Downloaded libz-sys v1.1.2
  Downloaded maybe-uninit v2.0.0
  Downloaded fixedbitset v0.2.0
  Downloaded adler v0.2.3
  Downloaded darling v0.10.2
  Downloaded synstructure v0.12.4
  Downloaded percent-encoding v2.1.0
  Downloaded hashbrown v0.9.1
  Downloaded form_urlencoded v1.0.0
  Downloaded idna v0.2.0
  Downloaded jobserver v0.1.21
  Downloaded matches v0.1.8
  Downloaded darling_core v0.10.2
  Downloaded darling_macro v0.10.2
  Downloaded unicode-bidi v0.3.4
  Downloaded unicode-normalization v0.1.16
  Downloaded fnv v1.0.7
  Downloaded strsim v0.9.3
  Downloaded byteorder v1.4.2
  Downloaded tinyvec v1.1.1
  Downloaded tinyvec_macros v0.1.0
   Compiling proc-macro2 v1.0.24
   Compiling autocfg v1.0.1
   Compiling libc v0.2.83
   Compiling unicode-xid v0.2.1
   Compiling syn v1.0.60
   Compiling serde_derive v1.0.123
   Compiling serde v1.0.123
   Compiling pkg-config v0.3.19
   Compiling cfg-if v1.0.0
   Compiling log v0.4.14
   Compiling matches v0.1.8
   Compiling tinyvec_macros v0.1.0
   Compiling gimli v0.23.0
   Compiling adler v0.2.3
   Compiling memchr v2.3.4
   Compiling object v0.23.0
   Compiling rustc-demangle v0.1.18
   Compiling percent-encoding v2.1.0
error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:162:41
    |
162 |             [0x7f, b'E', b'L', b'F', 1, ..] => FileKind::Elf32,
    |                                         ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:164:41
    |
164 |             [0x7f, b'E', b'L', b'F', 2, ..] => FileKind::Elf64,
    |                                         ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:166:38
    |
166 |             [0xfe, 0xed, 0xfa, 0xce, ..]
    |                                      ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:167:40
    |
167 |             | [0xce, 0xfa, 0xed, 0xfe, ..] => FileKind::MachO32,
    |                                        ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:169:40
    |
169 |             | [0xfe, 0xed, 0xfa, 0xcf, ..]
    |                                        ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:170:40
    |
170 |             | [0xcf, 0xfa, 0xed, 0xfe, ..] => FileKind::MachO64,
    |                                        ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:172:38
    |
172 |             [0xca, 0xfe, 0xba, 0xbe, ..] => FileKind::MachOFat32,
    |                                      ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:174:38
    |
174 |             [0xca, 0xfe, 0xba, 0xbf, ..] => FileKind::MachOFat64,
    |                                      ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:178:26
    |
178 |             [b'M', b'Z', ..] => {
    |                          ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:194:26
    |
194 |             [0x4c, 0x01, ..]
    |                          ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

error[E0658]: subslice patterns are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:196:28
    |
196 |             | [0x64, 0x86, ..] => FileKind::Coff,
    |                            ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254

   Compiling strsim v0.9.3
   Compiling regex-syntax v0.6.22
   Compiling ryu v1.0.5
   Compiling version_check v0.9.2
   Compiling ident_case v1.0.1
   Compiling fnv v1.0.7
   Compiling bitflags v1.2.1
   Compiling maybe-uninit v2.0.0
   Compiling lazy_static v1.4.0
   Compiling hashbrown v0.9.1
   Compiling once_cell v1.5.2
   Compiling serde_json v1.0.61
   Compiling byteorder v1.4.2
   Compiling semver-parser v0.7.0
   Compiling openssl-probe v0.1.2
   Compiling stable_deref_trait v1.2.0
   Compiling fixedbitset v0.2.0
   Compiling itoa v0.4.7
   Compiling pin-project-lite v0.2.4
   Compiling ansi_term v0.11.0
   Compiling glob v0.3.0
   Compiling termcolor v1.1.2
   Compiling zeroize v1.2.0
   Compiling home v0.5.3
   Compiling cfg-if v0.1.10
   Compiling canonical-path v2.0.2
   Compiling semver-parser v0.9.0
   Compiling tinyvec v1.1.1
   Compiling unicode-bidi v0.3.4
   Compiling form_urlencoded v1.0.0
   Compiling tracing-core v0.1.17
   Compiling thread_local v1.1.2
   Compiling miniz_oxide v0.4.3
   Compiling num-traits v0.2.14
   Compiling num-integer v0.1.44
   Compiling indexmap v1.6.1
   Compiling owning_ref v0.4.1
   Compiling generational-arena v0.2.8
   Compiling error-chain v0.12.4
   Compiling regex-automata v0.1.9
   Compiling addr2line v0.14.1
error: aborting due to 11 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `object`.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo-audit v0.12.1`, intermediate artifacts can be found at `/tmp/cargo-installwwGlHn`

Caused by:
  build failed
The command '/bin/bash -c source $HOME/.cargo/env &&    cargo install cargo-audit --version ^0.12' returned a non-zero code: 101
Makefile:92: recipe for target '.build-container' failed
make: *** [.build-container] Error 101

It appears that the software is using an unstable feature.
For convenience, I've included the rustc --explain output suggested above:
An unstable feature was used.

Erroneous code example:

#[repr(u128)] // error: use of unstable library feature 'repr128'
enum Foo {
    Bar(u64),
}

If you're using a stable or a beta version of rustc, you won't be able to use
any unstable features. In order to do so, please switch to a nightly version of
rustc (by using rustup).

If you're using a nightly version of rustc, just add the corresponding feature
to be able to use it:

#![feature(repr128)]

#[repr(u128)] // ok!
enum Foo {
    Bar(u64),
}

It seems like the version of cargo-audit being installed is not compatible with the Rust version you have specified in tools/Dockerfile1804, which is currently set to 1.41.1. When I change the following line:
ENV RUST_VERSION=1.41.1

to
ENV RUST_VERSION=1.49

The problem goes away. I am, of course, not certain that this is the correct way to solve this.
Digging deeper, it appears that (either directly or indirectly), cargo-audit depends on the object crate, which was updated between version 0.22 and 0.23 to use the feature that is unstable on Rust version 1.41.1.
Another possible way to solve this would be to be more specific in the version of the cargo-audit that is being installed. Currently, --version ^0.12 is being used. Perhaps being more specific would also solve the problem.

The update to rust 1.49 has been included in PR https://github.com/aws/aws-nitro-enclaves-cli/pull/224, that has been merged.


Slow

VSCode Version: 1.20
OS Version: Windows 10

Steps to Reproduce:
not sure. I have a somewhat large typescript project with several git submodules.
VS Code is extremely slow, everything, like invoking intellisense, jump to declaration, ... takes ages (easily >15 seconds). Even hitting ctrl+shift+b to start a build task takes several seconds of "Fetching build tasks..."
It's not always this slow but most of the time, especially once vscode has been running for a bit.
I've tried disabling all extensions I can live without to no effect.
VS Code is almost constantly at 13% CPU usage (one CPU out of 8) and uses ~2 GB of memory.
Profiling VS Code through Very Sleepy shows vscode spending almost the entire time in that process in StoreBufferOverflow:
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f441
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916ec63
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f98e
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f24e
v8::internal::GCIdleTimeHandler::ResetNoProgressCounter	node	[unknown]	0	0x7ff9f8e46169
v8::internal::ScavengeJob::NotifyIdleTask	node	[unknown]	0	0x7ff9f8e42122
v8::internal::GCTracer::AddScopeSample	node	[unknown]	0	0x7ff9f8e34400
v8::internal::ScopeInfo::Empty	node	[unknown]	0	0x7ff9f8e983c1
v8::internal::Factory::NewFillerObject	node	[unknown]	0	0x7ff9f8e9d2a5
v8::base::MagicNumbersForDivision<unsigned int>::operator=	node	[unknown]	0	0x7ff9f91d5b00
[000002E35AA843A1]			0	0x2e35aa843a1
[00000096F73CA580]			0	0x96f73ca580

v8::internal::GCIdleTimeHandler::ResetNoProgressCounter	node	[unknown]	0	0x7ff9f8e45187
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f36e
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916ec63
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f98e
v8::internal::StoreBuffer::StoreBufferOverflow	node	[unknown]	0	0x7ff9f916f24e
v8::internal::GCIdleTimeHandler::ResetNoProgressCounter	node	[unknown]	0	0x7ff9f8e46169
v8::internal::ScavengeJob::NotifyIdleTask	node	[unknown]	0	0x7ff9f8e42122
v8::internal::GCTracer::AddScopeSample	node	[unknown]	0	0x7ff9f8e34400
v8::internal::ScopeInfo::Empty	node	[unknown]	0	0x7ff9f8e983c1
v8::internal::Factory::NewFillerObject	node	[unknown]	0	0x7ff9f8e9d2a5
v8::base::MagicNumbersForDivision<unsigned int>::operator=	node	[unknown]	0	0x7ff9f91d5c93
[000002E35AA85C1C]			0	0x2e35aa85c1c

https://github.com/Microsoft/vscode/wiki/Performance-Issues

Sorry, after days of having this problem it seems to have disappeared. Not sure what happened, maybe it was one of the extension and it got updated.


Potential security thing for hashes

in the code for routes, a raw string is passed to _updateHash on line 1242, which can cause security issues according to certain automated scanners. Here's a potential solution that I am using, which quiets down these scanners:
// Update the hash location, either replacing the current entry, or adding
// a new one to the browser history.
_updateHash: function(location, fragment, replace) {
  if (replace) {
    var href = location.href.replace(/(javascript:|#).*$/, '');
    location.replace(href + '#' + fragment);
  } else {
    // Some browsers require that `hash` contains a leading #.
    location.hash = '#' + encodeURIComponent(fragment);
  }
}

@deanapeterson we are also using hp fortify and the same issues with backbone are being flagged.  We are in a similar situation where critical issues in fortify need to be addressed in order to be compliant.
I was wondering what you ended up doing in order to pass the fortify scans?

The initial suggestion is what I have used to pass security scans when this came up. We have since moved to AngularJS.

Since we never used the backbone router we took the entire router module
out of the source.
We have since moved to angular.
On Jan 13, 2015 8:22 PM, "Simon Collier-Baker"<EMAIL_ADDRESS>wrote:

@deanapeterson https://github.com/deanapeterson we are also using hp
fortify and the same issues with backbone are being flagged. We are in a
similar situation where critical issues in fortify need to be addressed in
order to be compliant.
I was wondering what you ended up doing in order to pass the fortify scans?
—
Reply to this email directly or view it on GitHub
https://github.com/jashkenas/backbone/issues/2071#issuecomment-69859081.

This check doesn't actually seem useful, since it lacks the case-insensitive regex modifier. JaVaScRiPt: URLs work just as well as javascript:.

Check this link out
<EMAIL_ADDRESS>


NO module named password

Hi Nick,
Thanks for the great work here.  You have an idea on why I might be getting the below error?  Im trying to just get the bld and pw for the roomba.  I cloned the repo and when i run python roomba.py I get the below..
Traceback (most recent call last):
File "roomba.py", line 25, in
from roomba.password import Password
File "/home/pi/roomba_pw/Roomba980-Python/roomba/roomba.py", line 25, in
from roomba.password import Password
ImportError: No module named password

I did the full install and when i run install i get
CV or numpy module not found, falling back to PIL
PIL module not found, maps are disabled
CV or numpy module not found, falling back to PIL
PIL module not found, maps are disabled
[I 2017-09-15 13:32:49,664] *******************
[I 2017-09-15 13:32:49,665] * Program Started *
[I 2017-09-15 13:32:49,665] *******************
[I 2017-09-15 13:32:49,666] Roomba.py Version: 1.2.1
[I 2017-09-15 13:32:49,666] Python Version: 3.6.2 (default, Sep  7 2017, 11:20:01) [GCC 6.3.0 20170516]
[I 2017-09-15 13:32:49,667] Paho MQTT Version: 1.3.0
Traceback (most recent call last):
File "/usr/local/bin/roomba", line 11, in
load_entry_point('roombapy==1.3.1.post1', 'console_scripts', 'roomba')()
File "/usr/local/lib/python3.6/site-packages/roomba/main.py", line 455, in main
if HAVE_CV2:
NameError: name 'HAVE_CV2' is not defined

@Darbos ,
Thanks for the feedback, @pschmitt reworked the code a while back, and I think some errors have crept in. There seems to be some sort of circular import loop going on, and possibly to functionality if you don't have opencv has been compromised.
I'm looking into it.

Thank you!!  I tried to install open cv like mentioned but it does not find the package.

you may have an older version of pip, older versions do not install opencv.
To upgrade pip, try:running
pip install --upgrade pip
then try installing opencv-python (worked for me after upgrading pip)

Thanks I tried that a little earlier and it says its good.
pi@sql_server:~/roomba_pw/Roomba980-Python/roomba $ sudo pip install --upgrade pip
Requirement already up-to-date: pip in /usr/lib/python2.7/dist-packages
pi@sql_server:~/roomba_pw/Roomba980-Python/roomba $ pip list
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
cryptography (1.7.1)
enum34 (1.1.6)
idna (2.2)
ipaddress (1.0.17)
Jinja2 (2.8)
keyring (10.1)
keyrings.alt (1.3)
MarkupSafe (0.23)
mysqlclient (1.3.7)
olefile (0.44)
pip (9.0.1)
psutil (5.0.1)
pyasn1 (0.1.9)
pycrypto (2.6.1)
pygobject (3.22.0)
pyxdg (0.25)
RPi.GPIO (0.6.3)
SecretStorage (2.3.1)
setuptools (33.1.1)
six (1.10.0)
WebIOPi (0.7.1)
wheel (0.29.0)

I was able to get this far...
pi@sql_server:~/roomba_pw/dorita980 $ sudo npm run getpassword <IP_ADDRESS>

<EMAIL_ADDRESS>getpassword /home/pi/roomba_pw/dorita980
node ./bin/getpassword.js "<IP_ADDRESS>"

Make sure your robot is on the Home Base and powered on (green lights on). Then press and hold the HOME button on your robot until it plays a series of tones (about 2 seconds). Release the button and your robot will flash WIFI light.
Then press any key here...
Robot Data:
{ ver: '3',
hostname: 'Roomba-3143C91031944720',
robotname: 'Roomba',
ip: '<IP_ADDRESS>',
mac: 'F0:03:8C:E0:EE:B4',
sw: '3.2.7',
sku: 'R690020',
nc: 0,
proto: 'mqtt',
cap: { ota: 1, eco: 1, svcConf: 1 },
blid: '3143C91031944720' }
Error getting password. Follow the instructions and try again.
pi@sql_server:~/roomba_pw/dorita980 $

I got that far in the past with Dorita, I believe that it’s because your node.js is out of date.
I should have a fixed python version uploaded soon.
Nick Waterton P.Eng.
National Support Leader - Nuclear Medicine, PET and RP
GE Healthcare
GE imagination at work
From: Darbos<EMAIL_ADDRESS>Sent: September-15-17 4:18 PM
To: NickWaterton/Roomba980-Python<EMAIL_ADDRESS>Cc: Waterton, Nick (GE Healthcare<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: EXT: Re: [NickWaterton/Roomba980-Python] NO module named password (#19)
I was able to get this far...
pi@sql_server:~/roomba_pw/dorita980 $ sudo npm run getpassword <IP_ADDRESS>
<EMAIL_ADDRESS>getpassword /home/pi/roomba_pw/dorita980
node ./bin/getpassword.js "<IP_ADDRESS>"
Make sure your robot is on the Home Base and powered on (green lights on). Then press and hold the HOME button on your robot until it plays a series of tones (about 2 seconds). Release the button and your robot will flash WIFI light.
Then press any key here...
Robot Data:
{ ver: '3',
hostname: 'Roomba-3143C91031944720',
robotname: 'Roomba',
ip: '<IP_ADDRESS>',
mac: 'F0:03:8C:E0:EE:B4',
sw: '3.2.7',
sku: 'R690020',
nc: 0,
proto: 'mqtt',
cap: { ota: 1, eco: 1, svcConf: 1 },
blid: '3143C91031944720' }
Error getting password. Follow the instructions and try again.
pi@sql_server:~/roomba_pw/dorita980 $
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/NickWaterton/Roomba980-Python/issues/19#issuecomment-329891267, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCUZz_yvCrMD3qkntCf-dlqGJc91Kj2ks5situMgaJpZM4PZQNw.
Unsubscribe from GE's commercial electronic messages: http://sc.ge.com/*casl-unsubscribe
Désabonner des messages électroniques commerciaux de GE: http://sc.ge.com/*lcap-desabonnement

AHHHH, lol you were correct!!!  thank you for taking the time to assist me.  updated node and got it!!

OK, just pushed a new commit, try pulling it, and see if everything works now...
once it's installed (with python ./setup.py install) you just need to run roomba (with whatever options you like)

Thank you! I was really looking for the un and pw so I can control it with my home assistant implementation. Working perfect!
Sent from my iPhone

On Sep 15, 2017, at 4:14 PM, NickWaterton<EMAIL_ADDRESS>wrote:
OK, just pushed a new commit, try pulling it, and see if everything works now...
once it's installed (with python ./setup.py install) you just need to run roomba (with whatever options you like)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Values not being rounded

Running v1.5.3 and values are randomly not being rounded. Example:

Another example: https://mybroadband.co.za/forum/threads/sunsynk-home-assistant.1183858/post-31279011
For these, I see that there's no rounding (.toFixed) here:
https://github.com/slipx06/sunsynk-power-flow-card/blob/f1b58e2816bc0b69088ca84945b3eed29b88031a/dist/sunsynk-power-flow-card.js#L160-L196
Could that be the issue?

This should be fixed in 1.5.4. Thanks


feat(types): Implement AssociativeArrays with dotted and bracketed indexing

This is one of the last steps blocking the start of CreateObject(objType as string), because it allows state to be
stored on a variable.  A few things that haven't been tested against RBI:

The maximum size of an associative array

The maximum debpth of an associative array

Handling of circular references within associative arrays, e.g.:
    a = { foo: "bar" }
    a.b = a

That realistically shouldn't be a huge issue because print a would simply list a.a as <Component: roAssociativeArray>.

This also doesn't have proper handling of the m pointer, but that can come next.

Rebased on master now that #81 has been merged.


scrollToItem not resolving with dynamic height items

Bug Report
Before I get to the bug details I would first like to say how impressed I've been with using this library so far.
It is straight-forward, well documented and I really like how the implementation doesn't make assumptions on the way to use your components.
Thanks for the time and effort you have put into this! 💯
Describe the Bug
I have a content panel with a long list of variable height items, each using the measureRef option.
The scrollToItem action with the smooth option can get caught in an unbreakable bouncing animation loop as it constantly tries to find the target scroll offset position - see the glitchy video examples below.
How to Reproduce
In my case the content items are quite large so it happens more easily if the initial itemSize is set to a small value like 100, and less so if it is something like window.innerHeight. It also seems to happen less often with align: 'start' but can still occur.
Also note that the measured heights of the items are sometimes floating point values (I'm using an HDPI display).
Forcing the measured size to be rounded down to an integer:
const measuredSize = Math.floor(target.getBoundingClientRect()[sizeKey]);

at
https://github.com/wellyshen/react-cool-virtual/blob/0259cf17b9badf13a5275230d491e218979e40d2/src/useVirtual.ts#L351
helped, but the problem still happens occasionally.
CodeSandbox Link
I managed to replicate the problem here (it might take a few clicks of the button to see the issue):
https://codesandbox.io/s/rcv-scroll-to-methods-forked-62gf3?file=/index.js
Expected Behavior
It scrolls to position without getting stuck in a bouncing around animation.
It might be that dynamic height items will always have potential for indeterministic behaviour so maybe there needs to be an extra guard against getting stuck in a never ending animation (maybe if the direction changes more than a couple of times it will end the animation).
Screenshots
The issue when it appears on CodeSandbox:
https://user-images.githubusercontent.com/3010/124582941-6c3fd180-de4a-11eb-8ed0-dc7496366ca2.mp4
The extreme case from my app (flicker warning!):
https://user-images.githubusercontent.com/3010/124571677-ecad0500-de3f-11eb-8dec-c1e54848846e.mp4
Your Environment

Device: Mac Pro
OS: MacOS 11.4
Browser: Chrome
Version: v92.0.4515.80

@subblue Thank you for reporting this issue, your information really helpful, will fix it soon.

@subblue This issue will be fixed alongside the next release, stay tune!


<Windows.h> breaks EnTT

I was trying to implement EnTT into my own game engine and I encountered very interesting problem. It looks like EnTT doesn't work at all with win32 window apps.
To investigate the problem I created fresh new solution with empty project in Visual Studio 2017. Then I copied all EnTT files into project and proper configuration. Then I added main class with this simple code:
#include "pch.h"
#include <entt.hpp>
#include <iostream>

int main() {
	entt::registry registry;
	std::cout << "It works!";
	return 0;
}

And it worked like a charm. In my game engine I'm using Win32 Windows API, so I need to include "Windows.h" header file. So I included it into my simple main function like this:
#include "pch.h"
#include <Windows.h>
#include <entt.hpp>
#include <iostream>

int main() {
	entt::registry registry;
	std::cout << "It works!";
	return 0;
}

And... It failed to compile due to:
1>------ Build started: Project: EnTT_test, Configuration: Debug x64 ------
1>EnTT_test.cpp
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(142): warning C4003: not enough arguments for function-like macro invocation 'min'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(204): warning C4003: not enough arguments for function-like macro invocation 'min'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(230): warning C4003: not enough arguments for function-like macro invocation 'min'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(142): error C2059: syntax error: ')'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(269): note: see reference to class template instantiation 'entt::basic_runtime_view<Entity>' being compiled
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(142): error C2334: unexpected token(s) preceding ':'; skipping apparent function body
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(269): error C2143: syntax error: missing ')' before ';'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(269): error C2059: syntax error: ')'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(269): error C2238: unexpected token(s) preceding ';'
1>c:\users\jbili\source\repos\entt_test\entt\src\entity\runtime_view.hpp(269): fatal error C1201: unable to continue after syntax error in class template definition
1>Done building project "EnTT_test.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped ==========

It looks like some elements (like min) are already defined in "Windows.h", so it won't compile. It's a preatty big issue in my opinion, becuase most DirectX games are using this include.

you can use windows lean and mean

https://github.com/Leandros/WindowsHModular
#define NOMINMAX

It fixed the problem! Thanks!


Replace IntermediateLayerGetter with feature_extraction.create_feature_extractor()

🚀 The feature
A new feature extraction utility based on FX was introduced by #4302. It allows us to extract internal outputs of a module in a simpler way and it should be a drop-in replacement of the old IntermediateLayerGetter class.
Unfortunately the create_feature_extractor() util is not currently used anywhere on vision. We should investigate using it to replace some of the old approaches. Here is a list of candidates:

[x] Replace IntermediateLayerGetter calls in Segmentation models [1, 2]
[ ] Replace IntermediateLayerGetter calls in Detection models [3]
[ ] Rewrite model surgery from the SSDFeatureExtractorVGG [4] and SSDLiteFeatureExtractorMobileNet modules [5].

Extra care needs to be given to ensure that the old weights of pre-trained models can still load and the validation statistics remain the same.
Motivation, pitch
Using the latest FX-based utility will help us future proof our code-base.
cc @datumbox

@datumbox can i work on this issue?

@kingjuno There are a few limitations of using the FX-based approach (losing class info) which means replacing the SSD ones might not work. I'm currently OOO, but I can look into if this still makes sense once I'm back.

ok

Backbones that have been passed through FX won't have class information in the submodules (see https://github.com/pytorch/pytorch/issues/66335). As a result we might no longer be able to do isinstance() to check for specific blocks. This idiom is often used in detection and segmentation for the weight initialization. So prior replacing the feature extractors we must check that none of the models are affected.
@vfdev-5 I know that you previously replaced segmentation but back then this limitation was not known and it's not clear if we are affected. I was hoping to take more time prior the next release to check carefully that we didn't mess up anything before rolling out the change to more places. But if you feel you have the capacity to thoroughly check that none of the models for segmentation or detection are affected, feel free to do it now.

@vfdev-5 Should I proceed with this issue?

Backbones that have been passed through FX won't have class information in the submodules (see pytorch/pytorch#66335). As a result we might no longer be able to do isinstance() to check for specific blocks. This idiom is often used in detection and segmentation for the weight initialization. So prior replacing the feature extractors we must check that none of the models are affected.
@vfdev-5 I know that you previously replaced segmentation but back then this limitation was not known and it's not clear if we are affected. I was hoping to take more time prior the next release to check carefully that we didn't mess up anything before rolling out the change to more places. But if you feel you have the capacity to thoroughly check that none of the models for segmentation or detection are affected, feel free to do it now.

@vfdev-5 Should I proceed with this issue?


Gateway/delete end point

Summary
Details and comments

From what we talked I open it for review, @korgan00


2674: little refactor

Context

Rename var to be different to the existing @jobs instance var.
Add @batch_id instance var to be used by the template so it gets displayed even when jobs have not started execution yet.

Changes proposed in this pull request
Guidance to review

 Scale bulk allocation updates


Setup GitHub Actions and Dependabot updates

This is just a maintenance pass, correct?

yes, a the foundation/prep to evaluate further updates.

We should probably add Ruby 3.2 to the CI list, as it is the latest 3 version.


python311Packages.dask-expr: 1.1.5 -> 1.1.6

Description of changes
Fixes https://github.com/NixOS/nixpkgs/pull/321175#issuecomment-2187404055

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322339 run on aarch64-linux 1

12 packages built:

python311Packages.dask-expr
python311Packages.dask-expr.dist
python311Packages.dask-ml
python311Packages.dask-ml.dist
python311Packages.streamz
python311Packages.streamz.dist
python312Packages.dask-expr
python312Packages.dask-expr.dist
python312Packages.dask-ml
python312Packages.dask-ml.dist
python312Packages.streamz
python312Packages.streamz.dist

Result of nixpkgs-review pr 322339 run on aarch64-darwin 1

4 packages marked as broken and skipped:

python311Packages.streamz
python311Packages.streamz.dist
python312Packages.streamz
python312Packages.streamz.dist

8 packages built:

python311Packages.dask-expr
python311Packages.dask-expr.dist
python311Packages.dask-ml
python311Packages.dask-ml.dist
python312Packages.dask-expr
python312Packages.dask-expr.dist
python312Packages.dask-ml
python312Packages.dask-ml.dist

Result of nixpkgs-review pr 322339 run on x86_64-darwin 1

4 packages marked as broken and skipped:

python311Packages.streamz
python311Packages.streamz.dist
python312Packages.streamz
python312Packages.streamz.dist

2 packages failed to build:

python312Packages.dask-ml
python312Packages.dask-ml.dist

6 packages built:

python311Packages.dask-expr
python311Packages.dask-expr.dist
python311Packages.dask-ml
python311Packages.dask-ml.dist
python312Packages.dask-expr
python312Packages.dask-expr.dist

Result of nixpkgs-review pr 322339 run on x86_64-darwin 1

4 packages marked as broken and skipped:

python311Packages.streamz
python311Packages.streamz.dist
python312Packages.streamz
python312Packages.streamz.dist

2 packages failed to build:

python312Packages.dask-ml
python312Packages.dask-ml.dist

6 packages built:

python311Packages.dask-expr
python311Packages.dask-expr.dist
python311Packages.dask-ml
python311Packages.dask-ml.dist
python312Packages.dask-expr
python312Packages.dask-expr.dist

Result of nixpkgs-review pr 322339 run on x86_64-darwin 1

4 packages marked as broken and skipped:

python311Packages.streamz
python311Packages.streamz.dist
python312Packages.streamz
python312Packages.streamz.dist

8 packages built:

python311Packages.dask-expr
python311Packages.dask-expr.dist
python311Packages.dask-ml
python311Packages.dask-ml.dist
python312Packages.dask-expr
python312Packages.dask-expr.dist
python312Packages.dask-ml
python312Packages.dask-ml.dist


fontbakery web is incomplete, but that's not immediatly clear to users

The checks than can't be run do display a message explaining it. But @vv-monsalve today told me she believes a warning should be displayed in the front page even before any check is run, so that it is clearer to the users that the web version is still experimental and currently incomplete.

I'm not convinced by this. "Still experimental and currently incomplete" suggests that one day we're going to make a full WASM version that does everything the command-line version does. This isn't going to happen, so let's not give people false hope. We already make it clear that some checks don't run, explain why not, and explain that the command-line version is best. I don't think we should do any more than that.

We already make it clear that some checks don't run, explain why not, and explain that the command-line version is best.

Where have we made it clear for the users? It is not informed on the front page, and it was not informed in the tweet about the WASM version.

the web version is still experimental and currently incomplete.

Otoh, is how @felipesanches defined the WASM version. And there is when I said that, if that is the case, this should be warned to users.

@vv-monsalve, as a user who did not at first understand that while using the tool, would you mind sharing your perspective on this?

This is an issue opened by you immediately after a meeting, so it's missing the context, and others discussed there (plus things I didn't mention as the meeting was reaching the end). If you opened the issue, please make it because you consider something a valid inclusion and make it in your own terms.
Otherwise, if this issue is going to be based on my comment at the meeting, I would prefer it to be closed here (I would do it if I can). I'll open another one providing feedback regarding the UX/UI (as I've done before) but on my own terms.

ok, thanks, @vv-monsalve

If you opened the issue, please make it because you consider something a valid inclusion and make it in your own terms.

yes, I do consider it a valid concern to be addressed. But I respect your wish to open your own issue detailing the problem in your own words.

Thanks, @felipesanches.


Add DITA-OT 3.5 install syntax to plug-in pages

Use tabs to show different install commands
Fixes #357

@infotexture Challenge accepted! https://deploy-preview-385--dita-ot.netlify.app/plugins#!com.elovirta.fo, is the copy ok?

Sure, it's just the tabs, right? :shipit:

Extracted the UI copy to translation file for easy updating.


什么时候支持2.2

翘首以盼，实在不想重复造车轮。。

为什么Fabric项目进展那么快，Cello项目进展却这么慢呢？说好的1.0更新，好久了都没出来。迫切需要1.0.0啊

为什么Fabric项目进展那么快，Cello项目进展却这么慢呢？说好的1.0更新，好久了都没出来。迫切需要1.0.0啊

Due to the re-arch work, the 1.0 release is  delayed to support HLF v2.2.
For latest stable version, can try release-0.9.0-h3c branch.

Due to the re-arch work, the 1.0 release is  delayed to support HLF v2.2.
For latest stable version, can try release-0.9.0-h3c branch.


ci: add action to test against new remix versions

receives a repository_dispatch event from the Remix repo on new releases so we can bump deps and run the tests against new Remix versions
depends on https://github.com/remix-run/remix/pull/3026
alternatively, instead of duplicating the various test jobs, i think we can have the deploy workflow run on all branches instead of just "dev" and "main" and just have this new one bump the deps skedaddle, but then i don't think we can properly clean up and remove the branch
note: we're using the default GitHub Actions bot account so we'll need to enable write permissions for it https://github.com/remix-run/grunge-stack/settings/actions
Signed-off-by: Logan McAnsh<EMAIL_ADDRESS>

going a different direction, check https://github.com/remix-run/remix/pull/3026 for updates


fix: enhance Filter Data with JQ Query, Column Selection and Index selection"

Consolidates JSON parsing, data filtering, and key extraction into a single streamlined component. Adds support for JQ queries, column selection, and index-based filtering, eliminating the need for separate Parse JSON and Extract Key components.

If this is approved we can remove the following:
src/backend/base/langflow/components/processing/extract_key.py
src/backend/base/langflow/components/processing/filter_data_values.py
src/backend/base/langflow/components/processing/parse_json_data.py

Sure can do!

Hey @vasconceloscezar
Please, check 12bac03 (#4774) and see if that makes sense.
Essentially, since we strive for returning a data object to maintain compatibility between components, I made it so if the jq query returns a list, it puts it inside the Data object.

Why don't we keep it as a Data list? I rather have a list being returned than a results field.
It's counterintuitive having a list being transformed in a result. Especially if the starter JSON is a list already.
I believe we soon will have more components to handle Data Lists and so on, so this whole List handling will be even better.
Example of not ideal results:
Start Data List:

Filtering with: .[2] | {"missionId": .missionId}

This is not ideal, bc the user will need to add another component just for re-parse that list again.
Toughts @ogabrielluiz ?

It is unintuitive but it would be better to add a component that makes flow work rather than having them change the component they want to use because it does not work with a list of Data objects.

@vasconceloscezar I've just added a new type: langflow.schema.data_set.DataSet (we can improve it in this PR) that can deal with a list of Data so we can display that more clearly now.


Calculation of Euclidian distance based on geographical coordinates

In wrf_remove_urban: distance is calculated as Euclidian distance based on  geographical coordinates (lat & lon):
 dis = (lat.where((luse!=13) &                                    (luse!=17) &                                    (luse!=21)                                    )-lat.isel(south_north=i,west_east=j))**2 +\                         (lon.where((luse!=13) &                                    (luse!=17) &                                    (luse!=21)                                    )-lon.isel(south_north=i,west_east=j))**2
Due to meridian convergence, there might be some issues with Euclidian distance calculation with the magnitude of the issues not clear to me. I would suggest to use array indices for distance calculation (with the same effect as projected coordinates).

Thanks for this remark @KlemensBarfus.
@dargueso designed this routine, perhaps he can have a look whether this can be optimised?

Yes, you're right. This was originally designed for cities near the equator, so it wasn't much of an issue. I will update it to calculate distances taking that into account.
Thanks @KlemensBarfus.

I have added a function to calculate distance using a better approximation (spherical law of cosines).  I have added a pull request for this.


[INF] Add workflow to handle external PRs

Closes #33

Changes proposed in this pull request:

find the PR by looking for different origin repo names
apply the _community label

The actual handling will be done by the existing workflow for bot PRs

Checklist
This section is for the PR reviewer

[x] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
[x] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

Shoot, sorry @surchs, I forgot I actually had another question about this PR.
Shouldn't this workflow actually live under template_workflows and not the .github directory? I think we want it in every repo, right?


Output STDOUT to Log tab on BCP

On Base Command Platform, the Log tab will display the launched job's STDOUT in addition to the results being piped to a log file.

@roclark could you fix the code style, please?


Document support for Powerlevel9k on Linux distros

Describe Your Issue
I have developers asking me about using Powerlevel9k on Linux distros, such as Arch and Fedora. Could there be a section in the documentation that covers Linux support?

In the wiki you have a section Install. I saw an arch section there, but I don't know if it's going to be complete enough for your use. Feel free to tell us what's missing

I think this link could help : https://github.com/bhilburn/powerlevel9k/wiki/Install-Instructions

The simplest answer with almost no portability issues would be
https://github.com/bhilburn/powerlevel9k/wiki/Install-Instructions#option-1-install-for-vanilla-zsh
Git is installed on most linux distros by default and zsh is usually available in the package-manager of your distro
The only thing that really differs per distro and per console(-emulator) is how to install powerline-fonts or nerd-fonts (if needed).

@ryanwhocodes I assume this issue can be closed since there wasn’t any activity on this?


remove-all-laradock-built-containers-and-images

Remove LaraDock-built containers and images

You just execute docker-compose down to remove all laradock container.

Thanks for the input. Only thing is that docker-compose down did not remove laradock_* images. I could use this function to simplify the script.
Thoughts?

I see a possible advantage of not using docker-compose down in that it would work on any LaraDock-based projects. You don't have to be standing in a laradock folder.

@LarryEitel docker-compose down just remove all containers not include images.

Hi @LarryEitel I think this is very case specific, and won't be used by the majority of the LaraDock users..


Link of Resnet has expired.

@yuanyuanli85  As the link of pretrained resnet model seems not avaliable at this moment, could you please update the link or provide alternative method to download? Thank you.

I just tried to visit the resnet pre-train model https://drive.google.com/file/d/0Byy2AcGyEVxfdUV1MHJhelpnSG8/view. It works for me. Could you try again?


Modal attempt: Error with wrapping app in the SvelteUIProvider

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
Hi.
Using SvelteKit 1.0.0-next.445, with the new Routing system, I have this case:
+layout.svelte file:
<script>
    import { SvelteUIProvider } from '@svelteuidev/core';
    import { page } from '$app/stores';
</script>
...
<div class="container">
    <SvelteUIProvider>
        <slot />
    </SvelteUIProvider>
</div>

as per your instructions here: https://www.svelteui.org/theming/svelteui-provider
+page.svelte file:
<script>
    import { Modal, Button } from '@svelteuidev/core';
    let opened = false;
    import Time from "svelte-time";
    /** @type {import('./$types').PageData} */
    export let data;
</script>
...
<Modal {opened} on:close={() => (opened = false)} overflow="inside">
	{@html data.content}
</Modal>
<Button on:click={() => (opened = true)}>Dnevni red</Button>

as per your docs.
VS Code with the Svelte plugin doesn't report any errors but in the browser console I'm getting this error:
Error: Wrap your app in the SvelteUIProvider, or provide a sufficent target throught the "target={''}" prop
Needless to say, the Modal content is never rendered in HTML, only these two lines, one below the other:
<!--<Modal>-->
<!--<Error>-->

Thank you for your time and effort putting SvelteUI together.
Cheers.
In which browser(s) did the problem occur?
Chrome
Steps To Reproduce
As mentioned in the description.
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
Yes
Relevant Assets
No response

I am getting the same. Have tried both SvelteUIProvider and the target prop. I am using the App.svelte method.

Thank you very much @BeeMargarida for your quick response.

You can close after the fix, so that it's clearer that it's not solved yet :smile:

Oops, my bad.

This should already be resolved in the new release 0.7.5 (an announcement will be made)

Uncaught (in promise) Error: Wrap your app in the SvelteUIProvider, or provide a sufficent target throught the "target={''}" prop

Uncaught (in promise) Error: Wrap your app in the SvelteUIProvider, or provide a sufficent target throught the "target={''}" prop

You need to set SvelteUIProvider in your +layout, like it's demonstrated here in the docs


Unexpected error

I cloned this repo and used the build.cmd but I get the following error
dotnet restore
  Restore completed in 27,98 ms for D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj.
  Restoring packages for D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj...
D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj : error NU1102: Unable to find package ElectronNET.API with version (>= 1.0.0)\r
D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj : error NU1102:   - Found 5 version(s) in nuget.org [ Nearest version: 0.0.5 ]\r
D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj : error NU1102:   - Found 0 version(s) in LocalDev
  Restore failed in 915,28 ms for D:\repositories\Electron.NET\ElectronNET.WebApp\ElectronNET.WebApp.csproj.

Am I missing something?

Hi
The build.cmd might be missleading. Currently it only builds the WebApp project, which requires that the API / CLI projects have been build.
Try "buildAll.cmd" - this might take a while, because it builds the API and CLI. After that the real WebApp will be published for Win/Linux with the electron stuff.
After a successful run of buildAll.cmd you should be able to use build.cmd/start.cmd.
I guess we need to a) rename those files or b) remove the build.cmd/start.cmd files, because AFAIK they might be not needed anymore. @GregorBiswanger

The build.cmd is now gone, please use buildAll.cmd.
I'll close this and add some notes to the ReadMe.md. Hope this is OK.