Removed ArtifactWrappers from experiments

Purpose

remove dependence on ArtifactWrappers from ClimaLand experiments
fix broke Vaira ranch site link
remove duplicate experiment from buildkite (soil evaporation is now in the docs as a tutorial)

To-do
Future PR (ClimaArtifacts) - add these files to ClimaArtifacts
Future PR (ClimaLand) - update the functions in src/Artifacts.jl
Content
as noted in PURPOSE
Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[x] I have read and checked the items on the review checklist.

Note that we cant run locally, because the era5 artifact is not available for download:
ERROR: LoadError: The following 1 direct dependency failed to precompile:

ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532]

Failed to precompile ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532] to "/Users/katherinedeck/.julia/compiled/v1.10/ClimaLand/jl_3eY3ez".
ERROR: LoadError: Cannot locate artifact 'era5_land_forcing_data2021' for x86_64-apple-darwin-libgfortran5-cxx11-julia_version+1.10.3 in '/Users/katherinedeck/Desktop/code/ClimaLand.jl/src/Artifacts.toml'
Stacktrace:

Note that we cant run locally, because the era5 artifact is not available for download:
ERROR: LoadError: The following 1 direct dependency failed to precompile:

ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532]

Failed to precompile ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532] to "/Users/katherinedeck/.julia/compiled/v1.10/ClimaLand/jl_3eY3ez".
ERROR: LoadError: Cannot locate artifact 'era5_land_forcing_data2021' for x86_64-apple-darwin-libgfortran5-cxx11-julia_version+1.10.3 in '/Users/katherinedeck/Desktop/code/ClimaLand.jl/src/Artifacts.toml'
Stacktrace:

Yes, you have to obtain it independently and write your own Overrides.toml

Note that we cant run locally, because the era5 artifact is not available for download:
ERROR: LoadError: The following 1 direct dependency failed to precompile:

ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532]

Failed to precompile ClimaLand [08f4d4ce-cf43-44bb-ad95-9d2d5f413532] to "/Users/katherinedeck/.julia/compiled/v1.10/ClimaLand/jl_3eY3ez".
ERROR: LoadError: Cannot locate artifact 'era5_land_forcing_data2021' for x86_64-apple-darwin-libgfortran5-cxx11-julia_version+1.10.3 in '/Users/katherinedeck/Desktop/code/ClimaLand.jl/src/Artifacts.toml'
Stacktrace:

Yes, you have to obtain it independently and write your own Overrides.toml

hmmm but how will someone who just clones ClimaLand know this? they wont be able to compile ClimaLand without it. I dont think right now that file is even on box (?)


📝 Update performance claims in docs

Use TechEmpower round 21 link for performance reference.  Refer to #5259 for detailed description.
Closes: #5259

@tiangolo Any issues/comments about this PR?

@tiangolo Thanks for the update, anything else needs to be done to merge this?

@tiangolo Please kindly let me know if you have no intention to merge this so I can stop updating it and close this MR.

Closing as the author seems has no intention to merge it and did not reply any of my comments.


R2 export link seems brokern

Hi,
I get a 404 when trying to get https://pub-f4b5a1306ebd42a3b1289ab59da1d9bf.r2.dev/manifest.json

Hi
The database with the new v1 schema is still in the making. We'll announce when these new exports are publicly available.
In the meantime you can play around with Souricfy's exports. It's based on the VerA schema
https://docs.sourcify.dev/docs/repository/sourcify-database/


[Cortx Hackathon 2021 Integration] Cookiecutter-Django-CORTX

Describe your changes in brief
Created an integration for the CORTX Hackathon 2021 in Singapore. It is an integration with Cookiecutter and Django, enabling anyone to quickstart a full stack project automatically integrated with CORTX in under 2 minutes. See doc/integrations/django/README.md.
Changes

[ ] Why is this change required? What problem does it solve?
[ ] If proposing a new change then please raise an issue first

How Has This Been Tested? (Optional)

[ ] Please describe in detail how you tested your changes.
[ ] Include details of your testing environment, and the tests you ran to
[ ] How your change affects other areas of the code, etc.

Screenshots (if appropriate)
Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

View rendered doc/integrations/django/README.md

Hi @calvinyanghwa
Thanks for the PR as part of the CORTX Hackathon :+1:
Notice your PR is missing a DCO ( https://github.com/Seagate/cortx/blob/main/doc/dco_cla.md ) and can't be accepted to CORTX without it ( https://github.com/Seagate/cortx/blob/main/CONTRIBUTING.md#contribution-process ).
Please sign your commits so that the DCO test can pass.


⚠ Doshipui has degraded performance

In a7d0c82, Doshipui (https://дошипуй.рф/) experienced degraded performance:

HTTP code: 200
Response time: 15107 ms

Resolved: Doshipui performance has improved in c676489 after 8 minutes.


Disabling VBO for Intel OpenGL drivers is not relevant anymore

In file gl.cpp.
In lines 1336 to 1352.
There is conditional code, disabling by default, VBO for Intel OpenGL driver.

=> Theses lines should be removed, as this problem is not relevant anymore.
This unnecessarily penalizes Intel graphics card users.
(Tested on Intel Graphics HD 4000)

Thanks for contributing to Coin, Yves. As always your contribution is highly appreciated.


blurred screen

Why is the screen flickering ten seconds before the 5.1 version is played

This version is outdated, we are working on production release of vlc plugin.

Will the new release be compatible with UE5.1/5.2?


Update the popup window that appears when deleting a super-event to state that all sub-events linked to the super event will also be deleted by this action.

Use isSuperEvent flag.
Use https://github.com/rokwire/events-manager/pull/793 as reference.

can you refer to https://github.com/rokwire/events-manager/pull/793?


Update fs-extra to version 10.0.0

This pull request was created using the JSFIX tool (https://jsfix.live) by Coana.tech (https://coana.tech).
The JSFIX run was completed by mR4smussen.
It bumps fs-extra to version 10.0.0.
Sign up your project here to receive notifications about other packages updates JSFIX can help with.

 Pull request details
 🚧 - Manual review items (please check before merge)
Breaking changes not automatically fixable by JSFIX.

General breaking changes (not related to specific API usages in your code).

Require Node.js v12+

The following breaking changes must be patched manually.

Allow copying broken symlinks

src/srcmak.ts#L20-L20

The following breaking changes are unlikely to affect your code. Below each bullet is listed the dependency usages detected by JSFIX that may be affected by the breaking change.

Error when attempting to copy*() unknown file type
Suggested fix: This is only relevant if dir may refer to a socket, a FIFO pipe or some other file type not recognized by the fs module.

src/compile.ts#L46-L46
Suggested fix: This is only relevant if srcdir may refer to a socket, a FIFO pipe or some other file type not recognized by the fs module.
src/srcmak.ts#L20-L20
Suggested fix: This is only relevant if path.join(workdir, '.jsii') may refer to a socket, a FIFO pipe or some other file type not recognized by the fs module.
src/srcmak.ts#L27-L27

Additional details
Breaking changes where JSFIX found that there were no occurrences.

Ensure correct type when destination exists for ensureLink*()/ensureSymlink*()
Remove undocumented options for remove*()

If you would like to provide feedback to the JSFIX developers, then please leave a comment on this pull request.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

jsfix.live analysis seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.


https://github.com/discountry/react/blob/master/content/blog/2017-12-07-introducing-the-react-rfc-process.md

认领~


Use designated labels in proposals to link to related issues & pull requests

PR #1868 introduces a new workflow for proposals. As described in my comment on that PR, I think proposals should evolve through discussion in multiple related issues and pull requests.
To manage this evolution more easily I suggest we create a designated GitHub label for each draft proposal. Apply that label to relevant issues and PRs. Specify that label towards the top of the draft proposal, followed by two links:

Open issues related to the draft proposal (filtered by label)
Open pull requests related to the draft proposal (filtered by label)

We now seem to have an approach to this. A small group of community members has labeling privileges, so we can manage this. I'll go back to my proposal and put this to use now. Assuming it works nicely, I'll also submit a PR to update the proposal template.

@tedepstein what changes to the proposals template did you have in mind?

@MikeRalphson , this would be easier to illustrate if I could show an example, but that requires creating a new label. I can only apply labels, not create them. Could you create a new label called "Proposal: clarify-nullable" so I can show how this would work?

@MikeRalphson , to answer your question directly, I would suggest modifying the proposal template as shown here:
https://github.com/tedepstein/OpenAPI-Specification/commit/ecf1ee95c5649a7e206bd2a22c605f9141a3f4ea

Looks good to me.

@lornajane recently updated the proposals documentation -if there is still something needed here, please open an issue based on the current state of things.


Update slide.component.ts

Small API Ref description improvements

Current coverage is 84.14% (diff: 100%)

Merging #1381 into development will not change coverage

@@           development      #1381   diff @@
=============================================
  Files               73         73
  Lines             1961       1961
  Methods             17         17
  Messages             0          0
  Branches           262        262
=============================================
  Hits              1650       1650
  Misses             214        214
  Partials            97         97

Powered by Codecov. Last update a688e6a...f0ff0fb


Allow directly recursive maps and arrays in Schema

{
  "$ref": "#/definitions/Foo",
  "definitions": {
    "Foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "#/definitions/Bar"
        }
      },
      "title": "Foo"
    },
    "Bar": {
      "type": "object",
      "additionalProperties": {
        "$ref": "#/definitions/Bar"
      }
    }
  }
}

The main problem at this point is making the renderers output these types.

Did you manage to fix this?

After changing $ref to point to a specific file, it is working now.

@gintsmurans The bug here is the type Bar that refers to itself.  This hasn't been fixed yet.

Here you go: https://ip.gm.lv/Castle.zip
Command I am using: /usr/bin/env quicktype -s schema --telemetry disable --no-initializers --type-prefix Api --density normal -o ./Castle/Sources/Models.swift ./Castle/Schemas/TestComplexArray ./Castle/Schemas/VerifyUserRequestType ./Castle/Schemas/GetPasswordResetTokenRequestType ./Castle/Schemas/CreateUserRequestType ./Castle/Schemas/ResetPasswordRequestType ./Castle/Schemas/ChangePasswordRequestType ./Castle/Schemas/JSONMyTriggeredEventDetails ./Castle/Schemas/LogInRequestType ./Castle/Schemas/JSONSubscription ./Castle/Schemas/JSONMyTriggeredEvent ./Castle/Schemas/JSONEvent ./Castle/Schemas/JSONSession ./Castle/Schemas/JSONUser
I tried multiple ways, one, for example, was to specify Schemas directory as input, but if I do, it wouldn't recognize files as Schema files, regardless of -s schema.
Then if I append .json extension to the filenames, it would append JSON to struct names.
And If I would specify $ref to the full id of the object (in example they are trimmed down for it to work), it would not find that object, so this was the only way I could find that is working as expected.
Btw, the project is really useful, thanks for working on it.


BSOD for windows 10.0.16299.371

ntoskrnl.exe version number is 10.0.16299.371
After starting exe and clicking load, the blue screen is uploaded, and the dump file has been uploaded.
041518-4015-01.zip

Solved, synchronizing upstream updates,大力么么哒,还是国语说起来爽的一批
https://github.com/tandasat/HyperPlatform/commit/be1f59abb715d32b0dac3e471d0ec4337b9709cd


NLog 4.4.12, new Logger("name"), and README additions

Update

nuget package updated to NLog 4.4.12
nuspec and assembly versions reflect change to 4.4.12
adds some basic help for visitors (quickstart, links for formatted text & nlog config)

Adds

Logger constructor accepts (name:string) as well

Hi @j-alexander ,
sorry, I've been away for a while. Thank you for you PR :). I will publish updated package soon.

Awesome, thank you!

Hi @Ravadre - is everything okay with the latest version?  Can I help in any way?

Hello @j-alexander , sorry, totally forgot about pushing it to Nuget repo :(. Updated version to 4.5.3 and pushed newest package to Nuget.org

It's much appreciated, sir!  Thank you.


Show appropriate error message when extension gallery service is not accessible

What does this PR do?
Update the query method to return the error thrown by the this.extensionsWorkbenchService.queryGallery
What issues does this PR fix or reference?
Microsoft/vscode#55723

@ramya-rao-a thanks for the review.
I think I got the wrong point for this problem.
And you are right. Thank you to point that.
const pager = await this.extensionsWorkbenchService.queryGallery(options);
		return new PagedModel(pager);

This code always returned a valid paged model.
So convert all await to normal promise in query when we await queryGallery.
Am I right?
I will fix it as soon as I can.
BTW my English is not very good. if something I got wrong, plz tell me, thank!

So convert all await to normal promise in query when we await queryGallery.
Am I right?

Yes

@aps32221 There was another PR #56767 that fixed the issue, so I'll be closing this PR.
Feel free to look for other issues that are marked as "help-wanted" to contribute.
Thanks again


Error: [Configuration system failed to initialize]

Describe the bug
Update watcher won't launch
I'm sure that it's not a 'known-not-a-bug'
Check https://github.com/tushev/aojdk-updatewatcher/wiki/Known-not-a-bugs
[X] Yes
To Reproduce
Steps to reproduce the behavior:

Launch either an update check or the configuration

Expected behavior
Successful update check
Screenshots

Desktop (please complete the following information):

App Version 2.0.4
Windows Version Windows 11 22H2
JDKs/JREs Temurin 17.0.7+7

Additional context
Tried a fresh install of updatewatcher with the same result

Hello,
try deleting the following file: %USERPROFILE%\AppData\Local\tushev.org\AJUpdateWatcher.exe_Url_SOME_RANDOM_STRING\<IP_ADDRESS>\user.config

Seems to have worked. Thanks for the help!


Update accesskit to 0.17

Updates accesskit and kittest.

[x] I have followed the instructions in the PR template

@mwcampbell the update was straightforward, but maybe you can review this in case I missed anything?
Especially around the set_default_action_verb, I just removed those calls but am not 100% sure if I need to do anything else there.

I see you dropped two calls to set_default_action_verb:

builder.set_default_action_verb(accesskit::DefaultActionVerb::Focus);: This one is no longer necessary.
builder.set_default_action_verb(accesskit::DefaultActionVerb::Click);: The if statement surrounding this needs to be re-added, but replace this statement with: builder.add_action(accesskit::Action::Click);.

The other problem is with the part where you use builder.set_label. If the role of the new node is Role::Label, you need to use builder.set_value instead.

@mwcampbell thank you for the review, I've updated the PR accordingly!

Just checking: are you waiting on something else from me before merging? Thanks.


urlRouter's sync method needs better/updated documentation and possibly fixed

this code does nothing, far as I can tell.  Even though I'm explicitly setting meetsRequirements to false, nothing is blocked and my next state loads.
I've done a ton of SO research and there are multiple posts regarding this method and how "broken" it is.
The confusion stems from it's use of $locationChangeSuccess instead of a $stateXXXX event and the fact that it just doesn't seem to work at all, as the code block below shows.
At minimum, it seems like having this documentation out there is counter productive.
// straight from http://angular-ui.github.io/ui-router/site/#/api/ui.router.router.$urlRouter
// in my .run function......
$rootScope.$on('$locationChangeSuccess', function(evt) {
            // Halt state change from even starting
            evt.preventDefault();
            // Perform custom logic
            var meetsRequirement = false;
            // Continue with the update and state transition if logic allows...which *should* never happen
            if(meetsRequirement) $urlRouter.sync();
        });

http://stackoverflow.com/questions/22537311/angular-ui-router-login-authentication
The solutions posted so far are needlessly complicated, in my opinion. There's a simpler way. The documentation of ui-router says listen to $locationChangeSuccess and use $urlRouter.sync() to check a state transition, halt it, or resume it. But even that actually doesn't work.

See https://angular-ui.github.io/ui-router/site/#/api/ui.router.router.$urlRouterProvider#methods_deferintercept


Switch policy to use RFC3986-compliant predicate type

Fixes: Now that we are attesting vuln scans with cosign 2.0, the policy is invalid since predicate types must now be RFC3986-compliant (start with https://)
Related: https://github.com/sigstore/policy-controller/issues/608
Pre-review Checklist

[ ] IMPORTANT: 'image-request' tag has been applied if this PR is adding any images, including new versions or variants

For new image PRs only
If you have an apko.yaml file in this PR you need to follow this checklist, otherwise feel free to remove.

[ ]  Image is marked experimental or stable as appropriate

[ ]  The last two minor versions are available

[ ]  The latest tag points to the newest stable version

[ ]  There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')

[ ]  The image runs as nonroot and GID/UID are set to 65532

[ ]  Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
[ ]  See above for exceptions to nonroot rule

[ ]  ENTRYPOINT

[ ]  For applications/servers/utilities call main program with no arguments e.g. [redis-server]
[ ]  For base images leave empty
[ ]  For dev variants set to entrypoint script that falls back to system

[ ]  CMD:

[ ]  For server applications give arguments to start in daemon mode (may be empty)
[ ]  For utilities/tooling bring up help e.g. –help
[ ]  For base images with a shell, call it e.g. [/bin/sh]

[ ]  Consider where and how the image deviates from popular alternatives. Is there a good reason and is it documented?

[ ]  Add annotations e.g:
  annotations:
    "org.opencontainers.image.authors": "Chainguard Team https://www.chainguard.dev/"
    "org.opencontainers.image.url": https://edu.chainguard.dev/chainguard/chainguard-images/reference/busybox/ #use the academy site here
    "org.opencontainers.image.source": https://github.com/chainguard-images/images/tree/main/images/bazel #use github here

[ ]  Check if environment variables are needed e.g. to set data locations

[ ]  Ensure the image responds to SIGTERM

[ ]   docker kill $(docker run -d --rm cgr.dev/chainguard/nginx)

[ ]  Documentation. Let's make this excellent. Include usage example.

[ ]  Error logs write to stderr and normal logs to stdout. DO NOT write to file.

[ ]  Include tests, at the very least a basic smoke test.

Ok, seems like the original error has been fixed, but this one is the one that failed now?
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +668bd6305358c8f9472000b99bacc00e5ce9beac:refs/remotes/pull/325/merge
  Error: fatal: unable to access 'https://github.com/chainguard-images/images/': The requested URL returned error: 429
  The process '/usr/bin/git' failed with exit code 128
  Waiting 16 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +668bd6305358c8f9[47](https://github.com/chainguard-images/images/actions/runs/4346621087/jobs/7592919798#step:2:52)2000b99bacc00e5ce9beac:refs/remotes/pull/325/merge
  Error: fatal: unable to access 'https://github.com/chainguard-images/images/': The requested URL returned error: 429
  The process '/usr/bin/git' failed with exit code 128
  Waiting 13 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +668bd6305358c8f9472000b99bacc00e5ce9beac:refs/remotes/pull/325/merge
  Error: fatal: unable to access 'https://github.com/chainguard-images/images/': The requested URL returned error: 429
  Error: The process '/usr/bin/git' failed with exit code 128

yea, thats just github actions spurious errors. re-running


Null coalescing operator makes yoda_style rule to fail

Bug report
For code like this: (($_SERVER['HTTP_HEADER'] ?? '') === 'test') yoda_style rule does nothing.
I think the code above should be changed to ('test' === ($_SERVER['HTTP_HEADER'] ?? '')).
PHP 7.3.21-1+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Aug  7 2020 14:44:10) ( NTS )
PHP CS Fixer 2.16.4 Yellow Bird by Fabien Potencier and Dariusz Ruminski (1023c34)
php-cs-fixer fix --verbose --diff --config ".php_cs.dist"

<?php

$finder = PhpCsFixer\Finder::create()
    ->in(__DIR__ . DIRECTORY_SEPARATOR . 'src')
    ->notPath('Kernel.php')
    ->in(__DIR__ . DIRECTORY_SEPARATOR . 'public')
    ->notPath('index.php')
;

return PhpCsFixer\Config::create()
    ->setRiskyAllowed(true)
    ->setRules([
        '@PSR2' => true,
        '@Symfony' => true,
        '@PhpCsFixer' => true,
        'declare_strict_types' => true,
        'concat_space' => ['spacing' => 'one'],
        'ordered_class_elements' => false,
        'phpdoc_add_missing_param_annotation' => false,
        'binary_operator_spaces' => [
            'default' => 'single_space',
            'operators' => [
                '=>' => null,
                '=' => null,
            ],
        ],
        'phpdoc_to_comment' => false, // breaks @var on return statements
    ])
    ->setFinder($finder)
;

Code snippet that reproduces the problem
<?php

if (($_SERVER['HTTP_X_HEADER'] ?? '') !== 'something') {
  return;
}

Yoda conditions are intended to avoid accidental assignments when comparing a variable.  The left side of your example condition is comparing the value of the conditional expression ($_SERVER['HTTP_X_HEADER'] ?? ''), which is not considered a variable.  You can verify this by trying to assign 'something' to the conditional expression:
// The bad thing you're trying to avoid
($_SERVER['HTTP_X_HEADER'] ?? '') = 'something'

You will receive the error: Parse error: syntax error, unexpected '='
Yoda conditions increase the cognitive load of reading code, so it's better not to use them if you don't need to protect from accidental variable assignment or unsafe null behavior.  Your use of the null-coalescing operator is a good example of safe null behavior. :)
If you're curious, this is where YodaStyleFixer determines if the left and ride side of a comparison are eligible to be swapped.
Recommend wontfix tag on this, but this was a good test case to bring up!

Thanks for reporting @fluffycondor , and thanks for the detailed response @hamdrew !
I think your report is valid, as we fix the form ($a === 1) we should/could also fix (($a) === 1) IMHO.
There is a lot to say about Yoda or not Yoda and since we found ourselves so divided we offer it all :D you can fix to Yoda, fix to not-Yoda or configure to allow both (i.e. don't touch).


Exporters shutdown() could return a promise

Is your feature request related to a problem? Please describe.
I would like to know when exporters, like jaeger, are done flushing after a shutdown(). Currently, the shutdown method returns nothing, and there's no way to effectively know when the shutdown finished (flushed + closed connection).
Describe the solution you'd like
In Node.js is quite hard to implement a synchronous shutdown() method. One way would be for it to return a promise that fulfils when the shutdown is done (flushed + closed connection)..
Describe alternatives you've considered
N/A.
Additional context
N/A.

I think this is a good idea and it seems like the spec allows for it. Would you like to make the PR or should I mark this as up for grabs?

@dyladan I was looking at the code, and found this: https://github.com/open-telemetry/opentelemetry-js/blob/master/packages/opentelemetry-exporter-prometheus/src/prometheus.ts#L112
It seems that the prometheus exporter uses callbacks. I would prefer to use promises as we can leverage async await more easily.
Can we agree on shutdown() => Promise for all exporters?

I am ok with it but I'd like to get @mayurkale22 opinion

SGTM

@satazor I am going to assign this issue to you. Let me know if that doesn't work for you or if you have any questions.

@dyladan alright, I'm going to try and find some time to do this. Do you expect a PR on all packages or can I do them separately?

There are only a small number of packages so I would say it can be done all in a single PR. If you do attempt to split it into multiple PRs, take note that we will not merge any PRs that break the build. Updating the interface but not the classes will break the build.

Closing as both SpanExporter.shutdown and PushMetricExporter.shutdown returns a promise now.


Issue-479-1: UI enhancements to handle runAll / runUpto using JavaFX Service/Task

Description
Patch to fix the pending item from https://github.com/intuit/karate/issues/425#issuecomment-408737943

Currently the threading model needs work, the status of step execution reflects only at the end of ALL steps. needs to be fixed

We were invoking runAll() / runUpto() in the Java FX Application thread, which was causing varPanel / logPanel updates to be taken up only after all steps are executed.  Introduced RunService to offload these (runAll/runUpto) and free Java FX Application thread.
Also added a unit test case (not sure of what happens when running tests on a headless / no-display system).  It ran fine in my local setup, will wait for the test results and then may be remove the newly added test.

Relevant Issues : https://github.com/intuit/karate/issues/479
Relevant PRs : https://github.com/intuit/karate/pull/480
Type of change :

[ ] New feature
[x] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

As expected, am seeing
Running com.intuit.karate.ui.ThreadTest
Exception in thread "Thread-1" java.lang.UnsupportedOperationException: Unable to open DISPLAY
Let me remove disable the newly added unit test (ThreadTest.java)

this is really great work, thanks ! I'll rename the test to be a little more convenient to run in the IDE


Setup Configuration ⚙

Allow user configuration
This is a https://github.com/Shresht7/vscsv/labels/priority as a lot of features depend on a configurable delimiter.

Honestly, there is no need to pre-emptively make it more complex than it needs to be. vscode.workspace.getConfiguration should do the job just file.


Dead code in allauth_ui.py

I think this is not used anywhere :thinking:
https://github.com/danihodovic/django-allauth-ui/blob/3fb6a49828e567c466f2ef1ceed3d6dc2a8a3423/allauth_ui/templatetags/allauth_ui.py#L9-L13

https://github.com/danihodovic/django-allauth-ui/pull/14


Create nut.yml

The problem was that code returned immediately, and the the container was closed even before sending request to server X.
The trick was to add the -w flag when calling code:
-w, --wait            Wait for the window to be closed before returning.

Big thanks for figuring out the -w switch! I was so confused why that wasn't working. How is nut doing the X11 communication?

TL;DR : it tells the container to open windows on the mac, and it mimics socat to make it possible
Long version:

it modifies $DISPLAY environment variable of the container so that it connect to X11 server of the mac
it connects to X11 unix socket of the Mac
listen on port 6000 of the Mac (default remote port for X11)
if it receives a connection from the VM on port 6000, then it forwards communication from/to X11 UNIX socket of the mac.

On Linux it is easier: nut simply mounts X11 UNIX socket in the container.


Allow stream to connect to a ditch

Right now a stream ends when connected to a ditch. I'd like to see the watershed area include ditches. BTW - I'm in an area next to the ocean that many of the small streams, often from mountains, connect to irrigation ditches before hitting the ocean.

As a first step, I calculated how many loops in waterway=ditch there are. The OSM wiki says ditches should be mapped in direction of waterflow, but I've always suspected that wasn't often done.
There are 28,000 loops in just waterway=ditch alone. If you want to look at the data, the 35 MiB geopackage file can be downloaded from https://data.waterwaymap.org/2024-08-planet-waterway-ditch-loops.gpkg.
The existance of loops shouldn't mean that
The geojsons was created with this osm-lump-ways command:
osm-lump-ways-down -i planet.osm.pbf -f waterway=ditch --loops ditch-loops.geojsons

There is a small number in the area around here. One was mistagged as a waterway=ditch + water=pond. It should have been natural=water + water=pond. I'm going to investigate the ones in the farmland near me to see if I can figure out if they are loops or not.


Fix output of special chars in /dexsearch, /movesearch and /itemsearch

You need to be more specific than "fix".

I hope that's specific enough, primary it fixes cases like bst < 600 and something like that


Breaking change: allow lower case type names except return type name of method declaration

Coverage increased (+0.1%) to 78.025% when pulling 242a668c3620d1b734cc6a393f4df5a4d6a2ca4c on breakingChanges into 31ccba5fb12e0f0b77fec845c60ed4475c8f1f16 on master.


Inconsistent with default Mx input widgets

This widget is inconsistent with standard Mendix input widgets. It offers no way of adding a label, nor does it handle validation feedback.

Hi Jelle,
Indeed, labels are not supported at the moment, in the future we might add it.
At the moment there is no way to provide labels in the same way as the core widgets, with the same exact behavior.
For now, you could create a text and use it as labels.
The missing validation is deed an issue.  We will add it to our sprint backlog.
Thanks for your feedback,
Andries


Add Dockerfile and docker-compose

Thanks Mohab, can you update the readme with instructions so it is easy for other people to get started?

Done


fix(a11y): making image captions their alt text

Fixes RM-1562

🧰 Changes

if a caption is provided for an image, but no alt text, use the caption text to populate the alt text for an image
we'll want to revisit this at some point and add proper alt text support to avoid potentially repeating alt text and caption text

🧬 QA & Testing

Does alt text appear now for images that have captions?

Broken on production.

Working in this PR app.

Updated the description some for ya! 👍

This PR was released!
🚀 Changes included in v6.30.2-next.1

This PR was released!
🚀 Changes included in v6.30.2


Explicitly fail on Keras3

This PR makes the helpers save_pretrained_keras and load_pretrained_keras explicitly fail if called with Keras 3 installed. The Keras x HF integration implemented in huggingface_hub is outdated and therefore not suitable for Keras 3 models. At least 2 parts broke with the Keras 2 -> 3 migration:

load model expects a file path instead of a folder path (as reported in https://github.com/huggingface/huggingface_hub/pull/2104 by @ZhanPascal)
model.history doesn't exist anymore (fails when saving model)

For the record, Tensorflow 2.16 has been release last week (7th March 2024) and introduces the breaking change of making Keras3 the default keras version. This makes our tests fail in the CI so I've pinned the versions to install TF2.15 and Keras2 when running the tests.
Of course,  this PR is a temporary fix to explicitly fail on version incompatibilities but the goal is to foster the Keras x HF integration even further.  Official support for Keras3 models is the objective.
Ping @Rocketknight1 as well for Keras discussions.

In the meantime, the integration can be handled like this:
# instead of 'save_pretrained_keras' / 'push_to_hub_keras'
import tensorflow as tf
from huggingface_hub import upload_folder

tf.keras.models.save_model(model, save_directory)
upload_folder(save_directory)

# instead of 'from_pretrained_keras'
import tensorflow as tf
from huggingface_hub import hf_hub_download

path = hf_hub_download("<repo_id_on_the_hub>", filename="model.keras")  # adapt repo_id and filename
model = tf.keras.models.load_model(path)

Those 2 workarounds don't include semi-automatic model cards or saving model history but should do the trick for most use cases.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Codecov Report
Attention: Patch coverage is 61.90476% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 82.87%. Comparing base (0453ae9) to head (186dd2c).

Files
Patch %
Lines

src/huggingface_hub/utils/_runtime.py
50.00%
8 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2107      +/-   ##
==========================================
- Coverage   82.94%   82.87%   -0.07%
==========================================
  Files         102      102
  Lines        9540     9560      +20
==========================================
+ Hits         7913     7923      +10
- Misses       1627     1637      +10

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

FYI @merveenoyan who worked in the initial implementation

LGTM! One comment is that TF has a compatibility package tf-keras, to allow you to use the Keras 2 API with TF >= 2.16. As a result, you might want to change the check so that it doesn't fail in cases when Keras 3 is installed, but the user is using tf-keras. See the section of the release notes here that starts with "To continue using Keras 2.0"

It might be easier to check for methods/attributes on the model itself? Several of those changed name with Keras 3.

@Rocketknight1 I've slightly updated the PR. Now behavior is:

when loading keras model, check for either tf_keras or tf.keras
when saving keras model, check if model is in keras 3 (hackily based on model attributes). If Keras 3 => raise exception.

Should handle cases correctly now, including if keras2 and keras3 are installed at the same time.

Thanks @LysandreJik @Rocketknight1 for the review and confirming the approach is correct. Ready to be merged then :)


sudo make install not finding nvcc

when installing with the GPU=cudanet flag, 'sudo make install' raises the error 'nvcc not found'. It turns out that nvcc is not in the sudo path. I was able to fix this error by following the instructions here:
http://askubuntu.com/questions/428234/nvcc-not-found-but-only-when-using-sudo
Things seem to compile fine after that, however, the AlexNet model example does not work:
neon --gpu cudanet examples/convnet/i1k-alexnet-fp32.yaml
error:
2015-05-30 14:17:09,331 ERROR:imageset - Batch dir cache not found in /home/esteva/data/I1K/imageset_batches/dataset_cache.pkl:
Press Y to create, otherwise exit: Y
Traceback (most recent call last):
File "/usr/local/bin/neon", line 240, in
experiment, result, status = main()
File "/usr/local/bin/neon", line 208, in main
result = experiment.run()
File "/usr/local/lib/python2.7/dist-packages/neon/experiments/fit_predict_err.py", line 99, in run
super(FitPredictErrorExperiment, self).run()
File "/usr/local/lib/python2.7/dist-packages/neon/experiments/fit.py", line 73, in run
self.dataset.load(backend=self.backend, experiment=self)
File "/usr/local/lib/python2.7/dist-packages/neon/datasets/imageset.py", line 171, in load
from neon.util.batch_writer import (BatchWriter,
File "/usr/local/lib/python2.7/dist-packages/neon/util/batch_writer.py", line 25, in
import imgworker
ImportError: No module named imgworker
Whereas the CPU example does:
neon examples/mlp/mnist-small.yaml

Can you make sure that you've installed the imgworker module as well?
https://github.com/NervanaSystems/imgworker
On Saturday, May 30, 2015, andreesteva<EMAIL_ADDRESS>wrote:

when installing with the GPU=cudanet flag, 'sudo make install' raises the
error 'nvcc not found'. It turns out that nvcc is not in the sudo path. I
was able to fix this error by following the instructions here:
http://askubuntu.com/questions/428234/nvcc-not-found-but-only-when-using-sudo
Things seem to compile fine after that, however, the AlexNet model example
does not work:
neon --gpu cudanet examples/convnet/i1k-alexnet-fp32.yaml
error:
2015-05-30 14:17:09,331 ERROR:imageset - Batch dir cache not found in
/home/esteva/data/I1K/imageset_batches/dataset_cache.pkl:
Press Y to create, otherwise exit: Y
Traceback (most recent call last):
File "/usr/local/bin/neon", line 240, in
experiment, result, status = main()
File "/usr/local/bin/neon", line 208, in main
result = experiment.run()
File
"/usr/local/lib/python2.7/dist-packages/neon/experiments/fit_predict_err.py",
line 99, in run
super(FitPredictErrorExperiment, self).run()
File "/usr/local/lib/python2.7/dist-packages/neon/experiments/fit.py",
line 73, in run
self.dataset.load(backend=self.backend, experiment=self)
File "/usr/local/lib/python2.7/dist-packages/neon/datasets/imageset.py",
line 171, in load
from neon.util.batch_writer import (BatchWriter,
File "/usr/local/lib/python2.7/dist-packages/neon/util/batch_writer.py",
line 25, in
import imgworker
ImportError: No module named imgworker
Whereas the CPU example does:
neon examples/mlp/mnist-small.yaml
—
Reply to this email directly or view it on GitHub
https://github.com/NervanaSystems/nervanagpu/issues/9.


GeoJson parsing fails on the Alpha variant of my app

Summary
GeoJson parsing fails on the Alpha variant of my app
Expected behavior
GeoJson should be parsed and displayed correctly like in the Debug variant
Observed behavior
I observed  that an error log was displayed in the console and my geojson was not rendered
Environment details

Oneplus 8 pro
Android version: 10
Lib version: 2.2.2

Steps to reproduce
If you can reproduce using the demo app in the project, it helps us troubleshoot faster.

?

Code example
# example

Stack trace
Feature could not be successfully parsed {"geometry":{"coordinates":[[[[0,89.99999999],[179.99999999,89.99999999],[179.99999999,-89.99999999],[0,-89.99999999],[-179.99999999,-89.99999999],[-179.99999999,89.99999999],[0,89.99999999]],[[13.326759338378906,52.53804805353589],[13.3209228515625,52.51287794429001],[13.3319091796875,52.5066092844801],[13.330020904541016,52.495427955337256],[13.345298767089844,52.49417379714532],[13.360748291015625,52.49417379714532],[13.376884460449219,52.49166537345018],[13.383407592773438,52.49375573646574],[13.406238555908201,52.489574911070385],[13.421688079833984,52.48643903118845],[13.417911529541014,52.4782846971225],[13.421001434326172,52.46343574667342],[13.43250274658203,52.465213701916504],[13.448982238769531,52.4777619318499],[13.440227508544922,52.482152967102564],[13.451557159423828,52.48863417058138],[13.46426010131836,52.4982496804861],[13.469581604003904,52.5066092844801],[13.479881286621094,52.51632532607162],[13.480052947998047,52.526456973352445],[13.476104736328125,52.533036069990786],[13.471813201904297,52.53167855932515],[13.457908630371092,52.54118025273576],[13.429241180419922,52.551201788517524],[13.42306137084961,52.55276744679156],[13.365554809570312,52.55746408645484],[13.326759338378906,52.53804805353589]],[[13.330535888671875,52.48717075649203],[13.331050872802734,52.485498223625996],[13.34564208984375,52.48528915254611],[13.345470428466797,52.489574911070385],[13.330535888671875,52.48717075649203]]]],"type":"MultiPolygon"},"type":"Feature","properties":{"providerId":"libe","backgroundColorWithOpacity":"#4D001E3E","borderColorWithOpacity":"#ff5e05","borderWidth":4,"type":"BUSINESS_AREA"}}
    Index of Feature in Feature Collection that could not be created: 0
    Feature could not be successfully parsed {"geometry":{"coordinates":[[[[13.416366577148438,52.52729246882668],[13.42031478881836,52.52530814112491],[13.43301773071289,52.53648187013421],[13.424434661865234,52.53909214476578],[13.416366577148438,52.52729246882668]]],[[[13.377227783203125,52.51246006145307],[13.375682830810547,52.517683311303244],[13.371219635009764,52.51799668655011],[13.371219635009764,52.51925016518623],[13.364009857177734,52.518727886767266],[13.350791931152344,52.51517622886228],[13.350791931152344,52.513818166144006],[13.351993560791016,52.50963924836329],[13.364181518554688,52.50995268098114],[13.377227783203125,52.51246006145307]]]],"type":"MultiPolygon"},"type":"Feature","properties":{"providerId":"mean","backgroundColorWithOpacity":"#33ff5e05","borderColorWithOpacity":"#ff5e05","borderWidth":2,"type":"NO_PARKING_AREA"}}
    Index of Feature in Feature Collection that could not be created: 1

Following these steps will guarantee the quickest resolution possible.
Thanks!

Fixed


Turtlebot 4 simulator not compiling from source

Please provide the following information:

OS: Description:	Ubuntu 20.04.5 LTS
ROS Distro: Galactic
Built from source or installed: from source
Package version: c63ffdc

Expected behaviour
I expected to compile the package.
Actual behaviour
This error:
--- stderr: irobot_create_ignition_toolbox
/usr/bin/ld: libirobot_create_ignition_sensors_lib.so: undefined reference to `rosidl_message_type_support_t const* rosidl_typesupport_cpp::get_message_type_support_handle<irobot_create_msgs::msg::Dock_<std::allocator > >()'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/sensors_node.dir/build.make:201: sensors_node] Error 1
make[1]: *** [CMakeFiles/Makefile2:223: CMakeFiles/sensors_node.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
---
Failed   <<< irobot_create_ignition_toolbox [48.1s, exited with code 2]
Aborted  <<< turtlebot4_node [50.0s]
Aborted  <<< irobot_create_nodes [51.4s]
Aborted  <<< irobot_create_gazebo_plugins [1min 13s]
Summary: 12 packages finished [1min 46s]
1 package failed: irobot_create_ignition_toolbox
3 packages aborted: irobot_create_gazebo_plugins irobot_create_nodes turtlebot4_node
2 packages had stderr output: irobot_create_ignition_toolbox turtlebot4_node
7 packages not processed
To Reproduce
I followed the steps shown here: https://turtlebot.github.io/turtlebot4-user-manual/software/turtlebot4_packages.html#turtlebot-4-simulator
1 - Not sure if it is relevant, but before trying to install the simulator, I installed the Turblebot 4 and Turtlebot 4 Desktop using apt install and compiled from source the Turtlebot 4 Desktop in the same workspace as the Simulator (turtlebot4_ws).
2 -
sudo apt-get update && sudo apt-get install wget
sudo sh -c 'echo "deb http://packages.osrfoundation.org/gazebo/ubuntu-stable lsb_release -cs main" > /etc/apt/sources.list.d/gazebo-stable.list'
wget http://packages.osrfoundation.org/gazebo.key -O - | sudo apt-key add -
--2022-10-25 12:59:54--  http://packages.osrfoundation.org/gazebo.key
sudo apt-get update && sudo apt-get install ignition-edifice
cd ~/turtlebot4_ws/src
git clone https://github.com/turtlebot/turtlebot4_simulator.git
cd ~/turtlebot4_ws
vcs import src < src/turtlebot4_simulator/dependencies.repos
rosdep install --from-path src -yi
source /opt/ros/galactic/setup.bash
colcon build --symlink-install
This is the full output from the last command:
[0.239s] WARNING:colcon.colcon_core.package_selection:Some selected packages are already built in one or more underlay workspaces:
'irobot_create_msgs' is in: /opt/ros/galactic
'turtlebot4_description' is in: /opt/ros/galactic
'turtlebot4_msgs' is in: /opt/ros/galactic
'turtlebot4_node' is in: /opt/ros/galactic
If a package in a merged underlay workspace is overridden and it installs headers, then all packages in the overlay must sort their include directories by workspace order. Failure to do so may result in build failures or undefined behavior at run time.
If the overridden package is used by another package in any underlay, then the overriding package in the overlay must be API and ABI compatible or undefined behavior at run time may occur.
If you understand the risks and want to override a package anyways, add the following to the command line:
--allow-overriding irobot_create_msgs turtlebot4_description turtlebot4_msgs turtlebot4_node
This may be promoted to an error in a future release of colcon-override-check.
 You will need to checkout the galactic branch.


Add support for fallback function in worldgen

See https://github.com/latticexyz/mud/pull/501#discussion_r1139503296

this was opened for parity with system fallback functions but I think we're not registering system fallback functions anymore, esp now that system name isn't included in function signatures?

Decided not to implement this


Is there support encryption with multiple keys?

Hi there,
In GPG keychain,
I can encrypt a message with multiple recipient public key, and it will return a PGP encrypted message.
So that the valid user can decrypt the file.
But I tried in your opengpg package, it can encrypt message, but only one person can decrypt it with GPG keychain.
My step:

Use GPG keychain export multiple users public key.
Use your tool to encrypt a message with above public key and output to base64.
Use GPG keychain CLI to decode the message. But got failed. The corresponding error message:

echo ${ENCRYPTD_BY_OPENGPG_BASE64} | base64 -D | gpg -d`

gpg: encrypted with 4096-bit RSA key, ID 0A00AA00A000AA00, created 2016-02-27
      "foo<EMAIL_ADDRESS>gpg: decryption failed: No secret key

What's step is wrong?

Hello, sorry for late reply.
Can you elaborate on the steps being done to encrypt the message?
go-crypto package supports encryption to multiple recipients, see here: https://github.com/keybase/go-crypto/blob/master/openpgp/write.go#L204-L209


Example with financial data

This is an example based on a patent application exploiting RG+quantum for detecting fraudulent behavior.

@qbarthelemy I made another pass on the example. There are mainly two changes:

I keep the NearMiss for computational reasons but increased the number of non-fraud example (that was also one of your remarks at the beginning if I remember correctly)
I changed the pb to "predict the type of fraud" rather than predict if the transaction is a fraud.

I also gave a tried to the halving grid search. It is quicker, but may be less accurate than the standard grid search.


Adds documentation for configfiles API and new ORT options

Adds documentation for configuration files and metadata API and the new configuration options in Traffic Ops and ORT for rapid revalidate and reverse proxy caching.

last i checked, these docs now build properly via sphinx...so i'm fine with the PR once the @dangogh  comment is addressed. I'll kick this over to @dangogh


Wrong property being read from /etc/os-release to define platform support

Describe the bug
When using EF with SqlServer driver under some linux distributions,  an exception is thrown saying that Microsoft.Data.SqlClient is not supported despite the full platform support of dotnet.
I saw this behavior with the same versions of dotnet [6.0.113] and EF [7.0.3] in two ubuntu systems that have dotnet installed from the same ubuntu official repository. The only difference is that one is a basic ubuntu server instalation and the other is a desktop distribution fully based on ubuntu called PopOS.
I believe that dotnet is reading the /etc/os-release property ID to define the platform when it should be reading the ID_LIKE because when I altered the ID property to ubuntu in the PopOS system, the DLL behaved as expected.
Here are BOTH /etc/os-release files.
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
--------------------------------------------
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
UBUNTU_CODENAME=jammy

As you can see, the correct platform definition is in the ID_LIKE, so I suggest merging both to compare and define if the system is supported or not.
My exception:
Exception message: Microsoft.Data.SqlClient is not supported on this platform
Stack trace:
System.PlatformNotSupportedException: Microsoft.Data.SqlClient is not supported on this platform.
         at Microsoft.Data.SqlClient.SqlConnectionStringBuilder..ctor(String connectionString)
         at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.<>c.<get_IsMultipleActiveResultSetsEnabled>b__7_0(String cs)
         at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
         at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.get_IsMultipleActiveResultSetsEnabled()
         at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query, Boolean async)
         at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
         at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.Execute[TResult](Expression expression)
         at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator()
         at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
         at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
         at @@MYPROJECT.Controller@@
         at lambda_method1(Closure , Object , Object[] )
         at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
         at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
         at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
         at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

To reproduce
Have a Ubuntu system and derivative distro. With the same project using EF and same dotnet version, an exception is thrown in the sub-distro.
Expected behavior
They should work as the same in both platforms because the sub-distro HAS A CORRECT platform definition.
Further technical details
Microsoft.Data.SqlClient version: 5.0.1
.NET target: Core 6.0.113
SQL Server version: 2022
Operating system: Ubuntu 22.04 AND PopOS based on 22.04 with same official repos

Thanks @raibtoffoletto for bring this to our attention and providing a suggestion to expand the support for the linux distros. We'll have to take a look at the implementation on how the check is performed and get back to you soon.

Thank you!
In my quick search I couldn't find the implementation, only mentions to the exception, so if this is not specific to the SqlClient I'm happy to open an issue upstream as well.

Thanks @lcheunglci .
So if I understand who implements this is the runtime, so I'll open an issue upstream.
Cheers, R.


How should I manage plugins across two .vim files?

I currently have one vimrc which I check into source control and distribute to all machines I use, and I source a ~/.vimrc-local at the end if it exists, for any machine-specific settings.
If I have machine-specific plugins to include, is there any way to specify them using my current setup (in ~/.vimrc-local), or do I need to create a third file (.vim-plugins-local) which is sourced from within the  plug#begin/plug#end block, as #425 implies? I understand that I can't have a second plug#begin/plug#end block, so I'm wondering if there are any other solutions.

Type:

[ ] Bug
[ ] Enhancement
[ ] Feature Request
[x] Question

OS:

[x] All/Other
[ ] Linux
[ ] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[ ] Neovim

The only alternative I see to having at least one more files specifiying the plugins would be to define you own syntax to include the global plugin lines as comments in one file and use some vimscript to read that file when processing the other, cut out the corresponding comments, uncomment, and source them. But personally I would probably just have the plug#begin/plug#end block in  ~/.vimrc-local and source  ~/.vim_plug and ~/.vim_plug-local there specifiying the global and local plugins instead of that way more hacky two-file version.

No, only single block is allowed.

I source a ~/.vimrc-local at the end if it exists, for any machine-specific settings.

You can just source the file from within begin-end block. If you have some settings and code that should be delayed until the end, you can put it in a function and make it triggered on VimEnter autocmd, or manually call it at the end of the file. I know this is not ideal, but I don't want to complicate things.
Plug 'junegunn/seoul256.vim'

function! Delayed()
  silent! colo seoul256
endfunction

autocmd VimEnter * call Delayed()

plug#begin resets the internal data structures. If plug#begin doesn't reset the data, there will be duplicate entries when you reload your Vim configuration file, and vim-plug will have to deduplicate the list. Extra code required.
plug#end does the heavy-lifting of initializing plugins. If we allow multiple plug blocks, plug#end() will be called multiple times, and it will do unnecessary work multiple times. Because vim-plug wouldn't know if this plug#end() is truly the last one. If we want to make things more efficient, we would need to replace plug#end with plug#not_really_end and manually call plug#really_end at the end.

Thanks for the info. It would be very useful if you could add this to the docs.


Single cell experiment page link broken for the experiment - E-MTAB-7316

Issue: Experiments page has been broken for the experiment:  E-MTAB-7316
E-MTAB-7316 - 400 error.
User ticket on RT:  https://helpdesk.ebi.ac.uk/Ticket/Display.html?id=489128
Pivotal reference: https://www.pivotaltracker.com/story/show/177533187

I have started my debugging to find a root cause:
I'm able to reproduce the bug. I could see '400' error code when I try to fetch the experiment: E-MTAB-7316 on ves-hx-77(test)

During code debugging, I have seen Solr Exceptions while fetching experiment:
Class - ExperimentController.java -> endpoint-> "/experiments/{experimentAccession}" method-> showExperimentPage(..)
In this method, while adding content to the model code is failing.
...model.addAttribute(
                "content",
                experimentPageContentSerializer.experimentPageContentForExperiment(experimentAccession, accessKey));

I have decided to switch test Solr to point to analytics v3 collection instead of v5 just to prove that collection issue or not.
I have created a new alias on Test Solr and pointed to the scxa-analytics-v3 collection from the scxa-analytics-v5.

I have tested after pointing test Solr to v3 and found that the experiment page working fine for the experiment: E-MTAB-7316. I have got the 200 status code.

Again I pointed Test Solr to analytics v5 collection to find out java problematic a piece of code. Here are the details and exceptions traces...
Problematic java code -

Class- CellMetaDataDao.java ->

method->

// Given a type of metadata and an experiment accession, this method retrieves the value of that metadata for the
    // cells in an experiment
    public ImmutableMap<String, String> getMetadataValues(String experimentAccession,
                                                          String metadataType) {
        // Find matching characteristic name and factor name docs...
 var solrQueryBuilder =
                new SolrQueryBuilder<SingleCellAnalyticsCollectionProxy>()
                        .addQueryFieldByTerm(EXPERIMENT_ACCESSION, experimentAccession)
                        .addQueryFieldByTerm(ImmutableMap.of(
                                FACTOR_NAME, ImmutableSet.of(metadataType),
                                CHARACTERISTIC_NAME, ImmutableSet.of(metadataType)))
                        .sortBy(CELL_ID, asc)
                        .setFieldList(ImmutableSet.of(CELL_ID, FACET_CHARACTERISTIC_VALUE, FACET_FACTOR_VALUE));
........}

Here are the exception details throwing from this method:
Exception trace: org.apache.solr.common.SolrException: Could not load collection from ZK: scxa-analytics-v5
Code: 400

Detailed message: Could not load collection from ZK: scxa-analytics-v5
Path: /collections/scxa-analytics-v5/state.json

org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /collections/scxa-analytics-v5/state.json

java.io.IOException: --> http://<IP_ADDRESS>:8983/solr/scxa-analytics-v5_shard4_replica_n4/: An exception has occurred on the server, refer to server log for details.

java.io.IOException: org.apache.solr.common.SolrException: Could not load collection from ZK: bioentities

This bug is a bit tricky - the majority of the exceptions are related to scxa-analytics-v5, But I have noticed bioentities exceptions as well sometimes during debugging.
As we are using Solr streams to deal with Solr, I'm not really sure which line of code causing the issue in the above method. But I can say that after fetching metadata types, we are trying to fetch metadata values for each type. During that process, for the metadata type = 'replicate' Solr contact is failing.

@lingyun1010 -Hope I have provided all the details that I found in my debugging to progress on this further.

Error is on the line in CellMetadataService class
cellMetadataDao.getCharacteristicTypes(experimentAccession).stream())

Error message is org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /collections/scxa-analytics-v5/state.json

Error meesage:  http://<IP_ADDRESS>:8983/solr/scxa-analytics-v5_shard4_replica_n4/: An exception has occurred on the server, refer to server log for details.
Line 160:        try (var tupleStreamer = TupleStreamer.of(uniqueStreamBuilder.build())) in CellMetadataDao class.

The error metadataType comes from cellMetadataDao.getFactorTypes(experimentAccession).stream() in CellMetadataService class.
The solution might be remove/filter the metadataType in return.

Great, @lingyun1010. Will see, what @alfonsomunozpomer or @pcm32 suggest on this.

Great debugging issue @upendrakumbham and @lingyun1010! This is very useful. What puzzles me still is why this error only comes up in the servers but not on your dev environments.... this also makes sense with the pattern that we saw in the past when loading data into solr for v5: it worked fine from laptops but failed from servers (and we could never figure out the issue - it went away when Alfonso replicated test solr into dev solr I think).

Hi @pcm32, last Friday @alfonsomunozpomer also joined us to debug this tricky bug, under his guidance we got more insights about the bug, but we didn't find the exact root cause why Solr TupleStreamer throwing UncheckedIOException.
We are planning to continue our debugging today with @alfonsomunozpomer to fix this bug as soon as possible.

Please debug the line cellMetadataDao.getMetadataValues(experimentAccession, metadataType); with metadataType in the experiment E-MTAB-7316
0 = "replicate"
1 = "individual"
2 = "sex"
3 = "inferred_cell_type_-_authors_labels"
4 = "inferred_cell_type_-_ontology_labels"

I suspect, based on logs, that E-ENAD-51 and E-ENAD-53 are suffering from the same.
14:50:55.134 [http-nio-8080-exec-83] INFO  uk.ac.ebi.atlas.web.interceptors.TimingInterceptor - /gxa/sc/experiments/E-ENAD-51?accesskey=c2d37860-f2f5-40bc-b60b-ae55cd4c63b5 - start
14:50:55.567 [http-nio-8080-exec-83] INFO  uk.ac.ebi.atlas.solr.cloud.CollectionProxy - Querying *:*
14:50:55.579 [http-nio-8080-exec-83] INFO  uk.ac.ebi.atlas.solr.cloud.CollectionProxy - Querying characteristic_name:("inferred_cell_type_\-_ontology_labels")
14:50:56.245 [http-nio-8080-exec-83] ERROR uk.ac.ebi.atlas.controllers.HtmlExceptionHandlingController - null -

@lingyun1010 @upendrakumbham @alfonsomunozpomer do we know if the issue is exactly the same across all experiments, or could it be that it is different pieces in the content brought by the solr query that could be generating this?

@lingyun1010 @upendrakumbham Many thanks for your comments and insights, it’s been very helpful and you were close to solving the mystery!
The issue is that in all these experiments there are cells that are missing the inferred cell type - authors labels field in Solr. This happens only in scxa-analytics-v5. For instance:

E-MTAB-7316: ERR2854358-AAACCTGAGAGGTAGA

This doesn’t match the condensed SDRF file, which has a value for the authros labels.
Looking at E-HCAD-5 and faceting over facet_factor_name, we’ve got in v3:
"facet_factor_name":[
        "cell_type",23474,
        "inferred_cell_type_-_authors_labels",17542,
        "inferred_cell_type_-_ontology_labels",17542,
        ...

And in v5 we have:
"facet_factor_name":[
        "cell_type",23572,
        "inferred_cell_type_-_authors_labels",17499,
        "inferred_cell_type_-_ontology_labels",17465,
        ...

Again, this doesn’t match the condensed SDRF file:
[tc_fg02@ves-hx-77 E-HCAD-5]$ grep "inferred cell type - authors labels" E-HCAD-5.condensed-sdrf.tsv | wc -l
17542
[tc_fg02@ves-hx-77 E-HCAD-5]$ grep "inferred cell type - ontology labels" E-HCAD-5.condensed-sdrf.tsv | wc -l
17542

This isn’t a comprehensive list, but I’d bet a beer that this is in fact the problem. Somewhere along the code this breaks some expectation or implicit assumption (from the looks of it, CellMetadataDao).
Now, we need to decide what we should do:

Fail gracefully and show data as it is from Solr, and "we do the best we can with what we have".
Show a meaningful error that will help us fix the error.

I'm guessing the question is why we have different numbers of elements loaded in Solr compared to the condensed, since the analytics index gets loaded from the condensed, and that process runs every time that the condensed get modified. We will need to check the loading. Or could this be somehow related to the ontology expansion?
Does the web application has any awareness on whether it is deployed on wwwdev or www? It would be great if in public it could just show what we find (option 1) and in the wwwdev do 1 as well but also show the message suggested in 2 for ourselves.
Could you please generate a list from Solr of the cell types with the 3 annotations for one of the experiments, so that we can compare the missing ones with the condensed and see whether there is any pattern in the data that can unravel the source of this disparity? Thanks!

The missing docs isn’t related to ontology expansion, or it shouldn’t be, since the document makes it to Solr and then BioSolr adds the missing fields. Of course, I don’t know if an exception in the ontology expansion process could prevent a document from getting into the collection, but I doubt it. A simple way of knowing for sure would be to inspect the JSON files before sending them to Solr. It‘d be easy to do with a very simple edit in our scripts and running it for one of these faulty experiments.
As for your second question the answer is no. The app is the same in both staging and public/fallback (this is a desirable feature). What we should do is to add logging messages in the code and produce warning messages that we can easily grep from the log files. If I’m not mistaken, the only difference in logging between staging and public/fallback is that in the latter logs are written in batches instead of line-by-line to decrease I/O waiting times. The logging configuration is injected when Tomcat deploys the app in the file logback.xml and is located together with jdbc.properties and solr.properties.
I’ll do the list for E-HCAD-5. It shouldn’t be hard with a bit of jq and comm.

For the E-MTAB-7316 cell mentioned, doing:
awk -F'\t' 'BEGIN { OFS = "\t"; } { if( $4 == "factor" || $4 == "characteristic" ) { gsub(/ /, "_", $5); print "{ \"experiment_accession\": \""$1"\",\n \"cell_id\": \""$3"\",\n \""$4"_name\": \""$5"\",\n \""$4"_value\": [\""$6"\"],\n \"ontology_annotation\": [\""$7"\"] }"; } }' E-MTAB-7316.condensed-sdrf.tsv |jq -s '. | del(.[][] | select(. == [""]))' | grep -A 5 -B 2 ERR2854358-AAACCTGAGAGGTAGA

in the ATLAS_SC_EXPERIMENTS/E-MTAB-7316 directory you get:
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "developmental_stage",
    "characteristic_value": [
      "adult"
    ],
    "ontology_annotation": [
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "disease",
    "characteristic_value": [
      "normal"
    ],
    "ontology_annotation": [
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "individual",
    "characteristic_value": [
      "Donor 1 [17-010]"
    ]
  },
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "organism",
    "characteristic_value": [
      "Homo sapiens"
    ],
    "ontology_annotation": [
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "organism_part",
    "characteristic_value": [
      "retinal neural layer"
    ],
    "ontology_annotation": [
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "replicate",
    "characteristic_value": [
      "5"
    ]
  },
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "sex",
    "characteristic_value": [
      "female"
    ],
    "ontology_annotation": [
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "replicate",
    "factor_value": [
      "5"
    ]
  },
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "inferred_cell_type_-_ontology_labels",
    "factor_value": [
      "retinal rod cell"
    ]
  },
--
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "inferred_cell_type_-_authors_labels",
    "factor_value": [
      "retinal rod cell CCA1"
    ]
  },

which looks alright to me. This is the same as running:
condSdrf2tsvForSCXAJSONFactorsIndex.sh $CHUNK_FILE | jsonFilterEmptyFields.sh

so everything before the loading.

A cleaner version of this which could be used to attempt a loading into solr (to see why it doesn't load):
cat E-MTAB-7316.condensed-sdrf.tsv | grep 'ERR2854358-AAACCTGAGAGGTAGA' | awk -F'\t' 'BEGIN { OFS = "\t"; } { if( $4 == "factor" || $4 == "characteristic" ) { gsub(/ /, "_", $5); print "{ \"experiment_accession\": \""$1"\",\n \"cell_id\": \""$3"\",\n \""$4"_name\": \""$5"\",\n \""$4"_value\": [\""$6"\"],\n \"ontology_annotation\": [\""$7"\"] }"; } }' | jq -s '. | del(.[][] | select(. == [""]))'

which yields:
[
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "developmental_stage",
    "characteristic_value": [
      "adult"
    ],
    "ontology_annotation": [
      "http://www.ebi.ac.uk/efo/EFO_0001272"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "disease",
    "characteristic_value": [
      "normal"
    ],
    "ontology_annotation": [
      "http://purl.obolibrary.org/obo/PATO_0000461"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "individual",
    "characteristic_value": [
      "Donor 1 [17-010]"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "organism",
    "characteristic_value": [
      "Homo sapiens"
    ],
    "ontology_annotation": [
      "http://purl.obolibrary.org/obo/NCBITaxon_9606"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "organism_part",
    "characteristic_value": [
      "retinal neural layer"
    ],
    "ontology_annotation": [
      "http://purl.obolibrary.org/obo/UBERON_0003902"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "replicate",
    "characteristic_value": [
      "5"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "characteristic_name": "sex",
    "characteristic_value": [
      "female"
    ],
    "ontology_annotation": [
      "http://purl.obolibrary.org/obo/PATO_0000383"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "replicate",
    "factor_value": [
      "5"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "inferred_cell_type_-_ontology_labels",
    "factor_value": [
      "retinal rod cell"
    ]
  },
  {
    "experiment_accession": "E-MTAB-7316",
    "cell_id": "ERR2854358-AAACCTGAGAGGTAGA",
    "factor_name": "inferred_cell_type_-_authors_labels",
    "factor_value": [
      "retinal rod cell CCA1"
    ]
  }
]

maybe someone can try loading this into solr and see if it goes through?

Fixed by https://github.com/ebi-gene-expression-group/atlas-web-single-cell/pull/185.


Can you tell me how to modify your code?

Hello !
I need to save other attributes as person wear glasser or not , I have append these attributes with QCheckBox.Can you tell me how to save these attributes ,I donot know how to append thess checks in shapes.
Thank you for your help !

@shiwenhao ,Hi,can you tell me how to add these attributes with QCheckBox?

@mengzhangjian Sorry for the late reply，I add these attributes with QCheckBox like

When I click person item,I change text of QCheckBox,and setVisible(True).But I do not know how to save thess attributes,if you find how to save, please tell me .Thanks a lot!

When I run python labelImg.py with LabelDialog.py included with additional codes above.
It gives me error: NameError: Global name ObjectItem is not defined.


Amplify mock using wrong resolvers directory

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
node 16
Amplify CLI Version
10.5.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
When 'amplify mock' is executed as part of the process it generates graphql vtl files.
However those files are written in 'amplify/backend/api/[apiName]/resolvers' instead of 'amplify/backend/api/[apiName]/build/resolvers'.
First path is used to overwrite the auto generated resolvers by amplify and I don't see why would the mock process use it. It also lead to a nasty bug where the files were not deleted when mocking process stoped executing and any chages made to schema.graphql after that were overwritten by the old resolvers.
Expected behavior
Amplify mock should use "/build/resolvers" path.
Reproduction steps
1.Setup test project with graphql api
2.Run amplify mock
3.Check where it saves generated resolvers
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @mstoyanovv :wave: thanks for raising this! Are you experiencing an issue with the generated resolvers placed in the api's resolvers/ directory (not build/resolvers/)? When you execute amplify mock the CLI should generate resolvers in resolvers/, and when mock is stopped those resolvers should be removed from this directory where custom/overridden resolvers should remain untouched.

Hi @josefaidt one example is if the terminal that was used to execute 'amplify mock' is closed or exits unexpectedly the generated resolvers are not deleted.
On next amplify-mock execution they are taken as 'user generated' and not 'mock generated'. Therefore any changes that are being done to schema.graphql after that are always going to be overwritten untill those resolvers are manually deleted from the folder.
This is why I aksed about the reason to use exaclty this folder which overwrites the build generated resolvers. It is risky and can lead to unexpected behaviour like the one described above.

Hey @mstoyanovv thanks for clarifying! Although I am not able to reproduce the issue where resolvers are leftover after explicitly closing mock by using ctrl+c, I can see how the resolvers are not cleaned up after mock exits unexpectedly. I'll mark this as a bug to revise the cleanup procedure of mock, or revise where resolvers are placed and used during mock.
In the immediate time frame, I would rely on git to maintain an unscathed copy of your resolvers/ directory


chore: release docker-jans-auth-server 1.0.0-beta.13

:robot: I have created a release *beep* *boop*
1.0.0-beta.13 (2021-12-03)
Features

add support for plugins (#67) (7f2204c)

Miscellaneous Chores

release 1.0.0-beta.13 (789a9ed)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/JanssenProject/jans-cloud-native/releases/tag/docker-jans-auth-server-v1.0.0-beta.13 :sunflower:


Authoring guidelines: creating kata

Breakdown of #139
Set of guidelines related to writing a new kata.
Should focus mostly on the concept of the kata itself, and link to articles related to specific parts (tests, description).
Use existing resources:

Current tutorial
maybe some parts of hobovsky's idea?

Suggested guidelines:

Task

avoid duplicates, use new idea. Do not use problems from other sites.
avoid distractions, keep kata focused on one task
if kata task is not language specific, use ideas which can be easily translated. Like, avoid mixed return types, because they are difficult to have with statically typed languages.
something about pointless, wrong, or untestable requirements: rounding, API restrictions,

Review

make kata complete before publishing it. Do not "I will add this later".
share links to draft before publishing to get early feedback
let others help you, use gitter

Responsibility

maintain your kata

This is the next topic which I would like to tackle, and I expect it to be quite big. @codewars/community every hint and idea counts!

task:

good katas are generally created wrapping code around the original idea, and not twisting the description/task around the code (that's for easy katas)
avoid antipatterns. For example, a wrong input is supposed to raise an error/exception, not to return -1 or "oops" or ...

responsibility:

write maintainable code. Once you'll quit CW, other users will have to handle your mess... XD

maybe to state that the language to use is english?

good katas are generally created wrapping code around the original idea, and not twisting the description/task around the code (that's for easy katas)

I am not sure if I agree in general, and I think that kata created "code first" can also be good. But still, I can see how noob authors are getting it wrong. I will think how to word it.

avoid antipatterns. For example, a wrong input is supposed to raise an error/exception, not to return -1 or "oops" or ...

Yup.

responsibility:

write maintainable code. Once you'll quit CW, other users will have to handle your mess... XD
don't approve translations without questions, especially if you don't know the language (?)
maybe to state that the language to use is english?

These will be mentioned in related parts (coding, translations, descriptions).

PR merged, please open a new issue if you find any problems or have more suggestions.


[Bug]: Trouble connecting to Shuttle Shared Databases with PgAdmin

What happened?
I'm struggling to use PgAdmin 4 v8.7 to connect to my shuttle shared database. When I deploy a project with a shared postgres database I get a connection string like postgres://user-<project_name>:********@db.shuttle.rs:5432/db-<project_name> and I can use cargo shuttle resource list --show-secrets to see the full connection string like postgres://user-<project_name>:<password>@db.shuttle.rs:5432/db-<project_name>
You can see here for an example of how I'm trying to configure the connection (note that I'm using my actual project name, not the <project_name> placeholder)

Then after connecting I get a "Failed to retrieve data from the server. permission denied for table pg_database" error.

I've also tried changing the "Maintenance database" setting but that does not seem to work either.

Version
v0.45.0
Which operating system(s) are you seeing the problem on?
macOS
Which CPU architectures are you seeing the problem on?
ARM64
Relevant log output
No response
Duplicate declaration

[X] I have searched the issues and there are none like this.

The shared Postgres cluster has lots of restrictions, making "permission denied for table pg_database" appear when doing various operations on pgAdmin. If you close the error box(es) you should still be able to interact with your database.


Update MD file on new branch 2017-12-03_07-28-19

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Manage Apps is missing

I'm a global admin (and a Teams Service Admin), but I don't get the Manage Apps menu item in the Team Admin Centre.
I have Permission policies and Setup policies, but no Manage Apps.
Am I missing something somewhere?

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

ID: fbbcabee-fa96-2878-e983-3c966f84ee15
Version Independent ID: 02fa4fd8-77e0-5cb2-a4af-576cbb68322f
Content: Manage your apps in the Microsoft Teams admin center - Microsoft Teams
Content Source: Teams/manage-apps.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Craig-Humphrey Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Craig-Humphrey thank you for reaching out. Please have a look at this article and let me know if it helps - https://docs.microsoft.com/microsoftteams/teams-app-permission-policies

Thanks @lindspea, no, that relates to Teams apps -> Permission Policies menu item, in Teams Admin.
I was after the Teams apps -> Manage apps.
However, it has now appeared on the menu for both the tenants I admin.
I wonder if it just took longer to roll out to the Australian O365 tenants...
You can close this ticket and check with the other two similar tickets...


Router silently fails

Enhancement Request
There are cases when the router will swallow errors during the navigation process, leaving the user with a blank page, and the console with no indication what went wrong.
I've found that most cases (for me at least) involve failing on some kind of deactivate or detached method, and every time I get this behavior, I have to go into the code and wrap the navigation inside a try-catch block to output the error.
It would be beneficial to have some kind of error logging for these errors.

Since you have figured out how to catch them, perhaps you can make a PR for the fix? @bryanrsmith can review and provide any guidance you need.

Sure. What I had done was just wrap the code at https://github.com/aurelia/router/blob/master/src/router.js#L143 inside a try catch. I can make a PR with just that, but I'm not sure if that's something that should just be thrown into the console, or interact with the aurelia logger (which I'm not as familiar with)?

@AStoker Since navigation is asynchronous, it's not clear to me how wrapping the line you reference in a try catch will actually catch any real errors that happen. Are you sure that's the correct location? Can you tell me how I can reproduce the unreported error? That would enable me to find the best place to put the error reporting logic.

@EisenbergEffect, I think the router has changed a bit, so that line number isn't accurate anymore. What was happening was one of the view model's deactivate method was throwing an error, and that method is called during the router lifecycle. But somewhere along the way, the error was being swallowed and not writing the error to the console, so wrapping the navigate logic was all I needed to at least get the error to be caught. I'll see if I can't get a simple repro-repo with the skeleton navigation project for you this week.

I have a similar issue, not sure it's exactly the same, but seems to have happened in the last release.
If something goes wrong when activating a route I get no error reporting at all, see child.js in the following gist:
https://gist.run/?id=e8e3c7fcc68957a9a11d24c4535f2c04

I don't know if this will catch all silent router errors, but the trick I managed to find is to put a breakpoint in bluebird's util.js.
function tryCatcher() {
    try {
        var target = tryCatchTarget;
        tryCatchTarget = null;
        return target.apply(this, arguments);
    } catch (e) {
        errorObj.e = e;  // ******* break point here ****** 'e' typically contains the error that is silently failing
        return errorObj;
    }
}

I use the CLI so to debug silent failures, I search for the tryCatcher() function in the vendor-bundle.js and break point there.  You'll typically see an error like Error invoking [TheNameOfOneOfYourViews]. Check the inner error for details.
The inner details typically is not helpful, so from there my strategy is to breakpoint the code related to the view and look for errors and/or remove parts of the template's HTML until it starts to work.
I have not been able to find what is swallowing the error.

Hero is an example of this: https://gist.run/?id=921f733f75d7c0658ab1bdf0cf534858. Router.prototype.generate is eventually callled with undefined which throws here but there is no error in console. I will send a PR that adds a logger.error call but I don't know if that is the most elegant solution.

This is stale
Could not find a PR merged
for gist  https://gist.run/?id=e8e3c7fcc68957a9a11d24c4535f2c04 there is now an error log with stack and error message
I augmented said gist with another child and an expception thrown on deactivate() of first
https://gist.run/?id=cfd7bc9a2dafcdab7701632beb7e906b
error is also being logged
can be closed, I guess

How about this comment? I never managed to assemble a fix. Should I open another issue?

@gheoan did you have any progress?

@gheoan Please do, especially if you can show a more common use case example. I closed this since the original gist.run is now working properly.


Android build fails for libs with minSdkVersion 17 with react-native 0.64

Environment

react-native-pager-view: 5.1.2
React Native: 0.64.0
Node: v14.8.0

Description
The following command fails after upgrading to RN 0.64
./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug
With the following message:
> Task :react-native-pager-view:processDebugAndroidTestManifest FAILED
[androidx.vectordrawable:vectordrawable-animated:1.0.0] /.gradle/caches/transforms-2/files-2.1/3050775700026023c1db3db79ab19a97/vectordrawable-animated-1.0.0/AndroidManifest.xml Warning:
        Package name 'androidx.vectordrawable' used in: androidx.vectordrawable:vectordrawable-animated:1.0.0, androidx.vectordrawable:vectordrawable:1.0.1.
/node_modules/react-native-pager-view/android/build/intermediates/tmp/manifest/androidTest/debug/manifestMerger2807704319365703146.xml:5:5-74 Error:
        uses-sdk:minSdkVersion 17 cannot be smaller than version 21 declared in library [com.facebook.react:react-native:0.64.0] /.gradle/caches/transforms-2/files-2.1/4e32a44ca1590525038237dd6b47cd32/jetified-react-native-0.64.0/AndroidManifest.xml as the library might be using APIs not available in 17
        Suggestion: use a compatible library with a minSdk of at most 17,
                or increase this project's minSdk version to at least 21,
                or use tools:overrideLibrary="com.facebook.react" to force usage (may lead to runtime failures)

See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.

Reproducible Demo
Run ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug

Would it be possible to release this change as it's currently causing a problem for us?

@IPWright83 I have this in my script waiting for the release: sed -i "s/minSdkVersion 17/minSdkVersion getExtOrIntegerDefault('minSdkVersion')/" ./node_modules/react-native-pager-view/android/build.gradle

@Andarius is that supposed to be add something to the file? I gave it a quick try but doesn't seem to be working for me :(
I've also tried adding <uses-sdk tools:overrideLibrary="com.facebook.react"/> into my android/app/src/debug/AndroidManifest.xml file which didn't help. All of which I thought would be irrelevant as our build.gradle defines 23 as our minSdkVersion.
 ext {
        buildToolsVersion = "29.0.3"
        minSdkVersion = 23
        compileSdkVersion = 29
        targetSdkVersion = 29
        kotlinVersion = '1.3.61'
        ndkVersion = "20.1.5948944"
    }

It'll replace the line containing minSdkVersion 17in the build.gradle of react-native-pager-view with minSdkVersion getExtOrIntegerDefault('minSdkVersion'). Run this after a yarn install from your folder that contains node_modules

This fix has been released here: https://github.com/callstack/react-native-pager-view/releases/tag/v5.1.3


Cannot read properties of undefined (reading 'use')

Details
Hi, this issue happened to me after installing nuxt-seo-kit, at first nothing worked until I upgraded my local node version, but now, each time my nuxt.config.ts updates, or I restart my dev server, this issue occurs, and I need to delete node_modules .nuxt and reinstall all packages.
I don't know if anyone have encountered this issue before, Thanks
some additional info:
pnpm version: 7.28.0
node version: lts/gallium
nuxt version: 3.2.2
nuxt-seo-kit version: 1.3.1

Console warning:
chunk-Q53DPCWL.js?v=08e16e01:1381 [Vue warn]: Hydration node mismatch:

Client vnode: div
Server rendered DOM:  (start of fragment)
at <ErrorDev statusCode=500 statusMessage="Internal Server Error" description="Cannot read properties of undefined (reading 'use')"  ... >
at <AsyncComponentWrapper statusCode=500 statusMessage="Internal Server Error" description="Cannot read properties of undefined (reading 'use')"  ... >
at <NuxtErrorPage key=0 error= TypeError: Cannot read properties of undefined (reading 'use')
at plugin.mjs?v=08e16e01:9:10
at fn (nuxt.mjs?v=08e16e01:146:27)
at callWithNuxt (nuxt.mjs?v=08e16e01:151:12)
at applyPlugin (nuxt.mjs?v=08e16e01:97:29)
at applyPlugins (nuxt.mjs?v=08e16e01:106:11)
at async initApp (entry.mjs:39:7) >
at <AsyncComponentWrapper key=0 error= TypeError: Cannot read properties of undefined (reading 'use')
at plugin.mjs?v=08e16e01:9:10
at fn (nuxt.mjs?v=08e16e01:146:27)
at callWithNuxt (nuxt.mjs?v=08e16e01:151:12)
at applyPlugin (nuxt.mjs?v=08e16e01:97:29)
at applyPlugins (nuxt.mjs?v=08e16e01:106:11)
at async initApp (entry.mjs:39:7) >
at

Error page message:
500
Cannot read properties of undefined (reading 'use')
at http://localhost:3000/_nuxt/node_modules/.pnpm/nuxt-unhead@1.4.6/node_modules/nuxt-unhead/dist/runtime/plugin.mjs?v=08e16e01:9:10
at fn (http://localhost:3000/_nuxt/node_modules/.pnpm/nuxt@3.2.2/node_modules/nuxt/dist/app/nuxt.mjs?v=08e16e01:146:27)
at callWithNuxt (http://localhost:3000/_nuxt/node_modules/.pnpm/nuxt@3.2.2/node_modules/nuxt/dist/app/nuxt.mjs?v=08e16e01:151:12)
at applyPlugin (http://localhost:3000/_nuxt/node_modules/.pnpm/nuxt@3.2.2/node_modules/nuxt/dist/app/nuxt.mjs?v=08e16e01:97:29)
at applyPlugins (http://localhost:3000/_nuxt/node_modules/.pnpm/nuxt@3.2.2/node_modules/nuxt/dist/app/nuxt.mjs?v=08e16e01:106:11)
at async initApp (http://localhost:3000/_nuxt/Users/ayoubel/Projects/blog/node_modules/.pnpm/nuxt@3.2.2/node_modules/nuxt/dist/app/entry.mjs:39:7)
Thanks

Hey @rzouhair, thanks for the issue
Please try the latest version, if you still have issues you may need to wait until the next Nuxt patch which will be in the next couple of days.

Thanks @harlan-zw for the reply, appreciate it.
Can I use nuxt/unhead along with nuxt-seo-kit ? as far as I know, nuxt unhead is intergrated in nuxt-seo-kit, so I don't know if they are compatible,
Thanks

Yes! It's one of the reasons I made Nuxt SEO Kit to increase the number of people using this package, allowing me to test out features quicker before I push them into the Nuxt core.

Thank you very much, appreciate your help

Interesting, thanks! Think this is a nuxt layer issue