Main branch panic due to COPY_SRC error

Running examples panic for me. I'm on Linux (NixOS) using amd-gpu (open source driver).
relevant parts:
https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/src/render/pipeline.rs#L77-L84
thread 'main' panicked at 'Failed to acquire next swap chain texture!: Timeout', /home/marek/.cargo/git/checkouts/bevy-f7ffde730c324c74/1d0d8a3/crates/bevy_render/src/view/window.rs:159:24

There are 2:
a) how is it possible that I see the error even when I run examples which do use the helper
b) the panic might be related to some issue of development version of bevy
$ cargo run --example layers
warning: use of deprecated associated function `std::array::IntoIter::<T, N>::new`: use `IntoIterator::into_iter` instead
  --> src/mesher.rs:49:48
   |
49 |                     positions.extend(IntoIter::new([
   |                                                ^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: use of deprecated associated function `std::array::IntoIter::<T, N>::new`: use `IntoIterator::into_iter` instead
  --> src/mesher.rs:63:45
   |
63 |                     colors.extend(IntoIter::new([
   |                                             ^^^

warning: use of deprecated associated function `std::array::IntoIter::<T, N>::new`: use `IntoIterator::into_iter` instead
  --> src/mesher.rs:98:47
   |
98 |                     textures.extend(IntoIter::new([
   |                                               ^^^

warning: `bevy_ecs_tilemap` (lib) generated 3 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.13s
     Running `target/debug/examples/layers`
2022-01-03T11:51:32.607631Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1.6666666666666667
2022-01-03T11:51:32.675060Z  INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 5700 XT", vendor: 4098, device: 29471, device_type: DiscreteGpu, backend: Vulkan }
2022-01-03T11:51:32.848836Z  INFO bevy_ecs_tilemap::layer: Updating tile cache.
2022-01-03T11:51:32.864576Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864632Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864663Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864694Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864723Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864753Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864782Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864810Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864845Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864876Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864907Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.864934Z ERROR bevy_ecs_tilemap::render::pipeline: Texture atlas MUST have COPY_SRC texture usages defined! Please see: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/helpers/texture.rs
2022-01-03T11:51:32.947540Z  INFO naga::back::spv::writer: Skip function Some("get_mesh")
thread 'main' panicked at 'Failed to acquire next swap chain texture!: Timeout', /home/marek/.cargo/git/checkouts/bevy-f7ffde730c324c74/1d0d8a3/crates/bevy_render/src/view/window.rs:159:24
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

upstream issue https://github.com/bevyengine/bevy/issues/3288

Yeah the COPY_SRC isn't the issue here, although it doesn't help its being spammed to the console though..

I was able to pin down the reason for panic - it's upstream issue in bevy specific to opensource amd-gpu drivers on linux.
I think that's all we can do here. I'm not sure if you want to do something about that error log as well but I think it would make sense to have separate issue for it anyway. For the panic we just need to wait for fix upstream. Current workaround is to switch to proprietary driver. A bit painful but it's the only option at the moment.


Build a basic Todo App

As apart of the documentation we want the user to create a basic Todo application. This will cover:

Form functionality to enter the text
View / ViewModel interaction
Service creation and dependency injection
Service creation for wrapping a package (like SharedPreferences)

Done :white_check_mark:

Going into review now.


Login Spotify. Can't see the device

Just installed Raspotify and it is awesome! Thank you for your hard work. :)
I wonder why i can only play songs on ra'spotify localy (over LAN/WLAN).
I've deleted the "#" before "OPTIONS and gave my username and pass like this:
OPTIONS="--username <1161875533> --password <********>"
Log says : Authenticated as "1161875533"
but i cant see the new device on my list...
maybe im doing smth. wrong?
greets Adam
my raspotify status:

● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled)
Active: active (running) since Wed 2017-07-05 08:58:21 UTC; 47s ago
Process: 19680 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 19677 ExecStartPre=/bin/mkdir -p 0755 /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 19683 (librespot)
CGroup: /system.slice/raspotify.service
└─19683 /usr/bin/librespot --name Wohnzimmer --backend alsa --cache /var/cache/raspotify --bitrate 160 --userna...
Jul 05 08:58:21 RASPBERRYPI systemd[1]: Started Raspotify.
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: INFO:librespot: librespot 2259188 (2017-06-14). Built on 2017-06-14.
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, messa..." } }
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: INFO:librespot::session: Connecting to AP "lon3-accesspoint-a8.ap.spoti...4070"
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: INFO:librespot::session: Authenticated as "1161875533" !
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: INFO:librespot::session: Country: "DE"
Jul 05 08:58:21 RASPBERRYPI librespot[19683]: INFO:librespot::audio_backend::alsa: Using alsa sink

issue Closed. I've tried it on other raspberry pi, and it worked. Maybe some network configuration issue.


All Speech is interrupted by new dialogue box text and chat box messages when "Cancel the current speech when new text is available or text is advanced" is enabled.

The following bug occurs when "Cancel the current speech when new text is available or text is advanced" is enabled.

All text from dialogue boxes and triggered chat messages interrupt the queue and cancels current speech.  Newest triggered chat box text or dialogue text is played.

     Ideally this feature should only cancel dialogue text when new dialogue text is available or advanced.
A possible solution to this is to label dialogue text in the queue as dialogue, and when new dialogue text is available or text is advanced, clear the text labeled, "dialogue". Then, move triggered chat messages up the queue so they aren't lost.
I think people probably only want dialogue messages to interrupt dialogue messages, and everything should not interrupt each other.

Here is an recording using /echo and a dialogue box as an example of chat messages interrupting dialogue, dialogue interrupting chat messages, and chat messages interrupting chat messages.
https://streamable.com/8rpyoh
Feel free to reach out if you need any clarification! this one was a bit wordy because it was hard to explain 😅

Should be done when https://github.com/goatcorp/DalamudPlugins/pull/969 is merged.

I'm sorry if I confused you but I do actually like when the speaker is reset when their dialogue box disappears and reappears.
It worked really well, so I'm sorry that I accidentally made you revert that! it was one of my favourite and most wished for features 😅
What I meant to say was that chat text is currently being cleared by the Dialogue box being read out loud. New Dialogue boxes interrupting old dialogue boxes is the intended use.
Dialogue boxes interrupting messages from chat is more of the issue, but the inverse of chat messages interrupting dialogue boxes has been fixed in your newest update. Ideally People wouldn't want to lose messages read out loud in chat because of a dialogue box, I think they'd want it in order of what's triggered. and if the dialogue box speech is skipped, it would read the next speech in the queue first,
It currently seems like new dialogue is clearing the queue completely. and it would be nice if it was put in the back of the queue, and let other speech from chat go first if it was in the queue first. and if there's new dialogue, it would clear or skip the old chat dialogue in the queue.
Here's a diagram how I think the queue should behave. I think a visual interpretation might be a better way to express it than words, because it's complicated to explain but simple visually.

Again I would like to mention that the speaker being reset when their dialogue box disappears and reappears is the ideal feature, and I'm so sorry for making you revert that! It was the feature I was most looking forward to!
I do know that I'm being a bit knit picky, I just know that if people have certain chat channels enabled for TTS, it means that they want to hear it, and if it gets skipped because of a dialogue box I could imagine it being annoying.
Thank you for being so kind and patient! I really appreciate it!

Oh, I didn't know that the speaker being reset was related to this request, I reverted that for an entirely different reason. I thought it'd be neat, but based on feedback it sounded like it felt more inconsistent than anything else. I guess I can revert it again and see how it goes.
As for the dialogue versus chat stuff, I was pretty sure that was how this worked, at least from TextToTalk/TextToTalk.cs#L129-L136. When new data is found in the Talk addon, it should remove all queued items originating in the Talk addon from the queue, without touching any queued items from chat.
It sounds like it's just bugged now, will look into it.

Oh, I'm just blind, the queue removal thing is reversed in the code I just posted.

Fixes will be merged with https://github.com/goatcorp/DalamudPlugins/pull/971.

Should be fixed, merging with the linked PR.


Add party variable to Characters

Adds the party variable to all Character objects, storing the ID of the associated party member to the Character if they were created from one, as the previous system of relying on actor IDs to connect them runs into issues if two party members make use of the same actor

Love this addition!


why is try/import/export/module/expceptions Special and not Keyword?

Thank you for your work ❤
Just a question on reasoning behind making these a Special. If you want I can make a PR making them Keyword.
https://github.com/HerringtonDarkholme/yats.vim/blob/7978f7d52e1cfbdba1d17951c7bd4be527807e4e/syntax/common.vim#L104-L111

Thanks for the suggestion. You can HiLink the syntax in your vimrc. I choose Special because it makes TS file visually rhythmic by removing repetitive keyword color.


Unable to build on macOS 12.1

➜ cabal new-build
Resolving dependencies...
Build profile: -w ghc-8.10.7 -O1
In order, the following will be built (use -v for more details):
 - lzma-<IP_ADDRESS> (lib) (first run)
 - optparse-applicative-<IP_ADDRESS> (lib) (requires build)
 - tasty-<IP_ADDRESS> (lib) (requires build)
 - tasty-quickcheck-0.10.2 (lib) (requires build)
 - tasty-hunit-<IP_ADDRESS> (lib) (requires build)
 - lzma-<IP_ADDRESS> (test:lzma-tests) (first run)
Starting     optparse-applicative-<IP_ADDRESS> (lib)
Configuring library for lzma-<IP_ADDRESS>..
Building     optparse-applicative-<IP_ADDRESS> (lib)
cabal-<IP_ADDRESS>: Missing dependency on a foreign library:
* Missing (or bad) header file: lzma.h
This problem can usually be solved by installing the system package that
provides this library (you may need the "-dev" version). If the library is
already installed but in a non-standard location then you can use the flags
--extra-include-dirs= and --extra-lib-dirs= to specify where it is.If the
library file does exist, it may contain errors that are caught by the C
compiler at the preprocessing stage. In this case you can re-run configure
with the verbosity flag -v3 to see the error messages.
If the header file does exist, it may contain errors that are caught by the C
compiler at the preprocessing stage. In this case you can re-run configure
with the verbosity flag -v3 to see the error messages.

Installing   optparse-applicative-<IP_ADDRESS> (lib)
Completed    optparse-applicative-<IP_ADDRESS> (lib)
cabal: Failed to build lzma-<IP_ADDRESS> (which is required by test:lzma-tests from
lzma-<IP_ADDRESS>). The failure occurred during the configure step.

Note that lzma.h exists in /opt/homebrew/include
I've also tried cabal new-build --extra-include-dirs="/opt/homebrew/include", with the same outcome.

Nevermind--I confused myself. Running it with --extra-include-dirs does allow me to build correctly.

Sorry for the spam: I can build lzma directly, but not any projects that use it as a dependency. Not sure if this is an issue on your end or what. My other project fails with:
Build log ( /Users/adlai/.cabal/logs/ghc-8.10.7/lzm-<IP_ADDRESS>-ed2b458b.log ):
Configuring library for lzma-<IP_ADDRESS>..
cabal-<IP_ADDRESS>: Missing dependency on a foreign library:
* Missing (or bad) header file: lzma.h
This problem can usually be solved by installing the system package that
provides this library (you may need the "-dev" version). If the library is
already installed but in a non-standard location then you can use the flags
--extra-include-dirs= and --extra-lib-dirs= to specify where it is.If the
library file does exist, it may contain errors that are caught by the C
compiler at the preprocessing stage. In this case you can re-run configure
with the verbosity flag -v3 to see the error messages.
If the header file does exist, it may contain errors that are caught by the C
compiler at the preprocessing stage. In this case you can re-run configure
with the verbosity flag -v3 to see the error messages.

cabal: Failed to build lzma-<IP_ADDRESS> (which is required by test:spec from
nauvoo-<IP_ADDRESS>, exe:nauvoo-integration from nauvoo-<IP_ADDRESS> and others). See
the build log above for details.```

OK, finally got it working. For some reason, when building lzma as a dependency, cabal new-build only seems to respect the extra-include-dirs flag in the global cabal config, not the command-line flag or the project-level config. Not sure if this is a general issue with cabal, a problem with lzma, or I missed something else entirely.


add tests for collections search

add tests for collections search
ref #42

🤷♂ I don't get why the tests pass. Locally running
SELECT * from search('{"collections":["pgstac-test-collection"],"fields":{"include":["id"]}, "limit": 1}')

returns {"next": null, "prev": null, "type": "FeatureCollection", "context": {"limit": 1, "matched": 0, "returned": 0}, "features": null}
while the incorrect query
SELECT * from search('{"collection":["pgstac-test-collection"],"fields":{"include":["id"]}, "limit": 1}');

returns  {"next": "20200307aC0870130w361200", "prev": null, "type": "FeatureCollection", "context": {"limit": 1, "matched": 353, "returned": 1}, "features": [{"id": "20200307aC0870130w361200"}]} which is the expected results for the previous command 🤷♂


Amendment required for Practice Exam 8

Which of the following steps should be taken by a customer when conducting penetration testing on AWS?

A. Conduct penetration testing using Amazon Inspector, and then notify AWS support.
B. Request and wait for approval from the customer’s internal security team, and then conduct testing.
C. Notify AWS support, and then conduct testing immediately.
D. Request and wait for approval from AWS support, and then conduct testing.
Answer
Correct answer: D

Correct answer: B
It should be B because i've read that certain services don't require prior approval from AWS.

@kananinirav @alessiobennardo what are your thoughts on the above?
Can the answer to the question be updated?

@rebeus
According to my understanding, correct answer is D

AWS has specific policies for penetration testing, which include obtaining approval from AWS itself for certain types of tests on their infrastructure. This is separate from any internal approvals that may be required by the customer’s own security team.
AWS requires notification and approval to prevent any confusion between legitimate penetration tests and actual security threats. This also helps AWS monitor and ensure that testing does not adversely affect their services or other customers.
Therefore, while internal approval from the customer’s security team might be necessary as part of the customer’s own processes, it is not sufficient on its own. Approval from AWS is mandatory for certain types of penetration testing activities, making D the correct answer.

@kananinirav  - Thanks for that, in that case, the explanation you've provided should be appended to that answer of that question to help others if they are thinking the same way as I initially did.
Could you do that for me please?

Hello, I believe Option C (Notify AWS support, and then conduct testing immediately) is the right answer
Please refer to this link where they clearly mentionion that you do not need prior approval for penetration testing.

Correct me if I am wrong.


Sunburst - onValueClick not triggered when displaying Hint on onValueMouseOver

The onValueClick is triggered when Hint is not displayed but not when Hint is displayed. I checked the css as well, everything seems fine.
I have worked on the showcase examples project.  Here's my code.
import React from 'react';
import { Hint, Sunburst } from 'index';

const DIVERGING_COLOR_SCALE = ['#00939C', '#85C4C8', '#EC9370', '#C22E00'];

export default class AnimatedSunburst extends React.Component {
  state = {
    data: {},
    hover: null
  };

  render() {
    return (
      <div className="animated-sunburst-example-wrapper">
        <Sunburst
          onValueClick={e => console.log(e)}
          onValueMouseOver={v => this.setState({hover: v})}
          onSeriesMouseOut={v => this.setState({hover: null})}
          animation={{damping: 20, stiffness: 300}}
          data={this.state.data}
          colorType={'category'}
          colorRange={DIVERGING_COLOR_SCALE}
          style={{stroke: '#fff'}}
          height={300}
          width={350}
        >
        {this.state.hover &&
          <Hint value={this.state.hover} />
        }
        </Sunburst>
      </div>
    );
  }

Please help me knowing where I'm doing wrong.

Try removing the animation prop, I had an issue where the listeners don't really fire properly when it's present

Hey @subhamagr this issue should be fixed now! Sorry about the long delay


Upgrade all the things (#1801)

Proposed changes

Upgrade Gradle
Upgrade AGP
Upgrade the JDK
Setup the toolchain

Testing

Run the tests

Issues fixed
Fixes #1801

We can merge this PR in a very slimmed down version. This is great:
tasks.withType<JavaCompile>().configureEach {
    options.release.set(8)
}

Let's replace calls to {source/target}Compatibility with it.

Overall this PR is great and I would happily merge it, if not for the Java 11 on our internal monorepo blocking this.

I am going to close it for now, but will keep this PR in mind.
Re this - we don't have any Java code in this repo, so I don't think it's worth changing it at all.


Fixed Variables origin not being serialized as string

Ensure that Variables origin is properly serialized to locale string instead of a Variables object

I just told you in the other issue that I'm working on it and to keep watching this.

Sorry! Just curious, maybe I can help

@jasonvarga Do you think we can close this one in favour of #168 ?

Yup!


Bump xterm.js version to 1.1.3

Major feature upgrade is that IMEs now work, so people
can type non-latin characters into them!
Also has:
Better mouse support
Signed releases
Scrollbar
https://github.com/sourcelair/xterm.js/releases/tag/1.1.3

Much obliged!


Error when creating config for Adressable groups.

I added adressable asset bundles to my adressable groups and built them. I get the following error every time I select 'Create config for Adressables Groups':

I used the 'Default build script' for building adressables.
My adressable groups look like this:

The asset bundle adressable settings look like this:

My guess is that I'm doing something wrong.

I'm too experienced strange problems sometimes when upgraded packages.
I'm using Addressables package version 1.18.9 (later version would not work for me), and Google Play Plugins 1.5.0 (1.4.0 used to work fine too.).
Not sure how exactly to fix your problem, but you can try: Build > Clean Build >  All.
Also try to close and reopen Unity, or even restart the whole system.
Maybe it's related to problem with a build path, that's how I defined it on my system and it is working:

Hey,
This generally happens when you haven't build Addressables or there was an error during building them.
if you have a look to make sure Addressables are actually build in Library\com.unity.addressables.

Looks like Addressables are actually being built by the looks of it.

The console is not reporting any issues while building them. However when I try to create the config, the console gives me this message:
[AssetPackBuilder.CreateAssetPacks] path=
UnityEngine.Debug:LogFormat(String, Object[])
Khepri.PlayAssetDelivery.Editor.AssetPackBuilder:CreateAssetPacks(TextureCompressionFormat, String) (at Assets/AdressablesAssetDelivery/Editor/AssetPackBuilder.cs:41)
Khepri.PlayAssetDelivery.Editor.AssetPackBuilderMenu:CreateConfig() (at Assets/AdressablesAssetDelivery/Editor/AssetPackBuilderMenu.cs:14)

hm, can you check your Addressables Active Profile that there is a variable Local.BuildPath ?

Ok this is my current active profile.

Yeah, I guess that's the problem.
the code uses AddressableAssetSettings.kLocalBuildPath  to determine where the bundles are located, which has the value Local.BuildPath
Probably this was changed in a later version of Addressables then when you first created the profile (is my best guess)
You could add the variable Local.BuildPath with the same value as your LocalBuildPath.

That looks like it solved the problem. Thanks a lot!


slash is replaced with "C:/msys64" on MSYS2

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[ ] Linux
[ ] Mac OS X
[x] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce

Install msys2
Install fzf according to https://github.com/junegunn/fzf#using-git
run fzf /

Doesn't sound like an issue of fzf. What happens when you run echo /?

How about fzf --expect='/'?

@junegunn

This happens not only in zsh, but also bash and fish. So I think this may be a bug of fzf.

more tests:

Unlikely. fzf doesn't have any code that replaces given arguments.

https://github.com/junegunn/fzf/blob/ce9af687bcc58b2005c5d3f92bbaa08e77755bb8/main.go#L13
https://github.com/junegunn/fzf/blob/ce9af687bcc58b2005c5d3f92bbaa08e77755bb8/src/options.go#L1730
https://github.com/junegunn/fzf/blob/ce9af687bcc58b2005c5d3f92bbaa08e77755bb8/src/options.go#L1283-L1284
https://github.com/junegunn/fzf/blob/ce9af687bcc58b2005c5d3f92bbaa08e77755bb8/src/options.go#L1583

Oh sorry, it's a bug of msys2


Fixed the issue 2481 by not to take PULSAR_MEM from env.

Motivation
Command ./bin/pulsar-admin clusters list failed with Error: Could not find or load main class " in my k8s deployment by using helm charts.
Modifications
With helm deployment the env var PULSAR_MEM is quoted with ", taking it for pulsar-admin will make the exec command to be:
exec /docker-java-home/bin/java -cp '/pulsar/conf:::/pulsar/lib/*:' -Dlog4j.configurationFile=log4j2.yaml -Djava.net.preferIPv4Stack=true '"' -Xms1g -Xmx1g '-XX:MaxDirectMemorySize=1g"' -client -Dio.netty.leakDetectionLevel=disabled ... org.apache.pulsar.admin.cli.PulsarAdminTool /pulsar/conf/client.conf clusters list
The fix is to take out the use of env var PULSAR_MEM in conf/pulsar_tools_env.sh.
Result
pulsar-admin works as expected.
Fixes #2481

retest this please

cherry-pick as 588f6f2c5d32288e7404bbbbeb5049ac03dc0697 to branch-2.1


DownLoad apk just Test apk,can't install

...as from title.

@anton-ljf, now it should install.
Thanks.


Switch to OD - Background changes to Profile after proceeding to "Before you go" page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.26-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to Account settings
Go to Workspaces
Click Switch to Expensify Classic
Select an option
Click Next

Expected Result:
The background will remain in Workspaces page
Actual Result:
The background changes to Profile after proceeding to "Before you go" page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/784425e5-77cd-45cb-b7b8-6c99bb52e7c9
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
The screen below the overlay changes to profile when go to switch to OD response page.
What is the root cause of that problem?
The survey page (reason, response, and confirm) mapped to the profile page.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/libs/Navigation/linkingConfig/CENTRAL_PANE_TO_RHP_MAPPING.ts#L5-L25
So, when we open those pages, the matching root will be the profile page.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L192
It doesn't happen on the reason page (the 1st page) because somehow the state here is undefined.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/libs/Navigation/AppNavigator/createCustomStackNavigator/CustomRouter.ts#L38-L41
Switch to OD page can be accessed from many pages, not just profiles, so always mapping it to the profile page isn't eniterly correct.
What changes do you think we should make in order to solve the problem?

To fix this, we can add a backTo params to each page, so the matching root will be based on the backTo.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L112-L116
Steps:

First, update the reason route to accept backTo. Response and confirm pages already accept backTo.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/ROUTES.ts#L222-L231

Pass the current route as the backTo to the reason page.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/pages/settings/InitialSettingsPage.tsx#L144-L148

action: () => Navigation.navigate(ROUTES.SETTINGS_EXIT_SURVEY_REASON.getRoute(Navigation.getActiveRoute())),

Keep passing the backTo to response and confirm page.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/pages/settings/ExitSurvey/ExitSurveyReasonPage.tsx#L72

Navigation.navigate(ROUTES.SETTINGS_EXIT_SURVEY_RESPONSE.getRoute(reason, route.params?.backTo));

https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/pages/settings/ExitSurvey/ExitSurveyResponsePage.tsx#L64-L66
Navigation.navigate(ROUTES.SETTINGS_EXIT_SURVEY_CONFIRM.getRoute(route.params?.backTo));

Currently, we have a logic to modify the backTo on response and confirm pages when offline which still causes the issue.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/pages/settings/ExitSurvey/ExitSurveyResponsePage.tsx#L50-L56

The reason for that is we want to close the page when offline instead of going back to the prev page. Instead of modifying the backTo, we can just conditionally do the navigation to either dismiss or going back.
For response page
onBackButtonPress={() => {
    if (isOffline) Navigation.dismissModal();
    else Navigation.goBack(ROUTES.SETTINGS_EXIT_SURVEY_REASON.getRoute(backTo));
}}

For confirm page
onBackButtonPress={() => {
    if (isOffline || !exitReason) Navigation.dismissModal();
    else Navigation.goBack(ROUTES.SETTINGS_EXIT_SURVEY_RESPONSE.getRoute(exitReason, route.params?.backTo));
}}

Last, even though we already pass the backTo, it will still fail because the central pane route doesn't have a state.
https://github.com/Expensify/App/blob/9e82ed89b07c62ccb5d21a70398975bf0c37d11b/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L130-L133

Central pane isn't a navigator anymore, so it doesn't have the state just like other navigator (RHP, full screen) that contains the child screens. To fix this, we can check for state only for full screen navigator.

I need to double-check the expected behaviour as @Nodebrute has mentioned here

I agree that this is expected, and I think it's way to minor to worry about at this point - it does not have any impact on the user experience from what I can see. I'm going to close this out.

@VictoriaExpensify hi, I don't agree that it's expected. In https://github.com/Expensify/App/pull/47115, the issue is that, after refreshing, the report screen is shown and the step performed specifically done from the profile page (open the switch to expensify while on the profile page) while in this issue, we open the switch to expensify while on other pages and expect the page to not change to profile.
We fixed this kind of issue here:
https://github.com/Expensify/App/issues/47612, https://github.com/Expensify/App/issues/47069, https://github.com/Expensify/App/issues/46773


Fix SYS_gettid type to match first argument of syscall.

My apoogies - I should have picked this up on the first PR

Thanks! I'm rolling this up with some others in https://github.com/rust-lang/libc/pull/216 to land all at once.


When virtual option is used Swiper-React 6.0.x renders no slide

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version:
6.0.0-alpha.10

Platform/Target and Browser Versions:
macOS 10.15.5
Google Chrome 83.0.4103.116

Demo
Download and extract this zip file. Then do yarn and yarn start.

What you did
Created minimal project with swiper-react and enabled virtual like this:
<Swiper virtual>{slides}</Swiper>;

Expected Behavior
Should start rendering slides.
Actual Behavior
Does not render any slides. Swiper-wrapper is empty.

Swiper is out of alpha for a while already. Can you provide live example, for example on https://stackblitz.com/

@nolimits4web Hm, weird. I upgraded to swiper 6.0.2 but still the same problem remains.
Tried to create demo app on stackblitz but getting Import error, can't find file: ../../core.
Link to stackblitz:
https://stackblitz.com/edit/react-af5alb
So, I uploaded the demo on my webspace:
https://timo-ernst.net/misc/swiper-react-test-virtual/
Source code on GitHub:
https://github.com/valnub/swiper-react-test-virtual

same here, using reactjs

+same here

same

You need to install Swiper's Virtual module in order to make it work:
import SwiperCore, { Virtual } from 'swiper';

SwiperCore.use([Virtual]);

@nolimits4web this is not documented, that s why so much people experiment this error :)

@JSteunou Looks like this was added here: https://github.com/nolimits4web/swiper-website/commit/52981e8a38eb8805279abb4c9318a78245764395


Java DecimalUtility byte swapping for Integration Tests

Need to swap bytes when converting from Arrow data to/from BigDecimal

Awesome! Thanks @BryanCutler, will take a look in a bit.

@BryanCutler Thank you!


Get Fizzler 1.1.0 from NuGet.

version 1.1.0.
get from NuGet.
fixes #563.

Reference Issue

Fixes #563 Fizzler
What does this implement/fix? Explain your changes.

Output NU1701 warning.

Any other comments?

I did a check on the compatibility for non Windows OS since the embedded package is a .NET Framework 4.6.1 package, which could be problematic for Linux and Mac.
As expected the compatibility message is shown on the restore and build:

warning NU1701: Package 'Fizzler 1.1.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.2'. This package may not be fully compatible with your project.

But the tests and library seem to work just as fine as it did before. So from the non-Windows side: "good job! I approve this PR 👍 ".
To be honest, I am surprised, did not expect the core framework to be able to work with this, but seems the folks at Microsoft thought this one through 😄

@gvheertum
Thank you for checking on non-Windows !!

@mrbean-bremen, since we are referencing this as a separate package I don't think we need to have an additional license. When adding the Fizzler package the user will be shown the own license of the package.
Regarding the mention, I think we can put something in the Readme.md of our project regarding the licenses that apply. I tried looking for examples, but haven't found a suitable example. I think we can have a paragraph regarding the license (stating our own license) and then also mention the dependent projects and their licenses. I'll get back on that topic soon.

When adding the Fizzler package the user will be shown the own license of the package.

Ah, thanks,  that sounds right! I will merge in this case.

Regarding the mention, I think we can put something in the Readme.md of our project regarding the licenses that apply.

Yes, I agree. It may not be needed, but it's good style to mention other people's work we use.

@mrbean-bremen I think we should add a part in the readme.md stating our license and mention the dependent projects.
License
Licensed under the MS-PL license.
This project has dependencies on other open-source projects. These projects are referenced via NuGet packages and might be subject to different licenses.
|Project|Url|License|
|Fizzler|Link to git|LGPL|
|ExCSS|Link to forked git|MIT|
(The PR-reaction are not allowing me to add a nicelooking table, but I guess you get what I mean)

Yes, that looks good to me (fixed that table for you 😛).

Yes, that looks good to me (fixed that table for you 😛).

Haha, thanks! 😃
Are you planning to put that in a PR (or append this change to your PR) or do you want me to do a PR for the change in the readme.md?

@H1Gdev - after adding Fizzler as NuGet, we get these warnings. I guess this is not a problem, though it would be nice if we could avoid them...


Ansible post-provision task file does not seem to be working correctly

Issue Type
Support Request
Your Environment
Vagrant 2.2.5
VirtualBox 6.0.12r133076
ansible 2.9.2
  config file = None
  configured module search path = ['/Users/username/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/2.9.2/libexec/lib/python3.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.7.6 (default, Dec 30 2019, 19:38:28) [Clang 11.0.0 (clang-1<IP_ADDRESS>)]

Your OS
macOS (Mojave - 10.14.6)
Full console output
Output from vagrant provision: https://gist.github.com/pyrello/ea5ea8f42a63f2d3670347a167a2ffd3
vagrant@uiowa01:/var/www/uiowa01$ nvm

Command 'nvm' not found, did you mean:

  command 'nam' from deb nam
  command 'num' from deb quickcal
  command 'nm' from deb binutils
  command 'vm' from deb mgetty-voice
  command 'nvme' from deb nvme-cli
  command 'lvm' from deb lvm2
  command 'nim' from deb nim
  command 'npm' from deb npm
  command 'kvm' from deb qemu-kvm
  command 'pvm' from deb pvm
  command 'nvim' from deb neovim
  command 'nvi' from deb nvi

Try: sudo apt install <deb name>

Summary
I am attempting to add an Ansible task file to Drupal VM per these instructions: http://docs.drupalvm.com/en/latest/extending/scripts/#ansible-task-files
My Ansible task file is stored at scripts/nvm.yml and is based on this link: https://github.com/nvm-sh/nvm#ansible
- name: nvm
  shell: >
    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash
  args:
    creates: "{{ ansible_env.HOME }}/.nvm/nvm.sh"

I have added the following to my box/config.yml file to try to get this working:
post_provision_tasks_dir:
  - ../../../../scripts/nvm.yml

It seems that the task file runs, but the expected addition is not made to the /home/vagrant/.bashrc file. Is there anything you can see that I'm doing wrong?

I also failed to make it work with an Ansible task so I wrote a bash script triggered at post_provision_scripts step.
config.yml
post_provision_scripts:
  - "../../../../box/scripts/provision-node.sh"

provision-node.sh
https://gist.github.com/hugronaphor/7d346eba90730517bc1985811e7a1098

{
"open-in-browser.default": "chrome"
}

{
"open-in-browser.default": "chrome"
}


MNT: Re-rendered with conda-smithy 2.4.5

Also skip win32 build. I checked the original PR to staged-recipes, and this wasn't mentioned as a specific need for this package.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks John!


Some translations for pt-BR

Some translations for pt-BR language

Thanks @lucaszc !
@paulo-graca : Would you be willing to give this a review?  I noticed this may overlap with #1866, so we may want to determine which to move forward.

sure @tdonohue !

Thank you @lucaszc for addressing my suggestions. Currently this PR has some code conflicts (because of PR #1866 ). Can you fixed them so it can be merged?

New commit with merge translations from #1866, and more translations ..

@paulo-graca  I don't understand the failure. The  json5 file , looks good.
Best Regards
Em seg., 3 de out. de 2022 18:39, Paulo Graça @.***>
escreveu:

@.**** approved this pull request.
Thank you again @lucaszc https://github.com/lucaszc for your
contribution and for addressing my suggestions! It's a +1 for me. It's
currently failing tests, I just saw the failure and it doesn't seam to be
related with this PR. I will force them to run again.
—
Reply to this email directly, view it on GitHub
https://github.com/DSpace/dspace-angular/pull/1869#pullrequestreview-1129056473,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMMUI3AO2BBQFRUJPXZFMLWBNHCPANCNFSM6AAAAAAQZAG2ZE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tdonohue , Now this file load correct in my DSpace UI Enviromment , but fail in build tests ...  I validate json5 in external validator.  Any suggestion ?

@lucaszc : We have some tests which randomly fail (we're still looking into why)...this looks to be one of them. I'll rerun the tests for you and chances are they will work the second time around.


Long compilation time when installing PyTorchEMD

Environment

OS: [e.g., Ubuntu 20.04]
GCC version: 8.5.0 20210514 (Red Hat 8.5.0-18)
NVCC version: 10.1
Others: followed your instruction

Issue Description
I tried to install PyTorchEMD on my system, but the compilation process is taking a very long time. I ran the following commands:
cd metrics/PyTorchEMD
python setup.py install

The python setup.py install step is particularly slow. Is there any way to speed up the compilation process or any pre-built binaries available?

Expected Behavior
I expected the compilation process to be relatively quick, or at least have some indication of progress or estimated time to completion.
Actual Behavior
The installation process takes an unusually long time with no clear indication as to why it's taking so long or how much longer it will take.
Any advice or solutions would be greatly appreciated!

Please try to follow README and set up the PyTorch environment properly. Meanwhile, you can post issues in the original PyTorchEMD repo for any help.


.NETFramework,Version=v4.8 were not found error

getting this error and not seeing a NETFramwork for Linux thats V4.8 tried using the normal installer but nothing.

Are you trying to use it on linux?

Yeah isint that where your suppose you use it?

Negative!
It's a UAC bypass, so you should use it on Windows

Yea I know but I'm getting that error trying to build the application via Linux...


Using arrows to pick year -- have to press 12x to change year

Describe the bug
In the calendar popup menu, if you click on the year, if you try to pick the year using the arrow keys (left/right are all that seem to work), you have to press the key 12x before it moves one year.
To Reproduce
Steps to reproduce the behavior:

Go to https://stackblitz.com/edit/vuepic-vue-datepicker?file=src%2Fcomponents%2FPlayground.vue
Click on the calendar control.  Then click on the year.  The click the right arrow -- after you press the arrow key 12 times the year will change

Expected behavior
I expected that for each arrow key pressed the year would change by one year
Screenshots
Here is the year view I'm having issues with:

Desktop & mobile (please complete the following information):

Browser: Chrome, Version 114.0.5735.134 (Official Build) (64-bit)
Library version ^5.3.0

The thing is, this was never intended behavior 😄 . What you see by pressing the arrow is a listener for changing months by 1 being called (for keyboard navigation), so when you press enough times, the year changes..
This makes it both bug and a feature.

Only the bug will be handled, for the arrow year switch, there is an arrow navigation instead (or use exposed methods), it requires unnecessary calculations to extract the data. It may be handled in some future release


Namespace Mechanism for Artifacts

We need a higher-level organizational construct that would enable mlte to be employed in a larger organization. A generic namespace mechanism should satisfy this need. To make this happen, we need to consider the following:

Addition of namespace to the mlte context
Integration of namespace into artifact store storage
Integration of namespace considerations into the mlte API

This is addressed by #152.

This is resolved by #152.


After<EMAIL_ADDRESS>,create by vite,The project con't read composition api

Version
3.2.20
Reproduction link
codesandbox.io
Steps to reproduce
create a project width vite and typescript, By the lastest version, import { InjectionKey, provide, inject } from 'vue', It's will report an error, TS2305: Module '"../../node_modules/vue/dist/vue"' has no exported member 'InjectionKey | provide | inject'
tips: System: Mac OS
What is expected?
import { InjectionKey, provide, inject } from 'vue' can work in project
What is actually happening?
Module '"../../node_modules/vue/dist/vue"' has no exported member 'InjectionKey | provide | inject'

I can't reproduce this with a fresh Vite project, and you didn't provide an actual reproduction of the issue. Closing.

@LinusBorg
InjectionKey is not exported. see docs https://v3.vuejs.org/api/composition-api.html#provide-inject and sfc

Yes it is.

https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/apiInject.ts#L6


Update API dependency: add detached mode

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>Relevant issue:
https://github.com/open-cluster-management-io/registration-operator/issues/157
https://github.com/open-cluster-management-io/registration-operator/issues/158

/assign @qiujian16
Since both cluster-manager and klusterlet rely on API updates, we could merge these updates at first.

/assign @zhujian7

/approve
/lgtm


⚠ Samsung has degraded performance

In 7e2e778, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1996 ms

Resolved: Samsung performance has improved in cb8f1d1.


never doesn't equal never when never is keys/values from filtering generic object wrapped inside another object by exact value

Bug Report

🔎 Search Terms
never equals filter mapped type

🕗 Version & Regression Information

It's broken in all tested versions of typescript (4.1.5 until 4.9.0-dev.20221011 in TS playground). Versions prior 4.1.5 do not support mapped types keys filtering.
⏯ Playground Link

Playground minimal code
Playground both keyof and of Values<> cases
💻 Code
So wee need to:

Wrap generic argument, lets say O, in an object(i.e {anyKey: O} or just [O]).
Then filter object keys by exact value via Equals<> in such a way to pass further empty object.
Extract keys or values. Since object is empty never will be passed.
And finally compare it with never via  Equals<>

// helpers start

type Values<O extends object> =
  O extends any[]
    ? O[number]
    : O[keyof O]

type Equals<A, B> =
  (<T>() => T extends B ? 1 : 0) extends
  (<T>() => T extends A ? 1 : 0)
    ? true
    : false

// helpers end

type FilterByStringValue<O extends object> = {
  [K in keyof O as Equals<O[K], string> extends true ? K : never]: any
}

type FilteredValuesMatchNever<O extends object>
  = Equals</*never*/Values</*{}*/FilterByStringValue<[O]>>, never>

type filteredValuesMatchNever = FilteredValuesMatchNever<[]> // false wrong

🙁 Actual behavior
filteredValuesMatchNever is false
🙂 Expected behavior
filteredValuesMatchNever must be true.
Actually with the FilterByStringValue rewritten like this:
type FilterByStringValue<O extends object> = {
  [K in keyof O as Equals<O[K], string> extends true ? K : never]: O[K]
}

filteredValuesMatchNever  somehow becomes true

This definition of Equals is very weird -- where did you find this?
Using a more straightforward definition
type Equals<A, B> = [A] extends [B] ? [B] extends [A] ? true : false : false;

this works as expected, though the more-compact form doesn't for some reason:
// Doesn't work
type Equals<A, B> = [A, B] extends [B, A] ? true : false;

@RyanCavanaugh That particular definition of Equals shows up quite a bit in the larger TS community and IIRC specifically takes advantage of assignability rules for deferred conditional types (isTypeIdenticalTo), to work around some edge cases with the more naive definition.  I don’t remember what these cases are off-hand, though.
Explanation here:
https://stackoverflow.com/questions/68961864/how-does-the-equals-work-in-typescript

Yep, this is a fairly popular type - it allows one to easily check if a type is any or not and stuff like that.
It also comes with a funny behavior related to structurally equivalent intersections:
TS playground
And I suspect that this sort-of thing is responsible for the issue here. Even though the type gets reduced~ to never, its identity is not actually never and thus it fails this Equals check. That probably shouldn't be observable publicly though.
This issue looks quite similar to what I've reported in the past (issue) and what got fixed here. However, I've confirmed that the issue is not the same and while my issue was a regression in 4.4, this one here didn't work before that.

The fact that it still repros on the tuple form is pretty interesting, since that should be going through the normal relational path

This is quite interesting!
We have 3 different Equals implementations here, let's call them as follows:

nested: type Equals<A, B> = [A] extends [B] ? [B] extends [A] ? true : false : false;
short: type Equals<A, B> = [A, B] extends [B, A] ? true : false;
identity-based: type Equals<A, B> = (<T>() => T extends B ? 1 : 0) extends (<T>() => T extends A ? 1 : 0) ? true : false

We also have 2 different implementations of the filtering mapped type:

any-value: one with any at the value position of the mapped type, note that different types at this position can also exhibit the same, broken, behavior
indexed access value: one with O[K] at the value position of the mapped type

I don't intend to explore all combinations of those 2 sets but I will mention particular variants from both of those.
nested Equals + any-value
This one works correctly: TS playground

this one is recognized as "typical nondistributive conditional type" (here)
so the type parameter gets unwrapped from the single-element tuple in the check type (here)
and thus the check type is classified as instantiatable (here)
based on this TypeScript doesn't attempt to resolve the conditional type (here). Thanks to that the conditional type is left roughly untouched and gets finally resolved when the actual type arguments are supplied to it

short Equals + any value
This one doesn't work correctly: TS playground

this isn't recognized as the typical nondistributive conditional type
its check type is left unwrapped
its instantiated check type is [A, B] and it's not classified as generic here. It turns out that a generic tuple type is only a one with a variadic element (isGenericTupleType)
So the TypeScript attempt to resolve this based on the check here
Resolving involves checking the assignability of the permissive intantiations of checkType ([any, never]) and inferredExtendsType ([never, any])
since any is not assignable to never this assignability check fails and falseType gets selected as the result (here)

short Equals + indexed access value
This one works correctly: TS playground
It's kinda interesting because almost everything here is the same as in the variant described above. However, in here checking the assignability of the permissive intantiations returns a different result despite the fact that we seamingly compare the same types ([any, never] and [never, any]).
So why is that? In here, the any type is actually not the "true any" - it's a "wildcard type" and that is assignable to never. So based on that the overall conditional type stays roughly untouched and gets finally resolved when the actual type arguments are supplied to it.
Note: it would be kinda nice if the wildcard type would get printed as any* or something like that. The same could be done about the silentNeverType (and maybe some others). Since they are printed in the same way, it's fairly easy to not notice the difference between them when debugging.
identity-based Equals + any value
This one doesn't work correctly: TS playground
This is fairly similar to the "short Equals + any value" case. The only difference here is what permissive instantiations we are comparing here for checkType (<T>() => T extends never ? 1 : 0) and inferredExtendsType (<T>() => T extends any ? 1 : 0). Since those are not assignable, we simply select the falseType here too.

I found out something interesting.

So ts assumes that this type will always be false and use cached value all the time.
Well, it's right about the type being supposed to always return the same value. But it must always be true rather than false.
FilteredValues wraps object type argument in another one so that resulting object has no string values. Then type is passed to FilterByStringValue where non string values are filtered from the result. So FilterByStringValue here always return {} and FilteredValues should always return never. Thus equality check to never should always be never.
If I substitute FilteredValuesMatchNever type call with it's implementation, the result will be true as desired.
type filteredValuesMatchNever = Equals<FilteredValues<O>, never> // true

I also tried passing never as an argument. And it worked.
type FilteredValuesMatch<O extends object, M> = Equals<FilteredValues<O>, M>

type filteredValuesMatchNeverAsArgument = FilteredValuesMatch<[], never> // true

infer works as well.
type FilteredValuesMatchNeverInfered<O extends object> =
  Equals<O extends infer R ? FilteredValues<O> : never, never>

type filteredValuesMatchNeverInfered = FilteredValuesMatchNeverInfered<[]> // true

update

That particular definition of Equals shows up quite a bit in the larger TS community

It doesn't work well. type-fest uses that implementation and failed some of my tests.
In type-plus, I do this:
export type Equal<A, B, Then = true, Else = false> = [A, B] extends [B, A]
	? And<IsAny<A>, IsAny<B>, Then, Or<IsAny<A>, IsAny<B>, Else, Then>>
	: Else

btw Equal<A, B> = [A, B] extends [B, A] ? true : false works correctly with TypeScript 5

Yep, this was fixed here (in response to this very issue here)


Deprecated constant values

Hey,
After HA Update, I saw in logs following infos. It's not crucial for now but it'll be easier to read them without it :)
Logger: homeassistant.const
Source: helpers/deprecation.py:205
First occurred: January 9, 2024 at 10:57:40 PM (1 occurrences)
Last logged: January 9, 2024 at 10:57:40 PM

TEMP_CELSIUS was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'tech' custom integration

Logger: homeassistant.components.climate.const
Source: helpers/deprecation.py:205
Integration: Climate (documentation, issues)
First occurred: January 9, 2024 at 10:57:40 PM (10 occurrences)
Last logged: January 9, 2024 at 10:57:40 PM

CURRENT_HVAC_COOL was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.COOLING instead, please report it to the author of the 'tech' custom integration
CURRENT_HVAC_IDLE was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please report it to the author of the 'tech' custom integration
CURRENT_HVAC_OFF was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.OFF instead, please report it to the author of the 'tech' custom integration
SUPPORT_PRESET_MODE was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please report it to the author of the 'tech' custom integration
SUPPORT_TARGET_TEMPERATURE was used from tech, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please report it to the author of the 'tech' custom integration

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:1520
First occurred: January 9, 2024 at 10:57:43 PM (8 occurrences)
Last logged: January 9, 2024 at 10:57:43 PM

Entity None (<class 'custom_components.tech.climate.TechThermostat'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE: 1>, please report it to the author of the 'tech' custom integration and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

I found your open issue, got the same message in the HA logs.
Hope that it will be fixed somewhere this year.


Use tool:pytest in setup.cfg since pytest has been deprecated

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   93.16%   93.16%
=======================================
  Files          56       56
  Lines        3056     3056
=======================================
  Hits         2847     2847
  Misses        209      209

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 b56f78c...da6a066. Read the comment docs.

Thank you!

This change is present in version 1.1.3.


Upgrade react-native to 0.59.0

Working on ios
Working on android
Upgrade react-native-maps to v0.24.0-rc1

also note, I am merging into a feature branch, I might want to do some more native upgrades before we merge this into master.


Fix window operation with kRange frames with column boundary

Summary:
When Window operator is initialized, WindowBuild reorders the input columns to
place partition keys and sorting keys first before adding input rows to
RowContainer. However, for window operations that use kRange frame with
column boundary, e.g., range between c1 preceding and current row, the original
column index of the frame column before reordering is passed to
computeKRangeFrameBounds(), which leads to incorrect result. This diff fixes
this bug by passing the actual index of the frame column after the reordering to
computeKRangeFrameBounds().
This diff fixes https://github.com/facebookincubator/velox/issues/9229.
Differential Revision: D55351848

Hi @aditi-pandit, could you help review this fix? Thanks!

@kagamiori : So your original idea to pass windowBuild_.inputType_  to createWindowFrame is actually a more correct fix imo.
The reason you had other issues is because the wrong type is used to figure indices in multiple places...in sending the function parameter indices to the WindowFunction, in mapping output columns to input columns for getOutput().. There might be other places as well.
We likely didn't encounter these issues because none of our testing flipped order of columns in this way :( So we should incorporate this in the fuzzer as well.
Let me try your test with some fix logic. I'll send you a sample PR in mind in a few hours.

@kagamiori : I debugged this a bit more.
So there wasn't an issue with the function column indices or output indices because the WindowBuild code had constructed WindowPartitions (used for function and output indices) providing a column mapping using the input type order.
The range frame code needed to use that mapping as well. Since the Window operator code uses the input type indices everywhere its consistent to send the original index from Window->WindowPartition.
See https://github.com/facebookincubator/velox/pull/9266/commits/355e13f535114eb360e9343ae78d1a309e5f1fdd for changes over some of the code in this fix.

Hi @aditi-pandit, thanks a lot for the suggestions in #9266! I've updated the PR and addressed your comments. I've also added addition comments about the expected order of columns in WindowBuild::data_ and WindowBuild::inputColumns_ for clarity. I've combined the computation of inversedInputChannels_ with the computation of inputChannels_ and inputType_ together. Please let me know if you would like a different refactoring or have further suggestions. Thanks!

Hi @aditi-pandit, I've updated the PR to address your comments. Please take a look again. Thanks!


Update gtm-your-marketplace-benefits.md

@pavankumarMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Implementing Empty Service Adapter

@tylerslaton
What does this PR do?

Implementing Empty Service Adapter (fixes #1157)
Exporting the adapter for use
Also exporting the Ollama experimental adapter
Exporting CopilotRuntimeChatCompletionRequest, CopilotRuntimeChatCompletionResponse to make it easier for someone to implement their own custom adapter

Related PRs and Issues

https://github.com/CopilotKit/CopilotKit/issues/1157

Checklist

[x] I have read the Contribution Guide
[ ] If the PR changes or adds functionality, I have updated the relevant documentation

Note: Experimental Ollama doesn't have documentation I found in this repo, I haven't added one for the Empty Adpater.

As per conversation with @tylerslaton

Let me know if any change is needed

Looks great, thanks for the contribution!

Hmmm, those quality checks...

Not sure about the versioning policy. No breaking changes here, maybe worth a step version bump, but maybe rolled together with other changes. I didn't want to touch versions because that can cause a recurring merge conflict point.

Another small thing before this can be merged @MrCsabaToth
Can you run pnpm run format in the packages folder? The prettier check seems to be failing

Another small thing before this can be merged @MrCsabaToth Can you run pnpm run format in the packages folder? The prettier check seems to be failing

Originally this supposed to cure that. I ran pnpm run check-prettier in the Copilot subdirectory and it didn't display change. Can you point to the failed check?

Another small thing before this can be merged @MrCsabaToth
Can you run pnpm run format in the packages folder? The prettier check seems to be failing

For the e2e checks: maybe that wasn't from the latest?

Great addition @MrCsabaToth. Thanks for the contribution. merged!
I will deal with the formatting, no need to worry about it.
Thanks again!

Awesome contribution, thanks @MrCsabaToth!


Paragraphs indented with no blank line

A blank line is not recognized as the start of a new paragraph, like what GFM does on GitHub.com.
Furthermore, there is an indent, which looks weird when there is no preceding blank line.
The example picture is from https://mmistakes.github.io/minimal-mistakes/theme-setup/

I understand that coding can be different within this theme and GitHub.
To get an empty line to show, I use the workaround of    between two blank lines.
But how can I begin a new paragragh without indention within index.md and post files?

It's a fairly simple CSS declaration. Basically I'm using p + p to apply an indent to a paragraph that follows another paragraph. There's also some negative margin being applied.
If the spacing is giving you issues I'd suggest disabling the indent. It's really typographic preference that's not for everyone and looks best in certain circumstances. When you have short paragraphs or list elements it can look off sometimes.

OK. That worked for me. But I would personally prefer to have the default $paragraph-indent: off since most of my paragraphs are short. Who writes long paragraphs anymore ;)


Any idea on server application?

I have actually live555 code for rtsp stream, websokify for converting rtsp to websocket. i then changed the rtsp and ws addess in index,js , but video not playing, in wireshark capture, After RTSP SETUP its showing "session not found"

other brand cameras have different track ids. try changing the track id in the code. Some cameras give trackId as video/audio


Revise ISSUE_TEMPLATE [skip ci]

Optimize typesetting and fix links.
Rename the template file.

I don't know why git shows it as deleted & new files.

thx!

I will consider porting it to other sub-projects.

If you are interested in this and have enough free time, you are welcome to :)


is_mutable_string takes one argument

fix #242

You could add a test, ifdef for C++20 that checks against the concept. The test would go in test/unit/grammar/type_traits.cpp

Done


ScrollView(maybe FlatList) Style issue

Hello, I try to use it however there is a problem about FlatList style issue.
This is my app screen.

I used RN 0.62.1

I think we need to downgrade to 1.0.7 It's best way to continue our work.

Hi! I look into this during this during the weekend.
Take care!

@jimmybengtsson Thank you for reply!

having same issue has it been resolved or i should downgrade to  1.0.7 . Thank you .

By reverting (pull #19 ) the change from View to Flastlist added in 1.0.8, this shall not be an issue anymore. Can you please download version 1.0.10 and confirm that it’s working?!
Thanks!


[WIP] PR: Add support for object arrays in the Variable Explorer

After PR #5259, I realized it was not that hard to support object arrays.
TODO:

[ ] Use value_to display to show the contents of the array (else big repr's would make the viewer to take a long time to appear).
[ ] Tests.

Hello @ccordoba12! Thanks for submitting the PR.

In the file spyder/widgets/variableexplorer/arrayeditor.py, following are the PEP8 issues :

Line 638:80: E501 line too long (82 > 79 characters)
Line 644:15: E127 continuation line over-indented for visual indent

@ccordoba12 The main idea for these PR is to visualice in the object explorer np arrays when they are made up of objects?
As well, I'm going to create a new PR for solving this one because the merge with our current master is huge and has a lot of conflicts.