add key exists check to prevent exception

It can occure that the ArgumentTypes dictionary does not have all keys. In order to prevent an exception, key check was added.

I stumble upon a weird issue with the fusion gateway. I got the following response when I query for fields on an items which are resolved in parallel and by batch.
{
  "errors": [
    {
      "message": "Unexpected Execution Error",
      "extensions": {
        "message": "The given key '__fusion_exports__1' was not present in the dictionary.",
        "stackTrace": "   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)\n   at HotChocolate.Fusion.Planning.ResolveByKeyBatch.BuildVariables(BatchWorkItem[] workItems) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/ResolveByKeyBatch.cs:line 124\n   at HotChocolate.Fusion.Planning.ResolveByKeyBatch.OnExecuteAsync(FusionExecutionContext context, ExecutionState state, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/ResolveByKeyBatch.cs:line 54\n   at HotChocolate.Fusion.Planning.QueryPlanNode.ExecuteAsync(FusionExecutionContext context, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/QueryPlanNode.cs:line 30\n   at HotChocolate.Fusion.Planning.Parallel.OnExecuteNodesAsync(FusionExecutionContext context, ExecutionState state, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/Parallel.cs:line 23\n   at HotChocolate.Fusion.Planning.QueryPlanNode.ExecuteAsync(FusionExecutionContext context, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/QueryPlanNode.cs:line 34\n   at HotChocolate.Fusion.Planning.QueryPlanNode.OnExecuteNodesAsync(FusionExecutionContext context, ExecutionState state, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/QueryPlanNode.cs:line 51\n   at HotChocolate.Fusion.Planning.QueryPlanNode.ExecuteAsync(FusionExecutionContext context, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/QueryPlanNode.cs:line 34\n   at HotChocolate.Fusion.Planning.QueryPlan.ExecuteAsync(FusionExecutionContext context, CancellationToken cancellationToken) in /...Repos/Github/graphql-platform/src/HotChocolate/Fusion/src/Core/Planning/Nodes/QueryPlan.cs:line 106"
      }
    }
  ],
  "data": {
    "parentType": {
      "components": [
        {},
        {},
        {}
      ]
    }
  },
  "extensions": {
    "queryPlan": {
      "document": "query GetChildrenData { parentType { components { ... on ChildTypeA { configuration { someData { createdAt } } position { somePositionField } } } } }",
      "operation": "GetChildrenData",
      "rootNode": {
        "type": "Sequence",
        "nodes": [
          {
            "type": "Resolve",
            "subgraph": "a",
            "document": "query GetChildrenData_1 { parentType { components { __typename ... on LasertecSecondGen {  } ... on ChildTypeA { __fusion_exports__1: index __fusion_exports__2: id } } } }",
            "selectionSetId": 0
          },
          {
            "type": "Compose",
            "selectionSetIds": [
              0
            ]
          },
          {
            "type": "Parallel",
            "nodes": [
              {
                "type": "ResolveByKeyBatch",
                "subgraph": "b",
                "document": "query GetChildrenData_2($__fusion_exports__2: [ID!]!) { nodes(ids: $__fusion_exports__2) { ... on ChildTypeA { configuration { someData { createdAt } } __fusion_exports__2: id } } }",
                "selectionSetId": 3,
                "argumentTypes": [
                  {
                    "argument": "__fusion_exports__2",
                    "type": "[ID!]!"
                  }
                ],
                "path": [
                  "nodes"
                ],
                "requires": [
                  {
                    "variable": "__fusion_exports__2"
                  }
                ]
              },
              {
                "type": "Resolve",
                "subgraph": "c",
                "document": "query GetChildrenData_3($__fusion_exports__1: Int!) { position(index: $__fusion_exports__1) { isBeamActive } }",
                "selectionSetId": 3,
                "requires": [
                  {
                    "variable": "__fusion_exports__1"
                  }
                ]
              }
            ]
          },
          {
            "type": "Compose",
            "selectionSetIds": [
              3
            ]
          }
        ]
      }
    }
  }
}

When I debugged the issue found the line which causes the issue in my case. I tried to setup a unittest which should result in the same issue. But actually it got weirder. The unittest i also committed does not return all fields and it does not execute multiple requests to the subgraphs.
query TopProducts {
  topProducts(first: 5) {
    weight
    deliveryEstimate(zip: "12345") {
      min
      max
    }
    reviews {
      body
    }
  }
}

I expected 3 execution steps here.

Fetch ids of products subgraph
Fetch deliveryEstimates
Fetch reviews

But I get this query plan
QueryPlan
---------------
{
  "document": "query TopProducts { topProducts(first: 5) { weight deliveryEstimate(zip: \u002212345\u0022) { min max } reviews { body } } }",
  "operation": "TopProducts",
  "rootNode": {
    "type": "Sequence",
    "nodes": [
      {
        "type": "Resolve",
        "subgraph": "Products",
        "document": "query TopProducts_1 { topProducts(first: 5) { weight __fusion_exports__1: dimension { size } __fusion_exports__2: dimension { weight } } }",
        "selectionSetId": 0
      },
      {
        "type": "Compose",
        "selectionSetIds": [
          0
        ]
      }
    ]
  }
}

I am still looking deeper into these two issues. But I am feeling a little bit stuck.

There seems to be an issue in the query plan builder ... looking into it.

The test has helper a lot ... I fixed it in a separate PR ... it was a bit more to do on this one.


Oops! Something went wrong and we couldn't connect to the conference: connection.otherError

help!pls!

same problem for me!! I dont know what im doing wrong, with 4.0.1 all ok i upgrade and work all but webrct breaks with the same problem!!!!!

Its some kind of problem with the plugin openfire websocket if you quit that plugin all will become to work, the ofmeet have less functions, but dele, guus and company are working for add again in the version 4.2.0 of openfire and 1.x of the plugin
I hope works for you!!!!!

There's to little information in this issue to go on. From the top of my head, I can think of issues related to older versions of Openfire and the websockets plugin, as well as issues with ofmeet and offocus that might be causing problems. I advise you to update to the latest version of Openfire (which no longer requires a separate websockets plugin, and ofmeet/offocus.


handle optional values properly in model classes

The optional values are not handled properly in the original python-flask template and this PR fixes the issue. More information can be found in #379.
Fixing this revealed a problematic usage of System model in our code. I added a FIX tag in the code and provided a workaround for now because it needs some big code changes. I put another FIX tag in utils.py. I will create an issue for each of them when we merge this PR.
I reordered the attributes for several models because the required attributes need to come before the optional ones now.
I moved the swagger_types and attribute_map definitions outside of __init__() because they are class variables and they are the same for all instances of the same Model type. This also makes it possible to get the attribute_map of the models without instantiating them.
I think it might be a good idea to go through the python-flask codegen templates and fix any issues we find so we don't run into problems like this again in the future.

Here's an example of the change:
Before
class BenchmarkMetric(Model):
    def __init__(self, name: str=None, weight: float=None, default: float=None):  # noqa: E501
         self._name = name
         self.swagger_types = {...}
         self.attribute_map = {...}
          ...

After
class BenchmarkMetric(Model):
    swagger_types = {...}
    attribute_map = {...}
    def __init__(self, name: str, weight: float | None = None, default: float | None = None):  # noqa: E501
        self._name = name
        ...

In this example, name is a required attribute of BenchmarkMetric. I removed the default value for required attributes.

It seems this fixes the issue discussed in #379. I'm okay with the approach for now.


[Add] New Click Me Animated Button

Details
The feature involves adding a "Click Me" button with interactive elements. When a user hovers over the button, a processing animation will start, featuring three dots that move sequentially. After approximately one second, a success message will appear, accompanied by a tick sign (✓), indicating a successful action.
Screenshots
https://github.com/Spyware007/Animating-Buttons/assets/101655716/89388860-5ddf-4fb8-98ec-c0524649444c
Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[X] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

I would like to work on this project . please assign it to me


write error, no space left on device.

Hi, When i am trying to create clone of npm by using below command on GIT on WindowXp
vrathod@ET3EBS6125 ~
$ git clone --recursive git://github.com/isaacs/npm.git
I am getting below error.
Cloning into npm...
remote: Counting objects: 16367, done.
remote: Compressing objects: 100% (4394/4394), done.
remote: Total 16367 (delta 12216), reused 15975 (delta 11871)
Receiving objects: 100% (16367/16367), 4.90 MiB | 227 KiB/s, done.
Resolving deltas: 100% (12216/12216), done.
fatal: sha1 file 'H:/npm/.git/objects/pack/tmp_idx_QmamNb' write error: No space
left on device
fatal: index-pack failed

Hello,
On My PC there is not drive like "H".

Then what's this about?
fatal: sha1 file 'H:/npm/.git/objects/pack/tmp_idx_QmamNb' write error: No space left on device
```

isaacs, That's i don't know.
On My PC there are only two drives "C" and "D".

Are you perhaps on some mounted drive, or somewhere odd in the git bash shell?  I don't really know what to tell you.
Figure out how to use git clone, and you'll be a step closer to npm working on your system.  Maybe try it in the normal cmd rather than in the msys bash shell.


node-cuda not found

hayashis@aprun2:~> npm install node-cuda
npm ERR! 404 404 Not Found: node-cuda
npm ERR! 404
npm ERR! 404 'node-cuda' is not in the npm registry.
Is this module removed from npm?

@soichih Try running npm install on the package "cuda". I checked it, it's just node-cuda.


Automatic deployment with TinyBlazorAdmin

[ ] Create the resources
[ ] Deploy the code
[ ]  Configure AAD

The original plan to use the New Azure Static Web App won't work for now.
We will use the Static  Website from the Azure Storage with the Function.
I will close this ticket to clean things.
I'm still planning to do automatic deployment we just need to refact a little.


add cassette labware type as an option in block registration

Tests are failing but that seems to be unrelated to the pull request.


Background color for operators is slightly off

Steps to Reproduce
See https://flutter.io/platform-channels/

Thought this was an issue in prism, but they consider it working-as-intended: https://github.com/PrismJS/prism/issues/1167


feature: add 'disable' functionality

Changes

<MultiSelect /> component can have disabled item(s)

Disabled item has different UI than normal item. (I just used the 'secondary' style variant! If you have better option, please let me know)
Disabled and default item's badge takes precedence in sort order.
User cannot click disabled option. there is also no 'x' button on the disabled option badge.

Add new component(<CardStyled />) for reuse in root page UI.
I just added another example card UI on root page for newly added usecase.

Working video
https://github.com/user-attachments/assets/593eafa7-8ea5-4d8e-8751-7c419f1da464

Thank you for your PR. Could you please provide examples of how disabled options would be used in different projects? I would like to understand the potential benefits of this approach.

Yes, sure!
In my project, I have a multi-select UI which a user can select assignee(s) of a task(like GitHub's PR).
In that UI, I want to show the default selected assignee(s) but not want to allow any interaction with it like below screenshot.

I think it will be quite useful especially when I need to explicitly show some options selected by default but not want to allow a user to change checked state of these options.

+1. I also need this feature where I wanted to show some features list where few features are premium i.e disabled for free users


Error 13 after upgrading to CWA 1.9.1 and opening the app

Error 13 after upgrading to CWA 1.9.1 and opening the app
See this FAQ entry:

English https://www.coronawarn.app/en/faq/#ENError13
German https://www.coronawarn.app/de/faq/#ENError13

If you updated to Corona-Warn-App version 1.9.1., some users may receive the following error message:

German error message: "Fehler 13: Ihre Risiko-Ermittlung für den heutigen Tag wurde bereits durchgeführt. Bitte versuchen Sie es in 24 Stunden erneut."

English error message: "Error 13: Your exposure logging for today has already been carried out. Please try again in 24 hours."

The Corona-Warn-App is functioning correctly despite this message. If you have any other problems in this context, you can describe your issue in detail in this thread.
Corona-Warn-App Open Source Team

ORIGINAL POST BY THE AUTHOR
Hi
I upgraded yesterday. Today, in the morning I opened the app, and an error message up, that made little sense,
the check was done correctly, though.
The screenshot is attached
regards
Uwe Brauer

Internal Tracking ID: EXPOSUREAPP-4066

@ouboub
Did you use 1.7.1 before the update?

Hi @ouboub,
Thanks for reporting. According to the developers, this can happen after the
If you open the app for the first time after the update, a risk check is initiated immediately, regardless of whether or not a check has already been carried out. This means that in some cases users may receive this error message.
Reference: EXPOSUREAPP-4066

Hi @ouboub,
Thanks for reporting. However, you can ignore this message.
If you open the app for the first time after the update, a risk check is initiated immediately, regardless of whether or not a check has already been carried out. This means that in some cases users may receive this error message.
Reference: EXPOSUREAPP-4066
Best wishes, DS
Corona-Warn-App Open Source Team

Yes I thought, I could ignore it, but I also thought it is worth letting you know, because it might confuse other users

@ouboub
Did you use 1.7.1 before the update?

I am pretty sure the answer is yes, but how I can I check it to be completely sure?

Thanks, we will update the FAQ now.

@ouboub

I am pretty sure the answer is yes, but how I can I check it to be completely sure?

You can't... But since @dsarkar stated that this does not mean anything, it's not relevant anymore

Thanks, we will update the FAQ https://www.coronawarn.app/de/faq/#ENError13 now.
And yes, we are very happy about any feedback. It tells us also, that we need to communicate more clearly and in a more timely manner.
Corona-Warn-App Open Source Team

thanks, but it also clearly shows, that it would be better to have more beta testers. Im telling you this also because I am beta tester in various Apple Apps.

I have a somewhat different behavior than the initial reporter. I get the same error, but the check doesn’t happen. So my risk status is „unknown“. I have not opened the app in a few days prior to upgrading.

@ellenkoenig
Wait, you can't manually start the risk check? What happens when you click the button? Does the error show up again?

@Ein-Tim yes, exactly

Okay...
@ellenkoenig
Did a restart from the App/your phone change something?
Could you maybe provide your EN-Log here, so that I can see what happens there?

How to export Exposure Notificaiton Logs under iOS 13.7 or newer
This log does not conatin any private information, but the number of encounters.
German:
Einstellungen ➡ Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡ Überprüfungen exportieren
English:
Settings ➡ Exposure Notifications ➡ Exosure Logging Status ➡ Exposure Checks ➡ Export Exposure Checks
To upload the file here, rename it form .json to .txt

@Ein-Tim Restarting the app didn’t help. I don’t want to restart my phone right now.
Here is the log:
ExposureChecks-2020-12-20.zip

Okay, thanks for sharing your log.
This is very weird because a check happend today at 19:09 and also one at 15:08.
But I see the "MatchCount" in your log and this is not normal under 1.9.1. So, could you please make sure that you are really using 1.9.1?

@Ein-Tim I updated a few hours ago to whatever was the most recent version offered. What else could I do?

@Ein-Tim Here is the Update confirmation.

@ellenkoenig ENF error 13 means: the API was called too often - see here.
I suggest that you wait until tomorrow, and try then again.
Please report if this helped.

@ndegend

@ellenkoenig ENF error 13 means: the API was called too often - see here.
I suggest that you wait until tomorrow, and try then again.
Please report if this helped.

Sure, that might or might not help. The inconsistent thing about this error is that I didn’t open the app in the 24 hrs before updating. So how could the API be called too often?

@ndegendogo
Yes she can wait but AFAIK this Error will prevent further calls to the ENF but they are happening here...

how could the API be called too often?

@ellenkoenig you are absolutely right
I just checked your uploaded file and it shows 5 checks today - which is definitely not above any limit.
Do you remember at which time you upgraded to 1.9.1? Before or after the check at 19:09?

@ndegendogo I would say after the check at 19:09. Probably around 19:30-19:45ish.

After updating to v2 an exposure check will be enforced. The v1 checks will count into v2 this means in rare case it can happens the limit is already reached. Please follow the information and wait 24h.

Thanks @thomasaugsten
so maybe Apple does not count max 14 checks per day, but calculates the limit with finer granularity ... and throws this error if the last check is less than 2 hours ago ... (just speculating ...)

Hello, everybody,
I’m using iOS 14.3 and CWA 1.10.1 on a iPhone SE 2016. Since yesterday I got always the notification mentioned above. Restarting my iPhone and waiting for 24 hours, as mentioned in the app’s FAQs didn’t help. This is the actual screenshot:

Hello, everybody,
I’m using iOS 14.3 and CWA 1.10.1 on a iPhone SE 2016. Since yesterday I got always the notification mentioned above. Restarting my iPhone and waiting for 24 hours, as mentioned in the app’s FAQs didn’t help. This is the actual screenshot:

Oh, apologies, I forgot to report back. Waiting 24h did fix the issue for me back then. Now the app is working again as it should.

Oh, apologies, I forgot to report back. Waiting 24h did fix the issue for me back then. Now the app is working again as it should.

@FallobstAmateur
Could you please provide a screenshot from the main screen of Corona-Warn-App without the error message?
Additionally you could provide your EN-Log here, so we can see if the Exposure Checks are working.

How to export Exposure Notificaiton Logs under iOS 13.7 or newer
This log does not conatin any private information, but the number of encounters.
German:
Einstellungen ➡ Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡ Überprüfungen exportieren
English:
Settings ➡ Exposure Notifications ➡ Exosure Logging Status ➡ Exposure Checks ➡ Export Exposure Checks
To upload the file here, rename it form .json to .txt

@FallobstAmateur
Could you please provide a screenshot from the main screen of Corona-Warn-App without the error message?
Additionally you could provide your EN-Log here, so we can see if the Exposure Checks are working.

How to export Exposure Notificaiton Logs under iOS 13.7 or newer
This log does not conatin any private information, but the number of encounters.
German:
Einstellungen ➡ Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡ Überprüfungen exportieren
English:
Settings ➡ Exposure Notifications ➡ Exosure Logging Status ➡ Exposure Checks ➡ Export Exposure Checks
To upload the file here, rename it form .json to .txt

Hello,
I added the EN-Log as a Word-Document; hopefully it will work for you. It’s
been quite difficult to get this log into this specific mail...
The next screenshot will be sent via GitHub.
Many thanks
Torsten Muth-Huber
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 18:58:

@FallobstAmateur https://github.com/FallobstAmateur
Could you please provide a screenshot from the main screen of
Corona-Warn-App without the error message?
Additionally you could provide your EN-Log here, so we can see if the
Exposure Checks are working.
How to export Exposure Notificaiton Logs under iOS 13.7 or newer
This log does not conatin any private information, but the number of
encounters.
German:
Einstellungen ➡ Begegnungsmitteilungen ➡ Status von
Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡ Überprüfungen
exportieren
English:
Settings ➡ Exposure Notifications ➡ Exosure Logging Status ➡ Exposure
Checks ➡ Export Exposure Checks
To upload the file here, rename it form .json to .txt
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753508809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJGTUAU35HKQACPIYHDSX5NFTANCNFSM4VA2WDEA
.

Hello,
I added the EN-Log as a Word-Document; hopefully it will work for you. It’s
been quite difficult to get this log into this specific mail...
The next screenshot will be sent via GitHub.
Many thanks
Torsten Muth-Huber
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 18:58:

@FallobstAmateur https://github.com/FallobstAmateur
Could you please provide a screenshot from the main screen of
Corona-Warn-App without the error message?
Additionally you could provide your EN-Log here, so we can see if the
Exposure Checks are working.
How to export Exposure Notificaiton Logs under iOS 13.7 or newer
This log does not conatin any private information, but the number of
encounters.
German:
Einstellungen ➡ Begegnungsmitteilungen ➡ Status von
Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡ Überprüfungen
exportieren
English:
Settings ➡ Exposure Notifications ➡ Exosure Logging Status ➡ Exposure
Checks ➡ Export Exposure Checks
To upload the file here, rename it form .json to .txt
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753508809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJGTUAU35HKQACPIYHDSX5NFTANCNFSM4VA2WDEA
.

@Ein-Tim
Good Evening,
as promised, here are two new screenshots:
 and after deleting this notification:

@Ein-Tim
Good Evening,
as promised, here are two new screenshots:
 and after deleting this notification:

Okay interesting, thank you for sharing @FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your log file did not work, could you maybe simply open up your phones settings and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here, then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.

Okay interesting, thank you for sharing @FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your log file did not work, could you maybe simply open up your phones settings and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡ Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here, then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.

Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡
Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡
Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

Most of my apps are programmed for automatic upgrades.. so this version
should have been installed quite early and is supposed to be based on
version 1.9.1. I’ll try to get more information from my iPhone...
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡
Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

Most of my apps are programmed for automatic upgrades.. so this version
should have been installed quite early and is supposed to be based on
version 1.9.1. I’ll try to get more information from my iPhone...
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.
The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:
Begegnungsmitteilungen ➡ Status von Begegnungsaufzeichnungen ➡
Begegnungsüberprüfungen ➡
From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...
When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

Thank you @FallobstAmateur.

Thank you @FallobstAmateur.

Okay, the Update was done on New Year’s Eve, but I can’t guarantee that the
predecessant version was really 1.9.1.  Sorry @Ein-Tim
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 20:04:

Thank you @FallobstAmateur https://github.com/FallobstAmateur.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753516427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6QB5RL7PFCQQMWIDSX5U4RANCNFSM4VA2WDEA
.

Okay, the Update was done on New Year’s Eve, but I can’t guarantee that the
predecessant version was really 1.9.1.  Sorry @Ein-Tim
Ein_Tim<EMAIL_ADDRESS>schrieb am Sa. 2. Jan. 2021 um 20:04:

Thank you @FallobstAmateur https://github.com/FallobstAmateur.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753516427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6QB5RL7PFCQQMWIDSX5U4RANCNFSM4VA2WDEA
.

Okay no problem @FallobstAmateur.
Sadly, I can't help you any further here. You could wait another 24h and then report back here.
@thomasaugsten maybe you could quickly jump in here?

Okay no problem @FallobstAmateur.
Sadly, I can't help you any further here. You could wait another 24h and then report back here.
@thomasaugsten maybe you could quickly jump in here?

Hey @FallobstAmateur
Did anything change, or are you still getting this Pop-Up?

Hey @FallobstAmateur
Did anything change, or are you still getting this Pop-Up?

Hallo @Ein-Tim
I've restarted the iPhone and wanted to wait until tonight to check once again how the app will react. I'll keep you informed..

Hallo @Ein-Tim
I've restarted the iPhone and wanted to wait until tonight to check once again how the app will react. I'll keep you informed..

Good Evening to everyone and @Ein-Tim,
tonight's trial has been successful. The EN-Log shows three Updates today, but the app hasn't shown the error code anymore.
Thanks for your assistance.

Good Evening to everyone and @Ein-Tim,
tonight's trial has been successful. The EN-Log shows three Updates today, but the app hasn't shown the error code anymore.
Thanks for your assistance.

@FallobstAmateur, Happy to hear, and many thanks for the feedback!
@Ein-Tim, Thanks !

@FallobstAmateur, Happy to hear, and many thanks for the feedback!
@Ein-Tim, Thanks !

Just started to have the same issue with the app version 1.10.1 under iOS 14.3

Just started to have the same issue with the app version 1.10.1 under iOS 14.3

@yannikbloscheck Thanks for reporting. Please, wait for at least 24 h. Feedback will be very much appreciated. See https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issue-770687899. Best wishes. DS

Corona-Warn-App Open Source Team

@yannikbloscheck Thanks for reporting. Please, wait for at least 24 h. Feedback will be very much appreciated. See https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issue-770687899. Best wishes. DS

Corona-Warn-App Open Source Team

I don't really understand where this message is coming from, looking at the log from @yannikbloscheck there were only 3 checks in the last 24h, this should only be shown if there were more than 6 checks in the last 24h.
Are you trying to fix this or is somebody investigating why this is happening?
cc @thomasaugsten

I don't really understand where this message is coming from, looking at the log from @yannikbloscheck there were only 3 checks in the last 24h, this should only be shown if there were more than 6 checks in the last 24h.
Are you trying to fix this or is somebody investigating why this is happening?
cc @thomasaugsten

It is hard to investigate its is very likely that the exposure checks fails but Apple still counting it in the rate limit. I assume their are only a few cases and it is gone after 24hr

It is hard to investigate its is very likely that the exposure checks fails but Apple still counting it in the rate limit. I assume their are only a few cases and it is gone after 24hr

It's now working again. Here is the current log now after.
From the error code it has to be the rate limit, but like with other errors before (#1000) a big question is why it isn't it just handled better by the app.
Instead this error message pop ups again and again, because the apps tries automatically again. The coloured background for the risk is gone and instead there is a dangerous sounding message "Risiko-Überprüfung fehlgeschlagen". Annoying the user gives him the impression that the app doesn't work while it actually does. In my case the last successful exposure comparison was just four hours ago. So no need for all the communicated drama.
It would be better to stop these error alerts and instead show a message next to the last updated date while keeping the coloured background for the risk and the big risk classification text. I would keep showing the button to manually trigger the exposure comparison in that case and provide an error alert dialog just when the button was used unsuccessfully.

It's now working again. Here is the current log now after.
From the error code it has to be the rate limit, but like with other errors before (#1000) a big question is why it isn't it just handled better by the app.
Instead this error message pop ups again and again, because the apps tries automatically again. The coloured background for the risk is gone and instead there is a dangerous sounding message "Risiko-Überprüfung fehlgeschlagen". Annoying the user gives him the impression that the app doesn't work while it actually does. In my case the last successful exposure comparison was just four hours ago. So no need for all the communicated drama.
It would be better to stop these error alerts and instead show a message next to the last updated date while keeping the coloured background for the risk and the big risk classification text. I would keep showing the button to manually trigger the exposure comparison in that case and provide an error alert dialog just when the button was used unsuccessfully.

@thomasaugsten what exactly is the implemented behaviour in cwa 1.10 when I open the app? In previous versions it triggered a risk check - is this still the same in 1.10?
Before 1.10 most users did not open the app frequently; but this has (hopefully) changed with the contact diary feature.

@thomasaugsten what exactly is the implemented behaviour in cwa 1.10 when I open the app? In previous versions it triggered a risk check - is this still the same in 1.10?
Before 1.10 most users did not open the app frequently; but this has (hopefully) changed with the contact diary feature.

It will trigger not at every start. Every 6h if there a new key files downloaded.

It will trigger not at every start. Every 6h if there a new key files downloaded.

Hi,
Version 1.10.1 (0)
IOS 14.3
same behaviour as Fallobst described 4 days ago.
I did a lot of refresh in the last 4 hours.
Any clues?
thanks!

Hi,
Version 1.10.1 (0)
IOS 14.3
same behaviour as Fallobst described 4 days ago.
I did a lot of refresh in the last 4 hours.
Any clues?
thanks!

Hey @ThisIsNotALoveSong
Please wait 24h and report back, thanks.

Hey @ThisIsNotALoveSong
Please wait 24h and report back, thanks.

Hi @ThisIsNotALoveSong. Thanks for reporting. All should be back to normal after 24 h as @Ein-Tim said. In any case we will appreciate your feedback then. Thanks.

Hi @ThisIsNotALoveSong. Thanks for reporting. All should be back to normal after 24 h as @Ein-Tim said. In any case we will appreciate your feedback then. Thanks.

@dsarkar
worked early this morning again. Thanks!
not funny: using the app since day 1.
Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.
Obviously refreshing stresses the app and throws
an userunfriendly error sending me to github.
I told my story and you guys told me to wait for the next refresh 24h
( what i didnt do waiting for the test)
( dont get me wrong, you were very fast and helpful,
I appreciate that)
To emphasise it: you use the refresh a lot of times
When you wait for a test result and then the app goes down?
Giving this error message and error dealing via github?
Cmon - you must be kidding, i am sure 95% of the app users are
not able to get in contact with you via github.
Rest of story:
first my doc, called me to tell me i am positive,
then my healthdepartment called and finally after
4 hours the app went positive.
On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

@dsarkar
worked early this morning again. Thanks!
not funny: using the app since day 1.
Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.
Obviously refreshing stresses the app and throws
an userunfriendly error sending me to github.
I told my story and you guys told me to wait for the next refresh 24h
( what i didnt do waiting for the test)
( dont get me wrong, you were very fast and helpful,
I appreciate that)
To emphasise it: you use the refresh a lot of times
When you wait for a test result and then the app goes down?
Giving this error message and error dealing via github?
Cmon - you must be kidding, i am sure 95% of the app users are
not able to get in contact with you via github.
Rest of story:
first my doc, called me to tell me i am positive,
then my healthdepartment called and finally after
4 hours the app went positive.
On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

Oder bin ich hiereinfach falsch?

Oder bin ich hiereinfach falsch?

Hey @ThisIsNotALoveSong
Just before I answer to your questions, the answer why we are speaking English can you find here.

Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.

The ENError 13 alert has absolutely nothing to do with the test result process so even if you clicked "Aktualisieren" inside of the box which showed „Ergebnis liegt noch nicht vor“, this has no impact on Issues like ENError13.

I told my story and you guys told me to wait for the next refresh 24h

The In-App pop-up also includes this information.

When you wait for a test result and then the app goes down?

As said before, no. The ENError 13 comes from the underlying API, the Exposure Notification Framework, from Apple & Google. It shows up when your risk detection has been checked more than 6 times in 24h.
Since CWA 1.9.1 there are some rare cases in which this error pops up although there were less than 6 checks in the last 24h.

On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

You said you are using the App since one day. If you had „Risiko-Ermittlung“ active the whole time AND there were other phones near your phone, these will be warned (either „Low-Risk encounter“ or „High-Risk encounter“. More detailed information how the warning process works can be found here

Hey @ThisIsNotALoveSong
Just before I answer to your questions, the answer why we are speaking English can you find here.

Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.

The ENError 13 alert has absolutely nothing to do with the test result process so even if you clicked "Aktualisieren" inside of the box which showed „Ergebnis liegt noch nicht vor“, this has no impact on Issues like ENError13.

I told my story and you guys told me to wait for the next refresh 24h

The In-App pop-up also includes this information.

When you wait for a test result and then the app goes down?

As said before, no. The ENError 13 comes from the underlying API, the Exposure Notification Framework, from Apple & Google. It shows up when your risk detection has been checked more than 6 times in 24h.
Since CWA 1.9.1 there are some rare cases in which this error pops up although there were less than 6 checks in the last 24h.

On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

You said you are using the App since one day. If you had „Risiko-Ermittlung“ active the whole time AND there were other phones near your phone, these will be warned (either „Low-Risk encounter“ or „High-Risk encounter“. More detailed information how the warning process works can be found here

Hey @Ein-Tim,
thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.
Concerning my app install date:
that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.
The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

Hey @Ein-Tim,
thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.
Concerning my app install date:
that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.
The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

@ThisIsNotALoveSong

thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.

There are some ENErrors which are not shown to the user, but since the ENError (normally) has a big effect on the risk calculation (next check can be done earliest in 24h) the devs decided to show it.

that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.

Oh okay I see, I understood you wrong 😅

The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

No phones which were close sho encounters? Not even green ones?
This is always hard to investigate because of the high data protection of CWA...

@ThisIsNotALoveSong

thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.

There are some ENErrors which are not shown to the user, but since the ENError (normally) has a big effect on the risk calculation (next check can be done earliest in 24h) the devs decided to show it.

that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.

Oh okay I see, I understood you wrong 😅

The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

No phones which were close sho encounters? Not even green ones?
This is always hard to investigate because of the high data protection of CWA...

I understand that you want to show the error, but please keep in mind, normaly this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.
He wants to know he has to wait for 24h but the rest of functionality i working poperly.
What you get from user perspective:
In my case i waited for the test
and got the error message.
To reflect the problem you have to go to github, read your Development and technical advises.
After some reading i understood the problem-but i am sure that you are loosing 98 percent of the users.
And furthermore, they are left unsure if the other application parts are still working.

I understand that you want to show the error, but please keep in mind, normaly this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.
He wants to know he has to wait for 24h but the rest of functionality i working poperly.
What you get from user perspective:
In my case i waited for the test
and got the error message.
To reflect the problem you have to go to github, read your Development and technical advises.
After some reading i understood the problem-but i am sure that you are loosing 98 percent of the users.
And furthermore, they are left unsure if the other application parts are still working.

@ThisIsNotALoveSong, Thanks for all your detailed input. We will bring forward to the developers your thoughts about showing and interpreting this error message for a "normal" user.
@Ein-Tim Thanks for replying in detail.

@ThisIsNotALoveSong, Thanks for all your detailed input. We will bring forward to the developers your thoughts about showing and interpreting this error message for a "normal" user.
@Ein-Tim Thanks for replying in detail.

@ThisIsNotALoveSong

this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.

I disagree.
Affected users will see this:

A click on "Mehr Erfahren" will bring the user to a FAQ entry which explains everything in detail.
So or so this is o/t here so...

@ThisIsNotALoveSong

this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.

I disagree.
Affected users will see this:

A click on "Mehr Erfahren" will bring the user to a FAQ entry which explains everything in detail.
So or so this is o/t here so...

@Ein-Tim:
yes this ist the message.
But when you wait for response for your corona-test and you are not sure wether this affects you or not.

@Ein-Tim:
yes this ist the message.
But when you wait for response for your corona-test and you are not sure wether this affects you or not.

first my doc, called me to tell me i am positive, then my healthdepartment called and finally after 4 hours the app went positive.

@dsarkar could you please ask the devs what is the current frequency of background task to poll for test results?
I am aware that risk checking procedure is rate-limited to intervals > 4 hours from Apple side, and that a high frequency of BG task always eats a lot of battery.

first my doc, called me to tell me i am positive, then my healthdepartment called and finally after 4 hours the app went positive.

@dsarkar could you please ask the devs what is the current frequency of background task to poll for test results?
I am aware that risk checking procedure is rate-limited to intervals > 4 hours from Apple side, and that a high frequency of BG task always eats a lot of battery.

The background task for test result fetching is scheduled for earliest time. At the moment our background task is executed every 2h. But this is influenced by the situation of the iPhone. With high usage, low battery or no internet the fetch is postponed. Test result fetching, key download and exposure check is executed in the same background task.

The background task for test result fetching is scheduled for earliest time. At the moment our background task is executed every 2h. But this is influenced by the situation of the iPhone. With high usage, low battery or no internet the fetch is postponed. Test result fetching, key download and exposure check is executed in the same background task.

Thanks @thomasaugsten.
As far as I understand, the key fetching is performed only while WLAN is availabe.
Does the same constraint apply also to fetching the test results?

Thanks @thomasaugsten.
As far as I understand, the key fetching is performed only while WLAN is availabe.
Does the same constraint apply also to fetching the test results?

Hourly key Download via wifi
Daily key download and test result fetching via mobile and wifi

Hourly key Download via wifi
Daily key download and test result fetching via mobile and wifi

@thomasaugsten is it possible to "poll" manually more often when I am waiting for a test tesult? Even when I don't have WLAN at that time, only mobile data?
Because a delay of up to one day seems quite much in this situation (so it could be worth an enhancement request)

@thomasaugsten is it possible to "poll" manually more often when I am waiting for a test tesult? Even when I don't have WLAN at that time, only mobile data?
Because a delay of up to one day seems quite much in this situation (so it could be worth an enhancement request)

Open the app will refresh the test result and there is a refresh button in the test result pending screen

Open the app will refresh the test result and there is a refresh button in the test result pending screen

I suggest to close this (like #1703) since I think that with the FAQ articles in place and the today released version 1.12 everything should be clear.
If there are any duplicates we can reopen this for long-term visibility.

@ouboub Do you want to close this issue as suggested by  @Ein-Tim? Thanks.

done
On Thu, Feb 11, 2021 at 8:42 AM dsarkar<EMAIL_ADDRESS>wrote:

@ouboub https://github.com/ouboub Do you want to close this issue as
suggested by @Ein-Tim https://github.com/Ein-Tim? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-777255324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNOMU6WF3J7CB5BOMW2ORLS6OC65ANCNFSM4VA2WDEA
.

@ouboub Thanks!

Related Internal Tracking ID: EXPOSUREAPP-4906


MTL-2272: use default xfs options

Summary and Scope

Fixes: MTL-2272

Issue Type

Bugfix Pull Request

Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[ ] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)
[ ] I tested this on a vshasta system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency

Risks and Mitigations

/backport lts/csm-1.5


Add patch masking functions

Summary:

Test plan:

Fixes #{issue number}

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.22% :tada:

Comparison is base (f708200) 69.53% compared to head (6e8c6a5) 69.76%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #452      +/-   ##
==========================================
+ Coverage   69.53%   69.76%   +0.22%
==========================================
  Files         170      172       +2
  Lines       11709    11797      +88
==========================================
+ Hits         8142     8230      +88
  Misses       3567     3567

Files Changed
Coverage Δ

tests/modules/masking/test_random_masking.py
100.00% <100.00%> (ø)

torchmultimodal/modules/masking/random_masking.py
100.00% <100.00%> (ø)

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


Daemon Crashed

coda_crash_report_2020-11-18_01-49-52.414595.tar.gz
coda.log

yes i deleted .coda-config. And now i just deleted again and found new issue

coda.log
coda_crash_report_2020-11-18_03-47-29.596587.tar.gz


Conform with SI units

Readme states that:
"fieldSize - integer - Max field value size (in bytes) (Default: 1MB)"
Or nowadays most OS filesystems respect the SI standard for files size so 1 MB = 1 * 1000 * 1000
Source example: https://wiki.ubuntu.com/UnitsPolicy
If you keep 1 * 1024 * 1024 you should modify the readme MB to MiB to avoid confusion

If anything, I'd rather prefer just changing the documentation to just say Default: 1024 * 1024. However I'm not particularly bothered by it.


Support multiple Sphinx projects in one VS Code folder / workspace

If I work on a large project with more than one Sphinx project,
e.g. with unrelated sphinx projects in a larger monorepo or because I use a multi-project build, I have several conf.py and thus several needs.json, usually in a directory structure like this:
|- build/
|  |- project_a/
|  |  |- needs
|  |     |- needs.json
|  |- project_b/
|  |  |- needs
|  |     |- needs.json
|     ...
|- src/
|  |- .git/
|  |- project_a/
|  |  |- conf.py
|  |  |- index.rst # reference project B
|  |  `  ...
|  |- project_b/
|  |  |- conf.py
|  |  |- index.rst
|  |  `  ...
|  ` ...

Ideally, Open-Needs IDE drops the limiting UI config and uses the folder/workspace-specific settings.json file (.vscode/settings.json), to configure an arbitrary number of sphinx-needs projects, just as I can configure an arbitrary number of debug or run configurations, e.g.:
{
  "needls.projects": [
      {
           "buildPath": "build/project_a",
           "docsRoot": "src/project_b"
      },
      {
           "buildPath": "build/project_a",
           "docsRoot": "src/project_b"
      }
   ]
...

Open-Needs IDE could then use the matching needs.json for every file based on a pattern matching of the relative path of the file w.r.t. the docsRoot.

It does already support the .vscode/settings.json file:
  {
      "needls.buildPath": "/home/daniel/workspace/open-needs/open-needs-ide/docs/_build/need",
      "needls.docsRoot": "/home/daniel/workspace/open-needs/open-needs-ide/docs"
  }

But this does not support any multi-project setups.
However, are you using the Multi-root Workspace concept from VS Code?
There you have one .vscode file per root project and then you can configure multiple docs-folders (but still one per settings.json only).
https://code.visualstudio.com/docs/editor/multi-root-workspaces#_settings
But for sure, you can still have multiple doc-projects in one vs-code root project. So this use case is still not covered and needs to be implemented.

Hi,
This project is not maintained anymore and is archived.
All the current features have been moved to project Sphinx-Needs: https://github.com/useblocks/sphinxcontrib-needs/tree/master/sphinx_needs/lsp. The features will be automatically detected by VsCode extension reStructuredText: https://github.com/vscode-restructuredtext/vscode-restructuredtext in your Sphinx-Needs project.
Further features development will be done inside the Sphinx-Needs project.
Thanks.


Web - Inconsistency in Pinning IOU: Possible in LHN but Not Inside IOU

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click on the plus sign and select "Request Money."
Enter the desired amount and add an email address. Submit the request.
Go to the IOU section by double-clicking on the requested money.
In the Left Hand Navigation (LHN), right-click and observe that you can pin the IOU from LHN.
However, inside the IOU, there is no option to pin it until you delete the requested money.

Expected Result:
Pinning the IOU should be possible consistently both inside the IOU and in the LHN before deleting the requested money. Alternatively, the pinned IOU should appear in the LHN only after deleting the requested money to ensure consistency.
Actual Result:
Pinning the IOU is possible in the LHN before deleting the requested money.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/bdbe1630-3c74-4fc2-abe1-249ef838dcf7
https://github.com/Expensify/App/assets/93399543/0bfbbca2-247e-4755-9941-5865e06450ab
Expensify/Expensify Issue URL:
Issue reported by: @tewodrosGirmaA
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692865226061699
View all open jobs on GitHub

Proposal
Please re-state the problem we are trying to solve
Able to pin a money request from LHN while there is no option to do so in the header
What is the root cause of this problem?
There is no condition to block the pin icon for a MoneyRequest in ContextMenuActions.
It seems to be intentional to hide the pin option from this deliberate commit: https://github.com/Expensify/App/pull/22562/commits/f79fc237fa00454daaeb7cf94f08ff34373819d6
However, I don't have a strong opinion about this, so, I'll include both solutions
What changes do you think should be made in order to solve this?
Any of the options can be chosen:

Hide pin option for money request:
To hide the pin option in LHN as well, we can add a condition to ContextMenuActions here:
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/pages/home/report/ContextMenu/ContextMenuActions.js#L334-L340
Add the condition !ReportUtils.isMoneyRequest(reportID)

shouldShow: (type, reportAction, isArchivedRoom, betas, anchor, isChronosReport, reportID, isPinnedChat) =>
  type === CONTEXT_MENU_TYPES.REPORT && !isPinnedChat && !ReportUtils.isMoneyRequestReport(reportID) && !ReportUtils.isMoneyRequest(reportID),

Show pin option for money request:
To show the pin button on the header as well, we can set the following to true:
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/components/MoneyRequestHeader.js#L82

I'm inclined to not accept this bug report, as it's a new feature request and was known at the time we built this feature. Do you agree @trjExpensify?

I think the Pin option should go inside the overflow menu at the top of all pages. I.e no independent buttons for call / pin, and consistently on chat/task/expense/iou/transaction pages that are all possible to
"keep" in your LHN. That's being worked on here I believe: https://github.com/Expensify/App/issues/22635

Ah yes, agreed. This is already being handled. Closing this duplicate report and feature request.


BufferUnderflowException

java.nio.BufferUnderflowException 	at com.strobel.assembler.metadata.Buffer.verifyReadableBytes(Buffer.java:387) 	at com.strobel.assembler.metadata.Buffer.readInt(Buffer.java:231) 	at com.strobel.assembler.metadata.ClassFileReader.readClass(ClassFileReader.java:335) 	at com.strobel.assembler.metadata.MetadataSystem.resolveType(MetadataSystem.java:129) 	at com.strobel.assembler.metadata.MetadataSystem.lookupTypeCore(MetadataSystem.java:86) 	at com.strobel.assembler.metadata.MetadataResolver.lookupType(MetadataResolver.java:46) 	at us.deathmarine.luyten.Model.openEntryByTreePath(Model.java:338) 	at us.deathmarine.luyten.Model$TreeListener$1.run(Model.java:266)
What would this error be and is there a chance that anyone can patch/fix it?

Hello! Please help, the same problem

Hello! Please help, the same problem

To beginwith - a common practice is to attach your .jar/.class file that leads to an issue
2) most probably this is an issue not in Luyten, but in backend engine, but that need to be proven

To beginwith - a common practice is to attach your .jar/.class file that leads to an issue
2) most probably this is an issue not in Luyten, but in backend engine, but that need to be proven

sample.zip

sample.zip


Timeline zoom to feature extent selects wrong range

Selecting a track feature that starts in 2010-05-28T02:02:09Z results in timeline zooming to 1908-03-15 04:42 Z
Selecting again goes further back.
Similar problems selecting other entries (Today, this year, etc).

Cannot duplicate.


Function app  - Encountered an error (InternalServerError) from host runtime.

Description
Recently migrated my functions from .NET 6 in process to .NET isolated workers. Deployed the Functions to Azure and all my functions  are invoked succesfully. But in azure portal am  seeing an error "Encountered an error (InternalServerError) from host runtime" when i click on below pages

In over view page , displaying an error Error while loading functions  "Encountered an error (InternalServerError) from host runtime" even though all functions are listed in that page
In App keys page ,  , displaying an error Error while loading functions  "Encountered an error (InternalServerError) from host runtime" but no keys are displayed

3 In Activity log, its showing SyncWeb apps function trigger and list host keys as failed

with status message as below

My project uses below references

Raised a support ticket with Microsoft on Azure. So far they were not able to identity it
Has anyone encountered a similar issue with isolated worker  function apps? If so, how did you resolved it?
Steps to reproduce
Refer the description

Hi @ganiths, are there any new updates from the support ticket you raised?

@liliankasem
Based on the investigation by Microsoft support team, below change is made in  azure portal recently
a recent experience change to highlight an issue in the portal in synchronizing the list of functions to avoid showing stale data. The logic was updated in a way so that if there are synchronization issues, the latest cached list of functions in your function app will be shown in addition to any error messages which may have come from a synchronization operation.  This is done to allow customers to continue operating on their existing functions while also raising awareness for any potential issues with their Function App.
Due to this change,  host runtime was sending request to function app  endpoint url to find out what functions are available and display the same in the portal
In my case, my function app was not publicly accessible and accessible only over private endpoint. Since i was not allowing the traffic between the  function app outbound integration subnet and inbound private endpoint subnet, i was getting an error "Internal server error"
After updating the NSG rule sto allow the traffic, error goes away in the portal.
Above error was not specific to isolated worker, it even happens for in-process app as well.

I encountered same issue but different root cause. My problem is that the AzureWebJobsStorage environment variable is setting to none accessible storage account. After granted access permission for the Function App to access the storage then the issue was gone.

Thank you for sharing the details, it sounds like this was a configuration issue to do with either network or permissions. Can we consider this issue resolved?

@liliankasem Yes,the issue is resolved and can be closed

I am now experiencing this issue with one of our prod deployments. Nothing changed and then 3 days ago the app stopped working. I've torn down the linux hosted instance, changed it to windows and still the same issue. The last deployment was in April this year.

Hi, if you're experiencing a similar issue, please open an azure support ticket. For anything production related a support ticket is required for the product team to investigate your application. Thanks!


Stm32f401: add TIM[4, 5] + DMAx_STREAMy Interrupts

I have added the missing interrupt handlers in the same manner as already done for USART2/6

This pull request closes #340


create contribution.md

update the contribution.MD file and the contribution guideline for the project .
which consist of git commands for " how to contribute to this project ? "

@rajraman786 I would like to work on this. Please assign it to me.

@rajraman786 Please review and merge it.


Update State Hook

https://reactjs.org/docs/hooks-state.html
following this i hope in the you create new feat to create hook state like
rur -> for create
import React, { useState } from 'react';

function Example() {
   return (
  );
}

Addressed with #72


Relax the restriction in building Column from JSON without index

Column has been deserialized through ColumnJacksonModule since #1290, but I found that ColumnJacksonModule is more strict than @JsonCreator -- index was able to be empty in @JsonCreator.
Although we've observed no problems with it, relaxing it back just in case.

Thanks!


Incorrect (inverse) patches when model action in onAttachedToRootStore

When a model action is performed in onAttachedToRootStore, the order in which onPatches emits patches is unexpected (to me) and the order in which it emits inverse patches is wrong, i.e. it is impossible to revert the changes by applying inverse patches (in reverse order - see #84).
I believe that model actions performed in onAttachedToRootStore should trigger a patch after, e.g., the patch for adding a model instance to a tree (with a root store) is triggered. This issue may be related to #76.
This is a test case that demonstrates the problem:
test("patches with action in onAttachedToRootStore", () => {
  @model("test/patchesWithActionInOnAttachedToRootStore/M")
  class M extends Model({ value: prop<number>(0) }) {
    onAttachedToRootStore() {
      this.setValue(1)
    }

    @modelAction
    setValue(value: number) {
      this.value = value
    }
  }

  @model("test/patchesWithActionInOnAttachedToRootStore/R")
  class R extends Model({ ms: prop<M[]>(() => []) }) {
    @modelAction
    addM(m: M) {
      this.ms.push(m)
    }
  }

  const r = new R({})
  autoDispose(() => unregisterRootStore(r))
  registerRootStore(r)

  const sn = getSnapshot(r)

  const rPatches: Patch[][] = []
  const rInvPatches: Patch[][] = []
  autoDispose(
    onPatches(r, (ptchs, iptchs) => {
      rPatches.push(ptchs)
      rInvPatches.push(iptchs)
    })
  )
  expect(rPatches).toMatchInlineSnapshot(`Array []`)
  expect(rInvPatches).toMatchInlineSnapshot(`Array []`)

  r.addM(new M({}))

  runUnprotected(() => {
    rInvPatches
      .slice()
      .reverse()
      .forEach(invpatches => applyPatches(r, invpatches, true))
  })
  expect(getSnapshot(r)).toStrictEqual(sn)
})

Does the PR you made fix this issue?

Just to clarify, #84 doesn't solve this problem. I was able to create a test case that demonstrates the problem, but I'm not sure what needs to be done to fix it.

As #84 has been merged, I've updated the test case to use the new reverse flag of applyPatches.

should be fixed in 0.33.0, thanks!

Perfect, thanks!


Proposal: smoother design for error squiggles

The error squiggle is very angular in VSCode / monaco. I think a more rounded design would be less anxiety-inducing and would harmonize more with the typography.
Zooming in on what I mean

Here are some explorations I did at full size:

I created a more rounded version of the underline would be a drop-in replacement for the current SVG pattern:
<?xml version="1.0" encoding="UTF-8"?>
<svg width="6px" height="3px" viewBox="0 0 6 3" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<path d="M0,2 C1.5,2 1.5,0.5 3,0.5 C4.5,0.5 4.5,2 6,2" stroke="#D60A0A" fill="none" />
</svg>

background-image: url("data:image/svg+xml,%3C%3Fxml version='1.0' encoding='UTF-8'%3F%3E%3Csvg width='6px' height='3px' viewBox='0 0 6 3' version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink'%3E%3Cpath d='M0,2 C1.5,2 1.5,0.5 3,0.5 C4.5,0.5 4.5,2 6,2' stroke='%23D60A0A' fill='none' /%3E%3C/svg%3E%0A");

I didn't see any process listed for UI design, so I though I would bring this up as a feature request. I would be happy to go through the designers for VSCode before submitting a pull request to change it, as they would have more context on why it is this way

Usability issues with squiggles for errors are brought up in https://github.com/Microsoft/vscode/issues/16204, but I think it's outside the scope of this issue

Oh, just noticed there is some design discussion going on in https://github.com/Microsoft/vscode/issues/8017 with regard to visual style, perhaps @misolori is one of the right people to see this since it should all look good together.

I think I'll be able to tackle this for this month, I do like the smoother lines you proposed. Thanks!
Code pointer:
https://github.com/microsoft/vscode/blob/877ce7ac034390e31c5ecebccbb0683bd2c51c3d/src/vs/editor/browser/widget/codeEditorWidget.ts#L1797-L1798

@darknoon  I've currently got a branch under misolori/squiggles that updates the squiggles to be just as you suggested and I'm not sure I'm a fan of the smoother lines:
Current

Proposed

Our current version is a lot crisper, which the straight edges help with, and with the proposed they feel a bit "smudged".

Unsure - the proposed design looks somewhat flat despite having the same hight (I assume)

After thinking this over and playing with the new squiggles, I don't think this something that we'd want to introduce since this doesn't looks crisp as I mentioned above. For this reason I'll be closing this issue and marking it as out-of-scope. If we ever revisit this in the future we can re-open.


Make training argument optional when calling ViTDINOBase

https://github.com/sayakpaul/probing-vits/issues/27

Thanks!


Cache rubocop in travis-ci

What was the end-user problem that led to this PR?
We run rubocop on every build that goes through every file looking for any breaking rules. Currently this takes about ~30s to execute. We also have the linting step required to pass before any other steps are executed, so having this step execute as fast as possible is important to developers.
I think there is a small optimize we can make to the build time by caching rubocop between builds.
What is your fix for the problem, implemented in this PR?
Have travis cache the results from rubocop between builds to speed up build times

@bundlerbot r+


Okello sam21 patch 4

Related Issue
Closes: #185
Describe the changes you've made ✍
I have added a java code to demonstrate the below screenshot.
Screenshots (if any) 📸

@OkelloSam21 if you want to add your own patterns which are not in this repo, you can do it and the procedure is mentioned here

@OkelloSam21 code works fine, but put this file in the Pattern48 folder.

sure

done


Update Gravity mechanism/tag

Post 1.9, the gravity NBT tag works with all entities, not just armor stands.
It'd be pretty useful if we could have that updated to work.

Is there any difference between this, and the has_ai functionality currently implemented?

Oh yeah, has_ai only affects mobs, not all entities.
For instance, the dropped_item and falling_block entities are not affected by it. There may be others as well, I assume the boat entity doesn't rely on AI.


Taps doesn't work

I can't ues tap  Feature in notion notion enhancer If I close the tap feature It work
screenshots

windows 10

see https://github.com/notion-enhancer/desktop/issues/606, use notion-repackaged instead of manually patching if you aren't already.


Joining machines to a swarm

Support joining machines to swarms from machines picker

It's better to just ssh onto a machine and join it to a swarm from there, makes no sense to implement additional features.


add description for snap users for cadvisor

When using defaults and docker-compose up
Snap users get the following
ERROR: for cadvisor  Cannot start service cadvisor: error while creating mount source path '/var/lib/docker': mkdir /var/lib/docker: read-only file system
Any idea what path should be used in docker-compose.yml?
/:rootfs:ro
/var/lib/docker:/var/lib/Docker - Doesn't exist with snap.

@mspencerl87 could you clarify what you mean by snap, what's that in reference to?

sudo snap install docker..
I would just close this.
I tested this across two hosts, it seems to be a issue with the docker snap package itself and not this repository..
Trying to reach out to launchpad


[WIP] Ti msg ack

Some background / context on this change would be good.
I assume we don't want a message to be ACKed if the TriggerInstance (or underlying Trace) creation fails, right?
Also, afaik, Trace creation should be / is best-effort anyway and we proceed even if it fails, right?

Some background / context on this change would be good.

Yes, will get more info out.

Also, afaik, Trace creation should be / is best-effort anyway and we proceed even if it fails, right?

Yes. There are some quirks in how I handled async creation etc which makes is a bit tricky to not depend on trace create but I will fix that part. It is not something I am focusing on at this point.

Looking forward to CLI and API changes.


Small improvements

@cmboling @johnlugton

Yeah, we should move things over soon indeed. I'll see whether I can get familiar with the necessary steps this week.
Re: John: Makes sense, I'll stop mentioning him.


[Feature Request] Please implement data breakpoints

VSCode already had the capability to enable data breakpoints since VSCode 1.38 (August 2019). So can we have this powerful and useful feature available in the OmniSharp C# extension, please?

Note that .NET Debugging services doesn't support data breakpoints on platforms other than Windows, and the mission of this extension is to deliver a cross-platform experience. So this isn't something that will be added anytime soon -- .NET would need to add support, which isn't an easy task. But I am happy to keep the issue around for people to vote in favor of the issue.
For anyone not aware: full Visual Studio supports data breakpoints on Windows. So if you are on Windows and want the feature, I would suggest debugging there.


Feature Request: Simulator Management

Managing simulators in Xcode is unfortunately quite a pain. The biggest issue is that every version of Xcode, all of the simulators are reinstalled, and you can only remove them one by one. The less time-consuming (yet time-consuming) approach is usually to delete them all and add them back one by one.
It'd be great to have a way to do this through ControlRoom to batch up requests, rather than doing it one by one every few months.
Upon suggestion from @twostraws, one idea would be to add an Edit/Done button for the current sidebar to show a list of checkboxes, with a delete button in that context to formalize the action.
An alternative idea I'd propose would be to provide identifiers for the simulators you'd like to install.
Thanks a lot!

How does that change work for you, Joe? You can select however many you want at once, right-click, then choose Delete.


Trying to alter timing nothing happens when clicking on UPDATE button, deploy stuck

When I update the timing setting on an existing node, very often the update window doesn't close when I click on "Update".
If I press cancel and then try to deploy, it hangs. Reloading the web page doesn't show the changes made in the update.
Any idea what could cause this?

I just have restarted Node Red. It's running as a Home Assistant Add-on.
After that, I did return from the "Update" window, but a Deploy still hangs.

Hi @rholighaus,
I don't know anything about HomeAssistant.   But you can try to do this:

Open the developer tools of your browser.
Repeat your steps that fail.
Look in the Console tabsheet of your developer tools if there are any errors, and share them here.

Bart


Stop using custom_cmd for control-plane DAGs

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[x] Optimization
[ ] Documentation Update

Description
Remove the usage of custom_cmd and use e2e-benchmarking instead for kube-burner based tests. Thanks to this change we don't need any of binaries in the image anymore

Codecov Report

Merging #354 (e083949) into master (745ea2c) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #354      +/-   ##
==========================================
- Coverage   79.06%   78.96%   -0.10%
==========================================
  Files          22       22
  Lines        1003     1003
==========================================
- Hits          793      792       -1
- Misses        210      211       +1

Flag
Coverage Δ

gha
78.96% <ø> (-0.10%)
:arrow_down:

python-3.9
78.96% <ø> (-0.10%)
:arrow_down:

unit
78.96% <ø> (-0.10%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes


TypeError: fs.existsSync is not a function

webpack-internal:///./node_modules/vue-router/dist/vue-router.esm.js:2305 TypeError: fs.existsSync is not a function
at read (webpack-internal:///./node_modules/i18n-factory/i18n.js:670)
at eval (webpack-internal:///./node_modules/i18n-factory/i18n.js:76)
at Array.forEach ()
at Object.i18nConfigure [as configure] (webpack-internal:///./node_modules/i18n-factory/i18n.js:75)
at Object.eval (webpack-internal:///./node_modules/@rimiti/invoice-it/dist/lib/i18n.js:14)
at eval (webpack-internal:///./node_modules/@rimiti/invoice-it/dist/lib/i18n.js:30)
at<EMAIL_ADDRESS>(5.js:1090)
at webpack_require (app.js:854)
at fn (app.js:151)
at eval (webpack-internal:///./node_modules/@rimiti/invoice-it/dist/classes/generator.js:24)
abort @ webpack-internal:///./node_modules/vue-router/dist/vue-router.esm.js:2305

This package can only be used in backend mode.

FS il the FileSystem nodejs api


Help I can't find the .env file.

Describe the bug
I can't find the .env file to put the .env.example in.
Reproduction

uh I just cant find it
?

Expected behaviour
to easily find the file
Logs
No response
System info
Bun 1.1.27

.. you rename the .env.example to .env
???

The .env.example file is in the site directory, you just rename that to .env and that is all you need to do for it

.. you rename the .env.example to .env ???

thanks shedletsky

you should close the issue now

you should close the issue now

how do i get the docker command to work in my terminal

what do you mean?

how do i get the docker command to work in my terminal

please create a separate issue for this


Resource methods in interfaces

Resource methods in interfaces (default implementations) are now picked up when registering providers.
This PR supersedes #1574
(this PR is a subset of #1574, as it does not include any actual interfaces with default implementations)

@ttntrifork confirmed, sorry about that. The failing test on master has been resolved.

@jamesagnew thanks, but your master seems to be failing for me locally still.
The test SubscriptionTriggeringDstu3Test.testTriggerUsingOrSeparatedList_MultipleStrings is failing.
Should I just not worry about the failing build of this PR? Will it be reviewed and considered for approval regardless? :)

HI @ttntrifork - Would you be able to merge master into this branch one more time just so we can get a clean CI build? We've had some stability issues lately but they appear to be settled down now. Much appreciated.
This does look good, and sorry for the extra steps. I'm hoping we're back to solid green on CI now.


Using without Composer seems to be deprecated?

Hi,
I have tried to use the full download by uploading to a server but it still has the Composer related error messaged.
Does the related instruction need to be removed?
The last one I could find that works without composer is version 1 but that won't connect to the API. So is pointless.

Downloading without composer IS supported! See this section of the README. Just download the release (w/ bundled vendors) from the releases page.

I think I tried that but I installed Composer on my shared server with SSH and it all works great now. =)


Add version checks for guppy and lib

After starting the guppy server but before connecting a client, I should do a check that the guppy server version matches the installed guppy client lib version.
I think I can do this with some API calls to the server and some lib version check stuff for the lib.
This should help give a more informative error in the case where they don't match but the output is...weird and not helpful.

Ahh i already do such a lib check using
major, minor, patch = [int(i) for i in pyguppy_client_lib.__version__.split(".")]

Add this into the lib checks, with the exception that 7.3.9 and 7.3.10 are the same, and not wrong.


SEO links: rewrites for pages URIs

https://github.com/unaio/una/commit/d3d998fa89120cad4138cd7b551454866009ab16


Nächster Donnerstag, Fail !!!

when i try to get next Thursday date with German language request it returns now() with status code 0.
request text Nächster Donnerstag(Naechster Donnerstag)

This is related to #102 if you don't mind adding a response to that issue. I was trying to improve the German locale based on some suggestions that came in but I ran into a few deeper issues with getting any of the customizations to work. Any examples that you can provide of common date phrases (and any alternate conjugations) that do not work properly would be helpful.


oj d https://atcoder.jp/contests/utpc2011/tasks/utpc2011_1 is broken

This contest seems different from any other contests in AtCoder (HTML).

Same problem has already been discussed in #106.


⚠ GitLab Server has degraded performance

In 47c35e9, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 13660 ms

Resolved: GitLab Server performance has improved in efcfd51.


Visual studio blazor templates preview 7 - client side and full stack both show same descriptions

With the latest preview version of visual studio (16.3 Preview 1) - if you create a new Blazor project from the "File -- New" then it shows 3 different Blazor templates to choose from but 2 of them show the exact same description. The 2nd and 3rd  ones say "Blazor WebAssembly App" and they have the same description that says "A project template for creating a Blazor app that runs on WebAssembly. This template can be used for web apps for rich dynamic user interfaces (UIs)."
They create different templates too -- one creates the one known as a "full stack webassembly" (with the 3 projects) and the other one creates the client-only blazor template (1 project created).

Can you please report this issue from the "Send Feedback" option within Visual Studio?

Closing as it's not a dotnet related issue.


get_webrtc fails with 'gyp_webrtc.py -Dextra_gyp_flag=0 returned non-zero exit status 1' error.

I am running the build scripts in VirtualBox with Ubuntu 14.04 64-bit. After resolving numerous errors, finally I am stuck at this:-
________ running 'download_from_google_storage --directory --recursive --num_threads=10 --no_auth --quiet --bucket chromium-webrtc-resources src/resources' in '/media/ag/External HD/webrtc-build-scripts-master/android/webrtc'
2> Downloading src/resources/far44_stereo.pcm...
5> Downloading src/resources/verizon3g-downlink.rx...
1> Downloading src/resources/audioproc.aecdump...
6> Downloading src/resources/paris_qcif.yuv...
0> Downloading src/resources/far48_stereo.pcm...
8> Downloading src/resources/short_mixed_stereo_48.dat...
3> Downloading src/resources/near32_stereo.pcm...
......
0> Downloading src/resources/rtp_rtcp/RTCPPacketTMMBR0.bin...
9> Downloading src/resources/rtp_rtcp/H263Foreman_CIF_Pframe.bin...
Hook 'download_from_google_storage --directory --recursive --num_threads=10 --no_auth --quiet --bucket chromium-webrtc-resources src/resources' took 606.83 secs

________ running '/usr/bin/python src/webrtc/build/gyp_webrtc.py -Dextra_gyp_flag=0' in '/media/ag/External HD/webrtc-build-scripts-master/android/webrtc'
Updating projects from gyp files...
gyp: Call to './build/linux/sysroot_ld_path.sh /media/ag/External HD/webrtc-build-scripts-master/android/webrtc/src/build/linux/debian_wheezy_amd64-sysroot' returned exit status 1 while in all.gyp.
Error: Command '/usr/bin/python src/webrtc/build/gyp_webrtc.py -Dextra_gyp_flag=0' returned non-zero exit status 1 in /media/ag/External HD/webrtc-build-scripts-master/android/webrtc

Tips for others, if you are using VirtualBox. Make sure to allocate atleast 2GB of RAM else git will die with code -9. Also make sure to use 64-bit Ubuntu not 32-bit. And do not use shared folders. The folder where you run these commands should be a VirtualBox HDD. On Shared folders symlinks creation will fail.
One more question, everywhere I see that the total size could be around 5-6GB, but for me it is 28GB and still counting!

It went away when re-ran get_webrtc.

still have this error  with get_webrtc.
can you share your latest  build lib?


libRDBoost.so.1: undefined symbol

I tried to build and import rdkit with Python.
But there was an error like this.
>>> from rdkit import Chem
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/root/rdkit-Release_2015_09_2/rdkit/Chem/__init__.py", line 18, in <module>
    from rdkit import rdBase
ImportError: /root/rdkit-Release_2015_09_2/lib/libRDBoost.so.1: undefined symbol: _ZN5boost6python23throw_error_already_setEv

You can reproduce this with
docker run -it kozo2/rdkit-notebook bash
cd
PYTHONPATH=~/rdkit-Release_2015_09_2/ LD_LIBRARY_PATH=~/rdkit-Release_2015_09_2/lib python
>>> from rdkit import Chem
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/root/rdkit-Release_2015_09_2/rdkit/Chem/__init__.py", line 18, in <module>
    from rdkit import rdBase
ImportError: /root/rdkit-Release_2015_09_2/lib/libRDBoost.so.1: undefined symbol: _ZN5boost6python23throw_error_already_setEv

The docker file is https://github.com/kozo2/rdkit-notebook/blob/master/Dockerfile

Something certainly changed when we made thread safe the default.  I updated your Dockerfile (see below)
to include boost-system boost-thread and boost-serialization and everything worked as expected (the Dockerfile is below).  I think these should be your defaults, otherwise, you can't do multithreaded conformer generating or substructure searching which can be useful.
I'm still going to file this as a bug, because if system is now a dependency, cmake should fail.
FROM ubuntu:14.04
RUN cd; apt update; apt install -y wget flex bison build-essential python-numpy cmake python-dev sqlite3 libsqlite3-dev libboost-dev libboost-system-dev libboost-thread-dev libboost-serialization-dev libboost-python-dev libboost-regex-dev; wget https://github.com/rdkit/rdkit/archive/Release_2015_09_2.tar.gz; tar xf Release_2015_09_2.tar.gz; cd rdkit-Release_2015_09_2; mkdir build; cd build; cmake ..; make; make install

Thanks @bp-kelley
https://hub.docker.com/r/kozo2/rdkit-notebook/builds/ works well now.
Is it possible that I send pull request to update http://www.rdkit.org/docs/Install.html#building-from-source ?
Is there public github repository for http://www.rdkit.org/docs ?

The documentation is here:
https://github.com/rdkit/rdkit/tree/master/Docs/Book
Please feel free to submit a PR against it.

Thanks @greglandrum
I sent a pull request to https://github.com/rdkit/rdkit/pull/765

Fixed and merged.

I tried latest version of RDKIT from GitHub and I had the same issue with cartridge. Althought I succesfully builded the rdkit and I could import Chem from rdkit but when I tried to add cartridge by:
postgres psql -c 'create extension rdkit' mydatabase
I got the same error:
rdkit.so: undefined symbol:  _ZN5boost6python2thread_data_baseE

I just updated my Anaconda to contain rdkit.2016.03. I get basically the same error.
import Chem from rdkit
libboost_serialization.so.1.56.0: undefined symbol: _ZN5boost13serialization6detail17singleton_wrapperINS_7archive6detail12extra_detail3mapINS3_15binary_oarchiveEEEEE14m_is_destroyedE
Is their a different rdkit I should be using. I used conda install -c rdkit rdkit

@jt-swanson : What system are you installing on? It seems odd to me that you would get a version that old.

I have a couple 'legacy' Linux systems. They run RedHat RHEL 5. I've been using them mostly for running scikit-learn. I have Anaconda 4.3.1 installed. That's all been working fine. I've been running rdkit on Windows. I am using Anaconda 4.2.0 there. When I installed rdkit on Windows through conda, it also installed 2016.03.1. On Windows rdkit is quite happily running. But if I could get it running on Linux, I could use it along with some other (legacy) software that also has a Python interface, but doesn't run on Windows.
I installed rdkit using
conda install -c rdkit rdkit
it reverted a lot of packages back to older versions to install rdkit, including boost.
I also tried
conda install -c rdkit boost=1.56.0
but conda just came back and said that was what was installed.
I can run
conda install -c rdkit rdkit=xxxx.xx
but the only one I found to work was 2016.03, though the anaconda repository claims the current version is 2016.09.

Is that system by any chance legacy enough that it's 32bit?

I have a couple system. I was trying to get things running on the machine that has 32bit Linux installed. I do have one machine that has 64bit Linux installed. The processors are 64bit Xeon.
I did the install on the machine with 32bit Linux. I see exactly the same message trying to run on either machine (with the 32bit version of Anaconda/rdkit).

Yeah, you are getting the old RDKit builds because you have 32 bit Linux installed.
Given the effort involved and lack of demand, I have stopped doing builds for 32 bit Linux systems.
Assuming you actually need the RDKit on that old machine your best option is probably  to do a build yourself (not impossible, but not trivial).

I'm not surprised the demand is low. An IT guy installed Linux on these systems many moons ago. Despite the fact that they have 64bit processors and 64bit Linux was available, he was quite insistent that 32bit Linux was  the way to go. I have one system with 64bit Linux (I installed that OS). It's still RHEL 5. When I ask conda to install rdkit, however, it still wants to install 2016.03.
Is this a Continuum Analytics thing- they don't have anything newer through conda? Are there any archived rdkit builds that are older and don't have the particular problem I am seeing?

It's not just a matter of 32bit versus 64bit. I installed the 64bit Anaconda4.3.1 and then ran conda install -c rdkit rdkit. It installed boost-1.56.0-py27_3 and rdkit-2016-09.4-nplllpy27_1. The install was cleaner in that no other packages were upgraded or downgraded. However, the result is the same. When I try from rdkit import Chem, I see the same libboost_serialization.so.1.56.0: undefined symbol error.


change slide order to match notebook order

Preprocessing --> Unsupervised --> Supervised

@brooksjessup can you swap these real quick?


Question about Additional Entity Attributes

About this one:
BONUS_RARE_LOOT_ROLLS: The number of times the chance-based loot table is rolled.
It accepts a float in the value. How does that work if it does? (Sorry I'm opening this as an issue, I didn't see anywhere else I could put it)

A value of 1.0 will result in 1 additional roll with the original chance. So if a drop has a 10% chance:

BONUS_RARE_LOOT_ROLLS=1.0 will roll another time with 10% chance
BONUS_RARE_LOOT_ROLLS = 2.0 will result in another roll with 20% chance
BONUS_RARE_LOOT_ROLLS = 0.5 will result in another roll with 5% chance

Thanks! That’s an interesting way of doing it, I assumed each one would be an extra roll, not one roll with modified/extra chance.

if you don't mind answering this too, what exactly do the values for bonus_loot_count_rolls work? my assumption originally was that it was more drops like rotten flesh but that's not how it worked in my tests

Some mobs have rare drops. Zombies have a small chance to drop a carrot, potato or iron ingot, and wither skeletons their head. These drops are what the rolls affect.

i didn't notice a difference between the two value but i might've set the values wayyy to high so if you do find the difference lmk

I had a test and the bonus loot count tools doesn’t seem to work for me at least. I observed no difference in drops when I had it set to 128 to when not with and without the looting enchantment.


Update dependencies and alter privacy of functions

So, this was supposed to be a simple typescript update. But as I found out, in typescript 3.8 the @private means private to the class (and not to the lib as its been used here)
Some of those I changed to @protected (accessible from extended classes)
Some I made public (and removed the underscore).

Removed the underscores from protected. tsc does not know meta.controller is a DatasetController etc, so there might be quite a few things still "not right"


Test failure: CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnAction

This issue was made automatically. If there is a problem contact ryanbrandenburg.
This test failed with the following error:
Assert.Equal() Failure
Expected: String[] ["*"]
Actual:   String[] ["Custom"]
   at Microsoft.AspNetCore.Mvc.FunctionalTests.CorsTestsBase`1.CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnAction() in /_/test/Microsoft.AspNetCore.Mvc.FunctionalTests/CorsTestsBase.cs:line 344
--- End of stack trace from previous location where exception was thrown ---

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC mkArtakMSFT

This comment was made automatically. If there is a problem contact ryanbrandenburg.
Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

Is there any logging or extra information that we could add to make this more diagnosable when it happens again?

Yes?

[ ] Add the logging (TODO: Link to PR/commit)

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 5 failures with about the same error on master at 1:52:06 AM:

CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnController
CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnAction
CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnController
SuccessfulPreflightRequest_AllowsCredentials_IfThePolicyAllowsCredentials
SuccessfulPreflightRequest_AllowsCredentials_IfThePolicyAllowsCredentials

This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 6 failures with about the same error on master at 2:30:07 PM:

CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnController
SuccessfulPreflightRequest_AllowsCredentials_IfThePolicyAllowsCredentials
CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnAction
CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnAction
SuccessfulPreflightRequest_AllowsCredentials_IfThePolicyAllowsCredentials
CorsFilter_RunsBeforeOtherAuthorizationFilters_UsesPolicySpecifiedOnController

@Pranav did you not take care of this failure or does it need to propagate to the rest of the build.

Pranav took care of this


Don't display viewing hint/direction for all colls

Closes #425.

Looks like the build is hanging on jetty_wait.  I'll try restarting it.


Update Gradle

Gradle is outdated on most of the sample apps and they cannot be built on JDK 11 or 17.

@ #``

It's updated in this commit (not yet merged): https://github.com/android/camera-samples/pull/489/commits/b269dc18c3d313d1de7f0e2734e71059611a8d3a


Adds boilerplate to repo

Making a new report to share a util that will be used in the cli.

@dipack95 im going to move out this class so that it can be consumed by @transcend-io/cli for a script to upload DSRs