SE-Notes | Notes for UW Software Engineering

For some reason I am unable to build my project. Yesterday everything worked fine, looking at https://firebase.google.com/support/release-notes/android#update_-_april_02_2019 there is a critical update from 5/11/21.

I tried to change the minSdkVersion as suggested but still no resolution.

This is the error:

When asserting that a field is definitely initialized in a class, what’s the difference between ! (exclamation point, definite assignment assertion) and the declare modifier?

The following code is an error in strict mode since TS doesn’t know for sure that the field has been initialized.

I'm currently working on a microservices application for my internship using Consul for service discovery and feign clients for communicating between the services. When we started working on the existing project which already was built using microservices, we upgraded Spring boot to 2.4.3 & cloud to 2020.0.1, so that we could make use of Java 15 to use records instead of normal classes for dtos. The problem we have now is that, whenever we make a call to a composite service, that will try to retrieve data from multiple services (for example users and teams service), that we get the following stacktrace:

We are using Azure Pipelines (azure-pipelines.yml) to automate ci/cd. Part of our configuration completes the versioning of our project for publishing to Azure Artifacts. We're also trying to configure this to update the existing version number in package.json without triggering a new pipeline in Azure DevOps.

This is the relevant section for our azure-pipelines.yml file:

I want to create a Typescript Type for an array of objects. In this array of objects, I require only one object to have a property set to true.

You can probably solve it just with this typescript example, but I will provide a long and detailed explanation.

Let's say (just an example!) I want to recreate a tag (or a dropdown list). My custom select has two have at least two options and I always want to have only one object to be active. I have three models: abstract class SimpleDropDownListElement { constructor(public label: string, public value: any) {} } class DropdownListElement extends SimpleDropDownListElement { constructor(public label: string, public value: any, public active?: false) { super(label, value); } } class DropdownActiveListElement extends SimpleDropDownListElement { active = true; constructor(public label: string, public value: any) { super(label, value); } } I want to have an array with at least one (or more) DropdownListElement(s) and one (always one - e.g. never 0 or 2+) DropdownActiveListElement. Any order (object with active set to true can be everywhere in the array). So my idea was to create a type like this: type DropDownOptionsArray = [DropdownActiveListElement, DropdownListElement, ...Array]; And that works, however, I need to have the object with the active property set to true as the first element of my array. So my idea was to reverse the array (not very smart), but I still get problems if the array holds more than 3 values. type Reverse = Tuple extends [infer A, ...infer B]? [...Reverse, A] : []; const dropInvertedWithInvertedType: Reverse = [new DropdownListElement('b', 'b'), new DropdownActiveListElement('a', 'a')]; const dropInvertedWithInvertedType1: Reverse = [new DropdownListElement('b', 'b'), new DropdownActiveListElement('a', 'a'), new DropdownListElement('b', 'b')]; // errors Then I started to go crazy with rest elements (hoping for TS v4 to help me with some magic): type DropDownOptionsArray = [...[DropdownActiveListElement], ...Array, ...Array]; // OK const twoEntries: DropDownOptionsArray = [new DropdownActiveListElement('a', 'a'), new DropdownListElement('b', 'b')]; const fourEntries: DropDownOptionsArray = [new DropdownActiveListElement('a', 'a'), new DropdownListElement('b', 'b'), new DropdownListElement('b', 'b'), new DropdownListElement('b', 'b')]; // should not error - but errors const twoEntriesRandomPos: DropDownOptionsArray = [new DropdownListElement('b', 'b'), new DropdownActiveListElement('a', 'a'), new DropdownListElement('b', 'b')]; const twoEntriesRandomPos: DropDownOptionsArray = [new DropdownListElement('b', 'b'), new DropdownListElement('b', 'b'), new DropdownActiveListElement('a', 'a')]; // should error const twoActiveEntries: DropDownOptionsArray = [new DropdownActiveListElement('a', 'a'), new DropdownListElement('b', 'b'), new DropdownActiveListElement('a', 'a')]; const noActiveEntry : DropDownOptionsArray = [new DropdownListElement('b', 'b')]; // should have a different error Writing overloads verbosely is not feasible, we could have an array of 20+ elements. To summarize, I would need this Type: array of objects holds at least two or more objects only one object has to have property active = true (all other objects may have active = false) the object with property active = true can be placed at any index in the array (from index 0 to index array.length - 1 ) Thank you!!

Windows Subsystem for Linux 2 is great tool, but has some issues as it's still a work in progress. I'm not on Insiders Program, so I don't get newest builds. I need to deal with some memory issues which are supposed to be fixed already, but I can't figure out if I already have required build or do I need to do some upgrading or is it available only for Insiders at the moment.

My Windows build is 19042.985 (v.20H2)

On Settings -> Apps there's WSL described with 4.19.104

So which build am I using?

Maven blocks external HTTP repositories by default since version 3.8.1 (see https://maven.apache.org/docs/3.8.1/release-notes.html)

Is there a way to disable that or to exempt a repository from this rule?

I've recently updated GKE cluster used in our project to version 1.18.16-gke.1200. One of the features we've been looking forward to were the startup probes. According to the overview of feature gates on Kubernetes' site, startup probes entered Beta stage in version 1.18 of Kubernetes and should be enabled by default, unless explicitly disabled in kubelet configuration. On the 1.18 cluster deployed with minikube the Deployment has its startup probes discovered properly:

On the GKE 1.18 cluster there is no mention of the probe:

Both Deployments have the API version apps/v1 and have the same probe configuration, but the startup probe one is ignored by GKE.

I've executed kubectl cluster-info dump against the GKE cluster to determine the parameters of the --feature-gates flag of kubelet, if the StartupProbe wasn't disabled by Google for that version. However, the only feature gates information returned by the dump is the parameter of kube-proxy container, which looks as follows: --feature-gates=DynamicKubeletConfig=false,RotateKubeletServerCertificate=true. There is no mention of startup probes in the dump at all, which means that the probes should be enabled.

GKE release notes does not seem to mention startup probes anywhere, even in the entry about introducing version 1.20 where the probes entered GA, although the graduation of some other feature (RuntimeClass) is mentioned. Could it be that Google is preventing introduction of startup probes in GKE for some reason? Is there any other way to enable startup probes for version 1.18 of GKE? I'm not using alpha cluster and the probes are not an alpha feature anyway anymore.

I am using Docker Desktop for Mac.

Since version 3.3.0 and with 3.3.1 I cannot connect to altssh.gitlab.com on port 443 any more whereas 3.2.2 and earlier work.

So, these commands both work in 3.2.2 (I downgraded and verified):