<EMAIL_ADDRESS>No typescript error if I use PIXI without importing it. Just runtime errror that is undefined.

Expected Behavior
Typescript error
Current Behavior
No error
Possible Solution
I think you guys cast pixi as a global somehow
Steps to Reproduce
create new file and add
// No PIXI import
new PIXI.Point()
No typescript error, but run time error.
Environment

pixi.js version: 5.2.1
<EMAIL_ADDRESS>Browser & Version: e.g. Chrome 67
OS & Version: e.g. Ubuntu 18.04
Running Example: url

The typings aren’t exactly perfect. They reference a global PIXI namespace, but this is only available if you are using the browser dist file. If you are building using webpack or a bundler, you need to import * as PIXI from ‘pixi. js’
If you look at the wiki there are a bunch of boilerplate projects.

I think you missed my point. I'm not importing pixi at all. So PIXI should be undefined, but somehow typescript thinks PIXI is present. @bigtimebuddy

If you could provide a sample project, that’d be helpful. Not enough information in your post to understand what’s going on. I assume your tsconfig is using the typings for pixi which says PIXI global is okay?

@bigtimebuddy  I didn't include the tsconfig because doesnt have anything special.
Just this:

  "typeRoots": [
    "./node_modules/@types"
  ],

To reproduce just create a new file like this:
new PIXI.Point()

run yarn add pixi.js
Configure typescript and run typechecker.
It should error because you didn't import PIXI. but it doesnt

Are you including<EMAIL_ADDRESS>as a dependency?

I'm pretty sure that this is intentional behavior. AFAIK TypeScript auto-detects globals (i.e. what would be available if you used a CDN) from type definitions which specify them.

I'm having this issue too in one of my projects. Thankfully this issue exists, so I created a small repo that reproduces the error:
https://github.com/JacobFischer/pixi-ts-global-error
The error appears to be that the current pixi.js.d.ts definitions pollute the global variable by declaring the PIXI namespaces without directly exporting them, so they just exist as a global ambient declarations to TypeScript as soon as PIXI is first imported, regardless if it actually is a global or not.
One solution would be to update the definitions to move away from ambient declarations and use exports instead.
I can try to put together a PR to resolve this.

I'm pretty sure that this is intentional behavior. AFAIK TypeScript auto-detects globals (i.e. what would be available if you used a CDN) from type definitions which specify them.

If this is intentional I think has a huge design flaw. You probably don't want to design something that will work at compile time, but will blow at run time. I hope you guys realize how important is for types to actually work properly.

I can provide some context here.
First, if you are importing as modules import { Application, Graphics } from 'pixi.js', types should work because we also export the namespace as the module:
declare module "pixi.js" {
    export = PIXI;
}

It's true that there is also a global PIXI namespace, however, there are some users that do not bundle PIXI using webpack/rollup/etc, but they still need typing information. The current typings serve both module and ambient use-cases. For instance, if you are including PixiJS from a CDN or the distribution (bundled) build.
If someone would like to propose an alternative that supports both these cases, please let us know.
Also, we are about to wrap our conversion to TypeScript, which will likely support module-only typings for all the low level packages (e.g., @pixi/core) and the namespace + module typings for the bundle (e.g, pixi.js or pixi.js-legacy).

I believe the "Typescript" way to approach modules is to not assume any modules are automatically loaded globally. This way developers have the freedom to inject a any modules they desire globally, like pixi.js in this case, and then extend their own global types to inform Typescript what they did.
For example, if a developer excepts pixi to be available globally as they loaded it into the window in browser, they just have to tell TypeScript they did that:
import * as PIXI from "pixi.js";

export declare global {
  interface Window {
    // add you custom properties and methods
    PixiOrWhateverYouWantToReferToItGlobally: PIXI;
  }
}

That’s fair.
Another important quirk of our current typings is they are generated from JSDocs. This assumes global namespacing. This approach is just temporary for the time being until we can auto generate typings.

Ah neat.
I created a PR that should be a simple fix for this issue. However as noted developers that use pixi globally will have to tell Typescript they are doing so. There should be no functional changes for non TS users as it only changes one line in typings file generated by the build script.


Folder IMAP, Sent, Drafts...

I do not have the option to select which folder is sent. I used to be.
Is it possible to add it again?

I'm confused what you mean, can you elaborate?

I can not select the Sent and Deleted folder on my IMAP server

See:
https://github.com/nylas/nylas-mail/issues/1457
This has already been soluced, but now it is not

unfortunately the fix put in https://github.com/nylas/nylas-mail/issues/1457 did not get put into github which is why it doesn't work in our branch. we'll see if we can look at the history in that issue and figure out what they did to fix it and implement it

Gracias!

@seesemichaelj that fix should be in the Nylas code dump.

It is already fixed in the latest version
Thanks!!!!

Awesome!


build(ci): workflow review

This PR resolves []
Description

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

review + simplify workflows on ci - Brian

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (review + simplify workflows on ci - Brian)

  Generated by :no_entry_sign: dangerJS against 17c7c77cdd9d85ea7dc586fcadcac3e571671477


Darwin: introduce a global override for debug prefix map entries

This patch adds a new Darwin Swift driver environment variable in the spirit of
RC_DEBUG_OPTIONS, called RC_DEBUG_PREFIX_MAP, which allows a meta build tool to
add one additional -fdebug-prefix-map entry without the knowledge of the build
system.
See also https://reviews.llvm.org/D119850
rdar://85224717

See also https://github.com/apple/swift/pull/41388

@swift-ci test

@swift-ci test

@swift-ci test


Inline Edits: Hide the  clear button from screen readers

The inline edit component shifts out of edit mode when the input loses focus. Due to this constraint, the clear button cannot take focus. Screen readers are still able to perceive this button in the DOM however. This button should be aria-hidden to prevent screen reader users from perceiving a button they cannot operate.

I think we're actually going to change the behavior of the Inline Edit so that when you're in edit mode and press Tab, it'll focus the Clear button. And if you press Tab again, then it'll blur the field.

Should we close this one and open another one with the new spec?

Do we have a label we can apply that is something like "waiting on updates from SLDS"? I'm OK with closing this one if that's the case, but depending on how long it is before the SLDS component is updated, I don't want to lose the reason why this component needs updating.

https://github.com/salesforce/design-system-react/labels/SLDS-action-needed label applied.

Sorry I should have clarified. The changed focus behavior is something that we can control and it's captured in a different thread. So this issue is a dupe of this one: https://github.com/salesforce/design-system-react/issues/702


Standardize naming of insecure/unsafe functions

Description

We have a few policy-level configuration functions that allow for insecure verification, useful for testing or private deployments: WithoutAnyObserverTimestampsInsecure, WithoutIdentitiesUnsafe, WithoutArtifactUnsafe. We should pick either "insecure", "unsafe", or some other adjective to describe risky verification behavior.

Just to repeat what I wrote in the slack:
I feel a preference for Unsafe over Insecure in so are that the first one implies "use with caution" and the other implies "inherently bad".
(Tho having typed that out, there is a qualitative difference in these options, isn't there? To try to just validate the bundle absent the artifact is one thing; the integrity of the Sigstore "system" is not at stake. Whereas to verify without ANY observer timestamps does imply that we're doing something other than the default Sigstore path)


Possible to run psc-ide-server, etc. in docker?

Tried the naive thing by "purescript.pscIdeServerExe": "docker-compose run --rm purescript psc-ide-server", which is a valid command in the workspace directory, but of course the core code expects to find the executable on $PATH (the emacs PS integration seems to follow a similar pattern).
Other than wrapping docker calls in executable scripts or submitting a PR, is there a canonical way?

Using the docker image from https://github.com/codewars/purescript this works perfectly for me:
docker run --name pscript --net=host -v $PWD:/$PWD -it --entrypoint bash  --rm ghcr.io/codewars/purescript -c "cd $PWD; purs ide server -p 1234"

I have to set the extension settings to use port 1234 and also change the build command to docker exec -it pscript bash -c "cd $PWD; spago build --purs-args --json-errors".


Numerous errors with docker otbr on Raspberry Pi 4 with SkyConnect

This is mainly about where I am left after the codelab, where everything "looks" alright, but actually, there seems to be a number of underlying issues.  In many of the docs, there is some wording about the docker setup being for ease, or convenience.  In my experience, it nearly is, but isn't.
The hardware I use is from NabuCasa/HomeAssistant, and while I have also asked there, some of what I'm experiencing seems to be more otbr related, and others have had similar issued... but just ended up as being closed as stale here.

docker-compose.yaml
version: '3.3'
services:
    otbr:
        image: openthread/otbr
        privileged: true
        container_name: otbr
        networks:
            otbr:
                ipv6_address: fd11:db8:1::20
        ports:
            - 8181:80
            - 8081:8081
        sysctls:
            net.ipv6.conf.all.disable_ipv6: 0
            net.ipv4.conf.all.forwarding: 1
            net.ipv6.conf.all.forwarding: 1
        volumes:
            - /dev/ttyUSB0:/dev/radio
        command:
            - --radio-url
            - spinel+hdlc+uart:///dev/radio?uart-baudrate=460800&uart-flow-control
            - --backend-interface
            - eth0

networks:
    otbr:
        driver: bridge
        driver_opts:
            com.docker.network.bridge.name: otbr0
        name: otbr
        enable_ipv6: true
        ipam:
            driver: default
            config:
              - subnet: fd11:db8:1::/64
                gateway: fd11:db8:1::1

Full container log, via portainer, is otbr docker logs syslog-userlog.log
System ip 6 route,
$ sudo ip -6 route add fd11:22::/64 dev otbr0 via fd11:db8:1::2
RTNETLINK answers: File exists

And that's basically it.  It "looks" to be up and running okay, and I'm able to form a new network, but I haven't been able to have this play nice with any matter server (specifically HA's python matter-server, but I've tried a few others too), but I'm not even 100% sure whether the problem's here, with the SkyConnect, or with my setup.
otbr has the most detailed logs, and it looks like there's a few things off here, so I decided to see if I could resolve them with some of your help first and foremost.  At this point in time, I don't know enough about the errors in the logs to even know if they are actually errors or not, but here are my best guesses,
The first thing that looks wrong is some of the Platform netif
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.070 [I] Platform------: [netif] Host netif is down
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.071 [I] Platform------: Session socket is ready
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.071 [D] Cli-----------: Input: state
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.071 [D] Cli-----------: Output: disabled
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.071 [D] Cli-----------: Output: Done
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.071 [I] Platform------: [netif] Succeeded to process request#1
Jul 11 15:44:13 6352bc86efa0 otbr-agent[143]: 00:00:00.072 [W] Platform------: [netif] Failed to process request#2: Unknown error -3

The consistent avahi-daemon host name conflicts

Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Host name conflict, retrying with 6352bc86efa0-2
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Registering new address record for fd11:db8:1::20 on eth0.*.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Registering new address record for <IP_ADDRESS> on eth0.IPv4.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Registering new address record for ::1 on lo.*.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Registering new address record for <IP_ADDRESS> on lo.IPv4.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Withdrawing address record for <IP_ADDRESS> on eth0.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Withdrawing address record for ::1 on lo.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Withdrawing address record for <IP_ADDRESS> on lo.
Jul 11 15:44:16 6352bc86efa0 avahi-daemon[126]: Host name conflict, retrying with 6352bc86efa0-3

The dns conflicts
Jul 11 15:44:21 6352bc86efa0 mDNSResponder: Default: mDNSCoreReceiveResponse: Received from <IP_ADDRESS>:5353   22 <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.8.b.d.0.1.1.d.f.ip6.arpa. PTR 6352bc86efa0-6.local.
Jul 11 15:44:21 6352bc86efa0 mDNSResponder: Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.8.B.D.0.1.1.D.F.ip6.arpa. PTR 6352bc86efa0.local.

Jul 11 15:44:21 6352bc86efa0 mDNSResponder: Default: mDNSCoreReceiveResponse: Received from <IP_ADDRESS>:5353   22 <IP_ADDRESS>.in-addr.arpa. PTR 6352bc86efa0-6.local.
Jul 11 15:44:21 6352bc86efa0 mDNSResponder: Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 <IP_ADDRESS>.in-addr.arpa. PTR 6352bc86efa0.local.

The messages dropped by thread, and rejected messages
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.976 [I] Platform------: [netif] Message dropped by Thread
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.976 [I] Platform------: [netif] ADD [M] ff33:40:fd0f:f2e6:34a0:c3e9:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Platform------: [netif] ADD [M] ff32:40:fd0f:f2e6:34a0:c3e9:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (rejected)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:03.977 [I] Notifier------: StateChanged (0x00001000) [Ip6Mult+]
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.024 [I] Platform------: [netif] Message dropped by Thread
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.024 [I] Platform------: [netif] ADD [M] ff33:40:fd0f:f2e6:34a0:c3e9:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.024 [I] Platform------: [netif] ADD [M] ff32:40:fd0f:f2e6:34a0:c3e9:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.025 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.025 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.025 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Jul 11 15:44:35 6352bc86efa0 otbr-agent[143]: 00:00:04.025 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (rejected)

The ChannelAccessFailures
Jul 11 15:44:36 6352bc86efa0 otbr-agent[143]: 00:00:04.819 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
Jul 11 15:44:36 6352bc86efa0 otbr-agent[143]: 00:00:04.820 [I] Mac-----------: Frame tx attempt 16/16 failed, error:ChannelAccessFailure, len:63, seqnum:179, type:Data, src:7ea926d64c8ef8de, dst:0xffff, sec:no, ackreq:no
Jul 11 15:44:36 6352bc86efa0 otbr-agent[143]: 00:00:04.820 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:6966, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
Jul 11 15:44:36 6352bc86efa0 otbr-agent[143]: 00:00:04.820 [N] MeshForwarder-:     src:[fe80:0:0:0:7ca9:26d6:4c8e:f8de]:19788
Jul 11 15:44:36 6352bc86efa0 otbr-agent[143]: 00:00:04.820 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788

Everything could be alright here, and all the problems on the Matter and/or Home Assistant side, but if that's the case, I'd love to know what's the cause of all of the above issues, and how to limit them.  As someone new to this area, with this amount of things "looking" wrong, it's difficult to even know where to start, to debug it myself.
And, as I said, it seems like others have had similar issues, but they just all ended up being closed as stale here.

Closing stale issue.


Column Order list

Can I get the sequence of columns in which they are ordered after drag and drop, because i need to save the order for the user.

Yes, I want to expand on this. Should emit the new columns (aka _internalColumns) along with the reorder and resize events so that you do not need to duplicate effort into calculating the very thing that the ngx-datatable has already calculated (or access what is likely meant to be a private property).
Can you rename issue to capture this larger scope: Emit new columns value (the value of _internalColumns) on reorder/resize.


Quota exceeded when used in tokio executor

I'm getting behavior where the quota per minute that I set is exceeded in a multi-threaded environment. Specifically it seems like the real quota seems about 50% higher than the one I set.
Here is the minimal replication code.
[package]
name = "governor_rate_limit"
version = "0.1.0"
authors = ["jean-airoldie<EMAIL_ADDRESS>edition = "2018"

[dependencies]
governor = { git = "https://github.com/antifuchs/governor" }
tokio = { version = "0.2", features = ["rt-threaded", "time", "macros"] }
nonzero_ext = "0.2.0"

use {
    governor::{
        clock::DefaultClock,
        state::{direct::NotKeyed, InMemoryState},
        Quota, RateLimiter,
    },
    nonzero_ext::nonzero,
};

use std::{sync::{Arc, atomic::{AtomicU32, Ordering}}, time::{Duration, Instant}};

const LIMIT: u32 = 1_200;

async fn fetch_add_forever(
    limiter: Arc<RateLimiter<NotKeyed, InMemoryState, DefaultClock>>,
    count: Arc<AtomicU32>,
) {
    let n = nonzero!(10u32);
    loop {
        limiter.until_n_ready(n).await.unwrap();
        count.fetch_add(n.get(), Ordering::Relaxed);
    }
}

#[tokio::main]
async fn main() {
    let start = Instant::now();

    let quota = Quota::per_minute(nonzero!(LIMIT));
    let limiter = Arc::new(RateLimiter::direct(quota));
    let count = Arc::new(AtomicU32::new(0));

    for _ in 0..4 {
        let fut = fetch_add_forever(limiter.clone(), count.clone());
        tokio::spawn(fut);
    }

    // Wait some time for the spawn tasks to use the rate limiter,
    // but not enought that the quota is reset.
    tokio::time::delay_for(Duration::from_secs(30)).await;

    let value = count.load(Ordering::Acquire);

    // Make sure that the total time of the experiment is
    // less than a minute.
    let delta = Instant::now() - start;
    assert!(delta < Duration::from_secs(60));

    dbg!(value);

    assert!(value <= LIMIT);
}

Which prints
[src/main.rs:49] value = 1800
thread 'main' panicked at 'assertion failed: value <= LIMIT', src/main.rs:51:5

when executed.

...wow, that certainly looks weird. I'll take a look asap!!

I have reproduced this, as well as with an n=1 in both until_n_ready and until_ready.
Hmmm, now that I think about this, isn't this exactly how it should behave? The quota we set here gives the number of elements that can burst - so in your example, you can send 1200 elements in 60s. The code does that - and then waits 30s, while the background tasks are continuing to send elements as the limiter allows the non-burst elements through - that comes out at 150% the burst capacity at the end of the test, because we used 50% of the quota's "per".
If you use let quota = Quota::new(nonzero!(10u32), Duration::from_millis(500)).unwrap();
(where 500ms = (60*1000ms) / LIMIT), then there is only exactly as much burst capacity as a single check would take, and no slack that could be drained. The test then passes with a value of 600, exactly as many cells as would be allowed in a 30s period in the original test, if there was no burst capacity.
Sounds like the quota and its interaction with burst capacity is not intuitive enough / needs some better docs - in particular, I think the per argument in new is confusing - it took me a bunch of time to understand what formula I was supposed to use to get the right value there.

Alright so now I understand better than to your explanation & docs. The behavior I'm looking for is a quota that gets fully refilled every interval, as opposed to a BUST quota that gets refilled periodically.
Do you think such behavior could be possible or would it require a different algorithm?

Hm, no, I don't think that's quite possible with the GCRA; that algorithm is meant to provide a very even flow of quota (shaping traffic as it goes).
It just occurred to me that by combining different n in check_n, it's possible to run into unfairness issues:

One thread tries to handle a thing that costs 10 "cells", and is put to sleep waiting for the rate limit to allow that.
On another thread, a task rapidly does things that cost 3 "cells" each, and never allows burst capacity to accumulate past 3 cells, which immediately get consumed.

That would block the first thread indefinitely. We don't do any scheduling to allow for the too-fast task to slow down - in fact, that would be an interesting use case for a second rate limit (:

I think the improved constructor does the trick so I'll close this.


Change the value of STRVAL_EMPTY to empty string

Describe your PR, what does it fix/add?
See the title. This was causing unpredictable behavior with screen shaders (and maybe some other variables too?).
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
This might be considered a breaking change for some, including me.
Is it ready for merging, or does it need work?
Ready

this breaks every single string config value. Please read the codebase before making such changes.


Investiage why empty namespaces are stored in Namespaces.properties

ERROR o.e.winery.common.ids.Namespace:28 <init> - Empty URI has been passed to Namespace constructor.

Wrong/strange entries:
= ns146
C = ns147
CapCanHostMySQL-DBMS-5.5 = ns149

Doesn't seem to be an issue anymore


testing/ostest: add nxevent test into ostest

Summary
testing/ostest: add nxevent test into ostest
Depends on: https://github.com/apache/nuttx/pull/12802
Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
ci-check

Does it require to adjust testing/ostest/CMakeLists.txt as well?

Does it require to adjust testing/ostest/CMakeLists.txt as well?

Yes, thanks for review, addressed.


Let's update the readme with instructions on how to "run the demo".

          Let's update the readme with instructions on how to "run the demo".

Originally posted by @geoknee in https://github.com/statechannels/SCBridge-Wallet/pull/110#discussion_r1363454522

Also add "caveats" section or "shortcuts" to be up front about how we have cut corners for the demo / what it would take to take this into production.

Some of this is done on #136


fix(breadcrumbs): import rxjs creation methods from 'rxjs'

Bug Report
The current breadcrumbs component implementation does not import merge and fromEvent from 'rxjs', which is not the correct way for rxjs 6.x and thus fails on build if rxjs-compat isnt installed.
What is the expected behavior?
Both creation methods should be imported from 'rxjs'
Other information
See it in the source code

Thank you for the Issue 👍


Error: unknown command "chart" for "helm"

Our Azure DevOps builds suddenly started failing with below error no changes from our end, we are pushing charts to ACR and its been working fine from past 4 months all of sudden builds started failing!! please help
Error: unknown command "chart" for "helm"
Not sure why we are getting errors suddenly, we are using ubuntu-latest agent and i tried specifying installing latest helm version as well in build pipeline. Looks weird to me ! can someone help helm support team?
Commands:
- bash: |
   export HELM_EXPERIMENTAL_OCI=1
   echo '$(registryPassword)' | helm registry login $(containerRegistry) --username $(registryLogin) --password-stdin
   helm chart save $(System.DefaultWorkingDirectory)/helmchart/ $(containerRegistry)/$(helmRepository):$(tag)
   helm chart push $(containerRegistry)/$(helmRepository):$(tag)

@jdolitsky Can you take a look at this issue? Thanks very much.

@yxxhero @jdolitsky I also want to know whether azure supports helm 3.7?

Actually in Helm 3.7.0 chart is not a command at all. Take a look at release page:
https://github.com/helm/helm/releases

Duplicate of #10145

Closing as a duplicate


Add ssl cert options

This change adds the following ssl/certificate options for connections:

sslcert
sslkey
sslcertmode
sslrootcert

Thank you very much for the improvement and the test coverage.

Thank you for the improvement and test coverage!


[Release Radar Request] Luciferin, bias lighting and ambient light project.

This is the first submission so I'll try to give you some context.
Open Source Project name
Luciferin
What is your project?
Luciferin is a generic term for the light-emitting compound found in organisms that generate bioluminescence like Fireflies and Glow Worms. The Luciferin project takes its cue from this world.
Firefly Luciferin is a Java Fast Screen Capture PC software designed for the Glow Worm Luciferin C++ Arduino firmware,
the combination of these software create the perfect Bias Lighting and Ambient Light system for PC.
Here two videos that shows Luciferin in action on a videogame, DooM Eternal.

and on a standard youtube video:

Version
2.0
Higher version
No response
Date
November 15, 2021
Description of changes

Added an option menu to the Web Interface where you can change all firmware related settings without the needs of reflashing the microcontroller.

GitHub Repo
https://github.com/sblantipodi/firefly_luciferin
https://github.com/sblantipodi/glow_worm_luciferin
Website
https://github.com/sblantipodi/firefly_luciferin/wiki
https://sblantipodi.github.io/glow_worm_luciferin
Link to changelog
https://github.com/sblantipodi/firefly_luciferin/releases/tag/v2.3.1
Social media
https://twitter.com/sblantipodi/status/1460195000336232451
Anything else to add?
In addition to the dynamic halo effect behind the monitor, with Luciferin you can control the LED strip behind your monitor (or whereever you want) like any normal RGB strip using a Web Interface

or with the Home Assistant Integration

Firefly Luciferin PC software gives you more control over all the features

There are a lot of light effects and a music mode:

Firefly Luciferin PC software is a very optimized software and it has nearly no impact on your system performance, it's written in Java but thanks to JNA it has access to the OS API that uses GPU hardware acceleration.

This is the simple circuit to create the hardware needed for Luciferin.
Basically you need an Arduino (ESP8266 or ESP32), a LED strip, some resistors and capacitors and a logic level converter.

for people who are not able to create a circuit, I released a Gerber file, the gerber file is a file that you can "print" using your favourite PCB Fabrication Manufacturer. In this way you don't need to do all the traces in the circuit.

the PC software, the firmware and the Gerber files for the PCBs are all open source on the github repo.
there is even a complete wiki to getting started here:
https://github.com/sblantipodi/firefly_luciferin/wiki
Firefly Luciferin PC software can run on Windows and Linux, macOS version is coming when it's ready.

Amazing! This is awesome and very comprehensive! Thank you ❤

added some more infos and screenshots of the PC software.
thank you for creating such a great community Mish!

Can you please @ me when you've got the next big version of this. Would love to feature it but we have too many others with major changes that were done in November. I would especially love to release it when you have the macOS version available since a lot of our readers will love that!

As you wish, mish!
Feel free to close the issue. :)
bye bye Davide
Il 01/12/2021 01:29, MishManners®™ ha scritto:

Can you please @ me when you've got the next big version of this.
Would love to feature it but we have too many others with major
changes that were done in November. I would especially love to release
it when you have the macOS version available since a lot of our
readers will love that!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/release-radar/issues/2#issuecomment-983156916,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEA4MZT4QA66WRWWP3E3TLUOVT7NANCNFSM5IBL4CQA.

This was included in our November Release Radar 🎉 congrats


Porcupine Issue: Exception thrown: Initialization failed. Use the Java demo on windows

My code:
accessKey = "ex***************************************=";
modelPath = "G:\\Downloads\\porcupine_params_ja.pv";
keywordPaths = new String[] {"C:\\Users\\SpCo\\Desktop\\bot\\key\\key.ppn"};
Log:
[INFO] Porcupine model path : 'G:\Downloads\porcupine_params_ja.pv'
[INFO] Porcupine keyword path [0] : 'C:\Users\SpCo\Desktop\bot\key\key.ppn'
[INFO] Porcupine sensitivity [0] : 0.50
[ERROR] loading keyword file at 'C:\Users\SpCo\Desktop\bot\key\key.ppn' failed with 'INVALID_ARGUMENT'
Please help, thank you very much

Can you show the rest of the initialization code? What is the language of PPN file?

你能展示其余的初始化代码吗？ 是什么语言 PPN文件？

is Japanese

Can you show the rest of the initialization code? What is the language of PPN file?

I used the demo on github, only modified the variables
public static void main(String[] args) {
    Options options = BuildCommandLineOptions();
    CommandLineParser parser = new DefaultParser();
    HelpFormatter formatter = new HelpFormatter();

    CommandLine cmd;
    try {
        cmd = parser.parse(options, args);
    } catch (ParseException e) {
        System.out.println(e.getMessage());
        formatter.printHelp("porcupinemicdemo", options);
        System.exit(1);
        return;
    }

    if (cmd.hasOption("help")) {
        formatter.printHelp("porcupinemicdemo", options);
        return;
    }

    if (cmd.hasOption("show_audio_devices")) {
        showAudioDevices();
        return;
    }

    String accessKey = cmd.getOptionValue("access_key");
    String libraryPath = cmd.getOptionValue("library_path");
    String modelPath = cmd.getOptionValue("model_path");
    String[] keywords = cmd.getOptionValues("keywords");
    String[] keywordPaths = cmd.getOptionValues("keyword_paths");
    String[] sensitivitiesStr = cmd.getOptionValues("sensitivities");
    String audioDeviceIndexStr = cmd.getOptionValue("audio_device_index");
    String outputPath = cmd.getOptionValue("output_path");

    accessKey = "exkQvA==";
    modelPath = "G:\\Downloads\\porcupine_params_ja.pv";
    //keywords = new String[] {"趙かれい"};
    keywordPaths = new String[] {"C:\\Users\\SpCo\\Desktop\\bot\\key\\key.ppn"};

    if (accessKey == null || accessKey.length() == 0) {
        throw new IllegalArgumentException("AccessKey is required for Porcupine.");
    }

    // parse sensitivity array
    float[] sensitivities = null;
    if (sensitivitiesStr != null) {
        sensitivities = new float[sensitivitiesStr.length];

        for (int i = 0; i < sensitivitiesStr.length; i++) {
            float sensitivity;
            try {
                sensitivity = Float.parseFloat(sensitivitiesStr[i]);
            } catch (Exception e) {
                throw new IllegalArgumentException("Failed to parse sensitivity value. " +
                        "Must be a decimal value between [0,1].");
            }

            if (sensitivity < 0 || sensitivity > 1) {
                throw new IllegalArgumentException(String.format("Failed to parse sensitivity value (%s). " +
                        "Must be a decimal value between [0,1].", sensitivitiesStr[i]));
            }
            sensitivities[i] = sensitivity;
        }
    }

    if (libraryPath == null) {
        libraryPath = Porcupine.LIBRARY_PATH;
    }

    if (modelPath == null) {
        modelPath = Porcupine.MODEL_PATH;
    }

    if (keywordPaths == null || keywordPaths.length == 0) {
        if (keywords == null || keywords.length == 0) {
            throw new IllegalArgumentException("Either '--keywords' or '--keyword_paths' must be set.");
        }

        keywordPaths = new String[keywords.length];
        for (int i = 0; i < keywords.length; i++) {
            final String keyword = keywords[i].toUpperCase().replace(" ", "_");
            try {
                final Porcupine.BuiltInKeyword builtInKeyword = Porcupine.BuiltInKeyword.valueOf(keyword);
                keywordPaths[i] = Porcupine.BUILT_IN_KEYWORD_PATHS.get(builtInKeyword);
            } catch (Exception e) {
                throw new IllegalArgumentException(String.format("'%s' not a built-in keyword", keyword));
            }
        }
    }

    if (sensitivities == null) {
        sensitivities = new float[keywordPaths.length];
        Arrays.fill(sensitivities, 0.5f);
    }

    if (sensitivities.length != keywordPaths.length) {
        throw new IllegalArgumentException(String.format("Number of keywords (%d) does " +
                "not match number of sensitivities (%d)", keywordPaths.length, sensitivities.length));
    }

    int audioDeviceIndex = -1;
    if (audioDeviceIndexStr != null) {
        try {
            audioDeviceIndex = Integer.parseInt(audioDeviceIndexStr);
            if (audioDeviceIndex < 0) {
                throw new IllegalArgumentException(String.format("Audio device index %s is not a " +
                        "valid positive integer.", audioDeviceIndexStr));
            }
        } catch (Exception e) {
            throw new IllegalArgumentException(String.format("Audio device index '%s' is not a " +
                    "valid positive integer.", audioDeviceIndexStr));
        }
    }

    runDemo(accessKey, libraryPath, modelPath, keywordPaths, sensitivities, audioDeviceIndex, outputPath);
}

Can you show the rest of the initialization code? What is the language of PPN file?

public static void runDemo(String accessKey, String libPath, String modelPath,
String[] keywordPaths, float[] sensitivities,
int audioDeviceIndex, String outputPath) {
    // create keywords from keyword_paths
    String[] keywords = new String[keywordPaths.length];
    for (int i = 0; i < keywordPaths.length; i++) {
        File keywordFile = new File(keywordPaths[i]);
        if (!keywordFile.exists())
            throw new IllegalArgumentException(String.format("Keyword file at '%s' " +
                    "does not exist", keywordPaths[i]));
        keywords[i] = keywordFile.getName().split("_")[0];
    }

    // for file output
    File outputFile = null;
    ByteArrayOutputStream outputStream = null;
    long totalBytesCaptured = 0;
    AudioFormat format = new AudioFormat(16000f, 16, 1, true, false);

    // get audio capture device
    DataLine.Info dataLineInfo = new DataLine.Info(TargetDataLine.class, format);
    TargetDataLine micDataLine;
    try {
        micDataLine = getAudioDevice(audioDeviceIndex, dataLineInfo);
        micDataLine.open(format);
    } catch (LineUnavailableException e) {
        System.err.println("Failed to get a valid capture device. Use --show_audio_devices to " +
                "show available capture devices and their indices");
        System.exit(1);
        return;
    }

    Porcupine porcupine = null;
    try {

        porcupine = new Porcupine.Builder()
                .setAccessKey(accessKey)
                .setLibraryPath(libPath)
                .setModelPath(modelPath)
                .setKeywordPaths(keywordPaths)
                .setSensitivities(sensitivities)
                .build();

        if (outputPath != null) {
            outputFile = new File(outputPath);
            outputStream = new ByteArrayOutputStream();
        }

        micDataLine.start();
        System.out.print("Listening for {");
        for (int i = 0; i < keywords.length; i++) {
            System.out.printf(" %s(%.02f)", keywords[i], sensitivities[i]);
        }
        System.out.print(" }\n");
        System.out.println("Press enter to stop recording...");

        // buffers for processing audio
        int frameLength = porcupine.getFrameLength();
        ByteBuffer captureBuffer = ByteBuffer.allocate(frameLength * 2);
        captureBuffer.order(ByteOrder.LITTLE_ENDIAN);
        short[] porcupineBuffer = new short[frameLength];

        int numBytesRead;
        while (System.in.available() == 0) {

            // read a buffer of audio
            numBytesRead = micDataLine.read(captureBuffer.array(), 0, captureBuffer.capacity());
            totalBytesCaptured += numBytesRead;

            // write to output if we're recording
            if (outputStream != null) {
                outputStream.write(captureBuffer.array(), 0, numBytesRead);
            }

            // don't pass to porcupine if we don't have a full buffer
            if (numBytesRead != frameLength * 2) {
                continue;
            }

            // copy into 16-bit buffer
            captureBuffer.asShortBuffer().get(porcupineBuffer);

            // process with porcupine
            int result = porcupine.process(porcupineBuffer);
            if (result >= 0) {
                System.out.printf("[%s] Detected '%s'\n",
                        LocalTime.now().format(DateTimeFormatter.ofPattern("HH:mm:ss")), keywords[result]);
            }
        }
    } catch (Exception e) {
        System.err.println(e.toString());
    } finally {
        if (outputStream != null && outputFile != null) {

            // need to transfer to input stream to write
            ByteArrayInputStream writeArray = new ByteArrayInputStream(outputStream.toByteArray());
            AudioInputStream writeStream = new AudioInputStream(writeArray, format, totalBytesCaptured / format.getFrameSize());

            try {
                AudioSystem.write(writeStream, AudioFileFormat.Type.WAVE, outputFile);
            } catch (IOException e) {
                System.err.printf("Failed to write audio to '%s'.\n", outputFile.getPath());
                e.printStackTrace();
            }
        }

        if (porcupine != null) {
            porcupine.delete();
        }
    }
}

I tried to reproduce the problem but I could not. is there a way for you to share the PPN file?

https://drive.google.com/file/d/1uLhfAfvbJgQwk9CaMFbsMpi-QVZs5Wqc/view?usp=share_link

I tried to reproduce the problem but I could not. is there a way for you to share the PPN file?

https://drive.google.com/file/d/1uLhfAfvbJgQwk9CaMFbsMpi-QVZs5Wqc/view?usp=share_link

Thanks @SpCoGov
I tried to reproduce with your PPN file and still cannot. I run the following from the command prompt following instructions and it works:
java -jar porcupine-mic-demo.jar -a ${ACCESS_KEY} -kp "C:\Users\picovoice\Downloads\key.ppn" -m ..\..\..\..\lib\common\porcupine_params_ja.pv

The demo works and I think there could be something wrong in how you modified the demo. I suggest you try the command line approach fist and then work backwards.

What JAVA SDK are you using? I am using temurin-17.0.5
then here is the mic-demo I built, I didn't modify anything, can you reproduce with this?
https://drive.google.com/file/d/11KBByuIQbMFEdTtz4i3NFZZ0mI2O0Nlj/view?usp=sharing

I'm using OpenJDK 15.0.2. Can you try to reproduce with it? I doubt SDK version is the issue here.

can you give me your "porcupine-mic-demo.jar" to try?
C:\Users\SpCo\Desktop\bot>"G:\JavaDevelop\jdks\corretto-15.0.2\bin\java.exe" -Dfile.encoding=UTF-8 -jar porcupine-mic-demo.jar -a exxxxxx= -kp "C:\Users\SpCo\Desktop\bot\key\key.ppn" -m C:\Users\SpCo\Desktop\bot\porcupine_params_ja.pv  [INFO] Porcupine model path : 'C:\Users\SpCo\Desktop\bot\porcupine_params_ja.pv'  [INFO] Porcupine keyword path [0] : 'C:\Users\SpCo\Desktop\bot\key\key.ppn'  [INFO] Porcupine sensitivity [0] : 0.50 [ERROR] loading keyword file at 'C:\Users\SpCo\Desktop\bot\key\key.ppn' failed with 'INVALID_ARGUMENT' ai.picovoice.porcupine.PorcupineInvalidArgumentException: Initialization failed.

I'm using OpenJDK 15.0.2. Can you try to reproduce with it? I doubt SDK version is the issue here.

it still doesn't work
can you give me your "porcupine-mic-demo.jar" to try?
C:\Users\SpCo\Desktop\bot>"G:\JavaDevelop\jdks\corretto-15.0.2\bin\java.exe" -Dfile.encoding=UTF-8 -jar porcupine-mic-demo.jar -a exxxxxx= -kp "C:\Users\SpCo\Desktop\bot\key\key.ppn" -m C:\Users\SpCo\Desktop\bot\porcupine_params_ja.pv [INFO] Porcupine model path : 'C:\Users\SpCo\Desktop\bot\porcupine_params_ja.pv' [INFO] Porcupine keyword path [0] : 'C:\Users\SpCo\Desktop\bot\key\key.ppn' [INFO] Porcupine sensitivity [0] : 0.50 [ERROR] loading keyword file at 'C:\Users\SpCo\Desktop\bot\key\key.ppn' failed with 'INVALID_ARGUMENT' ai.picovoice.porcupine.PorcupineInvalidArgumentException: Initialization failed.

I'm using OpenJDK 15.0.2. Can you try to reproduce with it? I doubt SDK version is the issue here.

I tested French, German and English and they all work fine. Only Japanese throws exception: ai.picovoice.porcupine.PorcupineInvalidArgumentException: Initialization failed.

Can you show the rest of the initialization code? What is the language of PPN file?

I tried it with python and it works fine. It seems that only java has this problem

Did you get a chance to try OpenJDK 15.0.2? If you can, then the result will shed more light

Did you get a chance to try OpenJDK 15.0.2? If you can, then the result will shed more light

����: �������� ai.picovoice.porcupinedemo.MicDemo ʱ���� LinkageError
java.lang.UnsupportedClassVersionError: ai/picovoice/porcupinedemo/MicDemo has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 59.0
Execution failed for task ':MicDemo.main()'.

Process 'command 'G:/JavaDevelop/azul-15.0.10/bin/java.exe'' finished with non-zero exit value 1

Did you get a chance to try OpenJDK 15.0.2? If you can, then the result will shed more light

This is my log with jdk15.0.2
ai.picovoice.porcupine.PorcupineInvalidArgumentException: Initialization failed.
[INFO] Porcupine model path : 'G:\Downloads\porcupine_params_ja.pv'
[INFO] Porcupine keyword path [0] : 'C:\Users\SpCo\Desktop\bot\key.ppn'
[INFO] Porcupine sensitivity [0] : 0.50
[ERROR] loading keyword file at 'C:\Users\SpCo\Desktop\bot\key.ppn' failed with 'INVALID_ARGUMENT'

OK. What is the version of Windows you are using? I am trying to make all parameters the same so I can reproduce your issue. If you can think of any other special setting please let me know.

Windows 11 Professiona Insider Preview 22H2 25284.1000


Add plugin for VAL Parser tool from King's College London.

Fixes #5.

Codecov Report

Merging #15 (d214fc6) into main (a432988) will decrease coverage by 15.68%.
The diff coverage is 79.03%.

@@             Coverage Diff              @@
##              main      #15       +/-   ##
============================================
- Coverage   100.00%   84.31%   -15.69%
============================================
  Files            1        3        +2
  Lines           36      153      +117
============================================
+ Hits            36      129       +93
- Misses           0       24       +24

Impacted Files
Coverage Δ

..._planning/plugins/tool/val_validate_tool_plugin.py
79.31% <66.66%> (ø)

...ck_planning/plugins/tool/val_parser_tool_plugin.py
79.66% <79.66%> (ø)

Continue to review full report at Codecov.

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


Jordanjones243/css imports

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #8
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Update references to unformatted style links
Update demo page references

Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

We need to talk about this update. This feature was supported and I am not sure why we are deleting code?

The unformatted feature is still supported and the examples still work as expected. There was no need for the link to the stylesheet in the example files anymore because we already had style-unformatted.css being imported into the component's JS file.

:tada: This PR is included in version 1.0.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[5.7] Add optionalRequirementOf builder

Cherry pick of #280 for swift-5.7 release.
Rationale: Swift-Docc currently does not deal with optionalRequirementOf for edge-kind.
Risk: Low
Risk Detail: Add optionalRequirementOf builder.
Reward: Medium
Reward Details: Fix a known bug about optional protocol requirement in swift-5.7 toolchain.
Original PR: #280
Code Reviewed By:@franklinsch
Testing Details: Add unit test to test isRequired property when building optionalRequirementOf builder.

@swift-ci please test


Combine with datadog

Hi there,
we would like to integrate the lambda-adapter with a datadog agent.
According to their docs (https://docs.datadoghq.com/serverless/aws_lambda/installation/nodejs/?tab=containerimage) we have to set the DD_LAMBDA_HANDLER env-var to the original handler.
When using the lambda-adapter, there is no real handler, can you give guidance on what to do in this case?

I'm converting this into a discussion.


test turn on all test in scalar function w

Proposed changes
Issue Number: close #xxx
Problem summary

turn on all test case in scalar function W
turn off all test case for group_concat(distinct order by)
fix width_bucket function bug
fix return nullable in TimestampArithmetic

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.52 seconds
stream load tsv:          477 seconds loaded<PHONE_NUMBER>9 Bytes, about 149 MB/s
stream load json:         38 seconds loaded<PHONE_NUMBER> Bytes, about 59 MB/s
stream load orc:          67 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230303043315_clickbench_pr_107753.html

run buildall

run buildall


fix: changed package to scoped (again)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Does not work with ESP-IDF 5.2

It is bumping heads with all kinds of things in the IDF and even more if I use posix compatibility for lwip

Hi @kdschlosser,
Thank you for reaching out to us. We appreciate your interest in our services.
If you don't mind, could you please provide some context as to why you're looking to use this specific library with ESP-IDF? I ask because, according to the official Espressif documentation, ESP-IDF already provides POSIX APIs.
Thank you.

The POSIX api's are only available when compiling under linux. it doesn't provide the API's when compiling for an ESP32, Nothing that is complete anyhow...
In my use case I am wanting to use a library that is written to run on linux. It has a dependency on pthreads and sockets. The ESP-IDF uses lwip to handle the IP stack and socket connections and lwip has compat headers for linux which satisfy the linux socket dependency. the last part is pthread and what the IDF has included in terms of compatibility to linux is not complete enough to satisfy the dependency where this library does provide everything that is needed.

There's a possibility we may not have accounted for all the pthread APIs in our current implementation for various reasons. To address this, we would greatly value your assistance in compiling a complete list of the pthread APIs you're working with or expecting to use.
Apart from that, if you or any other contributors have developed code related to this project, particularly implementations of pthread APIs, we would be delighted to review and potentially incorporate your work. Your expertise and unique perspectives can significantly enhance the quality and functionality of our project.
Thank you.

The problem is not so much missing portions of the API as it is the bumping of heads with portions of the API that are supplied by the ESP-IDF. The issue is the ESP-IDF doesn't supply enough of the API and that is where this library helps to fill in the blanks. Not to throw another twist into it the xtensa gcc compiler also provides a subset of glibc and that is causing some problems as well. I was able to sort out most of the issues by creating macros for missing types and things of that nature. After spending several days of hair pulling it finally compiled. whether or not it will actually run is a whole other animal and I have not gotten into yet as I still need to write the code to stitch everything together. It is a complex combination of the LVGL graphics framework, MicroPython and libvncserver running on an ESP32 MCU. Not an easy task to get the various pieces to not throw sand at each other while playing in the sand box, if you get my meaning.
The ultimate goal of what I am doing is to create a way for users to build devices and write software for small devices with attached displays. The VNC (RFB Protocol) portion is to be able to develop and run the software on the MCU without having a display attached. More times than I can count I have developed something for a display only to end up changing the design because the display was to large or to small. This is a good way for a user to start developing without needing to have the initial investment of buying display hardware. It also provides a mechanism for providing support for production devices. Lots of companies are using MCU's to automate all kinds of things and support persons being able to connect to the device and see exactly what the user is seeing would be a fantastic feature to have available.

Thank you for your detailed response. We appreciate the context you've provided. However, to better assist you, we'd need a more specific list of the components or features from this repository that you're trying to implement. Could you kindly outline these for us? This would help us provide more targeted support.
Thank you for your cooperation.


fix: comment typos

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thankyou for the contribution! You will also want to run pnpm changeset and commit an empty changeset to pass CI 🙂

You will also want to run pnpm changeset and commit an empty changeset to pass CI 🙂

The full command below — then add/commit/push the generated changeset and voilà.
pnpm changeset add --empty

@danielbate @arboleya
I think I have run: pnpm changeset add --empty.
Please help me to review again. Thank you very much.


Chapter policy reference is not up to date

Hi, I'm looking for assignment parameter names to disable particular ASC policies (like DDOS standard SKU for instance). This reference provides only small part of existing policies/parameters. Googling gives some old github commits from 01/2019, so I'm curious where I could find the complete list of them

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

ID: edaa802f-1ab4-e657-e604-3274d3333818
Version Independent ID: bc573f7b-0989-1471-889f-6d96bb32ff57
Content: Create and edit Azure Policy security policies using the REST API
Content Source: articles/security-center/configure-security-policy-azure-policy.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@svsvirid Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

Thanks for the feedback.
The instructions for disabling policies are here: https://docs.microsoft.com/en-us/azure/security-center/tutorial-security-policy#disable-security-policies
The full list of policies is here: https://docs.microsoft.com/en-us/azure/security-center/security-center-policy-definitions
Hopefully, that will help you solve this issue.
Thanks again! I'm closing this as an open issue for now, but feel free to continue to comment here as necessary.
We appreciate your contribution to our community.
#please-close

Hi,
It's a pity it's closed. Unfortunately the links above don't provide any reference on how to disable it in automatic way, with powershell for example. And for this, you need so called Policy Assignment parameter for every policy, which is not seen anywhere in policy reference list you've provided, also not in GitHub links. So MS documentation does not provide enough information on this matter.
Luckily in the meanwhile I've found a way to workaround it and get parameter names I was looking for. If I change Initiative Assignment parameters manually in the portal, Save and then retrieve policy assignment via PowerShell, I can see parameter names of the items recently changed:
$PolicyAssignment = Get-AzPolicyAssignment -Id xxx
$PolicyAssignment.Properties.parameters
output would be like this:
jitNetworkAccessMonitoringEffect                                   : @{value=Disabled}
vnetEnableDDoSProtectionMonitoringEffect                   : @{value=Disabled}
So I'd assume that using this way is more sustainable to mention in documentation than providing an old incomplete list of policies/parameters in the subject documentation page.
I'll leave it up to MS though.
Regards,
Svetlana


RFP - kde-firelight

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://utils.kde.org/projects/filelight/
Direct download URL for the software / installer : It is supposed to be Open source BUT https://www.microsoft.com/en-us/p/filelight/9pfxcd722m2c
Software summary / short description: A folder size checker and disk usage analyzer
Ooof https://github.com/KDE/filelight/releases

As this is a Windows Store only package, and AFAIK it is not possible to install the application outside of Windows Store when you do not have the application file.
As such I will, unfortunately, be closing this issue, we can always re-open the issue if the situation changes.


broken in new node.js

this depends on node-waf but it's deprecated in the node-0.10+
http://stackoverflow.com/questions/15024421/node-js-centos-node-waf/15979279#15979279

Seems to be solved via the upgrade to<EMAIL_ADDRESS>

Thanks @jpbriend
Closing this issue.


[bug] re-filed from old repository: Request queue was disposed

Describe the bug
original issue: https://github.com/mirromutth/r2dbc-mysql/issues/241
Hi, there was this bug in the old implementation where a connection would hang for hours, stopping the thread, and then throw this error:
java.lang.IllegalStateException: Request queue was disposed
at dev.miku.r2dbc.mysql.client.RequestQueue.requireDisposed(RequestQueue.java:150)
  at dev.miku.r2dbc.mysql.client.RequestQueue.dispose(RequestQueue.java:139)
  at dev.miku.r2dbc.mysql.client.MessageDuplexCodec.channelInactive(MessageDuplexCodec.java:131)
  at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
  at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
  at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
  at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:389)
  at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:354)
  at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
  at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)

To Reproduce
Steps to reproduce the behavior:
I'm not sure what triggers this bug 😢 but there were multiple reports on the original issue

could you confirm if this issue was handled when catching up to r2dbc 1.0.0?
Also, thanks a lot for taking over maintainership of this project and supporting r2dbc 1.0.0 🙇♂

Thanks @mscheong01  for reporting the issue.
We will look into it.

Hello, @mscheong01.
We've attempted to reproduce the issue you reported, but unfortunately, we were unable to do so. In order to help us better understand and address the problem, could you please provide a minimal (though not necessarily minimal) reproducible example along with relevant environment information? Details such as whether you are using r2dbc-pool, specific configurations, the Spring version, and any other pertinent information would be extremely helpful for us to identify the cause of the problem.
Thanks!

cant' repro

if there were an issue, it is expected to be resolved by #119.


improved pretty printing

this fixes an issue where we want this:
pkgs:
  something:
    src:
      github:
        repo: some_repo
        user: matt

but I'm seeing (and this fails if I try to parse the file):
pkgs:something:
    src:
      github:
        repo: some_repo
        user: matt

The other thing this does is line delimit arrays instead of comma delimit them, it makes it far easier to read if there's more than three items, hopefully this is ok with you?

Yeah, this looks great.  Condensing the lines isn't such a big deal when pretty printing.

Yeah, this looks great.  Condensing the lines isn't such a big deal when pretty printing.


Bots, Bots and More Bots

I've been going through a lot of repositories lately. Quite a few of them had services enabled that made their contributors lives easier. Would any of these work for us?

HoundCI Uses the code review process to make sure that we could fix issues in the bud. Could eliminate the need for Travis and Grunt.

Greenkeeper Checks the dependencies periodically and makes sure that they are up to date, and makes issues if they aren't.

Backstroke Checks that your fork is synced with the upstream, and makes a pull request if it isn't. Takes the headdesk out of updating forks. It should get rid of the semi-frequent merge conflicts we get.

Any comment, @MichMich and @paviro?

Also, @MichMich, I know that I already suggested Backstroke, but I think it's better now.


Add Accountant's as BCC on "thank you" emails

This is the last part to complete the https://github.com/opencollective/opencollective/issues/3112 plan, now that we have https://github.com/opencollective/opencollective/issues/2867 it should be fairly simple: we need to put accountants as BCC in thank you emails.

Do you have a plan to tackle this in the near future?

@Piedone We haven't found the time to prioritize it yet, but that's definitely something we want to do. I understand that it's annoying for your use case to not have this feature completed, I'll try to take care of it as soon as possible.

Thanks for the update!

Do we have to configure anything for this, or how will this work?

Hi @Piedone, I was about to post a comment here since we just deployed the change. People added as "Accountants" in your settings should now receive all the emails with PDF receipts.

Great, thank you!


No point cloud showed in the web viewer

Here is the screenshot. Do anyone know why I can't get point cloud showed in it? And the eval bbox seems not right also...

do you solve this error?


kube-lego deployed on GKE uses both NGINX and GLBC ingress controllers

When the kube-lego ingress is created, it uses both nginx-ingress-controller and loadbalancer-controller:
Name:                   kube-lego
Namespace:              default
Address:                <IP_ADDRESS>,<IP_ADDRESS>
Default backend:        default-http-backend:80 (<IP_ADDRESS>:8080)
Rules:
  Host                  Path    Backends
  ----                  ----    --------
  echo.example.com
                        /.well-known/acme-challenge     kube-lego:8080 (<none>)
Annotations:
  backends:             {"k8s-be-31590--64893abc10ca8449":"HEALTHY"}
  forwarding-rule:      k8s-fw-default-kube-lego--64893abc10ca8449
  ssl-redirect:         false
  target-proxy:         k8s-tp-default-kube-lego--64893abc10ca8449
  url-map:              k8s-um-default-kube-lego--64893abc10ca8449
Events:
  FirstSeen     LastSeen        Count   From                            SubobjectPath   Type            Reason  Message
  ---------     --------        -----   ----                            -------------   --------        ------  -------
  8m            8m              1       {nginx-ingress-controller }                     Normal          CREATE  default/kube-lego
  8m            8m              1       {loadbalancer-controller }                      Normal          ADD     default/kube-lego
  8m            7m              2       {nginx-ingress-controller }                     Normal          CREATE  ip: <IP_ADDRESS>
  7m            7m              1       {loadbalancer-controller }                      Normal          CREATE  ip: <IP_ADDRESS>
  7m            7m              1       {loadbalancer-controller }                      Warning         Status  Operation cannot be fulfilled on ingresses.extensions "kube-lego": the object has been modified; please apply your changes to the latest version and try again
  8m            2m              7       {nginx-ingress-controller }                     Normal          UPDATE  default/kube-lego

Probably it should be created with annotation kubernetes.io/ingress.class: "nginx" to disable GLBC.

Plan to do that as part of #11. This annotations haven't been around for too long. Should happen within the next week :+1:

What is about a simplification of the kube-lego setup?
One proposal:

Use a NodePort for the kube-lego service. AFAIK ports.type: NodePort is already necessary of service ports receiving ingress traffic (atleast on GKE)?
Manually (or automatically?) patch a referenced ingress resource (via env) to redirect /.well-known/acme-challenge to the kube-lego service.

I tried to change the configurations according to this, but the currently problem is, that kube-lego seems to stop after:
time="2016-08-04T00:26:59Z" level=fatal msg="Error while process certificate requests: reachabily test failed for this cert" context=kubelego

It restarts after a while, but not fast enough for the GKE health-check to recognize the service as healthy. So the ingress controller does not send any traffic to the service. Whats about to keep kube-lego up and running and always receiving traffic on / or /healthz?

Okay got it working with GKE as a proof of concept.
My steps:

kube-lego-deployment.yaml: Add a livenessProbe, so GKE can adopt this lifenessProbe for the health check for the backend-service
kube-lego-svc.yaml: Set ports.type: NodePort
kube-lego-configmap.yaml: Customize to your needs
kubectl apply -f kube-lego-configmap.yaml -f kube-lego-deployment.yaml -f kube-lego-svc.yaml
Change your ingress controller to redirect /.well-known/acme-challenge/ to the kube-lego service. DO NOT set annotations.kubernetes.io/tls-acme: "true" in the ingress for now! (Reason: [1])
Wait until the health check for kube-lego is HEALTHY (watch kubectl describe ing)
Test manually if everything is redirected to your endpoints, especially to kube-lego: curl -i http://example.com/.well-known/acme-challenge/_selftest should be status 200.
kubectl annotate ing your-ingress-name kubernetes.io/tls-acme="true"
Inspect the logs of the kube-lego pod and the secrets, hopefully it installed the desired secret and the GKE LoadBalancer installed it for SSL.

My examples as a Gist: https://gist.github.com/MaxDaten/482f6bd71348b1502edc7348318bea17
[1] You should not set annotations.kubernetes.io/tls-acme: "true" before health check for the backend-service is HEALTHY, because kube-lego immediately starts with the selfcheck, but no traffic on /.well-known/acme-challenge is redirected to it, as long the health check fails. This seems to result into a kind of deadlock.

@MaxDaten thanks for your input on that. First of all I am not too sure if you are aware that there is a simple setup based on using nginx-ingress on GKE/GCE like this is:

Disable L7-Loadbalancing in GKE: gcloud container clusters update <cluster-name> --update-addons HttpLoadBalancing=DISABLED
Run nginx-ingress like described in the examples

I am using this for months without any issue.
For having GCE ingress support, we need to support differentiation between ingress-classes. I plan to implement that for this ticket. This will include a lot of your (steps).
I agree on the deadlock, the reason for that is that kube-lego is currently not disabling ingress resources if they fail a couple of times, this is probably not trivial to implement. (see #13)

First of all I am not too sure if you are aware that there is a simple setup based on using nginx-ingress on GKE/GCE like this is:

Yes I'm aware of it, but wasn't aware how to disable the L7-LB, thanks for the hint. But this has the downside (depends on your perspective) to manage the LB on your own and you have to pull it into your cluster, since the L7 resides now on the managed master. Currently I prefer the managed LB. because I'm the one man army here.

GCE should be supported as of release 0.1.0. Look at the examples

Thanks alot, I will definitely try it out!

Just stopping by to say thank you. I installed it, and it works like a charm =)


You are running the esm-bundler build of vue-i18n

How to get rid of this error?
You are running the esm-bundler build of vue-i18n. It is recommended to configure your bundler to explicitly replace feature flag globals with boolean literals to get proper tree-shaking in the final bundle.

I'm seeing this as well, but only during development mode. The production build does seem to work fine.
Also I wanted to add that the message is received in the browser console.

I'm also seeing this error on the console.warn


(JS-0242) Use const declarations for variables that are never reassigned

Description
Variables that are not re-assigned are referred to as constant variables. So, we recommend using const for such variables instead of let to define because the value of a variable declared with const remains the same within its scope. It cannot be updated or re-declared and also reduces cognitive load …
Occurrences
There are 6 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/real2two/twochat-server/issue/JS-0242/occurrences/

what how does this program work


Feature Request: support computed property (such as enum value) as property key

Feature description
If the key of a property is not a literal, original behavior is it will be ignored.
It would be nice to support computed property key (such as constants and enum values)
I did found a quick way to work by modifying the source code:
// src/core/generateZodSchema.ts:190
    if (
      !ts.isPropertySignature(member) ||
      !member.type ||
      !(
        ts.isIdentifier(member.name) ||
        ts.isStringLiteral(member.name) ||
-       ts.isNumericLiteral(member.name)
+       ts.isNumericLiteral(member.name) ||
+       ts.isComputedPropertyName(member.name)
      )
    ) {
      return;
    }

But there might be edge cases I haven't thought of.
Input
export enum COL {
  MODEL = 'T0000'
}

export type Car = {
  [COL.MODEL]: string
}

Original Output
// Generated by ts-to-zod
import { z } from 'zod'
import { COL } from 'src/col'

export const colSchema = z.nativeEnum(COL)

export const carSchema = z.object({})

Desired Output
// Generated by ts-to-zod
import { z } from 'zod'
import { COL } from 'src/col'

export const colSchema = z.nativeEnum(COL)

export const carSchema = z.object({
  [COL.MODEL]: z.string(),
})

Ah I think it should check if computed property evaluates into string constant


Removes debug assertion that was related to issue 796

I don't think #796 is what you mean?
And I think this might effectively be a duplicate of https://github.com/bytecodealliance/wasmtime/pull/5553?
In any case, we don't want to simply remove assertions, we want to fix the underlying reason the assertion is failing. Therefore, we won't want to merge this PR in its current state.

It is issue 796 on the old cranelift repo before cranelift was merged into the wasmtime repo.

Happy to close, though maybe it's better to update the issue number on the PR?


Why '-DSTATIC_LINKING:BOOL=ON' not work for build static 'bpftrace'?

I use the follow command to build 'bpftrace'
# export CC=clang-7
# export CXX=clang++-7
# mkdir -p build && cd build
# cmake -DCMAKE_BUILD_TYPE=Release -DSTATIC_LINKING:BOOL=ON ..
# make -j4

After build success, I use 'ldd' to check the binnary and it hasn't been linked as static:
root@localhost:/data/local/bpftrace/build# ldd ./src/bpftrace
        linux-vdso.so.1 (0x0000007db523f000)
        libclang-7.so.1 => /lib/aarch64-linux-gnu/libclang-7.so.1 (0x0000007db3d1b000)
        libLLVM-7.so.1 => /lib/aarch64-linux-gnu/libLLVM-7.so.1 (0x0000007db096e000)
        libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000007db095a000)
        libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000007db092b000)
        libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000007db07a0000)
        libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000007db06e3000)
        libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000007db06bd000)
        libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007db054b000)
        libffi.so.6 => /lib/aarch64-linux-gnu/libffi.so.6 (0x0000007db0533000)
        libedit.so.2 => /lib/aarch64-linux-gnu/libedit.so.2 (0x0000007db04ed000)
        libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x0000007db04c0000)
        librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1 (0x0000007db04a8000)
        libtinfo.so.6 => /lib/aarch64-linux-gnu/libtinfo.so.6 (0x0000007db0468000)
        /lib/ld-linux-aarch64.so.1 (0x0000007db5211000)
        libbsd.so.0 => /lib/aarch64-linux-gnu/libbsd.so.0 (0x0000007db0442000)

Can you try again with   -DSTATIC_LIBC=ON -DSTATIC_LINKING=ON and attach the cmake output to this ticket?

Thanks so much for your response. After I switch to the below compile command
 cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_LIBC=ON -DSTATIC_LINKING:BOOL=ON ..

I got the below error, any why to check the detailed failed reason? Thanks in advance:
/usr/bin/ld: cannot find -lclang
/usr/bin/ld: cannot find -lclang
/usr/bin/ld/usr/bin/ld: : /usr/local/lib/libbfd.a(plugin.o)/usr/local/lib/libbfd.a(plugin.o): in function `: in function `try_load_plugintry_load_plugin':
':
/data/local/utils/binutils-2.36/build/bfd/../../bfd/plugin.c:/data/local/utils/binutils-2.36/build/bfd/../../bfd/plugin.c:274274: : warning: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linkingUsing 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

/usr/bin/ld: /usr/lib/llvm-7/lib/libLLVMSupport.a(Path.cpp.o): in function `llvm::sys::fs::real_path(llvm::Twine const&, llvm::SmallVectorImpl<char>&, bool)':
(.text._ZN4llvm3sys2fs9real_pathERKNS_5TwineERNS_15SmallVectorImplIcEEb+0x270): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /usr/lib/llvm-7/lib/libLLVMSupport.a(Path.cpp.o): in function `llvm::sys::path::home_directory(llvm::SmallVectorImpl<char>&)':
(.text._ZN4llvm3sys4path14home_directoryERNS_15SmallVectorImplIcEE+0x9c): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: gtest-git-prefix/src/gtest-git-build/googlemock/gtest/libgtest.a(gtest-all.cc.o): in function `testing::internal::StreamingListener::SocketWriter::MakeConnection()':
gtest-all.cc:(.text+0x17e7c): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /usr/lib/llvm-7/lib/libLLVMSupport.a(Path.cpp.o): in function `llvm::sys::fs::real_path(llvm::Twine const&, llvm::SmallVectorImpl<char>&, bool)':
(.text._ZN4llvm3sys2fs9real_pathERKNS_5TwineERNS_15SmallVectorImplIcEEb+0x270): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /usr/lib/llvm-7/lib/libLLVMSupport.a(Path.cpp.o): in function `llvm::sys::path::home_directory(llvm::SmallVectorImpl<char>&)':
(.text._ZN4llvm3sys4path14home_directoryERNS_15SmallVectorImplIcEE+0x9c): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
clang: error: linker command failed with exit code 1 (use -v to see invocation)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [tests/CMakeFiles/bpftrace_test.dir/build.make:932: tests/bpftrace_test] Error 1
make[2]: *** [src/CMakeFiles/bpftrace.dir/build.make:615: src/bpftrace] Error 1
make[1]: *** [CMakeFiles/Makefile2:1202: src/CMakeFiles/bpftrace.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:1600: tests/CMakeFiles/bpftrace_test.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

I've installed the follow package:

clang/stable,now 1:7.0-47 arm64 [installed]
  C, C++ and Objective-C compiler (LLVM based)

clang-7/stable,now 1:7.0.1-8+deb10u2 arm64 [installed]
  C, C++ and Objective-C compiler

libclang-6.0-dev/stable,now 1:6.0.1-10 arm64 [installed]
  clang library - Development package

libclang-7-dev/stable,now 1:7.0.1-8+deb10u2 arm64 [installed]
  Clang library - Development package

libclang-common-6.0-dev/stable,now 1:6.0.1-10 arm64 [installed,automatic]
  clang library - Common development package

libclang-common-7-dev/stable,now 1:7.0.1-8+deb10u2 arm64 [installed]
  Clang library - Common development package

libclang-dev/stable,now 1:7.0-47 arm64 [installed]
  clang library - Development package

libclang1-6.0/stable,now 1:6.0.1-10 arm64 [installed,automatic]
  C interface to the clang library

libclang1-7/stable,now 1:7.0.1-8+deb10u2 arm64 [installed]
  C interface to the Clang library

Sounds like you're missing one or more static libraries. You're probably looking for something like llvm-static, clang-static.
Are you sure you want a static build? You might be able to take the one we build with our ci and ship to quay.io (see install.md) or take some inspiration from the ci

Thanks for your update. It seems the binary from quay.io needs the 'glibc 2.27'.
I want to run bpftrace on Android device, that's why I'm trying to build static binary.

I've made it by re-compiling the LLVM & Clang. Thanks so much.


Simple test fails with 'TypeError: You may only yield a function...'

I'm hitting a problem in my tests and I can get the same thing with the simplest of tests.  Using the file simple.js containing:
it('should do something', function* () {
  yield;
});

When I run:
node node_modules/mocha/bin/mocha --require co-mocha simple.js

I get
  1)  should do something:
     TypeError: You may only yield a function, promise, generator, array, or object, but the following object was passed: "undefined"
      at next (/Users/p14n/dev/tools/moch/node_modules/co-mocha/node_modules/co/index.js:100:25)

co-mocha 1.1.0
mocha 2.0.1
node 1.6.4
I can't see why that wouldn't work?
Cheers

@p14n Looks like someone has asked about it a while ago on the co repo (https://github.com/tj/co/issues/119). Does that help you?

Yes thanks (it's not expected to work).  Returning an array there works fine.


Add files via upload

Hi
This is my first pull request with a simple project.
Related to > Area of Triangle #372
Why:
Closes [issue link]
What's being changed:
Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Hey @Glogius95
Thanks for contributing to this open source project 😃
This PR will be reviewed and merged shortly

https://codinasion.web.app/programme/area-of-triangle/


General improvments

This adds some general improvements and three bug fixes, I saw when implementing #261
Bugs:

The meson version wasn't detected correctly, since the g flag was used in the regex for the version number, so the resulting match array was ["1.6.0"] instead of ["1.6.0","1","6","0"]
The version comparison was done manually in https://github.com/mesonbuild/vscode-meson/pull/268/commits/5e9c9e961e8195dcc7276686775a2ae8e8e4abfe#diff-9a3b5396b880a25586663b03f9bda56906914991b7b43b493283eca3ccc74fc3R28 and there we only checked version[1] < 50, which only worked correctly before 1.0.0 (thsi never showed, since after this check we additionally check, if the returned filename is an array or not, so this only cleans this up)
The slicing of the version for meson was done incorrectly, ["1.6.0","1","6","0"].slice(1,.3) results in ["1","6"] and not in three components

Improvements:

add Version class, that handles:

comparison, so that we don't make obvious errors and so that it's much simpler
toString function, so that it can be easily printed
check at runtime, if the input is correct, this can help detect feature  errors easier, if e.g. muon changes it's version string, that we parse, so that we get a nice and early error (this also helped my find bug 3)

Most of these things I "need" for #261 or at least it makes the life much more easy, (I print versions in some places, comparison is an improvement, that benefits also existing code)
Feel free to suggest any changes 😄

Looks good. Please squash at will, and I will merge!

Squashed it to 2 commits, which makes the most sense to me


Add toggle to move sidebar to left or right side

Within the feature settings you will be given the option to toggle the sidebar to either side of the client or move them (the sidebar options) up into the title bar.
This feature should also allow you to toggle the sidebar options so that it opens in a pop-out window.

How is this a "bad idea"? Just because something is "fine" doesn't mean options aren't good.

Here is my argument.  Note the red square - After clicking the wrench to open the sidebar, the wrench MOVES to the right, which requires moving the mouse to a different location to close the bar again.  It would be much more convenient if, through a setting, we could stick the sidebar to the left so the mouse does not have to move:

It would be much more convenient if the settings button stayed here:

Is there still no intention of adding this feature?

Why isn't this implemented yet???

Crazy how all duplicates lead here but the issues been closed for years. Still dropping by once a year to check if its gonna ever happen.

Having a standard layout in the client provides an easier option to support the client. Whether this is the intention of the developers, it's a good bit of unnecessary code to implement on a client that will be deprecated in the future, as well as a hassle to help unsavvy users navigate their runelite installation. I'm sure if anyone wanted to contribute this to the client the maintainers would be willing to review it and play ball, but it's not on their horizon and clearly hasn't been for the six years this issue has been open.

This is just bad idea, its fine as it is now on right side

I don't understand how this is a bad idea. Simply saying that comes off as it not having a purpose just because you wouldn't use it yourself. Would it really break things that much? I'm genuinely curious.

I would love this feature to be implemented for side-by-side clients with an alt. That way the plugin bar of the client on the left would not move over the client on the right side. The current setup would either have an open space between both clients or overlapping plugin bar when extended

That way the plugin bar of the client on the left would not move over the client on the right side.

You can use a profile with RuneLite -> Window Settings -> Resize Type set to "Keep window size" to do this already

You can use a profile with RuneLite -> Window Settings -> Resize Type set to "Keep window size" to do this already

Not ideal since it makes the game window smaller, but it works for now

I would love this feature to be implemented for side-by-side clients with an alt. That way the plugin bar of the client on the left would not move over the client on the right side. The current setup would either have an open space between both clients or overlapping plugin bar when extended

The game window appears to have a minimum size that it can be. Not sure if it's set by the Runescape client or RuneLite, but either way it's locked at 25% of the screen (50% of the width and 50% of the height). By having the 2 windows next to each other, you're already taking up the entire screen space with just the game on it's own. So the only way to have the RuneLite sidebar visible in addition to this is to have the windows overlap. You can hide the menu with the Plugin Panel Toggle Key (default: CTRL + F11), which should make it to where the windows don't overlap, but I'm guessing you want to keep it up so that probably isn't helpful. As far as I can tell, that seems to be the only option right now. I would suggest that you try to open a ticket for a quality of life / enhancement change though. Assuming it can be done, it's a bit beyond what I'm trying to do, which is just allowing the sidebar to be on the left side of the screen.

I would love this feature to be implemented for side-by-side clients with an alt. That way the plugin bar of the client on the left would not move over the client on the right side. The current setup would either have an open space between both clients or overlapping plugin bar when extended

The game window appears to have a minimum size that it can be. Not sure if it's set by the Runescape client or RuneLite, but either way it's locked at 25% of the screen (50% of the width and 50% of the height). By having the 2 windows next to each other, you're already taking up the entire screen width with just the game on it's own. So the only way to have the RuneLite sidebar visible in addition to this is to have the windows overlap. You can hide the sidebar with the Plugin Panel Toggle Key (default: CTRL + F11), which should make it to where the windows don't overlap, but I'm guessing you want to keep it up so that probably isn't helpful. As far as I can tell, that seems to be the only option right now. I would suggest that you try to open a ticket for a quality of life / enhancement change though. Assuming it can be done, it's a bit beyond what I'm trying to do, which is just allowing the sidebar to be on the left side of the screen.

I'm playing on a wide screen, so 50% width (and 50% height) minimum is definitely not true for all setups. I also know people who run multiple screens next to each other on a laptop, that I think are smaller than 50%. Having the sidebar on the left for me would be a good solution for 2 clients.

I'm playing on a wide screen, so 50% width (and 50% height) minimum is definitely not true for all setups. I also know people who run multiple screens next to each other on a laptop, that I think are smaller than 50%. Having the sidebar on the left for me would be a good solution for 2 clients.

Ah, okay, that makes sense. In that case, there would probably need to be an interaction added that allows windows to stick together when side by side, similar to how it snaps to the side of the screen. Could maybe even add a toggle for it in the config too (i.e. Multiwindow Snapping or something). Certainly a good idea, not too sure how to implement it though. I'm relatively new to coding java and most of what I've learned has been for this project.


B #5442: get DOMAIN_ID from the deployment file

and optimize domain UUID extraction with awk

Merged as per 1a041abb6fb6d36e7564453fdddf561abfa6b7c8
THANKS


image cannot be rendered in low memory android

all images rendering fine after a fresh start of app,
but the image cannot load properly after some navigation through views
is anyone encountering this problem same as me?

@notlose Do you have a sample app / code to reproduce the behavior?

@gvaish i can create a sample app later on,
i have exactly the same situation described here:
http://stackoverflow.com/questions/34655189/react-native-image-missing-after-reloading-js-several-times/34786001#34786001

Having the same issue. I've been doing some playing around and noticed that in the situation @notlose describes (having reloaded JS many times), the image's onLoad doesn't fire, but onLoadStart and onLoadEnd do. Not sure if this is cause or effect, though...
Restarting app does seem to temporarily cure, as pointed out.
Setup is rn 0.19.0 and: GenyMotion on Mac, or GalaxyTab S2. GenyMotion emulator is set to 2048mb base memory.

@laeijebor We are suffering from the same issue, we have a quite large number of images in a certain scene in the app and it happens many times that appear/disappear randomly, both static images and network images. Any progress on that from your side ?

I think I'm seeing the same thing, my images just show up blank a lot of times when many are on the same page. I'm not really sure how to go about starting to fix this however.

@Sh3rawi @9mm you can try to add android:largeHeap="true" in your android manifest application tag as a workaround, my app works better with this

@notlose Yep - that has been working for me for the last few days, too...

Same error since v0.19, I think. Happened on emulator and on galaxy s2. Also onLoadEnd doesn't provide any information about the error.

+1

+1

still happening on 0.25

@notlose what i did to fix this issue permanently is to copy the image component to a custom component but turn off hardware acceleration for it (view.setLayerType(View.LAYER_TYPE_SOFTWARE, null) in the setSource function in the CustomImageManager.java

i write app for android (i used large heap setting in manifestfile).
but Image  disapear when i exit and start app serve time.
Image will apear again if i exit app by recently app list.
seem like when exit app (by back button) , memories for app not released .

+1

same issue here

+1

+1

I'm experiencing this issue on lower end Android devices with<EMAIL_ADDRESS>

I'm having this problem on Android too. I have a parallax background formed by a few overlapping layers. They are png images as static resources.

Still having this issue on lower end Android devices with RN 0.41.

I'm having same probleme with RN 0.42 .

@Kottidev Hi, can you solve this problems on android ?

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

It's not fixed at all...


Issue when installing Surface_Dock_FwUpdate that was released on 9/18

I installed the new firmware updater for surface dock - no errors once i completed the installation.
Registry showing the following:
Component10CurrentFwVersion = 4ac3970
Component20CurrentFwVersion = 499a170
But it appears the installation is failing silently. Looking at the logs in setupapi.dev.log file under C:\Windows\INF, I am seeing the following:

[Device Install (DiInstallDriver) - C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf]
Section start 2019/09/21 01:12:13.222
cmd: "C:\WINDOWS\system32\pnputil.exe" -i -a "C:\Program Files\SurfaceUpdate\SurfaceDockIntegration\SurfaceDockIntegration.inf"
ndv: Flags: 0x00000000
ndv: INF path: C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf
inf: {SetupCopyOEMInf: C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf} 01:12:13.224
inf:      Copy style: 0x00000000
inf:      Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf
inf:      Published Inf Path: C:\WINDOWS\INF\oem39.inf
inf: {SetupCopyOEMInf exit (0x00000000)} 01:12:13.227
ndv: {Update Device Driver - HID\VID_045E&PID_0904&COL05\7&2C78944B&0&0004}
ndv:      Search options: 0x00000081
ndv:      Searching single INF 'C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf'
dvi:      {Build Driver List} 01:12:13.244
dvi:           Searching for hardware ID(s):
dvi:                hid\vid_045e&pid_0904&rev_7007&col05
dvi:                hid\vid_045e&pid_0904&col05
dvi:                hid\vid_045e&up:ff08_u:0060
dvi:                hid_device_up:ff08_u:0060
dvi:                hid_device_upr:ff00-ffff
dvi:                hid_device
dvi:           Created Driver Node:
dvi:                HardwareID   - HID\VID_045E&PID_0904&Col05
dvi:                InfName      - c:\windows\system32\driverstore\filerepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf
dvi:                DevDesc      - Surface Dock Integration
dvi:                Section      - SurfaceDockIntegration.NT
dvi:                Rank         - 0x00ff0001
dvi:                Signer Score - WHQL
dvi:                DrvDate      - 03/01/2017
dvi:                Version      - 2.0.303.0
dvi:      {Build Driver List - exit(0x00000000)} 01:12:13.261
ndv:      Searching currently installed INF
dvi:      {Build Driver List} 01:12:13.262
dvi:           Searching for hardware ID(s):
dvi:                hid\vid_045e&pid_0904&rev_7007&col05
dvi:                hid\vid_045e&pid_0904&col05
dvi:                hid\vid_045e&up:ff08_u:0060
dvi:                hid_device_up:ff08_u:0060
dvi:                hid_device_upr:ff00-ffff
dvi:                hid_device
dvi:           Created Driver Node:
dvi:                HardwareID   - HID\VID_045E&PID_0904&Col05
dvi:                InfName      - C:\WINDOWS\System32\DriverStore\FileRepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf
dvi:                DevDesc      - Surface Dock Integration
dvi:                Section      - SurfaceDockIntegration.NT
dvi:                Rank         - 0x00ff0001
dvi:                Signer Score - WHQL
dvi:                DrvDate      - 03/01/2017
dvi:                Version      - 2.0.303.0
dvi:      {Build Driver List - exit(0x00000000)} 01:12:13.275
dvi:      {DIF_SELECTBESTCOMPATDRV} 01:12:13.276
dvi:           Default installer: Enter 01:12:13.277
dvi:                {Select Best Driver}
dvi:                     Class GUID of device changed to: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
dvi:                     Selected Driver:
dvi:                          Description - Surface Dock Integration
dvi:                          InfFile     - c:\windows\system32\driverstore\filerepository\surfacedockintegration.inf_amd64_97a6bac9a2c2eb00\surfacedockintegration.inf
dvi:                          Section     - SurfaceDockIntegration
dvi:                {Select Best Driver - exit(0x00000000)}
dvi:           Default installer: Exit
dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 01:12:13.283
ndv:      Currently Installed Driver:
ndv:           Inf Name       - oem39.inf
ndv:           Driver Date    - 03/01/2017
ndv:           Driver Version - 2.0.303.0
ndv: {Update Device Driver - exit(00000103)}
<<<  Section end 2019/09/21 01:12:13.297
<<<  [Exit status: FAILURE(0x00000103)]

Application event logs showing 2 errors when I try to unplug/plug back the surface dock connector to my surface book:
The description for Event ID 2007 from source SurfaceDockFwUpdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
surfacedockfwupdate
Firmware update finished. hr=-2147418113 DriverTelementry EventCode = 2007

@officedocsbot assign @jvsam

Thank you for bringing this to our attention @madhoun. We believe this will be best addressed by contacting Support. You can also check the Troubleshooting tips related to the Microsoft Surface Dock firmware update.
Other support resources include the Microsoft Tech Community or the Technet forums where community members can learn, collaborate, and share experiences about Microsoft products. You can ask your question and start a conversation with other users, experts and also Microsoft engineers.
We hope your issue will get resolved soon. Thanks for being part of the Microsoft Docs community!

Hi again @madhoun, we didn’t hear back from you but we hope you were able to contact support (or checked out the other support resources) and resolved your concern. We will now close this issue, however, feel free to re-open if you have suggestions or ideas to improve the quality of this documentation.
Thanks for being part of the Microsoft Docs community!

@officedocsbot close