fix: remove async support from effectFn and cleanupFn

Remove async support from effectFn and cleanupFn.
Related Discussion: https://github.com/jotaijs/jotai-effect/discussions/10
Related PR: https://github.com/pmndrs/jotai/pull/2189
TODO: bump minor after this change.

Looks good to me. This is so much more predictable.

I agree. The main issue with async I feel is the expectation that the effectFn will rerun multiple times independently but in reality atom deps are not updated until the promise resolves and overlapping runs will block each other.

We wouldn’t want to set atom vues synchronous to the read evaluation when
the store is recomputing dependencies. But I think it should be fine in the
next microtask after this recomputation has completed.
On Mon, Oct 16, 2023 at 5:58 PM Daishi Kato @.***>
wrote:

@.**** commented on this pull request.
In src/atomEffect.ts
https://github.com/jotaijs/jotai-effect/pull/12#discussion_r1361396523:

@@ -49,8 +48,9 @@ export function atomEffect(
}
++ref.inProgress
try {

   await ref.cleanup?.()

   ref.cleanup = await effectFn(get, setSelf as Setter)

   await void 0

Yes, what I mean is if we want to warn such usage, because it's usually
a bad idea in Jotai way.
—
Reply to this email directly, view it on GitHub
https://github.com/jotaijs/jotai-effect/pull/12#discussion_r1361396523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGNG6JHB63BKIHXVCKYKOTX7XJZ5AVCNFSM6AAAAAA6C7AQZWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMOBRGE2TENRXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


msert (32-bit) error issue

Hello,
There's an error message of running msert(32-bit), i looked through the msert.log following your direction, it was 0x4 something and says 'The signanutre was not signed'.
Could you help with this?
Thank you in advance.

문서 세부 정보
⚠ 이 섹션을 편집하지 마세요. docs.microsoft.com ➟ GitHub 문제 연결에 필요합니다.

ID: f5bb1ce3-9128-5385-4417-d22eb5f8cb77
Version Independent ID: cb6ba731-a2c2-e9b9-7c3e-db781b1b5222
Content: Microsoft 안전 검사 프로그램 다운로드
Content Source: windows/security/threat-protection/intelligence/safety-scanner-download.md
Product: w10
Technology: windows
GitHub Login: @levinec
Microsoft Alias: ellevin

@officedocsbot assign @jvsam

From a computer support agent viewpoint (myself), I would need more information to be able to even start to answer your question. A verbatim copy of the log file (%SYSTEMROOT%\debug\msert.log) would be a start. I would also recommend that you read the page https://support.microsoft.com/kb/2520970 (How to troubleshoot an error when you run the Microsoft Safety Scanner).
Regarding your mention of an error code starting with 0x4 (not listed in the support page for the tool), I would need to see the log file content (in English) to have any remote chance of estimating what the issue could be caused by. On the other hand, I presume it would be more productive to get help from a local Microsoft Support department (Seoul, Korea?) to find out what the root cause of your issue is.

Also: regarding your comment about the error message saying something like "The signature was not signed", just as a guess on my part, it looks like it could possibly be related to either a device driver or other software package not being supported because it has not been digitally signed by Microsoft. (This is just a guess, I have no evidence to back it up.)

Thank you for sharing that information @illfated 👍! Just to add @hyung-seop, please note that the Microsoft Safety Scanner signatures will expire ten days after downloading. You will need to download a new version of the tool to get the latest malware definitions. Downloading the Microsoft Safety Scanner again is also one of the troubleshooting steps, so that's what I will recommend.
You can also try to run File Signature Verification (SigVerif) tool to see what files are not digitally signed (Use SigVerif command on command prompt or try SigVerif in search). Of course, contacting Windows 10 Support is still your best option.

@jvsam : Thank you for your reply & follow-up. I had completely forgotten about the Microsoft Safety Scanner signatures.

Yesterday I scanned with msert64.exe, but I Don't got any above issue.

It is possible that some 32-bit systems behave differently from 64-bit systems, even if, in theory, they should be the same.

Thank you for all giving kind support and replys, first of all.
But, Unfortunately, i just tried re-installing following you guy's solutions above all, but it still keeps showing me same error message with it.
I've worked on with our companie's other computers(32-bits) and my colleagues are having same problem like me. (It was okay in the past few months)
In detail,
0x8050A005 | The signatures are not signed. | Download the Microsoft Safety Scanner again.
@jvsam Would you mind if i wonder how to use 'Sigverif' tool to make it right about 'signing' in detail?
here are captured pics of this symptom for your deeply understanding.

I'm cautiously curious about the actual program is messed with any lately 'updating' of it, please look into it's history one more time.

@hyung-seop.  sigverif.exe verifies the .exe and .dll files under the system32 and syswow64 folders.
copy the msert.exe file to system32 folder.
go to cmd run as administrator
type  sigverif
press enter
click start

Would you mind if i wonder how to use 'Sigverif' tool to make it right about 'signing' in detail?

I haven't tried @RAJU2529's suggestion since it's built into Windows. Have you tried it? I don't have a 32 bit version to verify.

Is that the information that you are looking for @hyung-seop?

Hi again @hyung-seop, we hope you were able to resolve your concern. We will now close this issue, but if you have feedback or suggestions to help improve the quality of the technical documentation of Microsoft Docs, please let us know by using the feedback feature. Thanks for being part of the Microsoft Docs community!

@officedocsbot close


fix: Adds a message when new logs aren't shown to the user immediately

Issue #, if available: NA
Description of Changes
Currently, when you run the tail logs command it can look like the command hung when it is run. This change provides some messaging to the user so that they are aware that the reason that there are no logs shows is because there aren't any new ones. This also adds back the logic to send through empty logs when no new events are sent back from Cloudwatch
NB: The current approach can show the message immediately before messages are shown if they exist since we split up the request to AWS if the number of streams is larger than the limit (greater than 100 streams). However this is unlikely and could also happen if the logs start appearing immediately after the first request is made to AWS. Since this could occur naturally anyway, would make the logic more complicated and doesn't impact the customer experience I have gone with the simpler solution.
Description of how you validated changes
Ran the commands while running workflows
$ agc logs engine -c onDemandContext -t
2021-10-29T10:53:41-07:00 𝒊  Showing engine logs for 'onDemandContext'
There are no new logs. Please wait for the first logs to appear...
Checklist

[ ] If this change would make any existing documentation invalid, I have included those updates within this PR
[ ] I have added unit tests that prove my fix is effective or that my feature works
[ ] I have linted my code before raising the PR
[ ] Title of this Pull Request follows Conventional Commits standard: https://www.conventionalcommits.org/en/v1.0.0/

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

AWS CodeBuild CI Report

CodeBuild project: AgcDeliveryAutoBuildProject-hB8CzWLG0RNN
Commit ID: 083b438c3a9e6911cec35e567653fb1b78e36b18
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AgcDeliveryAutoBuildProject-xgedwrM1euYG
Commit ID: 083b438c3a9e6911cec35e567653fb1b78e36b18
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

In regards to the AWS Codebuild comment above. It currently isn't able to find the Go version 17.2 so should be ignored for now as it does not relate to anything in the current CR.
go-build: definition not found: 1.17.2

See all available versions with 'goenv install --list'.

If the version you need is missing, try upgrading goenv:

  cd /root/.goenv/plugins/go-build/../.. && git pull && cd -

[Container] 2021/11/01 18:44:36 Command did not exit successfully goenv install exit status 2
[Container] 2021/11/01 18:44:36 Phase complete: INSTALL State: FAILED
[Container] 2021/11/01 18:44:36 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: goenv install. Reason: exit status 2


CLI - Invalid or unexpected token (on the shebang)

I don't know if my issue is entirely due to your package but I must start posting it somewhere (and as it is the first package mentioned in my log...)
I am working on EmberJS projects and for approximatively 2 weeks I always get this error from the command-line:

Content of the log file mentioned in the screenshot (click to toggle):
=================================================================================

ENV Summary:

  TIME: Wed Mar 11 2020 11:37:53 GMT+0000 (Greenwich Mean Time)
  TITLE: ember
  ARGV:
  -<EMAIL_ADDRESS>  - /usr/local/bin/ember
  - help
  - generate
  EXEC_PATH<EMAIL_ADDRESS>  TMPDIR: /var/folders/19/vqwg83651n772jt7n0914f6c0000gn/T
  SHELL: /bin/zsh
  PATH:
  - /usr/local/opt/node@12/bin
  - /Users/_my_user_/bin
  - /usr/local/bin
  - /usr/local/bin
  - /usr/bin
  - /bin
  - /usr/sbin
  - /sbin
  - /opt/X11/bin
  PLATFORM: darwin x64
  FREEMEM: 907194368
  TOTALMEM:<PHONE_NUMBER>4
  UPTIME: 1192041
  LOADAVG: 2.28857421875,2.46240234375,2.21533203125
  CPUS:
  - Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz - 2300
  - Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz - 2300
  - Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz - 2300
  - Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz - 2300
  ENDIANNESS: LE
  VERSIONS:
  - ares: 1.15.0
  - brotli: 1.0.7
  - cldr: 35.1
  - http_parser: 2.9.3
  - icu: 64.2
  - llhttp: 2.0.4
  - modules: 72
  - napi: 5
  - nghttp2: 1.40.0
  - node: 12.16.1
  - openssl: 1.1.1d
  - tz: 2019a
  - unicode: 12.1
  - uv: 1.34.0
  - v8: 7.8.279.23-node.31
  - zlib: 1.2.11

ERROR Summary:

  - broccoliBuilderErrorStack: [undefined]
  - code: [undefined]
  - codeFrame: [undefined]
  - errorMessage: Invalid or unexpected token
  - errorType: [undefined]
  - location:
    - column: [undefined]
    - file: [undefined]
    - line: [undefined]
  - message: Invalid or unexpected token
  - name: SyntaxError
  - nodeAnnotation: [undefined]
  - nodeName: [undefined]
  - originalErrorMessage: [undefined]
  - stack: /Users/_my_user_/Dev/_some_private_path/_playground/node_modules/sort-package-json/index.js:1
(function (exports, require, module, __filename, __dirname) { #!/usr/bin/env node
                                                              ^

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:88:7)
    at createScript (vm.js:263:10)
    at Object.runInThisContext (vm.js:311:10)
    at wrapSafe (internal/modules/cjs/loader.js:1059:15)
    at Module._compile (internal/modules/cjs/loader.js:1122:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Module.require (internal/modules/cjs/loader.js:1044:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at Object.<anonymous> (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/blueprints/addon/index.js:9:25)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Module.require (internal/modules/cjs/loader.js:1044:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at Function.Blueprint.load (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/blueprint.js:1309:31)
    at /Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/blueprint.js:1346:33
    at Array.map (<anonymous>:null:null)
    at /Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/blueprint.js:1345:38
    at Array.map (<anonymous>:null:null)
    at Function.Blueprint.list (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/blueprint.js:1336:22)
    at Class.getAllBlueprints (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/generate.js:92:35)
    at Class.printDetailedHelp (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/generate.js:83:28)
    at Class._printHelpForCommand (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/help.js:114:15)
    at Class.<anonymous> (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/help.js:86:14)
    at Array.forEach (<anonymous>:null:null)
    at Class._printHelp (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/help.js:85:15)
    at Class.run (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/commands/help.js:27:12)
    at /Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/command.js:311:20
    at initializePromise (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:523:7)
    at new Promise (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1017:35)
    at Class.validateAndRun (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/models/command.js:263:12)
    at /Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/lib/cli/cli.js:183:28
    at tryCatcher (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:326:21)
    at invokeCallback (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:498:33)
    at publish (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:484:9)
    at flush (/Users/_my_user_/Dev/_some_private_path/_playground/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:2441:7)
    at processTicksAndRejections (internal/process/task_queues.js:79:11)

=================================================================================

As you can see the #!/usr/bin/env node seems to be the problem, that I can temporarily fix by commenting the line.
I tried to reinstall my node_modules, my EmberJS dependencies, Node.js... Still have the problem.
I never ever had this issue in any of my projects for years... This is also weird as I still have other files that use the same shebang:

@MrChocolatine that seems frustrating. I don't know what ember does with your node_modules folder but I think it's worth filing with them.
I'm not sure what we can really do within this package; the shebang line needs to be there so the CLI works, so we can't really change our code to fit Ember. I'll close this because I don't really see an actionable path forward.

I didn't mean to "fit Ember" but maybe the concatenation or whatever could possibly be faulty. I am still investigating what is wrong (and again, I am was not convinced your package was the guilty one).

It's strange because the only file with the shebang is our cli.js - which is only referenced as a bin, not the main key or anything, so require('sort-package-json') should work absolutely fine. Definitely some tool is traversing node_modules in a non-standard way.

Ahh - also it looks like you're using an outdated version of sort-package-json which used to have index.js stand as both CLI and Library. If you update it might fix the problem.

I tried to clear and rebuild all my dependencies and everything seems to be back to normal now...

rm yarn.lock
rm -rf node_modules tmp dist
yarn cache clean
yarn install

What I still don't understand is that I simply rebuilt everything, I still have<EMAIL_ADDRESS>in my yarn.lock, but now it works... Quite strange 🤔 .

Thank you very much for your time @keithamus.


Documentation changes

Added django.contrib.sites and SITE_ID = 1 to the documentation.

Coverage remained the same at 90.903% when pulling 51dae22bd6d60a07e5c7dade6d3558b0e2b1073e on cmwaura:master into 2d7a77d3a857bde299c85349db3ff2cf764aeab5 on justquick:master.


OpenSprites Logo text

The OpenSprites logo is like so:

    OPENSPRITES

I know in some concept illustrations, we had the "OPEN" part bolded (<-- that's not a word :P). This bold tag isn't doing anything. Are we going to keep it bolded? If not, the  tag isn't needed.

If it means anything, I don't know it. I do think the bold thing made the logo looks better (kinda easier to read :P) but I prefer this syntax. (because the bold thing is for style?)
HTML:

    OPENSPRITES

CSS:
#some-id {
    font-weight:bold(or any number);
}

Also because the font-weight CSS selector is more customizable.

@Rumanti True, but what I mean is that you can't even see the bold. Instead of SPRITES, it shows up as OPENSPRITES.

Oh, sorry. I thought you meant "are we going to keep this bold-thing style?".

I think it might be something with the font. Can someone smarter than me give some input? :stuck_out_tongue:


Update micro/rcache version

Currently if you run the unit tests with race detector you will get a race fixed on the latest commit of the rcache lib.
I think to fix this you just need to tag rcache with a new version and update the go.mod

Ok thanks, will do the update now.

thanks, I saw that you have done it.
Closing the issue


npm script flow.compile:system not working on windows

npm run flow.compil.system on windows causes following issue
><EMAIL_ADDRESS>flow.compile:system C:\Users\divyjain\Documents\GitHub\ng2-formly
> ./.config/bundle-system.js

'.' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "flow.compile:system"
npm ERR! node v5.7.0
npm ERR! npm  v3.6.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>flow.compile:system: `./.config/bundle-system.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>flow.compile:system script './.config/bundle-system.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ng2-formly package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./.config/bundle-system.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ng2-formly
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ng2-formly
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\divyjain\Documents\GitHub\ng2-formly\npm-debug.log

To fix this problem created bundle-system and bundle-system.cmd in .config folder and update npm script location but it failed with similar error. But surprisingly it works when i move bundle-system.cmd to node_module/.bin

simple change package.json script tag to this.
    "flow.compile:system": "node ./.config/bundle-system.js",


Improve metrics coverage across ADAMContext load methods

Actually, even better, I found today that many of the _.instrument calls are misapplied.

Why are there some problems in ADAMContextSuite.scala?
I run it in local (windows system), Is the reason my environmental configuration error?

Adam-0.21.1-SNAPSHOT and adam-0.21.0 both happened.

Fixed by #1487


Typos in example on the Rust home page

Hi, although these are just minor typos, since this is prominently displayed on the main homepage (https://www.rust-lang.org/) and for each language, it might be worth fixing it:

The Arabic phrase has the exclamation mark to the right, instead of the left.*
The Czech phrase has no exclamation mark at all.

(*Additionally, maybe related, that "!" comes finally out on the very right of the output [supposed to be written in two steps from right to left, so that's slightly nontrivial...]. I assume somehow it is not in "RTL mode" in the string. But anyway, putting it to the left should (?) resolve the issue.
[Hm. Having tried some edits, that seems to be a resistant problem... Whether I put a "!" to the left or to the right, in a separate string or in a format string with " {} " or " {} {} ", or whatever, it always end up to the right! This is weird!!]
So this example is a kind of disproof of the statement itself, sine the RTL text can actually (almost) NOT be edited, at least in my Chrome browser: juts try to delete that "!"...)
HTH.
-M.

I think this is an issue with the embedded editor they're using (third party called Ace (Ajax.org Cloud9 Editor)); if you notice, you can move the cursor 3 spaces to the left and hit delete and it will delete the ! mark. I tried something similar on the third party's own website and got the same results. I'm thinking this is an encoding issue with the editor.

I agree, but this only concerns the side note (* ...), not the main bug report.

We are going to be re-doing the Rust website very soon, and it does not have this code example any more. I'm going to leave this open since it's technically a bug, and if anyone wants to fix it, please send in a PR, but it's likely to not get fixed until it's removed.


regression in "label faces" feature

With pull dated 2022-12-26
I want to associate a face to a known person. When I type the first letter all already known names disappear from the list. I have to type the full name to see it reappear. Easy to reproduce as well as with a brand new data base...

Doe's anyone share my concern? I tested it on demo base and it's the same...

Doe's anyone share my concern? I tested it on demo base and it's the same...

With demo1, or 2?

But yea, i think i know what you mean, the method that i always used, is to do a ctrl + f, to find the name of the person.
Because when you add it in the input, that input always stays, and it doesnt resets itself after searching for a person.

With demo2. My method was working before and I would appreciate to see it working again ;-)

I found what the issue is. will fix that.


Add Dockerfile to web service

#3065
A small step towards continuous deploys, where we can get
pre-built web service images from quay.io.
Took dockstore/compose_setup/templates/Dockerfile_webservice.template
and modified to make this file, with the main difference being
that the webservice JAR is built instead of being pulled from OICR
artifactory.
Arguably shouldn't have dockerize waiting on postgres in here; OTOH
the web service is useless without Postgres container. Also there
was a comment about not hard-coding the dockstore_logs directory, but
I left it hard-coded. We can revisit when we make the corresponding
compose_setup changes.
I have created
https://quay.io/repository/dockstore-testing/dockstore-webservice and
it images have been made against this branch.

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 5

Coverage increased per file
===========================
+ dockstore-webservice/src/main/java/io/swagger/model/ExtendedFileWrapper.java  25
+ dockstore-webservice/src/main/java/io/dockstore/webservice/permissions/Permission.java  26
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/ChecksumConverter.java  39
+ dockstore-webservice/src/main/java/io/dockstore/webservice/SimpleAuthenticator.java  32
+ dockstore-webservice/src/main/java/io/dockstore/webservice/languages/NextflowHandler.java  7
+ dockstore-webservice/src/main/java/io/dockstore/webservice/permissions/sam/SamPermissionsImpl.java  80
+ dockstore-webservice/src/main/java/io/dockstore/webservice/languages/WDLHandler.java  18
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/tooltester/ToolTesterS3Client.java  32
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/dag/ElementsDefinition.java  100
+ dockstore-common/src/main/java/io/dockstore/common/NextflowUtilities.java  72
+ dockstore-webservice/src/main/java/io/dockstore/webservice/permissions/InMemoryPermissionsImpl.java  25
+ dockstore-webservice/src/main/java/io/dockstore/webservice/languages/LanguageHandlerInterface.java  46
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/tooltester/ToolTesterLog.java  50
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/Checksum.java  30
+ dockstore-common/src/main/java/io/dockstore/common/PipHelper.java  45
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/DAGHelper.java  100
+ dockstore-webservice/src/main/java/io/dockstore/webservice/permissions/PermissionsInterface.java  12
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/tooltester/ObjectMetadataEnum.java  90
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/GoogleHelper.java  12
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/JsonLdRetriever.java  91
+ dockstore-webservice/src/main/java/io/dockstore/webservice/CustomWebApplicationException.java  25
+ dockstore-webservice/src/main/java/io/dockstore/webservice/permissions/sam/SamConstants.java  66
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/ZenodoHelper.java  11

See the complete overview on Codacy

Arguably shouldn't have dockerize waiting on postgres in here; OTOH
the web service is useless without Postgres container. Also there
was a comment about not hard-coding the dockstore_logs directory, but
I left it hard-coded. We can revisit when we make the corresponding
compose_setup changes.

If I recall correctly, some of the thoughts I had on this at the time were:

The webservice will repeatedly crash without a database instead of waiting, clogging up the log with verbose logging messages
I wished that docker_compose had a way of saying, "start this thing when this dependency is ready ... not just when this dependency has been kicked off", if it has something like that now, that could replace Dockerize

I don't recall if there were other issues

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy

Codacy suggestions seem good.

I have fixed the codacy issues except the one for pinning the versions for curl, vim, etc. I figure since they are tools, we should have the latest available. But I'm willing to be convinced otherwise.
I did pin the JDK version.


Authentication issue on iOS 14

The package works fine on iOS 15. But when trying to authenticate on iOS 14, the view cannot be closed and there is just a white blank. See video below:
Code:
ContentView() .enableGameCenter()
https://user-images.githubusercontent.com/20157293/153199958-76157f97-e6b9-415e-860b-6afdb112e506.mp4

Thanks for the report, I'll check this out!

I've tested on iOS simulator iPhone 6 iOS 14.5 and could not reproduce this issue.
Do you have any more details?
Maybe you can set a breakpoint in GameKitAuthenticationController.init inside the changeHandler. That changeHandler is called by GameKit when the authentication state changes. If anything could cause this issue, it'd be in that change handler.


Why @ApiResponse not support custom responseCode?

in general,developers need define own responseCode not http standard code，do you have plan to support it -.-

You can use any integer code.


pos_longpolling/pos_multi_session: [FIX] various longpolling issues

This fix also dependes on a timeout in the odoo core bus module...

Timeouts to protect deferred updates, if for any reason it takes longer than 3 seconds, the UI blocks with the turning circle suggesting you to take a coffee, which is pretty annoying.
Network is on: Just double check and update after the call so we have more timely feedback.
Randomness: Just avoid thundering heard in any possible given instance.

@yelizariev Could you have a look at this one? IIRC, it caused several hangups in our implementation while the server was not reachable...

Hi guys, sorry, I don't want to pressure, but this is the last bit I would like to see included upstream before rebasing my own code... We surfaced this problem in the case of a unreachable network and it was quite annoying, you can imagine... I'd like to make sure this cannot happen or become an oversight in any rebase...

Wow, thank you! That was quick!! :smile:

@blaggacao We have the error

Oh, sorry, must have been a regression. I have this code in production for some time now...

Fixed here https://github.com/it-projects-llc/pos-addons/pull/634/files
We are planning to make some refactoring there later

Thanks! And again, sorry for the regression!


#10694 do not escape dbgeometry

We need better type check.

What OTHER types need to be quoted as strings?
Can we just check for ' character in the beginning of strValue?

We need better type check.

What OTHER types need to be quoted as strings?
Can we just check for ' character in the beginning of strValue?


Send JSON parameter that has an array field

Basically my question is similar as this one
I have an object like so:
struct Service: Codable {
        let id: String
        let completed: Bool
}

my Moya task has the following parameters:
return .requestParameters(parameters: ["work_id" : work.id, "services": work.services],
                                      encoding: JSONEncoding.prettyPrinted)

As you may guess work.services is an array [Service]. The services inside the JSON should be like:
services: [
    { id: String,
    completed: Boolean },
    ...
],

But I'm getting *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (_SwiftValue)'
How can I make it work?

The encoding JSONEncoding.prettyPrinted uses the given [String: Any] and converts it to JSON using Apple's JSONSerialization.data(withJSONObject:).
Here is the doc of this function:
If obj will not produce valid JSON, an exception is thrown. This exception is thrown prior to parsing and represents a programming error, not an internal error. You should check whether the input will produce valid JSON before calling this method by using isValidJSONObject(_:).
Your Service is not a valid JSON Object, hence it crashes.
However, as you Service object is Encodable you can use the task .requestJSONEncodable instead.

Thanks a lot @amaurydavid I didn't know about the .requestJSONEncodable. For those that don't wanna extend their object to Encodable you can map an array to a dictionary. In this case would be like so:
let dict = services.map { ["id": $0.id, "completed": $0.completed] }
return .requestParameters(parameters: ["work_id" : work.id, "services": dict],
                                      encoding: JSONEncoding.prettyPrinted)

it does also works


change padding, opacity and line spacing

Work required no 2. from the tickets still requires to be implemented.
I also think we could get the text a bit smaller, it is smaller on both the subtitles, charts and heatmap table popups

The test is smaller now. Sonification tooltip matches the styles for the single value tooltips. HeatMap tooltip styling seems impossible.


fix(1509): SystemJS module resolution failure.

fix(agm): AgmFitBounds was being referenced as an absolute path. Causing module resolver SystemJS to fail.
fixes #1509

in "version": "1.0.0-beta.5" this issue is present

The fix is here, it works, just has to be merged. Or I suppose you can use my fork. I would recommend not using this library, it is not maintained... as evidenced from above "Stale".


Exception when message is deleted before navigator finished adding reactions

when navigator runs, and it adds the stop button, if you click it before all the reactions have been added it will cause an error
hikari.errors.NotFoundError: Not Found 404: {"message": "Unknown Message", "code": 10008} cause it tries to add them to a message that no longer exists
Original

So would it be good if you would check that the message still exists before adding the reactions?
For this method, it could check if the message exists, every time it is about add a reaction.
Or, we could implement this in another way. When you press the stop button, it would check if all the reactions are added to the message or not. If the reactions are all there, then it could safely delete the message as it won't throw an exception.
Let me know what you think.

This can just be an easy fix by handling hikari errors. There is not need to check if the message is there after every reaction, at it is too many requests

https://github.com/tandemdude/hikari-lightbulb/blob/7f7131bf22f6a1e4abfacfe73799d47f7b737f1a/lightbulb/utils/nav.py#L231-L232
This line raises the hikari.errors.NotFoundError as the message was deleted. So just simply using a try/except for the error should fix it.


Fix duplicate url issue for different casing and .git suffix.

If two dependencies are declared that use different casings in the spelling, for example.
.Package(url: "https://github.com/swiftx/s4.git", majorVersion: 0, minor: 2)

And somewhere else in the dependency tree:
.Package(url: "https://github.com/SwiftX/S4.git", majorVersion: 0, minor: 2),

Then there will be a collision
fatal: destination path '/path/to/project/vapor/vapor/Packages/s4' already exists and is not an empty directory.

error: Failed to clone https://github.com/swiftx/s4.git to /path/to/project/vapor/vapor/Packages/s4

By normalizing all urls to lowercase and requiring .git suffix, we can ensure that these types of collisions do not occur. Please let me know if you have any feedback on things I should adjust or if you'd prefer an alternative approach to the solution.

URLs are case-sensitive: http://www.w3.org/TR/WD-html40-970708/htmlweb.html

There may be URLs, or parts of URLs, where case doesn't matter, but identifying these may not be easy. Users should always consider that URLs are case-sensitive.

GitHub URLs are not, but to solve this we need to either specialize case providers, or normalize the URL by doing a HEAD request.

@mxcl Thank you for the quick response. It sounds like I was a bit too hasty about my solution here. I've filed a bug https://bugs.swift.org/browse/SR-1195 to discuss the best course of action.

Logan

@LoganWright @mxcl
https://monosnap.com/file/ntQuHlvS0JfwvUXe55Vg5EsTRZPocE.png
Next response is 200.
So algorithm very easy.
But what to do with ssh urls? Like git@github.com:Zewo/clibvenice.git

I would be happy with special casing github for now.
No .git suffix though, unless you want it to normalize to that. I feel the dependency URLs should be the ones you see in the URL bar.

Ugh... special casing GitHub doesn't sound like a good solution to me, developers can always use the "canonical" casing that GitHub reports and not hit this bug.
If we absolutely have to fix this soon, I would rather we go the other direction, and always assume packages with the same case-insensitive name are equivalent. This would solve the issue fairly generally -- it would prevent people from using multiple packages with alternate casings to be sure, but I'm not even sure that is a bad thing. :)

developers can always use the "canonical" casing that GitHub reports and not hit this bug.

I'm saying that if it's a Github URL then lowercase it (or whatever). So maybe I don't understand your point.
Anyway, thinking about it, being case insensitive in general is fine. The edge case is when there are two packages with the same spelling and separate case rather than the other way around.

@swift-ci Please test and merge

@mxcl @ddunbar
It wouldn't be too difficult for me to jump into the equals function and set it to compare urls case insensitive. I'll do that now.
Would you prefer it to check first if string contains github.com, or should it compare all domains as case sensitive?
I think it should apply to all domains since there'd likely be conflict in most git systems that haven't disabled case insensitivity. (I may be outdated, but on the git I have installed, it wouldn't allow two repositories of different casings, even if they were in fact different.).
Also follow up, master has changed, does this repository prefer rebase or merge workflow?

I've already set this one to merge. Do you consider what is there inadequate?

@mxcl I didn't realize that, my apologies. I do think the solution prior to today's commit is inadequate. Mostly because it will break case sensitive domains such as bitbucket. I think moving the insensitivity to == instead of assigning on initialization will achieve the desired result w/o breaking sensitive domains.
Let me know what you think.

@mxcl Is there something else you'd like me to add to this branch? I moved the lowercase check to equatable, I could also add a condition that the url contains github.com if you'd prefer.

@swift-ci Please test and merge

Future additions:

git: / http / https should be calculated if identical, OR we should error for anything that is not https (or something like that) since the protocol used should be implementation decided (with the user having the option to override) really the URL is just an identifier.
normalize slashes

/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux@2/swiftpm/Sources/PackageDescription/Package.swift:213:13: error: value of type 'String' has no member 'hasSuffix'
        if !url.hasSuffix(".git") {
            ^~~ ~~~~~~~~~

Import libc to fix.

@mxcl updated

@swift-ci Please test

Yes, PackageDescription could depend on libc but I think we'd prefer to avoid the pain there.
We should move this code to PackageType probably.

Tracking efforts for this here https://bugs.swift.org/browse/SR-2917


Support on-demand revalidatePath and revalidateTag

Currently for ISR, revalidatePath and revalidateTag are not supported because when ISR was implemented open-next didn't support them. Now open-next supports these features, cdk-nextjs just needs to implement them from an infrastructure perspective including adding a DynamoDB table to keep track of revalidations. This has already been implemented by SST's NextjsSite which can be used for inspiration. See release here.

@kevin-mitchell, since you implemented ISR for this project would you be interested in supporting this similar feature?

Closed in #145 thanks to @kevin-mitchell. Great work, Kevin!


Fixing orientation issue

Fixing bug
“Branch views are not shown in a  session after Branch view is
dismissed by orientation change.”
@aaustin @Sarkar @EvangelosG

:+1: makes sense to me.

:+1:


Autofac works, rest are broken?

Using the standard RC web template in VS 2015 RC, it seems that only Autofac works while other 3rd party DI containers fail in one way or other. The simple test is Open a new project > customize DI > Run > Access Log in from menu
For example, trying this code in public IServiceProvider ConfigureServices(IServiceCollection services), here's what other DI containers output:
SimpleInjector
var container = new Container();
container.RegisterAll(services);
container.Register(() => new SimpleInjectorServiceScopeFactory(container)); // this doesn't seem to matter for running the default pages though. the error occurs regardless
return container;

throws
:(  Oops.
500 Internal Server Error
System.InvalidOperationException
No service for type 'Microsoft.AspNet.Hosting.Builder.IApplicationBuilderFactory' has been registered.
at Microsoft.Framework.DependencyInjection.ServiceProviderExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
at Microsoft.Framework.DependencyInjection.ServiceProviderExtensions.GetRequiredService<T>(IServiceProvider provider)
at Microsoft.AspNet.Hosting.HostingEngine.EnsureBuilder(HostingContext context)
at Microsoft.AspNet.Hosting.HostingEngine.Start(HostingContext context)
at Microsoft.AspNet.Loader.IIS.RuntimeHttpApplication.ApplicationStart(IHttpApplication application)
at Microsoft.AspNet.Loader.IIS.HttpApplicationBase.InvokeApplicationStart(IHttpApplication application)
.NET Framework version 4.0.30319.0   |   Microsoft.AspNet.Loader.IIS version 1.0.0-beta4-11565   |   IIS version 10.0.10046.0 (fbl_srv2_iis_dev(sujitn).150324-1423)   |   Need help?

Ninject
var kernel = new Ninject.StandardKernel();
kernel.Populate(services);

return kernel.GetService<IServiceProvider>();

throws:
An unhandled exception occurred while processing the request.

NullReferenceException: Object reference not set to an instance of an object.
Microsoft.Data.Entity.Internal.DbContextServices.get_DataStoreServices()

Stack Query Cookies Headers Environment
NullReferenceException: Object reference not set to an instance of an object.
 All of them implement IServiceProvider so theoretically, they should all work or all fail in same manner. Not sure why they fail and that too with different errors.
Thoughts?

The Ninject issue could be #247

For using SimpleInjector with vNext, read this thread.

There's an official Autofac package for this DI system that you can grab from here: https://www.nuget.org/packages/Autofac.Framework.DependencyInjection
Can you try the latest build of the official Autofac package?
There is unfortunately no official Ninject support yet.

Autofac wasn't broken in the first place. It worked without any modifications or workarounds. Are you asking about testing this in general?

Ah, didn't realize Autofac was already fine.
What in particular is broken? Please note that we're in the process of removing the other sample implementations from this repo in https://github.com/aspnet/DependencyInjection/pull/266.

@Eilon I believe I noted what else is broken (and how) in my first post itself. As @Tragetaschen notes, Ninject issue could be due to #247 and for SimpleInjector, please refer to my earlier comment.
Not sure if you're looking for anything more.
If you remove other sample implementations, that'll at least remove the suggestion that others are compatible; but it still won't change the fact that they are not 100% drop dead replacements. Not sure about Ninject but for SimpleInjector, there is an interesting debate going on here.
Anyway, I guess this issue can be closed with the final thoughts that only Autofac was built as a drop dead replacement (atleast as of today), rest of the DIs may need some work.

@mrchief sorry, I wasn't sure if some issues had been resolved since this issue was originally opened - more than 2 months ago.
The system is nonetheless designed to work with most IoC's, even if we don't have working code for many of them. We did have Autofac, Ninject, and I believe one or two others at one point that were all demonstrably compatible with the requirements here.
We plan to reach out to more IoC authors and possibly lend a hand wherever possible.
We're happy to link to compatible IoC's from the README in this repo.

I wasn't sure if some issues had been resolved since this issue was originally opened - more than 2 months ago.

I haven't heard anything so I assume the status quo remains.

The system is nonetheless designed to work with most IoC's, even if we don't have working code for many of them. We did have Autofac, Ninject, and I believe one or two others at one point that were all demonstrably compatible with the requirements here.

Sorry to say, but this is a Unicorn at this point. We need PROOF! :smiling_imp:

We plan to reach out to more IoC authors and possibly lend a hand wherever possible.

:+1:

We're happy to link to compatible IoC's from the README in this repo.

Yes please!! That'll be a great help!

:one: :corn: ? :trollface:
We did have proofs-of-concept with several IoC's, and did a lot of research too! But, yes, talk is cheap, and without running bits it's not much to go on.

We will reach out to the various IoC container authors. Nothing to track here.


Fails consistently with "failed to process type: 68 [Numerical result out of range]"

I'm trying to use this addr2line as an alternative to the one provided by bin-utils. However, every time I try to run it, it fails with "failed to process type: 68 [Numerical result out of range]".

That's not an error I am familiar with, and a web search indicates that is an error returned by perf. Please provide steps to reproduce.

Download the trace from here: https://fastupload.io/3GTvyFVnIwgXGtW/file (even compressed, it takes up more than the >25 MB limit). Then run perf report -i perf.txt --addr2line=$PATH_OF_RUST_ADDRLINE. The problem should show up.

Interestingly, --no-demangle allows it to work.

I'm not sure that the trace alone is enough. I think I would need the DWARF debug info too. I can't spend time debugging problems in other tools. You need to reduce it to a problem that requires running addr2line alone.

Can't reproduce. The trace isn't enough, I need the DWARF debug info.


[REEF-902] Create .NET job resource uploader

This addressed the issue by:

Creating interface IJobResourceUploader
Adding a legacy implementation by calling into Java
Add test for the the legacy implementation

JIRA:
REEF-902

This looks good, only minor comments. @anupam128 Could you resolve the conflicts?

Thanks @afchung ! I have resolved the conflicts and made the changes.

@anupam128 Seems like there are still conflicts. Can you take a look? Thanks!

@afchung I have resolved the conflicts and made changes.


Add an option for hour labels format on the time axis

Checklist
Please put "X" in the below checkboxes that apply:

[ ] If committing a change of production code, I have tested it in different browsers (Chrome, Firefox, Safari).
[x] If committing a new feature, I have first submitted an issue (Please note: you are free to open PRs for non-issued features, but opening an issue increases your chance of a successful PR).
[ ] If committing a new feature, I have also written the appropriate tests for it.
[x] I have tried to build the feature in a way, that it does not cause any breaking changes for others (unless
agreed upon in an issue).

Happy to write a test for this, haven't looked into it yet.
Premium

[ ] I'm a Schedule-X premium user

This PR solves the following problem**.
See #621.
How to test this PR**.
For example:

Specify timeAxisFormatOptions: { hour: '2-digit', minute: '2-digit' } in weekOptions in the calendar config.
Now the hour labels look like: 08:00 if the locale is de-DE.

Nice. Good job!
A unit test for this feature would be nice, but I could add it too if you want. Other than that, there's a TODO left in your code and a commented out line, that I would rather keep :)

Oops, sorry! I accidentally added some files where I was experimenting with other changes. They were not intended for this PR. (I might send other requests later if it seems sensible. 😅) Will clean it up!

Added a test file for the TimeAxis component and included a test for the new feature in it.

I pushed a little fix to the last test. Apparently 12AM turns into 24:00 instead of 00:00 when using the formatting options:
{
  hour12: false,
  hour: '2-digit',
  minute: '2-digit',
}

Now everything is green. I can try and make a release tomorrow :)

I pushed a little fix to the last test. Apparently 12AM turns into 24:00 instead of 00:00 when using these formatting options:
{
  hour12: false,
  hour: '2-digit',
  minute: '2-digit',
}

Wow, this is a bad test then. It was passing on my machine, and now with your change it's failing.
There is an inconsistency in how this case is handled across the implementations:
new Date(0, 0, 0, 0).toLocaleTimeString('en-US', { hour12: false, hour: '2-digit' })

This returns '00' in node and firefox for me, but '24' in chrome! I dunno if there's some other hidden parameter which affects this, or this is an actual inconsistency in different javascript engines.
I amended your commit and restricted the test to avoid this case.

about displaying location for time grid events, I think that would also make sense, and I plan on introducing that for v2.
But if you need it now already, we could also make it configurable, that it should be displayed if the property exists on an event, and it is configured to be shown for the time grid in general

Yeah, this is how I was planning to handle it in a future PR. 😅  We need it for our use-case.
Also, thank you very much for reviewing this so quickly, and for the very productive comments!

In case you're wondering about the force push: I just rebased on main, because of some changes in the E2E test runner that forced me to fix the browser dimensions


Invalid cnpj cpf classifier tweaks

Renamed test file to match the other ones and added to more to tests.

Coverage increased (+0.9%) to 92.241% when pulling ba85b5dbda3255dfe11b952499daaa0eaf6d06bf on jtemporal-invalid-cnpj-cpf-classifier-tweaks into 19195d925df40abc041784cabe98b1bd33051ed9 on master.


fix: using typename in section

Why are these changes introduced?
Addresses ENG-8700

What is this pull request doing?

Update TypedFields names to reflect the new name in the schema
Update the sections to use __typename and a switch statement to render components
Remove unecessary __typename check in Article and Links components

How to Test

npm run dev in examples/typedfields
Checklist

[x] This Pull Request aligns with nacelle-js' Code of Conduct.
[x] You can follow your own "How to Test" instructions and get the expected result.
[x] Screenshots, videos, etc. in the PR description are free of brand names and sensitive details.
[ ] Created a changeset (if the change should appear in a changelog).
[ ] Updated the README.md with documentation changes (if applicable).

Nice! Everything's working as expected.
But...I think perhaps I wasn't clear about something when we were discussing <Section /> yesterday. While the <Section /> component with the switch definitely works in this case, I don't think it's a pattern that customers should take inspiration from, because in a "real" project it will import many unused components into a page that <Section /> is used in.
Instead, I think we can do without with <Section /> component altogether, and add the switch handling to the page template. That way, any page template can define which components it will use. It shouldn't make a bit of difference in this particular project, but I think it might be helpful to people using this project for inspiration.
Please let me know if you disagree, @KrisQ!

Thank you for clarifying @NWRichmond, it was a pretty simple change that should now be in!


Service binding for Kyma service instance

Description
Provide a service binding for Kyma Runtime instance. The binding should contain all the information to connect to the runtime (KUBECONFIG or all the information required to build a KUBECONFIG). The binding request can create TokenRequest and return the token in the binding.
Reasons
Users can create Kyma Runtime instances with API or BTP CLI. But the instance cannot be accessed without user being authenticated (OIDC flow). Therefore any automation flow that involves provisioning Kyma and deploying any workload there cannot be easily implemented. The only way to do that is to use custom OIDC provider, but that option is not easy to set up and use.
Attachments
Other way to achieve the automation would be https://github.com/kyma-project/kyma/issues/18305

the static bootstrap token created at the provisioning is extremely short living. (~5min)

POCs:

create a technical user in BTP and with BTP CLI create Kyma instance and Kyma binding
create a technical user in BTP and create btpOperator instance and then with clientCredential create Kyma instance and Kyma binding

FWIW, in order to address https://github.com/kyma-project/kyma/issues/18092 in our project we have come up with a script that

Uses the kyma human user kubeconfig to create an admin service account
Generates a kubeconfig containing the service account secret

The human user has to be a cluster admin in order to be able to create the service account though.

Next steps should be discussed with @pbochynski @PK85 @piotrmiskiewicz.

@PK85, @tobiscr wouldnt' this gardener's feature offer an alternative, shortcut solution?
https://github.com/gardener/gardener/blob/master/docs/usage/shoot_access.md#shootsadminkubeconfig-subresource

Another meeting with CIS team needed

MVP proposal sent to CIS team, awaiting timelines

MVP proposal, awaiting for CIS team: https://wiki.one.int.sap/wiki/display/kyma/Kyma+Environment+Service+Binding+-+MVP+proposal

Descisions after a meeting with CIS team:

binding ID - will be generated by ERS and the user will not have to send it to the create binding API
context - will be filled with the user id and origin (same as in create instance)
parameters - user will provide that as part for the ERS payload and no schema validation will be done on the parameters
bindable - ERS will validate the service and plan bindable property, if it is false, the binding request will be rejected.
rotate - will not be supported, the user will have to delete and create a new binding.
service and plan IDs - will be calculated by ERS (fetched form the service instance), the user will not have to send it as part of the payload.

Communication from CIS (11.08.2024):
A few updates from ERS side:

I saw that the user is sent as part of the headers in Service Instance creation, so we will align to it
ERS is acting as a proxy - meaning - we will not save anything on our side (from bindings perspective). this leads to the following:

a. The API user (call to ERS->createBinding) will need to pass the binding UUID (he is the one that manages the binding, and needs to know the ID)
b. We will support async creation, but polling will be on the API user's side (since we cannot poll on our side) - the user that creates the binding (and knows the ID), will request polling on that binding, from us
c. We will expose also API for polling last operation from the service broker

So, in terms of payload for service broker from ERS:

binding ID - will be sent by the user, we will not generate since we can't save it on our side
context - no need to send it, we will fill the user id and origin (same as in create instance) as part of the headers
parameters - user will provide that as part of the ERS payload and no schema validation will be done on the parameters (see bellow)
bindable - ERS will validate the service and plan bindable property, if it is false, the binding request will be rejected.
rotate - will not be supported, the user will have to delete and create a new binding.
service and plan IDs - will be calculated by ERS (fetched form the service instance), the user will not have to send it as part of the payload.
Headers - we will add user origin and email, as an encoded string in "X-Broker-API-Originating-Identity" header (same as in service instance creation)

And my answer:

about user id we are getting that as a part of the context for SI operations:

    "context": {
        ...
        "user_id"<EMAIL_ADDRESS>    }

About UUID, when user creates Service Instance, the ID is generated by ERS. I think it should be still generated for user. There is as well a way to list all Environments list,

Areas:

kcp CLI and REST API for runtime/bindings
create kubeconfig
broker API compatibility provisioning API/OSB API requirements
we need implement DB table and functionlity aroud service bindings

@pbochynski Is it a right approach, for the runtime implement a service binding to provide the kubeconfig ? Usually, service binding is for the services.

@gowrisankar22 Service Bindings APIs are right now under implementation for Provisioning Service by CIS team. Cheers

@pbochynski Is it a right approach, for the runtime implement a service binding to provide the kubeconfig ? Usually, service binding is for the services.

Exactly - Kyma runtime is a service and this is the long-term strategy. You can already provision Kyma from Service Marketplace in BTP cockpit.

Final meetings with CIS team (Zahi)
Hi, we should talk about three things.

Add user_id (clientid from Cloud Management Service binding) to the context in create binding request (PUT).

Set accepts_incomplete to false, because we've decided to use synchronous responses.

When binding expires we are removing entry form KEB database. Let's say user created 20 bindings and they all expired. In this case there will be no entries in KEB database, but get all bindings endpoint will return 20 binding with status OK. When user will try to get Credentials for one of them he will receive an error. Possible solution:
KEB will return expires_at field in Binding Metadata during binding creation. You can save this field in the database, and return only valid bindings to user.

There are two ways of getting an access token for SAP Provisioning Service API:

Using Password grant type

curl -L -X POST '<uaa_url>/oauth/token' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-u '<clientid>:<clientsecret>' \
-d 'grant_type=password' \
-d 'username=<user email>' \
-d 'password=<password>'

During binding creation KEB receives body with context:
context: {
   "email":"email",
   "origin":"origin"
}

Context should be saved to database as created_by = email + origin.

Major decisions about implementation details: https://github.com/kyma-project/kyma-environment-broker/issues/1198#issuecomment-2404880767

Meeting notes 16.10.24

Service Binding states are not required, we can delete objects by determining expires_at and kubeconfig fields. If expires_at is older than current time SB should be deleted,
kubeconfig value determines SB state. If it's empty, SB is in an unknown state, it may be in progress (800 ms max) or error,
the first step in SB provisioning is creating a record in DB with empty kubeconfig which is populated in the last step,
the first step in SB deprovisioning is the cleanup of resources (ServiceAccount, ClusterRole, ClusterRoleBinding) in SKR, the last step is SB removal from DB.

10.10.2024 - Summary from the meeting about using only token requests from SA from SKR and idempotent behaviour: https://github.com/kyma-project/kyma-environment-broker/issues/1198#issuecomment-2404880767

10.10.2024 - Summary from the meeting about using only token requests from SA from SKR and idempotent behaviour:
Legend:
BindingID: means: BindingId - InstanceID pair on KEB side
Contract between Provisioning Service and KEB bindings:

[ ] 1) KEB bindings returns 201 or 200 if everything ok, then Provisioning Service persist binding on their side
[ ] 2) KEB bindings returns 400, 409, 500 if something wrong happen and then Provisioning Service DO NOT persist binding on their side, just pass error to the user

KEB bindings responses details: @MarekMichali

[x] 1) we return 201 when BindingID was not existing, and was created with success
[ ] 2) we return 200 when BindingID WAS already existing, input parameters are the same and was created with success (in_progress,error is not success)
[ ] 3) we return 400 when invalid input params provided  [JP - question - including not existent InstanceID?]
[ ] 4) we return 409 when BindingID already exists but input params different
[ ] 5) we return 500 if KEB itself is not able to finalize binding creation
[x] 6) we return 200 on DELETE when bindings exists, [JP - question - 410 when does not exists?  - it seems that DELETE is not supposed to be idempotent] [MM - OSB says 410 if not exists]

KEB implementation about handling binding related resources, like ServiceAccount, ClusterRole, ClusterRoleBidning

[x] 1) ~we need to have internal binding state representing ok, in_progress and error states~ - The state is represented by kubeconfig field - non-empty kubeconfig: binding created ok; empty kubeconfig: otherwise
[ ] 2) probably we have two calls to db, at the begining setting in_progress state and later at the end ok or error at the beginning with an empty kubeconfig, and setting the kubeconfig when all is done/created without error
[ ] 3) to eliminate temporary issues when calling SKR to create SA, CR, CRB we need to add retries (2,3 attempts) every 1,2 seconds  [JP - it seems that during Wednesday meeting we decided otherwise]
[ ] 4) for whole binding creation we have internal overall timeout set to 15 seconds
[ ] 5) If we have expired bindings we do not return them when GetBinding is comming from Provisioner Service. We just keep that binding internally to be cleaned up by binding-cleanup-job later.
[x] 6) we have limit up to 10 valid bindings (expired ones do not count)
[ ] 7) delete Bindings enpoint deletes all sub resources, if some of them already not exist go to next one and send success code
[ ] 8) if get binding is called for ID that is expired or error we return not found status code

KEB binding-cleanup-job details

[ ] 1) responsible to remove expired bindings (we call deletion binding endpoint with some infromation probbaly in header that our job call it, see other jobs how it is implemented. Delete binding endpoint must log it)
[ ] 2) responsible and binding in error state (we call deletion binding endpoint with some infromation probbaly in header that our job call it, see other jobs how it is implemented. Delete binding endpoint must log it)
[ ] 3) we call job once per day with nice log how many and what type of deletions happen (expired, errors, total)

@PK85
Is it planned to support creation of  kyma environment bindings via

btp cli
sap btp terraform provider ?

@kwiatekus
BTP CLI and Cockpit was removed from the scope by CIS team. Maybe in the future we can back to them asking about that.

Managing Kyma Runtime Using the Provisioning API of the SAP Cloud Management Service added and ready for review.


In the Unique validation rule, when parameter contains space, ignore space

When use unique validation like this:
$v = \Validator::make($attributes, [
            'name' => 'required|min:1|max:20',
            'keyword' => 'required|min:3|unique:directories,   keyword',
        ]);

        if ($v->fails()){
            throw new \Exception($v->errors()->first(), 500);
        }

You will get a Exception:
Column not found: 1054 Unknown column ' id' in 'where clause' (SQL: select count(*) as aggregate from `target_table` where `   keyword` = "some_keyword")

This pull request will remove all space in validate parameters like '   keyword'.
This issue not only exist in version 5.2, but also exist in versions 5.1 .

Why not just delete the space in your Validator? Any reason for you to remain the space there?

It's can done in my Validator, But  I think some one like add space after "," .  this is a normal habit.

@mlanin thanks


Do not autorun query on tab duplicate

CATEGORY
Choose one

[ ] Bug Fix
[X] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

https://github.com/apache/incubator-superset/pull/8485 added an option in SQL Lab to duplicate tabs in order to iterate on them. When that happens, we don't want to autorun the query, since the user will probably want to change it before running it.
I left the old behavior of autorunning a query when opening it from the query search, though.

TEST PLAN

Tested locally.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@khtruong

Codecov Report

Merging #8577 into master will not change coverage.
The diff coverage is 66.66%.

@@          Coverage Diff           @@
##           master   #8577   +/-   ##
======================================
  Coverage    66.5%   66.5%
======================================
  Files         450     450
  Lines       23117   23117
  Branches     2451    2451
======================================
  Hits        15375   15375
  Misses       7593    7593
  Partials      149     149

Impacted Files
Coverage Δ

...perset/assets/src/SqlLab/components/QueryTable.jsx
59.25% <0%> (ø)
:arrow_up:

superset/assets/src/SqlLab/actions/sqlLab.js
63.13% <100%> (ø)
:arrow_up:

.../assets/src/SqlLab/components/TabbedSqlEditors.jsx
74.81% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78f41b3...e61bd72. Read the comment docs.


Compile everything in compileAllProduction

Groovy compilation seems to be non-deterministic, so
not compiling the Groovy test sources up-front causes
some cache misses later on :(

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Openshift ¨Post commit hook" failed

Builds with openshift online cluster features a validation process after the pods downloaded the source code. The following command tests AllTests out-of-the-box. It can be edited through configuration panel (web console).
./lib/Cake/Console/cake test app AllTests --stderr as of testing with session enabled command line guidelines
It fails after short time, and the build stops, no deployment follows.

Fixed cache issue missing temp folder write access.


Update actions/checkout in GitHub Actions workflows to v3

Updates the actions/checkout action used in the GitHub Actions workflows to its newest major version.
Changes in actions/checkout:

v3.3.0

Implement branch list using callbacks from exec function
Add in explicit reference to private checkout options
Fix comment typos

v3.2.0

Add GitHub Action to perform release
Fix status badge
Replace datadog/squid with ubuntu/squid Docker image
Wrap pipeline commands for submoduleForeach in quotes
Update @actions/io to 1.1.2
Upgrading version to 3.2.0

v3.1.0

Use @actions/core saveState and getState
Add github-server-url input

v3.0.2

Add input set-safe-directory

v3.0.1

Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory
Bumped various npm package versions

v3.0.0

Update to node 16

Still using v2 of actions/checkout will generate some warning like in this run: https://github.com/gimli-rs/cpp_demangle/actions/runs/3291544661

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/checkout

The PR will get rid of those warnings for actions/checkout, because v3 uses Node.js 16.

Thanks.


Paragraph text gets added to list item

When you have a paragraph followed by list (ordered or unordered), the last line of the paragraph gets added to the first list item. Adding an extra  prevents this from continuing until its all part of the list, but still results in an unexpected result.
Input

Start text
2nd line

List item 1

List item 2

Between text
Before unordered

Unordered 1

Unordered 2

result
Start text
1. 2nd lineList item 1
2. List item 2
Between text
- Before unorderedUnordered 1
- Unordered 2

expected
Start text
2nd line
1. List item 1
2. List item 2
Between text
Before unordered
- Unordered 1
- Unordered 2

I'll check it as soon as possible. Thanks for reporting it!

@DaemonInc please, if the issue persists, report it.


Support for Map and Hashtbl

Closing. Whoever needs this can implement this. In addition, I'm not sure what the output would look like.


Changed Padding, Location and similar properties to get the scrollbars back. Fix #224

This is for fixing #224.
I noticed that any small change in the Designer GUI to the MainForm will cause this issue to come back. I'll create an issue for that since it makes developing anything involving the UI on the MainForm difficult.

:white_check_mark: Build ServiceBusExplorer 4.1.0-PullRequest0225.226.build.409 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/dc7a0782e8 by @ErikMogensen)

I honestly don't know how to review it.
When  Size(495, 701) changes to Size(372, 570) it has no meaning to me 😃
Will defer to others.

Same here @SeanFeldman. @ErikMogensen did you try this on a few machines?
So the whole issue that caused this was the designer in VS?

@tomkerkhove , I tested this on three machines. One of the machines used a High dpi display and it worked before the change and after the change too :)
Yes, I did a minor thing in the designer on the MainForm and caused lots of changes, which had the effect of most scrollbars going away. I created an issue since for this, #226  since I did not fix the root cause.

:white_check_mark: Build ServiceBusExplorer 4.1.0-PullRequest0225.234.build.410 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/d3a39a74c0 by @ErikMogensen)

:white_check_mark: Build ServiceBusExplorer 4.1.0-PullRequest0225.235.build.411 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/f9a1c7bb9f by @ErikMogensen)

I was unable to work without the scrollbars so the commits I did for the Removing metrics issue ended up in this PR. Could/should I have done it differently?


React JSX global namespace is deprecated

Greetings,
I just tried to setup my first tuono project using
tuono new [NAME]

Everything runs correctly but I want to report that the documentation (e.g.: Components page) and template files (e.g.: src/routes/index.tsx) are using JSX global namespace from @types/react which is now deprecated:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/80e20dcf70052f5bacb051f641ea507e705aba5b/types/react/index.d.ts#L4302-L4306
declare global {
    /**
     * @deprecated Use `React.JSX` instead of the global `JSX` namespace.
     */
    namespace JSX {

If you wish I can setup a PR that import React in all the relevant template and documentation files.

Did you have problem with errors on your code editor for that?

Yes,
curiously on VSCode the text is not strikethrough, but on IntelliJ IDEA it is.

I'm not a huge fan of having a React import on any file.

I personally prefer to have all imports explicated.
But I completely understand that is something that might vary from person to person.

Maybe there is the change of using React.JSX to enable that on all the files WDYT?

The only method I could think of is augmenting the global scope using a .d.ts file.
Something like
declare global {
  // export all React types
}

IMHO this could do the trick, but having it in templates and documentation might be error prone since some user might not have React types available "globally".

Right, How do the other framework solves this issue? I know that Next.js for instance allow to not import React on every file.

Looking at some next.js examples (I haven't used next.js) I see that in some scenario they import React in each file:

https://github.com/vercel/next.js/blob/canary/examples/with-typescript/components/Layout.tsx

From what I see I think that the React import (used as value) is optional. On the other hand react types are always imported explicitly.

How about removing the deprecated declaration as you mentioned, but also update the "jsx": "react-jsx" property to "jsx": "preserve"? As far as I understood, this is a problem just with Typescript. Fixing the way it gets compiled might do the trick.
Personally, I strongly like avoiding the React declaration on top of every file.
Do you mind trying it out? Right now, I'm focusing on updating the server side API so I don't have room in the short term to update it.

How about removing the deprecated declaration as you mentioned

Personally, I strongly like avoiding the React declaration on top of every file.

I think that using typed name imports could be a compromise:
import type { JSX } from 'react';

Explicitly specifying return types of the functions helps typescript helps improve performance
(which can be a real pain in huge projects).
Here there are few references:

https://typescript-eslint.io/rules/explicit-module-boundary-types/
https://typescript-eslint.io/rules/explicit-function-return-type/
https://github.com/microsoft/TypeScript/wiki/Performance#using-type-annotations

Additionally these type annotations are required when using isolatedDeclarations.
Right now it might seem useless but it might speed up build process a lot,
if splitting a library in many packages depending on each other.
import type will not affect runtime values and removed during compilation.
A react import will still be present on the top of each tsx files but IMHO the advantages are worth it.

update the "jsx": "react-jsx" property to "jsx": "preserve"? As far as I understood, this is a problem just with Typescript. Fixing the way it gets compiled might do the trick.

I haven't dived deeply in tuono build process yet, so I can't be sure:
From a quick test it looks like that build output is the same when changing tsconfig jsx values.
Probably the build is executed by vite and tsc is not involved at all.
Anyway I don't see how this should affect react types, I'm sorry 😅.  Could you please elaborate?

Do you mind trying it out? Right now, I'm focusing on updating the server side API so I don't have room in the short term to update it.

Sure, as I stated in the description I'm more than happy to help 😉.
Which solution do you prefer I try?

remove deprecated type declarations
(as I stated in one of the above sections I don't think that changing jsx value affects the final build)
Use named type imports to replace deprecated values JSX values

Agree. Thanks for the dive!
I'd go with solution 2. Let's use named imports!


GetOkExists is deprecated

Although GetOkExists is deprecated, it is needed to fix the problem of zero becomes nil.
If it's replacement is created, it would be better to replace GetOkExists.
related. https://github.com/mackerelio-labs/terraform-provider-mackerel/pull/44

https://github.com/hashicorp/terraform-plugin-sdk/pull/350

this method would still exist since we have not come up with a replacement


Out of date information in the app reg. entitlement to free corona test with increased risk encounter(s)

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug affects both Android and iOS, for specific issues / questions that apply only to one operating system, please raise them in the respective repositories:

Android repository
iOS repository

[X] Bug is not already reported in another issue

Technical details

Device name: Not relevant
iOS/Android version: Not relevant
App version: 2.19.1 / 2.19.2

Describe the bug
The CWA includes this sentence:
"Please get tested, even if you don’t have any symptoms. If you get a warning of increased risk (“red tile”), you are entitled to a test free of charge. It does not necessarily have to be a PCR test."
However, with the new "Erste Verordnung zur Änderung der Coronavirus-Testverordnung Vom 11. Februar 2022" there actually is no special entitlement by law anymore, should the Corona-Warn-App show red.
Steps to reproduce the issue

Get an increased risk encounter
Tap on the increased risk tile
Scroll down
See the outdated text

Expected behaviour
The app should not make outdated statements.
Possible Fix
Change the text.

Internal Tracking ID: EXPOSUREAPP-13209

I provided a PR under iOS which fixes this issue: https://github.com/corona-warn-app/cwa-app-ios/pull/4391

@Ein-Tim
Please check also:
https://www.coronawarn.app/en/faq/results/#vac_cert_red_warning "How to behave if I am recovered, partially or completely vaccinated, but receive a red warning in the Corona-Warn-App?"
"In case of an increased risk warning (red tile), you are entitled to a free test. This does not necessarily have to be a PCR test."

https://www.rki.de/DE/Content/InfAZ/N/Neuartiges_Coronavirus/WarnApp/Warn_App.html also vaguely mentions a free test:
"Bei der kostenlosen Testung ..." in the section about a red warning in the app.

FYI: @marcussc informed me in https://github.com/corona-warn-app/cwa-app-ios/pull/4391#issuecomment-1080834789 that there will be a general overhaul of the "Handlungshinweise" section in the app. Thus my PR was closed.
I'm fine with that, as long as the rework of this section in the app will come somewhat soon.

As Marcus already mentioned, the team is currently working on an overhaul of this topic. Unfortunately, no information can be shared here at the moment.
Everyone has the possibility to get free rapid tests until the end of May. The increased risk encounter screen texts will not be changed until the team is finished with the overhaul.

@svengabr Wouldn't it make more sense to leave this issue open until the text has been corrected?

@svengabr Could you please reopen this issue until the problem is addressed?

@dsarkar Please, can this issue be re-opened until it was actually addressed?

@dsarkar @svengabr
Dear Team, it has been two months since the risk card overhaul has been promised. Since then we did not see any movement on this issue.
Could you please check for which version this overhaul is planned and if there is no fixed version yet cross check if it the PR I provided two months ago would be accepted when provided now.

Thanks for your report @Ein-Tim. We have created an internal ticket for it and will raise this topic internally.
Internal Tracking ID: EXPOSUREAPP-13209

Corona-Warn-App Open Source Team

Hi @Ein-Tim,
as far as I understand it, users with a red card in the CWA should in general get a RAT.
See e.g.: https://www.zusammengegencorona.de/testen/die-nationale-teststrategie/ (May 11, 2022)

@dsarkar
Hey, thanks for the feedback! Yes, they should get a RAT, but they have no legal entitlement to this, or am I mistaken? They just have to use their entitlement of a "Bürgerstest".

I also commented on this same issue in https://github.com/corona-warn-app/cwa-website/issues/2607.
https://www.bundesgesundheitsministerium.de/coronavirus/nationale-teststrategie/faq-covid-19-tests.html#c23926

@Ein-Tim @MikeMcC399 So your suggestion would be to be more specific un the app and to mention the entitlement of a test in the sense of "Bürgertest"?

@Ein-Tim Maybe I don't get it: A Bürgertest is free, if you go to the doctor, my understanding is that the test is free.
The issue here is rather of being more precise. (?)

@dsarkar Yeah, right. Because right now the text "Bei einer Warnung über ein erhöhtes Risiko ("Rote Kachel") haben Sie Anspruch auf auf einen kostenlosen Test." says that you are entitled to a free test because of the CWA, although your entitlement to a free test has nothing to do with the CWA.

The full DE text, also in CWA Android release/2.23.x from risk_details_increased_risk_faq_link_text
https://github.com/corona-warn-app/cwa-app-android/blob/b70569c8e1fe4fa4e26d37e2bbb7e4ff7acead13/Corona-Warn-App/src/main/res/values-de/strings.xml#L275-L276
"Lassen Sie sich testen, auch wenn Sie keine Symptome haben. Bei einer Warnung über ein erhöhtes Risiko („Rote Kachel“) haben Sie Anspruch auf einen kostenlosen Test. Dies muss nicht notwendigerweise ein PCR-Test sein."

This is such a central theme to CWA that it should be better explained. At least as well as on the website of the BMG, although maybe it is not necessary to quote exactly the legal paragraphs.
For instance:
"Lassen Sie sich testen, auch wenn Sie keine Symptome haben. Sie haben Anspruch auf eine kostenfreie Antigen-Schnelltestung (Bürgertestung). Fällt der Antigen-Schnelltest positiv aus, haben Sie Anspruch auf einen kostenlosen PCR-Test zur Bestätigung des Schnelltestergebnisses. Bei Vorliegen von COVID-19-spezifischen Symptomen kann im Rahmen der Krankenbehandlung durch einen Arzt/eine Ärztin auch direkt ein PCR-Test veranlasst werden."

Closing this issue as its related internal ticket was set to obsolete.
Developer comment:

People are still entiteled for a free antigen test. Therefore the sentance is still correct.

Mh, the sentence is incorrect in my opinion, and it has been fixed on the website. But your call here.

@larswmh

Developer comment:

People are still entiteled for a free antigen test. Therefore the sentance is still >>correct.

The fact that people are still entitled to a free test does not make the sentence "Bei einer Warnung über ein erhöhtes Risiko („Rote Kachel“) haben Sie Anspruch auf einen kostenlosen Test." correct.
The sentence implies that a red warning of its own right gives entitlement to a free test and it is therefore misleading. If the sentence were changed to "Sie haben Anspruch auf einen kostenlosen Test." i.e. remove the text "Bei einer Warnung über ein erhöhtes Risiko („Rote Kachel“)" it would be correct and not misleading.

See also discussion in PR https://github.com/corona-warn-app/cwa-website/pull/2921

§6 (3) Leistungserbringung of TestV was changed on Feb 12, 2022, see https://www.buzer.de/gesetz/14991/al164025-0.htm

@Ein-Tim @MikeMcC399 thanks for your feedback. Forwarding this to the internal ticket and will let you know once there's an update.

@larswmh
Please reopen this issue.

@Ein-Tim @MikeMcC399
Developer comment:

Issue was discussed in today's RKI call. Feedback: While the finding is in general correct, RKI's interpretation is still that people with a red risk card should get a free antigen test. As there is anyhow some changes in regards to free of charge antigen tests expected in the next months, we dont't do any changes now.

Closing this issue again accordingly, but thank you for your insistence. This is a more informative conclusion.

@larswmh
§19 TestV says:
"(1) Diese Verordnung tritt am 11. Oktober 2021 in Kraft; sie tritt am 30. Juni 2022 außer Kraft."
Is it clear what the status will be on July 1, 2022? Will it be extended, changed or allowed to expire?

@svengabr & @dsarkar & @larswmh
Please reopen this issue and bring to the attention of PO & stakeholders ASAP. Tests won't be free of charge anymore beginning next month! App needs to be changed!

This issue is continued in #903.