Renovate configuration fixes

Bundle of Renovate config fixes.
I pushed this patch to https://github.com/kaworu/cilium main branch and ran:
% npx --package=renovate -c renovate\ --dry-run\ --token\ $GITHUB_TOKEN\ kaworu/cilium

command output
 WARN: cli config dryRun property has been changed to full
 WARN: Please upgrade the version of Node.js used to run Renovate to satisfy "^18.12.0 || >=20.0.0". Support for your current version will be removed in Renovate's next major release.
       "versions": {
         "node": "19.9.0",
         "acorn": "8.8.2",
         "ada": "1.0.4",
         "ares": "1.19.0",
         "brotli": "1.0.9",
         "cldr": "42.0",
         "icu": "72.1",
         "llhttp": "8.1.0",
         "modules": "111",
         "napi": "8",
         "nghttp2": "1.52.0",
         "openssl": "3.0.8",
         "simdutf": "3.2.3",
         "tz": "2022e",
         "undici": "5.21.0",
         "unicode": "15.0",
         "uv": "1.44.2",
         "uvwasi": "0.0.16",
         "v8": "<IP_ADDRESS>-node.16",
         "zlib": "1.2.13"
       }
 INFO: Repository started (repository=kaworu/cilium)
       "renovateVersion": "35.74.1"
 INFO: git fetch completed (repository=kaworu/cilium)
       "durationMs": 3622
 INFO: Cannot ensure issue because issues are disabled in this repository (repository=kaworu/cilium)
 INFO: Dependency extraction complete (repository=kaworu/cilium, baseBranch=main)
       "stats": {
         "managers": {
           "dockerfile": {"fileCount": 8, "depCount": 29},
           "github-actions": {"fileCount": 62, "depCount": 570},
           "gomod": {"fileCount": 1, "depCount": 249},
           "kubernetes": {"fileCount": 1, "depCount": 2},
           "regex": {"fileCount": 50, "depCount": 59}
         },
         "total": {"fileCount": 122, "depCount": 909}
       }
 INFO: Dependency extraction complete (repository=kaworu/cilium, baseBranch=v1.13)
       "stats": {
         "managers": {
           "dockerfile": {"fileCount": 8, "depCount": 28},
           "github-actions": {"fileCount": 18, "depCount": 125},
           "gomod": {"fileCount": 1, "depCount": 241},
           "kubernetes": {"fileCount": 1, "depCount": 2},
           "regex": {"fileCount": 1, "depCount": 3}
         },
         "total": {"fileCount": 29, "depCount": 399}
       }
 INFO: Dependency extraction complete (repository=kaworu/cilium, baseBranch=v1.12)
       "stats": {
         "managers": {
           "dockerfile": {"fileCount": 8, "depCount": 28},
           "github-actions": {"fileCount": 16, "depCount": 104},
           "gomod": {"fileCount": 2, "depCount": 226},
           "kubernetes": {"fileCount": 1, "depCount": 2},
           "regex": {"fileCount": 1, "depCount": 3}
         },
         "total": {"fileCount": 28, "depCount": 363}
       }
 INFO: Dependency extraction complete (repository=kaworu/cilium, baseBranch=v1.11)
       "stats": {
         "managers": {
           "dockerfile": {"fileCount": 8, "depCount": 28},
           "github-actions": {"fileCount": 15, "depCount": 101},
           "gomod": {"fileCount": 2, "depCount": 221},
           "kubernetes": {"fileCount": 1, "depCount": 2},
           "regex": {"fileCount": 1, "depCount": 3}
         },
         "total": {"fileCount": 27, "depCount": 355}
       }
 INFO: GitHub GraphQL datasource: skipping empty item (repository=kaworu/cilium, baseBranch=main)
       "packageName": "coreos/go-systemd",
       "baseUrl": "https://api.github.com/"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "github.com/aws/aws-sdk-go-v2",
       "currentValue": "v1.17.8",
       "previousNewValue": "v1.18.0",
       "thisNewValue": "v1.17.8"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "github.com/go-openapi/runtime",
       "currentValue": "v0.25.0",
       "previousNewValue": "v0.26.0",
       "thisNewValue": "v0.25.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "github.com/osrg/gobgp/v3",
       "currentValue": "v3.13.0",
       "previousNewValue": "v3.14.0",
       "thisNewValue": "v3.13.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "github.com/prometheus/client_model",
       "currentValue": "v0.3.0",
       "previousNewValue": "v0.4.0",
       "thisNewValue": "v0.3.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "go.opentelemetry.io/otel",
       "currentValue": "v1.14.0",
       "previousNewValue": "v1.15.1",
       "thisNewValue": "v1.14.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "go.opentelemetry.io/otel/trace",
       "currentValue": "v1.14.0",
       "previousNewValue": "v1.15.1",
       "thisNewValue": "v1.14.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "go.uber.org/dig",
       "currentValue": "v1.16.1",
       "previousNewValue": "v1.17.0",
       "thisNewValue": "v1.16.1"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/crypto",
       "currentValue": "v0.8.0",
       "previousNewValue": "v0.9.0",
       "thisNewValue": "v0.8.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/net",
       "currentValue": "v0.9.0",
       "previousNewValue": "v0.10.0",
       "thisNewValue": "v0.9.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/sync",
       "currentValue": "v0.1.0",
       "previousNewValue": "v0.2.0",
       "thisNewValue": "v0.1.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/sys",
       "currentValue": "v0.7.0",
       "previousNewValue": "v0.8.0",
       "thisNewValue": "v0.7.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/term",
       "currentValue": "v0.7.0",
       "previousNewValue": "v0.8.0",
       "thisNewValue": "v0.7.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "golang.org/x/tools",
       "currentValue": "v0.8.0",
       "previousNewValue": "v0.9.0",
       "thisNewValue": "v0.8.0"
 INFO: Ignoring upgrade collision (repository=kaworu/cilium, baseBranch=main, packageFile=go.mod, branch=renovate/main-all-go-deps-main)
       "manager": "gomod",
       "depName": "google.golang.org/grpc",
       "currentValue": "v1.54.0",
       "previousNewValue": "v1.55.0",
       "thisNewValue": "v1.54.0"
 INFO: DRY-RUN: Would commit files to branch renovate/main-patch-hubble-cli (repository=kaworu/cilium, baseBranch=main, branch=renovate/main-patch-hubble-cli)
 INFO: DRY-RUN: Would commit files to branch renovate/v1.13-patch-hubble-cli (repository=kaworu/cilium, baseBranch=v1.13, branch=renovate/v1.13-patch-hubble-cli)
 INFO: DRY-RUN: Would commit files to branch renovate/v1.12-patch-hubble-cli (repository=kaworu/cilium, baseBranch=v1.12, branch=renovate/v1.12-patch-hubble-cli)
 INFO: DRY-RUN: Would commit files to branch renovate/v1.11-patch-hubble-cli (repository=kaworu/cilium, baseBranch=v1.11, branch=renovate/v1.11-patch-hubble-cli)
 INFO: DRY-RUN: Would ensure Dependency Dashboard (repository=kaworu/cilium)
       "title": "Dependency Dashboard"
 INFO: DRY-RUN: Would save repository cache. (repository=kaworu/cilium)
 INFO: Cannot ensure issue because issues are disabled in this repository (repository=kaworu/cilium)
 INFO: Repository finished (repository=kaworu/cilium)
       "cloned": true,
       "durationMs": 954738

Unfortunately I don't understand why Renovate would not open PRs for

contrib/backporting/Dockerfile from golang 1.20.2 to 1.20.4
contrib/coccinelle/Dockerfile from alpine 3.16.0 to alpine 3.17.3
contrib/coccinelle/Dockerfile, images/operator/Dockerfile, images/cache/Dockerfile, images/hubble-relay/Dockerfile, and images/clustermesh-apiserver/Dockerfile from alpine 3.17.0 to alpine 3.17.3

Ok seems working to me at https://github.com/kaworu/cilium/issues/292, marking as ready for review.

All reviews are in and this patch doesn't need a full CI run, so marking as ready-to-merge


A issue for custom dataset

Hi, thanks for your work. Recently I am trying to train the net using my custom dataset. There is an issue that I find it hard to debug it by myself. Here is my problem. Thanks a lot for your help again.
[  2]    2930 || B: 3.808 | C: 2.416 | M: 4.821 | S: 0.049 | T: 11.094 || ETA: 4 days, 14:47:05 || timer: 0.478
[  2]    2940 || B: 3.795 | C: 2.418 | M: 4.838 | S: 0.049 | T: 11.101 || ETA: 4 days, 14:47:10 || timer: 0.497
[  2]    2950 || B: 3.787 | C: 2.421 | M: 4.812 | S: 0.049 | T: 11.069 || ETA: 4 days, 14:49:01 || timer: 0.474
[  2]    2960 || B: 3.778 | C: 2.422 | M: 4.846 | S: 0.049 | T: 11.095 || ETA: 4 days, 14:49:52 || timer: 0.512
[  2]    2970 || B: 3.748 | C: 2.419 | M: 4.846 | S: 0.048 | T: 11.061 || ETA: 4 days, 14:49:04 || timer: 0.491
Computing validation mAP (this may take a while)...
Traceback (most recent call last):
File "train.py", line 377, in
train()
File "train.py", line 300, in train
compute_validation_map(yolact_net, val_dataset)
File "train.py", line 370, in compute_validation_map
eval_script.evaluate(yolact_net, dataset, train_mode=True)
File "/data/pancreas/root/yolact-master/eval.py", line 869, in evaluate
prep_metrics(ap_data, preds, img, gt, gt_masks, h, w, num_crowd, dataset.ids[image_idx], detections)
File "/data/pancreas/root/yolact-master/eval.py", line 433, in prep_metrics
ap_obj = ap_data[iou_type][iouIdx][_class]
IndexError: list index out of range

This happens because either the dataset is set up improperly or some annotation is mislabeled (see #31).
Can you send over your dataset and model config objects?

Thanks a lot for your reply!
Here is my config object:
Decathlon_dataset = dataset_base.copy({
'name': 'Dataset for Decathlon-10:Pancreas',
'train_images': '/data/pancreas/root/train',
'train_info':   '/data/pancreas/root/instances_pancreas.json',

'valid_images': '/data/pancreas/root/validation',
'valid_info':   '/data/pancreas/root/instances_pancreas_validation.json',

'has_gt': True,
'class_names': ('pancreas', 'tumor')

})
And here are the categories:
CATEGORIES = [
{
'id': 1,
'name': 'pancreas',
'supercategory': 'organ',
},
{
'id': 2,
'name': 'tumor',
'supercategory': 'disease',
}
]
I used pycococreator to create the annotation label. Here are some my annotation object:
{"annotations": [{"area": 374, "image_id": 1, "height": 512, "segmentation": [[276.0, 280.5, 271.0, 280.5, 266.5, 274.0, 267.5, 258.0, 271.0, 252.5, 283.5, 264.0, 283.5, 273.0, 276.0, 280.5]], "id": 1, "category_id": 1, "width": 512, "bbox": [267.0, 253.0, 17.0, 28.0], "iscrowd": 0}, {"area": 189, "image_id": 2, "height": 512, "segmentation": [[310.0, 257.5, 302.5, 253.0, 302.5, 245.0, 310.0, 240.5, 316.5, 244.0, 316.5, 251.0, 310.0, 257.5]], "id": 2, "category_id": 1, "width": 512, "bbox": [303.0, 241.0, 14.0, 17.0], "iscrowd": 0}}

Ok two things I can think of of the top of my head:

Make sure you have changed the number of classes in yolact_base_config or whatever config you're using to train. In your case, it should be 3 (len(Decathlon_dataset.class_names) + 1).
Make sure that every "category_id" in your annotations is either 1 or 2. Maybe pycococreator made a mistake in one of the annotations?

Ok, thanks for your advice! I will check the code about the above two tips which is very helpful!

The problem was solved. Thanks a lot!
I changed my classes in yolact_base_config to  len(Decathlon_dataset.class_names) + 1 . Now it can work successfully.  THX.


Review identified Common Crawl providers for inclusion

www.rawpixel.com
www.thorvaldsensmuseum.dk
eunis.eea.europa.eu
svgsilh.com **
digital.smb.museum
capl.washjeff.edu
www.perseus.tufts.edu
digi.ub.uni-heidelberg.de
www.free-photos.biz
www.ipernity.com
www.maxpixel.net

**do we want to integrate SVG in CC Search or are the concerns similar to icons? @janeatcc
Originally posted by @sclachar in https://github.com/creativecommons/cccatalog/issues/112#issuecomment-469272035
and those noted by @kgodey as well:
Here's some potential providers I found:
www.rawpixel.com
97353 CC0 images (C-MAIN-2019-04)
http://www.bcx.news/
84856 CC-BY-NC
84856 CC-BY (probably duplicates)
http://townmapsusa.com
44297 CC BY-NC
22150 CC-BY-SA
these seem programmatically generated (a map containing the location of a single US city for every US city), but they're unique and the site encourages remix and reuse.

reviewed. review strategy & process is in development, but for the purposes of this list, let's add the following providers:
rawpixel
thorvaldsen
svgsilh
capl.washjeff.edu
will send @sclachar deets

@janeatcc any concerns over svgsilh.com since there is a notice on their page which states the following "These SVG images were created by modifying the images of Pixabay."


Absence Forms

Description
Forms
As a "user",
So that "I can fill out forms for absence",
I want "be able to click on forms and fill them out to request absence"
Acceptance Criteria
What are some implicit tasks/criteria to be achieved within this story?

[x] Criteria/Task 1 User can click on forms for absence
[x] Criteria/Task 2 User can fill out absence forms
[x] Criteria/Task 3 User can submit absence forms

Exact specifications may be subject to changes per client request or us deciding to change it but the functionality of the form submission is there so I will close this issue and if we need to alter things later I will open a new issue to address that


mac->linux cross compiling fails on linking "unknown option: --no-undefined"

I'm having trouble cross-compiling from mac (darwin) to linux, both amd64.  I am running go version go1.14.3 darwin/amd64.
The program in question can be statically compiled for macOS (compiler host), and statically cross-compiled from macOS to Windows.  But static cross-compiling from macOS to linux gives the following error during linking:
CGO_ENABLED=1 CC=gcc GOOS=linux GOARCH=amd64 go build -tags static -ldflags "-s -w -v" emulator.go
# github.com/veandco/go-sdl2/sdl
ld: unknown option: --no-undefined

I've read elsewhere that this is a gcc/clang difference, and I can see that the sdl sources include that flag for building linux binaries, but I don't know how to either tell it to use the gcc linker or switch that flag for something clang-appropriate.
Also, when I statically compile on linux for linux:
$ CGO_ENABLED=1 CC=gcc GOOS=linux GOARCH=amd64 go build -tags static -ldflags "-s -w" emulator.go
# github.com/veandco/go-sdl2/sdl
/usr/bin/ld: ../../../go/src/github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../go/src/github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../go/src/github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL_dynapi.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../go/src/github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL_dynapi.c.o): unable to initialize decompress status for section .debug_info
../../../go/src/github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a: error adding symbols: File format not recognized
collect2: error: ld returned 1 exit status

Dynamic builds under mac->mac and linux->linux work fine.
It might be something silly, I admit that I haven't dug too deep into the options here.  Thanks for any help you can provide!
PS - I really like this project... I sure hope I can get a completely cross-platform build process working.

To cross-compile something that uses CGO you need to have a toolchain and compiler for that platform installed. For example, CC=x86_64-w64-mingw32-gcc when you cross compile for Windows, or CC=arm-linux-androideabi-clang for Android etc.
It seems you are just trying to add GOOS=linux and GOARCH=amd64 with your native compiler?

Now that you say this (and after sleeping on it), this makes perfect sense.  I did install x86_64-w64-mingw32-gcc in order to have a Windows cross-compiler, but I haven't installed one for Linux.  I guess part of why I was confused is because I was mixing up my native macOS gcc (which I have installed) and a Linux gcc cross-compiler (which I do not).
Is there a homebrew package for linux-gcc?  Is x86_64-elf-gcc what I'm looking for here?

Got the same issue on Linux using go1.14.3 linux/amd64 and gcc 7.5.0 (the default compiler currently for the distribution I'm using). The previous libraries (with go1.13.8) didn't have this issue. Output when go build-ing (-tags static):
# github.com/veandco/go-sdl2/sdl
/usr/bin/ld: ../../../../github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../../github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../../github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL_dynapi.c.o): unable to initialize decompress status for section .debug_info
/usr/bin/ld: ../../../../github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a(SDL_dynapi.c.o): unable to initialize decompress status for section .debug_info
../../../../github.com/veandco/go-sdl2/sdl/../.go-sdl2-libs/libSDL2_linux_amd64.a: error adding symbols: File format not recognized
collect2: error: ld returned 1 exit status


Put gzip support behind a feature

My thought is that since flate2 is now used when building rust, having the gzip code behind a feature might be nice, so it can be disabled for crates that don't use it (like rustc) to cut down on compile time.

Can you quantify the amount of build time attributed to gz support?

I'm going to close this for now as I don't think there's much benefit to be gained, but let me know if I'm wrong!


Please enable discussions on this repo.

@kevmoo

CC @liamappelbe @mit-mit – thoughts?

Fine with me

done


[Question] Longhorn and disk allocation for K8s cluster PV's

What I want to setup with Harvester v1.02 is a multi-node (3 bare metal systems for starters) Harvester cluster running a few plain vanilla VM's and 2 Kubernetes (RKE2 and/or K3s) clusters. I am struggling with the disk configuration for such a setup.
The physical configuration details: 3 bare metal nodes with 20 cores each, 128GB RAM, 1TB NVMe disks for Harvester installation (and some generic VM storage), 4x 8TB SSD for Kubernetes PV storage on each node.
The vanilla VM workloads are straightforward. I can just give them a volume from the Harvester (Longhorn-based) storage created during Harvester installation and let them run. One question I have to make sure I understand the architecture: are these volumes - that are based on the default Harvester/Longhorn storage created at install time on the NVMe disks - replicated across the 3 physical nodes? So, can I just failover and let it run on another node?
The real confusion comes from the Kubernetes storage configuration. I have created a 6 node RKE2 cluster and want to provide that cluster with persistent storage (PV/PVC) that is replicated across all Harvester nodes/hosts so I can leverage the HA/Failover features. As an example scenario: when running a pod on Harvester node 1 which has persistent storage that fails-over to Harvester node 2, its persistent  storage should be available on node 2 as replicated storage when the pod spins up there.
Now the confusion...
Longhorn is part of the Harvester setup and I was wondering if I could/should use that to add those 4 SSD's to each Harvester host/node and create Harvester/Longhorn volumes for the cluster VM's to provision K8s PV's. Also, when adding those 4 disks to the Harvester host (or combine them with LVM), will any LH volume created out of that and assigned to a K8s cluster VM/node be covered by Longhorn replication across the Harvester nodes?
Or...
Should I install Longhorn on the RKE2 cluster and somehow(?) attach the disks to the VMs of that cluster, mount them in the VM, and add them to Longhorn running in the Kubernetes Cluster?
Or...
Should I add the disks to the Harvester nodes, create volumes in Harvester/Longhorn and add those volumes to the Kubernetes nodes/VMs to create PVs?
I suppose there are multiple options, but what are the key pro's and con's when it comes to performance (loss) and redundancy/failover (particularly across Harvester nodes)?

In case you give the 8 TB disks to the Harvester "longhorn" and use them via Harvester CSI in the downstream cluster I believe you have more flexibilty especially because you can add additional clusters and workload to the environment without having the large 8 TB disks locked to a subset of VMs..
Let Harvesters Longhorn distribute the data and take care about fault tolerance - yes - Longhorn will create three replicas of the volumes per default and distribute them among the physical nodes.

https://github.com/harvester/harvester/issues/3342
We have 4 node cluster, on one node I have added a 40 TB NFS disk . On longhorn I can see the space is scheduled and shows the size of 40 TB . when I try to create a VM on that disk the volume or replica creation getting failed .
I read a doc and it says as below  -
Longhorn will detect the storage information (e.g. maximum space, available space) about the disk automatically, and start scheduling to it if it’s possible to accommodate the volume.


Create Dijkstra's-Algorithm.cpp

Hacktoberfest! 🎊🎈
🎉 Have you read the Contributing Guidelines? 🤔
Yes, I have read the contributing guidelines.
📝 Description
added the Shortest path Algorithm
✅ Checklist

[ ] I've read the contribution guidelines. 📚
[ ] I've checked the issue list before deciding what to submit. 🔍

Hi there!
I am the Mentor of this project.
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:
Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.
Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions

Hi there!
I am the Mentor of this project.
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


Move modal from head to footer

Questions
Answers

Description?
The modal is put to the header section with this PR it's in the footer

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/25434

How to test?
For this test you need to update the version of the module and made an update. After you need to check if module work and the modal is not on the header.

Possible impacts?
Please indicate what parts of the software we need to check to make sure everything is alright.

Hello @okom3pom ,
Sorry for the delay in the repsonse.
I didn't manage to see the fix.
I did the following :

install module blockwishlist
install PR #132
I could'nt upgrade to 2.0.2, v2.0.2 wasn't available.

Am I missing something ? ^^
Thanks!

@florine2623 I think you just have to install the module using this PRs branch, and it just should work as usually!

Hello @okom3pom ,
Thanks for the PR !
The block is moved to the body : OK
But I'm facing an issue, I can't add any product to my wishlist with this PR.
Here's my screenrecord : https://watch.screencastify.com/v/A19M9Fv0WRIBDv5ieYOT
Without the PR it is OK :
https://watch.screencastify.com/v/NRuaedCcll5viMCqlZY7
Could you take a look ?
Thanks!

Hello @florine2623
The update is to test if the hook is added, if you don't run update module don't work.

install module blockwishlist
install PR Move modal from head to footer #132
Change the version number to  2.0.2 ( ici )
And makes an update of the module

Or you can just fork my branch and make a new install
Possible it's a DEV QA ?

@florine2623 @okom3pom I can do the QA if needed

Hello @okom3pom @NeOMakinG ,
Thanks for the details :)
It is all good to me ! QA approved ✅

TThanks @florine2623 & @okom3pom


fix: Content Manager, Click outside the filter popover does not close it

Fixes https://github.com/strapi/strapi/issues/16381
What does it do?

Adds onClose to Popover component, which would be triggered whenever the user clicks outside the popover dropdown.

Why is it needed?

To Support toggling the visibility of the popover whenever a user clicks outside the popover.

How to Test

Open the popover  component in the storybook.
Click on the button to open the popover menu.
Click outside the popover menu to close it. Notice that it closes as expected.

Demo
https://user-images.githubusercontent.com/7220167/235848848-7f7feaea-59a7-4b90-aa21-d0391c29a85d.mov

IMO we should use the DismissibleLayer component.

Hi @joshuaellis,
The popover component has been updated to use DismissibleLayer  component.


Update setup.cfg to 5.2.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.50%. Comparing base (6db2bfc) to head (50920cf).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #664   +/-   ##
=======================================
  Coverage   93.50%   93.50%
=======================================
  Files          20       20
  Lines        2125     2125
=======================================
  Hits         1987     1987
  Misses        138      138

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


KeyError: 'chr1'

Hi Jeremy,
I successfully installed the package, then when I tried to run the example code, I happened to have this error
Traceback (most recent call last):
File "liftover/chain_file.pyx", line 72, in liftover.chain_file.ChainFile.getitem
KeyError: '1'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/yuchen/Desktop/CI-RA/Liftover genome version/liftover_genome_DocFile.py", line 26, in
converter[chrom][pos]
File "liftover/chain_file.pyx", line 74, in liftover.chain_file.ChainFile.getitem
KeyError: 'chr1'
Is there any idea why is error appear and how may I fix this? Thanks for your time and help.

What genome assemblies are you converting between? Or, what chain file are you using, if you are doing that instead?
It can't find chromosome "1" in converter[chrom], so it then attempts the alternate chromosome ID of "chr1", which also fails. If you're converting between human genome assemblies this should have worked, other species may have lack a chr1 though.

Thanks for your quick reply Jermy. I figured out that I am running your sample code without giving it a chain file. I think that's why.
After I run the code without 'ChainFile' part, it runs smoothly.
Sorry for the late reply. Thanks for your answer!


Added Aptech Computer Education

This is the email domain for  S.I.T.E Branch inKarachi

@haseebmallik Please provide us with:

the university official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students.

This is official website of aptech computer education
http://aptech-education.com.pk/.
Aptech has many branches in a city so they have separate domains for emails
in @aptech{branch-code}.{TLD}.
For example the email domain for Garden, Karachi area is @aptechgdn.com
http://aptechgdn.com, similarly my branch is S.I.T.E Karachi area so I
was given @aptechsite.net http://aptechsite.net
Attached is a snap of my email profile as a proof.
Regard
Haseeb Malik

http://webcache.googleusercontent.com/search?q=cache:M_nxEOY0ZIEJ:aptech-education.com.pk/+&cd=1&hl=en&ct=clnk&gl=pk
2.
https://www.google.com.pk/search?hl=en&q=related:aptech-education.com.pk/+aptech+computer+education&tbo=1&sa=X&ved=0ahUKEwiBi_PvsuXWAhXKmLQKHQz2BvUQHwgpMAA
On Mon, Oct 9, 2017 at 5:13 PM, Philip Torchinsky<EMAIL_ADDRESS>wrote:

@haseebmallik https://github.com/haseebmallik Please provide us with:

the university official website URL, if different from the domain
you are submitting
an URL of a page on the official website where an IT-related
long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK)
showing that the university recognizes the domain which you are submitting
as an official email domain for the students.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/3542#issuecomment-335139936, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aeo_updQ9m26H4nbPKE0awx-W2lJyIDlks5sqg3mgaJpZM4PyBIa
.

@haseebmallik Thank you for the details! Could you please provide us with the link to the long-term (> 1 year) courses? This page (http://aptech-education.com.pk/courses_includes/stc_javaI.aspx) says that Java course, for example, lasts for 48 hours, which is far less than usual 1-year-long courses which JetBrains tools are necessary for.
If there are just short-term courses at your school, it makes sense to use trial versions of the tools (they are valid for 30 days, and can be prolonged if necessary - you can email<EMAIL_ADDRESS>to get an extended trial.

Please check this http://aptech-education.com.pk/accp_ee.aspx
Thanks,
Regard
Haseeb Malik
On Tue, Oct 10, 2017 at 2:28 PM, Philip Torchinsky<EMAIL_ADDRESS>
wrote:

@haseebmallik https://github.com/haseebmallik Thank you for the
details! Could you please provide us with the link to the long-term (> 1
year) courses? This page (http://aptech-education.com.
pk/courses_includes/stc_javaI.aspx) says that Java course, for example,
lasts for 48 hours, which is far less than usual 1-year-long courses which
JetBrains tools are necessary for.
If there are just short-term courses at your school, it makes sense to use
trial versions of the tools (they are valid for 30 days, and can be
prolonged if necessary - you can email<EMAIL_ADDRESS>to get an
extended trial.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/3542#issuecomment-335415532, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aeo_urAPMZLtuJQfQ6vioJKqZ_Vh-op9ks5sqzjFgaJpZM4PyBIa
.

@haseebmallik Thank you very much for all the details! Pull request merged. Thank you!

Thank you so much.
I have friends at other branches of Aptech who might be interested in this
so I want to make more pull requests for their branch domains as well.
Regards,
On Tue, Oct 10, 2017 at 3:18 PM, Philip Torchinsky<EMAIL_ADDRESS>
wrote:

@haseebmallik https://github.com/haseebmallik Thank you very much for
all the details! Pull request merged. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/3542#issuecomment-335427995, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aeo_uubbKzQW4jGbzFbfsRxGuBiTJ0a6ks5sq0RfgaJpZM4PyBIa
.


Add mutation testing to the JavaScript client tests.

Hi,
we should add mutation testing to the tests for the JavaScript client.
Mutation testing will allow us to see the quality of our tests.
Regards
Simon

We currently have 342 passing (410ms) tests for the dolphin-platform-js 1.0.0-CR.4 with a coverage of >=90%
Current command for Mocha tests is: npm test
Current command for Mocha tests with code coverage is: test:coverage
We also do mutation testing for the dolphin-platform-js repository. The command is: test:mutation


MRG: Document special members

This adds documentation of __contains__, __getitem__, __iter__, and __len__ to our docs.
Closes #2998.

See examples for [Raw] (https://circle-artifacts.com/gh/mne-tools/mne-python/998/artifacts/0/home/ubuntu/mne-python/doc/_build/html/generated/mne.io.Raw.html) and [Epochs] (https://circle-artifacts.com/gh/mne-tools/mne-python/998/artifacts/0/home/ubuntu/mne-python/doc/_build/html/generated/mne.Epochs.html).
Ready for review/merge from my end.

Coverage decreased (-0.1%) to 90.747% when pulling 402dfaa7df548dbcc673b78c3f909be4cd525ae0 on Eric89GXL:doc-special into 38aac46012694c941e8255f2e1f7476c7b51c000 on mne-tools:master.

renders great on circle
thx @Eric89GXL !


UWP rotate pin image

FEATURE REQUEST / SUGGESTION
Bing maps does not support pin rotation so the only way how to rotate pin is rotate image.
Could we make feature to rotate pin?
SUMMARY
I want to create feature that will reflect pin rotation as on android and iOS.
PLATFORMS
which platform do you want?

[ ] Android
[ ] iOS
[x] UWP

I think it is difficult. Bing maps SDK is very cheep.


** A huge THANK YOU **

Thanks for your work! I was missing so much this plugins for v3!!
Congrats!!!

Thanks @zzseba78 – appreciate that!


Flutter Widget Inspector doesn't work with new kernel const format

The flutter widget inspector transform expects to be able to access the original const constructors.  It can't do that with new consts.
Per @mraleph : Flutter 3xHEAD started failing exactly at the enabling commit. [https://ci.chromium.org/p/dart/builders/ci.sandbox/flutter-engine-linux/2068]
@jacob314 is investigating if there is a way to proceed.

We discussed this on the front-end team, and here's our proposal for fixing it:

Add a flag to the front-end CompilerOptions which will make the constant evaluator leave constructor invocations unevaluated (as constructor invocations, rather than the InstanceCreation nodes they are usually translated into when unevaluated).
Enable the flag when compiling code that is to be transformed by the Wdiget transformer.
Instantiate a constant evaluator in the Widget transformer.
Make the Widget transformer recurse into unevaluated constants to find (and transform) the constructor invocations inside. When it comes back out, it will call its constant evaluator to evaluate the constant. It needs to do so for all constants (not just the unevaluated ones) to do correct canonicalization of all constants.
Also explicitly evaluate all new constants created by the Widget transformer (if they are not already inside a constant).

@jacob314 what do you think of this plan? It means the front-end run will need to know whether this transformation is happening later, so those two steps can't run independently. Does this fit how the compilation process in the Widget Inspector works already?

Can you describe the benefits of this plan relative to running the Widget Inspector transform before any const evaluation?
What do you expect the performance impact of this proposal will be? The kernel transformer tracking widget creation locations needs to be fast as it is run as part of all debugging runs of flutter applications initiated by IDEs.
If I'm understanding it correctly consts like
const [1,2,3]
const {'a': 3, 'b': 5}

would still be evaluated before the widget transformer
but consts such as
const Text('foo')

and
const [Text('foo'), Text('bar)]

would not be evaluated. Is that correct?

The overall issue with running the transformer before constant evaluation is that the CFE is, by design, a black-box translation from Dart to Kernel, and running external transformations in the middle of the translation exposes internal implementation details that are not meant to be part of the public API, which constrains the ability of the CFE to change its implementation in the future.
Specifically, in this case:

The fact that constant evaluation runs as a separate transformation is just an implementation detail. This is not the most efficient way to do it (mostly for cache reasons), and we would like to optimize this going forward.
Constant evaluation is responsible for some internal desugarings (e.g. for UI-as-code constructs), which means that before constant evaluation, there will be nodes in the tree that are internal to the CFE and not understandable by any external transformations.
In a separate compilation scenario (i.e. Flutter Web), some component might not refer to the Widget class at all, which means it does not show up in the ClassHierarchy. As I understand it, this was the issue that was hit during the flag flip just before Easter. It might be possible to work around this somehow, but that will put even more constraints on the internal workings of the CFE.

As for the performance: the constant evaluations themselves will be work that is just shifted from the first constant evaluation, so those on their own should not make much difference.
What could make a difference is that the constants need to be re-canonicalized. The constants produced by the constructor invocations (transformed or not) can never hit constants not containing constructor invocations, but the Widget transformer creates some new constants (representing the positions) that might collide with existing constants. Thus, all constants must be revisited to be considered for canonicalization.
We have plans to make the canonicalization more flexible, for instance to support re-use of the canonicalization cache, which would negate this overhead, canonicalizing every constant just once in any case.
Your examples of evaluated and not evaluated constants are correct. The unevaluated ones will still be wrapped in ConstantExpression nodes with UnevaluatedConstant children. This makes the points at which to do perform constant evaluation easy to recognize.

Ok this seems workable. Let me know when you have it working enough end to end to test the performance. If there are performance issues, another option is to use a simpler scheme for the location ids. For example, I suspect we would get a performance win by switching to integer ids and potentially providing a separate server side API to convert between the integer ids and actual locations instead of storing the complex const Location objects. If need to go that route we will need some lead time as it will require non-trivial changes to Flutter.

High level, the existing tests in package:flutter will validate correctness and the time delta running
flutter test
vs
flutter test --track-widget-creation

will gate whether the performance is good enough to ship. In general the time running with --track-widget-creation should be no more than 20% slower than without the flag and it would be very valuable if we could reduce the slowdown further.

To follow up based on offline discussions:
The main blocker to running the transform earlier in the pipline is the ClassHierarchy. The good news is that we want to stop using the ClassHierachy in the Kernel transformer anyway to improve performance.
Prototype CL removing the class hierarchy.
https://dart-review.googlesource.com/c/sdk/+/100408

Another blocker for running the widget inspector transformation before constant evaluation is that unevaluated constants contain Fasta-internal syntax that the Kernel transformation APIs can't handle.  I've marked this as blocked on solving that isssue.

Support for running the widget transformer before constant evaluation has landed in https://dart-review.googlesource.com/c/sdk/+/101987. It is already enabled for Flutter Web in DDC (and the old calls to the transformer removed).
For Flutter, it is controlled by the new trackWidgetCreation named parameter to the FlutterTarget constructor. This is off by default and currently not enabled by any callers. Flutter should set this flag to true where appropriate and remove existing calls to the transformer.

A CL is out for review here: https://dart-review.googlesource.com/c/sdk/+/102920.
@jacob314 may be OOO now; if so, I believe that @terrylucas will take over that CL. I'll confirm.

That CL will fix the issue with a performance improvement instead of a
regression.
On Tue, May 21, 2019, 8:52 AM Devon Carew<EMAIL_ADDRESS>wrote:

A CL is out for review here:
https://dart-review.googlesource.com/c/sdk/+/102920.
@jacob314 https://github.com/jacob314 may be OOO now; if so, I believe
that @terrylucas https://github.com/terrylucas will take over that CL.
I'll confirm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/36640?email_source=notifications&email_token=AAJLQPBNTVPSZEW4537ECGLPWQLEFA5CNFSM4HGDS6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4LMHA#issuecomment-494450204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJLQPCLFKGV7NHO24RG5A3PWQLEFANCNFSM4HGDS6QQ
.

This PR enables the new transformation in Flutter: https://github.com/flutter/engine/pull/8994

@terrylucas Assign this to you for completing the remaining work.

@terrylucas - can you please update?

I committed Jacobs CL and updated

Is there anything remaining on this issue, @terrylucas ?

Not that I'm aware of Travis tests passed, Flutter engine works and
DevTools inspector works as well.
On Tue, May 28, 2019 at 8:45 AM Dan Grove<EMAIL_ADDRESS>wrote:

Is there anything remaining on this issue, @terrylucas
https://github.com/terrylucas ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/36640?email_source=notifications&email_token=AAPV5QOYSGQ2APXGL72Z5O3PXVHRLA5CNFSM4HGDS6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMR2VA#issuecomment-496573780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPV5QL6QX6I3QEKDENQFW3PXVHRLANCNFSM4HGDS6QQ
.

Jacob's CLs are committed to Dart SDK and Flutter.

Reopening since the Flutter change was reverted due to a test failure (most likely an error in the test): https://github.com/flutter/engine/pull/9134

@terrylucas any updates on this?

Aske is there anything in the CFE/kernel transformer AST that might be in
the dill file (or something that's not computed until there is a dill file?
As I run the failing test (first time the dill file is deleted) the tests
will fail. After this failure all tests pass. As I debug the tests, when
there's success, the location object is the file name of the widget that
was created.
Vijay mentioned there a dill dump tool - I'm going to look at the dump. If
you think it's interesting to see this dill file I'll attach it too.
On Wed, Jun 5, 2019 at 8:24 AM Dan Grove<EMAIL_ADDRESS>wrote:

@terrylucas https://github.com/terrylucas any updates on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/36640?email_source=notifications&email_token=AAPV5QNITPVSG5E7HDAEJV3PY7LBVA5CNFSM4HGDS6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXACFVI#issuecomment-499131093,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPV5QKCFX6BSIMNRZ3DNW3PY7LBVANCNFSM4HGDS6QQ
.

====================================
Run #1
Flutter test run w/o --track-widget-creation
cd flutter/packages/flutter
flutter test
inside of widget_inspector_test.dart the WidgetInspectorService's isWidgetCreationTracked() is false therefore this test is not compiled w/ track-widget-creation from the kernel transformer point of view.
====================================
Run #2
flutter test --track-widget-creation
inside of the widget_inspector_test.dart the WidgetInspectorService's isWidgetCreationTracked() is true so this test should have been compiled w/ track-widget-creation
There is a dill file generated testfile.dill.track.dill however the test fails because no creationLocation entry can be found (at the top-level same level as children) the getSelectedWidget JSON payload is:
  description: Text,
  type: _DiagnosticableTreeNode,
  style: dense,
  hasChildren: true,
  allowWrap: false,
  objectId: inspector-0,
  valueId: inspector-1,
  widgetRuntimeType: Text,
  children: [
    {description: RichText,
    type: _DiagnosticableTreeNode,
    style: dense,
    allowWrap: false,
    objectId: inspector-2,
    valueId: inspector-3,
    widgetRuntimeType: RichText,
    locationId: 1,
    creationLocation: {
      file: file:///Users/terry/flutter-engine2-git/flutter/packages/flutter/lib/src/widgets/text.dart,
      line: 386,
      column: 21,
      parameterLocations: [
        {file: null, line: 387, column: 7, name: textAlign},
        {file: null, line: 388, column: 7, name: textDirection},
        {file: null, line: 389, column: 7, name: locale},
        {file: null, line: 390, column: 7, name: softWrap},
        {file: null, line: 391, column: 7, name: overflow},
        {file: null, line: 392, column: 7, name: textScaleFactor},
        {file: null, line: 393, column: 7, name: maxLines},
        {file: null, line: 394, column: 7, name: strutStyle},
        {file: null, line: 395, column: 7, name: textWidthBasis},
        {file: null, line: 396, column: 7, name: text}]},
        children: []}
      ]}

====================================
Run #3
When the dill file is generated all run with --track-widget-creation works, a dump of the dill file shows that creationLocation field exist so the tests all run successfully e.g.,
  final wid::_Location creationLocation = wid::_getCreationLocation(value);

Notice after the dill is generated there is a creationLocation (at the same level as children prefix with **)
description: Text,
type: _DiagnosticableTreeNode,
style: dense,
hasChildren: true,
allowWrap: false,
objectId: inspector-0,
valueId: inspector-1,
widgetRuntimeType: Text,
locationId: 10,

** creationLocation: {file: file:///Users/terry/flutter-engine2-git/flutter/packages/flutter/test/widgets/widget_inspector_test.dart,
  line: 803,
  column: 15,
  parameterLocations: [
    {file: null,
     line: 803,
     column: 20,
     name: data}
  ]
},

children: [
  {description: RichText,
  type: _DiagnosticableTreeNode,
  style: dense,
  allowWrap: false,
  objectId: inspector-2,
  valueId: inspector-3,
  widgetRuntimeType: RichText,
  locationId: 4,
  creationLocation: {
    file: file:///Users/terry/flutter-engine2-git/flutter/packages/flutter/lib/src/widgets/text.dart,
    line: 386,
    column: 21,
    parameterLocations: [
      {file: null, line: 387, column: 7, name: textAlign},
      {file: null, line: 388, column: 7, name: textDirection},
      {file: null, line: 389, column: 7, name: locale},
      {file: null, line: 390, column: 7, name: softWrap},
      {file: null, line: 391, column: 7, name: overflow},
      {file: null, line: 392, column: 7, name: textScaleFactor},
      {file: null, line: 393, column: 7, name: maxLines},
      {file: null, line: 394, column: 7, name: strutStyle},
      {file: null, line: 395, column: 7, name: textWidthBasis},
      {file: null, line: 396, column: 7, name: text}]}, children: []}
    ]}

Aske seems like an issue with the CFE either race condition of some fixup of the in memory data is not the same until after a dill is generated.  The ** creationLocation doesn't exist first time test if run.

Talked to Aske he suggested - ” Dmitry found a bug in the transformer which resulted in an invalid override.  It showed in connection with the new top-level type inference that he is working on landing, but it could have implications for the old one as well. Try patching in this CL (without its dependencies) and see if that changes anything: https://dart-review.googlesource.com/c/sdk/+/105245”.
I try patching Dart and rolling a new Flutter with patched Dart (will bring in Ben on how to do).

@stefantsov's transformer fix has now landed i the SDK, so it should be sufficient to just use the newest SDK head to test it against the Flutter change.

I presume Terry will verify this transformer fix.

Tried Dmitry's Dart PR re-built the flutter engine This didn't fix the problem same results.  Sent mail to Aske on other suggestions or areas where I should look?  I’ll drill into Widget Inspector Transformer in kernel to see if I can locate the problem.

Found the problem, with Jacob's help, CL

We are picking up the current dev release as release candidate to begin align with Flutter. We are out of time for D24. This will have to move to D25.

Fix is checked into tip of Dart.  Rebuilding Flutter engine, applying Jacob's engine change.  If all works will have Ben roll Dart into Flutter.

Flutter transformer PR is checked in to use the new kernel transformer and the Flutter bots remained green.


Add vmware anti-affinity for machine sets

What this PR does / why we need it:
This PR introduces vmware anti affinity rule creation, per machine.
To ensure a concurrent safe usage of the vsphere api, the create or update operation are synced via mutex which is only unlocked if the api returns the desired change or a timeout appears.
This feature can be enabled/disabled by setting: vmAntiAffinity: true in the cloud provider spec.
Required Permissions:
AutoDeploy:

Rule:

Create
Delete
Edit

Host:

Inventory:

Modify cluster

Docs required for the updated permissions.
Which issue(s) this PR fixes:

Fixes #1340
What type of PR is this?

/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Add VMs to an Anti-Affinity rule (vSphere only)

Documentation:

https://github.com/kubermatic/docs/pull/1455

/retest

What is the reasoning behind reconciling this based on MachineSets?

/retest

When can we use this machine-controller in KKP v2.23 and v2.22 as well as kubeone 1.6.x?

Since this will require additional permissions and is a new feature, I'm not sure we are planning to backport it as it has the potential to break existing setups. So it would be shipped with KKP v2.23 when it releases.

@WeirdMachine small request, can we maybe add the additional permissions needed in the release note so it will be visible to end users?

When can we use this machine-controller in KKP v2.23 and v2.22 as well as kubeone 1.6.x?

Since this will require additional permissions and is a new feature, I'm not sure we are planning to backport it as it has the potential to break existing setups. So it would be shipped with KKP v2.23 when it releases.

This feature is not enabled by default and won't be controllable in the dashboard in the next release.
However it is possible to enable it in the machine deployment itself, depending on the machine controller version
this should be possible in KKP v2.23


Add CI test to verify there is no upperbound errors amongst dependencies managed through this BOM

Example failure after shared-dependencies BOM was released to 80+ clients:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for com.google.auto.value:auto-value-annotations:1.7.2 paths to dependency are:
+-com.google.cloud:google-cloud-bigqueryreservation:0.3.10-SNAPSHOT
  +-com.google.api:api-common:1.10.0
    +-com.google.auto.value:auto-value-annotations:1.7.2
and
+-com.google.cloud:google-cloud-bigqueryreservation:0.3.10-SNAPSHOT
  +-com.google.api:gax:1.59.1
    +-com.google.auth:google-auth-library-oauth2-http:0.22.0 (managed) <-- com.google.auth:google-auth-library-oauth2-http:0.21.0
      +-com.google.auto.value:auto-value-annotations:1.7.2 (managed) <-- com.google.auto.value:auto-value-annotations:1.7.4
]

This could be avoided if we had a check in shared-dependencies BOM repo to see if dependencies would work compatibly after the BOM is released to the clients.

Will check against bigquery, bigqueryconnection, storage, and spanner repos for now.


subsequent render breaks google map

So at first I thought it was an issue with on-load, but I realized that Google Maps supports using an element not yet in the DOM..
Ok, so I have an example here where subsequent rerenders break the map: https://github.com/knownasilya/pizza-locator/blob/gh-pages/components/google-map.js#L13
To reproduce:

visit https://knownasilya.github.io/pizza-locator/
click "closest locations"

Map disappears on second render..
Looks like the element doesn't get updated properly the second time. Any thoughts?

Second... diving in :)

I can't run this locally - the API key is not set up for it, but it looks like the map is actually there -- just not displaying.
This is possibly due to the fact that you're triggering the resize event (https://github.com/knownasilya/pizza-locator/blob/gh-pages/components/google-map.js#L38) before the view is re-rendered.
I know google maps is a little picky about this.  Suggest wrapping that in a short-lived window.setTimeout call (like 5ms or so) so that it's rendered and triggered?

Oops accidentally closed :)

You should be able to run locally with port 8000, npm start && npm run watch

Use localhost:8000 instead.

I added a timeout, but nothing. You are correct, the map does load but something is still wrong since it doesn't load any tiles..

It's been a few years since I've played with the maps API.  I notice you're making a new map on each call -- every time I've worked with Google Maps I've always just called new once for the page, no matter what I was changing/updating.
Let me give that a shot locally

Good point, I usually do the same.. not sure why I did otherwise..

Ok, I fixed it with your suggestion. See my latest commit.

Awesome!
Yeah, the google maps API is a bit odd sometimes, but this is great :)


Need to use span instead of p tag

Hello World!

Some initial bold text

want my output like this:

  Hello World!

  Some initial bold text

HI ^^, you can redifine the block blots to use span instead of p tag
import Quill from 'quill'

const Block = Quill.import('blots/block')
Block.tagName = 'SPAN'

export default Block

You then need to register your new blot to quill so he use yours and not the default one.
Quill.register(Block, true)
And now you have span instead of p

As I needed the  along with the I did the following edit, hope it helps who needs it.
in the quill.js or quill.min.js (which ever you include)
find the "h6" and add "span" after it, then the 2nd "H6"and "SPAN" after it, case sensitive.
then in quill.snow.css find 'Heading 6' and the following after the end of the block "}"
.ql-snow .ql-picker.ql-header .ql-picker-label[data-value="7"]::before,.ql-snow .ql-picker.ql-header .ql-picker-item[data-value="7"]::before{content:'Span'}
last step, in your js code where you call for new Quill be sure to set the header as the following


feat: add teatest/v2 to use bubbletea@v2-exp

Will keep this open until we push a bubbletea/v2 release. I think it'd be good to keep both versions available and in separate packages.
Supersedes: https://github.com/charmbracelet/x/pull/191

lgtm, needs to run the scripts to update the CI/dependabot though


Add configurable delay on start of opentherm

My bowler need small pause (about 1-2 seconds) to send ch enabe, temperature etc after an opetherm initialisation. Now I make it using delay in on_boot automation. Wait and set value that I need from saved globals
on_boot:
then:
- delay: 2s
- lambda:  |-
if( id(ch_sw_save) ) id(ch_sw).turn_on();
if( id(ch2_sw_save) ) id(ch2_sw).turn_on();
if( id(dhw_sw_save) ) id(dhw_sw).turn_on();
It's better to have simple init_delay settings in opentherm component

Sorry for the late answer, life's busy sometimes.
What happens if you don't add the delay? The settings such as CH enabled are send every 5 seconds and the various temperature setpoints every 2 seconds. So if the boiler is unresponsive after startup, I would guess it automatically corrects itself?


ocpp 2.0.1 chargingState "Idle" in transactionevent not recognized

The chargingState "Idle" in a transactionevent is not recognized

I'm not entirely sure what you mean. ChargingStateType.Idle has been defined. It's also defined in the schemas. Can you elaborate on the issue? Maybe you give a code sample that shows the problem

Apologies, it was due to an error on my side.


Fix regression in FBX import caused by Skeleton3D

A change in commit f7fdc87 changed the Skeleton3D "pose" property from PROPERTY_USAGE_EDITOR to PROPERTY_USAGE_NOEDITOR.
This should have had no effect, however it turns out assimp was assigning to the pose property.
This change adjusts the FBX import to only get_bone_rest/set_bone_rest, not set_bone_pose
This PR supersedes #41490 - In other words, rather than undoing the cause of the regression, this attempts to fix the root cause in the old assimp FBX importer.
I have tested this on a poorly hand animated FBX, and can confirm that the second part of this patch appears to fix animation issues.

Some comments for @RevoluPowered : This change is on Master because this regression that caused this issue is not yet present in the 3.2 branch. I understand that a fix has a chance of conflicting with a forward-port of #39418 to master, but if the bug is left unfixed, we both risk having a starting state that cannot be tested or compared against... The other thing, is that #39418 still assigns to pose (skeleton->set_bone_pose on modules/fbx/data/fbx_skeleton.cpp line 107:
print_verbose("working on bone: " + itos(bone_index) + " bone name:" + bone->bone_name);
skeleton->set_bone_rest(bone->godot_bone_id, get_unscaled_transform(bone->pivot_xform->LocalTransform, state.scale));
skeleton->set_bone_pose(bone->godot_bone_id, get_unscaled_transform(bone->pose_node, state.scale));

In order to test the effect of this on the FBX rewrite, I started with 3.2 backport by @fire of the Skeleton Inspector (available at https://github.com/fire/godot/tree/skeleton-inspector-3-2 ), and then merged @RevoluPowered #39418 (from https://github.com/RevoluPowered/godot/tree/feature/fbx_final_stage ).
After testing this change has on the FBX rewrite + new Skeleton class, I can confirm that the bug is present in the above code, and again, the fix is to remove the "set_bone_pose" function call. Here are the some screenshots against the same (proprietary) FBX file I have been using to test:
Before:

After:

Hence, this work should still be relevant for the FBX rewrite when it comes time to port to master. I do not think this needs to be addressed in the 3.2 branch, at least not yet.

https://github.com/godotengine/godot/pull/40707 <-- 4.0 port of the FBX importer is here, but it's not got a lot of production fixes it needs from the 3.2 branch, I will update it soon once we resolve a bug found in the document parser.

Thanks!


Add JavaContainerBuilder to jib core

Fixes #1212.
Adds a JavaContainerBuilder class that can be used to build Java-specific containers. Example usage:
JavaContainerBuilder.fromDistroless()
  .addClasses(Paths.get("application/classes"))
  .addResources(Paths.get("application/resources"))
  .addDependencies(
      Paths.get("application/dependencies/dependency.jar"),
      Paths.get("application/dependencies/dependency2.jar"),
      Paths.get("application/dependencies/dependency3-SNAPSHOT.jar)) // Separates snapshots to their own layer
  .addToClasspath(Paths.get("extra/classpath/dir")) // Adds to extra layer, but also adds new directory to classpath
  .setJvmFlags("-Xms512m", "-Xdebug")
  .setMainClass("HelloWorld")
  .toContainerBuilder()
  .containerize(...);

Potential followup issues:

Add a WarContainerBuilder for WAR-specific case, or adjust JavaContainerBuilder to support WARs
Use JavaContainerBuilder in Gradle/MavenLayerConfigurations

Sorry if this has been discussed, but for all of these, what if there are duplicate file names?

I mean I know what happens (only the last file will win and survive), e.g.,
  .addToClasspath("/loser/messages.properties",
                  "/winner/messages.properties")

so my question is if this is what we really intended, and if so, I think we should explain it in the Javadocs.

@chanseokoh I can't remember where it was discussed, but I think this is intended behavior, and you are correct that I did forget to mention it in the javadocs. Will fix.

This LGTM - let's follow up this with having our plugins use this new API and make sure everything works the same as before.


Properly handle case when token doesn't exist or wasn't provided

Ebert has finished reviewing this Pull Request and has found:

2 possible new issues (including those that may have been commented here).
1 fixed issue! 🎉

But beware that this branch is 1 commit behind the Nebo15:master branch, and a review of an up to date branch would produce more accurate results.
You can see more details about this review at https://ebertapp.io/github/Nebo15/annon.api/pulls/233.

Changes Unknown when pulling 117541398f615c5d9932c5fd23abaee55d49368a on gmile:properly-handle-unknown-token into ** on Nebo15:master**.


feat(Icon): introduce 'background' property

Icon ('inverted' variant)
This property will introduce possibility to specify Icon's background color. In contrast with just inverted property being introduced, with background property we will provide all the necessary means to customize look of the icon to the client - without necessity to use heuristics for detecting which foreground color would be more appropriate for the given background one.

TODO

[x] Conformance test
[x] Minimal doc site example
[x] Stardust base theme
[ ] Teams Light theme
[ ] Teams Dark theme
[ ] Teams Contrast theme
[x] Confirm RTL usage
[x] W3 accessibility check
[x] Stardust accessibility check
[x] Update glossary props table
[x] Update the CHANGELOG.md

API Proposal
background: string

<Icon name='...' background='teal' color='white' />

I'm hesitant on this one.  It is adding a CSS properties directly to the public API.  We are targeting an API that is a high level abstraction and implementation agnostic.  It also sets precedent where users will expect other CSS properties to be exposed there: fontSize? fontWeight? etc.

sorry, @levithomason, cannot agree with the fact that we are introducing 'CSS Property' to the interface. If you take a look on the implementation, this property is not equivalent to just adding the CSS property - it does more. For example, it applies padded style to the icon. So, for that reason, one thing that I am absolutely against is to introduce it in styles as CSS property - it is higher level aspect.
The next question is about whether it should be introduced to variables or props. As you might notice, this is introduced in props and is duplicated in props (with props taking precedence). The reason of having it in props is that it will complement color property that is already there (and, by the way, it also while corresponding to CSS name, does much more that just setting foreground color) - otherwise the set of properties won't be consistent to achieve quite common case of circular button with specific background - the one that is used for presence indicator.
So, overall, I think that

asking clients to introduce background as a rule is not a solution - here we are dealing with an aspect that is higher than CSS property by its semantics
introducing it to props makes sense, as with that we will have it being consistent with already introduced color prop

TL;DR
We can merge this for progress.  I'm not sure the concept will hold up, but I don't have a better proposal or path for this work right now.
Would like to share my thoughts as well...

I think I understand your points on background now.  Both the color and background props share CSS properties of the same name, however, both props are trying to name a concept implemented by a component.
In the context of CSS, color sets text color while background sets the background color, however, in the context of a component these are concepts.  A component can apply a color however it chooses.  I can also see how a component could can have a background, more as a shape or additional element opposed to an explicit CSS value only.
I'd like to give more info on the relationship of color and inversion.
Color
Here is a Segment that contains a Button, Menu, and Icon.  Each component is shown with and without color.  Notice how each blue colored component applies color in its own way:

Inverted
The concept of "inverted" is creating contrast.  Here are all the same components, but adding the inverted prop to all of them.  Notice how "inverted" doesn't necessarily mean "use a background".
Also, inverting a component does not make any of its other variants invalid.  The icon can still use color, circular, and bordered variants.  The button can still appear default or basic (reduced complexity) while being inverted.

Background
I would like to see more components and real world usages that use this concept of "add a background" before we add it as a concept to the library.  I also want to be very cautious about adding any new concepts while we're in the infancy of our development.  I want to introduce a staging mechanism where concepts like "background" can be introduced and used, but without automatically becoming first class concepts and APIs.  Something like an opt-in so we can better test things and have slower more confident roll outs.
Conclusion
All said, we don't have a staging system yet for new ideas to thrive.  I also have doubts about whether or not inverted will survive as a concept once we have dark/contrast themes since those ideas seem to overlap.  I wanted to share my thoughts and background to keep us in sync with these idea.  Let's merge with the understanding that this concept of background might change in the near future as we introduce feature staging, theme switching, and more components.

Just to put final thoughts on this. We have agreed that either of these two options would work for us - as well as will be consistent for the client:

provide color and background both as props and variables
provide color and background as variables only

I would suggest the second one, and here is the reason why. If we'll consider the first option, we would have two ways of doing the same thing - and while it is not a cons per se, the problem could arise in the following context.
Suppose that someone is working on higher-order component (composite one), and this work has resulted in the following component tree to be rendered for this:
<ElementType>
    <Icon color='red' />
</ElementType>

There is a quite serious problem with this approach: now there are no ways to customize visual look for Icon component, as prop-provided values will take precedence over variables! This will be quite astonishing surprise for the client, to say the least.
In contrast, an option where these two will be introduced as variables only will open the door for theming (and honoring siteVariables values), as now the following would be possible, with all scenarios of the alternative option being covered as well.
<ElementType>
    <Icon variables={ siteVariables => { color: siteVariables.brand } } />
</ElementType>

Also, if merged component's variables will be passed to the renderComponent function (see discussion here), it will be possible to do the following as well:
...
// note that 'variables' are merged ones!
renderComponent({ .., variables } => (
  <ElementType>
      <Icon variables={ color: variables.color } } />   // inherits foreground color of the parent component
  </ElementType>
)

With that we will be able to significantly reduce amount of siteVariables necessary to handle these cases.
@levithomason, please, share your thoughts on that.

closing as now corresponding PR is introduced to the new repo: https://github.com/stardust-ui/react/pull/47


Fix bug with table display

after refactoring code into separate files and debugging, the table display seems to be broken...

turns out the time information in the data frame was missing in animalAttributes() due to refactoring the code to split things up into separate files. fix included moving the movebankPreprocess() call to before animalAttributes()

fixed by commit d35d593f330ab19ac47362b44c60b81380612754


Typescript compiler output bunch of errors for version 0.6.0-beta.3

Anybody familiar with this error when compiling a project running sequelize-typescript v 0.6.0-beta.3:
node_modules/sequelize-typescript/lib/models/Model.d.ts(133,129): error TS2693: 'T' only refers to a type, but is being used as a value here.

133   static scope<T extends Model<T>>(this: (new () => T), options?: string | string[] | ScopeOptions | WhereOptions<any>): typeof T;

Plus many others similar to this one.
Is there any settings or configuration setup that I am missing?

@bosunolanrewaju Looks like a bug. typeof T is invalid imo. @schmod or am I wrong?

@bosunolanrewaju What version of typescript are you using?

tsc -v 2.4.2 and the only solution is to copy the repository into
node_modules\@types

By the way, here is my tsconfig.json
{
  "compilerOptions": {
    "strictNullChecks": true,
    "rootDir": "./src",
    "lib": ["es2017"],
    "target": "es6",
    "outDir": "dist",
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  },
  "exclude":[
    "node_modules",
    "src/__test__"
  ]
}

@Tower540 @bosunolanrewaju can you try again with TS 2.5.3?
That's what we use internally, and it seems to work.

sorry i don't have this error, i was on the bad thread lol

Looks like you need skipLibCheck": true in your .tsconfig.

alright thanks bro! :)

@schmod According to this issue: https://github.com/Microsoft/TypeScript/issues/204 typeof T is not valid unfortunately

@schmod Typescript version is 2.6.1

v0.6.0-beta.4 is released now


How does it compare to...

I see the FAQ has a section for "How does it compare to...".
How does Pyjion compare to Nuitka and Shedskin?

Nuitka and Shedskin are somewhat like Cython in that they are Python -> C++ transpilers. Pyjion is adding a JIT and thus isn't transpiling to another language.

https://github.com/Microsoft/Pyjion/commit/8c8de01ca133b3eb2f45b199d6a821251db64697

Thanks for the update.


Page loads blank

After the installation and running, it was found that no error was reported, but the web page was loaded and displayed blank, with no content。

Sorry, i run zhe wrong py


Working with maven cli behind a proxy

The settings, as-is, won't work for maven even if you set the proxy server in settings.xml.
This leaves having to set the vars from your cli, a la https://github.com/rimerosolutions/maven-wrapper-example/issues/2 .
I think documentation should be updated for settings the proxies for each tool that is required to get mms all-in-one running.

Unfortunately, we don't have any way to test this right now. Do you know if this only applies to Windows?

Closing issue. Please open a new issue if this is still a problem.

Holy cow!  What's the point of metrics if you close stale tickets?  I
barely got a chance to respond to your question, that has been largely
ignored, before you close it?
No, this isn't just windows.
I also gave the solution in the ticket, so unless you've implemented what
I've asked for OR made an alternative fix, I don't see the justification
for closing this.
Again, if your doing it to drive down metrics because the employer wants
progress, then don't bother.  Your tool isn't ready for primetime if simple
observations regarding issues are summarily ignored.  I feel like I'm on
twitter trying to reason with people here!  Am I crazy?
Please explain the rationale for why you think it's OK to close this, and
waste MY time that I invested in a good faith effort to FIX your product
FOR FREE, absent of actual discussion?!?
On Mon, Jul 9, 2018 at 9:55 AM Jason Han<EMAIL_ADDRESS>wrote:

Closed #153 https://github.com/Open-MBEE/mms/issues/153.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Open-MBEE/mms/issues/153#event-1723631278, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYaehK6X5N3bWSN2eMFF2BzFeGfbD2Cks5uE4sAgaJpZM4PXvp0
.

If 10 months is not enough time for a ticket to be responded to, then I'm at a lose for words. The rationale is that it's been 10 months, and no updates, so it's safe to assume that the issue is resolved or abandoned. This is just a standard practice. It baffles me that you would question this.
The "solution" you gave was for a 5 year old issue on an abandoned fork of an abandoned maven wrapper version. If it worked for you, you're more than welcome to contribute the documentation back. This is open source software. There is no employer monitoring progress via github issues and people can contribute freely to the source code.

Then just close it.  I am more than capable of updating the MOST recent
stuff, but I'd need dialogue first.  But, again, you closed it. Which
baffles me why you care so much that you think I'd want to invest more time
when apparently, I'm the one that tracks your progress?  I just used one
branch as that is what your documentation points everyone to.  Don't be
pissed at me for your documentations lack of clarity (something I'll gladly
help, if there were an OPEN issue).
So MMMM :P  Jk, but seriously, I asked the question, got no response, and
assumed you'd all come back to it when you have time.  A perhaps more
optimal solution is to close, and then redirect me to a NEW ticket that
references closing a stale one, with at least some indication about what
you'd think I should or could do.
That all being said, what you wanna do about it? I can go troll mode and
not contribute as this is my personal time.  Or, you can be a little more
understanding that:
If it worked for you, you're more than welcome to contribute the
documentation back. This is open source software. There is no employer
monitoring progress via github issues and people can contribute freely to
the source code.
On Mon, Jul 9, 2018 at 1:52 PM Jason Han<EMAIL_ADDRESS>wrote:

If 10 months is not enough time for a ticket to be responded to, then I'm
at a lose for words. The rationale is that it's been 10 months, and no
updates, so it's safe to assume that the issue is resolved or abandoned.
This is just a standard practice. It baffles me that you would question
this.
The "solution" you gave was for a 5 year old issue on an abandoned fork of
an abandoned maven wrapper version. If it worked for you, you're more than
welcome to contribute the documentation back. This is open source software.
There is no employer monitoring progress via github issues and people can
contribute freely to the source code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Open-MBEE/mms/issues/153#issuecomment-403616420, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYaevDSZAklXRvyglq424hl7jZyLKytks5uE8JygaJpZM4PXvp0
.


[Bug] cant't find data on skywalking UI

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
OAP server (apache/skywalking)
What happened
the oap service show warn
2023-06-30 09:47:26,535 - graphql.execution.SimpleDataFetcherExceptionHandler -454784 [qtp19578363-34] WARN  [] - Exception while fetching data (/topo) : Service id is empty
org.apache.skywalking.oap.server.core.UnexpectedException: Service id is empty
        at org.apache.skywalking.oap.server.storage.plugin.elasticsearch.query.TopologyQueryEsDAO.loadSpecifiedClientSideServiceRelations(TopologyQueryEsDAO.java:73) ~[storage-elasticsearch-plugin-7.0.0.jar:7.0.0]
        at org.apache.skywalking.oap.server.core.query.TopologyQueryService.getServiceTopology(TopologyQueryService.java:106) ~[server-core-7.0.0.jar:7.0.0]
        at org.apache.skywalking.oap.query.graphql.resolver.TopologyQuery.getServicesTopology(TopologyQuery.java:68) ~[query-graphql-plugin-7.0.0.jar:7.0.0]
        at org.apache.skywalking.oap.query.graphql.resolver.TopologyQueryMethodAccess.invoke(Unknown Source) ~[reflectasm-1.11.7.jar:7.0.0]
        at com.coxautodev.graphql.tools.MethodFieldResolverDataFetcher.get(MethodFieldResolver.kt:147) ~[graphql-java-tools-5.2.3.jar:?]
        at graphql.execution.ExecutionStrategy.fetchField(ExecutionStrategy.java:227) [graphql-java-8.0.jar:?]

and my tomcat already connect to oap server
DEBUG 2023-06-30 09:46:40:826 SkywalkingAgent-7-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient : ServiceAndEndpointRegisterClient running, status:CONNECTED.
DEBUG 2023-06-30 09:46:43:826 SkywalkingAgent-7-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient : ServiceAndEndpointRegisterClient running, status:CONNECTED.
DEBUG 2023-06-30 09:46:46:826 SkywalkingAgent-7-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient : ServiceAndEndpointRegisterClient running, status:CONNECTED.
DEBUG 2023-06-30 09:46:49:826 SkywalkingAgent-7-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient : ServiceAndEndpointRegisterClient running, status:CONNECTED.
DEBUG 2023-06-30 09:46:52:826 SkywalkingAgent-7-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient : ServiceAndEndpointRegisterClient running, status:CONNECTED.

but the dashborad no data，and endpoint have number，other is empty！

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

v8 is dead for years.

v7 is older.
We don't have time to even read them.

Can this help with analysis? Thank you so much

No, we won't, official announcement has declared https://skywalking.apache.org/events/v8-eol/


Include study data from prepublished studies for the EBI Search Index data

Include study data from prepublished studies

[ ] need to sort out how to get and present ancestry information
[ ] need to sort out how this data will be annotated with EFO terms, e.g. to select data to add to the Covid portal

ancestry info will be presented the same as in the UI for prepublished studies

There is interest in including prepublished data in EBI search irrespective of output to the COVID portal. Could we add this to the export quite easily?


Slow NosTale performance in comparision with Gallium Nine or Windows native performance

As title says - despite the game being freaking p2w circlejet and I shouldn't play or support it, I decided to do that since I have friends here and I was active in community in the past.
Software information
I use r5 3600 + rx5700 XT setup with 3200mhz 32GB of RAM, so there should not be any CPU bottleneck.
Game works without fps dropdowns on my rig on Windows/Gallium Nine.
The issue is mostly visible when you enter area with many people (for example nosville or the nosmarket area).
Also the FPS counter is beetwen 30-50 FPS in DXVK HUD, which, I think is bad performance since it should be constant 60 FPS for game from mid 2000 era. I tested it on actual 5.13-1 steam proton release.
System information

GPU: rx5700 XT
Driver: AMDGPU (kernel 5.9.6, tested on many other kernel versions before too)
Wine version: 5.13
DXVK version: 1.7.2

Apitrace file(s)
https://share.froggi.es/cedc91762a8e [Password: h4ppycr0w] [8 weeks expiration from today (11 november)]
Log files

d3d9.log:
NostaleClientX_d3d9.log

Are you sure the game doesn't slow down on Windows or Gallium Nine.
The game is really inefficient.

Are you sure the game doesn't slow down on Windows or Gallium Nine.
The game is really inefficient.
Can you reupload your apitrace?

The apitrace is still available, you can download it still for next two weeks.
Also the game doesn't slowdown on Windows/Gallium Nine, the performance is better because in nosville (when you are around many people) you don't get instant framedrops to 30 fps, and on DXVK you do. Also, Gallium Nine have really better performance than DXVK, probably even better performance than Windows, what I saw from my testing.
I want also to note that I tested the game yesterday with mesa-git and the performance issue persists. Gonna answer next questions on VKx discord or here in next week, I'm pretty busy nowadays.

So, I'm here again. The issue remains even on Windows - and I supposed the problem exists in Mesa and AMDGPU/AMDVLK (AMDVLK has the same performance penalty, but thats normal, since it's not very different from AMDGPU). So conclusion is clear - something is wrong in DXVK.
D9 on Windows:

DXVK on Windows:

DGVoodoo:

So, I'm here again. The issue remains even on Windows - and I supposed the problem exists in Mesa and AMDGPU/AMDVLK (AMDVLK has the same performance penalty, but thats normal, since it's not very different from AMDGPU). So conclusion is clear - something is wrong in DXVK.
D9 on Windows:

DXVK on Windows:

DGVoodoo:

Just gonna dump CME's findings from GitHub here:

seems like the game spams SetTransform(.., D3DTS_VIEW,..) like crazy

So I guess the solution would be to calculate the NormalMatrix and the InverseView on the GPU inside the fixed function vertex shader.
@Joshua-Ashton

Now i haven't compared to Gallium Nine, but comparing 1.7.2 to 1.10.1 this seems like it has improved a lot. Unless someone complains maybe this one can be closed? Tho dunno if there are still improvements to be had.
With the fps cap it's hard to compare proper numbers, but the GPU load also kinda speaks for itself.

Linux

Windows

How fast does it run on Windows without DXVK at that spot?

Native windows d9 is slighty worse it seems looking at cpu and gpu usage.

dxvk 1.10.1 windows

Native d9 windows

Some more tests.
Unless my memory is just really shit or i missed it last time then it seems they've added a slider allowing to raise the framerate cap all the way up to 200 in a update.
Here are some tests with dxvk 1.10.1

Windows
Without dxvk & framecap @ 200

With dxvk & framecap @ 200

Linux tests are on proton 5.13 to get around the inputs not working wine bug. Also uses dxvk 1.10.1

Linux
With dxvk & framecap @ 60 (default)

With dxvk & framecap @ 200

The old framerate cap seems to be what caused all the extra frame timing variations as when it is raised to 200 as above you can see the graph is much nicer on windows. Even if the fps doesn't rise much from it.
Native dx9 and dxvk on windows seems to be at least on par and maybe dxvk goes ahead slightly also judging from gpu and cpu usage.
Linux seems to outperform windows with and without dxvk when i raise the framcap to 200 with around 15 - 20 more fps in this short test.
I also made a test where i set the framecap back to the 60 default and you can see the fps instead seems to stick in the low to mid 50's. Also frame timings are worse. So i would suggest raising the fps limit in the settings app.

@Blisto91 Yes, I tried game on 1280x1024 windowed mode and I got similar performance to your, still using r5 3600/rx5700 XT/3200mhz clocked RAM's. But I would not agree that game performs better on Linux - the game performs slighty worse after logging into international first server, to first channel, while being in nosville. I tested both operating systems on FullHD resolution using Xorg. I got around 45-60 fps in Windows and around 40-55 in Linux, so not really big difference, I would estimate it as 5-10%.
I think this game just can't sometimes achieve 60 fps no matter what, I heard from some people years ago that they tried to launch game on NVidia Titan X and had similar results. But, even if Linux has worse performance, it's not really noticeable and, because of that, I'm closing issue by now. If somebody does not agree - please post feedback here.

 My tests weren't totally scientific either hehe.
But at least it seems to not be as bad as it used to be. Hopefully the game itself or wine/dxvk can improve a bit more here and there in the future.

 My tests weren't totally scientific either hehe. But at least it seems to not be as bad as it used to be and the game itself seems to be quite heavy. Hopefully the game or wine/dxvk can improve a bit more here and there in the future.

Sorry for mislead, I redone the tests and maybe because I'm little busy I didn't notice that game has better performance on Linux. On Windows - it has similar performance, it's around 40-50 fps, on Linux - 45-55 fps. I was switching the resolutions and I noted wrong fps scores... (I even use scaling for 4k display, so I must do bunch stuff around while testing). Anyway, as I said - the game engine is not able to achieve 60 fps sometimes no matter what, and if game runs better on Linux than on Windows, it's good reason to close this issue.
Again, sorry for posting wrong results - I really appreciate your work guys, and I hope you all will have good evening. Thanks!


Have Travis CI run on main repo when a PR is submitted to a module repo

We think that this issue arose when the module repos were not fully configured. Now that they are, PR builds should have the same behavior as normal commit builds.


feat: Also publish chart to OCI registry

Description
See linked issue:

The helm chart of trivy-operator is published using the classic approach with a static webserver and an index.yaml (on a separate Repository https://github.com/aquasecurity/helm-charts).
$ helm repo add aqua https://aquasecurity.github.io/helm-charts/
$ helm install trivy-operator aqua/trivy-operator \
     --namespace trivy-system \
     --create-namespace \
     --version 0.20.6

In helm 3.8+ the OCI method went GA:

https://blog.bitnami.com/2023/04/httpsblog.bitnami.com202304bitnami-helm-charts-now-oci.html?m=1
https://helm.sh/docs/topics/registries/
https://github.com/helm/helm/releases/tag/v3.8.0

I'd like to see you pushing the packaged helm chart(s) also on ghcr.io, alongside the container images and trivy-db's.
There is existing code available from multiple Kubernetes projects which could easily adapted:

renovatebot/helm-charts
nextcloud/helm
cloudnative-pg/charts
argoproj/argo-helm
many more ;)

After one implemented this, users can easily install trivy-operator via:
helm install trivy-operator oci://ghcr.io/aquasecurity/charts/trivy-operator --version x.y.z

Related issues

Close #1887

Remove this section if you don't have related PRs.
Testing

I created a second branch feature/chart_oci_publish_FORK_ADAPTION with little adaption of the paths and run it inside my fork:git diff feature/chart_oci_publish..feature/chart_oci_publish_FORK_ADAPTION
diff --git a/.github/workflows/publish-helm-chart.yaml b/.github/workflows/publish-helm-chart.yaml
index d627445..7d7f539 100644
--- a/.github/workflows/publish-helm-chart.yaml
+++ b/.github/workflows/publish-helm-chart.yaml
@@ -7,17 +7,19 @@ on:
    types: [publish-chart]
    paths:
      - deploy/helm/Chart.yaml
+  # Manual trigger is also possible
+  workflow_dispatch: {}
env:
  CR_PACKAGE_PATH: .cr-release-packages
-  HELM_REP: helm-charts
-  GH_OWNER: aquasecurity
+  HELM_REP: aquasecurity-helm-charts
+  GH_OWNER: mkilchhofer
  CHART_DIR: deploy/helm
  KIND_VERSION: v0.17.0
  KIND_IMAGE: kindest/node:v1.21.1@sha256:69860bda5563ac81e3c0057d654b5253219618a22ec3a346306239bba8cfa1a6
jobs:
  release:
    # this job will only run if the PR has been merged
-    if: github.event.client_payload.action == 'chart-release' || github.event.client_payload.action == 'chart-and-app-release'
+    # if: github.event.client_payload.action == 'chart-release' || github.event.client_payload.action == 'chart-and-app-release'
    permissions:
      contents: write  # for peter-evans/repository-dispatch to create a repository dispatch event
      packages: write  # to push OCI chart package to GitHub Registry
@@ -92,16 +94,16 @@ jobs:
            helm push "${pkg}" oci://ghcr.io/${{ env.GH_OWNER }}/${{ env.HELM_REP }}
          done

-      - name: Get latest tag
-        id: latest_tag
-        run: |
-          latest_tag=$(git describe --tags --abbrev=0)
-          echo "::set-output name=tag::$latest_tag"
+      # - name: Get latest tag
+      #   id: latest_tag
+      #   run: |
+      #     latest_tag=$(git describe --tags --abbrev=0)
+      #     echo "::set-output name=tag::$latest_tag"

-      - name: Repository Dispatch Publish docs
-        if: github.event.client_payload.action == 'chart-and-app-release' && !contains(steps.latest_tag.outputs.tag, 'rc')
-        uses: peter-evans/repository-dispatch@v3
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          event-type: publish-docs
-          client-payload: '{"action": "docs-release", "tag": "${{ steps.latest_tag.outputs.tag }}"}'
+      # - name: Repository Dispatch Publish docs
+      #   if: github.event.client_payload.action == 'chart-and-app-release' && !contains(steps.latest_tag.outputs.tag, 'rc')
+      #   uses: peter-evans/repository-dispatch@v3
+      #   with:
+      #     token: ${{ secrets.GITHUB_TOKEN }}
+      #     event-type: publish-docs
+      #     client-payload: '{"action": "docs-release", "tag": "${{ steps.latest_tag.outputs.tag }}"}'

Created a repository to simulate the central helm repository: https://github.com/mkilchhofer/aquasecurity-helm-charts
Executed the workflow without simulating all repo dispatch events
See: https://github.com/mkilchhofer/trivy-operator/actions/runs/8130660226/job/22219118024
Classic chart publish works$ helm repo add aqua-fork https://mkilchhofer.github.io/aquasecurity-helm-charts/
"aqua-fork" has been added to your repositories

$ helm search repo aqua-fork
NAME                    	CHART VERSION	APP VERSION	DESCRIPTION
aqua-fork/trivy-operator	0.20.6       	0.18.5     	Keeps security report resources updated

OCI publish also works$ helm show chart oci://ghcr.io/mkilchhofer/aquasecurity-helm-charts/trivy-operator
Pulled: ghcr.io/mkilchhofer/aquasecurity-helm-charts/trivy-operator:0.20.6
Digest: sha256:abfb2006b259fb160daf5d5b51d90928d37242790a9a89273618d41ec4b50519
apiVersion: v2
appVersion: 0.18.5
description: Keeps security report resources updated
keywords:
- aquasecurity
- trivyoperator
- trivy
name: trivy-operator
sources:
- https://github.com/aquasecurity/trivy-operator
type: application
version: 0.20.6

Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[x] I've added usage information (if the PR introduces new options)
[x] I've included a "before" and "after" example to the description (if the PR is a user interface change).

@chen-keinan I can do that. But I skipped this intentional and wanted to add this as soon as the first chart is published to OCI.

@mkilchhofer should a small and quick change to docs , it will be great to have both so it can get merged together

@mkilchhofer should a small and quick change to docs , it will be great to have both so it can get merged together

@chen-keinan Alright, updated the PR. Is that okay for you like this?


invalid config item -Dio.netty.recycler.maxCapacity.default

netty version 4.1.66.Final
Can not find config item io.netty.recycler.maxCapacity.default in io.netty.util.Recycler. I think it's a invalid config.

@merlimat

Yes. I agree with you. I had a PR. please help to fix it. Pls help to review it. [Improvement] Recycler should use io.netty.recycler.maxCapacityPerThread instead of io.netty.recycler.maxCapacity.default as maxCapacityPerThread configuration in Netty 4.1.x #13563


html5semantic: Add Chrome status for

https://www.chromestatus.com/feature/5633937149788160

Thanks!


fix: moved all-components inside component folder

Tried to fix #27
By default it was also adding all-components in navigation.
So moved all-components to components directory

@ujjwal313  , No it didn't work


Added JSON Upload

Added a button next to "Start Node" field
Handle file upload using file reader, and an anonymous function to preserve async

Addresses issue #24

Hi I apologize for the delay in getting back to you, but this change looks good! I believe the json powering the web runner is quite out of date but I'll merge this and try to update it in the future separately
Thanks for the contribution!


Fix contact params estimation in fixed-base models

If the model.physics_model.is_floating_base is False, with the current version, the whole W_p_CoM variable is returned (shape=(3,)), but it should have shape=()

I believe this has been closed automatically as the target branch was merged upstream. Reopening in ami-iit/jaxsim

Woops, I didn't receive any notification of this PR. I'll check upstream.


Conventions Update Needed: PyBoolNet 2 -> pyboolnet 3

PyBoolNet is now pyboolnet and many of its conventions have changed. We will need to update.
There is a guide here:
https://github.com/hklarner/pyboolnet/blob/master/MIGRATION_GUIDE.md
But it is empty as of now (presumably it will be updated?)

Completed in newest version (3.0.0), see #69


Upgrade to using MUI v5

Describe the desired behavior
Update library to use the latest MUI v5 (@mui/material)
Describe the current behavior
We are using the old version 4.x.
Is this request related to a current issue?
No
Additional Context

Refer https://mui.com/guides/migration-v4/#migrate-themes-styleoverrides-to-emotion

Fixed in #33


mrpt2: 2.11.8-1 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository mrpt2 to 2.11.8-1:

upstream repository: https://github.com/MRPT/mrpt.git
release repository: https://github.com/ros2-gbp/mrpt2-release.git
distro file: iron/distribution.yaml
bloom version: 0.11.2
previous version for package: 2.11.7-1

Holding for Iron sync


AzureResourceGroupDeployment file path for "object" parameter in overrideParameters

Required Information
Question, Bug, or Feature?  Question, could be feature request if doesn't exist
Enter Task Name: AzureResourceGroupDeployment@2
Environment

Server - Azure Pipelines or TFS on-premises? Azure Pipelines

Account name: pontifex

Project: EvoqueRehab

Build details: "Reporting CI" - build id = 947

Agent - Hosted or Private: Hosted Ubuntu 1604

Issue Description
I would like to use the Azure resource group deployment task where one of the parameters is read from a JSON file containing a JSON object. looking at az group deployment create I used to do it from the command line by az group deployment create -g EvoqueGraphFunctions-dev --template-file azuredeploy.json --parameters<EMAIL_ADDRESS>From yaml passing the input parameter of overrideParameters: -logicAppDefinition @$(Pipeline.Workspace)/arm/Evoque.definition.json I get the error
"There was an error while overriding 'logicAppDefinition' parameter because of 'SyntaxError: Unexpected token @ in JSON at position 0', make sure it follows JavaScript Object Notation (JSON)"
It's obviously not reading the file but thinking it's a JSON inline object. The file is a logic app definition so I'd like to be able to pass it in.
Task logs
Checking if the following resource group exists: EvoqueGraphFunctions-dev.
Resource group exists: true.
Creating deployment parameters.
The detected encoding for file '/home/vsts/work/1/arm/azuredeploy.json' is 'utf-8'
There was an error while overriding 'logicAppDefinition' parameter because of 'SyntaxError: Unexpected token @ in JSON at position 0', make sure it follows JavaScript Object Notation (JSON)
Starting Deployment.
Deployment name is azuredeploy-20190808-042945-9c71
There were errors in your deployment. Error code: InvalidTemplate.
##[error]Deployment template validation failed: 'The provided value for the template parameter 'logicAppDefinition' at line '1' and column '255' is not valid.'.
##[error]Task failed while creating or updating the template deployment.

Hi @damienpontifex, thanks for reporting this. This feature is not yet supported in AzureResourceGroupDeployment task.

Thanks @anuragc617 is it something that might be supported in the future? And hence keep this open to track a potential future feature?

Agree with @damienpontifex , re-activating the issue and marking enhancement. But I am not sure when we will get to this as this is the first such request we have received.

any update on this?

@damienpontifex @bishal-pdMSFT any update on this?