Segmentation fault when training

python run_rnnt.py --mode train --data_dir data_p --batch_size 4 --steps_per_checkpoint 100 --eval_size 100

Output
/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/librosa/util/decorators.py:9: NumbaDeprecationWarning: An import was requested from a module that has moved location.
Import of 'jit' requested from: 'numba.decorators', please update to use 'numba.core.decorators' or pin to Numba version 0.48.0. This alias will not be present in Numba version 0.50.0.
  from numba.decorators import jit as optional_jit
2020-05-15 18:23:30.552682: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-05-15 18:23:30.554999: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-05-15 18:23:30.557774: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.558037: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:2d:00.0 name: GeForce RTX 2080 SUPER computeCapability: 7.5
coreClock: 1.845GHz coreCount: 48 deviceMemorySize: 7.79GiB deviceMemoryBandwidth: 462.00GiB/s
2020-05-15 18:23:30.558055: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-05-15 18:23:30.559051: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-05-15 18:23:30.560261: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-05-15 18:23:30.560434: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-05-15 18:23:30.561637: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-05-15 18:23:30.562292: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-05-15 18:23:30.564700: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-05-15 18:23:30.564832: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.565168: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.565402: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-05-15 18:23:30.565750: I tensorflow/core/platform/cpu_feature_guard.cc:143] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-05-15 18:23:30.575283: I tensorflow/core/platform/profile_utils/cpu_utils.cc:102] CPU Frequency:<PHONE_NUMBER> Hz
2020-05-15 18:23:30.576470: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7efa80000b20 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-05-15 18:23:30.576495: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-05-15 18:23:30.689371: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.689981: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x6814db0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-05-15 18:23:30.690025: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce RTX 2080 SUPER, Compute Capability 7.5
2020-05-15 18:23:30.690407: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.691010: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:2d:00.0 name: GeForce RTX 2080 SUPER computeCapability: 7.5
coreClock: 1.845GHz coreCount: 48 deviceMemorySize: 7.79GiB deviceMemoryBandwidth: 462.00GiB/s
2020-05-15 18:23:30.691075: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-05-15 18:23:30.691095: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-05-15 18:23:30.691112: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-05-15 18:23:30.691129: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-05-15 18:23:30.691146: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-05-15 18:23:30.691163: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-05-15 18:23:30.691180: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-05-15 18:23:30.691270: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.692583: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.692980: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-05-15 18:23:30.701118: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-05-15 18:23:30.701129: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1108]      0
2020-05-15 18:23:30.701134: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] 0:   N
2020-05-15 18:23:30.701322: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.701874: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-15 18:23:30.702169: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1247] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 3473 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2080 SUPER, pci bus id: 0000:2d:00.0, compute capability: 7.5)
1 Physical GPU, 1 Logical GPUs
Running single gpu: GPU:0
WARNING:tensorflow:From /home/carson/Documents/code/other/rnnt-speech-recognition/model.py:60: LSTMCell.__init__ (from tensorflow.python.ops.rnn_cell_impl) is deprecated and will be removed in a future version.
Instructions for updating:
This class is equivalent as tf.keras.layers.LSTMCell, and will be replaced by that in Tensorflow 2.0.
W0515 18:23:31.132123<PHONE_NUMBER>64992 deprecation.py:323] From /home/carson/Documents/code/other/rnnt-speech-recognition/model.py:60: LSTMCell.__init__ (from tensorflow.python.ops.rnn_cell_impl) is deprecated and will be removed in a future version.
Instructions for updating:
This class is equivalent as tf.keras.layers.LSTMCell, and will be replaced by that in Tensorflow 2.0.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb52af8208>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.132437<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb52af8208>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:From /home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/ops/rnn_cell_impl.py:966: Layer.add_variable (from tensorflow.python.keras.engine.base_layer) is deprecated and will be removed in a future version.
Instructions for updating:
Please use `layer.add_weight` method instead.
W0515 18:23:31.134259<PHONE_NUMBER>64992 deprecation.py:323] From /home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/ops/rnn_cell_impl.py:966: Layer.add_variable (from tensorflow.python.keras.engine.base_layer) is deprecated and will be removed in a future version.
Instructions for updating:
Please use `layer.add_weight` method instead.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4063e5f8>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.215806<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4063e5f8>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4061a8d0>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.376376<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4061a8d0>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb405a1550>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.436952<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb405a1550>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4050e208>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.493255<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4050e208>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4047ee48>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.548519<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4047ee48>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb40465a58>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.604781<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb40465a58>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb405b06a0>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:31.748168<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb405b06a0>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4003e7b8>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:32.258143<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efb4003e7b8>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
WARNING:tensorflow:<tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efaf40e5b00>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
W0515 18:23:32.318936<PHONE_NUMBER>64992 rnn_cell_impl.py:912] <tensorflow.python.ops.rnn_cell_impl.LSTMCell object at 0x7efaf40e5b00>: Note that this cell is not optimized for performance. Please use tf.contrib.cudnn_rnn.CudnnLSTM for better performance on GPU.
I0515 18:23:32.513643<PHONE_NUMBER>64992 run_rnnt.py:491] Using word-piece encoder with vocab size: 4088
Model: "encoder"
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
input_1 (InputLayer)         [(None, None, 240)]       0
_________________________________________________________________
batch_normalization (BatchNo (None, None, 240)         960
_________________________________________________________________
rnn (RNN)                    (None, None,<PHONE_NUMBER>
_________________________________________________________________
dropout (Dropout)            (None, None, 640)         0
_________________________________________________________________
layer_normalization (LayerNo (None, None, 640)         1280
_________________________________________________________________
rnn_1 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_1 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_1 (Layer (None, None, 640)         1280
_________________________________________________________________
time_reduction (TimeReductio (None, None, 1280)        0
_________________________________________________________________
rnn_2 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_2 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_2 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_3 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_3 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_3 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_4 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_4 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_4 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_5 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_5 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_5 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_6 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_6 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_6 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_7 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_7 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_7 (Layer (None, None, 640)         1280
=================================================================
Total params: 96,414,656
Trainable params: 96,414,176
Non-trainable params: 480
_________________________________________________________________
Model: "prediction_network"
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
input_2 (InputLayer)         [(None, None)]            0
_________________________________________________________________
embedding (Embedding)        (None, None,<PHONE_NUMBER>
_________________________________________________________________
rnn_8 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_8 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_8 (Layer (None, None, 640)         1280
_________________________________________________________________
rnn_9 (RNN)                  (None, None,<PHONE_NUMBER>2
_________________________________________________________________
dropout_9 (Dropout)          (None, None, 640)         0
_________________________________________________________________
layer_normalization_9 (Layer (None, None, 640)         1280
=================================================================
Total params: 24,509,024
Trainable params: 24,509,024
Non-trainable params: 0
_________________________________________________________________
Model: "transducer"
__________________________________________________________________________________________________
Layer (type)                    Output Shape         Param #     Connected to
==================================================================================================
mel_specs (InputLayer)          [(None, None, 240)]  0
__________________________________________________________________________________________________
pred_inp (InputLayer)           [(None, None)]       0
__________________________________________________________________________________________________
encoder (Model)                 (None, None,<PHONE_NUMBER>6    mel_specs[0][0]
__________________________________________________________________________________________________
prediction_network (Model)      (None, None,<PHONE_NUMBER>4    pred_inp[0][0]
__________________________________________________________________________________________________
tf_op_layer_ExpandDims (TensorF [(None, None, 1, 640 0           encoder[1][0]
__________________________________________________________________________________________________
tf_op_layer_ExpandDims_1 (Tenso [(None, 1, None, 640 0           prediction_network[1][0]
__________________________________________________________________________________________________
tf_op_layer_AddV2 (TensorFlowOp [(None, None, None,  0           tf_op_layer_ExpandDims[0][0]
                                                                 tf_op_layer_ExpandDims_1[0][0]
__________________________________________________________________________________________________
dense (Dense)                   (None, None, None, 6 410240      tf_op_layer_AddV2[0][0]
__________________________________________________________________________________________________
dense_1 (Dense)                 (None, None, None, 4 2620408     dense[0][0]
==================================================================================================
Total params: 123,954,328
Trainable params: 123,953,848
Non-trainable params: 480
__________________________________________________________________________________________________
Starting training.
Performing evaluation.
2020-05-15 18:23:36.665552: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
Fatal Python error: Segmentation fault

Current thread 0x00007efbff6c1740 (most recent call first):
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/execute.py", line 60 in quick_execute
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 598 in call
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1746 in _call_flat
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1665 in _filtered_call
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 650 in _call
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 580 in __call__
  File "run_rnnt.py", line 433 in run_evaluate
  File "run_rnnt.py", line 312 in checkpoint_model
  File "run_rnnt.py", line 347 in run_training
  File "run_rnnt.py", line 546 in main
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/absl/app.py", line 250 in _run_main
  File "/home/carson/Documents/code/other/rnnt-speech-recognition/.env/lib/python3.6/site-packages/absl/app.py", line 299 in run
  File "run_rnnt.py", line 587 in <module>
[1]    14991 segmentation fault (core dumped)  python run_rnnt.py --mode train --data_dir data_p --batch_size 4  100  100

@dyc3 What version of TensorFlow are you using? You should be using 2.2.0, I have a small model training right now and it works fine. Also make sure that you install TensorFlow 2.2.0 before you run the build_rnnt.sh script.

I had forgotten to recompile warp-transducer after installing the new version of tensorflow


Errors when numeric and alphabetic data is mixed

I am using the API to read data from an image.  I have created training files for the fonts I process and I pre-process the image to deskew and clean it.
When I read entirely numeric data it reads perfectly e.g. 123456.
When I read entirely alphabetic data it reads perfectly e.g. ABCDEFGH.
The problem arises when I try to read text where the two are combined e.f. 12ABC3456.  In this case, there are lots of errors (B and 8 mixed up for example).

I have tried setting load_system_dawg and load_freq_dawg to be false but that did not help.  Are there any other configuration changes I can make to help?


Not a bug.

Hey, I didn't know how else to contact you.
I'm the guy that made Augmentum, I just wanted to say you made a cool mod!

thanks (im on a lot of discords @ pr_d if that helps)


Fix dependency issues

omero-py requires zeroc-ice 3.6.5
OME maintains wheels for our required python versions, they are used in lavlab-omeropy-container, the base image for this dev container. however when running hatch, our build tool, it doesn't use our existing venv. Instead it attempts to build it's own venv, which errors as the zeroc-ice maintainers do not provide wheels past python3.8
not sure how to resolve atm.

resolved in a5f6834
using hatch remote direct references


human_img_edit_gradio.ipynb run error

cf = import_filename(args.cf)
Net, inner_collect_fn = cf.Net, cf.inner_collect_fn
cf is config/ref_attn_clip_combine_controlnet/app_demo_image_edit.py, and app_demo_image_edit.py does not have Net and inner_collect_fn

resolved


High Ram Usage

This mod seems to cause high ram usage of Lethal Company.
just by activating this mod without adding any suits Lethal's ram usage goes up by about 2-3 gb.
with over 100 suits added the highest Ram usage i observed in Lethal was 11gb just because of suits.

I don't believe there's any simple solution other than compressing them and only using the suits you plan on using.


[UNDERTOW-2518] At WebSocketTimeoutTestCase, use a longer watch timeout

Jira:
https://issues.redhat.com/browse/UNDERTOW-2518

Testing if increasing the watch timeout makes the error goes away


Add new "Cancelled" task status when PR is closed.

Cute animal pic
Because everyone likes pictures of animals.

Link to Trello card (if applicable)
If this PR relates to a Trello card, don't forget to reference this PR on the card as well.

https://trello.com/c/GvA1Lw5V

Description
The commit messages say what you did; this should explain why and/or how.

[x] Description is in Trello card

Steps to test/reproduce
Please explain how to best reproduce the issue and/or test the changes locally (including the pages/URLs/views/states to review).
In local dev, this takes a few steps to test:

You need a Task with an open PR (you could probably fake this by manually setting pr_is_open and pr_number via the admin).
Setup GitHub webhooks
Close the PR on GitHub
Profit!

Show me
Provide screenshots/animated gifs/videos if necessary.

 As a user, I want to see the status of a Task update to Closed if it is connected to a PR that gets closed in github, so that it doesn't appear to still be in progress when it's not.

@jerivas @jgerigmeyer
The instructions in this PR say:
2. Setup Github webhooks

with a link to the contributing guide that says you need to use ngrok. I don't know if that is something I should be installing first or if it installs with a build or something. I read through some of the docs at https://ngrok.com/docs/ngrok-link#service which really only made things less clear.  I did try to go on and ran the command in the https://github.com/oddbird/Metecho/blob/main/CONTRIBUTING.rst#github-webhooks-in-development section and got an error.
So I continued on with that section which says if you are an OddBird, you can access the app here with a broken link. I did poke around GitHub and found settings/apps/authorizations and in the Authorized GitHub Apps tab, I see one is called Metecho ( local dev). I don't know if that is even close to what I am looking for here.
If anyone could offer some insight or expand on the instructions, I would be grateful. TIA.

@stacyk when we work on a project locally the app is running in your computer and is accessible only to your local network. In other words you can't share a URL to your local version of Metecho because it runs on localhost. This is a problem for GitHub webhooks because they expect a publicly-accessible URL to query (not localhost). ngrok allows your local version of Metecho (or any other project) to be accessed globally by creating a public subdomain and "tunneling" the traffic from that URL to your localhost.
You will need to install ngrok separately, it won't be available as part of the project. Once you install it you should be able to create a tunnel using the instructions in the contributing guide, specifically ngrok http --host-header=localhost:8080 8080. This tells the ngrok command to start an http tunnel to your localhost on port 8080 (the one that webpack uses). In return ngrok will display a URL (assigned randomly) that you can use to access your tunneled project (something like abc123.ngrok.io). At this point you can visit that URL in your browser and you should see the traffic in your console as if you're coming from localhost:8080.
Once you confirm that is working you will need to edit the webhook configuration of Metecho Local Dev on GitHub to point to your newly assigned ngrok subdomain. Unfortunately the subdomain changes every time you start ngrok, so the app's configuration on GitHub needs to be updated every time and can only be used by one developer at a time. Here's where we'll need @jgerigmeyer's help because it looks like Stacy and I don't have permissions to edit the app settings on GitHub.
Finally once that's sorted out Metecho Local Dev will ping your ngrok subdomain when an issue is closed, ngrok will tunnel that request to your localhost, and that will let you test out this feature. Phew!

If anyone could offer some insight or expand on the instructions, I would be grateful. TIA.

@stacyk Yep! What @jerivas said. Sorry for not providing more detailed instructions.

Download ngrok from https://ngrok.com/download
Put it somewhere (e.g. I have mine saved as ~/Sites/ngrok)
Start your local Metecho server normally
Run the ngrok command from the docs, using the path to wherever you saved it (e.g. for me it's ~/Sites/ngrok http --host-header=localhost:8080 8080)
Go to https://github.com/organizations/oddbird/settings/apps/metecho-local-dev (I gave you both permissions), to the "Webhook URL" field under the "Webhook" section, and edit it using the hash from your local ngrok terminal (e.g. https://0953432f344d.ngrok.io/api/hook/), then "Save changes"

Then when you close or reopen a PR on GitHub, Metecho should update live (and you should see an "Accepted" line or something in your ngrok terminal).
Alternatively, it might be much simpler to just "fake" the incoming webhook locally. To do that, on a given Task with an open PR you can edit it via the Django admin to set the following items:

status: Canceled
pr_is_open: False
review_valid: False

That does essentially the same thing, and will give you a Canceled task locally.


[SPARK-7760] add /json back into master & worker pages; add test

Merged build triggered.

Merged build started.

Test build #33147 has started for   PR 6284 at commit 29df42b.

Test build #33147 has finished for   PR 6284 at commit 29df42b.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

LGTM aside from a couple of minor things. Seems like there are some scalastyle issues though.

Merged build triggered.

Merged build started.

Test build #33155 has started for   PR 6284 at commit fb32412.

Test build #33155 has finished for   PR 6284 at commit fb32412.

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

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #33164 has started for   PR 6284 at commit f32948d.

So actually the last commit https://github.com/squito/spark/commit/f32948d5407033519d2ed140d8a585f538c0a1ea will be unnecessary once https://github.com/apache/spark/pull/6273 is merged.  I will undo it once that is merged, and then this will be ready for merging I think

Test build #33164 has finished for   PR 6284 at commit f32948d.

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

Merged build finished. Test PASSed.

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

Merged build triggered.

Merged build started.

#6273 has been merged, and I updated this to reflect that, so I think this is now ready to go (assuming tests pass)

Test build #33206 has started for   PR 6284 at commit 5e02d8a.

Test build #33206 has finished for   PR 6284 at commit 5e02d8a.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build triggered.

Merged build started.

Test build #33251 has started for   PR 6284 at commit 5e02d8a.

Test build #33251 has finished for   PR 6284 at commit 5e02d8a.

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

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

Merged build finished. Test PASSed.

This looks good to me. The original JsonProtocolSuite tests for the actual contents of the responses weren't touched by the REST API patch, so I think that this test of the endpoints themselves should be sufficient to keep this from breaking in the future.  I'm going to merge this into master and branch-1.4.


[2.4] Update oke kontainer engine driver v1.7.0

This PR is a 2.4 back-port of this PR:update oke kontainer engine driver v1.7.0

@jrosinsk The UI updates will need to be back-ported as well.


SQL

@ACharbonneau mention at July 07th debriefing session that the SQLite provided by Anaconda have some problem and one workaround is changing the PATH so that the "native" SQLite is used. @mckays630 confirmed the problem.

Just to make sure we understand:

Anaconda distributes a version of sqlite3 and so does our Windows installer
Students install Anaconda to be the default Python, which puts the anaconda/bin directory at the beginning of the PATH
There is something not quite right about the Anaconda version of sqlite3 (this should get reported to them)
We should change the PATH in such a way as to load the version that we are distributing

Mostly accurate. The only changes are:
It's not just a Windows problem. I only installed Anaconda the day of the
workshop so I could follow along with the other instructor, and then found
that it broke my Macs native sqlite3. Installing Anaconda as per the
current instructions just makes it the default sqlite3. We ended up having
to fix the PATH of everyone in the class that had recently installed
Anaconda, regardless of OS.
Its already an issue on the Anaconda Github repo
https://github.com/ContinuumIO/anaconda-issues/issues/307. The only way I
figured out the problem was the magic of Google :)

We should change the PATH in such a way as to load the native sqlite3 or
the version we are distributing

-Amanda
On Wed, Jul 8, 2015 at 1:41 PM Ethan White<EMAIL_ADDRESS>wrote:

Just to make sure we understand:

Anaconda distributes a version of sqlite3 and so does our Windows
installer
Students install Anaconda to be the default Python, which puts the
anaconda/bin directory at the beginning of the PATH
There is something not quite right about the Anaconda version of
sqlite3 (this should get reported to them)
We should change the PATH in such a way as to load the version that
we are distributing

—
Reply to this email directly or view it on GitHub
https://github.com/swcarpentry/windows-installer/issues/30#issuecomment-119673725
.

On Wed, Jul 08, 2015 at 02:28:08PM -0700, Amanda Charbonneau wrote:

It's not just a Windows problem. I only installed Anaconda the day
of the workshop so I could follow along with the other instructor,
and then found that it broke my Macs native sqlite3.

It's hard to fix this just by changing the PATH.  We can shift the
Anaconda-specific component to the end of the PATH in the
.bash_profile we install on Windows, but that puts folks at risk of
not clobbering a system ‘conda’.  The real solution is addressing
ContinuumIO/anaconda-issues#372 (and that would help folks on
non-Windows OSes too).
In any event, I think readline for SQLite is a small enough problem
that it's not worth creating OS X or Linux SWC installers.  Is there
enough other material that such installers would be useful?  Or is
this something that's better addressed by a note in the OS X / Linux
setup instructions?

Thanks for the clarification @ACharbonneau. Since this is a multi-OS issue I agree with @wking that we're probably better off seeing if https://github.com/ContinuumIO/anaconda-issues/issues/372 or something equivalent goes through than trying to patch this right away on just one OS. Trying to fix this in the Windows Installer would probably also introduce some order of installation dependencies which wouldn't be ideal.

@wking and @ethanwhite What about https://github.com/swcarpentry/workshop-template/pull/230 until https://github.com/ContinuumIO/anaconda-issues/issues/307 isn't fixed?

It's better than nothing for the moment.
Fixing path issues across 3 operating systems for lots of students is never much fun. But, to fix the bigger problem we do need a cross-OS solution and if there are any Windows related hiccups with that solution then we can clean those up in the Windows Installer.

@ethanwhite @wking Can we close this?

@rgaiacs - I'm no longer maintaining the Windows Installer, so that's up to @wking and @embray now.


In Emulator it works, not via ionic view

Hi,
Emulator it's all working, not when I open it on a real iPhone. Looks like an error somewhere, because the {{ }}-tags are also visible like that instead of rendered. But I don't know how to debug that. On bottom of config.xml it has <plugin name="de.appplant.cordova.plugin.printer" spec="https://github.com/katzer/cordova-plugin-printer.git"/>

Hi,
I have the same problem. Everything's fine with the emulaor and nothing with my phone


Graph position and fit to view

Hi there :),
Doing some research from the past week on this package. Is there any feature available for the Graph to fit view. Even it should support drag and drop also.
Please refer below image

Is there any way to achieve this?

Hi @onlyreddy

Is there any feature available for the Graph to fit view.

Could you elaborate a bit on what "fit view" means for you? Do you intend to have the graph bounded to the view box? Would this be what you're looking for?

Fit view means suppose if user expanded 100 nodes and some of them may move out of the viewport. But somehow I need to fit them inside my viewport. So that user can see all nodes.
I saw the PR was approved but is it included in the latest release?

There is a dirty way to do this by modified the translation of graph  elements. After that we need to update initialZoom as 1.
 document
      .getElementById('info-map-graph-container-zoomable')
      .setAttribute('transform', `translate(0,0), scale(1)`);

    setConfiguration({
      ...configuration,
      initialZoom: 1,
    });

Above one is working for me.

@onlyreddy I've found a way to center and fit the graph based on the size/scale.

export const Graph = () => {
  const graphRef = React.useRef<any>();

  const centerGraph = () => {
    ...
    const wrapper = d3.select(`#${graphRef.current.state.id}-graph-wrapper`);

    const zoom = d3
      .zoom()
      .scaleExtent([
        graphRef.current.state.config.minZoom,
        graphRef.current.state.config.maxZoom,
      ]);

    const svg = d3.select(`svg`);
    const g = d3.select(
      `#${graphRef.current.state.id}-graph-container-zoomable`
    );

    zoom.on('zoom', () => {
      g.attr('transform', d3.event.transform);
    });
    wrapper.call(zoom).on('dblclick.zoom', null);

    const bbox = g.node().getBBox();
    const width = graphRef.current.state.config.width;
    const height = graphRef.current.state.config.height;

    const scale = Math.min(width / bbox.width, height / bbox.height);
    const translateX = (width - bbox.width * scale) / 2 - bbox.x * scale;
    const translateY = (height - bbox.height * scale) / 2 - bbox.y * scale;

    const transform = d3.zoomIdentity
      .translate(translateX, translateY)
      .scale(scale);

    svg.on('.zoom', null);
    svg.transition().duration(750).call(zoom.transform, transform);
    svg.call(zoom);
  };

  React.useEffect(() => {
    graphRef.current &&
      setTimeout(() => {
        centerGraph();
      }, 2000);
  }, [graphRef]);

  return (
    <D3Graph
      id="graph-id"
      data={data}
      config={config}
      ref={graphRef}
    />
  );
}

export default Graph;

The centerGraph could be also used in a button, it's working for me.


null response on getMessage()

Using FirstData_Webservice, getting a null response on the transaction send.
        $card = Omnipay::creditCard($cardInput);

        $response = Omnipay::purchase([
            'amount'        => '100.00',
            'transactionId' => '100.00',
            'accountId'     => '100.00',
            'card'          => $cardInput
        ])->send();

        dd($response->getMessage());

I noticed the gateways are updated to TLS 1.2 only, perhaps this is the cause?
https://www.firstdata.com/ecommerce/index.html

TLS1.2 Update: In order to adhere to the PCI mandate, the Gateways will update systems to support the TLS1.2 protocol only in January 2018. Please contact your sales representative for more information and steps required to ensure compliance.

The TLS 1.2 thing is almost certainly the issue. Can you check that your system is doing a TLS 1.2 connect? Depending on the version of OpenSSL or equivalent that you have, it may be necessary to set the TLS version explicitly.

I've been in contact with Firstdata about their API access, it appears some of the endpoints have been shutoff too. Even forcing TLS 1.2 in curl, etc - this would not connect using 'FirstData_Webservice'
Ended up writing my own with Guzzle using the only endpoint I could find that is still active, though according to them this will be sunset soon too.
Using version 1.1 of their API
$response = $client->request('POST', 'https://secure.linkpt.net:1129/LSGSXML', [
    'cert'   => 'key.pem',
    'verify' => false,
    'body'   => $xml_data
]);


"\widehat, \widetilde, \fbox, \sideset" can't convert

like "\widehat{7+x}, \fbox{E=mc^2},  \sideset{^1_2}{^3_4}\bigotimes" are not correctly converted.

Renamed title because \boxed is supported in 3.16.0 (https://github.com/roniemartinez/latex2mathml/pull/157)

@all-contributors please add @yuwenjun1 for bug


Charts using invalid rabbitmq credentials by default

Is this a bug report or feature request? (choose one):
Bug report
Kubernetes Version (output of kubectl version):
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"08e099554f3c31f6e6f07b448ab3ed78d0520507", GitTreeState:"clean", BuildDate:"2017-01-12T04:57:25Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:52:01Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Helm Client and Tiller Versions (output of helm version):
Client: &version.Version{SemVer:"v2.1.3", GitCommit:"5cbc48fb305ca4bf68c26eb8d2a7eb363227e973", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.1.3", GitCommit:"5cbc48fb305ca4bf68c26eb8d2a7eb363227e973", GitTreeState:"clean"}
Development or Deployment Environment?:
Single node bare metal dev
Release Tag or Master:
Master
Expected Behavior:
OpenStack services can communicate with rabbitmq
What Actually Happened:
A number of services fail to connect to rabbitmq, with the error:
AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.
How to Reproduce the Issue (as minimally as possible):
Do a fresh install from master, per the install guide.
Any Additional Comments:
Several pods get the error above:
neutron-dhcp-agent
neutron-l3-agent
cinder-scheduler
nova-compute
nova-consoleauth
nova-scheduler
These services are configured by default like so:
rabbitmq:
address: rabbitmq
admin_user: rabbitmq
admin_password: password
Rabbitmq reports the corresponding error:
AMQPLAIN login refused: user 'rabbitmq' - invalid credentials
Rabbitmq's values has:
auth:
default_user: openstack
default_pass: password
admin_user: rabbitmq
admin_pass: password
However, the admin_user/admin_pass are not actually included in a template.  So, rabbitmq is not configured by default to use the "rabbitmq" user that the OpenStack services are trying to use.

There are some different ways to resolve this, and I'm not sure which is best:

Change rabbitmq's default_user to "rabbitmq", like the openstack components expect.
Change the openstack components' rabbit login to "openstack", like rabbitmq expects.
Somehow template the admin_user in the rabbitmq values.yaml to actually configure something appropriate -- it's not clear to me what that is; there doesn't appear to be an "admin_user" setting in the rabbitmq config 1.

@mattmceuen this is indeed rather ugly at present, I'd like to see us move in the direction of using proper users for rabbitmq. Until then, unless anyone objects I think option 1 makes the most sense.

I would say the best is to have randomly generated values for the
password/username inside values.yaml by default that can be overridden.
And then for the interim case I agree with Pete. Option 1.
On Sat, Feb 25, 2017 at 11:18 PM Pete Birley<EMAIL_ADDRESS>wrote:

@mattmceuen https://github.com/mattmceuen this is indeed rather ugly at
present, I'd like to see us move in the direction of using proper users for
rabbitmq. Until then, unless anyone objects I think option 1 makes the most
sense.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/att-comdev/openstack-helm/issues/239#issuecomment-282531872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfutGRpTe7zdCby2ENdFiqoHRs4nLq2ks5rgP0MgaJpZM4MMLI8
.

@jallirs stronger passwords can be worked out later, when we can also reliably present the password artifact to users. there are likely a couple of ways to do this. but i'm with @intlabs, starting with sane users is a good first step and a quick, iterative approach.

Yeah I agree. :) I think for the  interim case we're on the same page :)
On Mon, Feb 27, 2017 at 8:33 AM Brandon B. Jozsa<EMAIL_ADDRESS>wrote:

@jallirs https://github.com/jallirs stronger passwords can be worked
out later, when we can also reliably present the password artifact to
users. there are likely a couple of ways to do this. but i'm with @intlabs
https://github.com/intlabs, starting with sane users is a good first
step and a quick, iterative approach.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/att-comdev/openstack-helm/issues/239#issuecomment-282720677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfutIoL_85YChBsdw96IgP6xyke8jZKks5rgtC4gaJpZM4MMLI8
.

@jallirs Using password everywhere is indeed about as far from ideal as you could get. Something we will need to address moving forward is how to set secure passwords for services by default. Personally, I'm leaning toward proper documentation that makes it clear that users can deploy either with a customized values.yaml or using a command like:
helm install local/rabbitmq \
--name=rabbitmq \
--namespace=openstack \
--set auth.default_user=rabbitmq,auth.default_pass=$(openssl rand -base64 32 )

But I'm very keen to get any other suggestions, and we should definitely start to think about this as a group before too long.

i think this is the best way to address this, honestly. otherwise, if we try to do it in code things will quickly get messy (something by nature and vision,  we're trying to avoid). i'm not saying that we're going to be able to fight this off forever, but we should try...and clearly documenting this operations case will give us something to point when operators bring it up. just my 0.2.

Another value add of a wrapper like armada (or even a helm plugin potentially), and nest the intent right in the YAML:
values:
  auth:
    default_pass: !!python/object/apply:armada.utils.gen_password(length=8)


Add github private vulnerability reporting

Apologies for the delay on this.
Fixes https://github.com/ossf/secure-sw-dev-fundamentals/issues/111

Thanks so much! It looks good! I'll merge, and then add that if the project uses this, typically there's a SECURITY.md file that tells people to use it.


Unable to use app after entering invalid connection details for custom lnd instance

Current behaviour
After selecting to use a custom connection during the onboarding process and then submitting the form with some invalid connection details:
Error message in the terminal:
Error: 14 UNAVAILABLE: Name resolution failure
Error in the app:
A JavaScript error occurred in the main process
Clicking OK after the error message takes you to a broken application window.
Desired Behaviour
User should see a user friendly error message and then be taken back to connection setup page so that they can try again

@mrfelton related thought. Should we allow users the ability to paste in their macaroon and cert directly so they don't have to copy it over to their local machine?

@JimmyMow the cert could be easily copy/pasted by the user and stored and secured by us via the app. Hover I think the macaroon is more tricky since it is stored as binary data in the admin.macaroon file which can't easily be copy/pasted by the user without first converting it to hex format. This may require some enhancements in lnd to provide other ways of exporting/accessibng the macaroon.


Any person search with a query forces sort to be by relevance

Not actually a bug! Had not officially tackled #200 (although sort was sort of implemented as part of #214)


Error message could be improved when referencing a closure

I see the following error message (correctly) in my code:
The return type 'List' isn't a 'FutureOr<List<Script>>', as defined by the method ''.

Note the name of the method above is ''. This is for a return value from a closure. The error message could probably just omit the as defined by the method ''..
@bwilkerson @lukechurch

The error message could probably just omit the as defined by the method ''..

Perhaps generally, or perhaps just for the closure case?

There are three potential cases here: a method, a function, and a closure. They might potentially all want different messages.
The reason for including that information in the message was to provide more context for users. Given local functions and nested closures, it isn't necessarily obvious which function (in the generic sense) a given return statement is returning from.
Ironically, I think this might be more important for closures than for methods because the return type of a closure is more likely to be inferred, making it even harder for users to understand what's wrong with their code and/or how to fix it.
(For my own future reference, this is a StaticTypeWarningCode.)

Sort of a duplicate of #26056, until @bwilkerson brought up the function case 😁 .

Closing with b50319c (I suppose open a new option with the function case, if we wish, but b50319c fixes the original issue)


[SPARK-31014][CORE][3.0] InMemoryStore: remove key from parentToChildrenMap when removing key from CountingRemoveIfForEach

What changes were proposed in this pull request?
This patch addresses missed spot on SPARK-30964 (#27716) - SPARK-30964 added secondary index which defines the relationship between parent - children and able to operate all children for given parent faster.
While SPARK-30964 handled the addition and deletion of secondary index in InstanceList properly, it missed to add code to handle deletion of secondary index in CountingRemoveIfForEach, resulting to the leak of indices. This patch adds the deletion of secondary index in CountingRemoveIfForEach.
Why are the changes needed?
Described above.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A, as relevant field and class are marked as private, and it cannot be checked in higher level. I'm not sure we want to adjust scope to add a test.

cc. @gengliangwang

Test build #119443 has started for PR 27825 at commit 5dc0a7d.

Merged build finished. Test PASSed.

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

Test build #119443 has finished for PR 27825 at commit 5dc0a7d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

[error] /home/jenkins/workspace/SparkPullRequestBuilder@4/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala:385: value version is not a member of org.apache.spark.internal.config.ConfigBuilder
[error] possible cause: maybe a semicolon is missing before `value version'?
[error]     .version("3.0.0")
[error]      ^
[error] one error found

Weird failure. Will check the recent branch-3.0.

OK we should be very careful while cherry-picking commit to branch-3.0 as they're now diverged. The build failure is due to this: .version is not available in branch-3.0.
I'll raise a PR to fix it soon.

#27826 to fix build failure.

Thanks, @HeartSaVioR . The PR is merged.

Retest this please.

Test build #119446 has started for PR 27825 at commit 5dc0a7d.

Merged build finished. Test PASSed.

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

Test build #119446 has finished for PR 27825 at commit 5dc0a7d.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this, please

Test build #119454 has started for PR 27825 at commit 5dc0a7d.

Merged build finished. Test PASSed.

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

Test build #119454 has finished for PR 27825 at commit 5dc0a7d.

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

Merged build finished. Test FAILed.

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

retest this, please

Test build #119462 has started for PR 27825 at commit 5dc0a7d.

Merged build finished. Test PASSed.

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

Test build #119462 has finished for PR 27825 at commit 5dc0a7d.

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

Merged build finished. Test PASSed.

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

Thanks for reviewing and merging!


Pattern json provider does not work under nestedField (nested json provider)

When the pattern is used under nestField, logstash-logback-encoder will ignore it.
for example:
  <encoder class="net.logstash.logback.encoder.LoggingEventCompositeJsonEncoder">
       <providers>
            <timestamp>
            <nestedField>
                    <fieldName>data</fieldName>
                    <providers>
                          <pattern>
                            <pattern>
                                {
                                "method":"%method"
                                }
                            </pattern>
                          </pattern>
                    </providers>
            </nestedField>
       </providers>
  </encoder>

The reason is that LoggingEventNestedJsonProvider does not implement interface JsonFactoryAware. there is no way to set the jsonFactory. Since LoggingEventNestedJsonProvider can hold different providers, the same logic should be implemented to loop each provider to set the jsonFactory. I made the following changes in my local box and it works fine. Could you add this fix into next release. AccessEventNestedJsonProvider should do same thing.
public class LoggingEventNestedJsonProvider extends
        AbstractNestedJsonProvider<ILoggingEvent> implements JsonFactoryAware {
     ........

    @Override
    public void setJsonFactory(final JsonFactory jsonFactory) {

        for (JsonProvider<ILoggingEvent> jsonProvider : getProviders().getProviders()) {
            if (jsonProvider instanceof JsonFactoryAware) {
                ((JsonFactoryAware) jsonProvider).setJsonFactory(jsonFactory);
            }
        }
    }
}

Good catch!  Fixed.  Will be in next release


Positive test cases and signature

Hi @siowyisheng done with the positive test cases and signature. For review before merging.

Strange, I'm getting this.

Oh you are not using the latest master which has this indentation fix -
https://github.com/kelaberetiv/TagUI/commit/9c328b1aae5d15fbbac0df2058aca79a250d6fff

Ah right I needed to rebase onto master.
All looks good. Only difference is I have some windows stuff like this. Which should be ok. Merging.

Thanks! I assume you mean that the generated signature is different. Interesting, the code that generates this should also be executed on other OS, not sure why but should be ok.


How to set labelBackgroundColor in the configuration for Confluence Server

Hello,
I'm trying to configure default styles for shapes and I would like to remove white background for labels.
When I open shape style (Cmd + E), I see this setting: labelBackgroundColor=#ffffff;, after deleting background via UI, this setting changes to labelBackgroundColor=none;. Good. According to this guide (Format section -> defaultVertexStyle or defaultEdgeStyle), the labelBackgroundColor should work properly in config:

To find the key/value pairs to be used, set the style in the application and find the key and value via Edit Style (Ctrl+E) (6.5.2 and later). For example, to assign a default fontFamily of Courier New to all edges and vertices (and override all other default styles), use {"defaultVertexStyle": {"fontFamily": "Courier New"}, "defaultEdgeStyle": {"fontFamily": "Courier New"}}.

I was trying this:
"defaultVertexStyle": {
    ...
    "labelBackgroundColor": null
  },

and this
"defaultVertexStyle": {
    ...
    "labelBackgroundColor": "none"
  },

and even this
"defaultVertexStyle": {
    ...
    "labelBackgroundColor": "#f00"
  },

None of the above worked. It seems that this setting is simply ignored.
What am I doing wrong, and is it possible to set labelBackgroundColor in Confluence configuration?

Plugin Version: 9.5.3
draw.io Diagrams: 5023
Confluence Server Version: 7.8.3

Hello,
I've tried the following configuration and it works

Can you please show us the exact full configuration and which shape is used to test with?
Thanks

@ashrafteleb Thanks.
Yes, moving the labelBackgroundColor to the top did work, I was able to see red background after setting the option to #f00.
But my problem is that I can't unset this option - "labelBackgroundColor": "none", "labelBackgroundColor": null, or even "labelBackgroundColor": null didn't work.
The exact configuration:
Variant 1:
  "defaultVertexStyle": {
    "labelBackgroundColor": "none",
    "fontFamily": "Verdana",
    "fontSize": "14",
    "fillColor": "#bec5ff",
    "strokeColor": "#2f3133",
    "strokeWidth": "2",
    "rounded": 1,
    "fontColor": "#000"
  }

Variant 2:
  "defaultVertexStyle": {
    "labelBackgroundColor": null,
    "fontFamily": "Verdana",
    "fontSize": "14",
    "fillColor": "#bec5ff",
    "strokeColor": "#2f3133",
    "strokeWidth": "2",
    "rounded": 1,
    "fontColor": "#000"
  }

The issue with BPMN shapes is they already define labelBackgroundColor in their style. The default configuration only applies to shape without that style.
I'll open a new issue as a feature request to change BPMN shape and remove labelBackgroundColor from their styles.
https://github.com/jgraph/drawio/issues/2674


Allow modifier+click to make 'walk here' first option

IE shift/ctrl/alt+click always chooses 'Walk Here' instead of accidentally interacting with something on the ground.
Doing hunter recently and thought of this, since to efficiently move between traps you can't actually click on the traps themselves or you'll move slower/at them indirectly.

Duplicate of #1412


New Resource O365OrgCustomizationSetting

Pull Request (PR) description
Created new resource O365OrgCustomizationSetting.
This Pull Request (PR) fixes the following issues
- Fixes #136

@NikCharlebois actually, I do not know if the Export-Target Resource is implemented correctly. There is no need to create a resource for a setting, that is one-way only.

This change is

@andikrueger It may not expose an update setting, but it still defines a State, that is that customization is enabled or not. We just don't need to expose the Ensure parameter, and do IsSingleInstance='yes'

@NikCharlebois Will change the resource accordingly.

I will let you resolve the merge conflicts on your end

I'm on it...

Codecov Report

Merging #231 into Dev will increase coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              Dev     #231      +/-   ##
==========================================
+ Coverage   88.76%   88.84%   +0.08%
==========================================
  Files          55       56       +1
  Lines        5100     5137      +37
  Branches        8        8
==========================================
+ Hits         4527     4564      +37
  Misses        565      565
  Partials        8        8

Impacted Files
Coverage Δ

...ationSetting/MSFT_O365OrgCustomizationSetting.psm1
100% <100%> (ø)

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 0b48987...4144864. Read the comment docs.

@andikrueger any updates on the Unit tests? Need help with something? Thanks

@NikCharlebois Could you have a look at the errors? I feel, it's not my unit test, that fails.

Looks like you are missing a new line  character ' `' on line 16 of the tests

Thanks for finding this glitch. I will fix it. Rebasing was a nightmare.

Current error is thrown by 'TeamsClientConfiguration' or at least I hope it is ;-)


Remove version: Microsoft.Edge.Beta version 124.0.2478.19

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/d6cef99e-abdd-4b31-8dc6-f1787b258f52/MicrosoftEdgeBetaEnterpriseX86.msi
OK
(Automated message - build 912)

Close with reason: Package still available;


update dependency for mas-kafka config

need to update dependency for the kafka mas config module to pull its namespace from strimzi to support bom generation properly

closed by PR https://github.com/cloud-native-toolkit/terraform-gitops-mas-kafka/pull/6


om relationship to p-automator (if any?)

As an operator trying to keep our PCF automation as clean & powerful as possible, I like to stay up-to-date on the OSS tools available to me.
That's why the pivotal-cf/platform-automation docs repo caught my eye. I'm noticing the UX workflows for this mystery p-automator binary appear very similar to om 🤔 I'm assuming there's a close connection?
Perhaps it's top secret and you cannot share, but I would love to hear more about these cf-platform-automation && p-automator projects.

cc @jtarchie @calebwashburn from the pcf-automation team

If necessary, we can close this. Our Pivotal contact is Paul Hopper. We have a meeting setup with the Platform Automation team on Monday, Sept. 10th.

I'll that will be in the conversation with the team. Please feel free to close this issue.


scp through teleconsole

Hi,
I can't seem to find documentation on copying/transferring file over teleconsole. Is it possible? What I mean is simply copy files from/to the computers connected by the teleconsole session. I can imagine that this behaviour is meant not to be possible, I just don't find an answer to it.
Any help would be welcome, thank you!

Indeed you're right, this isn't possible with teleconsole.

Thanks for this info.


ADD ability to pass policy file via --policy flag

This commit addresses HACBS-1975 and allows the user to specify a YAML or JSON file containing policy configuration to ec in lieu of inline policy configuration YAML or JSON text.

Tests?

I'll add them, standby.


allow setting the logVerbosity of Documents created within the repo

LogVerbosity on automerge's Document is internal and can only be specified on document creation.
This PR allows setting the default for this via the repository.
Note: My first approach was to add a case in LogComponent, though that also needs a logger. Given we don't really want to log into the Document's logger from the Repo, it felt better to add a separate public variable. Happy to adjust though!

No qualms with where you're going - I haven't needed the logging for debugging (which is mostly where I use it) at the Document level outside of the repo, but totally game to enable it. What do you think about making another "component" for the logger, including in that private dictionary, and going from there? The public var makes it look more like you can "turn it on and off", where in practice its not nearly as configurable (enable at start or not), although I've been mostly using it only in tests (unit, functional, or interop/integration) when something was confusing to me - to debug.
Is part of the goal here to make it more dynamically configurable?

No qualms with where you're going - I haven't needed the logging for debugging (which is mostly where I use it) at the Document level outside of the repo, but totally game to enable it.

We were debugging some timing issue and tried to crank up all logging to "eleven" to see what's going on. We only later found that compared to the Repo's use of the Logger infra, Doc's is quite minimal, so that didn't turn out to be helping in the end.

What do you think about making another "component" for the logger, including in that private dictionary, and going from there?

Yeah, I went that way initially but found adding a LogComponent also requires to return a Logger.
WDYT about adding it anyways and creating a Logger for the document here. The logger wouldn't currently be used though (which initially felt a bit weird, though it also doesn't really hurt, as I think they're initialised lazily)
We could also make the returned Logger from LogComponent optional, but that felt a bit much "burden" on the usage side just for being able to specify the Doc's logger.

The public var makes it look more like you can "turn it on and off", where in practice its not nearly as configurable (enable at start or not), although I've been mostly using it only in tests (unit, functional, or interop/integration) when something was confusing to me - to debug.

Yeah - agreed, it only works for documents loaded after setting.

Is part of the goal here to make it more dynamically configurable?

Nope, not at all. It was all just for local debugging.
With that all in mind, few ideas/options:

dropping the PR is fine, we didn't get as much help out of it as we thought. Having said that, others might fall into the same trap... :-)
I found the logging in the Repo (and its components) incredibly helpful for understanding more of the machinery. Extending the logging in Doc might be a good idea.
Doc's will likely always be created by the Repo in some way or another so passing the LogLevel in the initialiser seems the right choice.
We could pass the documentLogLevel in the initialiser(s) and default it to .errorOnly. No public API for changing and no additional Logger or Logger? required.

WDYT?

Rebase on current main and went with the init param route!


Passing translated text to the attributes. description:translate="foo"

<foo description:translate="foo" />

Added as |translate, which can be trated like an attribute modifier.


[WIP] Update CFSyslogDrains alert to track adapter numbers

What
The alert was hardcoded to go off when any of the schedulers reached more than
250 drains. However, the documentation that we link to in the alert indicates
that the number of adapters should be:
(cf-syslog-drain.scheduler.drains / 250) + 2

Previously, we were running only 2 instances across the 2 availability zones,
and it was running fine, so experience suggests that the below is probably fine
as a gauge of the number adapters needed:
(sum(drains) / 250)

In this commit, I've included the
manifests/cf-manifest/env-specific/${ENV_SPECIFIC_BOSH_VARS_FILE} in the vars
used to generate the Prometheus manifest, so that the alerts have access to
useful variables about the scale of different components. I've then used the
adapter_instances variable in the alert ops file so that in future the alert
threshold will automatically scale with the number of instances of the adapter.
How to review

Code review
This ought to be run down a dev env, just in case the variables from the newly included vars file override something in an unintended way.

Who can review
Anyone

Rebased this on master because my local master was behind  when I branched off.


Prepare code for development

This PR prepares the code for the planned developments:

Add rubocop with standard gem to ensure code consistency and style, also running it in the CI.
Add a Gemfile for development dependencies, a best practice.
Add the development gems' binstubs to the bin folder to avoid having to prefix commands with bundle exec.
Adds support for direnv, a utility that allows, among other things, to automatically add the bin folder to the PATH environment variable every time we enter the project directory, closely related to binstubs. This allows us to directly use the rake command in the console and actually execute bin/rake, which in turn is like writing bundle exec rake.
Adds an IRB console in bin/console with the preloaded library for testing in development.
Set the gem to require ruby >= 3.0
Fix all rubocop warnings.
Cleanup gitignore file.

@adrianthedev changes ready!


Switch from typer to click to speed up

Checklist:

[x] My code follows the code style of this project.
[ ] My CLI method respects the signature defined in the task.
[ ] I have documented the CLI method accordingly.
[ ] I have added tests to cover my changes.
[ ] I have added a CHANGELOG entry.

Remarks for the reviewer:
@retogerber , what do you think, time-wise? worth pursuing? I've only added 'software' signatures
Major important stuff:

@DanInci : mind I've butchered your run benchmark and run method, note I'm not adding the 'example' 'remote' 'all' unimplemented capabilities, and that I also modified the sys.exits on error
All: I'm adding the module imports within commands, so the CLI is faster when just exploring its commands/arguments. This is a two sided sword...
The single-file-click-cli is rather dirty
Only software and run commands are included, Reto will add his

Migration to click looks good, although why not have separete files for the CLI interface, like before, with run, software and storage separated?

I'll give it a try migrating to multiple files.

Thanks @retogerber, I think this is ready to merge :muscle:


Feature support short circuit query in Nereids

Add new rule LogicalResultSinkToShortCircuitPointQuery similar to original SelectStmt.checkAndSetPointQuery
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


WIP Unreal 4.19 changes

UPlatformInfo changes (not backward compatible as Epic changed the class in 4.19)
4.19 externs

This was merged on the Perforce side, so we can close it

For anyone watching this, please note that support to all versions prior to 4.19 was dropped on this release. The latest commit before this merge was made into a release, 0.4.0 - which you can see here: https://github.com/proletariatgames/unreal.hx/releases


PP-13158: Bump nginx

Bump nginx patch version
Also fix the docker compose commands

Looks like the docker tests need updating too?

@katstevens yeah :) Sorted


IPv4

This is a pattern to find any IPv4 addresses. This will have a semi-high False Positive rate due to not looking for "internal" or specified IP ranges. This pattern will come in the future.
#14

False Positive:
"<IP_ADDRESS>"

This highlights "<IP_ADDRESS> (includes the quote)

IP addresses in the context of URLs can be a broader range of weird cases, and you can also shorten IPs in some other cases, e.g. try ping 127.1 to see what happens.

https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/evasive-urls-in-spam/

@GeekMasher, before we merge, I want to discuss the NOT matches I added.
I'm trying not to hit on things that will be configured company IP address, so remove things such as multicast, broadcast and "all interfaces" addresses:
    # listening to everything
    - ^0\.0\.0\.0$
    # localhost
    - ^127\..*
    # example IP ranges - TEST-NET-1, etc.
    - ^192\.0.2\.
    - ^198\.51\.100\.
    - ^203\.0\.113\.
    - ^233\.252\.0\.
    # link local
    - ^169\.254\.
    # multicast
    - ^224\.0\.0\.
    # broadcast
    - ^255\.255\.255\.255$

I don't understand what's happening with the __snapshots__/any_ipv4_addresses.csv file at all.
It told me there was a line missing, so I removed it, and now it's telling me the opposite and failing as well.
Because the format is quite opaque I don't know what the lines are telling me and what to do to correct it.


pocket_lab: Increased the widgets size

Increased the size of most of the widgets on all GUI tabs so that user event is properly detected. The font size of lvgl texts is also changed to 20 in lv_config.h file, so it was necessary to increase widgets sizes as well

@ribdp @CMinajigi Any comments?

@ribdp @CMinajigi Any comments?

just the typo mistakes which janani is mentioned above.

V1.0: Review comment fixes

Fixed the typo in 'About' view text
Corrected spelling for textarea


python310Packages.nexia: 2.0.2 -> 2.0.4

Description of changes
https://github.com/bdraco/nexia/releases/tag/2.0.4

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant-component-tests.nexia
python310Packages.nexia
python39Packages.nexia


Fix usage withing prerendered SPA

Make sure not to crash on the absence of a window object
What kind of change does this PR introduce? (check one with "x")

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?
Using ngx-datatable in the context of a prerendered application crashes as described in https://github.com/swimlane/ngx-datatable/issues/1396
What is the new behavior?
ngx-datatable can be used in a prerendered application without crashing.
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

Other information:

Can this be merged and released soon?

Really need this

@marjan-georgiev Are there any stoppers to merge this?

No, looks good. Thanks for the contribution @GrimaceOfDespair
Will be in the next release.


feat(elasticsearch): allow plain text password

Fixes #262. Allows users to put passwords in the following format:
  elasticsearch:
    auth:
      username: abc123
      password:
        value: es-plaintextpassword

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable)

I haven't had the chance to fully test this yet, but it matches the style of similar patterns in this codebase.

This change looks good and makes sense.
Not necessary requests:

add a commented out value to the main values.yaml with some comment, so it can be found by other
currently if both secret and plaintext password is given the plain text is used. default to secret one. (this just an opinion).

thanks for the contribution.

Thanks Peter!
I agree on both parts but I tried to follow the existing style. For other auth parameters the "value" takes precedence over the secrets. The values.yaml file doesn't currently contain a reference to the secrets either, so I left it as is. If you'd like me to add it, I can.


Fix resource leak

Make sure fd doesn't stay open for longer than needed.

Might be a breaking change as cat "/proc/$(pgrep -n teering)/fd/3" is not possible after this change. Have to use cat "/proc/$(pgrep -n teering)/map_files/"* then.

Ah but this will modify errno if close() fails?

close() never really fails AFAIK, I think it can with NFS in theory, so errno should not get modified, but yes, moving it past the error handling should be fine.


Fixed unnecessary reallocation in vector::resize() when size == capacity

It think there is one commit that's not needed.

Ops... I don't understand how it happened.

You don't need to close the pull request, you can just do a forced push to the branched used for this pull request.


[Question] What did you do to solve

I'm having the same problem with CANNOT LINK EXECUTABLE ffmpeg: has text relocations would you mind to share what did you to fix the problem?
Which compiler parameters did you use and which ffmpeg configuration...
thanks

Duplicate of #33


NX 13 support

I force-installed this app in an NX 13 monorepo and I got this error in the console:
TypeError: workspace_1.toFileName is not a function
    at normalizeOptions (/home/jonathan/repos/directory/node_modules/@nx-plus/docusaurus/src/schematics/app/schematic.js:12:30)
    at /home/jonathan/repos/directory/node_modules/@nx-plus/docusaurus/src/schematics/app/schematic.js:74:35
    at MergeMapSubscriber.project (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/src/rules/call.js:75:24)
    at MergeMapSubscriber._tryNext (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/operators/mergeMap.js:67:27)
    at MergeMapSubscriber._next (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/operators/mergeMap.js:57:18)
    at MergeMapSubscriber.Subscriber.next (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/Subscriber.js:66:18)
    at Observable._subscribe (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/util/subscribeToArray.js:5:20)
    at Observable._trySubscribe (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/Observable.js:44:25)
    at Observable.subscribe (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/Observable.js:30:22)
    at MergeMapOperator.call (/home/jonathan/repos/directory/node_modules/@angular-devkit/schematics/node_modules/rxjs/internal/operators/mergeMap.js:37:23)
workspace_1.toFileName is not a function
The terminal process "bash '-c', 'npx nx generate @nx-plus/docusaurus:app --name=docs --no-interactive --dry-run'" terminated with exit code: 1.

This might not be the only issue, but maybe it would help somebody fix this.

Also, I used console.log() to inspect what this object looks like:
{
  readTsConfig: [Getter],
  ProjectType: [Getter],
  projectRootDir: [Getter],
  renameSync: [Getter],
  updateJsonFile: [Getter],
  copyFile: [Getter],
  createDirectory: [Getter],
  resolveUserExistingPrettierConfig: [Getter],
  output: [Getter],
  commandsObject: [Getter],
  supportedNxCommands: [Getter],
  readWorkspaceJson: [Getter],
  readNxJson: [Getter],
  readWorkspaceConfig: [Getter],
  readPackageJson: [Getter],
  readJsonInTree: [Getter],
  updateJsonInTree: [Getter],
  updateWorkspaceInTree: [Getter],
  insert: [Getter],
  replaceNodeValue: [Getter],
  addDepsToPackageJson: [Getter],
  addMethod: [Getter],
  addIncludeToTsConfig: [Getter],
  addGlobal: [Getter],
  getProjectConfig: [Getter],
  addParameterToConstructor: [Getter],
  createOrUpdate: [Getter],
  findNodes: [Getter],
  updatePackageJsonDependencies: [Getter],
  readWorkspace: [Getter],
  renameSyncInTree: [Getter],
  renameDirSyncInTree: [Getter],
  updateNxJsonInTree: [Getter],
  addProjectToNxJsonInTree: [Getter],
  readNxJsonInTree: [Getter],
  InsertChange: [Getter],
  ReplaceChange: [Getter],
  RemoveChange: [Getter],
  getNpmScope: [Getter],
  getWorkspacePath: [Getter],
  replaceAppNameWithPath: [Getter],
  editTarget: [Getter],
  parseTarget: [Getter],
  serializeTarget: [Getter],
  unparse: [Getter],
  getWorkspace: [Getter],
  updateWorkspace: [Getter],
  updateBuilderConfig: [Getter],
  addUpdateTask: [Getter],
  addLintFiles: [Getter],
  generateProjectLint: [Getter],
  addInstallTask: [Getter],
  formatFiles: [Getter],
  deleteFile: [Getter],
  updateKarmaConf: [Getter],
  visitNotIgnoredFiles: [Getter],
  setDefaultCollection: [Getter],
  renamePackageImports: [Getter],
  renameNpmPackages: [Getter],
  checkAndCleanWithSemver: [Getter],
  updatePackagesInPackageJson: [Getter],
  libraryGenerator: [Getter],
  moveGenerator: [Getter],
  removeGenerator: [Getter],
  runCommandsGenerator: [Getter],
  convertToNxProjectGenerator: [Getter],
  convertToNxProjectSchematic: [Getter],
  stringUtils: {
    decamelize: [Function: decamelize],
    dasherize: [Function: dasherize],
    camelize: [Function: camelize],
    classify: [Function: classify],
    underscore: [Function: underscore],
    capitalize: [Function: capitalize],
    group: [Function: group],
    featurePath: [Function: featurePath]
  },
  addPackageWithInit: [Getter]
}

I have te same issue.

Same issues here.
In Nx 13, toFileName() and offsetFromRoot() are exported by the the @nrwl/devkit package.
So, I've tried the following quick & dirty patch of the<EMAIL_ADDRESS>file:

Added the const devkit_1 = require('@nrwl/devkit'); at the bottom of the file
Changed the toFileName() usage (e.g. workspace_1.toFileName(options.name)) in something like devkit_1.names(options.name).fileName
Changed the offsetFromRoot() usage (e.g. workspace_1.offsetFromRoot(options.projectRoot)) in something like devkit_1.offsetFromRoot(options.projectRoot)

Now I'm able to create a docusaurus app and to serve that. But it's probable that there could be other regressions introduced by Nx 13.

Any plans to release nx 13 compatible version @ZachJW34?

I tried forking the update-all branch, it did manage to generate the library, but not having much luck building it

I can't get Nx to be more verbose..

I've just published v13 for all packages. Try them out and let me know how they work!

This works now @ZachJW34 . Thank you so much for fixing this!


No update so long?

Could this code be updated to native Promises, typescript, etc. Is this project stale?

I think it is, you might want to check our fork: https://github.com/kaliberjs/firebase-queue/
It's not typescript, but it is Promises. It might not be what you need though because I trimmed the library quite a bit and removed a lot of functionality.

I've created an alternative for simple queue implementation https://github.com/dflourusso/firebase-simple-queue


Familia not working

Whenever I try to join the Hestia familia, it gives me the Loki falna instead, and when I exit and rejoin the world, I don't have a falna anymore.

Fixed in 1.2.0 update


Add const for new_static

Make it possible:
#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc::new_static();

I actually realized it here, but I think the API in general, needs bigger change. The reason does not have to do with new_static, it's rather new. The original idea, is that one can do either of the following:
#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc::new_static();

or:
#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc::new(buf_ptr, 1024 * 1024, true);

Even though we can mark new_static as const, there is not way we can mark new as const, since new calls an unsafe C function.
So personally I kinda wanted to simply remove new_static and new, and just wrap the following in a macro:
#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc{};

Simply put, I don't think it is a good API design if we simply put const on new_static, it works around the issue in some cases, but it does not touch the root problem

#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc{};

is fine. And call initialize function at the first time of malloc.


First label is missing on the x-axis bar graph when it is datetime type

Bug report
I am not able to see the first label on x-axis with datetime type.
My configuration is like below

Codepen
Here is the example this codepen to demonstrate the problem i have.

It should show the label properly on x-axis.

What is happening instead?
It is not showing the label properly on x-axis.

What error message are you getting?
No error

Me too! I was able to make the first bar appear by setting the x-axis min value to 1 millisecond before the first value. Now the bars are not completely centered in the grid anymore though.

Hi, I am also having this issue. The workaround suggestedd by @junedchhipa is not working for me. Any ideas on how to fix?


target_category bug

An error is reported for the parameter target_category
TypeError: call() got an unexpected keyword argument 'target_category'
When I change the parameter to targets, the error is as follows:
TypeError: forward() missing 2 required positional arguments: 'targets' and 'args'

So I would like to ask if there is any way to solve this problem. Is the version of torch incorrect


Use "adb -d" since emulators don't have screenrecord

This should solve the "multiple devices" problem.

Thanks!


Deploy from MAC to Linux - "bcrypt_lib.node: invalid ELF header"

Hello,
I'm trying to deploy a meteor app from MAC OS to Linux.
The deployment fails:
✘ Invoking deployment process: FAILED
with log:
...app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
It looks like MUP is uploading the local MAC bcrypt. I'm not sure if MUP does build bcrypt on the target Linux machine, and if it does it probably doesn't clean-up the old (MAC) binaries.
If I go to the Linux machine and I do:
cd ...app/programs/server
rm -rf npm/npm-bcrypt/node_modules/bcrypt
npm install bcrypt
then I can start service and all works.
Strangely If I don't delete the bcrypt and just do:
cd ...app/programs/server
npm install bcrypt
it doesn't work. I tried to rebuild bcrypt, etc. - no success until I delete the old binaries.
Is there an easy fix for it? Am I doing something wrong or I'm missing something...?

Hi,
Try this:

Make sure you have node 0.10.36 specified in your mup.json file
upgrade to the latest version of mup (npm install -g mup)

If the problem persists, copy/paste your mup.json file here together with the full error stack. Also, it would help to know the Meteor version you're running.
Enviado do meu iPhone
No dia 15/04/2015, às 21:25, nickich<EMAIL_ADDRESS>escreveu:

Hello,
I'm trying to deploy a meteor app from MAC OS to Linux.
The deployment fails:
✘ Invoking deployment process: FAILED
with log:
...app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
It looks like MUP is uploading the local MAC bcrypt. I'm not sure if MUP does build bcrypt on the target Linux machine, and if it does it probably doesn't clean-up the old (MAC) binaries.
If I go to the Linux machine and I do:
cd ...app/programs/server
rm -rf npm/npm-bcrypt/node_modules/bcrypt
npm install bcrypt
then I can start service and all works.
Strangely If I don't delete the bcrypt and just do:
cd ...app/programs/server
npm install bcrypt
it doesn't work. I tried to rebuild bcrypt, etc. - no success until I delete the old binaries.
Is there an easy fix for it? Am I doing something wrong or I'm missing something...?
—
Reply to this email directly or view it on GitHub.

Hi,
On the MAC:
The Meteor version is:
Meteor <IP_ADDRESS>
MUP is updated.
On the target node version is: v0.10.38.
The upstart log is (beginning and end of it, rest is repeated...):
/opt/myapp/app/programs/server/node_modules/fibers/future.js:245
throw(ex);
^
Error: /opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at bindings (/opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
at Object. (/opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
error: Forever detected script exited with code: 8
error: Script restart attempt #1
......
/opt/myapp/app/programs/server/node_modules/fibers/future.js:245
throw(ex);
^
Error: Cannot find module './middleware/compress'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Function.load [as compress] (/opt/myapp/app/programs/server/npm/webapp/node_modules/connect/lib/connect.js:89:27)
at runWebAppServer (packages/webapp/webapp_server.js:575:1)
at Package (packages/webapp/webapp_server.js:763:1)
at /opt/myapp/app/programs/server/packages/webapp.js:818:4
at /opt/myapp/app/programs/server/packages/webapp.js:829:3
at /opt/myapp/app/programs/server/boot.js:222:10
error: Forever detected script exited with code: 8

stepping down to gid: meteoruser
stepping down to uid: meteoruser

Thanks.

Try to downgrade your node version to 0.10.36 in the target by specifying it in your mup.json file.

Change your mup.json file (setup node: yes; node version: 0.10.36)
Run "mup setup"
Run "mup deploy"

Should work!
Enviado do meu iPhone
No dia 16/04/2015, às 19:25, nickich<EMAIL_ADDRESS>escreveu:

Hi,
On the MAC:
The Meteor version is:
Meteor <IP_ADDRESS>
MUP is updated.
On the target node version is: v0.10.38.
The upstart log is (beginning and end of it, rest is repeated...):
/opt/myapp/app/programs/server/node_modules/fibers/future.js:245
throw(ex);
^
Error: /opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at bindings (/opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
at Object. (/opt/myapp/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
error: Forever detected script exited with code: 8
error: Script restart attempt #1
......
/opt/myapp/app/programs/server/node_modules/fibers/future.js:245
throw(ex);
^
Error: Cannot find module './middleware/compress'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Function.load as compress
at runWebAppServer (packages/webapp/webapp_server.js:575:1)
at Package (packages/webapp/webapp_server.js:763:1)
at /opt/myapp/app/programs/server/packages/webapp.js:818:4
at /opt/myapp/app/programs/server/packages/webapp.js:829:3
at /opt/myapp/app/programs/server/boot.js:222:10
error: Forever detected script exited with code: 8
stepping down to gid: meteoruser
stepping down to uid: meteoruser
Thanks.
—
Reply to this email directly or view it on GitHub.

Hello João,
Your suggestion seems to do the trick. Thanks!
So far it works great.
Thanks.
Nikolay

Glad I could help :-)
On 17 April 2015 at 18:54, nickich<EMAIL_ADDRESS>wrote:

Closed #377 https://github.com/arunoda/meteor-up/issues/377.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/377#event-284115502.

Still seeing this with deployment from OSx to Ubuntu with .36-.43 in Meteor 1.3.
All manner of setup/deploy and npm command do not seem to work.
Is this merely an OSX to Ubuntu issue?

@vincro same here facing same issue with deploying Meteor 1.3

@piyushcoader same issue for me since I have upgraded to Meteor 1.3

I have resorted to doing my own deploys on DigitalOcean and writing my own deploys using flightplans, not ideal but less of a black box and ultimate flexibility.

I think the issue is with new meteor build system
meteor build --architecture targetArch
and i think can be solved by updating the build but i did by manual deploying

I have manually updated the bcrypt dependency
app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt
from 0.7.8 to 0.8.5 directly on my server

@mlecoq How did you manually update bcrypt? It's definitely what's breaking my app.
Incidentally, is there a way to delete bcrypt from your app and re-add it now npm is supported?

@TheRealmGaming I am not very proud of it :)
In the following directory :
/opt/myapp/app/programs/server
 npm install bcrypt

The in this one
/opt/myapp/app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules
sudo rm -fr bcrypt && ln -s ../../../../../node_modules/bcrypt

Ugly, isn't it ;)

@mlecoq and then did you re-run mup deploy? Mine isn't deploying and I imagine re-running deploy would overwrite your changes.

@TheRealmGaming no, i did not re-run mup deploy.

Hi @TheRealmGaming @mlecoq , I'm having the same issue. Thanks for your help with this. I was able to use the new bcrypt and re-run mup deploy by "fighting the clock" -- I made my "deployCheckWaitTime" value in mup.json long enough for me to be able to delete the bcrypt that is installed at /opt/app-name/app/programs/server/npm/node_modules/meteor/npm-bcrypt/ upon deployment, and reinstall the newest version (0.8.5). All I'm wondering now is whether I can automate this process or if I should open a new issue to try and get this resolved...

@SV-Developer  I may try to migrate to the new meteor-up : https://github.com/kadirahq/meteor-up

@SV-Developer I don't think it's a meteor-up issue. I have tried a manual build (meteor build ...) and the same issue occurs.

\ o / Newer versions of the following indirect dependencies are available:
npm-bcrypt 0.7.8_2 (0.8.5 is available)

@SV-Developer @TheRealmGaming This issue will be fixed in Meteor 1.3.2
For the moment you can use 1.3-beta.11 to deploy
meteor update --release<EMAIL_ADDRESS>

Great news! Thank you for researching this.

@mlecoq  Looks like the fix is not included in the 1.3.2 or <IP_ADDRESS> releases.

@lijoantony I did not test them directly with meteor up (last time I used meteor build). I will check. This issue is viewed as closed : https://github.com/meteor/meteor/issues/6778

@lijoantony you are right I still have the issue with meteor up

Not fixed in <IP_ADDRESS> either :(

Same issue here. Cannot deploy to a VM hosted by DigitalOcean.
Any help?

As mentioned by @mlecoq above, use<EMAIL_ADDRESS>Unfortunately I need 1.3.2 for some mobile fixes. Juggling with git branches now!

I, in the end ditched MUP and rolled my own scripts.  Not that hard, just not as quick as writing one line of code.  The best thing you can do on DO is to make some snapshots and then all you need to do is deploy them and run deploy/build/npm install a number of time, which can be scripted anyhow.

In the end, I got no luck from mup.
I turned to mupx, the successor of mup. I update my meteor to <IP_ADDRESS>. Then mupx smoothly deploys my app on a DigitalOcean VM with 3.13 linux kernel.
Best luck for everyone. :)

Seems like this is affecting quite a few people. Is there any prospect of it getting resolved in the near future? It has been a problem for over a year.

@mbateman I also use manual build. I think that we have to wait a release of https://github.com/kadirahq/meteor-up

@mlecoq thanks for the reply. I assume you mean copy a local build to the target platform and start it there.

@mbateman yes

I just used the<EMAIL_ADDRESS>workaround which works fine too. It seems strange that it this is not in subsequent releases.

@mbateman  If you have a stacktrace with latest version (<IP_ADDRESS>), we can reopen this issue https://github.com/meteor/meteor/issues/6778

@mlecoq I have left a comment on meteor/meteor#6778.

@zliuInspire Thanks! <IP_ADDRESS> + mupx - good works! Install to flops.ru ubuntu 14.04 linux 3.16.

@mlecoq Is the plan to include the fix present in<EMAIL_ADDRESS>in the next release? (e.g. <IP_ADDRESS>)

Switched to mupx. it works!

I forked this repo and started a new project from this basis,  the deploy script will fix the bcrypt issue automatically. You can just install the mup from here https://github.com/c9s/meteor-up