[Docbug][Addednewlink][4131]

Added new link.

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit ce77556:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:warning:Warning
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/code-samples' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 30, Column 3: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/code-samples' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 26, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit a28df35:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:bulb:Suggestion
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 6926b2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:bulb:Suggestion
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 30: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 12: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit c318c1b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:bulb:Suggestion
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit fb2babb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:warning:Warning
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Warning-file-not-found] Invalid file link: '~/platform/get-started/code-samples'.
Line 30, Column 3: [Warning-file-not-found] Invalid file link: '~/platform/get-started/code-samples'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit fda3a13:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:warning:Warning
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Warning-file-not-found] Invalid file link: '~/microsoftteams/platform/get-started/code-samples'.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 305519a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:warning:Warning
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 26, Column 3: [Warning-file-not-found] Invalid file link: '../microsoftteams/platform/get-started/code-samples'.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 648a429:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:bulb:Suggestion
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md

Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/get-started/code-samples' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 4c67b6f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit a056e2a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md

link
:warning:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit ebca66b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md

link
:warning:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit f97dd39:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/visual-studio-code-overview.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

This issue is already resolved. The links are working fine in the live site. Hence closing this PR.


Convert GitHub checks to V2 checkout

Describe the bug
PRs are failing checks on checkout of sources
To reproduce
Steps to reproduce the behavior:
No good way to repro. Usually happens when rerunning checks on a PR.
Example: https://github.com/InstituteforDiseaseModeling/covasim/pull/152/checks?check_run_id=596695102
Additional context

Fixed bug in GitHub Actions - Checkout: https://github.com/actions/checkout/issues/23

This was fixed at some point


sig11 in docker container

It seems in an alpine container build I can ether have TCB support or a static binary, but not both, and my goaccess built without -static coredumps with no useful info. Is there a background to this, is it possible to have a containerized version with tokyocabinet support?
thx

This is related to #832. TCB is going away in favor of a more stable on-disk storage.

Sorry, my search-fu failed.
I just checked, build without -static and without tcb works, so yeah: this is a TCB problem.


[CSL-1009] - Move gitHash and gitBranch printing to executables

It was building, tests were passing
after merge of master, I can not build any more, so if it doesn't build please let me know

@7sedam7 FYI: I force-pushed to this branch, reset your local version please.

I think it can be closed, because we need a different solution anyway, see https://issues.serokell.io/issue/CSL-1328#comment=96-5292

Agree. If we need different solution so why spend time on non-viable solution? Does it improve anyone's life?

Well, this solution still improves our lifes, because it makes compilation faster than what we currently have. So if we know that we will not do CSL-1328 in near future, we can finish this effort at least (which seems much easier than CSL-1328).


Refactor ring, sign, and relay functionality

Summary
This PR completes the refactoring of the SDK. It breaks the functionality required for sending relay requests into multiple components. More specifically: building of a relay request, getting a ring for an application to sign the relay requests, and response verification.
Issue
This PR follows the direction set in the following comment:
https://github.com/pokt-network/shannon-sdk/pull/10#issuecomment-2167725491
Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[x] Code health or cleanup
[x] Documentation
[ ] Other (specify)

Sanity Checklist

[x] I have tested my changes using the available tooling
[x] I have commented my code
[x] I have performed a self-review of my own code; both comments & source code
[] I create and reference any new tickets, if applicable
[x] I have left TODOs throughout the codebase, if applicable

Created an issue to record the work we need to do to complete the example on sending relays.


Mechanism used to fetch Tokens from MSa Service

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
None
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
None
Description
HI Team, I am currently working on a chrome extension and we have a limitation that from Manifest Version3, chrome extensions don't allow the usage of XMLHttpRequest. I would like to confirm if the access tokens using in the MSAL library are extracted using fetch API or XMLHttpRequest.
MSAL Configuration
No response
Relevant Code Snippets
No response
Identity Provider
No response
Source
Internal (Microsoft)

@ashitaagrwl Where the Fetch API is detected (i.e. window.fetch && window.Headers), MSAL will use Fetch instead of XMLHttpRequest.


Recognition for Libri Speech

Could you please provide the recognition code for Libri speech to predict the sentence.

@profsatwinder  please reffer to #9, thank you


Fix python prepared statement null value

This PR handles the None value in the python api.

Does this fix https://github.com/kuzudb/kuzu/issues/2983 as well?

Yes this should fix #2983 as well


Speed up calculations using graphics card with GeoLift

Is your feature request related to a problem? Please describe.
GeoLiftMarketSelection takes a long time to run specially when increasing lookback_window and treatment_period values. Is it possible to speed up these calculations using a GPU?
Describe the solution you'd like
Would ideally like to specify device to speed up calculations on.
Describe alternatives you've considered
I have tried setting parallel_setup = "parallel" but this did not have a significant improvement in runtime.

Hi @sohammarin! Thanks for reaching out to us. This is a very interesting idea that we haven't actively explored before. I've added it to our Feature Requests here: https://github.com/facebookincubator/GeoLift/projects/1#card-84669647


News and tags page 403 forbidden if next export used

Describe the bug
News and tags page 403 forbidden if next export used
To Reproduce
Steps to reproduce the behavior:
use next export after build

Verified that it works on the latest starter template at https://github.com/timlrx/pliny


UI - Attempt to prompt for entering provider credentials when launching UI fails

gptscript version v0.8.2+1b5e068f
Steps to reproduce the problem:

Launch UI using a model from anthropic-provider

%gptscript --default-model 'claude-3-opus-20240229  from github.com/gptscript-ai/anthropic-provider'  --ui
14:22:49 WARNING: Changing the default model can have unknown behavior for existing tools. Use the model field per tool instead.
14:22:49 started  [main]
14:22:49 started  [provider: https://raw.githubusercontent.com/gptscript-ai/anthropic-provider/3b9b9365d469c4c702291f1764537ab5c226c2e0/tool.gpt:Anthropic Claude3 Model Provider]
14:22:49 started  [credential: github.com/gptscript-ai/claude3-anthropic-provider/credential]
14:22:49 sent     [credential: github.com/gptscript-ai/claude3-anthropic-provider/credential]
? Please enter your Anthropic API token. ^[[44;219R^[[44;42R2024/06/18 14:22:50 getting prompt response invalid status code [500], expected 200
Failed to run sys.prompt.
14:22:50 failed to run tool [claude3-anthropic-credential] cmd [/usr/bin/env python3 /Users/sangeethahariharan/Library/Caches/gptscript/repos/3b9b9365d469c4c702291f1764537ab5c226c2e0/credential/tool.gpt/python3.12/credential/credential.py]: exit status 1
2024/06/18 14:22:50 no prompt server found, can not continue
sangeethahariharan@Sangeethas-MBP gptscript % 4;219R4;42R

Launch UI .

sangeethahariharan@Sangeethas-MBP gptscript % gptscript --ui
14:24:54 started  [main]
2024/06/18 14:24:54 no prompt server found, can not continue

Launch UI using a model from local LLM

gptscript --disable-cache --default-model 'Llama-3-8b-function-calling-alpha-v1.gguf from http://localhost:1234/v1' --ui examples/bobchat.gpt
14:27:02 WARNING: Changing the default model can have unknown behavior for existing tools. Use the model field per tool instead.
14:27:03 started  [main] [input=--file=bobchat.gpt]
2024/06/18 14:27:03 no prompt server found, can not continue

i'm facing a similar issue:
```gptscript --ui
11:56:01 started  [main]
11:56:01 started  [context: github.com/gptscript-ai/context/os]
11:56:01 sent     [context: github.com/gptscript-ai/context/os]
11:56:01 ended    [context: github.com/gptscript-ai/context/os] [output=The local operating systems is uname_result(system='Darwin', node='MacBook-Pro-de-Daniel.local', rel...]
2024/07/30 11:56:01 no prompt server found, can not continue


Add Smarts strings for creation of secondary and tertiary alcohols

PR Summary:
Added Smarts strings for creation of secondary and tertiary alcohols.
Added test gro and top files for t-butanol and isopropanol.
PR Checklist

[x] Includes appropriate unit test(s)
[x] Appropriate docstring(s) are added/updated
[x] Code is (approximately) PEP8 compliant
[ ] Issue(s) raised/addressed?

Resolved the merge conflict. If all the tests pass, I am ready to merge.


[zh] sync 2023-05-18-seccomp-profiles-edge.md

Add zh text to this blog:
content/zh-cn/blog/_posts/2023-05-18-seccomp-profiles-edge.md

See preview please.

/approve


Missing script: "start"

Hej Leo,
I am giving a go and trying to get your application to run after I have followed your instructions.
On "npm start" I get the following error:
npm ERR! Missing script: "start"
npm ERR!
npm ERR! Did you mean one of these?
npm ERR!     npm star # Mark your favorite packages
npm ERR!     npm stars # View packages marked as favorites
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

Would you be ok for you to give help me out to get it up and running, I would appreciate the help?
I thank you in advance.

Hi Edineu. Is your backend running? In this case, you can try running a specific platform (IOS or android) .
or try : npx expo start. Let me know if now you got success.

Hey Leo,
Thank you for the reply.
I didn't quite get the 'back-end' running properly -  I am stuck on how to add my own credentials after I have install the dependencies:
Edit your '.env.example' to '.env' and add your credentials
DATABASE_URL="postgresql://server:password@localhost:5432/databasename?schema=public"
I did edit the '.env.example' to '.env, but not sure how do i change the credentials on the link provived - I am missing something? And how do I add my own credentails?
I appreciate the help.

Hey man! So about the database credentials.  You should create your own database and set up the credentials. When you run the server Prisma will automatically create the table using the schema. After that when you run the mobile application or the web app. you'll add the initial data through the server and send the data for a mailtrap account
(Need also your own account).
Basically, credentials are made up of password, port and database name
DATABASE_URL="postgresql://server:password@localhost:5432/databasename?schema=public"
the structure is like this
-- CreateTable CREATE TABLE "feedbacks" (     "id" TEXT NOT NULL,     "type" TEXT NOT NULL,     "comment" TEXT NOT NULL,     "screenshot" TEXT,     CONSTRAINT "feedbacks_pkey" PRIMARY KEY ("id") );
Let me know if you need more details,  Will be a pleasure to understand your needs and guide you!


Adding 4.13.23 to default install stream

Which issue this PR addresses:

This is part of ARO-2783
What this PR does / why we need it:

This will set 4.13.23 as default version for local dev installations
Test plan for issue:

NA
Is there any documentation that needs to be updated for this PR?

NA

LGTM

/azp run ci

Out of curiosity why X.Y.23
This was the version that has been GA-ed and is stable for more than a month now.
Were you able to spin up a cluster with the local RP using this setting and is this a useful test that I'm suggesting?
This is a useful test as this change will specifically impact local dev cluster installation. I will comment on the cluster creation once done.


Performance improvements related to startup of Kernels

Summary of most of the Perf Improvements added in November release

#7903
https://github.com/microsoft/vscode-jupyter/pull/8342
https://github.com/microsoft/vscode-jupyter/pull/8238
https://github.com/microsoft/vscode-jupyter/pull/8282
https://github.com/microsoft/vscode-jupyter/pull/8291
https://github.com/microsoft/vscode-jupyter/pull/8317
https://github.com/microsoft/vscode-jupyter/pull/8334

Issue used to track perf improvements made in Nov

Nothing to test, this is just a summary issue.


Write inital tests

Player interaction

[x] Focus set to bench on collision
[x] Player can break bench by attacking it
[ ] Break animation plays on low health
[ ] Bench despawns when out of health

For now I've left the second two tests off until the systems driving them are stabilized.


PyPI package consolidation

I'm the (unresponsive) author of the ConcurrentLogHandler.  I see that you have a package named concurrent-log-handler and just continued the version numbers from where I left off.  Thanks for that.  I switched jobs several times since first writing this code base and no longer need it or even have an easy way to test it anymore.  But I'm glad to see that others have found a use for it; thanks for stepping up.  My apologies for my unresponsiveness.
I've updated the LauchPad project page (https://launchpad.net/python-concurrent-log-handler) to link to your github repo in both the description and via an "announcment".   (Still wish there was a way to make it a bit more obvious, but I think it's adequate.)   Unfortunately, I don't think I can update anything on the ConcurrentLogHandler package page to tell others to use the new package.
Ultimately, it would be nice if there's a way to make the one package alias to the other.  (So that anyone does a "pip install" of either package name would get the latest version.)
Looks like my only option would be to submit a new package that updates the description text, but that seems silly.   Are you aware of any other options?
BTW, I've made you a maintainer of ConcurrentLogHandler (but glad to upgrade that to owner, if you want to take it over.)  Pushing the same code to both package I suppose would be an option, but not sure what's the most ideal.  I'm not a PyPi expert so perhaps there's mechanisms that would help out here that I'm unaware of.   Open to suggestions.

Why not re-upload the new package to the old namespace https://pypi.org/project/ConcurrentLogHandler/


code review

In construtor of rai::uint128_union from string,  if the string is invalid,  it will construct a uint128_union  with random data, i think it is better to set to zero in this situation. (uint256_union&uint512_union have the same problem)
rai::uint128_union::uint128_union (std::string const & string_a)
{
    decode_hex (string_a);
}

bool rai::uint128_union::decode_hex (std::string const & text)
{
    auto error (text.size () > 32);
    if (!error)
    {
        std::stringstream stream (text);
        stream << std::hex << std::noshowbase;
        rai::uint128_t number_l;
        try
        {
            stream >> number_l;
            *this = number_l;
            if (!stream.eof ())
            {
                error = true;
            }
        }
        catch (std::runtime_error &)
        {
            error = true;
        }
    }
    return error;
}

I'm pretty sure that since this is a union, it will be zero initialized by default.

i did a test, here is result:
-----------------------------------------code---------------------------------
int main()
{
rai::uint128_union t1("01234567890123456789012345678901");
std::cout<<t1.to_string()<<std::endl;
rai::uint128_union t2("012345678901234567890123456789012345");
std::cout<<t2.to_string()<<std::endl;

return 0;

}
---------------------output------------------------
[root@US1 nano]# ./a.out
01234567890123456789012345678901
03000000000000000400000000000000
[root@US1 nano]#

It looks like this constructor is only used with a constant argument, so it's not an immediate issue. In many of the uses, it would be inconvenient to use decode_hex directly. Maybe we should throw an exception if decode_hex fails.

uint128_union taking a string is never used and should be removed.
Since we're "kinda" not using exceptions except internally in functions, ledger_constants (the only user of the string constructor for uint256_union) could be rewritten to use decode_hex explicitly and check the bool return value. In other words, remove the string c'tor there as well.


No color output, --colors always does not work

tealdeer v1.4.1 (Linux)
tried to use
tldr --colors always ls

yet don't get any colour at all.
Regular tldr gives colour as expected.

:+1:


FROM java:8 on MacOS Sierra

Scanner failed to build for me on MacOS X Sierra (10.12.5). Changing Dockerfile line 1 to
FROM: java:8
allowed a successful build.

Trying this now with the existing Java 7 base to see how it goes. I'm also on Sierra.
Not sure why building this on Mac makes a difference, though, as Java 7 is the foundation for the Docker container itself and has nothing to do with the host. What exactly are you seeing as a failed build?

Just tested on my local system with Java 7 as the foundation and didn't see anything strange. I did have to add the following to sonar-runner.properties just to have it not fail to run, but apparently this isn't unusual (but I likely should have more reasonable, usable defaults, at least):
sonar.projectKey=myprojectkey
sonar.projectName=My Project Name
sonar.projectVersion=1
sonar.sources=.

Hey Ryan,
The build of both containers goes fine, but when I run a scan, I get the
output below. I using that minimal sonar-project.properties (different
values, but same keys). Using 'FROM java:8' cures the problem, as noted.
(I'm operating pretty much fire-and-pray here, this is a smoke test and I
haven't dug into the sonar project at all.) FWIW, I'm running latest Docker
for Mac (Edge/community edition), although I'm guessing that's irrelevant.
And while on the subject -- thanks for doing this work, I'm a software
engineer at the IT Services department at UT here in Austin, and being able
to run Sonar on a developer's workstation using Docker is probably all my
customers will need for the foreseeable future. I'm hoping to use it to
launch a conversation / community of practice about code quality and
software craftsmanship, and budgets being what they are, the price is
right. If you find yourself in Austin, shoot me a text, I'll buy you a beer
(maybe even some BBQ!).
Best regards,
Ned
INFO: Scanner configuration file:
/root/sonar-scanner-2.5.1/conf/sonar-runner.properties
INFO: Project configuration file: /root/./src/sonar-project.properties
INFO: SonarQube Scanner 2.5.1
INFO: Java 1.7.0_111 Oracle Corporation (64-bit)
INFO: Linux 4.9.31-moby amd64
INFO: User cache: /root/.sonar/cache
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/sonar/batch/bootstrapper/EnvironmentInformation : Unsupported
major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at
org.sonar.runner.impl.IsolatedClassloader.loadClass(IsolatedClassloader.java:82)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
org.sonar.runner.batch.DefaultBatchFactory.createBatch(DefaultBatchFactory.java:33)
at
org.sonar.runner.batch.BatchIsolatedLauncher.start(BatchIsolatedLauncher.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.sonar.runner.impl.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:61)
at com.sun.proxy.$Proxy0.start(Unknown Source)
at org.sonar.runner.api.EmbeddedRunner.doStart(EmbeddedRunner.java:251)
at org.sonar.runner.api.EmbeddedRunner.start(EmbeddedRunner.java:187)
at org.sonar.runner.api.EmbeddedRunner.start(EmbeddedRunner.java:182)
at org.sonarsource.scanner.cli.Main.execute(Main.java:76)
at org.sonarsource.scanner.cli.Main.main(Main.java:66)
On Mon, Jun 26, 2017 at 6:32 PM, Ryan Mitchell<EMAIL_ADDRESS>wrote:

Just tested on my local system with Java 7 as the foundation and didn't
see anything strange. I did have to add the following to
sonar-runner.properties just to have it not fail to run, but apparently
this isn't unusual (but I likely should have more reasonable, usable
defaults, at least):
sonar.projectKey=myprojectkey
sonar.projectName=My Project Name
sonar.projectVersion=1
sonar.sources=.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/newtmitch/docker-sonar-scanner/issues/3#issuecomment-311210421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS2ou4GEISAJReIp81Sz4ikp-Brkuko7ks5sID-CgaJpZM4OFTrO
.

--
Edward C Horvath, PhD
Skype/Twitter/LinkedIn: NedHorvath
Mobile +1<PHONE_NUMBER>
"I'm confused."
"It's a big club. We should get T-shirts." - The Doctor

@ned-horvath looks like you're analysing a Java8 project (major.minor 52.0) with a Java7 SDK as per Docker image.
As such requiring Java 8 looks sensible, as does the whole thing working when basing it off of the java:8 image.

@vyo Good catch. Regardless of what my repo uses now, it makes sense it should probably update to Java 8. Let me make that change, test it, and commit. The blog entry is right - no reason to stick on 7 if there's no specific reason to.

@ned-horvath Thanks for the detail. I'm guessing based on your statement that you built both containers that the Dockerfile.server build is the problem - it's pulling sonarqube:latest, I noticed, while the README for the project actually gives you the command line for starting sonarqube:5.2. I did the latter when I tested, which didn't show an error. Per @vyo's comment, my guess is that using the latest version of Sonar Qube would exhibit the problem you're seeing. I think that's confusion between my README and the server Dockerfile that I have in the project. I'll fix the README accordingly, as well as update the scanner's Dockerfile for Java 8 after doing a quick test on my side.
Glad you're getting use out of this container - I built it just to fiddle around with it and see how it worked - obviously I don't use it very often myself. That said, I'm also Austin-based, software dev / product / fullstack type guy. Perhaps we should meet up sometime, I can never turn down a beer, but I'll require I buy you one as well for troubleshooting my crap-code. :)

Just confirmed that when I run from the included Dockerfile.server as a base, it shows the "unsupported major/minor" version thing you're seeing. I believe my suspicion as to the problem is correct. If you use Sonarqube:5.2 per the README, it should work fine. I'm going to update to Java 8 to see if the problem is corrected as you both have seen. I'm sure it will, but I like to see for myself. :)

Updated, ran and confirmed working. Thanks for the help, guys.

Thanks again for doing this in the first place, Ryan!
On Wed, Jun 28, 2017 at 3:06 PM, Ryan Mitchell<EMAIL_ADDRESS>wrote:

Updated, ran and confirmed working. Thanks for the help, guys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/newtmitch/docker-sonar-scanner/issues/3#issuecomment-311772903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS2ou3k5jIZEqp21lmprrIl4l4J88yppks5sIrI5gaJpZM4OFTrO
.

--
Edward C Horvath, PhD
Skype/Twitter/LinkedIn: NedHorvath
Mobile +1<PHONE_NUMBER>
"I'm confused."
"It's a big club. We should get T-shirts." - The Doctor

For sure - figured I needed to get something out in the community somewhere to give back a bit... :) Drop me a note if you're interested in getting together for a beer. I'm around.


Tidak bisa ter sambung hp yang mau di fastboot sama hp host

Your screenshot attachment is broken, please upload screenshot correctly and use english lang.


Add more items to the drinks menu

Added more items to the drinks menu

[x] Code is well-documented
[x] Code follows the project's code style
[x] Tests have been added or updated

Hey Buddy !! Create PR with UI-Improvement Branch !! You just created it with main branch !!


KAFKA-10035: Safer conversion of consumer timeout parameters

In org.apache.kafka.streams.integration.AbstractResetIntegrationTest:

Corrected types of consumer timeout params: STREAMS_CONSUMER_TIMEOUT  and CLEANUP_CONSUMER_TIMEOUT  from long to int
Type-safe conversion from int to String

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chia7712, @mjsax, @ableegoldman could you please review this fix?

Retest this please.

Test this please

Ok to test

Some follow up nits: The method add10InputElements does not throw any exception and we should remove the throws statement. Also in AbstractResetIntegrationTest in L283 we use Assert.assertEquals(false, cleanResult) that should be Assert.assertFalse(cleanResult) and L607 we use Assert.assertEquals(true, cleanResult); that should be Assert.assertTrue(cleanResult);

In 24456ae addressed comments from @mjsax

@ableegoldman & @mjsax please have a look at updates.

Rebased to resolve merge conflict.
@mjsax could you please give it a second look?

@vvcephei & @mjsax this one seems to get stalled a bit - could you let me know if anything else is to be corrected here or should we move on with retesting the changes?

Retest this please.

Looks like no issues related to the changes in this PR. @mjsax could you please suggest what would be the next thing to do on this one?

@serjchebotarev he's out of office this week, just fyi.

@ableegoldman alright, thanks.


Arabic support

If Kivy is still alive and a strong project, Native arabic support is a must.
No native right to left language support; using Bidi and arabic reshaper modules is a long run, especially for big apps.
supporting it will surely give Kivy more power, and will ease multi-language development in Kivy.
Describe the solution you'd like
this BIDI-Algo and arabic reshaper; mixing it with I8n translation makes it hell of long run, to get a simple arabic/english interface.
this will give kivy a huge boost on supporters and adoption if added.
anyone can do it for us ? Arabic speaking community ?

Help is always welcome, we know about this issue, and there has been attempts at solutions, but no active core-dev speaks/read/write arabic as far as i know, or have the time to focus on that, contributions are welcome, it's probably not going to happen otherwise.

We need RTL and Arabic support. I am ready to help to resolve this issue. @tshirtman

We need RTL and Arabic support. I am ready to help to resolve this issue. @tshirtman

I think the first step would be getting this PR to be merged https://github.com/kivy/kivy/pull/7452 though i think it's mostly tested with indie, it would be nice to test it with arabic as well.

I think the first step would be getting this PR to be merged https://github.com/kivy/kivy/pull/7452 though i think it's mostly tested with indie, it would be nice to test it with arabic as well.

I cant find which part of kivy compiles the first string. If we add arabic_reshaper.reshape and bidi.algorithm.get_display to that part it can convert non-readable RTL words to readable ones; In other hand it dosnt effects on non-RTL (or LTR) languages as you can see blow

Hi @bambier, does the following works for you? (needs Kivy 2.2.0)
Label:
    text: "تشاو موندو"
    font_direction: "rtl"
    font_script_name: "Arab"

Hi @bambier, does the following Its for you? (needs Kivy 2.2.0)
Label:
    text: "تشاو موندو"
    font_direction: "rtl"
    font_script_name: "Arab"

EDIT: FYI, the feature I'm talking about has been added via #8115

Not exactly  what I want...
If we use 'arabic_reshaper' and 'bidi' we don't see that non-RTL fonts breakdown. Also, I feel that few pixels margins and paddings affect texts when we use font_direction
These aren't happening when we use those libraries.

I seem to be able to reproduce the issue with this example:
from kivy.app import App
from kivy.uix.label import Label

text ="""
تشاو موند Hellow world
Hello World!
"""
class MyApp(App):

    def build(self):
        return Label(text=text,
                     font_direction="rtl",
                     font_script_name="Arab",
                     font_name="data/Amiri-Regular.ttf" #Arabic supporting font
                     )

if __name__ == '__main__':
    MyApp().run()

Maybe this issue should be closed as the problem is located in mixed text only. When you don't mix RTL text with LTR text the language support seems to work.

@damascene: That's a useful thing to tell people having trouble - there may be a workaround if you limit how you use the textbox, but mixing languages isn't uncommon. In fact, it is done several times in this GitHub discussion!
So, I think the issue should still remain open.


feat(fe,meta): support logical view

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
close #2317
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes

SQL commands

Release note
Support CREATE VIEW

Not work yet
dev=> create view v as select 1;
CREATE_VIEW
dev=> select * from v;
--
(1 row)

dev=> create table t(x int);
CREATE_TABLE
dev=> insert into t values (1),(2);
INSERT 0 2
dev=> create view vv as select * from t;
CREATE_VIEW
dev=> select * from vv;
--
(2 rows)

Other outstanding tasks:

[ ] drop view
[ ] resolve dependent tables
[ ] consider how to handle * in case of ddl


options.variables final

Hi guys,
this morning I was updating to Flutter 3 but then I rolled back to Flutter 2.10 sue to some incompatibilities.
The problem is that now, even if I removed all the changes, the variables parameter of QueryOptions is marked as final even if in the QueryOption class it's not
Anyone with a similar problem?
Prior this problem, I was capable to do something like this:
final QueryOptions options = QueryOptions(
        document: ...,
        fetchPolicy: FetchPolicy.cacheAndNetwork,
    );

   ...
   ...
   options.variables = {....};

Mh! we have a problem right now that we point to solve before the next week with flutter #1134 However, nothing with final stuff, can you post the error that you receive?
Thanks!

Hi! thanks for the fast reply
The error is simply
'variables' can't be used as a setter because it's final.
Try finding a different setter, or making 'variables' non-final.

and is triggered when I try to assign some value to the variables field of a QueryOptions instance after the initialization.
I always used the graphql package version ^5.0.0. Nothing is changed  but now I cannot assing a value to that field of QueryOptions

@ITASerus we've recently made the query options immutable, instead of updating the variables on the options you should create a new options instance. Sorry for the problem this is causing.

@budde377
oh ok, no problem! Good to know then! I wasn't sure if it was a problem of the library or an error caused by the rollback to flutter 2.10
In any case, thanks for all the effort you all are putting in this library <3


Regarding Search select with real (remote) API data

Thanks for useful demo.
I need Out Put Like below
AccountName
PrimaryPhone EmailAddress
I want to Break the line after first field how toimplement.
I am using the same code then output shown below.
search(term: string): Observable<OptionEntry[]> {
console.log('searching for', term);
return http.get<Account[]>(apiURL, {
params: {
q: term || '',
_sort: 'AccountName,EmailAddress'
}
}).pipe(
map(list => list.map(e => ({
value: e.AccountID,
display: ${e.accountName}${e.primaryPhone }(${e.emailAddress}),
details: {}
}))));
}
};
Current Out Put :
AccountName PrimaryPhone EmailAddress
Please help me for this.

Hi Kyle ,
 not working here.....!!!

@sandyJ1 Can you make an example of the problem you are having, on StackBlitz?  It should be just a smallest example of the problem, not your entire "real" application.

(If anyone experiences a problem like this, please open a new issue with an example that reproduces it!)


bug in calc_gradient_penalty?

https://github.com/caogang/wgan-gp/blob/ae47a185ed2e938c39cf3eb2f06b32dc1b6a2064/gan_language.py#L159
Right before this line, it should be added "gradients = gradients.view(BATCH_SIZE, -1)"?

It's OK in gan_mnist.py, since real_data and fake_data has shape [BATCH_SZIE, OUTPUT_DIM], and Discriminator reshapes input at first.
https://github.com/caogang/wgan-gp/blob/ae47a185ed2e938c39cf3eb2f06b32dc1b6a2064/gan_mnist.py#L100
But, in gan_cifar10.py, Discriminator requires input tensor to have rank 4.
https://github.com/caogang/wgan-gp/blob/ae47a185ed2e938c39cf3eb2f06b32dc1b6a2064/gan_cifar10.py#L89-L93
So computation of gradient_penalty is not correct.
In original(?) implementation Discriminator requires rank 2 tensor.
https://github.com/igul222/improved_wgan_training/blob/master/gan_cifar.py#L71


Set iframe id and name attributes

Hi, first of all, thanks for this nice lib.
I'm trying to integrate this lib with another one (porthole.js) that requires that the iframe got the id and name set.
There is any easy way to do it?
Thanks in advance,

Hi there. Sorry for the very slow reply -- one of our devs moved on to another job and then election season started. See additional comments on your PR.

Fixed in v1.0.0 release eb8d39c


Add missing static_cast

First thank you for making/sharing this library, it works great so far! However, when compiling with -Werror -Wsign-conversion, I'm getting a compiler error due to an implicit std::streamsize -> size_t conversion. Making the conversion explicit with a (presumably forgotten) static_cast fixes this.

By the way I was on mobile earlier so I didn't have a chance to do this, but I invited you to be a contributor to the repo :)


Refactor margin utilities into mixins

wut

the margin classes: .margin-top-basic etc to be generated by a mixin


cloudhop.horse down

cloudhop.horse gives me "Site not found - GitHub Pages" since ~Wednesday.

Go to http://blackhole12.github.io/PonyClicker/


顶部导航栏错位了

Reproduction
https://pinia.vuejs.org/zh/
Steps to reproduce the bug

Expected behavior
应该是没有错位的
Actual behavior
顶部导航栏错位了
Additional information
No response

是网站加载完一样东西之后才开始错位的。

It seems that the English docs have a similar problem.

I can’t reproduce. It looks like the top banner is being blocked by a browser extension. Please don’t use extensions like Adblock on documentations, it’s possible to “trust” the site from the extension

I actually think where this comes from. The changes should be applied during the day


feat: add theme param url behaviour with react-router

Description
makes a theme focused directly thru the url with the help of react-router and searchParams
Closes #66

Yes, I left some refactoring that had to be done, this is not complete yet 👍


v9.02 update mess - redundant information in MQTT

PROBLEM DESCRIPTION
The update process from v9.01 to v9.02 was very tricky (update to latest version using the web interface, in the first attempt the ping timed out and a power cycle was needed, then switching from a strange partition "reboot to Nuki Hub" and initiating the update once again).
Now after successfully managing to upgrade to v9.02, there's a lot of things mixed up in MQTT looking at what is available in Home Assistant now:
Existing device, fine:

New device, unexpected and with redundant entities:

Is this a desired outcome or the result of a faulty update?
I don't get why one would need to have a sub set of entities redundantly available, one named by the lock (as it was for years) and in addition now one named by the Nuki Hub device.
If it's intentional (looks like as somehow the actual Nuki device is referenced as "linked device" at the bottom), I guess it's safe to disable all redundant entities or even delete the whole device, isn't it?
Quite confusing.
Please clarify.
Aside from this, in general, I'd really love to get back to Nuki Hub updates which a) don't create difficulties on really every single update and b) as a result don't waste a huge amount of time (for the first Nuki Hub now already one hour including this issure report). Stable updates are a long time ago unfortunately. Maybe we shouldn't pack too much changes in a minor release, looking at the quantity of 9.02 seems a bit oversized, just my 2 cents.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

[X] Read the Contributing Guide and Policy and the Code of Conduct
[X] Searched the problem in issues
[X] Searched the problem in discussions
[X] Searched the problem in the docs
[ ] Searched the problem in the chat
[X] Device used (e.g., ESP32-S3): ESP32 (LOLIN32 Lite)
[X] Nuki Hub binary firmware version number used: v9.02 (build<PHONE_NUMBER>2.4.1)

[X] Pre-compiled
[ ] Self-compiled

[X] Provide the output of http://nukihubIP/info:

System Information

------------ NUKI HUB ------------
Version: 9.02
Build:<PHONE_NUMBER>2.4.1
Build type: Release
Build date: 2024-11-24
Updater version: 9.02
Updater build:<PHONE_NUMBER>2.4.1
Updater build date: 2024-11-24
Uptime (min): 12
Config version: 902
Last restart reason FW: RequestedViaWebServer
Last restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
Free internal heap: 66976
Total internal heap: 260580
PSRAM Available: No
Network task stack high watermark: 8316
Nuki task stack high watermark: 5088

------------ GENERAL SETTINGS ------------
Network task stack size: 12288
Nuki task stack size: 8192
Check for updates: Yes
Latest version: 9.02
Allow update from MQTT: No
Web configurator username: ***
Web configurator password: ***
Web configurator enabled: Yes
Publish debug information enabled: No
MQTT log enabled: No
Webserial enabled: No
Bootloop protection enabled: No

------------ NETWORK ------------
Network device: Built-in Wi-Fi
Network connected: Yes
IP Address: xxx.xxx.xxx.xxx
SSID: XXX
BSSID of AP: XX:XX:XX:XX:XX:XX
ESP32 MAC address: XX:XX:XX:XX:XX:XX

------------ NETWORK SETTINGS ------------
Nuki Hub hostname: ESP-Nuki-Hub-XXX-XXX
DHCP enabled: Yes
RSSI Publish interval (s): Disabled
Find WiFi AP with strongest signal: Yes
Restart ESP32 on network disconnect enabled: Yes
MQTT Timeout until restart (s): Disabled

------------ MQTT ------------
MQTT connected: Yes
MQTT broker address: xxx.xxx.xxx.xxx
MQTT broker port: 1883
MQTT username: ***
MQTT password: ***
MQTT base topic: xxx
MQTT SSL CA: Not set
MQTT SSL CRT: Not set
MQTT SSL Key: Not set

------------ BLUETOOTH ------------
Bluetooth TX power (dB): 9
Bluetooth command nr of retries: 5
Bluetooth command retry delay (ms): 100
Seconds until reboot when no BLE beacons received: 60

------------ QUERY / PUBLISH SETTINGS ------------
Lock/Opener state query interval (s): 3600
Publish Nuki device authorization log: Yes
Max authorization log entries to retrieve: 5
Battery state query interval (s): 7200
Most non-JSON MQTT topics disabled: No
Publish Nuki device config: Yes
Config query interval (s): 3600
Publish Keypad info: No
Keypad query interval (s): 1800
Enable Keypad control: Yes
Publish Keypad topic per entry: No
Publish Keypad codes: No
Allow checking Keypad codes: No
Max keypad entries to retrieve: 10
Publish timecontrol info: No
Keypad query interval (s): 1800
Enable timecontrol control: No
Publish timecontrol topic per entry: No
Max timecontrol entries to retrieve: 10

------------ HOME ASSISTANT ------------
Home Assistant auto discovery enabled: Yes
Home Assistant auto discovery topic: homeassistant/
Nuki Hub configuration URL for HA: http://xxx.xxx.xxx.xxx

------------ NUKI LOCK ------------
Lock enabled: Yes
Paired: Yes
Nuki Hub device ID: XXXXXXXXX
Nuki device ID: ***
Firmware version: 3.10.7
Hardware version: 4.10
Valid PIN set: Yes
Has door sensor: No
Has keypad: No
Timecontrol highest entries count: 0
Register as: Bridge

------------ HYBRID MODE ------------
Hybrid mode enabled: No

------------ NUKI LOCK ACL ------------
Lock: Allowed
Unlock: Allowed
Unlatch: Allowed
Lock N Go: Allowed
Lock N Go Unlatch: Allowed
Full Lock: Allowed
Fob Action 1: Allowed
Fob Action 2: Allowed
Fob Action 3: Allowed

------------ NUKI LOCK CONFIG ACL ------------
Name: Disallowed
Latitude: Disallowed
Longitude: Disallowed
Auto Unlatch: Disallowed
Pairing enabled: Allowed
Button enabled: Allowed
LED flash enabled: Allowed
LED brightness: Allowed
Timezone offset: Disallowed
DST mode: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed
Single Lock: Allowed
Advertising Mode: Disallowed
Timezone ID: Disallowed
Unlocked Position Offset Degrees: Disallowed
Locked Position Offset Degrees: Disallowed
Single Locked Position Offset Degrees: Disallowed
Unlocked To Locked Transition Offset Degrees: Disallowed
Lock n Go timeout: Allowed
Single button press action: Allowed
Double button press action: Allowed
Detached cylinder: Disallowed
Battery type: Disallowed
Automatic battery type detection: Disallowed
Unlatch duration: Allowed
Auto lock timeout: Disallowed
Auto unlock disabled: Disallowed
Nightmode enabled: Disallowed
Nightmode start time: Disallowed
Nightmode end time: Disallowed
Nightmode auto lock enabled: Disallowed
Nightmode auto unlock disabled: Disallowed
Nightmode immediate lock on start: Disallowed
Auto lock enabled: Disallowed
Immediate auto lock enabled: Disallowed
Auto update enabled: Disallowed
Reboot Nuki: Allowed

------------ NUKI OPENER ------------
Opener enabled: No

------------ GPIO ------------

TO REPRODUCE
Update NH v9.01 to NH v9.02
EXPECTED BEHAVIOUR
No new device in MQTT, no redundant set of entities
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)

Note:
Same update experience with a 2nd Nuki Hub from 9.01 to 9.02.
After ping times out, a physical power cycle of the ESP is needed.
Then, the web interface presents this (after the initial update tab times out long time ago, like http://esp-nuki-hub-door.domain/autoupdate?release=1&release=1&token=5028):

Reboot to Nuki Hub:

Then: nothing has happened, still on 9.01

So second attempt with the green button:

For half a second a two-liner is visible before the page times out (http://esp-nuki-hub-door.domain/autoupdate?release=1&release=1&token=1737). Reloading the default page after a few minutes now gives the 9.02 update.

Now I had to reboot the Nuki Hub once again to make HA entities show up again at all (all unavailable). Besides that, the same mess in MQTT (HA to be precise) of course.
I decided to simply disable all entities (because all of them are redundant end therefore completely useless) of the new additional Nuki Hub MQTT device.
BUT: the second Nuki Hub MQTT device doesn't even has the "linked device" entry: seems another thing is broken here... I'm pretty done with NH updates for today.

I confirm this new "nukihub" device creation with duplicate diagnostic entities created.
I wouldn't call this a "mess", we have a different view of that word. I have experienced real messes in HA, and this not even close to those. I feel your frustration, but let's not exaggerate, you can simply disable those duplicate entities for now, no real production issues.

Been there done that, see

I decided to simply disable all entities (because all of them are redundant end therefore completely useless) of the new additional Nuki Hub MQTT device.

Maybe a bit lost in translation.  Nevermind, "solved" (worked around) that for the moment.

Hi everyone,
i'm not sure whether it's the same issue, but i updated to 9.02 from 9.0 today. I also had to do the ota update process twice, but it worked afterwards.
The problem started after restart of Homeassistant. Now HA is telling me that 'This entity is no longer being provided by the mqtt integration. If the entity is no longer in use, delete it in settings.'
Neither nukihub nor the lock.* entities are active any more. I don't see a duplicate nukihub entity in my setup.
Anyone got an idea how to fix this?

Luckily I don't see that behavior which would be a real issue. But: I did not restart HA yet.
I guess you should at first check in your MQTT broker if the Nuki Hub topics exist and if - once you restart a Nuki Hub - the corresponding topics in the homeassistant domain are created.
Besides the overall update issues I tend to say this is a separate topic.
We'll see how the maintainers will handle this.

So can this be closed then, or does it need further investigation?

Of course it requires further investigation.

I had only 4 entities duplicated. BTW: they're not really duplicates, after the upgrade the ones on the lock were orphaned, I simply deleted them.
Can you show which entities are "duplicated"?

For me all entities remain on the lock, and many have been duplicated to the NH.
Those are the 13 duplicates (another entity ID, same function). Same for another NH:

Those are not duplicate entities, they are orphaned (they're not being updated), since the "live" entities are now on the nukihub device. You simply need to delete them.
Difference is I had 4 of them.

No, lock entities are not orphaned. Continue to work just fine afaics. One lock for example:

IP and FW Update sensors, for example, should only be available on the nukihub device, not on the lock device. There are other 2-3 diag. sensors like that. You should see those orphaned on the lock, and active on the nukihub device.
If that's not the case, @iranl will probably need more info to understand what's happening in your case.
In my case it was very simple, I just needed to delete 4 orphaned sensors from the lock.

That's what it is for all my NHs.
Tell me what is needed in terms of information/logs (or: safely purge all MQTT topics once and restart NHs?).

The new NukiHub device separate from the lock and opener devices are there by design.
This is the proper way of providing hub/coordinator etc. devices in Home Assistant and is for example the same as how it is done by Zigbee2MQTT.
As the Nuki Lock, Nuki Opener and NukiHub are separate devices they should be presented in HA as separate devices,
This actually prevents duplicate entities going forward as previously NukiHub IP/Firmware etc. was provided to HA in both lock and opener devices, causing duplicates for users that used both these devices through one NukiHub device.
This was introduced based on a request in #494 in PR #515
It does cause some orphaned and/or duplicate entities in HA for users upgrading from earlier versions.
To fully remove these you need to search for MQTT topics containing "nuki_ using a program like MQTT Explorer and delete all found topics. Reboot NukiHub afterwards and than remove any orphaned/unavailable entities from the Nuki lock and/or opener device from inside Home Assistant.

I'll have a look at MQTT topics at the weekend. You mean looking for the nuki_ like topics in the homeassistant or the nuki hub root topic?
Curious to see if really only 4 entities are affected. With a bit of entity renaming everything should be back to normal in theory...

In general I would like to be made aware of such changes in the release notes. As I read them. Sometimes twice. And then decide if the amount of changes makes this a 2 minutes stressless update or a one hour pain or something in between.
Better a note than discovering strange behavior (not even consistent: one nuki hub has a link to the lock in HA, the other one does not) afterwards with the need of creating issues.
Fundamental changes usually require such changes to be flagged as breaking change or similar. Better safe than sorry (a little extra note is overall probably less struggle than handling issues I guess).

OK folks @iranl I need a bit more precise instruction on how to check/clean and hopefully finally fix this.

You mean looking for the nuki_ like topics in the homeassistant or the nuki hub root topic?

Otherwise it's literally impossible to detect which entities should be orphaned on the lock device. As mentioned I have potentially 13 new entities on the NH device. Confusing.

To sum up my adventure of the last 3 hours which included fixing a endless reboot issue (https://github.com/technyon/nuki_hub/issues/538#issuecomment-2510231276):

"switch.esp_nuki_hub_door_b_restart_nuki_hub" is still "unknown",
same for "switch.esp_nuki_hub_door_b_nuki_hub_webserver_enabled"

there's no reset or webserver topic in the mqtt "nuki_door_b/maintenance" section which might be the reason for this. The Nuki Hub simply does not create it. It did not no matter which version of NH was running: 9.02 or 9.03-master6.
Done with NH (for today), gosh it totally broke my sunday evening. for nothing.

I purged all topics - both the nuki hub ones as well as the homeassistant autodiscovery ones and restarted the Nuki Hubs.
Afterwards I could somehow solve this. Unfortunately, from time to time redundant device entries of the new Nuki Hub device appear, names like "Unnamed device" or "Wifi signal strength", always with the same set of entities but no connection to the locks, also no manufacturer or model is given. No idea what's the reason for those redundant devices. The corresponding entities are named e. g. sensor.none_nuki_hub_restart_reason where "none" should usually be "esp_nuki_hub_door_b". Maybe it's a MQTT broker mess and outside of NH control, as a matter of fact all this got introduced with the dividing of lock/opener and NH topics/entities into a separate device.
Word. Happy holidays.

Have you checked your YAML for manual MQTT configurations? I'm not sure "restart reason" was ever in the discovery payloads.

No idea what's the point with that. But my only custom sensor is a uptime sensor which was not available out of the box in the past. So those restart ones are stock.

The point is that you have a mess in your configuration and/or MQTT broker.
NH autodiscovery entities are ONLY the ones in the device page (see below): please show the entire device page with ALL entities, and highlight the entities there that are unavailable.

These are the manual entities I configured for NH:
mqtt:
  sensor:
    # sensors for Nuki Hub
    - name: "Portoncino Log"
      state_topic: "nuki_hub/maintenance/log"
    - name: "Portoncino Uptime"
      state_topic: "nuki_hub/maintenance/uptime"
      device_class: duration
      unit_of_measurement: min
    - name: "Portoncino Free Heap"
      state_topic: "nuki_hub/maintenance/freeHeap"
    - name: "Portoncino Restart Reason FW"
      state_topic: "nuki_hub/maintenance/restartReasonNukiHub"
    - name: "Portoncino Restart Reason ESP"
      state_topic: "nuki_hub/maintenance/restartReasonNukiEsp"

@alexdelprete The MQTT log & uptime are now included in auto-discovery. Available heap and the two restart reason entities still have to be configured entirely manually.
@bcutter Please check your configuration again. The restart reason has to be configured in your YAML somewhere (maybe a package?).

I don't get what we are talking about here. I just mentioned I managed to solve the initial redundant information by doing a full MQTT topics purge of all NH related HA autodiscovery topics as well as the NHs original topics, then restarted the NHs. I then removed the former unavailable entities on the lock devices.
Still on the HA side from time to time there pops up a new MQTT device in the MQTT integration with the very same set of entities like the new NH device introduced with 9.02.
So the issue's current name for me is "9.02 update mess - redundant information in MQTT integration in Home Assistant" and therefore very likely outside of this project's scope. MQTT/HA related, not NH.
Anyway it's a bit funny that 3 weeks after my comprehensive post with all the MQTT topics someone's now picking a detail and yelling "ESP reset is a custom thing, it's a custom thing!" :-D It made me smile :-)
As checked twice and proven already, my only YAML based custom MQTT entities related to locks are about uptime - a thing from the past. Everything else comes from NH via MQTT, so do the ESP reset topics and entities (_restart_reason and _restart_reason_esp). I have no idea where this would have been configured, maybe directly in NHs web interface. But as I'm discussing with project members here you would be aware of this I think.
locks.yaml
# Für Schlösser

# Am 2023-02-12 angelegt als Zusatz-Sensor um die Laufzeit der Nuki Hub-ESPs zu überwachen
# Gem. https://community.home-assistant.io/t/nuki-hub-firmware-for-the-esp32/417572
# Gem. https://www.home-assistant.io/integrations/sensor.mqtt/
mqtt:
  sensor:
    - name: "schloss_door_a_uptime_nukihub"
      state_topic: "nuki_door_a/maintenance/uptime"
      value_template: "{{ value }}"
      unit_of_measurement: Minuten
      unique_id: xyz
      state_class: total
      icon: mdi:clock
      device:
        identifiers: nuki_XXXXXXXX
      entity_category: diagnostic
    - name: "schloss_door_b_uptime_nukihub"
      state_topic: "nuki_door_b/maintenance/uptime"
      value_template: "{{ value }}"
      unit_of_measurement: Minuten
      unique_id: xyz
      state_class: total
      icon: mdi:clock
      device:
        identifiers: nuki_YYYYYYYY
      entity_category: diagnostic

So hopefully we won't waste more time here for irrelevant side discussions.
In case the redundant (yes they are and as long as they do I'll call them redundant) ghost devices pop up again I can publish the screenshots here so you might believe me. For the last times I instantly deleted those devices.

So you don't think there is bug in NH anymore but there is a problem with your HA install/the MQTT integration? Then we should close the issue.

Well, just tell me. Are the redundant/ghost devices a symptom created by NH 9.02 update (first seen when updating to 9.02) and the issue is within MQTT or even HA or is it an NH issue? I have indicators for both, not sure.

The MQTT log & uptime are now included in auto-discovery. Available heap and the two restart reason entities still have to be configured entirely manually.

That's exactly what I wrote in my post my friend. :)
@bcutter frankly speaking, with all due respect, your posts are really confusing and misleading, you talk about confusing issues, messing up everything, not giving any valuable info to allow us to help. And on top of this, the tone of your posts are really disturbing, you criticize the project like it was a commercial one that you paid for, suggesting there are bugs that are non-existent, while the problem is your HA configuration most probably.
So let me be very clear: this absurd and confusing thread will be closed, and if you still have issues, open a new one, but you'll have to be VERY SPECIFIC on the issue, you'll need to provide all the information needed to devs in order to REPRODUCE the issue, otherwise it will be impossible to help and it will be closed again.
Merry Christmas.

I think people are not reading things precisely (which happened to you too, see the start of your post). For example you were talking about ghost entities while I see ghost devices etc.
Then you come up with "these specific two topics (I had posted 3 weeks ago...) are not auto generated", pointing a few meters next to what this issue is about. That's confusing to me.
But well I think everyone is doing his best and I'm glad this great project exists. I'm lucky I finally have a stable release with 9.05 again after a lot of trouble in the past weeks. Hopefully my beta testing times are over for quite a while now ;-)

As mentioned I will provide screenshots once the ghost devices re-appear again. Precisely as requested: lock device, Nuki hub device, Nuki hub ghost device(s).

I think people are not reading things precisely

Ever thought that the cause is that you write in a very confusing way?
But let's agree to disagree and move forward.

I don't see writing in a confusing way. For example I provided all information regarding custom MQTT entities - extensively - after I was blamed "you must have configured it manually!". After I provided proof no one even responds to that information.
Ah well. Just be patient and wait for my ghost device screenshots.
As this is now a meta discussion on how people read and interpret information here, every additional word until then is a waste of time for the one writing and the ones reading them. I'm out, finger's crossed the redundant devices will never appear again.

For example I provided all information regarding custom MQTT entities - extensively - after I was blamed "you must have configured it manually!". After I provided proof no one even responds to that information.

You have no idea (or weird idea) of what a "proof" is probably. You said you had unavailable entities and we told you that those were NOT created by NH autodiscovery (check source code before replying), so logically we replied telling you that the ONLY rational reason is that you configured manual MQTT entities, but you said "no I didn't" and you think that's a PROOF. Then you're here telling us to "wait" for ghost devices to appear...ROTFL. We're not ghostbusters. :)
But I agree with you on last stament: this whole thread was/is just a waste of time, we live in two different multiverses from a technical standpoint. Keep chasing your ghost devices, but don't expect us to be able to help you.

Doing a system wide (VS Code takes care perfectly) search for "mqtt:" and checking all results for any lock/Nuki hub related sections and providing the only one found is the best I can do.
But as you are one of the "I need to have the last word in every discussion" character you will surely have another idea on this. Welcome on my friend's list.

@alexdelprete Regarding the YAML: I answered based on the initial post before the edits (got it via e-mail).


Update webpack.client.js

Improvements:
Clear Comments: Each section includes concise comments explaining its purpose.
Readable Formatting: Proper indentation and alignment enhance clarity.
Consistent Style: Keys, values, and array items are consistently formatted.
Professional Tone: Explanations are tailored for developers reviewing or maintaining the code.

this not in development


Request to EMS service has failed, unable to set FPA token

ChatClient.create with a token returns with error "Request to EMS service has failed, unable to set FPA token" . *The same works with IOS. The code used to work 2 months ago. I enabled the log using ChatClient.setLogLevel(android.util.Log.DEBUG). By this is a prototype client we coded using twilio-chat-demo as base code. As per the logs, I see the code attempts to send requests >>
trying to sendRequest to https://ems.us1.twilio.com/v1/token.. and failed in the end. Not able to make out the cause. Requesting any insight on this problem.
Here are the logs >>
13:05:37.589 D/jni_mate(18758): Got method ID 0x89a18a78 for method onError(Lcom/twilio/chat/ErrorInfo;)V
09-25 13:05:37.612 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:37.611 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:37.612 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:37.612 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:37.633 D/TWC: TNWebsocket(18758):<PHONE_NUMBER> | 09/25/13:05:37.633 | DEBUG    | 9      | TNWebsocket | Trying to establish connection to: https://tsock.us1.twilio.com
09-25 13:05:38.048 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:38.048 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:38.048 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:38.048 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:38.384 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:38.384 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:38.384 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:38.384 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:38.714 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:38.714 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:38.714 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:38.714 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:39.056 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:39.056 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:39.056 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:39.056 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:39.408 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:39.408 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:39.409 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:39.409 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:39.804 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:39.804 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:39.804 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:39.804 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:40.074 D/TWC: TNWebsocket(18758):<PHONE_NUMBER> | 09/25/13:05:40.073 | DEBUG    | 9      | TNWebsocket | Trying to establish connection to: https://tsock.us1.twilio.com
09-25 13:05:40.113 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:40.113 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:40.113 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:40.113 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:40.442 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:40.442 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:40.442 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:40.442 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:40.763 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:40.763 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:40.763 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:40.763 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:41.100 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:41.100 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:41.100 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:41.100 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:41.441 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:41.440 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:41.441 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:41.441 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:41.755 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:41.755 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:41.755 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:41.755 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:42.069 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:42.069 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:42.069 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:42.069 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:44.423 D/TWC: TNWebsocket(18758):<PHONE_NUMBER> | 09/25/13:05:44.423 | DEBUG    | 9      | TNWebsocket | Trying to establish connection to: https://tsock.us1.twilio.com
09-25 13:05:47.405 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:47.405 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:47.405 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:47.405 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:47.703 I/TWC: TNHttpTransportClient(18758):        -2142369504 | 09/25/13:05:47.703 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:47.703 I/TWC: TNRawHttp(18758):        -2142369504 | 09/25/13:05:47.703 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:48.008 I/TWC: TNHttpTransportClient(18758):        -2144458464 | 09/25/13:05:48.008 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:48.008 I/TWC: TNRawHttp(18758):        -2144458464 | 09/25/13:05:48.008 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:48.318 I/TWC: TNHttpTransportClient(18758):        -2145502944 | 09/25/13:05:48.318 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:48.318 I/TWC: TNRawHttp(18758):        -2145502944 | 09/25/13:05:48.318 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:48.585 I/TWC: TNHttpTransportClient(18758):        -2143413984 | 09/25/13:05:48.585 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:48.585 I/TWC: TNRawHttp(18758):        -2143413984 | 09/25/13:05:48.585 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:48.912 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:48.911 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:48.912 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:48.912 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:49.211 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:49.211 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:49.211 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:49.211 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:49.475 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:49.475 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:49.475 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:49.475 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:49.812 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:49.812 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:49.812 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:49.812 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:50.120 I/TWC: TNHttpTransportClient(18758):        -2140280544 | 09/25/13:05:50.120 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:50.120 I/TWC: TNRawHttp(18758):        -2140280544 | 09/25/13:05:50.120 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:50.402 I/TWC: TNHttpTransportClient(18758):        -2136102624 | 09/25/13:05:50.401 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:50.402 I/TWC: TNRawHttp(18758):        -2136102624 | 09/25/13:05:50.402 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:50.782 I/TWC: TNHttpTransportClient(18758):        -2135058144 | 09/25/13:05:50.782 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:50.782 I/TWC: TNRawHttp(18758):        -2135058144 | 09/25/13:05:50.782 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:51.094 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:51.094 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:51.095 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:51.095 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:51.361 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:51.361 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:51.361 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:51.361 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:51.808 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:51.808 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:51.808 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:51.808 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:52.141 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:52.141 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:52.141 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:52.141 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:52.422 I/TWC: TNHttpTransportClient(18758):<PHONE_NUMBER> | 09/25/13:05:52.422 | INFO     | 6      | TNHttpTransportClient | trying to send request to: https://ems.us1.twilio.com/v1/token
09-25 13:05:52.422 I/TWC: TNRawHttp(18758):<PHONE_NUMBER> | 09/25/13:05:52.422 | INFO     | 7      | TNRawHttp | trying to sendRequest to https://ems.us1.twilio.com/v1/token
09-25 13:05:52.766 E/MSG_CLIENT_MessageClient(18758): TWILIOM Error creating Twilio Chat Client: Request to EMS service has failed, unable to set FPA token
Thanks
Murali

Looks like you don't have internet access?

Hi, please try 4.0.0-rc11 and send your feedback.

Closing as there is no response.


AVS 2023-09-01 SDK generation

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Attestation


Valid return?

I was checking the page that minIP returns, and I noticed a few things I thought I'd bring up.
I'm not sure if these things are needed, but it seems like they should be.

Shouldn't there be a Content-length header?
Shouldn't headers end with a CR LF, instead of just a newline?

This is more of a proof-of-concept than anything else so HTTP specs were not taken into consideration. It was just the easiest way to see the the TCP stack was functioning properly.


Improve the readability of function definition

This is inspired from the behavior of the Java extension. So currently, for example, if my mouse hovers on a function, a docstring popup as the following displays:

I think it is unslightly, compared to "docstring" I get from the Java extension below, and not to mention there are many docstring styles, which creates inconsistency.

This may relate to microsoft/vscode-python#6676. I think we can simply parse the docstrings before displaying them - implementing different parsers for different styles. I'm happy to work on this issue.

current implementation just tries to reproduce the plaintext style in markdown.
docstirng conversion is in pyright.  https://github.com/microsoft/pyright/blob/ed13daf16f2621600a0f1ca67fdd18aa1b79d98b/packages/pyright-internal/src/analyzer/docStringConversion.ts#L558


Implement vectorized hashing for DictionaryArray types

Which issue does this PR close?
Re https://github.com/apache/arrow-datafusion/issues/790
Rationale for this change
In order to implment the GroupBy approach described https://github.com/apache/arrow-datafusion/issues/790, hashing needs to support all types that the existing grouping operator does, including dictionary arrays, including DictionaryArrays.
Also, support for hashing dictionaries is also necessary (but I don't think sufficient) to support joining on DictionaryArray columns
What changes are included in this PR?
Implement hashing for DictionaryArray types by hashing the values in the dictionary
Are there any user-facing changes?
No (not yet), and no API changes

Verified that this change fixes https://github.com/apache/arrow-datafusion/issues/821 : https://github.com/apache/arrow-datafusion/issues/821#issuecomment-892795370