Unify floating point types

The line
https://github.com/huiyuxie/trixi_cuda/blob/e2dd47f46f2d1d7c0dd6a6d657c2b4060ddbf7f1/example/example1.jl#L21
sets the type of the time t to Float64 instead of Float32.

For example1.jl, if I apply all the kernels in rhs_cpu!() here https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/cuda_dg_2d.jl#L622-L663
then the warning would disappear.
Here are the results of running extrema(sol_cpu.u[end] - sol_gpu.u[end]) for example1.jl, example2.jl, and example3.jl
# Example 1
(-0.7075251034787967, 0.7075251034787917)

# Example 2
(-0.15977738342860448, 0.2807921957743247)

# Example 3
(-5.969505079228554e-5, 2.7934254639205847e-5)

It seems that only the result of the third example is acceptable. The first two are deviated too much so that I doubted there was something wrong with my code.
But I checked the code again and further ran the same (similar) tests from here https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/cuda_dg_2d.jl#L5-L7
using the initial data from semidiscretize() like
https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/tests/advection_basic_2d.jl#L17-L21 for both branch main (Float32) and type64 (Float64), the result of these raw implementation tests https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/cuda_dg_2d.jl#L740-L799 are definitely correct, see an example result of the test coming from type64
julia> du1-du2
4×4×4×256 StrideArray{Float64, 4, (1, 2, 3, 4), Tuple{StaticInt{4}, StaticInt{4}, StaticInt{4}, Int64}, NTuple{4, Nothing}, NTuple{4, StaticInt{1}}, Vector{Float64}} with indices static(1):static(4)×static(1):static(4)×static(1):static(4)×Base.OneTo(256):
[:, :, 1, 1] =
  0.0           0.0          2.84217e-14   2.84217e-14
 -5.68434e-14  -1.11022e-16  0.0          -1.42109e-14
  5.68434e-14  -1.11022e-16  5.68434e-14   4.26326e-14
 -8.52651e-14   0.0          0.0           0.0

[:, :, 2, 1] =
  0.0          -1.77636e-15  7.10543e-15  0.0
 -1.11022e-16  -1.77636e-15  0.0          5.69544e-14
  2.83107e-14   3.55271e-15  0.0          1.11022e-16
  5.68434e-14  -3.55271e-15  0.0          5.68434e-14

[:, :, 3, 1] =
  0.0          -7.10543e-15  0.0           0.0
  0.0           0.0          0.0           1.11022e-16
  0.0           0.0          7.10543e-15  -2.83107e-14
 -5.68434e-14   0.0          0.0           2.22045e-16

[:, :, 4, 1] =
  0.0          0.0           0.0          0.0
  1.42109e-14  1.11022e-16  -5.67324e-14  5.68434e-14
 -1.42109e-14  1.11022e-16   5.69544e-14  4.26326e-14
  0.0          5.68434e-14   5.70655e-14  0.0

[:, :, 1, 2] =
 0.0           0.0           5.68434e-14   2.84217e-14
 2.84217e-14   1.11022e-16   1.11022e-16   1.42109e-14
 7.10543e-14   1.11022e-16  -1.13576e-13  -4.26326e-14
 0.0          -5.68434e-14  -5.66214e-14   5.68434e-14

[:, :, 2, 2] =
  2.84217e-14  -1.77636e-15  1.77636e-15  0.0
  1.11022e-16   1.11022e-16  3.55271e-15  0.0
  1.11022e-16   1.11022e-16  0.0          2.84217e-14
 -1.13687e-13   2.22045e-16  3.55271e-15  0.0

[:, :, 3, 2] =
 0.0          0.0  5.55112e-17  2.77556e-17
 1.13798e-13  0.0  1.11022e-16  5.55112e-17
 1.11022e-16  0.0  1.11022e-16  5.55112e-17
 2.22045e-16  0.0  2.22045e-16  2.22045e-16

[:, :, 4, 2] =
  2.84217e-14  0.0          2.77556e-17  1.42109e-14
 -4.26326e-14  5.68434e-14  5.55112e-17  4.25771e-14
  1.42109e-14  0.0          5.55112e-17  5.67879e-14
  1.13687e-13  0.0          2.22045e-16  0.0

[:, :, 1, 3] =
 0.0           0.0           5.68434e-14   2.84217e-14
 2.84217e-14   1.11022e-16   1.11022e-16   1.42109e-14
 7.10543e-14   1.11022e-16  -1.13576e-13  -4.26326e-14
 0.0          -5.68434e-14  -5.66214e-14   5.68434e-14

[:, :, 2, 3] =
  2.84217e-14  -1.77636e-15  1.77636e-15  0.0
  1.11022e-16   1.11022e-16  3.55271e-15  0.0
  1.11022e-16   1.11022e-16  0.0          2.84217e-14
 -1.13687e-13   2.22045e-16  3.55271e-15  0.0

[:, :, 3, 3] =
 0.0          0.0  5.55112e-17  2.77556e-17
 1.13798e-13  0.0  1.11022e-16  5.55112e-17
 1.11022e-16  0.0  1.11022e-16  5.55112e-17
 2.22045e-16  0.0  2.22045e-16  2.22045e-16

[:, :, 4, 3] =
  2.84217e-14  0.0          2.77556e-17  1.42109e-14
 -4.26326e-14  5.68434e-14  5.55112e-17  4.25771e-14
  1.42109e-14  0.0          5.55112e-17  5.67879e-14
  1.13687e-13  0.0          2.22045e-16  0.0

;;;; …

[:, :, 1, 254] =
 1.42109e-14  -2.84217e-14   0.0          -1.42109e-14
 1.42664e-14  -2.84772e-14   2.85327e-14   2.12053e-14
 1.42664e-14  -2.84772e-14  -5.67324e-14  -3.56382e-14
 2.84217e-14   0.0           0.0           0.0

[:, :, 2, 254] =
  0.0           1.77636e-15  -1.77636e-15   2.84217e-14
 -5.55112e-17  -1.77636e-15  -1.11022e-16   2.83107e-14
  2.83662e-14   3.55271e-15  -1.88738e-15  -1.11022e-16
  0.0           3.33067e-15   7.10543e-15  -2.22045e-16

[:, :, 3, 254] =
 2.84217e-14   0.0           0.0           0.0
 1.11022e-16  -1.11022e-16  -1.11022e-16  -5.69544e-14
 2.85327e-14   6.99441e-15  -1.11022e-16  -1.11022e-16
 0.0           0.0          -4.44089e-16   0.0

[:, :, 4, 254] =
  4.26326e-14   2.84217e-14   0.0          0.0
 -3.56382e-14  -2.85327e-14  -1.11022e-16  2.84217e-14
  2.12053e-14  -1.11022e-16   5.67324e-14  7.10543e-14
  0.0          -2.22045e-16   0.0          1.42109e-13

[:, :, 1, 255] =
 1.42109e-14  -2.84217e-14   0.0          -1.42109e-14
 1.42664e-14  -2.84772e-14   2.85327e-14   2.12053e-14
 1.42664e-14  -2.84772e-14  -5.67324e-14  -3.56382e-14
 2.84217e-14   0.0           0.0           0.0

[:, :, 2, 255] =
  0.0           1.77636e-15  -1.77636e-15   2.84217e-14
 -5.55112e-17  -1.77636e-15  -1.11022e-16   2.83107e-14
  2.83662e-14   3.55271e-15  -1.88738e-15  -1.11022e-16
  0.0           3.33067e-15   7.10543e-15  -2.22045e-16

[:, :, 3, 255] =
 2.84217e-14   0.0           0.0           0.0
 1.11022e-16  -1.11022e-16  -1.11022e-16  -5.69544e-14
 2.85327e-14   6.99441e-15  -1.11022e-16  -1.11022e-16
 0.0           0.0          -4.44089e-16   0.0

[:, :, 4, 255] =
  4.26326e-14   2.84217e-14   0.0          0.0
 -3.56382e-14  -2.85327e-14  -1.11022e-16  2.84217e-14
  2.12053e-14  -1.11022e-16   5.67324e-14  7.10543e-14
  0.0          -2.22045e-16   0.0          1.42109e-13

[:, :, 1, 256] =
  7.10543e-15  -2.84217e-14   0.0           0.0
 -3.56382e-14  -1.11022e-16  -1.11022e-16  -1.42109e-14
  2.83107e-14  -1.11022e-16  -1.11022e-16  -4.26326e-14
  0.0           5.66214e-14   0.0          -1.13687e-13

[:, :, 2, 256] =
  0.0           0.0          0.0           0.0
 -1.11022e-16  -1.77636e-15  1.77636e-15  -1.11022e-16
 -1.11022e-16  -3.55271e-15  0.0           2.83107e-14
 -2.22045e-16   0.0          3.55271e-15  -5.68434e-14

[:, :, 3, 256] =
  0.0          7.10543e-15  0.0   0.0
 -1.11022e-16  0.0          0.0   2.22045e-16
 -2.85327e-14  0.0          0.0  -2.81997e-14
 -5.68434e-14  0.0          0.0   0.0

[:, :, 4, 256] =
  0.0           0.0           0.0           0.0
 -1.42109e-14   2.83107e-14   2.22045e-16   0.0
  1.42109e-14  -1.11022e-16  -5.66214e-14   0.0
  5.68434e-14  -5.68434e-14   0.0          -2.84217e-14

The result of tests coming from main is weaker than type64 in accuracy, but they are still acceptable. So I could say that there is no wrong in the part of my implementation.

As for running this part from example1.jl (similar for example2.jl and example3.jl) https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/examples/example1.jl#L30-L32
https://github.com/huiyuxie/trixi_cuda/blob/6b736229fdea3466f008e4b5edac2ddad1dc566f/examples/example1.jl#L61-L63 it will cause errors like
ERROR: MethodError: no method matching rhs!(::Vector{Float64}, ::Vector{Float64}, ::SemiHypMeshBCSolver{TreeMesh{2, SerialTree{2}}, BoundaryConditionPeriodic, DGSEM{LobattoLegendreBasis{Float64, 4, SVector{4, Float64}, Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, LobattoLegendreMortarL2{Float64, 4, Matrix{Float64}, Matrix{Float64}}, SurfaceIntegralWeakForm{FluxLaxFriedrichs{typeof(max_abs_speed_naive)}}, VolumeIntegralWeakForm}, LinearScalarAdvectionEquation2D{Float64}, typeof(initial_condition_convergence_test), Nothing, NamedTuple{(:elements, :interfaces, :boundaries, :mortars, :fstar_upper_threaded, :fstar_lower_threaded), Tuple{ElementContainer2D{Float64, Float64}, InterfaceContainer2D{Float64}, BoundaryContainer2D{Float64, Float64}, L2MortarContainer2D{Float64}, Vector{StaticArraysCore.MMatrix{1, 4, Float64, 4}}, Vector{StaticArraysCore.MMatrix{1, 4, Float64, 4}}}}}, ::Float64)

Closest candidates are:
  rhs!(::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::BC, ::Source, ::Trixi.DGMulti{NDIMS, ElemType, var"#s2999", var"#s4308", var"#s4307", Mortar, <:RefElemData{NDIMS, ElemType, var"#s2999"}} where {var"#s2999"<:Polynomial{Gauss}, ElemType, NDIMS, var"#s4308"<:Trixi.SurfaceIntegralWeakForm, var"#s4307"<:Union{Trixi.VolumeIntegralFluxDifferencing, Trixi.VolumeIntegralShockCapturingHG}, Mortar}, ::Any) where {Source, BC}
   @ Trixi ~/.julia/packages/Trixi/IbRPV/src/solvers/dgmulti/flux_differencing_gauss_sbp.jl:509
  rhs!(::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::BC, ::Source, ::Trixi.DGMulti{NDIMS, ElemType, ApproxType, var"#s4308", var"#s4307", Mortar, <:RefElemData{NDIMS, ElemType, ApproxType}} where {ElemType, NDIMS, ApproxType<:Union{SBP, AbstractDerivativeOperator}, var"#s4308"<:Trixi.SurfaceIntegralWeakForm, var"#s4307"<:Union{Trixi.VolumeIntegralFluxDifferencing, Trixi.VolumeIntegralShockCapturingHG}, Mortar}, ::Any) where {BC, Source}
   @ Trixi ~/.julia/packages/Trixi/IbRPV/src/solvers/dgmulti/flux_differencing.jl:614
  rhs!(::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::BC, ::Source, ::Trixi.DGMulti{NDIMS, ElemType, ApproxType, var"#s4308", var"#s4307", Mortar, <:RefElemData{NDIMS, ElemType, ApproxType}} where {ApproxType, ElemType, NDIMS, var"#s4308"<:Trixi.SurfaceIntegralWeakForm, var"#s4307"<:Union{Trixi.VolumeIntegralFluxDifferencing, Trixi.VolumeIntegralShockCapturingHG}, Mortar}, ::Any) where {Source, BC}
   @ Trixi ~/.julia/packages/Trixi/IbRPV/src/solvers/dgmulti/flux_differencing.jl:578
  ...

Stacktrace:
 [1] top-level scope
   @ ~/trixi_cuda/examples/example1.jl:32

Sorry I have no idea about why it works in the raw implementation but fails after packing them into rhs!().

When we call ode = semidiscretize(semi, tspan), we set up an ODEProblem from OrdinaryDiffEq.jl. For this, we first compute the coefficients of the initial condition in
https://github.com/trixi-framework/Trixi.jl/blob/53a826b62241fc0f58c0a3cd0a0acc1789a79509/src/semidiscretization/semidiscretization.jl#L82
and create the corresponding ODEProblem in
https://github.com/trixi-framework/Trixi.jl/blob/53a826b62241fc0f58c0a3cd0a0acc1789a79509/src/semidiscretization/semidiscretization.jl#L88C66-L88C66
It is set up to use our Trixi.rhs! as the ODE right-hand side determining the time derivative.
In OrdinaryDiffEq.jl, calling solve leads to a time integration loop. One step for the algorithm you mentioned above is defined in
https://github.com/SciML/OrdinaryDiffEq.jl/blob/3bba7679a275cb2ecb1af666a754d49b850c4459/src/perform_step/low_storage_rk_perform_step.jl#L266-L302
There, p is our semidiscretization semi, u is our u_ode, and du is what we call du_ode in Trixi.jl.

You could try

other time integration methods like BS3() or Tsit5()
fixed time step sizes by passing adaptive = false, dt = some_time_step_size_that_is_small_enough to solve as keyword arguments
to look at the time integration process step by step

For the last approach, you can initialize an ODE integrator as
integrator = init(ode, ...)

instead of calling
sol = solve(ode, ...)

Then, you can perform one time step by calling
step!(integrator)

You can inspect

the current solution integrator.u,
the current time integrator.t
the current time step size integrator.dt

and see where the differences come from.
See also https://docs.sciml.ai/DiffEqDocs/stable/basics/integrator/

Thanks for your reply! I will try what you suggested and update them later here.

Other time integration methods like BS3() or Tsit5()

The results of extrema(sol_cpu.u[end] - sol_gpu.u[end]) are almost the same for these three examples, like below
# BS3() for example 1
(-0.7075268104564877, 0.7075268751976517)
# Tsit5() for example 1
(-0.7075284610182293, 0.7075285257425542)

# BS3() for example 2
(-0.15900264751233806, 0.2771948607762127)
#  Tsit5() for example 2
(-0.15904315725630624, 0.27707899666396685)

# BS3() for example 3
(-5.992841043767072e-5, 4.0195123097941376e-5)
# Tsit5() for example 3
(-4.856290201704638e-5, 3.6227811167410806e-5)

Similarly for

Fixed time step sizes by passing adaptive = false, dt = some_time_step_size_that_is_small_enough to solve as keyword arguments

# `BS3(), adaptive=false, dt=0.01` for example 1
(-0.707527725595977, 0.7075277903255727)
 # `Tsit5(), adaptive=false, dt=0.01` for example 1
(-0.707527803913327, 0.7075278686422818)

# `BS3(), adaptive=false, dt=0.01` for example 2
(-0.15904403780456278, 0.27709502086661075)
 # `Tsit5(), adaptive=false, dt=0.01` for example 2
(-0.15904728701467263, 0.27707896550769817)

To summarize,

Look at the time integration process step by step

These are what I tried for both Float32 and Float64 (like for example1.jl) https://github.com/huiyuxie/trixi_cuda/blob/5b52e0868a0b985dc70fc23168dd3919d454bf7b/examples/example1.jl#L69-L86
The results showed that both Float32 and Float64 began to deviate from true values (CPU values) from step 4. For more details, see (I omit both integrator_cpu.u and integrator_gpu.u since they are too long)
# For `main` branch
Step:4
CPU: [..] 0.15809316885652322 0.061322101745377694
GPU: [..] 0.001111 0.0009999999

Step:5
CPU: [..] 0.23943041625686362 0.08133724740034042
GPU: [..] 0.011111 0.01

Step:6
CPU: [..] 0.336277708599257 0.09684729234239334
GPU: [..] 0.11111099 0.099999994

Step:7
CPU: [..] 0.4520607965859968 0.11578308798673981
GPU: [..] 1.0 0.888889

# For `type64` branch
Step:4
CPU: [..] 0.1580932402085946 0.06132212497551236
GPU: [..] 0.001111 0.0009999999

Step:5
CPU: [..] 0.23943057558094133 0.08133733537234672
GPU: [..] 0.011111 0.01

Step:6
CPU: [..] 0.3362778733894814 0.09684729780854007
GPU: [..] 0.11111099 0.099999994

Step:7
CPU: [..] 0.45206094040929407 0.11578306701981268
GPU: [..] 1.0 0.888889

Based on the above, the GPU version of integrator.dt becomes large immediately at the final step, leading to its integrator.t increases slowly at first but rapidly at the end. Also, the values of integrator.dt and integrator.t even did not change at all. So I suspect that the problem maybe come from the rhs_gpu!() that it may not change the values of du successfully after packing those kernels inside.

Wow, that is so funny! It really fails to update the value of du, see if I ran
du1 = du
rhs_gpu!(du, u, t, mesh, equations, initial_condition, boundary_conditions, source_terms, solver, cache)
du2 = du

and then du1 - du2 would give me all zeros. Something like this happened before when I tried to prototype kernels copy_to_gpu!() and copy_to_cpu!() so that's why I used du, u = ... https://github.com/huiyuxie/trixi_cuda/blob/f0811dfaedf7ba03982007889b45e0ffe415885f/cuda_dg_2d.jl#L686-L719 here. If not, then the values du would not change after running these two kernels. So I think if in some way like changing the du to a global variable in the whole process it may help, or use something like du, u = ... here
https://github.com/huiyuxie/trixi_cuda/blob/f0811dfaedf7ba03982007889b45e0ffe415885f/cuda_dg_2d.jl#L727C5-L727C24.

I tried something like du, u = ... here https://github.com/huiyuxie/trixi_cuda/blob/8145d63632a218ec4d0c264f96288d76f1408bbd/cuda_dg_2d.jl#L686-L719 and here https://github.com/huiyuxie/trixi_cuda/blob/8145d63632a218ec4d0c264f96288d76f1408bbd/cuda_dg_2d.jl#L721-L730 but it still seemed that the du values did not update through rhs_gpu!().
Also, I'm still wired about why du values cannot be updated through rhs_gpu!(), but it can be updated with success in raw implementation (i.e. without packing kernels into rhs_gpu!()).


Make sure packages dir exists when loading plugins

Fixes a crash introduced in #513 which occured when no <Profile>/packages dir was present
fs::create_directories doesnt throw when the dir already exists so its safe calling this in both PluginManager and ModManager

fs::create_directories doesnt throw when the dir already exists so its safe calling this in both PluginManager and ModManager

We should have a better system for ensuring folder structure, but this fix works as is and doesnt clutter up the codebase much

As for code review, this PR only adds a single function call to create the missing directory.

std::filesystem functions can throw exceptions so id advise reading up when they throw when reviewing :). ( The bug this PR fixes is in one way caused by me not doing that )


Dual drivers should be able to reverse just one?

it can usually/always be solved by fiddling with driver settings, or overwriting settings for one driver after the other one is set, but that's annoying


Searchable select not outputting value in wizard on page

Package
filament/forms
Package Version
v3.0.88
Laravel Version
v10.29.0
Livewire Version
v3.0.10
PHP Version
PHP 8.2.11
Problem description
When a select form element is set to searchable in a wizard, the value is not output.

Expected behavior
Expected output below.

Steps to reproduce

Clone the repository
Navigate to the wizard page
Select a customer and enter a note
Click the next button

Reproduction repository
https://github.com/brain82/filament-bug
Relevant log output
No response

Please read the docs and call $this->form->fill().

Same issue in table


Feature Request: TOTP Support

Is it possible to support TOTP support for a second factor authentication?
Kind regards

Good idea will look into it.

Did some looking and going to consider this out of scope for something I would add. Or would be needed.
For others that really want this feature, please feel free to submit a PR!


testkube: 2.1.56 -> 2.1.61

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubeshop/testkube/releases.
meta.description for testkube is: Kubernetes-native framework for test definition and execution
meta.homepage for testkube is: https://github.com/kubeshop/testkube/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.61 with grep in /nix/store/gpi6w4wfa3kdgql6gdr8sw44rm9avk2c-testkube-2.1.61
found 2.1.61 in filename of file in /nix/store/gpi6w4wfa3kdgql6gdr8sw44rm9avk2c-testkube-2.1.61

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

testkube

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gpi6w4wfa3kdgql6gdr8sw44rm9avk2c-testkube-2.1.61 \
  --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 testkube https://github.com/r-ryantm/nixpkgs/archive/9ec5e03cb1bb9364174411fe5434f68bdf4bf0e9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9ec5e03cb1bb9364174411fe5434f68bdf4bf0e9#testkube

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gpi6w4wfa3kdgql6gdr8sw44rm9avk2c-testkube-2.1.61
ls -la /nix/store/gpi6w4wfa3kdgql6gdr8sw44rm9avk2c-testkube-2.1.61/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.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

testkube

Maintainer pings
cc @mathstlouis for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

ok tested on  aarch64-darwin

@NixOS/nixpkgs-merge-bot merge


Multiple filter issue

Prerequisites
affected version:
3.11.2
make sure to check this before filing an issue:

[x] I am running the latest version
[x] I checked to make sure that this issue has not already been filed

Describe the issue
What did not work as expected?
The scanning of the logs with multiple filters doesn't works on my side. I can just scan for one filter after another.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Environment
version info from chipmunk's about menu
Failure Logs
Please include any relevant log snippets or files here.

Issue Solved

Hi @virendobariya, thanks for reporting an issue. Could you please shortly describe how you solved the issue?

Actually, it is still unclear. After a complete restart it want to default functionality.

Hello @virendobariya . Thanks for the report. It would be helpful if you can give us a little bit more insight:

what do you open? File? Some stream (like TCP, UDP, terminal command)
what format of source? Text? DLT? SomeIP?
what kind of filters you are creating? Just filters or maybe filters & charts.

Thanks in advance for the extra-information.

I opened a terminal command
The format was TEXT exported from EsoTraceViewer
Filter and charts both were under search

@virendobariya and how does the problem look like?

you've added a couple of filters, you see in the main output indeed some matches, but the search output doesn't include rows with matches?
you've added some chart expressions, you see in the main view target content, but in the charts view you don't see any?

If it's possible and your logs don't have sensitive information - the best way would be - share with us problematic peace of logs (you can export it as text file) and filters, which you are using. In this case we will have a strong way to reproduce issue and resolve it.

@virendobariya also take into account: even if you have some filters are created (which you are seeing in right sidebar, tab "Filters"); if you have in same time some active filter (filter, which you are seeing in input of search) - in this case in search output you will see only active search. If you have active search, your filters in sidebar are ignored.

The problem:
you've added a couple of filters, you see in the main output indeed some matches, but the search output doesn't include rows with matches? applies in my case.

Right now as it is working well enough, it is not possible to show the error at the moment. I will get back to you if the problem persists in future with an exact overview including screenshots.

@virendobariya

Right now as it is working well enough, it is not possible to show the error at the moment. I will get back to you if the problem persists in future with an exact overview including screenshots.

I'm closing issue right now, because isn't confirmed. If you will got this issue again, please reopen it. And once again thanks!


How can I add files (like pictures) to the chat?

As we know, the chatgpt platform could use files as input, however, I haven't find this feature in Better ChatGPT. Is is possible to realize it in the future?

https://github.com/animalnots/BetterChatGPT-VISION/releases

@animalnots
Great fork repository! Thank you!


Can this library be released to the production environment?

Thanks to the author for providing this useful library

Hi & thanks! I can’t speak for the App Store but I don’t think there are any technical reasons why this wouldn’t be possible.


Examples does not work

Is this a bug report?
Yes

Have you read the Installation Instructions?
I'm raising an issue about the setup instruction for Example Project. I've read them all here: https://github.com/react-community/react-native-maps/blob/master/docs/examples-setup.md
Environment
Not relevant as I'm not doing anything on my own project. I just try to build/run the cloned code, example.

Steps to Reproduce

git clone https://github.com/react-community/react-native-maps.git
cd react-native-maps
yarn
yarn run:android

Expected Behavior

It builds and run
Actual Behavior

FAILURE: Build failed with an exception.

Where:
Build file '/Users/namtrang/workspace/react-native-maps/lib/android/build.gradle' line: 46

What went wrong:
A problem occurred evaluating project ':react-native-maps-lib'.

Could not find method compileOnly() for arguments [com.facebook.react:react-native:+] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Reproducible Demo

https://github.com/react-community/react-native-maps/blob/master/docs/examples-setup.md

Apparently it is related to the Graddle version. I tried this solution (#2155) but even after changing the build.gradle I got a different build error.

Same with iOS.
I'm following the instructions but noticed that the command npm run build:ios within package.json results in "build:ios": "bundle install --path ./example/ios/bundles && bundle exec pod install --project-directory=./example/ios/",. It appears that we are missing the /bundles folder within /ios.


fix: simdata-api deployment

What new features does this PR implement?
resuses the existing path data.biosimulations.dev/org which was used by HSDS for simdata-api.  This allows the TLS cert to be reused.
What bugs does this PR fix?
a cert error occurs when accessing the api externally.

:tada: This PR is included in version 9.55.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Early loading of external CompUnit::Repository

Allow an external CompUnit::Repository to be loaded before regular modules such that they are available to attempt loading from an identity matching their short-id. Something like:
perl6 -CCompUnit::Repository::GitHub -e 'require <github#http://github.com/user/repo.git>; ...'
or the example in the old s22:
CompUnitRepo::GitHub#masak/html-template
Can this be accomplished with CompUnit::Loader if the proper initialization bits are placed in ModuleLoader.nqp? Or will such an external CompUnit::Repository require its own CompUnit::Loader as well?

CompUnit::Loader could do this just fine. What would be nice was a way to load the CompUnit::Repository implementation while still retaining the precompilation ability. Right now once you change the $*REPO chain after a module has been loaded already, we have to disable precomp completely.


Add guard for just JWT validation.

Is your feature request related to a problem? Please describe.
When using Laravel for just and API we cannot use the hosted cognito login screen. Since the guard only checks for tokens it generates and does not actually verify or validate the JWT token itself.
Describe the solution you'd like
An additional guard which validates the access token and verifies its signature against the public key available at the well known URL. You could then cache the well known certificate for a period of time and even cache the access token for a period of time to prevent the crypto operations every request.
Describe alternatives you've considered
We have considered using this for our registration component to create the users and then writing our own Guard for the validation, but I think this fits in this package.
An alternative would be to use Auth0 or Okta which provide libraries for this very purpose.

Thanks @jamesrusso for the inputs. This is very specially intended for AWS Cognito. The token issued by AWS Cognito is JWT-compliant. The JWT token can work with generic certificates however, custom certificates would not work well with this library.
Have you tried tymondesigns/jwt-auth? This is based on JWT-based authentication.
We use Auth0 and Okta in other projects and plan to develop a separate library soon.

@jamesrusso Can you share what you have written, so that we understand the requirement better?

The library you mention is for generating and validating JWT tokens generated itself (hence you define your own JET secret). A better reference would be https://github.com/benbjurstrom/cognito-jwt-guard. I cannot use this one due to some version dependencies, but perhaps I should just fork and update it.
I'm looking for a guard which would validate a token against the public key of the issuer. In then cognito example it would download the key from https://cognito-idp..amazonaws.com//.well-known/jwks.json and the use it to validate it. The user in the guard would be selected by the uid or email in that access token.
https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-user-pools-using-tokens-verifying-a-jwt.html
If I understand this library correctly it doesn't verify verify the token it simply stores it in the session. There isn't a need to verify it since it is obtained from the cognito API. However, if it is instead obtained 100% on the browser side of things, then this library doesn't work for me.
It's my opinion that an API implementation with a bearer token should be competent stateless and not require a session.
Our project is a SPA with api.

This library gets and token from Cognito and authorizes it with Cognito every time using the AWS SDK. Just the token TTL is managed outside of the Cognito based on the expiry time.
We have a plan to use the Cognito certificates to read the token and use the sub as the key identifier. There is an open issue for the same.


manual/options-to-docbook: remove string escaping

This removes escaping of strings which lead to a false presentation in the
resulting manpages (e.g. "${someExpression}" in an option's default
value resulted in "\${someExpression}" in the manpages) which cannot be copied as is
and thus might be misleading in a manual.
Multiline-strings are now identified by the contained newlines and escaping them
is not necessary as they already have to be escaped in the module's definition.
-> example of escaped default value
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This PR seems wrong to me. In general, special characters like \, " and ${ must be escaped when rendering strings. Otherwise a string like "\"" will be rendered as """.
The real issue here is that the contents of defaultText should not be escaped. Unfortunately, it looks like optionAttrSetToDocList' doesn't allow distinguishing between default and defaultText.

I take it this can be closed?


Update sites.js

Oops! Sorry about that! I'll close this and open one with this fixed! Thank you for letting me know!


Update .travis.yml

Codecov Report

Merging #6387 into #noissue_cache_node_modules will not change coverage.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##           #noissue_cache_node_modules    #6387   +/-   ##
============================================================
  Coverage                        39.65%   39.65%
============================================================
  Files                             3065     3065
  Lines                            91444    91444
  Branches                         11842    11842
============================================================
  Hits                             36264    36264
+ Misses                           52195    52191    -4
- Partials                          2985     2989    +4

Impacted Files
Coverage Δ

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
52% <0%> (-16%)
:arrow_down:

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
55.55% <0%> (-11.12%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
84.1% <0%> (-4.64%)
:arrow_down:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
57.44% <0%> (-2.13%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.22% <0%> (-1.06%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.07% <0%> (-0.33%)
:arrow_down:

...rver/cluster/zookeeper/CuratorZookeeperClient.java
88.57% <0%> (+0.95%)
:arrow_up:

...cluster/zookeeper/ZookeeperClusterDataManager.java
58.06% <0%> (+3.22%)
:arrow_up:

...r/zookeeper/ZookeeperClusterDataManagerHelper.java
84.44% <0%> (+4.44%)
:arrow_up:

...r/zookeeper/CuratorZookeeperConnectionManager.java
75% <0%> (+6.25%)
:arrow_up:

... and 3 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 e7ab33d...5a3f164. Read the comment docs.


Only getting the last commit on "CHANGELOG.md"

My first Issue open in any github project.
When runned (auto-changelog) localy its beatfull, but when the github runs in the workflow, doesnt.
The action is made on a merge.
I use npm.
It run: auto-changelog -p --template changelog-template.hbs --commit-limit false && git add CHANGELOG.md.
But always get only the last commit.
Anyone knows why ?

--commit-limit=false?

I try, but yet only one :(

my repo: https://github.com/felipe-frade/github-actions-test-2
and the log

<EMAIL_ADDRESS>version /home/runner/work/github-actions-test-2/github-actions-test-2
auto-changelog -p --template changelog-template.hbs --commit-limit false && git add CHANGELOG.md

auto-changelog: Fetching tags…auto-changelog: 2 version tags found…auto-changelog: Fetched v1.10.0…auto-changelog: Fetched v1.10.0…auto-changelog: 1 kB written to CHANGELOG.md

<EMAIL_ADDRESS>version-json /home/runner/work/github-actions-test-2/github-actions-test-2
auto-changelog --template json --output changelog-data.json

auto-changelog: Fetching tags…auto-changelog: 1 version tags found…auto-changelog: Fetched v1.10.0…auto-changelog: 1 kB written to changelog-data.json

Hi @felipe-frade, I got a similar problem today. Just try adding fetch-depth: 0 to the Checkout step:
jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          # default depth is 1, which is not enough for changelog generation
          fetch-depth: 0


ListAlertsForOrg options should support cursor pagination

At the moment ListAlertsForOrg function supports only offset (page) pagination while querying REST API https://api.github.com/orgs/ORG/code-scanning/alerts endpoint returns link header with after query parameter. Therefore, the AlertListOptions struct should include ListCursorOptions field.

According to the docs here: https://docs.github.com/en/rest/code-scanning#list-code-scanning-alerts-for-an-organization
These endpoints also take a page parameter that it an integer, which is what ListOptions provides.
So unfortunately, this is not a simple replacement, and #2512 would be a breaking API change that would confuse anybody currently using the Page field.
This is going to need some discussion as how to correctly solve this situation.
My initial thought is that we need a third type of ListCursorOptions where Page is an int instead of a string, but am open to other ideas.

Yikes! That is a bit disturbing, @jporzucek - thank you for the research!
Would you mind contacting GitHub tech support and explaining the situation to them and see if they have a recommendation for us here in this repo?  Feel free to point to this issue that you started.

This seems to be a consistent issue across GitHub's API. I had just recently resolved this issue for Secret Scan Alerts #2446

Ah, right... thank you for the reminder, @AbbanMustafa !
So we are fine with pulling in both types of list options into the struct where it is necessary.
@jporzucek - could you please do something similar to #2446 ?


test: :green_heart: Added tag-version.yml

added version tagging workflow for use on github

All checks pass, CircleCI pipeline is no longer in use.


Too long: must have at most 1048576 bytes

Hi guys,
I am trying to create the configmap to save the test, but there seems to be a size limitation of 1Mb.
Do you know what other alternative can be implemented for this case?
Thanks a lot.

Support was added for a volume mount instead of configmap, I'd recommend you use that.
https://github.com/grafana/k6-operator/blob/main/api/v1alpha1/k6_types.go#L67
Instead of specifying configMap you should be able to specify volume mount, name and file to execute.

Do you suddenly have an example?

What @KnechtionsCoding said. We should probably mention this limitation in the docs though. 👍🏽


grafana: clean grafana descriptors

Update grafana to 6.0.0
Remove batch job to insert dashboard and datasources
Store descriptors as they are printed by kubectl get -o yaml for
easy comparison between version

Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-me-please

Coverage decreased (-0.01%) to 43.232% when pulling 6705ac239d1e3324b04fa630800a32d23083ca82 on pr/grafana-update into f85aab285b9c49246dd6691312c844268d729dc9 on master.


cross platform: add edge date cases support

This PR improves xplat date implementation with edge cases support.
Now test cases for Date passes on Ubuntu / Debian

tested against VSOFull and its test cases
no perf difference on Windows measured

Update:
Some details on what's been done with this update.

Linux implementation no longer converts from Windows SYSTEMTIME.
ChakraCore's internal YMD structure was a good fit between tm and
SYSTEMTIME. Besides, new implementation spends less time there.

Now xplat handles out of range year cases ( <1900 or > 2100) and
Feb28/29 + 1 (see test file under Date)

ChakraCore's common date utilities consider the start year is epoch.
Besides, system time and clock is based on epoch too. However, the C
api that calculates the time zone offset, and DST in case of leap year
depends on broken-out time starting from 1900.
We handle the leap year differences.

On xplat we need exact date to grab right tm_zone information instead
of caching approach on Windows. Windows API can bring back both DTS and
STD abbrv with a single call.

Ping @digitalinfinity @jianchun @curtisman

@digitalinfinity thanks for the review. PR is updated.

Overall it looks fine, but I didn't look at the logic too closely.

@digitalinfinity @curtisman Thanks for the review


Add another way to capture debug logs without the use of setting an environment variable.

In full IIS, reading an environment variable in the worker process isn't convenient as:

The environment variable must be set on the AppPool, which is part of the apphost.config. Also it is only supported on win10+
Must be set system wide and requires was/ computer restart to have the environment variable set.

After working on the full IIS tests, I personally feel that we should move away from setting environment variables and put more things in the web.config (in handler settings, for example).

This is a good diagnostics feature!

Done in https://github.com/aspnet/IISIntegration/pull/1033


Fix Package.swift

I would like to use your package, but I could not import it because there was no package whose url was https://github.com/kieranb662/Shapes.git.
To work around this, I changed package url and rename it in Package.swift.
I don't know whether it is correct, so please review my PR before marging.
Thanks.

not working in latest xcode
use this: https://github.com/Sling-Inc/Sliders-SwiftUI.git
target xcode14 branch


How to get Public Key from account hash?

client := sdk.NewRpcClient("xxxxx")
ressult, err := client.GetBlockTransfersByHeight(10000)
for _, r := range res {
    fmt.Println(r.DeployHash)
    fmt.Println(r.From)
    fmt.Println(r.To)
    fmt.Println(r.Amount)
}

From and To The format is account-hash-xxx
So, How to get Public Key from account hash?
Because exchanges use public key as the deposit address.
thanks

A hash by definition is a one-way conversion.  To convert between them, you need to keep an account-hash to public-key map.

ok, In other words, is there an rpc or rest api that can get the public key based on the account hash?

and, Are there any mainnet nodes available?
like testnet：http://testnet-node.make.services:7777/rpc


Get some basic measurements for a hello world polymer app

 Issue by jakemac53
Originally opened as dart-lang/sdk#21205

Total time until Polymer.onReady
Time spent loading polyfills
Time spent loading polymer.js
Get a high level breakdown of initPolymer() and what is taking time.

Get breakdown on both desktop and nexus 4, as well as dart2js and dartium/content shell.

 Comment by jakemac53

Some screenshots from a basic test harness I set up, https://drive.google.com/a/google.com/folderview?id=0B_91yIEjtfV9ZXZBRGJ1c2MxbDA&usp=sharing. These same tests can be ran locally using this repo https://github.com/jakemac53/polymer-perf-elements and running example/index.html.
The most interesting thing you will see is the time from the end of the body until the first line of dart code runs is accounting for over half the total load time across each of the platforms, and is over a second on the nexus 4. This happens even when running with dart2js (all the supplied stats were run using dart2js), so something strange is going on there that is causing a lot of slowness.

Added Done label.


[FIX] Incomplete string escaping or encoding

JIRA: CPOUI5FOUNDATION-728

coverage: 94.443%. remained the same
when pulling 760731f7e661b1381f40a19a9634559645ad194c on fix-incomplete-string-escape
into 52fb507c69c5e4279d388e130985da5465656682 on main.


go-feature-flag-in-process is not in the package

updated to the latest 0.2.0 but did not want to change my existing usage of the lib, so I wanted to switch to "in-process" part that uses go feature flag under the hood.
I cannot use that provider.

Thanks for raising this issue, let me check and I get back to you.

@zaitera I've reproduced your issue on my computer and I think the issue was because it is a brand new package and my go installation had some caching issue.
What I did do to solve the caching issue?
I have forced the version when doing the 1st go get command.
go get<EMAIL_ADDRESS>
This has solved the problem and download the module.
Will it work for others?
To be sure it was a caching issue, I also installed a fresh Ubuntu with a brand new go environment.
When doing the go get github.com/open-feature/go-sdk-contrib/providers/go-feature-flag-in-process it has worked without specifying any version.
Can you tell me if it has worked for you too?
If so don't hesitate to close the issue.

@thomaspoignant thanks for the quick response, that worked fine!

I am glad it worked for you 🎉
Thanks for raising it !

@thomaspoignant just a quick question, what is the reason behind calling it in process?
is it something we need to treat carefully and not take to production?
because it seems to me it is just the same code that used to be on normal go-feature-flag before that latest update to 0.2.0

@zaitera it is called in-process because the evaluation is made directly in the provider and is not doing any remote call to the relay-proxy.
It is not a reference to the state of the provider, it is production-ready.

clear, thanks for the quick responses :)


PolylineGeometry colorsPerVertex seems broken in 1.6+

This code shows per-vertex colours in Sandcastle in 1.5 but not in 1.6 or master.  Is there an interface change I missed?
var viewer = new Cesium.Viewer('cesiumContainer');
var scene = viewer.scene;

var instance = new Cesium.GeometryInstance({
  geometry : new Cesium.PolylineGeometry({
      positions: Cesium.Cartesian3.fromDegreesArray([
    0.0, 0.0,
    5.0, 0.0,
    5.0, 5.0
  ]),
      width: 5.0,
      vertexFormat: Cesium.PolylineColorAppearance.VERTEX_FORMAT,
      colors:[new Cesium.Color(1,0,0), new Cesium.Color(0,1,0), new Cesium.Color(0,0,1)],
      colorsPerVertex: true,
      ellipsoid: Cesium.Ellipsoid.WGS84  // <- required for Cesium 1.5
    }),
  id : 'object returned when this instance is picked and to get/set per-instance attributes'
});
scene.primitives.add(new Cesium.Primitive({
  geometryInstances : instance,
  appearance : new Cesium.PolylineColorAppearance({})
}));

This was indeed a bug due to a typo. It will be fixed in 1.7.

Fixed in #2529

Great, thanks!


External Waivers occasionally not linking

When working through external waivers and trying to link them to existing publications, in some cases I'm not able to link the publication listed in the external waiver to the publication in RMD.
https://metadata.libraries.psu.edu/admin/external_publication_waiver/7
https://metadata.libraries.psu.edu/admin/external_publication_waiver/8
https://metadata.libraries.psu.edu/admin/external_publication_waiver/9
Linking that waiver produces an error that the link already exists but the ability to link the publication to that waiver is still there.

@DanCoughlin I'm trying to understand the workflow that led to this problem. Looking at the first example, it looks like you already created a waiver that you linked to this user's authorship:  https://metadata.libraries.psu.edu/admin/internal_publication_waiver/51. That's the reason for the error that you're seeing - an authorship should only be associated with one waiver, so the one that you already created prevents you from linking the external waiver. What was it that prompted you to create https://metadata.libraries.psu.edu/admin/internal_publication_waiver/51?
I presume that the proper resolution to this is for us to delete the waiver that you created and then link the external one that the author submitted, do you agree? Then maybe we need to give admins the ability to delete waivers (now that they can create them) and provide a little more visibility into how these records are connected?

@EricDurante  Ohhh, ok. Dang that was a good catch! The bigger issue is just making sure the publication has a waiver so the author wont be bothered to submit an OA copy if they've already submitted a waiver. Whether it's internal or external isn't as important AFAIK.

@DanCoughlin Gotcha. Still, at some point I think that we should make sure that this workflow is streamlined so that we don't end up with a bunch of "clutter" eventually.
In terms of satisfying the conditions for not sending the OA email, the type of waiver does matter. If only an external waiver has been submitted for a publication that's actually in RMD, then an email will still be sent for that publication because we haven't made the connection between the waiver and the publication record yet. That's why it'll be important to stay on top of looking for matches and linking the external waivers. Creating the internal waivers manually, as you did in these cases, also satisfies the condition because that's part of what happens when you "link" an external waiver, but it's not the ideal workflow.

@EricDurante right, makes sense. Only linked waivers wont send emails.


Concurrent Procedure Support

This activity contains the following changes:

Adds support for concurrent procedures in the state machine framework.
Script optimizations.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Abandoning this PR. Changes were merged to
https://github.com/omec-project/Nucleus/pull/83


refactor: decouple CCs and messages from host, split parsing and creation, split ZWaveNode class

See migration guide for details.
fixes: https://github.com/zwave-js/node-zwave-js/issues/7261

@zwave-js-bot pack this

@zwave-js-bot automerge


Add temporary shims to Bug's Codable implementation to support proposed new layout.

We're proposing a new set of stored properties for Bug in #412. This new layout is incompatible with the old one when using Codable. This change adds a (very!) temporary workaround to ensure that bugs encoded with the current layout can be decoded with the new one once it is accepted and merged in.
This implementation can be removed when #412 is merged.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test

@swift-ci please test

Windows failure is a known issue. Linux CI is down right now. Merging as-is.


CI: Get list of the slowest 30 test durations

Uses https://docs.pytest.org/en/latest/how-to/usage.html#profiling-test-execution-duration to get a list of slowest 30 tests for which the durations is over 1.0s long.
This is a small change but will help identify if a test takes too long. Found a need to do that while working on https://github.com/astro-projects/astro/pull/367 and https://github.com/astro-projects/astro/pull/370

@kaxil, that's very interesting. I didn't know about this feature!
Even though we're using "pytest>=6.0", which should support this feature, the CI didn't seem particularly happy with it; any thoughts about it? It may relate to how pytest parses the config on the pyproject.toml.
nox > pytest tests/test_example_dags.py -k sqlite --cov=src --cov-report=xml --cov-branch
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: argument --durations: invalid int value: '30 --durations-min=1.0' (via addopts config)

nox > Command pytest tests/test_example_dags.py -k sqlite --cov=src --cov-report=xml --cov-branch failed with exit code 4

@tatiana fixed :)

That's great, @kaxil , thank you! :tada:
What is causing the current tests to fail? It seems they are passing in main, it would be great to address the root cause of the issue before merging this PR.

That's great, @kaxil , thank you! 🎉 What is causing the current tests to fail? It seems they are passing in main, it would be great to address the root cause of the issue before merging this PR.

It's the one I posted on Slack about:
E       sqlalchemy.exc.ProgrammingError: (snowflake.connector.errors.ProgrammingError) 090153 (22000): 01a46079-0604-a49f-0000-682108eb3a66: The result set size exceeded the max number of rows(10000) supported for SHOW statements. Use LIMIT option to limit result set to a smaller number.
E       [SQL: SHOW /* sqlalchemy:get_table_names */ TABLES IN astroflow_ci]
E       (Background on this error at: http://sqlalche.me/e/14/f405)

But I don't think we should hold this PR for that failure, it is completely unrelated, this PR barely does not impact the library just gives us the slowest test.


Fix sort when page is changed in view pager

Issue : When page is switched in view pager and sort option is changed headers are not arranged properly

I have combined sort and filter Update because there can case in which sort option is changed with filter


Changing editor default direction in RTL HTML document does not work

In the bidi.html demo file, Change the HTML direction to RTL ()
Then try to change the default directio of the editor.
The direction remains RTL

@BAMIR. FYI.

@amirbrans FYI.

@wajnberg thanks for fixing. Based on the comments in PR it looks like the fix for this issue will be available with CodeMirror 5.29.0 (expected to be released in Aug 2017).


Rename item IDs

Rename confusing item ids like ethereumore to ethereum_ore, etc.

valkyrium_ore*

Remove mod id   limit for 1.14 version?

there is no 1.14 version
mod id limits is not a problem, if it was we could use mod ids and data values


Fix lint issues

As per golangci-lint,
cmd/main.go:62:2: SA1019: rand.Seed has been deprecated since Go 1.20 and an alternative has been available since Go 1.0: Programs that call Seed and then expect a specific sequence of results from the global random source (using functions such as Int) can be broken when a dependency changes how much it consumes from the global random source. To avoid such breakages, programs that need a specific result sequence should use NewRand(NewSource(seed)) to obtain a random generator that other packages cannot access. (staticcheck)
	rand.Seed(time.Now().UnixNano())
	^

:thumbsup: Coverage increased from [%] to [67.1125%]


Add Web NFC Shopping Cart

Add my Web NFC Shopping Cart demo. Requires Web NFC for full functionality, but there is a "fake mode" that allows playing around with the app.

Any update on this, or is this project abandoned?


MSL compute shader support?

I'm wondering about the status of the compute shader support of the MSL backend...
When I checked for the last time, the following items were not working:

Workgroup storage class
shared uint kernel_values[64];

OpControlBarrier and OpMemoryBarrier
// wait for all inputs to be ready...
groupMemoryBarrier();
barrier();

Is there any plan to support them? Or is anyone currently working on them?

Because they were crucial components to make compute shaders unique from other shaders, I managed to implement them in my fork to use in an experimental project that I am working on. This currently has the following restrictions:

Shared variables cannot have a matrix type. Matrix types in Metal cannot be default-constructed in the threadgroup memory space.

OpMemoryBarrier has no MSL counterpart. Memory barriers only can be inserted as a part of a control barrier.
To make matters worse, barrier() in GLSL ES does not imply a memory barrier and users have to use the following common idiom:
groupMemoryBarrier();
barrier();

This code is translated by glslang into two separate instructions; OpMemoryBarrier that only inserts a workgroup memory barrier which does not have a MSL counterpart, and OpControlBarrier that only inserts a control barrier. As a result, the direct MSL translation of this code would look like this:
// (OpMemoryBarrier is ignored because there's no MSL counterpart)
threadgroup_barrier(mem_flags::mem_none);

This is unacceptable, so as a work-around I decided to automatically include Workgroup in OpControlBarrier's memory semantics. Therefore, the above code will be translated to
// memory barrier is not supported in MSL
threadgroup_barrier(mem_flags::mem_threadgroup);

Even with these restrictions, I think this adds a kind of real support for compute shader. With it, I successfully transpiled and got a simple convolution kernel working.  Let me know if you want me to send a pull request. (I will need to update reference/shaders-msl before doing that)

I will be able to look at computer shader support in a couple of weeks.

Development of this is now underway. I should be able to release functional code by next week.

Can this be closed now?


Show edition more clearly on the record in front office

In front office. When a book has different editions, it would be helpful to see more clearly which edition it is, ideally on the top of the page like in back office. For example:

Looks good!

Perfect for me!


Loading local datasets with split=‘test’

I’m trying to evaluate a new model with LongBench and would like to load the datasets stored locally (downloaded and unzipped directly from HuggingFace). But whenever I’m reading the data with flag split=‘test’ in pred.py (say we are reading xxx.jsonl within the loop, the line is modded as data = load_dataset("json", data_files="/some/dir/xxx.jsonl", split="test") ), it will return a ValurError: Unknown split “test”. Should be one of [‘train’]. Is there any pre-processing I should perform on the downloaded data? Thanks in advance.

If you have downloaded the dataset files locally, you can load them via:
data = [json.loads(line) for line in open("/some/dir/xxx.jsonl", "r", encoding="utf-8")]


Pane re-sizing allows you to shrink but not expand

Challenge Name
https://learn.freecodecamp.org/responsive-web-design/basic-html-and-html5/say-hello-to-html-elements
Issue Description
There are several issues here (similar to the issue that already existed in Beta):

When shrinking and expanding the lesson pane => the editor size does not expand to the new pane size when expanding the lesson pane. No issue on expanding the lesson pane, adjusts accordingly

Shirking the editor window is fine, expanding has several issues
a) does not allow you to expand the editor window, this green highlighted bar shows up

b) to get the editor back, you need to re-size the lesson plan, then you can re-size the editor/preview pane

After attempting to expand the editor/preview pane which fails, if you move your cursor over the lesson pane ( no mouse button is clicked) the cusor changes to from arrow to expanding icon and it resizes the editor/preview pane and follows the mouse movement.

Browser Information
Browser Name, Version:
Firefox Quantum 60.0.1 (64-bit)
Chrome: Version 66.0.3359.117 (64-bit)
Operating System: Windows 10 Pro 64-bit
Mobile, Desktop, or Tablet: Dell Latitude Laptop (15")

I'm not sure if this is the same issue or not but I'll just put it here since it is similar. When I resize, the editor pane stays small. Also, on small window sizes, the error messages in the bottom right are hard to see. See gif for demonstration.

@mstellaluna and @beaucarnes, I'm working on this now. Made some changes to both the editor and the output so that they expand and shrink horizontally when the browser window is resized. I'm currently working on a way to resize them vertically, and also resize horizontally/vertically when the panes resized, but the window size remains the same.

Closed via #82


[RFC] Store RestorationState into FrameState

Context
In order to prepare for the possibility to encode tiles in parallel, I implemented an iterator providing non-overlapping tiles (TileMut<'_>), which are a "view" on the underlying frame (see https://github.com/xiph/rav1e/pull/821).
But frames are only part of the data to be split.
To encode a tile, we will also need one TileState (similar to FrameState) per tile, each providing access to the tile (TileMut<'_>).
In addition, currently, the RestorationState is used both at "tile level" (accessing only data for a specific tile, independently of other tiles) and at "frame level" (crossing tile borders). To allow tile parallelization, the same way we created TileMut<'_> view from a Frame, we can create a TileRestorationStateMut<'_> (or whatever the name) view from a RestorationState. Concretely, such a view would expose only the RestorationUnits (stored in the RestorationPlanes) belonging to the tile.
Objective
Instead of managing several views (TileMut<'_>, TileStateMut<'_>, TileRestorationStateMut<'_>), the idea is to only use one (top-level) TileStateMut<'_> containing all tile-specific data and views.
Concretely, FrameState would expose an iterator providing TileStateMut<'_> instances, each one used to encode a tile (possibly in its own thread).
In TileStateMut<'_>:

tile_state.tile will expose the TileMut<'_>;
tile_state.restoration will expose the TileRestorationStateMut<'_>.

Once all the tiles for a frame have been encoded, we can then access the full FrameState (which has been written through the tile views) to execute "frame level" stuff (deblocking, restoration, …).
PR
The first step to get a "unified" view for a tile, containing all necessary states, is to move RestorationState into FrameState.
Here is a summary of the commits (see commit messages for more details):

commit 1 removes FrameState::widow(), which is unused and add unnecessary restrictions.
commit 2 avoids to borrow FrameState from a non-const RestorationState method (this would break borrowing rules once we move it).
commit 3 make RestorationState derive Debug.
commit 4 actually moves RestorationState into FrameState.
optional commits 5 and 6 narrow the borrowing to FrameState fields only (for consistency with what we do with RestorationState).

This PR is independent of tile encoding support (it just paves the way).
Impact
This will conflicts with https://github.com/xiph/rav1e/pull/833, but should be easy to resolve.

you could shuffle away the Debug decoration in a separate commit

Done. :wink:

Yes. However, I'm not happy with FrameState::new() requiring a &Sequence, just to pass it to RestorationState::new(), which just uses it to read the boolean use_128x128_superblock.


Added Pwnagotchi support

I added the ability to run the wall_of_flippers mode directly from the invocation without having to use the interactive ui.
The reason I made this change is to be able to run Wall of Flippers in the background as a systemd process. Mainly I did it so that it is possible to run the script on Pwnagotchi then using the plugin I made to see the name of the Flipper on the display, but the same thing can be done on any Linux system (except for the plugin of course).
I also added the instructions in the README about installing on the pwnagotchi trying to follow the current style.
For now the only mode that is possible to invoke from the command line is the wall_of_flippers mode, but it should be quick to add the other modes as well.
Last thing: when in no-ui mode all banner printing is disabled and only logged when a Flipper device changes from offline to online and vice versa, this is because the logs are looked at periodically.
I tried to touch as little of the existing code as possible, adding only the bare minimum.

I'll take a look when I can. I did notice that one of features hci selection was being skipped on windows resulting in hci_device not being defined

I did notice that one of features hci selection was being skipped on windows resulting in hci_device not being defined

I tried to run it on Windows (both, using interactive ui and using cli args) but can't reproduce the error. Can you add more details/how to reproduce it so I can push a fix?

Thank you, don't seem to have the issue anymore. Will take a further look when I get back and have time 👍

I updated the README.md documentation for the systemd service because after writing to NerdyJedi for #22, while debugging the problem we saw that the service docs wasn't updated (I forgot to push the updated version). Now it's fixed and working. Also #22 is solved.


ci: modify github alpha release action

Should only check the tag on the most recent commit instead finding the most recent tag.

Merge activity

May 20, 8:08 PM EDT: @juemrami started a stack merge that includes this pull request via Graphite.


Support mio version 0.8.x

This (very nice) crate seems to work just fine with mio 0.8.x, despite being a few years old.

Whoops, just saw there are identical pull requests.


Deletion not expected

Hi !
Version : 4.3
I encountered a behaviour I couldn't understand. This is my config file :
[/home/backup/data/mysql/production/scrap/fr/done]
relaxed = yes
include = '*.xbstream'
weekly = 3
monthly = 2
yearly = always
ionice = idle

And this is the behaviour rotate-backups had when launched :
Sep 27 12:04:02 backup-0001 rotate-backups[19632]: INFO Scanning /home/backup/data/mysql/production/scrap/fr/done for backups ..
Sep 27 12:04:02 backup-0001 rotate-backups[19632]: INFO Found 7 timestamped backups in /home/backup/data/mysql/production/scrap/fr/done.
Sep 27 12:04:02 backup-0001 rotate-backups[19632]: INFO Preserving /home/backup/data/mysql/production/scrap/fr/done/2017-01-13:22-24-57.xbstream (matches 'yearly' retention period) ..
Sep 27 12:04:02 backup-0001 rotate-backups[19632]: INFO Deleting /home/backup/data/mysql/production/scrap/fr/done/2017-05-17-mc_log_range ..
Sep 27 12:04:03 backup-0001 rotate-backups[19632]: INFO Deleting /home/backup/data/mysql/production/scrap/fr/done/2017-05-17-mc_log_range.tar.gz ..
Sep 27 12:04:03 backup-0001 rotate-backups[19632]: INFO Preserving /home/backup/data/mysql/production/scrap/fr/done/2017-08-04:04-45-05.xbstream (matches 'monthly' retention period) ..
Sep 27 12:04:03 backup-0001 rotate-backups[19632]: INFO Preserving /home/backup/data/mysql/production/scrap/fr/done/2017-09-09:19-48-41.xbstream (matches 'weekly' and 'monthly' retention periods) ..
Sep 27 12:04:03 backup-0001 rotate-backups[19632]: INFO Preserving /home/backup/data/mysql/production/scrap/fr/done/2017-09-20:07-17-24.xbstream (matches 'weekly' retention period) ..
Sep 27 12:04:03 backup-0001 rotate-backups[19632]: INFO Preserving /home/backup/data/mysql/production/scrap/fr/done/2017-09-27-mc_log_range (matches 'weekly' retention period) ..

The folder 2017-05-17-mc_log_range and the file 2017-05-17-mc_log_range.tar.gz were deleted even if they don't match the pattern '*.xbstream' defined in the config file.
Am I doing something wrong ?

Naturally, I'm not sore about the files being deleted (there are ample warnings about using --dry-run in the documentation), I'm just curious about the source for this surprising behavior.

Hi @Klabuser and thanks for the feedback. Looking at your configuration file I notice two problems:

It contains the option name include but rotate-backups is expecting include-list instead.
The pattern is quoted in strings but rotate-backups is expecting a literal pattern (without the quotes).

This made me realize that the include-list and exclude-list weren't documented anywhere, so in b150a239bffc7c8a2bcf3559248dd6861e18bca8 I documented all of the supported configuration file options and their expected values (e.g. that the patterns shouldn't be quoted). This information is now available in the online documentation.
I'm going to close this issue now because the actual include/exclude list processing is working fine, it was just the documentation that was insufficient.


SurfaceView support

Thanks for your amazing work ! But where are you in SurfaceView support ?

Hi @thomas-le-bihan I've created a new ticket #36 to track the progress of SurfaceView support. It will be release in our v1.1.0 release. If you have any comments or feature suggestions leave them there. Thanks!


Migrate the BFF parameters to the OneCX public repository

copy source code from gitlab
update package structure
switch to onecx portal-bff-lib
switch to common onecx client

Fix: https://github.com/onecx/onecx-parameter-bff/pull/3


Backport "HBASE-23660 hbase:meta's table.jsp ref to wrong rs address"…

… to branch-2

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  7s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
7m 34s
branch-2 passed

+1 :green_heart:
javadoc
0m 47s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
7m 34s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
158m 18s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

178m 58s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1005/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1005

Optional Tests
dupname asflicense javac javadoc unit

uname
Linux 92ac67dbf793 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1005/out/precommit/personality/provided.sh

git revision
branch-2 / e242d84b97

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1005/1/testReport/

Max. process+thread count
5009 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1005/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Add some compatibility imports

Hi!
I've added a compatibility import replacement for django 4.0 (TRANSLATOR_COMMENT_MARK, we were actually importing this in our code base at my work) and while at it, added some older one fitting existing target-version settings.
Fixes #293
I also noticed some compatibility imports were not mentioned in the readme so I've added the missing sections.
Cheers

I'm not quite fan of having so much compatibility import documentation section. Maybe it's better to group everything in a section at the end ?


Bugs to Report for Inital Release-

I decided to give Godotzilla a go and use it, and it's pretty great! Following your tutorials does make it easier to work on and understand. However, I did find two bugs to report here. I also do have a suggestion.
Bugs:

When shifting the board piece node for a new board or an existing board, when you enter in game, the icons will be shifted... but the "positions" won't be. So if I move Godzilla two tiles down, selecting the tile he seems to be on won't do anything, but going two tiles above somehow selects Godzilla, and lets you move him like a sort of ghost sprite. I'm aware that probably wasn't what the tutorial meant, but it doesn't go into detail on how to move it and not have it break in this way if I'm missing something.
When you move to a transition level while a boss is next to said transition level, it will let you select if you wish to fight it or not. Then you proceed into the level and move on.  You might think this is an issue with having multiple transition levels, but if one assembles the end of the board in a V/X formation with the boss somehow next to it in a normal game, this softlock is very well possible.

Suggestion:

The tutorial files are pretty good at going in depth for the most part, but as I said with moving the board pieces earlier, it's a little vague in certain areas. There should also be a tutorial for making new levels. I get it's probably relatively simple, but it's nice to have a tutorial on making new levels anyway, especially if there's certain common features people wish to add to their levels, like new enemies, minibosses, and cutscenes.

Thank you for the bug report and the suggestion!
Regarding the first bug, I'm not exactly sure how you're moving the node, can you provide a video that shows the issue, please?
Regarding the second bug, it's an interesting one, I didn't think of that possibility before, I will try to come up with a solution.
And regarding the suggestion, I didn't make a tutorial on how to make a new level for this exact reason (it's relatively simple) but now that I think about it, there are people with different amounts of Godot experience so it's probably good to have a tutorial that explains and suggests good practices on this topic. I will try to make it this week, and I will review other tutorials and try to make them less vague.
Thanks again!

Here's the footage of the two bugs in action.
https://www.youtube.com/watch?v=c_ypuNaAdIA
https://www.youtube.com/watch?v=y-BP7_c3Gss

Sorry for taking so long :D
I've replayed GMoM and I think this is how it should work, so it doesn't immediately send the character to the next planet but rather the player themselves should explicitly state that the character needs to go there
I will try to fix the tutorials right now.
https://github.com/user-attachments/assets/cc6c42e9-5ba7-4424-ba01-b5aa3e4bda87

I've made the "board peice" parts of the new board and new character tutorials more clear by specifying that board pieces are the character objects on the board. You can check out the changes in the "wip" branch of the repository :)

Great! Glad I could help.


Add nn.squareplus

Add the squareplus function, as described in Squareplus: A Softplus-Like Algebraic Rectifier, to jax.nn. It's a smooth rectifier like softplus, but without numerical stability issues and faster (1 algebraic function instead of 2 transcendental functions):
import timeit

import jax
from jax import numpy as jnp, nn, random

def squareplus(x, b=4):
    y = x + jnp.sqrt(jnp.square(x) + b)
    return jnp.ldexp(y, -1)  # fast division by 2

key = random.PRNGKey(0)
x = random.normal(key, [10**8])

jit_softplus = jax.jit(nn.softplus)
jit_squareplus = jax.jit(squareplus)

jit_softplus(x).block_until_ready()
jit_squareplus(x).block_until_ready()

start = timeit.default_timer()
jit_softplus(x).block_until_ready()
print(timeit.default_timer() - start)

start = timeit.default_timer()
jit_squareplus(x).block_until_ready()
print(timeit.default_timer() - start)

0.23485908400016342
0.0861067619998721

I can submit a PR.

Looks like we did this!

@jakevdp Out of curiosity, is there a reason why XLA doesn't have an ldexp primitive, or has it just not been requested/added yet? Seems like it could yield speed optimizations when users multiply/divide floats by a known power of 2.


Add functionality to retrieve resumable upload URL

Right now, the only way to get a resumable upload URL is to do the HTTP request "manually".
The problem with that, is that the storage does not expose the authClient which must be used to do the authenticated request to the storage.
So in our app, we first choose which client to use (whether we are in local development or in flex env), then create the authClient with either auth.clientViaServiceAccount or auth.clientViaMetadataServer and then do the request.
This seems very redundant, since all of this logic is already present in the gcloud/storage implementation, but isn't exposed (all of that functionality is private).
Adding a getResumableUploadUrl to Storage would be the easiest solution (and would benefit everybody who wanted to get such a Url), but if that is not wanted, it would be enough to expose the authClient (adding a auth.AuthClient get authClient => _authClient;) in the Storage class.
If you would be willing to accept such a change, I could propose a PR.

At least for package:appengine applications the auth client used for the storage api should be injected into the service scope (afaik) - it uses an oauth2 token with oauth2 scopes necessary for the storage API.
So you should be able to just use it via authClientService (from package:gcloud/http.dart).
Does this work?

Thank you! Will try and get back to you.

Closing as obsolete. Please open a new issue if this is still relevant.


help: Merge two similar sections in marking messages as read.

Previously, there was a two similar sections in marking messages as read. We want to move the intro paragraph from the second section to the first section. Then drop the "Do not mark as read" section altogether.
CZO discussion

Screenshots and screen captures:

Before:

After:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Hello @drrosa! This PR is ready for you to review, please have a look!

@Joelute Thanks! This is a good start.
The changes look good to me, except that the intro paragraph still needs to be modified in the context of the subheading Configure whether messages are automatically marked as read given it was originally written in the context of the Do not mark messages as read section.
Also, the titles for help center documentation PRs and commits should begin with help: instead of documentation:, and the PR/commit description shouldn't just rephrase what's already in the title. A better description would be something like:

Moves (modifying as needed) the intro paragraph from the second section into the first.
Drops the "Do not mark messages as read" section.

Ohhh I see, gotcha. Will make these changes!

Updated the PR! ready for another round of review :)

Updated the PR with the latest changes. Also updated the PR description and screenshots this time. :)

Great, thanks!
@alya This PR is ready for you.

Looks great to me! @timabbott this PR has been reviewed by @drrosa and me -- please take a look.

Looks great to me! @timabbott this PR has been reviewed by @drrosa and me -- please take a look.

@zulipbot add "integration review"


run example cpw

 Missing "Probe" point "X", "Y", or "Z" in configuration file!
... in function: void palace::config::ProbePostData::SetUp(palace::config::json&)
... in file: /tmp/hyb/spack-stage/spack-stage-palace-0.12.0-vdycxrh7g4aclofgm5xnpw5pj4mz4k7x/spack-src/palace/utils/configfile.cpp:575
how to revise this error?
-->

I found the reason is json file mismatch with palace 0.12.

Hi @huangyb2 I'm glad you managed to figure it out, the config files are still prone to some changes. We try to keep the changes to a minimum and to communicate them in the CHANGELOG.md file which should help.

I'm going to close this ticket as it seems you have resolved the issue, feel free to reopen if you have other questions.


Set env variable for some task packages (numba, cellpose)

When running the cellpose-segmentation task, and after fixing #310, it still fails with
$ cat 4_par_20200812-CardiomyocyteDifferentiation14-Cycle1_mip_zarr_B_03_0_.err
Matplotlib created a temporary config/cache directory at /tmp/matplotlib-mlqq0ii4 because the default path (/data/homes/fractal/.config/matplotlib) is not a writable directory; it is highly recommended to set the MPLCONFIGDIR environment variable to a writable directory, in particular to speed up the import of Matplotlib and to better support multiprocessing.
Traceback (most recent call last):
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/fractal_tasks_core/cellpose_segmentation.py", line 35, in <module>
    from cellpose import models
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/models.py", line 11, in <module>
    from . import transforms, dynamics, utils, plot
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/transforms.py", line 9, in <module>
    from . import dynamics, utils
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/dynamics.py", line 332, in <module>
    def map_coordinates(I, yc, xc, Y):
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/numba/core/decorators.py", line 212, in wrapper
    disp.enable_caching()
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/numba/core/dispatcher.py", line 863, in enable_caching
    self._cache = FunctionCache(self.py_func)
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/numba/core/caching.py", line 601, in __init__
    self._impl = self._impl_class(py_func)
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/numba/core/caching.py", line 337, in __init__
    raise RuntimeError("cannot cache function %r: no locator available "
RuntimeError: cannot cache function 'map_coordinates': no locator available for file '/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/dynamics.py'

Still in progress, but for sure related to numba caching of functions.
Possible reasons:

trying to write to a cache folder where the user does not have the right permissions,
not having the correct environment variables (e.g. NUMBA_CACHE_DIR) set,
other?

First attempt: I'm making all directories in the venv site-packages folder fully visible/writeable:
$ ls -l FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/ | grep cellpose
drwxrwxrwx  7 fractal fractal     4096 Nov 28 14:41 cellpose
drwxrwxrwx  2 fractal fractal     4096 Nov 28 14:41 cellpose-2.1.1.dist-info

(this is achieved with a recursive os.chmod(.., 0o777) as in https://stackoverflow.com/a/2853934/19085332)
This fixes the error, and leads to a new one:
Traceback (most recent call last):
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/fractal_tasks_core/cellpose_segmentation.py", line 489, in <module>
    run_fractal_task(
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/fractal_tasks_core/_utils.py", line 89, in run_fractal_task
    metadata_update = task_function(**task_args.dict())
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/fractal_tasks_core/cellpose_segmentation.py", line 335, in cellpose_segmentation
    model = models.CellposeModel(gpu=gpu, model_type=model_type)
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/models.py", line 369, in __init__
    self.net.load_model(self.pretrained_model[0], cpu=(not self.gpu))
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/resnet_torch.py", line 222, in load_model
    state_dict = torch.load(filename)
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/torch/serialization.py", line 699, in load
    with _open_file_like(f, 'rb') as opened_file:
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/torch/serialization.py", line 230, in _open_file_like
    return _open_file(name_or_buffer, mode)
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/torch/serialization.py", line 211, in __init__
    super(_open_file, self).__init__(open(name, mode))
PermissionError: [Errno 13] Permission denied: '/data/homes/fractal/.cellpose/models/nucleitorch_0'

Broader issue:
There exist some env variables for the task dependencies which are set to use paths which either belong to the fractal user or point (because they are not set) to a path which sits next to the python venv (then, again, in a fractal-owned directory).
Read access to these paths should be guaranteed, and also write access in some cases (e.g. numba caching). How would we proceed? Should we always export some user-specific env variables? How can we know which ones? Would switching back to sudo su - fix the issue?

By the way, note the permissions in
$ ls -l /data/homes/fractal/.cellpose/models/
total 25948
-rw------- 1 fractal fractal 26563614 Jul 28 07:23 nucleitorch_0
-rw------- 1 fractal fractal     3627 Jul 28 07:23 size_nucleitorch_0.npy

Question: does this information belong to WorkflowTask.meta?

Oh, good that we're discovering those issues.

Read access to these paths should be guaranteed, and also write access in some cases (e.g. numba caching). How would we proceed? Should we always export some user-specific env variables? How can we know which ones?

The more we can avoid having broad write access, the better. But at FMI, we now have a plan for a solution where there will be a (medium-sized) share that both the Fractal user and other users have read & write access to for logs & environments. So if there needs to be an env folder that users can write some things into, that is not perfect, but achievable.
If it would need to go to the home directory of the fractal user running the server: That likely won't be available on the FMI cluster (because we'll run the server from a separate VM that can submit to the cluster. But it has a local storage where it's home directory is and that won't be available on the nodes.

The more we can avoid having broad write access, the better.

I'm rather in favor of setting some env variables (which would go to some kind of WORKER_INIT) pointing to user-owned folders. Having all users writing their caches in some server folder doesn't look like the ideal solution.
The WORKER_INIT variable was there with the parsl backend, but it became unnecessary with the new slurm backend. We may have to reinstate it for the current issue.

Re-opening as a placeholder, until we check it in the fractal-demo examples

Now working with https://github.com/fractal-analytics-platform/fractal-demos/commit/a6ec6a8d86420febd2923f5b7a9744c4bcec1a1b. Closing.


Fortinet Fortigate Sourcetype Incorrect

Hi,
TA Fortigate updated sourcetypes in 1.6.3 from fgt_* to fortigate_* with no backwards compatibility.  To account for this the default sourcetype for fortigate logs should be updated in sc4s to fortigate_*
Reference:

https://splunkbase.splunk.com/app/2846/

Hi @rfaircloth-splunk
Since the default sourcetype has changed in the TA it only makes sense to match that in SC4S vs forcing people to manually override a deprecated sourcetype with the splunk_metadata.csv...
I believe saying "Please see our docs to address this issue" to every single person implanting SC4S with Fortigate logs is a poor answer.


📱💻 Make the App Fully Responsive for Mobile and Desktop

We need to improve the responsiveness of the app, ensuring it provides an optimal experience on both mobile and desktop screens. Currently, certain elements may not display correctly or may require too much scrolling. Your task is to update the app’s layout, ensuring it adapts fluidly to different screen sizes and devices.
Your Task:
Mobile Optimization: Make sure the app works smoothly on small screens (like smartphones). Focus on:
Adjusting layout elements, such as cards, images, and buttons.
Implementing mobile-friendly navigation (e.g., collapsible menus, touch-friendly elements).
Ensuring text is readable without zooming in or excessive scrolling.
Desktop Optimization: The app should look well-structured and professional on larger screens:
Adjust grid layouts, margins, and padding to use the extra screen space effectively.
Ensure that elements don’t look too stretched or compressed.
Consistency: Ensure the design remains consistent across all screen sizes. Avoid major differences between mobile and desktop except where necessary for usability.
Testing: Test the changes on various screen sizes (e.g., mobile, tablet, and desktop) using Chrome DevTools or a similar tool.
Suggested Approach:
Use CSS Flexbox or CSS Grid to make the layout responsive.
Consider implementing media queries to handle different screen sizes.
Optimize images and ensure they resize correctly without losing quality.
Use relative units like %, em, or rem rather than fixed pixel values.
Submission Guidelines:
Fork the repository.
Create a new branch (responsive-layout-improvements).
Update the CSS/JS/HTML files to make the layout responsive.
Open a pull request referencing this issue.
Let’s make this app look amazing on every device! 🌟

Can you please assign this to me?

go ahead @surajb0710

@Ctoic I see a lots of changes has been added for UI improvement, it wont be appropriate to push my changes, since it might introduce new issues. Hence, I unassigned myself from this ticket.

Sure still I can assign you some good first issues @surajb0710

Yes, but only front end please.


Brooke/firewallsettings

Description
Added a firewall policy that sets Threat Intelligence = Alert. Associated the firewall policy to the firewall.
Issue reference
The issue this PR will close: #119
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles or validates correctly
[x] BASH scripts have been validated using shellcheck
[x] All tests pass (manual and automated)
[x] The documentation is updated to cover any new or changed features
[x] Markdown files have been linted using the recommended linter. (See .vscode/extensions.json.)
[x] Relevant issues are linked to this PR

be sure to update the PR title to something descriptive, this is what makes it into the git log 👍


treewide: remove unused bindings

Motivation for this change
Big stress test of deadnix.
Rationale: per Nix convention we denote unused bindings with a leading underscore.  Doing this treewide and removing unused attrset arguments makes things cleaner.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Rebuild on linux is caused by a whitespace change

Closing to reduce maintenance burden.


Youtube Video Landscape on Android not work

Expected behaviour
I have a last version of Plyr and i have observed that landscape mode does not work on android.
Actual behaviour
When I'm in portrait mode the video disappears but the sound is still there. I think it's an iframe problem that must shift at the bottom of the screen. Only on Youtube videos.

Steps to reproduce
Go to landscape mode on any website with Plyr player.
Environment
Browser:  Chrome, Edge, Opera
Version:  Last Version
Operating System: Android
Version: 9
Console errors (if any)
None

+1 me too.

Hi @Thomasfds ,
I had the same error, updated today to v3.5.6 and I think it's fixed 👍 just in case you want to try.

This is still happening for me on v3.5.6

This is still happening for me on v3.5.6 unfortunately...
EDIT:
I was able to make it work by adding;
on.call(player, window, 'orientationchange', resized);
above (for example)
on.call(player, elements.container, 'enterfullscreen exitfullscreen', function (event) {

Can you elaborate on what your 'resized' function does to fix the problem on enterfullscreen and exitfullscreen?
Thanks

@EricSSartorius
It's not a function I added or wrote.
You can find the function here.
What I'm essentially doing, is catching a reorientation event and then call the resized function. This function ends up recalculating and setting the video width and height. Without doing this, there appears to be an issue with these dimensions not changing (e.g. remaining in portrait mode) when the video changes from portrait to landscape.

Ah gotcha. That makes sense, thank you. Is this something that will be added as a PR soon?

Got the same problem, everything works fine when using  a mp4 video file, but when using a video from youtube the videos is missalinged

Code I'm using:
  componentDidMount(){     this.player = new Plyr('#player');     this.player.on('enterfullscreen', event => window.screen.orientation.lock('landscape'));     this.player.on('exitfullscreen', event => window.screen.orientation.lock('portrait'));   }
Tried adding     this.player.on.call(this.player, window, 'orientationchange', resized); but React is unhappy with resized not being defined. Any way to fix this

Is there any fix for this? None of the above seem to work.


LuaJIT support, designed to support versions of openresty from 1.15+

Supports stripped versions of LuaJIT which is common and supports amd64
and arm64.  LuaJIT compressed 32 bit pointer mode is not supported.
Offsets are pulled from native code analysis using Go's builtin
x86asm and arm64asm packages. Zydis wasn't needed as the offsets are
mostly extracted from from the beginning of functions so none of x86asm
limitations were hit. Docker is used to extensively test the offset
extraction and do some simple integration testing (sudo required).
Assumptions are baked into the Go code and to a minimal extent the
unwinder code about the layout of LuaJIT structs, the codebase is old
and stable so making things fully generic was not necessary.
The unwinder supports interpreted and JIT'd execution, the fidelity of
JIT'd profiles is somewhat limited as the bytecode "PC" is not tracked
in JIT execution.  However the call stack is maintained so even though
a JIT'd LuaJIT trace can wind through any number of functions a full
stack trace can be constructed.
Tested on openresty docker images from 1.15 through 1.25 (latest).
Most of the changes are in line with other native unwinders with a
couple exceptions:

The LoaderInfo is now given access to the stack deltas.  This allows
the stack deltas to be consulted to determine the bounds of the
LuaJIT interpreter "function" (see comments for
extractInterpreterBounds).

The way the JIT traces are mapped is a little odd. First we establish
the entire anonyous/executable section with a pid mapping and then
as we learn about and walk the GCtrace objects we fill in specific
information about how to walk over each JIT trace. The stack adjustments
are specific to each trace and we store the LuaJIT global G pointer
in the pid mapping table to save the unwinder from having to remember
context and rely on best effort techniques to find it.  This should
have the advantage of making the unwinder work in untested contexts like
multi-threaded openresty or applications where multiple LuaJIT instances
are used fom the same process/threads.

Curious what others think about the dependency explosion from testcontainers.  I'm thinking we could switch the integration tests to otel corefile machinery and use command line docker for the offset testing purposes and get rid of it.  I'll explore those options.