distributed-systems

Currently many more Python projects like dask and optuna are using Python type hints. With the Python package of xgboost gaining more and more features, we should also adopt mypy as a safe guard against some type errors and for better code documentation.

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

Is your feature request related to a problem? Please describe.

I'd like to be able to debug cadence's space usage by breaking down the size of history events by workflow type. But currently I cannot.

Proposed Solution

Proposed by @longquanzheng in the cadence slack: track a historySize in ES so we can query it for aggregation.

Additional context

https://uber-cadence.sl

Add checks, similar to in RenameMaterializedViewTask, that the target table or view or materialized view does not exist in the RenameTableTask and RenameViewTask

Describe the bug
The IMap.get() call will be blocked forever when a com.datastax.oss.driver.api.core.NoNodeAvailableException is thrown from the MapStore.

Setup:
Hazelcast v5.1.1
Cassandra SDK v4.14.1
Client-server setup
Read through cache, Cassandra DB gets called on a cache miss.

Test scenario: Read through cache, Cassandra server is down:

We tested the scenario whe

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Need to fix this TODO in the code:

         // TODO: we need to consider adding execution time to mutable state
	// For now execution time will be calculated based on start time and cron schedule/retry policy
	// each time DescribeWorkflowExecution is called.

https://github.com/temporalio/temporal/blob/master/service/history/historyEngine.go#L1184

Describe the bug
certain pods are missing "standard" labels which are useful for certain scenarios:

app.kubernetes.io/name
app.kubernetes.io/instance

To Reproduce
Steps to reproduce the behaviour:

1. Deploy longhorn
2. Check labels

default labels are missing on:

all csi-.* pods
engine-image
instance-manager
longhorn-csi-plugin

Expected behavior
app.kubernetes.io