update the concourse-pulumi-resource to support k8s / eks

Description/Context
https://github.com/mitodl/concourse-pulumi-resource
This resource needs to have kubectl added to the docker file and it needs to be available on the default $PATH.
Per: https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#pre-requisites
Plan/Design

Testing my changes:
~/src/mit/concourse-pulumi-resource (cpatti_add_kubectl*) » docker build -t concourse-pulumi .                                                                     feoh@prometheus
[+] Building 8.1s (11/11) FINISHED                                                                                docker:default
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 528B                                                                                0.0s
 => [internal] load metadata for docker.io/pulumi/pulumi-python:3.134.1@sha256:d511ca9487de9aa47f34f862b0d660c82a5b8e5d0b60d205a2755b6b48b3f63f                               1.1s
 => [auth] pulumi/pulumi-python:pull token for registry-1.docker.io                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [1/5] FROM docker.io/pulumi/pulumi-python:3.134.1@sha256:d511ca9487de9aa47f34f862b0d660c82a5b8e5d0b60d205a2755b6b48b3f63f                                                 5.1s
 => => resolve docker.io/pulumi/pulumi-python:3.134.1@sha256:d511ca9487de9aa47f34f862b0d660c82a5b8e5d0b60d205a2755b6b48b3f63f                                                 0.0s
 => => sha256:fdeeec85abbad3878f2008f9445f15a19a5a224d1b7e7715ac6b923072333e57 14.74MB / 14.74MB                                                                              0.8s
 => => sha256:d511ca9487de9aa47f34f862b0d660c82a5b8e5d0b60d205a2755b6b48b3f63f 743B / 743B                                                                                0.0s
 => => sha256:e0cc5452ef7d35f50cdd6ddb3afb12697365b83fa25c23e4b9ca505fd442e1ba 7.36kB / 7.36kB                                                                                0.0s
 => => sha256:302e3ee498053a7b5332ac79e8efebec16e900289fc1ecd1c754ce8fa047fcab 29.13MB / 29.13MB                                                                              0.9s
 => => sha256:4c0965d3919510b506d8856ebc050a96e996c7dae96e4fb420882dbe7e037e67 3.51MB / 3.51MB                                                                                0.5s
 => => sha256:38e789cf6b2559a138ce3ec4af10d5d571be9248816776959866ff9f74ab0a51 2.42kB / 2.42kB                                                                                0.0s
 => => sha256:62a08b8dd4f53ad5493dabf2af00ccde91abb3771fb2187040bcf2fe94a7ced7 248B / 248B                                                                                0.7s
 => => sha256:0ca5c0b40ad56eb0ac0e1bbddf8b56985467b4ecbead0974cd2a590d3b27dd70 121B / 121B                                                                                0.9s
 => => sha256:ba3dcbe651c16bd241f1d1d14e7e5f316e982d8ab5fdefc44f0c50093cfa6d43 176B / 176B                                                                                1.1s
 => => sha256:bcf3cea15759ec7b19ed4c6d3bb07d42ec99ba0ccf7d84a6d5c6934de4fe4e7e 48.66MB / 48.66MB                                                                              2.5s
 => => extracting sha256:302e3ee498053a7b5332ac79e8efebec16e900289fc1ecd1c754ce8fa047fcab                                                                                1.0s
 => => sha256:cb0ea48542a3d441eec739ea333c57b8397151906c6507217955471bf6c0db33 47.37MB / 47.37MB                                                                              2.8s
 => => sha256:c2fb83ab8cd9c88fe261be0e7ae91f832d87d34811c85695d743aacd431ee156 43.26MB / 43.26MB                                                                              2.8s
 => => extracting sha256:4c0965d3919510b506d8856ebc050a96e996c7dae96e4fb420882dbe7e037e67                                                                                0.1s
 => => extracting sha256:fdeeec85abbad3878f2008f9445f15a19a5a224d1b7e7715ac6b923072333e57                                                                                0.6s
 => => sha256:e243b23ed3c75327d64a834eb6788825f71340cf8a87a81140f76680fbfc654f 26.39MB / 26.39MB                                                                              3.2s
 => => extracting sha256:62a08b8dd4f53ad5493dabf2af00ccde91abb3771fb2187040bcf2fe94a7ced7                                                                                0.0s
 => => extracting sha256:0ca5c0b40ad56eb0ac0e1bbddf8b56985467b4ecbead0974cd2a590d3b27dd70                                                                                0.0s
 => => extracting sha256:bcf3cea15759ec7b19ed4c6d3bb07d42ec99ba0ccf7d84a6d5c6934de4fe4e7e                                                                                0.8s
 => => extracting sha256:cb0ea48542a3d441eec739ea333c57b8397151906c6507217955471bf6c0db33                                                                                0.9s
 => => extracting sha256:ba3dcbe651c16bd241f1d1d14e7e5f316e982d8ab5fdefc44f0c50093cfa6d43                                                                                0.0s
 => => extracting sha256:c2fb83ab8cd9c88fe261be0e7ae91f832d87d34811c85695d743aacd431ee156                                                                                0.3s
 => => extracting sha256:e243b23ed3c75327d64a834eb6788825f71340cf8a87a81140f76680fbfc654f                                                                                0.2s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 11.94kB                                                                                0.0s
 => [2/5] WORKDIR /opt/resource                                                                                0.2s
 => [3/5] COPY bin/* /opt/resource/                                                                                0.0s
 => [4/5] COPY lib/* /opt/resource/lib/                                                                                0.0s
 => [5/5] RUN  /usr/bin/curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/b  1.5s
 => exporting to image                                                                                0.1s
 => => exporting layers                                                                                0.1s
 => => writing image sha256:20ffd8b2574ee5d384a178f9d35b2f42c1afc89ca79b99cb0cdd151d83a2df76                                                                                0.0s
 => => naming to docker.io/library/concourse-pulumi                                                                                0.0s
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
~/src/mit/concourse-pulumi-resource (cpatti_add_kubectl*) » docker run -it concourse-pulumi                                                                        feoh@prometheus
# kubectl
kubectl controls the Kubernetes cluster manager.

 Find more information at: https://kubernetes.io/docs/reference/kubectl/

Basic Commands (Beginner):


bun: 1.1.10 -> 1.1.13

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bun is: Incredibly fast JavaScript runtime, bundler, transpiler and package manager – all in one
meta.homepage for bun is: https://bun.sh
meta.changelog for bun is: https://bun.sh/blog/bun-v1.1.12
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.12 with grep in /nix/store/lc6nx3bvkjk8k1wspp7iia0xr9ln23i4-bun-1.1.12
found 1.1.12 in filename of file in /nix/store/lc6nx3bvkjk8k1wspp7iia0xr9ln23i4-bun-1.1.12

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

bun
helix-gpt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lc6nx3bvkjk8k1wspp7iia0xr9ln23i4-bun-1.1.12 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bun https://github.com/r-ryantm/nixpkgs/archive/ebacdaba09d5f20e649807f3e82cd38a52659276.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ebacdaba09d5f20e649807f3e82cd38a52659276#bun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lc6nx3bvkjk8k1wspp7iia0xr9ln23i4-bun-1.1.12
ls -la /nix/store/lc6nx3bvkjk8k1wspp7iia0xr9ln23i4-bun-1.1.12/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

bun
helix-gpt

Maintainer pings
cc @DAlperin @06kellyjac @thilobillerbeck @cdmistman @coffee-is-power for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bun is: Incredibly fast JavaScript runtime, bundler, transpiler and package manager – all in one
meta.homepage for bun is: https://bun.sh
meta.changelog for bun is: https://bun.sh/blog/bun-v1.1.13
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.13 with grep in /nix/store/miprrhmllrsvfjsj6y96ivb92p2l9dp8-bun-1.1.13
found 1.1.13 in filename of file in /nix/store/miprrhmllrsvfjsj6y96ivb92p2l9dp8-bun-1.1.13

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

bun
helix-gpt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/miprrhmllrsvfjsj6y96ivb92p2l9dp8-bun-1.1.13 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bun https://github.com/r-ryantm/nixpkgs/archive/01aed33c9153a59b0cf642d1ebd351a3f0d53e83.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/01aed33c9153a59b0cf642d1ebd351a3f0d53e83#bun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/miprrhmllrsvfjsj6y96ivb92p2l9dp8-bun-1.1.13
ls -la /nix/store/miprrhmllrsvfjsj6y96ivb92p2l9dp8-bun-1.1.13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

bun
helix-gpt

Maintainer pings
cc @DAlperin @06kellyjac @thilobillerbeck @cdmistman @coffee-is-power for testing.

Pinging @NickCao and @matthiasbeyer based on previous approvals of these PRs.
These 3 updates contain really important fixes that allow many NodeJS projects to start for the first time, so would be nice to have it merged. Thanks for your time!


the lambda in the option_parser.py is different from the paper

Hi, when I read the source code, I find that the lambda set in the option_parser.py is different from the paper set, like the lambda_ee in the paper is 2 but is 100 in the option_parse.py. Have I missed something important?

Sorry for our negligence. It should be 100 and we didn't fix it in the paper.

Sorry for our negligence. It should be 100 and we didn't fix it in the paper.

Thanks for your reply! And I find that there is a extra rec_loss_global which seems to never appear in the paper. Would you mind telling me why using it here? And in the adv loss, the code use the pos as input, but the paper use the rotation as input. Is that better for using the pos as input for discriminator?

We treat rec_loss_global as part of the rec_loss. It is an extra penalization over global position. It helps a lot with the global stability of output.
In adv_loss, the paper says both rotation and offset. We find using joint position is enough and joint position contains both (part of) rotation and offset information.

We treat rec_loss_global as part of the rec_loss. It is an extra penalization over global position. It helps a lot with the global stability of output.
In adv_loss, the paper says both rotation and offset. We find using joint position is enough and joint position contains both (part of) rotation and offset information.

Do you mean that using joint position is better than use the rotation and offset?And why does the rec_loss_global use motion divided by height as input?

We find that using position has same effect as literally using rotation + offset but easier to stabilize.
rec_loss_global is penalization over global position. Characters with different height have different scale of global position. Here dividing by height aims to normalize it.

But the motion is quaternion in the code. Can we use quaternion dividing by height as the representation of the global position?

I'm afraid you misunderstood the code. Motion consists both joint rotation and global position part. The rec_loss_global is only applied on global position part.

Thanks! I got it!


Sky was very bright for TILEID=6991 through NIGHT=20221113

The sky was very bright for tile 6991 on 11/13. The redshifts look reasonable, but there are ZSKYCHI2PDF alerts across multiple petals:
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/6991/20221113/tile-qa-6991-thru20221113.png
From Eddie on Slack:
The sky is really quite bright for 6990 and 6991.  Let's mark the former as good and make a ticket for the latter as unsure; I'll probably ask for it to be marked bad.

Sorry, you're ahead of me, awesome.  Yes, let's go ahead and mark both 153313 and 153314 on 6991 as bad and reprocess due to the slight pileup at z=1.4 and 1.8.  Thanks!

@schlafly to clarify for 20221113, can you fill in the "BAD" column with "yes" or "no" below? Thanks!
TILEID   EXPID  BAD
  6990  153312    ?
  6990  153313    ?
  6991  153314    ?
  6991  153315    ?

Thank you for catching my error.  This looks good to me.  I will reQA and close.


Keeps waiting for Valorant to Launch, Eventually terminates

I tried many methods to get it working, used the release 2.3 when it came out, tried reinstalling, tried building from source, tried running as admin, tried launching after game, gave up and waited patiently for 2.4 to release literally.... everything that came to my mind but I'm having trouble actually getting it to work.
What happens is the CLI runs and waits for the game to open, the game launches, but the rpc doesn't detect the game and eventually terminates itself due to "Valorant not running"

I've had the same issue. Neither I nor the owner knows what's the problem. I looked at the source, there's no problem at all.
I fixed it by cloning the git repo instead and added my own batch file program to execute the main python application.
I then created my own shortcut with the red icon located at the assets folder so I can open it via start menu


Updated to version 2.3.0

See https://bastion.js.org/changes for details.

Travis OS X builds are not proceeding because they are under maintenance.


Error: ffmpeg vmaf exit code Some(1)

Hi @alexheretic, many thanks for this contribution!
Unfortunately I haven't been able to debug a blocker and a major annoyance with the utility.(on Ubuntu 21.10):

Regardless of the command used, the process fails with "Error: ffmpeg vmaf exit code Some(1)". I tried using ffmpeg-build-script to install ffmpeg and its dependencies, libvmaf should be 2.2.1 (I see you mentioned 1.5.3 as the min requirement?) and I've also compiled the latest vmaf cli and include it in the path ($ ./vmaf --version -> 9e1fb0bb). I don't see anything obvious in VmafOut.
After this failure, I can no longer see my terminal's input buffer, and I have to open a new terminal/tab to return to normal (reset doesn't work). This affects all my terminals and terminals emulators (guake, alacritty, terminator, mate's).

Any thoughts on how we can debug this?

Can you try running vmaf via ffmpeg directly? Something like:
ffmpeg -i vid.av1.mp4 -i vid.mp4 -lavfi libvmaf -f null -

It's possible that you need to specify the model for your version of vmaf? (I tested with v1.5.3, and more recently v2.3.0, on arch both worked without any extra args)
I aim to improve error output #1
Regarding 2. I'm not sure why this would break your terminal, I'll try to reproduce this.

I got vmaf to work in a ubuntu 21.10 vm by using ffmpeg static and downloading https://github.com/Netflix/vmaf/blob/master/model/vmaf_v0.6.1.json then specifying ... -lavfi libvmaf=model_path=vmaf_v0.6.1.json ...
You can specify the same thing with ab-av1 with --vmaf model_path=vmaf_v0.6.1.json
Ubuntu is quite painful to use though, nothing useful is in the repos.

Was indeed my fault: a) libvmaf wasn't enabled (I recompiled with it and make sure I had a full static build and it's all good), and b) the models can be installed under /usr/local/share/model, but it's easier to override the path as you said! Thanks :)

As for 2. my uneducated guess is that the failure leads to some wayward escape code messing things up, but curiously a reset doesn't solve it. I wouldn't expect it to be a problem with Gnome3/Xorg because existing or new terminals are fine. I will experiment a bit more and see whether it will reoccur on successful invocations.

I'm getting this same error, could you post your ffmpeg compile flags? here are mine:
./configure --enable-gpl --enable-libx264 --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64 --enable-gpl --enable-libx265 --enable-libsvtav1 --enable-libass --enable-libopus --enable-libdav1d --enable-libvmaf --enable-avfilter --enable-static

I've tried both workarounds you specified and I get errors with the ffmpeg test command
libvmaf INFO `compute_vmaf()` is deprecated and will be removed in a future libvmaf version
libvmaf ERROR could not read model from path: "/usr/local/share/model/vmaf_v0.6.1.pkl"
libvmaf ERROR support for pkl model files has been removed, use json
libvmaf ERROR problem loading model file: /usr/local/share/model/vmaf_v0.6.1.pkl
[Parsed_libvmaf_0 @ 0x5608b8c39500] libvmaf encountered an error, check log for details
Error while filtering: Invalid argument
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #1:0
Conversion failed!

with workaround
libvmaf INFO `compute_vmaf()` is deprecated and will be removed in a future libvmaf version
libvmaf ERROR could not read model from path: "/usr/local/share/model/vmaf_v0.6.1.json"
libvmaf ERROR problem loading model file: /usr/local/share/model/vmaf_v0.6.1.json
[Parsed_libvmaf_0 @ 0x55be808fbd40] libvmaf encountered an error, check log for details
Error while filtering: Invalid argument
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #1:0
Conversion failed!

I've downloaded the file to /usr/local/share/model/vmaf_v0.6.1.json, with 664 permissions. I'm on Ubuntu 18.04

I've added a wiki page to capture some steps that can help on older linux distros.

On windows there is still this error.
Probably because of https://github.com/Netflix/vmaf/issues/424
It is possible to pass an argument to specify vmaf model path?

You can pass ffmpeg vmaf args using --vmaf ARG see https://ffmpeg.org/ffmpeg-filters.html#libvmaf
So something like --vmaf model=path=..., or maybe --vmaf model_path=... for older vmaf.

Also if you find some workarounds this may be worth adding to https://github.com/alexheretic/ab-av1/wiki/Troubleshooting

Thanks, I only saw after your clarification that there was the topic --vmaf.
I was able to get it to work on Windows with this template:
--vmaf '"model_path=C/:path\path 2\vmaf_v0.6.1.json"'
If it is of interest I share the .bat that automates the search also for preset of a video file passed as argument.
https://github.com/Werve/ab-av1/blob/main/Windows_cfr_search.bat


Add the possibility to provide custom color mapping for channels in raw.plot()

Describe the new feature or enhancement
Hello,
I think that it would be nice to have the possibility to have a custom color mapping control based on the provided channel names, because it doesn't seems to be possible so far. Please correct me if I am wrong.
Here is an example of a default raw.plot()

And for example I would like to plot every SFG channel into red, and MFG into green.
Describe your proposed implementation
One way would be to provide a dict in the color arg*, the key of the dict should be the channel name and the value should be the desired color.
color = {'SFG, Left':'red',  'SFG, Right':'red',  'MFG, Left':'green', 'MFG, Right':'green'}
raw.plot(color=color)

Describe possible alternatives
One of the possible alternative would be to change colors for specific channel would be to change the ch_types of the desired ch_names. basically assigning SFG to EMG types, MFG to EEG and so on, but it's not really convenient.
Additional context
Thank you!

seems like a reasonable feature request. Are you interested in implementing it yourself? As a purely aesthetic change it might be a bit before it reaches the top of our core devs' priority queues.


Type safe Middlewares

Hi,
I'd like to suggest a change that may make building middlewares a bit more intuitive and help to avoid ordering problems and ease development.
Right now, in order to create a pipeline, you use addLast on ChannelPipeline, and the code that involves actual processing usually has a lot of instanceOf and casts to the particular type.
Having a typed pipeline, for example:
pipeline.inbound(new FrameDecoder<List<Frame>>())      // Starts with ByteBuf, returns list of Frames
        .next(new MessageDecoder<Message>())      // Receives List<Frame> and returns the Message
// etc

And same way for the outbound.
Somewhat similar approach is used in the SimpleChannelInboundHandler<I>, although there are no type cheks for the next handler in the pipeline whether the type used for this handler is matching the type that the next handler is expecting.
For example, in Http2 case, the general workflow is ByteBuf -> Frame -> Frame (for SessionHandler) -> HttpMessage -> Frame -> ByteBuf, although, once again, the types aren't specified explicitly everywhere explicitly. It would be easier to compose same middlewares if the incoming and outgoing types of each handler were specified and type-checked during compilation.
In the end, this is just a different way of composition, maybe somewhat more "reactive" interface, although the idea comes more from the middleware approach.

less instanceof checks sounds good to me... were you considering submitted a PR @ifesdjeen ?

I'll work on a PR for HTTP2, as it's something I happen to use the most.

@ifesdjeen - How do you use HTTP/2 w.r.t to the channel pipeline? Can you provide an example? HTTP/2 in general (with the exception of the HTTP/1.x translation layer) is a bit of an outlier in how it interacts with the pipeline.

I thought it'd be rather standard: SslHandler -> HttpChooser -> HttpServerCodec -> HttpServerUpgradeHandler -> endHander
Pretty much the same exact way it was in examples and in the code we've seen publically available, so nothing very special in our setup.
My thinking was that middlewares such as routing, cookies etc are mostly headed out to the endHandler code. Having everything typed it'd be possible and quite simple to add more middleware layers that would be treated as first class citizens.
I will make a simple proof-of-concept patch to illustrate what I mean.

@ifesdjeen - I would be intereseted to see a POC (you don't have to fully implement, but just to get a better idea)

same here :+1:

Specifying the type of the outbound message of a handler was considered at the early stage of Netty 4 API design phase, but I ended up removing it because a subclass of a handler might want to transform the encoded/decoded object. A good example is the extractFrame() methods in some decoders.

@trustin yeah I remember that we considered it and not did it at the end. That said we may be able to provide some "type-safe" builders.

@ifesdjeen are you interested in providing a POC ? If not should we just close it for now ?

I'll try to find some time over the next few weeks. I'll just reopen the ticket if something. Thanks!


Add support for client TLS to pkg/metrics

This separates out the TLS support (which is finished) in #998 from the Resource support (which is not).
I can try to write a fake OpenCensus gRPC endpoint to test the TLS handshake if you want; I didn't do this yet because I got ratholed on the Resource support.
/assign @anniefu
/assign @vagababov

Looks like I do need test coverage to be able to merge this.
Tests incoming in the next day or so.

I added two tests for OpenCensus, one without certs, and one with client and server certs (though it doesn't test actual metrics delivery to the other end, only setup and configuration).

Small nit on exporting the TLS strings as consts for the sake of other Knative repos. But otherwise,
/lgtm


Fixing https://github.com/Netflix/Hystrix/issues/1508

Making COMMAND_MAX_ACTIVE convertible between HystrixRollingNumberEvent --> HystrixEventType
Fixing #1508 which was caused by #1489

👍

Thanks @chrisgray , for the code fix and the typo catch!

when are you gonna release the version with the fix?

Just released in v1.5.11


pbindex not found

Operating system
RedHat linux 7
Package name
pb-assembly (pb_unzip.py)
Conda environment
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             4.5                       1_gnu
bedtools                  2.30.0               h7d7f7ad_1    bioconda
blas                      1.0                         mkl
blasr                     5.3.5                         0    bioconda
bwa                       0.7.17               h5bf99c6_8    bioconda
bzip2                     1.0.8                h7b6447c_0
ca-certificates           2021.5.25            h06a4308_1
certifi                   2021.5.30        py37h06a4308_0
curl                      7.71.1               hbc83047_1
decorator                 5.0.9              pyhd3eb1b0_0
falcon-kit                1.8.1                    pypi_0    pypi
falcon-phase              1.2.0                    pypi_0    pypi
falcon-unzip              1.3.7                    pypi_0    pypi
future                    0.18.2                   py37_1
htslib                    1.9                  ha228f0b_7    bioconda
intel-openmp              2021.2.0           h06a4308_610
k8                        0.2.5                h9a82719_1    bioconda
krb5                      1.18.2               h173b8e3_0
ld_impl_linux-64          2.35.1               h7274673_9
libcurl                   7.71.1               h20c2e04_1
libdeflate                1.0                  h14c3975_1    bioconda
libedit                   3.1.20210216         h27cfd23_1
libffi                    3.3                  he6710b0_2
libgcc                    7.2.0                h69d50b8_2
libgcc-ng                 9.3.0               h5101ec6_17
libgomp                   9.3.0               h5101ec6_17
libssh2                   1.9.0                h1ba5d50_1
libstdcxx-ng              9.3.0               hd4cf53a_17
minimap2                  2.20                 h5bf99c6_0    bioconda
mkl                       2021.2.0           h06a4308_296
mkl-service               2.3.0            py37h27cfd23_1
mkl_fft                   1.3.0            py37h42c9631_2
mkl_random                1.2.1            py37ha9443f7_2
mummer4                   4.0.0rc1        pl5262h1b792b2_1    bioconda
ncurses                   6.2                  he6710b0_1
networkx                  2.2                      py37_1
nim-falcon                3.0.1                h1341992_0    bioconda
numpy                     1.20.2           py37h2d18471_0
numpy-base                1.20.2           py37hfae3a4d_0
openssl                   1.1.1k               h27cfd23_0
pb-assembly               0.0.8                hdfd78af_1    bioconda
pb-dazzler                0.0.1                h779adbc_1    bioconda
pb-falcon                 2.2.4            py37hed50d52_0    bioconda
pb-falcon-phase           0.1.0                h3889886_0    bioconda
pb-falconc                0.1.2                hc9558a2_1    bioconda
pbgcpp                    2.0.2                h9ee0642_1    bioconda
pbmm2                     1.3.0                h56fc30b_0    bioconda
pcre                      8.44                 he6710b0_0
perl                      5.26.2               h14c3975_0
pip                       21.1.2           py37h06a4308_0
pysam                     0.15.3           py37hda2845c_1    bioconda
python                    3.7.10               h12debd9_4
python-edlib              1.3.8.post2      py37h22450f8_1    bioconda
python-intervaltree       3.1.0              pyh864c0ab_0    bioconda
python-msgpack            0.6.1            py37h22450f8_4    bioconda
python-sortedcontainers   2.3.0              pyh3252c3a_0    bioconda
python_abi                3.7                     1_cp37m    conda-forge
racon                     1.4.20               h9a82719_1    bioconda
readline                  8.1                  h27cfd23_0
samtools                  1.7                           1    bioconda
setuptools                52.0.0           py37h06a4308_0
six                       1.15.0           py37h06a4308_0
sqlite                    3.35.4               hdfb4753_0
tk                        8.6.10               hbc83047_0
wheel                     0.36.2             pyhd3eb1b0_0
xz                        5.2.5                h7b6447c_0
zlib                      1.2.11               h7b6447c_3

Describe the bug
Not sure if it's a bug or simply something's lacking in the installed env.
I just installed pb-assembly with conda in a new env  and downloaded the test data according to the instruction in pb-assembly READM.md.  When I tried fc_run and succeeded (after updated pb-falconc separately).  But when I tried fc_unzip.py, I got errors about pbindex not found (see below).
Error message
[INFO]Popen: 'bash -C /usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pwatcher/mains/job_start.sh >| /data/test_pb/FALCON-examples/run/greg200k-sv2/4-polish/quiver-run/000000F_001/run-Pa79ce46875bf1f.bash.stdout 2>| /data/test_pb/FALCON-examples/run/greg200k-sv2/4-polish/quiver-run/000000F_001/run-Pa79ce46875bf1f.bash.stderr'
[INFO](slept for another 1.4s -- another 4 loop iterations)
[INFO](slept for another 2.0s -- another 5 loop iterations)
[ERROR]Task Node(4-polish/quiver-run/000000F_001) failed with exit-code=1
[ERROR]Task Node(4-polish/quiver-run/000000F) failed with exit-code=1
[ERROR]Some tasks are recently_done but not satisfied: {Node(4-polish/quiver-run/000000F), Node(4-polish/quiver-run/000000F_001)}
[ERROR]ready: set()
        submitted: set()
[ERROR]Noop. We cannot kill blocked threads.
[ERROR]Error for run(target=clr, config_fn=fc_unzip.cfg, logging_config_fn=None)
Traceback (most recent call last):
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 195, in run
    run_logged(target, config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 184, in run_logged
    unzip_all(config, unzip_config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 27, in unzip_all
    tasks_unzip.run_workflow(wf, config, unzip_config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/tasks/unzip.py", line 739, in run_workflow
    job_dict=config['job.step.unzip.quiver'],
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_kit/pype.py", line 195, in gen_parallel_tasks
    wf.refreshTargets()
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 278, in refreshTargets
    self._refreshTargets(updateFreq, exitOnFailure)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 362, in _refreshTargets
    raise Exception(msg)
Exception: Some tasks are recently_done but not satisfied: {Node(4-polish/quiver-run/000000F), Node(4-polish/quiver-run/000000F_001)}
Traceback (most recent call last):
  File "/usr/local/miniconda_py37/envs/pb-assembly/bin/fc_unzip.py", line 11, in <module>
    load_entry_point('falcon-unzip==1.3.7', 'console_scripts', 'fc_unzip.py')()
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/mains/start_unzip.py", line 33, in main
    unzip.run(**vars(args))
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 195, in run
    run_logged(target, config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 184, in run_logged
    unzip_all(config, unzip_config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/unzip.py", line 27, in unzip_all
    tasks_unzip.run_workflow(wf, config, unzip_config_fn)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_unzip/tasks/unzip.py", line 739, in run_workflow
    job_dict=config['job.step.unzip.quiver'],
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_kit/pype.py", line 195, in gen_parallel_tasks
    wf.refreshTargets()
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 278, in refreshTargets
    self._refreshTargets(updateFreq, exitOnFailure)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 362, in _refreshTargets
    raise Exception(msg)
Exception: Some tasks are recently_done but not satisfied: {Node(4-polish/quiver-run/000000F), Node(4-polish/quiver-run/000000F_001)}

The following are lines from the file /data/test_pb/FALCON-examples/run/greg200k-sv2/4-polish/quiver-run/000000F_001/run-Pa79ce46875bf1f.bash.stderr.
+ pbmm2 align --sort ../../../quiver-split/refs/000000F_001/ref.fasta /data/test_pb/FALCON-examples/run/greg200k-sv2/4-polish/segregate-run/segr001/segregated/000000F_001/000000F_001.bam aln-000000F_001.bam
+ pbindex aln-000000F_001.bam
user_script.sh: line 22: pbindex: command not found
touch quiver_done.exit
+ touch quiver_done.exit
WARNING:root:Call '/bin/bash user_script.sh' returned 32512.
INFO:root:CD: 'uow-00' -> '/data/test_pb/FALCON-examples/run/greg200k-sv2/4-polish/quiver-run/000000F_001'
ERROR:root:failed multiprocessing
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_kit/util/io.py", line 68, in run_func
    ret = func(*args)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/falcon_kit/mains/generic_run_units_of_work.py", line 45, in run_uow
    pypeflow.do_task.run_bash(script, inputs, outputs, params)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/do_task.py", line 200, in run_bash
    util.system(cmd)
  File "/usr/local/miniconda_py37/envs/pb-assembly/lib/python3.7/site-packages/pypeflow/io.py", line 27, in syscall
    raise Exception(msg)
Exception: Call '/bin/bash user_script.sh' returned 32512.

To Reproduce
followed steps descript in https://github.com/gconcepcion/pb-assembly
$ conda create -n pb-assembly
$ conda activate pb-assembly
$ conda install pb-assembly
$ conda update --all
$ conda install -c bioconda pb-falconc
$ mkdir test_pb
$ cd test_pb
$ git clone https://github.com/cdunn2001/git-sym.git
$ git clone https://github.com/pb-cdunn/FALCON-examples.git
$ cd FALCON-examples/
$ ../git-sym/git-sym update run/greg200k-sv2
$ cd run/greg200k-sv2/
$ fc_run fc_run.cfg
$ fc_unzip.py fc_unzip.cfg # got errors with exit code 1

Expected behavior
Expected fc_unzip.py to finish with exit code 0

I resolved the issue.  pbbam was not installed.  After I installed pbbam (conda install -c bioconda pbbam),  pbindex is available.  Wondering why pbbam is not included in pb-assembly installation (at least in my case).


pyjxslt cannot handle XSL stylesheets with imports

Perhaps alternate XSLT transformation approaches will obviate this.

This would apply to pyjxslt or a C++ call to Saxon wrapped:
Before transformation scenario is run, read through XSLT, download stylesheets and cache locally, rewriting the imports to be local imports.

Another alternative: allow users to upload supporting XSLT stylesheets that would be deposited in /home/combine/data/combine/transformations/.
Then, rewrite includes as local to match this location, e.g.:
 <xsl:include href="/home/combine/data/combine/transformations/dcmiType.xsl"/>
    <xsl:include href="/home/combine/data/combine/transformations/mimeType.xsl"/>
    <xsl:include href="/home/combine/data/combine/transformations/csdgm.xsl"/>
    <xsl:include href="/home/combine/data/combine/transformations/forms.xsl"/>
    <xsl:include href="/home/combine/data/combine/transformations/iso3166-1.xsl"/>
    <xsl:include href="/home/combine/data/combine/transformations/iso639-2.xsl"/>

Will also need to update documentation about transformations about this...

Local includes can be handled by creating a new Transformation Scenario, then rewriting main transform to use those local filesystem filepaths.
For HTTP imports, consder downloading and rewriting?  would be prohibitively slow otherwise, unless pyjxslt handles this (which it might, but it still can't see "outside")

Closing.


Learn csv-w schema structure

Learn more on context
why some schema is not having this
why in Ruby implementation 2 types of schema classes are returned as schema (CSV::Schema and Csvw::TableGroup)

more information here https://www.w3.org/TR/2015/REC-tabular-metadata-20151217/
Time box- half day?

TODO: @robons to signpost to some examples of the CSV-W schemas we're using.

TODO: @robons to signpost to some examples of the CSV-W schemas we're using.


[T2A2][W14-A1]Haya Alsharef

Ready for review

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


[2.12.2] Bug: Error when trying to delegate to pool

Getting this error when trying to delegate to a pool

An error occurred while using Stacks Wallet for Web (2.12.2).
Error

Not a c32-encoded string

Stack trace
Error: Not a c32-encoded string
    at Object.c32decode (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:85504:15)
    at Object.c32checkDecode (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:85390:30)
    at c32addressDecode (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:85205:23)
    at createAddress (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:25841:93)
    at createContractCallPayload (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:25196:90)
    at makeUnsignedContractCall (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:23578:98)
    at makeContractCall (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:23634:35)
    at generateContractCallTx (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:48213:90)
    at _callee2$ (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:48387:151)
    at tryCatch (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:141521:40)

This error means you're passing an incorrect stacks address somewhere -- can I ask where you're calling this transaction (what app?)


alwaysSet with empty Array only works as first specified mapping

Hi,
I am trying to copy an array between two objects. To works fine for Arrays with at least one object, if I understood the docs, to copy empty arrays I have to use the alwaysSet field.
This properly sets the field on the destination object, but only if the mapping was the first specified.
Code to Reproduce
const mapFactory = require("map-factory");

const mapFirst = mapFactory({ alwaysSet: true });
const mapLast = mapFactory({ alwaysSet: true });

const source = {
  foo: 0,
  bar: []
};

mapFirst
  .map("bar").to("bar[]")
  .map("foo");

mapLast
  .map("foo")
  .map("bar").to("bar[]");

console.log("Mapping First:", mapFirst.execute(source));
console.log("Mapping Last:", mapLast.execute(source));

Expected Output
Mapping First: { bar: [], foo: 0 }
Mapping Last: { foo: 0, bar: [] }

Actual Output
Mapping First: { bar: [], foo: 0 }
Mapping Last: { foo: 0 } // Missing bar

Oh god. It's in the object-mapper code. 😭


Adds Model stub as an equivalent for Folder

I'm currently testing some stuff related to characters and I need a Model class to feign as the character.

Coverage increased (+0.006%) to 97.742% when pulling 097a72d4072a3818105f3436d797d509a7cb2bcc on Kampfkarren:model into 7145587fa5c1382e4e67db137c3931e6823fa2b6 on LPGhatguy:master.

Cool, thanks!


Getting a 502 error with Kubernetes Dashboard.. Any Ideas?

Hello all,
Following this workshop verbatim, however I am getting a 502 error when previewing the application with the Cloud9 IDE. No idea why this is happening even after destroying the cluster. Does anyone have any ideas?

Hello,
I was unable to reproduce this behavior. Don't hesitate to reopen the issue if you still have the problem.


Add Popovers

Project URL
https://github.com/aheze/Popovers
Category
UI
Description
A library to present popovers. Simple, modern, and highly customizable. Not boring!
Why it should be included to awesome-ios (mandatory)
Simple, modern, and highly customizable.
Checklist

[x] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[x] Has more than one contributor
[ ] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@bennettyuan
Thanks for contributing!


Enable/Disable pinpoint agent in java using env varibale

Is there any env variable to enable/disable pinpoint agent in java?
For example in node, you can disable the agent by setting "PINPOINT_ENABLE=False".

I set up pinpoint agent like this:
JAVA_OPTS= ”-javaagent:/usr/local/pinpoint-agent/pinpoint-bootstrap.jar -Dpinpoint.agentId=MyIP -Dpinpoint.applicationName=MyAPPName"
i think you can disable this line to disable pinpoint agent.hopes help.
BTW,do you mean in docker?

Resolved in https://github.com/pinpoint-apm/pinpoint/pull/7880

Thank you @emeroad , @yjqg6666 .
This is exactly what i was looking for.
@itnikita in k8s cluster.


fix: classes got renamed

.terms_terms -> ._terms
.tabs_nav -> ._header

nm, with 1.4.2 ( https://github.com/zeit/hyper/pull/2139 ) this change is mute


suppress git errors

Sometimes .git directory exists, but git is not installed

In order to pass RuboCop's ClassLength rule, you may need to find a way to extract classes out of Configuration.
It seems that there's a theme of inspecting the filesystem and environment for information in these methods:

detect_release_from_heroku
detect_release_from_capistrano
detect_release_from_git

@nateberkopec Oh, hi!
Could you review this change?

@alexandrz Maybe you can improve the Descriptoin and the title of this PR, now that it does a little more (to the code).

@olleolleolle Updated it. Thank you for reviewing the changes.


MMM-Globe stop working after some hours

Hello,
i have a RPI4 4Gb, and after some hours the module stop working, i have a icon "broken" instead of the globe, cant find anything in the log.
I try to force openGL in raspi-conig with no luck.
Any idea to help please?

I have the same problem but module is gone after few minutes


docs: Delete fun-rec & Rearrange Index

本次更新的内容主要为...
删除 fun-rec 和重新排列索引
欢迎前来学习

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Reinstall option

@oznu
Sometimes we need to install some plugin again, it will be nice to add next to the “uninstall” option “reinstall” option. Right now we need first uninstall then search and install again.
Thanks

This is effectively covered by the "install previous version" feature in the upcoming v4.29.0 - as you can just select the current version and it will re-install.

Yes, thanks for this nice improvement.👍


CUE modules that have a gen directory can't be used

What version of CUE are you using (cue version)?

cue version v0.9.0-rc.1

go version go1.22.1
      -buildmode exe
       -compiler gc
  DefaultGODEBUG httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.9.0

Does this issue reproduce with the latest stable release?
yes
What did you do?
In a new directory, create a module and add a dependency:
cue mod init github.com/vikstrous/cuek8stest
cue mod get github.com/vikstrous/cuek8s

Create a file: test.cue
package cuek8stest

import "github.com/vikstrous/cuek8s"

hello: cuek8s.#Hello

service: cuek8s.#Service

Then run cue eval
What did you expect to see?
it shouldn't error
What did you see instead?
<EMAIL_ADDRESS>import failed: import failed: cannot find package "k8s.io/api/core/v1": cannot find module providing package k8s.io/api/core/v1:
    ./test.cue:3:8
    ../.cache/cue/mod/extract/github.com/vikstrous/cuek8s@v0.0.9/hello.cue:3:8

I'm seeing something similar as well

Same here.

I'm planning to start trying to work around this by rewriting package paths and moving the gen packages out of the gen directory. To reproduce this issue, use version v0.0.8 of https://github.com/vikstrous/cuek8s

This is the workaround: https://github.com/vikstrous/cuek8s/blob/master/generate.sh

I am also encountering this issue with a module published using 0.9.2 and source:  kind: "self".

Note that this behaviour is documented in the introduction to the Go modules reference:

as a transitionary measure, the CUE tool still supports the import of packages present in the cue.mod/pkg, cue.mod/usr and cue.mod/gen directories. This only applies to the main module, and if there is any ambiguity with respect to regular module dependencies an “ambiguous import” error will be reported.

Note the "as a transitionary measure" caveat above. Eventually, it's possible/probable that support for the gen, usr and pkg directories will be dropped in favour of regular published packages.

Closing this issue as everything seems to be functioning as intended.


Retrieving attachments

Hi,
Is there a way to retrieve email attachments with this package?

You can use its output (e.g., as from a RETR retrieval in this test from another project) along with other tools such as https://github.com/jhermsmeier/node-envelope (noting though that the latter currently has an issue reported stating that it is having problems with more than one attachment).
Closing as I think that may answer, but feel free to comment further as needed.

Thank you for your prompt reply!
I searched a little and since i'm using Node, there's the mailparser module available  https://nodemailer.com/extras/mailparser/

Envelope is also for Node, but it looks like mailparser has some heavy usage. Not sure how I missed that. Thanks for the info! By the way, for some reason, your link shows https://nodemailer.com/extras/mailparser/ but points back to this library.

Sorry, i misused the link feature of comments!
I thought it was the way to put a link to urls... Evidently not 😅
Anyway, fixed that, and I also reached my primary goal!
Thanks for everything :)


hostapp-update-hooks: Handle modules in old hostOS for pieeprom

If kernel is updated, modules cannot be loaded from
the hook that's running in a container with the new hostOS,
to which we are updating.
Therefore, we switch module handling to old hostOS so modules version match current running kernel.
Also, we need to ensure possible failures in updating EEPROM do not trigger any failure in HUP.
Addresses https://github.com/balena-os/balena-raspberrypi/issues/384

@ZubairLK I was revisiting this and was wondering what's the current status with the hooks.. Will the OS continue to support before/after hooks being run from the old hostOS? Or should we not rely on them and look for possible alternatives?

@alexgg yes, this is no longer necessary. Closing.


Updates to latest dependencies.

Codecov Report

Merging #84 into develop will decrease coverage by 5.41%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop      #84      +/-   ##
===========================================
- Coverage    86.54%   81.12%   -5.42%
===========================================
  Files           18       18
  Lines          639      641       +2
  Branches         0       79      +79
===========================================
- Hits           553      520      -33
- Misses          86       92       +6
- Partials         0       29      +29

Impacted Files
Coverage Δ

src/ui/controls/TextFieldControl.tsx
73.91% <0%> (-17%)
:arrow_down:

src/ui/controls/SliderControl.tsx
80% <0%> (-10%)
:arrow_down:

src/ui/controls/DropdownControl.tsx
81.81% <0%> (-9.1%)
:arrow_down:

src/core/variables/BooleanVariable.ts
92.3% <0%> (-7.7%)
:arrow_down:

src/ui/controls/SwitchControl.tsx
73.07% <0%> (-7.7%)
:arrow_down:

src/ui/controls/ColorSwatchControl.tsx
77.77% <0%> (-7.41%)
:arrow_down:

src/ui/controls/RadioListControl.tsx
71.42% <0%> (-7.15%)
:arrow_down:

src/lib/Remote.ts
53.01% <0%> (-6.03%)
:arrow_down:

src/core/variables/StringVariable.ts
94.11% <0%> (-5.89%)
:arrow_down:

src/core/variables/NumberVariable.ts
94.11% <0%> (-5.89%)
:arrow_down:

... and 6 more

Continue to review full report at Codecov.

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


Small to cloud custodian pipelines

Small fixes to allow these cleanup processes to run. Still won't actually delete any resources.

Description
N/A
Motivation and Context
Issues found in testing after --dry-run was turned off.
How Has This Been Tested?
Running the pipeline.
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Enhancement (improves on existing behavior)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My code follows the code style of this project. (Did you install and run the pre-commit hooks?)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

:+1:


fix: lazy load typescript and style options

Eagerly loading those configs would eagerly load their plugins, which could cause compatibility issues like #124 and is also a waste of compute in general
Fixes #124

Should add a regression test for this as well (when #85 is merged, to avoid merge conflicts)


OpenGraph-Tag doesn't show

Quick summary
I tried the new feature #786 but the tag doesn't show up in my source code: https://kaffeeringe.de/
Is it possible, that Yoast SEO is a problem?
Steps to reproduce
I updated to 2.50, emptied all caches.
What you expected to happen
A meta tag with "fediverse:creator" in the source code of an article
What actually happened
It doesn't show up
Impact
One
Available workarounds?
No and the platform is unusable
Logs or notes
No response

For now it "only" extends the OpenGraph Plugin to add it: https://de.wordpress.org/plugins/opengraph/

Ah! I saw the reference in the code, but I thought it avoided the conflict. Sorry, my PHP skills are not too good. :-D

I installed opengraph. Emptied all caches. It doesn't appear. :-(

Ah, you deactivated the author profiles... have not thought about this case!
...so maybe I have to release an update then ;)

It will be in the next release!


Not working in VirtualBox

When I try to open localhost:3000 (on host machine) I see "ERR_CONNECTION_RESET" or "ERR_CONNECTION_ABORTED".
How to reproduce:

Install virtualbox (5.0.26)
Install ubuntu 16.04
Configure port-forwarding screenshot
Install node (6.3.1) and npm (3.10.3)
Install create-react-app and run create-react-app my-app
Start it.
Open http://localhost:3000 at host machine.

P.S: when I use "curl localhost:3000" on a guest machine all is okay. It's very strange.

Open http://localhost:300 at host machine.

I assume this is a typo, did you open localhost:3000 or localhost:300?

Is this something we can fix from our side?

@mxstbr Yes, it was a typo (I fixed it).
I don't know, but if I create a file like this:
var http = require("http");

http.createServer(function(request, response) {
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.write("Hello World");
  response.end();
}).listen(3000);

then start it and all is okay.

Awesome, that's already very helpful @JWo1F! WebpackDevServer uses http under the hood, digging into that documentation this what it says about the hostname:

If the hostname is omitted, the server will accept connections on any IPv6 address (::) when IPv6 is available, or any IPv4 address (<IP_ADDRESS>) otherwise.

Which (I think) means that it's safe to remove that! Would you mind submitting a PR for that?

@mxstbr okay, please wait for PR :)

Thanks!

This should be fixed in 0.2.0 alpha. Can I ask you to try it and confirm? Here's how: https://github.com/facebookincubator/create-react-app/pull/190


Quick question, does this library can work in purely Angular webapps?

I would like to know if this library can work in purely Angular web applications. I saw in the description that is says that works with lit-html templates and custom elements. I mean, right now, I'm trying to add some accessibility linter rules to our Angular webapps, I would like to know if with eslint-plugin-lit-a11y that can be possible. We're not using lit-html at all, just normal Angular apps.

The eslint-plugin-lit-a11y internally uses the TemplateAnalyzer API from eslint-plugin-lit that supports Lit templates (tagged literal expressions). If you're writing templates in Angular, you might need another plugin, see this blog post.

In our app we are not using literal expression at all. It is just Angular, so we're saying that eslint-plugin-lit-a11y does not work without literal Lit templates?

eslint-plugin-lit-a11y does not work without literal Lit templates?

Yes, it's not going to work for Angular templates. Closing this issue as this is out of the scope for the plugin.


KeyError,  when serving include_runtime=True in request_thermostats call

selection = Selection(selection_type=SelectionType.REGISTERED.value, selection_match='',  include_runtime=True)
thermostat_response = ecobee_service.request_thermostats(selection)
File "/Users/jwu/PycharmProjects/ecobee/ecobee.py", line 133, in thermostats_summary
thermostat_response = self.ecobee_service.request_thermostats(selection)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/service.py", line 367, in request_thermostats
return EcobeeService.__process_http_response(response, EcobeeThermostatResponse)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/service.py", line 130, in __process_http_response
is_top_level=True)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/utilities.py", line 89, in dictionary_to_object
dictionary_to_object(data[key], property_type, response_properties, parent_classes, indent + 4)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/utilities.py", line 138, in dictionary_to_object
indent + 8)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/utilities.py", line 89, in dictionary_to_object
dictionary_to_object(data[key], property_type, response_properties, parent_classes, indent + 4)
File "/Users/jwu/ecobee/lib/python3.5/site-packages/pyecobee/utilities.py", line 159, in dictionary_to_object
generated_code = '{0}={1!r}'.format(parent_classes[-1].attribute_name_map[key], data[key])
KeyError: 'showIconMode'

I too am getting the same error. Is this software still being actively supported?

@LesFromIL -- I started to use the fork https://github.com/mumblepins/Pyecobee -- appears to work around this issue.

Thanks to you kirussel! It does appear to fix the original issue. Might you have a simple example of using pyecobee? My current program forces me to re-enter a pin every time I run it; a real pain. Certainly there must be a way to re-run the Python program without having to enter a pin on the ecobee site every time.

I've updated the implementation and will try to keep updating it regularly going forward.


Library Declaration Proposal

I don't know if this is the best idea, but...
Maybe we should introduce syntax for library declarations that declare the interface for primitive components:
The reason to do this explicitly so that we have a well defined source where primitives are defined that is not just documentation + implementation, and maybe this would also be useful if different backends supported different sets of primitives.
The syntax would look something like this:
(library
  (declare-component (name params ...)
    ((port in-a 32) ...)   ; inputs
    ((port out-a 32) ...) ; output ports
   ; maybe more flags, like whether it increments the time stamp
  )

  ...
)

@kwf37 Let me know what you think

Yes I like this notion.  One question is what can the params modify? My first thought is that params should only be used to modify the interface (i.e. multiported memories, parameterized bitwidths) and not have anything to do with implementation details, but if we wanted we could have some primitives where parameters adjust loop unrolling factors or something to increase performance.

(library
  (declare-prim
    (name (param_1 default_value) (param_2 default_value) ...)
    ((port in-a param_1) ...)   ; inputs (Can be parameterized on params)
    ((port out-a 32) ...) ; output ports
    (arr (port read 32) param_2) ; Perhaps some way of generating multiple input/output ports?
    (sequential true) ; True only for regs for now
  )

  ...
)

Sorry, these thoughts are a bit scattered:
I'm hesitant to have too many restrictions on what parameters can do, mainly because this would be harder and unnecessarily complex to implement. The idea is more that this is a very general interface + some metadata, not a new language for specifying library components.
The places we're using parameters now is for constant modules and for the size and dimension of memories. Bit-widths are the next natural thing to parametrize. Memories are a bit strange because I've been specifying them like this: (comp/memory 4 8 6) which would be a 3d array of size 3 x 8 x 6. But in general this means primitives can take any number of params? Specifying this in syntax seems weird and hard. Maybe we don't allow infinite params? and just have a different primitive for each memory size, and hope people don't make 10 dimensioned arrays. Or maybe we don't specify the params at all in this library thing. This seems like the wrong thing to do, this information is probably helpful for the backend.
Do FPGAs with multiported memories have both multiported memories and non multiported memories? I got a sense from somewhere, but I'm likely wrong, that either all of your memories are multiported or none of them are. In which case it doesn't seem like primitives are the right place to parametrize this. It's more like we want to parameterize the backend on whether there are multiported memories or not.

Not sure about the multi ported memory thing. I'll think about this stuff after my prelims and get back to you with some more thoughts.

I got a sense from somewhere, but I'm likely wrong, that either all of your memories are multiported or none of them are.

On this small matter: in general, both Xilinx and Intel FPGAs seem to have generic memory tiles that can be configured as either single- or dual-port. This page in the Intel docs sheds a little bit of light on what these memory modes are, for example. The only thing is that I'm not sure why you would ever use the single-port configuration when the dual-port version is available—can't you just not use the other port? There must be some resource advantage to doing so.

To pick this up again, I think that the syntax that we should introduce is this (modulo some renaming):
(library
 (define/prim (add B)
   ((port left B) (port right B))
   ((port out B) (port carry 1)))

 (define/prim (memory1d word-size addr-width port-mode)
   ((port data-in word-size) (port addr addr-width))
   ((port out word-size #t)))

 (define/prim (register B)
   ((port in B) (port res 1))
   ((port out B #t))))

In English, library primitives can declare parameters which can then be used in the port definitions to specify bitwidth. A primitive can also specify parameters that are not used as bitwidths. These can be used by an implementation of the primitive but we will not specify how.
Calyx will use these these declarations to do a "typechecking" / wellformedness pass to make sure that components are wired up in valid ways. Valid means that port names actually exist and port widths between connections match.
I've also included this #t on some of the output ports. This indicates that this output port increments the timestamp on that wire. I think that it makes the most sense to do this on the port level rather than the component level because some components might only want to increment the timestamp on some of their outputs.
With regards to the dual port, I guess it makes sense to just include this as a parameter for now. However, I think that this may require more thinking and there is no reason to decide this at part of this proposal.
To layout the things that need to be done to implement this:

parser for this new language fragment
make a structureless, controlless component type (maybe just make those fields optional)
implement a wellformedness pass, maybe just as a part of constructing the structure graph
update the Dahlia backend to generate bitwidths

Sounds good! I'm just a little worried about #t and associating it with ports, but we can see how it goes.

whats your worry?

Will the primitives files still be built-in libraries that they can import to use when compiling? Since each primitive library will have some kind of associated backend, can we setup a file structure where each library file is in the same folder as its associated backend-specific RTL files?

A super cool way this could work would be that something like define/prim could be backed either by RTL files or by more Futil code. That is, these declarations would work just like a "header" that describes otherwise-black-box RTL to bring it into the system. Reducing the distinctions between Futil and non-Futil hardware would be aesthetically pleasing.
Separately, you could totally imagine using this infrastructure even when the functionality is not backend-specific. That is, you might want to write some blocks in plain RTL for ultimate low-level control and wrap that up in your Futil design for ease of use.


BUG: On back press from the home page, navigate to the landing page.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When we press back button on HomePage it navigates back to Landing page. I think this should not be the flow. It should exit the app directly. I have already fixed it if its a bug and not the required flow of the app then I will raise a PR.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me  this issue

please assign this to me


Always conflict on title changes in merger

@fschwenn reports that we should show always have conflicts for changes in titles. Indeed, titles might have been curated (e.g. nicely LaTeX-ifield) and changes in titles might also be the sign of scenarios that are not handled automatically yet (e.g. an erratum is merged with the main publication and overwrites lots of fields) so having a conflict gives us an opportunity to review them.
TECH NOTES:

Change the merger config not to ignore conflicts on titles.
Add a pre-filter to remove titles from the root to avoid silently updating in case the title has not been curated.

Ad. 1.
Remove titles from list_megre_ops in ArxivOnPublisherOperations
Ad. 2.
Add a new filter (similar to this one but remove titles from root and place it in the pre-filters.

On pre-filters merge duplicated title, (remove one of them) leaving non archive source.

On pre-filters merge duplicated title, (remove one of them) leaving non archive source.


Fix #3435 : IDisposable objects using statement

Summary
IDisposable objects being used with "using" statement and fix naming eventargs parameter (should be "e").
Fixes #3435
Details
Code samples with IDisposable objects should dispose these objects correctly. Otherwise if code is taken from a sample to production (can happen), this can cause memory leaks.

@Styxxy,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


[FEA] Test V2 Parquet encoded files with reader

We have an issue https://github.com/NVIDIA/spark-rapids/issues/9058 to enable parquet writes in V2 format. We would like to also test the reader, and test combinations of GPU/CPU encoding and decoding v2 (potentially also fastparquet if it supports it)
V2 parquet encoded files should just work with the reader, but we have NOT tested it, so we are not documenting support for that as of today.

Scope is to add additional tests for creating V2 parquet files and testing reads/writes.


README extra-deps vs packages

As far as I can see using extra-deps to add dependencies is the correct with stack now. I belive its been that way for a while now so no need to keep the old docs around. Hopefully this helps others to get going a little faster.
Please let me know if this makes sense or if there is anything I can improve

Nope looks like I'm still not quite following how to correctly add a dependency :(


Add support for Reactive / Coroutine SQL

When available in Spring Data.

Is there a specific Spring Data project in the works for this that I can't find in GitHub Spring Projects? Or will it be rolled into an existing Spring Data module?
Or maybe I'm asking too many questions and it's still in the planning phase! Either way - this is quite exciting.

I was able to unearth some more info on future support for this - for anyone curious as I there is lots of background in the Spring JIRA:
https://jira.spring.io/browse/SPR-16069

Not yet but that's coming. Waiting that you can play with Spring Fu + https://github.com/r2dbc/r2dbc-client and send your feedback if you want ;-)

See related https://github.com/spring-projects/spring-fu/issues/119.


Optimize pdf

I developer of native_pdf_renderer and make some pdf memory usage optimization

is upgrade of native_pdf_renderer and freeing up some resources?
Yes, page.close need for normal works on android


Make mortal optional

I'd like to try use linefeed for the web with the xterm.js terminal emulator. Would it be possible to make mortal an optional feature? Currently, mortal has dependencies which prevent linefeed from being compiled to WASM.

Making the mortal dependency optional would not be my preference. linefeed uses a number of utility types defined in mortal. Moving these types into linefeed would mean a not insignificant amount of code duplication between the two projects.
However, it might be possible to implement a web backend for mortal. This would allow linefeed to work on the web platform without any modification. If you're interested in submitting a PR to mortal to implement the web backend, I'll do my best to help with any issues you encounter in the process.

sounds interesting, I will investigate if it's possible 👍

Great! I'm going to close this issue and, if any issues arise, please feel free to file an issue on mortal.


Add Python 3.12 support

Proposed change

This PR adds Python 3.12 support as lingua fork and update to 3.12 removed the blocker.

migrate to lingva
update CI/CD config
update pre-commit config
update readthedocs config
update tests config

Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[x] Dependency update (version deprecation/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] I've run make pre-commit, it didn't generate any changes
[x] I've run make test, all tests passed locally

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10628

Relevant Lines:
10628

💛  - Coveralls


Logout device

Why am I logged out of the device when using /login

u have to first logout then login otherwise mongodb will be locked thats why

u have to first logout then login otherwise mongodb will be locked thats why

So I log in then log out and log in again then download the file?

What's difference between log_group id and channel_id

channel_id

Log group for dump file
Channel id for subscribe channel

In render, 'this action is not allowed' message comes while deploying.....what can be the reason

Render par repo
Action not allowed
Plzz contact me  t.me/TGJokerX

In render, 'this action is not allowed' message comes while deploying.....what can be the reason

Yes bro same problem
Contact me
https://t.me/TGJokerX

fork and give star

@krackxor in which bot you were facing issue of logout ?

@krackxor in which bot you were facing issue of logout ?

V3 branch | Summer Release V2

Km

@krackxor in which bot you were facing issue of logout ?

V3 branch | Summer Release V2

Ok so make sure you are not logged in at many device and also in your bot there should be limit of logins on server where you are deploying so check that also


[bug]:  Cannot debug on iOS

Is there an existing issue for this?

[X] I have searched the existing issues.

CLI Version
0.3.0-dev.21
Firebase Tools version
13.0.3
Flutter Doctor Output
[✓] Flutter (Channel stable, 3.19.3, on macOS 14.4.1 23E224 darwin-arm64, locale en-CA)
• Flutter version 3.19.3 on channel stable at /Users/fstonge/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ba39319843 (3 weeks ago), 2024-03-07 15:22:21 -0600
• Engine revision 2e4ba9c6fb
• Dart version 3.3.1
• DevTools version 2.31.1
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/fstonge/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15E204a
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2023.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
[✓] VS Code (version 1.87.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.84.0
[✓] Connected device (3 available)
• iPhone 15 Pro Max (mobile) • 3997705A-2B36-4C35-9251-551F8AFA0B7F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-4
(simulator)
• macOS (desktop)            • macos                                • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
• Chrome (web)               • chrome                               • web-javascript • Google Chrome 123.0.6312.87
[✓] Network resources
• All expected network resources are available.
• No issues found!
Description
Since upgrading to flutterfire 0.3.0-dev.21, I cannot debug iOS.
The debug console shows :
Launching lib/main.dart on iPhone 15 Pro Max in debug mode...
Warning: CocoaPods not installed. Skipping pod install.
  CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
  Without CocoaPods, plugins will not work on iOS or macOS.
  For more info, see https://flutter.dev/platform-plugins
To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

CocoaPods not installed or not in valid state.
Error launching application on iPhone 15 Pro Max.

I tried to manually run pod updatefrom the ios folder, and this is the output:
Update all pods
Updating local specs repositories
Analyzing dependencies
firebase_analytics: Using Firebase SDK version '10.22.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '10.22.0' defined in 'firebase_core'
Warning: firebase_app_id_file.json file does not exist. This may cause issues in upload-symbols. If this error is unexpected, try running flutterfire configure again.
firebase_crashlytics: Using Firebase SDK version '10.22.0' defined in 'firebase_core'
firebase_performance: Using Firebase SDK version '10.22.0' defined in 'firebase_core'
firebase_remote_config: Using Firebase SDK version '10.22.0' defined in 'firebase_core'
Downloading dependencies
Installing CSCrashReporter (0.0.3)
Installing CS_iOS_SDK (4.30.2)
Installing Firebase (10.22.0)
Installing FirebaseABTesting (10.23.0)
Installing FirebaseAnalytics (10.22.0)
Installing FirebaseCore (10.22.0)
Installing FirebaseCoreExtension (10.23.0)
Installing FirebaseCoreInternal (10.23.0)
Installing FirebaseCrashlytics (10.22.0)
Installing FirebaseInstallations (10.23.0)
Installing FirebasePerformance (10.22.0)
Installing FirebaseRemoteConfig (10.22.0)
Installing FirebaseSessions (10.23.0)
Installing FirebaseSharedSwift (10.23.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (2.3.0)
Installing GoogleAppMeasurement (10.22.0)
Installing GoogleDataTransport (9.4.1)
Installing GoogleMLKit (4.0.0)
Installing GoogleToolboxForMac (2.3.2)
Installing GoogleUtilities (7.13.0)
Installing GoogleUtilitiesComponents (1.1.0)
Installing MLImage (1.0.0-beta4)
Installing MLKitBarcodeScanning (3.0.0)
Installing MLKitCommon (9.0.0)
Installing MLKitVision (5.0.0)
Installing PromisesObjC (2.4.0)
Installing PromisesSwift (2.4.0)
Installing SwiftProtobuf (1.26.0)
Installing app_settings (5.1.1)
Installing contentsquare (0.1.0)
Installing firebase_analytics (10.8.9)
Installing firebase_core (2.27.0)
Installing firebase_crashlytics (3.4.18)
Installing firebase_performance (0.9.3-17)
Installing firebase_remote_config (4.3.17)
Installing flutter_keyboard_visibility (0.0.1)
Installing flutter_native_splash (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing geolocator_apple (1.2.0)
Installing haptic_feedback (0.4.2)
Installing local_auth_darwin (0.0.1)
Installing local_auth_ios (0.0.1)
Installing mobile_scanner (3.5.5)
Installing nanopb (2.30910.0)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing sqflite (0.0.3)
Installing url_launcher_ios (0.0.1)
Installing video_player_avfoundation (0.0.1)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 22 dependencies from the Podfile and 51 total pods installed.

[!] Automatically assigning platform `iOS` with version `12.4` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

This is the line that raised an issue for me :
Warning: firebase_app_id_file.json file does not exist. This may cause issues in upload-symbols. If this error is unexpected, try running flutterfire configure again.
Steps to reproduce
I guess creating a new app and running the new 0.3.0-dev.21 flutterfire configure on it?
Expected behavior
The app should be able to start in debug.
Screenshots
No response
Additional context and comments
No response

Ok so turns out my app has two targets, Runner and RunnerTests.
After specifying Runner as the target, I'm getting this :
Launching lib/main.dart on iPhone 15 Pro Max in debug mode...
Xcode build done.                                           16.5s
Failed to build iOS app
Error output from Xcode build:
↳
    --- xcodebuild: WARNING: Using the first of multiple matching destinations:
    { platform:iOS Simulator, id:3997705A-2B36-4C35-9251-551F8AFA0B7F, OS:17.4, name:iPhone 15 Pro Max }
    { platform:iOS Simulator, id:3997705A-2B36-4C35-9251-551F8AFA0B7F, OS:17.4, name:iPhone 15 Pro Max }
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/_5/s0fnddx52xd36pj62l8cnyhj8q41tn/T/flutter_tools.PldJBq/flutter_ios_build_temp_dirgfRLDY/temporary_xcresult_bundle

    ld: warning: ignoring duplicate libraries: '-lc++'
    ld: warning: ignoring duplicate libraries: '-lc++'
    ld: warning: no platform load command found in '/Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/MLKitBarcodeScanning/Frameworks/MLKitBarcodeScanning.framework/MLKitBarcodeScanning', assuming: iOS-simulator
    error: Unable to read file at path /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/firebase_app_id_file.json
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Removed stale file '/Users/fstonge/Library/Developer/Xcode/DerivedData/Runner-dkrcmojidrmafebkkceqgnjkuayp/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Script-3EDA79F396D5D1323FAD1C26.sh'

    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleToolboxForMac' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseSharedSwift' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'SwiftProtobuf-SwiftProtobuf' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'nanopb-nanopb_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'geolocator_apple-geolocator_apple_privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'flutter_native_splash-flutter_native_splash_privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'PromisesObjC-FBLPromises_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'video_player_avfoundation-video_player_avfoundation_privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'path_provider_foundation-path_provider_foundation_privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GTMSessionFetcher' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'SwiftProtobuf' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'nanopb' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'PromisesObjC' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'PromisesSwift-Promises_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleUtilities-GoogleUtilities_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'PromisesSwift' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleUtilities' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleDataTransport-GoogleDataTransport_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleUtilitiesComponents' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCoreInternal-FirebaseCoreInternal_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleDataTransport' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCoreInternal' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCore-FirebaseCore_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCore' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseInstallations-FirebaseInstallations_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCoreExtension-FirebaseCoreExtension_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseABTesting-FirebaseABTesting_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseInstallations' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCoreExtension' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseABTesting' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseSessions' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseRemoteConfig-FirebaseRemoteConfig_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseRemoteConfig' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCrashlytics-FirebaseCrashlytics_Privacy' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseCrashlytics' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebasePerformance' from project 'Pods')
    note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
    warning: Run script build phase '[firebase_crashlytics] Crashlytics Upload Symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
    note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
    warning: Run script build phase 'FlutterFire: "flutterfire upload-crashlytics-symbols"' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'MLKitBarcodeScanning' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'Firebase' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'MLImage' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'MLKitCommon' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleAppMeasurement' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'GoogleMLKit' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'MLKitVision' from project 'Pods')
    /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'FirebaseAnalytics' from project 'Pods')

Could not build the application for the simulator.
Error launching application on iPhone 15 Pro Max.

Exited (1).

This line is the error :
 error: Unable to read file at path /Users/fstonge/Development/Company/spark-mobileapp-shop/ios/firebase_app_id_file.json

What happened to it since 0.2.0?

Turns out I needed to remove the old crashlytics upload symbols in my project.pbxproj:
4DF388FD168AB3B9AA3F6569 /* [firebase_crashlytics] Crashlytics Upload Symbols */,


feat: allow loading extension vector index

Add support for loading vector index types that are not natively supported in lance. This is done by registering a VectorIndexExtension in Session. During index loading, if the index type is not well known, we will check if there is an extension for it. This only works for v0.2 index.
This PR omits extensions points for creating and appending to the index to keep the change small. I will add create and append in following PRs.
This PR also extracted TestVectorDataset in scanner::test to scanner::test_dataset, which is pub and guarded under #[cfg(test)]

Codecov Report
Attention: Patch coverage is 81.91882% with 49 lines in your changes are missing coverage. Please review.

Project coverage is 81.09%.  Consider uploading reports for the commit e0a3b7d to get more accurate results

Files
Patch %
Lines

rust/lance/src/session/index_extension.rs
73.88%
35 Missing and 6 partials :warning:

rust/lance/src/dataset/scanner.rs
95.87%
0 Missing and 4 partials :warning:

rust/lance/src/session.rs
76.47%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2221      +/-   ##
==========================================
- Coverage   81.12%   81.09%   -0.04%
==========================================
  Files         184      185       +1
  Lines       53237    53411     +174
  Branches    53237    53411     +174
==========================================
+ Hits        43191    43315     +124
- Misses       7562     7607      +45
- Partials     2484     2489       +5

Flag
Coverage Δ

unittests
81.09% <81.91%> (-0.04%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Target List: Mosaic view

Mockups

Specifications

On mouse hover every element will slithly increase its size (as in Agents section)
Every element in the list will display upt to 4 domains contained in the target. In the footer section of the element will appear the following text Root domains: [number], where [number] is the amount of root domains contained in the selected target
Clicking in the target name will open the Target Details page (described in #49 )
Clicking in the name of a root domain will open the Root Domain Details page (described in another ticket)
Clicking the Edit Target button will open the Edit Target popup (described in #48 )

Working as expected