Some canonical URLs are still not working

Just a note on this one. I think it's a configuration issue rather than code: www-1 seems to be set up with itself as a canonical host (rather than just www)
Example: https://www-1.nuget.org/profiles/WindowsSDK
Originally posted by @MatthewSteeples in https://github.com/NuGet/NuGetGallery/issues/8559#issuecomment-1007534574

This is deployed to PROD. Thanks again, @MatthewSteeples. Please let us know if you see anything else strange with canonical URLs.


LICENSE file

Hi. Before trying out themer, I checked for a license and noticed that none of the repos have a LICENSE file. I see that it's in each package.json's license field, but to make it more immediately obvious, please consider adding the file. GitHub even lets you do it from the UI.

Good call. I had thought the package.json field would be enough but I think you are right. I'll go ahead and add one to each repo.


About various format definitions

Is it possible to make mkldnn_nchw == mkldnn_oihw in value? (and 2 other group)
The rationale is that several frameworks create tensor without knowing its purpose. It might be weights or inputs/outputs until actual operator. From MKL-DNN's perspective these formats are equivalent when initializing and manipulating.

Hi @4pao,
Good question. Eventually this is something that should happen.
In fact, mkldnn_nchw and all the other aliases should be used only on user side to specify the initial data layout. The problem is that unfortunately this abstraction is leaked to MKL-DNN internals and now it is not that easy to get rid of it.
One of the really minor thing that prevents us to do that right now is -Wall -Werror. As long as we want to use two enums with the same values we need to be really careful with ifs and switches, since the code below would generate warning (and hence trigger an error):
swich (layout) {
case mkldnn_nchw: ...;
case mkldnn_oihw: ...; // the same, duplicating
};

Other than that I probably don't see any problems...

Hi @emfomenk,
Hmmm, that's minor issue. The real problem is grouped format.

Could you please elaborate?

@emfomenk Consider we've done making iohw == nchw, then we created two memory with nchw but at this time we used these memory object in an operator which had group number 2, we should use goihw to initialize the format. Can we make goihw == nchw too?

No way. goihw is 5D tensor while nchw or oihw are 4D tensor.

Oh, then creating 5D tensor means we want grouped weights. It doesn't need to merge these format. That's a relief. I did a test that make oihw == nchw, changed a few line of code, make it pass build and it pass all MKL-DNN tests. Conceptually, these two terms can merge.

Yeah, conceptually nothing is preventing us from doing that.
This is also aligned with (easy) bullet in this comment.


design(style): fix ignored bottom padding on Firefox

The bottom of the sidebar is obstructed by the TS/JS/Dart language picker in Firefox because the bottom padding amount is ignored. This is fixed by moving the padding into the margin of a child element.

cc @ericjim

+1
Since padding-bottom is ignored by many non-webkit browsers on elements with overflow:auto, the "Cookbook" section is not reachable if the "Advanced" section is selected.

+1
And do you guys think the sidebar scrolling seems wired? When the scrollbar is at the top or the bottom, a part of it is covered by the top nav or the bottom dropdown.
Perhaps we can remove both padding-top and padding-bottom of .sidenav and set top and bottom instead. That way we don't even need to care about the ignored bottom padding.

Made moot by replacing this site with angular/angular/aio


Error after Update

See screenshot ... Suggestions?

You need PHP 5.5 or higher for it to work (see README.MD).  I am out of the
computer right now, but if you can't update your php version I will look
into it and tell you how to change the problematic line of code later.
On Sep 1, 2015 04:18, "B.A. Umberger"<EMAIL_ADDRESS>wrote:

See screenshot ... Suggestions?
[image: screen shot 2015-08-31 at 9 12 01 pm]
https://cloud.githubusercontent.com/assets/5008228/9594812/b6a3292a-5025-11e5-962a-f6fdc3095cad.png
—
Reply to this email directly or view it on GitHub
https://github.com/aradianoff/recaptchacontact/issues/6.

Since v 1.0.6 this line in recapthcha.php causes the plugin to depend on php 5.5. Previous versions of PHP will cause the plugin to break. If you have a previous PHP version just substitute the !empty($this->grav['page'] ->collection()) in line 61 for $this->grav['page'] ->collection()!=[]. Future releases of this plugin will already include this change to allow compatibility with the previous versions.

I just released a new version that I think allows PHP 5.4.

I will update and let you know ... THX!

The update did not work. Same error.

However, once I update to PHP 5.5 all is well :)

I believe I was getting a similar error since updating to GRΛV <IP_ADDRESS>, reCAPTCHA 1.0.7:
Whoops\Exception\ErrorException thrown with message "Can't use method return value in write context"

Stacktrace:
#0  in /.../plugins/recaptchacontact/recaptchacontact.php:88

Just like @umbergerba, updating PHP to 5.5 (specifically for me, php 5.5 FastCGI) resolved the issue.

Thanks, Tele-Pet. I had forgot ln.88 used the same expression that gave problems with older PHP versions. I changed that line so that now I think it is really backwards compatible with PHP 5.4 in the next update. :smile:


Docs/improvements

Hello again @SebastianWolf-SAP :-)
I'm not 100% sure if the licensing with REUSE is done right here.
Could you have a look at that last commit and let me know?

Thanks for the suggestions @SebastianWolf-SAP . I also saw that our copyright information was missing from the LICENSE file in the project root. I added that.
Could you please check again?


[BUG] Can't generate vm template if vm is stopped

Describe the bug

To Reproduce
Steps to reproduce the behavior:

stop a vm
check if vm can generate template

Expected behavior

also can generate vm template when vm is stopped
Log

Environment:

Harvester ISO version:
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

@WuJun2016 should allow users to specify the template name and description when creating a VM template from the existing VM.

validated on master-0008ce84-head


Clean up Visual Studio version determination

Instead of parsing the installation path, we invoke link.exe and see which version it returns.
Successfully works with Visual Studio 12. I didn't test VS 14 but its link.exe also returns the correct version.

Out of curiosity, did you run into this? I'm curious what the environment looked like to trigger this

The current code assumes that you install Visual Studio in the default path, but I installed it in a directory simply named VisualStudio instead.

Ok sounds good to me, thanks!

Unfortunately I had to revert this as it caused a regression which apparently because it was running /usr/bin/link.exe instead of MSVC's link.exe.
I'm also not sure that the link.exe version printed corresponds to the MSVC version? For example the version printed through cl.exe is 19...

I'm also not sure that the link.exe version printed corresponds to the MSVC version? For example the version printed through cl.exe is 19...

That was determine empirically. The code currently only supports VS 12 and 14, and the link.exe of both VS 12 and 14 return the correct version. Maybe that's not the case for other versions of MSVC, but the person who will add support for another version will notice if it doesn't work.

Ah yeah that's a good point, sounds good to me! If there's a solution to choosing the wrong link.exe by accident I'd be fine relanding


nodejs{,-slim}_14: drop as it has reached end of life since 2023-04-30

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Replaced by https://github.com/NixOS/nixpkgs/pull/264358


[ENH] - Add support for .ppt / .pptx

Feature description
(Largely a copy/paste from #225)
Powerpoint documents are everywhere in the corporate world. We should support them out of the box. There are multiple Python packages out there that provide this functionality. We should do a light comparison of them to get a clearer picture. Optimally, we find a package that can give us page information. Not sure if that is possible in these data formats though.
Value and/or benefit
Users with corporate documents will have a lower barrier of entry.
Anything else?
No response

Let's go for it!

Hi!
I'd like to take this challenge as my first issue!
I have looked into issue #225 and #221 and I think the feature can be achieved using the library python-pptx which has similar API to python-docx, already used for #221
I've installed Ragna and looked at the codebase, but currently I can only work with RagnaDemo, as I don't have a vector DB or an API key for a LLM, but I think as long as we correctly define a DocumentHandler implementing

requirements(cls) -> list[Requirement]:
supported_suffixes(cls) -> list[str]
extract_pages(self, document: Document) -> Iterator[Page]

we should be fine, right? Of course I'll add testing and documentation.
Let me know if I can be assigned to this issue. Thanks!

I'd like to take this challenge as my first issue!

Hey Davide and welcome to Ragna :wave: Sure go ahead!

I've installed Ragna and looked at the codebase, but currently I can only work with RagnaDemo, as I don't have a vector DB or an API key for a LLM

You can install local Vector DBS, i.e. Chroma and LanceDB. Either do it manually, pip install
https://github.com/Quansight/ragna/blob/61e8d5f6618d0533a106e5c27c350e2a2e71621e/pyproject.toml#L58-L59
or simply use the catch-all key pip install -e '.[all]'.
But yes, without an LLM API key, there is only the demo assistant for now.

we should be fine, right? Of course I'll add testing and documentation.

Yes, that is sufficient. You can implement and test the document handler without having access to everything else.

Closed in #296.


VCPKG rebuilds packages each time and won't generate a "vcpkg_abi_info.txt"

Describe the bug
I created an overlay port directory of this structure:
~/git/project/vcpkg-ports (jschaub/mingw *+)$ tree -L 2
.
├── python3
│   ├── 0001-only-build-required-projects.patch
│   ├── 0002-static-library.patch
│   ├── 0003-use-vcpkg-zlib.patch
│   ├── 0004-devendor-external-dependencies.patch
│   ├── 0005-dont-copy-vcruntime.patch
│   ├── 0006-restore-support-for-windows-7.patch
│   ├── 0007-workaround-windows-11-sdk-rc-compiler-error.patch
│   ├── 0008-python.pc.patch
│   ├── 0009-bz2d.patch
│   ├── 0010-dont-skip-rpath.patch
│   ├── 0011-gcc-ldflags-fix.patch
│   ├── 0012-force-disable-curses.patch
│   ├── 0013-configure-no-libcrypt.patch
│   ├── openssl.props.in
│   ├── patches-mingw
│   ├── portfile.cmake
│   ├── python_vcpkg.props.in
│   ├── usage
│   ├── usage.unix
│   ├── usage.win
│   ├── vcpkg-cmake-wrapper.cmake
│   └── vcpkg.json
└── README.md

In the patches-mingw folder, I have several patches that allow building the port on x64-mingw-dynamic triplet of VCPKG. It works and installs all fine. We use manifest mode and declare pybind11 (and thereby python3) as a dependency:
{
  "dependencies": [
   ...
    "pybind11",
  ],

  "builtin-baseline": "501db0f17ef6df184fcdbfbe0f87cde2313b6ab1",
  "overrides": [
    { "name": "catch2", "version": "2.13.9#1" }
  ]
}

I expected that when I run cmake a second time, nothing happens since everything was built. When cmake is run again a second time, VCPKG outputs:
-- Bootstrapping vcpkg before install
-- Bootstrapping vcpkg before install - done
-- Running vcpkg install
Detecting compiler hash for triplet x64-mingw-dynamic...
The following packages will be rebuilt:
    pybind11:x64-mingw-dynamic -> 2.10.3 -- C:\vcpkg-btrees\versioning_\versions\pybind11\a3b13210bfd5f8dcbab60336dd54f0ed7230c5c3
  * python3:x64-mingw-dynamic -> 3.10.7#6 -- C:/bbot/robo/build/vcpkg-ports\python3
Additional packages (*) will be modified to complete this operation.

I wanted to look into the vcpkg_abi_info.txt of the second build to try and compare it with a third build. However, the share/python3 folder in the install root only contains:
"C:\bbot\robo\build\.out\build\debug-mingw\vcpkg_installed\x64-mingw-dynamic\share\python3\vcpkg-cmake-wrapper.cmake"
"C:\bbot\robo\build\.out\build\debug-mingw\vcpkg_installed\x64-mingw-dynamic\share\python3\copyright"
"C:\bbot\robo\build\.out\build\debug-mingw\vcpkg_installed\x64-mingw-dynamic\share\python3\usage"
"C:\bbot\robo\build\.out\build\debug-mingw\vcpkg_installed\x64-mingw-dynamic\share\python3\vcpkg.spdx.json"

A minor detail which may be important: Before cmake is executed, our CI transfers the sourcecode (including the .git folder which is required for vcpkg, which is a submodule) from a developer's machine to the CI working directory. For the majority of packages, that doesn't cause a rebuild and probably isn't the cause of problems in the above case, I guess.
Environment

OS: Windows 11, x64-mingw-dynamic triplet

Compiler:

g++.exe (x86_64-posix-seh-rev2, Built by MinGW-W64 project) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Further investigation by passing --debug to VCPKG shows this output after gathering all ABI values for python3:
[DEBUG] Warning: abi keys are missing values:
    no_hash_max_portfile
[DEBUG] Binary caching for package pybind11:x64-mingw-dynamic is disabled due to missing abi info for python3

I have no idea yet how to fix that!

@RealLitb Thanks for posting this issue.
In my opinion, this is a port protection mechanism.
For your specific question:
AFAIU, the principle of patching is mainly to ensure the timeliness, accuracy and effectiveness of patches, while minimizing the impact on system stability and user experience.
Since you use the overlay port, you can completely fork a pybind11 github project and synchronize the content you want to modify instead of applying a large number of patches.

Even if the 100-file limit is to stay, there seems to be a need for better reporting of this state, such as a postbuild check warning message.


How to test with custom dataset?

Hi,
I've trained your pytorch version model using the MSRA dataset and it works well, and the next step I'd like to use the trained model to run on my own dataset, may I ask how to prepare the centered data like the paper described?
Thanks!

Hi eris231,
What's your dataset ? If you are doing experiment on hand depth images like MSRA dataset, you could firstly try the way the paper does. If you have any further questions, you may also ask the paper's author directly on his repo(since I have not computed the center yet).

Hi dragonbook,
I am trying to use this model to get the 3D coordinate from the depth image I recorded myself, and since the paper has described another network for center calculation, I was wondering if you have any plan to implement that.
Thanks

ok thanks for reply!

@eris231 Do you find a method to find the center? Thanks!

@eris231 Do you find a method to find the center? Thanks!


Unable to resolve module toolbar-android

Environment
Platform: Android
react-native: 0.61.0
react-native-vector-icons: 7.0.0
Description
Error: Unable to resolve module ./toolbar-android from node_modules/react-native-vector-icons/lib/create-icon-set.js

I've got the same error, did you find a solution ?

For me the issue appeared when using 6.7.0. Upgrading to 7.0.0 did the trick for me.
Did you try to pin 6.6.0?

Finally found a solution.
I'm using 6.7.0, and I just download @react-native-community/toolbar-android. That did the trick.
I know it's not the perfect solution, but a workaround. My iOS app doesn't use the toolbar, but she work anymore.

I was with the same error. The problem solve when I updated to version 7.0.0

For me the problem appeared when going from 6.6.0 -> 7.0.0.
Still trying to resolve it.

Is your environment in MacOS is like Windows?
I'm using MacOS too, I've never tested my project in other OS.
My environment:
RN: 0.63.0.
Node: 10.16.3
OS: MacOS Catalina v10.15.5

Same issue with 7.0.0  RN 0.63.2

I tested my solution even until version "^7.0.0" and the following command will help you:
yarn add @react-native-community/toolbar-android

By using this solution, everything will be ok.
see complete solution on Stack Overflow

Same issue, I solved it:
My environment:
RN: 0.61.5
Node: v12.18.3
OS:  Windows 10 Pro
You can install react-native-vector-icons latest version (current 7.0.0).
And do not use link (react-native link react-native-vector-icons)
Finally, running react-native start --reset-cache
Good luck.

@lamson-dev , @vishwanath-awate , @developerantoniosousa , @RosenTomov , @AlessioCamm
I tested my solution even until version "^7.0.0" and the following command will help you:
yarn add @react-native-community/toolbar-android

By using this solution, everything will be ok.
see complete solution on Stack Overflow

@lamson-dev , @vishwanath-awate , @developerantoniosousa , @RosenTomov , @AlessioCamm , @saxenanickk
I tested my solution even until version "^7.0.0" and the following command will help you:
yarn add @react-native-community/toolbar-android

By using this solution, everything will be ok.
see complete solution on Stack Overflow

@amerllica I solved the problem updating to v7.x.x. It's worked well for me. Thanks for mentioning me.

@developerantoniosousa, Thanks for your comment, I just tested the "7.0.0" version and the issue still remains, as soon as possible I will test the latest version "7.1.0".

At last, the issue is fixed on version "7.1.0", and there is no need to install @react-native-community/toolbar-android.
More explanation is on this StackOverflow post

@lamson-dev , @developerantoniosousa , @vishwanath-awate , @RosenTomov , @AlessioCamm , @jsbeckr , @saxenanickk
At last, the issue is fixed on version "7.1.0", and there is no need to install @react-native-community/toolbar-android.
More explanation is on this StackOverflow post

This feature has since been deprecated


Added Australian Catalog and Pricing

this is a simple update as a courtesy to Australia/New Zealand Builders.  I have included localised vendors for the electronic components and assemblies.

I think what's best is to have a different branch for this instead. I like the idea but I feel like if we do this for one country outside the US then we have to support adding any /all, and it feels like that is going to make the parts list unmanageable

thanks @au-chrismor for putting this together!  This will be a huge help to our friends in Australia and New Zealand!
I also have a bit of heartache with this particular pull request, but only because our current parts list is auto-generated from the build docs and we'd want to follow that same pattern with international parts lists.
I think the best way to proceed is to add a folder in the already existing parts_list/ folder for international builds.  That way, as we push forward and continue to make updates to the project, the international parts lists will not get lost in a deprecated branch that possibly hasn't been updated.
@au-chrismor, I suggest that you review the README document in the parts_list/ folder of our repository at https://github.com/nasa-jpl/open-source-rover/tree/master/parts_list.  That folder contains information about how our parts lists are auto-generated from our build documents.  I think that you should be able to add a new folder (international/ or similar) and add your own custom version of the parts_list_reference.csv file, so that we can automatically re-build the international parts lists as we move forward and make other changes to the project.
Let us know if you have any questions or concerns.  Thanks again for making this addition to the project!

Ok,I will create a branch for international components as presented.  Perhaps others will chime in further down the line.  I realized immediately upon generating the request that I  didn't check the build process, so apologies for that.If someone with rights can kill my merge request. That would be great.Thanks,Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: "Mik (Michael) Cox"<EMAIL_ADDRESS>Date: 11/5/19  03:06  (GMT+10:00) To: nasa-jpl/open-source-rover<EMAIL_ADDRESS>Cc: Chris Moran<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [nasa-jpl/open-source-rover] Added Australian Catalog and Pricing (#112) thanks @au-chrismor for putting this together!  This will be a huge help to our friends in Australia and New Zealand!
I also have a bit of heartache with this particular pull request, but only because our current parts list is auto-generated from the build docs and we'd want to follow that same pattern with international parts lists.
I think the best way to proceed is to add a folder in the already existing parts_list/ folder for international builds.  That way, as we push forward and continue to make updates to the project, the international parts lists will not get lost in a deprecated branch that possibly hasn't been updated.
@au-chrismor, I suggest that you review the README document in the parts_list/ folder of our repository at https://github.com/nasa-jpl/open-source-rover/tree/master/parts_list.  That folder contains information about how our parts lists are auto-generated from our build documents.  I think that you should be able to add a new folder (international/ or similar) and add your own custom version of the parts_list_reference.csv file, so that we can automatically re-build the international parts lists as we move forward and make other changes to the project.
Let us know if you have any questions or concerns.  Thanks again for making this addition to the project!
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/nasa-jpl/open-source-rover/pull/112#issuecomment-491361245",
"url": "https://github.com/nasa-jpl/open-source-rover/pull/112#issuecomment-491361245",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

Backing out of this merge after discussions.  Will revisit later

@au-chrismor: When you do this, please create a folder within the same master branch rather than creating an entirely new branch dedicated to international builds.
The flow should probably be:

Create a new international/ folder within the existing parts_list/ folder
Create a folder for Australia / New Zealand
Duplicate the existing parts_list_reference.csv into the Australia / New Zealand folder and make the necessary changes to modify the vendors and links for our Australia / New Zealand friends
Modify the parts_list/build.py script to also search into each subdirectory of the international/ folder and generate a version of the master parts list for that country

Let us know if you have any questions on this or need assistance.  It'll be a great feature; thanks for bringing it up and considering contributing!!

guys what do you think about AI controlling the rover it’s will be more easy after sending him to mars and taking by himself all the data
for all how thing about it’s groupe will be also created in WhatsApp just text this number with your name and you degree thanks number is<PHONE_NUMBER>455
On May 11, 2019, at 4:38 PM, Mik (Michael) Cox <notifications<EMAIL_ADDRESS>wrote:
@au-chrismorhttps://github.com/au-chrismor: When you do this, please create a folder within the same master branch rather than creating an entirely new branch dedicated to international builds.
The flow should probably be:

Create a new international/ folder within the existing parts_list/ folder
Create a folder for Australia / New Zealand
Duplicate the existing parts_list_reference.csv into the Australia / New Zealand folder and make the necessary changes to modify the vendors and links for our Australia / New Zealand friends
Modify the parts_list/build.py script to also search into each subdirectory of the international/ folder and generate a version of the master parts list for that country

Let us know if you have any questions on this or need assistance. It'll be a great feature; thanks for bringing it up and considering contributing!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/nasa-jpl/open-source-rover/pull/112#issuecomment-491525923, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKKAZEN24VGFNJOUVVREIB3PU3ZB3ANCNFSM4HMCFJRQ.

Hi All,
I've followed those recommendations, and I agree, it's a much better way.
Hopefully now others can share their local information.
Thanks for all the feedback.
On Sun, May 12, 2019 at 2:38 AM Mik (Michael) Cox<EMAIL_ADDRESS>wrote:

@au-chrismor https://github.com/au-chrismor: When you do this, please
create a folder within the same master branch rather than creating an
entirely new branch dedicated to international builds.
The flow should probably be:

Create a new international/ folder within the existing parts_list/
folder
Create a folder for Australia / New Zealand
Duplicate the existing parts_list_reference.csv into the Australia /
New Zealand folder and make the necessary changes to modify the vendors and
links for our Australia / New Zealand friends
Modify the parts_list/build.py script to also search into each
subdirectory of the international/ folder and generate a version of the
master parts list for that country

Let us know if you have any questions on this or need assistance. It'll be
a great feature; thanks for bringing it up and considering contributing!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nasa-jpl/open-source-rover/pull/112#issuecomment-491525923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACN5SU5BPGM6YUZZR3AOQCLPU3ZB5ANCNFSM4HMCFJRQ
.


htop displays black screen

Please fill out the below information:

Your Windows build number:  Microsoft Windows [Version 10.0.18363.778]

What you're doing and what's happening:  Programs such as htop are not working in WSL Ubuntu 20.04LTS. After I run htop I get a black screen that I can only leave with CTRL+C command.

What's wrong / what should be happening instead: I was expecting to see htop on the cmd, or windows terminal.

Strace of the failing command, if applicable:  https://gist.github.com/agostini01/dfa637de22743894ca845039f1d3e3f6

Additional notes: may be related to issue#25 (https://github.com/Microsoft/WSL/issues/25) . Can be an ncurses problem.

Let me know how can I further help. Thanks

Thank you for reporting this.
This is a duplicate of #4898 and there is a workaround for htop specifically there.
A fix is in testing.
It is being tracked in Ubuntu WSL here https://bugs.launchpad.net/ubuntuwsl/+bug/1871129
This bug report should be closed but you can subscribe to those other two bugs for updates.

/dupe #4898

Is this really a dupe? I'm seeing this under WSL 2 and not WSL 1, which is what #4898 refers to ...

It is. The workaround in #4898 works in WSL2 as well.

I'm getting a black screen on wsl 2

Just follow these steps:
sudo add-apt-repository ppa:rafaeldtinoco/lp1871129
sudo apt update
sudo apt install libc6=2.31-0ubuntu8+lp18711291 libc6-dev=2.31-0ubuntu8+lp18711291 libc-dev-bin=2.31-0ubuntu8+lp1871129~1 -y --allow-downgrades
sudo apt-mark hold libc6

This versions don't exist now. How to make htop work?

Tried the fix, same problem above as "woreom"

Same problem here as woreom.
Black screen in the htop and the update is failed.
Reading state information... Done
E: Version '2.31-0ubuntu8+lp18711291' for 'libc6' was not found
E: Version '2.31-0ubuntu8+lp18711291' for 'libc6-dev' was not found

I'm getting the same version found error.. Has there been any update on this issue?


Build for x64 & arm

This pull request includes changes to enable building for both x64 and arm architectures. It adds support for multiarch builds using QEMU and Docker buildx. The Docker images are tagged with the respective architecture (amd64 or arm64) and are pushed to the GitHub Container Registry.

Not sure if this will work or not 🤷♂


Triggering build on form submission

Hey Phil! Thanks for the cool example. I was just reading through the blog post and was wondering how exactly the re-build is triggered when you submit a link to the form.
This line in the code suggests it's happening, but you aren't posting to a webhook. Is there a way to configure Netlify to rebuild automatically on form submission?

I have the same question - I got to the point where i got the Buildhook URL, but don't know where to put it


Status bar items do not preserve whitespace between codicons

Extracted from https://github.com/microsoft/vscode/issues/145722
If you bring up a status bar entry with 2 codicons next to each other only separated by whitespace, the 2 icons are still rendered as if there was no white space:

HTML is:

Code:
const statusService = accessor.get(IStatusbarService);

statusService.addEntry({
	name: 'name',
	ariaLabel: 'label',
	text: '$(mark-github) $(mark-github)',
}, 'my.id', StatusbarAlignment.LEFT);

I traced this down to the fact that the parent anchor tag of a status item uses display: flex and this seems to collapse whitespace elements, as outlined in e.g. https://www.mattstobbs.com/flexbox-removing-trailing-whitespace/
However, we already set white-space: pre as suggested:
https://github.com/microsoft/vscode/blob/0140fba8bb128d7481a4bcd380de774ab1210c5d/src/vs/workbench/browser/parts/statusbar/media/statusbarpart.css#L118
Opening up for help for a CSS wizard to look at. Ideally all whitespaces between 2 codicons are preserved for styling purposes.
//cc @daviddossett @misolori @joaomoreno

Ah so, this originates from your change @misolori
https://github.com/microsoft/vscode/commit/ef84173ea6e64ee8f7126bbf3f5dc2c51eff798b#diff-b4dccdf238cc73547c4eefcfbac679210115fd5e0dc2fc9902844d6116b0e915
Maybe you have an idea.

The whole status bar might require a larger refactoring to use gap instead of margin-left or margin-right on each element: https://developer.mozilla.org/en-US/docs/Web/CSS/gap#flex_layout

Before boiling the ocean, an alternative is to wrap whitespaces into span itself to preserve them. I.e. here:
https://github.com/microsoft/vscode/blob/fcbf1eb903ad019fbd003d754067d0728d79d498/src/vs/workbench/browser/parts/statusbar/statusbarItem.ts#L285
and here
https://github.com/microsoft/vscode/blob/fcbf1eb903ad019fbd003d754067d0728d79d498/src/vs/workbench/browser/parts/statusbar/statusbarItem.ts#L290
Something along the lines of:
renderLabelWithIcons(text ?? '').map(value => {
	if (value instanceof HTMLSpanElement) {
		return value;
	}

	if (value.trim().length === 0) {
		const spacer = $(`span`);
		spacer.textContent = value;

		return spacer;
	}

	return value;
})

It's a bit ugly though and a pure CSS solution that only impacts white space would still be nice. Maybe we can go back to inline-block.

Status bar containers are flex. We always want status bar items to have spacing between them. So using gap is the only logical option. It's far from boiling an ocean.
The current solution of making up space by using :first-child and margin or padding is outdated and prone to errors, as we can now clearly see. I would not add yet another hack to that.

I think you are confusing things. There is a display: flex for status bar items to position them and yes maybe we can use gap there to drop a few CSS rules that are hard to understand. But we also started to use display: flex within a status bar item, which imho is not needed because a status bar item itself does not use flex layout at all.
I believe the only reason for having added display: flex is to align the codicon icons well when used inside a status bar item.

If you bring up a status bar entry with 2 codicons next to each other only separated by whitespace, the 2 icons are still rendered as if there was no white space:

Oh these are two icons in a single status bar entry. Why not simply using gap in that flex element then?

gap seems to stretch every status bar item then:

This is really very specific to the fact that there is whitespace between the span, everything else is proper. I think gap will cause other regressions.

Is there any way that we can transform a space (when next to other $(icon) elements) into a &nbsp? That seems to help preserve that spacing:

@misolori I had tried adding that explicitly e.g. $(bell) $(bell) without any luck. But maybe I was holding it wrong..

Yeah I think that would work at the place where we build the HTML elements, but I wouldn't suggest to force extension devs to use it.

I wasing trying to add this via a PR.
.monaco-workbench .part.statusbar>.items-container>.statusbar-item span.codicon::before {    content: " ";    white-space: pre; }
wanted to add more specificity to preserve the whitespace before this particular span.

@bpasero (@daviddossett @joaomoreno @misolori) I think I have a solution to this!
I believe the issue is that because span tags are inline elements by default any potential spacing you add to them will just be collapsed in a flex container. By setting the span as inline-block you should be able to add margin, padding, etc. without issue.
a > span {
  display: inline-block;
  margin-right: 10px;
}

I also made a super small reproduction in vanilla HTML/CSS to validate this works if you're curious, but assuming I've understood the issue correctly and all looks good I'd be happy to make a PR for this!

Oh shoot, looking back more closely I just realized the hope is to respect the literal whitespace characters between spans versus having spacing between icons in general.
The solution I have above could potentially be used if there's a decision that these icons should always have space between them, but would technically break the scenario where someone does not include spaces in the text field:
text: '$(mark-github)$(mark-github)', // <-- this would still render a 10px margin between icons despite no space in text

@hawkticehurst I think the solution for this issue is to first select all the sibling span element with the General sibling combinator. Look for more info here https://developer.mozilla.org/en-US/docs/Web/CSS/General_sibling_combinator
Then add margin-inline-start: a value;  plus writing-mode: horizontal-tb; properties to the selection.
https://developer.mozilla.org/en-US/docs/Web/CSS/margin-inline-start

In every trial I wanted to do this issue, a new aspect unfolded. This is not ideal as it adds to the workload rather than providing a straightforward solution.
First, to address the misalignment of icons and the text, I could come up with these solutions:
The icons do not have the same font-size as the text and this is because of the last line of code in the statubar.css:
https://github.com/microsoft/vscode/blob/d17726fe4beae5abe87ba9e9429cd298be8b53c4/src/vs/workbench/browser/parts/statusbar/media/statusbarpart.css#L146

Here the codicon icons wrapped in the spans are selected. This excludes the text included in the a tags. A suggestion for this is to change the selection in this way:

.monaco-workbench .part.statusbar > .items-container > .statusbar-item  a {
	text-align: center;
	font-size: 16px;
}

And to reposition the icons using transform: translate(2px, 1px);  property only for the icons. This can re-position them and align them with the text:

.monaco-workbench .part.statusbar > .items-container > .statusbar-item  span.codicon {
   transform: translate(2px, 1px);
   color: inherit;
}

To also align the text also, I suggest changing the line height on this selection:
https://github.com/microsoft/vscode/blob/d17726fe4beae5abe87ba9e9429cd298be8b53c4/src/vs/workbench/browser/parts/statusbar/media/statusbarpart.css#L10
Note: Changing its value only pushes items with the text in the div with the class=”status-bar-item left” to the upward direction or to the downward not the other items.
Something else to add:
some icons maybe were wrong picks for the test as they may need custom sizing to align properly.

As for the space between codicons icons, there is a specific scenario. The left section of the status bar has three separate sections. These sections are:

First-visible-item : We have a div with the class=”first-visible-item” this one is a solid subsection without the flexibility of many icon changes.
Middle (meaning without a specific class) : We have a div with the class=”left”  For this is for git branches, loading, and other synchronizations.
Last-visible-item: We have a div with the class=”last-visible-item” right after this one, here I can see there are warning icons and error icons.

My assumption was that all the extension icons would be added to the middle section of the left part of the status bar. However, the real examples I see on my desktop vscode app prove the other cases:
In this subsection, as an example, the gitlens extension adds two icons one before the warning icons and error icons in the last-visible-item div and one after.

Correction: these are two different extensions but my point here remains the same ( extensions add icons to different subsections of the status bar)
the other point is that, Also, a div has the display:inline-block property .  An example of this is line 43:
https://github.com/microsoft/vscode/blob/d17726fe4beae5abe87ba9e9429cd298be8b53c4/src/vs/workbench/browser/parts/statusbar/media/statusbarpart.css#L43
If changing the display property won't affect the items because of the nature of the statue bar, maybe display:inline-block can be used for other sections as well. Then the application of margin left and right can be easily done.
As a suggestion, maybe Instead of sectioning the main status bar div we can change the selectors like this:

span:first-of-type()
span:nth-of-type()
span:last-of-type()

and exclude any item that is not needed with :not() selector.

@bpasero if this is still valid for when there are 2 to 4 icons (pointing to the issue it is extracted from) then would mention the placement of the icons? as it possibly can not be done with CSS if the place of icons is interchangeable though out the whole status bar.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


JIT: Support cub::WarpReduce and cub::BlockReduce

Part of PFN summer internship project made by @TsutsuiMasayoshi (3/4)
This PR supports cub::WarpReduce.
Blocked by #7139.

/test

mypy error :(
cupyx/jit/_compile.py:874: error: Incompatible types in assignment (expression has type "Data", variable has type "expr")
cupyx/jit/_compile.py:874: error: Argument 1 to "init" of "Data" has incompatible type "expr"; expected "Expr"
cupyx/jit/_compile.py:875: error: Argument 1 to "_emit_assign_stmt" has incompatible type "expr"; expected "Union[Constant, Data]"
Found 3 errors in 1 file (checked 292 source files)

/test mini

/test mini

/test mini


Automated cherry pick of #3030: fix: disable cas idp not working

Cherry pick of #3030 on release/2.12.
#3030: fix: disable cas idp not working

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@bb5b39c). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.12   #3032   +/-   ##
==============================================
  Coverage                ?   7.17%
==============================================
  Files                   ?     478
  Lines                   ?   76701
  Branches                ?       0
==============================================
  Hits                    ?    5504
  Misses                  ?   70734
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.17% <ø> (?)

Continue to review full report at Codecov.

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

/approve
/lgtm


surface the overlap table in the API

we have https://github.com/opentargets/v2d_data#locus-overlap-table and to serve the multi-trait view it would be useful to serve it from the API.

@edm1 and I talked about loading the table this afternoon, but i see that @mkarmona was quicker than us. It's already in clickhouse 😄 👍
There are two queries that we should do on this data:

for a given study id, return the top 10 studies overlapping with its loci:

query{
overlap(studyId_a){
// returning a sorted list of overlapping studies
[ {studyInfo_b,num_overlapping_variants},...]
}
}

which would return the result of the following query:
SELECT
    study_id_a,
    study_id_b,
    uniq(index_variant_id_A) AS num_overlap_variants
FROM ot.studies_overlap
WHERE study_id_a = 'GCST000274'
GROUP BY
    study_id_a,
    study_id_b
ORDER BY num_overlap_variants DESC
LIMIT 10

┌─study_id_a─┬─study_id_b─┬─num_overlap_variants─┐
│ GCST000274 │ GCST000274 │                   16 │
│ GCST000274 │ GCST006034 │                    2 │
│ GCST000274 │ GCST000755 │                    2 │
│ GCST000274 │ GCST004232 │                    2 │
│ GCST000274 │ GCST000290 │                    2 │
│ GCST000274 │ GCST002899 │                    2 │
│ GCST000274 │ GCST002216 │                    2 │
│ GCST000274 │ GCST002896 │                    2 │
│ GCST000274 │ GCST002223 │                    2 │
│ GCST000274 │ GCST001414 │                    2 │
└────────────┴────────────┴──────────────────────┘

10 rows in set. Elapsed: 0.018 sec.

Given two or more studies, return those variants in common across all studies.
The Api should return the intersection of the arrays returned by the query:

SELECT
    study_id_a,
    study_id_b,
    groupUniqArray(index_variant_id_a)
FROM ot.studies_overlap
PREWHERE (study_id_a = 'GCST000274') AND (study_id_b IN ('GCST001414', 'GCST004607'))
GROUP BY
    study_id_a,
    study_id_b
LIMIT 50

┌─study_id_a─┬─study_id_b─┬─groupUniqArray(index_variant_id_a)────┐
│ GCST000274 │ GCST001414 │ ['11_61571348_C_G','15_58674695_G_C'] │
│ GCST000274 │ GCST004607 │ ['11_61571348_C_G']                   │
└────────────┴────────────┴───────────────────────────────────────┘

not only included but I also have a branch with the API working hehe
@elipapa @dm1. sounds great, I will check again what I already coded but I
came up with the same reasoning .
On Wed, 26 Sep 2018, 00:36 elipapa<EMAIL_ADDRESS>wrote:

@edm1 https://github.com/edm1 and I talked about loading the table this
afternoon, but i see that @mkarmona https://github.com/mkarmona was
quicker than us. It's already in clickhouse 😄 👍
There are two queries that we should do on this data:

for a given study id, return the top 10 studies overlapping with
its loci:

query{overlap(studyId_a){
// returning a sorted list of overlapping studies
[ {studyInfo_b,num_overlapping_variants},...]
}
}
which would return the result of the following query:
SELECT
study_id_a,
study_id_b,
uniq(index_variant_id_A) AS num_overlap_variantsFROM ot.studies_overlap WHERE study_id_a = 'GCST000274'GROUP BY
study_id_a,
study_id_bORDER BY num_overlap_variants DESCLIMIT 10
┌─study_id_a─┬─study_id_b─┬─num_overlap_variants─┐
│ GCST000274 │ GCST000274 │                   16 │
│ GCST000274 │ GCST006034 │                    2 │
│ GCST000274 │ GCST000755 │                    2 │
│ GCST000274 │ GCST004232 │                    2 │
│ GCST000274 │ GCST000290 │                    2 │
│ GCST000274 │ GCST002899 │                    2 │
│ GCST000274 │ GCST002216 │                    2 │
│ GCST000274 │ GCST002896 │                    2 │
│ GCST000274 │ GCST002223 │                    2 │
│ GCST000274 │ GCST001414 │                    2 │
└────────────┴────────────┴──────────────────────┘
10 rows in set. Elapsed: 0.018 sec.

Given two or more studies, return those variants in common across
all studies.
The Api should return the intersection of the arrays returned by the
query:

SELECT
study_id_a,
study_id_b,
groupUniqArray(index_variant_id_a)FROM ot.studies_overlap
PREWHERE (study_id_a = 'GCST000274') AND (study_id_b IN ('GCST001414', 'GCST004607'))GROUP BY
study_id_a,
study_id_bLIMIT 50
┌─study_id_a─┬─study_id_b─┬─groupUniqArray(index_variant_id_a)────┐
│ GCST000274 │ GCST001414 │ ['11_61571348_C_G','15_58674695_G_C'] │
│ GCST000274 │ GCST004607 │ ['11_61571348_C_G']                   │
└────────────┴────────────┴───────────────────────────────────────┘
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opentargets/genetics/issues/112#issuecomment-424536220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFJPOG5yzxpLD1uzxMmnHjS_U5WhGNK4ks5uer33gaJpZM4Wru6N
.

the real query we want to get the intersection result of index_variants from study A
SELECT
    index_variant_id_a,
    uniq(study_id_b) AS num_studies
FROM ot.studies_overlap
PREWHERE (study_id_a = 'NEALEUKB_50') AND (study_id_b IN ('NEALEUKB_20015', 'NEALEUKB_1697')) AND (set_type = 'combined')
GROUP BY index_variant_id_a
HAVING num_studies = 2
LIMIT 10

@edm1 @elipapa is there a reason to limit to 50 the overlap variants? it is not sorted so I guess it is a error in your query, isn't it?

As in your above query, there should be no limit on this.

the api is getting there
query test4 {
  manhattan(studyId:"NEALEUKB_50") {
    associations {
      variantRsId
      ldSetSize
      credibleSetSize
    }
    topOverlappedStudies {
      topStudiesByLociOverlap {
        study {
          studyId
        }
        numOverlapLoci
      }
    }
  }
  topOverlappedStudies(studyId:"NEALEUKB_50") {
    study {
        pmid
        pubDate
        pubJournal
        pubTitle
        pubAuthor
        nInitial
        nReplication
        nCases
        traitCategory
    }
    topStudiesByLociOverlap {
      study {
        studyId
        traitReported
      }
      numOverlapLoci
    }
  }

  overlapInfoForStudy(studyId:"NEALEUKB_50", studyIds:["NEALEUKB_20015", "NEALEUKB_1697"]) {
    study {
      studyId
    }
    overlappedVariantsForStudies {
    	study {
      	studyId
   		}
    	overlaps {
      	variantIdA
      	variantIdB
      	overlapAB
      	distinctA
      	distinctB
    	}
    }
    variantIntersectionSet
  }
}

@edm1 @elipapa is there a reason to limit to 50 the overlap variants? it is not sorted so I guess it is a error in your query, isn't it?

As in your above query, there should be no limit on this.

yup, just a copy paste typo. sorry.


https configurations not populated for route?

Description:
I am trying to install envoygateway with proxyprotocol enabled in both http and https. However, it does not work for https.
Repro steps:
install gateway controller
kubectl create ns envoy-gateway-system-external
kubectl label ns envoy-gateway-system-external pod-security.kubernetes.io/audit=baseline --overwrite
kubectl label ns envoy-gateway-system-external pod-security.kubernetes.io/enforce=baseline --overwrite
helm upgrade eg-external oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system-external --install -f external/values.yaml

values.yaml https://gist.github.com/zetaab/e08c957f0139f87533c55086f7f9ab4e
deploy.yaml: https://gist.github.com/zetaab/4838972dffb7f0143592f058333980a7
app.yaml https://gist.github.com/zetaab/c8ff93b05f460141abe3300a2da09e1d
% curl https://eg-ext.example.com -I
HTTP/2 404
date: Sun, 28 Jan 2024 16:45:45 GMT
server: envoy

% curl http://eg-ext.example.com -I
HTTP/1.1 200 OK
content-type: application/json; charset=utf-8
content-length: 1298
etag: W/"512-naqzlUgvLR3xY9+dP7je64t35bw"
date: Sun, 28 Jan 2024 16:45:50 GMT
x-envoy-upstream-service-time: 3
server: envoy

Environment:
Kubernetes 1.29.1
Logs:
https://gist.github.com/zetaab/052de1f3d65d4b5b8074df8988183c18 as we can see it does not populate anything under https listeners? Specs https://gateway-api.sigs.k8s.io/guides/implementers/#httproute says

HTTPRoutes route HTTP traffic that is unencrypted and available for inspection. This includes HTTPS traffic that's terminated at the Gateway (since that is then decrypted), and allows the HTTPRoute to use HTTP properties, like path, method, or headers in its routing directives.

So it should work (as it should include terminated traffic in gateway?). Am I missing something in httproute object?

my bad, was missing
      allowedRoutes:
        namespaces:
          from: All

in https listener


[Suggestion] Dark headers for space-gray theme (Tautulli, NZBGet, LazyLibrarian)

This is not a bug, entirely a suggestion that is open to your personal preference. If you disagree, feel free to close.
I noticed that the space-gray theme has a dark header for certain apps like the Arrs and NZBHydra. The header gives a good contrast and looks very clean in my opinion. Other apps are missing this distinction, so the header sort of blends into the body of the page. Both from a consistency as well as a theme perspective, I think adding similar black headers to apps that are missing them could enhance the theme.
Apps with dark headers already

Apps missing black headers

Example of Tautulli with black header

I'll answer you here as well.. Heh
Yeah, there's a bit of inconsistency between themes. It looks better with dark header standalone. But when using org it looks better without lol..
https://selfhosted.app/f3c10/SicopEdu01.png
But yeah I might add headers to all . Theres a lot of different inconsistencies I havent really made a cheat sheet to use when making the themes. To much work lol


Update ARN delimiter parsing in endpoint provider

This addresses a bug for aws_parse_arn in endpoint_provider.RuleSetStandardLibrary. Currently the resourceId portion of a parsed ARN was only thought to either have a / or : as a delimiter. However, in services such as kinesis, they can have both.
Current Behavior
arn:aws:kinesis:1234567890:us-east-1:thing/foo:bar  -> {...'resourceId': ['thing/foo', 'bar']}
New Behavior
arn:aws:kinesis:1234567890:us-east-1:thing/foo:bar  -> {...'resourceId': ['thing', 'foo', 'bar']}

Codecov Report
Base: 93.53% // Head: 93.53% // No change to project coverage :thumbsup:

Coverage data is based on head (21cb317) compared to base (9b6f5ad).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2831   +/-   ##
========================================
  Coverage    93.53%   93.53%
========================================
  Files           63       63
  Lines        13382    13382
========================================
  Hits         12517    12517
  Misses         865      865

Impacted Files
Coverage Δ

botocore/endpoint_provider.py
99.35% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@jonemo thanks for the feedback. I did some testing of my own and I do also see that the standard string splitting in Python is much faster than using regex. We needed to get this merged before today's release otherwise I would've waited for more feedback, but I'll put up a followup PR that we can merge later today or tomorrow.


Space.css Theme

The Final Fronter.
A Simple Theme for AMP <IP_ADDRESS> and can be used as a starter CSS Template for other to build from.

Needs updates to latest css format now


fix(cli): Conform python and java package names to language standards (no hyphens)

With new changes in jsii-srcmak, it throws an Error when trying to use a package or moduleName with a hyphen (see commit: https://github.com/aws/jsii-srcmak/commit/766de96d655463dadf5a9578ba38d47121be447b)
This is the other side of that and fixes that issue by replacing - with _.
Tested by changing the version.yaml in the python CRD example to use a hyphen in the name. It successfully comes in as an underscore and is able to be imported.
Fixes https://github.com/awslabs/cdk8s/issues/274
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Looks like I missed updating the snapshots in the unit tests. Will do that tomorrow!


merge_feed PostgreSQL query syntax error

# ./manage.py merge_feeds
DatabaseError: invalid reference to FROM-clause entry for table "f"
LINE 11: ...  INNER JOIN rss_feeds_feeddata fd ON fd.feed_id = f.feed_id
                                                               ^
HINT:  There is an entry for table "f", but it cannot be referenced from this part of the query.

The inner join clause is misplaced and throws an error when running merge_feeds command. I'm running an self hosted instance with docker image postgres:12.
The SQL query that should work:
SELECT DISTINCT
	f.ID AS original_id,
	f2.ID AS duplicate_id,
	f.feed_address AS original_feed_address,
	f2.feed_address AS duplicate_feed_address,
	f.feed_title AS original_feed_title,
	f2.feed_title AS duplicate_feed_title,
	f.feed_link AS original_feed_link,
	f2.feed_link AS duplicate_feed_link,
	fd2.feed_tagline AS original_feed_tagline,
	fd.feed_tagline AS duplicate_feed_tagline
FROM
	feeds f
	INNER JOIN rss_feeds_feeddata fd ON fd.feed_id = f.ID,
	feeds f2
	INNER JOIN rss_feeds_feeddata fd2 ON fd2.feed_id = f2.ID
WHERE
	f2.ID > f.ID
	AND fd.feed_tagline = fd2.feed_tagline
	AND f.feed_link = f2.feed_link
	AND f.feed_title = f2.feed_title
ORDER BY
	original_id ASC;

Related code:
https://github.com/samuelclay/NewsBlur/blob/0a608abb87e0bbb4df61ad555e7aa242d2361e21/apps/rss_feeds/management/commands/merge_feeds.py#L14-L30

Sorry but this merge_feeds command is old. I removed it as it shouldn't be used anymore. If you want to merge feeds, there is now a Feed.merge_feeds() function. But feed merging is now handled automatically.

Part of commit c8439da97


header ...

Expected behavior
Right now, our thumbnail pic, display name, username, rank and reputation are left justified. Because it's left justified, it doesn't work with our current steemit cover picture. If you could simply center the info instead of left justify it, the Steemit cover picture will still work.
Actual behavior

How to reproduce

Browser:
Operating system:

Hey,
this doesn't seem to be an issue. Busy has to meet expectations of a lot of people and still remain consistent and be itself. We sadly can't change the way user header looks to match your profile background, because this affects a lot of people and might break things for them.
As a side note, profile background is not well suited for more fancy images. There is a lot of different clients that people use and things look different on each of them. Additionally users use different devices and it might not look as good as on FullHD screen. I think that it should be kept simple.


harmonize tool does not work

harmonize tool is failing to run on my end. This makes me think that we should probably have some testing or CI/CD for changes in our command tools (including walkthrough).
Complete error traceback
✗ harmonize data/garden/health/latest/karlinsky/death_registration.feather country countries.json
181 countries/regions to harmonize
  └ 177 automatically matched
  └ 4 ambiguous countries/regions

Beginning interactive harmonization...

[1/4] Bosnia
Traceback (most recent call last):
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/process.py", line 108, in extractWithoutOrder
    for key, choice in choices.items():
AttributeError: 'dict_keys' object has no attribute 'items'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/lucas/repos/etl/.venv/bin/harmonize", line 6, in <module>
    sys.exit(harmonize())
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/lucas/repos/etl/etl/harmonize.py", line 51, in harmonize
    mapping = interactive_harmonize(geo_column, mapping, institution=institution)
  File "/home/lucas/repos/etl/etl/harmonize.py", line 104, in interactive_harmonize
    suggestions = mapper.suggestions(region, institution=institution)
  File "/home/lucas/repos/etl/etl/harmonize.py", line 158, in suggestions
    results = process.extract(region.lower(), self.aliases.keys(), limit=5)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/process.py", line 168, in extract
    return heapq.nlargest(limit, sl, key=lambda i: i[1]) if limit is not None else \
  File "/home/lucas/.pyenv/versions/3.10.9/lib/python3.10/heapq.py", line 563, in nlargest
    result = [(key(elem), i, elem) for i, elem in zip(range(0, -n, -1), it)]
  File "/home/lucas/.pyenv/versions/3.10.9/lib/python3.10/heapq.py", line 563, in <listcomp>
    result = [(key(elem), i, elem) for i, elem in zip(range(0, -n, -1), it)]
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/process.py", line 117, in extractWithoutOrder
    score = scorer(processed_query, processed)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/fuzz.py", line 276, in WRatio
    base = ratio(p1, p2)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/utils.py", line 38, in decorator
    return func(*args, **kwargs)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/utils.py", line 29, in decorator
    return func(*args, **kwargs)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/utils.py", line 47, in decorator
    return func(*args, **kwargs)
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/fuzz.py", line 28, in ratio
    return utils.intr(100 * m.ratio())
  File "/home/lucas/repos/etl/.venv/lib/python3.10/site-packages/thefuzz/StringMatcher.py", line 64, in ratio
    self._ratio = ratio(self._str1, self._str2)
NameError: name 'ratio' is not defined

I am unsure what caused this issue, but I can no longer recreate it. Fresh installed the library (poetry install) and it worked perfectly.


Fix double unlock, and lock order race

Ensure that caller always locks mutex first. Previously callee could theoretically get it first, causing the later condition wait to hang forever.
Avoid double unlock which has undefined behaviour for pthread. Previously both an explicit call to unlock, and the destructor would unlock the mutex.

These issues where found while investigating #1328.
fix #1328

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 88.69%

Files with Coverage Reduction
New Missed Lines
%

lib/src/list.dart
2
85.93%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
3215

Relevant Lines:
3625

💛  - Coveralls


Automatic Builds for latest

The latest tag could benefit from automatic builds to be up-to-date

Please refine your request. There is an automatic check of the latest tag in place https://github.com/dante-ev/docker-texlive/blob/main/.github/workflows/check-build.yml. What do you miss there?

I see that there is a schedule to build every two weeks. ("At 03:01 on day-of-month 1 and 15.")
I wasn't specific on how often there should be a rebuild. So that schedule fulfills building regularly automatically, thanks.
What I meant at the time of writing (IIRC) with "automatic build" was that there is a possibility to trigger the image build automatically, on docker hub, in the event that the underlying base image was (re-)build, e.g. in case of security patches.
But also fine like this if you don't see the need to be faster up-to-date with your image for cases like security.

What I meant at the time of writing (IIRC) with "automatic build" was that there is a possibility to trigger the image build automatically, on docker hub, in the event that the underlying base image was (re-)build, e.g. in case of security patches.

The only use case I see for a quicker build is the integration of new LaTeX packages. A workaround for that is that a user manually adds them to their images.

But also fine like this if you don't see the need to be faster up-to-date with your image for cases like security.

I did not make a thorough security analysis. Maybe it's a research topic to investigate the attack vectors and possible gains on LaTeX users. I would assume they know about the risks of Cloud computing, docker etc and surely have separate hardware for these tasks than their critical tasks. Also not using a laptop with an LED. https://blog.fefe.de/?ts=9a7678ed
Interesting times.
I'll close the issue. If anyone wants to contribute to this with code, we can investigate further.


[WIP] OccupiedEntry.replace_

First pass at implementing the OccupiedEntry.replace_ in #4
This is directly taken from hashbrown.
I see the existing warning in src/map.rs that the hashbrown implementation will not work (https://github.com/jonhoo/griddle/blob/13509e46953c0b24f93a2dc40690b422102c1ce3/src/map.rs#L1857-L1865)
However, I do not see where the bucket gets moved. Aren't the replace_entry and replace_key replacing the values in place?
I additionally ran a test with a million random inserts / replaces comparing the results of griddle::HashMap vs hashbrown::HashMap and it passed.
Do you have any guidance on better understanding / triggering the warning condition?
Thanks

Hmm, that's interesting. It feels like there has to be an unstated requirement that the new key hashes to the same as the old one for this to work. Apparently these methods are still under discussion in https://github.com/rust-lang/rust/issues/44286, so I filed a comment there: https://github.com/rust-lang/rust/issues/44286#issuecomment-652999596. Since this just seems to work though, and doesn't require shifting, I'm inclined to accept it!
One thing though: there are probably tests for replace_ in map as well that we should move over.

My strategy for that was to place assert_eq!(1, 2) at the first line of each method in hashbrown, run the hashbrown tests with --no-fail-fast, and see what fails.
Only the test_set::test_replace unit test fails:
failures:
    set::test_set::test_replace

test result: FAILED. 62 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

And these doctests
failures:
    src/map.rs - map::OccupiedEntry::replace_entry (line 2567)
    src/set.rs - set::HashSet<T, S>::replace (line 845)

test result: FAILED. 96 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

Oh, how weird... I definitely feel like we should have more tests for this, but it sounds like we should contribute those tests to hashbrown first then.
I just realized why this is okay (https://github.com/rust-lang/rust/issues/44286#issuecomment-653034548), and so I think it's fine for us to include this too then! Thank you :)

Should that warning note about the replace_ implementations also be removed?

Ah, yes, good catch! I just pushed that change.


i had to said

thanks!!!
Where i can invite a coffe ?

Ditto. You should set up a tip jar or something


Shallow routing, when updating URL parameters, still get old params when the page re-renders

To Reproduce
Create a page.
Create an event that calls Router.push(newUrl, newUrl, { shallow: true });
The new newUrl is the same page with updated query params.
When the event is called, page re-renders, but props.url.query still has old query params.
Expected behavior
props.url.query should have new query params
System information

Version of Next.js: 6.0.2

Maybe query is still mutable https://github.com/zeit/next.js/pull/4352/files#diff-c39f41208533f29db9e4150b6efd2b68R101

@timneutkens can you think of any way (aside from the test) that I can check if that's the case?

By the way, the workaround I found is to avoid using Next router, and instead update the URL with window.history.  I wonder how many are using this approach this since the router doesn't seem to work correctly.

@vonwao Do you remember if you had a custom app.js? I have hunch.

I guess I'm also expiriencing this issue in<EMAIL_ADDRESS>Here's my scenario:

Navigate to /my-page?x=1&y2.
Inject these values into the page component inside getInitialProps():

  public static getInitialProps({ query }) {
  return {
    x: query.x,
    y: query.y,
  };
}

Interact with the page and modify x or y using Router.replace(newHref, newHref, { shallow: true });. The new values of x and y are kept in the state of the page component to avoid full re-render of the whole layout every time.

Navigate to some other page by clicking on a <Link />. Let's assume that we see /my-page?x=42&y=43 at the moment of the click and the page is reflecting this data correctly.

Press back in the browser and return to /my-page?x=42&y=43. At this moment, I am expecting a client-side call of getInitialProps with query equal to {x: 42, y: 43}. However, I observe {x: 1, y: 2} as in the first render. This happens despite that window.location.href contains ?x=42&y=43, which means that it gets unsynchronised with the value of Next's { query }.

Here's my workaround for the time being:
import { parse } from "url";

// ...

public static getInitialProps({ query }) {
  // https://github.com/zeit/next.js/issues/4432
  const fixedQuery =
    typeof window === "undefined"
      ? query
      : parse(window.location.href, true).query;
  return {
    x: fixedQuery.x,
    y fixedQuery.y,
  };
}

The trick is to rely on { query } only during SSR and fall back to a more robust window.location.href on the client.

Can someone create a minimal repository reproducing this?

I tried creating an MWE, but could not reproduce the bug in my previous comment. Moreover, getInitialProps in the original app started working correctly without introducing fixedQuery 😅
I'll show up again if I notice the problem again and realise what's happening. Sorry if it's a false alarm!

Hi @timneutkens
I am facing this issue. I have created a repo to reproduce it.
Here it is: https://github.com/7c78/next-4432
Step to reproduce:

access to http://localhost:3000
press Navigate link and check the F12 console

System information
"next": "^6.1.1",
"next-routes": "^1.4.2",
"mobx": "^5.1.0",

The original issue was fixed already.
@7c78 the issue in your app is that you're doing:
console.log(appContext.router.query) whereas you should be doing:
console.log(appContext.ctx.query), ctx is the page context. router is the router at that point in time, before it's updated.

@timneutkens oh thanks!


Chinese localization of Signature reader

I think its would be helpful for Chinese localization

combat site -> 战斗地点
relic site -> 遗迹地点
data site -> 数据地点
gas site -> 气云地点
wormhole -> 虫洞
ore site -> 矿石地点
ghost -> I cant find its translate. i think ghost sig is a type of data site. Maybe it's 幽灵站点

Thanks for providing this information. I added the Chinese translation to the signature parser


J5 logo looks terrible in Firefox

Firefox render pngs doing a bilinear interpolation and that's why it looks terrible. Not even with the image-rendering property is possible to improve this image without replacing one with a better quality/dpi

:(
This is in Firefox Developer Edition (39.0a2 (2015-04-21)):

This is in Firefox (37.0.2)

(Which actually looks better now that I updated)

Firefox dev edition supports picture, so it's loading the SVG, but it's missing the font. Instead of exporting the SVG with a font, convert the text to path.
(the thick J5 is the fallback PNG)

Ah man, I’m a dumbass; I never outlined the font in the SVG.

I'll convert them with idraw or whatever and see what's what.

Well, either I did it wrong, or it doesn't work. Someone else want to take a crack at it?

http://wil.to/j5-logo.svg should do it.

Show off


not working with ui-bootstrap datepicker

This directive is not working when the input has a datepicker directive of ui-bootstrap

https://angular-ui.github.io/bootstrap/#/datepicker already have some kind of mask functionality built-in. Making ui-mask no needed at all.

@sibeliusseraphini  did you find any solution for this? i don't want to use type='date' as it is not supported by all the browsers?

@settysreekanth
@settysreekanth: We've created a directive to handle this problem: https://gist.github.com/sibeliusseraphini/4d1275ea1f8c980dd645
I'll create a bower package when I have time
Let me know if you need any help

@sibeliusseraphini thanks for the reply. I believe, your solution doesn't apply masking till user completes the field input or till model gets assigned.. please correct me if I am wrong?
I am actually looking at the same behavior as it works with angular-ui-mask

@settysreekanth the changeInput() and changeDP() will apply the mask, however it only support one type of mask yet, you can improve it if you want

Thanks @sibeliusseraphini .. I will try customize and use it for my requirement.

@settysreekanth, I'm in a similar scenario. Did you manage to fix this? If so, could you show how you did it. Thanks!

@augustbend Not sure if its good to give link to different library in this forum however I ended up using different masking library https://github.com/RobinHerbots/jquery.inputmask and writing my own custom directive as below

angular.module('my-app').directive('date-mask', function(){
  return{
    restrict: 'A',
    require: 'ngModel',
    link: function(scope, elem, attr){
      ngModel.$formatters.push(formatter);
      ngModel.$parsers.push(parser);

      function formatter(fromModelValue){
        element.val(fromModelValue);
        return element.inputmask(maskpattern).val();
      }
      function parser(fromViewValue){
        return fromViewValue;
      }

    }
  }
})

@PowerKiKi: Could you please provide a Plunker of the masking functionality (preferably on the datepicker-popup)? Based on the documentation, I'm not seeing how this is accomplished. Thanks in advanced.

...To be more specific, I'm looking to apply the ui-mask on the input of the datepicker-popup so that a user can enter a date manually (via the keyboard) and the mask will not only indicate the basic "format" expected ( //____ ), but will ALSO restrict the input (numeric values).

I don't do much work on this project anymore, but @lukepfeiffer10 may be able to help you...

@engemasa The more recent versions of this library should work in conjunction with the datepicker directive with a small caveat. I believe if you use space as the placeholder character then you could run into some goofy situations.
Wanting the input to be restricted by the ui-mask is a different thing altogether and I'm fairly certain would not work for your use case. I would recommend letting the datepicker throw an invalid date error or use ng-pattern too.

Thank you @lukepfeiffer10 .

I would just like to post this to illustrate the issues I've been having:
https://plnkr.co/edit/0Vr5YRVREIT5EMu1m55z?p=preview
Basically seems to be a disconnect on the data the "picker" component references as opposed to the value itself.

@patlv23 Look at this edited plnkr: https://plnkr.co/edit/DSM7JNqnRMgDULmfoZEb?p=preview
I did some modifications to "Case 1" example:

Added slash to uib-datepicker-popup="dd/MM/yyyy" to match ui-mask="99/99/9999" mask format
Added the following attribute  model-view-value="true" that is an option from ui-mask directive

In this way I get the mask working, input value linked to model, and model value reflected to datepicker calendar.
(Let me know if this works for you too. I'm using last version of ui-bootstrap datepicker-popup)

@edriang weird thing, I tried out your plunk but it doesn't seem to have any difference to my original
BUT...
I tried out the changes you mentioned and it seems to be working. Many thanks!

"https://plnkr.co/edit/DSM7JNqnRMgDULmfoZEb?p=preview"
that link dos not work already
need some solution here

@feonit I made changes to my original plunk, it works there


Make CI red when build fails

Currently (Jun 2022) Hoff, whenever the nix-build step fails, the CI does not detect it and we are left with a green build :heavy_check_mark: even though the build was supposed to be red :x:.
Here is an example:

Green build:

All steps green:

Nice!

Actual result of the nix-build step:

Ohno!  :scream:

Here's the failing command and output section:
$ nix-build --no-out-link release.nix | cachix push channable-public
...
[11 of 12] Compiling WebInterface     ( src/WebInterface.hs, dist/build/WebInterface.p_o ) 00:43
[12 of 12] Compiling Server           ( src/Server.hs, dist/build/Server.p_o ) 00:45
dist/build/libHShoff-0.25.2-9YPwmF3FCRkEo14kDrjgdt-ghc8.10.4.a: hPutBuf: resource exhausted (No space left on device) 00:45
error: writing to file: No space left on device 00:45
Nothing to push. 00:45

Semaphore fails to detect this as although nix-build fails, cachix succeeds.  The error code of a pipe is (normally) the error code of the last command.  So we should try to break down the commands into two.  Something like this:
nix-build --no-out-link release.nix > something

cat something | cachix push channable-public

Issue present since 19 April 2022
The CI build was failing all along for two previous versions:

v0.25.1
v0.25.0

The issue has been here since 19 April 2022 after this merge with hash c4c2e38353046a9526e4ffd5390e6b38b554cbcf PR #105.
The CI build was still okay on v0.24.0

Semaphore fails to detect this as although nix-build fails, cachix succeeds. The error code of a pipe is (normally) the error code of the last command.

You can also set -o pipefail to prevent errors from being masked.


Website performance profiling

Here are some performance issues that we should resolve before the release of version 1. This issue will be updated as needed; please post any other performance problems in the comments.
CSS
Problem Navigating to different pages is not smooth.
Solution Load all CSS in the root layout. layout.js
Each page imports it's own CSS file, which is loaded on each page navigation. When a new stylesheet it loaded, it causes the entire page to re-render. This could cause the page to "flash" and animations to not feel smooth. I want to run some tests to confirm this.

CSS
I see that new CSS is loaded in the devtools network tab each time the page changes. We should look at the "paint" metrics to confirm an performance benefits in fixing this.

@natebass Hi! Happy New Year! ) I don't notice any issues with the animation. Could the problem be specific to a particular browser? The site takes a bit longer to load the first time, but after caching, everything runs smoothly.
I can see that when transitioning between pages, an additional CSS chunk is sometimes loaded. Not all styles, just an additional part. These are the styles that were not required for rendering the previous page. Isn't this the expected behavior?


Remove the link-check step from the build-and-deploy script

This step has been timing out sporadically lately, causing backups in the deployment queue. I'm not sure why that's happening -- we may just be outgrowing broken-link-checker -- but while I investigate, I'd like to remove it in order to keep from blocking deployments that would otherwise pass.
@stack72 I'd most like to hear from you on this. Do you believe it'd be risky to do this? Given the way our automated docs-generation processes work today, how plausible is it that we'd ship a docs update adding a link to a Pulumi archive or checksum that didn't exist on get.pulumi.com?

cc @zchase so you know this was done.


Possible discussions tab

Would it be possible for you to enable the discussions tab currently rolling out under settings/features.I feel this may be productive for the project as it grows.

Sorry it took so long to get to this, but I've added in the tab for anyone interested.


Gitpod: Missing Packages in GOROOT during Build

What did you do?
Description
I am encountering issues while trying to build the Prometheus project in Gitpod following CONTRIBUTING.md guidelines. The build process fails with errors indicating that certain packages are not found in the GOROOT. Below are the specific error messages:
../go/pkg/mod/go.opentelemetry.io/otel@v1.25.0/attribute/set.go:7:2: package cmp is not in GOROOT (/home/gitpod/go/src/cmp)
../go/pkg/mod/github.com/!kim!machine!gun/automemlimit@v0.6.0/memlimit/logger.go:5:2: package log/slog is not in GOROOT (/home/gitpod/go/src/log/slog)
../go/pkg/mod/github.com/hashicorp/nomad/api@v0.0.0-20240418183417-ea5f2f6748c7/consul.go:7:2: package maps is not in GOROOT (/home/gitpod/go/src/maps)
model/labels/labels_common.go:19:2: package slices is not in GOROOT (/home/gitpod/go/src/slices)

Environment Details

Gitpod Dockerfile:
https://github.com/prometheus/prometheus/blob/52f68a96a45b1c60eda9986656f332472babd047/.gitpod.Dockerfile#L1-L14

Gitpod YAML Configuration:
https://github.com/prometheus/prometheus/blob/52f68a96a45b1c60eda9986656f332472babd047/.gitpod.yml#L1-L20

Steps to Reproduce

Open the project in Gitpod.
Ensure the Gitpod Dockerfile and .gitpod.yml are configured as above (the same in master branch).
Attempt to build the project using the tasks defined in the Gitpod YAML configuration.

Actual Behavior
The build fails with errors indicating that certain packages (cmp, log/slog, maps, slices) are not found in GOROOT.
What did you expect to see?
The build should complete successfully without missing package errors.
What did you see instead? Under which circumstances?
Proposed Solution
I propose updating the Go version in the Gitpod docker file to a version that includes the missing packages, such as the latest Go version (Go 1.22.3). This should resolve the missing package errors during the build process.
Willing to Submit a PR
I am willing to submit a PR with the following changes:

Update the Dockerfile to use the latest go version 1.22.3.

After updating the custom go version in the Gitpod docker file to 1.22.3. it works as expected and there are no mission packages errors:
gitpod /workspace/prometheus (test) $  HISTFILE=/workspace/.gitpod/cmd-0 history -r; {
> make build
> } && {
> gp sync-done build
> ./prometheus --config.file=documentation/examples/prometheus.yml
>
> }
cd web/ui && npm install
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify: timing arborist:cto(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ idealTree: sill logfile do(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ idealTree: timing idealTre(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ idealTree: timing idealTre(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ idealTree: timing idealTre(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ idealTree: timing idealTre(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:fsevents: sill reify(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:fsevents: sill reify(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:fsevents: sill reify(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:fsevents: sill reify(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/lezer(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠋ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠋ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠇ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠋ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠋ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠋ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠸ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠴ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@prometheus-io/app: (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:@prometheus-io/app:

added 1605 packages, and audited 1609 packages in 33s

236 packages are looking for funding
  run `npm fund` for details

13 vulnerabilities (6 moderate, 7 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
cd web/ui && CI="" npm run build

><EMAIL_ADDRESS>build
> GENERATE_SOURCEMAP=false bash build_ui.sh --all

build lezer-promql

><EMAIL_ADDRESS>build
> bash ./build.sh

+ npx lezer-generator src/promql.grammar -o src/parser
Wrote src/parser.js and src/parser.terms.js
+ cat src/parser.terms.js
+ bash ./generate-types.sh
+ mkdir -p ./dist
+ indexFile=./dist/index.d.ts
+ [[ -f ./dist/index.d.ts ]]
+ cat
++ sed -E 's/ = [0-9]+/: number/' src/parser.terms.js
+ rollup -c

./src/parser.js → ./dist/index.cjs, ./dist/index.es.js...
created ./dist/index.cjs, ./dist/index.es.js in 59ms
build codemirror-promql

><EMAIL_ADDRESS>build
> npm run build:lib

><EMAIL_ADDRESS>build:lib
> bash ./build.sh

+ tsc --module esnext --target es2018 --outDir dist/esm
+ tsc --module commonjs --target es5 --outDir dist/cjs --downlevelIteration
build react-app

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
=============

WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.9.0

YOUR TYPESCRIPT VERSION: 4.9.5

Please only submit bug reports when using the officially supported version.

=============
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Compiled with warnings.

[eslint]
src/pages/graph/SeriesName.tsx
  Line 1:21:  'useContext' is defined but never used  @typescript-eslint/no-unused-vars

src/pages/status/Status.tsx
  Line 130:37:  Expected '!==' and instead saw '!='                                                                                eqeqeq
  Line 133:6:   React Hook useEffect has a missing dependency: 'setAnimateLogo'. Either include it or remove the dependency array. If 'setAnimateLogo' changes too often, find the parent component that defines it and wrap that definition in useCallback  react-hooks/exhaustive-deps

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

File sizes after gzip:

  489.22 kB  build/static/js/main.b9e603c4.js
  54.21 kB   build/static/css/main.e075b686.css

The project was built assuming it is hosted at ./.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.

ts=2024-05-19T05:36:54.267Z caller=tls_config.go:313 level=info component=web msg="Listening on" address=[::]:9090
ts=2024-05-19T05:36:54.267Z caller=tls_config.go:316 level=info component=web msg="TLS is disabled." http2=false address=[::]:9090
ts=2024-05-19T05:36:54.269Z caller=head.go:616 level=info component=tsdb msg="Replaying on-disk memory mappable chunks if any"
ts=2024-05-19T05:36:54.269Z caller=head.go:703 level=info component=tsdb msg="On-disk memory mappable chunks replay completed" duration=1.13µs
ts=2024-05-19T05:36:54.269Z caller=head.go:711 level=info component=tsdb msg="Replaying WAL, this may take a while"
ts=2024-05-19T05:36:54.270Z caller=head.go:783 level=info component=tsdb msg="WAL segment loaded" segment=0 maxSegment=0
ts=2024-05-19T05:36:54.270Z caller=head.go:820 level=info component=tsdb msg="WAL replay completed" checkpoint_replay_duration=27.44µs wal_replay_duration=1.5294ms wbl_replay_duration=190ns chunk_snapshot_load_duration=0s mmap_chunk_replay_duration=1.13µs total_replay_duration=1.59951ms
ts=2024-05-19T05:36:54.273Z caller=main.go:1151 level=info fs_type=XFS_SUPER_MAGIC
ts=2024-05-19T05:36:54.273Z caller=main.go:1154 level=info msg="TSDB started"
ts=2024-05-19T05:36:54.273Z caller=main.go:1336 level=info msg="Loading configuration file" filename=documentation/examples/prometheus.yml
ts=2024-05-19T05:36:54.274Z caller=main.go:1373 level=info msg="Completed loading of configuration file" filename=documentation/examples/prometheus.yml totalDuration=619.44µs db_storage=950ns remote_storage=1.52µs web_handler=290ns query_engine=810ns scrape=345.4µs scrape_sd=29.06µs notify=16.76µs notify_sd=6.95µs rules=1.18µs tracing=4.93µs
ts=2024-05-19T05:36:54.274Z caller=main.go:1115 level=info msg="Server is ready to receive web requests."
ts=2024-05-19T05:36:54.274Z caller=manager.go:163 level=info component="rule manager" msg="Starting rule manager..."

Additional Testing
After updating the Go version to 1.22.3, I ran the test cases to ensure there were no regressions. All tests passed except for one:

TestAsyncRuleEvaluation/asynchronous_evaluation_of_all_independent_rules,_insufficient_concurrency

This failure is likely due to the limited computational resources allocated in the Gitpod workspace, rather than the Go version update.
gitpod /workspace/prometheus (test) $ make test
>> cleaning generated parser
>> running goyacc to generate the .go file.

conflicts: 19 shift/reduce
>> checking generated parser
>> running all tests
go test -race  ./...
go: downloading github.com/stretchr/objx v0.5.2
go: downloading github.com/evanphx/json-patch v5.6.0+incompatible
?       github.com/prometheus/prometheus/discovery/aws  [no test files]
?       github.com/prometheus/prometheus/discovery/gce  [no test files]
?       github.com/prometheus/prometheus/discovery/install      [no test files]
ok      github.com/prometheus/prometheus/cmd/prometheus 109.313s
ok      github.com/prometheus/prometheus/cmd/promtool   27.829s
ok      github.com/prometheus/prometheus/config 1.195s
ok      github.com/prometheus/prometheus/discovery      5.626s
ok      github.com/prometheus/prometheus/discovery/azure        1.018s
ok      github.com/prometheus/prometheus/discovery/consul       4.031s
ok      github.com/prometheus/prometheus/discovery/digitalocean 1.020s
ok      github.com/prometheus/prometheus/discovery/dns  1.019s
ok      github.com/prometheus/prometheus/discovery/eureka       1.030s
ok      github.com/prometheus/prometheus/discovery/file 3.336s
ok      github.com/prometheus/prometheus/discovery/hetzner      1.027s
ok      github.com/prometheus/prometheus/discovery/http 1.040s
ok      github.com/prometheus/prometheus/discovery/ionos        1.024s
ok      github.com/prometheus/prometheus/discovery/kubernetes   34.654s
ok      github.com/prometheus/prometheus/discovery/legacymanager        4.225s
ok      github.com/prometheus/prometheus/discovery/linode       1.030s
ok      github.com/prometheus/prometheus/discovery/marathon     1.021s
ok      github.com/prometheus/prometheus/discovery/moby 1.114s
ok      github.com/prometheus/prometheus/discovery/nomad        1.018s
ok      github.com/prometheus/prometheus/discovery/openstack    1.045s
ok      github.com/prometheus/prometheus/discovery/ovhcloud     1.028s
ok      github.com/prometheus/prometheus/discovery/puppetdb     1.035s
ok      github.com/prometheus/prometheus/discovery/refresh      1.018s
ok      github.com/prometheus/prometheus/discovery/scaleway     1.028s
ok      github.com/prometheus/prometheus/discovery/targetgroup  1.013s
ok      github.com/prometheus/prometheus/discovery/triton       1.081s
ok      github.com/prometheus/prometheus/discovery/uyuni        1.022s
ok      github.com/prometheus/prometheus/discovery/vultr        1.019s
ok      github.com/prometheus/prometheus/discovery/xds  3.093s
ok      github.com/prometheus/prometheus/discovery/zookeeper    1.032s
?       github.com/prometheus/prometheus/documentation/examples/custom-sd/adapter-usage [no test files]
?       github.com/prometheus/prometheus/model/exemplar [no test files]
ok      github.com/prometheus/prometheus/documentation/examples/custom-sd/adapter       1.015s
?       github.com/prometheus/prometheus/model/metadata [no test files]
ok      github.com/prometheus/prometheus/model/histogram        1.125s
?       github.com/prometheus/prometheus/model/timestamp        [no test files]
?       github.com/prometheus/prometheus/model/value    [no test files]
?       github.com/prometheus/prometheus/plugins        [no test files]
?       github.com/prometheus/prometheus/prompb [no test files]
?       github.com/prometheus/prometheus/prompb/io/prometheus/client    [no test files]
ok      github.com/prometheus/prometheus/model/labels   4.303s
ok      github.com/prometheus/prometheus/model/relabel  1.097s
ok      github.com/prometheus/prometheus/model/rulefmt  1.112s
ok      github.com/prometheus/prometheus/model/textparse        1.071s
ok      github.com/prometheus/prometheus/notifier       3.459s
?       github.com/prometheus/prometheus/promql/parser/posrange [no test files]
?       github.com/prometheus/prometheus/storage/remote/otlptranslator/prometheus       [no test files]
?       github.com/prometheus/prometheus/tsdb/encoding  [no test files]
?       github.com/prometheus/prometheus/tsdb/errors    [no test files]
?       github.com/prometheus/prometheus/util/almost    [no test files]
?       github.com/prometheus/prometheus/util/annotations       [no test files]
?       github.com/prometheus/prometheus/util/documentcli       [no test files]
?       github.com/prometheus/prometheus/util/gate      [no test files]
?       github.com/prometheus/prometheus/util/jsonutil  [no test files]
?       github.com/prometheus/prometheus/util/osutil    [no test files]
?       github.com/prometheus/prometheus/util/runtime   [no test files]
?       github.com/prometheus/prometheus/util/runutil   [no test files]
?       github.com/prometheus/prometheus/util/teststorage       [no test files]
?       github.com/prometheus/prometheus/util/testutil  [no test files]
?       github.com/prometheus/prometheus/util/treecache [no test files]
?       github.com/prometheus/prometheus/web/ui [no test files]
ok      github.com/prometheus/prometheus/promql 190.077s
ok      github.com/prometheus/prometheus/promql/parser  10.118s
ok      github.com/prometheus/prometheus/promql/promqltest      3.208s
--- FAIL: TestAsyncRuleEvaluation (0.51s)
    --- FAIL: TestAsyncRuleEvaluation/asynchronous_evaluation_of_all_independent_rules,_insufficient_concurrency (0.18s)
        manager_test.go:1963:
                Error Trace:    /workspace/prometheus/rules/manager_test.go:1963
                Error:          "0.115001058" is not less than "0.09"
                Test:           TestAsyncRuleEvaluation/asynchronous_evaluation_of_all_independent_rules,_insufficient_concurrency
FAIL
FAIL    github.com/prometheus/prometheus/rules  44.393s
ok      github.com/prometheus/prometheus/scrape 33.313s
ok      github.com/prometheus/prometheus/storage        1.377s
ok      github.com/prometheus/prometheus/storage/remote 63.304s
ok      github.com/prometheus/prometheus/storage/remote/azuread 13.043s
ok      github.com/prometheus/prometheus/storage/remote/otlptranslator/prometheusremotewrite    1.015s [no tests to run]
ok      github.com/prometheus/prometheus/template       1.025s
ok      github.com/prometheus/prometheus/tracing        1.098s
ok      github.com/prometheus/prometheus/tsdb   455.795s
ok      github.com/prometheus/prometheus/tsdb/agent     89.362s
ok      github.com/prometheus/prometheus/tsdb/chunkenc  1.093s
ok      github.com/prometheus/prometheus/tsdb/chunks    62.484s
ok      github.com/prometheus/prometheus/tsdb/fileutil  1.080s
ok      github.com/prometheus/prometheus/tsdb/goversion 1.070s
ok      github.com/prometheus/prometheus/tsdb/index     80.498s
ok      github.com/prometheus/prometheus/tsdb/record    1.030s
ok      github.com/prometheus/prometheus/tsdb/tombstones        1.028s
ok      github.com/prometheus/prometheus/tsdb/tsdbutil  1.027s
ok      github.com/prometheus/prometheus/tsdb/wlog      51.784s
ok      github.com/prometheus/prometheus/util/fmtutil   1.096s
ok      github.com/prometheus/prometheus/util/httputil  1.184s
ok      github.com/prometheus/prometheus/util/logging   1.219s
ok      github.com/prometheus/prometheus/util/pool      1.017s
ok      github.com/prometheus/prometheus/util/stats     1.180s
ok      github.com/prometheus/prometheus/util/strutil   1.087s
ok      github.com/prometheus/prometheus/util/zeropool  5.017s
ok      github.com/prometheus/prometheus/web    17.181s
ok      github.com/prometheus/prometheus/web/api/v1     2.206s
FAIL
make: *** [Makefile.common:153: common-test] Error 1

Please let me know if this solution is acceptable or if there are any additional considerations.
Thank you!
System information
No response
Prometheus version
No response
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

Hey @mohamedawnallah, updating the go version in Gitpod Dockerfile sounds like a good solution :)
Even better if somehow we could configure the Dockerfile go version based on the version specified in our go.mod, that way the Gitpod workspace would always be up to date!

Thanks so much, @ArthurSens, for the suggestion! I really like it; it's a durable solution. I've just submitted a PR that automatically fetches the Go version from the go.mod file and the goyacc parser version from the Makefile. I'd love to receive any feedback! 🙏