NuKeeper throws System.InvalidOperationException on start

🐛 Bug Report
Nukeeper throws System.InvalidOperationException on start
Expected behavior
Nukeeper will not throw an exception.
Reproduction steps
Run
 nukeeper repo "http://<IP_ADDRESS>/repo.name/name.base/_git/name.framework.abstractions" myverylongpersonalaccesstoken --platform "AzureDevOps" --verbosity detailed

System.InvalidOperationException: Sequence contains more than one matching element
   at System.Linq.ThrowHelper.ThrowMoreThanOneMatchException()
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
   at NuKeeper.Commands.RepositoryCommand.TryGetSettingsReader(Uri repoUri, Nullable`1 platform) in d:\a\r1\a\_NuKeeper PR Build\drop\NuKeeper\Commands\RepositoryCommand.cs:line 87
   at NuKeeper.Commands.RepositoryCommand.PopulateSettings(SettingsContainer settings) in d:\a\r1\a\_NuKeeper PR Build\drop\NuKeeper\Commands\RepositoryCommand.cs:line 55
   at NuKeeper.Commands.CommandBase.OnExecute() in d:\a\r1\a\_NuKeeper PR Build\drop\NuKeeper\Commands\CommandBase.cs:line 100
   at McMaster.Extensions.CommandLineUtils.Conventions.ExecuteMethodConvention.InvokeAsync(MethodInfo method, Object instance, Object[] arguments)
   at McMaster.Extensions.CommandLineUtils.Conventions.ExecuteMethodConvention.OnExecute(ConventionContext context, CancellationToken cancellationToken)
   at McMaster.Extensions.CommandLineUtils.Conventions.ExecuteMethodConvention.<>c__DisplayClass0_0.<<Apply>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at McMaster.Extensions.CommandLineUtils.CommandLineApplication.ExecuteAsync(String[] args, CancellationToken cancellationToken)
   at NuKeeper.Program.Main(String[] args) in d:\a\r1\a\_NuKeeper PR Build\drop\NuKeeper\Program.cs:line 35

Link to the line
Configuration
Testing on Azure Devops. Had some issues so I tested it using CLI
I'm checked out on develop branch
Logged in to Git server
Version: 0.33.0
Platform if applicable:

[x] :hammer_and_wrench: NuKeeper CLI
[ ] :sparkles: GitHub
[x] :robot: AzureDevops
[ ] :checkered_flag: Bitbucket
[ ] :earth_americas: Gitlab
[ ] :tv: Gitea
[ ] :whale: Docker

I downloaded and debugged the code. The current code here                 return _settingsReaders.Single(s => s.Platform == Platform); is wrong.
The code _settingsReaders.Where(s => s.Platform == Platform).ToList(); returns 3 items with type AzureDevOps

For my purposes I was able to use First(s => s.Platform == Platform) but obviously that's just my quick fix.


Version UP

Description
Please include a summary of the change and which is fixed.

openssf score badge add to main README
version up for #570 #571 release

How has this been tested?
Please describe the tests that you ran to verify your changes.

[ ] UnitTest
[ ] Benchmark

@Samsung/credsweeper_maintainers please approve the PR on trust, without checks now - the will pass after #570 #571


Update profile.php

Hey @myid13221 !!
Your code has certain bugs. I have rectified some of them.
Kindly have a look.
Thanks!!

Thanks, for the changes!!
Ya, I cam to knew that the PHP script was throwing unnecessary errors. May be because of the same issue.
Thanks for the changes.
#hacktobefest-accepted


too many arguments in call  to types.Eval in lint.go:1480

github.com\golang\lint\lint.go:1480: too many arguments in call to types.Eval
github.com\golang\lint\lint.go:1480: assignment count mismatch:2=3

You have an out of date dependency. Run the command in the README.


Create a Parquet IO Manager

Create a dagster IO Manager that can read and write parquet files using pandas or dask data frames. Dagster provides a nice example for this type of IO Manager.
This enables us to create assets that depend on CEMS data without needing to handle the IO management.

I'm still trying to work out the best way to implement this. I have two questions:

It might be difficult to take advantage of parallelism with dagster and produce a single epacems parquet file. Could we distribute a directory of parquet files where each file is a partition? It looks like dask supports loading partitioned data from a directory.

Where can I find examples of analyses or output tables that load data from CEMS?

You probably already saw it, but the code for producing a bunch of partitioned parquet files in parallel is already in there, it's just not the default output.


fix: store changes persistent

Apply changes to settings to allow fixed store.

Hey @dotmafia
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


python311Packages.versioneer: Fix hash

Description of changes
Fixed the hash mismatch
I diffed the new source with the cached source and the only difference is the following:
--- source-in-cache/_version.py 2023-11-14 17:17:39.434728709 +0100
+++ /nix/store/7z2m4szfp863y9bp1vsffflk22dyw1ci-source/_version.py      1970-01-01 01:00:01.000000000 +0100
@@ -26,7 +26,7 @@
     # setup.py/versioneer.py will grep for the variable names, so they must
     # each be defined on a line of their own. _version.py will just call
     # get_keywords().
-    git_refnames = " (HEAD -> master, tag: 0.29)"
+    git_refnames = " (tag: 0.29)"
     git_full = "28c613dbef5fce09dc3ba6b1baa811c2d76b2245"
     git_date = "2023-07-07 10:50:03 -0400"
     keywords = {"refnames": git_refnames, "full": git_full, "date": git_date}

I suspect upstream changed the GitHub release.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I diffed the new source with the cached source and the only difference is the following:

Can you put that in the commit message? (Tip: If you start out with patch descriptions in git, it will be automatically copied to the PR message.)

I diffed the new source with the cached source and the only difference is the following:

Can you put that in the commit message?

Done!

I see it causes more than 1000 rebuilds (general staging branch threshold), but I think since this is python packages they are quicker to build and it can be merged directly to master.


Updates and upgrades

Hey @straubt1,
Care to check out the changes in this rewrite?

@ksatirli I am late to the party, but did find one minor issue when running the basic example.
Basic example:
$ terraform init
Initializing modules...
- keybase_domain_proof in ../..

Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 4.29.0 does not match configured version constraint >=
│ 4.30.0, < 5.0.0; must use terraform init -upgrade to allow selection of new versions

Removing the .terraform.lock.hcl file worked in the examples/basic directory, it seemed to conflict with the one inside the module.


Whitespace fix

I think the whitespace for this file got borked after our messing around creating a release and a new branch.

Are we versioning this file in the end? I thought we bring it with grunt

maybe you're right and we shouldn't have any of the showcase and its assets versioned. However, they all currently are (and are in release 1 too...).

So at the moment its just the .js and .css we are building right? Html we are versioning?

At the moment it's arguably a bit messed up. We're building the showcase and copying it into our public folder, where it gets renamed and used. Everything from that build is versioned.. apart from the styles.css as we've excluded that. Doesn't make a great deal of sense.
Perhaps we should unversion and remove all the built showcase files. The reason we versioned them originally is because we weren't sure if we were going to be making changes to them before/after building them (including hooks or buttons etc), but we haven't done that yet... YAGNI...

ok so i am just making another pr to cleanup a bit, as this keeps tripping my git

Made redundant by #66


Test report from pytest will not be read properly

During parsing, Reqstool finds the report.xml file generated from pytest, but it can't read the test case element(s) of the root node.
See line 37 in test_data_generator.py
A sample xml file is provided here
The report file could also be generated using the following:
hatch run test:pytest --cov=reqstool-client --cov-report=xml --cov-report=html -o junit_family=xunit2 --junitxml=dist/report.xml

Is it possible to use junit_family=xunit1?
https://docs.pytest.org/en/7.1.x/deprecations.html#id22

This has been fixed here.


When adding a Skill to a project, if you have a dialog selected it adds it to the dialog not the root bot

Describe the bug
If you have a Bot with a dialog and have this dialog active when adding a Skill, the Skill trigger is incorrectly added to the dialog not the root Bot which is where Orchestrator is configured.

Version
2.0.0-nightly.240366
Browser

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

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create a new bot
Create a new dialog
Make this new dialog active
Add a skill  - e.g: https://djtest6.azurewebsites.net/manifests/djbfskill1-2-1-manifest.json

Expected behavior

Skill trigger added to root bot

@darrenj before we address this we need a PM owner to help reconcile your expectation with how recognizers compose with dialogs

A recognizer is scoped to a root-bot or sub-dialog. With a mixed recognizer infrastructure triggered by adding a Skill (Orchestrator and LUIS) we made the decision to reinforce the recommend pattern of having triggers in the root dialog which then "begin" child dialogs. This ensures that the child dialogs continue to use the recognizer of their choice (e.g. LUIS) and are not side-affected by switching to Orchestrator which would for example mean dialogs that use entities would stop working. By registering skills at the root level (using Orchestrator) we side-step this issue.
Hence this issue related to the fact that if we allow you to register skills elsewhere we end up with a situation where existing functionality can be impacted by adding a skill/orchestrator. If were to ensure skill registration happened at the root we would avoid this.
There's a broader issue here too, when adding a dialog we don't apply the best practice (?) we have of having a trigger than uses begin dialog on a child dialog. This is something I think we should look at too.
Can you help take a look and my thoughts above @garypretty and land on a direction, perhaps short-term and longer term (r15)?

Sync with @srinaath on this issue to ascertain if a short term fix to always add the trigger for a skill to the root was straightforward.  Srinaath confirms that this is the case and so I would like us to implement just that fix for R14.
I am key not to increase scope for R14 at this stage, so we can track the issue of best practice use of a dialog and @cwhitten's broader point about recognizer composition in a future milestone.

The line to add the fix https://github.com/microsoft/BotFramework-Composer/blob/main/Composer/packages/client/src/components/AddRemoteSkillModal/CreateSkillModal.tsx#L201. We need to pass the root dialog id here for the trigger to be added to the root dialog.

I see this needing to be special-cased around Orchestrator:
IF a user is adding a skill, AND Orchestrator is already configured at the root, OR this is the first skill the user is adding AND at the prompt decides to also add Orchestrator, we add it to the root bot.
I'd expect that the existing behavior would persist if they do not have Orchestrator configured and have not told Composer to install Orchestrator as part of adding a Skill.
This is special app-code that would sit on top of the framework, which is the issue we need to understand clearly: Should Composer only be adding Skills to the root dialog in all cases? This brings up some interesting scenarios to think about, like how a BF Package providing a dialog that calls a Skill would no longer be supported in Composer as it would be added as a child dialog and not the root. Do we want to be able to call a Skill from a Package? This in my mind would be the R15 thinking cc @darrenj  @garypretty

I see this needing to be special-cased around Orchestrator:
IF a user is adding a skill, AND Orchestrator is already configured at the root, OR this is the first skill the user is adding AND at the prompt decides to also add Orchestrator, we add it to the root bot.
I'd expect that the existing behavior would persist if they do not have Orchestrator configured and have not told Composer to install Orchestrator as part of adding a Skill. However I could see the need to be flexible here in the short-term.
This is special app-code that would sit on top of the framework, which is the issue we need to understand clearly: Should Composer only be adding Skills to the root dialog in all cases? This brings up some interesting scenarios to think about, like how a BF Package providing a dialog that calls a Skill would no longer be supported in Composer as it would be added as a child dialog and not the root. Do we want to be able to call a Skill from a Package? This in my mind would be the R15 thinking cc @darrenj @garypretty

@cwhitten Made the logic specific to Orchestrator sounds reasonable to me, otherwise, it sounds like a big breaking change.  Should we move forward on the engineering side on this now or we want to wait till @darrenj or @garypretty  confirmation?
If we can move forward, @lei9444 can you take this one?

@darrenj Are we ok with this change? @lei9444 PR ensures to check the root dialog's recognizer is Orchestrator or if the user chooses Orchestrator in the recommendation modal and then adds the new skill caller trigger to it.

(@vivekkshankar fyi)

Yes, this seems like a good way forward for now and give us time in R15 to think carefully about scenarios/patterns we want to support and those we want to encourage not!
Thanks all


Peer-to-peer review #1:

Works section, for SEO and others, should use UL tag instead DIV tag.
Should use wrappers only when necessary.

Thanks, guys for your time and your advice to improve my code. 👍

Please add all the unnecessary files into your Gitignore before pushing any changes.


OmniSharp shows errors in Problem panel of not built projects

Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version:   2.2.103
Commit:    8edbc2570a
Runtime:
OS Name:     ubuntu
OS Version:  18.04
OS Platform: Linux
RID:         ubuntu.18.04-x64
Base Path:   /usr/share/dotnet/sdk/2.2.103/
Host (useful for support):
Version: 2.2.1
Commit:  878dd11e62
.NET Core SDKs installed:
2.1.503 [/usr/share/dotnet/sdk]
2.2.103 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
VS Code version:
1.31.0
C# Extension version:
1.17.1
Steps to reproduce

Create solution with multiple projects
The main (app) project should reference other projects except one (it should not be relevant to build it)
Open solution in VSCode
Build it
Wait for OmniSharp to load it

Expected  behavior
0 errors in problems Problems panel. Files in excluded project not showing any errors
Actual behavior
Tons of errors in Problems panel. All code in *.cs files is "red".
Most problems say something like: "Predefined type 'System.Object' is not defined or imported [ExcludedProjectName]"
OmniSharp floods Problems panel with these "errors" making it of no use (as I see 1000+ errors in it).
They dissapear only if I make build of this project manually (dotnet build ExcludedProjectName.csproj). I suspect it creates "obj" and "bin" folders which OmniSharp uses.

@AOne-T You can use the folder icon in the lower left to choose the active project/solution. If you have an active solution, OmniSharp will not perform dotnet restore on other projects. You're correct that you'll need to manually restore projects that omnisharp is not tracking.

As you can see on the screenshot, the solution is loaded. Also using the "vscode-solution-explorer" extension I show that the problematic project exists in solution. But for now it is not referenced by any other project. And the main application project (that is configured to build and start) doesn't reference it either. So it is not build. And dotnet restore doesn't help: it reduces the number of errors (obvious errors about System.Object), but leaves a lot of others.

@AOne-T Can you share your OmniSharp log? Output -> OmniSharp log? It would also be helpful if you could share the csproj that isn't loading or at least describe it.

I managed to create sample solution for you. It reflect what we use. And we use $(SolutionDir) environment variable throughout our projects because we extensively use git submodules and it really helps, but it does bad for OmniSharp as we experience some strange problems and cannot test and debug tests using "Test lens" (or how they are called) - see https://github.com/OmniSharp/omnisharp-vscode/issues/2435


Property name mapping doesn't support underscore at the middle of the property name?

Hello,
I just found a problem of property name mapping when we have underscore at the middle of the property.
This is linked to
https://github.com/aryaxt/OCMapper/issues/46
My Model is:
@interface User : NSObject
@property (nonatomic) int user_id;
@property (nonatomic) NSString* registration;
@end

The dictionary is:
{
    registration = "my test registration";
    "user_id" = 10;
}

However OCMapper mapped user_id to userid(without underscore), I guess this is not supposed to be, you may want to map userid to _userid but forgetting the case when we have underscore at the middle.
Ok, I see the code in
    @implementation ObjectInstanceProvider

    // Support underscore case (EX: map first_name to firstName)
    caseInsensitivePropertyName = [caseInsensitivePropertyName stringByReplacingOccurrencesOfString:@"_" withString:@""];

I just saw that automatic underscore mapping from the latest changelog, but what if we want to keep the same name as in he dictionary?

as a workaround, I just removed that line of code,
but it would be better if it can allow user to choose wither default same name mapping or differen name mapping.

Hi, yes sorry this is not supported, objective c property naming convention is camel case

That was really annoying, spent two hours debugging it to discover that the component remove the underscores in the var names.
As I want to use the Pod, can that replace be optional instead of compulsory?


Optimize library size

Hi,
I have noticed that on android it ship with multiples files that aren't accessible:
org/bouncycastle/pqc/crypto/picnic/lowmcL5.bin.properties
org/bouncycastle/pqc/crypto/picnic/lowmcL3.bin.properties
org/bouncycastle/pqc/crypto/picnic/lowmcL1.bin.properties
org/bouncycastle/x509/CertPathReviewerMessages_de.properties
org/bouncycastle/x509/CertPathReviewerMessages.properties
org/bouncycastle/pkix/CertPathReviewerMessages_de.properties
org/bouncycastle/pkix/CertPathReviewerMessages.properties
Those files adds a total of 1.2MB to the apk size and aren't accessible to the android application, would it be possible to remove those files from the library ?
Thanks

Thanks for the report!
Am I correct that this is simply a resource.excludes.add for each of these?

That's what I use on my end yes


Add Following page

Can reuse the existing ChannelList components. There should be an API endpoint for this somewhere...

Early version: https://github.com/Glimesh/glimesh_app/commit/95b0a0a9aaa5fa4759237850612f654eb10560a0

This is mostly implemented now, we can make future issues for specific functionality.


Strip suffixes from the Lift class

It's better not to try and indicate what we're lifting "to" in the
names, as TH does.
Just pushing through a few final renames for friendliness.

In this case it's mostly renaming the functions that matters, most users won't see the typeclass.

The reasoning is:

The suffixing of the Lift class and methods is already semantically unclear. Is it what you're lifting from? What you're lifting to?
Technically when you lift a Haskell value in your contract you're lifting it into PLC, but the other stuff is talking about PlutusTx, so it's all very confusing. OTOH if it's just PlutusTx.lift then the connotation is just "lift as appropriate for PlutusTx", which is what we want.
This is similar to what TH does. That way they also sidestep the question of whether it should be LiftQ or LiftHsSyn or whatever.

As for potential clashes with lift - I don't think this is that much of a problem in practice. Qualified imports! Again, this is the same as TH and I've never had that be a problem.


allow streaming

if possible, can you expose the stream interface from request?

@seanc i plan to allow to pass anything to the request object


How does diffrax handle state variables becoming inf?

I'm trying to port some code from pure python to JAX. The code is a bit complicated with time-varying interpolated inputs but essentially involves solving a system of 8 coupled ODEs. The state variables and independent time variable span a large dynamic range so the system is solved in logarithmic form (i.e., read in 10^logt and 10^logy, do calculations in physical units, return dlogy/dlogt). The system is stiff but my pure python implementation based on scipy.integrate.solve_ivp leads to reasonable solutions for multiple solvers (the implicit methods BDF and Radau being the best, but RK23 and DOP853 also finish and give similar solutions though require lower tolerances and more steps; all of these agree with my manual Euler integrations with extremely small fixed timesteps, increasing my confidence in the solutions).
However, all of the adaptive diffrax solvers I've tried fail and JAX's odeint also fails. Both packages only get 4 steps in before they return NaN's (and diffrax hits up against max_steps=10K whereas scipy only needs 300 for BDF and 3000 for RK23). I used print/jax.debug.print() statements inside my integrator function to print the values of the state variables and their associated derivatives for both the pure python and JAX versions of my code. I find that early on, the derivatives for one or two of my state variables blows up (dlogy/dlogt=10^6) so in the next step, the value of that state variable becomes inf, and then that leads to NaN's. solve_ivp is able to deal with this by repeatedly going back to an earlier time and taking ever smaller timesteps, eventually getting over this initial hump. But both jax-odeint and diffrax remain stuck with NaN's. I was hoping diffrax's implicit solvers and adaptive step-size controller would help compared to the default jax-odeint one, but it has the same problem.
Should diffrax/jax-odeint be able to adapt to state variables becoming inf? Why is solve_ivp successful?
I can probably share a self-contained github repo with two example Jupyter notebooks comparing solve_ivp to diffrax/jax-odeint if that would help.

This sounds like an interesting problem! Diffrax should definitely be able to handle this kind of thing (at least, anything that solve_ivp can handle), and I've definitely had Diffrax detect NaNs, and go back and make smaller time steps until we get past the problematic region. C.f. this line in the integrator.
Perhaps the issue is that this line currently only checks for NaNs, but we should really be checking for infs as well, i.e. jnp.isnan(...) -> jnp.invert(jnp.isfinite(...)). You could try adjusting that line and seeing if it helps? If so I'd be happy to take a PR tweaking this.
Just to check, are you using 64-bit floats? (JAX_ENABLE_X64=1 python file.py)

An inf in y_error will force a step rejection, and subsequently shrinking the step. In practice this will be by the minimum amount of PIDController(factormin=...); the default is 0.2.
Ah, I had a typo in my previous suggestion. What happens on your problem if the line is changed to:
y_error = jtu.tree_map(lambda yei, yi: jnp.where(jnp.isnan(yei) | jnp.invert(jnp.isfinite(yi)), jnp.inf, yei), y_error, y)

?


Zombie process created every minute

:lady_beetle: Describe the bug
Every minute, a new zombie process is created while running ntfy server.
:computer: Components impacted
ntfy server
:bulb: Screenshots and/or logs
$ ps aux | grep 'Z'
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
appuser   857529  0.0  0.0      0     0 ?        Z    16:30   0:00 [ssl_client] <defunct>
appuser   857759  0.0  0.0      0     0 ?        Z    16:31   0:00 [ssl_client] <defunct>
appuser   857989  0.0  0.0      0     0 ?        Z    16:32   0:00 [ssl_client] <defunct>
appuser   858250  0.0  0.0      0     0 ?        Z    16:33   0:00 [ssl_client] <defunct>
appuser   858495  0.0  0.0      0     0 ?        Z    16:34   0:00 [ssl_client] <defunct>
appuser   858724  0.0  0.0      0     0 ?        Z    16:35   0:00 [ssl_client] <defunct>
appuser   858954  0.0  0.0      0     0 ?        Z    16:36   0:00 [ssl_client] <defunct>
appuser   859193  0.0  0.0      0     0 ?        Z    16:37   0:00 [ssl_client] <defunct>
appuser   859440  0.1  0.0      0     0 ?        Z    16:38   0:00 [ssl_client] <defunct>

$ pstree -p -s 857529
systemd(1)───containerd-shim(857137)───ntfy(857168)───ssl_client(857529)

:crystal_ball: Additional context
Running in docker
Image ID: 4c878c400806
Docker Version: Docker version 24.0.6, build ed223bc
Linux Info (uname): Linux server-home 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
OS Info: Ubuntu 22.04.3 LTS

I have this issue too, ntfy running in a Docker container keeps creating zombie processes.
I'm having this issue on two different servers:
Server1:
Image ID: 4c878c400806
Docker Version: Docker version 24.0.7, build afdd53b
Uname: Linux basilisk 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu release: Ubuntu 22.04.3 LTS
Server2:
Image ID: ff7cdd4539dd (not updated)
Docker Version: Docker version 24.0.7, build afdd53b
Uname: Linux hp-t620 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu release: Ubuntu 22.04.3 LTS

Adding init option fixed the issue for me


Add example code for adding OpenCensus and AWS X-Ray

Added some example code for tracing the boilerplate repo with OpenCensus and AWS X-Ray.

Thanks for your contribution!


Is this abandonware?

Is this abandonware?
I ask because nothing much has happened in the repo for years and the version of this software running on the MicroPython website is running a really old version of MicroPython.
I hope the project isn't abandoned as it is a great idea!

Even though it's old, it still works :smile:
But, yes, would be good to keep this repo active.  I've now updated to MicroPythov v1.19.1, see 537518db953f42e3a12104c28c611de0d2d0695f


Key Fingerprints

From @arnottcr on January 16, 2015 4:35
The current method for symmetric keys you have is useful [:N5gaDV7)P3.r5], but could cause some confusion with users: caps/nocaps, what random character is that. The move to either gpg style hexadecimal or tor hidden service style base-32 fingerprint could alleviate that as it will only has one case and numbers. Furthermore the symmetric fingerprints appear to have inconsistent lengths: [pYfK22pA>In=f67d;W8pA:           =n:?73Wdj;E=644              Gfj?:YKKO87S] {there are three passwords there, not sure what is going on}.
Also the pub/priv keys are all hex, so consistency might be something that users would like.
Copied from original issue: winhowes/grd.me#8

From @winhowes on January 23, 2015 9:27
Regarding length: it generates a random length of 8-32 characters long.
I did think about just hex, but the initial reason I decided against it was that this feature could double as a password generator for users (several users are using it that way now so I've been told), but maybe the confusion isn't worth "feature"?

From @winhowes on January 23, 2015 9:27
Regarding length: it generates a random length of 8-32 characters long.
I did think about just hex, but the initial reason I decided against it was that this feature could double as a password generator for users (several users are using it that way now so I've been told), but maybe the confusion isn't worth "feature"?

how much user base do you have currently and is JavaScript randomness trustworthy?
Without Wax,
Colin Arnott
On 23 January 2015 09:27:54 GMT+00:00, Winston Howes<EMAIL_ADDRESS>wrote:

Regarding length: it generates a random length of 8-32 characters long.
I did think about just hex, but the initial reason I decided against it
was that this feature could double as a password generator for users
(several users are using it that way now so I've been told), but maybe
the confusion isn't worth "feature"?

Reply to this email directly or view it on GitHub:
https://github.com/winhowes/grd.me/issues/8#issuecomment-71167715

how much user base do you have currently and is JavaScript randomness trustworthy?
Without Wax,
Colin Arnott
On 23 January 2015 09:27:54 GMT+00:00, Winston Howes<EMAIL_ADDRESS>wrote:

Regarding length: it generates a random length of 8-32 characters long.
I did think about just hex, but the initial reason I decided against it
was that this feature could double as a password generator for users
(several users are using it that way now so I've been told), but maybe
the confusion isn't worth "feature"?

Reply to this email directly or view it on GitHub:
https://github.com/winhowes/grd.me/issues/8#issuecomment-71167715

From @winhowes on January 23, 2015 18:2
User base < 20 (I haven't begun promoting it yet).
Regarding randomness, I believe so: https://developer.mozilla.org/en-US/docs/Web/API/RandomSource.getRandomValues
Also I may switch over to this soon for some crypto: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto
Only downside to this^ is that it supports RSA but not ECC, so we can debate the tradeoff (there may be performance tradeoffs too, but I haven't tested yet).

From @winhowes on January 31, 2015 7:9
Update: max shared key length is now 64 and the password generating feature of this has been pretty much killed as the generate button only generates 64 char keys

From @winhowes on January 23, 2015 18:2
User base < 20 (I haven't begun promoting it yet).
Regarding randomness, I believe so: https://developer.mozilla.org/en-US/docs/Web/API/RandomSource.getRandomValues
Also I may switch over to this soon for some crypto: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto
Only downside to this^ is that it supports RSA but not ECC, so we can debate the tradeoff (there may be performance tradeoffs too, but I haven't tested yet).

From @winhowes on January 31, 2015 7:9
Update: max shared key length is now 64 and the password generating feature of this has been pretty much killed as the generate button only generates 64 char keys

From @winhowes on February 2, 2015 21:21
Closing as I don't think there's an issue here anymore. If there is feel free to re-open

From @winhowes on February 2, 2015 21:21
Closing as I don't think there's an issue here anymore. If there is feel free to re-open

Yeah, I mostly wanted to stop insecure crypto and it looks like that is being done.

Yeah, I mostly wanted to stop insecure crypto and it looks like that is being done.


Typo in Descriptor for Libraries

OpenUI5 version: 1.32 upwards
URL (minimal example if possible): https://openui5.hana.ondemand.com/#docs/guide/b229914587444025be986d81dcc77303.html

There is a typo in the field for "openSourceComponents". The trailing "s" is missing.

Hi cgraff thanks for your feedback a simple unit test would catch this
Internal incident<PHONE_NUMBER> has been opened for this issue.

Hi @cgraff,
Openui5.hana.ondemand.com will be updated with RTC of SAPUI5 (next release is 1.42. on Nov. 21)
openui5nightly.hana.ondemand.com is updated regularly and gives a preview of the current development.
You could check there - https://uacp2.hana.ondemand.com/viewer/#/DRAFT/SAPUI5_DEMOKIT_142/b229914587444025be986d81dcc77303.html.
Therefore I'm closing the issue.
Thanks and Kind Regards,
Diana


Add LFP variants of Grafana dashboards

For quite some time now, Tesla equips its lower-range vehicles with batteries that use lithium iron phosphate chemistry (also known as LFP). These batteries are designed to be regularly charged to 100% without the danger of accelerated degradation associated with NMC batteries.
However some dashboards in TeslaMate do not reflect this and display red and yellow indicators when the battery's SOC is high. I have created LFP variants of some dashboards so that owners of LFP-based vehicles can have a slightly better experience when viewing their data.
The added dashboards are:

Overview - LFP: The battery level gauge has red and yellow zones only on the lower end. The maximum value of the charging kW gauge has been lowered to 170, as this is the maximum DC charging potential for Tesla's LFP batteries.
Charging Stats - LFP: The charge stats table remains green even for entries higher than 80% and 95%.
Battery Health - LFP: The current SOC bar has a red zone only on the lower end.

Looks good @eden881!
Very important, I'd like to see these new features.

Sorry for the beginner question.
How do I check this out ? My docker instance has the latest build but I don't see these dashboards.

Sorry for the beginner question. How do I check this out ? My docker instance has the latest build but I don't see these dashboards.

Copy the proposed file from the source and import dashboard. Its in JSON format.

I'm also torn on this, this may be extra noise. I think a long term option we could possiblly use variables to make the existing dashboards change if it is LFP. We should also know if it is LFP from the API, so it could be automatic in that way also. I'm not sure just adding more dashboards is the "cleanest" route .

I think in the same way, I'll try to work on a solution.

Would you like to see this merged and open a seperate PR for a variable based solution?

Would you like to see this merged and open a seperate PR for a variable based solution?

I think so. I also think that a variable based solution is the correct way to go, but I believe it's better to have those dashboards merged in now as they solve the issue, and maybe remove them when a variable is integrated into the main dashboards.

I added #3438 to track the variable handling idea


CRI log parser improvements

The function parseCRILog might have some room to introduce some changes to make it more performance as calling strings.Fields only once at the beginning of the method should be more efficient. I think it could even be more efficient if we use strings.SplitN as I think we do not need to split the whole message.
Likewise, it would be good to check the resulting array to make sure it has the correct or the expected size and avoid errors when accessing different fields, for example 2016-10-06T00:17:10.113242941Z stdout as an input would cause panic.
If we use strings.SplitN then we wouldn't need strings.Join.

I think we can close this one.


refactor(docs): hide methods not useful to API users

Overview

Review what is visible on the current API Reference page and remove anything that's not useful to API end users.
Implementation details

At least cleanup, clear_commands, and commands should be hidden. Others might get added as we work on this.
Two possibilities for implementation:

Add to the appropriate :exclude-members: lists in new_protocol_api.rst.
Use :meta private: in the source docstrings.

Acceptance criteria

[ ] review of what should/shouldn't be visible
[ ] additions made to exclusion lists or docstring tags added
[ ] reference builds properly in sandbox with new exclusions added

Closing on GitHub. Now on Jira as RTC-40.


Remove flame graph feature flag

Fixes #753
Merging this PR will "release" flame graph.

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

v0.95.0
GitHub release

Your semantic-release bot :package::rocket:


Develop

Coverage remained the same at 82.04% when pulling a49a28c5eb204bd23efbd785fa1728b6dca20f5b on develop into 89bfbfdf531cbf3ed22aebcdc255f83835053247 on qa.


How can I get Headwind to run on .svelte files?

Hello,
I love Headwind but have recently switched from React to Svelte which caused Headwind to not do anything.
What can I add to my settings.json to make this work? Everything Ive tried has failed.
Thank you!

@RickRyan26, have you found any solution for this problem?

For everyone following these issues with Svelte, the Tailwind team just released a prettier plugin


Updating vulnerable dependencies according to assessment report : http://localhost:8081/assessments/assessment/66a1095121270677f00d5e3e

Summary Report

Scenario
Upgrades
Critical
High
Medium
Low

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Full Upgrade
0
0
0
0
0

Vulnerability Upgrade Report
| CVE | Target Dependency | Parent Dependency | Project Dependency | Upgraded Dependency | Remediation Status | Description || --- | ----------------- | ----------------- | ------------------ | ------------------- |:------------------:| ----------- |


Update food-chain version test comments to be more clear for user

Found that users were getting confused by the version test and it's purpose (see ticket 188). Goal is to make it clear to users that there only need to return the number that is asked. They do not need to bump the versions themselves at any point. We have also included a link to the ruby docs on contstants so if a user is curious at what they are inserting, they can read more about them

Would you mind squashing these commits? They're both a change on food-chain, as far as I can tell.

@kytrinyx I think this one should be good to go too.

Yepp, this looks great. Thanks!


Web component: Number input - Prod QA testing of the fluid variant

User Story

As a [user role below]:
developer using the carbon web components Library Text input fluid variant

I need to:
have a version of the component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
See the Epic for the Design and Functional specs information
Dev issue (#508)
Carbon Web Components Production Instance
Once development is finished the updated code is available in the ** Carbon Web Components test environment**

Acceptance criteria

[ ] Accessibility testing is complete.  Component is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

Closing this issue as the Prod QA testing will be automated.


recommend npx

By using npx directly, we can specify the latest version of Framework (rather than whatever was cached the first time you run npm init). Also it makes it more obvious which package is being run. It is slightly longer though, and there’s no yarn equivalent (but you can still pick Yarn when installing via npx if you want).

On my machine this command prints the observable help, but does not init a project. Is this expected?
~/Source/test-npx
❯ npx @observablehq/framework@latest
usage: observable <command>
  create       create a new project from a template
  preview      start the preview server
  build        generate a static site
  login        sign-in to Observable
  logout       sign-out of Observable
  deploy       deploy a project to Observable
  whoami       check authentication status
  convert      convert an Observable notebook to Markdown
  help         print usage information
  version      print the version

~/Source/test-npx
❯ npx @observablehq/framework@latest create
(node:13714) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
┌   observable create  v1.10.1
│
◆  Welcome to Observable Framework! 👋 This command will help you create a new
│  project. When prompted, you can press Enter to accept the default value.
│
│  Want help? https://observablehq.com/framework/getting-started
│
◆  Where should we create your project?
│  ./hello-framework
└

Yes. You need to have create at the end, like in the second example. If you don’t have that then the default command is help.

Oh right, it's written right there—I don't know why I didn't see it :eyes:
Makes sense to indicate the more reliable command.

This diff was helpful as a reference to setup using Observable Framework with npm.  Ended up here after seeing npx "deprecated" in official repos.

https://github.com/npm/npx
https://www.npmjs.com/package/npx

The following worked for me to get started with Observable Framework using npm .  I'll give npx a go next time and live dangerously.
npm i @observable/framework
npm init @observablehq
...
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)
...
cd ./hello-framework
npm run dev
...
Observable Framework v1.13.0
↳ http://<IP_ADDRESS>:3000/

npx the command is not deprecated AFAIK — it’s just been folded into the npm CLI rather than a standalone package.


metal_cans

OID:

Tin can

Probably have around 1,200 right now between trashnet and Open Images (OID).

all done and uploaded to the S3 bucket.


v3.4.19 and newer breaks hyperlink

Filament Version
v3.2.124
Plugin Version
v3.4.19
PHP Version
PHP 8.3.14
Problem description
The hyperlink button in the TipTap editor does not work at v3.4.19 or later.
Expected behavior
Entering a URL and clicking "Save" inserts a hyperlink into the text.
Steps to reproduce

Select text
Click "Insert / Edit Link"
Enter a URL, e.g. "https://example.com"
Click "save"

Reproduction repository
No response
Relevant log output
TypeError: undefined is not an object (evaluating 'f.coordinates[0]') from Livewire.js

Any console errors. Links are working fine for me on 3.4.22

Specially the relevant log output; are you also on the latest Livewire?

There was a bug in livewire 3.5.13 and filament was locked down to v3.5.12 a couple of days ago. So, that bug might still be in the latest livewire.


Render V1 hazards

I can't figure out how to try to run this without merging to main. @dhosterman, do you know? If not, just bless it and then I'll be able to trigger manual runs.


Help with pwdusage setup

Jason...looking for some help with pwdusage setup on Synology NAS running Powerwall-Dashboard on Docker...

I have Poerwall-Dashboard running fine on Synology NAS thru Docker - No Issues
a. Synology IP <IP_ADDRESS> and grafane looks great <IP_ADDRESS>:9000. I connected to influxD and sun and moon fine

I created a pwdusage container through your image (jasoncox/pwdusage:latest) with the following settings
a. Local Port 9050
b. Folder added    Powerwall-Dashboard/tools/usage-service   /var/lib/pwdusage   rw
c. Added envir variable  USAGE_JSON   /var/lib/pwdsuage/usage.json
**d. It appears that I have to set the network to "Bridge" to get things to work. this requires the following..(i. and ii)
i. Need to set the influxdb site (in usage.json) to the container IP <IP_ADDRESS>:8086
ii. Need to set the url for JSON Data source to the container IP of pwdusage.... http://<IP_ADDRESS>:9050/usage_engine

I have tried setting the bridge to host in hopes of being able to use the ip address of the Synology nas port 8086 for influx (<IP_ADDRESS>:8086) in the usage.json file and the IP of Synology NAS for the address of the Data source JSON http://<IP_ADDRESS>:9050/usage_engine....This does not work

If I type <IP_ADDRESS>:9050/usage_engine. from a computer browser on the network... I get the message "Engine OK.. but I cannot connect to it from the synology grafana setup (see #3 above)

Is this just how things are done with Synology Docker or do I have something set up incorrectly.
Thanks for your help in advance.

@farberm As I mentioned yesterday, I don't believe this is a problem that Jason should be responsible for resolving. It's also not really a problem with pwd-usage setup.
I think you are asking a question around how  synology maps/bridges ports to/between docker containers - so your question would be better directed at the synology and docker communities. (I do have to admit I'm perplexed about why the docker stack works fine with Powerwall-Dashboard, but not pwd-usage, but that still looks like a docker comms problem and not a Powerwall-Dashboard problem.)
If Jason can quickly point to a solution, great! But I do think it's unfair to ask him to troubleshoot issues involving interactions between my add on and other software that he is not responsible for (and tbh, from our discussions to date, I don't think this is really a pwd-usage problem either - unless there are some additional configuration flags for docker that would sort the problem out).

I was just wondering if Jason had any insight. Not trying to cause any problems. Sorry about that. I will just let it be for now. Just thought that getting some help outside my knowledge base may help someone else in the future. Sorry for causing any problems. Thanks for alll your help getting things set up.

@farberm No problem - I'm just very conscious of how much Jason does already and I don't want to see him loaded up with problems that come from my space!
I do understand you have a real issue, and I'll help as far as I'm able, but I'm also well aware of my own limits when it comes to the unholy trinity of synology, docker and network problems. (of the 200 PWD issues, nearly 10% mention synology!) - hence the suggestion to do some digging on those sites.

ok will do. If I figure out the solution is it ok to post what I find here to help out others?

If I figure out the solution is it ok to post what I find here to help out others?

Absolutely! (well, either here or on the pwd-usage repository depending on what the actual problem & solution is). Depending on the outcome, there will probably need to be a code or documentation update, and I know both Jason and I welcome contributions!

Great... will search the other connections I have for a possible solution even though it currently works but not as I thought it was designed to do...stay tuned


Control testing experiment

I hoped I remembered all the steps - here's the experimental protocol for my control testing experiments, with links to results.

Thank you so much for the detailed write up and photos - absolutely brilliant.
Raspberry Pi 4B XGB RAM - can you recall how much RAM it had?
Should we also add "Raspberry Pi 400 - as available during Pi shortage” - did you use some sort of breakout board to attach to the hat?
triver - I’m guessing this is a typo, but don’t know what to fix it to.

@Aqueum I actually used a Raspberry Pi Zero W for the worker. I'm planning on replacing the Pi 400 I used on the leader with a Pi Zero 2 W, as that's what the Pioreactor docs recommends, and I'd rather use the Pi 400 as a desktop computer. As the Pi Zero 2 We is the cheapest of the models that are capable of functioning as a leader, I'll put that in the kit list as the recommended hardware.
I created another PR with the updates: https://github.com/Amybo-org/pages/pull/10

Brilliant, thanks Gerrit
I’ve just bought a 4B 1Gb for the OpenFlexure Microscope https://openflexure.org/ I hope to build, along with the Adafruit Spectrometer.  4B 1Gb seems to be the cheapest that comes with an ethernet port.  I’d probably be cheaper off figuring out how to get my studio ethernet to talk to items on the WiFi, but have a feeling that would eat too much time.
Kind regards
Martin

On 6 Nov 2023, at 20:15, Gerrit Niezen @.***> wrote:
@Aqueum https://github.com/Aqueum I actually used a Raspberry Pi Zero W for the worker. I'm planning on replacing the Pi 400 I used on the leader with a Pi Zero 2 W, as that's what the Pioreactor docs recommends https://docs.pioreactor.com/user-guide/common-questions#raspberry-pi-hardware, and I'd rather use the Pi 400 as a desktop computer. As the Pi Zero 2 We is the cheapest of the models that are capable of functioning as a leader, I'll put that in the kit list as the recommended hardware.
I created another PR with the updates: #10 https://github.com/Amybo-org/pages/pull/10
—
Reply to this email directly, view it on GitHub https://github.com/Amybo-org/pages/pull/8#issuecomment-1796354985, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQMNK2MNFEVFUXZ6DHPOXDYDFAPJAVCNFSM6AAAAAA6Z62DNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJWGM2TIOJYGU.
You are receiving this because you were mentioned.


handle client upgrade messages properly during 400 errors

This won't help us fix the current crop of stranded users, but it'll give us the option of forcing an update when this sort of update issue happens in the future.
r? @maxtaco

:+1:

Before:
$ keybase id t_alice
▶ WARNING not exportable error: 400 Bad Request (*libkb.APIError)
▶ ERROR 400 Bad Request

After:
$ keybase id t_alice
▶ WARNING Upgrade recommended to client version 1.0.15 or above (you have v1.0.14)
▶ WARNING To upgrade, run the following command:
▶ WARNING     sudo pacman -Syu && run_keybase
▶ WARNING not exportable error: 400 Bad Request (*libkb.APIError)
▶ ERROR 400 Bad Request


Reccomended database rules?

I set this up mainly following the instructions from the tutorial and have the project hosted on my server. I was unable to create resumes until I changed the default firebase database rules from
  /* Visit https://firebase.google.com/docs/database/security to learn more about security rules. */
  "rules": {
    ".read": false,
    ".write": false
  }
}

to
{
  /* Visit https://firebase.google.com/docs/database/security to learn more about security rules. */
  "rules": {
    ".read": true,
    ".write": true
  }
}

Is this the correct configuration for this project? (It seems a bit insecure, but I'm not sure how to change it to get it to work with the project)

There is a file on the repository itself for suggested database rules.
https://github.com/AmruthPillai/Reactive-Resume/blob/develop/database.rules.json
{
  "rules": {
    "resumes": {
      ".indexOn": "user",
      ".read": "auth !== null && query.orderByChild === 'user' && query.equalTo === auth.uid",
      "$rid": {
        ".read": "data.child('public').val() === true || data.child('user').val() === auth.uid",
        ".write": " !data.exists() || data.child('user').val() === auth.uid || (!newData.exists() && data.child('user').val() === auth.uid)"
      }
    },
    "users": {
      ".indexOn": "isAnonymous",
      "$uid": {
        ".read": "$uid === auth.uid",
        ".write": "$uid === auth.uid"
      }
    }
  }
}


Not all tags are processed

Hi,
When using the library I noticed that some tags do not have any value even though other tools show values.
I  first thought that the change below fixed it:
`diff --git a/src/stream/tag.rs b/src/stream/tag.rs
index 552954c..3d495eb 100644
--- a/src/stream/tag.rs
+++ b/src/stream/tag.rs
@@ -93,7 +93,7 @@ pub fn decode(mut reader: impl io::Read) -> crate::Result {
}
} else {
let mut tag = Tag::new();

   while offset < tag_size + tag_header.len() {

   while offset < tag_size * tag_header.len() {
       let rs = frame::decode(
           &mut reader,
           version,

`
When I debugged it I could see that, for the mp3 file I was using, tag_header contained 10 items, but only the first 6 were being processed because the while loop was exited too early.
With the above fix, 'cargo test' passed and a test I had added that previously failed now passed.
I now think my fix isn't right because it assumes that all tags are the same size and that doesn't seem to be true.
My current guess is that an APIC tag with a large amount of data is  the cause of the problem.
What always happens is that the loop in stream/tag.rs exits too early.
Regards,
Graeme

I think I may have corrupted the mp3 files which caused the problems. I'm not sure but don't want to waste your time.

Np! Thank you for raising issues instead of suffering them, even they turn out to be not a bug at all ;)


Add assumptions methods to be in sync with assertions methods

Summary
Sync assertThatXxx methods with assumptions assumeThatXxx.
Missing ones

assertThatCollection
assertThatIterable
assertThatIterator
assertThatList
assertThatPath
assertThatPredicate
assertThatStream
assertThatException
assertThatRuntimeException
assertThatNullPointerException
assertThatIllegalArgumentException
assertThatIOException
assertThatIndexOutOfBoundsException
assertThatReflectiveOperationException"

Refactor Assertions_sync_with_BDDAssumptions_Test to be parameterized as Assertions_sync_with_BDDAssertions_WithAssertions_and_soft_assertions_variants_Test.
Don't add assertThatComparable it is going to be done as part of another ongoing issue.

@joel-costigliola Hi, I am interested in this. Would you like to assign this to me?

Sure, go ahead @HDreamer2

@HDreamer2 are you working on this?

@joel-costigliola Yes, I’ve done some work but I'm a little busy last two weeks and I'm really sorry for that. I was working on this just now and I'll finish this soon.

@joel-costigliola Yes, I’ve done some work but I'm a little busy last two weeks and I'm really sorry for that. I was working on this just now and I'll finish this soon.

@joel-costigliola Yes, I’ve done some work but I'm a little busy last two weeks and I'm really sorry for that. I was working on this just now and I'll finish this soon.

@joel-costigliola Hi, I'm confused about the second requirement(refactoring). Does it mean I need to create a new test class named Assertions_sync_with_BDDAssumptions_WithAssertions_and_soft_assertions_variants_Test as it describes?

thanks @HDreamer2.
you need to change Assertions_sync_with_BDDAssumptions_Test so that it has a parameterized tests as we did in Assertions_sync_with_BDDAssumptions_WithAssertions_and_soft_assertions_variants_Test, hope it's clearer.

@joel-costigliola Thanks, it's quite clearer and I've done most of the work including refactoring. But I still have some questions like the implementation of assumeThatException. Since there is no method like assertThatExceptionOfType whose argument is exceptionType, I tried to call assumeThat(new Exception()) whose declaration is public static <T extends Throwable> AbstractThrowableAssert<?, T> assumeThat(T actual). Is that a kind of reasonable implementation?

@HDreamer2 I think it would be nice to add assumeThatExceptionOfType and use it in the implementation of assumeThatException, assumeThatRuntimeException etc ...

I updated the issue description to make it clearer that we want to add assumeThatXxx methods in sync with assertThatXxx

@joel-costigliola Thanks, the description confused me in the very beginning and the advice sounds great.

@joel-costigliola Hi, I've done the whole work. Should I write extra tests or make a PR now? This is my first contribution so I have no idea whether it is enough.

@HDreamer2 feel free to raise a PR! In case tests are missing, we'll give you feedback during the review.


port HR-V global

HR-V Global has differences according to your country.
For example the Brazilian does not need an alternative brake signal while the Thai hybrid has different gear signals. So using the Hyundai platform as an example I put the dynamic detection that if it detects canId message from some of these modules the flag to handle is set.
requires: https://github.com/commaai/opendbc/pull/814 (Thai gears messages)
Test routes:
US HR-V: 320098ff6c5e4730|2023-04-14--20-27-00
Brazilian HR:<PHONE_NUMBER>16e718|2023-04-10--08-46-37
Thai HR-V: 1e4baee1aa2687a0|2023-04-14--20-23-45 (https://github.com/commaai/openpilot/pull/27870)
Thai HR-V HDC button: 1e4baee1aa2687a0|2023-04-15--15-53-46--0
Thai HR-V stock: 1e4baee1aa2687a0|2023-04-15--15-37-29
Checklist

[x] added entry to CarInfo in selfdrive/car/*/values.py and ran selfdrive/car/docs.py to generate new docs
[x] test route added to routes.py

Did you figure out how to improve the stopping behavior? We saw plots on Discord of the car not reacting correctly to both the stock system and openpilot's acceleration request when stopping (releases brakes and lurches towards lead).

Any update on this?

Any update on this?

We are waiting for a second Brazilian Honda HR-V to confirm the behavior of the PCM, Shane suspects it is a defect in the Kotarou's HR-V. We estimate a test on January 9th, we will use the Harness borrowed from Kotarou in another HR-V (which will have a comma3 only in March)

The creep is only caused by the stock Honda longitudinal (it's a feature known by the owners themselves), the longitudinal control of the openpilot is perfect. PR #30235 can be merged without being under the dashcam flag. As you can see in this https://youtu.be/Q11veROVwF4?t=27m YouTube video that we recorded during the test of the second Brazilian HR-V 2023, openpilot longitudinal control is a tremendous upgrade compared to stock control.

We've moved the car interfacing code to our opendbc repository, which is now the new home for car ports and fingerprints. Please re-open your pull request against opendbc at your convenience by using this command below. This will transform all changes under selfdrive/car/ to opendbc_repo/opendbc/car/. Make sure you have initialized submodules beforehand and have checked out the latest opendbc commit.
PR_NUMBER=33045
curl -L https://github.com/commaai/openpilot/pull/$PR_NUMBER.patch | sed -e 's/selfdrive\/car/opendbc_repo\/opendbc\/car/g' | git apply -v --reject

Simply replace the PR number with your own. Once done, add the files, fix any conflicts, and open a new PR. Alternatively, you may start a new PR from scratch if that is easier for you.


inconsistent since calcualtions with ZonedDateTime

I am facing a wired bug with the current polyfill and here is an example to illustrate the problem:
const pivotPlainDate = Temporal.PlainDate.from('2020-08-20')
const yearPlainStart = pivotPlainDate.with({ month: 1, day: 1 })

const pivotPlainDateTime = pivotPlainDate.toPlainDateTime({ hour: 12 })
const yearPlainDateTimeStart = pivotPlainDateTime.with({ month: 1, day: 1 })

const pivotZonedDateTime = pivotPlainDateTime.toZonedDateTime('UTC')
const yearZonedDateTimeStart = pivotZonedDateTime.with({ month: 1, day: 1 })

console.log('Weeks since year start [PlainDate]', Math.ceil((pivotPlainDate.since(yearPlainStart).days + 1) / 7)) // 34
console.log('Weeks since year start [PlainDateTime]', Math.ceil((pivotPlainDateTime.since(yearPlainDateTimeStart).days + 1) / 7)) // 34
console.log('Weeks since year start [ZonedDateTime]', Math.ceil((pivotZonedDateTime.since(yearZonedDateTimeStart).days + 1) / 7)) // 1 => incorrect

As it can be seen in the example above (pivotZonedDateTime.since(yearZonedDateTimeStart).days + 1) / 7) is yielding 1 instead of 34 and this happens only for the ZonedDateTime Temporal Object. Is this an expected behaviour? am I missing something here?

I have solved this by adding { largestUnit: 'days' } as such
console.log('Weeks since year start [ZonedDateTime]', Math.ceil((pivotZonedDateTime.since(yearZonedDateTimeStart, { largestUnit: 'days' }).days + 1) / 7)) // -> 34

But i would appreciate to know if this is an expected behaviour

This is expected. The default largestUnit for ZonedDateTime since/until is hours: https://tc39.es/proposal-temporal/docs/zoneddatetime.html#until
That's because days may be different lengths in ZonedDateTime calculations. Hours are the largest unambiguous unit, so that's why they're the default. In PlainDate / PlainDateTime calculations, days are the largest unambiguous unit, so that's why they are the default there.
You can calculate directly with weeks, though. Here's how I'd recommend doing it:
const options = { smallestUnit: 'weeks', roundingMode: 'ceil' };
console.log('Weeks since year start [PlainDate]',
  yearPlainStart.until(pivotPlainDate, options).weeks); // 34
console.log('Weeks since year start [PlainDateTime]',
  yearPlainDateTimeStart.until(pivotPlainDateTime, options).weeks); // 34
console.log('Weeks since year start [ZonedDateTime]',
  yearZonedDateTimeStart.until(pivotZonedDateTime, options).weeks); // 34

Thank you @ptomato for the detailed explanation. It makes sense to me. I was actually worried to use weeks as i wasn't sure what definition of week we are talking about. In ISO a week is always 7 days wheres a calendar week can be shorter then that.

Depends on the calendar. For PlainDate/PlainDateTime/ZonedDateTime instances in the ISO calendar, the week is always 7 days. If you want to ensure that, use .withCalendar("iso8601") before doing the calculation.
If you want the behaviour where the calendar determines the length of a week, no need to do anything. (Although I don't know the status of how accurate the CLDR calendars' week information is.)
There should not be edge cases around year boundaries in the ISO calendar.

This is very clear to me thank you. In my usecase days makes more sense since I am dealing with calendars other than iso8601 and scales other then Gregorian


new: usr: allow to define schema directly on Transformations and Views

How will this impact the rest of the flycs-ci? It also needs to change so that we can handle the new schema key or we convert everything to the model.yaml for now?

@JordyHeusdensDT we are going to roll this in phase. For now, both the model.yaml and the schema will be supported. The goals being to deprecate the model.yaml eventually.


registerCommand('type') is unable to listen to some key press for extension development

Version of VS Code, and platform it is running on: 1.87.2
List of extensions that you have installed: none
Reproducible steps: follow the steps in https://www.google.com/search?client=firefox-b-d&q=vscode+first+extension
I am unable to detect key press with this for keys like up, down and modifiers when doing extension development with vscode API :
vscode.commands.registerCommand('type', e => console.log(e))
nothing printed in console when I press a key

sorry I forget to mention that it happens when I am developing vscode extension.

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

@bhavyaus thanks I updated the issues description

@doofin 'type' is not a command we provide through our API. Could you please elaborate on what you are trying to achieve?

@bhavyaus  it's here: https://github.com/microsoft/vscode/issues/65876 . I try to exec some some command when up, down or modifier keys are pressed.


[macOS] - macOS desktop deletes the work direction in a textfield

Link to flutter engine possible issue: https://github.com/flutter/engine/blob/8af3b1b4da63d560ff54abdedbaa376044555bdc/shell/platform/darwin/macos/framework/Source/FlutterTextInputPlugin.mm#L182
Simple test:
import 'package:flutter/material.dart';

final Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(scaffoldBackgroundColor: darkBlue),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return TextField();
  }
}

Run flutter create to test on macOS and web.
It works correctly on iOS, web but not macOS.
Enter data into the text field an press the delete key.

https://github.com/flutter/flutter/pull/49760 regressed this; backspace and delete are not the same, and shouldn't be treated as such.


Detail docs about building for relative path

Added docs is verified at here.
Hope it will help guys wanna change root path of built app without changing package.json.

Wrong branch, closed.


Add checkstyle for Test code and update documentation

Checkstyle added for Test cases as well under issue #38
Update .travis.yml file to extend checkstyle
Update UG, DG and PPP
Update documentation to add Travis usage instructions

Codecov Report

Merging #242 into master will increase coverage by 0.05%.
The diff coverage is 62.5%.

@@             Coverage Diff              @@
##             master     #242      +/-   ##
============================================
+ Coverage     73.43%   73.49%   +0.05%
- Complexity      622      624       +2
============================================
  Files            64       64
  Lines          2255     2260       +5
  Branches        260      260
============================================
+ Hits           1656     1661       +5
  Misses          513      513
  Partials         86       86

Impacted Files
Coverage Δ
Complexity Δ

src/seedu/addressbook/ui/MainWindow.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...c/seedu/addressbook/autocorrect/CheckDistance.java
59.25% <0%> (ø)
6 <0> (ø)
:arrow_down:

...rc/seedu/addressbook/commands/DateTimeCommand.java
100% <100%> (ø)
4 <3> (+2)
:arrow_up:

Continue to review full report at Codecov.

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


Add autocomplete of values when filtering telemetry

I think this is pretty cool. PR adds:

Autocomplete of values when filtering telemetry
Works for structured logs and traces
Works for adhoc attributes and known fields

Fixes https://github.com/dotnet/aspire/issues/5746
Depends on https://github.com/dotnet/aspire/pull/5751 being merged first.
Demo:

Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[ ] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[ ] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[ ] No

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

Blocked on some issues in FluentCombobox


Little inconsistency in error messages, while validating JWTs

If the we directly hit a service with an expired JWT (before being added to the cache) - following is the error on the logs:
2018-10-31 06:08:46,174 DEBUG [ballerina/http] - Trying to authenticate with the auth provider: jwt-1
2018-10-31 06:08:46,348 ERROR [ballerina/http] - Error while validating JWT token  : {message:"JWT token is expired", cause:null}
If the JWT is in the cache - and try the same (JWT) after it expires - I don't see any error logs.
2018-10-31 06:08:19,760 DEBUG [ballerina/http] - Trying to authenticate with the auth provider: jwt-1

This is now fixed with the refactoring of the authn/authz framework [1] [2] for Ballerina 1.0. The inconsistency in error messages is also fixed along with that.
[1] https://github.com/ballerina-platform/ballerina-lang/pull/15056
[2] https://github.com/ballerina-platform/ballerina-lang/pull/15696


[SPARK-13279] Remove unnecessary duplicate check in addPendingTask fu…

…nction

Can one of the admins verify this patch?

lgtm

I don't quite see why this solves a lock problem. Should this be a set?

As you can see from the jstack of the driver  http://pastebin.com/m8CP6VMv. The dag-scheduler-event-loop thread has taken a lock and is spending a lot of time in the addPendingTask function. For each task added, It is iterating over the list of tasks to check for duplicates. Which becomes an o(n2) operation and when the number of tasks is huge, it takes more than 5 minutes.
As mentioned in the comment, the addPendingTask function does not really need to check for duplicates because dequeueTaskFromList will skip already running tasks. If we remove the duplicate check from addPendingTask function, then the time period for which the lock is held is very short and things are working fine.  We can not make this as a set because we treat the list of pending tasks as a stack, please see https://github.com/sitalkedia/spark/blob/fix_stuck_driver/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala#L113 .
Please note that this is a regression from Spark 1.5 and is introduced in https://github.com/facebook/FB-Spark/commit/3535b91ddc9fd05b613a121e09263b0f378bd5fa#diff-bad3987c83bd22d46416d3dd9d208e76L789

OK, but the JIRA describes a deadlock, or at least that's how it reads.
@kayousterhout does that sound right? it sounds OK.

Sorry, I did not make it clear. Its not a deadlock, the lock is held for a very long time.

Thanks for fixing this! You're right that the change you linked to is broken; when I removed the readding parameter, I should have killed the if-statement. I updated the JIRA description to describe this problem somewhat better and link to the offending change.
This should be merged into 1.6 when it's ready since it's a regression.

Thanks @kayousterhout. I updated the comment accordingly.

Jenkins, test this please

I just merged this but then realized Jenkins hadn't run yet... reverted the pushed version but will re-merge when Jenkins passes

I reverted this since it hasn't passed tests yet.

@sitalkedia can you re-open this? (It was closed automatically when inadventently merged)  I don't think we can test it unless it's open

@kayousterhout I am not seeing an option to reopen this pull request. Should I create a new pull request?

That would be great thanks!! Sorry for the trouble caused by my rushed merging!

No problem. Created a new pull request https://github.com/apache/spark/pull/11175


CI/Documentation: Handling Pull Requests

Before submitting...

[X] I have searched for duplicate or closed issues.
[X] I have read the CONTRIBUTING document and my issue is following the guidelines.
[X] I have read the template completely before filling it in.

Context
We should update Documentation: Every new PR should be included in the Dev Branch.
I mistakenly wrote in the documentation, that Fixes should be merged into Main and Improvements should be merged into Dev, but I think we should ALWAYS merge every PR into dev-Branch. In the longer term we should merge from DEV -> MAIN only when a new release is done.
What do you think? I would update the documentation accordingly.
Current Behavior
Different process for a FIX and FEATURE.
Expected behavior
ONE process for every change.
Possible Solutions or Causes
Base PRs always from dev branch.
Your Environment
No response

In the longer term we should merge from DEV -> MAIN only when a new release is done.

Exactly my thought.


add site in gerenal and cep pt-br, Neighborhood pt-br and others

Suggestions for next additions:
-faker site
-faker cep (post address code) pt-br
-faker neighborhood in pt-br and others

I'm looking forward to reducing the number of open issues. If you need a place to keep a task list for your language, please use another tool!

As visions only improve the quality of your product, but sorry for the inconvenience


Update README.md

Adicionar meu perfil ao README.md
Summary

Type of change

[ ] Bug fix (added a non-breaking change which fixes an issue)
[x] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[ ] Ran tests with composer test
[x] Added or updated test cases to test new features

Looks good 👍


OP-1530 Packaging deb with systemd and documentation for Charlie

Adding all needed files to debian package.
casper-node and casper-client are installed in /usr/bin
All other files are currently in /etc/casper/.
Allows removable and reinstall of .deb while maintaining /etc/casper/config.toml' and keys in '/etc/casper/validator_keys.  This will allow distribution of updated accounts.csv and chainspec.toml with a .deb package install.

Orphaned with Private -> Public.  Replaced with #230.


Change Psalm error level to 1

Codecov Report

Merging #3 (054c666) into ci/psalm (eb87b7a) will decrease coverage by 0.08%.
The diff coverage is 97.95%.

@@              Coverage Diff               @@
##             ci/psalm       #3      +/-   ##
==============================================
- Coverage       99.15%   99.06%   -0.09%
  Complexity          2        2
==============================================
  Files              52       55       +3
  Lines             828      859      +31
==============================================
+ Hits              821      851      +30
- Misses              7        8       +1

Impacted Files
Coverage Δ

src/Command/Helper/ProgressBarSubscriber.php
100.00% <ø> (ø)

src/Configuration/Validator/BaseValidator.php
100.00% <ø> (ø)

src/Event/HookLoader.php
100.00% <ø> (ø)

src/Process/ChangesCountProcessBuilder.php
100.00% <ø> (ø)

src/Process/ConcreteProcessFactory.php
96.42% <ø> (ø)

src/Process/Handler/SequentialProcessHandler.php
100.00% <ø> (ø)

src/Result/ResultAccumulator.php
97.61% <50.00%> (-2.39%)
:arrow_down:

src/Event/Broker.php
100.00% <100.00%> (ø)

src/Event/Channel/AfterAnalysisChannel.php
100.00% <100.00%> (ø)

src/Event/Channel/AfterFileAnalysisChannel.php
100.00% <100.00%> (ø)

... and 8 more

Continue to review full report at Codecov.

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


Emmet: wrap with abbreviation is broken for 'span'

VSCode Version: Code - Insiders 1.15.0-insider (9912a545c9728ce5e6b3cdfcc9442ee47955aa42, 2017-07-21T05:16:15.475Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

Bookmarks
ale
0.15.2

project-manager
ale
0.18.1

vscode-eslint
dba
1.2.11

gitlens
eam
4.3.2

EditorConfig
Edi
0.9.4

beautify
Hoo
1.1.1

atom-keybindings
ms-
2.9.1

stylelint
shi
0.28.0

Steps to Reproduce:

Open the following HTML file:

Select all lines between the ul tags.
Invoke "Emmet: Wrap with Abbreviation", and then type span in the command palette.
The end result is horrific:

Interestingly enough, everything works fine for other tags, like div, p or body! 😳

Another bad tag that exhibits the same problem is em.
Trying to wrap with em leads to all lines combined into a single one.

Duplicate of #29898
This happens for all elements that have display: inline by default.
Emmet thinks that "oh this is an inline element, so I should place everything in a single line"
Solution would be to fix it upstream by not doing this single line treatment if the text being wrapped is multi line to begin with.


Enable additional platforms

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #4.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #4

@conda-forge-admin please rerender

@conda-forge-admin please rerender

The Windows build are timing out on:
** libs
using C compiler: 'x86_64-w64-mingw32-gcc.exe (conda-forge gcc 13.3.0-1) 13.3.0'
rm -Rf b64.dll ./rust/target/x86_64-pc-windows-gnu/release/libb64.a entrypoint.o /d/bld/r-b64_1725278545346/work/src/.cargo /d/bld/r-b64_1725278545346/work/src/vendor
x86_64-w64-mingw32-gcc  -I"D:/bld/r-b64_1725278545346/_h_env/lib/R/include" -DNDEBUG     -I"D:/bld/r-b64_1725278545346/_h_env/Library/include"     -O2 -Wall  -march=x86-64 -mtune=generic  -c entrypoint.c -o entrypoint.o
# uncompress vendored deps
if [ -f ./rust/vendor.tar.xz ]; then \
	tar xf rust/vendor.tar.xz && \
	mkdir -p /d/bld/r-b64_1725278545346/work/src/.cargo && \
	cp rust/vendor-config.toml /d/bld/r-b64_1725278545346/work/src/.cargo/config.toml; \
fi

Unsure why...


Model Speed

Hey,
this is an amazing pose estimation ai and it works realy good and is easy to use. I tried the new models and have some trouble. My goal is, to use your AI with 30 fps on 4  cameras. Currently I'm on ~22-25 fps with batching and the old model (metrabs_multiperson_smpl). So I tried the new ones. But they are much slower than metrabs_multiperson_smpl. Even the fastest one with less accuracy is barely faster than the old one. Additionaly the tensorflow load time is very high model = tf.saved_model.load(path). With the new models the system needs 18-62 seconds to be ready.

Images
metrabs_multiperson_smpl
metrabs_mob3l_y4
metrabs_eff2s_y4
metrabs_mob3l_y4t

Load Model
2,5 s
15 s
29 s
52 s

First Use
6 s
3 s
6,5 s
10 s

1
23 ms
28 ms
85 ms
250 ms

2
30 ms
28 ms
86 ms
250 ms

4
40 ms
37 ms
90 ms
260 ms

8
76 ms
58 ms
113 ms
300 ms

16
154 ms
116 ms
220 ms
600 ms

meassured call: pred = model.estimate_poses_batched(images, boxes=ragged_boxes, intrinsic_matrix=intrinsics)
1.
So my first question is if this is normal? With this values, "metrabs_multiperson_smpl" is the best model for real time applications. But this model is "outdated" because the functions does not match the new code and api.
2. Questions about the model "metrabs_multiperson_smpl":
The paper states that the AI can handle up to 511 crops pers second with a stride size of 32 and batch of 8. Is this model build with a stride size of 4?
If thats the case, I have to build the model myself again with an higher stride size. Can you provide any checkpoints or models with higher stride size with the same dataset and backbone as metrabs_multiperson_smpl? If not, on wich datasets was this model trained and how much epochs did it need?
If I have to train it again anyway, I can also use the new api for this model.
My System:
AMD Ryzen 5800X (8x3,8-4,7Ghz)
RTX 3080
32 GB RAM

Hi! Thanks for this detailed analysis! I have noticed slow initial load times as well, and 20-30 seconds seem the correct ballpark. I haven't had time to take a closer look at this issue yet. However, I'm in the process of doing some detail timing benchmarks.
Meanwhile, you may want to check out the newly released ResNet-based models as well (https://github.com/isarandi/metrabs/blob/master/docs/MODELS.md). These are based on ResNetv1.5, initialized from weights exported from PyTorch checkpoints, which I found to work better. The old metrabs_multiperson_smpl used ResNet101v2.

The paper states that the AI can handle up to 511 crops pers second with a stride size of 32 and batch of 8. Is this model build with a stride size of 4?

All these packaged models all run at stride 32. The 511 crops/second does not take into account the time to decode an image, run detection, crop (reproject) etc, it only measures the network described by the paper itself, i.e. from the point of having a 256x256 image to getting the prediction. The full pipeline of a real application will always take longer in practice.
The training data is listed at https://github.com/isarandi/metrabs/blob/master/docs/MODELS.md. I haven't released preprocessing code for some of those datasets (at least not yet). It is a long and complicated process to get all that data to a form that can be used for training. The number of update steps was 400,000 with a batch size of 128, taking on the order of a week on an Nvidia A40 GPU.

Thank you!
The new models  with resnet50 and resnet34 are perfect for me. But the load time is very high althought it is the same backbone as in metrabs_multiperson_smpl. Does the problem still exist if you build the model directly without tf.saved_model.load?
If it is that complex then i will not train the data myself.

have you solved how to get the real time fps ?
i run it in ubuntu18+2080ti+tf2.6+cuda11.2+cudnn8.1+model.estimate_poses, the fps is 10f/s,
now i will change to use the gpu:3090 to test it in win10 and ubuntu18,
are you sucessful in resnet50 and resnet34 ?
if sucess, the fps in your 3080 ?

Set num_aug=1 for fastest results. The new efficientnetv2-s models can run in real time even on a laptop GPU.

chal zutha!!


jquery tooltipster work only on second hover

Dear Louis,
Coud you please have a look at this question:
Stackoverflow
I can't find a solution, every time I need to hover twice to see the tooltip, is it an issue or am I doing something wrong with my Ajax post?
Best regards

Hello, you initialize your tooltip when the mouseover event has already been fired, so Tooltipster cannot "hear" this first event and open the tooltip. You'd better initialize your tooltips at page load and put your comment id in a data-id attribute that you'll retrieve in functionBefore when you prepare your ajax call.

Previously I used this:
`

...

`
With this anchor:
 Hover
And this JS

So basically I need to go back to this solution?
In my case it's really uncomfortable.

No, it would look like this:
Hover
    $(document).ready(function() {
        $('.tooltip').tooltipster({
            functionBefore: function(){
                var $origin = $(helper.origin);

                // we set a variable so the data is only loaded once via Ajax, not every time the tooltip opens
                if ($origin.data('loaded') !== true) {

                    $.ajax({
                        type: "POST",
                        url: baseUrl+"/requests/load_profilecard.php",
                        data: 'id='+ $origin.attr('data-commentid')+"&token_id="+token_id,
                        cache: false,
                        success: function(html) {
                            // call the 'content' method to update the content of our tooltip with the returned data
                            instance.content(html);

                            // to remember that the data has been loaded
                            $origin.html('loaded', true);
                        }
                });
            }
        },
        interactive:true,
        maxWidth:250
    });
});

Your token_idvariable seems unresolved here, check your console to see if you get an error. And try to understand the meaning of options in the documentation as it makes no sense to use both the contentCloning and contentAsHTML at the same time (even if it won't throw an error).

Thanks a lot,  I was reading this answer http://stackoverflow.com/a/38800017/4458531 .
I was using contentCloning  because I have different HTML content with the same content

You're welcome. The answer is good general advice although the "Initalize Tooltipster on Document Ready" and "Trigger Tooltipster with Hover" are misleading as in both cases he's initializing the tooltip.
You don't neeed contentCloning when the content is a unique element created by an Ajax call for each tooltip. And you only need contentAsHTML if the content is a string representing HTML.

contentAsHTML  was very clear to me indeed.
I tried this solution but from console I get Uncaught ReferenceError: helper is not defined

should be functionBefore: function(instance, helper){, I copy-pasted your code

Tried again, and again the same old issue, only at the second mousehover the tooltip is shown.
When I hover the 1st time from console it load Ajax content but it doesn't show it :s

Please copy-paste your current js code here.

Ok, this is my head tag:

    <link rel="stylesheet" type="text/css" href="https://s3-eu-west-1.amazonaws.com/../css/tooltipster.bundle.min.css" />

It looks good. Refresh your cache just in case. Is your content an image ?

Finally it works!
No, it's not a cache problem or content (my content is an HTML string with some img's inside) but the missing of this content: 'Loading...', after $('.tooltip').tooltipster({

Cool! You can close this issue if it's all good :)

I don't know why but Tooltipster on new load more contents via Ajax it's not working.
I added the script above inside my Ajax page but it doesn't init. On hover it does nothing.

As I can't spend much more time on helping individual users getting their script right, I suggest you take some time to think on it and go back to Stackoverflow with your new issue if you can't figure it out. Thank you.

Thanks, I made a new question http://stackoverflow.com/questions/38809488/dynamic-content-not-shown-after-ajax


Update to grafana Helm chart 6.49.0

Changes:
Update to Grafana 9.3.1.
Add support to deploy Grafana alerts via sidecar.alerts.*.

This failed with:
flux-system     helmrelease/grafana                     6.36.2          False           False   Helm upgrade failed: unable to build kubernetes objects from current release manifest: [resource mapping not found for name: "grafana" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
                                                                                ensure CRDs are installed first, resource mapping not found for name: "grafana-test" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
                                                                                ensure CRDs are installed first]

I'm now investigating it...

I've removed both grafana HelmRelease and grafana namespace and reconciled it and it fixed it.


pantheon.xdg-desktop-portal-pantheon: 1.1.0 -> 1.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pantheon.xdg-desktop-portal-pantheon is: "Backend implementation for xdg-desktop-portal for the Pantheon desktop environment"
meta.homepage for pantheon.xdg-desktop-portal-pantheon is: "https://github.com/elementary/portals"
meta.changelog for pantheon.xdg-desktop-portal-pantheon is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.0 with grep in /nix/store/5d2sjkdbawp48i06g3dvcn7a5ghp4fvz-xdg-desktop-portal-pantheon-1.2.0
found 1.2.0 in filename of file in /nix/store/5d2sjkdbawp48i06g3dvcn7a5ghp4fvz-xdg-desktop-portal-pantheon-1.2.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pantheon.xdg-desktop-portal-pantheon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5d2sjkdbawp48i06g3dvcn7a5ghp4fvz-xdg-desktop-portal-pantheon-1.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5d2sjkdbawp48i06g3dvcn7a5ghp4fvz-xdg-desktop-portal-pantheon-1.2.0
ls -la /nix/store/5d2sjkdbawp48i06g3dvcn7a5ghp4fvz-xdg-desktop-portal-pantheon-1.2.0/bin

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

1 package built:

pantheon.xdg-desktop-portal-pantheon

Maintainer pings
cc @davidak @bobby285271 for testing.

I will do the merge when I finish testing this.

[ ] make --verbose works (#50)

Files: meson.build

[ ] Updates for ExternalWindow (#54)

Files: meson.build
Keywords: dependency

[ ] Update portals.appdata.xml.in
[ ] Release 1.2.0 (#57)

Tags: 1.2.0
Files: meson.build

Maybe explicitly pull in xorg.libX11 per https://github.com/elementary/portals/commit/300563116bde8b33d92b1e312f35761d6bfb9e23.


v1.2.0: Update all dependencies, use Node.js v18, output error stack on failure

This PR performs numerous updates to the action for quality of life:

Use Node.js v18 instead of v12 (note that GitHub Actions forces v12 actions to use v16 instead now)
Update all of the dependencies to their latest available versions
Output the error stack on failure, instead of just the error message

This is important to help with debugging issues such as https://github.com/mdn/browser-compat-data/actions/runs/6664967284/job/18113611569.

Closing per the discussion to use my fork in BCD instead!


feat: add gogs git provider

add gogs git provider
Description
This PR adds support for a new Git provider gogs

[x] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
closes #1223
Screenshots
manual

via TUI
https://github.com/user-attachments/assets/30075f54-34ce-4fa7-92a0-6391e598ac66
@quest-bot loot #1223

@quest-bot loot https://github.com/daytonaio/daytona/issues/1223

@quest-bot loot https://github.com/daytonaio/daytona/issues/1223

@quest-bot loot #1223


Class based views creation using Django REST Framework

See the code in class_views.py from app emp_CRUD.
Also see urls.py from project and app.
Some screen shots from Django REST framework

gjhjgj


Best practices for number of connections

I was wondering what the best strategy would be to connect to a Redis server during the execution of a script:

Create one instance and share that across all code that requires Redis (= 1 connection to Redis)
Create different instances for read, write and polling requests (= 3 connections to Redis)

Are there any performance gains from having multiple connections?
Apart from that, would it make any difference to have a separate connection for code that relies a lot on BRPOPLPUSH?
Thanks

I am developing a common caching service which will be used by many micro services(Clients for me). How many number of connections should I create? Is 1 connection per application sufficient?

One connection is perfect. The performance will always be the same no matter if you use more than one client.


abiotic_tools introduced

I found a number of functions and universal constants that will be used by multiple submodules of the abiotic_model.
I introduced a new submodule called abiotic_tools which contains them all and can be accessed easily by other submodules.
The AbioticConstants might eventually go to a central point or can be accessed by others, for now it just makes the abiotic part of the model easier to manage.
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] 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
[x] All tests pass: $ poetry run pytest

Further checks

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

Codecov Report

Merging #186 (8f5f5bc) into develop (c7c7724) will increase coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head 8f5f5bc differs from pull request most recent head bf2bdb5. Consider uploading reports for the commit bf2bdb5 to get more accurate results

@@             Coverage Diff             @@
##           develop     #186      +/-   ##
===========================================
+ Coverage    95.51%   95.53%   +0.02%
===========================================
  Files           24       25       +1
  Lines         1181     1187       +6
===========================================
+ Hits          1128     1134       +6
  Misses          53       53

Impacted Files
Coverage Δ

virtual_rainforest/models/abiotic/__init__.py
100.00% <ø> (ø)

virtual_rainforest/models/abiotic/abiotic_tools.py
100.00% <100.00%> (ø)

virtual_rainforest/models/abiotic/radiation.py
89.28% <100.00%> (-0.19%)
:arrow_down:

virtual_rainforest/models/abiotic/wind.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Further discussion on uniform structure of constants needed, see #129 and https://github.com/ImperialCollegeLondon/virtual_rainforest/pull/186#pullrequestreview-1317041139


Mongodb use small files instead

As my pfsense have only 4GB SSD and only 3.1GB root partition, there was a error that my disk space is not enough for mongodb
my workaround is to remove the symbolic link in /usr/local/UniFi/bin/mongodb, but using following shell script instead

!/bin/sh
/usr/local/bin/mongod --smallfiles "$@"

Interesting. Were you not able to achieve the same results with the configuration file?
This is more of an issue with mongodb than with unifi-pfsense, but since pfsense is commonly run on minimal hardware like yours, I am inclined to make a note about this in the readme.
Since editing the configuration file is probably preferable to using a wrapper script, I would be interested to know whether that would work in your case.

Replacing link with shell script with extra argument (The method I mentioned) worked in my case.
I tired to edit configuration file (/usr/local/etc/mongodb.conf) and added a line "smallfiles = true" but no luck, I just don't know if the mongodb instance that launched by UniFi will load (/usr/local/etc/mongodb.conf).

Add the following to unifi/data/system.properties:
unifi.db.extraargs=--smallfiles

I believe this issue has been addressed and can now be closed.

Thank you!


Update IsApplicable() for fused winograd convolution

Current implementation of fused winograd convolution uses very limited subset of underlying kernel implementation.
Current limitations are:

only 2x3 version
no dilation support
no grouped convolution support

These limitations should be removed since kernel supports all the modes and it may allow to apply potentially faster kernel for more cases.
In the ideal case fused and non-fused convolutions should be merged because both of them are using the same kernels and have minimal difference in host code.

Seems #2002  is related but quite old.


Demo not working (grey boxes)

When I downloaded the demo from your website it showed me 2 grey boxes. The video is not playing. What did I do wrong? I'm using Chrome.

Using Inspect Element (right click > inspect element > console) you can see if there is a cross-site error.  I found that the demo would not run without serving it from some host rather than directly from a file.  You can setup a debug server using python: ( python -m SimpleHTTPServer)  from the downloaded directory and then go to localhost:8000 to see if that works.


[Suggestion] add DocBlock snippet functions for many languages

I know it is very easy to create your own snippet for it but I'd prefer the automatic creation of DocBlocks
This package for Atom.IO called DocBlockr is a perfect idea of what I want. It's a shame there is no plugins for this on VSCode but i'm sure a lot of people would love this feature!
At the moment I'm having to use Atom to write up my API Documentation and it's a pain having to switch between editors
If you don't know what docblocks are look up JavaDoc or phpDocumentor
To clarify: No this is not just creating snippets, It's reading the below function and automatically creating a document block

Or if anyone could create a plugin for this, It would be great!

It looks like that DocBlockr has been ported to VS Code: https://github.com/shardulm94/vscode-docblockr
I've not tested it, and don't know if it is in the market.

Its not in the market, but there is https://marketplace.visualstudio.com/items?itemName=joelday.docthis. ""Document This" is a Visual Studio Code extension that automatically generates detailed JSDoc comments for both TypeScript and JavaScript files."
I'm using C and C++, so I'm not sure that it is much use. Not tested yet.

@BillDenton But the Document This extension for VS Code only works for JavaScript and TypeScript, contrary to DocBlockr, which works for many languages (see https://github.com/spadgos/sublime-jsdocs).

I know :-(. Also there's nothing in https://github.com/shardulm94/vscode-docblockr.

I need this for C/C++. It's the only thing stopping me to move from Sublime.


Add PhantomJS2 to Karma browser list, fix Karma warnings

See discussion in #137 - not sure if that's the ideal/final solution, but at least it works...

@ryzy awesome job! I left a single comment, since we're coupled with the module structure now.

@mgechev : thanks for the comment, yeah, I was using npm 2.x, shame on me ;)
Indeed, no need for mapping @reactivex, I've reverted appropriate lines.
Plus rebase.
Please review again, thanks!

@ryzy looks great! Thanks for the PR!