Can't Install Terraform Version 1.0.3

Hello,
I'm using asdf version v0.10.1 and trying to install terraform version 1.0.3, but I am getting the following error:
$ asdf install terraform 1.0.3
Downloading terraform version 1.0.3 from https://releases.hashicorp.com/terraform/1.0.3/terraform_1.0.3_linux_amd64.zip
Error: terraform version 1.0.3 not found
I've checked hashicorp and verified that that version/path exists.
I'm using WSL 2.0 on Ubuntu-10.04.
Please let me know what I can do to resolve here.
Thanks,
Russell

Hmm, I do not have access to a WSL setup to try this out there, but just trying this out on a different Ubuntu, it installs fine. That file definitely exists to be downloaded. It's hard to know what might be the cause without more information.
Just going off the output, it looks like it failed here: https://github.com/asdf-community/asdf-hashicorp/blob/master/bin/install#L84 so if you can try that curl manually, maybe you'll see what error curl is returning?

Hey @DustinChaloupka,
Thanks  for responding, I appreciate it. This seems to be a local DNS issue for me- I haven't resolved it yet but it seems like it's not a universal bug


Dashboard Revamp

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
This PR revamps the current Dashboard

Updated the Layout
Added Table component with Sorting, Pagination
Integrated with CPT_JOBS API
Updated the Doc file Readme.md

Related Tickets & Documents

Related Issue # PANDA-361
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please describe the System Under Test.
Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

@MVarshini Can you update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

I still come across this error when I run sh local-compose.sh
[1/4] Resolving packages...
[2/4] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^18.0.0 || >=20.0.0". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: building at STEP "RUN yarn install": while running runtime: exit status 1
87f2197c97e62613568d0ee74158e85d4318c95da5152a2275b5244e79e1b474
Trying to pull localhost/frontend:latest...
WARN[0000] Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0001] Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0002] Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

I still come across this error when I run sh local-compose.sh
[1/4] Resolving packages...
[2/4] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^18.0.0 || >=20.0.0". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: building at STEP "RUN yarn install": while running runtime: exit status 1
87f2197c97e62613568d0ee74158e85d4318c95da5152a2275b5244e79e1b474
Trying to pull localhost/frontend:latest...
WARN[0000] Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0001] Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0002] Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

Checked again. Works fine.

What is our status on this integration?

@chentex and I had to chat to get these in after the telco changes. @MVarshini would you mind updating this PR please?

@MVarshini I am unable to test this change, local-compose seems to run, however the frontend pod doesn't seem to be serving out anything?

><EMAIL_ADDRESS>dev
> vite

  VITE v5.2.7  ready in 156 ms

  ➜  Local:   http://localhost:3000/
  ➜  Network: use --host to expose

Is the containerfile for the frontend up to date?

@jtaleric The container file is up to date. Try to hit http://localhost:3000/ on the browser if it doesn't work let's it offline and check.

@MVarshini Thanks for the fix to the local-compose -- in the past we never needed hostNetwork.
There are still aspects of the new dashboard that seem broken for me.

When I select OCP, the list of tests are not updating to just OCP workloads.

When I click the menu button, I see a "hello" message.
I don't want to rush things, but is this PR ready?

@MVarshini Thanks for the fix to the local-compose -- in the past we never needed hostNetwork.
There are still aspects of the new dashboard that seem broken for me.  When I select OCP, the list of tests are not updating to just OCP workloads.
 When I click the menu button, I see a "hello" message.
I don't want to rush things, but is this PR ready?

It has only the Home Page Table and OCP page hasn't been included here.
Also, Side menu toggle is a bug and it has been fixed in this PR #102 which has both Home and OCP pages with Filter and Summary Tab


Change environment of vscode shell

VSCode Version: 1.44.2 (remote)
OS Version: Red Hat

Not sure if this is a bug or a feature request:
I'm working with vscode remote via SSH.
The remote host is a Red Hat Linux and I have two projects configured. For both there are many bash scripts needed which setup some environment. My idea was to use an automated task when the project folder is loaded to source an environment.
The problem is that running bash scripts with a task will not change the environment of the shell which launched vscode. Or at least that is my understanding.
{
  "label": "SetEnv",
  "type": "shell",
  "command": "./scripts/EnvForProject1.sh",
  "runOptions": {
    "runOn": "folderOpen"
  }
}

So the current solution I have is to source the specific environments in all bash scripts which are called many times during a session(cmake build etc). I know that vscode will source .bashrc on startup and here I could set one project environment. But how can I then change to the other project's environment when opening it with vscode?
Is there some way to change to a different environment in the "main vscode" shell?

Is there some way to change to a different environment in the "main vscode" shell?

You might try asking on stack overflow as this sounds like a more general question of "how can I change the environment of a running process from another process". That sounds like a security problem though.
If you are only interested in changing the environment for the terminal and tasks, and not for all of VS Code, you could have workspace specific settings for terminal.integrated.env.linux.


Season match inconsistency

For the latest version: 2.0.3
There's a season match inconsistency when release names have no season (I'll provide real examples later today).
Given a video file as bellow:
Show.Name.E05.720p.x264.mkv
The created video object will have season 1, since guessit will not return season, but this code will default it to 1.
Then when the subtitles (e.g.: Show.Name.E05.720p.x264,srt) are found (by any provider), some/most of them will use guessit to retrieve all the release information and this code will prevent a season match, since video.season == 1 but 'season' is not in guess
Either the season shouldn't be defaulted to 1 in the video or the compute score should follow the same logic.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36387104-season-match-inconsistency?utm_campaign=plugin&utm_content=tracker%2F321252&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F321252&utm_medium=issues&utm_source=github).

I agree on that. The code you linked to was introduced to handle mini-series that don't have a season number in the filename. Something more clever is needed here.

Just to illustrate and give some real examples, there are series that doesn't follow season/episode numbering on their release names. Not all providers have subtitles for those series.
Here are some examples of episodes without season and/or episode numbers:

Air by date (guessit: date): documentaries episodes or talk shows
Catalyst.2015.11.10.Einstein.360p.LDTV.WEBRIP.[MPup]
Eastenders.2016.05.27.HDTV.x264-DEADPOOL

Absolute episode numbering (guessit: episode): animes
Kiznaiver.E06.SUBFRENCH.720p.HDTV.x264-D4KiD

Absolute episode using part (guessit: part):
The.Night.Of.Part.8.INTERNAL.720p.HDTV.x264


what exactly does the  word ''overridden'' mean here?

     In your paper, the III. METHODOLOGY and D. Environment model

you mentioned, "If the front is the ego vehicle and the gap between them is smaller than the desired gap given by IDM, the environment vehicle will be overridden by IDM and thus not follow its original trajectory anymore. " I cannot understand the meaning of overridden. Can you elaborate that? thanks a lot！

After I run [python dump_data.py D:\python311\daima\Driving-IRL-NGSIM-main\Next_Generation_Simulation__NGSIM__Vehicle_Trajectories_and_Supporting_Data.csv]
Although some data was generated, corresponding storage files were not generated. can you tell me the reason? thanks!

"Override" means that the influenced vehicle will be controlled by an IDM planner instead, deviating from its original trajectory. "dump_data.py" only processes the raw data from the NGSIM data into a more structured format, without saving any data points. It's worth noting that we collect training data from simulations, not offline datasets.

"Thank you for your response. The issue I'd like to address is that after I ran this command "dump_data.py", the 'processed' folder was not generated, and when I proceeded to the next step, I encountered the following error in the picture. I'm not sure what the reason is, so I'm seeking your assistance."

I don't exactly know the reason, but I strongly suggest using the code in a Linux environment since I have only tested it in Linux.

Yes, Python 3.7 would work.

Thanks again! When I read codes, I found that in "behavior.py" and "control.py", except the IDM and MOBIL models, there are many formulas and parameters you do not mentioned in your paper, I wonder what they are basing it on .Is there any relevant references paper or books you can provide me? Thanks a lot!

Sorry to bother you again. May I ask how long it usually takes to see the visualization results after running personal_IRL? I have been running it for over twelve hours and still haven't seen any results.

If you want to visualize the testing results, set the parameter render_env = True at the beginning of the code.


Errors building

Hi I have problems installing this repo.
When I run build.sh as suggested in the instructions i get the following error even when I update g++ and build-essesntials
running build_ext
building 'parsing._C' extension
Emitting ninja build file /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
[1/2] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc -I/home/ariel/.local/lib/python3.8/site-packages/torch/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/TH -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.8 -c -c /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/linesegment.cu -o /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/linesegment.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DCUDA_HAS_FP16=1 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_86,code=compute_86 -gencode=arch=compute_86,code=sm_86 -std=c++14
FAILED: /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/linesegment.o
/usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc -I/home/ariel/.local/lib/python3.8/site-packages/torch/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/TH -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.8 -c -c /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/linesegment.cu -o /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/linesegment.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DCUDA_HAS_FP16=1 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_86,code=compute_86 -gencode=arch=compute_86,code=sm_86 -std=c++14
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
nvcc fatal   : Failed to preprocess host compiler properties.

[2/2] c++ -MMD -MF /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/vision.o.d -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DWITH_CUDA -I/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc -I/home/ariel/.local/lib/python3.8/site-packages/torch/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/TH -I/home/ariel/.local/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.8 -c -c /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/vision.cpp -o /home/ariel/work/Replicate/repos/SRW-Net/build/temp.linux-x86_64-3.8/home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/vision.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
In file included from /home/ariel/.local/lib/python3.8/site-packages/torch/include/ATen/Parallel.h:140,
                 from /home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/utils.h:3,
                 from /home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/nn/cloneable.h:5,
                 from /home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/nn.h:3,
                 from /home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:13,
                 from /home/ariel/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
                 from /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/cuda/vision.h:2,
                 from /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/linesegment.h:2,
                 from /home/ariel/work/Replicate/repos/SRW-Net/parsing/csrc/vision.cpp:1:
/home/ariel/.local/lib/python3.8/site-packages/torch/include/ATen/ParallelOpenMP.h:87: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
   87 | #pragma omp parallel for if ((end - begin) >= grain_size)
      |
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "/home/ariel/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1666, in _run_ninja_build
    subprocess.run(
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "setup.py", line 62, in <module>
    setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 144, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/build_ext.py", line 87, in run
    _build_ext.run(self)
  File "/home/ariel/.local/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
    _build_ext.build_ext.run(self)
  File "/usr/lib/python3.8/distutils/command/build_ext.py", line 340, in run
    self.build_extensions()
  File "/home/ariel/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 709, in build_extensions
    build_ext.build_extensions(self)
  File "/home/ariel/.local/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
    _build_ext.build_ext.build_extensions(self)
  File "/usr/lib/python3.8/distutils/command/build_ext.py", line 449, in build_extensions
    self._build_extensions_serial()
  File "/usr/lib/python3.8/distutils/command/build_ext.py", line 474, in _build_extensions_serial
    self.build_extension(ext)
  File "/usr/lib/python3/dist-packages/setuptools/command/build_ext.py", line 208, in build_extension
    _build_ext.build_extension(self, ext)
  File "/usr/lib/python3.8/distutils/command/build_ext.py", line 528, in build_extension
    objects = self.compiler.compile(sources,
  File "/home/ariel/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 530, in unix_wrap_ninja_compile
    _write_ninja_file_and_compile_objects(
  File "/home/ariel/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1355, in _write_ninja_file_and_compile_objects
    _run_ninja_build(
  File "/home/ariel/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1682, in _run_ninja_build
    raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension

Can you help?

Hi,
Thanks for reaching out. Unfortunately I have not seen this error before.
Did you build a docker image defined by the supplied Dockerfile or are you setting up your own environment?
I've build in my docker-container using gcc and g++ version 7.5.0. What versions are you using?

Hi, thanks for the quick reply:
I'm building  localy and not using a docker image.
My versions are:
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
gcc (Ubuntu 8.4.0-3ubuntu2) 8.4.0
About docker
There is no docker/build_docker.sh script only docker/build.sh which didn't work for me giving the error:
./build.sh: line 2: ./../libs/dockers/common/build.sh: No such file or directory
When I built a docker image from the DockerFile in the docker folder using  docker build -f .
it asks for host name
[powerlevel10k] fetching gitstatusd .. [ok]
 pytorch  /host_home 

Unfortunately I have no ideas for your build.
I've only used the environment defined by the Dockerfile which is based on ubuntu18.04.
Please let me know if you figure it out!


Pluck on Nested Arrays Help

Hi,
I'm trying to use pluck method on my nested array objects.. My structure is same as in docs but mine gets only first object of child array. my object array structure is as follows
https://ibb.co/7W7NcRS
And I try to collect sizes with following code;
const totalSizePartCads = collect(this.parts).pluck('cads.*.size').sum()
I want to sum sizes in parts object array below.
parts = [
    { name: 'part name 1', cads: [ {name: 'name 1', size: 1024} ] },
    { name: 'part name 2', cads: [ {name: 'name 2', size: 1024} ] },
    { name: 'part name 3', cads: [ {name: 'name 3', size: 1024} ] },
    ...
    ...
    ...
]

Where is my mistake? Thank you..

Hi @ecrmnn thanks for your reply.. I solved it by adding collaps method as follows:
const totalSizePartCads = collect(this.parts).pluck('cads').collapse().pluck('size').sum()
Thank you

🙌


[BUG]  Error: Invalid argument (body)

Describe the bug
Error: Invalid argument (body): "{\"date_send\":null,\"stock_from_id\":2,\"stock_to_id\":8,\"user_from_id\":null,\"user_to_id\":null,\"comment\":null,\"consignments\":[{\"count\":1,\"product_model_id\":56}]}"
To Reproduce
{
    "name": "body",
    "in": "body",
    "description": "Specify 'product_model_id' and 'count' of consignments",
    "required": true,
    "schema": {
        "type": "object",
        "$ref": "#/definitions/ConsignmentBodyPost"
    }
}

Swagger specification link
Describing Request Body
Library version used:
swagger_dart_code_generator: ^2.6.0

Hi @vadimlukutin , I've tried to reprocude your case and have next generated code:
///Add a new pet to the store
  ///@param body Specify 'product_model_id' and 'count' of consignments
  @Post(path: '/pet')
  Future<chopper.Response> _petPost(
      {@Body() required ConsignmentBodyPost? body,
      @Header('Cache-Control') String? cacheControl});

request looks fine. So, possible, problem is in ConsignmentBodyPost. Please provide definition of this or describe expected generated code. Thanks.

@vadimlukutin  closing the issue due to no response. Now I have not enough information to fix it. Fill free to reopen issue.


[red-knot] Integrate formatter

Summary
This is a first hacky approach to integrate the formatter into red-knot.
There are plenty of TODOs. The main questions is where and when we should write the formatted content and how we avoid that formatting requires two-passes for the cache to be "hot".
Test Plan
I ran red knot and it formated my files (all lints gone, whoops)

I still plan to land this PR eventually but aren't prioritising it right now. Deciding on a query system and exploring persistent caching is of higher importance right now.


Entity Visualizer

A path visualizer that summons an entity which walks along the path as long as the player is close enough.

link a citizen to a visualizer via its id
the visualizer spawns a copy of the citizen at the fitting location and lets it move via edge based visualizer and a target point near the player


Adding aws to CI tests

Adding AWS EC2 to our pipeline
Spins up m.5 instance and runs molecule test

Pipeline works - molecule/README.md needs work to configure for local development workflow
Take a look at benchmarks to see if an instance with more cores is faster/does it make sense

I honestly cannot see anything that sticks out as wrong code wise. Structure wise do you think it might be worth splitting it out from the create files and dumping them as a task within the molecule/default/tasks/ directory.
@bkabrda @SequeI wdyt?
Outside of that it lgtm

@tommyd450
I fully agree, this will be good to do I think during the ticket to make the 2 scenarios run in parallel while network infra instantiates before they are run. For now it is probably fine as we get used to this new system but good idea!


Faster Whisper (CTranslate2) Support

https://github.com/guillaumekln/faster-whisper/

This implementation is up to 4 times faster than openai/whisper for the same accuracy while using less memory

I would assume we'd greatly benefit from the improved performance since we're working with live translating

thanks. this is now integrated and possible to activate in the UI (or setting faster_whisper: true in the config yaml)

Honestly I was not expecting support for this, thank you so much. I'm looking forward to testing and using this soon. Hopefully I can finally run the large whisper model and get better results.


valueList argument in the Image tag does not work

Describe the bug
When forming a Label Interface for a list of images, the value List argument is ignored.
Image column data example:
['https://103school.ru/foto/telef112.png', 'https://catherineasquithgallery.com/uploads/posts/2021-03/1614587266_10-p-kartinka-telefon-na-belom-fone-10.jpg', ...]
To Reproduce
Steps to reproduce the behavior:

Go to Project Settings
Click on Labeling Interface
Click on Code
Use Image tag with valueList  argument, pass the values of the argument

Expected behavior
Images reflect by the list
Environment (please complete the following information):

Label Studio Version 1.12.1

/jira create

For anyone following along on my issue #6106, follow here as well.

Please check this instructions:
https://github.com/HumanSignal/label-studio/issues/6106#issuecomment-2362507754
You have to enable this feature flag:
fflag_feat_front_lsdv_4583_multi_image_segmentation_short=1 label-studio

and then use this labeling configuration:
<View>
  <Image name="image" valueList="$images" />

  <RectangleLabels name="labels" toName="image">
    <Label value="Cat" />
    <Label value="Dog" />
  </RectangleLabels>
</View>

<!-- {
  "images": [
    "https://data.heartex.net/open-images/train_0/mini/00607c8121301d54.jpg",
    "https://data.heartex.net/open-images/train_0/mini/00a21fb1ed2af5e6.jpg"
  ]
} -->


Add Tokyo(MRHSLMusic Remix) by Ivycomb Music

Song Name
Tokyo(MRHSLMusic Remix)
Artist Name
Ivycomb Music
Source
Youtube
Youtube Link
Y-UPgQOt874
Direct File Link
No response
Song ID
1202803
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 109017547

accept


WIP: source: Mysql Source feature

This PR hopes to add a feature to work with data from a mysql database.

import unittest

from dffml.util.testing.source import SourceTest
from dffml.util.asynctestcase import AsyncTestCase

from dffml.source.mysql import MysqlSourceConfig, MysqlSource

class TestMysqlSource(SourceTest, AsyncTestCase):
    async def setUpSource(self):
        return MysqlSource(
            MysqlSourceConfig(... parameters, get from os.getenv ...)
            # user=os.getenv("MYSQL_USER")
            # password=os.getenv("MYSQL_PASSWORD")
        )

    async def test_update():
        await super().test_update()

We will start a mysql database within travis CI and set environment variables the same way we start the database, aka, same MYSQL_USER, MYSQL_PASSWORD from docker hub docs: @pdxjohnny will do this for travis.

To have aiomysql installed for testing, add to setup.py
    # ...
    packages=find_packages(),
    install_requires=[
        "aiomysql>=Go find the latest version number of PyPi and put it here",
    ],
    include_package_data=True,
    # ...

Codecov Report

Merging #114 into master will decrease coverage by 0.97%.
The diff coverage is 43.28%.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage   92.92%   91.95%   -0.98%
==========================================
  Files          53       54       +1
  Lines        3337     3404      +67
  Branches      381      385       +4
==========================================
+ Hits         3101     3130      +29
- Misses        185      222      +37
- Partials       51       52       +1

Impacted Files
Coverage Δ

dffml/source/mysql_source.py
43.28% <43.28%> (ø)

dffml/source/source.py
86.88% <0%> (ø)
: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 86a0168...facb3da. Read the comment docs.

For testing purpose, SSL certificate was generated using openssl.
openssl genrsa 2048 > private.pem
openssl req -x509 -days 1000 -new -key private.pem -out ca.pem

While generating cert, it'll ask for details such as country code, state code, etc. I've generated the cert used in tests/ssl_resources by giving only country code as 'IN', rest of the fields are left blank.

I'm working on fixing the merge test. I'll fix that for JSONSource, modify things here, and merge it all soon.

I'll get to adding this to travis soon


Python: Example notebook incorrect deployment name definition

Description
On of the python example notebooks the deployment is read from the environment but it is being passed as a hard coded variable to the class constructor. This PR aims to correct it
Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingTOTAL499893781% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1042
1 :zzz:
0 :x:
0 :fire:
17.227s :stopwatch:

Python 3.11 Test Coverage Report • FileStmtsMissCoverMissingTOTAL499893781% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.11 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1042
1 :zzz:
0 :x:
0 :fire:
18.036s :stopwatch:

Python 3.8 Test Coverage Report • FileStmtsMissCoverMissingTOTAL485594581% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.8 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1042
11 :zzz:
0 :x:
0 :fire:
20.472s :stopwatch:

Python 3.9 Test Coverage Report • FileStmtsMissCoverMissingTOTAL499293981% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.9 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1042
2 :zzz:
0 :x:
0 :fire:
20.855s :stopwatch:


AnVIL: Display and add search facets for Dataset consent_group and data_use_permission

Current Behavior
The Dataset consent_group and  data_use_permission values are not currently displayed in the Dataset tab, nor are there search facets for them.
Requested Behavior

Display the Dataset consent_group and  data_use_permission values as columns on the Dataset tab.
Add a search facets for Dataset consent_group and  data_use_permission

Considerations
Although the values of these two fields are similar, they are not necessarily the same.
My understanding is:

The consent_group is most commonly understood and used by researchers today.
The data_use_permission will see increasing use with DUOS in AnVIL going forward.
Therefore, I expect both are important, yet this may warrant verification/discussion.

Completed

Completed


Change logging and reporting of layer checksums to the container image's checksum

Problem Statement
Tern's logging and report checksum information is useful in identifying layers in the container image. However, the checksums do not actually match the checksums in the image manifest (they are tern's own checksums). These make it difficult to debug which layer brought in what packages and which layer metadata was not found
Describe the Proposal
Change the logging and reporting of the layers to reference the layer checksum from the container image manifest.
Steps to Implement Proposal

Create a method in the image_layer.py class to return the layer tarball's hash. This is the name of of the file in layer.tar_file.
Find all the places where layer.fs_hash[:10] is being used and use the new method instead.

Had some discussion with Nisha about this proposal. Instead of trying to pull the layer hash from the variety of container image client manifests (that all represent the hash in different ways/places) we will refer to the layers by order. We feel that this is more widely understood and intuitive.


About data processing

Hi,
Thanks for your great work. We are very interested in your online 3d segmentation method. We have tried to evaluate the model provided in https://github.com/jzhzhang/FusionAwareConv on scannet validation set, but find there is no scripts for processing data into the required h5 file. I would really appreciate it if you could share this part of code.
We also send an email to your gmail for some additional questions. Looking forward to your reply. Thanks a lot!

Thanks for your interest in our project. I already sent the data and training code to you.


Could dart support offline build and publish app to android?

I'm dart developer in china, due to the GFW( china great firewall), I can't using pub tool to get or upgrade package , so I hope dart sdk could support build and publish app in offline mode.
Could dartt support offline build and publish app to android?

Pub does have an --offline flag that you can pass to pub get or pub upgrade that will tell it to only fetch packages from your local cache. If you can fill that cache manually, it's certainly possible to avoid making requests to pub.dartlang.org. I don't think this is something we want to support more explicitly, though.


AWS - Metaphor app fails to pull due to image name mismatch

Which version of kubefirst are you using?
2.2.17
Which cloud provider?
AWS
Which installation type?
CLI
Which distributed Git provider?
GitHub
What is the issue?
Problem

Metaphor image is successfully published
Image fails to pull due to name mismatch

Metaphor is checking ghcr.io/<GITHUB_ORG>/metaphor:hash
Gitops is publishing to ghcr.io/<GITHUB_ORG>/metaphor/metaphor:hash (note the duplicative metaphor)

Similar to the GCP issue here: https://github.com/kubefirst/kubefirst/pull/1774, @cameronraysmith submitted a fix for AWS here: https://github.com/kubefirst/kubefirst/pull/1797
I believe @Claywd is currently looking into this (screenshots below for context)
Additional context

Related issues

https://github.com/kubefirst/kubefirst/issues/1788
https://github.com/kubefirst/kubefirst/issues/1764
https://github.com/kubefirst/kubefirst/issues/1790

Code of Conduct

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

Fixes that I originally tried (URL change based on @cameronraysmith's suggestion, the application.yaml change based on changes that are being made to Civo)

Tried digging into registry and noticed that it's unavailable

Thanks for reporting this issue @alechp: someone will review @cameronraysmith's PR soon.

Tried the build again. Getting no such file or directory for registry/development/components/development/metaphor/Chart.yaml:

When I dig into the gitops repo, I notice that the specified --cluster-name passed to kubefirst aws create is missing from the path that's being checked:

Full log
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: setting wrapper Chart.yaml to version: 0.0.1-rc.58bfec9
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: sed: can't read registry/development/components/development/metaphor/Chart.yaml: No such file or directory
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: time="2023-09-12T03:12:17.257Z" level=info msg="sub-process exited" argo=true error="<nil>"
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: time="2023-09-12T03:12:17.258Z" level=info msg="/src -> /var/run/argo/outputs/artifacts/src.tgz" argo=true
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: time="2023-09-12T03:12:17.258Z" level=info msg="Taring /src"
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: time="2023-09-12T03:12:17.381Z" level=info msg="archived 293 files/dirs in /src"
metaphor-development-58bfec9-gttdz-set-environment-version-3227680445: Error: exit status 2
metaphor-development-58bfec9-gttdz Failed at 2023-09-12 03:12:24 +0000 UTC

Context

running from source, not 2.2.17
This is the last commit on kubefirst as of testing this script:

https://github.com/kubefirst/kubefirst/commit/38c4d4fa7d691657956c785220bfa8b880b9357d

Source of the issue from https://github.com/kubefirst/kubefirst/issues/1801#issuecomment-1714902355 is due to the metaphor/github/main.yaml workflow setting the cluster name to the environment

I fixed this by updating the fullChartPath parameter in metaphor/.argo/deploy.yaml from registry/{{workflow.parameters.clusterName}}/components/{{workflow.parameters.environment}}/{{workflow.parameters.appName}}/Chart.yaml to        registry/capswancloud/components/{{workflow.parameters.environment}}/{{workflow.parameters.appName}}/Chart.yaml
You can see this matches the generated value:

The actual fix would be to update the -p clusterName in each stage. This would also address the subsequent failure in metaphor/.argo/release.yaml where it also references workflows.parameters.clusterName

The following manual changes gets Github Actions workflow to pass all the way through release:

fullChartPath value in metaphor/.argo/deploy.yaml and metaphor/.argo/release.yaml (2 files, same update in both):
From:

              parameters:
                - name: fullChartPath
                  value: 'registry/{{workflow.parameters.clusterName}}/components/{{workflow.parameters.environment}}/{{workflow.parameters.appName}}/Chart.yaml'

To:
              parameters:
                - name: fullChartPath
                  value: 'registry/WHATEVER_VALUE_YOU_PASSED_TO_--cluster-name_IN_CLI/components/{{workflow.parameters.environment}}/{{workflow.parameters.appName}}/Chart.yaml'

For sake of consistency (although this doesn't fix it by itself which is why I include it as second priority) update the clusterName in staging, development and production. Need to update once for each stage:
From:

      - name: development
        run: |
          echo "commit sha $GITHUB_SHA"
          argo version --short
          argo submit .argo/deploy.yaml \
            --generate-name="${GITHUB_REPOSITORY_NAME_PART}-development-${GITHUB_SHA_SHORT}-" \
            -p appName="${GITHUB_REPOSITORY_NAME_PART}" \
            -p branch="${GITHUB_REF_NAME}" \
            -p clusterName="development" \
            -p environment="development" \
            -p gitUrlNoProtocol="git@github.com:${GITHUB_REPOSITORY_OWNER_PART_SLUG}" \
            -p shortSha="${GITHUB_SHA_SHORT}" \
            --wait --log

To:
      - name: development
        run: |
          echo "commit sha $GITHUB_SHA"
          argo version --short
          argo submit .argo/deploy.yaml \
            --generate-name="${GITHUB_REPOSITORY_NAME_PART}-development-${GITHUB_SHA_SHORT}-" \
            -p appName="${GITHUB_REPOSITORY_NAME_PART}" \
            -p branch="${GITHUB_REF_NAME}" \
            -p clusterName="WHATEVER_VALUE_YOU_PASSED_TO_--cluster-name_IN_CLI" \
            -p environment="development" \
            -p gitUrlNoProtocol="git@github.com:${GITHUB_REPOSITORY_OWNER_PART_SLUG}" \
            -p shortSha="${GITHUB_SHA_SHORT}" \
            --wait --log

Add whitespace to metaphor Chart

Context:

Despite GH Action succeeding, still failing to deploy. PUblish failed multiple times, and the dev/stage/prod stuck as pending indefinitely (left it running since yesterday)
Screenshots

Only metaphor (dev/stage/prod namespaces)

Updated build script to include two extra flags:
--gitops-template-url https://github.com/kubefirst/gitops-template
--gitops-template-branch main

Before metaphor even loads, I'm getting an error on metaphor-development-[hash]-[hash]-set-environment-version-[hash]

Pertinent error from logs:
time="2023-09-19T01:19:50.226Z" level=warning msg="failed to patch task set, falling back to legacy/insecure pod patch, see https://argoproj.github.io/argo-workflows/workflow-rbac/" error="workflowtaskresults.argoproj.io is forbidden: User \"system:serviceaccount:argo:argo-server\" cannot create resource \"workflowtaskresults\" in API group \"argoproj.io\" in the namespace \"argo\""

This seems to be what kicks off the initial errors that we saw above; they still exist in current version. Namely:
metaphor-development-32f8779-65f8z-set-environment-version-3899486693: setting wrapper Chart.yaml to version: 0.0.1-rc.32f8779
metaphor-development-32f8779-65f8z-set-environment-version-3899486693: sed: can't read registry/development/components/development/metaphor/Chart.yaml: No such file or directory

Full logs for that failed pod:
time="2023-09-19T01:19:47.789Z" level=info msg="Starting Workflow Executor" version=v3.4.1
time="2023-09-19T01:19:47.796Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5
time="2023-09-19T01:19:47.796Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=argo podName=metaphor-development-32f8779-65f8z-set-environment-version-3899486693 template="{\"name\":\"set-environment-version\",\"inputs\":{\"parameters\":[{\"name\":\"chartVersion\",\"value\":\"0.0.1-rc.32f8779\"},{\"name\":\"environment\",\"value\":\"development\"},{\"name\":\"fullChartPath\",\"value\":\"registry/development/components/development/metaphor/Chart.yaml\"}],\"artifacts\":[{\"name\":\"repo-source\",\"path\":\"/src\",\"s3\":{\"key\":\"argo-workflows/artifacts/2023/09/19/073bca0e-d574-465a-995d-3e53cec87ebd/metaphor-development-32f8779-65f8z/metaphor-development-32f8779-65f8z-checkout-with-gitops-ssh-2115738426/repo-source.tgz\"}}]},\"outputs\":{\"artifacts\":[{\"name\":\"repo-source\",\"path\":\"/src\"}]},\"metadata\":{},\"script\":{\"name\":\"\",\"image\":\"kubefirst/chubbo:0.2\",\"command\":[\"bash\"],\"workingDir\":\"/src/gitops\",\"resources\":{},\"source\":\"set -e\\necho \\\"setting wrapper Chart.yaml to version: 0.0.1-rc.32f8779\\\"\\nsed -i \\\"s/  version:.*/  version: 0.0.1-rc.32f8779/g\\\" \\\"registry/development/components/development/metaphor/Chart.yaml\\\"\\necho \\\"updated development wrapper chart version to 0.0.1-rc.32f8779\\\"\\n\"},\"archiveLocation\":{\"archiveLogs\":false,\"s3\":{\"endpoint\":\"s3.amazonaws.com\",\"bucket\":\"k1-artifacts-capswancloud-lxwgx5\",\"region\":\"us-east-1\",\"insecure\":false,\"accessKeySecret\":{\"key\":\"accesskey\"},\"secretKeySecret\":{\"key\":\"secretkey\"},\"useSDKCreds\":true,\"encryptionOptions\":{},\"key\":\"argo-workflows/artifacts/2023/09/19/073bca0e-d574-465a-995d-3e53cec87ebd/metaphor-development-32f8779-65f8z/metaphor-development-32f8779-65f8z-set-environment-version-3899486693\"}}}" version="&Version{Version:v3.4.1,BuildDate:2022-10-01T15:03:42Z,GitCommit:0546fef0b096d84c9e3362d2b241614e743ebe97,GitTag:v3.4.1,GitTreeState:clean,GoVersion:go1.18.6,Compiler:gc,Platform:linux/amd64,}"
time="2023-09-19T01:19:47.796Z" level=info msg="Starting deadline monitor"
time="2023-09-19T01:19:49.796Z" level=info msg="Main container completed" error="<nil>"
time="2023-09-19T01:19:49.796Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2023-09-19T01:19:49.796Z" level=info msg="No output parameters"
time="2023-09-19T01:19:49.796Z" level=info msg="Saving output artifacts"
time="2023-09-19T01:19:49.797Z" level=info msg="Staging artifact: repo-source"
time="2023-09-19T01:19:49.797Z" level=info msg="Staging /src from mirrored volume mount /mainctrfs/src"
time="2023-09-19T01:19:49.797Z" level=info msg="Taring /mainctrfs/src"
time="2023-09-19T01:19:49.913Z" level=info msg="archived 293 files/dirs in /mainctrfs/src"
time="2023-09-19T01:19:49.914Z" level=info msg="Successfully staged /src from mirrored volume mount /mainctrfs/src"
time="2023-09-19T01:19:49.914Z" level=info msg="S3 Save path: /tmp/argo/outputs/artifacts/repo-source.tgz, key: argo-workflows/artifacts/2023/09/19/073bca0e-d574-465a-995d-3e53cec87ebd/metaphor-development-32f8779-65f8z/metaphor-development-32f8779-65f8z-set-environment-version-3899486693/repo-source.tgz"
time="2023-09-19T01:19:49.914Z" level=info msg="Creating minio client using AWS SDK credentials"
time="2023-09-19T01:19:50.037Z" level=info msg="Saving file to s3" bucket=k1-artifacts-capswancloud-lxwgx5 endpoint=s3.amazonaws.com key=argo-workflows/artifacts/2023/09/19/073bca0e-d574-465a-995d-3e53cec87ebd/metaphor-development-32f8779-65f8z/metaphor-development-32f8779-65f8z-set-environment-version-3899486693/repo-source.tgz path=/tmp/argo/outputs/artifacts/repo-source.tgz
time="2023-09-19T01:19:50.218Z" level=info msg="Save artifact" artifactName=repo-source duration=304.271429ms error="<nil>" key=argo-workflows/artifacts/2023/09/19/073bca0e-d574-465a-995d-3e53cec87ebd/metaphor-development-32f8779-65f8z/metaphor-development-32f8779-65f8z-set-environment-version-3899486693/repo-source.tgz
time="2023-09-19T01:19:50.218Z" level=info msg="not deleting local artifact" localArtPath=/tmp/argo/outputs/artifacts/repo-source.tgz
time="2023-09-19T01:19:50.218Z" level=info msg="Successfully saved file: /tmp/argo/outputs/artifacts/repo-source.tgz"
time="2023-09-19T01:19:50.226Z" level=info msg="Create workflowtaskresults 403"
time="2023-09-19T01:19:50.226Z" level=warning msg="failed to patch task set, falling back to legacy/insecure pod patch, see https://argoproj.github.io/argo-workflows/workflow-rbac/" error="workflowtaskresults.argoproj.io is forbidden: User \"system:serviceaccount:argo:argo-server\" cannot create resource \"workflowtaskresults\" in API group \"argoproj.io\" in the namespace \"argo\""
time="2023-09-19T01:19:50.252Z" level=info msg="Patch pods 200"
time="2023-09-19T01:19:50.256Z" level=info msg="stopping progress monitor (context done)" error="context canceled"
time="2023-09-19T01:19:50.256Z" level=info msg="Deadline monitor stopped"
time="2023-09-19T01:19:50.257Z" level=info msg="Alloc=8355 TotalAlloc=24180 Sys=22994 NumGC=6 Goroutines=9"

There's an active discussion about this on the Slack community at https://kubefirst.slack.com/archives/C03U34WJ7FW/p1694539096211389

Status update from slack: @Claywd and @johndietz working on this

Status update; blocked pending v2.3.0:

Will test again after https://github.com/kubefirst/kubefirst/pull/1832 is merged

Confirmed Metaphor is working now (tested with kubefirst v2.3.5)
CC: @jarededwards  @fharper @cameronraysmith


Mislabelled

um5-ultramodern-ogl is Ultramodern OGL/SRD (UM5)by Dias Ex Machina Games
Well the one labelled as "Ultramodern OGL/SRD (UM5)by Dias Ex Machina Games" is fvtt-me5e (Mass Effect 5e)

Hi Brent thanks for the input. I have updated the readme specifying that this is a personal use project for foundry version 0.8.x and that if you feel "stolen" of your work I will remove it immediately.


Change from int to double for the input timing parameters to daq.mac

This change is propagated through to use in WCSimWCDigitizer and WCSimWCTrigger
An extension of #188
It'd be worthwhile for someone with a good eye to go through all the files & check if I've missed any int -> double conversions
Standard verification. KS tests are 1

It's kind of hard to see with these plots. Does this PR change the timing behaviour back to the desired shape as shown in https://github.com/WCSim/WCSim/pull/188?

Closing this, since it's unlikely that these parameters (digitiser deadtime/integration window & trigger decision/readout windows) will ever need more than ns precision. They can of course be changed at a later date if required


Revert "libpcap: Add patch to fix instability of SONAME value in bina…

I run a command below without any error.
bitbake libpcap

Thanks!


Support editing HTTP headers

Original author<EMAIL_ADDRESS>(November 15, 2010 22:19:56)
What steps will reproduce the problem?

Find a closed API that requires API key as HTTP header
Oh noes! Can't enter API key.

What is the expected output? What do you see instead?
Happy data. Zilch.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=218

Fixed by #1434


Add delay on process send message telegram

Overview

change name network docker-compose
add delay 60 seconds
add generate File Path

Issue limit bot telegram

Solution
with the limit on the telegram API, the solution is to add a delay when executing queues, seen in the image below, there is a 60 second delay.

cc: @jabardigitalservice/jds-backend
Evidence
title: Menambahkan delay pada saat pengiriman data ke telegram IT Dev Evidence
project: Digiteam
participants: @firmanalamsyah580

the mentioned Telegram Docs said: "the API would not allow more than 30 messages per second", so I think rather than 60 seconds delay, 1 second should be enough. Waiting for 60 second before the message finally being sent is too long in my oppinion. CMIIW

the mentioned Telegram Docs said: "the API would not allow more than 30 messages per second", so I think rather than 60 seconds delay, 1 second should be enough. Waiting for 60 second before the message finally being sent is too long in my oppinion. CMIIW

very good opinion
I also think, that waiting for 1 minute is too long,
thank you very much,
I will change the delay to 1 second :+1: :partying_face:

the mentioned Telegram Docs said: "the API would not allow more than 30 messages per second", so I think rather than 60 seconds delay, 1 second should be enough. Waiting for 60 second before the message finally being sent is too long in my oppinion. CMIIW

oh yeah @azophy  i just remembered, why i put 1 minute because there is a limit from bots can't send more than 20 messages in the same group, maybe i set 20 seconds to prevent bot issues

Gass LGTM !

sepertinya sudah cukup ya review nya,, L.G.T.M 🚀 👍


docker build --pull does not respect insecure registries configuration

Standard docker pull <url> works fine. But building from Dockerfile
FROM <url>
...

using docker build -t my-image --pull . will fail. It is using https instead of http:
[+] Building 0.2s (3/3) FINISHED
 => [internal] load build definition from Dockerfile
 => => transferring dockerfile: 37B
 => [internal] load .dockerignore
 => => transferring context: 2B
 => ERROR [internal] load metadata for <url>
------
 > [internal] load metadata for <url>:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://<url>: http: server gave HTTP response to HTTPS client

It seems like the docker build --pull flag does not respect insecure registries configuration as the docker pull does.
docker version
Client:
 Cloud integration: 1.0.17
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.16.4
 Git commit:        f0df350
 Built:             Wed Jun  2 11:56:22 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc3
  Built:            Wed Jun  2 11:54:58 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.6
  GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc:
  Version:          1.0.0-rc95
  GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  compose: Docker Compose (Docker Inc., v2.0.0-beta.6)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 17
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.10.25-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.64GiB
 Name: docker-desktop
 ID: 643S:D3I5:HOSB:I4OC:XR3J:HGTH:ZPQP:ZLYE:VWII:EBEM:MG5F:65RL
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <url-domain-with-port>
  <IP_ADDRESS>/8
 Live Restore Enabled: false

I think think this issue would be best triaged by https://github.com/docker/cli, it's almost certainly not an issue in distribution.

Moved to https://github.com/docker/cli/issues/3186, thanks

did u solve your problem? i have the same problem and don't know how to fix it...


charge analysis should return ordered list

For the following ranging definition:
Range80=92.7780 93.0240 Vol:0.03115 Mo:2 Color:800080
The algorithm yields correctly two candidates
13354, 12842 but also the pair 12842, 13354

[x] these pairs should be filtered out as when sorted descendingly they are the same molecular ion
[x] if there is only one atom nuclide_hash should still be a 32 array with remaining values nullified and compressed

Range33=187.4800 190.2560 Vol:0.12084 Ce:1 O:3 Color:00FF00 is another example with many such duplicates

Key point is that all candidates found are returned not the relevant only right now, so this is no bug.
The array dimension issue was indeed a bug, both have been fixed with 7b816d7


Exclude node v12 from package engines

Although, it looks like v12 support may have been added already in master, so this PR might be irrelevant now

Node 12 support is coming in the next release as it's already been completed/merged.


Solve reCaptcha with selenium

Hi guys, can we solve reCaptcha in the middle of a selenium process please ?

I think I was scammed. I wish I had read this before.

Yes, both the Chrome extension and Firefox Add-on works with Selenium and all other browser automation tools.
Please refer to the documentation and guide for more information.


Why does YOLONAS use more System RAM when using GPU than CPU?

💡 Question
I was testing object detection using YOLONAS and realized it uses more System RAM when using GPU than CPU.
I tested on a batch of 2 images, using coco pretrained weights, in Google Colab. The rest of the parameters remained constant and I just changed the fuse_model argument in model.predict() from True to False.
The following were the results:

The results were the same when testing on my local machine.
Why is more System RAM used when using GPU than CPU and how I can reduce that?
Thank you in advance :)

I don't have answer for that. Probably investigating allocated memory and comparing living objects between two runs could shed some light on this. However this is not of a high priority and won't be investigated by our team.


Remove hardcoded string length clientside validation check

Hi,
this is for #494
Thank you

Hey @b0 - it looks good, I agree with you.
Thanks 👍


Missing horizontal tick sometimes

Sometimes a horizontal tick is missing:

If you pan left/right it comes in and fades so it seems like it's not removing the right one.

Delivered to master.
The issue was that the logic in GraphRenderer.GetDomainTickData was assuming months were evenly spaced at 30 days each. This causes some offsets between Jan-Feb and months with 31 days next to 30 days where when truncated the ticks will have duplicates at the next month. For example, February only has 28 days most of the time so it will return 2 March 1st points instead of a Feb 1st and a March 1st for some offsets. I replaced this logic and GetUnitBeginning with a section for months specifically and a generic tick calculator for evenly spaced granularities. Years are not supported but if added will have to be special cased as well since they can be unevenly spaced during leap years.
Commit
commit 1d513a03d23049307bd160f6f3d5ba035f6772c9
Author: Alex Hunt<EMAIL_ADDRESS>Date:   Thu May 26 11:54:34 2022 -0400
Issue76: Fixed horizontal tick missing sometimes.

Testing

Check a dataset with month granularity and verify that when zooming/scrolling the following are true:
a) The months are in the right place with respect to the data and hover point
b) The left and right most months fade out
c) No months are missing for any offset when panning
Zoom in further and retest (1) for each granularity level (Days, Hours, Minutes, Seconds)


multiple Notifications

is it possible to make mupltiple notifiactions from an app at the same time...?

add .identifier(uniqueid) for each notification


Appears to Have Issues Uploading Long Tracks

I received a 500 error while attempting to upload Symphony X's "The Odyssey" which is a 24 minute song.

An additional note - this puts the file size at ~55.5 MB.

Hi. According to YouTube Music, the max file size is 300MB. So you shouldn't really have an issue uploading the 24 minute song? Please can you put the track here and I'll certainly have a look for you: https://1drv.ms/u/s!At6EvCXZJAN6zOl9uVwUrwG6xUidHw?e=1WDJWb
Thanks for reporting the issue, much appreciated!

@jamesbrindle I assumed it was the file size, but the file uploaded successfully the next time it was attempted. This issue can be closed.


refactor(doctor): Clean up Dead Stuff

Was looking at the code and figured I'd run the standard clean-up stuff.

Deleted commented-out code

Thanks


feat: add table_id to datanode heartbeat

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?

Add table_id to Datanode heartbeat

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
close #1566

PTAL @evenyag


Scores file overwritten

Scores are stored in two different locations which are mapped in the code. The difference between these is not known, but two CSV files should be made for them. The code currently writes one, then overwrites it with the other.
These may be two different locations to store local and networked times, more testing will be needed to determine this.

Solved, the two data blocks alternate writing to ensure one is valid if the machine is shut off while writing to the HDD. One will be newer but even when writing race times the game writes so much audit data the difference between the two is minimal. A --block parameter has been added to the tool to allow choosing which block to work if the user wants to pick one.


Train-Accuracy decrease to 0

when learning_rate = 0.0001 after batch 1300 Train-Accuracy=0.000000.
did you change something？

Thanks


Explain relationship to hyperHTML/viperHTML etc

hyperHTML seems very similar, could a FAQ explain the difference?
https://viperhtml.js.org/

hyperHTML seems very similar

to be honest, this looks like a half baked clone of hyperHTML and I'm surprised there was no mention whatsoever to such library, or its author, that I think "inspired" 90% of this project ... anyway ...
viperHTML is a NodeJS backend version of hyperHTML, I think it's hard to standardize the pattern in a way that's useful for both worlds, so I'm curious to know more the following:

Also, we're keeping in mind potential standardization of the two main phases in lit-html: HTML-in-JS parsing of templates (Similar to E4H) and what's been called "template parts" (the ability to set the content of "holes" in cloned template instances).

With @marcoscaceres we were also thinking about possible standardization so it'd be great if someone would talk to us, since we've used this pattern for the last 6 months already.
Comparison so far
It's clear this project is still a work in progress but if somebody would like to know differences as of today with hyperHTML only, 'cause it cannot be compared with viperHTML at this point, these are the main things I've figured out going through the code:

it's not as cross browser as hyperHTML is. There are clear choices in the design that require un-polyfillable features such Symbols while hyperHTML works on IE9 and old Mobile Browsers just transpiling the template literal bit, which is technically the only thing that needs to be transpiled, if needed, and Babel does a very good job there
also partial layouts seems to be missing. Try to use htmlnope	 on browsers that don't support template and you'll see empty holes in tables
it doesn't let you inject html if needed. Only textContent can be used, you need third parts extension to create basic lists or you need a render function per each single template. This can be a limit, it was a limit for me when using highlightjs for code examples
it doesn't fully understand attributes. It uses only setAttribute which might not produce the desired behavior if the attribute is inherited and/or boolean. You cannot <button disabled="${isDisabled}"> as example, so it's half useful with forms and other cases with special attributes
it apparently supports partial attributes, which is intentionally not supported in hyperHTML because it's slower, performance wise, and it gives false idea that an attribute can be partially updated. On top of that, it confuses more 'cause attributes must be in quotes and stuff like this wouldn't look right  ... imo, a bit eyes-hurting
events are not supported so creating components isn't straight forward as it is for React and hyperHTML, you need extensions for standard events like an onclick too. With hyperHTML events are always DOM Level 3 with auto removal when changed or nullified and no conflict with DOM Level 0. You own the template, you own the events.

About extensions
Usage of extensions here is a very nice idea but it also means developers need to learn something else beside the rules to create valid templates and the signature to render them.
One of the main hyperHTML goal was not to ask to learn anything new.
Technically you just bind it to a DOM context and you start injecting templates with data.
Arrays are resolved, so are DOM nodes, text, and Promises so that all the extensions here work already out of the box.
Once hooked within the main parsing logic performance also could be affected, yet I think this is something missing that I might borrow, using a different implementation, in the near future.
As Summary
If anyone would like to ask or know more about how things are different or why, I'd be happy to provide as many details as needed.
If somebody pushing standards would like to ask the opinion of people already producing Web products with this pattern, that'd be a good way to collaborate.
Best Regards

to be honest, this looks like a half baked clone of hyperHTML and I'm surprised there was no mention whatsoever to such library, or its author, that I think "inspired" 90% of this project ... anyway ...

Well, like I said comparisons are tricky. As for the genesis of lit-html, if it seems like a clone, that's unfortunate, because it's honestly not, but in the realm of open source software and especially DOM creation libraries, there are hundreds of variations on very similar ideas.
For sure, there are a lot of template literals libraries, though hyperHTML seems the most similar to lit-html. I didn't know a whole lot about how hyperHTML worked when I started, because I looked over a bunch of similar ideas (bel, t7, hyperx, E4H, a lot of abandoned libraries on npm...), and honestly, the readme for hyperHTML was very hard for me to understand, so I didn't dig very deeply on it. At a cursory glance, it didn't seem like anything did exactly what I wanted to do. I didn't know that hyperHTML used template elements under the hood, for instance, when I started lit but I'm happy to see that there are now two libraries that do that.
I think we need multiple attempts to hone these ideas. I like to think that we're creating an easy to understand and simple API, in a small and fast library, and that the best of the individual ideas contained within the libraries out there will flourish. Maybe another one will come along soon too. For now, I want to see how good I can make lit-html itself.
As for specific comparisons, I have a few responses:

it's not as cross browser as hyperHTML is. There are clear choices in the design that require un-polyfillable features such Symbols while hyperHTML works on IE9 and old Mobile Browsers just transpiling the template literal bit, which is technically the only thing that needs to be transpiled, if needed, and Babel does a very good job there

We only use Symbols for detecting Iterables, and they're trivially polyfillable for that purpose. We've yet to stress lit-html through all the environments we will eventually support, through we'll probably focus on the same support matrix that Polymer has, which doesn't include IE9.

also partial layouts seems to be missing. Try to use htmlnope on browsers that don't support template and you'll see empty holes in tables

We will definitely have to test this...

it doesn't let you inject html if needed. Only textContent can be used

This is a feature - we get some protection against XSS this way. Many other libraries make you go out of your way to bind to HTML, ie React's dangerouslySetInnerHTML. But you can interpolate nodes easily:
const div = document.createElement('div');
div.innerHTML = 'hi';
html`${div}`;

you need third parts extension to create basic lists or you need a render function per each single template. This can be a limit, it was a limit for me when using highlightjs for code examples

I'm not sure what you're saying here. Arrays and Iterables are supported out-of-the-box, and the repeat directive gives keyed node reuse.

it doesn't fully understand attributes. It uses only setAttribute which might not produce the desired behavior if the attribute is inherited and/or boolean. You cannot  as example, so it's half useful with forms and other cases with special attributes

lit-html doesn't have any whitelists and it's likely to stay that way. For boolean attributes we can have a toggle directive:
html`<div hidden=${toggle(someBool)}></div>`

it apparently supports partial attributes, which is intentionally not supported in hyperHTML because it's slower, performance wise, and it gives false idea that an attribute can be partially updated. On top of that, it confuses more 'cause attributes must be in quotes and stuff like this wouldn't look right  ... imo, a bit eyes-hurting

That's a fine choice for hyperHTML to make. We've made a different one. Attributes don't need to be included in quotes in lit-html, this works fine:
html`<input value=${v}></input>`

events are not supported so creating components isn't straight forward as it is for React and hyperHTML, you need extensions for standard events like an onclick too.

Events and properties are supported in lit-extended. The core of lit-html only supports very unopinionated features, so only attributes and text node.

Usage of extensions here is a very nice idea but it also means developers need to learn something else beside the rules to create valid templates and the signature to render them.

This is a choice too. When we look at what could be standardized, support for setting properties, or declarative event handlers seems less likely than just attributes, text and a powerful extension point. Proving that extensions can handle use-cases like this is quite important then.
The shape of the extension points in lit comes out of a previous conversation on template extensions we've had: https://github.com/whatwg/html/issues/2254
I suspect that most developers wouldn't need to use something like lit-extended directly, but will use a component base-class that integrated extensions for them.

Arrays are resolved, so are DOM nodes, text, and Promises so that all the extensions here work already out of the box.

All those features are built into lit-html core as well.

Attributes don't need to be included in quotes in lit-html

Gotta test if IE would accept attr={{}} and I also wonder how are you dealing with SVGs which don't seem to be supported as well, another difference I forgot to mention.
Here thousands of SVGs as demo.
More on unquoted attributes, would the following produce a className==="a b" ?:

All those features are built into lit-html core as well.

Sort-of. You need directive, which I'm not sure I understand are a global scope pollution or a module one, but you need to use them to have these behaviors.
In hyperHTML if it's an iterable, you don't need to specify it's an iterable, you just let hyperHTML realize how to deal with the iterable.

I didn't know that hyperHTML used template elements under the hood, for instance

The initial post is on the 5th of March. .Net magazine published a whole article about hyperHTML and it's been the fastest HNPWA since the beginning, the only Polymer competitor.
I trust you didn't know much about it, but it's honestly quite hard to believe. I do agree on one point thought:

I think we need multiple attempts to hone these ideas. I like to think that we're creating an easy to understand and simple API, in a small and fast library, and that the best of the individual ideas contained within the libraries out there will flourish.

Yes, it is nice to have multiple takes and maybe trash all our work in favor of a standard candidate but that's also exactly what didn't sound great to me: 'cause you're at Google you have easier way to push standards and yet after me clarifying to you what was hyperHTML more than a month ago, you never even asked me a question about it but you wrote on the README that you are planning to standardize "your" lit ideas.
This was the thing that wasn't not cool at all Justin, the rest is just fine.

FYI I am updating this post with differences that I've previously forgotten.
https://github.com/PolymerLabs/lit-html/issues/32#issuecomment-320800997
I've also opened a discussion in hyperHTML repository about ideas that might be adopted by hyperHTML too.
https://github.com/WebReflection/hyperHTML/issues/79

I'm not sure how productive continuing this discussion will be, but there are some inaccuracies about lit-html I wanted to correct.

Attributes don't need to be included in quotes in lit-html

Gotta test if IE would accept attr={{}}

That works fine in IE11

More on unquoted attributes, would the following produce a className==="a b" ?:

Nope. If you wanted that you would need quotes:
. Quotes are optional in many cases, needed in others, much the same as HTML.

All those features are built into lit-html core as well.

Sort-of. You need directive

No. Nodes, nested templates, iterables, Promises are all handled in lit core. You can see some example tests here: https://github.com/PolymerLabs/lit-html/blob/master/src/test/lit-html_test.ts#L130 and https://github.com/PolymerLabs/lit-html/blob/master/src/test/lit-html_test.ts#L163 and https://github.com/PolymerLabs/lit-html/blob/master/src/test/lit-html_test.ts#L223

In hyperHTML if it's an iterable, you don't need to specify it's an iterable, you just let hyperHTML realize how to deal with the iterable.

Same with lit-html

Yes, it is nice to have multiple takes and maybe trash all our work in favor of a standard candidate but that's also exactly what didn't sound great to me: 'cause you're at Google you have easier way to push standards and yet after me clarifying to you what was hyperHTML more than a month ago, you never even asked me a question about it but you wrote on the README that you are planning to standardize "your" lit ideas.

This was the thing that wasn't cool at all Justin, the rest is fine.

I might have a little easier access to some people who write standards, but all I'm doing here is thinking of how to limit and layer lit-html so that some concepts might be more likely to be acceptable to standards committees. I'm just thinking ahead. That's why property setting, declarative event handling, and node recycling aren't in core - because they represent opinions that I'm betting would cause too much disagreement in a standards setting. The start of lit-html came from us discussing https://github.com/whatwg/html/issues/2254 in the context of JS and HTML modules, so that's obviously something I kept in mind when designing the layering.
I'm not trying to claim ownership of the ideas here, or saying that "mine" need to be standardized. I'm simply using the (pretty small, really) experience I've had with some of the standards people to try to predict what minimal feature set(s) would be amenable to standardization. That why there's the focus on extensibility.
Also note, that the idea of putting placeholders in a template a pulling them out into parts is not new. Polymer core has essentially worked this way for years. We also discussed it in 2254 and Ryosuke Niwa from Apple implemented a sketch in January: https://bug-167135-attachments.webkit.org/attachment.cgi?id=299053 And of course using JS template literals to produce HTML is not new, there have been libraries doing that for years. So it shouldn't be surprising that the two ideas are combined, and by more than one person.
I wasn't quite aware how similar hyperHTML was to what I started building at the beginning, but I'm not I would have or should have stopped if I did, or if that would have been better for anyone. lit-html and hyperHTML for all their similarities do some things very differently, and have some different capabilities and APIs. Those wouldn't have been uncovered if I hadn't worked on this.

P.S. Symbols are not possible to polyfill and you cannot partially polyfill them or all other libraries testing typeof Symbol will have issues. Same for WeakMaps. The old polyfill used by Polymer has always been problematic on objects deep cloning, as example.

The only this we use Symbols for is testing whether an object is an iterable. If Symbols don't exist, then neither do iterables.

I'm not sure how productive continuing this discussion will be

It is, it's a comparison between two developers reaching similar solution, right?

That works fine in IE11

Yeah, tested already in IE9 too. Although, hyperHTML uses less predictable output.
What's the plan to enable text like {{}} inside a pre content, as example?
I'm wondering it that's just a placeholder that needs a more unique name in the near future.

No. Nodes, nested templates, iterables, Promises are all handled in lit core.

I need to read more but then, because if that's the case, I don't understand what's a repeat() about.
I'm also not sure if same list of objects will trash previous layout when a .push({new:"object"}) happens or not. Just curious, with hyperHTML you can wire objects to specific templates too.

I might have a little easier access to some people who write standards

That's a very humble statement. Truth is, you work at Google, so you are already a potential TC39 contributor by default and influential to the Web thanks to  WHATWG which many of your colleagues in it.
Meanwhile, I'm doubling-down on Open Source these days, meaning that instead of receiving any kind of help or hint from a big interested player, I now have to compete with it: Google Polymer lab and full-time Google payed engineers bring it on !!!
As long as it's fair ... becaue putting a "we're going to standardize this" in the README, for a thing practically not even ready for production, was a very good move to kill any other attempt around template literals to make it even better attempts than lit-html implementation, isn't it?

The start of lit-html came from us ...

To be honest, that discussion looks more like like mustache templates to me.
The first comment about using template literals comes after my March post on hyperHTML and not before June there's interest on the JS looking template proposal.

I'm simply using the (pretty small, really) experience I've had with some of the standards people to try to predict what minimal feature set(s) would be amenable to standardization.

That's great. Although, are you talking with non googlers that used "your idea" before you created this repository?

focus on extensibility

I've proposed extensibility without needing scope pollution, and only thanks to this alternative project so competition does good things anyway.

We also discussed it in 2254 and Ryosuke Niwa from Apple implemented a sketch in January

I am part of few Web related W3C working groups and nothing like this came to my inbox.
What's discussed in there is not about unique template literals behavior, which was the real and only opened door for both hyperHTML and lit-html: that list of statics you can check on a Map is awesome, isn't it?
That's the real key to this pattern, and I'm sure we had a quite possibly a very similar "A-HA" moment there.

Those wouldn't have been uncovered if I hadn't worked on this.

Very true, the standardizing bit is still not as fair as your other statements.

If Symbols don't exist, then neither do iterables.

Array existed before Symbols, but again ... I am talking about compatibility.
You stated lit-html targets are the same of Polymer, I've decided to reach every other too.
Anyway, to stop this conversation, if you like, I just hope after me explaining hyperHTML to you the 29th of June, the day you created later on this repository, a mention to a 6 months older alternative based on exact same solution would've found a place in your README.
Regardless, lit-html will find place on my documentation once ready, don't doubt about that.
Best Regards
P.S. Next up: HyperHTMLElement class with observedAttributes magic.

That's why property setting, declarative event handling, and node recycling aren't in core - because they represent opinions that I'm betting would cause too much disagreement in a standards setting.

Just re that, I think property setting should be reconsidered for core. I have a few reasons for this.
Firstly, properties give you the ability to interleave complex data types. Though attributes are closer to "HTML", properties generally reflect to attributes, and can quite simply within the context of a custom element. There's use cases for only setting attributes, so I can see why this would be contentious. Maybe there's a happy path here. I'd very much like to see a way to pass around complex data types, declaratively using standard native platform APIs. This brings me to my second point.
The second point is less technical, but more political (for better or worse). Two of the biggest complaints I've seen against "the platform" (and conflated with a solution web components should provide) from other communities (namely React) are:

No way to declaratively pass around data structs in HTML (see above)
No vDOM / JSX (thought JSX would be contentious in itself, lit-html encapsulates that into something that is less contentious because it's using literals)

I think there's potential for a lot of buy in from other communities if a case can be made for them, so, FWIW, I think it's worth reconsidering, or at the very least, discussing. Happy to do it offline, or in another issue.
/2c

Firstly, properties give you the ability to interleave complex data types

Not only. <input value="${data}"> cannot be set through setAttribute once data changes.
document.body.innerHTML = '<input value="1">';
// type manually 2 in the input
document.body.firstChild.setAttribute('value', '3');
// see that input still has 2

This is solved in hyperHTML thanks to smarter property management, so if lit proposes to standardize this setAttribute only based proposal, the proposal itself will be very less useful than it could be.
Boolean for attributes such disabled, deferred, async, or attributes without values such download are also cut out from this implementation.
On top of that, having setAttribute as general mechanism means that onclick, which is just an attribute, will set the listener as string destroying completely its meaning.

No way to declaratively pass around data structs in HTML

This one itself would probably be a hell of a change and historically the best attempts to do that were dataset, as form of data-name serializable content, still a string, and detail in the CustomEvent specification, the only property that accepts and transports any data, even unserializable (but not cross realm).
I don't think it's a template role to define such mechanism, so probably this specific request is out of scope, unless a special meaning to

 is used (for which I'd say "why not", thinking about an ondata listener too)
/2c

@treshugart I think this is better discussed in another issue.

👍 no worries. Thought I was clear about that :)

To whoever is/was interested, I've written down the current-status comparison (and filed 3 bugs while doing so)
https://gist.github.com/WebReflection/fadcc419f5ccaae92bc167d8ff5c611b
I'll try to keep it updated as I can. If there's anything missing, ping me.


Creating a custom module

Hello,
This is most likely a question and not an issue; however I'm posting it here because I don't know where else to.
I am trying to create a custom waybar module to display whether or not my Yubikey needs to be touched or not.
I created a program which outputs json depending on the state of the yubikey—either
{"text": "","percentage": 0,"class":"active"}

if it needs attention; or
{"text": "","percentage": 0,"class":"inactive"}

if it does not.
It does this in a constant polling fashion so it is always running.
The relevant portion of my config is as follows
    "custom/yubikey": {
        "interval": "once",
        "return-type": "json",
        "exec": "~/.config/waybar/modules/touch",
        "format": "{icon}",
        "format-icons": ["<key icon>"],
        "escape": true
    }

and I wish to theme it such that #custom-yubikey-inactive is invisible while custom-yubikey-active is blinking or high res.
However, at the moment currently nothing shows up. Even if the program outputs json the module never appears. I am currently styling #custom-yubikey as every other module, so I'm not quite sure what is wrong.

Probably not the only problem, but I think that you probably don't want to set interval to once, if it is continuously running.

When text is empty the module will not show anything...

When text is empty the module will not show anything...

Do you mean text inside json which were generated by a script?

#custom-yubikey-inactive

According to  waybar-custom (5) man page, style should be in format #custom-<name>.<class>

So if the text is empty the module will not show, even if there is content in the format area?
Also I am running this script with once as it remains in the background and should not be started multiple times.

@4e554c4c FYI in case you are still looking into creating a Yubikey module, and in case you are using yubikey-touch-detector, here's how I did it, works really well with waybar:
https://github.com/maximbaz/dotfiles/blob/master/bin/waybar-yubikey
"custom/yubikey": {
    "exec": "waybar-yubikey",
    "return-type": "json"
},


Add bieniu/ha-shellies-discovery to default repo

@bieniu could you add that change to this file instead?
https://github.com/custom-components/hacs/blob/data/repositories/python_script

Of course, done.


5.6 regression: Inference related regression: should prefer named type rather than inferred generic type

🔎 Search Terms
Inference
🕗 Version & Regression Information

This changed between versions 5.5.4 and 5.6.0-beta (still happening in 5.6.1-rc)

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.6.1-rc#code/JYOwLgpgTgZghgYwgAgGIHt3IN4ChnJgCeADhAFzIDkMmVA3PsuiWMOiHADYAKULAfkoAjTFwhwQjAL65cxMsgDCHAM4BXALbQAPEwD0+5KGbqwyQ8gCqIBOk3bwoAOanzYABbBVyLqBQARDDAAB4QqgGEHijeGhAAdEwAKrgAfMgAvMgAFHBQzpRJAJSZ6QBu6MAAJoy4VRAIXHkoMOq2bBzIqvYQqG0IOikEECGQIFU+GFiWKg4QTiCu6GZR3r7+yEGh4ZGeMapxianZTHYgGtpQlCrnWrpJqQA0TPXw6lxgSYXPRYW19Y1msgzqpzLR0DcLtBrmo7lAdFNUvRkHIQeYoOF3uYst1tH1bNlwZC4Y8cAoKNRwVRpEVGJYCMgAHoCXBAA
💻 Code
interface Foo {
  type: 'foo';
  optionalProp?: boolean;
}

type Consumer<
  // in out // Uncommenting out this line "fixes" the issue.
  T
> = (arg: T) => void;

declare function someFunc<T
  extends Foo // Commenting out this line "fixes" the issue.
>(
  consumer: Consumer<T>,
  defaultT: T,
): T;

declare const fooConsumer: Consumer<Foo>;

const result = someFunc(fooConsumer, {type: 'foo'});
//    ^?

🙁 Actual behavior
result is of type { type: "foo"; }
🙂 Expected behavior
result is of type Foo as it was in previous releases
Additional information about the issue
See the comments in the example code for two tweaks to make for the code to work as expected. I get adding in out changing things. I'm less clear on why removing the extends should make any difference.
(Google note: relevant source location http://shortn/_eCS9djFiAR)

To be clear, this is a real builder error observed in Google that has been boiled down to a minimal reproduction with changed names.

Confirmed that https://github.com/microsoft/TypeScript/pull/59709 does not resolve this issue.

This seems correct? Let's say you wrote this:
interface Foo {
  type: 'foo';
  optionalProp?: boolean;
}

type Consumer<T> = (arg: T) => void;

declare function someFunc<T extends Foo>(consumer: Consumer<T>, defaultT: T): T;

declare const fooConsumer: Consumer<Foo>;

const result = someFunc(fooConsumer, { type: 'foo', extra: "bar" });
result.extra; // should be OK!

So I have at least three more classes of similar regressions to this we're seeing in Google that I need to investigate and then create simplified repros.
My Consumer name was bad. Here's the real code with names changed to make it a little less clear on what you might infer to be the correct behavior:
function functionName<C extends SomeUnionOfTypes>(
  arg1: Map<SomeType, AnotherType<YetAnotherType<C>>>,
  arg2: C,
  arg3: SomeType,
  arg4: unknown,
): C

Looking at this, it's less clear if we should prefer the literal type of C as extracted from arg1 or arg2.
The behavior has changed though which is causing new regressions.

I was about to log a bug for this last largest class but, thinking about it more, I believe it boils down to this bug as well.
Here's the example:
declare class TestEnvironment<Args> {
    constructor(template?: (args: Args) => Element, defaultTemplateData?: Args);
    render(data?: Args): void;
}

declare function myElRender(data: MyRenderParams): Element;

type MyRenderParams = {
    state: State,
    optBool?: boolean,
};

enum State {
    OPEN,
    CLOSE,
}

const env = new TestEnvironment(myElRender, {state: State.OPEN});

function doTheRender({
  state = State.OPEN,
  optBool = false,
}: {state?: State, optBool?: boolean} = {}) {
  env.render({state, optBool});
}

Or, as a TS Playground:
https://www.typescriptlang.org/play/?ts=5.6.1-rc#code/CYUwxgNghgTiAEkoGdnwComQFwKIDsA3ASxgHt8BbEfbAHgEEYBzZAPngG8AoePxCjhgBXMNjIwAFNhCUADtBkB+AFzxJsVmqasAlPAC8HXBFk1sAGnigAZlGERsmeYpAARKNiir4O5LoBuXn44fFApYE9vbRZ-NUIyYmAggF9ublAkOHgbYXwxYgp4SgBPEwAlGnDJSK81AFkSyrCQGAAFWChKOPgTM1og7mwSuQRG5vCOmC60Ay5gvhxPEDUAZS8ZCwX4MjlsACEyMggfACMj0yh8LZTBmmFKeHXl+f54AHk23AA5LbeAYQAMu9VrgbuluGBBNh4DRCIZ4PgQAB3DBYPBEUgUai0SSlCpVVpWThLGRrDYgAB0nx+KUC6Vy+WwhXw1jI6AAFiAJq1JDxFhSEc8ZNSvr9grsDhcEXYIMgQDc1CSKT5hQqdntDsczhcQFcUgjOHTXrCiJTQtVlcsrJKtRA6aluEA
TestEnvironment is inferring the type of Args as {state: State} instead of MyRenderParams as it previously did.

From the sample runs I performed, I detected 26 different tests failing this same way.
This particular pattern impacts thousands of our tests in the Google codebase so is more important.
If you feel this is significantly different, I can log a separate issue for this regression.

TestEnvironment as written just needs some help if the intended contract is that the template argument is the sole determinant of Args. This inference in both 5.5 and 5.6 doesn't match what you want to happen in cases where you pass optBool to defaultTemplateData
declare class TestEnvironment<Args> {
    constructor(template?: (args: Args) => Element, defaultTemplateData?: Args);
    render(data?: Args): void;
}

declare function myElRender(data: MyRenderParams): Element;

type MyRenderParams = {
    state: State,
    optBool?: boolean,
};

enum State {
    OPEN,
    CLOSE,
}

function f1() {
  const env = new TestEnvironment(myElRender, {state: State.OPEN});
  // OK
  env.render({ state: State.OPEN });
}

function f2() {
  const env = new TestEnvironment(myElRender, {state: State.OPEN, optBool: true});
  // optBool is required now??
  env.render({ state: State.OPEN });
}

This is a very good situation for using NoInfer, which fixes it in both cases and clarifies which argument the inference is supposed to happen from
    , defaultTemplateData?: NoInfer<Args>

I understand that I can rewrite code to make it compile with the new inference changes. I'm not sure that we should have to though.
My concern is that large swaths of pre-existing TypeScript is just going to stop compiling correctly around the world in this version. If that's okay, then okay.
For this particular case on our end, it's a little tricky because the TestEnvironment class is written in JavaScript, not TypeScript. I need to test how much I can influence the generated type declarations in this case.

Note that the title of this issue is a little bit misguided. Both of those types are inferred here internally. The fact that one of them was "named" was always irrelevant. It's all about the algorithm that chooses the covariant vs contravariant inference candidates to be selected as the final inferred type.

Note that the title of this issue is a little bit misguided. Both of those types are inferred here internally. The fact that one of them was "named" was always irrelevant. It's all about the algorithm that chooses the covariant vs contravariant inference candidates to be selected as the final inferred type.

I'm happy to change the title. Can you suggest a more accurate one?

Wider covariant inference gets picked over more narrow contravariant one

My concern is that large swaths of pre-existing TypeScript is just going to stop compiling correctly around the world in this version. If that's okay, then okay.

The available data we have is that this isn't going to be a disruptive change. The expected number of inference changes between versions isn't zero. The behavior change here is basically a "bug fix" in other contexts and it's expected to see similar-looking cases have similar-looking changes.

The available data we have is that this isn't going to be a disruptive change. The expected number of inference changes between versions isn't zero. The behavior change here is basically a "bug fix" in other contexts and it's expected to see similar-looking cases have similar-looking changes.

OK. That's good to see. I'm familiar with the tools to resolve these issues on our end (NoInfer + multiple template params where one extends the other) so I can make updates.
Thanks for being patient with me as I log these regressions. Still getting a feel for this process :)


Where Can I find documentation

I cannot find any form of documentation for neither this fork, or the original vte4-rs
Where can I find them?
https://malureau.pages.gitlab.gnome.org/vte4-rs/stable/latest/docs/vte4
Has been down for over 5 months

Hi!
Unfortunately I did not find any documentations either, I just hacked my way through it. Since I was hoping that the original project in the GNOME repository would be updated, I did not focus much on doign things the right way either :(

Hi!
Unfortunately I did not find any documentations either, I just hacked my way through it. Since I was hoping that the original project in the GNOME repository to be updated, I did not focus much on doign things the right way either :(

Can you give an example code snippet of spawing a vte
I'll find a way to make work of just that eventually
:(

This seems to be the issue on why we don't have docs
https://docs.rs/crate/vte4/latest
And it's 2 open issues on their gitlab, but gnome isn't responding to them for over 5 month
Maybe this project can fix the docs.rs build issue

This seems to be the issue on why we don't have docs
https://docs.rs/crate/vte4/latest
And it's 2 open issues on their gitlab, but gnome isn't responding to them for over 5 month
Maybe this project can fix the docs.rs build issue

Build logs show that this is just dependencies not being installed
I think it's easy AF to fix they just don't wanna do it

I think there's little interest in VTE for rust right now, hence no support or maintenance.

Please have a look at https://github.com/hkoosha/zoha4, specially this line:
The trick is to call spawn_async() on a VTE struct, else you'll get a blank terminal. Took me a while to figure this out. Please note the async has nothing to do with rust's async support, it just C stuff, expecting a callback fn.

<3

I have submitted a fix MR to vte4-rs let's hope the gnome isn't lazy enough to not accept a free fix
https://gitlab.gnome.org/World/Rust/vte4-rs/-/merge_requests/5


TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))

sudo npm install -g chrome-webstore-upload-cli

added 37 packages in 5s

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

dave@dave-pc:~/src/docker-media-center/config/sodarr-chrome-plugin/chrome-plugin$ npm list -g chrome-webstore-upload
/usr/local/lib
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
$ chrome-webstore-upload upload --source ../chrome-extension.zip --extension-id ........ --client-id ......... --client-secret ........ --refresh-token ...... --auto-publish
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at handlePublishStatus (file:///usr/local/lib/node_modules/chrome-webstore-upload-cli/util.js:8:27)
    at doAutoPublish (file:///usr/local/lib/node_modules/chrome-webstore-upload-cli/cli.js:90:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async init (file:///usr/local/lib/node_modules/chrome-webstore-upload-cli/cli.js:167:9)
    at async file:///usr/local/lib/node_modules/chrome-webstore-upload-cli/cli.js:176:5

Are you using Node 18+?
Also you don't need to install chrome-webstore-upload if you use the cli version

So I think this is because the publishing is failing, but I don't handle the response correctly. It looks like status isn't set, but something like error will be.
Can you add a console.log(publishResponse) in cli.js in your global node_modules? I'd like to see what the response looks like and what the error is.

I'm running into this one as well on GitHub actions. https://github.com/kj800x/nulinks/actions/runs/7505963707/job/20436589755

Here's the log I'm getting after logging out publishResponse. Hopefully it helps! I'm gonna go dig into the mess that is the GCP website to see if I can fix my issue.
./node_modules/.bin/chrome-webstore-upload upload --source nulinks-extension.zip --extension-id gfbdcgkehhkgfehdilpmldkeihiojjak --auto-publish
⠴ Publishing{
  error: {
    code: 400,
    message: 'Publish condition not met: You must verify your contact email before you can publish any item. Begin the verification process on the Account tab.',
    errors: [ [Object] ]
  }
}
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at handlePublishStatus (file:///Users/kjohnson/testing/node_modules/chrome-webstore-upload-cli/util.js:8:27)
    at doAutoPublish (file:///Users/kjohnson/testing/node_modules/chrome-webstore-upload-cli/cli.js:93:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async init (file:///Users/kjohnson/testing/node_modules/chrome-webstore-upload-cli/cli.js:170:9)
    at async file:///Users/kjohnson/testing/node_modules/chrome-webstore-upload-cli/cli.js:179:5
    ```

Oh and here's publishResponse.error.errors in case that's helpful too:
[
  {
    message: 'Publish condition not met: You must verify your contact email before you can publish any item. Begin the verification process on the Account tab.',
    domain: 'chromewebstore.access',
    reason: 'badRequest'
  }
]

Thank you! So yeah the error is due to the store, but the module isn't displaying it properly.
PR welcome to fix it.

As for the API error, you do need to take action in your own Dashboard, it's not something related to the uploader.

I see what happened. In the latest version I started using fetch instead of got. Everything works, except that got used to throw on non-200 HTTP responses, while fetch does not.

This is fixed in the current version.
https://github.com/fregante/chrome-webstore-upload/releases/tag/v3.0.3
If you installed chrome-webstore-upload-cli locally:
npm rm chrome-webstore-upload-cli chrome-webstore-upload
npm i chrome-webstore-upload-cli

If you installed chrome-webstore-upload-cli globally:
npm rm -g chrome-webstore-upload-cli chrome-webstore-upload
npm i -g chrome-webstore-upload-cli

If you're running it with npx:
npx clear-npx-cache
npx chrome-webstore-upload-cli