Random numbers

I would like the Num class to have 'rand' and 'seed' static methods.
I like the Wren language very much. ;-)

I'm working on those (and others) Num class methods.
I will submit the pull request in the very next days.

Since random number generation implies some (hidden) mutable state, this may be a case where a separate class is a better fit. Something roughly like:
class Random {
  new { /* Automatically seed... */ }
  new(seed) { ... }

  // Methods for getting random values...
}

That way users have clear control over where that state lives, can maintain separate PRNGS, etc.

I'm working on those (and others) Num class methods.

You can always send those out as individual pull requests. Incremental changes generally make everyone's life easier. :)

Since random number generation implies some (hidden) mutable state, this may be a case where a separate class is a better fit.

I started and added the PRNG feature to Wren some weeks ago, if you recall, but left incomplete (due to other priorities).
Now that we have modules, I was thinking just the same that having a separate PRNG as class instances would be a better choice.
First of all, it would be a first step in trying the module support itself. Moreover, it would be (eventually?) part of the standard Wren-lib... :dancer:

You can always send those out as individual pull requests. Incremental changes generally make everyone's life easier. :)

Yep, I will send them and leave the PRNG support as a module class, then. :wink:

I guess this one can be closed, now that we have module support and bitwise operations.
A class like this is enough to implement a fast and easy PRNG
class Random {

  new {
    _x = 123456789
    _y = 362436069
    _z = 521288629
    _w = 88675123
  }

  new(seed) {
    _x = seed
    _y = 362436069
    _z = 521288629
    _w = 88675123
  }

  next {
    var t = _x ^ (_x << 11)
    _x = _y
    _y = _z
    _z = _w
    _w = _w ^ (_w >> 19) ^ t ^ (t >> 8)
    return _w /<PHONE_NUMBER>
  }

}

Yeah, probably. I certainly want to keep the core lib minimal, and RNGs are something that we can exclude from core.
At the same time, it's really useful to have one widely available. Right now, Wren has no concept of a "standard library", meaning a module that you have to import to use but that physically ships with Wren. Everything in core is implicitly imported.
I'm not sure if I even want to have such a concept because I worry it's a slippery slope to having lots of standard libraries. But, at the same time, a nice PRNG is really useful to a lot of programs, especially given that Wren has an eye towards games.
I'll leave this open for now, but I don't intend to take any action on it until other stuff is further along.

But, at the same time, a nice PRNG is really useful to a lot of programs, especially given that Wren has an eye towards games.

Yep, in fact that's the reason why I started working on adding a PRNG to Wren some weeks ago.
However, the random number generator can be easily provided in some way thru' the embedding API by the host that is running Wren's VM (and you will use that API when developing a game or such).
Also, providing a PRNG raises another question: which one? A simple linear congruential generator could be enough for some but too simple for others. Implementing a "complex" generator would easily go against Wren's philosophy to keep everything reasonably simple.
I feel it won't be worth the effort, in the end. It's better to leave the pleasure to implement it to anyone who needs it.
Maybe we could create a snippets library, over time.

However, the random number generator can be easily provided in some way thru' the embedding API by the host that is running the Wren's VM (and you will use that API when developing a game or such).

True!

Also, providing a PRNG raises another question: which one?

Yeah, excellent point.

This is probably something that would make sense to include in wren-io.
cc @zeckalpha


E           AttributeError: 'str' object has no attribute 'year'

src/cffconvert/cff_1_0_x/apalike.py:24: AttributeError
===================================================================== short test summary info =====================================================================
FAILED tests/cff_1_0_3/a/test_apalike_object.py::TestApalikeObject::test_as_string - AttributeError: 'str' object has no attribute 'year'

It seems there may be some carry-over from the JSON based schema used in the tests preceding the error. Caching related maybe?

Somehow YAML seems to remember that I'm setting the parser to read dates as strings when cff-version is 1.2.0 or 1.3.0. If you then come back to it later with a different cff file that has cff-version 1.1.0 or 1.0.x, it uses the parser configured for later cff versions.

Fixed in PR #344, closing


[bulk] Validation: Metadata and Absolute Links

Docs Build status updates of commit 2fd6c74:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/preview/cosmos-readme.md
:bulb:Suggestion
View (azure-java-preview)
Details

docs-ref-services/preview/cosmos-readme.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 71, Column 391: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 108, Column 57: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/databases-containers-items' will be broken in isolated environments. Replace with a relative link.
Line 114, Column 45: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/distribute-data-globally' will be broken in isolated environments. Replace with a relative link.
Line 119, Column 49: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/set-throughput' will be broken in isolated environments. Replace with a relative link.
Line 126, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/request-units' will be broken in isolated environments. Replace with a relative link.
Line 133, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/partitioning-overview' will be broken in isolated environments. Replace with a relative link.
Line 241, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' 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

Docs Build status updates of commit 3c67190:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/preview/cosmos-readme.md
:bulb:Suggestion
View (azure-java-preview)
Details

docs-ref-services/preview/data-appconfiguration-readme.md
:bulb:Suggestion
View (azure-java-preview)
Details

docs-ref-services/preview/cosmos-readme.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 71, Column 391: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 241, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/data-appconfiguration-readme.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 32, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 411, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-java-spring-app' 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

Docs Build status updates of commit 5e859ba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/preview/cosmos-readme.md
:white_check_mark:Succeeded
View (azure-java-preview)

docs-ref-services/preview/data-appconfiguration-readme.md
:white_check_mark:Succeeded
View (azure-java-preview)

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

Docs Build status updates of commit e632ec1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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

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

File
Status
Preview URL
Details

docs-ref-services/preview/cosmos-readme.md
:white_check_mark:Succeeded
View (azure-java-preview)

docs-ref-services/preview/data-appconfiguration-readme.md
:white_check_mark:Succeeded
View (azure-java-preview)

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

Global effort to fix build validation errors
@kushagraThapar, @Shanfang
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!

@kushagraThapar, should we back out all changes to absolute links on readme.mds on the azure-docs-sdk-java repo? The validation team is working to clear the build warnings from this repo. I will loop in our content manager @v-andreaco so that we can coordinate how this should be best handled.

@kushagraThapar
Thanks so much for your patience! We have a large team working on these issues, so sometimes announcements slip through. I really appreciate you taking the time to explain, and we'll send out a stronger note to the team to back these changes up.
I think I asked in another PR if metadata changes will also be overwritten, and I don't remember seeing if that was answered. Should our team revert all changes to these files, or just the content edits, and metadata changes can go through?
Thanks again for being so helpful!! I know your time is valuable, and we really appreciate you taking the time to help us!

@v-andreaco - metadata changes can still go through, but my concern is this:
We release our SDKs once every month (on usual cadence), and sometimes twice in a month. With every release, our docs go out as part of the release process, which I am not sure will keep the meta data changes that your team is making or not.
One way to find out is to merge one of the PRs for the metadata changes, and see in May 2nd week, (once we release), if they will be kept or erased. Let me know if this works or not !

@kushagraThapar
That sounds like a great idea! Can we test with this one?

@kushagraThapar and @v-andreaco I have backed out the content changes and left metadata in place for testing on this PR.

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

File
Status
Preview URL
Details

docs-ref-services/preview/data-appconfiguration-readme.md
:warning:Warning
View (azure-java-preview)
Details

docs-ref-services/preview/cosmos-readme.md
:bulb:Suggestion
View (azure-java-preview)
Details

docs-ref-services/preview/data-appconfiguration-readme.md

Line 23, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 24, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 32, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-dotnet-core-app#create-an-app-configuration-store' will be broken in isolated environments. Replace with a relative link.
Line 48, Column 65: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 9: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 6: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 138, Column 30: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/rest-api-authorization-azure-ad#roles' will be broken in isolated environments. Replace with a relative link.
Line 409, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-java-spring-app' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/cosmos-readme.md

Line 16, Column 64: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/sql-api-sql-query' will be broken in isolated environments. Replace with a relative link.
Line 16, Column 92: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 115: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/introduction' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 391: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 57: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/databases-containers-items' will be broken in isolated environments. Replace with a relative link.
Line 115, Column 45: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/distribute-data-globally' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 49: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/set-throughput' will be broken in isolated environments. Replace with a relative link.
Line 127, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/request-units' will be broken in isolated environments. Replace with a relative link.
Line 134, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/partitioning-overview' will be broken in isolated environments. Replace with a relative link.
Line 240, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/performance-tips-java-sdk-v4-sql?tabs=api-async' will be broken in isolated environments. Replace with a relative link.
Line 242, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' will be broken in isolated environments. Replace with a relative link.
Line 284, Column 14: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-sql-api-java?tabs=sync' will be broken in isolated environments. Replace with a relative link.
Line 285, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/introduction' 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

Docs Build status updates of commit 6838b8a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/preview/data-appconfiguration-readme.md
:warning:Warning
View (azure-java-preview)
Details

docs-ref-services/preview/cosmos-readme.md
:bulb:Suggestion
View (azure-java-preview)
Details

docs-ref-services/preview/data-appconfiguration-readme.md

Line 23, Column 3: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 24, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 32, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-dotnet-core-app#create-an-app-configuration-store' will be broken in isolated environments. Replace with a relative link.
Line 48, Column 65: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 9: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 6: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 138, Column 30: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/rest-api-authorization-azure-ad#roles' will be broken in isolated environments. Replace with a relative link.
Line 409, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-java-spring-app' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/cosmos-readme.md

Line 16, Column 64: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/sql-api-sql-query' will be broken in isolated environments. Replace with a relative link.
Line 16, Column 92: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 115: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/introduction' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 391: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 57: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/databases-containers-items' will be broken in isolated environments. Replace with a relative link.
Line 115, Column 45: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/distribute-data-globally' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 49: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/set-throughput' will be broken in isolated environments. Replace with a relative link.
Line 127, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/request-units' will be broken in isolated environments. Replace with a relative link.
Line 134, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/partitioning-overview' will be broken in isolated environments. Replace with a relative link.
Line 240, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/performance-tips-java-sdk-v4-sql?tabs=api-async' will be broken in isolated environments. Replace with a relative link.
Line 242, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' will be broken in isolated environments. Replace with a relative link.
Line 284, Column 14: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-sql-api-java?tabs=sync' will be broken in isolated environments. Replace with a relative link.
Line 285, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/introduction' 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

@v-andreaco - yes, I can merge this, thanks!


[Fabric] - Android -Settings -Preferences- Can't change priority mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the special build v1.3.11-2
Log in with any account
Go to settings > Preferences
Try to change "Priority mode"

Expected Result:
Priority mode changed
Actual Result:
Can't change priority mode.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/ae350d26-233c-4cdd-8cee-f4cbd2fe5b2c
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Any option under Setting does not Work

I'll be working on this issue.

@WoLewicki will also be working on this issue, but he's OOO so I'm tagging him.


Compare TextDB with tools on IBM Bluemix Watson

Compare TextDB with tools on IBM bluemix Watson:
AlchemyLanguage: https://alchemy-language-demo.mybluemix.net
Conversation
Document Conversion
Language Translation
Natural Language Classifier
Personality Insights
Retrieve and Rank
Speech to Text
Text to Speech
Tone Analyzer
Tradeoff Analytics
Visual Recognition
Cognitive Commerce
Cognitive Graph
Cognitive Insights

AlchemyLanguage: https://alchemy-language-demo.mybluemix.net
===How to use===
You can do the search by copying the body of text to the box, or copy the URL of the website.

And then click on " Analyze", the system will show you the results.
AlchemyLangugae uses entities, keywords, concepts, taxonomy, document emotion, targeted emotion, document sentiment, targeted sentiment, typed relations, relations to display the results in different ways, and title, authors, publication date, language, text extraction and feeds are for URL analysis only.
Not finished

@fukoyui Per our discussion, to gain deeper understanding of their service, please use our Zika articles as a real example to show how to upload the data to them, and use their API to do extraction, if that's doable.  Prepare a demo do show the steps.


Add a check for iframes within a page and flag results for additional review

For pages that embed iframes - test and see if the full content is rendered, and therefore accessible.
This might be a non-issue; putting this here so it doesn't get lost.

Updating the title - this will be part of the checks that happen when a page is processed, and the iframe and the src can be surfaced for followup review.


Added new use cases and description of the use case - 5/14/24

The use case listing is not changed in a long time. While speaking with users, I came across several other use cases not listed here in the index. So I added new use cases and also added description against the use cases.

Fixes #XXXX.

Description

Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...

Release note

Key changed/added classes in this PR

MyFoo
OurBar
TheirBaz

This PR has:

[ x] been self-reviewed.
[x ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@amit-git-account : I added 2 comments -- to resolve the spelling issues, you need to edit .spelling in the docs website directory & add IoT and influencers


Stopping and restarting container results in duplicate UUID

Hello,
I have my Synology NAS configured to go to a power down state at night and restart the next day.
When it does I am getting the following error:
[2017-11-27 19:24:12] Homebridge is running on port 51826.
[2017-11-27 19:24:12] [Domoticz] Could not register platform accessory! (Thermostaat)
Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: f196f105-67c9-4c7b-9495-ba6f125d15fa
After this error occurred I can manually restart the container and the UUID error will be gone and everything will function correctly. Is this an issue with Homebridge or is the Domoticz plugin the culprit? Either way would it be possible for you to give me some advise how to possibly fix this?

I could be Domoticz, but it also could be Homebridge (main repo).

Your latest docker file, 4.0.

You might wanna try the develop branch, which uses a newer version of Homebridge. Alternatively, set the version in the .env file to latest.

Tried the develop version. Still the same UUID error.

What about the second option?

Yeah also tried that. No effect.

i recently got the same error
a simple stop and start solves the problem.
i also did a dsm upgrade followed by a reboot.
I think the synology is booting up both domoticz and homebridge and probably homebridge is starting up earlier then before Domoticz is completely done with discovering devices.
is it possible to add a delay in de container startup or maybee the install.sh
can we add a usleep command to install.sh?

This problem is still there with the latest version.
maybe it is a cache problem caused by cached files

I think it's caused through Domoticz – I've never seen this error in my logs. Might be the cache, as you suggested.


Add Option's commonly used methods to OptionSerializer

Problem
The OptionSerializer enum is not as easy to use ad the std::Option because many commonly used functions not implemented to it. For example if we are getting a JsonParsed transaction, to unwrap the meta, pre token balances etc we have to do it by hand. Also can't write if statements to only proceed if the OptionSerializer is Some. Adding these common methods can make it easier and more usual way to handle this type as we used to handle an Option.
Summary of Changes
Adding the most commonly used std::Option methods to OptionSerializer.
Fixes #
Missing functions added.

Okay I'm not sure why committed all the 130 other commits again. I think better if I'm stop trying to fix it before I'm creating more mess :( Can I get some assistance what I'm doing the wrong way?

Try:
git pull --rebase <upstream> master

where <upstream> is the anza-xyz/agave:master remote. Then you'll need to force-push to your branch

I've tried this, got many conflicts, so basically I just continued with:
git checkout --theirs .
git add .
git rebase --continue

Until the rebase done, had to do few times. Unfortunatelly this pull request looks still so bad. Should I close it again and try to reopen to make it look more clean? Waiting for istructions.

Should I close it again and try to reopen to make it look more clean? Waiting for istructions.

Up to you whether you open a new PR or force push to this one, but it certainly can't be reviewed as is.
There are a few different ways to accomplish what you need to do, but without knowing your experience with git, I can't really advise you much further. Just know you need your branch to be synced with the tip of anza-xyz/agave:master with just your new commits on top.
It shouldn't be a problem that your fork is from solana-labs/solana; solana-labs/solana:master is a subset of anza-xyz/agave:master, so the difference should be a simple pull from the new remote.

Should I close it again and try to reopen to make it look more clean? Waiting for istructions.

Up to you whether you open a new PR or force push to this one, but it certainly can't be reviewed as is. There are a few different ways to accomplish what you need to do, but without knowing your experience with git, I can't really advise you much further. Just know you need your branch to be synced with the tip of anza-xyz/agave:master with just your new commits on top.
It shouldn't be a problem that your fork is from solana-labs/solana; solana-labs/solana:master is a subset of anza-xyz/agave:master, so the difference should be a simple pull from the new remote.

I don't have too much experience with git, usually just using for my own repos and no one else committing there. So I'm using basic commands usually. I tried the rebase and the force push but as we can see not helped with too much things.

Okay seems like I've solved. I've used interactive rebase and dropped the extra commits :)


Pass headers from proxy without modification in Zuul

I am using Zuul as an API gateway between proxy and other services. I noticed that Zuul modifies headers coming from proxy. It modifies headers like x-forwarded-..., accept-encoding or host. It also sets Cookie header to sensitive and it adds connection header. Is it possible to pass all original headers from proxy to other services, without interference of Zuul?

Are the modifications causing issues in some way?

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


sql,stats: collect stats on non-index columns too

PR: https://github.com/cockroachdb/cockroach/pull/35192
From release notes:

Changed the default set of column statistics created by CREATE STATISTICS to include up to 100 regular table columns in addition to all indexed columns. [#35192][#35192] {% comment %}doc{% endcomment %}

This information is already live on the CBO page:

run a CREATE STATISTICS statement like the one shown below. It automatically figures out which columns to get statistics on — specifically, it chooses:

Columns that are part of the primary key or an index (in other words, all indexed columns).
Up to 100 non-indexed columns.


Is there a way to unselect columns from a query?

Say I have a QueryBuilder object that was constructed using
Query.from_("example_table").select("a", "b", "c")
If I later, given some condition, wanted to unselect some or all of the columns currently in that QueryBuilder object, is there a way to do this?
Thanks!

No, but the queries are immutable, so you could branch out into multiple query builder objects:
query = Query.from_("example_table").select("a", "b")
query_with_c = query.select("c")


./apollo.sh build  error 22

root@in-dev-docker:/apollo# ./apollo.sh build
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[INFO] Apollo Environment Settings:
[INFO]     APOLLO_ROOT_DIR: /apollo
[INFO]     APOLLO_CACHE_DIR: /apollo/.cache
[INFO]     APOLLO_IN_DOCKER: true
[INFO]     APOLLO_VERSION: @non-git
[INFO]     DOCKER_IMG: dev-x86_64-18.04-20210914_1336
[INFO]     APOLLO_ENV:  STAGE=dev USE_ESD_CAN=false
[INFO]     USE_GPU: USE_GPU_HOST=0 USE_GPU_TARGET=0
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[ OK ] Running CPU build on x86_64 platform.
[WARNING] ESD CAN library supplied by ESD Electronics doesn't exist.
[WARNING] If you need ESD CAN, please refer to:
[WARNING]   third_party/can_card_library/esd_can/README.md
[INFO] Build Overview:
[INFO]     USE_GPU: 0  [ 0 for CPU, 1 for GPU ]
[INFO]     Bazel Options: --config=cpu
[INFO]     Build Targets: //modules/... union //cyber/...
[INFO]     Disabled:      except //modules/drivers/canbus/can_client/esd/... except //modules/perception/... except //modules/planning/open_space/trajectory_smoother:planning_block except //modules/map/pnc_map:cuda_pnc_util except //modules/map/pnc_map:cuda_util_test
WARNING: Output base '/apollo/.cache/bazel/540135163923dd7d5820f3ee4b306b32' is on NFS. This may lead to surprising failures and undetermined behavior.
Extracting Bazel installation...
FATAL: failed to sync '/apollo/.cache/bazel/install/a09e0625770ce552a4233ba64ff13907.tmp.TvJZ7u/embedded_tools/jdk': (error: 22): Invalid argument

Output base '/apollo/.cache/bazel/540135163923dd7d5820f3ee4b306b32' is on NFS

According to the error, it is better to compile on local disk and try again


Updating existing Content Types with additional Fields

Hi there, I'm trying to use the PnP Provisioning template to update existing Content Types with additional fields - it fails as soon as it discovers that the Content type exists.
i.e. Apply-PnPProvisioningTemplate : A duplicate content type "XXXXX Item" was found.
I am assuming this is by design. Or is there a way to use the provisioning engine to update content types
regards
Shaun

When I provision to existing content types I do not get this error. Double check the ID of the content type you're provisioning to, maybe the ID is incorrect.

Make sure both name and ID are unique

Hi,
Thanks for your feedback. This is an engine related issue/request. Could you please insert this item, if still needed, in the PnP-Sites-Core repository (https://github.com/SharePoint/PnP-Sites-Core/issues/)? Thanks. I will close this item, because out of context.


Add page for react-native-track-player component

I am on vacation this week but I'll rebase this ASAP next week.

Ready to merge.

@chiaramooney Any chance this could be merged soon?
I have some others PR to process and there will be conflicts after this one is merged, so I'd appreciate if this one could be merged first.


Is upgrading from v2 to v3 safe?

Hi,
I've been looking for change logs without success.
No way to know if v3 api has breaking changes

Hi @luisjoserivera,
most of the API has been unchanged, so it's safe to upgrade for the large majority of use cases.
The breaking changes are around EXIF handling.
While I don't keep a manual changelog, I generally try to write useful commit messages, so the commit history is the closest thing to a formal changelog.
The following is the output of git log --pretty=%B v2.31.0...v3.0.0:
3.0.0

Remove the meta dependency from the fetch plugin.

Add url to load/error event handler params.

Fix ObjectURL revoke tests for Edge Legacy and IE.

Refactor EXIF and IPTC parsing.

Map EXIF private IFD tags into separate objects (Exif, GPSInfo, Interoperability).
Store IPTC tag offsets as data.iptcOffsets.
Add `getName` method to tag maps to retrieve the tag name for a given tag code.
Add new options to include/exclude tags from parsing (includeExifTags, excludeExifTags, includeIptcTags, excludeIptcTags).
Exclude EXIF MakerNote and IPTC ObjectPreviewData by default.
Add link to thumbnail image for the demo.

Store Exif Thumbnail as Blob instead of ObjectURL.

Please also see #91 for a previous requests for a separate changelog.
Here are examples on how to account for the changes in EXIF handling:
Displaying EXIF Thumbnails in v3+:
loadImage(
  fileOrBlobOrUrl,
  function (img, data) {
    var thumbBlob = data.exif && data.exif.get('Thumbnail')
    if (thumbBlob) {
      loadImage(thumbBlob, function (thumbImage) {
        document.body.appendChild(thumbImage)
      })
    }
  },
  { meta: true }
)

Displaying all parsed (TIFF and) Exif tags in v3+ (only the exif data structure changed, from a flat map to a multi-dimensional map with Private IFD tag values containing their own maps):
loadImage(
  fileOrBlobOrUrl,
  function (img, data) {
    if (data.exif) {
      // A map of all parsed tags with their mapped names/text as keys/values:
      // Private IFD tags contain objects with their own map.
      console.log(data.exif.getAll())
      // A specific tag value:
      console.log(data.exif.get('Orientation'))
    }
  },
  { meta: true }
)

Displaying Non-TIFF EXIF tags in v3+:
loadImage(
  fileOrBlobOrUrl,
  function (img, data) {
    var exifTags = data.exif && data.exif.get('Exif')
    if (exifTags) {
      // A map of all parsed Exif tags with their mapped names/text as keys/values:
      console.log(exifTags.getAll())
      // A specific Exif tag value:
      console.log(exifTags.get('UserComment'))
    }
  },
  { meta: true }
)

Displaying EXIF GPS Info in v3+:
loadImage(
  fileOrBlobOrUrl,
  function (img, data) {
    var gpsInfo = data.exif && data.exif.get('GPSInfo')
    if (gpsInfo) {
      // A map of all parsed GPS Info tags with their mapped names/text as keys/values:
      console.log(gpsInfo.getAll())
      // A specific GPS Info tag value:
      console.log(gpsInfo.get('GPSLatitude'))
    }
  },
  { meta: true }
)

I was wondering the same. Would be great if these breaking changes were mentioned in the docs.


AKSamplePlayer Conversion

fixed some issues with aksampleplayer - does not use incr or phasor but calculates steps through sample table manually

Cool, I think this is progress. There might be some issues, but I think this will go along way to solving most of the open issues on Github relating to this player.  Thanks!

Finally had time to build my app using AudioKit:develop and I am happy to say that the issues with regard to: https://github.com/AudioKit/AudioKit/issues/1121 are no longer present - sample lengths are calculated correctly. Thanks for the good work!


Improve explanation of retention policy specific inclusion/exclusion limits

Consider the following section: A policy with specific inclusions or exclusions
The statement says that every time we use specific locations we cannot exceed 1000 mailboxes per inclusion/exclusion. I noticed that it doesn't make clear that you can workaround by using groups and also that there is a possibility of to create multiple retention policies to satisfy the need to apply the same retention settings to more than 1000 inclusions/exclusions. I think would be better for readers to understand how to workaround the limits besides knowing the existence of them.

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

ID: ef663fdc-1776-3c73-7743-332796c284e6
Version Independent ID: ceb29788-39be-8c30-b92a-7a22243ebe83
Content: Create and configure retention policies to automatically retain or delete content - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/create-retention-policies.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@deividfoggi Thank you for your feedback. I have added information about the workaround. Once the author approves it will be live within the next 24-48 hours. The change can be tracked via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3876
Thanks
Sri

@deividfoggi Thank you for your feedback. I have added information about the workaround. Once the author approves it will be live within the next 24-48 hours. The change can be tracked via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3876
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @deividfoggi Hope the comment added by Author is helpful for you.  We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@msbemba Thank you very much for the contribution and sharing this explanation. @deividfoggi Hope the comment added by Author is helpful for you.  We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


element-{desktop,desktop-wayland,web}: security update to 1.9.7

Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name:

element-desktop
element-desktop-wayland
element-web

current version: 1.9.5
desired version: 1.9.7
Notify maintainers

maintainers: @ma27 @fadenb @mguentner @ekleog @ralith @mjlbach @dandellion @sumnerevans
Note for maintainers
https://matrix.org/blog/2021/12/13/disclosure-buffer-overflow-in-libolm-and-matrix-js-sdk and https://matrix.org/blog/2021/12/03/pre-disclosure-upcoming-security-release-of-libolm-and-matrix-js-sdk
There seems to be a not yet disclosed security release. I created a RR for olm in #150550.
Please tag this issue in your PR.

Fixed by #150558.


context: relax recommendation against putting Contexts in structs

This is a follow-on from discussion in #14660.
Right now the context package documentation says

Do not store Contexts inside a struct type; instead, pass a Context explicitly to each function that needs it. The Context should be the first parameter, typically named ctx: [...]

This advice seems overly restrictive. @bradfitz wrote in that issue:

While we've told people not to add contexts to structs, I think that guidance is over-aggressive. The real advice is not to store contexts. They should be passed along like parameters. But if the struct is essentially just a parameter, it's okay. I think this concern can be addressed with package-level documentation and examples.

Let's address this concern with package-level documentation.
Also see @rsc's comment at https://github.com/golang/go/issues/14660#issuecomment-200145301.
/cc @Sajmani @bradfitz @rsc

I'm open to relaxing this restriction as long as we can clearly define what a parameter struct is. However, I want to avoid having people define custom wrappers around Context like FooContext; I think that will lead to a world of hurt when a function that takes FooContext wants to call one that takes BarContext.  The current restriction prevents people from using the type system to create this kind of impedance mismatch.
I had also pushed for the explicit parameter restriction so that we could more easily automate refactorings to plumb context through existing code. But seeing as we've failed to produce such tools, we should probably loosen up here and deal with the tooling challenges later.

Hey @Sajmani, one of the reasons this came up is that at our company we are (I think) doing exactly this:

However, I want to avoid having people define custom wrappers around Context like FooContext;

We have a database system that defines a type
type queryContext struct {
	ctx context.Context
	// Other fields here are mostly shared state, some of which is
	// query-specific (including counters and other stats for this query)
	// and some of which is shared between queries (such as a semaphore that
	// bounds the parallelism of CPU-intensive work).
}

This has worked well for us. The context.Context is useful for propagating timeouts/cancelation throughout the query goroutines (and across the whole distributed system).
In our system, I don't see how this applies:

I think that will lead to a world of hurt when a function that takes FooContext wants to call one that takes BarContext.

Our queryContext type is local to the package; APIs that access this database take context.Context as the first argument. Internal functions take a *queryContext as the first argument. Where we call standard library functions or third-party APIs, we pass along qx.ctx. There is no impedance mismatch.
So, two questions:

Is your objection to the FooContext specifically about writing exported APIs that take a FooContext argument rather than a context.Context? Perhaps that is the thing we should recommend against? (Or have I misunderstood your objection?)

If we wanted to avoid nesting a context.Context inside our own struct, we would probably have to change dozens of internal methods from
 func (t *T) doAThing(qx *queryContext, ...)

to
 func (t *T) doAThing(ctx context.Context, qx *queryContext, ...)

Would you recommend we do that? It frankly seems like too much context to me.

Yes, the impedance mismatch is primarily a concern for exported types.
The scenario I'm worried about is:

package foo defines type Context that contains a context.Context and,
say, method Foo() *Foo, for accessing foo-specific data.
package bar defines type Context that contains a context.Context and,
say, method Bar() *Bar, for accessing bar-specific data.
Some function that accepts a foo.Context needs to call a bar.Context.
Passing just the context.Context loses the *Foo and doesn't necessarily
know what to pass for *Bar:
func F(fctx foo.Context) {
bctx := bar.NewContext(fctx.Context(), nil /*the Bar value/)
G(bctx)
}
Furthermore, if G later calls a function that expects a foo.Context, the
*Foo that should have been plumbed through has been lost:
func G(bctx bar.Context) {
fctx := foo.NewContext(bctx.Context(), nil /*the Foo value/)
H(fctx)
}
The point of the context.Context.Value design is that packages foo and bar
don't care about any of this.  Their values propagate through layers of the
call stack without intersecting or interfering with each other.  This is
exactly what you want for things like trace IDs, authentication scopes,
profiling tags.  But this is not what you should use for API-visible
options.

The "keep Context out of structs" restriction is a simple rule to follow
that helps users avoid problems like this, but it is overly restrictive.
The real guidelines are harder to articulate, but perhaps we should try
harder to do so.
S
On Thu, Nov 16, 2017 at 5:11 PM Caleb Spare<EMAIL_ADDRESS>wrote:

Hey @Sajmani https://github.com/sajmani, one of the reasons this came
up is that at our company we are (I think) doing exactly this:
However, I want to avoid having people define custom wrappers around
Context like FooContext;
We have a database system that defines a type
type queryContext struct {
ctx context.Context
// Other fields here are mostly shared state, some of which is
// query-specific (including counters and other stats for this query)
// and some of which is shared between queries (such as a semaphore that
// bounds the parallelism of CPU-intensive work).
}
This has worked well for us. The context.Context is useful for propagating
timeouts/cancelation throughout the query goroutines (and across the whole
distributed system).
In our system, I don't see how this applies:
I think that will lead to a world of hurt when a function that takes
FooContext wants to call one that takes BarContext.
Our queryContext type is local to the package; APIs that access this
database take context.Context as the first argument. Internal functions
take a *queryContext as the first argument. Where we call standard
library functions or third-party APIs, we pass along qx.ctx. There is no
impedance mismatch.
So, two questions:

Is your objection to the FooContext specifically about writing
exported APIs that take a FooContext argument rather than a
context.Context? Perhaps that is the thing we should recommend against? (Or
have I misunderstood your objection?)
2.
If we wanted to avoid nesting a context.Context inside our own struct,
we would probably have to change dozens of internal methods from
func (t *T) doAThing(qx *queryContext, ...)

to
func (t *T) doAThing(ctx context.Context, qx *queryContext, ...)

Would you recommend we do that? It frankly seems like too much context
to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/22602#issuecomment-345079151, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJSK3Y7C1eTSvGjZLf9Eym-ZxiHjcvXvks5s3LMrgaJpZM4QT82d
.

I was also thrown off by the recommendation in the package godoc. I agree that it should be fine to pass a context inside a struct as long as the function isn't exported. For my own purposes, it lets me avoid some boilerplate - the second option below is clearer, and avoids repetition in a number of signatures.
// separate context
func expandSomething(ctx context.Context, ectx expandContext, format string, a ...interface{}) string
// part of expandContext
func expandSomething(ectx expandContext, format string, a ...interface{}) string

So I think the recommended restriction should be modified to only apply to exposed APIs, i.e. exported functions. All the disadvantages outlined above generally don't apply to unexported funcs.

@mvdan I do not fully agree with this because I feel like it misses an important improvement to an exported API.
The context.Context is big and ugly, and its requirement to pass it as the first parameter implies one of the following:

Function signatures must all have context.Context as their first parameter
Functions must be written twice

Both of these make things significantly more annoying, and we have issues where context.Context is used as an argument for parametric polymorphism, goroutine-local storage, and other interesting features. I believe that these stem from the recommendation against object-local storage for request scoped context.Context values, and that a request scoped object could sufficiently provide a means to decorate a request with a context.Context for requests that actually want to use it.
Having written that, an potentially important pitfall is raised by @Sajmani about the loss of the original context.Context if it resides in a struct:
func F(fctx foo.Context) {
  bctx := bar.NewContext(fctx.Context(), nil /*the *Bar value*/)
  G(bctx)
}
Furthermore, if G later calls a function that expects a foo.Context, the
*Foo that should have been plumbed through has been lost:

I believe that if we are to relax the recommendation for unexported functions, we can also argue that the body of an exported function is under the domain of the API-author's control too, and should also be relaxed. Therefore, the API author should be responsible for deciding whether or not the new context is necessary for the request and how it is passed down to descendants: to use a request scoped object with a chain of method calls, the context.Context as the first parameter, or a value-duplication of the original request scoped object followed by a method call on that object.

I've taken to adding contexts as private fields on some higher-level manager/application/orchestration type objects, and re-deriving sub-contexts where appropriate.
I essentially do a version of what this reddit user says https://www.reddit.com/r/golang/comments/lro5va/contexts_and_structs/gomy4ip

Using errgroup is another case where I think it's totally normal and fine to store contexts inside structs. With errgroup, a context may not be used for a "request", necessarily, but purely as a cancellation mechanism for an arbitrary collection of tasks. If those tasks are associated with a struct, it sometimes makes sense to store the context and/or the CancelFunc in that struct.
(Perhaps you could argue that this is a misuse of context in the first place, but errgroup has established this pattern pretty firmly at this point. And in general it works fine apart from the confusion wrt the "Do not store contexts in structs" advice.)
At this point, after several years of using and reviewing context-using code, I've never yet reviewed code that misuses contexts in the way that the documentation warns against. (I'm sure it happens, particularly at Google scale, but I'm starting to think that it's not that common.) On the other hand, I've seen a lot of confusion and discussions arising from the "Don't store contexts in structs" advice and encountered multiple situations in which I concluded that it was fine, in fact, to store a context in a struct in some particular case. So in my opinion completely deleting this part of the documentation would be an improvement over the status quo.

I wanted to reply to this specifically from @Sajmani

However, I want to avoid having people define custom wrappers around Context like FooContext; I think that will lead to a world of hurt when a function that takes FooContext wants to call one that takes BarContext.

I think this concern is too abstract to refute.
Function calls form a tree, and the dependencies of a cycle are a stable superset of the involved functions.  If a function that takes FooContext wants to call a function that takes BarContext, either FooContext should be a superset of BarContext (e.g. be modified to have a Bar BarContext within it) or if FooContext and BarContext are both from external libraries, a the function should take a new FooBarContext that contains both instead of FooContext.
I have seen this done before and not encountered any issues with it, and wrapping contexts adds static type safety, so if there are concrete concerns blocking this change it'd be good to make them explicit.

Function calls form a tree but packages can be from very different branches of that tree.  If one developer produces a set of packages that take FooContext, and another developer produces a set of packages that take BarContext, it's going to be difficult for people to use both packages.  It's painful to use FooBarContext to call both, because you need to take steps to ensure that the deadline and the set of values are the same for both the derived FooContext and BarContext, and you will need to ensure that closing one closes the other.
To put it a different way, in effect using FooContext is a color, in the sense of https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/.  Colors should be avoided when feasible.

Thanks for the concrete example! That helps a lot, I agree it's an issue.
But common dependencies for a subtree (colors) are a real problem too, and saying "don't bundle them" doesn't make the issue disappear.  Unless there's some other solution I'm not aware of (and I'm aware of globals and goroutine-local variables) I think that's a tradeoff that that needs to be made considering individual circumstances.  It's a very large design choice for a single standard library type to prescribe.


Add format for date_saved

Currently, the date_saved property is of Feb 25th, 2023 format. My date format is different (230225).
When the article is saved to logseq it's shown in date's linked references, but if I click the date lable (Feb 25th, 2023) it leads nowhere since my date format is different.

Thanks @edshamis we are looking into this one.

Hey @edshamis, the date_saved format follows the date format in your global config.
May I know what is this format in your global settings?

Thanks @edshamis, yeah, it is what I meant.
In general, YY and YYYY represent the local week-numbering year (44, 01, 00, 17) are often confused with yy and yyyy that represent the calendar year. But I can see Logseq does accept them in the preferred date format so I will accept these in the plugin too.
Is it okay if the date_saved will be updated with the correct format only for new items synced in Logseq?

Thank you @sywhb, I wasn't even aware about the week-numbering year. After changing YY->yy and it worked as expected.

Is it okay if the date_saved will be updated with the correct format only for new items synced in Logseq?
It's fine for me, thanks

@edshamis That's great to hear!


Notices improvements

This does two things as requested by @colmharte:

convert created_at to timestamp
add rate limiting for the POST notices/create endpoint

The rate limiting has been completely lifted from the callback endpoints, but please @jackmurdoch double check the queries as I simplified one (also made the same change to the callback one)

@colmharte @jackmurdoch updated removing rate limit count for notices.
Now I have three modes:

noticesRateLimitSeconds is null or not found: limit to one notice per registration
noticesRateLimitSeconds is 0: no limit
noticesRateLimitSeconds is any number: one request each noticesRateLimitSeconds seconds

@colmharte @jackmurdoch updated with metrics

@colmharte updated with further simplification of rate limit and removed noticesToken


Make narrow sidebar more readable/useable

I'm guessing min width or similar is being set on the buttons and text.
It feels like at least up to some (currently smaller than it is currently) size, the buttons could actually shrink and still show the text etc

Compared with the notifications sidebar:

Thank you for taking the time to report this issue. The fix has been implemented in version 0.24.0 and is available on the Releases page for manual installation. Alternatively, you can wait for the official release on the JetBrains Marketplace, which should happen in approximately 3 days.

In response to the issue you raised: I managed to understand what you meant and simulate the problem. I made some minor adjustments to ensure that the texts don't force a minimum size. Additionally, I removed the checkbox for the "add missing semicolon" feature because it was causing too many issues (and at the same time, the checkbox itself was causing problems with the minimum width of this box you mentioned).


Fix infinite loop for Ref 4 @ L5.2

This fixes an infinite loop when an AVC stream has
4 ref frames and level 5.2... regression introduced
by:
commit e126273431b470a738e4c26896b829a6801cb455
Author: Guo, Will<EMAIL_ADDRESS>Date:   Sun Apr 26 19:22:34 2020 +0800

    Support AVC Level 6/6.1/6.2

    Support Decode AVC Level 6/6.1/6.2

    Issue: MDP-47088

    Change-Id: I42aa5f67b7480a264f86822d5e5e3cd750d8d090

Fixes #2325
Signed-off-by: U. Artie Eoff<EMAIL_ADDRESS>

@dmitryermilov can you do another quick review for my update?

Updated. Also improved commit message.


Remove version: taers232c.GAMADV-XTD3 version 6.68.06

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.68.06/gamadv-xtd3-6.68.06-windows-x86_64.msi
OK
(Automated message - build 910)


[WIP] Example of RAJA interoperability [artv3/interop-raja]

Hi Folks, building on PR #937 . This example illustrates interoperability between RAJA and MFEM's memory manager. Additionally, data is allocated externally and then passed into an MFEM vector. I show how to operate on the data on both the GPU and CPU (using RAJA) and maintain validity of the data flags. I found this exercise useful and thought it might be good to share.

@artv3 -- is this something you will like to merge eventually or is it just an example that could be useful for other users? In the latter case, I think it will be better to preserve it in an issue...

@tzanio , this was mostly an exercise to get a feel for how the memory manager worked. We don't have to merge this. I think it could be useful for application developers. If you like, I can do a cleanup pass and we can preserve it in an issue.

If you like, I can do a cleanup pass and we can preserve it in an issue.
Yes, please do that if you don't mind. I agree that it will be useful for other users.

Closing/Deleting this PR. Will move information to an MFEM issue this week.


Error when using https (encrypted)

When I use http unencrypted all things works fine
but after using https the connection opens but when broadcast(Event) it gives me error

{message: "", exception: "Illuminate\Broadcasting\BroadcastException",…} exception: "Illuminate\Broadcasting\BroadcastException" file:
"/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Broadcasting/Broadcasters/PusherBroadcaster.php" line: 117 message: "" trace: [{,…}, {function: "handle", class:
"Illuminate\Broadcasting\BroadcastEvent", type: "->"},
 {,…}, {,…},…] 0: {,…}
 class: "Illuminate\Broadcasting\Broadcasters\PusherBroadcaster" file:
"/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Broadcasting/BroadcastEvent.php" function: "broadcast" line: 48 type: "->" 1: {function: "handle", class:
"Illuminate\Broadcasting\BroadcastEvent", type: "->"} 2: {,…} file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php" function: "call_user_func_array" line: 29 3: {,…} 4: {,…} 5: {,…} 6: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php",…} 7: {,…} 8: {,…} 9: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php",…} 10: {,…} 11: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php",…} 12: {,…} 13: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Queue/Queue.php",…} 14: {,…} 15: {,…} 16: {,…} 17: {,…} 18: {,…} 19: {file: "/Applications/MAMP/htdocs/saafca/app/Http/Controllers/users/CheckoutController.php", line: 37,…} 20: {function: "addCredit", class: "App\Http\Controllers\users\CheckoutController", type: "->"} 21: {,…} 22: {,…} 23: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Route.php",…} 24: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Route.php",…} 25: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Router.php",…} 26: {,…} 27: {,…} 28: {,…} 29: {,…} 30: {,…} 31: {,…} 32: {,…} 33: {,…} 34: {,…} 35: {,…} 36: {,…} 37: {,…} 38: {,…} 39: {,…} 40: {,…} 41: {,…} 42: {,…} 43: {,…} 44: {,…} 45: {,…} 46: {,…} 47: {,…} 48: {,…} 49: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Router.php",…} 50: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Router.php",…} 51: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Router.php",…} 52: {file: "/Applications/MAMP/htdocs/saafca/vendor/laravel/framework/src/Illuminate/Routing/Router.php",…} 53: {,…} 54: {,…} 55: {file: "/Applications/MAMP/htdocs/saafca/vendor/fideloper/proxy/src/TrustProxies.php", line: 57,…} 56: {,…} 57: {,…} 58: {,…} 59: {,…} 60: {,…} 61: {,…} 62: {,…} 63: {,…} 64: {,…} 65: {,…} 66: {,…} 67: {,…} 68: {,…} 69: {,…} 70: {,…} 71: {,…} 72: {,…} 73: {file: "/Applications/MAMP/htdocs/saafca/public/index.php", line: 55, function: "handle",…} class: "Illuminate\Foundation\Http\Kernel" file: "/Applications/MAMP/htdocs/saafca/public/index.php" function: "handle" line: 55 type: "->" Name

My bootstrap.js
window.Echo = new Echo({
    broadcaster: 'pusher',
    key: process.env.MIX_PUSHER_APP_KEY,
    encrypted: true,
    wsHost: window.location.hostname,
    wsPort: 6001,
    wssPort: 6001,
    disableStats: true,

});

websocket.php
<?php

use BeyondCode\LaravelWebSockets\Dashboard\Http\Middleware\Authorize;

return [

    /*
     * This package comes with multi tenancy out of the box. Here you can
     * configure the different apps that can use the webSockets server.
     *
     * Optionally you can disable client events so clients cannot send
     * messages to each other via the webSockets.
     */
    'apps' => [
        [
            'id' => env('PUSHER_APP_ID'),
            'name' => env('APP_NAME'),
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'enable_client_messages' => false,
            'enable_statistics' => true,
        ],
    ],

    /*
     * This class is responsible for finding the apps. The default provider
     * will use the apps defined in this config file.
     *
     * You can create a custom provider by implementing the
     * `AppProvider` interface.
     */
    'app_provider' => BeyondCode\LaravelWebSockets\Apps\ConfigAppProvider::class,

    /*
     * This array contains the hosts of which you want to allow incoming requests.
     * Leave this empty if you want to accept requests from all hosts.
     */
    'allowed_origins' => [
        //
    ],

    /*
     * The maximum request size in kilobytes that is allowed for an incoming WebSocket request.
     */
    'max_request_size_in_kb' => 250,

    /*
     * This path will be used to register the necessary routes for the package.
     */
    'path' => 'laravel-websockets',

    /*
     * Dashboard Routes Middleware
     *
     * These middleware will be assigned to every dashboard route, giving you
     * the chance to add your own middleware to this list or change any of
     * the existing middleware. Or, you can simply stick with this list.
     */
    'middleware' => [
        'web',
        Authorize::class,
    ],

    'statistics' => [
        /*
         * This model will be used to store the statistics of the WebSocketsServer.
         * The only requirement is that the model should extend
         * `WebSocketsStatisticsEntry` provided by this package.
         */
        'model' => \BeyondCode\LaravelWebSockets\Statistics\Models\WebSocketsStatisticsEntry::class,

        /*
         * Here you can specify the interval in seconds at which statistics should be logged.
         */
        'interval_in_seconds' => 60,

        /*
         * When the clean-command is executed, all recorded statistics older than
         * the number of days specified here will be deleted.
         */
        'delete_statistics_older_than_days' => 60,

        /*
         * Use an DNS resolver to make the requests to the statistics logger
         * default is to resolve everything to <IP_ADDRESS>.
         */
        'perform_dns_lookup' => false,
    ],

    /*
     * Define the optional SSL context for your WebSocket connections.
     * You can see all available options at: http://php.net/manual/en/context.ssl.php
     */
    'ssl' => [
        /*
         * Path to local certificate file on filesystem. It must be a PEM encoded file which
         * contains your certificate and private key. It can optionally contain the
         * certificate chain of issuers. The private key also may be contained
         * in a separate file specified by local_pk.
         */
        'local_cert' =>  "/Users/sasuke/ssl/server.crt",

        /*
         * Path to local private key file on filesystem in case of separate files for
         * certificate (local_cert) and private key.
         */
        'local_pk' =>  "/Users/sasuke/ssl/server.key",

        /*
         * Passphrase for your local_cert file.
         */
        'passphrase' => null,
        'verify_peer'=>false
    ],

    /*
     * Channel Manager
     * This class handles how channel persistence is handled.
     * By default, persistence is stored in an array by the running webserver.
     * The only requirement is that the class should implement
     * `ChannelManager` interface provided by this package.
     */
    'channel_manager' => \BeyondCode\LaravelWebSockets\WebSockets\Channels\ChannelManagers\ArrayChannelManager::class,
];

broadcasting.php

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Broadcaster
    |--------------------------------------------------------------------------
    |
    | This option controls the default broadcaster that will be used by the
    | framework when an event needs to be broadcast. You may set this to
    | any of the connections defined in the "connections" array below.
    |
    | Supported: "pusher", "redis", "log", "null"
    |
    */

    'default' => env('BROADCAST_DRIVER', 'null'),

    /*
    |--------------------------------------------------------------------------
    | Broadcast Connections
    |--------------------------------------------------------------------------
    |
    | Here you may define all of the broadcast connections that will be used
    | to broadcast events to other systems or over websockets. Samples of
    | each available type of connection are provided inside this array.
    |
    */

    'connections' => [

        'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'app_id' => env('PUSHER_APP_ID'),
            'options' => [
                'cluster' => env('PUSHER_APP_CLUSTER'),
                'encrypted' => true,
                'host' => 'localhost',
                'port' => 6001,
                'scheme' => 'https'
            ],
        ],

        'redis' => [
            'driver' => 'redis',
            'connection' => 'default',
        ],

        'log' => [
            'driver' => 'log',
        ],

        'null' => [
            'driver' => 'null',
        ],
        'curl_options' => [
            CURLOPT_SSL_VERIFYHOST => 0,
            CURLOPT_SSL_VERIFYPEER => 0,
        ],

    ],

];

try encrypted: false

Same here with valet configuration from docs...
pusher.min.js:8 WebSocket connection to 'wss://xxx.test:6001/app/1?protocol=7&client=js&version=4.3.1&flash=false' failed: Error in connection establishment: net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Is it a self-signed cert? If so, that won't work out of the box, because cURL can't trust the certificate provided by laravel-websockets over HTTPS.
Instead, I recommend using https://github.com/FiloSottile/mkcert to make yourself a local CA and add it to your trust store, for development. In prod, you'll need to use a real cert. You can use Caddy and/or Let's Encrypt to issue one.

Add some CURLOPT options:
'pusher' => [
    'driver' => 'pusher',
    'key' => env('PUSHER_APP_KEY'),
    'secret' => env('PUSHER_APP_SECRET'),
    'app_id' => env('PUSHER_APP_ID'),
    'options' => [
        'cluster' => env('PUSHER_APP_CLUSTER'),
        'host' => '<IP_ADDRESS>',
        'port' => 6001,
        'scheme' => env('PUSHER_APP_SCHEME', 'http'),
        'encrypted' => true,
        'curl_options' => [
            CURLOPT_SSL_VERIFYHOST => 0,
            CURLOPT_SSL_VERIFYPEER => 0,
        ],
    ],
],


Expand Standard Values

A lot of helm charts follow standard values. Fields like serviceAccount, image, resources, etc...
It'd be cool if, either via a comment like  # $type: resources, or just smart detection, schema gen could "fill-in" the schema for standard fields.
So resources would from
        "resources": {
            "type": "object"
        },

to
              "resources": {
                "description": "ResourceRequirements describes the compute resource requirements.",
                "properties": {
                  "limits": {
                    "additionalProperties": {
                      "oneOf": [
                        {
                          "type": [
                            "string",
                            "null"
                          ]
                        },
                        {
                          "type": [
                            "number",
                            "null"
                          ]
                        }
                      ]
                    },
                    "description": "Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/",
                    "type": [
                      "object",
                      "null"
                    ]
                  },
                  "requests": {
                    "additionalProperties": {
                      "oneOf": [
                        {
                          "type": [
                            "string",
                            "null"
                          ]
                        },
                        {
                          "type": [
                            "number",
                            "null"
                          ]
                        }
                      ]
                    },
                    "description": "Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/",
                    "type": [
                      "object",
                      "null"
                    ]
                  }
                },
                "type": [
                  "object",
                  "null"
                ]
              },

Could possibly use https://github.com/instrumenta/kubernetes-json-schema as an update to date src for these fields.

@RichiCoder1 I'll try to analyze this. Sounds like a nice feature, but I'm also concerned about the correctness of the program. Even though many people have standard fields, it doesn't mean that people cannot use it differently. People could define their own custom fields inside these fields and then use it. In the default values.yaml , they would just mention it in comments.
I think, the current tooling is more correct, but with this feature, the correctness of the output might be questionable in some cases as some fields are magically detected which the user may or may not know and might also not need it sometimes. It might look like a rare case where such fields are used differently, but the possibility still opens up the possibility of the tool's output being wrong or providing extra unnecessary schema to the user

Also, the tool is more of a helper tool to get started, instead of starting from scratch. It's not exactly a full fledged tool

Some people have told me that there are few more tools that help with similar stuff related to schema.

For example Cuelang. Reference post: https://news.ycombinator.com/item?id=23730926

I can think of one way to solve this, need to dig in more. The idea is to have some optional feature, which works only when
explicitly turned on. This feature would provide the following things -

Magically fill in some standard fields - whose key is known, but the values are all hidden in comments with just example values
Get config from user to replace standard / custom fields
User can override the magic defaults that is provided by the tool

This is just an abstract idea. I gotta dig a bit more and think on how to implement it

Also, the comment in the values.yaml with # $type: resources could help too, and the tool can have some default understanding for it, and the user can provide custom config for it too! :) Basically custom types to give primitive types.
I'll also check if there are better ways to do this. Maybe I'll check cuelang too :)

@karuppiah7890  Hello, I'm not sure should I extend the current issue or create a different issue. But I want to propose to add the ability to use comments in the  values.yaml to point helm-schema-gen to the object explanation in the same way as we doing with json schema,so for adding the knowledge to about the object we should just add the ability to refer the object to  JSON schema reference that will be stored inside the comments.

@karuppiah7890  Hello, I'm not sure should I extend the current issue or create a different issue. But I want to propose to add the ability to use comments in the  values.yaml to point helm-schema-gen to the object explanation in the same way as we doing with json schema,so for adding the knowledge to about the object we should just add the ability to refer the object to  JSON schema reference that will be stored inside the comments.

@carbohydrates I think that's a great idea. Maybe that could be a different issue as this issues seems to have a different goal, which is more magical with as little user input as possible.
The use case you have mentioned requires more user input.
Another related idea I have had is - if there are sub charts which do not have values.schema.json then pull those sub charts and get the values.yaml and auto generate values.schema.json and merge it with the current chart's values.schema.json . This was just an idea as in one of the helm issues someone mentioned about schema for sub charts. But I still haven't checked much about how Helm handles schema for sub charts
Note: I don't have the time to continue on this project as of now. I'm willing to take PRs, or someone can even fork and work on it too and maintain it or maintain this project too. :)

@carbohydrates I think that's a great idea. Maybe that could be a different issue as this issues seems to have a different goal, which is more magical with as little user input as possible.
The use case you have mentioned requires more user input.
Another related idea I have had is - if there are sub charts which do not have values.schema.json then pull those sub charts and get the values.yaml and auto generate values.schema.json and merge it with the current chart's values.schema.json . This was just an idea as in one of the helm issues someone mentioned about schema for sub charts. But I still haven't checked much about how Helm handles schema for sub charts
Note: I don't have the time to continue on this project as of now. I'm willing to take PRs, or someone can even fork and work on it too and maintain it or maintain this project too. :)

@karuppiah7890 I think @RichiCoder1 has a good use case. This could be enabled with a parameter, e.g. --expand-default-objects or similar.
As for the implementation, I would create a catalog with either jsonpath or jmespath key and the corresponding replacement as the value:
{".resource": {"type": "object", "properties" ...

Great ideas! Also, if someone's looking to pick data from comments, there was a recent PR #10 but later @k-kinzal closed it for an alternate implementation method.
As of now, I'm not spending much time on maintaining this tool. I'll post here if and when I pick it up. So if anyone's already intrested to work on a solution, please don't wait for green signal, go ahead 😁


Promote isValidating to the global level of data and error

This fixes https://github.com/vercel/swr/issues/549 by caching and broadcasting isValidating in the same way that data and error are cached and broadcasted.
Before

After

Anything I can do to speed up a review?

Bump

@shuding Test has been added: useSWR › should broadcast isValidating
Test on master

Test on fix-is-validating

Bump

Bump

Bump

Thank you all for helping!


Script fails with 'Patch Missing' error after successfully downloading patches

RedHat Linux 8
Whenever running the script to download patches, it downloads the patches successfully, but then says 'Patch  missing', and exits with a return code of 1. I have tried this with several different patches and the result is the same:
$java -jar oraclePatchDownloader-1.0.0.jar -u $MOSUser -p $MOSPassword -x 36057774 -t 226P -d $downloadDir
File PEOPLETOOLS-LNX-8.60.11_1of4.zip downloaded successfully.
File PEOPLETOOLS-LNX-8.60.11_2of4.zip downloaded successfully.
File PEOPLETOOLS-LNX-8.60.11_3of4.zip downloaded successfully.
File PEOPLETOOLS-LNX-8.60.11_4of4.zip downloaded successfully.
Patch 36057774 missing

can you try with the latest version ?? i added the -c --check option and disabled by default the checking.
as i work mostly with databases, the patches are in form
p99999999.zip.... so we i can check if the patch is downloaded.  but this will done only if -c or --check is passed
thanks for testing and closing this ticket when the test was successfull

Yes, that worked great. Thanks for the quick fix! I think it would be helpful to note in the readme that using -c assumes that the patch files are named pxxxxxxxx.zip.
Closing Issue. Thanks again.


Array of columns not accepted as onConflict argument

The documentation says this is possible:
// array of columns:
db.table.create(data).onConfict(['email', 'name']).merge();

(Note the typo in onConfict by the way.)
However, I don't seem to be able to use this, at least types-wise:
class UserTable extends tables.BaseTable {
  readonly table = "user"

  columns = this.setColumns(t => ({
    email: t.varchar().primaryKey(),
    org: t.varchar().primaryKey(),
  }))
}

// gives type error
await db.user.create({ email: "", org: "" }).onConflict(["email", "org"]).merge()

It seems to be working in runtime, though.

orchid-orm 1.27.5

Thank you! I actually though this at first, but then I started to double confirm and what I discovered was:

At "Setup and Overview", if one searches for "composite", they will find:

documentation for composite primary keys, indexes, foreign keys, is residing in migration column methods

At "Column methods" > "composite primary key", the example shows multiple t.whatever().primaryKey(), and the second function seems to be demoing the way of providing a custom index name. It's not mentioning there are other cases the function form should used in.

So I decided it could not be it. :) Perhaps "Setup and Overview" deserves its own section for the composite keys (not only link to the migrations methods) which covers that difference briefly once again. Not a huge deal by all means, of course.


Updated guides with $firebaseAuth issues #743

Guides updated with fix related to issue  #743

Thanks for the PR! I think we just want to make sure all the docs are for the newest code, so let's go ahead and just keep the var auth = $firebaseAuth(); lines in all these and remove the rest. Thanks for catching our mistake!

You missed one last one in docs/quickstart.md that needs to be slimmed one.

Oh sorry! I forgot that last one

Looks good. Thanks for the PR and helping us improve our docs!


Rewrite 'copy' functionality to remove jQuery dependency and follow GOV.UK Frontend conventions

Removes jQuery dependency
Followes GOV.UK Frontend convevtions
Works in IE9+ (plugin does not support IE8)

Trello ticket: https://trello.com/c/J02wN45k/1326-update-copyjs-to-follow-frontend-conventions-and-remove-dependency-on-jquery
Ticket to build an ie8 bundle is here: https://trello.com/c/B6N3G2fS/1325-ensure-copy-to-clipboard-functionality-does-not-break-ie8-experience

You can preview this change here:
Built with commit 0260646d61add9ffd5b4dd59936c3b40c54ddabf
https://deploy-preview-512--govuk-design-system-preview.netlify.com

Now using data-moduleattribute instead of a css class to target copy functionality

Merging in @igloosi's absence.


[BD-46] docs: changing Layout colors

Description

corrected valid color contrasts for the Layout component (according to WCAG).

Issue: https://github.com/openedx/paragon/issues/2637
Deploy Preview
Layout component
Merge Checklist

[x] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @PKulkoRaccoonGang!
When this pull request is ready, tag your edX technical lead.

@PKulkoRaccoonGang 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 22.0.0-alpha.8 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


style(optional artifact):  catch the cause for misleading warning

This changes ensures the warning for optional artifacts will only be printed in valid cases.

Pull Request Test Coverage Report for Build 597367230

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 48.989%

Totals

Change from base Build 597010906:
0.04%

Covered Lines:
1381

Relevant Lines:
2819

💛  - Coveralls


grpc_ios_binary_size timeout

https://source.cloud.google.com/results/invocations/04689852-45b4-423d-8c1f-23bde1d4cdc2/targets/grpc%2Fcore%2Fpull_request%2Fmacos%2Fgrpc_ios_binary_size/log
.....
pod install
Analyzing dependencies
Fetching podspec for `!ProtoCompiler` from `../../../../src/objective-c`
Fetching podspec for `!ProtoCompiler-gRPCPlugin` from `../../../../src/objective-c`
Fetching podspec for `BoringSSL-GRPC` from `../../../../src/objective-c`
Fetching podspec for `Protobuf` from `../../../../third_party/protobuf`
Fetching podspec for `RemoteTest` from `../RemoteTestClient`
Fetching podspec for `gRPC` from `../../../..`
Fetching podspec for `gRPC-Core` from `../../../..`
Fetching podspec for `gRPC-ProtoRPC` from `../../../..`
Fetching podspec for `gRPC-RxLibrary` from `../../../..`
Downloading dependencies
Installing !ProtoCompiler (3.6.0)
ERROR: Aborting VM command due to timeout of 3600 seconds

Seen again in https://github.com/grpc/grpc/pull/18110: Aborting VM command due to timeout of 5400 seconds

@muxi  another item related to objC test taking way too long.


lnd fails to start

Background
I have had a working lnd node running on a RaspiberryPi for almost a year now. It was working fine a few days ago but something happened and now lnd won't start. I upgraded the lnd version from 5.2 to 6 to see if that might resolve it but the issue still exists. Thank you for any assistance.
Your environment
lnd version 0.6.0-beta commit=v0.6-beta
Linux RaspiNode 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
Bitcoin Core Daemon version v0.17.1
Steps to reproduce
Run "lnd"
Attempting automatic RPC configuration to bitcoind
Automatically obtained bitcoind's RPC credentials
2019-04-19 12:22:51.955 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta, build=production, logging=default
2019-04-19 12:22:51.955 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-04-19 12:22:51.956 [INF] LTND: Shutdown complete
panic: invalid freelist page: 13364, page type is leaf

goroutine 1 [running]:
github.com/coreos/bbolt.(*freelist).read(0x3210700, 0x5a01b000)
        /Users/roasbeef/gocode/pkg/mod/github.com/coreos/bbolt@v1.3.2/freelist.go:266 +0x23c
github.com/coreos/bbolt.(*DB).loadFreelist.func1()
        /Users/roasbeef/gocode/pkg/mod/github.com/coreos/bbolt@v1.3.2/db.go:310 +0xf0
sync.(*Once).Do(0x318c480, 0x3075d28)
        /usr/local/go/src/sync/once.go:44 +0xb8
github.com/coreos/bbolt.(*DB).loadFreelist(0x318c3c0)
        /Users/roasbeef/gocode/pkg/mod/github.com/coreos/bbolt@v1.3.2/db.go:303 +0x48
github.com/coreos/bbolt.Open(0x31044b0, 0x30, 0x180, 0x15d7fc8, 0x30, 0x25, 0x31fe380)
        /Users/roasbeef/gocode/pkg/mod/github.com/coreos/bbolt@v1.3.2/db.go:280 +0x2ac
github.com/lightningnetwork/lnd/channeldb.Open(0x3104480, 0x25, 0x3075f24, 0x2, 0x2, 0x2, 0x0, 0x3100580)
        /Users/roasbeef/gocode/src/github.com/lightningnetwork/lnd/channeldb/db.go:131 +0x104
main.lndMain(0x0, 0x0)
        /Users/roasbeef/gocode/src/github.com/lightningnetwork/lnd/lnd.go:164 +0x3a8
main.main()
        /Users/roasbeef/gocode/src/github.com/lightningnetwork/lnd/lnd.go:477 +0x14

Expected behaviour
lnd should have started
Actual behaviour
It fails to start with the above stack trace.

Looks like you've encountered disk corruption. Since this happened while you were on v0.5.2, there's no way to recover your off-chain funds. The best you can do is recover you on-chain funds following this guide.
Once you start the new node on v0.6, you'll have access to SCBs (you can read more about them here), which will allow you to recover your off-chain funds if this arises again.

Thanks for the info. I followed the steps and I believe that I need to run the dropwtxmgr but no matter what I tried I couldn't figure out how to get it to run. It just doesn't seem to "install" based on the instructions in the guide. I installed Go. I set a GOPATH. Running the "go get" doesn't seem to install the dropwtxmgr. I have a feeling that something is assumed in those instructions. Thanks for any help on this.

Running the "go get" doesn't seem to install the dropwtxmgr.

What's the output of the command? It'll install it into $GOPATH/bin/.

admin@RaspiNode:~ $ echo $GOPATH
/home/admin/gocode
admin@RaspiNode:~ $ go version
go version go1.7.4 linux/arm
admin@RaspiNode:~ $ go get -v -u github.com/btcsuite/btcwallet/cmd/dropwtxmgr
github.com/btcsuite/btcwallet (download)
github.com/btcsuite/btcutil (download)
github.com/btcsuite/btcd (download)
Fetching https://golang.org/x/crypto/ripemd160?go-get=1
Parsing meta tags from https://golang.org/x/crypto/ripemd160?go-get=1 (status code 200)
get "golang.org/x/crypto/ripemd160": found meta tag main.metaImport{Prefix:"golang.org/x/crypto", VCS:"git", RepoRoot:"https://go.googlesource.com/crypto"} at https://golang.org/x/crypto/ripemd160?go-get=1
get "golang.org/x/crypto/ripemd160": verifying non-authoritative meta tag
Fetching https://golang.org/x/crypto?go-get=1
Parsing meta tags from https://golang.org/x/crypto?go-get=1 (status code 200)
golang.org/x/crypto (download)
package math/bits: unrecognized import path "math/bits" (import path does not begin with hostname)
github.com/btcsuite/btclog (download)
github.com/btcsuite/golangcrypto (download)
github.com/coreos/bbolt (download)
github.com/jessevdk/go-flags (download)

it didn't install anything in the $GOPATH/bin/ directory sadly

Try these alternative steps to install the binary:
$ git clone https://github.com/btcsuite/btcwallet
$ cd btcwallet
$ GO111MODULE=on go install ./cmd/dropwtxmgr

@wpaulino thanks for your help on this. I figured out my issue with go as I was using version 1.7 (as that is what apt-get installs) but I needed at least 1.9. I have installed 1.12+ and have been able to follow the droptxmgr steps. It reverted everything back to my wallet's origin which is just over a year old. It then ran through all of the old blocks but didn't find anything. Is there anything else I can try? Is there something I need to do after the "Forced In-Place Rescan" finished?


x/pkgsite: builtin should be ranked higher in search

What is the URL of the page with the issue?
https://pkg.go.dev/search?q=builtin
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.59 Safari/537.36
screenshot

What did you do?
Visited the page.
What did you expect to see?
The stdlib builtin package listed as the first result; https://pkg.go.dev/builtin/?tab=doc
What did you see instead?
A list of packages, with the stdlib one not been one of them

Perhaps this is because builtin is not a normal package, it's not a package you can import. So if they have any "sort by" parameters like "number of packages that import this package", then that should always be 0 for builtin.

(To clarify, I agree this is likely a bug; I'm just guessing what the cause might be)

/cc @julieqiu @jba @jamalc

I had the same experience today, IMO we may indeed regard this as a bug.


On build, create a html file in the build directory containing the name of the main.hash.js file

For serving to the WeVoteServer for fastly custom domains

👍


Improved Prompts in Find Box.

Description of the new feature/enhancement
I would like to have a 'Current out of Total Results Found' and 'Not Found' prompt when searching for a word in the Terminal Window. Currently, no information of this kind is available.

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3920 and #6319 for more discussion.
/dup #3920