feat: Implement basic train_test_split

This PR implements the train_test_split function which wraps around sklearn.
The warnings are only emitted using warnings.warn for now; nothing is saved to a Project, as that part of the design still needs work.
In order to validate the technical design one warning is implemented, HighClassImbalanceWarning. This inherits from the built-in Warning class so that it can be used directly in warnings.warn.
Because we expect warnings to take a wide range of arguments, we pack all the relevant information into a kwargs dict inside train_test_split, and let the check static method accept **kwargs as well as the necessary positional arguments.
Closes https://github.com/probabl-ai/skore/issues/683

Todo:

[ ] Refactor _find_ml_task, as a function of the same name already exists in cross_validate.py?
[ ] Add an example
[ ] Test behaviour in a Jupyter notebook

Thanks, I got some issues:
from skore.sklearn.train_test_split import train_test_split

[ ] should be from skore import train_test_split

X = [[1]] * 4
y = [0, 1, 1, 1]
train_test_split(X, y)

[ ] the warning message does not return to line in VS Code:

https://github.com/user-attachments/assets/80845d61-8dfc-40d4-8307-84b4701e4c80


Alexa - Unable to link HA with Alexa Skill

Home Assistant release with the issue: 0.95.4

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): Docker

Component/platform: https://www.home-assistant.io/components/alexa.smart_home/

Description of problem:
I don't know which version or date this stopped working because I was using emulated hue component. However, others and I were trying to setup Alexa Smart Home Skill Component and the linking is not working.
According to this topic https://community.home-assistant.io/t/alexa-proactive-mode-unable-to-link-alexa/123530 people say that is an issue with proactive mode, however, I tried to disable it on my alexa dev console and removing it from the configuration file and I'm still unable to link my account with Alexa.
I also tested the lambda method using the AWS console and it is working fine, returning values when have the correct token.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

smart_home:
  endpoint: https://api.amazonalexa.com/v3/events
  client_id: !secret alexa_client_id
  client_secret: !secret alexa_client_secret
  filter:
    include_entities:
      - switch.alexandre_pc
      - switch.sonoff_basic_1
      - switch.sonoff_basic_2
      - switch.sonoff_basic_3
      - switch.sonoff_basic_4
      - switch.lightswitch_1_button_1
      - switch.lightswitch_1_button_2
      - switch.lightswitch_1_button_3
      - switch.lightswitch_2_button_1
      - switch.lightswitch_2_button_3
      - media_player.alexandre_tv
      - media_player.playstation_4
      - media_player.speaker_sala
      - climate.miairgateway1
  entity_config:
    switch.alexandre_pc:
      display_categories: LIGHT
      name: Computer
    switch.sonoff_basic_1:
      display_categories: LIGHT
      name: Computer Light
    switch.sonoff_basic_2:
      display_categories: LIGHT
      name: Bed Light
    switch.sonoff_basic_3:
      display_categories: LIGHT
      name: Livingroom Light
    switch.sonoff_basic_4:
      display_categories: LIGHT
      name: Bathroom Light
    switch.lightswitch_1_button_1:
      display_categories: LIGHT
      name: External Garage Light
    switch.lightswitch_1_button_2:
      display_categories: LIGHT
      name: Garage Light
    switch.lightswitch_1_button_3:
      display_categories: LIGHT
      name: Kitchen Light
    switch.lightswitch_2_button_2:
      display_categories: LIGHT
      name: External Entrance Light
    switch.lightswitch_2_button_3:
      display_categories: LIGHT
      name: Entrance Light
    media_player.alexandre_tv:
      display_categories: TV
      name: TV
    media_player.playstation_4:
      display_categories: SPEAKER
      name: Playstation 4
    media_player.speaker_sala:
      display_categories: SPEAKER
      name: Livingroom Speaker
    climate.miairgateway1:
      display_categories: THERMOSTAT
      name: Air Conditioning

Traceback (if applicable):
2019-06-29 10:35:36 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport to Alexa: INVALID_ACCESS_TOKEN_EXCEPTION: Access token is not valid.

Additional information:

When I disabled "Send Alexa events", I managed to link it, however, it would be nice to have a proactive mode working as it was advertised for the cloud in 0.95

When I disabled "Send Alexa events", I managed to link it, however, it would be nice to have a proactive mode working as it was advertised for the cloud in 0.95

@Molodax
Can you confirm which lambda are you using?

I'm using the lambda that you posted on forum.

Still have this in my log:
Log Details (ERROR)
Mon Jul 01 2019 00:19:50 GMT+0200 (Central European Summer Time)
Error when sending ChangeReport to Alexa: INVALID_ACCESS_TOKEN_EXCEPTION: Access token is not valid.

Yeah, I tried to fix the linking according to the docs but it didn't work.
@balloob
Can you help us here when you get time, please?

The same for me. Also if I use @xalexslx lambda, as soon as I activate “Send Alexa Events” in the Skill I am unable to link.
Tried also with Amazon as oauth provider and a fixed token for the lambda.

For proactive mode to be enabled, you need to have client ID and secret configured. Once that is set up, you need to relink the Alexa skill.

For proactive mode to be enabled, you need to have client ID and secret configured. Once that is set up, you need to relink the Alexa skill.

It was done (ID and secret configured, relink) but it doesn't work.

Are you using the right endpoint? It depends on where your lambda is hosted and where the account is linked which endpoint to use.

Are you using the right endpoint? It depends on where your lambda is hosted and where the account is linked which endpoint to use.

@balloob I am sure that I'm using the right endpoint because as soon as I disable "Send Alexa Events" in permissions, I am able to link Alexa and everything works in Alexa apart proactive status update since it is disabled. I've also checked the Client ID and Client secret. Others reproduced the same issue and discussed it on the forum (link above in the description)

What region is your lambda hosted and what endpoint do you use?

What region is your lambda hosted and what endpoint do you use?

endpoint: https://api.eu.amazonalexa.com/v3/events
lambda: Ireland
Thanks, @balloob

Region: us-east-1
Lambda: https://gist.github.com/awarecan/630510a9742f5f8901b5ab284c25e912
Default Endpoint: arn:aws:lambda:us-east-1:XXXXXXXXXXXX:function:HALambda
Send Alexa Events: Disabled
Testing Lambda via AWS Console with LLT: OK, Return my entities.
Config:
smart_home:
#  endpoint: https://api.amazonalexa.com/v3/events
#  client_id: !secret alexa_client_id
#  client_secret: !secret alexa_client_secret
  filter:
    include_entities:
      - switch.alexandre_pc
      - switch.sonoff_basic_1
      - switch.sonoff_basic_2
      - switch.sonoff_basic_3
      - switch.sonoff_basic_4
      - switch.lightswitch_1_button_1
      - switch.lightswitch_1_button_2
      - switch.lightswitch_1_button_3
      - switch.lightswitch_2_button_1
      - switch.lightswitch_2_button_3
      - media_player.alexandre_tv
      - media_player.playstation_4
      - media_player.speaker_sala
      - climate.miairgateway1
  entity_config:
    switch.alexandre_pc:
      display_categories: LIGHT
      name: Computer
    switch.sonoff_basic_1:
      display_categories: LIGHT
      name: Computer Light
    switch.sonoff_basic_2:
      display_categories: LIGHT
      name: Bed Light
    switch.sonoff_basic_3:
      display_categories: LIGHT
      name: Livingroom Light
    switch.sonoff_basic_4:
      display_categories: LIGHT
      name: Bathroom Light
    switch.lightswitch_1_button_1:
      display_categories: LIGHT
      name: External Garage Light
    switch.lightswitch_1_button_2:
      display_categories: LIGHT
      name: Garage Light
    switch.lightswitch_1_button_3:
      display_categories: LIGHT
      name: Kitchen Light
    switch.lightswitch_2_button_2:
      display_categories: LIGHT
      name: External Entrance Light
    switch.lightswitch_2_button_3:
      display_categories: LIGHT
      name: Entrance Light
    media_player.alexandre_tv:
      display_categories: TV
      name: TV
    media_player.playstation_4:
      display_categories: SPEAKER
      name: Playstation 4
    media_player.speaker_sala:
      display_categories: SPEAKER
      name: Livingroom Speaker
    climate.miairgateway1:
      display_categories: THERMOSTAT
      name: Air Conditioning

This file is being included by configuration.yaml
alexa: !include configs/alexa.yaml

Screenshots:

Okay, well then I don't know.

I have been wrestling with the same issue xalexslx (and others) have outlined above. I can't see any obvious things I'm doing wrong, but getting the same 'unable to link' message each time.

Hi!
For all having problems linking: For me, this lambda seems to be working ok (from here). Environment variables HOST and BEARER_TOKEN (long lived acces token) must be set. Handler is called lambda_function.event_handler
Can anyone confirm? Than maybe we can improve it to use the HA authentication instead of the long lived token.

Maybe this is the issue? I guess most of us are using Letsencrypt:

If you have not implemented OAuth 2.0, you can use Login with Amazon (LWA) as your OAuth 2.0 provider or any provider that has a certificate signed by an Amazon-approved certificate authority. Note that you cannot use https://letsencrypt.org/, even though it is on the certificate list.

@ronmichel
Are you using this lambda from Haaska but with the original alexa.smart_home component?
I'll try to update the lambda to use the token if it works later.

I Got mine linking using the modified script with send events turned on
Modified Lambda function
It's a quick hack based on this forum post
below is my configuration.
AWS region: Ireland
I have the following enviroment Variables
BASE_URL - pointing to https://<myhomeassistant>
DEBUG: TRUE
LONG_LIVED_ACCESS_TOKEN: <token Value from Homeassitant>
NOT_VERIFY_SSL: <BLANK>

#secrets.yaml
alexa_event_endpoint: "https://api.eu.amazonalexa.com/v3/events"
alexa_client_id: <value from “Alexa Skill Messaging">
alexa_client_secret: <value from “Alexa Skill Messaging">

alexa:
  smart_home:
    endpoint: !secret alexa_event_endpoint
    client_id: !secret alexa_client_id
    client_secret: !secret alexa_client_secret

Is this really working for anyone? I've been hammering on this now for two days without success. The 'test' function works without issue but linking the Skill always fails. I'm happy to provide whatever information would be helpful

I'll help but I'm not an expert I just know it took me over 2 weeks to get mine working.

@aLTeReGo-SWI it doesn't work (doesn't link) if you follow the original instructions posted here > https://www.home-assistant.io/components/alexa.smart_home/  AND enable "Send Alexa Events". It looks like it is possible to have "Send Alexa Events" enabled but not with HA OAuth2.
@balloob announced support in 0.95 for proactive state reporting (enabled "Send Alexa Events") for cloud, assuming it is possible to make it work but...

I have the same issue. Following for update

It seems like finally managed to make it work using the updated lambda from @matt2005. The "secret" for me was to reboot the homeassistant after every disable and enable skill step in Alexa, otherwise,  it messes up with tokens.

@Molodax could you please update the documentation?

@balloon I can update the docs, it will also require update of the lambda function.
It would be good to hear whether it was a solution for others.

It seems like finally managed to make it work using the updated lambda from @matt2005. The "secret" for me was to reboot the homeassistant after every disable and enable skill step in Alexa, otherwise, it messes up with tokens.

Where can we find the updated lambda code?

I got it to link using the updated lambda code. Unlinked, restarted hass, linked.

By changing my HA external port to 443 (standard HTTPS) account linking just started working.  Looks like Amazon Alexa doesn't like using non-standard ports for account linking.

Hello Guys
After a lot of hours trying too making it work, i finaly managed to make it work for me. The issue was: it doesn't work with the EU configuration for the client id and the lambda script. I had to use the US configuration for Alexa and AWS.
This message is just for the poor french guy triying the configure it with https://layla.amazon.com/

Closing issue as docs have been updated with new instructions.

Does anybody have this working on non-standard ports? Even with "Send Alexa Events" disabled I still get the same error.

Can confirm non-standard port don't work when used in Alexa skill account linking authorization/token URLs. I got it working using Login with Amazon and a long lived token in the Lambda.

You got working using login with amazon, what do You mean??


[CCI] Update "Yo" and remove "**/meow/trim-newlines"

Description

yo-doc and yo-component scripts work
After removing node_modules there are no errors regarding trim-newlines

yarn install v1.22.19
[1/4] 🔍  Resolving packages...
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>[2/4] 🚚  Fetching packages...
warning Pattern ["gonzales-pe-sl@github:srowhani/gonzales-pe#dev"] is trying to unpack in the same destination "/Users/andreymyssak/Library/Caches/Yarn/v6/npm-gonzales-pe-sl-4.2.3/node_modules/gonzales-pe-sl" as pattern<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping.
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-view > @miksu/prettier ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^7.0.0".
warning "react-view > @miksu/prettier ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^4.0.0 || ^5.0.0".
warning "react-view > @miksu/prettier ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 4".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "yo ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^2.0.0".
[4/4] 🔨  Building fresh packages...
$ node ./scripts/postinstall.js
✨  Done in 28.16s.

Issues Resolved
https://github.com/opensearch-project/oui/issues/598
Affected Issues
https://github.com/opensearch-project/oui/issues/594
https://github.com/opensearch-project/oui/issues/595
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[X] All tests pass

[X] yarn lint
[X] yarn test-unit

[X] Commits are signed per the DCO using --signoff

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

@andreymyssak Thanks for the PR. It looks like **/meow/trim-newlines was used to mitigate a security vulnerability. See the Mend security check for more details.

@ashwin-pc Thanks for pointing this out to me, the code is ready for review


feat: update vehicle info

Signed-off-by: tomoya.kimura<EMAIL_ADDRESS>update vehicle.info.param.yaml to lexus 450h model.
ref:
https://lexus.jp/models/rx/spec_price/specification/rx450h/
https://www.carsguide.com.au/lexus/rx/car-dimensions/2022

Should we also update https://github.com/autowarefoundation/sample_vehicle_launch?

@kenji-miyake
Do the vehicle_info in lexus_description.iv and  in sample_launch need to match?
https://github.com/autowarefoundation/sample_vehicle_launch/tree/main/sample_vehicle_description/config

@tkimura4 Not necessarily, but I guess it might be better.

Reference: Autoware's definition of vehicle dimensions -> https://github.com/autowarefoundation/autoware-documentation/pull/79

@tkimura4 Please merge this if it's okay for you. Or you can wait for comments from others if necessary.

LGTM


feat: expand tags api

This PR expands upon the new tags API so that we can load from tags using the top-level lance.dataset Python API. Once accepted, the changes from this PR will be used to update the quickstart notebook to demonstrate the new tags functionality.

Codecov Report
Attention: Patch coverage is 73.68421% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@6d34d5f). Learn more about missing BASE report.

Files
Patch %
Lines

rust/lance/src/dataset/refs.rs
75.00%
0 Missing and 3 partials :warning:

rust/lance/src/dataset/builder.rs
60.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2679   +/-   ##
=======================================
  Coverage        ?   79.59%
=======================================
  Files           ?      226
  Lines           ?    66333
  Branches        ?    66333
=======================================
  Hits            ?    52800
  Misses          ?    10412
  Partials        ?     3121

Flag
Coverage Δ

unittests
79.59% <73.68%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Get a staging branch here

I've pushed the staging branch, but I don't have access to the repos settings to have it be the default target for pull requests

We won't be changing staging to our main branch, but i've added the projects, gonna rebase the prs now


[samsungmobile] Add Galaxy A15 and A25

Links:

https://news.samsung.com/in/samsung-galaxy-a25-5g-galaxy-a15-5g-with-awesome-camera-and-new-editing-features-launched-in-india
Galaxy A15: https://www.gsmarena.com/samsung_galaxy_a15-12637.php
Galaxy A15 5G: https://www.gsmarena.com/samsung_galaxy_a15_5g-12638.php
Galaxy A25 5G: https://www.gsmarena.com/samsung_galaxy_a25-12555.php

Thanks @jjlin!


[Feature] Sort data on multi-axis line chart

Expected Behavior

Being able to dynamically sort datasets and labels on multi-axis line chart, for example using radio buttons or when clicking on data's label. This would allow to select and show different perspectives for the same datasets.
Current Behavior

Today, datasets are frozen and showing chart with different perspectives needs to be implemented every time since no native options exist for that purpose.
Possible Solution

Here is a way to do it (keep in mind that I begin in JS).
https://codepen.io/anon/pen/wPRmQg

Updated codepen for v3.0.0-beta.12. https://codepen.io/etimberg/pen/VwmGrxO
I think this is the best way to do this is externally as it allows a variety of integrations with frameworks (react, angular, etc) without causing problems


Nextflow json schema - use to populate launch tab

Nextflow core workflows use a json schema to provide information about workflow parameters. This file can be pretty thorough and is used to populate a web site graphical builder which can be used to write back to the json schema file.
This may become a nextflow standard and is also encouraging the use of explicit json files (which we register).
This provides an idea to look into
Populate the launch tab with more info based on a json schema (might be code in https://nf-co.re/mag/1.2.0/parameters that is helpful)

https://github.com/nf-core/nf-co.re/blob/e7786a43460a038333257ac54e25ff5592c59375/public_html/launch.php#L515-L530 may also be useful


Stuck on E

For a few days, I've experienced the Hub running only on the E formation without Briv, and also not stacking. I've confirmed that my modron settings are correct as well as the zones set in the Hub, but this behavior still persists. I run Steam in windowed mode, 1600x900 resolution. I'm happy to furnish any other info needed to diagnose the issue.

I have also had this issue come up over the last week or 2.  I am on Epic.

There's an update as of today. Delete existing files then re-download. Fixed for me.


Input (continued)

Migrating the work from #1441
The Caniuse entries seem to line up, so @petele already did that 🎉
I fixed the descriptions to be clearer when they contain a list of type values. I don't like the inconsistency w/ the single-type version, but is probably ok like this.
The idea of variants of a specific attribute value for a specific element being standalone features seems fine, but I don't know if that fits into how we've been thinking about the html-elements group. Do we expect that group to be each element, once? Or is this fine?

ok ready for another review pass. not stoked on the "represents" language from the original PR, so lmk if you think needs reworking.


workload is not authorized for the requested identities

after following the spire guide https://istio.io/latest/docs/ops/integrations/spire/ to install SPIFFE I'm getting the following error on my ingress-gateway
2022-08-09T15:39:26.825395Z     warning envoy config    StreamSecrets gRPC config stream closed: 3, workload is not authorized for the requested identities ["file-root:/etc/istio/shared/certs/cert-chain.pem"]
2022-08-09T15:39:31.818079Z     warning envoy config    StreamSecrets gRPC config stream closed: 3, workload is not authorized for the requested identities ["file-cert:/etc/istio/ingress-gateway/certs/tls.crt~/etc/istio/ingress-gateway/certs/tls.key

BTW, I'm using a self signed certificates on my ingress-gateway
Is there something I'm missing or do I need to register those worklods? Any guidance would be appreciated

Hello,
Got exactly same issue with SPIRE and selfsigned certificate!

@alexdotsh @SoulKyu sorry for the really late reply, but how did you solve this error. I am currently setting up spiffe/spire with istio and as soon as I deploy the istio-gateway I get the same error message as you had 2 years ago.


Bug Report

Describe the bug
First of all, I think the work your doing here is awesome!
I do encounter an issue when trying to deploy the template to any of my Azure tenants using any off my accounts. I'm receiving the following error:
"The client '{my account}' with object id '{my object id}' does not have authorization to perform action 'Microsoft.Resources/deployments/validate/action' over scope '/providers/Microsoft.Resources/deployments/Microsoft.Template-20200624223131' or the scope is invalid. If access was recently granted, please refresh your credentials."
RAW ERROR
{   "deploymentStatusCode": -1,   "stage": 6,   "expected": true,   "error": {     "message": "The client '{my account}' with object id '{my object id}' does not have authorization to perform action 'Microsoft.Resources/deployments/validate/action' over scope '/providers/Microsoft.Resources/deployments/Microsoft.Template-20200624223131' or the scope is invalid. If access was recently granted, please refresh your credentials."   },   "location": "westeurope",   "deploymentName": "Microsoft.Template-20200624223131",   "details": {     "code": "AuthorizationFailed",     "message": "The client '{my account}' with object id '{my object id}' does not have authorization to perform action 'Microsoft.Resources/deployments/validate/action' over scope '/providers/Microsoft.Resources/deployments/Microsoft.Template-20200624223131' or the scope is invalid. If access was recently granted, please refresh your credentials."   } }
The accounts I've tested have Global Administrator permissions in AAD, they have Owner been assigned the owner role on the subscription(s), and they have been assigned elevated rights at the tenant root management group level.
Steps to reproduce

Trying to deploy using the Deploy to Azure link: https://ms.portal.azure.com/?feature.customportal=false#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzOps%2Fmain%2Ftemplate%2Fux-foundation.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzOps%2Fmain%2Ftemplate%2Fesux.json
Filling in the required information, tried most options, non of them work.
In the final blade I'm getting the validation error.

Screenshots

Can you please grant required permission to user account you are using to provision template?
Step -1 :
Get-AzRoleAssignment | ? {$_.RoleDefinitionName -eq "User Access Administrator" `
  -and $_.SignInName -eq<EMAIL_ADDRESS>-and $_.Scope -eq "/"}

Step -2 :
New-AzRoleAssignment -SignInName <yourLoginName> -Scope "/" -RoleDefinitionName "Owner"

For anyone that hits this issue. The accounts utilised MUST NOT BE GUESTS to the Tenant - you must be authenticated with an account that is a member of the Tenants.


Adds a stack-trace to failures from OpenSearch

Description
The current logging of failures in OpenSearch only includes the top-level message. This is not very helpful with unexpected errors. This PR logs the full exception using SLF4J.
Issues Resolved
N/A
Check List

[x] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

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

Codecov Report

Merging #1899 (09ac80f) into main (bbca3d7) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1899      +/-   ##
============================================
- Coverage     93.94%   93.87%   -0.07%
  Complexity     1550     1550
============================================
  Files           198      198
  Lines          4589     4589
  Branches        372      372
============================================
- Hits           4311     4308       -3
- Misses          195      197       +2
- Partials         83       84       +1

Impacted Files
Coverage Δ

...rwarder/discovery/AwsCloudMapPeerListProvider.java
92.68% <0.00%> (-2.44%)
:arrow_down:

...opensearch/dataprepper/pipeline/ProcessWorker.java
88.46% <0.00%> (-1.93%)
:arrow_down:

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


Logging the presolving phase (CP-SAT)

I have models where roughly half the solve times are spent in the presolving phase. Is there any way to know which variables from the model were affected by a given presolve rule? That'll help me simplify my model so that I'm not repeatedly paying the latency cost of the presolve phase.
For example, from the below log output from or-tools, is there any way to know which variables were affected by each of the below presolve rules?
- 104753 affine relations were detected.
- 70753 variable equivalence relations were detected.
- rule 'bool_and: always false' was applied 100 times.
- rule 'bool_and: non-reified.' was applied 100 times.
- rule 'bool_or: always true' was applied 250 times.
- rule 'bool_or: only one literal' was applied 400 times.
- rule 'bool_or: removed enforcement literal' was applied 200 times.
- rule 'deductions: 200000 stored' was applied 1 time.
- rule 'false enforcement literal' was applied 2201 times.
- rule 'int_max: reduced domains' was applied 2 times.
- rule 'linear: empty' was applied 101 times.
- rule 'linear: fixed or dup variables' was applied 58101 times.
- rule 'linear: infeasible' was applied 150 times.
- rule 'linear: reduced variable domains' was applied 48004 times.
- rule 'linear: remapped using affine relations' was applied 1000 times.
- rule 'linear: simplified rhs' was applied 200098 times.
- rule 'linear: size one' was applied 60401 times.
- rule 'presolve: iteration' was applied 1 time.
- rule 'true enforcement literal' was applied 2451 times.

Sorry no, there are no good solution. And the presolve code is too complex to add this feature.
You can send us the model for us to profile.


case sensitivity [string]

use case: enum (type string)
How do we display this information in a clear and concise way?
I would like to avoid a regular expression solution?

Currently we don't have syntax for case insensitivity other than regex literals:
foo: /foo|bar|baz/i

method: /get|head|delete|post|patch|put/i,

It's not that bad after all.

Great. =)


fix(import): removes dependency of repo name to be same as app name i…

removes the dependency of repo name to be same as app name in import flow
Tracks :
https://github.com/openshiftio/openshift.io/issues/3818

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Confusion: There's different result  when using the same javascript code with Intellij ideaIU and TypeScript

Hello, I'm a fresh man about javascript and TypeScript.
The environment as below:

Intellij ideaIU-14.1.4, TypeScript is 1.6.2
The others tools are installed.
Chrome version 44.0.2403.157 m

[Description]
the javascript code like this, very simpleness.
function max1() {
    console.log(arguments);
}
max1(1, 2, "Hello");

and the html like this:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>Test</title>
    <script type="text/javascript" src="index.js"></script>
</head>
<body>

</body>
</html>

When I run the Chrome and check the console like this:

==> ok, that's right!
But when I compile the same javascript code on TS, it tell me that one error is occured.

But in the generated index.js, the JS code can also run on the Chrome.( console can show arguments info)
[Confusion]
So my question is that since the js code can't be compiled to success in TS. But it can be also create the *.js file ,and the js file can be run.  So In my babyish opinion the largest benefit of TypeScript is checking compilation errors of JS. Right??
If that, I think when the compilation errors are occured, the file js(like index.js) should't be generated.
[Resolution]
Of course, this error has been fixed, when I add some arguments to max1.
like this:
 function max1(a, b, c) {
 	console.log(arguments);
 }
 max1(1, 2, "hello");

You can prevent the compiler from emitting using the --noEmitOnError option.
We still emit syntactically valid JavaScript despite errors because our philosophy is that the type system shouldn't have the final say on whether the code is runnable - the user might feel that that an error is overly restrictive, and so they have the final say on that.
Type-checking is certainly one of the biggest advantages of TypeScript; another is that we support features from ECMAScript 2015 (a.k.a. ES6, the most recent version of JavaScript), as well as some other syntactic goodies, even when emitting to ES3 targets.
For example, another way you could fix your issue is to use ES6 rest parameters:
function max1(...args: any[]) {
    console.log(args);
}
max1(1, 2, "hello");

Hope that helps!


WebSocketをサポートする

Summary
Add a Summary here.
Contributor Tasks

[ ] Create or edit test cases here
[ ] Add a CHANGELOG entry for this change.
[ ] Ensure documentation requirements are met e.g., public API is commented.
[ ] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.

Test Cycle
Link to the test cycle here.
Reviewer Tasks

[ ] Code reviewed.
[ ] Non-code assets e.g. Unity assets/scenes reviewed.
[ ] All tests must be ran and cover all scenarios (If not, add new tests to the cycle and run them).
[ ] Documentation has been reviewed.
[ ] Approve with a comment of any additional tests run or any observations.

Related JIRA Issues
If this MR closes any JIRA issues list them below in the form Closes PROJECT-#
Pull Request Templates
Switch template by going to preview and clicking the link - note it will not work if you've made any changes to the description.

default.md - for contributions to stable packages.
release.md - for release merge requests.

You are currently using: default.md
Note: these links work by overwriting query parameters of the current url. If the current url contains any you may want to amend the url with &template=name.md instead of using the link. See query parameter docs for more information.

Expose service IP and port as variables in service providers by RodolpheHoudas-UL · Pull Request #1498 · ultraleap/UnityPlugin　を参考にする。


Promote "Metadata in Table Schema" recipe to the specs.

Context and related issue :
fix #899
Details
I tried to be as clear as possible in the constraints associated to the different metadata.
I chose to make a specific section for these properties, as they specifically refer to the schema and not to the data the schema describes, contrary to the other top schema properties. One may argue that the "$schema" property can also be seen as metadata, and could be moved into this section. What do you think ?
I see two points worth mentioning, as they differ from what was in the recipe :

The proposal adds more constraints on the version field and impose semantic versioning (with or without "v" prefix)
The proposal is more restrictive in the name property, and disallows the underscore "_" character. This is aiming at a more URL-friendly name. The current implementation of frictionless allows this character, but as the property was to my knowledge not in the specs, I don't think this can be considered a breaking change.

I'm happy to listen to any requests for modifications.

I'm generally positive about this, and certainly can appreciate its value. One concern is that such expansions to the official specification don't make it less accessible, which I think this PR does in part by placing these additional properties in a separate section. There might be other things that can be done in this regard in the final documentation.
One question: Is there a place where we track the linkage between these metadata properties and other established standards such as Dublin Core? That would make me a bit more comfortable when adding new properties, and would be a great resource when advocating for Frictionless in various contexts.

I generate HTML documentation from Table Schemas in (using Jekyll) in several places (here, here and here), so I support more structured metadata.

Personally, I only needed title, name and description as extra attributes.
Before reviewing, I'd like to see the changes to schema.yaml and how it borrows from the common dictionary. @roll is this something you can add?
version can be useful from a metadata perspective, but note that it can conflict with how we want to handle versioning when referring to a Table Schema. For example: a table schema at https://example.org/1.0/my-table-schema.json (implied to be version 1.0) could contain version: 0.9.
@pschumm "linkage between these metadata properties and other established standards such as Dublin Core" is true for all properties in Data Package and are maybe better defined at the common dictionary level, so they apply to all Data Package elements that use them. In Camtrap DP, I have added those as skos:exactMatch (or alike) properties, see here. Maybe we should open an issue to do discuss this further?

@pschumm "linkage between these metadata properties and other established standards such as Dublin Core" is true for all properties in Data Package and are maybe better defined at the common dictionary level, so they apply to all Data Package elements that use them. In Camtrap DP, I have added those as skos:exactMatch (or alike) properties, see here. Maybe we should open an issue to do discuss this further?

Thanks @peterdesmet; I have just done so with #69.

@pierrecamilleri
Also, thanks to Peter and Phil's comments, a few more thoughts:

we really don't need an additional section for it as it is just normal metadata the same level as fields or missingValues
can you please update profiles/source/dictionary/schema.yaml and run node profiles/build.js to build the user-facing JSON Schemas?

Thanks, I tried my best to take all your comments into account.
Some remarks :

I noticed that you have hidden the recipes, I don't know if I should delete the metadata recipe or not in this PR.
I had difficult times to factorize the JSON Schema, so I preferred to reuse some "common.json" definitions rather than duplicating the data, which can lead to not very accurate descriptions ("descriptor", or "resource" in place of "schema"). I had to adapt specifically some descriptions mentioning a data package, with this vocabulary ; tell me if this is not OK.
In particular, I am not sure about reusing the "sources" from "common.json". The description seems a bit cryptic to me ("The raw sources for this resource.") in the context of a Schema.

Thanks, I tried my best to take all your comments into account.
Some remarks :

I noticed that you have hidden the recipes, I don't know if I should delete the metadata recipe or not in this PR.
I had difficult times to factorize the JSON Schema, so I preferred to reuse some "common.json" definitions rather than duplicating the data, which can lead to not very accurate descriptions ("descriptor", or "resource" in place of "schema"). I had to adapt specifically some descriptions mentioning a data package, with this vocabulary ; tell me if this is not OK.
In particular, I am not sure about reusing the "sources" from "common.json". The description seems a bit cryptic to me ("The raw sources for this resource.") in the context of a Schema.

I noticed that you have hidden the recipes, I don't know if I should delete the metadata recipe or not in this PR

No problem, I'll handle it later

Great work @pierrecamilleri!
Let's wait for voting to complete; my only partial concern currently, the date fields and their possible sync with Data Package

I think it already looks good but I have one question regarding examples - "The “path” property is the URL to the example resource, it MUST be a fully qualified URL as described in RFC 1738." - I would say it's not clear what exactly is expected there. Is it a data file or a Data Resource descriptor?

@khughitt
@PietrH
@pschumm
@ezwelty
@nichtich
Can you please take a look?

Looks good as far as I can judge (via mobile, on vacation).

Hi @pierrecamilleri, can you please update the changelog as well:

It's under v2 / Table Schema heading

##### `name` (new)

##### `title` (new)

##### `description` (new)

##### `homepage` (new)

##### `keywords` (new)

##### `examples` (new)

##### `created` (new)

##### `version` (new)

##### `contributors` (new)

An adjusted [Metadata in Table Schema](https://specs.frictionlessdata.io/patterns/#table-schema-metadata-properties) pattern has been promoted to the standard ([#63](https://github.com/frictionlessdata/datapackage/pull/63)).

I think it already looks good but I have one question regarding examples - "The “path” property is the URL to the example resource, it MUST be a fully qualified URL as described in RFC 1738." - I would say it's not clear what exactly is expected there. Is it a data file or a Data Resource descriptor?

We used to use only data files, but it would make sense that it be a Data Resource descriptor.
I noticed however a technical issue : making it an array of data resources descriptors creates a circular reference in the json schema, as a data resource may itself reference a "schema".
I tried to push some changes (this commit) that references a Data Resource Descriptor without the schema property, I am however afraid that I may have broken things : the expansion of "allOf" does not seem supported by node profiles/build.js. (See here)
Do you have a clue on how I could perform this ?

@pierrecamilleri
TBH For me I would say that example being just data files makes more sense as it's more data publisher centric (a few people if any have some data resources published)

@pierrecamilleri I have a commit with some updated wording and fixing some links. I will commit this in a separate branch for you to review.

Hmm, git is all out of wack it seems. The repository has moved and the access rights have changed. Let's wait until the v2 dust has settled. Still to do on this PR:

[ ] Move table schema to /standards/table-schema.md (cf. main)
[ ] Move changelog to /overview/changelog.md (cf. main)
[ ] Update wording so it aligns with Data Package (my pending PR)
[ ] Update some links
[ ] Fix invalid json example
[ ] Clarify if examples are borrowing title and path from Data Resource (I think they are, included in my PR) or if this is something completely separate.

Thanks for your patience @pierrecamilleri 😄

@@pierrecamilleri
Thanks!
Unfortunately, we must migrate this to the merged spec/datapackage site - https://github.com/frictionlessdata/datapackage. I can assist but it will be great to keep author credits

I rebased this PR on the datapackage repo (see link  right above). Only conflict I had was the moved changelog, hope nothing else has broken.
I also moved the checklist in the pull request description.


ui.router custom type with a child state and full reload from server doesn't work.

I registered a GUID type into my ui-router using an example I followed online:
.config(['$urlMatcherFactoryProvider', function($urlMatcherFactoryProvider) {
  var GUID_REGEXP = /^[a-f\d]{8}-([a-f\d]{4}-){3}[a-f\d]{12}$/i;
  $urlMatcherFactoryProvider.type('guid', {
    encode: angular.identity,
    decode: angular.identity,
    is: function(item) {
      // BUG: item should just be the GUID and not the child url path!!
       return GUID_REGEXP.test(item);
    }
  });

Then I use it in my state like this "/parent/{id:guid}"
This works fine in all scenarios except when there is a child state to the above parent AND the user loads the child state directly by copying the URL in new tab or reloading browser.
The issue is, the is function receives "CD73FAD2-E226-4715-B6FA-14EDF0764162/child" instead of just receiving "CD73FAD2-E226-4715-B6FA-14EDF0764162" and so the regex fails.
Here is a plunker demoing this issue: http://plnkr.co/edit/kdKIG4ies3yuWS1z52f1?p=preview
Try clicking the four links in new tabs and you will notice that only the last 2 with the hard-coded GUID in the state will work and correctly load the state but the first 2 using the new custom type of GUID do not work.

sorry I seem to have missed this bug report.
Thanks for the plunker with easy reproduction.  Here's what's happening:
StateBuilder creates a UrlMatcher for each state.  The UrlMatcher is created by appending the current state's regexp to the parent state's regexp.  The current state's regexp is built by parsing the url property.  When a custom parameter type is encountered, the custom type's regexp is inserted in place of the parameter (in order to match the parameter in the URL).
By default, a custom type's pattern (regexp) is .*.   Your custom type didn't provide any custom pattern, so it was matching the url as .*, and including the /child suffix.  However, when the parameters were validate()ed in transitionTo(), the transition was rejected because the parameter.is() returned false.
The solution is to define a pattern in the custom type that works for your use case.
option 1
Don't match slashes
http://plnkr.co/edit/XRKGGAAZqPsQ8BcBvLAc?p=preview
.config(['$urlMatcherFactoryProvider', function($urlMatcherFactoryProvider) {
  var GUID_REGEXP = /^[a-f\d]{8}-([a-f\d]{4}-){3}[a-f\d]{12}$/i;
  $urlMatcherFactoryProvider.type('guid', {
    encode: angular.identity,
    decode: angular.identity,
    pattern: /[^/]+/,
    is: function(item) {
      // BUG: item should just be the GUID and not the child url path!!
       return GUID_REGEXP.test(item);
    }
  });

option 2
Match exactly GUIDs
http://plnkr.co/edit/82rpitArzhZdQci8yGS8?p=preview
This is probably a better option, but you have to play by the ui-router regexp rules, which means

no capture groups
no ^ or $ (because the regexp is embedded inside another regexp)
no modifiers like /i

.config(['$urlMatcherFactoryProvider', function($urlMatcherFactoryProvider) {
  var GUID_REGEXP = /^[a-f\d]{8}-([a-f\d]{4}-){3}[a-f\d]{12}$/i;
  $urlMatcherFactoryProvider.type('guid', {
    encode: angular.identity,
    decode: angular.identity,
    pattern: /[^/]+/,
    is: function(item) {
      // BUG: item should just be the GUID and not the child url path!!
       return GUID_REGEXP.test(item);
    }
  });


Error when a user tries to Export an API without endpoints

Description:
Error when a user tries to Export an API without endpoints
Steps to reproduce:
Create an API without endpoints.
Import the Created API

Reducing the priority as api creation with endpoints is not a common scenario.


Code cleanup + limit libdef versions to numbers+wildcards

This PR does a few things at once (sorry about that), but the biggest thing is that it no longer allows >= or <= on package version names (only x wildcards).
Also it:

Consolidates validation logic with the logic that scans the /definitions dir for info (DRY cleanup).
Adds jest + tests some of the semver library code

Once this lands, I'll rebase https://github.com/flowtype/flow-typed/pull/23 on top of this and hopefully our path forward will be a little more clear

Hoping to figure out the jest issues before this PR lands. Heading home now, but plan to dig back in later tonight.

I'll take a crack-o-la at it this morning

Alrighty, for now I've slapped a band-aid on the jest issues by just adding node_modules and dist to the paths that Jest won't mock. Now the tests are passing. If we want to invest more time later in debugging jest in combination with request we can, but for now I want to get some stuff DONE!

Nice, upgrading to http://facebook.github.io/jest/blog/2016/04/12/jest-11.html helps out the issues with automocking, which in turn helps out the issues with request

#herostatus


docs: add NGINX Plus

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

@Selflocking

There should be no spaces in the file name. Please rename to NGINX-Plus.md

@SkipperQ You can megre this PR(https://github.com/SkipperQ/casdoor-website/pull/2) to pass these checks.

https://github.com/SkipperQ/casdoor-website/pull/3

@SkipperQ please sign our Contributor License Agreement


Godot 3.2.1 Startup Crash and Missing/Broken Scenes

Godot Engine v3.2.1.stable

GLES3, Intel Mesa Integrated GPU
There was a crash immediately upon opening my project. Before it started crashing it reported missing/broken scenes that were correctly named and in the correct filepath that it was requesting. The backtrace is included here
[I] [faye@acerpred ~] godot --verbose                                            20:46:06
Godot Engine v3.2.1.stable.custom_build - https://godotengine.org
XInput: Refreshing devices.
XInput: No touch devices found.
Detecting GPUs, set DRI_PRIME in the environment to override GPU detection logic.
Only one GPU found, using default.
XcursorGetTheme could not get cursor theme
Using GLES3 video driver
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 630 (KBL GT2)
Audio buffer frames: 341 calculated latency: 7ms

CORE API HASH:<PHONE_NUMBER>1860774635
EDITOR API HASH:<PHONE_NUMBER>3158502407
Loading resource: res://.config/godot/editor_settings-3.tres
EditorSettings: Load OK!
EditorSettings: Save OK!
Loaded builtin certs
Editing project: /home/faye/Games/Dev/Godot/RPG (::home::faye::Games::Dev::Godot::RPG)
Godot Engine v3.2.1.stable.custom_build - https://godotengine.org
EditorSettings: Save OK!
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 630 (KBL GT2)
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x3c3e0) [0x7f08825d43e0] (??:0)
[2] /usr/bin/godot() [0x1b770a4] (??:?)
[3] /usr/bin/godot() [0x234cca9] (??:?)
[4] /usr/bin/godot() [0x234eebd] (??:?)
[5] /usr/bin/godot() [0x234d4b9] (??:?)
[6] /usr/bin/godot() [0x234eebd] (??:?)
[7] /usr/bin/godot() [0x12afd83] (??:?)
[8] /usr/bin/godot() [0x12b1768] (??:?)
[9] /usr/bin/godot() [0x9506e5] (??:0)
[10] /usr/bin/godot() [0x2a866c7] (??:?)
[11] /usr/bin/godot() [0x2a930d5] (??:?)
[12] /usr/bin/godot() [0x2a94180] (??:?)
[13] /usr/bin/godot() [0x1246c7d] (??:?)
[14] /usr/bin/godot() [0x2a86034] (??:?)
[15] /usr/bin/godot() [0x1bae9ba] (??:?)
[16] /usr/bin/godot() [0x1bb8e10] (??:?)
[17] /usr/bin/godot() [0x774a7a] (??:0)
[18] /usr/bin/godot() [0x75cfc1] (??:0)
[19] /usr/bin/godot() [0x74b07d] (??:0)
[20] /usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7f08825bf002] (??:0)
[21] /usr/bin/godot() [0x74d73e] (??:0)
-- END OF BACKTRACE --

I'm unsure of particular steps to reproduce, but the godot project that I had this crash on is included here. The issue persisted even after deleting .import to try and reimport everything.
RPG.zip

Godot Beta v3.2.2.rc1.official crashes in the same manner with nearly the exact same backtrace. Also Godot 4 crashes at startup (without opening the project), which I think is a separate issue

Backtrace
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f0d5f74b210] (??:0)
[2] Node::get_node_or_null(NodePath const&) const (/mnt/Miecz/godot/scene/main/node.cpp:1320)
[3] SceneState::instance(SceneState::GenEditState) const (/mnt/Miecz/godot/scene/resources/packed_scene.cpp:96 (discriminator 4))
[4] PackedScene::instance(PackedScene::GenEditState) const (/mnt/Miecz/godot/scene/resources/packed_scene.cpp:1698)
[5] SceneState::instance(SceneState::GenEditState) const (/mnt/Miecz/godot/scene/resources/packed_scene.cpp:141)
[6] PackedScene::instance(PackedScene::GenEditState) const (/mnt/Miecz/godot/scene/resources/packed_scene.cpp:1698)
[7] EditorNode::load_scene(String const&, bool, bool, bool, bool) (/mnt/Miecz/godot/editor/editor_node.cpp:3426)
[8] EditorNode::_sources_changed(bool) (/mnt/Miecz/godot/editor/editor_node.cpp:689)
[9] MethodBind1<bool>::call(Object*, Variant const**, int, Variant::CallError&) (/mnt/Miecz/godot/./core/method_bind.gen.inc:775 (discriminator 12))
[10] Object::call(StringName const&, Variant const**, int, Variant::CallError&) (/mnt/Miecz/godot/core/object.cpp:922 (discriminator 1))
[11] Object::emit_signal(StringName const&, Variant const**, int) (/mnt/Miecz/godot/core/object.cpp:1249 (discriminator 1))
[12] Object::emit_signal(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) (/mnt/Miecz/godot/core/object.cpp:1307)
[13] EditorFileSystem::_notification(int) (/mnt/Miecz/godot/editor/editor_file_system.cpp:1175 (discriminator 4))
[14] EditorFileSystem::_notificationv(int, bool) (/mnt/Miecz/godot/editor/editor_file_system.h:108 (discriminator 14))
[15] Object::notification(int, bool) (/mnt/Miecz/godot/core/object.cpp:934)
[16] SceneTree::_notify_group_pause(StringName const&, int) (/mnt/Miecz/godot/scene/main/scene_tree.cpp:985)
[17] SceneTree::idle(float) (/mnt/Miecz/godot/scene/main/scene_tree.cpp:525 (discriminator 3))
[18] Main::iteration() (/mnt/Miecz/godot/main/main.cpp:2090)
[19] OS_X11::run() (/mnt/Miecz/godot/platform/x11/os_x11.cpp:3265)
[20] godot(main+0x125) [0x141ab2b] (/mnt/Miecz/godot/platform/x11/godot_x11.cpp:57)
[21] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f0d5f72c0b3] (??:0)
[22] godot(_start+0x2e) [0x141a94e] (??:?)

@FayeAlephNil
Your Heart.tscn and HeartContainer.tscn somehow got corrupted.  It looks like maybe you were trying to make these inherited scenes, but something went wrong in the editor.  If you could reproduce that, then that would be the bug here.
Another thing to note is in these scenes the scripts are built-in, and you do have external scripts, so you might want to attach those.
The corruption here is that the nodes in the TSCN file didn't have types.  I added them as you can see in these highlights.

To get your project running again, you can overwrite these two files over top of what you have.  Then once the editor is running again you might want to try to fix them up from there.
Heart Items.zip

For devs:

The bug might be something to do with scene inheritance corrupting a scene file.
It would be worth adding checks on the parsing of node types to give errors, rather than crashing.

@avencherus Thanks for the help with that! The project is back up and running, but parse errors would definitely be helpful for this kind of thing

@FayeAlephNil Not a problem.  👍  Do you remember anything that might of happened with those scenes that might reproduce the problem?

@FayeAlephNil Not a problem. +1 Do you remember anything that might of happened with those scenes that might reproduce the problem?

Hm, the Heart.tscn and HeartContainer.tscn were being used as resources in Packed Scenes for a loot table system. I then restructured some folder stuff all within the editor. It began to report errors about broken scenes (which I didn't get the debug traces for, sorry), before refusing to launch altogether

Also same crash is shown when trying to run project from Godot 4.0 in Godot 3.2.4 beta 1 -
RegressionTestProject.zip


Tripmode: update zap stanza

I have updated the zap stanza for all the files that I found left after uninstalling.
After making all changes to the cask:

[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name

I also added uninstall signal: stanza. I tested the quit for the app, but didn't work.


Improve Development Experience

We need to review the development process and webpack config for the namada-interface project. As an example, currently, each file update is reloading the page, making really hard to implement UI changes. Would be important to check if we can make the webpack config simpler, and also make improvements to help the whole development experience.

Done in #713.


Support for surrounding basic authentication

We have: oidc implicit flow, IdentityServer4 with asp.net core identity acting as OP. Angular 2 app on top of asp.net core mvc api.
Our reverse proxy (ngins) adds basic authentication to the app, because we want to additionally limit the access to the entire application to a specific set of users/customers, instead of having the app publicly available to everyone - and also because basic auth was the first thing added to secure the early prototypes.
However, when basic authentications is required, oidc-client-js only sets the bearer token authorization header, possibly overriding any authorization header the browser added? I'm not entirely sure how basic authorization works exactly in terms of how the header (or value for it) are added to requests.
Wouldn't it be more correct, to check if an authorization header is already present and add to it (comma separated values iirc) instead of replacing it with just the bearer token authorization header?
See https://github.com/IdentityModel/oidc-client-js/blob/dev/src/JsonService.js#L43

I might have misunderstood how basic authentication works in the browser. It seems to me that each XMLHttpRequest needs to set the headers as the browser will not add any basic authentication to it (or rather: it will get challenged and the next request will still not have the basic authentication header, repeat).
Adding a header for the basic authentication from js would not be useful either since that would defeat the purpose of even having basic authentication (if the authentication is hardcoded) or require yet another page or component where the basic authentication is entered for the js application.
Anyway, it's bad UX if the user has to sign in with two different accounts.
Please correct me if I'm wrong there :)

If you're talking about the user's credentials then yes, you don't want to do both tokens and basic auth.

We have decided to remove Basic Authentication from our application. Thanks


Recurate doyle2011

I have made some changes. Please have a look.

@YojanaGadiya have a look at the last commit. I have made few changes and comments. Ones with confidence medium needs attention.

@trushaadeshara8  added some comments on the "Medium" confidence statements. Have a look.

@sgebel Discussion closed.


Automatic OS updates on Service Fabric Clusters

It looks like Service Fabric now supports automatic OS updates (at least when hosted directly on Azure) as mentioned in the documentation for the patch orchestration page. Should the FAQ section for automatic OS updates be updated to be reflect that?

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

ID: 71869d24-fe49-3b0f-b096-72d0bf515905
Version Independent ID: 9db6765c-b334-5ea5-13e7-aff0c59f4e58
Content: Common questions about Microsoft Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-common-questions.md
Service: service-fabric
GitHub Login: @ChackDan
Microsoft Alias: chackdan

Thanks for the feedback! We are currently investigating and will update you shortly.

Micah, I agree with the suggestion.  Please assign this to aljo

PR 57042 created to update the FAQ's section.
@MicahMcKittrick-MSFT
Please close this.


Change >>> to $ in the documentation

Issue Type

Documentation improvement

Desired Behaviour
For shell commands use the prefix $
Actual Behaviour (Bug report only)
For shell commands >>> prefix is used.
>>>

indicates Python interpreter and $ indicates shell.
I would be happy to send a PR if you like this idea.

Sure, thanks!

Implemented in #1146.


Adding a new Admin/User breaks at 3 max

The bug
As an admin when I create three (3) additional  users. After that, the system throughs an error if you want to create more users.
Steps To Reproduce
Steps to reproduce the behavior:

Go to 'Settings'
Click on 'Users'
Add A New User 'Click Add New User button', and now add more than  three (3) ADMINS until it Barks at you!.
See error

**Illuminate\Database\QueryException**
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 'users.users_slug_unique' (SQL: insert into `users` (`name`, `email`, `password`, `updated_at`, `created_at`) values (xtimx<EMAIL_ADDRESS>$2y$10$3VZvuaT9oG/.O9n7Cs4R../oFLxf7W9cgio0w3IsqyrJ8DGHj2rH6, 2021-06-28 13:45:27, 2021-06-28 13:45:27))
http://bookstack.localhost/settings/users/create

Expected behavior
I expect to have the ability to create as much user/admin as needed without errors.
Screenshots

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v0.31.8
PHP Version:
Hosting Method: Nginx

Additional context
Add any other context about the problem here.

Hi @aroldjacx,
I'm pretty sure your BookStack codebase and database state versions have got muddled here. Have you pehaps done some level of restore or attempted an upgrade to a more recent version? The column reported in the issue thrown was added in a later BookStack release than that shown in your reported version number.

Yes! what I have don is install the latest and now it working. You practically helped solve the issue from your first response. now i am just porting my setting over via the database

THANKS much for your help solider!

@aroldjacx Glad to hear you got things working. Will therefore close this off.


Channels not detected in MPC files

Audio
Format                                   : Musepack SV7
Duration                                 : 2 min 30 s
Bit rate                                 : 130 kb/s
Sampling rate                            : 44.1 kHz
Bit depth                                : 16 bits
Compression mode                         : Lossy
Stream size                              : 2.32 MiB (100%)
Writing library                          : 0.96 Beta

01 - Pumpkin and Honey Bunny (dialogue) - Dick Dale & His Del-Tones , Misirlou.mpc.txt

SV7 support is definitely poor, but no plan on our side to improve it.
Patch accepted ;-).

Not that i don't want, but my C++ skill is too weak :(
If adding one line of code Fill(Stream_Audio, 0, Audio_Channel_s_, Channels);
was suffisant it'll be nice, because this i can do :wink:
That's said, as a workaround i defined 2 channels as a default value ;)

C++ is not the main issue. Main issue is where to locate the channel count in the bitstream. So... You can do it ;-), it is digging in spec (if it exists), questioning people, digging in other code.
If you are sure (link please) that SV7 is stereo only, Fill(Stream_Audio, 0, Audio_Channel_s_, 2); would be enough.

To be honest i thought about it, stereo only, but didn't read any specifications yet. I'll check the FFmpeg code.
Thank you for you advices ;-)
Note: As i guess that will not deserve it's own issue, i prefer add here a RMVB (RealAudio Lossless) similar issue:
luckynight.rmvb.txt

i prefer add here a RMVB (RealAudio Lossless)

I don't like that, because even if the result is same for both the reason and the answer I do, it is 2 different issues, not in the same container so not the same code to change.
Here, RMVB header does not contain any channel info, and "RALF" audio format is not supported.

OK, i understand, i'll not do anymore.


2024-11-01 Custom DC stable release

Highlights:

Pins the version of transformers in nl_requirements.txt
Adds support for a schema update mode in the data management container, documented here. Schema check errors should also now have a direct link to the troubleshooting page.
Updates services container to exit as soon as any of the mixer, NL, or website servers fails to start up

Creating a PR with a branch on a fork instead so new changes to master don't sneak into this PR unexpectedly.


Fix post-install for layout generator

In testing https://github.com/liferay/liferay-js-themes-toolkit/pull/192 I noticed that our post-install gulp task was bombing out after creating a new layout. I went back and established that the same is happening on current "master", due to this change: https://github.com/liferay/liferay-js-themes-toolkit/pull/173
Testing the previous release (v8.0.0-rc.3) confirms that this was a regression.
The way it used to work was that the post-install would run in the directory of the just-generated layout, and the generated gulpfile in that directory pulls in "liferay-plugin-node-tasks" and runs "init".
In the buggy "master" branch, however, we were instead running "init" from "liferay-js-themes-toolkit" (AKA "liferay-themes-sdk"); that is fine for generated themes, but not for generated theme layouts.
So, the fix here is obvious: run the right gulp task.
This commit is a backport from #192 suitable for application to the current "master" branch. See also this issue which describes what I learned about "liferay-plugin-nodes-tasks" while preparing this fix, plus some next steps.
https://github.com/liferay/liferay-js-themes-toolkit/issues/193
Test plan: yo ./packages/generator-liferay-theme/generators/layout

Going to merge this to reduce the number of PRs in flight; will loop back to address any feedback that comes in.


is this supposed to be run on python 2?

it seems that this should be run on python 2, please add in read me if so

I also think this is for python 2, but installation error:       File "c:\users\ares\appdata\local\temp\easy_install-ioi9x4\numpy-1.18.3\setup.py", line 32, in
# these are required to build h5py
RuntimeError: Python version >= 3.5 required.

it seems that this should be run on python 2, please add in read me if so

I am now catching an error to change this code running in Python 2.7 to Python 3.6.
If the code runs in 3.6, can you share it?

I have a version that I modified if you would like to take a look
akoumino/LipNet

I have a version that I modified if you would like to take a look
akoumino/LipNet

Can I receive it by e-mail<EMAIL_ADDRESS>

@jeonsanghun - I think this is what you were after:
https://github.com/akouminov/LipNet
Akouminov had accidentally missed a "v" out of his username name earlier

Hi @akouminov - running your code but running into following error. Any help ?
!./predict evaluation/models/overlapped-weights368.h5 evaluation/samples/id2_vcd_swwp2s.mpg
2020-09-21 02:55:54.328514: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
Loading data from disk...
Data loaded.
WARNING:tensorflow:From /content/LipNet/LipNet/lipnet/model2.py:15: The name tf.keras.backend.set_session is deprecated. Please use tf.compat.v1.keras.backend.set_session instead.
2020-09-21 02:56:04.498704: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2020-09-21 02:56:04.558177: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.558868: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:00:04.0 name: Tesla V100-SXM2-16GB computeCapability: 7.0
coreClock: 1.53GHz coreCount: 80 deviceMemorySize: 15.75GiB deviceMemoryBandwidth: 836.37GiB/s
2020-09-21 02:56:04.558911: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-09-21 02:56:04.558966: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2020-09-21 02:56:04.706921: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-09-21 02:56:04.707073: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-09-21 02:56:04.707102: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2020-09-21 02:56:04.733860: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2020-09-21 02:56:04.733997: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.7
2020-09-21 02:56:04.734122: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.734888: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.735482: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2020-09-21 02:56:04.735846: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX512F
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-09-21 02:56:04.751132: I tensorflow/core/platform/profile_utils/cpu_utils.cc:104] CPU Frequency:<PHONE_NUMBER> Hz
2020-09-21 02:56:04.751413: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x26ffb80 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-09-21 02:56:04.751459: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-09-21 02:56:04.896747: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.897515: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0xb058380 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-09-21 02:56:04.897572: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Tesla V100-SXM2-16GB, Compute Capability 7.0
2020-09-21 02:56:04.898950: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.899536: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:00:04.0 name: Tesla V100-SXM2-16GB computeCapability: 7.0
coreClock: 1.53GHz coreCount: 80 deviceMemorySize: 15.75GiB deviceMemoryBandwidth: 836.37GiB/s
2020-09-21 02:56:04.899621: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-09-21 02:56:04.899659: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2020-09-21 02:56:04.899682: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-09-21 02:56:04.899695: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-09-21 02:56:04.899708: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2020-09-21 02:56:04.899721: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2020-09-21 02:56:04.899734: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.7
2020-09-21 02:56:04.899798: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.900359: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:04.900911: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2020-09-21 02:56:04.906025: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-09-21 02:56:08.762899: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1257] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-09-21 02:56:08.762957: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1263]      0
2020-09-21 02:56:08.762966: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1276] 0:   N
2020-09-21 02:56:08.769087: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:08.769850: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-09-21 02:56:08.770436: W tensorflow/core/common_runtime/gpu/gpu_bfc_allocator.cc:39] Overriding allow_growth setting because the TF_FORCE_GPU_ALLOW_GROWTH environment variable is set. Original config value was 0.
2020-09-21 02:56:08.770503: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1402] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 14756 MB memory) -> physical GPU (device: 0, name: Tesla V100-SXM2-16GB, pci bus id: 0000:00:04.0, compute capability: 7.0)
Traceback (most recent call last):
File "/content/LipNet/LipNet/evaluation/predict.py", line 60, in
video, result = predict(sys.argv[1], sys.argv[2])
File "/content/LipNet/LipNet/evaluation/predict.py", line 53, in predict
y_pred         = lipnet.predict(X_data)
File "/content/LipNet/LipNet/lipnet/model2.py", line 75, in predict
return self.test_function([input_batch, 0])[0]  # the first 0 indicates test
File "/content/LipNet/LipNet/lipnet/model2.py", line 80, in test_function
return K.function([self.input_data, K.learning_phase()], [self.y_pred, K.learning_phase()])
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/backend.py", line 3936, in function
model = models.Model(inputs=inputs, outputs=outputs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py", line 242, in new
return functional.Functional(*args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/training/tracking/base.py", line 457, in _method_wrapper
result = method(self, *args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/functional.py", line 115, in init
self._init_graph_network(inputs, outputs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/training/tracking/base.py", line 457, in _method_wrapper
result = method(self, *args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/functional.py", line 142, in _init_graph_network
base_layer_utils.create_keras_history(self._nested_outputs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer_utils.py", line 191, in create_keras_history
_, created_layers = _create_keras_history_helper(tensors, set(), [])
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer_utils.py", line 226, in _create_keras_history_helper
op = tensor.op  # The Op that created this Tensor.
AttributeError: 'int' object has no attribute 'op'

It can only run on Python 3.5 to Python 3.7 because TensorFlow only supports these versions of python as of October 2020.

It can only run on Python 3.5 to Python 3.7 because TensorFlow only supports these versions of python as of October 2020.

@arindam999 , have run into this before, this is an environment issue, if you still need it I can look into it for you


Extension field not initialized in HOME_POSITION message

Hi,
I've noticed that when receiving HOME_POSITION from fcc the extension field of the message (time_usec) is sometimes filled with garbage values.
I think the problem is that the field is not initialized in mavlink_messages as the other non extension fields of the message :
https://github.com/PX4/Firmware/blob/48df19c8dfa145a16278b48e2aff0a4eda74feda/src/modules/mavlink/mavlink_messages.cpp#L2686

Can you send a PR? Thanks!

@garfieldG , @mhkabir
I went over all messages (with extentions in praticular), and found more issues:
1)
https://github.com/PX4/Firmware/blob/311c0941c995ccc996df2494b4893007af49e6a5/src/modules/mavlink/mavlink_messages.cpp#L3425
Doesn't init chan9_raw-chan18_raw, and should they be 0?

https://github.com/PX4/Firmware/blob/311c0941c995ccc996df2494b4893007af49e6a5/src/modules/mavlink/mavlink_mission.cpp#L371
Here I am not sure. does 'mission_type' isn't being set inside the function and how to fix.

Fixed in https://github.com/PX4/Firmware/pull/11105


ping functions, swap Metro for NPL Website

but come up with a shorter name than "NPL Website". NPL-Web or something...

whoops, wrong repo! intended for BF


The Project Manager's Create Service button clicks but the service can not be created

In GitLab by @luotian-github on Nov 7, 2017, 10:26
If you are reporting a problem, please make sure the following information are provided:

Version of board (last git commit number) , docker engine and docker-compose.
Config files of board, you can get them by packaging "board.cfg" and files in the same directory, including subdirectory.
Log files, you can get them by package the /var/log/board/.
Other necessery information.

Menu location:Project / Create project
Preconditions:
operating:Create a project and delete it, then create a project with the same name
expected results:Project successfully created
actual results:Tips project name already exists

In GitLab by @sokril on Nov 8, 2019, 08:13
closed

In GitLab by @sokril on Nov 8, 2019, 08:13
assigned to @wknet123


Misc fixes

 NOTICE
I dedicate any and all copyright interest in this software to the
public domain. I make this dedication for the benefit of the public at
large and to the detriment of my heirs and successors. I intend this
dedication to be an overt act of relinquishment in perpetuity of all
present and future rights to this software under copyright law.

Fixes: Link to issue
#626

Added bypass for olamovies
Cleaned up some previously added bypasses

[x] I made sure there are no unnecessary changes in the code*
[x] Tested on Chromium- Browser OS
[x] Tested on Firefox

* indicates required

Isn't missing the TLD here?

They have so many of them, the issue mentions ".click", but that's no longer up they now they use ".wtf", so in hopes that the bypass doesn't break in the future I omitted it.

Makes sense.


Make sure ellipsis includes 3 periods

Add third period after "Read more" (EN) and "Leer mas" (ES).

Thanks for your pull request!


occurs check: replace exponential-time algorithm with linear-time one

Builds on #221, because the changes to the OccursCheck error variant would conflict with it if I PR'd it separately. But this is conceptually independent of #221.
Our old occurs-check loop would use the pre-order iterator from dag.rs with the NoSharing adaptor. This would iterate over the full explicit type, which may have exponential size in the program length. The correct algorithm notices when it is done checking a type bound and all its children, and does not check that bound again.
I wasn't able to produce a test vector showing the exponential-time behavior of the old algorithm, but I am hitting this issue in a fuzzing project I'm working on locally, and I think it's clear from the diff what the issue is and how this change fixes it.

Superseded by #221 ?

No, but it needs to be rebased on #221.

Oh, no, I guess I accidentally(?) pulled this commit into #221. It is superseded.


OutOfMemory Error on devices under 2GB of RAM.

Not much to go on, but it might be the AsyncStorage with huge JSONs in memory.
java.lang.OutOfMemoryError:
at java.lang.StringFactory.newStringFromBytes (StringFactory.java:178)
at java.lang.StringFactory.newStringFromBytes (StringFactory.java:54)
at java.lang.StringFactory.newStringFromBytes (StringFactory.java:46)
at com.RNFetchBlob.RNFetchBlobFS.readFile (RNFetchBlobFS.java:225)
at com.RNFetchBlob.RNFetchBlob$6.run (RNFetchBlob.java:227)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
at java.lang.Thread.run (Thread.java:764)

Good thing to check. Did you check the memory usage in AS?
Also, the app is already 19MB which is in the middle of below. Once, running, who knows what happens. Still interesting how some other apps can get by with 3-5MB and essentially already doing all it is supposed to do, check/track for contacts. Is this project over-engineered?

----------------------------------------------------------
Country/Region      AppName                 APK     Size (MB)
----------------------------------------------------------
Israel              Track Virus             1       12
Bolivia             Coronavirus Bolivia     2       24
S.Korea             Self-Diagnosis          3       5
India/Punjab        COVA Punjab             4       6
France/San Martín   CoronaISH               5       44
Singapore           TraceTogether           6       5
Thailand            NCOVI                   7       11
Spain/Catalunia     STOP COVID19 CAT        8       3
UK                  COVID Symptom Tracker   9       43
Israel              "The Shield"/HaMagen    10      22
India               CoWin-20                11      xx
India               Corona Kavach           12      5
India               COVID19 Feedback        13      47
Germany             COVID-19                14      23
----------------------------------------------------------

Feel free to implement a version of the Storage that is not loading memory so much. The current version uses the commonly used react async storage which, if I am not mistaken, needs to load in memory.

Not familiar with this type of storage. Seem a bit weird to abstract away simple SQLite into something that is anyway using SQLite3. But I found this:

https://github.com/react-native-community/async-storage/blob/LEGACY/docs/advanced/IncreaseDbSize.md

Current Async Storage's size is set to 6MB. Going over this limit causes database or disk is full error. This 6MB limit is a sane limit to protect the user from the app storing too much data in the database. This also protects the database from filling up the disk cache and becoming malformed (endTransaction() calls will throw an exception, not rollback, and leave the db malformed). You have to be aware of that risk when increasing the database size. We recommend to ensure that your app does not write more data to AsyncStorage than space is left on disk. Since AsyncStorage is based on SQLite on Android you also have to be aware of the SQLite limits.
Increase limit
Add a AsyncStorage_db_size_in_MB property to your android/gradle.properties:

AsyncStorage_db_size_in_MB=10

Async Storage size is not limited programmatically on iOS.

It's not weird. It's just way simpler than SQLite.
I think what you found refers to the disk space, not memory. Not sure what to do there.

It's not weird. It's just way simpler than SQLite.

Let's just agree to disagree on that. I've had these SQL discussions for almost a decade, and yet, all DBs are still using SQL. Why? Simplicity and clarity.

I think what you found refers to the disk space, not memory. Not sure what to do there.

LoL. Like I said above. If people actually bothered to understand SQL and SQLite3 in particular, you will quickly find that SQLite3 also has memory only implementation and the only relevant limitation is that what was put there by the abstraction layer. I beleiev that the new RockDB or whatever else they had, was to improve performance for non SSD devices.
Anyway, why not just try with the change proposed above?

Well, try and see if you can replicate the bug.
Btw, I have 25 years of SQL experience. In fact, I coded the business logic of an entire ERP in PLSQL, where stored procedures had 5k+ lines and selects with 34joins and sub-sub-sub queries were common. So, relax. I know what SQL is.

@vitorpamplona

So, relax. I know what SQL is.

Yes, I am sure you know your stuff. Please don't take my comments personal. But asking me to replicate something that you experienced, without any info at all how you got that message, is obviously asking the impossible. (From above) How do you even know it came from this app??
Anyway, it's in cases like this, it may be a good idea to implement a simple "debug screen" that the user can copy, to save elsewhere. That screen would contain some limited logcat messages coming from this app.

This is not something I experienced, unfortunately. This comes from the PlayStore Console. The stack is everything it gives us. And happens every day on such devices. So, it seems to be a very common problem (easy to replicate on an emulator, where you can reduce OS memory until it breaks). It's a good practice to first replicate and find where and how it happens before suggesting solutions. And, of course, we can't merge anything without evidence that actually solves the problem.

@vitorpamplona - do the logs give us anything more specific on the particular device?  Make/model, etc?  Wondering how we replicate to verify the fix.

The list is quite big. Most of the budget phones are there. Since this is an OutOfMemory, it can happen on all phones, we just need to load enough info on the memory to trigger similar errors.
Here are the top ones:

Name
Count
%

Pixel 3a (sargo)
8
7.8%

Pixel 3a XL (bonito)
6
5.8%

moto g(7) power (ocean)
6
5.8%

Pixel 3 (blueline)
5
4.9%

LG K10 (2017) (mlv5)
5
4.9%

Galaxy A5(2016) (a5xelte)
4
3.9%

People affected in the last 14 days.

Any of the following should provide you with enough info to track down the problem.
But I suggest to disable all other apps and related background services before using:.

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
https://play.google.com/store/apps/details?id=com.dp.logcatapp
https://play.google.com/store/apps/details?id=scd.lcex
https://play.google.com/store/apps/details?id=com.csgroup.logcat
https://play.google.com/store/apps/details?id=com.tortel.syslog

The issue is in Overlap.js where you pull the public csv dataset from here: https://raw.githubusercontent.com/beoutbreakprepared/nCoV2019/master/latest_data/latestdata.csv
This is over 50MB and is too much to be loading straight into memory. This needs to be buffered and stored somewhere without loading the entire csv into memory. This dataset is only going to get larger.

Overlap.js

Let's see:

each UTF-8 char is 4 bytes
each line can be 900+ chars
we may have ~100 M cases by the end of next month (May).

So someone need to be able to store at least :
4 x 900 x 100,000,000 = 3.6^11 [bytes] = 327 TB

@tstirrat Think we can close this one? I believe the work is in-progress on Jira to improve the overall app performance by reducing payload sizes from HAs.

Let's see:

each UTF-8 char is 4 bytes
each line can be 900+ chars
we may have ~100 M cases by the end of next month (May).

So someone need to be able to store at least :
4 x 900 x 100,000,000 = 3.6^11 [bytes] = 327 TB
Clearly we can't do anything of what was just suggested, without being able to first selectively chose the data to be downloaded. We need to use some kind of tile method like most GPS map apps are using to download only data from tiles where user has been.

On or after my joining Safe Path on April 25, 2020, I brought up this same bottle neck.  Where is data stored for the terra bytes involved?  A NoSQL database that can store highly structured columnar data, key value, etc. is best long term and deploy a master contact tracing app that can scale up across state lines and countries.


Dependabot/bundler/unicode display width 1.4.1

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[x] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

در شنبه ۲۹ دسامبر ۲۰۱۸، ۷:۱۲ Sara<EMAIL_ADDRESS>نوشت:

@Sara8988 approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/explore/pull/507#pullrequestreview-188393636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AsAW_xl6y7owzpkoYoTikedLmnQaUCVAks5u9uSIgaJpZM4ZjN8I
.

?


Add scripts for visual object detection

Uses the TFHub version of SSD on MobileNetV2

Latency on each 1024x768 input image is acceptable: <0.2 s
(CPU inference)

Refactor convert_events_to_tsv_rows into its own module
(events.py), so that it can be reused by audio_events.py
and object_detection.py
Add test images and video file to testdata.
Add command line examples for the detect_objects.py binary to
README.md. Includes example for a video file (e.g., .mp4) as the input
and example for a series of image files (e.g., .jpg files) as the input.

@TeamGleasonDev Any remaining comments or questions about this CL? If not, can we merge it?


Fixes for alex.

What's done
Added a few more words in the allow list. Otherwise latest minor release is breaking the builds.
It's a bit disappointing that their minor releases break it for us: https://github.com/wooorm/alex

Coverage remained the same at 97.361% when pulling 45d1f901139251f829244d4a537b33fe5d0debb9 on alex-fixes into 16d29d097b5112ceb6e759e65cb2478505967d28 on master.

@fahad19 Yeah sorry about that, I didn’t think it would affect to many words! 😬

@wooorm: it's alright! :D thanks for creating alex!


Improved web Camera

Description
Implemented all methods of CameraRef except SetCamera and implemented zoom CameraProps
Checklist

[x] I've read CONTRIBUTING.md
[x] I have tested the new feature

Done, although the lint errors were like: animationDuration: number = 0 should be animationDuration = 0, which I'm personally not a big fan of because it potentially removes the instruction about the specific type for future developers.

Done, although the lint errors were like: animationDuration: number = 0 should be animationDuration = 0, which I'm personally not a big fan of because it potentially removes the instruction about the specific type for future developers.

Thanks, yeah I hear you. I'm not 100% about this lint rule either. I think it's not something we use directly, but we're inheriting it from rn preset, in that case I'd vote for keeping it just for consistency with rn projects, otherwise I'm fine with removing that lint rule.


fix: Fix renovate config file

Description
Fix issue #197 https://github.com/newrelic/newrelic-k8s-metrics-adapter/issues/197
Type of change

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] New feature / enhancement (non-breaking change which adds functionality)
[ ] Security fix
[ ] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] Add changelog entry following the contributing guide
[ ] Documentation has been updated
[ ] This change requires changes in testing:

[ ] unit tests
[ ] E2E tests

Replacing this pr: https://github.com/newrelic/newrelic-k8s-metrics-adapter/pull/203


Exercise 25.1-4

A brute force verification will work. Here is the proof.
Proof of the exercise 25.1-4.pdf

Thanks. Can you attach this link to the solution and pull a request to me? If possible, could you type the solution in markdown in case that the link is broken in the future. Anyway, both is OK to me ^_^


Unable to scan for W3SVC service

I'm trying to run on a WS 2008 R2 and I'm getting this result,
Does anyone know about this?
Unable to scan for W3SVC service
A simple Windows ACMEv2 client (WACS)
Software version <IP_ADDRESS>5 (release, pluggable, standalone, 64-bit)
Connecting to https://acme-v02.api.letsencrypt.org/...
Scheduled task not configured yet
Please report issues at https://github.com/win-acme/win-acme
No scheduled renewals found.

Windows 2008 is not supported anymore by the latest releases. You can try version 2.0.x.


High level action: pull up

An operation that once applied on reactor (so multiple POMs) would "pull up" all versions to parent.
Affected versions:

dependency versions -> "pulled up" as depManagement entries
plugin versions -> "pulled up" as pluginManagement entries

Goal is to not have versions in any child POM.

Yes thanks, generally very useful!
A side note: folks may have good reasons to use a different module for maintaining their properties. A parameter for selecting the target module would be nice.


gradle task assemblerelease failed with exit code 1

Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                     210.7s (!)
Gradle task assembleRelease failed with exit code 1

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      _buildGradleProjectV2 (package:flutter_tools/src/android/gradle.dart:751:5)
<asynchronous suspension>
#2      buildGradleProject (package:flutter_tools/src/android/gradle.dart:494:14)
<asynchronous suspension>
#3      buildApk (package:flutter_tools/src/android/apk.dart:34:9)
<asynchronous suspension>
#4      BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:79:11)
<asynchronous suspension>
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:490:18)
#6      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#7      _rootRunUnary (dart:async/zone.dart:1132:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#12     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#13     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#17     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#18     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#19     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#20     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

I am also facing the same issue on production build

@irfanismaya20 can you provide full log running it with --verbose flag? also please provide your flutter doctor -v output.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of ' flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.

Removing every line from every build.gradle with android.support in it solved this for me.
This is probably caused by some libraries needing androidx instead of android.support dependencies.
In my case this was probably sqflite.


feat: Make list of supported built-in runtime server types overridable

Motivation
Model-mesh serving makes use of a single adapter image to interface with a number of "built-in" model server types, currently comprising triton, mlserver, ovms.
Currently which kind of adapter to run is controlled by the entrypoint to the adapter container within the modelmesh pods, which is set by the controller based on the builtInAdapter.serverType field of the ServingRuntime CRD.
However this is currently validated against a hardcoded list of type strings meaning that any extensions to the runtime adapter image to support new kinds of model servers also require a code change and rebuild of the controller image.
Modifications
Move the list of supported built-in server types to a list in the global config.
Update controller validation logic and tests accordingly.
Result
The shared built-in runtime adapter can be extended to support new runtime types without requiring a code change to the controller.

@chinhuang007 I'm not sure why this is failing the FVTs. I have a feeling it may be a resource constraint thing but I can't see how the changes in the PR could have affected that.

/lgtm


About card not going away when navigating back on desktop

In Desktop platform, user goes in the previous scene by pressing backspace button.
If previously user has opened the about card and then user presses backspace then the about card
doesn't go away.
In VR and HoloLens that user goes back through the menu, then about card goes away

fixed in #118


Eng 766. List bottom up checkpoint status.

Closes ENG-766.
Adding a new CLI method that lists the checkpoint status in bottom up checkpoint submission.

@cryptoAtwill please add a description and title here

This looks close enough to the finish line and it's just non-critical cli code. @aakoshh's comments are all on outdated code, though still open. @aakoshh can we get a re-review?


[BEAM-12106] [zetasql] Support ARRAY type in Java UDF.

Depends on #14746.

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

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

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run SQL PreCommit

Run Java_Examples_Dataflow PreCommit


update typealiases to fix deprecation warnings of julia v0.6.0

Thanks for the great JuliaCon talk. Here is a pretty simple update for v0.6.

@jpfairbanks Thanks for the commit - I've actually prepared a version of Genie that's Julia v0.6 ready but I had to stick it in a branch out of master. Sadly AbstractTrees seems to be broken on v0.6 - I've opened an issue already, hopefully, it will be resolved soon.
Till then we're stuck at v0.5 and these changes can't be applied as they break on 0.5.

Unless you were able to run Genie on v0.6?

I was able to load it.
julia> Pkg.test("Genie")
ERROR: Genie did not provide a test/runtests.jl file