Extend chatflows testsuite

Description
currently only basic scenarios are implemented for 3bot deploy-er test coverage.
Need to extend test suite with unhappy path scenarios
Implementation
current test coverage:
https://github.com/threefoldtech/js-sdk/tree/development/docs/tests/sals/automated_chatflows
Test scenarios:
1- pools

create/extend a pool with 0 units, should success
create/extend a pool with negative units, should fail
create/extend a pool with a non-existing farm, should fail
create/extend a pool with an empty wallet, should fail

2- threebot deployer

deploy a threebot with an expiration on the past, should fail to extend.
deploy a threebot then try to create another one with the same name, should fail
change the location of a running threebot, should fail
change the size of a running threebot, should fail
start a running threebot, should fails
deploy a threebot and check its expiration time should be as the exipration has been set while deploying
deploy a threebot and set ssh key, then ssh to it

3- admin dashboard solutions

deploy an ubuntu container with different versions
deploy an ubuntu with a specific node.
deploy a kubernetes with different sizes
deploy a s3 minio with master/slave setup
deploy a network then add access to it
deploy a network with ipv6
deploy  a network with a specific IP range
create a generic container with a non-exist flist, should fail

1- Pools Done
2- Threebot deployer in progress
3- deploy an ubuntu container with different versions Done

more test scenarios:
1- deploy a container with 0 unit pool.
2- deploy an ubuntu and push the container logs onto an external redis channel.
3- deploy a kubernetes with enable public IP.
4- deploy a container then ssh to it.
5- deploy a s3 minio with SSD and HDD.
6- deploy a s3 minio with a global IPv6 address.
7- expose solution with TRC and NGINX.
8- expose solution with custom domain.
9- deploy virtual machine (happy path).
10- deploy a container with attach an extra volume to the container.
11- deploy a container with environment variables.


HTTP error code

Hi,
first, its a great job!
second, how i can solve for a 416 http when starting a download ?
tnks

Hi @thibaultCha , I am also facing this issue. I my case there is nothing wrong with the url, but instead this error is only shown when the download is complete and you again tries to download the file.
Download Stopped with error Error Domain=com.thibaultcha.tcblobdownload Code=1 "Erroneous HTTP status code 416 (requested range not satisfiable)" UserInfo=0x7fde59dac680 {NSLocalizedDescription=Erroneous HTTP status code 416 (requested range not satisfiable), TCBlobDownloadErrorHTTPStatusKey=416}

Hi,
Can you describe exactly how you got this issue? What I understand reading your comment is that the file was 100% downloaded, and it somehow tried to download the file again, is that it? Or is your code trying to download the file again? (Which would, indeed, probably results in throwing that error)

Hi,
Yes the file was 100% downloaded, and after that when i tried to download it again, i got that error.

That is expected. When the library detects a part of the file (bas on its name) has already been downloaded, it sets the HTTP Range header. Since the range header is here set to the last byte of the file, the server is basically saying there is nothing left to download, thus the range is not satisfiable.
I agree this might be misleading and somehow signalling the file has already been downloaded would be more intuitive. This is a non covered use case.

Okey. Got it.
Thanks :)
Great Work :+1:

I have a question, in my use tcblobdownload ,i think pause download,but i
don't konw use;
also i am an chinese people , i use tcblobdownload don't use chinese


No generator for _build/stage1/libraries/ghc-prim/autogen/GHC/Prim.hs.

Invoking hadrian/build.stack.sh on a fresh copy of GHC results in above error message:
| Remove file _build/stage1/compiler/libHSghc-8.1_p.a
shakeArgsWith   0.000s    0%
Function shake  0.462s   13%  ====
Database read   0.446s   12%  ====
With database   0.013s    0%
Running rules   2.601s   73%  =========================
Total           3.522s  100%
Error when running Shake build system:
* inplace/bin/ghctags
* _build/stage1/compiler/libHSghc-8.1_p.a
* _build/stage1/compiler/GHCi.p_o
* _build/stage1/compiler/GHCi.p_o _build/stage1/compiler/GHCi.p_hi
* _build/stage1/libraries/ghci/GHCi/Message.p_hi
* _build/stage1/libraries/ghci/GHCi/Message.p_o _build/stage1/libraries/ghci/GHCi/Message.p_hi
* _build/stage1/libraries/ghci/GHCi/InfoTable.p_hi
* _build/stage1/libraries/ghci/GHCi/InfoTable.p_o _build/stage1/libraries/ghci/GHCi/InfoTable.p_hi
* _build/stage1/libraries/base/Foreign/C.p_hi
* _build/stage1/libraries/base/Foreign/C.p_o _build/stage1/libraries/base/Foreign/C.p_hi
* _build/stage1/libraries/base/Foreign/C/Types.p_hi
* _build/stage1/libraries/base/Foreign/C/Types.p_o _build/stage1/libraries/base/Foreign/C/Types.p_hi
* _build/stage1/libraries/base/Foreign/Storable.p_hi
* _build/stage1/libraries/base/Foreign/Storable.p_o _build/stage1/libraries/base/Foreign/Storable.p_hi
* _build/stage1/libraries/base/GHC/Int.p_hi
* _build/stage1/libraries/base/GHC/Int.p_o _build/stage1/libraries/base/GHC/Int.p_hi
* _build/stage1/libraries/base/GHC/Arr.p_hi
* _build/stage1/libraries/base/GHC/Arr.p_o _build/stage1/libraries/base/GHC/Arr.p_hi
* _build/stage1/libraries/base/GHC/List.p_hi
* _build/stage1/libraries/base/GHC/List.p_o _build/stage1/libraries/base/GHC/List.p_hi
* _build/stage1/libraries/integer-gmp/GHC/Integer.p_hi
* _build/stage1/libraries/integer-gmp/GHC/Integer.p_o _build/stage1/libraries/integer-gmp/GHC/Integer.p_hi
* _build/stage1/libraries/integer-gmp/GHC/Integer/Type.p_hi
* _build/stage1/libraries/integer-gmp/GHC/Integer/Type.p_o _build/stage1/libraries/integer-gmp/GHC/Integer/Type.p_hi
* _build/stage1/libraries/ghc-prim/GHC/Classes.p_hi
* _build/stage1/libraries/ghc-prim/GHC/Classes.p_o _build/stage1/libraries/ghc-prim/GHC/Classes.p_hi
* OracleQ (ObjDepsKey ("_build/stage1/libraries/ghc-prim/.dependencies","_build/stage1/libraries/ghc-prim/GHC/Classes.p_o"))
* _build/stage1/libraries/ghc-prim/.dependencies
* _build/stage1/libraries/ghc-prim/autogen/GHC/Prim.hs
No generator for _build/stage1/libraries/ghc-prim/autogen/GHC/Prim.hs.

@alexbiehl Thanks! I think this is related to this commit: https://github.com/snowleopard/hadrian/commit/eca7b6a6d9a17e44854cb8f696cec03140052208
Not sure what went wrong, the CI bots were happy. I'll have a look, but in the meanwhile feel free to rollback.
Was this a clean build?

Thanks for the fast response.
Yes, it was (the trace you see was copied from a successive run after the error occurred first)

Very strange. I cannot reproduce this either on my machine or by rerunning the CI bots.
@alexbiehl Could you try again, please? Make sure you do clean build first, and just in case double-check that the _build directory is indeed removed by the clean.

I reverted eca7b6a and it worked. I will try again later with that commit in.

@alexbiehl I was unable to reproduce this. I intend to close this, unless the issue is still relevant for you.


Button onPress not working - RN v0.62 from changelog: "Remove propTypes from TouchableWithoutFeedback."

https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#v0620
This breaks the Button component since utils.extractTouchableProps relies on TouchableWithoutFeedback.PropTypes

Please fix this. I'm using RN 0.65.


[containerapp] az containerapp env dapr-component resiliency: Remove empty dictionary from dapr-component resiliency request payload

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

containerapp


[BUG] - Failed to login using AD users and can login only via clusteradmin

Launched RES portal and was able to successfully login via clusteradmin. However, except clusteradmin unable to view any other users which are created by default in Windows AD launched as part of RES Setup. Tried creating a new AD user and did a sync as mentioned in the documentation via SQS. However, its not working.
Sync between Windows AD created by RES setup and Cognito is not working.

Hi Team,
Issue : AD Users Unable to Log into RES Portal
We are continuing to face problems where only the clusteradmin account is able to log into the RES (Research and Engineering Studio) portal, while Active Directory (AD) users from the Windows AD setup are not recognized.
Recent Steps:

We set up a new server and added another user in Windows AD using the Windows AD server.
Successfully logged into the RES portal using the clusteradmin account.
Created a new AD user and performed a sync as outlined in the documentation using SQS, but the issue persisted.
Attempted to log in to the RES portal using the newly created AD user, but the login failed, and the user was not recognized.

It appears that the synchronization between Windows AD and AWS Cognito is not functioning correctly, preventing AD user logins.

Hi, could you please cut a ticket and provide the required logs? Thanks.

Hi, could you please cut a ticket and provide the cluster manager logs? Thanks.

Hi - I have attached the cluster manager logs for your reference.
log-events-viewer-result-1.txt

Hi there, checked the log and the found following error message: [INVALID_PARAMS] Invalid parameters: email is required.
When adding user in Windows AD server, email is required to successfully sync from AD to RES. Could you try filling in the email, enable the user, trigger AD sync manually and retry login as the user?

The first issue, namely, email field is required for AD account to be syned, was reported on #62
The second issue, namely SSO is required for AD users to work, is discussed at #63. This is very confusing as the documentation seems to suggest otherwise.

Closing the issue now since @BoPeng has already shared the solution. Will follow up on the other issue (https://github.com/aws/res/issues/63) about the documentation.


fix fix comparison with date like

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
#45382 had fix compare date/datev1 with datetime literal wrong cutting.  but it not fix completely.
Notice that datetimev2 literal is datetime literal's child class.  so for datetimev2 literal,  it should also need to check the microseconds.
for example:   date_a  =  '2020-01-01 00:00:00.01' should opt as FALSE, but not date_a = '2020-01-01'.
Release note
None
Check List (For Author)

Test

[ ] Regression test
[x] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

run buildall

run p0


Can now pass -launch-timeout flag instead of always using 30 seconds #43...

...2
Allows users to pass a number of seconds to use for the launch timeout, instead of always defaulting to 30 seconds.
Closes #432
I have finished the CLA form as well.

I have emailed my CLA into the provided email. Looking forward to your comments.

Great, can you rebase?

Rebased

Awesome! Thanks so much! :tada:

CLA is in & good


Source of language corpus

Where is the source text dataset for the Ngrams of those 54 languages? Would like to see if it is different from https://github.com/wooorm/franc/issues/78 usage of UDHR, and if it is more accurate than them.

The source text dataset is not pubiic. It is composed of various sites (Wikipedia for example) selected for the quality of their data to which have been added a number of other websites.

@landrok what about the tools of which the dataset/corups is derived from? If not is it possible to point to other Wikipedia datasets/corpus that are public and similar?

Originally, this tool was designed to route tickets to dedicated teams in an international context.
Subsequently, I decided to offer it under a free license. The tool used to build the different corpus (1-2-3 grams) is a homemade crawler. This is a home-grown development that has undergone various modifications/patches to improve the output datasets. Its code is not clean enough to be released.
Nevertheless, version 2 of the library (currently under development) aims to integrate a learning mechanism and who knows, if time allows me, it is possible that the crawler is added as a plugin.
As for the accuracy of detections, this library has been evaluated in a professional context and its quality has been rather positive, especially for texts longer than 15 characters.
I would be curious to know how accurate it is compared to other libraries in the category. If you feel like it, feel free to do so.

As there is no activity here for more than one year, I'm closing this issue.
Feel free to reopen if needed.


Clone ConnectionWrapper before sending to plugin

Signed-off-by: lobkovilya<EMAIL_ADDRESS>
Description

Motivation and Context

How Has This Been Tested?

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Tested locally
[ ] Have not tested

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@lobkovilya What is this fixing? (I have no objection, but am curious :) )

Closing, since #1625 provides more general solution


Participants.tsv in BIDS: Recommended, Not Required

We (myself and @spieschnik) were checking the bids-example. We encountered an issue while running bids2openminds on the asl003 dataset. Upon further investigation, it appears that the participants.tsv file is not required. As a temporary solution, I propose modifying the code to skip subject creation if the file is not present. Additionally, in the future, I suggest implementing a backup method based on directory patterns to extract this information.

@Peyman-N can you please run asl003 through a BIDS validation to see/share the output of the validation please?

Modality agnostic files (not all) according to the BIDS specifications (human readable one):

dataset_description.json -> REQUIRED
README -> REQUIRED
CITATION.ccf -> RECOMMENDED
CHANGES -> RECOMMENDED (MUST follow CPAN::Changes::Spec)
LICENSE -> RECOMMENDED (MUST be in ASCII or UTF-8 encoding)
participants.tsv, participants.json -> RECOMMENDED
samples.tsv, samples.json -> REQUIRED (if sample-<label> is present)

We can discuss if we actually push people to a MUST participant.tsc/json when they want to convert to openMINDS.

@Peyman-N can you please run asl003 through a BIDS validation to see/share the output of the validation please?

@lzehl Here is the results of BIDS validator. It seems that validator don't care about participants files.

We can discuss if we actually push people to a MUST participant.tsc/json when they want to convert to openMINDS.

I think we should allow conversion to openMINDS for such cases, but we may not accept such datasets in EBRAINS.

We can discuss if we actually push people to a MUST participant.tsc/json when they want to convert to openMINDS.

I think with current structure of openMINDS and its emphasis on subject and subject states, we are implicitly forcing them to do so.

@lzehl Here is the results of BIDS validator. It seems that validator don't care about participants files.

@Peyman-N which fits what I extracted from the human readable BIDS specs. But since validation fails for this example dataset: this also means we should test all example datasets we use to know their behavior in a BIDS validator.


Errors on testnet.ordinals.com

seeing the same thing on my end, mobile and windows browsers.

Let me know and if it works

Still broken for me

Let me know and if it works

Still broken for me

same

We have it running on a too small disk size machine, disk space keeps running out and crashing bitcoind. Will have to upgrade

I've upgraded the server and https://testnet.ordinals.com should be working again

LGTM!


Frequent failures today on the new 5m api calls

Guys, I am seeing frequent failures on the 5m API calls today - these failures seem to stretch way into the defined interval after AEMO prices have been struck.
I am keying off the new estimate flag - starting at 10s into the interval and then retrying each 5s until i get an estimate: false value - i have notice a number of times today this has stretched up to 4m into the interval before i get a good read
I am using node red and same code as previously (for the last two weeks) that was working - just put in place a test/retry loop with a 5s delay for the new functionality as advised by Myles
Problems at your end ?
 You only get 10 a minute

Don’t believe so as I am only asking every 5 seconds – so unless it fails through the whole minute should not be so – I will check the API
From: Myles Eftos @.>
Sent: Thursday, December 12, 2024 2:07 PM
To: amberelectric/public-api @.>
Cc: Craig Curtin @.>; Author @.>
Subject: Re: [amberelectric/public-api] Frequent failures today on the new 5m api calls (Issue #233)
Are you running out of API calls? You only get 10 a minute
—
Reply to this email directly, view it on GitHubhttps://github.com/amberelectric/public-api/issues/233#issuecomment-2537703343, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6OST464BPLF764R2PDJ3T2FD4VJAVCNFSM6AAAAABTO2KWQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXG4YDGMZUGM.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I am not running out of calls - just did a call then in the at 2:28PM (Sydney) and it had 4 or 5 responses where estimate = true - still getting a 200 response code so does not appear to be an issue with numbers of api calls
Resolved after about 4 or 5 attempts - but this was right in the middle of the block
Craig

OK there is another one - Sydney time - 4:55PM call - started at 4:55:20 and retried every 5 seconds - still trying to 4:58 with estimate:true being returned and plenty of API calls left (which actually seem to be 50 over 5m rather than 10/minute ?)
Craig

started at 4:55:20 and retried every 5 seconds - still trying to 4:58 with estimate:true being returned and plenty of API calls left (which actually seem to be 50 over 5m rather than 10/minute ?)

Every final 5m of the 30 is doing that for me. 100% every time.  Reported it last night, so hopefully someone's chasing it.

Good call – had not correlated that – but you are right – it came good as soon as the next ½ block started
From: Rob @.>
Sent: Thursday, December 12, 2024 5:07 PM
To: amberelectric/public-api @.>
Cc: Craig Curtin @.>; Author @.>
Subject: Re: [amberelectric/public-api] Frequent failures today on the new 5m api calls (Issue #233)
started at 4:55:20 and retried every 5 seconds - still trying to 4:58 with estimate:true being returned and plenty of API calls left (which actually seem to be 50 over 5m rather than 10/minute ?)
Every final 5m of the 30 is doing that for me. 100% every time. Reported it last night, so hopefully someone's chasing it.
—
Reply to this email directly, view it on GitHubhttps://github.com/amberelectric/public-api/issues/233#issuecomment-2537896222, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6OST3L4CZ7OBFIHMMSPZ32FERZNAVCNFSM6AAAAABTO2KWQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXHA4TMMRSGI.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Noted. Didn't get to it today unfortunately

OK i havejust put my code back to remove the work around as previously suggested by Rob
Will monitor and send over if it is still failing
Thanks for the quick turnaround.
(Probably got you out of putting up XMAS trees over the weekend !)
Craig

OK here is a failure that is happening at the end of the 30min interval at 4:25-4:29PM in Sydney now
Amber5MinStatus.json
YOu can see the previous ones from today - when it has been working - but i had different code then based on Robs input.
Changed it earlier today when you made the request back to my original working code
Craig

Thanks! That's what I needed.

Same thing this 5m block - 4:55PM - 4:58PM (so far) - AEDT - Sydney - appears to be the same as the previous one

Do back to your work around. Not sure if I'll get it fixed today or not.

OK thanks for the quick response


Attach vegas slider to a div (not BODY)

It would be a nice feature, if it would be possible to attache the slider to a DIV.
e.g: $('mydiv').vegas();
I don't want the slider on the full size BODY tag. I want the slider loaded into a div with width and height.

Hello.
V2 will have this feature.
Released in a few weeks.

perfect!

I'm trying version  2.1.3 and tried to do it an only work for tag 'body' if i change it to '#mydiv' not work!!

Hello Hugo,
Do the Vegas website and the demo work on your browser?
http://vegas.jaysalvat.com/documentation/setup/
http://vegas.jaysalvat.com/demo/

Hi Jay,
 In the website everything is ok, i could see the slideshow in the body

and in the demo box. I've found my basic mistake, after put the start ot
the demo inside a on ready jquery funtion it started working. I supposed
this was not necessary since for body tag it worked without this!!
 Thanks very much for you answer.

 Best regards,
 Hugo Gomes

On Sat, May 30, 2015 at 6:27 PM, Jay Salvat<EMAIL_ADDRESS>wrote:

Hello Hugo,
Do the Vegas website and the demo work on your browser?
http://vegas.jaysalvat.com/documentation/setup/
http://vegas.jaysalvat.com/demo/
—
Reply to this email directly or view it on GitHub
https://github.com/jaysalvat/vegas/issues/69#issuecomment-107067839.

--
Hugo Gomes
URL: www.hmsg.net
Email<EMAIL_ADDRESS>

Great Hugo!
Yes, if you set Vegas before the DOM element is created, it can work.
You can use the jQuery ready solution or set Vegas at the end of the page.
Regards.
__
Jay Salvat
http://www.jaysalvat.com

Le 1 juin 2015 à 11:24, hugomsgomes<EMAIL_ADDRESS>a écrit :
Hi Jay,
In the website everything is ok, i could see the slideshow in the body
and in the demo box. I've found my basic mistake, after put the start ot
the demo inside a on ready jquery funtion it started working. I supposed
this was not necessary since for body tag it worked without this!!
Thanks very much for you answer.
Best regards,
Hugo Gomes
On Sat, May 30, 2015 at 6:27 PM, Jay Salvat<EMAIL_ADDRESS>wrote:

Hello Hugo,
Do the Vegas website and the demo work on your browser?
http://vegas.jaysalvat.com/documentation/setup/
http://vegas.jaysalvat.com/demo/
—
Reply to this email directly or view it on GitHub
https://github.com/jaysalvat/vegas/issues/69#issuecomment-107067839.

--
Hugo Gomes
URL: www.hmsg.net
Email<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub.


HV-1099 Extend tests around @Email constraint

https://hibernate.atlassian.net/browse/HV-1099

updated regex to match quotation inside local parts and added a few more test cases for email validation

Nice work!
Apart from my minor comment on the test pattern, it looks good.
I hope we don't enter a rabbit hole with the IPv6 regexp and the quoted local part :).

Squashed and merged! Thanks!


Feature request: Add a way to disable default formatter for a block of code

I've searched a lot over the internet for a way to prevent the (default) formatter from running on a section of my document and I have found nothing yet... I only found #36797, which asks for the same feature, but was closed and referred to a TypeScript-specific implementation, which does not cover my case.
I'm editing a .html document that mixes CSS, JS, HTML, and a custom template syntax. I need a way to disable the CSS formatter temporarily, and maybe the best option is by using a "comment code" like prettier has (prettier-ignore-begin/end).
Currently, I'm unable to do what I'm trying to do because the formatter messes up my template code.
I'm not using any custom extension that manages CSS, so the problem really lies with the default one. Also, disabling auto-formatting (I'm using formatOnSave) is not an option for me.

For the HTML formatter there's a setting html.format.unformattedContentDelimiter. See here: https://code.visualstudio.com/updates/v1_52#_html
Can you give it a try?

For the HTML formatter there's a setting html.format.unformattedContentDelimiter. See here: https://code.visualstudio.com/updates/v1_52#_html
Can you give it a try?

Thank you. It kinda works as a workaround, but now I have a very large <script> that I'll need to format manually...
For the time being it is acceptable, but I don't think it is enough to close this issue since the feature request still stands.


Updating from master

Codecov Report

Merging #52 into master will decrease coverage by 0.96%.
The diff coverage is 29.41%.

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage   46.67%   45.71%   -0.97%
==========================================
  Files           4        4
  Lines         632      665      +33
  Branches       64       65       +1
==========================================
+ Hits          295      304       +9
- Misses        324      346      +22
- Partials       13       15       +2

Impacted Files
Coverage Δ

mws/mws.py
43.73% <28.57%> (-0.87%)
:arrow_down:

mws/utils.py
69.44% <33.33%> (-2.41%)
:arrow_down:

Continue to review full report at Codecov.

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


[posm]: extra data encoded in params should not be allowed

Component
Position Manager
Describe the suggested feature and problem it solves.
there is no error thrown if there is more data encoded into params ie (Actions.DECREASE, abi.encode(tokenId, poolPos, 10_000 ether, ZERO_BYTES, false) still runs and passes tests
Describe the desired implementation.
No response
Describe alternatives.
No response
Additional context.
No response

fine behavior, closing


Hotfix: Sending tokens 10s only sends 1 because trailing zeros are stripped

For posterity. Already merged into master with #2436
Supersedes #2438

Not to be merged

Not to be merged

Submitted hotfix as 3.13 (369)

Submitted hotfix as 3.13 (369)


Not seeing new APM service in Elastic when using the extension

I'm attempting to use the apm-aws-lambda manual installation alongside the elastic-apm-node package.
Expectation
After instrumenting both apm-aws-lambda and elastic-apm-node for a lambda handler, I'm invoking this handler in hopes that I see a new service inside the APM > Services section of our Elastic dashboard.
Reality
I'm not seeing a new service inside the APM > Services section or our Elastic dashboard. However, I do see the extension's logs in the handler's log group.
Details
To set this up, I followed the Manual Installation section of the AWS Lambda Extension docs.
I downloaded the x86_64 version of the extension zip and uploaded to AWS. I set compatible runtimes for this layer to nodejs12.x. I configured the handler to use this layer, and it appears to be doing so based on the Cloudwatch logging.
Based on the Configure your Environment Variables section of the docs, I set these environment variables for the handler:

ELASTIC_APM_CENTRAL_CONFIG: false
ELASTIC_APM_CLOUD_PROVIDER: none
ELASTIC_APM_LAMBDA_APM_SERVER: https://xxxxxxxx.elastic-cloud.com:9243
ELASTIC_APM_API_KEY: xxxxxxxxxxxxxx
ELASTIC_APM_SERVER_URL: http://localhost:8200

We are also using the value for the ELASTIC_APM_LAMBDA_APM_SERVER variable in a different service (Fargate), and that is working as expected since we are seeing that service name populate in the APM > Services section of our Elastic dashboard.
For the ELASTIC_APM_API_KEY value, we created a brand new API key in Elastic and set the variable to the base64 version of this value. We did not update any permissions on the API key and created it with all default settings.
Inside the handler, we have set up elastic-apm-node like so:
const apm = require('elastic-apm-node').start({
  apiKey: process.env.ELASTIC_APM_API_KEY,
  serverUrl: process.env.ELASTIC_APM_LAMBDA_APM_SERVER
});

exports.handler = apm.lambda(async function (event) {
    ...
});

The logs for a single handler invocation are fairly short and seem to provide some details that indicate the extension is working. Here are the complete logs with some private details omitted:
--
START RequestId: xxxxxxxxxxxxxxxxx Version: $LATEST
2022/01/19 14:01:30 xxxxxxxxxxxxxxxxx
2022/01/19 14:01:30 Register response: {
"functionName": "xxxxxxxxxxxxxxxxx",
"functionVersion": "$LATEST",
"handler": "index.xxxxxxxxxxxxxxxxx.handler"
}
2022/01/19 14:01:30 Could not read ELASTIC_APM_DATA_RECEIVER_TIMEOUT_SECONDS, defaulting to 15: strconv.Atoi: parsing "": invalid syntax
2022/01/19 14:01:30 Extension listening for apm data on :8200
LOGS	Name: apm-lambda-extension	State: Subscribed	Types: [platform]
2022/01/19 14:01:30 Waiting for next event...
2022/01/19 14:01:30 Server listening for logs data from AWS Logs API on sandbox:1234
EXTENSION	Name: apm-lambda-extension	State: Ready	Events: [INVOKE,SHUTDOWN]
2022/01/19 14:01:31 Received event: {
"eventType": "INVOKE",
"deadlineMs":<PHONE_NUMBER>931,
"requestId": "xxxxxxxxxxxxxxxxx",
"invokedFunctionArn": "arn:aws:lambda:xxxxxxxxxxxxxxxxx",
"tracing": {
"type": "X-Amzn-Trace-Id",
"value": "Root=1-61e819b7-5d9e8dd4158fe1886c76e76f;Parent=58b2c1345e804c91;Sampled=1"
}
}
2022/01/19 14:01:31 Checking for agent data
2022/01/19 14:01:31 No agent data on buffer
2022/01/19 14:01:31 Received log event platform.logsSubscription
2022/01/19 14:01:31 Received log event platform.start
2022/01/19 14:01:31 Received log event platform.extension
2022-01-19T14:01:32.029Z	xxxxxxxxxxxxxxxxx	INFO xxxxxxxxxxxxxxxxx
2022/01/19 14:01:33 Adding agent data to buffer to be sent to apm server
END RequestId: xxxxxxxxxxxxxxxxx
REPORT RequestId: xxxxxxxxxxxxxxxxx	Duration: 1918.42 ms	Billed Duration: 1919 ms	Memory Size: 128 MB	Max Memory Used: 122 MB	Init Duration: 1591.33 ms	XRAY TraceId: xxxxxxxxxxxxxxxxx	SegmentId: 58b2c1345e804c91	Sampled: true

Based on the above, does it look like we are misconfiguring something here?
Thanks for the help!

Thanks for giving the Lambda extension a try @rpivovar-godaddy and for the detailed information about your configuration.  Let's see what we can do to get you up and running.
Looking over your configuration the first thing that pops out is this
const apm = require('elastic-apm-node').start({
  apiKey: process.env.ELASTIC_APM_API_KEY,
  serverUrl: process.env.ELASTIC_APM_LAMBDA_APM_SERVER
});

I would expect to see something more like
const apm = require('elastic-apm-node').start({});

That is, you shouldn't need to configure these variables when using the Node.js agent in Amazon Lambda.
With the Lambda extension it's intended that you configure your agent values via the Environment Variables tab in Lambda.  While you can set additional values via the agent's start method, it's a little too easy to accidentally overwrite a value. With the configuration you included, the agent was trying to send data directly to your APM Server endpoint instead of the extension.
More Details: Sending data directly to APM Server doesn't always work with Lambda -- if the HTTP request to send the data takes longer than the Lambda's freeze or shutdown phases, the data won't be sent.  It's not obvious, but this is why APM vendors need to use an extension based solution in the first place.
The agent actually needs to send data to http://localhost:8200 URL (which is the extension) and then the extension forwards it on to the https://xxxxxxxx.elastic-cloud.com:9243 URL.  Without getting too deep into the Amazon internals, Lambda Extensions have special permission to run in the background so they avoid the problems that come with posting data directly to a server.
Your Environment Variables tab looks correct. So, to start, I'd say let's get those fields out of the start method and give it another try.  I believe that will clear up your problem.  If it doesn't let us know what you're seeing in the logs and we'll get you up and running ASAP.

Thanks @astorm for the explanation and the help -- that makes sense. I think I'm a little further now, but still not seeing the new service show up in the APM dashboard.
Based on logs, it looks like the payloads are going to the right place now, but it looks like I'm failing authentication.
Below are the logs for several invocations within a 5-minute period.
START RequestId: xxxxxxxxxxxxx Version: $LATEST
--
2022/01/19 16:44:09 Received log event platform.runtimeDone
2022/01/19 16:44:09 Received runtimeDone event for this function invocation
2022/01/19 16:44:09 Received runtimeDone signal
2022/01/19 16:44:09 Checking for agent data
2022/01/19 16:44:09 No agent data on buffer
2022/01/19 16:44:09 Waiting for next event...
2022/01/19 16:48:24 Error sending to APM server, skipping: failed to post to APM server: Post "https://xxxxxxxxxxxxx.elastic-cloud.com:9243/intake/v2/events": net/http: TLS handshake timeout
2022/01/19 16:48:24 funcDone signal received, not processing any more agent data
2022-01-19T16:48:24.818Z	0f6182f3-7eb5-4a0d-8012-cb58e5ca9f6c	INFO	xxxxxxxxxxxxx
2022/01/19 16:48:24 Received event: {
"eventType": "INVOKE",
"deadlineMs":<PHONE_NUMBER>811,
"requestId": "xxxxxxxxxxxxx",
"invokedFunctionArn": "arn:aws:lambda:xxxxxxxxxxxxx",
"tracing": {
"type": "X-Amzn-Trace-Id",
"value": "Root=1-61e840d8-33d3a4d348a2ed7a1c879d29;Parent=7bba51a71b0dff24;Sampled=1"
}
}
2022/01/19 16:48:24 Checking for agent data
2022/01/19 16:48:24 No agent data on buffer
2022/01/19 16:48:24 Received log event platform.end
2022/01/19 16:48:25 Received log event platform.report
2022/01/19 16:48:25 Received log event platform.start
2022/01/19 16:48:25 Adding agent data to buffer to be sent to apm server
2022/01/19 16:48:26 Received log event platform.runtimeDone
2022/01/19 16:48:26 Received runtimeDone event for this function invocation
2022/01/19 16:48:26 Received runtimeDone signal
2022/01/19 16:48:26 Checking for agent data
2022/01/19 16:48:26 No agent data on buffer
2022/01/19 16:48:26 Waiting for next event...
END RequestId: xxxxxxxxxxxxx
REPORT RequestId: xxxxxxxxxxxxx	Duration: 1226.03 ms	Billed Duration: 1227 ms	Memory Size: 128 MB	Max Memory Used: 121 MB	XRAY TraceId: 1-61e840d8-33d3a4d348a2ed7a1c879d29	SegmentId: 7bba51a71b0dff24	Sampled: true
START RequestId: xxxxxxxxxxxxx Version: $LATEST
2022/01/19 16:48:29 Received event: {
"eventType": "INVOKE",
"deadlineMs":<PHONE_NUMBER>458,
"requestId": "xxxxxxxxxxxxx",
"invokedFunctionArn": "arn:aws:lambda:xxxxxxxxxxxxx",
"tracing": {
"type": "X-Amzn-Trace-Id",
"value": "Root=1-61e840dd-44a171e14f071e9b46a23664;Parent=0e351b8a33c58434;Sampled=1"
}
}
2022/01/19 16:48:29 Checking for agent data
2022/01/19 16:48:29 No agent data on buffer
2022/01/19 16:48:29 Received log event platform.end
2022/01/19 16:48:29 Received log event platform.report
2022/01/19 16:48:29 Received log event platform.start
2022-01-19T16:48:30.037Z	xxxxxxxxxxxxx	INFO	xxxxxxxxxxxxx
2022/01/19 16:48:30 Adding agent data to buffer to be sent to apm server
2022/01/19 16:48:30 Received log event platform.runtimeDone
2022/01/19 16:48:30 Received runtimeDone event for this function invocation
2022/01/19 16:48:30 Received runtimeDone signal
2022/01/19 16:48:30 Checking for agent data
2022/01/19 16:48:30 No agent data on buffer
2022/01/19 16:48:30 Waiting for next event...
END RequestId: xxxxxxxxxxxxx
REPORT RequestId: xxxxxxxxxxxxx	Duration: 1379.28 ms	Billed Duration: 1380 ms	Memory Size: 128 MB	Max Memory Used: 123 MB	XRAY TraceId: 1-61e840dd-44a171e14f071e9b46a23664	SegmentId: 0e351b8a33c58434	Sampled: true
START RequestId: xxxxxxxxxxxxx Version: $LATEST
2022/01/19 16:48:32 Received event: {
"eventType": "INVOKE",
"deadlineMs":<PHONE_NUMBER>096,
"requestId": "xxxxxxxxxxxxx",
"invokedFunctionArn": "arn:aws:lambda:xxxxxxxxxxxxx",
"tracing": {
"type": "X-Amzn-Trace-Id",
"value": "Root=1-61e840e0-2b90f02b2444501a4c47c867;Parent=225fb9bb1ff7efa7;Sampled=1"
}
}
2022/01/19 16:48:32 Checking for agent data
2022/01/19 16:48:32 No agent data on buffer
2022/01/19 16:48:32 Received log event platform.end
2022/01/19 16:48:32 Received log event platform.report
2022-01-19T16:48:32.097Z	3d07a330-8dd1-4ae8-8399-2a493ca40e84	INFO	xxxxxxxxxxxxx
2022/01/19 16:48:32 APM server response body: {     "error": "authentication failed" }

2022/01/19 16:48:32 APM server response status code: 401
2022/01/19 16:48:32 funcDone signal received, not processing any more agent data
2022/01/19 16:48:32 APM server response body: {     "error": "authentication failed" }

2022/01/19 16:48:32 APM server response status code: 401
2022/01/19 16:48:32 funcDone signal received, not processing any more agent data
2022/01/19 16:48:32 Received log event platform.start
2022/01/19 16:48:32 Adding agent data to buffer to be sent to apm server
2022/01/19 16:48:32 APM server response body: {     "error": "authentication failed" }

2022/01/19 16:48:32 APM server response status code: 401
2022/01/19 16:48:32 Received log event platform.runtimeDone
2022/01/19 16:48:32 Received runtimeDone event for this function invocation
2022/01/19 16:48:32 Received runtimeDone signal
2022/01/19 16:48:32 Checking for agent data
2022/01/19 16:48:32 No agent data on buffer
2022/01/19 16:48:32 Waiting for next event...
2022/01/19 16:48:32 funcDone signal received, not processing any more agent data
END RequestId: xxxxxxxxxxxxx
REPORT RequestId: xxxxxxxxxxxxx	Duration: 287.92 ms	Billed Duration: 288 ms	Memory Size: 128 MB	Max Memory Used: 123 MB	XRAY TraceId: 1-61e840e0-2b90f02b2444501a4c47c867	SegmentId: 225fb9bb1ff7efa7	Sampled: true

We are using version 7.15.2 of Elastic -- it looks like the API key should work for this version.
I also followed along with this thread "401 Unathorized when trying to call the Kibana API" which looked like a similar issue.
I tried making this curl request from the thread:
curl -v --location --request GET 'https://xxxxxxxxxxxxx.elastic-cloud.com:9243/_security/_authenticate' \
--header 'Authorization: ApiKey xxxxxxxxxxxxx'

And got this response:
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to xxxxxxxxxxxxx.elastic-cloud.com (xxxxxxxxxxxxx) port 9243 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.xxxxxxxxxxxxx.elastic-cloud.com
*  start date: Jan 11 00:02:20 2022 GMT
*  expire date: Apr 11 00:02:19 2022 GMT
*  subjectAltName: host "xxxxxxxxxxxxx.elastic-cloud.com" matched cert's "*.xxxxxxxxxxxxx.elastic-cloud.com"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fedda009200)
> GET /_security/_authenticate HTTP/2
> Host: xxxxxxxxxxxxx.elastic-cloud.com:9243
> User-Agent: curl/7.64.1
> Accept: */*
> Authorization: ApiKey xxxxxxxxxxxxx
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 404
< content-type: application/json
< date: Wed, 19 Jan 2022 16:38:12 GMT
< x-cloud-request-id: 1eEQ61amSCapsK0nb2UJqA
< x-content-type-options: nosniff
< x-found-handling-cluster: 1a098c00d32543fd95fe7ad5ec57cfce
< x-found-handling-instance: instance-0000000002
< content-length: 36
<
{
  "error": "404 page not found"
}
* Connection #0 to host xxxxxxxxxxxxx.elastic-cloud.com left intact
* Closing connection 0

Not 100% sure the meaning of this response. I'll also add that this API key was made from my user account, and I do not have superuser permissions in Elastic (I can't view Users/Roles/Role Mappings in the dashboard).
It looks like there is an authentication issue with my API key.

It looks like there is an authentication issue with my API key.

@rpivovar-godaddy  Agreed -- just for completeness the following logs indicate an authentication error.
2022/01/19 16:48:32 APM server response status code: 401
2022/01/19 16:48:32 funcDone signal received, not processing any more agent data
2022/01/19 16:48:32 APM server response body: {     "error": "authentication failed" }

That's an HTTP status code of 401, which indicates the request is Unauthorized.
So I think I see the next problem with your Lambda configuration, and then a second problem with the ElasticSearch API URL you're using.  I'm going to cover each separately.
Re: next steps Lambda configuration
Looking over the latest information you sent over and re-reading your previous post, I think I see another issue/point-of-confusion.
The ELASTIC_APM_LAMBDA_APM_SERVER value should point at your APM Server endpoint and NOT your ElasticSearch API endpoint.  These are two different URLs
The port you have in your value (9243) makes me believe this is your Elastic API endpoint and NOT your APM Server endpoint.   You can get your APM Server endpoint by navigating to
Cloud -> Deployments -> [Specific Deployment]

and then looking at the applications section

If you click on the Copy Endpoint link next to APM you'll copy the APM Server endpoint to your clipboard, and can paste it in to the ELASTIC_APM_LAMBDA_APM_SERVER value in your environment configuration.
Does that make sense/get you pointed in the right direction?
Re: your API Key
I saw you tried to test your API key by making an API request to an ElasticSearch API endpoint via curl
curl -v --location --request GET 'https://xxxxxxxxxxxxx.elastic-cloud.com:9243/_security/_authenticate' \
--header 'Authorization: ApiKey xxxxxxxxxxxxx'

and got back
{
  "error": "404 page not found"
}

This also confuses me.  I would expect you to receive either a response that listed your credentials -- something like this
% curl --location --request GET 'https://xxx.us-east-1.aws.found.io:9243/_security/_authenticate' \
--header 'Authorization: ApiKey yyy'

{
  "username": "someusername",
  "roles": [],
  "full_name": "Bob Jenkins",
  "email"<EMAIL_ADDRESS>  "metadata": {},
  "enabled": true,
  "authentication_realm": {
    "name": "_es_api_key",
    "type": "_es_api_key"
  },
  "lookup_realm": {
    "name": "_es_api_key",
    "type": "_es_api_key"
  },
  "authentication_type": "api_key"
}

or to get back an unauthorized response.
{
  "error": {
    "root_cause": [
      {
        "type": "security_exception",
        "reason": "missing authentication credentials for REST request [/_security/_authenticate]",
        "header": {
          "WWW-Authenticate": [
            "Basic realm=\"security\" charset=\"UTF-8\"",
            "Bearer realm=\"security\"",
            "ApiKey"
          ]
        }
      }
    ],
    "type": "security_exception",
    "reason": "missing authentication credentials for REST request [/_security/_authenticate]",
    "header": {
      "WWW-Authenticate": [
        "Basic realm=\"security\" charset=\"UTF-8\"",
        "Bearer realm=\"security\"",
        "ApiKey"
      ]
    }
  },
  "status": 401
}

The fact that your response is a 404 page not found makes me wonder if https://xxxxxxxxxxxxx.elastic-cloud.com:9243 is the correct URL, and if it is the correct URL it would make me wonder if the computer your made the request from has access to that URL (routing, firewalls, etc.)  This specific issue with xxxxxxxxxxxxx.elastic-cloud.com:9243 might be better handled by our traditional support channels -- I'm not sure how you'all have your cluster(s) setup/configured and even if I did I don't have access to those particular levers :)
That said, let me know if the APM Server info about clears up your problem or not.

Hi @astorm -- following up here. apm-aws-lambda does work with elastic-apm-node after making the above fixes. I do see our app showing up in APM. I'm still having an issue with secrets, which I will share on #105. Feel free to close this issue. Thanks again for the help.


mono: more fixes and update gtk-sharp/gnome-sharp

Motivation for this change
Follow on to #52712
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I also note that dbus-sharp and mono-addins are still on mono4 because of https://github.com/mono/dbus-sharp/issues/64. gnome-sharp has a different error.

Cc @kuznero @Mic92 @thoughtpolice @vrthra @jraygauthier @avnik @ciil
Will merge in ~12 hours if no objections.

lgtm, built and tested for pdfmod. I'd suggest you just merge this and close  #52484.


Easier includes / excludes for JacocoReportBase

Currently it is pretty cumbersome to exclude classes from being reported on.
You need solutions like shown here: https://stackoverflow.com/questions/29887805/filter-jacoco-coverage-reports-with-gradle
It would be nice if JacocoReportBase would allow to set includes and excludes and then properly applies them internally.
Even nicer would additionally be a way to exclude by source directories, so you can easily exclude generated sources.

Just FYI: jacoco automatically ignores a lot of cases itself including anything annotated ‘@Generated’ (Matches on the name of the annotation). See also https://github.com/jacoco/jacoco/wiki/FilteringOptions

Unfortunately this doesn't help at all.
The typical @Generated annotations (javax.annotation.Generated and javax.annotation.processing.Generated) that are used by normal code-generation tools have retention SOURCE.
The "invisible" on the page you linked is pretty misleading.
It only means retention CLASS, so only RUNTIME and CLASS are considered.
So I would need to post-process all generated files to add an additional @Generated annotation that has not retention SOURCE.
JaCoCo will not improve regarding this point, as they only process bytecode and do not do source parsing.


fix connection count on SignalConnection disconnect

The connection count doesn't decrement when calling disconnect() on a SignalConnection. Let me know if you'd like it implemented differently, happy to amend.

Sorry, was on vacation. Looks good to me. Thanks!
I'll do a dependency update chore on my repositories soon, this fix will be released during that process.

@cmandlbaur 2.5.0 has been released. Sorry about the delay, I've been out sick.


ML.NET November 2022 Doc Updates

Deep Learning (dotnet/machinelearning#6393)

[ ] Concepts - What is Deep Learning? (P0)
[ ] Tutorial - Text Classification (P0)
[ ] Tutorial - Sentence Similarity (P1)

AutoML (#32011)

[ ] Overview - Automated ML (P0)

What is AutoML?

What is FLAML?

What can I do with AutoML?

[ ] How-To - Use Automated ML API (P0)

ColumnInference
Featurizer
Experiment
Sweepable API
Search Space API

Model Builder

[ ] Conceptual documentation up to date

[ ] What is Model Builder and how does it work?

[ ] Tutorials up to date

[ ]  Regression: Predict prices
[ ] Binary: Analyze sentiment
[ ] Multiclass: Classify health violations
[ ] Image classification: Landsat image classification
[ ] OD: Detect traffic signs
[ ] Recommendation: movie recommendations

[ ] All references point to VS2022
[ ] Install docs up to date

CLI

[ ] All references point to latest version
[ ] Install docs up to date

Related to #32112


chore: prepare v9.1.5 release

Draft PR to see CI green before tagging/publishing.

Green:

https://travis-ci.org/liferay/liferay-js-themes-toolkit/builds/549620092
https://travis-ci.org/liferay/liferay-js-themes-toolkit/builds/549620515


feat!: core8

[skip-validate-pr]
I'm not sure how current your pipelines are and whether the ! will major bump it.  If not, please bump the pjson version as needed.

Hi @mshanemc can you guys go ahead with beta release of this module like you did last time. This will unblock you and also let us not rush with core v8 upgrade. We are planning to work on v8 upgrade this iteration, so that will likely go out in our next week's release or after that depending on how big the change is.


Support Emacs-like three-state recenter

In emacs, successively pressing ctrl+l move the caret between three states: caret at the center, caret at the top, caret at the bottom. It would be useful to have such a feature: it makes the extension more powerful, without making UI more complicated.

@matklad Here's your late christmas present: b8669cde7a9b5cbdc80ae41290484956b5686ad6, feature is published in the marketplace. It's not enabled by default, you need to set center-editor-window.threeStateToggle to true.
As far as my Emacs memories go back, it was possible to set an explicit offset of lines when moving top or bottom, implementing this as well will be my next logical step. Anything else missing?

Ohhh, works flawlessly @kaiwood !!
Thank you very much!

Anything else missing?

No, I don't remember any other features except for explicit offset.


Roundup: [oss-security] Re: CVE Request: Irssi use after free in netjoin condition (2017/03)

Here is a report from the oss-security mailing list for Vulnerability Roundup 27.
Skip to First Email
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable. Then determine if we are vulnerable, and make a comment with your findings. It can also be helpful to specify if you think there is a patch, or if it can be fixed via a general update.
Example:
unstable: we are not vulnerable (link to the package)
17.03: we are vulnerable (link to the package)
16.09: we don't have it packaged

IMPORTANT: If you believe there are possibly related issues, bring them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch. This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue for the roundup.
If you commit the patch directly to a branch, please leave a comment on this issue with the branch and the commit hash, example:
fixed:

release-16.09: abc123

Skip to First Email
Upon Completion ...

[ ] Update Graham's database

Info
Triage Indicator:
-needs-triage +roundup27 thread:0000000000004135

File Search: https://search.nix.gsc.io/?q=irssi&i=fosho&repos=nixos-nixpkgs
GitHub Search: https://github.com/NixOS/nixpkgs/search?utf8=✓&q=irssi+in%3Apath&type=Code

Should the search term be changed from irssi? Suggest a new package search by commenting:
-suggested:irssi +suggested:correctPackageName thread:0000000000004135

Known CVEs: CVE-2017-7191

Skip to End
Sat, 11 Mar 2017 22:25:55 +0100 Ailin Nemui <ailin.nemui-at-gmail.com><EMAIL_ADDRESS>Dear CVE Assignment Team,

please provide CVE for the following issue:

use after free condition during netjoin processing [1]
======================================================
CWE Classification: CWE-416

Description
-----------

Use after free while producing list of netjoins (CWE-416)

This issue was found and reported to us by APic.

Impact
------

This issue usually leads to segmentation faults. Targeted code
execution should be difficult.

Affected versions
-----------------

Irssi up to and including 1.0.1

We believe Irssi 0.8.21 and prior are not affected since a different
code path causes the netjoins to be flushed prior to reaching the use
after free condition.

Fixed in
--------

Irssi 1.0.2

Recommended action
------------------

Upgrade to Irssi 1.0.2. Irssi 1.0.2 is a maintenance release
without any new features.

Patch
-----

https://github.com/irssi/irssi/commit/77b2631c78461965bc9a7414aae206b5c
514e1b3

References
----------

[1] https://irssi.org/security/irssi_sa_2017_03.txt

Skip to End

Sun, 12 Mar 2017 10:45:03 +0100 Emilio Pozuelo Monfort <pochu27-at-gmail.com><EMAIL_ADDRESS>On 11/03/17 22:25, Ailin Nemui wrote:
> Dear CVE Assignment Team,
>
> please provide CVE for the following issue:

Please report these through http://cveform.mitre.org/ to get CVEs assigned, and
follow up here with the CVE identifiers after that's done.

Thanks,
Emilio

Skip to End

Mon, 20 Mar 2017 16:33:17 +0100 Ailin Nemui <ailin.nemui-at-gmail.com><EMAIL_ADDRESS>On Sat, 2017-03-11 at 22:25 +0100, Ailin Nemui wrote:
> Dear CVE Assignment Team,
>
> please provide CVE for the following issue:
>
> use after free condition during netjoin processing [1]
> ======================================================

-------- Forwarded Message --------
From<EMAIL_ADDRESS>Subject: Re: [scr308011] Irssi - 1.0.0, 1.0.1
Date: Mon, 20 Mar 2017 09:14:07 -0400

Use CVE-2017-7191.

--
CVE Assignment Team
M/S M300, 202 Burlington Road, Bedford, MA 01730 USA
[ A PGP key is available for encrypted communications at
  http://cve.mitre.org/cve/request_id.html ]

> [1] https://irssi.org/security/irssi_sa_2017_03.txt

Skip to End

Master: is affected
Will try to work on upgrading this package

Sorry, didn't notice you were working on it.

fixed:
unstable: b00cfd49d50d46c6e8ae5257cbd98c11ba543df3
release-17.03: d3124a5259f531d2f94c257b4f14edf4a8f2f051

What's the status on 16.09?

Give me a sec and I will look
Sent from my iphone
On Mar 26, 2017, 6:02 AM -0500, Graham Christensen<EMAIL_ADDRESS>wrote:

What's the status on 16.09?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/NixOS/security/issues/55#issuecomment-289272843), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAHL73b5v8ltEni7-RmIitkBPKTFUWYJks5rpkXAgaJpZM4MpFho).

It is version 0.8.21
Sent from my iphone
On Mar 26, 2017, 6:02 AM -0500, Graham Christensen<EMAIL_ADDRESS>wrote:

What's the status on 16.09?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/NixOS/security/issues/55#issuecomment-289272843), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAHL73b5v8ltEni7-RmIitkBPKTFUWYJks5rpkXAgaJpZM4MpFho).

16.09 is not vulnerable.


Don't show checkbox as a list on summary if only one box is checked

What is the context of this PR?
On the summary page for a set of checkboxes we no longer want to show it as a list if only one box is checked
How to review
Check one item, see that there's not a bullet point next to it, check two items, see that there is a bullet point next to each.

Change looks reasonable. I don't think this case warrants a jinja filter. 👍 to making sure this is covered by a functional test.

@shahi645 cool, will do.
@AndrewTorrance I've added a couple of tests


feat(Dropdown): update styles for dark and hc Teams themes

Fixes: https://github.com/stardust-ui/react/issues/1215
In order for the styles to applied correctly, I've added the following things:

selectedIndex in the Dropdown component's state
selected prop for the DropdownItem, which is set to true from the Dropdown, if the selection is single, and the item is the selected one
isFromKeyboard prop for the DropdownItem, which is set from the Dropdown, based on the type of event received from Downshift, when the item is set to active

Thins that will be addressed in separte PRs:

adding inverted prop to the Dropdown
adding selected icon for the selected list item (may be implemented differently)

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

Click anywhere on the dropdown doesn't seem to work anymore

Click anywhere on the dropdown doesn't seem to work anymore

@codepretty acknowledge the problem, the worse part is that the tests didn't caught this :(

The issue with the trigger button is resolved, everything works as expected now.


Fixes

This PR fixes two bugs:

When a task has failed lint-staged will restore the original original state and abort committing. If this operation itself fails, the backup stash should not be removed. In f589336 it always sets the gitRestoreOriginalStateError flag in Listr's context which causes the cleanup task to be skipped. This change fixes https://github.com/okonet/lint-staged/issues/793
Fixes https://github.com/okonet/lint-staged/issues/797. In the issue it was reported that lint-staged evaluates functional configuration three times. This worked as intended, since the first run is for validating, second for generating tasks, and third for generating a name. This causes some issues, however, so it's best to try evaluating only once. A fix was to validate functional config only when generating tasks, and then relaxing the name generation, so that the name is only [Function] XXX ..., where XXX is taken from the evaluated task string up to the first whitespace character (so for example, [Function] eslint ...). I think this tradeoff is acceptable, since users no longer need to do filtering for the "[file]" argument passed to the functional config.

Thoughts, @okonet?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


What's the meaning of avg_drift

https://github.com/ApolloAuto/apollo/blob/e076feecb46232bacdf08490c5ff213832e6bdd8/modules/prediction/container/obstacles/obstacle.cc#L1346

@gumpcarl  Could you pls describe your question in detail so that it may be easier for others to answer.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Expecting an array or an iterable object but got (object Null)

Firewall= off
No anti-virus
Admin run= on.
any help ?

Where are you see this exactly?

after I import the item sets.

From: Dustin Blackman<EMAIL_ADDRESS>Sent: Sunday, August 21, 2016 10:04 PM
To: dustinblackman/Championify
Cc: questions123; Author
Subject: Re: [dustinblackman/Championify] Expecting an array or an iterable object but got (object Null) (#209)
Where are you see this exactly?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dustinblackman/Championify/issues/209#issuecomment-241278456, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AULXVEAV9q_C2ci8xTxcJ3xmiGg2bkudks5qiK9AgaJpZM4JpUMM.

Mind passing me the log file please? It's located at C:\Users\YOURNAME\AppData\Roaming\Championify\championify.log

2016-08-21T15:00:14.894Z - info: Version: 1.3.5
2016-08-21T15:00:21.819Z - info: Saved preference file to C:\Users\Sam\AppData\Roaming\Championify\prefs.json
2016-08-21T15:00:22.022Z - info: LoL Versie aan het Verkrijgen
2016-08-21T15:00:22.489Z - info: Champions aan het downloaden van Riot
2016-08-21T15:00:24.670Z - info: Downloading Lane Champs
2016-08-21T15:00:24.670Z - info: Downloading Jungle Champs
2016-08-21T15:00:24.670Z - info: Downloading Support Champs
2016-08-21T15:00:24.672Z - error:  TypeError: expecting an array or an iterable object but got [object Null]
at apiRejection (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:10:27)
at MappingPromiseArray.init (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise_array.js:62:19)
at new MappingPromiseArray (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:25:10)
at map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:139:12)
at Promise.map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:143:12)
at getSr (C:\Program Files (x86)\Championify\resources\app.asar\js\sources\championgg.js:347:45)
at C:\Program Files (x86)\Championify\resources\app.asar\js\championify.js:223:159
at _map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:247:27)
at map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:5850:20)
at C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:547:23
at Object.f2 [as map] (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:434:22)
at C:\Program Files (x86)\Championify\resources\app.asar\js\championify.js:223:149
at tryCatcher (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:503:31)
at Promise._settlePromise (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:560:18)
at Promise._settlePromise0 (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:605:10)
2016-08-21T15:00:24.673Z - error:  TypeError: expecting an array or an iterable object but got [object Null]
at apiRejection (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:10:27)
at MappingPromiseArray.init (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise_array.js:62:19)
at new MappingPromiseArray (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:25:10)
at map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:139:12)
at Promise.map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\map.js:143:12)
at getSr (C:\Program Files (x86)\Championify\resources\app.asar\js\sources\championgg.js:347:45)
at C:\Program Files (x86)\Championify\resources\app.asar\js\championify.js:223:159
at _map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:247:27)
at map (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:5850:20)
at C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:547:23
at Object.f2 [as map] (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\ramda\dist\ramda.js:434:22)
at C:\Program Files (x86)\Championify\resources\app.asar\js\championify.js:223:149
at tryCatcher (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:503:31)
at Promise._settlePromise (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:560:18)
at Promise._settlePromise0 (C:\Program Files (x86)\Championify\resources\app.asar\node_modules\bluebird\js\release\promise.js:605:10)
2016-08-21T15:00:24.825Z - info: koreanbuilds: Getting Roles

From: Dustin Blackman<EMAIL_ADDRESS>Sent: Monday, August 22, 2016 3:27 PM
To: dustinblackman/Championify
Cc: questions123; Author
Subject: Re: [dustinblackman/Championify] Expecting an array or an iterable object but got (object Null) (#209)
Mind passing me the log file please? It's located at C:\Users\YOURNAME\AppData\Roaming\Championify\championify.log

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dustinblackman/Championify/issues/209#issuecomment-241411819, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AULXVOEioGtJOpGos50BIgubHZ4o5-fRks5qiaOugaJpZM4JpUMM.

Ah, it looks like Riot removed some locales. Dutch isn't supported anymore. Patch incoming!

so Install the english one ?

From: Dustin Blackman<EMAIL_ADDRESS>Sent: Wednesday, August 24, 2016 3:55 PM
To: dustinblackman/Championify
Cc: questions123; Author
Subject: Re: [dustinblackman/Championify] Expecting an array or an iterable object but got (object Null) (#209)
Ah, it looks like Riot removed some locales. Dutch isn't supported anymore. Patch incoming!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dustinblackman/Championify/issues/209#issuecomment-242072654, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AULXVJM6pWMpjI2PlsQo_VNLg416PuyDks5qjE1JgaJpZM4JpUMM.

@questions123 I've just pushed an update. Your client will automatically update and you'll be able to do imports in Dutch again.

thnx, great response ! Great app!

From: Dustin Blackman<EMAIL_ADDRESS>Sent: Wednesday, August 24, 2016 4:34 PM
To: dustinblackman/Championify
Cc: questions123; Mention
Subject: Re: [dustinblackman/Championify] Expecting an array or an iterable object but got (object Null) (#209)
@questions123https://github.com/questions123 I've just pushed an update. Your client will automatically update and you'll be able to do imports in Dutch again.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dustinblackman/Championify/issues/209#issuecomment-242086578, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AULXVOlX7T-bTuQaio6rzy2_FoltQIQEks5qjFaJgaJpZM4JpUMM.


Running without docker

Hi, I am not much familiar with docker would like to build it on my desktop. I am using k80 on GCP's vm instance. Please suggest which file I should follow. thanks a lot!

Tried it, irrespective of what I do, I always get this error
 make: *** [Makefile:99: batch_recognizer.o] Error 1

Can you paste more logs? This line is just the result. But it's not descriptive enough to guess what's going on.

I see! Actually, there were no logs created! This error happened during the execution of the following
cd /opt/vosk-api/src && \
KALDI_ROOT=/opt/kaldi HAVE_CUDA=1 make -j $(nproc)

Which URL you used for pulling vosk-api?

git clone -b gpu-fix https://github.com/sskorol/vosk-api.git /opt/vosk-api

Have you successfully built Kaldi on previous steps?

That's right, it had no errors.

Ok, try pulling from here https://github.com/alphacep/vosk-api.git and run those command again.

Got it, will do right away!

Hey, this does not produce any errors. I followed these
cd /opt/vosk-api/src && \
KALDI_ROOT=/opt/kaldi HAVE_CUDA=1 make -j $(nproc) && \
python3 -m pip install --upgrade pip setuptools wheel cython && \
cd ../python && \
python3 ./setup.py bdist_wheel && \
cd ./dist && pip3 install vosk-*.whl

After that, I did the following
cd vosk-api/python/example
wget https://alphacephei.com/kaldi/models/vosk-model-small-en-us-0.15.zip
unzip vosk-model-small-en-us-0.15.zip
mv vosk-model-small-en-us-0.15 model
python3 ./test_simple.py test.wav

It gave me the following error though.
Traceback (most recent call last):
  File "./test_simple.py", line 3, in <module>
    from vosk import Model, KaldiRecognizer, SetLogLevel
  File "/usr/local/lib/python3.7/dist-packages/vosk-0.3.32-py3.7.egg/vosk/__init__.py", line 21, in <module>
    _c = open_dll()
  File "/usr/local/lib/python3.7/dist-packages/vosk-0.3.32-py3.7.egg/vosk/__init__.py", line 15, in open_dll
    return _ffi.dlopen(os.path.join(dlldir, "libvosk.so"))
OSError: cannot load library '/usr/local/lib/python3.7/dist-packages/vosk-0.3.32-py3.7.egg/vosk/libvosk.so': /usr/local/lib/python3.7/dist-packages/vosk-0.3.32-py3.7.egg/vosk/libvosk.so: undefined symbol: cudaMemcpyAsync

What's in your test_simple.py?

The test_simple.py has the following
from vosk import Model, KaldiRecognizer, SetLogLevel
import sys
import os
import wave

SetLogLevel(0)

if not os.path.exists("model"):
    print ("Please download the model from https://alphacephei.com/vosk/models and unpack as 'model' in the current folder.")
    exit (1)

wf = wave.open(sys.argv[1], "rb")
if wf.getnchannels() != 1 or wf.getsampwidth() != 2 or wf.getcomptype() != "NONE":
    print ("Audio file must be WAV format mono PCM.")
    exit (1)

model = Model("model")
rec = KaldiRecognizer(model, wf.getframerate())
rec.SetWords(True)
rec.SetPartialWords(True)

while True:
    data = wf.readframes(4000)
    if len(data) == 0:
        break
    if rec.AcceptWaveform(data):
        print(rec.Result())
    else:
        print(rec.PartialResult())

print(rec.FinalResult())

I think this is not suitable so I ran this instead https://github.com/alphacep/vosk-api/blob/master/python/example/test_gpu_batch.py

In general, it's likely Kaldi wasn't correctly built for your platform. It's a crash from a native code. To see native logs you need to run the python process with gdb.

./test_gpu_batch.py test.wav seems to be closer to working
It gives the error
WARNING ([5.5.1028~1-d8d8]:SelectGpuId():cu-device.cc:243) Not in compute-exclusive mode.  Suggestion: use 'nvidia-smi -c 3' to set compute exclusive mode
LOG ([5.5.1028~1-d8d8]:SelectGpuIdAuto():cu-device.cc:438) Selecting from 1 GPUs
LOG ([5.5.1028~1-d8d8]:SelectGpuIdAuto():cu-device.cc:453) cudaSetDevice(0): Tesla K80  free:4845M, used:6595M, total:11441M, free/total:0.423544
LOG ([5.5.1028~1-d8d8]:SelectGpuIdAuto():cu-device.cc:501) Device: 0, mem_ratio: 0.423544
LOG ([5.5.1028~1-d8d8]:SelectGpuId():cu-device.cc:382) Trying to select device: 0
LOG ([5.5.1028~1-d8d8]:SelectGpuIdAuto():cu-device.cc:511) Success selecting device 0 free mem ratio: 0.423544
LOG ([5.5.1028~1-d8d8]:FinalizeActiveGpu():cu-device.cc:338) The active GPU is [0]: Tesla K80   free:4692M, used:6748M, total:11441M, free/total:0.410172 version 3.7
LOG ([5.5.1028~1-d8d8]:RemoveOrphanNodes():nnet-nnet.cc:948) Removed 0 orphan nodes.
LOG ([5.5.1028~1-d8d8]:RemoveOrphanComponents():nnet-nnet.cc:847) Removing 0 orphan components.
LOG ([5.5.1028~1-d8d8]:BatchModel():batch_model.cc:52) Loading HCLG from model/graph/HCLG.fst
LOG ([5.5.1028~1-d8d8]:BatchModel():batch_model.cc:56) Loading words from model/graph/words.txt
LOG ([5.5.1028~1-d8d8]:BatchModel():batch_model.cc:64) Loading winfo model/graph/phones/word_boundary.int
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:183) Computing derived variables for iVector extractor
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:204) Done.
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:183) Computing derived variables for iVector extractor
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:204) Done.
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:183) Computing derived variables for iVector extractor
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:204) Done.
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:183) Computing derived variables for iVector extractor
LOG ([5.5.1028~1-d8d8]:ComputeDerivedVars():ivector-extractor.cc:204) Done.
Traceback (most recent call last):
  File "./test_gpu_batch.py", line 17, in <module>
    fnames = open(sys.argv[1]).readlines()
  File "/opt/conda/lib/python3.7/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 4: invalid start byte
LOG ([5.5.1028~1-d8d8]:~CachingOptimizingCompiler():nnet-optimize.cc:710) 0.0972 seconds taken in nnet3 compilation total (breakdown: 0.0587 compilation, 0.00505 optimization, 0.0301 shortcut expansion, 0.000912 checking, 0.000153 computing indexes, 0.00224 misc.) + 0 I/O.

I see! I think I will just give up here. I have little hope here. I am using tesla k80 on GCP as a platform. Thank you so much for your kind help man.

That's an encoding error while reading cli args in the python code. Should be easy to fix. Note that all those scripts were written just as a set of examples. They can't cover all the environments out of the box and assume you have some programming experience to fix or tune things for your own needs. I'm not a Vosk creator. I'm the same user as you are. Just created a repo to reduce GPU overhead while working with Vosk. But again, setting everything up for the first time requires some engineering skills. So it might be hard for newbies. I see your pain and frustration. But that's how it works.

I guess it's not actual anymore, as you have succeeded with a relative ticket.

@sskorol I could run without docker on the P4 instance. Thanks again for the support.

Great! Have you built it on your own or just reused those new image that I recently pushed?

@raghavendrajain btw, I prepared instructions for building images in GCP. Recent updates contain terraform configs to spawn T4 instance where you can easily deploy Vosk w/ or w/o docker.

@raghavendrajain btw, I prepared instructions for building images in GCP. Recent updates contain terraform configs to spawn T4 instance where you can easily deploy Vosk w/ or w/o docker.

Oh great, I will check it! I did not see them earlier but just ran the commands you described in Dockerfile.pc.

But note that a build script in gcp folder attempts to patch a model. If you already have a working version, you may want to comment these lines.


Can't add scatter with 2 points in array

Run into an issue where if the lng/lat array of coords provided to m.scatter(...) is 2 or less I get the following error:
Traceback (most recent call last):
  File "basemap_scatter.py", line 55, in <module>
    m.scatter(points2[0],points2[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)
  File "~/anaconda/lib/python3.5/site-packages/mpl_toolkits/basemap/__init__.py", line 536, in with_transform
    x = self.shiftdata(x)
  File "~/anaconda/lib/python3.5/site-packages/mpl_toolkits/basemap/__init__.py", line 4775, in shiftdata
    thresh = 360.-londiff_sort[-2]
IndexError: index -2 is out of bounds for axis 0 with size 1

single coords work and 3+ appears to work.
Example showing working/not working combinations I have tried.
import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap
from shapely.ops import transform
from shapely.geometry import Polygon, Point, MultiPolygon
from descartes import PolygonPatch

#setup bounds
minx, miny, maxx, maxy = [144.699997,-37.882599,144.7813598,-37.753114]

#width height
w, h = maxx - minx, maxy - miny

plt.figure(figsize=(18,12))
m = Basemap(
    projection='merc',
    ellps = 'WGS84',
    llcrnrlon=minx - 3 * w,
    llcrnrlat=miny - 3 * h,
    urcrnrlon=maxx + 3 * w,
    urcrnrlat=maxy + 3 * h,
    resolution='h')
m.drawcoastlines()
m.drawmapboundary(fill_color='lightskyblue')
m.fillcontinents(color='silver',lake_color='lightskyblue', zorder=0.1)

point1 = [144.687,-37.751]
point2 = [144.793,-37.881]
point3 = [144.695,-37.742]

# =============================== Scatter tests ====== #

#single point - WORKS
#m.scatter(point1[0],point1[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)

##2 single points - WORKS
# m.scatter(point1[0],point1[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)
# m.scatter(point2[0],point2[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)

#Array of 3 elements - WORKS
# points3 = [list(i) for i in zip(point1,point2,point3)]
# print(points3)
# m.scatter(points3[0],points3[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)

#array of 1 element - DOESNT WORK
# points1 = [list(i) for i in zip(point1)]
# print(points1)
# m.scatter(points1[0],points1[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)

#array of 2 elements - DOESNT WORK
points2 = [list(i) for i in zip(point1,point2)]
print(points2)
m.scatter(points2[0],points2[1], 500, c='blue',alpha=1, zorder=0.6, latlon=True)

plt.show()

Yes, this is a known issue....
@WeatherGod I was thinking about a hacky fix: just in cases when user feeds less than 3 points, just duplicate to have at least 3 points?
But I think you have already rejected that...
Cheers

This was already fixed in the current master, try updating your basemap package.
Cheers

Updated from master and confirmed its working, thanks


Allow marker optimization=false in module configuration

The only reliable way to write an integration test for google maps v3 seems to be disabling marker optimization in order to interact with markers using jQuery (or capybara/webdriver) selectors. I know your library already permit this by using attributes i.e.
<marker postion='NY' optimized=false>

I was wondering if you can provide a configurable service (Attr2Options??) to globally disable optimization, in this way instead of cluttering app code with optimized="{{whateverFlag}}" one can simply define it in module initialization, something like:
angular.module('myApp', ["ngMap"]).config(function(NgOptimizerProvider) {
  NgOptmizerProvider.disableMarkerOptimization(); // or whatever names you choose
});

It should be pretty easy to do and imho would be very useful. What do you think?

Good idea, but what could it be? only for a marker? or including all other directives?
The implementation would be simple, but design should be done properly at early stage.
Need few options that requires configuration.

Default marker options

According to documentation optimized option is supported only for markers.
In order to create an extensible solution I'd start with a NgMapOptions configurable provider open to future improvements. This provider will be then used by Attr2Options service to fetch global options or by individual directives.
Right now I don't know what other global options could go in that provider.

NgMap factory is introduced in 1.14, we can expand this NgMap as a provider later.

This has been implemented with 1.14.6. Example here, http://ngmap.github.io/#/marker-with-default-options.html


Update for clarity

Removal of reference to IR Mode RAID controllers as that seems to be causing confusion.
Confirm with: Andrew Hansen on DL (AnHansen@)

@JasonGerend Please look at this change and let me know if it's ready to merge. Thanks!

I would prefer not to take these changes. IT and IR mode are vendor specific terms. I would prefer not to include. Raid is also supported on ReFS. RAID is not supported with Spaces and ReFS together.

Andrew,
Got it. I was confusing things there. Sorry.
Philip Elder MCTS
Microsoft High Availability MVPhttps://mvp.microsoft.com/en-us/PublicProfile/4024277
E-mail: PhilipElder<EMAIL_ADDRESS>Phone: +1<PHONE_NUMBER>
Web: www.mpecsinc.comhttp://www.mpecsinc.com/
Cloud: www.CanadianCloudWorx.comhttp://www.canadiancloudworx.com/
Blog: blog.mpecsinc.comhttp://blog.mpecsinc.com/
Twitter: Twitter.com/MPECSInchttps://twitter.com/MPECSInc
Skype: MPECSInc.
Please note: Although we may sometimes respond to email, text and phone calls instantly at all hours of the day, our regular business hours are 8:00 AM - 5:00 PM, Monday thru Friday.
From: Andrew Hansen<EMAIL_ADDRESS>Sent: Friday, March 20, 2020 15:13
To: MicrosoftDocs/windowsserverdocs<EMAIL_ADDRESS>Cc: Philip Elder<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windowsserverdocs] Update for clarity (#4046)
I would prefer not to take these changes. IT and IR mode are vendor specific terms. I would prefer not to include. Raid is also supported on ReFS. RAID is not supported with Spaces and ReFS together.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MicrosoftDocs_windowsserverdocs_pull_4046-23issuecomment-2D601912917&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0mRsRNE8chpNqrO_K4qEv0KlpJIZgNEvhN8ZhTgAQ9w&m=F8nKH1zJXb4FnMcq0qbeMBbSwZkDxTpZUmyGl77md9k&s=lpGyHLSjQhuFfJPkAkrGE85whzxcFrSiGxnQ6Pm1tME&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AGIFF6YAR7TDVTVHBQUX2T3RIPL4LANCNFSM4LQNFV4Q&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0mRsRNE8chpNqrO_K4qEv0KlpJIZgNEvhN8ZhTgAQ9w&m=F8nKH1zJXb4FnMcq0qbeMBbSwZkDxTpZUmyGl77md9k&s=F57tYyMW9nk3X4v61G5ZlagzCPHYtQ9it3X1vecizmI&e=.


page keep refreshing

I completed all steps without a problem
except when I run page I experience this

I load pages https://d436-70-54-115-39.ngrok.io.  I see the content and then in about 2 seconds I have login.microsoftonline.com loaded
I'm finishing the login steps there and then I'm redirected back to https://d436-70-54-115-39.ngrok.io
page loaded and it keeps refreshing itself with this URL https://d436-70-54-115-39.ngrok.io/#code=0.AVIAxxxxxxxxxxxxxx&client_info=eyJ1axxxxxxx&state=eyxxxxxx&session_state=79xxxxxxxxxxx

duplicate


  This fixes that.

Fixed in https://github.com/niklasvh/html2canvas/commit/50608e9cd4327c3503223dca85ab7b2b2b9e629c


Feature/lit 3767 fix could only connect to 8 of 6 required nodes from 9 all nodes

Description
This PR:

updates the "connected to X of Y nodes, with a minimum of Z" as that was misleading when X>=Z
adds retry logic to each node handshake request (with a flag to [de]activate it, and retries until handshake timeout is reached). Defaults to true
adds a per node HANDSHAKE timeout, configurable. (apart from full handshake timeout). This one overrides the request timeout if present. Defaults to 7500ms.
adds per node REQUEST timeout (applies also to handshake if present and handshake one is not), configurable. Defaults to 35000ms (because LitActions have a 30s timeout, plus some network lag)

With default configs, the handshake process will attempt to connect to each node, the ones that don't succeed before 7500ms will be cancelled and retried in loop until they all succeed or handshake timeout is reached
When retry is set to false, the first failing node will fail the whole process (can be changed for naga allowing X=>Z handshakes)

Type of change

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manually tested several configs with a demo app

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Closing this and replaced by #624 as that is using staging/v7 as base. It was easier that than rebasing
I also improved error handling and retry logic there. Using this PR would leave some followups and nasty code that we would have to update shortly so there was no reason to stay on this one


GKE enable cert auth

 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.


Unable to Expose to <IP_ADDRESS>

Hey there,
Thank you so much for this project!! 4 little instructions to install, WAY simpler than the native way!
Currently, I am trying to host this in a container for my local network, however the way this is setup natively:
<IP_ADDRESS>:8888
Doesn't allow it to be exposed to my network
Changing the config file to be <IP_ADDRESS>:8888 and <IP_ADDRESS> port 8888 allows me to get to the User Manager through the /uc/admin page, but going to ipaddress:8888 in my web browser, where Outline should appear, shows a blank dark-themed screen
Is there another way to expose this application to the network?
Thank you!

Update, changing to my local IP works locally (instead of  <IP_ADDRESS>:8888, use localip:8888, in my case <IP_ADDRESS>:8888), however I am trying to assign this to a domain @ notes.mydomain.com, and while I can load this on my local net, trying to load on notes.mydomain.com loads the blank page again, while the UC Admin can be accessed just fine
I've got an NGINX proxy manager on a different server that is pointing back to this instance

I'm trying to do exatcly the same. Have you found a solution to this? Thanks

Bump

这个问题我也遇到了   但是，这个nginx代理就会出问题。外网访问 ，但是无法绑定域名。

I found how to fix this,
Combined with the resolution in here of adding  user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline in the Docker Compose and what I'm about to post here, this should work for you all, too
FULL STEPS OF HOW I SET THIS UP:
~~
Create an Ubuntu / Debian Container / VM
Install Updates and Upgrades
Install Docker, Make, and Nano
Clone the Git
Clone the config.sh from scripts/config.sh.example
Nano the config.sh
Then, “Make Install”
Commands:
Start Off:
cd /
mkdir outlineserverfolder
Apt-get update && apt-get upgrade -y
Apt install make && apt install nano
Install Docker:
apt-get install ca-certificates curl gnupg
install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
echo \   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \   $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \   sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
apt-get update
apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-compose
Install Outline from Github:
outline-docker-compose-master.zipcd directory/where/outlinedata/is/stored (/outlineserverfolder in this case)
git clone https://github.com/vicalloy/outline-docker-compose.git
cd outline-docker-compose
cp /scripts/config.sh.sample scripts/config.sh
nano scripts/config.sh
OutlineConfig: URL= (PublicFacingURL:PublicFacingPort[PORT REQUIRED!])notes.mydomain.com:443 PORT= 3000
NginxConfig: URL=<IP_ADDRESS> (Ties Nginx Container to the Host IP) PORT = 8888
CTRL + O to save, CTRL + X to exit nano
Run the MakeFile to Install and Setup the Server:
make install
Other Commands:
docker ps ~ Will show Docker Containers
docker exec -it  /bin/bash ~ executes /bin/bash on container, CTRL+P+Q to exit
make install ~ Installs and Sets Up the server
make start ~ Starts all associated containers
make stop ~ Stops all associated containers
make clean ~ Clears data from all containers
make clean-data ~ Clears All Container .env Variables and All Container Data, also Deletes Containers
Notes regarding- Outline Config: URL = PublicFacingURL:PublicFacingPort
The URL and domain that you are using to host this with the port of the site. Essentially, if you host this at notes.yourdomain.com via cloudflare, and you’re pointing it back to an NGINX proxy, the service itself will host on the NginxConfig host, <IP_ADDRESS>, and is accessible via port 8888, so redirect from notes.yourdomain.com to the IP Address of the Outline host on port 8888, ensure 443 and 80 are open in your firewall, and in the configuration, when it is asking for the OutlineConfig URL, ensure that you list both the domain URL and the port utilized (if using HTTP, port 80, if HTTPS, port 443) in the Outline Config, the port is a required element
How this is setup:
Docker Host: <IP_ADDRESS>
Config File:
                OutlineSection ~ URL: notes.mydomain.com:443 PORT: 3000

                NginxSection    ~ URL: <IP_ADDRESS> PORT: 8888

                Leave the Rest Alone

Nginx Proxy Manager:
Add a HTTP Redirection Host to <IP_ADDRESS>:8888 from notes.mydomain.com
               WebSocket Support + Block Common Exploits + Cache
               SSL > Request New SSL Certificate

Firewall(s):
              NAT Forward port 80/443 to Nginx Proxy Manager

              If multiple firewalls / routers / layers to network, push port through to each until host reached

Access:
             For Internal Useage / Testing, <IP_ADDRESS>:8888 will get to the site

             For Public Access / Useage, notes.mydomain.com should get to the site

             For User Management, <IP_ADDRESS>:8888/uc/admin/auth/user/

                            NOTE: USER MUST HAVE LISTED EMAIL ADDRESS OR SIGN-IN WILL FAIL

In this current state, photos will fail to upload anywhere. Within the docker-compose.yml,
wk-outline:
image: outlinewiki/outline:${OUTLINE_VERSION}
command: sh -c "yarn db:migrate --env production-ssl-disabled && yarn start"
environment:
- DATABASE_URL=postgres://user:pass@wk-postgres:5432/outline
- DATABASE_URL_TEST=postgres://user:pass@wk-postgres:5432/outline-test
- REDIS_URL=redis://wk-redis:6379
- AWS_S3_UPLOAD_BUCKET_NAME=outline-bucket
env_file:
- ./env.outline
- ./env.oidc
volumes:
- ./data/outline:/var/lib/outline/data
user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline
restart: unless-stopped
depends_on:
- wk-postgres
- wk-redis
##BEGIN MINIO
- wk-minio
##END

I wrote an entire document on Outline for how to host Outline, sorry if the formatting isn't great, but this is basically every step I took

What you'll need to do is set the config.sh outline URL to the PUBLIC FACING URL:443 or :80, depending on if HTTP or HTTPS, if using LetsEncrypt with your NGINX Proxy Manager, set it to your notes.yourdomain.com:443. Leave the PORT option at 3000

Then, for the NGINX config, I have it hosted on <IP_ADDRESS>, to ensure that if you navigate to the local domain, <IP_ADDRESS>:8888, it still works and still redirects fine, so that the <IP_ADDRESS> cannot access issue is gone, but with the outline url set to notes.yourdomain.com:443 PORT3000 you should be able to redirect through Proxy Manager to it just fine without needing advanced flags or location flags

The only thing I am now working on is blocking access to the /uc/admin site through proxy manager, and though I am struggling to figure that out, this is not an NGINX Proxy Manager Github, so I'll figure that one out

@giovannipollo @Codename-11 @hardingCheng

Please ping me if anyone has issues with understanding that, I just copy pasted from my Outline page

Thanks it works!
Following the documents of @7ekhed , I did the following things.
clone git
git clone https://github.com/vicalloy/outline-docker-compose.git
cd outline-docker-compose
cp scripts/config.sh.sample scripts/config.sh

Change configuration
nano scripts/config.sh

URL=<my_url>:8888
HTTP_IP=<IP_ADDRESS>

Change configuration - 2
nano scripts/templates/docker-compose.yml

volumes:
- ./data/outline:/var/lib/outline/data
user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline
restart: unless-stopped

Install and run
make install

Anyone has tried this approach with traefik? I tried numbers on configuration to use traefik as reverse proxy but it would only work temporarily then nginx would result in worker process 23 exited with code 0

Thank you all, especially @7ekhed & @sheepvs5 !
I spend several hours to try to fix it.
Got it to work now. 🤝🏼

Mine still not working.
I have no problem open it with local ip:8888
http://<IP_ADDRESS>:8888
then I set up nginx reverse proxy with my own domain name pointing to my local ip and port 8888
the nginx proxy manager is running on a different server on my local network:

config.sh file URL 但and HTTP_IP was set like below:

but when I go to https://docs.stonelab.me
I can open the page, but it brought to the following page with a button Using OenID to continue, then nothing working from there. I think it might be the authentication issue?


request offline tokens

Offline tokens are required if we expect to be able to exchange the refresh token for a new access token at a later date.

scratch this; the issue is that the refresh token is one-use only.
Can you help me understand how you envision handling this? I've sort of worked around it for now, but I feel like this library or maybe just the docs could be improved to deal with this.

I ran into this way back when I made the changes for v2 and apparently neglected to push the changes up and update the documentation. I have pushed a commit that contains the changes.
You are correct, after you use the refresh token to get an access token that refresh token is now invalid and a new token is created. On the latest commit, when you call any method on a user it tracks and updates the internal refresh token which can be found at CurrentRefrehToken. Also, there is a method named RefreshTokenReplaced that will return true if the token has been replaced. You can then store that token wherever works for your application.


Add support for Treesitter textobjects

I was thinking about sending the output of a treesitter.textobjects command to irons REPL but I fear my lua skills aren't there yet.
I tried this
:lua require('iron').core.send(vim.bo.ft<EMAIL_ADDRESS>'o'))
and this
require("iron").core.visual_send(vim.bo.ft<EMAIL_ADDRESS>'o'))
without success and I dont really understand whats meant with "data" in the documentation, help about this would be appreciated.
If it is feasible it would be nice to have native support for treesitter objects :)

This would definitely be an amazing addition.. I'll have a look at it and will try to come up with something workable :)

I use succesfully the following snippet.
local is = require("nvim-treesitter.incremental_selection")
local function treesitter_selection()
  is.init_selection()
  is.node_incremental()
end
require("iron").core.visual_send(vim.bo.ft, treesitter_selection)

local is = require("nvim-treesitter.incremental_selection")
local function treesitter_selection()
  is.init_selection()
  is.node_incremental()
end
require("iron").core.visual_send(vim.bo.ft, treesitter_selection)

I might be mistaken, but it seems that visual_send doesn't take any arguments. Am I missing something?

Not entirely sure this is needed at repl level given searching / selecting treesitter object is a non-trivial task and can be used beyond the scope of repl. This is actually implemented neatly by motion plugins:

leap ,
flash
among other plugins.

Some simple keymap would achieve what is requested. e..g,
vim.keymap.set(
  { "n" },
  "gt",
  function()
      vim.cmd('normal V')
      require("leap.treesitter").select()
      require("iron.core").visual_send()
      vim.cmd("norm! j")
  end,
  { desc = "send treesitter textobj" }
)

In my opinion, we could simply update the README instead of reinvent the wheel.


Add live fps test

Added a unit test under live/frames to test fps.
Only nightly because run time ~200 seconds for D400 and ~110 seconds for L515

You meant explain in a comment on the code or in the PR?
From: Eran @.>
Sent: Sunday, June 19, 2022 12:55
To: IntelRealSense/librealsense @.>
Cc: Meir, Ohad1 @.>; Author @.>
Subject: Re: [IntelRealSense/librealsense] Add live fps test (PR #10591)
@maloel commented on this pull request.

In unit-tests/live/frames/test-fps.pyhttps://github.com/IntelRealSense/librealsense/pull/10591#discussion_r901078837:

   print("Requested fps: {:.1f} [Hz], not supported".format(requested_fps))

else:

   fps = measure_fps(ds, dp)

   print("Requested fps: {:.1f} [Hz], actual fps: {:.1f} [Hz] ".format(requested_fps, fps))

   test.check(fps <= (requested_fps + acceptable_exception_rate_Hz) and fps >= (requested_fps - acceptable_exception_rate_Hz))

+test.finish()

+#####################################################################################################
+test.start("Testing color fps " + product_line + " device - "+ platform.system() + " OS")

+for requested_fps in tested_fps:

dev = test.find_first_device_or_exit()

cs = dev.first_color_sensor()

if product_line == "D400":

   ds.set_option(rs.option.enable_auto_exposure, 1)

Please explain
—
Reply to this email directly, view it on GitHubhttps://github.com/IntelRealSense/librealsense/pull/10591#pullrequestreview-1011500015, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX3PS5UNA2HEHEGMZZKJBQDVP3U6RANCNFSM5YWOOVZA.
You are receiving this because you authored the thread.Message ID: @.***>
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.