[Android] [Localization] “.” (Dot) is shown instead of “,” (Comma) for payment request decimal amount on “Payment Request” section from “Wallet” tab when app language is “Espanol (America Latina)”.

App version: Zero - sync  build v1.5.0, Play store build v1.5.0
Repro on: Samsung Galaxy S6 (7.0), Samsung Galaxy S7 (8.0.0)
Testing Account:<PHONE_NUMBER>/Backup Kay
Pre-condition:
Payment request decimal amount should show on “Payment Request” section from “Wallet” tab
App language should be “Espanol (America Latina)”.
Repro Steps:

Launch the app.
Make sure Decimal amount is shown in Payment request section.
Observe.

Investigation:  Issue also repro for “Exchange Fee” amount on “Review Exchange” page.
Current Behavior: “.” (Dot) is shown instead of “,” (Comma) for payment request decimal amount
Expected Behavior: “,” (Comma) should show for every decimal amount if app language is “Espanol (America Latina)”.
Attachment: Android_DotIsShown.png

@nityas  I have verified this issue on  Android internal build v1.1.0 & iOS test flight build v1.1.0(20) and found issue is still repro
(Dot) is shown instead of “,” (Comma) for payment request decimal amount on “Payment Request” section from “Wallet” tab when app language is “Espanol (America Latina)
Device: iPhone 11 (14 beta 6), Samsung Galaxy A70(9.0)
Attachment: DotISShown.PNG

This is the expected behavior now. Comma / Dot depends on the user locale settings. And not the language selection.


dbab.adblock.conf is wrong.

I installed dbab on raspberry pi 4 using apt-get install dbab. The dbab.adblock.conf file is wrong and only has the following content:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>302 Found</title>

Found

The document has moved here.

<address>Apache/2.4.29 (Ubuntu) Server at pgl.yoyo.org Port 80</address>

There's a bug in some version of dbab. I've solved the problem by modifying the file /usr/sbin/dbab-get-list according to the following patch:
diff -u  /usr/sbin/dbab-get-list.old  /usr/sbin/dbab-get-list
--- /usr/sbin/dbab-get-list.old.fixed	2020-02-13 11:39:35.858206630 +0100
+++ /usr/sbin/dbab-get-list	2019-12-28 03:31:28.000000000 +0100
@@ -3,7 +3,7 @@
 ##-----------------------------------------------------------------------
 ## Porgram: dbab-get-list
 ## Purpose: Get dnsmasq blocking list from pgl.yoyo.org
-## Authors: Tong Sun (c) 2013
+## Authors: Tong Sun (c) 2013-2019
 ## License: BSD license
 ##-----------------------------------------------------------------------

@@ -14,7 +14,9 @@
 }

 dbabsvr_addr=`cat /etc/dbab/dbab.addr`
+dbab_conf=/etc/dnsmasq.d/dbab-map.adblock.conf

 # Down the DNSmasq formatted ad block list
-curl "https://pgl.yoyo.org/adservers/serverlist.php?hostformat=dnsmasq&showintro=0&mimetype=plaintext" | grep -vFf /etc/dbab/dbab.list- | sed "s/127\.0\.0\.1/$dbabsvr_addr/" > /etc/dnsmasq.d/dbab.adblock.conf
-echo File /etc/dnsmasq.d/dbab.adblock.conf updated.
+curl "https://pgl.yoyo.org/adservers/serverlist.php?hostformat=dnsmasq&showintro=0&mimetype=plaintext" | grep -vFf /etc/dbab/dbab.list- | sed "s/127\.0\.0\.1/$dbabsvr_addr/" > $dbab_conf
+echo File $dbab_conf updated.

Thanks a lot for helping out @pms967,
I'll see if a new version need to be packed for Debian...

Dup of #2. Closing.
@dantesun please check existing issues next time.


TO CATALOG button after creating new component does not work

After the change to the new routing model the button on the pop up after creating a new component does not redirect anywhere.
Expected Behavior
On clic it should take you to the new component catalog page

Current Behavior
TO CATALOG link does nothing.

Possible Solution
Update routing to point to backstage/catalog/Component/

Steps to Reproduce
Try clicking on the TO CATALOG button.

Start the app on master.
Register an existing service (http://localhost:3000/register-component)
Try clicking on the TO CATALOG button

Your Environment

NodeJS Version (v12): v12.18.2
Operating System and Version (e.g. Ubuntu 14.04): Ubuntu 20.04
Browser Information: Chrome Version 85.0.4183.83 (Official Build) (64-bit)

Thanks for reporting @ebarriosjr, I'm going to take a look 😉


Paddy 2 vs Anima Toolkit

Hey,
What a pain… hat a pain… how can it be? do you aim at compete with Anima autolayout?!
Heck! how can we work by now? we do need bith of the plugin. Our design system has numerous symbols using paddy and autolayout.
We had big issues with Paddy 1 earlier this year and now, just being happy to welcome back paddy 2, it messes once again!
We CAN'T work this way. I'm in worldwide company. We CAN't afford wasting time because of messy plugins.
Think about it.
best,

What is the issue? .6 just came out a couple hours ago which had some fixes.

This is a free plugin someone makes in his free time.
Think about it.

The issue? guess you know it. :-)
When you activate the last paddy version here is what you get:
"Unfortunately, Paddy doesn't play nice with Anima Toolkit; so you're going to have to make the difficult choice of using one over the other..."
Regarding the big evolution of paddy and the common functions with autolayout, I don't think it's preposturous to think you might try to challenge Anima et get the first place…
But if it is true, it's quite a hard way to behave with designers…

Oh wow, that is really disrespectful. The issue is you have installed a beta version and don't know what that means. It means it's likely you'll experience bugs. Maybe you shouldn't rely on beta software for your worldwide company.
If you find yourself wasting too much time messing around with messy plugins let me give you a hint: invest that time in creating your own.
I'd say this issue can be closed.

I think my point is still valid. Don't rely that much on beta plugins for your workflow (cause the chance is big you'll run into issues).
A beta version is helpful for developers so that others can help find and file issues. Your 'issue' sounds more like a complaint, which is invalid since this plugin is free (!) and is still in beta.
If you describe the issues you're having, David might be able to fix it and release a stable version sooner.

@stigmates Are you willing to give hundreds of hours of your time for free to your clients? If not, then why are you expecting perfection from someone who is giving hundreds of hours of his valuable time to you?
Paddy 2 is in beta, and he clearly states that it might have bugs. If you want better quality in Paddy 2, then consider donating generously to its development. If you find it isn't stable enough for your incredibly important worldwide design company, then don't use it. No one is forcing you to. You didn't pay anything for it. Is it fair for you to attack him like this?
David is not trying to compete with Anima, he's just doing what interests him. What he said is exactly right: "Unfortunately, Paddy doesn't play nice with Anima Toolkit." Of course they don't play nice together, they are both trying to do the same thing to layers, which is bound to cause problems. So what he said is a simple statement of fact, not of competition. Maybe you think that way, but David doesn't. He's just having fun... or perhaps he was, until now.

@stigmates I support what @aparajita said above. And to add more to that …
This is a labor of love from David. I do not believe you paid him anything for his plugin. BE POLITE and ask for help – DO NOT DEMAND. Even if you paid for something, BE POLITE. You're not going to get far by being rude. This is in beta and we are all working together with David to help iron out the bugs. If that's too much work for you, stop using it, and stop being rude!

Thanks all for the responses and love in response. And thank you for taking your time to clarify for @stigmates.
I still think I might be able to shed a bit of light here, and offer a bit more clarity and transparency to everyone regarding 'Anima vs Paddy 2'. Bare with me as I try to provide more information on the matter...

Messy/buggy plugin?
@stigmates Firstly in response to; 'We CAN'T work this way. I'm in worldwide company. We CAN't afford wasting time because of messy plugins.'
Whilst I do understand your frustration, I have clearly stated that this is a Beta plugin and "Warning: Please use the Beta version at your own risk. I don't want be responsible for possibly 'ruining' your very important Sketch document." So whilst I appreciate you giving Paddy 2 a go; I would not advise integrating it with your projects within your 'worldwide company'... yet. I am in the process of trying to iron out these bugs; hence why it is in beta.
Competing with Anima Toolkit?
Whilst the question wasn't asked in the most polite way; it is a very valid point. Let me answer you...
Why doesn't Paddy 2 work with Anima?
In order to integrate with Sketch the way Paddy 2 does, it uses some methods of 'swizzling', which allows me to hook in some code to specific actions that Sketch uses internally. I do this in a way that shouldn't affect other plugins...
Anima hooks into internal actions too via a framework called Aspects. Using this framework makes it much easier for them, and gives a higher level of control — which makes perfect sense as to why the'd use it. Unfortunately, since they use Aspects, it doesn't allow other plugins to be able to swizzle the same actions they do... meaning Paddy 2 wouldn't be able to be automated or function in some cases when working around this constraint.
I got in contact with the developers of Anima to see if it was at all possible for them to move off the Aspects framework, or if they knew a way that I could work with it. Which was a massive ask — and completely understandably they responding saying that after investigation, they aren't able to move off the framework.
I have spent numerous hours & hours trying to work around this limitation to no avail. :(
What's my approach?
Since it is completely unavoidable that the 2 plugins cannot work together, there's a couple of options I have here...

I could remove all the functionality that integrates deeply into Sketch to work around the constraints, creating a much less valuable experience, if not unusable.
I could just give up... given your philosophy @stigmates that you wouldn't release a plugin like this with such a huge limitation to professionals — then that would be the only option.
Try and build out as much functionality as I can to fill the gap that not using Anima may have on users. I know a lot of people use Anima purely for Stack Groups; and their ability to stack content even within a symbol instance... so I am going to make sure that functionality is built out in Paddy 2.

What's next?
There's a couple of things I still aim to do to make the transition from Anima to Paddy 2 for users easier, if they make that decision.

Allow stack groups to be rendered dynamically within a symbol instance — whilst very tricky, this is a key differentiator for Anima's stack groups right now. But rest assured, that is coming for Paddy 2.
Create an action to convert existing Anima Stack groups to Paddy Stack groups; which will hopefully make that transition easier

Conclusion
The fact that I have not allowed them to work together is not a choice! I spent ages trying to make it happen... it's simply unavoidable.
Using Paddy 2 is optional. Whilst not ideal, users are going to have to make the difficult choice of using one plugin over the other. Paddy 2 will not in any way be able to replace Anima Toolkit overall; but I am hoping that it will live up to the task of replacing Stack Groups.
It doesn't look like this is a bug I will be able to work around any time soon... if anyone knows a way, please let me know.
Thanks all for your understanding.

TL;DR

Using Paddy 2 is optional
This is not a choice; it is a technical constraint that it appears I won't be able to work around
I've tried and tried to work fix it and reached out to Anima developers – but no fix seems available
I will do all I can to make the transition for people who rely on Anima Stack Groups easier

@DWilliames Thank you for your response and explanation. I understand the choices you have to make. Working with a everyday evolving tool (Sketch) is quite a new way to do for designers. But not only; it's concerning techs and industry in a wider way. It's cool but sometimes uncomfortable. And releasing unfinished device or software (MVPs, but sometimes not so viable…) I think it is a real issue of contemporary way of producing.
Sometimes it's hard to rely on constant moving tools to build a lasting solution (design system or whatever). I already explained why I chose to go with paddy 2 whilst it's beta. I didn't and wouldn't build the whole library with it of course. But key symbols have been designed with previous versions… and it was a time saviour (sometimes not…).
I was disappointed because paddy and Anima were complementary and my team and I were linked to the both plugins. We had numerous troubles to deal with (craft issues, zeplin exports, sketch updates…) and now we have to chosse between the bothn plugins… 'la goutte d'eau qui fait déborder la vase' (in french).
Typing instead of talking often turns terms harsher than they really are, especially when you write in a foreign language. Maybe several users had the same thoughts and reaction, but they didn't tell.
Let's close this debate and please accept my apologies if I hurt you.

Thanks for understanding.
It’s tough with so much fluidity with design tools and plugins right now. Stability and compatibility is very sought after, I understand that.
I definitely don’t see this as a debate; but more of an opportunity for me to have open and honest dialogue.
I feel that perhaps ‘Beta’ may have been too generous a term for ‘Paddy 2’ — in reality it’s more of an ‘Alpha release’ or simply a ‘tech preview’. For me, I’ve always struggled to complete projects as I have a constant urge for it to be ‘perfect’ before showing others... so this was a big step for me to put Paddy 2 out there in the open as I work through it, in its infancy. And letting everyone come on the journey with me. Perhaps I should have framed the context a bit better so that others are also not as frustrated with a ‘buggy’ or ‘unstable’ plugin.
I can without a doubt say that the support from everyone has been incredible and definitely helped me push forward on this project. I gave it a break for a couple of weeks; but now I’m back on it, pushing full steam ahead. 🙌
Thanks everyone for your patience and understanding as I try make this thing better. 👌🤗❤

I think this is one of the most important discussions as the future of the Paddy 2 is at stake as a successful plugin. There have been numerous projects (including the native resizing behavior of Sketch) that address flexible layout and layout constraints. To this day none of the solutions provides a comprehensive 100% cover of all the layout cases we face. It is impossible to build a button that autoresizes just like that, which is extremely frustrating for UI work.
I don't really need the additional functionality bundled with Anima's auto layout (HTML export, timeline) as I really would like to have a complex layout constraints system that does only that, and works well with Sketch. I hope that at some point Bohemian would open up the system to support auto layout on a new level that would make working with higher abstraction elements reality (I think of them as components - buttons, input fields, repeater grids, etc.). This is what we face as UI designers that deal with multiple screen resolutions and devices.
So the question for Paddy 2 is really - where to? Should Paddy 2 become the ultimate auto-layout engine, or just a complimentary plugin? I would firmly prefer to have a single solution! Hope @DWilliames really succeeds in this very hard undertaking!

Well, guys, let's talk straight: this kind of functionality should be integrated natively by Sketch because nowadays is kinda mandatory for people working on UI like us. Bohemian should seriously think about this... Or just hiring @DWilliames 😉
By the way, @DWilliames thanks for all the hard work ❤Can't wait to use Paddy 2!


Add hyperlink to DeletionPolicy

This PR added the hyperlink for delete section to the DeletionPolicy under the Volume Snapshot Classes.
Fixes #28728

/sig storage

hi @saad-ali @xing-yang
PTAL!

/retitle Add hyperlink to DeletionPolicy

/lgtm

/assign @divya-mohan0209
PTAL!

@xing-yang @divya-mohan0209
could you please take a look so that it will merge?


Terminology change for Areas Surrounded

Change the term for "area surrounded by SLR Planning Area". Instead, could be called isolated areas, islands, isolated high points, cutoff areas / locations. Let's think about terminology.

Our conversations are leading us to:

"impacted by"

1 hazard, 2 hazards, 3 hazards

"surrounded by"

for the new legend of terms

Explanation for Pink Areas - specify that they will be islands

We've changed the cartography to striped, for these areas, and we are now using "surrounded by", so closing this issue


Update readme examples

👋 I've taken a pass through the readme to update the examples to be consistent with the tutorial series. This includes no longer instantiating the plugins:

Note: You may see examples that use new funnel() as a way to create an instance of a plugin, however this is a practice that the Broccoli.js team are trying to move away from, with the intention being that Broccoli is like a functional programming language, where the input of one function is the output of another, to build up a "tree" structure.

Related https://github.com/broccolijs/broccoli-funnel/pull/18

Thank you!


bump version

you might make dependabot to track latest updates of windicss

I don't use Windi CSS so I am ending support for this project.
After the svelte-add rewrite, someone who can be trusted to set it up correctly and maintain it can contribute it to the svelte-add repository.


How secure is having an 8-character AuthToken.token_key?

I notice the AuthToken.token_key is only 8 characters long which is significantly shorter than something like DRF's own TokenAuthentication.
Wouldn't this make it significantly easier to brute-force a user account?

token_key is not the actual token, it’s a shortened version that can be used to filter out matching potential token before actually matching them against the digest.
See https://github.com/James1345/django-rest-knox/blob/3a1bc584f9691f4bc19d8a04a98c68c293be9ca6/knox/auth.py#L64

@johnraz I might be misunderstanding something here – I understand that the token_key is a shortened version of the digest, but since the token_key is what the client provides, what prevents an attacker from generating random 8-char long auth tokens and passing them in as bearer tokens until they get a right one?

The client provides the full token which is shortened and used to filter out records in the database to get back the AuthToken objects matching the shortened token_key field.
We then loop over all those objects and compare their stored digest value against the digest value of the token provided by the client.
If the client only provide a shortened token and not the full token, it will never match the digest.


[APIM-4.0.0][Improvement] - Mention the API revision creation as the mandatory step in the document

Description:
In wso2am-4.0.0, adding API revision under deployment UI is mandatory. If not, the API will not be published in the gateway and cannot invoke the API calls. The following issues will not happen if the "Create and Publish" button is clicked during the API creation process in the publisher portal. But if the "Create" button is clicked, then the revision APIs will not be created. Unless a revision is created for an API it will not be published via the gateway nor will be able to invoke the API calls. It will result in a "Bad Request". Therefore, if the API is created and published separately (Create button -> Publish button) the API revision should be added manually in the "Deployment" UI.
Case 1:
When the sample endpoint(HTTP - http://run.mocky.io/v2/5185415ba171ea3a00704eed) in the doc [1] is used in a newly created REST API in the publisher portal, the Bad Request is sent as the response.
Request
curl -X GET "http://localhost:9443/restAPI/1.0.0" -H "accept: */*" -H "Authorization: Bearer eyJ4NXQiOiJNell4TW1Ga09HWXdNV0kwWldObU5EY3hOR1l3WW1NNFpUQTNNV0kyTkRBelpHUXpOR00wWkdSbE5qSmtPREZrWkRSaU9URmtNV0ZoTXpVMlpHVmxOZyIsImtpZCI6Ik16WXhNbUZrT0dZd01XSTBaV05tTkRjeE5HWXdZbU00WlRBM01XSTJOREF6WkdRek5HTTBaR1JsTmpKa09ERmtaRFJpT1RGa01XRmhNelUyWkdWbE5nX1JTMjU2IiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiJhZG1pbiIsImF1dCI6IkFQUExJQ0FUSU9OIiwiYXVkIjoiZUFwa01zMENvYlpSeEFnd1JaQTJublU1ZmVvYSIsIm5iZiI6MTYxOTA4ODY4NCwiYXpwIjoiZUFwa01zMENvYlpSeEFnd1JaQTJublU1ZmVvYSIsInNjb3BlIjoiZGVmYXVsdCIsImlzcyI6Imh0dHBzOlwvXC9sb2NhbGhvc3Q6OTQ0M1wvb2F1dGgyXC90b2tlbiIsImV4cCI6MTYxOTA5MjI4NCwiaWF0IjoxNjE5MDg4Njg0LCJqdGkiOiIzOWFkZjE1Yy1kOWEyLTQzY2MtYjg3Zi05NzIxMzBlYjllNzEifQ.TIsbZAJ_SOtGOTkLb7oBhzdDBk2lWzkKkJl9a1ODPLRTyXYkhDOj7aGGmJ1Zf7fmafnEzQmBGmv5sm-tNgyCn-f5w5w832wW_cvul8Bx5UrwEDZUMkfY3sGPBjevxl5sb736siDv3UIChs5Yo8DVypl6MSa3sL5zp24zuXglKxl1e0aXTPdRCyCPdlMHB4zTHjBOuwq2XPE-2vUAx1D0-RoJa8kB5BEFzF9uUdALqEWwZUmqHPejvyslvAAgyC8JFmkgjKATMR9IMM_etxDbAgr9kyIFlHpjBVb2I8CeAftJiUqLV-Qd8X6RT-TpLyQ7J60SUb1Yyg-cDhkHSdIJhw" -k

Response
Bad Request
This combination of host and port requires TLS.

Case 2:
The servers dropdown in devportal is displayed as http:///hello/1.0.0.

Solution:
Add a revision under the "Deployment" UI in the publisher portal for the API to get published via the gateway.
[1] https://apim.docs.wso2.com/en/4.0.0/get-started/quick-start-guide/quick-start-guide/
Affected Product Version:
wso2am-4.0.0-RC

Update the revision content with https://github.com/wso2/docs-apim/pull/3766. Closing the issue as the PR is merged.


gilescope: retain at Rank 1

Please find my Polkadot contributions for this season attached.

Hello there!
We are testing a new procedure for submitting evidences on-chain and publishing evidence-related referenda via Subsquare.
So, we ask you to do the following:

Finalise the PR with your evidence based on reviewers’ comments (if any)
Copy/paste your evidence report and submit it on this page.
Copy/paste the (IPFS) link to your evidence as a comment on this PR.

Below is a step-by-step guide for this procedure.

Thanks!

@anaelleltd https://collectives.subsquare.io/ doesn't seem to support parity signer/parity vault which is a shame. In fact the parity signer extension seems unmaintained with no apparent replacement? I don't see the polkadot-js extension being able to link to a parity signer account, only ledger, but ledger you can't import a private seed to. How do others do this or do they not use hard wallets? Maybe the new polkadot ledger app will improve the situation?

@anaelleltd https://collectives.subsquare.io/ doesn't seem to support parity signer/parity vault which is a shame. In fact the parity signer extension seems unmaintained with no apparent replacement?

Hello gilescope.
AFAIK, the Polkadot Vault (formerly Parity signer) is now maintained by Novasama Tech (the team behind Nova wallet): https://github.com/novasamatech/parity-signer . You can look into the repo and see what they suggest re: support for ecosystem UIs.

I don't see the polkadot-js extension being able to link to a parity signer account, only ledger, but ledger you can't import a private seed to. How do others do this or do they not use hard wallets? Maybe the new polkadot ledger app will improve the situation?

Talisman, Nova wallet, Subwallet, and many others (see: https://wiki.polkadot.network/docs/wallets-index) have integrated Ledger accounts, without requiring to import seed phrases. So, you could connect to Subsquare using your Ledger account once it is imported into any of the above wallet.
On another note, I have seen that you are not imported into the Fellowship core, so your retention evidence is not due yet.


Back button not working

started using the most recent .exe and noticed that the tab key/back button weren't working.

Do you know if this was working before?  The last build and newest don't work for me.

It thought It worked on the last one. I still have the zip folder from the last one so I'll check on that tonight.

I don't remember it ever worked, haha.  I took a look at the code and this problem might be fairly difficult to fix.

just tried the last build and I can confirm it doesn't work there either.

Fixed it and I switched the back button to 'B' instead of Tab as a workaround for another issue.


Wrong pull request count in a single repo

Gitea version (or commit ref): 1.7.2
Git version:
Operating system: CentOS 7
Database (use [x]):

[X] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

Description
I have a single repository which displays a wrong PR count. If no PR is opened, it displays -1, if one PR is opened it displays 0 and so on. All other repos work fine. If this is not a bug, how to fix this by hand?
Screenshots

Not solved

update pr count in repositories table in sql

@lafriks: I'll give it a try

I had this happen with a user today. The URL is  https://git.door43.org/unfoldingWord/en_ugg/pulls/95 showing a -1 for open Pull Requests, and this issue is the culprit, where it somehow closed twice. From the user:

I received an error message (500?) when I merged a change. It did not bringing up the merged successful page and the "Do you want to delete the branch" choice.
That said, it did merge the change I was making.   I then went in and manually deleted the branch I merged into master.   But there appears to be a problem with the merge procedure.   I also note that there is a negative 1 pull request.  This may also be part of the problem.

From the gitea.log:

2019/05/30 13:49:49 [...routers/repo/pull.go:943 CompareAndPullRequestPost()] [E] NewPullRequest: newIssue: Error 1062: Duplicate entry '28434-95' for key 'UQE_issue_repo_index'

Maybe tries to insert rather than update?

@richmahn you issue should have been fixed by my PR https://github.com/go-gitea/gitea/pull/6973 , but it's not back ported to v1.8
@xoxys I think this maybe caused by merging some pull request failed and panic.

Linked PR is merged, closing this ticket.
Please re-open if needed (after updating to latest Gitea)


"where" clause with just a column name

Currently, if we want to select all files, we have to write
fselect name from . where is_file = true
Having to write " = true" for a boolean feels very redundant for me. I wish I could just write fselect name from . where is_file for any boolean column. I tried that now, fselect runs without any error, but doesn't produce any output.

Finally, this simplified syntax has arrived to the master branch. Thank you for the suggestion!


CORS support for logos?

Is it possible to add support for CORS to the view serving the logos?
(Example: http://cie-provider.org:8002/static/svg/logo-cie.svg).
When the RP fetches the metadata in order to leverage the logo declared by the OP for its UI it has to download it somewhere and then serve it to the frontend, with all the complexity deriving from having to keep a local copy in sync.
With CORS support the RP could directly use the remote image as-is for its UI.
I don't know if this is something in line with specs, and probably there are security issues involved, so feel free to close it at will.

cors can be enabled in django
please consider that the RP doesn't make any use of the provider's logo, it only provide the logo URI in a UI, then it's the user-agent fetching the logo


Exposing container ports to the outside world

Hi,
How do I expose a container port to the outside world using docker.net? I'm working with a PostGres container and need to expose port 5432, Currently, I'm creating a dictionary of a string and a NoEmptyStruct and adding the port in the form $"{containerPort}:{hostPort}", but when running PostGres, the connection is being refused. I can do this using docker at the commandline quite happily, so know it's my docker.net code.
Any help appreciated.
Cheers
Sean.

@Justin,
Thanks, is there a way to map all exposed container ports to random ports on the host to simulate the -P docker run command line parameter?
Such as:
docker run --name mynginx1 -P -d nginx
From: Justin<EMAIL_ADDRESS>Sent: 27 August 2018 16:25
To: Microsoft/Docker.DotNet<EMAIL_ADDRESS>Cc: Sean Farrow<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/Docker.DotNet] Exposing container ports to the outside world (#337)
In the Create call the HostConfig has PortBindings.
var config = new CreateContainerParameters
{
// ...

HostConfig = new HostConfig

{

    PortBindings = new Dictionary<string, IList<PortBinding>>

    {

        { "5423", new List<PortBinding> { new PortBinding { "5423" } } }

    }

}

// ...

}
The first "5432" is the container port, the second "5432" is the host port.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/Docker.DotNet/issues/337#issuecomment-416264531, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABY1fm-NECcdbGBMbJac2radhbs1PUXoks5uVA9cgaJpZM4WMQGu.

Yes set
new HostConfig
{
    // ...
    PublishAllPorts = true,
    // ...
}

Thanks, that worked, so feel free to close.
From: Justin<EMAIL_ADDRESS>Sent: 27 August 2018 19:57
To: Microsoft/Docker.DotNet<EMAIL_ADDRESS>Cc: Sean Farrow<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/Docker.DotNet] Exposing container ports to the outside world (#337)
Yes set
new HostConfig
{
// ...

PublishAllPorts = true,

// ...

}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/Docker.DotNet/issues/337#issuecomment-416331003, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABY1ftoTqAgl6SiWzeBiG2ODLsZ7jzg2ks5uVEEHgaJpZM4WMQGu.


WebAssembly

It would be amazing to get this compiled to WebAssembly!
I am specifically wanting to run Sharp on CloudFlare workers which doesn't support native binaries (libvips), but does support WebAssembly.
Thanks,
Dane

This has been discussed previously at https://github.com/libvips/libvips/issues/192 - libvips and its dependencies will also need to be compiled. Good luck!

I appreciate @lovell

Good luck!

I with I could hear how you'd say that IRL, I can't over the internet, do you mean it's gonna be a really hard task?
here is a list of libvips' dependencies:

cfitsio [A library of C and Fortran subroutines for reading and writing data files in FITS (Flexible Image Transport System) data format]
fftw [A library for computing the discrete Fourier transform (DFT)]
imagemagick [An image viewing/manipulation program]
libexif [A library to parse an EXIF file and read the data from those tags]
libgsf [An extensible I/O abstraction library for dealing with structured file formats]
libheif [HEIF file format decoder and encoder]
libimagequant [Library for high-quality conversion of RGBA images to 8-bit indexed-color (palette) images]
librsvg [SVG rendering library]
libwebp [WebP library and conversion tools]
libxml2 [XML parsing library, version 2]
openexr [An high dynamic-range image file format library]
orc [Optimized Inner Loop Runtime Compiler]
pango [A library for layout and rendering of text]
poppler-glib [Poppler glib bindings]

does sharp not use any of the functionalities that depend on any of these dependencies and thus it can be/was removed?
which dependencies do you think is gonna be the hardest to port/compile with emscripten?

Let's track this at https://github.com/libvips/libvips/issues/192


Add amazon HOC modal after level 4

Coverage remained the same at 63.494% when pulling aa9a27bf0d3090f10915f7214312422b046d36c1 on amazon-hoc into aff33423288a010b5cac9ecd5c2a20080ec83a06 on master.


Fixes onShouldStartLoadWithRequest not called on first load on Android.

Summary
Fix for issue https://github.com/react-native-webview/react-native-webview/issues/1661. onShouldStartLoadWithRequest is not called on first load on Android because the first lockIdentifier value is 0, but the callback is only invoked if lockIdentifier is truthy.
Compatibility

OS
Implemented

iOS
❌

Android
✅

Checklist

[X] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Bump. Can we get some traction on this one-liner? Seems simple and safe.

Bump. Please review and merge, we need that in our code :)

@jamonholmgren @Titozzz +1 to the above. This seems like a simple fix for a recent-ish regression?
(and in case you're looking at this for the first time, I'll note that the linked issue has a better explanation of how/why this fixes things than the PR description does)

Thanks ❤

I got this erro in version 11.23.1


Add-AppxPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle error within Windows Sandbox

Type of issue
Code doesn't work
Feedback
When Installing winget on Windows Sandbox the following error is given. Using the Powershell code provided. Only occured since the October 2024 Culmative Update on Windows 11 23H2.
I'm not able to find a download to Microsoft.VCLibs.140.00.UWPDesktop .
`Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.
Windows cannot install package Microsoft.DesktopAppInstaller_1.24.25180.0_x64__8wekyb3d8bbwe because this package depends
on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00.UWPDesktop" published by
"CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor
architecture and minimum version 14.0.33728.0, along with this package to install.
NOTE: For additional information, look for [ActivityId] a41da940-2d81-000a-c60d-1ea4812ddb01 in the Event Log or use the
command line Get-AppPackageLog -ActivityID a41da940-2d81-000a-c60d-1ea4812ddb01
At line:8 char:1

Add-AppxPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundl ...

  + CategoryInfo          : WriteError: (C:\Users\WDAGUt...bbwe.msixbundle:String) [Add-AppxPackage], IOException
  + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand`

Page URL
https://learn.microsoft.com/en-us/windows/package-manager/winget/
Content source URL
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/package-manager/winget/index.md
Author
@mattwojo
Document Id
b49c32ea-2efa-b090-7123-87c31d10279b

I am also experiencing this issue. It should be related to https://github.com/microsoft/winget-cli/issues/4903 and https://github.com/microsoft/winget-cli/issues/4916

Thanks for the links - the documented installation flow is still broken, but
Install-PackageProvider -Name NuGet -Force | Out-Null
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null
Repair-WinGetPackageManager -IncludePrerelease

works again


Unbreaking make local

This removes a composer require drupal/search_api_solr that snuck into make local.  If you build from scratch, you won't neccessarily have search_api_solr from the outset.

I think @ajstanley reported this. Got a few minutes to test the fix, Alan?

Works as it's meant to.


feat: Add non-plus version of Opi 5 to docs

I may update the docs to also suggest PWM1 GPIO (wPI 16) instead of PWM15 (wPI 2) as one user was reporting an issue over in #1


multi: add zstd support

ZSTD is both faster and compresses at higher ratios than gzip, so it would be useful to have it as an option when rotating logs.
Further pro-ZSTD arguments here:
https://github.com/golang/go/issues/62513

closing in favor of #3.


Markdown - Preview synchronization after save

VSCode Version: 1.3.1
OS Version: Win10

Steps to Reproduce:

Start with new Markdown file (unsaved)
Open live preview
Create some content and save file

After saving the live preview of Markdown file is still connected to (now) nonexisting "unsaved" file. You have to close preview and open new one to see changes again...
Similar situation with "Save as..."

Duplicate of #12033


Consider prefixing methods exposed by Node and ClassifierInstance with lw

This would reduce the possibility of conflicting names in the domain space. This is similar to what EMF does.
This came up in the discussion of #148

We could consider different prefixes:

lw (LW lowercase)

Pro:

obvious abbreviation

Con:

Two letters
Spread to far sides of the keyboard

l (L lowercase)

Pro:

One letter

Con:

very easy to mix up with I (i uppercase) or 1 (one as numeral)

w (W lowercase)

Pro:

One letter
Easily recognizable

Con:

No obvious connection to LionWeb

Personally, I'd vote for 3. (w).

cc @dslmeinte

I would vote for 1. because 2. is easy to mix up and 3. is not immediately obvious in my opinion

Same as @ftomassetti


How to store and get filename with its original name in serenity

By following previous issues i also change 'OriginalNameProperty' with field name but still i am not able to save it with original name. please share me some reference code for that.

+1

Thatmust be a separate field


Convert EventGrid tests to Track2

@KieranBrantnerMagee commented on Tue May 19 2020
Currently, EventGrid tests are written in a legacy fasion, see here.
As part of modernizing EventGrid for Track2, we must utilize the proper test harness as seen here
This will broadly involve:

Writing a preparer for the EventGrid resource as seen here
Utilize the preparer on the Event grid tests mentioned above, adjusting credentials to properly thread through.
Adjusting the wrapper class to StorageTestCase as seen here
Generate new recordings, and validate that tests still run properly in both live and recorded mode

@JoshLove-msft commented on Wed Jun 09 2021
Looks like this was added to the wrong repo.

This can be closed - outdated issue which has been fixed since an year :)


Submissions not working - via API and even Kaggle web forms

Since March, 8th I can no longer submit any predictions to e.g. Porto Seguro competition (https://www.kaggle.com/c/porto-seguro-safe-driver-prediction/submit). A Late Submission using kaggle.com web form just hangs in the Scoring phase.
I replicated this error using Kaggle API (repeating dozens of times with different CSV files that used to work), I consistently get this error:
Evaluation Exception: Object of type 'Kaggle.DataFrames.Series1[System.Int32]' cannot be converted to type 'Kaggle.DataFrames.Series1[System.String]
The problem with submissions has been confirmed over the last day by other non-API users on Kaggle Feedback forum:
https://www.kaggle.com/product-feedback/83191
https://www.kaggle.com/product-feedback/83247

The problem is rather urgent, as I suspect the reported inability to process predictions data spilled over also to your Contact Form backend (as we informed you on the Product Feedback forum here). For the past 24 hours users have been unable to inform you of this issue, as it is a typical "catch 22" situation: you cannot file a bug because the bug filling channel is broken...:

[ https://www.kaggle.com/contact ]
. Keeping silent will only increase the number of people using Github as a contact form replacement

I noticed the Evaluation Exception error (which as its name suggests occurs during the scoring phase - uploads work correctly), happens at roughly 75% of the file (at the 6th second in the scoring process which normally completes after 8 seconds). This happens also to files which I previously managed to score successfully, so the error is not inside my files.

This is not an API issue.  Please continue this on the Kaggle website.  I'm the only one who checks this repo, and I can't help you.  I've pinged appropriate people about the threads on our site, but posting issues here won't help further.


The code get stuck

I run the code with Slurm job scheduling system (which means I use sbatch xx.sh to run the code), however when I set the --nproc_per_node = 2, the code will get stuck, while I set the --nproc_per_node = 1 the code won't get stuck.
When I set --nproc_per_node=2, one process will get stuck at  for data in train_loader: (line 198 in train.py), the other  process get stuck at self.scaler.step(self.optimizer) (line 165 in model.py). The code does not stop, but it does not go to the next step, nor does it output anything. It just keep running.
Do you know why this phenomenon occurs?

@zhouweii234 I actually ran into this problem in some other places today... It seems to be related to PyTorch DDP in some machines, and using NCCL_P2P_DISABLE=1 before training solves it for me.
Related discussion: https://github.com/PyTorchLightning/pytorch-lightning/issues/4612


Get values/states in FormSection

Hello,
I started to learn redux and redux-forms few days ago. For my project I used latest Redux form and i split original form into multiple FormSections. Inside user registration "FormSection" I want to dynamically add new fields based on field/state values. Problem is that I can't get values of current form section.
I tried all I could find but I didn't find any solution.
Is there way to get form values inside FormSections?
Here is Form Section code I use:
class BookerInformation extends FormSection {

    static defaultProps = {
        name: "booker"
    }
    handleEmailBlur(event){

        //triggers error that state is empty/undefined
        //fetchUser(this.state.email);
        const ItemList = formValues('booker.name')(BookerInformation)
        const ItemList2 = formValues({name: 'name'})(BookerInformation)
        const ItemList3 = formValues('busRentForm')(BookerInformation)

        //outputs original code of formValues

        console.log(ItemList);
        console.log(ItemList2);
        console.log(ItemList3);
    }

    render() {
        return

Booker information

                        <Field name="name" validate={[required, maxLength15]} classname="col-md-4" type="text"
                               icon="icon-User" component={renderInput}
                               label="Full Name"/>
                        <Field name="phone" classname="col-md-4" validate={[required]} type="text"
                               component={renderInput} icon="icon-Phone"
                               label="Phone"/>

                        <Field name="email" onBlur={this.handleEmailBlur} classname="col-md-4"
                               validate={[required, email]} type="email" component={renderInput} icon="icon-Email"
                               label="E-mail"/>

                        <button type="button" className="btn btn-continue waves-effect waves-light">Continue</button>

    }

@zmaglica, thanks for this. A current solution which you can use now, and and a proposal to make this easier than the current solution is available at https://github.com/erikras/redux-form/issues/3182#issue-242856265. You will need to add an HOC that can use the prefixed name prop, and inject it for you. I'm closing this issue as a duplicate of #3182.


[Monaco] CSP has no extension associated with it in monaco_languages.json.

Microsoft PowerToys version
0.80.1
Installation method
GitHub
Running as admin
None
Area(s) with issue?
File Explorer: Preview Pane, Peek
Steps to reproduce
This piece of code in monaco_languages.json.
{
    "id": "csp",
    "extensions": [],
    "aliases": [
        "CSP",
        "csp"
    ]
}

It seems that .csp files were intended to be previewable. However since extensions is empty, they aren't.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

cc: @Aaron-Junker

This would have to be fixed in the monaco source code: https://github.com/microsoft/monaco-editor/blob/main/src%2Fbasic-languages%2Fcsp%2Fcsp.contribution.ts#L13

@Aaron-Junker
Is there in issue in Monaco's repository or do you plan to open a fix PR?

@Aaron-Junker
PR in monaco repo is merged and marked for the May release. Can you please update monaco after the release?

fyi: Thanks all for flagging

@crutkas , @Aaron-Junker
The monaco version including the fix was released 8 days ago. We can update our dependency.


tests-d2d/*.jpg

what is this line:
cp tests-d2d/*.jpg dist/tests-d2d

for in buildbundle.sh ?

This is to import the test image used for loadimage in the test cases. Importing an image from elsewhere gives cors errors when trying to get the canvas image data for generating the hash. Having it be a local image was the easiest fix, but I can try finding another solution if needed.

seems okay to me.


List the PackageIdentifier of the package to be added to automation
Minusium.MicaForEveryone
Details about the application
https://github.com/minusium/MicaForEveryone
https://github.com/minusium/MicaForEveryone/releases/download/v<IP_ADDRESS>/MicaForEveryone-v<IP_ADDRESS>-Release.msixbundle

Oops

https://github.com/minusium/MicaForEveryone/issues/36 would have to be sorted out first.

You need to install my custom certificate to be able to install it.

You need to install my custom certificate to be able to install it.

Like I said in https://github.com/minusium/MicaForEveryone/issues/36#issuecomment-1074116748, not secure and not supported. What the blocker here is waiting for the Microsoft Store release.

Since Mica is being made available on Microsoft Store, and WinGet supports installing from Microsoft Store... it doesn't need to be there in winget-pkgs repo.

It can be both, right? Like Windows Terminal?

Btw project link is no longer valid, it's https://github.com/minusium/MicaForEveryone now.

You mean https://github.com/MicaForEveryone/MicaForEveryone, updated links.

https://github.com/MicaForEveryone/MicaForEveryone/pull/102


fix: make social container element a span

When using SocialIcon inside a <p> element you will see the following warning in your console:
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>.

This is triggered by the social-container div, so setting the as prop has no effect on this warning.
Fixed by changing this div into a span. Since the social-container is positioned absolute this has no visible effects.

@dejorrit thank you for contributing, released in v6.7.0


Address change because script change

const brcop = '{"p":"brc-20","op":"mint","tick":"aaa","amt":"10"}'
const script = [ pubkey, 'OP_CHECKSIG', 'OP_0', 'OP_IF', Buffer.from(brcop), 'OP_ENDIF' ];
const tapleaf = tapScript.Tap.encodeScript(script);
const [ tpubkey, cblock ] = tapScript.Tap.getPubKey(pubkey, { target: tapleaf });
const address = tapScript.Address.p2tr.fromPubKey(tpubkey);
const txdata = tapScript.Tx.create({
vin  : [{
txid: 'txid',
vout: 0,
prevout: {
value: 10000,
scriptPubKey: tapScript.Address.toScriptPubKey(address)
},
}],
vout : [{
value: 5000,
scriptPubKey: tapScript.Address.toScriptPubKey('myaddress')
}]
});
const sig = tapScript.Signer.taproot.sign(seckey, txdata, 0, {extension: tapleaf});
txdata.vin[0].witness = [ sig, script, cblock ];
const isValid = await tapScript.Signer.taproot.verify(txdata, 0, { "pubkey": pubkey,"script":script});
If I change brcop to  '{"p":"brc-20","op":"mint","tick":"bbb","amt":"10"}', the script will change and the address will also be changed, and I can not submit the transaction because 'non-mandatory-script-verify-flag (Witness program hash mismatch)'. Could you tell me how to solve it?

The address is calculated using the script, so if the script changes then the address must also change. There is no way around this as the address is a cryptographic representation of the scripts. Once it is published and coins are locked to it, there is no changing it. You have to spend the coins in order to move them to a new address.


Refactored to use Slash Commands

Changelog

Refactored to add a slash command
Added some testing

/label enhancement

/dog

/label merge

/approve


Websocket stops sending data but doesn't close connection

Hi,
Previously mentioned in issue #89 . The web socket stops sending data and seems to get stuck inside the on_error method in the websocket_client.py class. The print statement infinitely outputs: "socket is already closed. - data: None". Which means that the websocket doesn't really close and gets stuck in the _listen method even when there is no data coming through. We're currently testing a fix for this, where we close the current thread in the on_error method and then automatically restart the socket.

Are you using the github version or the version from PyPi?

pretty sure I'm using the github version. Used the following command:
pip3 install git+https://github.com/danpaquin/gdax-python.git

I am also running into this issue. Is there a way to restart the socket if it gets caught up in the on_error method?

I am also running into this issue. Is there a way to restart the socket if it gets caught up in the on_error method?

I raise the Exception in the WebsocketClient on_error method(), then in my main thread run an infinite loop over a try: except: block, and for any exception I call WebsocketClient.close() and WebsocketClient.start()

I check every 15 seconds to see if there is data coming from the stream. If there is no data within 15 I close and start the stream again.
wsClient.close()
wsClient.start()

@ankit1200 can you show your code how you implemented it? thanks in advance


Don't bail out on missing app-info file

We might want to tighten this up because we don't want to leave any metainfo/app-info/... in the Flatpaks which get merged into the appstream but don't get found and patched to have true storefront info (verified, pricing, etc). Do we need to check any legacy paths that appstream-cli would still pick up? Or is this definitely the only path Flatpak will export?

Flatpak also exports appdata/metainfo, but I have no idea what for and what consumes it. The combined AppStream file is the one consumed by frontends.

Yeah, I think we need to make sure we are checking/filtering all paths that the appstream tools will collect into our official appstream. Hopefully @jameswestman can take a look when he awakes.

This hook is a "security" filter though, from this point on, only true data we have checked should remain. We should explicitly remove the legacy paths at this point if we only want there to be one valid path through the system. ie we don't want to be leaving false vending data in a path that some people do use just because it's not the one we use.


add script to enable publish by time

Content can be wrapped around with the following tag in templates to enable displaying them only once a preset time is past.
{{#if (timed_publish "2023-07-25T17:26:00Z" env.PREVIEW_MODE)}}

// Content

{{/if}}

Thanks @karthik2804
This works great (even nesting the publish time if inside a sidebar menu's if.
Thanks again; this will come in handy in the future.


[tool_crash] FileSystemException: Cannot create link, OS Error: Incorrect function., errno = 1

Command
flutter build windows

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot create link, OS Error: Incorrect function.
, errno = 1
#0      _Link.throwIfError (dart:io/link.dart:254:7)
#1      _Link.createSync (dart:io/link.dart:182:5)
#2      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#3      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#4      _createPlatformPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:1057:12)
#5      createPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:987:5)
#6      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1089:5)
<asynchronous suspension>
#7      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:357:5)
<asynchronous suspension>
#8      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1412:7)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1257:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)

[✓] Flutter (Channel stable, 3.7.12, on Microsoft Windows [Version 10.0.17134.1246], locale en-US)
    • Flutter version 3.7.12 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (11 days ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Build Tools 2022 17.5.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools
    • Visual Studio Build Tools 2022 version 17.5.33530.505
    • Windows 10 SDK version 10.0.22000.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[✓] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.17134.1246]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 112.0.5615.138
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 112.0.1722.58

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: b8f7f1f9869bb2d116aa6a70dbeac61000b52849
Plugins
path_provider-2.0.12
path_provider_android-2.0.22
path_provider_foundation-2.1.1
path_provider_linux-2.1.7
path_provider_windows-2.1.3
realm-1.0.0

Closing this as a duplicate of https://github.com/flutter/flutter/issues/66224.
Kindly subscribe to the original issue for updates.
Thank you


Weird behavior when using virtual slides

BUG REPORT TEMPLATE
Vue.js version and component version
{
  "dependencies": {
    "swiper": "5.3.7",
    "vue": "^2.6.11",
    "vue-awesome-swiper": "4.1.0"
  },
}

Reproduction Link
https://codesandbox.io/s/vue-awesome-swiper-virtual-slides-test-p9wnf?file=/src/App.vue
Steps to reproduce
Slide to the end of slides
What is Expected?
I can't reach the last slide. everything works fine when I create a Swiper instance manually (see demo)
We should not be able to view the last slide when using vue-awesome-swiper.
This may be related to #609.

Hi! @bgondy
Thanks for your feedback, it seems that this bug is caused by component automatic update.
You can comment the local node_module/vue-awesome-swiper/dist/vue-awesome-swiper.js file related 420 421 lines for testing.
If the example works as expected after the comment, I will publish a new version soon.

It worked!

upgrade to v4.1.1
add option :auto-update="false" to swiper component

I'm sorry but what does auto-update prop do ?

I'm sorry but what does auto-update prop do ?
https://github.com/surmon-china/vue-awesome-swiper/blob/master/README.md#swiper-component-api

Thank you, it now works as expected.


Decode and expose fan speed capabilities

Based on reference code, the fan speed capability can be decoded to indicate which discrete fan speeds are actually supported (and possibly indicate if custom speeds are supported)

Of my devices, one is capable of arbitrary fan speeds, the other only supports low, med, high, auto. Their fan speed capabilities are 1 and 5, respectively.
Based on the decoding map from the plugin. I am led to believe that isNopolar property indicates if a fan is capability of arbitrary fan speeds, and otherwise the type array indicates the supported modes.
var windMap = {
    "0": { //-1
        isNopolar: false,
        type: []
    },
    "1": {
        isNopolar: true,
        type: []
    },
    "2": { //-1
        isNopolar: false,
        type: []
    },
    "3": {
        isNopolar: false,
        type: [_Data.CMD.WINDSPEED_LOW, _Data.CMD.WINDSPEED_HIGH]
    },
    "4": {
        isNopolar: false,
        type: [_Data.CMD.WINDSPEED_LOW, _Data.CMD.WINDSPEED_HIGH, _Data.CMD.WINDSPEED_AUTO]
    },
    "5": {
        isNopolar: false,
        type: [_Data.CMD.WINDSPEED_LOW, _Data.CMD.WINDSPEED_MID, _Data.CMD.WINDSPEED_HIGH, _Data.CMD.WINDSPEED_AUTO]
    },
    "6": {
        isNopolar: false,
        type: [_Data.CMD.WINDSPEED_MUTE, _Data.CMD.WINDSPEED_LOW, _Data.CMD.WINDSPEED_MID, _Data.CMD.WINDSPEED_HIGH, _Data.CMD.WINDSPEED_AUTO]
    },
    "7": {
        isNopolar: false,
        type: [_Data.CMD.WINDSPEED_LOW, _Data.CMD.WINDSPEED_MID, _Data.CMD.WINDSPEED_HIGH]
    }
};


Email/SMS Support

Just to jot down the thoughts that I have in my mind

Each App has its set of credentials. An app can have multiple clients who use them. So example fk would be an app, and clients would be website, oms etc. Another app would be fk-marketing which would have a different set of credentials and so on.
Retries : Based on the providers available for a particular app, it will retry and fall back to alternate provider when an 5xx exception happens for a particular provider. If a provider breaches a particular threshold of errors that provider would be killed for x minutes.
Tracking - open & click tracking would happen via a cname "l.example.com" which would have urls like "l.example.com/t/". This would be the only endpoint which will not have any versioning since urls needs to be backwards compatible and we neither want to expose anything. The base64 token may consit of the versioning information if required.  Each client would add a cname pointing to connekt.flipkart.net so that when redirection happens for clients like ekart/phonepe they don't see flipkart urls. This cname would be available in the app info and would be used to build corresponding tracking urls.
Optional: There should be provision for ramp up of a particular provided. This is optional but should be thought of.
Bounce list would be also maintained at connekt end and would be queriable via api. Whenever any provider marks an email address as bounced the email id is also marked as bounce by connekt and all future requests to be dropped at connekt end and not forwarded to any provider. Soft bounce to auto-expire after 15 days (at which connekt would via api call remove it from all providers bounce list). For hard bounces, clearing should be available via api, which clients can trigger and connekt would in turn remove from all providers lists.
Multicast: If providers support then yes. But this will loose on unique click/open metrics. Or is there option to have this without losing tracking [browser signature maybe (Clicks are certainly possible, for opens which are proxied via google this may not work)] ?
Metrics : Aggregate: total open, total click, unique open, unique clicks. Individual metrics available at messageId level.
Support for blacklist of addresses  #151 to be completed before this channel. This is required since there would be complaints. (Blacklist would be just another suppression list like bounces, you get the idea..)
Scheduling of email? barklice may not be right place for it (due to the size of the email). IF all our providers support it, we should only support by directly handing off the request to the provider)
etc.. (to be added as new thoughts come to mind)

Supported via #246


Remove the "Under construction" section in the README right before releasing version 1.0.0

Closed by https://github.com/robertpainsi/filtering.js/commit/059d1383600baef74936aa9c75c6ad16f01b00bc


Use pytest.mark.filterwarnings instead of filtering each test case.

We often forget to put the per-test-case decorators, resulting in test
failures in cases not covered by github CI (e.g. Cloud TPU
tests). This change filters warnings for the whole test module
instead. It's only applied if pytest is installed.

We have similar global filters in pytest.ini; maybe put this one there as well? https://github.com/google/jax/blob/90d606fe25297f6adb675391c54d68f77a7a37b7/pytest.ini#L1-L16

Ooh agreed Jake's proposal is better! Done.


1.4 (stable) plans

1.4.??? Doesn't WC already have 1.4? the 1.4 Beta has been out since 4 days ago since at the time of typing this.
changes:

adds Old Combat Mod or Combatify
re-adds Legacy Mipmaps
re-adds Not Enough Animations

other changes:

idk

you should release a full version of 1.4 before just adding a subversion

Yeah, I get ya, the beta is pretty much complete just without the above.

combatify seems to mess up the held item tooltips

https://github.com/contrarybaton60/Williams-Console/releases/tag/v1.4b2%2Bmc1.21

https://github.com/contrarybaton60/Williams-Console/releases/tag/v1.4b3%2Bmc1.21


Log exceptions

Related to this PR. I forgot to log the exceptions

Codecov Report
Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

apps/experiments/tasks.py
66.66%
1 Missing :warning:

Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


LNPoS Clear Button Not Working

When selecting LNPoS as a payment method and typing in any value, the Clear button does not work and forced to restart the stack

Seems to be fixed after removing && lnCheck from line 558

Unsure if this is related, but AMT invoices are being created 100x less than they should be

LNURLPos and LNURLATM QR codes can't be scanned


Add jmolecules-hexagonal-architecture dependency

This PR resolves #5

That's merged. Coming with 2022.2.4. Also merged to main.


Wine:/Debian/xUbuntu_20.10 Resource Not Available

Describe the bug
When installing against Ubuntu 20.10 it seems like the Wine repo no longer exists for 20.10. The only available versions seem to be:

xUbuntu_18.04/
xUbuntu_20.04/
xUbuntu_21.04/
xUbuntu_21.10/

To Reproduce
Install against Ubuntu 20.10.
Expected behavior
Expected to download and/or update Wine:
Ign:20 https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_20.10 ./ InRelease
Err:21 https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_20.10 ./ Release
  404  Not Found [IP: <IP_ADDRESS> 443]
Reading package lists... Done
E: The repository 'https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_20.10 ./ Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Screenshots

It looks like Ubuntu 20.10 is end of life in July 2021 so Wine probably dropped the repo.

@realumhelp Thank you very much for help. :+1:

No problem that was crazy fast response time! I guess this shows how often I update my system... haha


Combining labels with a custom resource prevents logs from being recorded

Environment details

OS: node:8.11.2 docker image
Node.js version: 8.11.2
npm version: 5.6.0
@google-cloud/logging-winston version: 0.9.0

Steps to reproduce

Initialize a Winston logger with LoggingWinston
Define a custom resource with the proper project labels
Define custom default labels to be emitted with the specified resource
Log a line with labels
The event will be rejected by Stackdriver (or never emitted)

const { LoggingWinston } = require('@google-cloud/logging-winston');
sdLoggingOptions = {
  logName: 'custom_logname',
  resource: {
    type: 'gae_app',
    labels: {
      project_id: 'my-project-id',
      module_id: 'default',
      version_id: 1
    }
  },
  labels: {
    main_app: true
  }
};
let logger = new winston.Logger({
  level: 'info',
  transports: [new LoggingWinston(sdLoggingOptions)]
});
logger.info('This will be recorded properly');
logger.info('This will NOT be recorded properly', {custom_metadata: 'yes', labels: {log_line: 'sample'}});

The first event will be logged properly with the extra labels attached to the log entry but the second event will not be logged AT ALL.

Thank you for opening this issue.  I do not know off hand why the second event is not being logged, and we will need to look into it.  We will keep this thread updated as we explore the issue.  Thanks.

Any updated on this issue ?
I am having the same problem.
Every time I try to log with custom metadata the logs don't get logged, although if I put only a single property it works (in my case I wanted to log a json object tough).

I am closing this for now since I cannot reproduce this bug.  If anyone is still experiencing this bug, we can reopen the bug at that time.


Having trouble training this

Could you upload a pre-trained MetaFBP model?

Sorry, the pre-trained weights are not in my PC.  You can provide any error log or screenshot during training so that we can help you to solve it.


Events Page

Needs to have Google Cal embed and look nice

Began work on events page

Page done in 7fa5641467d4f1153d3c7882b8b878bcbea9edc9


Compatibility with older python versions

Hi !
The use of from __future__ import annotations, and subsequent postponed annotations, prevents xstate to be used with version 3.6 of python, despite being still officially supported.
Can you ensure the compatibility with that version ?

Hi Aluriak,
You are correct 3.6 is still supported and that using postponed annotations is 3.7+ pep-0563.
I'll work on a solution. Cheers.


How to wrap callbacks?

This is a genuine question at this point, cause I don't have a plan :P

There's an example of using a C callback function from Nim, does it help? https://github.com/greenfork/nimraylib_now/blob/master/examples/core/core_custom_logging.nim

I used vsprintf to a buffer and added an extra function pointer:
type
  TraceLogCallback* = proc (logLevel: TraceLogLevel; text: string) {.nimcall.} ## Logging: Redirect trace log messages

var
  traceLog: TraceLogCallback # TraceLog callback function pointer

proc wrapTraceLogCallback(logLevel: int32; text: cstring; args: va_list) {.cdecl.} =
  var buf = newString(128)
  vsprintf(buf.cstring, text, args)
  traceLog(logLevel.TraceLogLevel, buf)

proc setTraceLogCallback*(callback: TraceLogCallback) =
  ## Set custom trace log
  traceLog = callback
  setTraceLogCallbackImpl(wrapTraceLogCallback)

Not sure if it's worth it. Your opinion?

There's still va_list type from C varargs. I'm not sure that we want it because if we choose to change it, we make it Nim-native implementation. Here we still have to interface with C. And I'm not sure if we can safely translate it to Nim either.


new import of custom template latest develop

import gives an error No template.xml found!
language issues e.g. Add a custom learn object in Xerte
Description needs to be text area rather than single line input or at least wider input field

I think this was fixed as part of the sub-template developments so will close the issue.


fix(idle): overview fiat amount from underlying asset

Description

Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #3405   👈

This comment was auto-generated by Graphite.


Import the Equinix Metal Terraform provider

This PR imports all of the resources from the Equinix Metal Terraform provider, preserving the history of the project.
Most of this import was mechanical, with search/replace and scripted git mv commands.
Changes to equinix/provider.go, equinix/config.go, equinix/provider_test.go, equinix/config_test.go, and /main.go were minor but more hands-on.
TODO and open questions:

[ ] Add Equinix Metal API tokens to GH
[ ] Remove vendor/ from the repo? (rewrite history to remove vendor/?)
[ ] Remove metal deprecations (volumes, PACKET_ variables, other features)
[ ] Squash history?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c420672). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #94   +/-   ##
=========================================
  Coverage          ?   52.00%
=========================================
  Files             ?       65
  Lines             ?    10837
  Branches          ?        0
=========================================
  Hits              ?     5636
  Misses            ?     5048
  Partials          ?      153

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 c420672...e321045. Read the comment docs.

[ ]  Use subcategory: 'metal' (and others) in docs?

I'd keep for now current dir structure

It will allow us to take advantage of the plugin  to generate terraform provider docs whose output follows the same structure

https://www.terraform.io/registry/providers/docs#generating-documentation
using the generator will reduce workload and we can ensure that all resources appear in the registry and we don't forget any of them. It will also si

Additional tasks identified so far:

[ ] Rename the metal data source files so they all follow the same pattern: datasource --> data_source_
[ ] Redefine GH Actions so that it does not fail in each code push. In metal there was an action to run acceptance test on push. At this moment it is not possible to add this for Fabric/ne resources
[ ] Split code into folders by product? It can help simplify management / independently handle behaviors for tests/actions/checks:

It could be:
          equinix/provider.go
          equinix/fabric/
          equinix/network_edge/
          equinix/metal/

Or a subfolder services like AWS and Azure providers:
          equinix/
          equinix/provider/
          equinix/services/fabric/
          equinix/services/network_edge/
          equinix/services/metal/

[ ] Rename "ecx" files to "fabric"?

@ocobleseqx Some of Hashicorp's modern providers (AWS, Azure) take the approach of internal/service/foo/foo_resource.go and internal/service/foo/foo_data_source.go.  The Azure provider splits functionality up further, _import.go.

Split code into folders by product? It can help simplify management / independently handle behaviors for tests/actions/checks:
Rename the metal data source files so they all follow the same pattern: datasource --> data_source_

I think we care come up with a more comprehensive refactoring after this is merged. s/datasource/data_source/ seems fine for now.

Closing in favor of #95


Add support for Xiaomi Mijia Smart Door Lock

My door lock is Xiaomi Smart Door Lock.
After add XiaomiGateway3 component, the system cannot recognize the device and only showed BLE device.

BLE ID: 794
Brand: Xiaomi
Device: Smart Door Lock
Model: MJZNMS02LM
Hope this could be helpful.

It should already supported. Unknown model not a problem. Do you have action entity? Is it attributes changed with any activity with lock?

It should already supported. Unknown model not a problem. Do you have action entity? Is it attributes changed with any activity with lock?

I edit bluetooth.py and added the model into list. After that, the model name shows up. I think it is OK now.  👍

I edit bluetooth.py and added the model into list. After that, the model name shows up. I think it is OK now.  👍


Add test case for #602 pull request fix.

@lukewestby @rluiten could one of you please update this PR with context from #602 ?

@eeue56 sure!
The primary occurrence of this issue is described in this thread from elm-dev. One of the tests in @rluiten's trie package is attempting to decode key-value pairs on something that is not an object. Instead of resulting in Err as expect, it's throwing a runtime error because the err function used on https://github.com/elm-lang/core/blob/master/src/Native/Json.js#L409 does not exist and should be badPrimitive instead. As of Sun May 15 2016 10:58:49 GMT-0500 (CDT) this PR is still waiting on https://github.com/rluiten/core/pull/1 and will include both the fix and the test case covering this branch of runHelp in Native.Json once merged.

@evancz ping (this is fairly important)
tl;dr -
err should be badPrimitive, this renames that and adds a test case to make sure dict decoding is more tested


fix: test service spec and apply validation

The validation step was skipped. I enabled it and fixed one spec error.

Only one thing you could do - check if the generator fails with exit code != 0 in case of a faulty spec file.

Only one thing you could do - check if the generator fails with exit code != 0 in case of a faulty spec file.

@FrankEssenberger , I skipped the validation again and only kept the fix for the test service spec after discussed with @marikaner , because this might be related to a decision about whether we allow duplicate operationId in the spec file.

@FrankEssenberger , I skipped the validation again and only kept the fix for the test service spec after discussed with @marikaner , because this might be related to a decision about whether we allow duplicate operationId in the spec file.


AKS workload identity - clarify required labels

The docs state:

Ensure your application pods using workload identity have added the following label [azure.workload.identity/use: "true"] to your running pods/deployments, otherwise the pods will fail once restarted.

It's not clear what pods/deployments means - specifically, if we have a deployment, should we add the label at the deployment metadata level as well, or just the pod template?
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    azure.workload.identity/use: "true" //required too?
spec:
  template:
    metadata:
      labels:
        azure.workload.identity/use: "true"

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

ID: 773aa5fa-a931-f6f1-f339-6367cef12209
Version Independent ID: 48c7d57f-55a0-5894-5379-ef7d6ed1e24d
Content: Deploy and configure an Azure Kubernetes Service (AKS) cluster with workload identity - Azure Kubernetes Service
Content Source: articles/aks/workload-identity-deploy-cluster.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@ohads-MSFT
Thanks for your feedback! We will investigate and update as appropriate.

@ohads-MSFT
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@MGoedtel
Can you please check and add your comments on this doc update request as applicable.

@ohads-MSFT - This note was written by one of our PMs and I believe what they were trying to emphasize is that annotation is required in a pod template. I'm going to file a bug for this note and also reach out to them to confirm that's the point they were attempting to make. I should have this article updated tomorrow.

kind: Deployment
metadata:
  labels:
    azure.workload.identity/use: "true" //required too?

In other words, this is not needed right?
kind: Deployment
metadata:
  labels:
    azure.workload.identity/use: "true"

@ohads-MSFT - This note was written by one of our PMs and I believe what they were trying to emphasize is that annotation is required in a pod template. I'm going to file a bug for this note and also reach out to them to confirm that's the point they were attempting to make. I should have this article updated tomorrow.

In other words, this is not needed right?
kind: Deployment
metadata:
  labels:
    azure.workload.identity/use: "true"

@ohads-MSFT - Just got confirmation the note was meant to be specific to the Pod spec. So to answer your last question, no you don't add that annotation to the Deployment spec.

PR https://github.com/MicrosoftDocs/azure-docs-pr/pull/253016 is completed and merged. I'm going to proceed with closing this PR. Thank you.
#please-close


NTR: [ACP-dependent peptidyl-lysine N6-myristoyltransferase activity] and other terms related

Hi GO,
I recently requested an update to add Rhea cross references for GO:0018030 (peptidyl-lysine N6-myristoyltransferase activity) and GO:0018031 (peptidyl-lysine N6-palmitoyltransferase activity)
Unfortunately, it looks like that there are 2 different manners to catalyze peptidyl-lysine N6-palmitoylation and N6-myristoylation.
Some proteins catalyze a CoA-dependent reaction, while a family in bacteria catalyzes reactions dependent on ACP.
I would therefore need to create children GO terms
Thanks
Sylvain

ACP-dependent peptidyl-lysine N6-myristoyltransferase activity
Catalysis of the reaction: L-lysyl-[protein] + tetradecanoyl-[ACP] = H(+) + holo-[ACP] + N(6)-tetradecanoyl-L-lysyl-[protein]
child of GO:0018030 peptidyl-lysine N6-myristoyltransferase activity
PMID:32461253
Xref: Rhea:70611

ACP-dependent peptidyl-lysine N6-palmitoyltransferase activity
Catalysis of the reaction: hexadecanoyl-[ACP] + L-lysyl-[protein] = H(+) + holo-[ACP] + N(6)-hexadecanoyl-L-lysyl-[protein]
child of GO:0018031 peptidyl-lysine N6-palmitoyltransferase activity
PMID:32461253
Xref Rhea:70615

CoA-dependent peptidyl-lysine N6-myristoyltransferase activity
Catalysis of the reaction: L-lysyl-[protein] + tetradecanoyl-CoA = CoA + H(+) + N(6)-tetradecanoyl-L-lysyl-[protein] ~[Rhea:59752]~
PMID: 1402651
child of GO:0018030 peptidyl-lysine N6-myristoyltransferase activity
~RHEA:59752~

CoA-dependent peptidyl-lysine N6-palmitoyltransferase activity
Catalysis of the reaction: L-lysyl-[protein] + hexadecanoyl-CoA = CoA + H(+) + N(6)-hexadecanoyl-L-lysyl-[protein] [Rhea:59752]
PMID: 30061757
child of GO:0018031 peptidyl-lysine N6-palmitoyltransferase activity
~RHEA:55420~ has been removed  from RHEA.

Update GO:0018031 peptidyl-lysine N6-palmitoyltransferase activity

Remove Xref RHEA:55420

Update GO:0018030 peptidyl-lysine N6-myristoyltransferase activity

Remove RHEA:59752

+def: "Catalysis of the reaction: L-lysyl-[protein] + tetradecanoyl-[ACP] = H(+) + holo-[ACP] + N(6)-tetradecanoyl-L-lysyl-[protein]." [PMID:32461253, RHEA:70611]
+xref: RHEA:70611
+is_a: GO:0018030 ! peptidyl-lysine N6-myristoyltransferase activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/22968 xsd:anyURI
+created_by: pg
+creation_date: 2022-03-02T12:44:18Z
+
+[Term]
+id: GO:0140770
+name: CoA-dependent peptidyl-lysine N6-myristoyltransferase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: L-lysyl-[protein] + tetradecanoyl-CoA = CoA + H(+) + N(6)-tetradecanoyl-L-lysyl-[protein]." [PMID:1402651, RHEA:59752]
+xref: RHEA:59752
+is_a: GO:0018030 ! peptidyl-lysine N6-myristoyltransferase activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/22968 xsd:anyURI
+created_by: pg
+creation_date: 2022-03-02T12:45:16Z
+
+[Term]
+id: GO:0140771
+name: ACP-dependent peptidyl-lysine N6-palmitoyltransferase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: hexadecanoyl-[ACP] + L-lysyl-[protein] = H(+) + holo-[ACP] + N(6)-hexadecanoyl-L-lysyl-[protein]." [PMID:32461253, RHEA:70615]
+xref: RHEA:70615
+is_a: GO:0018031 ! peptidyl-lysine N6-palmitoyltransferase activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/22968 xsd:anyURI
+created_by: pg
+creation_date: 2022-03-02T12:51:53Z
+
+[Term]
+id: GO:0140772
+name: CoA-dependent peptidyl-lysine N6-palmitoyltransferase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: L-lysyl-[protein] + hexadecanoyl-CoA = CoA + H(+) + N(6)-hexadecanoyl-L-lysyl-[protein]." [PMID:30061757, RHEA:59752]
+xref: RHEA:59752
+is_a: GO:0018031 ! peptidyl-lysine N6-palmitoyltransferase activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/22968 xsd:anyURI
+created_by: pg
+creation_date: 2022-03-02T12:52:22Z

After exchange with @sylvainpoux
GO:0140772  CoA-dependent peptidyl-lysine N6-palmitoyltransferase activity is in fact a broader term for
RHEA:59768
hexadecanoyl-CoA + L-lysyl-/S-(2E,6E,10E)-geranylgeranyl-L-cysteinyl-[protein] = CoA + H(+) + N(6)-hexadecanoyl-L-lysyl-/S-(2E,6E,10E)-geranylgeranyl-L-cysteinyl-[protein]


Array.indexedMap stops at 1024

Try this in repl:
Array.indexedMap (\idx v -> idx) <| Array.fromList [0..1030]
results in ... 1021,1022,1023,0,1,2,3,4,5,6]
List.indexedMap seems to be OK

Isn't that the same as https://github.com/elm-lang/elm-lang.org/issues/262 and https://github.com/elm-lang/core/issues/271, which was fixed in https://github.com/elm-lang/core/pull/391 (but hasn't yet been released as part of a new core version)?


How to set up a development environment?

When I clone the repo and run go build, I get:
main.go:13:2: cannot find package "github.com/blang/semver" in any of:
	/usr/local/go/src/github.com/blang/semver (from $GOROOT)
	/Users/anovak/Documents/Workspace/Go/src/github.com/blang/semver (from $GOPATH)
main.go:14:2: cannot find package "github.com/codegangsta/cli" in any of:
	/usr/local/go/src/github.com/codegangsta/cli (from $GOROOT)
	/Users/anovak/Documents/Workspace/Go/src/github.com/codegangsta/cli (from $GOPATH)
main.go:15:2: cannot find package "github.com/whyrusleeping/gx/gxutil" in any of:
	/usr/local/go/src/github.com/whyrusleeping/gx/gxutil (from $GOROOT)
	/Users/anovak/Documents/Workspace/Go/src/github.com/whyrusleeping/gx/gxutil (from $GOPATH)
main.go:16:2: cannot find package "github.com/whyrusleeping/stump" in any of:
	/usr/local/go/src/github.com/whyrusleeping/stump (from $GOROOT)
	/Users/anovak/Documents/Workspace/Go/src/github.com/whyrusleeping/stump (from $GOPATH)

It looks like, according to the Internet, the solution is to run go get ./..., but then I'm stuck using the Github version of gxutil, so if I were to want to make a change in that package, I'm not sure how I'd do that.
It also looks like my checkout has to be under $GOPATH/src.
This is all probably obvious information for anyone who has ever used Go before, but I haven't, so I would appreciate a simple step-by-step guide in the README for getting set up. Something like:
cd $GOPATH/src
git clone git@github.com:whyrusleeping/gx.git
cd gx
go get ./...
go build

Is that actually the right procedure to get set up? How should I extend it if I also want to tinker with a dependency?
If this is the Right Way, I'll open a PR.

I usually do:
go get -d github.com/whyrusleeping/gx
cd $GOPATH/src/github.com/whyrusleeping/gx
go build

It works afaik.

what @Kubuxu says here is the recommended way of setting up a gx dev environment, I'll add it to the readme

docs updated in the readme


HTTP status code when errors occur

From casual and impressionistic observation of several BRAPI implementations, it seems that even when errors are reported in the status collection of the meta data object, the http status code  remains 200. It has been suggested that the status code should be in the 500-and-above series in these situations.
It has also been pointed out, on the other hand, that as long as the server's response is intelligible as BRAPI response, even if that response contains error messages, the status from the http point of view should remain 200.
One way or another, the API spec should define the standard practice.

I agree that the specification should define a standard practice.
Roy Fielding originator of REST developed it based on HTTP specification.
HTTP RFC states that:
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request.
So I think it makes more sense to use a status code from 5XX.

Makes sense to me, too.

I agree that we should be using standard HTTP response codes whenever possible. I'd like to piggy back this issue and ask the question, what is the purpose of the "status" array in the brapi metadata?
The use of "code" within each status object seems redundant. If your HTTP status is 500, do you need the status array to also contain a "500" code? In reality, I believe the the "status" objects are primarily used to send log data to be presented to the user (or developer).
I propose that the structure of the "status" objects should be changed to the following:
{
message: "this is a log message",
messageType: "INFO"
}
where "messageType" can be any of the standard logging levels (INFO, DEBUG, WARNING, ERROR, etc)

One valid use case for status array is if there is a request for data extraction then an asyncId is provided in the status which is queried till completion.
It seems that the use of "code" is redundant. For the above case if HTTP response is 200 then  we can assume that status is JobId.
{
message: "this is a log message",
messageType: "INFO"
}
There is no issue with this status structure . But it looks like an overkill. We can just have a message field which when combined with HTTP status code can give complete information. I think we dont care MessageType unless it is error,  when we go bat crazy :)

I think #146 covers your asyncID concerns.
messageType may be overkill, but I'd like to give people the flexibility to produce meaningful log messages. HTTP status codes can only distinguish between error and success.
For example, a PUT request might return code 200, but you may want to include a INFO or WARNING message to the user that says "the ID was not found, therefore a new object was created".

Then this seems ok.

Getting in late but perhaps a consideration is whether we are only using
HTTP as the transport protocol or not.
Consider sending an instruction to someone via snail mail envelope. If the
instruction has an error you shouldn't get an error reported by the
delivery system.
Or the layers in ISO network protocols. Each wrapped protocol is opaque to
the wrapping protocol.
On Wed, 28 Feb. 2018, 00:56 Philip Glaser<EMAIL_ADDRESS>wrote:

From casual and impressionistic observation of several BRAPI
implementations, it seems that even when errors are reported in the status
collection of the meta data object, the http status code remains 200. It
has been suggested that the status code should be in the 500-and-above
series in these situations.
It has also been pointed out, on the other hand, that as long as the
server's response is intelligible as BRAPI response, even if that response
contains error messages, the status from the http point of view should
remain 200.
One way or another, the API spec should define the standard practice.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/plantbreeding/API/issues/210, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQIYCRmU2IlGTPPBJA9IB9MpHzXOXWNks5tZDOygaJpZM4SVSPV
.

If anyone intends to use a different transfer protocol, I'd be happy to work with them to adapt the BrAPI specifications, BUT BrAPI is built on the assumption that you are using HTTP. I don't think it is productive to question that assumption unless there is a real need to do so.
Using HTTP error codes is an accepted best practice in the RESTful web service community. To continue your snail mail analogy, imagine if the post office provided a form letter with a checkbox for the reason you didn't accept the letter. Every sender (client) already knows what that form letter means and how to handle it, coming from any receiver (server). I'm stretching the metaphor a bit now, but the point is the HTTP status codes provide an established ontology for handling most errors.

I wasn't suggesting that we should change the transport protocol !
As a consumer of APIs what i like to have is the situation where when I get
an error response i can figure out what had gone wrong.
This is not always the case when HTTP error codes are used for errors in
the wrapped request.
When that happens a developer can waste valuable time.
On Wed, 10 Oct. 2018, 22:17 Peter Selby<EMAIL_ADDRESS>wrote:

If anyone intends to use a different transfer protocol, I'd be happy to
work with them to adapt the BrAPI specifications, BUT BrAPI is built on the
assumption that you are using HTTP. I don't think it is productive to
question that assumption unless there is a real need to do so.
Using HTTP error codes is an accepted best practice in the RESTful web
service community. To continue your snail mail analogy, imagine if the post
office provided a form letter with a checkbox for the reason you didn't
accept the letter. Every sender (client) already knows what that form
letter means and how to handle it, coming from any receiver (server). I'm
stretching the metaphor a bit now, but the point is the HTTP status codes
provide an established ontology for handling most errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/plantbreeding/API/issues/210#issuecomment-428589507,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQIYBasYEbASwH8xf2bRCb2oKBJRoBwks5ujgFagaJpZM4SVSPV
.


Added HTTP/2 and a new TLS engine - Botan

This is a targeted pull for http2-botan branch of the pull request at https://github.com/rejectedsoftware/vibe.d/pull/1081
I read the review and made a few corrections and will keep doing so as long as I see them coming. Since this is a pretty big project (> 115k LOC incl. libasync, botan, libhttp2, memtuils), some of those bugs may take roots deeper into dmd/dub/druntime/etc, for example

The use of 32mscoff configuration is necessary on win32 because -m32mscoff doesn't propagate and dub doesn't have a --arch=x86coff option. Also, the dub fetch packages don't seem to generate the dub files correctly so the repositories need to be cloned and the dependency "path"s manually adjusted.
This branch is also not compatible with DMD < 2.067.1 on windows because of the amount of symbols, I implemented COFF Big Tables in DMD for this reason.
This is not compatible with DMD < 2.067.0 because Botan uses the asm pure attributes
The LDC/GDC compilers are thus not compatible because they haven't reached 2.067 yet and don't seem to be able to ignore the DMD-specific code
It also requires DMD64 when building win64 because it uses too much ram to compile.
The linker for posix is very slow (>13 seconds) unless you use the Gold linker (~2 seconds) because of the amount of symbols.

I added appropriate error messages where possible. I think everything runs very stable right now nonetheless once you have the platform correctly setup

Thanks a lot for pushing this forward.
I'll try to review stuff here frequently, and we'll see if we can integrate it step by step into master.

Thanks a lot for pushing this forward.
I'll try to review stuff here frequently, and we'll see if we can integrate it step by step into master.

My pleasure (I needed it). vibe.d will be an absolute powerhouse in terms of web development with this. I still wish there were more native libraries (dns resolvers, distributed balancers, ssh, git, etc) but I think this will give us an edge over other libraries, whereas it could show off the low-level & high-level combined abilities of the platform to help convince some highly skilled contributors to hop on eventually.

Since this is too big for a meaningful review, I'll pull as it is now and then move things bit by bit into master until nothing is left (I'll try to let this be the main focus of my work next week).

Thanks! And I hope you'll like it. I'm going to be concentrating more on vibe.d because I need more features related to it in my developments now, e.g. I'll need to implement the HTTPClient.writePart method this week

A question regarding licensing: Usually all contributions have to be made under the rejectedsoftware copyright as noted in the contribution guidelines. But they definitely have to be MIT licensed and they definitely may not violate any external license terms. Since some of the code looks like it's ported from C++ and copyright/license notes are missing for new files (cookiejar and http2), this still needs some clarification.

Since some of the code looks like it's ported from C++ and copyright/license notes are missing for new files (cookiejar and http2), this still needs some clarification.

The http2.d file was completely written from scratch and I'm licensing it MIT
The cookiejar.d file was completely written from scratch except for the date parsing, which was heavily inspired by: https://github.com/icefox/parse_cookie_date - The Nokia license doesn't apply here because nothing from Qt was used so I removed it. But the original author licensed it 3-BSD which is why I tried to rewrite it as differently as possible. If I infringed on anything I might as well start over, right?

Can you make a quick pull adding the module headers to the http2-botan branch? I'd say the date parsing code should better be rewritten (that was actually also what I was looking at when referring to ported code).  I'll just keep it in mind for now though, no need for action before the code is ready to be pulled into master.

I'll just keep it in mind for now though, no need for action before the code is ready to be pulled into master.

What about dependencies though? The libhttp2 library has MIT but with a clause from curl license. Can vibe.d rely on that kind of dependency or should it be removable through versioning?

Should be fine. Only GPL and similar licenses have additional restrictions on dependent code. It's just that their license terms will apply to any compiled software (e.g. if there is a clause that dictates showing the copyright string(s) in the final application).

So I might as well move the cookie date parser to libhttp2 ?

Yeah, that would just mean that you'll get a mixed license library. Since it's also used for HTTP/1.x, libhttp2 doesn't seem to be the most fitting place though. But let's wait with that until things are close to getting merged. The HTTP2 code could even be merged before the cookie code.

The HTTP2 code could even be merged before the cookie code.

A nice ordering I think would be :
semaphore, libasync fixes, client refactoring & features, server refactoring & features, botan, waitLocal, http/2, cookie jar
The memutils library is mixed license though, you have the secure pool there that is 2-BSD under Botan license but it's really important for the flow of data. It maps to a memory region that doesn't ever touch peristent memory on any occasion.

I'm currently undoing as much of the refactorings and optimizations in the HTTP client/server as possible. Otherwise it won't be possible to merge the HTTP/2 additions at all (usually the whole PR would have had zero chances of being merged due to its size and due to mixing so many things, but in this case it would be a shame). waitLocal is removed, too, I think we need a solution that is implemented as an optimization under the hood instead. But otherwise I'd chose the same order.
I'll get back with a list of all things that I've removed/reverted when I'm ready, so that we can go through them one by one to see what makes sense to be put back and in which form.

A lot of the refactoring was necessary from my perspective. Are you sure its going to be possible to remove it?

Quoting some further fixes that need to be applied to the http2 branch:

The outputStream can be null in which case the freeing shouldn't happen and the streams are still flushed (currently this fails the assertion): if (!outputStream) skip freeing
The outputStream doesn't necessarily exist when writing headers (the current code may trigger a segfault): should be StreamOutputRange(topStream)
The libasync driver has an assertion that slows everything down a lot when many writes are involved: should be removed
The libasync AsyncFile was sluggish for large files which is fixed in 0.7.4 (I tagged it just now).

A lot of the refactoring was necessary from my perspective. Are you sure its going to be possible to remove it?

Some of it seems to be removable without any issues. Other things may have a performance/memory impact. Maybe others are necessary in a more fundamental way, but I'll have to get everything to a point where the actual changes are small enough to keep a mental model of them. When everything is done so far, the refactorings can be discussed one-by-one and possibly added back (or maybe a suitable alternative).
But using it as-is would basically mean that the previously tested implementation gets swapped by an almost completely new implementation that could introduce any number of bugs that are more or less impossible to detect by pure inspection. Since there is no serious HTTP protocol test coverage, this is really not an option at this stage.

Since there is no serious HTTP protocol test coverage, this is really not an option at this stage.

I'd really like to have some more high-level tests. ie. phantomjs with a vibe.d proxy - so that some dynamic websites with real json events can be tested through the vibe.d server using a browser and http/2 multiplexing enabled/disabled in the proxy.