Icon Code for CSS Table datatable.js

Hello i need for my css for datatable.js the content for the icon
chevron-up
chevron-down
sort-up
sort-down
Example
content: "\ea4f";

@scheugma you need to encode the SVG before you can use it as a bg-image using url(). Check this site to encode SVGs for multiple uses: https://yoksel.github.io/url-encoder/


Data will now be filtered each time add_link is called, even if the f…

…iltered key already exists. This is for ease of use.

:+1:

:+1:


Idea: shouldFilter per Group/Item

I have some items which I'm fetching from TypeSense and don't need filtering. Others are statically-defined. It would be useful to define shouldFilter at the Item/Group level, rather than only the parent. I believe cmdk is built in a way where this would be possible, but I haven't peaked at the source in a while, so I'm not totally sure. Figured I'd mention it!

One way around this I found, is to use the searchFilter prop and assign something common to the <Command.Group> value prop to ensure that these items dont get filtered like so:
<Command
     filter={(value, search) => {
       if (value.includes(search) || value.includes("doNotFilter-")) return 1; // ensures items arent filtered
       return 0;
     }}
>
   <Command.Group>
      {unfilteredItem.map((item) => (
         <Command.Item value={`doNotFilter-${item.name}`} />
      )}
   </Command.Group>
   <Command.Group>
      {filtered.map((item) => (
         <Command.Item value={item.name} />
      )}
   </Command.Group>
</Command>

I've also ran into a very similar use case to you, where my command consists of static data, such as links to pages, but also has dynamic data which has been fetching and searched via an API.
For example:
const Page = () => {
  const [searchTerm, setSearchTerm] = React.useState<string>('');

  const { data: itemsA } = useSearchItemsA({
    query: {
      search: searchTerm,
    },
    enabled: !!searchTerm,
  });

  const { data: itemsB } = useSearchItemsB({
    query: {
      search: searchTerm,
    },
    enabled: !!searchTerm,
  });

  return (
    <div>
      <Command>
        <Command.Input placeholder="Search…" onValueChange={setSearchTerm} />
        <Command.List>
          <Command.Empty>No results.</Command.Empty>
          <Command.Group heading="Links">
            <Command.Item>Link A</Command.Item>
            <Command.Item>Link B</Command.Item>
            <Command.Item>Link C</Command.Item>
          </Command.Group>

          {/* This data has already been filtered by an external source, do not apply additional filtering */}
          <Command.Group heading="Items A">
            {itemsA.map((item) => (
              <Command.Item key={item.id}>{item.name}</Command.Item>
            ))}
          </Command.Group>

          {/* This data has already been filtered by an external source, do not apply additional filtering */}
          <Command.Group heading="Items B">
            {itemsB.map((item) => (
              <Command.Item key={item.id}>{item.name}</Command.Item>
            ))}
          </Command.Group>
        </Command.List>
      </Command>
    </div>
  );
};

I've opened a PR, which adds shouldFilter to the Command.Item component so these items can be skipped during any filtering.


Shutdown time slowed with recent compiler changes

Previously there was an error on shutdown (issue #296), but that was resolved. Even before that error was fixed, the shutdown process has shown to take much longer than usual. It started from the recent streaming compiler changes. Shutdown now takes anywhere from 2000ms to 22000ms or more. @Nogrod

Fixed in PR #333.


added cloudflare acme support

I just tested acme with cloudflare. thought to update the README in case anyone else wants to do the same.
thanks for your work!
fixes #396

Thanks for the contribution!
Unfortunately, I don’t have a domain that is managed by Cloudflare, so I can’t really test if this works properly myself.
Every time the AWX Operator and Cert Manager versions change, I actually run and test most of my documentation, so the issue of not being able to test by myself will keep coming up while I’m maintaining this repository.
Honestly, I'm a bit hesitant about keeping the documentation up to date for environments I don’t use. I might consider merging this PR if I start using Cloudflare. (I actually have a few domains I’d like to transfer to Cloudflare).
Any thoughts?

Thanks for the contribution!
Unfortunately, I don’t have a domain that is managed by Cloudflare, so I can’t really test if this works properly myself.
Every time the AWX Operator and Cert Manager versions change, I actually run and test most of my documentation, so the issue of not being able to test by myself will keep coming up while I’m maintaining this repository.
Honestly, I'm a bit hesitant about keeping the documentation up to date for environments I don’t use. I might consider merging this PR if I start using Cloudflare. (I actually have a few domains I’d like to transfer to Cloudflare).
Any thoughts?

Hi,
thank you for your message and I totally understand where you're coming from.
I have you used your project to setup AWX at work and in my homelab and you have been a great support. This was my way of saying thanks to you.
I have deployed on 3 different OS distributions using latest K3S and cert manager (your docs are using old versions). All working perfectly fine.
There are a lot of people who use cloud flare for DNS so I thought I would share my configs for someone who comes here looking for it.
It's your project and your rules. If you don't wish to merge. Then no probs :)
Keep up the good work my friend!
Cheers

can confirm the documentation is sound, as it goes through the same steps as we had to do for our domain managed by cloudflare


No Typescript support

For projects created using Typescript unfortunately the Lib doesn't work, because it doesn't find equivalent types of the lib.

It does work, you just need to declare the module, still, TS support would be great.
declare module "react-media-player";


List built-in images

Argument 'linux' has been deprecated and will be removed in a future release. Use '--os-type' instead.

@CarnegieJ : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


error: Maximum call stack size exceeded with schemas having ~510 properties or more

While this was originally posted on https://github.com/ajv-validator/ajv-cli/issues/134 it proved to not be caused by the cli itself, but being more of a generic issue with ajv schema loader.
I recently discovered that bigger generated schemas can easily produce a a error: Maximum call stack size exceeded, even when the checks are quite simple.
ajv -- validate --strict=false --errors=json -s f/ansible-playbook.json -d /Users/ssbarnea/c/a/schemas/examples/playbooks/run.yml
schema f/ansible-playbook.json is invalid
error: Maximum call stack size exceeded

Based on my initial tests 500 properties worked but 1000 generated this error, which is a very low number. My expectation that that I will likely need 10k in the end. I tested with 510 and job only one schema failing instead of both, with 550 both failed. Clearly the moment it starts to fail is just after 500.
I am not sure what is confusing the loader because in the end the entries are very simple.
Here is one file that has ~1000 entries https://sbarnea.com/ss/ansible-playbook.json and is only ~100kb, just removing some of the properties will make it pass.
I also observed that if I reduce the number of properties to be near the limit, i also get an interesting behavior where it randomly fails with Maximum call stack size exceeded on each run. As soon you increase the number bit more it fails all the time.
I tried to use the API directly in order to to some of the options, like loopRequired as I was told by @epoberezkin but I was unable to find any configuration option that would prevent this bug from occurring.

Thanks for looking into this! The ulimit workaround is quite inconvenient to use but I will try to see if I can squeeze it as a script command inside package.json
The issue can be reproduced with a far smaller file than the one in my example. Based on my test somewhere right after 500-510 properties is enough, not 5000 like in my the example. Still, the final schema will have more than 5000 and these will all have their own parameters not being just plain "object".

Ajv  basically compiles your schema into javascript code and then executes this code.
If your schema is more or less stable you could compile the code once (getting the 4.3 Mb parser ;-))
This works for me to create the parser:
/bin/bash -c "ulimit -s 65500; npx --node-arg=--stack-size=65500 ajv-cli compile -s ansible-playbook.json -o ansibleParser.js --code-lines
However the resulting 115K lines of javascript in ansibleParser.js also run out of stack.
If you only need this as a command line parser then there might be tools that are currently better suited for this use case.
Kind regards,
Hans

I am only using ajv as a way to validate that the generated schema is valid and produce expected results on a set of tests files. The only deliverables of the project are the schemas themselves, not a loader/parser.
At this moment the only known consumer of these schemas is the vscode-ansible extension, which idirectly makes use of https://github.com/microsoft/vscode-json-languageservice which has its own schema validator implementation.
I am planning to drop use of ajv completely due to this limitation, especially as I suspect that even if some improvement is done now, I will later face the same kind of issues when the schema size will be full grown.

Generating code from the 500K JSON schema file resulted in a 4.3 Mb standalone parser javascript file.

That's not that bad, given that JSON Schema is a much higher level (however restrictive) language than JS :)
The problem is that with "properties" keyword each property is compiled into its own code, but if there is a substantial similarity between them, it would be highly repetitive...
Some optimisation ideas:

Try using allErrors: true option - it should results in the code with less nesting of conditions (which is what causing deep recursion stack). It would collect all errors, though, rather than bail on the first one.
Try extracting (programmatically) any share parts into definitions and use inlineRefs: false (to make sure that the definition is compiled into a separate function and not just inlined every time it is used).

As a library improvement, there

The above suggestions work: see https://runkit.com/esp/6097b403293f88001a7fbb96
Using allErrors: true makes validation function shallow, so it doesn't exceed the stack regardless of the number of properties (I tried 10000 too).
Using $ref with inlineRefs: false option substantially reduces the size of the validation function.


Create user guide documentation

Document what's available for maintainers looking to use the code in here.

[ ] GitHub client
[ ] Filtering results
[ ] Building key Markdown components from objects
[ ] Available reports (and models)
[ ] Running workflows across repositories
[ ] Testing framework

I would put this on hold until we have moved the codebase to TypeScript, at which point we can use TypeDoc and start with API docs generate from the extensive comments & annotations you already added.

Just saw your comment here - I think I misunderstood the scope of this issue and API docs will in fact be addressed later on.


DiscoveryClientHealthIndicator does not respect "light weight operation" of probe() when using CompositeDiscoveryClient

I am using spring-cloud-consul. Spring Cloud Consul constructs a ConsulDiscoveryClient, which has an override for DiscoveryClient.probe() for a light weight operation. This lightweight operation is not respected when  spring.cloud.discovery.client.health-indicator.use-service-query, is set to false and there are multiple DiscoveryClient beans.
The DiscoveryClientHealthIndicator performs the following operation in the method, health().
if (properties.isUseServicesQuery()) {
	List<String> services = client.getServices();
	builder.status(new Status("UP", description)).withDetail("services", services);
}
else {
	client.probe();
	builder.status(new Status("UP", description));
}

If the property, spring.cloud.discovery.client.health-indicator.use-service-query, is set to false then the DiscoveryClient should use the light weight probe() instead of getServices(). In the case where the client is of type CompositeDiscoveryClient, we end up executing getServices() because the CompositeDiscoveryClient does not override the implementation for probe(). Instead, if uses the default implementation of DiscoveryClient.getProbe(), which calls DiscoveryClient.getServices().

Submitted a pull request to resolve - https://github.com/spring-cloud/spring-cloud-commons/pull/1210


nat: add extraCommands option

Motivation for this change
Due to the order in which the iptables rules are combined, it's not possible to write some NAT rules in networking.firewall.extraCommands.  This PR adds networking.nat.extraCommands, which is inserted in the appropriate place for users to add their own custom NAT commands.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Shouldn't it have extraStopCommands as well?
Like networking.firewall.extraCommands and networking.firewall.extraStopCommands

and doesn't mkBefore/mkAfter solve the problem with order?

@volth extraStopCommands makes sense to me - I'll add that.  I don't think mkBefore and mkAfter are quite powerful enough to do what we would need here: networking.nat uses networking.firewall.extraCommands to insert itself into the firewall code, but we need our commands to run in the middle of those inserted nat commands, not before or after the nat commands.

@volth Do you have an example of a stop command that would be good to put in the documentation?  I'm not quite sure what would make sense there.

I am not sure if it is good (easy enough) for documentation, just something from the real world...
extraStopCommands cleaning up the old entries if something changed (the IPs which are hardcoded in the example are variables and could be changed, then nixos-rebuild cleans up old entries).
# <IP_ADDRESS>/16    on tinc.dmz is a Tinc network
# <IP_ADDRESS>/24  on brdmz is a bridge on a physical machine with libvirt/qemu virtual machines, VMs are in tinc.dmz and also have Internet access via NAT

  firewall = let
    extra = [
      "FORWARD  -i tinc.dmz  -s <IP_ADDRESS>/16   -o brdmz     -d <IP_ADDRESS>/24 -j ACCEPT"
      "FORWARD  -i brdmz     -s <IP_ADDRESS>/24 -o tinc.dmz  -d <IP_ADDRESS>/16   -j ACCEPT"
    ];
  in rec {
    enable = true;
    extraCommands     = extraStopCommands + (lib.concatMapStrings (x: "iptables -I ${x}\n"        ) extra);
    extraStopCommands =                      lib.concatMapStrings (x: "iptables -D ${x} || true\n") extra;
  };
  bridges.brdmz.interfaces = [];
  interfaces.brdmz.ip4     = [{ address = "<IP_ADDRESS>"; prefixLength = 24; } ];
  nat = {
    enable = true;
    externalInterface = "bond0";
    externalIP = public-ip;
    internalInterfaces = ["brdmz"];
  };

extraCommands     = extraStopCommands + ... is here to work around an old bug which might be not actual nowdays, so could be removed from the example

@volhovm Ah ok, cool!  I kept it a bit shorter here, and just made it the opposite of the example extraCommands, so hopefully that will give people a good enough sense of what to do!

@volth Does the extraStopCommands splice look like it's in the right place?

I do not know, I had no problems with the ordering.


CPU hotpath originating in CosmosQueryClientCore.GetCosmosElementResponse

Describe the bug
Seeing CPU hotpath that is originating in CosmosQueryClientCore.GetCosmosElementResponse which is using 6% of application CPU during a query workload.
Flame graph reference internal link:

Zooming into the QueryPage ctor:

The main issue is whether this CPU impact can be reduced when SDK is handling high volume query workloads.
Within this hotpath two methods are of note:

Page ctor is creating an ImmutableDictionary for AdditionalHeaders property, see - ImmutableDictionary is known to be much slower than Dictionary, so maybe IReadOnlyDictionary would be better for this even if the trade-off is that true immutability guarantee is lost?

QueryExceutionInfo header is deserialized with Newtonsoft.Json here -  Would it be more performant to use the Json text readers built-in to the SDK instead?

To Reproduce
Run a high volume query workload and monitor/profile on the SDK.
More likely to see the issue with the following setup/workload

10+ partitions collection.
Query workload issuing cross partition queries which return no results. This highlights the impact of many empty pages being returned but where the header/execution info is still significant.

Expected behavior
Expect a lower CPU impact on an application for the critical path in query responses.
Actual behavior
Higher CPU impact for query response handling especially when very few items are returned.
Environment summary
SDK Version: 3.21/Any
OS Version: Win 10

@sourabh1007 what else is pending for this issue?

It can be closed now.


[FEATURE] command, tcpSocket and grpc livenessProbe and readinessProbe support

Detailed description
It would be ideal to support the command, tcpSocket and grpc methods for livenessProbe and readinessProbe.
Context
Today, only the httpGet method for livenessProbe and readinessProbe is supported.
command is another very popular method, like illustrated here with grpc apps: https://github.com/GoogleCloudPlatform/microservices-demo/blob/main/release/kubernetes-manifests.yaml#L61.
So for example, today, this below is supported:
apiVersion: score.dev/v1b1
metadata:
  name: adservice
containers:
  adservice:
    image: gcr.io/google-samples/microservices-demo/adservice:v0.6.0
    variables:
      PORT: "9555"
    livenessProbe:
      exec:
        command:
          - /bin/grpc_health_probe
          - '-addr=:9555'
    readinessProbe:
      exec:
        command:
          - /bin/grpc_health_probe
          - '-addr=:9555'

Possible implementation
Humanitec is already supported tcpSocket and command in addition to httpGet.
Note: gRPC (only supported since Kubernetes 1.24+) is not yet supported in Humanitec. The alternative is to use the command method by using the grpc_health_probe binary.
Additional information
Configure Liveness, Readiness and Startup Probes in Kubernetes.

We've received a similar feature request:

"Need to translate this

                "liveness_probe": {
                    "port": "3000",
                    "type": "tcp"
                },

using score"

This should be straight forward. But things will need to be cautious because not all score implementations will support all kinds of probes (as it is docker compose doesn't support httpGet).


chore(main): release 1.2.2-beta

:robot: I have created a release beep boop
1.2.2-beta (2023-07-31)
Bug Fixes

json stringify formatted write (729a0cc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/appblocks-hub/BB-CLI/releases/tag/v1.2.2-beta :sunflower:


What belongd into the JSON file?

Please follow the guide below

Issues submitted without this template format will be ignored.
You will be asked some questions and requested to provide some information, please read them carefully and answer completely.
Do not post screenshots of error messages or code.
Put an x into all the boxes [ ] relevant to your issue (like so [x] no spaces).
Use the Preview tab to see how your issue will actually look like.
Issues about reverse engineering is out of scope and will be closed without response.

Before submitting an issue, make sure you have:

[x] Updated to the lastest version v1.3.6
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones
[x] Reviewed the sample code in tests and examples

Which client are you using?

[x] app (instagram_private_api/)
[ ] web (instagram_web_api/)

Purpose of your issue?

[ ] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

For a bug report, you must include the Python version used, code that will reproduce the error, and the error log/traceback.
Describe your issue
Hey I am sorry but I am not that familiar with python and from your code I cant really read why a JSON file has to be put in as a parameter or what even belongs into the json file 🤔 .
Hope you could clarify that for me thanks!

The use of a json file in the examples is just a demo of how people can store their authenticated session info to avoid constantly relogging in. Devs can choose to store the info in a database, or any other persistant format they want. The library doesn't take in any json file parameter at all.
If you're unfamiliar with Python, this library is probably not suitable for you.


sgt constructor problem v. 1.2.13

Hey all!
Im currently getting the following error messages from the sgt constructor
sgt_constructor.py -t 50 -i working_dataset_constructor_out_Nov.06.2024
Building DAG of jobs...
Creating conda environment /home/arodr412/mambaforge/envs/fisher/bin/mafft.yaml...
Downloading and installing remote packages.
CreateCondaEnvironmentException:
Could not create conda environment from /home/arodr412/mambaforge/envs/fisher/bin/mafft.yaml:
Traceback (most recent call last):
File "/home/arodr412/mambaforge/condabin/mamba", line 7, in
from mamba.mamba import main
File "/home/arodr412/mambaforge/lib/python3.10/site-packages/mamba/mamba.py", line 18, in
from conda.cli.main import generate_parser, init_loggers
ImportError: cannot import name 'generate_parser' from 'conda.cli.main' (/home/arodr412/mambaforge/lib/python3.10/site-packages/conda/cli/main.py)
File "/home/arodr412/mambaforge/envs/fisher/lib/python3.7/site-packages/snakemake/deployment/conda.py", line 390, in create
Traceback (most recent call last):
File "/home/arodr412/mambaforge/envs/fisher/bin/sgt_constructor.py", line 150, in
run_snakemake(length_filter=False)
File "/home/arodr412/mambaforge/envs/fisher/bin/sgt_constructor.py", line 85, in run_snakemake
f'--config {make_config(length_filter)}',
File "/home/arodr412/mambaforge/envs/fisher/bin/sgt_constructor.py", line 49, in make_config
f'genes={",".join(get_genes(length_filter))}',
File "/home/arodr412/mambaforge/envs/fisher/bin/sgt_constructor.py", line 27, in get_genes
bmge_out_files = [file for file in os.listdir(len_filt_bmge_dir) if file.endswith('.bmge')]
FileNotFoundError: [Errno 2] No such file or directory: '/home/arodr412/hokuleaphylo/hokuwatst/sgt_constructor_out_Nov.06.2024/length_filtration/bmge'
Ok so import it manually???
ImportError: cannot import name 'generate_parser' from 'conda.cli.main'
/home/arodr412/mambaforge/lib/python3.10/site-packages/conda/cli/
(fisher) [arodr412@sc009:~/mambaforge/lib/python3.10/site-packages/conda/cli]$ ls
actions.py install.py        main_env_config.py  main_env_update.py  main_list.py             main.py pycache/
common.py          main_clean.py     main_env_create.py  main_env_vars.py    main_mock_activate.py    main_remove.py  python_api.py
conda_argparse.py  main_commands.py  main_env_export.py  main_export.py      main_mock_deactivate.py  main_rename.py
find_commands.py   main_compare.py   main_env_list.py    main_info.py        main_notices.py          main_run.py
helpers.py         main_config.py    main_env.py         main_init.py        main_package.py          main_search.py
init.py        main_create.py    main_env_remove.py  main_install.py     main_pip.py              main_update.py
it was trying to access the directory which it couldn't create basically because of the reasons above?
FileNotFoundError: [Errno 2] No such file or directory: '/home/arodr412/hokuleaphylo/hokuwatst/sgt_constructor_out_Nov.06.2024/length_filtration/bmge'
Any help and input is appreciated!

Its fixed!! downgrade the mamba version  " mamba install -c conda-forge mamba=1 "


Cannot get Flutter Hello World to build on one computer in particular

Steps to Reproduce

Get latest flutter stable (v1.12.13+hotfix.5).
Create a new Flutter project in Android studio. Include Androidx, Kotlin, and Swift support.
Call flutter build apk --debug. It will fail, usually saying Execution failed for task ':app:compileDebugKotlin'.

Background
I have been developing on my Windows 10 desktop on flutter for about a year with no problem. This was working fine until I updated to 1.12.13 of flutter and Android Studio to 3.5. Suddenly my main project stopped building. I tried the starter app and noticed it didn't work either.
Note that this works perfectly on both an old Windows 10 laptop and my Macbook Pro.
I have tried uninstalling and reinstalling Android Studio, Android SDK, and Flutter to no avail. Please help!
Logs

logs
PS C:\Development\test_app_flutter> flutter build apk --debug --target-platform android-x64 --verbose
[  +24 ms] executing: [C:\Development\flutter\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +59 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 27321ebbad34b0a3fafe99fac037102196d655ff
[        ] executing: [C:\Development\flutter\] git describe --match v*.*.* --first-parent --long --tags
[  +48 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.12.13+hotfix.5-0-g27321ebba
[   +6 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[  +41 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\Development\flutter\] git ls-remote --get-url origin
[  +37 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +77 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref HEAD
[  +38 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +40 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[  +11 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +197 ms] Generating C:\Development\test_app_flutter\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +60 ms] Running Gradle task 'assembleDebug'...
[   +2 ms] gradle.properties already sets `android.enableR8`
[   +3 ms] Using gradle from C:\Development\test_app_flutter\android\gradlew.bat.
[   +7 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[  +91 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[        ] openjdk version "1.8.0_202-release"
           OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
           OpenJDK 64-Bit Server VM (build 25.202-b03, mixed mode)
[   +3 ms] executing: [C:\Development\test_app_flutter\android\] C:\Development\test_app_flutter\android\gradlew.bat -Pverbose=true -Ptarget=lib\main.dart -Ptrack-widget-creation=true -Pshrink=true -Ptarget-platform=android-x64 assembleDebug
[+3591 ms] > Task :app:compileFlutterBuildDebug
[   +1 ms] [  +20 ms] executing: [C:\Development\flutter\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] [  +61 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] 27321ebbad34b0a3fafe99fac037102196d655ff
[        ] [        ] executing: [C:\Development\flutter\] git describe --match v*.*.* --first-parent --long --tags
[        ] [  +40 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[   +1 ms] [        ] v1.12.13+hotfix.5-0-g27321ebba
[        ] [   +6 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[   +2 ms] [  +38 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[  +18 ms] [        ] origin/stable
[   +1 ms] [        ] executing: [C:\Development\flutter\] git ls-remote --get-url origin
[   +1 ms] [  +36 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[   +1 ms] [  +71 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref HEAD
[        ] [  +38 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[  +15 ms] [        ] stable
[   +4 ms] [  +16 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[  +23 ms] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[  +10 ms] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +1 ms] [  +73 ms] Initializing file store
[  +11 ms] [  +14 ms] Done initializing file store
[  +83 ms] [+1260 ms] Skipping target: kernel_snapshot
[        ] [  +51 ms] debug_android_application: Starting due to {InvalidatedReason.outputMissing}
[ +200 ms] [ +130 ms] debug_android_application: Complete
[   +1 ms] [  +15 ms] Persisting file store
[        ] [  +13 ms] Done persisting file store
[        ] [   +3 ms] build succeeded.
[        ] [  +18 ms] "flutter assemble" took 1,639ms.
[  +97 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[   +1 ms] > Task :app:preBuild UP-TO-DATE
[   +1 ms] > Task :app:preDebugBuild UP-TO-DATE
[  +11 ms] > Task :app:compileDebugAidl NO-SOURCE
[        ] > Task :app:checkDebugManifest UP-TO-DATE
[        ] > Task :app:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :app:compileDebugRenderscript NO-SOURCE
[        ] > Task :app:cleanMergeDebugAssets
[        ] > Task :app:mergeDebugShaders UP-TO-DATE
[        ] > Task :app:compileDebugShaders UP-TO-DATE
[        ] > Task :app:generateDebugAssets UP-TO-DATE
[  +80 ms] > Task :app:mergeDebugAssets
[ +202 ms] > Task :app:copyFlutterAssetsDebug
[   +4 ms] > Task :app:mainApkListPersistenceDebug UP-TO-DATE
[  +12 ms] > Task :app:generateDebugResValues UP-TO-DATE
[        ] > Task :app:generateDebugResources UP-TO-DATE
[        ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[  +80 ms] > Task :app:mergeDebugResources UP-TO-DATE
[   +2 ms] > Task :app:processDebugManifest UP-TO-DATE
[        ] > Task :app:processDebugResources UP-TO-DATE
[        ] > Task :app:compileDebugKotlin FAILED
[        ] FAILURE: Build failed with an exception.
[   +1 ms] * What went wrong:
[        ] Execution failed for task ':app:compileDebugKotlin'.
[        ] > Could not resolve all artifacts for configuration ':app:debugCompileClasspath'.
[        ]    > Failed to transform artifact 'flutter_embedding_debug.jar (io.flutter:flutter_embedding_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[  +12 ms]       > Execution failed for JetifyTransform:
C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\flutter_embedding_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\397363798e6ed63dd1263a0c71860ee74a39b682\flutter_embedding_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.
[   +5 ms]          > Failed to transform
'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\flutter_embedding_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\397363798e6ed63dd1263a0c71860ee74a39b682\flutter_embedding_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using Jetifier. Reason: invalid
entry CRC (expected 0xfa4c5549 but got 0xc04c61c3). (Run with --stacktrace for more details.)
[  +11 ms]    > Failed to transform artifact 'x86_64_debug.jar (io.flutter:x86_64_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[        ]       > Execution failed for JetifyTransform: C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_64_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\9d58742ea4187814c2c34c3e08d7219028482b00\x86_64_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.[   +1 ms]          > Failed to transform 'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_64_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\9d58742ea4187814c2c34c3e08d7219028482b00\x86_64_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using
Jetifier. Reason: invalid code lengths set. (Run with --stacktrace for more details.)
[   +1 ms]    > Failed to transform artifact 'x86_debug.jar (io.flutter:x86_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[  +15 ms]       > Execution failed for JetifyTransform: C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\5397ba2fdad89010a49162dc1ad6eadfdb2f27df\x86_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.
[   +1 ms]          > Failed to transform 'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\5397ba2fdad89010a49162dc1ad6eadfdb2f27df\x86_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using Jetifier.
Reason: too many length or distance symbols. (Run with --stacktrace for more details.)
[  +16 ms] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[  +17 ms] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 4s
[        ] 16 actionable tasks: 5 executed, 11 up-to-date
[ +277 ms] Running Gradle task 'assembleDebug'... (completed in 5.0s)
[   +5 ms] "flutter apk" took 5,329ms.
Gradle task assembleDebug failed with exit code 1

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      buildGradleApp (package:flutter_tools/src/android/gradle.dart:387:7)
#2      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#3      _rootRunUnary (dart:async/zone.dart:1134:38)
#4      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:524:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#11     _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart)
#12     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#13     _rootRunUnary (dart:async/zone.dart:1134:38)
#14     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#15     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#16     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#17     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#18     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#19     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#20     _rootRun (dart:async/zone.dart:1126:13)
#21     _CustomZone.run (dart:async/zone.dart:1023:19)
#22     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#23     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#24     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#25     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#26     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#27     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

Flutter Doctor
PS C:\Development\test_app_flutter> flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale en-US)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 3.5)
[√] VS Code, 64-bit edition (version 1.41.1)
[√] Connected device (1 available)

• No issues found!

Build.gradle
buildscript {
    ext.kotlin_version = '1.3.50'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Hi @lovelessX
from the information you provided,
especially the fact that the issue occurs only a single machine
I recommend to run on said machine
flutter pub cache repair
cd <YOUR APP FOLDER>
flutter clean
If the issue persist please provide your updated
flutter doctor -v and flutter run --verbose
thank you

That did not help.
Verbose Doctor (note I switched to an x86 emulator to try to mimic my other machine after posting the original bug report)
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale en-US)
    • Flutter version 1.12.13+hotfix.5 at C:\Development\flutter
    • Framework revision 27321ebbad (4 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\MyUserName\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code, 64-bit edition (version 1.41.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.7.1

[√] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

• No issues found!

Flutter Run Verbose
[  +21 ms] executing: [C:\Development\flutter\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +61 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] 27321ebbad34b0a3fafe99fac037102196d655ff
[        ] executing: [C:\Development\flutter\] git describe --match v*.*.* --first-parent --long --tags
[  +44 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.12.13+hotfix.5-0-g27321ebba
[   +7 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[  +38 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\Development\flutter\] git ls-remote --get-url origin
[  +38 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +74 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref HEAD
[  +34 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +96 ms] executing: C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[  +23 ms] Exit code 0 from: C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[        ] List of devices attached
           emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:4
[  +13 ms] C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell getprop
[  +56 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[  +11 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +129 ms] Generating C:\Development\test_app_flutter\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +24 ms] ro.hardware = ranchu
[  +32 ms] Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider enabling software rendering with "--enable-software-rendering".
[  +16 ms] Launching lib\main.dart on Android SDK built for x86 in debug mode...
[  +16 ms] executing: C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell -x logcat -v time -s flutter
[  +11 ms] executing: C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe version
[  +58 ms] Android Debug Bridge version 1.0.41
           Version 29.0.5-5949299
           Installed as C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe
[   +2 ms] executing: C:\Users\MyUserName\AppData\Local\Android\sdk\platform-tools\adb.exe start-server
[  +34 ms] Building APK
[  +15 ms] Running Gradle task 'assembleDebug'...
[   +1 ms] gradle.properties already sets `android.enableR8`
[   +5 ms] Using gradle from C:\Development\test_app_flutter\android\gradlew.bat.
[  +10 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[  +90 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[        ] openjdk version "1.8.0_202-release"
           OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
           OpenJDK 64-Bit Server VM (build 25.202-b03, mixed mode)
[   +3 ms] executing: [C:\Development\test_app_flutter\android\] C:\Development\test_app_flutter\android\gradlew.bat -Pverbose=true -Ptarget=C:\Development\test_app_flutter\lib\main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
-Ptarget-platform=android-x86 assembleDebug
[+3580 ms] > Task :app:compileFlutterBuildDebug
[   +1 ms] [  +20 ms] executing: [C:\Development\flutter\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +15 ms] [  +62 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +23 ms] [        ] 27321ebbad34b0a3fafe99fac037102196d655ff
[  +54 ms] [        ] executing: [C:\Development\flutter\] git describe --match v*.*.* --first-parent --long --tags
[   +5 ms] [  +40 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] [        ] v1.12.13+hotfix.5-0-g27321ebba
[  +13 ms] [   +6 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[        ] [  +40 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/stable
[        ] [        ] executing: [C:\Development\flutter\] git ls-remote --get-url origin
[        ] [  +33 ms] Exit code 0 from: git ls-remote --get-url origin
[  +11 ms] [        ] https://github.com/flutter/flutter.git
[        ] [  +67 ms] executing: [C:\Development\flutter\] git rev-parse --abbrev-ref HEAD
[        ] [  +32 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[        ] [  +17 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +10 ms] [   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [  +75 ms] Initializing file store
[        ] [  +18 ms] kernel_snapshot: Starting due to {}
[   +9 ms] [  +11 ms] C:\Development\flutter\bin\cache\dart-sdk\bin\dart.exe C:\Development\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root C:\Development\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --target=flutter
-Ddart.developer.causal_async_stacks=true -Ddart.vm.profile=false -Ddart.vm.product=false --bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts --track-widget-creation
--no-link-platform --packages C:\Development\test_app_flutter\.packages --output-dill C:\Development\test_app_flutter\.dart_tool\flutter_build\3abd275395033124b056356cfb21af4a\app.dill --depfile
C:\Development\test_app_flutter\.dart_tool\flutter_build\3abd275395033124b056356cfb21af4a\kernel_snapshot.d package:test_app_flutter/main.dart
[+3630 ms] [+4757 ms] kernel_snapshot: Complete
[+1202 ms] [+1229 ms] debug_android_application: Starting due to {}
[  +99 ms] [ +120 ms] debug_android_application: Complete
[ +300 ms] [ +290 ms] Persisting file store
[   +1 ms] [  +15 ms] Done persisting file store
[        ] [   +3 ms] build succeeded.
[  +97 ms] [  +30 ms] "flutter assemble" took 6,589ms.
[ +110 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[   +1 ms] > Task :app:preBuild UP-TO-DATE
[   +2 ms] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[   +6 ms] > Task :app:checkDebugManifest UP-TO-DATE
[  +14 ms] > Task :app:generateDebugBuildConfig UP-TO-DATE
[  +10 ms] > Task :app:compileDebugRenderscript NO-SOURCE
[   +1 ms] > Task :app:cleanMergeDebugAssets
[  +53 ms] > Task :app:mergeDebugShaders UP-TO-DATE
[        ] > Task :app:compileDebugShaders UP-TO-DATE
[        ] > Task :app:generateDebugAssets UP-TO-DATE
[   +1 ms] > Task :app:mergeDebugAssets
[ +195 ms] > Task :app:copyFlutterAssetsDebug
[  +17 ms] > Task :app:mainApkListPersistenceDebug UP-TO-DATE
[  +21 ms] > Task :app:generateDebugResValues UP-TO-DATE
[   +2 ms] > Task :app:generateDebugResources UP-TO-DATE
[  +25 ms] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[   +6 ms] > Task :app:processDebugJavaRes NO-SOURCE
[  +30 ms] > Task :app:mergeDebugResources UP-TO-DATE
[   +2 ms] > Task :app:processDebugManifest UP-TO-DATE
[  +39 ms] > Task :app:processDebugResources UP-TO-DATE
[   +5 ms] > Task :app:compileDebugKotlin FAILED
[   +4 ms] FAILURE: Build failed with an exception.
[   +1 ms] * What went wrong:
[        ] Execution failed for task ':app:compileDebugKotlin'.
[   +1 ms] > Could not resolve all artifacts for configuration ':app:debugCompileClasspath'.
[   +2 ms]    > Failed to transform artifact 'flutter_embedding_debug.jar (io.flutter:flutter_embedding_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[   +7 ms]       > Execution failed for JetifyTransform:
C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\flutter_embedding_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\397363798e6ed63dd1263a0c71860ee74a39b682\flutter_embedding_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.
[  +18 ms]          > Failed to transform
'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\flutter_embedding_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\397363798e6ed63dd1263a0c71860ee74a39b682\flutter_embedding_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using Jetifier. Reason: invalid
entry CRC (expected 0xfa4c5549 but got 0xc04c61c3). (Run with --stacktrace for more details.)
[   +1 ms]    > Failed to transform artifact 'x86_debug.jar (io.flutter:x86_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[        ]       > Execution failed for JetifyTransform: C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\5397ba2fdad89010a49162dc1ad6eadfdb2f27df\x86_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.
[        ]          > Failed to transform 'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\5397ba2fdad89010a49162dc1ad6eadfdb2f27df\x86_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using Jetifier.
Reason: too many length or distance symbols. (Run with --stacktrace for more details.)
[   +1 ms] 16 actionable tasks: 5 executed, 11 up-to-date
[        ]    > Failed to transform artifact 'x86_64_debug.jar (io.flutter:x86_64_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695)' to match attributes {artifactType=android-classes, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
[   +1 ms]       > Execution failed for JetifyTransform: C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_64_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\9d58742ea4187814c2c34c3e08d7219028482b00\x86_64_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar.[  +15 ms]          > Failed to transform 'C:\Users\MyUserName\.gradle\caches\modules-2\files-2.1\io.flutter\x86_64_debug\1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695\9d58742ea4187814c2c34c3e08d7219028482b00\x86_64_debug-1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695.jar' using
Jetifier. Reason: invalid code lengths set. (Run with --stacktrace for more details.)
[  +16 ms] * Try:
[   +1 ms] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[  +18 ms] * Get more help at https://help.gradle.org
[  +15 ms] BUILD FAILED in 9s
[ +257 ms] Running Gradle task 'assembleDebug'... (completed in 10.1s)
[   +5 ms] "flutter run" took 10,701ms.
Gradle task assembleDebug failed with exit code 1

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      buildGradleApp (package:flutter_tools/src/android/gradle.dart:387:7)
#2      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#3      _rootRunUnary (dart:async/zone.dart:1134:38)
#4      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:524:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#11     _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart)
#12     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#13     _rootRunUnary (dart:async/zone.dart:1134:38)
#14     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#15     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#16     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#17     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#18     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#19     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#20     _rootRun (dart:async/zone.dart:1126:13)
#21     _CustomZone.run (dart:async/zone.dart:1023:19)
#22     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#23     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#24     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#25     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#26     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#27     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

Turns out my gradle caches were corrupted in some way.
I followed the guide here to delete everything and then it started working again.
https://stackoverflow.com/questions/23025433/how-to-clear-gradle-cache/30450020#30450020
Closing this ticket.


Fix carousel box sizes, added auto carousel, and changed button layout

Changes proposed

Fixing the problem of inconsistent box sizes within the carousel, improving the overall appearance and usability.
Converting the carousel into an auto carousel for automatic transitions between slides, providing a more engaging user experience.
Adjusting the button layout, moving them from the side to the bottom of the carousel for better user accessibility and intuition.

Screenshots

before changes

-After changes

Note to reviewers
In this pull request, I have made several improvements to the carousel feature:
Fixed the issue of inconsistent box sizes within the carousel: Previously, the varying sizes of the boxes caused a poor user experience. Now, the boxes display consistently, enhancing the overall appearance and usability of the carousel.
Converted the carousel to an auto carousel: With this update, the carousel will automatically transition between slides, providing a more engaging and seamless user experience. Users will no longer need to manually interact with the carousel.
Adjusted the button layout: The buttons, which were initially located on the side of the carousel, have been moved to the bottom. This change is aimed at improving user accessibility and intuition, making it easier for users to navigate the carousel.
I kindly request the reviewers to focus on the code changes related to these enhancements. Your feedback and suggestions are greatly appreciated, especially if you notice any potential issues or areas that require further refinement.
Thank you for your time and assistance in reviewing this pull request.
Label Request
Dear reviewers, I kindly request the addition of the "gssoc" , "enhancements" label to this pull request. As I am participating in the GirlScript Summer of Code, this label will help in identifying my contributions. Thank you for your attention and assistance.

yes i made some changes as per requirements but there is an other issue with the nav bar with the social media icons due to it there is an issue of center as it is taking the whole space

with symbol

without symbol

@prnvtripathi @Susmita-Dey  can you please review the pull request and add the tags of gssoc

@abhipatel0211 Issue no?
I see that you're not following the CONTRIBUTING GUIDELINES as you haven't linked any issue no here which was being assigned to you.

Sorry i haven't raised the issue

Should I raise now?

GSSoC endeed I guess @abhipatel0211

Ok no issue but can you merge it or I have to raise the issue first and then you will merge

i have raised the issue #452  can you please assign that issue to me and review this PR @Susmita-Dey

@Susmita-Dey  @prnvtripathi  can you please review this PR

@abhipatel0211 Do not change UI just make Automation of Carousal that will be good.

@AbhiPatel10 @Susmita-Dey @prnvtripathi  can you please review the changes


Encoding structs such as DateTime/Date is slow for many structs

In [encode_datetime_series](https://github.com/elixir-nx/explorer/blob/main/native/explorer/src/datatypes.rs#L1990, the struct type is built then returned to Rustler to encode.
I've found instead building the map myself, then adding the struct key is up to 4x faster and uses much less memory. This is because it doesn't have to be sent into Rustler to encode the structs when you have hundreds of thousands of structs.
I'm happy to create a PR for this with some benchmarks to show this. These sorts of tasks should have the least amount of encoding done to them.
Here is what I've done for snowflake arrow:

Outside the series loop, define this:

    // Here we build the NaiveDateTime struct manually, as it's about 4x faster than using NifStruct.
    // It's faster because we already have the keys (we know this at compile time), and the type.
    let datetime_struct_keys = [
        atom::__struct__().encode(env).as_c_arg(),
        calendar().encode(env).as_c_arg(),
        microsecond().encode(env).as_c_arg(),
        day().encode(env).as_c_arg(),
        month().encode(env).as_c_arg(),
        year().encode(env).as_c_arg(),
        hour().encode(env).as_c_arg(),
        minute().encode(env).as_c_arg(),
        second().encode(env).as_c_arg(),
    ];

    // This is used for the map to know that it's a struct. Define it here so it's not redefined in the loop.
    let datetime_module_atom = Atom::from_str(env, "Elixir.NaiveDateTime")
        .unwrap()
        .encode(env)
        .as_c_arg();
    let nil = nil().encode(env).as_c_arg();

We use encode here for the types because the c_arg could change between OTP versions if we hardcode it. Plus it's done once, so it's cheap enough.

Inside the loop, I do this:

                            dt_item.map(|dt_value| {
                                let dt = match tu {
                                    TimeUnit::Nanoseconds => timestamp_ns_to_datetime(dt_value),
                                    TimeUnit::Microseconds => timestamp_us_to_datetime(dt_value),
                                    TimeUnit::Milliseconds => timestamp_ms_to_datetime(dt_value),
                                };

                                let values = &[
                                    datetime_module_atom,
                                    calendar_iso_c_arg,
                                    (dt.timestamp_subsec_micros(), 6).encode(env).as_c_arg(),
                                    dt.day().encode(env).as_c_arg(),
                                    dt.month().encode(env).as_c_arg(),
                                    dt.year().encode(env).as_c_arg(),
                                    dt.hour().encode(env).as_c_arg(),
                                    dt.minute().encode(env).as_c_arg(),
                                    dt.second().encode(env).as_c_arg(),
                                ];
                                Term::new(
                                    env,
                                    map::make_map_from_arrays(
                                        env.as_c_arg(),
                                        &datetime_struct_keys,
                                        values,
                                    )
                                    .unwrap(),
                                )
                            })
                            .encode(env)
                            .as_c_arg()

I've found this has made the biggest difference in terms of memory usage and has sped up the encoding times drastically when you have many structs.

PR definitely welcome for this one!


withParam value could not be parsed as a JSON list with nested list parameters

Checklist:

[x] I've included the version.
[x] I've included reproduction steps.
[x] I've included the workflow YAML.
[x] I've included the logs.

What happened:
Working with a parameter that contains a nested list, argo fail with json parsing error even json payload is correct.
What you expected to happen:
We should be able to use json input parameters with nested lists.
Related PRs

https://github.com/argoproj/argo/issues/1389

How to reproduce it (as minimally and precisely as possible):
You can see we have as input a json list.
Removing the data[].dict_param.bug key it passes, but if you keep it it fails.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: bug-nested-list-param-
spec:
  entrypoint: main
  arguments:
    parameters:
      - name: data
        value: |
          [
            {
              "scalar_param": "bar",
              "dict_param": {"foo": "bar", "bug": [1, 2]},
              "list_param": [{"foo": "bar"}]
            }
          ]

  templates:

    - name: main
      inputs:
        parameters:
          - name: data
            value: "{{workflow.parameters.data}}"
      steps:
        - - name: multiple-workflow
            template: one-workflow
            arguments:
              parameters:
                - name: scalar_param
                  value: "{{item.scalar_param}}"
                - name: dict_param
                  value: "{{item.dict_param}}"
                - name: list_param
                  value: "{{item.list_param}}"
            withParam: "{{inputs.parameters.data}}"

    - name: one-workflow
      inputs:
        parameters:
          - name: scalar_param
          - name: dict_param
          - name: list_param
      steps:
        - - name: read-scalar
            template: echo-param
            arguments:
              parameters:
                - name: data
                  value: "{{inputs.parameters.scalar_param}}"
          - name: read-dict
            template: echo-param
            arguments:
              parameters:
                - name: data
                  value: "{{inputs.parameters.dict_param}}"
          - name: read-list
            template: echo-param
            arguments:
              parameters:
                - name: data
                  value: "{{inputs.parameters.list_param}}"

    - name: echo-param
      inputs:
        parameters:
          - name: data
      container:
        image: alpine:latest
        command: [sh, -c]
        args: ["echo 'Input parameter: <{{inputs.parameters.data}}>'"]

Anything else we need to know?:
Environment:

Argo version:

▶ argo version
argo: v2.8.1
  BuildDate: 2020-05-28T23:39:46Z
  GitCommit: 0fff4b21c21c5ff5adbb5ff62c68e67edd95d6b8
  GitTreeState: clean
  GitTag: v2.8.1
  GoVersion: go1.13.4
  Compiler: gc
  Platform: linux/amd64

Kubernetes version :

▶  kubectl version -o yaml
clientVersion:
  buildDate: "2019-12-11T12:41:00Z"
  compiler: gc
  gitCommit: 575467a0eaf3ca1f20eb86215b3bde40a5ae617a
  gitTreeState: clean
  gitVersion: v1.14.10
  goVersion: go1.12.12
  major: "1"
  minor: "14"
  platform: linux/amd64
serverVersion:
  buildDate: "2020-03-18T04:24:17Z"
  compiler: gc
  gitCommit: f459c0672169dd35e77af56c24556530a05e9ab1
  gitTreeState: clean
  gitVersion: v1.14.9-eks-f459c0
  goVersion: go1.12.12
  major: "1"
  minor: 14+
  platform: linux/amd64

Other debugging information (if applicable):

workflow result:

▶ argo --loglevel DEBUG get bug-nested-list-param-6shm8
DEBU[0000] CLI version                                   version="{v2.8.1 2020-05-28T23:39:46Z 0fff4b21c21c5ff5adbb5ff62c68e67edd95d6b8 v2.8.1 clean go1.13.4 gc linux/amd64}"
DEBU[0000] Client options                                opts="{{ false false} 0x1574ab0 0xc0006db090}"
Name:                bug-nested-list-param-6shm8
Namespace:           unicron-serenity-dev
ServiceAccount:      default
Status:              Failed
Message:             withParam value could not be parsed as a JSON list: [
  {
    "scalar_param": "bar",
    "dict_param": {"foo": "bar", "bug": ["1", "2"]},
    "list_param": [{"foo": "bar"}]
  }
]
Conditions:
 Completed           True
Created:             Wed Jun 24 08:59:22 +0200 (32 seconds ago)
Started:             Wed Jun 24 08:59:22 +0200 (32 seconds ago)
Finished:            Wed Jun 24 08:59:22 +0200 (32 seconds ago)
Duration:            0 seconds
Parameters:
  data:              [
  {
    "scalar_param": "bar",
    "dict_param": {"foo": "bar", "bug": ["1", "2"]},
    "list_param": [{"foo": "bar"}]
  }
]

STEP                            TEMPLATE  PODNAME  DURATION  MESSAGE
 ✖ bug-nested-list-param-6shm8  main                         withParam value could not be parsed as a JSON list: [
  {
    "scalar_param": "bar",
    "dict_param": {"foo": "bar", "bug": ["1", "2"]},
    "list_param": [{"foo": "bar"}]
  }
]

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

#3129

func TestBug(t *testing.T) {
	var items []wfv1.Item
	withParam := `[
  {
    "scalar_param": "bar",
    "dict_param": {"foo": "bar", "bug": ["1", "2"]},
    "list_param": [{"foo": "bar"}]
  }
]`
	err := json.Unmarshal([]byte(withParam), &items)
	assert.NoError(t, err)
}

        	Error Trace:	steps_test.go:23
        	Error:      	Received unexpected error:
        	            	json: cannot unmarshal array into Go value of type string

The bug is caused the code only recognises the text as an array if the first character is [. Any leading whitespace breaks that.
Work-around: trim leading whitespace.


"Tips And Tricks" update

I want to resolve #159 issue.
Implemented:

Detailed description for error wrapper.
Paragraph about markdown syntax support.

Please, review changes.
@avarabyeu
@evjlobanova


docker-bridge-address not documented

The option '--docker-bridge-address' is used/required in the example which creates the aks cluster, but it is not documented. eg what range to choose? how large a range? can it overlap with other address space in the env? etc.

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

ID: 719f4010-810f-b3c7-d807-222b39b20e20
Version Independent ID: 82ac8cfa-b0a2-c77a-408a-ab9aa2b6bce4
Content: Configure kubenet networking in Azure Kubernetes Service (AKS)
Content Source: articles/aks/configure-kubenet.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

@larryms the networking restraints should follow the standard Azure Vnet Properties which you can find here
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq
So in that case, The smallest supported subnet is /29, and the largest is /8 (using CIDR subnet definitions).
As per overlapping, each Vnet is isolated from each other. So the address space can be basically whatever you like. In the above doc there are a few ranges you cannot use. If you are peering multiple Vnets then you would not want the ranges to overlap as it would cause issues. This would fall under general best practices for Vnets in Azure.
All that being said, I will assign to the author to see if it makes sense to link to some of these other virtual network docs to make it more clear.

@MicahMcKittrick-MSFT Per my reading of the these docs, I don't believe the --docker-bridge-address is creating a VNET; rather it's creating a virtual bridge network in the docker space.
To ask the question a different way:  the other three networking parameters ( --service-cidr, --dns-service-ip, and --pod-cidr ) are explained/documented in this document, but the --docker-bridge-address is not.  I'm asking if this parameter can have some explanatory text similar to how the other three parameters are explained.

perhaps linking to this document would be useful (https://docs.microsoft.com/en-us/azure/aks/configure-azure-cni) where there is a little bit more documentation of this parameter

That´s a great question. We are creating a new cluster within our subscription and found ourselves questioning the same thing. I know the docker-bridge-address should not overlap with our VNets and on-prem networks and "<IP_ADDRESS>/16" does overlap. This way we should reserve some range for this and don´t use it anywhere else. How large this network range is got to be, in a way that will allow us to scale up the cluster? We wouldn´t like to "kill" a whole /16 and at the end, a /24 or similar would be enough.
Thank you for any clarification.

The Docker Bridge Address was an issue for our on-prem as well. You can find a more detailed explanation of the docker bridge address here:
https://docs.docker.com/v17.09/engine/userguide/networking/default_network/custom-docker0/

I still dont see any answer for this question. Why was it closed?


incorporate Dr. Xiong's input to add a higher level architecture diagram and description

Signed-off-by: Cathy Hong Zhang<EMAIL_ADDRESS>
What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind design
/kind documentation

@XiaoningDing

Close outdated and unused PR. Global scheduler has its own repo.


[WIP] Silk.NET 2.0

#48

Ignore this, having some issues releasing some preview 1 packages and need somewhere to store this ZIP:
output_packages.zip


Remove logos from Asset Manager when a logo is replaced in Whitehall

This was added in https://github.com/alphagov/whitehall/pull/3503.


View area gradually shrinks when browser is resized

Hi, very cool project!
I noticed that when I open the homepage demo, if I resize the browser window (horizontally) a bunch of times, the displayed animation gets gradually smaller and smaller.
I haven't looked closely, but at first glance it looks like the canvas itself is getting vertically smaller, so I imagine it's a CSS issue with the page, rather than a problem with the rendering per se.
Tested in current Chrome on PC.

Hmm I can't seem to reproduce it..

It's very gradual - if I resize the browser window (horizontally) from quite large to quite small, and then back, the displayed image gets a few pixels smaller.
Now that I check, it only reproduces for me on PC - no issue on chrome/Mac. Could just be a chrome bug..

Could be, I don't recall having any special resizing code in there. Interesting none the less... Let's wait for a next chrome release and re-evaluate. I think it is outside of this project scope.  (I do want to change the main website to be based on docusaurus in the future, maybe that can solve some issues as well)

No idea if the project's rendering is involved, but curiously I noticed that the canvas isn't just scaled down; the illustration parts seem to be affected differently. Here are some images, if you don't have windows handy to check:
Initially:

After resizing a bunch of times - note the woman and the cloud.

Reloading the page fixes things, so just an FYI I guess.

Its not an issue of the player, the issue was in the updating of width/height of the geppetto website. Adding a aspect-ratio: 2 / 1; seems to fix it: https://github.com/matthijsgroen/geppetto/commit/b24b0410997e96d74864cb26b1f351ac37149377
@fenomas  can you verify?

Yes, issue is fixed. Lovely project by the way and thanks for checking!


Adding docs generation support to ansible-creator

Remaining items:

[ ] Switch generation from rst to md?
[x] Fix pre-commit errors

This is not really what I was hoping to see, moving it to draft.

Looks like the signature for subcommands got changed from under this PR yesterday in #110. I'll  go in and check that nothing else is awry before re-readying


using tflite for movenet with some error on parsing data

Hi, I would like to switch the posenet model to movenet model which is more efficient to generate the pose, however, tflite generate the following error.
Initialized TensorFlow Lite runtime.
flutter: Model:success
Assertion failed: (TfLiteInterpreterGetOutputTensorCount(interpreter) == 4), function parsePoseNet, file /Users/tonylu/sdk/flutter/.pub-cache/hosted/pub.dartlang.org/tflite-1.1.2/ios/Classes/TflitePlugin.mm, line 1327.

thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
I think this error is caused due to output format of the model is different than posenet. Is any way I can fix this issue to make movenet work with this awesome plugin?
Tony

Hello tonylu,
did you find a way to run movenet in flutter? If you did can you share a code snippet or example of how you did it? I have been trying to do it and searched everywhere, but it is all unsuccessful.
Thanks

+1

Hello tonylu, did you find a way to run movenet in flutter? If you did can you share a code snippet or example of how you did it? I have been trying to do it and searched everywhere, but it is all unsuccessful. Thanks

still no luck sorry ....

Is this working?
https://github.com/harriseldon/movenet_flutter_example

Any updates


Support for cloudflared cli Args

I don't see a way of configuring command line args for the cloudflared agents configured via ClusterTunnel CRD.
pod describe reveals the current configuration which is the following.
    Args:
      tunnel
      --config
      /etc/cloudflared/config/config.yaml
      --metrics
      <IP_ADDRESS>:2000
      run

I would like to request to be a able to set a custom Args configuration eg
arguments:
  - tunnel
  #- --loglevel
  #- debug
  - -p
  - http2
  - --metrics
  - <IP_ADDRESS>:2000
  - --region
  - us
  - --config
  - /etc/cloudflared/config/config.yaml
  - run

For my setup the http2 protocol and the region are really important for the performance. I hope they are included
Also, if you have your ingress configuration managed by Cloudflare dashboard (and not in cloudflared), you can still use the operator but in this case you would need to remove --config config.yaml from the command line so cloudflared just pulls the ingress configuration from CF. In this case you would need something like this
arguments:
  - tunnel
  - -p
  - http2
  - --metrics
  - <IP_ADDRESS>:2000
  #- --loglevel
  #- debug
  - --region
  - us
  - --no-autoupdate
  - --credentials-file
  - /etc/cloudflared/creds/credentials.json
  - run
  - uuid

I've been thinking of allowing any of the pod spec of cloudflared to be changed as part of the CRD. The first request should be good.
Regarding your second statement on removing the config, this operator works only with the config.yaml. Without it, you could just deploy the cloudflared deployment directly and perform configuration on the CF dashboard.

this operator works only with the config.yaml. Without it, you could just deploy the cloudflared deployment directly and perform configuration on the CF dashboard.

Fair enough. Sure, you can do that, but you would still need to create and manage the tunnels and their secrets externally which is something that the operator can nicely do for you. I am not personally interested for this feature, I've just added for the sake of completeness.

I've been thinking of allowing any of the pod spec of cloudflared to be changed as part of the CRD. The first request should be good. See #73

Good to see it's on the roadmap!

Even the official chart relies solely on the config file. I wouldn't want to diverge too much from "upstream" in that regard.

The Upstream here is Cloudflare Zero Trust and not the chart for cloudflared. They are the ones who offer cloudflare-managed tunnel configurations in the first place and the instructions to run cloudflared with a cloudflare-managed tunnel config does not include the --config arg at all. eg
docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token secret

IMO there is no diverge here, there is only support for both options and in an easy way too; by providing the option of fully controlling the arguments in values.yaml.


Single-port memory inference error (Yosys + ISE)

I was comparing Yosys against ISE and Vivado, using examples provided by Xilinx. I found only this problem related to a Single-port memory inference when synth_xilinx with -ise- option is used with ISE as backend.
// Single-Port BRAM with Byte-wide Write Enable
// Read-First mode
// Single-process description
// Compact description of the write with a generate-for
//   statement
// Column width and number of columns easily configurable
//
// bytewrite_ram_1b.v
//

module bytewrite_ram_1b (clk, we, addr, di, do);

parameter SIZE = 1024;
parameter ADDR_WIDTH = 10;
parameter COL_WIDTH = 8;
parameter NB_COL = 4;

input clk;
input [NB_COL-1:0] we;
input [ADDR_WIDTH-1:0] addr;
input [NB_COL*COL_WIDTH-1:0] di;
output reg [NB_COL*COL_WIDTH-1:0] do;

reg [NB_COL*COL_WIDTH-1:0] RAM [SIZE-1:0];

always @(posedge clk)
begin
    do <= RAM[addr];
end

generate genvar i;
for (i = 0; i < NB_COL; i = i+1)
begin
always @(posedge clk)
begin
    if (we[i])
        RAM[addr][(i+1)*COL_WIDTH-1:i*COL_WIDTH] <= di[(i+1)*COL_WIDTH-1:i*COL_WIDTH];
    end
end
endgenerate

endmodule

The Yosys command:
yosys -Q -p "read_verilog bytewrite_ram_1b; synth_xilinx -top bytewrite_ram_1b -family xc7 -ise; write_edif -pvector bra yosys.edif"

The ISE error message (when mapping):
...
Phase 12.34  Placement Validation (Checksum:847cfe79) REAL time: 26 secs

Total REAL time to Placer completion: 26 secs
Total CPU  time to Placer completion: 26 secs
Running post-placement packing...
Writing output files...
ERROR:PhysDesignRules:2378 - Issue with pin connections and/or configuration on
   block:<RAM.0.0.0>:<RAMB36E1_RAMB36E1>.  The cascadable BlockRam feature is
   not used for port A (RAM_EXTENSION_A set to NONE). The highest order port A
   address bit (ADDRARDADDRL15) must be tied to LOGIC 1.
ERROR:PhysDesignRules:2379 - Issue with pin connections and/or configuration on
   block:<RAM.0.0.0>:<RAMB36E1_RAMB36E1>.  The cascadable BlockRam feature is
   not used for port B (RAM_EXTENSION_B set to NONE). The highest order port B
   address bit (ADDRBWRADDRL15) must be tied to LOGIC 1.
ERROR:Pack:1642 - Errors in physical DRC.

Mapping completed.
See MAP report file "bytewrite_ram_1b_map.mrp" for details.
Problem encountered during the packing phase.

Design Summary
--------------
Number of errors   :   3
Number of warnings :  81

Process "Map" failed
...

There are other (very similar, but no-change instead of read-first) file with exactly the same problem.
//
// Single-Port BRAM with Byte-wide Write Enable
//   4x9-bit write
//   No-Change mode
//   Single-process description
//   Compact description of the write with a generate-for statement
//   Column width and number of columns easily configurable
//
// Download: ftp://ftp.xilinx.com/pub/documentation/misc/xstug_examples.zip
// File: HDL_Coding_Techniques/rams/bytewrite_nochange.v
//
module v_bytewrite_nochange (clk, we, addr, di, do);

  parameter SIZE	= 1024;
  parameter ADDR_WIDTH  = 10;
  parameter COL_WIDTH	= 9;
  parameter NB_COL	= 4;

  input 			     clk;
  input      [NB_COL-1:0]	     we;
  input      [ADDR_WIDTH-1:0]	     addr;
  input      [NB_COL*COL_WIDTH-1:0]  di;
  output reg [NB_COL*COL_WIDTH-1:0]  do;

  reg	     [NB_COL*COL_WIDTH-1:0]  RAM [SIZE-1:0];

  always @(posedge clk)
  begin
    if (~|we)
      do <= RAM[addr];
  end

  generate
  genvar i;
    for (i = 0; i < NB_COL; i = i+1)
    begin
      always @(posedge clk)
      begin
        if (we[i])
          RAM[addr][(i+1)*COL_WIDTH-1:i*COL_WIDTH]
	    <= di[(i+1)*COL_WIDTH-1:i*COL_WIDTH];
      end
    end
  endgenerate

endmodule

Here a similar write-first example which works (is implemented without errors):
//
// Single-Port BRAM with Byte-wide Write Enable
//   4x9-bit write
//   Write-First mode
//   Single-process description
//   Compact description of the write with a generate-for statement
//   Column width and number of columns easily configurable
//
// Download: ftp://ftp.xilinx.com/pub/documentation/misc/xstug_examples.zip
// File: HDL_Coding_Techniques/rams/bytewrite_writefirst.v
//
module v_bytewrite_writefirst (clk, we, addr, di, do);

  parameter SIZE	= 1024;
  parameter ADDR_WIDTH  = 10;
  parameter COL_WIDTH	= 9;
  parameter NB_COL	= 4;

  input 			     clk;
  input      [NB_COL-1:0]	     we;
  input      [ADDR_WIDTH-1:0]	     addr;
  input      [NB_COL*COL_WIDTH-1:0]  di;
  output reg [NB_COL*COL_WIDTH-1:0]  do;

  reg	     [NB_COL*COL_WIDTH-1:0]  RAM [SIZE-1:0];

  generate
  genvar i;
    for (i = 0; i < NB_COL; i = i+1)
    begin
      always @(posedge clk)
      begin
        if (we[i])
	 begin
          RAM[addr][(i+1)*COL_WIDTH-1:i*COL_WIDTH]
	    <= di[(i+1)*COL_WIDTH-1:i*COL_WIDTH];
          do[(i+1)*COL_WIDTH-1:i*COL_WIDTH]
	    <= di[(i+1)*COL_WIDTH-1:i*COL_WIDTH];
         end
        else
          do[(i+1)*COL_WIDTH-1:i*COL_WIDTH]
	    <= RAM[addr][(i+1)*COL_WIDTH-1:i*COL_WIDTH];
      end
    end
  endgenerate

endmodule

@mwkmwkmwk these are examples from Xilinx, let me know if I can help you, providing own made minimalistic examples. Maybe I could put them somewhere under tests/memories. The same offer for #1809. I can provide the Verilog files and the scripts to run automatically from the command-line.

I think that one should be closed by #2900


Upgrading the main Snoop project to .NET 4.0 for real this time. This…

… necessitated adding the Nuget package for PowerShell 5.

This effort was done in a different pull request.


Fixed wrapping of long values in technical 500 debug page.

As coincidence would have it (given #15251 proposes the same fix elsewhere), I've just opened up a project and noted I had a looooong horizontal scrollbar  (4.0 and 3.2 both exhibit it) because of some env var shenanigans (thanks, direnv :)). Here's a quick proposed fix for that.
Unlike that PR, I don't have a ticket to reference.
Before:

After:

@kezabelle Thanks :+1:


WeldInitiator enhancements to allow per-method Weld setup

The @ExtendWith annotation is permitted on both types and methods.  When placed on methods, the referenced extensions apply only to the annotated method.  The @WeldSetup annotation and related WeldInitiator can not be used to provide customized set-ups for multiple annotated methods.
This issue is a feature request to provide a means of setting-up the Weld container on a per method basis.  One possibility is to add member attributes to @EnableWeld to allow classes, beans and packages to be declaratively specified.

@smoyer64 Thanks for the issue but to be honest I don't like this idea very much. The original idea was to share the container configuration for all test methods. If we allow to configure container per test method things get more complicated and unclear:

I cannot see any significant improvement in UX or appropriate use case
The annotation approach is very limited
What happens if I configure the cotainer both on the class level and on the method level?

@mkouba - What was the rationale for the original idea?

The original idea was to share the container configuration for all test methods.

I actually prefer the look of the annotation-based configuration but agree that it's more limited than the WeldInitiator but I don't have a concrete use case.  I'm imagining a few that I haven't actually run into yet.  Can we just leave this (and the associated PR) open for a few days while I code up more tests?
As far as annotating both the class and the method, just like with other JUnit 5 constructs, the method will always take precedence.

Can we just leave this (and the associated PR) open for a few days while I code up more tests?

Of course. We're always open for discussion ;-)

While I see the benefit of the PR, I think it's very limited use-case and would eventually lead to bloating the annotation with more and more config options (as there would be more and more possible uses).
You can always have an extra class with the test which requires special handling and set it up there.
We can of course leave it open for a while and keep the ideas flowing.

I second the request, a per-method setup would keep the code neat without leaving a huge initialization on startup

This issue is outdated, so I'll close it.
JUnit5 extensions support both test instance lifecycles, as per JUnit 5 specification.


Add 181 to 190 tea-time images

Add 181 to 190 tea-time images

Tea time 181 to 190 merged. Thanks 👍


[d3d9] Black Mesa lighting breaks on Intel, but is fixed with AMD vendor ID

Software information
Black Mesa (362890)
System information

GPU: Intel Corporation DG2 [Arc A380] (rev 05)
Driver: Mesa 22.2.3
Wine version: Proton Experimental
DXVK version: 2.0

Screenshots
d3d9.customVendorId = 8086

d3d9.customVendorId = 1002

Quick note that this even happens when you on Windows spoof the vendor id to Intel without dxvk.
This was tested on a AMD R9 380 so dunno if anything is actually different with Intels own d3d9 driver.

Quick note that this even happens when you on Windows spoof the vendor id to Intel without dxvk. This was tested on a AMD R9 380 so dunno if anything is actually different with Intels own d3d9 driver.

Apologies, but from this wording you're saying on Windows it is possible to spoof the vendor id to something else without DXVK, how is this possible?

Apologies, but from this wording you're saying on Windows it is possible to spoof the vendor id to something else without DXVK, how is this possible?

https://www.pcgamingwiki.com/wiki/Black_Mesa#Flashlight_not_working_on_Intel_GPU
It's a launch argument for Black Mesa


BUG: cni config field is required but tagged as optional

Hey there, I'm using talhelper first time. Everything works great!
I encounter an issue with the cni config. In the documentations it is marked as optional but when I don't specify it talhelper genconfig throughs an error:

If it is really an bug, I can provide an fix but don't investigate it for now.
Thanks
Tom

Hey @tzabbi, thanks for reporting!
I just tried genconfig command locally without cniConfig specified and the command ran fine. Can you provide your talconfig.yaml?

The check will only run if cniConfig is defined: https://github.com/budimanjojo/talhelper/blob/94c2348d36537b917975a82c0089e5b454995445/pkg/config/validator.go#L196
Are you sure you don't have it defined somewhere in your config file? Also make sure you're running the latest version of Talhelper.

Strange I cloudn't reproduce it. So I will close it. Sorry for the inconvenience.


README for 0.1 branch.

If this is way off base, I'd welcome a link to an example in which it's "done right," a doc of best practices, etc.
Thanks again for the recommendation.

(And if there are ways in which I got the branch itself wrong, etc., don't hesitate to let me know about that, too.)

W.r.t. the CLA warning: there's a CLA linked to the work email address I use for "regular" commits, but apparently there's no CLA linked to my personal/primary email address, which is the one Github uses for the PR code suggestion feature. Will look into linking the other address later today.

@googlebot I fixed it.

Looks like this repository has two Google bots :smile:

Two Google bots, two Stephans... :)
I might have set up an extra one for the repo when one was already set up for the organization? I've removed the per-repo one. We'll see what happens.

And thanks for getting that taken care of. I was envisioning losing an afternoon over the casing of two letters :)

Thanks also for the comment on the branch name. I'm not sure I can predict at this point how we'll be navigating from here to 1.0. But it at least seems fair to say that we're not going to go back and make an emergency patch release of 0.1.1, so I don't see much need for a long-lived release-0.1 branch. I'll do the rename after I merge this.

https://github.com/jspecify/jspecify/tree/release-0.x
I think I did the branch rename in some suboptimal way, so I ended up wiping my local clone and my GitHub fork just to be safe.

I still got a googlebot response on https://github.com/jspecify/jspecify/pull/120, so my per-repo googlebot looks to have been redundant. I had technically just disabled it earlier, so now I'll remove it for good.


Secure initialization for SQL databases

Just want to say that I think this is a great project, even though it's still in beta. Keep up the good work!
I noticed in the docs for configuring databases that you seem to recommend using the root user's login credentials for SQL databases. Best practice would be to advise users to create a new user for each service, then grant that user privileges only on the app's database. Granting root user access to an app is risky.
(As a side note, consider adding support for reading the connection string from a secure file to support services like Docker Secrets).
To guide users towards secure practices I propose adding the following steps to space-cloud init when a SQL database is selected:

Ask the user to temporarily provide root user access to the database
Create a new database (ask for a name on the command line, default to the project name)
Create a new user and grant them all privileges on the new database

Ask for a user name, default to the database name + "_space-cloud"
Ask for a password, using a randomly generated password as a default. Require them to retype the password for confirmation.

Format the user's credentials and the database name into the connection string

For ease of use you could also automatically initialize the users table, but that could be its own issue.
Hope this helps!

Hey @ollykel!! That's actually a great suggestion! A quick clarification though. We do not recommend, using the root user at all. We should reflect that in the docs though. Also, currently you as the user have to create the database user roles and define the roles and tables.

(As a side note, consider adding support for reading the connection string from a secure file to support services like Docker Secrets).

We should absolutely do that. Can you raise a separate ticket for that??

For ease of use you could also automatically initialise the users table, but that could be its own issue.

We should definitely do that. But how can we accomodate the fields the user might want to capture? We do not restrict the user to the columns allowed in the users table. The are a few minimum columns which needs to be there, but apart from that you can add multiple columns.

The user can always log into the database as an admin after it has been initialized and add new columns to the users table:
ALTER TABLE users ADD COLUMN foobar VARCHAR(64);

This way the minimum columns will be there, but the user will not be restricted to them.
Creating a new database and user and granting privileges only takes a few queries, so that should be manageable. Other than initializing the users table, it probably is best to leave creating tables to the user for the near future, since creating an ORM that can manage tables and migrations like Django can be time-consuming.

Awesome! I understand your point better now. I'm taking two things away from this. Prompt me if i missed anything.

There should be a better way to manage secrets like db connections (we already have an issue on that open)
Auto set-up the users table to make life a lot easier

Can you create another ticket for the second point?

Great! That was essentially the point of this issue. Also remember to change the default conn strings for sql-mysql and sql-postgres to use a different username than root.

Perfect! So @ollykel can you open up two tickets? One for correcting the docs and one for auto creating the users table?
We can't use this ticket since the title seems to suggest something else.

The appropriate issues have been opened here: #150, #158, and #159. Hence closing this one!


Add --config-file to the CLI

The .backportrc.json file name is hardcoded at https://github.com/sqren/backport/blob/b14d9778be41be8ccdbd0a936821b9e19549a095/src/options/config/projectConfig.ts#L5
which makes it impossible to provide another name.
My use case is to allow developers to run backport locally using a specific configuration, and use another configuration when the backport is done in the CI/CD.
surfacing a --config-file option that defaults to .backportrc.json will allow this.
Happy to contribute a patch if @sqren thinks that sounds good

I've been thinking about this myself but didn't get around to it.
A PR is very welcome


Integration Test - Release - 2021/09/29 03:03:55

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#reassign PRMergerTest2

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#please-close


Issues in CCS811 sensor reading

The following are the issues we are having with the ccs811 sensor.

If we are moving a sensor from places where there is a high level of gas to a low level of gas. The sensor is taking a large amount of time to settle down to the actual gas level of that place.

We have noticed that sometimes there are sudden jumps in CO2 and TVOC values.

If sensors exposed to the high level of Co2 and TVOC  ( Co2: 2000 to 2500 TVOC: 400 to 800) constantly for more than 4 to 5 weeks they are getting damaged after that those sensors are reporting co2 value of nearly around 400 to 500 even if it is exposed to the higher level of gas.

Following is the initialization flow of the Gas sensor

Turn on the sensor.
Initialize sensor in PulseHeat drive mode (10-second interrupt).
Update temperature and humidity at every 2-second interval.
After a reset or a startup Wait for 30 min for the gas sensor to adjust according to the environment and then write the previously-stored baseline value if present else stores the baseline.

Following Hardware we are using

Microcontroller : nRF52832.
Temperature and humidity sensor: HTS221.
Gas sensor:  CCS811

Please let us know, what is going wrong in the initialization process of the sensor resulting in these issues
Below is the flow chart for the reference

Hi I'm software developer, and these questions require an expert on MoX sensors.
One thing in your flow chart triggers me, and that is in the areas of baseline management. You correctly wait for the sensor to settle before using reading or writing the baseline. That's good. But it also suggests that you "backup" the baseline from sensor to mcu once, 30 minutes after startup. I believe the application note suggests to backup just after switching off the sensor (if it has been on long enough).
Another question: did you write the humidity and temperature values in the correct format? These are a bit obscure.

Thanks for the reply, I have checked in my Firmware I am writing temperature and humidity in a correct format as mentioned in the datasheet


Automated cherry pick of #1111: fix: image-show missing can-delete/can-update fields

Cherry pick of #1111 on release/2.10.0.
#1111: fix: image-show missing can-delete/can-update fields

Codecov Report

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

@@               Coverage Diff                @@
##             release/2.10.0   #1134   +/-   ##
================================================
  Coverage                  ?   7.91%
================================================
  Files                     ?     357
  Lines                     ?   56855
  Branches                  ?       0
================================================
  Hits                      ?    4499
  Misses                    ?   51957
  Partials                  ?     399

Flag
Coverage Δ

#aFlag
7.91% <0%> (?)

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 083bc1c...04a9997. Read the comment docs.


anomalous dipole moment

find references for the dipole moment of a proton, a neutron, a deuteron, and He3 from PDG. Write a code to pull down the measured moment and get the anomalous part of it, returning a vector.

I think there is no data for deuteron and He3, here are all the particles PDG have: https://pdg.lbl.gov/2023/mcdata/mass_width_2023.txt

I'll handle this, I actually found the values I'm looking for