Rendering of Definition List/Option List/Field List

Problem
Definition List/Option List/Field List are rendered differently on ReadTheDocs than in a local build. See attached screenshots:
on https://sphinx-rtd-theme.readthedocs.io/en/0.5.0/

local build:

Environment Info

Python Version: 3.6.8
Sphinx Version: 3.1.2
RTD Theme Version: 0.5.0

Same here.
The CSS code seems to have disappeared completely.

It seems to have disappeared in commit ff594d23ff16b52f3a2d626e7c8b295f550e0de1 by @agjohnson

Oops, I see the issue. Nothing disappeared, but the versioned docs are being built with sphinx_rtd_theme==0.4.3 still. The last PR build looks fine:
https://sphinx-rtd-theme--981.org.readthedocs.build/en/981/demo/lists_tables.html#definition-lists
PR builds use the local version of the theme, not a pinned version of the PyPI theme. I'd prefer if the versioned docs are built using the local theme as well -- that is, 0.5.0 docs use the local 0.5.0 of the theme -- but I think there were some objections to that previously.

@agjohnson thanks for the info.
so the design change was intended. that's good to know although I'm not 100% happy with it. I like it for the field list but not for the definition list. for the option list I'm uncertain... a little bit off topic but is the a easy way to revert it locally (css override) for the definition list but leave it for the field list?

To bring back the definition list style, I added this CSS via a custom stylesheet file:
.rst-content dl:not(.docutils) dt:first-child {
  margin-top: 0;
}
.rst-content dl:not(.docutils) dt {
  display: table;
  margin: 6px 0;
  font-size: 90%;
  line-height: normal;
  background: #e7f2fa;
  color: #2980B9;
  border-top: solid 3px #6ab0de;
  padding: 6px;
  position: relative;
}

@agjohnson , are you 100% sure the removal of those styles was intentional, rather than by mistake?

The intended styles are available at https://sphinx-rtd-theme--981.org.readthedocs.build/en/981/demo/lists_tables.html#definition-lists
These styles match sphinx_rtd_theme version 0.4.2 with the Sphinx html4 writer. The first image you posted, sphinx_rtd_theme with the Sphinx html5 writer, is mostly buggy display, those were not intended to be the styles.
Custom CSS should not be required, use 0.5.0 and the HTML5 writer.

@agjohnson , are you 100% sure the removal of those styles was intentional, rather than by mistake?

Yes, intentional, to match the display styles of sphinx_rtd_theme 0.4.3 and html4 writer. 0.4.3 does not support the html5 writer.

Hello! I’m very glad I found this because I believe I'm experiencing a similar issue. In my case, the option lists are rendered very stylishly on my local laptop, but they look really ugly in the web.
This is what I see from my local laptop:

This is what's rendered on the web (https://pypgx.readthedocs.io/en/latest/commands.html#options):

@agjohnson, how can I tell readthedocs to use the "HTML5 writer" and sphinx_rtd_theme==0.4.3? I tried simply adding sphinx==3.1.2 and sphinx_rtd_theme==0.5.0 to the reqruements_dev.txt file, but it didn't do the trick. I also tried explicitly telling readthedocs to use the changed reqruements_dev.txt file in Project > Admin > Advanced Settings > "Requirements file" but it didn't work. Finally, I tried wiping build environment because of this issue but without success. It seems, no matter what I do, readthedocs keeps using lower versions of sphinx and sphinx_rtd_theme (i.e. sphinx<2 sphinx-rtd-theme<0.5 readthedocs-sphinx-ext<1.1), as shown in my latest build attempt.
Would greatly appreciate if you or anyone else can help me start enjoying the beautiful rendering of readthedocs again!

Add the following to your conf.py

# Enable HTML5 writer support
html_experimental_html5_writer = True

@Daltz333 Thank you very much for the reply! I followed your advice for one of my projects, and it is now showing the intended style for the option lists (thanks to html5), except they are still in "buggy display" as agjohnson mentioned above (https://stargazer.readthedocs.io/en/latest/documentation.html#options). I think it's because RTD is still using a lower version of sphinx_rtd_theme (the build history says it used v0.4.3). If you don't, could you please teach me how to properly specify a higher version of sphinx_rtd_theme (==v0.5.0)?

@sbslee To specify a version of sphinx_rtd_theme, you'll need to create a requirements.txt file with the line
sphinx_rtd_theme==0.5.0

and then point RTD to this in your RTD interface, or through a RTD configuration file.

@Daltz333 Thank you! I totally forgot about the existence of the RTD configuration file (.readthedocs.yml)! I got it confused with the conf.py file. Once I updated the configuration file, it finally successfully installed sphinx_rtd_theme==0.5.0. However, it seems the "buggy display" is still there (https://stargazer.readthedocs.io/en/latest/documentation.html#options) and I don't know what the problem is anymore... As per agjohnson's advise, I am using sphinx_rtd_theme==0.5.0 and html5.

I also reproduced the issue. Even when specifying the HTML4 builder.

Hi, I just wanted to give an update to those who might be interested: For whatever reason, my website started displaying the option lists properly. I didn't change anything, it just got fixed (I'm using HTML5 and sphinx_rtd_theme==0.5.0; for more information, read above). My guess is it has to do with cookies/cache being updated (but I'm not an expert on this)?

@sbslee what version of Sphinx do you use btw?

Looking at the latest build history (https://readthedocs.org/projects/stargazer/builds/11578782/), I think Sphinx-1.8.5 was used to generate the website.

@agjohnson This has persisted into version 0.5.0. The CSS style provided by @jobec fixed my issue. Will this be fixed?

Just a quick note to anyone else who may find themselves here, looking for a solution to the misplaced CSS for these lists. If using pip, make sure your requirements.txt file has version 0.5.0 for sphinx-rtd-theme (I was using 0.5.0rc1).

sphinx-rtd-theme==0.5.0

And run pip install -r requirements.txt, to ensure the right package version is installed. This is key. Use pip list to verify the installed package versions.
Once I has updated to the latest release and rebuilt the HTML using Sphinx, these lists formatted correctly.

This has been fixed except for the spacing issues with lists, to keep track of that issue see #1029. For those still experiencing the other issues make sure you are using spinx_rtd_theme 0.5.1 or greater and are not using the html4 writer.


Feed known DE in neural DE

First of all thank you for all of the work that went into this!
I've been trying to get the gist of DiffEqFlux and I'm having a hard time solving a seemingly trivial problem: I'm trying to solve a Neural SDE in which one of the inputs of the neural network is the solution to a given DE. Basically I have two series (Z, K) - that were generated jointly - where Z is independent of K. What I want is for the neural network to learn the evolution of K given that it knows exactly the evolution of Z.
In the following MWE I'll be using sensealg = TrackerAdjoint() because the actual problem is for an SDE which, if I understood correctly from the docs, leaves me only that.
using Plots
using Flux, DiffEqFlux, DifferentialEquations, DiffEqSensitivity
using DiffEqFlux.Tracker

Z̄ = 1.5f0
K̄ = 3.0f0
u0 = [Z̄; K̄]

mp       = Float32[0.2, 0.0]
datasize = 30
t_min    = 1.0f0
t_max    = 10.0f0
t_span   = (t_min, t_max)
t_range   = range(t_span[1], t_span[2], length = datasize)

training_t_span = (0.9*t_min, 1.1*t_max)

dZ_d(Z, K, t) = -0.1f0*(Z̄ - Z)^3 + 0.2f0*(Z̄ - Z) + cos(t)/((t - t_min) + 1)
dK_d(Z, K, t) = 2.0f0*Z^3 - 0.1f0*K^3

dZ_n(Z, K, t) = mp[1].*Z
dK_n(Z, K, t) = mp[2].*K

# True SDE
function trueODE!(du, u, p, t)
    Z, K = u
    du[1], du[2] = dZ_d(Z, K, t), dK_d(Z, K, t)
end
function true_noise!(du, u, p, t)
    Z, K = u
    du[1], du[2] = dZ_n(Z, K, t), dK_n(Z, K, t)
end
prob_true = SDEProblem{true}(trueODE!, true_noise!, u0, training_t_span)
training_sol = solve(prob_true, SOSRI(); dense = true, reltol = 1e-1, abstol = 1e-1)
training_data = training_sol(t_range)

nn_drift = Chain(x -> (x).^3,
                Dense(2, 16, tanh),
                Dense(16, 1))

p_d, re_drift = Flux.destructure(nn_drift)
ps = Flux.params(p_d)

function sdeN(par)
    function dudt(u, p, t)
        Z = training_sol(t, idxs = 1) |> Float32
        n_input = [Z, u] #|> Tracker.collect

        du = re_drift(p)(n_input)[1]
        return du #|> Tracker.collect
    end

    prob = ODEProblem{false}(dudt, u0[2], t_span, par)
    return Array(concrete_solve(prob, SOSRI(), u0[2], par; sensealg = TrackerAdjoint(), saveat = t_range, reltol = 1e-1, abstol = 1e-1)) #|> Tracker.collect
end

predict_sdeN() = sdeN(p_d)
predict_sdeN()

opt = ADAM(1e-3)
loss_flux() = sum(abs2, training_data[2, :] .- predict_sdeN())

function cb(K_pred)
    K_train = training_data[2, :]

    println("Current loss: $(sum(abs2, K_train .- K_pred))")

    pl = plot(t_range, K_pred, lw = 5, label = "K prediction", xlabel = "Time")
         scatter!(pl, t_range, K_train, label = "K data", title = "Neural ODE: Training")
    display(plot(pl))
end
cb_flux() = cb(predict_sdeN())
Flux.train!(loss_flux, ps, Iterators.repeated((), 100), opt, cb = cb_flux)

However, this gives me the following MethodError (I leave out the stacktrace which is very unwieldy):
ERROR: MethodError: no method matching Float32(::Tracker.TrackedReal{Float64})

I tried playing around with Tracker.collect or even with different sensealg but different errors pop up at different times and I'm not sure what I'm doing wrong and where.

So, I figured the problem doesn't really have anything to do with feeding a known series in the neural DE.
There are in fact two (separate) issues that I don't fully understand:

The first has to do with defining u0 as a scalar or an array (I have found a fix but I’d like to understand why the example isn’t working)
The second, which is more important, has to do with using sensealg = TrackerAdjoint(), for which my problem doesn’t actually work (I’d like to run a neural SDE, which is why I need to use that)

I know this is a lot to read, but any help would be very much appreciated.
This first part (setup) is fine:
using DifferentialEquations, DiffEqFlux, DiffEqSensitivity, Flux

u0 = 1/2

datasize = 30
t_span = (t_min, t_max) = (0.0, 1.0)
t_range = range(t_min, t_max, length = datasize)
dt = (t_max - t_min)/datasize

true_ode(u, p, t) = 1.01*u

prob = ODEProblem{false}(true_ode, u0, t_span)
sol = solve(prob; dense = true)
sim = sol(t_range)

nn = Chain(Dense(1, 16, softplus),
                 Dense(16, 1))

p_nn, re_nn = Flux.destructure(nn)

So, as mentioned above the first problem has to do with using u0 as a scalar rather than an array.
What I find especially weird is that I can solve the neural ODE, but I cannot train the network.
function odeN(par)
    function dudt(u, p, t)
        return re_nn(p)([u[1]])[1]
    end
    prob = ODEProblem{false}(dudt, u0, t_span, par)
    return Array(concrete_solve(prob, Euler(), u0, par; dt = dt, saveat = t_range))
end
loss = θ -> sum(abs2, sim .- odeN(θ)[:])
l = loss(p_non)
cb = (θ, l) -> println("Current loss:", l)

# this works:
loss(p_nn)

# this doesn't work:
DiffEqFlux.sciml_train!(loss, p_nn, ADAM(0.1), maxiters = 100, cb = cb)

ERROR: MethodError: no method matching similar(::Float64, ::Int64)
Closest candidates are:
  similar(::JuliaInterpreter.Compiled, ::Any) at /Users/Riccardo/.julia/packages/JuliaInterpreter/oKkmr/src/types.jl:7
  similar(::Array{T,N} where N, ::Int64) where T at array.jl:333
  similar(::BitArray, ::Int64...) at bitarray.jl:342
  ...
Stacktrace:
 [1] #ODEAdjointProblem#50(::Array{Float64,1}, ::CallbackSet{Tuple{},Tuple{}}, ::Float64, ::Float64, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}}, ::typeof(ODEAdjointProblem), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::InterpolatingAdjoint{0,true,Val{:central}}, ::DiffEqSensitivity.var"#df#62"{Array{Float64,1}}, ::StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}, ::Nothing) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/interpolating_adjoint.jl:102
 [2] (::DiffEqSensitivity.var"#kw##ODEAdjointProblem")(::NamedTuple{(:checkpoints, :abstol, :reltol),Tuple{Array{Float64,1},Float64,Float64}}, ::typeof(ODEAdjointProblem), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::InterpolatingAdjoint{0,true,Val{:central}}, ::Function, ::StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}, ::Nothing) at ./none:0
 [3] #_adjoint_sensitivities#13(::Float64, ::Float64, ::Array{Float64,1}, ::Base.Iterators.Pairs{Symbol,Float64,Tuple{Symbol},NamedTuple{(:dt,),Tuple{Float64}}}, ::typeof(DiffEqSensitivity._adjoint_sensitivities), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::InterpolatingAdjoint{0,true,Val{:central}}, ::Euler, ::DiffEqSensitivity.var"#df#62"{Array{Float64,1}}, ::StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}, ::Nothing) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/sensitivity_interface.jl:13
 [4] (::DiffEqSensitivity.var"#kw##_adjoint_sensitivities")(::NamedTuple{(:dt,),Tuple{Float64}}, ::typeof(DiffEqSensitivity._adjoint_sensitivities), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::InterpolatingAdjoint{0,true,Val{:central}}, ::Euler, ::Function, ::StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}, ::Nothing) at ./none:0 (repeats 2 times)
 [5] #adjoint_sensitivities#12(::InterpolatingAdjoint{0,true,Val{:central}}, ::Base.Iterators.Pairs{Symbol,Float64,Tuple{Symbol},NamedTuple{(:dt,),Tuple{Float64}}}, ::typeof(adjoint_sensitivities), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::Euler, ::Vararg{Any,N} where N) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/sensitivity_interface.jl:6
 [6] (::DiffEqSensitivity.var"#kw##adjoint_sensitivities")(::NamedTuple{(:sensealg, :dt),Tuple{InterpolatingAdjoint{0,true,Val{:central}},Float64}}, ::typeof(adjoint_sensitivities), ::ODESolution{Float64,1,Array{Float64,1},Nothing,Nothing,Array{Float64,1},Array{Array{Float64,1},1},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,var"#dudt#8",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{Float64,1},Array{Float64,1},Array{Array{Float64,1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats}, ::Euler, ::Vararg{Any,N} where N) at ./none:0
 [7] (::DiffEqSensitivity.var"#adjoint_sensitivity_backpass#61"{Euler,InterpolatingAdjoint{0,true,Val{:central}},Float64,Array{Float32,1},Tuple{}})(::Array{Float64,1}) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/concrete_solve.jl:69
 [8] #553#back at /Users/Riccardo/.julia/packages/ZygoteRules/6nssF/src/adjoint.jl:55 [inlined]
 [9] odeN at ./REPL[13]:6 [inlined]
 [10] (::typeof(∂(odeN)))(::Array{Float64,1}) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface2.jl:0
 [11] (::typeof(∂(#9)))(::Float64) at ./REPL[14]:1
 [12] #16 at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:24 [inlined]
 [13] (::typeof(∂(λ)))(::Float64) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface2.jl:0
 [14] (::Zygote.var"#46#47"{Zygote.Params,Zygote.Context,typeof(∂(λ))})(::Float64) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface.jl:101
 [15] gradient(::Function, ::Zygote.Params) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface.jl:47
 [16] macro expansion at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:23 [inlined]
 [17] macro expansion at /Users/Riccardo/.julia/packages/Juno/oLB1d/src/progress.jl:134 [inlined]
 [18] #sciml_train!#13(::Function, ::Int64, ::typeof(DiffEqFlux.sciml_train!), ::var"#9#10", ::Array{Float32,1}, ::ADAM) at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:22
 [19] (::DiffEqFlux.var"#kw##sciml_train!")(::NamedTuple{(:maxiters, :cb),Tuple{Int64,var"#11#12"}}, ::typeof(DiffEqFlux.sciml_train!), ::Function, ::Array{Float32,1}, ::ADAM) at ./none:0
 [20] top-level scope at REPL[18]:2

I can easily solve this by wrapping u0 in an array in the return of odeN(par) and removing the final [1] indexing in the return of dudt(u, p, t) (as I will do in the next example with a different sensealg).
However, it is not clear to me why this comes up as an error, especially given odeN(p_nn) works just fine.
The second, more important, problem is that if I try to use sensealg = TrackerAdjoint() in odeN, it gives me an error about TrackedArray.
Also here what I find weird is that odeN works, but I cannot train the network:
function odeN(par)
    function dudt(u, p, t)
        return re_nn(p)([u[1]])
    end
    prob = ODEProblem{false}(dudt, u0, t_span, par)
    return Array(concrete_solve(prob, Euler(), [u0], par; sensealg = TrackerAdjoint(), dt = dt, saveat = t_range))
end
loss = θ -> sum(abs2, sim .- odeN(θ)[:])
l = loss(p_nn)
cb = (θ, l) -> println("Current loss:", l)

# this works:
loss(p_nn)

# this doesn't work:
DiffEqFlux.sciml_train!(loss, p_nn, ADAM(0.1), maxiters = 100, cb = cb)

ERROR: Not implemented: convert TrackedArray{…,Array{Tracker.TrackedReal{Float64},1}} to TrackedArray{…,Array{Float64,1}}
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] convert(::Type{TrackedArray{…,Array{Float64,1}}}, ::TrackedArray{…,Array{Tracker.TrackedReal{Float64},1}}) at /Users/Riccardo/.julia/packages/Tracker/cpxco/src/lib/array.jl:38
 [3] setproperty!(::OrdinaryDiffEq.ODEIntegrator{Euler,false,TrackedArray{…,Array{Float64,1}},Float64,TrackedArray{…,Array{Float32,1}},Float64,Float64,Float64,Array{TrackedArray{…,Array{Float64,1}},1},ODESolution{Tracker.TrackedReal{Float64},2,Array{TrackedArray{…,Array{Float64,1}},1},Nothing,Nothing,Array{Float64,1},Array{Array{TrackedArray{…,Array{Float64,1}},1},1},ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{TrackedArray{…,Array{Float64,1}},1},Array{Float64,1},Array{Array{TrackedArray{…,Array{Float64,1}},1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},OrdinaryDiffEq.EulerConstantCache,OrdinaryDiffEq.DEOptions{Tracker.TrackedReal{Float64},Tracker.TrackedReal{Float64},Float64,Float64,typeof(DiffEqBase.ODE_DEFAULT_NORM),typeof(LinearAlgebra.opnorm),CallbackSet{Tuple{},Tuple{}},typeof(DiffEqBase.ODE_DEFAULT_ISOUTOFDOMAIN),typeof(DiffEqBase.ODE_DEFAULT_PROG_MESSAGE),typeof(DiffEqBase.ODE_DEFAULT_UNSTABLE_CHECK),DataStructures.BinaryHeap{Float64,DataStructures.LessThan},DataStructures.BinaryHeap{Float64,DataStructures.LessThan},Nothing,Nothing,Int64,Array{Float64,1},StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}},Array{Float64,1}},TrackedArray{…,Array{Float64,1}},Tracker.TrackedReal{Float64},Nothing}, ::Symbol, ::TrackedArray{…,Array{Tracker.TrackedReal{Float64},1}}) at ./Base.jl:21
 [4] initialize!(::OrdinaryDiffEq.ODEIntegrator{Euler,false,TrackedArray{…,Array{Float64,1}},Float64,TrackedArray{…,Array{Float32,1}},Float64,Float64,Float64,Array{TrackedArray{…,Array{Float64,1}},1},ODESolution{Tracker.TrackedReal{Float64},2,Array{TrackedArray{…,Array{Float64,1}},1},Nothing,Nothing,Array{Float64,1},Array{Array{TrackedArray{…,Array{Float64,1}},1},1},ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,OrdinaryDiffEq.InterpolationData{ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Array{TrackedArray{…,Array{Float64,1}},1},Array{Float64,1},Array{Array{TrackedArray{…,Array{Float64,1}},1},1},OrdinaryDiffEq.EulerConstantCache},DiffEqBase.DEStats},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},OrdinaryDiffEq.EulerConstantCache,OrdinaryDiffEq.DEOptions{Tracker.TrackedReal{Float64},Tracker.TrackedReal{Float64},Float64,Float64,typeof(DiffEqBase.ODE_DEFAULT_NORM),typeof(LinearAlgebra.opnorm),CallbackSet{Tuple{},Tuple{}},typeof(DiffEqBase.ODE_DEFAULT_ISOUTOFDOMAIN),typeof(DiffEqBase.ODE_DEFAULT_PROG_MESSAGE),typeof(DiffEqBase.ODE_DEFAULT_UNSTABLE_CHECK),DataStructures.BinaryHeap{Float64,DataStructures.LessThan},DataStructures.BinaryHeap{Float64,DataStructures.LessThan},Nothing,Nothing,Int64,Array{Float64,1},StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}},Array{Float64,1}},TrackedArray{…,Array{Float64,1}},Tracker.TrackedReal{Float64},Nothing}, ::OrdinaryDiffEq.EulerConstantCache) at /Users/Riccardo/.julia/packages/OrdinaryDiffEq/nV9bA/src/perform_step/fixed_timestep_perform_step.jl:45
 [5] #__init#328(::StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}, ::Array{Float64,1}, ::Array{Float64,1}, ::Nothing, ::Bool, ::Bool, ::Bool, ::Bool, ::Nothing, ::Bool, ::Bool, ::Float64, ::Float64, ::Float64, ::Bool, ::Bool, ::Rational{Int64}, ::Nothing, ::Nothing, ::Rational{Int64}, ::Int64, ::Int64, ::Int64, ::Rational{Int64}, ::Bool, ::Int64, ::Nothing, ::Nothing, ::Int64, ::typeof(DiffEqBase.ODE_DEFAULT_NORM), ::typeof(LinearAlgebra.opnorm), ::typeof(DiffEqBase.ODE_DEFAULT_ISOUTOFDOMAIN), ::typeof(DiffEqBase.ODE_DEFAULT_UNSTABLE_CHECK), ::Bool, ::Bool, ::Bool, ::Bool, ::Bool, ::Bool, ::Bool, ::Int64, ::String, ::typeof(DiffEqBase.ODE_DEFAULT_PROG_MESSAGE), ::Nothing, ::Bool, ::Bool, ::Bool, ::Bool, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}}, ::typeof(DiffEqBase.__init), ::ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler, ::Array{TrackedArray{…,Array{Float64,1}},1}, ::Array{Float64,1}, ::Array{Any,1}, ::Type{Val{true}}) at /Users/Riccardo/.julia/packages/OrdinaryDiffEq/nV9bA/src/solve.jl:383
 [6] (::DiffEqBase.var"#kw##__init")(::NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}, ::typeof(DiffEqBase.__init), ::ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler, ::Array{TrackedArray{…,Array{Float64,1}},1}, ::Array{Float64,1}, ::Array{Any,1}, ::Type{Val{true}}) at ./none:0 (repeats 4 times)
 [7] #__solve#327 at /Users/Riccardo/.julia/packages/OrdinaryDiffEq/nV9bA/src/solve.jl:4 [inlined]
 [8] #__solve at ./none:0 [inlined]
 [9] #solve_call#442(::Base.Iterators.Pairs{Symbol,Any,Tuple{Symbol,Symbol},NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}}, ::typeof(DiffEqBase.solve_call), ::ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler) at /Users/Riccardo/.julia/packages/DiffEqBase/YIwj5/src/solve.jl:40
 [10] #solve_call at ./none:0 [inlined]
 [11] #solve#443 at /Users/Riccardo/.julia/packages/DiffEqBase/YIwj5/src/solve.jl:57 [inlined]
 [12] (::DiffEqBase.var"#kw##solve")(::NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}, ::typeof(solve), ::ODEProblem{TrackedArray{…,Array{Float64,1}},Tuple{Float64,Float64},false,TrackedArray{…,Array{Float32,1}},ODEFunction{false,DiffEqSensitivity.var"#_f#84"{ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}},LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler) at ./none:0
 [13] (::DiffEqSensitivity.var"#tracker_adjoint_forwardpass#83"{Base.Iterators.Pairs{Symbol,Any,Tuple{Symbol,Symbol},NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,Tuple{}})(::TrackedArray{…,Array{Float64,1}}, ::TrackedArray{…,Array{Float32,1}}) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/concrete_solve.jl:172
 [14] #20 at /Users/Riccardo/.julia/packages/Tracker/cpxco/src/back.jl:148 [inlined]
 [15] forward(::Tracker.var"#20#22"{DiffEqSensitivity.var"#tracker_adjoint_forwardpass#83"{Base.Iterators.Pairs{Symbol,Any,Tuple{Symbol,Symbol},NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}},ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem},Euler,Tuple{}}}, ::Tracker.Params) at /Users/Riccardo/.julia/packages/Tracker/cpxco/src/back.jl:135
 [16] forward(::Function, ::Array{Float64,1}, ::Array{Float32,1}) at /Users/Riccardo/.julia/packages/Tracker/cpxco/src/back.jl:148
 [17] #_concrete_solve_adjoint#81(::Base.Iterators.Pairs{Symbol,Any,Tuple{Symbol,Symbol},NamedTuple{(:dt, :saveat),Tuple{Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}}, ::typeof(DiffEqBase._concrete_solve_adjoint), ::ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler, ::TrackerAdjoint, ::Array{Float64,1}, ::Array{Float32,1}) at /Users/Riccardo/.julia/packages/DiffEqSensitivity/9ybQN/src/local_sensitivity/concrete_solve.jl:182
 [18] #_concrete_solve_adjoint at ./none:0 [inlined]
 [19] #adjoint#452 at /Users/Riccardo/.julia/packages/DiffEqBase/YIwj5/src/solve.jl:210 [inlined]
 [20] #adjoint at ./none:0 [inlined]
 [21] _pullback(::Zygote.Context, ::DiffEqBase.var"#kw##concrete_solve", ::NamedTuple{(:sensealg, :dt, :saveat),Tuple{TrackerAdjoint,Float64,StepRangeLen{Float64,Base.TwicePrecision{Float64},Base.TwicePrecision{Float64}}}}, ::typeof(concrete_solve), ::ODEProblem{Float64,Tuple{Float64,Float64},false,Array{Float32,1},ODEFunction{false,var"#dudt#18",LinearAlgebra.UniformScaling{Bool},Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing},Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{,Tuple{}}},DiffEqBase.StandardODEProblem}, ::Euler, ::Array{Float64,1}, ::Array{Float32,1}) at /Users/Riccardo/.julia/packages/ZygoteRules/6nssF/src/adjoint.jl:53
 [22] odeN at ./REPL[25]:6 [inlined]
 [23] _pullback(::Zygote.Context, ::typeof(odeN), ::Array{Float32,1}) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface2.jl:0
 [24] #19 at ./REPL[26]:1 [inlined]
 [25] _pullback(::Zygote.Context, ::var"#19#20", ::Array{Float32,1}) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface2.jl:0
 [26] #16 at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:24 [inlined]
 [27] _pullback(::Zygote.Context, ::DiffEqFlux.var"#16#22"{var"#19#20",Array{Float32,1}}) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface2.jl:0
 [28] pullback(::Function, ::Zygote.Params) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface.jl:96
 [29] gradient(::Function, ::Zygote.Params) at /Users/Riccardo/.julia/packages/Zygote/tJj2w/src/compiler/interface.jl:46
 [30] macro expansion at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:23 [inlined]
 [31] macro expansion at /Users/Riccardo/.julia/packages/Juno/oLB1d/src/progress.jl:134 [inlined]
 [32] #sciml_train!#13(::Function, ::Int64, ::typeof(DiffEqFlux.sciml_train!), ::var"#19#20", ::Array{Float32,1}, ::ADAM) at /Users/Riccardo/.julia/packages/DiffEqFlux/ltHvf/src/train.jl:22
 [33] (::DiffEqFlux.var"#kw##sciml_train!")(::NamedTuple{(:maxiters, :cb),Tuple{Int64,var"#21#22"}}, ::typeof(DiffEqFlux.sciml_train!), ::Function, ::Array{Float32,1}, ::ADAM) at ./none:0
 [34] top-level scope at REPL[30]:2

By the way, I'm on Julia 1.3, and packages are<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Hey,
I haven't been ignoring this, just hoping that the interface changes would help out some of this, and then taking the time to dig through your issue. So sorry for the late response!

What I find especially weird is that I can solve the neural ODE, but I cannot train the network.

The adjoint right now requires using in-place differential equations (Xref: https://github.com/JuliaDiffEq/DiffEqSensitivity.jl/issues/113 ). This can be fixed, but it's an extreme edge case where you want to use a Number or StaticArray in something that makes sense to use an adjoint with. Doesn't mean it doesn't make sense though, but that's why it hasn't been prioritized. The fact that f(u,p,t) (out of place) with arrays works in adjoints is somewhat of a nice hack that's useful for neural ODEs, but it can only work with mutable objects (like arrays).
The second one... I gotta run it to see.

Tracker just has funny semantics sometimes. That's why we are trying to phase out the use of it, though right now indeed you need it for SDEs. You just have to be careful that scalar indexing produces a TrackedReal so [u[1]] is not the same as u here. The next issue is that some things were Float32 and others were Float64, which makes Tracker mad. Working code on the latest versions for this is as follows:
using OrdinaryDiffEq, DiffEqFlux, DiffEqSensitivity, Flux

u0 = Float32(1/2)

datasize = 30
t_span = (t_min, t_max) = (0f0, 1f0)
t_range = range(t_min, t_max, length = datasize)
dt = (t_max - t_min)/datasize

true_ode(u, p, t) = Float32(1.01)*u

prob = ODEProblem{false}(true_ode, u0, t_span)
sol = solve(prob, Tsit5(); dense = true)
sim = sol(t_range)

nn = Chain(Dense(1, 16, softplus),
                 Dense(16, 1))

p_nn, re_nn = Flux.destructure(nn)

function odeN(par)
    function dudt(u, p, t)
        return re_nn(p)(u)
    end
    prob = ODEProblem{false}(dudt, u0, t_span, par)
    return Array(concrete_solve(prob, Euler(), [u0], par; sensealg = TrackerAdjoint(), dt = dt, saveat = t_range))
end
loss = θ -> sum(abs2, sim .- odeN(θ)[:])
l = loss(p_nn)
cb = (θ, l) -> (println("Current loss:", l); false)
loss(p_nn)
DiffEqFlux.sciml_train(loss, p_nn, ADAM(0.1), maxiters = 300, cb = cb)

Let me know if you need any more help. Now to go implement SDE adjoints so we can stop recommending TrackerAdjoint 👍


support for response-filtering ?

Which version of Elastic are you using?
[ ] elastic.v2 (for Elasticsearch 1.x)
[X ] elastic.v3 (for Elasticsearch 2.x)
[X ] elastic.v5 (for Elasticsearch 5.x)
Please describe the expected behavior
elastic.v5 and elastic.v3 supports all the features defined in the Elasticsearch HTTP API
Please describe the actual behavior
It is not possible to add a response-filtering to the query.

I browsed your code and it should be fairly easy to append the filter_path URL param in search.go file

Thanks for reporting. It's next to impossible to implement all features defined in the ES API. But I try my best.
Yes, it'd be easy for searching which is probably the 99% use case of filter_path. But as it's a common API setting, so we probably need to implement it for every request. I'll see if that's possible without too many problems.

Thanks @olivere .
I am using elasticearch with libbeat to aggregate metrics.
By using filter_path, I can reduce the size of the HTTP response body by filtering the results of sub-aggregations

I added source filtering to the Search API for v3 and v5 in v3.0.65 and v5.0.21 respectively.


improvementadd some description for show create

Proposed changes

add location and properties for show create table.
add location for show create database.

run buildall


Feature/3440 hero playground

Changes proposed in this Pull Request:

Add Hero Playground

There's no prefix property for the Hero API?
Everything else looks good

There's no prefix property for the Hero API?

Looking at the source it doesn't look there there is.   It's on ChannelValue but not on the Hero.  Sounds like a +1 issue.

Add a new issue here: https://github.com/brightlayer-ui/angular-component-library/issues/501


[SPARK-27272][CORE] Enable blacklisting of node/executor on fetch failures by default

What changes were proposed in this pull request?
SPARK-20898 added a new configuration to blacklist a node/executor on fetch
failures. This config was deemed risky at the time and was disabled by default
until more data is collected.
This commit aims to enable that feature by default as we have seen couple of
instances where that feature was found to be useful. Additionally, the commit
changes the blacklist criteria slightly.
If external shuffle service is not enabled, the commit will blacklist the
executor immediately (on first fetch failure). This is consistent with the fact
that we delete all the shuffle outputs on that executor. So, I think it is
useful that we also blacklist that executor temporarily.
Otherwise, if external shuffle service is enabled, instead of blacklisting the
node immediately, it keeps track of all such fetch failures on that node. If
unique and active fetch failures on that node exceed the configured threshold
(it re-uses MAX_FAILED_EXEC_PER_NODE, but can be changed), then the node is also
blacklisted. This will ensure that persistent issues with a node do not lead to
job failures.
How was this patch tested?

Added a unit test case to ensure that blacklisting works as configured

Can one of the admins verify this patch?

Can one of the admins verify this patch?

cc @squito @tgravescs

Test build #103923 has started for PR 24208 at commit 209c2cf.

I'm definitely good turning it on by default, you added the extra config and tracking because you saw instances the current version is to aggressive?  If so can you give details.   Right now it blacklists immediately because you get a stage failure immediately.  I can see reasons to make this configurable but  I'm not seeing how that ties into the config MAX_FAILED_EXEC_PER_NODE, which is at the application level not the stage level.

I do not have any instances where the current version is too aggressive but I think that can be a case in some instances. So, I think it may be useful to track the failures before blacklisting a node.
I realize that MAX_FAILED_EXEC_PER_NODE is at the application level and I want to keep it that way, as there is a possibility that we may not observe another fetch failure from the same stage but we may get it from another stage or another stage attempt (this was observed in my situation).

Test build #103923 has finished for PR 24208 at commit 209c2cf.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103923/
Test FAILed.

Test build #103931 has started for PR 24208 at commit 9751318.

Test build #103931 has finished for PR 24208 at commit 9751318.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103931/
Test PASSed.

I guess I'm not sure I agree with tying the fetch failure count to the same config as MAX_FAILED_EXEC_PER_NODE.  I can see someone wanting that to stay the same but be more aggressive on the fetch failures.
I used to run with the config on all the time at Yahoo where it did it immediately, never saw any issues with it that people reported but that doesn't mean it wasn't to aggressive since generally we had very large clusters.  @abellina have you seen any issues with this being on?
If we don't have any data with needing it perhaps we leave it as is now, the customers out is they just turn it back off and if people report it to aggressive then at that point we add a new config, what do you think?

Test build #103983 has started for PR 24208 at commit a4c77c7.

Thanks for your review @tgravescs
I just added another config MAX_FETCH_FAILURES_PER_NODE. So, this way users can choose to be more aggressive on fetch failures.
I think without this configuration, it can be too aggressive on smaller clusters, especially one with beefy nodes, where each node has many executors running but there are very few nodes overall.
If you still think we do not need this configuration, then I can remove it altogether.

I feel the same as Tom --I'm in favor of turning it on by default, but not sure about the extra config.  Given that the scheduler still treats all map output as missing on the node after one fetch failure, it seems inconsistent to have this part configurable, unless we have a case supporting it.  (If its going to be true by default, I think we should remove "experimental" from the docs in the configuration.md also).
Separately, do you have any opinions on turning blacklisting on by default?  maybe we should start a discussion on dev@ to get more input on that.  Its been working for us for a while now, and seems critical for large clusters, so I think it would be good.

Test build #103987 has started for PR 24208 at commit 4e77e5d.

Thanks for the review @squito !
I have removed the additional logic and configuration and changed the PR to just enable blacklisting for fetch failure to on by default. As @tgravescs suggested, we can add that logic later on, if needed.
I also wanted to check if we should enable spark.files.fetchFailure.unRegisterOutputOnHost by default (added in SPARK-19753). This ensures that not only is the host blacklisted but all the files on that host are deleted.
@squito , I also agree with turning blacklisting on by default.

Test build #103983 has finished for PR 24208 at commit a4c77c7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103983/
Test PASSed.

Test build #103987 has finished for PR 24208 at commit 4e77e5d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103987/
Test PASSed.

Let me start an email thread where we can discuss which blacklisting configurations seem stable now and should be enabled by default.

Thanks for the work. The description said there was a added unit test, but it isn't included in the changed files. Did you decide to remove it?

Yes, the PR body is not up-to-date. The PR just updates the config now, as mentioned in this comment above: https://github.com/apache/spark/pull/24208#issuecomment-476788386

Sorry -1 on this. See my comment on the dev list thread.

Thanks for the review @rxin!
Actually, this is a slightly different change than what I proposed in the dev thread. It enables blacklisting on fetch failure if general blacklisting feature is enabled. The general blacklisting feature (controlled by spark.blacklisting.enabled) is still disabled by default.

Ah got it. Thanks for explaining. What's the behavior if this is false? Do we just treat fetch failure as a normal failure?

If this is false, there is a possibility that map task can be retried on the same executor/node multiple times and then, reduce stage retries max times before failing the job.
Overall, this seems to be an essential feature of blacklisting, to ensure executor/nodes are blacklisted if there are fetch failures originating from that executor/node.

Makes sense. Thanks for explaining!

Test build #104167 has started for PR 24208 at commit 65f2eca.

Test build #104167 has finished for PR 24208 at commit 65f2eca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104167/
Test PASSed.

Retest this please.

Test build #108790 has started for PR 24208 at commit 65f2eca.

Test build #108790 has finished for PR 24208 at commit 65f2eca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108790/
Test PASSed.

thanks as is looks good to me, I think the discussion on dev didn't want blacklisting in general on by default but this is now just turning on the fetch failures handling by default and you still have to enable blacklisting to get it.  @rxin just to confirm you are ok with this?

Retest this please.

Test build #110326 has started for PR 24208 at commit 65f2eca.

Hi, All. Can we make a final decision on this PR from @ankuriitg ?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15318/
Test PASSed.

Test build #110326 has finished for PR 24208 at commit 65f2eca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110326/
Test PASSed.

Can one of the admins verify this patch?

Looks like this got two +1s but stuck with -1. Origin concern seemed to be resolved but the veto didn't get rid.
@rxin Shall we cancel the veto if you're OK with the explanation?

Sorry didn't get to this earlier. Do we ever release a node from blacklist? I'm asking because it'd be bad if a transient network error immediately blacklists all the nodes. It'd make sense if it blacklists after a few fetch failures, or if the blacklist is automatically released after a while.


CLI output on multiple lines when resizing the terminal

Which version of kubefirst are you using?
2.0.8
Which installation type?
None specific
Which distributed Git provider?
None specific
What is the issue?
When you start a command creating some output long enough for you to resize the terminal width while there are still output from the command, it starts to display on multiple lines, instead of updating the actual line as it's default behavior.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

It won't be an issue anymore as the revamp of the CLI will use the API instead of its own code.


macOS touchbar RUN option missing

Issue Type: Bug
Latest stable version of AzureDataStudio
When you open a script (.SQL) the RUN option was there on the macOS TouchBar.
In the latest version if you click in the script window, the option goes missing from the TouchBar.
If you run the script by pressing F5 or Run icon and then click in the bottom pane, the Touch Bar shows the same.
See the attached images.
Similar issue was there VSCode https://github.com/microsoft/vscode/issues/123105
Azure Data Studio version: azuredatastudio 1.30.0 (59c4b8e90cf2d3a24bed72623197f10f8d090fdc, 2021-06-16T18:57:01.467Z)
OS version: Darwin x64 20.5.0

@Abhijit-Revamp Does this still repro with the latest insiders build?

Yes. Its repro on
Version: 1.31.0-insider
Commit: 5fa53c3519eb0ad6b6b4fd815a2336133cc1fb99
Date: 2021-06-29T05:49:12.638Z (2 days ago)
VS Code: 1.56.0
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.5.0

Hi @Abhijit-Revamp, I was not able to repro this issue on main or insiders build. Does this happen for both new untitled sql files and saved sql files?

It happens on both saved and untitled files.

@lucyzhang929 Are you focusing in the editor? (maybe try typing some text too) That's one of the things mentioned in https://github.com/microsoft/vscode/issues/106541 to repo the issue

Yep I can still see the Run Query button in the touch bar when I'm typing. (both main and insiders)

Interesting...ok well I have a PR out for pulling over the fix VS Code did (basically just bump the Electron version to get a fixed version there) so we'll probably just get that in and then see if it still repros on the insiders build once that goes out. I'll update here once that happens.

awesome.
Thanks

Yep I can still see the Run Query button in the touch bar when I'm typing. (both main and insiders)

I know when this works. If you are in Explorer view then it works. In all other views, it breaks.

@Abhijit-Revamp The latest insiders build has my fix, when you get a chance could you test it out and see if it fixes the issue for you?

@Charles-Gagnon
Bingo. Now the "Run Query" option is continuously available irrespective of which window pane I click.
And its visible even when I am typing in the editor
Thanks a lot

Thanks for the confirmation! And thanks for finding that VS Code issue, definitely made this a lot easier to track down 😄


Fixed endpoint group behavior on collapsing of the node.

When collapsing a node endpoints of an endpoint group were vanishing even if they were connected. Fixed the issue. Added test and fixed another.

Excellent work, thanks!


error in display of call out note in Missing values: Exercises

this page seems incomplete - just writing it down in case you forget


[ENHANCEMENT] Revamp project page

Description
Revamping project page to the design selected. The dashboard listing has been replaced by MUI DataGrid component allowing user to search, to filter and to sort items easily.
Images
Project page

Home page

Checklist

[x] Pull request has a descriptive title and context useful to a reviewer.
[x] Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, IGNORE.
[x] All commits have DCO signoffs.
[x] Changes that impact the UI include screenshots and/or screencasts of the relevant changes.

Oh wow, I like the datetime picker in datagrid, we're going to update the absolute timepicker UX on dashboards to look similar

Could change the cursor to 'pointer' on hover, just so it's extra clear that clicking takes you to the dashboard:

nit: not sure where the blue border is being set, but looks a little odd:

A lot of white space when a project doesn't have many dashboards, maybe it could grow as more dashboards are added? So more projects are visible at a time:

Oh so cool! You can even control the columns, and rename/delete from the 'Recently Visited' list:

@Nexucis I pulled this locally and it looks amazing! Do you want to take a pass too for any UX feedback or testing for bugs (I didn't do a ton of this, just clicked around quickly)?

nit: not sure where the blue border is being set, but looks a little odd (if it's just a default MUI setting it's probably fine to leave):

MUI default setting, I still removed it with cursor on hover style change. It should be better now ✌

A lot of white space when a project doesn't have many dashboards, maybe it could grow as more dashboards are added? So more projects are visible at a time:

I first thought DataGrid couldn't have a auto height depending on visible rows. But it's available, changed! (screens updated too) 😅

Adding some tests here would be great specially since it is adding a tons of (great) code.

@foxbat07 FYI the design you made is alive :)


Add readCursor to Pool.DB

Issue Number
#713
Overview

[x] I have added readCursor to Pool.DB such that we can resume restoration from the node.

Comments

bors r+


Migrate '/' division operator to use math.div() and list.slash() instead

Migrated using https://github.com/sass/migrator.
More info at https://sass-lang.com/documentation/breaking-changes/slash-div.

Thanks! It looks like math.div is available starting at v1.33, and this project is still at v1.32 (making this a breaking change). You'll need to upgrade the sass npm dependency to address that.
For linting, you can run yarn fix to apply prettier.

Woops, thank you for catching that. I think fixed the dependency (is it bad practice to set the dependency at a later version than is minimally needed?) and Prettified it.

is it bad practice to set the dependency at a later version than is minimally needed?

Nah, not in my opinion for this. Since it's a dev dependency here it won't actually affect anyone using the package. The actual sass changes will still work back to the oldest supported version.
This package currently doesn't actually do anything to inform the user about sass compatibility. There's not really a way to do this in an automated fashion though. For normal dependencies you can use peerDependencies, but in this case that would require sass in the production dependency set, which is usually wrong (we'd need peerDevDependencies).
It's probably worth adding the minimum supported sass version to the readme, though I wouldn't consider it a blocking thing for this PR. We could even modify and expand the tests to test on old versions of sass, though that might be overkill.

Minimum supported Sass version

Sass Compiler
Version

Dart Sass
1.33.0

LibSass
?

Ruby Sass
?


Fix #74 Add TreeExpansionListener to expand descendant tree nodes with only one member

Implements the automatic expansion of package tree nodes if they contain only one descendant by adding a TreeExpansionListener to the package tree.
This feature is explained in Ticket #74  .

This looks great. Thanks for your contribution.


Release notes for 1.69.0

Need to collect them and submit.

trac-7364, trac-5419: Avoid conversion to Container's Allocator. (#29)
trac-10477: rvalue reference, perfect forwarding and variadic template support (#6)


include a listing of the fulfilled create transaction in the handcrafting instructions

As asked by @mgrand on gitter:

One simple thing that would be very helpful is to include a listing of the fulfilled create transaction in the handcrafting instructions.

Closing as it was added via #263 : https://docs.bigchaindb.com/projects/py-driver/en/master/handcraft.html#the-fulfilled-transaction


Articles: add Go coding guide plus update url for hardening guide

This change adds under "Articles", a new URL for a suggested Go coding guide at https://cyber.orijtech.com/scsec/cosmos-go-coding-guide as well as updates the hardening guide at https://cyber.orijtech.com/scsec/cosmos-hardening

/cc @julienrbrt


Adapt WebIDL parser to new output of webidl2 parser

Currently, crawl.json doesn't include any WebIDL parsed data because the object model coming out the new version WebIDL2.js is incompatible with the existing code.
This change adapts to some of the changes I detected when running parse-webidl.js on the WebRTC spec

Actually, I do see weird outputs in crawl.json such as occurrences of [object Object] and JSON structures where simple names are expected but the updates in that PR don't fix them and actually break IDL parsing on my end.

See adjustments I made for parsing of Global and Exposed in: https://github.com/tidoust/reffy/commit/56dab23a6213a75a77cac6e292dff1c51bb543c0

Hmm, the WebIDL parser fails to parse WebIDL content when Reffy is run on the W3C server. I don't have the same result when I run Reffy locally. Could it be that npm install (needed to update webidl2) did not run on the server, @dontcallmedom ?

re-run with a cleaned up checkout - does it produce your expected output?

Yup! When you have time, can you confirm that this pull request is no longer needed?


[Feature] Add Bulk Pin

Is it be possible to add a feature to select multiple messages to pin at once ?

I just release v1.0.2 which include that 🎉


[operations] Implement process_attestation

https://github.com/lambdaclass/lambda_ethereum_consensus/blob/dd0a0523e6be2a21fa3f6a96d4466926307d236c/docs/specs/beacon-chain.md?plain=1#L2761-L2795
See Spec tests format: https://github.com/ethereum/consensus-specs/tree/dev/tests/formats/operations
Acceptance criteria:

Run corresponding spec tests

Can I take this?

Sure assigned

I would also recommend going through this handbook before starting your implementation: https://github.com/lambdaclass/lambda_ethereum_consensus/pull/295/files
PS: open the graph and let me know what you think / if it's useful to you

@sm-stack how is it going with this issue, are you able to go forward ?

As you can see this is not the easiest implementation, I might cut down on the task and start with implementations of helper functions first before going into the full function.

@sm-stack how is it going with this issue, are you able to go forward ?

Thanks for checking in. Currently implementing a few helper functions at accessors.ex and predicates.ex. I have a 2 question about implementation, which is

Where can I get DOMAIN_BEACON_ATTESTER? I need that when implementing get_beacon_committee, and maybe I add it to the config?
Could I generate operations.ex at lib/lambdaclass_ethereum_consensus/state_transition for process_attestation function, or should it be at different path?

As you can see this is not the easiest implementation, I might cut down on the task and start with implementations of helper functions first before going into the full function.

Also that will be great. I'm working on the helper functions now, so will focus on implementing them first if you do so.

For 1, you should do like #309 and declare them in the Constants module: https://github.com/lambdaclass/lambda_ethereum_consensus/blob/acb74b5544f3a18ec7529808c72805c0513489ef/lib/constants.ex

@sm-stack how is it going with this issue, are you able to go forward ?

Thanks for checking in. Currently implementing a few helper functions at accessors.ex and predicates.ex. I have 2 questions about implementation, which is

Where can I get DOMAIN_BEACON_ATTESTER? I need that when implementing get_beacon_committee, and maybe I add it to the config?
Could I generate operations.ex at lib/lambdaclass_ethereum_consensus/state_transition for process_attestation function, or should it be at different path?

As you can see this is not the easiest implementation, I might cut down on the task and start with implementations of helper functions first before going into the full function.

Also that will be great. I'm working on the helper functions now, so will focus on implementing them if you do so.

Absolutely you should generate a operations.ex file at the location you pointed.


Update secor.prod.properties

To clarify this issue https://github.com/pinterest/secor/issues/267

Thanks for the contribution.


fix(deps<EMAIL_ADDRESS>

This synchronizes the licensing changes for the packages to MIT as well as the node version support.
Version 4 of genfun uses the CC0-1.0 license which is preventing the Angular CLI from using pacote.
/cc @zkat

@zkat Just a friendly ping.  The Angular CLI team would very much like to use pacote.  However, the licensing issue with the old version of genfun is currently preventing us from doing so.  Can you take a look at this when you have some time?  Thank you.


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Thank you Google for such a good lab.


used vs2010 complice for eeror:

Hi, When I use VS to compile the following error
fatal error C1083: 无法打开包括文件:“allheaders.h”: No such file or directory
Excuse me is the reason?

You forget to read instructions ;-)

Use latest installer for windows from
https://github.com/UB-Mannheim/tesseract/wiki
ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com
On Thu, Sep 1, 2016 at 2:18 PM, zdenop<EMAIL_ADDRESS>wrote:

You forget to read instructions ;-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/407#issuecomment-244015951,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_oxnScEQkuJqWz09xxrQbjZPSjBmkks5qlpFCgaJpZM4Jyc9o
.


Issue with xADGroup when using MembersToInclude

We've been using the xADGroup resource for some time without an issue.  I saw with the latest version 2.10 that we could use the resource to add/remove members to the group as well.  The issue is when we try to add members to the group we get an error saying the group already exists.  Looking into the logs, the test resource successfully shows there are missing members in the group which then moves to the set resource. The set resource sees there are missing members, adds the missing members but kicks back a warning saying the group was not found, tries to great the group and errors out saying the specified group already exists.  Here is the snippet of the log so you can see what is happening:
##########################################################################
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]: LCM:  [ Start  Resource ]  [[xADGroup]SessionHosts]
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]: LCM:  [ Start  Test     ]  [[xADGroup]SessionHosts]
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Retrieving group
membership based on 'SamAccountName' property.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Checking for
'Included' members.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Member 'rd-stan-01'
is not in the desired state.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Group membership is
NOT in the desired state.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]: LCM:  [ End    Test     ]  [[xADGroup]SessionHosts]  in 0.3430 seconds.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]: LCM:  [ Start  Set      ]  [[xADGroup]SessionHosts]
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Updating AD Group
'SessionHosts'
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Retrieving group
membership based on 'SamAccountName' property.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Checking for
'Included' members.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Member 'rd-stan-01'
is not in the desired state.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Adding '2' member(s)
to AD group 'SessionHosts'.
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] AD Group
'SessionHosts' was not found
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]:                            [[xADGroup]SessionHosts] Adding AD Group
'SessionHosts'
VERBOSE: [2016-04-24T15:40:40] [ERROR] The specified group already exists
VERBOSE: [2016-04-24T15:40:40] [VERBOSE] [DC-STAN-01]: LCM:  [ End    Set      ]  [[xADGroup]SessionHosts]  in 1.0940 seconds.
VERBOSE: [2016-04-24T15:40:40] [ERROR] The PowerShell DSC resource '[xADGroup]SessionHosts' with SourceInfo
'C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\ConfigDcServer.0\ConfigDC.ps1::362::13::xADGroup' threw one or
more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel
called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.
#############################################################################
We're passing the resource a variable which is an array of users to add to the group.  The MOF file seems to correctly handle the array so I guess the real question is what is the format for adding/removing multiple users when using the Members/MembersToInclude/MembersToRemove?  Here is what my MOF file is showing for the resource:
instance of MSFT_xADGroup as $MSFT_xADGroup3ref
{
ResourceID = "[xADGroup]SessionHosts";
Path = "OU=SessionHosts,OU=xServers,DC=some,DC=domain,DC=com";
Credential = $MSFT_Credential15ref;
Ensure = "Present";
Category = "Security";
MembersToInclude = {
"rd-stan-01",
"rd-stan-02"
};
SourceInfo = "C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\ConfigDcServer.0\ConfigDC.ps1::362::13::xADGroup";
GroupScope = "Global";
GroupName = "SessionHosts";
ModuleName = "xActiveDirectory";
ModuleVersion = "<IP_ADDRESS>";
DependsOn = {
"[xADOrganizationalUnit]SessionHosts",

 "[Script]AddSessionHostComputerObjects"};

ConfigurationName = "ConfigDC";
};
Let me know if the format of the MembersToInclude is correct or if we need to pass this in a different way.  Thanks!

@gmatusko It looks like the Test method finds the group and determines that the membership is incorrect. Looking at the verbose output, it looks like the Set method doesn't find the group and tries to recreate it.
However, I don't think this is the issue. I'm guessing rd-stan-01 is a computer account? If this is the case you need to specify rd-stan-01$. Can you confirm this works?

@iainbrighton you are correct.  I'm trying to add computer objects to a group and forgot the samAccountName includes the $.  I've modified my array to include the computer name with a $ and all seems to be working as it should.  Thanks for helping me out on this one.

No problem! It is reporting the wrong error though as it says the group doesn't exist, not the AD member doesn't exist. I'll fix this to make it clearer in future :)


Fix the command for checking port on macOS in server docs

The original netstat command is not working on macOS, I change it to lsof for a better output.
Continues #4343

From my understanding, lsof is not available by default on MacOS. What is failing in the netstat command, can the options be changed?

What is failing in the netstat command, can the options be changed?

The -p option means protocol on macOS, and there isn't a -t option:
$ netstat -nlp | grep 5000
netstat: option requires an argument -- p
Usage:	netstat [-AaLlnW] [-f address_family | -p protocol]
	netstat [-gilns] [-f address_family]
	netstat -i | -I interface [-w wait] [-abdgRtS]
	netstat -s [-s] [-f address_family | -p protocol] [-w wait]
	netstat -i | -I interface -s [-f address_family | -p protocol]
	netstat -m [-m]
	netstat -r [-Aaln] [-f address_family]
	netstat -rs [-s]

It should be:
$ netstat -anlp tcp | grep 5000
tcp4       0      0  <IP_ADDRESS>.5000         *.*                    LISTEN
tcp6       0      0  *.5000                 *.*                    LISTEN
tcp4       0      0  *.5000                 *.*                    LISTEN

But it didn't show the process name or PID, so I think it's better to use lsof.

From my understanding, lsof is not available by default on MacOS.

From this answer:

lsof has been available since OS X 10.5 (2007). From the manual page :

Lsof  revision 4.87 lists on its standard output file information about
files opened by processes for the following UNIX dialects:

Apple Darwin 9 and Mac OS X 10.[567]

Oops, the typo fix from 2.0.x was overwritten. I will rebase it later.

Which typo? I was about to merge this.

got -> go in this line.

Never mind, I found it, I'll fix it.


Corrected an issue with double Spring contexts.

When initializing DXA, two Spring context is actually created, one through the context listener (reading all META-INF/spring-context.xml files) and through the SpringConfiguration class (using @Configuration annotation). I've corrected it so only one context is created and shared between the context listener and the MVC dispatcher servlet.

Closing this PR in favour of the pull request #10


chore(v2): bump react-waypoint from 9.0.2 to 10.1.0

Motivation
Resolves #4913
Fixes following warning during @docusaurus/plugin-ideal-image installing:

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
E2E test.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

@slorber Being this is a blocker, may I ask an estimated release date for this fix?

LGTM thanks
@praveen4463 we have a @canary npm dist tag if you want to use the fix right now before the next release


To generate fixed-size images

I want to generate fixed width and height image. Could you please tell me where I should make modification?

The image obtained here is fixed height, you can padding to fixed width


Binding documentation needed for Alicloud Object Storage (OSS)

This OSS component needs docs https://github.com/dapr/components-contrib/tree/master/bindings/alicloud/oss
Overview of AliCloud OSS here
https://www.alibabacloud.com/product/oss?spm=a2c63.p38356.879954.30.3ede5922W645OH
To Do

This page needs updating for overview https://docs.dapr.io/operations/components/setup-bindings/supported-bindings/
Create a new HowTo page like this https://docs.dapr.io/operations/components/setup-bindings/supported-bindings/blobstorage/ that describes how to use the components

@madhugilla - Could you provide docs for OSS https://github.com/dapr/components-contrib/tree/master/bindings/alicloud/oss. They should follow the same format as the existing docs.


Telnet Protocol Handler Fixes

This corrects intermittent issues with servers not receiving complete TELOPT  sequence causing incorrect terminal and screen size detection.
Built Telnet Response Sequences in to an ArrayList to transpose back to a byte[] array so all response sequences are sent in a single write() instead of sending each separate byte in an individual write().

This addresses Issue #450
Thanks.

Coverage decreased (-0.1%) to 34.385% when pulling 23337a83c75f082153eeccb7efb4d7a00b47a8be on M-griffin:master into 626f79f35c1903612e4623a633a097f90fbb10df on connectbot:master.


Expanded not working with Offstage

Steps to Reproduce

Execute flutter run on the code sample
Immediate Exception by assertion: "Incorrect use of ParentDataWidget"

Expected results:
No exceptions. I believe that Offstage should work just like adding a Builder around a widget and making a test whether the offstage parameter is true or false to show the child. Am I wrong?

Code sample
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _offstage = false;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Row(
        children: [
          Offstage(
            offstage: _offstage,
            child: Expanded(
              child: Column(
                children: [
                  for (int i = 0; i < 10; i++) Text('Index: ${i + 1}'),
                ],
              ),
            ),
          ),
        ],
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: () => setState(() => _offstage = !_offstage),
        child: _offstage
            ? const Icon(Icons.visibility_off)
            : const Icon(Icons.visibility),
      ),
    );
  }
}

flutter doctor -v
[√] Flutter (Channel stable, 3.7.7, on Microsoft Windows [Version 10.0.22621.1265], locale pt-BR)
    • Flutter version 3.7.7 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (7 days ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at C:\Users\felip_0vh5fa6\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: C:\Users\felip_0vh5fa6\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\213.7172.25.2113.9123335\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.4.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.4.33403.182
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.3)
    • Android Studio at C:\Users\felip_0vh5fa6\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\213.7172.25.2113.9123335
    • Flutter plugin version 72.0.1
    • Dart plugin version 213.7433
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[√] VS Code (version 1.76.1)
    • VS Code at C:\Users\felip_0vh5fa6\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.60.0

[√] Connected device (4 available)
    • SM G780F (mobile) • RX8R30G5WDH • android-arm64  • Android 13 (API 33)
    • Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.22621.1265]
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 111.0.5563.65
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 110.0.1587.50

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

EDIT:
I wanted to have this setup so the other things in my Row would get resized by their own Expanded widgets. Solved my problem by using (as I've said before in the "what I expected" section) Builder with that test, and returning const SizedBox.shrink() when offstage.
Besides on dartpad.dev, the code actually runs successfully, just throws this exception.

I only meant to open this because I think this should work in the sense that this is unintuitive for new Flutter programmers. At least for me, the Offstage widget should not give this error, just as any Builder actually works. But if you don't agree with me, you can close this.


Install more recent version of CMake

Currently, cmake is being installed from the Ubuntu repository which for 16.04 installs 3.5.1 which fails to work on certain repos.
Version 3.5.2 can be installed from PPA - ppa:george-edison55/cmake-3.x
It's a stable & tested version for xenial and doesn't give any errors.

Every ppa added would lead to an increase in the time sudo apt-get update takes every single time it is run. I think it would be better to not add it unless 3.5.1 is really terrible and not working for a lot of builds. Let me know if that's the case @rajat2004
If need be, one should be able to build cmake from scratch for the latest version, similar to what is being done in opencvDirectInstall.sh which uses Markus-Perl's ffmpeg-build-script (which as of this comment builds cmake 3.11.1)

Every ppa added would lead to an increase in the time sudo apt-get update takes every single time it is run. I think it would be better to not add it unless 3.5.1 is really terrible and not working for a lot of builds. Let me know if that's the case @rajat2004

That's a good point. I didn't face any errors until when I was trying to build a simulator. Let's see, if there are any problems while using it for other more common builds then this can be added.

If need be, one should be able to build cmake from scratch for the latest version, similar to what is being done in opencvDirectInstall.sh which uses Markus-Perl's ffmpeg-build-script (which as of this comment builds cmake 3.11.1)

I thought that cmake was being built from source somewhere down the line but wasn't able to remember where exactly. I'll maybe have a look into this, see if it's possible to use this instead of the one installed by apt

Okay. Do reopen this if the problem pops up in multiple cases


Conmon timestamp buffer too small

Description
On some systems, conmon may fail to write anything to the attach socket at the timestamp buffer is too small.
I'm not sure exactly what kind of locale generates this, but I have shell on a system that consistently produces 45-length timestamps (longer than the 44 length of the buffer).
An example timestamp:
2018-06-21T01:33:55.102183860+05:1800 stdout
@edsantiago suggests that the error is at https://github.com/kubernetes-incubator/cri-o/blob/master/conmon/conmon.c#L311 and off % 3600 should actually be (off % 3600) / 60

Found this while tracking down https://github.com/projectatomic/libpod/issues/580

Reasoning: this is one of those weird non-integer-hour tz offsets. @mheon helpfully provided a sample timestamp:
2018-06-21T01:33:55.102183860+05:1800
                              ^^^^^^^

That should be 05:30.

Can you open a PR to fix it.

@rhatdan Sure, I'll take this one


Telemetry for start page

Need the following telemetry:

Track how long page is open
Track if click command before closing
Track if dont show again is clicked
Each event also has flag if first time seeing or subsequent (maybe include release version)

Validated as work item


[stable/cockroachdb] make use of jetstack/cert-manager

Currently the certificate management is based on the k8s internal ca. We'd like to add the posibility to enhance the certificate management to issue certificates by CAs managed via cert-manager.
Cert-Manager can fully automate the process and can use external PKIs like hashicorps vault or self-signed CAs.
We already implemented this based on non-helm deployment files and would like to add this with a feature switch to alternatively use cert-manager.

Why has this issue been closed? This feature would of great value when starting up a CockroachDB cluster and wanting to use letsencrypt certs

Indeed, would be a great feature.


Cassandra : pass UUID in binary instead of string ?

See http://www.cloudera.com/documentation/other/shared/CDH5-Beta-2-RNs/hbase_jdiff_report-p-cdh4.5-c-cdh5b2/cdh5b2/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.UUID.html
But endianness potential issues should be checked ?

This looks possible but the endianness would have to be specified and implementations would have to use it with regards to their own endianness. This looks very complex just to save some bytes (16 bytes for binary vs 36 for string) so closing for now.


Combined pipelines

This PR adds a new pipeline (ios - client and ios - client - ci) which is the pipeline that will replace ios - [service] - ci etc. At this point in time I've left all the CocoaPods wire-up in there since ripping that out will require a few other changes in the project files and I didn't want to overcomplicate this PR.
/cc @bsiegel @tjprescott

@mitchdenny will this PR effectively complete #220?

@tjprescott yep


Request Failed 404 from CAPI apiserver : Droplet not found : CF-ResourceNotFound

We deployed cf-for-k8s and performed a scale tests . We pushed source code based apps. We reached till 800 apps . Under such high load we could  see the following error in capi-api-server

{"timestamp":1587738150.8981497,"message":"Request failed: 404: {\"errors\"=>[{\"detail\"=>\"Droplet not found\", \"title\"=>\"CF-ResourceNotFound\", \"code\"=>10010, \"test_mode_info\"=>{\"detail\"=>\"Droplet not found\", \"title\"=>\"CF-ResourceNotFound\", \"backtrace\"=>[\"/cloud_controller_ng/app/controllers/v3/application_controller.rb:34:in `resource_not_found!'\", \"/cloud_controller_ng/app/controllers/v3/apps_controller.rb:347:in `droplet_not_found!'\", \"/cloud_controller_ng/app/controllers/v3/apps_controller.rb:322:in `current_droplet'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:194:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:42:in `block in process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:132:in `run_callbacks'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:41:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:22:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `block in instrument'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:23:in `instrument'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `instrument'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:32:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:256:in `process_action'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:134:in `process'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:32:in `process'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:191:in `dispatch'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:252:in `dispatch'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:52:in `dispatch'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:34:in `serve'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:52:in `block in serve'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:35:in `each'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:35:in `serve'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:840:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/tempfile_reaper.rb:15:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/content_security_policy.rb:18:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:98:in `run_callbacks'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:26:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:61:in `call'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/runtime.rb:22:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/activesupport-
<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:14:in `call'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/sendfile.rb:110:in `call'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/urlmap.rb:74:in `block in call'\", \"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/urlmap.rb:58:in `each'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/urlmap.rb:58:in `call'\",
\"/cloud_controller_ng/middleware/request_logs.rb:22:in `call'\",
\"/cloud_controller_ng/middleware/security_context_setter.rb:19:in `call'\", \"/cloud_controller_ng/middleware/vcap_request_id.rb:15:in `call'\",
 \"/cloud_controller_ng/middleware/cors.rb:49:in `call_app'\",
\"/cloud_controller_ng/middleware/cors.rb:14:in `call'\",
\"/cloud_controller_ng/middleware/request_metrics.rb:12:in `call'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/rack-2.2.2/lib/rack/builder.rb:244:in `call'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'\",
\"/usr/local/lib/ruby/gems/2.5.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:1067:in `block in
spawn_threadpool'\"]}}]}","log_level":"info","source":"cc.api","data":{"request_guid":"3b75e731-1246-
4c94-b2a0-b7300d9359e7::02a69280-4037-4b1a-bec8-
aef5a674c325"},"thread_id":47075637335140,"fiber_id":47075631752220,"process_id":1,"file":"/cloud_c
ontroller_ng/app/controllers/v3/application_controller.rb","lineno":178,"method":"handle_exception"}

cf-for-k8s Version:  https://github.com/cloudfoundry/cf-for-k8s/releases/tag/v0.1.0

Hey @KesavanKing,
Looks like there are a couple issues you've observed while scaling cf-for-k8s. Was wondering if you could share some of the steps folks on our team can take to reproduce some of these scale tests. Information like the size of our cluster, IAAS, instance types, any custom overlays...etc.
Thanks!

@aashah  , Thanks for the reaching out. We have created a page where we captured our tests setup, and all relevant details https://github.com/perf-cfk8s/docs/wiki/cf-for-k8s-v0.1.0
Hope this might help you to reproduce.

Hi @KesavanKing,
Thank you for your patience as we get around to doing performance tests on our team. I wanted to follow-up on this issue as its been a while and see that it was reported on v0.1.0. A lot has changed since v0.1.0 particularly around storing packages in a registry instead of a blobstore. In the past we have seen the kind of errors mentioned here when there are issues downloading from the blobstore.
We also currently have 2000 apps in our performance environment but have not seen this error - it would help a lot if you can document additional info for the types of app, registry used, iaas etc so that we can reproduce on our end. Have you seen the droplet not found error with the with the newer version v1.0.0? If yes, can you provide updated logs so we can update this issue and take a look?
Thank you for reporting this bug, looking forward to your reply.

Hi Sannidhi,
Thanks for the consideration.
In our recent scale tests on v1.0.0 , we didn't face this issue. So we can close it safely.


Spacing updates (visual)

Page layout updates to specs
Update all the visuals assets as a result of the changes made on the CSS side. Many designs are impacted including: modal, card, etc.

This is completed and reflected in several places in the Sketch file.


fix crashes on macOS 12

fixes #10

One thing I noticed: when running sudo limes start (so that it can bind to the port) it will now try to load its config from root's home dir instead of the sudoer' one. Seems to be a change in golang's user.Current(), but I'm not sure how to mitigate that. Suggestions are welcome.


[i2c, dv] Add excl for intr_state

Previously, excl of intr_state register is added via add_csr_exclusions function. With the proposal of #1635, the function add_csr_exclusions was removed by adding excl tags in .hjson file. However, the intr_state (and other intr regs) are not defined by hjson file thus all i2c_csr_* tests failed (add_csr_exclusions).
Should add_csr_exclusions  function are used in combination with excl tags defined in  .hjson file? Another solution is to expose all register via .hjson file to give the designer full controllability.

PR #1635 does a blanket exlcusion of INTR_TEST with CsrExclWrite (dont write to it) and INTR_STATE with CsrExclWriteCheck (dont read-check it) in the script itself. See here. This should get applied to all IPs. Considering this, its a little surprising that your tests are failing. Would you please share logs / waves to debug further?
Also, note that the new solution is backward-compatible with the old methodology (with add_csr_exclusions), so you still have the full controllability from the verification side.

@sriyerg
I add excl tags into i2c.hjson and remove add_csr_exclusions function. Currently, only csr_hw_reset failed

As described in the testplan, csr_hw_reset checks the reset value of the registers. Looks like some interrupt is getting asserted right out of reset (which means SW will get interrupted the moment it is enabled). Please check if this is intentional.

@tunghoang290780 can this be closed?


stm32/i2c: remove peripheral generic param.

stm32/rcc: add ClockEnableBit struct.
stm32/spi: remove peripheral generic param.
stm32/spi: check that the RCC enable bit is disabled on drop.
stm32: use funcs for info/state, const for ENABLE_BIT.
stm32/i2c: remove peripheral generic param.

bender run


[gha] Add workflow to build and publish docs

We should be able to use Turbo here instead of yarn commands but I'm not 100% sure it will matter without a remote cache, so we can figure this out later. These tasks should be plenty fast at the moment anyways.

Isn't this just going to use turbo under the hood anyway?

@jklein24 I think you have to actually use the turbo commands like yarn turbo docs and add docs as a task to the turbo config.


Adding IOC and UN/LOCODE

Hi Josh,
Hi Marcin,
I added IOC codes and UN/LOCODE codes to the data and added some spec for it.
I thought of writing my own countries gem till I found your's and find it quite fulfilling my needs. Thanks.
Cheers,
Norman

Thank you for your contribution unnu! I will update the gem early this week after I verify the tests.

Great! If you have any question let me know.


typescript@next version number still at 3.4.0?

Today in npm the @latest version is<EMAIL_ADDRESS>but the @next version is<EMAIL_ADDRESS> Is that expected or should we be up to<EMAIL_ADDRESS> or 3.4.2-dev or something?  Thanks!

Fixed, thanks!

(You'll see a new version tonight)

<EMAIL_ADDRESS>👍


Migration Issue

Thanks for taking over the plugin!
Unfortunately I upgraded and it seems that we've lost the data. Is there anyway to keep compatibility with previously created fields?

@keyurshah, we will look into this as soon as possible! It's currently a bit hectic with everything, but if you lock to 1.2.7 everything should be working as expected, since the last release only has some updated namespacing. So at least you could move on and keep on using it!

Same here. 1.2.8 broke the plugin for my installation. Luckily I noticed that before deploying to production. Going back to 1.2.7 fixed it for the moment.
Thanks for maintaining this plugin!

Thanks, I changed it to 1.2.7 and that worked.

I had the same issue, running the following SQL fixed it for me, YMMV:
UPDATE fields SET type = REPLACE(type, 'rias\colourswatches\fields\ColourSwatches', 'percipioglobal\colourswatches\fields\ColourSwatches');

Got this working with an SQL snippet similar to @mattslack's:
UPDATE fields SET `type` = 'percipioglobal\\colourswatches\\fields\\ColourSwatches' WHERE `type` = 'rias\\colourswatches\\fields\\ColourSwatches'

This is an issue for me as well. Maybe it would help to make the old class names (including the namespace) aliases of the new names, and then create a migration that updates the type column in the database.

@mtnorthrop we will make some time this week to address the update issues!
@aaronwaldon @mattslack feel free to PR.

Updates to the plugins are coming soon. Starting from mid-august we have more capacity to handle these issues! Thank you for your patience! 👍

For anyone else who is dead in the water right now after this, dropping this inside your site's migrations folder (or create a migrations folder if you don't have one) will get you up and running: https://gist.github.com/mildlygeeky/50d9d9b8e0a74fc5e343859c508a6e4b

@WeArePercipio could you update the plugin with the above gist?
Thank you @mildlygeeky for the gist btw!

updated in version 1.4.0


pull request for e2e test at 01/23/2017 20:15:08

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


SharedViewModel

Hello, is it possible to do something similar in androidx.navigation?

Currently there's no previousBackStackEntry yet, as a workaround you can wrap your screen inside a NavHost.


Styling details and a button missing when targets deleted from an indicator

Issue
Some styling details and a button are missing when I delete targets for an indicator.
Here's what I see on Staging:

Here's what I see on Dev2:

Things I notice: Red font looks smaller on Dev2. No bullet icon. No "Add targets" button.

Styling looks good. @camgnostic do you know why the wording is slightly different on QA from Staging?