Utility to enforce coordinate order

As an IMPROVER developer, I want a single utility that consolidates existing functionality that orders coordinates so that I can easily pass a cube into the utility and be confident that the resulting cube has coordinates in the correct order.
Related issues: #209, #166, #236
Existing utilities:

Investigate the make_stat_coordinate_first method in #236.
Investigate the ensure_dimension_is_the_zeroth_dimension function within ensemble_calibration_utilities.py
Investigate check_cube_coordinates method.

Things to consider:

Order of preference for realization, percentiles, thresholds. Note that there can be both realizations and percentiles on a cube.
Vertical coordinates: height, pressure.
Time.
Equal preference for projection_x_coordinate, longitude and grid_longitude.
Equal preference for projection_y_coordinate, latitude and grid_latitude.

This utility will be extended in the future, as use cases emerge.
Acceptance criteria:

Make sure that the coordinate ordering follows the agreed temporary conventions for probabilistic data.
Identify use cases for the existing utilities and identify whether this use case can be served by a single utility or that there is a requirement for multiple utilities.
Consolidate existing utilities, if possible.
Unit tests.

Use case:
In circular_kernel.py, there is a section of code that reorders the resulting cube. This could be factored out and potentially generalised, as at the moment, it is hard-coded to use the percentiles_over_neighbourhood coordinate. There is some similar functionality existing in check_cube_coordinates for modifying coordinates within an output cube to match the coordinates within the input cube. However, the function suggested in this issue would order the coordinates within an output cube without the need for an input cube.

Work completed.


[5.1] Fix bounds check in bridged ASCII String comparison 5.1

Cherry-pick of https://github.com/apple/swift/pull/24457
Fixes rdar://problem/50407214

@swift-ci please test

@Catfish-Man - do I detect a reference to Dollhouse?  if so, amazing!

Indeed! Though I honestly forget how the pun was supposed to work semantically, it's been long enough since I made the original branch 😅

Something about NSString's indexes being a two byte stride or something like that

Branch names don't go in the title, silly github


Note fetch error

V3 is not supported by Homebridge.
Need an update of the NPT package

Seems to work on version 1.8.3 with updated HomeBridge Pi Image, Node and NPM


v0.7.1_18:Color change is implemented but color of the scale remains unchanged

SEVERITY: Minor
MODULE: Bubble chart
Platform: Nexus 9 (5.0.1) / Chrome 45.0
RELEASE: v0.7.1
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.7.1/preview/mountainchart.html
Bubble chart will be loaded
Click “Colors”
Click first dropdown
Select “Time”
Change the color of the scale
Note that the color change is implemented but color of the scale remains unchanged

ACTUAL RESULTS:
Color change is implemented but color of the scale remains unchanged
EXPECTED RESULTS:
Color of the scale should be changed according to the implemented changed color. It should not remain constant
SCREENSHOT:

Already fixed since it was reported


Support flat config

With a recent change git::configs was added.
With this follow-up a flat configuration like this is now also supported:
git::configs:
  user.name: 'test'
  user.email<EMAIL_ADDRESS>

:+1:

Any idea why the build doesn't start?

The build is fine, any objection to merging this? :-)

Ping. :-)

I would appreciate comments whether this could be merged or something is wrong.

Thanks for the contribution @mbrodala! Looks good!

Awesome, thanks a lot. :-)


[FLINK-2564] Failing Test: RandomSamplerTest

As discussed in here, it's a balance between accurate verification and failure-positive result. As this failure and KS test failure happens more often than expected, we should expand the verification boundary which would reduce the fail-positive case to an acceptable level.
With this PR, the KS test and fraction verification never fail after tens of thousands executions in my local environment. @tillrohrmann , @chiwanpark .

I've tested with increased count of sources and count of samples. It seems okay but I'm not sure which approach is more proper.
https://travis-ci.org/chiwanpark/flink/builds/76923033

@chiwanpark , it may need thousands of times' execution to verify, as the failure possibility is quite low. Besides, how many times do you increased count of sources and count of samples, the tests of reservoir samplers are executed on seconds level, so be careful about the unit test cost as well.

Here is my changes: chiwanpark@0699411
The changes are tested in my local environment about 200 hundred times and also tested in Travis-CI 10 times.

I think both ways (increasing the number of times we sample as well as softening the accuracy thresholds) will improve the test stability. However, as @ChengXiangLi pointed out, increasing the number of samplings and the sample size, will also increase the unit test costs (even though it should be in the range of fractions of a second). Maybe we can also combine both approaches.
Other than that, LGTM.

Merge part of chiwanpark's change, add the execute time for fraction sample from 5 to 20. As changing input size from 10000 to 50000 would increase the unit test costs from 15s to 74s in my local environment, it seems too much for a unit test, so i didn't merge this part.

Looks good to merge.

Merging....

Are you still merging @chiwanpark? Doesn't seem that the commit made it to the master.

@tillrohrmann Sorry for late. I forgot push the commit to apache master. The commit is pushed.


Updated EKS-D versions for 1.19, 1.20, and 1.21

Issue #, if available:
closes https://github.com/aws/eks-distro/issues/1150
Description of changes:
Base image updates. THIS IS THE LAST 1.19 RELEASE!

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


upload 3d files to thingiverse

Not an issue, because there is no point in having duplicates that have to be updated every time something gets changed. We don't have infinite time (that you apparently have) for useless stuff like that...

No description given.


List Promotions

As a promotion manager,
I need the ability to list all current promotions,
So that I can see an overview of all active discounts and sales.
Assumptions:
The promotions will be stored in a PostgreSQL database.
Each promotion includes details like type (e.g., "Buy 1 Get 1 Free", "20% Off"), applicable products, and duration.
Acceptance Criteria:
Given there are multiple promotions in the database,
When I request to list all promotions,
Then I should see a list of all active promotions with their details.
As a promotion user,
I need the ability to check promotion of the specified product or the products with greater discount
So that I can make the decision to purchase or not
Acceptance Criteria:
Given there are multiple promotions in the database,
When I request to search a specified product or a range of discount,
Then I should see a list of all active promotions with their details.


Handling several categories

Issue Fixed #
None
Proposed Changes

You can put several categories for each post;
The script generating categories is updated to check all the categories of each post;
The post mentioning the number of categories for each post has been modified.

I believe that the case where a user would list a post under multiple categories is limited. Let's not take this change in in the sake of trying to satisfy the common cases instead of trying to satisfy every possible scenario, leading to a complicated codebase 😄

Yeah I saw that Jekyll users mostly used one category for each post.
I'll keep this feature for my personal use ;)

Think we agreed on not merging this PR


Suggestion: add generic tagged objects to core library

A lot of suggestions have been around nominal typing. A fair share of those are made by people who are pleasantly surprised to discover the tagged interface method. I propose adding @RyanCavanaugh's elegant generic solution to the library (and the documentation!), to help users discover this great feature. It would also avoid every popular Typescript library eventually adding their own version of this. I know I was surprised to find it and I would have loved to discover it sooner.
type Branded<T, U> = T & { [Symbol.species]: U };

Example use:
// UUID or a symbol, once symbol literal types are supported
type OrderUUID = "d3a8e9b5-07c2-4a2d-a245-8a5908826b0f";

// Tagged Alias
type OrderID = Branded<string, OrderUUID>;

It may be useful to split this into a type and an interface, though this may make it less elegant (and thus overreaching for inclusion in the core library):
interface Specified<T> {
    [Symbol.species]: T;
}

type Branded<T, U> = T & Specified<U>;

It does allow for more advanced uses of this system, such as runtime type checking:
// Is there a more elegant way to get a string literal type?
const OrderUUID = "d3a8e9b5-07c2-4a2d-a245-8a5908826b0f" as "d3a8e9b5-07c2-4a2d-a245-8a5908826b0f";

// Tagged Class
class Order implements Specified<typeof OrderUUID> {
    [Symbol.species] = "d3a8e9b5-07c2-4a2d-a245-8a5908826b0f" as typeof OrderUUID;
}

function isOrder(arg: any): arg is Order {
    return OrderUUID in arg;
}

The naming might need some discussion.

We've kicked this idea around a bunch of times and have opted to look into built-in solutions instead of adding types to the lib.


Contribute a change in docs

Hi. I would like to contribute some doc changes but I couldn't find where are they located in the docs directory. I want to contribute to examples where we have an option for Java and Kotlin. Currently, we have to select language for each example. Java is the default as I could see but if you are a Kotlin user, you have to switch for each of the examples. I want to check if that is possible to switch all tabs together and would love to contribute if possible.

Hi @abhilashmandaliya, the document you are looking for is this:
https://github.com/remkop/picocli/blob/main/docs/index.adoc
Documentation about the AsciiDoc format can be found here: https://asciidoctor.org/

Hi @abhilashmandaliya, the document you are looking for (the main picocli user manual) is this file: https://github.com/remkop/picocli/blob/main/docs/index.adoc
Documentation about the AsciiDoc format can be found here: https://asciidoctor.org/

Thanks a lot, @remkop. I will look into it and see if I can do the useful.


Updated index.html

-changed codemirro linksr to latest release
-removed redundant css and js references that were preventing the code mirror addons and linting from working.

Thank you!


[PROBLEM] DeepSpeedChat  Create HF Model FOR LLAMA Token ID Question

Hello, I wish you good work.

I got stuck at a point here and wanted to get an answer from you. When we first set up the tokenizer structure, these were our token information for the OPT Models.

OPT TOKEN ID:
{'bos_token': '</s>',
 'eos_token': '</s>',
 'unk_token': '</s>',
 'pad_token': '</s>'}

And then in "create_hf_model" when calling the model;

model.config.eos_token_id = tokenizer.eos_token_id
model.config.pad_token_id = model.config.eos_token_id

as we equate.

But as far as I normally see in LLama Models, pad_token is not included and we add it later, in the "load_hf_tokenizer" section.

In short;

LLAMA TOKEN ID BEFORE ADD PAD TOKEN ID:
{'bos_token': '<s>',
'eos_token': '</s>',
'unk_token': '<unk>'}

...
tokenizer.add_special_tokens({"pad_token" : "[PAD]"})
.....

But while we are calling the LLAMA model in the "create_hf_model" section in this model section, it doesn't seem to apply our change in the pad_token section.

model.config.eos_token_id = tokenizer.eos_token_id ----> </s>
model.config.pad_token_id = model.config.eos_token_id --> </s>

Isn't that what it should be?

as model.config.pad_token_id = tokenizer.pad_token_id--> [PAD]
doesn't it need to be set?

Can you explain if there is a different approach for the MODEL TOKEN ID and TOKENIZER ID?

@awan-10

@syngokhan - there's no need to focus on pad token, it can be anything. the pad embedding will never affect the output.


add php7.4

add php7.4 image.
i am unsure about the jsonnet change, guess someone with push rights need to push the image and then modify the tag to the sha256.
please let me know if you need me to change something.

Thanks for the update @hjanuschka! I have updated the PHP images and triggered the tests.

@hjanuschka it seems that the test for PHP 7.4 is failing. Can you check it?

@andresmgot i am sorry, totally forgot to wait for CI.
i think i fixed it, by rm /etc/nginx/sites-enabled/default in the 7.4 image, i can run it locally, could you please update the image hashes and re-trigger the ci? (anyway i can run ci with custom built image?)

Thanks! Updated the images.

anyway i can run ci with custom built image?

Well, you can use your personal DockerHub to temporarily push images there, I can later on push them to the kubeless repo when everything is ready.

Everything good now, thanks!

hooray! thx!  keep up the great project!


aks-periscope do not deploy Pods for Windows Nodes

Hello,
We are trying to collect logs from our Windows Nodes in AKS Cluster. We deployed aks-periscope from Azure Cloud-Shell but it worked only for Linux nodes, as in our Storage found only those folders. Although there was a DaemonSet for Windows Nodes, no Pods has been started for this one. Could you please let me know how we should troubleshoot those issues?
Will mention that we are using AKS Cluster integrated with AAD.
If need any logs from resources, we can provide as requested.
Thank you

Thank you so much @OvidiuBorlean for reporting this, can you please share how you are trying to deploy the tool? or replication steps for this issue please? I tried for a windows node and it worked so I thought I will ask. The windows image reference is: mcr.microsoft.com/aks/periscope-win:0.0.9 Thanks ☕ 🙏 cc: @peterbom as fyi.

Hi @OvidiuBorlean - were you using the az aks kollect command to deploy Periscope? There were some changes made to the CLI tool to support the latest Periscope version, and I'm guessing those haven't been released yet. I'll have to do more research to understand how/when the aks-preview extension gets released... @Tatsinnit - do you know anything about this?
In the meantime, you can try using the VS Code AKS extension to deploy Periscope. We have released that with the changes to support the latest Periscope release.

As for troubleshooting, the following commands might be helpful:
# Check the desired/ready/available pods for the DaemonSets (there should be two)
kubectl get ds -n aks-periscope

# Get more detail about the Windows DaemonSet
kubectl describe ds -n aks-periscope aks-periscope-win

# Check the statuses of all the Periscope pods
kubectl get po -n aks-periscope

# In case a pod is stuck in Pending (or some other not ready state), check the events at the bottom of:
kubectl describe po -n aks-periscope <podname>

Hi everyone,
Thank you very much for your fast reply on this thread. This actually happened for one of our customer when tried to collect the Windows logs for troubleshooting process. I have done a repro on a AKS test cluster with AAD integration and it works just fine, with both admin user configured for cluster access and AAD user. Will try to get some more logs during the deployment for the affected cluster, maybe there is some particular configuration that is doing this. Thank you for your support

Thanks you @OvidiuBorlean , glad it helped! Since it’s is working will it be cool if I close this issue, as no further action is in need? Kind regards!

Thanks all, @peterbom Here are the responses from the commands you suggested after running aks collect from cloud shell bash terminal:
Check the desired/ready/available pods for the DaemonSets (there should be two)
kubectl get ds -n aks-periscope
NAME                DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR              AGE
aks-periscope       2         2         2       2            2           kubernetes.io/os=linux     19m
aks-periscope-win   0         0         0       0            0           kubernetes.io/os=windows   19m
Get more detail about the Windows DaemonSet
kubectl describe ds -n aks-periscope aks-periscope-win
Name:           aks-periscope-win
Selector:       app=aks-periscope
Node-Selector:  kubernetes.io/os=windows
Labels:         app=aks-periscope
Annotations:    deprecated.daemonset.template.generation: 1
Desired Number of Nodes Scheduled: 0
Current Number of Nodes Scheduled: 0
Number of Nodes Scheduled with Up-to-date Pods: 0
Number of Nodes Scheduled with Available Pods: 0
Number of Nodes Misscheduled: 0
Pods Status:  0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
Labels:           app=aks-periscope
Service Account:  aks-periscope-service-account
Containers:
aks-periscope:
Image:      mcr.microsoft.com/aks/periscope-win:0.0.9
Port:
Host Port:
Limits:
cpu:     1
memory:  2000Mi
Requests:
cpu:     250m
memory:  500Mi
Environment Variables from:
diagnostic-config  ConfigMap  Optional: false
azureblob-secret   Secret     Optional: false
Environment:
HOST_NODE_NAME:   (v1:spec.nodeName)
Mounts:
/AzureData from azuredata (rw)
/k from k (rw)
Volumes:
k:
Type:          HostPath (bare host directory volume)
Path:          /k
HostPathType:
azuredata:
Type:          HostPath (bare host directory volume)
Path:          /AzureData
HostPathType:
Events:
Check the statuses of all the Periscope pods
kubectl get po -n aks-periscope
NAME                  READY   STATUS    RESTARTS   AGE
aks-periscope-cqxqx   1/1     Running   0          20m
aks-periscope-fz2rh   1/1     Running   0          20m
In case a pod is stuck in Pending (or some other not ready state), check the events at the bottom of:
kubectl describe po -n aks-periscope
N/A

Thanks for the extra info, @philshur and @OvidiuBorlean!
Given that the 'desired' pod count is 0, that suggests your cluster doesn't think it has any Windows nodes. Or at least there aren't any matching the selector kubernetes.io/os=windows that Kubernetes thinks it should schedule pods to.
Next things I can think of to look at:
# Check the AKS node pools (there should be one or more with `OsType` == `Windows`). Do they have `ProvisioningState` == `Succeeded`?
az aks nodepool list -g <resource_group> --cluster-name <aks_cluster> -o table

# Check the nodes - do any of them start with `aks<windows_node_pool_name>`?
kubectl get no

# If there are nodes in a Windows node pool which are successfully provisioned, check they all match the `selector` value:
kubectl get no --selector kubernetes.io/os=windows

# If there are still nodes that match that selector, I have no idea why they wouldn't be getting any pods! But if that's the case, we might get *some* insight from:
kubectl describe no <windows_node>

Thanks @peterbom
These are the responses I get from the above:
Check the AKS node pools (there should be one or more with OsType == Windows). Do they have ProvisioningState == Succeeded?
az aks nodepool list -g <resource_group> --cluster-name <aks_cluster> -o table
Name       OsType    VmSize           Count    MaxPods    ProvisioningState    Mode

nodepool1  Linux     Standard_D4s_v4  2        250        Succeeded            System
winle      Windows   Standard_E8s_v5  0        250        Succeeded            User
winse      Windows   Standard_E4s_v5  1        250        Succeeded            User
Check the nodes - do any of them start with aks<windows_node_pool_name>?
kubectl get no
NAME                                STATUS   ROLES   AGE   VERSION
aks-nodepool1-19583413-vmss000000   Ready    agent   11d   v1.21.7
aks-nodepool1-19583413-vmss000001   Ready    agent   11d   v1.21.7
akswinse000000                      Ready    agent   11d   v1.21.7
If there are nodes in a Windows node pool which are successfully provisioned, check they all match the selector value:
kubectl get no --selector kubernetes.io/os=windows
NAME             STATUS   ROLES   AGE   VERSION
akswinse000000   Ready    agent   11d   v1.21.7
If there are still nodes that match that selector, I have no idea why they wouldn't be getting any pods! But if that's the case, we might get some insight from:
kubectl describe no <windows_node>
Name:               akswinse000000
Roles:              agent
Labels:             agentpool=winse
beta.kubernetes.io/arch=amd64
beta.kubernetes.io/instance-type=Standard_E4s_v5
beta.kubernetes.io/os=windows
failure-domain.beta.kubernetes.io/region=westus
failure-domain.beta.kubernetes.io/zone=0
kubernetes.azure.com/agentpool=winse
kubernetes.azure.com/cluster=MC_Kube-Experimental_starling-westus-experimental_westus
kubernetes.azure.com/kubelet-identity-client-id=
kubernetes.azure.com/mode=user
kubernetes.azure.com/node-image-version=AKSWindows-2019-17763.2803.220428
kubernetes.azure.com/role=agent
kubernetes.azure.com/storageprofile=managed
kubernetes.azure.com/storagetier=Premium_LRS
kubernetes.io/arch=amd64
kubernetes.io/hostname=akswinse000000
kubernetes.io/os=windows
kubernetes.io/role=agent
node-role.kubernetes.io/agent=
node.kubernetes.io/instance-type=Standard_E4s_v5
node.kubernetes.io/windows-build=10.0.17763
storageprofile=managed
storagetier=Premium_LRS
topology.disk.csi.azure.com/zone=
topology.kubernetes.io/region=westus
topology.kubernetes.io/zone=0
Annotations:        csi.volume.kubernetes.io/nodeid: {"disk.csi.azure.com":"akswinse000000","file.csi.azure.com":"akswinse000000"}
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Wed, 01 Jun 2022 15:35:39 +0100
Taints:             node.kubernetes.io/os=windows:NoSchedule
Unschedulable:      false
Lease:
HolderIdentity:  akswinse000000
AcquireTime:
RenewTime:       Mon, 13 Jun 2022 10:07:41 +0100
Conditions:
Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message

MemoryPressure   False   Mon, 13 Jun 2022 10:06:17 +0100   Tue, 07 Jun 2022 22:49:13 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
DiskPressure     False   Mon, 13 Jun 2022 10:06:17 +0100   Tue, 07 Jun 2022 22:49:13 +0100   KubeletHasNoDiskPressure     kubelet has no disk pressure
PIDPressure      False   Mon, 13 Jun 2022 10:06:17 +0100   Tue, 07 Jun 2022 22:49:13 +0100   KubeletHasSufficientPID      kubelet has sufficient PID available
Ready            True    Mon, 13 Jun 2022 10:06:17 +0100   Tue, 07 Jun 2022 22:49:13 +0100   KubeletReady                 kubelet is posting ready status
Addresses:
Hostname:    akswinse000000
InternalIP:  <IP_ADDRESS>
Capacity:
attachable-volumes-azure-disk:  16
cpu:                            4
ephemeral-storage:              267921404Ki
memory:                         33553972Ki
pods:                           250
Allocatable:
attachable-volumes-azure-disk:  16
cpu:                            3860m
ephemeral-storage:              267921404Ki
memory:                         27724340Ki
pods:                           250
System Info:
Machine ID:                 akswinse000000
System UUID:                16CCB378-693C-452D-B32E-C183430EB4AC
Boot ID:
Kernel Version:             10.0.17763.2803
OS Image:                   Windows Server 2019 Datacenter
Operating System:           windows
Architecture:               amd64
Container Runtime Version:  docker://20.10.9
Kubelet Version:            v1.21.7
Kube-Proxy Version:         v1.21.7
ProviderID:                   azure:///subscriptions/cf9fa274-ff0f-4ec4-be0b-4f6fea78a018/resourceGroups/mc_kube-experimental_starling-westus-experimental_westus/providers/Microsoft.Compute/virtualMachineScaleSets/akswinse/virtualMachines/0
Non-terminated Pods:          (3 in total)
Namespace                   Name                            CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE

kube-system                 csi-azuredisk-node-win-wmv8c    30m (0%)      0 (0%)      60Mi (0%)        800Mi (2%)     11d
kube-system                 csi-azurefile-node-win-b6fr9    30m (0%)      0 (0%)      60Mi (0%)        800Mi (2%)     3d21h
kube-system                 omsagent-win-zdcfs              500m (12%)    500m (12%)  600Mi (2%)       600Mi (2%)     3d21h
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource                       Requests    Limits

cpu                            560m (14%)  500m (12%)
memory                         720Mi (2%)  2200Mi (8%)
ephemeral-storage              0 (0%)      0 (0%)
attachable-volumes-azure-disk  0           0
Events:

@philshur - thank you for the extra info.
I think the issue is in the output from kubectl describe no, specifically this:
Taints: node.kubernetes.io/os=windows:NoSchedule

According to the kubernetes docs, no pods will be scheduled to the node, unless they have a corresponding toleration, which the Periscope pods don't have.
The question now is what to do about it. I assume the taint is there for a reason, and you can't simply remove it?
I'm not sure if our Periscope deployment should be specifying that toleration, and whether there would be any unintended consequences if we always did that. @Tatsinnit - we can discuss this and maybe create an issue?
In the meantime, it is possible to deploy Periscope manually by creating a kustomization.yaml file which I think we could use to set that toleration and see if we can get it to work that way. I'll have a try myself and post something here shortly.

@philshur - this works for me (with the taint applied to my Windows node):
# Set some variables for where you want the logs uploaded to:
sub_id=<storage_account_subscription_id>
stg_account=<storage_account_name>
blob_container=<desired_blob_container_name>

# Create a SAS for the storage account
sas_expiry=`date -u -d "60 minutes" '+%Y-%m-%dT%H:%MZ'`
sas=$(az storage account generate-sas \
    --account-name $stg_account \
    --subscription $sub_id \
    --permissions rwdlacup \
    --services b \
    --resource-types sco \
    --expiry $sas_expiry \
    -o tsv)

# Create a 'kustomization' folder to contain the Periscope resources to be deployed
mkdir ./periscope-deploy

# Create a YAML file to override the default deployment behaviour
cat <<EOF > ./periscope-deploy/kustomization.yaml
resources:
- https://github.com/azure/aks-periscope//deployment/base?ref=v0.9

patches:
- target:
    group: apps
    kind: DaemonSet
    name: aks-periscope-win
    version: v1
  patch: |-
    - op: add
      path: '/spec/template/spec/tolerations'
      value:
      - key: node.kubernetes.io/os
        operator: Equal
        value: windows
        effect: NoSchedule

images:
- name: periscope-linux
  newName: mcr.microsoft.com/aks/periscope
  newTag: "0.0.9"
- name: periscope-windows
  newName: mcr.microsoft.com/aks/periscope-win
  newTag: "0.0.9"

secretGenerator:
- name: azureblob-secret
  behavior: replace
  literals:
  - AZURE_BLOB_ACCOUNT_NAME=${stg_account}
  - AZURE_BLOB_SAS_KEY=?${sas}
  - AZURE_BLOB_CONTAINER_NAME=${blob_container}
EOF

# Deploy
kubectl apply -k ./periscope-deploy

After deploying, you should be able to see a pod for the Windows node by running kubectl get po -n aks-periscope. Assuming that runs, the data collected by Periscope should be available in the Azure Portal, by navigating to the storage account and blob container specified in the variables above.
If you do try this, let me know how you get on!

@peterbom thanks for your advice and quick responses!
That worked for me too, thanks again!

I'm not sure if our Periscope deployment should be specifying that toleration, and whether there would be any unintended consequences if we always did that.

I've started a discussion (#183) about this, and made a few initial notes that lean towards not changing our deployment. However, I have very little real-world Kubernetes experience, and would welcome any thoughts/corrections from folks in the field (@philshur, @OvidiuBorlean).

Nice, thank you so much @peterbom for creating the discussion here (https://github.com/Azure/aks-periscope/discussions/183) for any further improvements. Given the primary issue is resolved I will close this issue and move rest of ideas and discussion to discussion board. Thank you so much to @philshur, @OvidiuBorlean for reporting this and we have clarity in unblocking this for any other user if need be.


nginx module: update statsd, develkit, rtmp

Motivation for this change
nginx statsd module doesn't build, the zebrafishlabs github repo seems dead -- switch to a working one
update ngx_devel_kit and rtmp to fix mainline build
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[X] OS X
[X] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Thanks!


Build multiple tagged images per Dockerfile

As discussed with @creack, the goal of this PR is to allow a single Dockerfile to build multiple flavors of an image using the current build environment.  This is useful for:

Creating lightweight image layers that customize metadata (ENV, ENTRYPOINT, etc)
Adding layers to a base image from arbitrary points in the current build
Modeling Heroku-style process types as specified in a Procfile

Example Usage
A developer is creating a Dockerfile to deploy a web application.  The application has 3 main flavors of usage:

Run an interactive shell
Run a web server
Run a worker

With the TAG instruction, developers can create multiple tagged images for each flavor from a single Dockerfile:
FROM stackbrew/ubuntu:12.04
ENV DEFAULT value
TAG :latest

FROM :latest
ENV WEB 1
ENTRYPOINT ["/bin/echo", "web"]
TAG :web

FROM :latest
ENV WORKER 1
ENTRYPOINT ["/bin/echo", "worker"]
TAG :worker

Building the Dockerfile results in the following output:
# docker build -t gabrtv/test .
Uploading context 204.8 kB
Step 1 : FROM stackbrew/ubuntu:12.04
 ---> 4fc5ba8a5b33
Step 2 : ENV DEFAULT value
 ---> Running in 0787811a7674
 ---> e2e373ff1a73
Step 3 : TAG :latest
 ---> e2e373ff1a73
Step 4 : FROM :latest
 ---> e2e373ff1a73
Step 5 : ENV WEB 1
 ---> Running in 715022e443a5
 ---> be2cd6668a56
Step 6 : ENTRYPOINT ["/bin/echo", "web"]
 ---> Running in ba94a225079b
 ---> 09484a63e190
Step 7 : TAG :web
 ---> 09484a63e190
Step 8 : FROM :latest
 ---> e2e373ff1a73
Step 9 : ENV WORKER 1
 ---> Running in a0d0154804af
 ---> 76cb1d83b7bd
Step 10 : ENTRYPOINT ["/bin/echo", "worker"]
 ---> Running in f370e833e660
 ---> 2ff2d5c7942b
Step 11 : TAG :worker
 ---> 2ff2d5c7942b
Successfully built 2ff2d5c7942b

.. which results in the following new images:
# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
gabrtv/test         latest              e2e373ff1a73        38 seconds ago      93.66 MB
gabrtv/test         worker              2ff2d5c7942b        38 seconds ago      93.66 MB
gabrtv/test         web                 09484a63e190        38 seconds ago      93.66 MB

Playing with the images demonstrates their unique flavors:
# docker run -t -i gabrtv/test bash
root@3b527e5a0c8c:/# echo $DEFAULT
value

# docker run gabrtv/test:web
web

# docker run gabrtv/test:worker
worker

# docker run -entrypoint=/usr/bin/env gabrtv/test:worker
HOME=/
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=af87e9b3306e
DEFAULT=value
WORKER=1
container=lxc

The PR includes documentation, integration tests and should be backwards compatible.

:+1:


Is this adapter still maintained?

Please let us know wether you still plan to maintain this adapter.

yes

Thanjs for the info.
Please zry to fix / close issues especially the qustion relsted to release numbering.
Thabks a lot


[Improvement] Improve GravitinoCatalogManager close method

What would you like to be improved?
GravitinoCatalogManager's close method mixes static and volatile variables in a nonstatic method and that may cause issues. Correctly updating a static field from a non-static method can be tricky to get right and could easily lead to bugs if there are multiple threads.
How should we improve?
See if this can be improved to be more thread safe.

I created a PR(#3096) for this, could you take a look at it?

it's not supposed to work in the multi-thread environment, so I prefer no to change it.

Is the fact that it won't work in a multi-thread environment documented anywhere? That seems like an omission that a user would want to know about.

There is no document for this, maybe we could add some comment to the class file, WDYT?

See if this can be improved to be more thread safe.

Is there a need to support multi-threading? It currently does not support multi-threading.

Perhaps I'm misisng something, but I assume users expect this to support muti-threading.

I agree with Justin, we couldn't stop user/client (especially it is a flink connector) from using it in multi-threading, so the code should be robust, especially that is too complex to achieve.


GAVNOR-2206: M2Repo perspective don't filter pom.xml files.

http://github.com/droolsjbpm/guvnor/commit/2e26984a1


Cannot set parameter in SnapshotHook

By setting
hooks = [     dict(typename='SnapshotHook', interval=1, save_optim_flag=False, max_keep_ckpts=3), ]
I hope to keep only the last three checkpoints of weights. But it still saves weights, meta and optim checkpoints after all epochs. Could you help to solve this problem? It does not work as what it should be according to vedacore/hooks/snapshot.py.

This issue is caused by several minor mistakes in . and . I have fixed it. Perhaps pull request if required.


_include with _tag and _id produce missing results

Describe the bug
When using the include operator and also filtering the matches based on _tag and _id at the same time => expected included items are not returned
To Reproduce
Steps to reproduce the behavior:

ASSUMING there is only 1 tag in the db....or that both queries return just 1 tag so the tag wont change the results

find a match (patient for example) that has an include / revinclude item
consider the following query:
(id and tag to be changed to produce a valid match)
https://localhost:44348/Patient?_revinclude=Observation:subject&_id=186xxxa1c&_tag=774xxxce98

it might produce less items compared to this query:
https://localhost:44348/Patient?_revinclude=Observation:subject&_id=186xxxca1c
Expected behavior
both queries should produce the same results
Actual behavior
the query with both _tag and _id produce less results
when debugging this behavior I've noticed that adding _tag completely changes the generated query which in turn has an affect on the included statement.

Current assumption (not verified yet) is that since the filtering is now done only at the end (bottom) of the query, non relevant includes are passing the top / asc sorting / filtering and relevant includes get dropped, later those are filtered while the relevant includes are already dropped...

Addressed by #1273


Link to IDL pictogram page on Carbon

I think it would be helpful if Carbon pictogram page had a link to the one on IDL that explains color usage and shading.
https://www.ibm.com/design/language/elements/pictograms/design#color

We link to that page in the Contribute tab


Move dependency management to poetry

Is your feature request related to a problem? Please describe.
Move the dependency management to poetry
Describe the solution you'd like
requirements.txt replaced with poetry files
Additional context
This can fix platform issues and help pin the dependencies

not currently possible with poetry as tensorflow built version only available on conda


Accept UTC time for departure and arrival

Is your feature request related to a problem? Please describe.
The current API accepts a string for the flight arrival and departure times. The current spec defines this as 7:30 am.
Describe the solution you'd like
This requirement means that data that usually comes into an app as UTC requires conversion prior to entering the string into the element.
The element should be updated to require a UTC time code versus a converted string. This will ensure consistency of entered data into the element and reduce the dependency on the user to pre-convert time prior to use with the element.
Exit criteria
The element's departure and arrival API will only accept a UTC time code as a value and will use internal logic to convert to a standard display of time.

It would be great to have a feature to toggle between local time, relative time, and military time as well - some standard format strings could probably be decided on.

It would be great to have a feature to toggle between local time, relative time, and military time as well - some standard format strings could probably be decided on.

I see what you are going for, but is that a feature people want? Relative time or a 24hr clock really seems like a reach. I can maybe see departure and arrival times in your time zone.

The scope of this issue was explored with the spike PR. After further review of data received from the FlightResultsAPI it was learned that the flight search team has a BFF that converts a lot of data to a simpler string for consumption in the custom element.
It was discussed that the data coming from the API is not of proprietary nature and others is no need to pre-process the data in a BFF. Therefore the following revision is suggested to update the departureTime and arrivalTime props to access the full datetime UTC code that comes from the API.
departureTime="2022-04-13T01:10:00-07:00"
arrivalTime="2022-04-13T12:30:00-04:00"

Getting this datetime UTC code also enables the element to address additional capabilities that were manually addressed in the current version. That being the daysChanged property. With this update, the element can easily calculate the days changed without that being pre-processed as well.
Additionally getting this data is required for the issue of SEO and structured data.  The departureTime and arrivalTime nodes require the date to be in its UTC format.


" setToolMode call for tool not available globally" error

Am adding anew custom tool to OHIF through an extenstion.
This works fine in dev mode ,
but when i build the extention and embed it in a web page using the script tag , the tool icon appears on the ohif tool bar ,but when i click on the tool ,i get the above error
and then
Unable to find tool "save-Tool" for enabledElement
here is the referenced source of the error from the browser console
 var globalTool = _index_js__WEBPACK_IMPORTED_MODULE_5__["default"].state.globalTools[toolName];

  if (!globalTool) {
    logger.warn("setToolMode call for tool not available globally: ".concat(toolName));
    return;
  }

Please review the latest code in the master branch. I am confident that this issue has been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing


Is there a way to upgrade the distro?

Im a bit newbie here but is there a way to upgrade without installing everything again? Since there is a new release now, and I just finished installing everything a few hours ago

There are no major changes in that release.
It just fixes bugs in running Windows binaries.
Updates are still in preparation.

The update still requires manual replacement of the script.

Although I can install everything again since I also doing something for learning but how exactly do you mean by that? Sorry really noob here. Is it easy to that myself?

i'm not sure if this works or not but try to install or move all the packages on arch1 to arch2

I've been using Archwsl on wsl1 for almost a year, and I just convert it to wsl2 last month. I wonder is there a way to upgrade the original Archwsl to Archwsl2 without reinstalling everything.


Alice's keys are 65 bytes

Alice's keys are 65 bytes because of a trailing linebreak character. It should be trimmed as well as admin's keys are.

Closed since pr is merged.


failure to clean up process

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/Pyro-3.16-py2.7.egg/Pyro/protocol.py", line 1126, in connectionHandler
    if self.getAdapter().handleConnection(conn, self):
  File "/usr/lib/python2.7/site-packages/Pyro-3.16-py2.7.egg/Pyro/protocol.py", line 836, in handleConnection
    ver,body,pflags = self.receiveMsg(conn)
  File "/usr/lib/python2.7/site-packages/Pyro-3.16-py2.7.egg/Pyro/protocol.py", line 633, in receiveMsg
    self.returnException(conn, ProtocolError(msg))
  File "/usr/lib/python2.7/site-packages/Pyro-3.16-py2.7.egg/Pyro/protocol.py", line 813, in returnException
    pic=Pyro.util.getXMLPickle('gnosis')
  File "/usr/lib/python2.7/site-packages/Pyro-3.16-py2.7.egg/Pyro/util.py", line 435, in getXMLPickle
    raise NotImplementedError('xml pickling implementation (%s) is not available' % impl)
NotImplementedError: xml pickling implementation (gnosis) is not available

Not the case in Pyro4. To be superseeded by: https://github.com/cmscaltech/fdtcp/issues/3


test: [M3-7315] - Add tests assgining VPCs during Linode creation flow

Description 📝
Add regression tests for assigning VPCs during Linode creation flow.
Major Changes 🔄

Add regression tests to assign a VPC when creating a Linode.

How to test 🧪
yarn cy:run -s "cypress/e2e/core/linodes/create-linode.spec.ts"

I had 3 tests fail for me:


Describe behavior ext. for SFENCE.VMA and HFENCE.VMA

addresses issue #77

LGTM. The description turned out to be bit more wordy than needed.

yeah can reduce it in the arc review stage.


Ghost Listing

I see a huge problem with the pattern suggested in this nft-storefront. And that is GhostListings.
There is nothing stopping a user from listing a NFT in two nft-storefronts. And when it is sold in one there is nothing that cleans up the other. Likewise a user can also manually withdraw an item from the collection they own without cleanup logic beeing called.
Are we sure using pointerns to a resource is a good idea here?

I just mentioned this in https://github.com/onflow/nft-storefront/issues/33 but i can mention it here again.
In practise with blocto bay and rarible I cannot list the same item twice. If i list it in rarible it shows up in blocto and the other way around.
How is a tenant in this contract supposed to know that a listing is made by them?


A petty issue with MetricsEnsemble's global score, that surfaces a general problem

As seen in the unit test:
https://github.com/IBM/unitxt/blob/a0c39a5267da52e6d37e4ad904c93914b80c56a9/tests/library/test_metrics.py#L1712
In the global score,  as expected, "score_name": "ensemble_score",  "score": 0.44, and "ensemble_score": 0.44.
However, the CI-s reported in  "score_ci_high": 0.56,  and  "score_ci_low": 0.0,  are those left from ensemble_1_recall_macro  (the last of self.metrics for which CI is computed). For MetricEnsemble itself, CI is not computed in the settings of the unit test, as is evident from the absence of ensemble_score_ci_.. from the global score.
The association of these values (ci_high = 0.56, and ci_low = 0.0) with "score" is misleading here, since it is not consistent with "score_name".

This inconsistency (of score_ci_high / score_ci_low  with score_name  can be reproduced also with a task of several metrics (each having its own main_score), the last of which to be applied (being the first one in task.metrics) gives its name to score_name,  but score_ci_low and score_ci_high are simply the last ones computed in the task:
from unitxt.artifact import fetch_artifact
from unitxt.operators import ApplyMetric, CastFields, Copy, Perturb
from unitxt.standard import StandardRecipe
from unitxt.settings_utils import get_settings
from unitxt.text_utils import print_dict

settings = get_settings()
settings.allow_unverified_code=True

card, _ =fetch_artifact("cards.coedit_error_detection")
print(card.task.metrics)

recipe = StandardRecipe(card=card, loader_limit=50, demos_pool_size=0, num_demos=0, template_card_index=0)
ms = recipe()
copyoperator = Copy(field="target", to_field="prediction")
ms = copyoperator(ms)
castfieldoperator = CastFields(fields={"prediction":"float"}, failure_defaults={})
ms = castfieldoperator(ms)
castfieldoperator = CastFields(fields={"references":"int"}, failure_defaults={}, process_every_value=True)
ms = castfieldoperator(ms)
perturboperator = Perturb(field="prediction", select_from=[0,1], percentage_to_perturb=60)
ms = perturboperator(ms)
applymetricoperator = ApplyMetric(metric_field="metrics", calc_confidence_intervals=True)
ms = applymetricoperator(ms)
trains = list(ms["train"])
print(len(trains))
print_dict(trains[0]["score"]["global"])

print("**** no CI in last metric applied, the metric that is marked by 'score_name'*******")
card.task.metrics[0] = 'metrics.accuracy[n_resamples=0]'
print(card.task.metrics)

recipe = StandardRecipe(card=card, loader_limit=50, demos_pool_size=0, num_demos=0, template_card_index=0)
ms = recipe()
copyoperator = Copy(field="target", to_field="prediction")
ms = copyoperator(ms)
castfieldoperator = CastFields(fields={"prediction":"float"}, failure_defaults={})
ms = castfieldoperator(ms)
castfieldoperator = CastFields(fields={"references":"int"}, failure_defaults={}, process_every_value=True)
ms = castfieldoperator(ms)
perturboperator = Perturb(field="prediction", select_from=[0,1], percentage_to_perturb=60)
ms = perturboperator(ms)
applymetricoperator = ApplyMetric(metric_field="metrics", calc_confidence_intervals=True)
ms = applymetricoperator(ms)
trains=list(ms["train"])
print_dict(trains[0]["score"]["global"])

that prints out:
Loading filtered by: lambda x: x['task'] == 'gec';

Loading limited to 50 instances by setting LoadHF.loader_limit;
90

f1_binary (float64):
    0.7619047619047619
f1_binary_neg (float64):
    0.7916666666666666
recall_binary (float64):
    0.7111111111111111
recall_binary_neg (float64):
    0.8444444444444444
precision_binary (float64):
    0.8205128205128205
precision_binary_neg (float64):
    0.7450980392156863
score (float64):
    0.15555555555555556
score_name (str):
    accuracy
score_ci_low (float64):
    0.08888888888888889
score_ci_high (float64):
    0.25555555555555554
recall_binary_ci_low (float64):
    0.5463282189392394
recall_binary_ci_high (float64):
    0.8462029114420383
precision_binary_ci_low (float64):
    0.711368184735433
precision_binary_ci_high (float64):
    0.9028650762467041
f1_binary_ci_low (float64):
    0.6528563264107466
f1_binary_ci_high (float64):
    0.8550395441291192
accuracy (float64):
    0.15555555555555556
accuracy_ci_low (float64):
    0.08888888888888889
accuracy_ci_high (float64):
    0.25555555555555554

**** no CI in last metric applied, the metric that is marked by 'score_name'*******
['metrics.accuracy[n_resamples=0]', 'metrics.f1_binary', 'metrics.precision_binary', 'metrics.recall_binary']
Loader line limit was set to  50

Loading filtered by: lambda x: x['task'] == 'gec';

Loading limited to 50 instances by setting LoadHF.loader_limit;

f1_binary (float64):
    0.7619047619047619
f1_binary_neg (float64):
    0.7916666666666666
recall_binary (float64):
    0.7111111111111111
recall_binary_neg (float64):
    0.8444444444444444
precision_binary (float64):
    0.8205128205128205
precision_binary_neg (float64):
    0.7450980392156863
score (float64):
    0.15555555555555556
score_name (str):
    accuracy
score_ci_low (float64):
    0.6528563264107466
score_ci_high (float64):
    0.8550395441291192
recall_binary_ci_low (float64):
    0.5463282189392394
recall_binary_ci_high (float64):
    0.8462029114420383
precision_binary_ci_low (float64):
    0.711368184735433
precision_binary_ci_high (float64):
    0.9028650762467041
f1_binary_ci_low (float64):
    0.6528563264107466
f1_binary_ci_high (float64):
    0.8550395441291192
accuracy (float64):
    0.15555555555555556

Resolved by https://github.com/IBM/unitxt/pull/1065


Example of usage dual SC16IS740 (SPI)

Hi @rickkas7
We have an HW setup with 2xSC16IS740 shared SPI lanes and dedicated CS for each IC.
Can you help me understand the proper initialization for 2 UARTs? My understanding that it's should be somehow similar to a dual port IC example. A short example would be highly appreciated.
We are testing with B524.
Best,
Bogdan

For other who could be interested here is the solution from the library author
Use the SC16IS7xxRK library (not the older one)
Create two SC16IS7x0 objects, one for each chip, typically as global variables
SC16IS7x0 serialA;
SC16IS7x0 serialB;
Initialize them with the appropriate CS pin and settings, typically from setup():
    serialA
        .withSPI(&SPI, D2, 4)   // SPI port, CS line, speed in MHz
        .begin(9600);

    serialB
        .withSPI(&SPI, D3, 4)   // SPI port, CS line, speed in MHz
        .begin(9600);

Do not attempt to control the CS pins directly. It won't work.
If you want to make something that you can switch between ports, store the pointer to the one you want in a variable of type Print. For example:
Print *port = &SerialA;

port->println("UART A working");
delay(1000);

port = &SerialB;
port->println("UART B working");
More likely you'd make port a global variable or a class member and you'd set it to whatever port you want to use.


YARN-11022. Fix the documentation for max-parallel-apps in CS. Contri…

…buted by Tamas Domok

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
10m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
35m  4s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 26s

branch-3.3 passed

+1 :green_heart:
shadedclient
59m 57s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 11s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 17s

the patch passed

+1 :green_heart:
shadedclient
24m  8s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

97m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4019/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4019

Optional Tests
dupname asflicense mvnsite codespell markdownlint

uname
Linux 2e87bb6ddb31 4.15.0-166-generic #174-Ubuntu SMP Wed Dec 8 19:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 375e500e15fe45fa2f57ba757161f0fdbc916f2b

Max. process+thread count
517 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4019/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks @tomicooler ,
Patch LGTM, committed to branch-3.3


no reloading context after power on

I used LoraWan Basic on stm32Cube with STM32L082KZT6 and semtech SX1276IMLTRT.
Join, Uplink and downlink work correctly.
I would like the system not to make a "join" at each startup (power on).
I see backups in EEPROM, at startup during init I also see loading from the EEPROM but I cannot send any frame.
I don't understand why and I haven't found an example.
thanks a lot
David

Hi,
Only Devnonce and joinnonce are stored in non-volatile memory as requested by LoRaWAN standard.
The full LoRaWAN stack context is not stored in NVM.

Hi,
In the current LBM implementation, you have to perform a new Join after a Reset.
The whole context of LoRaWAN is not saved.
We are studying the possibility to improve it (especially to support ABP) in the next release.
Many thanks,

Thank you very much for these clarifications.
I succeeded in saving the context by making these modifications in the lower layers:

I added the devAdr in the context (CONTEXT_LORAWAN_STACK)
I added a function to write to fcnt_up:  I have a special algorithm who save de fcnt_up only every 100 to limit writing in eprom
on the SMTC_MODEM_EVENT_JOINED event, I added the key backup: smtc_secure_element_store_context(STACK_ID);

So on the reset event:

I force the status to join: lorawan_api_set_join_status(STACK_ID, JOINED);
I load the modem context: modem_load_modem_context();
I load the keys: smtc_secure_element_restore_context(STACK_ID);
and I load the new fcnt_up

Hi,
To be more LoRaWAN compliant, you could improve your code by saving the LoRaWAN/regional parameters (channel, Data rate, RX1 delay ...) sent by the network server.
Many thanks,

Hi, it would indeed be very useful to be able to reuse the OTAA context across boot cycles. Any rough estimates on when this feature would be available?

Shouldn't this be implemented specially for devices not powered by battery (like an energy meter)? Resets can be a frequent thing, and It makes no sense to perform a join every time there's a power outage.


Crash when performing migration

The first version was set to 0. Now to 1 and the app crashes with the following exception:
Cannot set schema version for Realms that are already open."

It seems that the buggy peace of code is due to the if-statement
if (RLMGetAnyCachedRealmForPath(realmPath) && schemaVersionForPath(realmPath) != version) {
            NSLog(@"version = %llu, schemaVersionForPath(realmPath)  = %lu", version, (unsigned long)schemaVersionForPath(realmPath));
            @throw RLMException(@"Cannot set schema version for Realms that are already open.");
        }

Instead of
if (RLMGetAnyCachedRealmForPath(realmPath) && schemaVersionForPath(realmPath) > version) {
            NSLog(@"version = %llu, schemaVersionForPath(realmPath)  = %lu", version, (unsigned long)schemaVersionForPath(realmPath));
            @throw RLMException(@"Cannot set schema version for Realms that are already open.");
        }

@virt87 no, the if statement is correct. Once you've opened a Realm at that path, you cannot set a different schema version for that path, since the open Realm would not be able to update to that new schema version you've set.

But the problem is that i has put updating version code at the first line of didFinishLaunchingWithOptions and it simply crashes

Are you sure you haven't created a Realm instance elsewhere, like via a Swift property default value or using storyboards?

Yes. We  are instantiated it in a viewmodel acting as a property of a viewController only. It is not referenced in the storyboard.
We have this
    func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {

        UIApplication.sharedApplication().statusBarStyle = UIStatusBarStyle.LightContent

        // setup Realm
        setupRealm()
...

// MARK: - REALM
    private func setupRealm(){

        setSchemaVersion(1, Realm.defaultPath) { (migration, oldSchemaVersion) -> Void in
            if oldSchemaVersion < 1 {
                migration.enumerate(Food.className(), { (oldObject, newObject) -> Void in
                    let price = oldObject!["price"] as! Int
                    newObject!["price"] = Float(price)
                })
            }
        }
    }

Or.Wait. yes, you are true... The viewcontroller is instantiated via storyboard->initWithCoder.

Due to the fact that a viewController was instantiated via unarchiving the UI (means the storyboard package) some lazy properties was created with a Realm initialization.
To resolve this we changes
let categoryViewModel = CategoryViewModel()

where * CategoryViewModel* contains Realm initialization to
var categoryViewModel = CategoryViewModel(){
        willSet{
            CategoryViewController.setupRealm()
        }
    }
...

// MARK: - REALM VERSIONING
    private class func setupRealm(){

        setSchemaVersion(1, Realm.defaultPath) { (migration, oldSchemaVersion) -> Void in
            if oldSchemaVersion < 1 {
                migration.enumerate(Food.className(), { (oldObject, newObject) -> Void in
                    let price = oldObject!["price"] as! Int
                    newObject!["price"] = Float(price)
                })
            }
        }
    }

Thank you Realm's team for your patience!

@virt87 glad you were able to get things working!


Port DT Release 4.9.0 changes to Hyades

Changelog for DT Release 4.9.0 https://docs.dependencytrack.org/changelog/
Release 4.9.0 changes have to be ported to hyades

Issue / PR
Type
Description
Backported
Backport PR

https://github.com/DependencyTrack/dependency-track/pull/2817
Misc
Fix GHA set-output deprecation warnings
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/361

https://github.com/DependencyTrack/dependency-track/pull/2872
Bugfix
Fix memory leak in policy evaluation
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/230

https://github.com/DependencyTrack/dependency-track/pull/2873
Bugfix
Fix memory leak issue in vex upload processing task
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/229

https://github.com/DependencyTrack/dependency-track/pull/2769
Enhancement
Custom licenses
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/364

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/3051
Bugfix
Fix JsonIgnore having no effect on transient field
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/362

@sahibamittal https://github.com/DependencyTrack/dependency-track/pull/3083, https://github.com/DependencyTrack/dependency-track/pull/2623
Enhancement
Create endpoint to fetch many components and services
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/366

https://github.com/DependencyTrack/dependency-track/issues/2423
Enhancement
Separate policy evaluation into its own task
N/A, already implemented in Hyades
https://github.com/DependencyTrack/hyades-apiserver/pull/160

https://github.com/DependencyTrack/dependency-track/pull/2581
Enhancement
Added transient List of ProjectVersions and set Metrics in Project
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/367

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/3068
Bugfix
Fix NPE when checking for project without version
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/365

@sahibamittal https://github.com/DependencyTrack/dependency-track/pull/2568
Enhancement
New option to only return outdated components and/or only direct dependencies in the ComponentResource
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/372

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/2911
Enhancement
Upgrade the snyk api version
N/A version is in application properties
-

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/2989
Enhancement
Log warning when Vex cannot be applied
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/368

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/3047
Enhancement
Prefix apikey with odt_
N/A Already ported to apiserver
https://github.com/DependencyTrack/hyades-apiserver/pull/327

https://github.com/DependencyTrack/dependency-track/issues/2871
Enhancement
CWE Catalogue Out of Date
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/369https://github.com/DependencyTrack/hyades/pull/859

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2997
Enhancement
Allow operator and violation state to be specified
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/371

@nscuro https://github.com/DependencyTrack/dependency-track/pull/3006
Enhancement
Update SPDX license list to v3.21
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/375

@nscuro https://github.com/DependencyTrack/dependency-track/pull/2675
Enhancement
Add Docker Compose files for simplified local testing
Only porting partially; Compose files now live in the hyades repo
https://github.com/DependencyTrack/hyades-apiserver/pull/370

@nscuro https://github.com/DependencyTrack/dependency-track/pull/2913
Enhancement
Use IntelliJ standard directory for run configurations, and add project icon
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/370

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2537
Enhancement
New Version Distance Policy Evaluator
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/374

@nscuro https://github.com/DependencyTrack/dependency-track/pull/3070
Bugfix
Fix false negatives in NVD CPE matching
✅
https://github.com/DependencyTrack/hyades/pull/861

@sahibamittal https://github.com/DependencyTrack/dependency-track/issues/2859
Misc
Add regression test for XML BOM parsing
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/372

@sahibamittal https://github.com/DependencyTrack/dependency-track/issues/2788
Bugfix
Fix VDR export containing non-vulnerable components
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/372

@nscuro https://github.com/DependencyTrack/dependency-track/pull/3095
Bugfix
Fix invalid Mattermost notification template; Add more thorough publisher tests
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/384

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2243
Bugfix
Add extensive test suite for CPE matching logic
NA Implemented with porting of #3070
-

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2878
Bugfix
Fix VDR export erroneously containing non-vulnerable components
NA Implemented already with porting of #2788
-

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/3067
Bugfix
Fix VEX export erroneously containing dependency graph
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/381

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2980
Bugfix
Fix version distance policy being evaluated despite not being configured
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/382

@nscuro https://github.com/DependencyTrack/dependency-track/pull/2651
Enhancement
Include Cloud SQL database connectors
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/383https://github.com/DependencyTrack/hyades/pull/870

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/2967
Bugfix
Fix AffectedComponent format for CPEs with version ranges
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/385

@VithikaS https://github.com/DependencyTrack/dependency-track/issues/2903
Enhancement
Update Docker image to latest debian stable release
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/387

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/3071
Enhancement
Update cyclonedx-core-java to 8.0.0 / Support Import of CycloneDX 1.5 BOMs
On hold, waiting for release of cyclonedx-core-java 8.0.2
-

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/3069
Enhancement
Bump temurin base image to <IP_ADDRESS>_1
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/387

@VithikaS https://github.com/DependencyTrack/dependency-track/pull/2971
Bugfix
Exclude xml-apis dependency / The package javax.xml.parsers is accessible from more than one module
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/387

@nscuro https://github.com/DependencyTrack/dependency-track/pull/2400
Enhancement
Implement SPDX expressions
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/393

@nscuro https://github.com/DependencyTrack/dependency-track/pull/2965
Enhancement
SPDX expression support improvements
✅
https://github.com/DependencyTrack/hyades-apiserver/pull/396

Note: Two PRs related to fixing memory leaks were already backported:

https://github.com/DependencyTrack/dependency-track/pull/2872
https://github.com/DependencyTrack/dependency-track/pull/2873

Closing #660 as duplicate.

All done!


Upload to my desire path

Hi,
Thank you for this plugin awesome.
I set url: upload.php now what to do then? how to upload the images to the desired path.
Can you give me sample upload.php
Please help me.
Thank You

@danielm
would you consider adding a secure php backend? I like the look and feel of this library


[Monorepo] feat: remove hufi from monorepo

Description

Summary of changes

How test the changes

Related issues
Keywords for linking issues

Closes #1440

I think we can remove DBs. Private keys were in vercel project, not the DB. @portuu3 already removed the vercel projects, and I think he already did move the funds.


Delete temporary gif files once they are done with

Resolves #160  (at least the gif files part of it). Don't think it resolve the pymp- folders part of the issue.

thanks~


Individuals are tracked by Google Analytics.

Describe the bug
Individuals are tracked by Google Analytics.
When accessing the Privacy Policy tracking code is passed from the application to the covid19.nhs.uk website which is processed by Google Analytics. Data captured could be used to re-identify an individual.
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Appearance/LogoStrapline.swift#L45-L48
Expected behaviour
Individuals are NOT tracked by Google Analytics

Further tracking links found in StatusContent.json.
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Status/statusContent.json#L3-L4
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Status/statusContent.json#L7-L8
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Status/statusContent.json#L11-L12

https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Frameworks/FirebaseAnalytics.framework/Headers/FIRUserPropertyNames.h#L28-L29
The firebase analystics framework also permits personalized adverts. This has not been opted out.

Just want to point out that this is also a violation of the #GDPR as the user was never given the opportunity to consent to this tracking or manage what data is collected.

Wow, sort this out lads.

FYI, the same discussion is happening in the Android app issues and has some more discussion points: https://github.com/nhsx/COVID-19-app-Android-BETA/issues/11

Thanks for all the comments. As we say in the blog

The public version of the app does not use any third-party analytics. In order to improve the app, we need to collect information about what happens if it crashes. This will use the operating system's default error-reporting tools.
Our closed Beta will collect some volunteers' data for performance analytics and A/B testing. The libraries required for these analytics may still be present - but deactivated -  in the public version of the app.

I agree that we probably don't want UTM trackers on the links.

@edent Thanks for clarifying. I'm just curious if your deactivating also takes care of cases where 3rd party SDK's hook into events even without even being initialized? Similar to the Facebook SDK which was further highlighted in the past week with the analytics related crash.

@ay8s I'll check whether there are any side-effects of deactivating APIs. To be absolutely clear, we aren't using the Facebook SDK.

@ay8s I'll check whether there are any side-effects of deactivating APIs. To be absolutely clear, we aren't using the Facebook SDK.

👍 Should’ve made it clear in my comment it was just an example of an SDK that runs code even if it’s not initialized. I’m not sure if Google Analytics does the same, personally think there’s a high chance it does.

Just for observation and transparancy after looking at the Android issue nhsx/COVID-19-app-Android-BETA#11 I noticed they mentioned the use of Microsoft App Center Analytics. This has also been implimented in the iOS app as well.
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Frameworks/AppCenter.framework/Headers/MSAppCenter.h#L102
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Monitoring/AppCenterMonitor.swift#L47-L53
https://github.com/nhsx/COVID-19-app-iOS-BETA/blob/370a51857b8a680925adc85bfc2e08936a2fd77d/Sonar/Monitoring/AppEvent.swift#L18-L22

Thanks for all the comments. As we say in the blog

The public version of the app does not use any third-party analytics. In order to improve the app, we need to collect information about what happens if it crashes. This will use the operating system's default error-reporting tools.
Our closed Beta will collect some volunteers' data for performance analytics and A/B testing. The libraries required for these analytics may still be present - but deactivated -  in the public version of the app.

I agree that we probably don't want UTM trackers on the links.

Are you saying there is a different code base for the public release?

Thanks for all the comments. As we say in the blog

The public version of the app does not use any third-party analytics. In order to improve the app, we need to collect information about what happens if it crashes. This will use the operating system's default error-reporting tools.
Our closed Beta will collect some volunteers' data for performance analytics and A/B testing. The libraries required for these analytics may still be present - but deactivated -  in the public version of the app.

I agree that we probably don't want UTM trackers on the links.

Are you saying there is a different code base for the public release?

There is an internal branch which is used for releases. https://github.com/nhsx/COVID-19-app-iOS-BETA#releases

Thanks for all the comments. As we say in the blog

The public version of the app does not use any third-party analytics. In order to improve the app, we need to collect information about what happens if it crashes. This will use the operating system's default error-reporting tools.
Our closed Beta will collect some volunteers' data for performance analytics and A/B testing. The libraries required for these analytics may still be present - but deactivated -  in the public version of the app.

I agree that we probably don't want UTM trackers on the links.

Are you saying there is a different code base for the public release?

There is an internal branch which is used for releases. https://github.com/nhsx/COVID-19-app-iOS-BETA#releases

If there is a hidden internal branch for releases, is there a potential for code not found in this repository to make it's way into a build that's hidden from the public?

well there's been no updates to this repo in 9 days so im guessing the project is no longer being worked on or this isn't actually an open source project

So everyone is reviewIng code that may or may not be used in production. In effect this is a closed source project where no one can be certain what’s actually being coded. Or do you plan to release the final production code?
Also it seems you’re capitalising on the support of the community under false pretences, hardly a great start in being open and transparent.

I think no matter what happens, we the community need to get access to one of these APK's and tear it apart to see what kind of tracking is really involved.

I'm working as hard as I can to get the updated code on here. We have a lot of competing demands on our time. I want to make sure that we get an updated version of Android and iOS up this week. We have limited resources and - as you can imagine - prepping the code for release, making sure it is in a suitable condition, removing the personal details of the people working on it, responding to media questions, answering vulnerability reports etc, isn't a simple process.
My mission is to make these things as open as possible. I'm sorry for letting you down like this.

Please do not guess, presume or assume; and I am saying this to myself only.  Fact (non fake!) based evidence only :-p. Hurrah for Edent; and @Edent, please do not apologise to the community.

@edent, as mentioned by @philipswift. You don't need to apologise to the community and although most of the responses will be emotionally charged due to the nature of this application and the air surrounding it on design and security, we accept you're likely making the best of a bad situation.
I would hope that you don't feel personally attacked by some of these comments as they're likely more targeted at those driving the project as opposed to working on it.

I wish to eco @Matthew-Beckett there's no need to say sorry to us. Your doing the best with the resources you have and as a community we will do what we can to provide feedback. I can only imagine a small part of the stress your going though at the moment. It goes without saying but please take care of yourself and your team as well.

@edent I think it would be valuable for a clarification on the purpose of this repository and it's use in the wider project.
Specifically, the build process for the application going forward and the process for quelling concerns that this repository is in fact not indicative of the code which will be pushed via OS storefronts.

@Matthew-Beckett at the moment, these repos are copies of the code from the initial public beta in the Isle of Wight. These repos used to let people see the code, examine it, and report back their bugs and suggestions.
We read every issue and PR and - where suitable - we copy them to an internal tracker.
When the app is released to the wider public, the source code will appear here.
This code is indicative of the code published to app stores - but is missing API keys etc.
Hope that answers your question.

We read every issue and PR and - where suitable - we copy them to an internal tracker.
So your not using GitHub for tracking? Just as a proxy?

When the app is released to the wider public, the source code will appear here.
Will it? Or will it be a public branch?

This code is indicative of the code published to app stores - but is missing API keys etc.
If we disassemble the public build will we get teh same thing as what is published?'

Hope that answers your question.
It makes it seem like your just using GiitHub to take feedback and not really integrating yourself with the community; It feels like marketing and doublespeak and not true collaboration.

I'm pasting this message in every active GitHub issue, so you may receive duplicate notifications.
Today, I'm happy to announce that NHSX has released the full git commit history for the Isle of Wight Beta apps.

Android - https://github.com/nhsx/COVID-19-app-Android-BETA
iOS - https://github.com/nhsx/COVID-19-app-iOS-BETA

As discussed, we have redacted API keys, sensitive domain names, and some of the developers' personal details. I am still waiting on final approval to publish the server-side code.
I would like to personally thank the community for your comments, bug reports, and vulnerability disclosures. They all went into helping the development process.
The beta trial of this app has now ended and we've moved to the next phase of app development. It is our intention to publish the source code of future apps as the binaries are released to the public.
Once again, thank you for being part of this.
Terence Eden
Head of Open Technology - NHSX


New Endpoint - APIKey Auth removed

-New Endpoint "getAssociatedPersonsWithtrust" added
-APIKey Authentication removed

I would like to see this split into 2 Pull Requests because the context of the commits are unrelated.
Could you please update so that the addition of the Endpoint is a separate Pull Request, just in case we need to revert any of these features in the future :)

Funny enough they were separate I merged them today :D I did test them thoroughly but sure for the peace of mind I will separate them 👍


Will a UMD be released with the library?

Hi. Thanks for building this great lib. It's an integral part of one of our libs so we'd love to have a UMD for it since it'll be used in multiple projects that come together at runtime. We're using webpack externals for the libs that are commonly used and I guess other people would do so for sure.
Will a UMD file be released with the library? Again thanks for the work.

+1
I would like to use this lib in Chrome extension without a build step. Chrome Web Store disallows minified code, so I cannot really use notyf.min.js

Thanks @Strajk! The UMD is already available in version 3.9.0.

@caroso1222 awesome, thanks!
I still consider myself new to open source world and so far I have only the best experience :)
https://www.youtube.com/watch?v=StTqXEQ2l-Y


details

could this be supported?

Title
Content

<details>
	<summary>Title</summary>
Content
</details>

No ideas. Please, use commonmark forum for markup questions. This repo is about implementation only, with limited support.


EthStorage Devs Meeting #33 Agenda

Meeting Info

May 30, 2023, 10:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress
TBA

W3URL

ERC5018ForBlob - add testing

EthStorage

miner proof

KZG proof: testing
ZK proof: in progress
Integration of blob hash getter: done

Downloader: 50%

https://github.com/ethereum/EIPs/pull/6944 (some issues with the gateway)
https://github.com/ethereum/EIPs/pull/7087 (MIME type query support)
EdCon

EthStorage

Implementation:

refactor ethStorage -- (add provers: done); (add DB to store: done)
add sync protocol - (refactor the p2p sync) (ongoing: 40%)
add mining logic - TODO
add KZG prover or ZK prover - TODO

update code with comments:  https://github.com/ethstorage/storage-contracts-v1/pull/5
Use the ec-gpu library(https://github.com/filecoin-project/ec-gpu) to implement the encoding and decoding process
Reading Halo paper : https://eprint.iacr.org/2019/1021.pdf

Recording: https://drive.google.com/file/d/1_bHP_m-8wMG8ezSMOaxzAj2eXMnxiLBd/view?usp=share_link


Avoid the runtime dependencies onto validation-runtime

This changeset updates the generated validation code to use CollectionsConverter introduced to spine-base.
The idea is to get rid of validation-runtime artifact when compiling the Java files enhanced with the generated validation code. It is going to be enough that the generated code uses spine-base artifact already.
The validation-runtime module is left intact in this project to avoid any compatibility issues, as there are some complex Gradle dependency relations between validation, mc-java and ProtoData libraries, which are addressed partially by forcing some artifact versions. The validation-runtime module is now marked deprecated and will be removed in the following changesets.

@alexander-yevsyukov PTAL.
@dmdashenkov FYI.


account for force_ascii

The original implementation had some intricate logic around force_ascii that I did not properly reproduce.

@bigtoast this is fixes two regression in relation to the preprocessor function handling:

some scorers call utils.full_process with force_ascii=True which was not properly done
it restores the edge case described in the comment above

Together they fix the behavior change reported in #57

Note that in the last release the version number was not updated: https://github.com/seatgeek/thefuzz/blob/master/thefuzz/init.py.


Update index.md

Added full namespace to types as some conflict with classes in other namespaces.
Fixed the MemberAuthoize attribute example as it is incorrect (should be = instead of :)

thx!


correcting sample links for Python SDK

Docs Build status updates of commit 1d089be:
:clock10: Full build: the average full build time is 218 min(s) 50 sec(s), this is based on the last 59 build(s) for this repository.

#sign-off

Docs Build status updates of commit 1d089be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/servicebus.md
:white_check_mark:Succeeded
View (azure-python)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off


error in stack example on the agent docs page

Bug description
The docs page for the agent has a litte error inside the stack file example.
A wrong indent in line 20 and 21 prevents the stack from deploying.
version: '3.2'

services:
  agent:
    image: portainer/agent
    environment:
      AGENT_CLUSTER_ADDR: tasks.agent
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/lib/docker/volumes:/var/lib/docker/volumes
    ports:
      - target: 9001
        published: 9001
        protocol: tcp
        mode: host
    networks:
      - portainer_agent
    deploy:
      mode: global
    placement:
      constraints: [node.platform.os == linux]

networks:
  portainer_agent:
    driver: overlay
    attachable: true

Expected behavior
The stack should deploy without an error.
Steps to reproduce the issue:

create a yml file with the sample code
try to deploy it

Technical details:
Additional context
This version of the script worked for me.
version: '3.2'

services:
  agent:
    image: portainer/agent
    environment:
      AGENT_CLUSTER_ADDR: tasks.agent
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/lib/docker/volumes:/var/lib/docker/volumes
    ports:
      - target: 9001
        published: 9001
        protocol: tcp
        mode: host
    networks:
      - portainer_agent
    deploy:
      mode: global
      placement:
        constraints: [node.platform.os == linux]

networks:
  portainer_agent:
    driver: overlay
    attachable: true

Yup, this was fixed via https://github.com/portainer/portainer-docs/commit/87924e052619aace5bd5607c941b46ecdc0e43db
Will be updated after next release.


Ros2 refactor, link to external repo

Signed-off-by: Budai<EMAIL_ADDRESS>ROS2: added target for ros2 cmake
Signed-off-by: Budai<EMAIL_ADDRESS>ROS1: added target for ros2 cmake
Signed-off-by: Budai<EMAIL_ADDRESS>RO2: big cmake functional
Signed-off-by: rbudai<EMAIL_ADDRESS>ROS2, big cmake restored to initial version
Signed-off-by: Budai<EMAIL_ADDRESS>ROS2: added humble for ubuntu 22 version
Signed-off-by: Budai<EMAIL_ADDRESS>

Looks good. Can you keep the bindings/ros2 dir? And inside keep a readme that mentions that ROS2 bindings exists in a separate repo, and provide the link.


Head fade on Rift still allows you to see through walls

Environment

GitHub
f46a07aa6455d4c0c59349f346b50aaad2cc55d4
5.5.1f1
Oculus
Oculus Utilities

Steps to reproduce
Using Example 11 HeadSetCollisionFading putting your head inside the wall ever so slightly (putting your head in sideways works even better) still allows you to see through to the other side of the wall.
Expected behavior
You should not be able to see through the wall
Current behavior
You can see through the wall
The headset collider might need to be a little bigger to prevent this from happening.

What version of Oculus Utilities are you using?

First issue seems to be the headset collider is too small for the rift so it doesn't fade before you start clipping.
Second issue seems to be it doesn't fade completely to black and  you can still faintly see through,

Fix for the not completely fading to black issue.
https://github.com/thestonefox/VRTK/commit/dcd69452ec2f2daade5654510263910c7ef978a1
As for the collider being too small, you can change the size of the collider radius on the headset collision script, I recommend 0.2f for the rift.

As for the collider being too small, you can change the size of the collider radius on the headset collision script, I recommend 0.2f for the rift.

But wouldn't it be better if this was something that would work without "tweaking"? Otherwise switching between SDKs (like we'll be able to do very easily with @bddckr 's PR in the near future) will always cause these slight "imperfections", right?
Perhaps an idea would be to have each headset come with a "recommended size" and have a "multiplication factor" on the headset collision script (which would default to "1.0f"?

Maybe we could have it where if you set the headset collider radius to 0f then it defaults to the headset default?

Sure, we could do that too.


Fix some broken links in the building with spack section of the manual.

Description
I deleted a couple of files referenced by the building with spack section of the manual. I deleted one and updated another.
Type of change

[X] Documentation update~~

How Has This Been Tested?
The CI will test the change.
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[ ] I have commented my code where applicable.
[ ] I have updated the release notes.
[X] I have made corresponding changes to the documentation.~~
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have confirmed new and existing unit tests pass locally with my changes.
[ ] I have added new baselines for any new tests to the repo.
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.

The CI isn't showing any errors, but I'm not seeing the literal included file in the CI.

Never mind, I was looking in the wrong spot.


allow to set the resync period via env var

@StephenCoady @secondsun mind taking a quick look?

Pull Request Test Coverage Report for Build 461

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 74.678%

Totals

Change from base Build 459:
0.6%

Covered Lines:
348

Relevant Lines:
466

💛  - Coveralls


Cache the regularized form of union types

Fixes #37744
I doubled the example size for good measure. This simple change takes the test run down from 11 minutes to 30 seconds. That 30 seconds could likely still stand to be improved, but this fixes the obvious complexity issue.

@typescript-bot perf test this

Oops, I meant, why doesn't memory usage increase, not improve.

Oops, I meant, why doesn't memory usage increase, not improve.

Why would memory usage change? Unions are globally cached so long as their members are the same, so the final type counts are inevitably the same. All that's different is we now keep a direct reference to the result on the union (saving us from needing to iterate over it more than once), which means the only addition is a property, which are allocated by the vm in blocks (rather than one at a time) anyway.

The VM allocating properties in blocks was the missing piece in my understanding. Thanks.

So my last commit takes the test runtime locally down from 30s to 5s, but CI is failing on npm install because a version of rxjs is missing from the registry!?!?

@typescript-bot perf test this
At least travis is green 😾 - hopefully perf can install and run.

Nice improvement on material-ui check time!


simplehandler history problems

Hello.
I'm trying read a history file.
While processing nodes works very fine to get a timeline, it is not possible with ways, relations or area:
RuntimeError: Way ID twice in input. Maybe you are using a history or change file?
Is there any way around this?

You can read history files only when you do not assemble geometry. That means no area callbacks, no geometries for ways.

Ok. thanks for the quick answer.
Do you know of any way around this problem? E.g. retrieving way IDs only including versions and then further retrieving the area separately based on iD? Is this only possible with separated osm files? One with history, the other one without?

@cmikovits This is all very vague. If you explain what it is that you are trying to achieve in the end, it might be easier for other to help you.

Hey, My task is as follows:

get all OSM buildings of an area
calculate the area of each building
get the date of first entry to OSM (version 1) of each building

For small areas I can do it online via the API, this is already working, but it would be really fantastic if this is achievable with the full history planet file.

You have to do this in two steps. One is the area calculation with a current planet file and one is getting at version 1 using the history file.

Thanks very much. This clarifies that my current approach is already in the right direction, I just have to change the API call and use the history file instead. Maybe a short question to this topic? Is it possible with simplehandler to fetch a single ID (or a list of IDs)? I know this is possible from the command line, but not sure about the python handling.

No. You can only scan sequentially, which is rather slow to do in Python for finding a single object. You are better off with the command line tools.


vim 7.4.488: Fix for Linuxbrew

Hi.
In my centos 6.5, brew install vim fails due to missing of link to ncurses.
When I added homebrew/dupes/ncurses to depends_on, install succeeded.
So I'd like to send patch, but I'm not sure if this is a correct way to solve it (Can I specify dupes formula as a depends_on ?).
Could you please review this patch?

The current policy is that Linuxbrew must install all the formula provided by homebrew/dupes to provide a system that has all the dependencies that are usually provided by Mac OS.

Thanks for the feedback though. The above policy may change.

My understanding is that the policy for dependencies on homebrew/dupes has not been  determined yet and if I would like to pass through this issue, I should have install all homebrew/dupes manually.
OK. I see. I close this ticket. I hope the policy will be determined nicely.

Yes, you understand correctly. Thanks for your understanding. I'd like to eventually add dependencies like depends_on :ncurses that on Mac is satisfied by Mac OS and on Linux possibly checks whether a native package is installed, and otherwise installs homebrew/dupes/ncurses.


perl conda package is not relocatable

The perl conda package is not outputting relocatable binaries.
It seems like there are these wonky paths with triple dots in conda packaged perl that is shipped from the conda-forge and dan_blanchard channels.  That seems like a problem with the relocation since I don't think that unix paths can have these triple dots in them.  At least I was unsuccessful in finding any information about triple dots (...) in unix paths via google.
To see the files that have these triple-dot-paths:
conda create -p /tmp/foo perl -c conda-forge --yes
cd /tmp/foo
grep -r "\.\.\.\/"

[link to the output of the above command] (https://gist.github.com/ericdill/e2eba39cc6b29b74d087fb3e3d372cba) since it is sort of long
There is [this thread] (http://www.london.pm/pipermail/london.pm/Week-of-Mon-20080721/014636.html) from 2008 that suggests that the combination of -de, -Dprefix and Duserelocatableinc has a very specific order that it needs to go in for the call to Configure. Specifically that -de needs to come last or things go wonky.  I did try that to no avail.
I discovered this while trying to build epics-base in conda-forge/staged-recipes#640 since it needs to be able to see those files.  I am basically dropping this off and running away since I've got little experience with this. Sorry!
attn @jakirkham @msarahan

Do you know a simple test for this, @ericdill? Preferably something that doesn't involve grepping.

@jakirkham I do not have any idea how to test this

This might be fixed by PR ( https://github.com/conda-forge/perl-feedstock/pull/6 ). Not sure. Going to mark it as fixed at least. If it is not actually fixed by it, we can retry with a new PR.


Add dirhtml special-case handling for canonical URLs

Discussed in https://github.com/pradyunsg/furo/discussions/656
https://github.com/sphinx-doc/sphinx/issues/9730 is the upstream issue about how the dirhtml builder with Sphinx is buggy when used with dirhtml pages, and generates incorrect URLs.
Other Sphinx themes have been working around this bug:

Sphinx RTD
Sphinx awesome

Pallets-Sphinx-Themes as well: https://github.com/pallets/pallets-sphinx-themes/blob/7a6fa47323af403c19008a5df8b5302a1ead7be3/src/pallets_sphinx_themes/init.py#L72-L91

Furo also assumes that its an extension, and relies on that. That actually seems like a cleaner fix -- thanks for sharing that @davidism! :)

@pradyunsg is there any movement on this? I just realized that this bug impacts your google SEO so I'd love to have it fixed. Let me know how I can help -- and thanks for the theme!

A PR for this would be welcome! I've had limited OSS tim lately.

A PR for this would be welcome! I've had limited OSS time lately.

yep -- would you be able to point me in the right direction please? I have limited bandwidth too, and really what I need help is knowing where I should be looking modify and in how many places etc., since I don't know the code base that well.

I don't mind doing this at the end of the week when I'm home for vacation, I'll base it on my solution from pallets I posted above.

I don't mind doing this at the end of the week when I'm home for vacation, I'll base it on my solution from pallets I posted above.

Awesome thanks. I'm happy to help validate the fix if that's helpful.

I don't mind doing this at the end of the week when I'm home for vacation, I'll base it on my solution from pallets I posted above.

@davidism bump happy to test when you have something up please! :)

@davidism @pradyunsg sorry -- I didn't actually validate the URL 🤦  -- I just validated that the .html was gone.
So to me the URL is still incorrect, or I have something incorrect in my sphinx set up.
E.g.
Go to https://hamilton.dagworks.io/en/latest/concepts/hamilton-function-structure/
you'll see the following in the HTML:
<link rel="canonical" href="https://hamilton.dagworks.io/concepts/hamilton-function-structure/">

However that URL leads to a 404 because it is missing the en/latest/ part in the URL. So question -- is this expected? Or do I have sphinx incorrectly configured here and instead it should redirect appropriately?

Okay I have a PR up that fixes this - https://github.com/pradyunsg/furo/pull/733


Make Bottom Section Nicer

The bottom now is nicer spaced with a different color button that fits with the theme

@webdev03


Update get_today function

pass in optional date format

@gsvr please review

@gsvr please review again

@gsvr all ok now?


feat: keep using the namespace proof for GetBlob and GetAll

Closes https://github.com/celestiaorg/celestia-node/issues/3629

Codecov Report
Attention: Patch coverage is 79.77528% with 18 lines in your changes missing coverage. Please review.

Please upload report for BASE (feature_branch_blob_proof@32d3137). Learn more about missing BASE report.

Files
Patch %
Lines

blob/service.go
79.77%
13 Missing and 5 partials :warning:

Additional details and impacted files
@@                     Coverage Diff                      @@
##             feature_branch_blob_proof    #3633   +/-   ##
============================================================
  Coverage                             ?   45.87%
============================================================
  Files                                ?      281
  Lines                                ?    16171
  Branches                             ?        0
============================================================
  Hits                                 ?     7419
  Misses                               ?     7896
  Partials                             ?      856

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