support aarch64 for linux and macos

The rustfmt (neo)vim plugins installed via mason fetches releases from github. However there are only x86_64 assets in the release. This means on linux aarch64, rustfmt vim plugin is not installable, and on macOS it's installing the x86_64 version so it runs in rosetta, this is not ideal. Note that if you run neovim inside a docker container on apple silicon macs, you also get this problem (it's running aarch64 linux inside).
This PR adds support for aarch64 for linux and macos. The workflows pass, but no artifacts are generated in my fork.
Please let me know if there's anything else needed besides this PR.

bump?

Sorry I've been meaning to post here for a bit but haven't really had the time.
This is definitely something I would've been interested in prior to some semi-recent upstream changes, but now I'm leaning towards closing this.
In short, there were some upstream changes made in rustc around how certain modules were packaged (some of the rustc internals rustfmt depends upon). Those changes have in turn made it quite infeasible for us to be able to ship our own self-contained binaries, and practically requires users to have a full toolchain with requisite components.
I haven't had the cycles to see if it's even possible for us to statically link things in from the sysroot, and I'm not sure if we ever will, so the most likely outcome is that we'll stop bundling the binaries in our github releases altogether.
I'm going to test some things out after our next release (perhaps as early as today), and if it seems like this round of binaries are still generally working then I may merge this for expanded arch support within the status quo. If not, then I'll close since we'll just end up deleting the workflow files anyway
Longer term though, I think this model will need to change :point_down:

The rustfmt (neo)vim plugins installed via mason fetches releases from github.

Thanks for replying. I had first created a PR where the rustfmt binary was built from scratch during mason builds, but this idea was rejected there.
If you can not make it work in the status quo like you say, what is the way forward? If you stop producing binaries for all platforms, that means all vim installations will have no rustfmt support anymore :-(.

Thanks for replying. I had first created a PR where the rustfmt binary was built from scratch during mason builds, but this idea was rejected there.
If you can not make it work in the status quo like you say, what is the way forward? If you stop producing binaries for all platforms, that means all vim installations will have no rustfmt support anymore :-(.

Most editor plugins rely on the user to acquire rustfmt via standard models (rustup) and fork out to it. Are there reasons why the vim plugin couldn't do so?

I mean technically the official binaries generated as part of the official Rust release and what rustup grabs are accessible on the internet, though the infra team really discourages people from grabbing those directly

I don't know why it was done this way, I guess because the binaries were easily available here. I'm not even sure why it needs to download them at all, I'd wager that if someone wants the rustfmt plugin, he'd have rust installed (and so also rustfmt). For some other vim plugins, mason even builds the needed binaries on the fly (that's what I tried first time as I said).
Anyway, I'll wait a bit to see if you manage to make this work. Please let me know if not and I'll try to find another solution for the mason (build from source or copy from OS path).

Unfortunately the expected behavior with these binaries has started appearing (see #5805). I understand the value having these pre-built binaries can provide, but we're the only official tool that was/is doing so and I just don't think it's going to be feasible for us to continue doing so.
Sorry for the inconvenience, let us know if there's anything else we could do to help on the editor plugin side (even if it's just docs, pinned issue, etc. on our end)

thanks for letting me know, this means rustfmt will be broken for all archs going forward, so we'll have to find a solution anyway (as otherwise there won't be any fixes anymore).
What do you propose we can do? The mason team expects plugin installation to take seconds rather than minutes, so building from source locally is not really an option.

My recommendation remains to shift the responsibility of acquiring rustfmt to users. That's the standard model in all other IDE/editor scenarios that I'm aware of, and it feels reasonable to me as well.
Most users will have a toolchain already, and the default rustup profile includes rustfmt amongst other components. The only subset of the audience I could see this burdening would be those that obtained Rust via some default system installation or their system package manager. Even then, I believe the majority of distros have the dev tools available as well through those models, including rustfmt


Fix read/write for some bugs, add test coverage

cc @achille-roussel
I found some bugs while integrating this into the Dapr project. Small fixes, plus improved tests which would have caught these bugs.

Addressed comment, switched to DeepEqual


Update README.md

addresses #4

@mrbuddhu please review this pull request, i have used markdown to enhance the look of it.


memory.x only included by accident

memory.x is only included by an INCLUDE memory.x line in the cortex-m-rt link.x file. Because we don't copy the file to ./target, the file is effectively only included by accident and only if you happen to be in the root of the git repo when you do the build.
Also, the sections are out of order which breaks https://github.com/raspberrypi/picotool/issues/39

Might be related: I'm trying to build an example and I get this error
error: linking with `rust-lld` failed: exit code: 1
<lots of arguments>
\target\thumbv6m-none-eabi\debug\build\cortex-m-rt-eb0715ff362a68a0\o
ut\link.x:23: cannot find linker script memory.x
          >>> INCLUDE memory.x
          >>>         ^

Might be. I'm having trouble reproducing it or @jonathanpallant's issue with it only building from the root of the repo.
I just tried doing clean builds of blinky on linux and windows

in the root
in the rp2040-hal directory
in the rp2040-hal/examples directory
And builds of pico_blinky
in the boards directory
in the boards/pico/
in the boards/pico/examples directory
Successfully built and linked every time.

Can you provide any more information on OS, how you're building, rust version, etc?

Windows 10, cargo 1.56.0 (4ed5d137b 2021-10-04)
I copied .cargo/config to my project, and the pico_blinky.rs example to my main.rs, then ran cargo run from the root of the project.
dependencies mostly copied from pico/Cargo.toml:
[dependencies]
pico = { git = "https://github.com/rp-rs/rp-hal.git" }
cortex-m = "0.7.2"
rp2040-hal = "0.2"
cortex-m-rt = { version = "0.7"}
embedded-time = "0.12.0"
usb-device= "0.2.8"
usbd-serial = "0.1.1"
usbd-hid = "0.5.1"
panic-halt= "0.2.0"
embedded-hal ="0.2.5"
cortex-m-rtic = "0.6.0-alpha.5"
rp2040-boot2 = "0.2"
nb = "1.0"
i2c-pio = { git = "https://github.com/ithinuel/i2c-pio-rs", rev = "fb6167d02b7fbc46a83f344f5242823bcd16e271" }

oh, in that case you will need a copy of memory.x in your project folder.
if you just want to run an example from the HAL, use this command from inside your rp-hal folder:
cargo build --release --example blinky

If you want something you can copy the examples into, can I suggest looking at https://github.com/rp-rs/rp2040-project-template?
It's configured by default to use a debugger (a second Pico will do, if you have one), but you could strip out a bunch of the dependencies and use the .cargo/config from the hal with it if you want to program over the USB bootloader.

@9names thanks a lot, that works! Time to mess around with it :D


Remove png fork me on GitHub background

Fixed : #82

Thanks for the PR @vicheanath ! I need to get a branch build of the index page deployed so I can validate this.

Thanks for the PR @vicheanath ! I need to get a branch build of the index page deployed so I can validate this.

So. I need to check out a new branch to build.

You can manually test this by opening a browser and going to https://boeing.github.io/config-file-validator, opening developer tools, and applying your changes directly to the HTML. See below, using your image does not fix the issue. Please play around with the css instead so that the images don't overlap, but adjust in size to fit the screen.


Add more narrative to the events and rituals section

We could add more narrative to the events and rituals section, for context and more engagement with the lists of information

I will address this issue.


Add markdown preview plugin

This plugin doesn't target neovim specific features, so I think it's best to not add it in favor of the other markdown plugins.


Add a "deploy to netlify" starter repo for soupault

Also improves the description to reflect recent changes in the 2.0.0 release.

Build failure seems unrelated to my changes.
11:32:13 PM: error No repo found in the frontmatter for content/projects/poole.md, skipping. The file or frontmatter may be malformed.
11:32:13 PM: Local archive not found, fetching new data.
11:32:14 PM: error Error: Request failed with status code 401

Ok, the real problem seems to be an undefined Github token somewhere...
12:57:43 AM: error Error: Request failed with status code 401
12:57:43 AM:     at createError (/opt/build/repo/node_modules/axios/lib/core/createError.js:16:15)
12:57:43 AM:     at settle (/opt/build/repo/node_modules/axios/lib/core/settle.js:17:12)
12:57:43 AM:     at IncomingMessage.handleStreamEnd (/opt/build/repo/node_modules/axios/lib/adapters/http.js:244:11)
12:57:43 AM:     at IncomingMessage.emit (events.js:326:22)
12:57:43 AM:     at endReadableNT (_stream_readable.js:1223:12)
12:57:43 AM:     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
12:57:43 AM:   config: {
12:57:43 AM:     url: 'https://api.github.com/gists',
12:57:43 AM:     method: 'get',
12:57:43 AM:     headers: {
12:57:43 AM:       Accept: 'application/json, text/plain, */*',
12:57:43 AM:       Authorization: 'token undefined',
12:57:43 AM:       'User-Agent': 'axios/0.20.0'
12:57:43 AM:     },

Updated on jamstack.org via https://github.com/jamstack/jamstack.org/pull/420 !


refactor: replace ad-hoc sum lemmas with mathlib4 Finset_sum*

cc @sgouezel for replaced lemma prod_finset_eq_prod / sum_finset_eq_sum with mathlib4 sum_subset (but can be kept if desired)

Much better, thanks! I had not found sum_subset so I had reinvented a worse version of it.


Wish: Add deviceName and manufacturerName to .deviceDescriptor

I realize that you are already implementing hotplug events ( #80 ), nevertheless I use usb-detection package [ https://github.com/MadLittleMods/node-usb-detection ] because it returns the deviceName and manufacturerName.
I think it would be great if you add these info to your deviceDescriptor.

deviceName: 'Teensy USB Serial (COM3)',
manufacturer: 'PJRC.COM, LLC.',

Thank you!

You can do this easily with the library, but I'd accept a PR that added convenience functions. Fetching the string involves IO, so it'd have to be an async function with a callback.
dev.getStringDescriptor(dev.deviceDescriptor.iManufacturer, cb)
dev.getStringDescriptor(dev.deviceDescriptor.iProduct, cb)
dev.getStringDescriptor(dev.deviceDescriptor.iSerialNumber, cb)

You should check that the descriptor index is nonzero, because zero indicates that the descriptor is not present.

Hi,
is there any progress for this enhancements? I can need this too. An extra getStringDescriptor call is working fine in case of an attach event but when y detect an detach event there is no way to get deviceName any more, otherwise I have to cache names of each attached devices done before.
Best regards,
Nic

You'll have to cache them before the device is disconnected. There's no way for the library to communicate with a disconnected device either.

Yes I know, but I do not want to implement extra infrastructure thats why I am using sometimes libs from npm ;)

Hello, were you guys able to get the deviceName? I only see manufacturer, product and serial number.

device.open();
  device.getStringDescriptor(deviceDescriptor.iManufacturer, function (err, manufacturer) {
    device.getStringDescriptor(deviceDescriptor.iProduct, function (err, product) {
      device.getStringDescriptor(deviceDescriptor.iSerialNumber, function (err, serialNumber) {
        console.log(manufacturer, product, serialNumber);
        device.close();
      }));
    });
  });
});

only shows the first one

Sorry ignore the deviceName, I narrowed down the problem into only getting a response from the first one. I tried switching iManufacturer with iProduct and I am getting product string descriptor only. Not sure what I'm doing wrong here.


tests: Use openjdk images repository instead of java

It seems like "java" was removed, I get:
"Error response from daemon: manifest for java:latest not found: manifest unknown: manifest unknown"
Also, heading to https://hub.docker.com//java redirects you to https://hub.docker.com//openjdk so I suppose that's the official successor.

The existing test runs assert is_musl(psutil.Process(application_pid)) so we can be sure the new image is musl-based as well.

The old image (which I had on my box, luckily) gives:
openjdk version "1.8.0_111-internal"
OpenJDK Runtime Environment (build 1.8.0_111-internal-alpine-r0-b14)
OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)

The openjdk:alpine one is a much newer build and it does use libgcc + libsrdc++ so the test that ensures they don't get loaded doesn't pass. I do want to test it in case we continue to encounter the older build.
Luckily, pulling by the hash I had on my box seems to work... so I changed it by hash and it gives the old image we had at java:alpine :)

Flaky tests - I created https://github.com/Granulate/gprofiler/issues/448 which describes one problem there, but the core issue appears to be flakiness in the get_stack_offset program.


Download files directly from the server

Fixes #817.

It's too bad that the contents API doesn't have a way of getting a URL for a file. Here, we have to download the entire file to the browser's memory, and then tell the browser to put it on disk. If the contents api instead had a way of fetching a server path for the file, we could just point to that.
The current notebook server has the convention of the /files/ path, but I don't think that's encoded in the API, so I'm hesitant to use it. @minrk - thoughts?

cf https://github.com/jupyter/jupyter-js-services/blob/master/src/contents.ts#L197

Oh hey, nice!
On Fri, Sep 2, 2016, 14:31 Steven Silvester<EMAIL_ADDRESS>wrote:

cf
https://github.com/jupyter/jupyter-js-services/blob/master/src/contents.ts#L197
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/jupyterlab/pull/838#issuecomment-244453634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALwZnHH1CSFKYs05bottA6I0V2X3RGYks5qmGtpgaJpZM4Jz9vH
.

This should work much better.

Cool, I will test this now...

I have confirmed this this PR work. See my one comment about deleting the DOM node...


runtime neon detection

tested on Oracle Cloud's cheapest ARM VPS VM.Standard.A1.Flex, seems to work.
related documentation: https://developer.arm.com/documentation/100403/0200/register-descriptions/aarch64-system-registers/id-aa64pfr0-el1--aarch64-processor-feature-register-0--el1
AdvSIMD, [23:20]
    Advanced SIMD. The possible values are:
    0x1	Advanced SIMD, including Half-precision support, is implemented.

seems the ARM marketing department calls it "NEON" and the ARM engineering department calls it "AdvSIMD".
possible alternative for https://github.com/BLAKE3-team/BLAKE3/pull/382

If you go to the generic AArch64 manual instead of the Cortex-A75 one, a value of 0 means that AdvSIMD is present, a value of 1 means AdvSIMD+FP16 is present, and a value of 15 means no AdvSIMD. I was under the impression that AdvSIMD was a required feature of AArch64. Go figure.

@sneves  hmm... does that mean
    uint64_t id_aa64pfr0_el1;
    __asm__ ("mrs %0, ID_AA64PFR0_EL1" : "=r" (id_aa64pfr0_el1));
    const uint8_t AdvSIMD = (id_aa64pfr0_el1 >> 20) & (1<<0 | 1<<1 | 1<<2 | 1 << 3);
    if(AdvSIMD != 15) {
      features = ARM_NEON;
    } else {
      features = 0;
    }

is better?

As far as I know standard ARMv8 implementations are required to support NEON, so apart from some rare special purpose CPUs NEON is guaranteed to be available. I heavily doubt that such a special purpose CPU would be used to run off-the-mill binaries / these people would compile with NEON=off anyways. Therefore it looks a whole lot like checking for SSE2 on x86-64 to me.

Note that the code in this PR will need minor changes now that #389 has been merged.
Details here: https://github.com/BLAKE3-team/BLAKE3/pull/389#issuecomment-2041255514


High CPU when broker is down/connectivity issues

Description
When a broker goes down, we see significant high CPU consumption. I understand that library abstracts the logic to connect back when the broker goes online. Are there any specific settings or known issues with high CPU when a broker is not available?
How to reproduce
Checklist
Please provide the following information:

[ ] Confluent.Kafka nuget version: 11.4
[ ] Apache Kafka version: 2.11
[ ] Client configuration:
[ ] Operating system: Windows 2012
[ ] Provide logs (with "debug" : "..." as necessary in configuration)
[ ] Provide broker log excerpts
[ ] Critical issue

please upgrade to a later version (preferably 1.0-beta3, or 0.11.6 if migrating to the new API is difficult).

Is this a known issue in 11.4? Also, is there a setting to provide timeout when connecting to a broker

I can't recall for this specific scenario, but there were high CPU issues on windows in 0.11.4 that have been resolved.

there's no way specify broker timeouts - this is all abstracted from you. the client will manage connections to brokers it requires, deal with brokers going down, moving partitions etc. all automatically.

please upgrade to a later version (preferably 1.0-beta3, or 0.11.6 if migrating to the new API is difficult).

hi @mhowlett  would you please indicate what's been changed in the 0.11.6 to fix this issue? We are investigation a similar high CPU issue that might related to client timeout. Many thanks.

Hi,
We have the same problem in production with version 1.1.0
2020-02-27 11:41:25,697 [48] ERROR ProducerFactory: Producer local error [Local_AllBrokersDown] 1/1 brokers are down
Error: sasl_ssl://servername.gcp.confluent.cloud:9092/4: Receive failed: SSL transpo rt error: Connection reset by peer (after 914219652ms in state UP)
Thanks

@acesyde - which platform?
i'm not aware of anything that has changed that might resolve this since 1.1.0, but want to take the opportunity to note that as a general rule, keeping the client at the latest version is a good idea. see e.g. https://www.slideshare.net/ConfluentInc/please-upgrade-apache-kafka-now-gwen-shapira-confluent-kafka-summit-sf-2019

Hi @mhowlett,
We are on linux platform with ubuntu LTS.
Yes it's a good rule to keep latest version, but actually we don't push a new production version if it's only for upgrade dependency.
We can try to update the dependency and try to reproduce it with 1.1.0 and 1.3.0 tomorrow.
Have a nice day

So we have a very similar issue.  When the Kafka cluster is unstable, our Kafka .Net clients are all using a lot of CPU and basically they are loading our server farms to a point were we have problem even login in!!  We had production incidents because of this.
In investigating the problem I used the Consumer example in this Git repo, didn't change anything (just added SSL), and started 3 instances (on my dev computer) that are connecting to our Kafka cluster. The single topic has 3 partitions, and 3 replicas.  The consumers, being in the same group, each get a partition (not using manual assignment).
I then start chaoskube and trash the Kafka cluster (yes, it runs in Kubernetes).  Consumers are doing nothing since there's no traffic.  At some point (when the cluster gets a bit unstable), they all start using between 20-40% CPU each and my CPU is loaded at 100%.  This will go on for minutes!  Let's imagine a server with a few dozens of instances, this is a PRODUCTION NIGHTMARE.
We understand the client is trying to reconnect but this high CPU utilization is a huge problem for us.
Is there a solution to this?

Hi @mhowlett,
We are on linux platform with ubuntu LTS.
Yes it's a good rule to keep latest version, but actually we don't push a new production version if it's only for upgrade dependency.
We can try to update the dependency and try to reproduce it with 1.1.0 and 1.3.0 tomorrow.
Have a nice day

Hi @acesyde , updating the dependency fix the problem? We are using 1.1.0 version too.
Thanks,

Is this still an issue with the latest version?


Only Can Show Ads 1 Time in Android Test Ads

Hi, AppLovin Team
I found a problem that why i only can load the test ads 1 time on android emulator ? Because on iOS simulator it's working good.
I found this problem after 1 load banner on the first screen, after i move to the second screen, the intertitial not loaded. This also applies to the opposite. But, when i load banner on the first screen then i move to the second screen that also using banner, it's working, but when i go black to the first screen from the second screen, the banner on the first screen getting blank.
May you help me or check it why that's happend on android ? Or am i skipping something from android documentation ? Because that kind of problem i don't found in ios, it's working very good just like i expected in ios.
I also have another question,
2. If 1 have 3 screen, to load the banner on the all of that screen, can i do "AppLovinMAX.initialize" on all screen ? Or i only can do "AppLovinMAX.initialize" on the first screen ?
3. If 1 have 2 screen with the first screen using banner and second screen using intertitial, after i load banner on the first screen then i move to the second screen then i load intertitial, why on the second screen that no banner ads, i still got log "Banner ad loaded from ..." ? Am a doing something wrong or it's just like that.
Thank you so much

Are you implementing banners programmatically or as a native ui component? Also, would you be able to enable verbose logging by calling AppLovinMAX. setVerboseLogging(true) and sending over the logs?
You only need to call AppLovinMAX.initialize() once per session.
When moving to a new screen, I would call AppLovinMAX.hideBanner(...) to stop the ad auto-refresh logic and AppLovinMAX.showBanner(...) to show the banner again. I'd try this approach for your issue in #1 and see if that resolves it.

Hi, thank you thomas for your reply

I'm using native ui component.
So if i have 3 screen, i still should load it in every screen right ? Or only on the first screen ?
To hide a banner should set the ad unit id ? Can i hide all the banner without knowing the ad unit id ? Am a still should do this even i'm using native ui component ?

Are you implementing banners programmatically or as a native ui component? Also, would you be able to enable verbose logging by calling AppLovinMAX. setVerboseLogging(true) and sending over the logs?
You only need to call AppLovinMAX.initialize() once per session.
When moving to a new screen, I would call AppLovinMAX.hideBanner(...) to stop the ad auto-refresh logic and AppLovinMAX.showBanner(...) to show the banner again. I'd try this approach for your issue in item 1 and see if that resolves it.

This is the error that i found from android studio
2021-03-12 12:20:44.008 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:20:44.009 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:20:44.283 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:45.783 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:20:45.784 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:20:46.145 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:46.564 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:47.051 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:20:47.051 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:20:47.051 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:20:47.052 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:47.052 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:20:48.437 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:48.899 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:20:48.899 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:20:48.899 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:20:48.900 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:20:48.901 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:20:59.606 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:20:59.607 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:20:59.970 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:01.369 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:01.370 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:01.779 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:02.241 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:02.703 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:02.703 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:21:02.703 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:21:02.706 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:02.706 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:04.672 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:04.672 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:21:04.672 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:21:04.673 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:04.673 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:04.950 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:15.198 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:15.199 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:15.604 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:17.012 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:17.013 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:17.340 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:18.341 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:18.341 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:21:18.341 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:21:18.342 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:18.342 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:18.357 1638-1651/? E/memtrack: Couldn't load memtrack module
2021-03-12 12:21:18.742 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:20.367 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is hidden
2021-03-12 12:21:20.367 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has width (0) below threshold
2021-03-12 12:21:20.367 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View has height (0) below threshold
2021-03-12 12:21:20.368 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 0 - 0, 0)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:20.368 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] View is not in top activity's view hierarchy
2021-03-12 12:21:20.621 3281-3281/aw.subscribers E/AppLovinSdk: [ViewabilityTracker] Rect (Rect(0, 84256 - 1080, 84393)) outside of screen's bounds (Rect(0, 0 - 1080, 2160))
2021-03-12 12:21:21.079 7298-7329/? E/aqtc: Phenotype API error. Event # chag@fafdb9a0, EventCode: 12 [CONTEXT service_id=51 ]
aqsh: 29503
at aqti.b(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):25)
at aqtc.a(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):4)
at aqtc.fW(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):12)
at abcx.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):9)
at bqlt.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
at tmw.c(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):6)
at tmw.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):7)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at tsu.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at java.lang.Thread.run(Thread.java:764)
2021-03-12 12:21:21.080 7298-7329/? E/AsyncOperation: operation=GetCommittedConfigurationOperationCall, opStatusCode=29503 [CONTEXT service_id=51 ]
OperationException[Status{statusCode=unknown status code: 29503, resolution=null}]
at aqtc.a(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):6)
at aqtc.fW(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):12)
at abcx.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):9)
at bqlt.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
at tmw.c(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):6)
at tmw.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):7)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at tsu.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at java.lang.Thread.run(Thread.java:764)
2021-03-12 12:21:21.080 7298-7398/? E/NetRec: [462] anom.c: Could not retrieve server token for package com.google.android.apps.gcs
java.util.concurrent.ExecutionException: sfa: 29503:
at axyh.m(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):3)
at axyh.f(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):7)
at anom.c(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):1)
at anom.a(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):1)
at anol.getHeaders(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
at com.android.volley.toolbox.HttpClientStack.performRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):18)
at tgs.performRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):1)
at btt.executeRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):1)
at com.android.volley.toolbox.BasicNetwork.performRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):3)
at tgt.performRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):17)
at com.android.volley.NetworkDispatcher.processRequest(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):5)
at com.android.volley.NetworkDispatcher.a(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at com.android.volley.NetworkDispatcher.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
Caused by: sfa: 29503:
at sks.b(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
at aqsr.o(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at aqti.e(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at abcr.p(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):4)
at abcx.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):11)
at bqlt.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):2)
at tmw.c(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):6)
at tmw.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):7)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at tsu.run(:com.google.android.gms<EMAIL_ADDRESS>(040700-352619232):0)
at java.lang.Thread.run(Thread.java:764)

Ok, thank you for your advice
But, i have another question

What is different between Banners and MRECs ? On MRECs am i also should hide it when move to another screen ? Or it's just working just like intertitial
I'm using React Native 0.63.3 and React Navigation 4.4.4 do you have an advice or best practice to implement banner ad ? Because i already read the example code on git but it's can't implement just like that on the real case.

Because if we only add hide banner when user tap the button on the screen, it's can't trigger when we swipe the screen or tab back button on the device. What kind of function or lib that i can use to track is the user move out the screen or not ?
Thank you for your time, hope you willing to give me the samples or references

I also had this problem where ads appear only in one place at the same time on sdk smaato https://github.com/khalisafkari/react-native-smaato-ad which I created but now I fixed it by adding child support for SDK , I want to contribute to this SDK but I can't find contribution guidelines in this SDK

@jacow:

What is different between Banners and MRECs ? On MRECs am i also should hide it when move to another screen ? Or it's just working just like intertitial

MRECs are not meant to be fullscreen immersive content and meant to be placed with your app's content.

I'm using React Native 0.63.3 and React Navigation 4.4.4 do you have an advice or best practice to implement banner ad ? Because i already read the example code on git but it's can't implement just like that on the real case.

Not at the moment - like the issue above, we'll have to look at it when we have bandwidth
@khalisafkari - there are several ways to help contribute (which we'll greatly appreciate as well):

Fork and submit a PR, or
Let us know what your solution is either on here or at my email<EMAIL_ADDRESS>
Thanks both!

I think it's will be great if the applovin banner ad can work normally just like admob banner ad. We don't need to hide and show the banner manually or programmatically, just placed the ui component to all screen and working normaly just like another ui component even we move to another screen or close the app and another activity.
I will come back again if the banner component is improved.
Thank you for your time.

I also had this problem where ads appear only in one place at the same time on sdk smaato https://github.com/khalisafkari/react-native-smaato-ad which I created but now I fixed it by adding child support for SDK , I want to contribute to this SDK but I can't find contribution guidelines in this SDK

That's will be great news if you can helping to solved this problem 🤩🤩🤩 Maybe @thomasmso can help you about the contribution guidelines

@jacow  I have done a pull request for this problem multi ad

Hey @jacow & @khalisafkari - the issue has been fixed here: https://github.com/AppLovin/AppLovin-MAX-React-Native/commit/65dc1eaa3211dccec4216947628364b9d7b21ecc and released in v1.1.7. Let me know if there are any issues. Thanks!

@thomasmso I think the update you are releasing works well with react-navigation but not with react-native-navigation

Hmm, if you could help reproduce the issue either in a new project or ideally a fork of our example app that would help me expedite the triage.

@khalisafkari / @jacow - Can we close this issue? Let me know if issue persists in the latest module (not your forked implementation).


Blueprints

Awesome integration you are the MAN!
Would it be possible to add your automations as blueprints?
Again thank you for this

The automations in the readme are both simple and complex in that they do a simple thing, but multiple simple things in one automation.  This complicates a blueprint (which, TBH, I have never created before, so have to figure this out first.   I'm pretty sure it can be done.  I tried doing one, but it's a bit of a mish and I'm not sure that the effort is worth it.
What I can suggest is that you

Create a new empty automation
Switch to Edit in YAML
Copy and paste an example from the Automation Code sections in the README
Switch back to Edit in visual editor.
Rename sensors where relevant
Delete what you don't need

If anyone knows how to create Blueprints or wants to figure it out and contribute them, that would be wonderful.


relay and direct connection timeouts

Wormhole-william has a 5 second timeout specified in the code for both direct connection and relay connections. This seem too small. More over, the specification defaults to OS connection timeouts, as far I can tell. So, this timeout and the associated handling of a timed out condition seem extraneous.

PR #46 closes this issue.


[enhancement] Use React Docgen to implement autodoc feature

最近我在做一个 Solid JS 的组件库，我使用了 Storybook 作为我的组件库的调试工具，但是发现 Controls 面板并没有显示出来。后面看到这个仓库在上个版本删除了 docgen 相关的数据，我就去查看 storybook react 版本的那个插件库，自己实现了 docgen。
Recently, I have been working on a Solid JS component library, and I have been using Storybook as a debugging tool for my component library. However, I noticed that the Controls panel was not displaying. Later, I found out that the repository had removed docgen-related data in the previous version. I checked the Storybook React version of that plugin library and implemented docgen myself.
其核心原理是使用 react-docgen 或者 react-docgen-typescript 生成组件的相关信息并交给 storybook 进行处理。因为 Solidjs 函数式组件的设计方式和 React 非常像，所以其大部分的功能都能够迁移使用。
The core principle is to use either react-docgen or react-docgen-typescript to generate relevant information about the components and hand it over to Storybook for processing. Since the design approach of SolidJS functional components is very similar to React, most of its functionality can be migrated and used.
实现方式

mian.ts： I add a Vite plugin like react component do

import solidjsDocgen from '@joshwooding/vite-plugin-react-docgen-typescript' // from react-vite
const config: StorybookConfig = {
    // ....
    async viteFinal(config, { presets }) {
        // Add docgen plugin
        const { reactDocgen: reactDocgenOption, reactDocgenTypescriptOptions } = await presets.apply<any>('typescript', {})
        config.plugins?.push({
            enforce: 'pre',
            ...solidjsDocgen({
                ...reactDocgenTypescriptOptions,
                savePropValueAsString: true
            })
        })
        return config
    }
}

preview.ts:
copy whole docs folder from react plugin;
and I imported extractArgTypes function only. (dependencies need to be installed.)

import { extractArgTypes } from 'storybook-solidjs-docgen/src/docs/extractArgTypes' // in my monorepo workspace

const preview: Preview = {
    parameters: {
       // ...
        controls: {
            expanded: true
        },
        docs: {
            extractArgTypes() {
                const res = extractArgTypes(...arguments)
                console.log(res)
                return res
            }
        }
    }
}

My project is here: https://github.com/KonghaYao/cn-ui/blob/story/.storybook/main.ts 😀


"Săbiești", "Stănești" are listed in the drop-down menu

Description:
"Săbiești" and "Stănești" are listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Săbiești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Săbiești, DÂMBOVIȚA (RĂCARI)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Stănești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Stănești, DÂMBOVIȚA (RĂCARI)".


Windows Client - Detected TCP Connection Failure

Hello I have a Sensu server (Ubuntu 14.04) and a Sensu client (different Ubuntu 14.04) set up in a test environment. I am trying to connect Windows clients to RabbitMQ running on the Sensu server. I have tested the latest Windows build (26.3-1) on Windows 7 32-bit, 64-bit, and Windows server 2008.
I have:
client.json
rabbitmq.json
transport.json - RabbitMQ as the transport.
in the C:\opt\sensu\conf.d directory.
I can verify that I have communication from my Ubuntu Sensu client via RabbitMQ logs, Uchiwa and so on, so I know Rabbit is set up right.
There are no firewalls included in this set up, and SSL is not enabled at the moment either.
I would like to know if I am missing something here with the Windows client. Any help or feedback is appreciated.

@kwright5150 RabbitMQ "TCP Connection Failure" can identify one of many things, e.g. unable to reach or authentication. Sensu 0.27 is expected to drop any day now, it has better RabbitMQ/transport logging capabilities, hopefully it will shed light on this issue. You may be able to find help via the IRC channel on Freenode #sensu, just be sure to stick around for an answer (asynchronous).

0.27.0-1 is in the unstable repositories, it adds better logging around connection issues and will soon be promoted to stable. Check out http://repositories.sensuapp.org/msi-unstable/2012r2/sensu-0.27.0-1-x64.msi for the unstable MSI.


Cope when we get errors from S3

At the moment we don't catch errors if something goes wrong we we interact with our S3 bucket.

app/services/image_uploader.rb (creating the blob)
app/image.rb (destroying the blob)

We should consider if we want to support this and handle any exceptions gracefully for the user.

I see this as a situation where it'd be ok to serve a user a 500 error in the same vein as if we have a database access error.
The distinctions between this and some of our internal web services is:

It's easy to be an environment without access to our services (heroku, dev)
We know from logs it's quite frequent that our services can return an error or timeout

Both of these should not be the case with S3 as we have the local option for the first situation and we expect S3 to have availability.
So I'd think that this is only something to consider coding for if we discover the frequency of the problems is sufficient that they cause a problem.

@kevindew nice argument - I'm happy to close :-).


Remove levers of the finger actuation mechanism from the meshes of the distal fingers

As per the title.
Meshes were manually adapted using the following Meshlab tools:

"Select faces in a rectangular region"
"Close Holes"

Fixes #82

Should I maybe change them in https://github.com/icub-tech-iit/ergocub-software/tree/master/urdf/simmechanics/data/ergocub/meshes/simmechanics instead?

@Nicogene told me that this is the correct folder, hence I changed that in the last commit

Merged, thanks!


[FEATURE] How to building custom agent using local LLM?

I'd like to customize an agent using a local LLM without relying on OpenAI's Assistants API. Do you have any examples or development plans?

@Zhouuuuo what do you mean by "agent"? Which exactly features are required?

@Zhouuuuo please open a discussion and reply here


Add Language: Luau

Luau is a programming language used on the incredibly platform Roblox, which has recently become it's own independent project.
Luau repository
Syntax is practically the same as Lua.
https://luau-lang.org/syntax
Most popular extensions
.luau
Detected language
Plain text

Closing as a duplicate of https://github.com/github-linguist/linguist/issues/6000

my bad, thx


Add ibex_rv_trace module template to implement risc5_trace_specs

This is initial trace module interface (to be compatible with riscv-trace-spec doc at https://github.com/riscv/riscv-trace-spec/blob/master/riscv-trace-spec.pdf ).
The aim is to check IO's and agree about them.
A core module which includes this tracer is also added (ibex_core_rv_tr.sv).
Signed-off-by: Rehab Massoud<EMAIL_ADDRESS>

The trace_signals specified by the riscv-trace-spec should be implemented in ibex_core.
Files here should be added only later as the encoder and a top module containing it and the core with its new added trace-signals. So I'll close this pull-request and initiate another one with what is actually required in the first step.


test: Expand tests for built-in functions

Which issue does this PR close?
Closes #128
Rationale for this change
Improve test coverage for buit-in functions
What changes are included in this PR?

Expand tests for math functions
Expand tests for string functions
Expand tests for hash functions
Add tests for temporal functions

Are there any user-facing changes?
No

Thanks for running the GitHub Action, saw it was failing yesterday.

Rebased branch to latest master
Fix failing unit tests (change in data types)
Ran formatter & linter so that GitHub Action job should pass now

@simicd I don't have permissions to officially review but wanted to say changes look good. More test coverage is always a good thing

Thanks @jdye64! One question: When you want to update a branch after submitting a PR, do you rebase or just merge main into your branch? Asking because it seems like Actions require someone to trigger the workflow again, hope I didn't pick the wrong option by rebasing.

I always prefer using git rebase for Pull Request branches.
Rebasing also makes it easier  to use Squash and merge Github UI functionality.
The workflows should be triggered manually for first time contributors. Once your first PR is merged all following PRs will execute the checks automatically!

Thanks for the review @andygrove and for the explanation @martin-g!


Writing Documentation

I would like to write a guide on how to write documentation, why to write it and the different tools we can use like Markdown and RST. Please assign this issue to me.

@Man-Jain there are various really good tools for this. An issue was raised previously too for this but I have specified the reasons for why it is not required. See #138

Okay, I have understood your point. No problem I will find something else to write on. :)


Add EnsureNamespace call to create a namespace

What issue type does this pull request address? (keep at least one, remove the others)
/kind bugfix
What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
resolves #2399
Please provide a short message that should be published in the DevSpace release notes
Add --create-namespace arg to helm install command to create a namespace if not exists
What else do we need to know?

@FabianKramm May I ask why this was closed? It seems like a great addition and would simplify our setup a lot.


Avoid warning on Xcode 11

Description

This warning is raised on Xcode 11 when BlueCrypto is installed as dependency
Motivation and Context
This variable should be immutable.
How Has This Been Tested?

Built on Xcode 10.2
Built on Xcode 11
Pass CI

Checklist:

[x] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

I sent CLA. Please check it out.

I saw the CLA and I sent my application form to<EMAIL_ADDRESS>However, this email seems not to be reachable 🤔
How can I sign CLA?


fix concurrent map writes

concurrent map writes #1296

@ZekeLu This should be left to the friends who have used it deeply before to PR. I give up this change, and I will manually adjust the temporary code locally and compile it for use.

Sorry, I meant to drop the review message to #1111. I can not delete the message, my only choice is to hide it. Sorry for the noises.


DRAFT: bump ktor client version to 2.3.3

there are some vulnerabilities in current 1.6.4 version https://security.snyk.io/package/maven/io.ktor:ktor-client-core/1.6.4

wrong branch name


Ensure we are cross compiling when any cross env variables are set.

Potential partial fix for #1513.

Thanks,

Did you confirm that this works for your case?
What do you mean by 'partial'? What problem do you think remains?

Did you confirm that this works for your case?

At the moment I haven't been able to fully validate this properly due to the cargo issue, the rust toolchain is rather exotic and buildroot's rust support is different from most other language toolchains we use(mostly due to having to use prebuilt rust toolchains since rust can't easily be bootstrapped due to the rust requires rust to build issue) so I'm having difficulty testing stuff that requires modifications to stuff deep in the dependency tree(I'm quite familiar with python package cross compilation in buildroot since I help maintain a good number of python packages there but have not worked much with rust). In any case having this merged should make it easier for me to isolate the cargo issue since env variables are generally quite easy to control with buildroot.

What do you mean by 'partial'? What problem do you think remains?

Well it looks like the main other issue is the cargo issue, but this best I can tell fixes the most obvious cross compilation detection logic issue I saw in pyo3. This at least shouldn't cause regressions since these env variables seem to be exclusively used in cross compilation enabled codepaths, so if any of them are set we should be able to safely assume that cross compilation should be unconditionally enabled.

can you check if this patch in conjunction with the suggested LD_LIBRARY_PATH setting might provide enough of a working solution to unblock you?

Well the LD_LIBRARY_PATH workaround doesn't really look like it's viable to upstream for buildroot to me as we do in fact support compiling for x86_64 targets with newer instructions sets than the build host(buildroot uses a custom autobuilder CI system with older build hosts to ensure this sort of thing isn't broken). I'll play around with this a little though.

This could also use a CHANGELOG entry - e.g. "Fixed - Always use cross-compiling configuration if any of the environment variables are set".

Added.

👍 I'm satisfied that this patch is correct; and while there's other upstream issues at least we can get one step closer with this in place.

Great, by the way I made a few attempts to go through the cargo codebase to try and isolate how it detects cross compilation but so far I haven't been able to understand the internal logic all that well.
Would you happen to know if there's a good place to find someone familiar with those internals enough to give me some pointers to help me better understand how the auto-detection there currently works?
Best I can tell none of the longstanding github issues relating to this issue that were opened against the cargo or rust repos have been given any serious attention by anyone who has a good understanding of what's going on internally so far.

You could try the t-cargo stream on the Rust zulip server?

For reference I have an open pull request to fix the related cargo bug in #9322.


Remove version: Jackett.Jackett version 0.20.2486

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.2486/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Measuring recent performance gains

This issue is here to compile a list of measurements from the recent, rather massive, performance gains achieved with advice and code improvements from @madmann91
I'll post more of my findings here as I do more testing in the coming days.
Ideally, these measurements should have three variants. original, IPO enabled and IPO with the new BVH enabled.
This should give indication as to the performance gains attained from the new BVH implementation, and isolate that from the large performance gain attained with interprocedural optimization.
All comparisons here are performed with the same exact scene and same settings. We could also perform multiple runs and average them to negate any temporary performance fluctuations of the operating system.
This is an incomplete measurement I performed yesterday on my Core i5-6600K desktop system running macOS:
Original kd-tree, no IPO, input/hdr.json @2560x1600, 6000spp, 30 bounces: 8h 40min
New BVH, IPO enabled, input/hdr.json @2560x1600, 6000spp, 30 bounces: 2h 15min
As you can see, massive performance gains. This measurement lacks the test with the old k-d trees + IPO enabled to truly compare k-d tree vs BVH, I'm performing that measurement at the moment.
One more note, C-ray encodes some render information into the tEXt chunks of PNG files. These can be observed with imagemagick as follows:
identify -verbose /path/to/rendered_0000.png
You should get output resembling the following:
...
Properties:
    C-ray Bounces: 30
    C-ray RenderTime: 2h 15m
    C-ray Samples: 6000
    C-ray Source: https://github.com/vkoskiv/c-ray
    C-ray SysInfo: x86_64 Proteus 16.7.0 Darwin Darwin Kernel Version 16.7.0: Tue Jan 30 11:27:06 PST 2018; root:xnu-3789.73.11~1/RELEASE_X86_64
    C-ray Threads: 6
    C-ray Version: C-ray v0.6.3 [8468d9e4], © 2015-2020 Valtteri Koskivuori
    date:create: 2020-06-07T22:21:18+00:00
    date:modify: 2020-06-07T21:07:31+00:00
    LodePNG: 20191109
...

Sorry for offtopic here. Didn't would like to create new issue. Please, can you add me to your telegram cuz somebody pushed me As Spam on telegram. Are you remember me?

If you add me i can continue to discussion


Unpacking error

When i try to unpack any file i either get an unsupported file error or on EndOfStremException.
It still creates the folders but they just dont contain anything

What version of the app are you using?
And what game are you trying to unpack with it?

Im using the latest release and trying to unpack ds3 files also latest version

I figurred it out, i assumed there only was one release since i didn't any other. Using the version meant for ds3 fixed the problem sorry for the annoyance


Fixes sprint 2017 Week 24-25

Fixes + tests
@romartin Can you approve & merge please?

jenkins retest this

Hey @dgutierr
Running this on wildlfly results in several warnings on startup (about errai), that should not be there... in addition, from the UI, once clicking on Gallery, the whole main menu disappears too.... I think something is not right yet.

@Roger both issues are fixed now.
The Errai warnings were caused by a client side dep not excluded from WAR.
Please have a look. Thanks!

Merged:
04c315032f302554a6bfd064d7399bf8521942dc
c48aa563c11911e40d76f59ecdaab50291fd6f90
258510f2a1843b9f549ef32cbed45caafe91448c


bump midterm for better TUI support

This bumps midterm to fix a ton of rendering issues with TUI apps, primarily with how scrolling regions are handled.
Vim now mostly works, but only with TERM=tmux-256color. With TERM=xterm-256color for whatever reason it prints \r\n when it should be printing \n which totally butchers the UI. Easy to trigger with just deleting a line (dd). Something similar happens when selecting lines upward (e.g. GV{{{). Currently compiling neovim to figure out why it does this only when running in midterm but that'll take too long to sneak in to v0.9.10.
Before:

After:

Looks like a test failed, probably legitimate (probably need to update a midterm usage somewhere), we don't really need this for v0.9.10 so just taking it out.

Test fixed but no fix for the \n -> \r\n conversion.
I noticed if I stty -opost and stty -onlcr in the container (whether in the shim or in the shell), the change has no effect. If I docker exec into the engine and run that against /dev/pts/0 (the container's PTY), it takes effect.
Seems like this change has to happen on the host side. Next thing to try would be changing this buildkit/containerd code path path to put the PTY in raw mode, but that might not be a sane default in all scenarios.

I'm confident that the \r -> \r\n issue has nothing to do with Midterm at this point, but unfrotunately it's a rat's nest of issues.
Linux defaults to onlcr, and Buildkit is allocating a PTY without clearing it, which isn't necessarily wrong because if you're trying to run e.g. bash you'll need that in order for text to not just walk across the screen.
The root of the issue seems to be that processes are not able to clear it from inside the container. I wonder if we can fix this by clearing onlcr on the host side and then adding it back on the shim side? Not sure, the change might not propagate for the same reason that -onlcr doesn't propagate. But other changes do seem to take effect, so maybe that would work...?
What's funny is you'll see a ton of confused discussion and issues around this strewn across projects in the container ecosystem (e.g. https://github.com/opencontainers/runc/pull/1146 - later reverted by https://github.com/containerd/console/pull/19). Now I suppose it is our turn.
In any case I think this PR is good to go; the above will require an upstream patch, and all of this is orthogonal to these midterm fixes.

Found a fix for the onlcr issues that doesn't require any upstream changes :tada: https://github.com/dagger/dagger/pull/6650/commits/6a4cb245695da6e5e5aeddd7f4eba620b93a5c46

Piled on another terminal DX improvement: https://github.com/dagger/dagger/pull/6650/commits/cebfbb01080cceb422540e2ed2eb5a37a762fb3f - and a fix for scrolling in htop.


Better visualization and UX for CIDR delegation

In it's current state, I don't find CIDR selection and delegation to be a particularly stress-free experience. I think it could benefit from some more clever uses of auto-suggestion of new CIDR blocks when allocating, as well as prettier and more intuitive ways to show the current usage of the subnet blocks within the network.

When it comes to using IPv4 within innernet...
Preamble: My CIDR calculations might sound wonky, but please bear with me, as to the broader point I'm trying to make:
IMHO I like the idea of IP's starting with 10., then 6 bits for the top-level "Corporate" CIDR (like "evilcorp"), as in <IP_ADDRESS>/6, allowing up to 64 unique "corporations"/innernet interfaces after that 10., then another 6 bits for the "group"/"department"-level CIDR's (<IP_ADDRESS>/14), allowing up to 64 departments in each "corporation", then 12 bits for the CIDRS of each department.  So the 4096 IPs in each department for assigning to peers (end client machines) are much better: <IP_ADDRESS>/20 (not <IP_ADDRESS>/24).  Remember, all client innernet hosts get disabled/decommissioned, never removed.  My point is this: if each group/department only got 256 IPs, that would feel like too few, especially considering you can't recycle these IP addresses.
PS: I love how innernet has you just choose the CIDR's (it's all about calculating those), then IP address assignment is automatic, taking many of the tougher calculaations out of the hands of the end user.


Missing .AddAzureSignalR()

Since this is the asp.net core "azure" signalr example the .AddAzureSignalR() extension method call is missing in the ConfigureService() method in the step 4, also the description "By not passing a parameter to AddSignalR()" it doesn't correspond to this method but to  .AddAzureSignalR().

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

ID: edb1fa6c-8433-882f-8b97-4d381f885b1d
Version Independent ID: aad3ec71-363f-3500-8bcd-dc040f71821e
Content: Quickstart to learn how to use Azure SignalR Service
Content Source: articles/azure-signalr/signalr-quickstart-dotnet-core.md
Service: signalr
GitHub Login: @sffamily
Microsoft Alias: zhshang

@BenyErnest Thanks for your comment. We will review the issue and get back to you shortly.

@BenyErnest Thank you for pointing this out. We have gone ahead and made the necessary changes. The updated content should be publicly visible within 24 hours.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Bundle Size is hUUUUUge

Our code: 143.84kb uncompressed, 16.14kb gzipped
All code: 1.43mb uncompressed, 158.21kb gzipped
😮
https://bundlephobia.com/scan-results?packages=bignumber.js@7.2.1,bmp-js@0.1.0,buffer@5.0.2,exif-parser@0.1.9,file-type@8.1.0,jpeg-js@0.3.4,load-bmfont@1.2.3,mime@2.3.1,mkdirp@0.5.1,omggif@1.0.9,phin@2.9.0,pixelmatch@4.0.0,pngjs@3.0.0,tinycolor2<EMAIL_ADDRESS>import Jimp from 'jimp/es'

Jimp.read('./exampleImages/npm.jpg').then(image => {
  image.resize(10, Jimp.AUTO).getBuffer(Jimp.AUTO, (err, res) => {
    console.log(res)
  })
})

Offenders (only using stat sizes unless otherwise specified, cause parse time matters!):

utif - TIFF support

total (including deps): 441.35kB 😭 119kB minified
size: 38kb
requires:

jpgjs = 190.02kB
pako = 213.33kB

potential replacements:

<EMAIL_ADDRESS>- 19.6kB minified
<EMAIL_ADDRESS>- 3.8kB minified
both these have no encoder so we'd have to figure that out

bignumber.js - used for hashes #497

size:  84.19kB with tree-shaking 79.41kB, minified 17.7kB
potential replacements:

big.js - 5.9kB minified
buffer? maybe we don't even need the dep
@babel/plugin-syntax-bigint - this would be really cool. IDK how big it would be. the packaged minified is only 1.7kB though

https://developers.google.com/web/updates/2018/05/bigint

Image:
We use a bunch of different libraries to process images. Switching to a library that does multiple could provide a big win. Options

<EMAIL_ADDRESS>- processes png, jpeg, and gif 9.8kB minified

pngjs - encode/decode

potential replacements:

<EMAIL_ADDRESS>- 8.6kB minfified - low downloads though

Lower Hanging Fruit:

exif-parser - load exif data from JPEG image

size: 20.7kB minified
potential replacements:

<EMAIL_ADDRESS>- 5.6kB minified
<EMAIL_ADDRESS>- 14.5kB also supports TIFF!~ doesn't support node runtime!?
<EMAIL_ADDRESS>- 12kB

mime #496

size: 32.3kB minified
mime/lite = 8.21kB
potential replacements:

<EMAIL_ADDRESS>- 4.7kB minified

probably supports less formats, but we really only need 5 anyway (gif, tiff, png, jpeg, bmp)

Just write our own. We only need to identify the above 5

I'm gonna switch exif-parser to jpeg-exif once my two PRs are merged.
https://github.com/zhso/jpeg-exif/pull/9 - So we don't have to read the file twice
https://github.com/zhso/jpeg-exif/pull/10 - So we can support tiff as well.
The only information from exif that we use is the orientation. jpeg-exif exposes that property so we can easily switch to it! 15kB of the bundle but that's still one less cut 😜

great bit of analysis - i'll have to do the same on my projects!

Bundlephobia is a great tool! With that plus webpack-bundle-analyze you can really hunt down bloated dependancies.

Opened #496 to switch to our own mime type lookup.

Opened #497 switch from BigNumber.js to any-base

Yesterday we started using jimp to rotate image created using node-canvas.
Adding jimp added 2000~ files to the project and it seemed quite large.
The only thing being done is
`Jimp.read(canvas.toBuffer()).then(image => {
image.rotate(rotation);
                image.getBuffer(Jimp.MIME_PNG, (err, buffer) => {`

Is there a lighter weight version of JIMP that supports just this? Or do you have any suggestions on how to rotate without diving into image processing code?

I'm currently researching which image library might fit best for my "server-less" web app. I just need scaling, resizing and filling background with a color. It would be really cool if features would be modularized so that only that code is included in ones project which you actually use.
Apart from that, this seems to be a very nice project!

The problem with the bundle doesn't really come from the functions that jimp does. Rather it is the encoding and decoding of images that adds a lot to the bundle. If you were to take out all the rotate, resize, etc the bundle size would basically be the same because the image libraries are the majority of the bundle.
Does your web app require jimp to decode the images? If the answer is yes then then you won't really find a smaller pure JS image processing library.

@Killian22 the same goes for you. decoding images is hard and takes some code to do. The getbuffer function uses libraries fro png, jpg, bmp, and tiff. those libararies account for the brunt of jimp.
I've wrestled with this fact for the past week. In the future I may come up with a way to only include the decoding libraries that are needed but until then I think the best solution is to lazy load jimp or load it in a webworker. Since jimp really shouldn't be needed on page load you should be able to do this.
In my mind the two places you would use jimp in a frontend project would be:

during the build step to transform images somehow
after the page loads and a user wants to do something with an image

I good way to do this would be with code-splitting in webpack with import() and possibly in combination with prefetch or preload so the library is already loaded once the user gets to it.
I've also been thinking of breaking off individual function into modules that just operate on buffers. But this would require a pretty big overhaul of the codebase and a major release. Speaking with @oliver-moran backwards compatibility is a big focus and a major breaking change isn't on the horizon. Right now I want to focus on error handling.

Thanks! That is what I wanted to hear!  ( I think ) .  The 2k File check in just was kinda scary adding to the project haha.
We're not using this front-end. We have draw routines on the front end using canvas. And even though our app is C# Web app , we are using Node + IISNode + node-canvas so that we can use the same code frontend + backend.
Our backend images are used in reports and those images need rotated, but we don't want to update draw routines, so googling 'node image rotate' this came up first and I gave it a try!
Thanks for your activity!

@hipstersmoothie Hello, I'm author of exifr and I'd like to suggest it as the replacement for exif-parser. I have written exifr from the ground up for performance and modularity. In its full it supports many formats (jpeg, tiff, heic) and metadata types (tiff/exif, xmp, iptc, icc, jfif) each of which adds +3-10kb to the full bundle. But it's all modular so every feature and parser can be excluded. Even exif tag dictionaries (believe it or not but just dictionaries can take up to 40kb) can be avoided altogether driving the size of the library down to the 15kb core.
I know it's still a bit more than desired but I'd like to improve on that, make exifr even more modular, lighter and tailor it to your needs if you'd be interrested.
The 15kb consists of two things:

chunked reader - reads just a first few bytes of the image, saves a lot of memory and time, enables to parse hundreds of photos without crashing the browser
support for node.js and browser - there's a wrapper for ArrayBuffer, Uint8Array and node's Buffer

Since jimp works with the full image, the chunked reader is quite useless here and could be dropped altogether. This specifically is already possible but there's more that could be done and like I said, I'd be happy to work with you (on both sides, improvements to exifr as well as PRs to jimp) if you would be interrested.
Thanks, Mike

If it can get the bundle size down and is a better solution for exif parsing, I'm all for you integrating it into jimp! Feel free to make PRs as you see fit and I'll try to address them in a timely manner

I'm gonna close this. Jimp included image encoder and decoders and those aren't small. If a use wants a smaller jimp the best way is to use jump custom to only include what you need


README: Reference CM5, CM5IO

Should we suggest disconnecting any peripherals from the IO board e.g. USB keyboards. If the host is limited to 900mA for USB3 for power + data then that's not necessarily enough. The workaround is to use a powered Raspberry Pi hub between the host and the DUT.

Should we suggest disconnecting any peripherals from the IO board e.g. USB keyboards.

That's probably the easier / simpler / more-reliable option?
ping also @nathan-contino because it probably makes sense to use similar language here and at https://www.raspberrypi.com/documentation/computers/compute-module.html#flash-compute-module-emmc ?


KAFKA-8315: fix the JoinWindows retention deprecation doc

Fix a javadoc mistake introduced in https://github.com/apache/kafka/pull/5911/files#diff-35e3523474fa277a63e36a3fe9e22af8 .
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang , can you take a quick look at this? (in case you had some special intent in #5911 )

Flaky test.
Retest this, please.

LGTM. If @mjsax agrees with the above conversation we can merge this PR.
I think we can also fix the other issue about not leveraging the period on changelog topic in a separate PR.

Cherry-picked to 2.3 as well.


[LDA] - (Core) Backward Compatibility on Luxoria Architecture

Describe the Bug
When a change is introduced to the current Luxoria architecture, modules built prior to this update become incompatible and cease to function as expected. This breaks backward compatibility and impacts existing integrations.
Steps to Reproduce
Use a module developed for the pre-change architecture.
Introduce a structural change in the Luxoria architecture.
Attempt to load or run the pre-change module.
Observe that the module fails or exhibits incorrect behavior.
Expected Behavior
Modules developed before the architectural changes should remain functional, or there should be a clear migration path or compatibility layer to ensure they work seamlessly.
Suggested Fix
Implement a backward compatibility mechanism, such as version handling or an abstraction layer, to ensure legacy modules remain operational when architecture changes occur.

Add Gateways to core functions
Working on implementation of some gateways for :

IEventGateway -> IEventBus
IModuleContextGateway -> IModuleContext
ILoggerGateway -> ILoggerService


[SQL] [WIP] Switch internal catalog types to use URI instead of string for locationUri

What changes were proposed in this pull request?
This should help prevent accidental incorrect conversions between Path <-> URI.
How was this patch tested?
Existing tests.

Test build #70379 has started for PR 16341 at commit 6e0cc04.

Test build #70380 has started for PR 16341 at commit 155f9ab.

Test build #70379 has finished for PR 16341 at commit 6e0cc04.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70379/
Test FAILed.

Test build #70380 has finished for PR 16341 at commit 155f9ab.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70380/
Test FAILed.

Test build #70394 has started for PR 16341 at commit bcdac16.

Test build #70394 has finished for PR 16341 at commit bcdac16.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70394/
Test FAILed.

Test build #70762 has started for PR 16341 at commit 16b6030.

Test build #70762 has finished for PR 16341 at commit 16b6030.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70762/
Test FAILed.

Test build #70824 has started for PR 16341 at commit d4f4fe0.

Test build #70824 has finished for PR 16341 at commit d4f4fe0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70824/
Test FAILed.

Merged build finished. Test FAILed.

Test build #70934 has started for PR 16341 at commit 0388ae4.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70934/
Test FAILed.

Test build #70978 has started for PR 16341 at commit a47e724.

Test build #70978 has finished for PR 16341 at commit a47e724.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70978/
Test FAILed.

Merged build finished. Test FAILed.

Test build #71236 has started for PR 16341 at commit 23b30b9.

Test build #71236 has finished for PR 16341 at commit 23b30b9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71236/
Test FAILed.


why return Invalid target_lang.

I deploy as a docker container, but translate api response:
{"code":-32600,"message":"Invalid Request","data":{"what":"Invalid target_lang."}}

response already tells you why

I use it translate english to chinese. Before a week ago It works. how to make it work?

read docs.

I have read docs and I run it with
docker run -itd -p 1188:1188 ghcr.io/owo-network/deeplx:latest
Am I miss something?

I tunk  back to Bob plugin DeepLX 1.0.8 version. It work.
So it must  be a bug of new version Bob plugin DeepLX 1.0.9.


fix(ui): use Select widget for invoice expiry

Description:
Use Select widget for invoice expiry
Motivation and Context:
Improved usability
How Has This Been Tested?
Manually
Screenshots (if appropriate):
Before:

After:

Types of changes:

UI enhancement
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.002%) to 20.227% when pulling b54e58e3653501916e322d81f961178eff987e89 on mrfelton:refactor/invoce-expire-select-widget into f283421b5fc62fabeca1e5c1c1ec7e4b09158f0f on LN-Zap:next.

Issue with far the future date should be resolved @JimmyMow

Copy needs update


Update api-management-caching-policies.md

Both vary-by-developer and vary-by-developer-groups showed as false when I made a fresh cache policy, so they should be documented as such.

@dcbrown16 : Thanks for your contribution! The author, @vladvino, has been notified to review your proposed change.


"Cannot find module 'graphql-request' or its corresponding type declarations" when using with pnpm

Environment

Operating System: Windows_NT
Node Version:     v20.11.1
Nuxt Version:     3.10.3
CLI Version:      3.10.1
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, graphql-client
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Describe the bug
After updating nuxt from 3.9.3 to 3.10.3 I'm getting this error:
$ pnpm typecheck

> nuxt-app@ typecheck C:\...\nuxt3-2024-03-02
> nuxt typecheck

.nuxt/gql/default.ts:1:52 - error TS2307: Cannot find module 'graphql-request' or its corresponding type declarations.

1 import type { GraphQLClient, RequestOptions } from 'graphql-request';
                                                     ~~~~~~~~~~~~~~~~~

.nuxt/gql/default.ts:2:21 - error TS2307: Cannot find module 'graphql-request' or its corresponding type declarations.

2 import { gql } from 'graphql-request';
                      ~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: .nuxt/gql/default.ts:1

 ERROR  Command failed with exit code 2: vue-tsc --noEmit                                                                                21:52:41

  at makeError (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/chunks/index3.mjs:1259:11)
  at handlePromise (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/chunks/index3.mjs:2497:26)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async Object.run (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/chunks/typecheck.mjs:73:7)
  at async runCommand$1 (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/shared/nuxi.a9f3bca7.mjs:1648:16)
  at async runCommand$1 (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/shared/nuxi.a9f3bca7.mjs:1639:11)
  at async runMain$1 (/C:/.../nuxt3-2024-03-02/node_modules/.pnpm/nuxi@3.10.1/node_modules/nuxi/dist/shared/nuxi.a9f3bca7.mjs:1777:7)

 ERROR  Command failed with exit code 2: vue-tsc --noEmit                                                                                21:52:41

 ELIFECYCLE  Command failed with exit code 1.

Expected behaviour
Should not fail ;-)
Reproduction
https://github.com/some-user123/nuxt-graphql-client-issue-471

pnpm install --frozen-lockfile
pnpm prepare
pnpm typecheck

https://github.com/some-user123/nuxt-graphql-client-issue-471/actions/runs/8152835329/job/22283031110
Additional context
No response
Logs
No response

@some-user123 This was caused due to upstream changes in the graphql-request package (jasonkuhrt/graphql-request#616), hence the dependencies for this module need to be updated.
For the time being you can manually install the dep as seen below to avoid the error:
pnpm add -D<EMAIL_ADDRESS>

I was withholding nuxt updates so far because I don't like workarounds ;-) (In some weeks nobody knows, why the package was added and it will stay there forever...)
When can we expect a solution? Wouldn't it just be an update to the package.json of nuxt-graphql-client?
Meanwhile graphql-request 7 was released which causes module resolution issues - not sure, if this is related.

@some-user123
For the time being you can manually install the dep as seen below to avoid the error: pnpm add -D<EMAIL_ADDRESS>
I'm still getting the error about graphql-request after trying this workaround.

Operating System: Darwin
Node Version:     v20.11.0
Nuxt Version:     3.12.3
CLI Version:      3.12.0
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, compatibilityDate, modules, typescript
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

package.json
  "devDependencies": {
    "@graphql-codegen/typescript-graphql-request": "6.2.0"
  }

pnpm dev

> nuxt-app@ dev /...
> nuxt dev

Nuxt 3.12.3 with Nitro 2.9.7                                                                                01:57:09
                                                                                01:57:09
  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

  ➜ DevTools: press Shift + Option + D in the browser (v1.3.9)                                                           01:57:14

✔ Nuxt Nitro server built in 3056 ms                                                                              nitro 01:57:23
ℹ Vite client warmed up in 8491ms                                                                                01:57:24
ℹ Vite server warmed up in 9043ms                                                                                01:57:24

 ERROR                                                                                01:57:25
 **ERROR(vue-tsc)  Cannot find module 'graphql-request' or its corresponding type declarations.**

I am facing the same problem. I tried the solution proposed by @Diizzayy without success.
Furthermore, I also tried installed the "missing" packages without success


iOS XCode fatal hanging error while Unlock

Created an XCode project, launched it via terminal "react-native run-ios", while launching got a bunch of permission (EACCES) errors, overriden by "sudo ..." commands

opened .xcodeproj file in XCode (7.2.1)

got an Unlock issue as in attached screenshots

made sure I did change the owner of all parent folders of the project by
"sudo chown -R $MYSELF ~/PROJECTPATH"

XCode did not allow to exit normally after the error, I forced the exit manually

[x] What's the version of React Native you're using?

the latest available today (installed today, 16/03/2016)

[x] Does this occur on iOS, Android or both?
iOS

[x] Are you using Mac, Linux or Windows?
Mac OS X 10.11.3

Hey, we use Github for issues only and all questions should be asked on StackOverflow. Please consider posting your question up there providing more details on what specifically you'd like to achieve!
This is for us to keep the number of issues smaller so that we can iterate on React Native versions faster and provide you with the better developer experience.
If you have any ideas on how we could improve the entire process, please share your thoughts on React Native Community group.


[feature request] cache for saving with different frame speeds

If you save a gif, where it is analyzed for changes between frames and then saved to a file, that information could be preserved to make saving the gif much faster if all the user does is change frame times.
For example, if you save a gif with frame timings of 50 ms, but realize that that is too slow, overriding frame times to 30 ms would not change the individual frame-to-frame compression that has to occur when saving. Even modifying individual frames, such as extending a frame in case where it contains text that otherwise would disappear too quickly to be readable, would not change the frame-to-frame compression.
It should be possible to cache the compression data after saving the gif the first time, and use that on subsequent saves. Changes like overriding or decreasing frame times would not invalidate the cache, but reversing, transitions, etc. would.
This would vastly speed up workflows where all that a user does is change frametimes.
Since such a cache would take up additional system memory, this could be an option in the save dialogue or settings, so that users that don't often modify frame times as part of their workflow don't have additional memory usage for something they don't benefit from.

Alright. :)
Just to add some details of how it works right now:

The frames are only analyzed if the option Detect unchanged pixels is enabled. (So, if you disable this option right now, you can speed up your framerate tests)

The frames are cut (if they retain the same pixels of the previous frame) and saved into a new file inside a temp folder.

This temporary folder gets deleted after the encoding, so the analyzed frames are lost.


#1706 Fix the property mismatch in Annotation CronJobConfiguration of s3-integration-starter

Description
Fix the property mismatch in Annotation CronJobConfiguration of s3-integration-starter
Reference
Issues: #1706
Check-List

[ ] All Acceptance criteria of user story are met
[ ] Accessibility was considered and tested (On UI Change)
[ ] JUnit tests are written (60% CodeCov)
[ ] Internal Review is maintained
[ ] Documentations external and internal are completed
[ ] Smoketest successful (Manual E2E-Test depending on Change)
[ ] No waste on Branch left (e.g. console.logs)
[ ] Board is up-to-date
[ ] Internal Services / Artifacts updated (Depending on Change - See Dependency Graph)
[ ] Openshift environments are prepared (Secrets, etc.) and release-issue is maintained

Aufgrund von https://github.com/it-at-m/digiwf-core/issues/1706#issuecomment-2126288018 werden wir das über einen anderen PR lösen müssen.


Need advice on how to change manifest.json for using node-fetch in background script

Hello:
I tried to write one chrome extension, which get some Json format data from content script, and send it to localhost http server.
I use Node.js version 15.10.0 on Windows 10.
My current manifest.json look like this:
{
"manifest_version": 2,
"name": "DOMJsonData",
"description": "Extension to post data to http server with fetch",
"version": "1.0",
"default_locale": "en",
"icons": {
"128": "icons/icon128.png",
"48": "icons/icon48.png",
"16": "icons/icon16.png"
},
"browser_action": {
"default_icon": "icons/icon16.png",
"default_popup": "src/popup.html"
},
"content_scripts": [
{
"matches": ["<all_urls>"],
"js": ["lib/jquery.min.js", "src/content.js"]
}
],
"permissions": ["tabs", "activeTab", "contextMenus", "storage" ],
"background": {
"scripts": ["src/background.js"]
},
"web_accessible_resources": [
"lib/",
"src/"
]
}
I installed node-fetch npm package, version: 2.6.1
I had the following background.js file:
const fetch = require('node-fetch');
chrome.runtime.onMessage.addListener(
function(request, sender, sendResponse) {
if( request.message === "export_dom_data" ) {
console.log("Post data to http server");
fetch('http://localhost:3000/', {
method: 'post',
body: request.data
}).then(function(response) {
return response.text();
}).then(function(data) {
console.log(data);
});
}
}
);
I also ran http-echo-server on localhost (npm version 2.1.1), if I wrote the following JavaScript to post http data to localhost http-echo-server, it worked.  The code was like this:
const fetch = require('node-fetch');
let json_data = {
npm_title: "node-fetch",
version: "2.6.1"
}
fetch('http://localhost:3000/', {
method: 'POST',
body: JSON.stringify(json_data),
headers: { 'Content-Type': 'application/json' }
}).then(res => res.text())
.then(json => console.log(json))
.catch(err => console.log(err))
I have the following questions:

How I can change manifest.json, so my Background.js can use the “node-fetch” npm package. For jquery, I can download jquery.min.js, and put it in folder “lib”, which is easy.
However, when I install node-fetch npm package, I can’t find such min.js file for node-fetch package.  I looked at your extension, but I didn’t find any manifest.json file for your extension; besides, your extension is way more complicated.  I only need to send some Json data to a fixed stand-alone http server. (I will use C# to write a http server later, but now, simply use http-echo-server for testing.)
I found Google has something like background fetch: https://developers.google.com/web/updates/2018/12/background-fetch
I want to know if I can use such background fetch API to send out some Json data to an http server in the localhost, then I don’t have to install other npm package or have other headache like find min.js file for npm packages.
Please advise!

This question is unrelated to this repo and should be asked on stackoverflow instead.
I am answering you anyways.
fetch is a Web API and doesn't requires polyfill in most modern browsers. You should be able to use it in your extension without node-fetch.
node-fetch is a fetch polyfill exclusively for Node.js, which does not implement the fetch API (yet). node-fetch is a wrapper for Node.js native http module, which absent in browsers. Therefore, it won't work in Chrome extensions.
require() function doesn't works in browsers, native import statements does. If you use any other libraries and would like to use it with require() calls, you will need a JavaScript bundler, like webpack, rollup, etc.


Update using-directive.md

@Rick-Anderson Here, the original text is needed: It's meant to drive readers to a different article for a different use of using.
I'll close this.

I was thinking also is not exactly correct because one is a directive and the other a statement. But it's close enough. Probably too verbose to say
The using keyword  is different than the using directive. The using keyword  used to create using statements, which help en...
That was my point.  aslo mean in addition, but it's not really additional, it's different.


Sample project works from the command line, doesn't compile from Xcode (CCurl missing)

I followed the steps on the Kitura & Kitura-Sample pages and manage to get the server running from the command line, but it doesn't compile from Xcode. The error is: 'No such module CCurl'.
I'm running Xcode 8b6 with the 25-07 snapshot.

@greg3z Please try running make openXcode in the command line. It will generate Xcode project and open it for you.
Alternatively, please see https://github.com/IBM-Swift/Kitura/wiki/Building-your-Kitura-application-in-Xcode#troubleshooting

Hello Vadim and thank you for your quick answer!
The make openXcode command works as intended but once in Xcode, I still get the  'No such module CCurl' error, even after modifying the Library Search Path as recommended in your link.

You are welcome, Greg. Do you have curl command on your Mac? If not, please try brew install curl.

Yes, curl is installed, here is the version I have:
curl 7.50.0 (x86_64-apple-darwin15.5.0) libcurl/7.50.0 SecureTransport zlib/1.2.5

OK, let somebody from the Kitura core team handle it.

Any updates on this? I'm having the same issue.

I'm running XCode 8 GA, the Toolchain is set to the default one. Kitura-Sample builds, but won't run. We need to investigate this some more.

Hi @greg3z, @Lascorbe  are you still having the problem? I have managed to build and run Kitura-Sample on XCode 8.0 again with the default toolchain.

Hello @rob-deans, I'll check that tonite as I don't have my mbp with me.

No, sadly, with the last Xcode (8A218a) and the default toolchain, I get the same error.

@greg3z could you show us your search path inside Build Settings under KituraSample, it should look something like this:

I have those 4 (the 1st is twice in the list):
/Users/glhotellier/Library/Mobile (this isn't a valid path btw, probably the beginning of Mobile Documents...)
Documents/com~apple~CloudDocs/code/Kitura-Sample/Packages/CCurl-0.2.1
Documents/com~apple~CloudDocs/code/Kitura-Sample/Packages/CHTTPParser-0.3.0/Sources/CHTTPParser/include
All those path are configured as non-recursive

@greg3z Someone else encountered a similar problem before and was able to solve the issue, presumably by removing spaces from path.
https://gitter.im/IBM-Swift/Kitura?at=57dab85bc3e7045a3050b2ee

Thank you @youming-lin!
Indeed, it was because of a space in the path where I installed the project. I tried installing it on a path with no spaces and it worked!


Solve problem day2 with 2 less variables.

New solution for day2 problem with using 2 less variables.

بسیار عالی


Azure Functions v2 Programming Model for Python - GA enhancements

Support for creating functions in new files (as blueprints)
Create experience enhancements

Details are given in the doc shared via email

#2 - Split programming model version as a next step in quick pick for Create.

Fixed by https://github.com/microsoft/vscode-azurefunctions/pull/3692


Support CUDA 11 + linux fixes

This adds support for CUDA 11, but still checks for CUDA 12 in the main cmake config. The few places in the CUDA code where CUDA12-specific features are used are behind #include guards.
The patches in the patches/ dir need to be applied to the recursively checked out repository, as we need to patches to the glad, tiny-cuda-nn and pybind11 source repos in include/.
The first is needed as a shared library (and so the Python module) on Linux requires the code in the tiny-cuda-nn library to be built as position-independent code (-fPIC). I did not see the required options to enable this in the upstream code, hence the patches like this.
The patch to pybind11 is needed when building against CUDA12 to work around https://github.com/pybind/pybind11/issues/4606
Finally, I had an error related to the use of #pragma once, which I worked around using include guards.

Yep, all done!

Found a small error in the pybind11 patch while trying to apply it on a different workstation. Fixed now.


[Suggestion] Responsive Design

Hi man
First of all, I'd like to say this is an awesome project!
But I am just wondering if you have any plans to introduce some mobile-friendly features to the project,
like this one for instance Jquery DataTable Responsive Extension

Hi man
Yes, this approach looks quite interesting, thanks for the suggestion.
I don't plan to go in that direction at the moment (especially if it would require DOM manipulation).
Afterwards, if someone wants to open a PR, it is not completely ruled out


Add annotations

they cause a lot of warnings still, and i don't yet know how to communicate the way terms-generators works to the annotation language

yay!