HBASE-26649 Support meta replica LoadBalance mode for RegionLocator#g…

…etAllRegionLocations() (#4442)
Signed-off-by: Duo Zhang<EMAIL_ADDRESS>

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m  5s
branch-2.4 passed

+1 :green_heart:
compile
0m 53s
branch-2.4 passed

+1 :green_heart:
shadedjars
3m 57s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  1s
the patch passed

+1 :green_heart:
compile
0m 53s
the patch passed

+1 :green_heart:
javac
0m 53s
the patch passed

+1 :green_heart:
shadedjars
3m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
the patch passed

_ Other Tests _

-1 :x:
unit
0m  8s
hbase-client in the patch failed.

-1 :x:
unit
0m  7s
hbase-server in the patch failed.

18m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4485

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 41e009536aa7 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 9ea3e39d7a

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-client.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/testReport/

Max. process+thread count
64 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  5s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
1m  2s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 32s
branch-2.4 passed

+1 :green_heart:
compile
1m 33s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 23s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 37s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 16s
the patch passed

+1 :green_heart:
compile
1m 33s
the patch passed

+1 :green_heart:
javac
1m 33s
the patch passed

+1 :green_heart:
shadedjars
5m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 58s
the patch passed

_ Other Tests _

-1 :x:
unit
0m  7s
hbase-client in the patch failed.

-1 :x:
unit
0m  9s
hbase-server in the patch failed.

30m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4485

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ccd8fb0d05ea 5.4.0-1025-aws #25~18.04.1-Ubuntu SMP Fri Sep 11 12:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 9ea3e39d7a

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-client.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/testReport/

Max. process+thread count
76 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
1m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 16s
branch-2.4 passed

+1 :green_heart:
compile
2m 52s
branch-2.4 passed

+1 :green_heart:
checkstyle
0m 40s
branch-2.4 passed

+1 :green_heart:
spotless
0m 49s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 55s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  9s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 58s
the patch passed

+1 :green_heart:
compile
2m 50s
the patch passed

+1 :green_heart:
javac
2m 50s
the patch passed

+1 :green_heart:
checkstyle
0m 41s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m 33s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotless
0m 48s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 32s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 15s
The patch does not generate ASF License warnings.

41m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4485

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux f91aa6a3c023 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 9ea3e39d7a

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
62 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 54s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
1m 55s
branch-2.4 passed

+1 :green_heart:
compile
2m 48s
branch-2.4 passed

+1 :green_heart:
checkstyle
0m 41s
branch-2.4 passed

+1 :green_heart:
spotless
0m 39s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 52s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  9s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s
the patch passed

+1 :green_heart:
compile
2m 52s
the patch passed

+1 :green_heart:
javac
2m 52s
the patch passed

+1 :green_heart:
checkstyle
0m 41s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m 26s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotless
0m 39s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  7s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

32m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4485

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 46c499044010 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 2e08c69c5c

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
60 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4485/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

TestQuotaThrottle failure is being tracked by HBASE-27087.


Add Auto obm setting script

Add a tool to set OBM setting automatically.

To apply the obm settings, this piece of code seems to be rather complicated. Is it possible that we use a small program to  accomplish the same function? For example, we directly execute  "curl -X PATCH..." in shell command with subprocess.Popen or subprocess.Checkoutput

It is a little complicated because it need handle the with/without authentication and also different situation of BMC/RMM. If use shell script, it also will get complicated if consider those situation above.

👍


🐛 Bug: Replaces ; (empty statement) with {} (block statement)

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Expected
Given code like:
for (; i < lines.length && lines[i] !== until; i++);

I'd expect no changes, as the ; indicates the for's body is an intentionally empty statement
Actual
It gets changed to:
for (; i < lines.length && lines[i] !== until; i++) {}

Additional Info
Seen when verifying #309 works on @danvk's https://github.com/danvk/literate-ts/blob/5d04101f895285d838cb4cdccadc8941c86b0771/src/ts-checker.ts#L85 as referenced by #284.
Thanks again @danvk for using the plugin & filing the issue! 😄

@all-contributors please add @joshuakgoldberg for bug.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


Feat: send and receive DataWedge broadcast intents

I don't have an idea about how the contribution should be done since this is my first time tbh, I'll be more then happy if you guide me ^^
changes description :
2 methods are added to send and receive broadcast intents, they will give the chance to integrate DataWedge intent  commands ( create/update profile , get DataWedge version , custom broadcast intent filters etc )

registerBroadcastReceiver :
gives the ability to register custom broadcast receivers , example :

    const filterActions = [
      "com.symbol.datawedge.api.RESULT_ACTION",
      "com.example.ACTION"
    ]
    const filterCategories = ["android.intent.category.DEFAULT"]
    const filter = { filterActions, filterCategories }
    await DataWedge.registerBroadcastReceiver(filter)

sendBroadcastWithExtras :
gives the ability to send broadcast intents with extras, with it we can implement any DataWedge api commands,
example :

await DataWedge.sendBroadcastWithExtras({
      action: "com.symbol.datawedge.api.ACTION",
      extras: {
        "com.symbol.datawedge.api.SET_CONFIG": {
          PROFILE_NAME: "Example",
          PROFILE_ENABLED: "true",
          CONFIG_MODE: "UPDATE",
          PLUGIN_CONFIG: {
            PLUGIN_NAME: "INTENT",
            RESET_CONFIG: "true",
            PARAM_LIST: {
              intent_output_enabled: "true",
              intent_action: "com.example.ACTION",
              intent_delivery: "2"
            }
          }
        }
      }
    })

Hey, thanks for sending the PR!
The feature you sent is too low-level, it should belong to a plugin package like "capacitor android intents" and not a plugin for datawedge, while it would allow to access datawedge things it would also allow access to a lot of more stuff that are not related to the datawedge and it also requires the developer to know things about datawedge android intents internals which this library aims to abstract away so that is the reason I don't really want to accept that change. The PR is still valuable because it shows minimal example of receiving android intents and we can use that code to create abstracted away methods (like getVersion(), createProfile()), feel free to implement those using the code from this PR if you want to, I would gladly accept them or fork the repo entirely ;)


OAuth node with realistic sample

Rationale
Provide OAuth node types, demonstrate its usage with a realistic sample using Twitter (v1.0) and Facebook (v2).
Sadly the two versions are different and major services use one of them, such as Twitter that uses v1.0 and Facebook that uses v2.
OAuth Work Flow
V1:
Using Twitter's API (https://dev.twitter.com/web/sign-in/implementing, replacing /oauth/authenticate with /oauth/authorize as per https://dev.twitter.com/oauth/3-legged).

Step 1: Obtaining a request token: POST /oauth/request_token with oauth_callback set to device IP address and some node-internal path (ie: http://device-ip/namespace/oauth_callback). Receive the temporary oauth_token and oauth_token_secret. Likely this is started by user accessing the device web server using his desktop/mobile web browser, at say http://device-ip/namespace/oauth_start. The HTTP request handler on the device web server is asynchronous and will delay the response while it finishes the POST request. After the POST is finished, the device web server answers the desktop/mobile web browser request with a 302 - Redirect to https://api.twitter.com/oauth/authorize?oauth_token=....
Step 2: Redirecting the user to OAuth Service Login: as per step 1, the user should use his desktop/mobile web browser to login to the service and authorize the device application (client) to use on his behalf. Once the user finishes this process at the OAuth service provider web server, it will be redirected to the oauth_callback specified before, that points to the http://device-ip/namespace/oauth_callback as per step 1. The device web server will parse the result, upon success it will convert the temporary token into a long-lived access token using the received oauth_verifier. On failure the user will be 302 - Redirect to a device web page to show the error (finish_uri node option).
Step 3: Converting the request token to an access token: as per step 2, if a valid token is received, it must be converted into a long-lived access token via POST /oauth/access_token with oauth_verifier. The response is an access token and a secret. On both success or failure the user is 302 - Redirect to finish_uri with an URI fragment indicating the current status (success or error). On success, the token string is sent on node's TOKEN output port. On failure the error is sent on node's ERROR output port.

V2:
Using Facebook's API (https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow):

Step 1: Redirecting the user to OAuth Service Login: The user access the device web server using his desktop/mobile web browser, at say http://device-ip/namespace/oauth_start. The device web server will issue a 302 - Redirect to OAuth Service Login page such as https://www.facebook.com/dialog/oauth?client_id=XXX&response_type=token&redirect_uri=http://device-ip/namespace/oauth_callback. The user should use his desktop/mobile web browser to login to the service and authorize the device application (client) to use on his behalf. Once the user finishes this process at the OAuth service provider web server, it will be redirected to the redirect_uri specified before, that points to the http://device-ip/namespace/oauth_callback. The device web server will parse the result, upon success it use the received access_token. On failure the user will be 302 - Redirect to a device web page to show the error (finish_uri node option).
Step 2: (Optional) Facebook token validation: since the token above is returned as URI fragment, it's visible and may be modified. Then Facebook recommends one to validate it using its token inspection (https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow#checktoken). This is done by using an external server (ie: your product server) with a secret and private access_token. That server should do a GET graph.facebook.com/debug_token?input_token=.... If the token is valid, then it's sent on node's TOKEN output port, otherwise error is sent on node's ERROR output port.

Suggested Node Type
V1:

Options:

client_id (string, required): the client identifier.
namespace (string, required): namespace to use to allow multiple services, such as /oauth/twitter and /oauth/facebook.
temporary_endpoint_uri (string, required): where to get the temporary request token.
authorization_endpoint_uri (string, required): where to redirect user to login and then callback our app.
access_token_url (string, required): where to get the access token given the token verifier.
finish_uri (string, required): after the process is finished, then redirect to this URI providing status as URI fragment. This should show the user the result of the operation.

Output Ports:

TOKEN (string): the access token to use (it's actually a set of URL form-encoded parameters from oauth)

V2:

Options:

client_id (string, required): the client identifier.
namespace (string, required): namespace to use to allow multiple services, such as /oauth/twitter and /oauth/facebook.
authorization_endpoint_uri (string, required): where to redirect user to login and then callback to our app.
validation_endpoint_uri (string, optional): server to reach with access token in order to validate it against spoof.
finish_uri (string, required): after the process is finished, then redirect to this URI providing status as URI fragment. This should show the user the result of the operation.

scope (string, optional): the scope to request authorization for.
Output Ports:

TOKEN (string): the access token to use.

Sample FBP
fb_oauth(oauth/v2:client_id=xxx,namespace="/oauth/facebook",authorization_endpoint_uri="https://www.facebook.com/dialog/oauth",validation_endpoint_uri="https://my-server.com/oauth-verify-token/facebook",finish_uri="/facebook-oauth.html")
fb_oauth_token_persistence(persistence/string:name="fb.oauth.token",storage="efivars")
fb_updater(facebook/status-update)
needs_fb_oauth(http-server/boolean:path="needs-fb-oauth")

fb_oauth TOKEN -> IN fb_oauth_token_persistence
fb_oauth_token_persistence OUT -> OAUTH_TOKEN fb_updater
fb_oauth_token_persistence OUT -> IN (string/is-empty) OUT -> IN needs_fb_oauth
some_content_provider OUT -> MESSAGE fb_updater

Test is to ask user to visit http://device-ip, this should contain a static HTML provided by the product with its UI/theme that will query http://device-ip/needs-fb-oauth (node option), if it's true, then it will show a facebook login button. Click that button and it will go to http://device-ip/oauth/facebook/oauth_start (based on node option). User will be then redirected to Facebook's website. Once the OAuth process finishes, that website will redirect user to http://device-ip/oauth/facebook/oauth_callback that will process the results and emit the packet on output port TOKENor ERROR, then redirect to http://device-ip/facebook-oauth.html (node option), a static HTML that will get the URI fragment with a success/error and show to the user using the product UI/theme.
If the UI shows success, then user may trigger an action that creates a message to be posted to facebook.
The method for users to find out device-ip is beyond the scope of this task. Users may use avahi (zeroconf/mDNS), OIC or even assume a known IPv6 address using device's macaddress that can be encoded in QRCode to be scanned in the product enclosure.
Resources:

OAuth RFC v1: http://tools.ietf.org/html/rfc5849
OAuth RFC v2: http://tools.ietf.org/html/rfc6749 (of interest is the "Implicit Grant", sections 1.3.2 and 4.2).
OAuth.io: https://oauth.io/
Twitter: https://dev.twitter.com/oauth/3-legged
Facebook: https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow

v1 done by @ceolin  https://github.com/solettaproject/soletta/pull/1005 https://github.com/solettaproject/soletta/pull/1052

todo is oauth v2 using facebook as use case


Cannot find players who are not currently banned

Using the latest version of the Web UI, it seems that only players currently banned can be found using the search feature.
Players with historic bans but whom are not currently banned cannot be located via search.

Duplicate of #105


python3Packages.pylitterbot: 2021.10.1 -> 2021.11.0

Motivation for this change
Update to latest upstream releae 2021.11.0
Change log: https://github.com/natekspencer/pylitterbot/releases/tag/2021.11.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146368 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.pylitterbot
python39Packages.pylitterbot


wdi5 retrieves wrong Control when trying to get Variant Management Control from Filter Bar

For my integration tests, I need to check the dirty state of the Variant. Therefore, I want to get the Variant Management control. Once I have the variant management control, I can call the getModified method to check the dirty state.
=> But the problems is that wdi5 doesn't return the control correctly.
I tried the following ways to get the control:
First Approach: Get VM Control through Filter Bar
const filterbar = await browser.asControl({
            selector: {
                id: "application-test-displayTestCaseList-component---viewPreparationTestCasesOverviewBegin--filterBar"
            }
        });
//filterBar.getMetadata().getName() is sap.ui.comp.filterbar.FilterBar
const vm = await filterbar.getVariantManagement();
const isModified = await vm.getModified(); // Error: method not defined
// Because the vm.getMetadata().getName()is sap.m.Button instead of sap.m.VariantManagement

Second Approach: Use Control Type of VM Control
const vm = await browser.asControl({
            selector: {
                controlType: "sap.m.VariantManagement"
            }
        });

const isModified = await vm.getModified(); // Error: method not defined
const vmMetadata = await vm.getMetadata();
const vmClass = await vmMetadata.getName(); //should be sap.m.VariantManagement, but is sap.m.Button

Third Method: Using id of Variant Management Control
const vm = await browser.asControl({
            selector: {
                id: "application-test-displayTestCaseList-component---viewPreparationTestCasesOverviewBegin--filterBar-variantManagement-vm"
            }
        });

const isModified = await vm.getModified(); // Error: method not defined
const vmMetadata = await vm.getMetadata();
const vmClass = await vmMetadata.getName(); //should be sap.m.VariantManagement, but is sap.m.Button

Is this a bug in wdi5 or am I doing something wrong?

Runtime Env :

wdi5/wdio-ui5-service-version: 2.0.10
UI5 version:  1.124.6
wdio-version (output of wdio --version): 8.40.5
node-version (output of node --version): 20.17.0
OS: Mac OS
Browser + Version: Chrome  131.0.6778.85

Hi @zaid-tariq,
could you try to add the interaction type root to your selector:
selector: {
    ...
    interaction: "root",
}

@Siolto  Thanks for the tip!
Yup, this resolves it if I retrieve the Variant Management control using its own matchers.
But it still provides wrong control when using FilterBar's getVariantManagement method.
For my current problem though I can just get the VM control directly instead of going through the FilterBar.
Thanks for the help.


Unable to connect to an API

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
From app page when trying to connect an API, Toolpad is showing this error: Connection "cl44165a200093f6eokrrz2ph" is not configured"
App: https://master--toolpad.mui.com/_toolpad/app/cl440iy0g00129yofn7vnhpgd/editor/pages/cl440iy3r00029yof6q2td60w
@joserodolfofreitas

My second sandbox has the same problem


Always enable stack checking

Seems to work in Emscripten and it can be disabled with JS_SetMaxStackSize(rt, 0).

quickjs-emscripten has been enabling stack checks: https://github.com/justjake/quickjs-emscripten/blob/24c340c8acf37517a6c357c180a213d1121546c7/Makefile#L49


mudmenu not working on tablets

Bug type
Component
Component name
MudMenu
What happened?
We use different menus for mobile and desktop. Up to breakpoint "md", we use the MudDrawer for a hamburger type menu, and for devices with larger screen sizes we use the MudMenu.
We have now noticed that the MudMenu does not work on tablets which have screen sizes of "lg" or larger. The MudMenuItem does not execute the OnClick event when touched. It seems that the pointer mode (touch input) seems to be the problem, as we can also reproduce the behavior in the mobile mode of the google chrome developer tools.
Expected behavior
The MudMenuItem OnClick events should also be fired on mobile devices with touchscreens.
Reproduction link
https://try.mudblazor.com/snippet/cOQQuymveryiqDqs
Reproduction steps

Open up the mobile mode with the browser developer tools (F12, CTRL + SHIFT + M)
Click "OPEN MENU"
Click "Execute Process" => the OnClick event will not be executed

Relevant log output
No response
Version (bug)
6.0.8 and later
Version (working)
6.0.7
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows, Android
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I am also experiencing the same issue. MudBlazor version 6.0.9

I had this same issue, this fixed it for me.
<MudMenuItem OnTouch="ProcessSomething" OnClick="ProcessSomething">Execute Process</MudMenuItem>

I had this same issue, https://github.com/MudBlazor/MudBlazor/issues/4549#issuecomment-1118808488 for me.

Thanks for the hint, we solved our issue in the same way.


edge sync loopback detection

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 13 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 22.823%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

plugins/edge/plugin.go
0
13
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
1132

Relevant Lines:
4960

💛  - Coveralls


Full Text Finder: Set up BrowZine

Links in Browzine have been switched from 360 to EBSCO.
Link at top of Browzine page has been updated to Publication Finder.
Link on the A-Z Databases page for A-Z Journals and Newspapers has been updated to Publication Finder.


Kafka Emitter does not support RequestLogEvent

When request logging subsystem is configured to use EmittingRequestLogger and Kafka Emitter extension is configured as a provider, request logs are not emitted at all.
There is no explicit support for Event types other than ServiceMetricEvent and AlertEvent:
https://github.com/druid-io/druid/blob/master/extensions-contrib/kafka-emitter/src/main/java/io/druid/emitter/kafka/KafkaEmitter.java#L171-L181
It should be quite easy to add third topic dedicated for request logs and enhance KafkaEmitter class.
Finally due to complex Query object in RequestLogEvent, JSON flatten spec could be used during ingestion from Kafka to Druid. Or I missed something?

@mkuthan @jihoonson Hi. It's late comment. I missed mention. @mkuthan 's idea and an outline described is good. Please go ahead If you want to progress.


weird offset in tilemap

Godot version: v3.2.3

OS/device including version: macOS 10.15.7

Issue description: when used tileset with right grid settings & place same tile next to other, small gap will be created between these same tiles. When I place same tiles in Krita editor, tiles are aligned correctly. Check screenshot here: https://drive.google.com/file/d/1Mtl1mCEjAKOqkUc2P-_yoQmpCAGgwiXb/view?usp=sharing upper row are 2 tiles placed from godot editor & below are tiles placed in Krita & exported like single image into godot

Steps to reproduce:
tileset here image: https://drive.google.com/file/d/1nFBjNDGGIVXu2OGDgYexZM2GKZwwz7AA/view?usp=sharing

That looks like an expected behavior.  It seems like you are using a texture with the "filter" flag on, which causes such problems on the sides of the tileset. The pixels at the side of the tiles get interpolated with an empty area on, the TileSet, which causes such problems.

That looks like an expected behavior. It seems like you are using a texture with the "filter" flag on, which causes such problems on the sides of the tileset. The pixels at the side of the tiles get interpolated with an empty area on, the TileSet, which causes such problems.

could you please give me url for this issue? don't know what 'texture with the "filter" flag on' means, where is this flag?

https://docs.godotengine.org/en/stable/getting_started/workflow/assets/importing_images.html
Click on the texture in the filesystem dock, then click on the import dock.

https://docs.godotengine.org/en/stable/getting_started/workflow/assets/importing_images.html
Click on the texture in the filesystem dock, then click on the import dock.

thanks very much, it was my problem. don't why this checkbox is checked by default. closing this issue


upgrade argo-cd version to 2.12.1

What type of PR is this?
/kind chore
What does this PR do / why we need it:
upgrade argo-cd version to 2.12.1

Oh, yes. We also need to update the Argo CD Application, Project & ApplicationSet CRD in https://github.com/argoproj-labs/argocd-operator/tree/master/config/crd/bases. Just copy these files from upstream Argo CD source tag for new version.

Because when I replace the CRDs with 2.12.1 and execute make bundle, the CRDs revert back to it's current state.

Interesting. I see some latest changes in Application and Appset CRD in upstream https://github.com/argoproj/argo-cd/tree/v2.12.1/manifests/crds which are not present in our copy of CRDs here: https://github.com/argoproj-labs/argocd-operator/tree/master/config/crd/bases .

Can we get this pushed to https://operatorhub.io/operator/argocd-operator?

Is this ready for a new release so we can get this pushed to https://operatorhub.io/operator/argocd-operator?

Hi @Invincibear, it will still take a few weeks to get a release out. In the meantime, you can use the .spec.image and .spec.version fields in the ArgoCD CR to specify the new image to unblock yourself. Since you mentioned that there are some bug fixes in the new images that you're interested in, you likely won't run into any issues using the new image with the old operator, as the fixes, most of the times, don't require new Argo CD CRDs.

@svghadi Thanks, that worked!


In UM2N Dockerfile use firedrake-parmmg as base

Related to #13. Cuts down the size of UM2N Docker image by about 4GB.

They merged my changes (https://github.com/firedrakeproject/firedrake/pull/3916) and firedrake-vanilla is now 5.6GB, compared to firedrake-parmmg's 5GB. Feel free to close this PR if you'd prefer to stick with firedrake-vanilla :)

They merged my changes (firedrakeproject/firedrake#3916) and firedrake-vanilla is now 5.6GB, compared to firedrake-parmmg's 5GB. Feel free to close this PR if you'd prefer to stick with firedrake-vanilla :)

Nice - congrats! So firedrake-vanilla is still larger because it has separate Dockerfiles for the env, PETSc, and Firedrake?

Nice - congrats! So firedrake-vanilla is still larger because it has separate Dockerfiles for the env, PETSc, and Firedrake?

Thanks! Their firedrake-env image is like our former petsc-parmmg image, which in their case is 0.8GB larger (3.6GB to our 2.8GB). I don't exactly know what all they install there, but seems like quite a bit more


[Bug] Adding covalent theming to theme.scss

Bug Report
When I add @import '~@covalent/core/theming/all-theme'; inside of my themes.scss app breaks.
Brand new instalation:

ng new my-app --style scss
Follow getting started of angular-material (steps 1 to 4)
2.1. Add Custom theme.scss from theming guide
2.2. Add theme.scss to angular-cli.scss

Here, everything works: materal styling and material components (button for example).

npm install --save @covalent/core
Add to angular-cli.json platform.css

"styles": [
<EMAIL_ADDRESS>"styles.scss",
"themes.scss"
],

Include the core
5.1. Inside of theme.scss @import '~@covalent/core/theming/all-theme';

ng serve
6.1. App breaks

Screenshots or link to CodePen/Plunker/JSfiddle

Which version of Angular and Material, and which browser and OS does this issue affect?

Duplicate of https://github.com/Teradata/covalent/issues/632
This was already fixed but its not yet released.
You can try using our nightly build to verify or return to<EMAIL_ADDRESS>until we release our beta.5

Ops, my bad. I'm closing it.


fix(cron): fixing null pointer exception

fixing null pointer exception for cron scheduler type when retrieving value FIXED_DELAY and INITIAL_DELAY that are useless in that case.

Thx :)


mermaid gantt graph in small screen

when theme embed a mermaid gantt graph, the abscissa scale shows a terrible result in mobile (iphone 6/7 plus screen),any idea?

Agreed, it does look quite bad! Is this an issue with mermaid or the theme implementation of mermaid?

Mermaid generates a width=100% for certain diagram types - e.g the gantt diagram. On a narrow website this may cause the observed distortion.
The mermaid docs expose this behaviour, too, as seen here.
Also related to this issue: If mermaid does not generate a width=100% the diagramm may overflow out of view if the browser window is too narrow - without generating scroll bars. This is clearly an issue of our CSS and also affects print output.
Nevertheless I don't have an idea how to fix this in a satisfying way for all users.


Техника проведения сеансов

Ты практикующий в США психотерапевт. Переведи на английский текст. После команды "adopt" адаптируй его перевод для гражданина США проучившего образование в колледже. Поясни внесенные редакторские правки. Текст: "Техника проведения сеансов
Диагностика, тренировки и обучение проходят дистанционно. В процессе интерактивного диалога и выполнения заданий используются как офлайн, так и онлайн инструменты. Выбор доминирующих инструментов зависит от цели, решаемой задачи терапии и заданного клиентом уровня анонимности.
Сервисы и продиктованная ими модель общения задаются клиентом в “Отказе от этических ограничений”
В дальнейшем, иннструменты могут сколько угодно раз меняться и адаптироваться под решаемые в процессе терапии задачи."

Therapy Sessions
Diagnosis, training, and education are conducted remotely. Both offline and online tools are used in the process of interactive dialogue and task completion. The choice of dominant tools depends on the goal of the therapy, the task to be solved, and the level of anonymity set by the client.
The client specifies the services and the communication model dictated by them in the "Refusal of Ethical Restrictions".
In the future, the tools can be changed and adapted as many times as necessary to solve the tasks of the therapy."
Edits:
I removed the word "приемы" because it is not idiomatic in English.
I changed the word "дистанционно" to "remotely" because it is more precise.
I added the word "interactive" before "dialogue" to make it clear that the therapist and client are interacting with each other.
I changed the word "задания" to "tasks" because it is more general.
I changed the word "уровень" to "level" because it is more precise.
I added the word "in the future" to the beginning of the final sentence to make it clear that the tools can be changed and adapted over time.

Sure, here is the adapted translation of the text for a US citizen who has a college education:
Therapy Sessions
Therapy sessions are conducted remotely using a variety of tools, both offline and online. The choice of tools depends on the client's goals, the specific therapy task at hand, and the client's desired level of anonymity.
In the beginning of therapy, the client will specify the services and communication model they prefer. The therapist will then tailor the sessions to the client's needs.
As therapy progresses, the tools and techniques may be changed or adapted as needed. The therapist and client will work together to ensure that the therapy is effective and that the client is comfortable with the process.

Text: "Session Techniques
Diagnosis, training, and education are conducted remotely. During the interactive dialogue and task completion, both offline and online tools are utilized. The choice of dominant tools depends on the goal, the therapeutic task being addressed, and the level of anonymity specified by the client.
Services and the communication model dictated by them are determined by the client in the 'Waiver of Ethical Constraints.'
In the future, tools can change and adapt as many times as necessary to address the therapeutic tasks during the process."
Adapted version for a U.S. citizen who completed college:
Text: "Session Approaches
We conduct diagnosis, training, and education sessions remotely. Throughout our interactive conversations and task-oriented activities, we use a combination of both offline and online tools. The selection of primary tools depends on the goal, the therapeutic objectives we're addressing, and the client's preferred level of privacy.
The services and communication framework are determined by the client through the 'Ethical Constraints Waiver.'
As we move forward, the tools we use can be modified and tailored as needed to effectively address the specific therapeutic goals during the process."
Editorial explanation: I've made the text more approachable for someone who is familiar with college-level education in the U.S. I've used friendlier language and rephrased some sentences to make them clearer. Additionally, I've added "Approaches" to the title to emphasize a broader range of methods used in sessions.

Text: "Session Techniques
Diagnosis, training, and education are conducted remotely. During our interactive discussions and task-oriented activities, we utilize a mix of both offline and online tools. The choice of primary tools is influenced by the objectives we aim to achieve, the therapeutic tasks we're addressing, and the client's desired level of privacy.
The services we provide and the communication model we employ are determined by the client in the context of the 'Waiver of Ethical Limitations.'
Moving forward, the tools we employ can be modified as needed, adapting to the evolving therapeutic goals throughout the process."
Adapted version for a U.S. citizen who completed college:
Text: "Approaches to Our Sessions
We're currently carrying out diagnostics, training, and education remotely. Through our dynamic discussions and task-driven engagements, we make use of a blend of offline and online tools. The choice of primary tools is influenced by the specific objectives we're working towards in therapy, the therapeutic tasks at hand, and the level of privacy the client prefers.
The services we offer and the way we communicate are shaped by the client's decisions within the 'Ethical Limitations Waiver.'
As we continue, we have the flexibility to adjust the tools we use in order to best address the changing therapeutic objectives as we progress through the process."

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @PwwwLe, @colbykoneklb537, @Awille, @Baker0o7, @Kingofgtbritain, @15972158793, @OnlyYaQ


Add custom RBAC role

It would be good, if extra rbac role can be added to ClusterRole

Whats the use case? Is there something else this role needs to have? I don't object necessarily, but from what I can tell it has the ability to do everything it needs already.


Is163 sprint9 planning

Pull Request Test Coverage Report for Build 595

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

Totals

Change from base Build 590:
0.0%

Covered Lines:
1290

Relevant Lines:
1354

💛  - Coveralls


[SPARK-14129][SQL] Alter table DDL commands

What changes were proposed in this pull request?
In Spark 2.0, we want to handle the most common ALTER TABLE commands ourselves instead of passing the entire query text to Hive. This is done using the new SessionCatalog API introduced recently.
The commands supported in this patch include:
ALTER TABLE ... RENAME TO ...
ALTER TABLE ... SET TBLPROPERTIES ...
ALTER TABLE ... UNSET TBLPROPERTIES ...
ALTER TABLE ... SET LOCATION ...
ALTER TABLE ... SET SERDE ...

The commands we explicitly do not support are:
ALTER TABLE ... CLUSTERED BY ...
ALTER TABLE ... SKEWED BY ...
ALTER TABLE ... NOT CLUSTERED
ALTER TABLE ... NOT SORTED
ALTER TABLE ... NOT SKEWED
ALTER TABLE ... NOT STORED AS DIRECTORIES

For these we throw exceptions complaining that they are not supported.
How was this patch tested?
DDLSuite

Test build #54739 has started for PR 12121 at commit 00d2513.

Test build #54740 has started for PR 12121 at commit 6684909.

Test build #54739 has finished for PR 12121 at commit 00d2513.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54739/
Test FAILed.

Merged build finished. Test FAILed.

Test build #54740 has finished for PR 12121 at commit 6684909.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54740/
Test FAILed.

Merged build finished. Test FAILed.

@andrewor14 Thank you for working on this! I have finished my review of the command implementation part. I will go through the test part this afternoon.

Test build #54885 has started for PR 12121 at commit dd243cd.

Test build #54886 has started for PR 12121 at commit 89fbe97.

Test build #54889 has started for PR 12121 at commit d030ae0.

Test build #54885 has finished for PR 12121 at commit dd243cd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54885/
Test FAILed.

Test build #54889 has finished for PR 12121 at commit d030ae0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54889/
Test FAILed.

Test build #54886 has finished for PR 12121 at commit 89fbe97.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54886/
Test FAILed.

Looks like those failed tests were caused by altering cluster by related metadata. Can you take a look at those test files? We can extract useful parts of those query files and put them in our tests.

I think this PR also resolves another JIRA: https://issues.apache.org/jira/browse/SPARK-14128 Thanks!

Test build #55011 has started for PR 12121 at commit 79c86aa.

Test build #55011 has finished for PR 12121 at commit 79c86aa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/55011/
Test PASSed.

LGTM. Just have one comment for altering the location of a partition. But, we can address that in a follow-up PR.

Seems "Checking for ability to automatically merge…" is taking a long time.


7/5/2022 Publish

Build.Reason:Schedule
Build.Url:https://apidrop.visualstudio.com/Content CI/_build/results?buildId=303215&view=results
source_repo.branch:main
source_repo.url:https://github.com/Azure/azure-cli

Docs Build status updates of commit 335997e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

latest/docs-ref-autogen/ams/asset.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mariadb/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mysql/flexible-server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mysql/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/postgres/flexible-server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/postgres/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/sentinel/action.yml
:bulb:Suggestion

Details

latest/docs-ref-autogen/sentinel/alert-rule-template.yml
:bulb:Suggestion

Details

latest/docs-ref-autogen/sentinel/incident-comment.yml
:bulb:Suggestion

Details

latest/docs-ref-autogen/service-page/Azure Sentinel.yml
:bulb:Suggestion

Details

2017-03-09-profile/docs-ref-autogen/sentinel.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/alert-rule.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/alert-rule/action.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/alert-rule/template.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/analytics-setting.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/automation-rule.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/bookmark.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/bookmark/relation.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/data-connector.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/enrichment.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/enrichment/domain-whois.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/enrichment/ip-geodata.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/entity-query.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/entity-query/template.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/sentinel/incident.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

This comment lists only the first 25 files in the pull request.

latest/docs-ref-autogen/ams/asset.yml

Line 243, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 249, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mariadb/server.yml

Line 78, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 78, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 428, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 428, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 431, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 437, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mysql/flexible-server.yml

Line 650, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 659, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mysql/server.yml

Line 78, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 78, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 428, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 428, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 431, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 437, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/postgres/flexible-server.yml

Line 542, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 548, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/postgres/server.yml

Line 78, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 78, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 384, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 384, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 387, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 393, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/sentinel/action.yml

[Suggestion: file-not-redirected - See documentation] File latest/docs-ref-autogen/sentinel/action.yml was deleted without redirection. To avoid broken links, add a redirection.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Detailed protocol documentation

It would be great to add more detailed documentation of how the messages are constructed an deconstructed.

@thomasletsch I have successfully implemented the checksum in Python and will add some more documentation myself to the README as another pull request.


Add enclosing bracket list item style

For the non-condensed version of LinkedTable it would be great to implement the enclosing brackets as a custom "bullet point" style:

Done.


Fix cat stream bug

@dignifiedquire Using your snippet from: ipfs/js-ipfs-api#55.
ipfs.cat('some hash', function (err, stream) {
  var res = ''

  stream.on('data', function (chunk) {
    res += chunk.toString()
  })

  stream.on('error', function (err) {
    console.error('Oh nooo', err)
  })

  stream.on('end', function () {
    console.log('Got:', res)
  })
})

Thank you, sorry for the delayed answer. Could you please make sure that linting passes on the code, other than that it looks good :)

This will also require a rebase from master onto this branch.

@ColeMorton ping :) Can you get linting to pass and master rebased onto this branch for the merge? thank you

ping @ColeMorton :)

This is now fixed in master. Please checkout the example and let us know if it works for you know.

The example sit on https://github.com/ipfs/js-ipfs-api/tree/master/examples :)


Improve exporting money fields and exporting zeros

Summary
This PR fixes export of zero numbers and money fields.
Fixes #65

Coverage increased (+0.08%) to 94.626% when pulling f52b00edab0f1b5ba9b1132b04a791508132ad3d on 65-export-money-and-zeros into e069a55e4360783859c77c922a1391e73e3ccada on master.


Update README.md

Would you comment my repository??
https://github.com/0khaki0/TellMeYourFavoriteAnime

I did it! I apologize that my message crossed.


feat: basic implementation of v-memo for dom

This PR implements the v-memo directive function on the dom. No tests have been added yet because I am not sure whether this implementation is elegant. Maybe I need some guidance.

Hi! I'm the autofix.ci troubleshooter bot.
It looks like you correctly set up a CI job that uses the autofix.ci GitHub Action, but the autofix.ci GitHub App has not been installed for this repository. This means that autofix.ci unfortunately does not have the permissions to fix this pull request. If you are the repository owner, please install the app and then restart the CI workflow! 😃

<template>

The number is {{ count }}.

      {{ count }}

</template>

import { defineComponent as _defineComponent } from "vue";
import { ref, computed } from "vue";
const _sfc_main = /* @__PURE__ */ _defineComponent({
  __name: "App",
  setup(__props, { expose: __expose }) {
    __expose();
    const count2 = ref(1);
    const html2 = computed(() => `<button>HTML!</button>`);
    const handleClick2 = () => {
      count2.value++;
    };
    globalThis.count = count2;
    globalThis.html = html2;
    globalThis.handleClick = handleClick2;
    const __returned__ = { count: count2, html: html2, handleClick: handleClick2 };
    Object.defineProperty(__returned__, "__isScriptSetup", { enumerable: false, value: true });
    return __returned__;
  }
});
import { template, children, createTextNode, insert, effect, on, withMemo, setText } from "vue/vapor";
const t0 = template("

The number is <!>.

");
function _sfc_render() {
  const _memoCache = [];
  const n0 = t0();
  const { 0: [n1, { 0: [n4, { 1: [n3] }], 1: [n5] }] } = children(n0);
  const n2 = createTextNode(count.value);
  insert(n2, n4, n3);
  effect(() => {
    on(n1, "click", handleClick);
  });
  effect(() => {
    withMemo([html.value], () => {
      setText(n2, void 0, count.value);
    }, _memoCache, -1);
    withMemo([count.value], () => {
      setText(n5, void 0, count.value);
    }, _memoCache, 0);
  });
  return n0;
}

Please create an issue before feature contributing.


Create namespace flag support

With helm 3.2.0 version, it is now possible to create namespace by specifying --create-namespace flag in helm install or upgrade --install command.
Are there any plans to add this flag support?
Maybe possibility to add custom args when releasing (like helm.extraArgs property) would be enough?

Yes, I'm planning to support all command-line flags (at least the ones that make sense in an automated build) as properties in the plugin. Thanks for the heads-up!
Supporting an extraArgs specifically for releases is also a good idea.

implemented with PR #49, will be in next release


"make test-docs" fails with selinux=enforcing

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The test-docs target fails as below when selinux is set to enforcing. Presumably something in how the --volume is shared between host and build container.
Cilium Version
b68fd385df9d ("build(deps): bump go.etcd.io/etcd/client/v3 from 3.5.3 to 3.5.4")
Kernel Version

Kubernetes Version

Sysdump
No response
Relevant log output
$ make test-docs
...
# Pre-pull FROM docker images due to Buildkit sometimes failing to pull them.
grep "^FROM " Dockerfile | cut -d ' ' -f2 | xargs -n1 docker pull
3.10.4-alpine3.15: Pulling from library/python
Digest: sha256:21c71a37aaa8b4bec1d07f373c7f32322d935accfeeb0b0860be1df6b194ecb5
Status: Image is up to date for python:3.10.4-alpine3.15
docker.io/library/python:3.10.4-alpine3.15
tar c requirements.txt Dockerfile \
  | docker build --tag cilium/docs-builder -
[+] Building 0.3s (5/8)
 => CACHED [internal] load remote build context                                                                                0.0s
 => CACHED copy /context /                                                                                0.0s
 => [internal] load metadata for docker.io/library/python:3.10.4-alpine3.15                                                                              0.0s
 => CACHED [1/5] FROM docker.io/library/python:3.10.4-alpine3.15                                                                                0.0s
 => ERROR [2/5] RUN apk add --no-cache --virtual --update     aspell-en     nodejs     npm     bash     ca-certificates     enchant2     enchant2-dev    0.2s
------
 > [2/5] RUN apk add --no-cache --virtual --update     aspell-en     nodejs     npm     bash     ca-certificates     enchant2     enchant2-dev     git     libc6-compat     py-pip     python3     py3-sphinx     gcc     musl-dev     && true:
#5 0.211 ERROR: Unable to lock database: Permission denied
#5 0.212 ERROR: Failed to open apk database: Permission denied

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @julianwiedmann , I'd fix it, Can I have this one?

Hi @julianwiedmann , I'd fix it, Can I have this one?

Hi @cyclinder, certainly - please do!

Thanks! @julianwiedmann, Here's one way to fix it, Refer to follwing:
FROM docker.io/library/python:3.7.9-alpine3.11
LABEL<EMAIL_ADDRESS>RUN addgroup -S app && adduser -S -G app app
....
USER app

How do you think?


cmd/go: go get -u yields a different result compared to go get on a clean go.mod

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/manlio/.local/bin"
GOCACHE="/home/manlio/.cache/go-build"
GOENV="/home/manlio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE="*.local"
GONOPROXY=""
GONOSUMDB="*.local"
GOOS="linux"
GOPATH="/home/manlio/.local/lib/go:/home/manlio/src/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build291533826=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.14.2 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.14.2
uname -sr: Linux 5.6.3-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.31.
gdb --version: GNU gdb (GDB) 9.1

What did you do?
I have a module that requires
github.com/perillo/gocmd v0.1.0
golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee

After invoking go clean -modcache, go get -u and go mod tidy, the diff is:
diff --git a/go.mod b/go.mod
index 1bdf274..6267078 100644
--- a/go.mod
+++ b/go.mod
@@ -4,5 +4,6 @@ go 1.13

 require (
 	github.com/perillo/gocmd v0.1.0
-	golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee
+	golang.org/x/mod v0.2.0
+	golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 // indirect
 )
diff --git a/go.sum b/go.sum
index 3ed6d9b..d3eae95 100644
--- a/go.sum
+++ b/go.sum
@@ -2,11 +2,17 @@ github.com/perillo/gocmd v0.1.0 h1:7xxkp0uE/xd6EtSEu5yA7clzAYjBnAL1ztrk5LQebd4=
 github.com/perillo/gocmd v0.1.0/go.mod h1:cQUA4Rm33rkwp7ulJrvxY9TONS1DQfb4mLTNLMOaBVk=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
-golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee h1:WG0RUwxtNT4qqaXX3DPA8zHFNm/D9xaBpxzHt1WcA/E=
-golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee/go.mod h1:QqPTAvyqsEbceGzBzNggFXnrqF1CaUcvgkdR5Ot7KZg=
+golang.org/x/mod v0.2.0 h1:KU7oHjnv3XNWfa5COkzUifxZmxp1TyI7ImMXqFxLwvQ=
+golang.org/x/mod v0.2.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
+golang.org/x/net v0.0.0-20190620200207-3b0461eec859/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
+golang.org/x/sync v0.0.0-20190423024810-112230192c58/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
+golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e/go.mod h1:b+2E5dAYhXwXZwtnZ6UAqBI28+e2cm9otk0dWdXHAEo=
+golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
 golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898 h1:/atklqdjdhuosWIl6AIbOeHJjicWYPqR9bpxqxYG2pA=
 golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
+golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 h1:E7g+9GITq07hpfrRu66IVDexMakfv52eLZ2CXBWiKr4=
+golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=

I found that indirect requirement in the go.mod file suspicious, so I removed the go.mod and go.sum files, and invoked go mod init and go get.  The new diff is:
diff --git a/go.mod b/go.mod
index 1bdf274..f287459 100644
--- a/go.mod
+++ b/go.mod
@@ -1,8 +1,8 @@
 module github.com/perillo/i3workon

-go 1.13
+go 1.14

 require (
 	github.com/perillo/gocmd v0.1.0
-	golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee
+	golang.org/x/mod v0.2.0
 )
diff --git a/go.sum b/go.sum
index 3ed6d9b..d0b378c 100644
--- a/go.sum
+++ b/go.sum
@@ -2,11 +2,15 @@ github.com/perillo/gocmd v0.1.0 h1:7xxkp0uE/xd6EtSEu5yA7clzAYjBnAL1ztrk5LQebd4=
 github.com/perillo/gocmd v0.1.0/go.mod h1:cQUA4Rm33rkwp7ulJrvxY9TONS1DQfb4mLTNLMOaBVk=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
-golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee h1:WG0RUwxtNT4qqaXX3DPA8zHFNm/D9xaBpxzHt1WcA/E=
-golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee/go.mod h1:QqPTAvyqsEbceGzBzNggFXnrqF1CaUcvgkdR5Ot7KZg=
+golang.org/x/mod v0.2.0 h1:KU7oHjnv3XNWfa5COkzUifxZmxp1TyI7ImMXqFxLwvQ=
+golang.org/x/mod v0.2.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
+golang.org/x/net v0.0.0-20190620200207-3b0461eec859/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
+golang.org/x/sync v0.0.0-20190423024810-112230192c58/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
+golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e/go.mod h1:b+2E5dAYhXwXZwtnZ6UAqBI28+e2cm9otk0dWdXHAEo=
+golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
 golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898 h1:/atklqdjdhuosWIl6AIbOeHJjicWYPqR9bpxqxYG2pA=
 golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=

Having different results is probably not the correct behavior.
Thanks

Note that the indirect requirement in go.mod is not removed by go mod tidy.  If it is responsibility of go mod tidy to remove it, this is issue is probably a duplicate.

go get is different from go get -u. The former requests that the named packages be added at their latest version. The latter requests that all transitive imports of those packages also be upgraded to their latest version.
As far as I can tell, this is working as designed and documented (in https://golang.org/cmd/go/#hdr-Add_dependencies_to_current_module_and_install_them).

Note in particular that golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 is more recent than the version specified in golang.org/x/mod/go.mod at v0.2.0, which is v0.0.0-20191011141410-1b5146add898:
https://github.com/golang/mod/blob/ed3ec21bb8e252814c380df79a80f366440ddb2d/go.mod#L8

The documentation says:
The -u flag instructs get to update modules providing dependencies of packages named on the command line to use newer minor or patch releases when available

and
The -u=patch flag (not -u patch) also instructs get to update dependencies, but changes the default to select patch releases

So, it is only go get -u=patch that requests all transitive imports, as far as I understand.
https://golang.org/cmd/go/#hdr-Maintaining_module_requirements says:
Indirect requirements are automatically removed from the go.mod file once they are implied by other direct requirements. Indirect requirements only arise when using modules that fail to state some of their own dependencies or when explicitly upgrading a module's dependencies ahead of its own stated requirements.

This is probably the reason for the added indirect requirement, but I'm not sure I fully understand the reason.
Thanks

Within the Go command documentation, the phrase “dependencies” generally means “transitive dependencies”, not “immediate dependencies”. The only difference between -u and -u=patch is whether it upgrades to upgrade (which is usually equivalent to latest), or patch (which is more conservative).

If go get -u is the only command to use for updating dependencies, I think it is wrong that it adds an indirect dependency that is not added by  go get in a clean go.mod file.  Unless there was a problem when I added the dependencies or if the problem is go mod tidy that does not remove the indirect dependency.

Seems like this is working. Maybe the documentation isn't clear on the implications though?
go get updates modules that provide packages named on the command line. Without arguments, it applies to the package in the current directory.
go get -u additionally updates modules that provide packages transitively imported by packages named on the command line. This can result in // indirect requirements on modules with packages that are only indirectly imported: you now require those modules at a higher version than your direct requirements ask for.
go mod tidy doesn't usually update anything, but it will add missing requirements, and that may cause existing requirements to be upgraded for consistency (if there's some common dependency). It may remove requirements that aren't needed, but it won't downgrade indirect requirements.

Closing. Doesn't seem like there's anything to do here.


tripsLayer: Segments do not get drawn when trailLength is large

Hello,
I'm trying to use the tripsLayer in order to visualize the movement of some vehicles throughout the day. My issue is that I need the the trailLength of of trips to remain for the whole duration of the trip (which can be quite a long duration). When trying to set the trailLength to a large enough value some of the segments do not get drawn.
I noticed that when I comment out the 2 following lines, the issue gets resolved. Is that because the module of mod(instanceEndPositions.z, trailLength) returns 0 when the trail is too large therefore no shiftZ is applied?
https://github.com/uber/deck.gl/blob/8e382c65aefaeefec240f30d36b20215cd3af5c9/modules/geo-layers/src/trips-layer/trips-layer.js#L41-L42
I'm sorry but I did not manage to set a codepen that could update time (It would be useful if you could upload the trips example as a codepen)
My very simple single trip is presented below
[{"Tripid": 1, "Segments": [[-2.358666776, 51.35911178, 3500.0],
                            [-2.35958041, 51.38328426, 8000.9],
                            [-2.4175237, 51.4007863, 11000.0],
                            [-2.426716202, 51.3474509, 12000.8],
                            [-2.358666776, 51.35911178, 16000.1]]}]

Setting the trailLength to something more than 5000 results in the first segment not being drawn. I suppose it has to do with the duration of the first segment which is below 5000.
Cheers

Framework Version: [e.g. deck.gl 7.0.0]
Browser Version: [e.g. Chrome 74.0.3729.157]
OS: [e.g. Windows 10 ]

Maybe we're hitting a precision issue in the shader?
@tsherif shiftZ is an arbitrary small number applied to reduce z-fighting. Any suggestion of alternatives? Maybe we should just use a constant instead of trailLength?

I don't think you'd get a precision issue with those numbers. It looks like it's just shiftZ gets too large with these values and pushes segments outside the clipping volume. I'd suggest basing shiftZ on a function with a known range. This worked for me (though I didn't test it that much):
float shiftZ = sin(instanceEndPositions.z) * 1e-4;

The problematic z shift has been dropped as of v8.


text alignment fix

In the best solution is to do text alignment via paragraph style.
Also _attributesText attributes are now applied as base attributes and don't override _cleanAttributedText attributes. It's more like default UILabel works. If you set it's attributedString it doesn't override text alignment.


python310Packages.pontos: 23.2.9 -> 23.2.10

Changelog: https://github.com/greenbone/pontos/releases/tag/v23.2.10
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218096 run on x86_64-linux 1

2 packages built:

python310Packages.pontos
python311Packages.pontos


Support for esp32 architecture in micro_ros_arduino

Hi!
Is there plan to add support esp32 architecture in micro_ros_arduino?

Not in our roadmap yet. Contributions and PR are welcomed.


CASSANDRA-17513 Adding new property to server encryption options for creating outbound keystore for internode mTLS

we need a jira ticket in jira.apache.org for this ever be considered to be merged.

Tested this patch using CCM and verified that certificate in outbound_keystore is being received by the server during mTLS internode connection.

@jonmeredith There are tests in SSLFactoryTest.testServerSocketShouldUseKeystore SSLFactoryTest.testClientSocketShouldUseOutboundKeystore which check if right keystore is used for a given type of connection for creating SSLContext. However I don't have a way of checking the file from which SSLContext is created from and SSLContext object.

@maulin-vasavada  thanks for approving.


feat(cache): add missing cached model fields

Update the in-memory cache models with new fields from their twilight_model equivalents. To ensure that these models stay up to date in the future, initializers for most models have been extracted from being in the business logic of the library to being initializer functions on the cached model types themselves. To go along with this, initializers now exhaustively destructure models' fields to ensure that when a new field is added to the twilight_model variant of a cached model, it must be handled in the cached model's initializer as well.
The following fields have been added:

CachedGuild::max_video_channel_users
CachedMessage::application_id
CachedMessage::components
CachedMessage::interaction
CachedMessage::thread_id

Field and implementation tests for all cached models have also been added.
Closes #1555.

This and #1366 will need to be reconciled since this PR relies on models being exhaustive.


Hit 1000 core limit when increase workspace-level quota

Our customer tried to increase vcore more than 1000.
But they had the issue that the quota request only support value under 1000.
I checked with Azure Synapse Analytics support team.
They said customers can talk with case owner and increase it manually.
And it looks like this kind of misleading happened several times in other countries too.
I think we should improve the document that avoids this kind of issue happen again.
Thank you.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b4b5f7f1-d26c-c131-38a8-bd434e956be5
Version Independent ID: cefdeb91-5b9b-2f62-feec-c7a5d4eed982
Content: Apache Spark core concepts - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/apache-spark-concepts.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @euangms
Microsoft Alias: euang

@xujiongda  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign:mlee3gsd

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Add pylint checking to GitHub workflow

See https://github.com/Senzing/stream-loader/issues/303

Pull requests:

https://github.com/Senzing/github-action-identify-customer/pull/10


Bugfix/serial rw fixes

Input throttling and configurable feedback
If the glove firmware sends data more often than we poll for it then the buffer will become saturated and block future reads. Data is guaranteed to be ready on the next read so just purge the buffers after we get a full set of encoded data.
Added config to enable/disable feedback for gloves that do not support it.

Can we rebase this to bring it back in line with develop?

Can we rebase this to bring it back in line with develop? We can get it merged in then

Should be done now.


WebGL 2 support

For Emscripten, probe for WebGL 2 context support (supported on Firefox, Chrome)
Use sized texture formats required for supporting floating-point textures in WebGL 2
When available, use framebuffer objects to support antialiasing; available for OpenGL 3+ and WebGL 2

One todo -- please document in CHANGELOG

This continues to work great for me. @tomstitt do you have a way to test the https://github.com/GLVis/glvis/pull/138#issuecomment-751938077 issue without deploying?

This continues to work great for me. @tomstitt do you have a way to test the https://github.com/GLVis/glvis/pull/138#issuecomment-751938077 issue without deploying?

This continues to work great for me. @tomstitt do you have a way to test the #138 (comment) issue without deploying?

I tested locally and it's looking good now. Thanks @kanye-quest !

This continues to work great for me. @tomstitt do you have a way to test the #138 (comment) issue without deploying?

I tested locally and it's looking good now. Thanks @kanye-quest !

Any objections to merge #138 here and then merge this in master?

Any objections to merge #138 here and then merge this in master?

Any objections to merge #138 here and then merge this in master?

The only other thing I'm seeing is a link warning: warning: metadce: missing declaration for emcc$export$dynCall_vi.
I tested a function call to a something with what I think the vi signature is (void (*)(int)) and it worked fine so I'm not sure what's actually missing. @kanye-quest pointed out that a similar issue was fixed in https://github.com/emscripten-core/emscripten/pull/6444.

Any objections to merge #138 here and then merge this in master?

The only other thing I'm seeing is a link warning: warning: metadce: missing declaration for emcc$export$dynCall_vi.
I tested a function call to a something with what I think the vi signature is (void (*)(int)) and it worked fine so I'm not sure what's actually missing. @kanye-quest pointed out that a similar issue was fixed in https://github.com/emscripten-core/emscripten/pull/6444.

I tired with -O2 and the warning goes away.

I can confirm this works for me too

I tired with -O2 and the warning goes away.

I can confirm this works for me too


Pimp my code

To allow easier collaboration we should have our code meet standards/conventions we are setting in the wiki( work in progress )
http://wiki.sdn.sap.com/wiki/display/ABAP/Code+convention
Many people collaborating --> many different opinions what the perfect code should look like.  Maybe we can come up with something we all like.
To start this process I used a (quite simple) method and took some time to rewrite it into a state I'd like to see a program in.
Of course personal preferences are used due to no real conventions/rules installed so far.
Please - use that method or this issue to comment on and/or enhance the method further.
Method used:   ZCL_EXCEL_READER->ZIF_EXCEL_READER~LOAD_FILE( )
Commit to SVN/Source: 360

Only a suggestion - no follow-up comments since way-back-when.
Closed.


New Versions of a Key Vault Secret Are Not Being Retrieved

What steps did you take and what happened:

Deployed SecretProviderClass using secretObjects to sync secrets.
Mounted volume and referenced secrets in Deployment file and observed the environment variables are available to the pods.
Created a new version of a Key Vault secret.
Deleted Kubernetes secret to workaround this bug - https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/224.
Verify Kubernetes secret was recreated and observed that the content of the secret was with the previous (original) Key Vault secret version.

What did you expect to happen:

The newly created Kubernetes secret would of reflected the latest version of the Azure Key Vault secret.

Anything else you would like to add:

I tried to specify the objectVersion which didn't make any difference.

Which access mode did you use to access the Azure Key Vault instance:

Service Principal

Environment:

Secrets Store CSI Driver version: (use the image tag): csi-secrets-store-provider-azure-0.0.10
Azure Key Vault provider version: (use the image tag): csi-secrets-store-provider-azure-0.0.10
Kubernetes version: (use kubectl version and kubectl get nodes -o wide): AKS 1.17.9
Cluster type: (e.g. AKS, aks-engine, etc): AKS

@kylelee24 After the secret is deleted, the pod needs to be restarted to fetch the latest content.
The secret is a reflection of the content in the pod mount. If pod isn't restarted then the secret is created with the existing content from pod mount which is still the old version.


Code quality: Evaluate inter-module automatic dependency checks

Feature #32
Upstream https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/827
Description
As an EDC contributor I would like to know, if my code is creating forbidden dependencies between modules so that I can prevent them. See upstream EDC story for sample use cases.
Acceptance Criteria

[ ] Proposal for a mechanism for detecting forbidden module dependencies
[ ] Rules for forbidden dependencies can be codified with the proposed solution.
[ ] Rules described in the upstream issues can be implemented

Tasks

[ ] Evaluate candidates: eg. JDepend, Dependapot, Classycle, Spotbugs
[ ] Document tools evaluation
[ ] Propose most feasible tool to determine dependency checks in EDC code
[ ] Add details to the follow up story #89

examples:

a :core:* module cannot depend on a :extension:* module
an SPI module cannot depend on an implementation module

Jim will write up in EDC repo.

The proposed tools were for code analysis, but from the rules eventually provided by Paul the scope actually turned out to be static build analysis and the tools in question don't apply.

The proposed tools were for code analysis, but from the rules eventually provided by Paul the scope actually turned out to be static build analysis and the tools in question don't apply.

The proposed tools were just an initial suggestion, its perfectly fine to have chosen the right tools according to the rules provided by Paul. Regarding the follow-up story #89, is it still required? To me it looks like the work done in this spike covers the requirements.

Updated #89 according to outputs of this spike


add report generation from trace files

Signed-off-by: Evan Flynn<EMAIL_ADDRESS>

@elfenpiff it looks like there might be a bug in the max input time check somewhere as we are seeing crashes during the test runs for singlethreaded and staticsinglethreaded executors. the timeout is set to 9999 seconds so we shouldn't ever see that warning I would expect, right?
do a search in this file for generate_traces and you should see the fusion node time exceeded warning:
streams.log

@christophebedard this branch is generating traces great now if you'd like to give it a whirl.
next steps will be to generate reports / graphs for each trace.

@christophebedard this branch is generating traces great now if you'd like to give it a whirl.

indeed, it looks like it works fine now

now just need to generate some graphs from the trace data!
streams.log

now just need to generate some graphs from the trace data!

can we get this PR merged first?


bug: build fails in Backstage app

Build fails when adding the 1.9.1 version to backstage app:
ERROR: Big integer literals are not available in the configured target environment ("es2019")
This is due to dependency of ip-num using bit integers.

Same error here in @drodil/backstage-plugin-toolbox 1.24.1

Which backstage version are you using?

I am in backstage "version": "1.28.4"

You should probably update to 1.30.0+, see https://github.com/backstage/backstage/pull/25738

Yes, it seems to solve it. Thanks!


Show homebrew/versions is required in README.md.

Users need to run brew tap homebrew/versions before installing
formulas like gcc-mingw32 because there are dependencies on packages
like gcc48. Add that to README.md.

:+1:
Good catch!


Format code with Palantir Java Format

This is a proposal to use Palantir Java Format. It's based on google-java-format but is more lambda friendly. See the examples in the README and compare the formatted code. This resolves my personal complaint about the excessive vertical formatting of google-java-format.
The only actual code change here is the configuration in pom.xml. The rest is the result of running the formater. The changes are easier to see if you view the diff with "hide whitespace".
This uses <style>AOSP</style> which maintains the 100 character limit. This change brings the option of using  <style>PALANTIR</style> which has a 120 character limit.

@andreaTP Good point about two commits -- updated for that

I like it!

Closing as discussed until we find a replacement for the Palantir formatter.


Remove Custom Field References In Filtered Lookups

Scenario:
Given a Custom Field with a Filtered Lookup (fld1) references another Custom Field (fld2),
When the Custom Field referenced in the Filtered Lookup (fld2) needs to be removed,
Then remove the Filtered Lookup reference in the Custom Field with a Filtered Lookup (fld1).
Currently, if a Custom Field is in this scenario and the destroyStaleMetadata target is used then the following error message is received.

Error: This custom field is referenced elsewhere in salesforce.com. : Filtered Lookup.

Once the Filtered Lookups are removed manually the destroyStaleMetadata target works as expected.

We're running into the same issue and managed to workaround by creating a predeploy target deploying the fields without the filter. Perhaps it's something you can use in the meantime!

@jorrit-steporange could you share your predeploy target here for reference?

@brentfamily1 I'll try to add it tonight or tomorrow, no problem!

Hi @brentfamily1, Sorry for my late reply ....
In my build.xml i've added an extra target
<target name="preUninstall"> 		<echo>Custom preUninstall</echo> 		<sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="preuninstall" runAllTests="false" purgeOnDelete="true" maxPoll="${cumulusci.maxPoll.notest}" />     <echo>Custom preUninstall Done</echo> </target>
In my preuninstall folder i've checked the metadata in containing the lookups without the filter
Let me know if this helps as a workaround or that you need more information

@jorrit-steporange OK, thank you.  Got it.

The Ant targets are now removed from CumulusCI and no longer actively supported. The old Ant target based CumulusCI now lives in the legacy-1.0 branch. I'll try to review and accept pull requests on that branch but will not be actively developing against the Ant version going forward.
All development focus has shifted to CumulusCI 2 which now has feature parity with the Ant based CumulusCI along with far better configurability, access to all Salesforce API's, and encrypted OAuth toolbelt, and a single CLI cci with command help for a much better user experience.


AI Tic Tac Toe

Describe the project you want to add with tech stack
AI based tic tac toe in python which uses AI algorithms  to create a computer opponent that makes intelligent moves and challenges players in the classic game.
Expected behavior

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @TusharKesarwani @pranjay-poddar


update the list of projects adding Plastiks

hi! are we missing something?

Hi @garciapd, this update has been covered, and Plastik has been added already. Thanks!


upstream face login setup has overflowing strings in card layout

this is an upstream bug (part of android settings app). we need to decide whether we want to modify the same.

this is only applicable to the face login setup screen. updated issue title.

moved to https://github.com/GrapheneOS/platform_packages_apps_SetupWizard2/issues/3


Incredibly hard to use compared to Mermaid

For example, you have to escape < and > when using @pintora/cli.  Additionally you cannot have characters like - hyphens, e.g. in notes.  Just filing here, we came to Pintora as an alternative to Mermaid, albeit there are many issues as you can see we've filed #241 #240.

Thank you for the try and sorry about the disappointment .
My personal ability is limited, and I hope that the community will give feedback on various deficiencies in the process of using it,  so I get to improve it.

Can you post some example here ?

For example, you have to escape < and > when using @pintora/cli

Same here , show the example and I will try to fix it


Add documentation example that persists to a file.

Based on this question: https://stackoverflow.com/a/75086108/10693596

[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

The example is the same (reuses the same data) except for persisting to a regular file vs tmpfile. Not sure how valuable this is, but the question came up, so seemed like a quick thing to suggest (but I can also understand if you want to keep the docs a bit more streamlined).

I see -- thanks for clarifying. In that case, I'd prefer to keep the current example. The tmpfile context manager is just being used so that we can clean up after ourselves when doctests are run and this example is actually executed.

Sure, this makes sense. I doubt it's a common issue.


[BUG] Resources limits in chart values.yaml not work

Describe the bug
When i uncomment resources lines in values.yaml, adjust them as necessary, and remove the curly braces after 'resources:' it does not apply.
To Reproduce
Steps to reproduce the behavior:

Specify resources in values.yaml
Install Longhorn from helm chart
kubectl describe pod <pod_name>

Expected behavior
Created pods have resources limits
Environment:

Longhorn version: 1.2.2
Installation method: Helm
Kubernetes distro: AWS EKS 1.19
Node config

OS type and version: Amazon Linux

Thanks @jenting and @wpi86
TODO: We need to evaluate how to add this setting back for both user deployed components (e.g, Longhorn manager, Longhorn driver, Longhorn UI) and system managed components (e.g, instance manager, engine image, CSI driver, etc.)

Any updates on this enhancement?


Clean ApiException.cs

We should clean this commented out part in
public static ApiRequestException FromApiResponse(ApiResponse apiResponse)
some exceptions already implemented, and there is no need to keep dead code for them, some not implemented yet, like case "bot was blocked by the user" but declared, which is misleading

Should BadRequestException and ForbiddenException abstract classes be renamed to BadRequestExceptionBase and ForbiddenExceptionBase?
Could then BadRequestException and ForbiddenException classes be used to throw general 400 and 403 errors?

@karb0f0s Agree, it makes sense to throw general BadRequestException and ForbiddenException  when there is no particular exception type.

https://github.com/TelegramBots/Telegram.Bot/pull/653

Closed due to inactivity


Update .gitignore to ignore standard venv names

Tiny little PR for quality of life when people make venvs to look at cabinetry :)
feel free to do yourself if you don't want to give me easy contributor status ;)

Thanks, this is very useful to have! The CI issue is unrelated and another instance of #199, I will get that fixed separately.

fwiw, I think these and more are covered in github's standard python template, may be worth looking at: https://github.com/github/gitignore/blob/master/Python.gitignore

should be good now!

The CI fails during Codecov upload, which should have been fixed by #230 upon which this branch is based. It is currently unclear to me why the token is not picked up in the CI here.

This is likely related to https://github.com/codecov/codecov-action/issues/330, so let's see whether it can get resolved centrally. The fact that #230 worked fine may have just been a lucky coincidence.

Independent of Codecov, the release of mypy 0.900 requires another small update which will go in via https://github.com/alexander-held/cabinetry/pull/232. With that done and Codecov stabilized, it should then be able to get CI to pass here again.

With #232 done this PR now passed CI as well. Thanks for the contribution!


Prevent password updates for SAML and LDAP users

Description
Currently, CloudStack does not support dual authentication methods for SAML users. If their source is equal to SAML or SAMLDISABLED, then they're not able to login with a username and password. However, when executing the updateUser API to update their password, the password is changed in the database, even though username/password authentication is unsupported for these users.
Regarding LDAP users, password updates directly through CloudStack should also not be allowed. Therefore, this PR addresses these issues by providing a clear error message when SAML or LDAP users attempt to change their password via the updateUser API.

Fixes #9933
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):

How Has This Been Tested?

Verified that attempting to update a SAML or LDAP user's password results in an appropriate error message.
Verified that attempting to update a SAMLDISABLED user's password also triggers the error message.
Verified that non-SAML/LDAP users can update their passwords without any issues.

@blueorangutan package

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11612

@blueorangutan test

@rohityadavcloud a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11830)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 46108 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9999-t11830-kvm-ol8.zip
Smoke tests completed. 132 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_04_nonsecured_to_secured_vm_migration
Error
393.99
test_vm_life_cycle.py

I am merging forward 4.19 on 4.20 and will merge this as soon as the conflicts are taken care of.