🚧 Do not merge 🚧 Isolate flaky tests

The flakes for the find-and-replace package have been bugging me recently. They aren't timeouts, so it should be an issue with the test or package logic. I couldn't reproduce them locally or on the package repo (https://github.com/atom/find-and-replace/pull/1134), so I'm testing the CI directly with this PR to try and reproduce it and then work out why it fails.

It seems the project state is incorrect even in the closing of the core:move-to-top and core:move-to-bottom beforeEach function. There seems to be an assumed state with the fixtures/project path open as the atom.project paths; perhaps this project path is incorrect from another test. The results-view-spec specs only set the project paths to fixtures/project, but I've also only been able to reproduce the problem so far with all spec files enabled.

Got a local failure, yay. Only seems to fail on macOS; it's never failed on Linux for me. The mac is much older though, so it could just be because it's slower. Linux doesn't seem to open anything, whereas the mac tests open an Atom instance (one appears in the dock).
Noticed that when it fails the tests sometimes log Specs will fail because the Dev Tools have focus. To fix this close the Dev Tools or click the spec runner., which is interesting because I didn't think the dev tools would open in CI (or in the local tests).

The dev tools are definitely being opened as well, and was the cause of some of the failures. This is meant to happen on an uncaught exception, but I've had it happen apparently randomly before, so that will need looking into as well.

Preventing dev tools from opening appears to fix most of the errors. I haven't tried it without the render patch though, so I don't know if the two combined are important.
Applying this as a patch may lower flakes in the short term, but working out what is causing them to open would be better long term.
Of 100 runs, 5 errored. I did not observe any failures in results-view-spec. All were in the project view ripgrep specs. These errors were all similar to
2020-09-20T06:56:25.9056460Z ProjectFindView (ripgrep=true)
2020-09-20T06:56:25.9056800Z   finding
2020-09-20T06:56:25.9057160Z     when the find string contains an escaped char
2020-09-20T06:56:25.9057600Z       when regex search is disabled
2020-09-20T06:56:25.9058910Z         it ProjectFindView (ripgrep=true) finding when the find string contains an escaped char when regex search is disabled doesn't insert a escaped char if there are multiple backslashs in front of the char
2020-09-20T06:56:25.9059740Z           Expected object with length 0 to have length 1
2020-09-20T06:56:25.9060780Z             at jasmine.Spec.<anonymous> (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:345:84)
2020-09-20T06:56:25.9061450Z             at Generator.next (<anonymous>)
2020-09-20T06:56:25.9062420Z             at step (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:3:273)

and
2020-09-20T06:37:36.6222490Z ProjectFindView (ripgrep=true)
2020-09-20T06:37:36.6222830Z   finding
2020-09-20T06:37:36.6223200Z     when core:confirm is triggered
2020-09-20T06:37:36.6223580Z       when results exist
2020-09-20T06:37:36.6224750Z         it ProjectFindView (ripgrep=true) finding when core:confirm is triggered when results exist doesn't update the results list when a buffer outside the project changes
2020-09-20T06:37:36.6225530Z           Expected object with length 0 to have length 13
2020-09-20T06:37:36.6226580Z             at jasmine.Spec.<anonymous> (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:854:84)
2020-09-20T06:37:36.6227250Z             at Generator.next (<anonymous>)
2020-09-20T06:37:36.6228220Z             at step (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:3:273)
2020-09-20T06:37:36.6229420Z           Expected undefined to have class 'selected'.
2020-09-20T06:37:36.6231220Z             at jasmine.Spec.<anonymous> (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:859:94)
2020-09-20T06:37:36.6231930Z             at Generator.next (<anonymous>)
2020-09-20T06:37:36.6232940Z             at step (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:3:273)
2020-09-20T06:37:36.6234070Z           Expected undefined to have class 'selected'.
2020-09-20T06:37:36.6235130Z             at jasmine.Spec.<anonymous> (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:865:94)
2020-09-20T06:37:36.6235770Z             at Generator.next (<anonymous>)
2020-09-20T06:37:36.6236710Z             at step (/Users/runner/work/1/s/packages/find-and-replace/spec/project-find-view-spec.js:3:273)

@Aerijo We could try the dev tools patch here on find and replace and then observe for a couple of runs. If the failure still occurs we can include the list view patch

I've put in atom/find-and-replace#1137 with the devtools patch.

Closing in favour of https://github.com/atom/find-and-replace/pull/1137

Closing in favour of https://github.com/atom/find-and-replace/pull/1137


How to use DLA-34 to be the backbone of  CenterNet?

Model/Dataset/Scheduler description
Most original backbone of CenterNet is ResNet18. However, I don't know how to change and use the DLA34 to be the backbone of CenterNet. I am looking forward to some structural suggestions, thanks!
Open source status

[ ] The model implementation is available
[ ] The model weights are available.

Provide useful links for the implementation
No response

The quotations about 2d detection could be posed on MMDet.

We have provided an implementation of DLA34 in our repo, you can refer to https://github.com/open-mmlab/mmdetection3d/blob/master/configs/base/models/smoke.py to see how to use it.

We have provided an implementation of DLA34 in our repo, you can refer to https://github.com/open-mmlab/mmdetection3d/blob/master/configs/base/models/smoke.py to see how to use it.

thanks a lot, it is work


Implement log(cosh()) loss function

log-cosh is a doubly differential alternative to the huber loss. A naive implementation is prone to overflow (since cosh has an e^x term), so I think it'd be a useful addition to the library. Plus, it's implemented in other libraries, such as TensorFlow.
If this sounds like a relevant addition, I'd be happy to contribute it!

This would be a great contribution! Looking forward to it!


Policy category - Add GL Code

From the design doc:
settings/workspaces/{policyID}/categories/{categoryName}/gl-code -> CategoryGLCodePage
- Parameter: categoryName, the name of the category for which we are updating the GL code.
- Calls UpdateCategoryGLCode
policyID
categoryName - the name of the category for which we are updating the GL code.
glCode - the updated GL code for the category.
The pendingAction for the OfflineWithFeedback component will be policyCategory.pendingFields?.glCode

@rushatgabhane will be working on this

PR here: https://github.com/Expensify/App/pull/43149

monitoring PR - https://github.com/Expensify/App/pull/43149

Update for Melvin - monitoring PR - https://github.com/Expensify/App/pull/43149

PR in staging - https://github.com/Expensify/App/pull/43149
@Gonals do we need to be concerned about this comment - https://github.com/Expensify/App/issues/44255#issuecomment-2229783919

@Christinadobrzyn no, that is part of plan.
We are replacing it with Upgrade flow

I don't think we need a regression test since this is a new feature, correct @rushatgabhane?
Payouts due:

[ ] Contributor+: $250 @rushatgabhane (paid in NewDot)

Payment day is here - payment summary - https://github.com/Expensify/App/issues/44255#issuecomment-2248619739
I don't think we need a regression test for this since it's a new feature but let me know @rushatgabhane!

@Christinadobrzyn this will need a regression steps because we want to avoid future bugs.

Please assign @shubham1206agra as they were the C+ for the PR.
I was the PR author

$250 approved for @rushatgabhane

Just checking on this - https://github.com/Expensify/App/issues/44255#issuecomment-2251824144
@shubham1206agra should you be paid for this as well? If yes, are you paid through Upwork or NewDot?
Can you create a regression test?

Thanks @shubham1206agra - here's the upwork offer - https://www.upwork.com/nx/wm/offer/103283703
Are you happy with these as the regression test steps:

Go to a collect policy
Go to category page
Select any category
Verify that you see GL Code
Verify that you can set a GL Code in the text input.
Verify that clicking save sets the GL Code and navigates you back

Regression test here - https://github.com/Expensify/Expensify/issues/416064
Paid @shubham1206agra in Upwork. Payment summary here - https://github.com/Expensify/App/issues/44255#issuecomment-2248619739
Closing!


Weird id of game name in CreateGameScreen

Contains
The id of the game name UIText was worldName for some reason. Maybe it was used for worlds before or something. I've changed that to gameName. Just a little something I discovered while dealing with the create game flow.
How to test
Run the game. You can even do a search for worldName with the Match Case option ticked in IntelliJ. There should be 0 results.

Hooray Jenkins reported success with all tests good!

Thanks for the tweak! :-)


Install Argo on Minikube failing with permission issue

Argo install on Minikube failing

argo cluster ops> argocluster install-argo-only --cluster-name minikube --kubeconfig /tmp/ax_kube/argo_cluster_inline-minikube.conf --cloud-provider minikube
2017-10-19T19:52:41 INFO ax.cluster_management.argo_cluster_manager MainThread: Installing Argo platform ...
2017-10-19T19:52:41 INFO ax.cluster_management.argo_cluster_manager MainThread: Installing s3 proxy ...
namespace "axs3" created
persistentvolumeclaim "s3proxy-pvc" created
service "s3proxy" created
deployment "s3proxy-deployment" created
2017-10-19T19:52:43 INFO ax.cluster_management.argo_cluster_manager MainThread: Creating s3 bucket using location: http://<IP_ADDRESS>:31791/argo
2017-10-19T19:52:50 INFO ax.cluster_management.argo_cluster_manager MainThread: Creating s3 bucket using location: http://<IP_ADDRESS>:31791/argo
2017-10-19T19:53:02 INFO ax.cluster_management.argo_cluster_manager MainThread: Creating s3 bucket using location: http://<IP_ADDRESS>:31791/argo
2017-10-19T19:53:26 INFO ax.cluster_management.argo_cluster_manager MainThread: Creating s3 bucket using location: http://<IP_ADDRESS>:31791/argo
2017-10-19T19:53:27 INFO ax.cluster_management.argo_cluster_manager MainThread: s3 bucket endpoint: http://<IP_ADDRESS>:31791
2017-10-19T19:53:27 INFO ax.meta.cluster_id MainThread: Instantiating cluster bucket ...
2017-10-19T19:53:32 INFO ax.cloud.aws.aws_s3 MainThread: Using region None for bucket argo
2017-10-19T19:53:32 INFO ax.meta.cluster_id MainThread: Cannot find cluster name/id mapping from bucket
2017-10-19T19:53:32 INFO ax.cluster_management.app.common MainThread: Cannot find cluster name id: Failed to load cluster name and cluster id from bucket. Cluster is not yet created.
2017-10-19T19:53:32 INFO ax.meta.cluster_id MainThread: Cluster id not provided, generate one.
2017-10-19T19:53:32 INFO ax.meta.cluster_id MainThread: Created new name-id minikube-2fcc70fc-b507-11e7-b250-025000000001
2017-10-19T19:53:32 INFO ax.meta.config_s3_path MainThread: Using AX cluster config path argo
2017-10-19T19:53:33 INFO ax.cloud.aws.aws_s3 MainThread: Using region None for bucket argo
2017-10-19T19:53:33 INFO ax.cloud.aws.aws_s3 MainThread: Using region None for bucket argo
2017-10-19T19:53:33 INFO ax.platform.ax_cluster_info MainThread: Downloading cluster current state ...
2017-10-19T19:53:33 INFO ax.platform.cluster_buckets MainThread: Creating and updating all cluster buckets ...
2017-10-19T19:53:33 INFO ax.cloud.aws.aws_s3 MainThread: Using region None for bucket argo
2017-10-19T19:53:34 INFO ax.cloud.aws.aws_s3 MainThread: Bucket argo already exist, don't create.
2017-10-19T19:53:34 INFO ax.platform.cluster_buckets MainThread: Created argo bucket ... DONE
2017-10-19T19:53:34 INFO ax.meta.config_s3_path MainThread: Using AX cluster data path argo
2017-10-19T19:53:34 INFO ax.cloud.aws.aws_s3 MainThread: Using region None for bucket argo
2017-10-19T19:53:34 INFO ax.cloud.aws.aws_s3 MainThread: Bucket argo already exist, don't create.
2017-10-19T19:53:34 INFO ax.platform.cluster_buckets MainThread: Created argo bucket ... DONE
2017-10-19T19:53:34 INFO ax.platform.cluster_buckets MainThread: Creating and updating all cluster buckets ... DONE
2017-10-19T19:53:34 INFO ax.platform.ax_cluster_info MainThread: Setting kube_config to /tmp/ax_kube/argo_cluster_inline-minikube.conf
2017-10-19T19:53:35 ERROR ax.cluster_management.argo_cluster_manager MainThread: An error occurred (AccessDenied) when calling the AssumeRole operation: Not authorized to perform sts:AssumeRole
Traceback (most recent call last):
File "/ax/python/ax/cluster_management/argo_cluster_manager.py", line 86, in parse_args_and_run
getattr(self, cmd)(args)
File "/ax/python/ax/cluster_management/argo_cluster_manager.py", line 265, in install_argo_only
PlatformOnlyInstaller(platform_install_config).run()
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 525, in run
cloud_provider=self._cfg.cloud_provider)
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 498, in update_and_save_config
raw_cluster_config_dict = self._generate_raw_cluster_config_dict()
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 408, in _generate_raw_cluster_config_dict
return self._generate_raw_cluster_config_dict_aws(config)
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 474, in _generate_raw_cluster_config_dict_aws
aws_region=self._cfg.cloud_region
File "/ax/python/ax/cloud/aws/ami.py", line 22, in init
self._amicli = boto3.Session(region_name=aws_region, profile_name=aws_profile).client("ec2")
File "/usr/local/lib/python2.7/dist-packages/boto3/session.py", line 263, in client
aws_session_token=aws_session_token, config=config)
File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 825, in create_client
credentials = self.get_credentials()
File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 449, in get_credentials
'credential_provider').load_credentials()
File "/usr/local/lib/python2.7/dist-packages/botocore/credentials.py", line 1146, in load_credentials
creds = provider.load()
File "/usr/local/lib/python2.7/dist-packages/botocore/credentials.py", line 842, in load
return self._load_creds_via_assume_role()
File "/usr/local/lib/python2.7/dist-packages/botocore/credentials.py", line 861, in _load_creds_via_assume_role
creds, response = self._retrieve_temp_credentials()
File "/usr/local/lib/python2.7/dist-packages/botocore/credentials.py", line 970, in _retrieve_temp_credentials
response = client.assume_role(**assume_role_kwargs)
File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 312, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 601, in _make_api_call
raise error_class(parsed_response, operation_name)
ClientError: An error occurred (AccessDenied) when calling the AssumeRole operation: Not authorized to perform sts:AssumeRole
!!! Operation failed due to runtime error: An error occurred (AccessDenied) when calling the AssumeRole operation: Not authorized to perform sts:AssumeRole

My env is
argo cluster ops> env | grep ARGO
ARGO_DIST_REGISTRY_SECRETS=
ARGO_DIST_REGISTRY=docker.io
argo cluster ops> env | grep AX
AX_NAMESPACE=argoproj
AX_VERSION=latest
AX_AWS_IMAGE_NAME=k8s-1.6-debian-jessie-amd64-hvm-ebs-2017-05-02
AX_KUBERNETES_ROOT=/kubernetes
AX_KUBE_VERSION=1.6.7
argo cluster ops>
argo_cluster_inline-minikube.txt

Fixed with 64c2698.


Popup two-way binding

Hi,
can you please suggest me how to do two way binding for popup?

Hello @SupriyaSudhindra,
You can check this example

Hi @KoRiGaN ,
Thanks for the update...but i need for v-model value as array object value i.e., dynamic...sorry forgot to mention that....
Also, i tried using computed, watch with deep clone etc...but didn't work

Here is the example i am trying to achieve..
<l-map :zoom="zoom" :center="center">               <l-tile-layer :url="tileprovider" :attribution="attribution"></l-tile-layer>               <l-layer-group :visible="visible" >                 <l-layer-group :visible="markersVisible" >                   <l-marker ref="pin" v-for="(items, index) in markers" :key="index" :icon="items.icon" :visible="items.visible" :draggable="items.draggable" :lat-lng="items.position">                     <l-popup >                       Location Name: {{items.location_name}}
Date: {{items.time}}
<button class="btn btn-warning btn-sm" style="color: white;margin:5% 0% 0% 35%;" @click="addStops(items.stop)">Add</button>                     </l-popup>                   </l-marker>                 </l-layer-group>                 <l-layer-group :visible="polyVisible" v-for="(poly, index) in polylines" :key="index">                   <v-editable-polyline ref="poly" :latLng="poly.points" :options="poly.options">                   </v-editable-polyline>                 </l-layer-group>               </l-layer-group>             </l-map>
computed: {     tempstudent: function () {       var me = this       if (me.studentSearch !== '') {         return me.students.filter(function (item) {           return item['text'].includes(me.studentSearch)         })       } else {         return me.students       }     },     tempmarkers: function () {       var me = this       me.Stops.filter(function (item) {         var mark = me.markers.find(x => x.log_id === item.log_id)         if (mark !== undefined) {           mark.location_name = item.location_name           mark.time = item.date           return me.markers         } else {           return me.markers         }       })     }   }
             <template slot="location_name" slot-scope="row">
{{row.value}}
                            </template>
so for the change of value of row.item.location_name should change value in popup two-way binding simultaneously.
please suggest...

Hi @KoRiGaN ,
any luck with popup two-way binding?

Hi @SupriyaSudhindra,
Still not sure what is not working. I spent some time having a try with Bootstrap table and Vue2Lealfet marker popup edition.
I ended up with this example  that works properly.
So I still don't know what is your issue as you don't provide a clear working example.
Hope this helps,

Hi @SupriyaSudhindra,
Still not sure what you want to achieve here. Do you want 2 different arrays to be sync together?

yes...

Then this is not 2-way binding and what you want to achieve is not related to a bug in Vue2Leaflet but how to implement your requirement in javascript.
The VueJs watch functionality should probably help so you should dig on this side.
You can also ask for help on VueJs Discord chat.
Micka

ok...thank you...


Recruitment cta homepage

An implementation of task #1824.
There's one main difference from the Figma design, and that's the text color on the CTA button. I used the  component since it wasn't currently in use. There's just a slight (potential) issue with the current theme implementation. primary.contrastText on the primary.light background color results in white text with a contrast ratio of only 2.07:1. Switching it to black text makes it much more readable. I can change it back to white if desired by the design team, though.

Anika from design has seen the preview and approves of the changes made. Thanks @stuttskl!👍


Pagination throw exception when dismissing the $mddialog Angularjs

The pagination works well but when displaying a dialog and dismiss then browser is frozen and show exception. I found out the root cause is $state.reload(); but I had to use this method to reload and get date from API to update.
Error in console (debug mode):
** pagination directive: the itemsPerPage id argument (id: __default) does not match a registered pagination-id.**
Code js:
var useFullScreen = ($mdMedia('sm') || $mdMedia('xs')) && vm.customFullscreen;
            $mdDialog.show({
                    templateUrl: 'app/dev-blog/dialog.composer.html',
                    controller: 'DialogController',
                    controllerAs: 'vm',
                    parent: angular.element(document.body),
                    targetEvent: ev,
                    clickOutsideToClose: true,
                    fullscreen: useFullScreen,
                    resolve: { //do some thing}

                })
                .then(function() {
                     $state.reload();
                }, function() {
                     $state.reload();
                });

Code html:

{{ article.title }}

        <dir-pagination-controls on-page-change="vm.pageChangeHandler(newPageNumber)" template-url="app/dev-blog/pagination.tpl.html"></dir-pagination-controls>

That error comes from here and means that when the pagination filter is executed, the dir-pagination-controls directive seems to not exist for some reason.
This could occur, for example, if the controls are inside an ngIf which has not yet become true. If the code you posted above is verbatim, then of course this is not the case. Is there some indication in your code (the parts you did not post here) that the controls directive may not be created after a state reload?

I try set a pagination-id="value" but this issue is still existence when call $state.reload(); Maybe when $state.reload() the service of directive is not create and issue occurs. I try using another way to reload: window.location.reload() when dismissing $mddialog and issue does not occur. But this way is not good because the page is reloaded global.

I noted, since the last upgrade (from 0.10.1 to 0.11.0), that if I switch from a state (using ui-router) to the same state with different url params, i get a this error in a loop:
angular.js:13236 pagination directive: the itemsPerPage id argument (id: myFirstPaginationID) does not match a registered pagination-id.

No error instead when I load that state for the first time, or using the previous release (0.10.1)

Hi, this should be fixed in v0.11.1. The previous release introduced a bug which I then had to revert.
Re-open if the new version is still broken.


Class file has wrong version 55.0

Hello !
I got some trouble to build the extension.

I'am on an arch linux x86_64
I git clone the master branch
I have the 9.1.2 public build 2020-feb-12 ghidra version (it works well)

export GHIDRA_INSTALL_DIR=/path/to/ghidra
./gradlew

Throw an exception :

gameboy/GhidraBoy/src/main/java/fi/gekkio/ghidraboy/RomUtils.java:16: error: cannot access ByteProvider
import ghidra.app.util.bin.ByteProvider;
^
bad class file: > /opt/ghidra_9.1.2_PUBLIC/Ghidra/Features/Base/lib/Base.jar(ghidra/app/util/bin/ByteProvider.class)
class file has wrong version 55.0, should be 52.0

Is someone else have the same issue or an idea to solve this problem ?
I'am not good with java and i don't have any idea on how to solve this.
Thanks and have a nice day !

Sorry, it was jdk version problem.
Ghidra were compiled with java 11 and i tried to build with java 8.
Just upgrade to java 11 and everything worked well
Issue closed


F2 "Rename failed to apply edits" for variables

Hello! Bug info below:
Using F2 to rename variables in VS Code fails.
I've managed to reproduce 2 types of error messages by trying different things:

If I select the variable name without the $ and try to rename, I get a red error that states "Rename failed to apply edits"
If I select the whole variable including the $ and try to rename, I get a blue error that says "Cannot read properties of undefined reading "error""

Screenshots of both errors attached.
There was nothing in the debug console in VS Code or problems in the workspace – just these little error pop ups.
This happens every time I try to rename a variable. Tested on both Windows 11 and Mac OS.
Using Yarn Spinner v2.2.15 extension, and VS Code 1.69.

Closed because I realized I didn't submit a proper bug report. Resubmitted the issue with the appropriate formatting.


QAT concept Query

@leimao Is it necessary to first train our models in FP32? Can't we train our models straight away in INT8 and still achieve the fp32 accuracy?

I would say it depends on the use cases. You can experiment on your models to see if there is any difference.


tests: call assert() when allocating memory fails

In tests, we can just call assert() when allocating memory fails,
as done in io_uring_regeister.c and io_uring_enter.c.
Signed-off-by: Zhiqiang Liu<EMAIL_ADDRESS>

It makes more sense to do this in the lib itself, for tests we can just let them crash. The kernel usually grinds itself into the ground before it fails to hand out memory.
Is this a setup concern where you regularly see malloc failures and expect the app to handle it? Because if not, I'd much rather just leave it be rather than have this churn. Crashing on NULL pointer deref or explicitly with an assert, doesn't make a lot of difference for the test case.

Another concern is that new tests will forget. Here's what I think could be done if you wanted to harden the tests:

We should have some helper code that can be used from tests. Right now a lot of basic stuff is duplicated, and it makes the tests bigger than they should be. If we had a helpers.c and helpers.h that had various utilities that tests could use, then that'd help make tests simpler.
If we had that helper, then you could add memory allocation helpers and convert the tests to use them.
If you had memory alloc helpers, then you have one unified spot to put the NULL checking into. The callers would not need to check, as they'd either get memory or an assert would be triggered and the call never returns.

If you were willing to start this helpers.c part with adding the mem alloc routines we use, then I'd be all for doing the assert. Putting the logic and assert in each caller, not so much.

Another concern is that new tests will forget. Here's what I think could be done if you wanted to harden the tests:

We should have some helper code that can be used from tests. Right now a lot of basic stuff is duplicated, and it makes the tests bigger than they should be. If we had a helpers.c and helpers.h that had various utilities that tests could use, then that'd help make tests simpler.
If we had that helper, then you could add memory allocation helpers and convert the tests to use them.
If you had memory alloc helpers, then you have one unified spot to put the NULL checking into. The callers would not need to check, as they'd either get memory or an assert would be triggered and the call never returns.

If you were willing to start this helpers.c part with adding the mem alloc routines we use, then I'd be all for doing the assert. Putting the logic and assert in each caller, not so much.

thanks for your patient reply. I will try to write this helper as you said.
Actually, I also found there were many duplicated codes in tests. After adding helper, I will try to do some cleanup.

That sounds good, thanks. Just keep it as incremental patches - first add the helper with something trivial in it, then add further things in subsequent patches. Doing just the malloc first would be a good start, then posix_memalign, etc. Thanks!

I'm going to close this one, just open a new pull request with the new approach discussed here.


Watches: Migrate phone number out of regexes

Some time ago, Mayken wrote a heavily obfuscated phone number matching regex. This migrates it to watched_numbers.txt.

The CI checks are failing because you did not follow the correct format. The items in each line of watched_numbers.txt are tab-separated. Spaces will not work. It must be:
1725623085→micsthepick→919145958860
where → is an actual tab character (\t).

!!/blame Github.dev

The file also has to end with a newline character. That got omitted somehow. This is why the CI is failing this time (Failed: watched_numbers.txt:4713:No newline).

For context, I encouraged @micsthepick to submit this as a PR so that we could have a brief discussion and rope in @makyen as a reviewer. I think we would want to do this, but I wanted to check before merging.

Perhaps to remain faithful to the original,<PHONE_NUMBER> should remain the date stamp on the new entry?

@tripleee I don't think that makes sense, unless we also attribute mayken there also, but that seems less genuine?

Well yes, if this is a migration then the original author and timestamp should be preserved; sorry for being vague.

oops, somehow in all that rebasing I managed to copy paste the wrong whitespace, one moment


Ubuntu repositories broken

Hello,
Ubuntu repositories seems to be broken, specifically I am getting '404 not found' for any .deb
from apt update
Err:1 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-host amd64 5.0.7-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:2 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-hostfxr-3.1 amd64 3.1.16-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:3 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-runtime-deps-3.1 amd64 3.1.16-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:4 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-runtime-3.1 amd64 3.1.16-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:5 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 aspnetcore-runtime-3.1 amd64 3.1.16-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:6 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-apphost-pack-3.1 amd64 3.1.16-1
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:7 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 dotnet-sdk-3.1 amd64 3.1.410-1
  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-host/dotnet-host-5.0.7-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-hostfxr-3.1/dotnet-hostfxr-3.1.16-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-runtime-deps-3.1/dotnet-runtime-deps-3.1.16-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-runtime-3.1/dotnet-runtime-3.1.16-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/a/aspnetcore-runtime-3.1/aspnetcore-runtime-3.1.16-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-apphost-pack-3.1/dotnet-apphost-pack-3.1.16-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/dotnet-sdk-3.1/dotnet-sdk-3.1.410-x64.deb  404  Not Found [IP: <IP_ADDRESS> 443]

Tried to re-download the repository package, however it seems to be simply not there:
~> wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
--2021-06-16 22:40:24--  https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-06-16 22:40:24 ERROR 404: Not Found.

This issue seems to be there only for .deb files though, as others can be downloaded without issues, e.g.
~> wget https://packages.microsoft.com/config/ubuntu/20.04/mssql-server-2019.list -O mssql-server-2019.list
--2021-06-16 22:52:28--  https://packages.microsoft.com/config/ubuntu/20.04/mssql-server-2019.list
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101 [application/octet-stream]
Saving to: ‘mssql-server-2019.list’

mssql-server-2019.list        100%[=================================================>]     101  --.-KB/s    in 0s

2021-06-16 22:52:28 (29.2 MB/s) - ‘mssql-server-2019.list’ saved [101/101]

~> cat mssql-server-2019.list
deb [arch=amd64,armhf,arm64] https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019 focal main

This is true for ALL Ubuntu versions

Broken here too
wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
--2021-06-16 20:58:37--  https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found

Seeing similar issue for:
Failed to fetch https://packages.microsoft.com/debian/10/prod/pool/main/m/msodbcsql17/msodbcsql17_<IP_ADDRESS>-1_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 443]

Same here:

@rbhanda are you able to help here? This seems similar to the situation we saw the other day #6371

Thanks for letting me @michaelgsharp . I am following up on this with our infrastructure team.

Update: Our infra team is working on this. There is an issue with some of the mirrors on packages.microsoft.com so as per them, the current ETA to resolve this issue is in next two hours or so.

@rbhanda - can you please provide me an update ?

https://github.com/microsoft/vscode/issues/126543

Update: our infra team is still working to resolve this issue. They ran into some space issues but this issue should be resolved quickly. Unfortunately, I do not have an ETA yet.

I also understand this is little-bit off-topic for this project.
But let me just say this; I think the problem is not only package repository was broken. Another side of the problem is about communication.
It might be there some progresses on some task tracking system ore some collaboration tools at Microsoft. But we can't see it.
Following issues were opened and some issues were closed so quickly.
It doesn't show somewhere to go. It doesn't show how long we must wait.
So issues are opened repeatedly here and there. This is spreading between projects outside of Microsoft.

https://github.com/MicrosoftDocs/sql-docs/issues/6495
https://github.com/MicrosoftDocs/sql-docs/issues/6494
https://github.com/dotnet/core/issues/6381
https://github.com/microsoft/msphpsql/issues/1271
https://github.com/microsoft/vscode/issues/126543
https://github.com/mkleehammer/pyodbc/issues/914

FYI the Edge repo is broken as well, the whole pool directory is gone: https://packages.microsoft.com/repos/edge/pool/

FYI the Edge repo is broken as well, the whole pool directory is gone: https://packages.microsoft.com/repos/edge/pool/

Same problem for the Teams repo

We've also had the bug raised against our Microsoft build of OpenJDK repo https://github.com/microsoft/openjdk/discussions/74

This of course affects everyone who uses GitHub Actions' Ubuntu image and hasn't already binned off any repositories that include the word "microsoft" (that are included by default) in their apt config as part of their pipeline.
@kitsuyui is correct that the communication from MS/GH around reliability of these servers is somewhat lacking. To add to the list of knock-on issues, a while ago I filed https://github.com/actions/virtual-environments/issues/3410 when unavailability of these servers last bit me, but GitHub's response was (somewhat amazingly) basically not our problem, wontfix.

I can confirm this issue. 404 in every debian or ubuntu .deb I search.
In the meantime, is there a mirror where we could find the packages?
Get:1 http://deb.debian.org/debian buster/main amd64 multiarch-support amd64 2.28-10 [215 kB] Ign:2 https://packages.microsoft.com/debian/10/prod buster/main amd64 odbcinst amd64 2.3.7 Ign:3 https://packages.microsoft.com/debian/10/prod buster/main amd64 unixodbc-dev amd64 2.3.7 Ign:4 https://packages.microsoft.com/debian/10/prod buster/main amd64 odbcinst1debian2 amd64 2.3.7 Ign:5 https://packages.microsoft.com/debian/10/prod buster/main amd64 libodbc1 amd64 2.3.7 Ign:6 https://packages.microsoft.com/debian/10/prod buster/main amd64 unixodbc amd64 2.3.7 Err:7 https://packages.microsoft.com/debian/10/prod buster/main amd64 msodbcsql17 amd64 <IP_ADDRESS>-1   404  Not Found [IP: <IP_ADDRESS> 443] Err:2 https://packages.microsoft.com/debian/10/prod buster/main amd64 odbcinst amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443] Err:3 https://packages.microsoft.com/debian/10/prod buster/main amd64 unixodbc-dev amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443] Err:4 https://packages.microsoft.com/debian/10/prod buster/main amd64 odbcinst1debian2 amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443] Err:5 https://packages.microsoft.com/debian/10/prod buster/main amd64 libodbc1 amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443] Err:6 https://packages.microsoft.com/debian/10/prod buster/main amd64 unixodbc amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443] Fetched 215 kB in 1s (373 kB/s) Unable to correct missing packages.

Some people suggesting its an issue isolated to Europe, other regions as able to build
https://docs.microsoft.com/en-us/answers/questions/439491/pyodbc-install-error-in-azure-databricks-file-not.html

14 hours! this is blocking us in the production environment right now. as we can't build new machines/vms in Azure.

same too with Debain10 and Ubuntu 20.04LTS

Same here - this is going to be a killer

Might be worth holding off on the "me too!" or "+1" comments unless there's some new information to make the issue easier to follow.

Space issues?
LOL

Ask Bill to buy some disks from Amazon :-P

I started seeing issue with  Certificates (https://packages.microsoft.com/keys/microsoft.asc) too

I can confirm this issue too. We noticed this today morning and the releases are blocked because of this.
command in DockerFile:
RUN apt-get update && apt-get install -y --no-install-recommends \      g++ \     unixodbc-dev
Error in azure pipelines:
Err:1 https://packages.microsoft.com/debian/9/prod stretch/main amd64 unixodbc-dev amd64 2.3.7   404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/debian/9/prod/pool/main/u/unixodbc/unixodbc-dev_2.3.7_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 443]

I have also started seeing this issue from 17th june morning IST timezone,
Need to get 210 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal/main amd64 azure-functions-core-tools-3 amd64 3.0.3568-1 [210 MB]
It has got stuck here and not able to get the response. Kindly help in resolving the issue.

@rbhanda any update on this, this is blocking production server builds for us

@rbhanda  - its same here and I hope a lot of processes / projects are impacted, is there any update ETA, and any MSFT official status page having the details and update ?

any updates on this
this is affecting Production environment and we need some ETA to communicate to our Stack holders

for people who need, snap installation is working, i know it is not apt but it can be a temporary solution

14 hours later and this is still broken - prevents rolling new builds.  Can we get an update on this please???

for people who need, snap installation is working, i know it is not apt but it can be a temporary solution

@rvResolving can you please provide some context with commands around what works for you?
I am using the apt repositories (on Debian) for the SQL Server integration, so I tried this:
snap find microsoft | grep -e msodbcsql17 -e mssql-tools -e unixodbc-dev

It does not find anything

All deb-based repos at packages.microsoft.com are broken. I suggest, that they hid the "pool" folder for some reason.

I tried to use proxy in US, but unfortunately no success in doing that, pool folder does not exists. Also snap wont help for packages aziot-edge and moby-engine

Ask Bill to buy some disks from Amazon ;-)

No need! His 5G vaccine is turning everybody with a phone into supplementary Azure bio-blob storage! I wonder what files I'm infected with? Exciting!

It does not find anything. I also tried the strings msodbcsql17 and so on, still nothing is being found.

@tappoz i don't know for msodbcsql17 i need the donet-sdk
and  I just do sudo snap install dotnet-sdk --classic --channel=3.1

There seems to be a common root cause to all the Microsoft apt repos. People is cross-referencing different GitHub issues in different git repositories.

Similar issues here trying to use Ubuntu packages

I was able to get the package using Invoke-WebRequest
PS C:\Users\felipe> iwr https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -OutFile packages-microsoft-prod.deb
PS C:\Users\felipe> dir | findstr "pac"
-a----         6/17/2021  10:31 AM           3124 packages-microsoft-prod.deb

This seems to be the most active thread on the issue, does anyone know if this is being tracked elsewhere by Microsoft, this is affecting our production systems and we need some sort of ETA.

I have also started seeing this issue from 17th june,2021 morning IST timezone,
Need to get 210 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal/main amd64 azure-functions-core-tools-3 amd64 3.0.3568-1 [210 MB]
It has got stuck here and not able to get the response. Kindly help in resolving the issue.
This one also i got -
curl: (28) Failed to connect to packages.microsoft.com port 443: Connection timed out
gpg: no valid OpenPGP data found.
Error: Process completed with exit code 2.

@rbhanda Could you let me know when this issue will get fixed, Below is the script i am using to download the package
    curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
    sudo mv microsoft.gpg /etc/apt/trusted.gpg.d/microsoft.gpg
    sudo sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-ubuntu-$(lsb_release -cs)-prod $(lsb_release -cs) main" > /etc/apt/sources.list.d/dotnetdev.list'
    sudo apt-get update
    sudo apt-get install azure-functions-core-tools-3

Just making some noise here 😄

Seems to be fixed..

Yes, deb's such as dotnet-host-5.0.7-x64.deb are available again.

I can confirm that it is fixed now 👍 ❤

.deb packages available again!

Finally! Everybody on their way doing build and deployments :)

I'm sure there'll be no congestions when hundreds or maybe thousands of machines pull large packages at the exact same time ;-)

Now i am getting this error -
Get:21 https://releases.jfrog.io/artifactory/jfrog-debs xenial/contrib amd64 Packages [3634 B]
Ign:22 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
Err:23 https://packages.microsoft.com/ubuntu/20.04/prod focal Release
Could not connect to packages.microsoft.com:443 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 443]
Reading package lists...
E: The repository 'https://packages.microsoft.com/ubuntu/20.04/prod focal Release' no longer has a Release file.

Still seeing an issue : The repository 'https://packages.microsoft.com/ubuntu/18.04/prod bionic Release' does not have a Release file.

Well, the speed was 58KB/s, now it's nown to 22KB/s as more machines noticed the repos are up.  But I hope a few more acoustic modems will be added to the cloud. ☺
(That's in jest — thanks for making it work again!)

Hello,
As per our infra team, you may see degraded performance but the packages should be available as of now. The original cause of this issue was because there was a regression in APT Linux repos during some feature migration work that resulted in the APT repo packages becoming unavailable on the mirrors.

Does anybody have some mirrors?

Does anybody have some mirrors?

In my bathroom, yes.
For this, unfortunately not 🙁

apt install apt-cacher-ng then point all machines on your site to it.  Should help if you download the same package multiple times; and it'll be good to leave the cache running even after the current performance degradation is resolved.

apt install apt-cacher-ng then point all machines on your site to it. Should help if you download the same package multiple times; and it'll be good to leave the cache running even after the current performance degradation is resolved.

This package is broken and has lots of bugs. Better use this:
https://packages.debian.org/buster/squid-deb-proxy
We were using apt-cacher-ng for CI and such and index files broke multiple times per week. This has also been acknowledged by the maintainers. After the switch to squid-deb-proxy, cache worked better and we never had to do any maintenance again.

I'm still seeing problems:
2021-06-17T15:27:24.1409046Z -- 2021-06-17 15:27:24--  https://packages.microsoft.com/config/ubuntu/16.04/packages-microsoft-prod.deb
2021-06-17T15:27:24.1464907Z Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
2021-06-17T15:27:24.1985507Z Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
2021-06-17T15:27:24.4294434Z HTTP request sent, awaiting response... 500 Internal Server Error
2021-06-17T15:27:24.4297105Z 2021-06-17 15:27:24 ERROR 500: Internal Server Error.

I had the same issue two hours ago with Moby. But at this moment I am able to install it. The installation was very, very slow but at the end it was completed. I am working with Ubuntu 18.04.

One can also use https://www.aptly.info for mirroring

Hello, at my step,  i now have:
Err:1 https://packages.microsoft.com/ubuntu/21.04/prod hirsute/main amd64 dotnet-host amd64 5.0.7-1
Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/21.04/prod/pool/main/d/dotnet-host/dotnet-host-5.0.7-x64.deb  Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: <IP_ADDRESS> 443]

seems like now the Azure devops is having issue - https://status.dev.azure.com/_event/246136621

also seeing issues downloading azure-cli content from microsofts yumrepos:
azure-arm: [MIRROR] azure-cli-2.25.0-1.el7.x86_64.rpm: Curl error (28): Timeout was reached for https://packages.microsoft.com/yumrepos/azure-cli/azure-cli-2.25.0-1.el7.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]

We are still having issues
https://packages.microsoft.com/debian/10/prod buster/main amd64 aspnetcore-runtime-2.1 amd64 2.1.28-1
[8 aspnetcore-runtime-2.1 3768 kB/21.9 MB 17%]        8183 B/s 3h 43min 46s30% [8 aspnetcore-runtime-2.1 3784 kB/21.9 MB 17%]        8183 B/s 3h 43min 44s30% [8 aspnetcore-runtime-2.1 3784 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 50s30% [8 aspnetcore-runtime-2.1 3784 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 50s30% [8 aspnetcore-runtime-2.1 3784 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 50s30% [8 aspnetcore-runtime-2.1 3784 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 50s30% [8 aspnetcore-runtime-2.1 3801 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 48s30% [8 aspnetcore-runtime-2.1 3801 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 48s30% [8 aspnetcore-runtime-2.1 3817 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 47s30% [8 aspnetcore-runtime-2.1 3817 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 47s30% [8 aspnetcore-runtime-2.1 3817 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 47s30% [8 aspnetcore-runtime-2.1 3817 kB/21.9 MB 17%]       10.9 kB/s 2h 47min 47s30% [8 aspnetcore-runtime-2.1 3833 kB/21.9 MB 18%]       10.9 kB/s 2h 47min 45s30% [8 aspnetcore-runtime-2.1 3833 kB/21.9 MB 18%]       10.9 kB/s 2h 47min 45s30% [8 aspnetcore-runtime-2.1 3833 kB/21.9 MB 18%]        8183 B/s 3h 43min 38s30% [8 aspnetcore-runtime-2.1 3850 kB/21.9 MB 18%]        8183 B/s 3h 43min 36s30% [8 aspnetcore-runtime-2.1 3850 kB/21.9 MB 18%]
The pipeline is taking hours if it will ever finish

The servers seem to be overloaded for now but the files are indeed back when checked manually. Our Travis-ci build is now failing with a timeout.

Microsoft ran in an overload situation. Maybe try GCP?

@rbhanda will there be an incident report in response to this? I'd be particularly interested in why mirror sites were not available or if available, why there is a single point of failure affecting them all.  We've faced issues in the past where packages would fail when a deployment was running but a cataclysmic failure of this nature would have affected many production workloads today. Package managers are the backbone of our industry and we need to be able to rely on them. I've been forced to remove reliance on Microsoft package repos in favour of self hosted ones for the time being which is unnecessary manual maintenance I'd like to avoid if possible. Will there be an issue I can track on Microsoft adding reliable resilience to these services? Also, are there any status pages I can refer to going forward on these services?

Have This Issue, I Also +1

@rbhanda will there be an incident report in response to this? I'd be particularly interested in why mirror sites were not available or if available, why there is a single point of failure affecting them all. We've faced issues in the past where packages would fail when a deployment was running but a cataclysmic failure of this nature would have affected many production workloads today. Package managers are the backbone of our industry and we need to be able to rely on them. I've been forced to remove reliance on Microsoft package repos in favour of self hosted ones for the time being which is unnecessary manual maintenance I'd like to avoid if possible. Will there be an issue I can track on Microsoft adding reliable resilience to these services? Also, are there any status pages I can refer to going forward on these services?

Agree, this is the 3rd time we have encountered this issue, and Microsoft does not seem care.

@rbhanda will there be an incident report in response to this? I'd be particularly interested in why mirror sites were not available or if available, why there is a single point of failure affecting them all. We've faced issues in the past where packages would fail when a deployment was running but a cataclysmic failure of this nature would have affected many production workloads today. Package managers are the backbone of our industry and we need to be able to rely on them. I've been forced to remove reliance on Microsoft package repos in favour of self hosted ones for the time being which is unnecessary manual maintenance I'd like to avoid if possible. Will there be an issue I can track on Microsoft adding reliable resilience to these services? Also, are there any status pages I can refer to going forward on these services?

Agree, this is the 3rd time we have encountered this issue, and Microsoft does not seem care.

That's nothing new and has always been working like that. This applies to many of their products and services.
You always need an alternative handy (which is always a good idea, not just when working with MS).

We had an incident with packages.microsoft.com that resulted in packages being unavailable. Our engineering team has mitigated the issue and our internal data shows improvement in the availability. If you still have problems, please provide us more information (output of "apt-get update|install") and we can investigate it further.

Install azure-cli is also very slow when downloading it via official scripts: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

Same for me, downloads are very slow from packages.microsoft.com

This is what I'm seeing at the moment
Get:1 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 odbcinst amd64 2.3.7 [12.0 kB]
Err:2 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 unixodbc-dev amd64 2.3.7
  Connection failed [IP: <IP_ADDRESS> 443]
Get:3 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 odbcinst1debian2 amd64 2.3.7 [135 kB]
Err:4 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 libodbc1 amd64 2.3.7
  Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: <IP_ADDRESS> 443]

Sorry for all of the issues and inconveniences this has caused! I just saw a report from the team that owns packages.microsoft.com and here's a summary of where they're at:

West US mirrors will be up very soon (if not already done), which should begin to alleviate some of the performance issues.
Mirrors in Europe online in ~5 hours (currently replicating), which will address the latency in Europe and further help the US responsiveness by reducing the load.

Don't spy on users (I'm looking on You Win10) and You will have a lot of free space on disks.

From Europe behind a proxy impossible to download   few byte/s

Using a VPN and ipconfig /flushdns i was able to download azure cli since europe still down

apt-get fails to get the package from this repo.
Get:1 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 blobfuse amd64 1.3.7 [7,195 kB].
Is this a known issue that is getting worked upon?

Now it works

yeah it is still slow(intermittently) but working..

Yeah ours is running only from last 2 hours not sure when it will complete :( @rbhanda  Please let me know when we can expect this to be completely working.

This solution helped for me
snap install dotnet-sdk --classic

I don't think it is appropriate for Microsoft to proclaim to the world in their own health dashboards and event trackers that all is well, when these services are still clearly degraded.

Yeah ours is running only from last 2 hours not sure when it will complete :( @rbhanda Please let me know when we can expect this to be completely working.

Now i can confirm its running fine, but yeah we need to monitor it for few more times.
Thanks

I'm just downloading code update and it's ~500kbps so slow.....

60kb/sec for the azure-cli :( Still hope that microsoft will fix their slow connection for ubuntu repositories.

Confirming the incident resolution at 10:17PM PST last night. We have restored the service in all regions, been monitoring the results since resolution and got confirmation from multiple customers that they no longer observe the issue. Thank you for reporting this issue.

Hey guys,
I am still having issues interacting with the repo...
`#10 6.790 deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ hirsute main
#10 6.961 Hit:1 http://archive.ubuntu.com/ubuntu hirsute InRelease
#10 7.009 Hit:2 http://archive.ubuntu.com/ubuntu hirsute-updates InRelease
#10 7.070 Hit:3 http://archive.ubuntu.com/ubuntu hirsute-backports InRelease
#10 7.096 Hit:4 http://security.ubuntu.com/ubuntu hirsute-security InRelease
#10 7.156 Ign:5 https://packages.microsoft.com/repos/azure-cli hirsute InRelease
#10 7.215 Err:6 https://packages.microsoft.com/repos/azure-cli hirsute Release
#10 7.215   404  Not Found [IP: <IP_ADDRESS> 443]
#10 7.306 Reading package lists...
#10 7.837 E: The repository 'https://packages.microsoft.com/repos/azure-cli hirsute Release' does not have a Release file.
executor failed running [/bin/sh -c DEBIAN_FRONTEND="noninteractive"  apt-get install -yq ca-certificates curl apt-transport-https lsb-release gnupg         && curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null         && AZ_REPO=$(lsb_release -cs)         && echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" | tee /etc/apt/sources.list.d/azure-cli.list         && apt-get update         && apt-get install -yq azure-cli         && apt-get clean]: exit code: 100`

My bad... I was using ubuntu 21.04 (hirsute). I noticed that version is not yet supported (doesn't exist) in the repo: https://packages.microsoft.com/repos/azure-cli/dists/
Switched back to 20.04 (focal) and it worked.
Thanks

Closing since the issue has been resolved.

pi@raspberrypi:~ $ sudo apt-get install -y dotnet-runtime-5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-runtime-5.0
E: Couldn't find any package by glob 'dotnet-runtime-5.0'
E: Couldn't find any package by regex 'dotnet-runtime-5.0'

It somehow does not work...

pi@raspberrypi:~ $ sudo apt-get install -y dotnet-runtime-5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-runtime-5.0
E: Couldn't find any package by glob 'dotnet-runtime-5.0'
E: Couldn't find any package by regex 'dotnet-runtime-5.0'

It somehow does not work...

+1
still the same problem for me too
Used these receipes:
https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#2004-
and
https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#apt-troubleshooting

I am having trouble install az package

@xTEddie That issue is probably related to the packages.microsoft.com outage that has happened today. See #6560.

cannot install dotnet5 on ubuntu, is this still a problem?

Solved by manual install.
Brgds
Stefano Hämmerle @.***> (šajā datumā: pirmd., 2021. g.
30. aug. 12:11) rakstīja:

cannot install dotnet5 on ubuntu, is this still a problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/6381#issuecomment-908178366, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWC4YCJBZFTFLSOBXDJIYTT7NDLBANCNFSM462H54IQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@rbhanda What is the correct place to file issues with repositories located at https://packages.microsoft.com/?
Specifically, I have noticed some issues with https://packages.microsoft.com/rhel/8/prod/, but I have not been able to find the correct venue to report them.

Hello @dralley as of now we do not have a repository for  https://packages.microsoft.com/ on GitHub. Until we have one, if you are facing any issues, I recommend to create them on https://github.com/dotnet/core/issues

I know this thread is old but I am still seeing this issue with 20.04
Ign:6 https://packages.microsoft.com/config/ubuntu/20.04/prod focal InRelease Err:7 https://packages.microsoft.com/config/ubuntu/20.04/prod focal Release   404  Not Found [IP: <IP_ADDRESS> 443] Reading package lists... Done E: The repository 'https://packages.microsoft.com/config/ubuntu/20.04/prod focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
surely a company with as much resource as Microsoft could fix an issue like this and not take 4 months to do so?

I'm on Ubuntu Impish 20.10.
The command given at https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#2110- refers to 20.10

But when I go to https://packages.microsoft.com/config/ubuntu/, there's no 20.10

I had to change the command to below:
wget https://packages.microsoft.com/config/ubuntu/21.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

Then it worked like a charm.
Perhaps before pushing out documentation, it would be good to test and verify the commands in them.

@hrai it would be great if you open feedback for the doc in question. There's a feedback button on the bottom of the page. /cc @adegeo

To close the loop, this was updated in the doc: using the 21.04 repository is the current guidance.

Itt seems it's still problematic this morning. Both Azure Devops pipelines are taking an eternity to download Packages and on my workstation too (avg 85kb/s)


yum_package version comparison works differently from yum itself

Description
yum_package installs older version than yum would install.
We have some internal packages with version strings gathered from issue tracker issue numbers and commit id's. The logic is that packages from the master branch are "newer" than packages from branches. This works when installing with yum by hand, but yum_package installs the branch version incorrectly.
Example of the versions, from master: 1.3+36_ga1cdc0f-199 and from a branch: 1.3~354_g6c80130~ISSUE_117-7. The + and ~ stuff originates from the deb packages of the same software.
Any way, I tracked the error through the Chef::Provider::Package::Yum stuff, to rpm_utils
Like the comment says, it's a bit difficult. :)
Chef Version
13.6.4
Platform Version
CentOS 7.2
Replication Case
Minimal example:
require 'chef/provider/package/yum/rpm_utils'
Chef::Provider::Package::Yum::RPMUtils.rpmvercmp('1.3+36_ga1cdc0f', '1.3~354_g6c80130~ISSUE_117')
=> -1

Compared with the Python library of yum, yum itself and rpmdev-vercmp:
>>> import yum
>>> yum.rpmUtils.miscutils.compareVerOnly('1.3+36_ga1cdc0f', '1.3~354_g6c80130~ISSUE_117')
1

# yum install internal-package
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
...
Resolving Dependencies
--> Running transaction check
---> Package internal-package.noarch 0:1.3~354_g6c80130~ISSUE_117-7.el7 will be updated
---> Package internal-package.noarch 0:1.3+36_ga1cdc0f-199.el7 will be an update

$ rpmdev-vercmp  1 1.3+36_ga1cdc0f 199 1 1.3~354_g6c80130~ISSUE_117 7
1:1.3+36_ga1cdc0f-199 > 1:1.3~354_g6c80130~ISSUE_117-7

Some more things I checked with package objects and RPMDb:
master_pkg = Chef::Provider::Package::Yum::RPMDbPackage.new('internal-package', '0', '1.3+36_ga1cdc0f', '199', 'noarch', [], false, false, 'testing-repoid')
branch_pkg = Chef::Provider::Package::Yum::RPMDbPackage.new('internal-package', '0', '1.3~354_g6c80130~ISSUE_117', '7', 'noarch', [], false, false, 'testing-repoid')
master_pkg.compare(branch_pkg)

rpmdb = Chef::Provider::Package::Yum::RPMDb.new()
rpmdb.push(branch_pkg)
rpmdb.push(master_pkg)
rpmdb['internal-package'][0].version

think i'm going to close this one, work can be tracked in #6540 which should be fixed in Chef-14.0 (we're pretty much at the point where failure is not an option and it has to ship then)


ci: run: consoletests: Fail on error

ci: run: consoletests: Fail on error
examples: tutorials: models: slr: run: Add MSE scorer

Codecov Report

Merging #1195 (78a6ba7) into master (051577b) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1195      +/-   ##
==========================================
- Coverage   86.09%   86.02%   -0.08%
==========================================
  Files         171      171
  Lines       10700    10696       -4
  Branches     1755     1755
==========================================
- Hits         9212     9201      -11
- Misses       1141     1148       +7
  Partials      347      347

Impacted Files
Coverage Δ

dffml/util/data.py
72.92% <0.00%> (-2.77%)
:arrow_down:

tests/util/test_net.py
98.36% <0.00%> (-1.64%)
:arrow_down:

dffml/noasync.py
78.94% <0.00%> (-1.06%)
:arrow_down:

dffml/base.py
83.81% <0.00%> (-0.29%)
:arrow_down:

dffml/util/testing/consoletest/commands.py
75.56% <0.00%> (-0.06%)
:arrow_down:

dffml/source/df.py
75.60% <0.00%> (ø)

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 051577b...78a6ba7. Read the comment docs.

Merged


[Bug] Fix warning DB: Row X doesn't contain data for all columns in OC challenge service

Is there an existing issue for this?

[X] I have searched the existing issues

What product(s) are you seeing the problem on?
OpenChallenges
Current behavior
$ nx serve openchallenges-challenge-service
...
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 36 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 37 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 38 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 39 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 40 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 41 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 42 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 43 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 44 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 45 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 46 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 47 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 48 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 49 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 50 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 51 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 52 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 53 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 54 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 55 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 56 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 57 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 58 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 59 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 60 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 61 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 62 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 63 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 64 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-10-19 22:09:02 INFO  [restartedMain] o.f.core.internal.command.DbMigrate - Successfully applied 2 migrations to schema `challenge_service`, now at version v1.0.1 (execution time 00:00.304s)

Expected behavior
No response
Anything else?
No response
Commit ID
10dc1a3ebba33591ad984bd117b560325ac529a2
Are you developing inside the dev container?

[X] I am using the dev container

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Added to Sprint 23.11

This issue does not affect the organization service

The challenge service shows this error twice that counts rows from 1 to 64:
...
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 62 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 63 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 64 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 1 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 2 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
2023-11-02 17:00:44 WARN  [restartedMain] o.f.c.i.s.DefaultSqlScriptExecutor - DB: Row 3 doesn't contain data for all columns (SQL State: 01000 - Error Code: 1261)
...

One batch of 1-64 errors comes from:
LOAD DATA LOCAL INFILE '${db_incentives_csv_path}' INTO TABLE challenge_incentive
  FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
  LINES TERMINATED BY '\n'
  IGNORE 1 LINES
  SET created_at=NOW();

Another batch:
-- challenge_submission_type data
LOAD DATA LOCAL INFILE '${db_submission_types_csv_path}' INTO TABLE challenge_submission_type
  FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
  LINES TERMINATED BY '\n'
  IGNORE 1 LINES
  SET created_at=NOW();

@vpchung The issue is because incentives.csv and submission_types.csv do not include data for created_at. Also, we should export the "created at" information from the spreadsheet instead of executing SET created_at=NOW();.

Sounds good.
Out of curiosity, why are we tracking created_at for these tables?

It's a standard field that usually part of all tables that may receive new records at any time. This column is often used for the sake of troubleshooting errors using time related information (e.g. new record should have been added on "2023-10-01").

CSV files for incentives and submission types now include the created_at values from the challenges sheet:

This fix will be seen with the data push on Monday.


Support other term query format and support number term value.

Fix #3900.
Tests added.
The PR is a bit lame... I mostly copy pasted the code used to deserialize the match query and adapted it to the term query.
We may want to find a generic way of handling this... I suggest to not do  it now unless there is an obvious way to do it (I'm not capable to see that right now).

Can we prefer it https://github.com/quickwit-oss/quickwit/pull/3906?


Incorrect architecture detection on M1 Mac arm64 on Chrome 118.0.5993.117

Summary
Short summary of the bug or feature request.
On m1 max mac/arm64 I am getting the x86 chromedriver and hence it launches slow compatibility chrome.
You can see in the logs it decides I'm not compatible when comparing version strings.  Possibly a bug there.
2023-10-30 13:24:37 DEBUG Webdrivers Checking current version
2023-10-30 13:24:37 DEBUG Webdrivers /Users/daniel.toms/.webdrivers/chromedriver is not already downloaded
2023-10-30 13:24:37 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers Checking current version
2023-10-30 13:24:38 DEBUG Webdrivers /Users/daniel.toms/.webdrivers/chromedriver is not already downloaded
2023-10-30 13:24:38 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers Making network call to https://googlechromelabs.github.io/chrome-for-testing/latest-patch-versions-per-build.json
2023-10-30 13:24:38 DEBUG Webdrivers Get response: #<Net::HTTPOK 200 OK readbody=true>
2023-10-30 13:24:38 DEBUG Webdrivers Latest version available: 118.0.5993.70
2023-10-30 13:24:38 DEBUG Webdrivers Deleting /Users/daniel.toms/.webdrivers/chromedriver.version
2023-10-30 13:24:38 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers Checking current version
2023-10-30 13:24:38 DEBUG Webdrivers /Users/daniel.toms/.webdrivers/chromedriver is not already downloaded
2023-10-30 13:24:38 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers making System call: ["//Applications/Google Chrome.app/Contents/MacOS/Google Chrome", "--version"]
2023-10-30 13:24:38 DEBUG Webdrivers System call returned: Google Chrome 118.0.5993.117

2023-10-30 13:24:38 DEBUG Webdrivers Browser version: Google Chrome 118.0.5993.117
2023-10-30 13:24:38 DEBUG Webdrivers Making network call to https://googlechromelabs.github.io/chrome-for-testing/latest-patch-versions-per-build.json
2023-10-30 13:24:38 DEBUG Webdrivers Get response: #<Net::HTTPOK 200 OK readbody=true>
2023-10-30 13:24:38 DEBUG Webdrivers Latest version available: 118.0.5993.70
2023-10-30 13:24:38 DEBUG Webdrivers Making network call to https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json
2023-10-30 13:24:38 DEBUG Webdrivers Get response: #<Net::HTTPOK 200 OK readbody=true>
2023-10-30 13:24:38 DEBUG Webdrivers Apple architecture: Intel (mac64)
2023-10-30 13:24:38 DEBUG Webdrivers chromedriver version is NOT Apple M1 compatible. Required >= 87.0.4280.88
2023-10-30 13:24:38 DEBUG Webdrivers Apple architecture: Intel (mac64)
2023-10-30 13:24:38 DEBUG Webdrivers chromedriver version is NOT Apple M1 compatible. Required >= 87.0.4280.88
2023-10-30 13:24:38 DEBUG Webdrivers Apple architecture: Intel (mac64)
2023-10-30 13:24:38 DEBUG Webdrivers chromedriver version is NOT Apple M1 compatible. Required >= 87.0.4280.88
2023-10-30 13:24:38 DEBUG Webdrivers chromedriver URL: https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/118.0.5993.70/mac-x64/chromedriver-mac-x64.zip
2023-10-30 13:24:38 DEBUG Webdrivers Making network call to https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/118.0.5993.70/mac-x64/chromedriver-mac-x64.zip
2023-10-30 13:24:39 DEBUG Webdrivers Get response: #<Net::HTTPOK 200 OK readbody=true>
2023-10-30 13:24:39 DEBUG Webdrivers Successfully downloaded /var/folders/7x/xnyl5k7d0xd6q9y6pnb74fsw0000gp/T/20231030-40959-in71mvchromedriver-mac-x64.zip
2023-10-30 13:24:39 DEBUG Webdrivers Decompressing /var/folders/7x/xnyl5k7d0xd6q9y6pnb74fsw0000gp/T/20231030-40959-in71mvchromedriver-mac-x64.zip
2023-10-30 13:24:39 DEBUG Webdrivers Completed download and processing of /Users/daniel.toms/.webdrivers/chromedriver

Debug Info
Please provide the following information for bug reports:

Webdrivers version:       webdrivers (>= 5.3.1, < 6)
Ruby version: ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-darwin21]

This was my/our bad.  Somehow I had the x86 version of ruby installed which is part of the above logic check. Uninstalling it,  reinstalling it to get the correct arm version, removing the existing chromedriver, then re-running solved the issue.


New feature "Optimize" as we have talked in #107

This way it is easier to compare than with the ZIP that I sent you.
I have also corrected a problem when the piece has no holes to recognize.

That looks great.
I might change the name if that's OK.  In my opinion, it doesn't really capture what the command does.
I usually announce new releases on the SE Forum.  This one might go out later this summer.  I want to give you credit when that happens, but would prefer you change your profile name to something that doesn't look like a database key.
Thank you for your contribution!


Two records shows up for each email sent in Correspondence log

Duplicated issue #2882. Closed this one.


Bug | Failed to build iOS app

Describe the bug
Swift Compiler Error (Xcode): Could not build Objective-C module 'in_app_purchase_storekit'
To reproduce
Error in Screenshot when fvm flutter run -d device id
Expected behavior
flutter run successfully
Screenshots

Desktop (please complete the following information)

OS: [macOS] - Version: [12.6]

Smartphone (please complete the following information)

Device: [IPhone 14 Pro Max]

Additional context
No response

fixed i missed in build use other flutter version by "flflutter pub run build_runner build -d"
I Use:
"fvm flutter pub run build_runner build -d"


[CW-3751] Revert back to original multipath code handling.

We need to back to upstream original code for multipath handling to avoid flapping.

There is another root cause for the issue.


update meta.yaml with python constraints

Checklist

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

fix https://github.com/conda-forge/baal-feedstock/issues/10

@conda-forge-admin, please rerender


minor fix: don't calc model J-52 on amount

this fix don't let the lib handle with the model J-52, that doesn't have payment values.

@ali1ariel hi! Thanks for the PR!!


Add support for points to Cesium3DTileset option classificationType

Summary:
As stated in the docs, the classificationType option for Cesium3dTileset currently ‘... is not supported for points or instanced 3D models.’
When used to create tilesets consisting of both line and points entities the classification only applies to the line entities and not the points.
Example:
Cesium3DTileset.fromUrl can be used to create an instance consisting of lines and labelled points in a Cesium viewer, and providing the option classificationType: Cesium.ClassificationType.TERRAIN will clamp the lines entities to the terrain but not the points.
Example code:
const viewer = new Cesium.Viewer("cesiumContainer");

//tileset consists of lines.vctr, points.vctr and tileset.json
const tileset = await Cesium.Cesium3DTileset.fromUrl('/Apps/SampleData/tileset.json', {
  classificationType: Cesium.ClassificationType.TERRAIN,
});

tileset.style = new Cesium.Cesium3DTileStyle({
  color: "rgb(255, 0, 0, 1)",
});

viewer.scene.primitives.add(tileset);
viewer.zoomTo(tileset);

Result: Linework entities are clamped to terrain with points floating above.
Request:
Provide classification support for points, in order to enable clamping of instances that consist of both lines and points entities to terrain or other 3d tilesets by providing the classificationType option with Cesium.ClassificationType.TERRAIN or Cesium.ClassificationType.CESIUM_3D_TILES values.

Hi @gdiehlEB, thanks for the request!
I believe this is a duplicate of https://github.com/CesiumGS/cesium/issues/6714. I'm going to close this issue and add your a link to your writeup there to keep conversation in one place. Thanks!

@ggetz While testing the implementation from my draft PR with the new heightReference options, I found clamping to a 3D tile works if the 3d Tile is added directly to viewer.scene.primitives but not if it is added via a PrimitiveCollection.
So setting heightReference.CLAMP_TO_3D_TILE will clamp a point, etc to tileset in this case:
const tileset = await Cesium.Cesium3DTileset.fromUrl('/Apps/SampleData/b3dmTileset.json', {
});
viewer.scene.primitives.add(tileset);

but not in this case:
const tileset = await Cesium.Cesium3DTileset.fromUrl('/Apps/SampleData/b3dmTileset.json', {
});

const collection = new Cesium.PrimitiveCollection();
collection.add(tileset);

viewer.scene.primitives.add(collection);

This is something I'd like to add support for as part of this issue. Do you have any thoughts as to what that would entail, any pitfalls, etc? I am familarizing myself with both of your recent PRs to get a better understanding but figure you might have some good insight.

This is something I'd like to add support for as part of this issue.

Will open a 2nd PR separate from #11710 to support clamping to tilesets within hierarchies of Primitives.


telegraf

URL for relevant page?
What products and version are you using?
Where did you look before opening the issue?

Closing since no info.


Try to scan 'non-functional' QR code - improve UI

Possibly related to #469 ?
Current Implementation

Today I got tested at Fürstenfeldbruck. A very lightweight, fully digitized procedure for self-registration. They have meanwhile added a checkbox to their registration form for a request for a cwa-compatible QR code! 🚀
I got a card with the phone number of their hotline, and the QR code of my sample ID (the lab is Eurofins).
I know that this QR code is not compatible to cwa, but I pretended to be the average user, and tried to scan it with cwa, in the expectation to see the error message.
So I went through all these dialogs of cwa; but finally it did no scan and no error message.
Note: the QR code is very small. Maybe the scanner didn't even detect / focus it correctly. But as an "average user" I would now go away and tell all my friends that cwa QR code scanning just does not work.
Suggested Enhancement

Additionally to the "autoscan" that was never triggered in my case, a button to force a scan. You can then give error messages with possible reasons (bad lighting / incompatible QR code system / ...) and/or direct the user to a FAQ page which explains more details (e.g. how a correct / cwa-compatible QR code should look like).
Expected Benefits

Less confusion on user side. Give them the opportunity to do the first steps of trouble-shooting.

@ndegendogo
Just as a sanity test I tried scanning a QR code using CWA for something completely unrelated and CWA gave me an error message. In other words, it recognized that it was a QR code, but not one which could be used by CWA.
Did you try scanning your non-CWA code with a generic QR scanner? Was it accepted and scanned by your mobile device? Are you using iOS or Android?

This suggestion overlaps the existing request:
"Improve response to scanning non-CWA lab QR code" #343

@MikeMcC399

Did you try scanning your non-CWA code with a generic QR scanner? Was it accepted and scanned by your mobile device?

Good point, I'll try this. And I agree that this also will be one of the first steps of trouble-shooting that the user should try.

Are you using iOS or Android?

cwa 1.12.1 / iOS 14.2 / iPhone 8.
I remember that end of October I tried to scan a similar QR code with cwa, and got an error message like "bad lighting". Same device, but I don't remember the cwa version nor the iOS version.

@ndegendogo
You could also try scanning a dummy (non-CWA) QR code that I posted in https://github.com/corona-warn-app/cwa-wishlist/issues/343

@MikeMcC399 Bingo!
It seems that my 'wrong' code is not even a QR code (is this possible? Are there maybe other types of codes?)
I tried to read it with a QR code scanning app, and did not succeed (tried forever).
Whereas the code you posted above was read immediately by the QR code app, and produced an error message in cwa.
By the way, I noticed that a similar "code" appears sometimes on my letters; not sure if that is the replacement for a stamp, or an encoding of the address for automatted processing.

@ndegendogo

It seems that my 'wrong' code is not even a QR code (is this possible? Are there maybe other types of codes?)

There are many types of 2-D barcodes (see https://en.wikipedia.org/wiki/Barcode#Matrix_(2D)_barcodes) and QR is just one type.

I tried to read it with a QR code scanning app, and did not succeed (tried forever).
Whereas the code you posted above was read immediately by the QR code app, and produced an error message in cwa.

So your experiment suggests that the code you thought was a QR code, was not in fact coded in QR format. In that case I don't think that there is any reasonable enhancement which could be done to the CWA app to cover this case.

By the way, I noticed that a similar "code" appears sometimes on my letters; not sure if that is the replacement for a stamp, or an encoding of the address for automatted processing.

According to https://www.deutschepost.de/de/f/frankierung/matrixcode.html the Deutsche Post uses Matrixcode, but I think this is a little off topic 🙂 !

@MikeMcC399 it looks like this

And, yes, I agree that this is not any issue for cwa.
Any trouble-shooting user would find out fast that this code does not even scan with a 'generic' QR code scanner.

Closing


feat(Mobile Menu Variants): global header mobile

Overview

cowritten by @katiezutter
Created the AppHeaderMobile
Modified AppHeaderMainMenuMobile to be able to render the profile dropdown, and added the search component/functionality to it
Add variants for the different mobile headers (ex anonymous, free, pro)
Some code clean up
Updated stories + added mock data to be shared across the many stories requiring AppHeaderItems
Added render props for mobile search + notifications
Fixed mobile menu accessibility bug as well : https://codecademy.atlassian.net/browse/EGG-507 @jcenglish tagging you to take a look at the mobile menu from an a11y angle!
*please note we have tickets for design check + documentation polishing
Testing Instructions!

Visit preview link
Check out the AppHeaderMainMenu story
Check out the AppHeaderMobile story
Check out the Global Navigation story & toggle your screen between mobile & desktop and see that the header changes from the mobile version to the desktop version!
Check using voice over or by tabbing through that when the mobile menu is open, you cannot tab through or scroll through content behind the mobile menu

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: EGG-744

[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.27-alpha.8f6bc6.0@codecademy/gamut-labs@9.1.1-alpha.8f6bc6.0@codecademy/gamut-styles@7.7.3-alpha.8f6bc6.0@codecademy/gamut-system@0.2.4-alpha.8f6bc6.0@codecademy/gamut@21.2.4-alpha.8f6bc6.0@codecademy/markdown-overrides@0.4.7-alpha.8f6bc6.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601cc5105f91d456057bcd7d--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.27-alpha.c20769.0@codecademy/gamut-labs@9.1.1-alpha.c20769.0@codecademy/gamut-styles@7.7.3-alpha.c20769.0@codecademy/gamut-system@0.2.4-alpha.c20769.0@codecademy/gamut@21.2.4-alpha.c20769.0@codecademy/markdown-overrides@0.4.7-alpha.c20769.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601cc920bf0a364d08eb067a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.27-alpha.071a7f.0@codecademy/gamut-labs@9.1.1-alpha.071a7f.0@codecademy/gamut-styles@7.7.3-alpha.071a7f.0@codecademy/gamut-system@0.2.4-alpha.071a7f.0@codecademy/gamut@21.2.4-alpha.071a7f.0@codecademy/markdown-overrides@0.4.7-alpha.071a7f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601cd879b9896f61c44c40e8--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.27-alpha.be2ccc.0@codecademy/gamut-labs@9.1.1-alpha.be2ccc.0@codecademy/gamut-styles@7.7.3-alpha.be2ccc.0@codecademy/gamut-system@0.2.4-alpha.be2ccc.0@codecademy/gamut@21.2.4-alpha.be2ccc.0@codecademy/markdown-overrides@0.4.7-alpha.be2ccc.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601cdef05610f96e974b1bf4--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.f1e587.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601cea6ab9896f7df54c3dfb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.101052.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601d5e635610f90ae44b1abb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.92a31f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601d634f3966b2fbe006bd92--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://601d693bbcf6cd0b8601c9a0--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.cead50.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.cdce4e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601d71dd016eb7126400af12--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.61e0c5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601d8c1cbf0a363000eb1be6--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.a4bcd4.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601d96988bacca36f333007c--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.5397f5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021846565a09d00fd338c79--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.1d9f53.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021887c06dd760087824784--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.6fa21b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021949ab3a45c19e6ee99c3--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.1.1-alpha.5aefd8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021970351def81678d26f1d--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.5-alpha.230089.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021ac522a132f0bc61f2e83--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.5-alpha.7c1f39.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6021be9f7574fa1cdcd2fd2a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.5-alpha.68658a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6022eb13792a0a139d98a879--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.5-alpha.70dcc1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6022f9bd0969df20f2f9dee9--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.0f7aff.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6023ecb5a7709d41395fbd63--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.00b6ba.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6023f354c2b7b746b60496b4--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.32c4bc.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://602401dbf5f40f55ea95291a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.f454d9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6024037bd4ef077434ef1ff5--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.e496da.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://602405c001045c6fc55dc8b9--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.cc05fe.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6024139603fd9e0150d28e94--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.10-alpha.ad68f8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://602421236a42611210f49493--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@9.2.13-alpha.87efd9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://602452a78f4cb04ab5e1cd3f--gamut-preview.netlify.appDeploy Logs


output: Summary section has K8s Info

Merrily dumping more info here in the Summary section!

Hm, not totally sure how to fix this test failure in CI...
go vet -all -printfuncs=Verbosef,Infof,Debugf ./...
! grep --include=\*.go -rn . -e '^[^/].*defer [^ ]*EndPipeline(' # linting for improperly deferred EndPipeline calls; should be in closure, i.e. `defer func() { ...EndPipeline(err) }()`
errcheck -ignoretests -ignoregenerated ./...
internal/engine/upper.go:81:10:	s.Gather(services)
Makefile:32: recipe for target 'errcheck' failed
make: *** [errcheck] Error 1
Exited with code 2

Don't seem to see this error when I run this locally
go vet -all -printfuncs=Verbosef,Infof,Debugf ./...

Did I do something to affect EndPipeline?
I don't see any error in my IDE for s.Gather(services)...


Remove go fmt and vendor from binary build scripts

Bump version of goreleaser to latest

/cherry-pick v0.35.x

/cherry-pick v0.36.x