torch.nn.modules.module.ModuleAttributeError: 'AlbertEmbeddings' object has no attribute 'bias'

transformers-cli convert --model_type albert
--tf_checkpoint $ALBERT_BASE_DIR/model.ckpt-64000
--config $ALBERT_BASE_DIR/albert_config.json
--pytorch_dump_output $ALBERT_BASE_DIR/pytorch_model.bin
i am running this script
AlbertConfig {
"attention_probs_dropout_prob": 0,
"bos_token_id": 2,
"classifier_dropout_prob": 0.1,
"down_scale_factor": 1,
"embedding_size": 128,
"eos_token_id": 3,
"gap_size": 0,
"hidden_act": "gelu",
"hidden_dropout_prob": 0,
"hidden_size": 768,
"initializer_range": 0.02,
"inner_group_num": 1,
"intermediate_size": 3072,
"layer_norm_eps": 1e-12,
"max_position_embeddings": 512,
"model_type": "albert",
"net_structure_type": 0,
"num_attention_heads": 12,
"num_hidden_groups": 1,
"num_hidden_layers": 12,
"num_memory_blocks": 0,
"pad_token_id": 0,
"type_vocab_size": 2,
"vocab_size": 31990
}
Converting TensorFlow checkpoint from /data/NLP/ALBERT_Inspird_Train/albert_base/model.ckpt-64000
Loading TF weight bert/embeddings/layer_normalization/beta with shape [128]
Loading TF weight bert/embeddings/layer_normalization/beta/adam_m with shape [128]
Loading TF weight bert/embeddings/layer_normalization/beta/adam_v with shape [128]
Loading TF weight bert/embeddings/layer_normalization/gamma with shape [128]
Loading TF weight bert/embeddings/layer_normalization/gamma/adam_m with shape [128]
Loading TF weight bert/embeddings/layer_normalization/gamma/adam_v with shape [128]
Loading TF weight bert/embeddings/position_embeddings with shape [512, 128]
Loading TF weight bert/embeddings/position_embeddings/adam_m with shape [512, 128]
Loading TF weight bert/embeddings/position_embeddings/adam_v with shape [512, 128]
Loading TF weight bert/embeddings/token_type_embeddings with shape [2, 128]
Loading TF weight bert/embeddings/token_type_embeddings/adam_m with shape [2, 128]
Loading TF weight bert/embeddings/token_type_embeddings/adam_v with shape [2, 128]
Loading TF weight bert/embeddings/word_embeddings with shape [31990, 128]
Loading TF weight bert/embeddings/word_embeddings/adam_m with shape [31990, 128]
Loading TF weight bert/embeddings/word_embeddings/adam_v with shape [31990, 128]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/bias with shape [768]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/bias/adam_m with shape [768]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/bias/adam_v with shape [768]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/kernel with shape [128, 768]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/kernel/adam_m with shape [128, 768]
Loading TF weight bert/encoder/embedding_hidden_mapping_in/kernel/adam_v with shape [128, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/bias with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/bias/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/bias/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/kernel with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/kernel/adam_m with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/output/dense/kernel/adam_v with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/bias with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/bias/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/bias/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/kernel with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/kernel/adam_m with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/key/kernel/adam_v with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/bias with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/bias/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/bias/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/kernel with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/kernel/adam_m with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/query/kernel/adam_v with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/bias with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/bias/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/bias/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/kernel with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/kernel/adam_m with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/attention_1/self/value/kernel/adam_v with shape [768, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/bias with shape [3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/bias/adam_m with shape [3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/bias/adam_v with shape [3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/kernel with shape [768, 3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/kernel/adam_m with shape [768, 3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/dense/kernel/adam_v with shape [768, 3072]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/bias with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/bias/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/bias/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/kernel with shape [3072, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/kernel/adam_m with shape [3072, 768]
Loading TF weight bert/encoder/transformer/group_0/inner_group_0/ffn_1/intermediate/output/dense/kernel/adam_v with shape [3072, 768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_1/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0/layer_0/inner_group_0/layer_normalization_2/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_3/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_1/layer_1/inner_group_0/layer_normalization_4/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_21/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_10/layer_10/inner_group_0/layer_normalization_22/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_23/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_11/layer_11/inner_group_0/layer_normalization_24/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_5/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_2/layer_2/inner_group_0/layer_normalization_6/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_7/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_3/layer_3/inner_group_0/layer_normalization_8/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_10/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_4/layer_4/inner_group_0/layer_normalization_9/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_11/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_5/layer_5/inner_group_0/layer_normalization_12/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_13/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_6/layer_6/inner_group_0/layer_normalization_14/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_15/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_7/layer_7/inner_group_0/layer_normalization_16/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_17/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_8/layer_8/inner_group_0/layer_normalization_18/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_19/gamma/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/beta with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/beta/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/beta/adam_v with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/gamma with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/gamma/adam_m with shape [768]
Loading TF weight bert/encoder/transformer/group_0_9/layer_9/inner_group_0/layer_normalization_20/gamma/adam_v with shape [768]
Loading TF weight bert/pooler/dense/bias with shape [768]
Loading TF weight bert/pooler/dense/bias/adam_m with shape [768]
Loading TF weight bert/pooler/dense/bias/adam_v with shape [768]
Loading TF weight bert/pooler/dense/kernel with shape [768, 768]
Loading TF weight bert/pooler/dense/kernel/adam_m with shape [768, 768]
Loading TF weight bert/pooler/dense/kernel/adam_v with shape [768, 768]
Loading TF weight cls/predictions/output_bias with shape [31990]
Loading TF weight cls/predictions/output_bias/adam_m with shape [31990]
Loading TF weight cls/predictions/output_bias/adam_v with shape [31990]
Loading TF weight cls/predictions/transform/dense/bias with shape [128]
Loading TF weight cls/predictions/transform/dense/bias/adam_m with shape [128]
Loading TF weight cls/predictions/transform/dense/bias/adam_v with shape [128]
Loading TF weight cls/predictions/transform/dense/kernel with shape [768, 128]
Loading TF weight cls/predictions/transform/dense/kernel/adam_m with shape [768, 128]
Loading TF weight cls/predictions/transform/dense/kernel/adam_v with shape [768, 128]
Loading TF weight cls/predictions/transform/layer_normalization_25/beta with shape [128]
Loading TF weight cls/predictions/transform/layer_normalization_25/beta/adam_m with shape [128]
Loading TF weight cls/predictions/transform/layer_normalization_25/beta/adam_v with shape [128]
Loading TF weight cls/predictions/transform/layer_normalization_25/gamma with shape [128]
Loading TF weight cls/predictions/transform/layer_normalization_25/gamma/adam_m with shape [128]
Loading TF weight cls/predictions/transform/layer_normalization_25/gamma/adam_v with shape [128]
Loading TF weight cls/seq_relationship/output_bias with shape [2]
Loading TF weight cls/seq_relationship/output_bias/adam_m with shape [2]
Loading TF weight cls/seq_relationship/output_bias/adam_v with shape [2]
Loading TF weight cls/seq_relationship/output_weights with shape [2, 768]
Loading TF weight cls/seq_relationship/output_weights/adam_m with shape [2, 768]
Loading TF weight cls/seq_relationship/output_weights/adam_v with shape [2, 768]
Loading TF weight global_step with shape []
bert/embeddings/layer_normalization/beta
bert/embeddings/layer_normalization/beta/adam_m
bert/embeddings/layer_normalization/beta/adam_v
bert/embeddings/layer_normalization/gamma
bert/embeddings/layer_normalization/gamma/adam_m
bert/embeddings/layer_normalization/gamma/adam_v
bert/embeddings/position_embeddings
bert/embeddings/position_embeddings/adam_m
bert/embeddings/position_embeddings/adam_v
bert/embeddings/token_type_embeddings
bert/embeddings/token_type_embeddings/adam_m
bert/embeddings/token_type_embeddings/adam_v
bert/embeddings/word_embeddings
bert/embeddings/word_embeddings/adam_m
bert/embeddings/word_embeddings/adam_v
bert/encoder/embedding_hidden_mapping_in/bias
bert/encoder/embedding_hidden_mapping_in/bias/adam_m
bert/encoder/embedding_hidden_mapping_in/bias/adam_v
bert/encoder/embedding_hidden_mapping_in/kernel
bert/encoder/embedding_hidden_mapping_in/kernel/adam_m
bert/encoder/embedding_hidden_mapping_in/kernel/adam_v
[encoded data, 15766 characters]
bert/pooler/dense/bias/adam_m
bert/pooler/dense/bias/adam_v
bert/pooler/dense/kernel
bert/pooler/dense/kernel/adam_m
bert/pooler/dense/kernel/adam_v
cls/predictions/output_bias
cls/predictions/output_bias/adam_m
cls/predictions/output_bias/adam_v
cls/predictions/transform/dense/bias
cls/predictions/transform/dense/bias/adam_m
cls/predictions/transform/dense/bias/adam_v
cls/predictions/transform/dense/kernel
cls/predictions/transform/dense/kernel/adam_m
cls/predictions/transform/dense/kernel/adam_v
cls/predictions/transform/layer_normalization_25/beta
cls/predictions/transform/layer_normalization_25/beta/adam_m
cls/predictions/transform/layer_normalization_25/beta/adam_v
cls/predictions/transform/layer_normalization_25/gamma
cls/predictions/transform/layer_normalization_25/gamma/adam_m
cls/predictions/transform/layer_normalization_25/gamma/adam_v
cls/seq_relationship/output_bias
cls/seq_relationship/output_bias/adam_m
cls/seq_relationship/output_bias/adam_v
cls/seq_relationship/output_weights
cls/seq_relationship/output_weights/adam_m
cls/seq_relationship/output_weights/adam_v
global_step
Skipping albert/embeddings/layer_normalization/beta
Traceback (most recent call last):
File "/home/dshah/venv/bin/transformers-cli", line 8, in
sys.exit(main())
File "/home/dshah/venv/lib64/python3.8/site-packages/transformers/commands/transformers_cli.py", line 33, in main
service.run()
File "/home/dshah/venv/lib64/python3.8/site-packages/transformers/commands/convert.py", line 80, in run
convert_tf_checkpoint_to_pytorch(self._tf_checkpoint, self._config, self._pytorch_dump_output)
File "/home/dshah/venv/lib64/python3.8/site-packages/transformers/convert_albert_original_tf_checkpoint_to_pytorch.py", line 36, in convert_tf_checkpoint_to_pytorch
load_tf_weights_in_albert(model, config, tf_checkpoint_path)
File "/home/dshah/venv/lib64/python3.8/site-packages/transformers/modeling_albert.py", line 163, in load_tf_weights_in_albert
pointer = getattr(pointer, "bias")
File "/home/dshah/venv/lib64/python3.8/site-packages/torch/nn/modules/module.py", line 771, in getattr
raise ModuleAttributeError("'{}' object has no attribute '{}'".format(
torch.nn.modules.module.ModuleAttributeError: 'AlbertEmbeddings' object has no attribute 'bias'

Hi there !
I'm curious : Did you find a solution about this issue ?
Thank you


Fedora/OpenSuse crash with cereal

It seems that files generated on one system are not loadable by the same binaries on another system.

Do you think it can be a locale problem?
=> check the separator for float on both systems...

Another crash in cereal. I don't use it at all in that case.
Not analyzed but to keep the information:
Program received signal SIGILL, Illegal instruction.
0x00000000004679f3 in cereal::detail::InputBindingCreator<cereal::BinaryInputArchive, openMVG::cameras::Pinhole_Intrinsic>::InputBindingCreator() ()
(gdb) bt
#0  0x00000000004679f3 in cereal::detail::InputBindingCreator<cereal::BinaryInputArchive, openMVG::cameras::Pinhole_Intrinsic>::InputBindingCreator() ()
#1  0x0000000000453ffd in _GLOBAL__sub_I_descriptor_loader.cpp ()
#2  0x00000000004c1036 in __do_global_ctors_aux ()
#3  0x0000000000450a7b in _init ()
#4  0x00007fffffffa1e0 in ?? ()
#5  0x00000000004c0fb5 in __libc_csu_init (argc=1, argv=0x7fffffffa278, envp=0x7fffffffa288) at elf-init.c:120
#6  0x00007fffef1c21d0 in __libc_start_main () from /lib64/libc.so.6
#7  0x0000000000454d29 in _start () at ../sysdeps/x86_64/elf/start.S:113

Does unit test run correctly?

yes, unit tests works fine.
Another error that happens on renderfarm:
rapidjson internal assertion failure: IsObject()

No more opensuse machines...


What is the difference between staging-security-group, running-security-group & security-group ?

The command cf bind-security-group SECURITY-GROUP ORG SPACE binds security group to ORG and SPACE. Already security-group bind with ORG and SPACE then what is the use of bind-staging-security-group and bind-running-security-group.
It make sense that different security groups for app staging and running, what is use of bind-security-group when running security group applied to app.
Commands
cf bind-staging-security-group SECURITY-GROUP
cf bind-running-security-group SECURITY-GROUP

not mentioned ORG and SPACE. With what it is binding ORG or SPACE or container ?

I believe bind-staging-security-group applies the security group to all staging containers, and similar for the -running- variety.  The bind-security-group applies to a specific space as you can see in the command usage from the CLI, and I believe only applies to running containers.  Docs: https://docs.pivotal.io/pivotalcf/1-7/adminguide/app-sec-groups.html#binding-groups
/cc @SocalNick @dkoper

@Amit-PivotalLabs that is correct, this is also documented in OSS docs: http://docs.cloudfoundry.org/adminguide/app-sec-groups.html#binding-groups

Thank you Amit, Thats simple and clear reply.
@Amit-PivotalLabs  & @SocalNick If ORG has 5 SPACES and applied security group using bind-staging-security-group or bind-running-security-group. Is this security group will applied to all 5 SPACES ?
Because these commands applies to containers not to SPACES. Is my understanding correct ?

I believe bind-staging-security-group and bind-running-security-group would apply to not only your 5 spaces in your org, but in fact all spaces in all orgs.  I believe you need to be an admin to do this.  I don't understand your last statement: "Because these commands applies to containers."

@Niranjana-5588 all security groups end up applying to containers (personally, I would think about them applying to apps and staging tasks as containers are an implementation detail), it's just a matter of which containers.
cf bind-staging-security-group SECURITY-GROUP Applies to all staging tasks for the entire Cloud Foundry deployment.
cf bind-running-security-group SECURITY-GROUP Applies to all applications for the entire Cloud Foundry deployment.
cf bind-security-group SECURITY-GROUP ORG SPACE Applies to all applications in a space.

Got it and closing this issue. Thank you all.


The : in template event bindings is required or not

This should be made clear in documentation.

The legacy bindxxx syntax without : is only valid in these conditions.

For component tags, it is valid, but can be overrided by component properties. For example:
<my-component bindtap="func" />

This will be treated as bind:tap , unless bindtap is a component property of my-component .

For native node tags, it is valid only when fallbackListenerOnNativeNode is set in the user's template configuration. This configuration can be set like this:
Component({ template: { fallbackListenerOnNativeNode: true, /* compiled template body */ } })

It is NOT recommanded since it disables any attribute names started with bind catch on .

Invalid on other tags.

It is recommanded that : should ALWAYS be added for event bindings. It makes code clear and causes better compilation results.


7.0.1  run web error，Web Bundling failed

"version": "7.0.1",
Web Bundling failed 174ms node_modules/expo-router/entry.js (47 modules)
Unable to resolve "core-js/modules/es.error.cause.js" from "node_modules/expo-router/build/renderRootComponent.js"

hey @320430, can you provide more context how to reproduce this issue? i just tried it but there wasn't no issue, please to delete node_modules and try again

@hamzamekk
Today I downloaded a compressed file from the homepage:
https://github.com/obytes/react-native-template-obytes/archive/refs/heads/master.zip
Unzip, run pnpm install, pnpm web
The error mentioned above will occur,

If I go from the command line, "npx create-obytes-app@latest MyApp"
created the project without any errors!
What is the reason for this?

@320430, can you try the latest version now? A few fixes have been made for the web with the new expo version


Quick fix for issue 6

As discussed the proper fix will be pushed later. This fix fixes a more common use case where data is little endian. This would fail if big endian data is passed to p5.ble.js.
@yining1023 I followed the steps mentioned in CONTRIBUTING.md. Everything was a success. Tested the code too using <script src="http://localhost:8080/p5.ble.js"></script>. However the modified files in the dist folder - which are the actual library that we release - were not committed as they are ignored from the .gitignore file. Hence only parseData.js has been pushed here.
Is this correct?
This is my first time developing with javascript so I don't know the exact details. Please let me know if I made a mistake, I will correct it soon.

Hi, @armsp, this looks good! I will merge it now. I will make some API change to support big-endian soon, and publish a new version of the library.
this is correct! dist is ignored. When a new version is published, a new public link to the library will be generated. (But I'm thinking it might be helpful to keep it in case people would like to download it and use it locally.)
Thank you for your contribution, @armsp! 🎉❤


port config

hey there.
Thanks for the effort! super appreciate this!
This wondering how does one specify a port when yarn start
Thanks!

aw after some attempts i managed to get it work with appending PORT=5000 unto .env~


Swift 1.2

Includes upgrading to SwiftyJSON 2.2.0.
/cc @incanus

I’m leaning towards internal(set) var, which would keep access to the setters internal to MBRouteStep rather than exposing them to the entire app’s module.

Cool, yeah I ran with that as well. I also cleaned up some stuff around optionals some more and built out a basic playground that we can use to run through a simple use case. We can build it up from there. I symlinked the requisite files (SwiftyJSON.swift and MapboxDirections.swift) into the playground, which gets a little weird during dev, but works fine for demo purposes.

Low priority right now, but we can make a framework (https://github.com/mapbox/MapboxDirections.swift/issues/4) to bring back Objective-C support.


Updates in T2Ramsey testing

Summary
Changed frequency to always be in Hz (a few places were missing).
Changed delta in asserAlmostEqual to be a percentage of the result rather than a hard-coded value.
Details and comments
Also changed default frequency value to be osc_freq.

@yaelbh , can you please review?


Spans and Errors

Background
As we convert instrumentation, ensuring that we preserve error recording from the original instrumentation is becoming a problem. One of the big bottlenecks to this problem is that there is not clear guidance on how to record errors in OpenTelemetry. Several proposals have surfaced recently, notably:

https://github.com/open-telemetry/opentelemetry-specification/pull/427
https://github.com/open-telemetry/opentelemetry-specification/pull/432

I wrote some Ruby code to see how handling an error would look for each of the proposals. It's in this comment, but I'll cut and paste it for reference:
Example for #427
begin
  buggy_method     # raises an exception when called
rescue => e
  span.add_event(name: 'error',
                 attributes: {
                   'error.type' => e.class,
                   'error.message' => e.message,
                   'error.stack' => e.backtrace
                 })
end

Example for #432
begin
  buggy_method     # raises an exception when called
rescue => e
  span.add_event(name: 'error',
                 attributes: {
                   'log.type' => e.class,
                   'log.severity' => 'error',
                   'log.message' => e.message,
                   'frame.file' => e.backtrace_locations[0].absolute_path,
                   'frame.line' => e.backtrace_locations[0].lineno,
                   'frame.func' => e.backtrace_locations[0].label,
                   'frame.stack' => stack_to_json(e)
                 })
end

def stack_to_json(e)
  JSON.dump(
    e.backtrace_locations.map do |loc|
      { 'frame.file' => loc.absolute_path, 'frame.line' => loc.lineno, 'frame.func' => loc.label }
    end
  )
end

Should we add a Span#add_error or Span#record_error convenience method?
In writing that example, one thing became clear to me - we're going to want a convenience method to simplify recording errors.
The Go SIG has reached the same conclusion:

https://github.com/open-telemetry/opentelemetry-go/issues/248
https://github.com/open-telemetry/opentelemetry-go/pull/473

I'm wondering if we should preemptively add a convenience method. It could even no-op for the time being, or perhaps speculatively record an event with semantic conventions we expect to change. Possible names could be:

Span#add_error
Span#record_error

Should in_span record and reraise exceptions?
If we decide to add a convenience method for recording an error, does it make sense for Tracer#in_span to automatically rescue, record, and reraise exceptions. Currently dd-trace does this, and to replicate that behavior with in_span error handling needs to be inlined.

I think we can close this @mwear.

I think we can close this @mwear.


Jinja macro-centric refactor & organization

We've had several discussions about jinja macros for readability recently, and we're on board with more liberal use of them. This ticket is about trying to do this in a structured way - the google approach seems like a reasonable analog to what we should be thinking about.
While this does not need to be done in one go, generally we should follow these steps:

When updating old templates, try to replace repeated/quirky control logic with macros
If you're using the same macro more than one file, move that macro to someplace inside of ./cumulus_library/template_sql/macros, and import it from there
if you're working on a downstream study, try to follow this same pattern, and merge shared, non-study specific macros back to the main library.

We'll close this issue by consensus when we feel like we've made enough progress on this that this pattern will be self-enforcing due to utility.

Addressed via #177


Changing the port for Kibana from 5601 to any thing but still the port used is 5601

please see the screen shot

everything has started correctly but the issue is I cannot connect to Kibana

@rbcrack the port you changed is the port exposed on your host by Docker, not the port of the Kibana server.
Change that value to 8622:5601 and Docker will properly forward your host's port 8622 to the port 5601 inside the container that runs Kibana.
To change the actual port Kibana is listening on, you need to edit the value of the server.port parameter inside Kibana's configuration. There are two ways to do this, both are explained in the README.
If you do that, don't forget to also edit the Compose file with 8622:<new port value> so that Docker can forward to the right port.


Apply nullability annotations to Objective-C classes

See https://developer.apple.com/swift/blog/?id=25.

The nullability annotations have been added.


Docker container cannot run python scripts with tensorflow imported.

OS: ubuntu 20.04
CPU: 12th Gen Intel(R) Core(TM) i7-12700K
GPU: RTX 3060
When I enter the docker environment of alideeprec/deeprec-release-modelzoo:latest and run python train.py in DCN, it reports Illegal instruction (core dumped). If I use python command line, I can import numpy but as soon as I import tensorflow, the same error occurs. I searched the Internet and found the reason maybe my cpu does not support AVX but it does support AVX. Can you help me solve the problem? Thank you!

Release images are built on "Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz". For your CPU, you can't run because your CPU can't support advanced instructions. You have to build DeepRec yourself on your CPU.

My bad. Thank you!


Python crashes when computing max/min of a complex tensor

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 2.1
Python version: 3.6.8

Describe the current behavior
When taking (by mistake) the max value of a tensor with complex dtype, tf crashes python.
Describe the expected behavior
Tf should fail gracefully, i.e. throwing an error.
Standalone code to reproduce the issue
import tensorflow as tf
tf.reduce_max(tf.ones((9,), dtype=tf.complex64))

Other info / logs
2020-03-09 15:40:04.604547: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2020-03-09 15:40:04.604625: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: UNKNOWN ERROR (303)
2020-03-09 15:40:04.604723: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:156] kernel driver does not appear to be running on this host (zaccharie-Latitude-7490): /proc/driver/nvidia/version does not exist
2020-03-09 15:40:04.605857: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-03-09 15:40:04.645752: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-03-09 15:40:04.647241: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x4c32870 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-03-09 15:40:04.647293: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-03-09 15:40:04.671854: F tensorflow/compiler/xla/literal_util.cc:212] C64 element type has no minimum value
[1]    23558 abort (core dumped)  ipython

I tried on machine with and without GPU for the same result.

Hi @zaccharieramzi, I think the input type of tf.complex64 is not support in reduce_max.
Here make a PR to pick out this condition and avoid core_dump.

yes of course, you can't use reduce_max on a complex tensor, but I mean there should be a way to fail nicely: hopefully your PR does the job.
What is the new output with this fix?

@zaccharieramzi you will failed to create the max op and see the error message as this:
OP_REQUIRES failed at reduction_ops.cc:88 : Invalid argument: Unsupported PrimitiveType of MaxOp: 'C64'

Was able to reproduce the issue with TF-2.1 and TF-nightly. Please find the Gist here. Thanks!

@Leslie-Fang Can you please update related doc also? Thanks!

@jvishnuvardhan Thanks for the remind. I think it's already in the doc  https://github.com/tensorflow/tensorflow/blob/78b09356f5c1a17d869a2fbc571bd720b3450d9b/tensorflow/python/ops/math_ops.py#L2409
input_tensor: The tensor to reduce. Should have real numeric type.

You could add that it raises an exception in the style of https://github.com/tensorflow/tensorflow/blob/78b09356f5c1a17d869a2fbc571bd720b3450d9b/tensorflow/python/ops/math_ops.py#L376-L378

Hi @zaccharieramzi Thanks for the suggestions. I think this PR (https://github.com/tensorflow/tensorflow/pull/37483) has been merged.  Please take a look when feasible.

Ha, I didn't take the time to review the PR, sorry. Had I done it, I would have suggested to do the same also for the reduce_min operator which suffers from the same problem (just tested). I am going to change the title of the issue to reflect that the problem is for both operators and leave this open. I can actually even make the PR.

I would like to work on this issue

The same problem occurs for tf.keras.backend.max and tf.keras.backend.min when passing a complex dtype tensor for the argument x.

I like to contribute in this project.

@jvishnuvardhan, is it feasible to support complex numbers instead? How much work will it take?

@Rendok what would it mean to compute the max/min of a complex tensor?

@zaccharieramzi, agree, there is no total order in complex space

Now the issue produces proper error message in both Tensorflow GPU 2.4.1 and Tf Nightly 2.6 version, please find the gist here.

Closing this issue since the error message is proper now, feel free to reopen the issue.


Fix circular dependency

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (99cafb8) 100.00% compared to head (734601b) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #240   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          316       316
  Lines         9817      9819    +2
  Branches       954       954
=========================================
+ Hits          9817      9819    +2

Impacted Files
Coverage Δ

src/gravitorch/engines/alpha.py
100.00% <100.00%> (ø)

src/gravitorch/loops/observers/batch_saving.py
100.00% <100.00%> (ø)

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


Publish Action failing [BUG]

The publishing of updated charts is failing with the following error:
fatal: could not read Password for<EMAIL_ADDRESS>No such device or address

See: https://github.com/DandyDeveloper/charts/actions/runs/6274420303/job/17039782331#step:3:1

hi @DandyDeveloper - could you please take a look at this issue?
Thanks! 🙏

Hi @DandyDeveloper it looks like this chart is far ahead of what is published: https://artifacthub.io/packages/helm/dandydev-charts/redis-ha

@trawler Fixed. I'm slowly going to get up to speed with everything and update what needs to be.
I've neglected the repo for far too long - Sorry.


Attribute parts with value undefined set attribute to string "undefined"

Please refer to the following reduced repro case and read the console output: https://enshrined-noise.glitch.me/
What I wanted
Element.outerHTML:

What I got
Element.outerHTML:

After talking, I'm unsure whether or not this is a bug. Calling setAttribute() with a value of undefined results in the attribute having the string value "undefined".
The question to answer is how much an attribute binding should behave like setAttribute(). Should attribute bindings be just setAttribute(), or should the try to fix the DOM API somewhat?
@sorvell @kevinpschaaf for opinions

Definitely think this was a matter of ergonomics and not correctness for me. Consider this food for thought and not a bug report, because I'm also on the fence about what is the best way.

@sorvell @kevinpschaaf interested in your opinion here. Should undefined as an attribute value act like setAttribute(undefined) (set the attribute to the string "undefined"), or should it do something different, like remove attribute, or remove its value?

setAttribute should only accept a string so anything else is type coercion (which should be avoided). If someone wanted undefined they can return a string value of "undefined". If the value returned is false || undefined || NaN || null then the attribute should most likely be removed as you're most likely doing this for boolean values. So this usually boils down to an API like

returning '' should output

and not

In some template engines most falsey values are converted to null otherwise you have to deal with  false || undefined || NaN || null ('' is an exception)
Even though we would like to live in a world with an API decoupled from the DOM at the end of the day it's still the browser DOM API.
-from experience working with Angular's templating engine

The question for me, especially in lit-html core as opposed to lit-extended, is how much should an attribute binding behave like setAttribute(), and how does a full-binding relate to an interpolation. Would it be surprising that
 behaves different than setAttribute('foo', undefined), or different than
 (note the spaces).

I think the the spaces is a gotcha and can't be avoided unless you detect it's an attribute binding. You can provide console warnings but then you need a way to remove the warning code from production. I think all this should be in core to avoid anyone else, who plans of making their own lit-extended, to recreate these rules
another question is being able to set a property vs the attribute (I think for polymer 3 it was  el['foo'] = ' ' + undefined

My PR #204  has a possible solution

Since lit-extended has added support for the ? suffix, and I think we've pretty well determined there's no nice way to encode boolean semantics in plain HTML syntax, I think we can close this.

Well, I'm getting 'Uncaught Error: boolean attributes can only contain a single expression' at BooleanAttributePart.setValue for a very simple test <input type="checkbox" checked?=${true}/> - why is that?

That's due to HTML including the / in the attribute value in your example:
d = document.createElement('div')
d.innerHTML = `<input type="checkbox" checked?=${true}/>`

console.log(JSON.stringify(d.firstElementChild.getAttribute('checked?')))
// logs: "true/"


pmd: 6.53.0 -> 6.55.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pmd/versions.
meta.description for pmd is: An extensible cross-language static code analyzer
meta.homepage for pmd is: https://pmd.github.io/
meta.changelog for pmd is: https://pmd.github.io/pmd-6.55.0/pmd_release_notes.html
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.55.0 with grep in /nix/store/iwaxv4jfqyvzsa8ipw3pr0yk4j18zr81-pmd-6.55.0
found 6.55.0 in filename of file in /nix/store/iwaxv4jfqyvzsa8ipw3pr0yk4j18zr81-pmd-6.55.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pmd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iwaxv4jfqyvzsa8ipw3pr0yk4j18zr81-pmd-6.55.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pmd https://github.com/r-ryantm/nixpkgs/archive/19cfe4473ed099bf9d9ca1f874b0d302a8fccd91.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iwaxv4jfqyvzsa8ipw3pr0yk4j18zr81-pmd-6.55.0
ls -la /nix/store/iwaxv4jfqyvzsa8ipw3pr0yk4j18zr81-pmd-6.55.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.


Documentation issue: chaining middleware with next

Prerequisites

[X] I have searched the repository’s issues and the Kinde community to ensure my documentation issue isn’t a duplicate
[X] I have read the contributing guidelines
[X] I agree to the terms in the code of conduct

How can we improve the docs or what is missing?
I'm setting up Kinde for the first time and I need to have a few other middleware along with the include authMiddleware.  I've looked through docs and other areas and can't find an example on how to do this.
I've done this setup before following https://reacthustle.com/blog/how-to-chain-multiple-middleware-functions-in-nextjs as an example how to chain middleware but when I do this option I get an error back from the authMiddleware.
Is there any guidance that could be given?  It should would be handy to have an example in the documentation.
Provide extra context, such as what you were trying to do and your requirements
Trying to use multiple middleware in NextJS
If the docs page already exists, please provide a link
No response

Hey @rogueturnip thanks for the issue, we'll take a look into this asap

Any updates on this issue?


nbdev_build_docs fails with NotImplementedError raised in asyncio

After upgrading all Python modules with conda update --all, the nbdev_build_docs now fails with the following error:
$ nbdev_build_docs
converting: C:\Users\jnare\GitHub\git-commit-graph-ext\index.ipynb

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "c:\programdata\anaconda3\lib\site-packages\nbclient\client.py", line 365, in _async_cleanup_kernel
    await ensure_async(self.kc.stop_channels())
  File "c:\programdata\anaconda3\lib\site-packages\jupyter_client\client.py", line 125, in stop_channels
    if self.shell_channel.is_alive():
  File "c:\programdata\anaconda3\lib\site-packages\jupyter_client\client.py", line 151, in shell_channel
    socket = self.connect_shell(identity=self.session.bsession)
  File "c:\programdata\anaconda3\lib\site-packages\jupyter_client\connect.py", line 561, in connect_shell
    return self._create_connected_socket('shell', identity=identity)
  File "c:\programdata\anaconda3\lib\site-packages\jupyter_client\connect.py", line 545, in _create_connected_socket
    sock = self.context.socket(socket_type)
  File "c:\programdata\anaconda3\lib\site-packages\zmq\sugar\context.py", line 226, in socket
    s = self._socket_class(self, socket_type, **kwargs)
  File "c:\programdata\anaconda3\lib\site-packages\zmq\_future.py", line 144, in __init__
    self._init_io_state()
  File "c:\programdata\anaconda3\lib\site-packages\zmq\asyncio\__init__.py", line 53, in _init_io_state
    self.io_loop.add_reader(self._fd, lambda : self._handle_events(0, 0))
  File "c:\programdata\anaconda3\lib\asyncio\events.py", line 501, in add_reader
    raise NotImplementedError
NotImplementedError
Exception ignored in: <function Socket.__del__ at 0x000002036B509160>
Traceback (most recent call last):
  File "c:\programdata\anaconda3\lib\site-packages\zmq\sugar\socket.py", line 67, in __del__
    self.close()
  File "c:\programdata\anaconda3\lib\site-packages\zmq\_future.py", line 160, in close
    self._clear_io_state()
  File "c:\programdata\anaconda3\lib\site-packages\zmq\asyncio\__init__.py", line 60, in _clear_io_state
    self.io_loop.remove_reader(self._fd)
  File "c:\programdata\anaconda3\lib\asyncio\events.py", line 504, in remove_reader
    raise NotImplementedError
NotImplementedError:
Exception ignored in: <function Socket.__del__ at 0x000002036B509160>
Traceback (most recent call last):
  File "c:\programdata\anaconda3\lib\site-packages\zmq\sugar\socket.py", line 67, in __del__
    self.close()
  File "c:\programdata\anaconda3\lib\site-packages\zmq\_future.py", line 160, in close
    self._clear_io_state()
  File "c:\programdata\anaconda3\lib\site-packages\zmq\asyncio\__init__.py", line 60, in _clear_io_state
    self.io_loop.remove_reader(self._fd)
  File "c:\programdata\anaconda3\lib\asyncio\events.py", line 504, in remove_reader
    raise NotImplementedError
NotImplementedError:
Conversion failed on the following:
index.ipynb

I use Python 3.8.5 (from Anaconda3), Jupyter Notebook 6.1.4, JupyterLab 2.2.6
The following version of libraries are currently installed:

nbclient 0.5.1
jupyter_client 6.1.7
pyzmq 19.0.2
nbdev 1.1.5

My operating system is Windows 10 Home 64-bit, version 1909

It turns out that the same problem exists in nbdev_test_nb and was caused, from what I understand, by the change in Python 3.8, where the default event loop on Windows changed to proactor (and not "selector" event loop).
See for example issue mkdocs/mkdocs#1885 fixed in mkdocs/mkdocs#1922
It looks like for Windows one needs to add the following line
asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())


v0.1.5 doesn't run

Error message:
npm run start

><EMAIL_ADDRESS>start
> node index.js

node:internal/modules/cjs/loader:1042
  throw err;
  ^

Error: Cannot find module 'express'
Require stack:
- /home/xx/easy-reddit-downloader/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
    at Module._load (node:internal/modules/cjs/loader:885:27)
    at Module.require (node:internal/modules/cjs/loader:1105:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/home/xx/easy-reddit-downloader/index.js:12:11)
    at Module._compile (node:internal/modules/cjs/loader:1218:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at Module._load (node:internal/modules/cjs/loader:922:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/home/xx/easy-reddit-downloader/index.js' ]
}

Node.js v19.3.0

Fixing it right now!

@etec-masterofsynapse Give this version a shot! https://github.com/josephrcox/easy-reddit-downloader/releases/tag/v<IP_ADDRESS>
Sorry about that!

@josephrcox Just tested it, runs again now, thanks for the quick fix.

Woo!
 Let me know if you run into any other issues, still a work in progress! 😊


Multi Cluster EKS Istio submitting invalid Envoy config

Bug Description
I'm trying to set up a multi-network multi-primary mesh in EKS between two regions. Per https://github.com/istio/istio/issues/29359, I am setting up EIPs strapped onto my EW NLB and notifying Istio about them via the istio cm. When I add workloads following the multi cluster verify runbook though, envoy gets very mad at the config Istio is sending it:
2021-09-23T13:08:01.396294Z warn    ads ADS:EDS: ACK ERROR sleep-557747455f-8mtxg.sample-105 Internal:Proto constraint validation failed (ClusterLoadAssignmentValidationError.Endpoints[0]: embedded message failed validation | caused by LocalityLbEndpointsValidationError.LbEndpoints[1]: embedded message failed validation | caused by LbEndpointValidationError.LoadBalancingWeight: value must be greater than or equal to 1): cluster_name: "outbound|80||sleep.sample.svc.cluster.local"
endpoints {
  locality {
    region: "us-east-1"
    zone: "us-east-1a"
  }
  lb_endpoints {
    endpoint {
      address {
        socket_address {
          address: "US-EAST-1A-IP"
          port_value: 15443
        }
      }
    }
    metadata {
      filter_metadata {
        key: "envoy.transport_socket_match"
        value {
          fields {
            key: "tlsMode"
            value {
              string_value: "istio"
            }
          }
        }
      }
      filter_metadata {
        key: "istio"
        value {
          fields {
            key: "workload"
            value {
              string_value: ";;;;us-west-2-cluster"
            }
          }
        }
      }
    }
    load_balancing_weight {
      value: 1
    }
  }
  lb_endpoints {
    endpoint {
      address {
        socket_address {
          address: "US-EAST-1B-IP"
          port_value: 15443
        }
      }
    }
    metadata {
      filter_metadata {
        key: "envoy.transport_socket_match"
        value {
          fields {
            key: "tlsMode"
            value {
              string_value: "istio"
            }
          }
        }
      }
      filter_metadata {
        key: "istio"
        value {
          fields {
            key: "workload"
            value {
              string_value: ";;;;us-west-2-cluster"
            }
          }
        }
      }
    }
    load_balancing_weight {
    }
  }
...

Clearly, the load balancing weight is in fact omitted -- but I haven't done anything here other than add the EKS workaround to multi-primary multi-network vanilla stuff.
My config map fwiw:
kubectl get cm -n istio-system istio -ojsonpath='{.data.meshNetworks}' | sed -f sedscript
networks:
  vpc-0295cb78f0beb68e6:
    endpoints:
    - fromRegistry: us-east-1-cluster
    gateways:
    - address: US-EAST-1A-IP
      port: 15443
    - address: US-EAST-1B-IP
      port: 15443
    - address: US-EAST-1C-IP
      port: 15443
  vpc-0384b42480762c56a:
    endpoints:
    - fromRegistry: us-west-2-cluster
    gateways:
    - address: US-WEST-2A-IP
      port: 15443
    - address: US-WEST-2B-IP
      port: 15443
    - address: US-WEST-2C-IP
      port: 15443

Given the relatively few changes I've made, it seems like this might be a bug in Istio?
Version
$ istioctl version
client version: 1.11.2
control plane version: 1.11.2
data plane version: 1.11.2 (4 proxies), 1.9.5 (1 proxies)
$ kubectl version --short
Client Version: v1.22.1
Server Version: v1.20.7-eks-d88609
WARNING: version difference between client (1.22) and server (1.20) exceeds the supported minor version skew of +/-1

Additional Information
No response

Having the same problem on Istio 1.11.2 on EKS and Kops. On Istio 1.11.1 everything was fine so it's definitely some regression introduced in 1.11.2.

It must've been broken in https://github.com/istio/istio/pull/34810

I met the same issue, It cost me whole day to debug it.
Those func generate a 0 weight when multiple  E-W gateway instances.
https://github.com/istio/istio/blob/96710172e1e47cee227e7e8dd591a318fdfe0326/pilot/pkg/xds/ep_filters.go#L50
https://github.com/istio/istio/blob/96710172e1e47cee227e7e8dd591a318fdfe0326/pilot/pkg/xds/ep_filters.go#L174-L180
https://github.com/istio/istio/blob/96710172e1e47cee227e7e8dd591a318fdfe0326/pilot/pkg/xds/ep_filters.go#L183-L194
Now #35346 fixed it. waiting for next release.
🤡


Add a scroll-bar for news?

Is it possible to add a vertical scroll bar for news? The previous news keeps on getting hidden when new is added.

Solved by PR #729.


SideNav might not have appropriate semantics for expandability

A nav-item with sub-items is currently structured roughly as follows (omitting shadow dom boundaries and slots for simplicity):

nav-item role="listitem"

anchor

text
button aria-label="Toggle child items" aria-controls="children" expanded="false"

role="list" id="children"

nav-item
nav-item
nav-item

(Note that the sub-list (with id="children") is hidden, including from screen readers, until the parent item is expanded, so it's crucial for screen reader users to be able to discover the expandability.)
As the toggle button is inside the anchor, it is announced as part of the anchor's label, so a parent-item with the text "Dashboard" is announced (at least by VO+Safari) as "Dashboard toggle child items", rather than as something expandable or that has child-items.
Tabbing onward from the nav-item into the button inside it does announce the button as collapsed or expanded, but the association between the nav-item and the button is not particularly evident.
I'm not sure what structure would be more appropriate and provide better semantics and/or announcements. There are two vaguely similar examples in the ARIA Authoring Practices Guide:

A) A horizontal navigation whose parent items can be links themselves, in which the expand button is a sibling to the parent's anchor rather than inside it;
B) A much more complex navigation tree-view pattern, that uses roving tabindex and, although it uses list elements, overrides their semantics with treeitems and groups.

Perhaps option B – the tree-view pattern – would be the best option, but it would also add a lot of complexity and require significant changes to the current implementation.
I suspect that, at the very least, we should move the toggle button outside of the anchor, and somehow ensure that it's announced in a way that clearly identifies the parent item that it's part of. That might be achieved by combining the parent item's text with a static sub-items text (configurable via i18n API) through aria-labelledby along these lines:

nav-item role="listitem"

anchor id="anchor"

link text

button aria-labelledby="anchor subtext" aria-controls="children" expanded="false"

span hidden id="subtext"

" sub-items"

role="list" id="children"

nav-item
nav-item
nav-item

Hopefully this would lead the button of a "Dashboard" item to be annonunced as "Dashboard sub-items".

Right, thanks for raising this issue.  Not sure why I thought it was okay to put the toggle button inside the anchor.

Created a web component issue based on this issue.


File Download Auth Header Problem- Http 403 error

I am trying to download a file from server which requires the authentication. I am creating the download request like this -
var url = "http://mysite.com/GetData";
var targetPath = getLocalFolder() + 'Data/' + "offlinedata.txt";   //getLocalFolder returns "ms-appdata:///local/"
var trustHosts = true
var options = { headers: { 'Authorization': getAuthToken() } }; //Get Auth Token returns "Bearers base64String"

$cordovaFileTransfer.download(url, targetPath, options, trustHosts)
                        .then(function (result) {
}, function (err) {
      alert(JSON.stringify(err));
}, function (progress) {
                            console.log("Progress = " + JSON.stringify(progress));
 });

The above code is going to err and printing
{"code":"1","source":"http://mysite.com/GetData","target":"C:\\Data\\Users\\DefApps\\APPDATA\\Local\\Packages\\packagename\\LocalState\\Data\\Offlinedata.txt","http_status":403,"body":"Not Authenticated!"........................

However when I pass the same generated token to the same url using curl request, the data gets successfully printed in the console.
$ curl -D- -X GET -H "Authorization: Basic base64string" http://mysite.com/GetData
HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 393530
Content-Type: text/plain
Expires: -1
Server: Microsoft-IIS/8.5
content-disposition: attachment; filename=offlinedata.txt
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Thu, 30 Apr 2015 13:39:09 GMT

'Authorization': 'Basic ' + getAuthToken()

If you can include a sample project that reproduces this issue and uses both the wrapper and the underlying plugin without the wrapper (and shows which works and which doesn't), we'll be happy to take a look at this.


Handle extensible types

Compilation should be ok now that changes in ppx_deriving has been merged.

OK, this isn't bad. I don't like the naming of externally visible modules (M__...) and that unit results are stored under the names of _extend_of_yojson and _extend_to_yojson.

... unit results are stored under the names of _extend_of_yojson and _extend_to_yojson.

Since they end in a let rec, I can't use _ nor (). I added a type annotation in the form (_extend_to_yojson : unit) to ensure the resulting type.
I changed to use only one underscore rather than two in the generated module and type names. I also handled constructor rebind.

Well, they don't have to be in a let rec. You can return a non-Recursive structure item for these generated functions.

I've looked at everything else and it's good. I'll merge (and probably release) after you fix the let rec.

This is done.

How can I attribute you in a email announcement?

Zoggy's fine :)


[IT-1818] Add data and tooling dev AWS account

PR Checklist:

[x] Describe and explain your intentions for this change
See JIRA ticket.
[x] Setup pre-commit and run the validators (info in README.md)

Thanks for the review @zaro0508 !

@zaro0508 Thanks again for the review. See Bruce's comment here: https://sagebionetworks.jira.com/browse/IT-1818?focusedCommentId=146583 for his approval.

Just wanted to see if this could be merged @zaro0508


Permanent Command Palette

I would like an option to make the command palette permanently visible as a toolbar or integrated in the new "custom" title bar.
I use the command palette a lot and many times I find myself using the palette with just a mouse by scrolling through the available commands or picking one of the recent file/commands from the list. I can navigate just fine after the pallet is open but in order to open the palette quickly I have to hit the keyboard shortcut.
If the palette was permanently visible I could just pick the recent commands from it directly using a mouse.
I understand that navigation through a mouse might not be the top priority when it comes to palette design, but I hope that adding the option to make the palette permanent is not too big of a task.

I would treat this as duplicate of https://github.com/Microsoft/vscode/issues/41309


add numainfo crd and add volcano previous crd client code

add numainfo crd and add volcano previous crd client code

/approve


Fix exception when app host has no ASPNETCORE_URLS

Fixes #1928
If an app host project's launch profile doesn't specify a launchUrl or applicationUrl then the running app host won't have a ASPNETCORE_URLS environment variable. We want to pass this variable's value to the dashboard process, and currently if it's missing we throw.
The dashboard executable has a fallback value when the ASPNETCORE_URLS variable is not present (of http://localhost:18888), so it's perfectly happy to run without this variable.
This change causes the app host to fall back to that same default value for the dashboard's ASPNETCORE_URLS variable. While we could pass no value at all, and have the dashboard choose the default, it's more helpful to the user if we log the dashboard URL. This allows the user to find the dashboard, as the IDE will not be launching it automatically when in this state.

NOTE I will backport this to p3 once approved here on main.
Microsoft Reviewers: Open in CodeFlow

Can it be moved to a shared file? That will prevent it from going out of sync.

That'll make the backport challenging. Do it after we backport.

I contemplated making a shared KnownUrls file, but don't know if we want all URLs of the whole system in it. We could make it partial and import just the URLs we want, one-per-file.

/backport to 8.0-preview3

/backport to release/8.0-preview3


OPENTOK-46938 add blur options to publisher filters

What is this PR doing?
Add background blur with low and high blur strength as options in the publisher filter picker.
How should this be manually tested?

Run locally
Check that filters work and that all transitions between filters work i.e.
between blur and none
between high and low blur
between blur and existing color filters
between none and color filters
blur effects should be cleared when selected other filters (the clear method should be called, you can't tell just by looking at the publisher because the current filters actually create a new publisher, so the blur effect wouldn't be visible anyway).

What are the relevant tickets?
https://jira.vonage.com/browse/OPENTOK-46938

@maikthomas, is this ready for review again?

@maikthomas, any update?  Please advise.  Thanks! 🙏

@v-kpheng yep I just tested this with your latest blur changes and it looks like it's working well 👍
Please re-review

Tested this locally.  Looks good! 💪
Awesome work, Mike! 💪


Multiline Definition List term consumes Mustache Block opening text

Your idea:
Repro code:
{{color:red
:: 1
}}

Expected output:

Current output:

I suspect that a tweak of the Marked extension priority order may be all that is required to correct this issue.

You are probably right. Curly divs should have higher priority than definition lists.


No sample applications for the operators: IPASNEnricher and IPSpatialEnricher

The streams.network toolkit does not provide samples for the operators in the com.ibm.streamsx.network.enrichment namespace.
Currently sample applications using these operators exist in CyberSecurity toolkit only.

add a README file to document this in the samples directory


Ember 2 compatibility

I am experiencing some problems with Ember 2. I tried setting the locale property and I got an error. It works correctly only for literal values. It fails otherwise (the test in the PR will fail without the rest of the changes). I traced it to this piece of code in bs-datetimepicker.js:
config[isDatetimepickerConfigKeys[i]] = this.getWithDefault(
  'attrs.'+isDatetimepickerConfigKeys[i],
  datetimepickerDefaultConfig[isDatetimepickerConfigKeys[i]]);

When accessing attrs.locale Ember returns a MUTABLE_CELL object. Its value is something like {"value": "en-US", ...} instead of just "en-US". This results in an error in moment.js. Using just locale instead of attrs.locale seems to return the correct thing.
I am assuming this is done intentionally because of something in Ember 1. So I don't expect this to get merged as it is.

Looks good, thanks

Hi @jasonmit
Any idea when these changes will be pushed to npm?

@gburnett I will release it in the next 24 hours.

Thanks @claudiocro


Template translations with dynamic params are not correctly parsed/found

Given a {{t}} helper instance like the following:
{{t "foo.bar" baz="test"}}

Where "foo.bar" does exist in the translations file, the extension will add the green squiggly "not found" underline to it, and a hover tooltip with the text:
Translations for foo.bar" baz="test:
en-us no translation
Missed translation in project

Additionally, if the dynamic params are not set to a string value (using quotes), e.g.
{{t "foo.bar" baz=test}}

The extension appears to skip/omit (or possible fails) parsing of the instance altogether, and produces no hover tooltip or intellisense suggestion (lightbulb button).

Fixed in #3


Support type checking when using type hints

Environment data

VS Code version: 1.25.1
Extension version: 2018.7.1
OS and version: Kubuntu 18.04
Python version: Python 3.7.0b3 64-bit
Type of virtual environment used: N/A
Relevant/affected Python packages and their versions: N/A

Actual behavior

No error shown when using type hints and wrong parameters are passed to a function
Code hint pop-up shows incorrect types. The type of the "wrong" parameter gets added to the type list. In the screenshot below, see how b is shown to have a type of int, str.

Expected  behavior
Squiggly lines will be shown and errors will be reported when parameters of wrong types are passed
Steps to reproduce:

Enable the new language server (i.e. set "python.jediEnabled": false)
Write a simple function that uses type hints (like the one in the screenshot)
Call the function while passing parameters of invalid types

Logs
Starting Microsoft Python language server.
[Info  - 21:57:00] Created Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreter instance from Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreterFactory
Initializing for /usr/bin/python3.7
##########Linting Output - pylint##########

--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

[Info  - 21:58:02] Found 198 completions for file:///home/<username>/Desktop/server.py at (6, 2) after filtering

https://github.com/Microsoft/PTVS/issues/3917

@tuhinkarmakar is there any reason you can't use mypy?

There isn't any particular reason why I can't use it. Is mypy a must for type hints to work in VS Code? I don't have it installed on my system. You'll have to excuse my lack of knowledge. Python is my third language. I thought type hints will be available out of the box in the new language server.

We use type hints to help provide auto-completion/IntelliSense, not linting/error detection against type hints. For the latter you should install mypy.

Okay, I understand. I thought since VS Code shows type errors for TypeScript code, the same will be true for code written in Python as well.

As someone learning Python, and a longtime VS Code user, I found the lack of support for this to be very surprising.


Board Review: Azure DigitalTwins

The Basics
Responsible service team: Azure Digital Twins

Link to documentation describing the service:
https://github.com/Azure/azure-digital-twins/blob/private-preview/Documentation/overview.md
API surface: https://github.com/zolvarga/azure-sdk-for-js/blob/digitaltwins/sdk/digitaltwins/digitaltwins/review/digitaltwins.api.md
Product Manager contact email<EMAIL_ADDRESS>(elhorton)
Dev Lead contact email<EMAIL_ADDRESS>(jebrando)

About this client library

Name of the client library: @azure/digitaltwins
Languages for this review: Typescript
Link to the service REST APIs: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/digitaltwins/data-plane/Microsoft.DigitalTwins/preview/2020-05-31-preview/digitaltwins.json

Artifacts required (per language)
We use an API review tool (apiview) to support .NET and Java API reviews.  For Python and TypeScript, use the API extractor tool, then submit the output as a Draft PR to the relevant repository (azure-sdk-for-python or azure-sdk-for-js).
TypeScript

Upload output of api-extractor as a Draft PR.  Link to PR:
https://github.com/Azure/azure-sdk-for-js/pull/10560
Link to samples for champion scenarios:
https://github.com/zolvarga/azure-sdk-for-js/blob/digitaltwins/sdk/digitaltwins/digitaltwins/samples/Readme.md

Champion Scenarios
Manage model lifecycle
Models represent some physical or logical entity, such as an IoT device, a room it is in, or a building that room is in. They are the cornerstone of digital twins. Each type of entity should be modeled using the DTDL schema. Once a schema is documented in the service, it can be known to other clients so when a digital twin is loaded, a program unfamiliar with that digital twin could interact with it in a dynamic way (e.g. UI created from a model to enable an operator to interact with the digital twin).
Note: this API is only available for bulk creation at this time. When multiple models are included, the service will validate any internal references and reject the request (think transaction) if the validation fails. Without that validation, one would need to create all the models in a specific order to avoid bad references.

Create models in bulk
List models
Decommission a model
Delete a model

Digital twins
Digital Twins are the entities in ADT that represent physical or logical devices. They can be created, updated, read, and deleted.

CRUD
Query for digital twins

Relationships
Based on the models applied to a digital twin, it can have relationships to other digital twins. Those relationships are managed independent of the digital twin (they aren't properties directly on the twin), and are 1-way (that is, a relationship created from A->B only appears on A and not on B).

Link a digital twins to another via a relationship
List relationships on a digital twin
List incoming relationships (made by other digital twins targeting this one)
Delete a relationship

Telemetry
Digital twins that aren't physical devices may need telemetry sent on their behalf. The service SDK provides an avenue for that.

Publish telemetry for a digital twin, or a component on a digital twin

Event routes
An event route lets you send event data from digital twins in Azure Digital Twins to custom-defined endpoints in your subscriptions. Three Azure services are currently supported for endpoints: Event Hub, Event Grid, and Service Bus. Each of these Azure services can be connected to other services and acts as the middleman, sending data along to final destinations such as TSI or Azure Maps for whatever processing you need.

CRUD

Content looks good! Thanks @zolvarga

(Thanks to @meeraharidasa for the notes!)
[MS Internal only] Video

Context

Node SDK 1st review

All comments have been addressed by Zoltan

Changes made by Zoltan since last meeting:

OperationOptions is clean now
API has the same option handling (fixed by the generator mostly)
Pipeline creation was made more advanced
Client shape is the same

Breaking the Client vs. keeping it Flat?

This is a task for the swagger team
Brian suggests: break out the client to different swagger
Comparing against c# (flat structure) - Keep this consistent across JS and C#
If we wanted to split it would be : Event Routes, relationships, Models, Twins
If you want multiple clients together and there is more variation some things might be lost (ex: Storage)
Query would worry the most - used in conjunction with other things (would need all clients parallel)
Telemetry - either you want it or not (not a big deal if it gets lost)

OperationOptions

Question: Is there a way to abort interation operator if its in the middle of an io?

Action: listIncomeRelationships needs to take options
Brian said he will take this offline with Zoltan

Samples (Notes)

Scenario 1 (DigitalTwins)

Question: The Id's are constant strings that have been hard coded - is there a specific way the customers should name their models?

The underlying philosophy is that customers can use anything they like, some use GUID and some use naming systems that they come from ADT
Customers wanted the ability to define their own - tried and tested.

Question: Why is there an @ line 141 $ Line 151

It's coming from the dtdl model
In the json that’s returned from the service they have $ in front of them they are metadata items
Metadata are always $ prefixed
Important: Documented in the DT documentation

Future Plans

Action: Fix the few remaining issues then ready for release
The API is ready to release, except for a few minor changes
Everyone is comfortable w preview

Hoping for early release for ADT customers
Cadence: every month we release packages at the same time
Action: Brian will get in touch with the engineering system folks to get the preview rolling

Action Items:

Consider the fact that: If you want multiple clients together and there is more variation some things might be lost for a flat strcuture
@zolvarga  to follow up on items above
@bterlson  to follow up with engineering teams for preview


There is no escape

Is this right? Everywhere I go, a little icon is covering my code, I just want to read my code. The action in the light bulb is "move symbol to"

Hi @roblourens thank you for posting this issue. That's curious, I thought that TypeScript offers only Move to file and move to new file actions. I did a search for move symbol to in our repo and do not find results. Perhaps this is an action contributed by another extension @mjbvz ?

@aiday-mar it might be contributed from python/pylance?
Maybe further discussion could having another setting (like onCode) which minimizes lightbulb being shown by only showing lightbulb for if there are more than a certain # of refactors (these code actions have the refactor type iirc) or if there are quick fixes? This way we're not just fixing in each extension, and it might be a more blanket approach. No real preference here, just want to throw some smol ideas out there.

Hey @justschen those are good ideas. Indeed on most cursor positions, there are code actions available in the lightbulb menu, so it appears very often. We can indeed decide to show the lightbulbs only if more than 'n' actions are available where 'n' could be defined by the user. The issue I see here is that we would need to define some sort of importance metric, so that importance code actions when present, always make the lightbulb appear. I also think that with this change it could be that the lightbulb does not show up in cases where the user would have expected it to.

@aiday-mar that's a good point!
I know there is importance in certain contexts already:

in code actions: isPreferred (boolean) which is used in the context of quick fixable fixes
in diagnostics: severity (number)

both don't really help in this case since the code option appearing is basically the same move to actions that we wanted to not show everywhere, just contributed differently it seems. but definitely could field some discussion on other ways as well to improve visibility (maybe something like taking a look at max line/column length and showing the lightbulb at the end of line instead of above the cursor? just to chuck another idea out there).

Agreed. For the move to action, I am working on a PR to make it appear less often. Perhaps here we should also track the extension which is contributing the code action and notify them that the code action appears too often.

fixed by https://github.com/microsoft/vscode/pull/221419 and https://github.com/microsoft/TypeScript/pull/58548


Removed unused local process variables

I imagine those variables were left over from an earlier implementation.

I don't like this example and should probably scrap it entirely. Thanks for fixing it, though!

Out of curiosity, what don't you like about it? I liked how it's a small example that shows an intermingling of up to 6 processes

It's a holdover from an earlier draft where concurrency was covered before TLA+ or Models, so it contorts itself to avoid using things in either of those chapters. For example, assert made_calls <= max_calls; should be an invariant, while it'd be better to inject a model value or strings for the process values. That way we could show how concurrency bugs present vary with the number of workers.
So not exactly scrap it entirely, but I definitely want to rewrite it entirely to be more in line with the rest of the guide's flow.

Ok, that makes sense. I'm looking at taking this example and turning it into an internal (for now) presentation. I'd already tossed the assert and replaced with an invariant, so we're thinking along the same lines there :)
I like the idea about varying the number of workers to show concurrency bugs.


Get response url from response.xhr on ie11

RxJS version:
5.5.6
Observable version:
0.18.0
Code to reproduce:
export default response => Observable.if(
  () => response.xhr.responseURL.indexOf(URL_PART) !== -1,
  Observable.throw('redirect'),
  Observable.of(response.response),
);

Expected behavior:
return response or redirect (works fine in ff and chrome)
Actual behavior:
"Exception thrown and not caught" in file Observable.js, line 165 in IE11
There is any other way to get response URL on IE11? Or Someone see something wrong in my code? I tried babel-polyfill but still same error.

The problem is IE11 and old Edge don't have responseURL property on XMLHttpRequest object. Lots of frameworks will use request url as a fallback, but this will fail when 30x redirects happens.  The only reliable solution maybe is the backend server set some custom header to indicate response url, so I don't think rxjs need to solve this

I agree. This isn't something we can fix on the RxJS side.


Package SpringerPE/firehose-to-syslog as custom ingestor

We need a custom ingestor to consume CloudFoundry's Doppler Firehost (which is delivered via Websockets); and needs to authenticate with Cloud Foundry's UUA component.
The nice folks over at https://github.com/SpringerPE/firehose-to-syslog have just such a component; so lets just use that!

@simonjohansson - Could you add some licensing info to https://github.com/SpringerPE/firehose-to-syslog please - ideally MIT or APACHE v2.

@mrdavidlaing sure thing. All have a go at it on Monday, and keep implementing the events stuff you need.

@mrdavidlaing added licence, will start working on the extra events today if no fires crop up :)

@simonjohansson - thanks!  I'll take over packaging firehose-to-syslog into a bosh release

@mrdavidlaing great!
Let me know if you need any help.

Done - see https://github.com/logsearch/logsearch-for-cloudfoundry#adding-to-an-existing-cloud-foundry--logsearch-deployments


Bugs in the yaw calculation of snapdragon flight.

My P2 snapdragon flight still can't fly though rotation parameter has been set. Today I attempted to use the mag in MPU9250, the result is heading will slowly circle clockwise. If HMC5883 in 3DR GPS module is used, didn't circle but if I rotate quadrotor 90 degrees clockwise every time, it slowly try to turn to the origin direction before it turned. I've tried to invert y direction or invert x direction at HMC5883.cpp https://github.com/PX4/DriverFramework/blob/791c584969b2f84b2921c8c8c373962c677cefdb/drivers/hmc5883/HMC5883.cpp#L237, still the same as the follow plots:

@SamChenzx Please don't open multiple issues for the same topic. Let's continue the discussion on https://github.com/PX4/Firmware/issues/4652.


Firebase Unity SDK - Unity Editor crashed after second play

[REQUIRED] Please fill in the following fields:

Unity editor version: Unity 2020.2.1f1
Firebase Unity SDK version: 7.0.2
Source you installed the SDK: .unitypackage (.unitypackage or Unity Package Manager)
Problematic Firebase Component: Auth or Database? (Auth, Database, etc.)
Other Firebase Components in use: Auth, Database, Analytics (Auth, Database, etc.)
Additional SDKs you are using: Nothing (Only mirror) (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Windows (Mac, Windows, or Linux)
Platform you are targeting: Windows Client / Server & Linux Server (iOS, Android, and/or desktop)
Scripting Runtime: Mono (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:
I now this issue has been talked before (for ex: #720). But it started happening to me. Unity editor always crashes on second play. Execution Engine Exception error and "Could not initialize persistence" occurs. Then, any sort of process just goes infinitely and editor stops responding. I'm sick of this because I have to reopen project to test my code again.
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
Sorry but no.
What's the issue repro rate? (eg 100%, 1/5 etc)
It's probably 2/5
What happened? How can we make the problem occur?
Just download the project and open "MainMenu" scene. Run, then stop. Try to run again aannnnnd. It should freeze.
Drive Download Link
Relevant Code:
using UnityEngine;
using Firebase.Database;
using Firebase.Auth;
using Firebase;
using System.Collections;

[DisallowMultipleComponent]
[AddComponentMenu("CodeEasyYT Firebase/Firebase Auth")]
public class FirebaseManager : MonoBehaviour
{
    [Header("Firebase")]
    public DependencyStatus dependencyStatus;
    [HideInInspector] public FirebaseAuth auth;
    [HideInInspector] public FirebaseUser user;
    [HideInInspector] public DatabaseReference database;

    private MainMenuManager mainMenuManager;

    private static FirebaseManager _instance;

    public static FirebaseManager Instance { get { return _instance; } }

    public static string Username { get; private set; }

    private bool loggedIn = false;

    private void Awake()
    {
        if (_instance != null && _instance != this)
        {
            Destroy(gameObject);
            return;
        }
        else
        {
            _instance = this;
            DontDestroyOnLoad(gameObject);
        }

        FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith(task =>
        {
            dependencyStatus = task.Result;
            if(dependencyStatus == DependencyStatus.Available)
            {
                InitializeFirebase();
            }
            else
            {
                Debug.LogError("Could not resolve all Firebase dependencies: " + dependencyStatus);
                mainMenuManager.DependencyError = true;
                mainMenuManager.statusText.text = "Dependency Error";
            }
        });

        if (UnityEngine.SceneManagement.SceneManager.GetActiveScene().name == "MainMenu")
            mainMenuManager = FindObjectOfType<MainMenuManager>();
    }

    private void InitializeFirebase()
    {
        Debug.Log("Setting up Firebase Auth...");

        auth = FirebaseAuth.DefaultInstance;
        database = FirebaseDatabase.DefaultInstance.RootReference;
    }

    public void Login(string email, string password)
    {
        StartCoroutine(ActualLogin(email, password));
    }

    private IEnumerator ActualLogin(string email, string password)
    {
        var LoginTask = auth.SignInWithEmailAndPasswordAsync(email, password);

        yield return new WaitUntil(predicate: () => LoginTask.IsCompleted);

        if(LoginTask.Exception != null)
        {
            FirebaseException firebaseEx = LoginTask.Exception.GetBaseException() as FirebaseException;

            Debug.LogWarning($"Failed to register task with {firebaseEx}");
            AuthError errorCode = (AuthError)firebaseEx.ErrorCode;

            mainMenuManager.LoginFailed(errorCode);
        }
        else
        {
            loggedIn = true;

            StartCoroutine(GetUsername());

            mainMenuManager.LoginSuccess();
        }
    }

    private IEnumerator GetUsername()
    {
        var DBTask = database.Child("users").Child(user.UserId).GetValueAsync();

        yield return new WaitUntil(predicate: () => DBTask.IsCompleted);

        if(DBTask.Exception != null)
        {
            Debug.LogError($"Failed to get username with {DBTask.Exception}");
        }
        else if(DBTask.Result.Value == null)
        {
            Debug.LogError($"No user data exists on {user.UserId}");
        }
        else
        {
            //Data has successfully retrieved from server.
            DataSnapshot snapshot = DBTask.Result;

            Username = snapshot.Child("username").Value.ToString();
        }
    }
}

I just gave up on this project. I'll just do it in a way that I experienced. Still, thanks for your service.
(I'm not closing issue please fix it.

I think I done everything wrong. Sorry for disturbing.