Move few functions from utils.js to night_mode.js

Those functions appear on utils.js, but maybe they should be moved to night_mode.js
function setTheme(theme) {
    document.documentElement.setAttribute('data-theme', theme);
    document.cookie = 'data-theme=' + theme;
}

// On page load, set the theme based on the cookie
document.addEventListener('DOMContentLoaded', () => {
    const theme = getCookie('data-theme') || 'light'; // Default to 'light' if no cookie is found
    setTheme(theme);
});

I feel like we should remove the utils.js completely.
Maybe create handle_cookie.js and save_game.js

Alright.
I am planning to do some (hopefully non-breaking) refactoring on the stats.ejs file to move most of the static code to the stats.js file.
Will try to handle this in that PR.

We will however, be better off at least keeping the file.
We can try to have as few functions as possible.


drag bug with iframe.

i find drag and drop feature has bugs when z-tree is over an iframe.
js fiddle:
https://jsfiddle.net/xpvt214o/447489/
i cannot drop to target node anymore.

please change your css
.content_wrap{
  z-index: 10001;
}


Minified version

Hi @bendrucker, in my current project our build process requires a minified version of all libraries we use, is there any possibility you provide this as part of the release, I would appreciate so much cuz I really like your work and dont want to use other else, thanks in advance and hope this can be done in the near future.

Glad you like the lib! I don't provide minified files since it's best you do that in your build process.


Latest updates for Last Mile Fleet Solution Sample Apps.

Latest updates for Last Mile Fleet Solution Sample Apps.

Hello Angela!

cla/google: we're modifying our config to use another bot account to submit.
CI builds: these will not work because LMFS Sample Apps require special configurations, which are infeasible with Github Actions right now. I will ping you a write up on these issues.

Angela's original request was to make the CI builds run, however as Tom mentioned this is currently impossible.
Got Alex to also take a look. Since Angela is OOO, will merge without waiting.


Feature: EmptyDataTemplate

I'm going to create a PR for the EmptyDataTemplate feature. My proposed design is as follows:

EmptyDataTemplate is an optional render fragment

If a BlazorTable dataset has no rows and an EmptyDataTemplate is defined, this should be rendered, replacing the current static text
No items....
. It would still be rendered inside a single row+cell spanning the table width.

If there is no EmptyDataTemplate set then nothing is rendered after the header row.

Sounds good


Flaky test: StreamDoesNotStartIfTokenAlreadyCanceled

This test fails occasionally with the following error:
System.Exception : 1 error(s) logged.
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection - TransportThrewExceptionOnStop - The transport threw an exception while stopping.
===================
System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found).
   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
   at Microsoft.AspNetCore.Http.Connections.Client.Internal.SendUtils.<SendMessages>d__0.MoveNext() in /_/src/Microsoft.AspNetCore.Http.Connections.Client/Internal/SendUtils.cs:line 81
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Http.Connections.Client.Internal.ServerSentEventsTransport.<ProcessAsync>d__18.MoveNext() in /_/src/Microsoft.AspNetCore.Http.Connections.Client/Internal/ServerSentEventsTransport.cs:line 105
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Http.Connections.Client.Internal.ServerSentEventsTransport.<StopAsync>d__20.MoveNext() in /_/src/Microsoft.AspNetCore.Http.Connections.Client/Internal/ServerSentEventsTransport.cs:line 228
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<DisposeAsyncCore>d__43.MoveNext() in /_/src/Microsoft.AspNetCore.Http.Connections.Client/HttpConnection.cs:line 256
===================
   at Microsoft.AspNetCore.SignalR.Tests.VerifyNoErrorsScope.Dispose() in /_/test/Microsoft.AspNetCore.SignalR.Tests.Utils/VerifyNoErrorsScope.cs:line 63
   at Microsoft.AspNetCore.SignalR.Tests.ServerLogScope.Dispose() in /_/test/Microsoft.AspNetCore.SignalR.Tests.Utils/ServerLogScope.cs:line 66
   at Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.<StreamDoesNotStartIfTokenAlreadyCanceled>d__12.MoveNext() in /_/test/Microsoft.AspNetCore.SignalR.Client.FunctionalTests/HubConnectionTests.cs:line 424
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
------- Stdout: -------
| [2018-07-25T01:11:07] TestLifetime Information: Starting test StreamDoesNotStartIfTokenAlreadyCanceled_json_ServerSentEvents_hubT
| [2018-07-25T01:11:07] ServerLogScope Information: Server log scope started.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.SignalR.Client.HubConnection Trace: Waiting on Connection Lock in StartAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:211).
| [2018-07-25T01:11:07] Microsoft.AspNetCore.SignalR.Client.HubConnection Debug: Starting HubConnection.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Debug: Starting HttpConnection.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Debug: Establishing connection with server at 'http://<IP_ADDRESS>:57032/hubT'.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.Internal.LoggingHttpMessageHandler Trace: Sending HTTP request POST 'http://<IP_ADDRESS>:57032/hubT/negotiate'.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Server.Kestrel Debug: Connection id "0HLFHPDREK8JO" started.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 POST http://<IP_ADDRESS>:57032/hubT/negotiate  0
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler Debug: AuthenticationScheme: Bearer was not authenticated.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Routing.RouteBase Debug: Request successfully matched the route with name '(null)' and template '/hubT/negotiate'.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager Debug: New connection pryDiUe2EYfvErXiZUI6_A created.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher Debug: Sending negotiation response.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Server.Kestrel Debug: Connection id "0HLFHPDREK8JO" completed keep alive response.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 0.9709ms 200 application/json
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Debug: Established connection 'pryDiUe2EYfvErXiZUI6_A' with the server.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Debug: Skipping transport WebSockets because it was disabled by the client.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Debug: Starting transport 'ServerSentEvents' with Url: http://<IP_ADDRESS>:57032/hubT?id=pryDiUe2EYfvErXiZUI6_A.
| [2018-07-25T01:11:07] Microsoft.AspNetCore.Http.Connections.Client.Internal.ServerSentEventsTransport Information: Starting transport
...

It sounds like it's an unavoidable race. Just suppress it in the test then.

https://github.com/aspnet/SignalR/pull/2739 Fixed


Past user-experience section

Describe the feature
Since this is a project focusing on building communities for networking it is essential that new users can know how things work here by reading the experiences and feedback of past/current users. This will enhance the user experience to a great extent.
Please consider assigning this issue to me along with the gssoc level label.
Add ScreenShots
Here is the reference

Record

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

hi, i am amit kumar
GSSOC'24 Contributor.
Could you please assign this task to me.
i will add a new section where past user shares his/her experience , and new users see and learnt something new from this.

hello, I am a gssoc 2024 contributer, could you please assign this task to me, please add the gssoc 2024 label

@ananya-sh30 Please work on it, it will be helpful


dir-paginate cannot be used in filteration in modals

I tried to use the pagination using dir-paginate in modal but i does n't worked fine

I am closing this issue as it is not actionable - there is not enough information for me to go off.
Please read and use the issue template next time.


Visual Studio Code Fehler beim Ausführen der Test

Hi @sime200992,
thanks for sharing your issue when trying to run the CalculatorJava project.
The error indicates that you do have an older version of the Java Runtime installed that only supports class file versions up to a specific version number - more specific in your case version 52.0 which reflects Java 8.
Let us try to identify the required changes at your end to provide a fix in the repository.
Please check your Java version installed running the following command in a Windows Terminal (e.g., PowerShell)
java -version.
In the pom.xml file of the project, change the Java version from 17 to your java version.
   <properties>         <maven.compiler.source>17</maven.compiler.source> <!-- change here your version -->         <maven.compiler.target>17</maven.compiler.target>     </properties>
Please let me know if this solves you problem, so I can make the necessary adjustments and configurations of the project.

Hi @sime200992 ,
besteht das Problem weiterhin?
VG


Bing Translate

Ref: Conversation #495 / Jules

Done: http://pilotmoon.com/popclip/extensions/page/BingTranslator


add(theme): uobristol

A new theme inspired by the brand guidelines of University of Bristol based on the Metropolis theme.
Questions before merging:

[ ] Can I move the theme into a subfolder under the theme folder and move the uob-logo and uob-bullet into two SVG files?
[ ] How to update the document?

It's an beautiful theme, thanks!
However, this theme is designed for a specific university, would you consider publishing it to typst universe instead of the touying built-in themes?

A reasonable suggestion. Thanks. I will close this PR and publish it to typst universe.


Performance issue when adding copied rows

When repeatedly adding copied rows to a table, it causes performance issues.
It appears this only happens when copying and adding alternate. When all rows are copied first and then added, this does not cause this issue.
Example code, which causes this issue:

Most likely the collection of visited objects contributes to this issue.
After adding the 6th copied row, visited contains more than 20000 records.

I'm using NPOI 2.6.0

I have a similar issue with CloneRow(), after 5 or 6 iterations, it starts taking longer and longer.


Revise specs to protect config

There is now a method on the spec helper, checkout_config, which will ensure that changes to the otel config which happen inside the block passed into the method are reversed when the block exits.
The specs should all be modified so that anything that alters the otel config does so inside of a checked out config, so that there are no unexpected side effects from config leakage when subsequent specs run. This work has been partially completed, but should be fully finished.

Closing this. A lot of this has been done, and will continue to be done. It now applies specifically to the SDK repo, as well.


feat: allow to use function as rhs for button keymap

This is useful when generating some button actions programmatically to avoid defining new globally accesible functions.

why not just set opts.callback = rhs? i'm kinda wary about overloading neovim api

i would have used vim.keymap but it wasn't available when I wrote the plugin, and just using opts.callback honestly doesn't feel that dirty to me

Ah, ok, my button() wrapper code is pretty complicated so when searching why functions do not work I didn't initially find a way to support function rhs there, so I did this change to alpha. I now changed my code to conditionally use opts.callback so this PR is not needed. It might be useful as a convenience for users (as probably most are now used to vim.keymap.set) but if you don't want to complicate the code then feel free to close this PR.

https://github.com/goolord/alpha-nvim/commit/7dc1bd80fac6da1b15a952e9b8fe245cbe5c0287


Haskell

This issue is to create a builder script for Haskell programs.
One suggestion I have is to reuse and slightly modify the SCons/scons-contrib Haskell script for our needs, since it seems to do what we need.
However, this would require we create a builders directory at the repo root. It could help us separate builders from the SConstruct file, and basically provide a library of builders (builders like the Copier, cargo, rutsc builders could go in the __init__.py file, though). On the other hand, it could be less clear.

I response to the original post:
The Haskell SCons tool script in scons-contrib is under GPLv3, so we probably can't use it without changing the whole project to a license compatible with GPLv3.
The could be a way to integrate the tool by recreating it ourselves, but it feels weird, and I'm not sure about the legality of it.
One important thing to note is that apparently the original author (Russel Winder) died, so getting permission from them is impossible, and I don't know who maintains the repository, so I can't get permission from them either.


OAuth2 client authentication error responses are broken.

When trying to get tokens, proper error messages will not be shown when authentication fails.

Were you able to try it out in 5.4.1 ?

Yes we tried in 5.4.1. Seems like we need to change the error messages. I am working on it.


Add a netlify.toml file to control options.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add automatic publish to PyPI workflow with automatic release note

The Release workflow publishes the package on PyPI. The workflow also creates a version tag in the GitHub repository, and publishes a GitHub Release using Release Drafter. The workflow is triggered on every push to the master branch.
Release steps only run if the package version was bumped. If the package version did not change, the package is instead uploaded to TestPyPI as a prerelease, and only a draft GitHub Release is created. TestPyPI is a test instance of the Python Package Index.

Contributes to #18


Proposal: Post Limits

I like the idea of open hunt, but I feel like it's going to be spammed to death every day, I think they're should be a cap to how many products can be submitted a day, just so that good products don't get left to the very bottom of 500x products

There is a suggestion regarding a karma system which would help with this #9, perhaps the two ideas can be linked as a reward tier.

Possibly more karma === ability to break post block per day? Not sure, my idea is rather a block for everyone (so only like the first 25 could post their product a day, or the first 25 + 5 curated picks)

I think a user level cap would be better and more fair, something like dribbble.

Agree with @nblackburn. If we restrict to the first 25 posts, we're taking away incentives and privileges for people who invest time and energy into the platform, who also happen to be very valuable users to the team. We need to reward early adopters to keep the momentum going.
A user level cap sort of idea that gives users with more karma more posts while now restricting new users from posting will be great.


[Question] about the action's icon color

according to this
https://github.com/phonegap/phonegap-plugin-push/issues/345
thanks @macdonst let me know the "white" situation
well，it is my screenshot，left side is Android 5.1.1，right side is Android 4.4.2

all code all the same
the icon in 5.1.1 will become gray but Android 4.4.2 is normal
is it a Android 5 "feature" just like the "white" situation ? (what a ugly feature XD...)

Android app built with target-sdk > 20, running on a device with android 5.0 or higher
Just as is the case on https://github.com/phonegap/phonegap-plugin-push/issues/345, as explained by @macdonst , every system wide icon will be manipulated by android so that it is composed of transparent and a single main color pixels. On stock android, these colors are white for the notification icons, and gray for action icons. That applies to any and every app, unless they are creating custom notification objects from the start.
Android app built with target-sdk > 20, running on a device with android 4.4 or lower
The new apis are non-existant, so the icons will be shown AS IS.
Android app built with target-sdk = 20, running on a device with android 5.0 or higher
Although the new apis are present, the app is demanding to be treated as if the device was on android 4.4 or lower, so compatibility mode will apply, with the old (4.4) api taking place.
Android app built with target-sdk = 20, running on a device with android 4.4 or lower
The app is at home, there is no compatibility mode in place, so the icons will be shown AS IS.

@fredgalvao Great explanation! I was looking for this... thanks

awesome explanation @fredgalvao
maybe you can update the readme
thanks your help and close it


fix deprecations: tfLite.setNumThreads -> tfLiteOptions.setNumThreads

The latest tfLite does not allow to directly set the numThreads to the interpreter.
Instead, the numThreads must be set to an optionsObject that has to be passed while creating the tflite interpreter.
The changes are

instantiation of tfLite interpreter passing the options object
the num threads is set to the options object

I signed it!
On Fri, Apr 26, 2019 at 11:00 PM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I
signed it!) and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google.com/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Ftensorflow%2Fexamples%2Fpull%2F43
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/examples/pull/43#issuecomment-487199514,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALVZDUOWOHWOK66XWVHDI3PSNUQBANCNFSM4HI2IBRQ
.

--
Thanks & Regards
PraveenKumar Vasudevan

Hi @praveenv4k,
To make the CLA bot happy you'll need to be sure to sign the CLA with the same email address you use for github.
It might be easiest to check your email settings and remake the PR.
Or use this trick:
https://stackoverflow.com/questions/2919878/git-rewrite-previous-commit-usernames-and-emails


mesa: 18.1.5->18.1.2 [revert]

Motivation for this change
Holy hell, did this ever take debugging. So after nixos-unstable-small was finally unstuck, I eagerly rebased my branch and went onto rebuilding. Just to find that Xorg was segfaulting whenever I got past sddm and into an actual session. See sample log excerpt below.
I took to bisecting the nixpkgs tree, with eternal rebuilds, and eventually isolated the problem: mesa. I know this seems obvious in retrospect, but seeing radeonsi in the trace had me thinking the kernel might be at fault, what with all the new AMDGPU code being merged and me running a fancy Vega card.
Anyway, I tried 18.1.5, found that it did not fix it, and so I reverted that and the bump to 18.1.4 as well. 18.1.2 seems to run fine for me. Let's wait for another release before updating mesa maybe.
 Server aborting
Aug 01 23:58:15 cryptbreaker X[1230]: (EE)
Aug 01 23:58:15 cryptbreaker X[1230]: Please consult the The X.Org Foundation support
Aug 01 23:58:15 cryptbreaker X[1230]:          at http://wiki.x.org
Aug 01 23:58:15 cryptbreaker X[1230]:  for help.
Aug 01 23:58:15 cryptbreaker X[1230]: (EE) Please also check the log file at "/dev/null" for additional information.
Aug 01 23:58:15 cryptbreaker X[1230]: (EE)
Aug 01 23:58:15 cryptbreaker X[1230]: (II) AIGLX: Suspending AIGLX clients for VT switch
Aug 01 23:58:15 cryptbreaker X[1230]: (EE) Server terminated with error (1). Closing log file.

Things done
I've reverted two commits that bump mesa to 18.1.4 and then to 18.1.5

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[ ] 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)
[x] Fits CONTRIBUTING.md.

Thanks for tracking this down! I think this is okay for now, but eventually we will want to update mesa. We should file an issue in the mesa tracker & maybe someone there will have an idea as to what caused this.

Hmm, the AMD situation is getting complex here.  amdgpu users actually have problems with 18.1.2 and so far only reverting to 18.0.x helped (and there's how to avoid rebuilds, too): https://github.com/NixOS/nixpkgs/issues/44183

I use AMDGPU. In fact, I have little choice. amdgpu-pro hasn't been updated forever and fails to build, so only amdgpu since 4.15 can even run my Vega card.

I seem to have some issues here and there, such as mpv not being able to use the GPU for decoding, or flickering in Electron apps, but these are not because of 18.1.2. I'd been running 18.1.2 for weeks without an issue, but the recent rebuild of my system off staging seems to have borked something else.

It would seem there's no reason to revert, now, instead we should look into deleting the mesa cache on upgrade possibly.
See @corngood 's comment near the bottom of #44183 .

@Chiiruno you should be able to use the current mesa just by deleting your cache. To be clear, that's:
_
sudo rm -rf /root/.cache/mesa_shader_cache
rm -rf ~/.cache/mesa_shader_cache
The problem is, you may have to do it whenever you switch to a new version of mesa, even if you just want to go back from 18.1 to your previously working system config with 18.0. Fixing the cache logic would essentially clear the cache automatically when switching versions.
_
For anyone hitting this problem, I'd suggest just deleting the cache and moving to 18.1. Hopefully by time there's another breaking update, we'll have a fix in place.

@Chiiruno cache fix is in #44575, which should supersede this if there are no problems with it.

Should be fixed by #44575

My bad, whenever it gets merged to master.

Yeah, and it might explain why different users needed to roll back to different mesa versions.

I've been having some flickering issues in some apps like Slack and Discord, but I'm not sure if that's even related. Everything else works fine, including games.


Improving development experience: how to debug schematics

What is this feature?
This feature does not directly concern the users of the library, but its developers/contributors.
How the feature should work?
This feature aims to improve the development experience by providing an easy way to debug the library's schematics.
It can be achieved by creating a .vscode/launch.json file with the following content:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "skipFiles": [
        "<node_internals>/**"
      ],
      "program": "${workspaceFolder}/node_modules/@angular/cli/bin/ng",
      "args": [
        // # 1
        // "add",
        // // "@routerkit/core"
        // "./dist/routerkit/",
        // "--skipInstall",

       // # 2
        "g",
        "@routerkit/core:parse",
        "--project",
        "example-app",
      ],
      "sourceMaps": true,
      "outFiles": [
        "${workspaceFolder}/dist/routerkit/**/*.js"
      ],
      "outputCapture": "std"
    }
  ]
}

# 1 and # 2 could have their own launch configuration eventually.
In order to create the dist/routerkit, we need to run both npm run build and npm run build:schematics, because, in this case, the parse schematic relies on a (built) project. The first build command will build the project the schematic will be tested on and the second build command will build the schematics(with source maps).
Then, we can go to parse/index.ts and place a breakpoint there to see the results.
On a side note, I noticed that, during debugging, the ora package throws the following error: cannot write after stream was close. I think it's because it uses by default the process.stderr stream by default:
const projectSpinner = ora(taskStart('Analyzing project')).start();

I got rid of the error by instantiating the spinner like this:
const projectSpinner = ora({ text: taskStart('Analyzing project'), stream: process.stdout }).start();

Is your feature request related to a problem?
No.
I think we could add the necessary steps in the CONTRIBUTING.md file. Also, it would be my pleasure to create a PR for this, if everything is alright.

so, is your suggestion to add .vscode/launch.json and modify ora (change stream)?

anyway, let's proceed with a pull request


Botón de Inicio en la Barra de Tareas.

Describe the bug
When I run "TaskbarX.exe" v<IP_ADDRESS>, my taskbar shows 2 start buttons. This happens in all versions of TaskbarX except "TaskbarX v<IP_ADDRESS>".
To Reproduce
Just run "TaskbarX.exe" v<IP_ADDRESS> and the error happens.
Expected behavior
Icons centered with a single Start button.
Screenshots
Without running "TaskbarX.exe" v<IP_ADDRESS>:
https://drive.google.com/file/d/1FuNyb4_Ama1K4l2NA_aaG-tlhyPO9krx/view?usp=sharing
Running "TaskbarX.exe" v<IP_ADDRESS>:
https://drive.google.com/file/d/1dVoALmvhPzUdOjH-POxzOvBFg6BwkRZc/view?usp=sharing
Running old version "TaskbarX.exe" v<IP_ADDRESS>:
https://drive.google.com/file/d/1egSwg0pTSP1WACNu0wPGcpt1-fg7waap/view?usp=sharing
Desktop (please complete the following information):

OS: Windows 10 LTSC Delta OS (Modified Windows. This is the web: https://windowsminios.org/).
Browser: Chrome.
Version: v87.0.4280.88 (Build oficial) (64 bits)

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


AsyncChannel crash when cancelled with only one awaiting

Hi,
AsyncChannel can crash in the following context:

start an iteration in a Task
cancel the task while the AsyncChannel is being awaited
send a value in the channel

Here is a test that crashes:
func test_cancel_when_only_one_iterator_while_waiting() async throws {
  let channel = AsyncChannel<Int>()

  let task = Task {
    for await _ in channel {}
  }

  try await Task.sleep(nanoseconds: 1_000_000_000) // ensures the loop is waiting for a next value

  task.cancel() // sets the inner state of the channel to awaiting but with 0 nexts

  await channel.send(1) // tries to remove the first element of the awaiting state (which is empty) -> crash
}

linked to https://github.com/apple/swift-async-algorithms/pull/143

The PR has been merged and an issue has been created to track the potential unit tests #148


HOCS-1640 : editing and deleting case notes API

Editing and deleting case notes API

I've now made the changes to the Timeline items.


adapting pigpiod for Odroid

hello!
great library you have there.
As we are pretty much out of interest witg our platform (infakt C2 on 5.14.19 Ubuntu 18.04) I wondered if it was possibel to adapt your pigpiod library with somewhat effort for the C2 in order to be able to run node-red-node-pi-pgiod nodes on it!
what do you thiink?
with kind regards
Habakuk

pigpio is only supported on Raspberry Pi SoCs.


dbeaver: 5.2.1 -> 5.2.2

Motivation for this change

Updates dbeaver 5.2.2.

Things done

✔ Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

✔ NixOS

✔ Tested execution of all binary files (usually in ./result/bin/)
✔ Fits CONTRIBUTING.md.

As a side note, #34182 is still open and I will still gladly accept any help in figuring out how to build this using the source release.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: dbeaver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: dbeaver
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2
shrinking /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2/dbeaver/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.551.v20171108-1834/eclipse_1630.so
shrinking /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2/dbeaver/dbeaver
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2/bin
patching script interpreter paths in /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2
checking for references to /build in /nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2...
/nix/store/v2266i9vqrgvfiysicpiw6i9pc3nfhh7-dbeaver-ce-5.2.2

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: dbeaver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Ghasty⚡

Closes #292
Closes #294
What new changes did you make? Tick all applicable boxes

[x] Added new abbreviation
[ ] Fixed something in the source code
[ ] Added a new feature
[ ] Fixed the docs (README.md, CONTRIBTUING.md, etc)

Describe the new changes you added.
Added few abbreviations.

Share a screenshot of new changes

I'm asking because I want to include something that is commonly used. I asked around a bit and many more people know HS for happy sunday(an alternative could be High School) over HSD.

Alright. So what do you think? I should probably change that?

I think adding it as HS would be better, since it is common, I think it is likely to be searched.

Hello @Ghasty003 Any updates on this pull request?

Hello @Ghasty003 Any updates on this pull request?

Hi, @Njong392 apologizes for not updating you.
I've been really busy. I'll work on this as soon as possible.

Thank you for the changes, but I see that you have made changes to the package-lock.json file. To revert this, please check out this guide.

I've reverted the change.

Uhm, your commit still has the changes. I don't think you have successfully reverted. If you have any trouble doing this, I am happy to help.

Hmm, I think I'd need the help. I've reverted the changed made to the file, and re-push it here according to the reference you suggested. If you actually check the last push, you'd see the package-lock.json is different from the initial.

🤔 Okay. Here's what I suggest you try. Try syncing your fork with this one, pulling newest changes. If u try to commit again, stage files first so that you can easily exclude the package-lock if it is still among the files that have changes.

Fr I actually sync the fork before I pushed my code. And i've changed the package-lock.json already on here. Unless we'd have to close this pull request & I'd have to open another, idk.

Did you pull after syncing the fork? If you did, we might fr have to maybe close the pr and try again. I'm not so expert in git, I'm sorry. Maybe I'll do some reading to see what might have been the issue.

All looking great now. Thank you. What did you do to fix it, if I may ask?


Angular  - Add support for Angular 19 in our peerDependencies

Acceptance Criteria:

Support added for Angular 19 in our peerDependencies

:tada: This issue has been resolved in version 3.0.0-alpha.9 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.17.0-alpha.129 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.29.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 5.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Hotfix][CI] Pin setup-envtest dep

Why are these changes needed?
Last week, setup-envtest upgraded the dependencies from Golang 1.20 to 1.22. The CI test fails with the following error message:
go: sigs.k8s.io/controller-runtime/tools/setup-envtest@latest (in sigs.k8s.io/controller-runtime/tools/setup-envtest@v0.0.0-20240323114127-e08b286e313e): go.mod:3: invalid go version '1.22.0': must match format 1.23

Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

will we need to unpin this?

Not sure. We have two options: (1) pin the tag of setup-envtest (2) upgrade Golang version from v1.20 to v1.22. However, (2) requires much more effort compared to (1). I will discuss with the community to check which one is the long term solution.


fix for kafka feature row deserializer test throwing error

This fixes the error being thrown by the test, which breaks the build, although the test passes.

@baskaranz can you please squash the commits and also create an issue for this PR?

I'd be interested to know why this fixed the warnings?

@tims I've used google-java-format plugin and it didn't reformat my code to keep ContextConfiguration at the bottom.
Coming to the fix, I've seen multiple issue raised even with spring and other forums about the same issue, which stated that it fails their jenkins build etc., (assuming we would face the same as well) Here's one
https://github.com/spring-projects/spring-kafka/issues/194
I've used @ClassRule for KafkaEmbedded instead of bean and it resolved the ERROR messages I see while running the test

Make sure it's enabled for your project, you need turn it on, not just install it.

@tims Intelij was smart enough to suggest me when I installed the plugin to enable for my projects and I did, not sure why it doesn't reorganize the code when it reformats :)

Sorry to keep harping on about it, but formatting changes in every commit will continue to drive us nuts.
I've found I need to enable for every project separately, it's not global, so you may have enabled for another project?
Can you check preferences -> other settings -> google-java-format settings
And ensure Enable google-java-format is checked.
And make sure you've restarted intellij since installing.
Then run cmd-alt-shift-L in the file (assuming on osx)

Sorry to keep harping on about it, but formatting changes in every commit will continue to drive us nuts.
I've found I need to enable for every project separately, it's not global, so you may have enabled for another project?
Can you check preferences -> other settings -> google-java-format settings
And ensure Enable google-java-format is checked.
And make sure you've restarted intellij since installing.
Then run cmd-alt-shift-L in the file (assuming on osx)

Should we make an issue for creating a contributing document again? Where we can specify how your development environment should be set up for contributing to each component?

@baskaranz you mind squashing this into atomic commits?

/retest
/assign tims
/assign pradithya

The test wont pass until a rebase is done on current master. Also, @pradithya can you please review this instead of me? You have more familiarity.

@baskaranz  Is it possible to remove dependency to org.springframework.kafka for testing in the future?

@baskaranz  @tims the import ordering is not handled by google-java-format plugin, you'll need to import google code style for intelliJ to your code style settings.


Added JSON payload support for POST

I was trying to send JSON inside the POST body when I realized qwest only seems to support form encoded data. I've made a little modification for it to support application/json content-type for requests. Main changes are, support for options.headers (as using the "before" functionality was not correct as you have to know request content-type prior to serializing the request body) and the adition of JSON.stringify in case of POST and */json.
Also I think there was some buggy code on lines 293 and 294 in case the header name comes already in the correct format.
Hope you find it useful.

i have a problem when upgraded to the 3.0 version by bower and the json posting became normal formData, is it true that was changed?

Many things have changed from 0.7.0 since we're at 3.0.0. What is your request? As stated in the docs, the default value for dataType option is post. To send JSON data you need to set dataType to json.

oh i have my problem fixed that i set the dataType at wrong place. thank u all the same~@pyrsmk

Great :)


New French documentation (docsite)

Still work in progress (no new screenshots, TODOs remaining) but peer review should start :-).

merged


feat: Panelplot config redesign (dashboard)

Loom walkthrough:
https://www.loom.com/share/5d39b8212bc8425784c133003fe6aa17?sid=7c3c4097-7afe-447f-a6ad-283ac5aec084
Screenshots:

Chatted in Slack, this is a problem in prod too so nothing particular to this PR.
fixed
fixed
fixed
fixed
Chatted in Slack, this is the same behavior as in prod, nothing particular to this PR


DBZ-5997 Debezium Storage add support for Apache RocketMQ

https://issues.redhat.com/browse/DBZ-5997

@vjuranek Could you please review this one too? Thanks

Overall LGTM, just a few mostly code-style comments. Also checkstyle fails - these issues are not mentioned here, just run mvn clean verify to see list of issues.

Thanks review PR, I have modified according to your suggestions

ok， I made some fixes

@sunxiaojian thanks! There are still few javadoc params without description - please remove them and also there are some checkstyle issues. Please fix them (or check "Allow edits and access to secrets by maintainers " and I can push the changes). Once done, IMHO ready to merge (and once we have working CI again).

ok， I made some fixes

Thanks @sunxiaojian ! LGTM now, will merge once we fix CI and tests pass.

The failure of CI may be a bug (https://github.com/tj-actions/changed-files/issues/419). May need to upgrade the tj-actions/changed-files version?

@sunxiaojian Interesting notice, could you please try to updated the PR with the Actions change so we can see if it is root cause or not?

@sunxiaojian yes, there's already a PR for it - you can use it and rebase this PR on top of it to test if it really fixed the issue or not as suggested by @jpechane

@sunxiaojian yes, there's already a PR for it - you can use it and rebase this PR on top of it to test if it really fixed the issue or not as suggested by @jpechane

After rebase this PR , the issue is fixed

@sunxiaojian yes, there's already a PR for it - you can use it and rebase this PR on top of it to test if it really fixed the issue or not as suggested by @jpechane

After rebase this PR , the issue is fixed

Merge, thanks @sunxiaojian !


Automatically chunk large request bodies

Motivation
If the HTTPClientRequest.Body is created from a type that is not ByteBuffer, we need to convert it to it at some point.
ByteBuffer can only hold up to Int32.max on 32-bit platforms and UInt32.max on 64-bit platforms and crashes if it exceeds this size limit.
Modification

Convert from some Sequence<UInt8>, some Collection<UInt8>, some RandomAccessCollection<UInt8> and String in lazy chunks if the input exceeds 4 MB.
some Sequence<UInt8> is special as it can't be efficiently chunked lazily. Therefore we need to do the chunking eagerly if it implements the fast path withContiguousStorageIfAvailable. Otherwise we do the chunking lazy but "slowly".
conform HTTPClientRequest.Body to AsyncSequence to make testing easier.

Result
Converting from some Sequence<UInt8>, some Collection<UInt8>, some RandomAccessCollection<UInt8> and String to ByteBuffer will no longer crash for inputs that are larger than 4GB. Conversion above 4MB is now more memory efficient as we do it lazily and not eagerly all at once.

@Lukasa anything else?


Remove four unused methods in tools code

We cannot remove these yet because they were just deprecated between last release and now.  We need to give this time to bake.


Cannot log "page" events in v1.9.0

Puppeteer: 1.9.0
macOS: 10.14
Node: 8.12.0
Code that reproduces the issue:
const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto('https://example.com');
  await page.screenshot({path: 'example.png'});

  await browser.close();
})();

Steps:

Install Puppeteer v1.8.0
Run a puppeteer script with DEBUG='puppeteer:page'
In the terminal you'll see all the page events logged.
Install Puppeteer v1.9.0
Run the script the same way with DEBUG='puppeteer:page'
No logs are shown in the terminal

Note: If you run with DEBUG='puppeteer:*' you will get logs for session and protocol but nothing else.
Expected: I should be able to get logs of all the page events.
Actual: I can only get logs for session and protocol.

@patrickeakin we dropped the Public API logging in 1.9.0 since we've never used it to debug issues; on the contrary, it was yielding overly verbose logs. Why do you need it?

@aslushnikov Thanks for getting back to me 😄.  I'm using Puppeteer and Ava to write integration and UI tests for a large web application. As I write the tests I used the logging to see exactly on what step the script is timing out. These timeouts normally indicate things like a transition not accounted for, a selector that needs to be changed, etc. Essentially the logging pointed to the exact place in my test suites where a problem lies. It's been indispensable in my ability to debug the scripts as i develop them.
I'd appreciate in giant heaping amounts to at least be able to log the page and elementHandle events. Or if you can suggest another avenue I might try I'd be a happy dude.

I do my own debug logging by hooking all the page.on events and .catch(err,fcn) promise api callbacks.  @patrickeakin does the DEBUG= provide you more details than that?     Or something the trace api doesn't provide?  (I haven't used DEBUG= or trace, just curious)

@jasonswearingen Thanks for the suggestion. I'll try that out and let you know if that does what I need.

@jasonswearingen Thought you'd like to see an example of what I get when I log out page events in the way I described. Below is the output of a script where I go to Google, search for 'sup' and take a screenshot.
Output like this is really helpful when a before hook or something in my tests takes a 💩and I want to see where the hang up happened.
$ DEBUG='puppeteer:page' node puppeteerTest.js
  puppeteer:page page.setViewport({"width":"800","height":"600"}) +0ms
  puppeteer:page page.goto("https://google.com") +252ms
  puppeteer:page page.waitForSelector("input[aria-label=\"Search\"]") +876ms
  puppeteer:page page.mainFrame() +0ms
  puppeteer:page page.type("input[aria-label=\"Search\"]", "sup") +508ms
  puppeteer:page page.mainFrame() +1ms
  puppeteer:page page.click("input[value=\"Google Search\"]") +3s
  puppeteer:page page.mainFrame() +0ms
  puppeteer:page page.waitForSelector("#hdtb-msb") +1s
  puppeteer:page page.mainFrame() +0ms
  puppeteer:page page.screenshot({"path":"\"example.png\""}) +735ms

@aslushnikov
Using the page.on events doesn't appear to get me what I was getting by logging out puppeteer:page.
Here is some extra context.
Often the values passed to puppeteer functions are variables. Some of these variables are functions that build the values dynamically depending on the specifics of the test. Much of this is stored in objects that are iterated over. Also, Puppeteer scripts are mostly broken out into reusable functions. The debug is valuable because I can see the value of these variables in sequence in any given run.

@patrickeakin I see how this might be valuable for your case. The actual code that was doing this is not that involved, please see the f0beabd22a3908a7405b22b8e24e3c9295e1455b that was removing it.
In fact, you can run the same code on your side; it's actually quite easy:

Get our helper.js right before we dropped the public API logging (I linked the right one; just copy it). You can clean it up to drop everything but the tracePublicAPI method
In the very beginning of your scripts, proactively "trace" classes you care about:

const helper = require('./myhelper'); // this is the helper from (1)
const {Page} = require('puppeteer/lib/Page.js'); // this is Puppeteer's Page
helper.tracePublicAPI(Page); // this will bring back the public API logging for you

I don't think we should resurrect this feature and ship it to everybody, but this should help for your case.
Let me know what you think.

@aslushnikov That does the trick. Thanks a ton for your help. I really appreciate it.


Frames mismatch/missing using 'extract_frames.py'

When using the  'extract_frames.py' to process MSRVTT, it works well. However, when I adopted it to process MSVD and Breakfast datasets, I met the following error:

No such file or directory: 'myfile/MA-LMM/lavis/../data/msvd/frames/G6w6k08UPyg_31_41/frame000102.jpg'

I found that there are only 101 frames in the folder of G6w6k08UPyg,  and this is not an individual case.  Could you give a solution to deal with it? Thank you!

Sorry for the duplicate submission due to network error, see Ref:#37

Sorry for the duplicate submission due to network error, see Ref:#37

Sorry for the duplicate submission due to network error, see Ref:#37

Sorry for the duplicate submission due to network error, see Ref:#37


Upload new LIVD table

Problem statement
The LIVD team sent over a new LIVD table that needs to be uploaded into ReportStream.
What you need to know
https://app.zenhub.com/files/304423150/fd0852c2-aa70-4e42-8d2f-e18f4ae04bfe/download
To do
Run livd-table-update command with new table

Closed as duplicate of #7952

Re-opening as this is the correct file with the additional columns.

https://app.zenhub.com/files/304423150/3ea41f50-b8e9-4b19-b15b-b3f70ed02a0f/download

Waiting for issues with Staging to be resolved.


fix: reference the types in package json

@xenova added the types to the package json file so the types could be used.

Is there a way to do this that allows users to use npm link? If I'm not mistaken, this will cause an issue since the types won't be updated?

Also, this main.d.ts file won't be updated each time we build.

That is right, the main.d.ts file is not updated. I will try to find a solution that won't require us to change the build process.

Changes live on main 👍


New version: Tencent.TIM version <IP_ADDRESS>38

Created by 🥟 Dumplings in Run #3446.
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Installer https://dldir1v6.qq.com/qqfile/qq/TIM3.4.8/TIM<IP_ADDRESS>38.exe
Scan request id: '88719223-54e5-4e48-8042-7ac312cc181a'
Error information: BlockingDetectionFound

2/22/2024 10:41:36 AM

Installer Validation

(Automated response - build 795.)

This might be due to a network block of data centers, to prevent automated downloads.
(Automated response - build 795.)


Comparison of different networks: failed with error

used your code as it is to compare multiple nets and get this one
tried with the version your provided hours ago on windows

TypeError                                 Traceback (most recent call last)
 in ()
10
11 with tf.Session() as sess:
---> 12     nets.pretrained(models)
13     for (model, img) in zip(models, imgs):
14         preds = sess.run(model, {inputs: img})
c:\anaconda3\lib\site-packages\tensornets\pretrained.py in assign(scopes)
56         model_name = parse_scopes(scope)[0]
57         try:
---> 58             load_dictmodel_name
59         except KeyError:
60             try:
c:\anaconda3\lib\site-packages\tensornets\pretrained.py in load_mobilenet75(scopes, return_fn)
511         cache_subdir='models',
512         file_hash='d4557a46a44eebfeaf08c82ae33765ed')
--> 513     values = parse_weights(weights_path)
514     return return_fn(scopes, values)
515
c:\anaconda3\lib\site-packages\tensornets\utils.py in parse_weights(weights_path, move_rules)
291     if later_tf_version:
292         for (i, name) in enumerate(data['names']):
--> 293             if '/beta' in data['names'][i-1] and '/gamma' in name:
294                 values[i], values[i-1] = values[i-1], values[i]
295
TypeError: a bytes-like object is required, not 'str'

The issue has been resolved by this patch. If you want to use the latest version, you can try pip install -U --no-deps git+https://github.com/taehoonlee/tensornets. Thank you for the comments, @alain2208!


Inline format is applied to line breaks despite format being set to be removed

Inserting a line break doesn't apply/remove pending formats, only replace_text does.
let mut model = cm("{Test}|");
model.bold();
model.select(Location::from(4), Location::from(4));
model.bold(); // This writes bold into toggled_format_types
model.enter(); // This should apply pending formats (e.g. remove bold)
model.enter();
model.enter();
model.replace_text("T"); // Bold is only removed here
model.replace_text("e");
model.replace_text("s");
model.replace_text("t");
assert_eq!(tx(&model), "Test

Test|");

Tested this and is now working, the output looks like this with no formatting applied to the linebreaks
assert_eq!(tx(&model), "
Test

Test
");

Was probably fixed during the paragraphs rewrite.


Faction defs used as Slayer on weapon | Other defs section not working in IF statements

So im trying to use those faction defs on the weapon -> for example SLAYER=faction_flame.
If i do this and wants to show tooltip ON=@ClientToolTip based on slayer, for all defs it works fine, except the last section.

// Others
faction_bovine<PHONE_NUMBER>
faction_flame<PHONE_NUMBER>
faction_ice<PHONE_NUMBER>
faction_wolf<PHONE_NUMBER>

If i test it with custom function using STRMATCH and not IF, the statement is true, but only in custom function, in trigger ON=@ClientToolTip it just doesnt either way, the statement is never true.
I have no idea what could cause this, maybe too long def number?
This is never true, even tho the slayer==<def.faction_flame>
IF (<SLAYER>&<def.faction_flame>)
ADDCLILOC 1072511
ENDIF

This somehow is true, but only inside the function, if i use this statement in trigger, not true.
[function ttt]
IF (strmatch(*<slayer>*,<slayer>&<def.faction_flame>))
serv.log yo <slayer>
endif

Possible solution, from a discord discussion:
nolok
—
15/07/2023 20:08
split the faction prop in two?
Gladie
—
15/07/2023 20:09
what do you mean?
nolok
—
15/07/2023 20:10
a better idea even
we have npcgroups and factions
some factions are exclusive to an npcgroup
still, every faction is in a big bitmask, thus we have enormous numbers
eg:
[DEFNAME npc_factions]
// Fey group (opposed to Abyss Group)
faction_fey                 01            // Super Slayer
// Elemental Group (opposed to Abyss Group)
faction_elemental           02          // Super Slayer
faction_air_elemental        04
faction_blood_elemental     08
faction_earth_elemental     010
faction_fire_elemental      020
faction_poison_elemental    040
faction_snow_elemental      080
faction_water_elemental     0100
// Abyss group (opposed to Elemental and Fey Groups)
faction_demon               0200        // Super Slayer
faction_gargoyle            0400        // Super Slayer
we could instead start from 1 when beginning a new group
eg:
[DEFNAME npc_factions]
// Fey group (opposed to Abyss Group)
faction_fey                 01            // Super Slayer
// Elemental Group (opposed to Abyss Group)
faction_elemental           01          // Super Slayer
faction_air_elemental       02
faction_blood_elemental     04
faction_earth_elemental     08
// Abyss group (opposed to Elemental and Fey Groups)
faction_demon               01        // Super Slayer
faction_gargoyle            02        // Super Slayer
that means that we have to change the code to check for both group and faction, but that will solve our problem with no additional memory footprint
or core complexities
Gladie
—
15/07/2023 20:16
but then would be 01 usefull twice?
because the faction system in core is done that if you have only the faction_elemental, you deal double damage to all the elementals of this group, but if you have only faction_air_elemental, you only deal tripple dmg to air elemental
maybe i dont get fully what you mean
nolok
—
15/07/2023 21:02
Yes
More than twice
Then we would need to split that into faction_group and faction_species/subgroup/something in the source
I have no better ideas honestly
And if the faction species is 0 but not the group, you will deal more damage to every monster in the group
The other thing that might be worth adding in the case of a rework is to enable to slay a specific defname
Maybe with another property like faction_extended, if 1 you check for additional tags containing defnames
That's an idea, maybe not the best one

The problem is not a range of values if I understand the issue correctly. Because 2^62 == 4,611,686,018,427,387,904 so that mean you can set values until 0x4000000000000000
The problem is EVAL not works perfectly for llong values, even faction_wolf not working correctly
[FUNCTION t] FACTION faction_wolf SERV.LOG <FACTION> IF (<FACTION>&<def.faction_wolf>)   SERV.LOG X ELSE   SERV.LOG NO-X ENDIF IF (<FACTION>&faction_wolf)   SERV.LOG Y ELSE   SERV.LOG NO-Y ENDIF IF <EVAL <FACTION>&0800000000>   SERV.LOG Z ELSE   SERV.LOG NO-Z ENDIF
Returns;
Resync complete! 19:09:(defs_faction.scp,78)0800000000 19:09:(defs_faction.scp,82)NO-X 19:09:(defs_faction.scp,87)NO-Y 19:09:(defs_faction.scp,92)NO-Z 19:09:1:'xwerswoodx' commands 't'=1
Even faction_bird works well;
[FUNCTION t] FACTION faction_bird SERV.LOG <FACTION> IF (<FACTION>&<def.faction_bird>)   SERV.LOG X ELSE   SERV.LOG NO-X ENDIF IF (<FACTION>&faction_bird)   SERV.LOG Y ELSE   SERV.LOG NO-Y ENDIF IF <EVAL <FACTION>&080000000>   SERV.LOG Z ELSE   SERV.LOG NO-Z ENDIF
Returns
Resync complete! 19:12:(defs_faction.scp,78)080000000 19:12:(defs_faction.scp,80)X 19:12:(defs_faction.scp,85)Y 19:12:(defs_faction.scp,90)Z 19:12:1:'xwerswoodx' commands 't'=1
080000000 equals to 2,147,483,648 which is 32bit integer max value not llong.
We probably need to change the evaluation system from int to llong to update that for 64-bit integers.

Okay I found out the issue, it's same as I wrote before, because _Evaluate_Conditional_EvalSingle returns as fVal = bool(Exp_GetVal(ptcSubexpr)); while Exp_GetVal is 32bit integer it causes this issue. Changing it Exp_GetLLVal solve the problem.

But there no eval on the problematic if.  You mean server us eval on internal?

Yes, I meant the IF statements evaluate function like _Evaluate_Conditional_EvalSingle and QConditional for  function not the EVAL function itself. EVAL, FVAL, HVAL etc already set 64-bit in CScriptObj.cpp but IF and QVAL have forgotten in 32-bit int. I changed both of them to 64-bit, I am testing right now but honestly it should work fine.

Now with the new action on github, .exe will be create when you create a PR. Everyone can test it easy.

I pushed but haven't seen how to download any pushed version honestly :))

works, thanks.


I like to contribute

I like to make a contribution, to test and see if I really understood.

You're welcome to fork the repository and work on your own copy.


feat: Trying out multiple replicas (#6686)

POC!

I run integration tests on my GKE cluster with keptn 0.13.0-dev
Services that needs some work on/ changes
Configuration-service, as we already knew, cannot handle multiple replicas but it will be substituted anyway.
Resource-service is very close to being able to do so, (see TODOs)
Services that worked with no need for any change

api-service
approval-service
helm-service
jmeter-service
lighthouse-service
mongodb-datastore
remediation-service
secret-service
statistics-service
webhook-service

TODOs:

Make sure that there is an appropriate retry logic for every part in the service/stage manager where we write something to the repo to avoid failing for no fast forward updates when multiple replicas try to change a repo. This is for sure missing at least in writeAndCommitResource . Falures still happens at create service or project and during most calls that write on the repos.


Spawning vehicles in Carla

To test many of our perception methods, we need other road users in Carla.  Adding this functionality to the carla_interface and making it easy to customize is what this is all about.

09/16/2024 Update: Spawning Vehicles in CARLA
Status: Delayed - I successfully developed a python script capable of spawning vehicles in CARLA. When this script is running, it displays the spawn-point coordinates, vehicle number, and brake light status (ON or OFF).
Next Steps: - I'm currently working on developing a ROS2 based service for this file in order to integrate vehicle spawning and brake light detection into the broader ROS2 NOVA Navigator system.
Projected Completion: Projected to be completed by September 30.
Update: Successfully able to spawn vehicles at any coordinate in CARLA with brake light statuses (ON or OFF) and their respective vehicle numbers.

09/23/2024 Update: Spawning Vehicles in CARLA
Status: Completed! - I successfully integrated the current python script as a ROS2 package that can be built using "colcon build" and "ros2 run" commands that automatically spawn vehicles in CARLA. When this script is running, it infinitely displays the spawn-point coordinates, vehicle number, and brake light status (ON or OFF) until terminated by the user.
Next Steps: - I'm waiting for approval by Professor Ruths before merging my pull request.
Projected Completion: Completed!
Update: Completed task with a ROS2 package!


Info.plist error extra info about

I will deploy ios app
Error: An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
No se pudo instalar “ThingsBoard PE App”

HI @ribera01,
I'll close it as a lot of time has passed, but if it's still relevant for you feel free to reopen with additional description.


Popover & Tooltip: focus reference element on tab if it's focusable

Please make sure these boxes are checked before submitting your PR, thank you!
Fixes #9748
Fixes #9920

[ ] Make sure you follow Element's contributing guide (中文 | English | Español).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

this change left a memory leak
https://github.com/ElemeFE/element/issues/19370


LSP: wait till port is up and parse it

This captures the LSP's output and waits until it announces its listening port. Then the connection is set up towards that port.

Avoids premature connect when the listening port is not ready yet. (This happened routinely on my Mac.)
Also avoids the fixing of a port number for LSP.
Also eliminates Viper-related junk from the distribution (reducing size) and reuses the artefacts that come with Viper itself.

CAVEAT: You'll need to install the "pre-release" Viper extension from the marketplace and (suggested) switch the tool download to Nightly.

This branch now appears to work as expected on Linux. Tested in the following environment:

Ubuntu 20.04 (WSL), OpenJRE 17
Nightly Viper Tools build version (required)
viper-ide v0.3.1 (default from marketplace)

I anticipate some additional corner cases, but this is a promising sign for reusing the viper-ide language server.

Fixed the unexpected error message offsets: https://github.com/dfinity/motoko/pull/3523
Verification is now limited to open documents, which fixes various issues when loading workspaces with multiple *.mo files.


Timeout error occurs when I try to navigate to certain url immediately after opening the browser.

Issue: Timeout error occurs when I try to navigate to certain URL immediately after opening the browser. But when I try to navigate second time, I was able to navigate.
Please make sure I am able to navigate to any url immediately after opening the browser consistently.
I am attaching the screenshot for reference.
Steps:
Expected behavior
I should able to navigate to any url immediately after opening the browser.
Actual behavior
I am not able to navigate to certain url immediately after opening the browser. Timeout error occurs. Only after second time i am able to navigate successfully.
Steps to reproduce

OpenBrowser()
goto("url")

Error: Navigation took more than 30000ms. Please increase the timeout.,
3. Repeat step 2 again.. Now it will work.

Suspect this is happening because whenever a browser is opened it is opened in clean state (i.e.) without any cache and localstorage with new profile, in the subsequent gotos there could be some requests loaded from cache which might make the load time lesser than the one done immediately after openBrowser since there will be no cache and everything has to be loaded from source when loaded for the first time.
Can you please try increasing the timeout?
goto("url",{timeout:60000})

@NivedhaSenthil  Even after adding timeout i am getting timeout error message.But i could see the url is launched.
goto("http://devtlnx4017.stbc2.jstest2.net/webui/",{timeout:60000})
Also i feel sometimes chromium browser is slow.Tough this issue is inconsistent.
please refer the screenshot attached.

@Prakash0989 Do you get the timeout error running your tests in headless as well? Or its always in the REPL?

Yes i am getting error running headless as well.

I think @saikrishna321  wanted to know if this happening only on REPL or even when running script in headless mode. Like,
code.js
const { openBrowser, goto, closeBrowser } = require('taiko');
(async () => {
    try {
        await openBrowser();
        await goto("google.com");
    } catch (e) {
        console.error(e);
    } finally {
        await closeBrowser();
    }
})();

and run taiko code.js does it timeout even then. To confirm if it an issue with REPL or with general execution.

I think there are potentially 2 issues wrapped up here. I will try my best to give a decent explanation.

I noticed in the REPL. If you take focus away from the chromium browser window (perhaps click another browser window or another application). Then return to the REPL and proceed to navigate the chromium browser will run the next action (e.g goto ('somewhere'). However, sometimes, the repl window will report an error

e.g Error: Navigation took more than 30000ms. Please increase the timeout., run .trace for more info.
If I can manage to consistently recreate this I will report it separately.
The reason I mention this is because I think it is occuring in some instances alongside issue 2 (below) and it all seems like it is part of the same problem.

@NivedhaSenthil to answer your question in the particular endpoint we are testing. The issue is in both the .code version and REPL. I think you are right that the speed of the endpoint is causing some of the issue with clean cache, I believe this is shown this can be seen by:
i. Hitting the same URL in the same REPL session twice. The second time it will usually succeed with loading.
II. Not everyone is experiencing the same issue with navigating to the site with either method.

However, the concern is when the page does appear to complete loading in ample time, but then the subsequent actions are not run. I'm not sure if the timeout you pass waits for anything particular to occur before it proceeds (or waits for the DOM to complete loading) with the next action?
As a guess - Maybe the loading of the page occurs in an obscure way passing what you are waiting to see but then it still doesn't have the next element available at this time the product is an off the shelf one, so i am limited in my understanding of how it works.

Guess Point 1 is related to https://github.com/getgauge/taiko/issues/369
Taiko waits for page load and first meaningful paint events by default for every load. Even when navigation timeouts subsequent action should happen from REPL wherein taiko runner will break on any error.

@NivedhaSenthil Should we just wait for first meaningful paint(that proves the content is loaded) to resolve and give access to the users to add waits on networkIdle and loadEventFired

Ideally yes waiting for firstMeaningfulPaint should ensure document load and page load, that way user don't have to wait for networkIdle and loadEventFired since those event should get triggered before firstMeaningfulPaint.  I feel it will be great to give user the flexibility to choose any events to wait for and if not given default to firstMeaningfulPaint.
This may not be related to to the timeout issue though.

Dear Team, Do we have any update on this inconsistent issue which is blocking me to move forward.
Even with google.com i am getting timeout exception.

@NivedhaSenthil Still i am getting timeout error. Sometimes I also observe chromium browser response speed is slow, compare to other browser's at same time.

@Prakash0989 you have installed Taiko globally from the master, are you sure the project has Taiko from master?
Can you make sure in your package.json has "taiko": "git+https://github.com/getgauge/taiko.git", if Yes, please remove the node_modules (rm -rf node_modules) and run npm test to make sure you have the latest master.

@saikrishna321  Still i am facing the same issue. Can you please look into my screenshot attached.
Additional information:

Always 1st navigation fails and sometimes its understandable navigation took more than the specified time ( But not always,  even after successful navigation, timeout exception occurs)
In my case, my application fails even after successful navigation (Attached screenshot)

@Prakash0989 can you please provide more info about your environment like OS, npm and node versions?
It is very difficult to fix such issue without a repro, I don't face any issue with navigating to google.com.

node -v : v11.0.0
npm -v  : 6.4.1
System Details:
Mac OS High Sierra, version : 10.13.3
Model Name:	MacBook Pro
Model Identifier:	MacBookPro14,1
Processor Name:	Intel Core i5
Processor Speed:	2.3 GHz
Number of Processors:	1
Total Number of Cores:	2
L2 Cache (per Core):	256 KB
L3 Cache:	4 MB
Memory:	16 GB

@Prakash0989  Thanks for the info.
You did say you cant navigate to google.com and it timeouts https://github.com/getgauge/taiko/issues/393#issuecomment-463936172
Did you try on other machine ? Are you behind proxy network? Can you try switching to different network and try ?

@saikrishna321 : I understand sometimes google.com takes longer time ( more than 2 mins to load completely) hence navigation timeout error occurs .Thats fine. Its different story, we have to see why its taking longer time to load only in chromium browser not in other browser at same time. As mentioned, this issue is inconsistent.
I am more concerned when my application fails with navigation timeout error though the page gets navigated completely. Please refer the screenshot which i mentioned in my previous comments.
To answer your question, regarding proxy network, i was able to open  same web applications in other browser without any issues.

If you are behind proxy, can you please try setting proxy command line args like given here to see if it helps ?

I am seeing the same issue with master. The page was loaded but the test failed the timeout error.

@yingzuo can you pls share the URL or sample to reproduce

The URL I used is not public accessible. It is an authenticated page, so there's a redirect going on. I can't reproduce the issue with 'google.com'.

If you are behind proxy, can you please try setting proxy command line args like given here to see if it help

If you are behind proxy, can you please try setting proxy command line args like given here to see if it helps ?

@NivedhaSenthil Please let me know once your available for call.Let me share my screen and we will sort out this issue.  Below is the link to join the call. (Kindly Inform me before you join this link)
https://tcs.webex.com/meet/k.prakash2
@suleytron

@NivedhaSenthil Please let me know once your available for call.Let me share my screen and we will sort out this issue. Below is the link to join the call. (Kindly Inform me before you join this link)
https://tcs.webex.com/meet/k.prakash2
@suleytron

@Prakash0989 @suleytron can you try with master, we have {waitForNavigation: false} added to goto()

@saikrishna321 I have pulled the latest changes from master and gave a try. I am able to see navigation timeout is skipped, since we have added {waitForNavigation: false},but then after my navigation step( step1), immediately it looks to execute the next step(step 2) which is inputting the user name and it fails since navigation is not originally completed. Can you provide me a suggestion/solution so that i instruct to wait for specific time interval before executing step 2. similar to sleep command before executing the step2.refer screenshot for reference.

write api does not accept plain text currently,  this need to be handled in Taiko.
you can try write('something',into(inputField({id:'id'}))) this will wait for the inputfield and then writes into it

focus and then write to the field. See if that works as well

@NivedhaSenthil @saikrishna321  Please refer the screenshot attached. I have skipped navigation timeout by adding {waitForNavigation: false},but then as i mentioned in my above comment, once url is launched in browser, immediately it goes on to execute the next step which is, looking for Input field. Since the URL is not completely loaded, input field is not visible or not loaded in this point ,hence failing to see input field in DOM. can you provide me some solution so that i wait for element to be visible in DOM .Any keyword which waits until the element is visible will do.
navigation workaround observation.docx
@suleytron

exists method in selectors should ideally wait for the element to appear, default timeout is 10sec and it should be configurable. That feature seems to be broken now https://github.com/getgauge/taiko/issues/406
you could still try await inputField({id:'id'}).exists() before focusing which will wait for element to exists within 10 secs.

@NivedhaSenthil Tried with 'exists' method but no luck. Understandable its going to fail since my navigation is taking more than 10sec. Let me know once exists method configurable feature is fixed so that i can configure and will give a try.
Also please feel free to add any another solution to this issue.
exists functionality.docx
@suleytron

Raised an issue in devtools protocol to understand why firstMeaningfulPaint event is missed https://github.com/ChromeDevTools/devtools-protocol/issues/159.
Meanwhile you can try waiting for custom events, like
await goto("google.com",{waitForEvents:['loadEventFired']}). Changes are in master yet to be released.

Finally its working. Thanks for your workaround. Lets keep this issue open until original issue is resolved.

@NivedhaSenthil Today I have pulled the latest changes from master and when I execute I am getting some exception.(Refer screenshot). The reason behind executing from master is i believe 'waitforevents' workaround is released only in master. Note, i was not getting same exception when i execute from latest version of taiko, only getting exception from master. Assume some changes are made in master. Refer the screenshot attached and add your thoughts.

Can you please tell us what command you are using to run gauge test suite ?
yes there are some changes done around taiko runner, seems that is causing the issue. We will be fixing and making a release soon with waitForEvents

@NivedhaSenthil Tried the below two commands

npm test
gauge run specs/create_and_approve_single_sku.spec

Fixed via https://github.com/getgauge/taiko/issues/430

@NivedhaSenthil Thanks for the quick fix. Able to run gauge taiko tests

Hello!
Is the timeout issue has already been resolved? I am currently experiencing timeout issues intermittently when checking for multiple pages in a single scenario.
SPECS:
`
Validate URL Redirection

Goto Sample UPWA Homepage
Open page "bussmann"
Page lands in brand directory page
Close browser
`

Please note that sometimes it works, sometimes it is not. Please advise. Thank you!

Sometimes this issue is encountered. All test specs PASSED but a timeout is still encountered.

@qaryas  you have a test closing the browser? why? Do you have an additional afterSuite closing the browser again? Maybe that's the timeout happening?

Seems you are right @paulwellnerbou. It seems to be working perfectly without the close browser. Thanks!

Seems you are right @paulwellnerbou. It seems to be working perfectly without the close browser. Thanks!

Ooops! Encountered Error Message: Error: Timed out again without the close browser. :(

@qaryas Are you able to reproduce issue with taiko example project?

to reproduce issue with taiko example project?

@JaniJegoroff , No, it is only happening in the project I am currently working with.

ChromeDevTools/devtools-protocol#159

This worked for me as well. Thank you!

Raised an issue in devtools protocol to understand why firstMeaningfulPaint event is missed ChromeDevTools/devtools-protocol#159.
Meanwhile you can try waiting for custom events, like
await goto("google.com",{waitForEvents:['loadEventFired']}). Changes are in master yet to be released.

This worked for me as well. Thank you @NivedhaSenthil !

I'm seeing the same issue.  Unfortunately I don't have a simple test case for you, and see it in my app.
Using waitForEvents:['loadEventFired'] in goto, does seem to work around the issue.
Before I saw that workaround, I had tried using waitForNavigation = false, and hit #922.
My app has websockets.  Is it possible that's the cause of this issue?  Watching the network tab, it does show the websocket request is always pending.

Updating my comment above - it turns out the waitForEvents:['loadEventFired'] doesn't really solve the issue.  Problems just seem to move around to different test steps and cause random hanging of commands.  Looking at the code, I assume that's because its not just gotos that are waiting on network requests.
However I finally figured out what the cause was in my case.  The problem is that we use various 3rd party services.  Some of them frequently pinging their servers.  Two examples are Log Rocket and Intercom.  I highly suspect that their constant traffic to their servers is causing issues for Taiko's network waiting mechanisms.
To test my theory, I modified Taiko code (networkHandler) to whitelist which requests it watched.  That worked.  I also tried turning off those services during test runs.  That worked as well.
I imagine it would be nice to have Taiko support a whitelist feature so we don't have to modify our app for test runs.  However I'm not convinced the issue is really the frequent pinging of these services.  I still occasionally see Taiko get stuck (but it's so infrequent its very hard for me to track down further).  I think there still can be an issue within Taiko code itself, or made the Chrome protocol.  It's not clear to me.  Regardless, if you want a fairly reproducible way of seeing Taiko get stuck, as Intercom and Log Rocket to your app.  With that in place, I could reproduce the issue on our app, in about 5 Taiko commands.
I'm not sure if this info is related this issue or not, and happy to file a new one if you'd like.

Does using intercept to add those url's act like a whitelist?
Either way this needs fixing for apps that use those services. The assumption was that services like Intercom and Log Rocket are turned off on test instances. But it must be possible to run Taiko scripts against production instances.
Thanks for investigating and finding the cause can you create a separate issue for this?

In my case, it the error ("Navigation took more than 30000ms. Please increase the timeout") is shown if the URL I'm navigating to loads TOO quickly (ie: from localhost).
In our Rails dev environments, we use a local tool called "Letter Opener". It's a local Inbox that traps any email your Rails app would normally send out to the world when in production. It's small, lightweight, and after a few times loading it, will reload lightening quick.
goto() and openBrowser() both use this option when they start navigation. The default value for the "waitForStart" option is 100ms.
When I dialled this back down to 0ms, the error no longer appears for me. Setting it back to 100, and the error returns. Seems like some events fire before Taiko has a change to spot them.
await goto("https://localhost:3023/letter_opener", { waitForStart: 0 })
see https://taiko.gauge.org/?#taiko-wait-mechanism


(Question) There's a CLI tool?

Like the official Lua interpreter.

it's not very full featured, but https://github.com/kyren/piccolo/blob/master/examples/interpreter.rs


[NEW ICON] Ubuntu/Distros Linux

Skill Name
Ubuntu
Why?
Ubuntu is one of the most widely used Linux distributions, and it would be interesting to have its icon as well as icons of other distros.
Reference Image

Added in e67133b!


fix: Slide export without slide per click (#1416)

Closes https://github.com/slidevjs/slidev/issues/1416 by disabling clicks when in print mode

I'm so sorry that I worked on this at the same time (#1419)
IIRC using useNav() inside useClicks.ts will cause HMR-related problems. So I think maybe #1419 may be a better fix.
Thanks for your contribution!


Fix: Improve sharpness of thumbnail previews

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #10067...

Before:

After:

File Explorer

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)
Add screenshots here.

After != File Explorer, visually it is still noticeable that it is not like in File Explorer, sharper but still not so good for the eyes hmm


New SI summary table

*Issue:*https://github.com/bcgov/entity/issues/19062
Description of changes:

Create a new Table component in btr-common-components
Update the SummaryTable in btr-main-app

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-89-3hj8sw4m.web.app


Refactor to handle new keyrings with bridge dependencies

The PR was initially going to add code to handle an asynchronous init method for keyrings. But now it has more changes, many of them breaking changes.
Related PR for eth-trezor-keyring.
https://github.com/MetaMask/eth-trezor-keyring/pull/143
Summary
New `init` method
Adds support for asynchronous `init` method present in some keyrings. It'll only be called if it exists to preserve compatibility.
Keyring Builder Functions (BREAKING CHANGE)
Adds support to inject bridge logic into keyrings. This is a breaking change as it means that we no longer have an array of classes that can be instantiated, but an array of keyring builder functions that return an instance.
This is done so that MetaMaskController can provide the KeyringController a builder function for a keyring that can contain MV2, MV3 or Node logic to communicate with a hardware device. It will also allow us to, eventually, change the bridge logic dynamically.
This means no longer passing an array of classes, but an array of builder functions. A keyringBuilderFactory function is exported in order to assist with this task.
It also means the internal property called keyringTypes is now replaced with keyringBuilders.
Moved keyring instantiation logic to a single private method
`_restoreKeyring` and `addNewKeyring` were both creating new instances. The logic has been moved to a single place so that we can make sure that, after instantiation, we call `deserialize` and `init`.
Replace `getKeyringClassForType` with `getKeyringBuilderForType` (BREAKING CHANGE)
This method is used mostly internally, but also by `seed-phrase-verifier` in the extension.
Missing await when adding accounts for HD Keyring
Adds a missing await in the `addAccounts` method for the `HD_KEYRING`, which is asynchronous and it is currently not being awaited.

Thanks @bergarces, that would be great! If we can get this into the extension and update the keyrings to use this builder API one-at-a-time that would be ideal.


Add abiotic documentation

This PR adds the theory for the abiotic components of the Virtual Ecosystem. So far, I have added the overview and microclimate, I would appreciate feedback on structure and content before I put a lot of effort in adding references and repeating the exercise for the hydrology.
You can read the docs here
https://virtual-ecosystem.readthedocs.io/en/add_abiotic_documentation/virtual_ecosystem/abiotic_theory.html
https://virtual-ecosystem.readthedocs.io/en/add_abiotic_documentation/virtual_ecosystem/microclimate_theory.html
Type of change

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

[x] Make sure you've run the pre-commit checks: $ pre-commit run -a
[ ] All tests pass: $ poetry run pytest

Further checks

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works
[x] Relevant documentation reviewed and updated

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.91%. Comparing base (19d24a1) to head (e7dbea9).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #500   +/-   ##
========================================
  Coverage    94.91%   94.91%
========================================
  Files           70       70
  Lines         3857     3857
========================================
  Hits          3661     3661
  Misses         196      196

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


Fix list update typing on list to enable partial updates

I added Partial type around type parameter in update operation, to enable partial updates, as claimed in docs

@googlebot I signed it!


[java_api] "Unable to read ONNX model on Android platform" or "ONNX model loading issue on Android platform"

`FATAL EXCEPTION: main
Process: com.xmut.openvinotest1, PID: 20544
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xmut.openvinotest1/com.xmut.openvinotest1.MainActivity}: java.lang.Exception:
InferenceEngineException:
ReadModel: Exception from src/inference/src/cpp/core.cpp:90:
Exception from src/inference/src/model_reader.cpp:160:
Unable to read the model: /storage/emulated/0/data/rec.onnx Please check that model format: onnx is supported and the model is correct. Available frontends:
                                                                                at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3177)
                                                                                at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3314)
                                                                                at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
                                                                                at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:113)
                                                                                at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:71)
                                                                                at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2043)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:106)
                                                                                at android.os.Looper.loop(Looper.java:224)
                                                                                at android.app.ActivityThread.main(ActivityThread.java:7096)
                                                                                at java.lang.reflect.Method.invoke(Native Method)
                                                                                at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
                                                                                at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:928)
                                                                                Caused by: java.lang.Exception:
                                                                                InferenceEngineException:
                                                                                ReadModel: Exception from src/inference/src/cpp/core.cpp:90:
                                                                                Exception from src/inference/src/model_reader.cpp:160:
                                                                                Unable to read the model: /storage/emulated/0/data/rec.onnx Please check that model format: onnx is supported and the model is correct. Available frontends:

                                                                                at org.intel.openvino.Core.ReadModel(Native Method)
                                                                                at org.intel.openvino.Core.read_model(Core.java:31)
                                                                                at com.xmut.openvinotest1.MainActivity.onCreate(MainActivity.java:34)
                                                                                at android.app.Activity.performCreate(Activity.java:7264)
                                                                                at android.app.Activity.performCreate(Activity.java:7255)
                                                                                at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
                                                                                at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3157)
                                                                                ... 11 more`

Hi,
Could you clarify:

Which OpenVINO version are you using?
Which sample OpenVINO app areyou using (If any)
Steps that you did till encountered that error
Your hardwares information

Hi,
Could you clarify:

Which OpenVINO version are you using?
Which sample OpenVINO app areyou using (If any)
Steps that you did till encountered that error
Your hardwares information
Your ONNX model details (related files, url, etc)

Closing issue, feel free to re-open or start a new issue if additional assistance is needed.


Fixes #169 no artifacts/ created after operator-sdk scorecard fails

The proposed code encapsulates stderr from operator-sdk scorecard to artifacts/.

@rocrisp please make sure to squash all your commits into one.


combine multiple selections into a single summary (e.g., "3 items selected")

Hi,
Is it possible to have a multiple selection without tags ?
in the selection, we would have something like : 3 items selected.

Tagging and multi-select are two distinct features.  Please avoid using the term "tag" because that actually refers to dynamic option creation.

FWIW, it would appear that Bootstrap multiselect supports this feature.  It might already be doable in Select2 with templateSelection - I'm not really sure.

Have a look at my fiddle. I managed to put something together
https://jsfiddle.net/Lkkm2L48/7/

Nice!  Seems like we need some sort of place to organize community-contributed solutions like these.  Maybe this would be good to post in the new forums, under Ecosystem?

This appears to be a duplicate of #2965.


Uncaught TypeError

Please see this PR
https://github.com/shahradelahi/coinmarketcap/pull/1
Function return type is array, but was attempting to return null on occasion
Regards

Thanks for the contribution.