text:
Examples fail to build

I'm trying to build the master version of this crate and run test and am seeing some failures in examples so far,
$ cargo --version
cargo 1.35.0 (6f3e9c367 2019-04-04)
$ cargo test
cargo test                                                                                [tags/v0.2.4]
   Compiling argmin v0.2.4 (/home/rth/src/argmin)
error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`
[...]

error: aborting due to 21 previous errors

Some errors occurred: E0277, E0599.
For more information about an error, try `rustc --explain E0277`.
error: aborting due to 9 previous errors

Some errors occurred: E0277, E0599.
For more information about an error, try `rustc --explain E0277`.
error: Could not compile `argmin`.
warning: build failed, waiting for other jobs to finish...
error: Could not compile `argmin`.
warning: build failed, waiting for other jobs to finish...
error: build failed

see full output below,

cargo test                                                                                [tags/v0.2.4]
   Compiling argmin v0.2.4 (/home/rth/src/argmin)
error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminNorm<f64>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminNorm<f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin::prelude::ArgminZeroLike` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminZeroLike` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin::prelude::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin::prelude::ArgminInv<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/trustregion_nd.rs:66:15
   |
66 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin::prelude::ArgminInv<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<argmin::prelude::OpWrapper<Rosenbrock>>` for `argmin::solver::trustregion::Dogleg`
   = note: required because of the requirements on the impl of `argmin::prelude::Solver<Rosenbrock>` for `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>`
   = note: required by `argmin::prelude::Executor::<O, S>::new`

error[E0599]: no method named `forward_diff` found for type `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>` in the current scope
  --> examples/sr1_trustregion.rs:36:17
   |
36 |         Ok((*p).forward_diff(&|x| rosenbrock(&x.to_vec(), self.a, self.b)))
   |                 ^^^^^^^^^^^^

error[E0599]: no method named `forward_hessian` found for type `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>` in the current scope
  --> examples/sr1_trustregion.rs:45:17
   |
45 |         Ok((*p).forward_hessian(&|x| self.gradient(&x).unwrap()))
   |                 ^^^^^^^^^^^^^^^

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminNorm<f64>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminNorm<f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminZeroLike` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminZeroLike` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin_core::math::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminSub<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>: argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:69:15
   |
69 |     let res = Executor::new(cost, solver, init_param)
   |               ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>`
   |
   = note: required because of the requirements on the impl of `argmin_core::Solver<Rosenbrock>` for `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>`
   = note: required by `argmin_core::executor::Executor::<O, S>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:61:38
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                                      ^^^^^^^^^ the trait `argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not satisfied
  --> examples/sr1_trustregion.rs:61:38
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                                      ^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:61:38
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                                      ^^^^^^^^^ the trait `argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:61:22
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                      ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminMul<f64, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required by `argmin::solver::trustregion::Steihaug::<P>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not satisfied
  --> examples/sr1_trustregion.rs:61:22
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                      ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminDot<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, f64>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required by `argmin::solver::trustregion::Steihaug::<P>::new`

error[E0277]: the trait bound `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>: argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not satisfied
  --> examples/sr1_trustregion.rs:61:22
   |
61 |     let subproblem = Steihaug::new().max_iters(20);
   |                      ^^^^^^^^^^^^^ the trait `argmin_core::math::ArgminAdd<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>, ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>` is not implemented for `ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>`
   |
   = note: required by `argmin::solver::trustregion::Steihaug::<P>::new`

error[E0599]: no method named `add_observer` found for type `argmin_core::executor::Executor<Rosenbrock, argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>>>` in the current scope
  --> examples/sr1_trustregion.rs:70:10
   |
70 |         .add_observer(ArgminSlogLogger::term(), ObserverMode::Always)
   |          ^^^^^^^^^^^^
   |
   = note: the method `add_observer` exists but the following trait bounds were not satisfied:
           `argmin::solver::quasinewton::SR1TrustRegion<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 2]>>, argmin::solver::trustregion::Steihaug<ndarray::ArrayBase<ndarray::OwnedRepr<f64>, ndarray::Dim<[usize; 1]>>>> : argmin_core::Solver<Rosenbrock>`

error[E0599]: no method named `add_observer` found for type `argmin::prelude::Executor<Rosenbrock, argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg>>` in the current scope
  --> examples/trustregion_nd.rs:67:10
   |
67 |         .add_observer(ArgminSlogLogger::term(), ObserverMode::Always)
   |          ^^^^^^^^^^^^
   |
   = note: the method `add_observer` exists but the following trait bounds were not satisfied:
           `argmin::solver::trustregion::TrustRegion<argmin::solver::trustregion::Dogleg> : argmin::prelude::Solver<Rosenbrock>`

warning: unused import: `argmin_core::finitediff`
  --> examples/sr1_trustregion.rs:15:5
   |
15 | use argmin_core::finitediff::*;
   |     ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: #[warn(unused_imports)] on by default

error: aborting due to 21 previous errors

Some errors occurred: E0277, E0599.
For more information about an error, try `rustc --explain E0277`.
error: aborting due to 9 previous errors

Some errors occurred: E0277, E0599.
For more information about an error, try `rustc --explain E0277`.
error: Could not compile `argmin`.
warning: build failed, waiting for other jobs to finish...
error: Could not compile `argmin`.
warning: build failed, waiting for other jobs to finish...
error: build failed

Hi,
I think the problem may be that it is necessary to compile with the ndarrayl feature if you want to run tests. I apologize, this should be documented better, I'll try to do that tomorrow morning.

Thanks! Indeed, running,
cargo test --features ndarrayl

does work as expected. It's interesting that the feature is needed, since ndarray and ndarray-linalg are in dev-dependencies already.

The feature is only necessary in order to compile argmin-core with the ndarrayl feature. I'll see if I can find a way to automatically do that.

authors: rth stefan-k

repo: argmin-rs/argmin


text:
Fixed typos and added spellcheck to CI

Well, that was a lot. I really don't know how to write "internal" and "initial".

Codecov Report
Base: 93.39% // Head: 93.39% // No change to project coverage :thumbsup:

Coverage data is based on head (0fe7080) compared to base (938b3ca).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #312   +/-   ##
=======================================
  Coverage   93.39%   93.39%
=======================================
  Files         119      119
  Lines       19012    19012
=======================================
  Hits        17756    17756
  Misses       1256     1256

Impacted Files
Coverage Δ

argmin/src/core/observers/slog_logger.rs
98.83% <ø> (ø)

argmin/src/solver/quasinewton/sr1.rs
76.50% <ø> (ø)

argmin/src/solver/quasinewton/sr1_trustregion.rs
72.25% <ø> (ø)

argmin/src/core/checkpointing/mod.rs
66.19% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

source: gharchive/pull-request

authors: codecov-commenter stefan-k

license_type: permissive

license_source: github-api


text:
Add trace IDs for debugging

We should use industry-standard, e.g. OpenTelemery (was Open Zipkin).

https://github.com/nats-io/not.go

https://medium.com/data-rocks/kafka-record-tracing-379ed2b0af51

Opentelemetry already has first class support for Kafka, but nats is not there. not.go is still for opentracing, not opentelemetry.

Superseded by #161

source: gharchive/issue

authors: alexec whynowy

repo: argoproj-labs/argo-dataflow


text:
Define spec.url in Configmap

When deploying Ingress externally to ArgoCD operator (GKE with Traefik), altering spec.url in Operator CR will not cause argocd-cm to change. It is a problem when using DEX.

Regular approach:

data:
  url: https://example-argocd-server

It will keep the default value of:
url: https://argocd-server

https://github.com/argoproj-labs/argocd-operator/issues/103 did not work:

spec:
  server:
    route:
      enabled: true
    host: my.domain.app

kubectl get configmap argocd-cm -n argocd -o yaml
apiVersion: v1
data:
  url: https://argocd-server

https://github.com/argoproj-labs/argocd-operator/pull/236 also did not work:

spec:
  server:
    host: my.domain.app

kubectl get configmap argocd-cm -n argocd -o yaml
apiVersion: v1
data:
  url: https://argocd-server

Only (but not viable) way found makes ArgoCD Operator to create additional Ingress:

spec:
  server:
    grpc:
      ingress:
        enabled: true
    ingress:
      enabled: true
    insecure: true
    host: my.domain.app

kubectl get configmap argocd-cm -n argocd -o yaml
apiVersion: v1
data:
  url: https://my.domain.app

Please, is not possible to add a direct way to set URL value to any defined in CR spec.url?

Hi @rv-silva , Thanks for using operator and raising issue with us :)

Only (but not viable) way found makes ArgoCD Operator to create additional Ingress:
I am trying to understand why is this not a viable solution for you ?

@iam-veeramalla thank you for your prompt answer.
It is not viable because Ingress is being used externally to ArgoCD, in this case with Traefik. The Ingress created by Operator will be duplicated.

Does your traefik ingress controller read the ingress created by operator?

@iam-veeramalla nope, in fact they conflict and ArgoCD becomes unreachable.

@iam-veeramalla nope, in fact they conflict and ArgoCD becomes unreachable.

@rv-silva  Thanks for making it clear :) . Can you please let me know few more things to  label this issue as a bug.

Instead of deploying ingress externally, Is it possible to make traefik read the ingress created by the operator? Probably by updating the ingress-class or something?

Can you workaround this issue by updating argocd-cm manually ?

Thanks :)

Thank you for accepting my request.

Not sure if works, but still ArgoCD is creating a new Ingress resource, consequently a billed load balancer in GCP.
Unfortunately not, whenever url field is updated in argocd-cm, ArgoCD returns its value to https://argocd-server.

I tried all ways before opening the issue.

@iam-veeramalla Pls, can you save me with that feature? Lots of pressure to put ArgoCD in production.

Hi @rv-silva Sure :)
Have you tried the point no.1 that I suggested above ?

Instead of deploying ingress externally, Is it possible to make traefik read the ingress created by the operator? Probably by updating the ingress-class or something?

Meanwhile, please give me sometime to look at a permanent solution to this bug.

@rv-silva  looking at the code, Point no. 3 in your issue description should work.

Allow user to provide custom external hostname for argo-server #236 also did not work:

https://github.com/argoproj-labs/argocd-operator/blob/6fa33c97c84411e589ff0465b03ae8d5d0e0bb71/pkg/controller/argocd/util.go#L232
Can you please confirm the version of argocd-operator that you are running ?

@iam-veeramalla It worked after updating and using the config you pointed out. Thank you so much!

Closing the issue as the configuration works :)

authors: iam-veeramalla rv-silva

repo: argoproj-labs/argocd-operator


text:
When a parameter is missing, the template is passed explicitly, and results in incomprehensible error

I have a set of parameters in a git repo that I care about, example:
a: "aaa"
b: "bbb"
c: "ccc"

My appset generator uses a helm chart to deploy the app:
...
      source:
        chart: mychart
        path: ''
        repoURL: >-
          https://my.helm.repo
        targetRevision: 0.0.13
        helm:
          releaseName: myapp
          parameters:
          - name: a
            value: '{{a}}'
          - name: b
            value: '{{b}}'
          - name: c
            value: '{{c}}'
          - name: d
            value: '{{d}}'

As you can see, d isn't in the config file. What happens is the appset creates the app manifest with --set d={{d}} which fails with an error that's irrelevant to the issue:
      status 1: Error: failed parsing --set data: key "}" has no value'

In my specific case, I would expect the argument to not be passed at all, resulting in a default being picked from the chart's default values.yaml, or for the application to spit out an error about a missing parameter.
Maybe even make it configurable, so that if I have a variable in git, it gets templated, if I don't, depending on the applicationSet settings, the entire setting gets skipped, or fails on missing variable.

Is there any way around this, I've got the same issue where some helm charts have value files and some do not.

authors: dyasny jasonmacdonald

repo: argoproj/applicationset


text:
Wait container failing: 'level=info msg="stopping progress monitor (context done)" error="context canceled"'

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
I am trying to implement a mechanism to clone a repository and pass it downstream. This has been failing due to the "unable to resolve delta" that was happening in 3.4.4. I just updated to argo v3.4.5.
I am now getting errors on Argo's "wait" container. I performed several tests and concluded the following:

The repo is succesfully cloned, as the status is correctly displayed
Error does not happen when I omit the output artifact
Error does not happen for public repositories (even with output artifact defined)

Version
v.3.4.5
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: test-clone-repo
spec:
  entrypoint: run
  templates:
    - name: run
      inputs:
        parameters:
          artifacts:
          - name: repo-artifact
            path: /src
            git:
              repo: "https://gitlab.com/url"
              revision: "main"
              usernameSecret:
                name: argo-git-creds
                key: username
              passwordSecret:
                name: argo-git-creds
                key: token
      container:
        image: "python:3.9-buster"
        command: [ sh, -c ]
        args: [ "git status && ls && pwd" ]
        workingDir: /src
      outputs:
        artifacts:
          - name: repo-artifact
            path: /src

Logs from the workflow controller
time="2023-02-08T19:14:09.342Z" level=info msg="Processing workflow" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Task-result reconciliation" namespace=fix-arg-workflows numObjs=0 workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Pod failed: Error (exit code 2)" displayName=test-clone-repo-drqpb namespace=fix-arg-workflows pod=test-clone-repo-drqpb templateName=run workflow=test-clone-repo-drqpb         │
│ time="2023-02-08T19:14:09.342Z" level=info msg="node changed" namespace=fix-arg-workflows new.message="Error (exit code 2)" new.phase=Error new.progress=0/1 nodeID=test-clone-repo-drqpb old.message= old.phase=Running old.pro │
│ time="2023-02-08T19:14:09.342Z" level=info msg="TaskSet Reconciliation" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg=reconcileAgentPod namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Updated phase Running -> Error" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Updated message  -> Error (exit code 2)" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                              │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Marking workflow completed" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Marking workflow as pending archiving" namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Checking daemoned children of " namespace=fix-arg-workflows workflow=test-clone-repo-drqpb                                                                                │
│ time="2023-02-08T19:14:09.342Z" level=info msg="Workflow to be dehydrated" Workflow Size=2398                                                                                │
│ time="2023-02-08T19:14:09.348Z" level=info msg="cleaning up pod" action=deletePod key=fix-arg-workflows/test-clone-repo-drqpb-1340600742-agent/deletePod                                                                         │
│ time="2023-02-08T19:14:09.352Z" level=info msg="Delete pods 404"                                                                                │
│ time="2023-02-08T19:14:09.359Z" level=info msg="Update workflows 200"                                                                                │
│ time="2023-02-08T19:14:09.359Z" level=info msg="Workflow update successful" namespace=fix-arg-workflows phase=Error resourceVersion=80452200 workflow=test-clone-repo-drqpb                                                      │
│ time="2023-02-08T19:14:09.359Z" level=info msg="Create events 201"                                                                                │
│ time="2023-02-08T19:14:09.371Z" level=info msg="DeleteCollection workflowtaskresults 200"                                                                                │
│ time="2023-02-08T19:14:09.371Z" level=info msg="Create events 201"                                                                                │
│ time="2023-02-08T19:14:09.371Z" level=info msg="archiving workflow" namespace=fix-arg-workflows uid=4621fee1-4e34-46a5-a718-a955b880a4e2 workflow=test-clone-repo-drqpb                                                          │
│ time="2023-02-08T19:14:09.377Z" level=info msg="cleaning up pod" action=labelPodCompleted key=fix-arg-workflows/test-clone-repo-drqpb/labelPodCompleted                                                                          │
│ time="2023-02-08T19:14:09.394Z" level=info msg="Patch pods 200"                                                                                │
│ time="2023-02-08T19:14:09.424Z" level=info msg="Patch workflows 200"                                                                                │
│ time="2023-02-08T19:14:12.044Z" level=info msg="Get leases 200"                                                                                │
│ time="2023-02-08T19:14:12.051Z" level=info msg="Update leases 200"                                                                                │
│ time="2023-02-08T19:14:17.059Z" level=info msg="Get leases 200"                                                                                │
│ time="2023-02-08T19:14:17.068Z" level=info msg="Update leases 200"                                                                                │
│ time="2023-02-08T19:14:18.099Z" level=info msg="Watch workflows 200"                                                                                │
│
│ time="2023-02-08T19:14:21.086Z" level=info msg=healthz age=5m0s err="<nil>" instanceID= labelSelector="!workflows.argoproj.io/phase,!workflows.argoproj.io/controller-instanceid" managedNamespace=                              │
│ time="2023-02-08T19:14:22.076Z" level=info msg="Get leases 200"                                                                                │
│ time="2023-02-08T19:14:22.083Z" level=info msg="Update leases 200"                                                                                │
│ time="2023-02-08T19:14:27.090Z" level=info msg="Get leases 200"                                                                                │
│ time="2023-02-08T19:14:27.096Z" level=info msg="Update leases 200"                                                                                │
│ time="2023-02-08T19:14:27.303Z" level=info msg="cleaning up pod" action=killContainers key=fix-arg-workflows/test-clone-repo-drqpb/killContainers                                                                                │
│ time="2023-02-08T19:14:32.111Z" level=info msg="Get leases 200"                                                                                │
│ time="2023-02-08T19:14:32.119Z" level=info msg="Update leases 200"                                                                                │
│

Logs from in your workflow's wait container
time="2023-02-08T18:56:22.825Z" level=info msg="Starting Workflow Executor" version=v3.4.5                                                                                │
│ time="2023-02-08T18:56:22.827Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5                                                                                │
│ time="2023-02-08T18:56:22.827Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=fix-arg-workflows podName=test-clone-repo-8nnkq template="{\"name\":\"run\",\ │
│ time="2023-02-08T18:56:22.828Z" level=info msg="Starting deadline monitor"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Main container completed" error="<nil>"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Deadline monitor stopped"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="stopping progress monitor (context done)" error="context canceled"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="No output parameters"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Saving output artifacts"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Staging artifact: repo-artifact"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Staging /src from mirrored volume mount /mainctrfs/src"                                                                                │
│ time="2023-02-08T18:56:35.829Z" level=info msg="Taring /mainctrfs/src"                                                                                │
│ time="2023-02-08T18:56:46.803Z" level=info msg="archived 651 files/dirs in /mainctrfs/src"                                                                                │
│ time="2023-02-08T18:56:46.803Z" level=info msg="Successfully staged /src from mirrored volume mount /mainctrfs/src"                                                                                │
│ time="2023-02-08T18:56:46.803Z" level=info msg="S3 Save path: /tmp/argo/outputs/artifacts/repo-artifact.tgz, key: fix-arg-workflows/test-clone-repo-8nnkq/test-clone-repo-8nnkq/repo-artifact.tgz"                               │
│ time="2023-02-08T18:56:46.803Z" level=info msg="Creating minio client using IAM role"                                                                                │
│ time="2023-02-08T18:56:46.811Z" level=info msg="Saving file to s3" bucket=bla-k8s endpoint=s3.amazonaws.com key=fix-arg-workflows/test-clone-repo-8nnkq/test-clone-repo-8nnkq/repo-artifact.tgz path=/tmp/argo/outputs/artifact │
│

i am getting several "Error (exit code 2)" on v3.4.5 too, but this never happened on v3.4.4

This is actually not related to the repo artifact, but it seems to be related to artifact passing. I am also getting this on other stuff I am passing through workflows.
How can such big regression come from a new update?

#10140 does place constraints on context scope. But I don't think it is caused by this modification.

stopping progress monitor (context done)

This log is as expected. Happens in this code snippet whenever wait-container receives SIGTERM (kubelet stops pod's Sometimes it will try to send this signal to the container in the Pod https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination ) will trigger.

I think we should pay more attention to the "unable to resolve delta" error. We may need the following information to help troubleshoot the problem (information can be desensitized):

Provide full log of main-container
Provide the complete yaml of the failed workflow (if it can be reproduced, it will speed up troubleshooting).
Check whether the configmap of workflow-controller contains ActiveDeadlineSeconds related settings,
Try to rule out whether it is caused by a git server error.

@sxllwx i don't have any "unable to resolve delta" messages

i am getting several "Error (exit code 2)" on v3.4.5 too (nothing special about the workflows but seems to affect the shorter running ones ie < 30 seconds long, reading inline source artifact i guess s3, not git), but this never happened on v3.4.4
can see the spike of 100s of instances (appearance of "Error (exit code 2)" in controller logs) of this after upgrading (the 2 bars on right are after upgrade, whereas in 30 days before that only happened 4 times):

emmm... I'm answering lvijnck's question. 😅

For your case, you can provide the following information for troubleshooting:

The log of workflow-controller.
(init, main, wait) container related logs.
The manifest of the workflow.

@sxllwx Thanks for the response! Briefly updated the original post. The "unable to resolve reference delta" was in Argo v3.4.4, hence why I updated to 3.4.5. As a current workaround, I have setup a custom template where I implement the cloning myself.
As soon as I did set this up, my pipeline continued to crash signalling the exit 2 above. Some additional observations:

It's not related to the Git input artifact, i.e.,

I was successfully able to swap out my repository for another private one
I was able to clone any other public repo, e.g., the argo workflows repo and pass it as an artifact

It seems to be related to output artifacts

When I omit the output artifact I no longer get the error
The error is also happening for other steps in my pipeline with output artifacts

I ended up downgrading to v.3.4.4. and the issue was no longer present.
The only log notifications that resembles an error is the following:
│ time="2023-02-08T18:56:35.829Z" level=info msg="stopping progress monitor (context done)" error="context canceled"

Follow-ups:

Workflow above contains full example (only secrets to repo are omitted)
Adding the Helm deployment below

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: argo-workflows
  namespace: argocd
spec:
  project: default
  source:
    chart: argo-workflows
    repoURL: https://argoproj.github.io/argo-helm
    targetRevision: 0.22.10
    helm:
      releaseName: argo-workflows
      values: |
        server:
          baseHref: /
          extraArgs:
            - --auth-mode=server
        useDefaultArtifactRepo: true
        useStaticCredentials: false
        artifactRepository:
          archiveLogs: true
          s3:
            insecure: false
            bucket: blabla-k8s
            endpoint: s3.amazonaws.com
            region: us-east-2
            keyFormat: "{{workflow.namespace}}/{{workflow.name}}/{{pod.name}}"
        controller:
          persistence:
            connectionPool:
              maxIdleConns: 100
              maxOpenConns: 0
            nodeStatusOffLoad: true
            # enable archiving of old workflows
            archive: true
            archiveTTL: 90d
            postgresql:
              host: host
              port: 5432
              database: postgres
              tableName: argo_workflows
              # the database secrets must be in the same namespace of the controller
              userNameSecret:
                name: argo-db-creds
                key: username
              passwordSecret:
                name: argo-db-creds
                key: password
  destination:
    server: https://kubernetes.default.svc
    namespace: argo-workflows
  syncPolicy:
    syncOptions:
    - CreateNamespace=true
    automated:
      prune: true
      selfHeal: true
    retry:
      limit: 20
      backoff:
        duration: 10s
        factor: 2

Thank you for the information
Can you provide the manifest of the Pod with Error (exit code 2)?

@danajp perhaps https://github.com/argoproj/argo-workflows/pull/10039 is the cause? https://github.com/argoproj/argo-workflows/issues/9179#issuecomment-1237456023 comment caught my attention "Most users will never need tty. Replacing os.Exec with pty is risky (reasons should be obvious). I think benefit outweights risk."

@tooptoop4 Seems unlikely. pty is only used for templates that set tty: true. It's also only used in the main container, not the waitcontainer.

The following facts have been confirmed so far:

wait-container may receive SIGTERM (15) more than once
If we call cancel, it will cause argo wait written in golang All signal processing of the app is reset to the default processing method.

There is a question here, why argo wait will receive sig-term? Who can provide some ideas?

Update:
Here is a summary:

is indeed an issue introduced by PR#10140, and I believe [PR#10523](https://github.com/argoproj/ argo-workflows/pull/10523) can be fixed

But here's one more part to explain (it's going to involve a lot of code):

Why does PR#10140 cause problems with (exit code 2) ?

https://github.com/argoproj/argo-workflows/blob/v3.4.5/cmd/argoexec/commands/wait.go#L36-L46
The cancel here will be executed when the function exits. The semantics of cancel (in addition, it should be called stop here) is: This argoexec wait will not be willing to receive signals (sigterm )(ref: https://github.com/golang/go/blob/go1.19.2/src/os/signal/signal.go#L262-L276). If the signal is received again, argoexec wait will use the default behavior provided by golang, which is exit(2)
https://github.com/argoproj/argo-workflows/blob/v3.4.4/cmd/argoexec/commands/wait.go#L36-L46
Here cancel will be executed when func waitContainer exits. func waitContainer can receive multiple sigterms during execution.

Why is it sporadic?

From the above analysis, we can see that whether exit(2) depends on the timing of receiving sigterm for the second time, our workflow can succeed in the following situations

The cleanup logic performed by our argoexec wait can be done very quickly. (@lvijnck If the warehouse code is very large, you will also encounter this problem. I use kubernetes/kubernetes, and it is relatively easy to reproduce)
When our workflow-controller executes podCleanupItem (this function will send a signal to argoexec wait)

I hope my answer can clarify your doubts (you are welcome to question again): @lvijnck tooptoop4

Do you have an estimation when will this fix be released?

authors: danajp lvijnck omarkalloush sxllwx tooptoop4

repo: argoproj/argo-workflows


text:
Inline templates still do not create the pod name correctly

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issue exists when I tested with :latest
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what did you expect to happen?
It still looks like the bug from https://github.com/argoproj/argo-workflows/issues/10912 only that now with version v3.5.5 argo is not even realizing anymore that the pod is already completed.

The pod argo wants to refer to is named fantastic-python-2118328171 as can be seen in the UI. (for the workflow, see the example workflow further down)
It's stuck in pending mode as the pod is not found on the Kubernetes cluster, because when I look at the cluster, I see the pod called fantastic-python--2118328171 which is either running or already done. Since argo apparently uses the wrong name to fetch the pod and its status, the workflow does not proceed. Even if it would continue, the logs would not be visible in the argo UI, see the referenced bug report for it.
You can even see in the logs of the controller that it created the pod using the double - and then it tries to pull the status of the pod using only one -. (see logs further, the first log is being returned when I search for the pod name with double -, the other logs, when I search for the pod name with only one -)
If I got your fix right for https://github.com/argoproj/argo-workflows/issues/10912 I think you tried to fix a problem with the naming of the task, but I think the issue goes deeper:
As far as I understood it, the pod name should always be something like {workflow-name}-{workflow-id}-{step-name}-{step-id} but when I use the inline option rather than the template option to reference another template, it simply does not add the step-name to the pod name.
Please have a look at it, since I need to use the inline option as I'm creating the workflows automatically, and using the template option would make everything much much harder.
Version
v3.5.5
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
metadata:
  name: fantastic-python
  namespace: default
spec:
  entrypoint: argosay
  templates:
    - name: argosay
      dag:
        tasks:
          - name: some-task
            inline:
              container:
                name: main
                image: argoproj/argosay:v2
                command:
                  - /argosay
                args:
                  - echo
                  - 'Hello argo'

Logs from the workflow controller
time="2024-04-15T12:44:16.689Z" level=info msg="Created pod: fantastic-python.some-task (fantastic-python--2118328171)" namespace=default workflow=fantastic-python

time="2024-04-15T12:44:16.678Z" level=warning msg="was unable to obtain the node for fantastic-python-2118328171, taskName some-task"
time="2024-04-15T12:44:16.678Z" level=warning msg="was unable to obtain the node for fantastic-python-2118328171, taskName some-task"
time="2024-04-15T12:44:16.678Z" level=info msg="Pod node fantastic-python-2118328171 initialized Pending" namespace=default workflow=fantastic-python
time="2024-04-15T12:44:26.691Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python
time="2024-04-15T12:44:36.695Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python
time="2024-04-15T12:44:46.711Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python
time="2024-04-15T12:44:56.714Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python
time="2024-04-15T12:45:06.717Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python
time="2024-04-15T12:45:16.722Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=fantastic-python-2118328171 old.message= old.phase=Pending old.progress=0/1 workflow=fantastic-python

Logs from in your workflow's wait container
time="2024-04-15T12:59:16.660Z" level=info msg="Starting Workflow Executor" version=v3.4.8
time="2024-04-15T12:59:16.661Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5
time="2024-04-15T12:59:16.661Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=default podName=fantastic-python--2118328171 template="{\"inputs\":{},\"outputs\":{},\"metadata\":{},\"container\":{\"name\":\"main\",\"image\":\"argoproj/argosay:v2\",\"command\":[\"/argosay\"],\"args\":[\"echo\",\"Hello argo\"],\"resources\":{}}}" version="&Version{Version:v3.4.8,BuildDate:2023-05-25T22:21:53Z,GitCommit:9e27baee4b3be78bb662ffa5e3a06f8a6c28fb53,GitTag:v3.4.8,GitTreeState:clean,GoVersion:go1.20.4,Compiler:gc,Platform:linux/arm64,}"
time="2024-04-15T12:59:16.661Z" level=info msg="Starting deadline monitor"
time="2024-04-15T12:59:18.663Z" level=info msg="Main container completed" error="<nil>"
time="2024-04-15T12:59:18.663Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2024-04-15T12:59:18.663Z" level=info msg="No output parameters"
time="2024-04-15T12:59:18.663Z" level=info msg="No output artifacts"
time="2024-04-15T12:59:18.663Z" level=info msg="Alloc=9863 TotalAlloc=15937 Sys=24429 NumGC=4 Goroutines=7"

looks the same reason with https://github.com/argoproj/argo-workflows/issues/12895, and will be fixed by https://github.com/argoproj/argo-workflows/pull/12928

mmh okay looks like it yes, I was somehow only able to find 2 already closed issues on this, but never found the open one on google. Thank you for the quick response!

authors: McKMarcBruchner shuangkun


text:
Default auth mode is not set to "server"

Summary
After updating Argo Workflow from v3.0 to v3.1-rc7, we were experiencing "token not valid for running mode" error when accessing argo-server's Web UI. This error always redirected us to Login page.
Although the following document indicates the default auth mode is set to server, it seems like the default auth mode is set to client and this behavior was causing the error.
https://github.com/argoproj/argo-workflows/blob/v3.1.0-rc8/docs/argo-server-auth-mode.md
After explicitly setting the --auth-mode to server in the manifest, the auth mode is set to server and works without error. (NOTE: we were also setting --secure=false option to disable TLS)
# Snippet of the argo-server manifest
    spec:
      containers:
      - name: argo-server
        image: docker.io/argoproj/argocli:v3.1.0-rc8
        args:
        - server
        - "--secure=false"
        # Need to add auth-mode setting explicitly.
        - "--auth-mode=server"

If the document is correct, default auth mode must be set to server when --auth-mode option isn't set.
Diagnostics
What Kubernetes provider are you using?
-> Kubernetes v1.16
What version of Argo Workflows are you running?
-> Argo Workflow v3.1.0-rc7, v3.1.0-rc8
What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary
-> K8sAPI
Did this work in a previous version? I.e. is it a regression?
-> Worked as expected in Argo Workflow v3.0.2. Possible regression.
argo-server's startup log: Without --auth-mode option, authModes is set to ["client"].
level=info authModes="[client]" baseHRef=/ managedNamespace= namespace=argo secure=false
level=warning msg="You are running in insecure mode. Learn how to enable transport layer security: https://argoproj.github.io/argo-workflows/tls/"                                                                   level=info msg="config map" name=workflow-controller-configmap
level=info msg="SSO disabled"
level=info msg="Starting Argo Server" instanceID= version=v3.1.0-rc8
level=info msg="Creating DB session"
level=info msg="Node status offloading config" ttl=5m0s
level=info msg="Creating event controller" operationQueueSize=16 workerCount=4
level=info msg="Argo Server started successfully on http://localhost:2746"

argo-server's error log:
level=info msg="finished unary call with code Unauthenticated" error="rpc error: code = Unauthenticated desc = token not valid for running mode" grpc.code=Unauthenticated grpc.method=GetInfo grpc.service=info.InfoService grpc.start_time="2021-05-25T06:57:04Z" grpc.time_ms=0.114 span.kind=server system=grp

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

You are correct. As of a security audit in v3, the default auth-mode was changed to client. You'll need to override it to use server mode.

@alexec
Thanks for the reply.
I still think it's a bug because default auth mode is different even in v3 and no document refers to it.

v3.0.x: Default auth mode is set to server.  (Tested with latest v3.0.7)
v3.1.x: Default auth mode is set to client.

Both codes and documents must be fixed according to Argo Workflows' v3 decision. And if the default mode has been changed to client in v3, it would be nice to note this as breaking changes like TLS.

Hey @alexec, if you have time can you sometimes fix, documentation? By default, the server will start with auth mode of "server". https://github.com/argoproj/argo-workflows/blob/4e450e250168e6b4d51a126b784e90b11a0162bc/docs/argo-server-auth-mode.md

authors: alexec vetyy yoichiwo7


text:
Archived workflows : no logs without artifact repo ?

Summary
This issue is a followup to #5966 that has been closed to say that argo ui does not fail to display logs when there is no artifacts
however, the documentation https://argoproj.github.io/argo-workflows/workflow-archive/ only says that you need to enable database to have archives, not that you also have to configure an artifact repository (and let's say that archives without logs are a bit useless)
Questions

is the artifact repo really needed for logs archives ? if yes, amend the documentation (I can submit a PR for this)

is it possible to only use the db (either as a full blown artifact repository or just to store logs) ?

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

The workflow archive is only for archiving workflows, not logs. It's a different thing, you need an artifact repository for your logs.

@alexec
PR for the documentation : https://github.com/argoproj/argo-workflows/pull/6005
what about using the database to store the logs  of the pods ?
I was thinking about something like tjis in the configmap :
archive: true
logs: true

my understanding is that artefacts are required to save specific data (like a specific file in a container) not to save all the outputs of all the pods... (even if the output of a pod CAN be an artifact in some cases)
can you elaborate a bit on this question plz ?

For logs, you can save them as an artifact. Most enterprises simply dump all logs into Splunk or similar.

note that I am aware that I can use "pipe-tee" into a file + declare an ouput artifact (obviously, like a "normal" artifact)
however, I do not like the idea to change all my templates to do that just for the "sake" of archives, so I am looking to an "automatic" approach
if you are interested into the pipe-tee approach, have a look at https://github.com/argoproj/argo-workflows/blob/4e450e250168e6b4d51a126b784e90b11a0162bc/test/e2e/expectedfailures/output-artifact-not-optional.yaml

I think you may have found a bug. Can you please attach the version you're using?

I am using docker.io/argoproj/workflow-controller:latest from this morning in my TZ :)
how can I see version ? I tried to use logs/describe of argo-server and workflow-controller pods, but I cannot see a version there ...

The correct way to have automatic logs is to use the configmap (either controller CM or a new artifact-repositories CM), see https://github.com/argoproj/argo-workflows/issues/5983#issuecomment-849010919
@alexec unless you suspect another problem, you can close this issue (and thank you for the support 👍 )

authors: alexec christopheblin


text:
fix: argo plugins docs refer to plugin.* but should be server.*

Signed-off-by: NikeNano niklas.sven.hansson@gmail.com
https://github.com/argoproj/argo-workflows/blob/b7a525be4014e3bdd28124c8736c25a007049ae7/cmd/argo/commands/executorplugin/io.go#L25
Fixes #TODO

ops - should be docs: not feat: - but merged now

authors: NikeNano alexec


text:
Updating Jaws tests after adding a default value for aria-labelledby

After commit 24960cb98cef30f45e0cd897c64e0c317eecddff, the following tests failed because the corresponding radio buttons now have a label (which was not expected in Jaws history):

test.aria.widgets.wai.fieldset.FieldsetLabelJawsTestCase
test.aria.widgets.wai.input.radiobutton.RadioButtonGroupJawsTestCase

This PR updates the expected history in those tests.

@benouat Thank you for your review!

repo: ariatemplates/ariatemplates

license_source: bigquery


text:
Feat(eos_cli_config_gen): Add 'route_reflector_client' key to BGP neighbor in VRF

Enhancement summary
Currently this is only supported at peer-group level and global neighbor level, but not under a VRF.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
Configure a BGP neighbor as a route reflector client inside a VRF
Describe the solution you would like
The following key added to the BGP neighbors data model under VRF:
route_reflector_client: < true | false >

Describe alternatives you have considered
eos_cli for BGP VRF
Additional context
No response
Contributing Guide

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

I can work on a PR for this

repo: aristanetworks/ansible-avd


text:
feat(calculator): add french translation

Proposed changes
This pull request adds French translations to the Arithmico calculator app. It include the French language option in the settings, and a new French translation file (fr.json) for the user interface.
Types of changes
What types of changes does your code introduce to Arithmico?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
(none)

:+1:

repo: arithmico/arithmico

license: MIT


text:
Angle brackets are erroneously escaped in content of noscript tags

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1

What steps will reproduce the problem?
2.1. Use PhantomJS to view the content of https://www.amazon.com.  This script will work:

var page = require('webpage').create();
page.open('https://www.amazon.com', function(status) {
  console.log("Status: " + status);
  if(status === "success") {
    console.log(page.content);
  }
  phantom.exit();
});

Result: The content contains escaped angle brackets (< and >) that should not be escaped.  This is an excerpt from the PhantomJS output:
<![endif]>
<style type="text/css"><!--
  #navbar #nav-shop .nav-a:hover {
    color: #ff9900;
    text-decoration: underline;
  }
  #navbar #nav-search .nav-search-facade,
  #navbar #nav-tools .nav-icon,
  #navbar #nav-shop .nav-icon,
  #navbar #nav-subnav .nav-hasArrow .nav-arrow {
    display: none;
  }
  #navbar #nav-search .nav-search-submit,
  #navbar #nav-search .nav-search-scope {
    display: block;
  }
  #nav-search .nav-search-scope {
    padding: 0 5px;
  }
  #navbar #nav-search .nav-search-dropdown {
    position: relative;
    top: 5px;
    height: 23px;
    font-size: 14px;
    opacity: 1;
    filter: alpha(opacity = 100);
  }
--></style>
<![if gt IE 6]>

Here's the same piece of HTML as downloaded by Firefox or Chrome:
<![if gt IE 6]><![endif]>

<![if gt IE 6]><![endif]>

Which operating system are you using?
OSX

Did you use binary PhantomJS or did you compile it from source?
Binary

Please provide any additional information below.
This appears to be an issue when HTML tags or comments are included as children of a noscript element.

I do see the same behavior (same version)
Also I really can't manage to have javascriptEnabled = false working as I'd expect: wether it's true of false doesn't seem to make any difference?
Setting javascriptEnabled = false, I'd expect to:

don't see requests for elements that are dynamically added with Javascript => I do see them
see requests for elements included in  => I don't see them

Unless I'm missing something, there is something wrong with javascriptEnabled

authors: OlivierChirouze mrog

repo: ariya/phantomjs


text:
merge from template-arlac77-github

package.json

chore(deps): add ^6.1.1 remove ^6.1.0 (devDependencies.ava)

Pull Request Test Coverage Report for Build 7710963908
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.825%

Totals

Change from base Build 7710751602:
0.0%

Covered Lines:
195

Relevant Lines:
227

💛  - Coveralls


text:
chore(release): Automated agent release notes (v1.0.31)

Automated PR

@danielGz do you have any idea why I had to manually add date to the front matter section? date is in the template https://github.com/armory-io/agent-k8s/blob/master/.github/workflows/release-notes.yml#L35

No :( that's weird

PR outdated creating anew

authors: armory-astrolabe danielGz

repo: armory/docs


text:
Redesign Front-end

Screen shot for references

Not closing the issue here as these are some of the CSS improvements. There is scope for a lot more design improvements.Most importantly making the site responsive.

@arnav-t Kindly review.

@arc9693 I've left a review.
Also, if you are here from KWoC, please join this GItter channel.
We can further discuss the design there.

Response to suggestions:

 Would really like to keep the title as it is. If change is strictly needed , then OK
 Title size correction - OK
 Readable font for subheadings - OK
 Sidebar looks highlighted with black color also it differentiates the sidebar section as well. Would like you to be more specific regarding changes.
 Gradient  for the highlighted subjects - OK
 Will change the font for uploaded file names

Response to suggestions:

 Would really like to keep the title as it is. If change is strictly needed , then OK
 Title size correction - OK
 Readable font for subheadings - OK
 Sidebar looks highlighted with black color also it differentiates the sidebar section as well. Would like you to be more specific regarding changes.
 Gradient  for the highlighted subjects - OK
 Will change the font for uploaded file names

Response to suggestions:

 Would really like to keep the title as it is. If change is strictly needed , then OK
 Title size correction - OK
 Readable font for subheadings - OK
 Sidebar looks highlighted with black color also it differentiates the sidebar section as well. Would like you to be more specific regarding changes.
 Gradient  for the highlighted subjects - OK
 Will change the font for uploaded file names

@arnav-t
Hope we are good to go now! Kindly review. :smile:

repo: arnav-t/what-slot


text:
Install library into ${prefix}/lib

This is important so that our library-locating machinery can find it properly.

Thanks, I think this is the issue we were running into.

authors: arnavs staticfloat

repo: arnavs/ArpackMKLBuilder


text:
🛑 NWTFV is down

In d000df7, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 5fbd18c.

repo: arnef/status


text:
🛑 NWTFV is down

In 494b7f0, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 095848d.


text:
Error: No Stash Entries found. On a brand new installation.

Syncify Version and Operating System
I am using Syncify v4.0.4 on Mac
Describe the bug
I have 2 Macbooks.
Both use VSCodium (not VS Code).
On Mac1 I installed Syncify and startet uploading ... went OK.
On Mac2 I installed Syncify (no other extension; complete fresh VsCodium) -> Get Error "Keine Stash-Einträge gefunden"
I tried:

public vs. private repo
reset vs. reinitiate
complete uninistall

The public repos is here:
https://github.com/kuddl/vsCodeSettings

This has been fixed in v4.0.5

authors: arnohovhannisyan kuddl

repo: arnohovhannisyan/vscode-syncify


text:
Bundle webapp as AMD for use with require.js

it's nice. Can you make min file so I can use it in NGLView? I am not familiar with JS packaging (there are so many ways :D)
https://github.com/arose/ngl/blob/master/examples/webapp.html#L17-L23

it needs

examples/js/lib/*
examples/js/ui/*
examples/js/gui.js
examples/css/*
examples/fonts/*

it's nice. Can you make min file so I can use it in NGLView?

Needs to be an AMD bundle as far as I can tell.

nglview will be stick with ipywidgets and jupyterlab for now.

authors: arose hainm

repo: arose/ngl

license: mit


text:
Add ball representation similar to VMD's 'VDW'

I'm currently work with code that models proteins as spheres with a fixed radius.  I can visualize these models in VMD using the VDW drawing method. I haven't found anything similar in for nglview. I thought ball+stick could be used but that doesn't allow me to set a defined radius of the balls. Only a value for some spectRatio.

Is the spacefill representation with radiusType: "vdw" what you're after?

Spacefil already looks promising. How can I set the radius? There isn't anything in the docs
As a reference for 1E8L I get the following in VMD with selecting 'name CA', as a drawing method VWD and as spherescale 4.2 (thats the bead radius in Angström).

OK I found that I can do 'radiustype=size' and then set the radius to the value I like.

There are a scale and a radius parameter that work for most structure representations, see https://arose.github.io/ngl/api/global.html#StructureRepresentationParameters
The doc on radiusTyoe is a bit unclear, possible values are size, vdw, sstruc, covalent, and bfactor.
comp.addRepresentation( "spacefill", { radius: 4.6 } )  // will set radiusType to "size"

You beat me :-)

@kain88-de  you meant using radiustype=size in nglview? This is weird. (should be radius_type or radiusType)

I meant radiusType. I just missed the capital letter when writing

@arose the size parameter has Angström as units?

the radius parameter has Angström as units?

yes

authors: arose fredludlow hainm kain88-de


text:
Create a functional authentication system

Description
Add following features to the app-

login page
register page
login required to access courses
password reset functionality
contact us form

Note -
I plan to completely change the login and contact us page of the current project as they lack uniformity with the website.
Screenshots
No response

@ephemeralshay
work on only login and sign up in this PR
do not implement password reset functionality and contact us form

Alright


text:
gazebo not opening with the .so file

gzserver: symbol lookup error: /home/madhu/work/gazebo_map_creator_ws/install/gazebo_map_creator/lib/libgazebo_map_creator.so: undefined symbol: _ZN10gazebo_ros4Node3GetEv

When I try to run gazebo -s libgazebo_map_creator.so myworld.world command I get the above issue.
What could be the issue here?

Looks like you haven't sourced ROS2 env before initiating gazebo launch.
e.g source /opt/ros/<humble|foxy>/setup.bash

I don't think that is the case. I have sourced the environments correctly. But I also have ROS 1 in my environment, could that cause this issue?

I also faced this issue and I too have both ROS 1 (Noetic) and ROS 2 (Foxy) installed on my system. I managed to find a solution which involves modifying the ~/.bashrc file. When I previously installed ROS 1, I ran echo "source /opt/ros/noetic/setup.bash" >> ~/.bashrc in my shell which automatically sources ROS 1 whenever a shell is opened. Hence when sourcing ROS 2, two different versions of ROS are being sourced in the same environment. This results in issues with the rosdep tool, and might also be what's causing this issue wth gzserver.
After opening the ~/.bashrc file and removing the line source /opt/ros/noetic/setup.bash, I created a new workspace and followed the guide again which got it to work.

I also faced this issue and I too have both ROS 1 (Noetic) and ROS 2 (Foxy) installed on my system. I managed to find a solution which involves modifying the ~/.bashrc file. When I previously installed ROS 1, I ran echo "source /opt/ros/noetic/setup.bash" >> ~/.bashrc in my shell which automatically sources ROS 1 whenever a shell is opened. Hence when sourcing ROS 2, two different versions of ROS are being sourced in the same environment. This results in issues with the rosdep tool, and might also be what's causing this issue wth gzserver.
After opening the ~/.bashrc file and removing the line source /opt/ros/noetic/setup.bash, I created a new workspace and followed the guide again which got it to work.

authors: arshadlab madhu-korada webtjs


text:
Update export

Add .fbx and .glft export options (supported by Gazebo Harmonic)
Use the official bpy python package

This packages includes a blender binary so we don't need to install Blender anymore for RoboProp

Refactor export script

@azazdeaz I think this is now ready, do you have anything else to add?
Adds Metadata, as well as the conversion

Oh great! Thanks a lot @tomonorman!!!!!

authors: azazdeaz tomonorman

repo: art-e-fact/RoboProp


text:
Problem: AIPs do not download via the Archivematica Storage Service

Is your feature request related to a problem? Please describe.
Currently when we download an AIP in the Dashboard's UI it comes from Minio, our clients need to be able to download it directly from the Archivematica Storage Service when using Enduro with Archivematica.
Describe the solution you'd like
Change the backend API such that if the preservation system identified in the configuration file is Archivematica, change the download endpoint behavior to use the storage service and not Minio.
Describe alternatives you've considered
We could change/add a button/option on the dashboard to have the option of downloading from the storage service instead of Minio. And we could bypass Enduro and talk directly to Archivematica, or add a new endpoint to Enduro for this.
Additional context
#782

It looks like the legacy Enduro implementation of AIP download is here: https://github.com/artefactual-labs/enduro/blob/cced3fcdbd3eaf5bc1fff610a3da3b7899eba0a2/internal/collection/goa.go#L324

I didn't mean to close the issue. Keith's PR implements a new storage location type based on the ssblob package, but I don't think we have a mechanism yet to enable it when deploying with Archivematica. I believe that locations are currently populated using raw SQL using k8s jobs.

authors: Diogenesoftoronto djjuhasz sevein

repo: artefactual-sdps/enduro


text:
🛑 Matrix (server) is down

In 9ead998, Matrix (server) (https://matrix.artemislena.eu:8448/_matrix/static) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matrix (server) is back up in 4776a26.

repo: artemislena/upptime


text:
🛑 BreezeWiki is down

In c1bc32f, BreezeWiki (https://bw.artemislena.eu) was down:

HTTP code: 502
Response time: 432 ms

Resolved: BreezeWiki is back up in 10bee47 after 10 minutes.


text:
Replace deprecated imp module with importlib

This project's tests uses the imp module which has been deprecated since Python 3.4 and set for removal in 3.12:

Raised PendingDeprecationWarning since 3.4 (2014)
Raised DeprecationWarning since 3.5 (2015)
Updated DeprecationWarning to say removal in 3.12 since 3.10 (2021)
Removal planned for 3.12 (2023)

Python 3.12 is set for release on 2023-10-02 and this library is one of the top 5,000 most-downloaded from PyPI.
Please could you upgrade to use importlib? The imp docs have suggestions on what to use to replace each function and constant.

Closing, this issue has been open for over a year and this repo not updated for 7 years, so looks unmaintained.

repo: arteria/django-compat


text:
MJML support

Hi,
Can you support MJML?
https://github.com/mjmlio/mjml
It seems that you do not support HTML templates generated by MJML.
I can't save my HTML templates generated by MJML.
Thanks,

Really cool, seems like MJML takes care of a lot of stuff that I, probably, will never find time to integrate (eg. conditional tags). I'll definitely take a look

hey, Nicolas from the MJML team here! Don't hesitate if you have any question regarding integrating MJML, happy to help.
Regarding your use case, you might be interested in creating an MJML JSON structure (easy to manipulate) from blocks users drag and drop to then render the full template as responsive HTML.

Thanks @ngarnier for reaching out to me, MJML team made a really great work. I've already started playing around with the framework and I hope to release soon the first release of the plugin :)

@artf, awesome! Just started poking around the codebase this evening thinking about giving this a shot myself (in case you weren't already on it).
I'm thrilled to read this! Guess we all are. :)

@witzig @ngarnier @HLFH
The first release is out https://github.com/artf/grapesjs-mjml
At the moment, works only with few standard components from the MJML library but I think it's ok as a starting point.
Here you can find the demo

authors: HLFH artf ngarnier witzig

repo: artf/grapesjs-preset-newsletter


text:
refactor: Use Python 3.9 type annotations

what.

Refactor codebase to use old-style type annotations like Union and Optional in place of Python 3.10's new | (union) operator.
Update workflows to run tests against Python 3.9, simplify publishing pipeline
Update workflows to install Poetry via github action
Update README and other docs mentioning minimum supported version.

why.
To support still alive Python 3.9 version.
There might be more work needed in order to support earlier versions, I just need this to work under 3.9.
IMHO rewriting this to support Py3.7 is not worth it, as it's going EOL in 9 months. Maybe 3.8 is worth supporting.
references.
Fixes #109
https://endoflife.date/python

FYI @arthurio, @sizfx

@bartelemi Thank you so much, taking a look now.

@bartelemi If you give me permissions to push code I can commit the stuff you missed.

I missed the fact that you wanted me to update the notation in docs as well. I wanted to do similar thing to what fastapi docs have - separate examples for Py3.10 and earlier versions, but I am not familiar with the syntax for that. So I've just updated the syntax to be Py3.9 compatible for now.

I missed the fact that you wanted me to update the notation in docs as well. I wanted to do similar thing to what fastapi docs have - separate examples for Py3.10 and earlier versions, but I am not familiar with the syntax for that. So I've just updated the syntax to be Py3.9 compatible for now.

I don't know the notation either haha, but it's a good idea, I'll look into it.

Feel free to kick off test pipelines and merge this PR if you're happy with it 👍🏻

We'll do, thanks a lot!

authors: arthurio bartelemi

repo: arthurio/fastapi-filter


text:
adding SARS-CoV-2 schemes and adding latest scheme format to all versions

This PR:

adds the SARS-CoV-2 primer schemes which are currently stored here
duplicates reference sequence and primer schemes for Nipah V1 and Ebola V3, and then renames them to conform to the standard file extension used in the other schemes (*.reference.fasta and *.scheme.bed)
adds the new Primal Scheme primer files (BED compatible) to each scheme version in this repo

new extension is *.primer.bed
used a liftover script (provided under ./scripts) to convert from existing scheme data

adds scheme validation via CI (travis)

runs artic-tools validate_vcf on each *primer.bed file in the repo

adds MIT license
adds placeholder for zenodo release archiving

Note: no original files are changed or removed.

@joshquick gave his approval!

repo: artic-network/primer-schemes


text:
Update what-is-artsy.md

Hi, I was just taking a look through your values and noticed a typo. Cheers!

Thank you!

Thanks @dgolant!!

authors: damassi dblandin dgolant

repo: artsy/README


text:
feat: turn-key dev setup.

https://artsyproduct.atlassian.net/browse/PLATFORM-3403
This PR introduces "turn key development environments" pattern to this project, namely the shared configuration pattern.

change setup script into a shell script
make setup script do more, including pulling down shared config from S3
add .foreman to load env files in order
replace dotenv with foreman where applicable
update README

LGTM. No failure for rabbitmq.
Thanks @ovasdi for confirming.

repo: artsy/convection


text:
fix(build): update react native to fix flipper issues

This PR resolves PHIRE-732
Description

Updates react native to patch version that fixes build issues on Xcode 15.3
https://github.com/facebook/react-native/releases/tag/v0.72.12
PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

update react native to fix Xcode 15.3 build issues - Brian

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (update react native to fix Xcode 15.3 build issues - Brian)

  Generated by :no_entry_sign: dangerJS against 6eba09b0d4d5571090bc1f56c4db3eb361a21665

Do we need to follow up on Folio here as well?

yes we do :) : https://artsyproduct.atlassian.net/browse/PHIRE-733

gonna merge, tested that it is building on iOS and Android and think pretty low risk so would like to keep more devs from running into this but let me know if anything needs updates

authors: ArtsyOpenSource brainbicycle damassi

repo: artsy/eigen


text:
[WIP] [MX-279] [MX-280] Artwork tile updates

Paired with @brainbicycle on these. Started as one ticket, but it made sense to do them together I think.
We have a tonne of compiler errors but I wanted to get this PR up for review while I fix them. It's all snake- versus camel-case issues from the Metaphysics v1 -> v2 migration 😞 In 6a5485e I tried to revert the updates we made, but we're now getting errors based on the changed shape of the data (instead of just the casing changes we tried to make to the ArtworkGridItem_artwork fragment). So tomorrow I plan to move to camel case and have to fix a bunch of mock data.
Here's what it looks like:

Fails

:no_entry_sign:
Missing Test Files:

src/lib/Scenes/Home/Components/__tests__/SmallTileRail-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS

this is looking incredible ❤

Reviewed this with @brainbicycle 🎉 #mergeongreen

authors: ArtsyOpenSource ashfurrow ds300


text:
[MSG] Message/Composer

Requirements

[ ] Gallery name (Gallery should be considered as one entity with no consideration as to who the sender is, different from how we handle this in CMS)
[ ] Timestamp
[ ] Message content
[ ] Composer
[ ] Composer error states (failure to send message/retry)

Most of the UI should already exist from other tickets + error state handling: 1 day
We may need to modify/create a specific endpoint on Impulse to send a message: 2 days

create separate ticket around email edge cases and how to represent them in the native chat view

Issue moved to artsy/collector-experience #294 via ZenHub

authors: alloy katarinabatina tayapage6

repo: artsy/emission


text:
ci(smoke-tests): parallelize smoke tests on CI

The type of this PR is: CI
This PR solves WP-111
Description
Following the work done in https://github.com/artsy/integrity/pull/368, this parallelizes our smoke tests in Force in an effort to bring the smoke test runner down by 3min.
cc @artsy/grow-devs

👏👏👏

authors: MounirDhahri damassi

repo: artsy/force


text:
"Unknown function: getcurpos" occurs when using JCimportXXX in older Vim

The following ERROR "Unknown function: getcurpos" occurs when using JCimportXXX (JCimportAdd, JCimportAddI, JCimportsAddMissing and JCimportsRemoveUnused) in Vim 7.4.160, which is included in CentOS/RHEL 7:
Error detected while processing function javacomplete#imports#Add..<SNR>67_SortImports:
line   11:
E117: Unknown function: getcurpos
E15: Invalid expression: getcurpos()
line   21:
E121: Undefined variable: saveCursor
E116: Invalid arguments for function setpos

Error detected while processing function javacomplete#imports#RemoveUnused:
line    6:
E117: Unknown function: getcurpos
E15: Invalid expression: getcurpos()
line   19:
E121: Undefined variable: saveCursor
E15: Invalid expression: saveCursor[1] - len(unused)
line   20:
E121: Undefined variable: saveCursor
E116: Invalid arguments for function setpos

getcurpos() is not available in 7.4.160 because it wasn't added until 7.4.313. I think using getpos('.') instead of getcurpos() resolve this issue.

@msfm
I have no this func,but I can use JCimportAdd,why?

Although the error occurs, adding import statement itself would work. However, your cursor position is moved to the line at the added import statement. Because the function (getcursor()) is called to preserve the original cursor position and get back your cursor position after adding import statement.

my cursor will go back to origin position!

I'm not sure why your cursor goes back to original position without having getcurpos() func and I don't know what's happening on your environment.
Anyway, the error message "Unknown function: getcurpos" was resolved in my environment by the PR#191 which I sent.

I also feal strange,but now I remove the old vim ,and compile from the source,now I am using 7.4.1222

Fixed by #191

authors: artur-shaik msfm wsdjeg

license: Vim


text:
Add neutral element concept to aes generation

Closes #33

📚 Documentation preview 📚: https://arviz-plots--35.org.readthedocs.build/en/35/

Codecov Report
Attention: Patch coverage is 85.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 76.68%. Comparing base (cfa1ebb) to head (1463ac7).

Files
Patch %
Lines

src/arviz_plots/plot_collection.py
83.33%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
+ Coverage   76.65%   76.68%   +0.03%
==========================================
  Files          15       15
  Lines        1281     1287       +6
==========================================
+ Hits          982      987       +5
- Misses        299      300       +1

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

I have to update _get_aes_dict_from_dt and add tests for it.

authors: OriolAbril codecov-commenter

repo: arviz-devs/arviz-plots


text:
test sample data sets

run the tests through to the allelic imbalance step. see whether reference bias disappeared

we will actually have to run these on a much bigger sample size. so I'll close this issue for now


text:
[Snyk] Fix for 1 vulnerabilities

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

frontend/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Cross-site Scripting (XSS) SNYK-JS-WEBPACK-7840298
  157

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)

repo: asabushaban/juice-shop-goof


text:
Code listing CSS bug in some themes when source type is unrecognized

The cerulean and slate themes have a bunch of CSS like this:
.listingblock:hover code.asciidoc:before {
  content: "asciidoc";
}

But if I set my source to a value other than the ones that are listed, like so:
[source,foo,numbered]
.First Foo app
---------------------------------------
begin Foo;
if foo && bar

Then when I hover my mouse over the listing in the preview window, it inserts the name of the language it thinks I'm using in front of the code. In this screenshot it thinks I'm using Ruby:

This also happens if I set my source to html though in that case it tells me I'm using XML:

I tried this with Cerulean, Slate, and Github themes and your example listing. Works for me. Could you please give more details regarding exact versions of Brackets and this plugin you are using?

Sorry, I truncated the code for the sake of posting it here, but the bug doesn't happen with the abbreviated code.  Here's the full code:
[source,foo,numbered]
.First Foo app
---------------------------------------
begin Foo;
if foo && bar
   then
     if foobar == true
     output foo
   else
     if foobar == maybe
     output foo
   else
     if foobar == unknowable
       output foo
   else
     output bar
for each Foo
   print 'foo'
   next;
end Foo.
---------------------------------------

I'm using
Brackets Release 1.4 build 1.4.0-16380 (release 273804eb3)
asciidoc-preview 1.1.6

authors: nerk stallio

repo: asciidoctor/brackets-asciidoc-preview


text:
変数 var, let, const

基本文法 #14

[ ] グローバル変数 ( without var - #25 strict modeに依存 )
[x] var
[x] let
[x] const
[x] 変数名に使える文字 mothereff.in/js-variables
[ ] プロパティ #27

変数とプロパティは一緒に説明すべきかは微妙そう。
オブジェクトの説明のあとになりそう。
この書籍のユースケースでは prefer-const ではいいと思ってるけど、REPLで確かめて見て！ みたいなケースだとletの方が繰り返し定義できて便利である。
ここではなぜ複数あるのかとその意味の違いについてだけ簡潔にやる

JavaScript variables hoisting in details
ES2015の現在とESNextの未来 // Speaker Deck

hoistingについて

http://wirfs-brock.com/allen/talks/viewsource-es2015.pdf
letの良いところの話

JavaScriptにおけるvar/let/constの使い分け

これは閉じてもいいのかな

repo: asciidwango/js-primer


text:
Allow configuring Redis

It would be nice if I could configure the Redis connection so I can connect to my existing Redis cluster instead of hosting a single node on my Asciinema server.

You can set REDIS_URL=redis://1.2.3.4:6379 environment variable. It should be set for both Rails and Sidekiq process. More info here: https://github.com/mperham/sidekiq/wiki/Using-Redis

authors: dasJ sickill