Cannot run RocketMQ 4.7.1: Unrecognized VM option 'UseConcMarkSweepGC'

BUG REPORT

Please describe the issue you observed:

I downloaded the built release of RocketMQ 4.7.1 from https://rocketmq.apache.org/docs/quick-start/ and tried to start it according to the docs at the same page. Instead of the mqnamesrv program running, it exits and nohup.txt claims there's an unrecognized java option: Unrecognized VM option 'UseConcMarkSweepGC'

What did you do (The steps to reproduce)?

$ pwd
/Users/jah/Downloads/rocketmq-all-4.7.1-bin-release
$ nohup bin/mqnamesrv &
[1] 9273
appending output to nohup.out
[1]  + 9273 exit 1     nohup bin/mqnamesrv
$ cat nohup.out
Unrecognized VM option 'UseConcMarkSweepGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

What did you expect to see?
Something indicating the server started successfully.

What did you see instead?
Unrecognized VM option: 'UseConcMarkSweepGC'

Please tell us about your environment:

$ java -version
java version "15.0.1" 2020-10-20
Java(TM) SE Runtime Environment (build 15.0.1+9-18)
Java HotSpot(TM) 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)
$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk-15.0.1.jdk/Contents/Home
$ uname -a
Darwin nova.local 19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 x86_64

Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

I tried "hacking" the bin/runserver.sh script to just remove the unrecognized option (I don't need this working in prod, just for local development) but additional unrecognized options were found, so I kept removing them until eventually the program just plain wouldn't start and gave me some weird fatal error in a file I've since deleted. Apparently hacking away at the unknown options is not the way to fix it, who knew ;P

@jahio You are right.  There are some problems when using scripts to start rocketmq with jdk15.  At present, it is better to use jdk8.

getting this issue with jdk-18.0.1

I am getting the same issue with java version "17.0.1"


Support updating mesh config with istioctl command

Describe the feature request
We often need to tweak some fields in the meshconfig for various needs, for example, enabling/updating the access log format, configuring the extension provider, and etc.
Currently we usually ask the user to run kubectl edit configmap istio and manually edit the configmap. This is really a pain process, the user needs to be careful about the indent and also not accidentally changing other parts. What's worse, this process cannot be used with CI/CD or other automatic pipeline.
It would be much easier if the istioctl can support such use cases with a simple sub command, for example:
istioctl experimental meshconfig merge -f mesh-config-patch.yaml

Internally the meshconfig merge command can just use the proto.Merge for the merge behavior, it won't support all operations but should be good enough for most cases. It should also support the --revision flag for meshconfig with non-default name.
cc @istio/wg-user-experience-maintainers for comments.
Describe alternatives you've considered
Use yq with some shell commands to serialize and modify the meshconfig. The drawback is that yq is not a standard program on every system and needs to be installed separately, it also requires the user to learn the yq syntax even for simple modifications.
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
Additional context

I like this idea.  I put it on the agenda to discuss at next week's UX working group.
In the past when I have proposed istioctl commands that modify mesh config I have heard that we want istioctl install to be how the mesh config gets modified.  I am curious to see if attitudes have changed.

Please, don't.
Current MeshConfig is 'owned' by the installer of the revision ( istioctl or helm ), any change by user will be overridden. That's how the installer works, and there is no way to prevent that AFAIK.
Last Env WG we discussed the other problem with MeshConfig - if you have multiple revisions it is hard to have settings that apply to all revisions, you need to effectively re-install (reapply) each of them.
The proposal was to change the code loading MeshConfig and instead of reading istio-REVISION, to also read one or
more 'fragments', and merge. This will allow proper CI/CD systems to be used. For example config maps with name prefix
'istiod-user-' can be merged. Of course, this behavior will only apply to 1.10+.
The installer should NEVER create such configs - they will be owned by user CI/CD.
The main risk is that a change in the common mesh config can break ALL istio revisions, since it is global.
This is common with other 'default' settings (DestinationRule, etc) - and we can use the common solution, which
is that we can still use the 'istio.io/rev' annotation to 'bind' the config to a revision. So user can still canary
the config change, and if canary works apply it to other revisions.
Edit in general is not the right way to operate - so we should not 'promote' it with a dedicated command in
istioctl.
In addition, there is an issue of 'separation of concerns' - MeshConfig has many settings, and it is desirable to
have for example a separate CR with the default log settings, another one with the default proxy config, one
for authz, etc. This is aligned with the planned 'graduation' of MeshConfig features into proper APIs - we are
already working on having telemetry separated to a proper CRD.
The change is super localized - only one function is used to load MeshConfig, we already have code
to merge ( there is a 'default mesh config' hard-coded ).

https://github.com/istio/istio/issues/31400

Edit in general is not the right way to operate - so we should not 'promote' it with a dedicated command in istioctl

:+1:

@esnible @costinm @howardjohn
I had this idea only for making it a bit easier to modify the meshconfig for convenience because there are a lot places on istio.io asking users to run kubectl edit configmap istio to update the content manually.
I don't understand how this will block Env WG's plans for changing the meshconfig or making it harder in any ways.
Also I don't think it should be considered to promote editing meshconfig in istioctl. It's just like istioctl dashboard prometheus that allows opening the prometheus dashboard conveniently but I don't think anyone would consider it the right way to operate prometheus in production.

@yangminzhu In the current istio.io, I see only two places we ask the user to edit the configmap:

https://preliminary.istio.io/latest/blog/2021/better-external-authz/ (written by you)
https://preliminary.istio.io/latest/docs/tasks/security/authorization/authz-custom/

My understanding is that users aren't supposed to do that.  @costinm told me they should do istioctl install to change settings.  Is my understanding correct?
I believe users want to see and make changes quickly.  However, some changes require istiod and/or pods to restart, so we can't offer the ability to make changes to the mesh config.  I still would like the ability for data-plane users to see the mesh config.  I want something like an istioctl describe mesh for that.

@esnible If the user knows everything they need in the meshconfig, of course they won't need to edit the meshconfig after the installation.
But this issue is not trying to change that, this issue is trying to help a different use case when the user needs to tweak the meshconfig after the installation because the meshconfig includes many dynamic configurations. One example is the extension provider in the ext-authz where you want to customize how to talk to the extension provider later.
Some more examples, the following tasks involve updating meshconfig. I don't think most users would just use these values configured once in the initial installation, they often need to modify these values after the installation, for example, change the logging format to include/exclude some information, change the trace sampling rate temporarily for debugging (and change back after):
https://istio.io/latest/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging
https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#using-meshconfig-for-trace-settings

kubectl patch or equivalent (kubectl edit, etc) should never ever be used in a real production environment - users should be using gitops or similar declarative configuration management. So its really a matter of if we want to make our docs recommend best practices, or make them simpler.

@yangminzhu I agree with you.  Let's work toward a solution.
I tried the following
cat > /tmp/external-auth.yaml <<EOF
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    extensionProviders:
    - name: "opa.local"
      envoyExtAuthzGrpc:
        service: "local-opa-grpc.local"
        port: "9191"
EOF
istioctl install -f /tmp/external-auth.yaml

I realize it looks weird to do istioctl install just to update a single configmap.  But there is a bigger problem.  Many users SHOULD have permission to update the meshconfig, but not to install.  I am not sure how to handle those people.  See next comment.

@howardjohn @costinm See previous comment for situation.
Suppose we have a user who has a declarative model of their OPA authorization.  Suppose the OPA server has changed and they need to use a different OPA server.  This is a pure data plane thing, and they have RBAC permission to edit the ConfigMap on their cluster.
How should they make the change in their OPA config?  Let's assume their control plane is managed by their vendor and they can't do istioctl install.  Perhaps the user is not a human, but a service account authorized pipeline script.

@yangminzhu After reading your blog I feel like users would like to do something with more hand-holding, either using a new Istio CRD for "EnvoyAuthzExtensionProvider".  I think that would be the best way, rather than using MeshConfig.  Are you working on CRDs?
If we plan to continue to go through the MeshConfig, the user might want commands like istioctl x authz extensions list and istioctl x authz extensions add <yamlfile> rather than generic istioctl experimental meshconfig merge.
$ istioctl x authz extensions list
PROVIDER SERVICE             PORT
opa.local local-opa-grpc.local 9191
my-custom-ext-authz-service ext-authz.istio-system.svc.cluster.local 9000
keycloak                    keycloak.default.svc.cluster.local.      8080 path_prefix=/openid-connect/token

It doesn't really matter how they install it - if they have external
control plane maybe they have a plain configmap yaml, if they use helm they
have a values.yaml, otherwise they have an IstioOperator yaml.
Regardless, there is some yaml file on a disk somewhere - for prod, likely
a git repo with gitops. The recommended flow, regardless of method, is
modifying that yaml and reapplying. I don't think imperative commands are
ever a good option, aside from demos, regardless of install type.
On Sat, Mar 13, 2021, 7:45 AM Ed Snible @.***> wrote:

@yangminzhu https://github.com/yangminzhu After reading your blog I
feel like users would like to do something with more hand-holding, either
using a new Istio CRD for "EnvoyAuthzExtensionProvider". I think that would
be the best way, rather than using MeshConfig. Are you working on CRDs?
If we plan to continue to go through the MeshConfig, the user might want
commands like istioctl x authz extensions list and istioctl x authz
extensions add  rather than generic istioctl experimental
meshconfig merge.
$ istioctl x authz extensions list
PROVIDER SERVICE             PORT
opa.local local-opa-grpc.local 9191
my-custom-ext-authz-service ext-authz.istio-system.svc.cluster.local 9000
keycloak                    keycloak.default.svc.cluster.local.      8080 path_prefix=/openid-connect/token
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31387#issuecomment-798533841, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIKUELQQ2G46J76R7DTDN3BZANCNFSM4Y7RDIOA
.

What is the current status?
We have also the use case that we are using multiple IstioOperator CRs for creating multiple environments. Since we switch to the amazing extAuthz feature of istio we have the problem that the meshConfig is overridden every time a new IstioOperator CR is created... Right now we are using the workaround to specify all extensionProviders in every IstioOperator CR. But I don't think that this should be the natural way. I would do a PR to the istio operator for handling this merge but as I understand from this discussion, it would be better to move the whole extensionProvider to an own CRD?

You should configure it in the IstioOperator spec. under spec.meshConfig
On Sat, Sep 25, 2021, 7:33 AM Sven Batista Steinbach <
@.***> wrote:

What is the current status?
We have also the use case that we are using multiple IstioOperator CRs for
creating multiple environments. Since we switch to the amazing extAuthz
feature of istio we have the problem that the meshConfig is overridden
every time a new IstioOperator CR is created... Right now we are using the
workaround to specify all extensionProviders in every IstioOperator CR. But
I don't think that this should be the natural way. I would do a PR to the
istio operator for handling this merge but as I understand from this
discussion, it would be better to move the whole extensionProvider to an
own CRD?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31387#issuecomment-927129791, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJCIIGK7ZQXHTVGYP3UDXMT7ANCNFSM4Y7RDIOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Include preferred-versions in index file

The index file on Hackage contains a file called preferred-versions containing information on deprecated versions of packages (e.g. it's where the information that stack versin 9.9.9 is deprecated is found).  It'd probably be good to include that file also in the index file on the mirror.

@dysinger As the last guy to touch this: do you know offhand if this is easy to implement?

Looking at the codebase myself right now... I don't understand why it needs to reconstruct the tarball instead of just uploading the original, unmodified tarball. This seems to be fragile and CPU-intensive for no reason. @manny-fp @dysinger any thoughts?

I don't know why.  That repacking code just seems to exist to explicitly leave out preferred-versions, but no idea why.  I went back to the original history of simple-mirror in the private repo and the code was there from the beginning.

In that case, I'm going to modify this to just upload the unmodified file.

This is now resolved. @magthe if there are still problems, please let me know.


Windows10, VisualStudio2015, System.NotSupportedException

After moving to Windows10 I get the error "System.NotSupportedException" in SQLite.Net.dll, additional info is "Cannot compile: Parameter".
The statement when I get the error is
(From s In MyDb.Table(Of Song)()
Where (s.GetArtist = ArtistName)).OrderBy(Function(x) x.Songname)
Think it has to do mainly with Win10, not VS2015 ?
Maybe there's any help ?
Thx in advance !

It's working again with the new version 3.1. thank you !

Strange, but good :)


TW-64306: Output prior release

https://jira.extendhealth.com/browse/TW-64306
Summary of PR changes
Output prior version.
When pushing PR comments with the next version, in some cases it is helpful to update said comments with current release when a major or minor bump is not generated.  My team is using this in various scenarios and would rather not have to compute the previous version ourselves.  Since this action already gets the previous version, it seemed easy enough to include it as an output.
PR Requirements

[x] For major, minor, or breaking changes, at least one of the commit messages contains the appropriate +semver: keywords.

See the Incrementing the Version section of the repository's README.md for more details.

[x] The action code does not contain sensitive information.

NOTE: If the repo's workflow could not automatically update the README.md, it should be updated manually with the next version.  For javascript actions, if the repo's workflow could not automatically recompile the action it should also be updated manually as part of the PR.

PRIOR_RELEASE_VERSION

But is it really a really a release?  It could just be a previous tag, not an actual release.
I am fine naming it whatever, I don't have much of a stake in it.  I will change it to PRIOR_RELEASE_VERSION.

PRIOR_RELEASE_VERSION

But is it really a really a release? It could just be a previous tag, not an actual release.
I am fine naming it whatever, I don't have much of a stake in it. I will change it to PRIOR_RELEASE_VERSION.

Well, the tag that git-version-lite uses to base its version calculation is always a tag that matches a non-prerelease semver pattern. So from a semver perspective it's a release.

Closed in favor of #38 because the forked branch is unable to be merged.


[3345] add magic link tokens to users

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Add support for magic link tokens to users


cmd/go: TestVetWithOnlyCgoFiles failing on Plan 9

CL 99175 added TestVetWithOnlyCgoFiles. However, this test is failing on Plan 9.
--- FAIL: TestVetWithOnlyCgoFiles (0.12s)
	go_test.go:3243: running testgo [vet p]
	go_test.go:3243: standard error:
	go_test.go:3243: can't load package: package p: build constraints exclude all Go files in /tmp/gotest874832146/src/p

	go_test.go:3243: go [vet p] failed unexpectedly: exit status: 'testgo 2781: 1'
FAIL
FAIL	cmd/go	140.465s

See https://build.golang.org/log/4f68771333f1332d45b1faaebb05892188b01c85

More generally, this test should be disabled on every platform where CGO is disabled.


chore: compress images

Losslessly compress images using Pngcrush. Should reduce the build size by a tiny amount.

Thanks for this! I rebased this change onto the manifest-v3 branch, as I intend to re-release that update pretty soon.


Added few faqs

Added few faqs
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66315ba9a8a5f228d2117532--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66315e14f64c282aa19a485d--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66315ea68eb74b2c15cb07ba--harness-developer.netlify.app

To avoid further merge conflicts and merge delays, I am moving the CI questions from this PR to #6534

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6631753261af493d04070615--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://663175b84bcbfd3eeca85c44--harness-developer.netlify.app

combined CD FAQs from PRs 6532, 6529, 6524 to minimize MCs.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://663196749e2b8e58270eb1f4--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://663256d82cb0fff37baabda9--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6632a46a653c4510aece3131--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66332c0e7e6f097650054bde--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6646228cf1c060cc5bf5b43f--harness-developer.netlify.app


Add table aws_qldb_ledger and aws_qldb_stream Closes #2265 #2266

Integration test logs

Logs
N/A

Example query results

Results
N/A

The Amazon QLDB service is in a retirement state, and they have stopped supporting the creation of resources under the QLDB service. Therefore, this PR could not be tested. Announcement: https://docs.aws.amazon.com/qldb/latest/developerguide/what-is.html

Closing this PR since the Amazon QLDB service is in a retirement state, and they have stopped supporting the creation of resources under the QLDB service. Announcement: https://docs.aws.amazon.com/qldb/latest/developerguide/what-is.html


Add JavaMelod to amp-add-common

Current coverage is 96.67% (diff: 100%)

No coverage report found for master at 5fbea0e.

Powered by Codecov. Last update 5fbea0e...efc6257


magpylib v1.1.0b

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed) (Was already 0)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This bumps the feedstock to our latest version on PyPi.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


REL-1381 v23.1.28 (was 23.1.27): [Docs] Adjust release notes for download/SH

Fixes REL-1381
In releases.yml, removed cloud attributes to show download links.

@mdlinville please review the markdown fix. thanks!


Skip data preparation in model.setup if input data exist

Currently model.setup takes a config template file and prepares output that are needed for model.run i.e. these preprocessing:
        forcing_io.prepare_forcing(self._config)
        soil_io.prepare_soil_data(self._config)
        soil_io.prepare_soil_init(self._config)

It should be possible to skip data preparation in model.setup if input data exist.

@SarahAlidoost Hi Sarah, it will help save storage space if we can skip data preparation when the input data is ready to be used. W can add an input parameter, prepare_data_option: Optional [bool] = True in model.setup, and add an if-else statement to decide whether to copy and prepare input data before running the model. Please let me know your opinion, and I'd like to pick up this issue.

@SarahAlidoost Hi Sarah, it will help save storage space if we can skip data preparation when the input data is ready to be used. W can add an input parameter, prepare_data_option: Optional [bool] = True in model.setup, and add an if-else statement to decide whether to copy and prepare input data before running the model. Please let me know your opinion, and I'd like to pick up this issue.

nice that you want to pick this up. Perhaps a better idea is that to be able to skip model.setup(), e.g. instead of
model = StemmusScope(config_file=path_to_config_file, model_src_path=path_to_exe_file)
model.setup()
model.run()

we can also do:
model = StemmusScope(config_file=path_to_config_file, model_src_path=path_to_exe_file)
model.run()

This will require to setself.cfg_file in init function and adding some validations for input and output directories e.g. they exist and are valid.


feat: extract Editor component into core package

closes #100
This PR pulls the UI in the screenshot below into a separate React component inside the core run-wasm package.
A user could import this component from the package to use this default interface. import { Editor } from '@run-wasm/runwasm'

Great work @octokatherine!
@all-contributors add @octokatherine for her code contributions


dunstone, automobilists

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,d]

/trunk merge


Role Assignments Platform Dependency

This appears to work the first time but subsequent runs result in an error.
| 18:16:21 - The deployment
| 'roleAssignments-20211107T1811318847Z' failed with error(s).
| Showing 1 out of 1 error(s). Status Message: The role
| assignment already exists. (Code:RoleAssignmentExists)
| CorrelationId: 857164a2-a31a-4d4c-9bab-9c19239cb5be

@eriqua for me it looks like, that is working in our environment. Do you have an idea, why it failed for @cacarroll ?

@cacarroll , can you please do a fetch and see if the issue is still present. We’ve recently updated most modules part of the 0.3 release. Thanks

Closing as there was no progress in 3 months


Appium Scroll: added ability to set top and bottom point coordinates …

…for scroll
Proposed changes
As Is: coordinates for scroll in Appium are hardcoded (from center of screen to 0.25 of height). I have a some kind of bottomsheet, wich can be expanded by swipe from bottom to top. But start point of swipe should be below then center of the screen. I cannot do that.
To Be: user can set start and end points of scroll in percent of screen height.
Checklist

[x] Checkstyle and unit tests are passed locally with my changes by running gradlew :appium test command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@qwez Thank you. Very good for the first contribution! :)
Code style warnings:
> Task :modules:appium:checkstyleMain FAILED
Error: eckstyle] [ERROR] /home/runner/work/selenide/selenide/modules/appium/src/main/java/com/codeborne/selenide/appium/commands/AppiumScrollTo.java:75: Line is longer than 136 characters (found 157). [LineLength]
Error: eckstyle] [ERROR] /home/runner/work/selenide/selenide/modules/appium/src/main/java/com/codeborne/selenide/appium/AppiumScrollOptions.java:17: Line is longer than 136 characters (found 145). [LineLength]

Code style warnings

Fixed

@qwez - can you update the readme file about how people can use this feature? People might be unaware of this functionality if we don't update it. It is better to update the PR description as well with the code.

@qwez - can you update the readme file about how people can use this feature? People might be unaware of this functionality if we don't update it. It is better to update the PR description as well with the code.

yeah, sure, will do soon


💅 Polish: Run a performance audit

Tooling Report Checklist

[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my request.
[X] This is the appropriate issue form for the tooling issue I would like to report.

Expected
The site performance is pretty good as-is. But, it can be better.
Actual
At least the Google Font embed is too much data. And I should check whether that font (and any other resources) should be loaded from the learningtypescript.com domain.
Additional Info
Marking as blocked similar to #15.

Nice.
I'll just fix the one last // TODO: Reduce these to just the weights I actually need: referring to the Google Fonts family include.


Check Cardinality [Model/API]

Set of model cardinality settings that need checking and changes made if found to be wrong. Item numbers refer to the row numbers in column A of the attached spreadsheet.
See rows 74, 101, 106, 107,  129, 200
Final decisions:
74: endpoint.endpointlevel: change cardinality to 1
101: encounter.encounterScheduledAtTiming: keep cardinality at 0..1 => No change
106: encounter.encounterType: change cardinality to 1
107: encounter.encounterEnvironmentalSetting: keep cardinality at 0..1 => No change
129:
estimand.treatment: change cardinality to 1
estimand.variableofinterest: change cardinality to 1
200: scheduleTimeline.scheduleTimelineEntry: change cardinality to 1
USDM_CT_Required.xlsx

@BSnoeijerCD  @jared-schreibman-cdisc Just an image from the spreadsheet of all the rows mentioned above, make it easier to see them. These are tidy-up changes, just review them and see if a change is necessary (might not be).
Note: At some point in time we want to get these cardinalities into the UML inside of EA, don't forget that.

@daveih @jared-schreibman-cdisc
Notes:
Row 74: endpointLevel will be changed to Level (See ticket #98). Discuss with team whether endpoint always needs a level. As objectives already have a level and are linked to endpoints. The endpoint level might be superfluous. However, as discussed in phase 1 with the SMEs, some companies might have a secondary endpoint linked to a primary objective.
Row 101: According to my opinion an encounter should have a timing. That is the basic principle of an encounter. Could be the same as the timing of scheduledinstance.
Row 106/107: encountertype and encounterenvironmental setting might also have been changed to Type and EnvironmentalSetting already (to be checked). To discuss whether we this must be completed. I tend to have the first one 1 and keep the environmentalsetting at 0..1
Row 129: An estimand combines 1 analysispopulation with 1 endpoint (variableOfInterest) and 1 or more intercurrent events. So, given that: 1 is ok for this one.
Row 200: To discuss. I tend to say 1. What happens if it is 0?

@BSnoeijerCD @jared-schreibman-cdisc
Row 74: Endpoint has a level, we have had this discussion previously as part of the public review, see https://jira.cdisc.org/browse/DDF-438
Row 101: It is whether we constrain the model at the current time?
Row 129: Need to look at the entire set, the set is inconsistent, see image below
Row 200: Implication is you have a timeline with no start point, would be a little odd

@dih-cdisc based on the points above I would then suggest the following:
74: endpoint.endpointlevel - Set to 1 instead of 0..1
101: encounter.encounterScheduledAtTiming: Set to 1 instead of 0..1
(I believe it should be constrained and is save to do so. But if you want to leave it for now that is ok with me).
106: encounter.encounterType: change cardinality to 1 (already decided above)
107: encounter.encounterEnvironmentalSetting: keep cardinality at 0..1 => No change (already decided above)
129:
estimand.analysispopulation Keep at 1
estimand.treatment ?  Set to 1 instead of 0..1
estimand.variableofinterest ? set to 1 instead of 0..1
200: scheduleTimeline.scheduleTimelineEntry ? set to 1 instead of 0..1
Can you agree on that? Then I will update it above to make it clear to the team.

All good except for "101: encounter.encounterScheduledAtTiming: Set to 1 instead of 0..1" Just being cautious on this one, leave it as is. We can always make a separate ticket just for it and place in backlog so we recheck it.

@jared-schreibman-cdisc : documented final decisions in description of ticket above. So you have 1 overview.
You are good to go to make the changes
FYI: @dih-cdisc @drewcdisc

Reviewed: Except for the first change indicated in the descriptions above - other changes did not yet land in final API.


Readme error log consent

Mostly generated by GPT. The key points are that we adhere to CCPA requirements and that the SDK is subject to our Privacy Policy.

Let's have a TOS.md instead of putting this in README.md

I looked at some other repos, and TOS is not a common readme (sorry for the misleading suggestion). Let's keep these changes though; I've raised an issue to the  documentation repository in the meantime.


Upgrade to Guzzle 6

There are too much work to be done (and too much code to be added) only to get the effective url so I'll stay on Guzzle 5 for now.


Vickel: Watch fulminoussoftware.com

Vickel requests the watch of the watch_keyword fulminoussoftware\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

fulminoussoftware\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


yo office requires git

Tutorials and quick starts that use Yo Office don't currently list git as a required prerequisite-- but Yo Office requires it.
Article URL
(All quick starts and tutorials that use Yo Office)
e.g., https://docs.microsoft.com/office/dev/add-ins/tutorials/excel-tutorial-create-custom-functions
Issue
Yo Office requires git to operator correctly. You'll see this if you follow the steps on a brand new computer with nothing already installed.
All articles that contain guidance about using Yo Office should be updated to list Git as a required prerequisite.

@davidchesnut FYI, I've updated the description of this issue to indicate that this issue applies to any article that contains guidance for Yo Office (not just the Custom Functions tutorial). I'll fix this issue today.

Submitted PR #1029 to address this issue. Changes will be visible in the live docs later this week, after the PR is merged and doc updates are published.


AWSPowerShell cmdlets error - Could not load type from assembly

I was following the documentation to start using the AWSPowershell Module, and installed AWS SDK for .NET on the server but when I would open powershell and import the module I would receive an error.
Expected Behavior

The documentation on setting up my credentials into a profile, said to use the Set-AWSCredential and saved them as a profile, and then i'd be able to use my profile with other cmdlets.
Current Behavior

Then issue started when I entered the Set-AWSCredential and received following error:
Get-AWSCredential : Could not load type "Amazon.Runtime.CredentialManagement.CredentialProfile" from assembly "AWSSDK.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=885c28607f98e604".
At line:1 char:1
+ Get-AWSCredential
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-AWSCredential], TypeLoadException
    + FullyQualifiedErrorId : System.TypeLoadException,Amazon.PowerShell.Common.GetCredentialCmdlet

I received this error on a number of other cmdlets as well. (For example, Get-AWSCredential, Get-EC2Instance, etc)
Possible Solution

I loaded the assembly on PowerShell and I saw that the dll was being loaded from the GAC, which had an older version of the file. I removed the old dll and reloaded PowerShell and it started working.
Steps to Reproduce (for bugs)

I'm not sure how to reproduce the bug. These happened on Terminal servers that are shared between multiple people; however, I made sure that the SDK and the PowerShell module were not installed before performing the installation.
The old dll file was over a year old too, 6/6/2016, so maybe someone installed it the SDK at one point and since removed it; however, it's hard to tell.
Context

This issue prevented me from being able to use the AWSPowershell cmdlets and manage my VPC through code.
I couldn't find any help on google, or even from AWS support, about this issue, so I'm hoping to be able to provide someone with some insight in case they find themselves in this situation.
Your Environment

AWSSDK.Core version used: <IP_ADDRESS> (Or so I thought)
Service assembly and version used: AWSSDK.Core version <IP_ADDRESS>
Operating System and version:  Windows Server 2012 R2
Visual Studio version: N/A
Targeted .NET platform: .NET 4.5

.NET Core Info

.NET Core version used for development: N/A
.NET Core version installed in the environment where application runs: N/A
Output of dotnet --info: N/A
Contents of project.json/project.csproj:  N/A

Thanks for reporting the issue and figuring out what the problem was.
None of our installers have been placing SDK assemblies into the GAC for quite some time, and any behavior that did pre-dates the v3 SDK and PowerShell tools so it's a bit of a mystery as to how these older assemblies got there.
The AWSPowerShell module manifest lists the SDK assemblies that we depend on. I'm going to see if we can prefix these with a variable that might cause the shell to start looking at the install folder for the module first in the hopes that this might circumvent the issue should it occur again. Apart from that, there's little I can think of to do to 'fix' this so I'm going to resolve the issue.

I think I've run into the same issue. I'm going to be a bit verbose here to make it easier for googlers to find it.
For me I was actually using  AWSPowershell.NetCore (running on windows 10), and I get the following error:
 Get-AWSCredential -ListProfileDetail
Get-AWSCredential : The type initializer for 'Amazon.AWSConfigs' threw an exception.
At line:1 char:1
+ Get-AWSCredential -ListProfileDetail
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Get-AWSCredential], TypeInitializationException
+ FullyQualifiedErrorId : System.TypeInitializationException,Amazon.PowerShell.Common.GetCredentialCmdlet

After attaching the debugger and digging to the exception, I found that I also had a DLL coming from the GAC. Which I then confirmed with the gacutil.
 PS> & "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.1 Tools\gacutil.exe" /l | Select-String AWS
InputStream:457:  AWSSDK.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=885c28607f98e604, processorArchitecture=MSIL
InputStream:458:  AWSSDK.S3, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=885c28607f98e604, processorArchitecture=MSIL

The actual version I found in the GAC was:
[assembly: AssemblyVersion("<IP_ADDRESS>")]
[assembly: AssemblyTitle("AWSSDK.Core")]
[assembly: AssemblyDescription("The Amazon Web Services SDK for .NET (4.5) - Core Runtime")]
[assembly: AssemblyProduct("Amazon Web Services SDK for .NET")]
[assembly: AssemblyCompany("Amazon.com, Inc")]
[assembly: AssemblyCopyright("Copyright 2009-2015 Amazon.com, Inc. or its affiliates. All Rights Reserved.")]
[assembly: AssemblyFileVersion("<IP_ADDRESS>")]
[assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName = ".NET Framework 4.5")]
[assembly: AssemblyInformationalVersion("1.0.0")]

Removing the DLLs from the GAC and restarting resolved the issue.


Impossible to distringuish the official plugin from RedHat and debugger integration

Hi,
I would say that current plugin name is slightly misleading:

May be change it to something related to debugger or run configuration? Let's say Quarkus Run Configuration or Quarkus Debug?
Also, two plugins with the same icon look suspicious. I'd recommend to change icon or add some detail that is associated with debug/run.

I changed the plugin title and icon. Version update was requested, and the update should be available soon.

Thank you so much!


Add CoreDNS details to the customize DNS doc

Rewrite the document to include more details about CoreDNS, since it's now the default from v1.12

@johnbelamaric @chrisohaver @fturib PTAL

@rajansandeep @chrisohaver @johnbelamaric Is this in a place where it's ready for my final review?

@zparnold Yes, this is ready for final review.

@rajansandeep can you please address @chrisohaver 's concerns, and then I can review

/assign @zparnold
I've addressed all concerns.

/lgtm
/approve


Error:connect etimedout

code:'BAD NETWORK'.

please tell me how can i solve this problem?

This isn't an issue of the repo itself, but of your Internet connection. Try using https://github.com/vitalets/google-translate-api and see if that will fix your issue.

emmm, I am annoyed with this problem too. But '@vitalets/google-translate-api' seems not to work for me.

@qwtao Have you used tld: 'cn' option?


plots for KA and % agreement

closed via https://github.com/ebgoldstein/StormImpactIRR/commit/ea60a0440cdce1ae605bc30ce2ffd43df183dc8e


fix: Ping helms3 version

To fix the issue mentioned here https://github.com/hypnoglow/helm-s3/issues/203

@mahmoud-samy How should we address such issues/fixes in the future? This is already available on the main repo but I'm hesistant to sync the 2 repos, wdyt?


Faulty? mt942 from mBank

I'ma trying to parse mt942 provided by polish mBank, which throws:
  File "/home/users/bociek/lmsmap/eggs/mt_940-4.3-py2.7.egg/mt940/tags.py", line 70, in parse
    self, value)
RuntimeError: ('Unable to parse "<mt940.tags.FloorLimitIndicator object at 0x7fab98295050>" from "PLN0"', <mt940.tags.FloorLimitIndicator object at 0x7fab98295050>, 'PLN0')

That is because of line:
:34F:PLN0

Which does not match https://github.com/WoLpH/mt940/blob/develop/mt940/tags.py#L162 regex - the line is lacking credit/debit mark.
I'm not sure if credit/debit mark is obligatory here, however there's one thing i know almost for sure - mBank will not fix it ;).
i can imagine two resolutions:

make regrex [DC] optional, if it's optional indeed
add support for another preparse_ processors, which could be run somewhere before https://github.com/WoLpH/mt940/blob/develop/mt940/models.py#L341

I need advice what is the better solutoin, anybody?

Well, seems like debit mark is optional: https://www2.swift.com/uhbonline/books/public/en_uk/us9m_20160722/htframe.htm
but it not quite clear for me:

When D/C Mark is present, it must contain the following code (Error code(s): T51):
D	Debit	Debit floor limit.

So, only "D" is allowed??
and:

PRESENCE
Mandatory
…
When field 34F Credit Floor Limit Indicator is absent, the floor limit applies to both debit and credit amounts. When different limits apply, field 34F Credit Floor Limit Indicator must be present.

How it's possible than presence od 34F is mandatory and last sentence allows it's absence? It' contradictory, isn't it?

As I understand it (from your link) the pattern is: 3!a[1!a]15d
Which means:

3!a: 3 required characters (the currency in this case)
[1!a] an optional character for debit/credit (C or D)
15d a 15 character number decimal number

It seems when I accepted the pull request for the MT942 support (which added the 34F statement) I didn't check the code thoroughly enough. The pattern seems to be broken: https://github.com/WoLpH/mt940/blob/develop/mt940/tags.py#L162
Instead of (?P<status>[A-Z]?[DC])  # 2a Debit/Credit Mark that should be: (?P<status>[DC]?)  # 2a Debit/Credit Mark I think.
Can you try the current development release? I think my last change might fix the issue.

Thanks @WoLpH,  I've forked this repo, and working on https://github.com/sq9mev/mt940/tree/feature/mbank.
Investigating further i've found some more issues with mt942:

currency of transactions can not be recognized correctly
sum_credit_debit_entries adds the same keys to transactions.data overwriting each other

You can take a look at my work, i'll try to provide PR with some tests tomorrow.

Great! Thanks so much for the help :)

Thanks @WoLpH, closed in #32


Weird Scroll Issue

no matter how "long" the description of a card is using Legacy Editor, it doesn't actually extend the box. It remains at like, three-ish lines long. It is incredibly irritating. Not sure if there's a fix.

Hi @Rift0715,
can you confirm that you use the latest version of the extension (1.7)?

yes. i am @sewerynkalemba

@Rift0715,
Do you use Firefox or Chromium-based browser?

i use Firefox, yes

Ok, I've used a CSS property field-sizing that is not supported by Firefox – that's my oversight. I will try to find a workaround and realease a new version with the fix as soon as possible. Sorry for the inconvenience.

@Rift0715,
The fix was published with version 1.8, which should be already available to update to on Firefox. It's not as smooth as it can be, but I believe it's enough of a workaround until we get field-sizing property in Firefox.


Add French

French file for Hello World.

@LeDuke-AS Update the readme here: https://github.com/LeDuke-AS/hello-world/blob/patch-3/readme.md


Add unpkg field to package.json

This allows unpkg.com to point to the UMD build of redux via https://unpkg.com/redux. Currently, this points at lib/redux.js (as it falls back to using the main field) which will not run in browsers.

Thanks!


ZooLock uses ZooReader which may retry on session expired

Accumulo tablet servers use ephemeral nodes in zookeeper to advertise their existence. If this ephemeral node is deleted for any reason a tablet server must halt.   One way it can be deleted is if  a tablet server is not responsive enough to zookeeper servers.  In this case the zookeeper servers will close the session which causes any ephemeral nodes related to the session to be deleted.  If the tablet server is still alive and tries to communicate with zookeeper it will get a session expired exception.  When this happens the tablet server should halt.
The code that manages tablet servers ephemeral nodes is called ZookLock.  ZooLock uses an Accumulo abstraction  for Zookeeper called ZooReader.  The ZooReader code may retry on session expired events.  Need to examine ZooLock's use of ZooReader to ensure that retrying on session expired events does not delay ZooLock from becoming aware of session expiration.

@keith-turner Any interest in investigating this before we start voting on 2.0.0 release candidates?

I added this a blocker because I think it would be good to investigate before 1.9.4.  Since its a long standing issue not introduced in 1.9.3, It need not block 1.9.4 if not investigated in time.

I looked into this a bit today.  Another issue I discovered with ZooLock's use of ZooReader is that it automatically creates new Zookeeper objects when a session has expired.  I am not sure if this is causing any problems, but its a concern I have.  The following is some background info.

Zookeeper objects have a one to relationship with a zookeeper session.  When a session expires zookeeper objects become non-functional.
Zoolock relies on ephemeral nodes which are automatically deleted when a session expires.

It may be ok that new Zookeeper objects are automatically created because the ephemeral node will cease to exist and this would be visible through the new zookeeper object.
Because of the tight coupling between zoolock, ephemeral nodes, zookeeper objects, and zookeeper sessions I think it may be better if zoolock directly uses zookeeper w/o any intermediate abstraction layer.

@keith-turner do you think this issue is still around?  I'd like to try to understand it and possibly help get it resolved for a 1.10 release.

@milleruntime I suspect its still around.  I will take a look and post some code links if I find its still an issue.

@milleruntime  I researched this a bit more, looking into the following two concerns.

ZooReaderWriter retries on session expired exceptions.
ZooReaderWriter automatically gets a new zookeeper when one is closed.

For issue 1, looking at the code zoolock code it deals mainly deals with session expired in watcher.  As far as I can tell ZooReaderWriter does not alter events from watcher at the moment.  For other code in ZooLock, its difficult to analyze the impact of ZooReaderWriter retrying on session expired.  There were a few places I was concerned about that seemed like they may work by accident.  So for concern 1 I have yet to identify an actual bug through code analysis, but I suspect there could be potential bugs.
For concern 2, I did find an actual race condition that seems like it could result in erroneous being placed in the metadata table.
In the code below, ZooLock calls ZooReaderWriter.getZooKeeper().getSessionId() to compute its LockId
https://github.com/apache/accumulo/blob/rel/1.9.3/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooLock.java#L358-L363
Below is the code for ZooReaderWriter.getZooKeeper().  If you follow this code you will see that it creates a new Zookeeper if the current one is closed.  For the above code that is problematic, because a new ZK object would have a different session id.
https://github.com/apache/accumulo/blob/rel/1.9.3/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooReaderWriter.java#L48-L54
The code below is called by the tablet server and based on the previous code may put the wrong id in the metadata table.
https://github.com/apache/accumulo/blob/rel/1.9.3/server/base/src/main/java/org/apache/accumulo/server/util/MetadataTableUtil.java#L135-L138
For this particular case a fix may be to make ZooLock.getLockID call ZooLock.getSessionId() instead of ZooLock.zooKeeper.getZooKeeper().getSessionId().  But I am not completely sure.  Anyway this is one example of how the zookeeper silently switching under zoolock could be problematic, there may be other cases.

Looking at the code and comparing that with the zookeeper examples on locks, would it be viable to use a guid when the ephemeral node is created?  (See https://zookeeper.apache.org/doc/r3.5.0-alpha/recipes.html#sc_recipes_errorHandlingNote - as well as the Recoverable Errors and the GUID section.)
When creating a sequential ephemeral node there is an error case in which the create() succeeds on the server but the server crashes before returning the name of the node to the client. When the client reconnects its session is still valid and, thus, the node is not removed. The implication is that it is difficult for the client to know if its node was created or not.
With this scheme, ZooLock may become independent of sessions - if the session that created the lock expires, then the ephemeral node goes away and without creating a new lock with a new guid there is no way to proceed.  This moves the issue from needing the session id to watching a particular node via a zk path that is unique for each time the lock is created / acquired.
Another consideration may be that getting the session id is not thread safe. The getLockId() method is synchronized, but may not want to keep repeatedly asking for the session id.
If this seems feasible, I could take a stab and see what it looks like.  Or, I just need to look more and then I would have found out why the is "a bad idea".

Created PR against the 637-validate-lock-acquired branch branch. This new PR modifies ZooLock such that is uses the native ZooKeeper client instead of using ZooReaderWriter.

Created PR against the 637-validate-lock-acquired branch branch. This new PR modifies ZooLock such that is uses the native ZooKeeper client instead of using ZooReaderWriter.


Add get_user_achievement util method

to get all the achievements unlocked by a specific user.

Implemented here:
1a73eaa0cca96d87bcb46902f6202325f54ddff2

nice thx, i'll integrate it if you don't mine ?

Nope, I'm learning how to send you a pull request through github :)

that would be great :)

Cool, I've sent the pull request :D

merged :)

i updated the AUTHORS file too,
thx


Capitalize proper names and edit for clarity

Also added "Some Caveats" section at the end.

Merged as https://github.com/inblockio/micro-PKC/commit/156fe333bcbe0dcb1e14e2e005581acadce2ddab.


Update documentation

I dont know if you still maintain MinePI, but your documentation got something wrong, the render_3d_head function has no argument „display_second_layer“. The second thing is, if I‘m maybe allowed to continue maintaining the library and maybe add some features or something
Greetings, Kejax

Hi, thanks for reaching out. I was doing the obligatory basic military training the past few months and sadly didn't have time/motivation for anything besides that.
So yes, i do plan on maintaining it (at least for now).
Anyway. The project is licensed under MIT which means you are free to do whatever you want with it basically. I have zero problems with you forking it/maintaining your own fork. If you want to submit something to the parent project, feel free to open a PR.
Regards

Okay, thx
Good luck and I hope the basic military training was a success 🙂
Greetings, Kejax!

If you want to try the latest changes, feel free to use the development branch.
Docs are available under https://minepi.readthedocs.io/en/develop/
Bug reports and suggestions are welcome. Feel free to hit me up here or on discord (Benno#8969)

Hi, thanks for your feedback!
Rotating the head vertically would of course be possible but i doubt that'd look decent.
I will give it a try tho!


Added PartialEq implementation for the Client structure.

Hi,
this little patch add PartialEq implementation for the Client structure by just using the already implemented equals function. Implementing PartialEq allow to integrate Client with other standard rust components that rely on that trait.
Thanks for the attention,
Have a good day

The PR needs a cargo fmt, but other than that this is good, thanks!

Yes, i forgot it. Done.


feat: add C implementation for math/base/special/minmax

Resolves #2106 .
Description

This PR contains the C implementation for minmax function

This pull request:

C implementation with benchmarks added in this PR.

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #2106

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@Planeshifter Can you please tell me why minmax.h is unable to locate ?

@AbhijitRaut04 There are some of inconsistencies in your PR. Namely, the STDLIB_MATH_BASE_NAPI_MODULE_D_D macro is specifically for registering a Node-API module that exports a unary function, one that accepts a single double precision input and returns a double precision output.
To see what macros are available for you see: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/math/base/napi
Also, from your lib folder you are missing the native.js file. You are also missing the documentation for the C in the README.
I suggest you go through the similar merged PRs to understand how to implement the C functionality, to start see: https://github.com/stdlib-js/stdlib/pull/3031

@headlessNode I have resolved most of the issues. I am little bit confused why lint files are not passing.

@kgryte Please take a review and suggest me changes required.

@headlessNode
@kgryte
@Planeshifter
Can you suggest me the updates in pr so that the above issue will get resolved ?

/stdlib merge

@AbhijitRaut04 This PR needs some updating. See https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/math/base/special/frexp for an example of how to cross from JS to C and back. The difference here will be that minmax is a binary function, not a unary function, but this should be straightforward to accommodate based on the structure of frexp.

For the C API, we don't need stride and offset. Just provide an *out pointer and assume that the user has provided a two element array.

@kgryte Please take a look and suggest me what should be the changes made for passing lint javascript files ?


Support RFC 3253 (Versioning Extensions)

RFC 3253 seems to be largely concerned with resource version history, but it looks like there may be some things in there that are more generally applicable.

For the read-only operation, as what we have here ATM, what versioning aspects besides providing ETAGs (for files only or also for collections/folders where available) are "in play"?

@yarikoptic

For what's currently implemented, the only things that could be viewed as versioning-related are etags and "modified" timestamps.

As regards RFC 3253, I haven't looked at all of it yet (that's part of this issue), but it seems to define some WebDAV features that dandidav could support even without actual versioning, like a <DAV:supported-live-property-set> element (though, looking further into this at the moment, it seems that particular example is only allowed if versioning is fully supported).


Reapply popups' win_options on layout update

Assume I have a layout that contains a popup for which win_options.number = true is set (or a similar window option). These options are set for the window on Popupp:_open_window(). But if the layout with the popup is visible and i call layout:update(…) (the updated layout still containing the same popup with the number option set), the numbering is lost. I would expect the win_options to be conserved during such an update. As a simple workaround, one can call layout:hide() before and layout:show() after the layout:update(…).
The behavior is probably due to the layout update eventually calling vim.api.nvim_win_set_config for the popup, which by default sets the window style to minimal. This clears things like the number option. It seems one should reapply the window options via a call to _.set_win_options(self.winid, info.win_options) after the call to vim.api.nvim_win_set_config in:
https://github.com/MunifTanjim/nui.nvim/blob/4eaec2ac66af2ca6ddddd3f665ad0909b90ae36a/lua/nui/popup/init.lua#L363-L365

Related Upstream Issue: https://github.com/neovim/neovim/issues/20370

Thanks for the quick fix!


How to run ...

Hello,  I would like to ask a question.    src flod    What is the difference between the src directory and the .ipynb file

@giter915 All of the data exploration, training and inference is in the Jupyter Notebook .ipynb file. I put some of the functions inside the separate directory so the notebook is less cluttered. These are imported at the beginning in the Jupyter Notebook .ipynb like this:
from src.utils import RunningAverage, iou_coef
from src.data import SegmentationDataset, get_loaders, get_transforms
from src.train import train
from src.inference import get_batch_predictions, upscale_mask, convert_bool_mask_to_submission
from src.visualizations import visualize_augmentations

You can also check my notebook on Google Colab - https://colab.research.google.com/drive/1ZpusX5_8jv6mvNSe9pwRF0kU9XDCCETN

You can also check my notebook on Google Colab - https://colab.research.google.com/drive/1ZpusX5_8jv6mvNSe9pwRF0kU9XDCCETN
thank you very much!  thanks!


ModalNavBar: Add marginLeft to title text if there is no back button.

Before:

After:

I caught that but didn't have the time to fix it.
This a good approach.


Groups are missing while generating the test cases if sub-group is same in multiple groups

Area -> Functionality
New Feature - No
Describe the bug -
Version - NO
Expected behavior - Groups are missing while generating the test cases if sub-group is same
Actual behavior - Groups should not missed while generating the test cases  if sub-group is same
How to Reproduce? -
1.Create a multiple group with sub-groups
2.Export the collections
3.Import the collection in new branch
4.Duplicate the groups
5.Delete the copy text
6.Import again the same collection
7.Now we have same sub-group name for multiple groups
8.Generate the test cases
Anything else? - NO

Reason is that duplicate names are not allowed. We restricted the duplicate group name in 3.2.0. That should reolve the issue. For existing issues please rename the groups.


environment variables are not read properly

See below, POSTGRES_USERNAME is set as env var, but soda-core can't read it when using env_var in configuration.yml
soda/demos/sodacl-showcase via 🐍 v3.8.10 (soda-core-38)
➜ echo $POSTGRES_USERNAME
postgres
soda/demos/sodacl-showcase via 🐍 v3.8.10 (soda-core-38)
➜ cat configuration.yml
data_source adventureworks:
  type: postgres
  connection:
    host: localhost
    port: 5433
    username: env_var(POSTGRES_USERNAME)
    password: secret
  database: postgres
  schema: public

soda/demos/sodacl-showcase via 🐍 v3.8.10 (soda-core-38)
➜ soda scan -c configuration.yml -d adventureworks row_count.yml
Soda Core 3.0.0b11
Could not connect to data source "adventureworks": connection to server at "localhost" (::1), port 5433 failed: FATAL:  password authentication failed for user "env_var(POSTGRES_USERNAME)"

  | connection to server at "localhost" (::1), port 5433 failed: FATAL:  password authentication failed for user "env_var(POSTGRES_USERNAME)"

Error occurred while executing scan.
  | dictionary changed size during iteration

SODA-493


expected nil self.account_seed

For some reason my MyMonero destroyed itself. I cant login anymore. Upon logging in

Now after i click ok, im in the programm but my wallet is GONE.
also

And its worse
In the wallet overview, i see no wallet !

in the exchange tab, i see the wallets but with wrong amounts

can you please fix this mess ?

did you delete the entire Monero folder or just certain folders? I had the same problem and lost all my wallets!

Hi @Joeyd348039
The easiest would be to delete the folder itself and restore from keys

Problem is, I forgot to write the keys down. I did it with the 2nd wallet but not the first.
I find it hard to believe that I don't have anything written down at all since you need the phrase in order to complete the wallet.
I still have the wallet files saved though is there anyway to import them or read them somehow?


Jupyterlite Support wanted

It is great for ark to support Jupyterlab.
It seems so far it does not support Jupyterlite (https://github.com/jupyterlite/jupyterlite), a serverless Jupyterlab.
If you support Jupyterlite, some new use cases will appear.
Thanks,

Thank you for the suggestion and pointer. Building to wasm is something that we will consider in the future, but not in the short term.


Adding metadata to traces

#In an internal product we are currently heavily instrumenting various codepaths and we would like to be able to add additional metadata to traces, e.g. sizes of responses, various queries etc. The core zipkin spec allows for that, how do we go about exposing that in this library?
As a sidenote, brave 4.0 was released in January and has fixed a lot of the gripes we had with the library and seems to have added better support for async apps.

Presently it's only possible to change the string operation name. As an alternative, you could cooperatively log (and logs will automatically be labeled with traceId) associated information rather than emit it as part of the same event.
Both Rob and I are subscribed to the "internal traces" issue on Brave's repo, and it's still not resolved.

I think I should've looked at the code first then :P Logging associated information is not ideal, because it will get associated with the server span id, not a local trace, I think, but I suppose it's a start.

The current spanId is available to you, if you want to include it in your log:
Optional<String> spanId = Trace.top().map(OpenSpan::getSpanId);

Ah sorry, that's bogus advice, you'd have to open a span explicitly:
try {
OpenSpan newSpan = Tracer.startSpan("operation");
// now can access: newSpan.getSpanId();
} finally {
    Tracer.completeSpan();
}

...but would be open to adding one of these to Tracer:

Optional<OpenSpan> getCurrentSpan()
Optional<String> getSpanId()

Cool, I can figure out a workaround. Question is, whether we are open to adding something more systematic that will allow me to attach those through the API, not by logging my own messages and how would we go about that.

https://github.com/openzipkin/brave/issues/166 just merged

Fixed in #429


Google Cloud: Error 403: Request had insufficient authentication scopes

We are getting errors on a newly created GKE cluster (same configuration works on older clusters):
time="2019-05-10T17:23:13Z" level=info msg="config: {Master: KubeConfig: RequestTimeout:30s IstioIngressGatewayServices:[istio-system/istio-ingressgateway] Sources:[ingress] Namespace: AnnotationFilter: FQDNTemplate: CombineFQDNAndAnnotation:false IgnoreHostnameAnnotation:false Compatibility: PublishInternal:false PublishHostIP:false ConnectorSourceServer:localhost:8080 Provider:google GoogleProject: DomainFilter:[] ZoneIDFilter:[] AlibabaCloudConfigFile:/etc/kubernetes/alibaba-cloud.json AlibabaCloudZoneType: AWSZoneType: AWSZoneTagFilter:[] AWSAssumeRole: AWSBatchChangeSize:1000 AWSBatchChangeInterval:1s AWSEvaluateTargetHealth:true AWSAPIRetries:3 AzureConfigFile:/etc/kubernetes/azure.json AzureResourceGroup: CloudflareProxied:false CloudflareZonesPerPage:50 RcodezeroTXTEncrypt:false InfobloxGridHost: InfobloxWapiPort:443 InfobloxWapiUsername:admin InfobloxWapiPassword: InfobloxWapiVersion:2.3.1 InfobloxSSLVerify:true InfobloxView: DynCustomerName: DynUsername: DynPassword: DynMinTTLSeconds:0 OCIConfigFile:/etc/kubernetes/oci.yaml InMemoryZones:[] PDNSServer:http://localhost:8081 PDNSAPIKey: PDNSTLSEnabled:false TLSCA: TLSClientCert: TLSClientCertKey: Policy:sync Registry:txt TXTOwnerID:default TXTPrefix: Interval:1m0s Once:false DryRun:false LogFormat:text MetricsAddress::7979 LogLevel:info TXTCacheInterval:0s ExoscaleEndpoint:https://api.exoscale.ch/dns ExoscaleAPIKey: ExoscaleAPISecret: CRDSourceAPIVersion:externaldns.k8s.io/v1alpha1 CRDSourceKind:DNSEndpoint ServiceTypeFilter:[] RFC2136Host: RFC2136Port:0 RFC2136Zone: RFC2136Insecure:false RFC2136TSIGKeyName: RFC2136TSIGSecret: RFC2136TSIGSecretAlg: RFC2136TAXFR:false}"
ERROR: logging before flag.Parse: W0510 17:23:13.197232       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2019-05-10T17:23:13Z" level=info msg="Created Kubernetes client https://<IP_ADDRESS>:443"
time="2019-05-10T17:23:14Z" level=info msg="Google project auto-detected: app-staging"
time="2019-05-10T17:23:14Z" level=error msg="googleapi: Error 403: Forbidden, forbidden"
ERROR: logging before flag.Parse: E0510 17:23:43.214165       1 round_trippers.go:291] CancelRequest not implemented
ERROR: logging before flag.Parse: E0510 17:23:43.214430       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
ERROR: logging before flag.Parse: E0510 17:24:13.215004       1 round_trippers.go:291] CancelRequest not implemented
ERROR: logging before flag.Parse: E0510 17:24:13.215387       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
time="2019-05-10T17:24:14Z" level=error msg="googleapi: Error 403: Forbidden, forbidden"
ERROR: logging before flag.Parse: E0510 17:24:43.216704       1 round_trippers.go:291] CancelRequest not implemented
ERROR: logging before flag.Parse: E0510 17:24:43.217118       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)

This I have tried to do:

Making sure correct service account and service account key is used (with DNS Administrator role) many many times.
Adding both https://www.googleapis.com/auth/devstorage.read_write, https://www.googleapis.com/auth/cloud-platform oAuth scopes to GKE cluster.
Explicitly and implicitly setting google project ID when external-dns is started.
Recreating managed DNS zone.
Making sure dns.googleapis.com is enabled on the project
Updated external-dns to v0.5.13.

Some desperate things I did too:

Adding project/owner permissions to service account used by external-dns;
Adding DNS Administrator to Compute Engine and Kubernetes Engine default service account
Recreating service account and furnishing new key (3 times).
SSH'ed into a container and made sure the correct key is written in file system.
Killing and re-creating external-dns pod/deployment.
Disabling and then re-enabling dns.googleapis.com api.

dns.googleapis.com api metrics show 100% error rate on this call: cloud.dns.api.v1.ManagedZonesService.List.
If I invalidate service account key I get: time="2019-05-10T17:43:57Z" level=error msg="Get https://www.googleapis.com/dns/v1/projects/hammer-staging/managedZones?alt=json&prettyPrint=false: oauth2: cannot fetch token: 400 Bad Request\nResponse: {\n  \"error\": \"invalid_grant\",\n  \"error_description\": \"Invalid JWT Signature.\"\n}", when remove service account I get time="2019-05-10T17:47:18Z" level=error msg="googleapi: Error 401: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.\nMore details:\nReason: authError, Message: Invalid Credentials\n" that tells that request works to some point but then fails.
Maybe you have any other ideas that I should try?

Solved!
I'm laughing. I deleted cloud-dns service account and recreated it as cloud-dns2 with exactly same steps, furnished key for it and it works! Then I did it reverse changes, deleted cloud-dns2 and created a new cloud-dns and it stopped working again. Then I did one more round and created cloud-dns2.
The problem was in the name (for whatever reason).


First pass at the conference landing page

This PR is for a revised landing page for IEEE VR.
The proposed design can be found here: https://www.figma.com/file/kz0G24kuNF3lyaDQQTxVPd/VR2020?node-id=1%3A2

@blairmacintyre the landing page should be pretty much ready to go. I'd like to get that content for the landing page before we merge this.

How about we start with
Welcome to IEEEVR 2020
The Premier International Conference on Virtual Reality and 3D User Interfaces
To join the online experience, you must be registered as a conference attendee, and logged in with the same email you used to register.  Visit the main IEEEVR 2020 Conference to register.  Visit the Online Information page for more information about the online experience, links to join our conference Slack, and an FAQ for the conference and systems we are using.  (Registration information is not immediately synchronized, so don't wait till the last minute to register.)
After signing in, please visit the Tutorial rooms if you are unfamiliar with the Hubs virtual world software. Documentation on the hubs controls for various platforms is available on the Hubs Wiki, along with a wealth of other information that might make your IEEE VR experience using Hubs more enjoyable.

Did you manage to figure out a way to sort the sets of rooms?

Ready to merge & deploy?

@speigg yeah, it should be ready now.


fix: add missing entries

Fixes #1345

Codecov Report

Merging #1346 (822a304) into main (9128953) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1346   +/-   ##
=======================================
  Coverage   48.24%   48.25%
=======================================
  Files         296      296
  Lines       16758    16760    +2
=======================================
+ Hits         8085     8087    +2
  Misses       8673     8673

Impacted Files
Coverage Δ

lnbits/settings.py
85.55% <100.00%> (+0.16%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Mistake in documentation at npmjs

README on npmjs is not in sync with github:
https://www.npmjs.com/package/healthcheck-ping
It suggests to require module like this:
var createHealthcheckMiddleware = require('healthcheck-middleware');
This throw that module was not found. It has to be changed to:
var createHealthcheckMiddleware = require('healthcheck-ping');

This was fixed in dde91207f46bb88935efc3338baab4bdaed7fa4e


Synthetic time series generator

Create a module to generate synthetic time series.
See also aurora issue 97
2014 publication (Neukirch, Maik, and Xavier García. "Nonstationary magnetotelluric data processing with instantaneous parameter." Journal of Geophysical Research: Solid Earth 119.3 (2014): 1634-1654.) is a reference for this work.  Also, the Matlab scripts are available, however, the E, H fields are related by the TF, but do not, in that example, appear to be pinned to the Grand Spectrum.
Note that a recent article showing the updated Grand Spectrum is available in Constable & Constable 2023.

They include a digital archive with the following:

Start Quoted Text from https://marineemlab.ucsd.edu/steve/projects/GrandSpectrum/index.html

**Download the pdf image: grandspectrum.pdf (276 kB)

Download the zipped data: GSpectrum.zip (37 MB) (recommended)
Download the ascii data: GSpectrum.dat (291 MB) (not recommended - might open the 291 MB file in a new window)
There are 5 columns in the digital file:
Frequency in Hz
Power spectral estimate in nT^2/Hz
One standard error estimate of the spectrum in nT^2/Hz
Frequency resolution in Hz
Number of sine tapers used
Coming soon: The time series and power spectrum code.**

End Quoted Text from https://marineemlab.ucsd.edu/steve/projects/GrandSpectrum/index.html

TODO:

[ ] Unpack the grans spectrum and plot it in the ipynb on branch fix_issue_262


Update MIME types

Deleted the charset parameter from application/json because the default encoding for JSON, or the only one that’s allowed, is UTF-8 and there’s actually no that parameter defined for the MIME type.
Added the charset parameter to image/svg+xml because it has no such default charset.
Added the following formats to the list:

the RSS and Atom feed
web app manifest
AV1 image format (AVIF) and animated PNG (APNG), both having some browser support.

Thanks! 👍