Bot sometimes does not join meeting: Server Internal Error. DiagCode: 500#7117

Describe the issue
Sometimes when inviting the bot to a meeting, the call stays stuck in "Establishing", before eventually getting "terminated" with an HTTP 500 server error.
Scenario
We have the sample setup and it works pretty most of the time. But there seem to be random moments/hours where we can not get the bot to join the call and it's the one thing stopping us from implementing this successfully.
Because it's highly unpredictable when our integration does and does not work. The same software, without any new changes in the infrastructure or code. Sometimes works 100% of the time and on certain days it drops down to 20%.
By not working I mean - the bot not joining the call. This is the only issue. Once the bot actually joins and the call is established, all audio media is received just as expected.
We can usually get it to work by re-inviting the bot many times, but this is not practical for our users.
Scenario:

Create a meeting
Invite the bot to the call through the JoinCallController, which runs all the way up to the .AddAsync() of the BotService class as shown in the sample. This also executes successfully and the request is sent to microsoft.

We then receive an "Establishing" message back. However we then sometimes never receive the "Established" callback. After a period of about a minute, we end up receiving a "Terminated" status update with the error code:
Server Internal Error. DiagCode: 500#7117
Code Snippet
var statefulCall = await this.Client.Calls().AddAsync(joinParams).ConfigureAwait(false);
This runs successfully, but we never receive the Established callback.
Expected behavior
I expect microsoft to (eventually) send us the "Established" callback to our platform signaling endpoint. Which it sometimes does not.
Graph SDK:
Microsoft.Graph.Communications.Calls" Version="<IP_ADDRESS>0"
Microsoft.Graph.Communications.Client" Version="<IP_ADDRESS>0"
Microsoft.Graph.Communications.Common" Version="<IP_ADDRESS>0"
Microsoft.Graph.Communications.Core" Version="<IP_ADDRESS>0"
Microsoft.Graph.Communications.Calls.Media" Version="<IP_ADDRESS>0"
Microsoft.Skype.Bots.Media" Version="<IP_ADDRESS>-alpha"

Call Chain ID
adb8687d-12fc-4878-a1c9-66a28a168403
Logs
Establishing received:
{
    "@odata.type":"#microsoft.graph.commsNotifications",
    "value":[
       {
          "@odata.type":"#microsoft.graph.commsNotification",
          "changeType":"updated",
          "resource":"/app/calls/39003780-ad9d-42d2-a09c-bee3a0721389",
          "resourceUrl":"/communications/calls/39003780-ad9d-42d2-a09c-bee3a0721389",
          "resourceData":{
             "@odata.type":"#microsoft.graph.call",
             "state":"establishing",
             "chatInfo":{
                "@odata.type":"#microsoft.graph.chatInfo",
<EMAIL_ADDRESS>                "messageId":"0"
             },
             "meetingInfo":{
                "@odata.type":"#microsoft.graph.organizerMeetingInfo",
                "organizer":{
                   "@odata.type":"#microsoft.graph.identitySet",
                   "user":{
                      "@odata.type":"#microsoft.graph.identity",
                      "id":"6200feed-a0e8-49c0-95a9-e5bbb4d3d1c5",
                      "tenantId":"<ommitted>"
                   }
                },
                "callChainId":"adb8687d-12fc-4878-a1c9-66a28a168403"
        }
    ]
}

Terminated 500 7117 received
{
    "@odata.type":"#microsoft.graph.commsNotifications",
    "value":[
       {
          "@odata.type":"#microsoft.graph.commsNotification",
          "changeType":"deleted",
          "resource":"/app/calls/39003780-ad9d-42d2-a09c-bee3a0721389",
          "resourceUrl":"/communications/calls/39003780-ad9d-42d2-a09c-bee3a0721389",
          "resourceData":{
             "@odata.type":"#microsoft.graph.call",
             "state":"terminated",
             "resultInfo":{
                "@odata.type":"#microsoft.graph.resultInfo",
                "code":500,
                "subcode":7117,
                "message":"Server Internal Error. DiagCode: 500#7117.@"
             },
             "chatInfo":{
                "@odata.type":"#microsoft.graph.chatInfo",
<EMAIL_ADDRESS>                "messageId":"0"
             },
             "meetingInfo":{
                "@odata.type":"#microsoft.graph.organizerMeetingInfo",
                "organizer":{
                   "@odata.type":"#microsoft.graph.identitySet",
                   "user":{
                      "@odata.type":"#microsoft.graph.identity",
                      "id":"6200feed-a0e8-49c0-95a9-e5bbb4d3d1c5",
                      "tenantId":"<ommitted>"
                   }
                },
                "callChainId":"adb8687d-12fc-4878-a1c9-66a28a168403"
             }
          ]
       }

Additional context

We only run a single instance (one on our Dev environment, one on our prod environment). During these 'broken' moments, it happens in either environment.
This happens regardless whether this is a new or old meeting
This happens regardless of the participant state in the meeting in question
This only happens SOMETIMES. Sometimes the bot joins 100% of the time for a whole day, then on some days, the bot joins 20% of the time, under the exact same conditions.

Please take a look at this item and make sure you are not doing anything silly with TLS termination: https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/457

Please take a look at this item and make sure you are not doing anything silly with TLS termination: #457

Thank you @InDieTasten I did come across that thread. But if this were the root cause, wouldn't I experience consistent failures rather than intermittent ones?

Hello @leroypijlman
I've taken a look but so far cannot tell what the reason for your sporadic call setup failures is.
Is your bot running in Azure?
Thanks.

@ssulzer Thank you for your answer. I was afraid of hearing that...
We have the option to migrate to Azure, however this will be a big operation for us (think complicance and internal policies). Is there any clues in the MSFT logging that this is indeed related to this?
Some form of reassurance that this is indeed related to the bot not running in Azure would be most welcome.
Migrating to Azure and still issue still occurring would be ... "hell". 🔥

Our platform service has TCP connection timeouts trying to reach your bot during call session setup.
If you can capture incoming TCP traffic to your bot VM(s), there should be TCP packets from the following Office365 IP address ranges during call session setup (after you have started the call join process and received the "Establishing" notification):
<IP_ADDRESS>/14
<IP_ADDRESS>/15
On the bot's local network interface, these TCP packets should be going to the InstanceInternalPort specified in your MediaPlatformInstanceSettings.
One option to consider: if you have a lot of application "machinery" running in another cloud which post-processes the audio/video received from the Teams meeting, can you at least move the portion of the bot which uses the media SDK (Audio/VideoSocket APIs) into Azure?
So that at least the application's real-time media endpoint connected to the Teams meeting is running in Azure. And then have that bot app transport the received media over to the rest of the application running elsewhere, ideally over a lossless, reliable transport (like a websocket).

@leroypijlman Perhaps a bit of a shameless plug, but if you decide to migrate to Azure, do not hesitate to hit me up. While nobody will be able to help you with internal processes directly, I could at least offer assistance regarding technical hurdles during migration. Options like no downtime migration can alleviate some pain points for internal discussions for example.

Really appreciative of your answers and overall helpfulness @InDieTasten @ssulzer Thank you so much.
I managed to deploy the bot to a basic VM2022 (quick manual setup), just to see if I could reproduce the issue. As of right now - it's working well. We'll assess this over the next couple of days with some actual user load. If it proves to alleviate the problem, we'll follow @ssulzer advice and just host the bot instances in Azure and send it downstream through websockets.
The Only downside being... having to manage an extra k8s(AKS) cluster with a separate cloud provider. (We already have 5 of our own data centers and 1 aws cluster.) Ops is not going to like this. 😅
One concern that I do have, is, whether my current basic VM setup is a good representation. e.g. maybe the issue was really just occurring due to the bot running in k8s (which should not matter, but still..)
Because I find it odd that those call signaling messages timed-out.  Whenever the call did get established, 99,9999% of the audio packets were being received successfully. QualityOfExperience metrics were close to being lossless even during heavy load. Same goes for all other messages, which never seemed to get lost. Making me think wonder if this wasn't a bug in this particular callback.
I'll post back whether it worked and know where to find you if I do get stuck. 🙏

Given a choice, my preference/recommendation is to run a media bot endpoint in a "basic VM setup" versus running within a Windows container.

If all your load is capable to run on a single machine and you aren't concerned about uptime during Windows updates, configuration changes or application updates, I would agree with ssulzer.
If automated scaling, high-availability and rolling deployment strategies are of interest, I would recommend AKS.

Over 2 months later I return to this thread to again seek for your assistance.
Our infra department has been working OT to get an Azure cluster up and running which is now finally live.
We have deployed our teams bot software there, similarly to the way we did this in our previous cluster.
Unfortunately we are still plagued with the issue as mentioned in the original post of this thread.
The bot sometimes does not receive the callback. On subsequent invite attempts it joins eventually. But after about a minute of that bot joining, it's instructed by teams to leave. Which gives me the impression that "reinviting until it works" is not intended since it causes the bot to get kicked. So retrying the invite is not really an option.
Can you please dig into the logs to see if you can find any meta data for us that can be of assistance?
Here's some metadata:
Establishing
{
<EMAIL_ADDRESS>"#microsoft.graph.commsNotifications",
    "value": [
        {
<EMAIL_ADDRESS>"#microsoft.graph.commsNotification",
            "changeType": "updated",
            "resource": "/app/calls/05005180-709a-43c2-8264-3d12938e1155",
            "resourceUrl": "/communications/calls/05005180-709a-43c2-8264-3d12938e1155",
            "resourceData": {
<EMAIL_ADDRESS>"#microsoft.graph.call",
                "state": "establishing",
                "chatInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.chatInfo",
                    "threadId"<EMAIL_ADDRESS>                    "messageId": "0"
                },
                "meetingInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.organizerMeetingInfo",
                    "organizer": {
<EMAIL_ADDRESS>"#microsoft.graph.identitySet",
                        "user": {
<EMAIL_ADDRESS>"#microsoft.graph.identity",
                            "id": "fbe232de-fdb4-40fb-bbd4-222b2bc44d3a",
                            "tenantId": "<redacted>"
                        }
                    },
                    "callChainId": "e2cc7f79-0326-436c-a2b1-80f381ba5a20"
                }
            ]
        }

Terminated
{
<EMAIL_ADDRESS>"#microsoft.graph.commsNotifications",
    "value": [
        {
<EMAIL_ADDRESS>"#microsoft.graph.commsNotification",
            "changeType": "deleted",
            "resource": "/app/calls/05005180-709a-43c2-8264-3d12938e1155",
            "resourceUrl": "/communications/calls/05005180-709a-43c2-8264-3d12938e1155",
            "resourceData": {
<EMAIL_ADDRESS>"#microsoft.graph.call",
                "state": "terminated",
                "resultInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.resultInfo",
                    "code": 500,
                    "subcode": 7117,
                    "message": "Server Internal Error. DiagCode: 500#7117.@"
                },
                "chatInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.chatInfo",
                    "threadId"<EMAIL_ADDRESS>                    "messageId": "0"
                },
                "meetingInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.organizerMeetingInfo",
                    "organizer": {
<EMAIL_ADDRESS>"#microsoft.graph.identitySet",
                        "user": {
<EMAIL_ADDRESS>"#microsoft.graph.identity",
                            "id": "fbe232de-fdb4-40fb-bbd4-222b2bc44d3a",
                            "tenantId": "<redacted>"
                        }
                    },
                    "callChainId": "e2cc7f79-0326-436c-a2b1-80f381ba5a20"
                }
            ]
        }

Where a successful instance usually contains an "Established" message.
@ssulzer can you confirm whether or not this is still related to TCP connection timeouts?
I want to have our infra department analyze this for us and I want to be able to give enough details to aid their search.

@leroypijlman
Hi
Were you able to identify the source of the problem and resolve it?
I only get this same error ("Server Internal Error. DiagCode: 500#7117.@") when running the bot locally.

@arantar Unfortunately not. Can you describe your local setup? Are you using ngrok?
For us it only seems to happen when running it inside of kubernetes.


Add unit test

Describe the bug
It will be better to have enough test cases to bring a feature breaking existing feature when making changes
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

what's the best approach @oesukam ? because webase is modular...then each modules can contains his own testcase...
instead of putting in the application folder

unit testing has been added
run test with : vendor/bin/phpunit -c application/tests/
or adding future testcase following example of dahsboard

this issue is done successfully the develop branch build successfully with Travis


How to transfer this model to onnx?

I'm not familiar with ONNX, but since my implementation is based on Detectron2, you can probably try this: https://github.com/facebookresearch/detectron2/blob/master/tools/deploy/export_model.py


feat(csharp/Client): Implement support for primary schema collections

Adds support for MetaDataCollection, Restrictions, Catalogs, Schemas, TableTypes, Tables and Columns.

I verified these


Crash on writeCopy method call

How frequently does the bug occur?
All the time
Description
I'm trying to copy the local realm DB file using Realm.writeCopy(for: Configuration) method. But every time I get an Assertion failed: val.is_type(type_Link, type_TypedLink) error.
Stacktrace & log output
...realm-core/src/realm/db.cpp:1239: [realm-core-11.13.0] Assertion failed: val.is_type(type_Link, type_TypedLink)
0   MyApp                           0x0000000101c34b80 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   MyApp                           0x0000000101c34dac _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 224
2   MyApp                           0x000000010150ed5c _ZZN12_GLOBAL__N_127generate_properties_for_objERN5realm11ReplicationERKNS0_3ObjERKNSt3__16vectorINS6_4pairINS0_6ColKeyEPNS0_5TableEEENS6_9allocatorISC_EEEEENK3$_9clENS0_5MixedE + 128
3   MyApp                           0x00000001014fe650 _ZN12_GLOBAL__N_127generate_properties_for_objERN5realm11ReplicationERKNS0_3ObjERKNSt3__16vectorINS6_4pairINS0_6ColKeyEPNS0_5TableEEENS6_9allocatorISC_EEEE + 1600
4   MyApp                           0x00000001014fd290 _ZNK5realm11Transaction9replicateEPS0_RNS_11ReplicationE + 2444
5   MyApp                           0x00000001014fe960 _ZN5realm2DB18create_new_historyERNS_11ReplicationE + 144
6   MyApp                           0x00000001014fef2c _ZN5realm2DB18create_new_historyENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEE + 52
7   MyApp                           0x00000001017bdbb4 _ZN5realm5Realm9export_toERKNS0_6ConfigE + 744
8   MyApp                           0x00000001013ded64 -[RLMRealm writeCopyForConfiguration:error:] + 1032

Can you reproduce the bug?
Yes, always
Reproduction Steps

Create a local realm instance.
Get sync configuration.
Call writeCopy(for: method

try localRealm.writeCopy(configuration: currentConfiguration)

Version
10.25.0
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 15
Build environment
Xcode version: 13.2.1
Dependency manager and version: SPM

Hi @Bogdan-Belogurov
Can you share realm configuration and objects schema?

Hi! @pavel-ship-it
Sorry, I can't share an objects schema for you 😓

@pavel-ship-it
If this error depends on the object schema, could you please explain the meaning of the error, and maybe I can understand why it happens.

@pavel-ship-it
I have reinstalled my app to have the latest schema version and still have this issue.

@pavel-ship-it
Are there other solutions to move all data from the local realm to synced?

@pavel-ship-it I have reinstalled my app to have the latest schema version and still have this issue.
So the local Realm is just created and you have some Synced Realm. Am I right?
Were there any change in the remote Schema? Any field type has changed or renamed?

@pavel-ship-it Are there other solutions to move all data from the local realm to synced?
writeCopy is the best way. Let's see how we can find a solution. If there is a privacy concern you can share the sensitive data in private.

@pavel-ship-it

So the local Realm is just created and you have some Synced Realm. Am I right?
Were there any change in the remote Schema? Any field type has changed or renamed?

Before I started working on moving data from the local realm to the synchronized one, in the Realm App I turned on developer mode and synchronized the local schema with the remote one.

It seems this issue was resolved by this PR: https://github.com/realm/realm-core/pull/5456 which was merged back in realm core 11.16, based on the information provided the customer is using swift 10.25.0 which targets realm core 11.13.

@Bogdan-Belogurov
Please upgrade to the latest (or at least past 10.25.0), which includes https://github.com/realm/realm-core/pull/5456
If you still see the same crash, please open a new issue and link to this one.
Thanks


Header fixes

Fixes to a couple of problems that were bugging me about the header. First, the initial year selection (if the user has not chosen anything) was hardcoded to 2021-2022; that is now chosen to be the current year/last one we have records for (assuming years.json is kept in reverse chronological order). Second, I made the year selection and dark/light mode button vertically centered within the header (ish; the switch is slightly off center for reasons I have not figured out yet), which looks nicer. Finally, the "My Pathways" button on the top right now becomes lighter when you hover over it, like the rest of the buttons on the home page.

Oh wow very good changes!! Looks much better in the header now!


Support for VS Community Edition

HI,
is there a way to get this running in VS Community 2019?

Not that I'm aware of. The plugin architecture is not the same with VS as with VSC. I'm sorry to tell yuh.


Format: fix to format newline after &.foo in call

Fixed #7237
Now, the formatter keeps the following code:
foo(
  1,
  &.foo
)

@MakeNowJust Thank you!


Problems with some labels

I'm trying to use the splited data in a study about disagreement and I found out that there are some instances that are mislabeled. I found "0, 0", "1, 1", "0, 0, 0" and "1, 0". For example, the 1850 example_id sample in validation data. Is it a formatting problem?
Thanks in advance.

I have tried to omit the problem by dropping the rows which are not correct:
df = pd.read_csv(dataset_path / '2_splits'/ f'ConvAbuseEMNLP{split}.csv')

    df = df.astype({'example_id': 'int64'})
    annot_columns = [f'Annotator{i+1}_is_abuse.{value}' for value in abuse_values for i in range(8)]
    index_to_drop = []

    for i, row in df.iterrows():
        for c in annot_columns:
            if row[c] not in ['0', '1', np.nan]:
                index_to_drop.append(i)
                break

    df = df.drop(index_to_drop).reset_index(drop=False)
    df = df.astype({c: 'float64' for c in annot_columns})

Unfortunately, it drops a large qunity of data (~10k) so it is half of all annotations. Therefore the test split has no examples labeled as -3, -2, 0 is_abusive. I suggest fixing the entire dataset & reuploading.


Broken installation of OSE 3.7.x as of 2018-03-21

Hello everyone,
2 days ago, packages for OSE v3.7.1 were pushed to http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin37/, however these new v3.7.1 packages are completely broken and install a version which identifies as v3.10 alpha (see https://github.com/openshift/openshift-ansible/issues/7567#issuecomment-374455481).
After re-initializing my deployment and locking the ose_version explicitly to 3.7.0-1.0.7ed6862, the cookbook starts installing the correct version but when installing the origin-node package it somehow tries to install the broken v3.7.1 version instead of the v3.7.0 I requested, as if one of the package resource in this cookbook is not passing the ose_version in the version attribute.
The broken version of origin-node will trigger installation of the broken version of the origin-master packages, resulting in the converge failing with the following output:
==> master: [2018-03-21T08:11:51+00:00] ERROR: yum_package[origin-sdn-ovs] (cookbook-openshift3::node line 105) had an error: Chef::Exceptions::Exec: yum -d0 -e0 -y install origin-sdn-ovs-3.7.0-1.0.7ed6862 returned 1:
==> master: STDOUT:  You could try using --skip-broken to work around the problem
==> master:  You could try running: rpm -Va --nofiles --nodigest
==> master:
==> master: STDERR: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 (centos-openshift-origin37)
==> master:            Requires: origin-node = 3.7.0-1.0.7ed6862
==> master:            Installed: origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 (@centos-openshift-origin37)
==> master:                origin-node = 3.7.1-1.el7.git.0.0a2d6a1
==> master:            Available: origin-node-3.7.0-1.0.7ed6862.x86_64 (centos-openshift-origin37)
==> master:                origin-node = 3.7.0-1.0.7ed6862
==> master: [2018-03-21T08:11:51+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

@jperville I know and I have already got a fix for that shit :-) SHould be pushed ASAP. I have already got it here

I had to fix it here: https://github.com/IshentRas/cookbook-openshift3/blob/master/attributes/default.rb#L34
and here: https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/validate.rb#L21-L23

This is ugly indeed.

Revert my changes as they have released a fix version 3.7.1-2.
Please close if it is now ok on your side. (It should be)

Closing as solved


Pictures are not displayed properly

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.603
Where did you get the app from?
Google Play
Android version
14, build UQ1A.231205.015
Device model
Pixel 6 Pro
Steps to reproduce

Open an e-mail containing pictures.
Some pictures are not displayed properly but others are. See screenshot. Flix logo is displayed but QR code not.

Expected behavior
All pictures must be displayed.
Actual behavior
Some pictures are not displayed properly but others are. See screenshot. Flix logo is displayed but QR code not.

Logs
No response

as noted by the line included at the bottom of your screenshot, the complete message hasn't been downloaded. without the full message it's a tad hard to do complete/accurate rendering.
try downloading the full message and see if you still have an issue.
also note, depending on settings, you may need to explicitly load remote images.

In the future please use the forum for support requests.


Decode nested cats to concrete category

Coverage increased (+0.1%) to 42.6% when pulling cf7e9de7e53252b3354db8d28d30e76568f28378 on nested-cats-transformer into 141df07d6b972cec80c867216d69b41aef7aa8d0 on master.


bugfixes

hi @djoos,
thanks for merging the other two pull requests!
here's a small addition which fixes the following bugs:
Abstract class name is not prefixed with "Abstract" error raised while running into
abstract public function getType();

Use parentheses when instantiating classes error raised while running into
$foo = new My\Qualified\Namespace\Bar();

Thx @wickedOne!


YouTube fails to play songs • 1.20.1

https://www.youtube.com/watch?v=oGi8PDit6cQ should explain the clear issue

Yeah I have also just tested the same scenario with cdn links working but youtube not, could be some incorrect yt-dlp settings or smth

on which operating system did you try to use it? it should be fixed on linux with #21

on which operating system did you try to use it? it should be fixed on linux with #21
For me Windows 11

Thats weird, it should work perfectly fine on Windows, which version of the mod did you use? Did you use it on a singleplayerworld or on a Server (do you know the OS of the Server?)

Thats weird, it should work perfectly fine on Windows, which version of the mod did you use? Did you use it on a singleplayerworld or on a Server (do you know the OS of the Server?)

yeah, I was running it locally singleplayer, version 1.1.0

soon there should be a major release 1.3.0 which fixes a lot of things, i hope it works at that point for you, if not another Issue with more details regarding the problem would be great 👍🏻

Same Issue, I'm on Windows 11 and had a friend who has Windows 10 (NT) and had the same issue + same log output.

soon there should be a major release 1.3.0 which fixes a lot of things, i hope it works at that point for you, if not another Issue with more details regarding the problem would be great 👍🏻

any update on this release?

soon there should be a major release 1.3.0 which fixes a lot of things, i hope it works at that point for you, if not another Issue with more details regarding the problem would be great 👍🏻

any update on this release?

https://github.com/Plompi/VinURL


Mobile WebSites and localstorage

Hi,
having one big js or css asset is great for desktop browsers. However, using this technique for mobile devices has some negative side effects, cause mobile devices often have a quite small browser cache and these big files have to be loaded more often than one might have expected.
It s better to use browsers localstorage to store assets on mobile devices.
Would be great if you could inform me if there are any plans to integrate this technique into sprocket or rails in general.
Thanks a lot in advance.

Just curious.
If WebPerformance is nt relevant..., why does sprocket exist?

Go use requirejs instead of sprockets.


BindTo can't be used to update a model that has existing data

Hiya,
When using model binding, the behavior of the ModuleExtensions.BindTo method only updates properties if they are null (or default for value types). My expectation was that I could update an existing model with the request data.
My scenario is that I'm constructing a rest service where it would be really useful to update an existing model with whatever json data has been sent to it. I would have thought this would be a very common scenario, much more common than only needing to update null/empty fields?
I'm not sure on the best approach for changing the code to support this scenario so I'll probably have a go at implementing a custom IBinder to get it working for now.

@bennidhamma I just ran into this. Seems like how it should work.


Update update-codegen

Use the not-so-new codegenlibrary to fix problems with gopath causing https://github.com/knative-sandbox/eventing-couchdb/pull/105/checks?check_run_id=2690916651 to fail

/lgtm
/approve


Fix UTC offset issue

Fixes #1101

This also relates to a comment on #1030

Looks good, any chance for a merge soon?

Hi there, any chance to merge this one ?

@linvi ?

Coming up. Sorry for that.

Tweetinvi 5.0.4 got released with the fix in it.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(engines<EMAIL_ADDRESS>chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

.travis.yml

chore(travis): remove node versions 10.14.2
chore(travis): add node versions 10.15.0

Codecov Report

Merging #415 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #415   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          41     41
=====================================
  Hits           41     41

Continue to review full report at Codecov.

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

Coverage remained the same at 98.148% when pulling c6c82c0ba8eb3f48260f5fb1ba0081521588d5b9 on template-sync-1 into ab981b220ea3222376cacf63e62f83f807f2a244 on master.

:tada: This PR is included in version 1.2.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


template and templateURL properties not working with blockUIConfig

as mentioned in here to add Image loader, I tried to use template and templateURL properties individually. not working after adding those properties.
although adding blockUIConfig.message =" custom loading msg" is working.
but
blockUIConfig.template = '

';
not working.

Try it:
blockUIConfig.template = '

   Please, stop clicking!

'
As you see, block with class="block-ui-container" is not need.
If you wouldn't need message then remove ng-binding and ng-class="$_blockUiMessageClass".
If you not need


Default excluded exceptions and explicit excluded exceptions are ignored

I have the same issue when using the default list of excluded exceptions and passing them explicitly: exceptions are still sent to Sentry.
Here's the list I'm using right now in a Rails app (after realising the default list did not work):
config.excluded_exceptions = [
  'ActionController::RoutingError',
  'Mongoid::Errors::DocumentNotFound'
]

This looks similar to #27, looks like it either never worked or that it's a regression.

That's strange, the default list has always worked for me. Can you give me some more details here?

I can't reproduce the problem anymore, closing.


accessibility: Focus displayed after drop down menu on firefox

Environment Details
Spartacus: epic/accessibility branch
Browser: Firefox
Device: mac
Happens on: http://dev-com-3.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD
Steps to Reproduce

Tab on the Header Category, Brands for eg.
Press TAB  again -> The focus is on something empty? We see it whenever there's a drop down menu.
Therefore, after tabbing on MyAccount, Brands, Digital Cameras etc

Note for devs: This is related to an empty <span> in the navigation, we (Kacper, Caine, Miguel) have agreed to tackle this when the cx-category-navigation gets refactored, as there are currently other issues to be fixed in there as well.

This is related to GH-6310

This problem is already addressed with the latest changes to a11y epic branch.


All kinds of patterns for instanceof (Java 14-21)

New NodeCategory PATTERN subtype of AST_NODE.
New NodeTypes UNNAMED_PATTERN (_), TYPE_PATTERN (subtype of LOCAL_DEC) and RECORD_PATTERN, all subtypes of PATTERN.
The TYPE_PATTERN is processed as its variable declaration inside, having all its relationships and properties (they may be final, have type and name).
new AST relation RECORD_PATTERN_TYPE to relate RECORD_PATTERN to its record AST_TYPE.
new AST relation COMPONENT_PATTERN to relate RECORD_PATTERN to each of its component patterns, with the integer property "patternIndex".
new AST relation INSTANCE_OF_PATTERN to relate INSTANCE_OF nodes to its pattern if any.
Update visitInstanceof method to scan the pattern if any.
Add three visit****Pattern methods to the ASTTypesVisitor to process and scan the three different patterns introduced.

CLosed by 83e3cb2c01d0030473a04614d7391ff53db5f698


docs: Document node field selector. Closes #2860

Checklist:

[X] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[X] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[X] I've signed the CLA.
[ ] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[X] My builds are green. Try syncing with master if they are not.
[X] My organization is added to USERS.md.

@simster7 done

Please run make lint to fix CI.

@alexec lint issue should be fixed


"Surround with" in TypeScript/JavaScript via snippets

A while back, @mjbvz filed https://github.com/microsoft/TypeScript/issues/18458 on the TypeScript side. The idea is that it would be great if we could easily transform.
// Hello
someFunc();
someOtherFunc();

into something like
if ([|condition|]) {
  // Hello
  someFunc();
  someOtherFunc();
}

as a refactoring. (The [|condition|] here represents a tab-stop where a user can start filling in condition as a placeholder).
The consensus there was that "surround with" is often simple enough that it could be provided through snippets. This won't always be precise, but it's good enough. Taking a look at the documentation, it seems like we can leverage $TM_SELECTED_TEXT in existing snippets to add this behavior.

I guess one thing that I'll add is that "insert snippet" is probably less used compared to the "lightbulb" UI.
I wonder if it makes sense to provide snippets that use $TM_SELECTED_TEXT as refactoring items in some way.


Several text improvements and bad translated words

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@TarikPonciano Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


The web call to retrieve ipv4 addresses now returns 61 entries, breaking security groups in AWS

Bitbucket now has 61 IPV4 addresses, which breaks the max # of IP's per security group.
╷
│ Error: Error authorizing security group rule type ingress: RulesPerSecurityGroupLimitExceeded: The maximum number of rules per security group has been reached.
│       status code: 400

@brunzefb This technically wasn't the responsibility of this module - as a consumer may be using something different than AWS SGs and had the option to chunk the list returned in their usage.
That said, I added two new outputs that will chunk the list of ip addresses returned by a configurable size. Making it a map versus a list makes it easier to use for_each (instead of count) to dynamically create the desired number of SGs. I updated the readme with an example.

Years ago, Atlassian's address list length also used to be this long.
My way to go with AWS security groups was to request enlarging the limits in my account.
Having https://www.terraform.io/language/functions/chunklist I do not see either why chunking should happen in this module. For sure it will come handy for a bunch of people, but defeats software design best practices.


Hardcoded label heritage=deckhouse breaks modules after PR#8696

https://github.com/deckhouse/deckhouse/pull/8696/ breaks all modules that use helm-lib. heritage=deckhouse is hardcoded here:
https://github.com/deckhouse/lib-helm/blob/main/charts/helm_lib/templates/_module_labels.tpl#L7
Modules use this template to set labels for all resources:
...
metadata:
  ...
    {{- include "helm_lib_module_labels" (list . (dict "app" "some-app")) | nindent 2 }}
spec:
  ...

After merging PR 8696 we got "forbidden" errors:
Warning  FailedScheduling  2s    default-scheduler  running PreBind plugin "VolumeBinding": persistentvolumeclaims "dvcr" is forbidden: Validat │
│ ingAdmissionPolicy 'label-objects.deckhouse.io' with binding 'heritage-label-objects.deckhouse.io' denied request: Creating an object with the `h │
│ eritage: deckhouse` label is forbidden

heritage=deckhouse is OK, fixed by allowing more service accounts in https://github.com/deckhouse/deckhouse/pull/8819


Add in driver types and rejig code to make it easier to extend

Added support for https://github.com/godotengine/godot/pull/52562
And just rejigged code a bit so it becomes less work to add more to this.

Thanks!


Multiple taxonomy terms returned when same term exists for multiple taxonomies

When multiple terms with same slugs exists in different taxonomies, e.g.
Taxonomy: Tags, Term: Pop
Taxonomy: Genres, Term: Pop
then for a collection entry where only one taxonomy is attached (e.g. Genres), both Terms (tags/pop and genres/pop) are returned on control panel listing (and who knows where else)
It's an issue in Taxonomies/TermQueryBuilder.php where and whereIn functions, because the taxonomy-wheres aren't applied in this case.

Taxonomy wheres are applied during get() and paginate(), they dont need to be added to where and whereIn.
I've run a quick test and I'm not able to replicate this locally - are you able to share your blueprints so I can try and reproduce it?

Here are the blueprints for the collection and taxonomies.
taxonomy_issue.zip
Try to create a taxonomy term with same slug in both taxonomies, and attach one of them to the collection entry.
You should see both terms in the collection listing

Yeah I can see this, though Im not convinced its a specific to eloquent bug as the taxonomy limitation is not being applied at the field level (that I can see).
If you mount the genres taxonomy on the collection (in the collection edit form) it then limits it to genres. So thats a work around to get past your issue.


Update feature for creating app cert

Proposed changes
This PR updates feature for creating app cert.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[ ] I have updated the change log (CHANGELOG.md)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Codecov Report

Merging #127 (d0d3217) into main (03dea75) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #127   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines         1474      1474
=========================================
  Hits          1474      1474

Continue to review full report at Codecov.

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


no-undef rule for component class methods

Is it possible detect undefined method in this case?
export default class Test extends Component {
  render() {
    return (
      <Example
        onClick={this.undefinedMethod}
      />
    );
  }
}

P. S. Sorry if the question has already been asked, I didn't find.

No, it's not possible to statically detect this without a type system. This is the domain of unit tests.


Uncaught Messages must be object

According to the examples in the readme file, I changed the default message, but when I did, it threw an error:
Uncaught Messages must be object.
Used the exact same code: V.setDefaultMessage('This is default message');

#6


Documentation for adding R kernels

The documentation for this page clearly explains how to create new Jupyter kernels for Python, but it does not cover doing so for R. Please consider extending this documentation to include how to add R kernels for Jupyter notebooks, if possible. Thank you.

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

ID: aecfa7a6-e520-308f-0b4c-289d8ad466ef
Version Independent ID: 18044427-f9ac-2e8b-69ae-6fd674ad3f77
Content: How to access a compute instance terminal in your workspace - Azure Machine Learning
Content Source: articles/machine-learning/how-to-access-terminal.md
Service: machine-learning
Sub-service: compute
GitHub Login: @AbeOmor
Microsoft Alias: osomorog

@gcoyle83
Thanks for your feedback! We will investigate and update as appropriate.

@gcoyle83
Thank you for bringing this to our attention.
I've delegated this to content author @sdgilley, who will review it and offer their insightful opinions.


Support loadbalancer for ingress-nginx

/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Hi, I've been following this tutorial
and have created manually a loadbalancer with two service pointing to both ports 80 and 443 with ssl-passthrough, because ingress-nginx should be terminating that.
Is it possible to allow the creation of a loadbalancer additionally to the already provisioned controlPlaneLoadBalancer?
Do I need a regular floating ip that ingress-nginx is able to pick that up or use something like metallb for multiple ones?
Thanks in advance!
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I'll definitely try out your tilt setup next
https://github.com/syself/cluster-api-provider-hetzner/blob/main/docs/developers/development.md#tilt-for-dev-in-caph
to be able to incorporate your changes sooner.
Environment:

cluster-api-provider-hetzner version: v1.1.1 (This new version works with provisioning too)
Kubernetes version: (use kubectl version) 1.23.3
OS (e.g. from /etc/os-release): fedora-35

@FischerLGLN Thank you for your issue. Only to clarify: You mean an additional loadbalancer to use ingress-nginx?
Right now the created loadbalancer is necessary because the ccm is not available at cluster creation time. It's also only there to serve the kube-apiserver and has only the control-plane nodes as a target. Therefore every additional loadbalancer to consume in a k8s service is managed by the cloud-controller-manager .

@batistein Thanks for the quick response. Yes, the first control plane loadbalancer forwards from 443 to 6443, therefore blocking port 443. That's why I need another one for ingress-nginx or let it's 443 service listen on another port.
Following your link, is this the reason for deciding on Cilium?

The CNI plugin you use needs to support this k8s native functionality (Cilium does it, I don't know about Calico & WeaveNet), so basically you use the Hetzner Cloud Networks as the underlying networking stack.

Calico with eBPF works fine too, at least if not using cloud-controller-manager.
helm repo add projectcalico https://projectcalico.docs.tigera.io/charts
helm install calico projectcalico/tigera-operator --version v3.22.0

If I use cloud-controller-manager in contrast to terraform, I get the benefit that changes in Hetzner Console also affect the underlying Kubernetes, right?

@FischerLGLN you could change the port to anything you want by changing in HetznerCluster spec.controlPlaneEndpoint.port to what you want. It's only important to know that you cannot update this port in a running cluster. Also FYI you could use the host for specifing a dns name which needs to point to the created loadbalancer.
There is no decision to use only cilium you could use whatever CNI you want. Cilium in my experience is only the best option at the moment as you could also run it kube-proxy free and use only eBPF and no iptables. But of course that's only my opinion.
To use or not to use cloud controller manager is nothing we could really decide as this is mandatory for running kubernetes on hcloud.

@batistein ah okay, so I would have to power down the node and make the service-changes then.
About the dns name, I did something like that on openstack with k3s using tls-san on the master-node pointing to my ports 80/443 loadbalancer.
Yes, Cilium has the best performance (with a higher load).
Okay great, I am closing this issue now.
Thank you for the technical exchange!

Hi, I tried it the next day and autoprovisioning of the loadbalancer for the ingress-nginx worked!
After installing ccm in private network mode, I had to annotate the nginx loadbalancer
to provide a cloud loadbalancer for example in Falkenstein.
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace --set 'controller.service.annotations.load-balancer\.hetzner\.cloud/location=fsn1'


Add test file location on timeout exceeded test failure

This is a problem when running a directory of multiple tests.
Test failures on assertion or exception give the correct file from the stack trace.
A timeout however leaves us grepping for the correct file:
  2) lophilo watch watching...:
     Error: timeout of 2000ms exceeded
      at Object.<anonymous> (/home/rngadam/local/node/lib/node_modules/mocha/lib/runnable.js:158:14)
      at Timer.list.ontimeout (timers.js:101:19

:+1:


Create caeci-ol entry

Website: https://caeci.de/

@lsiem Pull request merged. Thank you!
For the record: proof of the domain ownership - https://caeci.de/index.php?bereich=caeci&seite=kov


feat: [cheqd] add parse cmd to top accounts module with workers

Description
Closes: #XXXX

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

:exclamation: No coverage uploaded for pull request base (chains/cheqd/mainnet@2c75a27). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                   @@
##             chains/cheqd/mainnet     #511   +/-   ##
=======================================================
  Coverage                        ?   58.06%
=======================================================
  Files                           ?       20
  Lines                           ?     1495
  Branches                        ?        0
=======================================================
  Hits                            ?      868
  Misses                          ?      522
  Partials                        ?      105


launchType in ECS create_service

In moto/ecs/responses.py the function create_services doesn't pickup the launchType parameter.  As a result, the describe_service operation doesn't return the launchType passed during creation.

Thanks for raising this @borisreitman - marking it as an enhancement!

This should now be part of moto >= 1.3.16.dev189

This should now be part of moto >= 1.3.16.dev189


Milestones & feature

Hello,
I see that some cam/recorder-related features are being implemented. Can you shed some light on the new part or any other plans for the future?
BR!

yes indeed. i am working on a IP/rtsp camera dashboard which would have face detection and recognition capability using opencv.. hopefully the initial implementation should be out in the next 3 weeks.

Yes I know.. it is not related to image backups.. Ill move this outside in its own repo. same with FTP tab as well.


Improving communication of scaling settings to renderer implementation

This PR implements #64478
The problem in the renderer is that we never communicated the scaling option to the renderer, instead assumption are made based on the difference between target size and internal size.
This PR introduces an internally used "scaling off" setting and communicates the resulting scaling to the renderer. This also allows us to enhance the scaling system by offering more variation in the techniques.
This PR also makes scaling work on the mobile renderer, which was not previously supported.
Do note that the logic makes no assumption whether a renderer supports a given scaling option and leaves it up to the renderer to fall back.
So when FSR is supported and you're using the mobile renderer, or the needed Vulkan features are not supported, it will fall back to bilinear scaling.

Sorry @Calinou , my UI was lagging so I kept selecting the wrong dropdown :P

Thanks!


Scratch Card Application🧩

Description 📜
It's typical Scratch Card Application which everyone can see  in any payment applications mainly in Gpay, Paytm..which is made by HTML,CSS,JS. Where By cursor when we rub the card any random surprise will be appeared.
Fixes #847

Type of change 📝

[x] Add a new project

Domain of Contribution 📊

[x] Project using HTML, CSS & JS

Checklist ✅

[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
https://user-images.githubusercontent.com/77873383/164383920-29cb1887-0ef0-43d1-9afa-c5e1e70d82ef.mp4

@khushi-purwar  please check it

Bs scratch hoga paise bhi dalwa deta kamai hojati

@Mrjoy832 conflicts h jra dekh lena

@Mrjoy832 conflicts h jra dekh lena

Pr create ke time nehi rehta.. suddenly bud me kyese ho jata hain pata nehi

@Mrjoy832 conflicts h jra dekh lena

Pr create ke time nehi rehta.. suddenly bud me kyese ho jata hain pata nehi

bhut sari PR merge hone pr aajata hai

@Mrjoy832 conflicts h jra dekh lena

Pr create ke time nehi rehta.. suddenly bud me kyese ho jata hain pata nehi

bhut sari PR merge hone pr aajata hai

achaa

@Mrjoy832 conflicts h jra dekh lena

Pr create ke time nehi rehta.. suddenly bud me kyese ho jata hain pata nehi

bhut sari PR merge hone pr aajata hai

achaa

Resolved Conflicts

@Mrjoy832 conflicts h jra dekh lena

@gurjeetsinghvirdee Resolved Conflicts


ctrl-scroll font-sizing (feature request)

In 2015, dbeaver could not easily implement ctrl-scroll font sizing on top of the eclipse framework:
http://dbeaver.jkiss.org/forum/viewtopic.php?f=2&t=1826
Is this still the case in 2016? If so, how difficult would it be to tie the control-scroll-up and control-scroll-down events to the methods by which eclipse does indeed allow font-size changes (as a shortcut)?

Duplicate of #671
We going to migrate on Eclipse 4.6 in next couple of months.

This is not an exact duplicate of #671. #671 is closed because the scaling can be achieved via ctrl+ and ctrl-, which does indeed meet the either or nature of that feature request.
In my feature request, I'm specifically wanting to be able to achieve the font scaling via ctrl + mouse-scroll-wheel, which makes my request slightly different from #671.
Are there in upstream feature requests in Eclipse that may one day lead to this functionality? If not, where would you submit that?
Lastly, would it be possible for Dbeaver to implement this feature without the help of Eclipse, by listening for ctrl+scroll-wheel events and redirecting those events to the event handler for ctrl+ and ctrl-?

Can we please open this issue? In my previous post (over a year ago), I explained why this issue is NOT a duplicate of #671. At the top of this issue, you can see that I've been requesting this since 2015.

I suggest you open a new issue. I think your point is valid and this issue was closed by mistake, but sometimes comments on old closed issues will get lost.

Are we dragging the zoom feature into 2022? Is there a new ticket?


Problems with sort function

sort() uses Array.prototype.sort https://github.com/galkowskit/denofun/blob/55d9b59ff46523a5113ba99f6ecfb3f5334abb2a/lib/sort.ts#L12

It mutates the array
It does not support non-Array

It does not support function returning number other than -1, 0, 1 while Array.prototype.sort does, for example:

myArray.sort((a, b) => a - b)

That's clearly a non-intended behavior. :D
Good catch.

I think you should re-add "enhancement" tag:
I did say

It does not support function returning number other than -1, 0, 1 while Array.prototype.sort does

What I meant is you should allow callback function to return numbers other than -1, 0, and 1, so that the following one-liner works (it already works in vanilla JavaScript, but TypeScript definition does not allow it):
sort((a, b) => a - b, myArray)

Does sort function still mutates array

It shouldn't, no.


The meeting scheduler should include the GitHub id of the meeting requester in the GitHub issue

When the meeting scheduler creates an issue for a REST API review, it includes the name of the person requesting the review, e.g.:
Review Created By: Nicolas Rafalowski

But if I want to tag this person in the issue, e.g. to ask them to link a PR to the issue, I need to find their GitHub id. Rather than looking this up manually, it would be nice if the meeting scheduler could do that lookup and just include it in the initial issue description:
Review Created By: Nicolas Rafalowski @nrafalowski

Remind the stakeholders that any updates not made via the Scheduling tool will not be in sync with the central datas ource for the Release Plan.  For example, if someone updates the GitHub with links to the APIView vs adding the APIView links to the scheduled meeting, then the release plan will not know about it.  But if the updates are made to the meeting invite using the scheduling tool then the GitHub issue will be updated and the data source for the Release Plan will be updated.

This came up again in the Stewardship board where they decided to do offline reviews of the PRs, therefore they cancelled the meetings. The reason was posted in the issue but because the user's GH handled is not connected to the GH issue they were not notified and this created confusion.
Bumping the priority


[1.6/1.7] kubernetes ephemeral-storage limits not enforced with remote snapshotters

Description
When using a remote snapshotter (or any other snapshotter that doesn't place snapshots under the containerd root directory), ephemeral storage limits are not enforced by the kubelet. The container can blow past its limits and keep running indefinitely.
The kublet logs show errors like:
kubelet[3094]: E0419 15:57:23.046299    3094 cri_stats_provider.go:448] "Failed toget the info of the filesystem with mountpoint" err="failed to get device for dir \"/var/lib/containerd/io.containerd.snapshotter.v1.soci\": stat failed on /var/lib/containerd/io.containerd.snapshotter.v1.soci with error: no such file or directory" mountpoint="/var/lib/containerd/io.containerd.snapshotter.v1.soci"

and
kubelet[3094]: E0419 15:56:55.022396    3094 kubelet.go:1436]  "Image garbage collection failed multiple times in a row" err="invalid capacity 0 on image filesystem"

It looks like the kublet is unable to run ephemeral storage checks and image garbage collection because it's looking for image filesystem information in the wrong place.
Steps to reproduce the issue

Configure containerd to use a remote snapshotter in a k8s environment
Create a pod with an ephemeral storage limit:

resources:
  limits:
    ephemeral-storage: 20M
  requests:
    ephemeral-storage: 10M

Exec into the container and allocate more disk space than allowed

# fallocate -l 1G test1

Observe that the pod does not get evicted and the kubelet logs show errors above

Describe the results you received and expected
The pod should be evicted and the kubelet logs should not show erorrs
What version of containerd are you using?
containerd github.com/containerd/containerd 1.7.11 64b8a811b07ba6288238eefc14d898ee0b5b99ba
Any other relevant information
Related downstream issue https://github.com/awslabs/soci-snapshotter/issues/1093
Show configuration if it is related to CRI plugin.
$ cat /etc/containerd/config.toml
version = 2
root = "/var/lib/containerd"
state = "/run/containerd"

[grpc]
address = "/run/containerd/containerd.sock"

[proxy_plugins.soci]
type = "snapshot"
address = "/run/soci-snapshotter-grpc/soci-snapshotter-grpc.sock"

[plugins."io.containerd.grpc.v1.cri".containerd]
default_runtime_name = "runc"
discard_unpacked_layers = true
snapshotter = "soci"
# This line is required for containerd to send information about how to lazily load the image to the snapshotter
disable_snapshot_annotations = false

[plugins."io.containerd.grpc.v1.cri".registry]
config_path = "/etc/containerd/certs.d:/etc/docker/certs.d"

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
runtime_type = "io.containerd.runc.v2"

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
SystemdCgroup = true

[plugins."io.containerd.grpc.v1.cri".cni]
bin_dir = "/opt/cni/bin"
conf_dir = "/etc/cni/net.d"

Related to https://github.com/containerd/containerd/pull/9216

From my investigation, this is fixed in 2.0/main by:

https://github.com/containerd/containerd/pull/9152 which refactored the CRI plugin to get a map of snapshotter -> correct snapshotter root dir based on an exported root key on the snapshotter or the default hard coded path
https://github.com/containerd/containerd/pull/9253 which allows proxy plugins to have exports
https://github.com/containerd/containerd/pull/10073 which exports snapshotter root for the remaining snapshotters that didn't before

Rebasing  #9152 onto 1.6/1.7 would be tricky because there's a lot of structural change. https://github.com/containerd/containerd/pull/9216 was an attempt to fix this before the structural changes and would probably be a better starting point.

This is fixed in containerd 1.7.16.
1.6 backport is still pending.


Getting bad OCR on "Simple" Image.

Can you provide some tips on how to properly train SwiftOCR? Every image I feed it even after training with new fonts, SwiftOCR spits out garbage or an empty array. I feel like I'm not doing something properly.
These are not difficult images either, something as simple at 3 numbers it can't recognize. What am I doing wrong??
Here is an example image. I've trained the OCR-Network with all fonts.

It seems to skip letters and Tesseract can identify this 100%. What am I doing wrong?

By default SwiftOCR can only recognize uppercase letters and numbers. Your image contains lowercase letters and a special font. If you want to recognize images like these, I would suggest you to train SwiftOCR to recognize this font and lowercase characters.


[Bug]: Widget Image Bug

Component
Widget
Is this a regression?
None
Describe the bug
When using the widget component and not passing the img prop,

 is still rendered and takes up space. Please remove

 if the img prop is not passed.
To Reproduce
Render the Widget component with the prop type='default' and without the img prop,
Expected behavior
When using the Widget component with the prop type='default' and without the img prop, the

 should not be rendered.
Screenshots

Package version
2.12.0
Desktop
No response
Smartphone
No response
Exception or Error
No response
Additional context
No response

Hi @SargisKarapetyan. Please refine what is your use case. Do you need the Widget component without an image?

Using the type prop you can choose another Widget appearance where you can remove the img prop and get a more minimal widget UI.
https://github.com/softconstruct/gene-ui-components/assets/150047343/c9f068fa-df9d-460c-acdf-db2b1174d67f

I have to use the default type because the headerActions prop is only supported in the default type.

Got it thx. We will add the new prop withHeaderActions which will cover the compact type case also.

Thanks for the update!


Settings are not kept after closing the browser

Hi!
Settings (speed type and notification value) are not kept after closing the browser. Any new browser session causes them to reset.
Extension Version: 0.2.5

I guess it's working correctly now 🤔


ctapipe (called through lstchain) searches to download from an non-existing ctapipe-extra version

Hi,
Using lstchain v0.7.0 at la Palma to run the r0_to_dl1 stage I found the following error.
Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe/cccta-dataserver.in2p3.fr/data/ctapipe-extra/v0.3.3'

In the env, it is installed ctapipe-extra v0.3.1, but what puzzles me is the version of ctapipe-extra...
the full error is the following
Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe/cccta-dataserver.in2p3.fr/data/ctapipe-extra/v0.3.3'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe/cccta-dataserver.in2p3.fr/data/ctapipe-extra'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe/cccta-dataserver.in2p3.fr/data'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe/cccta-dataserver.in2p3.fr'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache/ctapipe'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer/.cache'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home/lstanalyzer'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/local/home'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/bin/lstchain_mc_r0_to_dl1", line 33, in <module>
    sys.exit(load_entry_point('lstchain', 'console_scripts', 'lstchain_mc_r0_to_dl1')())
  File "/fefs/aswg/software/virtual_env/ctasoft/cta-lstchain/lstchain/scripts/lstchain_mc_r0_to_dl1.py", line 69, in main
    custom_config=config,
  File "/fefs/aswg/software/virtual_env/ctasoft/cta-lstchain/lstchain/reco/r0_to_dl1.py", line 570, in r0_to_dl1
    focal = OpticsDescription.from_name(tel_name.split('_')[0]).equivalent_focal_length
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/site-packages/ctapipe/instrument/optics.py", line 98, in from_name
    table = get_table_dataset(optics_table, role="OpticsDescription.from_name")
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/site-packages/ctapipe/utils/datasets.py", line 232, in get_table_dataset
    return try_filetypes(table_name, role, table_types, **kwargs)
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/site-packages/ctapipe/utils/datasets.py", line 178, in try_filetypes
    cache_path = get_cache_path(os.path.join(DEFAULT_URL, filename))
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/site-packages/ctapipe/utils/download.py", line 75, in get_cache_path
    path.parent.mkdir(parents=True, exist_ok=True)
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1277, in mkdir
    self.parent.mkdir(parents=True, exist_ok=True)
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1277, in mkdir
    self.parent.mkdir(parents=True, exist_ok=True)
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1277, in mkdir
    self.parent.mkdir(parents=True, exist_ok=True)
  [Previous line repeated 5 more times]
  File "/fefs/aswg/software/virtual_env/anaconda3/envs/cta/lib/python3.7/pathlib.py", line 1273, in mkdir
    self._accessor.mkdir(self, mode)
PermissionError: [Errno 13] Permission denied: '/local'

ctapipe-extra is no longer used in ctapipe-0.10.x - instead ctapipe download data to a cache directory from the ctapipe-extra directory on the data server, so no ctapipe-extra package should be installed.   But this sounds like a problem with the caching mechanism.  Try removing ~/.local/cache/ctapipe just to be sure, and try again (and also uninstall ctapipe-extra)

lstchain uses get_dataset_path at several places also important for actually running analysis, these should just be removed.

Agreed that you should not use this in lstchain.  You can in principle still use get_dataset_path (even though it is really intended for getting test files and default configurations), as long as you set CTAPIPE_SVC_PATH, which can contain any number of directories in which to search - if that is set, it looks first there, before trying to download from the server.   But the intention of the datasets module is access to testing datasets, not real data.
If we need some real-data search/management functionality, we could open an issue to add that, but that is probably out of scope for ctapipe, as it really depends on the computing infrastructure on which you are runnning. The script that calls ctapipe should handle data management and just pass a valid pathname to the tool.

@kosack should we switch to downloading from the ctapipe-testdata directory instead of a directory called ctapipe-extra ?
That would make it clearer that this is not related to ctapipe-extra anymore.
I will also go ahead and archive ctapipe-extra

Closing this.


More system data in analytics

It would be good to be able to send information about the memory used, battery level, type of network connection.
Now there is not enough information about what is happening with the system, during a crash or event.

Thanks for the feedback and suggestion, We added this as a feature request.


Set: Remove obsolete whitespace from documentation

Raven
Number of Findings: 0

lgtm

+1

RM +1 manually reviewed dependencies.


Calculated Values tool: When calculating reaction, there is different behavior in different modes

Steps to Reproduce

Launch Ketcher
Open reaction_2.zip
Select reaction components as:
A + B;
B -> C;
A and D;
B -> C + D.
Click Calculated Values

Expected behavior
Information in the Calculated Values window displayed identical in both modes
Actual behavior
Standalone mode:
brackets and signs of reactions are displayed in the Calculated Values window

Remote mode:

Desktop

OS: W10

Related issue: https://github.com/epam/Indigo/issues/465

fixed, tested v.2.4


Not fully Closing

Are you aware the process isn't closing when you close the GUI window?

Thank you for bringing this bug to my attention! I will have a fix for it as soon as possible (trying to wait a bit for Blub to release an updated version of his miner). :)


packaging: remove .orig files

unfortunately there is no option to patch that prevents this
it seems that patch creates an .orig file in some cases even
when it was successful, e.g. when the patch has an offset
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

lgtm


Support block and macro processors with no arg constructors if name i…

…s defined via an annotation
As discussed in #196 this PR brings support for macro and block processors that only provide a no arg constructor if the name is defined via an annotation.
All processor proxies now use a more generic way to instantiate the processor by using the constructor with the most matching arguments, so this could also be used if we would support passing a configuration at processor registration time.
(JavaExtensionRegistry does not support passing a config yet, but I think Asciidoctor itself supports that.)

Force pushed to fix usage of Java8 only method Constructor.getParameterCount().

:+1:


mvn build fails due to test failures

Downloaded the repo, attempted to mvn clean install
It fails, looking at the first error
12:27:15.325 [main] WARN  o.s.c.s.GenericApplicationContext - Exception encountered during context initialization - cancelling refresh attempt
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cratePersistentEntitySchemaManager' defined in class org.springframework.data.crate.repository.support.SimpleCrateRepositoryIntegrationTest$CrateContextConfig: Invocation of init method failed; nested exception is org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: []
I didn't see any information in the readme about having elasticsearch running. Or building this on a machine where create is installed. Is that the case to make build work?

Also tried building this on a machine with latest build of Crate.io and it's failing another test
16:57:54.765 [main] DEBUG o.s.t.c.s.DirtiesContextTestExecutionListener - After test method: context [DefaultTestContext@a53bb6f testClass = SimpleCrateRepositoryIntegrationTest, testInstance = org.springframework.data.crate.repository.support.SimpleCrateRepositoryIntegrationTest@5e63cad, testMethod = shouldDelete@SimpleCrateRepositoryIntegrationTest, testException = org.springframework.dao.DataAccessResourceFailureException: [person][1] null; nested exception is SQLActionException{errorCode=5000, status=INTERNAL_SERVER_ERROR, stackTrace='org.elasticsearch.action.NoShardAvailableActionException: [person][1] null

Looking at the log of crate.log
I see
[2016-03-01 16:57:55,197][DEBUG][action.admin.indices.delete] [ip-10-0-0-11] [person] failed to delete indices
org.elasticsearch.indices.IndexMissingException: [person] missing
at org.elasticsearch.cluster.metadata.MetaDataDeleteIndexService$2.execute(MetaDataDeleteIndexService.java:157)
at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:374)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:204)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:167)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

            Thread.sleep(500);
            repository.refreshTable();
            repository.delete(hasnain);

Adding sleep + refresh table cures the issue.
Although complexid tests fail and above is a hack of a larger issue of creating/deleting indexes in rapid succession causes some unpredictable results.

Hi,
The project has integration tests so you will need to have an instance if crate running locally.
Kindly have a look at the following issue as your exceptions are related to it
https://github.com/crate/crate/issues/1453
As the issue suggested, we added the following configuration in our test calss
@Table(...., numberOfReplicas="0")
Do keep this is mind that the project was developed with an old version of Crate. The behaviour might have changed in newer versions of Crate.
Kind Regards.

Great thank you, also the byComplexId  tests are failing as well. It's unable to cast from provided ID into String.

Hi,
The issue is with Crate DB. I have opened an issue with them
https://github.com/crate/crate/issues/3320
You can see from the staktrace that no spring data crate package is listed :)
Kind Regards

You the man!


Using google tiles in the application

Is it legal to use google tiles without using google api?
Refer to
https://cloud.google.com/maps-platform/terms/?hl=en#10-license-restrictions

Hello @prateek99 , thank you for inquiring about this. We have reached out to Google, and they have verified that everything is in order.
Please feel free to let us know if you ever have any questions/feedback!
Best,
Teresa Schofield
Junior Product Specialist
Global Forest Watch


no able to perform a dnf update in a fedora container

It is not possible to do an update in a fedora container
docker run -td --name test fedora sh
docker exec test sh -c "dnf -y update"
BDB0126 mmap: Invalid argument
Configurations:
cc-runtime  : 3.0.10
commit   : 3d402d1
OCI specs: 1.0.0-dev
Docker 1.17.09

I suspect this is the mmap issue that is iirc related to 9p.
Can you check if the current '9p tmpfs' workaround fixes it? Hmm, that is if dnf honours TMPDIR and the like.
So, inside the container set export TMPDIR=/dev/shm to point at a ramfs fs, and then try again.
Failing that - an strace of the failing dnf could help further diagnosis.

This does indeed look like the old :chestnut: https://github.com/01org/cc-oci-runtime/issues/669.

(See https://github.com/01org/cc-oci-runtime/issues/669#issuecomment-281280979 for the ramfs workaround).

this issue was fixed in qemu 2.10  :)

@jodh-intel - that 'old' fix will no longer work as we have tightened the privs in the CC containers, so you cannot do the mount from inside the container any more :-)  The 'new' fix (workaround) is to try and point the apps to use an existing tmpfs in the container for their tmp space:
export TMPDIR=/dev/shm; <your command here>

@devimc - so, that begs the question - do you know when that will land into a version of CC ?

Hi @grahamwhaley - I think this should be captured atleast in the wiki, but ideally in https://github.com/clearcontainers/runtime/blob/master/docs/limitations.md.


Showing "+" (extra asterisks appears)

https://docs.microsoft.com/ja-jp/microsoftteams/let-your-teams-users-communicate-with-other-people

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: 59900927-5e5f-77a4-04be-e05a91330fca
Version Independent ID: 1e4d6b87-f57c-fa45-1630-3c32b821d93c
Content: 他の組織の Teams ユーザーとの通信
Content Source: Teams/let-your-teams-users-communicate-with-other-people.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@officedocsbot assign @officeglobal

@officeglobal could you please take a look at this? Thanks!

Working on a fix

@hyoshioka0128 article has been HumanTranslated. The issue is fixed

@hyoshioka0128 Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close


undefined symbol: syspower_show_windows

Installed via the AUR, syspower
On launch prints those warnings:
Unable to open file: /home/alex/.config/sys64/power/config.conf
Cannot load symbols: /usr/lib/libsyspower.so: undefined symbol: syspower_show_windows

Compilation was successful, however.

Oh whoops, forgot to clean that up
My bad!

Oh whoops, forgot to clean that up My bad!

It's all good, don't worry about it!
We all make mistakes :)

Fixed, can you test now?

Fixed, can you test now?

Yep, works now!
Don't forget to increment the pkgrel var in the PKGBUILD!

Awesome!
As for the aur pkgbuild
I never increment those
I might add the commit date to them like some packages do though (Automatically grab commit date on build)


[rviz_rendering] Cleanup of code with help of the linters

I needed to do this now so I could build on it with upcoming pull requests.
I'm going to merge this without waiting on reviews since it's just what the linter said to do and removing files we had already agreed to remove.

Btw, the render_widget.* files are no longer needed because they were ported from rviz's code that integrated with a QWidget. The code we have for integrating with a QWindow (new recommendation) is completely new, so the QWidget code is no longer needed.


Check (shared) file exists

Doing a check if the shared file already exists.
A touch could result in a 'Permission denied' causing the deploy to stop.

I think in this case deploy should stop?

I think in this case deploy should stop?

@antonmedv
Why? The shared file does not have to be writable by the person (or its group) performing the deploy is it? This is the case in our situation. Also, touching a file that already exists only changes the modification time. That is where our deploy fails now.

@antonmedv
Why? The shared file does not have to be writable by the person (or its group) performing the deploy is it? This is the case in our situation. Also, touching a file that already exists only changes the modification time. That is where our deploy fails now.

Got it.

Got it.

@antonmedv do you want/need anything to merge this? A test or something?

Nice! Thanks for pr and merge hustle.


Sample job got failed : Python no such file or directory

[emr-cli]: Waiting for job to complete...
[emr-cli]: Job state is now: PENDING
[emr-cli]: Job state is now: SCHEDULED
[emr-cli]: Job state is now: RUNNING
[emr-cli]: Job state is now: FAILED
[emr-cli]: EMR Serverless job failed: Job failed, please check complete logs in configured logging destination. ExitCode: 1. Last few exceptions: Caused by: java.io.IOException: error=2, No such file or directory
Exception in thread "main" java.io.IOException: Cannot run program "./environment/bin/python": error=2, No such file or directory...

Hi there, thanks for trying the EMR CLI.
It looks like your job required a virtual environment, but it didn't get packaged or uploaded properly.
Please try the following.

Run emr run with the --build flag

Can you provide some more details on your environment and command? Did you use the emr init command or do you have a pre-existing project?

Full commands used to package, deploy, and/or run the sample job (with sensitive info redacted)
Layout of your Python project - Is it a poetry project, project with multiple Python files? Any dependencies?

Thanks!

Just wanted to check back in here? Will close this if I don't hear back. :)


Add build setting to xcodebuild command ...

…so projects can detect snaphot during build via $FASTLANE_SNAPSHOT.
Runtime detection is already provided by the launch_argument in the helper.
https://github.com/fastlane/fastlane/issues/4356

Hey @Ashton-W, thanks for the pull request, unfortunately danger has an issue, could you rebase from master and update the PR? 👍

This looks great btw, thanks for the pull request

Hey @Ashton-W! I recreated you PR here https://github.com/fastlane/fastlane/pull/5051 and rebased it on master so we can merge 🚀 !


refactor(kit)!: InputFiles refactor API and get rid of built-in rejections

Closes #

input-files.spec.ts

something is wrong with the 1st example
https://github.com/taiga-family/taiga-ui/assets/46284632/dcf83fc7-ca22-4d1d-ac5d-3cc86af50c96


CUDA error cudaErrorInvalidConfiguration:invalid configuration argument

RuntimeError: Error in backward pass execution: Non-zero status code returned while running BiasGeluGrad_dX node. Name:'BiasGelu_token_112_Grad/BiasGeluGrad_dX_0' Status Message: CUDA error cudaErrorInvalidConfiguration:invalid configuration argument
when I use a big tensor like (128, 3, 224, 224)，it will cause some errors.
If I change the tensor dimension to (16, 3, 224, 224), it works. So why?

Thanks for reporting it, working on a fix now.

@baijumeswani  please kindly help close this issue (seems I don't have permission for this one).


Cannot cancel buy orders

I am trying to change my buy order price but Oasis is not letting me cancel my orders.

could you please provide me with some additional informations:

What client are you using (name and version please)?
What server are you connected (If Metamask, Ethereum Mainnet ? )


ISPN-12514 ProtocolVersion in HotRod must be 3.1

https://issues.redhat.com/browse/ISPN-12514

Integrated into master, thanks @diegolovison !


net/http/httputil: ReverseProxy copyHeader() appends to pre-existing headers instead of overwriting them from target service's response.

I used the NewSingleHostReverseProxy constructor to generate a *ReverseProxy to a target service, and then called ServeHTTP from an http handler func.
What did you see happen?
Header values for keys that pre-existed on the http.ResponseWriter passed to *ReverseProxy.ServeHTTP — for example, "Vary" and "Access-Control-Allow-Origin" — are duplicated in the final response due to the call to copyHeader(rw.Header(), res.Header), which appends to existing headers because it uses dst.Add(k, v) as opposed to dst.Set(k, v).
What did you expect to see?
I expected to see the target service's response headers copied directly to the final response, instead of appended to the pre-existing headers. If this is the correct intended behavior, then this can be fixed by changing dst.Add(k, v) in copyHeader() to dst.Set(k, v).

Duplicate of #50730

Sorry I didn't check the closed issues, thanks!


Fixed #33161 -- Do not ignore transaction durability errors within TestCase

Ticket: https://code.djangoproject.com/ticket/33161

Did you see #14922 ?

@adamchainz Yep! Just saw it and I feel like it is a more straightforward solution to this specific ticket.
Having the atomic_blocks stack would make sense if I would also change the way connection.in_atomic_block and connection.savepoint_ids work, but maybe it feels like an unnecessary undertaking.

Let's close this one and go with your PR instead


Hiding all MediaStreaming

Hiding all MediaStreaming and fixing its tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.CallAutomation


Issue 82: Added xlsx-renderer-cli

TODO:

[x] readme
[x] badges

closes #82 #94

@Metastasis could I please you for review?

@Siemienik ok, I will check it soon

@Metastasis, I did requested fix, could I please you to do review again?

@Siemienik Yes, thanks, I reviewed changes and I think marked PR as approved

@Metastasis Thank you for review :)


Easier dev setup

Heya! I took a stab at simplifying the setup of a development environment by encapsulating a lot of the stuff everyone has to repeat every time. Also added a README which you hopefully find agreeable. :)

setup.py already at project


Fix 32-bit test failures and test workspace on a 32-bit target on CI

Currently, on 32-bit systems, 19 to 22 tests fail because they assert that data structures have exactly the size they are known to have on 64-bit systems, which the test-32bit job does not catch because it only runs tests in gix-hashtable.
At one time, test-32bit had included an i686 job, but this was removed because of problems related to glibc versioning in the image used by cross. This brings that back, splits it out to own job--naming the new job test-32bit and renaming the cross-using armv7 job test-32bit-cross--and solves that problem for it by using a 32-bit Debian container for the job with the container key rather than using cross.
This reveals a few bugs, which this PR includes fixes or partial workarounds for.
Data structure size assertions
As noted above, 22 tests of data structure size have been failing on 32-bit GNU/Linux systems. (Only 19 of the 22 have been failing on 32-bit Windows.) Of these:

18 are mainly to ensure data structures do not grow larger than they have been, but there is some value in immediately finding out if they shrink as well, as described in 77c3c59. So, as described in fc13fc3, the assertions continue to do exact equality comparisons on 64-bit targets, but do <= comparisons on 32-bit targets.
4 guard against unanticipated changes to internal data representations, such that it seems like it may be equally useful to find out if they change in size on any target. So for those, exact equality comparisons continue to be done on all targets, but separate expected values are used for 64-bit and 32-bit targets, as detailed in daf9990.

Various other assertions of data structure size already do <= comparisons. I think most of those should be changed to the approach in (1)--and perhaps some even to (2)--but that change is not necessary to get tests to run on CI or anywhere, so I haven't included it in this PR.
Even as used in this PR, it is not immediately obvious that the approach in (1) makes sense, because it is in principle possible for different 64-bit targets to have differently sized data structures. This does happen on 32-bit targets--sometimes even for the same architecture--which is why three fewer of these tests fail on 32-bit Windows systems than 32-bit GNU/Linux. However, the sizes have all been the same on four separate 64-bit architectures tested:

x86-64 (amd64) - most test runs, including on CI (except macOS)
AArch64 (arm64) - macOS test runs on CI, and Windows 11 arm64
riscv64 - tested while working on http://rust-lang/libz-sys#218, I don't recall any of these tests failing
s390x - tested recently as part of research for this, with the idea that it might reveal a problem due to being bigendian - although some other tests fail, all the size tests pass

So at least for now I think it's reasonable to continue viewing our data structures as generally not varying in size across 64-bit targets.
Coupling to gitoxide's own repo
The gitoxide test suite currently depends, I believe mostly unintentionally, on the gitoxide repository itself existing and having various properties. Various fixture scripts and tests fail if there is no outer repository; or if the outer repository is blocked by configured ceiling directories; or if the tests are run from a linked worktree, rather than its main worktree; or if git operations cannot be performed on the outer repository due to safe.directory errors.
As far as I know, the only coupling to the gitoxide repository that is firmly intended in the design of the test suite is the use of .gitignore information to determine which fixtures are allowed to generate archives. A few uses of the outer repository seem intentional, but not essential to the design, and they can be fixed using a fixture with nested repositories, decoupling completely from gitoxide's own repository. More often, I think this coupling is entirely unintended.
I haven't documented this in full detail yet, and maybe it should have an issue, but see this gist and this repo. (The latter is a full repo rather than a gist to facilitate visual diff via the web editor, and because it benefits from a non-flat directory structure.)
Fortunately, for this 32-bit Debian container on CI, only one case of this had to be addressed, largely because GIX_TEST_IGNORE_ARCHIVES is not being used. git fetch-pack commands that were run to produce baseline output--in a fixture script that run even without GIX_TEST_IGNORE_ARCHIVES--were actually operations on the gitoxide repository itself.
Because of the way ownership works with actions/checkout in jobs that use a container key, unless customized or chowned, the owner and process UIDs differ. This could be worked around with chown (47f3819), but after verifying that works I instead fixed the bug in the fixture script by introducing a temporary nesting repository for fetch-pack to operate on (d07c32d).
Tests of "GitInstallation" when it is empty
Independent of the above, six tests failed in the container due to weaknesses of tests I introduced in #1567: when there is no identifiable "GitInstallation" scope, some of the tests of "GitInstallation" scope detection fail. This was an intentional decision at the time, but less sound than I had thought.
My thinking in #1567 had been that it will be natural to fix this at the same time as we exclude the global scope from ever being detected as "GitIntallation" (or if for some reason that is not to be done then the reason it shouldn't be done would inform how the tests should be improved). However, I had not anticipated that there were already prominent cases where these tests regularly fail even though there is no bug in the code under test. One such case is running the tests in a mostly minimal container that has git.
See 178cf25 for details. That commit works around the problem by defining a variable in the system scope in the container. It also describes the current situation in detail and describes the significance of likely future developments that would improve or worsen the situation.
This bug is not related to the container being 32-bit, just to it not containing system or global configuration (and not being macOS with Apple Git, thus not having a high unknown scope) as is typical of containers.
Duplicated tests
Some data structure size tests were duplicated within their package, as described in #1685. Code duplication would be increased by the changes here, since the tests use more code (see the note at the bottom of fc13fc3). The deduplication resolving #1685 is therefore also included in this PR (dc0a73a).

Thank you - not only does that save time, but it's likely these started out with equality comparisons, but ended up a bit more flexible due to frequent failures on various platforms.

Because of the way sizes can shrink and later grow again, as described in 77c3c59, I think it's probably worthwhile to bring back equality comparisons for them on 64-bit systems, while still using <= on 32-bit systems, as size_ok helps do. (Whether size_ok is the best way to express this, moving forward, I'm not sure. Maybe an assertion macro should be introduced for this?) However, that only applies if the size is expected to be the same on different 64-bit targets.

git fetch-pack commands that were run to produce baseline output--in a fixture script that run even without GIX_TEST_IGNORE_ARCHIVES--were actually operations on the gitoxide repository itself.

That's probably also a great example for how easily one could accidentally create a huge tar file, after fetching the parent repository without noticing it happened. Even though in this case it appears git fetch-pack was called merely to invoke --diag-url, which is probably mostly unrelated.

Although I can imagine that happening, the more likely kind of problem, with the kinds of coupling I've observed here, would be fetching something into the gitoxide repository. (That's what the code changed here had, notionally, done; but, as you mention, nothing was actually ever fetched.) As far as I know, the outer gitoxide repository is never added as a remote of a test repository.

Something I found generally interesting was that 32bit data structures were only about 20% smaller, not at all close to 50% like one would intuitively expect.

Although it may be unintuitive, it seems that, at least in the data structures in gitoxide that have tests with size assertions, the "lower level" a data structure is, the less it is likely to shrink going from 64-bit to 32-bit targets:

Data structures that contain lots of handles to data elsewhere, such as Vec objects, will shrink more, since such objects consists of pointers and sizes that are meant to participate in arithmetic with the pointers.
In contrast, data structures that contain a lot of scalar values only decrease in size if some of the data types vary in size across architectures, and for numbers, fixed-size data types, e.g. u32, u64, seem more common.

But there may also be correlation between a data structure holding values of fixed size and having its size considered important enough to be asserted in a test.

Although it may be unintuitive, it seems that, at least in the data structures in gitoxide that have tests with size assertions, the "lower level" a data structure is, the less it is likely to shrink going from 64-bit to 32-bit targets:

Thanks for elaborating! Now that I read it it makes perfect sense and I am feeling very naive for having that intuition, without even realising (or caring to think about) the most obvious possible reason for this 🤦♂.

I should mention--so as to avoid confusion for anyone looking at this later--that in most cases I have not checked the reason for specific data structure size differences. Sometimes the difference is small or zero because the data structure consists mostly or entirely of scalar types whose sizes are not architecture dependent. And it may be that this account for the entire effect.
But another possible contributing factor is packing: some data structures may have less efficient layouts on 32-bit architectures, with holes in some places, to satisfy alignment requirements, to satisfy an ABI convention, or because the Rust compiler decides to lay them out that way. I found this to be why some data structures are different sizes on different 32-bit targets, though I didn't spend time examining all their layouts.


Update passport to 0.6.0

Also applied a change required by this update.
Fixes https://github.com/advisories/GHSA-v923-w3x8-wh69

@Poslovitch FYI, this caused a small regression with welcome messages, which I just fixed in 358e1073132ff34ea88dc2427b8f14a31ad17b5b - I think a similar root cause as with the code you fixed as part of this PR. There might be other less obvious regressions - will keep an eye out.

Good catch @eloquence. I'll definitely keep an eye out.