text:
when I run code python setup.py build develop,there is a question occur.

when I run code python setup.py build develop,there is a question occur.
the main error information on below:
LINK : fatal error LNK1181: 无法打开输入文件“E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\vision.obj”
error: command 'D:\softinstall\VS2015\VC\BIN\x86_amd64\link.exe' failed with exit status 1181
I don't know how to resolve this problem,Can you help me ?

I checked my folders, there are no obj in E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc folder,just some folders with obj name.
I guess there is no obj generated by the compiler.but I don't know how to resolve it.

(BorderDet) E:\cslg\drone_object_detection\BorderDet-master>python setup.py build develop
running build
running build_py
running build_ext
building 'cvpods._C' extension
Emitting ninja build file E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
1.7.2
D:\softinstall\VS2015\VC\BIN\x86_amd64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:D:\softinstall\anaco
nda3\envs\BorderDet\lib\site-packages\torch\lib "/LIBPATH:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\lib/x64" /LIBPATH:D:\softinstall\a
naconda3\envs\BorderDet\libs /LIBPATH:D:\softinstall\anaconda3\envs\BorderDet\PCbuild\amd64 /LIBPATH:D:\softinstall\VS2015\VC\LIB\amd64 /LIBPATH:D:\s
oftinstall\VS2015\VC\ATLMFC\LIB\amd64 "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Wi
ndows Kits\NETFXSDK\4.6\lib\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x64" c10.lib torch.lib torch_cpu.lib torch_pytho
n.lib cudart.lib c10_cuda.lib torch_cuda.lib /EXPORT:PyInit__C E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg
drone_object_detection\BorderDet-master\cvpods\layers\csrc\vision.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Releas
e\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\box_iou_rotated\box_iou_rotated_cpu.obj E:\cslg\drone_object_detection\BorderDet-ma
ster\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\nms_rotated\nms_rotated_cpu.obj E:\cslg\drone_o
bject_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlign\ROIAlign_c
pu.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\cs
rc\ROIAlignRotated\ROIAlignRotated_cpu.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detecti
on\BorderDet-master\cvpods\layers\csrc\border_align\border_align_kernel.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7
Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\box_iou_rotated\box_iou_rotated_cuda.obj E:\cslg\drone_object_detection\Borde
rDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\deformable\deform_conv_cuda.obj E:\cslg
drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\deformable\d
eform_conv_cuda_kernel.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-mas
ter\cvpods\layers\csrc\lars\adaptive_lr_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_d
etection\BorderDet-master\cvpods\layers\csrc\ml_nms\ml_nms.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg
drone_object_detection\BorderDet-master\cvpods\layers\csrc\nms_rotated\nms_rotated_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\tem
p.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlign\ROIAlign_cuda.obj E:\cslg\drone_object_detection\Bor
derDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlignRotated\ROIAlignRotated_cuda.o
bj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\s
igmoid_focal_loss\SigmoidFocalLoss_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detect
ion\BorderDet-master\cvpods\layers\csrc\SwapAlign2Nat\SwapAlign2Nat_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7
\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\cuda_version.obj /OUT:build\lib.win-amd64-3.7\cvpods_C.cp37-win_amd64.pyd /
IMPLIB:E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\cs
rc_C.cp37-win_amd64.lib
LINK : fatal error LNK1181: 无法打开输入文件“E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_dete
ction\BorderDet-master\cvpods\layers\csrc\vision.obj”
error: command 'D:\softinstall\VS2015\VC\BIN\x86_amd64\link.exe' failed with exit status 1181
(BorderDet) E:\cslg\drone_object_detection\BorderDet-master>python setup.py build develop
running build
running build_py
creating build
creating build\lib.win-amd64-3.7
creating build\lib.win-amd64-3.7\cvpods
copying cvpods_init_.py -> build\lib.win-amd64-3.7\cvpods
creating build\lib.win-amd64-3.7\cvpods\checkpoint
copying cvpods\checkpoint\catalog.py -> build\lib.win-amd64-3.7\cvpods\checkpoint
copying cvpods\checkpoint\checkpoint.py -> build\lib.win-amd64-3.7\cvpods\checkpoint
copying cvpods\checkpoint\detection_checkpoint.py -> build\lib.win-amd64-3.7\cvpods\checkpoint
copying cvpods\checkpoint\model_loading.py -> build\lib.win-amd64-3.7\cvpods\checkpoint
copying cvpods\checkpoint_init_.py -> build\lib.win-amd64-3.7\cvpods\checkpoint
creating build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data\base_dataset.py -> build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data\build.py -> build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data\detection_utils.py -> build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data\registry.py -> build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data\wrapped_dataset.py -> build\lib.win-amd64-3.7\cvpods\data
copying cvpods\data_init_.py -> build\lib.win-amd64-3.7\cvpods\data
creating build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine\hooks.py -> build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine\launch.py -> build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine\predictor.py -> build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine\setup.py -> build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine\trainer.py -> build\lib.win-amd64-3.7\cvpods\engine
copying cvpods\engine_init_.py -> build\lib.win-amd64-3.7\cvpods\engine
creating build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\citypersons_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\cityscapes_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\classification_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\coco_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\crowdhumantools.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\crowdhuman_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\evaluator.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\eval_MR_multisetup.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\lvis_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\panoptic_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\pascal_voc_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\rotated_coco_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\sem_seg_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\testing.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\widerfacetools.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation\widerface_evaluation.py -> build\lib.win-amd64-3.7\cvpods\evaluation
copying cvpods\evaluation_init_.py -> build\lib.win-amd64-3.7\cvpods\evaluation
creating build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\api.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\c10.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\caffe2_export.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\caffe2_inference.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\caffe2_modeling.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\patcher.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export\shared.py -> build\lib.win-amd64-3.7\cvpods\export
copying cvpods\export_init_.py -> build\lib.win-amd64-3.7\cvpods\export
creating build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\activation_funcs.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\batch_norm.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\border_align.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\deform_conv.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\deform_conv_with_off.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\lars.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\mask_ops.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\nms.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\roi_align.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\roi_align_rotated.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\rotated_boxes.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\shape_spec.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\swap_align2nat.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers\wrappers.py -> build\lib.win-amd64-3.7\cvpods\layers
copying cvpods\layers_init_.py -> build\lib.win-amd64-3.7\cvpods\layers
creating build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\anchor_generator.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\box_regression.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\matcher.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\poolers.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\postprocessing.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\sampling.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling\test_time_augmentation.py -> build\lib.win-amd64-3.7\cvpods\modeling
copying cvpods\modeling_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling
creating build\lib.win-amd64-3.7\cvpods\solver
copying cvpods\solver\build.py -> build\lib.win-amd64-3.7\cvpods\solver
copying cvpods\solver\lr_scheduler.py -> build\lib.win-amd64-3.7\cvpods\solver
copying cvpods\solver\registry.py -> build\lib.win-amd64-3.7\cvpods\solver
copying cvpods\solver_init_.py -> build\lib.win-amd64-3.7\cvpods\solver
creating build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\boxes.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\image_list.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\instances.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\keypoints.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\masks.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures\rotated_boxes.py -> build\lib.win-amd64-3.7\cvpods\structures
copying cvpods\structures_init_.py -> build\lib.win-amd64-3.7\cvpods\structures
creating build\lib.win-amd64-3.7\cvpods\utils
copying cvpods\utils\imports.py -> build\lib.win-amd64-3.7\cvpods\utils
copying cvpods\utils\memory.py -> build\lib.win-amd64-3.7\cvpods\utils
copying cvpods\utils\registry.py -> build\lib.win-amd64-3.7\cvpods\utils
copying cvpods\utils_init_.py -> build\lib.win-amd64-3.7\cvpods\utils
creating build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\builtin_meta.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\citypersons.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\cityscapes.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\coco.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\crowdhuman.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\imagenet.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\lvis.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\paths_route.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\voc.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets\widerface.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
copying cvpods\data\datasets_init_.py -> build\lib.win-amd64-3.7\cvpods\data\datasets
creating build\lib.win-amd64-3.7\cvpods\data\samplers
copying cvpods\data\samplers\distributed_sampler.py -> build\lib.win-amd64-3.7\cvpods\data\samplers
copying cvpods\data\samplers\grouped_batch_sampler.py -> build\lib.win-amd64-3.7\cvpods\data\samplers
copying cvpods\data\samplers\sampler.py -> build\lib.win-amd64-3.7\cvpods\data\samplers
copying cvpods\data\samplers_init_.py -> build\lib.win-amd64-3.7\cvpods\data\samplers
creating build\lib.win-amd64-3.7\cvpods\data\transforms
copying cvpods\data\transforms\transform.py -> build\lib.win-amd64-3.7\cvpods\data\transforms
copying cvpods\data\transforms\transform_gen.py -> build\lib.win-amd64-3.7\cvpods\data\transforms
copying cvpods\data\transforms\transform_util.py -> build\lib.win-amd64-3.7\cvpods\data\transforms
copying cvpods\data\transforms_init_.py -> build\lib.win-amd64-3.7\cvpods\data\transforms
creating build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\backbone.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\bifpn.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\darknet.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\efficientnet.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\fpn.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\resnet.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\splat.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone\vgg.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
copying cvpods\modeling\backbone_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone
creating build\lib.win-amd64-3.7\cvpods\modeling\basenet
copying cvpods\modeling\basenet\basenet.py -> build\lib.win-amd64-3.7\cvpods\modeling\basenet
copying cvpods\modeling\basenet_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\basenet
creating build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\circle_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\dice_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\focal_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\iou_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\reg_l1_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\sigmoid_focal_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses\smooth_l1_loss.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
copying cvpods\modeling\losses_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\losses
creating build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\borderdet.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\centernet.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\dynamic4seg.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\efficientdet.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\fcn.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\fcos.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\imagenet.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\moco.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\panoptic_fpn.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\pointrend.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\rcnn.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\reppoints.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\retinanet.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\semantic_seg.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\solo.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\solo_decoupled.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\ssd.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\tensormask.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch\yolov3.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
copying cvpods\modeling\meta_arch_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\meta_arch
creating build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\activation_count.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\feature_utils.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\flop_count.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\jit_handles.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\parameter_count.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\precise_bn.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\scale_grad.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils\weight_init.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
copying cvpods\modeling\nn_utils_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\nn_utils
creating build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator\proposal_utils.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator\rpn.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator\rpn_outputs.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator\rrpn.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator\rrpn_outputs.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
copying cvpods\modeling\proposal_generator_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\proposal_generator
creating build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\box_head.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\cascade_rcnn.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\fast_rcnn.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\keypoint_head.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\mask_head.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\roi_heads.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads\rotated_fast_rcnn.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
copying cvpods\modeling\roi_heads_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\roi_heads
creating build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
copying cvpods\modeling\backbone\dynamic_arch\cal_op_flops.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
copying cvpods\modeling\backbone\dynamic_arch\dynamic_backbone.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
copying cvpods\modeling\backbone\dynamic_arch\dynamic_cell.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
copying cvpods\modeling\backbone\dynamic_arch\op_with_flops.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
copying cvpods\modeling\backbone\dynamic_arch_init_.py -> build\lib.win-amd64-3.7\cvpods\modeling\backbone\dynamic_arch
creating build\lib.win-amd64-3.7\cvpods\utils\benchmark
copying cvpods\utils\benchmark\benchmark.py -> build\lib.win-amd64-3.7\cvpods\utils\benchmark
copying cvpods\utils\benchmark\timer.py -> build\lib.win-amd64-3.7\cvpods\utils\benchmark
copying cvpods\utils\benchmark_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\benchmark
creating build\lib.win-amd64-3.7\cvpods\utils\distributed
copying cvpods\utils\distributed\comm.py -> build\lib.win-amd64-3.7\cvpods\utils\distributed
copying cvpods\utils\distributed_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\distributed
creating build\lib.win-amd64-3.7\cvpods\utils\dump
copying cvpods\utils\dump\events.py -> build\lib.win-amd64-3.7\cvpods\utils\dump
copying cvpods\utils\dump\history_buffer.py -> build\lib.win-amd64-3.7\cvpods\utils\dump
copying cvpods\utils\dump\logger.py -> build\lib.win-amd64-3.7\cvpods\utils\dump
copying cvpods\utils\dump_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\dump
creating build\lib.win-amd64-3.7\cvpods\utils\env
copying cvpods\utils\env\collect_env.py -> build\lib.win-amd64-3.7\cvpods\utils\env
copying cvpods\utils\env\env.py -> build\lib.win-amd64-3.7\cvpods\utils\env
copying cvpods\utils\env_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\env
creating build\lib.win-amd64-3.7\cvpods\utils\file
copying cvpods\utils\file\download.py -> build\lib.win-amd64-3.7\cvpods\utils\file
copying cvpods\utils\file\file_io.py -> build\lib.win-amd64-3.7\cvpods\utils\file
copying cvpods\utils\file\serialize.py -> build\lib.win-amd64-3.7\cvpods\utils\file
copying cvpods\utils\file_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\file
creating build\lib.win-amd64-3.7\cvpods\utils\visualizer
copying cvpods\utils\visualizer\colormap.py -> build\lib.win-amd64-3.7\cvpods\utils\visualizer
copying cvpods\utils\visualizer\show.py -> build\lib.win-amd64-3.7\cvpods\utils\visualizer
copying cvpods\utils\visualizer\video_visualizer.py -> build\lib.win-amd64-3.7\cvpods\utils\visualizer
copying cvpods\utils\visualizer\visualizer.py -> build\lib.win-amd64-3.7\cvpods\utils\visualizer
copying cvpods\utils\visualizer_init_.py -> build\lib.win-amd64-3.7\cvpods\utils\visualizer
running build_ext
building 'cvpods._C' extension
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\box_iou_rotated
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\nms_rotated
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\ROIAlign
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\ROIAlignRotated
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\border_align
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\deformable
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\lars
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\ml_nms
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\sigmoid_focal_loss
creating E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers
csrc\SwapAlign2Nat
Emitting ninja build file E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
1.7.2
D:\softinstall\VS2015\VC\BIN\x86_amd64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:D:\softinstall\anaco
nda3\envs\BorderDet\lib\site-packages\torch\lib "/LIBPATH:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\lib/x64" /LIBPATH:D:\softinstall\a
naconda3\envs\BorderDet\libs /LIBPATH:D:\softinstall\anaconda3\envs\BorderDet\PCbuild\amd64 /LIBPATH:D:\softinstall\VS2015\VC\LIB\amd64 /LIBPATH:D:\s
oftinstall\VS2015\VC\ATLMFC\LIB\amd64 "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Wi
ndows Kits\NETFXSDK\4.6\lib\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x64" c10.lib torch.lib torch_cpu.lib torch_pytho
n.lib cudart.lib c10_cuda.lib torch_cuda.lib /EXPORT:PyInit__C E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg
drone_object_detection\BorderDet-master\cvpods\layers\csrc\vision.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Releas
e\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\box_iou_rotated\box_iou_rotated_cpu.obj E:\cslg\drone_object_detection\BorderDet-ma
ster\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\nms_rotated\nms_rotated_cpu.obj E:\cslg\drone_o
bject_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlign\ROIAlign_c
pu.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\cs
rc\ROIAlignRotated\ROIAlignRotated_cpu.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detecti
on\BorderDet-master\cvpods\layers\csrc\border_align\border_align_kernel.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7
Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\box_iou_rotated\box_iou_rotated_cuda.obj E:\cslg\drone_object_detection\Borde
rDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\deformable\deform_conv_cuda.obj E:\cslg
drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\deformable\d
eform_conv_cuda_kernel.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-mas
ter\cvpods\layers\csrc\lars\adaptive_lr_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_d
etection\BorderDet-master\cvpods\layers\csrc\ml_nms\ml_nms.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg
drone_object_detection\BorderDet-master\cvpods\layers\csrc\nms_rotated\nms_rotated_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\tem
p.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlign\ROIAlign_cuda.obj E:\cslg\drone_object_detection\Bor
derDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\ROIAlignRotated\ROIAlignRotated_cuda.o
bj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\s
igmoid_focal_loss\SigmoidFocalLoss_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detect
ion\BorderDet-master\cvpods\layers\csrc\SwapAlign2Nat\SwapAlign2Nat_cuda.obj E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7
\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\csrc\cuda_version.obj /OUT:build\lib.win-amd64-3.7\cvpods_C.cp37-win_amd64.pyd /
IMPLIB:E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_detection\BorderDet-master\cvpods\layers\cs
rc_C.cp37-win_amd64.lib
LINK : fatal error LNK1181: 无法打开输入文件“E:\cslg\drone_object_detection\BorderDet-master\build\temp.win-amd64-3.7\Release\cslg\drone_object_dete
ction\BorderDet-master\cvpods\layers\csrc\vision.obj”
error: command 'D:\softinstall\VS2015\VC\BIN\x86_amd64\link.exe' failed with exit status 1181

cvpods doesn't support windows platform currently, please check Linux system for using.

authors: FateScript shaojiestar

repo: Megvii-BaseDetection/BorderDet


text:
No Read Me information from ioBroker

Inside ioBroker under "Adapters", clicking "?" there comes no information about the adapter.
I have to go manually on github to get the information about the adapter.

done

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
加上Robust能不能上Google Play

加上Robust能不能上Google Play，有没有案例？

1.保守方案：
可以针对Google Play做一个单独的Flavor，在这个Flavor下删除DexClassLoader即可。
2.参考Google Play上的梦幻西游藏宝阁案例
集成了Robust

如果是采用保守方案，对于Flavor的配置等可以联系我，qq : 514019824

删除了DexClassLoader 那Robust还能用吗？==

authors: hedex kartyjoin liukewill

repo: Meituan-Dianping/Robust

license_source: bigquery


text:
为什么组件的ShardDatabaseMetaData实现是空的

在结合hibernate使用该组件的时候，发现开启hibernate的自动生成表功能后，报出空指针异常，具体看下来是因为组件的ShardDatabaseMetaData实现为空，这里是使用错误吗？有解决方案吗？

具体是调用的ShardDatabaseMetaData的哪个方法? 我看一下能否支持

具体是调用的ShardDatabaseMetaData的哪个方法? 我看一下能否支持

public ResultSet getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types)
你是这个类里面的大部分实现方法好像都是空实现，这个是需要使用者自己去实现吗？想问下咱们这个组件只有结合mybatis使用的最佳实践吗？

1.分库分表场景下ShardDatabaseMetaData这里的方法大部分是"没有准确实现或无需使用"的 所以我们这里一般都是上层框架必须要使用的情况下才会想办法做下支持
2.mtdp内部基本都是mybatis 其他框架目前没有专门去做支持 后面我们会考虑增加

还有就是，我发现组件对connection中不支持的方法直接抛出了异常，其中有个方法是getWarnings，这个方法在Hibernate释放连接资源的时候使用到了，而且是在释放资源前调用的，这样导致连接释放失败。。。这个就是很大的问题了，我的资源池设置了100个连接，很快就耗尽了
如果方便的话，加下微信好友(duanmu1210893441),这样交流比较方便

repo: Meituan-Dianping/Zebra


text:
Longlist 安卓机上卡顿

当Longlist中有图片或者结构稍微复杂时候，和rn的自带组件flatlist组件一样在安卓机器上卡顿
希望官方能够参考 https://github.com/Flipkart/recyclerlistview 改善下性能

好的，我会列入到后续任务

@wxlworkhard 大才😄

authors: leoxiaoping wxlworkhard

repo: Meituan-Dianping/beeshell


text:
setState后Modal里展示没有渲染

伪代码
this.state = {createStartDate: '2017-11-11'}
render() {
return (
<View style={{flex: 1}}>
<SlideModal  ref={(c) => {this._slideModal = c;}}>

<Text style={{fontSize: 14, color: colors.black}}>
{this.state.createStartDate}

);
}
使用SlideModal作了一个 筛选框，里面一些类似input，还有文本 。Moadl展开的情况下setState，没渲染，关闭后重新展开，又渲染了

我也遇到了这个问题，暂时的解决方案是在setState函数中传入一个回调，在回调中调用modal的open方法


text:
如何禁用转发？

小程序原生代码只要不实现onShareAppMessage即可禁用转发功能，mpvue貌似没法去掉

升级下 mpvue 版本

不适用 onShareAppMessage 就可以啦~ 估计版本问题把

wx.hideShareMenu()

新版本的mpvue确实可以了。之前的版本是没有定义也自动绑上去的。感谢

authors: aOrz yuconora yuki070 zzzzzshPig

repo: Meituan-Dianping/mpvue


text:
Initial implementation for framework flag shell completion

Resolves #61
This pr adds shell completion for the --framework flag. This feature should
help users with discovering framework options, prevent typos and last but not
leas, typing less.
cc @basokant

Lgtm! I'm guessing u still need to run the completion command and add the completion script?

Yes, you need to register the flag for the completion generation with a function that gets called for the option but that's a simple one line function.
https://github.com/MitchellBerend/go-blueprint/blob/7bef3e027fa9491d4c8a25ae1f40ff8124581bed/cmd/create.go#L47-L49
https://github.com/MitchellBerend/go-blueprint/blob/7bef3e027fa9491d4c8a25ae1f40ff8124581bed/cmd/frameworks/frameworkFlag.go#L42-L44

Lgtm! I'm guessing u still need to run the completion command and add the completion script?

Yes, you need to register the flag for the completion generation with a function that gets called for the option but that's a simple one line function.
https://github.com/MitchellBerend/go-blueprint/blob/7bef3e027fa9491d4c8a25ae1f40ff8124581bed/cmd/create.go#L47-L49
https://github.com/MitchellBerend/go-blueprint/blob/7bef3e027fa9491d4c8a25ae1f40ff8124581bed/cmd/frameworks/frameworkFlag.go#L42-L44
cc @basokant

This is awesome! I thought you would have to add the shell completion script that's generated from 'go-blueprint completion', but this is way better!

source: gharchive/pull-request

authors: MitchellBerend basokant

repo: Melkeydev/go-blueprint


text:
Decide which pair should work on what datetime work unit

The work units available are:
1. datetime.TimeDelta
   * constructor
   * class and instance attributes
   * pick two operations
   * total_seconds()

2. datetime.Date
   * constructor
   * pick one of the class methods
   * class and instance attributes
   * pick two instance methods

3. datetime.DateTime
   * constructor
   * pick one of the class methods
   * class and instance attributes
   * pick two instance methods

Decide which pair from #11 should work on what work unit. Document this

Pair 2: Adam+Michael+Melker takes datetime.TimeDelta

repo: Melkster/voc


text:
RuntimeError: Tensor for 'out' is on CPU, Tensor for argument #1 'self' is on CPU, but expected them to be on GPU (while checking arguments for addmm) [ WARN:0] global C:\Users\appveyor\AppData\Local\Temp\1\pip-req-build-n4ekh6o5\opencv\modules\videoio\src\cap_msmf.cpp (435) `anonymous-namespace'::SourceReaderCB::~SourceReaderCB terminating async callback

Hi, there
I've been trying to run the code but failed, this is the error I get.
el start
load model finished
start opencv
opencv finished
Traceback (most recent call last):
File "C:/Users/1/PycharmProjects/Minimal-Hand-pytorch-main/demo.py", line 55, in
hand_verts, j3d_recon = mano(pose0, shape.float())
File "E:\Users\1\anaconda3\envs\yolo\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "C:\Users\1\PycharmProjects\Minimal-Hand-pytorch-main\manopth\manolayer.py", line 187, in forward
th_v_posed = th_v_shaped + torch.matmul(
RuntimeError: Tensor for 'out' is on CPU, Tensor for argument #1 'self' is on CPU, but expected them to be on GPU (while checking arguments for addmm)
[ WARN:0] global C:\Users\appveyor\AppData\Local\Temp\1\pip-req-build-n4ekh6o5\opencv\modules\videoio\src\cap_msmf.cpp (435) `anonymous-namespace'::SourceReaderCB::~SourceReaderCB terminating async callback
Any ideas as to how to fix this? Thanks in advance

@Alvin-guodong  Try to run print(torch.cuda.is_available())

I also meet this error, torch.cuda.is_available() is True
File "/home/zy/code/Minimal-Hand-pytorch/demo_dl.py", line 66, in <module>     hand_verts, j3d_recon = mano(pose0, shape.float())   File "/home/zy/miniconda3/envs/zy/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl     result = self.forward(*input, **kwargs)   File "/home/zy/miniconda3/envs/zy/lib/python3.8/site-packages/manopth/manolayer.py", line 187, in forward     th_v_posed = th_v_shaped + torch.matmul( RuntimeError: Tensor for 'out' is on CPU, Tensor for argument #1 'self' is on CPU, but expected them to be on GPU (while checking arguments for addmm)
as the above error states describes, in manolayer.py th_v_posed = th_v_shaped + torch.matmul(self.th_posedirs, th_pose_map.transpose(0, 1)).permute(2, 0, 1). the  th_v_shaped and self.th_posedirs's device is cpu, but the th_pose_map's device is cuda.

Please refer to here

authors: Alvin-guodong MengHao666 canghaiyunfan


text:
Change "Playlist 0000" to something more fun

C'mon, this is Streamus awesomesauce program not a robot. What's a good name for an initial playlist?

Simply just: awesomesauce ?

"Dank Memes"

Its a bit generic but how about just "Favorite Playlist"?

Honestly, "New Playlist". Anything too crazy could be confusing to new users.
I don't get the trend of informal language in software. It doesn't make the application any more familiar, just seems patronizing. That's just me.

Seriously, I think "New Playlist" would be best. Kinda helps explain to the user what it is if that makes sense and gets them to click it.

As a counter-argument, https://www.youtube.com/watch?v=KKYkmYuk5l8&t=23m20s
I've watched this a couple of times and Alexis Ohanian can't stress enough how important it is to surprise and delight users. Especially when you're a small company. Little things can really make people happy..
Maybe this isn't the area for that, but I certainly think it's worth considering more than being drab with the title.

I vote for "My Playlist".

"MeoMix"? "Blank Mixtape"? "My Jams"?

I think I'm going to be lame and go with "My first playlist" :-1: but it's for the best.

authors: DynamicSeagull JordanBlakey MeoMix bshah2016 gaborbernat hypershadsy silviubogan

repo: MeoMix/StreamusChromeExtension


text:
tabBarView's title can not be displayed  properly in Swift Example

hi, MerrickSapsford,
I downloaded and tried your the Example. Objective-C version worked great, but Swift version can not work finely.
Following your ReadME, I had run the Example, result as follow: (Xcode 7.3.1)
Can you help me ? Thanks in advance !

Can not upload the pic

Fixed as of 0.3.3

It works, thanks

authors: MerrickSapsford sunwrt

license: mit


text:
Test/na 250

Updates to the tests

Updated Max Volume rendering
Added Min Volume Rendering
Expanded 3D panel when taking snapshots of Max and Min Volume Rendering

@seankmartin
I was getting errors on the last test step of the tests, related to the color map and the transfer function. The error was on the Shader and it said that there was no transferFunction function. So I marked as 'skip' the last step for each test.
What shader can I use that would allow me to unskip the last test step?

Hey @SimaoBolota-MetaCell, this looks great! Thanks
Actually, the transferFunction tests might just work for you now, they were only recently merged into main so it might have just been bad timing. If it still doesn't work, let me know and I can help

@seankmartin
I am still getting these errors when using the transferFunction in the shader, tried with

https://neuroglancer.dev.metacell.us/#!{"dimensions":{"x":[7.48e-7%2C"m"]%2C"y":[7.48e-7%2C"m"]%2C"z":[0.000001%2C"m"]%2C"t":[0.001%2C"s"]}%2C"position":[29725.693359375%2C17808.77734375%2C11941.41796875%2C0]%2C"crossSectionScale":36.59823444367803%2C"projectionOrientation":[-0.13906417787075043%2C0.09761909395456314%2C0.22333434224128723%2C0.959819495677948]%2C"projectionScale":17983.459691529064%2C"projectionDepth":-0.7497788410238861%2C"layers":[{"type":"image"%2C"source":"zarr://s3://aind-open-data/exaSPIM_653980_2023-08-10_20-08-29_fusion_2023-08-24/fused.zarr/"%2C"localDimensions":{"c'":[1%2C""]}%2C"localPosition":[0]%2C"tab":"rendering"%2C"shader":"#uicontrol invlerp normalized(range=[0%2C200])\n#uicontrol transferFunction colormap(range=[0%2C200])\nvoid main() {\n  emitRGBA(colormap())%3B\n}\n"%2C"shaderControls":{"normalized":{"range":[67%2C201]}%2C"colormap":{"color":"#1100ff"%2C"controlPoints":[{"position":174%2C"color":{"0":0%2C"1":0%2C"2":0%2C"3":0}}%2C{"position":450%2C"color":{"0":255%2C"1":255%2C"2":255%2C"3":255}}]}}%2C"crossSectionRenderScale":0.47527330239775784%2C"volumeRendering":"on"%2C"volumeRenderingDepthSamples":844.412726025728%2C"name":"fused.zarr"}]%2C"showSlices":false%2C"selectedLayer":{"visible":true%2C"layer":"fused.zarr"}%2C"layout":"4panel"}
https://neuroglancer.dev.metacell.us/#!{"dimensions":{"x":[6e-9%2C"m"]%2C"y":[6e-9%2C"m"]%2C"z":[3e-8%2C"m"]}%2C"position":[5376.5%2C6656.5%2C925.5]%2C"crossSectionScale":1%2C"projectionOrientation":[0.013126025907695293%2C0.08239474147558212%2C-0.01648133620619774%2C0.9963770508766174]%2C"projectionScale":16384%2C"layers":[{"type":"image"%2C"source":"precomputed://gs://neuroglancer-public-data/kasthuri2011/image_color_corrected"%2C"tab":"rendering"%2C"shader":"#uicontrol invlerp normalized\n#uicontrol transferFunction tf\nvoid main() {\n  emitRGBA(tf())%3B\n}\n"%2C"shaderControls":{"tf":{"defaultColor":"#b21f1f"%2C"controlPoints":[[35%2C"#b21f1f"%2C0.5176470588235295]%2C[179%2C"#ffffff"%2C1]]}}%2C"volumeRendering":"on"%2C"name":"image_color_corrected"}]%2C"showSlices":false%2C"selectedLayer":{"visible":true%2C"layer":"image_color_corrected"}%2C"layout":"4panel"}

in neuroglancer.dev which is displaying the 'master' branch
https://github.com/MetaCell/neuroglancer-python/assets/99416933/55128bcb-aa4d-4730-99f6-46347fc963fc

authors: SimaoBolota-MetaCell seankmartin

repo: MetaCell/neuroglancer-python


text:
Build fails with "undefined symbol: camlMetacoq_template_plugin__Primitive__7"

I run into a problem when building MetaCoq 1.1 for Coq 8.16 from the source release. The full error is:
COQC theories/Loader.v
File "./theories/Loader.v", line 4, characters 0-51:
Error:
Dynlink error: error loading shared library: Dynlink.Error (Dynlink.Cannot_open_dll "Failure(\"/home/dev/metacoq-1.1-8.16/safechecker/src/././metacoq_safechecker_plugin.cmxs: undefined symbol: camlMetacoq_template_plugin__Primitive__7\")")

metacoq-compile-log.txt
I'm quite lost at how to solve this problem.

I think the problem is that you have MetaCoq installed as an opam package and want to build locally. That's what the
findlib: [WARNING] Package coq-metacoq-template-ocaml has multiple definitions in /home/dev/metacoq-1.1-8.16/safechecker/../template-coq/META.coq-metacoq-template-ocaml, /home/dev/.local/share/ocaml/coq-metacoq-template-ocaml/META

warnings are about.
Try getting rid of anything MetaCoq-related in /home/dev/.local/share/ocaml/, then build locally, and then -- optionally -- use make install to install again.

@yforster I do not use opam, but I did have an compiled version of MetaCoq in my path indeed. Removing the old files indeed gets rid of the warnings, but I still get the same compilation error: metacoq-error.txt

This should be added to the FAQ of compilation problems

authors: JasonGross haansn08 yforster

repo: MetaCoq/metacoq


text:
The SelaVPR in Figure 2 is missing the citation.

Thank you for the comprehensive and insightful survey paper. The SelaVPR [1] method mentioned in Figure 2 of the paper is missing the citation. Could you update it?
[1] Lu, Feng, et al. "Towards Seamless Adaptation of Pre-trained Models for Visual Place Recognition." The Twelfth International Conference on Learning Representations. 2024.

Thanks for your reminder. We will add this citation in our revised manuscript.

authors: Lu-Feng gogojjh


text:
Endpoint for retrying cover downloads

Endpoint for retrying cover downloads for metal archives releases without coverUrl.
Does not yet create an import job, just schedules the tasks. Therefore the naming may seem a bit weird as the importJobService executes the tasks but does not create jobs. But I think that's fine for now and we can change that when we know how we want to display the cover download jobs in that table.

 [Butler] Mechanism to reload covers

repo: MetalDetectorRocks/metal-release-butler


text:
vscode远程连接到ubuntu,点击登陆cursor账户无反应

vscode版本和cursorcode版本都是当日看的最新版

同遇到，这个问题无解吗？ 登陆授权非常慢

已经解决ssh问题，请更新到插件最新版本。

系统环境
Powershell 输出
Repository  λ wsl --version
WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1555

WSL2 输出
18:21:30 ~/Documents 1ms $ wslfetch --colorbar --options "windows-build,windows-rel-branch,wsl-release,wsl-kernel,windows-uptime"
               .-/+oossssoo+/-.               Windows Subsystem for Linux (WSL2)
           `:+ssssssssssssssssss+:`           dragon1573@ubuntu.localhost
         -+ssssssssssssssssssyyssss+-         Build: 22621
       .ossssssssssssssssssdMMMNysssso.       Branch: ni_release
      /ssssssssssshdmmNNmmyNMMMMhssssss/      Release: Ubuntu 23.04
     +ssssssssshmydMMMMMMMNddddyssssssss+     Kernel: Linux 5.15.90.1-microsoft-standard-WSL2
    /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Uptime (Windows): 1d 1h 51m
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
    /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
     +sssssssssdmydMMMMMMMMddddyssssssss+
      /ssssssssssshdmNNNNmyNMMMMhssssss/
       .ossssssssssssssssssdMMMNysssso.
         -+sssssssssssssssssyyyssss+-
           `:+ssssssssssssssssss+:`
               .-/+oossssoo+/-.

18:22:16 ~/Documents 1ms $ neowofetch
                             ....             dragon1573@ubuntu
              .',:clooo:  .:looooo:.          _________________
           .;looooooooc  .oooooooooo'         OS: Ubuntu 23.04 on Windows x86_64
        .;looooool:,''.  :ooooooooooc         Kernel: Linux 5.15.90.1-microsoft-standard-WSL2
       ;looool;.         'oooooooooo,         Uptime: 26 mins
      ;clool'             .cooooooc.  ,,      Packages: 3 (pipx), 1796 (dpkg), 3 (snap)
         ...                ......  .:oo,     Shell: fish 3.6.0
  .;clol:,.                        .loooo'    Terminal: Windows Terminal
 :ooooooooo,                        'ooool    CPU: 11th Gen Intel i7-1165G7 (8) @ 2.8GHz
'ooooooooooo.                        loooo.   GPU: Microsoft Corporation Basic Render Driver
'ooooooooool                         coooo.   Memory: 0.58 GiB / 7.66 GiB (7%)
 ,loooooooc.                        .loooo.   Disk (c): 131G / 248G (53%)
   .,;;;'.                          ;ooooc    Disk (d): 94G / 693G (14%)
       ...                         ,ooool.    Font: Cantarell 11 [GTK3]
    .cooooc.              ..',,'.  .cooo.     Local IP: 172.27.240.107
      ;ooooo:.           ;oooooooc.  :l.      Locale: zh_CN.utf8
       .coooooc,..      coooooooooo.
         .:ooooooolc:. .ooooooooooo'
           .':loooooo;  ,oooooooooc
               ..';::c'  .;loooo:'
                             .

18:20:53 ~/Documents 1ms $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 23.04
Release:        23.04
Codename:       lunar

软件环境

Visual Studio Code v1.77.3 (user setup)
CursorCode v0.1.1
Remote Development v0.24.0 预览版
WSL v0.77.0 预览版

当前现象

安装插件并激活，打开任意源代码文件，切换到 CursorCode 插件页面

点击「登录 Cursor 账号」，自动跳转到浏览器提示登录

使用 GitHub OAuth 三方登录 Cursor 账号，登录成功后有如下页面提示

返回 VSCode ，登录按钮仍然存在

发送任意对话，卡死在「正在思考中」状态

WSL2 问题以自行解决，希望后续版本也可以把 WSL2 的支持加上。需要用户自己在 WSL2 里安装浏览器，借助 WSLg 可视化界面完成账号登录还是有那么一点麻烦……

问题分析
已确认此问题与 WSL2 相关。
在使用 VSCode for Windows 连接到 WSL2 实例的过程中，CursorCode 插件安装在 WSL2 的 ~/.vscode-server/extensions/extensions/meteorstudio.cursorcode-x.y.z/ 下，而 VSCode 会在 Windows 环境下拉起默认浏览器使用户完成登录过程。
WSL2 中的插件无法跨系统获取 Windows 浏览器得到的登录令牌，因此 VSCode 中不提示用户登录成功。
解决方案
在 WSL2 中另外安装浏览器，复制 Cursor 插件提供的登录 URL 并在 WSL2 浏览器中打开完成登录。WSL2 提供配套 WSLg 图形化显示功能，可见浏览器界面完成登录。

Originally posted by @Dragon1573 in https://github.com/Meteo-Pig/CursorCode/issues/25#issuecomment-1518677291

authors: Dragon1573 Meteo-Pig forrestlinfeng gjm-anban

repo: Meteo-Pig/CursorCode


text:
time-sync server doesn't seem to work Meteor ROOT_URL configuration

Hello:
I have found that the time-sync server '/_timesync' route doesn't work (route not executed) when the Meteor ROOT_URL environment or configuration variable is specified.  As a result, I quickly played around with the handler using __meteor_runtime_config__.ROOT_URL_PATH_PREFIX and that seemed to do the trick.  Thus, the handler looked something like this:
const pathPrefix = __meteor_runtime_config__.ROOT_URL_PATH_PREFIX || "";

WebApp.rawConnectHandlers.use(pathPrefix + "/_timesync", function (req, res, next) {
    // Existing code
});

Since I am not using Cordova or anything like that, I didn't account for all the various server configurations (assuming it is required).
Is this something that can be fixed and released soon such that it will work with the user-status package?
Please let me know.

What version of timesync are you running?

I just played around with the latest version 0.5.1.

Also, please note that I am having to support Meteor version 1.4.3.2 right now.  I don't think this makes a difference in this case.  Hopefully I can change that soon :-)

Question please:
If I am using this with the user-status package, what is the worst case scenario with an non-function time sync handler outside of the following issues:

User login timestamp information not synchronized across all browsers.
A bogus API call which returns the entire Meteor application contents instead of a timestamp.
Basically, I am wanting to know if you can think of anything really bad or catastrophic please.

Would you please consider the code snippet I previously provided (or something similar) and create a release soon?

Fix released in v0.5.3

Fix released in v0.5.3

authors: StorytellerCZ blongstreth wreiske


text:
tracer::KvmRunWrapper: better hypervisor threads and kvm cpu count support

i think KvmRunWrapper will misbehave (or crash?) when hypervisor threads exit or spawn.
Also: Support more than one KVM CPU are should be implemented. Note that a kvm cpu is not strictly required to stick to one thread, but it may switch threads!

New threads might be hard to track. Once that disappears should be possible so.

Right. That's probably how strace -f works.

d9db7b8b04066cbc81881af6fcbd67558cec25f7 fixes cashes. KvmRunWrapper is still quite incomplete as a debugger, but apparently sufficient for qemu.

#204 introduces ed39cca which fixes an issue during wrap_syscall device operation in multi-vcpu scenarios.
There still is a chance though, that vmsh startup will fail. Check out  #206 (0f73ff9) for that.

Works for me now with 8 cores.


text:
weathergov.js:  Removed weatherEndpoint definition

Removed weatherEnpoint definition in defaults.  It is not used in the weathergov.js provider.

@rejas can you please review this PR, seems related to https://github.com/MichMich/MagicMirror/pull/2927, thanks.

Looks good @khassel

authors: dWoolridge khassel rejas

repo: MichMich/MagicMirror


text:
No way of ignoring bed explosions

Beds aren't considered entities and therefore their explosions cannot be ignored.

I'm hesitant to solve this by simply checking if the block is a bed, because it could be a plugin-induced explosion on a bed

I'm not sure, but I tried including it in the ignored_entity_explosions list but it wasn't recognized (- BED)

I'm hesitant to solve this by simply checking if the block is a bed, because it could be a plugin-induced explosion on a bed

That would be enough I think

It would work, but again, it would interfere with e.g. projectiles from a plugin that has explosive projectiles whenever they hit a protected block.

Could you detect the radius of the explosion? Because the only explosions with radius 5 are beds and respawn anchors, they could be detected and then verify the block maybe?

authors: Acervans MicleBrick

repo: MicleBrick/ExplosionRegen


text:
FATAL error upon setup: role 'xyz' doesn't exist

Hi there,
after following all the instructions to setup the project when I try to run
python manage.py migrate
I get error that role 'xyz' (my username on computer) doesn't exist. How can I resolve this issue? Entire backtrace is below....
Traceback (most recent call last):
File "/home/mihir/crm/lib/python3.8/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection
self.connect()
File "/home/mihir/crm/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/mihir/crm/lib/python3.8/site-packages/django/db/backends/base/base.py", line 200, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/mihir/crm/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/mihir/crm/lib/python3.8/site-packages/django/db/backends/postgresql/base.py", line 187, in get_new_connection
connection = Database.connect(**conn_params)
File "/home/mihir/crm/lib/python3.8/site-packages/psycopg2/init.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL:  role "xyz" does not exist
Thanks.

If you just installed postgres or haven't used it on this machine before, then you probably need to create the role xyz via the psql prompt first.

Thanks very much @RShehri . I will try this out over the weekend. I really appreciate this help.

Hi @RShehri ,
I was able to get past role doesn't exist by creating a role in postgres. Thanks for that hint. My next problem is upon running default configuration I am seeing page/resource not found on 17.0.0.1:8000/ any suggestions?
Thanks.

authors: RShehri imsevak

repo: MicroPyramid/Django-CRM


text:
Can we have ApplyRelationshipFilters Function of CU 1501 as Public and External ?

I am trying to build some generic config. functionality for which I would like to save relation between two different, I have noticed that standard NAV has a function in COD : 1501 as ApplyRelationshipFilters which can be used in this purpose as well, as it has only two parameters for Source and related RecordRef. Can we have this Function as non Local and External ?

Hi,
we don't change a local to global and external unless there is a very good reason for it. As it does not sound like you need this to extend WF functionality but rather as a helper to a new feature I suggest you copy the code into your extension instead.
Cheers,
Gert

authors: grobyns rishiaurrishabh

repo: Microsoft/AL


text:
Automatic ToString call-up

If you enter an integer or similar in messages and errors etc. a ToString should be called automatically in the background. Analog to a console. WriteLine (a);
You should not need a FORMAT

You can skip the Format if you do like this:
Message('This is my value: %1',MyInteger);

It is also usefull to add support for tables.
When calling ToString on a table, the ToString function would convert the primary key fields caption and values into a string.
example:
message(SalesHeader);
Should give
'Document Type: Order, No.: SO00001'
Perhaps adding support for overloading it, so we could add other fields to it.
Instead of showing the "Entry No." on the "Cust. Ledger Entry", we could show the "Document Type" and "Document No.".

authors: Gallimathias SirBETE kalberes kaspermoerch


text:
[Question] Dialog not called called upon button click?

Bot Info

SDK Platform: Node.js
Active Channels: Skype
Deployment Environment: Azure Bot Service

Issue Description
I am trying to build a Notification bot, in which the notifications can be approved, rejected or can be scheduled to be reminded on a later date and time.
I am using a trigger function which on an event sends the initial notification to the bot.
When the 'askLaterTime's' options are clicked the dialog which is supposed to be called is not called instantly, but when the option is clicked again the dialog starts.
I wish to send the remind later options to LUIS to get the proper date and time resolution.
I am bit stumped and hope that y'all can help.
Code Example
//Intent Recognizer
var LaterTimeIntent = new builder.IntentDialog({
    recognizers: [recognizer]
  })
  .matches('IntentName', (session, args) => {
    session.send('Will remind you ' + session.message.text)
    session.endDialog();
  });

bot.on('trigger', function(message) {
  // handle message from trigger function
  bot.beginDialog(message.address, "/ApproveRejectNotification", {
    data: message.value,
    address: message.value.address
  });
});

bot.dialog('/ApproveRejectNotification', [
  function(session, args) {
    var msg = new builder.Message().address(args.address)
      .textFormat(builder.TextFormat.markdown)
      .attachments([
        new builder.HeroCard()
        .title('Notification')
        .buttons([builder.CardAction.postBack(session, 'approved', 'Approve'),
        builder.CardAction.postBack(session, 'rejected', 'Reject'),
        builder.CardAction.postBack(session, 'remind_later' + , 'Remind Later')])
      ]);
    session.send(msg);
  }
]);

bot.dialog('/Approved', function(session, args, next) {
    //Send notification
  })
  .triggerAction({
    matches: /^approved/i,
  });

bot.dialog('/Reject', function(session, args, next) {
    //Send notification
  })
  .triggerAction({
    matches: /^rejected/i,
  });

bot.dialog('/GetLaterTime', LaterTimeIntent);

bot.dialog('/RemindLater', [
    function(session, args) {
      var askLaterTime = new builder.Message(session)
        .textFormat(builder.TextFormat.markdown)
        .text('Set reminder for : ')
        .attachments([
          new builder.HeroCard(session)
          .buttons([builder.CardAction.imBack(session, 'Tomorrow', 'Tomorrow'),
            builder.CardAction.imBack(session, 'Day after tomorrow', 'Day after tomorrow'),
            builder.CardAction.imBack(session, 'After 3 days', 'After 3 days')
          ])
        ]);
      builder.Prompts.text(session, askLaterTime)
    },
    function(session, result) {
      bot.beginDialog(session.message.address, '/GetLaterTime', result.response);
    }
  ])
  .triggerAction({
    matches: /^remind_later/i,
  });

Expected Behavior
The GetLaterTime to be called the very first time any of those buttons are clicked.
Actual Results
"Tomorrow" has to be clicked twice for the  GetLaterTime dialog to be called.

Well, I got some problem similar like this too... About the twice response, I thought is because using two recognizer.
the fisrt one is:
bot = new builder.UniversalBot(connector)
bot.dialog('/', function (session, args) {
....
})

the second is :
bot.dialog('/testPrompt', testPrompt);

const testPrompt = new builder.IntentDialog({recognizers: [recognizer]})
.matches('IntentName', (session, args) => {
.....
  })

So it has been called twice, but I have no idea how to fix this..... @nwhitmont

Can you please let us know if the issue still persists?

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botbuilder-channels/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team

authors: daveta fanidamj jinot92 lijiarui

repo: Microsoft/BotBuilder


text:
Error in documentation Sign-In Card (Attachments, cards and actions)

Hello,
The "Sign-In Card" documentation is incorrect. It seems to be a duplication of a previous card documentation.

I believe this has been fixed - I see

Sign-In Card
The Sign-In card is a card representing a request to sign in the user

on
https://docs.botframework.com/en-us/csharp/builder/sdkreference/attachments.html
I'm going to close this issue, but feel free to open new issues for further discussion.

authors: TechWatching willportnoy


text:
OAuth prompt dialog disappears (Regression)

Version
4.3.3.-56387
Describe the bug
When clicking an oauthprompt a identity selection dialog is briefly shown not giving the user enough time to select. sometimes doesn't appear at all. It defaults to an identity (the wrong one) yielding oauthprompts not working
To Reproduce
Steps to reproduce the behavior:
1.Click an oauthprompt and observe the window disappearing when shown briefly.
Expected behavior
The user can select an identity and it not default
Screenshots
Video capture doesn't show the identity selection box appearing due to behaviour of game mode on windows 10

Bot Framework Emulator - vakonadj 2019-04-27 12-09-03.zip
Additional context
Add any other context about the problem here.
[bug]

@darrenj We'll take a look at this soon. Do you know the most recent version of the Emulator where this was working as expected?

I'll try and check but last preview build was fine as far as I'm aware.
Sent from my 📱

From: Chris Whitten notifications@github.com
Sent: Sunday, April 28, 2019 7:30:42 PM
To: Microsoft/BotFramework-Emulator
Cc: Darren Jefford; Mention
Subject: Re: [Microsoft/BotFramework-Emulator] OAuth prompt dialog disappears (Regression) (#1467)
@darrenjhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdarrenj&data=01|01|darrenj%40microsoft.com|c0891f5cf999409083fa08d6cc079fef|72f988bf86f141af91ab2d7cd011db47|1&sdata=z3%2BpaqzBRjaEaVI7eM6kdFd2uY3fDpILYCZLFvddzz8%3D&reserved=0 We'll take a look at this soon. Do you know the most recent version of the Emulator where this was working as expected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FBotFramework-Emulator%2Fissues%2F1467%23issuecomment-487404112&data=01|01|darrenj%40microsoft.com|c0891f5cf999409083fa08d6cc079fef|72f988bf86f141af91ab2d7cd011db47|1&sdata=JCOXZurzL%2BLk200TRaWyMSTbH7ouxlOb0kt%2BkCcsmaI%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH7XPIAATTQEU6BDK4T7TKTPSXUNFANCNFSM4HI4AQ2A&data=01|01|darrenj%40microsoft.com|c0891f5cf999409083fa08d6cc079fef|72f988bf86f141af91ab2d7cd011db47|1&sdata=0eFk8xU9dMGAD8CeuZ2iKg1GDzeCI00kxcOheAB8GWI%3D&reserved=0.

Related to #1354

This was not reproducible on a Mac when I took #1354. There is a known defect within Electron's chromium that selects the first cert in the store which is not guaranteed to be the correct one. This may be related and if so, it is not a trivial fix.
@carlosscastro understood the problem and was looking into a possible fix a while back. I'll check with him to determine if a solution can be implemented.

Interesting, I only observed this issue coming back in the latest experimental build. Once I land I'll see if I can repro it working fine on the previous experimental build or perhaps something has changed on my machine that's caused the regression

@darrenj -
Try logging into the Emulator using File -> Sign in to Azure and then sign out using File -> Sign out. This should clear any session data that may be shared between Auth prompts and effectively "reset" the Emulator. Afterwards, try the OAuth card again. If you still see the behavior, shutdown the Emulator, remove Cookies and Cookies-journal from the C:\Users\<you>\AppData\Roaming\@bfemulator\main directory and try once more.
One of the paths above should solve the issue. If not, let me know and I'll continue to investigate...

Tested deleting the cookies/cookie/journal route and that resolved the issue. It stopped remembering any of the previous users and let me login using my selected account. As we explore options I wonder if the emulator might be best to have some form of "cookieless/icognitio-private" mode to help prevent the normally desirable caching/default selection of identity (SSO)

Closing this since there is an issue already tracking this, and a workaround exists.

authors: cwhitten darrenj justinwilaby tonyanziano

repo: Microsoft/BotFramework-Emulator


text:
Corrected diff selection process

This PR provides proper selection of the previous bot state when diffing.

Pull Request Test Coverage Report for Build 2484

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.795%

Totals

Change from base Build 2472:
0.0%

Covered Lines:
5245

Relevant Lines:
8680

💛  - Coveralls

authors: coveralls justinwilaby


text:
how to hide directLine secret, user and bot id..

Hi all,
referring to script below:

how to hide such info?
please help
..
thanks

For Direct Line secret, you will need to implement a server solution to exchange the secret into token. That's the only way to make sure the secret does not expose to the client.
For user ID, it is not able to hide. You should sign it to prevent forgery, this is very similar to how we usually handle user ID in HTTP cookies.
For bot ID, I need to double-check. But I think it is not sensitive so you should not need to hide it.

@compulim
Thanks for your reply!..
I am also looking for article how to implement server solution.. can you share it for me? and for the others that might need it..
thanks a lot in advance

You can find some of the token exchange/renewal code here. This repos is a Docker template we use to host both Bot.js and Web Chat on a single server.

authors: Primtek compulim

repo: Microsoft/BotFramework-WebChat


text:
JSRT APIs for Proxy

Currently target and handler as internal fields of JavascriptProxy.cpp and there is no way to retrieve them natively. Recently node started taking dependency on these fields natively. This breaks node on chakracore as chakracore doesn't have these fields exposed via JSRT. Additionally as per ES6 spec, there is no way to check if an object is a proxy or not.
This issue is to track adding below JSRT APIs

GetTargetOfProxy
GetHandlerOfProxy
IsProxy

@digitalinfinity is this still needed?

Yes, the v8 Proxy implementation in chakrashim is still just a stub

Do you want a PR for these? Looks easy enough.
My only questions would be:
a) whether they should really be 3 separate APIs?
b) what sort of test should be there for this functionality - particularly if it's 3 separate functions adding them as callable methods in ch may start bloating ch's API a bit

Maybe something like this:
JsGetProxy(_In_ JsValueRef proxyObject, _Out_ bool* isProxy, _Out_opt_ JsValueRef* Target, _Out_opt_ JsValueRef* Handler);

Do you want a PR for these?

Sure! Let's hash out what's needed first and how we will test it. I'd imagine a NativeTests addition for this would be part of it.

Options for the API:

One function:

JsGetProxyProperties(_In_ JsValueRef proxyObject,
           _Out_ bool* isProxy,
           _Out_opt_ JsValueRef* Target,
           _Out_opt_ JsValueRef* Handler);

Call it with a normal Proxy would output:
isProxy = true
And values for Target and Handler.
Call it with a revoked Proxy, would output:
isProxy = true
BUT nullptrs for Target and Handler
Call it with something that is not a proxy and you'd be given:
isProxy = false
And nullptrs for Target and Handler

two functions:
One for IsProxy - the other to get target and Handler.

All 3 functions separately.

Options for testing:

If done as one function could track it into ch and fire several tests at it from JS
If done as multiple APIs should probably have a native test rather than implementing multiple new APIs in ch for one thing

Thoughts?

I like the elegance of one function. Let's explore that first. I think it's probably fairly likely if they want to know Target they will also want to know Handler, and need to guard accessing those on whether the object is a proxy at all.
There's value in keeping the APIs lean and this will be an experimental API at first so we could provide fewer APIs at first  and go from there if there are perf concerns. If getting all the information has significantly more overhead and "all the info" is not the most common scenario in practice, then we can explore splitting up the API.
I can imagine this pattern being pretty common:
JsGetProxyProperties(obj, &isProxy, &target, &handler);
if (isProxy) { doSomethingWith(&target, &handler); }

And, for that reason, I vote that any such change go into release/1.9 unless we plan on making 1.10 very soon.

@jackhorton I was waiting on further comment before writing anything as the ask didn't seem quite fixed yet.
I'll have time to write the code this weekend if we can be sure what's wanted before then.

I agree with @dilijev about the design strategy. I don't think there will be a perf impact to get the target and handler, but also we could perhaps pass null for those if we don't want that information and are concerned about doing extra work.

Just a heads up chakra-node has shipped v10 so now beyond util.inspect() with showProxy not working there is also util.types.isProxy() which doesn't work either.

authors: digitalinfinity dilijev jackhorton jdalton kunalspathak rhuanjl

repo: Microsoft/ChakraCore


text:
WASM - api testing + bugfixes

This is a pretty big change as I had to do some refactoring to fix some issues with the WebAssembly.Module.imports api and a bug in reusing the same module for multiple instance with imported globals.
I took the opportunity to cleanup the global/imports code as well as the module environment in the instance.
Fixes #2033
Overview of the changes I made:

Throw a different error message if the element in the function table is null on call.
Throw a WebAssembly.RuntimeError  for exception thrown from the jitted code for Wasm functions
Throw in WebAssembly::ReadBufferSource if the buffer is empty and/or null since we assume the buffer is valid after that
Created the class WebAssemblyEnvironment to handle get/set elements in the module environment. This allows to do additional checks to avoid writing past the buffer limit.
The WasmGlobal objects are now immutable. This allows to re-instantiate the module with imported globals. The globals needs to be read from the WebAssemblyEnvironment for init_expr and local references
Some of the apis we use in WebAssemblyInstance::CreateInstance can throw a WasmCompilationException, for now I converted that exception to a TypeError. Related #2035
Insert all the imports type in the imports array in WebAssemblyModule. Treat all imports similarly to how we do exports in instantiate.
Fixes #2034

This change is

Reviewed 44 of 44 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

test/wasm/baselines/api.baseline, line 1 at r1 (raw file):

There are some unexpected results here that I hadn't seen before, I will reinvestigate that

Comments from Reviewable

@MikeHolman Can you review this please ?

:shipit:

@dotnet-bot test Ubuntu ubuntu_linux_debug_static please

authors: Cellule MikeHolman


text:
Filters

I created a framework for inserting filter graphs into Uncompressed sample providers and implemented an example audio filter class (which works out of the box).
You can pass filters using the configurations described in the link bellow by creating AvEffectDefinition objects
For example, you can insert an aecho effect like so
new AvEffectDefinition("aecho", "aecho=0.8:0.88:60:0.4")
Effects can be enabled or disabled during playback at will.
I have tested this branch a little, it has no obvious memory leaks or hard hitting errors.
I haven't done anything for videos yet (should be roughly similar to the existing AudioEffect class, but with different configurations for buffer source and resampler filter), and I am not sure if it is even possible for compressed samples.
https://ffmpeg.org/ffmpeg-filters.html#Audio-Filters
PS: I am not sure why the entire history of the repository is visible here, only the last 2 commits matter.
PS2: I know filters have several ways of initialization, but i find the string based approach the best, and it seems to work every time, and is easiest and most versatile to implement. The context options API doesn't seem to work every time. I only used it for the abuffer source because that filter has many options that would be harder to express as strings.

@mcosmin222 I know this problem. I solve it this way: Create a new clean branch, based off the branch where you want to merge (in this case, master). Checkout that branch, then use git bash: git merge --squash  ( could then be "lukasf/filters" or just a different branch in the same repo).

This was my mistake. The PR should have been in your parallel repo, not here. I guess the coxe was eager to come here :)

Oh ok I see :)

We can move over there :)

repo: Microsoft/FFmpegInterop


text:
Memory leak here?

Should we have to free the buf here, otherwise we will have a memory leak here?
https://github.com/Microsoft/GraphEngine/blob/3a83cba54f5d3d9b2cb1e6cf34670679a9dffcce/src/Trinity.Core/Network/Client/SynClient.Message.cs#L139
This buf will not be free if we recieved TrinityErrorCode.E_NETWORK_RECV_FAILURE
But, We allocate the buf in https://github.com/Microsoft/GraphEngine/blob/3045175cb39d4a439fae8bb1fbb060b030ee753b/src/Trinity.C/src/Network/Network.cpp#L480

hey @huoyao thanks for letting us know! I've taken a look, and yes you're right, that's a leak.

authors: huoyao yatli

repo: Microsoft/GraphEngine


text:
No trees in PMML file using pmml.py

I ran pmml.py and it yielded a xml file containing no trees.
Environment info
Operating System: OS X
CPU:
C++/Python/R version: Python 3.5
Reproducible examples
Booster text file from save_booster: https://gist.github.com/travisbrady/3408dedf1a8217a32eb859337b354648
Steps to reproduce

Create binary classifier using Python
Save booster
Run pmml.py

Output PMML
<PMML version="4.3"
        xmlns="http://www.dmg.org/PMML-4_3"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.dmg.org/PMML-4_3 http://dmg.org/pmml/v4-3/pmml-4-3.xsd">
    <Header copyright="Microsoft">
        <Application name="LightGBM"/>
    </Header>
    <DataDictionary numberOfFields="20">
        <DataField name="feat_5" optype="continuous" dataType="double"/>
        <DataField name="feat_20" optype="continuous" dataType="double"/>
        <DataField name="feat_11" optype="continuous" dataType="double"/>
        <DataField name="feat_4" optype="continuous" dataType="double"/>
        <DataField name="feat_16" optype="continuous" dataType="double"/>
        <DataField name="feat_14" optype="continuous" dataType="double"/>
        <DataField name="feat_3" optype="continuous" dataType="double"/>
        <DataField name="feat_0" optype="continuous" dataType="double"/>
        <DataField name="feat_7" optype="continuous" dataType="double"/>
        <DataField name="feat_13" optype="continuous" dataType="double"/>
        <DataField name="feat_1" optype="continuous" dataType="double"/>
        <DataField name="feat_6" optype="continuous" dataType="double"/>
        <DataField name="feat_17" optype="continuous" dataType="double"/>
        <DataField name="feat_8" optype="continuous" dataType="double"/>
        <DataField name="feat_15" optype="continuous" dataType="double"/>
        <DataField name="feat_12" optype="continuous" dataType="double"/>
        <DataField name="feat_18" optype="continuous" dataType="double"/>
        <DataField name="feat_19" optype="continuous" dataType="double"/>
        <DataField name="feat_2" optype="continuous" dataType="double"/>
        <DataField name="feat_9" optype="continuous" dataType="double"/>
    </DataDictionary>
    <MiningModel functionName="regression">
        <MiningSchema>
            <MiningField name="feat_5"/>
            <MiningField name="feat_20"/>
            <MiningField name="feat_11"/>
            <MiningField name="feat_4"/>
            <MiningField name="feat_16"/>
            <MiningField name="feat_14"/>
            <MiningField name="feat_3"/>
            <MiningField name="feat_0"/>
            <MiningField name="feat_7"/>
            <MiningField name="feat_13"/>
            <MiningField name="feat_1"/>
            <MiningField name="feat_6"/>
            <MiningField name="feat_17"/>
            <MiningField name="feat_8"/>
            <MiningField name="feat_15"/>
            <MiningField name="feat_12"/>
            <MiningField name="feat_18"/>
            <MiningField name="feat_19"/>
            <MiningField name="feat_2"/>
            <MiningField name="feat_9"/>
        </MiningSchema>
        <Segmentation multipleModelMethod="sum">
        </Segmentation>
    </MiningModel>
</PMML>

fixed in the latest commit.

authors: guolinke travisbrady

repo: Microsoft/LightGBM


text:
[R PACKAGE]doubt with lgb.importance and lgb.interprete

@guolinke
as said in syntax:
lgb.importance  -- Compute feature importance in a model
lgb.interprete -- Compute feature contribution for prediction
what's the difference between them indeed?? can u show me a simple example??
and which is the key part for feather selection?

Run the R manual doc examples to check the difference between both.

I think the feature importance is a statistic from the model file, and it is based on the split-gain on training data.
The "feature contribution for prediction" is using the validation data to verify the model. It can be used for the checking of over-fitting. e.g. if a feature have a large gain in training, but small gain in validation, that feature could be a bad feature that cause the over-fitting.
@yanyachen Is that right ?

The feature importance is the statistic for model performance on training data, it contains split-gain and split count.
the feature contribution is trying to explain the feature contribution for single row prediction. It's like "which feature drives this particular prediction by how far". Further detailed explanation can be found on here: http://blog.datadive.net/interpreting-random-forests/
I will send PR to refine documents and codes later. @guolinke

@guolinke
@yanyachen
lgb.interprete compute the contribution of each feather for predictions, it's a influence element. and it has positive and negative directions.  while, importance seems to be abs(interpretation)/sum(abs(interpretation))  which is as same as influence computing in linear regression.
Is this true ??

@zheguzai100 Just run the examples to check.
Interpretation is locally (by row), importance is globally (in general).
> tree_interpretation <- lgb.interprete(model, test$data, 1:5)
> str(tree_interpretation)
List of 5
 $ :Classes ‘data.table’ and 'data.frame':	6 obs. of  2 variables:
  ..$ Feature     : chr [1:6] "stalk-root=club" "odor=none" "bruises?=bruises" "cap-shape=bell" ...
  ..$ Contribution: num [1:6] -55.55 25.12 17.63 7.22 3.52 ...
  ..- attr(*, ".internal.selfref")=<externalptr>
 $ :Classes ‘data.table’ and 'data.frame':	13 obs. of  2 variables:
  ..$ Feature     : chr [1:13] "odor=none" "odor=anise" "stalk-root=club" "cap-color=pink" ...
  ..$ Contribution: num [1:13] 25.12 -17.67 7.62 -4.02 -3.81 ...
  ..- attr(*, ".internal.selfref")=<externalptr>
 $ :Classes ‘data.table’ and 'data.frame':	6 obs. of  2 variables:
  ..$ Feature     : chr [1:6] "stalk-root=club" "odor=none" "bruises?=bruises" "cap-shape=bell" ...
  ..$ Contribution: num [1:6] -55.55 25.12 17.63 7.22 3.38 ...
  ..- attr(*, ".internal.selfref")=<externalptr>
 $ :Classes ‘data.table’ and 'data.frame':	6 obs. of  2 variables:
  ..$ Feature     : chr [1:6] "stalk-root=club" "odor=none" "bruises?=bruises" "cap-shape=bell" ...
  ..$ Contribution: num [1:6] -55.55 25.12 17.63 7.22 3.52 ...
  ..- attr(*, ".internal.selfref")=<externalptr>
 $ :Classes ‘data.table’ and 'data.frame':	13 obs. of  2 variables:
  ..$ Feature     : chr [1:13] "odor=none" "bruises?=bruises" "cap-surface=fibrous" "stalk-surface-below-ring=smooth" ...
  ..$ Contribution: num [1:13] -33.29 8.23 6.9 5.1 3.67 ...
  ..- attr(*, ".internal.selfref")=<externalptr>

and the other one:
> tree_imp1 <- lgb.importance(model, percentage = TRUE)
> tree_imp2 <- lgb.importance(model, percentage = FALSE)
> str(tree_imp1)
Classes ‘data.table’ and 'data.frame':	41 obs. of  4 variables:
 $ Feature  : chr  "odor=none" "stalk-root=club" "stalk-root=rooted" "spore-print-color=green" ...
 $ Gain     : num  0.6168 0.178 0.0877 0.0312 0.0224 ...
 $ Cover    : num  0.2012 0.1142 0.1003 0.087 0.0961 ...
 $ Frequency: num  0.0613 0.0613 0.0613 0.0613 0.0675 ...
 - attr(*, ".internal.selfref")=<externalptr>
> str(tree_imp2)
Classes ‘data.table’ and 'data.frame':	41 obs. of  4 variables:
 $ Feature  : chr  "odor=none" "stalk-root=club" "stalk-root=rooted" "spore-print-color=green" ...
 $ Gain     : num  67465 19476 9589 3416 2453 ...
 $ Cover    : int  130260 73960 64960 56300 62218 12937 61040 55240 55197 765 ...
 $ Frequency: int  20 20 20 20 22 36 20 20 39 5 ...
 - attr(*, ".internal.selfref")=<externalptr>


text:
The results of lightgbm in linux and windows are inconsistent under the same version

Operating System:
linux: ubuntu 14.04
windows: windows2008 R2
Version：
2.0.4
Error Message:

Under the same configuration，the same trainset, the model of windows is different from linux
With two model to predict the same testset , There is a big difference between the results

"big difference?"
There are many possible reasons.
With different compilers, the result could be different. the main reason is the multi-threading and openmp executing order issues.
The python in the different platform also may cause the difference. you can exclude this reason by using CLI version.

authors: guolinke kbzhang


text:
Debugger doesn't stop for Step Into or Step Over

In VS2015 with 2.7.10, the Python debugger is working nicely in all but one regard: Using "step over" or "step into" is equivalent to pressing F5:  the program doesn't stop on the next line.  The only way to halt it at the next line is to set a break point.

Are you stepping through your own code? Or the standard library?
This is a known issue - specifically, we are not meant to be hitting breakpoints there unless you've set the Enable debugging of the standard library option - generally enabling this option makes it all work as expected (if you expect to be able to step through the standard library).
If this is occurring in your own code, we'd need to take a look at the actual code you're seeing it on and the callstack at the point where it is occurring.

It is my own code but the files live in the python folder.  Checking that checkbox addressed the issue.  Thank you Zooba!

authors: mkimberling zooba

repo: Microsoft/PTVS


text:
Intellisense issues and crashes with Python 2.7 in VS2017 Enterprise

I have recently installed VS2017 Enterprise at work. We not only use it for standard .NET dev but for Python too. Anyhow, whilst with previous VS versions I managed to make the Python intellisense work (DB refresh, trial-and-error and the rest), this time all I get is an error message and some encouraging words to report this issue on the issue tracker - so here it is:
My VS 2017 Enterprise version number is 15.8.2
This issue only happens if I try to use the Python2.7 under the standard ArcGIS installation path (C:\Python27\ArcGIS10.5) if I use the Python 3.6 (C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64) things seem working fine in the interactive window.
This problem did not exists neither in VS2013 nor VS2015...
Well - the prinout from the as follows:
`
[Window Title]
devenv.exe
[Main Instruction]
An unexpected error occurred
[Content]
Please press Ctrl+C to copy the contents of this dialog and report this error to our issue tracker.
[^] Hide details  [Close]
[Expanded Information]
Build: 15.8.18201.1

System.InvalidOperationException: Failed to initialize analyzer
   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<InitializeAsync>d__42.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<CreateForProjectAsync>d__34.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<CreateAnalyzerAsync>d__134.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<ReanalyzeProjectHelper>d__147.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<ReanalyzeProject>d__146.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Infrastructure.VSTaskExtensions.<HandleAllExceptions>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

`

Thanks!
This is a duplicate of #4660
This is fixed in 15.8.3, which will be released very soon (this week).

authors: huguesv tamasoz


text:
morley.csv

I want to create csv file for my dataset.

Hi @RobertMelvin, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

authors: RobertMelvin msftclas

repo: Microsoft/PowerBI-visuals


text:
Improve protocol to simplify remoting

Change protocol so that the type of every message (one-way notification, request, response) is encoded in the message name in a uniform way.
Rename associated APIs (send_message etc) for clarity.

Corresponding changes in R-Host coming shortly.

The purpose of this is to enable the broker to figure out how to handle the packet by only looking at its name (so all custom messages sent from e.g. R code do not need to be special-cased). With the change, there are three types of messages:
Notifications: !Foo
Requests: ?Foo
Responses: :Foo
So first character alone determines message type.
Also, I got rid of most special character names for the sake of clarity, keeping them only for those messages that constitute the bulk of the typical session: input prompts, evals, console output, and busy status reporting.

:+1:

repo: Microsoft/RTVS


text:
JavaScript Syntax Highlight: RegExp literals improperly parsed

From @zia-newversion on November 6, 2016 1:13

VSCode Version: 1.7.1 (02611b40b24c9df2726ad8b33f5ef5f67ac30b44)
OS Version: Linux Mint 17.2 (Ubuntu 14.04)

Steps to Reproduce:

In a JavaScript file, type a statement containing a division operation (/) followed by a RegExp literal (/.*/) as part of the same statement e.g. var v = (a / b).toString().match(/\d*(\.\d+)?/)
The code highlighter does not highlight the statement properly e.g. in the example provided in step 1, the code highlighter thinks that the / in a / b is where the RegExp literal /\d*(\.\d+)?/ starts from and highlights the whole / b).toString().match(/\d*(\.\d+)?/ part one RegExp literal.
The same behaviour does not exhibit if the RegExp precedes a division operator in a similar fashion, e.g. in the statement var v = parseFloat(s.match(/\d*(\.\d+)?/).toString(), 10) / 2.5, the same RegExp literal is highlighted properly.

Example: (recreated from the "Steps to Reproduce" section)

Another example: (this one is caught in the wild, free-range and organic)

Please forgive the obscene, blasphemic JavaScript in the above example(s?). The point is, it's syntactically valid. Also, in my experience, this did not happen before the recent VSCode upgrade to 1.7.1 so I'm presuming this relates to something that was changed in 1.7.1.
Copied from original issue: Microsoft/vscode#15051

This has been fixed by ca47120 and 9e936d2

authors: aeschli sheetalkamat

repo: Microsoft/TypeScript-TmLanguage


text:
Explicit type parameter breaks Index signature "inference"

TypeScript Version:  2.0.6 or nightly (2.2.0-dev.20161205)
Code
interface Obj<V> { [key: string]: V }

interface Bla {
  iAmABla: string
}

function doSomething(obj: Obj<Bla>) {
  return true
}

function doSomethingElse<T extends Obj<Bla>>(obj: T) {
  return true
}

interface ObjBla {
  a: { iAmABla: 'abc' },
  b: { iAmABla: 'def' }
}

const input = { a: { iAmABla: '' }, b: { iAmABla: '' } }

doSomething(input)
doSomethingElse<ObjBla>(input)

Expected behavior:
doSomethingElse should compile, as the passed input's type verifies the constraint.
In fact, both doSomething and doSomethingElse compile if the type parameter is not explicitely written by the developer (I need it in a more complex scenario where there are two other type parameters and requires me to provide them to lift ambiguities)
Actual behavior:
error TS2344: Type 'ObjBla' does not satisfy the constraint 'Obj'. Index signature is missing in type 'ObjBla'.
Of course there is the workaround of adding an index signature, but it's very annoying in my case as this function is used a lot. I think index signature inference was improved recently, looks like a corner case when a type parameter is explicit.

The index signature is exclusionary here because it implies the non-existence of other explicit properties. Consider something like this
interface Obj<V> { [key: string]: V }

interface Bla {
  iAmABla: string
}

function doSomething(obj: Obj<Bla>) {
  return true
}

function doSomethingElse<T extends Obj<Bla>>(obj: T) {
  return true
}

interface ObjBla {
  a: { iAmABla: 'abc' },
  b: { iAmABla: 'def' }
}
interface BetterObjBla extends ObjBla {
    somethingElse: string;
    anotherThing: number;
}

const input = { a: { iAmABla: '' }, b: { iAmABla: '' } }
const myBetterObj: BetterObjBla = { a: { iAmABla: 'abc' }, b: { iAmABla: 'def' }, somethingElse: 'oops', anotherThing: 34 };

let x: typeof input = myBetterObj

doSomething(input)
doSomethingElse<ObjBla>(x)

If doSomethingElse's implementation loops through the keys of its input (as would be expected based on its signature) and does things assuming the values from those keys conform to ObjBla, it's going to fail.
Index signatures get inferred in places where we can be reasonably sure that there aren't extra properties coming out of nowhere (e.g. object literals). For an arbitrary object reference, that's not a safe assumption.

I see!

authors: AlexGalays RyanCavanaugh

repo: Microsoft/TypeScript


text:
Promise<string | string[]> should be interchangable with type Promise | Promise<string[]>

TypeScript Version:  2.1.1 / nightly (2.2.0-dev.201xxxxx)
2.1.5
Code
Currently if, I expect a type 'Promise<string | string[]>' but got a type 'Promise | Promise<string[]>' the compiler will complain. I would expect the types to be interchangeable.

I would expect the types to be interchangeable.

This isn't correct. Without some justification for this statement I can't provide a meaningful counterexample.

I have correct the example - the formatted text got the wrong GitHub markup so it distorted the example. Is it better?

The formatting was good enough to know what you meant. These types just simply are not the same. One is not substitutable for the other. They are different. If you provide some reasoning or example of why you think they should be the same (this should be our default assumption since they're not identical) I could explain why that's not the case.

@mmc41
consider:
declare var x: (number | string)[];
declare var y: (number[]) | (string[]);
y = x; // <-- do you think you can do it?

oh, it's the other way around, then yes, it should work, @RyanCavanaugh please fix

indeed Promise<string[]> can be assigned to (a subtype of) Promise<(string | number)[]> being a special case of it (as long as we are structural), dying to see a counter example

@RyanCavanaugh can we get a counterexample or reopen it?

authors: RyanCavanaugh aleksey-bykov mmc41


text:
Overload on constants requires cast for resolution

Hi,
TS Version: 1.4
In the following the first call to doFoo fails to compile because the overload resolution algorithm picks the general case:
interface Bar {
    bar?: number;
    baz?: string;
}

interface Foo {
    foo(): string;
}

declare function doFoo(kind: 'Foo', bar?: Bar): Foo;
declare function doFoo(kind: string, bar: any): {}

var x = doFoo('Foo', { bar: 1 });
x.foo(); // Error: Property 'foo' does not exist on type '{}'.

var y = doFoo('Foo', <Bar> { bar: 1 });
y.foo(); // Okay

This is a breaking change because it used to work without the need for the cast in 1.3.
I feel this should compile because { bar: 1 } is compatible with the Bar interface.

Doesn't seem specific to string overloads. This has the potential to break a lot of scenarios.
declare function doFoo(bar?: { baz?: string; bar: number; }): string;
declare function doFoo(bar?: any): number;

var x = doFoo({ bar: 1 }); // x: number, should be x: string
x = 3; // should error

Bisected to https://github.com/Microsoft/TypeScript/commit/81eaae0afa37ff150456ccc058a153ebb0f0c428 from #919

@JsonFreeman @RyanCavanaugh @mhegazy I have a proposed fix for this in #1774.

Here is a similar case without any:
declare function doFoo(bar?: { bar: number; baz?: string; }): string;
declare function doFoo(bar?: { bar: number }): number;

var x = doFoo({ bar: 1 }); // x: number, should be x: string
x = 3; // should error

authors: JsonFreeman NoelAbrahams RyanCavanaugh ahejlsberg


text:
Building when path is a symbolic link doesn't work

I have C:\users\jhudson\dev -> E:\git (to get the development arena onto the mirrored drives)
Expected behavior:
typescript doesn't care if there's a symbolic link in the path to the current directory or not
Actual behavior:
The failing code was in a stock knockout pulled from node_modules.
declare module "knockout" { export = ko; }

would complain about duplicate symbol definition. We finally got the error to duplicate in Visual studio permitting us to notice what the problem was.
It imported C:\users\jhudson\dev<solutionname>\src<projectname>\node_modules@types\knockout\index.d.ts and E:\git<solutionname>\src<projectname>\node_modules@types\knockout\index.d.ts
Was thinking it was a problem with Visual Studio; discovered the problem will recur if a tsc command is issued from the command line from C:\users\jhudson\dev<solutionname>\src<projectname> but not
E:\git<solutionname>\src<projectname>.
Reproduced with tsc 2.3 and 2.5.
I don't even know typescript and can't figure out how to reduce this. I'm just working on a project that uses it.

I am really unable to piece together a repro from what you describe.. not sure where symlinks fit in this whole thing.
The only thing i can think of is you already have another definition of knockout in your project.. it could be in a local file, or it can be you have two dependencies that have two different versions of @types/knockout.  if it is the earlier, then remove that file from your compilation, if its the later, install a version of @types/knockout in your devdependencies, and that one should take priority.

I have a symbolic link above the build root. It included the same file twice resulting in it conflicting with itself.
Changing directory to use the symbolic link target rather than the symbolic link makes the build error go away.

does --preserveSymlinks solves the issue?

Ah, yes it does. Documentation fail. (The docs suggest it's for dealing with symbolic links within the project root that point out of it, which is not this case)

authors: jhudsoncedaron mhegazy