Script to enable Yammer license doesn't work

Your article says the following put in the script will enable Yammer licenses but I just tested it and it does not work. The Yammer license is still disabled:
If ($.ProvisioningStatus -eq "Disabled" -and $.ServicePlan.ServiceName -notlike "YAMMER") { $DisabledOptions += "$($_.ServicePlan.ServiceName)" }

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

ID: 6cffee5c-7540-c606-3293-c0a51be06fa5
Version Independent ID: 359a567b-4fcd-0cb4-03e0-f00fdcff5d5b
Content: Manage Yammer user licenses in Office 365
Content Source: yammer/manage-yammer-users/manage-yammer-licenses-in-office-365.md
Service: o365-administration
GitHub Login: @IrenePasternack
Microsoft Alias: v-irpast

The script you mention is used for disabling the license.
For enabling, use the previous example in the article:
The following example assigns a license from the litwareinc:ENTERPRISEPACK (Office 365 Enterprise E3) licensing plan to the unlicensed user belindan<EMAIL_ADDRESS>Set-MsolUserLicense -UserPrincipalName<EMAIL_ADDRESS>-AddLicenses "litwareinc:YAMMER_ENTERPRISE_STANDALONE"
From: mauldlouie<EMAIL_ADDRESS>Sent: Monday, October 8, 2018 12:22 PM
To: MicrosoftDocs/OfficeDocs-O365ITPro<EMAIL_ADDRESS>Cc: Irene Pasternack (Steyer Associates Inc<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/OfficeDocs-O365ITPro] Script to enable Yammer license doesn't work (#27)
Your article says the following put in the script will enable Yammer licenses but I just tested it and it does not work. The Yammer license is still disabled:
If ($.ProvisioningStatus -eq "Disabled" -and $.ServicePlan.ServiceName -notlike "YAMMER") { $DisabledOptions += "$($_.ServicePlan.ServiceName)" }

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

ID: 6cffee5c-7540-c606-3293-c0a51be06fa5
Version Independent ID: 359a567b-4fcd-0cb4-03e0-f00fdcff5d5b
Content: Manage Yammer user licenses in Office 365https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fyammer%2Fmanage-yammer-users%2Fmanage-yammer-licenses-in-office-365%3FredirectSourcePath%3D%25252fen-us%25252farticle%25252fManage-Yammer-user-licenses-in-Office-365-34a67e3a-3fd8-4e54-bffb-dd5ad0e48590&data=02|01|v-irpast%40microsoft.com|ad9588ccc5be4a6adf9908d62d53486f|72f988bf86f141af91ab2d7cd011db47|1|0|636746233057948475&sdata=GpNiC3v6B7giGNuy1M8QhkAxWxEYzI5OCjHhK2pWt9c%3D&reserved=0
Content Source: yammer/manage-yammer-users/manage-yammer-licenses-in-office-365.mdhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-O365ITPro%2Fblob%2Fpublic%2Fyammer%2Fmanage-yammer-users%2Fmanage-yammer-licenses-in-office-365.md&data=02|01|v-irpast%40microsoft.com|ad9588ccc5be4a6adf9908d62d53486f|72f988bf86f141af91ab2d7cd011db47|1|0|636746233057948475&sdata=zUTPBsuX9C8W8VCUPx4odxocvmDQVIKjp4uf4YRnJQU%3D&reserved=0
Service: o365-administration
GitHub Login: @IrenePasternackhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIrenePasternack&data=02|01|v-irpast%40microsoft.com|ad9588ccc5be4a6adf9908d62d53486f|72f988bf86f141af91ab2d7cd011db47|1|0|636746233057948475&sdata=z1%2BsHKJW0d%2FBNoNolaVJG%2BlaVsJEUSZ230ZMKx47bH8%3D&reserved=0
Microsoft Alias: v-irpast

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-O365ITPro%2Fissues%2F27&data=02|01|v-irpast%40microsoft.com|ad9588ccc5be4a6adf9908d62d53486f|72f988bf86f141af91ab2d7cd011db47|1|0|636746233057948475&sdata=fGPl%2FpFDE6J345WNLrX%2BGxKnBRaPLAXjoZCjA%2Bzdv2Q%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAkqBo1YV1pBf4bWbu0z8XSNesj6w1IW-ks5ui6XHgaJpZM4XNhwd&data=02|01|v-irpast%40microsoft.com|ad9588ccc5be4a6adf9908d62d53486f|72f988bf86f141af91ab2d7cd011db47|1|0|636746233057948475&sdata=72sWsrTI21SExTJBT7MytV4M5RndGkijbexAkP1XloY%3D&reserved=0.

I was wrong. The Yammer license is enabled by the code you showed. I thought it was disabled because the GUI was showing it disabled. I guess the GUI just hadn't caught up. When I ran a PowerShell command to check the status, it showed it enabled.

I’m glad you were able to get it enabled. The GUI sometimes does take a while to refresh.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: mauldlouie<EMAIL_ADDRESS>Sent: Monday, October 8, 2018 4:10:25 PM
To: MicrosoftDocs/OfficeDocs-O365ITPro
Cc: Irene Pasternack (Steyer Associates Inc); Mention
Subject: Re: [MicrosoftDocs/OfficeDocs-O365ITPro] Script to enable Yammer license doesn't work (#27)
I was wrong. The Yammer license is enabled by the code you showed. I thought it was disabled because the GUI was showing it disabled. I guess the GUI just hadn't caught up. When I ran a PowerShell command to check the status, it showed it enabled.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-O365ITPro%2Fissues%2F27%23issuecomment-428007869&data=02|01|v-irpast%40microsoft.com|ea6cd7ca57b24e3fa72d08d62d733b5c|72f988bf86f141af91ab2d7cd011db47|1|0|636746370458178713&sdata=BhoyTuDdFISaPR7%2FUen%2FN5s3wLoa8AxsvlBh5PDw7HQ%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAkqBo4dc_OPYopMWJkeutIUi-4VHdbSnks5ui9thgaJpZM4XNhwd&data=02|01|v-irpast%40microsoft.com|ea6cd7ca57b24e3fa72d08d62d733b5c|72f988bf86f141af91ab2d7cd011db47|1|0|636746370458178713&sdata=o29oOHs%2FyWMzkhCc3W%2FYq94SBz36rLleyuwStZXbsJI%3D&reserved=0.


damienbod/aspnetcore-data-ef-mvc-intro-samples-cu-update-csproj

Hi @damienbod, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@Rick-Anderson
The docs need to be updated for this as well

intro.md is updated

@tdykstra owns this.


Asset loading fails when using cargo flamegraph

Bevy version
0.10.1
What you did

Created a project that requires asset loading. In this case, this commit of Emergence.
Verify that the game works in cargo run --release.
Use the flamegraph cargo tool linked here by calling  cargo flamegraph --bin=emergence_game.

What went wrong
Assets failed to load, and thus the game never started.
Additional information
This might be an incompatibility between bevy_tasks and whatever flamegraph is doing?

I'm guessing that this has to do with asset paths. Maybe cargo flamegraph isn't setting the CARGO_MANIFEST_DIR when it should be, or its setting it to the wrong value? Maybe running the binary from a different folder / working directory?

I've found that disabling the "file_watcher" and "asset_processor" features enables a working build, but of course this then leaves the application without any of the assets it may need, yielding a bunch of "bevy_asset::server" errors, but ultimately compiling and executing with a flamegraph output.


Customize base build image via build args

Currently, the base image is hardcoded to buildpack-deps:bionic.
It's a good idea to customize this - particularly to point at registry cache to avoid dockerhub pull limits (and cleaner than modifying the configuration to use a different default registry).
I can push a relatively straightforward patch if that's OK

This is a duplicate of https://github.com/jupyterhub/repo2docker/issues/487
Please feel free to add any additional information or ideas there!


Backport #20616 #20673

Backport of:

Release 3.8 binary wheels #20616
Add manylinux2010_x86 wheels into artifacts #20673

grpc_build_artifacts_multiplatform
grpc_build_artifacts_extra_release


Certificate verify failed (unable to get local issuer certificate)

Getting SSL Cert Error with 1.15.0 Docker Image
ferrarimarco/github-changelog-generator:latest
Version: 1.15.0
Fetching tags...
Traceback (most recent call last):
	43: from /usr/local/bundle/bin/github_changelog_generator:23:in `<main>'
	42: from /usr/local/bundle/bin/github_changelog_generator:23:in `load'
	41: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/bin/github_changelog_generator:5:in `<top (required)>'
	40: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator.rb:35:in `run'
	39: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/generator/generator.rb:46:in `compound_changelog'
	38: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/generator/generator_tags.rb:10:in `fetch_and_filter_tags'
	37: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:85:in `get_all_tags'
	36: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:397:in `check_github_response'
	35: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:56:in `retriable'
	34: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:56:in `times'
	33: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:61:in `block in retriable'
	32: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:398:in `block in check_github_response'
	31: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:85:in `block in get_all_tags'
	30: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:112:in `github_fetch_tags'
	29: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:93:in `calculate_pages'
	28: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:397:in `check_github_response'
	27: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:56:in `retriable'
	26: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:56:in `times'
	25: from /usr/local/bundle/gems/retriable-3.1.2/lib/retriable.rb:61:in `block in retriable'
	24: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:398:in `block in check_github_response'
	23: from /usr/local/bundle/gems/github_changelog_generator-1.15.0/lib/github_changelog_generator/octo_fetcher.rb:94:in `block in calculate_pages'
	22: from /usr/local/bundle/gems/octokit-4.14.0/lib/octokit/client/repositories.rb:528:in `tags'
	21: from /usr/local/bundle/gems/octokit-4.14.0/lib/octokit/connection.rb:84:in `paginate'
	20: from /usr/local/bundle/gems/octokit-4.14.0/lib/octokit/connection.rb:156:in `request'
	19: from /usr/local/bundle/gems/sawyer-0.8.2/lib/sawyer/agent.rb:94:in `call'
	18: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/connection.rb:138:in `get'
	17: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/connection.rb:387:in `run_request'
	16: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/rack_builder.rb:143:in `build_response'
	15: from /usr/local/bundle/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:115:in `call'
	14: from /usr/local/bundle/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:142:in `call!'
	13: from /usr/local/bundle/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:195:in `process'
	12: from /usr/local/bundle/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:290:in `fetch'
	11: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/response.rb:8:in `call'
	10: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/adapter/net_http.rb:38:in `call'
	 9: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/adapter/net_http.rb:92:in `with_net_http_connection'
	 8: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/adapter/net_http.rb:43:in `block in call'
	 7: from /usr/local/bundle/gems/faraday-0.17.0/lib/faraday/adapter/net_http.rb:85:in `perform_request'
	 6: from /usr/local/lib/ruby/2.6.0/net/http.rb:1228:in `get'
	 5: from /usr/local/lib/ruby/2.6.0/net/http.rb:1470:in `request'
	 4: from /usr/local/lib/ruby/2.6.0/net/http.rb:919:in `start'
	 3: from /usr/local/lib/ruby/2.6.0/net/http.rb:930:in `do_start'
	 2: from /usr/local/lib/ruby/2.6.0/net/http.rb:996:in `connect'
	 1: from /usr/local/lib/ruby/2.6.0/net/protocol.rb:44:in `ssl_socket_connect'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unable to get local issuer certificate) (OpenSSL::SSL::SSLError)

Should be solved in the latest release


Commit new solution files for Data Structures

Visit HackerRank's Data Structures website, visit the subdomains and commit new problem solutions at the repo's Data Structures folder.
Rules:

Solutions must be correct (obviously), I will review them before merging.
The solution's directory path must be according to the subdomain HackerRank provides for Data Structures. Example: /Data Structures/Subdomain name/Solution.java or /Data Structures/Subdomain name/RelevantFileName.java
Code can be done in any preferred language but Java and JavaScript are recommended. Someone who provides the solution in Kotlin/PHP (or any other language except recommended ones) will be considered later.
Code should be formatted properly. Unformatted code will be disregarded.
The solution you submit should be of your own.

Will C++ and Python accepted or not?

When can I start working in this?

Hey, can i work on this ?

@rajvijen yes, it will be accepted but if someone provides a correct solution for the same with Java/JavaScript then his/her solution will be added.
@cfsnsalazar @aayushbhan you can start working but make sure you follow the rules and you don't work on a same problem.


Use fork choice to determine finalized_checkpoint in gossip validation

Update gossip validation rules to use the highest finalized_checkpoint across all branches (store.finalized_checkpoint), instead of the one on the currently selected branch (state.finalized_checkpoint) when deciding whether to ignore a block / blob because they are already finalized.

even though it may not be different

notably, it doesn't move backwards when you reorg

It actually may move backwards with the new system, w.r.t. light client data. The old spec tracked the best update across all branches (including orphaned ones), while the new one only considers the current branch, which may have lower sync committee participation. is_better_update prefers older data to reduce the risk for reorgs, though, making this rather theoretical. In practice, any supermajority participation > 2/3 works similarly well, and having a shared canonical view of what is considered the best LightClientUpdate per period has higher value than some peers potentially having an update that has 1-2 more participants than what the other peers have seen.

Ah, oops, was commenting on the wrong PR. NVM


Don't change HOMEBREW_GITHUB_PACKAGES_AUTH if it is already set.

Right now, I can't directly pass HOMEBREW_GITHUB_PACKAGES_AUTH, making it difficult to configure a separate packages authentication header from Docker-related credentials. This may be a regression via the refactor in 04938efc2429e1b40f3a3ff8fe8f2446b104b1ff and makes it difficult to use GitHub packages along side a non-GitHub Docker registry (such as DockerHub or ECR).
If HOMEBREW_GITHUB_PACKAGES_AUTH is unset, it still borrows the value from HOMEBREW_DOCKER_REGISTRY_BASIC_AUTH_TOKEN or HOMEBREW_DOCKER_REGISTRY_TOKEN.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This may be a regression via the refactor in 04938ef and makes it difficult to use GitHub packages along side a non-GitHub Docker registry (such as DockerHub or ECR).

We've never supported setting HOMEBREW_GITHUB_PACKAGES_AUTH, and it appears the env never existed before that commit too.
But that shouldn't matter. Can you describe why HOMEBREW_DOCKER_REGISTRY_TOKEN and HOMEBREW_DOCKER_REGISTRY_BASIC_AUTH_TOKEN are not suitable? The scope of them are no different to HOMEBREW_GITHUB_PACKAGES_AUTH so this PR doesn't seem to change much.

We've never supported setting HOMEBREW_GITHUB_PACKAGES_AUTH, and it appears the env never existed before that commit too.

Yes, it's just an internal implementation detail.


Use specs2

The barebones hook-in to specs2.

Good enough for now. Should file a ticket to track moving the assertions over fully.


proxy-patch for fabric v2 peer

This should enable proxy support for the v2 peer.
Should be only temporary necessary until externalbuilder support is there.
PS (Marcus): if this is added, you actually can remove all the other (obsolete) patches and instructions and docker should be fine as in the original version!

@g2flyer this needs a rebase patch must be applied "again"

btw: what is also annoying is that each clean build seems to touch both go.mod and go.sum!  I think  the problems are the // indirect links in go.mod. We probably should do a go mod tidy before checking in go.mod when it contains indirect references?

Note the way we build the dev docker image right now, it is build from master and not from the pr, so travis will fail right now, but should work once this pr is merged.  (The underlying problem is of course the same as the one in #269 ...)

Travis build failed:
error: patch failed: core/chaincode/chaincode_support.go:8
error: core/chaincode/chaincode_support.go: patch does not apply
Applying: proxy-enable chaincode containers if necessary
Patch failed at 0001 proxy-enable chaincode containers if necessary
Use 'git am --show-current-patch' to see the failed patch

LGTM! I verified that patch can be applied on Fabric v2.0.1 release tag - cannot perform functional test as not sitting behind a proxy. @bvavala please do you review and we are good to go. Thanks!

Travis failed. Is it expected?

Travis failed. Is it expected?

yes, see my comment two comments above yours ....

One other note: you might have to manually pull the image hyperledger/fabric-ccenv:2.0.  the underlying go-dockerclient doesn't seem to support proxy when pulling images and if you do not have that image ledger_init might timeout ....


Unable to open ... File not found issue while trying to debug code inside NuGet via sourcefilemap option

Environment data
dotnet --info output:
VS Code version:1.23.1
C# Extension version: 1.15.1
Steps to reproduce

Create a c# class library project and generate NuGet package which also include source files for the class library.

Create a nunit project add the NuGet Project and update sourceFileMap in Launch.json
"sourceFileMap": {
"C:\Users\{userid}\.nuget\packages\{projectName}\version\src": "c:\src"
},

Try to debug the code in nunit project and access class library code.

Expected  behavior
VSCode should load the code from class library project from the given path in sourcefilemap
Actual behavior
4Instead of searching in the give path mentioned in sourcefilemap , vscode is searching in the path from where NuGet package is created(The path of class library project)
Kindly Help.

To be clear, is your source file map using \\ or \ to separate path entries? (GitHub formats it as a single backslash, but I am assuming you are using double backslashes).
Furthermore, when you say 'c:\Users{userid}' I am assuming that '{userid}' is a replacement value in your example, and in your actual launch.json you have placed your real user id.
Lastly, when you say "VSCode should load the code from class library project" you mean that when you step into your class library (or stop in an exception), you are seeing it open up the code from there. Is that correct?
Assuming my three assumptions are right - your sourceFileMap looks correct. I am guessing you have some sort of typeo there such that the two paths don't quite match. Can you double check?


SSL Error HttpErrorConnClosed version 0.11

I'm running nodejs listening at port 8181 on locahost
After last update from release 0.10 to 0.11 starting a upstream/forward proxy:
 mitmproxy -U http://localhost:8181 -p 11112

I get SSL errors when connecting to localhost:
>> CONNECT apic.musixmatch.com:443
           ← HttpErrorConnClosed('Server disconnect.',)
   CONNECT apic.musixmatch.com:443
           ← HttpErrorConnClosed('Server disconnect.',)

(Originating URI is over HTTPS)

The error happens in upstream -Umode only.

Adding that via script If I do via flows it works properly intercepting the host
def request(context, flow):
    if flow.request.pretty_host(hostheader=True).endswith("musixmatch.com"):
        flow.request.host = "localhost"
        flow.request.port = 9999
        flow.request.scheme = 'http'
        flow.request.update_host_header()

Hi @loretoparisi,
do you have a node proxy or a node web application running on 8181? -U is the upstream proxy mode, which expects another proxy upstream. You're probably looking for the regular proxy mode with the inline script you posted above?
Cheers,
Max

Uhm right question! It's a nodejs api listening on 8181 i.e.
server.listen(  process.env.PROXY_PORT || process.env.port || config.server_port);

If it's a regular application, you should not use upstream proxy mode. http://mitmproxy.org/doc/modes.html

thanks that's correct.


Failure when trying to run MS Learn Lab for Build Serverless API with Functions API Management Exercise

https://docs.microsoft.com/en-us/learn/modules/build-serverless-api-with-functions-api-management/3-exercise-import-function-app-api-management
This is autogenerated. Please review and update as needed.
Describe the bug
This error was encountered when running bash setup.sh in the instructions on this page in MS Learn:  https://docs.microsoft.com/en-us/learn/modules/build-serverless-api-with-functions-api-management/3-exercise-import-function-app-api-management
Command Name
az functionapp create
Errors:
The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az functionapp create --resource-group {} --consumption-plan-location {} --name {} --storage-account {} --runtime {}

Expected Behavior
Probably a change in the CLI or default commands that needs to be updated in the github repo that is pulled down in this step.
Environment Summary
Linux-4.15.0-1061-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.75

Additional Context

duplicate of https://github.com/Azure/azure-cli/issues/11098
This is not an Azure CLI issue, the script in the Learn module is written against westus region, please change it to another US region (ex. centralus)
You may also want to open the issue against the Learn repo https://github.com/MicrosoftDocs/mslearn-apim-and-functions


feat: implement useControlledRerenderState hook

What new hook does?
Like React.useState, but its state setter accepts extra argument, that allows to cancel rerender.
Checklist

[x] Have you read contribution guideline?
[x] Does the code have comments in hard-to-understand areas?
[ ] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?
[x] Have the docs been updated?
[x] Have the tests been added to cover new hook?
[x] Have you run the tests locally to confirm they pass?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Errnos are available through multiple paths in nix

The current problem is the errnos (like EAGAIN) are exposed at nix::Errno::EAGAIN and nix::errno::EAGAIN. We should choose one "right" path and only expose these constants there. I'd probably keep Errno at nix::errno::Errno instead of re-exporting it in the root.

AFAIK reexporting enum variants is considered bad style (they're scoped for a reason)

Indeed. Would you be interested in taking this on and filing a PR to get this all cleaned up? I started working on this but the errno module needs more work than I realized.

I'm currently taking a look at #586, but after that's finished I can check this one out.


Convert Datastore to GAX

This PR converts all Datastore requests to the GAX client introduced in #884.
There is a breaking change: The retries parameter is no longer supported (although method signatures have not changed.) See #848 and #849 for proposals to add new configuration options for retry behavior.
Also, Datastore is one of the three services that still requires expanded acceptance testing (#759). I could add the needed tests as part of this PR if desired.

This PR should also remove files that are no longer needed for backoff, to close #893.

Not all gems are converted to GAX, so the backoff code should stay until they are all converted.

Oh right, I mistakenly thought it wasn't shared. Of course.

The fourth commit on this PR removes retries (no longer supported) from the factory methods, and adds a new client_config parameter accepting a hash of google-gax client_config values. Our intention with this change is to greatly increase client control over retry, timeout, and error handling behaviors, addressing issues such as #808.
Here is the default  datastore_client_config.json, which can be overridden via the new parameter:
{
  "interfaces": {
    "google.datastore.v1.Datastore": {
      "retry_codes": {
        "retry_codes_def": {
          "idempotent": [
            "DEADLINE_EXCEEDED",
            "UNAVAILABLE"
          ],
          "non_idempotent": []
        }
      },
      "retry_params": {
        "default": {
          "initial_retry_delay_millis": 100,
          "retry_delay_multiplier": 1.3,
          "max_retry_delay_millis": 60000,
          "initial_rpc_timeout_millis": 60000,
          "rpc_timeout_multiplier": 1.0,
          "max_rpc_timeout_millis": 60000,
          "total_timeout_millis": 600000
        }
      },
      "methods": {
        "Lookup": {
          "timeout_millis": 60000,
          "retry_codes_name": "idempotent",
          "retry_params_name": "default"
        },
        "RunQuery": {
          "timeout_millis": 60000,
          "retry_codes_name": "idempotent",
          "retry_params_name": "default"
        },
        "BeginTransaction": {
          "timeout_millis": 60000,
          "retry_codes_name": "non_idempotent",
          "retry_params_name": "default"
        },
        "Commit": {
          "timeout_millis": 60000,
          "retry_codes_name": "non_idempotent",
          "retry_params_name": "default"
        },
        "Rollback": {
          "timeout_millis": 60000,
          "retry_codes_name": "non_idempotent",
          "retry_params_name": "default"
        },
        "AllocateIds": {
          "timeout_millis": 60000,
          "retry_codes_name": "non_idempotent",
          "retry_params_name": "default"
        }
      }
    }
  }
}

As you can see, there are some interesting fields, such as retry_codes, which suggests the ability to configure retry logic based on error status codes. At this time there is not much documentation for the client_config fields, but @jmuk from google-gax is working with us and should be able to answer questions.
Please note that this leaks the GAPIC implementation to the google-cloud-datastore public API. If google-gax changes its implementation, this may result in a change to the google-cloud-datastore public API.
@timanovsky @bmclean Any feedback on this proposal? We hope to merge and release this PR next week.

@quartzmo Please correct me if I have any of this wrong:
For a datastore Lookup, since it has a retry_codes_name defined of "idempotent", if an UNAVAILABLE error was raised, it would retry using the default params.
For a datastore Commit,  since it has a retry_codes_name defined of "non_idempotent", any error raised would not be retried.

@bmclean I'll take a swing at answering your question. Yes, your understanding is correct. That is the default behavior. We asked several times which endpoints we should retry and which ones we should not. But we never got an answer so we did a blanket retry on them all. I believe that this new behavior is correct.
Of course, the good news is that you can now override how each endpoint is treated and use whatever behavior you wish. :)

@blowmage What do you mean by "blanket retry on them all"?

Correct. Not all errors, and not all endpoints should be retried. Of course, you are free to override the default configuration and make it behave as you want.

Thanks. I agree that the proposed default config is correct. For Lookup and RunQuery, if datastore returns either a DEADLINE_EXCEEDED or UNAVAILABLE error the request is retried as per the retry configuration. For all other endpoints, the default is not to invoke the retry logic.

This new configuration comes from Google. It has been hard for those of us outside of Google to get this information, so we are happy to finally get this level of guidance. :smile:

@blowmage I believe I've updated this PR with everything it needs to match the merged GAPIC conversions for Vision and Pub/Sub. PTAL!

oops wrong comment button


Replace gcc12 with gcc11 due to binutils 2.38 bug

Description
Replace gcc12 with gcc11 due to binutils 2.38 bug
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/4379#issuecomment-2083623882
https://github.com/opensearch-project/opensearch-build/issues/4379#issuecomment-2084133839
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Waiting:

https://github.com/opensearch-project/k-NN/pull/1665

https://build.ci.opensearch.org/job/docker-build/5233/console

https://build.ci.opensearch.org/job/docker-copy/1163/console


Fetching ISO vs ISO-joint-published standards

Fetching ISO 2382 vs ISO/IEC 2382 results in a difference on what is returned.
From @opoudjis :

These are joint ISO/IEC standards. Referencing ISO 2382 instead of ISO/IEC 2382 is going to result in a mismatch with what has been fetched, and Relaton (correctly) is refusing to process it further.

@andrew2net could you help fix this (and spec it)? Thanks!

What is there to fix though? It is correct that ISO/IEC 2382 works and ISO 2382 does not. You should be providing the exact document identifier for fetching that ISO itself uses, not a truncation of it.

Well, what you said is true but can often cause confusion. For example, people often refer to "ISO/IEC 27001" as "ISO 27001", and we should not bail on such since we have the information to recover from this. At most we should return a "warning". Right?

That's assuming you can trust the user to mean "ISO/IEC 27001" when they say "ISO 27001". Is it guaranteed that there will never be an ISO/X nnnn standard and an ISO/X nnnn standard with the same number? If so, as long as ISO is the first named body in the list of standards bodies.... I guess it's OK.

Yes, the ISO project number for joint publishing will not be reused.
If there is an ISO/IEC 27000, then:

ISO only has ISO/IEC 27000
IEC may have IEC 27000

@ronaldtse @opoudjis Could you explain how we can get what user means ISO/IEC 2382 when he refers to ISO 2382?

@andrew2net at ISO, a project number is only assigned once. For example, 2382 can be assigned to ISO 2382, or ISO/IEC 2382 or ISO/IEEE 2382 or ISO/IEC/IEEE 2382.
In this case, 2382 is assigned to ISO/IEC 2382. This means that ISO 2382, ISO/IEEE 2382 and ISO/IEC/IEEE 2382 all don't exist.
So if user searches for ISO 2382 and the result gives ISO/IEC 2382, it means the correct ID is ISO/IEC 2382.

@opoudjis so we should try ISO 2382 first. If no documents except ISO 2382-* found then we should try ISO/IEC 2382. Right?

If the prefix is ISO/IEC 2382, 2382-1 will have same prefix. But yes, if a search for ISO 2382 fails, try ISO/IEC 2382. I guess the hope is that a search for ISO 2382 will retrieve ISO/IEC 2382, and that we will do a prefix match so that that results will not be rejected.

@opoudjis I'm trying to understand when the search fails. If I search for ISO 2382 it returns me documents:
ISO 2382-7:1977 Data processing -- Vocabulary -- Section 07 : Digital computer programming [Withdrawn]
ISO 2382-5:1974 Data processing -- Vocabulary -- Section 05 : Representation of data [Withdrawn]
...

How can I determine that the search failed?

Agree with @opoudjis, the search should not match part documents (ISO 2382-X).

@opoudjis done it. Please check if all ok.


New version: UncertainData v0.7.0

Registering package: UncertainData
Repository: https://github.com/kahaaga/UncertainData.jl
Created by: @kahaaga
Version: v0.7.0
Commit: fe5ff19c4b13d850f7a18677058303326041eac9
Reviewed by: @kahaaga
Reference: https://github.com/kahaaga/UncertainData.jl/issues/112#issuecomment-544900095

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: Distributions, HypothesisTests, DynamicalSystemsBase, Interpolations, Measurements, Bootstrap, Combinatorics, KernelDensity, StatsBase, DocumenterTools, Unitful, julia, StaticArrays, IntervalArithmetic, RecipesBase, Reexport

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]


org.apache.commons:commons-io - J2ObjC continuous build

The Apache Commons IO library.
@krosenvold @jmaerki - FYI for you both. This is to support translation of your Java library to Objective-C such that it can be used on iOS. This bug is specifically for testing this as part of a continuous build using Google's J2ObjC conversion tool.
@advayDev1 FYI

@brunobowden - I don't see any up to date version (2.3+) of this on maven central.  The 1.3.2 version seems suspect, the POM for it has no copyright notices etc. like the other org.apache libraries...
http://search.maven.org/#search|ga|1|a%3A"commons-io"

You want "commons-io:commons-io" and not "org.apache.commons:commons-io".
Not sure why they changed the package name. Confirmation from here:
http://stackoverflow.com/a/5592255/1509221
On Sat, Sep 26, 2015 at 4:10 PM Advay Mengle<EMAIL_ADDRESS>wrote:

@brunobowden https://github.com/brunobowden - I don't see any up to
date version (2.3+) of this on maven central. The 1.3.2 version seems
suspect, the POM for it has no copyright notices etc. like the other
org.apache libraries...
http://search.maven.org/#search|ga|1|a%3A"commons-io"
—
Reply to this email directly or view it on GitHub
https://github.com/j2objc-contrib/j2objc-common-libs-e2e-test/issues/12#issuecomment-143503644
.


⚠ RPC server - Conflux has degraded performance

In 5cd2642, RPC server - Conflux ($CONFLUX_RPC_URL) experienced degraded performance:

HTTP code: 200
Response time: 12428 ms

Resolved: RPC server - Conflux performance has improved in e21e989 after 7 minutes.


Please reopen 50417

I believe it still happens per the bug I opened, misguidedly, on npm - https://github.com/nodejs/node/issues/31269

Does this occur with all extensions disabled as well?

/needsMoreInfo

Is there some easy way to save/restore the set of extensions to do such troubleshooting? If the answer is no - I'm in the middle of time critical work right now and unless this is super easy its probably going to be easier to answer that question yourself.

Yep, you can launch code with code --disable-extensions to turn off extensions for just the current instance.

Ah, so I can't test this with extensions disabled sorry. I attempted it:(. I'm working from a windows desktop (as explained in the node bug I filed) - without extensions the remote-wsl extension isn't present, and so I can't get into the context of where I would be able to reproduce the issue. Trying to install the remote extension after launching with code --disable-extensions  results in an error about the gallery missing.


common_to_all_curves.weighted_curve

Need to finish implementing/testing. Attempt a test-driven development pattern if possible!

redundant issue


refactor(popover): Simpler interface for NPopover

I've made simpler interface for Popover, which is also more similar to nuxt/ui.
Breaking changes and migration:

Replace radix-vue's required PopoverTrigger with the default slot.
Replace usage of NPopoverContent with the popper slot.
Props for <NPopoverContent> can be passed via the <NPopover :popper="{}">

Old code:
<NPopover>
  <NPopoverTrigger as-child>
    <NButton>Click me</NButton>
  </NPopoverTrigger>
  <NPopoverContent align="start" class="w-80">
    Popover content
  </NPopoverContent>
</NPopover>

New, simpler code:
<NPopover :popper="{align: 'start', class: 'w-80'}">
  <NButton>Click me</NButton>
  <template #popper>
    Popover content
  </template>
</NPopover>

Hello @killjoy1221, I understand that Una-UI currently doesn't have a clear anatomy or architecture yet. but here's my insight on this:
Props
In the Nuxt UI Popover component from the current version, they are using HeadlessUI for their unstyled components, which we are no longer using in our upcoming components including this one. Since we are now using Radix Vue's Popover for this, we're aiming to maintain its anatomy as much as possible. This approach will make Una-UI more future-proof for upcoming updates in Radix (e.g., additions or changes in props and emits), by simply passing all the current props through subcomponents (e.g., _popoverContent). This way, it will be easier for us to refer to Radix docs for additional API information.
Note that the NuxtUI team is also migrating from HeadlessUI to RadixUI. In fact, Una-UI is the closest to following the same direction. You can check their Popover repo here: https://github.com/nuxt/ui/blob/v3/src/runtime/components/Popover.vue#L22.
Slots
But you have a good point here, in having slot instead of using PopoverContent, this is really good idea. same what we have in https://unaui.com/components/tooltip#slots.
❌  old code
<NPopover>
  <NPopoverTrigger as-child>
    <NButton>Click me</NButton>
  </NPopoverTrigger>
  <NPopoverContent align="start" class="w-80">
    Popover content
  </NPopoverContent>
</NPopover>

✅ new code
<NPopover
	:_popover-content={
	    side: 'top',
	}
>
      <NButton>Click me</NButton>

	  <template #content>
	      Popover content
	  </template>
</NPopover>

for _popover-content props, it can pass what ever available props in https://www.radix-vue.com/components/popover.html#content

What do you think, @killjoy1221 @mnenie ? Feel free to add your suggestions here 💛 . You're really doing a good job. We are being enlightened to improve this Popover."
Let me know if you'd like any further changes! 🚀

Hello @killjoy1221, I understand that Una-UI currently doesn't have a clear anatomy or architecture yet. but here's my insight on this:
Props
In the Nuxt UI Popover component from the current version, they are using HeadlessUI for their unstyled components, which we are no longer using in our upcoming components including this one. Since we are now using Radix Vue's Popover for this, we're aiming to maintain its anatomy as much as possible. This approach will make Una-UI more future-proof for upcoming updates in Radix (e.g., additions or changes in props and emits), by simply passing all the current props through subcomponents (e.g., _popoverContent). This way, it will be easier for us to refer to Radix docs for additional API information.
Note that the NuxtUI team is also migrating from HeadlessUI to RadixUI. In fact, Una-UI is the closest to following the same direction. You can check their Popover repo here: https://github.com/nuxt/ui/blob/v3/src/runtime/components/Popover.vue#L22.
Slots
But you have a good point here, in having slot instead of using PopoverContent, this is really good idea. same what we have in https://unaui.com/components/tooltip#slots.
❌ old code
<NPopover>
  <NPopoverTrigger as-child>
    <NButton>Click me</NButton>
  </NPopoverTrigger>
  <NPopoverContent align="start" class="w-80">
    Popover content
  </NPopoverContent>
</NPopover>

✅ new code
<NPopover
	:_popover-content={
	    side: 'top',
	}
>
      <NButton>Click me</NButton>

	  <template #content>
	      Popover content
	  </template>
</NPopover>

for _popover-content props, it can pass what ever available props in https://www.radix-vue.com/components/popover.html#content
What do you think, @killjoy1221 @mnenie ? Feel free to add your suggestions here 💛 . You're really doing a good job. We are being enlightened to improve this Popover.
Let me know if you'd like any further changes! 🚀

@phojie looks good

@phojie Sounds like a good idea. I'll work on making the changes.

All set!

Thanks for this @killjoy1221 , do you want to join us in discord ? please drop your id here 💛

@phojie I'm<PHONE_NUMBER>77511425

@killjoy1221 , looks like I cant see your account, but heres the invitation link.
https://discord.gg/CjRKzEzD
come join with us! 💛


JS API Error message should contain index position

When using JS API, code as below:
standard.lintText('var a = 1\n1var b=2;', {fix: true}, (err, result)=>{
	console.log(err, result)
})

the error object of callback result
null { filePath: '<text>',
  messages:
   [ { ruleId: null,
       fatal: true,
       severity: 2,
       source: 'var a = 1\n1var b=2;',
       message: 'Parsing error: Identifier directly after number',
       line: 2,
       column: 2 } ],
  errorCount: 1,
  warningCount: 0,
  source: 'var a = 1\n1var b=2;' }

There's should add aditional index: 12  in the above result, for better locating the error.
This will good for editors like Emacs, to goto-char in source position instead of line+column combination.

We're currently just returning the object that ESLint provides. If you want that additional information, you can read in the file and calculate the index yourself.

That's ok, for anyone encountered the same problem, I've created a tool for adding index field:
https://github.com/futurist/src-location


[Doc Improvement][SEO description update 10][3876708]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/develop-your-apps-with-teams-toolkit.md
98
1
link
:white_check_mark:

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
91
13
link
:white_check_mark:

msteams-platform/concepts/build-and-test/prepare-your-o365-tenant.md
92
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-personal-app-or-tab.md
93
3
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-overview.md
94
2
link
:white_check_mark:

msteams-platform/concepts/build-and-test/tool-sdk-overview.md
93
12
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md
86
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/build-app.md
88
3
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/gain-traction.md
84
45
link
:white_check_mark:

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/develop-your-apps-with-teams-toolkit.md
98
1
link
:white_check_mark:

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
91
13
link
:white_check_mark:

msteams-platform/concepts/build-and-test/prepare-your-o365-tenant.md
92
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-personal-app-or-tab.md
93
3
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-overview.md
94
2
link
:white_check_mark:

msteams-platform/concepts/build-and-test/tool-sdk-overview.md
93
12
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md
86
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/build-app.md
88
3
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/gain-traction.md
84
44
link
:white_check_mark:

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/develop-your-apps-with-teams-toolkit.md
98
1
link
:white_check_mark:

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
91
13
link
:white_check_mark:

msteams-platform/concepts/build-and-test/prepare-your-o365-tenant.md
92
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-personal-app-or-tab.md
93
3
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-overview.md
94
2
link
:white_check_mark:

msteams-platform/concepts/build-and-test/tool-sdk-overview.md
93
12
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md
86
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/build-app.md
88
3
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/gain-traction.md
84
44
link
:white_check_mark:

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


defer/streaming SSR isn’t responding with the fallback UI on iOS Safari

What version of Remix are you using?
v1.14.2 (repro on v1.11)
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
Load https://simple-remix-deferred-demo.fly.dev/ from jacob-ebey/stupid-simple-remix-deferred-demo (just an example of an easy hosted repro from a contributor) in Safari on iOS. After the initial load, also reload the page a few times.
If it helps, I am on the 16.4 beta but have seen this issue for non-beta minor releases since defer was introduced. I am able to reproduce it on other WebKit browsers on iOS, with extensions, content blockers and iCloud Private Relay disabled.
Expected Behavior
The skeleton UI should be immediately visible, and the data should load a second later. When inspecting the source of the webpage, the response HTML from the initial request should include the HTML for the suspense fallback.
Actual Behavior
The page waits a second and then loads all at once. When inspecting the source of the webpage, the fully-loaded HTML is present in the response instead of the fallback HTML.
A couple of notes that made this hard to diagnose:

On the initial load it shows up quite quickly, but this is just because Safari preloads URLs and not because streaming is working there. If you want to see for yourself, you can try with a longer initial load, say 5 seconds.
On reloads, it keeps the page as-is and just reloads a couple of the images. But you can tell that the actual request is taking longer by connecting to a Mac and using the Web Inspector, or just by observing the loading bar.

Here’s a video of a few different loading scenarios:
https://user-images.githubusercontent.com/2456132/225180800-7b58c50e-ddaa-4469-ab4c-ad7ee11b1611.mov
Some more background & thoughts
I was originally splitting a normal webpage load into a deferred and awaited call, and was assuming that the awaited call was bottlenecking the page. But when I created a new loader with some deferred data, it became clear that I’d actually been seeing this issue for months.
I have no idea how to diagnose and handle this issue, I have no idea whether it’s Remix, react-router, React, Safari, or whatever. I don’t really know if it’s even a bug and not something weird with my own setup (I’ve tried everything I can think of there), but I’m filing it in case a kind soul can and reproduce it :)

Safari buffer the HTML response until it reach a certain kb size, if your HTML is smaller it will buffer it and give it time to your deferred data to finish, so this could be causing that behavior.

@sergiodxa Really interesting! Found the same behaviour on this repo. I will investigate a bit later today and if that’s the fix I’ll close this as an upstream problem.

Yeah, the only workaround I could find is to pad out the page to the rough limit for Safari, which seems to be around ~650B gzipped, but this is extremely annoying and there’s no good way to dynamically resize the pad (I tried transforming the output stream, but that just puts it at the end of the stream which Safari doesn’t count).
Very annoying! But definitely not something the Remix team can deal with.

I recently ran in to this problem when trying to configure Remix to stream the HTML response. Just like OP I was a bit confused why streaming didn't work as described on iOS.
Eventually I found a similar bug report for SvelteKit which had resulted in WebKit Bug 252413:WebKit is too conservative in its first paint threshold
This problem/bug/optimization (depending on how you see it) is obviously not something that Remix, or any other framework, can fix in itself.
However, consider if this should be documented in Streaming to prevent more people from being confused.

Solve
Add for safari html tag
// example react - 200 sequence  \u200b
const sp = '\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b'


ERROR: Signature extraction failed

tux ~ % youtube-dl --version
2014.10.15
tux ~ % youtube-dl -x --audio-format mp3 --audio-quality 0 'https://www.youtube.com/watch?v=VwjwKn9ARzY'
[youtube] Setting language
[youtube] Confirming age
[youtube] VwjwKn9ARzY: Downloading webpage
[youtube] VwjwKn9ARzY: Downloading video info webpage
[youtube] VwjwKn9ARzY: Extracting video information
[youtube] VwjwKn9ARzY: Encrypted signatures detected.
[youtube] VwjwKn9ARzY: Downloading js player vflWLYnud
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/home/cub/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 533, in _decrypt_signature
video_id, player_url, s
File "/home/cub/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 447, in _extract_signature_function
res = self._parse_sig_js(code)
File "/home/cub/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 508, in _parse_sig_js
'Initial JS player signature function name')
File "/home/cub/bin/youtube-dl/youtube_dl/extractor/common.py", line 424, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
(caused by RegexNotFoundError(u'Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.',)); please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

You are using a very OLD version of youtube-dl. Please update it following the instructions.


NumericField Trunc-ing

Was trunc-ing all numbers.
I changed (int) to (float) on lines 31 and 38 /field/NumericField.php.

Numeric fields holds only integer values. If you would like to return value in particular way use filter instead of modifying code base https://github.com/majkel89/dbase#filters

Do filters have precendence over the truncated value of the field? For example, will a (for example) FloatingPointFilter do the trick to store floats in numeric fields?

Apparently no (https://github.com/majkel89/dbase/blob/master/src/field/NumericField.php#L38).
I missed the fact that Numeric field can store floating point numbers (http://www.oocities.org/geoff_wass/dBASE/GaryWhite/dBASE/FAQ/qformt.htm).
The solution to your problem would be to drop casting to integer and truncating ;-)
Casting to floating point number could in some edge cases result in loosing precision.
I would be glad if you push PR for this.

Well, I have been using a fork of your library for a while now (https://github.com/emielmolenaar/dbase/commit/4a3285f55d82dadf3311ed1eaa008411020bb3a5) . It's working fine, but I have no idea if such a PR would break stuff for others. We might just have to check the type of the incoming value and return the same type of value.

The issue seems to be solved in a fork in this commit: https://github.com/naril/dbase/commit/0c8828dbc374cb4ae1e1881229f69bde825a5ef5
(the fix in the previous comment only fixes the truncate on reading)

Sweet! Indeed my "fix" was just a simple hacky one to quick fix truncating. @majkel89 Would you accept a PR that merges https://github.com/naril/dbase/commit/0c8828dbc374cb4ae1e1881229f69bde825a5ef5 into this library?

@emielmolenaar could you verify that this version works for you org.majkel/dbase:dev-decimal-fixes

@emielmolenaar Did you verified the package (org.majkel/dbase:dev-decimal-fixes) that it works with decimal numbers.
If you are unable to do so please provide me sample data.

@majkel89 Excuse me for the delay, but org.majkel/dbase:dev-decimal-fixes seems to work correctly for me!

fixed i 1.1.6


[terra-navigation-side-menu] Example Update

Summary

What was changed:
Updated navigation-side-menu example.
Why it was changed:
Example does not convey name, role, value of the control.
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[x] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

@MadanKumarGovindaswamy You may have to resolve the conflict here

+1, the issue mentioned in the PR is fixed.
But there are few issue I found in the Terra Side Menu navigation component.
Issues:

When an menuitem is selected it SR does read message as "--menuitem, selected", but when user navigates away and back to the selected menutiem the selected state is not exposed to users.
Back button present in the submenu control doesn't have a contextual label.
When user lands on 'Hospital Services' sub menu- The instructions to activate with enter / space key is not announced. - (Default behaviour, checked with https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/examples/menu-button-links/)


[Storage Blob] Throw errors for unresolved imports in the browser

As seen at https://github.com/Azure/azure-sdk-for-js/issues/13267#issuecomment-762757559, unresolved "crypto" module in the browser caused the angular app to break.
This could have been caught before if the build step with rollup had thrown an error instead of a warning for the unresolved imports in the browser. This PR attempts to throw an error instead of a warning for the unresolved imports.
Example

https://github.com/Azure/azure-sdk-for-js/pull/13275 would fix the supposed rollup error (https://github.com/Azure/azure-sdk-for-js/pull/13294).
Also, we don't publish the browser bundle, but this rollup error from the build step would be capable of catching regressions before we publish the library.
@ljian3377 @jeremymeng @bterlson @xirzec @witemple-msft

Looking good. Let's also change it for the other packages including storage-blob-changefeed and storage-internal-avro.
Is it viable to use a same rollup config file for all these packages?

Looking good. Let's also change it for the other packages including storage-blob-changefeed and storage-internal-avro.
Is it viable to use a same rollup config file for all these packages?


vmTools.debClosureGenerator: Fix non-determinism in dependency graph

Motivation for this change
By default, Perl versions since 5.8.1 use randomization to make hashes resistant to complexity attacks.
That randomization makes building VM images such as ubuntu1804x86_64 non-deterministic because the (imported) derivations built by deb/deb-closure.pl are not stable.
This can easily be observed by repeating the following sequence of commands and noting the path of the image's .drv file:
nix-instantiate -E '(import <nixpkgs> {}).vmTools.diskImageFuns.ubuntu1804x86_64 {}'
nix-store --delete /nix/store/*ubuntu-18.04-bionic-amd64.nix

One source of non-determinism is the handling of Provides/Replaces, which depends on the order of iteration over %packages.  Here is a diff showing the corresponding change in output:
 >>> awk
-virtual awk: using original-awk
-    original-awk: libc6 (>= 2.14)
+virtual awk: using mawk
+    mawk: libc6 (>= 2.14)
 [...]
-    mawk: libc6 (>= 2.14)
->>> libc6

This patch sorts packages by name for Provides/Replaces processing, which seems to result in stable output.
(If the above turns out not to be sufficient, one could also set the PERL_HASH_SEED and PERL_PERTURB_KEYS environment variables, documented in perlrun, to disable Perl's built-in randomization.  Complexity attacks are not an issue as we control and trust all inputs.)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

nixos/tests/os-prober.nix
nixos/tests/virtualbox.nix

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"

(None?)

[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date

(None?)

[x] Fits CONTRIBUTING.md.

nix-instantiate -E '(import <nixpkgs> {}).vmTools.diskImageFuns.ubuntu1804x86_64 {}'
nix-store --delete /nix/store/*ubuntu-18.04-bionic-amd64.nix

I've run those commands 3 times and the output is deterministic for me. Am I missing something?

nix-instantiate -E '(import <nixpkgs> {}).vmTools.diskImageFuns.ubuntu1804x86_64 {}'
nix-store --delete /nix/store/*ubuntu-18.04-bionic-amd64.nix

I've run those commands 3 times and the output is deterministic for me. Am I missing something?

  That being said, it's a possibility: I sometimes see repeats, too, and the number of combinations doesn't seem to be very high.
I just ran it 10 times; here is what I am seeing:
/nix/store/2mxm76g659d0pb4w1vdypg90592nd4my-ubuntu-18.04-bionic-amd64.drv
/nix/store/njfg4qapz840szplbbr4wkxh0wnzl28f-ubuntu-18.04-bionic-amd64.drv
/nix/store/njfg4qapz840szplbbr4wkxh0wnzl28f-ubuntu-18.04-bionic-amd64.drv
/nix/store/0v06kxjl0a2za5k7258fp24gkmfqgfpg-ubuntu-18.04-bionic-amd64.drv
/nix/store/0v06kxjl0a2za5k7258fp24gkmfqgfpg-ubuntu-18.04-bionic-amd64.drv
/nix/store/njfg4qapz840szplbbr4wkxh0wnzl28f-ubuntu-18.04-bionic-amd64.drv
/nix/store/2mxm76g659d0pb4w1vdypg90592nd4my-ubuntu-18.04-bionic-amd64.drv
/nix/store/0v06kxjl0a2za5k7258fp24gkmfqgfpg-ubuntu-18.04-bionic-amd64.drv
/nix/store/2mxm76g659d0pb4w1vdypg90592nd4my-ubuntu-18.04-bionic-amd64.drv
/nix/store/2mxm76g659d0pb4w1vdypg90592nd4my-ubuntu-18.04-bionic-amd64.drv

After running it like 10 times I finally got a hash mismatch.

After running it like 10 times I finally got a hash mismatch.

After running it like 10 times I finally got a hash mismatch.

Interesting.  No idea how to explain the relative stability in your environment.

After running it like 10 times I finally got a hash mismatch.

Interesting.  No idea how to explain the relative stability in your environment.

Hi @SuperSandro2000,
What do you think would be the next steps for this PR?  Would you have specific reviewers to suggest?
Thanks, -D

Hi @SuperSandro2000,
What do you think would be the next steps for this PR?  Would you have specific reviewers to suggest?
Thanks, -D

Great; thanks!

Great; thanks!


Create index with same expression error.

When I tried to create an index using an already indexed expression I got the following error:
mysql> CREATE INDEX commits_author_email_idxxx ON commits using pilosalib (commit_author_email);                                                                                ERROR 1105 (HY000): unknown error: there is already an index registered for the expressions: commits.commit_author_email
mysql> show indexes from commits;
+---------+------------+---------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
| Table   | Non_unique | Key_name                  | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment | Visible | Expression |
+---------+------------+---------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
| commits |          1 | commits_author_email_idx  |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
| commits |          1 | commits_author_email_idxx |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
| commits |          1 | commits_author_name_idx   |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
+---------+------------+---------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
3 rows in set (0,00 sec)

That is totally OK.
The problem appears when I restart gitbase. Somehow that index is there:
mysql> show indexes from commits;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    1
Current database: *** NONE ***

+---------+------------+----------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
| Table   | Non_unique | Key_name                   | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment | Visible | Expression |
+---------+------------+----------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
| commits |          1 | commits_author_email_idx   |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
| commits |          1 | commits_author_email_idxx  |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
| commits |          1 | commits_author_email_idxxx |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
| commits |          1 | commits_author_name_idx    |            0 | NULL        |           |           0 |        0 |        |      | pilosalib  |         |               | YES     | NULL       |
+---------+------------+----------------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+---------+------------+
4 rows in set (0,00 sec)

mysql>

@mcarmonaa let me know if you need any help. The example uses a new pilosa driver.
config file looks as follows:
db: ""
table: commits
id: commits_author_email_idxxx
expressions:
- commits.commit_author_email
drivers:
  pilosalib:
    fld-d2aea0e78bbbaf5257486fc382526d864a7243d9: commits.commit_author_email

the problem here is when you try to create an index for existing expression it returns an error, e.g.:
unknown error: there is already an index registered for the expressions: commits.commit_author_email
but it calls a Create function, so driver creates a folder structure:
    ├── [  96]  commits_author_email_idx
    │   └── [ 194]  config.yml
    ├── [  96]  commits_author_email_idxx
    │   └── [ 195]  config.yml
    ├── [ 128]  commits_author_email_idxxx
    │   ├── [ 196]  config.yml
    │   └── [ 64K]  mapping.db
    └── [  96]  commits_author_email_idxxxx
        └── [ 197]  config.yml

so you can notice dummy indexes (leftovers) without any mapping etc.
But after you restart gitbase it tries to load all indexes for certain driver which have config file.
I think, first we have to pre-check registered indexes and expressions and if it's OK call driver.Create or at least cleanup an index folder (but not physical pilosa index) on error.

I think it can be closed


Changed the font properties of entire website

changing of fonts is not required as of now , previous looks fine to me! @anmode

yeah I also like previous one.. but @shruti8302 increase the font size that look cool! in my opinion

I have restored the original font family of the website but I have not changed the other styling of the fonts which I did. So, please take a look if u guys find it relevant.

@shruti8302 I think this pR should be merged after https://github.com/anmode/grabtern-frontend/pull/224.
And it would be good if you resume your PR after this pR got merged. Meantime you can work on other UI/UX or optimization

@shruti8302 I think this pR should be merged after #224. And it would be good if you resume your PR after this pR got merged. Meantime you can work on other UI/UX or optimization

Okay


AppSettings are sometimes null during function run

I have some functions hosted in an app service plan. One of the first things they do is initialize Application Insights Telemetry by calling
        TelemetryConfiguration.Active.InstrumentationKey = ConfigurationManager.AppSettings["TelemetryConfiguration_InstrumentationKey"];

where "TelemetryConfiguration_InstrumentationKey" is defined in the application settings page for the function app.
99% of the time, the function executes fine, but I'll occasionally have a run of exceptions where it complains that that the value passed into InstrumentationKey is null, as if the AppSettings suddenly vanished. A subsequent execution runs fine.
Looking through my AI logs, it looks like cancellation was requested, so I guess the host was shutting down for whatever reason, but what's weird is that it seemed to continue to be making new function invocations during the teardown process (which is why AppSettings went away, I guess). There's a gap in the invocation logs when this happens and things kind of stop working for a few minutes before things get going again.
Any ideas what might be up? Thanks.

Hmm ... well I totally had a memory leak, I was doing some static initializing on each function call that really needed to only be done once per host. Since this is on an app plan, it was allowed to grow and grow. I'm going to close this and will reopen this if the problem reoccurs. Sorry for the bother!


DF Manual Rolls: Initiative issue when toggled off in V9

Module
DF Manual Rolls 2.2.4
Describe the issue
Unable to roll initiative with the Manual Rolls toggle feature enabled but toggled off.
To Reproduce
Steps to reproduce the behavior:
Enable to Manual Rolls toggle
2. Set the toggle to "off"
3. Attempt to roll initiative
Expected behavior
Initiative should roll normally when Manual Rolls is toggled off.
Screenshots (Optional)
Uncaught (in promise) Error: The Roll has already been evaluated and is now immutable
[Detected 2 packages: df-manual-rolls, lib-wrapper]
    at Roll.evaluate (foundry.js:6687)
    at Combat.rollInitiative (foundry.js:15589)
    at Z.🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:502)
    at Combat.<anonymous> (df-manual-rolls.js:5)
    at Generator.next (<anonymous>)
    at df-manual-rolls.js:5
    at new Promise (<anonymous>)
    at __awaiter$2 (df-manual-rolls.js:5)
    at Combat._Combat_rollInitiative (df-manual-rolls.js:5)
    at Combat.🎁Combat.prototype.rollInitiative#0 (libWrapper-wrapper.js:182)
    at CombatTracker._onCombatantControl (foundry.js:58305)
    at HTMLAnchorElement.<anonymous> (foundry.js:58198)
    at HTMLAnchorElement.dispatch (jquery.min.js:2)
    at HTMLAnchorElement.v.handle (jquery.min.js:2)
evaluate	@	foundry.js:6687
rollInitiative	@	foundry.js:15589
🎁call_wrapped	@	libWrapper-wrapper.js:502
(anonymous)	@	df-manual-rolls.js:5
(anonymous)	@	df-manual-rolls.js:5
__awaiter$2	@	df-manual-rolls.js:5
_Combat_rollInitiative	@	df-manual-rolls.js:5
🎁Combat.prototype.rollInitiative#0	@	libWrapper-wrapper.js:182
_onCombatantControl	@	foundry.js:58305
(anonymous)	@	foundry.js:58198
dispatch	@	jquery.min.js:2
v.handle	@	jquery.min.js:2

Can't reproduce in DF Manual Rolls v2.3 and FVTT v9.

Ah I missed this one when I was looking for reported issues relating to V9. I did fix this with issue #271


Update Set-OwaMailboxPolicy.md

CalendarEnabled parameter works OnPremise only.

@TomonoriAbe, yes, but CalendarEnabled is available in Exchange Online PowerShell in the two Microsoft 365 E5 tenants that I checked. The applicable/Applicable values on a cmdlet and parameter respectively are about simple availability, not intent or functionality.
The fact that CalendarEnabled doesn't work in ExO PowerShell is covered by the first sentence of the parameter description:

This parameter is functional only in on-premises Exchange.

If/when that parameter is ever made truly unavailable in ExO PowerShell, we'll update the description accordingly.
Therefore, I'm closing the PR.


indy_create_and_store_credential_def: support_revocation is documented as optional but is actually mandatory

From the documentation in api/anoncreds.rs:
/// config_json: type-specific configuration of credential definition as json:
/// - 'CL':
///   - support_revocation: whether to request non-revocation credential (optional, default false)

But if config_json is left empty, as the documentation suggests, the following error pops up:
Invalid structure: Cannot deserialize CredentialDefinitionConfig: InvalidStructure("missing field `support_revocation` at line 1 column 2")

This is due to the fact that in domain/anoncreds/credential_definition.rs CredentialDefinitionConfig::support_revocation has type bool instead of Option<bool>.

Also, this line in the comment looks like a mistake to me. Seems like it was mistakenly copy-pasted from the section above:

/// - 'CL':
It's in the documentation for the wrappers too. This was confusing & the line should be removed.

@lodo1995
We fixed parameter as optional in current master branch
Please let us know if problem wouldn't be resolved

@lodo1995 problem was solved and i am closing the ticket. You can re-open if you still experience this problem.


HADOOP-18151. Switch the baseurl for Centos 8

Description of PR
Centos 8 has reached its End-of-Life and thus its packages are no longer accessible from mirror.centos.org. We need to switch the baseurl to vault.centos.org where the packages are archived.
Please see https://www.centos.org/centos-linux-eol/ for more details.
How was this patch tested?
Through CI.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
docker
5m 48s

Docker failed to build yetus/hadoop:13467f45240.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
35m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 31s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 21s

trunk passed

+1 :green_heart:
mvnsite
0m  0s

trunk passed

+1 :green_heart:
shadedclient
53m 50s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
54m  9s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m  0s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m  0s

the patch passed

+1 :green_heart:
shadedclient
18m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

109m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit

uname
Linux cd6e20ed3764 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 415b3e640c601846d4ec630b32661d99e95779c1

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/2/testReport/

Max. process+thread count
547 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/2/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
11m 21s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 27s

trunk passed

+1 :green_heart:
mvnsite
0m  0s

trunk passed

+1 :green_heart:
shadedclient
52m 33s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
52m 53s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m  0s

the patch passed

+1 :green_heart:
shadedclient
18m 39s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

74m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit

uname
Linux 52a95bbf3e43 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / cf89b241307335039eae0a62202db873ed93b2fe

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/3/testReport/

Max. process+thread count
544 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/3/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m  7s

trunk passed

+1 :green_heart:
compile
3m 20s

trunk passed

+1 :green_heart:
mvnsite
0m 29s

trunk passed

+1 :green_heart:
shadedclient
55m 40s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
55m 59s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 17s

the patch passed

+1 :green_heart:
compile
3m 12s

the patch passed

+1 :green_heart:
cc
3m 12s

the patch passed

+1 :green_heart:
javac
3m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 18s

the patch passed

+1 :green_heart:
shadedclient
18m 43s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
32m 13s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

113m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit compile cc javac

uname
Linux 57eedfe76a3f 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5090f6d96af7be7705d4ad52ab5fe176ca5faf6

Default Java
Red Hat, Inc.-1.8.0_322-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/testReport/

Max. process+thread count
738 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console in case of problems.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
22m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
21m 55s

trunk passed

+1 :green_heart:
compile
3m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
shadedclient
45m 38s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
46m  5s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 25s

the patch passed

+1 :green_heart:
compile
3m 16s

the patch passed

+1 :green_heart:
cc
3m 16s

the patch passed

+1 :green_heart:
javac
3m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 27s

the patch passed

+1 :green_heart:
shadedclient
19m  1s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
32m 30s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

127m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit compile cc javac

uname
Linux b96557ddb2ee 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5090f6d96af7be7705d4ad52ab5fe176ca5faf6

Default Java
Red Hat, Inc.-1.8.0_312-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/testReport/

Max. process+thread count
545 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console

versions
git=2.27.0 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m  8s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
26m  6s

trunk passed

+1 :green_heart:
compile
3m 10s

trunk passed

+1 :green_heart:
mvnsite
0m 31s

trunk passed

+1 :green_heart:
shadedclient
25m 47s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
26m  9s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 19s

the patch passed

+1 :green_heart:
compile
2m 59s

the patch passed

+1 :green_heart:
cc
2m 59s

the patch passed

+1 :green_heart:
javac
2m 59s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
hadolint
0m  3s

No new issues.

+1 :green_heart:
mvnsite
0m 20s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
25m 35s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
31m 55s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

131m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit compile cc javac

uname
Linux ee3e53c280b0 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5090f6d96af7be7705d4ad52ab5fe176ca5faf6

Default Java
Debian-11.0.14+9-post-Debian-1deb10u1

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/testReport/

Max. process+thread count
571 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console

versions
git=2.20.1 maven=3.6.0 shellcheck=0.5.0 hadolint=1.11.1-0-g0e692dd

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console in case of problems.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
21m 10s

trunk passed

+1 :green_heart:
compile
3m 27s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
3m 32s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
mvnsite
0m 27s

trunk passed

+1 :green_heart:
shadedclient
19m 15s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
19m 34s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s

the patch passed

+1 :green_heart:
compile
3m 18s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
cc
3m 18s

the patch passed

+1 :green_heart:
javac
3m 18s

the patch passed

+1 :green_heart:
compile
3m 21s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
cc
3m 20s

the patch passed

+1 :green_heart:
javac
3m 20s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
hadolint
0m  2s

No new issues.

+1 :green_heart:
mvnsite
0m 18s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
18m 55s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
32m 25s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

122m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4047

Optional Tests
dupname asflicense codespell hadolint shellcheck shelldocs mvnsite unit compile cc javac

uname
Linux e56609bfea1c 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5090f6d96af7be7705d4ad52ab5fe176ca5faf6

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/testReport/

Max. process+thread count
698 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4047/6/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0 hadolint=1.11.1-0-g0e692dd

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


logo copyright - bump year

Coverage remained the same at 92.347% when pulling c905dc720d6200493b1272a792d23bbafd8241ee on SpacePossum:master_logo_year into 74397ac3439e1f8d2564f70df6e9be93c809e9fc on FriendsOfPHP:master.


chore: removed irrelevant dependency on package sensors_plus

What

We got pinged for an upgrade of package sensors_plus.
We actually have a very very limited usage of this package: only on the very first onboarding page and for a questionable added value.
I think we would be better off without this package for the moment, for maintenance reasons.
Of course if in the future we have sensible use-cases that would require sensors_plus, we would put it back in our dependencies.

Fixes bug(s)

Fixes: #4992

What was the use case for using it (accelerometer, gyroscope, and magnetometer sensors)? @monsieurtanuki @g123k any clue ?

What was the use case for using it (accelerometer, gyroscope, and magnetometer sensors)? @monsieurtanuki @g123k any clue ?

@teolemon The impact was an animation up to 30 pixels depending on the gyroscope. My guess is that there was something more ambitious, finally discarded, except for this couple of code lines.

Codecov Report
Attention: 45 lines in your changes are missing coverage. Please review.

Comparison is base (4d9c7fc) 9.54% compared to head (b614c3a) 9.54%.
Report is 16 commits behind head on develop.

Files
Patch %
Lines

...kages/smooth_app/lib/resources/app_animations.dart
0.00%
28 Missing :warning:

..._app/lib/pages/product/add_basic_details_page.dart
0.00%
5 Missing :warning:

...app/lib/pages/product/simple_input_text_field.dart
0.00%
4 Missing :warning:

...oth_app/lib/pages/onboarding/reinvention_page.dart
0.00%
3 Missing :warning:

...es/smooth_app/lib/query/barcode_product_query.dart
0.00%
3 Missing :warning:

.../smooth_app/lib/pages/navigator/external_page.dart
0.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##           develop   #5040   +/-   ##
=======================================
  Coverage     9.54%   9.54%
=======================================
  Files          325     323    -2
  Lines        16411   16411
=======================================
  Hits          1567    1567
  Misses       14844   14844

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Closing as stale.

Thank you @g123k for your review!


Minor fixes and refactoring

Minor changes and code style fixes
Implemented amazing testing system (see WhenAny tests)

Detailed description:

Add branch coverage to lcov report
Update .clang-tidy rules to avoid stupid warnings
Fix stupid GCC warning
Make style_guide more comprehensive
Add MBkkt's TODO
Implement ranged Wait/WaitFor/WaitUntil for iterators
Fix Wait tests and update test/CMakeLists.txt
Update WhenAny implementation
Make ultimate WhenAny tests using cartesian product of different params
Add InlineCore
Separate WhenAll implementation from interface
Code style fixes
WaitGroup fixes

Merged this changes in #123