[Bug] Train on the basis of github releases model，Error：Key batch_normalization/beta/Adam not found in checkpoint

Description

Hi, All
I want restore github releases model，continue training on this basis。
I use ‘spleeter train’ command train model
But this error occurred：tensorflow.python.framework.errors_impl.NotFoundError: Key batch_normalization/beta/Adam not found in checkpoint [[{{node save/RestoreV2}}]]
When not using github releases model，not copy github releases model to ’ "model_dir": "musdb_model" ’，training is normal
Step to reproduce

1.I copy github releases model in to ’ "model_dir": "musdb_model" ’
2.Run  ‘python -m spleeter train -p /Users/baiyu/train-all-data/musdb_config.json -d /Users/baiyu/train-all-data’
Output
% python -m spleeter train -p /Users/baiyu/train-all-data/musdb_config_local.json -d /Users/baiyu/train-all-data
INFO:spleeter:Start model training
WARNING:tensorflow:From /Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/spleeter/commands/train.py:117: The name tf.reset_default_graph is deprecated. Please use tf.compat.v1.reset_default_graph instead.

INFO:tensorflow:Not using Distribute Coordinator.
INFO:tensorflow:Running training and evaluation locally (non-distributed).
INFO:tensorflow:Start train and evaluate loop. The evaluate will happen after every checkpoint. Checkpoint frequency is determined based on RunConfig arguments: save_checkpoints_steps 300 or save_checkpoints_secs None.
WARNING:tensorflow:From /Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/training_util.py:236: Variable.initialized_value (from tensorflow.python.ops.variables) is deprecated and will be removed in a future version.
Instructions for updating:
Use Variable.read_value. Variables in 2.X are initialized automatically both in eager and graph (inside tf.defun) contexts.
WARNING:tensorflow:From /Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/data/util/random_seed.py:58: where (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
WARNING:tensorflow:From /Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/autograph/converters/directives.py:119: The name tf.string_join is deprecated. Please use tf.strings.join instead.

INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Apply unet for vocals_spectrogram
WARNING:tensorflow:From /Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/ops/resource_variable_ops.py:1630: calling BaseResourceVariable.__init__ (from tensorflow.python.ops.resource_variable_ops) with constraint is deprecated and will be removed in a future version.
Instructions for updating:
If using Keras pass *_constraint arguments to layers.
INFO:tensorflow:Apply unet for drums_spectrogram
INFO:tensorflow:Apply unet for bass_spectrogram
INFO:tensorflow:Apply unet for other_spectrogram
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Create CheckpointSaverHook.
INFO:tensorflow:Graph was finalized.
INFO:tensorflow:Restoring parameters from musdb_model/model
Traceback (most recent call last):
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1365, in _do_call
    return fn(*args)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1350, in _run_fn
    target_list, run_metadata)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1443, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.NotFoundError: Key batch_normalization/beta/Adam not found in checkpoint
	 [[{{node save/RestoreV2}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/saver.py", line 1290, in restore
    {self.saver_def.filename_tensor_name: save_path})
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 956, in run
    run_metadata_ptr)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1180, in _run
    feed_dict_tensor, options, run_metadata)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1359, in _do_run
    run_metadata)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1384, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.NotFoundError: Key batch_normalization/beta/Adam not found in checkpoint
	 [[node save/RestoreV2 (defined at /site-packages/tensorflow_core/python/framework/ops.py:1748) ]]

Original stack trace for 'save/RestoreV2':
  File "/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/site-packages/spleeter/__main__.py", line 58, in <module>
    entrypoint()
  File "/site-packages/spleeter/__main__.py", line 54, in entrypoint
    main(sys.argv)
  File "/site-packages/spleeter/__main__.py", line 46, in main
    entrypoint(arguments, params)
  File "/site-packages/spleeter/commands/train.py", line 121, in entrypoint
    evaluation_spec)
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 473, in train_and_evaluate
    return executor.run()
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 613, in run
    return self.run_local()
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 714, in run_local
    saving_listeners=saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 370, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1161, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1195, in _train_model_default
    saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1490, in _train_with_estimator_spec
    log_step_count_steps=log_step_count_steps) as mon_sess:
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 584, in MonitoredTrainingSession
    stop_grace_period_secs=stop_grace_period_secs)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1014, in __init__
    stop_grace_period_secs=stop_grace_period_secs)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 725, in __init__
    self._sess = _RecoverableSession(self._coordinated_creator)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1207, in __init__
    _WrappedSession.__init__(self, self._create_session())
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1212, in _create_session
    return self._sess_creator.create_session()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 878, in create_session
    self.tf_sess = self._session_creator.create_session()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 638, in create_session
    self._scaffold.finalize()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 237, in finalize
    self._saver.build()
  File "/site-packages/tensorflow_core/python/training/saver.py", line 840, in build
    self._build(self._filename, build_save=True, build_restore=True)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 878, in _build
    build_restore=build_restore)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 502, in _build_internal
    restore_sequentially, reshape)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 381, in _AddShardedRestoreOps
    name="restore_shard"))
  File "/site-packages/tensorflow_core/python/training/saver.py", line 328, in _AddRestoreOps
    restore_sequentially)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 575, in bulk_restore
    return io_ops.restore_v2(filename_tensor, names, slices, dtypes)
  File "/site-packages/tensorflow_core/python/ops/gen_io_ops.py", line 1696, in restore_v2
    name=name)
  File "/site-packages/tensorflow_core/python/framework/op_def_library.py", line 794, in _apply_op_helper
    op_def=op_def)
  File "/site-packages/tensorflow_core/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 3357, in create_op
    attrs, op_def, compute_device)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 3426, in _create_op_internal
    op_def=op_def)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 1748, in __init__
    self._traceback = tf_stack.extract_stack()

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/saver.py", line 1300, in restore
    names_to_keys = object_graph_key_mapping(save_path)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/saver.py", line 1618, in object_graph_key_mapping
    object_graph_string = reader.get_tensor(trackable.OBJECT_GRAPH_PROTO_KEY)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/pywrap_tensorflow_internal.py", line 915, in get_tensor
    return CheckpointReader_GetTensor(self, compat.as_bytes(tensor_str))
tensorflow.python.framework.errors_impl.NotFoundError: Key _CHECKPOINTABLE_OBJECT_GRAPH not found in checkpoint

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/spleeter/__main__.py", line 58, in <module>
    entrypoint()
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/spleeter/__main__.py", line 54, in entrypoint
    main(sys.argv)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/spleeter/__main__.py", line 46, in main
    entrypoint(arguments, params)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/spleeter/commands/train.py", line 121, in entrypoint
    evaluation_spec)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/training.py", line 473, in train_and_evaluate
    return executor.run()
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/training.py", line 613, in run
    return self.run_local()
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/training.py", line 714, in run_local
    saving_listeners=saving_listeners)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 370, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1161, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1195, in _train_model_default
    saving_listeners)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1490, in _train_with_estimator_spec
    log_step_count_steps=log_step_count_steps) as mon_sess:
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 584, in MonitoredTrainingSession
    stop_grace_period_secs=stop_grace_period_secs)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 1014, in __init__
    stop_grace_period_secs=stop_grace_period_secs)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 725, in __init__
    self._sess = _RecoverableSession(self._coordinated_creator)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 1207, in __init__
    _WrappedSession.__init__(self, self._create_session())
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 1212, in _create_session
    return self._sess_creator.create_session()
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 878, in create_session
    self.tf_sess = self._session_creator.create_session()
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 647, in create_session
    init_fn=self._scaffold.init_fn)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/session_manager.py", line 290, in prepare_session
    config=config)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/session_manager.py", line 220, in _restore_checkpoint
    saver.restore(sess, ckpt.model_checkpoint_path)
  File "/Users/baiyu/opt/anaconda3/envs/spleeter/lib/python3.7/site-packages/tensorflow_core/python/training/saver.py", line 1306, in restore
    err, "a Variable name or other graph key that is missing")
tensorflow.python.framework.errors_impl.NotFoundError: Restoring from checkpoint failed. This is most likely due to a Variable name or other graph key that is missing from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:

Key batch_normalization/beta/Adam not found in checkpoint
	 [[node save/RestoreV2 (defined at /site-packages/tensorflow_core/python/framework/ops.py:1748) ]]

Original stack trace for 'save/RestoreV2':
  File "/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/site-packages/spleeter/__main__.py", line 58, in <module>
    entrypoint()
  File "/site-packages/spleeter/__main__.py", line 54, in entrypoint
    main(sys.argv)
  File "/site-packages/spleeter/__main__.py", line 46, in main
    entrypoint(arguments, params)
  File "/site-packages/spleeter/commands/train.py", line 121, in entrypoint
    evaluation_spec)
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 473, in train_and_evaluate
    return executor.run()
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 613, in run
    return self.run_local()
  File "/site-packages/tensorflow_estimator/python/estimator/training.py", line 714, in run_local
    saving_listeners=saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 370, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1161, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1195, in _train_model_default
    saving_listeners)
  File "/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1490, in _train_with_estimator_spec
    log_step_count_steps=log_step_count_steps) as mon_sess:
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 584, in MonitoredTrainingSession
    stop_grace_period_secs=stop_grace_period_secs)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1014, in __init__
    stop_grace_period_secs=stop_grace_period_secs)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 725, in __init__
    self._sess = _RecoverableSession(self._coordinated_creator)
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1207, in __init__
    _WrappedSession.__init__(self, self._create_session())
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 1212, in _create_session
    return self._sess_creator.create_session()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 878, in create_session
    self.tf_sess = self._session_creator.create_session()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 638, in create_session
    self._scaffold.finalize()
  File "/site-packages/tensorflow_core/python/training/monitored_session.py", line 237, in finalize
    self._saver.build()
  File "/site-packages/tensorflow_core/python/training/saver.py", line 840, in build
    self._build(self._filename, build_save=True, build_restore=True)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 878, in _build
    build_restore=build_restore)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 502, in _build_internal
    restore_sequentially, reshape)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 381, in _AddShardedRestoreOps
    name="restore_shard"))
  File "/site-packages/tensorflow_core/python/training/saver.py", line 328, in _AddRestoreOps
    restore_sequentially)
  File "/site-packages/tensorflow_core/python/training/saver.py", line 575, in bulk_restore
    return io_ops.restore_v2(filename_tensor, names, slices, dtypes)
  File "/site-packages/tensorflow_core/python/ops/gen_io_ops.py", line 1696, in restore_v2
    name=name)
  File "/site-packages/tensorflow_core/python/framework/op_def_library.py", line 794, in _apply_op_helper
    op_def=op_def)
  File "/site-packages/tensorflow_core/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 3357, in create_op
    attrs, op_def, compute_device)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 3426, in _create_op_internal
    op_def=op_def)
  File "/site-packages/tensorflow_core/python/framework/ops.py", line 1748, in __init__
    self._traceback = tf_stack.extract_stack()

Environment

OS
MacOS  10.15.1

Installation type
pip

RAM available
8G

Hardware spec
Intel Core i5  2.8 GHz

Additional context

I fixed. Use GradientDescentOptimizer
    def _build_optimizer(self):
        """ Builds an optimizer instance from internal parameter values.

        Default to AdamOptimizer if not specified.

        :returns: Optimizer instance from internal configuration.
        """
        name = self._params.get('optimizer')
        if name == self.ADADELTA:
            return tf.compat.v1.train.AdadeltaOptimizer()
        rate = self._params['learning_rate']
        if name == self.SGD:
            return tf.compat.v1.train.GradientDescentOptimizer(rate)
        # return tf.compat.v1.train.AdamOptimizer(rate)
        return tf.compat.v1.train.GradientDescentOptimizer(rate)


Can't close an host request if expired

Subject: Can't close an host request if expired
Description:
Like in the title the expired host request remain in pending and I can't close it
Results:
Backend version: develop-58373f44
Frontend version: develop-58373f44
User Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36
Page: https://couchers.org/messages/chats/91713
User: andreaa (40293)

#3526


Add optional block_identifier

Optional block_identifier allows historical data to be read.

that's interesting... wasn't it populated by default by the underlying library?

Yes, but this allows users to pass in custom block numbers so you look back in time.

Yes, but this allows users to pass in custom block numbers so you look back in time.

correct, if that's the use case then yea, this is required.

Implemented in aa12a6fa400af8448071b2e31feb8af6984703a4


Unchecking "allow pages to choose their own fonts" in Firefox causes blank PDFs.

Attach (recommended) or Link to PDF file here:  (any)
Configuration:

Web browser and its version: Current Firefox Nightly
Operating system and its version: Up-to-date Win10
PDF.js version:  Current
Is a browser extension: no

Steps to reproduce the problem:

In Firefox, Options -> Language And Appearance -> Advanced , uncheck the "Allow pages to choose their own fonts, instead of your selections above" checkbox and select a font of your own preference that is not one of the most commonly used (Arial/TimesNewRoman, etc..)
Open any PDF, results should be mostly blank.

What is the expected behavior?
I'm not sure what the "right" behavior here is - when that option is toggled the browser falls back to the chosen default font to display web pages, but it appears that PDF.js falls back to nothing, so the PDF is full of blank spaces, and nothing is displayed.  Is the right behavior a best-effort rendering with the selected default font? Should pdf.js ignore that pref? I'm not sure; what it's doing is clearly not the right thing, but I don't know what a users' expectations should be in this case.

Closing since this is a duplicate of #7549. In short, we don't have such a fallback system yet.


gl-texture-cube

Likely tricky as gl-texture2d has to cover a lot of ground, but this would be super useful for enabling skyboxes (#4) and reflection/refraction among other things :)

I've got a first draft of this here: github/npm.
It's based heavily on gl-texture2d. So heavily, in fact, that I'm not sure we'll want to keep them separate going forward - there's a lot of duplicated code. Up to you guys!
It's very bare-bones right now - all it does is create cube textures from DOM elements, not empty ones or from ndarrays. I'll probably add stuff as I need it or you guys ask me to. :)

I've got a first draft of this here: github/npm.
It's based heavily on gl-texture2d. So heavily, in fact, that I'm not sure we'll want to keep them separate going forward - there's a lot of duplicated code. Up to you guys!
It's very bare-bones right now - all it does is create cube textures from DOM elements, not empty ones or from ndarrays. I'll probably add stuff as I need it or you guys ask me to. :)

This looks great so far! I'm leaning more to keeping it separate for simplicity's sake, but that's more @mikolalysenko's area :)
p.s. I've been meaning to ask, would you like us to add you to the stackgl org on github/npm? :D

Thanks! I'm in agreement regarding keeping it separate. Maybe there's a clean way to separate the shared stuff into a gl-texture package.
As far as making me official goes... That. Would. Be. AWESOME! :D

Sweet! You've been doing great stuff lately :grin: I'll do that now :)

:tada: :tada: :tada: :tada: :smile:


Add Amazon Clone

Amazon Clone using React Js with proper functionality & used the stripe to make demo payments and in the end, you will get to see your orders history on the Order Page

/assign


Error when trying to build cluster

I'm on ubuntu 18.10 with Docker version 18.06.1-ce.
When i try to launch it.
$ ./dind-cluster-v1.12.sh up
WARNING: No swap limit support
WARNING: No swap limit support
WARNING: No swap limit support
WARNING: No swap limit support
* Making sure DIND image is up to date
v1.12: Pulling from mirantis/kubeadm-dind-cluster
Digest: sha256:8e679951101f3f2030e77a1146cc514631f21f424027fcc003fc78a0337eb730
Status: Image is up to date for mirantis/kubeadm-dind-cluster:v1.12
* Starting DIND container: kube-master
./dind-cluster-v1.12.sh: line 1040: DIND_K8S_BIN_DIR: unbound variable

same issue here
OS: RHEL 7.5
DOCKER VERSION: 18.09
./dind-cluster-v1.12.sh up

Making sure DIND image is up to date
v1.12: Pulling from mirantis/kubeadm-dind-cluster
Digest: sha256:8e679951101f3f2030e77a1146cc514631f21f424027fcc003fc78a0337eb730
Status: Image is up to date for mirantis/kubeadm-dind-cluster:v1.12
Starting DIND container: kube-master
./dind-cluster-v1.12.sh: line 1040: DIND_K8S_BIN_DIR: unbound variable

So, shellcheck say that it's better to use -n than ! -z
I just saw that the script have been modified.
I will give it a try.
$ shellcheck myscript

Line 1:
if [[ ! -z ${DIND_K8S_BIN_DIR:-} ]]; then
^-- SC2148: Tips depend on target shell and yours is unknown. Add a shebang.
      ^-- SC2236: Use -n instead of ! -z.

Line 2:
       opts+=(-v ${DIND_K8S_BIN_DIR}:/k8s)
                 ^-- SC2206: Quote to prevent word splitting, or split robustly with mapfile or read -a.


Cache not busted from admin anymore

Hi,
With the latest version of Strapi (3.4.1) I noticed the cache isn't busted anymore when saving/updating an entry in the CMS.
I did notice in the source (https://github.com/patrixr/strapi-middleware-cache/blob/master/lib/index.js#L189) that the admin REST endpoint refer to /content-manager/explorer/:scope and that Strapi uses /content-manager/collection-types/:scope.
I'm not fully sure if these routes have changed in the latest version of Strapi, but I think this prevents the busting of the cache as those do not match anymore.

@roelbeerens Thank you for finding the fix, I've released version 1.4.1 to NPM with that included


4 add strike line descriptor objects

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

Project coverage is 91.35%. Comparing base (5d0cffb) to head (09cd20b).
Report is 1 commits behind head on main.

Files
Patch %
Lines

thermal_events/strike_line_descriptor.py
64.81%
19 Missing :warning:

thermal_events/thermal_event.py
13.33%
13 Missing :warning:

thermal_events/thermal_event_instance.py
33.33%
6 Missing :warning:

thermal_events/crud/strike_line_descriptor.py
95.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #5      +/-   ##
==========================================
- Coverage   94.68%   91.35%   -3.33%
==========================================
  Files          13       16       +3
  Lines         752      879     +127
==========================================
+ Hits          712      803      +91
- Misses         40       76      +36

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


Shutdown socket before closing it.

As stated in socket module, the close() method releases the resource associated with the
connection but does not necessarily close the connection. Thus, this commit introduces a call to
the 'shutdown()' method before closing the socket.

Thanks!


Progress Bar (TDR-16)

Jira card: https://national-archives.atlassian.net/browse/TDR-16?atlOrigin=eyJpIjoiYjQ5MWMxMTNmZDFhNDc3MmJjZWZlYTBkN2IyYTY4YWQiLCJwIjoiaiJ9
[TDR-21 & TDR-19]
This PR is showing that upon selecting a file on the upload page and clicking continue, the file-upload div is hidden and the progress-bar div is visible. This also shows the progress bar extracting the metadata up until 50% as the other half will be completed with s3 uploads.

When I run this locally, I still see the unstyled version of the progress bar:

How do the custom styles get loaded in? Is there a missing npm library or have I missed a build step? I've run npm install and npm run build:local.

Hi Suzanne, have you tried commenting this line out?
https://github.com/nationalarchives/tdr-transfer-frontend/blob/5d52d73f875c27c0a5a78917a22a34bfe9e8e682/npm/src/clientfileprocessing/index.ts#L74

@rsulxo I've been testing it with a large file, so I have time to see the progress bar for the metadata before it reaches the S3 upload step.


New Crowdin updates

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

v0.23.1
GitHub release

Your semantic-release bot :package::rocket:


[SymfonyStaticDumper] Translations are ignored for localized routes

SymfonyStaticDump seems always to use the default_locale from config/packages/translation.yaml for Translatable Objects.
https://symfony.com/doc/current/routing.html#localized-routes-i18n
https://symfony.com/doc/current/translation.html
https://symfony.com/doc/current/translation/locale.html
Is there a way to tell SymfonyStaticDump to use the different locales set by the localized route?

Hi, there is no such way yet. But it would be helpful addition :+1:

Closing for lack of feedback and missing PR.
Feel free to re-open with one.


feat: serialize logger messages

So that you could print objects, nulls/undefineds, arrays, functions, and others.

Released: v0.2.0 🎉
This has been released in v0.2.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @open-draft/logger@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Updates are a pain

Why can't Power BI Desktop be updated through Windows Update? Or when you update Office 365?
Or even offered as a product category in SCCM?

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

ID: ba6a76e2-8d94-5e76-bfb6-971c3b2c7c85
Version Independent ID: f7bd2111-3bb0-fb08-0f23-a31efd407f66
Content: What's new in the latest Power BI Desktop update? - Power BI
Content Source: powerbi-docs/desktop-latest-update.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @tyddaj -- Thanks for the feedback!
This is a good place to make documentation feedback.
https://ideas.powerbi.com/forums/265200-power-bi is the place to submit product feedback. Plus you can look through it and see if anyone else has suggested the same thing already.
Thanks!


Question about hasSynonym property

I was not able to find best practices / rules for using oboInOwl:hasSynonym and its sub properties (e.g. oboInOwl:hasExactSynonym). In particular, for some cases I need to represent some metadata (not only editorial) about labels (e.g. their source, author, and other).
To ensure OBO compliance I am using oboInOwl:hasExactSynonym, but not sure whether the intended use-cases involve also resources as fillers (not just literals). Basically, I need st. similar to skosxl:Label.
What is the intended usage of oboInOwl:hasSynonym and its sub properties? Thanks a lot.

Hi @psiotwo
The guidelines for GO synonym types are here: https://wiki.geneontology.org/Synonyms#Synonym_scopes
Does that address your question?
Thanks, Pascale

@pgaudet thanks a lot for the link to the wiki. It does not seem to contain an explicit discussion about what should be a filler here. But I found this query which seems to suggest that OWL annotation mechanism is the anticipated way of modeling the metadata here.

OK great!


docs:Auto Gen of Reference Page

added auto gen for reference pages plus the  makefile update for the same.
There is some issues as a lot of  pages ( both init and otherwise ) are empty.

quick tip: try to keep PRs with: docs:Auto Gen of Reference Page by zodwick · Pull Request #1408 · explodinggradients/ragas


Mohsen / added webpack bundle analyzer

Changes:

added webpack bundle analyzer gatsby plugin
on each build it will generate a html file in webpack-bundle-report in
the root of the project.
added this new folder to .gitignore.

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[x] Dependency update
[ ] Documentation update
[ ] Release

i think this runs on each build so maybe its better to add a script for generating the report in package.json

thanks for the suggestion, added the npm script for generating report.


Animation panel appears in incorrect location

Bug Description
When many tabs are open the animation panel appears up to the animation section so there is no context where the panel animation belongs to. (@angelapgUX  - can you provide some additional detail on this issue please)
Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Suggested update to solve this in the existing structure here: https://github.com/google/web-stories-wp/pull/5503
Pending 👍  from @angelapgUX
(We've been chatting in slack, posting here for posterity and inclusion)

hey @angelapgUX / @o-fernandez  / @samitron7
could I get one of you to confirm that this interim solution to get a "label" onto the open animation effect dropdown is ok? I'd love for it to be done for this release.  It's just the "Select Animation" on top of the "No Effect" button.

Verified in QA

@BrittanyIRL and I chatted offline and adding our convo here. This quick fix is ok but we'll run into this issues for all the dropdown so I filed a more robust solution here.

@samitron7 Ok to close this ticket since you opened a new one for a more robust solution?

@samitron7 Ok to close this ticket since you opened a new one for a more robust solution?

@samitron7 Ok to close this ticket since you opened a new one for a more robust solution?

sounds like it!

@samitron7 Ok to close this ticket since you opened a new one for a more robust solution?

sounds like it!


Set URL for the guide to the repository

On GitHub repositories you can set a URL which will be shown next to the description here:

I think we should provide the URL to the getting started guide. This is a more accessible place than the README (where it should also be linked, of course) as no scrolling down or parsing text is required and users just sort of expect the most relevant link to be there.

Thanks. Done. Please have a look and check if that's what you had in mind.

It is, thanks!


Why does the MVP return the location of a match rather than just the existence of a match?

enclave code should be returning a binary for whether there exists a match or not -- this is average-case more efficient (since you can break out of the loop as soon as you find a match) as well as less leaky on the info side.

Our thinking is users / client apps get important information about risk from knowing some information about the match. I.e., a match in a small cafe > risk than a match in an open park.

Leor, when and where is important.

If you know where you had a high risk interaction, you can let ppl know who were potentially with you at that time
If you know when you had a high risk interaction, you can let ppl know whom you've been with after (importance of time)

Alright, fair

Closing the issue as we think it's resolved


Can't Set An Enum With an Integer

When using the new enum feature in rails 4.1.0.rc1, rspec tests fail when attempting to set an enum with an integer vs a string. This only occurs during tests, but not when running the server.
Failures:

1) Api::V1::CollectionsController when creating a new collection with valid params should return 201
 Failure/Error: post :create, user_id: @user.id, collection: @collection
 ArgumentError:
   '0' is not a valid privacy_level
 # ./app/controllers/api/v1/collections_controller.rb:9:in `block in create'
 # ./app/controllers/api/v1/collections_controller.rb:8:in `each'
 # ./app/controllers/api/v1/collections_controller.rb:8:in `create'
 # ./spec/controllers/api/v1/collections_controller_spec.rb:16:in `block (3 levels) in <top (required)>'

It is a rails issue? So how do we bypass it?
PS: I started hitting this issue when i upgraded from 6.1 to 7.1 for rails. Rails recently added enum validations as well, i thought it might be related to that, but seems like it is something else

If you’re experiencing a problem, I suggest creating a new issue with a reproduction example, @ziaulrehman40 . It would be helpful if you could ensure it’s not reproducible with native Rails tests prior to filing.
Most probably, you set an invalid value somewhere and as you mention, Rails started detecting that.

Thanks for responding @pirj , i have for now added as: :json to my requests, and it solved for now.


yarn build:tflite fails

I need to update the size of modelBuffer to use a bigger model of MediaPipe (MultiSegmentation).
I'm executing yarn build:tflite but it fails with the following error:
invalid registered toolchain '@local_config_python//:py_toolchain': error loading package '@local_config_python//': Unable to find package for @python//:defs.bzl: The repository '@python' could not be resolved: Repository '@python' is not defined.

Do you have an idea what could cause the issue?

I'm currently trying to fix the build. I managed to pass the Python error but now there are other errors popping related XNNPACK.
You can find some updates in the branch fix-tflite-build-python. And you can see the latest logs here.
This is a tedious investigation and I won't have a lot of time to spend on it. So perhaps could you also experiment on a fork on your own.
Also now that there are other builds of tflite in tfjs and mediapipe repositories (see https://github.com/Volcomix/virtual-background/issues/38), have you considered trying to switch to them?

Have tou tried using https://developer.mozilla.org/en-US/docs/Web/API/HTMLVideoElement/requestVideoFrameCallback instead of rAF ?

I am not using (tflite.js | tflite.wasm | tflite-simd.js | tflite-simd.wasm) from this repository but instead  vision_wasm_internal.
(If you look into "@mediapipe/tasks-vision/wasm/" you'll find the files I'm talking about)

inside of vision_wasm_internal, requestAnimationFrame is used. I don't think MediaPipe provide the C++ files from which vision_wasm_internal was compiled.

However, you've pointed out something I didn't realize. In my implementation I AM using requestVideoFrameCallback. requestVideoFrameCallback freezes as well when changing tabs

Therefore I may be able to make it work with my implementation if I try using a web worker similar to this demo. I thought I was done for because the requestAnimationFrame is inside of vision_wasm_internal but I may be wrong.

Otherwise, as to why the bazel build fails, I think this is the issue but I've yet to try the fix:
https://gateway240.com/blog/mediapipe-macos-build-failure/

I replaced requestVideoFrameCallback by setTimeout, added timerWorker.ts, added timerHelper and it worked! Thanks again for pointing that out saghul and for your time Volcomix.
--    videoFrameCallbackHandle = video.requestVideoFrameCallback(render);
++   timerWorker.setTimeout(render, 0);
If anybody is interested I could do a fork / branch where I implement vision_wasm_internal and MultiSegment model with ImageSegmenter into this demo.

Err, should I re-open the issue since it is related to yarn build:tflite though?

I replaced requestVideoFrameCallback by setTimeout, added timerWorker.ts, added timerHelper and it worked! Thanks again for pointing that out saghul and for your time Volcomix.
-- videoFrameCallbackHandle = video.requestVideoFrameCallback(render); ++ timerWorker.setTimeout(render, 1000/30); // 30fps
If anybody is interested I could do a fork / branch where I implement vision_wasm_internal and MultiSegment model with ImageSegmenter into this demo.

I would be interested in having that fork :)


Updated problem example to a working implementation matching the solution style

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

@co16353sidak Actually, the user is correcting the existing solution.  The existing solution no longer works in latest version of Chrome. The solution now follows the standard in which you must specify what happens for the 3 possible cases (a < b, a > b, and a === b).

@co16353sidak  @RandellDawson
Exactly, the current solution is outdated and needs to be updated.

Congrats @dchenmei on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Cannot mount elasticsearch keystore in pod, device busy

I'm trying to mount the elasticsearch keystore per the documentation but I keep getting the error below. I've verified the the elasticsearch keystore file is valid (by adding it to a test continer and testing the values).
Error:
Exception in thread "main" java.nio.file.FileSystemException: /usr/share/elasticsearch/config/elasticsearch.keystore.tmp /usr/share/elasticsearch/config/elasticsearch.keystore: Device or resource busy
Steps taken:

Command to create the secret:
kubectl create secret generic elasticsearch-keystore --from-file=./elasticsearch.keystore

SecretMounts in my yaml configuration:

  secretMounts:
  - name: elastic-certificates
    secretName: elastic-certificates
    path: /usr/share/elasticsearch/config/certs
  - name: elastic-license
    secretName: elastic-license
    path: /usr/share/elasticsearch/config/license
  - name: elasticsearch-keystore
    secretName: elasticsearch-keystore
    path: /usr/share/elasticsearch/config/elasticsearch.keystore
    subPath: elasticsearch.keystore

Is there something I am missing?

It looks like you did everything right to me.
Can you give me the output of the following commands:
You can attach into one of the containers by running kubectl exec -ti elasticsearch-master-0 bash
head -n1 /usr/share/elasticsearch/config/elasticsearch.keystore
ls -lhatr /usr/share/elasticsearch/config/
df -h
elasticsearch-keystore list

Could you also give me the following:

The rest of your configuration
Output of kubectl get events after attempting to deploy
Kubernetes provider and version (e.g. Google Kubernetes Engine 1.12)

I'm also running into this same issue after following the instructions for using the keystore in the readme - created the same way as in this issue.
This is running on GKE 1.11.8-gke-6 and I'm not seeing anything of note in kubectl get events, just appears to create the container/pull container etc, and then "back off restarting failed container".

@ofaz Thanks for the report! Could you give me the following information to try to reproduce it:

Output of helm get elasticsearch (or whatever your release name is)
Output of kubectl get pod -o yaml elasticsearch-master-0
Output of kubectl get events
The output of these commands run from within one of the containers:

head -n1 /usr/share/elasticsearch/config/elasticsearch.keystore
ls -lhatr /usr/share/elasticsearch/config/
df -h
elasticsearch-keystore list

I just bumped one of our internal clusters to use 7.1.0 and got the same error. So this seems to be an issue with how 7.1.0 is accessing the keystore differently to previous releases. No need to send anymore debug information now that I can reproduce it.

Well that was a fun journey. I found it though!
In https://github.com/elastic/elasticsearch/pull/41701 the internal format for the keystore was bumped from version 3 to version 4. On startup Elasticsearch notices this and attempts to upgrade the format of the keystore. All mounted secrets and configmaps in Kubernetes are always readonly. So when it tries to make the change you get the error as seen above.
So the fix is to either:

Make sure you are creating the keystore with the right version of Elasticsearch. So if you are using 7.1.1 in the cluster you should use the same version when creating the keystore
If you already have an existing keystore you should run elasticsearch-keystore upgrade with the right Elasticsearch version to get it upgraded to the right format.

Hi,
I have the same issue with version 6.8.1. Keystore was created using the same version.

@JanKowalik if it really was made with the same version than this sounds like a different issue. Can you give me the exact commands you used to create the keystore and the output of helm get elasticsearch (replace elasticsearch with your release name).

I will try it again to make sure and if it does not work I will provide the information you are sking for.
Thank you.

It did not work this time too.
I generated the keystore within docker using elastic 6.8.1 and the created a secrete out of it.
The command I ran within docker image is:
elasticsearch-keystore create
I moved the created file out of docker container and used this command to create the secret:
kubectl create secret generic elasticsearch-keystore --from-file=./elasticsearch-keystore/elasticsearch.keystore -o yaml --dry-run > manifests/elasticsearch-keystore-config-secret.yaml
I used helm chart to generate manifests only. I can attach the manifest files and values I used if that helps?
elasticsearch-master-nodes.txt
values-data-nodes.txt
values-master-nodes.txt
elasticsearch-data-nodes.txt
I did not include secrets here.

@JanKowalik Thank you for providing the extra details. I think that the issue you are running into is because you have the $ELASTIC_PASSWORD set but aren't adding it to your keystore as the bootstrap password. The docker image startup script tries to add this to the keystore when it is set.
You want to add it with:
elasticsearch-keystore add -x bootstrap.password

Once https://github.com/elastic/helm-charts/pull/154 is finished off there won't be any need to manually create and update the keystore anymore.

Yeah, I did not add the bootstrap.password. I did not think it was necessary if I am using the default password.
I will give it a go and report back.
Thank you for your help!

Nearly works. But I think this is a different problem now.
How does setting bootstarp.password influence elastic user password? I have 2 out of 3 nodes in either master-nodes or data-nodes groups connected fine but thirds are complaining about authentication.
[2019-07-18T16:20:48,202][INFO ][o.e.x.s.a.AuthenticationService] [elasticsearch-data-2] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

Nearly works. But I think this is a different problem now.
How does setting bootstarp.password influence elastic user password? I have 2 out of 3 nodes in either master-nodes or data-nodes groups connected fine but thirds are complaining about authentication.

Which version of Elasticsearch are your running? In the manifest output I see the image is image: "elasticsearch:pulse". The reason that I ask is that in Elasticsearch versions before security was included in basic (before 6.8 release) you needed to activate the license for the cluster to fully form. What would happen is that the first 2 nodes would start bootstrapping the cluster, and the third one would fail to join until the license was enabled. The output from curl -u elastic:$ELASTIC_PASSWORD localhost:9200/ will show the version.

It uses version 6.8.1

How does setting bootstarp.password influence elastic user password?

To be clear, the bootstrap.password should be set to what you have for $ELASTIC_PASSWORD. Have all nodes in the cluster been restarted with the new keystore btw?

I have an issue with kibana-keystore if mounted as k8s secret now.
onfiguring logger failed: { Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:494:3)
    at tryReadSync (fs.js:333:20)
    at readFileSync (fs.js:370:19)
    at Keystore.load (/usr/share/kibana/src/server/keystore/keystore.js:97:45)
    at new Keystore (/usr/share/kibana/src/server/keystore/keystore.js:46:10)
    at readKeystore (/usr/share/kibana/src/cli/serve/read_keystore.js:40:20)
    at applyConfigOverrides (/usr/share/kibana/src/cli/serve/serve.js:186:41)
    at applyConfigOverrides (/usr/share/kibana/src/cli/serve/serve.js:50:42)
    at config_1.RawConfigService.rawConfig (/usr/share/kibana/src/core/server/bootstrap.js:33:134)
    at MapSubscriber.RawConfigService.config$.rawConfigFromFile$.pipe.operators_1.map.rawConfig [as project] (/usr/share/kibana/src/core/server/config/raw_config_service.js:41:24) errno: -21, syscall: 'read', code: 'EISDIR' }

 FATAL  Error: EISDIR: illegal operation on a directory, read

Shall I open another ticket for that?

@Crazybus: Shall I open another ticket for that?

Yes please! If I'm honest I have never actually used the keystore for Kibana with the helm-charts. My bet is that its going to be failing for the same issue as Elasticsearch (docker image trying to automatically add the ELASTICSEARCH_PASSWORD to the keystore on startup.

The changes in #90 will also be ported to the other charts which will make this a lot easier to manage.


Quick Edit does not work on JS files

I click on Quick-Edit and see nothing.
Log error says:
main.js:815 Uncaught TypeError: Cannot read property 'getCursor' of null
more log errors:
Recursive tests with the same id are not supported. Timer id: INLINE_WIDGET_OPEN
Recursive tests with the same id are not supported. Timer id: JAVASCRIPT_INLINE_CREATE

@yaronby Try Debug > Reload Without Extensions to see if problem is being caused by an extension.

Yes, The problem stays without extensions.
Brackets version: Release 1.1 build 1.1.0-15558
Run on Windows 7.

I have the same problem, with and without extensions.
Problem: JavaScriptQuickEdit call brackets._jsCodeHintsHelper and session is null.
Brackets version: Version 1.2 édition 1.2.0-15697 (release 8f82e2a97)
OS: Windows 7 (x86)

OK, problem solved.
I was working on EJS files and this extension is not supported by JavaScriptCodeHints. That's why there was no session.


isi function ValueError

Given spikes
>>> spike_slice
<SpikeTrain(array([  503.8  ,   520.05 ,   536.325,   552.625,   568.925,   585.225,          601.575,   617.95 ,   634.325,   650.725,   667.15 ,   683.575,          700.05 ,   716.525,   733.025,   749.55 ,   766.075,   782.625,          799.175,   815.75 ,   832.35 ,   848.95 ,   865.575,   882.225,          898.9  ,   915.575,   932.275,   949.   ,   965.75 ,   982.5  ,          999.25 ,  1016.025,  1032.825,  1049.65 ,  1066.5  ,  1083.35 ,         1100.225,  1117.125,  1134.025,  1150.95 ,  1167.9  ,  1184.875,         1201.85 ,  1218.85 ,  1235.875,  1252.9  ,  1269.95 ,  1287.025,         1304.1  ,  1321.175,  1338.275,  1355.4  ,  1372.525,  1389.675,         1406.85 ,  1424.05 ,  1441.25 ,  1458.5  ,  1475.75 ,  1493.   ]) * ms, [500.0, 1500.0])>
When I run the elephant.statistics.isi to get the inter-spike interval
isi(spike_slice)
I get
>>> isi(spike_slice)
Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "~/miniconda2/lib/python2.7/site-packages/elephant/statistics.py", line 49, in isi     intervals = np.diff(spiketrain, axis=axis)   File "~/miniconda2/lib/python2.7/site-packages/numpy/lib/function_base.py", line 1578, in diff     return a[slice1]-a[slice2]   File "~/miniconda2/lib/python2.7/site-packages/neo/core/spiketrain.py", line 461, in __sub__     _check_time_in_range(spikes - time, self.t_start, self.t_stop)   File "~/miniconda2/lib/python2.7/site-packages/neo/core/spiketrain.py", line 66, in _check_time_in_range     (value, t_start))
ValueError: The first spike ([ 16.25   16.275  16.3    16.3    16.3    16.35   16.375  16.375  16.4   16.425  16.425  16.475  16.475  16.5    16.525  16.525  16.55   16.55   16.575  16.6    16.6    16.625  16.65   16.675  16.675  16.7    16.725   16.75   16.75   16.75   16.775  16.8    16.825  16.85   16.85   16.875   16.9    16.9    16.925  16.95   16.975  16.975  17.     17.025  17.025   17.05   17.075  17.075  17.075  17.1    17.125  17.125  17.15   17.175   17.2    17.2    17.25   17.25   17.25 ] ms) is before t_start (500.0)
Why am I getting this error?
Clearly,
>>> spike_slice[0]
array(503.79999999967873) * ms
does not start before t_start(500.0)
Does isi function not work with slice taken from a complete spike train?
Note:

I don't get the error with isi(whole_spike_train)
I get the same error with np.diff(spike_slice)
Elephant 0.4.1
Neo 0.5.1
this appears to be linked with Neo issue #412

Hi Lungsi, I think this error has been fixed in the current elephant master branch. I can reproduce your error with elephant 0.4.1, but not with the master branch using the following minimal example:
>>> k=neo.SpikeTrain([1, 2, 502, 506, 1000]*pq.ms, t_start=0*pq.ms, t_stop=2000*pq.ms)
>>> l=k.time_slice(500*pq.ms, 1500*pq.ms)
>>> s.isi(l)
Out: array([   4.,  494.]) * ms

Indeed, as far as I recall this had to do with Neo introducing checks for spike times, therefore the SpikeTrain object is no longer used to return ISI values.


Update peers dependencies for React Native 0.63

This also removes and shuffles some unused dependencies.

thanks for the update


test cases for invalid input sequence (relative locktime)

[x] issue #178
[x] follows contribution guide
[x] code change includes tests

should_panic

we can't use should_panic
we are returning a ByteArray containing the error message  not panic

should_panic

we can't use should_panic
we are returning a ByteArray containing the error message not panic

Use unwrap(), on the result it will panic. Or you can destruct the error to get the error message.

(expected: ("...",))

am getting the following error
 Result::unwrap failed.
am setting this
 #[should_panic(expected: ("Relative block-based lock time is not respected: current height 603019, outpoint height 603018, lock time 144 blocks",))]


[WIP] Re-open log files on SIGUSR1 signal

With this pull request all the Python service processes now re-open log files when receiving SIGUSR1 signal.
To test it start the st2api service and run the commands listed bellow.
Screen 1:
tail -F logs/st2api.log

Screen 2:
python ./st2client/st2client/shell.py runner list - you should see new messages in the log file
rm logs/st2api.log
python ./st2client/st2client/shell.py runner list - you should see no new messages in the log file since the process is still referencing the old file handle
kill -USR1 <st2api pid>
python ./st2client/st2client/shell.py runner list - you should see new messages in the log file because SIGUSR1 causes process to reopen the log files

TODO:

[x] Do the same for all the Python services
[x] Update log rotate configs
[x] Remove rotating file handler code

Do we need to remove RotatingFileHandler?

@manasdk The question is if we need it for the dev environment or not. If we do, we then need two different set of logging configs (dev, prod).
Or we could just leave it there, but update the default values so no rotation happens. This way user needs to explicitly enable it if they want to use that instead of logrotate.

@kami - I guess I don't understand why logrotate is better than RotatingFileHandler.

@manasdk Alright, let me try to clarify it again.

e.g. who calls kill -USR1

This would be called by an external program which is responsible for rotating logs. In our case, this is logrotate - we just need to update logrotate.conf to send this signal to the service instead of restarting it.

Oh ok. in postrotate - got it.
So still these are 2 parallel choices - yes/no?

@manasdk Yeah.
@jfryman added a log rotate config and we will install this config in the package based deployment which means log rotation will already be taken care of in the packaged based deployments.

I've pushed a change which updates log rotate config - f19f0580249683915a31de4741bb0b44e02ee995, 07404817b838e67447249edfec7d79c310ee020b
I also pushed a logging config change which disables log rotation by default. I didn't touch the handler so if user for some reasons wants to use Python and not logrotate to rotate the logs for them, they can do that by updating the logging configs (need to add some docs for the whole log rotation stuff).

Added some docs about configuring log rotation - 423d998418ac25c87d9d7310e4915c6283eb72c0.

@Kami - Seems like logrotate wins by default. No use arguing over this any longer.
+1

Note / reminder for us - we still need to update packaging manifest files to copy over logrotate config on installation.


Fix wrong calculation of group availability

Closes https://github.com/pypeclub/pype/issues/1335

By accident contains code solving https://github.com/pypeclub/pype/issues/1337
Implementation is ready for testing


graying out w/ affinity color when disabled

Rather than replacing the fill color with grey, we should just grey-ify the existing block color. This lets blocks with affinity zones keep their color to show the affinity association.

https://github.com/pothosware/pothos/commit/9fda413914c1bc015f626222392e2757fafbbefb


Optimization : Erasure of Levels and Sets.

Ocaml unboxes constructors that have zero arity, they are constant.
Agda possibly adds the levels and the Sets into the constructor even though they are never used.
This will force us to translate them into boxes.

There is little value in this optimization because fields are introduced only if the Set and Level are part of the constructor . For example this does not increase the arity of the constructor :
data G {l : Level} {A : Set} : Set where
  g : G {l} {A}

Moreover if the Set and Level are part of the constructor and they are used to define the type of other fields, I believe that it is not possible to export that data type into OCaml, its type system does not support it.


virtualbox: 6.1.10 -> 6.1.14

Motivation for this change
6.1.14 is the latest release of VirtualBox
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Looks like VirtualBox 6.1.10 build is broken on current nixos-unstable (61525137fd10) when using kernelPackages = pkgs.linuxPackages_latest:
In file included from /nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/include/asm-generic/percpu.h:7,
                 from /nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/arch/x86/include/asm/percpu.h:556,
                 from /nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/arch/x86/include/asm/preempt.h:6,
                 from /nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/include/linux/preempt.h:78,
                 from /nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/include/linux/spinlock.h:51,
                 from /build/virtualbox-6.1.10-modsrc/vboxdrv/linux/../SUPDrvInternal.h:79,
                 from /build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c:32:
/build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c: In function 'supdrvOSChangeCR4':
/build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c:760:38: error: 'cpu_tlbstate' undeclared (first use in this function); did you mean 'cpuhp_state'?
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                                      ^~~~~~~~~~~~
/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/include/linux/percpu-defs.h:318:9: note: in definition of macro '__pcpu_size_call_return'
  318 |  typeof(variable) pscr_ret__;     \
      |         ^~~~~~~~
/build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c:760:24: note: in expansion of macro 'this_cpu_read'
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                        ^~~~~~~~~~~~~
/build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c:760:38: note: each undeclared identifier is reported only once for each function it appears in
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                                      ^~~~~~~~~~~~
/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/include/linux/percpu-defs.h:318:9: note: in definition of macro '__pcpu_size_call_return'
  318 |  typeof(variable) pscr_ret__;     \
      |         ^~~~~~~~
/build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.c:760:24: note: in expansion of macro 'this_cpu_read'
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                        ^~~~~~~~~~~~~
make[4]: *** [/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/scripts/Makefile.build:280: /build/virtualbox-6.1.10-modsrc/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[3]: *** [/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/Makefile:1756: /build/virtualbox-6.1.10-modsrc/vboxdrv] Error 2
make[2]: *** [/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/source/Makefile:185: __sub-make] Error 2
make[2]: Leaving directory '/nix/store/lm27zw14mmif9prrslgawdi0i5wpx25v-linux-5.8.6-dev/lib/modules/5.8.6/build'
make[1]: *** [/build/virtualbox-6.1.10-modsrc/vboxdrv/Makefile-footer.gmk:114: vboxdrv] Error 2
make[1]: Leaving directory '/build/virtualbox-6.1.10-modsrc/vboxdrv'
make: *** [Makefile:58: vboxdrv] Error 2
builder for '/nix/store/1009iybgsnfr9p5vvkc19aajcxcqnklj-virtualbox-modules-6.1.10-5.8.6.drv' failed with exit code 2
cannot build derivation '/nix/store/cv7lscscdxnbnixn1dh7272az51qg7mf-kernel-modules.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/imcfygi6v5yvbd1pzav77nrj50k0z3w0-linux-5.8.6-modules.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/rjxwdazq3zff1iwb5pssgy5iql31wgkx-linux-5.8.6-modules-shrunk.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/yqq8z4y33g46yggpbah68crqd7xzj465-stage-1-init.sh.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/fh0jm66daaf4qnxpd1yx1qci05v36glm-initrd-linux-5.8.6.drv': 1 dependencies couldn't be built

The same configuration builds and runs fine with 6.1.14, so this is a very welcome change :slightly_smiling_face:

Thanks for contribution @Magicloud.
However, the commit message doesn't follow the guideline. please check example section in https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#submitting-changes . Can you please git commit --amend it?

Done.

@evenbrenden One change of 6.1.14 is to support some new features of 5.8 kernel, as I recalled. But not sure if that was exactly what you got.

@evenbrenden One change of 6.1.14 is to support some new features of 5.8 kernel, as I recalled. But not sure if that was exactly what you got.

Yep, thats what currently happens when you use kernel 5.8 with Virtualbox 6.1.10, more information available at:
https://www.virtualbox.org/ticket/19644?cversion=0&cnum_hist=8
But basically, we need this version bump.
Maybe @svanderburg can help with PR review?

Currently testing this on my 20.09 as I'd like to upgrade my kernel to 5.8, but I need VirtualBox for work atm. If everything is fine, I'd merge & backport, but just to be sure - @evenbrenden @bryanasdev000 @Magicloud @turboMaCk are there any issues with this PR I'm currently missing?

No problems here. Been using it with a couple of VMs (Windows and Linux). Running NixOS at a5931fa6e3 with this PR on top.

I can confirm this as well and will merge tonight. First I'd like to take a look at the failing virtualbox VM test though.

Just fixed the virtio support that was originally disabled by @Magicloud due to a misconfigured tarball from upstream. Currently running the VM test locally, after that I'll merge!

Ported to 20.09 as 07504c93648ee155c0f09f2a4b90a6a4cd2a74fc, f3d099fb1d75a2bc3786724c42d0bac1904ca656


Improve Hubble memory usage and performance on decoding events

The first 7 commits are preparatory cleanup and addition/extension of tests to avoid regressions introduced by the successive two commits. These reduce Hubble's memory usage on L3/4 and L7 event decoding as follows:
name         old time/op    new time/op    delta
L34Decode-8    4.10µs ± 5%    3.63µs ± 8%  -11.51%  (p=0.000 n=10+10)

name         old alloc/op   new alloc/op   delta
L34Decode-8    1.24kB ± 0%    1.03kB ± 0%  -16.77%  (p=0.000 n=10+10)

name         old allocs/op  new allocs/op  delta
L34Decode-8      26.0 ± 0%      21.0 ± 0%  -19.23%  (p=0.000 n=10+10)

name        old time/op    new time/op    delta
L7Decode-8    6.37µs ±11%    5.79µs ± 4%   -9.02%  (p=0.000 n=10+10)

name        old alloc/op   new alloc/op   delta
L7Decode-8    1.53kB ± 0%    1.37kB ± 0%  -10.47%  (p=0.000 n=10+10)

name        old allocs/op  new allocs/op  delta
L7Decode-8      36.0 ± 0%      34.0 ± 0%   -5.56%  (p=0.000 n=10+10)

See the individual commit messages for details.

/test

CI is green and reviews were provided by all teams. Marking as ready to merge.


install multiple mt5 on casaos

I have successfully run MT5 on Casaos but can only install 1 MT5, how can I install many MT5s?

You just need to change exposed TCP port and volume to a different location so that they do not collide.


add puppeteer options

This is the first step needed to fix https://github.com/marko-js/marko-util/issues/7
Once this is in and a new version is published, I can send a PR to marko-cli to actually get this working through the CLI.

LGTM 🙂


Add support for Cron Jobs

Closes #13

[X] implement
[ ] write tests

Pull Request Test Coverage Report for Build 308367339

13 of 22 (59.09%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.7%) to 80.532%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

api/src/scheduler/jobs-repo.ts
13
22
59.09%

Totals

Change from base Build 307075718:
-1.7%

Covered Lines:
361

Relevant Lines:
422

💛  - Coveralls


[Actions] push event does not have Activity types

Why:
Closes [issue link]

remove surplus property from the note's sample code explaining the interaction of paths/branches filters
What's being changed:

the note section here: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes). author's note: ~where?~ consider rephrasing this section
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@kaznovac
Thanks so much for opening a PR! I'll get this triaged for review :zap:

This looks good to me -- thanks for the PR!


ArchLinux: patched PKGBUILD for opencv2-opt AUR package

Hi. I'm providing this files for those who (heavily) depend on opencv3 and can not just replace it with the older v2. I experimented a lot and finally got your app working with the /opt libraries from the opencv2-opt AUR package :smiley:

PKGBUILD

pkgname=butterflow
pkgver=0.2.3
pkgrel=1
pkgdesc="Make slow motion and motion interpolated videos from the command line"
arch=('x86_64')
url="https://github.com/dthpham/butterflow"
license=('custom')
makedepends=('python2-setuptools' 'opencl-headers')
depends=('python2-numpy' 'ffmpeg' 'opencv2-opt' 'ocl-icd')
optdepends=('intel-opencl-runtime: Intel processor device support'
            'opencl-nvidia: NVIDIA device support'
            'amdapp-sdk: AMD device suppport')
provides=('butterflow')
conflicts=('butterflow')
install=butterflow.install
source=("http://srv.dthpham.me/butterflow/releases/${pkgname}-${pkgver}.tar.gz"
        "opencv2-opt.patch" "butterflow-opt.sh")
sha256sums=('83e3ce52eef57ae2e4f4b3dc98d97ab354621e4a095d9734751bd876c34b755e'
            'SKIP' 'SKIP')

prepare() {
  cd "${srcdir}/${pkgname}-${pkgver}"

  # apply opencv2-opt patch to use the opencv2 inside /opt
  # for those who need/depend on opencv3 and can not just replace it with the older version
  patch -p1 < "../opencv2-opt.patch"
}

package() {
  cd "${srcdir}/${pkgname}-${pkgver}"
  python2 setup.py install --root="${pkgdir}/" --optimize=1
  install -D -m644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

  # install wrapper script to set LD_LIBRARY_PATH and PYTHONPATH before launching butterflow
  # note: the python script must be named exactly 'butterflow' or weird import errors occur :/
  mkdir -p "${pkgdir}/usr/lib/butterflow"
  mv "${pkgdir}/usr/bin/butterflow" "${pkgdir}/usr/lib/butterflow/butterflow"
  install -m755 ../butterflow-opt.sh "${pkgdir}/usr/bin/butterflow"
}

opencv2-opt.patch

--- butterflow-0.2.3/setup.cfg.orig	2017-04-10 23:34:55.000000000 +0200
+++ butterflow-0.2.3/setup.cfg	2017-06-27 10:37:44.281444271 +0200
@@ -3,3 +3,7 @@
 tag_date = 0
 tag_svn_revision = 0

+[build_ext]
+include-dirs=/opt/opencv2/include
+library-dirs=/opt/opencv2/lib
+rpath=True

butterflow-opt.sh

#!/bin/bash

export LD_LIBRARY_PATH="/opt/opencv2/lib:$LD_LIBRARY_PATH"
export PYTHONPATH="/opt/opencv2/lib/python2.7/site-packages:$PYTHONPATH"
exec /usr/lib/butterflow/butterflow "$@"

I hope this helps some people. It took me way too long to figure this out.

I don't have access to my Arch Linux machine at this moment so I can't try this out yet, but I do think that this should be the default — with BF depending on opencv2 installed to opt so that other people can use opencv3 at the same time. When I'm able to try and verify that it works, I'll update the PKGBUILD with your patches. Thanks for this!

Is there any update w.r.t. to this issue?

I have tried the proposed solution, and I was able to install BF this way alongside with opencv. But I get this error when trying to run it (first time ever user here):
frank@HomeC ~/kdenlive> butterflow -s full,spd=0.25 Megható.mkv
Traceback (most recent call last):
  File "/usr/lib/butterflow/butterflow", line 11, in <module>
    load_entry_point('butterflow==0.2.3', 'console_scripts', 'butterflow')()
  File "/usr/lib/python2.7/site-packages/butterflow/cli.py", line 287, in main
    if not args.sw and not ocl.compat_ocl_device_available():
RuntimeError: opencl call failed

Slightly offtopic: @dthpham can you provide Appimage package for BF?

Here's an alternative patch that handles numpy as well:
--- setup.py.orig	2020-05-15 13:46:33.271309422 -0500
+++ setup.py	2020-05-15 13:46:45.938100357 -0500
@@ -135,6 +135,8 @@

 ocl_ext = Extension('butterflow.ocl', extra_compile_args=cxxflags,
                     extra_link_args=linkflags,
+                    include_dirs=['/opt/opencv2/include'],
+                    library_dirs=['/opt/opencv2/lib'],
                     libraries=mklist(cl_lib, 'opencv_core', 'opencv_ocl'),
                     sources=[os.path.join(pkgdir, 'ocl.cpp')], language='c++')

@@ -156,6 +158,7 @@
         # fallback to the system's numpy
         np_includes = '/System/Library/Frameworks/Python.framework/Versions/'\
                       '{}/Extras/lib/python/numpy/core/include'.format(py_ver)
+np_includes = '/usr/lib/python{}/site-packages/numpy/core/include'.format(py_ver)

 # opencv-ndarray-conversion args
 nddir = os.path.join(vendordir, 'opencv-ndarray-conversion')
@@ -164,7 +167,8 @@
 motion_ext = Extension('butterflow.motion',
                        extra_compile_args=cxxflags,
                        extra_link_args=linkflags,
-                       include_dirs=mklist(nd_includes, np_includes),
+                       include_dirs=mklist(nd_includes, np_includes, '/opt/opencv2/include'),
+                       library_dirs=['/opt/opencv2/lib'],
                        libraries=['opencv_core', 'opencv_ocl',
                                   'opencv_imgproc'],
                        sources=[os.path.join(pkgdir, 'motion.cpp'),


Rule: UseIfInsteadOfWhen

Suggests replacing simple when expressions with an equivalent if else in line with this recommendation: https://kotlinlang.org/docs/reference/coding-conventions.html#if-versus-when
Ran the rule on detekt's codebase and fixed the resulting issues.
Only when expressions with two entries (one of them being else and the other a single condition) are flagged. I tried other versions that also allowed for flagging multiple conditions in a single entry but the rewritten code was no clearer, so made it more conservative. It should be quite safe to enable by default but that can be changed later.

Codecov Report

Merging #1904 into master will increase coverage by 0.05%.
The diff coverage is 85.18%.

@@             Coverage Diff              @@
##             master    #1904      +/-   ##
============================================
+ Coverage     80.43%   80.49%   +0.05%
- Complexity     1950     1957       +7
============================================
  Files           325      326       +1
  Lines          5490     5495       +5
  Branches       1013     1014       +1
============================================
+ Hits           4416     4423       +7
+ Misses          545      543       -2
  Partials        529      529

Impacted Files
Coverage Δ
Complexity Δ

...itlab/arturbosch/detekt/rules/style/MagicNumber.kt
89.61% <100%> (-0.14%)
60 <0> (ø)

...n/kotlin/io/gitlab/arturbosch/detekt/api/Config.kt
89.36% <100%> (+1.6%)
0 <0> (ø)
:arrow_down:

...bosch/detekt/rules/providers/StyleGuideProvider.kt
100% <100%> (ø)
3 <0> (ø)
:arrow_down:

...otlin/io/gitlab/arturbosch/detekt/api/CodeSmell.kt
52.5% <50%> (+0.22%)
10 <3> (ø)
:arrow_down:

...b/arturbosch/detekt/rules/style/UseCheckOrError.kt
90% <50%> (-0.91%)
9 <3> (ø)

...rturbosch/detekt/formatting/OffsetsToLineColumn.kt
78.37% <80%> (-0.57%)
0 <0> (ø)

...rturbosch/detekt/rules/style/UseIfInsteadOfWhen.kt
92.3% <92.3%> (ø)
7 <7> (?)

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 9691e0d...852080e. Read the comment docs.


Swap problem

The bot mainly swap position of pets. It barely do anything else. You should add a limit to the amount of times the bot allowed to swap pet position so it actually does something else than swapping

And it never buy any of the new pets. Because it also never sell

By new i mean tier 2+ pets.

It definitely buys stuff. It also sells. Only thing it cannot do yet is freeze items.
Have you trained a bot from scratch yourself, or have you tried using the pretrained model from here:
https://github.com/andreped/super-ml-pets/releases/tag/v0.0.6
It is far from perfect, but at least there it seems to have learned some relevant stuff. However, we are current trying to improve the reward system to make it more efficient.

 If not its alright

Hmm do you have a video cause i think my system broke the ai or something i wanna see how v6 plays. If not its alright

Don't have a video right now, but I can make a gif later.
Note that the current deployment solution is not that optimized, runtime wise. The reason why it might seems that shuffling is very often done, is because a reorder action does not just mean a single movement, but rather a full change of the current animal order. If the animal order is (0, 1, 2, 3, 4), a reorder action generates a full new order (2, 4, 0, 3, 1). In order to generate the new order, multiple animal swaps will have to be made. This is probably what you are observing.
However, I agree with you that it is rather strange that in a single game it needs to do more than a single reorder, as humans would find it more natural to do it at the end of the shop, right before a battle. However, this is what the AI has found suitable. We could add a feature to better guide it in the reward system, but it is not prioritized atm. Right now we are trying to get the full pipeline stable.

One of the main reasons why the AI is not performing better is because the simulated environment used for training, does not mimic real games well enough. Hence, even if we see a high reward per game, the AI is just playing another computer, and currently a very naive computer. Initially we tested Deep Q-Learning, but for fixing bugs we tried a simpler solution. Hopefully we will be able to add a better reward system.
Note that you are free to contribute to the framework. I have limited time doing this, as I do it in my sparetime, but when I get time I will try to be as productive as possible :) However, I will likely spend more time on developing the framework than training models, but for every release I hope to make an improved model.

If you made the gif pls send it to me tks


Add gif description for easy-to understand this project

Consider making awesome gif that explain or executing AutoRAG and add it to README.md.

add vllm
edit config YAML file in README

Make it simple.
Easy to understand the concept.


Feature/add 13.8.0 browser

relies on https://github.com/cypress-io/cypress-docker-images/pull/312

[x] add node13.8.0-chrome81-ff75 browsers image

@zammer The build is failing.

@jennifer-shehane
The build is failing.
yes it relies on the other PR https://github.com/cypress-io/cypress-docker-images/pull/312

@jennifer-shehane fixed the build now :)

For my learning, how did you know/pick which versions of Chrome/Firefox to install?


[PE-D][Tester B] Date Time format unrecognised though followed

Even though the date time is input according to the last format provided the command is not recognised to work.

Labels: severity.Medium type.FunctionalityBug
original: Cheamybunny/ped#8

Fixes Issue by updating the date parser


there is no index.html in react-admin

there is no index.html in my installation of the current version of react-admin.
Where can I put should the stylesheet link instead?

The index file here is where you load the bundle resulting from building a react-admin app, and is not part of react-admin package.


Windows 11 10.0.22621.1778 not supported

termsrv.zip
thanks :)

I've the same problem, i change the rdpwrap.ini and the termsrv.dll, but still not working... Please help me. Thanks

works, thanks for all the continued support!

i change the rdpwrap.ini and the termsrv.dll, but still not working.

You shouldn't change the termsrv.dll!

works, thanks for all the continued support!

Reopened thi, because not added to official rdpwrap.ini

@sashaqwert, worked for me, thanks

10.0.22621.1778
3q


Add googleapis and grpc-java

These are in the same PR since they have a circular dependency on each other
Fixes: https://github.com/bazelbuild/bazel-central-registry/issues/353
Fixes: https://github.com/bazelbuild/bazel-central-registry/issues/1113

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (googleapis, grpc-java) have been updated in this PR. Please review the changes.

upstream prs are up:

https://github.com/grpc/grpc-java/pull/11046
https://github.com/googleapis/googleapis/pull/892

but thanks for reviewing, either way we need this one first because of the circular dependency


Tutorial 2: step 7 includes reference to a property called "Test2", will result in a failed built

Tutorial 2, step 7 code for render()

Customize SharePoint experiences using Web Parts.

${this.properties.description}

${this.properties.test2}

Loading from ${this.context.pageContext.web.title}

${this.properties.test2} is going to throw build errors:

Property 'test2' does not exist on type 'SPWeb'

Should this be removed from the example? Happy to submit a PR if the above makes sense.

Did you at test2 to the interface IHelloWorldWebPartProps.ts?

No, I didn't. I understand I could do this, but I thought I would raise it as it's not mentioned in the exercise. Would it make sense to add a note about this?

I think it does says that it's continuing from Tutorial 1 at the top.

Yeah, you're right. It looks like those changes including adding the property were made in a revision to Tutorial 1 yesterday. My issue is I did tutorial 1 yesterday, before that revision, so when I started tutorial 2 I was out of sync. Thanks.

No turns out I just can't read.


Upcoming API Changes

https://twitter.com/frazer_HX/status/816600136029786112

Post once per day.
Multiple images per post.
Use description text.
Link to https://flood-warning-information.service.gov.uk/5-day-flood-risk


Implement a basic optimization for pddl compilation at Profiler.

Implement a basic optimization for pddl compilation at Profiler.
See https://github.com/IBM/nl2flow/pull/59 for detail.
from nl2flow.compile.options import NL2FlowOptions

flow_object.optimization_options.remove(NL2FlowOptions.multi_instance)
flow_object.optimization_options.remove(NL2FlowOptions.allow_retries)

Example: example

completed #66


Following along

Hey man, hope you are doing well. I am attempting this project mashed up with the 3d printable pikon telescope.
I am currently having an issue running the Astrocam correctly.
I have moved the text files from the github on to my display and have set them to be executable by anyone.
when i click on the shortcuts it shows a loading icon but never pops up on to screen.
through ssh terminal im getting this error
pi@raspberrypi:~/AstroCameraApp/PythonScripts $ python3 AstroCam.py
Traceback (most recent call last):
File "AstroCam.py", line 12, in
from PIL import ImageTk, Image
ImportError: cannot import name 'ImageTk' from 'PIL' (/usr/lib/python3/dist-pack                                                                                ages/PIL/init.py)
kstars is working and running on my touchscreen display along with the shortcut for the camera preview, im using a 2.8" tft resistive touch screen from adafruit and it measures 320x240 and was trying to figure out how to edit that in the settings as mentioned in your pdf but am having issues there as well. Im not sure if the screen size difference is the issue with it not loading up or not! Im not to experienced in python but am a slightly capable with rpi's.
hope to hear from you soon!

if i try to run it with python it gives this error
~/AstroCameraApp/PythonScripts $ python AstroCam.py
Traceback (most recent call last):
File "AstroCam.py", line 10, in
import tkinter as Tkinter
ImportError: No module named tkinter

pi@raspberrypi:~ $ sudo apt-get install python-tk
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-tk is already the newest version (2.7.16-2).
0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded.
pi@raspberrypi:~ $ sudo apt-get install python3-tk
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-tk is already the newest version (3.7.3-1).
0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded.

Hi sirfressh :)
It looks like the issue lies in your Tkinter installation, although from your last comment it looks like you already have it installed, which is.. a little odd then. What Python version are you using it with? Make sure you have Tkinter installed for Python 3 (I think you needed to use the pip3 package manager to install Python 3 packages specifically) and in case that doesn't work, try checking the name your installation uses for the Tkinter package and swap that with "tkinter" at the "import tkinter as Tkinter" line.
Regarding the screen size, fortunately I can assure you that once the Tkinter package issue is resolved, there you should be no code-breaking bug occurring due to the window sizes (aside from them not fitting on your lower res and smaller screen at least).
You can change the individual window sizes by modifying the .geometry lines below (lines 139-151 in the code) within your AstroCam.py file. Tkinter uses a format of ("width x height + displacement of the window to the right + displacement of the window horizontally") in pixels for defining the window geometry, meaning that you will for example want to set the height to the same as your screens vertical resolution (240) and split up the horizontal resolution of (320) between the tkTop and previewWin width values. You can then move their starting positions on the touchscreen by modifying the displacement values, although here I simply recommend to set the right displacement value for the tkTop window to the same value as your previewWin chosen width.
tkTop = Tkinter.Tk()
tkTop.wm_title("Settings")
tkTop.geometry("130x300+350+0")                  #Main Settings Window Size
previewWin = Tkinter.Toplevel(tkTop)
previewWin.title('AstroCam')
previewWin.geometry('350x300+1+0')              #Preview Window Size
previewPanel = Tkinter.Label(previewWin)
previewPanel.pack(side = "bottom", fill = "both", expand = "yes")
tkBottom = Tkinter.Toplevel(tkTop)
tkBottom.wm_title("Advanced Settings")
tkBottom.geometry("610x300+0+330")            #Advanced Window Size (not as important, as this one is only intended for remote desktop usage, but you can modify it to fit the other two once you are done with the resizing so as to make it look better)
You also might need to tinker a bit with the
SCALE_WIDTH = 130;
SCALE_LENGHT = 250
values on lines 165-166 to get all of the relevant settings and functions to fit on the smaller screen of your Raspberry Pi, as they don't automatically scale to fit within the window sizes. Also, make sure to set all the "camera.resolution = (350, 300)" lines to the (width x height) size of your previewWin.
Unfortunately, this was my first project using Tkinter and thus I didn't implement any proportion based scaling to make the app easily compatible across multiple screen sizes, which is why this is such a pain to set up. As I am still a newbie at making GUIs and originally intended the AstroCam script for only my personal use with my specific setup before deciding to publish it here due to the huge amount of positive feedback it received, this didn't seem like an urgent issue at first but... I will try to look into it now during the next few weeks as I try to make further improvements to the code, so feel free to keep an eye out for further updates too.
I hope this answer can be of help to you. Should any further issues come up, do not hesitate to write back too, as the more issues are found, the further I can improve my project for other people to have a smoother experience when trying to reproduce it like you are, and thus the more helpful it can be to others :)
With kind regards, Santiago

Thanks for the quick response! I will try to install tkinter through pip3
and see if that works and then work on the screen adjustments. I appreciate
your help! If you could possible link me the screen you're using and where
I can buy one possible that would be great as well! I'd enjoy a bigger
screen myself!!
On Tue, Jul 7, 2020, 3:35 PM Santi<EMAIL_ADDRESS>wrote:

Hi sirfressh :)
It looks like the issue lies in your Tkinter installation, although from
your last comment it looks like you already have it installed, which is.. a
little odd then. What Python version are you using it with? Make sure you
have Tkinter installed for Python 3 (I think you needed to use the pip3
package manager to install Python 3 packages specifically) and in case that
doesn't work, try checking the name your installation uses for the Tkinter
package and swap that with "tkinter" at the "import tkinter as Tkinter"
line.
Regarding the screen size, fortunately I can assure you that once the
Tkinter package issue is resolved, there you should be no code-breaking bug
occurring due to the window sizes (aside from them not fitting on your
lower res and smaller screen at least).
You can change the individual window sizes by modifying the .geometry
lines below (lines 139-151 in the code) within your AstroCam.py file.
Tkinter uses a format of ("width x height + displacement of the window to
the right + displacement of the window horizontally") in pixels for
defining the window geometry, meaning that you will for example want to set
the height to the same as your screens vertical resolution (240) and split
up the horizontal resolution of (320) between the tkTop and previewWin
width values. You can then move their starting positions on the touchscreen
by modifying the displacement values, although here I simply recommend to
set the right displacement value for the tkTop window to the same value as
your previewWin chosen width.
tkTop = Tkinter.Tk()
tkTop.wm_title("Settings")
tkTop.geometry("130x300+350+0") #Main Settings Window Size
previewWin = Tkinter.Toplevel(tkTop)
previewWin.title('AstroCam')
previewWin.geometry('350x300+1+0') #Preview Window Size
previewPanel = Tkinter.Label(previewWin)
previewPanel.pack(side = "bottom", fill = "both", expand = "yes")
tkBottom = Tkinter.Toplevel(tkTop)
tkBottom.wm_title("Advanced Settings")
tkBottom.geometry("610x300+0+330") #Advanced Window Size (not as
important, as this one is only intended for remote desktop usage, but you
can modify it to fit the other two once you are done with the resizing so
as to make it look better)
You also might need to tinker a bit with the
SCALE_WIDTH = 130;
SCALE_LENGHT = 250
values on lines 165-166 to get all of the relevant settings and functions
to fit on the smaller screen of your Raspberry Pi, as they don't
automatically scale to fit within the window sizes. Also, make sure to set
all the "camera.resolution = (350, 300)" lines to the (width x height) size
of your previewWin.
Unfortunately, this was my first project using Tkinter and thus I didn't
implement any proportion based scaling to make the app easily compatible
across multiple screen sizes, which is why this is such a pain to set up.
As I am still a newbie at making GUIs and originally intended the AstroCam
script for only my personal use with my specific setup before deciding to
publish it here due to the huge amount of positive feedback it received,
this didn't seem like an urgent issue at first but... I will try to look
into it now during the next few weeks as I try to make further improvements
to the code, so feel free to keep an eye out for further updates too.
I hope this answer can be of help to you. Should any further issues come
up, do not hesitate to write back too, as the more issues are found, the
further I can improve my project for other people to have a smoother
experience when trying to reproduce it like you are, and thus the more
helpful it can be to others :)
With kind regards, Santiago
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RemovedMoney326/Hubble-Pi/issues/2#issuecomment-655117416,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3MEF2OHXJOZ7W2GF2WOJDR2OBJVANCNFSM4OTGZRMQ
.

NVM I just noticed you linked the screen in your pdf!!!! Thanks again for
your help!
On Tue, Jul 7, 2020, 3:51 PM Matthew Gaither<EMAIL_ADDRESS>wrote:

Thanks for the quick response! I will try to install tkinter through pip3
and see if that works and then work on the screen adjustments. I appreciate
your help! If you could possible link me the screen you're using and where
I can buy one possible that would be great as well! I'd enjoy a bigger
screen myself!!
On Tue, Jul 7, 2020, 3:35 PM Santi<EMAIL_ADDRESS>wrote:

Hi sirfressh :)
It looks like the issue lies in your Tkinter installation, although from
your last comment it looks like you already have it installed, which is.. a
little odd then. What Python version are you using it with? Make sure you
have Tkinter installed for Python 3 (I think you needed to use the pip3
package manager to install Python 3 packages specifically) and in case that
doesn't work, try checking the name your installation uses for the Tkinter
package and swap that with "tkinter" at the "import tkinter as Tkinter"
line.
Regarding the screen size, fortunately I can assure you that once the
Tkinter package issue is resolved, there you should be no code-breaking bug
occurring due to the window sizes (aside from them not fitting on your
lower res and smaller screen at least).
You can change the individual window sizes by modifying the .geometry
lines below (lines 139-151 in the code) within your AstroCam.py file.
Tkinter uses a format of ("width x height + displacement of the window to
the right + displacement of the window horizontally") in pixels for
defining the window geometry, meaning that you will for example want to set
the height to the same as your screens vertical resolution (240) and split
up the horizontal resolution of (320) between the tkTop and previewWin
width values. You can then move their starting positions on the touchscreen
by modifying the displacement values, although here I simply recommend to
set the right displacement value for the tkTop window to the same value as
your previewWin chosen width.
tkTop = Tkinter.Tk()
tkTop.wm_title("Settings")
tkTop.geometry("130x300+350+0") #Main Settings Window Size
previewWin = Tkinter.Toplevel(tkTop)
previewWin.title('AstroCam')
previewWin.geometry('350x300+1+0') #Preview Window Size
previewPanel = Tkinter.Label(previewWin)
previewPanel.pack(side = "bottom", fill = "both", expand = "yes")
tkBottom = Tkinter.Toplevel(tkTop)
tkBottom.wm_title("Advanced Settings")
tkBottom.geometry("610x300+0+330") #Advanced Window Size (not as
important, as this one is only intended for remote desktop usage, but you
can modify it to fit the other two once you are done with the resizing so
as to make it look better)
You also might need to tinker a bit with the
SCALE_WIDTH = 130;
SCALE_LENGHT = 250
values on lines 165-166 to get all of the relevant settings and functions
to fit on the smaller screen of your Raspberry Pi, as they don't
automatically scale to fit within the window sizes. Also, make sure to set
all the "camera.resolution = (350, 300)" lines to the (width x height) size
of your previewWin.
Unfortunately, this was my first project using Tkinter and thus I didn't
implement any proportion based scaling to make the app easily compatible
across multiple screen sizes, which is why this is such a pain to set up.
As I am still a newbie at making GUIs and originally intended the AstroCam
script for only my personal use with my specific setup before deciding to
publish it here due to the huge amount of positive feedback it received,
this didn't seem like an urgent issue at first but... I will try to look
into it now during the next few weeks as I try to make further improvements
to the code, so feel free to keep an eye out for further updates too.
I hope this answer can be of help to you. Should any further issues come
up, do not hesitate to write back too, as the more issues are found, the
further I can improve my project for other people to have a smoother
experience when trying to reproduce it like you are, and thus the more
helpful it can be to others :)
With kind regards, Santiago
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RemovedMoney326/Hubble-Pi/issues/2#issuecomment-655117416,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3MEF2OHXJOZ7W2GF2WOJDR2OBJVANCNFSM4OTGZRMQ
.

No problem! If possible, do let me know if it works once you install the Tkinter package so I can then close the issue, otherwise you can also post any further issues you might have here and I will try to help out as best I can.

hey so i went ahead and ordered the same screen that you had just so i wouldnt have to worry about adjusting anything in the python script. I was able to figure out what the issue was with it not wanting to load up. It was unable to import tkinter from PIL so i was able to update and install the packages with this command.
sudo apt-get install python3-pil python3-pil.imagetk
it installed the python3-pil.imagetk which i guess was the problem.
after it installed i opened python and imported PIL and tkinter again.
rebooted and now it comes up as it should and shows video feed.


docs: Mismatched quotation mark

This PR fixes a syntax error in one of the "Using a JSON array" example code snippets.

Thanks