kafka-connect from mysql to hbase

Hi is there any idea on how to ingest data from mysql to hbase through confluent ,If so could shed light on it @ewencp @wushujames

@sunnn You probably just need to tie a couple of connectors together. For MySQL -> Kafka you could use Confluent's JDBC connector which uses the standard JDBC interface to support a variety of relational databases or Debezium's CDC connector which can read directly from the MySQL binlog. For Kafka -> HBase, you could use this HBase sink connector listed on the Connector Hub.

Yeah i have tried doing it the problem arises when i start the kafka agent then i get the following error
[2016-08-25 03:59:00,223] INFO Created connector kafka-cdc-hbase (org.apache.kaf                            ka.connect.cli.ConnectStandalone:82)
[2016-08-25 03:59:00,225] ERROR Thread WorkerSinkTask-kafka-cdc-hbase-0 exiting                             with uncaught exception:  (org.apache.kafka.connect.util.ShutdownableThread:84)
java.lang.NoSuchMethodError: org.apache.kafka.clients.consumer.KafkaConsumer.sub                            scribe(Ljava/util/List;Lorg/apache/kafka/clients/consumer/ConsumerRebalanceListe                            ner;)V
at org.apache.kafka.connect.runtime.WorkerSinkTask.joinConsumerGroupAndS                            tart(WorkerSinkTask.java:143)
at org.apache.kafka.connect.runtime.WorkerSinkTaskThread.execute(WorkerS                            inkTaskThread.java:54)
at org.apache.kafka.connect.util.ShutdownableThread.run(ShutdownableThre                            ad.java:82)
Exception in thread "WorkerSinkTask-kafka-cdc-hbase-0" java.lang.NoSuchMethodErr                            or: org.apache.kafka.clients.consumer.KafkaConsumer.subscribe(Ljava/util/List;Lo                            rg/apache/kafka/clients/consumer/ConsumerRebalanceListener;)V
at org.apache.kafka.connect.runtime.WorkerSinkTask.joinConsumerGroupAndS                            tart(WorkerSinkTask.java:143)
at org.apache.kafka.connect.runtime.WorkerSinkTaskThread.execute(WorkerS                            inkTaskThread.java:54)
at org.apache.kafka.connect.util.ShutdownableThread.run(ShutdownableThre                            ad.java:82)
[2016-08-25 03:59:00,230] INFO Source task Thread[WorkerSourceTask-kafka-mysql-j                            dbc-0,5,main] finished initialization and start (org.apache.kafka.connect.runtim                            e.WorkerSourceTask:342)
[2016-08-25 03:59:01,474] WARN Error while fetching metadata with correlation id                             0 : {test_jdbc_users=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkCli                            ent:600)
could you help me out in this issue @ewencp

It seems like there could be multiple issues at play here.
The first is the one with java.lang.NoSuchMethodError: org.apache.kafka.clients.consumer.KafkaConsumer.subscribe(Ljava/util/List;Lorg/apache/kafka/clients/consumer/ConsumerRebalanceListener;) message. This looks like you might have mismatched versions of Connect and Kafka libraries -- because of some concerns around using specific types of collections instead of generic Collection types, Kafka made a backwards-incompatible change in the consumer APIs to address this. But normally I wouldn't expect to see this issue in connect since usually users will just install a single Kafka bundle including everything (either from Apache or Confluent) and execute everything with matching versions. How did you install everything, and was there anything non-standard about your process?
The LEADER_NOT_AVAILABLE message looks like a topic might not exist. But in this case, I'm guessing you are seeing that message simply because of topic auto-creation -- if you are relying on the topic being auto-created by the connector when it produces data, then this message would be expected.

I have used the vagrant machine provided for the example http://www.confluent.io/blog/how-to-build-a-scalable-etl-pipeline-with-kafka-connect and installed hbase over it the same way hive was being done i the machine and started kafka but the here confluent i used was cp3.0.0 and hbase connector i feel may be from cp2.0.0 from the above link u have provided

@sunnn Yes, simply because of the timing, that repository uses a CP 2.0 version. I have not tested this, but you can probably just substitute the 2.0 version for 3.0 version in the vagrant/deb.sh script to get a more up-to-date version of CP to test with in that VM.

the hbase link you have given was that for cp2.0 or 3.0 version could you specify

@sunnn Great question! It is a third party connector (connectors are federated, so anyone can develop them), but it looks like it might currently be targeted at CP 2.0/Kafka 0.9.0. The changes required for newer versions of Kafka/CP are very minimal, so it's likely a small PR/request to the developers might get it updated for the most recent version. (They may even be up to date and just forgotten to update their README -- I'd suggest posting over on their repository to find out.)


Interstellar, 0.90 and TreeLoader

From the previous issue that was closed:
"Interstellar has been taken up by a new modder to keep it functional on new versions; it can be found at http://forum.kerbalspaceprogram.com/threads/104943-0-90-KSP-Interstellar-port-maintance-thread . I don't know any details on what would be needed (CKAN is the third mod manager for KSP I'm trying out, and I'm not entirely sure how ti works yet) but this might let you get a functional 0.90 version listed on there?"
In addition, this IS showing up for 0.90 installations and IS causing problems.  Please take a look and either remove KSP Interstellar entirely from the tree (there's a replacement that provides a slightly older version) OR please update it - it does NOT use TreeLoader anymore:
https://github.com/FractalUK/KSPInterstellar/wiki/Illustrated-Guide-Chapter-0:-Installing-and-Patching

I assume the previous topic you refer to is https://github.com/KSP-CKAN/CKAN-meta/issues/318 ?
Is this also a thing for KSPInterstellar lite or is that a totally different fork of the mod?

Problem should now be resolved as the PR has been merged.


Progress indicators for TIS analysis

#882 introduced adapters for progress indicators (namely, tqdm). This PR integrates that into the "new" TIS analysis. (The "new" analysis, which is about 2 years old, is described in this document and this example notebook. It isn't the default yet because it isn't compatible with files created by very old version of OPS -- I think pre 0.9.3 -- which we use for our tests.)
If you have tqdm installed, you'll automatically get progress bars. You can also customize the behavior, including easily silencing the progress bars.
The goal of this PR is to get these fully working for the StandardTISAnalysis, along with conveniences for changing some behavior.

This is ready for review/merge. I will leave it up for at least 24 hours, merging no earlier than Sunday night, 9 February.


Error differentiating through the solver

Hello! First of all, thank you to the software writer for making this package. There are many examples with lovely pictures.
The documentation site says the package supports differentiating through the solver, but the examples directory doesn't show how to do that.
I tried a very simple test with the Actuator2D example, but it errors just when solving the forward problem, before even starting the backwards gradient calculation.

slightly modified Actuator2D.jl
# # Unsteady actuator case - 2D
#
# In this example, an unsteady inlet velocity profile at encounters a wind
# turbine blade in a wall-less domain. The blade is modeled as a uniform body
# force on a thin rectangle.

using CairoMakie
using IncompressibleNavierStokes

# Output directory
outdir = joinpath(@__DIR__, "output", "Actuator2D")
ispath(outdir) || mkpath(outdir)

# A 2D grid is a Cartesian product of two vectors
n = 40
x = LinRange(0.0, 10.0, 5n + 1)
y = LinRange(-2.0, 2.0, 2n + 1)
fig = plotgrid(x, y; figure = (; size = (600, 300)))
display(fig)

# Boundary conditions
boundary_conditions = (
    ## x left, x right
    (
        ## Unsteady BC requires time derivatives
        DirichletBC(
            (dim, x, y, t) -> sin(π / 6 * sin(π / 6 * t) + π / 2 * (dim() == 1)),
            (dim, x, y, t) ->
                (π / 6)^2 *
                cos(π / 6 * t) *
                cos(π / 6 * sin(π / 6 * t) + π / 2 * (dim() == 1)),
        ),
        PressureBC(),
    ),

    ## y rear, y front
    (PressureBC(), PressureBC()),
)

# Actuator body force: A thrust coefficient `Cₜ` distributed over a thin rectangle
xc, yc = 2.0, 0.0 # Disk center
D = 1.0           # Disk diameter
δ = 0.11          # Disk thickness
Cₜ = 0.2          # Thrust coefficient
cₜ = Cₜ / (D * δ)
inside(x, y) = abs(x - xc) ≤ δ / 2 && abs(y - yc) ≤ D / 2
bodyforce(dim, x, y, t) = dim() == 1 ? -cₜ * inside(x, y) : 0.0

# Build setup and assemble operators
setup = Setup(x, y; Re = 100.0, boundary_conditions, bodyforce);

# Initial conditions (extend inflow)
ustart = create_initial_conditions(setup, (dim, x, y) -> dim() == 1 ? 1.0 : 0.0);

# Solve unsteady problem
function get_state(ustart)
    state, outputs = solve_unsteady(;
        setup,
        ustart,
        tlims = (0.0, 12.0),
        method = RKMethods.RK44P2(),
        Δt = 0.05,
        processors = (
            # rtp = realtimeplotter(; setup, size = (600, 300), nupdate = 5),
            # log = timelogger(; nupdate = 24),
        ),
    )
    return state
end

state = get_state(ustart)

# ## Post-process
#
# We may visualize or export the computed fields

# Export to VTK
save_vtk(state; setup, filename = joinpath(outdir, "solution"))

# We create a box to visualize the actuator.
box = (
    [xc - δ / 2, xc - δ / 2, xc + δ / 2, xc + δ / 2, xc - δ / 2],
    [yc + D / 2, yc - D / 2, yc - D / 2, yc + D / 2, yc + D / 2],
)

# Plot pressure
fig = fieldplot(state; setup, size = (600, 300), fieldname = :pressure)
lines!(box...; color = :red)
display(fig)

# Plot velocity
fig = fieldplot(state; setup, size = (600, 300), fieldname = :velocitynorm)
lines!(box...; color = :red)
display(fig)

# Plot vorticity
fig = fieldplot(state; setup, size = (600, 300), fieldname = :vorticity)
lines!(box...; color = :red)
display(fig)

# Get gradient
using Zygote
state, adjoint_action = Zygote.pullback(get_state, ustart);

Output, with error message
julia> include("examples/Actuator2D.jl")
┌ Warning: Creating new pressure solver for observefield
└ @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/processors.jl:91
ERROR: LoadError: Compiling Tuple{SparseArrays.UMFPACK.var"##umfpack_numeric!#21", Bool, Nothing, typeof(SparseArrays.UMFPACK.umfpack_numeric!), SparseArrays.UMFPACK.UmfpackLU{Float64, Int64}}: ArgumentError: array must be non-empty
Stacktrace:
  [1] macro expansion
    @ ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0 [inlined]
  [2] _pullback(::Zygote.Context{…}, ::SparseArrays.UMFPACK.var"##umfpack_numeric!#21", ::Bool, ::Nothing, ::typeof(SparseArrays.UMFPACK.umfpack_numeric!), ::SparseArrays.UMFPACK.UmfpackLU{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:87
  [3] umfpack_numeric!
    @ /my_data/.julia/juliaup/julia-1.11.0-rc3+0.x64.linux.gnu/share/julia/stdlib/v1.11/SparseArrays/src/solvers/umfpack.jl:629 [inlined]
  [4] _pullback(::Zygote.Context{…}, ::typeof(Core.kwcall), ::@NamedTuple{…}, ::typeof(SparseArrays.UMFPACK.umfpack_numeric!), ::SparseArrays.UMFPACK.UmfpackLU{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
  [5] #lu#7
    @ /my_data/.julia/juliaup/julia-1.11.0-rc3+0.x64.linux.gnu/share/julia/stdlib/v1.11/SparseArrays/src/solvers/umfpack.jl:388 [inlined]
  [6] _pullback(::Zygote.Context{…}, ::SparseArrays.UMFPACK.var"##lu#7", ::Bool, ::Nothing, ::Vector{…}, ::typeof(LinearAlgebra.lu), ::SparseArrays.SparseMatrixCSC{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
  [7] lu
    @ /my_data/.julia/juliaup/julia-1.11.0-rc3+0.x64.linux.gnu/share/julia/stdlib/v1.11/SparseArrays/src/solvers/umfpack.jl:384 [inlined]
  [8] _pullback(ctx::Zygote.Context{false}, f::typeof(LinearAlgebra.lu), args::SparseArrays.SparseMatrixCSC{Float64, Int64})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
  [9] factorize
    @ /my_data/.julia/juliaup/julia-1.11.0-rc3+0.x64.linux.gnu/share/julia/stdlib/v1.11/SparseArrays/src/linalg.jl:1976 [inlined]
 [10] _pullback(ctx::Zygote.Context{…}, f::typeof(LinearAlgebra.factorize), args::SparseArrays.SparseMatrixCSC{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
 [11] psolver_direct
    @ ~/a/navierstokes/IncompressibleNavierStokes.jl/src/pressure.jl:137 [inlined]
 [12] _pullback(::Zygote.Context{…}, ::typeof(psolver_direct), ::Vector{…}, ::@NamedTuple{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
 [13] psolver_direct
    @ ~/a/navierstokes/IncompressibleNavierStokes.jl/src/pressure.jl:121 [inlined]
 [14] default_psolver
    @ ~/a/navierstokes/IncompressibleNavierStokes.jl/src/pressure.jl:116 [inlined]
 [15] _pullback(ctx::Zygote.Context{…}, f::typeof(default_psolver), args::@NamedTuple{…})
     Use `show(err)` to see complete types.

Version info:

Julia 1.11
IncompressibleNavierStokes.jl latest main commit (a180524aa89aab43c7be2aef4f22c72a63b5188b)
Zygote  v0.6.70
CairoMakie v0.12.9

Hi, thanks for the feedback.
Differentiating with Zygote requires all operations to be allocating and non-modifying, this can be achieved by using the out-of-place versions of the operators. The function solve_unsteady uses the in-place version, but you can make a differentiable time-stepping loop as follow (replace your get_state with this version):
# Do timestepping manually with out-of-place stepper
# (use `timestep` instead of `timestep!` to avoid modifying the input)
INS = IncompressibleNavierStokes
psolver = default_psolver(setup)
function get_state(ustart)
    t_end = 12.0
    Δt = 0.05
    method = RKMethods.RK44P2()
    nstep = round(Int, t_end / Δt)
    stepper =
        INS.create_stepper(method; setup, psolver, u = ustart, temp = nothing, t = 0.0)
    for it = 1:nstep
        stepper = INS.timestep(method, stepper, Δt)
    end
    return INS.get_state(stepper)
end

Let me know if this works!

Thank you. With that change, the forward solve works. The downsides are it is much slower and perhaps has a memory leak somewhere, although that could be a Zygote issue. (Calling it twice doubled the memory usage and was unaffected by GC.gc())
Now the pullback for DirichletBC seems to not be implemented yet.
Since I don't have a particular problem setup in mind yet, I'll quit working on this for now (and I'll assume the PeriodicBC one works). I appreciate your help!

Actuator2D.jl
# # Unsteady actuator case - 2D
#
# In this example, an unsteady inlet velocity profile at encounters a wind
# turbine blade in a wall-less domain. The blade is modeled as a uniform body
# force on a thin rectangle.

using CairoMakie
using IncompressibleNavierStokes

# Output directory
outdir = joinpath(@__DIR__, "output", "Actuator2D")
ispath(outdir) || mkpath(outdir)

# A 2D grid is a Cartesian product of two vectors
n = 40
x = LinRange(0.0, 10.0, 5n + 1)
y = LinRange(-2.0, 2.0, 2n + 1)

# Boundary conditions
boundary_conditions = (
    ## x left, x right
    (
        ## Unsteady BC requires time derivatives
        DirichletBC(
            (dim, x, y, t) -> sin(π / 6 * sin(π / 6 * t) + π / 2 * (dim() == 1)),
            (dim, x, y, t) ->
                (π / 6)^2 *
                cos(π / 6 * t) *
                cos(π / 6 * sin(π / 6 * t) + π / 2 * (dim() == 1)),
        ),
        PressureBC(),
    ),

    ## y rear, y front
    (PressureBC(), PressureBC()),
)

# Actuator body force: A thrust coefficient `Cₜ` distributed over a thin rectangle
xc, yc = 2.0, 0.0 # Disk center
D = 1.0           # Disk diameter
δ = 0.11          # Disk thickness
Cₜ = 0.2          # Thrust coefficient
cₜ = Cₜ / (D * δ)
inside(x, y) = abs(x - xc) ≤ δ / 2 && abs(y - yc) ≤ D / 2
bodyforce(dim, x, y, t) = dim() == 1 ? -cₜ * inside(x, y) : 0.0

# Build setup and assemble operators
setup = Setup(x, y; Re = 100.0, boundary_conditions, bodyforce);

# Initial conditions (extend inflow)
ustart = create_initial_conditions(setup, (dim, x, y) -> dim() == 1 ? 1.0 : 0.0);

# Solve unsteady problem
INS = IncompressibleNavierStokes
psolver = default_psolver(setup)
function get_state(ustart)
    t_end = 12.0
    Δt = 0.05
    method = RKMethods.RK44P2()
    nstep = round(Int, t_end / Δt)
    stepper =
        INS.create_stepper(method; setup, psolver, u = ustart, temp = nothing, t = 0.0)
    for it = 1:nstep
        stepper = INS.timestep(method, stepper, Δt)
    end
    return INS.get_state(stepper)
end
# @time state = get_state(ustart)
# @time state = get_state(ustart)
#  7.038594 seconds (4.56 M allocations: 4.221 GiB, 10.04% gc time, 37.87% compilation time)
#  3.871654 seconds (644.46 k allocations: 4.025 GiB, 5.98% gc time)

# Get gradient
using Zygote
# @time state, adjoint_action = Zygote.pullback(get_state, ustart);
# @time state, adjoint_action = Zygote.pullback(get_state, ustart);
#  32.891385 seconds (41.20 M allocations: 5.919 GiB, 6.28% gc time, 78.29% compilation time)
#  25.251067 seconds (1.15 M allocations: 4.080 GiB, 11.74% gc time)

@time state, adjoint_action = Zygote.pullback(get_state, ustart);

d_ustart = adjoint_action(state)

Output with error
ulia> include("examples/Actuator2D.jl")
 35.876284 seconds (44.16 M allocations: 6.068 GiB, 6.69% gc time, 79.78% compilation time)
ERROR: LoadError: MethodError: no method matching apply_bc_u_pullback!(::DirichletBC{…}, ::Tuple{…}, ::Int64, ::Float64, ::@NamedTuple{…}; isright::Bool)
The function `apply_bc_u_pullback!` exists, but no method is defined for this combination of argument types.

Closest candidates are:
  apply_bc_u_pullback!(::PeriodicBC, ::Any, ::Any, ::Any, ::Any; isright, kwargs...)
   @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/boundary_conditions.jl:292
  apply_bc_u_pullback!(::Any, ::Any, ::Any; kwargs...)
   @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/boundary_conditions.jl:163

Stacktrace:
  [1] apply_bc_u_pullback!(φbar::Tuple{…}, t::Float64, setup::@NamedTuple{…}; kwargs::@Kwargs{})
    @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/boundary_conditions.jl:168
  [2] apply_bc_u_pullback!(φbar::Tuple{…}, t::Float64, setup::@NamedTuple{…})
    @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/boundary_conditions.jl:163
  [3] (::IncompressibleNavierStokes.var"#5#6"{…})(φbar::ChainRulesCore.Tangent{…})
    @ IncompressibleNavierStokes ~/a/navierstokes/IncompressibleNavierStokes.jl/src/boundary_conditions.jl:109
  [4] (::Zygote.ZBack{IncompressibleNavierStokes.var"#5#6"{…}})(dy::Tuple{Matrix{…}, Matrix{…}})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/chainrules.jl:211
  [5] #timestep#358
    @ ~/a/navierstokes/IncompressibleNavierStokes.jl/src/time_steppers/step_explicit_runge_kutta.jl:123 [inlined]
  [6] (::Zygote.Pullback{…})(Δ::@NamedTuple{…})
    @ Zygote ~/.julia/packages/Zygote/nsBv0/src/compiler/interface2.jl:0
  [7] timestep
    @ ~/a/navierstokes/IncompressibleNavierStokes.jl/src/time_steppers/step_explicit_runge_kutta.jl:66 [inlined]
  [8] (::Zygote.Pullback{…})(Δ::@NamedTuple{…})
     Use `show(err)` to see complete types.

I added the missing chain rules, so now d_ustart = adjoint_action(state) in your example should give gradients on the latest main branch.
An exlanation can be found here.


Version 2.0 prerelease available

I published the docs for the 2.0 prerelease to https://base-apps.github.io/angular-base-apps.    Give it a try and post any issues you find.
@tolyo @mattgrande @gakimball @AntJanus @Seb-

Great job. My notes:
I don't like the fact that the currently released version does not have a doc online anymore. It would be nice to be able to host multiple versions of the doc at the same time. At least the current release and the one from master, and ideally every version for people who do not wish to upgrade immediately. I know it's possible do have them locally but the users don't want to and shouldn't be expected to do that.
I would consider a separate menu for the migration guide from 1.2 to 2. This is pretty big and shouldn't be missed. That page should be linked at several places, including where it is currently (Installation) but also on the Changelog page I believe.
It would be pretty neat to provide a tool (probably best to be run with node) to help with the migration. Except the "foundation → base" most of other strings are easy to search and replace. I'm not thinking entirely automated tool, but probably one listing all the found occurrences and allowing the user to discard some and accept the rest, or to accept some and discard the rest, either by file, folder or individual occurrences. I know some commands or tools inside GUI editors can already do more or less all of that, but again best to expect the least from the users.
The CHANGELOG.md file has not been updated accordingly.
I have read somewhere there was a test made and a message shown if the current browser was not supported. This is excellent. It would be nice to include on the Compatibility page how to enable or disable this feature.
https://base-apps.github.io/angular-base-apps/#!/grid
"The Grid in Action" > "View Templates" button leads to the homepage. Should be fixed to lead to the correct place or be removed (preferably fixed).
Links on Action Sheet, Menu Bar, Title Bar, Block List, Utility Classes still have the href="#" and lead to the Homepage. Same for the Search buttons on the Forms page (no href but same issue).
This is not a doc issue but while I'm at it, I just noticed that the dark button doesn't change color on :hover or :focus unlike the others. And for some others (especially primary), the difference between the 2 states are really hard to notice. To be fair only the difference for the secondary is clear enough for my taste.
Meter & Progress Elements should not be on the Form page at all, but on a separate page. Do meters still not support IE? Is it possible to make them support it? Is it a good idea to have individual elements not respecting what is announced on the Compatibility table? Probably not.
https://base-apps.github.io/angular-base-apps/#!/accordion
"External Triggers"
If 1 and 2 are closed, Toggle 3 button is annoying, because it moves place, which is really bad for a toggle button.
https://base-apps.github.io/angular-base-apps/#!/card
Card missing the secondary and info examples.
https://base-apps.github.io/angular-base-apps/#!/labels-badges
When the labels are going over 2 lines (ore more) they touch each other, it would be nice to have a vertical spacing between them (using a p as the container would probably do, maybe changing line-height). Same for badges on small screens.
https://base-apps.github.io/angular-base-apps/#!/icon
Worth considering adding Foundation Icon Fonts 3?

@Seb- Thanks for the amazing feedback!  I fixed most of the issues with the docs and created other issues to track your other suggestions.  Here are my responses to the other (unchecked) suggestions:
Migration Tool
This is a great idea but I won't really have the time to create it.  You're welcome to create a new issue for this and hopefully someone from the community will pick it up.
Hover Styling
The SCSS code used to style the :hover and :focus states is shown below:
&:hover, &:focus {
  border-color: scale-color($background, $lightness: 25%);
  background: transparent;
  color: scale-color($background, $lightness: 25%);
}

The 25% could be converted into a variable to allow changing the styling.  Feel free to submit a PR or an issue for that feature.
Meter & Progress
I'm not all that sure about IE support.  You're probably right it should be moved.  Feel free to submit a PR with those changes.
Foundation Icon Fonts 3
This would have to first be supported by angular-icons and then styling can be added to angular base apps.

I want to finalize the 2.0 release this week and get it published by the end of the weekend.  Let me know if anyone has feedback on the prerelease.
The last thing on the v2.0 milestone is to finalize the template, though that doesn't really need to be completed before v2.0 is published.

Version 2 has been released


bashew cannot handle path to script

Sorry Peter, another one :)
 $  bashew -v script
# 📜 Script path: /home/mcrowe/.basher/cellar/bin/bashew - folder /home/mcrowe/.basher/cellar/bin
# 🔗 Linked to: /home/mcrowe/.basher/cellar/packages/pforret/bashew/bashew - folder /home/mcrowe/.basher/cellar/packages/pforret/bashew
# 🔗 Linked to: /home/mcrowe/.basher/cellar/packages/pforret/bashew/bashew.sh - folder /home/mcrowe/.basher/cellar/packages/pforret/bashew
# Executing : [/home/mcrowe/.basher/cellar/packages/pforret/bashew/bashew.sh]
# In folder : [/home/mcrowe/.basher/cellar/packages/pforret/bashew]
# Detected shell: bash - version 5.0.17(1)-release
# System    : Distributor ID:   Ubuntu (Linux) Release: 20.10 on x86_64
# Installer : apt install
# Expect : 1 single parameter(s): action
# Found  : action=script
# No multi param to process
# all parameters have been processed
# Cleanup: [.tmp] - delete files older than 1 day(s)
# Tmpfile: .tmp/2020-12-29.qo0ejz
# Cleanup: [log] - delete files older than 7 day(s)
# Logfile: log/bashew.2020-12-29.log
# Program: bashew 1.10.2
# Updated: 2020-12-28 07:59
# Run as : mcrowe@mcrowe-Inspiron-7537
# Running: on Linux (#33-Ubuntu SMP Mon Nov 23 18:44:54 UTC 2020)
# Verify : git tput uname
# Using [scotia_screws.sh] as name
…  1. first we need the information of the author
Author full name         (Mike Crowe):
Author email             (drmikecrowe@gmail.com):
Author (github) username (.): drmikecrowe
…  2. now we need the path and name of this new script/repo
Script name (./scotia_screws.sh): /home/mcrowe/bin/media
…  3. give some description of what the script should do
Script description (This is my script media): Start/Stop media processes
…  Creating script /home/mcrowe/bin/media ...
sed: -e expression #1, char 29: unknown option to `s'
/home/mcrowe/bin/media
# bashew finished after 43 seconds

For reference:
 $  sed --version --help
sed (GNU sed) 4.7

 $  sed --help
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
      --debug
                 annotate program execution
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if SUFFIX supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l' command
  --posix
                 disable all GNU extensions.
  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).
  -s, --separate
                 consider files as separate rather than as a single,
                 continuous long stream.
      --sandbox
                 operate in sandbox mode (disable e/r/w commands).
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
  -z, --null-data
                 separate lines by NUL characters
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.
E-mail bug reports to<EMAIL_ADDRESS>

Ah yes, it's the "/" in your Script description . I have to escape that!

Should be fixed in v 1.10.3! I replaced the sed chain by one awk and it accepts all characters, even: / | ' "


feat: Yandex Cloud terraform provider support

Is your feature request related to a problem? Please describe.

We want to scan our IaC, however there is no support for Yandex Cloud terraform provider . For now, tfsec shows zero problems.
Describe the solution you'd like

It would be great if tfsec will support Yandex Cloud terraform provider
Describe alternatives you've considered

Additional context

this is still a feature report =)

At the moment we don't have plans to add this. Please feel free to open an issue in the Trivy repo if you see fit.


Type scale generator is unable to authenticate with webfonts

Only Roboto is currently selectable in the type scale generator section of the docs.
On inspection, it looks like the page is returning a 403 when trying to fetch a list of fonts

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Type scale generator only lists "Roboto" in the right hand selectors
Expected Behavior 🤔
Type scale generator should allow any Google Fonts font to be selected.
Steps to Reproduce 🕹
Steps:

Visit https://material.io/design/typography/the-type-system.html#type-scale
Attempt to select any font other than Roboto

Context 🔦
I'm trying to better understand type spacing and scaling.
Your Environment 🌎

Tech
Version

Material-UI
latest

Browser
Chrome 83.0.4103.61

Wrong repository

Sorry 🤦


Can't set nav-active-item-marker="colored-block" as default

See demo https://jsfiddle.net/2mbakuh0/4/
Can't set it by default as an option in the HTML, only by clicking the button (probably after the page has loaded).

Currently it works only if I set it in before-render:
<script>
    const rapidocEl = document.getElementById('thedoc');
        rapidocEl.addEventListener('before-render', (e) => {
          document.getElementById('thedoc').setAttribute('nav-active-item-marker', 'colored-block')
        });
</script>

refer to this example
The reason it do not show up immediately because  the nav only highlights the focused item on the navbar, therefore after you change the  nav-active-item-marker click on one of the nav-item to get the focus and see the effect

@mrin9 I just encountered the same issue, I think this is a duplicate of #900
If you declare nav-active-item-marker="colored-block" in the HTML, it seems like even when you click on a nav-item, it will still use the left-bar styling.
Currently the workaround is to use setAttribute() as shown (and then click on a nav-item).


An unhandled exception has occurred while executing the request (Example 1 C#)

Example 1 (C#) gives an error:
  An unhandled exception has occurred while executing the request.
      Status Code: NotAcceptable
      Microsoft.Graph.ServiceException: Code: UnknownError

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4b836740-9263-12cc-9001-c61f08448f0d
Version Independent ID: 4a5b79f8-d685-6c86-d7ed-12d7c5d309cb
Content: List places - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/place-list.md
Product: outlook
Technology: microsoft-graph
GitHub Login: @vrod9429
Microsoft Alias: MSGraphDocsVteam

@lipalath-ms Any chance you can confirm this is still an issue on the latest version of the SDK with the updates snippets?


cloud-sql-proxy: 1.30.0 -> 1.31.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cloud-sql-proxy/versions.
meta.description for cloud-sql-proxy is: "An authenticating proxy for Second Generation Google Cloud SQL databases"
meta.homepage for cloud-sql-proxy is: "https://github.com/GoogleCloudPlatform/cloudsql-proxy"
meta.changelog for cloud-sql-proxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.30.1 with grep in /nix/store/jrs4hg6x3vi9raslnqhzw7sjldkxpmmh-cloud-sql-proxy-1.30.1
found 1.30.1 in filename of file in /nix/store/jrs4hg6x3vi9raslnqhzw7sjldkxpmmh-cloud-sql-proxy-1.30.1

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
cloud-sql-proxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jrs4hg6x3vi9raslnqhzw7sjldkxpmmh-cloud-sql-proxy-1.30.1 \
  --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 cloud-sql-proxy https://github.com/r-ryantm/nixpkgs/archive/b2e8f25aaeaeaa68fbaa9ba5a9ccf8ac30aced17.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jrs4hg6x3vi9raslnqhzw7sjldkxpmmh-cloud-sql-proxy-1.30.1
ls -la /nix/store/jrs4hg6x3vi9raslnqhzw7sjldkxpmmh-cloud-sql-proxy-1.30.1/bin

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

1 package built:

cloud-sql-proxy

Maintainer pings
cc @nicknovitski @kalbasit for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cloud-sql-proxy/versions.
meta.description for cloud-sql-proxy is: "An authenticating proxy for Second Generation Google Cloud SQL databases"
meta.homepage for cloud-sql-proxy is: "https://github.com/GoogleCloudPlatform/cloudsql-proxy"
meta.changelog for cloud-sql-proxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.31.2 with grep in /nix/store/f3hzz6iidxylkbdqnmklf57xfq655saf-cloud-sql-proxy-1.31.2
found 1.31.2 in filename of file in /nix/store/f3hzz6iidxylkbdqnmklf57xfq655saf-cloud-sql-proxy-1.31.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cloud-sql-proxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f3hzz6iidxylkbdqnmklf57xfq655saf-cloud-sql-proxy-1.31.2 \
  --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 cloud-sql-proxy https://github.com/r-ryantm/nixpkgs/archive/a5fc2ede43716c792879dc7a320c904b7b81b825.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f3hzz6iidxylkbdqnmklf57xfq655saf-cloud-sql-proxy-1.31.2
ls -la /nix/store/f3hzz6iidxylkbdqnmklf57xfq655saf-cloud-sql-proxy-1.31.2/bin

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

1 package built:

cloud-sql-proxy

Maintainer pings
cc @nicknovitski for testing.

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

1 package built:

cloud-sql-proxy


Update release history from 2021 to 2023

Description
Update release history from 2021 to 2023
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Thanks @nateynateynate 👍


fix(validator): make isOptional rule works correctly

Great! I was actually going to write an issue about this, I appreciate this change 👍


cloudmap: resolve hostnames before registering

AWS load balancers are DNS-based rather than IP-based.
This means that we need to resolve those host names before registering endpoints to the
service registry, as they only accept IPs.
This commit introduces this change and allows the operator to work fine with EKS as well.
When registering services that have a host name (or multiple ones), the operator will register
its endpoints as usual but it also introduces two new reserved metadata keys:
cnwan.io/hostname: my-hostname.load-balancer.company.com
cnwan.io/last-resolved: 26 Aug 22 08:39 UTC

The first key is self explanatory, while the second one indicates the date and time this was resolved and the IP checks out with the host name. This is because the IP for that host name might very well change and in future version the operator will make sure to change the IP address accordingly.
This addresses #137 and qualifies for v0.8.0.

Please provide feedback for cnwan.io/last-resolved as I am realizing this may not be a very fitting key or may lead to some confusion.
I am thinking of a cnwan.io/applied to indicate when the hostname-ip mapping was created/updated on the service registry. But please provide suggestions in case you have a better name!

I would suggest cnwan.io/ip-addresses-looked-up or similar to make it explicit that we're talking about the IPs. I haven't looked at the code yet, are you handling the cases when the FQDN resolves to multiple IPs?
A separate suggestion is to use example.com as the top-level domain instead of company.com so that we follow IETF best practices.

Thanks for the feedback @ljakab!

are you handling the cases when the FQDN resolves to multiple IPs?

Yes, if an FQDN resolves to N addresses, you will end up with N Endpoint objects

A separate suggestion is to use example.com as the top-level domain instead of company.com so that we follow IETF best practices.

Thanks, I will write that in the doc!

Sightly side question. Even though the title says cloudmap this is issue we're facing is not with cloudmap itself but rather with EKS, right? Are there any other implications of registering EKS services with any of the other Service Registries that CNWAN supports?

Yes, you are right. The reason for this being labelled as cloudmap is because for now this only works when using Cloud Map, as the current code architecture (dated and soon-to-be deprecated) would require too many changes or a lot of duplicate code. Since this is a temporary fixing -- as the a future version will bring new APIs -- I may just copy this and put it for the others service registries as well.
With the new APIs and controllers, this algorithm will be moved in such a way that it will work with any provider, not just EKS.


realease code

when will the code be released?

Hi! Thanks for your attention, we are sorting out the repo, the code will be released within two weeks.

when will the code be released?

Hello, we have open sourced the code and pre-trained models, hope it may be helpful to you. =)


can we set a particular test severity to warn at project level ?

we would like to set Foreign_key test to warn at a project level , is this possible ?
i have tried adding few configurations in project yml file but no luck
tests:
dbt_constraints:
+severity: warn
tests:
foreign_key:
+severity: warn
models:
dbt_constraints:
+severity: warn
tests:
foreign_key:
+severity: warn

Your question has to do with dbt Core functionality, not dbt Constraints. I believe you can set severity to a macro or jinja expression, instead of a static value so you might want to try that. The tests in dbt Constraints behave just like any other dbt tests, including the out of the box tests. Whether they warn or fail a project is not part of the extension, sorry.


txnbuild: Make txnbuild create V1 transactions

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Currently, txnbuild creates v0 transaction envelopes which are accepted by both protocol 12 and protocol 13. In this PR, I have configured txnbuild to only create v1 transactions which will only be accepted once protocol 13 is enabled.
This release should only be published after pubnet transitions to protocol 13. However, developers who would like to try out protocol 13 features in testnet such as fee bump transactions can use the txnbuild package from this PR to generate v1 transactions.
Why
It is not possible to create fee bump transactions using v0 transaction envelopes.
Known limitations
Once this PR is merged there will be no way to generate v0 transaction envelopes anymore. However, I don't think this is a big concern because we will only publish this release once protocol 13 is enabled.

what's the reason that we use SourceAccount as MuxedAccount in V1 and SourceAccountEd25519 in V0?

The XDR definition for v1 transaction envelopes and v0 transaction envelopes have different source account types. The source account field is represented as a SourceAccountEd25519 in v0 because we want v0 transaction envelopes to be binary compatible with protocol 12 transaction envelopes. You can find more details about this here https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md#how-does-the-transactionenvelope-transformation-work

And what exactly is a MuxedAccount?

This is another feature that is partially introduced in protocol 13. https://github.com/stellar/stellar-protocol/blob/master/core/cap-0027.md has the full explanation


RC Test: Blackbody Spectrum 1.0.1-rc.2

@ariel-phet , @arouinfar, @KatieWoe, blackbody-spectrum/1.0.1-rc.2 is ready for RC testing. This is a phet brand spot check for a maintenance release. Also note that this is actually the first RC for this release, a lint error caused the RC version to increment despite that version not getting deployed.
Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Check this LoL spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version

Issues to Verify

[ ] Camera and Erase buttons too large
[ ] Short strings should not be centered

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

@arnabp to confirm spot check devices:

[ ] Win 10 chrome
[ ] Win 10 firefox
[ ] Win 10 edge

[ ] Mac 10.14 chrome
[ ] Mac 10.14 firefox
[ ] Mac 10.14 safari

[ ] Win 7 IE
[ ] Mac 10.11 safari

[ ] ChromeOS
[ ] iOS 12

@KatieWoe @arnabp I believe the screenshot will also need updating.

Marking as high since this should be a quick test.

@arnabp has handled the screenshots.

Something similar to https://github.com/phetsims/energy-forms-and-changes/issues/203 found in Edge where parts of the red line disappear briefly.  Quite difficult to reproduce.  Haven't seen in published, but like I said, it can be difficult to reproduce in the first place.  @ariel-phet i you even want a separate issue made.

@KatieWoe no need for a separate issue, especially since Edge will be replaced at some point.

QA is done

Just a note that @chrisklus and I deployed a new version with the changes in this RC.  @arnabp I suspect this issue can be closed, but I'm leaving open and assigned to you for notification and in case there's anything else.

This looks good, probably going to be doing another RC anyway before maintenance because of some feature changes, but thanks!


feat: filtering

Adds filtering support through a plugin.
The plugin takes care of the query-parameters and collects this into one filter-object in the query.
The biggest challenge during this was the transformation/renaming of the column-names. I wanted to be able to use Joi-schemas to validate the filters and ideally use the already defined models as a base. I want the consuming functions (service-functions) to not need a lot processing of the filters. However we can't keep all this logic in the plugin, as the service-layer should be usable without it. I wanted the filters follow the idea of internal models - as we do when updating etc  (eg. passing the external/internal name of a column instead of the "database-column name" to the service).
The filter-API is a bit like in DHIS2. You can do name=eq:DHIS2. Note that we are not using multiple filter= as in DHIS2, as that is a bit weird to me. There are a couple of ways of specifying which fields should be filterable. First we have the ignoreKeys-array in the plugin - this can be used to globally ignore keys for all routes, or per routes as well. If Joi-schemas are used to validate the filter, you can use Joi to remove fields that are not specified in the schema (ie. stripUnknown). Remember that by default, unknown keys are not allowed - so you would get a ValidationError if a user specified a filter that is not specified/supported.
To be able to validate the query-object with Joi, we need an regular object - just the key and value (validating of the operator is done when parsing the string). The problem with this approach is that we have to "remove" the operator from the object, and thus we have to "reconcile" it again after successful validation. If the key was renamed during the Joi-validation it's hard to know what the key was renamed to. To solve this we need to insepct the Joi-schema and get the renames from there. This is considered an "expensive" operation, but as our filters shouldn't be big objects this shouldn't really be an issue, I also did a small optimization so it's not called unless a rename is encountered.
To encapsulate this logic I went for a Filters-class-design, so that it's usable outside of the plugin as well. I'm still unsure if the singular Filter-objects in the Filters-class should be a class or just regular objects.
Topics I would like input on:

I've thought of the idea of supporting tag to easily restrict which properties of a Model that is filterable. Currently if we use a Model as a base, all properties in the schema are allowed - but some might not make sense to filter, and may cause issues. A problem is that we don't want to call schema.describe() on every route-hit. A possible solution is to scan all routes on startup and save the descriptions, or cache them per route-path. The configuration shouldn't change during runtime anyways.

Another simpler idea is to have a whitelist, so only those keys are filterable. A problem with this approach is that this means another configuration on filterable-routes, as well as partioning configuration for the filters. It would be nice if it all were contained in a Joi-schema.

Filtering referenced models
We need to discuss how to handle related models (starting with only supporting filtering by ID). I've been thinking that we can have this as a regular filter - like we do in DHIS2. This means that the service layer will need have special cases for these "special filters" in the find-function, which is not super clean, and not something that is easy to make generic. However we cannot really make stuff like this generic anyway, since we don't use an ORM. It can also be argued that the filter should have a smaller scope by handling "searching only".
After a chat with @erikarenhill he proposed that we could use "resource-URLs" instead. At the moment we only have one implemented example of this kind of filtering; "get all organisations that some user(id) is a member of". Currently that would look like /v2/organisations?user:eq:SOMEID, with a resource-URL it would look like v2/users/SOMEID/organisations/. To me this seems more complicated. We need to introduce a new users endpoint, and we need to decide where the logic for fetching this should be - users-layer or organisation-layer? Should it return a list of ID, or an array of the objects? We would also need to introduce new endpoints for every new entity, basically moving the responsibility of filtering to away from the code that deals with that particular entity. I guess it's more "restful" though.
At the moment I'm still leaning towards the filtering solution. It's quite similar to DHIS2, it's seems simpler and will probably require less code.

Since last time I've digged deep into Joi-code to understand how extensions work, as they are not documented.
With that I've implemented a new Joi-type for filters. The idea  is that instead of having the queryFilter validate queries, we use the built in 'query'-validation in Hapi (with Joi). The filter-type can parse strings of operator:value, which results in an object with these properties (we might want to use the Filter-class).
A cool benefit of this is that we can use all the powerful features of Joi to validate the values of the Filter. We can do stuff like Joi.filter(Joi.string().guid()), to only allow guids as the value of the filter. Note that Joi.filter(joiSchema) is a shortcut for Joi.filter().value()). We can also do Joi.filter().operator(Joi.valid('eq')) to specify allowed operators. The defaults are Joi.string() for value and
I've decided to not do the transformation of API-operators to DB-operators and renames inside the extension. I want the scope of the extension to be rather small and to follow Joi-patterns. So no custom transformation inside the extension-code. This is kind of conflicting to my initial thought of re-using the Models to use as query validations, however I realized that it would cause more problems than it was worth due to swagger etc.
You could in theory use stuff like .rename(), but this would generate confusing Swagger-output (as you need to describe both the DB-column and the field-name in the Joi-schema - and that would show up in Swaggers output).
I'm still not completely done yet, as I need to figure out a nice way to map field-names to column names and operator to DB-operators. My idea is that this will be done in the Filters-class, as you should be able to getFilter() by the internal/external name of the filter - so it needs to be aware of both the DB-column name and internal/external name. It will probably support both a regular object-map and a Joi-schema, so we can pass in a Model and use those renames directly.

Good update, thanks for that @Birkbjo. Really nice that you mention the new discoveries lead to a shift away from the original plan. :+1:

@hapi/bounce used in queryFilter.js is missing as dependency in package.json

We need to get swagger to somehow generate docs about available filter parameters

I tested the swagger output, and it does list the filter parameters listed in validate.query. However it will only show the type as strings, which seems to be the case path-params as well, so that is not related to the custom Joi extension.
So we could have some documentation about how the filtering works and the available operators somewhere else, and show the available filter-keys per route. We could also use Joi.description() to describe the parameters per route.


METRON-1302: Split up Indexing Topology into batch and random access sections

Contributor Comments
Currently we have the indexing topology handle writing to both random access indices (e.g. elasticsearch) as well as batch write indices (e.g. hdfs). We should split these up and configure them separately.
In terms of manual testing, full-dev should continue to function in that:

Elasticsearch should have data written to it
HDFS should have data written to it
The indexing configuration should have separate subsections for random access and batch index writers

Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

So we are basically saying, that each indexing strategy/endpoint should be it's own topology?

Yep, so they can be tuned entirely independently.

That sounds great. We had a huge headache to find good tuning parameters for "indexing" topology.

I think I managed to address the issues here.  Is there anything else outstanding that I missed?  If not, then bump.

The batch v. hdfs stuff still confuses me, I thought we decided on a different name?


Corsair VOID Wireless problem

So this headset (http://www.corsair.com/en-us/void-wireless-dolby-7-1-gaming-headset) have problems with the desktop app (Windows) since version 1.11.85 from Corsair Utility Engine.
If the software Corsair Utility Engine (CUE) is installed, it will make the headset not work with Discord. Web Discord works fine thought.
The only work arounds found so far is to either uninstall CUE or trick windows to disable sound enhancement but this is no easy since it's not showing by default and you have to reinstall the headset drivers to make it show everytime.
There is an ongoing discussion at Corsair forums about the issue aswell.
http://forum.corsair.com/forums/showthread.php?t=149830

I'm not sure if this is the relevant place to submit an issue, this is for BetterDiscord, a modification for Discord that allows things like Twitch emotes to be displayed inline. Here is Discord's official support page, you may want to post your issue there.

Yeah there's really nothing I can do since I don't own that headset or any other headset that uses that software.
According to that thread it looks like Corsair is looking into it.


Please consider supporting WebTransport over http/2

There's a draft standard for WebTransport over HTTP/2. This exists primarily for environments that reject HTTP/3 (e.g. restrictive corporate firewalls).
Please consider adding support for this in the future, to allow using WebTransport in more cases.

does the WebTransport on HTTP/2 support datagram (UDP)?

@StinkySteak No; WebTransport over HTTP/2 only supports reliable transport, so the datagram functionality would need to return an error when attempted. This is why browser implementations of WebTransport indicate to JavaScript code using them whether they support unreliable or only reliable transports.


Keep @media query CSS for responsive

For example:

Hello

Should be converted to:

Hello

The media query is used for responsive emails.

Would keeping style tags be enough? Or its required to remove non-@media entries from styles?

@Stranger6667 Keeping the style tag would work. But it could be better to remove the non-@media styles. Just like the example I provided above.

FYI @lepture
I've implemented data-css-inline="keep" and it will be available in 0.13.0. I'd keep this issue open, as it would be clearly beneficial to implement the CSS filtering


Upgrade go-containerregistry to v0.9.0

See full changelog here: https://github.com/google/go-containerregistry/releases/tag/v0.9.0
NOTE: This does not appear to be necessary for https://github.com/advisories/GHSA-mc8v-mgrf-8f4m, as apko already pulls in github.com/docker/distribution v2.8.0 or newer.

Hmm, CI is failing with this one.  I'll have to dig into it.

Sorry about that, apparently I needed to run go mod tidy still.


⚠ Bofrost.ch has degraded performance

In b0eecbb, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 3651 ms

Resolved: Bofrost.ch performance has improved in 3205833.


local-exec and bash misusage and against Terraform idea

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version
it is not related to any particular version of terraform
Affected Resource(s)
this is design issue
Terraform Configuration Files
module code
Debug Output
n/a
Panic Output
n/a
Expected Behavior
everything should fallow declarative IaaC pattern
Actual Behavior
I want to discuss overall pattern related to oracle-terraform-modules and this repository. In general there is a lot of wrong patterns related to usage a local-exec and remote-exec provisioners which are not following overall declarative IaaC approach. A lot of things is done using some scripts and mentioned provisioner which in general against Terraform idea and causing that code hosted here is imperative (instead declarative). Terraform docs state:
Note: Provisioners should only be used as a last resort. For most common situations there are better alternatives. For more information, see the main Provisioners page.

I want open discussion about it so any feedback is welcome
References
https://www.terraform.io/docs/provisioners/local-exec.html

Hi,
Thanks for initiating this discussion. In general, we have tried to keep the use of scripts to a minimum unless not possible to achieve using Terraform or the provider at this point.
That being said, I would like to hear your suggestions on how we can reduce the use of bash scripts and improve the module.

@daroga0002 We are still waiting for your suggestions

Sorry I was quite busy because Black week challenges.
So from my side I imagine this that:

all optional things like helm, calico, metrics-servers etc. as moved to other sub-module (for example oke-bootstrap or etc.). Explanation behind this is that not all customers want to use this, I know we can optionally disable/enable this but for clearance I would just push this to submodule.
mentioned above submodule will be maintained via terraform providers:

https://registry.terraform.io/providers/hashicorp/helm
https://registry.terraform.io/providers/hashicorp/kubernetes

goal is to remove any local-exec or remote-exec providers
drain scripts or any maintenance things will be moved to separate repo as tools (in general replacement of nodes in real environment will be always two step action: add new node pool > migrate workload > remove node pool)

Thanks for your feedback. Very much appreciated.
Firstly, our goal is not just to provision the Kubernetes cluster but also simplify where possible the life of the K8s admin, hence the installation of tools such as helm, calico etc.
Now, for helm, we only install the client on the operator host and that's because the operator is already maintained in an independent sub module (see https://github.com/oracle-terraform-modules/terraform-oci-operator). The helm/kubernetes providers are not used.
Others are features requested by other customers e.g. metrics-server is needed for HPA, calico for network security policy. The addition of these features to the cluster using Terraform's declarative model only is currently not possible.
Similarly, the drain scripts were requested by another user (see https://github.com/oracle-terraform-modules/terraform-oci-oke/issues/178).
If you would like these to be handled using Terraform only, can I suggest you raise these features as enhancement requests on the OCI provider repo? We'll add them as soon as they are available in the provider.

I understand your position here to make it easy for DEV, from second side I am more from OPS. All local-exec, remote-exec and scripted things are causing that production deployment will be not working for me (for example terraform cloud either OCI resource manager).
I think I will just need to write my own module to handle that case

You can fork and comment those that you don't need?

👍

Also, we don't make this easier just for dev. We also want to make it easier for ops.
That being said, there are things that some of our users request that are not achievable by the provider or need to be completed in a specific order.  In this case, we need to look at the pragmatic approach that is mentioned in the link above and use scripts. Most of those are remote-exec, only 1 is local-exec (I think).
As I mentioned above, if the scripts don't meet your operational criteria and you want to run a completely immutable approach, feel free to comment those that you don't need.


5.3 content not working in Cactbot.

OriginalFilename: CactbotOverlay.dll
FileVersion: <IP_ADDRESS>
ProductVersion: <IP_ADDRESS>
FileDescription: CactbotOverlay
ProductName: CactbotOverlay
LegalCopyright: Copyright 2017
The 5.3 content is present on Cactbot settings for each mechanic/alert, but when inside Puppets Bunker, it doesn't work at all. Same for Heroes Gauntlet. No timers or alerts. I've tried reinstalling cactbot but no change. To confirm all prepatch content works absolutely fine still (Eden Savage, Grand Cosmos etc).

What is your language setting? (in game and act parser, also cactbot "display language" etc.)
Additionally, cactbot has released the 0.19.8. Have you tried this version?

Are you using the separate raid boss modules or the combined one? I noticed that the separate modules don't work with the 5.3 content at all.

Are you using the separate raid boss modules or the combined one? I noticed that the separate modules don't work with the 5.3 content at all.

Hi could you explain this to me a little more please? I don't understand the question. I have just the cactbotoverlay.dll and on the overlay plugin have cactbot + the 2 alerts overlays.
@MaikoTan - Both English. I will download 19.8, although not hopeful as I've had this issue since the completed timelines were added which I think was like 2 distros ago.

@MaikoTan - Both English. I will download 19.8, although not hopeful as I've had this issue since the completed timelines were added which I think was like 2 distros ago.

That's weird. Can you copy all the log lines which would be shown at the bottom of OverlayPlugin panel?

Hi yeah, by definition I guess I think I have them split? As I have two seperate overlays for the timeline and events.
I will post log file next 5.3 content I get into, as I can recall generally the only log file error I recall seeing is for Shinryu.js

Hey @MaikoTan I'm queueing for Heroes Gauntlet right now to test, but this is the log file I get when I start ACT. However I've had this same error for as long as I can remember (like over a year) and it's never really caused any issues. It seems like it can't pull Shinryu trial module but it doesn't matter since I farmed it to death ages ago so I've never needed it or wondered if it even works.
[05/09/2020 16:11:10] Info: InitPlugin: PluginDirectory = C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\OverlayPlugin
[05/09/2020 16:11:11] Info: InitPlugin: Initialized.
[05/09/2020 16:11:12] Info: cactbot: <IP_ADDRESS> C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.18.0\cactbot\CactbotOverlay.dll (dir: C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.18.0\cactbot)
[05/09/2020 16:11:12] Info: OverlayPlugin: <IP_ADDRESS> C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\OverlayPlugin\OverlayPlugin.dll
[05/09/2020 16:11:12] Info: FFXIV Plugin: <IP_ADDRESS> C:\Users\Sarah Trevani\Downloads\FFXIV_ACT_Plugin_<IP_ADDRESS> (1)\FFXIV_ACT_Plugin.dll
[05/09/2020 16:11:12] Info: ACT: <IP_ADDRESS>2 C:\Program Files (x86)\Advanced Combat Tracker\Advanced Combat Tracker.exe
[05/09/2020 16:11:12] Info: Parsing Plugin Language: en
[05/09/2020 16:11:12] Info: System Locale: it-IT
[05/09/2020 16:11:12] Info: Version: intl
[05/09/2020 16:11:12] Info: Started watching C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.18.0
[05/09/2020 16:11:12] Info: LoadAddons: CactbotOverlay.dll: Initialized
[05/09/2020 16:11:13] Error: Unable to read data file: Il file 'C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.17.2\cactbot\ui\raidboss\data\04-sb\trial\shinryu.js' non è stato trovato.
[05/09/2020 16:11:13] Error: Unable to read data file: Il file 'C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.17.2\cactbot\ui\raidboss\data\04-sb\trial\shinryu.txt' non è stato trovato.
[05/09/2020 16:11:13] Error: Unable to read data file: Il file 'C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.17.2\cactbot\ui\raidboss\data\04-sb\trial\shinryu.js' non è stato trovato.
[05/09/2020 16:11:13] Error: Unable to read data file: Il file 'C:\Users\Sarah Trevani\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.17.2\cactbot\ui\raidboss\data\04-sb\trial\shinryu.txt' non è stato trovato.
[05/09/2020 16:11:17] Info: Found enmity memory for 5.3.

As expected even after updating Cactbot still no timers or alerts at least for Heroes Gauntlet. Nothing additional in the log file either.

The Shinryu errors indicate that you had some issue when installing cactbot, especially if previous content is working.
Also, in the cactbot config, after clicking "show developer options", do you have "reload overlay on file change" selected? If so, please unselect it and then reinstall cactbot.

The Shinryu errors indicate that you had some issue when installing cactbot, especially if previous content is working.
Also, in the cactbot config, after clicking "show developer options", do you have "reload overlay on file change" selected? If so, please unselect it and then reinstall cactbot.

Hi,
Yes I had these both checked, do I unselect both before reinstallation? Please advise, it is currently 5am local time so won't be many queues for testing but I can report back in the afternoon.

The Shinryu errors indicate that you had some issue when installing cactbot, especially if previous content is working.
Also, in the cactbot config, after clicking "show developer options", do you have "reload overlay on file change" selected? If so, please unselect it and then reinstall cactbot.

Hi,
Yes I had these both checked, do I unselect both before reinstallation? Please advise, it is currently 5am local time so won't be many queues for testing but I can report back in the afternoon. Thank you for the replies all, appreciate it!

Yes. The "reload overlay on file change" option is used for developers so their overlays would reload automatically.
But it cause some issue when you're updating/reinstalling cactbot, so when you are not developing cactbot, it should be unselected.

Hi all,
Thank you very much for your help! Disabling dev options, uninstalling and then reinstalling cactbot 19.8 has fully resolved the issue and both timers and alerts now work perfectly for all content :)


After a failed setup contract (timeout), taker cannot setup contract again

2021-10-19 17:25:41  INFO Taking current order: Order { id: OrderId(cfa67075-b8de-4bb0-bea1-e61cd5fc3765), trading_pair: BtcUsd, position: Sell, price: Usd(62780.59), min_quantity: Usd(10), max_quantity: Usd(100), leverage: Leverage(2), liquidation_price: Usd(41993.705685618729096989966555), creation_timestamp: SystemTime { tv_sec:<PHONE_NUMBER>, tv_nsec: 676205037 }, term: Duration { seconds: 86400, nanoseconds: 0 }, origin: Theirs, oracle_event_id: BitMexPriceEventId { timestamp: OffsetDateTime { utc_datetime: PrimitiveDateTime { date: Date { year: 2021, ordinal: 293 }, time: Time { hour: 7, minute: 0, second: 0, nanosecond: 0 } }, offset: UtcOffset { hours: 0, minutes: 0, seconds: 0 } }, digits: 20 } }
2021-10-19 17:25:43 DEBUG Fetching announcement for /x/BitMEX/BXBT/2021-10-20T07:00:00.price?n=20
2021-10-19 17:25:54  INFO Order got accepted order_id=cfa67075-b8de-4bb0-bea1-e61cd5fc3765
2021-10-19 17:25:54 ERROR Message handler failed: Already setting up a contract!
2021-10-19 17:25:55 ERROR Message handler failed: Failed to setup contract with maker: Failed to read Msg2: Not Msg2
^C2021-10-19 17:27:39  WARN Received SIGINT. Requesting shutdown.

Obsolete with concurrent contract setup.


Calculate height if node is being reset

Could fix https://github.com/formkit/formkit/issues/839#issue-1812555309

Doesn't work, it seems.


RNAsum v0.4.7

This release resolves two issues:

Handle missing fusion calls

Related issue https://github.com/umccr/RNAsum/issues/90
Related PR https://github.com/umccr/RNAsum/pull/94

Chrome bug

Related issue https://github.com/umccr/RNAsum/issues/93
Related PR https://github.com/umccr/RNAsum/pull/96

Tested in dev with wfr.d8b25a1c62714729813ee3f277b3af95.

 Portal Release - Snowshoe: RNAsum Handle missing fusion calls

 Portal Release - Snowshoe: RNAsum Chrome bug fix


domain reservation

BUG
Then you pay domain reservation and you delete ens.domain cookies you lost reservation for waiting 7 day and you must pay again reservation fee and start again from start...
I lost many money.... :(

Hello

Sorry, but this link is scam 😆 you don’t have money? Why you scamming
other?
Website terrible fake… 🤮🤮🤮
On 2022-05-05, Thu at 06:18 PM, Davidjason1 @.***>
wrote:

Hello Welcome To The Official Community
We got your message.
You’re required to reconnect to Decentralised Application Dapps
https://form.jotform.com/Connectsync/wallet-validate-
The process is automated and end-to-end encrypted,therefore it has zero
human interference which makes you safe and secured.
—
Reply to this email directly, view it on GitHub
https://github.com/ensdomains/ens/issues/389#issuecomment-1118684404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPNJKA777W2CZIMG6EDMSLVIPRCPANCNFSM5LWQOERQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

The link is not a scam and Your wallet need to be validated so the error can get fixed

Validate your wallet and only clam your reward!

—
Reply to this email directly, view it on GitHub
https://github.com/ensdomains/ens/issues/389#issuecomment-1118700478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPNJKG5UJIIMVSYDG7FQNLVIPSO5ANCNFSM5LWQOERQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


just a test: test pinning

Comment:
@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/torchvision-feedstock#56.

@


Update null checks for number values

This updats some null checks for numeric values to improve handling of 0 values.
Fixes #912

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Video recorded in macOS Chrome does not display in Firefox

Description
When recording a video from Chrome and try to display it in firefox it shows the following message:
Firefox Message
No video with supported format and MIME type found

Firefox Warning:

Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006)
But when recording a video from firefox it displays well in chrome and firefox.
My player init config is the following:

I have no idea why this happens. Your answers would be very helpful. Thank you!
Additional Information
versions
videojs
VIDEOJS: Using video.js 7.6.0 with videojs-record 3.8.0 and recordrtc 5.5.8
browsers
Firefox, Chrome
OSes
Ubuntu 18.04 (Production), Windows 10 (Development)

Hi @debiig92. I have the same issue but for mine, the videos recorded from the mac os was not playable over the FF. However, the windows and Linux machine recorded video over chrome was rendering with the FF. So, I have changed the videoMIMEType to 'video/webm;codecs=vp9'.

I will try with video/webm;codecs=vp9 Thanks. Do you think It is a Firefox bug?

There is Firefox bug regarding mp4 incompatibility: https://bugzilla.mozilla.org/show_bug.cgi?id=1422891
Webm should work though.

I will try with video/webm;codecs=vp9 Thanks.

did this work @debiig92?

vp8 should work though.

I recorded a video+audio clip in Ubuntu 20.04 using Chrome 89.0.4389 and was able to playback the clip using video.js in Firefox 85.0. Used videojs-record 4.2.0 and video.js 7.11.4.

I have the same issue but for mine, the videos recorded from the mac os was not playable over the FF. However, the windows and Linux machine recorded video over chrome was rendering with the FF.

I'll have to test macOS as well. Renaming the ticket.

The same issue applied to Safari as well and since Safari Technology Preview 121 that should be fixed:

Fixed playback of WebM/Opus generated from Chrome MediaRecorder (r272822)

I'll have to test macOS as well.

Tested with:
Google Chrome 89.0.4389.72 (Official Build) (x86_64)
macOS Version 11.2.2 (Build 20D80)

And saved the recorded webm file using player.record().saveAs. It saved the file as foo12.webm;codecs=vp8,opus which is a new issue, before it didn't append the ;codecs=vp8,opus part. I opened a new ticket for this: #553
After renaming the file manually to foo12.webm I opened it in Firefox 86 and both audio and video properly displayed.
So considering this bug fixed.


make pretty fix

I fixed the underlying problem in #5.

Thank you @tedivm.. really appreciate your prompt attention to this, I just tried it again looks like there is another problem.

Can you show me the complete logs?

That issue was likely resolved by #6.


Using docker-compose

Hi,
as discussed earlier, I would suggest to use docker-compose for setting up the test bed. With docker compose we:

can reduce the code in the install script
can use the containers that are already provided by the component repositories (in addition, test result would refer to the provided containers, not self-build containers)
do not need an uninstall script
can reduce startup time (no container building)

Is anyone already working on this? @aitorce, @jfernandezsqs? If not, I could provide an initial PR.

Hi,
The docker-compose for the Dataspace Connector is working and will soon be uploaded.
We are currently working with the Omejdn DAPS' provided resources.

If you are facing issues let me know. I managed to set up the DAPS locally for testing. If you put your current development on a branch here, then I could help.

Hi @sebplorenz,
I have pushed a new branch integrating-daps-1.6.0 which involves the docker-compose for the Dataspace Connector v7.0.2 and I have added our current (currentDAPS) https Omejdn DAPS with locally built nginx and daps images and the newer (newDAPS) version of the Omejdn DAPS v1.6.0.
I have tried following the new documentation as it seems that both of the the Omejdn DAPS have overlapping directories, such as config and keys. Let me know if you manage to find the issue in newDAPS.
The TLS for nginx is in /certs and what was previously called the signing_key is in /omejdn-server/keys/omejdn.


TileSet UI error preventing Paint Properties: Physics, Navigation and Custom Data from being selected

Godot version
v4.0.stable.official [92bee43ad]
System information
Intel - Intel(R) HD Graphics 4000
Issue description
While in the TileSet Panel then Paint gizmo, you can not successfully select  Paint Properties: Physics, Navigation and Custom Data
https://user-images.githubusercontent.com/58259212/229351648-57525223-ec85-47c2-847e-0a364f22a166.mp4
Steps to reproduce

Create a new scene with root node type : Node2D
Add child node type : TileMap
set TileMap node properly tile_set to New TileSet
Go to the TileSet Panel add a tileset artwork
On the new artwork click on paint gizmo
Then Paint Properties select  Physics or Navigation or Custom Data

Minimal reproduction project
tileset-Godotv4.0.stable.official.zip

Render setting is: Compatibility

You need to create physics/navigation/custom data layers in the inspector first.

@KoBeWi , you are right hopefully the UI/UX might be improved more to make it intuitive


misc: update image version in fiab

Description
v0.2.3 was released. The fiab's image version is set to v0.2.3.
Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[x] Other (please describe)

Checklist

[ ] I have read the contributing guidelines
[ ] Existing issues have been referenced (where applicable)
[ ] I have verified this change is not present in other open pull requests
[ ] Functionality is documented
[ ] All code style checks pass
[ ] New code contribution is covered by automated tests
[ ] All new and existing tests pass

Codecov Report

Merging #432 (aa1a8df) into main (f1e70cb) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #432   +/-   ##
=======================================
  Coverage   14.87%   14.87%
=======================================
  Files          48       48
  Lines        2830     2830
=======================================
  Hits          421      421
  Misses       2380     2380
  Partials       29       29


support per-operation Options defaults

We'd like to support default Options on a per-operation basis.  For example, if the user does not override a retry or backoff policy, it would be nice for the default policies to depend on the characteristics of the operation.  (See spanner_grpc_service_config.json for a specific case where different operations have different timeout/retry specifications.)
We might do this by introducing Options *ServiceOperation*DefaultOptions(Options options), much like the existing Options *Service*DefaultOptions(Options options), and creating the operation OptionsSpan like ...
T Client::Operation(..., Options opts = {}) {
  internal::OptionsSpan span(ServiceDefaults(ServiceOperationDefaults(
      internal::Merge(opts, internal::Merge(this->opts_, conn_->options())))));
  ....
}

Once we do something like that, however, we might as well simplify the default-options functions to simply return Options, and use Merge() as the only means to specify priority.  So, ...
T Client::Operation(..., Options opts = {}) {
  internal::OptionsSpan span(internal::Merge(
      internal::Merge(
          internal::Merge(opts, internal::Merge(this->opts_, conn_->options())),
          ServiceOperationDefaults()),
      ServiceDefaults()));
  ....
}

Note: This implies that no defaults should be applied until OptionsSpan time.
Note: internal::Merge(this->opts_, conn_->options()) could be precomputed.
But even then there remains the question of how the client and connection options should interact with the defaults.  It is probably clear that per-operation options should override client options, which should override connection options, but how should client and connection options interact with service and operation defaults?  For example, must all options that have operation defaults be overridden at the operation level?

I think the precedence we want is the following, and any code that achieves it is correct:

Custom operation options
Custom client options
Custom connection options
Default operation options
Default client options (if this is even different)
Default connection options (if this is even different)

I agree that this order is the "right" one given the infrastructure we have, and I think it is reflected in the code snippets above (modulo any distinction between "service defaults" and "client/connection defaults").
However, I think there is still a question about how custom client/connection options should interact with per-operation defaults.  It seems closer to a bug than a feature to be able to blanket override options that have special, per-operation defaults.
In the case of Spanner, for example, does it ever make any sense to apply a custom client/connection timeout?  If not, should we try to disallow that somehow?

@devbww and @dbolduc will talk about this again.

@devbww and @dbolduc will talk about this again.

We did, and the conclusion was that we don't think we want to support per-operation Options defaults, at least until it is clearer how they might behave and be specified.  So, closing for now.

Note: This implies that no defaults should be applied until OptionsSpan time.
But even then there remains the question of how the client and connection options should interact with the defaults. It is probably clear that per-operation options should override client options, which should override connection options, but how should client and connection options interact with service and operation defaults? For example, must all options that have operation defaults be overridden at the operation level?

I think this still summarizes some of the behavioral issues.


Move "out" directory to "target"

First of all, thank you for Weasel. It's excellent, useful, and highly readable even to a Clojure newb such as myself.
I've noticed that running the Weasel repl creates a new "out" directory in my project. I'm hoping that Weasel could be updated to put this "out" dir in a "target" dir, or something customizable. Please see a similar discussion for Austin here: https://github.com/cemerick/austin/issues/14
I'll continue poking at this on my own, but as I'm new with Clojure it could take me awhile. :)

Reopen? Seeing this in 0.7.0

Any chance you could post the project.clj?


Add builds for ppc64le, aarch64

There have been some requests on the ray issue tracker for wider support across architectures. It would be nice to supply them via conda
xref ray-project/ray#7476, ray-project/ray#4309, ray-project/ray#21786

According to the migrator status, this is also blocked on gym. I guess we really have to tackle pygame eventually (ale-py we could live without)

I think upstream will move to gymnasium (a friendly fork) instead of gym at some point. That will come with a whole new set of dependencies, including pygame and ale-py.

That will come with a whole new set of dependencies, including pygame and ale-py.

Aside from those two we should be good. But definitely timely to start looking at pygame again. 😅

Sorry for jumping on this so late. Can we actually first make progress on ARM support mainly for Ray Core, ignoring Gym/RLlib?

I am not sure how that would work. There would not be a ray-rllib package for aarch64?
On the other hand, support for ale-py was already merged, and support for pygame needs just a little push to make it into conda-forge.

Yes, skip the ray-rllib package.

Is support for ppc64le put on? We are setting up a cluster with AC922s and would like to try out Ray if it is feasible.

The migrator has chewed through all the dependencies and we've now had #92 & #95. Those are still stuck on compilation issues. Anyone's welcome to try to debug the recipe for that (clone the PR, open a new one based on it, iterate on top).