[Bug] 802.11x broken wpa_supplicant is missing.

Hello
802.11X is a username password authentication mechanism commonly used on WPA entreprise BUT many forget that wired connection can have this settings enabled in too.
It's my case (my switch require this log to allow wired device to connect (and prevent someone to simply plug his computer to my network)).
The problem is that since it's the same mechanism as WPA it use wpa_supplicant package I thing unbreack 802.11X for wired connection is in the scope of this project
to fix it you need to add wpa_supplicant in image.
I've opened this here since in found this in secure blue, here the issue from there who redirect me here : https://github.com/secureblue/secureblue/issues/267

I appreciate the report, but what image and version are you running?
wpa_supplicant should be installed since merging #140 on April 9, 2024.
Here's some example from a test system showing it's present:
root@orcrist:~# rpm-ostree status -b
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: inactive
BootedDeployment:
● ostree-image-signed:docker://ghcr.io/ublue-os/ucore-hci:stable-zfs
                   Digest: sha256:1f1ec422401a9b2645863f7d4c924d6e0d320a46728b6d372a47cadebbcc0ae6
                  Version: 39.20240407.3.0 (2024-04-26T20:16:39Z)
root@orcrist:~# rpm -q wpa_supplicant
wpa_supplicant-2.10-9.fc39.x86_64
root@orcrist:~# which wpa_supplicant
/usr/sbin/wpa_supplicant

I use ucore-minimal:stable, and also secure blue that is plugged on it suffer the same problem (and they do not remove it (I checked their config)).

secure blue do not remove it and there is the answer (I don't have (again) rebase I miss time to do it today but the problem is the same on minimal, I guess it was not included on minimal since many people forget that wpa_supplicant is not used only with wifi but also 802.11x
birdinfire@localhost:~$ sudo rpm-ostree status -q
[sudo] password for birdinfire:
State: idle
AutomaticUpdates: apply; rpm-ostreed-automatic.timer: no runs since boot
Deployments:

ostree-image-signed:docker://ghcr.io/secureblue/server-main-userns-hardened:latest
Digest: sha256:2266b162f42e24e784d6c16d018ec255177dd8bb3c48a9b82b2db81cc3a5fa1e
Version: 39.20240407.3.0 (2024-04-28T18:38:28Z)
ostree-image-signed:docker://ghcr.io/secureblue/server-main-userns-hardened:latest
Digest: sha256:2266b162f42e24e784d6c16d018ec255177dd8bb3c48a9b82b2db81cc3a5fa1e
Version: 39.20240407.3.0 (2024-04-28T18:38:28Z)
LayeredPackages: wpa_supplicant

birdinfire@localhost:~$ rpm -q wpa_supplicant
package wpa_supplicant is not installed
Once I go on the same image with supplicant layered it work

@bsherman  I checked the merge and it's integrated in the ucore and not the ucore minimal in this file : https://github.com/ublue-os/ucore/blob/main/ucore/packages.json with : NetworkManager-wifi into ucore, ucore minimal don't have wpa_supplicant so leading to a breakage of 802.11x

@BirdInFire first, I want to clarify. I don't see this as a bug, it's a package request.
A bug would exist if a feature (either in Fedora CoreOS or a feature exclusively developed for uCore) does not work as expected.
This is not a bug. This is a package which was intentionally not included in Fedora CoreOS or the ucore-minimal image.
As you noted, the package is in ucore and ucore-hci.
So there's a couple workarounds here:

as you are using a custom image, the custom image can add wpa_supplicant
upgrade to ucore
continue layering.

Regarding the package request. I'll consider it, but please retitle the issue as a package request.

@BirdInFire first, I want to clarify. I don't see this as a bug, it's a package request.
A bug would exist if a feature (either in Fedora CoreOS or a feature exclusively developed for uCore) does not work as expected.
This is not a bug. This is a package which was intentionally not included in Fedora CoreOS or the ucore-minimal image.
As you noted, the package is in ucore and ucore-hci.
So there's a couple workarounds here:

as you are using a custom image, the custom image can add wpa_supplicant
upgrade to ucore
continue layering.

Regarding the package request. I'll consider it, but please retitle the issue as a package request.

ok I thanked it was a package forget (since as I said it's very very often forgotten that WPA supplicant is also used for 802.11X.
If it was intended you could simply say it and not be this passive/agressive in the answer.
I close bye.

If it was intended you could simply say it and not be this passive/agressive in the answer. I close bye.

Apologies that my response seemed rude to you. I realize that I was editing the message and accidently left both "this is not a bug. this is a package request" statements, but I only meant to have one.
Regardless, I did offer you workarounds and I told you I'd consider adding the package.
For the moment, I will leave the package list as is.


Support for manually adding labels to models

Is your enhancement related to a problem? Please describe.

Embedding models like gte-Qwen2 cannot be recognized as an embedding model by GPUStack. Because there is no "Embedding Only" tag, this model cannot be tested in the playground.

Describe the solution you'd like

Support for manually adding labels to models.

When deploying models on a slave worker from local path, labels are also not supported


feat: remove testing runtime

Fixes: #576

remove testing runtime
remove test-upgrade-runtime script and gh job

remove test-upgrade-runtime script and gh job

didn't work anymore? how do we currently test them?

The script requires the testing runtime, and it also uses polkadot-launch. We will need to test it manually or find another way how to test it.

Any suggestions?

Yeah we should probably use chopsticks for this? cc @mrq1911


[FEATURE] Support ORDER BY RANDOM()

Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

implemented


memaryParse

memary currently parses the agents' responses, which are stored in a .txt file, before inserting them into our knowledge graphs.
As we look to support agentic systems running real-world tasks, our memory unit needs to allow the system's maintainer to pre-process the knowledge graph with relevant data. For example, an e-commerce company wants to upload their users' information so that the agent can initially respond with context.
Companies may present this data in various file formats, such as .csv, .pdf, .txt, .pptx, or others. That is why memary must support many configurable parsers under a parent parser - memaryParse. For example, a company running an agent with data in .csv and .docx files can configure a parent retriever that supports both formats to pre-process the data into the knowledge graph before running their agents using memary.
We expect memaryParse to expand over time. Initially, we hope to support the following formats:

.txt (already configured)
table extraction
JSON
Images (.jpg, .jpeg, .png, .gif)
Document and presentations (.pdf, .doc / .docx, .rtf, .pages, .pptx, .xml, .key)
Web (htm, html)
Spreadsheets (.xlsx, .xls, .csv, .numbers)

memaryParse should also support the following result types: TXT, MD, and JSON (we will look to add others in the future).
Resource for inspiration: https://github.com/run-llama/llama_parse/blob/main/llama_parse/utils.py

for PDFs, please just let me put my llamaindex API key to use llamaparse. they have worked so hard on this, i would strongly advise not to re-invent it.
for other datatypes, here are some resources. neo4j has done a lot of work on this.

https://neo4j.com/developer-blog/construct-knowledge-graphs-unstructured-text/
https://www.youtube.com/live/NbyxWAC2TLc
https://github.com/neo4j-labs/llm-graph-builder


Support for python3.9 and 3.10 added

#1

Currently only supporting Python 3.11 because that's all I've tested on, but supporting 3.9+ should be easy enough.
To do:

[x]  Set up testing matrix (tox or GitHub CI)
[x]  Fix any potential issues with Python 3.9 and 3.10

Thanks for the PR @Chandrahas-B! Looks great, merging :)


Remove wget from build and run

Likely not needed in build and causes problems on Windows in
run (where it is also not needed)

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

closes #3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Fake HTTP requests on preview should report as HTTPS on HTTPS sites

Ref https://groups.google.com/d/msg/wagtail/hTFw1jKCHm4/E99gQ3wqWhwJ - if the site developer has installed any middleware that blocks or redirects non-HTTPS requests, previewing will fail with "Couldn't create request mock object - request middleware returned a response". This is because the fake request used to generate the preview is always created as a plain HTTP request, and gets intercepted by the middleware.
This could be fixed by making the fake request behave as HTTPS where appropriate: we would create a subclass of WSGIRequest that overrides the _get_scheme method, allowing us to pass in the correct scheme (as reported by self.full_url) when we construct the request object.

Strictly speaking this isn't fixed - we're still reporting requests as HTTP when the real request would be HTTPS. The fix in #946 ensures that this discrepancy doesn't lead to a middleware-induced failure, but it could conceivably lead to other differences in behaviour if any other components of the site check the request.is_secure flag. However, at this point this is just a theoretical concern, so I'm happy to leave this ticket closed.

Argh, you are correct. Completely misread the last paragraph.
Judging from the comments on Groups, the reported issue was fixed.
As you say, if we get reports about issues with HTTP/HTTPS, this can be revisited.


[Improvement] Accelerate compileDistribution task for Gravitino

What would you like to be improved?
If we run
./gradlew compileDistribution -x test -x web

It will take as long as 10 minutes. We need to speed up the construction process.
How should we improve?
No response

@yuqi1129
BUILD SUCCESSFUL in 1m 18s
125 actionable tasks: 83 executed, 42 up-to-date
It takes about a minute for me, is it based on the time when I just hit that command inside the terminal?

@yuqi1129
BUILD SUCCESSFUL in 1m 18s 125 actionable tasks: 83 executed, 42 up-to-date
It takes about a minute for me, is it based on the time when I just hit that command inside the terminal?

Perhaps the network is causing the compiling process to take so long. I will check to see if that's the case.

@yuqi1129
BUILD SUCCESSFUL in 1m 18s 125 actionable tasks: 83 executed, 42 up-to-date
It takes about a minute for me, is it based on the time when I just hit that command inside the terminal?

Perhaps the network is causing the compiling process to take so long. I will check to see if that's the case.

My internet is using a 100mb plan based on Korea, but I would appreciate it if you could check it.


Samples - 200.3.0 Release checklist, v.next merged with main

Description
Merged v.next into main in the branch.
No build errors, done a sanity test, no issues noticed.
No diff between v.next and v.next_merged_with_main branches.

Type of change

[ ] Bug fix
[ ] New sample implementation
[ ] Sample viewer enhancement
[ ] Other enhancement

Platforms tested on:

[ ] Windows
[ ] Android
[ ] Linux
[x] macOS
[ ] iOS

Checklist

[ ] Runs and compiles on all active platforms as a standalone sample
[x] Runs and compiles in the sample viewer(s)
[ ] Branch is up to date with the latest main/v.next
[ ] All merge conflicts have been resolved
[ ] Self-review of changes
[ ] There are no warnings related to changes
[ ] No unrelated changes have been made to any other code or project files
[ ] Code is commented with correct formatting (CTRL+i)
[ ] All variable and method names are camel case
[ ] There is no leftover commented code
[ ] Screenshots are correct size and display in description tab (500px by 500px, platform agnostic)
[ ] If adding a new sample, it is added to the sample viewer
[ ] Cherry-picked to Main branch (if applicable)

This branch is clean and flush with v.next:
https://github.com/Esri/arcgis-maps-sdk-samples-qt/compare/v.next...v.next_merged_with_main


Problem with scanning by HOSTS

Hello! Everything is ok with scanning by an IPs...by with host name it doesn't work.
Tell me, if I do something wrong:
var options = {
target:'google.com',
port:'21-23',
status:'TROU', // Timeout, Refused, Open, Unreachable
banner:true,
};

hi,
i'll try to take a look today

Thank you very much!
пн, 1 мар. 2021 г. в 18:02, eviltik<EMAIL_ADDRESS>
hi,
i'll try to take a look today
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eviltik/evilscan/issues/68#issuecomment-787896077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVI336GPYQW3YAOULPMPK3TBN65HANCNFSM4YMHEWAA
.

It's work for me. But no result because no port 21/22/23 opened.
You can handle "done" event, see examples.


[BUG] Not booting after installing from ISO

Describe the bug
After installing Harvester v0.3-rc1 on the first hard drive (of 2 installed), and enabling UEFI, the hard drive does not show up as a boot option in the boot menu. I did manage to fix it by copying the EFI partition and parts of the GRUB partition from an UEFI-enabled Ubuntu installation (see below).
To Reproduce
Steps to reproduce the behavior:

Flash the ISO on a USB drive
Boot from it and install Harvester v0.3-rc1
Restart the machine and open the boot menu

Expected behavior
The Harvester installation being detected and the boot option available.
Environment

Harvester ISO version: v0.3-rc1
Underlying Infrastructure: Intel Xeon E3-1275V6 (4 cores, 8 threads, GPU), 2x SSD SATA 480 GB Datacenter, 64 GB DDR4 ECC, Intel NIC 1 Gbit

Additional context
I managed to get it to work. I did:

Resize the EFI partition from 47M to 300M, because I read that it should be >=200M (not sure whether that was necessary though)
Copy entire directory structure from an UEFI-enabled Ubuntu 20.04 EFI partition to Harvester's EFI partition
On Harvester's GRUB partition, rename the directory grub2 to grub because that's referenced now in the EFI partition
Overwrite Harvester's entire directory in grub/x86_64-efi (on the GRUB partition) by what's in that directory on Ubuntu's GRUB partition

Please let me know what other information would be useful for you.

Were you able to find a resolution to this? I have the exact same issue. Can't boot the installer in BIOS mode. I can seeminly install in UEFI mode, but once rebooted, the drive is not detected as bootable. Using Harvester-v1.0.0-amd64 iso and burned via Rufus on Windows 10.
Server is a Dell R710 set to UEFI boot mode, as BIOS mode just gets the same Grub prompt.

@bk201
Hello, I should have updated this sooner.
I resolved the problem by installing a UEFI ROM on the HBA the boot disk was attached to.
As a note, it seems like when Harvester moved to GRUB2, they dropped support for BIOS-based installs.

@Just-Insane Thanks for the reply! But in fact, I tested installing Harvester on both legacy and UEFI VMs. So it might be some reason you can't boot from an HBA-attached disk.

Were you able to find a resolution to this?

I did not try it again with a newer Harvester version, unfortunately.

I am facing similar situation, I tried USB installation, UEFI mode, installation was successful but once rebooted, it did not booted from the hard drive and even there were no option for Harvester in the bios menu.
I use official document as reference https://docs.harvesterhci.io/v1.0/install/usb-install/  but failed multiple times.

I have a similar issue when trying to install harvester from a USB stick, created from the iso.
Install appears to work, but the resulting install drive does not appear to be bootable.
Grub does not appear when the installation drive is selected to boot.

@mannp What hardware are you using? And are you booting with UEFI or legacy BIOS?
There is a related issue #2023 that is tracking the support for installing and booting the installed Harvester using legacy BIOS motherboards. The information we need to move forward on this and #2023 is the hardware you are using, the boot mode (UEFI or BIOS), and the partitioning scheme you use during install (GPT or MBR)

@mannp I am working on the legacy BIOS booting mode. About the UEFI installation, did you set up the partitioning scheme using MBR or GPT?

@mannp I am working on the legacy BIOS booting mode. About the UEFI installation, did you set up the partitioning scheme using MBR or GPT?

@tlehman apologies, I forgot to add, that I could not remember.
I did install harvester on an empty drive, but didn't check what partition type it was prior to installing.

I could also not boot directly into the partition (dell r710) of usb drive.
What I did was follow https://unix.stackexchange.com/questions/329926/grub-starts-in-command-line-after-reboot
ls should give you something like (hd3,msdos1).
That should be the right one.
So in the end it should be something like (hd3,msdos)/boot/grub2

I have the same problem here - install from USB/ISO and after the successful install and reboot, the machine can't find the boot disk anymore.
Setup:

Dell Precision Workstation T7910
2x E5-2699v4 / 1Tb RAM
Boot set as UEFI with support to legacy ROM
OS disk is on a SATA SSD connected to the motherboard SATA port (not going to any HBA or controller)
Data disks thru onboard HBA in IT mode

After the install I can see on the BIOS that elemental-shim was added to the UEFI boot entries but if I pick it, it will not boot and the machine reset.
I confirmed that the install was made by picking the USB boot option on UEFI, and after the install we are trying to boot thru UEFI.
Any thoughts on what can it be? I'm using latest harvester 1.3.0.
Thanks!

Hi @galvesribeiro can you confirm if the installation is done in UEFI or legacy mode? One way is to boot any linux or Harvester installer and run lablk to list partition tables.

galvesribeiro After about two weeks of troubleshooting, I figured out a fix that might help you out.
I also have a Dell T7910 (not as beefy, only 128GB of RAM).
For some reason, every time I would try to install the Harvester v1.3.1 ISO, it would install but then when I would go to boot, it wouldn't find the EFI that Harvester builds. To fix this, here is what I did:

Build a bootable live environment (I put Ventoy w/ OpenSUSE Tumbleweed Live GNOME onto it)
Set one-time boot priority to the USB (F12)
Run Tumbleweed and pull up the terminal
3.a) Identify where the EFI is installed by typing " sudo fdisk -l " -mine happened to be /dev/sdc1, but your could be a or x.
3.b) Identify the right EFI, this is found by: " ls /mnt/EFI/boot ," you should see a couple of EFIs. The one I used was bootx64.efi
Use the Tumbleweed efibootmgr service to set your disk to boot from that by typing the following:
sudo efibootmgr --create --disk /dev/sdX --part Y --label "Harvester" --loader "\EFI\boot\bootx64.efi"

-Replace /dev/sdX with your disk identifier.
-Replace Y with the partition number of your EFI partition.
-Adjust the loader path if necessary.

Once I rebooted, I checked the BIOS (F2) to pull it up. This time, my Dell UEFI showed a checked 'Harvester' as number 1 boot priority.

Let it boot- this system takes some time to load. When you get to the Grub 2.0.6 screen, DON'T TOUCH ANYTHING...wait a few minutes for all the services to boot and just let it go through its service setup. Once done, you'll get to harvester.

This crap took me two weeks and a lot of ChatGPT queries, but I got it fixed. I hope this helps someone else...

Hi @galvesribeiro can you confirm if the installation is done in UEFI or legacy mode? One way is to boot any linux or Harvester installer and run lablk to list partition tables.

@bk201 Sorry, I missed your reply. I was installing on UEFI mode for sure. The only reason I had the Legacy ROM support was because of a very old GPU. I added a Geforce RTX3080 which has the UEFI firmware and disabled the Legacy ROM, so everything was thru UEFI and I had the same issue.

galvesribeiro After about two weeks of troubleshooting, I figured out a fix that might help you out.

@aelkins02 holy crap! Thanks! That may possibly be the problem. However, I gave up on harvesters mostly because of the Storage. The performance isn't good with Longhorn after I made test with it on another cluster. There was no support to RDMA either. I've also got under the impression that both Harvester and Longhorn were not very actively maintained, given that this issue is 3 years old and there was no resolution up to now. The Longhorn release that theoretically would improve the performance, also wouldn't come up ever, so Harvester still stuck on the old/slow storage.
Anyway, thank you both for the replies, but I've decided to move on to another solution.


Wrong entry in Plain English words list

Can we remove the first example under Like this.. Not this - It's not a plain English issue.
State and Territory and Local Governments	state and territory, and local governments

This is moved now http://content-guide.apps.staging.digital.gov.au/terms-phrases/index.html#plain-english-terms


Use GoogleDefaultChannelBuilder

Resolves https://github.com/googleapis/gax-java/issues/626.

Still need to test with google-cloud-java.

Codecov Report

Merging #627 into master will increase coverage by 0.34%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master     #627      +/-   ##
============================================
+ Coverage     74.94%   75.29%   +0.34%
  Complexity      935      935
============================================
  Files           177      177
  Lines          4099     4080      -19
  Branches        328      328
============================================
  Hits           3072     3072
+ Misses          874      855      -19
  Partials        153      153

Impacted Files
Coverage Δ
Complexity Δ

...api/gax/grpc/InstantiatingGrpcChannelProvider.java
74.45% <50%> (+9.06%)
26 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

PTAL

See https://buganizer.corp.google.com/issues/120606286#comment16

Swapping everyone over to GoogleDefaultChannelBuilder would break users in ClassLoading environments because it will leak a thread and thus the class loader. You should really wait for https://github.com/grpc/grpc-java/issues/4755 to be fixed and released.


[Feature]: Block streaming endpoint

To whom is this feature for?
App developer
Why is is this feature needed?
For block indexer/explorer developers It might be useful to be able to obtain new blocks not by using polling, but connecting to a streaming endpoint and receive every new block once it is ready. This also can speed up consumer synchronization from the first block to current, if the blockchain has been running for a long time.
How is this feature used?
Developer requests blocks starting from the given number, this establishes streaming connection using native gRPC streaming support.
Anything else?
No response

I guess there are a couple of options here:

The endpoint takes the block_num as input and streams all blocks starting at that number until the current block.
The connection stays open and the user streams blocks as they are created.
(we could also combine the two).

I'm not sure about the complexities (and implications) of the second option - so, don't have a good sense which option we should go with.
Also, regardless of the option, we probably should think about some kind of DoS prevention mechanism as this endpoint can result in returning lots of data. This would probably be related to #52.


Telescope picker opts causing long load times

I have been trying to reduce load times. It seems like the telescope picker settings significantly increases load times from around 600ms to over 2000ms. This is my configuration using Lazy:
return {
  'gbprod/yanky.nvim',
  dependencies = {
    { 'kkharji/sqlite.lua' }
  },
  -- event = "VeryLazy",
  opts = function()
    local utils = require'yanky.utils'
    local map = require'yanky.telescope.mapping'

    return {
      history_length = 100,
      sync_with_numbered_registers = true,
      storage = 'sqlite',
      cancel_event = 'update',
      ignore_registers = { '_' },
      update_register_on_cycle = false,
      system_clipboard = {
        sync_with_ring = true,
      },
      picker = {
        telescope = {
          mappings = {
            default = map.put('p'),
            i = {
              ['<c-j>'] = map.put('p'),
              ['<c-k>'] = map.put('P'),
              ['<c-h>'] = map.put('gp'),
              ['<c-l>'] = map.put('gP'),
              ['<c-x>'] = map.delete(),
              ['<c-r>'] = map.set_register(utils.get_default_register()),
            },
            n = {
              p = map.put('p'),
              P = map.put('P'),
              d = map.delete(),
              r = map.set_register(utils.get_default_register())
            },
          }
        }
      }
    }
  end,
  keys = {
    { '<leader>p', function() require'telescope'.extensions.yank_history.yank_history({ }) end,
      mode = { 'n', 'x' }, desc = 'Open Yank History' },
    { 'y',     '<Plug>(YankyYank)',       mode = { 'n', 'x' }, desc = 'Yank text' },
    { 'p',     '<Plug>(YankyPutAfter)',   mode = { 'n', 'x' }, desc = 'Put yanked text after cursor' },
    { 'P',     '<Plug>(YankyPutBefore)',  mode = { 'n', 'x' }, desc = 'Put yanked text before cursor' },
    { 'gp',    '<Plug>(YankyGPutAfter)',  mode = { 'n', 'x' }, desc = 'Put yanked text after selection' },
    { 'gP',    '<Plug>(YankyGPutBefore)', mode = { 'n', 'x' }, desc = 'Put yanked text before selection' },
    { '<c-p>', '<Plug>(YankyPreviousEntry)', desc = 'Select previous entry through yank history' },
    { '<c-n>', '<Plug>(YankyNextEntry)',     desc = 'Select next entry through yank history' },
    { ']p',    '<Plug>(YankyPutIndentAfterLinewise)',    desc = 'Put indented after cursor (linewise)' },
    { '[p',    '<Plug>(YankyPutIndentBeforeLinewise)',   desc = 'Put indented before cursor (linewise)' },
    { ']P',    '<Plug>(YankyPutIndentAfterLinewise)',    desc = 'Put indented after cursor (linewise)' },
    { '[P',    '<Plug>(YankyPutIndentBeforeLinewise)',   desc = 'Put indented before cursor (linewise)' },
    { '>p',    '<Plug>(YankyPutIndentAfterShiftRight)',  desc = 'Put and indent right' },
    { '<p',    '<Plug>(YankyPutIndentAfterShiftLeft)',   desc = 'Put and indent left' },
    { '>P',    '<Plug>(YankyPutIndentBeforeShiftRight)', desc = 'Put before and indent right' },
    { '<P',    '<Plug>(YankyPutIndentBeforeShiftLeft)',  desc = 'Put before and indent left' },
    { '=p',    '<Plug>(YankyPutAfterFilter)',            desc = 'Put after applying a filter' },
    { '=P',    '<Plug>(YankyPutBeforeFilter)',           desc = 'Put before applying a filter' },
  },
}

Removing the picker section improves load times significantly.
Is this expected, or am I doing something wrong?

Following up. I realized that moving the picker settings down to the <leader>p key mapping would help:
    { '<leader>p',
      function()
        local utils = require'yanky.utils'
        local map = require'yanky.telescope.mapping'
        local telescope = require'telescope'

        telescope.extensions.yank_history.yank_history({
        picker = {
          telescope = {
            mappings = {
              default = map.put('p'),
              i = {
                ['<c-j>'] = map.put('p'),
                ['<c-k>'] = map.put('P'),
                ['<c-h>'] = map.put('gp'),
                ['<c-l>'] = map.put('gP'),
                ['<c-x>'] = map.delete(),
                ['<c-r>'] = map.set_register(utils.get_default_register()),
              },
              n = {
                p = map.put('p'),
                P = map.put('P'),
                d = map.delete(),
                r = map.set_register(utils.get_default_register())
              },
            }
          }
        }
      })
      end,
      mode = { 'n', 'x' }, desc = 'Open Yank History'
    },

That at least moves the extra loading time to that key specifically.

Can you try using shada storage instead of sqlite?

Switching to shada does not have an appreciable effect. I tested a number of the configurations described below, and did not fine sqlite increased load times.
Without using telescope at all yanky loads quickly (~2ms) either way.
I've tested a number of combinations, and found that this alone:
{ '<leader>p', function() require'telescope'.extensions.yank_history.yank_history({ }) end,
      mode = { 'n', 'x' }, desc = 'Open Yank History' },

Takes about 600ms to execute, but only when it is invoked the first time.
Adding the picker settings alone is not the problem either. It looks like these lines cause the long load times:
['<c-r>'] = map.set_register(utils.get_default_register()),
r = map.set_register(utils.get_default_register())

Each take around 900ms.

I did a little more testing. The cause of the long delay seems to be this specifically:
require'yanky.telescope.mapping'.get_default_register()

Using require'yanky.telescope.mapping'.set_register()  with a fixed value gets rid of the problem:
['<c-r>'] = `require'yanky.telescope.mapping'.set_register('+'),

I am testing in WSL2. Maybe it's a problem related to how the default register is fetched in WSL2 / Windows?

Hi!
Sorry for the late answer!
Can you tell me the result of :echo provider#clipboard#Executable() and tell me if it take a long time to execute ?

Can you tell me the result of :echo provider#clipboard#Executable() and tell me if it take a long time to execute ?

It's very fast.


[synthetics-job-manager] Add new runtime charts

Is this a new chart
Yes.
What this PR does / why we need it:
Ticket: NR-27388
This PR adds the new charts for the Synthetics Job Manager with the new runtimes and these changes are needed to be able to migrate off the old helm charts to the new ones.
Charts are getting installed and running:

Running Jobs:

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [mychartname])

Hi!
As it is a new chart, the CODEOWNERS file is pointing us as the owners, because it is taking the wildcard on top of it.
Please, add your team as CODEOWNERS for this new chart so you can own it and merge PRs without our approval. As one of your teammates have approved it I have no problem approving it either.
PRs fixing the spelling and removing the bumpers action have been merged so you might also want to rebase to the tip of master to have your tests clean.
Sorry for taking this long to answer.


Allow LinkedDictionary setValue inserting to head

Currently setting value is adding to the list tail. Adding to the head is a frequent and useful operation (and if one needs it, there it is not possible to reuse anything in this implementation).
In general I think it was better not to hide completely the linked list structure from outside and allow in the linked dictionary an optional custom linked list appender.

Closing this because of old age. If the issue persists, discuss it here and/or open a Pull Request please.


How to match plans offered to plans specified (e.g. have console offer plans based on the presence of configmaps in its namespace or variations of that)

Fixed in master


Fix go lint issues in amount.go

Following file has a lint issue:
 maya/types/v1/amount.go
The lint  issue is :
Line 16: warning: package comment should be of the form "Package v1 ..." (golint)
Line 37: warning: exported const Nano should have comment (or a comment on this block) or be unexported (golint)
Line 49: warning: exported var Zero should have comment or be unexported (golint)

Help Links :
Contributors guide

I'd like to look into this

Thanxx @galihmelon for raising the PR.


support sdk 9(add something like ButterKnife's unbinder)

Currently the library use ActivityLifecycleCallbacks to auto-remove event upon Activity's onDestroy.
but it would be great if we can support sdk 9
maybe ButterKnife style unbinder work?

http://jakewharton.github.io/butterknife/#reset

@yshrsmz So, will the method to add listener will remain same? Only change is that the register method will return something that can be used to deregister?

@anoop44 yes, what you said is exactly what I think.
And unregister logic using AativityLifecycleCallbacks should be dropped in favor of this feature.

@yshrsmz Will try to come up something of that sort, just to clarify, do you expect that someone might need multiple listeners?

I think multiple listeners will be needed if someone tries to register listeners from Conductor's controllers, right?

but maybe not needed for initial implementation 😉

since sdk 9 is really old, maybe we should recommend users to upgrade sdk version, and keep current min sdk(which is 14)

closed by #18

Hi,
When I can expect a release for #18 ?

yep, I'm currently working on the release.
sorry to be late

released as v2.1.0


QueryProfiler Interface Update

What is the requested change?
below are some of things that can be implemented on QueryProfilerInterface to increase its utility:
For the [for get_qplan_tree] function

[x] Default metrics of qprof should be more meaningful like: execution_time_ms and prod_rows.
[x] The name of metrics should be more self-explanatory or should have some help. e.g. proc_rows is not easily understandable.
[ ] #1180

select
q1.transaction_id,
q1.statement_id,
q1.row_count as collection_events,
q2.row_count as collection_info,
q3.row_count as dc_requests_issued,
q4.row_count as execution_engine_profiles,
q5.row_count as query_profiles
from
(select transaction_id, statement_id, count(*) as row_count from jan09_cqm_v05.qprof_collection_events_key group by 1,2) q1
full join
(select transaction_id, statement_id, count(*) as row_count from jan09_cqm_v05.qprof_collection_info_key group by 1,2) q2 using (transaction_id, statement_id)
full join
(select transaction_id, statement_id, count(*) as row_count from jan09_cqm_v05.qprof_dc_requests_issued_key group by 1,2) q3 using (transaction_id, statement_id)
full join
(select transaction_id, statement_id, count(*) as row_count from jan09_cqm_v05.qprof_execution_engine_profiles_key group by 1,2) q4 using (transaction_id, statement_id)
full join
(select transaction_id, statement_id, count(*) as row_count from jan09_cqm_v05.qprof_query_profiles_key group by 1,2) q5 using (transaction_id, statement_id)

   transaction_id   | statement_id | collection_events | collection_info | dc_requests_issued | execution_engine_profiles | query_profiles
--------------------+--------------+-------------------+-----------------+--------------------+---------------------------+----------------
<PHONE_NUMBER>14989205 |            1 |                10 |               1 |                  1 |                     60866 |              1
<PHONE_NUMBER>14989217 |            1 |                10 |               1 |                  1 |                     25264 |              1
<PHONE_NUMBER>14989229 |            1 |                10 |               1 |                  1 |                     66535 |              1
<PHONE_NUMBER>14989241 |            1 |                10 |               1 |                  1 |                     57680 |              1
<PHONE_NUMBER>14989328 |            1 |                10 |               1 |                  1 |                     61184 |              1
<PHONE_NUMBER>14989352 |            1 |                10 |               1 |                  1 |                     52464 |              1
<PHONE_NUMBER>14989388 |            1 |                10 |               1 |                  1 |                     48135 |              1
<PHONE_NUMBER>14989601 |            1 |                10 |               1 |                  1 |                     89302 |              1
<PHONE_NUMBER>14989669 |            1 |                10 |               1 |                  1 |                     72842 |              1
<PHONE_NUMBER>14989296 |            1 |                10 |               1 |                  1 |                     60866 |              1
<PHONE_NUMBER>14989364 |            1 |                10 |               1 |                  1 |                     48135 |              1
<PHONE_NUMBER>14989420 |            1 |                10 |               1 |                  1 |                     36802 |              1
<PHONE_NUMBER>14989432 |            1 |                10 |               1 |                  1 |                     52464 |              1
<PHONE_NUMBER>14989181 |            1 |                10 |               1 |                  1 |                     79929 |              1
<PHONE_NUMBER>14989193 |            1 |                10 |               1 |                  1 |                     71719 |              1
<PHONE_NUMBER>14989256 |            1 |                10 |               1 |                  1 |                     56447 |              1
<PHONE_NUMBER>14989268 |            1 |                10 |               1 |                  1 |                     51283 |              1
<PHONE_NUMBER>14989316 |            1 |                10 |               1 |                  1 |                     48135 |              1
<PHONE_NUMBER>14989340 |            1 |                10 |               1 |                  1 |                     48135 |              1
<PHONE_NUMBER>14989376 |            1 |                10 |               1 |                  1 |                     36802 |              1
<PHONE_NUMBER>14989400 |            1 |                10 |               1 |                  1 |                     52464 |              1
<PHONE_NUMBER>14989444 |            1 |                10 |               1 |                  1 |                     51265 |              1
<PHONE_NUMBER>14989569 |            1 |                10 |               1 |                  1 |                     15545 |              1
<PHONE_NUMBER>14989581 |            1 |                10 |               1 |                  1 |                     94739 |              1
<PHONE_NUMBER>14989699 |            1 |                10 |               1 |                  1 |                     56294 |              1
(25 rows)

For the QueryProfiler/QueryProfilerInterface object:

[x] Add the entire metric name when choosing the metric.
[x] Query time should also be displayed in the box
[x] A display of the current query should be available in the get_qplan_tree function

Created an issue with the remaining one so we can close this one.


Implement hint from get_felt_bitlength (Garaga)

Implement hint from get_felt_bitlength (Garaga)
ISSUE: https://github.com/lambdaclass/cairo-rs/issues/977
Description

Implement hint on get_felt_bitlength #993
BuiltinHintProcessor now supports the following hint:
x = ids.x
ids.bit_length = x.bit_length()

Used by the Garaga library function get_felt_bitlength

Checklist

[X] Linked to Github Issue
[ ] Unit tests added
[X] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.
[X] CHANGELOG has been updated.

Can you add some unit tests?

Can you add some unit tests?

Done


DllMain should allocate TLS on DLL_PROCESS_ATTACH

OPENSSL_thread_stop(); is called on DLL_THREAD_DETACH which leads to usage of the Thread local storage (see https://github.com/openssl/openssl/blob/74a8acbdfb2c7f398d1ae2fe914cd32b437f6df4/crypto/init.c#L400) without allocating it beforehand if a thread exits before the user initializes libcrypto.
The suggested fix initializes the libcrypto base only, so that TLS will
be allocated.
(https://github.com/openssl/openssl/blob/74a8acbdfb2c7f398d1ae2fe914cd32b437f6df4/crypto/init.c#L84)
OPENSSL_cpuid_setup(); has been removed since it is already called by ossl_init_base.
Note:This was detected using AppVerifier on windows10
VERIFIER STOP<PHONE_NUMBER>000301: pid 0x6D20: Invalid TLS index used for current stack trace.

<PHONE_NUMBER>000000 : Invalid TLS index.
<PHONE_NUMBER>00ABBA : Expected lower part of the index.
<PHONE_NUMBER>000000 : Not used.
<PHONE_NUMBER>000000 : Not used.

CLA: trivial

Ping @mattcaswell to take a look at this.  I think like @bernd-edlinger says, this code isn't the right way.  A better thing to do is no-op out if the thread-stop variable isn't set.  But looking at crypto/init.c made my brain hurt. :)

This is only a workaround for CRYPTO_THREAD_init_local on windows not using the cleanup function.
Maybe that should be fixed.

The problem was addressed #6752. Thanks for report!


fix(cli): Fixes incorrect variable reference

Because these were additions in #6632, git didn't pick up that the recent refactor of
env settings had changed some of the variables. This fixes those small changes

@thomastaylor312 Thanks a lot for your support 👍


New Core Feature: Edit posts

Ability to edit a post once already made.  Could be combined with the create post page and just have it pull information from the DB.

To support this we'd need an edit history... otherwise people can [and will] play games with trolling then removing the evidence, making the aggrieved respondents look like the aggressors.

Definitely.  Admins or moderators could possibly have access to the prior posts.  Its also good to restrict a post from being edited until it is 5 minutes old.


bump github.com/DataDog/nikos to v1.12.9

What does this PR do?
https://github.com/DataDog/nikos/releases/tag/v1.12.9, fixes an issue with latest version of rpmutils preventing some trivy related work.
Motivation
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

/merge


Unable to satisfy 100% MinSuccessfulInstancesPercent requirement

I get the following error when deploying:
16:21:37 | CREATE_IN_PROGRESS   | AWS::CloudFormation::Stack            | GitlabrunnerBastionStack
16:29:52 | CREATE_FAILED        | AWS::AutoScaling::AutoScalingGroup    | GitlabrunnerAsg1bASG63ACEABF
Received 0 SUCCESS signal(s) out of 1.  Unable to satisfy 100% MinSuccessfulInstancesPercent requirement

Hello Daniel,
ThIs error indicates  that there were an error in cfn-init when installing  gitlab runner bastion. Can you check the network configuration? The subnet where the bastion is deployed should have internet out access and also https  access to the gilab host.

Hello Daniel,
A new version published yesterday which is full serveless, no need now to ec2 instance , all run with fargate.


[FEA] running window like memory improvement for range based queries

#2596 is adding in a memory optimization for rolling window operations. But that only works for row based queries.  We can probably do something very similar for range based queries, but then we would still have to make sure that each batch was partitioned on the order-by columns.  This should be fairly simple to do because we already have code that can partition the batches based off of columns.  The main advantage to this would be that we could support large windows without needing all of the data for a given window in GPU memory at once. But for large running like windows we have performance problems compared to the CPU.  https://github.com/rapidsai/cudf/issues/8440 essentially applies to range based windows, not just row based windows.
But because no customer is complaining about it yet I don't think this should be a priority at this time.

We need to be careful here because GpuRunningWindowFunction also has an optimization to do a scan aggregation instead of a normal window aggregation. This will have to be disabled for range based queries. The performance will not be great here, but at least it will work. We can have a follow on issue to try and understand if there is a good way to still have some of the performance wins from this.


allow tree_implementation="gemm" with onnx backend

Allows onnx backend with TREE_IMPLEMENTATION="gemm".

It looks that the exception here is not related to your PR. I am looking into it (they may have updated the metrics in the latest sklearn release).

Hi @jfrery Thanks for the PR!! Can you please rebase with Matteo's fix and try again? Pipeline should be working now. :)

Codecov Report

Merging #566 (96cffce) into main (cba2e41) will decrease coverage by 4.09%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main     #566      +/-   ##
==========================================
- Coverage   90.41%   86.32%   -4.10%
==========================================
  Files          78       78
  Lines        4560     4556       -4
  Branches      945      946       +1
==========================================
- Hits         4123     3933     -190
- Misses        249      422     +173
- Partials      188      201      +13

Flag
Coverage Δ

unittests
86.32% <66.66%> (-3.94%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

hummingbird/ml/_topology.py
69.13% <60.00%> (-17.18%)
:arrow_down:

hummingbird/ml/convert.py
79.24% <100.00%> (-2.75%)
:arrow_down:

...ummingbird/ml/containers/sklearn/tvm_containers.py
17.24% <0.00%> (-75.87%)
:arrow_down:

.../ml/operator_converters/_linear_implementations.py
75.55% <0.00%> (-22.23%)
:arrow_down:

...ird/ml/operator_converters/onnx/one_hot_encoder.py
62.50% <0.00%> (-18.75%)
:arrow_down:

...tor_converters/_one_hot_encoder_implementations.py
92.45% <0.00%> (-3.78%)
:arrow_down:

hummingbird/ml/operator_converters/sklearn/mlp.py
88.88% <0.00%> (-3.71%)
:arrow_down:

hummingbird/ml/supported.py
90.43% <0.00%> (-2.61%)
:arrow_down:

... and 7 more

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 cba2e41...96cffce. Read the comment docs.


<p> will be added

after edit content it looks like this.. .<p&gt tags added in content
Create fdgfgfghfgjhfgggfgfhfgkhkfgkhkfkghkfgh

Hi, I have the same issue? Any solutions?

Sorry, I don't understand.
@lorisbenedetto could you elaborate? Also, if you create an example of this issue on https://codesandbox.io/ I'll check it.

Hello,
In my case, the reactive v-model data field is wrapped around  tags when I start typing any character. I had attached an example.

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 7 days since being marked as stale.


Fix that downloader options about image decoding is not correctly set

New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[x] I have added the required tests to prove the fix/feature I am adding

[x] I have updated the documentation (if necessary)

[x] I have run the tests and they pass

[x] I have run the lint and it passes (pod lib lint)

This merge request fixes / reffers to the following issues: ...
Pull Request Description
There is a mistake that the 3 options in SDWebImageDownloader does not correctly been set.

SDWebImageAvoidDecodeImage
SDWebImageDecodeFirstFrameOnly
SDWebImagePreloadAllFrames

This PR also fix the warning which shadow the local variable of options

Codecov Report

Merging #2414 into 5.x will increase coverage by 0.05%.
The diff coverage is 66.66%.

@@            Coverage Diff            @@
##              5.x   #2414      +/-   ##
=========================================
+ Coverage   68.74%   68.8%   +0.05%
=========================================
  Files          47      47
  Lines        6649    6652       +3
=========================================
+ Hits         4571    4577       +6
+ Misses       2078    2075       -3

Flag
Coverage Δ

#iOS
69.92% <66.66%> (+0.09%)
:arrow_up:

#macOS
68.53% <66.66%> (-0.06%)
:arrow_down:

Impacted Files
Coverage Δ

SDWebImage/SDWebImageDownloader.m
81.01% <100%> (-0.15%)
:arrow_down:

SDWebImage/SDImageCacheDefine.m
62.16% <40%> (ø)
:arrow_up:

SDWebImage/SDImageLoader.m
86% <70%> (ø)
:arrow_up:

SDWebImage/SDAnimatedImageView.m
69.74% <0%> (-1.16%)
:arrow_down:

SDWebImage/SDWebImageManager.m
81.3% <0%> (-0.82%)
:arrow_down:

SDWebImage/SDWebImageDownloaderOperation.m
88.31% <0%> (+3.78%)
:arrow_up:

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 1c89282...892267a. Read the comment docs.


Server side vs client side build matrix generation

Comparing client side (current) and server side implementations of the CI Build Matrix:
Client Side
Assumptions:

build static HTML/JS/CSS which fetches latest state from the client side
Use github API.  If their IP runs out of API juice, allow them to oath into github
deployed to IPFS, available at ci-status.ipfs.io or similar

Pros:

always see very current information via Github API

Cons:

requires setting up an oauth gateway that we manage

Server Side
Assumptions:

build static HTML/CSS based on latest state
kick off from a cronjob, eg hourly
anyone can manually run the script to get the freshest information
deployed to IPFS, available at ci-status.ipfs.io or similar

Pros:

no need for oauth server
all the information is baked into the actual HTML in IPFS, not fetched/generated in client side

Cons:

not realtime information (hourly)
cronjob needs to be hosted somewhere: another moving part (maybe free heroku scheduler?)
ideally cronjob should fail visibly, eg a build should fail

I think through the exercise of creating the comparison above I have convinced myself that client side:

is a much better experience for users
is not significantly harder to implement
has the same or lower number of moving parts

can maybe cache some of the generated stuff even clientside under some shared ipns space. doubt it will be abused and can always be overridden.

can maybe cache some of the generated stuff even clientside under some shared ipns space.

how can we do that from the client side?  through a gateway?  can you even write to IPNS via gateway?  do you need a private key to do so?

Closing, as we are now firmly doing client-side.

Woot. Thanks @harlantwood


IAM support seems to have broken for me

Not sure maybe I am missing a step here, this used to work for me but now with a new 3ec2 instance, new role, and new bucket it no longer works.
For troubleshooting purposes I created the role/policy as:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": "*"
        }
    ]
}

aws s3 cli tools work with no need to give keys, they use IAM fine and work for every url I have tried.
So what can I do to troubleshoot this and figure out whats going on?

Oh, by the way this is the error I get:
failure: repodata/repomd.xml from $MYBUCKETNAME: [Errno 256] No more mirrors to try.
Where $MYBUCKETNAME obviously is my bucket name in the output. If I make that file publicly accessible, it then chokes on the next file, one of the sqlite gzipped dbs, with the same error. So in my mind that would mean its not a path mismatch problem. Its probably something simple I am missing, please help me diagnose the problem.

What region are you in?  This plugin only supports SigV2 but some regions only support SigV4: http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html.  Also, would you mind sharing your yum repo conf?

I use the configuration specified from https://github.com/revmischa/udo
I'm in us-west-2 (Oregon)


Improve the Variant class documentation

Taken from https://docs.godotengine.org/en/latest/development/cpp/variant_class.html.
The page above could be edited or even removed if we add enough information to the Variant class directly.

Brief description: The most important data type in Godot.

Sees empty docs. 🤷♂

Thanks!

Cherry-picked for 3.1.2.


[Construct/NextjsSite] Allow page router preview mode to bypass the cloudfront cache

Hi,
In Next.js page router when using preview mode we often received the cached page instead of the preview version. This ensures that when we are in preview mode (depends on the cookie __prerender_bypass) we set a header called x-prerender-bypass which is added to the list in DEFAULT_CACHE_POLICY_ALLOWED_HEADERS.
Thanks @conico974 for the help
Relevant discord discussion: https://discord.com/channels/983865673656705025/1179733950533480538

Thanks!

@jayair Just wondering whats preventing currently for getting this merged and how I can assist in getting it to a point where its acceptable? I've seen a couple of discord questions specifically mentioning that pages router + preview is broken in open next and this fixes it.

Oh no the team might've missed this. I'll ping them.

Thanks @JanStevens! Will be in the next release.


Use layer caching to speed up Build / Release workflows

The Build workflow, which is a required status check, takes about an hour to run.
When we run the Release workflow we have to rebuild the container again from scratch, because we don't have any of the layers cached.
This blog post could be a good starting point for how to use GitHub's cache.

I've merged #46 so we can watch it perform.

Don't know why this isn't working. It all looks correct to me, but the images are still being completely rebuilt every time.

This may be improved by #69

Shall we close this now @ciaranmcnulty ?

Think so, yeah

@mattwynne although thinking about it, what's the point of a nightly cached build?

I guess the nightly build should not be cached, but it would be nice if the on.push build were faster.

As we gradually dismantle the monorepo, this image becomes less and less important anyway. I think we can figure out a new approach if we want to be able to do polyglot builds locally of libraries like gherkin once they're out of the monorepo.

We could --no-cache the nightly
I've been holding off on optimising the cucumber/common build because of the promised monorepo future :)

if we want to be able to do polyglot builds locally of libraries

A buildkit + multiple container approach would be good here. Is it worth prototyping inside, say, Messages?

I think an existing polyglot repo like cucumber-expressions would be a better place to prove the concept, then when we have extracted messages we can try it there with more languages/build environments.

Is there a problem with the cucumber-expressions build process we need to address? I’m fine with the way it currently works.

Not particularly. The suggestion is that we may, for some polyglot projects (e.g. gherkin), want a way to run tests across all/several platforms locally, without having to push and wait for CI for feedback, or rely on this big docker image. I think cucumber-expressions would be a good place to try that kind of thing out.

Expressions is fine IMO because there's not anything generated
The complexity has in the past come from something like messages where Ruby+target are used, or Gherkin where dotnet+target were used
I don't know how we are tackling the DX of running the tests locally for Expressions?


Too many request

Its showing me too many request when I run the script.
File "gsmarena-scraper.py", line 32     logger.info(f"Too many requests.")                                     ^ SyntaxError: invalid syntax
How can I solve this?

@tushar09 did you able to solve it?