Only run generated quantities when needed for optimizing, sampling, and ADVI

Summary:
Right now,

optimization and ADVI create generated quantities each iteration

sampling creates generated quantities during warmup which aren't needed

Provide options so they're not saved when not needed.
Current Version:
v2.17.1

Are we sure that generated quantities are computed at every step for ADVI? I've just been looking at the source code and get the impression that they are only computed once after the optimisation has terminated. For LBFGS, however, it does seem like they are unnecessarily computed at every step.
Am I right in thinking that they are only computed by the write_array method? This even has a flag which you can set to not compute the generated quantities, so it should be really easy to fix this (based on my first impression).

I don't know what ADVI does.  It doesn't use the L-BFGS in algorithms for its optimization.
Sampling computes generated quantities during warmup whether the warmup iterations are saved or not.
I thought optimization computed generated quantities every iteration, but it should also only need them at the end.
How much are any of these saved values used for debugging?  Probably not much because generated quatnities don't affect sampling.
You'll need to be careful that nothing requires rectangular input for "parameters" (everything dumped out including transformed parameters and generated quantities) in RStan or PyStan.

Huh?  Generated quantities is called only when the parameters are requested
to be written out and that occurs only if the “save_warmup” argument is set
to true,
https://github.com/stan-dev/stan/blob/develop/src/stan/services/util/run_adaptive_sampler.hpp https://github.com/stan-dev/stan/blob/develop/src/stan/services/util/run_adaptive_sampler.hpp
If interfaces other than CmdStan modify this to always save warmup
iterations then this is an interface issue, not a core Stan issue.

On Feb 1, 2018, at 5:16 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:
I don't know what ADVI does. It doesn't use the L-BFGS in algorithms for its optimization.
Sampling computes generated quantities during warmup whether the warmup iterations are saved or not.
I thought optimization computed generated quantities every iteration, but it should also only need them at the end.
How much are any of these saved values used for debugging? Probably not much because generated quatnities don't affect sampling.
You'll need to be careful that nothing requires rectangular input for "parameters" (everything dumped out including transformed parameters and generated quantities) in RStan or PyStan.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/stan-dev/stan/issues/2459#issuecomment-362420626, or mute the thread https://github.com/notifications/unsubscribe-auth/ABdNloleFN8DHTMquS-1AF41kUHQ4nJHks5tQjfDgaJpZM4RjTXD.

On Feb 1, 2018, at 5:36 PM, Michael Betancourt<EMAIL_ADDRESS>wrote:
Huh? Generated quantities is called only when the parameters are requested
to be written out and that occurs only if the “save_warmup” argument is set
to true,

Great.  That's what I think it should do.  I think we were running
into issues where running generated quantities during warmup (I believe
RStan saves warmup by default) led to crashing behavior due to numerical
issues.  I think the right behavior is to write out NaN values if
generated quantities throws an exception, but I don't know if that ever
got merged.
If we can turn off saving warmup, I don't see there's much else
we can do at the interface level.

This issue is supposed to be about optimization and ADVI, which do not have a save warmup flag. Run this
library(rstan)
m <- stan_model(model_code = 'parameters {real y;} model {y ~ normal(0,1);} generated quantities {reject("this gets executed");}')
optimizing(m) # fails on initial evaluation
optimizing(m, save_warmup) # fails due to lack of a save_warmup option
vb(m) # fails after adaptation but before optimization
vb(m, save_warmup) # fails due to lack of a save_warmup option

Could this be an RStan issue? I just don't think I saw this behaviour in CmdStan, either in my experiments or in the source code.

Done. This is the output:
`method = optimize
optimize
algorithm = lbfgs (Default)
lbfgs
init_alpha = 0.001 (Default)
tol_obj = 9.9999999999999998e-13 (Default)
tol_rel_obj = 10000 (Default)
tol_grad = 1e-08 (Default)
tol_rel_grad = 10000000 (Default)
tol_param = 1e-08 (Default)
history_size = 5 (Default)
iter = 2000 (Default)
save_iterations = 0 (Default)
id = 0 (Default)
data
file =  (Default)
init = 2 (Default)
random
seed =<PHONE_NUMBER>
output
file = output.csv (Default)
diagnostic_file =  (Default)
refresh = 100 (Default)
Initial log joint probability = -0.835716
Iter      log prob        ||dx||      ||grad||       alpha      alpha0  # evals  Notes
2  -2.46519e-32       1.16356   2.22045e-16           1           1        5
Exception: this gets executed  (in 'stan/src/test/test-models/good/gqfail.stan' at line 8)`
`method = variational
variational
algorithm = meanfield (Default)
meanfield
iter = 10000 (Default)
grad_samples = 1 (Default)
elbo_samples = 100 (Default)
eta = 1 (Default)
adapt
engaged = 1 (Default)
iter = 50 (Default)
tol_rel_obj = 0.01 (Default)
eval_elbo = 100 (Default)
output_samples = 1000 (Default)
id = 0 (Default)
data
file =  (Default)
init = 2 (Default)
random
seed =<PHONE_NUMBER>
output
file = output.csv (Default)
diagnostic_file =  (Default)
refresh = 100 (Default)

EXPERIMENTAL ALGORITHM:
This procedure has not been thoroughly tested and may be unstable
or buggy. The interface is subject to change.
Gradient evaluation took 0 seconds
1000 transitions using 10 leapfrog steps per transition would take 0 seconds.
Adjust your expectations accordingly!
Begin eta adaptation.
Iteration:   1 / 250 [  0%]  (Adaptation)
Iteration:  50 / 250 [ 20%]  (Adaptation)
Iteration: 100 / 250 [ 40%]  (Adaptation)
Iteration: 150 / 250 [ 60%]  (Adaptation)
Iteration: 200 / 250 [ 80%]  (Adaptation)
Success! Found best value [eta = 1] earlier than expected.
Begin stochastic gradient ascent.
iter             ELBO   delta_ELBO_mean   delta_ELBO_med   notes
100           -0.019             1.000            1.000
200           -0.053             0.822            1.000
300           -0.072             0.633            0.643
400            0.138             0.855            1.000
500           -0.072             1.269            1.000
600           -0.002             6.053            1.521
700           -0.044             5.323            1.000
800            0.110             4.833            1.399
900           -0.000            40.428            1.399
1000            0.111            36.486            1.399
1100           -0.036            36.790            1.521   MAY BE DIVERGING... INSPECT ELBO
1200            0.004            37.650            2.923   MAY BE DIVERGING... INSPECT ELBO
1300           -0.058            37.732            2.923   MAY BE DIVERGING... INSPECT ELBO
1400           -0.007            38.265            4.037   MAY BE DIVERGING... INSPECT ELBO
1500           -0.005            38.034            4.037   MAY BE DIVERGING... INSPECT ELBO
1600            0.038            35.149            1.399   MAY BE DIVERGING... INSPECT ELBO
1700           -0.080            35.201            1.471   MAY BE DIVERGING... INSPECT ELBO
1800           -0.021            35.350            2.888   MAY BE DIVERGING... INSPECT ELBO
1900            0.023             3.019            1.885   MAY BE DIVERGING... INSPECT ELBO
2000            0.050             2.972            1.885   MAY BE DIVERGING... INSPECT ELBO
2100           -0.020             2.916            1.885   MAY BE DIVERGING... INSPECT ELBO
2200           -0.161             2.079            1.471   MAY BE DIVERGING... INSPECT ELBO
2300           -0.061             2.138            1.667   MAY BE DIVERGING... INSPECT ELBO
2400           -0.164             1.516            1.471   MAY BE DIVERGING... INSPECT ELBO
2500            0.002            12.296            1.667   MAY BE DIVERGING... INSPECT ELBO
2600            0.042            12.280            1.667   MAY BE DIVERGING... INSPECT ELBO
2700            0.069            12.172            1.667   MAY BE DIVERGING... INSPECT ELBO
2800            0.006            12.913            1.667   MAY BE DIVERGING... INSPECT ELBO
2900            0.100            12.818            0.964   MAY BE DIVERGING... INSPECT ELBO
3000            0.081            12.789            0.964   MAY BE DIVERGING... INSPECT ELBO
3100            0.050            12.504            0.939   MAY BE DIVERGING... INSPECT ELBO
3200           -0.042            12.636            0.964   MAY BE DIVERGING... INSPECT ELBO
3300            0.175            12.593            0.964   MAY BE DIVERGING... INSPECT ELBO
3400           -0.012            14.151            1.238   MAY BE DIVERGING... INSPECT ELBO
3500           -0.024             3.362            0.964   MAY BE DIVERGING... INSPECT ELBO
3600            0.087             3.393            1.238   MAY BE DIVERGING... INSPECT ELBO
3700            0.002             6.993            1.276   MAY BE DIVERGING... INSPECT ELBO
3800           -0.144             6.064            1.238   MAY BE DIVERGING... INSPECT ELBO
3900           -0.028             6.391            1.276   MAY BE DIVERGING... INSPECT ELBO
4000           -0.109             6.442            1.276   MAY BE DIVERGING... INSPECT ELBO
4100           -0.137             6.399            1.276   MAY BE DIVERGING... INSPECT ELBO
4200            0.098             6.419            1.276   MAY BE DIVERGING... INSPECT ELBO
4300            0.133             6.321            1.276   MAY BE DIVERGING... INSPECT ELBO
4400            0.050             4.867            1.276   MAY BE DIVERGING... INSPECT ELBO
4500            0.048             4.818            1.276   MAY BE DIVERGING... INSPECT ELBO
4600            0.108             4.746            1.016   MAY BE DIVERGING... INSPECT ELBO
4700           -0.030             1.567            1.016   MAY BE DIVERGING... INSPECT ELBO
4800            0.004             2.247            1.667   MAY BE DIVERGING... INSPECT ELBO
4900            0.065             1.920            0.932   MAY BE DIVERGING... INSPECT ELBO
5000           -0.105             2.007            1.615   MAY BE DIVERGING... INSPECT ELBO
5100           -0.002             6.202            1.667   MAY BE DIVERGING... INSPECT ELBO
5200            0.058             6.067            1.615   MAY BE DIVERGING... INSPECT ELBO
5300            0.011             6.467            1.667   MAY BE DIVERGING... INSPECT ELBO
5400           -0.073             6.416            1.615   MAY BE DIVERGING... INSPECT ELBO
5500            0.105             6.582            1.690   MAY BE DIVERGING... INSPECT ELBO
5600           -0.073             6.770            2.433   MAY BE DIVERGING... INSPECT ELBO
5700           -0.126             6.351            1.690   MAY BE DIVERGING... INSPECT ELBO
5800           -0.064             5.665            1.615   MAY BE DIVERGING... INSPECT ELBO
5900           -0.123             5.619            1.615   MAY BE DIVERGING... INSPECT ELBO
6000            0.011             6.644            1.690   MAY BE DIVERGING... INSPECT ELBO
6100            0.075             2.513            1.153   MAY BE DIVERGING... INSPECT ELBO
6200           -0.005             4.042            1.690   MAY BE DIVERGING... INSPECT ELBO
6300            0.052             3.725            1.153   MAY BE DIVERGING... INSPECT ELBO
6400            0.052             3.611            1.095   MAY BE DIVERGING... INSPECT ELBO
6500            0.024             3.561            1.095   MAY BE DIVERGING... INSPECT ELBO
6600            0.047             3.367            0.952   MAY BE DIVERGING... INSPECT ELBO
6700            0.034             3.362            0.952   MAY BE DIVERGING... INSPECT ELBO
6800           -0.046             3.442            1.095   MAY BE DIVERGING... INSPECT ELBO
6900           -0.150             3.464            1.095   MAY BE DIVERGING... INSPECT ELBO
7000            0.035             2.812            1.095   MAY BE DIVERGING... INSPECT ELBO
7100            0.044             2.749            1.095   MAY BE DIVERGING... INSPECT ELBO
7200           -0.123             1.252            1.095   MAY BE DIVERGING... INSPECT ELBO
7300            0.065             1.432            1.188   MAY BE DIVERGING... INSPECT ELBO
7400           -0.000           461.421            1.360   MAY BE DIVERGING... INSPECT ELBO
7500            0.059           461.402            1.360   MAY BE DIVERGING... INSPECT ELBO
7600           -0.086           461.521            1.682   MAY BE DIVERGING... INSPECT ELBO
7700            0.035           461.829            1.752   MAY BE DIVERGING... INSPECT ELBO
7800           -0.007           462.243            2.893   MAY BE DIVERGING... INSPECT ELBO
7900           -0.033           462.251            2.893   MAY BE DIVERGING... INSPECT ELBO
8000           -0.018           461.798            1.682   MAY BE DIVERGING... INSPECT ELBO
8100           -0.028           461.812            1.682   MAY BE DIVERGING... INSPECT ELBO
8200           -0.034           461.693            1.682   MAY BE DIVERGING... INSPECT ELBO
8300           -0.235           461.489            1.000   MAY BE DIVERGING... INSPECT ELBO
8400           -0.016             2.857            1.000   MAY BE DIVERGING... INSPECT ELBO
8500            0.086             2.875            1.187   MAY BE DIVERGING... INSPECT ELBO
8600            0.037             2.837            1.187   MAY BE DIVERGING... INSPECT ELBO
8700           -0.080             2.639            1.187   MAY BE DIVERGING... INSPECT ELBO
8800            0.082             2.249            1.187   MAY BE DIVERGING... INSPECT ELBO
8900            0.047             2.243            1.187   MAY BE DIVERGING... INSPECT ELBO
9000           -0.042             2.375            1.301   MAY BE DIVERGING... INSPECT ELBO
9100            0.010             2.867            1.467   MAY BE DIVERGING... INSPECT ELBO
9200           -0.080             2.963            1.467   MAY BE DIVERGING... INSPECT ELBO
9300           -0.068             2.895            1.467   MAY BE DIVERGING... INSPECT ELBO
9400           -0.024             1.722            1.467   MAY BE DIVERGING... INSPECT ELBO
9500           -0.198             1.691            1.467   MAY BE DIVERGING... INSPECT ELBO
9600           -0.014             2.844            1.838   MAY BE DIVERGING... INSPECT ELBO
9700           -0.146             2.787            1.838   MAY BE DIVERGING... INSPECT ELBO
9800            0.054             2.958            1.838   MAY BE DIVERGING... INSPECT ELBO
9900            0.066             2.902            1.838   MAY BE DIVERGING... INSPECT ELBO
10000           -0.019             3.132            1.838   MAY BE DIVERGING... INSPECT ELBO
Informational Message: The maximum number of iterations is reached! The algorithm may not have converged.
This variational approximation is not guaranteed to be meaningful.
Exception: this gets executed  (in 'stan/src/test/test-models/good/gqfail.stan' at line 8)`

The vb seems different than what I got in rstan, but that may have just
been a random failure. The optimization is what Andrew has been complaining
about for months if not years. He wants it to be faster than literally
every other optimization algorithm, which it will never be, but one reason
is that it executes generating quantities at all the suboptimal points,
which is why you get that exception after 1 function evaluation.
On Fri, Feb 2, 2018 at 3:12 PM, Matthijs Vákár<EMAIL_ADDRESS>wrote:

Done. This is the output:
`method = optimize
optimize
algorithm = lbfgs (Default)
lbfgs
init_alpha = 0.001 (Default)
tol_obj = 9.9999999999999998e-13 (Default)
tol_rel_obj = 10000 (Default)
tol_grad = 1e-08 (Default)
tol_rel_grad = 10000000 (Default)
tol_param = 1e-08 (Default)
history_size = 5 (Default)
iter = 2000 (Default)
save_iterations = 0 (Default)
id = 0 (Default)
data
file = (Default)
init = 2 (Default)
random
seed =<PHONE_NUMBER>
output
file = output.csv (Default)
diagnostic_file = (Default)
refresh = 100 (Default)
Initial log joint probability = -0.835716
Iter log prob ||dx|| ||grad|| alpha alpha0 # evals Notes
2 -2.46519e-32 1.16356 2.22045e-16 1 1 5
Exception: this gets executed (in 'stan/src/test/test-models/good/gqfail.stan'
at line 8)`
`method = variational
variational
algorithm = meanfield (Default)
meanfield
iter = 10000 (Default)
grad_samples = 1 (Default)
elbo_samples = 100 (Default)
eta = 1 (Default)
adapt
engaged = 1 (Default)
iter = 50 (Default)
tol_rel_obj = 0.01 (Default)
eval_elbo = 100 (Default)
output_samples = 1000 (Default)
id = 0 (Default)
data
file = (Default)
init = 2 (Default)
random
seed =<PHONE_NUMBER>
output
file = output.csv (Default)
diagnostic_file = (Default)
refresh = 100 (Default)
EXPERIMENTAL ALGORITHM:
This procedure has not been thoroughly tested and may be unstable
or buggy. The interface is subject to change.
Gradient evaluation took 0 seconds
1000 transitions using 10 leapfrog steps per transition would take 0
seconds.
Adjust your expectations accordingly!
Begin eta adaptation.
Iteration: 1 / 250 [ 0%] (Adaptation)
Iteration: 50 / 250 [ 20%] (Adaptation)
Iteration: 100 / 250 [ 40%] (Adaptation)
Iteration: 150 / 250 [ 60%] (Adaptation)
Iteration: 200 / 250 [ 80%] (Adaptation)
Success! Found best value [eta = 1] earlier than expected.
Begin stochastic gradient ascent.
iter ELBO delta_ELBO_mean delta_ELBO_med notes
100 -0.019 1.000 1.000
200 -0.053 0.822 1.000
300 -0.072 0.633 0.643
400 0.138 0.855 1.000
500 -0.072 1.269 1.000
600 -0.002 6.053 1.521
700 -0.044 5.323 1.000
800 0.110 4.833 1.399
900 -0.000 40.428 1.399
1000 0.111 36.486 1.399
1100 -0.036 36.790 1.521 MAY BE DIVERGING... INSPECT ELBO
1200 0.004 37.650 2.923 MAY BE DIVERGING... INSPECT ELBO
1300 -0.058 37.732 2.923 MAY BE DIVERGING... INSPECT ELBO
1400 -0.007 38.265 4.037 MAY BE DIVERGING... INSPECT ELBO
1500 -0.005 38.034 4.037 MAY BE DIVERGING... INSPECT ELBO
1600 0.038 35.149 1.399 MAY BE DIVERGING... INSPECT ELBO
1700 -0.080 35.201 1.471 MAY BE DIVERGING... INSPECT ELBO
1800 -0.021 35.350 2.888 MAY BE DIVERGING... INSPECT ELBO
1900 0.023 3.019 1.885 MAY BE DIVERGING... INSPECT ELBO
2000 0.050 2.972 1.885 MAY BE DIVERGING... INSPECT ELBO
2100 -0.020 2.916 1.885 MAY BE DIVERGING... INSPECT ELBO
2200 -0.161 2.079 1.471 MAY BE DIVERGING... INSPECT ELBO
2300 -0.061 2.138 1.667 MAY BE DIVERGING... INSPECT ELBO
2400 -0.164 1.516 1.471 MAY BE DIVERGING... INSPECT ELBO
2500 0.002 12.296 1.667 MAY BE DIVERGING... INSPECT ELBO
2600 0.042 12.280 1.667 MAY BE DIVERGING... INSPECT ELBO
2700 0.069 12.172 1.667 MAY BE DIVERGING... INSPECT ELBO
2800 0.006 12.913 1.667 MAY BE DIVERGING... INSPECT ELBO
2900 0.100 12.818 0.964 MAY BE DIVERGING... INSPECT ELBO
3000 0.081 12.789 0.964 MAY BE DIVERGING... INSPECT ELBO
3100 0.050 12.504 0.939 MAY BE DIVERGING... INSPECT ELBO
3200 -0.042 12.636 0.964 MAY BE DIVERGING... INSPECT ELBO
3300 0.175 12.593 0.964 MAY BE DIVERGING... INSPECT ELBO
3400 -0.012 14.151 1.238 MAY BE DIVERGING... INSPECT ELBO
3500 -0.024 3.362 0.964 MAY BE DIVERGING... INSPECT ELBO
3600 0.087 3.393 1.238 MAY BE DIVERGING... INSPECT ELBO
3700 0.002 6.993 1.276 MAY BE DIVERGING... INSPECT ELBO
3800 -0.144 6.064 1.238 MAY BE DIVERGING... INSPECT ELBO
3900 -0.028 6.391 1.276 MAY BE DIVERGING... INSPECT ELBO
4000 -0.109 6.442 1.276 MAY BE DIVERGING... INSPECT ELBO
4100 -0.137 6.399 1.276 MAY BE DIVERGING... INSPECT ELBO
4200 0.098 6.419 1.276 MAY BE DIVERGING... INSPECT ELBO
4300 0.133 6.321 1.276 MAY BE DIVERGING... INSPECT ELBO
4400 0.050 4.867 1.276 MAY BE DIVERGING... INSPECT ELBO
4500 0.048 4.818 1.276 MAY BE DIVERGING... INSPECT ELBO
4600 0.108 4.746 1.016 MAY BE DIVERGING... INSPECT ELBO
4700 -0.030 1.567 1.016 MAY BE DIVERGING... INSPECT ELBO
4800 0.004 2.247 1.667 MAY BE DIVERGING... INSPECT ELBO
4900 0.065 1.920 0.932 MAY BE DIVERGING... INSPECT ELBO
5000 -0.105 2.007 1.615 MAY BE DIVERGING... INSPECT ELBO
5100 -0.002 6.202 1.667 MAY BE DIVERGING... INSPECT ELBO
5200 0.058 6.067 1.615 MAY BE DIVERGING... INSPECT ELBO
5300 0.011 6.467 1.667 MAY BE DIVERGING... INSPECT ELBO
5400 -0.073 6.416 1.615 MAY BE DIVERGING... INSPECT ELBO
5500 0.105 6.582 1.690 MAY BE DIVERGING... INSPECT ELBO
5600 -0.073 6.770 2.433 MAY BE DIVERGING... INSPECT ELBO
5700 -0.126 6.351 1.690 MAY BE DIVERGING... INSPECT ELBO
5800 -0.064 5.665 1.615 MAY BE DIVERGING... INSPECT ELBO
5900 -0.123 5.619 1.615 MAY BE DIVERGING... INSPECT ELBO
6000 0.011 6.644 1.690 MAY BE DIVERGING... INSPECT ELBO
6100 0.075 2.513 1.153 MAY BE DIVERGING... INSPECT ELBO
6200 -0.005 4.042 1.690 MAY BE DIVERGING... INSPECT ELBO
6300 0.052 3.725 1.153 MAY BE DIVERGING... INSPECT ELBO
6400 0.052 3.611 1.095 MAY BE DIVERGING... INSPECT ELBO
6500 0.024 3.561 1.095 MAY BE DIVERGING... INSPECT ELBO
6600 0.047 3.367 0.952 MAY BE DIVERGING... INSPECT ELBO
6700 0.034 3.362 0.952 MAY BE DIVERGING... INSPECT ELBO
6800 -0.046 3.442 1.095 MAY BE DIVERGING... INSPECT ELBO
6900 -0.150 3.464 1.095 MAY BE DIVERGING... INSPECT ELBO
7000 0.035 2.812 1.095 MAY BE DIVERGING... INSPECT ELBO
7100 0.044 2.749 1.095 MAY BE DIVERGING... INSPECT ELBO
7200 -0.123 1.252 1.095 MAY BE DIVERGING... INSPECT ELBO
7300 0.065 1.432 1.188 MAY BE DIVERGING... INSPECT ELBO
7400 -0.000 461.421 1.360 MAY BE DIVERGING... INSPECT ELBO
7500 0.059 461.402 1.360 MAY BE DIVERGING... INSPECT ELBO
7600 -0.086 461.521 1.682 MAY BE DIVERGING... INSPECT ELBO
7700 0.035 461.829 1.752 MAY BE DIVERGING... INSPECT ELBO
7800 -0.007 462.243 2.893 MAY BE DIVERGING... INSPECT ELBO
7900 -0.033 462.251 2.893 MAY BE DIVERGING... INSPECT ELBO
8000 -0.018 461.798 1.682 MAY BE DIVERGING... INSPECT ELBO
8100 -0.028 461.812 1.682 MAY BE DIVERGING... INSPECT ELBO
8200 -0.034 461.693 1.682 MAY BE DIVERGING... INSPECT ELBO
8300 -0.235 461.489 1.000 MAY BE DIVERGING... INSPECT ELBO
8400 -0.016 2.857 1.000 MAY BE DIVERGING... INSPECT ELBO
8500 0.086 2.875 1.187 MAY BE DIVERGING... INSPECT ELBO
8600 0.037 2.837 1.187 MAY BE DIVERGING... INSPECT ELBO
8700 -0.080 2.639 1.187 MAY BE DIVERGING... INSPECT ELBO
8800 0.082 2.249 1.187 MAY BE DIVERGING... INSPECT ELBO
8900 0.047 2.243 1.187 MAY BE DIVERGING... INSPECT ELBO
9000 -0.042 2.375 1.301 MAY BE DIVERGING... INSPECT ELBO
9100 0.010 2.867 1.467 MAY BE DIVERGING... INSPECT ELBO
9200 -0.080 2.963 1.467 MAY BE DIVERGING... INSPECT ELBO
9300 -0.068 2.895 1.467 MAY BE DIVERGING... INSPECT ELBO
9400 -0.024 1.722 1.467 MAY BE DIVERGING... INSPECT ELBO
9500 -0.198 1.691 1.467 MAY BE DIVERGING... INSPECT ELBO
9600 -0.014 2.844 1.838 MAY BE DIVERGING... INSPECT ELBO
9700 -0.146 2.787 1.838 MAY BE DIVERGING... INSPECT ELBO
9800 0.054 2.958 1.838 MAY BE DIVERGING... INSPECT ELBO
9900 0.066 2.902 1.838 MAY BE DIVERGING... INSPECT ELBO
10000 -0.019 3.132 1.838 MAY BE DIVERGING... INSPECT ELBO
Informational Message: The maximum number of iterations is reached! The
algorithm may not have converged.
This variational approximation is not guaranteed to be meaningful.
Exception: this gets executed (in 'stan/src/test/test-models/good/gqfail.stan'
at line 8)`
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/issues/2459#issuecomment-362693906, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADOrqiItbP-1LFSr50EywCJ08ns9VHbAks5tQ2wvgaJpZM4RjTXD
.

OK so is the behaviour of ADVI as intended?
For LBFGS, what's wrong about the current behaviour? It takes 5 steps before it's done optimising and then evaluates the GQs, right? Based on the source code, it should only evaluate GQs once, after it's done optimising.

I think ADVI is as intended. For LBFGS, if you change the generated quantities to a print message rather than a reject, in CmdStan it is only printing once at the end. But in rstan, it is printing multiple times before it reaches the optimum despite the C++ just calling
        stan::services::optimize::lbfgs(model, *init_context_ptr,
                                          random_seed, id, init_radius,
                                          history_size,
                                          init_alpha,
                                          tol_obj,
                                          tol_rel_obj,
                                          tol_grad,
                                          tol_rel_grad,
                                          tol_param,
                                          num_iterations,
                                          save_iterations,
                                          refresh,
                                          interrupt, logger,
                                          init_writer, sample_writer);

Which of those arguments is supposed to turn off generated quantities at suboptimal points during warmup?

Related to #2355


Modularize generated lib.rs

Description
There are two motivations for this ticket:
The generated lib.rs file is getting rather big and unweildy. The code can logically be broken down into modules and so it makes sense to do that. It would lead to a more readable/navigatable file.
We still have the possibility of name collisions because of the way JS/Python imports work. For example, if a developer imports the managementCanister, they also get all the types/structs/enums that it uses behind the scenes in Rust, whether they use them or not. We can likely prevent this problem by embracing modules.
We already attempted some of this before. See https://github.com/demergent-labs/azle/pull/985 and https://github.com/demergent-labs/cdk_framework/pull/64. However, we encountered many problems with generics, and knowing which prefix to add at which level (See https://github.com/demergent-labs/azle/pull/985#issuecomment-1502334243).
This is likely going to be a cross-repository problem/solution, with some changes implemented in the CDK Framework, and some in Azle/Kybra.

Moved to the cdk_framework: https://github.com/demergent-labs/cdk_framework/issues/78


Search Filters are lost after sorting or change page.

I don't know if I'm doing something wrong but I have a server side ajax controller that sorts, page and filter based on request parameters.
  		$("#grid").jsGrid("search", filter).done(function() {
  		   console.log("filtering completed");
  		});

On this call, search is working correctly but If i sort using the column header or change page the filter is lost. (paging and sorting is working okey without filters.

I guess you have pageLoading: true. In this case changing a page or sorting requires reloading all data. Where filter data are coming from? Do you have a filter row? If not, then you can pass your filter to server right in the controller.loadData method. If you have filter row, then the values of filtering inputs should be set.
As explained in this issue https://github.com/tabalinas/jsgrid/issues/81

For now you should restore the filter directly with jQuery (select elements by .jsgrid-filter-row and set values to inputs). Then you can call sort and filter with sorting will be applied.

Yes, I have pageLoading: true . I don't use filter rows. I'm calling programmatic the method    $("#grid").jsGrid("search", filter) with a filter object I build (with extra parameters for the server-side controller), then inside the loaddata function I pass it to the server with ajax.
   ...
   pageLoading: true,
   controller: {
          loadData: function(filter) {
               jQuery.extend(true, filter, savedSearchFilter);
               var data=$.ajax({
                 url: "/listJson",
                data: filter,
                dataType: "json",
                async: false,
            });
            return {
                data: data.responseJSON.rows,
                itemsCount: data.responseJSON.total
             };
     }
     ...

But when I click on the pager or a column header for sorting the loaddata method is called again but the filters I used on the search method are lost. So for now as a workaround I am saving in the savedSearchFilter object before calling search and then extending inside loaddata.

Yes, what you are doing I guess is the best workaround. Your scenario just was not considered - having filtering but turn off filter row.

Looks like the method causing the trouble is this one
sort: function() {     return this._grid.loadData(); }
It calls loadData() without parameters.
But it's still not fixed in the newest version.


How to achieve elementwise convolution for two tensors?

In my problem, I want to convolve two tensors in my neural network model.
The shape of two tensors is [None, 2, 1], [None, 3, 1] respectively. The axis with dimension None means the batch size of the input tensor. For each sample in batch, I want to convolve the two tensors with shape [2, 1] and [3, 1].
However, the tf.nn.conv1d in TensorFlow can only convolve the input with a fixed kernel. Is there any function that can support the convolution of two tensors according to the batch size axis, similar to the tf.multiply which can multiply two tensors for each sample or just elementwise multiplication.

@bugzhu ,
Hi, can you please provide a standalone code used?Thanks!

The code I ran can be simplified as follows:
input_signal = Input(shape=(L, M), name='input_signal')
input_h = Input(shape=(N), name='input_h')
faded= Lambda(lambda x: tf.nn.conv1d(input, x))(input_h)

What I want to do is that the sample of input_signal can be convolved by the sample of input_h with the same index. However, it just shows my pure idea which can not be able to run in the env. My question is that how I can modify the code to enable the input tensor can be convolved with another input tensor for every sample in the batch.

This is not Build/Installation or Bug/Performance issue. Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions. GitHub is mainly for addressing bugs in installation and performance. Thanks!


Syntax highlighting and minor style updates

This PR encompasses the following:

[x] Add stylesheets required for syntax-highlighting in Github pages.
( Sourced from here )
[x] Add styles for nested lists (e.g. in Table of Contents)
[x] Make images within a document / page responsive.

N.B. The other changes were unintentionally generated by compass watch

Code looks good, I'll test it out tomorrow when I get a chance. Thanks for the addition

Works great. Merging.


Test notification system for setting up deactivate command

Refs: #22121

[x] windows @joyceerhl
[x] linux @sbatten
[ ] macOS @aiday-mar

Complexity: 5
Create Issue

Requirements

Python extension pre-release & VS Code Insiders
Basic terminal shell types, please install if necessary and tick once tested:

Windows:

[x] cmd
[x] powershell
[x] powershellcore

Linux (our codespaces already have these installed):

[x] bash
[x] zsh
[x] fish

macOS :

[ ] bash
[ ] zsh
[ ] powershellcore (no need to test this if powershellcore on Windows is tested)

Background
Traditionally, activation script (<venv>/<bin>/activate) was run to activate terminals, which registered the deactivate command as well. But now that we're using environment variables to activate terminals instead, deactivate command is broken as it never gets registered.
To make it work, this we added a notification system which helps user register the "deactivate" command in their shell init script.
Verification

Add following to user settings and reload window:

"python.experiments.optInto": ["pythonTerminalEnvVarActivation"]

Open a workspace folder and activate Python extension by opening a Python file.

Use Create environment command to select a venv

Loop -> Do the following for all terminal shell types:

Open a new terminal.
Make sure terminal is activated using the selected environment. Run the following in terminal:python -c"import sys;print(sys.executable)"

Output should contain the path to interpreter selected. For eg. for .venv it looks something like:C:\Users\karraj\OneDrive - Microsoft\Desktop\folders\crap\.venv\Scripts\python.exe

Run "deactivate" command in terminal, a similar notification should show up:

Verify clicking "learn more" points to appropriate wiki.
After following through with the notification, ensure deactivate command works:

Change the default shell in your OS using Terminal: Select Default Profile, say bash->fish

So I was doing the above steps in a bash terminal and I saw the notification which appears in the image below. I was wondering if it is intended that from a bash shell, VS Code suggests to modify the .zshrc and not the .bashrc? I have limited knowledge in shell types, so I am just wondering.

I was following the steps but I am not able to deactivate the env with deactivate. I opened an issue about it. I think I may be not following the steps correctly?

it all worked for me, fwiw I totally missed the "Tip" in the linked document so I was a bit confused about the file script being populated automatically.

@aiday-mar, Not to worry, this is expected for bash on newer macOS. But it should work for zsh or powershellCore, if not please open an issue regarding the same.

@sbatten Thanks! Maybe I should not quote that? I was trying to follow what VS Code docs generally does for tips. Feel free to edit the Wiki link.


Process package level annotations

Added configured packages to the metadata sources to be able to process package-level annotations.

Thanks @didiez !!


Revert to allowing auto-advance selects to trigger form submission

In this PR https://github.com/dimagi/commcare-odk/pull/1126, I changed the behavior of auto-advance widgets to NOT perform an auto-advance if it is the last question in the form, so that auto-advancing would no longer trigger an automatic form submission. My thinking being that nothing should trigger a form submission other than a user explicitly pressing the submit button. However, @phillipm brought up the issue that some existing users (namely Ray it sounds like) are currently relying on this functionality in their apps, and would be upset to discover it has changed.
On principle, I think my reasoning is technically correct, but given the reality that app builders are very unlikely to use the auto-advance setting on a question unless they know what they're doing and are going to explicitly train their users accordingly, it also seems fine to leave the old functionality. Just wanted to check if anyone else has strong opinions on what the right thing to do here is, before I revert the change (cc: @ctsims @wpride @amsagoff).

I thought we decided that we explicitly wanted people to click the green check mark to submit forms in the new UI. Allowing workarounds seems against that

I think we should get the opinion of more people; seems like a change that 3 devs shouldn't be making without consulting the product team or even users.

That's fine with me, although we probably need to make a short-term decision sooner than that, for 2.27. Left as it is now, the auto-advance to submit a form will be disabled. If we want to leave the old behavior, this PR should get merged for now.

I agree with @amstone326 's reasoning here. Curious to hear more about how Ray/others are relying on this, and then we can make a call on whether we want to productize that workflow or just support it for legacy projects.

Reached out to Ray. I'll report back with his response.

@phillipm Did you hear back from Ray on this?

Ray is all set. Closing this out, thanks for reconsidering this.


add: Log parser for renderer

Issue  #1
Added log-parser function.

Codecov Report

Merging #5 (16a0ecc) into main (2e73bf9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

Continue to review full report at Codecov.

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


Azure Lore logic

There is currently no SC logic for Azure Lore being active
https://www.bg-wiki.com/ffxi/Azure_Lore

should be fixed in 1.10


Optimise distance length 258 edge case

Distance codes with a length of 258 are usually encoded with code 285. However, it's technically possible to encode these with code 284, as a length of 227 (base length) + 31 (extra bits). This may not be legal according to the Deflate specification, and it's not considered good practice (Mark Adler has stated "In any case, a self-respecting deflate compressor should never produce [this code]."). deft4j currently misses two optimisations related to this:

[ ] Trying to replace code 285 with code 284 if it saves space (possibly not spec legal)
[ ] Trying to replace code 284 (with a length of 258) with code 285 if it saves space (spec legal)

See #1 for previous discussion.

Perhaps add the parameter switch -cautious (vs -reckless!) to cover this stricter conformance and for #2 ?

Perhaps add the parameter switch -cautious (vs -reckless!) to cover this stricter conformance and for #2 ?

I think options like that would be a good idea. I might keep these two optimisations behind seperate switches, because issues related to #2 are from decoders which can't decode certain valid deflate streams, while issues related to this would be from creating possibly standard non-compliant streams.


Generate carpetplots even if MNI is not one of the output spaces

Right now, as it needs an atlas to grab labels from, this output space is necessary.

We should consider making a separate normalize flag, that ensures the T1-MNI transform gets calculated, even if no outputs are in that space. AROMA, SyN-SDC and now carpetplots all require this transform to exist.

Actually, I guess if carpetplots are always produced, then it's even easier: don't ever disable T1w-MNI registration, even if we don't save the registered series as derivatives.

That has been my temptation forever. But #808.

In that case, does it make sense to do EPI-MNI directly? The templates exist.

True that.

I believe MNI152NLin2009cAsym is automatically included as an internal transform target at this point, so I think this can be closed.

It is.


Gradle error: D8: Program type already present

I'm not sure what was changed, but I suddenly couldn't run my app on Android devices. I've already tried flutter clean. Please see the console output below. Thanks!
$ flutter run
Launching lib/main.dart on Nexus 5 in debug mode...
Initializing gradle...                                       0.9s
Resolving dependencies...                                    0.9s
Running 'gradlew assembleDebug'...
D8: Program type already present: com.example.perfdiagnosisdemo.MainActivity
java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/13, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/14, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/externalLibsDexMerger/debug/0
        at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1431)
        at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
        at java.util.concurrent.ForkJoinTask.externalAwaitDone(ForkJoinTask.java:326)
        at java.util.concurrent.ForkJoinTask.doJoin(ForkJoinTask.java:391)
        at java.util.concurrent.ForkJoinTask.join(ForkJoinTask.java:719)
        at com.google.common.collect.ImmutableList.forEach(ImmutableList.java:397)
        at com.android.build.gradle.internal.transforms.DexMergerTransform.transform(DexMergerTransform.java:221)
        at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:221)
        at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:217)
        at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102)
        at com.android.build.gradle.internal.pipeline.TransformTask.transform(TransformTask.java:212)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
        at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:46)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:121)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:110)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
        at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
        at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/13, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/14, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/externalLibsDexMerger/debug/0
        at com.android.builder.dexing.D8DexArchiveMerger.getExceptionToRethrow(D8DexArchiveMerger.java:124)
        at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:109)
        at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java:101)
        at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java:36)
        at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1424)
        ... 57 more
Caused by: com.android.tools.r8.CompilationFailedException: Compilation failed to complete
        at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:76)
        at com.android.tools.r8.utils.ExceptionUtils.withD8CompilationHandler(ExceptionUtils.java:45)
        at com.android.tools.r8.D8.run(D8.java:67)
        at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:107)
        ... 60 more
Caused by: com.android.tools.r8.utils.AbortException
        at com.android.tools.r8.utils.Reporter.failIfPendingErrors(Reporter.java:77)
        at com.android.tools.r8.utils.Reporter.fatalError(Reporter.java:58)
        at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:67)
        ... 63 more

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithDexMergerForDebug'.
> com.android.build.api.transform.TransformException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/13, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/dexBuilder/debug/14, /Users/taodong/Code/flutter_projects/perf_diagnosis_demo/build/app/intermediates/transforms/externalLibsDexMerger/debug/0

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s                                                                                3.3s
Gradle build failed: 1

== Version Info ==
[✓] Flutter (Channel master, v0.5.9-pre.79, on Mac OS X 10.13.6 17G65, locale en-US)
    • Flutter version 0.5.9-pre.79 at /Users/taodong/flutter
    • Framework revision 3a4ae280e3 (61 minutes ago), 2018-08-17 15:02:39 -0700
    • Engine revision 4ee648914f
    • Dart version 2.1.0-dev.0.0.flutter-be6309690f

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/taodong/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4, Build version 9F1027a
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 27.1.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Community Edition (version 2018.1.6)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 26.0.2
    • Dart plugin version 181.4892.1

[!] VS Code (version 1.25.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected devices (1 available)
    • Nexus 5 • 07e84ccb010aa11a • android-arm • Android 6.0.1 (API 23)

I solved it by deleting the android folder in my project and rerun flutter create.

I solved it by deleting the android folder in my project and rerun flutter create.

Its flutter create.

Re-creating the project with flutter-create didn't work for me. I have the sample app (that is automatically created when starting a project) only with the following dependencies added :
dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.2
  firebase_storage: 2.1.1+2
  image_picker: 0.6.0+2

I solved the problem buy running following 2 commands:
1- flutter clean
2- flutter run
that's all.

D8: Program type already present: androidx.work.Configuration$Builder
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: androidx.work.Configuration$Builder

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Gradle task assembleDebug failed with exit code 1
same type of error but any of above solutions didn't work for me..

In my case, I re-created the project to enable web-support. So I did
flutter create .
This ended up creating a java folder in my main package and thus creating the same

MainActivity.java class

But I was using kotlin and which already had a MainActivity class.
So rolled back my changes and did
flutter create -i swift -a kotlin .
Remember the flutter create template by default supports java, more info here
It didn't mess up my iOS though 🤔

I solved the problem by running following 2 commands:
1- flutter clean
2- flutter run
that's all.

Thank you, it's work for me

I solved the problem by running following 2 commands:
1- flutter clean
2- flutter run
that's all.

worked for me

for me, I had to
delete the kotlin files in the android/app/src/main directory
cd into the android directory
run ./gradlew clean
problem solved.

for some reason i had both java and kotlin dirs in my project (probably commited java and then later switch to kotlin and when i pulled i got both present in my project)
So for me, solution was to delete com/package/java dirs, so java code dir


Go up prototype chain when checking isPlainObject

Implement a more robust version of isPlainObject that checks the prototype chain, inspired by Lodash's isPlainObject.
Fixes https://github.com/kysely-org/kysely/issues/1036.
Sorry for not writing a test, I'm a first-time contributor and the idea of adding a test for my particular use case--complex objects returned from PG.types.setTypeMapParser--was daunting. However, all tests pass on my machine.

Can't merge untested code. Expecially for such a crucial function.

Fixed in master.


Tell system to stop callbacks when they return false

Rails 5 changed how callback chains are interpreted. See:
https://blog.bigbinary.com/2016/02/13/
rails-5-does-not-halt-callback-chain-when-false-is-returned.html
This commit restores the old semantics, until we're confident that
things work correctly with the new semantics.  If we need to, we can
change some things, but the point of this commit is to simply ensure
that we're using the expected semantics.  We will then walk through
all the actions to make sure that there are no problems.
This commit causes the following expected deprecation warning:
DEPRECATION WARNING: ActiveSupport.halt_callback_chains_on_return_false=
is deprecated and will be removed in Rails 5.2. (called from ...)
Once everything has been reviewed, we'll remove the setting
(which will eliminate the deprecation warning).
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

I discussed this with @jdossett who agreed this made sense.


analyzer_benchmark_flutter_repo_watch_maximum & analyzer_benchmark_flutter_repo_batch_maximum regressions

Looks like around https://github.com/flutter/flutter/pull/50844, which I don't quite believe.

Dupe of https://github.com/flutter/flutter/issues/50013.


test_hierarchy_flow_using_select_speaker failed

Check out this https://github.com/microsoft/autogen/actions/runs/6838669585/job/18596023812
Running agentchat_hierarchy_flow_using_select_speaker.ipynb but fails.

It passed in #640


[CT-1341] [Bug] Source not evaluated properly when used in a set block which is then assigned to a hook in a model file

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
It looks like source doesn't work properly when it's being used in a set jinja block + used in a hook.
Expected Behavior
source() should always evaluate correctly everywhere no matter where we're calling it.
Steps To Reproduce

Setup profile.

# ~/.dbt/profiles.yml

snowflake:
  target: dev
  outputs:
    dev:
      database: development   # Just to show the default (I think is not relevant here).
      ...

dbt_project.yml - nothing special.

# dbt_project.yml

name: "my_dbt_project"
version: "1.0.0"
config-version: 2
profile: "snowflake"

models:
  my_dbt_project:
    +materialized: table

Sources.

# models/sources.yml

version: 2
sources:
  - name: my_sources
    database: analytics  # Override default of 'development'
    tables:
      - name: my_source

Setup model.

-- models/foo.sql

{% set my_var -%}
    update {{ source('my_sources', 'my_source') }} set foo = 'bar'
{%- endset %}

{{ config(post_hook = 'select 2 -- ' ~ my_var) }}

select 1 as id -- {{ source('my_sources', 'my_source') }}

Run our models:

$ dbt --debug run | grep -E 'select 1|select 2'

select 1 as id -- analytics.my_sources.my_source
select 2 -- update development.dbt_jyeo.foo set foo = 'bar'

Clearly {{ source('my_sources', 'my_source') }} evaluated correctly when it's in the body of the model but when we declare it in a set and then assign that to a hook, it becomes weird (evaluates to the {{ this }} for some reason).
Relevant log output
No response
Environment
- OS: macOS
- Python: 3.8.7
- dbt: 1.2.1

Which database adapter are you using with dbt?
snowflake
Additional Context
I know this is not best practice but more so for understanding why this is happening.
For readers, to make this work properly, we could do something like:

Add a macro:

-- macros/update.sql
{% macro update_something(arg) %}
    select 2 -- update {{ arg }} set foo = 'bar'
{% endmacro %}

Tweak our model:

-- models/foo.sql

{{ config(post_hook = "{{ update_something(source('my_sources', 'my_source')) }}") }}

select 1 as id -- {{ source('my_sources', 'my_source') }}

Run:

$ dbt --debug run | grep -E 'select 1|select 2'

select 1 as id -- analytics.my_sources.my_source
select 2 -- update analytics.my_sources.my_source set foo = 'bar'

Thanks @jeremyyeo. I believe this is the same issue as https://github.com/dbt-labs/dbt-core/issues/4606 (and https://github.com/dbt-labs/dbt-core/issues/2793 before that).

In its first parse through the project, dbt captures all refs (to construct the DAG) but renders the code with a "dummy" value. That "dummy" value is, for no great reason, the current node reference.

Put another way: At parse time, we don't have the resolved form of that source yet. So {{ this }} is the placeholder used instead.
Pre- and post-hooks can be defined with double/nested curlies to force a re-render at execution time, which is what you've shown in the example by defining update_something as a custom macro and then wrapping it in an extra set of curly braces. https://docs.getdbt.com/docs/building-a-dbt-project/dont-nest-your-curlies#an-exception
This is a problem that crops up with some frequency, so it is worth figuring out what an actually good solution might be. Best I've come up with is finding a way to store the raw/unrendered values of all configs (especially hooks) at parse time—not a thing we can do today—and then re-rendering them at execution time. It's not a totally satisfying answer.
Closing this for now as a duplicate, but it shouldn't be far from our thoughts.


Add Support for Vault Userpass Auth Method

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
The userpass auth method allows users to authenticate with Vault using a username and password combination.

https://www.vaultproject.io/docs/auth/userpass
https://www.vaultproject.io/api-docs/auth/userpass

Describe alternatives you've considered
N/A
Additional context
PR: #388

This feature was released in https://github.com/argoproj-labs/argocd-vault-plugin/releases/tag/v1.13.0


Wyscout event data serializer

Any status on this one?

Not yet. If you have documentation on the format we can have a look at it. So far no people asked for it nor did we have docs on the format

I have started to WyScout integration: https://github.com/PySport/kloppy/pull/79
This is very early stage code and not yet complete.

@koenvo can you link this issue with the pull request #79 ?


Feature/forecast controllers test

Added integration test for forecast-spec and forecast-instance.
Also changed forecast-spec and forecast-instance to extend CwmsDTO and added fields to forecast-instance so that it could find its corresponding spec.

I don't actually want the gradle file changed - I was just starting from devins pr https://github.com/USACE/cwms-data-api/pull/591


WIP: Implement support for optional fuel metering

Closes https://github.com/paritytech/wasmi/issues/643.

The diff coverage is 5.26%.

@@            Coverage Diff             @@
##           master     #653      +/-   ##
==========================================
- Coverage   81.13%   80.43%   -0.71%
==========================================
  Files          93       93
  Lines        7719     7788      +69
==========================================
+ Hits         6263     6264       +1
- Misses       1456     1524      +68

Impacted Files
Coverage Δ

crates/core/src/trap.rs
53.73% <0.00%> (-0.82%)
:arrow_down:

crates/wasmi/src/engine/bytecode/mod.rs
100.00% <ø> (ø)

crates/wasmi/src/engine/cache.rs
81.81% <ø> (ø)

crates/wasmi/src/engine/config.rs
56.52% <0.00%> (-6.90%)
:arrow_down:

crates/wasmi/src/engine/executor.rs
96.32% <0.00%> (-0.50%)
:arrow_down:

crates/wasmi/src/error.rs
58.62% <0.00%> (-6.77%)
:arrow_down:

crates/wasmi/src/store.rs
65.98% <2.00%> (-16.50%)
:arrow_down:

crates/wasmi/src/func/caller.rs
41.66% <23.07%> (-13.89%)
:arrow_down:

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


fix: report connection down when there are no producers/consumers

Previously, an empty list of producers or consumers would make pulsar_{producers,consumers}:all_connected/1 to return true.
Since there's currently no rebalance in Pulsar consumers, we should expect at least one consumer pid to exist as well.

Tagged 0.8.1.


[DJS13]Setting default volume?

Hi.
I'm trying to set a default volume for the bot when joining a vc. Here's what I've tried so far:
https://github.com/Allvaa/lavalink-musicbot/blob/0e47d9b086e88021c4b813f2e572de9f1529c581/src/structures/MusicHandler.js#L114
I changed it to:
        this.player?.playTrack(this.queue[0].track, {volume: 15});
However, it stil plays the music at 100% volume. I've also tried changing it to:
        this.player?.playTrack(this.queue[0].track, {setVolume: 15});
However it still won't work. What am I doing wrong here?

Why don't you use the already defined function to set volume which should be this.setVolume(volume) add this after playing the track it will be default volume IG

Why don't you use the already defined function to set volume which should be this.setVolume(volume) add this after playing the track it will be default volume IG

Hi.
When I change it using that function:
this.player?.playTrack(this.queue[0].track, {this.setVolume(15)});
I get the following error:
SyntaxError: Unexpected token '.'
How can I fix this?


Differences in font metadatas between the originial and generated one

Metadatas (Family and Style) from the font generated with fontTools are different from the original one.
See images below:
Original:

fontTools:

pyftsubset only keeps nameIDs between 0 and 6.
set --name-IDs=* to keep the original names


Fixed issue with positioning and setting the width of the dropdown on decimal numbers

Currently, when setting the position and the width of the dropdown, offset(Width|Left|Top) is used.
The issue is that these properties only give integer values. In cases when the position or the width is a decimal number, 'Element.getBoundingClientRect()' is recommended to be used.
Plunker showing the issue: DropdownIssue
The dropdown is shown as smaller than the placeholder (maybe with some zoom-in will be more visible).

I merged the pull request, but reverted the changes again. The fixed positioning of the drop down is undesired because the drop down will not scroll with the page in that case. But with absolute positioning the drop down is wrongly positioned.


[WIP] fix: remove @ts-nocheck and fix type errors

I got an type error when using graphql-language-service-server.
server/node_modules/graphql-language-service-interface/dist/getAutocompleteSuggestions.d.ts:2:26 - error TS2305: Module '"../../graphql-language-service-types/dist"' has no exported member 'ContextToken'.

server/node_modules/graphql-language-service-interface/dist/getAutocompleteSuggestions.d.ts:2:40 - error TS2305: Module '"../../graphql-language-service-types/dist"' has no exported member 'State'.

It seems that ContextToken and State are defined in graphql-language-service-parser instead of graphql-language-service-types. So I removed the @ts-nocheck flag and fix the type errors.
@acao can you help me to review this

@stonexer thank you, this is a good catch!


SQLite3 platform needs some more configuration to pass more tests.

A number of tests are fixed by defining method maximumQueryValueSize and returning 50000.
This is the largest string SQLite can handle in a like or glob expression and, lets be real, one isn't likely to be querying with parameters this large.
See https://sqlite.org/limits.html
"The pattern matching algorithm used in the default LIKE and GLOB implementation of SQLite can exhibit O(N²) performance (where N is the number of characters in the pattern) for certain pathological cases. To avoid denial-of-service attacks from miscreants who are able to specify their own LIKE or GLOB patterns, the length of the LIKE or GLOB pattern is limited to SQLITE_MAX_LIKE_PATTERN_LENGTH bytes. The default value of this limit is 50000. A modern workstation can evaluate even a pathological LIKE or GLOB pattern of 50000 bytes relatively quickly. The denial of service problem only comes into play when the pattern length gets into millions of bytes. Nevertheless, since most useful LIKE or GLOB patterns are at most a few dozen bytes in length, paranoid application developers may want to reduce this parameter to something in the range of a few hundred if they know that external users are able to generate arbitrary patterns."
Also need to define autoTrimsStringsLongerThanColumnSize to return true.  It doesn't really trim strings.  SQLite will let you put a string of arbitrary length in any field type and it does not constrain inputs like other dbs.  But the tests use this to determine whether to expect an error to be thrown if an oversized string is set.  SQLite does not throw an error, it takes whatever you give it.
Finally, I went ahead and defined sqlTextCurrentServerUTCTimestamp because despite not having date and time types (use strings), it does have functions for manipulating date and time types, but always returns formatted strings.

@tblanchard Can you try with UDBCSQLite3Platform instead of SQLite3Platform? The latter is from Glorp upstream. When I did the initial integration of Glorp and SQLite on Pharo 5, I created UDBCSQLite3Platform subclassing SQLite3Platform, the intention of which was to make all necessary changes in this class and leave Glorp upstream code untouched as much as possible. My SQLite-related changes and tests have always been for UDBCSQLite3Platform.

@PierceNg a user of this package would know this how?  I ran the tests with SQLite3Platform because I have no idea at all what UDBCSQLitePlatform is for and it doesn't say anywhere.  I thought it was a garage holdover or something and I spent the better part of a day and a half diagnosing and fixing failures with SQLite3Platform.

On Fri, Feb 05, 2021 at 09:52:03AM -0800, Todd Blanchard wrote:

@PierceNg a user of this package would know this how?

By searching the web, by asking on mailing lists, and so on?  Most search
engine hits would point to my blog or my repos.
The Metacello loading snippet for loading Glorp + SQLite has been in place
since 2018:
https://www.samadhiweb.com/blog/2018.10.23.glorp.sqlite3.html
I just tested with a fresh Pharo 7.0.5 image with the snippet stated in the
README of https://github.com/pharo-rdbms/glorp-sqlite3:
Metacello new
    repository: 'github://pharo-rdbms/glorp-sqlite3:p7_newsqlite';
    baseline: 'GlorpSQLite';
    load.

890 run, 890 test passes, 13 skipped. One more skipped compared to my 2018
blog post, because (IIRC) the then-new SQLite binding broke part of one
blob test.

I shouldn't have to search the web and ask on mailing lists about a package.  It should be documented in the package.  The UDBCSQLitePlatform class comment is pretty unhelpful in that regard.  That's where I looked.
I'm working on Pharo-SQLite3 and trying to make that work out of the box.  That seems to be what people hop on when they want SQLite, optionally with glorp.
It seems there is a duplication of effort here.  I would like us to have packages of Pharo- with optional glorp loading targets so someone can run a load command and get going.  I'm open to proposals to get to one clean package.
Also, with regard to glorp updates, who pulls those?  What is the process for getting updates?  I kind of figured the fork was a one time thing and we carry it forward.  Is there a process to push enhancements back?  Because the SQLitePlatform is half baked at best.


Attempt to handle variable length positional nargs

This is an imperfect solution that chooses to show too many completions rather than too few. Note that this somewhat blurs the meaning of active_actions since we have to store the whole sequence of positionals in case we need to run completers for all of them.
The problem is that you can't know in advance which arguments belong to which action. For example, one of the original tests was "prog c bus apple " => ["-h", "--help"]. The user intends for apple to fill in value and hence no more positional arguments can be added. However, if the user were to then type orange, argparse would assign both bus and apple to var (in this case that happens to be invalid, but it won't always be). The solution I've taken is to always complete all positionals after var since anything typed past that point could eventually end up as one of those arguments.
I'm not 100% sure this is the best solution, but I've put up this PR for discussion.

[Current coverage][cc-pull] is 77.98%

Merging [#133][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master       #133   diff @@
==========================================
  Files             5          5
  Lines           778        781     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            607        609     +2
- Misses          171        172     +1
  Partials          0          0

Powered by Codecov. Last updated by [cd426a5...7ba3ee4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/kislyuk/argcomplete/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/kislyuk/argcomplete/compare/cd426a58e2f5a027f1774f008dcb73ed32447025...7ba3ee4ee6b759dffba2cb10fcc71cf65ec89135
[cc-pull]: https://codecov.io/gh/kislyuk/argcomplete/pull/133?src=pr

I think this is very close to perfect. I have one improvement in mind - don't add an action to active actions if it's preceded by an unsatisfied action with nargs > 0 - but I can play around with this and add it myself.
Thanks so much for your work on this!

After thinking about this for a bit, I agree with you - it's intractable to try to guess which trailing actions to inactivate if there is an unbounded-nargs action active. So I think we're set here - great work!

Thanks! I think it may be possible to improve the handling of nargs='?' since it can only take 0 or 1 arguments. In this case, it's probably only necessary to to complete 1 extra argument when the action is open rather than all of them.


NPE when preparing structure feature

Versions

Minecraft: 1.12.2
Forge: <IP_ADDRESS>24
OTG: v6
Biome Bundle: 5.1

The issue
This is the crash, it looks like it's related to Mansion generation.
This crash started on a modpack with ~101 mods, but I took the same world it was crashing on and transferred it to an instance with only the listed mods. Even with just these few mods, it still crashes exactly the same.
Let me know if you need any other info or tests!

In fact, dropping back to v5 is still having this issue...

...any update on this? I made the PR, but at this point I can't load my singleplayer let's play world up with or without it... (without due to an Antique Atlas bug with biome mapping)

Should be fixed with v7.


workflow error: node acompcor failed to run on host [fmriprep]

Hello,
I received an error for one participant file in this dataset: https://openneuro.org/datasets/ds000009/versions/00002?app=FMRIPREP&version=23&job=e2902b0b-029b-4163-bdad-75418cfd64f9
This caused the newest version of fmriprep to fail on this dataset.
Here is the crash log for that particular subject [07]:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 51, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 407, in run
self._run_interface()
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 517, in _run_interface
self._result = self._run_command(execute)
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 650, in _run_command
result = self._interface.run()
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base.py", line 1088, in run
runtime = self._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/common/report.py", line 55, in _run_interface
ReportCapableInterface, self)._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/algorithms/confounds.py", line 471, in _run_interface
self.inputs.pre_filter, degree, self.inputs.high_pass_cutoff, TR)
File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/algorithms/confounds.py", line 1070, in compute_noise_components
u, _, _ = linalg.svd(M, full_matrices=False)
File "/usr/local/miniconda/lib/python3.6/site-packages/scipy/linalg/decomp_svd.py", line 119, in svd
raise LinAlgError("SVD did not converge")
numpy.linalg.linalg.LinAlgError: SVD did not converge

Duplicate of #776. Should be resolved by #807, which will be in the next release.


fix: added translation ordinal number support for all languages

Description
Added ordinals to the languages so it doesn't say like in the ticket: [ticket #1976]
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A

Risk

Testing

Screenshots (if applicable)

verified working in fleek

If I may suggest not defining the key/pairs in main.json files that are not actually translated (id, ko, ru ad zh from what I can see), otherwise translators will most likely not notice these new (untranslated) strings on the translation platform.

They are not translated because their dont seem to be a ordinal for them. Thats why.

They are not translated because their dont seem to be a ordinal for them. Thats why.

The first result on Google for Russian "abbreviating ordinal numbers in Russian" gives this:

Source: https://blog.mangolanguages.com/how-do-you-use-ordinal-numerals-in-russian
Online translators seem to agree too.
Anyways, in general, I think it would be preferable to leave translation work to translators, we have a Workstream section dedicated to Globalization/Translations with native speakers for each language that can deal with those nuances and not waste engineering efforts. As I understand the keys that would be missing in a language fallback to English and as I said they can then be more easily identified as "untranslated strings" during the translators' work.
That being said, thanks for your work on this issue, it will look much cleaner in other languages now ! 👍


Run systemd service as user

Unprivileged user should be able to start the sshtunnel.
When running as a root there is no HOME env.
https://wiki.archlinux.org/title/systemd/User

Fixed in v1.20


Stringupdate

Here are some more strings for you

Thanks for this! The Pull is a bit of a mess so I've manually copied the fixes over in ea3e136ab9f743b54d6bcb1ac712ee96f2772e7a


added show password icon to password input

👷 Deploy Preview for cg-eleventy-blog processing.

Name
Link

🔨 Latest commit
ae43424a20cec83bb4fadaedb8ce680ccbeab682

🔍 Latest deploy log
https://app.netlify.com/sites/cg-eleventy-blog/deploys/65c6bd572b2714000806adc2


fix: retract version 1.0.1

v1.0.1 is broken and should not be used. Add an explicit
retract directive to the go.mod.
See https://go.dev/doc/modules/gomod-ref#retract

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-07-28T17:06:54.592+0000

Duration: 23 min 12 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
196

Skipped
64

Total
260

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Looking into this a bit more I don't think it's really necessary. v1.0.1 is not technically broken, the release zip is.
Using the docker image or building the extension into a docker image would work just fine.
I'll close this. Thanks for the help :bow:


Getting stuck on the horizontal boundries.

If the player eats while along the top and bottom horizontal borders they eventually lose the ability to move on the y axis. I haven't been able to recreate it along the verticle boundies.

Someone already reported that at #154. Maybe you could improve the issue description there? :)


Directly creating a terminal in a group editor

Directly creating a terminal in a group editor.
Creating it in the terminal panel, moving it, then closing the terminal
panel is too indirect.

There are existing commands in Command palette(F1 or Ctrl+Shift+P): >Terminal: Create New Terminal In Editor area and >Terminal: Create New Terminal In Editor area to the Side
You can assign key bindings for them as well.

@Tyriar maybe it make sense to add Create New Terminal In Editor area to the Terminal section of Main menu?

@IllusionMH the thinking was if someone wants to use editor terminals a lot they would set "terminal.integrated.defaultLocation": "editor"

I missed the obvious.
But the discussion was enlightening.
I should have said I am trying to do everything from the keyboard, so I don't use the main menu even if on my Mac I could access it with shift cmd /
So IllusionMH suggestion may be very good but is irrelevant to me.
But the setting proposed by Tyriar seems promising.
Thanks everyone.


Enhancement: Can update memory cache

closes #20

Codecov Report
Attention: Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.41%.

Files
Patch %
Lines

...tCache.InMemory/Drivers/MultiBucketsMemoryCache.cs
95.00%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage   89.06%   89.41%   +0.35%
==========================================
  Files          23       23
  Lines         512      529      +17
  Branches       95       98       +3
==========================================
+ Hits          456      473      +17
  Misses         30       30
  Partials       26       26

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


unable to view PPPoE tunnel packet

Hi there,
i'm not sure this is a bug or design of the system. apparently i cannot view any packet capture inside the PPPoE tunnel. I can use tcpdump -r filename.pcap to view the file and confirmed the packet was captured properly but i unable to view it in the moloch-viewer interface.
sample packet capture as below,
03:51:40.267679 PPPoE  [ses 0x59f7] IP <IP_ADDRESS>.51051 > <IP_ADDRESS>.http: Flags [.], ack 199064, win 258, length 0
03:51:40.275320 PPPoE  [ses 0x440e] IP <IP_ADDRESS>.52407 > edge-star-shv-01-sin6.facebook.com.https: Flags [.], ack 69, win 4093, options [nop,nop,TS val 524449190 ecr<PHONE_NUMBER>], length 0
03:51:40.275336 PPPoE  [ses 0x440e] IP <IP_ADDRESS>.52407 > edge-star-shv-01-sin6.facebook.com.https: Flags [.], ack 137, win 4091, options [nop,nop,TS val 524449190 ecr<PHONE_NUMBER>], length 0
03:51:40.278380 PPPoE  [ses 0x1c8] IP server-54-240-168-122.sin3.r.cloudfront.net.https > <IP_ADDRESS>.53993: Flags [.], ack 224, win 118, options [nop,nop,TS val 327658430 ecr 5570866], length 0
I'm on ubuntu 14.0.5 with moloch 0.15/ES 2.4
Appreciate anyone can give me a hand on this matter.
thanks,

do you have a pcap you can share?

Yes. How can i share the file to you? Email?
Thanks

andywick gmail

ok, sent.

it's working now.
thank you for making this feature available !


'Microk8s.enable Kubeflow' replies "Kubeflow is already enabled" with missing services

When 'microk8s.enable kubeflow' fails to launch all the services, or is in a state with missing services, 'microk8s.enable kubeflow' states that Kubeflow is enabled.
There should be some kind of recovery mechanism, where this command checks the status of the Kubeflow services and restarts missing ones - (e.g. 7/30 pods running).
Example:

Under these circumstances, the user is forced to disable kubeflow and enable again, which takes a lot time.

@RFMVasconcelos: Closing this as a duplicate of #1397, feel free to reopen if that's wrong.


do preprocess before making lmdb

A simple question, is it possible to do all the preprocess before writing to lmdb, so when training, we won't be bottlenecked by CPU preprocessing

It is.
Just write a different dataflow to lmdb.

I see, will try it!


Update tools

TODO: Please replace this header with a description of your pull request.
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

I keep forgetting that this is not like any other CI workflow 😆


Intermittent build failure when the distribution is used for tests after buidling a module

Description:
Currently the gRPC library has ballerina module and the tests in 2 separate modules and separate runtimes are created when building these. To avoid the duplication, we tried using the same runtime for both ballerina module build and test module build (see https://github.com/ballerina-platform/ballerina-standard-library/issues/1987#issuecomment-939926915). But when the tests are build, following error occurs intermittently.
Running Tests with Coverage

        grpc_tests
error: null

Generating Test Report
        .................../module-ballerina-grpc/ballerina-tests/target/report/test_results.json

error: there are test failures

> Task :grpc-ballerina-tests:ballerinaTest FAILED

Sometimes the build passes without any issues.
When this runtime is used to run a simple BBE, following error occurs.
Compiling source
	dilan/simple_rpc_server:0.1.0
error: failed to load the module 'ballerina/grpc:1.0.1' from its BIR

Steps to reproduce:
Clone the following repo [1] and checkout the branch change-distro-location and do ./gradlew clean build
[1] https://github.com/dilanSachi/module-ballerina-grpc.git
Affected Versions:
Ballerina lang version 2.0.0-beta.3
OS, DB, other environment details and versions:
Ubuntu 20.04
Related Issues (optional):
https://github.com/ballerina-platform/ballerina-standard-library/issues/1987
Suggested Labels (optional):
Suggested Assignees (optional):

Could not reproduce this in beta5. Hence closing


feat(note): ✨ compare spellings by closest distance

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1005

Relevant Lines:
1005

💛  - Coveralls


Meeting (Project Management) -  Wednesday, 29th May, 2024

Welcome
SingularityNET-Archive contains a history of the activities of the SingularityNET Ambassador Program.
All content is provided under an Open Source Apache 2 Licence.
Contributions will be licensed under a Creative Commons licence.
Video Recording

https://youtu.be/S86uaRLN5Ns
Our goal
Our goal is to provide a collaborative platform for the SingularityNET-Archive community to share knowledge, ideas, and best practices. We welcome contributions from anyone interested in SingularityNET, whether it's a new project, code example, or documentation.
Our Process
Please review the following at the beginning of each meeting.
And add any new Action or Decision items that arise from issues here. The assignee will update the issue, speak to the work and update with any comments
Action and Decision Items
Mark Action Items in each issue as follows -
https://archive-oracle.netlify.app
Previous meeting

https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/134

Links:

Project Board
Archival Workgroup proposal
Archive GitBook

Present:

[ ] Andre
[ ] Stephen
[ ] Vani
[ ] Peter
[ ] Onyeka
[ ] Vasu
[ ] SucrenSpice
[ ] Ese Williams
[ ] Kenichi
[ ] Duke Peter
[ ] Ekemini Samuel

Archive

[ ] Add to meeting summary channel
[ ] Close meeting issue (to ensure charge in correct month)
[ ] Meeting uploaded to YouTube and Timestamped
[ ] Meeting recorded in Archive GitBook

To consider

Decision and action items to be in main meeting issue - possibly populated from the template in future
To be added to main body to be carried forward

Previous in series: #156

Next in series: #168


⚠ Bofrost.be has degraded performance

In ba3fd8f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2059 ms

Resolved: Bofrost.be performance has improved in 54bde0d.


New FFI Macro

Brand new ludicrously overengineered macro for automagically™ interoping with byond smoothly and cleanly.
Here's what you can do with the new macro
All of these are callable directly from byond.
Write bare functions without being wrapped in a macro
#[byond_fn]
pub fn example_byond_fn() {
    let x = "yeah, we can bind vars";
    println!("{x}");
}

Have string arguments and return strings
#[byond_fn]
pub fn concat(first: &str, second: &str) -> String {
    format!("{first}{second")
}

Have arbitrary args that can be parsed from strings and return arbitrary types that can be converted to strings
#[byond_fn]
pub fn add(arg1: u8, arg2: u8) -> u8 {
    arg1 + arg2
}

Have some arguments be optional and not required to be passed
#[byond_fn]
pub fn example_optional_params(arg1: u8, arg2: Option<u8>) -> u8 {
    arg1 + arg2.unwrap_or(0)
}

Automagic JSON Transport
pub fn fungle_the_goobler(goobler: Json<Goobler>) -> Json<Fungled> {
    let fungled = goobler.into_inner().fungle();
    Json(fungled)
}

New macro lives here (at the moment): https://github.com/actioninja/byond_fn
Docs here: https://docs.rs/byond_fn/0.5.1/byond_fn/
byond_fn todo

[ ] Finalize the argument structure and how FFI types should be specified
[ ] Finalize the error handling structure
[ ] Implement some way of automatically generating the byond-side call signature (companion crate for usage in build.rs?)
[ ] Fully cover all pub api with documentation
[ ] Write some basic unit tests
[ ] Implement the new byond FFI interface

Things that should happen before this is merged

[ ] finalize byond_fn structure and output and hit 1.0 (above todo list should be finished)
[ ] convert all existing functions in rust-g to use the new macro
[ ] bring byond_fn under the tgstation org and give more accounts crates.io publish perms
[ ] run a built binary using the new macro in prod for a while to check against regressions

fungle_the_goobler

How (un)performant is this?

How (un)performant is this?

Shouldn't be meaningfully different from the existing macro. The two potential vectors for performance differences are the extra error handling and sanity checking (of which this mostly consists of a check to make sure the amount of arguments is correct), and the extra trait function calls which are all static dispatch anyways.

FFIV2 is out - Tiger is currently making a crate for it https://github.com/spacestation13/byondapi-rs


Changing debouce time on mice

At the moment it's impossible to change the debouce time of mice on hyprland. libinput does offer this with its own option ModelBoucingKeys
It would be best if you could set it in hyprland.conf under the 'input' section. Something like 'mouce_debouce=value' I think is best.
If this does not get fixed I might have to leave my dear beloved smooth animations :sob: :sob: :sob:
I gotta get those combos in minecraft don't judge me.

can't see it in available libinput funcs, does sway have this? maybe it's called different internally


Provide us repository link to clone entire build version and ready to execute from local system

Hi,
We are trying to download using the below urls
https://github.com/readium/readium-js-viewer/releases/download/0.25.0/Readium_cloud-reader-lite.zip
https://github.com/readium/readium-js-viewer/releases/download/0.25.0/Readium_cloud-reader.zip
But it seems we are always getting incomplete build.
Can you please give us the repository link, so that we could clone entire build version. And we could execute it from local iis with our sample epub file.
Best Regards
Ashish

I have just tried the ZIP downloads Readium_cloud-reader-lite.zip and Readium_cloud-reader.zip from the official v0.25 release:
https://github.com/readium/readium-js-viewer/releases/tag/0.25.0
...and it all works fine.
Basically:

unzip into a directory,
serve static HTTP files from that folder (or any parent folder),
open web browser to root URL (e.g. http://<IP_ADDRESS>:8080/readium/cloud-reader/index.html),
then try a URL with the epubs query string parameter to load an ebook library file (e.g. http://<IP_ADDRESS>:8080/readium/cloud-reader/index.html?epubs=../ebooks_library.opds, assuming the OPDS file exists inside the HTTP folder ./readium/ebooks_library.opds)
then try a URL with the epub query string parameter to load a single ebook file (e.g. http://<IP_ADDRESS>:8080/readium/cloud-reader/index.html?epub=../../ebook.epub, assuming the EPUB file exists inside the HTTP folder ./ebook.epub)

Alternatively, you can build your own version of the cloud reader by following instructions in the README:
https://github.com/readium/readium-js-viewer/blob/develop/README.md


[REQUEST] MHI2_ER_AUG22_S2148 UPDATE TO P2156 PROBLEM

HI I AM LOOKING FOR SOLUTION , HOW TO UPDATE FIRMWARE OF AUDI Q7 4M FROM S2148 TO P2156.
I CHANGED IN EEPROM SETTINGS, NOW SYSTEM SEE SOFTWARE LIKE P2148, AND NOW I CAN UPDATE SYSTEM BECAUSE OF SUPPORTED TRAIN LIST P2148 EXISTS.
BUT UNFORTUNATELLY NOT POSSIBLE TO UPDATE TO P2156.
"PARSING OF RELEASE  INFO FAILED"
FILE:
LINE: 7
PLEASE ANY ADVICE HOW TO UPDATE THIS 4M TO SOMETING NORMAL SOFTWARE :)
THX

No caps-lock needed here 😉
It is very plausible that the newer release has an updated metainfo key. Not sure about that, I've had no similar issues.
Since this is not a Toolbox issue, I will close it, to prevent this place from becoming a big chaotic forum for everyone with MIB issues.

thx Jilleb for answer me, at start car had:
s2148 software.

after i changed in eeprom to get p2148 :

and try to update to k2156 because support train: SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*
but got error like this

don't know why get this error, if trains now is supported.
thx for help

But the train was no supported for a reason, probably because the metainfo key has changed


Bump to 0.0.9 with file import support

Added support for safe pip -r style installs for requirements.txt style files
Prevent using requirements.txt lines that are not direct dependencies
Added Package license to FULL output report

Codecov Report

Merging #7 (c4ea06b) into master (0d75544) will decrease coverage by 0.40%.
The diff coverage is 81.39%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   82.34%   81.93%   -0.41%
==========================================
  Files          10       11       +1
  Lines         606      631      +25
  Branches       92       97       +5
==========================================
+ Hits          499      517      +18
- Misses         93       98       +5
- Partials       14       16       +2

Impacted Files
Coverage Δ

ochrona/config.py
82.60% <ø> (ø)

ochrona/reporter.py
82.10% <0.00%> (-0.88%)
:arrow_down:

ochrona/import_wrapper.py
74.60% <80.00%> (-3.18%)
:arrow_down:

ochrona/__init__.py
100.00% <100.00%> (ø)

ochrona/const.py
100.00% <100.00%> (ø)

ochrona/file_handler.py
92.30% <100.00%> (-0.17%)
:arrow_down:

ochrona/logger.py
78.12% <0.00%> (+3.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Add Linux and Mac support

Currently we update the code for Windows one to be have real-time feature, but need to add this to Linux ad Mac too

:tada: This issue has been resolved in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Udpate links in redme.md

@Sahiljawale assign this task to me

@Sahiljawale have fixed the links to point to this repo but I see that this issue has been assigned to @Soumyajit2825 . Should be opening a PR for this ?

Pull Req done . PLease check and merge it if u find it helpful
On Thu, Oct 6, 2022 at 8:46 AM Sahil Jawale @.***>
wrote:

Assigned #7 https://github.com/Sahiljawale/CodeChef/issues/7 to
@Soumyajit2825 https://github.com/Soumyajit2825.
—
Reply to this email directly, view it on GitHub
https://github.com/Sahiljawale/CodeChef/issues/7#event-7530023661, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AX64266EWALYEMDDRF2NE4LWBZACBANCNFSM6AAAAAAQ6C7MNA
.
You are receiving this because you were assigned.Message ID:
@.***>

Have updated the links. Even @Soumyajit2825 were redirecting to his fork. Have updated them.

good job
On Thu, Oct 6, 2022 at 9:57 AM Ansh Sarkar @.***> wrote:

Have updated the links. Even @Soumyajit2825
https://github.com/Soumyajit2825 were redirecting to his fork. Have
updated them.
—
Reply to this email directly, view it on GitHub
https://github.com/Sahiljawale/CodeChef/issues/7#issuecomment-1269293937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX6426ZM4GML5GIKWI4COE3WBZILXANCNFSM6AAAAAAQ6C7MNA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey, @Sahiljawale I want to add some more difficult level problems of good quality Questions.

Hey @Sahiljawale I want to add Some problems
Can You assign me ?

Hey, @Sahiljawale I solved so much problems in codechef and I want  to add solution . Can you assign me?

Hi there, I would like to add some more problems which I find quite interesting & good !


Modify Comments row mapper datetime conversion

Coverage remained the same at 0.661% when pulling 50be4df55132cebce3e80aac3fb95d1790ecc573 on alyiwang:master into f0ac5c58b2c3cbd72210cf5874bbac5763ee1c85 on linkedin:master.


Feel free to ask for this to be re-opened if you find a bug/issue with Slick, and also please read https://github.com/kenwheeler/slick/blob/master/CONTRIBUTING.markdown :smile:


Upgrading Windows 10 Deleted All Data

Yesterday I upgraded Windows 10 to version 1909.  I opened up my app in Chrome for the first time since the upgrade and see that all my data has been deleted.
Is this a common issue?
Is there anyway to avoid it?
Edit: I might've upgraded VSCode yesterday, too.

Yes . You should export import when changing browsers, the indexedDB that Dexie uses is local to the browser.
https://dexie.org/docs/ExportImport/dexie-export-import
https://codepen.io/dfahlander/pen/RqwoaB/

I didn't change browsers, though.

ahhh . yes . the "Windows 10 version upgrade" would wipe your filesystem so the browser do not have the handle to the wiped instance.
Different browsers on same OS ex. chrome, edge, opera, firefox etc ... are all locally separated to DB instance's. Separate browser = separate DB.

oohhh . i thought clean install and can not answer on what update and migration of apps-preferences for W-10 do or not ... it is the chrome preferences and files that should be preserved on the update is what one expect ? . please check for more info on the specifics on W-10 related sites and forums.

Might be the chrome update https://www.theregister.co.uk/2019/12/16/chrome_79_update_a_catastrophe_for_android_users_with_webview_apps/


radvd does not advertise addresses for virtual IPs

The radvd configuration does not provide a section for virtual ips. If you use any virtual ip from the fc00::/7 range for Unique Local Unicast, no advertisements are configured. The radvd.conf only has the configuration for the "real" interfaces.

The whole config for radvd is based on static IPv6 addresses from the interface setting itself. To support this, what would be necessary to change in the radvd.conf file? I am not sure we can easily add new configuration blocks for virtual IPs here...

There should be a  prefix stanza for every IPv6 address in the interface definition. This is, what I use on my Linux-Router:
interface enp1s0 {
        AdvSendAdvert on;
        AdvLinkMTU 1280;
        MaxRtrAdvInterval 120;
        prefix 200x:x:x:x::/64 {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr on;
        };
        prefix fd42:1313:815:1::/64 {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr on;
        };

};

One prefix stanza for the public IP-Range and one for the IP-alias with the unique local unicast address.

@wytchmaster that looks doable, give me some time to integrate this :)

You can try the proposed patch 9471303 with the following command... needs another commit, some other radvd improvement via 38c1daa
opnsense-patch 38c1daa 9471303
If anything goes wrong:
opnsense-revert opnsense
Cheers,
Franco

I will try to check that this evening.

works like a charm :-) Thank you.

purrfect, thanks! expecting this to land in 17.7.10. if not, please prod again :)

Will be in 17.7.9 :)