Google Vulnerability Report: insecure URI handling scheme

Remove the URI scheme for performing VM operations because they can be triggered from the web browser.

Kind of unfortunate to see this removed, given there's no AppleScript on iOS. This also breaks some of my Shortcuts which control UTM using the URL scheme. Maybe I can look into adding Shortcuts-API-based automation.

Maybe we should implement a new API in iOS just for shortcuts. You want to open a new issue for that? The problem with the URL scheme is there's no way to authenticate the actions.

I opened #6245 about Shortcuts support.


Book store setup

create the bookstore set up:

create the bookstore for mobile and desktop screen
use min-width for responsiveness
create the bookstore pages (books and categories)
create the navbar
A form to add books
React hook to manage state (useState)

Thank you for
The review


Documentation issue

Here it says as follows:
Raven.configure do |config|
  config.sanitize_data_for_request_methods = %w(PATCH) # Only send data for PATCH request method
  # config.processors -= [Raven::Processor::RequestMethodData] # Do this to always send request data
  config.processors -= [Raven::Processor::Cookies] # Do this to send cookies by default
end

Several issues:

afaict Raven::Processor::RequestMethodData is only a recent addition and is not available in any released gem yet
it's missing a require 'raven/processor/request_method_data' line
it says # Only send data for PATCH request method but don't you mean # Only NOT send data for PATCH request method?
why is removestacktrace in one word, but request_method_date with underscores? Consistency would be nice to discover these undocumented (or poorly documented) features, you'd never know you'd have to require request_method_data for to be able to use this processor, not requestmethoddata.

afaict Raven::Processor::RequestMethodData is only a recent addition and is not available in any released gem yet

Sorry, that's been raised before. Unfortunately the published docs always reflect master, not the latest release. We're working on a better process for this.

it's missing a require 'raven/processor/request_method_data' line

No, it isn't - that is required for you by Raven. I think you're confused because of the RemoveStacktrace example above it - that processor is not required by default so you do have to require it yourself. It's worth noting that this is intentionally hard to use because removing stacktraces from Events makes Sentry half as useful, so we want to make sure You Are Completely Sure You Want To Do This.

it says # Only send data for PATCH request method but don't you mean # Only NOT send data for PATCH request method?

Yeah that's wrong. Fixed. Made it clearer in configuration.rb too.

why is removestacktrace in one word, but request_method_date with underscores?

You know, I never even noticed our filenames were inconsistent 😆 I can fix that and deprecate the old names.

Sweet, thanks for clearing this up! 👍 If not required anymore than the consistency is not that big of an issue, but it sure looks weird ;-)


WIP: Allow customisation of kubenetwork

Split out from https://github.com/stackhpc/magnum-capi-helm/pull/23
Should be updated to include relevant label or config values before submitting.

Closing, until this is needed. It can stay in the Helm Chart for now.


Fix: Implement retries in StopBizTalkHost.vbs like in BounceBizTalkHost.vbs

Sometimes the Stop method on the BizTalk host instance WMI object fails for an obscure reason (at least obscure for me). This seems to be taken into account in BounceBizTalkHost.vbs through implementation of retries (5) in a loop. However, this is done in StopBizTalkHost.vbs, and makes the deployment fail when Stop fail. Simply retrying the command in a loop like in BounceBizTalkHost.vbs works.
This work item was migrated from CodePlex
CodePlex work item ID: '8318'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@6/19/2011]
Resolved with changeset 59700.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


docs: fix typo in migration guide

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Admin commands for resources?

Hello,
is there a way for an admin to add resources like supplies, ammunition and fuel for the FOB? Either by a command, air-drop or something similar?
Thank you in advance.

Are there any commands that work? These do not.

I found that commands have changed, look here: https://github.com/KillahPotatoes/KP-Liberation/wiki/EN_Commands


Flow for RN doesn't resolve ".ios" / ".android" dependencies correctly

Small bug here. If I have a file with name "SOMETHING.ios.js" and import it like
import SOMETHING from './src/components/SOMETHING'

Flow gives me the following error
./src/components/SOMETHING: ~/dev/macaron/index.ios.js:165
Required module not found

The apps works perfect.
I'm using
"dependencies": {
  "react": "^0.14.7",
  "react-native": "^0.23.1"
},
"devDependencies": {
  "flow-bin": "^0.22.1"
}

Hello
I don't think you need to specifiy .ios (or .android) when requiring a module. React Native should resolve this for you depending on the platform it runs on. See https://github.com/fbsamples/f8app and the use of F8TabsView for example : https://github.com/fbsamples/f8app/search?utf8=✓&q=F8TabsView&type=Code

@abalhier, i know i don't need to specify .ios (or android) when requiring a module, but flow gives me an error (it can find the module). it doesn't have the logic to look for .ios / .android suffixes.

Worse than this, the flow errors only show for files with an ios extension. The same code with an android.js extension doesn't show any flow errors.

duplicate of #945


Add stats

Contributes to #26. This collects city statistics like presets count, tag coverage, etc. The stack now requires a PostgreSQL database. Some refactor was done in the CLI.

Changes:

Monorepo setup improved
Removed 'reset-git-remote' in favor of property '--overwrite' in the update task
Better support from Github

To do:

[ ] Forbid '--overwrite' with '--recursive'
[ ] Add confirmation of '--overwrite', display target git URL
[ ] Improve country page
[ ] Add home content

This Prisma issue was solved and Next.js website with stats is set up.


Experiencing endless Amazon-Captchas while trying to install integration

Describe the bug
Experiencing endless Amazon-Captchas while trying to install integration
To Reproduce

Go to Home Assistant / Settings / Devices & Services
Click on "Add Integration"
Search for Alexa Media Player
Fill in Amazon eMail address, Amazon password, adjust Amazon region to amazon.de, put in HA URL starting with https://..., put in 2FA-Code from Amazon
Press "Submit"
Enter OTP at Amazon, see number of authentification devices increasing by 1
In HA check the box saying that the OTP has been entered, submit
Get redirected to Amazon Captcha-Page
After correctly entering the captcha I get another (URL then includes an "/error/") and another and another captcha, etc. (I stopped after about 20 inputs)

(tried this in Edge, Edge incognito mode, Chrome, Chrome incognito mode and with different IP addresses)
Expected behavior
Integration appearing under installed integrations
System details

Home-assistant (version): Core 2023.11.0 / Supervisor 2023.10.1 / Operating System 11.1 / Frontend 20231030.1
alexa_media (version from const.py or HA startup): ?
alexapy (version from pip show alexapy or HA startup): ?
Amazon [2FA is enabled]: y

Logs
Please provide logs.
Unable due to integration not installing
Additional context
Login into Amazon and Alexa App is possible without problems
Would be very thankful for any help!!

Please provide logs per the logs instruction via editing configuration.yaml.

Same here. Endless captcha requests. Core 2023.11.0, all updates installed.

Besides the domain, are you doing anything that rewrites your HA path?

If you man something like a reverse proxy, than no. I'm using the lets encrypt addon to secure the connection and thats it.
When I look at the log, only a connection to amazon.com is established, but not to amazon.de. Does this play a role at this point or is it intended that way?

I'm experiencing exactly the same, also with amazon.de; using nabu casa to access homeassistant from "outside". I always end up on this screen, in an endless loop of recaptcha.

I read somewhere that amazon did shut down alexa for web recently, maybe that is related?

Same here this morning, an endless loop of captcha requests, exactly as mentioned above.

Same problem with amozon.it

Same 🫤

Confirmed having the same issue when registering AMP with Captcha requests

Same Problem at here

I for the moment solved it this way while waiting for an update.
I modified in the config_flow.py file present in the /custom_components/alexa_media/ folder the strings with "amazon.com" with the store of my appearance in my case "amazon.it" there are 3 of them (line: 116, 158 and 758). I have saved restarted HA logging in again everything went correctly.

@sixdas , great find, this worked for me too :-)

@sixdas: seems not to work for Germany (amazon.de)

I can agree with that. It doesn't seem to help in Germany. I have tried both variant. (.de and .it). If i use the URL (the original one, without the proxy, it redirect my browser to a 404 Page.

Me too posts are not helpful. Use +1 on the relevant post instead.
Changing the domain may or may not avoid the Captcha request Amazon is generating. You can try it, but it'll work until Amazon decides to give you a captcha.
Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.
Logs showing the urls being generated help the most because we can see if Amazon is taking you to a new set of pages. The auth capture proxy has a test to detect when you've successfully logged in. If Amazon takes you to a new set of pages, we can't detect it.

For reference, here is an example of a functioning captcha path which I can force by choosing a non-default domain (.de vs my .com).
alexalogincaptcha.log
The key point is
2023-11-06 03:51:46.015 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/alexamedia/proxy/errors/validateCaptcha to <IP_ADDRESS> (auth: False)
2023-11-06 03:51:46.015 DEBUG (MainThread) [authcaptureproxy.auth_capture_proxy] Received get: http://localhost:8123/auth/alexamedia/proxy/errors/validateCaptcha?amzn=qqvGp88Bkip%2FKYJIXbPSVg%3D%3D&amzn-r=%2Fap%2Fsignin%3Fopenid.return_to%3Dhttps%3A%2F%2Fwww.amazon.com%2Fap%2Fmaplanding%26openid.assoc_handle%3Damzn_dp_project_dee_ios%26openid.identity%3Dhttp%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select%26pageId%3Damzn_dp_project_dee_ios%26accountStatusPolicy%3DP1%26openid.claimed_id%3Dhttp%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select%26openid.mode%3Dcheckid_setup%26openid.ns.oa2%3Dhttp%3A%2F%2Fwww.amazon.com%2Fap%2Fext%2Foauth%2F2%26openid.oa2.client_id%3Ddevice%3A623731363964653561326132303964633366616164633565363266383138336632333431333234393536346335363335353634643332353733383331%26openid.ns.pape%3Dhttp%3A%2F%2Fspecs.openid.net%2Fextensions%2Fpape%2F1.0%26openid.oa2.response_type%3Dcode%26openid.ns%3Dhttp%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%26openid.pape.max_auth_age%3D0%26openid.oa2.scope%3Ddevice_auth_access%26openid.oa2.code_challenge_method%3DS256%26openid.oa2.code_challenge%3DWuV7-aRufazwcnxdAfcVL47btWENWhKqJjVSxSFW9Mk%26language%3Dde_DE&amzn-pt=AuthenticationPortal&field-keywords=jbnnem for https://www.amazon.com/ap/signin?openid.return_to=https://www.amazon.com/ap/maplanding&openid.assoc_handle=amzn_dp_project_dee_ios&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&pageId=amzn_dp_project_dee_ios&accountStatusPolicy=P1&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns.oa2=http://www.amazon.com/ap/ext/oauth/2&openid.oa2.client_id=device:623731363964653561326132303964633366616164633565363266383138336632333431333234393536346335363335353634643332353733383331&openid.ns.pape=http://specs.openid.net/extensions/pape/1.0&openid.oa2.response_type=code&openid.ns=http://specs.openid.net/auth/2.0&openid.pape.max_auth_age=0&openid.oa2.scope=device_auth_access&openid.oa2.code_challenge_method=S256&openid.oa2.code_challenge=WuV7-aRufazwcnxdAfcVL47btWENWhKqJjVSxSFW9Mk&language=de_DE
2023-11-06 03:51:46.016 DEBUG (MainThread) [authcaptureproxy.auth_capture_proxy] Final headers {'Connection': 'keep-alive', 'sec-ch-ua': '"Google Chrome";v="119", "Chromium";v="119", "Not?A_Brand";v="24"', 'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7', 'DNT': '1', 'sec-ch-ua-mobile': '?0', 'Upgrade-Insecure-Requests': '1', 'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36', 'sec-ch-ua-platform': '"macOS"', 'Sec-Fetch-Site': 'same-origin', 'Sec-Fetch-Mode': 'navigate', 'Sec-Fetch-Dest': 'empty', 'Accept-Encoding': 'gzip, deflate, br', 'Accept-Language': 'en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7,ja;q=0.6,mt;q=0.5'}
2023-11-06 03:51:46.016 DEBUG (MainThread) [authcaptureproxy.auth_capture_proxy] Attempting get to https://www.amazon.com/errors/validateCaptcha?amzn=qqvGp88Bkip/KYJIXbPSVg%3D%3D&amzn-r=/ap/signin?openid.return_to%3Dhttps://www.amazon.com/ap/maplanding%26openid.assoc_handle%3Damzn_dp_project_dee_ios%26openid.identity%3Dhttp://specs.openid.net/auth/2.0/identifier_select%26pageId%3Damzn_dp_project_dee_ios%26accountStatusPolicy%3DP1%26openid.claimed_id%3Dhttp://specs.openid.net/auth/2.0/identifier_select%26openid.mode%3Dcheckid_setup%26openid.ns.oa2%3Dhttp://www.amazon.com/ap/ext/oauth/2%26openid.oa2.client_id%3Ddevice:623731363964653561326132303964633366616164633565363266383138336632333431333234393536346335363335353634643332353733383331%26openid.ns.pape%3Dhttp://specs.openid.net/extensions/pape/1.0%26openid.oa2.response_type%3Dcode%26openid.ns%3Dhttp://specs.openid.net/auth/2.0%26openid.pape.max_auth_age%3D0%26openid.oa2.scope%3Ddevice_auth_access%26openid.oa2.code_challenge_method%3DS256%26openid.oa2.code_challenge%3DWuV7-aRufazwcnxdAfcVL47btWENWhKqJjVSxSFW9Mk%26language%3Dde_DE&amzn-pt=AuthenticationPortal&field-keywords=jbnnem
headers: {'Connection': 'keep-alive', 'sec-ch-ua': '"Google Chrome";v="119", "Chromium";v="119", "Not?A_Brand";v="24"', 'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7', 'DNT': '1', 'sec-ch-ua-mobile': '?0', 'Upgrade-Insecure-Requests': '1', 'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36', 'sec-ch-ua-platform': '"macOS"', 'Sec-Fetch-Site': 'same-origin', 'Sec-Fetch-Mode': 'navigate', 'Sec-Fetch-Dest': 'empty', 'Accept-Encoding': 'gzip, deflate, br', 'Accept-Language': 'en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7,ja;q=0.6,mt;q=0.5'}
cookies: <CookieJar[]>
2023-11-06 03:51:46.472 DEBUG (MainThread) [authcaptureproxy.helper] GET: redirected from
https://www.amazon.com/errors/validateCaptcha?amzn=qqvGp88Bkip/KYJIXbPSVg%3D%3D&amzn-r=/ap/signin?openid.return_to%3Dhttps://www.amazon.com/ap/maplanding%26openid.assoc_handle%3Damzn_dp_project_dee_ios%26openid.identity%3Dhttp://specs.openid.net/auth/2.0/identifier_select%26pageId%3Damzn_dp_project_dee_ios%26accountStatusPolicy%3DP1%26openid.claimed_id%3Dhttp://specs.openid.net/auth/2.0/identifier_select%26openid.mode%3Dcheckid_setup%26openid.ns.oa2%3Dhttp://www.amazon.com/ap/ext/oauth/2%26openid.oa2.client_id%3Ddevice:623731363964653561326132303964633366616164633565363266383138336632333431333234393536346335363335353634643332353733383331%26openid.ns.pape%3Dhttp://specs.openid.net/extensions/pape/1.0%26openid.oa2.response_type%3Dcode%26openid.ns%3Dhttp://specs.openid.net/auth/2.0%26openid.pape.max_auth_age%3D0%26openid.oa2.scope%3Ddevice_auth_access%26openid.oa2.code_challenge_method%3DS256%26openid.oa2.code_challenge%3DWuV7-aRufazwcnxdAfcVL47btWENWhKqJjVSxSFW9Mk%26language%3Dde_DE&amzn-pt=AuthenticationPortal&field-keywords=jbnnem
2023-11-06 03:51:46.472 DEBUG (MainThread) [authcaptureproxy.helper] GET:
https://www.amazon.com/ap/signin?openid.return_to=https://www.amazon.com/ap/maplanding&openid.assoc_handle=amzn_dp_project_dee_ios&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&pageId=amzn_dp_project_dee_ios&accountStatusPolicy=P1&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns.oa2=http://www.amazon.com/ap/ext/oauth/2&openid.oa2.client_id=device:623731363964653561326132303964633366616164633565363266383138336632333431333234393536346335363335353634643332353733383331&openid.ns.pape=http://specs.openid.net/extensions/pape/1.0&openid.oa2.response_type=code&openid.ns=http://specs.openid.net/auth/2.0&openid.pape.max_auth_age=0&openid.oa2.scope=device_auth_access&openid.oa2.code_challenge_method=S256&openid.oa2.code_challenge=WuV7-aRufazwcnxdAfcVL47btWENWhKqJjVSxSFW9Mk&language=de_DE with
{"host": "www.amazon.com", "connection": "keep-alive", "sec-ch-ua": "\"Google Chrome\";v=\"119\", \"Chromium\";v=\"119\", \"Not?A_Brand\";v=\"24\"", "accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7", "dnt": "1", "sec-ch-ua-mobile": "?0", "upgrade-insecure-requests": "1", "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36", "sec-ch-ua-platform": "\"macOS\"", "sec-fetch-site": "same-origin", "sec-fetch-mode": "navigate", "sec-fetch-dest": "empty", "accept-encoding": "gzip, deflate, br", "accept-language": "en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7,ja;q=0.6,mt;q=0.5", "cookie": {"x-amz-captcha-1": "1699249906184068", "x-amz-captcha-2": "spkci0nrHAslG4p0B6tAWA=="}}
returned 200:OK with response Headers([('server', 'Server'), ('content-type', 'text/html;charset=UTF-8'), ('x-amz-rid', '6FENPTMRYADGR1QA4TYV'), ('x-xss-protection', '1'), ('x-content-type-options', 'nosniff'), ('x-ua-compatible', 'IE=edge'), ('pragma', 'No-cache'), ('cache-control', 'max-age=0, no-cache, no-store, must-revalidate'), ('expires', 'Thu, 01 Jan 1970 00:00:00 GMT'), ('strict-transport-security', 'max-age=47474747; includeSubDomains; preload'), ('vary', 'Content-Type,Accept-Encoding,User-Agent'), ('p3p', 'policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC "'), ('x-frame-options', 'SAMEORIGIN'), ('content-encoding', 'gzip'), ('date', 'Mon, 06 Nov 2023 03:51:46 GMT'), ('transfer-encoding', 'chunked'), ('connection', 'keep-alive'), ('connection', 'Transfer-Encoding'), ('set-cookie', 'ap-fid=""; Domain=.amazon.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ap/; Secure'), ('set-cookie', 'session-id=135-2588688-3322068; Domain=.amazon.com; Expires=Tue, 05-Nov-2024 03:51:46 GMT; Path=/; Secure'), ('set-cookie', 'session-id-time=2329962706l; Domain=.amazon.com; Expires=Tue, 05-Nov-2024 03:51:46 GMT; Path=/; Secure'), ('set-cookie', 'lc-main=de_DE; Domain=.amazon.com; Expires=Tue, 05-Nov-2024 03:51:46 GMT; Path=/; Secure'), ('alt-svc', 'h3=":443"; ma=93600'), ('x-amzn-cdn-id', 'ak-1a5022'), ('x-cache', 'NotCacheable from child')])

After sending a successful captcha, we get the redirect to the signin url https://www.amazon.com/ap/signin.

Same problem with amazon.it

I confirm the issue using the last release 4.7.9: no way to get it working.

Problem with Captcha always here also with 4.7.9 (amazon.de)

Same problem without any solution 👎🏻

One tip that worked for me: Disabled IPV6 stack on Homeassistant Network confiiguration..

Disabled IPv6 and it still persists for me.

Disabled IPv6 does Not make a change

Is there a solution ?

Please confirm you have 2FA enabled. That is required.

2FA is enabled.

2FA ist enabled and OTP is confirmed after opening the Popup there is coming the never ending Captcha journey

2FA is enabled.
I've download againg Alexa Media Player 4.7.9
Deleted the two .pikle files
Reboot HA
At the end of the setup, the process stops at the screen "Caricamento del passaggio successivo per Alexa Media Player" (I've waited minutes)

Is there a solution ?

One more the same. Catcha never end.

Hello,
I was able to sign in flawlessly 3 days ago but I had some issues and needed to reboot my entire system (hard reset everything). And now I'm trying to integrate everything again, I'm presented with this issue.
I was wondering if traces of my previous configuration is interfering with what I'm trying to do now.
I have installed Alexa Media Player 4.7.9.
I can't find logs.
My level of understanding about all this is like a baby knowing how to say 'mama'
Thanks for your time

same with me... will there be a solution or can we forget about it? it would be nice if the developer would get in touch instead of leaving us standing here in the dark!

Hello,
I did some YouTube research and stumbled on deleting traces of previous integration through WinSCP. Deleted my browser history twice. Restarted HA twice. Downloaded AMP and started it, refreshed my browser. Restarted HA twice, tried to integrate it, but still the same issue. I don't know any other work around because I don't understand codes, yet.
If someone can help us, please.
Additional info, I have the nabu casa cloud with Amazon and Google embedded.
Many thanks,
Kristine

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I'm not not going to look at this thread anymore.

🤣🤣🤣

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I'm not not going to look at this thread anymore.

please don't listen to this comment :) you are doing a great job :) I would love to try this integration, but i also know that this integration is not your "reason to live" and I'am sure you have so much more to do in your free time than read comments like the one above and feel forced to find a fix for something, but please don't let one "lost soul" be the reason to be mad a some users :)

SAme experiences here, no way to get it work:(

Please confirm you have 2FA enabled. That is required.

Can you please let me know if that’s 2FA on the Amazon account or 2FA for login to HA. Thanks loads, and for your work.

Please try to ignore the disparaging comments - we are all very grateful for the work you put in to keep this integration going!

Latest Alexa Media Player 4.7.9 component installed. AZ 2FA enabled as described. Logged in HA with private domain URL via Cloudflare or alternatively locally. AZ domain is amazon.de. Anything strictly according to instructions. Several restarts of HA and reinstallation of Alexa Media Player component.
AZ Captcha of death still appears!
Any further ideas? Or is it completely dependent from AZ, so nothing can be done to avoid it?
I understand that this piece of software is a private gift to all the other users and for sure everybody who wants to use it, is thankful!
And I will wait with patience to get an answer or any new hints. But at the same time, when I read the comments, I got the feeling that this problem is not taken seriously because it cannot be reproduced. Maybe there is an example of a functioning captcha path which "alandste" can force by choosing a non-default domain (.de vs my .com). But it doesn't work here.
Here is the excerpt of my HA log (HA Alexa Media Player component debug mode)
home-assistant.log

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I'm not not going to look at this thread anymore.

Have some alternative attitude. I enabled 2FA on HA as suggested and it worked. It did a 404 captcha failure and then I tried again and it was fine. The key seems to be ensuring that the 2FA code matched that from Authy before logging in. Thankyou so much for your efforts and help on this. I'm a dev too (commercial) and know what it's like when your work isn't appreciated. Thanks again and have a virtual beer on me.

3. Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks!
Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I'm not not going to look at this thread anymore.

Have some alternative attitude. I enabled 2FA on HA as suggested and it worked. It did a 404 captcha failure and then I tried again and it was fine. The key seems to be ensuring that the 2FA code matched that from Authy before logging in. Thankyou so much for your efforts and help on this. I'm a dev too (commercial) and know what it's like when your work isn't appreciated. Thanks again and have a virtual beer on me.

Which Amazon domain did you use?

Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

When you submit it should get you to the alexa login site. and after you log in is when the captcha comes up.
submit once. if it gives you an extra captcha, go back to the login screen. and then you start logging in and going back until no captcha is requested.

Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

When you submit it should get you to the alexa login site. and after you log in is when the captcha comes up. submit once. if it gives you an extra captcha, go back to the login screen. and then you start logging in and going back until no captcha is requested.

Unfortunately, this approach doesn't work for me either. However, after submitting I go straight to the CAPTCHA. Frustrating

Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

When you submit it should get you to the alexa login site. and after you log in is when the captcha comes up. submit once. if it gives you an extra captcha, go back to the login screen. and then you start logging in and going back until no captcha is requested.

When I click submit, it never brings me to the Alexa Login site, independently if I am logged-in in my Amazon Account or not. It brings me ALWAYS directly to this captcha site. I tried it out many times. Maybe there is an issue with our german Alexa Login site. As far as I know, since quite a while, there is no german Alexa Login site anymore. They canceled it maybe 6 to 10 months ago. When I want to Log-In to Alexa account in any browser a QR code appears which is for bringing me to my Alexa App on my phone. You can check it: https://alexa.amazon.de/

Same here with amazon.de (Germany):
No matter which variant I choose, I cannot bring it up to be working...
NOT for the amazon.de
NOT for the amazon.com
NOT with clicking-"back"-approach (neither .de nor .com)
😣

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I'm not not going to look at this thread anymore.

Have some alternative attitude. I enabled 2FA on HA as suggested and it worked. It did a 404 captcha failure and then I tried again and it was fine. The key seems to be ensuring that the 2FA code matched that from Authy before logging in. Thankyou so much for your efforts and help on this. I'm a dev too (commercial) and know what it's like when your work isn't appreciated. Thanks again and have a virtual beer on me.

Which Amazon domain did you use?

.co.uk

Given this attitude, I'm not not going to look at this thread anymore.

sorry but making everyone suffer for one statement shows what a very bad character you have, it's just a cheap excuse because you don't feel like it or can't manage it, nothing more and nothing less

same issue with .es domain

@alandtse Hello!
Are you really not looking into this because of one person not hitting the right tone?
I am following this thread and affected users are increasing steadily, it seems.
Are there any contributors who might be willing to inspect?
I am new to ha and this is not my stack so it seems tough to onboard and search for a solution but I might consider if you really are not interested in investigating?
Please let us know!
Best, H

I am willing to give a hand where possible. I am a Javascript developer primarily but happy to assist wherever I can.

I am facing the same issue. Any work around?

I am facing the same issue. Any workaround?

Have you made sure that you have 2FA turned on for your HA login? Done through the user menu in HA. When you register for 2FA on the screen in HA there is a long code under the QR code. I forget what this was called. Take a note of it - I’ll call it the 2FA main code. If goes in the entry when configuring where is says “this is not 6 digits”
I removed the custom component. Turned on 2FA. Re-installed the custom component. Added it to the integrations. Entering all the details including the domain for amazon as .co.uk (where I registered my amazon account) and the 2FA main code. I got a screen pop up showing the 2FA code as incorrect. So I re-did the process. This produced a correct 2FA code and I could finish installing. I think there is possibly a lag that means the 2FA code can be out of date when produced.
I’m up later than I should be typing this but I hope it makes sense.

Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

Can confirm this worked for me as well. I entered a few of the Captcha's in a row, hit back in my browser like 10 times. Then I refreshed the page continuously (who knows, like 20 times) until the Captcha disappeared end the Amazon login screen appeared.

Doesnt work for me, amazon.de, too bad!

Doesnt work for me, amazon.de, too bad!

same here.. tryed refreshing and getting to the alexa login page. If i log in.. i get back to the captcha loop.
amazon.de

me too :)

Have the same Problem at amazon.de
All mentioned Workarrounds did not work.

Have the same Problem at amazon.de
All mentioned Workarrounds did not work.

same here

Hello! Mine is finally working! I was so ready for the battle but I wasn't even presented with one captcha!
I left it for a while, maybe 8 days, when the workaround (shown at the bottom) didn't push through. One thing that is different is that I'm using a different device when it worked. I was previously using my desktop and now I'm using a laptop. I don't know if that makes it any different but it worked!

Hello,
I did some YouTube research and stumbled on deleting traces of previous integration through WinSCP. Deleted my browser history twice. Restarted HA twice. Downloaded AMP and started it, refreshed my browser. Restarted HA twice, tried to integrate it, but still the same issue. I don't know any other work around because I don't understand codes, yet.
If someone can help us, please.
Additional info, I have the nabu casa cloud with Amazon and Google embedded.
Many thanks, Kristine

Given this attitude, I'm not not going to look at this thread anymore.

Most of us appreciate your work.  But this is a bullshit, immature and irresponsible response.

Try to add the "Alxa Media Player" Integration in the App on your Smartphone, not in the Browser.
Thats the way it worked in my case. Maybe its a workaround.

Given this attitude, I'm not not going to look at this thread anymore.

This is an immature and irresponsible response, it's clear you cannot work with a community.

But I don't think requesting for this integration to be removed is the solution because it's working for some people. And maybe that was just an initial response because the latter comment was really insensitive and wasn't thought of, too.

Try to add the "Alexa Media Player" Integration in the HA App on your Smartphone, not in the Browser. Thats the way it worked in my case. Maybe its a workaround.

I tried it on my smartphone in the app and in the mobile browser, as well as via various browsers on the desktop. Unfortunately, it didn't work in any of the variants.
For the people for whom a workaround works, it would be helpful to know from which country they are trying it and with which amazon domain.

I did it in a second test. I tried it with my Macbook and Safari on the first try!

I just realised that it does not matter what I enter into the setup.
Can be completely random.
I always get sent to the nabucasa url displaying the Amazon captchas.

Given this attitude, I'm not not going to look at this thread anymore.

This is an immature and irresponsible response, it's clear you cannot work with a community.

he's probably just using it as an excuse because he's not able to fix the bug or just doesn't feel like it anymore, then it should be maintained by other developers as well

he's probably just using it as an excuse because he's not able to fix the bug or just doesn't feel like it anymore, then it should be maintained by other developers as well

@Doldak Feel free to fix the issue and to send à pull Request, if you can do it better.

Given this attitude, I'm not not going to look at this thread anymore.

This is an immature and irresponsible response, it's clear you cannot work with a community.

he's probably just using it as an excuse because he's not able to fix the bug or just doesn't feel like it anymore, then it should be maintained by other developers as well

Hello sir,
You clearly needed attention and you have many things to say. Unfortunately, in my honest opinion, your 'many things to say' are rude, off putting, and impolite, to say the least. I hope you get the attention that you need to choose better words to become a helpful member of the society. Cheers.

Una vez me salieron los captchas, pulse varias veces f5 y al final entro en login

This is not an Amazon hosted website.
The links go nowhere, the copyright is 2006-2014 and the domain is nabucasa.
This looks a lot like someone is stealing passwords?
Through the 2fa the risk increases strongly.
I dont know it this is the case but I suggest to log out everywhere and change the password everyone.

I did it in a second test. I tried it with my Macbook and Safari on the first try!

Confirmed this worked for me too. Had failed repeatedley over the past two weeks on my Windows 10 desktop using Firefox, and also failed on iPhone (following some advice above), but pulled my old Macbook out of the drawer and it worked first time. Macbook Pro running MacOS Big Sur 11.7.3 and Safari 16.3, if that helps anyone else.

I does it with my Handy and the HA-App. All worked fine and i am logged in :) And thank you for your work and time on this great integration.

I does it with my Handy and the HA-App. All worked fine and i am logged in :) And thank you for your work and time on this great integration.

Which Smartphone do you use?

I does it with my Handy and the HA-App. All worked fine and i am logged in :) And thank you for your work and time on this great integration.

Which Smartphone do you use?

I use Oppo Find X5 Pro with Android and Chrome-Browser

Same problem here :/
Using working 2FA-Code & my nabu casa url

Thanks, labaland! I tried Edge too, and it worked - don't know whether this is reproducible, since I had tried Firefox, Chrome, and the local browser on my phone before and none of those did the trick. Location is Germany, if anyone else wants to try this.

Yes, with Smartphone App works! Here Apple iOS!
Great!

success with android APP

Danke, labaland! Ich habe es auch mit Edge versucht und es hat funktioniert. Ich weiß nicht, ob das reproduzierbar ist, da ich Firefox, Chrome und den lokalen Browser auf meinem Telefon bereits ausprobiert hatte und keiner davon geholfen hat. Standort ist Deutschland, falls das noch jemand ausprobieren möchte.

That`s it. With Edge it works! Thanks.

After a very lot of different captcha Problems with different Browsers and configurations i was able to install the Integration with the HA App on my iPad. With this machine i had also a lot of unsuccessful attempts.
at the moment it is working for me

work with edge

Okay, it worked for me too. iPhone 12 with Standard Safari Browser and Amazon App. It worked immediately.
But I am sorry, that "Alan Tse" doesn't look at this thread anymore. So he is not able to share the joy with us! And even if he reads all this silently, I guess he will not tell us?!
Don't waste your time with anger everybody out there! Peace!

I dont think it works browser-related.
Amazon may have had and fixed an issue?

It works again on my end; using the same browser I've used for all the failed attempts before.

Following the wiki instructions, https://github.com/custom-components/alexa_media_player/wiki/Configuration#installation-and-configuration. I used my local HA URL as suggested in the notes. "http://<IP_ADDRESS>:8123"
While reading these instructions, I was also watching: https://www.youtube.com/watch?v=UsnhL2z_UUY
Where I followed a long with Mark's comments.
When presented with the "orange" captcha, I was going round in loops, like everyone here.

I got fed up and in my frustration, I mashed the refresh button on the page.
At which point I was presented with a "blue" login.
Once logged in, I got a "blue" OTP prompt which I used my mobile auth app.
All was good at this point.
Once its all setup and working, I found in "Integration entries" configure for the Alexa Integration.
Here I found it was asking for the "public URL" for HA. I am not sure if this was required,

Worked for me in edge. Had to refresh login a few times, but than worked fine; amazon.de. Great experience:D

Is last_called_summary back again?

Obviously, Amazon did fix something in the login procedure.
I did try just the same as before, using Edge on Win11, and now it immediately worked with .de (Germany) domain just out-of-the-box without any hassles.
Great to see it working now!

It's working for me. After 3 weeks of testing, today Amazon changed something and now it's working for amazon.de

Obviously, Amazon did fix something in the login procedure. I did try just the same as before, using Edge on Win11, and now it immediately worked with .de (Germany) domain just out-of-the-box without any hassles and no captchas at all anymore.
Great to see it working now!

worked in Firefox on Win10 as well after 3 attempts. I just had the annoying captcha again, but after closing the tab and opening again from the integration i could simply log in..

Finally! It's working for me.
 "Preferences" -> "Security" -> "Enable 2FA" (info) that's mandatory.
Open Microsoft Edge (In my case in Mac OS Sonoma). I tried in Safari/Chrome/Firefox and not worked for me.
Go to Home Assistant (your url) -> Settings -> Integrations -> Devices & services -> "Add integration" -> Search "Alexa media player"
Complete form info:

Write your email and password  (Amazon Account)
Write your region (In my case "amazon.es")
Write your 2FA App Key (You need complete this steps to get your 2FA App Key)

Click "Submit" -> Sign in Amazon login (Blue login) -> Confirm your code (auto filled) in new screen (Blue Alexa screen)

I hope you find it helpful.
Thanks a lot!

luckily we didn't need the arrogant developer and amazon fixed it themselves, great!

I'm still unable to make it work :(
Tried .com, .it and .de, on Edge/Chrome on Windows PC, Chrome for Linux and Android, to no avail.

Hi Folks, Here was my fix:
I switched to edge.
The Prep:
-> I was previously using a port trigger to flip the url from externaleurl.com:8321 to externaleurl.com:8123 via a Ubiquity UDM Pro router.
-> I changed the port forward to have matching internal and external ports.
I logged into my HA GUI via a loopback of the external URL (mydynamicname.externalurl.com:8123)
I then updated the settings in HA, to reflect the new external domain name and port.
The Setup
Start to add the integration from the edge browser logged into the external HA.
Input all of the requested info including the 2fa code.
Now rather then a loop or a black 404 screen, you should get a blue amazon login.
the login should work, a new type of fuzzy looking captcha should display, and after you fill it out correctly, the integration should complete and you will be presented with a question about where each of the devices are located.
I hope this helps.
Canada user (amazon.ca) but you may be able to get it to work by leaving the domain as amazon.com in the integration.
Cheers!

Since this appears resolved by Amazon, I'll close this out.

Same problem here :/ Using working 2FA-Code & my nabu casa url
** EDIT ** It did work when i tried to do it in another browser! i got it to work in Microsoft EDGE.

It also worked for me using Microsoft Edge. In Chrome and Mozilla the same problem.

Same as above - didn't work in Chrome but using MS Edge browser it worked ok


SwiftUi compatibility?

Hello,
pardon my ignorance, but can this library work on a SwiftUi project?
Does it require any kind of adaptation for SwiftUi?

@Brakkar I think this link may be helpful.

To represent UIKit views and view controllers in SwiftUI, you create types that conform to the UIViewRepresentable and UIViewControllerRepresentable protocols. Your custom types create and configure the UIKit types that they represent, while SwiftUI manages their life cycle and updates them when needed.

I haven't tried it yet. If it works please let me know. Thank you!


Publisher: Optional "This is not your fault" gif

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
The This is not your fault page in the publisher, is not but fun enough, so we need to enhance it with an optional gif from "Good Will Hunting".
https://tenor.com/en-GB/view/its-not-your-fault-supportive-crying-not-your-fault-gif-3707453
How would you imagine the implementation of the feature?
Some QT magic to include the GIF on the page. Setting for making it optional.
Obviously will get a copyright take down of the repository, but its worth it.
Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
No response
Additional context:
No response

Obviously will get a copyright take down of the repository, but its worth it.

After the OpenPype repository being taken down briefly due to someone sharing security details in a PR I'm not sure that's really worth it, hehe.
Anyway - I'd actually prefer the "It's not your fault" page to provide more details on the error instead of hiding it all away. The current design is a bit as if the user has no control whatsoever to fix it - which e.g. in the case of raised KnownPublishError might not necessarily be the case? Of course, we should make things crash less - but an extractor failing may just occur if we know what might have caused it. (E.g. artist being able to interrupt an export process in the DCC - which ironically is their fault!)

Nonetheless, being able to randomize throughout a bunch of gifs could be fun. Not sure if it's worth it - but fun, sure.
Could be more fun if it's gamification instead.  if it happened recently or "You must have missed me!" if it's been long. Ok, bad idea. 🤦

We've talked about this internally and think that this is not worth pursuing at the moment. Closing the issue


Highlight important parts in the code

Would it be possible to highlight the parts in the code that are being focussed on in the section?
A few times there is a lot of code including styles around the one or two lines of code that is being talked about. For example, in Rendering with ternary -
{subtitle ? (

{subtitle}

        ) : (

No subtitle

        )}

this is the part that should attract the reader's focus, but it blends in with 50 other lines of code.

This would be very helpful. It would go in the underlying project, react-native-web-player.
I can do this at some point, but in case somebody wants to take it, this is a good place to start: https://github.com/dabbott/react-native-web-player/blob/master/components/workspace/Workspace.js#L357. We would add something like a new selectedLines=[...] prop and a url param for it.


Fix a bug that capturing piece

How replicate an issue - Capturing each pieces by sequential

Pull Request Test Coverage Report for Build 87

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.301%

Totals

Change from base Build 86:
0.0%

Covered Lines:
266

Relevant Lines:
296

💛  - Coveralls


Toolset validation runs when not necessary

Related to #881, @brthor saw some problems running unit tests for an app that uses MSBuild's construction APIs, but doesn't run builds.
Ideally, we could disambiguate between scenarios: if the user is using our code but doesn't need a toolset, we shouldn't error that we can't find a valid toolset. But if they're starting a build, we need to whine when we can't find a copy of MSBuild.exe to start our multiproc build.

@rainersigwald any thoughts on when this will be fixed?

Team triage: we don't think this is worth the time.


[Feature]: Syncing PackageManagerTabs and Tabs Choices

What problem does this feature solve?
Users may want choices of the same kind of tabs to sync with each other when they choose from PackageManagerTabs.

Also for the Tabs Component, we can also do the same thing to sync tab choices
What does the proposed API look like?
E.g.: https://docusaurus.io/docs/markdown-features/tabs#syncing-tab-choices

FYI, Docusaurus stores the latest chosen tab in local storage.


Refactor MergeOperator

Codecov Report

Merging #422 (ffc6280) into main (7fa0404) will decrease coverage by 41.74%.
The diff coverage is 11.71%.

@@             Coverage Diff             @@
##             main     #422       +/-   ##
===========================================
- Coverage   90.44%   48.70%   -41.75%
===========================================
  Files          53       49        -4
  Lines        1801     1772       -29
  Branches      280      274        -6
===========================================
- Hits         1629      863      -766
- Misses        133      871      +738
+ Partials       39       38        -1

Impacted Files
Coverage Δ

src/astro/databases/google/bigquery.py
0.00% <0.00%> (-94.12%)
:arrow_down:

src/astro/databases/postgres.py
0.00% <0.00%> (-100.00%)
:arrow_down:

src/astro/databases/snowflake.py
0.00% <0.00%> (-96.88%)
:arrow_down:

src/astro/databases/sqlite.py
70.00% <23.07%> (-26.43%)
:arrow_down:

src/astro/sql/operators/merge.py
50.00% <46.66%> (-38.38%)
:arrow_down:

src/astro/databases/base.py
59.78% <66.66%> (-38.00%)
:arrow_down:

src/astro/constants.py
94.44% <100.00%> (+0.15%)
:arrow_up:

src/astro/sql/__init__.py
81.25% <100.00%> (-18.75%)
:arrow_down:

... and 38 more

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 7fa0404...ffc6280. Read the comment docs.


Adds banner for KubeCon + CloudNativeCon EU 2022

Fixes #33560
This PR:

Adds banner for KubeCon + CloudNativeCon EU 2022 on the K8s website.
Changes the end time of the Dockershim Removal  to match the start time of the KubeCon Banner.

I am open to suggestions on the colour scheme (I do not have a good sense of colour schemes😅😅)
Files changed:

https://github.com/kubernetes/website/blob/main/data/announcements/scheduled.yaml
https://github.com/kubernetes/website/tree/main/static/images/announcements (to add the banner image)

Signed by: Vitthal Kaul<EMAIL_ADDRESS>

/cc @sftim

/committee steering

@sftim I tried the workflow you suggested, but it is asking me to open a new PR with 3 commits. What should I do, could you please guide me. Thanks.

As I had some issues in rebasing this PR based on @sftim's suggestion I have opened a new PR #33578 . Thanks

I will close this PR now.
/close


Next/Previous buttons not disabled on initialization when there are not enough slides

It looks like the bc-flickity-previous and bc-flickity-next directives do not initialize as disabled, even if there are not enough slides to scroll. It looks like the functions defined here: https://github.com/benjamincharity/angular-flickity/blob/master/src/previous/previous.directive.js#L71 and here: https://github.com/benjamincharity/angular-flickity/blob/master/src/next/next.directive.js#L73 need to be called when Flickity is initialized.

Good catch @nhardy. I don't currently have much bandwidth to work on this, but will try to get to it soon(ish). As always, PRs are welcome!


SRDF conventions and parsing

Hi guys,
I want to raise a discussion and potential actions to be tackled regarding SRDF convention. My motivation is to have relevant semantic information that is used for motion planners, controllers, etc. Specifically I have these two points in mind:

Defining set of foot and hand end-effectors
Describing unimportant joints (i.e. joints that are not needed to be considered for planning, control, etc; e.g. neck joints).

I would say that everyone agree that this information should be described in the SRDF. However it is not very clear for me how to properly do it. In any case I believe we can attach to this standard, otherwise we should discuss how to modify the SRDF standard.

Point 1: set of foot and hand end-effector
I think the best way to do this is through the end_effector tag. With this tag we should also define the groups in order to semantically describe a leg or arm. Let me write an example for the HyQ robot:
    <!-- left front leg -->
    <group name="lf_leg">
        <joint name="lf_haa_joint" />
        <joint name="lf_hfe_joint" />
        <joint name="lf_kfe_joint" />
        <chain base_link="trunk" tip_link="lf_foot" />
    </group>
    <!-- right front leg -->
    <group name="rf_leg">
        <joint name="rf_haa_joint" />
        <joint name="rf_hfe_joint" />
        <joint name="rf_kfe_joint" />
        <chain base_link="trunk" tip_link="rf_foot" />
    </group>
    <!-- left hind leg -->
    <group name="lh_leg">
        <joint name="lh_haa_joint" />
        <joint name="lh_hfe_joint" />
        <joint name="lh_kfe_joint" />
        <chain base_link="trunk" tip_link="lh_foot" />
    </group>
    <!-- right hind leg -->
    <group name="rh_leg">
        <joint name="rh_haa_joint" />
        <joint name="rh_hfe_joint" />
        <joint name="rh_kfe_joint" />
        <chain base_link="trunk" tip_link="lh_foot" />
    </group>

    <end_effector name="lf_foot" parent_link="lf_foot" group="lf_leg" />
    <end_effector name="rf_foot" parent_link="rf_foot" group="rf_leg" />
    <end_effector name="lh_foot" parent_link="lh_foot" group="lh_leg" />
    <end_effector name="rh_foot" parent_link="rh_foot" group="rh_leg" />

With this example, you can parser:

The frame of the end-effector.
The number of joints of that chain, then, for instance, you can build an appropriate Jacobian.

Please note that it's missing the foot dimension. For that we will have to improve the SRDF. This is an example of how it could look:
    <foot name="lf_foot" type="point" /?>
    <!-- for a humanoid case -->
    <foot name="l_foot" type="planar" dim_x="0.1" dim_y="0.1" />

Point 2: Unrelevant joints*
There are sometime joints that you don't want to consider, these are examples:

Neck joints are not needed for walking planning.
Gripper joints are not controlled in torque (e.g. TSID)

For doing so, I suggest to extract this information from the groups tag, and the developer decides which group to use. In this case, it's important to define a naming convention for groups.

Final note
This might be long way discussion, and it's possible that we cannot make a decision any-time soon. I would invite everyone to this discussion, especially I would appreciate the point of view of main developers (@jcarpent @jmirabel @gabrielebndn @nim65s @olivier-stasse @nmansard).

However it missing the foot dimension. For that we will have to improve the SRDF.

We do this by defining the corners/contact points as relative offset frames of the foot frame. This allows us to handle the points for contact wrenches explicitly (and also add intermediate points instead of just the four corners, if desired). Perhaps something like this would be better than specifying the dimension and assuming implicitly that the foot is a rectangle.

For contacts, I implemented the following convention (https://gepettoweb.laas.fr/hpp/hpp-manipulation-urdf/doxygen-html/index.html):
<contact name="name">
  <!-- Exactly 1 of -->
  <!-- Set the link used to build the reference frame
       In the first case, the position of the points below are expressed in the
       link frame.

       In the second case, the position of the points below are expressed in the
       frame of the "index_collision_object"th collision body in the link. If
       you have only one body, then set it to zero. This is a convenient way of
       of defining surfaces on a particular body.
       -->
    <link name="link_name" />
    <link name="link_name" index="index_collision_object" />

  <!-- Exactly 1 -->
    <!-- Sequence of 3D points expressed in the frame defined above -->
    <point>-0.025 -0.025 -0.025   -0.025 0.025 -0.025   -0.025 -0.025 0.025   -0.025 0.025 0.025 </point>

    <!-- Sequence of planar shape.
         Shapes are defined by a sequence of points to be connected (consecutively).
         For a shape defined by N points, N+1 values must be provided in this tag:
         N iPoint_1 ... iPoint_N

         WARNING: Shapes 3 0 1 2 and 3 0 2 1 are different because their respective orientations are opposites.
         firstSegment ^ secondSegment must points outside the object -->
    <shape> 3 0 2 1 3 2 1 3</shape>
</contact>


[BUG] Image Markdown with spaces in URL not rendered correctly

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Image is not rendered, with the markdown link exposed:

Expected Behavior
URL in markdown images should be URL sanitized:
![Nvidia Stock Performance](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfOcXoq5qx7BzkTcTnVnF2V8_Y7wFyTrjlWWxwJpF3bnJtayv5GHKmjUCW2LBArZZO2P-2s1WPd-Do2ZbbI8KMbs1Ji6WZuIn2n6LSR5gD7kp2SLdkrQUK9DYhIJ-tEejkVTjyP-uVQcs_w28P3BzRIBIROW4BX5pCSNubxhdl-NM2WR_JtV_i0JSYXA/s1266/Screenshot%202023-05-31%20102952.png)

Steps To Reproduce

Go on morphic.sh
Search for Why is Nvidia growing rapidly?
Search follow up What future innovations can we expect from Nvidia that may influence its stock performance?

Environment
- OS: Darwin Kernel Version 23.5.0 arm64
- Browser: Arc Browser

Anything else?
No response

Thank you for the detailed report.


https command not found after fresh installation

Hi guys,
Any time I install httpie on Ubuntu (sudo apt-get install httpie), the http command works perfectly fine afterwards.
However, https is never found.

I have had this on all machines where I tried this so far, WSL on Windows, as well as native Ubuntu 19.x and 20.x.
What do I need to do to get https command working as well, and what needs to change in the installation instructions, because I can't imagine I'm the only one encountering this?

@batjko it should work out of the box, but I can see the Ubuntu version very old. We’re working on having it updated to the latest 2.x. In the meantime, I’d recommend you installing HTTPie via pip.

Ok thanks, I'll try that instead.

I close that issue as the root cause is #1003, let's focus on one issue.


Inventory groups

This PR adds support of inventory groups. Groups are optional, and "plain" (groupless) files without still supported
i.e. the oll format like this, sill valid:
h1.example.com
h2.example.com:2222
h3.example.com:2223 user2

in addition, ini-style groups can be defined:
[gr1]
h1.example.com
h2.example.com:2222

[gr2]
h3.example.com:2223 user2

PR also changes the inventory format for both inventory_file and inventory_url to support groups, i.e.
inventory_file: {location: "testdata/inventory", groups: ["staging"]}

Note: this is a breaking change


fix(github/workflows/security): install gosec fails with package embed is not in GOROOT

security workflow runs gosec which needs go version > 1.16 but install v1.15.15; package embed is not in GOROOT
bumps deps
closes #271

Not sure what snyk is complaining about, don't have access. Otherwise I'm pretty sure this PR is good.

Hey @ReneWerner87 there was also a missing exclude on the root gosec run; fixed with 660a7fs


chore(keda): add 2.8 and 2.9 versions

Similar to https://github.com/jsonnet-libs/k8s/pull/254 but with the most recent versions.

Hi @Duologic, I noticed you reviewed the PR https://github.com/jsonnet-libs/k8s/pull/167. Can you please review this one?


Edit functionality fails.

I get the error
stack traceback:
        ...cal/share/nvim/lazy/avante.nvim/lua/avante/selection.lua:300: in function 'create_editing_input'
        ...m/.local/share/nvim/lazy/avante.nvim/lua/avante/init.lua:311: in function 'edit'
        [string ":lua"]:1: in main chunk

when attempting to use the edit functionality. The stacktrace points to the same line in both V and v mode, so Utils.get_visual_selection_and_range() may not be working correctly? I am far from a lua expert, but happy to help debug.

are you on main? works for me
https://github.com/user-attachments/assets/6d5e0e4f-b108-4379-8d55-25192b8d85ef

On this topic, edit changes more than just the selected code for me:

Am I using it incorrectly?

On this topic, edit changes more than just the selected code for me:在这个主题上，编辑更改不仅仅是为我选择的代码：   Am I using it incorrectly?是我使用方式不对吗？

The performance of OpenAI is very poor, it often doesn't follow instructions. I suggest using Claude only.

are you on main? works for me

Yes, on 77d344d. I tried triggering get_visual_selection_and_range with a function (which may be incorrect)
:lua print(require('avante.utils').get_visual_selection_and_range())<CR>
which gives nil. Presumably this means I have some conflicting settings somewhere that stop this working.

Ok it is definitely my problem. I have defined the shortcut via whichkey with
      {
          mode = { "v" },
          { "<leader>ae", ":lua require('avante').edit()<CR>", desc = "Avante Edit" },
          { "<leader>ab", ":lua print(vim.fn.mode())<CR>"  },
      }

when I use <leader>ab, the mode reported is n, which causes get_visual_selection_and_range() to return nil, which then causes the error.

For anyone else who runs into this, this works:
{ "<leader>ae", function() require('avante').edit() end, desc = "Avante Edit" },

On this topic, edit changes more than just the selected code for me:在这个主题上，编辑更改不仅仅是为我选择的代码：   Am I using it incorrectly?是我使用方式不对吗？

The performance of OpenAI is very poor, it often doesn't follow instructions. I suggest using Claude only.

Nice this change works. Any idea how curser gets theirs to work with openai? Maybe a different prompt depending on the model?

On this topic, edit changes more than just the selected code for me:在这个主题上，编辑更改不仅仅是为我选择的代码：   Am I using it incorrectly?是我使用方式不对吗？

The performance of OpenAI is very poor, it often doesn't follow instructions. I suggest using Claude only.

Nice this change works. Any idea how curser gets theirs to work with openai? Maybe a different prompt depending on the model?

Cursor has done a lot of prompt engineering work, and these prompts are all closed-source. They even have their own trained models for assistance, so they cannot be compared on the same level.


feat: allow one failed decryption before reauth

feat: allow one failed decryption before reauth
fix for #107

Thanks


chore(js): update version

When this is merged I will do a "publish wrappers" GH action.

This is needed for argon2i support for the JS wrapper.


clang12 and archlinux

Hello
I cannot build it in ArchLinux with clang 12.0.0
Some ideas?

Sorry for the late feedback. If you still have this problem and are interested in solving it, please provide the error output generated when building.


Editor: Fix code completions when working with bootstrap

@blink1073, this fixes completions for me when using bootstrap.
I think the solution is the right one because we should only touch PYTHONPATH for the QProcess that starts plugin_server when using bootstrap. In other situations plugin_server should be able to find spyderlib (the only third-party module it needs) in site-packages.
Please review and let me know what you think about this one, given that now you're our Editor completion expert :-)

This forces the user to have spyder installed in the virtual/conda environment.  I think the right fix is to use the dirname on the results provided by find_module, but otherwise leave the code the same.

I see, so you want to use the spyderlib module from where Spyder is installed to start plugin_server with executables of virtual/conda envs.
In that case the solution is to change this
if DEV:
    python_path = imp.find_module('spyderlib')[1]
    env.append("PYTHONPATH=%s" % osp.dirname(python_path))

for this
python_path = imp.find_module('spyderlib')[1]
env.append("PYTHONPATH=%s" % osp.dirname(python_path))

But we also would need to start IntrospectionManager with the executable selected by users in
Preferences > Console > Advanced Settings

right? Because right now we're not doing that, as can be seen here:
https://github.com/spyder-ide/spyder/pull/2932/files#diff-608bfe6fde6d5ca0e735b2715ebf63c5R404

We also want rope or jedi, since those might not be environment.  We had punted on using executable setting because @goanpeca said environment handling was in flux.

Ok, I understand things better now :-) Your previous code was not working though, but it only requires some minor changes to make it so.

@blink1073, I think this is ready now.

Great, thanks!


statusline in the same position than cmdline

Hi,
I just installed the vim-airline plugin but I've a problem. The statusline is over the cmdline. When I write some command, like :w, it writes over status line.
This is when I open a file:

When I save the file:

And when I move the cursor after save:

This is my .vimrc:
set nocompatible              " be iMproved, required
filetype off                  " required

" Set Proper Tabs
set tabstop=4
set shiftwidth=4
set smarttab
set expandtab

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
" alternatively, pass a path where Vundle should install plugins
"call vundle#begin('~/some/path/here')

" let Vundle manage Vundle, required
Plugin 'VundleVim/Vundle.vim'

" The following are examples of different formats supported.
" Keep Plugin commands between vundle#begin/end.
" plugin on GitHub repo
Plugin 'tpope/vim-rails'
Plugin 'vim-ruby/vim-ruby'

" Browser
Plugin 'scrooloose/nerdtree'

" Syntax Utils
Plugin 'scrooloose/syntastic'
Plugin 'godlygeek/tabular'
Plugin 'plasticboy/vim-markdown'

" Terminal Utils
Plugin 'bling/vim-airline'
Plugin 'vim-airline/vim-airline-themes'

" Developers Tools
Plugin 'taglist.vim'

" Git Integration
Plugin 'tpope/vim-fugitive'

" All of your Plugins must be added before the following line
call vundle#end()            " required
filetype plugin indent on    " required

" NerdTree Settings
" Open Automatically
let g:NERDTreeWinPos = "right"
autocmd StdinReadPre * let s:std_in=1
autocmd VimEnter * if argc() == 0 && !exists("s:std_in") | NERDTree | endif
autocmd VimEnter * wincmd p " Not needed if WinPos if right
autocmd bufenter * if (winnr("$") == 1 && exists("b:NERDTree") && b:NERDTree.isTabTree()) | q | endif

Regards

@surver not sure this is related, but what happens if you add this to .vimrc?
set cmdheight=2

what is your terminal? and is your $TERM correct?

Thanks @slabua , it works fine.


MongoDB unable to create replSet on ubuntu 14.04 VM

BigchainDB version:Latest

Operating System: Ubuntu 14.04

Deployment Type: [Docker|Host|IPDB|Other] Google Cloud

If you are using IPDB, please specify your network type [test, prod]
and the bdb_url(BigchainDB URL) you are using.
For every other type of deployment, please specify the documentation/instructions
you are following.

BigchainDB driver: [yes|no] yes

If using a driver please specify, driver type [python|js|java]
and version.  : Python

Description
I'm trying to install bigchaindb on ubuntu 14.04 VM running on Google Cloud.
Steps to Reproduce
I was following the quickstart documentation to install mongodb and bigchain python driver.
After $ sudo chmod -R 700 /data/db
I ran $ sudo mongod --replSet=bigchain-rs
which led to this
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback/error message here.

017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] MongoDB starting : pid=15435 port=27017 dbpath=/data/db 64-bit host=ubuntu-1
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] db version v3.4.10
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] git version: 078f28920cb24de0dd479b5ea6c66c644f6326e9
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] modules: none
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] build environment:
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten]     distmod: ubuntu1404
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-11-15T08:48:53.314+0000 I CONTROL  [initandlisten] options: { replication: { replSet: "bigchain-rs" } }
2017-11-15T08:48:53.335+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTi
ger'.
2017-11-15T08:48:53.336+0000 I STORAGE  [initandlisten]
2017-11-15T08:48:53.336+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2017-11-15T08:48:53.336+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2017-11-15T08:48:53.336+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1337M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,s
tatistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten]
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten]
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten]
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten]
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2017-11-15T08:48:53.555+0000 I CONTROL  [initandlisten]
2017-11-15T08:48:53.558+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2017-11-15T08:48:53.558+0000 I REPL     [initandlisten] Did not find local voted for document at startup.
2017-11-15T08:48:53.558+0000 I REPL     [initandlisten] Did not find local replica set configuration document at startup;  NoMatchingDocument: Did not find replica set configuratio
n document in local.system.replset
2017-11-15T08:48:53.558+0000 I NETWORK  [thread1] waiting for connections on port 27017

@raaghavvd  I guess we resolved this on the gitter channel, can I close this issue?

@muawiakh  you can! Thanks again :)


Remove outdated information about the long running and lambda based verification test

Remove outdated information about the long running and lambda based verification test.

Thank for the quick review @jackkleeman and @igalshilman. Merging it now.


343 pjg simple demos

@doutriaux1 @durack1  Changes to setup.py have been made as discussed,  but likely need work.   Demo data is currently not built into package but rather available at http://oceanonly.llnl.gov/gleckler1/pmp-demo-data/pmpv1.1_demodata.tar as indicated in demo1 parameter file:
https://github.com/PCMDI/pcmdi_metrics/blob/343_pjg_simple_demos/demo/parameter_files/pmp_input_parameters_demo1.py
PLS address ASAP so that we can iterate as needed and because there is more "demo" coming.
FYI documentation progressing: https://github.com/PCMDI/pcmdi_metrics/wiki/Using-the-package

@doutriaux1 there are still errors in travis, so will leave this for you to resolve..

@doutriaux1 this is still causing segfaults:
here and here
/Users/travis/build.sh: line 45:  1761 Segmentation fault: 11  python test/test_suite.py

@doutriaux1 @durack1  Really need to get this fixed/pushed asap.... 2 users struggling with demo right now and need this.

@gleckler1 this is still going to fail the tests until the fixes in #378 are merged into master and these changes are pulled into this branch.. If it's holding you up, merge this, however it's going to cause conflicts with the setup.py edits in #378

@durack1 @doutriaux1  Agreed, best would be get it all in, but first the bug in #378 (failing with needs to be fixed, and also verify that PG has not messed setup with this (PR343)

@gleckler1 if you feel like a pro, you could merge #378 into this branch and push again.. Then we'd know and could merge without hesitation..

@durack1 not a pro

@gleckler1 wanna be a pro?
git fetch --all -p ; # Will pull all remote history across to your repo, without changing anything
git merge --no-commit origin/issue_316_regions ; # A dry run to see what will change
and if you like what you see
git merge --no-ff origin/issue_316_regions ; # Make the changes
I think.. You'll likely also have to fix the setup.py conflicts..

@durack1 don't want to be a pro... I'm juggling too many fires to do this well... what I'm looking for is help

@gleckler1 I tried with #379 but I am no out-pro'd, so will have to wait for @doutriaux1 to take a peek

hum @gleckler1 did you really mean to close this?

oh i see you have another issue #371

@doutriaux1 yes its nearly the same as
https://github.com/PCMDI/pcmdi_metrics/pull/376...
checking out til 9am

@doutriaux1 scratch that, have kept this open and instead closed
https://github.com/PCMDI/pcmdi_metrics/pull/373
PLEASE REVIEW AND MODIFY AS NECESSARY.  NEED FEEDBACK ON proposed setup changes before preparation of demos can be continued

@gleckler1 why did you merge?

@doutriaux1 Because I've been pleading for this to be the top priority since it was opened and kept asking for it to be looked at and nothing was happening.   As noted the priority was to help me advance the other demo stuff coming down z pipe ...

yes but there are things to tweak. I reverted it and will resubmit the PR soon. Look at my comments please

why did you need it into master? If you need this for something else, simply merge this branch into whatever branch needs it.

I wanted to get your confirmation on how the demo files were going to get mapped by setup.py (and into conda build) so that I could advance other demos based on their location.
From: Charles Doutriaux <notifications<EMAIL_ADDRESS>Reply-To: PCMDI/pcmdi_metrics <reply<EMAIL_ADDRESS>Date: Tuesday, July 19, 2016 at 1:49 PM
To: PCMDI/pcmdi_metrics <pcmdi_metrics<EMAIL_ADDRESS>Cc: gleckler1 <pgleckler<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [PCMDI/pcmdi_metrics] 343 pjg simple demos (#376)
why did you need it into master? If you need this for something else, simply merge this branch into whatever branch needs it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PCMDI/pcmdi_metrics/pull/376#issuecomment-233761112, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEV6rWNyuN-cBa8k18LNPFQOS-9CcBOdks5qXThfgaJpZM4JKney.


feat: add fuel wallet

Background
I would love to add full Fuel support to the GOAT SDK, and I figured a good place to start would be adding the wallet; followed by plugins later :)
What does this PR do?
This PR adds a FuelWalletClient (@goat-sdk/wallet-fuel).
What kind of change is this?
New wallet
Documentation changes needed?
Yes. Done
Testing
Detailed testing steps

cd into the vercel-ai/fuel example
Populate the .env file with a Fuel Wallet private key and an OpenAI API key
Run pnpm send-eth

For plugins

[x] I have tested this change locally with key pair wallets
[ ] I have tested this change locally with hosted wallets (e.g. Crossmint Smart Wallets, etc.)

Discord username
dhaiwat10

Need to run pnpm lint:fix only


long name for autogenerated file

In process of switching my big old enterprice system from sync model to sync+async model with this ISG, I noticed that the ISG can produce a very long cs name if cs's namespace is long itself.
I did not face with problems but I suspect the problems can arise if g.cs filename + usual folder (e.g. C:\Users\your nickname\AppData\Local\Temp\VSGeneratedDocuments\71a6d680-b451-552c-0837-9b526402ade0) will be longer than 260 symbols.
May be the better behaviour is to truncate the name of g.cs file if it is too long.
just fyi, I may be wrong.

Yeah, good scenario to test.


Run/Debug for the IDEs takes a long time

Description:
Run/Debug for the IDEs takes a long time. Need to inform user when "compiling" is started.
For ex. "Compiling source code..."
Affected Versions:
1.0.0-beta-SNAPSHOT

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/18089


MukeshNanda-MSFT-Planned-Maintenance-Update

Added description for new ImpactType and ImpactDuration properties with examples.

@MukeshNandaMS
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


Allow a permalink to the demo with a given piece of code and config

Fixes https://github.com/eslint/eslint.github.io/issues/99
This updates the demo to allow code and config to be specified with a URL. Hopefully, this should make the demo an easy bug-reporting tool -- as an alternative to filling out information on Node versions etc., users could just paste a link to the demo with a particular code and config to demonstrate the bug.
The serialization format is:
atob(JSON.stringify({ text: "the text", options: { /* the config */ })
The serialized state is placed in the URL hash whenever the config or text is changed.
This commit also updates the config-building logic to make the serialized configs smaller, to prevent the URLs from getting too long. In particular, rules that were previously configured with "off" are now omitted from the config, and envs that were previously false are now omitted.
Even with these changes, the URL for the default state is still very long, because every rule from eslint:recommended is explicitly enabled in the demo config by default:

URL for default text/config
https://eslint.org/demo/#eyJ0ZXh0IjoidmFyIGZvbyA9IGJhcjsiLCJvcHRpb25zIjp7InBhcnNlck9wdGlvbnMiOnsiZWNtYVZlcnNpb24iOjUsInNvdXJjZVR5cGUiOiJzY3JpcHQiLCJlY21hRmVhdHVyZXMiOnsianN4IjpmYWxzZSwiZ2xvYmFsUmV0dXJuIjpmYWxzZSwiaW1wbGllZFN0cmljdCI6ZmFsc2UsImV4cGVyaW1lbnRhbE9iamVjdFJlc3RTcHJlYWQiOmZhbHNlfX0sInJ1bGVzIjp7ImNvbnN0cnVjdG9yLXN1cGVyIjoiZXJyb3IiLCJuby1jYXNlLWRlY2xhcmF0aW9ucyI6ImVycm9yIiwibm8tY2xhc3MtYXNzaWduIjoiZXJyb3IiLCJuby1jb21wYXJlLW5lZy16ZXJvIjoiZXJyb3IiLCJuby1jb25kLWFzc2lnbiI6ImVycm9yIiwibm8tY29uc29sZSI6ImVycm9yIiwibm8tY29uc3QtYXNzaWduIjoiZXJyb3IiLCJuby1jb25zdGFudC1jb25kaXRpb24iOiJlcnJvciIsIm5vLWNvbnRyb2wtcmVnZXgiOiJlcnJvciIsIm5vLWRlYnVnZ2VyIjoiZXJyb3IiLCJuby1kZWxldGUtdmFyIjoiZXJyb3IiLCJuby1kdXBlLWFyZ3MiOiJlcnJvciIsIm5vLWR1cGUtY2xhc3MtbWVtYmVycyI6ImVycm9yIiwibm8tZHVwZS1rZXlzIjoiZXJyb3IiLCJuby1kdXBsaWNhdGUtY2FzZSI6ImVycm9yIiwibm8tZW1wdHktY2hhcmFjdGVyLWNsYXNzIjoiZXJyb3IiLCJuby1lbXB0eS1wYXR0ZXJuIjoiZXJyb3IiLCJuby1lbXB0eSI6ImVycm9yIiwibm8tZXgtYXNzaWduIjoiZXJyb3IiLCJuby1leHRyYS1ib29sZWFuLWNhc3QiOiJlcnJvciIsIm5vLWV4dHJhLXNlbWkiOiJlcnJvciIsIm5vLWZhbGx0aHJvdWdoIjoiZXJyb3IiLCJuby1mdW5jLWFzc2lnbiI6ImVycm9yIiwibm8tZ2xvYmFsLWFzc2lnbiI6ImVycm9yIiwibm8taW5uZXItZGVjbGFyYXRpb25zIjoiZXJyb3IiLCJuby1pbnZhbGlkLXJlZ2V4cCI6ImVycm9yIiwibm8taXJyZWd1bGFyLXdoaXRlc3BhY2UiOiJlcnJvciIsIm5vLW1peGVkLXNwYWNlcy1hbmQtdGFicyI6ImVycm9yIiwibm8tbmV3LXN5bWJvbCI6ImVycm9yIiwibm8tb2JqLWNhbGxzIjoiZXJyb3IiLCJuby1vY3RhbCI6ImVycm9yIiwibm8tcmVkZWNsYXJlIjoiZXJyb3IiLCJuby1yZWdleC1zcGFjZXMiOiJlcnJvciIsIm5vLXNlbGYtYXNzaWduIjoiZXJyb3IiLCJuby1zcGFyc2UtYXJyYXlzIjoiZXJyb3IiLCJuby10aGlzLWJlZm9yZS1zdXBlciI6ImVycm9yIiwibm8tdW5kZWYiOiJlcnJvciIsIm5vLXVuZXhwZWN0ZWQtbXVsdGlsaW5lIjoiZXJyb3IiLCJuby11bnJlYWNoYWJsZSI6ImVycm9yIiwibm8tdW5zYWZlLWZpbmFsbHkiOiJlcnJvciIsIm5vLXVuc2FmZS1uZWdhdGlvbiI6ImVycm9yIiwibm8tdW51c2VkLWxhYmVscyI6ImVycm9yIiwibm8tdW51c2VkLXZhcnMiOiJlcnJvciIsIm5vLXVzZWxlc3MtZXNjYXBlIjoiZXJyb3IiLCJyZXF1aXJlLXlpZWxkIjoiZXJyb3IiLCJ1c2UtaXNuYW4iOiJlcnJvciIsInZhbGlkLXR5cGVvZiI6ImVycm9yIn0sImVudiI6e319fQ==

It might be possible to make this shorter in the default case by making the config extend from eslint:recommended, and then explicitly disabling rules from eslint:recommended in the config if necessary.
Security considerations:

If it's possible to cause ESLint to execute custom code when linting a given text with a given config, then this change will allow reflected XSS on the eslint.org origin. An attacker could get a victim to click a link/load an iframe with a URL that puts malicious code in the demo, and some JavaScript would get run in the user's browser. eslint.org is a static site, so it would be difficult for an attacker to cause any significant damage, but reflected XSS is still undesirable. This change assumes that it's not possible for this to happen when linting untrusted code.
An attacker could tamper with the user's cached state in localStorage by getting the user to click a link/load an iframe with different code/config. This could be mildly annoying for the user. To avoid this, if code is loaded from the URL hash, the state is not saved to localStorage until the user modifies the code or the config.

We could do something like what astexplorer.net (or was that some other online tool?) is doing and store the code/config in gist.

That's true. One potential issue with using gists is that unlike astexplorer.net, we don't have any backend to store OAuth tokens, and I'm unsure about whether the GitHub API supports anonymous OAuth tokens (i.e. creating a gist without authenticating through the user's account first).


Add BasePath input to NugetPackager task

@jlucansky,
Thanks for having already signed the Contribution License Agreement. Your agreement has not been validated yet. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

take or leave

Thanks for contributing!
Unfortunately, this task is deprecated, because its functionality was combined into the "NuGet" (called "NuGetCommand" in this repo) task. If you'd like, you can port the change to the "NuGetCommand" task, and we'd be willing to accept it from there, after review.


Inter-Module Configuration passing

Current work on multiaxis support is leading to some issues with passing configurations between modules. This is likely part of our on-going understanding of how to use memories effectively and RTL design patterns. There was some offline discussion of an inter-module bus architecture. The downsides are this may add additional gates/LUTs. The upside is this would greatly simplify macrofying a driver module on ASIC.
Filing this as an issue because it is likely best to get multi axis in ASAP for integration test and hack around this until we find a proper solution.

Somewhat philosophical point:
Verilog Modules are intended (at least as far as I can tell) to be logical abstractions and physical black boxes. Now for ASIC hardening we need to plan somewhat in advance what we want to harden separately. During the eFabless MPW-one we tried both a hyper-modularized approach, somewhere inbetween, and a "monolith". Ultimately the monolith was shipped, but I think that we all agreed that it was not a satisfying solution.
The core issue with the FSM and modularization is that memories cannot be passed in and out of modules. To really get multiaxis into the protocol we need either a bus on each module to pass configuration or we need to instantiate them alongside the FSM. Instantiating along side the FSM is the simplest solution and likely uses the fewest resources. A bus is satisfying from a re-use and validation standpoint.
I am proposing we punt the bus issue to work on the SPI user-facing APIs, and make the statemachine at the top-level again. So leave this an open issue, but fix the core issue which is getting per-axis parameters (such as current and microsteps) supported ASAP.


Upgrade to Terraform 3.x

Problem statement
Terraform 2.99 will go EOL two years after release.  In the mean time, new Azure features and configuration capabilities will not be added to the 2.x code base.
HashiCorp recommends that customers "stay current within two (2) releases from the latest major release in order to receive optimal support".
What you need to know

Terraform 2.99 release notes
HshiCorp support/End-of-Life polity
Terraform 3.x releases
Terraform 3.x upgrade guide

Acceptance criteria

[ ] ...

To do

[ ] ...

duplicate of https://github.com/CDCgov/prime-reportstream/issues/6819


Make browser example runnable

previous browser command is not available anymore from theia command line.

Someone already did a PR for this.