Enable apparmor on Rancher (apparmor_parser missing)

What kind of request is this (question/bug/enhancement/feature request): enhancement
Following up on an issue I created in the forum (https://forums.rancher.com/t/apparmor-and-rancher-2-x/12763) and related to closed v1.6 issue https://github.com/rancher/rancher/issues/6317
It seems Apparmor is not working on Rancher 2, but surprisingly appears fairly trivial to enable : if /sbin/apparmor_parser exists on the host where the kubelet is running, then bind it into the kubelet container.
This was our previous sleuthing on Rancher 1.x, but it applies equally to Rancher 2.x:

We have AppArmor enabled and working on the host OS, etc.
AppArmor Feature gate is not explicitly disabled, so we have to assume it’s enabled
Neither kube-apiserver nor kubelet logs show anything related to AppArmor being disabled (https://github.com/rancher/kubernetes/blob/v1.11.3-rancher/pkg/security/apparmor/validate.go has some nice errors, not sure if they would be logged though)
We noticed that /sys/kernel/security/ is properly mounted in the kubelet containers on our workers
The binary /sbin/apparmor_parser is not present in the kubelet, although it appears that func IsAppArmorEnabled() requires it to be!
AppArmor on a newly deployed /non-Rancher/ k8s cluster works

Following up on this I copied /sbin/apparmor_parser (x86-64 binary) into the kubelet container docker cp `which apparmor_parser` kubelet:/sbin/apparmor_parser on a worker node, and then ran docker restart kubelet. Suddenly, AppArmor shows now as enabled, whereas previously it was not!
$ kubectl get nodes -o=jsonpath=$'{range<EMAIL_ADDRESS>{.status.conditions[?(@.reason=="KubeletReady")].message}\n{end}'
s10: kubelet is posting ready status
s20: kubelet is posting ready status
s30: kubelet is posting ready status. AppArmor enabled

Further testing (loading an apparmor profile on the worker node(s), and adding the necessary apparmor annotation in a deployment (spec: template: metadata: annotations:) indicates that with the apparmor_parser binary in place, AppArmor now works as intended in the Kubernetes docs! - https://kubernetes.io/docs/tutorials/clusters/apparmor/
Environment information
I tested AppArmor on a cluster deployed using rke v0.2.2 - rancher (k8s v1.13.5 / ubuntu 16.04lts

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.0
 API version:       1.39 (downgraded from 1.40)
 Go version:        go1.12.5
 Git commit:        aeac949
 Built:             Wed Jul 17 18:16:07 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:42:13 2019
  OS/Arch:          linux/amd64
  Experimental:     false

So the obvious question: can Rancher do this out-of-the-box?

Walked right into this one as well when I tried to deploy cert-manager.
I edited cluster.yml as follows:
services:
  kubelet:
    extra_binds:
      - "/sbin/apparmor_parser:/sbin/apparmor_parser"

I'm not entirely sure if this is the best way. Please advise.

Still needed.

still needed

Still occuring on SLES


AWS_AWS Relationship AWS_CLOUDFRONT to AWS_S3

Relevant information
The changes represent AWS_AWS Relationships wrt Cloudfront and S3. Cloudfront requires an S3 domain name. Domain name is available in AWS Config and has been imported into New Relic here - https://source.datanerd.us/beyond/beyond-common/pull/219
The changes establishes relationship between Cloudfront and S3 which is based on the attribute value for domain-name which is S3 URL.
Checklist

[ Yes] I've read the guidelines and understand the acceptance criteria.
[Yes ] The value of the attribute marked as identifier will be unique and valid.
[ Yes] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Waiting on CLA signature and the final decision here. Apart from that LGTM.

This definition is correct and approved. However, we will not merge it yet since the team will still include a capture clause to match distinct CloudFront hosts.
I will keep it marked on waiting-on-submitter-feedback for now, please let's go ahead once it is included.

Updated as per feedback from Javier Noguera


Update @ArrayContentBased to @ReadArrayContent

Poko deprecated the former in favor of the latter.

Yes, nice. I meant to check this on the Renovate bump, but my finger had already pressed the button on merge when the thought occurred to me and I couldn't really do anything but let go.


Minor fix for AD.

@rxwei This is based on what you mentioned in this email thread.

Thanks!

It's not a bug though. We just need a API that allows you to use any function/property while forcing the derivative to be zero.

It's not a bug though. We just need a API that allows you to use any function/property while forcing the derivative to be zero.

Sorry, the "bug fix" commit was referring to the use of _TFGetScalarOrDie in Math.swift, which was missing from the previous PR moving stuff over from stdlib. :)

Got it!

Since this doesn't compile with SwiftPM, I'll have to revert it along with #70 to iterate further. Happy to help with resolving the compilation issues!


WIP: Reporting JSON to Mutation Testing Elements

Forgot to mention: is it possible to parallelize this reporter?


Sysusers only for sysusers

d43e323b4aa9ddace802bd12f3fcc34b7701f53e fixes https://github.com/NixOS/nixpkgs/issues/325052
2710a49adb11016f2e1bb4f3786dc099b99cd315 fixes https://github.com/NixOS/nixpkgs/issues/318365
2ca04530c92866b1868f4963c2cb0c97c6a2e4cc fixes https://github.com/NixOS/nixpkgs/issues/307159
The most important change is that sysusers now will only create system users. You cannot use this when you have normal users! I plan to add a perlless mode to add normal users via systemd-homed in the future.
Also, sysusers is now always executed at runtime even when /etc is immutable and when mutableUsers = false.
closes #328727
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

How will the root user be handled in the homed case?

How will the root user be handled in the homed case?

The root user will always be handled by sysusers

@ofborg test systemd-sysusers-immutable systemd-sysusers-mutable activation-etc-overlay-immutable activation-etc-overlay-mutable

Hi there,
I am afraid this patch has some problems within.
       assertion = !opts.isNormalUser;
        message = "systemd-sysusers doesn't create normal users. You can currently only use it to create system users.";

First of all, the above assertion is pretty cruel to devs, I had no idea which user is blocking my build so adding "${_username}" as a prefix mite be kind to all of us.
Another problem is I build a kexec image with nixos-images by the modules noninteractive and kexec-installer. The former uses perlless and the latter insert users.user.nixos. I do not know any means to remove the nixos user from the installer hence the following uglyness.
 users.users.nixos = {
    isSystemUser = true;
    isNormalUser = lib.mkForce false;
  };
  users.users.nixos.group = "nixos";
  users.groups.nixos = {};

I think there must be an agreement btw the installer in nixos and the perlless otherwise the above error message mite bite us on the long run.
best,
evrim.

       assertion = !opts.isNormalUser;
        message = "systemd-sysusers doesn't create normal users. You can currently only use it to create system users.";

First of all, the above assertion is pretty cruel to devs, I had no idea which user is blocking my build so adding "${_username}" as a prefix mite be kind to all of us.

Makes sense. Could you make a pull request?

I also added your patch to nixos-images: https://github.com/nix-community/nixos-images/pull/261


[libplist/libusbmuxd/libimobiledevice/libideviceactivation/usbmuxd] Update version

Fix pkgconfig files
Rename part of library names
Fix definitions
Fix find dependencies

Continue PR #13558.

Should be okay.

Should be okay.

Sorry, I added comments but forgot to publish them.

@BillyONeal Ready.

Thanks for your contribution!


FSx Netap Ontap not displaying filesystems

The drop down under the FSx Netapp Ontap filesystem section doesn't display the list of filesystems running in the region:

Thanks Sean, tracking it, we'll fix asap

@sean-smith can you add more details about the environment? Region used, PC version, state of the NetApp filesystem (they are filtered based on their state) and so on.

Sure, this is using 3.2.0 and I have the filesystems in region and I've tried both Multi-Az and Single-Az with the filesystem residing in the same AZ. Filesystem is running.

We found the root cause and the fix will ship with https://github.com/aws-samples/pcluster-manager/pull/284.
Until a new version of PCM is released, you can create/update a stack with the pcluster-manager.yaml template from the main branch of the repository.
Thank you.


update README to reflect release of data processing code, manuscript

Updated the README to acknowledge the public release of v.1.0.0 of the disco data processing code, and updated the manuscript information.

found problems in this commit, making a new one


New version: namazso.OpenHashTab version v3.0.2

null
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-No-Executables

No-Executables looks expected as it is a shell extension. Hopefully Executable-Error goes away on its own.

/azp run


Use const value to replace hard coded manifest yaml file name.

For fix issue https://github.com/apache/incubator-openwhisk-wskdeploy/issues/415


[Question] Steps of implementing AAD Workload Identity

Hi,
I have followed https://azure.github.io/azure-workload-identity/docs/quick-start.html and the output are same as the example. But I have few questions about implementing it to our real project:

The steps in quick-start are all steps required to implement AAD Workload Identity?
From my understanding the image (ghcr.io/azure/azure-workload-identity/msal-go) used in deploy-workload is just an example? For a real project, we just need to change it to our image? Do we need to do any other setups or code changes?
From the doc, with AAD Workload Identity, AAD should give access token to workloads, not secrets (e.g. keyvault secret), is that correct? And /var/run/secrets/azure/tokens is the path where the token should be found within the pod?
Does AAD workload Identity only work for kubernetes pods? Can we use it to generate token for API server?
Is there any microsoft alias email that we can contact to start a thread if needed?

Thanks.

The steps in quick-start are all steps required to implement AAD Workload Identity?

Those steps include creating Key vault and providing permissions for the demo, but those steps might not be necessary for you. You'll need to create the identity and provide it access to the Azure resource for your workload. The rest of the steps will be applicable for every workload.

From my understanding the image (ghcr.io/azure/azure-workload-identity/msal-go) used in deploy-workload is just an example? For a real project, we just need to change it to our image? Do we need to do any other setups or code changes?

For your workload, you'll already have a pod spec. You'll need to add the required labels and annotations. Also, your workload needs to use the sdk to obtain a token using workload identity. There are some examples and minimum required versions here: https://azure.github.io/azure-workload-identity/docs/topics/language-specific-examples/azure-identity-sdk.html

From the doc, with AAD Workload Identity, AAD should give access token to workloads, not secrets (e.g. keyvault secret), is that correct? And /var/run/secrets/azure/tokens is the path where the token should be found within the pod?

Not sure I understand this question. Yes /var/run/secrets/azure/tokens is the token path inside the pod and that path is also set as an env var AZURE_FEDERATED_TOKEN_FILE. That env var is used by sdks and can also be used by the workload to know the token path.

Does AAD workload Identity only work for kubernetes pods? Can we use it to generate token for API server?

Can you elaborate on what token is generated here for API server?

Is there any microsoft alias email that we can contact to start a thread if needed?

You can reach out to us via GitHub issues or discussions. If there is something internal, you can reach out to us internally on teams.

For your workload, you'll already have a pod spec. You'll need to add the required labels and annotations. Also, your workload needs to use the sdk to obtain a token using workload identity. There are some examples and minimum required versions here: https://azure.github.io/azure-workload-identity/docs/topics/language-specific-examples/azure-identity-sdk.html

From labels and annotations, seems the only 'Required' one is azure.workload.identity/use ?
Also I'm a bit confused about the Service Account section in this page. If we use AKS I think we can ignore this part?

Not sure I understand this question. Yes /var/run/secrets/azure/tokens is the token path inside the pod and that path is also set as an env var AZURE_FEDERATED_TOKEN_FILE. That env var is used by sdks and can also be used by the workload to know the token path.

Let me try to make the question more clear: I think 'access token' is a different thing from 'KeyVault secrets' (or KeyVault keys), correct? From the doc, the Workload Identity is supposed to get 'access token' for workloads to access Azure resources, while in the example it's getting the KeyVault secrets. I'm confused about this part.
I took a look at the code and found the function GetToken but I didn't see reference of it. Is this the function that we should use to actually get azure access token for workloads? Is there any example of calling it?
Thanks

Oh I think I misunderstood the example. The case should be: in the example in quick-start, the keyvault is the 'Azure resource' that kubernetes pod wants to access. Is this correct?


Mouse Coordinate troubles

https://discourse.vvvv.org/t/mouse-coordinates-in-stride/19324
ravel: Hi there. Something weird is just happening with the mouse Position in the Stride Renderer. If I change the renderer size the MousePosition stays the same proportional according to my screen and not to the renderer window. So the Mouse Pos in the renderer goes from 0 to 0.5 if I change the renderer to half size. F8 and F5 is fixing it again.
bjorn: When going fullscreen on a secondary monitor, the Mouse position in Stride no longer  goes from 0 to 1. In windowed mode it does. Is this a bug?
tebjan: I've seen that before, someone reported it a while ago. It seems that the mouse coordinate scaling isn't updated on every window change. We'll investigate...
bentec: in his game, when resizing the window or going fullscreen, the mouse-ray is off
Originally posted by @joreg in https://github.com/vvvv/VL.Stride/issues/437#issuecomment-848634258

There are two issues:

[ ] on fullscreen the bounds are not updated
[ ] MouseRay can only work with one window


Does anyone find reliable proxies from this project?

I have this project running a cron job every hour and collecting IP addresses and running test bases on those IP addresses. I mostly get timeouts and unreliable IP addresses.
Even if I health checks them using node-fetch with a timeout and HTTP proxies, they are not reliable enough to be used for scrapping multiple times. I am running these tests using node-fetch, puppeteer, and I am still getting the same results.
Have anyone experienced this? I did not expect free proxies to be 100% reliable, but I think they are about 10% (best case) reliable from my testing using HTTPS requests.
Does anyone find reliable proxies from this project?

I have had a similar experience but I don't think its an issue with this project, just the general unreliability of free proxy sources.  The main benefit of this project is that you can collect thousands and thousands of proxies that might work and then like you said, check them for whether or not they work and end up with some that work.
If you keep a database that is updated with a cron job, you should have enough to be able to run some scraping projects with depending on their scale.  The problem with scraping using proxies in general though is that often times they will get banned from the website you're trying to scrape quickly.

I have had a similar experience but I don't think its an issue with this project, just the general unreliability of free proxy sources.

I agreed, the project is great.

If you keep a database that is updated with a cron job, you should have enough to be able to run some scraping projects with depending on their scale.

My cron job was running every 2 hours, and I was just trying to scrape few pages few times every hour or so and that did not work well for me.
I was considering on making an API for free to get these IP addresses automatically, but if not reliable enough for me, it's not worth the effort. :(

Around 5% of the proxies are fine just test them and verify before using them

new proxy list:
http://pzzqz.com


Boilerplate option

I downloaded this MERN boilerplate 2.0 from http://mern.io. Thoughts on using it as a launch point? It uses node 8 though.

I think I am trying to commit this to master instead of a new branch. Canceling for now.


build: pin google-generativeai<0.7.1

Related Issues

temporary fix for https://github.com/deepset-ai/haystack-core-integrations/issues/855

Proposed Changes:
Pin the google-generativeai to a version that works with our integration
How did you test it?
CI
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

Pinning google-generativeai<0.7.1 does not work.
Should be investigated better.


Weird performance issues with firefox

For some reason, firefox' reaction time is vastly worse compared to other environments and applications. Reaction time and graphical update are significantly slower for some reason.

Reproducible with dwm, but not inside Xephyr. Some investigation of the requests firefox sends us should be done.

Seems to be caused by missing reparenting, but couldn't be fixed with a trivial implementation.

Currently impossible to reproduce on debug binaries, testing on release.


Test different versions of React

So using a Github Action Matrix would help solve this.
Something like:
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index bedfb5f..fb48a49 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -14,6 +14,7 @@ jobs:
     strategy:
       matrix:
         node-version: [16.x, 18.x]
+        react-version: [17, 18]

     steps:
     - uses: actions/checkout@v2
@@ -24,6 +25,7 @@ jobs:
         node-version: ${{ matrix.node-version }}

     - run: npm install
+    - run: npm install react@${{ matrix.node-version }}
     - run: npm run build
     - run: npm run lint
     - run: npm test

But the issue is this changes the version of the React we are using in our project. What we really want to do is change the version of React being used in the demo.
We may need to add some e2e tests to the demo if we want to test this.

We want both don't we?
Both to test the accordion works with this version of React (e.g. it won't work with React version before hooks) and also with the demo.

Also need to update the package.json to allow different version of React.


Issue with k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

Documentation needs to be upgrade a Kubernetes cluster created with kubeadm from version 1.19.x to version 1.20.x
https://v1-20.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

/triage accepted
/help

duplicate of:
https://github.com/kubernetes/website/issues/27525
/sig cluster-lifecycle
/close


Change API event_type from enum to string

closes #4608

@itaiad200  Did you test the fix on a previously unsupported hook?

@itaiad200 Did you test the fix on a previously unsupported hook?

Testing it as we speak

@itaiad200 Did you test the fix on a previously unsupported hook?

Testing it as we speak

Tested locally with post-commit and it worked as expected.


Get-NixLog

We should have a command to Get-NixLogs.
It should handle several different log formats, and use the first line / name of the log to detect which format to use.
It should also be "smart aliased", so that calling it with a well-known log name will get results from that log (e.g. sys.log)
It would be nice to provide some filtering parameters, though these should probably be limited.

I can take a look at this.

I have been think about this a bit, and I think that we should do the following
Create Get-NixLog

Use journalctl to get and filter logs as this supports a json format which will make it easier to convert to an object.
Standard across supported versions of Linux where PowerShell would be installed

Create Get-NixLogFile

For older logs that may be based on rsyslog format of logs.
This will be a little more string/text manipulation but should be doable because it is in a standard format.

How about we expose it as Get-NixLog and Get-NixLog -LogFile ? (or some such switch)
Basically the default parameter set would use journalctl, and the -LogFile switch would make it return the fileinfo.
What do you think?

That works as well. Will start with the journalctl portion.

👍


Next/Link causing app to unmount

Describe the bug
For some reason if you use a next/link component and click the same link twice, the entire app will unmount and mount itself, causing some parts of my application to behave weirdly. Upon further inspection, clicking a link your already on will set the locale key on App to null (which is probably what's causing the issue). It seems that this only happens in production (im using vercel).
next-i18next.config.js
module.exports = {   i18n: {     defaultLocale: "en-US",     locales: ["en-US", "sv-SE"],   }, };
Occurs in next-i18next version
10.1.0
Steps to reproduce
I have created a minimal setup repo that's deployed to vercel
Expected behaviour
The app should not unmount if you click on a next/link component twice.
Screenshots
Everything fine

Until you click on the same link again

And what is router.locale?

And what is router.locale?

router.locale stays the same, checked it.

Just to be sure, i made another branch where i removed turborepo, so now its basically a fresh nextjs project with an extremely basic next-i18next configuration, problem still persists. vercel deployment

look like we have a same problem, this issue also happen when use router.push/replace

@JonahLund Can you link to the repo without turborepo?

@JonahLund Can you link to the repo without turborepo?

https://github.com/JonahLund/next-i18next_link_bug/tree/no-monorepo-test

How do I build and run this application in production mode? Can you remove the turbo dependency?

How do I build and run this application in production mode? Can you remove the turbo dependency?

I removed turborepo in the repo i linked, so its just a basic nextjs project, build using yarn run build, i deployed it using vercel.

Update: No need to deploy to vercel. I tested it with a production build locally, the problem still persists. So this is a global issue. Testing the prod build locally: yarn run build, and yarn run start.

Thanks for your help! I have been able to identify the issue. It's this useMemo call. When the same locale is passed multiple times, useMemo is not called, and thus locale remains equal to its instantiated value of null.
@JonahLund Would you be willing to work on a PR for this bug fix?

Thanks for your help! I have been able to identify the issue. It's this useMemo call. When the same locale is passed multiple times, useMemo is not called, and thus locale remains equal to its instantiated value of null.
@JonahLund Would you be willing to work on a PR for this bug fix?

Great! Yeah can do a PR to fix the issue.

I also seem to be getting this issue when running the dev server


Generate Target interface methods

What problem are you facing?

The new Target interface was implemented as part of https://github.com/crossplaneio/crossplane-runtime/pull/103, but the methods required to satisfy its embedded interfaces are not generated by angryjet.
How could Crossplane help solve your problem?

While there is only one implementation of the Target interface at this time (KubernetesTarget), it would be helpful and more consistent with other Crossplane interfaces if we generated the required methods automatically.

Closing this as Target is now slated for removal per https://github.com/crossplane/crossplane/issues/1755


Filter out empty strings as post processing

Let users filter out empty strings as post-processing if they do want to.
Re indices and shapes, the right answer is to have proper ragged and sparse tensor support to tf.boolean_mask.
This is a follow up to issue #26368 . and PR #26475 .

@alextp

@edloper do you have any pointers as to how to implement boolean_mask support for RaggedTensor?

Has there been any movement?

Sorry I’ve been out sick for the past few days.
It’s already implemented. See:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/ragged/ragged_array_ops.py
But it’s not exported yet (via delegation) because the API doesn’t exactly
match the existing boolean_mask op.  In particular it has a new keepdims
argument.
I would like to modify the existing boolean_mask op to add a keepdims arg
(defaulting to false) and to delegate to this if keepdims is true.
-Edward
On Fri, Mar 15, 2019 at 10:46 AM lhendre<EMAIL_ADDRESS>wrote:

Has there been any movement?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/26638#issuecomment-473312191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFhajJ_fNm9j9rBPTYfQMqyXDUl8Igv5ks5vW7JegaJpZM4bsUSd
.

Is this something that you would want help on?

@lhendre I'd happily review a pull request with this change. Do you think you have enough information to open one?

Let me do a little digging and work over the day and Ill get back here with questions

I had some personal things come up over the last two weeks, but this week is looking better to dig into this

I have started working on this and have some stuff down but I want to clarify and make sure I am on the right path.
The existing boolean mask I am modifying to add a keepdims arg(defaulting to false) and to delegate to the ragged ops is here right?
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/array_ops.py
I am a little less familiar with this portion of the code and wanted to check first?  Additionally the ragged function does make a callback to this so I am unsure of it or is their a higher level location?  @alextp and @edloper

Checking in real quick @edloper, I want to make sure this is the correct approach.

Yes, you'll need to make changes to the boolean_mask function in array_ops.py.  However, looking at this a little closer, we might have some issues with circular dependencies that make this more of a pain to do than it would otherwise be.  If you can figure out a good way around the circular dependencies, I'm happy to look at a PR; otherwise, I'll try to look at this sometime in the next couple weeks to see what I can do.

I think we will refactor the code a little to make this circular dependency go away.  So it's probably easiest to hold off on this until we do that.

Its been a while and thought I'd circle back and see if there have been any updates?

Sorry for not updating this thread.  In PR 1366762 I added a "tf.ragged.boolean_mask" op, which preserves the masked dimensions.  (We decided that it was better to add this as a separate op, rather than adding an option to the existing tf.boolean_mask op.)

No Problem, thanks for the update!


Add support context sensitive events

Add support for optionally passing a context with events on the event
bus. This makes it possible for Area, SingleInput and
MultipleInput components to address events to a particular instance
of a Droplet component.

:shipit:


Rollout: env values are not picked up

Bug Description
Given an ArgoCd Rollout with below config
spec:
      containers:
        - env:
          - name: GROUP_INSTANCE_ID
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: ABC
            value: 'someValue'
          - name: JAVA_TOOL_OPTIONS
            value: '-Xms{{.Values.jvm.heap}} -Xmx{{.Values.jvm.heap}} -XX:HeapDumpPath=/dumps'
          envFrom:
          - configMapRef:
              name: {{ template "xyz.fullname" . }}

None of the set env values are available in my process, neither ABC nor any contained in the configmap
Steps to Reproduce
Create a rollout with given spec above
run mirrord on it
check the env variables
Backtrace
No response
Relevant Logs
No response
Your operating system and version
Ubuntu 22.04.2 LTS, Intellij Idea Ultimate 2023.2,mirrord 3.75.3, mirrord plugin 3.56.0
Local process
a java process within Intellij Idea Ultimate 2023.2
Local process version
No response
Additional Info
No response

Thanks for reporting this. Can you share your mirrord.json file? Specifically, do you use the ephemeral feature?

---
target:
    path:
        rollout: service-name
    namespace: namespace
accept_invalid_certificates: false
feature:
    network:
        incoming:
            mode: mirror
            ignore_ports:
                - 8181
        outgoing: true
    fs: read

this is my config, but I just realized that even the configmap mapped env values are not picked up, I'll update the description

Any chance you have more than one container in the target?

In the rollout itself I defined 2 containers

Then it might be mirrord is targetting the other container (not the one you want it to target)
To specify a specific container, change your yaml to be like:
---
target:
    path:
        rollout: service-name
        container: desired-container
    namespace: namespace
accept_invalid_certificates: false
feature:
    network:
        incoming:
            mode: mirror
            ignore_ports:
                - 8181
        outgoing: true
    fs: read

yes that was indeed the issue, sorry about that. Thanks for the help though


Find out which packages depend on a specific package

Nice pkg. Is it able to find out the tree depending on a specific package? Thank you!

Implemented in d276dc5fa. I'll prepare a new release later.


ARROW-9929: [Dev] Autotune cmake-format

Successfully tested on my fork using https://github.com/xhochy/arrow/pull/5


Allow usage of transform and onImport options

Previously the preprocessor was overriding these options for its own
means which prevented a user from passing their own transform and
onImport options.
Now we call the user passed functions by proxy, so that it still works
as expected.
Fixes #36

Don't mind the red x I just wanted to try the new fancy feature :D

Argh great tip with the done in catch. Can't believe I forgot that.
And I did match slashes before but Appveyor fails because of forward slashes on windows.

Appveyor fails because of forward slashes on windows
meh Windows :/ Nevermind the current check is fine ;)

Fixed the catch(done) fail

:ship:


Intermittent build failure on :bugsnag-react-native:verifyReleaseResources Gradle task

Description
Running an android build which depends on bugsnag-react-native
Issue
Encountering a sporadic build failure on the Gradle task :bugsnag-react-native:verifyReleaseResources
Error does not occur reliably, temporary workaround is to rerun build.
Environment
Library versions:
yarn list v1.22.0
warning Filtering by arguments is deprecated. Please use the pattern option instead.
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>✨  Done in 0.76s.

cocoapods version (if any) (pod -v): N/A (android only)
iOS/Android version(s): N/A (build error)
simulator/emulator or physical device?: N/A (build error)
debug mode or production?: N/A (build error)

Error messages:
Execution failed for task ':bugsnag-react-native:verifyReleaseResources'.
> 1 exception was raised by workers:
  com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-linux Daemon #0: Unexpected error during compile '/home/circleci/project/node_modules/bugsnag-react-native/android/build/intermediates/res/merged/release/drawable/abc_spinner_textfield_background_material.xml', attempting to stop daemon.
  This should not happen under normal circumstances, please file an issue if it does.

Hey @jhbertra, do you still get this same error if Bugsnag is not enabled? I am not sure if Aapt2 exception is related to Bugsnag. Are you able to produce a minimal example that can reproduce this error? Additionally, which compileSdkVersion are you using?

Hi @jhbertra,
Were you able to determine that is caused by the presence of Bugsnag in the application?
Closing for now but do let us know if you are still seeing this and we will be happy to reopen and investigate further.


ModuleNotFoundError

Hello
with kalliope 0.6.0 i have the following error
File "/usr/local/lib/python3.7/dist-packages/gmail/__init__.py", line 16, in <module>
   from .gmail import Gmail
 File "/usr/local/lib/python3.7/dist-packages/gmail/gmail.py", line 3, in <module>
   from exceptions import *
ModuleNotFoundError: No module named 'exceptions'

This neuron is based on a lib gmail which is totally deprecated and not python 3 compliant.
It would need to be rewritten entirely.
I think I'll delete it.

Hi
I've made an update here : https://github.com/tom333/kalliope_neuron_gmail/tree/feature/simplegmail
Does it worth a pull request ?

Sure go ahead.


[Bug] [Module Name] Doris custom_sql can't work

Search before asking

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

What happened
I have tested 2.3.5 and 2.3.6 version with
data_save_mode=CUSTOM_PROCESSING
custom_sql="delete from table;
system can't work. I also tested the same function with starocks. It is ok.
SeaTunnel Version
2.3.5
2.3.6
SeaTunnel Config
sink {
    Doris {
        fenodes = "ip***:8030"
        query-port=9030
        password=""
        username=""
        database = "test"
        table = "***"
        batch_max_rows=10240
        data_save_mode=CUSTOM_PROCESSING
        custom_sql="delete from table;"
        doris.config = {
           format = "json"
           read_json_by_line = "true"
        }
    }
}

Running Command
/seatunnel-2.3.6/bin/seatunnel.sh --config aa.config

Error Exception
have no error. all the data have been inserted into the database . System can't delete the data from db.

Zeta or Flink or Spark Version
zeta
Java or Scala Version
java 1.8
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

even if I write the wrong sql in custom_sql. System don't issue the error. It prove system don't execute the custom_sql.
this function is seem to have the bug

cc @chl-wxp

@Hisoka-X You can assign it to me, I'll handle it


RemixJS Blog

Changes README file

Update file structure and create a homepage.

@yakubsiyam please resolve the conflicts so we can merge this.


FIX: Revert chat-composer keyUp to keyDown event

In 009f7321bf83699ce0997b04a35b68ab85757717 we changed the composer
key event to keyup instead of keydown. This does not work correctly
for the composer's case though, because we want to prevent the default
behaviour of Enter if we do not hit certain special cases, such as
when we want to a) send the message or b) save the edit to a message.
On keyup, these special events still worked, but they would insert
an additional \n in the message because the Enter key event already
happened.

we want to prevent the default behaviour of Enter

@martin-brennan is it possible to test that? 😃


update actions

Coverage remained the same at 76.037% when pulling 37bf60f08fd9cecd72d076e9b0f34f70ede8cba0 on Rory-Z:test/update-actions into abd65057fc9df58427b38de51b6449449b308159 on emqx:main.


Fix for untestable step in 0069-VCBS-042

Reverts vegaprotocol/specs#1198
As per @wwestgarth the above PR hasn't fixed the issue:https://github.com/vegaprotocol/specs/pull/1198#discussion_r952776108
So let's get it right this time.

Closing as this has been actioned in a different PR


[REVIEW] A Very Mogul Christmas!

Project link
https://github.com/KendallDoesCoding/mogul-christmas

Closing as the user is banned due to abusive language


Is it possible to change Verts Dimension ?

I have a question about whether Is it possible to change Verts Dimension? Because for SMPLX the verts dimension is not the same as SMPL verts. So If I want to use SMPLX, Is it possible to change the verts dimension in your source code?
Thanks.

Hello,
currently it is not possible. I plan to add support for the different body models in the near future: SMPLX, SMPLH, STAR.
The measure.py script is easy to adapt to a different body model, but each body model should have its own measurement definitions, since I rely on the topology of the body model (currently SMPL) to know exactly where to define the measurements.
I am also planning to add an anthropometry module to the mmhuman3d repository (basically integrate this repo into theirs), where all the body models would be supported -- but I'm waiting on the authors to contact me back about the idea -- if you'd like to speed things up, you can maybe add a thumbs up (or comment, or whatever) to let the authors know there is interest in the idea here. Thanks 😊.

Thank you for getting back to me. Please give me some advice or tips to modify SMPLX in your source code.
Thanks.

You would need to change the following:

In measure.py:
a) function create_model  to create smplx model
b) function get_SMPL_joint_regressor to get smplx joint regressor
c) few bits here and there to adapt the code to be able to use SMPLX instead of SMPL
In measurement_definitions.py
a) Change IND2JOINT, LANDMARK_INDICES, CIRCUMFERENCES from MeasurementDefinitions class and
CIRCUMFERENCE_TO_BODYPARTS to reflect the SMPLX joints, landmarks,..
Create smplx_body_parts_2_faces.json, similar to smpl_body_parts_2_faces.json, where you label each face from
the SMPLX model to its body part
download the SMPLX model and put it in data/SMPLX or wherever you find convenient

Thanks @DavidBoja


Color picker in "Raw" mode uses wrong ranges for sliders

Tested versions
Reproducible in 4.3.dev6
System information
Godot v4.3.dev6 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; <IP_ADDRESS>12) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)
Issue description
Color picker in "Raw" mode uses wrong ranges for sliders. They should be 0 -> 1, but instead they are using 0 -> 100.
https://github.com/godotengine/godot/assets/13228932/306284c2-70a4-442c-877a-c4b5045b3da7
Steps to reproduce
Open any color slider, set it to "Raw" mode, move any of the sliders, and observe that the ranges are wrong.
Minimal reproduction project (MRP)
N/A

I thought color raw ranges are from 0 to FLOAT_MAX. Maybe someone tried to make raw colors easier to use.

I thought color raw ranges are from 0 to FLOAT_MAX. Maybe someone tried to make raw colors easier to use.

Whenever I used raw mode in the past, it's been from 0 to 1. And as you can see in the video, the values are clearly expected to be in 0 - 1 range. Setting them with these new ranges gives very washed out results.

There's a way to change slider properties so they slide from 0 to 1 and then you can enter any value.

I'll love to hear a better setting for raw colours though.
You mentioned:

Raw colours range from 0 - 1.
Raw colours can be set to any value.

I'll love to hear a better setting for raw colours though.
You mentioned:
1. Raw colours range from (0 - 1) not like (0 - 100)

2. Raw colours can be set to any value.

The way I see it, there are three aspects to raw colors:

The actual range: FLOAT_MIN - FLOAT_MAX
The normal (non-HDR) range: 0 - 1
The UX

The UX, ideally, should allow for setting to any value within the actual range, while simultaneously communicating the existence and/or relative placement of the normal range.
It's debatable what the ideal UX would look like. It could be anything from using fields instead of sliders, to having helpful labels, to disabling the sliders when a value is explicitly set.
But what I think is bad is the current approach, which:

Fails to communicate either type of range (actual or normal)
Introduces an arbitrary third range (0 - 100) which is meaningless to the actual user task
Prevents the user from setting above 100, and prevents the user from setting negative values, both of which should be allowed (it's allowed in code, and is useful for many graphics tricks).

My personal take on a better UX for this would be:

Make the sliders disabled, and only allow setting component values via the spinners / fields.
Make the sliders still display using a range of 0 - 1, thus communicating the normal range.
Optionally add indicators for when the values are set beyond the normal range.

Make the sliders read-only but still shown. The raw colour channel property is still editable.
show the range of the slider as between 0 and 1 and indicate when exceeding.

@KoBeWi do we have anything in Godot Engine proposals or pull requests that can do this?

Optionally add indicators for when the values are set beyond the normal range.

This exists:

The base color range is 0-1, but higher values are allowed to enable some effects like glow. It's even documented: https://docs.godotengine.org/en/stable/classes/class_colorpicker.html#enumerations

Make the sliders read-only but still shown.

idk what this would achieve.

do we have anything in Godot Engine proposals or pull requests that can do this?

There is https://github.com/godotengine/godot/pull/88072

Optionally add indicators for when the values are set beyond the normal range.

This exists:

The base color range is 0-1, but higher values are allowed to enable some effects like glow. It's even documented: https://docs.godotengine.org/en/stable/classes/class_colorpicker.html#enumerations

Make the sliders read-only but still shown.

idk what this would achieve.

do we have anything in Godot Engine proposals or pull requests that can do this?

There is #88072

See my last post for all the rationale. I understand the base range, and the higher representational range. The issue here is with the 0 - 100 range.
The disabling of the sliders was really to simplify the implementation, because leaving a slider interactable while allowing out-of-range value representation is quite a complicated change from the current implementation.

There is #88072

Thanks for that link though! Will comment there. :)
I don't want this to get derailed into a proposal, because I didn't open this issue intending / prepared to do that. I already closed it.


Create markteplace banner for the plugin page

Create a banner similar to:

This banner should have the following dimensions: 837 × 348


Cannot compile: “/bin/sh: 1: ctags: not found”

  yasm  kernel/symbols.s
   CC   kernel/start.o
   --   Kernel is ready!
  ctag  Generating CTags...! Fatal error encountered.
/bin/sh: 1: ctags: not found
Makefile:246: recipe for target 'tags' failed
make: [tags] Error 1 (ignored)
  ctag  Generated CTags.
/bin/sh: 1: ctags: not found
progval@ion:~/ponyos$ exit
root@ion:/home/progval/ponyos# aptitude show exuberant-ctags
Package: exuberant-ctags
State: installed
[…]

This is a fresh Debian 8.2 system (with git, python3, and make installed).

It looks like the exuberant-ctags package in Debian only provides an exuberant-ctags binary and not a ctags. But this is only a warning (Error 1 (ignored)). Additionally, this is not an issue with PonyOS, but an upstream issue with ToaruOS that has already been reported and marked as WONTFIX.


Enum support

Some of my models have enum fields.
This causes typescript:generate to throw:
Unknown database type enum requested, Doctrine\DBAL\Platforms\MariaDb1027Platform may not support it.

  at ___\vendor\doctrine\dbal\src\Platforms\AbstractPlatform.php:398

I'm not sure why it's not supported, as enums are working fine on my project/setup.

Enums aren't supported by DBAL, which is used for the columns analysis. I'm going to make a driver for it.

Schema::getConnection()
->getDoctrineSchemaManager()
->getDatabasePlatform()
->registerDoctrineTypeMapping('enum', 'string');
        In some of your provider


Feature request: cq:template updater (TBD: Better name)

I have a container component that includes another component. I have added this component to the cq:template of the container component, so that the node will always be present (and will not result in a synthetic resource).
Later on, I change the container component to include an additional component. I add the definition to the cq:template of the container component, so that the node will always be present.
However, the existing instances of the container component, don't have the new component node under it and therefore still result in being synthetic resources.
It would be very nice if we can create a tool that finds all components of a specific sling:resourceType, and then apply the cq:template again. It would be nice if this tool would be configurable/reusable, such as the resource type updater for example.

Hey @henrykuijpers ,
Why don't you just use Sling Pipes for this? This is meant to do migrations like this and is generic instead of this pretty custom use case
Greets,
Roy


valgrind: Fix darwin build

Motivation for this change
Fix the darwin build of valgrind and valgrind-light as part of #29221
Things done

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

[ ] NixOS
[x] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I'm still seeing an issue with the build
clang -DHAVE_CONFIG_H -I. -I..  -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_amd64=1 -DVGO_darwin=1 -DVGP_amd64_darwin=1 -DVGPV_amd64_darwin_vanilla=1 -I../coregrind -DVG_LIBDIR="\"/nix/store/kmrrafjalnj4mbc4b0ykxmbppp6f84cv-valgrind-3.13.0/lib/valgrind"\" -DVG_PLATFORM="\"amd64-darwin\""    -O2 -g -std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align -Wno-self-assign -Wno-tautological-compare -mmacosx-version-min=10.6 -fno-stack-protector   -c -o m_syswrap/libcoregrind_amd64_darwin_a-syswrap-linux.o `test -f 'm_syswrap/syswrap-linux.c' || echo './'`m_syswrap/syswrap-linux.c
clang -DHAVE_CONFIG_H -I. -I..  -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_amd64=1 -DVGO_darwin=1 -DVGP_amd64_darwin=1 -DVGPV_amd64_darwin_vanilla=1 -I../coregrind -DVG_LIBDIR="\"/nix/store/kmrrafjalnj4mbc4b0ykxmbppp6f84cv-valgrind-3.13.0/lib/valgrind"\" -DVG_PLATFORM="\"amd64-darwin\""    -O2 -g -std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align -Wno-self-assign -Wno-tautological-compare -mmacosx-version-min=10.6 -fno-stack-protector   -c -o m_syswrap/libcoregrind_amd64_darwin_a-syswrap-linux-variants.o `test -f 'm_syswrap/syswrap-linux-variants.c' || echo './'`m_syswrap/syswrap-linux-variants.c
clang -DHAVE_CONFIG_H -I. -I..  -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_amd64=1 -DVGO_darwin=1 -DVGP_amd64_darwin=1 -DVGPV_amd64_darwin_vanilla=1 -I../coregrind -DVG_LIBDIR="\"/nix/store/kmrrafjalnj4mbc4b0ykxmbppp6f84cv-valgrind-3.13.0/lib/valgrind"\" -DVG_PLATFORM="\"amd64-darwin\""    -O2 -g -std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align -Wno-self-assign -Wno-tautological-compare -mmacosx-version-min=10.6 -fno-stack-protector   -c -o m_syswrap/libcoregrind_amd64_darwin_a-syswrap-darwin.o `test -f 'm_syswrap/syswrap-darwin.c' || echo './'`m_syswrap/syswrap-darwin.c
m_syswrap/syswrap-darwin.c:9869:8: error: unknown type name 'dyld_kernel_image_info_t'
       dyld_kernel_image_info_t dyld_cache_image;
       ^
1 error generated.
make[3]: *** [Makefile:5666: m_syswrap/libcoregrind_amd64_darwin_a-syswrap-darwin.o] Error 1
make[3]: Leaving directory '/private/tmp/nix-build-valgrind-3.13.0.drv-0/valgrind-3.13.0/coregrind'
make[2]: *** [Makefile:1827: all] Error 2
make[2]: Leaving directory '/private/tmp/nix-build-valgrind-3.13.0.drv-0/valgrind-3.13.0/coregrind'
make[1]: *** [Makefile:829: all-recursive] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-valgrind-3.13.0.drv-0/valgrind-3.13.0'
make: *** [Makefile:698: all] Error 2
builder for ‘/nix/store/c0x9gb1bknxnfhwl1b9f6b4sqgvvk2dr-valgrind-3.13.0.drv’ failed with exit code 2

Hm. Ok. I'm on 10.11.6 and I've got Xcode Command line tools installed. (It seems that sometimes this is a problem) I've heard that sandboxed builds would help me getting more reproducible builds. How can I configure my nix, so I'll get the same build errors?

Is this bzero-patch not needed anymore?

As far as I can tell the patch was  merged in: https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=f6d7adf7e983dea468c8cf337630acce902934e3

@LnL7: I suppose the reason for the build error is the following:
Your build determines you are on macOS 10.12. This makes valgrind use the dyld_kernel_image_info_t type of xnu that was only recently introduced (It seems xnu-3789.1.32?), but we don't ship a xnu in nixpkgs that recent.
So assuming this analysis is correct, I guess this narrows our option down to:

Make the valgrind build think the macOS version is 10.11 regardless the actual system
Add a more recent xnu for 10.12. (Which I'm pretty sure you could teach me considering your contributions )
What would you suggest?

Ok. I've tried to wrap my head around the apple-source-releases.
I think I understand which changes would be necessary to this file to get a more current xnu built. As I'm however a little confused about this file, I'd hope to get some clarifications first.
Initially I thought that as there are multiple os versions listed in the versions attribute that we probably build different versions of all those attributes depending on the host OS.
But now that I've read through it, I have the feeling even though this is split up into all those osx-10.11.6, osx-10.9.5, ... that this os-x versions is actually only ever used in the generation of the store path, but the build is the same no matter the host version.
What is the rationale behind using:
/nix/store/wyyddffl27q7kspvfl4d4h9yagp2smyi-xnu-osx-10.11.6 instead of /nix/store/wyyddffl27q7kspvfl4d4h9yagp2smyi-xnu-3248.60.10?
It seems to make this file more complicated than it actually needs to be. Can't we simply use consistent versions listed on one of those release pages?

@LnL7: Since I've learned that upgrading the xnu kernel might break support for macOS < 10.12, I've instead opted for teaching the valgrind build how to figure out which version of xnu we use in nixpkgs. Build seems to work fine on 10.11.6 at least.

@knedlsepp Indeed, using the same versions of the sources is important for reproducibility and compatibility. We still support 10.10, even tho all of the hydra.org macs are running a more recent version. That's why we define MACOSX_DEPLOYMENT_TARGET=10.10 in the stdenv.
Getting rid of the impurity that looks at the kernel version of the build host is definitely the preferred solution. But we could bump the version of xnu if that doesn't break things for older versions of OSX.

Thank you for your work!
Does this work on Sierra? On my system I get (say running valgrind ls):
valgrind: mmap-FIXED(0x0, 253952) failed in UME (load_segment1) with error 12 (Cannot allocate memory).

I'm running 10.12.6 with no CLT or XCode. I've also tried building valgrind from current master (b9df4c8dec4d) instead of version 3.13.0. That didn't help.

Hm. While this is unfortunate, I suppose it's quite likely that my patch wasn't that helpful after all. Valgrind probably has good reasons to do things differently for 10.12. I guess instead I should have tried bumping the xnu version as this is something I could actually test on my 10.11 system

I've tried bumping xnu and got stuck with build error in coreutils (built as a stdenv dependency):
Undefined symbols for architecture x86_64:
  "_renameatx_np", referenced from:
      _renameat2 in libcoreutils.a(renameat2.o)
ld: symbol(s) not found for architecture x86_64

To fix that I've tried to bump Libsystem and Libc, but that didn't help.
Other possibility would be to supply bumped xnu only for valgrind. Not sure if that can work.


Automatic version updates for v1.32.5 release

Description
Preparing for v1.32.5
For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

I'm sorry but I failed delete the branch after merging the pull request.


Client returns error on intentionally empty file

If a format does not require content - until there is one, such as Localizable strings, the push command currently returns an error.
ERROR: Validation failed
[upload:file] content can't be blank

This could maybe be a notice instead of an error in that case.

So, you suggest making this a warning instead of an error in general? Or just for specific formats?

This appears to be a server-side issue. The client only prints the error message it received from the API:
Empty file upload:
POST /api/v2/projects/a70a690c355ddd8f68321dcfb71971ad/uploads HTTP/1.1
Host: localhost:3000
User-Agent: PhraseApp go (DEV)
Content-Length: 644
Authorization: token 1d9f8050f3d13278481405bb3e25a1cd52b7ec5be22345fb72cfd3e158d0411a
Content-Type: multipart/form-data; boundary=d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9
Accept-Encoding: gzip

--d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9
Content-Disposition: form-data; name="file"; filename="Localizable.strings"
Content-Type: application/octet-stream

--d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9
Content-Disposition: form-data; name="file_format"

strings
--d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9
Content-Disposition: form-data; name="locale_id"

54aaa99c9a9e1bef8d160149d9720d51
--d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9
Content-Disposition: form-data; name="utf8"

...
--d0836fe607b510cf08d634e06622d2f8dbcdc02f3e1175c867b54cf9a7d9--

Response:
HTTP/1.1 422 Unprocessable Entity
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json; charset=utf-8
Cache-Control: no-cache
Set-Cookie: language=en; path=/; expires=Sat, 20 Dec 2036 12:50:58 -0000; HttpOnly
Set-Cookie: current_account=BAhJIg05ZThlZGY1NgY6BkVU--33c6a8bf0791db300890cfe49236d73fa0336fbf; path=/; expires=Sat, 20 Dec 2036 12:50:58 -0000
Set-Cookie: _translate_session=MFVieXlMMGhVcmZuVW5WOUhHT1E3aHZkTnJOSEYzVm1kNzNLT1JSOWZ4eE9xY0l3WUZHYk56ZTFIYmluWVB5ZGR3ZFRrdC8wSHF6Wk8yaFhUZUVmNUNIN3J2aERGNHlkZG5IMXpSSHdRSHpETE9MaStINExUUU5IalFFdllCeVctLWVrMnRkeDZ5TEl4VnkvRittNXJXMnc9PQ%3D%3D--81314cf17276ffcd2e2c9845065f611a755c3c18; path=/; HttpOnly
X-Request-Stats: pid=19278 rev=- uuid=2bbc5ec1-c02e-445e-937e-7918e87b045b action=api/v2/uploads#create etag=- rack=0.064147 db=0.016094/9 db_cache=0.000274/2 x_ua=PhraseApp%20go%20(DEV) x_requested_with=- project_id=3 account_id=1 user_id=1 access_token=58d0411a
X-Request-Id: 2bbc5ec1-c02e-445e-937e-7918e87b045b
X-Runtime: 0.065726
Vary: Origin
Transfer-Encoding: chunked

{"message":"Validation failed","errors":[{"resource":"upload","field":"file","message":"content can't be blank"}]}


skip watchQuery

Fixes an issue we discovered in web (https://github.com/Shopify/web/issues/13938).
(Happening through AdjacentResources in web.)
The query was being run when we wanted to skip it; variables in the query may not be valid yet, so we need to wait until we don't want to skip to watchQuery.

Unsure how to write a test for this 🤷♂

This makes sense. A test you could write here would be to spy on watchQuery and make sure it was never called.

@lemonmade Good suggestion; added tests that do exactly that 👌


Music Assistant doesn't load with 2022.12 core update

What version of Music Assistant has the issue?
2022.12
The problem
Music Assistant doesn't load with 2022.12 core update.
Logs:
Logger: homeassistant.util.package
Source: util/package.py:98
First occurred: 8:34:14 PM (3 occurrences)
Last logged: 8:34:20 PM
Unable to install package music-assistant==1.8.7: ERROR: Cannot install music-assistant==1.8.7 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip available: 22.3 -> 22.3.1 [notice] To update, run: pip install --upgrade pip
How to reproduce
Upgrade to the last core release and restart.
Relevant log output
Logger: homeassistant.util.package
Source: util/package.py:98
First occurred: 8:34:14 PM (3 occurrences)
Last logged: 8:34:20 PM
Unable to install package music-assistant==1.8.7: ERROR: Cannot install music-assistant==1.8.7 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip available: 22.3 -> 22.3.1 [notice] To update, run: pip install --upgrade pip
Logger: homeassistant.setup
Source: setup.py:202
First occurred: 8:34:26 PM (1 occurrences)
Last logged: 8:34:26 PM
Setup failed for custom integration mass: Requirements for mass not found: ['music-assistant==1.8.7'].
Additional information
No response
What version of Home Assistant Core are your running
2022.12
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Seriously? The excuse is that something working, something people used, broke because you where busy working on something that's not released, that's no one is currently using?
Thanks, it's extremely logical thinking. Bye bye Music Assistant.

You are free to contribute to this FREE component any time you like. Bye.

Free is an excuse to be delayed, but free doesn't give you the excuse to have the attitude you have. Which is proof that you shouldn't be making this to begin with, you should delete it and live with the fact that your rationale and logic isn't suited to be in charge of a project, any project.
The delay isn't the problem, obviously. It's your mental state and attitude. Free or paid, you should not be in charge, the logic and reasoning is a huge warning sign for all the millions of problems that are going to pop up in the future (On top of the ton of bugs that already exists).
And yes, bye.

@fjeddy I have filed an official report against you for offensive behavior. You clearly have no idea how open source software works and you do not belong on Github. You have really hurt my feelings. Do notice that I have been working on Music Assistant in the last 3 years in my own free spare time which I could have spent with my family or other hobbies. And yes, there are bugs and issues. They will be fixed by me or any other open source volunteer who wants to get the hands dirty. We do not have a huge pile of software developers and you are the tester as user of open source / free software. With positive feedback you drive us to to make it better and better and correct issues, implement new features. Feedback like this makes me think I should just pull the plug and make it private again for my own selfish use.
There is a choice. You could have gone to a store and buy a ready made product there with a support department you pay for and some good level quality control. Another choice you had was just restoring a backup of HA and wait a few days until MA is compatible with the version that came out just hours ago.
But no instead you decide to troll the very people that make this possible in their free time, besides me that also includes @OzGav who gives this endless and patient support to users.
You should be really ashamed of yourself!

@marcelveldt I think everyone here loves being able to use Music Assistant. I know I make good use of it and love it. For me personally at the moment it is more important than Matter, as I do not have any Matter devices. But in the bigger picture, for the future of Home Assistant, Matter is a bigger thing.
Kudos for spending so much time in making a nice product. Take the time you need and please don't feel rushed, having enough mental rest is more important than any software product.

@marcelveldt No, and just no... It's called critical, constructive feedback, on your priorities. Where your response is "Sorry we broke your entire music and speaker related setup, just wait a couple of days while we priortize putting our name on something else that's not even remotely urgent in the meantime".
I've been in the opensource community for 20 years, and I work as a developer, 12 hours a day, every day. I know exactly how it works, down to the core. And that's the problem. Your attitude.
"Developers" these days have this idea in their head that they can release anything they want, and as long as it's open source, then they can care as little or as much as they want. That's not true. The moment you decided to release this as a plugin, release it as a module for the public to use, then you also committed to actually maintaining it. The arguement "It's free, deal with it", simply doesn't cut it, and that's literally what I'm here telling you. Having the system break down because the developers don't care, is just enough for me to not use it. That's an issue, an issue for you, who released it.
There are thousands of opensource projects where the maintainer has the same attitude you have, and they all slowly die and wither into nothing. Why? Because people can't use something that's not actively being maintained. Opensource or not, it doesn't matter.
Let me just make it crystal clear! My problem is not that it broke down, my problem is not that I have to wait a couple of days. My problem is your initial response, where you whole heartedly claim, without any hesitation. I don't care enough about Music Assistant to make sure it works when there are other more exciting projects I can do instead, that, and that alone, is the problem, your attitude towards your own project.
You are actively choosing to work on a project that no-one is using, a project that is under no circumstances vital or used by a single person in the entire world. And as a consequence, every single install of Music Assistant, every single person who is using it, now has a completely, utterly broken system. Does that sound like some clever use of your time? No.
And seriously, you really need to get of your horse, if you can't deal with the critism I am giving, not towards the code, but towards you as a dev and how you chose to spend the time you spend on opensource projects, then you are just proving my initial point.

For all other people reading this: I will of course provide a fix but the solution is a little less straightforward as I hoped so it takes bit longer. If your life depends on Music Assistant, I'd advice to just wait a few days updating your HA instance.
I've given a more detailed explanation on discord btw for all who care.

@marcelveldtM thanks for everything you have done and continue to contribute. If I can help in a non coding way, please let me know. Take a much time as you need!

@marcelveldt Thank you and appreciate your work.  I will buy you more coffee!  Should we roll back to a previous version of HA first or will the patch fix the current broken state?  No rush but I could go ahead and roll back HA now if that would be the path forward.  Thanks again

@marcelveldt Thank you for all your hard work.    As an embedded SW engineer myself, I understand how challenging a project like this is and you have my respect.  I would love to learn how to be an assistant developer if it would be useful.  My experience is rusty, but very willing to learn if you have a lieutenant that could point me in the right direction.

@marcelveldt Thank you and appreciate your work. I will buy you more coffee! Should we roll back to a previous version of HA first or will the patch fix the current broken state? No rush but I could go ahead and roll back HA now if that would be the path forward. Thanks again

Just roll back to 2022.11 is enough. I will install the patch release as 2022.12 to make it clear it belongs to HA 2022.12.
The patch release will btw also fix a broken situation

@marcelveldt Thank you very much for your effort. Do you know if the integration has problems again?
Since this month's update it doesn't load

Please see the pinned issue https://github.com/music-assistant/hass-music-assistant/issues/1104


Add client methods for epochs

See epochs docs

i can do it

This has been implemented in feat/epochs

ok, I try to impl other feat

Currently working on refactoring and standardizing client methods


Ensure make check is ran in travis

Looking at the travis configuration, it does not actually run make check. It only runs make typecheck which is completely different. I ran into this when I ran make prcheck when developing on python 3. If it fails (as I suspect it will), I will send updates in this PR to make Travis run cleanly again.

Cool. Test failed. Will update the code to get everything passing.

Codecov Report

Merging #345 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #345   +/-   ##
=======================================
  Coverage   89.87%   89.87%
=======================================
  Files          18       18
  Lines        1986     1986
  Branches      240      240
=======================================
  Hits         1785     1785
  Misses        147      147
  Partials       54       54

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6995500...34bc727. Read the comment docs.

@jamesls @stealthycoin Fixed the linters. It ended up being just configuration updates. I tried to be pretty descriptive in the commits and comments. No actual code changes in chalice were needed to get these to pass.


Changing parent Container creates a visual copy of a GameObject

Version

Phaser Version:

Phaser 3.53.1

Operating system:

MacOs

Browser:

Chrome 89.0.4389.90
Description
When a GameObject is moved from one Container to another one, a copy of this GameObject appears rendered at a global position of (0,0).
The expected behaviour is the GameObject to just be rendered according to its own position relative to the parent Container.
Example Test Code
https://codepen.io/mariogarranz/pen/VwPLzjG
Additional Information
I can confirm this issue was not present in 3.50.0.
It could be that issue #5599 is related to this problem.

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

This issue has been mentioned on Phaser. There might be relevant details there:
https://phaser.discourse.group/t/phaser-3-53-1-objects-get-duplicated-when-move-from-a-container-to-another/9167/2

Just built and tested the latest master version and I can confirm it's fixed.
Thanks a lot for the quick response.


Day 10: Cathode-Ray Tube

Codecov Report

Merging #19 (52b654e) into main (b03c505) will increase coverage by 0.04%.
The diff coverage is 98.78%.

@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   98.13%   98.18%   +0.04%
==========================================
  Files          28       31       +3
  Lines        2095     2257     +162
==========================================
+ Hits         2056     2216     +160
- Misses         39       41       +2

Impacted Files
Coverage Δ

lib/solution/src/lib.rs
100.00% <ø> (ø)

lib/solution/src/day10/mod.rs
98.00% <98.00%> (ø)

lib/solution/src/day10/computer.rs
98.73% <98.73%> (ø)

bin/aoc2022/src/main.rs
94.02% <100.00%> (ø)

lib/solution/src/day10/instruction.rs
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


p2p.network flag issue in 0.6.x

Celestia Node version
v0.6.1
OS
Ubuntu 20.04
Install tools
No response
Others
No response
Steps to reproduce it
Im putting both cases here, not all might be bugs:

a user reported no chain head messages on v0.6.1, with start command celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090 --gateway --gateway.addr localhost --gateway.port 26659 --p2p.network mocha

I have done some tests on light node but couldnt reproduce the above no head bug, but found these out:

using
Semantic version: v0.6.2-rc1
Commit: 0ab5df64adb7a1452043ef7677a448ec1b103dfb

Command used: celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090 --gateway --gateway.addr localhost --gateway.port 26659 --p2p.network mocha
2022-12-28T11:13:16.860Z        INFO    badger  v2@v2.2007.4/levels.go:183      All 1 tables opened in 1ms

2022-12-28T11:13:16.862Z        INFO    badger  v2@v2.2007.4/value.go:1158      Replaying file id: 0 at offset: 30344255

2022-12-28T11:13:16.862Z        INFO    badger  v2@v2.2007.4/value.go:1178      Replay took: 1.593µs

2022-12-28T11:13:16.866Z        WARN    swarm2  swarm/swarm_listen.go:29        listening failed        {"on": "/ip4/<IP_ADDRESS>/udp/2121/quic", "error": "listen udp4 <IP_ADDRESS>:2121: bind: address already in use"}
2022-12-28T11:13:16.866Z        WARN    swarm2  swarm/swarm_listen.go:29        listening failed        {"on": "/ip6/::/udp/2121/quic", "error": "listen udp6 [::]:2121: bind: address already in use"}
2022-12-28T11:13:16.885Z        INFO    module/state    state/keyring.go:69     constructed keyring signer      {"backend": "test", "path": "/home/pops/.celestia-light-mocha/keys", "key name": "my_celes_key", "chain-id": "mocha"}
2022-12-28T11:13:16.885Z        INFO    module/header   header/config.go:54     No trusted peers in config, initializing with default bootstrappers as trusted peers
2022-12-28T11:13:16.887Z        INFO    header/store    store/store.go:166      loaded head     {"height": 20481, "hash": "20F686A2E09D0C9C09E9826D7866D9A4E5698869D68D1D8D35D5EA03B6559298"}
2022-12-28T11:13:16.888Z        INFO    header/sync     sync/sync_head.go:39    subjective header expired       {"height": 20481}
2022-12-28T11:13:16.893Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWK5aDotDcLsabBmWDazehQLMsDkRyARm1k7f1zGAXqbt4", "err": "failed to dial 12D3KooWK5aDotDcLsabBmWDazehQLMsDkRyARm1k7f1zGAXqbt4:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:16.914Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWKvPXtV1yaQ6e3BRNUHa5Phh8daBwBi3KkGaSSkUPys6D", "err": "failed to dial 12D3KooWKvPXtV1yaQ6e3BRNUHa5Phh8daBwBi3KkGaSSkUPys6D:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:16.914Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWHYczJDVNfYVkLcNHPTDKCeiVvRhg8Q9JU3bE3m9eEVyY", "err": "failed to dial 12D3KooWHYczJDVNfYVkLcNHPTDKCeiVvRhg8Q9JU3bE3m9eEVyY:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:16.914Z        INFO    basichost       basic/basic_host.go:758 error resolving /dns4/norma.celestia-devops.dev/tcp/2121/p2p/12D3KooWHYczJDVNfYVkLcNHPTDKCeiVvRhg8Q9JU3bE3m9eEVyY: lookup norma.celestia-devops.dev: operation was canceled
2022-12-28T11:13:16.914Z        INFO    basichost       basic/natmgr.go:94      DiscoverNAT error:no NAT found
2022-12-28T11:13:16.914Z        INFO    pubsub  go-libp2p-pubsub@v0.6.2-0.20220812132010-46b2a019f2f2/pubsub.go:640     pubsub processloop shutting down
2022-12-28T11:13:16.915Z        ERROR   node    nodebuilder/node.go:95  starting Light Node: header: not found
Error: node: failed to start: header: not found
pops@val02-tia-t:/home/pops$ celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090 --gateway --gateway.addr localhost --gateway.port 26688 --p2p.network mocha
2022-12-28T11:13:26.137Z        INFO    badger  v2@v2.2007.4/levels.go:183      All 1 tables opened in 2ms

2022-12-28T11:13:26.138Z        INFO    badger  v2@v2.2007.4/value.go:1158      Replaying file id: 0 at offset: 30344255

2022-12-28T11:13:26.138Z        INFO    badger  v2@v2.2007.4/value.go:1178      Replay took: 2.394µs

2022-12-28T11:13:26.143Z        WARN    swarm2  swarm/swarm_listen.go:29        listening failed        {"on": "/ip4/<IP_ADDRESS>/udp/2121/quic", "error": "listen udp4 <IP_ADDRESS>:2121: bind: address already in use"}
2022-12-28T11:13:26.143Z        WARN    swarm2  swarm/swarm_listen.go:29        listening failed        {"on": "/ip6/::/udp/2121/quic", "error": "listen udp6 [::]:2121: bind: address already in use"}
2022-12-28T11:13:26.162Z        INFO    module/state    state/keyring.go:69     constructed keyring signer      {"backend": "test", "path": "/home/pops/.celestia-light-mocha/keys", "key name": "my_celes_key", "chain-id": "mocha"}
2022-12-28T11:13:26.162Z        INFO    module/header   header/config.go:54     No trusted peers in config, initializing with default bootstrappers as trusted peers
2022-12-28T11:13:26.165Z        INFO    header/store    store/store.go:166      loaded head     {"height": 20481, "hash": "20F686A2E09D0C9C09E9826D7866D9A4E5698869D68D1D8D35D5EA03B6559298"}
2022-12-28T11:13:26.165Z        INFO    header/sync     sync/sync_head.go:39    subjective header expired       {"height": 20481}
2022-12-28T11:13:26.170Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWKvPXtV1yaQ6e3BRNUHa5Phh8daBwBi3KkGaSSkUPys6D", "err": "failed to dial 12D3KooWKvPXtV1yaQ6e3BRNUHa5Phh8daBwBi3KkGaSSkUPys6D:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:26.191Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWHYczJDVNfYVkLcNHPTDKCeiVvRhg8Q9JU3bE3m9eEVyY", "err": "failed to dial 12D3KooWHYczJDVNfYVkLcNHPTDKCeiVvRhg8Q9JU3bE3m9eEVyY:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:26.192Z        ERROR   header/p2p      p2p/exchange.go:110     head request to trusted peer failed     {"trustedPeer": "12D3KooWK5aDotDcLsabBmWDazehQLMsDkRyARm1k7f1zGAXqbt4", "err": "failed to dial 12D3KooWK5aDotDcLsabBmWDazehQLMsDkRyARm1k7f1zGAXqbt4:\n  * [/ip4/<IP_ADDRESS>/tcp/2121] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:2121-><IP_ADDRESS>:2121: read: connection reset by peer"}
2022-12-28T11:13:26.193Z        INFO    basichost       basic/basic_host.go:758 error resolving /dns4/libra.celestia-devops.dev/tcp/2121/p2p/12D3KooWK5aDotDcLsabBmWDazehQLMsDkRyARm1k7f1zGAXqbt4: lookup libra.celestia-devops.dev: operation was canceled
2022-12-28T11:13:26.193Z        INFO    basichost       basic/natmgr.go:94      DiscoverNAT error:no NAT found
2022-12-28T11:13:26.193Z        INFO    pubsub  go-libp2p-pubsub@v0.6.2-0.20220812132010-46b2a019f2f2/pubsub.go:640     pubsub processloop shutting down
2022-12-28T11:13:26.193Z        ERROR   node    nodebuilder/node.go:95  starting Light Node: header: not found
Error: node: failed to start: header: not found

same issue if i try to start it as:
celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090 --p2p.network mocha or celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090 --gateway --p2p.network mocha
it then started to work when started with:
 celestia light start --core.ip https://grpc-mocha.pops.one/ --core.grpc.port 9090
Expected result
node working normally
Actual result
on v0.6.1 i couldnt reproduce the no chain head errors, while it seems that if using --p2p.network flag there are issues running the light node as seen above in point 2
Relevant log output
No response
Notes
No response

i see others getting the "no chain head" messages when using the --p2p.network flag

FWIW this issue is not necessarily due to --p2p.network flag usage but related to infrastructural issues we've been having - working on a fix (cc @Wondertan )

ok, if you dont need this issue open youre welcome to close it, especially since you are aware of it already :)


Implement SubWallet connector for wagmi

Implement SubWallet connector for wagmi https://wagmi.sh/

https://www.npmjs.com/package/@subwallet/wagmi-connector


add pages

-Add React Router.
-Add styles in a React app.

Hi @BANCUNGUYE66, can you update your readme to have the Key features section?

Hi @BANCUNGUYE66, Kindly add the key features section to your readme it is missing in your readme 👍🏿

@prolajumokeoni I don't understand how to do that, can you recheck my README.md file again. Thank you!

Microverse readme
Your readme

Please add the heading for key features section and description content


Revert "OLS Workload" fix ci debugging code.

Reverts only changes in test.yml introduced in coiled/coiled-runtime#443

It looks like we have a legit failure in windows https://github.com/coiled/coiled-runtime/actions/runs/3576035693/jobs/6013493204#step:5:269

@gjoseph92 Do you know if this error is expected on windows? I'm not super familiar with the scaled_array_shape utility, but if this is expected to fail on windows?

It should not fail on windows and there's no reason why windows would be related to the failure

It should not fail on windows and there's no reason why windows would be related to the failure

Well I'm not sure what's the reason for the failure, it looks like the nbytes are not calculated properly. I do not have a way to investigate this without a windows machine, nor the time. I think I will skip the test on windows for now and open an issue about it.

I think I will skip the test on windows for now and open an issue about it

Sure, but I don't see a reason why windows would be related to it. Unless it reproduces on windows I'm not sure why we'd skip it?

haven't looked closely so maybe this is unhelpful but should actual_nbytes ever be negative, or is the fact that it is mean there's likely overflow or something like that?

Sure, but I don't see a reason why windows would be related to it. Unless it reproduces on windows I'm not sure why we'd skip it?

It reproduces on windows at least on ci, I ran it 4 times, always failed on windows.

That's bizarre, thanks for re-running it and confirming. I guess it is some sort of overflow issue on windows? Maybe in the np.prod?


Handle cleanup of Viewables in the notebook

Ensures that whenever a cell is deleted the model and corresponding Viewable that are displayed in that cell is cleaned up.
TODO: Work out how to make this work when the holoviews extension is loaded instead.

Codecov Report

Merging #74 into master will decrease coverage by 0.05%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   90.53%   90.48%   -0.06%
==========================================
  Files          23       23
  Lines        3076     3079       +3
==========================================
+ Hits         2785     2786       +1
- Misses        291      293       +2

Impacted Files
Coverage Δ

panel/__init__.py
58.62% <0%> (-2.1%)
:arrow_down:

panel/viewable.py
68.53% <50%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8e0f6d...30fee42. Read the comment docs.


Rename kube-arbitrator to kube-batch

Signed-off-by: Atul Bhosale<EMAIL_ADDRESS>

Travis tests have failed
Hey @k82cn,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
1st Build
View build log

     make

$ make
mkdir -p _output/bin
go build -o _output/bin/kube-batchd ./cmd/kube-batchd/
pkg/scheduler/api/types.go:20:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:27:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:28:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOPATH)
make: *** [kube-batch] Error 1

     make run-test

hack/make-rules/test.sh
Running tests for APIVersion: v1,admissionregistration.k8s.io/v1alpha1,admission.k8s.io/v1alpha1,apps/v1beta1,apps/v1beta2,authentication.k8s.io/v1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1,authorization.k8s.io/v1beta1,autoscaling/v1,autoscaling/v2beta1,batch/v1,batch/v1beta1,batch/v2alpha1,certificates.k8s.io/v1beta1,extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1,rbac.authorization.k8s.io/v1beta1,rbac.authorization.k8s.io/v1alpha1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1beta1,storage.k8s.io/v1,
+++ [1006 01:07:13] Running tests without code coverage
pkg/scheduler/api/types.go:20:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOPATH)
!!! [1006 01:07:14] Call tree:
!!! [1006 01:07:14]  1: hack/make-rules/test.sh:322 runTests(...)
!!! Error in hack/make-rules/test.sh:204
  Error in hack/make-rules/test.sh:204. '((i<3-1))' exited with status 1
Call stack:
  1: hack/make-rules/test.sh:204 runTests(...)
  2: hack/make-rules/test.sh:322 main(...)
Exiting with status 1
make: *** [run-test] Error 1

     make e2e

mkdir -p _output/bin
go build -o _output/bin/kube-batchd ./cmd/kube-batchd/
ramework (from $GOPATH)
make: *** [kube-batch] Error 1

TravisBuddy Request Identifier: 29d95040-c904-11e8-9f05-3b03edf74094

Travis tests have failed
Hey @k82cn,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
1st Build
View build log

     make

$ make
mkdir -p _output/bin
go build -o _output/bin/kube-batchd ./cmd/kube-batchd/
pkg/scheduler/api/types.go:20:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:27:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:28:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOPATH)
make: *** [kube-batch] Error 1

     make run-test

hack/make-rules/test.sh
Running tests for APIVersion: v1,admissionregistration.k8s.io/v1alpha1,admission.k8s.io/v1alpha1,apps/v1beta1,apps/v1beta2,authentication.k8s.io/v1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1,authorization.k8s.io/v1beta1,autoscaling/v1,autoscaling/v2beta1,batch/v1,batch/v1beta1,batch/v2alpha1,certificates.k8s.io/v1beta1,extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1,rbac.authorization.k8s.io/v1beta1,rbac.authorization.k8s.io/v1alpha1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1beta1,storage.k8s.io/v1,
+++ [1006 01:59:17] Running tests without code coverage
pkg/scheduler/api/types.go:20:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOPATH)
!!! [1006 01:59:17] Call tree:
!!! [1006 01:59:17]  1: hack/make-rules/test.sh:322 runTests(...)
!!! Error in hack/make-rules/test.sh:204
  Error in hack/make-rules/test.sh:204. '((i<3-1))' exited with status 1
Call stack:
  1: hack/make-rules/test.sh:204 runTests(...)
  2: hack/make-rules/test.sh:322 main(...)
Exiting with status 1
make: *** [run-test] Error 1

     make e2e

mkdir -p _output/bin
go build -o _output/bin/kube-batchd ./cmd/kube-batchd/
pkg/scheduler/api/types.go:20:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/apis/scheduling/v1alpha1 (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:27:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/api (from $GOPATH)
pkg/scheduler/plugins/hostport/hostport.go:28:2: cannot find package "github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework" in any of:
	/home/travis/gopath/src/github.com/kubernetes-sigs/kube-batch/vendor/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (vendor tree)
	/home/travis/.gimme/versions/go1.10.linux.amd64/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOROOT)
	/home/travis/gopath/src/github.com/kubernetes-incubator/kube-arbitrator/pkg/scheduler/framework (from $GOPATH)
make: *** [kube-batch] Error 1

TravisBuddy Request Identifier: 6f9c0800-c90b-11e8-9f05-3b03edf74094


About OpenBazaar page not opening on first load

When program is loaded for the first time, about OpenBazaar page doesn't open when clicking on its link in menu. If program is closed and reopened, it starts working.
V. 2.0.9

We haven't been able to reproduce this.

I have reproduced it again on 2.0.10 on Windows and MacOs.
You have to do a clean install, create a store, go to menu and click on "About OpenBazaar" item.
When you start the software for the second time, it doesn't happen.


Include public IP output in blueprint example

You can update the snippet to automatically provide the public IP address to the user:
data "azurerm_public_ip" "myterraformpublicip" {
name                = azurerm_public_ip. myterraformpublicip.name
resource_group_name = azurerm_linux_virtual_machine. myterraformgroup.resource_group_name
}
output "public_ip_address" {
value = data.azurerm_public_ip.myterraformpublicip.ip_address
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 163088fc-67d3-aa81-26e7-0155f3aaa90c
Version Independent ID: fafceb81-d8fc-8c20-72e5-b2dddc445f73
Content: Quickstart - Use Terraform to create a complete Linux VM in Azure
Content Source: articles/terraform/terraform-create-complete-vm.md
Service: terraform
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

@CloudSurgeon
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@TomArcherMsft
Can you please check and add your comments on this doc update request as applicable.

Closing out old GitHub Issues. If the issue is still valid, please open again so it's created in current repo. #please-close

NOTE: I updated this article and tested it. It will go live by tomorrow afternoon (PST).


Sync accounts without legacyId

70 accounts were synchronized.
PR is not supposed to be merged, so closing it


typo in oboInOwl

the following files
contrib/oboInOwl.obo
contrib/oboInOwl
contrib/oboInOwl.owl
have the following typos:
synonymy
is related the primary class name,
which should be:
synonym
is related to the primary class name,

@cmungall, is this a GO issue?

I think synonymy is correct. I believe it is the quality of being synonymous or having the same meaning.

@ukemi you are right, I didn't know about this word!

Sorry, forgot to close the issue.


Add vignettes tab to to the GUI

for all the cool applications. drag and drop files with results to compare against

an item in a dropdown menu linking to the vignette wiki page https://github.com/smith-chem-wisc/MetaMorpheus/wiki/Vignettes would be good enough for me for now

now that you have the micro-vignette, maybe we could add that to the help menu. clicking the button would fill the appropriate boxes in the gui and the user could click the go button? quick way to test install without the trouble of downloaded everything from the box.

I do plan to add the microvignette to the GUI in a separate PR. I'd like this PR to be focused on command-line stuff though

that's what I expected. great.


Update appveyor.yml

:white_check_mark: Build SmtpLw 2.0.78 completed (commit https://github.com/guibranco/SmtpLw/commit/412445656a by @guibranco)


SPIKE: User created metadata files in repositories

This spike relates to "Enhance Understanding of GitHub Repositories" (#3144).

As a Developer
I want a better understanding of the repositories in the 'ministryofjustice' and 'moj-analytical-services' GitHub organisations
so that I can comprehend what these repositories are, who they belong to and what purpose they serve.

We are unclear on the value of this work or the limitation of our approach. To learn more about the problem space to to determine next steps we want to explore how we might get users to add metadata files to their repos.
Assumptions

We will only focus on MoJ Github org for this spike.
We exclude archived repos
Process would be a Standard (although we are not making changes to Standards as part of this spike), i.e. process is not optional.

Questions

What data would we ask users to provide?
What format will the file be?
What is the quality of the data? i.e. is it meaningful/easy to understand?
How might we use that data?
What limitations might there be?
How do we get users to add metadata files?
How might we encourage compliance?
What documentation might we need?
How might we build this file into the Template Repo

Acceptance Criteria:

We understand what data is available to us without users needing to do anything.
We can have a discussion about whether there is value in this approach and whether to continue or abandon the EPIC.

Notes:
Timebox - Max 1 week

We have insufficient understand of the value that this adds.


Fs.verify.concurrency

What problem are we solving?
Verifying is too slow, which makes it impossible to verify all files in a week during intensive writing
How are we solving the problem?
Verify in parallel on each volume server
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

Tested
total 64729 directories, 18731395 files
verified 10359 files, error 0 files

Would you consider adding a deletion parameter?


Fix: wrong register for BMI1 bit

The BMI1 bit is in the ebx register and not in ecx. See reference: https://software.intel.com/sites/default/files/article/405250/how-to-detect-new-instruction-support-in-the-4th-generation-intel-core-processor-family.pdf

Thanks


Update go installation command in README.md

Installing using go get returns an error message:
$ go get -u -v github.com/cirocosta/asciinema-edit
go: go.mod file not found in current directory or any parent directory.
	'go get' is no longer supported outside a module.
	To build and install a command, use 'go install' with a version,
	like 'go install example.com/cmd@latest'
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.

The command is updated to use go install as suggested in the error message.

Thanks that helped me!
Worth merging!