python310Packages.pyunifiprotect: 4.5.2 -> 4.5.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pyunifiprotect is: "Library for interacting with the Unifi Protect API"
meta.homepage for python310Packages.pyunifiprotect is: "https://github.com/briis/pyunifiprotect"
meta.changelog for python310Packages.pyunifiprotect is: "https://github.com/AngellusMortis/pyunifiprotect/releases/tag/v4.5.3"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5.3 with grep in /nix/store/qr75awvb7a9a7dfs3ap1xrmr4z4q6ibl-python3.10-pyunifiprotect-4.5.3
found 4.5.3 in filename of file in /nix/store/qr75awvb7a9a7dfs3ap1xrmr4z4q6ibl-python3.10-pyunifiprotect-4.5.3

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python39Packages.pyunifiprotect
unifi-protect-backup

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qr75awvb7a9a7dfs3ap1xrmr4z4q6ibl-python3.10-pyunifiprotect-4.5.3
ls -la /nix/store/qr75awvb7a9a7dfs3ap1xrmr4z4q6ibl-python3.10-pyunifiprotect-4.5.3/bin

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

4 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python39Packages.pyunifiprotect
unifi-protect-backup

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 207998 run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python39Packages.pyunifiprotect
unifi-protect-backup


Please update npm

I'm using github as dependency since npm has the same version but with different source code and method getAudioSources is missing.
Thanks.

#8 needs to be fixed first 😅

@matheuss I don't think that's necessary. None of those changes in #8 are breaking. I think we should just do a new release now.

// @StefMa

Done: https://github.com/wulkano/aperture/commit/0288c3b52e1a6cf5008c47faa2669882e1d22513 Note that we renamed this project from aperture.js to aperture.


PDF to JPG converter

Description of the new feature / enhancement
An option to quickly convert PDFs to JPGs from right-click context menu in File Explorer.
Scenario when this would be used?
This would be used whenever a quick PDF to JPG conversion is needed.
Supporting information
This is a long-standing feature on Macs, apparently. It would reduce the multi-step pain point of having to (find and) open a program, find the  right tool, do a save as, go back and find the file in the folder, etc.

/dup https://github.com/microsoft/PowerToys/issues/9743


Bad recording results

OS: [Windows]
scrcpy version: [1.17]
installation method: [command prompt]
device model: Nokia 3.1 plus
Android version: [10]

To put it simply, when I mirror the screen and record it, everything is normal, but after I watch my recording results that I have done, everything is!!??? [I don’t know how to describe it, just look at the video]
https://user-images.githubusercontent.com/84991558/120033635-7f1de580-c004-11eb-8af6-af7d3110a06f.mp4
and i don't know but you might need this:-        :p
C:\Users\USER\Downloads\scrcpy-win64-v1.17>scrcpy -b 100M --max-fps 60 -r test.mp4 INFO: scrcpy 1.17 <https://github.com/Genymobile/scrcpy> C:\Users\USER\Downloads\scrcpy-win64-v1.17\scrcpy-server: 1 file pushed, 0 skipped. 84.4 MB/s (34930 bytes in 0.000s) [server] INFO: Device: HMD Global Nokia 3.1 Plus (Android 10) INFO: Recording started to mp4 file: test.mp4 INFO: Renderer: direct3d INFO: Initial texture: 1280x720 INFO: Finishing recording... INFO: Recording complete to mp4 file: test.mp4 WARN: Killing the server...
That's all    ;)

oh wait!!!!! I'm so sorry, I know why did this happened it's not because of scrcpy it's because of the media player that I was using it was the original media player that comes officially with windows 10, I realized this when I uploaded the video on github for you to see it and I saw that the quality was normal so I played it on VLC and also it was normal and good quality and I don't know why is this happening but any way thanks.   ╰(°▽°)╯
I'm sorry to bother you  👍
scrcpy is  🥇


Finding gradients.

gradientify and get_var_ranges.

This is fine. Tests passing. Merging.

This is fine. Tests passing. Merging.


IntelGPU backend: Sin, cos, log, exp operations

Implementation of these layers are done in clDNN (https://github.com/intel/clDNN/pull/36) and we can use it in nGraph.
The latest version of clDNN required to build.

TESTNOW


socket protocol

We are trying to make socket connection from ios, but on connect, it crashes, it can't read the protocol and it gives error ( negotiated protocol is (null)), any idea about that?

Is this still a problem?


Delete a few paragraphs that should not have been there.

I pushed the wrong branch yesterday when trying to delete these paragraphs and so the change didn't 'stick'.

This change is

@duglin

thanks! LGTM but IANAM


Dry run is not effective when Import Resource is used

When I do a dryrun on Test Cases that utilize a dynamic import (Import Resource), it fails saying that the keywords are missing, but during a real run, they are imported and available as expected.

The problem is that library keywords like "Import Resource" aren't executed at all. There are certain exceptions to this, like "Run Keyword If", and possibly "Import Resource" and other import keywords could be handled the same way. Unfortunately variables cannot be evaluated in the dry-run mode (we got an issue about that as well), and I would except most import keyword usages to use them. It this thus a bit questionable would that change alone make a real difference.
What's your use case for using "Import Resource"?

I am essentially trying to implement polymorphism. So that from my Test Case, I can call a Keyword, but depending on the environment, the Keyword implementation may come from one of a few different Resource files. The way this is done is that during Suite Setup, the execution environment is checked and the proper Resources are Imported.
As far as implementing the dry run for robot, it would be quite a challenge because, in this case, there are duplicated Keywords. I just thought I would see where this idea lands :)

Have you tried implementing this by using normal resource import having a variable like:
Resource            ${ENVIRONMENT}.resource

In this context variables may be resolved even in dry-run.

Interesting..I did not realize that was an option. I can definitely use that to simplify some of my test cases. But, there are still variables, in my situation, which are only determined during run-time. I do not see how I can do the normal resource import for this case. Any other thoughts/ideas?

I encountered a similar issue using Import Library.
My use case
I use the Import Library myvar=${baz} FOO to generate multiple instance of library FOO with value myvar set to variable baz. As a configuration. Because baz variable is present in the call, dry-run fails because it is unable to resolve the Import Library keyword.
Error message is: Resolving variable '${baz}' failed: Variable '${baz}' not found. It causes the successive call of FOO's method to also fail, leading to multiple failures in the dryrun.
Saving our CI
We use dryrun in our CI to validate syntax. Ignoring segments where we do dynamic Import Library would be fine. Ideally we would have a way to avoid failures when they are encountered. We though about overloading Import Library to have a version where the variable is not used when in dry-run, but it feels like it is a very hacky solution.
Is there a way to ignore the dynamics import, such as Import Resource or Import Library during dry-run? Even if it ignores the complete test case or resources associated

In my case, I had to use only one keyword from imported resource, so I just moved Import Resource keyword to another container-keyword with robot:no-dry-run tag in it. Worked correctly but I wouldn't like to use it in a broader context.

There's PR #5131 that ought to fix this, but it lacks tests. It can still be merged before RF 7.1 if tests are added.

Implemented in PR #5131 by @wendi616. Thanks for the contribution!

Due to the limitation that variables aren't available in dry-run, all Import Resource usages aren't going to work. An exception is using the ${CURDIR} variable, because it is handled differently than other variables.


Log reasons why npm audit can't succeed

This will make it easier to see why an update wasn't possible by viewing the job logs. Ideally we'd surface these in update error message but until then this is better than needing to reproduce the failure with the debugger.

I only wonder about the change in terminology from valid to viable in the method name, while keeping the method a predicate that returns true only if the result is :valid.

Good eye! I renamed that because valid_audit_result? returned true when audit_result["fix_available"] == false. In that case it was technically valid but later on we wouldn't do the update because there wasn't a fix available. viable_audit_result? returns false when audit_result["fix_available"] == false but this doesn't change the end behavior of not doing the update.
I think I'll change the result from :valid to :viable to be more consistent?

Makes sense!


(OUI Docs) Notification event

Notification event is listed as "beta" in the last open source version of EUI, now forked for OUI.

[ ] Evaluate Notification event in its current state and validate documentation (functionality provided, implementation details correct)
[ ] List changes if documentation needs to be updated
[ ] Evaluate Notification Event and identify a pathway to making this component more stable (out of beta)

@KrooshalUX
Evaluate Notification event in its current state from the above list - Is it auditing task for notification event?

@kaddy645 will look into this.

@KrooshalUX I do not think we are using this component anywhere in OSD. looking at its current state it looks good to use. In future we might need to update some of its prop if needed.

@kaddy645  correct, we are not using it yet. I mostly just wanted to know if there is anything you might find that would prevent us from using it - sounds like no concern with its current implementation and documentation. Thanks!

@kaddy645 did you notice any differences between the component and the documentation? if not, we can check these tasks off and close the issue, and i can remove beta from the docs pages (tracked in the meta docs issue)

Component looks good to me. there are few required props we have in docs that end user will need when using this component.

Id : A unique identifier
title :The title of the event.
eventName : A unique, human-friendly name for the event to be used in aria attributes (e.g. "alert-critical-01", "cloud-no-severity-12", etc..
messages : Notification messages as an array of strings. More than one message wraps in an accordion.
time : Indicates when the event was received.
iconType : icon used to visually represent this data type. Accepts any OuiIcon IconType.
type : Type of event (e.g. "Alert", "Cloud", etc..). Shows inside a badge.

Updated description relevant to docs site task


Where do things get downloaded to?

Instead of printing
Installing runtime/org.gnome.Platform/x86_64/46...

maybe it could print the path where it gets downloaded to?

Looks like

Runtimes get downloaded to the system-wide /var/lib/flatpak/ (where Flatpak would also download them). This might be the reason why we need to be root to use this tool?
Applications get downloaded to /tmp/flatrun/.tmpXXXXXXX/

Looks like
* Runtimes get downloaded to the system-wide `/var/lib/flatpak/` (where Flatpak would also download them). This might be the reason why we need to be root to use this tool?

* Applications get downloaded to `/tmp/flatrun/.tmpXXXXXXX/`

Correct

I am looking for a way to download an application and any runtimes it requires into its own directory, so that everything that is needed to run the application is contained in that one directory. Ideally also bubblewrap and a small launcher script to launch the application.

The extraction to a directory is certainly doable, the bubblewrap part might take some more involved steps but that can be on the roadmap as well. I think I have an idea of what you'd like to do with that ;)


Prefix not added to all URLs?

Hello!
I'm trying to run JSbin under a special path, however it seems not all asset URLs get prefix with the prefix configuration option. I've sprinkled some log statements in app.js, and I can see the prefix is loaded correctly from the configuration, yet it seems the {{root}} and {{static}} variables in the templates are set to the hostname (including protocol) but the prefix is nowhere to be found. What might I have done wrong?

If I add the prefix to the host field of the configuration, assets seem to be loaded correctly. However, then the runner no longer works since this adds the prefix twice.

Some further investigation leads me to believe this is a problem that occurs when you try to serve jsbin behind a TLS terminating proxy, and also mounted at a path different from /. Let me provide some context by describing our setup, which is not particularly exotic I think.
Basically, we have an load balancing proxy sitting as the external facing host. This proxy is just a server that terminates TLS and passes on the request to a backend instance hosting whatever service you're looking for – in this case, JSbin. Thus, JSbin is served over http.
Now, the host we run jsbin on is shared with other services and applications as well, so the proxy doesn't just load balance, it also provides some very rudimentary routing (i.e. if the path begins with x, route to service y.) These services are served under different paths, not different subdomains. Thus, we serve JSbin from a specific path, e.g. /jsbin.
So what follows is:

We need to serve JSbin over http, but tell it that it's running behind a proxy that serves things over https
We need to server JSbin from a path other than /

I think this combo is what makes prefixes break. You can do one or the other, but not both at the same time given the current code I think. I've narrowed the issue down to the url and urlForStatic functions in lib/helpers.js. Specifically these lines in url, and these lines in urlForStatic. Essentially, when the secure flag is set – which is a side effect only of X-Forwarded-Proto being sent by the TLS terminating proxy btw, which is another issue – the root only considers the host in both cases, and forgets about the prefix. Simply doing root += app.get('url prefix') after it's been set to the https variant of the host, seems to fix it. I reckon both of these functions could probably be refactored to be less brittle however.
We need to fix this, so we're going to implement this in our fork. Happy to open a PR for it if you like?


OnClick stops being called after rapidly clicking

I have a few cases where onClick stopped being called. This case, where I rapidly click the ZoomableAsyncImage is the one I can reliable reproduce.
I have a onClick functionality that enables immersive mode. In some weird cases it gets stuck in this mode.
  code if relevant
 ZoomableAsyncImage(
                    contentScale = ContentScale.Fit,
                    model = image,
                    imageLoader = imageGifLoader,
                    contentDescription = null,
                    onClick = {
                        showTopBar = !showTopBar
                        systemUiController.isSystemBarsVisible = showTopBar

                        // Default behavior is that if navigation bar is hidden, the system will "steal" touches
                        // and show it again upon user's touch. We just want the user to be able to show the
                        // navigation bar by swipe, touches are handled by custom code -> change system bar behavior.
                        // Alternative to deprecated SYSTEM_UI_FLAG_IMMERSIVE.
                        systemUiController.systemBarsBehavior = BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE
                    },
                    modifier = Modifier.fillMaxSize(),
                )

(v1.0.0-alpha02)
https://github.com/MV-GH/jerboa/blob/feb5954c6c0d96763aef4822b4623a66c620713e/app/src/main/java/com/jerboa/ui/components/imageviewer/ImageViewerActivity.kt#L153

The video below illustrates the problem:
In the first part I show the correct behaviour.
In the second part, It attempt to reproduce the problem. You cant really see it but i am rapidly clicking until it gets stuck.
In the third part I am stuck in immersive mode.
https://github.com/saket/telephoto/assets/67873169/93ae68b3-fb04-454b-9fe7-d0b040a3e0d0

Are you able to reproduce this in the sample app by any chances? I can't seem to run into this. I'll try building your project to see if something else is affecting this.

I can no longer reproduce this, you can close it. I think it was because i was using that old version.

Awesome, thanks for confirming.


#1241 - Possible solution for 2-click re-select on multi-select for Select Menu Component

Overview
The isSelected(item) && isMultiSelect condition on line 142 of OptionsList was causing the user to need to click twice to re-select an option on multiselect (per issue #1241). I could not find any example of where this condition was used, but removing it solved this issue.
Screenshots (if applicable)
N/A
Documentation

[ ] Updated Typescript types and/or component PropTypes
[ ] Added / modified component docs
[ ] Added / modified Storybook stories

@derekvelzy thanks for submitting this!! I'm going to close it out in favor of the more complete refactor in the other PR, but thank you for the contribution and pointing out a solution :)


[BUG] MultiSig creation failed: ENS is not supported on network private

Environment
Operating System: Win10
Celo Terminal Version: 1.18.2
Bug description
I tried to create a new MultiSig using the 'Create MultiSig Account' in the Accounts tab.
I keep getting this error: 'ENS is not supported on network private' and the creation systematically fails, consuming the fee.
I tried swapping the owners' addresses but it does not seem to make a difference.
Looks like this is a known issue in the Ethereum community  but I cannot find any trace of it in Celo dapps.

The tx initiating the smart contract goes through (e.g. here) but when I try to add the multisig by importing the contract's address, I run into an error code stating the execution was reverted: 'execution reverted: No Implementation set'
Can someone look into this and give a noob some help?

The "ENS is not supported on network private" is just a red-herring. Have pushed a fix that will make those errors go away.
You must be getting some other error in creation. I just tried it out and it is working fine from my account. Is there anything special about the account you are using to create the multisig account from?

Just updated the app. It works great. No more errors and creation successful.
Thank you for the patch 👍

Is there anything special about the account you are using to create the multisig account from?

Nothing particular really. I ended up creating a multisig on Safe.global and it went smoothly.


Referencing missing column

@supabase/supabase-js": "^2.39.0" using Supabase CLI to [generate the types]   "supabase": "^1.123.0"
Query the same referenced table multiple times work but give you a Typescript error as it expect an array.
to reproduce you can use the datasource (doc example)
create table
 users (id int8 primary key, name text);

 create table
   messages (
     sender_id int8 not null references users,
     receiver_id int8 not null references users,
     content text
   );

 insert into
   users (id, name)
 values
   (1, 'Kiran'),
   (2, 'Evan');

 insert into
   messages (sender_id, receiver_id, content)
 values
   (1, 2, '👋');

query :
const { data, error } = await supabase
  .from('messages')
  .select(`
    content,
    sender_id(name),
    receiver_id(name)
  `)

now using data[0].sender_id.name  will work but will give you an typescript error.  "sender_id: SelectQueryError<"Referencing missing column name">[];
Bypass temporary  solution :
type patch = { content: text; sender_id: Tables<"users">; receiver_id: Tables<"users">}[];
const { data, error } = await supabase
  .from('messages')
  .select(`
    content,
    sender_id(name),
    receiver_id(name)
  `).returns<patch>()

Is there any PR which fixes those? I recently updated supabase-js version and generaetd new types and got similar issue, some database fields are not recognized anymore.

Same problem for me even when switching to 2.39.3

i got the same error

Same here!

same here...

still an issue

Same here. Weirdly, this works...
supabase
  .from('selection_assets')
  .select(
    `
    id,
    comment,
    order,
    created_at,
    asset: assets (
      id,
      name,
      is_listed
    )
  `,
  )
  .eq('selection_id', selectionId)
  .single();

and this doesn't...
supabase
  .from('selections')
  .select(
    `
    *,
      client: client_id(id)
    `,
  )
  .eq('id', selectionId)
  .single();

still an issue

Got the issue too

Same issue

Any solution?

I have the feeling it depends on in which direction or on which side the relation is defined. Still need to verify this.

@ohrrkan As mentioned in the documentation here:
https://supabase.com/docs/reference/javascript/select
(example for 'Query referenced tables through a join table')
We can infer types by doing this:
// To infer types, use the name of the table (in this case `users`) and
// the name of the foreign key constraint.
const { data, error } = await supabase
  .from('messages')
  .select(`
    content,
    from:users!messages_sender_id_fkey(name),
    to:users!messages_receiver_id_fkey(name)
  `)

this works for me
  const { data, error } = await db
    .from("posts")
    .select(
      `
      id,
      content,
      user:users(
        id,
        full_name,
        handler,
        avatar
      )
      `
    )

user is the column name in posts
users is the name of foreign table.

A fix has been released in supabase-js v2.46.0. I'm closing this issue, but feel free to reopen if you encounter any further errors.

Same issue

@KouroshBhl @Gabriel-Volpini
We had to revert the fix in 2.46.1 as we had some unexpected breaking changes due to the type rework.
However, we did released a new version as a "release candidate", and we are currently collecting feedback about it: https://github.com/orgs/supabase/discussions/30324
Please give 2.46.2-rc.3 a try, and don't hesitate to report back any remaining error with the debugging informations mentioned in the discussion. In the meantime I reopen this issue and will be closing it when this release candidate land on the main release channel (which should happen in December).

Happy to announce that we just released v2.47.8 that include the typing inference rework which should fix this issue.


active_op_id needs to be shared

store widget data corresponding to docks
Purpose of PR?:
Fixes #2322
including tests

@matrss something more missing or should be improved?

I still think we shouldn't duplicate this attribute everywhere. What is wrong with exposing a reference to the mainwindow on the topview? Then it would be possible for the MultipleFlightpathControlWidget to just access self.ui.mainwindow.active_op_id, or something like that.

Alternatively, make the topview's active_op_id a getter/@property for the one from the mainwindow so that it can never be out of sync. Depends on how much if the mainwindow we want to have accessible everywhere.

@ReimarBauer and I talked about this a bit this morning and we came to the conclusion that the PR should be merged as-is, but we need to take a look at things like this in the future and make an effort to refactor these things and clean up some of it.


PSR2 compatibile codestyle

This does nothing special except Class/Methods/Variables are renamed to be PRS2 compatible

@yswery can you make a tagged release before this merge so we don't break anything. And later we can publish new version from master branch

PR #56 has incorporated these changes.


BUG: area_mode="range" in viz._plot_psd is wrong.

As pointed out by #6500, the changes done in #6451 broke average plotting when area_mode="range." This fixes that, and also sets linewidth=0.5, and passes along the line_alpha parameter to plot.

@jshanna100 does this fix the titles? I don't see how it could from the code but maybe I'm missing it.

thx @jshanna100


Reply to bridge bot?

Is your feature request related to a problem? Please describe.
I think this is a new feature request. let me describe more.
I have gitter and telegram bridged. peopel (@user_one) sends a message (hello) in gitter. I will see:
Bot                                      admin
**user_one**: hello

now I am in telegram, if I hold on this message. and press reply. insert hello too. and send.
people in gitter will see:
Bot:
**wsdjeg**: hello too(re @Bot: user_one: hello)

Describe the solution you'd like
what I want in gitter is:
Bot:
**wsdjeg**: hello too(re @user_one: hello)

Duplicate of #638?

Duplicate of #638?


parquet

yazi --debug output
WARNING: `exec` will be deprecated in the next major version v0.3 and replaced by `run`.

Please replace all `exec = ...` with `run = ...`, in your `yazi.toml` and `keymap.toml`.

---
Add `disable_exec_warn = true` to your `yazi.toml` under `[headsup]` to suppress this warning.

Yazi
    Version: 0.2.5 (Homebrew 2024-04-23)
    OS: macos-aarch64 (unix)
    Debug: false

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect: Kitty

Adaptor
    Adaptor.matches: Kitty

Desktop
    XDG_SESSION_TYPE: None
    WAYLAND_DISPLAY: None
    DISPLAY: None

SSH
    shared.in_ssh_connection: false

WSL
    /proc/sys/fs/binfmt_misc/WSLInterop: false

Variables
    SHELL: Some("/opt/homebrew/bin/fish")
    EDITOR: Some("nvim")
    ZELLIJ_SESSION_NAME: None
    YAZI_FILE_ONE: None
    YAZI_CONFIG_HOME: None

file(1)
    Version: Ok(Output { status: ExitStatus(unix_wait_status(0)), stdout: "file-5.41\nmagic file from /usr/share/file/magic\n", stderr: "" })

Text Opener
    default: Some(Opener { run: "$EDITOR \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block: Some(Opener { run: "$EDITOR \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

tmux
    TMUX: false

Ueberzug++
    Version: Err(Os { code: 2, kind: NotFound, message: "No such file or directory" })

--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/Users/kang/.local/state/yazi" directory.

Please describe the problem you're trying to solve
I am wondering if yazi could support parquet preview as table

Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
preview parquet as table like preview csv,

not sure how to implemnt this, but duckdb could preview parquet very quick
Additional context
No response
Validations

[X] I have searched the existing issues
[X] The latest nightly build of Yazi doesn't already have this feature

No plans to have it built-in, as that would require pulling in an additional dependency, but you should be able to implement it as a custom previewer via https://github.com/chhantyal/parquet-cli or https://github.com/manojkarthick/pqrs
Doc https://yazi-rs.github.io/docs/plugins/overview#previewer


Message inheritance is broken

Hi, after I upgraded globalize to 1.0.0-alpha.16, the inheritance feature as fixed in #266 and mentioned in https://github.com/jquery/globalize/blob/master/doc/api/message/load-messages.md#messages-inheritance seems to be broken. I get the following error if I try to call formatMessage() method on a locale for which no message was loaded
Error: E_MISSING_MESSAGE_BUNDLE: Missing message bundle for locale `de`.
    at createError (/home/devang/tmp/Globalize/node_modules/globalize/dist/globalize.js:105:10)
    at validate (/home/devang/tmp/Globalize/node_modules/globalize/dist/globalize.js:118:9)
    at validateMessageBundle (/home/devang/tmp/Globalize/node_modules/globalize/dist/globalize/message.js:1705:2)
    at Globalize.messageFormatter.Globalize.messageFormatter (/home/devang/tmp/Globalize/node_modules/globalize/dist/globalize/message.js:1822:2)
    at Globalize.formatMessage.Globalize.formatMessage (/home/devang/tmp/Globalize/node_modules/globalize/dist/globalize/message.js:1855:14)
    at Object.<anonymous> (/home/devang/tmp/Globalize/i18n.js:19:31)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)

This is working fine in version 1.0.0-alpha.15

Thanks for filing this issue. I have updated the documentation accordingly.
Short answer: you should let Globalize know de is a valid bundle. In case all its messages are going to be inherited, define it by using an empty set.
Globalize.loadMessages({
  de: {}
});

Long answer: Although the bundle inheritance chain is predefined independent of any loaded data (e.g., en-IN chain is: en-IN ➡ en-GB (via parent locale) ➡ en-001 (via parent locale) ➡ en (via truncation)  ➡ root), the bundle lookup depends on the available loaded bundles (e.g., the bundle for zh-TW could be either zh-Hant or zh-Hant-TW depending on the available bundles). See also https://github.com/rxaviers/cldrjs/blob/master/doc/bundle_lookup_matcher.md#implementation-details.
Please, just let me know if having to load the empty set in that case turns out to be a problem.


liftoff 2x / v8flags 2x released

Heya, this is just a friendly note to let you know that a new version of Liftoff and some of the dependencies commonly used in conjunction with it have been released. This release adds better support for situations where your user's configuration files are written using features behind a v8 flag (e.g. --harmony). Windows users and io.js users should see less issues if you upgrade!
Some helpful links:
https://github.com/tkellen/node-liftoff/blob/master/UPGRADING.md#100---200
https://github.com/tkellen/node-v8flags/blob/master/README.md#example
https://github.com/tkellen/node-hacker/blob/master/bin/hacker.js#L10-L14
Thanks!

Thank you for taking the time to let me know @tkellen! However, I am going to close this issue, since I have already removed Liftoff from the V2 dependencies.


Connection backoff interop test client and server

This is based on #2590 which is based on #2477. They need to be merged first.

Yang, can you tell me which commits are unique? Then I can just review those before the others get reviewed...

Never mind; I'll just figure it out by authorship..

Sorry I did not make it clear, just the last commit for this PR. I squashed all commits into one. The other two are from #2590

The parameters are from https://github.com/grpc/grpc/blob/master/doc/connection-backoff.md except kTransmissionDelay which is chosen to cover network delay between the test client and server. It was chosen generously and might be too large.

Ok, I understand. In an ideal world, that 100 ms would be too large for sure on localhost, but in the real world where we might encounter the occasional context switch, I'm afraid that we're stuck with it. So, LGTM on this commit. Let me know when the other PRs get merged.

Status update: I'll wait for a minor code change on CV usage and then can merge if you're ready. The CV usage issue will be explored at a later date under issue #2714 .

Fixed, thanks for the discussion. Would you like to take the parent PR as well? #2590

Conflicts!

Gone!

Green enough?


ir: Cleanup name duplication in aliases and named types.

It's just dumb.
r? @fitzgen

@bors-servo r=fitzgen

:pushpin: Commit a46971c has been approved by fitzgen

:zap: Test exempted - status


SPIRVProducerPass refactor - phase2.2

Removed pre-pass collection of Constants (caused some reorder in tests)

Collect Capabilitys on-the-fly

This is the last refactor phase (for now). This enables easy implementation for extensions (e.g. SubGroups)

Enhancement for clspv issue #545

Testing windows now.. strange that linux passed the same tests.

@alan-baker please review latest. This is where I wanted to go, cleans up alot and makes operands more obvious.

please hold off, 1 more debug fix.

Ok, all clear.


(C#) Hard to tell that a channel has been shut down

I'm writing tests to make sure I'm shutting channels down properly. I'd expect the State enum to have a value for Shutdown, but I don't see one... but requesting the state after shutting the channel down throws an exception ("Safe handle has been closed").

(Suggest assigning @jtattermusch)

I think exposing a CancellationToken as suggested here might also be useful - as suggested here:  #6311


Apps status needed

Description of the new feature / enhancement
Need a command to check apps status, and then we can know upgrade its
Thank you.
Proposed technical implementation details
No response

I believe the command you are looking for is winget upgrade.
It will show any applications with upgrades available via any configured sources.
winget upgrade                                                        in powershell at 07:45:32
Name                                               Id                                Version       Available     Source
-----------------------------------------------------------------------------------------------------------------------
GitHub Desktop                                     GitHub.GitHubDesktop              2.9.15        3.0.0         winget
Windows Package Manager Manifest Creator           Microsoft.WingetCreate            <IP_ADDRESS>       <IP_ADDRESS>       winget
Oh My Posh                                         JanDeDobbeleer.OhMyPosh           7.74.0        7.79.0        winget
VLC media player                                   VideoLAN.VLC                      3.0.16        <IP_ADDRESS>      winget
Microsoft Visual C++ 2015-2019 Redistributable (x… Microsoft.VC++2015-2019Redist-x86 14.28.29914.0 14.29.30139.0 winget
Microsoft Visual C++ 2015-2019 Redistributable (x… Microsoft.VC++2015-2019Redist-x64 14.28.29914.0 14.29.30139.0 winget
Microsoft Teams                                    Microsoft.Teams                   <IP_ADDRESS>74    <IP_ADDRESS>63   winget
Microsoft Visual Studio Code                       Microsoft.VisualStudioCode        1.66.2        1.67.0        winget
ScreenToGif                                        NickeManarin.ScreenToGif          2.36          2.37          winget
9 upgrades available.


Display total number of accounts on dashboard

Problem
The total number of Hedera accounts is not easily visible.
Solution
Add total accounts field when viewing accounts tab, https://hashscan.io/#/mainnet/accounts.
Alternatives
No response

The explorer currently has no way to retrieve that information from the mirror-node REST API.

See following mirror-node enhancement request for some business metrics: #759


Administrator back-end

Should allow administrators to:

Add users who pledged for a book
Change user details (add e-mail addresses to receivers who did not pledge themselves)
Add Books
Bulk-add BookInstances with codes and batch

Already present, except #20


[Button] Use correct classnames in adding margin-left

Closed Issues
n/a
Description
Previously, the following line was copy-pasted in each button style section:
.ui.buttons:not(.vertical) > .basic.primary.button:not(:first-child) {
  margin-left: -1px;
}

(copied from the static semantic-ui-css)
however, it appears that the button style (primary, secondary, positive, negative) was not updated in each usage. I've changed this so now this rule is applied to the style of the section the rule is contained in.
I hope this makes sense - I've also foregone the testcase section as this is such a minor fix.
Testcase
n/a

Good catch!
I adopted your fix for upcoming Fomantic-UI 2.7.3 by https://github.com/fomantic/Fomantic-UI/pull/537

Ok to close this?


changeset status: allow absolute paths in --output

Affected Packages
@changesets/cli
Problem
Because of https://github.com/changesets/changesets/issues/1020, I decided that I'll print the JSON output of changeset status into a temporary file (made with tmp-promise library). The problem is that if you pass an absolute path to --output flag, it treats it like a relative path.
michal@dzieni strato-agent % npx changeset status --output="/a/b/c/d.json"
🦋  error [Error: ENOENT: no such file or directory, open '/Users/michal/Projects/strato-agent/a/b/c/d.json'] {
🦋  error   errno: -2,
🦋  error   code: 'ENOENT',
🦋  error   syscall: 'open',
🦋  error   path: '/Users/michal/Projects/strato-agent/a/b/c/d.json'
🦋  error }

Proposed solution
#1020 would be good enough for me, but ideally the tool should just support the absolute paths, unless there's a security reasoning behind it.

This could be improved here:
https://github.com/changesets/changesets/blob/e02a0c4b7ec869d21b10495138d9fb193b213917/packages/cli/src/commands/status/index.ts#L56-L62


Can't establish connection with rtmp server

Hi there !
I'm trying to setup a small stream server with nginx and OBS Studio. Stream is ok with VLC. But I can't get it working with MediaElement. Here is my code:
<html>
<head>
    <title>Mediaelement test</title>
    <meta charset="utf-8">
    <script src="https://code.jquery.com/jquery-3.2.1.slim.min.js"></script>
    <script src="./mediaelement/build/mediaelement-and-player.min.js"></script>
    <link rel="stylesheet" href="./mediaelement/build/mediaelementplayer.min.css"/>
    <script>
        $(function () {
            $('.live-player').mediaelementplayer({
                pluginPath: './mediaelement/build/',
                renderers: ['flash_hls'],
                success: function (mediaElement, domObject) {
                    mediaElement.setSrc('rtmp://<server-ip>:1935/live/test');
                    mediaElement.load();
                    mediaElement.play();
                },
            });
        });
    </script>
</head>
<body>
<video class="live-player" style="width:100%;height:100%;" width="640" height="360" controls="controls" preload="none"></video>
</body>
</html>

No errors in console but a black player. What am I doing wrong ?

@nicolaspetitjean rtmp and hls are two different protocols. If you want to use an rtmp stream, you need to use a renderer which supports it see: https://github.com/mediaelement/mediaelement/blob/master/docs/usage.md#use-renderers


add support for the text highlighting

This feature will help to highlight text

property name is highlightColor

This feature will help to highlight text
* property name is `highlightColor`

For a reference can you please also add the link to the specific documentation page which i shared with you.


ki --autonomous #error

It gives me a SyntaxError: Unexpected token ;
r("mori.mutable.disj.fn",ge.K);;return this.mori;}.call({});});
                                                           ^

Can you share a snippet that reproduces the error? It's working for me.

I pushed a datomiki ki-a-mori branch to point to the commit where I realized it wasn't working.  First I thought it was a problem because I had ki npm link-ed and forgot to npm install, but it builds without errors.  Do npm run build to confirm.  Running node datomiki.js produces:
/Users/om/Dev/datomiki/datomiki.js:924
disj.f2",ge.a);r("mori.mutable.disj.fn",ge.K);;return this.mori;}.call({});});
                                                                          ^
SyntaxError: Unexpected token ;
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:427:25)
    at Object.Module._extensions..js (module.js:462:10)
    at Module.load (module.js:339:32)
    at Function.Module._load (module.js:294:12)
    at Function.Module.runMain (module.js:485:10)
    at startup (node.js:112:16)
    at node.js:863:3

I get the same error with node 0.10, 0.12, and io.js - it otherwise runs fine on all three.

I ran into an npm bug - if mori is a devDependency of a project that has ki as dependency, npm doesn't install  node_modules/ki/node_modules/mori and ki can't can't build with --autonomous option because mori isn't found where expected.  Getting around this didn't fix the issue.

Sorry for the wait, I couldn't reproduce the error until I noticed that you were using source maps: the error showed only when -a was used in conjunction with -s. It's fixed now in master, I'll release shortly.


[dunfell][gatesgarth][hardknott][master] {melodic} Upgrade 2021-04-27 release

https://discourse.ros.org/t/new-packages-for-melodic-2021-04-27/20088
https://discourse.ros.org/t/new-packages-for-melodic-2021-05-17/20418

Remaining issues:
{noformat}
Summary: 3 tasks failed:
virtual:native:/jenkins/mjansa/build/ros/ros1-melodic-dunfell/meta-ros/meta-ros1-melodic/generated-recipes/ros-comm/rosout_1.14.11-1.bb:do_configure
/jenkins/mjansa/build/ros/ros1-melodic-dunfell/meta-ros/meta-ros1-melodic/generated-recipes/move-basic/move-basic_0.4.1-1.bb:do_compile
/jenkins/mjansa/build/ros/ros1-melodic-dunfell/meta-ros/meta-ros1-melodic/generated-recipes/jsk-recognition/checkerboard-detector_1.2.15-1.bb:do_compile
{noformat}
The rosout is from WIP commit to allow building xacro-native (called by flir-ptu-description during build).

Pushed to other branches as well:
130cc3dff..2ae69f904  dunfell -> dunfell-next
bfafca29b..fbc5b8fae  gatesgarth -> gatesgarth
bfafca29b..fbc5b8fae  gatesgarth -> gatesgarth-next
0e78198a1..4aea9e120  hardknott -> hardknott
0e78198a1..4aea9e120  hardknott -> hardknott-next
0e78198a1..4aea9e120  master -> master
0e78198a1..4aea9e120  master -> master-next


[v2] Auto-generate configuration documentation

We want to employ a schema-first approach to configuration:

define a schema for configuration structures first
use code generator to create types in Go
automatically generate documentation from the schema

References:

Print active configuration (unresolved: Print final configuration OTEL #5223)
https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27003
Config documentation

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/configschema/docsgen/README.md
https://www.otelbin.io/ https://github.com/dash0hq/otelbin/issues/179

https://github.com/nimbushq/otel-validator

@yurishkuro how should we get started on this?

Can't, blocked by upstream issues


Can't login when langauge changed

When the language of the default admin account is changed, I can't login
Even if I through another admin account change the language back to English, I can't login
But if I create another user, and change the language, I can perfectly login with that account

The problem occurs only when the language is changed for a specific account. Because when I change the language through config.php it still works.

Ho you were able to change the language via the browser?
I'm trying to do that, but I can only choose English.


Display name

We should add display name and allow users to search for players either using name or display name.
Our current use case is that everybody's name is their initials. This way we wouldn't have to request initials every time we play with someone new. It would also ensure people do not make typos. Azure DevOps assignment could be an inspiration.

Closed by #36


Authme BUG big/small characters. Fix fast, help fast.. Thanks.

Hi,
I need help please help me
How to prevent join with big/small characters?
TOPIC: https://www.spigotmc.org/threads/help-me-fast-please-small-and-large-characters-the-name-when-do-join.79653/

Wrong repo :/ Can you re-open this here :
https://github.com/Xephi/AuthMeReloaded

Already solverd


Add support for argument definition

The help template contains just [arguments...], but it would be very useful if it was possible to define those arguments (optional arguments including) and see them in help, i.e. to se ARG1 ARG2 [ARG2] in the usage if ARG2 is optional instead of just [arguments...].

Rolling this into #140


Better Modbox Support (Import mode)

Add Detune (Song Detune), Filter (EQ/Envelopes), and Effect (Vibrato) support

I also need to add support for Modbox's panning (ipan)

support for Modbox Fixed's ipan was added in the latest commit, however the other three listed still need to be added


Allow users to upgrade their iOS engines without removing their edits to the Xcode project

cc @devoncarew

LGTM

some late comments :)

Thanks. Will fix these in the morning.


picolisp: 19.12 -> 20.6

Motivation for this change
New version released
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Seems like we are already at that version:
https://github.com/NixOS/nixpkgs/pull/92403


[EventGrid] Update pylint/mypy

Look at test-weekly warnings and update code accordingly

krista has autogen issues for this :)


pull request for e2e test at 11/05/2016 11:26:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Filter throws exception when some columns are hidden

(Original issue 37 created by None on 2014-06-23T14:43:33+00:00)
What steps will reproduce the problem?
1. set up a table; hide some columns
2. set up filter header as normal
3. add a separate filter; the separate filter causes the crash

What is the expected output? What do you see instead?

filter the table; instead, it throws an exception.

What version of the product are you using? On what operating system?

5.1.1

Please provide any additional information below.

// create table and TableFilterHeader in the usual way
JTable table = ....
 TableFilterHeader filterHeader = new TableFilterHeader(_table, AutoChoices.ENABLED);
filterHeader.setFilterOnUpdates(true);

//now add an additional, separate filter to the header
filterHeader.addFilter(RowFilter.regexFilter("ALICE");

// the separate filter cause an exception b/c some columns are hidden (see Entry.getStringValue(...)

// if the visible columns are inserted into the regex filter, the exception is avoided
filterHeader.addFilter(RowFilter.regexFilter("ALICE",visibleColumnsIntArray);

Original issue reported on code.google.com by elisebotworld.ww on 2014-06-23 14:43:33

(Original issue 37 last updated on 2015-04-26T00:22:40.773211+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by {u'display_name': u'coderazzi coderazzi', u'account_id': u'557058:790eb198-2ae4-49b4-b920-8d654aa86b3f'} on 2014-06-25T11:26:56+00:00)
Hi, I was checking the code that you provided, but addFilter requires an IFilter instance,
not a RowFilter.
I still get an exception, as you point out, when I create an IFilter wrapping the RowFilter,
doing:

        filterHeader.addFilter(new Filter(){
    		RowFilter r = RowFilter.regexFilter("ALICE");
        	@Override public boolean include(Entry entry) {
        		return r.include(entry);
        	}
        });

Is this the code that you have?

Original issue reported on code.google.com by coderazzi on 2014-06-25 11:26:56

(Original comment by {u'display_name': u'coderazzi coderazzi', u'account_id': u'557058:790eb198-2ae4-49b4-b920-8d654aa86b3f'} on 2015-03-18T22:26:18+00:00)
Solved on 5.1.2

Original issue reported on code.google.com by coderazzi on 2015-03-18 22:26:18

(Original comment by {u'display_name': u'coderazzi coderazzi', u'account_id': u'557058:790eb198-2ae4-49b4-b920-8d654aa86b3f'} on 2015-04-26T00:22:40.782784+00:00)
Already resolved (previously, before migrating to BitBucket)


Unable to convert existing Workflow to WorkflowTemplate in v3.0.7

Summary
What happened/what you expected to happen?
Converted an existing Workflow to a WorkflowTemplate. Referencing the new WorkflowTemplate in another Workflow resulted in volume $VOLUME_NAME not found in workflow spec error. Since the original Workflow succeeded, I expected the WorkflowTemplate to succeed as well (based on this section from the docs)

v2.7 and after

In v2.7 and after, all the fields in WorkflowSpec (except for priority that must be configured in a WorkflowSpec itself) are supported for WorkflowTemplates. You can take any existing Workflow you may have and convert it to a WorkflowTemplate by substituting kind: Workflow to kind: WorkflowTemplate.

Diagnostics
What Kubernetes provider are you using?
Discovered on `EKS` cluster, reproduced with local `kind (kind.x-k8s.io/v1alpha4)` cluster.

What version of Argo Workflows are you running?
v.3.0.7 - EKS
v.3.1.0 - kind

What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary
PNS for the kind cluster

Did this work in a previous version? I.e. is it a regression?
Not tested with other versions.
cat empty-volume-wf.yaml

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: empty-dir-
spec:
  volumes:   <--- NOTE LOCATION
    - name: out
      emptyDir: { }
  entrypoint: main
  templates:
    - name: main
      container:
        image: argoproj/argosay:v2
        command: [sh, -c]
        args: ["cowsay hello world | tee /mnt/out/hello_world.txt"]
        volumeMounts:
          - name: out
            mountPath: /mnt/out
      outputs:
        parameters:
          - name: message
            valueFrom:
              path: /mnt/out/hello_world.txt
---
cat bad-empty-volume-wft.yaml

apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: bad-empty-dir-wft
spec:
  volumes:
    - name: out
      emptyDir: { }
  entrypoint: main
  templates:
    - name: main
      container:
        image: argoproj/argosay:v2
        command: [sh, -c]
        args: ["cowsay hello world | tee /mnt/out/hello_world.txt"]
        volumeMounts:
          - name: out
            mountPath: /mnt/out
      outputs:
        parameters:
          - name: message
            valueFrom:
              path: /mnt/out/hello_world.txt
---
cat bad-ref-template.yaml

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: bad-empty-dir-wft-
spec:
  entrypoint: main
  templates:
    - name: main
      steps:
        - - name: hello-world
            templateRef:
              name: bad-empty-dir-wft
              template: main
---
cat good-empty-volume-wft.yaml

apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: good-empty-dir-wft
spec:
  entrypoint: main
  templates:
    - name: main
      container:
        image: argoproj/argosay:v2
        command: [sh, -c]
        args: ["cowsay hello world | tee /mnt/out/hello_world.txt"]
        volumeMounts:
          - name: out
            mountPath: /mnt/out
      volumes:  <-- MOVED UNDERNEATH templates
        - name: out
          emptyDir: { }
      outputs:
        parameters:
          - name: message
            valueFrom:
              path: /mnt/out/hello_world.txt
---
cat good-ref-template.yaml

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: good-empty-dir-wft-
spec:
  entrypoint: main
  templates:
    - name: main
      steps:
        - - name: hello-world
            templateRef:
              name: good-empty-dir-wft
              template: main

Then run
kubectl create -f empty-volume-wf.yaml (succeeds)

kubectl create -f bad-empty-volume-wft.yaml
kubectl create -f bad-ref-template.yaml (fails)

kubectl create -f good-empty-volume-wft.yaml
kubectl create -f good-ref-template.yaml (succeeds)

Screenshots

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@edhjer  This is by design. WorkflowTemplate Spec level fields will not referred/copied to workflow if  workflow refers ONLY templates using templateRef. When workflow has templateRef referring workflowtemplate's template, controller will only copy/refer all Template scope fields.

Thanks for following up @sarabala1979, that design choice makes sense to me. However, the above blurb from the docs seems incorrect then, based on what you're saying.


Remove bad dependency, make build pass again.

thanks! we're building with mvn clean deploy (and i usually test things locally with mvn clean package), and it looks like that doesn't run all the goals that travis' mvn install does. is there a better goal I should be using? or do i just need to manually run dependency:analyze too?

You can change the phase of the dependency plugin to prepare-package which I think is helpful


Web Chat (or more fundimental) error after changing an LG template

Describe the bug
After changing the template and restarting the bot, the bot is responding with the previous version of the template.
Version
            Version:  1.3.1-nightly.219396.61c944a
            Electron: 8.2.4
            Chrome: 80.0.3987.165
            NodeJS: 12.13.0
            V8: 8.0.426.27-electron.0

Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create an echo bot.
Change the Send a response activity template in the Unknown intent trigger to:	-  ```
	You said:
	> ${turn.activity.text}
	> 1. **Type**: ${turn.activity.type}
	> 1. **Value**: ${turn.activity.value}
	```

Restart the bot and test it in Web Chat. (This part works as expected.)
Change the template to:	-  ```
	You said:
	> ${turn.activity.text}
	- **Type**: ${turn.activity.type}
	- **Value**: ${turn.activity.value}
	```

Restart the bot and text it in Web Chat.
Error: I got this output (which does not match the updated template.)

Expected behavior
The Markdown should render correctly.

The numbered list should be a bullet list.
The list should be outside the blockquote.

for example:
You said:

${turn.activity.text}

Type: ${turn.activity.type}
Value: ${turn.activity.value}

Additional context

Secondary error: I should not need to restart Web Chat to see the changes in the template if the resource manager is working correctly. It should notice changes in the resource files and reload them on the fly. (A baked in feature of the SDK.)

I believe this has to do with how the LG is structured.  I have seen the resource manager work for LG in the current runtime intermittently (where I can update some LG and immediately see a change in the emulator), even though it never works for dialogs.  Right now we are expecting the new runtime to be updated so that the resource manager correctly refreshes dialogs / language files on update as per a recommendation from @tomlm.  Given this is related to the current runtime, I don't anticipate we would fix the existing behavior ahead of replacing it in a few weeks in R13 and so I will close this issue.


Delay font texture update, until draw is called. Rasterize glyphs during shaping.

Should increase new font loading (and maybe startup times), font variation changes and rendering text with the glyph that was not used before. Instead of updating the texture when each new glyph is encountered, all glyphs updates are processed at once, and only when trying to draw.
Substantially, decreases the number of times font texture is uploaded to GPU. For Project Manager opening from 100 to 4. And from 160 to 38 when opening simple project with some extra fonts used.

Thanks!


Send CPU usage to metron client

Related story in the Garden backlog: https://www.pivotaltracker.com/story/show/159827961
Send container CPU usage data to the new metron client SendCPUUsage method. Note that the cpu entitlement is calculated in a very naive way. We have further stories in the Garden backlog to configure entitlement depending on operator configurable property.

Please do not merge this PR yet
We came across uin64 overflow that we need to investigate tomorrow

We have addressed the uint64 overflow, please proceed with reviewing and merging the PR
Thanks!

Thanks, @danail-branekov ! I asked a couple of questions in the line comments.

@emalm @jvshahid Looks like Danail has either responded to or changed code where comments were made. Is there more to be done on the Garden side?

@BooleanCat yes, left a comment at https://github.com/cloudfoundry/executor/pull/35#discussion_r219849028, but I'm not particularly comfortable with the bogus-metric approach here. If we're at the point where we need to figure out a real entitlement value, though, we should probably all sync up about what the desired operator experience should be, what the controls to support that behavior are, and in which components they should live to have an appropriate separation of concerns. /cc @julz

@emalm we moved the calculations in garden and updated the PR.
Note: When bumping executor in diego-release, you also need to bump the following submodules:

diego-logging-client with this PR included
garden to at least this commit

I'm really not certain that this approach is fundamentally different, and may be slightly worse: I see the same entitlement calculation is now moved into guardian in https://github.com/cloudfoundry/guardian/commit/54383ac770754155ecd667a398a9b385894ef1dd, but now we're also making a Garden API addition to transmit the CPU entitlement when I don't think we have a clear understanding that that's definitely the right place for the entitlement calculation to happen. I can see at least two potential trajectories so far:

We decide that the rep is actually the right place to compute this metric, in which case the entitlement field is an awkward vestigial wart on the Garden API;
We decide that guardian is the right place to compute this metric, in which case we still need to work out how the CF operator will ultimately arrange for the rep and/or garden-runc to translate the memory allocation into a corresponding CPU entitlement allocation.

Maybe the Garden team has already made that irreversible change on the Garden API by introducing this field in a final garden-runc release, so we're stuck with the wart even if the rep is the right place to compute the ongoing CPU entitlement.
Even then, we still have the issue that this metric will be misleading until we figure out at least a realistic default CPU entitlement strategy: I interpret the current formula to mean an entitlement of 1 CPU core per 1 GB of RAM allocation, which is wrong in practically every realistic environment if the desired default behavior is indeed to match a full memory allocation to a full CPU-entitlement allocation. I would like to start having the conversation now across the Diego and Garden teams (including with @julz and @BooleanCat specifically) about what CF operators will want the CPU allocation behavior to be and how we should divide responsibilities for the CPU allocations and enforcement thereof across these components to achieve that behavior.

@emalm totally agreed this metric doesn't make sense as stands, that's because it wasn't intended to :) -- for this story we just wanted to flow through a metric that has the property of being relative to memory -- it wasn't and isn't supposed to be the final metric (there's follow-on stories to improve it)
Let me say why we think it's best to land this early even though our goal is to iterate on this property to add better semantics. We very much want to avoid a Big Bang integration at the end, as happened with things like OCI mode, where we only find out problems when we've completed the feature, and where we aren't able to try the feature out "for real" until it's entirely done. More importantly, I very strongly suspect that in order to get this right we need to be able to actually play with it with real apps, and with operator input, as we develop the feature. Moving it in to garden (a) makes it easy to change (b) is almost certainly needed for implementation reasons to avoid clock skew problems anyway (I think we already talked about doing this, totally separately from the entitlements stuff?). I understand the concern about the intermediate metric not being perfect straight away, maybe it would be best to just mark the metric experimental for now to give us flexibility to yank and change it as we iterate? Let's chat at sync-up later?

Thanks, @julz. I got some more context from @jvshahid on the discussion y'all had about this earlier last week, and so that makes more sense about computing the cumulative entitlement Garden-side. Putting it on the Garden side also makes it easier to allow entitlement rates that vary over time (such as permitting an initial burst of entitlement at startup) easier to report.
Since the rep already has a feature-flag for this area of work in the form of containers.set_cpu_weight , maybe it would make sense for the executor to emit these new metrics only when that flag is enabled? Alternatively, we could achieve that opt-in behavior for the entitlement metric implicitly in Garden by having Garden compute it proportionally to the Weight field on the container's CPULimits, so it would be 0 if the rep hasn't opted into setting that value.
Also, if we can agree on what makes sense for Garden in terms of a default CPU entitlement policy, I think it would be straightforward to incorporate that into the Garden metric computation. Assuming that the desired behavior from operators is for containers to be able to consume "all" of both the VM RAM and the VM CPU (which we do need to validate further, of course), then the corresponding CPU entitlement per unit time is CPU cores * (RAM allocation / total RAM), and so the cumulative CPU entitlement is that times container uptime. But we've already structured the Garden container API to include that new CPU weight, so that should likely determine the proportional entitlement. For now, the implicit contract could be that Garden provides a total number of CPU entitlement units equal to the number of RAM megabytes it detects on the system. So translating the formula into those terms with the rep currently setting the container's CPU weight to its RAM allocation, the container's entitlement rate becomes CPU cores * (CPU weight / total CPU entitlement units).
Anyway, happy to continue sorting this out during the sync-up today, too!

Ok, for the record, after the sync-up today we determined that the cumulative entitlement computed in Garden will end up being proportional to the CPU weight set on the container anyway, so that will make the entitlement metric non-zero only when the rep opts into setting the CPU weight. That sounds like what we want, so I'm prioritizing this PR and https://github.com/cloudfoundry/diego-logging-client/pull/6 for us to pull in soon (as well as our chore to enable the CPU weight on warp-drive).
Also, getting the measurement timestamp from Garden probably means we can now address #30.


Does not take photo in Simulator

Hi, do you know why it does not take a photo in the simulator? It does not run the inside of the
camera2.takePhoto {
            Toast.makeText(v.context, "Saving Picture", Toast.LENGTH_SHORT).show()
            disposable = Converters.convertBitmapToFile(it) { file ->
                Toast.makeText(v.context, "Saved Picture Path ${file.path}", Toast.LENGTH_SHORT).show()
            }
        }

so it does not call Toast. I hope you can help me. Thanks!

@orkhanalizade I never tested the code on any emulator but only on some devices.
Please test on a physical device and then let me know if the toast shows or not.


Unit Test Django Client Login?

How can I unit test authentication on my Django app using python-social-auth?
I attempted this:
    self.c = Client()
    self.u = User.objects.create(username="testuser", password="password", is_staff=True, is_active=True, is_superuser=True)
    self.u.save()
    self.auth = UserSocialAuth(user=self.u, provider="Facebook")
    self.auth.save()
    self.c.login(username=self.u.username, password=self.u.password)

but this call to login returns False and the user is not authenticated

Thanks man!

@omab what if I really want to make sure that the integration of python social auth with my django project is working? I do not need to test that the social endpoints are working, but at least I would like to know that my site is doing right the request/reply cycle. How to go about this? Is there any example available?

@gonvaled +1


changes listed under Local History: Find Entry to Restore are fragmented across relative and absolute paths

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.71.2
OS Version: 12.6

Steps to Reproduce:

Create a dev container and open a git repo as a workspace foo
Clone a project into the workspace and add it as a submodule bar
Create/edit/delete files /foo/bar/baz
Command Palette -> Local History: Find Entry to Restore
Notice that baz is sometimes listed as both /foo/bar/baz and bar/baz, as shown for __init__.py below:
Select and view the histories for foo/bar/baz and bar/baz and notice that they are non-overlapping as shown for:
a. relative path listing (acvi_scverse/mypackage/__init__.py):
b. absolute path listing (/workspaces/scvi_work_pip/acvi_scverse/mypackage/__init__.py):

The logic for storing local history entries is actually quite simple: any time an editor is saved, we take the contents and store it under the full resource of the editor locally or in the remote machine if you are connected to a remote.
Is it somehow possible that you maybe edited the same file with different resources in 2 different editors?

Yeah that is possible if the resource that the editor ends up having encodes that IP. You can actually get a glimpse of the URI when you do this:

open the editor
from the command palette quick pick select "Log working copies"
open developer tools (from the help menu)
find in the "Console" tab output beginning with [Working Copies]
you should see an entry for your editor with the resource URI

The logic for storing local history entries is actually quite simple: any time an editor is saved, we take the contents and store it under the full resource of the editor input (for example file:///Users/bpasero/Development/Microsoft/vscode/src/vs/workbench/services/workingCopy/common/workingCopyHistoryService.ts) locally or in the remote machine if you are connected to a remote.

Thanks @bpasero,
Can you please provide a link for the documentation on this?
I don't have a local (MacOS 12.6) or remote (Ubuntu 20.04) ~/Development path.

Hm?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Held key when game loses focus

When a key is held and the game loses focus (IsActive becomes false), it's possible for the player to let go of that key. When that happens the Released() condition doesn't fire. It might be useful to consider the focus loss to be the same as letting go of the key.

There's another case to consider. When clicking away from the window, that click will trigger Held(). The fix should be the same as what's done in Pressed() with IsMouseValid.


Needs new theme

BlockLauncher's theme is old and its 2016 @zhuowei, Blockalauncher's theme should be changed

Fixed in latest beta.


Add mouse-over stats for Ancient Brews

Closes  #14838
Adds stats for the ancient brew.

This implementation is not right, as it does not take into account the boost cap the potion implements. #14566 implements the boost correctly.


Add test for Course Service

Helpful References to create tests:
https://blog.logrocket.com/unit-testing-nestjs-applications-with-jest/,
https://docs.nestjs.com/fundamentals/testing,
https://github.com/jmcdo29/testing-nestjs/tree/master/apps/mongo-sample/src

Can I work on this issue


not connected to DevTools

Hi @chilio ,
Thanks for your great work,
I am using your image since a month I am setting it up with a gitlab ci yml file.
But I keep getting the error
[WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
after the 3rd or 4th tests
and sometime it comes
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable or
Facebook\WebDriver\Exception\NoSuchDriverException: invalid session id
Any idea what can it cause I am having hard time trying but it does not work
Below is the log
System Chrome version: 70
System Chromedriver version: 2.43
Laravel Chromedriver version: 2.35
Chromedriver shipped with your Laravel installation is NOT compatible with this systems chrome version!
Don't worry, we are fixing this right now, so you will be able, to test your app anyway.
You can always read more about running tests with system inbuilt chromedriver in laravel-dusk-ci docs.
Scheduled start of inbuilt Chromedriver (2.43). Chromedriver will be ready soon...
$ start-nginx-ci-project
Starting ChromeDriver 2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d) on port 9515
Only local connections are allowed.
[1540405389.987][SEVERE]: bind() returned an error, errno=0: Cannot assign requested address (99)
 * Starting nginx nginx
   ...done.
$ php artisan dusk --colors --debug
Warning: TTY mode requires /dev/tty to be read/writable.
PHPUnit 6.5.13 by Sebastian Bergmann and contributors.

Test 'Tests\Browser\AdminLoginTest::testInvalidLogin' started
Test 'Tests\Browser\AdminLoginTest::testInvalidLogin' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_working' started
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_edit_modal_working' started
[1540405436.988][WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_edit_modal_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_language_modal_working' started
[1540405437.036][WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_language_modal_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_health_modal_working' started
[1540405437.080][WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_health_modal_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_allergy_modal_working' started
[1540405437.128][WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_allergy_modal_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_medical_history_working' started
[1540405437.175][WARNING]: Unable to evaluate script: disconnected: not connected to DevTools
Test 'Tests\Browser\ProfileComponentTest::test_profile_page_medical_history_working' ended
Test 'Tests\Browser\ProfileComponentTest::test_can_add_medication' started
Test 'Tests\Browser\ProfileComponentTest::test_can_add_medication' ended
Test 'Tests\Browser\UserRegistrationLoginTest::testLoginPage' started
Test 'Tests\Browser\UserRegistrationLoginTest::testLoginPage' ended
Test 'Tests\Browser\UserRegistrationLoginTest::testUserCanRegister' started
Test 'Tests\Browser\UserRegistrationLoginTest::testUserCanRegister' ended

Time: 1.36 minutes, Memory: 32.00MB

There were 6 errors:

1) Tests\Browser\ProfileComponentTest::test_profile_page_edit_modal_working
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable
  (Session info: headless chrome=70.0.3538.67)
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:158
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/ProfileComponentTest.php:55

2) Tests\Browser\ProfileComponentTest::test_profile_page_language_modal_working
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable
  (Session info: headless chrome=70.0.3538.67)
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:158
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/ProfileComponentTest.php:66

3) Tests\Browser\ProfileComponentTest::test_profile_page_health_modal_working
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable
  (Session info: headless chrome=70.0.3538.67)
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:158
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/ProfileComponentTest.php:77

4) Tests\Browser\ProfileComponentTest::test_profile_page_allergy_modal_working
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable
  (Session info: headless chrome=70.0.3538.67)
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:158
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/ProfileComponentTest.php:88

5) Tests\Browser\ProfileComponentTest::test_profile_page_medical_history_working
Facebook\WebDriver\Exception\UnrecognizedExceptionException: chrome not reachable
  (Session info: headless chrome=70.0.3538.67)
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:158
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/ProfileComponentTest.php:99

6) Tests\Browser\UserRegistrationLoginTest::testUserCanRegister
Facebook\WebDriver\Exception\NoSuchDriverException: invalid session id
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:100
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteExecuteMethod.php:40
/builds/titans/project/vendor/facebook/webdriver/lib/WebDriverOptions.php:156
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:259
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:148
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:149
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:77
/builds/titans/project/tests/Browser/UserRegistrationLoginTest.php:69
/builds/titans/project/tests/Browser/UserRegistrationLoginTest.php:57

Caused by
Facebook\WebDriver\Exception\NoSuchDriverException: invalid session id
  (Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.4.0-1069-aws x86_64)

/builds/titans/project/vendor/facebook/webdriver/lib/Exception/WebDriverException.php:100
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:326
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:547
/builds/titans/project/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:345
/builds/titans/project/vendor/laravel/dusk/src/Browser.php:244
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:135
/builds/titans/project/vendor/laravel/framework/src/Illuminate/Support/Collection.php:339
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:136
/builds/titans/project/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:69
/builds/titans/project/tests/Browser/UserRegistrationLoginTest.php:69
/builds/titans/project/tests/Browser/UserRegistrationLoginTest.php:57

--```

Can you check this thread for the beginnng?

@chilio
I have checked and tried every possible no luck maybe resolution resize can cause this?

@msonowal I doubt resize could cause this (you can always verify it yourself), rather I would suspect infrastructure or too complex tests.
I have a few additional questions for your case:

Can you find any significant common block in your modal tests, which might break tests, cause from your log it seems to happen on modals mostly? If tests are failing randomly, please omit this question.
Are you sure, that all tests are passing green on your local dev environment?
What are the parameters of your machine on AWS (CPU, MEM, Storage)?

@msonowal Additional note  I have seen same tests randomly failing while using certain jquery plugins like for example iCheck. Removing these plugins made my stressed out, concurrent gitlab-runners going green.
So please keep in mind, that your project may be responsible for any strange behavior also...

@msonowal great to hear that. I hope Laravel Dusk becomes more robust with time...