JobSet release for ARM?

I'm testing JobSet with an operator, and I saw this error in my operator
2023-07-24T22:04:51Z	ERROR	Reconciler error	{"controller": "hyperqueue", "controllerGroup": "flux-framework.org", "controllerKind": "Hyperqueue", "Hyperqueue": {"name":"hyperqueue-sample","namespace":"flux-operator"}, "namespace": "flux-operator", "name": "hyperqueue-sample", "reconcileID": "a2514367-0003-4f54-bec9-cde6aed4365e", "error": "Internal error occurred: failed calling webhook \"mjobset.kb.io\": failed to call webhook: Post \"https://jobset-webhook-service.jobset-system.svc:443/mutate-jobset-x-k8s-io-v1alpha2-jobset?timeout=10s\": no endpoints available for service \"jobset-webhook-service\""}

Doh! I forgot that JobSet is probably built for x86!
$ kubectl logs -n jobset-system jobset-controller-manager-547857948-d9m82
exec /manager: exec format error

Would it be possible to have an ARM build / set of manifests?

heyo! I was wondering if this is something we could look into?

I think it is doable.  I believe that Kueue supports both.
Looks like its some work in the makefile: https://github.com/kubernetes-sigs/kueue/blob/main/Makefile to tell which platform to build.

Yes! I've done this for two operators now, if you want another pattern to look at:

https://github.com/converged-computing/metrics-operator/blob/1a4fb5065866beb0dd1400e35dc2ee7e9acdaa3d/Makefile#L288-L301
https://github.com/flux-framework/flux-operator/blob/76c4754f90043dfc7afecc16ade053549c89ba18/Makefile#L281-L298

Arm is much slower to build, so I only do it on merges. https://github.com/flux-framework/flux-operator/blob/76c4754f90043dfc7afecc16ade053549c89ba18/.github/workflows/build-deploy.yaml#L12-L37

yeah, we can support that, do you want to send a PR that follows the Kueue pattern?

yeah, we can support that, do you want to send a PR that follows the Kueue pattern?

The lab asked me to stop contributing until we have a corporate CLA (I was using an individual one before) so I definitely could, but with some delay for that to finalize (we are pushing fairly hard for it to be signed)! If there is someone else that wants to do it, go ahead, if not I can when we have that.

/help
/good-first-issue

@vsoch Thanks for the links, very insightful. QQ: Do you also use/publish manifests to group multiple image tags (*-arm, *-amd ) under the same tags?

I don’t use publish manifests - I have a similar workflow that just builds an explicit arm tag (for a push to main or release with the version) and then generates the equivalent CRD yaml file targeting arm. I didn’t want to tangle the builds together or assume they would stay the same (aside from the architecture).

I have a similar workflow that just builds an explicit arm tag

Thanks for the clarification. I'm bringing this conversation because I'm currently reading about container registry manifests, and i think it would be useful (in the context of this project) to push image tags for each of the supported platform + a manifest mapping the images the their respective platforms. This way user will only have to specify the same tag, regardless of the platform, and leave it up the container runtime to pull the right image. I want to hear what folks this this about this solution/approach? Also happy to contribute and help supporting this.

I’ve developed container registries and contributed to OCI, so I’m familiar. My reasons are primarily the drastic differences in build times. The typical approach is to use this action to build and push both at once (same manifest) and it’s not reasonable to do in the time of a PR. https://drpdishant.medium.com/multi-arch-images-with-docker-buildx-and-qemu-141e0b6161e7 that said, it would work fine to do both like that on merge to main and release, and just one for PR. It’s up to you how you want to maintain your images and CRDs - I want to keep them separate. I don’t think there is a right choice, just different preferences.

Thanks for clarifying again! I have few questions to complete the missing pieces in my mind:

How come CRDs come into the game here? My understanding is that this is about building controller binaries and shipping container images.
If understand well, building and pushing images separately for each platform is faster than using docker buildx build/push --platforms=$(SOME_PLATFORM) ?

Maybe i brought some confusion with my initial message, but the manifest i'm talking about was more the  "container registry manifests" (https://docs.docker.com/engine/reference/commandline/manifest/), not the released manifest.yaml file (that contains CRDs as well)

How come CRDs come into the game here? My understanding is that this is about building controller binaries and shipping container images.

A container image for a controller is directly tied to a CRD. If the metadata is off or wrong there, it won't install properly. E.g., here is the container reference for my CRD that the user applies (that single file) to do the entire deployment. https://github.com/flux-framework/flux-operator/blob/76c4754f90043dfc7afecc16ade053549c89ba18/examples/dist/flux-operator.yaml#L1398. The chart is just a more separated variant of that, where the version (or tag) is filled with a variable, e.g., here is the same. https://github.com/flux-framework/flux-operator/blob/76c4754f90043dfc7afecc16ade053549c89ba18/chart/templates/deployment.yaml#L58

If understand well, building and pushing images separately for each platform is faster than using docker buildx build/push --platforms=$(SOME_PLATFORM) ?

if you use the buildx action and give it two architectures, it's going to take (I think) the sum of both, or at best, the time of the fastest one (if it can somehow build in parallel without losing efficiency). In my operator's case, the difference in times is 6 minutes for x86 and 33 for arm. And (in the scope of things I've built with QEMU and arm) that is really speedy, if you have to do more compilation it can take hours (or go outside of action limits). Here are the two paired, which happens on merge to main / releases. https://github.com/flux-framework/flux-operator/actions/runs/6137092811

Maybe i brought some confusion with my initial message, but the manifest i'm talking about was more the "container registry manifests" (https://docs.docker.com/engine/reference/commandline/manifest/), not the released manifest.yaml file (that contains CRDs as well)

No I understand. You want to pull one digest/tag and have the registry choose the platform. That happens by way of packaging them together into the same OCI image manifest. That is separate from the CRD yaml manifests (that I tried to distinguish based on name). My other point is that the second set of manifests (for the operator) can have subtle differences that would make sharing the OCI image manifest platform potentially problematic. I don't have a good example yet but a simple one might be that some of the clouds expect a pod selector for arm, which we'd need for one CRD manifest for arm but not the other.

To be explicitly clear, you can find a good strategy to put both platforms in the same manifest and allow the OCI registry choose. The complexity, I think, is ensuring that the builds happen in a reasonable time in testing, and if you can do then, ensuring that (forever) there are no differences in the operator manifests to warrant having just one the wrong approach. As I already said, I don't think there is a right answer, but it's a choice depending on the needs / use cases for your operator and choices for CI.

I understand that CRDs can be tightly coupled with the controller version (e.g when it comes to controllers reconciliation logic). Is it accurate to say that the main issue revolves around ensuring compatibility between CRDs (in terms of versioning) and container images, preventing them from diverging?
Additionally, in the case of this project, could there be scenarios where different platforms require distinct "CRDs yaml defintions" to accommodate platform-specific requirements?

Additionally, in the case of this project, could there be scenarios where different platforms require distinct "CRDs yaml defintions" to accommodate platform-specific requirements?

Yes that's why I have two :)  And I mentioned:

I don't have a good example yet but a simple one might be that some of the clouds expect a pod selector for arm, which we'd need for one CRD manifest for arm but not the other.


Web UI | Class 'MongoDB\Driver\Manager' not found

Hey,
I have installed the MUD-Manager with the web GUI, everything went ok
now when i tried to run the GUI i get the following issue
`MUD Manager Configuration
This is the MUD Manager Configuration Screen. Click "edit" on those rows you wish to change.
Fatal error: Uncaught Error: Class 'MongoDB\Driver\Manager' not found in /home/tester/MUD-Manager/web/vendor/mongodb/mongodb/src/Client.php:87 Stack trace: #0 /home/tester/MUD-Manager/web/funcs.php(78): MongoDB\Client->__construct('mongodb://local...') #1 /home/tester/MUD-Manager/web/mud-home.php(26): init_database(NULL, NULL, NULL, NULL) #2 /home/tester/MUD-Manager/web/index.php(2): include('/home/tester/MU...') #3 {main} thrown in /home/tester/MUD-Manager/web/vendor/mongodb/mongodb/src/Client.php on line 87`

I have installed the dependency with
/usr/bin/composer require mongodb/mongodb
in the directory of the web folder
the generated JSON file of the composer contains the following
{     "require": {         "mongodb/mongodb": "^1.4"     } }
The files in the web folder:

Any suggestion where the issue could be ?

This looks like mongodb isn't running.  Is it?

I think I have spotted a problem here.  It has to do with the version of the mongodb plugin.  pecl offers a better version to install.  Can you try it and let me know?

It's hard to try now since i have moved on and don't have the project files anymore, it's up to you to decide to keep this ticket open or not


Citation for the Cloud-Optimized geospatial formats guide?

Is there a way to make a proper citation for the Cloud-optimized geospatial formats guide? I see one under https://github.com/cloudnativegeo/cloud-optimized-geospatial-formats-guide#license with @abarciauskas-bgse's name, but it doesn't list all the other authors. Context is that I'm helping to draft an academic paper right now, and would like to provide proper credit if possible.
Ideally, there would be something like a CITATION.cff file with a DOI included (e.g. from Zenodo), and that would allow exporting to different formats such as APA style or BibTeX.
References:

https://citation-file-format.github.io
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files

👍🏽


[skip ci] [WIP] rolling_upgrade: follow MDS upgrade procedure

From: http://docs.ceph.com/docs/master/cephfs/upgrading/#upgrading-the-mds-cluster
Signed-off-by: Patrick Donnelly<EMAIL_ADDRESS>

I don't expect this code to work as-is. I need help rapidly learning how to test this. Also, the procedure is different for pre-Mimic clusters so the code needs to add a check for that and do a slightly differnet procedure:
http://docs.ceph.com/docs/luminous/cephfs/upgrading/

@batrick what's the status of this? How can we help? Thanks

We need to generate the bash script which can do the loop deactivating MDS ranks. I haven't had time to work on it yet.

@leseb @guits I have the CephFS parts of this done but I'm not sure how to get the ansible bits right. Can I get some help? I left some comments in.
There's now a python script (py2/3 compat) that does the preupgrade sequence.

@batrick can you allow write access to that PR so I get push into your branch? Thanks! https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/

@leseb, the PR shows you have permission (that check box is already clicked).

@batrick thanks I'll give it a try then.

@leseb, if that doesn't work, feel free to just create a new PR.

@batrick nop, this hasn't moved yet because I didn't have time yet. Probably next week.

ACK, no problem


currency issue

Hi
while using the Monthly Budget editor the currency shown is the base currency which in my MD is set as INR indian rupees.
but the monthly  budget report shows the currency as AED . How do I get both the report in the same currency.

Hi,
Are you using the latest release of monthly budget report - 2205? If so, in the edit budget report parameters is "Use Category Currency" checked or unchecked? It should be unchecked if you want to use the base currency. What version of Moneydance are you on and what OS?

Hi
I am using monthly budget report 2202.I tried downloading 2205 but not able to update to 2205.i am using v2205 of the monthly budget editor. Pls advice
From: Jerry Jones @.>
Sent: Thursday, April 6, 2023 6:59 PM
To: jerrymjones/MonthlyBudgetReport @.>
Cc: shamsu203 @.>; Author @.>
Subject: Re: [jerrymjones/MonthlyBudgetReport] currency issue (Issue #10)
Hi,
Are you using the latest release of monthly budget report - 2205? If so, in the edit budget report parameters is "Use Category Currency" checked or unchecked? It should be unchecked if you want to use the base currency. What version of Moneydance are you on and what OS?
—
Reply to this email directly, view it on GitHub https://github.com/jerrymjones/MonthlyBudgetReport/issues/10#issuecomment-1499209709 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A55YIEGTACOI7UNJMCPCRB3W73K4XANCNFSM6AAAAAAWU4KZTU .
You are receiving this because you auththe moored the thread.  https://github.com/notifications/beacon/A55YIEHO3IILQXKEHVYVJJLW73K4XA5CNFSM6AAAAAAWU4KZTWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSZLQP62.gif Message ID: @.*** @.***> >

Ok, so that's likely the issue. currencies weren't correctly supported until v2205 so what we need to do first is figure out why you can't update the Budget Report extension. You should be able to download the .mxt file for the latest release from github. Then go to Manage Extensions and select Add From File to load the file you just downloaded. What happens when you do that? Why doesn't it update?

Hi
I did exactly as u said and still the same result. Screenshot of the extension page which still shows the version as 2202. Pls advice
From: Jerry Jones @.>
Sent: Friday, April 7, 2023 7:39 PM
To: jerrymjones/MonthlyBudgetReport @.>
Cc: shamsu203 @.>; Author @.>
Subject: Re: [jerrymjones/MonthlyBudgetReport] currency issue (Issue #10)
Ok, so that's likely the issue. currencies weren't correctly supported until v2205 so what we need to do first is figure out why you can't update the Budget Report extension. You should be able to download the .mxt file for the latest release from github. Then go to Manage Extensions and select Add From File to load the file you just downloaded. What happens when you do that? Why doesn't it update?
—
Reply to this email directly, view it on GitHub https://github.com/jerrymjones/MonthlyBudgetReport/issues/10#issuecomment-1500397749 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A55YIECDC3PRAP3T7AKGH5DXAAYI3ANCNFSM6AAAAAAWU4KZTU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/A55YIEBDWNO7OCIDP6PDZZLXAAYI3A5CNFSM6AAAAAAWU4KZTWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSZNZALK.gif Message ID: @.*** @.***> >

Hi
I finally got the correct version and works fine. Tks for ur help.
From: Jerry Jones @.>
Sent: Friday, April 7, 2023 7:39 PM
To: jerrymjones/MonthlyBudgetReport @.>
Cc: shamsu203 @.>; Author @.>
Subject: Re: [jerrymjones/MonthlyBudgetReport] currency issue (Issue #10)
Ok, so that's likely the issue. currencies weren't correctly supported until v2205 so what we need to do first is figure out why you can't update the Budget Report extension. You should be able to download the .mxt file for the latest release from github. Then go to Manage Extensions and select Add From File to load the file you just downloaded. What happens when you do that? Why doesn't it update?
—
Reply to this email directly, view it on GitHub https://github.com/jerrymjones/MonthlyBudgetReport/issues/10#issuecomment-1500397749 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A55YIECDC3PRAP3T7AKGH5DXAAYI3ANCNFSM6AAAAAAWU4KZTU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/A55YIEBDWNO7OCIDP6PDZZLXAAYI3A5CNFSM6AAAAAAWU4KZTWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSZNZALK.gif Message ID: @.*** @.***> >

Fantastic, sorry you had problems! Is there anything I need to add to the instructions about updating versions so it is more clear?

Hi
The problem was that the original download of version 2022 had to be deleted from the download folder then only the new version to be downloaded. I was just downloading the new version without  doing this and when I used the install from file of Md it just installed the old version. Once the old version was deleted from the folder the correct version was installed. Tks for ur help
From: Jerry Jones @.>
Sent: Saturday, April 8, 2023 8:51 PM
To: jerrymjones/MonthlyBudgetReport @.>
Cc: shamsu203 @.>; Author @.>
Subject: Re: [jerrymjones/MonthlyBudgetReport] currency issue (Issue #10)
Fantastic, sorry you had problems! Is there anything I need to add to the instructions about updating versions so it is more clear?
—
Reply to this email directly, view it on GitHub https://github.com/jerrymjones/MonthlyBudgetReport/issues/10#issuecomment-1500931564 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A55YIEDFIXZJITDL26VNT5LXAGJOBANCNFSM6AAAAAAWU4KZTU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/A55YIEDD2EWN4HZ54LHOYFDXAGJOBA5CNFSM6AAAAAAWU4KZTWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSZOZS6Y.gif Message ID: @.*** @.***> >

Closed, using wrong version.


Infer empty list/map when possible

[num] numbers = [];
{str, str} map = {};

fun count([str] list) > num -> list.len();

count([]) == 0;

Infer in other contexts:

function arguments
object properties
dot assignment

Then: remove the [<type>, ...] and {<K, V>, ...} since its ambiguous with a list of types


local_plot predictions always blank

I am trying to train the DRIVE data with RVGAN-tf-2.6. An issue I'm finding is the predictions in local_plot are always blank even after 53 epochs of training which took over 20 hours:

local_plot_000053.png
The global_plot though is visible

global_plot_000053.png
I am trying to reproduce eval.py IOU values but the predictions are always blank and looks like it is because predictions from g_local_model are always blank though not from g_global_model

Hi,
We have not tested or experimented on tf-2.6 gpu version for our model. Please use the original tf-2.0 gpu implementation to replicate our experiment.
This version was created in response to this issue
All I can suggest is to train for longer for g_local_model to get good output. As It was mentioned in the paper to train for 100 epochs in three stages to get good output. So You need to resume training by loading weights for both g_local and g_global after 100th epoch. And in total you need to do it for 300 epochs (3 stages).
Hope this answers your questions.

Thanks. Yes, I'm getting much better results with tf-2.0gpu.  Seeing segmentation in both local and global.


Rename adjacentPairs -> pairs

It's kind obvious, and unreasonably verbose.

i actually prefer the specificity of adjacentPairs.. in supercollider pairs by default means consecutive pairs. it could also mean 'all possible pairs', aka cartesian product

What's the diff between adjacent pairs and consecutive pairs ?


Gulp not finishing task

I am using cssnano 2.0.1 but my minification task doesn't finish:
[12:02:48] Starting 'less-compile'...
[12:02:48] Finished 'less-compile' after 378 ms
[12:02:48] Starting 'css-minify'...
Process terminated with code 0.
This is the code i am using. When i remove the .pipe(cssnano()) the task finishes just not minified.
 var clientSrcRootName = 'wwwroot';
    var client = './' + clientSrcRootName + '/';
    var clientStyles = path.join(client, 'styles');

gulp.task('less-compile', function () {
    return gulp.src(config.less)
        .pipe(sourcemaps.init())
        .pipe(less({}))
        .pipe(sourcemaps.write('./'))
        .pipe(gulp.dest(config.clientStyles));
});
gulp.task('css-minify', ['less-compile'], function () {
    return gulp.src(config.cssOnly)
        .pipe(cssnano())
        .pipe(rename(function (path) {
            path.extname = '.min' + path.extname;
        }))
        .pipe(gulp.dest(config.clientStyles));
});

I have also tried the following code from another example:
gulp.task('less', function () {
    var cssnano = require('gulp-cssnano');
    var postcss = require('gulp-postcss');
    var cssnext = require('postcss-cssnext');
    var gradientfixer = require('postcss-gradientfixer');
    var processors = [
        gradientfixer,
        cssnext
    ];
    var css = gulp.src(config.less)
      .pipe(sourcemaps.init())
      .pipe(less({}))
      .pipe(postcss(processors));

    var min = css.pipe(clone())
      .pipe(cssnano({ discardComments: { removeAll: true } }))
      .pipe(rename(function (path) {
          path.extname = '.min' + path.extname;
      }));

    return merge(css, min)
      .pipe(sourcemaps.write('./'))
      .pipe(gulp.dest(config.clientStyles));
});

However same result:
[12:06:31] Starting 'less'...
Process terminated with code 0.

Can you try reinstalling? I've released a couple of patches that fixed some crashes caused by the recent update to postcss-discard-comments.

I'm seeing this behavior on v2.1.1. From debugging the situation with on('data') logging, it gets the the cssnano call and exits without an error being thrown.
If it helps track things down, using the CLI works properly. For reference, the output of cssnano -v is cssnano v3.5.2 (cli v1.0.3).

Potentially related: https://github.com/ben-eb/gulp-cssnano/issues/35

+1 as well posted my code on #38

This is resolved in https://github.com/ben-eb/gulp-cssnano/commit/67795f65cbff99e66e3ecceac56ce274233233f0. 🎉


support flist v2 urls

first version ending with .flist and served from the hub needs to stay supported
for version 2, they end with .fl
they don't have .md5 suffix to get the hash

basically disable all of the validation based on hub features in case of v2 except for it to be a valid url

WIP:
There's a type error in the validation that I'm working on fixing so it doesn't fail the workflows


looking up error on macOS sonoma 14.5

When I started spoof-dpi all the youtube videos hasn't preview pictures and in terminal i saw a few resolve errors for i.ytimage.com. If I do ping i.ytimg.com in another terminal it's resolved without issues.
macOS sonoma 14.5, macbook pro m3 max.

unfortunately, i can't attach any file so I copy-pasted text from terminal
❯ spoof-dpi
███████ ██████   ██████   ██████  ███████ ██████  ██████  ██
██      ██   ██ ██    ██ ██    ██ ██      ██   ██ ██   ██ ██
███████ ██████  ██    ██ ██    ██ █████   ██   ██ ██████  ██
██ ██      ██    ██ ██    ██ ██      ██   ██ ██      ██
███████ ██       ██████   ██████  ██      ██████  ██      ██
• ADDR    : <IP_ADDRESS>
• PORT    : 8080
• DNS     : <IP_ADDRESS>
• DEBUG   : false
INFO[2024-07-31T11:35:44+03:00] [PROXY] Connection timeout is set to 2000ms
INFO[2024-07-31T11:35:44+03:00] [PROXY] Created a listener on port 8080
ERRO[2024-07-31T11:35:50+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:52+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:52+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:52+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:52+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:53+03:00] [PROXY] Error looking up for domain with jnn-pa.googleapis.com couldn not resolve the domain
ERRO[2024-07-31T11:35:53+03:00] [PROXY] Error looking up for domain with i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T11:35:54+03:00] [PROXY] Error looking up for domain with jnn-pa.googleapis.com couldn not resolve the domain
ERRO[2024-07-31T11:35:54+03:00] [PROXY] Error looking up for domain with jnn-pa.googleapis.com couldn not resolve the domain
ERRO[2024-07-31T11:35:55+03:00] [PROXY] Error looking up for domain with jnn-pa.googleapis.com couldn not resolve the domain
===================
❯ ping i.ytimg.com
PING i.ytimg.com (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=104 time=28.518 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=104 time=27.224 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=104 time=26.916 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=104 time=32.809 ms
❯ nslookup i.ytimg.com <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53
Non-authoritative answer:
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>
Name:	i.ytimg.com
Address: <IP_ADDRESS>

It could not have been reproduced on my environmnet. I just released another release with updated logging for dns package, that might help find out what's actually happening with your environment.
please take a look at this part to debug.
https://github.com/xvzc/SpoofDPI/blob/6f151e7038c8c6eb3529129451065f649a92ee08/dns/dns.go#L49-L61

❯ spoof-dpi
███████ ██████   ██████   ██████  ███████ ██████  ██████  ██
██      ██   ██ ██    ██ ██    ██ ██      ██   ██ ██   ██ ██
███████ ██████  ██    ██ ██    ██ █████   ██   ██ ██████  ██
██ ██      ██    ██ ██    ██ ██      ██   ██ ██      ██
███████ ██       ██████   ██████  ██      ██████  ██      ██
• ADDR    : <IP_ADDRESS>
• PORT    : 8080
• DNS     : <IP_ADDRESS>
• DEBUG   : false
INFO[2024-07-31T15:35:17+03:00] [PROXY] Connection timeout is set to 2000ms
INFO[2024-07-31T15:35:17+03:00] [PROXY] Created a listener on port 8080
ERRO[2024-07-31T15:35:25+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
ERRO[2024-07-31T15:35:26+03:00] [PROXY] Error while dns lookup: accounts.youtube.com couldn not resolve the domain
ERRO[2024-07-31T15:35:26+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
ERRO[2024-07-31T15:35:27+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
^C%
❯ spoof-dpi -debug
███████ ██████   ██████   ██████  ███████ ██████  ██████  ██
██      ██   ██ ██    ██ ██    ██ ██      ██   ██ ██   ██ ██
███████ ██████  ██    ██ ██    ██ █████   ██   ██ ██████  ██
██ ██      ██    ██ ██    ██ ██      ██   ██ ██      ██
███████ ██       ██████   ██████  ██      ██████  ██      ██
• ADDR    : <IP_ADDRESS>
• PORT    : 8080
• DNS     : <IP_ADDRESS>
• DEBUG   : true
INFO[2024-07-31T15:35:43+03:00] [PROXY] Connection timeout is set to 2000ms
INFO[2024-07-31T15:35:43+03:00] [PROXY] Created a listener on port 8080
DEBU[2024-07-31T15:35:46+03:00] [PROXY] Request from <IP_ADDRESS>:62030
CONNECT www.youtube.com:443 HTTP/1.1
Host: www.youtube.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:46+03:00] [PROXY] Request from <IP_ADDRESS>:62031
CONNECT www.youtube.com:443 HTTP/1.1
Host: www.youtube.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:46+03:00] [DNS] resolved www.youtube.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:46+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:46+03:00] [DNS] resolved www.youtube.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:46+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] New connection to the server www.youtube.com <IP_ADDRESS>:62032
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62030
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Error reading client hello from the clientEOF
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62030
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Closing server Connection.. www.youtube.com <IP_ADDRESS>:62032
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] New connection to the server www.youtube.com <IP_ADDRESS>:62033
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62031
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Client sent hello 588bytes
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Writing chunked client hello to www.youtube.com
DEBU[2024-07-31T15:35:46+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:46+03:00] [PROXY] Request from <IP_ADDRESS>:62034
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
ERRO[2024-07-31T15:35:46+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62035
CONNECT www.youtube.com:443 HTTP/1.1
Host: www.youtube.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:47+03:00] [DNS] resolved www.youtube.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] New connection to the server www.youtube.com <IP_ADDRESS>:62036
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62035
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Client sent hello 588bytes
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Writing chunked client hello to www.youtube.com
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62037
CONNECT googleads.g.doubleclick.net:443 HTTP/1.1
Host: googleads.g.doubleclick.net
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:47+03:00] [DNS] resolved googleads.g.doubleclick.net: <IP_ADDRESS>
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] New connection to the server googleads.g.doubleclick.net <IP_ADDRESS>:62038
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62037
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Client sent hello 600bytes
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Writing chunked client hello to googleads.g.doubleclick.net
DEBU[2024-07-31T15:35:47+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62039
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62040
CONNECT www.google.com:443 HTTP/1.1
Host: www.google.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62042
CONNECT www.google.ru:443 HTTP/1.1
Host: www.google.ru
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:47+03:00] [PROXY] Request from <IP_ADDRESS>:62041
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved www.google.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved www.google.ru: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62045
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62046
CONNECT play.google.com:443 HTTP/1.1
Host: play.google.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62047
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved play.google.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server www.google.com <IP_ADDRESS>:62043
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62040
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server www.google.ru <IP_ADDRESS>:62044
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62042
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 587bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to www.google.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 586bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to www.google.ru
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server play.google.com <IP_ADDRESS>:62048
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62046
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 588bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to play.google.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62050
CONNECT www.youtube.com:443 HTTP/1.1
Host: www.youtube.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved www.youtube.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62052
CONNECT yt3.ggpht.com:443 HTTP/1.1
Host: yt3.ggpht.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62053
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62054
CONNECT i9.ytimg.com:443 HTTP/1.1
Host: i9.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved yt3.ggpht.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved i9.ytimg.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62057
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server www.youtube.com <IP_ADDRESS>:62051
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62050
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: i.ytimg.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 588bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to www.youtube.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62049
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62039
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server i9.ytimg.com <IP_ADDRESS>:62056
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62054
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server yt3.ggpht.com <IP_ADDRESS>:62055
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62052
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 585bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to i9.ytimg.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 586bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to yt3.ggpht.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Finished <IP_ADDRESS>:62050
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62050
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing server Connection.. www.youtube.com <IP_ADDRESS>:62051
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62058
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62059
CONNECT jnn-pa.googleapis.com:443 HTTP/1.1
Host: jnn-pa.googleapis.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62060
CONNECT static.doubleclick.net:443 HTTP/1.1
Host: static.doubleclick.net
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62061
CONNECT accounts.youtube.com:443 HTTP/1.1
Host: accounts.youtube.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved static.doubleclick.net: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
ERRO[2024-07-31T15:35:48+03:00] [PROXY] Error while dns lookup: accounts.youtube.com couldn not resolve the domain
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server static.doubleclick.net <IP_ADDRESS>:62063
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62060
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to static.doubleclick.net
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Finished <IP_ADDRESS>:62039
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62039
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62049
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62062
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62058
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62064
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62065
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62064
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Finished <IP_ADDRESS>:62058
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62058
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:48+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62062
DEBU[2024-07-31T15:35:48+03:00] [PROXY] Request from <IP_ADDRESS>:62066
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62067
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62066
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Finished <IP_ADDRESS>:62064
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62064
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62065
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62068
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62069
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62068
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62070
CONNECT jnn-pa.googleapis.com:443 HTTP/1.1
Host: jnn-pa.googleapis.com
Proxy-Connection: keep-alive
Connection: keep-alive
ERRO[2024-07-31T15:35:49+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Finished <IP_ADDRESS>:62066
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62066
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62067
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62071
CONNECT rr4---sn-q4flrnel.googlevideo.com:443 HTTP/1.1
Host: rr4---sn-q4flrnel.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [DNS] resolved rr4---sn-q4flrnel.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62035 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62035
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing server Connection.. www.youtube.com <IP_ADDRESS>:62036
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62073
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [DNS] resolved i.ytimg.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] New connection to the server rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62072
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62071
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] New connection to the server i.ytimg.com <IP_ADDRESS>:62074
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62073
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Writing chunked client hello to rr4---sn-q4flrnel.googlevideo.com
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Writing chunked client hello to i.ytimg.com
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Finished <IP_ADDRESS>:62068
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62068
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62069
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62076
CONNECT rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com:443 HTTP/1.1
Host: rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [DNS] resolved rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:49+03:00] [PROXY] Request from <IP_ADDRESS>:62078
CONNECT jnn-pa.googleapis.com:443 HTTP/1.1
Host: jnn-pa.googleapis.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] New connection to the server rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com <IP_ADDRESS>:62077
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62076
ERRO[2024-07-31T15:35:49+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Writing chunked client hello to rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62037 timed out
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62037
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Closing server Connection.. googleads.g.doubleclick.net <IP_ADDRESS>:62038
DEBU[2024-07-31T15:35:49+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Finished <IP_ADDRESS>:62071
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62071
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. rr4---sn-q4flrnel.googlevideo.com <IP_ADDRESS>:62072
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62040 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62040
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. www.google.com <IP_ADDRESS>:62043
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62042 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62042
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. www.google.ru <IP_ADDRESS>:62044
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62046 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62046
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. play.google.com <IP_ADDRESS>:62048
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62052 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62052
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. yt3.ggpht.com <IP_ADDRESS>:62055
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62054 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62054
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. i9.ytimg.com <IP_ADDRESS>:62056
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62060 timed out
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62060
DEBU[2024-07-31T15:35:50+03:00] [HTTPS] Closing server Connection.. static.doubleclick.net <IP_ADDRESS>:62063
DEBU[2024-07-31T15:35:50+03:00] [PROXY] Request from <IP_ADDRESS>:62080
CONNECT jnn-pa.googleapis.com:443 HTTP/1.1
Host: jnn-pa.googleapis.com
Proxy-Connection: keep-alive
Connection: keep-alive
ERRO[2024-07-31T15:35:50+03:00] [PROXY] Error while dns lookup: jnn-pa.googleapis.com couldn not resolve the domain
DEBU[2024-07-31T15:35:51+03:00] [PROXY] Request from <IP_ADDRESS>:62081
CONNECT play.google.com:443 HTTP/1.1
Host: play.google.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-07-31T15:35:51+03:00] [DNS] resolved play.google.com: <IP_ADDRESS>
DEBU[2024-07-31T15:35:51+03:00] [PROXY] Start HTTPS
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] New connection to the server play.google.com <IP_ADDRESS>:62082
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:62081
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Client sent hello 588bytes
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Writing chunked client hello to play.google.com
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Chunking client hello.
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62073 timed out
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62073
DEBU[2024-07-31T15:35:51+03:00] [HTTPS] Closing server Connection.. i.ytimg.com <IP_ADDRESS>:62074
DEBU[2024-07-31T15:35:52+03:00] [HTTPS] Error reading from <IP_ADDRESS>:62076 timed out
DEBU[2024-07-31T15:35:52+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:62076
DEBU[2024-07-31T15:35:52+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-07-31T15:35:52+03:00] [HTTPS] Closing server Connection.. rr7---sn-gvnuxaxjvh-n8ves.googlevideo.com <IP_ADDRESS>:62077
DEBU[2024-07-31T15:35:52+03:00] [PROXY] Request from <IP_ADDRESS>:62083
CONNECT i.ytimg.com:443 HTTP/1.1
Host: i.ytimg.com
Proxy-Connection: keep-alive
Connection: keep-alive


Initial transition only when turning off sleepmode

Most of the lights in my house are controlled by motion sensors. In the mornings we find the lights get too bright too early so we leave on night mode longer. To get a smooth transition when night mode turns off (in my case 20% -> 100% most of the time) we set an hight initial transition.
The problem with motion sensor control is that my lights ar regularly turned of and on. And every time it turns on it gets the initial transition which takes to long to change the lights when you want them to change quickly during day time.
I could make more switches and set the according switches based on daytime to overcome this, but it would be nice to have an transition time only for switching night mode off.

You could just use the service to turn on the light when motion is detected and set the transition there.

Hey @smqrt,
I can see the issue and why this would be nice to have.
I think a master switch for the lights would be all you need, right?
In this case that ticket here would be superseded by https://github.com/basnijholt/adaptive-lighting/issues/132

I think that's fixed in 1.0.15.
If not, LMK


Enhanced the scrollbar

Done with the scrollbar, hope it looks better now :)

@kaur-rajdeep please provide screenshot


dev/test: handful of smallish fixes

See individual commit messages for specifics.

Docs build failure appears to be Google Font related? https://github.com/squidfunk/mkdocs-material/issues/6983


Upgrade to Ruby 2.5.0 and part of gems

Hope the enhancement works 🤞

Looks good to me! I'll merge this and cut a new version shortly. Thank you for your contribution!

Version 0.2.0 is now on RubyGems!


Update quickstart-for-actions-runner-controller.md

we need to be auth first, before the helm install (https://github.com/github/docs/issues/34636)

Why:
To resolve this issue https://github.com/github/docs/issues/34636
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

we need to be auth first, before the helm install (#34636)
Why:
To resolve this issue #34636
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:

[x]  I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x]  For content changes, I have completed the self-review checklist.

@seilorjunior Thanks so much for opening a PR! I'll get this triaged for review ✨

This looks great from a docs-content perspective. Once we have a confirmation from a subject matter expert, we can go ahead and merge this.

seilorjunior:patch-1

@seilorjunior Thank you for your patience while our SME team reviewed! For the reasons listed above (and in the linked issue), we are unable to accept this contribution 💛
Thank you for willingness to contribute to GitHub Docs! If you're interested, take a look at our help wanted section to find open issues you can work on ✨


Google Analytics import doesn't track Safari on iOS

I'm trying to import our usage from Google Analytics but Safari on iOS is no longer being tracked at all.
All entries for the browser "Safari & Chrome for iOS" going back to version 9.0 up to 14.6 are being listed as browsers not included.

Thanks for reporting! Should be fixed now.


Add -Path alias to -FilePath parameter for Out-File command

The Out-File command has a mandatory -FilePath parameter. The name of the -FilePath parameter is a bit redundant, given that the command's noun is File. I'd recommend adding a parameter alias -Path to the -FilePath parameter, to remove the requirement to have this redundancy.
Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

FWIW- It's not an accident that Out-File uses -FilePath instead of Path. It was intended that commands which take -Path should work against any provider supporting the underlying operations. Out-File explicitly and only works against the file system hence -FilePath instead of the more general -Path.

That makes sense.


Fix CI issues

Changes proposed:

[x] Fix

Fix publication stage

Fix docker stages

Fix wiki pages icons list generator stage

wpilgen stage failed due to non-allowed node version but I fixed it on the repo and it will run successfully next time.


Hide some parts of stack trace in __PYX_ERR macro

I'm always using Cython for seeing how this or that piece of code in Python will be represented using Python C API, so my changes are devoted to improving (in a way) readability of the resulting C code. The idea is the following. The resulting code is full of the constructions like this
{__pyx_filename = __pyx_f[0]; __pyx_lineno = 4; __pyx_clineno = __LINE__; goto __pyx_L1_error;}

They are always catching your eye and distract attention from other pieces of automatically generated code. I suggest we hide each constructions like that in the macro like this
__PYX_ERR(0, 4, __pyx_L1_error)

The __PYX_ERR macro looks in the following way
#define __PYX_ERR(f_index, lineno, Ln_error) \\
{ \\
  %s = %s[f_index]; %s = lineno; %sgoto Ln_error; \\
}

Works for me too.


Audit Trail: Unable to filter by Content type

When using the audit trail module alongside the Audit Trail Content Definition Events to allow for filtering, if a content item is saved, published, deleted, created or imported they will not show up in the filtered audit trail when filtering by Content Type
Replication Steps: As an admin
Enable the Audit Trail module and the Audit Trail Content Definition Events module
Create a content item and click publish now
With the same content item make some changes click publish now
Navigate to the audit trail and attempt to filter by that content type

I believe the Content Type filter behaves differently than one might expect, but I don't recall the details. Notice the little question mark? Can you please hover over it and capture the tooltip? Thanks

"Applies to content type events only, not to content item events"

There you go: it does not filter by a content item's content type, but only events regarding content type changes, e.g. when a content type was created, modified or deleted.
I do realize this is a confusing UI, but we weren't able at the time to come up with a better solution. It has to do with the modularity of the system. Each audit trail provider has a say in what filtering controls they want to contribute. If both the content item provider as well as the content type provider contribute a content type filter, it would not be much better.
But that was a while ago. Anyone any clever suggestions?

I still can't think of a better way. :)

Yeah me neither. :)
What if we did add another "Content Type" filter, but using slightly different labels?
For example, the Content Items Audit Trail Provider would use something like: "Content events by Content Type", while the Content Type Audit Trail Provider would use: "Content Type events by Content Type".

That's not a bad idea! I'm not sure if this actually makes it more clear, but I had the thought that maybe it could be shortened to:

Content of type:
Changes to content type:

That's one of the views that I would really like seeing filters to be hidden in a side panel like this one :
https://codyhouse.co/gem/content-filter/


KAFKA-16551: add integration test with bootstrap controller for ClusterTool

Add testClusterIdWithBootstrapController and testUnregisterWithBootstrapController.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

As unregisterBroker  is unsupported to take with quorum controller, it is fine to assume the exception. I have filed https://issues.apache.org/jira/browse/KAFKA-17039 to address that.


Publishing Images to Prime Registry for Chart OOB releases

Currently, when we do out-of-band Chart releases, the necessary images are published to Dockerhub as part of the development/release process. They are not mirrored into the Rancher Prime registry.
Currently, adding in new images to the SUSE registry is only available using artifacts published as part of a Rancher release. The out of band release process that exists will publish new Docker images in Dockerhub and extends feature functionality to existing Rancher Manager installs.
When releasing something out of band from a Rancher release, these images are not being published into the SUSE registry. No image-digest file is generated.
The "ask"
We need to automate the process to be able to have the images of an OOB release being pushed into prime registry without needing the manual monitoring.

It was pointed out in the confluence doc that a potential solution is to cut a "dummy" tag in rancher/rancher to generate the digests file EIO needs. This would be the most straight forward solution as we can tag a x.x.x-rc0 (where x.x.x is whatever next rancher version we are releasing next to avoid the maintenance overhead of having specific tags for this specifically) after a chars OOB release to generate that file for EIO. However, it is important to not this case will generate digests for all images including the charts that were last released and newly released in the OOB release. Would this still work for EIO, or do they need a "filtered" digests file that contains the images of the charts that were released OOB specifically? (this would involve more work to do it right, but doable)

Tasks Ahead

Remove the Github Action code from dev-v2.7
Test if it works even if there is no changes in regsync file.

Implemented Solution 3 in this - https://confluence.suse.com/display/EN/Rancher+Prime+Image+Publishing+for+OOB+Chart+Releases after consulting the EIO team for Charts OOB releases.
PRs - https://github.com/rancher/charts-build-scripts/pull/95


Update sshd to 1.2.0 and mina to 2.0.10

I haven't really tested if ssh still works but it builds ok with this patch.

I do hope you realise that updating a dependency involves a lot of testing to make sure that everything still works as before, and is not done with just making things compile.


Support jsonb functions

Currently when using jsonb_build_object on a select clause
I get the following error:
function jsonb_build_object(unknown, unknown) does not exist

A workaround that I'm using atm is:
json_build_object('foo', 'bar')::jsonb

any progress?

This has been fixed https://play.sqlc.dev/p/f3ec71909782550b9cd6d7bcce3902b749f4f753ac36968e3ee7fcfd5db460a4


Fix Turbolinks warning

Warning message in browser console: "You are loading Turbolinks from a

@alexanmtz please assign me this one.


Validate datetime for version.

Resolves https://github.com/cakephp/phinx/issues/2248
For legacy reasons and BC on the test harnesses I allowed the 0 to pass for now as well.
I think thats fair since most mistakes would happen with actual datetime values.

I've debated on if the appropriate place to put this is as a runtime check within initialization the migration, vs within the getMigrations method in which the migrations are initialized (and which all other methods use to get the list of migrations). I'm somewhat leaning towards the latter with the concept that if some alternative versioning scheme was desired, it'd probably be easier to support via the getMigrations method where we have access to the config object to determine said alternative versioning strategy.
Thoughts?

For legacy reasons and BC on the test harnesses I allowed the 0 to pass for now as well.

I'm curious what legacy reason beyond test harnesses exist to support 0 as a version. I feel like having support for this just for tests seems wrong, where the tests should be updated as it's maybe a bug for production to allow this?

I do like the approach here of only validating that the version integer is a valid date string, and not putting limits on what the allowed range of dates is, as I think that has the potential to be limiting for less value.

where the tests should be updated as it's maybe a bug for production to allow this?

could be a follow up if you want to further narrow the possible valid values.

I pushed the update, was a quick write-up.
Hopefully we can get this in now asap to avoid people running into this like me and others did.

Easy enough to move this check to somewhere else if we decide we need to down the road without breaking BC I think.
I do think this check does break BC though in that it's possible to bypass the date version naming scheme that phinx uses, and just use any number you wanted (e.g. having a counter), though you'd just have to manually create each migration. Not sure if anyone is doing that, so probably fine to just merge it into the next 0.15.x release, and easy to revert if there's enough pushback, or minimally just have them override the base AbstractMigration class.


fix(kit): scroll to active tab when views are ready

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Tests related changes
[ ] Documentation content changes

What is the current behavior?
Closes #2182
What is the new behavior?

@waterplea hello, please review me


ARROW-15044: [C++] Add OpenTelemetry exporters for debugging use

This adds two exporters that can be toggled with an environment variable, for debug use. One is the standard ostream exporter, which logs a human-friendly but machine-unfriendly format. The other uses a trick to log the JSON OTLP request format, which is easily parsable JSON but not very readable.

Example of ostream output:
{
  name          : test
  trace_id      : 577bb5359fd4c9babdfb7e8def43d476
  span_id       :<PHONE_NUMBER>7c4635
  tracestate    :
  parent_span_id:<PHONE_NUMBER>000000
  start         :<PHONE_NUMBER>620946845
  duration      : 8538876
  description   :
  span kind     : Internal
  status        : Unset
  attributes    :
	thread_id:<PHONE_NUMBER>33184
	foo: bar
  events        :
  links         :
  resources     :
	service.name: unknown_service
	telemetry.sdk.version: 1.1.0
	telemetry.sdk.name: opentelemetry
	telemetry.sdk.language: cpp
  instr-lib     : arrow
}

Example of OTLP output:
{"resource":{"attributes":[{"key":"service.name","value":{"stringValue":"unknown_service"}},{"key":"telemetry.sdk.version","value":{"stringValue":"1.1.0"}},{"key":"telemetry.sdk.name","value":{"stringValue":"opentelemetry"}},{"key":"telemetry.sdk.language","value":{"stringValue":"cpp"}}]},"instrumentationLibrarySpans":[{"instrumentationLibrary":{"name":"arrow"},"spans":[{"traceId":"ID+DVD1Rarxdh8dNLchUmw==","spanId":"7IGA2C88AQk=","parentSpanId":"AAAAAAAAAAA=","name":"test","kind":"SPAN_KIND_INTERNAL","startTimeUnixNano":"1639087084846448841","endTimeUnixNano":"1639087084849284338","attributes":[{"key":"foo","value":{"stringValue":"bar"}},{"key":"thread_id","value":{"stringValue":"140253881153728"}}]},{"traceId":"pPN+j22d17tQVbHZpG6pbA==","spanId":"6apExpYokXw=","parentSpanId":"AAAAAAAAAAA=","name":"test","kind":"SPAN_KIND_INTERNAL","startTimeUnixNano":"1639087084850354448","endTimeUnixNano":"1639087084853673659","attributes":[{"key":"foo","value":{"stringValue":"bar"}},{"key":"thread_id","value":{"stringValue":"140253881153728"}}]},{"traceId":"yVWEeB/z4NedBKrCdezTMg==","spanId":"4AGb3ndTHek=","parentSpanId":"AAAAAAAAAAA=","name":"test","kind":"SPAN_KIND_INTERNAL","startTimeUnixNano":"1639087084873028556","endTimeUnixNano":"1639087084876243603","attributes":[{"key":"foo","value":{"stringValue":"bar"}},{"key":"thread_id","value":{"stringValue":"140253881153728"}}]}]}]}

The other uses a trick to log the JSON OTLP request format, which is easily parsable JSON but not very readable.

Can't we just output the machine-readable JSON and users can use jq or something? No reason to write code for tools that already do an amazing job of formatting JSON

I'm not planning on writing any code to format the OTLP output further. I just added that to contrast it with the ostream exporter. (That said, the ostream exporter is not super useful once you log more than ~50 traces, so maybe it's not worth having at all.)

This LGTM.

@pitrou any other comments here?

@github-actions crossbow submit -g cpp


Support setting right-side margin in text_flow method

Adds support for setting the right-side margin in text_flow method
Sets the right-side margin terminal reporter to 1

Before this change:

After this change:

oh yes! This is great! ;-D


Add example-python plugin

Also contains a rename of the legacy-mariadb plugin's directory to a more intuitive name.

@foxish, we should update README.md, given it has references to port-old2new-example. Apart from that, I would also include this new plugin under the Overwiew section.

@foxish, we should update README.md, given it has references to port-old2new-example.

As I looked more through it, it felt a bit redundant / confusing and the references to our legacy system aren't really useful anymore IMO - so, I removed that directory and references to it - we can just use the new mariadb plugin as the canonical one.  LMK if either of you have any objections to that.


chore(ci): travis ci release stage updates

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support for testnet

Describe the feature
I would like to have a testing env for KodaDot so we can test features more effortlessly.
This indexer would be based on the Paseo testnet
Expected outcome

paseo.json with defined stuff
typegen for paseo testnet
snack.yml for deploy

Reference
Seems assethub is missing, pinged people


bug(windows-client): Windows GUI Client isn't producing any logs

Describe the bug
There's no log files in C:\Users\User\AppData\Local\dev.firezone.client\data\logs, when I open the Logs tab it shows 0 files and 0 MB, and when I export a zip file it's empty.
To Reproduce
Can't replicate it.
I had the filter set to firezone_gui_client=debug,firezone_tunnel=info,phoenix_channel=info,connlib_shared=info,connlib_client_shared=info,boringtun=info,snownet=info,str0m=info,warn
but that worked when I tried it again.
Expected behavior
Expected at least some logs since firezone_gui_client=debug and warn are in there
Screenshots / Logs
N/A
Platform (please complete the following information)

Component (i.e. macOS client / Linux client / Gateway / Admin portal): Windows GUI Client
Firezone Version (e.g. 1.0.0 or N/A): Version 1.0.0 (d656cd5)
OS and version: (e.g. Ubuntu 22.04 or N/A): Windows 11
Deployment method: (e.g. Docker / Systemd / App Store or N/A): MSI from draft release

Additional context
I set the filter to debug and restarted the app and it worked.

I remember hitting this a while back and I may have forgotten to open an issue about it. Perhaps tracing isn't being initialized properly?

Or maybe the log filter isn't taking effect until being re-saved?

I don't think I had changed the filter since I installed the new version yesterday.
The hypotheses I've got are this:

Clearing the logs maybe messes up the logging system because it doesn't expect the file to vanish from under it?
Maybe if the computer goes to sleep, when it wakes up and the clock suddenly changes, the logging code gets confused?

Yeah I'm not sure if we still roll the log files, but when I hit "Clear logs" it definitely deletes the current file and doesn't try to write any more logs to that.
Since we know when that happens maybe we can signal to the logger, "recreate your file, we just deleted it"

Clearing the logs maybe messes up the logging system because it doesn't expect the file to vanish from under it?

Ah yes! I hit this recently with the Apple client as well -- also happened with the Swift-side logs.
Yeah we should either detect the file is missing and recreate it, or just clear all files except the current one being written to.

@ReactorScram I think this has been probably hit enough times to make it worth fixing after #5123. Maybe it would be simpler if we just updated the clear behavior to remove all files except the most recent one? Or expose an FFI rotateLogfile function or something

Yeah, maybe we can go off the filenames and keep the last one, when sorted lexicographically. (mtime would work, but I prefer not to use mtime if I can help it)

Status: PR got reviewed, so I can make more progress on it today


Add HPE/Grommet theme switch menu prototype

Deploy Preview

This prototype uses a menu in the Nav section of each page on the Grommet site as a theme switcher. Context code and logic remain similar to the other prototypes. Final visual design for Theme Switch Menu TBD.

Based on the screenshots shown, it looks like there will be no theme selected on initial entry and the user can then choose a particular theme if desired. However, there always needs to be an active theme. The site will never have "no theme".


Cargo check failed for wasm32

➜  rust git:(master) cargo check --target=wasm32-unknown-unknown
Compiling blst v0.3.6 (/Users/khalaniaiyaj/www/supra/blst/bindings/rust)
Compiling zeroize_derive v1.2.0
The following warnings were emitted during compilation:
warning: In file included from /Users/khalaniaiyaj/www/supra/blst/src/server.c:7:
warning: In file included from /Users/khalaniaiyaj/www/supra/blst/src/keygen.c:7:
warning: In file included from /Users/khalaniaiyaj/www/supra/blst/src/consts.h:8:
warning: /Users/khalaniaiyaj/www/supra/blst/src/vect.h:467:10: fatal error: 'stdlib.h' file not found
warning: #include <stdlib.h>
warning:          ^~~~~~~~~~
warning: 1 error generated.
error: failed to run custom build command for blst v0.3.6 (/Users/khalaniaiyaj/www/supra/blst/bindings/rust)
Caused by:
process didn't exit successfully: /Users/khalaniaiyaj/www/supra/blst/bindings/rust/target/debug/build/blst-a11370621bd00ea1/build-script-build (exit status: 1)
--- stdout
Using blst source directory /Users/khalaniaiyaj/www/supra/blst
TARGET = Some("wasm32-unknown-unknown")
OPT_LEVEL = Some("0")
HOST = Some("aarch64-apple-darwin")
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
running: "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-Wall" "-Wextra" "-D__BLST_NO_ASM__" "-o" "/Users/khalaniaiyaj/www/supra/blst/bindings/rust/target/wasm32-unknown-unknown/debug/build/blst-87228100d838f205/out/server.o" "-c" "/Users/khalaniaiyaj/www/supra/blst/src/server.c"
cargo:warning=In file included from /Users/khalaniaiyaj/www/supra/blst/src/server.c:7:
cargo:warning=In file included from /Users/khalaniaiyaj/www/supra/blst/src/keygen.c:7:
cargo:warning=In file included from /Users/khalaniaiyaj/www/supra/blst/src/consts.h:8:
cargo:warning=/Users/khalaniaiyaj/www/supra/blst/src/vect.h:467:10: fatal error: 'stdlib.h' file not found
cargo:warning=#include <stdlib.h>
cargo:warning=         ^~~~~~~~~~
cargo:warning=1 error generated.
exit status: 1
--- stderr
error occurred: Command "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-Wall" "-Wextra" "-D__BLST_NO_ASM__" "-o" "/Users/khalaniaiyaj/www/supra/blst/bindings/rust/target/wasm32-unknown-unknown/debug/build/blst-87228100d838f205/out/server.o" "-c" "/Users/khalaniaiyaj/www/supra/blst/src/server.c" with args "clang" did not execute successfully (status code exit status: 1).
warning: build failed, waiting for other jobs to finish...
error: build failed
➜  rust git:(master)

On Linux,
➜  rust git:(master) cargo check --target=wasm32-unknown-unknown
Updating crates.io index
Downloaded libc v0.2.104
Downloaded 1 crate (548.8 KB) in 1.14s
Compiling proc-macro2 v1.0.30
Compiling unicode-xid v0.2.2
Compiling syn v1.0.80
Compiling libc v0.2.104
Compiling glob v0.3.0
Compiling cc v1.0.71
Checking num_cpus v1.13.0
Checking threadpool v1.8.1
Compiling quote v1.0.10
Compiling blst v0.3.6 (/home/webelight-013/Downloads/blst/bindings/rust)
The following warnings were emitted during compilation:
warning: In file included from /home/webelight-013/Downloads/blst/src/server.c:7:
warning: In file included from /home/webelight-013/Downloads/blst/src/keygen.c:7:
warning: In file included from /home/webelight-013/Downloads/blst/src/consts.h:8:
warning: /home/webelight-013/Downloads/blst/src/vect.h:467:10: fatal error: 'stdlib.h' file not found
warning: #include <stdlib.h>
warning:          ^~~~~~~~~~
warning: 1 error generated.
error: failed to run custom build command for blst v0.3.6 (/home/webelight-013/Downloads/blst/bindings/rust)
Caused by:
process didn't exit successfully: /home/webelight-013/Downloads/blst/bindings/rust/target/debug/build/blst-a2b0ea68ba96650b/build-script-build (exit status: 1)
--- stdout
Using blst source directory /home/webelight-013/Downloads/blst
TARGET = Some("wasm32-unknown-unknown")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-unknown-linux-gnu")
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CC_wasm32-unknown-unknown = None
CC_wasm32_unknown_unknown = None
TARGET_CC = None
CC = None
CFLAGS_wasm32-unknown-unknown = None
CFLAGS_wasm32_unknown_unknown = None
TARGET_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
running: "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-Wall" "-Wextra" "-D__BLST_NO_ASM__" "-o" "/home/webelight-013/Downloads/blst/bindings/rust/target/wasm32-unknown-unknown/debug/build/blst-a6a6d11b301f05d5/out/server.o" "-c" "/home/webelight-013/Downloads/blst/src/server.c"
cargo:warning=In file included from /home/webelight-013/Downloads/blst/src/server.c:7:
cargo:warning=In file included from /home/webelight-013/Downloads/blst/src/keygen.c:7:
cargo:warning=In file included from /home/webelight-013/Downloads/blst/src/consts.h:8:
cargo:warning=/home/webelight-013/Downloads/blst/src/vect.h:467:10: fatal error: 'stdlib.h' file not found
cargo:warning=#include <stdlib.h>
cargo:warning=         ^~~~~~~~~~
cargo:warning=1 error generated.
exit status: 1
--- stderr
error occurred: Command "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-Wall" "-Wextra" "-D__BLST_NO_ASM__" "-o" "/home/webelight-013/Downloads/blst/bindings/rust/target/wasm32-unknown-unknown/debug/build/blst-a6a6d11b301f05d5/out/server.o" "-c" "/home/webelight-013/Downloads/blst/src/server.c" with args "clang" did not execute successfully (status code exit status: 1).
warning: build failed, waiting for other jobs to finish...
error: build failed
➜  rust git:(master)

While it is in fact possible to compile core blst for wasm(*), the current understanding is that an attempt to build it with Rust is bound to fail. Because Rust bindings are dependent on multi-threading support, which is not an option on wasm target. This doesn't really answer the question about dysfunctional C compiler setup, but if you get past it, there is a bigger road block ahead...
(*) It was tested with emcc, e.g. ./build.sh CC=emcc, which was then linked with a test program in C.

./build.sh CC=emcc

Doesn't work anymore, ./build.sh CROSS_COMPILE=em is the answer.

3ab76cd46ad04a25e202fec427d56d31a5d6141f.
I'm closing this. The next road block is assumed to be removed (if there are problems with it, open a new issue), while the original problem is viewed as something for the user to resolve. On a potentially related note, build.rs checks if there is pre-compiled libblst.a in the current working directory, so that it's possible to avoid cargo-C-compiler interaction by compiling it in advance, in this case with '../../build.sh CROSS_COMPILE=em'...

For reference, 1307ecd.


commonlib: separate major versions

@adammhaile this is what I was thinking for doing different things for the different major versions. Fairly straightforward...

/assign @tbielawa

Before too long, it may make sense to rename build/ocp to build/ocp3. That will be clearer but we'll lose the build history, so I'm not super eager to do it.

@sosiouxme agree on the rename, but I feel like after 4.0 GA is a more proper time.


Add information about userid

User id is used in many methods, but it's not clear from docs how to get it. Can you please add a recommended way?
Btw, Python library fetches and stores account information on init to avoid asking user to provide user id in each method.

Getting token is also not clear, but it's probably because there's no official way to get. Leaving this discussion here in case somebody looks for it as me.

I got my ID via this way:
curl<EMAIL_ADDRESS>
Instead of<EMAIL_ADDRESS>of course, put email on which yandex account registered.
You'll get JSON map. Your ID is in result.uid field

I ended up with this
ya := yamusic.NewClient(yamusic.AccessToken(0, token))
status, _, err := ya.Account().GetStatus(ctx)
if err != nil {}
	// handle
}
ya.SetUserID(status.Result.Account.UID)


Added player drops

Adding player drops. Item drops working as expected, however, meso drop essentially freezes player. Does the client expect a packet back confirming mesos change?

Relevant vana code: https://github.com/retep998/Vana/blob/19116c07dd0082b6c570bfd6d2ea604947773c10/src/channel_server/drop_handler.cpp#L198

Quantity drop is not 100% working but pickup/drop for mesos is 100% and single items/full stacks is working

I tested this locally to test and found two issues:

The message for the amount of mesos received is not correct
When dropping an item and then picking it up followed by a relog, the item is gone from inventory, if using /drop command and picking up the items it spawns then they get saved, apart from the mesos, picking that up doesn't change the value in inventory.

@Hucaru thank you for the hook, that will definitely help.
I appreciate you taking time to review the PR.
As far as the meal amount goes that's an issue I haven't been able to figure out. The packet is structured basically exactly like the Vana pickup notice yet the meso amount is not showing. I know you're a bit busy but if you have time could you review that specific packet? I'm really not sure what I'm doing wrong with that one.
Everything else I'll get taken care of.

I think the dropping of items that have an amount greater than 1 such as potions should have the window pop up asking for the amount before the packet is sent, not really sure. It could be there is a property about the item (not the amount?) that tells the client when to do this.

I'm not really sure how to get that to pop-up because it does not do it by itself in the client as it would with dropping mesos. The packet itself does not contain any unique identifiers either it simply has (opcode | pos | dropid). I'm assuming it is related to the item itself. I'll review that and see what I can find.

I believe they are handling the window via inventory operations here:
https://github.com/retep998/Vana/blob/19116c07dd0082b6c570bfd6d2ea604947773c10/src/channel_server/inventory_handler.cpp#L113
Not too familiar with C++ so it's a little fuzzy but I'll work on it

I have had another play locally and it appears when dropping a potion and picking it up it can sometimes crash the client and the inventory for that item isn't handled properly i.e. I had a stack of 100 and 200 dropped 100, picked up 100 crashed loged in again and had a stack of 100 only in inventory.

I think that has to do with the saving inconsistencies. The server does not save as often as it should so I think it would be best to tackle that as a DB saving refactor.
Also I believe the dropping issue is relate to the item packets itself as you stated. I read an old ragezone post where it happened because the expiration time wasn't properly set. Will need to review more

I resolved the issue with the drop UI not showing by adding an expiration time. Not really sure why that matters, but it does apparently.

Pretty sure the stacking issue is related to the updateItem function. It looks like the slice is getting copied and we are modifying the copy slice.
https://github.com/Hucaru/Valhalla/blob/354ba204ae26b73bf43df07b4859f3aac33ac575/channel/player.go#L685

Pretty sure the stacking issue is related to the updateItem function. It looks like the slice is getting copied and we are modifying the copy slice.
https://github.com/Hucaru/Valhalla/blob/354ba204ae26b73bf43df07b4859f3aac33ac575/channel/player.go#L685

That could very well be it. I don't have a specific test for it apart from moving stackable items around and dropping them then logging on and off

Drops appear to be working as expected now. The copy slice was getting updated versus the players slice. In addition, when the item was added to the DB item.save function was not using a pointer so it was not updating the actual item, but rather a copy as well.

It might be worthwhile looking into changing the script system to just be the same as Odin. Have you finished the item related changes you wanted to make? I would like to keep the PRs scoped to a single area/topic/issue if possible.

Agreed, it would be a lot easier to mimic Odin versus making 300 different NPC scripts.
Yes all the changes are done and drops are working exactly as expected now from my testing.

There is a bug where if an item is spawned e.g. /item 2000003 100 then dropped and picked up, it is no longer in inventory when reloged (if partial amount dropped and picked up then works as expected). This applies to all item types. Would suggest there is a database saving issue when an item is picked up.

There is a bug where if an item is spawned e.g. /item 2000003 100 then dropped and picked up, it is no longer in inventory when reloged (if partial amount dropped and picked up then works as expected). This applies to all item types. Would suggest there is a database saving issue when an item is picked up.

Just tested and it looks like this was related to the drop item's DB ID. It kept the same db ID once dropped so changing it to have a db ID of 0 resolved the bug.

Happy for me to merge?

Yep, I'm working on skills which seems like it's going to be a lot. So this can merge


Clarification required re Component

What would you like to share?

see components/common/button
As far as I can tell this should be deprecated or documented why its needed.

Additional information
No response

components/common/button is currently used only on MaintainerForm on MaintainersPage

So, we can move it to the maintainers section or try to reuse this class to be common among all the buttons on the website.
Do you prefer just moving it?
Can you assign it to me?

I am working on this page right now, I will remove this button as it contains nothing special to be considered different componenet


setup Java samples CI

This branch/PR handles the creation of a CI pipeline using Github actions.
The pipeline will run:

clean
assemble
unit tests
lint
pmd
checkstyle

LG to the team! 🚀


calling decorate in serialize

HI everyone, I have an parse json and I use active_model_serializers.
In article_seriallizer.rb
I call object.decorate and it throw error:
Draper::UninferrableDecoratorError - Could not infer a decorator for ActiveRecord::Base.:

I have the same error when using 2.1 version. Is there something in the documentation about using the 2.x version?

I have nothing to say on this without details provided, sorry 🤷
I hope the issue is resolved long ago. If not, I'll reopen it.


Krane Global Deploy

#567 Causes krane deploy to fail validation when a global resource is present. This is a breaking change from kubernetes-deploy. As a result I believe we need to provide a krane global-deploy command to that only allows global resources to be deployed.

Done https://github.com/Shopify/kubernetes-deploy/pull/602 & https://github.com/Shopify/kubernetes-deploy/pull/612


Gifs don't upload nicely/correctly

Test Tweet
Result in Riot
The image is not a gif, it's just a frame from the Gif. It would be nice if Gifs were uploaded in their entirety.
Note: I used the built-in gif functionality of the Twitter app for this.

Aware of the issue. We currently use the legacy twitter media API. In the future, I want to cover all types of media.


Set custom maxY

For example, for a chart:

It's impossible to show ThresholdLine for a value which is higher than other values on Y axis, thresholdValue must be in between. Is there any workaround?

Hello! You can achieve this by specifying a custom maxY value. In the compose module, columnChart and lineChart have maxY parameters: columnChart(maxY = 10f). In the view system, you can set a custom maxY value as follows: chartView.chart?.maxY = 10f (where chartView is a reference to your ChartView instance).

Thank you, it works!

Sure thing.


YamlConfigurationService: Reject origins file if it introduces name clashes.

Reject origins file reload if it would result in name clashes between routing objects, and
log a meaningful error message.

Addresses #529. But in a more restrictive manner.


CopyExternalsPlugin correctly supports node builtin modules

Fixes https://github.com/iTwin/itwinjs-core/issues/5738

@mergifyio backport release/4.0.x


Harrison/pinecone check and log warning

check if key is present, log warning if not

I don't really understand when this would happen. Aren't we forcing each document to have a text key when we build the index? I refer to these lines in /langchain/vectorstores/pinecone.py:
for j, line in enumerate(lines_batch):
      metadata[j][text_key] = line
to_upsert = zip(ids_batch, embeds, metadata)

I guess what would make more sense is to raise an error if a document does not have a text key in the metadata, what do you think?

I don't really understand when this would happen. Aren't we forcing each document to have a text key when we build the index? I refer to these lines in /langchain/vectorstores/pinecone.py:
for j, line in enumerate(lines_batch):
      metadata[j][text_key] = line
to_upsert = zip(ids_batch, embeds, metadata)

I guess what would make more sense is to raise an error if a document does not have a text key in the metadata, what do you think?

The issue isn't when there isn't a text key in the metadata, it's when it's the wrong text key. If you submit two documents with two different text keys and then query pinecone with something that returns both documents this method will throw a KeyError. Since this method essentially just filters out results by text key, I don't think it makes sense to log a warning or an error as it is intended behavior (from what I understand).

took over in #4424


Redstone clock perhaps?

Can you please add the Redstone Clock block in? its really helpful especially when using it with mods like tinkers construct.

In dev


Removing PureComponents breaks inputs

Hi, I did a bisect to find the problem we were having with styled components v4 and surveyjs. I ended up with narrowing the problem to this commit:
a7ab4704fbe0de7450ff0ff634e5024cad24fd31
I understand that PureComponents might cause some problem for you but you have to have some strategy not to mess with props.
The last version of v3 is fine if that helps.

? The current implementation is equivalent to v3 since the purecomponent change was removed. That was going to be a new v4 optimization. v3 also used Component.


feat(temporal): initial support

Requires:

https://github.com/temporalio/helm-charts/pull/555
https://github.com/glasskube/packages/pull/393
https://github.com/glasskube/glasskube/pull/1218

@kosmoz I talked with @robholland about the upstream pr. He is eager to merge it, but as he is traveling it will take at least one more week. In the meantime we should either deploy the helm chart to the glasskube charts repo or build the chart and push it to an oci registry so we are not blocked by the upstream.

@pmig OK thanks, a version of the chart that includes the TTL and default namespace features is now available on charts.glasskube.eu
@christophenne can you check if the package works for you use case?


declaration_files_incremental_* tests should use strip_root

gonna land this because it fixes the linux tests and seems right, but the mac tests seem to still be failing for probably some other reason.

@facebook-github-bot shipit


Profiles API

Description
Based on the profiles improvements suggested here , we need to move the two profiles endpoints from cluster service in weave-gitops-enterprise to profiles API in weave-gitops
service ProfilesService {
  // GetProfiles returns a list of profiles
  // from the cluster.
  rpc GetProfiles(GetProfilesRequest)
    returns (GetProfilesResponse) {
      option (google.api.http) = {
        get: "/v1/profiles"
      };
    }

  // GetProfileValues returns the contents of the `values.yaml` for a Profile
  // with a specific version.
  rpc GetProfileValues(GetProfileValuesRequest)
    returns (google.api.HttpBody) {
      option (google.api.http) = {
        get: "/v1/profiles/{profile_name}/{profile_version}/values"
      };
    }
}

Scope
The code is already written, we need to move it from WGE to wego-core. Make sure it works with WGE. If there are tests written, they should be moved too, if they are missing and then we'll have to add them.
Acceptance Criteria
As a developer
I want to move profile endpoints from cluster service in WGE to profiles api in weave-gitops
So that I can call the endpoints from Profiles API
Scenario: GetProfiles endpoint called from weave-gitops
Given that I am a developer
When I send a Get request to /v1/profiles
Then the endpoint should return the list of profiles
Scenario: GetProfilesValues endpoint called from weave-gitops
Given that I am a developer
When I send a Get request to /v1/profiles/{profile_name}/{profile_version}/values
Then the endpoint should return the contents of the values.yaml for a Profile with a specific version
Scenario: GetProfiles endpoint called from weave-gitops-enterprise
Given that I am a UI developer
When I send a Get request to /v1/profiles
Then the endpoint should return the list of profiles
Scenario: GetProfilesValues endpoint called from weave-gitops-enterprise
Given that I am a UI developer
When I send a Get request to /v1/profiles/{profile_name}/{profile_version}/values
Then the endpoint should return the contents of the values.yaml for a Profile with a specific version
Technical Notes

Find the current implementation of two endpoints here
Implement the Profiles API first in weave-gitops
Make sure the api is well tested and documented
Then proceed to remove/update weave-gitops-enterprise [details in a related ticket here]

Note: Needs investigation for how both EE and wego-core handles both endpoints and whether these endpoints co-exist in both repositories. Also need to find out how to coordinate releases with both repositories.

Also check with Yiannis about testing