s3 bucket backend.tf issue resolution related to terraform

User stories
As a developer, I want to resolve backend issue related to terraform. Since it is not managing the state file of terraform when a deployment is done using pipeline.
Add more as required
Acceptance Criteria

[x]  Determine the appropriate solution or fix for the identified issue.
[x] Implement the necessary changes to resolve the issue in the backend.tf file.
[x] Ensure that the S3 bucket backend configuration allows Terraform to store the state file securely and efficiently.
[x] Test the updated configuration by initializing Terraform and validating that it connects to the S3 bucket backend without errors.

Using of -state flag in terraform apply resolved the issue. Since we have backend.tf saving state file to s3 bucket. We will just change the command from buildspec in such a way that instead of running terraform apply, buildspec will be updated with command: terraform apply -state=s3bucketpath/key.


Cannot post stars

Cannot post stars using POST /api/star/{from_employee_id}/give/star/to/{to_employee_id}/
Response Body
Server Error (500)
Response Code
500 Internal Server Error
Response Headers
{
"Date": "Tue, 03 May 2016 17:40:53 GMT",
"Via": "1.1 vegur",
"Server": "gunicorn/19.4.5",
"X-Frame-Options": "SAMEORIGIN",
"Vary": "Cookie",
"Content-Type": "text/html",
"Access-Control-Allow-Origin": "*",
"Access-Control-Expose-Headers": "Access-Control-Allow-Origin, Access-Control-Allow-Headers",
"Transfer-Encoding": "chunked",
"Connection": "keep-alive"
}

Fixed and published


copr: Add vectorized FromBase64

Signed-off-by: Alex Chi<EMAIL_ADDRESS>UCP #6933
Checklist #5751
What problem does this PR solve?
Issue Number: close #6933
Problem Summary: add vectorized FromBase64
What is changed and how it works?

Add vectorized FromBase64
Move strip_whitespace to tidb_query_shared_expr

Check List
Unit tested.

This function is not in push-down test list. Should I make a PR to https://github.com/tikv/copr-test/blob/master/push-down-test/functions.txt , and run push-down test?

rest LGTM

/approve

It seems that integration test failed. Is it acceptable?

@sre-bot /test

Integration common test reports
[2020-05-11T01:35:15.752Z] time="2020-05-11T09:35:15+08:00" level=fatal msg="run test [gcol_blocked_sql_funcs] err: sql:create table t1 (a varchar(32), b bool generated always as (match a against ('sample text')) virtual);: run \"create table t1 (a varchar(32), b bool generated always as (match a against ('sample text')) virtual);\" around line 80 err, we need(299):\ncreate table t1 (a varchar(32), b bool generated always as (match a against ('sample text')) virtual);\n[parser:1064]You have an error in your SQL syntax; check the manual that corresponds to your TiDB version for the right syntax to use line 1 column 65 near \"match a against ('sample text')) virtua\nbut got(299):\ncreate table t1 (a varchar(32), b bool generated always as (match a against ('sample text')) virtual);\n[parser:1064]You have an error in your SQL syntax; check the manual that corresponds to your TiDB version for the right syntax to use line 1 column 67 near \"a against ('sample text')) virtual);\" \n\n"

in integration MySQL test

It seems there are some bugs in the main branch.

Thanks for reviewing! Maybe I can trigger CI build later today to see if it works.

/run-all-tests

/merge


'SqlConnection' does not contain a definition for 'BulkInsertAsync'

Hi,
I am not sure whether it's an expected behaviour or not, but after updating RepoDB packages as follows:
"RepoDb" version="1.12.9" targetFramework="net48"
"RepoDb.MySql" version="1.1.5" targetFramework="net48"
"RepoDb.SqlServer" version="1.1.5-beta1" targetFramework="net48"
"RepoDb.SqlServer.BulkOperations" version="1.1.6-beta1" targetFramework="net48"
I started getting this error message:
'SqlConnection' does not contain a definition for 'BulkInsertAsync' and the best extension method overload 'SqlConnectionExtension.BulkInsertAsync(SqlConnection, IEnumerable, IEnumerable, SqlBulkCopyOptions?, string, int?, int?, bool?, bool?, SqlTransaction, CancellationToken)' requires a receiver of type 'SqlConnection'
Is it caused by this change:
https://twitter.com/mike_pendon/status/1441499327814422530?s=20
?

Yes, it is expected. The latest beta versions of RepoDb.SqlServer and RepoDb.SqlServer has already eliminated the SDS. If you still would like to work with SDS, you have to bootstrap it explicitly, see here.
The other solutions are:

Fallback to RepoDb.SqlSever v1.1.4 and RepoDb.SqlServer v1.1.5.
Use the MDS in your using statement and completely eliminate the SDS

Everything is in your perusal.
We will never issue an actual release until the beta releases that removes the SDS is matured enough. Hope this helps!

Thank you for your reply! Now everything is clear :)
The issues were limited to a legacy module still based on SDS, now I switched to MDS (and I will report issues, if any)


fix(replica): best-effort to delete old head disk file

Which issue(s) this PR fixes:

Issue Longhorn/longhorn#9168
What this PR does / why we need it:
The deletion of old head disk file is a best-effort task, and the failure should not hinder the following tasks.
The regression is caused by
https://github.com/longhorn/longhorn-engine/commit/737bf77b6e0f01e68dbb340e4b3421bb0c7417b6#diff-b54af9ffed94a317525bc7609415261b623020d2aa410c124e9fe3b871d2d2bdR918
Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x

Does this mean there would be chances to have orphaned old head snapshot img?

Does this mean there would be chances to have orphaned old head snapshot img?

Yes, need a manual intervention for the deletion.

@mergify backport v1.6.x

@mergify backport v1.6.x

Backporting to v1.6.x is necessary, because the bug is also in v1.6.x,


Event scheduling

Adds the ability to set up schedules that trigger when events are sent.

I'll want to see a strong argument for a) what role does this serve for users and b) why does this need to exist in bevy_ecs before I'm in favor of this. I would really, really like to keep our scheduling abstractions minimal.

This was brought up as part of other work (same-state transitions) - but I don't believe it is actually worthwhile at this point.


[workflow] Update version to 0.9.6

I have communicated with the maintainer of workflow. We think this REF is consistent with the Release v0.9.6  on branch master.
We made a tag v0.9.6-win for windows branch. PTAL


additional data types for custom functions needed

only numerical valued custom functions with numrerical arguments are supported.  adding strings and bools would be great for starters.
many thanks for the important work being done here!

I also hit this issue today. Did not realise that only NumberValue is supported (https://github.com/microsoft/Power-Fx/blob/47f0dfc2b13dcbdd8a2310289c902e19f9752314/src/libraries/Microsoft.PowerFx.Interpreter/ReflectionFunction.cs#L132). It would be good to get a timeline for support of other types.

@timnudecision - It is possible to use other data types as well. Please see Creating new Functions in Power Fx  section in the notebook https://github.com/rajyraman/Power-Fx-.NET-Interactive/blob/main/notebooks/PowerFx.ipynb

@rajyraman that works, thanks.

We also need support for async functions (returning task), and likely leveraging the new TypeMarshaller support.


Add a Docat API client/CLI tool

API endpoints are hard to remember and hard to read.
A nice-to-have feature would be a Docat API client, which can be used with Python or with the command line.
The Docat CLI tool shall be runnable via a Docker container or via Pip
e.g.
Tag:
# Previously:
$ curl -X PUT http://localhost:8000/api/PROJECT/VERSION/tags/latest
# After:
$ docat tag my-project 1.0.0 latest --url http://localhost:8000

Publish:
# Previously:
$ curl -X POST -F<EMAIL_ADDRESS>http://localhost:8000/api/PROJECT/VERSION
# After:
$ docat push my-project 1.0.0 ./docs.zip --url http://localhost:8000

(optional) Add a docat.yml config:
$ cat <<EOF > docat.yml
url: http://localhost:8000
project: my-project
EOF

$ docat push 1.0.0 ./docs.zip

or as API client
from docat import tag

tag("my-project", "1.0.0", "latest")

Should the client reside in this repo or should its homebase be the new @docat-org? And finally, would you want to publish the CLI to PyPI?

I close this since https://github.com/docat-org/docatl exists :taco:

Good job @timofurrer. Would have been a “great job” if it was written in JavaScript but ok

@BrunnerLivio 👀


Update README.md

Homebrew didn't support the original options without tapping this repository first. I've updated the installation instructions accordingly. If there's a preferred installation strategy that nullifies this, let me know and I'll update my PR accordingly.

Thanks, you are absolutely correct!


Deprecation of Transifex API v2 and sunset of Transifex Client

The transifex-client as well is going away in November 30, 2022. The new transifex/cli is going to be the new thing. Since the new client is written in Go lang, it won't be installable via Python's requirements.txt,
For more info: https://community.transifex.com/t/postponing-api-2-0-2-5-and-transifex-client-sunset-date/2759

Blocked by https://github.com/sphinx-doc/sphinx-intl/issues/60


Could not find a version that satisfies the requirement nvidia-ml-py>=375.53

when i run "pip install -r requirements.txt" in conda python=2.7
it show tips like this : Could not find a version that satisfies the requirement nvidia-ml-py>=375.53
Is anyone know how can i fix that?

The naming convention of nvidia-ml-py has changed. You can refer to the following link: https://forums.developer.nvidia.com/t/mistake-with-nvidia-ml-py-on-pypi/112942.
What i use the version of nvidia-ml-py is 12.560.30, and it works! I hope it can help you.

当我在 conda python=2.7 中运行“pip install -r requirements.txt”时， 它会显示如下提示：找不到满足要求 nvidia-ml-py>=375.53 的版本
有人知道我该如何修复它吗？

The naming convention of nvidia-ml-py has changed. You can refer to the following link: https://forums.developer.nvidia.com/t/mistake-with-nvidia-ml-py-on-pypi/112942.
What i use the version of nvidia-ml-py is 12.560.30, and it works! I hope it can help you


Supported?

It's been a long time since this project was updated, is it still maintained?

Not really. Go-libsass has much better sass support. It will take considerable effort to catch this project up.


Add greatest(T,...) and least(T,...) SQL functions

Is your feature request related to a problem or challenge?
a challenge to implement greatest and least SQL functions
Describe the solution you'd like
Similar to the 2023 standard
Describe alternatives you've considered
using if else but it is very cumbersome
Additional context
No response

I'd like to continue this task if you don't mind. AFAIK there isn't an obvious blocker from the history of #6527 by @jimexist and #12474 by @rluvaton.
For the topic in #12357 by @alamb, given greatest and least are both supported by PG and in the spec, adding them to the built-in function list makes sense to me.

I can reopen my pr and add it

Upate is that @rluvaton  added support for greatest in

https://github.com/apache/datafusion/pull/12474

Perhaps we should file a separate ticket for least 🤔

I'll try to add the least function in the coming week


Update brands.txt

Added 8 known legit office furniture brands
BenchPro
Boss Office Products
Chair Master
Flash Furniture
HON
Laura Davidson Furniture
Modway
Office Star
Also, there were a couple of sort issues (see commit for changes)

I'm currently out of town but will be able to review and merge this later tonight.


More this page inside of Main Homepage

I am starting to wonder do we need a separate subdomain showing our timezone information? Instead how about integrating this page under the main website https://manim.community say under a page called /timezone? What do you guys think?

Yeah, agreed that would make more sense.


Update Vocalink data sets to versions valid as of 27/05/2019

Hi,
This pull request includes the new Vocalink data which became valid on 27 May 2019.
Thanks!

Thanks for the PR @gunjam. The new release is already available.


Approximate time sync for odom/scan input to HdlGraphSlamNodelet

Hello, this is a pull request for the diff I posted in #74 .
It allows the HdlGraphSlamNodelet to use odometry when the odom message timestamps do not exactly match the pointcloud message timestamps - as would be typical if using, say, wheel encoder odometry.
This is achieved by switching the time synchroniser for sync::ApproximateTime.
http://wiki.ros.org/message_filters/ApproximateTime
From my understanding of the filter, it will have the same behaviour as before if timestamps match exactly, and if they don't then odometry will be matched to point clouds based on proximity in time.
I've tested on the provided hdl_501_filtered.bag, I didn't notice any difference in the resulting map before and after this change.

Thanks a lot for the pull request. It would be helpful for many users :+1:


Support KW 566\d{5} as a valid mobile range for VIVA

Please read the "guidelines for contributing" (linked above) and fill in the template below.
Country/region affected (e.g., "US"): KW
Example number(s) affected ("+1<PHONE_NUMBER>"): +96556607933
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):
The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
The cost, if applicable ("toll-free", "premium rate", "shared cost"):
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): IMPORTANT - anything posted here is made public. Read the guidelines first!
link to demo

Thanks for reporting @wakiel!
We've accepted this issue and will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we
may use, modify, reproduce, publicly display, and distribute the information in
accordance with our open source policies. Please let us know if you did not
intend to submit the information for such use.

hi ,when will be the coming release date ?
Date: Mon, 4 Jul 2016 04:52:10 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [googlei18n/libphonenumber] Validation issue with +96556607933 (KW) (#1190)
Thanks for reporting @wakiel!
We've accepted this issue and will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we
may use, modify, reproduce, publicly display, and distribute the information in
accordance with our open source policies. Please let us know if you did not
intend to submit the information for such use.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Mid-next week. This is expected to be fixed in that release.

dears when we will have a new MSISDN range , to which e mails or link we have to send to have that range defined fast and avoid any delay in activating new accounts for :-Twitter , face book , Whatsapp , ,, and other VoIP applications
Date: Fri, 8 Jul 2016 06:57:59 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [googlei18n/libphonenumber] Support KW 566\d{5} as a valid mobile range for VIVA (#1190)
Mid-next week. This is expected to be fixed in that release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

If the information is public you can file an issue as you did this one.
Otherwise for private documents please sign the CLA and join the group for documentation sharing.
You can see detailed instructions in our contribution guidelines.

Dear can you help us to get that issue solved by today or it will take more time :) ?
Date: Fri, 8 Jul 2016 06:57:59 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [googlei18n/libphonenumber] Support KW 566\d{5} as a valid mobile range for VIVA (#1190)
Mid-next week. This is expected to be fixed in that release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@wakiel,
This fix will be part of upcoming release. Mostly it will happen by tomorrow.

Fixed in 7.4.5


when I try to install angular , I got below error. I have used so many commands to get rid out of this.

C:\Program Files\nodejs>npm install -g @angular/cli
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code EEXIST
npm ERR! path C:\Users\XXXXX\AppData\Roaming\npm\node_modules@angular\cli\bin\ng
npm ERR! dest C:\Users\XXXXX\AppData\Roaming\npm\ng
npm ERR! EEXIST: file already exists, cmd shim 'C:\Users\XXXXXX\AppData\Roaming\npm\node_modules@angular\cli\bin\ng' -> 'C:\Users\XXXXXX\AppData\Roaming\npm\ng'
npm ERR! File exists: C:\Users\XXXXXX\AppData\Roaming\npm\ng
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
npm ERR!      C:\Users\XXXXXX\AppData\Roaming\npm-cache_logs\2020-06-26T18_27_50_041Z-debug.log

Please read #3142, then refer to #3143


There is no "..." next to the “Disable Static Website” option

OS: Win10
Build Version: 20230407.1
Regression: Not a Regression
Repro Steps:

Right click a storage account.
Check the context menu.

Expect:
There is a "..." next to the “Disable Static Website” option.
Actual:
There is no "..." next to the “Disable Static Website” option.

More Info:
This issue also reproduces when executing "Azure Storage: Disable Static Website" from command palette.

There is a prompt after selecting Disable Static Website so we should have indices after the command name.


🛠 Tooling: Use Remix's static deployments

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Thanks to the glorious efforts of the wonderful @brophdawg11 in https://github.com/remix-run/react-router/pull/11539, Remix now has the ability to pre-render to static HTML files. That's what this site is currently deployed to in production - so let's use that!
Additional Info
What we do now is ... not ideal:
https://github.com/JoshuaKGoldberg/boston-ts-website/blob/2867f57fe3c63b95e48e9b7efa19b05807ba06c5/.github/DEVELOPMENT.md#L24-L37
Reference of the experimental things we'll need to do: https://github.com/philly-js-club/philly-js-club-website/pull/97

https://github.com/philly-js-club/philly-js-club-website/pull/105 shows how we're doing this on the Philly JS Club side.


Upgrade project to XCode 10.3.

Disabled code sign.
Increased deployment target to 10.6.

This is a great PR. I hope it will be merged eventually.

I know of a bug... but will merge this and create a new PR to fix


Add disableAvm flag, which turns off both AVM1 and AVM2.

This is extremely useful for anyone who wants to host and display a SWF on their site, but does not know or does not trust the author of the SWF.
Adding disableAvm: true to the SWF.embed() options allows SWFs to render and play, but without executing any of the code inside (which could potentially be malicious).

This PR is stale, a lot has changed. If we still need this feature, we should submit a new PR.


typo: powerbi-docs/desktop-tooltips.md

assocaited -> associated
uints -> units

@nschonni : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

Verified the updates.

@ktoliver : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.


Portal theme research

Requirements:

Customizable
Open-source licence
Responsive layout

We will use PrimeNG as the component library. The library is licensed under MIT.
https://primefaces.org/primeng/
The theme can be customized with the "Theme Designer" from PrimeNG.
https://primefaces.org/primeng/showcase/#/theming
The Theme Designer is not free. However, the resulting CSS can be used in an Open-Source project, but not the SCSS files required to generate the CSS. They will have to be kept in a private repository.
We will start with one of the free provided themes that are under MIT.

The Theme Designer is not free. However, the resulting CSS can be used in an Open-Source project, but not the SCSS files required to generate the CSS. They will have to be kept in a private repository.

How should we tackle that? It feels a bit disturbing to store parts of this project in a private repository and doesn't feel Open Source like...

What do you mean by "How should we tackle that?"?
PrimeNG comes with 33 free themes: https://primefaces.org/primeng/showcase/#/setup
These themes are all open-source under the MIT licence and can be edited.
However, that is not the best way to create a stunning custom theme. The easier way is to use the “Theme Designer” from PrimeNG which costs $490. As luck would have it, nxt has a licence which we can use in this project ;-).
The "Theme Designer" itself is also an angular app, which can be checked in into a private repository.
We can then use the designer to create a stunning theme and export it into a theme.css. This resulting theme.css file can be used instead of an open-source PrimeNG theme.  The "Theme Designer" is like an IDE. It helps you to create a theme. But it is not needed. If you are a badass, you can do it in vi. However, that would take you a lot longer ;-).

Maybe I misunderstood the part "but not the SCSS files required to generate the CSS". What does that mean?

SCSS is an extension of the syntax of CSS. It has variables, loops, ifs and so on. SCSS files are compiled into one or many CSS files, so the browser can understand them. The “Theme Designer” from PrimeNG contains all SCSS files required to build a theme.css file. Unfortunately, this SCSS files are not open-source. That's because PrimeNG earns its money with it.


fixed sorted maplists playing the wrong map

also the engine decided to change some import files on its own

Hi, just tested and is fixed when using the sorting presets, but not when using the search feature

Working now, thanks!


Remove broken SVGs

We had one more particularly weird CSS error (blocking #466) that took me a while to track down. Here's the story.
Inside of _forms.scss we have an image for radio inputs and checkboxes that are in a checked + hover state. However (and you can double check them on the styleguide here: https://mapzen.com/common/styleguide/design-elements.html#forms) these hovered states do not work properly. It's very subtle, but the hover state is actually black instead of dark purple.
If we examine the SVG data-URI, it would be the equivalent of this string:
<svg data-name='Layer 1' xmlns='http://www.w3.org/2000/svg' viewBox='0 0 36 36'><title>checkbox-focused</title><path fill='!E0E33e' d='M0 0h36v36H0z'/><path fill='none' stroke='#fff' stroke-linecap='round' stroke-linejoin='round' stroke-width='4.252' d='M26.19 11.16l-9.17 13.68-7.21-5.22'/></svg>

The problem lies in path fill='!E0E33e', which mistakenly uses a ! instead of a # for a hex color. This was making the CSS minifier very unhappy. (I don't think it's the minifier's business to parse data-URIs, but that's a separate conversation.)
If it were formatted properly, the hovered checkbox state would be this version of yellow instead of black:

Upon reviewing with @souperneon we decided that if it didn't work before, it doesn't need to work now, especially since this yellow is not really used anywhere else. So we can fix the minifier issue just by removing the offending data-URIs from the styleguide.

I wonder this happened while manually converting svg to (otpimized svg and then to ) datauri. 🤔 Thanks for tracking it down!


Use upstart stanzas to set environment

Are you reffering to upstart's env directive?
This may be good time to think further about supporting limit and maybe chdir as documented in http://upstart.ubuntu.com/wiki/Stanzas


Release 0.2.8

Hi, may I know when this will be released, please? I noticed the 0.2.7 was approved and merged on the same day so thought I would ask xD. TIA!

Hi, may I know when this will be released, please? I noticed the 0.2.7 was approved and merged on the same day so thought I would ask xD. TIA!
@aaguilarguero we have just released 0.2.8. thank you!


feat: card supports image prop that readers passed image on top of the card

This PR will enable card component accept image prop that is basically an image link. This image is passed to img element that renders an image.
closes #57
Screenshots

@sboy99  try this: https://stackoverflow.com/a/71063465

That was a mistake while I was resolving merge conflict className in  component got replaced by previous so the changes were lost that image is not going to the edge. Is it working now?

@sboy99 can you make a PR in mint updating the Card docs with the new image property?

Sure I will do

Should I update only API reference or should I showcase A example component with API reference


Check domains of StrainToVolume

For the 4 types of strains, usually they are reals, but sometimes, even if they are complex numbers, they still can produce real volumes.

Eg. Eulerian & Lagrangian strains can be real if (2f + 1)^(3 / 2) are real, even if f is a Complex, which means the argument of 2f + 1 is an integer multiple of 120 degrees.
Natural strains can be real if exp(3f) is real, which means the argument of f is an integer multiple of 60 degrees.
Infinitesimal strains can be real if (1 - f)^3 is real, which means the argument of 1 - f is an integer multiple of 60 degrees.


Fixed Distributed: the number of indexes to keep after merging small indexes can't be bigger than the number of small indexes

LGTM ! Good catch !

Thanks!


Hooking up getDocCommentTemplateAtPosition() in Eclipse

I'm really excited by the new getDocCommentTemplateAtPosition() functionality and I'm trying to hook it up for Eclipse (for https://github.com/palantir/eclipse-typescript).
In Eclipse, the typical way of starting a documentation comment is by typing "/**" and then hitting <enter>. It looks like the current getDocCommentTemplateAtPosition() may not support this method of autocompleting a doc comment though (but perhaps I'm misunderstanding how to call it).

Basically what we do is

Determine whether the current location in the buffer is a JSDoc comment completion location.

Basically this consists of

Ensuring the immediately preceding text is /** (watch your indexes here!).
Ensuring that the only thing preceding the comment on the current line is whitespace,
Ensuring there isn't an existing multiline comment (basically whether the next non-whitespace is an * or EOF. (This is a very rough approximation).

Yes, I think we should move this to the script side, and not do this on the managed side.

If the above succeeds, erase the relevant text span for which the /** applies, then try to call into the script language service to see if it can give us a JSDoc completion.
If we got a completion from the script language service, insert the relevant text.

Whoa, ok, thanks for the thorough explanation. I got it working now - this is pretty cool!
I think it might be easier to use the API if the service could handle more of this stuff. In particular, step 2 is kinda tricky because it requires deleting characters, then calling getDocCommentTemplateAtPosition(), then restoring the deleted characters if undefined is returned (which happens for methods currently because they are unsupported).

Yup, I'll discuss with @mhegazy. If @CyrusNajmabadi has any input why this would or would not be a good idea it'd be appreciated.

The problem is it is a bit late for the language service at this point. ideally you would hold on to the snapshot before the user entered "/**", alternatively, if you are automatically adding the closing comment "*/", you can do the check afterwards.
I agree that the workflow for the API user is not great. @CyrusNajmabadi any suggestions here?

I don't think there is a problem with the API.  I think the right way to think about it "I'm going to ask the question about Doc comments as if there wasn't a doc comment already written in the source.".  This is necessary as the question becomes super difficiult the moment you ask it on code that does have the start of the comment already in there.  i.e. if the code looks like:
/**
public Blah(i: number) ...

Then, from TS's perspective, it just looked like an entirely commented out region of code.
The idea, as Dan said, is that the host will go "let me get the buffer back to the state before the comment was inserted.  Then, i'll ask about doc comments.  Then, if i get something back, i'll insert that in place.  I think that's a non-arduous model to implement.

Yes, I think we should move this to the script side, and not do this on the managed side.

I don't see a problem with this.  I think we should take the existing Classifier API and move it to a more general "real time, synchronous language service" API.  i.e. it's for features that ask really simple, non-tree, non-syntax, based questions on the text of the document.
Examples of features that would sit here would be:

the lexical classifier. It needs to be real time.  It only cares about strings.
the doc comment check.  (i.e. everything we've been talking about).
quick questions about completion lists.  i.e. "is this a trigger character".

Basically, all the places we hardcode smarts about TS into the Managed layer (because we don't want to marshal to another thread when we're on the UI thread) should move into here.  Dan, do you want to do this?  @paulvanbrenk or @vladima could also do it.

I thought we were trying to move to the syntactic classifier, why would we invest in the lexical classifier again? It sounds like we'd have to implement a scanner for TypeScript in C#.
Do you mean just a general restructuring of the managed side?

I thought we were trying to move to the syntactic classifier,

Even with the syntactic classifier, the lexical classifier is still necessary.

It's what is used when a file is open and we don't even have a tree.  If we need ot wait for a tree, you could have black text for several seconds.  (This is easy for you to try out by just disabling the lexical classifier and trying to open a compiler file).

Even if we have trees, syntactic classification can be noticeably slow.  This is because perception time for classification is on the order of milliseconds.  Syntactically classifying still involves us having to marshal to another thread, wait for an existing task to finish, marshall over to the script side, have the script side incrementally parse, marshall over the results, and then then have the async tagger display things.  The async tagger itself adds overhead as well as it batches and throttles.  So syntactic classification in the absence of lexical can be very noticeable.

The benefit of Syntactic classification is correctness.  The benefit of Lexical is perf.  You want both, and so we need to keep both.
Note: thanks to @JsonFreeman's great idea about ClassificationTag ordering, we don't need to coordinate the two classifiers.  They can both produce results on their own schedule, and the Syntactic classification tags will naturally override the lexical one.
That way things look really fast (because of the lexical classifier doing things quickly), but they'll always appear accurate almost immediately.  In the 99% case where you're not tying anything lexically odd, you won't even notice because no visible change will happen.

Do you mean just a general restructuring of the managed side to clarify where these APIs should go?

I mean a restructing on the script side.  Right now we have:

Lexical operations that happens on the UI thread.  These go through the ClassifierProxy.
Syntactic operations that happen on one of two syntactic threads.
Semantic operations that happen on the semantic thread.

On the managed side though we hard-code in several bits of knowledge about TS on the managed side.  This is so we can answer things quickly on the UI thread (since we don't want to jump the syntactic or semantic threads).  These operations should move to the script side.  THe most natural place for this is the Classifier object on the script side.  Except now that will be a terrible name.  Because we'll be asking non-classifier related questions.  So i'm saying, rename that guy to better reflect that it's for extremely cheap, extremely fast, text only questions that the host has.   or "is this a trigger character?")
should i insert a JSDoc comment here?

I think that is very sensible, and I can't imagine there are that many synchronous operations that would have to be moved over. The reason the classifier is its own thread is not because it's the classifier. It's because it happens to be the sole operation that runs synchronously on the UI thread that needs knowledge of TypeScript. That concept could be naturally generalized.

We should open different issues for the action items from this issue.


CAMEL-21127 - Migrate from Deprecated o.a.maven.plugins.annotations.Component

Description
Migrate Camel plugins from @org.apache.maven.plugins.annotations.Component
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.
[x] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

Yes lets do this after 4.8.0 release as we had troubles in the past with doing some last minute maven changes or other build system changes that caused an upcoming release to fail.


chore: Update GitHub Actions

Codecov Report

Merging #448 (d23b735) into main (d4b1f29) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #448   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          503       503
  Branches        40        40
=========================================
  Hits           503       503

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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


V1.2.0

Build against Apache Kafka 0.10.2
Added support for Scala 2.12.1
Added .stateTable and .windowStateTable method for retrieving the contant of the state store as Map
Added contributors file
Removed dependencies to Log4j and Slf4j
Updated RocksDB version to 5.0.1
Updated ScalaTest version to 3.0.1
Added assertions in the test for input validation

As discussed, waiting for the state store changes.

@hrafzali, for me the MAX_VALUE issue did not arise, maybe a caching problem there was a wrong method header though. I also shortened the fixture values. Added documentation for stateTable and windowStateTable and added some extra tests for input validations.

@jpzk LGTM!

Allright, I am going to merge and then release


STORM-2972: Replace storm-kafka with storm-kafka-client in storm-sql-…

…kafka
https://issues.apache.org/jira/browse/STORM-2972
The new kafka scheme syntax is stolen from Apache Camel, since I figure we are doing something very similar to them.
The primary limitation here compared to the storm-kafka version is that you can't include metadata (e.g. partition) in the emitted tuple, because I had to adapt the Scheme API to the RecordTranslator API used in storm-kafka-client. Emitting metadata with a Scheme in the storm-kafka spout is handled by special case instanceof'ing the scheme to see if it fits one that takes metadata, and I'd really prefer not to do that.
If we need to be able to emit metadata as well, we can just allow people to override the RecordTranslatorSchemeAdapter. I'll leave that as a task for later, unless someone objects.

I tried out storm-sql-kafka with a small example similar to the orders example at https://storm.apache.org/releases/2.0.0-SNAPSHOT/storm-sql.html. I adjusted the docs for the storm-sql-example page, but did not go through and run it.


 We run gofmt -s on your code, where -s is for the "simplify" command

No problems detected. Good job!

go_vet100%
go vet examines Go source code and reports suspicious constructs, such as Printf calls whose arguments do not align with the format string.

No problems detected. Good job!

gocyclo90%
Gocyclo calculates cyclomatic complexities of functions in Go source code. The cyclomatic complexity of a function is calculated according to the following rules: 1 is the base complexity of a function +1 for each 'if', 'for', 'case', '&&' or '||' Go Report Card warns on functions with cyclomatic complexity > 15.

bb/strategies/http_egress_test.go
Line 14: warning: cyclomatic complexity 17 of function TestHttpEgressStrategy() is high (> 15) (gocyclo)
bb/protocols/http_test.go
Line 17: warning: cyclomatic complexity 20 of function TestTheHttpServer() is high (> 15) (gocyclo)
golint59%
Golint is a linter for Go source code.

bb/service/service.go
Line 13: warning: exported type Config should have comment or be unexported (golint)
Line 26: warning: exported type Client should have comment or be unexported (golint)
Line 53: warning: exported function MakeFireAndForget should have comment or be unexported (golint)
Line 57: warning: exported type Server should have comment or be unexported (golint)
Line 61: warning: exported type Strategy should have comment or be unexported (golint)
Line 65: warning: exported type RequestHandler should have comment or be unexported (golint)
Line 70: warning: exported method RequestHandler.Handle should have comment or be unexported (golint)
Line 75: warning: if block ends with a return statement, so drop this else and outdent its block (golint)
Line 96: warning: exported type Service should have comment or be unexported (golint)
Line 102: warning: exported method Service.Close should have comment or be unexported (golint)
bb/strategies/http_egress.go
Line 19: warning: exported const HttpEgressStrategyName should have comment (or a comment on this block) or be unexported (golint)
Line 27: warning: exported type HttpEgressStrategy should have comment or be unexported (golint)
Line 33: warning: exported method HttpEgressStrategy.Do should have comment or be unexported (golint)
Line 63: warning: exported function NewHttpEgress should have comment or be unexported (golint)
bb/strategies/point_to_point_channel.go
Line 11: warning: exported const PointToPointStrategyName should have comment or be unexported (golint)
Line 13: warning: exported type PointToPointChannelStrategy should have comment or be unexported (golint)
Line 17: warning: exported method PointToPointChannelStrategy.Do should have comment or be unexported (golint)
Line 23: warning: exported function NewPointToPointChannel should have comment or be unexported (golint)
bb/strategies/terminus.go
Line 12: warning: exported const TerminusStrategyName should have comment or be unexported (golint)
Line 13: warning: exported const TerminusResponseTextArgName should have comment or be unexported (golint)
Line 15: warning: exported type TerminusStrategy should have comment or be unexported (golint)
Line 19: warning: exported method TerminusStrategy.Do should have comment or be unexported (golint)
Line 31: warning: exported function NewTerminusStrategy should have comment or be unexported (golint)
bb/protocols/grpc.go
Line 48: warning: exported function NewGrpcServerIfConfigured should have comment or be unexported (golint)
Line 71: warning: exported function NewGrpcClientsIfConfigured should have comment or be unexported (golint)
bb/protocols/http.go
Line 150: warning: exported function NewHttpServerIfConfigured should have comment or be unexported (golint)
Line 166: warning: exported function NewHttpClientsIfConfigured should have comment or be unexported (golint)
bb/service/test_helper.go
Line 9: warning: exported type MockClient should have comment or be unexported (golint)
Line 18: warning: exported method MockClient.Close should have comment or be unexported (golint)
Line 23: warning: exported method MockClient.GetId should have comment or be unexported (golint)
Line 25: warning: exported method MockClient.Send should have comment or be unexported (golint)
Line 33: warning: exported type MockServer should have comment or be unexported (golint)
Line 37: warning: exported method MockServer.GetId should have comment or be unexported (golint)
Line 39: warning: exported type MockStrategy should have comment or be unexported (golint)
Line 46: warning: exported method MockStrategy.Do should have comment or be unexported (golint)
bb/cmd/services.go
Line 63: warning: exported function NewService should have comment or be unexported (golint)
Line 111: warning: exported function NewStrategyByName should have comment or be unexported (golint)
bb/strategies/broadcast_channel.go
Line 15: warning: exported const BroadcastChannelStrategyName should have comment or be unexported (golint)
Line 17: warning: exported type BroadcastChannelStrategy should have comment or be unexported (golint)
Line 21: warning: exported method BroadcastChannelStrategy.Do should have comment or be unexported (golint)
Line 69: warning: exported function NewBroadcastChannel should have comment or be unexported (golint)
license0%
Checks whether your project has a LICENSE file.

ineffassign95%
IneffAssign detects ineffectual assignments in Go code.

bb/protocols/http_test.go
Line 169: warning: err assigned and not used (ineffassign)
misspell100%
Misspell Finds commonly misspelled English words

No problems detected. Good job!

Master right now:


Open BIM React template bug in Chrome and Safari browsers

Describe the bug 📝
I have installed and run Open BIM React template. And first time I could to load iFC model, but next times - no (

I am loading model and There is error in console

ok - I solved it by copy web-ifc.wasm file to public directory

try to load again and there is other error in console

I've solved it by put row await culler.setup() before culler add mesh.

try to load again and there is other error in console

Interesting fact, that in Firefox browser it works great and no errors. But I tried Chrome, Safari browsers, there are problems I described above
Reproduction ▶
No response
Steps to reproduce 🔢

Install it globally with npm i -g openbim-app-templates.
Create a folder anywhere you want and open it within your IDE.
In the terminal of the opened folder, run create-openbim-app and follow the prompts.
Run npm i and then npm run dev

System Info 💻
MacOS M1Pro Sonoma OS 14.2

Used Package Manager 📦
pnpm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Solved by clear localstorage


Mandatory replace requests

Is your feature request related to a problem? Please describe.
Any vault that provides unused mint capacity is subject to the ‘risk’ of receiving an issue request that can fill up all its remaining mint capacity. Hence, a replace request by another vault is nothing else than an issue request by a user (and hence should charge the same fees) but helps vaults at risk to mitigate liquidations.
Describe the solution you'd like
If a vault can request a replace by another vault with certainty, there is much lower risk of getting liquidated. If the vault which is supposed to replace the original vault has an option to decline this request, that option of risk mitigation becomes quite meaningless.
Additional context
We can achieve this functionality without changing too much in the replace core model.

As is: oldVault announces to want to replace X BTC
Changed: oldVault can accept replace request on behalf of newVault (similar to how on issue the vault is not involved but rather the user makes the request and the vault cannot decline)
As is: execution of the request.

If we want mandatory replace requests, we can simplify replaces a lot by removing the request_replace and withdraw_replace extrinsics, and modifying accept_replace such that it can be called by the old vault (and probably rename the function at that point)

Yes, I think that is ideal.

Following is the proposal for the mandatory replace request

accept_replace extrinsic

Parameters

old_vault:AccountID
new_vault:VaultID
amount: BalanceOf<T> // amount in IBTC
currency_pair: DefaultVaultCurrencyPair<T>

Flow Diagram

Questions
Question 1: Is collateral for replacement value necessary to be provided as a parameter or can it be calculated in runtime depending upon the wrapped token amount
-> If no how do I use calculate_collateral as it takes 1st parameter as collateral.

I think the following steps need to be done. A problem is that by making replace request originate from the old_vault, we can't supply a btc address as argument. Instead, we'll have to generate one like we do for issue, which does mean the client needs changes as well.

remove the existing request_replace and withdraw_replace extrinsics

Rename the current accept_replace to request_replace

Change the new request_replace such that it is called by the old_vault rather than new_vault

remove the collateral argument - instead we'll determine the collateral amount based on the amount_btc

Remove btc_address - we'll have to auto-generate a deposit address like we do for issue

remove replace_collateral from the vault type, it's no longer used

On the client side, we'll have to scan for new replace deposit addresses the same way we do for issue

It's quite an involved change.. I'd like to have a think about if we can re-use the issue/redeem logic, as essentially the old-vault is making an issue with the new_vault, while the new_vault is making a redeem with the old_vault

We can't supply a btc address as argument
Why not? Do you mean from a UX perspective? In that case we can just use the master key which is already in the Vault's wallet.

Otherwise the change is as you describe, basically refactor accept_replace to request_replace. I would be happy for @nakul1010 to make that change already and then we can review after if it is possible to refactor further.

Why not? Do you mean from a UX perspective? In that case we can just use the master key which is already in the Vault's wallet.

The master key is per account_id, not per vault_id though, so it's not part of the vault's currency-specific wallet

Had a discussion with @sander2, we believe the best way forward is to re-use the issue and redeem logic. @nakul1010 hold-off on the implementation for now until we've had a chance to review the design.

We will refactor the replace pallet to reuse issue and redeem events / structs. Let's assume Vault A (old_vault) now wants to move their BTC to Vault B (new_vault) we can do the following:

Vault A calls request_replace against Vault B
Issue generates BtcAddress for Vault B
Redeem request is generated for Vault A to send BTC to Vault B (using generated address)

Don't reserve wrapped tokens (since Vault A doesn't have any)

Vault A sends BTC to Vault B (address + OP_RETURN)
Vault A calls execute_replace with BTC transaction

We need to disallow execute_issue and execute_redeem

Redeem request is executed
Issue request is completed

Don't mint wrapped tokens

Some very rough code as a guide:
#[pallet::storage]
pub(super) type Requests<T: Config> = StorageMap<_, Blake2_128Concat, H256, H256>;

fn request_replace(
  old_vault_id: DefaultVaultId<T>,
  new_vault_id: DefaultVaultId<T>,
  amount: BalanceOf<T>,
) {
  // Vault B increases to_be_issued
  let (issue_id, btc_address) = Issue::request_issue(
    new_vault_id, // account to receive BTC
    amount, // amount of BTC
  );
  // Vault A increases to_be_redeemed
  let redeem_id = Redeem::request_redeem(
    old_vault_id, // account to send BTC
    btc_address, // owned by Vault B
    amount, // amount of BTC
  );
  Requests::insert(redeem_id, issue_id);
}

fn execute_replace(
  redeem_id: H256,
  unchecked_transaction: FullTransactionProof,
) {
  // Vault A decreases to_be_redeemed (and issued_tokens)
  Redeem::execute_redeem(redeem_id, unchecked_transaction);
  let issue_id = Requests::take(redeem_id);
  // Vault B decreases to_be_issued
  // Vault B increases issued_tokens
  Issue::complete_issue(issue_id);
}

Both extrinsics are submitted by the old_vault.
We should hence remove any unused replace code including storage items, events and extrinsics. We can also remove to_be_replaced_tokens, replace_collateral, and active_replace_collateral on the Vault struct. Please also consider any necessary migrations.
To disallow the other "execute" extrinsics (and generally make merging this into issue / redeem easier) it might be worth considering altering the IssueRequest and RedeemRequest structs, for example requester / redeemer could become:
enum AccountOrVault<AccountId, CurrencyId> {
  Account(AccountId),
  Vault(VaultId<AccountId, CurrencyId>)
}

Hmm I'm not completely convinced by this approach - both on the parachain side and on the client side this needs special handling. If we go with the issue/redeem approach, then I think for the vault client they should appear as normal issue/redeems. So the old_vault would execute by calling execute_redeem rather than execute_replace. The parachain can then apply replace logic if the AccountOrVault type is a Vault

Otherwise if we're ok with special handling on vault side then we might as well keep the current approach of having a special replace type, since arguably that keeps the parachain simpler

We had a call to discuss the approach and I think we are in agreement. Let's still remove the replace pallet (and Vault struct fields) but modify the following structs:
pub struct IssueRequest {
  ...
  pub requester: AccountOrVault,
}

pub struct RedeemRequest {
  ...
  pub redeemer: AccountOrVault,
  pub issue_id: Option<H256>,
}

We can add the request_replace extrinsic to the redeem pallet, but we should modify execute_redeem to include an additional code path for when issue_id is set. As stated before we should disallow the normal execution if the requester or redeemer is a Vault. Note that this approach creates an issue dependency on the redeem crate.

Yup agreed, just a small note that we don't need the pub redeemer: AccountOrVault, change - the request already contains the vaultid so if issue_id is set, you can just use that one


Create dvpn_on_wsl.md

Experimental guide to run Sentinel dVPN Node on WIndows SUbsystem for Linux.
It is quite complex deployment, however interesting experience for those who don't want to run virtual machines and stillw ant to run dVPN node.

Closed as new docs website has now been deployed


Google pay payment token decrypt with Jave "cannot verify signature"

I use three method to add sender verifying key from Google root signing keys test link, however it still error for "cannot verify signature".  And I used TEST environment to try google pay.  Which part don't I notice it? Thanks.

java.security.GeneralSecurityException: cannot verify signature

`  String decryptedMessage =
new PaymentMethodTokenRecipient.Builder()
.fetchSenderVerifyingKeysWith(GooglePaymentsPublicKeysManager.INSTANCE_TEST)
//                        .addSenderVerifyingKey(senderVerifyingKey)    // verify signature public key string
//                        .senderVerifyingKeys(senderVerifyingKeyJson)    // verify signature public key json
.recipientId("merchant:01234567890123456789")   //<PHONE_NUMBER>1234567890
// This guide applies only to protocolVersion = ECv2
.protocolVersion("ECv2")
// Multiple private keys can be added to support graceful
// key rotations.
.addRecipientPrivateKey(recipientPrivateKey)
.addRecipientPrivateKey(recipientPrivateKey)
.build()
.unseal(ciphertext);
    System.out.println(decryptedMessage);
}`

Freya Griffin
On Tue, Sep 10, 2019, 3:08 AM Wu<EMAIL_ADDRESS>wrote:

I use three method to add sender verifying key from Google root signing
keys test link, however it still error for "cannot verify signature". And I
used TEST environment to try google pay. Which part don't I notice it?
Thanks.
java.security.GeneralSecurityException: cannot verify signature
` String decryptedMessage =
new PaymentMethodTokenRecipient.Builder()
.fetchSenderVerifyingKeysWith(GooglePaymentsPublicKeysManager.INSTANCE_TEST)
// .addSenderVerifyingKey(senderVerifyingKey) // verify signature public
key string
// .senderVerifyingKeys(senderVerifyingKeyJson) // verify signature public
key json
.recipientId("merchant:01234567890123456789") //<PHONE_NUMBER>1234567890
// This guide applies only to protocolVersion = ECv2
.protocolVersion("ECv2")
// Multiple private keys can be added to support graceful
// key rotations.
.addRecipientPrivateKey(recipientPrivateKey)
.addRecipientPrivateKey(recipientPrivateKey)
.build()
.unseal(ciphertext);
System.out.println(decryptedMessage);

}`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/tink/issues/249?email_source=notifications&email_token=AMBPERFTMMWETPFKURZJ33LQI5IWFA5CNFSM4IVELLOKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HKL6DXQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMBPERHTGIG6WDAEEQSE7OLQI5IWFANCNFSM4IVELLOA
.

I find my problem for wrong test sender verify key.
Additionally, the merchant id is<PHONE_NUMBER>0123456789 for test environment.

01234567890123456789

Hey @st931630 I'm facing the same issue, I'm using google's test ECv2 keys as sender Key
https://payments.developers.google.com/paymentmethodtoken/test/keys.json
And the merchant I tried both,<PHONE_NUMBER>0123456789 and generated my merchant.
Can you please help?

01234567890123456789

Hey @st931630 I'm facing the same issue, I'm using google's test ECv2 keys as sender Key
https://payments.developers.google.com/paymentmethodtoken/test/keys.json
And the merchant I tried both,<PHONE_NUMBER>0123456789 and generated my merchant.
Can you please help?

I used this method to get google verify signature.
`Verify signature
The tokens produced in ENVIRONMENT_TEST are encrypted with your test public key that was previously sent to Google.
The tokens are signed with Google's test keys. If you use Tink, ensure that .fetchSenderVerifyingKeysWith(GooglePaymentsPublicKeysManager.INSTANCE_TEST) is set when you build a PaymentMethodTokenRecipient object.`
reference:
https://developers.google.com/pay/api/android/guides/resources/sample-tokens#verify-signature
And merchant id for test environment is '12345678901234567890'.
*Notice: If you complete a DIRECT tokenizationSpecification type integration, you must annually rotate your public encryption key and provide PCI Attestation to Google via the Business Console.
So I used GATEWAY type integration, and I don't use Tink to decrypt payment data by myself.

I had similiar exeption.
I'm using C# wrapper  for tink and this is how my code looks like.
          private const string _paymentSampleToken = "{\"signature\":your_payment_sample_token...}";
          var keyProvider = new GooglePay.PaymentDataCryptography.GoogleKeyProvider(true);//true = test env
          var parser = new GooglePay.PaymentDataCryptography.PaymentMethodTokenRecipient("gateway:your_gateway_name", keyProvider);

          //loading pem key
          AsymmetricCipherKeyPair keyPair;
          var path = $"path to your key.pem file"
          using (var reader = File.OpenText(path)) // file containing RSA PKCS1 private key
              keyPair = (AsymmetricCipherKeyPair)new PemReader(reader).ReadObject();

          parser.AddPrivateKey((ECPrivateKeyParameters)keyPair.Private);
          string decryptedMessage = parser.Unseal(_paymentSampleToken);
          Console.WriteLine(decryptedMessage);

I had similiar exeption. I'm using C# wrapper  for tink and this is how my code looks like.
          private const string _paymentSampleToken = "{\"signature\":your_payment_sample_token...}";
          var keyProvider = new GooglePay.PaymentDataCryptography.GoogleKeyProvider(true);//true = test env
          var parser = new GooglePay.PaymentDataCryptography.PaymentMethodTokenRecipient("gateway:your_gateway_name", keyProvider);

          //loading pem key
          AsymmetricCipherKeyPair keyPair;
          var path = $"path to your key.pem file"
          using (var reader = File.OpenText(path)) // file containing RSA PKCS1 private key
              keyPair = (AsymmetricCipherKeyPair)new PemReader(reader).ReadObject();

          parser.AddPrivateKey((ECPrivateKeyParameters)keyPair.Private);
          string decryptedMessage = parser.Unseal(_paymentSampleToken);
          Console.WriteLine(decryptedMessage);

Hi - I have the same error,  Are there any updates on how you have resolved the issue?


Create a Template for Pull request

I would like to create a template for the PRs

I am a GSSoC'21 Participant. Please assign this issue to me.

@Kriti-bit Sure, done.


par()$usr[1:2] is not honored on return after the print method

I think this is because we reset par after we exit the print method.

Yeah, so do we really want to do that? If we reset, the user can't add stuff manually later (ie..with base R). If we don't reset, the altered par's stay in the system...but I don't think that's a big deal.

OH, and that fixes our mfcol problem!

OK, so in PR #140, I did this in print:
par(defaultPar)
(commented it out)...
For something like the inset plot, the user will have to know to reset the par...but they would in base R too. But, I think there are far more benefits than drawbacks to not reseting par.
However, maybe there are other issues I'm missing...hence I'll keep this open for awhile.

And now:
par(mfcol=c(2,2))
for(i in 1:num.plots){
  gs<-gsplot() %>%
    points(i,2)
  print(gs)
}


Dropin: You support the payment method 'scheme' but this component has not been configured. Make sure to import the Class  'Card' and then pass it in the Dropin's 'paymentMethodComponents' config property if you wish to offer this payment method.

"vite": "^5.2.8"  "@adyen/adyen-web": "^6.2.0"
The following error appears according to the official website integration
https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=Web&integration=Drop-in&version=6.2.0
Dropin: You support the payment method 'scheme' but this component has not been configured. Make sure to import the Class  'Card' and then pass it in the Dropin's 'paymentMethodComponents' config property if you wish to offer this payment method.

@xyg00 - what exactly is the issue here?

You can read more how to integrate here:
https://docs.adyen.com/online-payments/build-your-integration/advanced-flow/?platform=Web&integration=Drop-in&version=6.2.0#import-drop-in-with-individual-payment-methods


Implement 'app dev' support for Functions via draft versions

Implements app dev support for function extensions by watching for file changes, automatically rebuilding, and pushing an extension draft.
WHY are these changes introduced?
To align Functions with other extensions and enable a better inner loop DX.
WHAT is this pull request doing?

Performs an initial build and draft deploy of all function extensions on dev start.
Enables a file watcher which builds and draft deploys functions on any changes.
Adds a watch setting to function extensions to allow customizing the file watcher paths.

These new behaviors only apply for unified/simplified deployments.
How to test your changes?

Create a new app
Add a function extension
Enable unified/simplified deployments for the app
If using a non-JavaScript/TypeScript template, add the watch configuration to your function toml, e.g.[build]
command = "cargo wasi build --release"
path = "target/wasm32-wasi/release/order-discount-rust.wasm"
watch = "src/**/*.rs"

Run shopify app dev on the app, adding --verbose to validate draft deployments
Verify build and deploy on launch and when you make file changes.

Example output (end of startup + rust file change)
2023-06-22 16:27:41 │ extensions   │ Draft updated successfully for extension: order-discount-javascript
2023-06-22 16:27:41 │ extensions   │ Draft updated successfully for extension: order-discount-typescript
2023-06-22 16:27:41 │ extensions   │ Draft updated successfully for extension: checkout-validation-js
2023-06-22 16:27:42 │ extensions   │ Draft updated successfully for extension: order-discount-assemblyscript
2023-06-22 16:27:44 │ extensions   │ Draft updated successfully for extension: order-discount-cpp
2023-06-22 16:27:45 │ extensions   │    Compiling order-discount-rust v1.0.0 (/Users/nickwesselman/src/polyglot-functions/app/extensions/order-discount-rust)
2023-06-22 16:27:46 │ extensions   │ wasm-opt -Oz --zero-filled-memory --strip-producers -o build/order-discount-golang.wasm build/order-discount-golang-unopt.wasm
2023-06-22 16:27:48 │ extensions   │ Draft updated successfully for extension: order-discount-golang
2023-06-22 16:27:48 │ extensions   │     Finished release [optimized] target(s) in 14.24s
2023-06-22 16:27:48 │ extensions   │   Optimizing with wasm-opt
2023-06-22 16:27:50 │ extensions   │ Draft updated successfully for extension: order-discount-rust
2023-06-22 16:27:50 │ extensions   │ Function extension order-discount-cpp is missing the 'build.watch' setting, automatic builds are disabled.
2023-06-22 16:27:50 │ extensions   │ Function extension order-discount-assemblyscript is missing the 'build.watch' setting, automatic builds are disabled.
2023-06-22 16:27:50 │ extensions   │ Function extension order-discount-golang is missing the 'build.watch' setting, automatic builds are disabled.
2023-06-22 16:27:50 │ extensions   │ Function extension order-discount-zig is missing the 'build.watch' setting, automatic builds are disabled.
2023-06-22 16:29:36 │ extensions   │ Config file at path /Users/nickwesselman/src/polyglot-functions/app/extensions/order-discount-rust/shopify.function.extension.toml changed
2023-06-22 16:29:37 │ extensions   │ Draft updated successfully for extension: order-discount-rust
2023-06-22 16:29:41 │ extensions   │ Config file at path /Users/nickwesselman/src/polyglot-functions/app/extensions/order-discount-rust/shopify.function.extension.toml changed
2023-06-22 16:29:42 │ extensions   │ Draft updated successfully for extension: order-discount-rust

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

@Arkham

I'm a bit surprised by this, I would have expected the function to be killed when the abortcontroller was terminated. cc @matteodepalo

ConcurrentOutput is not using the AbortController to finish the command but a treeKill. I have created a PR to restore the use of the AbortController so there is a graceful command shutdown. In my PR I have had to modified that to disable the development store preview when the dev command finishes


pt translation with wrong keyword

(line 57)    "login_with_service": "Logar com _service_",
keyword should be with two underscores
(line 57)    "login_with_service": "Logar com __service__",
screenshot with wrong keyword

I saw that this project is not to be edited by hand.
So how can i help to fix this? and fix some typos like described here #4 ? these typos still is in the code!

Fixed in https://github.com/overleaf/translations/commit/4ba4ba21890dc446920e12fed9d7173d08da1d44


Create basic SocketClient PATCH unit tests.

A set of tests is needed to ensure the SocketClient is handling PATCH requests correctly and efficiently.
These tests are required to progress with Issue #31.

Closed as we are now using the existing HttpClientTests class and will not be creating any new tests (unless necessary).


MM-17589 Update "passcode required" help text

The previous help text told the user to go to the "Touch ID & Passcode" section of the settings, even if the device didn't support Touch ID. This fixes that by checking whether or not the phone supports Touch ID.
Ticket Link
https://mattermost.atlassian.net/browse/MM-17589
Checklist

Includes text changes and localization file updates

Device Information
This PR was tested on: iPhone 6, iPad Pro, iPhone 7 Simulator, iPhone X Simulator

There's no option to send the user to those settings directly on iOS. The help text was already a workaround for that


Is there simple way to set timeout for async call?

For some unknown reasons, library I am trying to call will throw some exception internally which cannot be catch outside, in this case it will keeping running (using 99% capacity of CPU) and never return... so I am trying to control this situation by setting a timeout for my async like this:
var handler = test.myCall.async(xxxx, (err, res) =>
    //deal with results
})
setTimeout( () = > {
 //nothing return in 5s, how to kill(handler) ?
}, 5000);
thanks in advance!

You would need to use a child processs and invoke myCall inside that sub-process. This is because there is no way to cancel an async call in-flight.


WIP: Test remove client-go flags from commands that don't use

DON'T MERGE. This is meant to test whether the client-go flags can be removed from commands that don't use them.

Per offline conversation with @anguslees, we're going to merge this today.


WCAG 2.0 A Compliance

We've been using Pickadate for many of our projects but it would be great if it was also WCAG 2.0 A compliant.
We ran the pickadate demo site through the AMP tool to test for WCAG 2.0 A compliance and found a couple errors. Most of them are related to aria-activedescendant, aria-expanded, and aria-labels.
Date
aria-activedescendant used when it is not allowed
Value "true" for aria-activedescendant is not appropriate. It should be the id of a selected descendant. https://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology for more info

aria-expanded used when it is not allowed
Aria-expanded should not be used on input elements. Aria-controls may be more appropriate here. https://www.w3.org/TR/wai-aria/states_and_properties#aria-controls for more info
<input type="text" placeholder="Try me…" class="fieldset__input js__datepicker picker__input" name="" id="P1037699023" readonly="readonly" aria-haspopup="true" aria-expanded="false" aria-readonly="false" aria-owns="P1037699023_root">

ARIA based form control found without aria-label or aria-labelledby or inner text (where applicable)
Previous and Next month doesn't have aria-label

Time
aria-activedescendant used when it is not allowed
Value "true" for aria-activedescendant is not appropriate. It should be the id of a selected descendant. https://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology for more info
aria-expanded used when it is not allowed
Aria-expanded should not be used on input elements. Aria-controls may be more appropriate here. https://www.w3.org/TR/wai-aria/states_and_properties#aria-controls for more info
<input type="text" placeholder="Try me…" class="fieldset__input  picker__input" name="" id="time_demo__translations" readonly="readonly" aria-haspopup="true" aria-expanded="false" aria-readonly="false" aria-owns="time_demo__translations_root">

Is there any update on this issue?

Providing a PR for this issue

@Vishwaas can you add also the fixes for the picker.time.js?

@revdbrink  I made a lot more fixes for pickadate regarding wcag but later I changed to using ember datepicker. I will try to push the changes today. Sorry for the late response


Add a command to setup KubeSphere

case 1
Sometimes we need multiple environments for development and testing purposes. It's hard to memorize the address of those KubeSphere clusters. Even worse, part of those environments might be temporary. Give that, it would be good to have a simple way to set up a remote kubeclt connection locally, open the console of the KubeSphere cluster.
You can consider the following usage:
ks config add --cluster dev --host <IP_ADDRESS>
The above command will get the token of the default serviceAccount, then add it to ~/.kube/config as dev. Secondly, create a configMap to store the address of the cluster. It could be like:
kind: ConfigMap
apiVersion: v1
data:
  externalAddress: http://<IP_ADDRESS>:30880

If you want to open it in your browser, just need to type: ks open dev.

/help


Request: Implement -i (--inode) to include inode numbers

Expected behavior
touch README.rst
ls -i README.rst

53850413 README.rst
busybox ls -i README.rst

53850413 README.rst
lsd -i README.rst

53850413  README.rst
ls -li README.rst

53850413 -rw-r--r-- 1 andy andy 0 Sep  4 15:56 README.rst
busybox ls -li README.rst

53850413 -rw-r--r--    1 andy     andy             0 Sep  4 15:56 README.rst
lsd -li README.rst

53850413 .rw-r--r-- andy andy 0 B Wed Sep  4 15:56:36 2019   README.rst
Actual behavior
-i not implemented.
Both GNU Coreutils and BusyBox support -i to show inode numbers, and Coreutils additionally supports the equivalent --inode. -i should be sufficient, and handy for identifying hard links.

Hi @AndydeCleyre,
This look a great feature indeed. I guess it can be integrated as a block. I don't have time to work on this feature but if you want to make a PR we would be happy to review it.

If it were implemented as a block, would that preclude the following behavior?
lsd -i

57011337   app.rs    57011339   core.rs     57011341   flags.rs  57011343   main.rs  57011354   sort.rs
57011338   color.rs  57011340   display.rs  57011342   icon.rs   57094940   meta

In other words, would we have to use the --long/table view to access it? In this case and in general I prefer keeping behavior close to other ls(-like) implementations.

I don't think it would preclude anything. It would just facilitate the -i integration as is only require to run an ls with the blocks name and inode.
So lsd -i == lsd --blocks inode,name

This is now possible with https://github.com/Peltoche/lsd/pull/296


Duplicate companies being created.

In production, there are extra companies being created causing issues with cla managers accessing the cla corporate console. An example is:

This company was created by the cla manager in v1 4/14 at 00:35:48
The company existed as an Account in Salesforce previously.
At 1:07:34, another entry was created in the database for this company, assigning the SFID to it, with no company acl or manager info, with the note: Created based on SF Organization Service record - signing entity name not set - using organization name:

What is the mechanism for creating this company in EasyCLA? How can we stop the creation of duplicate companies like this?

This is being done through the contributor flow and is working as intended.


Move from less to sass

UIKit 3 beta now supports sass. The only reason less was originally integrated was because of the UIKit requirement, so the project can now be migrated over to sass.

Now that Decipher is adopting Bootstrap 4 as it's standard CSS framework, the logic for this issue has changes. The work should be done in conjunction with #103.

Closed by 0.2.1 release


IDEA: Detect if replit is being used, and use a proxy if so.

Basically what the title above says. I know that you can just use session id login, but that's a lot heftier of a process than a username and password.

[ ] Find a way to check for replit
[ ] Implement the way
[ ] Use a proxy for replit users
[ ] Check the proxy works
[ ] Confirm replit integration works

Interesting idea, I'll consider implementing that

Update: I won't implement a proxy (I don't have time), but if someone else wants to do that they can create a pull request.

Update: I won't implement a proxy (I don't have time), but if someone else wants to do that they can create a pull request.

Thanks.


Update sbt-sonatype to 3.9.6

Updates org.xerial.sbt:sbt-sonatype from 3.8 to 3.9.6.
GitHub Release Notes - Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.xerial.sbt", artifactId = "sbt-sonatype" } ]

labels: sbt-plugin-update

Coverage decreased (-0.5%) to 95.455% when pulling 278d951267c77e8be410fb0e63a0b37e107b45d8 on scala-steward:update/sbt-sonatype-3.9.6 into cc542fa6a0c118677a94867c631cfd3799170ec5 on iheartradio:master.

Superseded by #145.


markdown: parse fenced_code_attributes extension

Pandoc supports this extension: https://pandoc.org/MANUAL.html#extension-fenced_code_attributes

And this:

Recognize them in the lexer. Try to limit the complexity of the regular expression by splitting off parsing of attributes into a separate 'parse' (otherwise we hit automata size limits in ocamllex).
According to
https://quarto.org/docs/authoring/markdown-basics.html#ordering-of-attributes the ordering has to be:

#identifiers
.classes
key-value attributes

For now on output we always normalize to this form (which isn't ideal, but could be improved later):

I initially tried to fully parse the attributes, but I've exceeded the maximum size of the ocamllex automaton, so I kept it simple in this PR (and do some minimal parsing in OCaml later, note that key-value pairs aren't split correctly, but when joined backed together they retain the original value).

(this PR might need some wider testing to check it doesn't break backwards compatibility, is there a larger corpus you'd normally test changes like this on? e.g. the realworldocaml book, anything else?)

Testing on RWO would indeed be a great idea - and checking that the resulting diff doesn't contain surprising results


Set dynamic memory limit in pdfalto_server

This is a fix for #1036
The memory limit for the pdfalto subprocess was only set for batch mode, not for server mode.
This PR pass the memory limit defined in the Grobid configuration file to the pdfalto_server script, which set the ulimit before creating the pdfalto subprocess.
Tested successfully with the java server.
todo: to be tested with Docker.

coverage: 39.98% (+0.003%) from 39.977% when pulling 3de1ca40f90a5a4221b583ba61e0f06de887d9f8 on fix-1036 into bbf1e85632ead9472b77465dd7d2a6fda7b29d43 on master.

Tested successfully with docker too. The memory limit is used by the docker service and a pdfalto subprocess for a large PDF is killed as expected.

@lfoppiano I made the change to the pdfalto_server script for macos too, but I can't test it. Could you check maybe?

I tested on M1, it seems to work by setting 6M as maximum memory for pdfalto.
Does this correspond to the expected behaviour?
Aug 08 09:00:59 falcon docker[26816]: ERROR [2023-08-08 00:00:59,218] org.grobid.core.process.ProcessPdfToXml: pdfalto process finished with error code: 139. [/opt/grobid/grobid-home/pdfalto/lin-64/pdfalto_server, -fullFontName, -noLineNumbers, -noImage, -annotation, -filesLimit, 2000, /opt/grobid/grobid-home/tmp/origin12466301919498765093.pdf, /opt/grobid/grobid-home/tmp/ahxv9U7ABP.lxml, --timeout, 60, --ulimit, 6144]
Aug 08 09:00:59 falcon docker[26816]: ERROR [2023-08-08 00:00:59,218] org.grobid.core.process.ProcessPdfToXml: pdfalto return message:
Aug 08 09:00:59 falcon docker[26816]: ERROR [2023-08-08 00:00:59,219] org.grobid.service.process.GrobidRestProcessFiles: An unexpected exception occurs.
Aug 08 09:00:59 falcon docker[26816]: ! org.grobid.core.exceptions.GrobidException: [BAD_INPUT_DATA] PDF to XML conversion failed with error code: 139
[...]

Does this correspond to the expected behaviour?

Thank you ! yes this is the expected failing exception when subprocess is OOM and killed

I just realised that I did not really test on the M1 macos but on Linux 😅
On the M1 the script was not modified so no PDF could be processed. I fixed it in 2c720dd55344f48edab83f636f9bff640a92fbdc.
However, the ulimit is commented because it fails to set the limit:
WARN  [2023-08-15 01:47:02,132] org.grobid.core.process.ProcessPdfToXml: pdfalto stderr: /Users/lfoppiano/development/projects/grobid/grobid-home/pdfalto/mac_arm-64/pdfalto_server: line 38: ulimit: virtual memory: cannot modify limit: Invalid argument

Ha yes I modified only the old mac ones grobid-home/pdfalto/mac-64/pdfalto_server.
Maybe changing the ulimit on latest macos requires sudo?

I need to investigate more, however, for mac on intel works without issue. Just tested.


Cwebp error message fails

Can not get $uniqueFailCodesBesides127[0] because the array is not reindexed after array_unique() call


Windows Desktop Server Application cant send message to Client

Hi ,
I am using MQTTnet <IP_ADDRESS> version and I want to send message from Server to specific client . Firstly I try "SubscribeAsync" method to send message and when I try this on Unit Test application everything work well , But when I try exactly same things on Windows Form application , Client just dont accept messages
Here is my Server and Client code
Server Code
`
    public static async void CreateServer(Action<MqttConnectionValidatorContext> validation)
    {
        mqttServer = new MqttFactory().CreateMqttServer();

        var optionsBuilder = new MqttServerOptionsBuilder()
        .WithConnectionBacklog(100)
        .WithDefaultEndpointPort(1884);

        if (validation != null)
            optionsBuilder = optionsBuilder.WithConnectionValidator(validation);
        var options = optionsBuilder.Build();
        await mqttServer.StartAsync(options);

    }
    public static void SendMessageToClient(string clientId, string message)
    {
        if (mqttServer == null)
            return;
        mqttServer.SubscribeAsync(clientId, new List<TopicFilter>()
            {
                 new TopicFilter(message,MQTTnet.Protocol.MqttQualityOfServiceLevel.ExactlyOnce)
                 {

                 }
            });
    }

`
Client Code
`
    IMqttClient client;
    public Form1()
    {
        InitializeComponent();
    }
    private void btnConnect_Click(object sender, EventArgs e)
    {
        try
        {
            client = new MqttFactory().CreateMqttClient();

            var clientOptions = new MqttClientOptionsBuilder().WithTcpServer(txtServer.Text.Trim(), 1884).WithClientId(txtClientId.Text.Trim()).Build();

            client.ConnectAsync(clientOptions).GetAwaiter().GetResult();
            client.ApplicationMessageReceived += Client_ApplicationMessageReceived;
            MessageBox.Show("Connected");
        }
        catch(Exception ex)
        {
            MessageBox.Show(ex.Message);
        }

    }
    private void Client_ApplicationMessageReceived(object sender, MqttApplicationMessageReceivedEventArgs e)
    {
        MessageBox.Show("Message= " + e.ApplicationMessage.Topic);
    }

`
Is there any missing?

Hi,
I added await but result is same.
Here is my message send code
    private void btnSend_Click(object sender, EventArgs e)
    {
          MqttServerConfiguration.SendMessageToClient(txtClientId.Text.Trim(), txtMessage.Text.Trim());
     }

message send code is in the server app.
if you want I can publish code to github
Best regards Jack

I will close this issue now due to inactivity, feel free to re-open this issue if you have further questions. Please make sure to re-check this issue with the latest version if you re-open this issue again.


Project Analysis on Thanos

project thanos.docx

@fpetkovski Pretty sure this one can be deleted (and I'm not touching a .docx from GitHub)


114 flatten nested objects

@aybabtme
I fixed the JSONHandler to be able to flatten the arrays(and nested arrays) including some tests


[multistage] fix usage of metadata overrides

custom properties in StageMetadata and
requestMetadata from WorkerRequest are immutable
mutating it during execution causes race-condition in set b/c multiple worker shares the same metadata
thus

create an immutable wrapper around
move the consolidation logic to create a new local map of requestMetadata for each queryRunner call and set it context, never use the customProperties field from StageMetadata again.

Codecov Report

Merging #11587 (e1ed225) into master (3c7cc4f) will decrease coverage by 48.55%.
Report is 23 commits behind head on master.
The diff coverage is 0.00%.

:exclamation: Current head e1ed225 differs from pull request most recent head 87c31b5. Consider uploading reports for the commit 87c31b5 to get more accurate results

@@              Coverage Diff              @@
##             master   #11587       +/-   ##
=============================================
- Coverage     63.04%   14.50%   -48.55%
+ Complexity     1109      201      -908
=============================================
  Files          2320     2326        +6
  Lines        124667   124884      +217
  Branches      19033    19063       +30
=============================================
- Hits          78600    18112    -60488
- Misses        40476   105239    +64763
+ Partials       5591     1533     -4058

Flag
Coverage Δ

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
0.00% <0.00%> (ø)

java-11
14.48% <0.00%> (-48.54%)
:arrow_down:

java-17
14.49% <0.00%> (-48.41%)
:arrow_down:

java-20
14.48% <0.00%> (-48.43%)
:arrow_down:

temurin
14.50% <0.00%> (-48.55%)
:arrow_down:

unittests
14.49% <0.00%> (-48.55%)
:arrow_down:

unittests1
?

unittests2
14.49% <0.00%> (+<0.01%)
:arrow_up:

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

Files Changed
Coverage Δ

...va/org/apache/pinot/query/runtime/QueryRunner.java
0.00% <0.00%> (-77.28%)
:arrow_down:

...inot/query/runtime/operator/AggregateOperator.java
0.00% <0.00%> (-94.45%)
:arrow_down:

...pinot/query/runtime/operator/HashJoinOperator.java
0.00% <0.00%> (-92.99%)
:arrow_down:

...ot/query/runtime/plan/OpChainExecutionContext.java
0.00% <0.00%> (-96.16%)
:arrow_down:

...apache/pinot/query/runtime/plan/StageMetadata.java
0.00% <0.00%> (-76.00%)
:arrow_down:

... and 1503 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Codecov Report

Merging #11587 (e1ed225) into master (3c7cc4f) will decrease coverage by 48.55%.
Report is 23 commits behind head on master.
The diff coverage is 0.00%.

:exclamation: Current head e1ed225 differs from pull request most recent head 87c31b5. Consider uploading reports for the commit 87c31b5 to get more accurate results

@@              Coverage Diff              @@
##             master   #11587       +/-   ##
=============================================
- Coverage     63.04%   14.50%   -48.55%
+ Complexity     1109      201      -908
=============================================
  Files          2320     2326        +6
  Lines        124667   124884      +217
  Branches      19033    19063       +30
=============================================
- Hits          78600    18112    -60488
- Misses        40476   105239    +64763
+ Partials       5591     1533     -4058

Flag
Coverage Δ

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
0.00% <0.00%> (ø)

java-11
14.48% <0.00%> (-48.54%)
:arrow_down:

java-17
14.49% <0.00%> (-48.41%)
:arrow_down:

java-20
14.48% <0.00%> (-48.43%)
:arrow_down:

temurin
14.50% <0.00%> (-48.55%)
:arrow_down:

unittests
14.49% <0.00%> (-48.55%)
:arrow_down:

unittests1
?

unittests2
14.49% <0.00%> (+<0.01%)
:arrow_up:

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

Files Changed
Coverage Δ

...va/org/apache/pinot/query/runtime/QueryRunner.java
0.00% <0.00%> (-77.28%)
:arrow_down:

...inot/query/runtime/operator/AggregateOperator.java
0.00% <0.00%> (-94.45%)
:arrow_down:

...pinot/query/runtime/operator/HashJoinOperator.java
0.00% <0.00%> (-92.99%)
:arrow_down:

...ot/query/runtime/plan/OpChainExecutionContext.java
0.00% <0.00%> (-96.16%)
:arrow_down:

...apache/pinot/query/runtime/plan/StageMetadata.java
0.00% <0.00%> (-76.00%)
:arrow_down:

... and 1503 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


SteamVR error when make launch

I am running carla 0.9.7 , ubuntu 18.04 , UE 4.22 , using VMware.
I build carla with this URL's step.
https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
But when I run make launch , I got error message bellow.
Plugin 'steamVR' failed to load because module 'steamVR' could not be found. Please ensure the plugin is properly installed, otherwise consider disabling the plugin for this project.
This question is same for my situation .
https://github.com/carla-simulator/carla/issues/1213
And, I also check ".uproject" . I see both of them's setting is false.
So, I don't know how to disabling the plugin.
Does anyone help me?

were you trying to launch the UE4 editor from the Binaries sub folder of the Unreal Folder ?? if yes, you should not run it that way, in the Carla folder, run "make launch-only"  or "make launch" to build before starting the Unreal editor, make sure you have imported the Unreal Editor path.


New version: IJulia v1.27.0

Registering package: IJulia
Repository: https://github.com/JuliaLang/IJulia.jl
Created by: @stevengj
Version: v1.27.0
Commit: 0db1fa2c6b3f04d43a18830c631a1e46851908b6
Reviewed by: @stevengj
Reference: https://github.com/JuliaLang/IJulia.jl/commit/0db1fa2c6b3f04d43a18830c631a1e46851908b6#commitcomment-147918415
Description: Julia kernel for Jupyter

Close this, I will submit a 1.26 release


purview starter kit for linux please

for those of us who'd like to learn purview but are working from linux/bash,
Follow these steps to set up the starter kit client software on your Windows machine:

Download the starter kit, and extract its contents to the location of your choice.

On your computer, enter PowerShell in the search box on the Windows taskbar. In the search list, right-click Windows PowerShell, and then select Run as administrator.

Would've been great if linux was a first class citizen in the azure universe :-)

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

ID: cd2039cb-fc85-a189-1938-57d102a09b2f
Version Independent ID: 4bc83b4b-afcb-8521-a882-628ce151b093
Content: Tutorial: Scan data with Azure Purview (preview) - Azure Purview
Content Source: articles/purview/tutorial-scan-data.md
Service: purview
Sub-service: purview-data-catalog
GitHub Login: @viseshag
Microsoft Alias: viseshag

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@viseshag Hello, could you please take a look on this issue and update the document if necessary? Thanks.

At this point, we won't be offering a Linux version. Please vote in the Uservoice community for this feature request.
#please-close


[Request] Add Glimpse

Open source image editor based on the GNU Image Manipulation Program.
Repository and website

This package already exists. (extras/glimpse)


Aggregate styles

Just combined them in the cases where inlining the styles didn't make things too frighteningly long. Could probably do this to everything, since it makes it easier to cross-reference styles with their classes in the JS, but... eh, we'll see.

(Realized that this is a non-behavioural change, so really doesn't need much review.)


shamefully-hoist breaks package isolation in a monorepo

Describe the bug
wxt adds shamefully-hoist=true to an .npmrc file in the folder of the wxt extension. However, this setting changes hoisting for the entire monorepo. After running pnpm install, pnpm shows the following warning:
Scope: all 15 workspace projects
✔ The modules directory at "/Users/robert/code/ditto/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) · true

Now the node_modules at the root of the monorepo has all modules from all packages in the monorepo hoisted. This breaks one of the main benefits of using pnpm.
To Reproduce
Steps to reproduce the behavior:

mkdir bug-repro && cd bug-repro
npm create svelte@latest my-app
pnpx wxt@latest init my-ext
Create a pnpm-workspace.yaml with my-app and my-ext in them
npm install

Expected behavior
node_modules in root shouldn't have modules from my-app and my-ext
Environment
  System:
    OS: macOS 14.1.2
    CPU: (10) arm64 Apple M1 Max
    Memory: 15.90 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
    pnpm: 8.12.0 - ~/.nvm/versions/node/v18.17.1/bin/pnpm
    bun: 1.0.15 - ~/.bun/bin/bun
  Browsers:
    Chrome: 120.0.6099.109
    Safari: 17.1.2
  npmPackages:
    wxt: ^0.12.0 => 0.12.0

Additional context
I love wxt. It's incredible!

I also use WXT in a monorepo, but we have an electron app that requires shamefully-hoist=true, so this isn't something I've thought about much. I created this project based off Nuxt, which, at the time, also required setting this flag. Now though, it doesn't seem like the case (https://github.com/nuxt/nuxt/issues/14146).
So I can look into fixing this in WXT as well. Right now, there are 2 dependencies that prevent it from working:

webextension-polyfill
@webext-core/match-patterns

Unfortunately, I'm not an expert on PNPM and module resolution, so I don't know why only these two packages cause problems.
But if you list those two dependencies in your package.json, you can remove the .npmrc file. You can see this in a non-monorepo project:
$ pnpx wxt@latest init wxt-without-hoisting
$ cd wxt-without-hoisting
$ rm .npmrc
$ pnpm i
$ pnpm build
...
[vite]: Rollup failed to resolve import "webextension-polyfill" from "virtual:wxt-background?/Users/aklinker1/Development/local/wxt-without-hoisting/entrypoints/background.ts".
...

$ pnpm i webextension-polyfill
$ pnpm build
...
[vite]: Rollup failed to resolve import "@webext-core/match-patterns" from "virtual:wxt-background?/Users/aklinker1/Development/local/wxt-without-hoisting/entrypoints/background.ts".
...

$ pnpm i @webext-core/match-patterns
$ pnpm build
...
✔ Built extension

Same errors for dev mode.

So I don't really know where to start with this...
Nuxt solved their problems by listing vue and vue-router in their package.json. I will probably do this with webextension-polyfill, but I don't know why @webext-core/match-patterns is causing any problems...

Here's an issue for vite that talks more about it: https://github.com/vitejs/vite/issues/324
And here's a issue that this was fixed in: https://github.com/preactjs/prefresh/issues/75
Both talk about talk about packages importing a subdependency not listed in the library's package.json, but I do list @webext-core/match-patterns inside WXT's package.json, and it has 0 dependencies, so it's not importing any sub-dependencies.

Actually, I know what the problem is now.
[vite]: Rollup failed to resolve import "@webext-core/match-patterns" from "virtual:wxt-background?/Users/aklinker1/Development/local/wxt-without-hoisting/entrypoints/background.ts".

The error says it's coming from a virtual input. These inputs are shipped with WXT, but are not bundled until build time. This means they're effectively apart of your project, not WXT. That means they can't import any package not listed in your project's package.json.
Solution: Export any utilities from WXT and import them from WXT in these virtual entrypoints instead of from the 3rd party package directly.
This may also work for webextension-polyfill, and we might not have to add it to the package.json of the templates. That would be ideal, because eventuall, I want to remove the polyfill. If it's internal to WXT, I could remove it at anytime without making any breaking changes.

@rsweeney21 Can you try out v0.12.2-alpha2? I've got it working locally for some test projects.
pnpm i -D<EMAIL_ADDRESS>

@aklinker1 I encountered this issue today using the package manager pnpm and monorepo tool turbo. I installed 0.12.2-alpha2 and it worked for me.

Ok, I'll merge and release this today then!

Released in v0.12.2

@tesths Can you open a new issue? Your problem is unrelated to this issue


Inputs no longer autofocus after input is submitted.

BUG=https://github.com/flutter/flutter/issues/4905

Not sure it makes sense to clear the autofocus, but without it, we would always refocus the Input immediately after submitting.

This doesn't seem like the right solution.  @Hixie might have better ideas what to do here.

I don't really understand what this is trying to do (I don't really understand the bug description either).

When you dismiss the keyboard while focused on the Input control in the Stocks app, the Input does not appear to lose focus. The underline highlight on the Input remains. That seems like a bug.
This appears to be caused by the combination of 2 things:

The Input widget is unfocused when the keyboard is dismissed. However, a rebuild is not usually triggered, so there's no opportunity to update the focus highlight.
Even if we trigger a rebuild when dismissing the keyboard, if autofocus is true, we just end up re-focusing the same Input. So we need to rebuild without autofocusing somehow.

I thought it might be reasonable to only autofocus the Input the first time it is displayed.

Adam and I discussed this and came to the following conclusions:
Requiring that the input's owner manage this is too onerous. Instead, we should give the Focus widget a constructor argument that decides whether or not autofocus is enabled. When it's enabled, everything works like today. When it's not, autofocus doesn't do anything. The ModalScope widget (which owns the Focus widget) would then set this bit the first time a route is built, and unset it for all subsequent frames (it would register a post-frame callback the first time to ensure it was built the second time. In practice it's already built twice anyway by the heroes code to toggle the offstage bit in the same way).

Is this PR still active?

Nope


Improved grid intersection calculation in validator

Codecov Report

Merging #30 into master will decrease coverage by 0.8%.
The diff coverage is 3.44%.

@@            Coverage Diff            @@
##           master     #30      +/-   ##
=========================================
- Coverage    56.2%   55.4%   -0.81%
=========================================
  Files          33      33
  Lines        1370    1388      +18
=========================================
- Hits          770     769       -1
- Misses        600     619      +19

Impacted Files
Coverage Δ

pycomlink/spatial/interpolator.py
94.35% <ø> (-0.05%)
:arrow_down:

pycomlink/validation/validator.py
20.17% <3.44%> (-4.04%)
: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 af009a4...d731a88. Read the comment docs.


Powertoys block Win key in GTA5

Microsoft PowerToys version
0.70.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
My powertoys is start with the windows.
In GTA5, the Windows key has been blocked when focus on the game.
The Windows key has been free when not focus on the game.
Then I exit the powertoy, the Windows key is free when focus on the game.
Then I reopen the powertoy, the Windows key is blocked again when focus on the game.
✔ Expected Behavior
The Windows key has been free when focus on the game.
❌ Actual Behavior
The Windows key has been blocked when focus on the game.
Other Software
Grand Theft Auto V Steam Version

This is not a BUG that can be reproduced stably, it seems to have a certain degree of randomness, and I have not been able to determine what affects whether it appears or not.

/reportbug

Just uploaded the debug.zip, and this bug seems to have occurred with the system started, and it disappeared after I restarted the powertoys a few times

Not able to repro this, going to close. Let us know if you see this again!


Add Europe region support

Europe region accounts use separate API/WS endpoint
Added new config key region (with default='us', current configs should work as-is)
Added DR-HTF002S support

Hi, I just made a new beta version that uses the HA Config UX flow.  It also auto-detects region now.  Should try to auth with US, and detect that you're in EU, then redo it.  Let me know if the beta version works for you?

@JeffSteinbok tested 0.1.0b1, working as expected including UI config flow. Thanks.