karths/binary-10IQR-defect · Datasets at Hugging Face

Unnamed: 0 int64 0 832k	id float64 2.49B 32.1B	type stringclasses 1 value	created_at stringlengths 19 19	repo stringlengths 5 112	repo_url stringlengths 34 141	action stringclasses 3 values	title stringlengths 1 757	labels stringlengths 4 664	body stringlengths 3 261k	index stringclasses 10 values	text_combine stringlengths 96 261k	label stringclasses 2 values	text stringlengths 96 232k	binary_label int64 0 1
22,539	4,817,559,919	IssuesEvent	2016-11-04 14:04:36	outcobra/outstanding-cobra	https://api.github.com/repos/outcobra/outstanding-cobra	opened	contributing guidelines are off	administration/documentation bug	The section [here](https://github.com/outcobra/outstanding-cobra/blob/develop/CONTRIBUTING.md#branches) is not quite right. I think the branches should be called by their actual names (as in `master`, `develop` and `feature/your-feature`).	1.0	contributing guidelines are off - The section [here](https://github.com/outcobra/outstanding-cobra/blob/develop/CONTRIBUTING.md#branches) is not quite right. I think the branches should be called by their actual names (as in `master`, `develop` and `feature/your-feature`).	non_defect	contributing guidelines are off the section is not quite right i think the branches should be called by their actual names as in master develop and feature your feature	0
20,774	3,413,990,381	IssuesEvent	2015-12-07 01:45:22	bounswe/bounswe2015group8	https://api.github.com/repos/bounswe/bounswe2015group8	closed	Post-Heritage Linking	Priority-Medium Type-Defect	Right now, we can relate a post to only one heritage. The users shall be able to link posts with other heritages. Implement a basic system in which they can accomplish that.	1.0	Post-Heritage Linking - Right now, we can relate a post to only one heritage. The users shall be able to link posts with other heritages. Implement a basic system in which they can accomplish that.	defect	post heritage linking right now we can relate a post to only one heritage the users shall be able to link posts with other heritages implement a basic system in which they can accomplish that	1
302,321	26,139,371,862	IssuesEvent	2022-12-29 16:11:24	DMTF/libspdm	https://api.github.com/repos/DMTF/libspdm	opened	Testing should be opt in	enhancement test	Now that there appears to be a class of Integrators who will be using libspdm as a real library and who don't care about running its unit and fuzz testing (for example https://github.com/altera-opensource/verifier), we should make testing opt in when CMake is invoked; ie `-DTEST=On`.	1.0	Testing should be opt in - Now that there appears to be a class of Integrators who will be using libspdm as a real library and who don't care about running its unit and fuzz testing (for example https://github.com/altera-opensource/verifier), we should make testing opt in when CMake is invoked; ie `-DTEST=On`.	non_defect	testing should be opt in now that there appears to be a class of integrators who will be using libspdm as a real library and who don t care about running its unit and fuzz testing for example we should make testing opt in when cmake is invoked ie dtest on	0
27,366	4,974,227,299	IssuesEvent	2016-12-06 05:19:39	rbei-etas/busmaster	https://api.github.com/repos/rbei-etas/busmaster	opened	Trace window shows unexpected messages while enabling node simulation after disabling it	1.3 patch (defect) 3.3 low priority (EC3)	1. Add a node and message hanlder to it And trace some messages inside the handler for LIN 2.Add the same frame and response in tx wnd 3.Transmit the messahe by disabling the nodes 4.Enable the nodes and and connect 5.Trace window is printing the trace messages which was added in the message handler [Issue is reproducible in V2.6.4]	1.0	Trace window shows unexpected messages while enabling node simulation after disabling it - 1. Add a node and message hanlder to it And trace some messages inside the handler for LIN 2.Add the same frame and response in tx wnd 3.Transmit the messahe by disabling the nodes 4.Enable the nodes and and connect 5.Trace window is printing the trace messages which was added in the message handler [Issue is reproducible in V2.6.4]	defect	trace window shows unexpected messages while enabling node simulation after disabling it add a node and message hanlder to it and trace some messages inside the handler for lin add the same frame and response in tx wnd transmit the messahe by disabling the nodes enable the nodes and and connect trace window is printing the trace messages which was added in the message handler	1
5,162	2,610,182,230	IssuesEvent	2015-02-26 18:58:06	chrsmith/quchuseban	https://api.github.com/repos/chrsmith/quchuseban	opened	剖析怎么去除脸上的色斑	auto-migrated Priority-Medium Type-Defect	``` 《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。</br> 　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� ��购了2套黛芙薇尔。</br> 　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊! 阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐�� 去掉吗? 　　答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新�� 客都是通过老顾客介绍而来，口碑由此而来! 　　2，服用黛芙薇尔美白，会伤身体吗?有副作用吗? 　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技�� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖! 　　3，去除黄褐斑之后，会反弹吗? 　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌!我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗? 　　4，你们的价格有点贵，能不能便宜一点? 　　答：如果您使用西药最少需要2000元，煎服的药最少需要3 000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　5，我适合用黛芙薇尔精华液吗? 　　答：黛芙薇尔适用人群：　　1、生理紊乱引起的黄褐斑人群　　2、生育引起的妊娠斑人群　　3、年纪增长引起的老年斑人群　　4、化妆品色素沉积、辐射斑人群　　5、长期日照引起的日晒斑人群　　6、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法 1、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。 2、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素A、B12、E，还含� ��、镁等23种矿物质，可调节人体的新陈代谢，止血止痛，消� ��安神。 ``` ----- Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 2:45	1.0	剖析怎么去除脸上的色斑 - ``` 《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。</br> 　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� ��购了2套黛芙薇尔。</br> 　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊! 阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐�� 去掉吗? 　　答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新�� 客都是通过老顾客介绍而来，口碑由此而来! 　　2，服用黛芙薇尔美白，会伤身体吗?有副作用吗? 　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技�� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖! 　　3，去除黄褐斑之后，会反弹吗? 　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌!我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗? 　　4，你们的价格有点贵，能不能便宜一点? 　　答：如果您使用西药最少需要2000元，煎服的药最少需要3 000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　5，我适合用黛芙薇尔精华液吗? 　　答：黛芙薇尔适用人群：　　1、生理紊乱引起的黄褐斑人群　　2、生育引起的妊娠斑人群　　3、年纪增长引起的老年斑人群　　4、化妆品色素沉积、辐射斑人群　　5、长期日照引起的日晒斑人群　　6、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法 1、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。 2、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素A、B12、E，还含� ��、镁等23种矿物质，可调节人体的新陈代谢，止血止痛，消� ��安神。 ``` ----- Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 2:45	defect	剖析怎么去除脸上的色斑《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� �� 。　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加， — 现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　黛芙薇尔精华液真的有效果吗真的可以把脸上的黄褐�� 去掉吗　　答：黛芙薇尔精华液dna精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，的新�� 客都是通过老顾客介绍而来，口碑由此而来　　，服用黛芙薇尔美白，会伤身体吗有副作用吗　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“dna美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作， �� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖　　，去除黄褐斑之后，会反弹吗　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗　　，你们的价格有点贵，能不能便宜一点　　答：，，，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　，我适合用黛芙薇尔精华液吗　　答：黛芙薇尔适用人群：　　、生理紊乱引起的黄褐斑人群　　、生育引起的妊娠斑人群　　、年纪增长引起的老年斑人群　　、化妆品色素沉积、辐射斑人群　　、长期日照引起的日晒斑人群　　、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素a、、e，还含� ��、，可调节人体的新陈代谢，止血止痛，消� ��安神。 original issue reported on code google com by additive gmail com on jul at	1
53,987	13,282,190,302	IssuesEvent	2020-08-23 21:24:27	Cockatrice/Cockatrice	https://api.github.com/repos/Cockatrice/Cockatrice	closed	tappedout.net deck analysis not working	Bug Defect - Basic	<b>System Information:</b> Client Version: 2.7.4 (2020-03-20) Client Operating System: Windows 10 (10.0) Build Architecture: 64-bit Qt Version: 5.12.6 System Locale: en_US Install Mode: Standard _______________________________________________________________________________________ Sending a deck to tappedout.net for analysis results in an invalid URL in the browser: `http://www.tappedout.nethttps//tappedout.net/mtg-decks/paste/` Tested with Firefox and Edge, and multiple decks. Relevant debug log entry: `Tappedout: good reply, http status 301 location "https://tappedout.net/mtg-decks/paste/"` Perhaps an issue with the redirection from http to https?	1.0	tappedout.net deck analysis not working - <b>System Information:</b> Client Version: 2.7.4 (2020-03-20) Client Operating System: Windows 10 (10.0) Build Architecture: 64-bit Qt Version: 5.12.6 System Locale: en_US Install Mode: Standard _______________________________________________________________________________________ Sending a deck to tappedout.net for analysis results in an invalid URL in the browser: `http://www.tappedout.nethttps//tappedout.net/mtg-decks/paste/` Tested with Firefox and Edge, and multiple decks. Relevant debug log entry: `Tappedout: good reply, http status 301 location "https://tappedout.net/mtg-decks/paste/"` Perhaps an issue with the redirection from http to https?	defect	tappedout net deck analysis not working system information client version client operating system windows build architecture bit qt version system locale en us install mode standard sending a deck to tappedout net for analysis results in an invalid url in the browser tested with firefox and edge and multiple decks relevant debug log entry tappedout good reply http status location perhaps an issue with the redirection from http to https	1
182,151	6,667,515,267	IssuesEvent	2017-10-03 12:53:48	spring-projects/spring-boot	https://api.github.com/repos/spring-projects/spring-boot	closed	Using multiple embedded databases requires a lot of manual configuration exclusions	priority: normal theme: datasource type: enhancement	<!-- Thanks for raising a Spring Boot issue. Please provide a brief description of your problem along with the version of Spring Boot that you are using. If possible, please also consider putting together a sample application that reproduces the issue. --> If multiple embedded `DataSources` are declared, one needs to explicitly disable the `DataSourceAutoConfiguration` and `DataSourceTransactionManagerAutoConfiguration` as can be seen [here](https://github.com/spring-projects/spring-data-examples/blob/master/jpa/multiple-datasources/src/main/java/example/springdata/jpa/multipleds/Application.java#L41). They fail as they rely on unique `DataSource` instances to be present. Can we let the simply opt out of being applied if multiple `DataSource`s are present?	1.0	Using multiple embedded databases requires a lot of manual configuration exclusions - <!-- Thanks for raising a Spring Boot issue. Please provide a brief description of your problem along with the version of Spring Boot that you are using. If possible, please also consider putting together a sample application that reproduces the issue. --> If multiple embedded `DataSources` are declared, one needs to explicitly disable the `DataSourceAutoConfiguration` and `DataSourceTransactionManagerAutoConfiguration` as can be seen [here](https://github.com/spring-projects/spring-data-examples/blob/master/jpa/multiple-datasources/src/main/java/example/springdata/jpa/multipleds/Application.java#L41). They fail as they rely on unique `DataSource` instances to be present. Can we let the simply opt out of being applied if multiple `DataSource`s are present?	non_defect	using multiple embedded databases requires a lot of manual configuration exclusions thanks for raising a spring boot issue please provide a brief description of your problem along with the version of spring boot that you are using if possible please also consider putting together a sample application that reproduces the issue if multiple embedded datasources are declared one needs to explicitly disable the datasourceautoconfiguration and datasourcetransactionmanagerautoconfiguration as can be seen they fail as they rely on unique datasource instances to be present can we let the simply opt out of being applied if multiple datasource s are present	0
74,058	24,922,623,189	IssuesEvent	2022-10-31 02:44:42	matrix-org/matrix-public-archive	https://api.github.com/repos/matrix-org/matrix-public-archive	opened	Don't change the URL as you scroll around	T-Defect A-archive-room-view	Even if we had https://github.com/matrix-org/matrix-public-archive/issues/72 to page-load the room with a stable URL, it still probably doesn't make sense to change the URL around as you scroll. The content on the page should be consistent with the URL. > ## UX problems > > ### One person's link will not look like the other once they start scrolling > > Because we change the URL as you scroll around. Someone may link a page expecting all the same messages to be there but it will actually only be the current day they're scrolled to plus whatever is above it. It will probably also affect how search engines index the site attributing messages with a certain URL that when visiting will be missing. --- I think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you're currently viewing in the surrounding context.	1.0	Don't change the URL as you scroll around - Even if we had https://github.com/matrix-org/matrix-public-archive/issues/72 to page-load the room with a stable URL, it still probably doesn't make sense to change the URL around as you scroll. The content on the page should be consistent with the URL. > ## UX problems > > ### One person's link will not look like the other once they start scrolling > > Because we change the URL as you scroll around. Someone may link a page expecting all the same messages to be there but it will actually only be the current day they're scrolled to plus whatever is above it. It will probably also affect how search engines index the site attributing messages with a certain URL that when visiting will be missing. --- I think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you're currently viewing in the surrounding context.	defect	don t change the url as you scroll around even if we had to page load the room with a stable url it still probably doesn t make sense to change the url around as you scroll the content on the page should be consistent with the url ux problems one person s link will not look like the other once they start scrolling because we change the url as you scroll around someone may link a page expecting all the same messages to be there but it will actually only be the current day they re scrolled to plus whatever is above it it will probably also affect how search engines index the site attributing messages with a certain url that when visiting will be missing i think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you re currently viewing in the surrounding context	1
44,439	12,157,618,061	IssuesEvent	2020-04-25 23:00:04	SarahAbigayle/SE310SE420FinalProjectNonGUI	https://api.github.com/repos/SarahAbigayle/SE310SE420FinalProjectNonGUI	closed	Remove “No journals. Create a journal?”	defect	File: MainActivity.java Line #: 31 This is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the GUI	1.0	Remove “No journals. Create a journal?” - File: MainActivity.java Line #: 31 This is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the GUI	defect	remove “no journals create a journal ” file mainactivity java line this is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the gui	1
3,146	2,607,985,572	IssuesEvent	2015-02-26 00:51:32	chrsmithdemos/zen-coding	https://api.github.com/repos/chrsmithdemos/zen-coding	closed	Direct shortcut for "wrap with abbreviation"	auto-migrated Priority-Medium Type-Defect	``` I use zen-coding with Eclipse. I really dislike the "wrap with abbreviation..." pop-up. 99% of the time I just want to wrap, requiring an additional keypress. There should be a separate shortcut for the pop-up, and one for directly wrapping the selected text block. ``` ----- Original issue reported on code.google.com by `poisonborz` on 20 Mar 2012 at 10:55	1.0	Direct shortcut for "wrap with abbreviation" - ``` I use zen-coding with Eclipse. I really dislike the "wrap with abbreviation..." pop-up. 99% of the time I just want to wrap, requiring an additional keypress. There should be a separate shortcut for the pop-up, and one for directly wrapping the selected text block. ``` ----- Original issue reported on code.google.com by `poisonborz` on 20 Mar 2012 at 10:55	defect	direct shortcut for wrap with abbreviation i use zen coding with eclipse i really dislike the wrap with abbreviation pop up of the time i just want to wrap requiring an additional keypress there should be a separate shortcut for the pop up and one for directly wrapping the selected text block original issue reported on code google com by poisonborz on mar at	1
4,238	2,610,089,902	IssuesEvent	2015-02-26 18:27:13	chrsmith/dsdsdaadf	https://api.github.com/repos/chrsmith/dsdsdaadf	opened	深圳痘痘在哪祛除	auto-migrated Priority-Medium Type-Defect	``` 深圳痘痘在哪祛除【深圳韩方科颜全国热线400-869-1818，24小时 QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:38	1.0	深圳痘痘在哪祛除 - ``` 深圳痘痘在哪祛除【深圳韩方科颜全国热线400-869-1818，24小时 QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:38	defect	深圳痘痘在哪祛除深圳痘痘在哪祛除【，】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 original issue reported on code google com by szft com on may at	1
37,808	8,365,389,070	IssuesEvent	2018-10-04 04:49:09	SkygearIO/features	https://api.github.com/repos/SkygearIO/features	opened	Support activity logging in server side	require/code require/spec vote/1	# Description Currently if user want to do activity logging for analytics, they can do in the lambda or handlers. But there is not way to log the skygear server build in functions like login, signup... etc. We need a feature to combine the logs for custom actions and skygear server build in functions. #### Possible approaches 1. Have events to plugins for skygear server build in functions, e.g. login, signup, reset password events...etc 2. Skygear server support logging, and have logging functions in cloud SDK. ## Scenario Put list of Scenario how developers will use this API # Portal Design Remove this section if the feature have no Portal # API Design Remove this section if the feature have no API # Open Questions Put a list of open questions here before a complete design / specification is decided # Related Issues - Server Issues - Client Issues - Guides Issues	1.0	Support activity logging in server side - # Description Currently if user want to do activity logging for analytics, they can do in the lambda or handlers. But there is not way to log the skygear server build in functions like login, signup... etc. We need a feature to combine the logs for custom actions and skygear server build in functions. #### Possible approaches 1. Have events to plugins for skygear server build in functions, e.g. login, signup, reset password events...etc 2. Skygear server support logging, and have logging functions in cloud SDK. ## Scenario Put list of Scenario how developers will use this API # Portal Design Remove this section if the feature have no Portal # API Design Remove this section if the feature have no API # Open Questions Put a list of open questions here before a complete design / specification is decided # Related Issues - Server Issues - Client Issues - Guides Issues	non_defect	support activity logging in server side description currently if user want to do activity logging for analytics they can do in the lambda or handlers but there is not way to log the skygear server build in functions like login signup etc we need a feature to combine the logs for custom actions and skygear server build in functions possible approaches have events to plugins for skygear server build in functions e g login signup reset password events etc skygear server support logging and have logging functions in cloud sdk scenario put list of scenario how developers will use this api portal design remove this section if the feature have no portal api design remove this section if the feature have no api open questions put a list of open questions here before a complete design specification is decided related issues server issues client issues guides issues	0
718,985	24,740,406,875	IssuesEvent	2022-10-21 04:16:06	brave/brave-browser	https://api.github.com/repos/brave/brave-browser	opened	Support ENS wildcard resolution Android implementation of #24430	priority/P3 QA/Yes release-notes/include feature/wallet OS/Android	Android version of #24430 > To complete support of ENS L2 https://github.com/brave/brave-browser/issues/22930 we also need support of wildcard resolution for ENS https://docs.ens.domains/ens-improvement-proposals/ensip-10-wildcard-resolution Associated PR: https://github.com/brave/brave-core/pull/15317 cc: @jamesmudgett @supermassive @Pavneet-Sing @SergeyZhukovsky	1.0	Support ENS wildcard resolution Android implementation of #24430 - Android version of #24430 > To complete support of ENS L2 https://github.com/brave/brave-browser/issues/22930 we also need support of wildcard resolution for ENS https://docs.ens.domains/ens-improvement-proposals/ensip-10-wildcard-resolution Associated PR: https://github.com/brave/brave-core/pull/15317 cc: @jamesmudgett @supermassive @Pavneet-Sing @SergeyZhukovsky	non_defect	support ens wildcard resolution android implementation of android version of to complete support of ens we also need support of wildcard resolution for ens associated pr cc jamesmudgett supermassive pavneet sing sergeyzhukovsky	0
16,156	9,696,244,529	IssuesEvent	2019-05-25 05:28:50	manusa/isotope-mail	https://api.github.com/repos/manusa/isotope-mail	reopened	Security alert: tar v2.2.1 (node-sass)	security technical	Node-sass v4.9.3 depends on tar v2.2.0 which has a security vulnerability ``` +-- node-sass@4.9.3 `-- node-gyp@3.8.0 `-- tar@2.2.1 ``` > CVE-2018-20834 More information > high severity > Vulnerable versions: < 4.4.2 > Patched version: 4.4.2 > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. Blocked by [sass/node-sass#2625]	True	Security alert: tar v2.2.1 (node-sass) - Node-sass v4.9.3 depends on tar v2.2.0 which has a security vulnerability ``` +-- node-sass@4.9.3 `-- node-gyp@3.8.0 `-- tar@2.2.1 ``` > CVE-2018-20834 More information > high severity > Vulnerable versions: < 4.4.2 > Patched version: 4.4.2 > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. Blocked by [sass/node-sass#2625]	non_defect	security alert tar node sass node sass depends on tar which has a security vulnerability node sass node gyp tar cve more information high severity vulnerable versions patched version a vulnerability was found in node tar before version an arbitrary file overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system in conjunction with a later plain file with the same name as the hardlink this plain file content replaces the existing file content blocked by	0
131,153	12,476,459,560	IssuesEvent	2020-05-29 13:30:58	F5Networks/k8s-bigip-ctlr	https://api.github.com/repos/F5Networks/k8s-bigip-ctlr	closed	Self-signed BIG-IP certificate resulted in as3 agent internal error	Awaiting response documentation	#### Setup Details CIS Version : 2.0 Build: f5networks/k8s-bigip-ctlr:latest BIGIP Version: Big IP 15.1.0.3 AS3 Version: 3.19.1 Agent Mode: AS3 Orchestration: K8S Orchestration Version: 1.18.2 Pool Mode: Cluster Additional Setup details: bare metal / flannel #### Description BIG-IP has self signed certificate. Unable to get the controller pod up and running. #### Steps To Reproduce Just deploy CIS version 2.0 and see the controller pod fails. Ensure that BIG-IP device certificate is self-signed. #### Expected Result Controller pod up and running regardless of whether BIG-IP device certificate is self-signed or not. #### Actual Result Logs are as follows: [root@km143 ~]# kn logs k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 2020/05/29 08:20:48 [INFO] [INIT] Starting: Container Ingress Services - Version: 2.0.0, BuildInfo: cloud-user-efcab9e-20200522033624 2020/05/29 08:20:48 [INFO] ConfigWriter started: 0xc00031e570 2020/05/29 08:20:48 [INFO] Started config driver sub-process at pid: 17 2020/05/29 08:20:48 [INFO] [INIT] Creating Agent for as3 2020/05/29 08:20:48 [INFO] [AS3] Initializing AS3 Agent 2020/05/29 08:20:48 [ERROR] [AS3] REST call error: Get https://172.28.22.148/mgmt/shared/appsvcs/info: x509: certificate signed by unknown authority 2020/05/29 08:20:48 [ERROR] [AS3] Internal Error 2020/05/29 08:20:48 [CRITICAL] [INIT] Failed to initialize as3 agent, Internal Error [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 0/1 CrashLoopBackOff 1 8s <snip> In an act of desperation, I downgraded to CIS to version 1.14: [root@km143 ~]# kn logs k8s-bigip-ctlr-669559c7d7-ph2bh 2020/05/29 08:52:04 [INFO] Starting: Version: 1.14.0, BuildInfo: n2285-661543171 2020/05/29 08:52:04 [INFO] ConfigWriter started: 0xc0003401b0 2020/05/29 08:52:04 [INFO] Started config driver sub-process at pid: 13 2020/05/29 08:52:06 [INFO] [2020-05-29 08:52:06,181 __main__ INFO] entering inotify loop to watch /tmp/k8s-bigip-ctlr.config589230808/config.json 2020/05/29 08:52:07 [INFO] Wrote 0 Virtual Server and 0 IApp configs 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3400 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3470 2020/05/29 08:52:07 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:52:07 [INFO] ProcessNodeUpdate: Change in Node state detected 2020/05/29 08:52:07 [INFO] NodePoller started: (0xc0009bf680) 2020/05/29 08:52:07 [INFO] Watching Ingress resources. 2020/05/29 08:52:07 [INFO] Watching ConfigMap resources. 2020/05/29 08:52:07 [INFO] Handling ConfigMap resource events. 2020/05/29 08:52:07 [INFO] Handling Ingress resource events. 2020/05/29 08:52:07 [INFO] Registered BigIP Metrics 2020/05/29 08:52:10 [INFO] [2020-05-29 08:52:10,996 f5_cccl.resource.resource INFO] Updating ApiFDBTunnel: /Common/flannel_ingress 2020/05/29 08:52:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:57:08 [ERROR] [AS3] REST call error: Post [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-669559c7d7-ph2bh 1/1 Running 0 10m <snip> #### Diagnostic Information #### Observations (if any)	1.0	Self-signed BIG-IP certificate resulted in as3 agent internal error - #### Setup Details CIS Version : 2.0 Build: f5networks/k8s-bigip-ctlr:latest BIGIP Version: Big IP 15.1.0.3 AS3 Version: 3.19.1 Agent Mode: AS3 Orchestration: K8S Orchestration Version: 1.18.2 Pool Mode: Cluster Additional Setup details: bare metal / flannel #### Description BIG-IP has self signed certificate. Unable to get the controller pod up and running. #### Steps To Reproduce Just deploy CIS version 2.0 and see the controller pod fails. Ensure that BIG-IP device certificate is self-signed. #### Expected Result Controller pod up and running regardless of whether BIG-IP device certificate is self-signed or not. #### Actual Result Logs are as follows: [root@km143 ~]# kn logs k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 2020/05/29 08:20:48 [INFO] [INIT] Starting: Container Ingress Services - Version: 2.0.0, BuildInfo: cloud-user-efcab9e-20200522033624 2020/05/29 08:20:48 [INFO] ConfigWriter started: 0xc00031e570 2020/05/29 08:20:48 [INFO] Started config driver sub-process at pid: 17 2020/05/29 08:20:48 [INFO] [INIT] Creating Agent for as3 2020/05/29 08:20:48 [INFO] [AS3] Initializing AS3 Agent 2020/05/29 08:20:48 [ERROR] [AS3] REST call error: Get https://172.28.22.148/mgmt/shared/appsvcs/info: x509: certificate signed by unknown authority 2020/05/29 08:20:48 [ERROR] [AS3] Internal Error 2020/05/29 08:20:48 [CRITICAL] [INIT] Failed to initialize as3 agent, Internal Error [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 0/1 CrashLoopBackOff 1 8s <snip> In an act of desperation, I downgraded to CIS to version 1.14: [root@km143 ~]# kn logs k8s-bigip-ctlr-669559c7d7-ph2bh 2020/05/29 08:52:04 [INFO] Starting: Version: 1.14.0, BuildInfo: n2285-661543171 2020/05/29 08:52:04 [INFO] ConfigWriter started: 0xc0003401b0 2020/05/29 08:52:04 [INFO] Started config driver sub-process at pid: 13 2020/05/29 08:52:06 [INFO] [2020-05-29 08:52:06,181 __main__ INFO] entering inotify loop to watch /tmp/k8s-bigip-ctlr.config589230808/config.json 2020/05/29 08:52:07 [INFO] Wrote 0 Virtual Server and 0 IApp configs 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3400 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3470 2020/05/29 08:52:07 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:52:07 [INFO] ProcessNodeUpdate: Change in Node state detected 2020/05/29 08:52:07 [INFO] NodePoller started: (0xc0009bf680) 2020/05/29 08:52:07 [INFO] Watching Ingress resources. 2020/05/29 08:52:07 [INFO] Watching ConfigMap resources. 2020/05/29 08:52:07 [INFO] Handling ConfigMap resource events. 2020/05/29 08:52:07 [INFO] Handling Ingress resource events. 2020/05/29 08:52:07 [INFO] Registered BigIP Metrics 2020/05/29 08:52:10 [INFO] [2020-05-29 08:52:10,996 f5_cccl.resource.resource INFO] Updating ApiFDBTunnel: /Common/flannel_ingress 2020/05/29 08:52:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:57:08 [ERROR] [AS3] REST call error: Post [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-669559c7d7-ph2bh 1/1 Running 0 10m <snip> #### Diagnostic Information #### Observations (if any)	non_defect	self signed big ip certificate resulted in agent internal error setup details cis version build bigip ctlr latest bigip version big ip version agent mode orchestration orchestration version pool mode cluster additional setup details bare metal flannel description big ip has self signed certificate unable to get the controller pod up and running steps to reproduce just deploy cis version and see the controller pod fails ensure that big ip device certificate is self signed expected result controller pod up and running regardless of whether big ip device certificate is self signed or not actual result logs are as follows kn logs bigip ctlr starting container ingress services version buildinfo cloud user configwriter started started config driver sub process at pid creating agent for initializing agent rest call error get certificate signed by unknown authority internal error failed to initialize agent internal error kn get pods name ready status restarts age bigip ctlr crashloopbackoff in an act of desperation i downgraded to cis to version kn logs bigip ctlr starting version buildinfo configwriter started started config driver sub process at pid entering inotify loop to watch tmp bigip ctlr config json wrote virtual server and iapp configs nodepoller registering new listener nodepoller registering new listener rest call error post certificate signed by unknown authority processnodeupdate change in node state detected nodepoller started watching ingress resources watching configmap resources handling configmap resource events handling ingress resource events registered bigip metrics updating apifdbtunnel common flannel ingress rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post kn get pods name ready status restarts age bigip ctlr running diagnostic information observations if any	0
53,253	13,261,260,070	IssuesEvent	2020-08-20 19:34:07	icecube-trac/tix4	https://api.github.com/repos/icecube-trac/tix4	closed	[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk (Trac #1049)	Migrated from Trac cmake defect	Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1049">https://code.icecube.wisc.edu/projects/icecube/ticket/1049</a>, reported by mamdayand owned by nega</em></summary> <p> ```json { "status": "closed", "changetime": "2019-01-11T23:56:01", "_ts": "1547250961636294", "description": "Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary", "reporter": "mamday", "cc": "david.schultz", "resolution": "fixed", "time": "2015-07-14T18:46:13", "component": "cmake", "summary": "[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk", "priority": "normal", "keywords": "tarball cmake simprod-scripts", "milestone": "", "owner": "nega", "type": "defect" } ``` </p> </details>	1.0	[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk (Trac #1049) - Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1049">https://code.icecube.wisc.edu/projects/icecube/ticket/1049</a>, reported by mamdayand owned by nega</em></summary> <p> ```json { "status": "closed", "changetime": "2019-01-11T23:56:01", "_ts": "1547250961636294", "description": "Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary", "reporter": "mamday", "cc": "david.schultz", "resolution": "fixed", "time": "2015-07-14T18:46:13", "component": "cmake", "summary": "[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk", "priority": "normal", "keywords": "tarball cmake simprod-scripts", "milestone": "", "owner": "nega", "type": "defect" } ``` </p> </details>	defect	running make production tarball make tarball doesn t make libgsl so in simulation trunk trac tested this a couple times with trunk of simulation running make install tool libs will install it but shouldn t be necessary migrated from json status closed changetime ts description tested this a couple times with trunk of simulation running make install tool libs will install it but shouldn t be necessary reporter mamday cc david schultz resolution fixed time component cmake summary running make production tarball make tarball doesn t make libgsl so in simulation trunk priority normal keywords tarball cmake simprod scripts milestone owner nega type defect	1
6,454	6,422,667,041	IssuesEvent	2017-08-09 09:03:22	openshiftio/appdev-documentation	https://api.github.com/repos/openshiftio/appdev-documentation	opened	cico_build_deploy.sh is undocumented	Bug Infrastructure	There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.	1.0	cico_build_deploy.sh is undocumented - There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.	non_defect	cico build deploy sh is undocumented there is currently no documentation of the cico build deploy sh script which can be used for running the server locally	0
79,290	28,086,294,891	IssuesEvent	2023-03-30 09:59:39	vector-im/element-android	https://api.github.com/repos/vector-im/element-android	closed	Maunium sticker picker loads indefinitely on new update	T-Defect A-Stickers S-Minor O-Occasional	### Steps to reproduce 1. Where are you starting? What can you see? Chat view 2. What do you click? Sticker button 3. More steps… N/A ### Outcome #### What did you expect? Sticker picker view loads and i can pick a sticker to send #### What happened instead? Indefinite loading of the sticker picker view. Works fine after downgrading to 1.5.11. Also, unrelated but I don't want to make another PR for this and it's technically not a bug: can you revert the image viewer to the pre-1.5.18 behaviour? What I mean is that when I open an image if I slide down on the image a little I used to be able to see the chat window and messages behind it but now it's blank and this means that whenever I view a video or photo file if I'm scrolled up in the chat after exiting the photo/video I'll immediately be jumped to the bottom and lose my position in the chat ### Your phone model Pixel 5a ### Operating system version Android 13.0 ### Application version and app store Element version 1.5.20, F-Droid ### Homeserver Synapse 1.75.0 ### Will you send logs? No ### Are you willing to provide a PR? No	1.0	Maunium sticker picker loads indefinitely on new update - ### Steps to reproduce 1. Where are you starting? What can you see? Chat view 2. What do you click? Sticker button 3. More steps… N/A ### Outcome #### What did you expect? Sticker picker view loads and i can pick a sticker to send #### What happened instead? Indefinite loading of the sticker picker view. Works fine after downgrading to 1.5.11. Also, unrelated but I don't want to make another PR for this and it's technically not a bug: can you revert the image viewer to the pre-1.5.18 behaviour? What I mean is that when I open an image if I slide down on the image a little I used to be able to see the chat window and messages behind it but now it's blank and this means that whenever I view a video or photo file if I'm scrolled up in the chat after exiting the photo/video I'll immediately be jumped to the bottom and lose my position in the chat ### Your phone model Pixel 5a ### Operating system version Android 13.0 ### Application version and app store Element version 1.5.20, F-Droid ### Homeserver Synapse 1.75.0 ### Will you send logs? No ### Are you willing to provide a PR? No	defect	maunium sticker picker loads indefinitely on new update steps to reproduce where are you starting what can you see chat view what do you click sticker button more steps… n a outcome what did you expect sticker picker view loads and i can pick a sticker to send what happened instead indefinite loading of the sticker picker view works fine after downgrading to also unrelated but i don t want to make another pr for this and it s technically not a bug can you revert the image viewer to the pre behaviour what i mean is that when i open an image if i slide down on the image a little i used to be able to see the chat window and messages behind it but now it s blank and this means that whenever i view a video or photo file if i m scrolled up in the chat after exiting the photo video i ll immediately be jumped to the bottom and lose my position in the chat your phone model pixel operating system version android application version and app store element version f droid homeserver synapse will you send logs no are you willing to provide a pr no	1
622,907	19,658,613,618	IssuesEvent	2022-01-10 14:57:11	threefoldtech/tfchain	https://api.github.com/repos/threefoldtech/tfchain	closed	Move pallets from tfchain_pallets to this repo	priority_major type_feature	Currently issue and releasemgmt is a mess. While almost all functionality resides in tfchain_pallets, they are combined and released in tfchain resulting in git commit history with "chore: bump dependencies and spec version".	1.0	Move pallets from tfchain_pallets to this repo - Currently issue and releasemgmt is a mess. While almost all functionality resides in tfchain_pallets, they are combined and released in tfchain resulting in git commit history with "chore: bump dependencies and spec version".	non_defect	move pallets from tfchain pallets to this repo currently issue and releasemgmt is a mess while almost all functionality resides in tfchain pallets they are combined and released in tfchain resulting in git commit history with chore bump dependencies and spec version	0
52,890	13,225,206,072	IssuesEvent	2020-08-17 20:42:16	icecube-trac/tix4	https://api.github.com/repos/icecube-trac/tix4	closed	make tarball copying error in install_shlib.pl (Trac #535)	Migrated from Trac cmake defect	When running 'make tarball' errors like this one appear: "Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74" The reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute. <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/535">https://code.icecube.wisc.edu/projects/icecube/ticket/535</a>, reported by henjoh@physto.seand owned by troy</em></summary> <p> ```json { "status": "closed", "changetime": "2009-07-23T13:45:14", "_ts": "1248356714000000", "description": "When running 'make tarball' errors like this one appear:\n\"Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74\"\n\nThe reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute.\n", "reporter": "henjoh@physto.se", "cc": "", "resolution": "duplicate", "time": "2009-02-16T20:06:18", "component": "cmake", "summary": "make tarball copying error in install_shlib.pl", "priority": "normal", "keywords": "install_shlib.pl", "milestone": "", "owner": "troy", "type": "defect" } ``` </p> </details>	1.0	make tarball copying error in install_shlib.pl (Trac #535) - When running 'make tarball' errors like this one appear: "Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74" The reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute. <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/535">https://code.icecube.wisc.edu/projects/icecube/ticket/535</a>, reported by henjoh@physto.seand owned by troy</em></summary> <p> ```json { "status": "closed", "changetime": "2009-07-23T13:45:14", "_ts": "1248356714000000", "description": "When running 'make tarball' errors like this one appear:\n\"Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74\"\n\nThe reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute.\n", "reporter": "henjoh@physto.se", "cc": "", "resolution": "duplicate", "time": "2009-02-16T20:06:18", "component": "cmake", "summary": "make tarball copying error in install_shlib.pl", "priority": "normal", "keywords": "install_shlib.pl", "milestone": "", "owner": "troy", "type": "defect" } ``` </p> </details>	defect	make tarball copying error in install shlib pl trac when running make tarball errors like this one appear couldn t copy lap ports root lib lap ports var db dports software root lap ports root lib libcore so to simulation candidates linux gcc lib tools no such file or directory at scratch scratch meta project src cmake install shlib pl line the reason seems to be that if the src variable in install shlib pl is a symbolic link it is assumed to be a relative link while it might be absolute migrated from json status closed changetime ts description when running make tarball errors like this one appear n couldn t copy lap ports root lib lap ports var db dports software root lap ports root lib libcore so to simulation candidates linux gcc lib tools no such file or directory at scratch scratch meta project src cmake install shlib pl line n nthe reason seems to be that if the src variable in install shlib pl is a symbolic link it is assumed to be a relative link while it might be absolute n reporter henjoh physto se cc resolution duplicate time component cmake summary make tarball copying error in install shlib pl priority normal keywords install shlib pl milestone owner troy type defect	1
74,810	25,339,080,007	IssuesEvent	2022-11-18 19:38:39	openzfs/zfs	https://api.github.com/repos/openzfs/zfs	closed	per dataset large_block feature detection not reliable when sending raw encrypted large block ds	Type: Defect Component: Send/Recv Component: Encryption	Tests for https://github.com/openzfs/zfs/pull/9372 have revealed what seems to be a bug (race ?) with the `large_blocks` zpool feature. If we have a raw send of an encrypted dataset with large blocks present the send often fails with `warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported` message even though the dataset in question has large block and has the feature active. This behavior is not consistent and re-running the same test sometimes does pass and sometimes does not. ### System information This is seen on the tip of master ### Describe the problem you're observing Sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn't. A failure looks like: ``` 20:49:46.93 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:47.28 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:47.31 warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported 20:49:47.31 ERROR: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup exited 1 ``` When the same test succeeds it looks like: ``` 20:49:57.12 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:57.48 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:57.51 SUCCESS: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup ``` I spend a little time debugging this and noticed that https://github.com/openzfs/zfs/blob/master/module/zfs/dmu_send.c#L1019-L1020 doesn't always have `dsc_featureflags` set correctly. If you run with this patch ``` diff --git a/module/zfs/dmu_send.c b/module/zfs/dmu_send.c index 5e6ced2bb..b70002361 100644 --- a/module/zfs/dmu_send.c +++ b/module/zfs/dmu_send.c @@ -1965,8 +1965,9 @@ setup_featureflags(struct dmu_send_params dspp, objset_t os, #endif /* raw sends imply large_block_ok / - if ((dspp->rawok \|\| dspp->large_block_ok) && - dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) { + if (dspp->rawok \|\| dspp->large_block_ok) { + zfs_dbgmsg("%d",(dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS))); + if (dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) featureflags \|= DMU_BACKUP_FEATURE_LARGE_BLOCKS; } ``` You can see that `dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)` is not reliable and will sometime return 0 and other times return 1. I also noticed that the dataset object passed to `load_zfeature()` seems to be different for passing vs not passing tests. ### Describe how to reproduce the problem Here is the minimal zfs-test I used to recreate the problem: ``` #!/bin/ksh -p . $STF_SUITE/include/libtest.shlib verify_runnable "both" DISK=${DISKS%% *} backup=$TEST_BASE_DIR/backup raw_backup=$TEST_BASE_DIR/raw_backup function cleanup { log_must rm -f $backup $raw_backup $ibackup $unc_backup log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f $TESTPOOL $DISK } log_onexit cleanup typeset passphrase="password" typeset file="/$TESTPOOL/$TESTFS1/$TESTFILE0" log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f -o feature@head_errlog=disabled \ -o feature@large_blocks=enabled $TESTPOOL $DISK log_must eval "echo $passphrase > /$TESTPOOL/pwd" log_must zfs create -o recordsize=1m -o primarycache=none \ -o atime=off -o compression=lz4 $TESTPOOL/$TESTFS1 log_must dd if=/dev/urandom of=$file bs=1024 count=1024 oflag=sync log_must zfs snapshot $TESTPOOL/$TESTFS1@snap1 log_must eval "zfs send -L $TESTPOOL/$TESTFS1@snap1 > $backup" log_must eval "zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase \ -o keylocation=file:///$TESTPOOL/pwd -o primarycache=none \ -o recordsize=1m $TESTPOOL/testfs5 < $backup" log_must eval "zfs send --raw $TESTPOOL/testfs5@snap1 > $raw_backup" ```	1.0	per dataset large_block feature detection not reliable when sending raw encrypted large block ds - Tests for https://github.com/openzfs/zfs/pull/9372 have revealed what seems to be a bug (race ?) with the `large_blocks` zpool feature. If we have a raw send of an encrypted dataset with large blocks present the send often fails with `warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported` message even though the dataset in question has large block and has the feature active. This behavior is not consistent and re-running the same test sometimes does pass and sometimes does not. ### System information This is seen on the tip of master ### Describe the problem you're observing Sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn't. A failure looks like: ``` 20:49:46.93 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:47.28 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:47.31 warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported 20:49:47.31 ERROR: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup exited 1 ``` When the same test succeeds it looks like: ``` 20:49:57.12 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:57.48 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:57.51 SUCCESS: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup ``` I spend a little time debugging this and noticed that https://github.com/openzfs/zfs/blob/master/module/zfs/dmu_send.c#L1019-L1020 doesn't always have `dsc_featureflags` set correctly. If you run with this patch ``` diff --git a/module/zfs/dmu_send.c b/module/zfs/dmu_send.c index 5e6ced2bb..b70002361 100644 --- a/module/zfs/dmu_send.c +++ b/module/zfs/dmu_send.c @@ -1965,8 +1965,9 @@ setup_featureflags(struct dmu_send_params dspp, objset_t os, #endif /* raw sends imply large_block_ok / - if ((dspp->rawok \|\| dspp->large_block_ok) && - dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) { + if (dspp->rawok \|\| dspp->large_block_ok) { + zfs_dbgmsg("%d",(dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS))); + if (dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) featureflags \|= DMU_BACKUP_FEATURE_LARGE_BLOCKS; } ``` You can see that `dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)` is not reliable and will sometime return 0 and other times return 1. I also noticed that the dataset object passed to `load_zfeature()` seems to be different for passing vs not passing tests. ### Describe how to reproduce the problem Here is the minimal zfs-test I used to recreate the problem: ``` #!/bin/ksh -p . $STF_SUITE/include/libtest.shlib verify_runnable "both" DISK=${DISKS%% *} backup=$TEST_BASE_DIR/backup raw_backup=$TEST_BASE_DIR/raw_backup function cleanup { log_must rm -f $backup $raw_backup $ibackup $unc_backup log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f $TESTPOOL $DISK } log_onexit cleanup typeset passphrase="password" typeset file="/$TESTPOOL/$TESTFS1/$TESTFILE0" log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f -o feature@head_errlog=disabled \ -o feature@large_blocks=enabled $TESTPOOL $DISK log_must eval "echo $passphrase > /$TESTPOOL/pwd" log_must zfs create -o recordsize=1m -o primarycache=none \ -o atime=off -o compression=lz4 $TESTPOOL/$TESTFS1 log_must dd if=/dev/urandom of=$file bs=1024 count=1024 oflag=sync log_must zfs snapshot $TESTPOOL/$TESTFS1@snap1 log_must eval "zfs send -L $TESTPOOL/$TESTFS1@snap1 > $backup" log_must eval "zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase \ -o keylocation=file:///$TESTPOOL/pwd -o primarycache=none \ -o recordsize=1m $TESTPOOL/testfs5 < $backup" log_must eval "zfs send --raw $TESTPOOL/testfs5@snap1 > $raw_backup" ```	defect	per dataset large block feature detection not reliable when sending raw encrypted large block ds tests for have revealed what seems to be a bug race with the large blocks zpool feature if we have a raw send of an encrypted dataset with large blocks present the send often fails with warning cannot send testpool large blocks detected but large blocks feature is inactive raw send unsupported message even though the dataset in question has large block and has the feature active this behavior is not consistent and re running the same test sometimes does pass and sometimes does not system information this is seen on the tip of master describe the problem you re observing sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn t a failure looks like success eval zfs send l testpool var tmp backup success eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool var tmp backup warning cannot send testpool large blocks detected but large blocks feature is inactive raw send unsupported error eval zfs send raw testpool var tmp raw backup exited when the same test succeeds it looks like success eval zfs send l testpool var tmp backup success eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool var tmp backup success eval zfs send raw testpool var tmp raw backup i spend a little time debugging this and noticed that doesn t always have dsc featureflags set correctly if you run with this patch diff git a module zfs dmu send c b module zfs dmu send c index a module zfs dmu send c b module zfs dmu send c setup featureflags struct dmu send params dspp objset t os endif raw sends imply large block ok if dspp rawok dspp large block ok dsl dataset feature is active to ds spa feature large blocks if dspp rawok dspp large block ok zfs dbgmsg d dsl dataset feature is active to ds spa feature large blocks if dsl dataset feature is active to ds spa feature large blocks featureflags dmu backup feature large blocks you can see that dsl dataset feature is active to ds spa feature large blocks is not reliable and will sometime return and other times return i also noticed that the dataset object passed to load zfeature seems to be different for passing vs not passing tests describe how to reproduce the problem here is the minimal zfs test i used to recreate the problem bin ksh p stf suite include libtest shlib verify runnable both disk disks backup test base dir backup raw backup test base dir raw backup function cleanup log must rm f backup raw backup ibackup unc backup log must eval poolexists testpool destroy pool testpool log must zpool create f testpool disk log onexit cleanup typeset passphrase password typeset file testpool log must eval poolexists testpool destroy pool testpool log must zpool create f o feature head errlog disabled o feature large blocks enabled testpool disk log must eval echo passphrase testpool pwd log must zfs create o recordsize o primarycache none o atime off o compression testpool log must dd if dev urandom of file bs count oflag sync log must zfs snapshot testpool log must eval zfs send l testpool backup log must eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool backup log must eval zfs send raw testpool raw backup	1
30,259	8,507,451,633	IssuesEvent	2018-10-30 19:06:32	hashicorp/packer	https://api.github.com/repos/hashicorp/packer	closed	Remote ESXi builder failing on retrieving VM ip. ESXi 6.0, packer 1.0	builder/vmware-esxi question waiting-reply	I'm using a ESXi 6.0 host for testing packer and I've been trying to get the vmware-iso remote ESXi builder to work. With packer 1.0. I get to the point where packer tries to retrieve the guest IP with "esxcli --formatter csv network vm port list -w #######" but errors out saying it cannot find the ip. Packer log: ``` 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Using internal plugin for vmware-vmx 2017/06/15 08:41:00 Using internal plugin for hyperv-iso 2017/06/15 08:41:00 Using internal plugin for virtualbox-iso 2017/06/15 08:41:00 Using internal plugin for amazon-instance 2017/06/15 08:41:00 Using internal plugin for digitalocean 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for oneandone 2017/06/15 08:41:00 Using internal plugin for openstack 2017/06/15 08:41:00 Using internal plugin for parallels-iso 2017/06/15 08:41:00 Using internal plugin for amazon-ebs 2017/06/15 08:41:00 Using internal plugin for amazon-ebsvolume 2017/06/15 08:41:00 Using internal plugin for null 2017/06/15 08:41:00 Using internal plugin for profitbricks 2017/06/15 08:41:00 Using internal plugin for cloudstack 2017/06/15 08:41:00 Using internal plugin for googlecompute 2017/06/15 08:41:00 Using internal plugin for azure-arm 2017/06/15 08:41:00 Using internal plugin for docker 2017/06/15 08:41:00 Using internal plugin for parallels-pvm 2017/06/15 08:41:00 Using internal plugin for qemu 2017/06/15 08:41:00 Using internal plugin for triton 2017/06/15 08:41:00 Using internal plugin for virtualbox-ovf 2017/06/15 08:41:00 Using internal plugin for amazon-chroot 2017/06/15 08:41:00 Using internal plugin for amazon-ebssurrogate 2017/06/15 08:41:00 Using internal plugin for vmware-iso 2017/06/15 08:41:00 Using internal plugin for converge 2017/06/15 08:41:00 Using internal plugin for salt-masterless 2017/06/15 08:41:00 Using internal plugin for chef-client 2017/06/15 08:41:00 Using internal plugin for chef-solo 2017/06/15 08:41:00 Using internal plugin for shell 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for ansible-local 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for puppet-masterless 2017/06/15 08:41:00 Using internal plugin for puppet-server 2017/06/15 08:41:00 Using internal plugin for ansible 2017/06/15 08:41:00 Using internal plugin for powershell 2017/06/15 08:41:00 Using internal plugin for windows-restart 2017/06/15 08:41:00 Using internal plugin for windows-shell 2017/06/15 08:41:00 Using internal plugin for checksum 2017/06/15 08:41:00 Using internal plugin for docker-save 2017/06/15 08:41:00 Using internal plugin for docker-tag 2017/06/15 08:41:00 Using internal plugin for atlas 2017/06/15 08:41:00 Using internal plugin for manifest 2017/06/15 08:41:00 Using internal plugin for compress 2017/06/15 08:41:00 Using internal plugin for googlecompute-export 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for vagrant-cloud 2017/06/15 08:41:00 Using internal plugin for vsphere 2017/06/15 08:41:00 Using internal plugin for docker-import 2017/06/15 08:41:00 Using internal plugin for artifice 2017/06/15 08:41:00 Using internal plugin for docker-push 2017/06/15 08:41:00 Using internal plugin for vagrant 2017/06/15 08:41:00 Using internal plugin for amazon-import 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[null:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null googlecompute:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute qemu:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu virtualbox-ovf:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf amazon-chroot:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot vmware-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso amazon-ebsvolume:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume digitalocean:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file oneandone:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone parallels-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso amazon-ebs:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs cloudstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack parallels-pvm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm vmware-vmx:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx virtualbox-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-instance:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance azure-arm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm triton:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton amazon-ebssurrogate:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate hyperv-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso profitbricks:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks docker:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker openstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack] PostProcessors:map[docker-save:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save docker-tag:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag atlas:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-atlas manifest:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local vagrant-cloud:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud checksum:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum artifice:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice vagrant:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant amazon-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import compress:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress vsphere:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere docker-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import docker-push:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push googlecompute-export:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export] Provisioners:map[ansible:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible powershell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell converge:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local puppet-server:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server chef-solo:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file windows-restart:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart puppet-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless salt-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-client:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client ansible-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local]} 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 Loading builder: vmware-iso 2017/06/15 08:41:00 Plugin could not be found. Checking same directory as executable. 2017/06/15 08:41:00 Current exe path: /usr/local/bin/packer 2017/06/15 08:41:00 Creating plugin client for path: /usr/local/bin/packer 2017/06/15 08:41:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-builder-vmware-iso"} 2017/06/15 08:41:00 Waiting for RPC address for: /usr/local/bin/packer 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 args: []string{"packer-builder-vmware-iso"} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin minimum port: 10000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin maximum port: 25000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin address: unix /tmp/packer-plugin255655097 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Waiting for connection... 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Serving a plugin connection... 2017/06/15 08:41:00 ui: [1;32mvmware-iso output will be in this color.[0m 2017/06/15 08:41:00 ui: 2017/06/15 08:41:00 Build debug mode: false 2017/06/15 08:41:00 Force build: false 2017/06/15 08:41:00 On error: 2017/06/15 08:41:00 Preparing build: vmware-iso 2017/06/15 08:41:00 Waiting on builds to complete... 2017/06/15 08:41:00 Starting build run: vmware-iso 2017/06/15 08:41:00 Running builder: vmware-iso 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 reconnecting to TCP connection for SSH 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 handshaking with SSH 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Question 1: Password: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 handshake complete! 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 [INFO] no local agent socket, will not connect agent 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system version get 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Connected to VMware ESXi 6.0.0 Releasebuild-3620759 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system settings advanced list -o /Net/GuestIPHack 2017/06/15 08:41:02 ui: [1;32m==> vmware-iso: Downloading or copying ISO[0m 2017/06/15 08:41:02 ui: [0;32m vmware-iso: Downloading or copying: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso[0m 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Acquiring lock to download: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Verifying checksum of /home/git/chief-masterhost/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 [DEBUG] Initial checksum matched, no download needed. 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: test -e /vmfs/volumes/*/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote command exited with '1': test -e /vmfs/volumes//ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/GB/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 No floppy files specified. Floppy disk will not be made. 2017/06/15 08:41:14 ui: [1;32m==> vmware-iso: Uploading ISO to remote machine...[0m 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote uploading: /home/git//ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/GB/packer_cache 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Verifying checksum of /vmfs/volumes/GB/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: sha256sum -c 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 Initial checksum matched, no upload needed. 2017/06/15 08:41:50 ui: [1;32m==> vmware-iso: Creating virtual machine disk[0m 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 opening new ssh session 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 starting remote command: vmkfstools -c 7000M -d zeroedthick -a lsilogic /vmfs/volumes/GB/ubuntu/output-vmware-iso/disk.vmdk 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Building and writing VMX file[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'memsize' = '512' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'cpuid.coresPerSocket' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.present' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.startConnected' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.virtualDev' = 'e1000' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'RemoteDisplay.vnc.webSocket.port' = '5900' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.networkName' = '' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'numvcpus' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Suppressing messages in VMX 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying port: 8446 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Starting HTTP server on port 8446[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Looking for available port between 5900 and 6000 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 starting remote command: esxcli --formatter csv network ip connection list 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5989, port 5989 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:8889, port 8889 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address fe80:2::207:e9ff:fe5a:7c5f:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8000, port 8000 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8100, port 8100 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8300, port 8300 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:2233, port 2233 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5900 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5901 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying address: ... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Found available VNC port: 5902 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Registering remote VM...[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Starting remote scp process: scp -vt /vmfs/volumes/GB/ubuntu/output-vmware-iso 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Started SCP session, beginning transfers... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Copying input data into temporary file so we can read the length 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 [DEBUG] scp: Uploading ubuntu.vmx: perms=C0644 size=2501 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 SCP session complete, closing stdin pipe. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 Waiting for SSH session to complete. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 scp stderr (length 28): Sink: C0644 2501 ubuntu.vmx 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd solo/registervm /vmfs/volumes/GB/ubuntu/output-vmware-iso/ubuntu.vmx 2017/06/15 08:41:52 ui: [1;32m==> vmware-iso: Starting virtual machine...[0m 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd vmsvc/power.on 77 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 opening new ssh session 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 starting remote command: vim-cmd vmsvc/power.getstate 77 2017/06/15 08:41:54 ui: [1;32m==> vmware-iso: Waiting 10s for boot...[0m 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Connecting to VM via VNC[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Connected to VNC desktop: ubuntu 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Host IP for the VMware machine: ** 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Typing the boot command over VNC...[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:05 packer: 2017/06/15 08:42:05 Special code '<f6>' found, replacing with: 65475 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<esc>' found, replacing with: 65307 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:22 packer: 2017/06/15 08:42:22 Sending char '/', code 47, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'i', code 105, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'n', code 110, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 's', code 115, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 't', code 116, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'a', code 97, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char '/', code 47, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'v', code 118, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'm', code 109, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'l', code 108, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'i', code 105, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'n', code 110, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'u', code 117, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'z', code 122, shift false 2017/06/15 08:42:26 packer: 2017/06/15 08:42:26 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char ' ', code 32, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'a', code 97, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'u', code 117, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 't', code 116, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'o', code 111, shift false 2017/06/15 08:42:28 packer: 2017/06/15 08:42:28 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char ' ', code 32, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'c', code 99, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'o', code 111, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'n', code 110, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 's', code 115, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'o', code 111, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'l', code 108, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'e', code 101, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char '-', code 45, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 's', code 115, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'e', code 101, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 't', code 116, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'u', code 117, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'p', code 112, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char '/', code 47, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'a', code 97, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 's', code 115, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'k', code 107, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char '_', code 95, shift true 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'd', code 100, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 't', code 116, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'c', code 99, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 't', code 116, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char '=', code 61, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'f', code 102, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'a', code 97, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'l', code 108, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 's', code 115, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 'e', code 101, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char ' ', code 32, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'c', code 99, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'n', code 110, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 's', code 115, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'l', code 108, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char '-', code 45, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 's', code 115, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 't', code 116, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'u', code 117, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'p', code 112, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char '/', code 47, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'l', code 108, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'a', code 97, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'y', code 121, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'u', code 117, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 't', code 116, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'c', code 99, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'd', code 100, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'e', code 101, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char '=', code 61, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'u', code 117, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 's', code 115, shift false 2017/06/15 08:42:42 packer: 2017/06/15 08:42:42 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char ' ', code 32, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'c', code 99, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'o', code 111, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'n', code 110, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 's', code 115, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'o', code 111, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'l', code 108, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'e', code 101, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char '-', code 45, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 's', code 115, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'e', code 101, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 't', code 116, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'u', code 117, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'p', code 112, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char '/', code 47, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'm', code 109, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'o', code 111, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'd', code 100, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'e', code 101, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'l', code 108, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'c', code 99, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'o', code 111, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'd', code 100, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'e', code 101, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char '=', code 61, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'p', code 112, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'c', code 99, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '1', code 49, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '0', code 48, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '5', code 53, shift false 2017/06/15 08:42:49 packer: 2017/06/15 08:42:49 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char ' ', code 32, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'd', code 100, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'e', code 101, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'b', code 98, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'c', code 99, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'o', code 111, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'n', code 110, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char '/', code 47, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'r', code 114, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'o', code 111, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'n', code 110, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 't', code 116, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'e', code 101, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'd', code 100, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char '=', code 61, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'o', code 111, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'i', code 105, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 't', code 116, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'e', code 101, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'r', code 114, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'a', code 97, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'c', code 99, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 't', code 116, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'i', code 105, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'v', code 118, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'e', code 101, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char ' ', code 32, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'd', code 100, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'e', code 101, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'b', code 98, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'i', code 105, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'a', code 97, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'n', code 110, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char '-', code 45, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'i', code 105, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'n', code 110, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 's', code 115, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 't', code 116, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'a', code 97, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'e', code 101, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'r', code 114, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char '=', code 61, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'e', code 101, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'n', code 110, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char '_', code 95, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'U', code 85, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'S', code 83, shift true 2017/06/15 08:43:02 packer: 2017/06/15 08:43:02 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char ' ', code 32, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'b', code 98, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char '=', code 61, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'a', code 97, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'l', code 108, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 's', code 115, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'e', code 101, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:05 packer: 2017/06/15 08:43:05 Sending char ' ', code 32, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'n', code 110, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 't', code 116, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'r', code 114, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'd', code 100, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '=', code 61, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '/', code 47, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'i', code 105, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'n', code 110, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 's', code 115, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 't', code 116, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'a', code 97, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char '/', code 47, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'n', code 110, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 't', code 116, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'r', code 114, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'd', code 100, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char '.', code 46, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'g', code 103, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'z', code 122, shift false 2017/06/15 08:43:11 packer: 2017/06/15 08:43:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char ' ', code 32, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'k', code 107, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'b', code 98, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'd', code 100, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char '-', code 45, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'c', code 99, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'h', code 104, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 's', code 115, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'r', code 114, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char '/', code 47, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'm', code 109, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 't', code 116, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'h', code 104, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'o', code 111, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'd', code 100, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char '=', code 61, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 'u', code 117, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 's', code 115, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char ' ', code 32, shift false 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char 'k', code 107, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'e', code 101, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'y', code 121, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'b', code 98, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'o', code 111, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'a', code 97, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'r', code 114, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'd', code 100, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char '-', code 45, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'c', code 99, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'o', code 111, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'n', code 110, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'f', code 102, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'i', code 105, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'g', code 103, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'u', code 117, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'r', code 114, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'a', code 97, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 't', code 116, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'i', code 105, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'o', code 111, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'n', code 110, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char '/', code 47, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'l', code 108, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'a', code 97, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'y', code 121, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'o', code 111, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'u', code 117, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 't', code 116, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char '=', code 61, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'U', code 85, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'S', code 83, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'A', code 65, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char ' ', code 32, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'k', code 107, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'e', code 101, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'y', code 121, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'b', code 98, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'o', code 111, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'a', code 97, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'r', code 114, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'd', code 100, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char '-', code 45, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'c', code 99, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'o', code 111, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'n', code 110, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'f', code 102, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'i', code 105, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'g', code 103, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'u', code 117, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'r', code 114, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'a', code 97, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 't', code 116, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'i', code 105, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'o', code 111, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'n', code 110, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char '/', code 47, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'v', code 118, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'a', code 97, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'r', code 114, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'i', code 105, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'a', code 97, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'n', code 110, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 't', code 116, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char '=', code 61, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'U', code 85, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'S', code 83, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'A', code 65, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char ' ', code 32, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'l', code 108, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'o', code 111, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'c', code 99, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'a', code 97, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'l', code 108, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'e', code 101, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char '=', code 61, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'e', code 101, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'n', code 110, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char '_', code 95, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'U', code 85, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'S', code 83, shift true 2017/06/15 08:43:36 packer: 2017/06/15 08:43:36 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char ' ', code 32, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'n', code 110, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'e', code 101, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 't', code 116, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'c', code 99, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'f', code 102, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char '/', code 47, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'e', code 101, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 't', code 116, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char '_', code 95, shift true 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'd', code 100, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'o', code 111, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'm', code 109, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'a', code 97, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'i', code 105, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'n', code 110, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char '=', code 61, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'v', code 118, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Sending char 'm', code 109, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char ' ', code 32, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'n', code 110, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'e', code 101, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 't', code 116, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'c', code 99, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'f', code 102, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char '/', code 47, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'e', code 101, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 't', code 116, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char '_', code 95, shift true 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'h', code 104, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'o', code 111, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 's', code 115, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 't', code 116, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'n', code 110, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'a', code 97, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'm', code 109, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'e', code 101, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char '=', code 61, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'v', code 118, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'a', code 97, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'g', code 103, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'r', code 114, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'a', code 97, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'n', code 110, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 't', code 116, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:48 packer: 2017/06/15 08:43:48 Sending char ' ', code 32, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'g', code 103, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'r', code 114, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'u', code 117, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'b', code 98, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char '-', code 45, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'i', code 105, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'n', code 110, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 's', code 115, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 't', code 116, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'a', code 97, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'e', code 101, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'r', code 114, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char '/', code 47, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'b', code 98, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 't', code 116, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'd', code 100, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'e', code 101, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'v', code 118, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '=', code 61, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '/', code 47, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'd', code 100, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'e', code 101, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'v', code 118, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char '/', code 47, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 's', code 115, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'd', code 100, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Sending char 'a', code 97, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char ' ', code 32, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'n', code 110, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'o', code 111, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'a', code 97, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'p', code 112, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'i', code 105, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'c', code 99, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char ' ', code 32, shift false 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char 'p', code 112, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'r', code 114, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 's', code 115, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'd', code 100, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char '/', code 47, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'u', code 117, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'r', code 114, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'l', code 108, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char '=', code 61, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'h', code 104, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'p', code 112, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char ':', code 58, shift true 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 55, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 50, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '.', code 46, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 55, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 50, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 52, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 49, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '', code 50, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '', code 53, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 48, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char ':', code 58, shift true 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '8', code 56, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '6', code 54, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '/', code 47, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char 'p', code 112, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'r', code 114, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 's', code 115, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'd', code 100, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char '.', code 46, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'c', code 99, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'f', code 102, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'g', code 103, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:10 packer: 2017/06/15 08:44:10 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:44:11 packer: 2017/06/15 08:44:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 [INFO] Waiting for SSH, up to timeout: 2h46m40s 2017/06/15 08:44:12 ui: [1;32m==> vmware-iso: Waiting for SSH to become available...[0m 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:13 packer: 2017/06/15 08:44:13 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:19 packer: 2017/06/15 08:44:19 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:25 packer: 2017/06/15 08:44:25 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:31 packer: 2017/06/15 08:44:31 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:37 packer: 2017/06/15 08:44:37 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready ```	1.0	Remote ESXi builder failing on retrieving VM ip. ESXi 6.0, packer 1.0 - I'm using a ESXi 6.0 host for testing packer and I've been trying to get the vmware-iso remote ESXi builder to work. With packer 1.0. I get to the point where packer tries to retrieve the guest IP with "esxcli --formatter csv network vm port list -w #######" but errors out saying it cannot find the ip. Packer log: ``` 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Using internal plugin for vmware-vmx 2017/06/15 08:41:00 Using internal plugin for hyperv-iso 2017/06/15 08:41:00 Using internal plugin for virtualbox-iso 2017/06/15 08:41:00 Using internal plugin for amazon-instance 2017/06/15 08:41:00 Using internal plugin for digitalocean 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for oneandone 2017/06/15 08:41:00 Using internal plugin for openstack 2017/06/15 08:41:00 Using internal plugin for parallels-iso 2017/06/15 08:41:00 Using internal plugin for amazon-ebs 2017/06/15 08:41:00 Using internal plugin for amazon-ebsvolume 2017/06/15 08:41:00 Using internal plugin for null 2017/06/15 08:41:00 Using internal plugin for profitbricks 2017/06/15 08:41:00 Using internal plugin for cloudstack 2017/06/15 08:41:00 Using internal plugin for googlecompute 2017/06/15 08:41:00 Using internal plugin for azure-arm 2017/06/15 08:41:00 Using internal plugin for docker 2017/06/15 08:41:00 Using internal plugin for parallels-pvm 2017/06/15 08:41:00 Using internal plugin for qemu 2017/06/15 08:41:00 Using internal plugin for triton 2017/06/15 08:41:00 Using internal plugin for virtualbox-ovf 2017/06/15 08:41:00 Using internal plugin for amazon-chroot 2017/06/15 08:41:00 Using internal plugin for amazon-ebssurrogate 2017/06/15 08:41:00 Using internal plugin for vmware-iso 2017/06/15 08:41:00 Using internal plugin for converge 2017/06/15 08:41:00 Using internal plugin for salt-masterless 2017/06/15 08:41:00 Using internal plugin for chef-client 2017/06/15 08:41:00 Using internal plugin for chef-solo 2017/06/15 08:41:00 Using internal plugin for shell 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for ansible-local 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for puppet-masterless 2017/06/15 08:41:00 Using internal plugin for puppet-server 2017/06/15 08:41:00 Using internal plugin for ansible 2017/06/15 08:41:00 Using internal plugin for powershell 2017/06/15 08:41:00 Using internal plugin for windows-restart 2017/06/15 08:41:00 Using internal plugin for windows-shell 2017/06/15 08:41:00 Using internal plugin for checksum 2017/06/15 08:41:00 Using internal plugin for docker-save 2017/06/15 08:41:00 Using internal plugin for docker-tag 2017/06/15 08:41:00 Using internal plugin for atlas 2017/06/15 08:41:00 Using internal plugin for manifest 2017/06/15 08:41:00 Using internal plugin for compress 2017/06/15 08:41:00 Using internal plugin for googlecompute-export 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for vagrant-cloud 2017/06/15 08:41:00 Using internal plugin for vsphere 2017/06/15 08:41:00 Using internal plugin for docker-import 2017/06/15 08:41:00 Using internal plugin for artifice 2017/06/15 08:41:00 Using internal plugin for docker-push 2017/06/15 08:41:00 Using internal plugin for vagrant 2017/06/15 08:41:00 Using internal plugin for amazon-import 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[null:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null googlecompute:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute qemu:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu virtualbox-ovf:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf amazon-chroot:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot vmware-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso amazon-ebsvolume:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume digitalocean:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file oneandone:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone parallels-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso amazon-ebs:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs cloudstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack parallels-pvm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm vmware-vmx:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx virtualbox-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-instance:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance azure-arm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm triton:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton amazon-ebssurrogate:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate hyperv-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso profitbricks:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks docker:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker openstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack] PostProcessors:map[docker-save:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save docker-tag:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag atlas:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-atlas manifest:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local vagrant-cloud:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud checksum:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum artifice:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice vagrant:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant amazon-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import compress:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress vsphere:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere docker-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import docker-push:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push googlecompute-export:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export] Provisioners:map[ansible:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible powershell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell converge:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local puppet-server:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server chef-solo:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file windows-restart:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart puppet-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless salt-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-client:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client ansible-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local]} 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 Loading builder: vmware-iso 2017/06/15 08:41:00 Plugin could not be found. Checking same directory as executable. 2017/06/15 08:41:00 Current exe path: /usr/local/bin/packer 2017/06/15 08:41:00 Creating plugin client for path: /usr/local/bin/packer 2017/06/15 08:41:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-builder-vmware-iso"} 2017/06/15 08:41:00 Waiting for RPC address for: /usr/local/bin/packer 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 args: []string{"packer-builder-vmware-iso"} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin minimum port: 10000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin maximum port: 25000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin address: unix /tmp/packer-plugin255655097 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Waiting for connection... 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Serving a plugin connection... 2017/06/15 08:41:00 ui: [1;32mvmware-iso output will be in this color.[0m 2017/06/15 08:41:00 ui: 2017/06/15 08:41:00 Build debug mode: false 2017/06/15 08:41:00 Force build: false 2017/06/15 08:41:00 On error: 2017/06/15 08:41:00 Preparing build: vmware-iso 2017/06/15 08:41:00 Waiting on builds to complete... 2017/06/15 08:41:00 Starting build run: vmware-iso 2017/06/15 08:41:00 Running builder: vmware-iso 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 reconnecting to TCP connection for SSH 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 handshaking with SSH 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Question 1: Password: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 handshake complete! 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 [INFO] no local agent socket, will not connect agent 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system version get 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Connected to VMware ESXi 6.0.0 Releasebuild-3620759 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system settings advanced list -o /Net/GuestIPHack 2017/06/15 08:41:02 ui: [1;32m==> vmware-iso: Downloading or copying ISO[0m 2017/06/15 08:41:02 ui: [0;32m vmware-iso: Downloading or copying: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso[0m 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Acquiring lock to download: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Verifying checksum of /home/git/chief-masterhost/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 [DEBUG] Initial checksum matched, no download needed. 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: test -e /vmfs/volumes/*/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote command exited with '1': test -e /vmfs/volumes//ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/GB/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 No floppy files specified. Floppy disk will not be made. 2017/06/15 08:41:14 ui: [1;32m==> vmware-iso: Uploading ISO to remote machine...[0m 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote uploading: /home/git//ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/GB/packer_cache 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Verifying checksum of /vmfs/volumes/GB/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: sha256sum -c 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 Initial checksum matched, no upload needed. 2017/06/15 08:41:50 ui: [1;32m==> vmware-iso: Creating virtual machine disk[0m 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 opening new ssh session 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 starting remote command: vmkfstools -c 7000M -d zeroedthick -a lsilogic /vmfs/volumes/GB/ubuntu/output-vmware-iso/disk.vmdk 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Building and writing VMX file[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'memsize' = '512' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'cpuid.coresPerSocket' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.present' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.startConnected' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.virtualDev' = 'e1000' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'RemoteDisplay.vnc.webSocket.port' = '5900' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.networkName' = '' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'numvcpus' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Suppressing messages in VMX 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying port: 8446 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Starting HTTP server on port 8446[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Looking for available port between 5900 and 6000 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 starting remote command: esxcli --formatter csv network ip connection list 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5989, port 5989 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:8889, port 8889 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address fe80:2::207:e9ff:fe5a:7c5f:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8000, port 8000 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8100, port 8100 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8300, port 8300 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:2233, port 2233 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5900 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5901 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying address: ... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Found available VNC port: 5902 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Registering remote VM...[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Starting remote scp process: scp -vt /vmfs/volumes/GB/ubuntu/output-vmware-iso 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Started SCP session, beginning transfers... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Copying input data into temporary file so we can read the length 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 [DEBUG] scp: Uploading ubuntu.vmx: perms=C0644 size=2501 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 SCP session complete, closing stdin pipe. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 Waiting for SSH session to complete. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 scp stderr (length 28): Sink: C0644 2501 ubuntu.vmx 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd solo/registervm /vmfs/volumes/GB/ubuntu/output-vmware-iso/ubuntu.vmx 2017/06/15 08:41:52 ui: [1;32m==> vmware-iso: Starting virtual machine...[0m 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd vmsvc/power.on 77 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 opening new ssh session 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 starting remote command: vim-cmd vmsvc/power.getstate 77 2017/06/15 08:41:54 ui: [1;32m==> vmware-iso: Waiting 10s for boot...[0m 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Connecting to VM via VNC[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Connected to VNC desktop: ubuntu 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Host IP for the VMware machine: ** 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Typing the boot command over VNC...[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:05 packer: 2017/06/15 08:42:05 Special code '<f6>' found, replacing with: 65475 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<esc>' found, replacing with: 65307 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:22 packer: 2017/06/15 08:42:22 Sending char '/', code 47, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'i', code 105, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'n', code 110, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 's', code 115, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 't', code 116, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'a', code 97, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char '/', code 47, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'v', code 118, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'm', code 109, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'l', code 108, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'i', code 105, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'n', code 110, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'u', code 117, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'z', code 122, shift false 2017/06/15 08:42:26 packer: 2017/06/15 08:42:26 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char ' ', code 32, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'a', code 97, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'u', code 117, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 't', code 116, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'o', code 111, shift false 2017/06/15 08:42:28 packer: 2017/06/15 08:42:28 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char ' ', code 32, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'c', code 99, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'o', code 111, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'n', code 110, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 's', code 115, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'o', code 111, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'l', code 108, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'e', code 101, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char '-', code 45, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 's', code 115, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'e', code 101, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 't', code 116, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'u', code 117, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'p', code 112, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char '/', code 47, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'a', code 97, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 's', code 115, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'k', code 107, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char '_', code 95, shift true 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'd', code 100, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 't', code 116, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'c', code 99, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 't', code 116, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char '=', code 61, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'f', code 102, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'a', code 97, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'l', code 108, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 's', code 115, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 'e', code 101, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char ' ', code 32, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'c', code 99, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'n', code 110, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 's', code 115, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'l', code 108, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char '-', code 45, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 's', code 115, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 't', code 116, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'u', code 117, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'p', code 112, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char '/', code 47, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'l', code 108, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'a', code 97, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'y', code 121, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'u', code 117, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 't', code 116, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'c', code 99, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'd', code 100, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'e', code 101, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char '=', code 61, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'u', code 117, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 's', code 115, shift false 2017/06/15 08:42:42 packer: 2017/06/15 08:42:42 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char ' ', code 32, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'c', code 99, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'o', code 111, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'n', code 110, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 's', code 115, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'o', code 111, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'l', code 108, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'e', code 101, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char '-', code 45, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 's', code 115, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'e', code 101, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 't', code 116, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'u', code 117, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'p', code 112, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char '/', code 47, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'm', code 109, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'o', code 111, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'd', code 100, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'e', code 101, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'l', code 108, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'c', code 99, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'o', code 111, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'd', code 100, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'e', code 101, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char '=', code 61, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'p', code 112, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'c', code 99, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '1', code 49, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '0', code 48, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '5', code 53, shift false 2017/06/15 08:42:49 packer: 2017/06/15 08:42:49 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char ' ', code 32, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'd', code 100, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'e', code 101, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'b', code 98, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'c', code 99, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'o', code 111, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'n', code 110, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char '/', code 47, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'r', code 114, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'o', code 111, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'n', code 110, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 't', code 116, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'e', code 101, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'd', code 100, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char '=', code 61, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'o', code 111, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'i', code 105, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 't', code 116, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'e', code 101, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'r', code 114, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'a', code 97, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'c', code 99, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 't', code 116, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'i', code 105, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'v', code 118, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'e', code 101, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char ' ', code 32, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'd', code 100, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'e', code 101, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'b', code 98, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'i', code 105, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'a', code 97, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'n', code 110, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char '-', code 45, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'i', code 105, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'n', code 110, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 's', code 115, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 't', code 116, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'a', code 97, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'e', code 101, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'r', code 114, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char '=', code 61, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'e', code 101, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'n', code 110, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char '_', code 95, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'U', code 85, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'S', code 83, shift true 2017/06/15 08:43:02 packer: 2017/06/15 08:43:02 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char ' ', code 32, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'b', code 98, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char '=', code 61, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'a', code 97, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'l', code 108, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 's', code 115, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'e', code 101, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:05 packer: 2017/06/15 08:43:05 Sending char ' ', code 32, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'n', code 110, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 't', code 116, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'r', code 114, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'd', code 100, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '=', code 61, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '/', code 47, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'i', code 105, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'n', code 110, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 's', code 115, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 't', code 116, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'a', code 97, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char '/', code 47, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'n', code 110, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 't', code 116, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'r', code 114, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'd', code 100, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char '.', code 46, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'g', code 103, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'z', code 122, shift false 2017/06/15 08:43:11 packer: 2017/06/15 08:43:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char ' ', code 32, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'k', code 107, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'b', code 98, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'd', code 100, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char '-', code 45, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'c', code 99, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'h', code 104, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 's', code 115, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'r', code 114, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char '/', code 47, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'm', code 109, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 't', code 116, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'h', code 104, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'o', code 111, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'd', code 100, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char '=', code 61, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 'u', code 117, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 's', code 115, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char ' ', code 32, shift false 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char 'k', code 107, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'e', code 101, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'y', code 121, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'b', code 98, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'o', code 111, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'a', code 97, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'r', code 114, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'd', code 100, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char '-', code 45, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'c', code 99, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'o', code 111, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'n', code 110, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'f', code 102, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'i', code 105, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'g', code 103, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'u', code 117, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'r', code 114, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'a', code 97, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 't', code 116, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'i', code 105, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'o', code 111, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'n', code 110, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char '/', code 47, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'l', code 108, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'a', code 97, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'y', code 121, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'o', code 111, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'u', code 117, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 't', code 116, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char '=', code 61, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'U', code 85, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'S', code 83, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'A', code 65, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char ' ', code 32, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'k', code 107, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'e', code 101, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'y', code 121, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'b', code 98, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'o', code 111, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'a', code 97, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'r', code 114, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'd', code 100, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char '-', code 45, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'c', code 99, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'o', code 111, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'n', code 110, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'f', code 102, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'i', code 105, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'g', code 103, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'u', code 117, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'r', code 114, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'a', code 97, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 't', code 116, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'i', code 105, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'o', code 111, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'n', code 110, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char '/', code 47, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'v', code 118, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'a', code 97, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'r', code 114, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'i', code 105, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'a', code 97, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'n', code 110, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 't', code 116, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char '=', code 61, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'U', code 85, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'S', code 83, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'A', code 65, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char ' ', code 32, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'l', code 108, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'o', code 111, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'c', code 99, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'a', code 97, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'l', code 108, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'e', code 101, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char '=', code 61, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'e', code 101, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'n', code 110, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char '_', code 95, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'U', code 85, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'S', code 83, shift true 2017/06/15 08:43:36 packer: 2017/06/15 08:43:36 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char ' ', code 32, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'n', code 110, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'e', code 101, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 't', code 116, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'c', code 99, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'f', code 102, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char '/', code 47, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'e', code 101, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 't', code 116, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char '_', code 95, shift true 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'd', code 100, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'o', code 111, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'm', code 109, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'a', code 97, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'i', code 105, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'n', code 110, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char '=', code 61, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'v', code 118, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Sending char 'm', code 109, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char ' ', code 32, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'n', code 110, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'e', code 101, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 't', code 116, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'c', code 99, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'f', code 102, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char '/', code 47, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'e', code 101, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 't', code 116, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char '_', code 95, shift true 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'h', code 104, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'o', code 111, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 's', code 115, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 't', code 116, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'n', code 110, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'a', code 97, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'm', code 109, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'e', code 101, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char '=', code 61, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'v', code 118, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'a', code 97, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'g', code 103, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'r', code 114, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'a', code 97, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'n', code 110, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 't', code 116, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:48 packer: 2017/06/15 08:43:48 Sending char ' ', code 32, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'g', code 103, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'r', code 114, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'u', code 117, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'b', code 98, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char '-', code 45, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'i', code 105, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'n', code 110, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 's', code 115, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 't', code 116, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'a', code 97, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'e', code 101, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'r', code 114, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char '/', code 47, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'b', code 98, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 't', code 116, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'd', code 100, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'e', code 101, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'v', code 118, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '=', code 61, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '/', code 47, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'd', code 100, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'e', code 101, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'v', code 118, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char '/', code 47, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 's', code 115, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'd', code 100, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Sending char 'a', code 97, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char ' ', code 32, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'n', code 110, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'o', code 111, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'a', code 97, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'p', code 112, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'i', code 105, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'c', code 99, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char ' ', code 32, shift false 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char 'p', code 112, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'r', code 114, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 's', code 115, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'd', code 100, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char '/', code 47, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'u', code 117, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'r', code 114, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'l', code 108, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char '=', code 61, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'h', code 104, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'p', code 112, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char ':', code 58, shift true 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 55, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 50, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '.', code 46, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '', code 55, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 50, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 52, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '', code 49, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '', code 50, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '', code 53, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 48, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char ':', code 58, shift true 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '8', code 56, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '6', code 54, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '/', code 47, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char 'p', code 112, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'r', code 114, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 's', code 115, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'd', code 100, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char '.', code 46, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'c', code 99, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'f', code 102, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'g', code 103, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:10 packer: 2017/06/15 08:44:10 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:44:11 packer: 2017/06/15 08:44:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 [INFO] Waiting for SSH, up to timeout: 2h46m40s 2017/06/15 08:44:12 ui: [1;32m==> vmware-iso: Waiting for SSH to become available...[0m 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:13 packer: 2017/06/15 08:44:13 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:19 packer: 2017/06/15 08:44:19 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:25 packer: 2017/06/15 08:44:25 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:31 packer: 2017/06/15 08:44:31 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:37 packer: 2017/06/15 08:44:37 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready ```	non_defect	remote esxi builder failing on retrieving vm ip esxi packer i m using a esxi host for testing packer and i ve been trying to get the vmware iso remote esxi builder to work with packer i get to the point where packer tries to retrieve the guest ip with esxcli formatter csv network vm port list w but errors out saying it cannot find the ip packer log packer version packer target os arch linux built with go version detected home directory from env var root using internal plugin for vmware vmx using internal plugin for hyperv iso using internal plugin for virtualbox iso using internal plugin for amazon instance using internal plugin for digitalocean using internal plugin for file using internal plugin for oneandone using internal plugin for openstack using internal plugin for parallels iso using internal plugin for amazon ebs using internal plugin for amazon ebsvolume using internal plugin for null using internal plugin for profitbricks using internal plugin for cloudstack using internal plugin for googlecompute using internal plugin for azure arm using internal plugin for docker using internal plugin for parallels pvm using internal plugin for qemu using internal plugin for triton using internal plugin for virtualbox ovf using internal plugin for amazon chroot using internal plugin for amazon ebssurrogate using internal plugin for vmware iso using internal plugin for converge using internal plugin for salt masterless using internal plugin for chef client using internal plugin for chef solo using internal plugin for shell using internal plugin for shell local using internal plugin for ansible local using internal plugin for file using internal plugin for puppet masterless using internal plugin for puppet server using internal plugin for ansible using internal plugin for powershell using internal plugin for windows restart using internal plugin for windows shell using internal plugin for checksum using internal plugin for docker save using internal plugin for docker tag using internal plugin for atlas using internal plugin for manifest using internal plugin for compress using internal plugin for googlecompute export using internal plugin for shell local using internal plugin for vagrant cloud using internal plugin for vsphere using internal plugin for docker import using internal plugin for artifice using internal plugin for docker push using internal plugin for vagrant using internal plugin for amazon import detected home directory from env var root attempting to open config file root packerconfig config file doesn t exist root packerconfig packer config disablecheckpoint false disablecheckpointsignature false pluginminport pluginmaxport builders map postprocessors map provisioners map setting cache directory home git chief masterhost ubuntu packer cache loading builder vmware iso plugin could not be found checking same directory as executable current exe path usr local bin packer creating plugin client for path usr local bin packer starting plugin usr local bin packer string usr local bin packer plugin packer builder vmware iso waiting for rpc address for usr local bin packer detected home directory from env var root packer packer version packer packer target os arch linux packer built with go version packer detected home directory from env var root packer attempting to open config file root packerconfig packer config file doesn t exist root packerconfig packer packer config disablecheckpoint false disablecheckpointsignature false pluginminport pluginmaxport builders map postprocessors map provisioners map packer setting cache directory home git chief masterhost ubuntu packer cache packer args string packer builder vmware iso packer plugin minimum port packer plugin maximum port packer plugin address unix tmp packer packer waiting for connection packer detected home directory from env var root packer serving a plugin connection ui iso output will be in this color ui build debug mode false force build false on error preparing build vmware iso waiting on builds to complete starting build run vmware iso running builder vmware iso packer reconnecting to tcp connection for ssh packer handshaking with ssh packer keyboard interactive challenge packer user packer instructions packer question password packer keyboard interactive challenge packer user packer instructions packer handshake complete packer no local agent socket will not connect agent packer opening new ssh session packer starting remote command esxcli formatter csv system version get packer connected to vmware esxi releasebuild packer opening new ssh session packer starting remote command esxcli formatter csv system settings advanced list o net guestiphack ui vmware iso downloading or copying iso ui vmware iso downloading or copying packer acquiring lock to download packer verifying checksum of home git chief masterhost ubuntu packer cache iso packer initial checksum matched no download needed packer opening new ssh session packer starting remote command test e vmfs volumes ubuntu output vmware iso packer remote command exited with test e vmfs volumes ubuntu output vmware iso packer opening new ssh session packer starting remote command mkdir p vmfs volumes gb ubuntu output vmware iso packer no floppy files specified floppy disk will not be made ui vmware iso uploading iso to remote machine packer remote uploading home git ubuntu packer cache iso packer opening new ssh session packer starting remote command mkdir p vmfs volumes gb packer cache packer verifying checksum of vmfs volumes gb packer cache iso packer opening new ssh session packer starting remote command c packer initial checksum matched no upload needed ui vmware iso creating virtual machine disk packer opening new ssh session packer starting remote command vmkfstools c d zeroedthick a lsilogic vmfs volumes gb ubuntu output vmware iso disk vmdk ui vmware iso building and writing vmx file packer writing vmx to tmp packer ubuntu vmx packer setting vmx memsize packer setting vmx cpuid corespersocket packer setting vmx present true packer setting vmx startconnected true packer setting vmx virtualdev packer setting vmx remotedisplay vnc websocket port packer setting vmx networkname packer setting vmx numvcpus packer writing vmx to tmp packer ubuntu vmx packer suppressing messages in vmx packer trying port ui vmware iso starting http server on port packer looking for available port between and packer opening new ssh session packer starting remote command esxcli formatter csv network ip connection list packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer port in use packer port in use packer trying address packer found available vnc port packer writing vmx to tmp packer ubuntu vmx ui vmware iso registering remote vm packer opening new ssh session packer starting remote scp process scp vt vmfs volumes gb ubuntu output vmware iso packer started scp session beginning transfers packer copying input data into temporary file so we can read the length packer scp uploading ubuntu vmx perms size packer scp session complete closing stdin pipe packer waiting for ssh session to complete packer scp stderr length sink ubuntu vmx packer opening new ssh session packer starting remote command vim cmd solo registervm vmfs volumes gb ubuntu output vmware iso ubuntu vmx ui vmware iso starting virtual machine packer opening new ssh session packer starting remote command vim cmd vmsvc power on packer opening new ssh session packer starting remote command vim cmd vmsvc power getstate ui vmware iso waiting for boot ui vmware iso connecting to vm via vnc packer connected to vnc desktop ubuntu packer host ip for the vmware machine ui vmware iso typing the boot command over vnc packer special code found replacing with packer special code found sleeping one second packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char code shift false packer sending char v code shift false packer sending char m code shift false packer sending char l code shift false packer sending char i code shift false packer sending char n code shift false packer sending char u code shift false packer sending char z code shift false packer special code found sleeping one second packer sending char code shift false packer sending char a code shift false packer sending char u code shift false packer sending char t code shift false packer sending char o code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char a code shift false packer sending char s code shift false packer sending char k code shift false packer sending char code shift true packer sending char d code shift false packer sending char e code shift false packer sending char t code shift false packer sending char e code shift false packer sending char c code shift false packer sending char t code shift false packer sending char code shift false packer sending char f code shift false packer sending char a code shift false packer sending char l code shift false packer sending char s code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char l code shift false packer sending char a code shift false packer sending char y code shift false packer sending char o code shift false packer sending char u code shift false packer sending char t code shift false packer sending char c code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char code shift false packer sending char u code shift false packer sending char s code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char m code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char l code shift false packer sending char c code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char code shift false packer sending char p code shift false packer sending char c code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer special code found sleeping one second packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char b code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char code shift false packer sending char f code shift false packer sending char r code shift false packer sending char o code shift false packer sending char n code shift false packer sending char t code shift false packer sending char e code shift false packer sending char n code shift false packer sending char d code shift false packer sending char code shift false packer sending char n code shift false packer sending char o code shift false packer sending char n code shift false packer sending char i code shift false packer sending char n code shift false packer sending char t code shift false packer sending char e code shift false packer sending char r code shift false packer sending char a code shift false packer sending char c code shift false packer sending char t code shift false packer sending char i code shift false packer sending char v code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char b code shift false packer sending char i code shift false packer sending char a code shift false packer sending char n code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char e code shift false packer sending char n code shift false packer sending char code shift true packer sending char u code shift true packer sending char s code shift true packer special code found sleeping one second packer sending char code shift false packer sending char f code shift false packer sending char b code shift false packer sending char code shift false packer sending char f code shift false packer sending char a code shift false packer sending char l code shift false packer sending char s code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char i code shift false packer sending char t code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char i code shift false packer sending char t code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char g code shift false packer sending char z code shift false packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char b code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char h code shift false packer sending char o code shift false packer sending char o code shift false packer sending char s code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char m code shift false packer sending char e code shift false packer sending char t code shift false packer sending char h code shift false packer sending char o code shift false packer sending char d code shift false packer sending char code shift false packer sending char u code shift false packer sending char s code shift false packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char e code shift false packer sending char y code shift false packer sending char b code shift false packer sending char o code shift false packer sending char a code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char i code shift false packer sending char g code shift false packer sending char u code shift false packer sending char r code shift false packer sending char a code shift false packer sending char t code shift false packer sending char i code shift false packer sending char o code shift false packer sending char n code shift false packer sending char code shift false packer sending char l code shift false packer sending char a code shift false packer sending char y code shift false packer sending char o code shift false packer sending char u code shift false packer sending char t code shift false packer sending char code shift false packer sending char u code shift true packer sending char s code shift true packer sending char a code shift true packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char e code shift false packer sending char y code shift false packer sending char b code shift false packer sending char o code shift false packer sending char a code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char i code shift false packer sending char g code shift false packer sending char u code shift false packer sending char r code shift false packer sending char a code shift false packer sending char t code shift false packer sending char i code shift false packer sending char o code shift false packer sending char n code shift false packer sending char code shift false packer sending char v code shift false packer sending char a code shift false packer sending char r code shift false packer sending char i code shift false packer sending char a code shift false packer sending char n code shift false packer sending char t code shift false packer sending char code shift false packer sending char u code shift true packer sending char s code shift true packer sending char a code shift true packer special code found sleeping one second packer sending char code shift false packer sending char l code shift false packer sending char o code shift false packer sending char c code shift false packer sending char a code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char e code shift false packer sending char n code shift false packer sending char code shift true packer sending char u code shift true packer sending char s code shift true packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char e code shift false packer sending char t code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char g code shift false packer sending char e code shift false packer sending char t code shift false packer sending char code shift true packer sending char d code shift false packer sending char o code shift false packer sending char m code shift false packer sending char a code shift false packer sending char i code shift false packer sending char n code shift false packer sending char code shift false packer sending char v code shift false packer sending char m code shift false packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char e code shift false packer sending char t code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char g code shift false packer sending char e code shift false packer sending char t code shift false packer sending char code shift true packer sending char h code shift false packer sending char o code shift false packer sending char s code shift false packer sending char t code shift false packer sending char n code shift false packer sending char a code shift false packer sending char m code shift false packer sending char e code shift false packer sending char code shift false packer sending char v code shift false packer sending char a code shift false packer sending char g code shift false packer sending char r code shift false packer sending char a code shift false packer sending char n code shift false packer sending char t code shift false packer special code found sleeping one second packer sending char code shift false packer sending char g code shift false packer sending char r code shift false packer sending char u code shift false packer sending char b code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char b code shift false packer sending char o code shift false packer sending char o code shift false packer sending char t code shift false packer sending char d code shift false packer sending char e code shift false packer sending char v code shift false packer sending char code shift false packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char v code shift false packer sending char code shift false packer sending char s code shift false packer sending char d code shift false packer sending char a code shift false packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char o code shift false packer sending char a code shift false packer sending char p code shift false packer sending char i code shift false packer sending char c code shift false packer special code found sleeping one second packer sending char code shift false packer sending char p code shift false packer sending char r code shift false packer sending char e code shift false packer sending char s code shift false packer sending char e code shift false packer sending char e code shift false packer sending char d code shift false packer sending char code shift false packer sending char u code shift false packer sending char r code shift false packer sending char l code shift false packer sending char code shift false packer sending char h code shift false packer sending char t code shift false packer sending char t code shift false packer sending char p code shift false packer sending char code shift true packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift true packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char p code shift false packer sending char r code shift false packer sending char e code shift false packer sending char s code shift false packer sending char e code shift false packer sending char e code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer special code found sleeping one second packer special code found replacing with packer special code found sleeping one second packer waiting for ssh up to timeout ui vmware iso waiting for ssh to become available packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready	0
9,329	2,615,144,893	IssuesEvent	2015-03-01 06:20:37	chrsmith/html5rocks	https://api.github.com/repos/chrsmith/html5rocks	closed	add fileAPI example	auto-migrated Milestone-2 playground Priority-Medium Type-Defect	``` corey hart submitted a fileapi example for the playground. let's add it in! ``` Original issue reported on code.google.com by `paulir...@google.com` on 28 Jul 2010 at 10:00	1.0	add fileAPI example - ``` corey hart submitted a fileapi example for the playground. let's add it in! ``` Original issue reported on code.google.com by `paulir...@google.com` on 28 Jul 2010 at 10:00	defect	add fileapi example corey hart submitted a fileapi example for the playground let s add it in original issue reported on code google com by paulir google com on jul at	1
24,106	3,917,070,253	IssuesEvent	2016-04-21 06:23:36	irnawansuprapti/openbiz-cubi	https://api.github.com/repos/irnawansuprapti/openbiz-cubi	closed	muscles 56	auto-migrated Priority-Medium spam Type-Defect	``` To avoid such fate, start working on a good plan. You are not told to go out and buy a long term care insurance (LTCI) policy or a hybrid life insurance policy with LTC rider this very instant. You are simply advised to be more conscious of your health. You may have an hourglass figure or muscles in the right places but how are your internal organs? Take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle. http://www.skinphysiciantips.com/rapid-repair-eye-serum/ ``` Original issue reported on code.google.com by `OliverV...@gmail.com` on 16 Apr 2015 at 10:08	1.0	muscles 56 - ``` To avoid such fate, start working on a good plan. You are not told to go out and buy a long term care insurance (LTCI) policy or a hybrid life insurance policy with LTC rider this very instant. You are simply advised to be more conscious of your health. You may have an hourglass figure or muscles in the right places but how are your internal organs? Take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle. http://www.skinphysiciantips.com/rapid-repair-eye-serum/ ``` Original issue reported on code.google.com by `OliverV...@gmail.com` on 16 Apr 2015 at 10:08	defect	muscles to avoid such fate start working on a good plan you are not told to go out and buy a long term care insurance ltci policy or a hybrid life insurance policy with ltc rider this very instant you are simply advised to be more conscious of your health you may have an hourglass figure or muscles in the right places but how are your internal organs take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle original issue reported on code google com by oliverv gmail com on apr at	1
81,574	7,786,660,956	IssuesEvent	2018-06-06 19:42:17	gomods/athens	https://api.github.com/repos/gomods/athens	closed	Tests don't run locally	athens good first issue olympus testing	A few things: - I run `docker-compose -p athenstest up -d` to launch all services that tests depend on - I run `make test` and it runs `go test ./...` - it should instead run `buffalo test` on the buffalo apps (`cmd/proxy` and `cmd/olympus`) - I get this error: ```console [~/gocode/src/github.com/gomods/athens] aaschles $ make test cd cmd/proxy && buffalo test [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF Usage: buffalo test [flags] Flags: -h, --help help for test ERRO[0000] Error: error creating MySQL database olympusdb: driver: bad connection make: *** [test] Error 255 ``` I think there will be other errors that come up after this one gets fixed	1.0	Tests don't run locally - A few things: - I run `docker-compose -p athenstest up -d` to launch all services that tests depend on - I run `make test` and it runs `go test ./...` - it should instead run `buffalo test` on the buffalo apps (`cmd/proxy` and `cmd/olympus`) - I get this error: ```console [~/gocode/src/github.com/gomods/athens] aaschles $ make test cd cmd/proxy && buffalo test [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF Usage: buffalo test [flags] Flags: -h, --help help for test ERRO[0000] Error: error creating MySQL database olympusdb: driver: bad connection make: *** [test] Error 255 ``` I think there will be other errors that come up after this one gets fixed	non_defect	tests don t run locally a few things i run docker compose p athenstest up d to launch all services that tests depend on i run make test and it runs go test it should instead run buffalo test on the buffalo apps cmd proxy and cmd olympus i get this error console aaschles make test cd cmd proxy buffalo test packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof usage buffalo test flags h help help for test erro error error creating mysql database olympusdb driver bad connection make error i think there will be other errors that come up after this one gets fixed	0
346,777	10,419,705,196	IssuesEvent	2019-09-15 18:31:50	LunarWatcher/AdventureLandCpp	https://api.github.com/repos/LunarWatcher/AdventureLandCpp	closed	Critical: replace Poco	priority:high	Poco works like a charm on Linux, but on Windows with MinGW, it's a different story. It injects incompatible libraries (attempts to link `-lCrypt32.lib` - `-lcrypt32` (used by a different library) is fine, but the `.lib` ending breaks it), and I can't fix it. It probably works fine on full-native Windows, My current plan is to switch over to [whoshuu/cpr](https://github.com/whoshuu/cpr) (through [conan-cpr](https://github.com/DEGoodmanWilson/conan-cpr)), which relies on cURL (fortunately available through Conan). One major advantage with changing, beyond potentially better support for Windows, is that cURL and CPR is considerably lighter than Poco. This is especially noticeable on devices with little resources available (such as the Raspberry Pi)	1.0	Critical: replace Poco - Poco works like a charm on Linux, but on Windows with MinGW, it's a different story. It injects incompatible libraries (attempts to link `-lCrypt32.lib` - `-lcrypt32` (used by a different library) is fine, but the `.lib` ending breaks it), and I can't fix it. It probably works fine on full-native Windows, My current plan is to switch over to [whoshuu/cpr](https://github.com/whoshuu/cpr) (through [conan-cpr](https://github.com/DEGoodmanWilson/conan-cpr)), which relies on cURL (fortunately available through Conan). One major advantage with changing, beyond potentially better support for Windows, is that cURL and CPR is considerably lighter than Poco. This is especially noticeable on devices with little resources available (such as the Raspberry Pi)	non_defect	critical replace poco poco works like a charm on linux but on windows with mingw it s a different story it injects incompatible libraries attempts to link lib used by a different library is fine but the lib ending breaks it and i can t fix it it probably works fine on full native windows my current plan is to switch over to through which relies on curl fortunately available through conan one major advantage with changing beyond potentially better support for windows is that curl and cpr is considerably lighter than poco this is especially noticeable on devices with little resources available such as the raspberry pi	0
32,733	6,905,571,158	IssuesEvent	2017-11-27 07:49:50	hazelcast/hazelcast-jet	https://api.github.com/repos/hazelcast/hazelcast-jet	closed	PeekWrappedP obscures actual class of the processor	core defect	When logging using PeekWrappedP it obscures the class of the actual processor: ```16:05:29,650 INFO \|\| - [com.hazelcast.jet.impl.processor.PeekWrappedP.groupByKey.cd6373be.stage2#0] hz._hzInstance_1_jet.jet.cooperative.thread-1 - [10.0.1.3]:5701 [jet] [0.6-SNAPSHOT] Output to 0: accusers=6```	1.0	PeekWrappedP obscures actual class of the processor - When logging using PeekWrappedP it obscures the class of the actual processor: ```16:05:29,650 INFO \|\| - [com.hazelcast.jet.impl.processor.PeekWrappedP.groupByKey.cd6373be.stage2#0] hz._hzInstance_1_jet.jet.cooperative.thread-1 - [10.0.1.3]:5701 [jet] [0.6-SNAPSHOT] Output to 0: accusers=6```	defect	peekwrappedp obscures actual class of the processor when logging using peekwrappedp it obscures the class of the actual processor info hz hzinstance jet jet cooperative thread output to accusers	1
330,266	24,253,503,008	IssuesEvent	2022-09-27 15:49:39	nebari-dev/nebari-docs	https://api.github.com/repos/nebari-dev/nebari-docs	opened	[DOC] - Security Overview and best practices	area: documentation 📖	### Preliminary Checks - [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions ### Summary [Notion Page](https://www.notion.so/quansightlabs/Security-overview-and-best-practices-86376fd95d5f4395b6648647ad51dedb) ### Steps to Resolve this Issue 1. 2. 3. ...	1.0	[DOC] - Security Overview and best practices - ### Preliminary Checks - [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions ### Summary [Notion Page](https://www.notion.so/quansightlabs/Security-overview-and-best-practices-86376fd95d5f4395b6648647ad51dedb) ### Steps to Resolve this Issue 1. 2. 3. ...	non_defect	security overview and best practices preliminary checks this issue is not a question feature request rfc or anything other than a bug report please post those things in github discussions summary steps to resolve this issue	0
22,234	3,619,269,925	IssuesEvent	2016-02-08 15:26:05	pavva94/snake-os	https://api.github.com/repos/pavva94/snake-os	closed	SNAKE OS does NOT have OPKG at all!	auto-migrated Priority-Medium Type-Defect	``` When i log into SNAKE, and go to services, i can see: DDNS FTP Samba SFTP/SSH Swapfile Syslog telnet transmission webserver that's it! and there is no OPKG there! what can i do? I use: SNAKE OS V1.3.2 (20101130) Kernel version: 2.6.16-gazineu thanks ``` Original issue reported on code.google.com by `ez2...@gmail.com` on 26 Jun 2013 at 11:13 Attachments: * [snake.jpg](https://storage.googleapis.com/google-code-attachments/snake-os/issue-364/comment-0/snake.jpg)	1.0	SNAKE OS does NOT have OPKG at all! - ``` When i log into SNAKE, and go to services, i can see: DDNS FTP Samba SFTP/SSH Swapfile Syslog telnet transmission webserver that's it! and there is no OPKG there! what can i do? I use: SNAKE OS V1.3.2 (20101130) Kernel version: 2.6.16-gazineu thanks ``` Original issue reported on code.google.com by `ez2...@gmail.com` on 26 Jun 2013 at 11:13 Attachments: * [snake.jpg](https://storage.googleapis.com/google-code-attachments/snake-os/issue-364/comment-0/snake.jpg)	defect	snake os does not have opkg at all when i log into snake and go to services i can see ddns ftp samba sftp ssh swapfile syslog telnet transmission webserver that s it and there is no opkg there what can i do i use snake os kernel version gazineu thanks original issue reported on code google com by gmail com on jun at attachments	1
224,447	17,188,607,933	IssuesEvent	2021-07-16 07:42:24	numpy/numpy	https://api.github.com/repos/numpy/numpy	closed	DOC: There is no easy way to find the NumPy PDF docs.	04 - Documentation	They are located at `https://numpy.org/doc/`, but there is no visible link to that page.	1.0	DOC: There is no easy way to find the NumPy PDF docs. - They are located at `https://numpy.org/doc/`, but there is no visible link to that page.	non_defect	doc there is no easy way to find the numpy pdf docs they are located at but there is no visible link to that page	0
62,278	17,023,888,031	IssuesEvent	2021-07-03 04:22:58	tomhughes/trac-tickets	https://api.github.com/repos/tomhughes/trac-tickets	closed	Website does not show the location of the note being viewed.	Component: website Priority: minor Resolution: fixed Type: defect	[Submitted to the original trac issue database at 12.06pm, Sunday, 1st December 2013] Since the website redesign the map component no longer focuses on the location of the note when opened from an RSS feed. This bug makes it difficult for mappers who monitor their local area and triage note reports. Steps to reproduce: 1. Generate a notes RSS feed (e.g. http://api.openstreetmap.org/api/0.6/notes/feed?bbox=-1.717,50.772,-0.748,51.236 ) 2. Click on one of the feed entries (e.g. http://api.openstreetmap.org/note/81260#c158974 ) Expected results: Webpage loads showing a sidebar containing note details and the map focused on the location of the note. Actual results: Webpage shows sidebar containing note detail and the map component is focused on the last viewed location.	1.0	Website does not show the location of the note being viewed. - [Submitted to the original trac issue database at 12.06pm, Sunday, 1st December 2013] Since the website redesign the map component no longer focuses on the location of the note when opened from an RSS feed. This bug makes it difficult for mappers who monitor their local area and triage note reports. Steps to reproduce: 1. Generate a notes RSS feed (e.g. http://api.openstreetmap.org/api/0.6/notes/feed?bbox=-1.717,50.772,-0.748,51.236 ) 2. Click on one of the feed entries (e.g. http://api.openstreetmap.org/note/81260#c158974 ) Expected results: Webpage loads showing a sidebar containing note details and the map focused on the location of the note. Actual results: Webpage shows sidebar containing note detail and the map component is focused on the last viewed location.	defect	website does not show the location of the note being viewed since the website redesign the map component no longer focuses on the location of the note when opened from an rss feed this bug makes it difficult for mappers who monitor their local area and triage note reports steps to reproduce generate a notes rss feed e g click on one of the feed entries e g expected results webpage loads showing a sidebar containing note details and the map focused on the location of the note actual results webpage shows sidebar containing note detail and the map component is focused on the last viewed location	1
132,615	10,760,532,335	IssuesEvent	2019-10-31 18:47:56	PulpQE/pulp-smash	https://api.github.com/repos/PulpQE/pulp-smash	closed	Verify that duplicate userid is not allowed	Issue Type: Test Case pulp 2 - closed - wontfix	https://pulp.plan.io/issues/2957 Assert user create does not allow creation of duplicate userid.	1.0	Verify that duplicate userid is not allowed - https://pulp.plan.io/issues/2957 Assert user create does not allow creation of duplicate userid.	non_defect	verify that duplicate userid is not allowed assert user create does not allow creation of duplicate userid	0
95,006	16,064,579,031	IssuesEvent	2021-04-23 17:00:47	NixOS/nixpkgs	https://api.github.com/repos/NixOS/nixpkgs	opened	Vulnerability roundup 101: gitlab-13.8.6: 6 advisories [7.5]	1.severity: security	[search](https://search.nix.gsc.io/?q=gitlab&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gitlab+in%3Apath&type=Code) * [ ] [CVE-2021-22200](https://nvd.nist.gov/vuln/detail/CVE-2021-22200) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22203](https://nvd.nist.gov/vuln/detail/CVE-2021-22203) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22196](https://nvd.nist.gov/vuln/detail/CVE-2021-22196) CVSSv3=5.4 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22197](https://nvd.nist.gov/vuln/detail/CVE-2021-22197) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22198](https://nvd.nist.gov/vuln/detail/CVE-2021-22198) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22202](https://nvd.nist.gov/vuln/detail/CVE-2021-22202) CVSSv3=4.3 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: c7e905b6a97; nixos-unstable: f5e8bdd07d1. Cc @fpletz Cc @globin Cc @krav Cc @talyz	True	Vulnerability roundup 101: gitlab-13.8.6: 6 advisories [7.5] - [search](https://search.nix.gsc.io/?q=gitlab&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gitlab+in%3Apath&type=Code) * [ ] [CVE-2021-22200](https://nvd.nist.gov/vuln/detail/CVE-2021-22200) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22203](https://nvd.nist.gov/vuln/detail/CVE-2021-22203) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22196](https://nvd.nist.gov/vuln/detail/CVE-2021-22196) CVSSv3=5.4 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22197](https://nvd.nist.gov/vuln/detail/CVE-2021-22197) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22198](https://nvd.nist.gov/vuln/detail/CVE-2021-22198) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22202](https://nvd.nist.gov/vuln/detail/CVE-2021-22202) CVSSv3=4.3 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: c7e905b6a97; nixos-unstable: f5e8bdd07d1. Cc @fpletz Cc @globin Cc @krav Cc @talyz	non_defect	vulnerability roundup gitlab advisories nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable scanned versions nixos nixos unstable cc fpletz cc globin cc krav cc talyz	0
37,987	8,628,279,534	IssuesEvent	2018-11-21 16:58:00	vrapper/vrapper	https://api.github.com/repos/vrapper/vrapper	closed	Commands (: and /) trigger file corruption through macros	Defect	In Eclipse 4.9 (latest release currently) pressing the colon key in the default Eclipse editor to run a command behaves strangely by inserting (random?) text into the file but not showing the command popup. The slash key to search for text is also showing the popup only on second press. Especially the first one makes Vrapper unusable.	1.0	Commands (: and /) trigger file corruption through macros - In Eclipse 4.9 (latest release currently) pressing the colon key in the default Eclipse editor to run a command behaves strangely by inserting (random?) text into the file but not showing the command popup. The slash key to search for text is also showing the popup only on second press. Especially the first one makes Vrapper unusable.	defect	commands and trigger file corruption through macros in eclipse latest release currently pressing the colon key in the default eclipse editor to run a command behaves strangely by inserting random text into the file but not showing the command popup the slash key to search for text is also showing the popup only on second press especially the first one makes vrapper unusable	1
23,269	3,785,178,165	IssuesEvent	2016-03-20 10:21:48	pearu/pyvtk	https://api.github.com/repos/pearu/pyvtk	closed	Non integer mesh points	auto-migrated Priority-Medium Type-Defect	``` What steps will reproduce the problem? 1. Write a mesh ( in my case unstructured) with 'float' mesh points 2. Output VTK file will state that the data is still of type 'int' Looking at the source I see that 'int' is hard coded in UnstructuredGrid.py in line 100 I recommend placing a switch that detects whether the mesh coordinates are of type 'int' or 'float' then write the correct string. I've attached a sample VTK written by pyvtk where the issue may be seen (I left it in ASCII format). The error is on line 5 of the sample newTest.vtk ``` Original issue reported on code.google.com by `komperda...@gmail.com` on 25 Aug 2012 at 9:48 Attachments: * [newTest.vtk](https://storage.googleapis.com/google-code-attachments/pyvtk/issue-2/comment-0/newTest.vtk)	1.0	Non integer mesh points - ``` What steps will reproduce the problem? 1. Write a mesh ( in my case unstructured) with 'float' mesh points 2. Output VTK file will state that the data is still of type 'int' Looking at the source I see that 'int' is hard coded in UnstructuredGrid.py in line 100 I recommend placing a switch that detects whether the mesh coordinates are of type 'int' or 'float' then write the correct string. I've attached a sample VTK written by pyvtk where the issue may be seen (I left it in ASCII format). The error is on line 5 of the sample newTest.vtk ``` Original issue reported on code.google.com by `komperda...@gmail.com` on 25 Aug 2012 at 9:48 Attachments: * [newTest.vtk](https://storage.googleapis.com/google-code-attachments/pyvtk/issue-2/comment-0/newTest.vtk)	defect	non integer mesh points what steps will reproduce the problem write a mesh in my case unstructured with float mesh points output vtk file will state that the data is still of type int looking at the source i see that int is hard coded in unstructuredgrid py in line i recommend placing a switch that detects whether the mesh coordinates are of type int or float then write the correct string i ve attached a sample vtk written by pyvtk where the issue may be seen i left it in ascii format the error is on line of the sample newtest vtk original issue reported on code google com by komperda gmail com on aug at attachments	1
46,497	13,055,921,526	IssuesEvent	2020-07-30 03:07:38	icecube-trac/tix2	https://api.github.com/repos/icecube-trac/tix2	opened	paraboloid - coverage of private interfaces is weak (Trac #1305)	Incomplete Migration Migrated from Trac combo reconstruction defect	Migrated from https://code.icecube.wisc.edu/ticket/1305 ```json { "status": "closed", "changetime": "2016-02-10T10:59:05", "description": "a serialization and a \"known failure\" test will quickly bump coverage", "reporter": "nega", "cc": "", "resolution": "fixed", "_ts": "1455101945934200", "component": "combo reconstruction", "summary": "paraboloid - coverage of private interfaces is weak", "priority": "normal", "keywords": "", "time": "2015-08-28T23:07:43", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```	1.0	paraboloid - coverage of private interfaces is weak (Trac #1305) - Migrated from https://code.icecube.wisc.edu/ticket/1305 ```json { "status": "closed", "changetime": "2016-02-10T10:59:05", "description": "a serialization and a \"known failure\" test will quickly bump coverage", "reporter": "nega", "cc": "", "resolution": "fixed", "_ts": "1455101945934200", "component": "combo reconstruction", "summary": "paraboloid - coverage of private interfaces is weak", "priority": "normal", "keywords": "", "time": "2015-08-28T23:07:43", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```	defect	paraboloid coverage of private interfaces is weak trac migrated from json status closed changetime description a serialization and a known failure test will quickly bump coverage reporter nega cc resolution fixed ts component combo reconstruction summary paraboloid coverage of private interfaces is weak priority normal keywords time milestone owner kjmeagher type defect	1
130,951	18,214,175,323	IssuesEvent	2021-09-30 00:39:35	ghc-dev/Brenda-Jacobs	https://api.github.com/repos/ghc-dev/Brenda-Jacobs	closed	CVE-2017-16119 (High) detected in fresh-0.2.4.tgz - autoclosed	security vulnerability	## CVE-2017-16119 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fresh-0.2.4.tgz</b></p></summary> <p>HTTP response freshness testing</p> <p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz">https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz</a></p> <p>Path to dependency file: Brenda-Jacobs/package.json</p> <p>Path to vulnerable library: Brenda-Jacobs/node_modules/fresh/package.json</p> <p> Dependency Hierarchy: - send-0.11.1.tgz (Root Library) - :x: fresh-0.2.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Brenda-Jacobs/commit/8b710e312525a6b8c5c2de0698af2c35e0a6c1f7">8b710e312525a6b8c5c2de0698af2c35e0a6c1f7</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119>CVE-2017-16119</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: fresh - 0.5.2</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"fresh","packageVersion":"0.2.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"send:0.11.1;fresh:0.2.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"fresh - 0.5.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16119","vulnerabilityDetails":"Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->	True	CVE-2017-16119 (High) detected in fresh-0.2.4.tgz - autoclosed - ## CVE-2017-16119 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fresh-0.2.4.tgz</b></p></summary> <p>HTTP response freshness testing</p> <p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz">https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz</a></p> <p>Path to dependency file: Brenda-Jacobs/package.json</p> <p>Path to vulnerable library: Brenda-Jacobs/node_modules/fresh/package.json</p> <p> Dependency Hierarchy: - send-0.11.1.tgz (Root Library) - :x: fresh-0.2.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Brenda-Jacobs/commit/8b710e312525a6b8c5c2de0698af2c35e0a6c1f7">8b710e312525a6b8c5c2de0698af2c35e0a6c1f7</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119>CVE-2017-16119</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: fresh - 0.5.2</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"fresh","packageVersion":"0.2.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"send:0.11.1;fresh:0.2.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"fresh - 0.5.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16119","vulnerabilityDetails":"Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->	non_defect	cve high detected in fresh tgz autoclosed cve high severity vulnerability vulnerable library fresh tgz http response freshness testing library home page a href path to dependency file brenda jacobs package json path to vulnerable library brenda jacobs node modules fresh package json dependency hierarchy send tgz root library x fresh tgz vulnerable library found in head commit a href found in base branch master vulnerability details fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution fresh isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree send fresh isminimumfixversionavailable true minimumfixversion fresh basebranches vulnerabilityidentifier cve vulnerabilitydetails fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition vulnerabilityurl	0
27,546	5,047,520,154	IssuesEvent	2016-12-20 09:42:27	JohnAustinDev/osis-converters	https://api.github.com/repos/JohnAustinDev/osis-converters	closed	.conf Feature settings	auto-migrated Priority-High Type-Defect	``` Some .conf Feature settings (such as Glossary and Images) need to be added when appropriate. ``` Original issue reported on code.google.com by `gpl.prog...@gmail.com` on 2 Aug 2013 at 5:44	1.0	.conf Feature settings - ``` Some .conf Feature settings (such as Glossary and Images) need to be added when appropriate. ``` Original issue reported on code.google.com by `gpl.prog...@gmail.com` on 2 Aug 2013 at 5:44	defect	conf feature settings some conf feature settings such as glossary and images need to be added when appropriate original issue reported on code google com by gpl prog gmail com on aug at	1
98,237	20,622,864,988	IssuesEvent	2022-03-07 19:13:10	withfig/fig	https://api.github.com/repos/withfig/fig	opened	CLI not working	bug codebase:cli placeholder	Most of the time this is really an issue with something else If the Fig CLI isn't working, please comment relevant info here! * Run `fig diagnostic` if you can * Run `fig doctor` if you can * Share your $PATH * Anything else that might help	1.0	CLI not working - Most of the time this is really an issue with something else If the Fig CLI isn't working, please comment relevant info here! * Run `fig diagnostic` if you can * Run `fig doctor` if you can * Share your $PATH * Anything else that might help	non_defect	cli not working most of the time this is really an issue with something else if the fig cli isn t working please comment relevant info here run fig diagnostic if you can run fig doctor if you can share your path anything else that might help	0
33,190	27,292,763,665	IssuesEvent	2023-02-23 17:47:06	google/site-kit-wp	https://api.github.com/repos/google/site-kit-wp	closed	Add support for Site Kit Service's playground environment	P0 Type: Infrastructure	Site Kit supports overriding the Site Kit Service base URL to use via the `GOOGLESITEKIT_PROXY_URL` (only used for internal debugging and testing). However that constant only works with an allowlist of URLs. Since Site Kit Service now has a new "playground" environment called `site-kit-local`, we will need to add support for it as well, in addition to the existing staging environment called `site-kit-dev`. --------------- _Do not alter or remove anything below. The following sections will be managed by moderators only._ ## Acceptance criteria * It should be possible to use the value `https://site-kit-local.appspot.com` in the `GOOGLESITEKIT_PROXY_URL` constant. ## Implementation Brief * Add new `DEVELOPMENT_BASE_URL` constant to `Google_Proxy` class with the URL from the ACs. * Modify `Google_Proxy::url()` to also allow that value when provided in the `GOOGLESITEKIT_PROXY_URL` constant. ### Test Coverage * N/A ## QA Brief * With Site Kit currently not being set up (e.g. after a reset), set the constant `GOOGLESITEKIT_PROXY_URL` to `https://site-kit-local.appspot.com`, e.g. in your `wp-config.php`. * Verify that when starting the setup flow, you land on a URL that starts with `https://site-kit-local.appspot.com`. * It is not necessary for QA of this issue to complete the setup flow. There is a chance that that environment is not fully working yet, which is okay for the scope of this issue. ## Changelog entry * N/A	1.0	Add support for Site Kit Service's playground environment - Site Kit supports overriding the Site Kit Service base URL to use via the `GOOGLESITEKIT_PROXY_URL` (only used for internal debugging and testing). However that constant only works with an allowlist of URLs. Since Site Kit Service now has a new "playground" environment called `site-kit-local`, we will need to add support for it as well, in addition to the existing staging environment called `site-kit-dev`. --------------- _Do not alter or remove anything below. The following sections will be managed by moderators only._ ## Acceptance criteria * It should be possible to use the value `https://site-kit-local.appspot.com` in the `GOOGLESITEKIT_PROXY_URL` constant. ## Implementation Brief * Add new `DEVELOPMENT_BASE_URL` constant to `Google_Proxy` class with the URL from the ACs. * Modify `Google_Proxy::url()` to also allow that value when provided in the `GOOGLESITEKIT_PROXY_URL` constant. ### Test Coverage * N/A ## QA Brief * With Site Kit currently not being set up (e.g. after a reset), set the constant `GOOGLESITEKIT_PROXY_URL` to `https://site-kit-local.appspot.com`, e.g. in your `wp-config.php`. * Verify that when starting the setup flow, you land on a URL that starts with `https://site-kit-local.appspot.com`. * It is not necessary for QA of this issue to complete the setup flow. There is a chance that that environment is not fully working yet, which is okay for the scope of this issue. ## Changelog entry * N/A	non_defect	add support for site kit service s playground environment site kit supports overriding the site kit service base url to use via the googlesitekit proxy url only used for internal debugging and testing however that constant only works with an allowlist of urls since site kit service now has a new playground environment called site kit local we will need to add support for it as well in addition to the existing staging environment called site kit dev do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria it should be possible to use the value in the googlesitekit proxy url constant implementation brief add new development base url constant to google proxy class with the url from the acs modify google proxy url to also allow that value when provided in the googlesitekit proxy url constant test coverage n a qa brief with site kit currently not being set up e g after a reset set the constant googlesitekit proxy url to e g in your wp config php verify that when starting the setup flow you land on a url that starts with it is not necessary for qa of this issue to complete the setup flow there is a chance that that environment is not fully working yet which is okay for the scope of this issue changelog entry n a	0
230,953	7,621,829,576	IssuesEvent	2018-05-03 09:54:35	InFact-coop/infactcoop.com	https://api.github.com/repos/InFact-coop/infactcoop.com	opened	Our Story section	Priority-2 Section T4h	In which we talk a bit about us and how we came to fruition, and the kind of projects (charity, small business, public sector) we like to work on, and then link to a different view outlining these things in more detail.	1.0	Our Story section - In which we talk a bit about us and how we came to fruition, and the kind of projects (charity, small business, public sector) we like to work on, and then link to a different view outlining these things in more detail.	non_defect	our story section in which we talk a bit about us and how we came to fruition and the kind of projects charity small business public sector we like to work on and then link to a different view outlining these things in more detail	0
52,293	13,218,998,762	IssuesEvent	2020-08-17 09:42:18	hazelcast/hazelcast	https://api.github.com/repos/hazelcast/hazelcast	opened	Near Cache is not controlled by Split Brain Protection	Type: Defect	<!-- Thanks for reporting your issue. Please share with us the following information, to help us resolve your issue quickly and efficiently. --> Describe the bug When split brain isn't happened, near cache caches correct data for service. Then split brain happens, the service which caches by near cache is still returning correct response. Expected behavior when split brain has happened, all service shuold be forbidden. To Reproduce Steps to reproduce the behavior: 1. split brain not happens 2. near cache caches the correct response to service 3. split brain happens 4. try to request the service on step 2 Additional context - in spring boot project，use embed hazelcast 4.0.1 - set Near Cache - set Split Brain Protection - set SplitBrainProtectionOn.READ_WRITE - use MemberCountSpitBrainProtectionFuntion - JDK 8 <!-- Add any other context about the problem here. Common details that we're often interested in: - Detailed description of the steps to reproduce your issue - Logs and stack traces, if available - Hazelcast version that you use (e.g. 3.4, also specify whether it is a minor release or the latest snapshot) - If available, integration module versions (e.g. Tomcat, Jetty, Spring, Hibernate). Also, include their detailed configuration information such as web.xml, Hibernate configuration and `context.xml` for Spring - Cluster size, i.e. the number of Hazelcast cluster members - Number of the clients - Version of Java. It is also helpful to mention the JVM parameters - Operating system. If it is Linux, kernel version is helpful - Unit test with the `hazelcast.xml` file. If you could include a unit test which reproduces your issue, we would be grateful -->	1.0	Near Cache is not controlled by Split Brain Protection - <!-- Thanks for reporting your issue. Please share with us the following information, to help us resolve your issue quickly and efficiently. --> Describe the bug When split brain isn't happened, near cache caches correct data for service. Then split brain happens, the service which caches by near cache is still returning correct response. Expected behavior when split brain has happened, all service shuold be forbidden. To Reproduce Steps to reproduce the behavior: 1. split brain not happens 2. near cache caches the correct response to service 3. split brain happens 4. try to request the service on step 2 Additional context - in spring boot project，use embed hazelcast 4.0.1 - set Near Cache - set Split Brain Protection - set SplitBrainProtectionOn.READ_WRITE - use MemberCountSpitBrainProtectionFuntion - JDK 8 <!-- Add any other context about the problem here. Common details that we're often interested in: - Detailed description of the steps to reproduce your issue - Logs and stack traces, if available - Hazelcast version that you use (e.g. 3.4, also specify whether it is a minor release or the latest snapshot) - If available, integration module versions (e.g. Tomcat, Jetty, Spring, Hibernate). Also, include their detailed configuration information such as web.xml, Hibernate configuration and `context.xml` for Spring - Cluster size, i.e. the number of Hazelcast cluster members - Number of the clients - Version of Java. It is also helpful to mention the JVM parameters - Operating system. If it is Linux, kernel version is helpful - Unit test with the `hazelcast.xml` file. If you could include a unit test which reproduces your issue, we would be grateful -->	defect	near cache is not controlled by split brain protection thanks for reporting your issue please share with us the following information to help us resolve your issue quickly and efficiently describe the bug when split brain isn t happened near cache caches correct data for service then split brain happens the service which caches by near cache is still returning correct response expected behavior when split brain has happened all service shuold be forbidden to reproduce steps to reproduce the behavior split brain not happens near cache caches the correct response to service split brain happens try to request the service on step additional context in spring boot project，use embed hazelcast set near cache set split brain protection set splitbrainprotectionon read write use membercountspitbrainprotectionfuntion jdk add any other context about the problem here common details that we re often interested in detailed description of the steps to reproduce your issue logs and stack traces if available hazelcast version that you use e g also specify whether it is a minor release or the latest snapshot if available integration module versions e g tomcat jetty spring hibernate also include their detailed configuration information such as web xml hibernate configuration and context xml for spring cluster size i e the number of hazelcast cluster members number of the clients version of java it is also helpful to mention the jvm parameters operating system if it is linux kernel version is helpful unit test with the hazelcast xml file if you could include a unit test which reproduces your issue we would be grateful	1
1,529	2,603,967,017	IssuesEvent	2015-02-24 18:59:17	chrsmith/nishazi6	https://api.github.com/repos/chrsmith/nishazi6	opened	沈阳龟头上长有白色疙瘩	auto-migrated Priority-Medium Type-Defect	``` 沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓TEL：02 4-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治療� ��位于沈陽市沈河區二緯路32號。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 ``` ----- Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:08	1.0	沈阳龟头上长有白色疙瘩 - ``` 沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓TEL：02 4-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治療� ��位于沈陽市沈河區二緯路32號。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 ``` ----- Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:08	defect	沈阳龟头上长有白色疙瘩沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓tel：〓， � �� 。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 original issue reported on code google com by gmail com on jun at	1
18,440	3,061,246,092	IssuesEvent	2015-08-15 10:04:17	google/mozc	https://api.github.com/repos/google/mozc	closed	Preedit and candidate changes buffer modification flag.	auto-migrated Priority-Medium Type-Defect	``` What steps will reproduce the problem? 1. setup mozc.el under emacs. 2. activate mozc, and input something in preedit on unmodified buffer. 3. push ESC for clear preedit string. What is the expected output? The buffer modification flag isn't changed. (keep unmodified) What do you see instead? The buffer modification flag is turned on. What version of the product are you using? On what operating system? 2.16.1924.102 Please provide any additional information below. A propose patch is attached. ``` Original issue reported on code.google.com by `d588...@gmail.com` on 24 Nov 2014 at 11:14 Attachments: * [mozc-el-diff](https://storage.googleapis.com/google-code-attachments/mozc/issue-254/comment-0/mozc-el-diff)	1.0	Preedit and candidate changes buffer modification flag. - ``` What steps will reproduce the problem? 1. setup mozc.el under emacs. 2. activate mozc, and input something in preedit on unmodified buffer. 3. push ESC for clear preedit string. What is the expected output? The buffer modification flag isn't changed. (keep unmodified) What do you see instead? The buffer modification flag is turned on. What version of the product are you using? On what operating system? 2.16.1924.102 Please provide any additional information below. A propose patch is attached. ``` Original issue reported on code.google.com by `d588...@gmail.com` on 24 Nov 2014 at 11:14 Attachments: * [mozc-el-diff](https://storage.googleapis.com/google-code-attachments/mozc/issue-254/comment-0/mozc-el-diff)	defect	preedit and candidate changes buffer modification flag what steps will reproduce the problem setup mozc el under emacs activate mozc and input something in preedit on unmodified buffer push esc for clear preedit string what is the expected output the buffer modification flag isn t changed keep unmodified what do you see instead the buffer modification flag is turned on what version of the product are you using on what operating system please provide any additional information below a propose patch is attached original issue reported on code google com by gmail com on nov at attachments	1
325,976	27,971,796,196	IssuesEvent	2023-03-25 04:54:39	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	opened	pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test: TestLogic_propagate_input_ordering failed	C-test-failure O-robot branch-master	pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test.TestLogic_propagate_input_ordering [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=artifacts#/) on master @ [9a0d4932cd634034070a7e5ca91559e8d67d8fbe](https://github.com/cockroachdb/cockroach/commits/9a0d4932cd634034070a7e5ca91559e8d67d8fbe): Fatal error: ``` panic: test timed out after 59m55s ``` Stack: ``` goroutine 46816 [running]: testing.(M).startAlarm.func1() GOROOT/src/testing/testing.go:2036 +0x88 created by time.goFunc GOROOT/src/time/sleep.go:176 +0x38 ``` <details><summary>Log preceding fatal error</summary> <p> ``` runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x40041386c0?, 0x5d59440?}}, 0x40019c1f98) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4697fc0?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38570 [select, 2 minutes]: * github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue.func2() * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:388 +0x7c * created by github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:385 +0x30c * * goroutine 39107 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x4005a2e510}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4000729500?, 0x0?}}, 0x400001a798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x400001a758?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38610 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x400974e030}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4007d7cae6?, 0x100000000000000?}}, 0x4001398798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4002c5b330?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 41560 [select, 2 minutes]: * database/sql.(DB).connectionOpener(0x4003f58750, {0x5d59398, 0x40050e8300}) GOROOT/src/database/sql/sql.go:1224 +0x80 * created by database/sql.OpenDB * GOROOT/src/database/sql/sql.go:792 +0x184 * * goroutine 38630 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x4002f5aa50}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x5d59401?, 0x0?}}, 0x40013e4798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4006cb1380?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * ``` </p> </details> <details><summary>Help</summary> <p> See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </p> </details> /cc @cockroachdb/sql-queries <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.TestLogic_propagate_input_ordering.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>	1.0	pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test: TestLogic_propagate_input_ordering failed - pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test.TestLogic_propagate_input_ordering [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=artifacts#/) on master @ [9a0d4932cd634034070a7e5ca91559e8d67d8fbe](https://github.com/cockroachdb/cockroach/commits/9a0d4932cd634034070a7e5ca91559e8d67d8fbe): Fatal error: ``` panic: test timed out after 59m55s ``` Stack: ``` goroutine 46816 [running]: testing.(M).startAlarm.func1() GOROOT/src/testing/testing.go:2036 +0x88 created by time.goFunc GOROOT/src/time/sleep.go:176 +0x38 ``` <details><summary>Log preceding fatal error</summary> <p> ``` runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x40041386c0?, 0x5d59440?}}, 0x40019c1f98) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4697fc0?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38570 [select, 2 minutes]: * github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue.func2() * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:388 +0x7c * created by github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:385 +0x30c * * goroutine 39107 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x4005a2e510}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4000729500?, 0x0?}}, 0x400001a798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x400001a758?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38610 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x400974e030}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4007d7cae6?, 0x100000000000000?}}, 0x4001398798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4002c5b330?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 41560 [select, 2 minutes]: * database/sql.(DB).connectionOpener(0x4003f58750, {0x5d59398, 0x40050e8300}) GOROOT/src/database/sql/sql.go:1224 +0x80 * created by database/sql.OpenDB * GOROOT/src/database/sql/sql.go:792 +0x184 * * goroutine 38630 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop.func1({0x5d59440, 0x4002f5aa50}) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x5d59401?, 0x0?}}, 0x40013e4798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(tableCacheShard).releaseLoop(0x4006cb1380?) github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(tableCacheShard).init github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * ``` </p> </details> <details><summary>Help</summary> <p> See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </p> </details> /cc @cockroachdb/sql-queries <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.TestLogic_propagate_input_ordering.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>	non_defect	pkg sql logictest tests fakedist vec off fakedist vec off test testlogic propagate input ordering failed pkg sql logictest tests fakedist vec off fakedist vec off test testlogic propagate input ordering with on master fatal error panic test timed out after stack goroutine testing m startalarm goroot src testing testing go created by time gofunc goroot src time sleep go log preceding fatal error runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine github com cockroachdb cockroach pkg util admission initworkqueue github com cockroachdb cockroach pkg util admission work queue go created by github com cockroachdb cockroach pkg util admission initworkqueue github com cockroachdb cockroach pkg util admission work queue go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine database sql db connectionopener goroot src database sql sql go created by database sql opendb goroot src database sql sql go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go help see also cc cockroachdb sql queries	0
69,557	22,494,962,494	IssuesEvent	2022-06-23 06:39:28	ankitpokhrel/jira-cli	https://api.github.com/repos/ankitpokhrel/jira-cli	closed	Assigning issue to self doesn't assign it	defect help wanted jira server	Describe the bug <!--- A clear and concise description of what the bug is. ---> Running the following command doesn't assign the issue to me, instead the user search opens up, in which I'm unfindable as well. ```sh jira issue assign "TICKET-CODE" "$(jira me)" ``` Please provide following details 1. JiraCLI Version: ``` (Version="0.1.1", GitCommit="6663763b44a2e5d328b551ae7d2f1a37d1e232ae", GoVersion="go1.17.2", BuildDate="2021-11-03"", Compiler="gc", Platform="darwin/amd64") ``` 2. Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation. ``` Jira Server v8.20.0 ``` 3. What operating system are you using? Also mention version. ``` macOS 12.0.1 ``` 4. What terminal are you using? Also mention version. ``` alacritty 0.9.0 (fed349a) ``` To Reproduce Steps to reproduce the behavior: 1. Run `jira issue assign "TICKET-CODE" "$(jira me)"` 2. Issue isn't assigned to you, user search is opened up 3. Probably a separate issue but no names past the initial cropped list are findable Expected behavior <!--- A clear and concise description of what you expected to happen. ---> The issue would be assigned to me. Additional context <!--- Add any other context about the problem here. ---> Not that it's relevant here but I'm using the line in the following function: ```sh # Move an issue back to progress jmbk() { jira issue transition "$1" "Back To Progress" jira issue assign "$1" "$(jira me)" } ```	1.0	Assigning issue to self doesn't assign it - Describe the bug <!--- A clear and concise description of what the bug is. ---> Running the following command doesn't assign the issue to me, instead the user search opens up, in which I'm unfindable as well. ```sh jira issue assign "TICKET-CODE" "$(jira me)" ``` Please provide following details 1. JiraCLI Version: ``` (Version="0.1.1", GitCommit="6663763b44a2e5d328b551ae7d2f1a37d1e232ae", GoVersion="go1.17.2", BuildDate="2021-11-03"", Compiler="gc", Platform="darwin/amd64") ``` 2. Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation. ``` Jira Server v8.20.0 ``` 3. What operating system are you using? Also mention version. ``` macOS 12.0.1 ``` 4. What terminal are you using? Also mention version. ``` alacritty 0.9.0 (fed349a) ``` To Reproduce Steps to reproduce the behavior: 1. Run `jira issue assign "TICKET-CODE" "$(jira me)"` 2. Issue isn't assigned to you, user search is opened up 3. Probably a separate issue but no names past the initial cropped list are findable Expected behavior <!--- A clear and concise description of what you expected to happen. ---> The issue would be assigned to me. Additional context <!--- Add any other context about the problem here. ---> Not that it's relevant here but I'm using the line in the following function: ```sh # Move an issue back to progress jmbk() { jira issue transition "$1" "Back To Progress" jira issue assign "$1" "$(jira me)" } ```	defect	assigning issue to self doesn t assign it describe the bug running the following command doesn t assign the issue to me instead the user search opens up in which i m unfindable as well sh jira issue assign ticket code jira me please provide following details jiracli version version gitcommit goversion builddate compiler gc platform darwin are you using jira cloud or on premise jira server also mention the version for on premise installation jira server what operating system are you using also mention version macos what terminal are you using also mention version alacritty to reproduce steps to reproduce the behavior run jira issue assign ticket code jira me issue isn t assigned to you user search is opened up probably a separate issue but no names past the initial cropped list are findable expected behavior the issue would be assigned to me additional context not that it s relevant here but i m using the line in the following function sh move an issue back to progress jmbk jira issue transition back to progress jira issue assign jira me	1
711,050	24,448,849,107	IssuesEvent	2022-10-06 20:33:47	pytorch/pytorch	https://api.github.com/repos/pytorch/pytorch	closed	Investigate binary validation failure nightly linux 3.9 cuda 11.6	high priority module: ci triaged	### 🐛 Describe the bug Failure: https://github.com/pytorch/builder/actions/runs/3018052016/jobs/4939894670 ``` done + conda run -p conda-env-3018052016 python3 ./test/smoke_test/smoke_test.py ERROR conda.cli.main_run:execute(41): `conda run python3 ./test/smoke_test/smoke_test.py` failed. (See above for error) Traceback (most recent call last): File "/root/work/builder/builder/./test/smoke_test/smoke_test.py", line 5, in <module> import torchaudio File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/__init__.py", line 1, in <module> from torchaudio import ( # noqa: F401 File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 103, in <module> _init_extension() File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 88, in _init_extension _load_lib("libtorchaudio") File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 51, in _load_lib torch.ops.load_library(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torch/_ops.py", line 481, in load_library ctypes.CDLL(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/ctypes/__init__.py", line 382, in __init__ self._handle = _dlopen(self._name, mode) OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory ``` ### Versions nightly 1.13 cc @ezyang @gchanan @zou3519 @seemethere @malfet @pytorch/pytorch-dev-infra @weiwangmeta	1.0	Investigate binary validation failure nightly linux 3.9 cuda 11.6 - ### 🐛 Describe the bug Failure: https://github.com/pytorch/builder/actions/runs/3018052016/jobs/4939894670 ``` done + conda run -p conda-env-3018052016 python3 ./test/smoke_test/smoke_test.py ERROR conda.cli.main_run:execute(41): `conda run python3 ./test/smoke_test/smoke_test.py` failed. (See above for error) Traceback (most recent call last): File "/root/work/builder/builder/./test/smoke_test/smoke_test.py", line 5, in <module> import torchaudio File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/__init__.py", line 1, in <module> from torchaudio import ( # noqa: F401 File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 103, in <module> _init_extension() File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 88, in _init_extension _load_lib("libtorchaudio") File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 51, in _load_lib torch.ops.load_library(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torch/_ops.py", line 481, in load_library ctypes.CDLL(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/ctypes/__init__.py", line 382, in __init__ self._handle = _dlopen(self._name, mode) OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory ``` ### Versions nightly 1.13 cc @ezyang @gchanan @zou3519 @seemethere @malfet @pytorch/pytorch-dev-infra @weiwangmeta	non_defect	investigate binary validation failure nightly linux cuda 🐛 describe the bug failure done conda run p conda env test smoke test smoke test py error conda cli main run execute conda run test smoke test smoke test py failed see above for error traceback most recent call last file root work builder builder test smoke test smoke test py line in import torchaudio file root work builder builder conda env lib site packages torchaudio init py line in from torchaudio import noqa file root work builder builder conda env lib site packages torchaudio extension py line in init extension file root work builder builder conda env lib site packages torchaudio extension py line in init extension load lib libtorchaudio file root work builder builder conda env lib site packages torchaudio extension py line in load lib torch ops load library path file root work builder builder conda env lib site packages torch ops py line in load library ctypes cdll path file root work builder builder conda env lib ctypes init py line in init self handle dlopen self name mode oserror libtorch cuda cpp so cannot open shared object file no such file or directory versions nightly cc ezyang gchanan seemethere malfet pytorch pytorch dev infra weiwangmeta	0
107,829	13,524,195,118	IssuesEvent	2020-09-15 11:09:18	nextcloud/desktop	https://api.github.com/repos/nextcloud/desktop	closed	3.0.1 new activity feed does not show filenames	design enhancement feature: :cloud: system tray feature: :zap: activity and :bell: notification	### Expected behaviour If I read an entry in the activity feed, I want to know which file caused the entry. ### Actual behaviour The feed does not show the file name. It displays the file name including the path (with sync folder as root), but the path is cut as it is to long for the feed. As it is cut at the end, the file name is not readable at all. There is also no baloon tooltip that shows the full path. ### Steps to reproduce 1. Open activity feed (click once on the task bar/info bar icon) 2. Look at any activity entry ### Client configuration Client version: 3.0.1 Operating system: Windows 10 OS language: German Installation path of client: C:\Program FIles\Nextcloud ### Logs As this is a design issue, logs do not make sense.	1.0	3.0.1 new activity feed does not show filenames - ### Expected behaviour If I read an entry in the activity feed, I want to know which file caused the entry. ### Actual behaviour The feed does not show the file name. It displays the file name including the path (with sync folder as root), but the path is cut as it is to long for the feed. As it is cut at the end, the file name is not readable at all. There is also no baloon tooltip that shows the full path. ### Steps to reproduce 1. Open activity feed (click once on the task bar/info bar icon) 2. Look at any activity entry ### Client configuration Client version: 3.0.1 Operating system: Windows 10 OS language: German Installation path of client: C:\Program FIles\Nextcloud ### Logs As this is a design issue, logs do not make sense.	non_defect	new activity feed does not show filenames expected behaviour if i read an entry in the activity feed i want to know which file caused the entry actual behaviour the feed does not show the file name it displays the file name including the path with sync folder as root but the path is cut as it is to long for the feed as it is cut at the end the file name is not readable at all there is also no baloon tooltip that shows the full path steps to reproduce open activity feed click once on the task bar info bar icon look at any activity entry client configuration client version operating system windows os language german installation path of client c program files nextcloud logs as this is a design issue logs do not make sense	0
72,108	23,947,307,632	IssuesEvent	2022-09-12 08:30:58	vector-im/element-android	https://api.github.com/repos/vector-im/element-android	closed	Push notification not working (Google Play variant)	T-Defect A-Notifications S-Critical O-Occasional	### Steps to reproduce Trouble shooting Notification is stuck on "Test Push". Self hosted synapse homeserver is on 1.65, and Android client is 1.4.32 ![image](https://user-images.githubusercontent.com/379266/185794099-3986846d-2131-4ffb-9d82-7e73410321bc.png) ### Outcome Push notification is not received. ### Your phone model Samsung Note 9 ### Operating system version Android 10 ### Application version and app store Element Android 1.4.32 ### Homeserver 1.65.0 ### Will you send logs? Yes ### Are you willing to provide a PR? No	1.0	Push notification not working (Google Play variant) - ### Steps to reproduce Trouble shooting Notification is stuck on "Test Push". Self hosted synapse homeserver is on 1.65, and Android client is 1.4.32 ![image](https://user-images.githubusercontent.com/379266/185794099-3986846d-2131-4ffb-9d82-7e73410321bc.png) ### Outcome Push notification is not received. ### Your phone model Samsung Note 9 ### Operating system version Android 10 ### Application version and app store Element Android 1.4.32 ### Homeserver 1.65.0 ### Will you send logs? Yes ### Are you willing to provide a PR? No	defect	push notification not working google play variant steps to reproduce trouble shooting notification is stuck on test push self hosted synapse homeserver is on and android client is outcome push notification is not received your phone model samsung note operating system version android application version and app store element android homeserver will you send logs yes are you willing to provide a pr no	1
40,819	10,168,548,788	IssuesEvent	2019-08-07 21:06:49	scipy/scipy	https://api.github.com/repos/scipy/scipy	closed	Strictly increasing requirement in UnivariateSpline	Documentation defect scipy.interpolate	I am trying to describe a large dataset using an Univariate spline. With a previous Scipy 0.19 version this worked nicely, now the same data gives with a current Scipy 1.0 the error message > x must be strictly increasing According to the current documentation at https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.UnivariateSpline.html it is enough if x is increasing. The error message is caused by the commit https://github.com/scipy/scipy/commit/8b37277f721eb0f69b2aa4644a961ba0b84e665c which adds a checks for strictly increasing x. On the other hand in the issue https://github.com/scipy/scipy/issues/1753 it is mentioned that the strictly increasing requirement has been lifted already. So does the current documentation need to be updated to include the "strictly" requirement or would a test for increasing x be sufficient? I am not familiar with the underlying routines and maybe overlooking some detail here.	1.0	Strictly increasing requirement in UnivariateSpline - I am trying to describe a large dataset using an Univariate spline. With a previous Scipy 0.19 version this worked nicely, now the same data gives with a current Scipy 1.0 the error message > x must be strictly increasing According to the current documentation at https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.UnivariateSpline.html it is enough if x is increasing. The error message is caused by the commit https://github.com/scipy/scipy/commit/8b37277f721eb0f69b2aa4644a961ba0b84e665c which adds a checks for strictly increasing x. On the other hand in the issue https://github.com/scipy/scipy/issues/1753 it is mentioned that the strictly increasing requirement has been lifted already. So does the current documentation need to be updated to include the "strictly" requirement or would a test for increasing x be sufficient? I am not familiar with the underlying routines and maybe overlooking some detail here.	defect	strictly increasing requirement in univariatespline i am trying to describe a large dataset using an univariate spline with a previous scipy version this worked nicely now the same data gives with a current scipy the error message x must be strictly increasing according to the current documentation at it is enough if x is increasing the error message is caused by the commit which adds a checks for strictly increasing x on the other hand in the issue it is mentioned that the strictly increasing requirement has been lifted already so does the current documentation need to be updated to include the strictly requirement or would a test for increasing x be sufficient i am not familiar with the underlying routines and maybe overlooking some detail here	1
13,152	8,816,084,743	IssuesEvent	2018-12-30 04:52:13	pixelfed/pixelfed	https://api.github.com/repos/pixelfed/pixelfed	closed	Please add support for Blind Key Rotation (privacy feature)	activitypub security work in progress	### Background Blind Key Rotation is a mitigation for the problem that JSON-LD Linked Data Signatures are irrevocable. It is also useful (albeit less so) in the context of HTTP Signatures, since HTTP Signatures only sign headers and not the object itself, and are also detached from the object. ### Implementation - receiving objects Supporting Blind Key Rotation in the validation pipeline is simple enough: if a signature validation fails, refetch the remote actor and recheck the signature accordingly. ### Implementation - deleting objects Supporting Blind Key Rotation to enhance the deniability of deleted objects is also simple enough: send the `Delete` signed with the original key and then silently replace the keypair. The new keys will be fetched when the user publishes new content. ### Questions? Contact me on fediverse: https://pleroma.site/kaniini	True	Please add support for Blind Key Rotation (privacy feature) - ### Background Blind Key Rotation is a mitigation for the problem that JSON-LD Linked Data Signatures are irrevocable. It is also useful (albeit less so) in the context of HTTP Signatures, since HTTP Signatures only sign headers and not the object itself, and are also detached from the object. ### Implementation - receiving objects Supporting Blind Key Rotation in the validation pipeline is simple enough: if a signature validation fails, refetch the remote actor and recheck the signature accordingly. ### Implementation - deleting objects Supporting Blind Key Rotation to enhance the deniability of deleted objects is also simple enough: send the `Delete` signed with the original key and then silently replace the keypair. The new keys will be fetched when the user publishes new content. ### Questions? Contact me on fediverse: https://pleroma.site/kaniini	non_defect	please add support for blind key rotation privacy feature background blind key rotation is a mitigation for the problem that json ld linked data signatures are irrevocable it is also useful albeit less so in the context of http signatures since http signatures only sign headers and not the object itself and are also detached from the object implementation receiving objects supporting blind key rotation in the validation pipeline is simple enough if a signature validation fails refetch the remote actor and recheck the signature accordingly implementation deleting objects supporting blind key rotation to enhance the deniability of deleted objects is also simple enough send the delete signed with the original key and then silently replace the keypair the new keys will be fetched when the user publishes new content questions contact me on fediverse	0
32,065	26,398,389,436	IssuesEvent	2023-01-12 21:48:43	woocommerce/woocommerce	https://api.github.com/repos/woocommerce/woocommerce	closed	Code Freeze: Automation broken	status: prioritization tool: monorepo infrastructure	<!-- This form is for other issue types specific to the WooCommerce plugin. This is not a support portal. --> Prerequisites (mark completed items with an [x]): - [x] I have checked that my issue type is not listed here https://github.com/woocommerce/woocommerce/issues/new/choose - [x] My issue is not a security issue, support request, bug report, enhancement or feature request (Please use the link above if it is). Issue Description: Code Freeze action doesn't complete. This causes the release lead to have to make manual PRs introducing the potential for errors. First, a `pnpm-lock.yaml` change caused a failure https://github.com/woocommerce/woocommerce/actions/runs/3738934217/jobs/6345560765 I solved this in just the branch with a `git checkout pnpm-lock.yaml` and ran into the next error https://github.com/woocommerce/woocommerce/actions/runs/3739098586/jobs/6345912026 I'm not sure why there was a conflict	1.0	Code Freeze: Automation broken - <!-- This form is for other issue types specific to the WooCommerce plugin. This is not a support portal. --> Prerequisites (mark completed items with an [x]): - [x] I have checked that my issue type is not listed here https://github.com/woocommerce/woocommerce/issues/new/choose - [x] My issue is not a security issue, support request, bug report, enhancement or feature request (Please use the link above if it is). Issue Description: Code Freeze action doesn't complete. This causes the release lead to have to make manual PRs introducing the potential for errors. First, a `pnpm-lock.yaml` change caused a failure https://github.com/woocommerce/woocommerce/actions/runs/3738934217/jobs/6345560765 I solved this in just the branch with a `git checkout pnpm-lock.yaml` and ran into the next error https://github.com/woocommerce/woocommerce/actions/runs/3739098586/jobs/6345912026 I'm not sure why there was a conflict	non_defect	code freeze automation broken prerequisites mark completed items with an i have checked that my issue type is not listed here my issue is not a security issue support request bug report enhancement or feature request please use the link above if it is issue description code freeze action doesn t complete this causes the release lead to have to make manual prs introducing the potential for errors first a pnpm lock yaml change caused a failure i solved this in just the branch with a git checkout pnpm lock yaml and ran into the next error i m not sure why there was a conflict	0
220,461	16,960,107,833	IssuesEvent	2021-06-29 01:44:31	RaRe-Technologies/gensim	https://api.github.com/repos/RaRe-Technologies/gensim	closed	Documentation of strip_punctuation vs strip_punctuation2 in gensim.parsing.preprocessing	documentation	Thanks for all the hard work on this fantastic library. I found a small quirk today, not really a bug, just a bit of a rough edge: In `gensim.parsing` [preprocessing.py ](https://github.com/RaRe-Technologies/gensim/blob/e210f73c42c5df5a511ca27166cbc7d10970eab2/gensim/parsing/preprocessing.py#L121) `strip_punctuation2` is defined: `strip_punctuation2 = strip_punctuation`. In the [documentation](https://radimrehurek.com/gensim/parsing/preprocessing.html) the description of [`strip_punctuation2`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation2) is a duplication of [`strip_punctuation`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation) rather than a statement of equality. I noticed this while reading the documentation and, assuming I was missing an obvious distinction, attempting to hand diff the the docs for the two functions. When I gave up and flipped to the source it became obvious how the two functions are related.	1.0	Documentation of strip_punctuation vs strip_punctuation2 in gensim.parsing.preprocessing - Thanks for all the hard work on this fantastic library. I found a small quirk today, not really a bug, just a bit of a rough edge: In `gensim.parsing` [preprocessing.py ](https://github.com/RaRe-Technologies/gensim/blob/e210f73c42c5df5a511ca27166cbc7d10970eab2/gensim/parsing/preprocessing.py#L121) `strip_punctuation2` is defined: `strip_punctuation2 = strip_punctuation`. In the [documentation](https://radimrehurek.com/gensim/parsing/preprocessing.html) the description of [`strip_punctuation2`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation2) is a duplication of [`strip_punctuation`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation) rather than a statement of equality. I noticed this while reading the documentation and, assuming I was missing an obvious distinction, attempting to hand diff the the docs for the two functions. When I gave up and flipped to the source it became obvious how the two functions are related.	non_defect	documentation of strip punctuation vs strip in gensim parsing preprocessing thanks for all the hard work on this fantastic library i found a small quirk today not really a bug just a bit of a rough edge in gensim parsing strip is defined strip strip punctuation in the the description of is a duplication of rather than a statement of equality i noticed this while reading the documentation and assuming i was missing an obvious distinction attempting to hand diff the the docs for the two functions when i gave up and flipped to the source it became obvious how the two functions are related	0
6,652	2,610,258,440	IssuesEvent	2015-02-26 19:22:26	chrsmith/dsdsdaadf	https://api.github.com/repos/chrsmith/dsdsdaadf	opened	深圳激光治痘痘	auto-migrated Priority-Medium Type-Defect	``` 深圳激光治痘痘【深圳韩方科颜全国热线400-869-1818，24小时QQ4 008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:51	1.0	深圳激光治痘痘 - ``` 深圳激光治痘痘【深圳韩方科颜全国热线400-869-1818，24小时QQ4 008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:51	defect	深圳激光治痘痘深圳激光治痘痘【，】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� original issue reported on code google com by szft com on may at	1
121,362	15,893,811,257	IssuesEvent	2021-04-11 07:42:45	lopis/job-board	https://api.github.com/repos/lopis/job-board	closed	Create Job Listing Page	⚛️ React 🎨 Design	Create new Page component under `pages/` for displaying a single job listing. This requires creating a new API call to fetch a single job listing in full detail (as well as adapting the mocks)	1.0	Create Job Listing Page - Create new Page component under `pages/` for displaying a single job listing. This requires creating a new API call to fetch a single job listing in full detail (as well as adapting the mocks)	non_defect	create job listing page create new page component under pages for displaying a single job listing this requires creating a new api call to fetch a single job listing in full detail as well as adapting the mocks	0
173,013	21,094,381,199	IssuesEvent	2022-04-04 08:56:16	lukebroganws/NodeGoat	https://api.github.com/repos/lukebroganws/NodeGoat	closed	zaproxy-0.2.0.tgz: 18 vulnerabilities (highest severity is: 9.8) - autoclosed	security vulnerability	<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>zaproxy-0.2.0.tgz</b></p></summary> <p></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| --- \| --- \| \| [CVE-2018-1000620](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| cryptiles-0.2.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2019-10744](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2018-3728](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.8 \| hoek-0.9.1.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [WS-2014-0005](https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2016-2515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| hawk-1.0.0.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2021-44907](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| N/A \| ❌ \| \| [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| mime-1.2.11.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2014-10064](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2020-8203](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.4 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2021-23337](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.2 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2019-1010266](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2018-3721](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2017-16026](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.9 \| request-2.36.0.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2018-16487](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.6 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2020-28500](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2014-7191](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [WS-2017-0266](https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.5 \| http-signature-0.10.1.tgz \| Transitive \| 0.3.0 \| ✅ \| ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000620</summary> ### Vulnerable Library - <b>cryptiles-0.2.2.tgz</b></p> <p>General purpose crypto utilities</p> <p>Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/cryptiles/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: cryptiles-0.2.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2. <p>Publish Date: 2018-07-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620</a></p> <p>Release Date: 2018-07-09</p> <p>Fix Resolution (cryptiles): 4.1.2</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. <p>Publish Date: 2019-07-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744>CVE-2019-10744</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a></p> <p>Release Date: 2019-07-26</p> <p>Fix Resolution (lodash): 4.17.12</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-3728</summary> ### Vulnerable Library - <b>hoek-0.9.1.tgz</b></p> <p>General purpose node utilities</p> <p>Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz">https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/hoek/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: hoek-0.9.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. <p>Publish Date: 2018-03-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p> <p>Release Date: 2018-03-30</p> <p>Fix Resolution (hoek): 4.2.0</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0005</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time <p>Publish Date: 2014-07-31 <p>URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2014-0005">https://nvd.nist.gov/vuln/detail/WS-2014-0005</a></p> <p>Release Date: 2014-07-31</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2515</summary> ### Vulnerable Library - <b>hawk-1.0.0.tgz</b></p> <p>HTTP Hawk Authentication Scheme</p> <p>Library home page: <a href="https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz">https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/hawk/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: hawk-1.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression. <p>Publish Date: 2016-04-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515>CVE-2016-2515</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2515">https://nvd.nist.gov/vuln/detail/CVE-2016-2515</a></p> <p>Release Date: 2016-04-13</p> <p>Fix Resolution (hawk): 3.1.3</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44907</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior. <p>Publish Date: 2022-03-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907>CVE-2021-44907</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907</a></p> <p>Release Date: 2022-03-17</p> <p>Fix Resolution: qs - 6.8.1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - <b>mime-1.2.11.tgz</b></p> <p>A comprehensive library for mime-type mapping</p> <p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.11.tgz">https://registry.npmjs.org/mime/-/mime-1.2.11.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/mime/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: mime-1.2.11.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (mime): 1.4.1</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10064</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring. <p>Publish Date: 2018-05-31 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064>CVE-2014-10064</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10064">https://nvd.nist.gov/vuln/detail/CVE-2014-10064</a></p> <p>Release Date: 2018-05-31</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. <p>Publish Date: 2020-07-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p> <p>Release Date: 2020-07-15</p> <p>Fix Resolution (lodash): 4.17.9</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. <p>Publish Date: 2021-02-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. <p>Publish Date: 2019-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p> <p>Release Date: 2020-09-30</p> <p>Fix Resolution (lodash): 4.17.11</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (lodash): 4.17.5</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-16026</summary> ### Vulnerable Library - <b>request-2.36.0.tgz</b></p> <p>Simplified HTTP request client.</p> <p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.36.0.tgz">https://registry.npmjs.org/request/-/request-2.36.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/request/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: request-2.36.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 \|\| >2.51.0 <=2.67.0. <p>Publish Date: 2018-06-04 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026>CVE-2017-16026</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.9</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-16026">https://nvd.nist.gov/vuln/detail/CVE-2017-16026</a></p> <p>Release Date: 2018-06-04</p> <p>Fix Resolution (request): 2.68.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype. <p>Publish Date: 2019-02-01 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p> <p>Release Date: 2019-02-01</p> <p>Fix Resolution (lodash): 4.17.11</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash. <p>Publish Date: 2021-02-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-1000048</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash. <p>Publish Date: 2017-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a></p> <p>Release Date: 2017-07-17</p> <p>Fix Resolution (qs): 6.0.4</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. <p>Publish Date: 2014-10-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191>CVE-2014-7191</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a></p> <p>Release Date: 2014-10-19</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> WS-2017-0266</summary> ### Vulnerable Library - <b>http-signature-0.10.1.tgz</b></p> <p>Reference implementation of Joyent's HTTP Signature scheme.</p> <p>Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: http-signature-0.10.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure. <p>Publish Date: 2015-01-22 <p>URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>3.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a></p> <p>Release Date: 2015-01-22</p> <p>Fix Resolution (http-signature): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> <p>In order to enable automatic remediation, please create <a target="_blank" href="https://whitesource.atlassian.net/wiki/spaces/WD/pages/697696422/WhiteSource+for+GitHub.com#Remediate-Settings-(remediateSettings)">workflow rules</a></p> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> <!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1000620","vulnerabilityDetails":"Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-10744","vulnerabilityDetails":"Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3728","vulnerabilityDetails":"hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via \u0027merge\u0027 and \u0027applyToDefaults\u0027 functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2014-0005","vulnerabilityDetails":"Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time","vulnerabilityUrl":"https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2016-2515","vulnerabilityDetails":"Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"0.6.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"zaproxy:0.2.0;request:2.36.0;qs:0.6.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.8.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44907","vulnerabilityDetails":"A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16138","vulnerabilityDetails":"The mime module \u003c 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2014-10064","vulnerabilityDetails":"The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8203","vulnerabilityDetails":"Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-1010266","vulnerabilityDetails":"lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3721","vulnerabilityDetails":"lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16026","vulnerabilityDetails":"Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request \u003e\u003d2.2.6 \u003c2.47.0 \|\| \u003e2.51.0 \u003c\u003d2.67.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16487","vulnerabilityDetails":"A prototype pollution vulnerability was found in lodash \u003c4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-28500","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.\n WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2014-7191","vulnerabilityDetails":"The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2017-0266","vulnerabilityDetails":"http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure.","vulnerabilityUrl":"https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56","cvss3Severity":"low","cvss3Score":"3.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"Required","AV":"Adjacent","I":"None"},"extraData":{}}]</REMEDIATE> -->	True	zaproxy-0.2.0.tgz: 18 vulnerabilities (highest severity is: 9.8) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>zaproxy-0.2.0.tgz</b></p></summary> <p></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| --- \| --- \| \| [CVE-2018-1000620](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| cryptiles-0.2.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2019-10744](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2018-3728](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.8 \| hoek-0.9.1.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [WS-2014-0005](https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2016-2515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| hawk-1.0.0.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2021-44907](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| N/A \| ❌ \| \| [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| mime-1.2.11.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2014-10064](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2020-8203](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.4 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2021-23337](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.2 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2019-1010266](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2018-3721](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2017-16026](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.9 \| request-2.36.0.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2018-16487](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.6 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2020-28500](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| lodash-2.4.2.tgz \| Transitive \| 1.0.0-rc.1 \| ✅ \| \| [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [CVE-2014-7191](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| qs-0.6.6.tgz \| Transitive \| 0.3.0 \| ✅ \| \| [WS-2017-0266](https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.5 \| http-signature-0.10.1.tgz \| Transitive \| 0.3.0 \| ✅ \| ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000620</summary> ### Vulnerable Library - <b>cryptiles-0.2.2.tgz</b></p> <p>General purpose crypto utilities</p> <p>Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/cryptiles/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: cryptiles-0.2.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2. <p>Publish Date: 2018-07-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620</a></p> <p>Release Date: 2018-07-09</p> <p>Fix Resolution (cryptiles): 4.1.2</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. <p>Publish Date: 2019-07-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744>CVE-2019-10744</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a></p> <p>Release Date: 2019-07-26</p> <p>Fix Resolution (lodash): 4.17.12</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-3728</summary> ### Vulnerable Library - <b>hoek-0.9.1.tgz</b></p> <p>General purpose node utilities</p> <p>Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz">https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/hoek/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: hoek-0.9.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. <p>Publish Date: 2018-03-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p> <p>Release Date: 2018-03-30</p> <p>Fix Resolution (hoek): 4.2.0</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0005</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time <p>Publish Date: 2014-07-31 <p>URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2014-0005">https://nvd.nist.gov/vuln/detail/WS-2014-0005</a></p> <p>Release Date: 2014-07-31</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2515</summary> ### Vulnerable Library - <b>hawk-1.0.0.tgz</b></p> <p>HTTP Hawk Authentication Scheme</p> <p>Library home page: <a href="https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz">https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/hawk/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: hawk-1.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression. <p>Publish Date: 2016-04-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515>CVE-2016-2515</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2515">https://nvd.nist.gov/vuln/detail/CVE-2016-2515</a></p> <p>Release Date: 2016-04-13</p> <p>Fix Resolution (hawk): 3.1.3</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44907</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior. <p>Publish Date: 2022-03-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907>CVE-2021-44907</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907</a></p> <p>Release Date: 2022-03-17</p> <p>Fix Resolution: qs - 6.8.1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - <b>mime-1.2.11.tgz</b></p> <p>A comprehensive library for mime-type mapping</p> <p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.11.tgz">https://registry.npmjs.org/mime/-/mime-1.2.11.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/mime/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: mime-1.2.11.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (mime): 1.4.1</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10064</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring. <p>Publish Date: 2018-05-31 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064>CVE-2014-10064</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10064">https://nvd.nist.gov/vuln/detail/CVE-2014-10064</a></p> <p>Release Date: 2018-05-31</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. <p>Publish Date: 2020-07-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p> <p>Release Date: 2020-07-15</p> <p>Fix Resolution (lodash): 4.17.9</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. <p>Publish Date: 2021-02-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. <p>Publish Date: 2019-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p> <p>Release Date: 2020-09-30</p> <p>Fix Resolution (lodash): 4.17.11</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (lodash): 4.17.5</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-16026</summary> ### Vulnerable Library - <b>request-2.36.0.tgz</b></p> <p>Simplified HTTP request client.</p> <p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.36.0.tgz">https://registry.npmjs.org/request/-/request-2.36.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/request/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: request-2.36.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 \|\| >2.51.0 <=2.67.0. <p>Publish Date: 2018-06-04 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026>CVE-2017-16026</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.9</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-16026">https://nvd.nist.gov/vuln/detail/CVE-2017-16026</a></p> <p>Release Date: 2018-06-04</p> <p>Fix Resolution (request): 2.68.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype. <p>Publish Date: 2019-02-01 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p> <p>Release Date: 2019-02-01</p> <p>Fix Resolution (lodash): 4.17.11</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary> ### Vulnerable Library - <b>lodash-2.4.2.tgz</b></p> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash. <p>Publish Date: 2021-02-15 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-1000048</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash. <p>Publish Date: 2017-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a></p> <p>Release Date: 2017-07-17</p> <p>Fix Resolution (qs): 6.0.4</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - <b>qs-0.6.6.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: qs-0.6.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. <p>Publish Date: 2014-10-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191>CVE-2014-7191</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a></p> <p>Release Date: 2014-10-19</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> WS-2017-0266</summary> ### Vulnerable Library - <b>http-signature-0.10.1.tgz</b></p> <p>Reference implementation of Joyent's HTTP Signature scheme.</p> <p>Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: http-signature-0.10.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure. <p>Publish Date: 2015-01-22 <p>URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>3.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a></p> <p>Release Date: 2015-01-22</p> <p>Fix Resolution (http-signature): 1.0.0</p> <p>Direct dependency fix Resolution (zaproxy): 0.3.0</p> </p> <p></p> <p>In order to enable automatic remediation, please create <a target="_blank" href="https://whitesource.atlassian.net/wiki/spaces/WD/pages/697696422/WhiteSource+for+GitHub.com#Remediate-Settings-(remediateSettings)">workflow rules</a></p> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> <!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1000620","vulnerabilityDetails":"Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-10744","vulnerabilityDetails":"Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3728","vulnerabilityDetails":"hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via \u0027merge\u0027 and \u0027applyToDefaults\u0027 functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2014-0005","vulnerabilityDetails":"Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time","vulnerabilityUrl":"https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2016-2515","vulnerabilityDetails":"Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"0.6.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"zaproxy:0.2.0;request:2.36.0;qs:0.6.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.8.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44907","vulnerabilityDetails":"A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16138","vulnerabilityDetails":"The mime module \u003c 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2014-10064","vulnerabilityDetails":"The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8203","vulnerabilityDetails":"Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-1010266","vulnerabilityDetails":"lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3721","vulnerabilityDetails":"lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16026","vulnerabilityDetails":"Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request \u003e\u003d2.2.6 \u003c2.47.0 \|\| \u003e2.51.0 \u003c\u003d2.67.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16487","vulnerabilityDetails":"A prototype pollution vulnerability was found in lodash \u003c4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.0-rc.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-28500","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.\n WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2014-7191","vulnerabilityDetails":"The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"zaproxy","packageVersion":"0.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"zaproxy:0.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2017-0266","vulnerabilityDetails":"http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure.","vulnerabilityUrl":"https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56","cvss3Severity":"low","cvss3Score":"3.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"Required","AV":"Adjacent","I":"None"},"extraData":{}}]</REMEDIATE> -->	non_defect	zaproxy tgz vulnerabilities highest severity is autoclosed vulnerable library zaproxy tgz path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high cryptiles tgz transitive rc high lodash tgz transitive rc high hoek tgz transitive rc high qs tgz transitive high hawk tgz transitive high qs tgz transitive n a high mime tgz transitive high qs tgz transitive high lodash tgz transitive rc high lodash tgz transitive rc medium lodash tgz transitive rc medium lodash tgz transitive rc medium request tgz transitive medium lodash tgz transitive rc medium lodash tgz transitive rc medium qs tgz transitive medium qs tgz transitive low http signature tgz transitive details cve vulnerable library cryptiles tgz general purpose crypto utilities library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules cryptiles package json dependency hierarchy zaproxy tgz root library request tgz hawk tgz x cryptiles tgz vulnerable library found in head commit a href found in base branch master vulnerability details eran hammer cryptiles version earlier contains a cwe insufficient entropy vulnerability in randomdigits method that can result in an attacker is more likely to be able to brute force something that was supposed to be random this attack appear to be exploitable via depends upon the calling application this vulnerability appears to have been fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cryptiles direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of lodash lower than are vulnerable to prototype pollution the function defaultsdeep could be tricked into adding or modifying properties of object prototype using a constructor payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library hoek tgz general purpose node utilities library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules hoek package json dependency hierarchy zaproxy tgz root library request tgz hawk tgz x hoek tgz vulnerable library found in head commit a href found in base branch master vulnerability details hoek node module before and x before suffers from a modification of assumed immutable data maid vulnerability via merge and applytodefaults functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hoek direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue ws vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details denial of service extended event loop blocking the qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library hawk tgz http hawk authentication scheme library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules hawk package json dependency hierarchy zaproxy tgz root library request tgz x hawk tgz vulnerable library found in head commit a href found in base branch master vulnerability details hawk before and x before allow remote attackers to cause a denial of service cpu consumption or partial outage via a long header or uri that is matched against an improper regular expression publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hawk direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details a denial of service vulnerability exists in qs up to due to insufficient sanitization of property in the gs parse function the merge function allows the assignment of properties on an array in the query for any property being assigned a value in the array is converted to an object containing these properties essentially this means that the property whose expected type is array always has to be checked with array isarray by the user this may not be obvious to the user and can cause unexpected behavior publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs cve vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules mime package json dependency hierarchy zaproxy tgz root library request tgz x mime tgz vulnerable library found in head commit a href found in base branch master vulnerability details the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution mime direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the qs module before does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time an attacker could leverage this to cause a temporary denial of service condition for example in a web application other requests would not be processed while this blocking is occurring publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution attack when using zipobjectdeep in lodash before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules request package json dependency hierarchy zaproxy tgz root library x request tgz vulnerable library found in head commit a href found in base branch master vulnerability details request is an http client if a request is made using multipart and the body type is a number then the specified number of non zero memory is passed in the body this affects request publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution request direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions whitesource note after conducting further research whitesource has determined that cve only affects environments with versions to of lodash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the web framework using ljharb s qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the qs module before in node js does not call the compact function for array data which allows remote attackers to cause a denial of service memory consumption by using a large index value to create a sparse array publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue ws vulnerable library http signature tgz reference implementation of joyent s http signature scheme library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules http signature package json dependency hierarchy zaproxy tgz root library request tgz x http signature tgz vulnerable library found in head commit a href found in base branch master vulnerability details http signature before version are vulnerable to timing attack which may lead to information disclosure publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution http signature direct dependency fix resolution zaproxy in order to enable automatic remediation please create rescue worker helmet automatic remediation is available for this issue istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails eran hammer cryptiles version earlier contains a cwe insufficient entropy vulnerability in randomdigits method that can result in an attacker is more likely to be able to brute force something that was supposed to be random this attack appear to be exploitable via depends upon the calling application this vulnerability appears to have been fixed in vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of lodash lower than are vulnerable to prototype pollution the function defaultsdeep could be tricked into adding or modifying properties of object prototype using a constructor payload vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails hoek node module before and x before suffers from a modification of assumed immutable data maid vulnerability via and functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails denial of service extended event loop blocking the qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails hawk before and x before allow remote attackers to cause a denial of service cpu consumption or partial outage via a long header or uri that is matched against an improper regular expression vulnerabilityurl istransitivedependency true dependencytree zaproxy request qs isminimumfixversionavailable true minimumfixversion qs isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a denial of service vulnerability exists in qs up to due to insufficient sanitization of property in the gs parse function the merge function allows the assignment of properties on an array in the query for any property being assigned a value in the array is converted to an object containing these properties essentially this means that the property whose expected type is array always has to be checked with array isarray by the user this may not be obvious to the user and can cause unexpected behavior vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the qs module before does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time an attacker could leverage this to cause a temporary denial of service condition for example in a web application other requests would not be processed while this blocking is occurring vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails prototype pollution attack when using zipobjectdeep in lodash before vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to command injection via the template function vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails request is an http client if a request is made using multipart and the body type is a number then the specified number of non zero memory is passed in the body this affects request vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions n whitesource note after conducting further research whitesource has determined that cve only affects environments with versions to of lodash vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the web framework using ljharb qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the qs module before in node js does not call the compact function for array data which allows remote attackers to cause a denial of service memory consumption by using a large index value to create a sparse array vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails http signature before version are vulnerable to timing attack which may lead to information disclosure vulnerabilityurl	0
212,904	16,487,071,335	IssuesEvent	2021-05-24 19:41:49	E3SM-Project/zppy	https://api.github.com/repos/E3SM-Project/zppy	closed	Add testing	for next version testing	Add a unit test that runs on Chrysalis or another machine (not on GitHub Actions Linux machine).	1.0	Add testing - Add a unit test that runs on Chrysalis or another machine (not on GitHub Actions Linux machine).	non_defect	add testing add a unit test that runs on chrysalis or another machine not on github actions linux machine	0
840	2,644,777,690	IssuesEvent	2015-03-12 18:45:00	Homebrew/homebrew-science	https://api.github.com/repos/Homebrew/homebrew-science	closed	Infernal 1.1.1 - Make Error 2 with fresh install of Linuxbrew	Bioinformatics build-error Linux	Got this unexpected error on _Red Hat Enterprise Linux Server release 7.1 (Maipo)_ ``` ==> Installing prokka dependency: infernal ==> Downloading http://selab.janelia.org/software/infernal/infernal-1.1.1.tar.gz ######################################################################## 100.0% ==> ./configure --prefix=/home/linuxbrew/Cellar/infernal/1.1.1 ==> make make[2]: * [hmmpgmd] Error 1 make[2]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer/src' make[1]: * [all] Error 2 make[1]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer' make: *** [all] Error 2 ```	1.0	Infernal 1.1.1 - Make Error 2 with fresh install of Linuxbrew - Got this unexpected error on _Red Hat Enterprise Linux Server release 7.1 (Maipo)_ ``` ==> Installing prokka dependency: infernal ==> Downloading http://selab.janelia.org/software/infernal/infernal-1.1.1.tar.gz ######################################################################## 100.0% ==> ./configure --prefix=/home/linuxbrew/Cellar/infernal/1.1.1 ==> make make[2]: * [hmmpgmd] Error 1 make[2]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer/src' make[1]: * [all] Error 2 make[1]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer' make: *** [all] Error 2 ```	non_defect	infernal make error with fresh install of linuxbrew got this unexpected error on red hat enterprise linux server release maipo installing prokka dependency infernal downloading configure prefix home linuxbrew cellar infernal make make error make leaving directory tmp infernal infernal hmmer src make error make leaving directory tmp infernal infernal hmmer make error	0
41,200	12,831,755,528	IssuesEvent	2020-07-07 06:14:07	rvvergara/todolist-api-igaku	https://api.github.com/repos/rvvergara/todolist-api-igaku	closed	WS-2020-0070 (High) detected in lodash-4.17.15.tgz	security vulnerability	## WS-2020-0070 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/todolist-api-igaku/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/todolist-api-igaku/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - eslint-6.6.0.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/rvvergara/todolist-api-igaku/commit/e74ac424f4412547afcf733f031f27227a0f28e9">e74ac424f4412547afcf733f031f27227a0f28e9</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> All versions of lodash are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays. This vulnerability may lead to Denial of Service or Code Execution. <p>Publish Date: 2020-04-28 <p>URL: <a href=https://hackerone.com/reports/712065>WS-2020-0070</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	True	WS-2020-0070 (High) detected in lodash-4.17.15.tgz - ## WS-2020-0070 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/todolist-api-igaku/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/todolist-api-igaku/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - eslint-6.6.0.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/rvvergara/todolist-api-igaku/commit/e74ac424f4412547afcf733f031f27227a0f28e9">e74ac424f4412547afcf733f031f27227a0f28e9</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> All versions of lodash are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays. This vulnerability may lead to Denial of Service or Code Execution. <p>Publish Date: 2020-04-28 <p>URL: <a href=https://hackerone.com/reports/712065>WS-2020-0070</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_defect	ws high detected in lodash tgz ws high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file tmp ws scm todolist api igaku package json path to vulnerable library tmp ws scm todolist api igaku node modules lodash package json dependency hierarchy eslint tgz root library x lodash tgz vulnerable library found in head commit a href vulnerability details all versions of lodash are vulnerable to prototype pollution the function zipobjectdeep allows a malicious user to modify the prototype of object if the property identifiers are user supplied being affected by this issue requires zipping objects based on user provided property arrays this vulnerability may lead to denial of service or code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with whitesource	0
61,717	17,023,763,360	IssuesEvent	2021-07-03 03:43:09	tomhughes/trac-tickets	https://api.github.com/repos/tomhughes/trac-tickets	closed	Item name not updated on different zoomlevel	Component: mapnik Priority: minor Resolution: invalid Type: defect	[Submitted to the original trac issue database at 8.39pm, Saturday, 10th December 2011] I just updated an item. When zooming in to the maximum, the new name shows up nicely, but when I zoom out one level, the old name shows up again. This happened on a different browser from where I am making the changes (also not logged in). I tried to find if such a ticket already exists but it's hard to find a correct search term, so I didn't find any similar reports.	1.0	Item name not updated on different zoomlevel - [Submitted to the original trac issue database at 8.39pm, Saturday, 10th December 2011] I just updated an item. When zooming in to the maximum, the new name shows up nicely, but when I zoom out one level, the old name shows up again. This happened on a different browser from where I am making the changes (also not logged in). I tried to find if such a ticket already exists but it's hard to find a correct search term, so I didn't find any similar reports.	defect	item name not updated on different zoomlevel i just updated an item when zooming in to the maximum the new name shows up nicely but when i zoom out one level the old name shows up again this happened on a different browser from where i am making the changes also not logged in i tried to find if such a ticket already exists but it s hard to find a correct search term so i didn t find any similar reports	1
101,248	4,111,218,737	IssuesEvent	2016-06-07 04:31:36	rdunlop/unicycling-registration	https://api.github.com/repos/rdunlop/unicycling-registration	opened	Deleting the last member in a competitor, site crashes	High Priority	If I remove the last member of a competitor, I get persistent 500 errors.	1.0	Deleting the last member in a competitor, site crashes - If I remove the last member of a competitor, I get persistent 500 errors.	non_defect	deleting the last member in a competitor site crashes if i remove the last member of a competitor i get persistent errors	0
55,085	7,954,596,897	IssuesEvent	2018-07-12 08:05:32	ppy/osu-framework	https://api.github.com/repos/ppy/osu-framework	opened	Update wiki page for the loading process of a Drawable	documentation	The loading process was adjusted in #1670. The following connection doesn't exist anymore: ![screen shot 2018-07-12 at 5 02 28 pm](https://user-images.githubusercontent.com/1329837/42620347-aeba3272-85f5-11e8-8b38-ec2d65d6e2c1.png)	1.0	Update wiki page for the loading process of a Drawable - The loading process was adjusted in #1670. The following connection doesn't exist anymore: ![screen shot 2018-07-12 at 5 02 28 pm](https://user-images.githubusercontent.com/1329837/42620347-aeba3272-85f5-11e8-8b38-ec2d65d6e2c1.png)	non_defect	update wiki page for the loading process of a drawable the loading process was adjusted in the following connection doesn t exist anymore	0
80,241	30,182,204,491	IssuesEvent	2023-07-04 09:37:15	jOOQ/jOOQ	https://api.github.com/repos/jOOQ/jOOQ	closed	Parser error when using SET new.x = y syntax in triggers	T: Defect P: Medium R: Fixed E: Professional Edition E: Enterprise Edition C: Parser	The following is a valid trigger definition, e.g. in Db2: ```sql CREATE TRIGGER trg_triggers_before_i BEFORE INSERT ON t_triggers_before REFERENCING NEW AS new FOR EACH ROW BEGIN SET new.c = 1; END; ``` However, we can't parse it: ``` org.jooq.impl.ParserException: Assignment expected: [53:3] ...efore REFERENCING NEW AS new FOR EACH ROW BEGIN [*]SET new.c = 1; END; CREATE TRIGGER trg_triggers_before_u BEFORE UPDATE ON t_tri... at org.jooq.impl.DefaultParseContext.expected (ParserImpl.java:14775) at org.jooq.impl.DefaultParseContext.parseAssignment (ParserImpl.java:4035) at org.jooq.impl.DefaultParseContext.parseStatement (ParserImpl.java:3671) at org.jooq.impl.DefaultParseContext.parseStatements (ParserImpl.java:3392) at org.jooq.impl.DefaultParseContext.parseStatementsAndPeek (ParserImpl.java:3410) at org.jooq.impl.DefaultParseContext.parseBlock (ParserImpl.java:3339) at org.jooq.impl.DefaultParseContext.parseCreateTrigger (ParserImpl.java:5893) at org.jooq.impl.DefaultParseContext.parseCreate (ParserImpl.java:2937) at org.jooq.impl.DefaultParseContext.parseQuery (ParserImpl.java:1133) at org.jooq.impl.DefaultParseContext.lambda$parse$0 (ParserImpl.java:903) at org.jooq.impl.DefaultParseContext.wrap (ParserImpl.java:15002) at org.jooq.impl.DefaultParseContext.parse (ParserImpl.java:891) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:769) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:764) ``` This issue just handles the parser error for now. There might be more follow-up issues handling the emulation of the feature, in case the `REFERENCING` clause isn't supported.	1.0	Parser error when using SET new.x = y syntax in triggers - The following is a valid trigger definition, e.g. in Db2: ```sql CREATE TRIGGER trg_triggers_before_i BEFORE INSERT ON t_triggers_before REFERENCING NEW AS new FOR EACH ROW BEGIN SET new.c = 1; END; ``` However, we can't parse it: ``` org.jooq.impl.ParserException: Assignment expected: [53:3] ...efore REFERENCING NEW AS new FOR EACH ROW BEGIN [*]SET new.c = 1; END; CREATE TRIGGER trg_triggers_before_u BEFORE UPDATE ON t_tri... at org.jooq.impl.DefaultParseContext.expected (ParserImpl.java:14775) at org.jooq.impl.DefaultParseContext.parseAssignment (ParserImpl.java:4035) at org.jooq.impl.DefaultParseContext.parseStatement (ParserImpl.java:3671) at org.jooq.impl.DefaultParseContext.parseStatements (ParserImpl.java:3392) at org.jooq.impl.DefaultParseContext.parseStatementsAndPeek (ParserImpl.java:3410) at org.jooq.impl.DefaultParseContext.parseBlock (ParserImpl.java:3339) at org.jooq.impl.DefaultParseContext.parseCreateTrigger (ParserImpl.java:5893) at org.jooq.impl.DefaultParseContext.parseCreate (ParserImpl.java:2937) at org.jooq.impl.DefaultParseContext.parseQuery (ParserImpl.java:1133) at org.jooq.impl.DefaultParseContext.lambda$parse$0 (ParserImpl.java:903) at org.jooq.impl.DefaultParseContext.wrap (ParserImpl.java:15002) at org.jooq.impl.DefaultParseContext.parse (ParserImpl.java:891) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:769) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:764) ``` This issue just handles the parser error for now. There might be more follow-up issues handling the emulation of the feature, in case the `REFERENCING` clause isn't supported.	defect	parser error when using set new x y syntax in triggers the following is a valid trigger definition e g in sql create trigger trg triggers before i before insert on t triggers before referencing new as new for each row begin set new c end however we can t parse it org jooq impl parserexception assignment expected efore referencing new as new for each row begin set new c end create trigger trg triggers before u before update on t tri at org jooq impl defaultparsecontext expected parserimpl java at org jooq impl defaultparsecontext parseassignment parserimpl java at org jooq impl defaultparsecontext parsestatement parserimpl java at org jooq impl defaultparsecontext parsestatements parserimpl java at org jooq impl defaultparsecontext parsestatementsandpeek parserimpl java at org jooq impl defaultparsecontext parseblock parserimpl java at org jooq impl defaultparsecontext parsecreatetrigger parserimpl java at org jooq impl defaultparsecontext parsecreate parserimpl java at org jooq impl defaultparsecontext parsequery parserimpl java at org jooq impl defaultparsecontext lambda parse parserimpl java at org jooq impl defaultparsecontext wrap parserimpl java at org jooq impl defaultparsecontext parse parserimpl java at org jooq impl parserimpl parse parserimpl java at org jooq impl parserimpl parse parserimpl java this issue just handles the parser error for now there might be more follow up issues handling the emulation of the feature in case the referencing clause isn t supported	1
39,611	9,562,138,550	IssuesEvent	2019-05-04 06:00:54	catmaid/CATMAID	https://api.github.com/repos/catmaid/CATMAID	opened	Issue with Neuron Similarity Widget on dev	type: defect	Hi! I'm trying to setup NBLAST/Neuron Similarity Widget being on `dev` branch. R and its dependencies are setup and Celery is working. When I open the Neuron Similarity Widget, I get a JSON parsing error, caused by the request `http://localhost:8000/catmaid/3/similarity/queries/?with_objects=false&with_scoring=false` which returns None. Any pointer how to fix this? Also, when I try to setup a configuration, in the Configuration Tab of the widget, when I press "Create Similarity Matrix", a message is shown, "No matching transformed skeletons selected" even though I have selected an active skeletons. Thanks for help.	1.0	Issue with Neuron Similarity Widget on dev - Hi! I'm trying to setup NBLAST/Neuron Similarity Widget being on `dev` branch. R and its dependencies are setup and Celery is working. When I open the Neuron Similarity Widget, I get a JSON parsing error, caused by the request `http://localhost:8000/catmaid/3/similarity/queries/?with_objects=false&with_scoring=false` which returns None. Any pointer how to fix this? Also, when I try to setup a configuration, in the Configuration Tab of the widget, when I press "Create Similarity Matrix", a message is shown, "No matching transformed skeletons selected" even though I have selected an active skeletons. Thanks for help.	defect	issue with neuron similarity widget on dev hi i m trying to setup nblast neuron similarity widget being on dev branch r and its dependencies are setup and celery is working when i open the neuron similarity widget i get a json parsing error caused by the request which returns none any pointer how to fix this also when i try to setup a configuration in the configuration tab of the widget when i press create similarity matrix a message is shown no matching transformed skeletons selected even though i have selected an active skeletons thanks for help	1
39,252	9,358,111,648	IssuesEvent	2019-04-02 00:53:43	jOOQ/jOOQ	https://api.github.com/repos/jOOQ/jOOQ	opened	WHERE caluse missing when using INSERT ... ON DUPLICATE	T: Defect	Using jooq 3.11.9, the following query prints: `` public static void main(String[] args) throws SQLException { String sql = DSL.using(SQLDialect.MYSQL_5_7).renderInlined( insertInto(table("tableA")) .columns(field("colA"), field("colB")) .values("val1", "val2") .onDuplicateKeyUpdate() .set(field("colA"), "something") .where(field("colC").eq("other"))); System.out.println(sql); } `` `insert into tableA (colA, colB) values ('val1', 'val2') on duplicate key update colA = 'something'` The WHERE clause and "colC" are never mentioned in the query. I'm might be inexperienced with SQL but I would expect and exception or at least a warning would be thrown if I'm doing something invalid or unsupported.	1.0	WHERE caluse missing when using INSERT ... ON DUPLICATE - Using jooq 3.11.9, the following query prints: `` public static void main(String[] args) throws SQLException { String sql = DSL.using(SQLDialect.MYSQL_5_7).renderInlined( insertInto(table("tableA")) .columns(field("colA"), field("colB")) .values("val1", "val2") .onDuplicateKeyUpdate() .set(field("colA"), "something") .where(field("colC").eq("other"))); System.out.println(sql); } `` `insert into tableA (colA, colB) values ('val1', 'val2') on duplicate key update colA = 'something'` The WHERE clause and "colC" are never mentioned in the query. I'm might be inexperienced with SQL but I would expect and exception or at least a warning would be thrown if I'm doing something invalid or unsupported.	defect	where caluse missing when using insert on duplicate using jooq the following query prints public static void main string args throws sqlexception string sql dsl using sqldialect mysql renderinlined insertinto table tablea columns field cola field colb values onduplicatekeyupdate set field cola something where field colc eq other system out println sql insert into tablea cola colb values on duplicate key update cola something the where clause and colc are never mentioned in the query i m might be inexperienced with sql but i would expect and exception or at least a warning would be thrown if i m doing something invalid or unsupported	1
80,209	30,115,919,308	IssuesEvent	2023-06-30 11:30:13	vector-im/element-desktop	https://api.github.com/repos/vector-im/element-desktop	opened	CMD-plus does not increase the size of the text	T-Defect	### Steps to reproduce I wrongly reduced the size of the text by cmd-minus I tried to revert it by cmd-plus but does not work cmd-zero works to reset ### Outcome #### What did you expect? cmd-plus increase the size as opposite operation to cmd-minus #### What happened instead? nothing ### Operating system macOSX ### Application version Element Nightly version: 2023063001 Olm version: 3.2.14 ### How did you install the app? _No response_ ### Homeserver _No response_ ### Will you send logs? No	1.0	CMD-plus does not increase the size of the text - ### Steps to reproduce I wrongly reduced the size of the text by cmd-minus I tried to revert it by cmd-plus but does not work cmd-zero works to reset ### Outcome #### What did you expect? cmd-plus increase the size as opposite operation to cmd-minus #### What happened instead? nothing ### Operating system macOSX ### Application version Element Nightly version: 2023063001 Olm version: 3.2.14 ### How did you install the app? _No response_ ### Homeserver _No response_ ### Will you send logs? No	defect	cmd plus does not increase the size of the text steps to reproduce i wrongly reduced the size of the text by cmd minus i tried to revert it by cmd plus but does not work cmd zero works to reset outcome what did you expect cmd plus increase the size as opposite operation to cmd minus what happened instead nothing operating system macosx application version element nightly version olm version how did you install the app no response homeserver no response will you send logs no	1
18,431	3,060,510,995	IssuesEvent	2015-08-14 21:08:32	prettydiff/prettydiff	https://api.github.com/repos/prettydiff/prettydiff	closed	Nested rules not indented in SCSS	Defect Underway	Nested rules aren't indented in SCSS if the option to insert new lines between rules is checked. This only effects the nested rules that aren't the first on that level. Original: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Expected: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Actual: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ```	1.0	Nested rules not indented in SCSS - Nested rules aren't indented in SCSS if the option to insert new lines between rules is checked. This only effects the nested rules that aren't the first on that level. Original: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Expected: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Actual: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ```	defect	nested rules not indented in scss nested rules aren t indented in scss if the option to insert new lines between rules is checked this only effects the nested rules that aren t the first on that level original scss header navbar nav float none footer navbar min height other class min height other class min height expected scss header navbar nav float none footer navbar min height other class min height other class min height actual scss header navbar nav float none footer navbar min height other class min height other class min height	1
328,036	28,099,353,456	IssuesEvent	2023-03-30 18:11:46	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	roachtest: sqlsmith/setup=seed/setting=no-ddl failed	C-test-failure O-robot O-roachtest T-sql-queries branch-release-23.1	roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on release-23.1 @ [aec78f33d45a8376a0ecec885688bae60dbfb85c](https://github.com/cockroachdb/cockroach/commits/aec78f33d45a8376a0ecec885688bae60dbfb85c): ``` test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1 (sqlsmith.go:244).func3: error: pq: internal error: regproc(): ResolveFunction unimplemented stmt: WITH "w'\\U00035ED1ith381" (col2573) AS (SELECT tab1110._bool AS col2573 FROM defaultdb.public.seed@[0] AS tab1110), "?wi%03th382" (col2574) AS ( SELECT 2990964997:::OID AS col2574 FROM defaultdb.public.seed@[0] AS "tab""1111", defaultdb.public.seed@seed__int8__float8__date_idx AS tab1112, "w'\\U00035ED1ith381" AS ".cte_ref102" ) SELECT regproc(e'z\\a).+A':::STRING::STRING)::REGPROC AS "cOl2575" FROM "?wi%03th382" AS "cte_r""ef103" ORDER BY "cte_r""ef103".col2574 DESC NULLS LAST, "cte_r""ef103".col2574, "cte_r""ef103".col2574 ASC NULLS FIRST LIMIT 23:::INT8; ``` <p>Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=4</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> </p> <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> /cc @cockroachdb/sql-queries <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.sqlsmith/setup=seed/setting=no-ddl.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub> Jira issue: CRDB-26184	2.0	roachtest: sqlsmith/setup=seed/setting=no-ddl failed - roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on release-23.1 @ [aec78f33d45a8376a0ecec885688bae60dbfb85c](https://github.com/cockroachdb/cockroach/commits/aec78f33d45a8376a0ecec885688bae60dbfb85c): ``` test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1 (sqlsmith.go:244).func3: error: pq: internal error: regproc(): ResolveFunction unimplemented stmt: WITH "w'\\U00035ED1ith381" (col2573) AS (SELECT tab1110._bool AS col2573 FROM defaultdb.public.seed@[0] AS tab1110), "?wi%03th382" (col2574) AS ( SELECT 2990964997:::OID AS col2574 FROM defaultdb.public.seed@[0] AS "tab""1111", defaultdb.public.seed@seed__int8__float8__date_idx AS tab1112, "w'\\U00035ED1ith381" AS ".cte_ref102" ) SELECT regproc(e'z\\a).+A':::STRING::STRING)::REGPROC AS "cOl2575" FROM "?wi%03th382" AS "cte_r""ef103" ORDER BY "cte_r""ef103".col2574 DESC NULLS LAST, "cte_r""ef103".col2574, "cte_r""ef103".col2574 ASC NULLS FIRST LIMIT 23:::INT8; ``` <p>Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=4</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> </p> <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> /cc @cockroachdb/sql-queries <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.sqlsmith/setup=seed/setting=no-ddl.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub> Jira issue: CRDB-26184	non_defect	roachtest sqlsmith setup seed setting no ddl failed roachtest sqlsmith setup seed setting no ddl with on release test artifacts and logs in artifacts sqlsmith setup seed setting no ddl run sqlsmith go error pq internal error regproc resolvefunction unimplemented stmt with w as select bool as from defaultdb public seed as wi as select oid as from defaultdb public seed as tab defaultdb public seed seed date idx as w as cte select regproc e z a a string string regproc as from wi as cte r order by cte r desc nulls last cte r cte r asc nulls first limit parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb sql queries jira issue crdb	0
621,596	19,592,558,646	IssuesEvent	2022-01-05 14:29:57	GameFreedomGG/Sindragosa	https://api.github.com/repos/GameFreedomGG/Sindragosa	closed	[Raid][NPC][Spell] Naxxramas - Gluth - Decimate	Raid Priority: High NPC Spell Status: Closed- Resolved Status: Confirmed Bug (Awaiting Development)	Decription: Gluthʼs decimate can one shot you. How it works: Gluthʼs decimate can deal more dmg to you then your actual HP. How it should work: Decimate: Reduce the current health of all nearby units (friendly or enemy) to 5% of their maximum health. Affects both players and zombies. Used approximately every 90 seconds. Source (you should point out proofs of your report, please give us some source): It occured during 10man Naxx. Screenshot from recount death recap: ![image](https://user-images.githubusercontent.com/95646548/144896325-a111aa6c-7fbf-428e-8a69-15bd3db79425.png)	1.0	[Raid][NPC][Spell] Naxxramas - Gluth - Decimate - Decription: Gluthʼs decimate can one shot you. How it works: Gluthʼs decimate can deal more dmg to you then your actual HP. How it should work: Decimate: Reduce the current health of all nearby units (friendly or enemy) to 5% of their maximum health. Affects both players and zombies. Used approximately every 90 seconds. Source (you should point out proofs of your report, please give us some source): It occured during 10man Naxx. Screenshot from recount death recap: ![image](https://user-images.githubusercontent.com/95646548/144896325-a111aa6c-7fbf-428e-8a69-15bd3db79425.png)	non_defect	naxxramas gluth decimate decription gluthʼs decimate can one shot you how it works gluthʼs decimate can deal more dmg to you then your actual hp how it should work decimate reduce the current health of all nearby units friendly or enemy to of their maximum health affects both players and zombies used approximately every seconds source you should point out proofs of your report please give us some source it occured during naxx screenshot from recount death recap	0
744,970	25,963,432,124	IssuesEvent	2022-12-19 03:15:58	FlutterFlow/flutterflow-issues	https://api.github.com/repos/FlutterFlow/flutterflow-issues	closed	Set value List<String> into a Custom Function	type: bug status: needs information priority: low	## Expected behavior (required) You can't click Confirm, because it says Available Options - List Contains Item. You should get "No further changes". ## Current behavior (required) You can't click Confirm nothing is happening and the value is not saved. ## To Reproduce (required) Steps to reproduce the behavior: 1. Create a Custom Function which has only one argument List<String> and it is returning the same List<String> value. 2. Create a Local State variable List<String> as well 3. Go to a Page - Click on a Text Widget and Click on Actions 4. Update Local State, Select the Local State that you just create, Set Value, From Variable 5. Choose the Custom Function you just created and then click on Confirm ## Context (required) You can't use this when using Custom Function with an argument of a List<String>. ## Screenshots / recordings <!-- If applicable, add screenshots to help explain your problem. --> ## Your environment <!--- Include relevant details about the environment you experienced the bug in --> * Version of FlutterFlow used: 3.0.5 * Platform (e.g. Web, MacOS Desktop): Web * Browser name and version: Chrome 106 * Operating system and version (desktop or mobile): desktop	1.0	Set value List<String> into a Custom Function - ## Expected behavior (required) You can't click Confirm, because it says Available Options - List Contains Item. You should get "No further changes". ## Current behavior (required) You can't click Confirm nothing is happening and the value is not saved. ## To Reproduce (required) Steps to reproduce the behavior: 1. Create a Custom Function which has only one argument List<String> and it is returning the same List<String> value. 2. Create a Local State variable List<String> as well 3. Go to a Page - Click on a Text Widget and Click on Actions 4. Update Local State, Select the Local State that you just create, Set Value, From Variable 5. Choose the Custom Function you just created and then click on Confirm ## Context (required) You can't use this when using Custom Function with an argument of a List<String>. ## Screenshots / recordings <!-- If applicable, add screenshots to help explain your problem. --> ## Your environment <!--- Include relevant details about the environment you experienced the bug in --> * Version of FlutterFlow used: 3.0.5 * Platform (e.g. Web, MacOS Desktop): Web * Browser name and version: Chrome 106 * Operating system and version (desktop or mobile): desktop	non_defect	set value list into a custom function expected behavior required you can t click confirm because it says available options list contains item you should get no further changes current behavior required you can t click confirm nothing is happening and the value is not saved to reproduce required steps to reproduce the behavior create a custom function which has only one argument list and it is returning the same list value create a local state variable list as well go to a page click on a text widget and click on actions update local state select the local state that you just create set value from variable choose the custom function you just created and then click on confirm context required you can t use this when using custom function with an argument of a list screenshots recordings your environment version of flutterflow used platform e g web macos desktop web browser name and version chrome operating system and version desktop or mobile desktop	0
72,276	24,031,687,948	IssuesEvent	2022-09-15 15:29:30	SeleniumHQ/selenium	https://api.github.com/repos/SeleniumHQ/selenium	closed	[🐛 Bug]: JS firefox driver crashes on setting a profile.	C-nodejs I-defect	### What happened? I want to use a custom firefox profile, so I set it according the [documentation](https://www.selenium.dev/selenium/docs/api/javascript/module/selenium-webdriver/firefox.html). However then my code crashes with the provided error. When I investigated why it is unable to serialize the object to JSON, I found `httpRequest.data` contains content of the specified firefox profile which is about 200MB in size and it reaches the maximum length of the string. However, the profile should be used for the browser, not be attached to the request body. Is it a bug, or I'm doing something wrong ? In python, using the custom profile works without problems. ### How can we reproduce the issue? ```shell const {By,Key,Builder} = require("selenium-webdriver"); const firefox = require('selenium-webdriver/firefox'); async function example(){ let profile = '/home/kabell/.mozilla/firefox/4rmepnvo.default-release'; let options = new firefox.Options().setProfile(profile); //To wait for browser to build and launch properly let driver = await new Builder().forBrowser("firefox").setFirefoxOptions(options).build(); //To fetch http://google.com from the browser with our code. await driver.get("http://google.com"); //It is always a safe practice to quit the browser after execution await driver.quit(); } example() ``` ### Relevant log output ```shell /home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132 data = JSON.stringify(httpRequest.data) ^ RangeError: Invalid string length at JSON.stringify (<anonymous>) at HttpClient.send (/home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132:19) at Executor.execute (/home/kabell/selenium/node_modules/selenium-webdriver/lib/http.js:470:33) ``` ``` ### Operating System Ubuntu ### Selenium version Javascript 4.1.1 ### What are the browser(s) and version(s) where you see this issue? Firefox 97 ### What are the browser driver(s) and version(s) where you see this issue? Geckodriver 0.30.0 ### Are you using Selenium Grid? _No response_	1.0	[🐛 Bug]: JS firefox driver crashes on setting a profile. - ### What happened? I want to use a custom firefox profile, so I set it according the [documentation](https://www.selenium.dev/selenium/docs/api/javascript/module/selenium-webdriver/firefox.html). However then my code crashes with the provided error. When I investigated why it is unable to serialize the object to JSON, I found `httpRequest.data` contains content of the specified firefox profile which is about 200MB in size and it reaches the maximum length of the string. However, the profile should be used for the browser, not be attached to the request body. Is it a bug, or I'm doing something wrong ? In python, using the custom profile works without problems. ### How can we reproduce the issue? ```shell const {By,Key,Builder} = require("selenium-webdriver"); const firefox = require('selenium-webdriver/firefox'); async function example(){ let profile = '/home/kabell/.mozilla/firefox/4rmepnvo.default-release'; let options = new firefox.Options().setProfile(profile); //To wait for browser to build and launch properly let driver = await new Builder().forBrowser("firefox").setFirefoxOptions(options).build(); //To fetch http://google.com from the browser with our code. await driver.get("http://google.com"); //It is always a safe practice to quit the browser after execution await driver.quit(); } example() ``` ### Relevant log output ```shell /home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132 data = JSON.stringify(httpRequest.data) ^ RangeError: Invalid string length at JSON.stringify (<anonymous>) at HttpClient.send (/home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132:19) at Executor.execute (/home/kabell/selenium/node_modules/selenium-webdriver/lib/http.js:470:33) ``` ``` ### Operating System Ubuntu ### Selenium version Javascript 4.1.1 ### What are the browser(s) and version(s) where you see this issue? Firefox 97 ### What are the browser driver(s) and version(s) where you see this issue? Geckodriver 0.30.0 ### Are you using Selenium Grid? _No response_	defect	js firefox driver crashes on setting a profile what happened i want to use a custom firefox profile so i set it according the however then my code crashes with the provided error when i investigated why it is unable to serialize the object to json i found httprequest data contains content of the specified firefox profile which is about in size and it reaches the maximum length of the string however the profile should be used for the browser not be attached to the request body is it a bug or i m doing something wrong in python using the custom profile works without problems how can we reproduce the issue shell const by key builder require selenium webdriver const firefox require selenium webdriver firefox async function example let profile home kabell mozilla firefox default release let options new firefox options setprofile profile to wait for browser to build and launch properly let driver await new builder forbrowser firefox setfirefoxoptions options build to fetch from the browser with our code await driver get it is always a safe practice to quit the browser after execution await driver quit example relevant log output shell home kabell selenium node modules selenium webdriver http index js data json stringify httprequest data rangeerror invalid string length at json stringify at httpclient send home kabell selenium node modules selenium webdriver http index js at executor execute home kabell selenium node modules selenium webdriver lib http js operating system ubuntu selenium version javascript what are the browser s and version s where you see this issue firefox what are the browser driver s and version s where you see this issue geckodriver are you using selenium grid no response	1
58,900	16,888,832,809	IssuesEvent	2021-06-23 06:31:38	openzfs/zfs	https://api.github.com/repos/openzfs/zfs	opened	#12145 breaks support for x32	Status: Triage Needed Type: Defect	<!-- Please fill out the following template, which will help other contributors address your issue. --> <!-- Thank you for reporting an issue. IMPORTANT - Please check our issue tracker before opening a new issue. Additional valuable information can be found in the OpenZFS documentation and mailing list archives. Please fill in as much of the template as possible. --> ### System information <!-- add version after "\|" character --> Type \| Version/Name --- \| --- Distribution Name \| N/A Distribution Version \| N/A Linux Kernel \| 5.12.12 Architecture \| x86_64 (x32) ZFS Version \| 2.1.0-rc7 SPL Version \| <!-- Commands to find ZFS/SPL versions: modinfo zfs \| grep -iw version modinfo spl \| grep -iw version --> ### Describe the problem you're observing ``` make[3]: Entering directory '/home/harald/zfs/lib/libzpool' CCLD libzpool.la ld.lld: error: undefined symbol: atomic_load_64 >>> referenced by aggsum.c:119 (../../module/zfs/aggsum.c:119) >>> .libs/aggsum.o:(aggsum_lower_bound) >>> referenced by aggsum.c:125 (../../module/zfs/aggsum.c:125) >>> .libs/aggsum.o:(aggsum_upper_bound) >>> referenced by aggsum.c:218 (../../module/zfs/aggsum.c:218) >>> .libs/aggsum.o:(aggsum_compare) >>> referenced 1 more times ld.lld: error: undefined symbol: atomic_store_64 >>> referenced by aggsum.c:157 (../../module/zfs/aggsum.c:157) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:158 (../../module/zfs/aggsum.c:158) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:199 (../../module/zfs/aggsum.c:199) >>> .libs/aggsum.o:(aggsum_add) >>> referenced 3 more times clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: * [Makefile:1115: libzpool.la] Error 1 make[3]: Leaving directory '/home/harald/zfs/lib/libzpool' make[2]: * [Makefile:701: all-recursive] Error 1 make[2]: Leaving directory '/home/harald/zfs/lib' make[1]: * [Makefile:906: all-recursive] Error 1 make[1]: Leaving directory '/home/harald/zfs' make: * [Makefile:767: all] Error 2 ``` ### Describe how to reproduce the problem Build with plain `./configure && make` on an x32 system. ### Include any warning/errors/backtraces from the system logs <!-- IMPORTANT - Please mark logs and text output from terminal commands or else Github will not display them correctly. An example is provided below. Example: ``` this is an example how log text should be marked (wrap it with ```) ``` --> N/A The problem is that on x32, `_LP64` is not defined so `atomic_load_64` gets declared as a function, but `atomic.c` does not get to define that function because x32 is still x86_64, so the assembly version `lib/libspl/asm-x86_64/atomic.S` is picked over `lib/libspl/asm-generic/atomic.c`. For x32, it should be fine to use the same macro using `volatile` that also gets defined for LP64 mode.	1.0	#12145 breaks support for x32 - <!-- Please fill out the following template, which will help other contributors address your issue. --> <!-- Thank you for reporting an issue. IMPORTANT - Please check our issue tracker before opening a new issue. Additional valuable information can be found in the OpenZFS documentation and mailing list archives. Please fill in as much of the template as possible. --> ### System information <!-- add version after "\|" character --> Type \| Version/Name --- \| --- Distribution Name \| N/A Distribution Version \| N/A Linux Kernel \| 5.12.12 Architecture \| x86_64 (x32) ZFS Version \| 2.1.0-rc7 SPL Version \| <!-- Commands to find ZFS/SPL versions: modinfo zfs \| grep -iw version modinfo spl \| grep -iw version --> ### Describe the problem you're observing ``` make[3]: Entering directory '/home/harald/zfs/lib/libzpool' CCLD libzpool.la ld.lld: error: undefined symbol: atomic_load_64 >>> referenced by aggsum.c:119 (../../module/zfs/aggsum.c:119) >>> .libs/aggsum.o:(aggsum_lower_bound) >>> referenced by aggsum.c:125 (../../module/zfs/aggsum.c:125) >>> .libs/aggsum.o:(aggsum_upper_bound) >>> referenced by aggsum.c:218 (../../module/zfs/aggsum.c:218) >>> .libs/aggsum.o:(aggsum_compare) >>> referenced 1 more times ld.lld: error: undefined symbol: atomic_store_64 >>> referenced by aggsum.c:157 (../../module/zfs/aggsum.c:157) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:158 (../../module/zfs/aggsum.c:158) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:199 (../../module/zfs/aggsum.c:199) >>> .libs/aggsum.o:(aggsum_add) >>> referenced 3 more times clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: * [Makefile:1115: libzpool.la] Error 1 make[3]: Leaving directory '/home/harald/zfs/lib/libzpool' make[2]: * [Makefile:701: all-recursive] Error 1 make[2]: Leaving directory '/home/harald/zfs/lib' make[1]: * [Makefile:906: all-recursive] Error 1 make[1]: Leaving directory '/home/harald/zfs' make: * [Makefile:767: all] Error 2 ``` ### Describe how to reproduce the problem Build with plain `./configure && make` on an x32 system. ### Include any warning/errors/backtraces from the system logs <!-- IMPORTANT - Please mark logs and text output from terminal commands or else Github will not display them correctly. An example is provided below. Example: ``` this is an example how log text should be marked (wrap it with ```) ``` --> N/A The problem is that on x32, `_LP64` is not defined so `atomic_load_64` gets declared as a function, but `atomic.c` does not get to define that function because x32 is still x86_64, so the assembly version `lib/libspl/asm-x86_64/atomic.S` is picked over `lib/libspl/asm-generic/atomic.c`. For x32, it should be fine to use the same macro using `volatile` that also gets defined for LP64 mode.	defect	breaks support for thank you for reporting an issue important please check our issue tracker before opening a new issue additional valuable information can be found in the openzfs documentation and mailing list archives please fill in as much of the template as possible system information type version name distribution name n a distribution version n a linux kernel architecture zfs version spl version commands to find zfs spl versions modinfo zfs grep iw version modinfo spl grep iw version describe the problem you re observing make entering directory home harald zfs lib libzpool ccld libzpool la ld lld error undefined symbol atomic load referenced by aggsum c module zfs aggsum c libs aggsum o aggsum lower bound referenced by aggsum c module zfs aggsum c libs aggsum o aggsum upper bound referenced by aggsum c module zfs aggsum c libs aggsum o aggsum compare referenced more times ld lld error undefined symbol atomic store referenced by aggsum c module zfs aggsum c libs aggsum o aggsum value referenced by aggsum c module zfs aggsum c libs aggsum o aggsum value referenced by aggsum c module zfs aggsum c libs aggsum o aggsum add referenced more times clang error linker command failed with exit code use v to see invocation make error make leaving directory home harald zfs lib libzpool make error make leaving directory home harald zfs lib make error make leaving directory home harald zfs make error describe how to reproduce the problem build with plain configure make on an system include any warning errors backtraces from the system logs important please mark logs and text output from terminal commands or else github will not display them correctly an example is provided below example this is an example how log text should be marked wrap it with n a the problem is that on is not defined so atomic load gets declared as a function but atomic c does not get to define that function because is still so the assembly version lib libspl asm atomic s is picked over lib libspl asm generic atomic c for it should be fine to use the same macro using volatile that also gets defined for mode	1
168,961	20,827,983,070	IssuesEvent	2022-03-19 01:11:41	snowdensb/caseflow	https://api.github.com/repos/snowdensb/caseflow	opened	CVE-2021-44906 (Medium) detected in multiple libraries	security vulnerability	## CVE-2021-44906 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-0.0.10.tgz</b>, <b>minimist-1.2.5.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary> <p> <details><summary><b>minimist-0.0.8.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/mocha/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - mocha-5.2.0.tgz (Root Library) - mkdirp-0.5.1.tgz - :x: minimist-0.0.8.tgz (Vulnerable Library) </details> <details><summary><b>minimist-0.0.10.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/optimist/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - optimist-0.6.1.tgz - :x: minimist-0.0.10.tgz (Vulnerable Library) </details> <details><summary><b>minimist-1.2.5.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - core-7.13.15.tgz (Root Library) - json5-2.2.0.tgz - :x: minimist-1.2.5.tgz (Vulnerable Library) </details> <details><summary><b>minimist-1.2.0.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/karma-mocha/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - karma-mocha-1.3.0.tgz (Root Library) - :x: minimist-1.2.0.tgz (Vulnerable Library) </details> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95). <p>Publish Date: 2022-03-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a></p> <p>Release Date: 2022-03-17</p> <p>Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"mocha:5.2.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma:1.7.1;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.5","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"@babel/core:7.13.15;json5:2.2.0;minimist:1.2.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma-mocha:1.3.0;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44906","vulnerabilityDetails":"Minimist \u003c\u003d1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->	True	CVE-2021-44906 (Medium) detected in multiple libraries - ## CVE-2021-44906 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-0.0.10.tgz</b>, <b>minimist-1.2.5.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary> <p> <details><summary><b>minimist-0.0.8.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/mocha/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - mocha-5.2.0.tgz (Root Library) - mkdirp-0.5.1.tgz - :x: minimist-0.0.8.tgz (Vulnerable Library) </details> <details><summary><b>minimist-0.0.10.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/optimist/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - optimist-0.6.1.tgz - :x: minimist-0.0.10.tgz (Vulnerable Library) </details> <details><summary><b>minimist-1.2.5.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - core-7.13.15.tgz (Root Library) - json5-2.2.0.tgz - :x: minimist-1.2.5.tgz (Vulnerable Library) </details> <details><summary><b>minimist-1.2.0.tgz</b></p></summary> <p>parse argument options</p> <p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p> <p>Path to dependency file: /client/package.json</p> <p>Path to vulnerable library: /client/node_modules/karma-mocha/node_modules/minimist/package.json</p> <p> Dependency Hierarchy: - karma-mocha-1.3.0.tgz (Root Library) - :x: minimist-1.2.0.tgz (Vulnerable Library) </details> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95). <p>Publish Date: 2022-03-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a></p> <p>Release Date: 2022-03-17</p> <p>Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"mocha:5.2.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma:1.7.1;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.5","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"@babel/core:7.13.15;json5:2.2.0;minimist:1.2.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","packageFilePaths":["/client/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma-mocha:1.3.0;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44906","vulnerabilityDetails":"Minimist \u003c\u003d1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->	non_defect	cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries minimist tgz minimist tgz minimist tgz minimist tgz minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules mocha node modules minimist package json dependency hierarchy mocha tgz root library mkdirp tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules optimist node modules minimist package json dependency hierarchy karma tgz root library optimist tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules minimist package json dependency hierarchy core tgz root library tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules karma mocha node modules minimist package json dependency hierarchy karma mocha tgz root library x minimist tgz vulnerable library found in base branch master vulnerability details minimist is vulnerable to prototype pollution via file index js function setkey lines publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree mocha mkdirp minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree karma optimist minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree babel core minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree karma mocha minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails minimist is vulnerable to prototype pollution via file index js function setkey lines vulnerabilityurl	0
48,711	13,184,722,926	IssuesEvent	2020-08-12 19:58:35	icecube-trac/tix3	https://api.github.com/repos/icecube-trac/tix3	opened	Python on Mac defaulting to system (Trac #90)	IceTray Incomplete Migration Migrated from Trac defect	<details> <summary>_Migrated from https://code.icecube.wisc.edu/ticket/90 , reported by cgils and owned by cgils_</summary> <p> ```json { "status": "closed", "changetime": "2007-09-07T17:14:11", "description": "15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% ./examples/resources/scripts/pass1.py\n\n15:47 < blaufuss@> Fatal Python error: Interpreter not initialized (version mismatch?)\n\n15:47 < blaufuss@> Abort trap\n\n15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% which python\n\n15:47 < blaufuss@> /Users/blaufuss/icework/i3tools/bin/python\n\n15:47 < blaufuss@> I reproduce Georges error on teufel\n\n15:49 < gekolu > OK so I'm not totally mad :-)\n\n15:49 < drool@> hrm\n\n15:50 < blaufuss@> otool -L libithon.so\n\n15:50 < blaufuss@> /System/Library/Frameworks/Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current version 2.3.5)", "reporter": "cgils", "cc": "", "resolution": "fixed", "_ts": "1189185251000000", "component": "IceTray", "summary": "Python on Mac defaulting to system", "priority": "normal", "keywords": "", "time": "2007-08-13T19:58:05", "milestone": "", "owner": "cgils", "type": "defect" } ``` </p> </details>	1.0	Python on Mac defaulting to system (Trac #90) - <details> <summary>_Migrated from https://code.icecube.wisc.edu/ticket/90 , reported by cgils and owned by cgils_</summary> <p> ```json { "status": "closed", "changetime": "2007-09-07T17:14:11", "description": "15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% ./examples/resources/scripts/pass1.py\n\n15:47 < blaufuss@> Fatal Python error: Interpreter not initialized (version mismatch?)\n\n15:47 < blaufuss@> Abort trap\n\n15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% which python\n\n15:47 < blaufuss@> /Users/blaufuss/icework/i3tools/bin/python\n\n15:47 < blaufuss@> I reproduce Georges error on teufel\n\n15:49 < gekolu > OK so I'm not totally mad :-)\n\n15:49 < drool@> hrm\n\n15:50 < blaufuss@> otool -L libithon.so\n\n15:50 < blaufuss@> /System/Library/Frameworks/Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current version 2.3.5)", "reporter": "cgils", "cc": "", "resolution": "fixed", "_ts": "1189185251000000", "component": "IceTray", "summary": "Python on Mac defaulting to system", "priority": "normal", "keywords": "", "time": "2007-08-13T19:58:05", "milestone": "", "owner": "cgils", "type": "defect" } ``` </p> </details>	defect	python on mac defaulting to system trac migrated from reported by cgils and owned by cgils json status closed changetime description blaufuss teufel examples resources scripts py n fatal python error interpreter not initialized version mismatch n abort trap n blaufuss teufel which python n users blaufuss icework bin python n i reproduce georges error on teufel n ok so i m not totally mad n hrm n otool l libithon so n system library frameworks python framework versions python compatibility version current version reporter cgils cc resolution fixed ts component icetray summary python on mac defaulting to system priority normal keywords time milestone owner cgils type defect	1
27,351	4,970,017,694	IssuesEvent	2016-12-05 15:00:11	cakephp/cakephp	https://api.github.com/repos/cakephp/cakephp	closed	"HTTP/1.1 400" is not valid header name	Defect On hold	This is a (multiple allowed): * [x] bug * [ ] enhancement * [ ] feature-discussion (RFC) * CakePHP Version: 3.3.8 * Platform and Target: nginx, postgres, phpleague/oauth2-server v.4, uafrica/oauth-server ### What you did GET request to a Cake controller which is declined by the OAuth server w/ 400 HTTP code. ### What happened The header returned by phpleague/oauth2-server HTTP/1.1 400 is invalidated by Zend\Diactoros I see "HTTP/1.1 400" is not valid header name ### What you expected to happen The header should not be invalidated and the regular 400 response should be returned.	1.0	"HTTP/1.1 400" is not valid header name - This is a (multiple allowed): * [x] bug * [ ] enhancement * [ ] feature-discussion (RFC) * CakePHP Version: 3.3.8 * Platform and Target: nginx, postgres, phpleague/oauth2-server v.4, uafrica/oauth-server ### What you did GET request to a Cake controller which is declined by the OAuth server w/ 400 HTTP code. ### What happened The header returned by phpleague/oauth2-server HTTP/1.1 400 is invalidated by Zend\Diactoros I see "HTTP/1.1 400" is not valid header name ### What you expected to happen The header should not be invalidated and the regular 400 response should be returned.	defect	http is not valid header name this is a multiple allowed bug enhancement feature discussion rfc cakephp version platform and target nginx postgres phpleague server v uafrica oauth server what you did get request to a cake controller which is declined by the oauth server w http code what happened the header returned by phpleague server http is invalidated by zend diactoros i see http is not valid header name what you expected to happen the header should not be invalidated and the regular response should be returned	1
51,781	13,211,305,868	IssuesEvent	2020-08-15 22:11:13	icecube-trac/tix4	https://api.github.com/repos/icecube-trac/tix4	opened	steamshovel - link errors on OSX (Trac #1036)	Incomplete Migration Migrated from Trac combo core defect	<details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1036">https://code.icecube.wisc.edu/projects/icecube/ticket/1036</a>, reported by negaand owned by nega</em></summary> <p> ```json { "status": "closed", "changetime": "2015-06-29T19:43:17", "_ts": "1435606997623274", "description": "On OSX Mavericks+, `steamshovel` fails to build because `libshovelart` fails to link.\n\n{{{\nLinking CXX shared module ../lib/icecube/shovelart.so\nUndefined symbols for architecture x86_64:\n \"boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter>::dispose()\", referenced from:\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in PyArtist.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in Scenario.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in SceneObject.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in SceneVariant.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in Types.cpp.o\nld: symbol(s) not found for architecture x86_64\nclang: error: linker command failed with exit code 1 (use -v to see invocation)\nmake[2]: * [lib/icecube/shovelart.so] Error 1\nmake[1]: * [steamshovel/CMakeFiles/shovelart-pybindings.dir/all] Error 2\nmake: *** [all] Error 2\n}}}\n\n`::dispose()` is in pycompat.cpp which was remove from the build in r134357/IceCube.\nCombining diff:IceCube/projects/steamshovel/branches/new_shovelio/CMakeLists.txt@134353:134357 with diff:IceCube@134185:134188 demonstrates this fix.\n\nThis should be checked to ensure that re-including `pycompat.cpp` doesn't break something in recent commits.", "reporter": "nega", "cc": "hdembinski", "resolution": "fixed", "time": "2015-06-29T19:43:07", "component": "combo core", "summary": "steamshovel - link errors on OSX", "priority": "normal", "keywords": "", "milestone": "", "owner": "nega", "type": "defect" } ``` </p> </details>	1.0	steamshovel - link errors on OSX (Trac #1036) - <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1036">https://code.icecube.wisc.edu/projects/icecube/ticket/1036</a>, reported by negaand owned by nega</em></summary> <p> ```json { "status": "closed", "changetime": "2015-06-29T19:43:17", "_ts": "1435606997623274", "description": "On OSX Mavericks+, `steamshovel` fails to build because `libshovelart` fails to link.\n\n{{{\nLinking CXX shared module ../lib/icecube/shovelart.so\nUndefined symbols for architecture x86_64:\n \"boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter>::dispose()\", referenced from:\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in PyArtist.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in Scenario.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in SceneObject.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in SceneVariant.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void, boost::python::converter::shared_ptr_deleter> in Types.cpp.o\nld: symbol(s) not found for architecture x86_64\nclang: error: linker command failed with exit code 1 (use -v to see invocation)\nmake[2]: * [lib/icecube/shovelart.so] Error 1\nmake[1]: * [steamshovel/CMakeFiles/shovelart-pybindings.dir/all] Error 2\nmake: *** [all] Error 2\n}}}\n\n`::dispose()` is in pycompat.cpp which was remove from the build in r134357/IceCube.\nCombining diff:IceCube/projects/steamshovel/branches/new_shovelio/CMakeLists.txt@134353:134357 with diff:IceCube@134185:134188 demonstrates this fix.\n\nThis should be checked to ensure that re-including `pycompat.cpp` doesn't break something in recent commits.", "reporter": "nega", "cc": "hdembinski", "resolution": "fixed", "time": "2015-06-29T19:43:07", "component": "combo core", "summary": "steamshovel - link errors on OSX", "priority": "normal", "keywords": "", "milestone": "", "owner": "nega", "type": "defect" } ``` </p> </details>	defect	steamshovel link errors on osx trac migrated from json status closed changetime ts description on osx mavericks steamshovel fails to build because libshovelart fails to link n n nlinking cxx shared module lib icecube shovelart so nundefined symbols for architecture n boost detail sp counted impl pd dispose referenced from n vtable for boost detail sp counted impl pd in pyartist cpp o n vtable for boost detail sp counted impl pd in scenario cpp o n vtable for boost detail sp counted impl pd in sceneobject cpp o n vtable for boost detail sp counted impl pd in scenevariant cpp o n vtable for boost detail sp counted impl pd in types cpp o nld symbol s not found for architecture nclang error linker command failed with exit code use v to see invocation nmake error nmake error nmake error n n n dispose is in pycompat cpp which was remove from the build in icecube ncombining diff icecube projects steamshovel branches new shovelio cmakelists txt with diff icecube demonstrates this fix n nthis should be checked to ensure that re including pycompat cpp doesn t break something in recent commits reporter nega cc hdembinski resolution fixed time component combo core summary steamshovel link errors on osx priority normal keywords milestone owner nega type defect	1
9,380	8,616,060,374	IssuesEvent	2018-11-19 22:35:20	kyma-project/kyma	https://api.github.com/repos/kyma-project/kyma	closed	Service Binding failing for GCP service	area/service-catalog bug	<!-- Thank you for your contribution. Before you submit the issue: 1. Search open and closed issues for duplicates. 2. Read the contributing guidelines. --> Description Creating a service binding for a GCP service (Spanner) fails. Cluster version is 0.5 rc Expected result Service binding + usage is successfully created with using both the CLI and UI. Actual result Creating fails. The error message on the binding is the following: `Failed - ServiceBroker returned failure; bind operation will not be retried: Status: 422; ErrorMessage: <nil>; Description: This request requires client support for asynchronous service operations.; ResponseError: <nil> @ 2018-11-15 23:03:53 +0000 UTC ` Steps to reproduce 1. Provision an instance of the Spanner using kubectl ([spanner-instance.txt](https://github.com/kyma-project/kyma/files/2588582/spanner-instance.txt)) or svcat 2. Create a binding using the UI to a lambda function The binding will immediately fail. See screenshot below... ![service-binding-failure](https://user-images.githubusercontent.com/5688693/48611847-1a876780-e97f-11e8-939e-d6e66074acd1.png) Troubleshooting <!-- Describe the steps you have already taken to solve the issue. -->	1.0	Service Binding failing for GCP service - <!-- Thank you for your contribution. Before you submit the issue: 1. Search open and closed issues for duplicates. 2. Read the contributing guidelines. --> Description Creating a service binding for a GCP service (Spanner) fails. Cluster version is 0.5 rc Expected result Service binding + usage is successfully created with using both the CLI and UI. Actual result Creating fails. The error message on the binding is the following: `Failed - ServiceBroker returned failure; bind operation will not be retried: Status: 422; ErrorMessage: <nil>; Description: This request requires client support for asynchronous service operations.; ResponseError: <nil> @ 2018-11-15 23:03:53 +0000 UTC ` Steps to reproduce 1. Provision an instance of the Spanner using kubectl ([spanner-instance.txt](https://github.com/kyma-project/kyma/files/2588582/spanner-instance.txt)) or svcat 2. Create a binding using the UI to a lambda function The binding will immediately fail. See screenshot below... ![service-binding-failure](https://user-images.githubusercontent.com/5688693/48611847-1a876780-e97f-11e8-939e-d6e66074acd1.png) Troubleshooting <!-- Describe the steps you have already taken to solve the issue. -->	non_defect	service binding failing for gcp service thank you for your contribution before you submit the issue search open and closed issues for duplicates read the contributing guidelines description creating a service binding for a gcp service spanner fails cluster version is rc expected result service binding usage is successfully created with using both the cli and ui actual result creating fails the error message on the binding is the following failed servicebroker returned failure bind operation will not be retried status errormessage description this request requires client support for asynchronous service operations responseerror utc steps to reproduce provision an instance of the spanner using kubectl or svcat create a binding using the ui to a lambda function the binding will immediately fail see screenshot below troubleshooting	0
580,210	17,212,941,959	IssuesEvent	2021-07-19 07:52:56	nextcloud/calendar	https://api.github.com/repos/nextcloud/calendar	opened	Attendees can move and change scheduling object copies in their calendars	1 - to develop bug priority	https://datatracker.ietf.org/doc/html/rfc6638#section-3.2.2.1 shows which actions a client should be able to take on a scheduling object. We're currently allowing an attendee to edit calendar scheduling objects for their own private calendars - i. e., they can move and edit an event they are invited to. This does not propagate to the server, which is correct. The UI should reflect this.	1.0	Attendees can move and change scheduling object copies in their calendars - https://datatracker.ietf.org/doc/html/rfc6638#section-3.2.2.1 shows which actions a client should be able to take on a scheduling object. We're currently allowing an attendee to edit calendar scheduling objects for their own private calendars - i. e., they can move and edit an event they are invited to. This does not propagate to the server, which is correct. The UI should reflect this.	non_defect	attendees can move and change scheduling object copies in their calendars shows which actions a client should be able to take on a scheduling object we re currently allowing an attendee to edit calendar scheduling objects for their own private calendars i e they can move and edit an event they are invited to this does not propagate to the server which is correct the ui should reflect this	0
10,021	2,618,931,292	IssuesEvent	2015-03-03 00:00:22	chrsmith/open-ig	https://api.github.com/repos/chrsmith/open-ig	closed	Garthogs seem to be too strong even on easy difficulty	auto-migrated Balance Milestone-0.95.200 Priority-High Type-Defect	``` Reported by sailorshark, Nov 25, 2012 "7. Mire eljutottam oda, hogy neki támadjak (2427 dec.) egy Garthog bolygónak igencsak nagy meglepetés ért, hiszen 3 űrállomással 4 2-es szintű löveggel és bolygópajzsal kerültem szembe, ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet. Néztem végigjáttszás videót eredetiről és abban a Garthogok nem voltak ennyire legyőzhetetlenek. Bolgyóbajzs nem is volt és katonai űrállomás sem." Apparently, the Garthogs deploy defenses too quickly. I need to observe what the AI does. ``` Original issue reported on code.google.com by `akarn...@gmail.com` on 4 Dec 2012 at 2:51	1.0	Garthogs seem to be too strong even on easy difficulty - ``` Reported by sailorshark, Nov 25, 2012 "7. Mire eljutottam oda, hogy neki támadjak (2427 dec.) egy Garthog bolygónak igencsak nagy meglepetés ért, hiszen 3 űrállomással 4 2-es szintű löveggel és bolygópajzsal kerültem szembe, ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet. Néztem végigjáttszás videót eredetiről és abban a Garthogok nem voltak ennyire legyőzhetetlenek. Bolgyóbajzs nem is volt és katonai űrállomás sem." Apparently, the Garthogs deploy defenses too quickly. I need to observe what the AI does. ``` Original issue reported on code.google.com by `akarn...@gmail.com` on 4 Dec 2012 at 2:51	defect	garthogs seem to be too strong even on easy difficulty reported by sailorshark nov mire eljutottam oda hogy neki támadjak dec egy garthog bolygónak igencsak nagy meglepetés ért hiszen űrállomással es szintű löveggel és bolygópajzsal kerültem szembe ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet néztem végigjáttszás videót eredetiről és abban a garthogok nem voltak ennyire legyőzhetetlenek bolgyóbajzs nem is volt és katonai űrállomás sem apparently the garthogs deploy defenses too quickly i need to observe what the ai does original issue reported on code google com by akarn gmail com on dec at	1
4,843	2,610,158,109	IssuesEvent	2015-02-26 18:50:11	chrsmith/republic-at-war	https://api.github.com/repos/chrsmith/republic-at-war	closed	Map Issue	auto-migrated Priority-Medium Type-Defect	``` Fix passability on Tatooine ``` ----- Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:58	1.0	Map Issue - ``` Fix passability on Tatooine ``` ----- Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:58	defect	map issue fix passability on tatooine original issue reported on code google com by gmail com on jan at	1
36,598	8,028,957,574	IssuesEvent	2018-07-27 14:33:28	catmaid/CATMAID	https://api.github.com/repos/catmaid/CATMAID	closed	3D viewer: serialized node scaling is not properly reloaded	context: 3d-viewer difficulty: low status: done type: defect	Node scaling is serialized and deserialized into the controls correctly, but is not applied (i.e., is still default) until modifying the control field.	1.0	3D viewer: serialized node scaling is not properly reloaded - Node scaling is serialized and deserialized into the controls correctly, but is not applied (i.e., is still default) until modifying the control field.	defect	viewer serialized node scaling is not properly reloaded node scaling is serialized and deserialized into the controls correctly but is not applied i e is still default until modifying the control field	1
431,668	12,484,732,944	IssuesEvent	2020-05-30 16:10:29	spectrochempy/test_issues_migration_from_redmine	https://api.github.com/repos/spectrochempy/test_issues_migration_from_redmine	opened	Maker a Docker build, for an easy an portable installation.	Category: Deployment Priority: Minor Project: SpectroChemPy Status: In Progress Tracker: Task	Author: Christian Fernandez (Christian Fernandez ) Redmine Issue: 7, https://redmine.spectrochempy.fr/issues/7 --- Pytest ne s.execute pas. Pas trouve encore pourquoi warning pytest tests/ ============================= test session starts ============================== platform linux -- Python 3.7.1, pytest-4.0.2, py-1.7.0, pluggy-0.8.0 -- /opt/conda/bin/python cachedir: .pytest_cache rootdir: /opt/atlassian/pipelines/agent/build/tests, inifile: pytest.ini plugins: console-scripts-0.1.5 collecting ... Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4 Finished scanning for test reports. Found 0 test report files. Merged test suites, total number tests is 0, with 0 failures and 0 errors.	1.0	Maker a Docker build, for an easy an portable installation. - Author: Christian Fernandez (Christian Fernandez ) Redmine Issue: 7, https://redmine.spectrochempy.fr/issues/7 --- Pytest ne s.execute pas. Pas trouve encore pourquoi warning pytest tests/ ============================= test session starts ============================== platform linux -- Python 3.7.1, pytest-4.0.2, py-1.7.0, pluggy-0.8.0 -- /opt/conda/bin/python cachedir: .pytest_cache rootdir: /opt/atlassian/pipelines/agent/build/tests, inifile: pytest.ini plugins: console-scripts-0.1.5 collecting ... Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4 Finished scanning for test reports. Found 0 test report files. Merged test suites, total number tests is 0, with 0 failures and 0 errors.	non_defect	maker a docker build for an easy an portable installation author christian fernandez christian fernandez redmine issue pytest ne s execute pas pas trouve encore pourquoi warning pytest tests test session starts platform linux python pytest py pluggy opt conda bin python cachedir pytest cache rootdir opt atlassian pipelines agent build tests inifile pytest ini plugins console scripts collecting searching for test report files in directories named down to a depth of finished scanning for test reports found test report files merged test suites total number tests is with failures and errors	0
79,621	28,485,027,214	IssuesEvent	2023-04-18 07:14:12	hazelcast/hazelcast	https://api.github.com/repos/hazelcast/hazelcast	closed	No backup flag is passed to getRecordOrNull method in lock interceptor operation [HZ-2287]	Type: Defect Team: Core Module: IMap Module: Lock to-jira	Issue makes itself visible by publishing multiple events for expiration of a single key, normally it must be 1. With this defect, number of events for a single key is same with number of replicas(owner+backup) in this case. Workaround: Using cp-subsystem locking instead of imap locking fixes the issue.	1.0	No backup flag is passed to getRecordOrNull method in lock interceptor operation [HZ-2287] - Issue makes itself visible by publishing multiple events for expiration of a single key, normally it must be 1. With this defect, number of events for a single key is same with number of replicas(owner+backup) in this case. Workaround: Using cp-subsystem locking instead of imap locking fixes the issue.	defect	no backup flag is passed to getrecordornull method in lock interceptor operation issue makes itself visible by publishing multiple events for expiration of a single key normally it must be with this defect number of events for a single key is same with number of replicas owner backup in this case workaround using cp subsystem locking instead of imap locking fixes the issue	1
12,041	14,214,351,298	IssuesEvent	2020-11-17 05:00:58	ice1000/jimgui	https://api.github.com/repos/ice1000/jimgui	closed	Ubuntu 16.04 support?	compatibility	I've tried jimgui on windows 10 64bit and everything worked perfectly, today I tried on Ubuntu 16.04 64bit but I can't run it. I get the error: > java.lang.UnsupportedOperationException: java.lang.UnsatisfiedLinkError: /tmp/jimgui1605317730496/libjimgui.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/jimgui1605317730496/libjimgui.so) I think it's because on ubuntu 16.04 glibc version 2.23 is used. Does this mean jimgui only supports >=Ubuntu18?	True	Ubuntu 16.04 support? - I've tried jimgui on windows 10 64bit and everything worked perfectly, today I tried on Ubuntu 16.04 64bit but I can't run it. I get the error: > java.lang.UnsupportedOperationException: java.lang.UnsatisfiedLinkError: /tmp/jimgui1605317730496/libjimgui.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/jimgui1605317730496/libjimgui.so) I think it's because on ubuntu 16.04 glibc version 2.23 is used. Does this mean jimgui only supports >=Ubuntu18?	non_defect	ubuntu support i ve tried jimgui on windows and everything worked perfectly today i tried on ubuntu but i can t run it i get the error java lang unsupportedoperationexception java lang unsatisfiedlinkerror tmp libjimgui so lib linux gnu libm so version glibc not found required by tmp libjimgui so i think it s because on ubuntu glibc version is used does this mean jimgui only supports	0
48,832	12,247,361,308	IssuesEvent	2020-05-05 15:46:45	GoogleCloudPlatform/python-docs-samples	https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples	closed	iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed	api: cloudiot buildcop: flaky buildcop: issue priority: p2 type: bug	iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed buildID: 48f7af782874d6a51ce4b361ccde2da3bc075ffa buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31 status: failed	2.0	iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed - iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed buildID: 48f7af782874d6a51ce4b361ccde2da3bc075ffa buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31 status: failed	non_defect	iot api client mqtt example cloudiot mqtt example test test gateway send data for device failed iot api client mqtt example cloudiot mqtt example test test gateway send data for device failed buildid buildurl status failed	0
27,231	4,939,525,681	IssuesEvent	2016-11-29 14:37:49	jfabry/LiveRobotProgramming	https://api.github.com/repos/jfabry/LiveRobotProgramming	closed	Import of a program that does not parse crashes the interpreter	Component-Parser Priority-High Type-Defect	We should check in LRPProgram>>exportedMachines and loadImports if the current ast is not a failure	1.0	Import of a program that does not parse crashes the interpreter - We should check in LRPProgram>>exportedMachines and loadImports if the current ast is not a failure	defect	import of a program that does not parse crashes the interpreter we should check in lrpprogram exportedmachines and loadimports if the current ast is not a failure	1
64,214	18,280,374,863	IssuesEvent	2021-10-05 01:58:30	microsoft/STL	https://api.github.com/repos/microsoft/STL	opened	P2432R1 Fix `istream_view`	cxx20 ranges defect report	[P2432R1](https://wg21.link/P2432R1) Fix `istream_view` This paper intentionally does not provide a feature-test macro.	1.0	P2432R1 Fix `istream_view` - [P2432R1](https://wg21.link/P2432R1) Fix `istream_view` This paper intentionally does not provide a feature-test macro.	defect	fix istream view fix istream view this paper intentionally does not provide a feature test macro	1
57,025	15,595,420,550	IssuesEvent	2021-03-18 14:52:35	department-of-veterans-affairs/va.gov-cms	https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms	closed	field_office on Vet Center Locations List should only allow vet_center content type, not MVC, OS, or CAP	Content model Defect Vet Center	Describe the defect Vet Center entity reference on Locations List should only allow _Vet Center_ content type. To Reproduce Steps to reproduce the behavior: 1. Go to /node/16478/edit 2. In the Vet Center entity reference field, you will see Outstations and Mobile Vet Centers Expected behavior Only Vet Centers should be visible (no outstations or mobile vet centers or CAPs) Implementation Config at /admin/structure/types/manage/vet_center_locations_list/fields/node.vet_center_locations_list.field_office	1.0	field_office on Vet Center Locations List should only allow vet_center content type, not MVC, OS, or CAP - Describe the defect Vet Center entity reference on Locations List should only allow _Vet Center_ content type. To Reproduce Steps to reproduce the behavior: 1. Go to /node/16478/edit 2. In the Vet Center entity reference field, you will see Outstations and Mobile Vet Centers Expected behavior Only Vet Centers should be visible (no outstations or mobile vet centers or CAPs) Implementation Config at /admin/structure/types/manage/vet_center_locations_list/fields/node.vet_center_locations_list.field_office	defect	field office on vet center locations list should only allow vet center content type not mvc os or cap describe the defect vet center entity reference on locations list should only allow vet center content type to reproduce steps to reproduce the behavior go to node edit in the vet center entity reference field you will see outstations and mobile vet centers expected behavior only vet centers should be visible no outstations or mobile vet centers or caps implementation config at admin structure types manage vet center locations list fields node vet center locations list field office	1
76,900	21,609,252,350	IssuesEvent	2022-05-04 08:23:22	cryspen/hacl-packages	https://api.github.com/repos/cryspen/hacl-packages	closed	Feature parity with upstream dist	build 🔨	Tracking build feature parity with the upstream hacl* dist directory.	1.0	Feature parity with upstream dist - Tracking build feature parity with the upstream hacl* dist directory.	non_defect	feature parity with upstream dist tracking build feature parity with the upstream hacl dist directory	0
48,741	25,787,899,596	IssuesEvent	2022-12-09 22:46:37	model-checking/kani	https://api.github.com/repos/model-checking/kani	closed	Memory reallocation with `Vec` kills performance	[C] Bug [E] Performance T-CBMC	<!-- If this is a security issue, please report it following the [security reporting procedure](https://github.com/model-checking/kani/security/policy). --> <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the issue, along with the information necessary to replicate. --> This example is from #1651, implemented using a vector: <!-- If the reproducing code is small, please post it here. Otherwise, please attach the relevant files to this issue. Alternatively, post a link to the repository and branch that exposes the issue. --> ```rust const N: usize = 4; const M: usize = N+1; trait T { fn foo(&self) -> i32; } struct A { x: i32, } impl T for A { fn foo(&self) -> i32 { self.x } } struct B { x: i32, } impl T for B { fn foo(&self) -> i32 { self.x } } #[kani::proof] #[kani::unwind(6)] fn main() { //let mut a: Vec<Box<dyn T>> = Vec::with_capacity(N); let mut a: Vec<Box<dyn T>> = Vec::new(); a.push(Box::new(A { x: 5 })); for i in 1..N { a.push(Box::new(B { x: 9 })); } let mut val: i32 = 0; for _i in 0..M { let index: usize = kani::any(); kani::assume(index < a.len()); let x = a[index].as_mut().foo(); val += x; } } ``` with Kani version: d53296ac3fb When the vector is created with `Vec::with_capacity` to pre-allocate memory, verification time is 3.2 seconds, and consumes less than 1 GB of memory. But when using `Vec::new()`, verification takes 160 seconds, and consumes more than 14 GB of memory. If I bump `N` to 5 (and the unwind value to 7), the `Vec::with_capacity` version finishes in 7 seconds, and consumes less than 1 GB, and the `Vec::new` version runs out of memory (>32 GB) after running for about 3 minutes.	True	Memory reallocation with `Vec` kills performance - <!-- If this is a security issue, please report it following the [security reporting procedure](https://github.com/model-checking/kani/security/policy). --> <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the issue, along with the information necessary to replicate. --> This example is from #1651, implemented using a vector: <!-- If the reproducing code is small, please post it here. Otherwise, please attach the relevant files to this issue. Alternatively, post a link to the repository and branch that exposes the issue. --> ```rust const N: usize = 4; const M: usize = N+1; trait T { fn foo(&self) -> i32; } struct A { x: i32, } impl T for A { fn foo(&self) -> i32 { self.x } } struct B { x: i32, } impl T for B { fn foo(&self) -> i32 { self.x } } #[kani::proof] #[kani::unwind(6)] fn main() { //let mut a: Vec<Box<dyn T>> = Vec::with_capacity(N); let mut a: Vec<Box<dyn T>> = Vec::new(); a.push(Box::new(A { x: 5 })); for i in 1..N { a.push(Box::new(B { x: 9 })); } let mut val: i32 = 0; for _i in 0..M { let index: usize = kani::any(); kani::assume(index < a.len()); let x = a[index].as_mut().foo(); val += x; } } ``` with Kani version: d53296ac3fb When the vector is created with `Vec::with_capacity` to pre-allocate memory, verification time is 3.2 seconds, and consumes less than 1 GB of memory. But when using `Vec::new()`, verification takes 160 seconds, and consumes more than 14 GB of memory. If I bump `N` to 5 (and the unwind value to 7), the `Vec::with_capacity` version finishes in 7 seconds, and consumes less than 1 GB, and the `Vec::new` version runs out of memory (>32 GB) after running for about 3 minutes.	non_defect	memory reallocation with vec kills performance if this is a security issue please report it following the thank you for filing a bug report 🐛 please provide a short summary of the issue along with the information necessary to replicate this example is from implemented using a vector if the reproducing code is small please post it here otherwise please attach the relevant files to this issue alternatively post a link to the repository and branch that exposes the issue rust const n usize const m usize n trait t fn foo self struct a x impl t for a fn foo self self x struct b x impl t for b fn foo self self x fn main let mut a vec vec with capacity n let mut a vec vec new a push box new a x for i in n a push box new b x let mut val for i in m let index usize kani any kani assume index a len let x a as mut foo val x with kani version when the vector is created with vec with capacity to pre allocate memory verification time is seconds and consumes less than gb of memory but when using vec new verification takes seconds and consumes more than gb of memory if i bump n to and the unwind value to the vec with capacity version finishes in seconds and consumes less than gb and the vec new version runs out of memory gb after running for about minutes	0
224,457	17,188,988,531	IssuesEvent	2021-07-16 08:14:06	capactio/capact	https://api.github.com/repos/capactio/capact	closed	Add quality badges to the repository README	area/community area/documentation enhancement size/XS	## Description - Generate quality badges: - [Github Actions](https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge) - https://goreportcard.com/ - https://bestpractices.coreinfrastructure.org/en - Consider Snyk and CodeClimate badges - Check our score and fix detected issues Timeboxed task, we do as much as we can in a given time. ## Reason Show that we follow best practices during Capact development and that we do care about the quality of the project.	1.0	Add quality badges to the repository README - ## Description - Generate quality badges: - [Github Actions](https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge) - https://goreportcard.com/ - https://bestpractices.coreinfrastructure.org/en - Consider Snyk and CodeClimate badges - Check our score and fix detected issues Timeboxed task, we do as much as we can in a given time. ## Reason Show that we follow best practices during Capact development and that we do care about the quality of the project.	non_defect	add quality badges to the repository readme description generate quality badges consider snyk and codeclimate badges check our score and fix detected issues timeboxed task we do as much as we can in a given time reason show that we follow best practices during capact development and that we do care about the quality of the project	0
69,902	22,744,619,423	IssuesEvent	2022-07-07 08:04:47	melink14/rikaikun	https://api.github.com/repos/melink14/rikaikun	closed	Error message	Type-Defect auto-migrated P2 obsolete	``` I've been trying to save words into file using Rikaichan, but seem to always get this error: Error while saving: [Exception..."Component returned failure code 0x800040005" (NS_ERROR_FAILURE) [nslFileOutputStream.init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: Chrome://rikaichan/content/ricaichan.js :: anonymous :: line 697" data:no] Any idea what might be wrong? ``` Original issue reported on code.google.com by `joshuagi...@yahoo.co.uk` on 16 Aug 2013 at 4:33	1.0	Error message - ``` I've been trying to save words into file using Rikaichan, but seem to always get this error: Error while saving: [Exception..."Component returned failure code 0x800040005" (NS_ERROR_FAILURE) [nslFileOutputStream.init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: Chrome://rikaichan/content/ricaichan.js :: anonymous :: line 697" data:no] Any idea what might be wrong? ``` Original issue reported on code.google.com by `joshuagi...@yahoo.co.uk` on 16 Aug 2013 at 4:33	defect	error message i ve been trying to save words into file using rikaichan but seem to always get this error error while saving exception component returned failure code ns error failure nsresult ns error failure location js frame chrome rikaichan content ricaichan js anonymous line data no any idea what might be wrong original issue reported on code google com by joshuagi yahoo co uk on aug at	1
79,218	28,045,877,127	IssuesEvent	2023-03-28 22:50:29	cliffparnitzky/ApparelManager	https://api.github.com/repos/cliffparnitzky/ApparelManager	closed	Using a visibility toggle without a "data-state" attribute is deprecated.	Defect ✓ - Accepted	Using a visibility toggle without a "data-state" attribute is deprecated. Please adjust your Contao DCA file.	1.0	Using a visibility toggle without a "data-state" attribute is deprecated. - Using a visibility toggle without a "data-state" attribute is deprecated. Please adjust your Contao DCA file.	defect	using a visibility toggle without a data state attribute is deprecated using a visibility toggle without a data state attribute is deprecated please adjust your contao dca file	1
10,915	2,622,847,876	IssuesEvent	2015-03-04 08:03:33	max99x/pagemon-chrome-ext	https://api.github.com/repos/max99x/pagemon-chrome-ext	closed	Still detecting change	auto-migrated Priority-Medium Type-Defect	``` Extension is still reporting changed page, even if there is only minor changes. http://wmmania.cz/clanky/android/ On bottom of page is time and number of queries, that is different on every reload. So I use Custom-mode - selector functionality with #article_list>div.article:nth-child(1)>div.heading>h3 On test button, it gives me only name of first article. But after a hour or two it mark page as changed. But only highlighted change, is time on page bottom. Thanks for help ``` Original issue reported on code.google.com by `hund...@gmail.com` on 22 Dec 2010 at 1:04	1.0	Still detecting change - ``` Extension is still reporting changed page, even if there is only minor changes. http://wmmania.cz/clanky/android/ On bottom of page is time and number of queries, that is different on every reload. So I use Custom-mode - selector functionality with #article_list>div.article:nth-child(1)>div.heading>h3 On test button, it gives me only name of first article. But after a hour or two it mark page as changed. But only highlighted change, is time on page bottom. Thanks for help ``` Original issue reported on code.google.com by `hund...@gmail.com` on 22 Dec 2010 at 1:04	defect	still detecting change extension is still reporting changed page even if there is only minor changes on bottom of page is time and number of queries that is different on every reload so i use custom mode selector functionality with article list div article nth child div heading on test button it gives me only name of first article but after a hour or two it mark page as changed but only highlighted change is time on page bottom thanks for help original issue reported on code google com by hund gmail com on dec at	1
38,610	8,933,332,043	IssuesEvent	2019-01-23 01:32:28	Microsoft/spring-data-cosmosdb	https://api.github.com/repos/Microsoft/spring-data-cosmosdb	closed	exception when integrate with spring data commons 2.1.x	Defect	``` Caused by: java.lang.IllegalStateException: You have defined query method in the repository but you don't have any query lookup strategy defined. The infrastructure apparently does not support query methods! at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.<init>(RepositoryFactorySupport.java:545) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.getNullable(Lazy.java:211) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.get(Lazy.java:94) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] ```	1.0	exception when integrate with spring data commons 2.1.x - ``` Caused by: java.lang.IllegalStateException: You have defined query method in the repository but you don't have any query lookup strategy defined. The infrastructure apparently does not support query methods! at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.<init>(RepositoryFactorySupport.java:545) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.getNullable(Lazy.java:211) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.get(Lazy.java:94) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] ```	defect	exception when integrate with spring data commons x caused by java lang illegalstateexception you have defined query method in the repository but you don t have any query lookup strategy defined the infrastructure apparently does not support query methods at org springframework data repository core support repositoryfactorysupport queryexecutormethodinterceptor repositoryfactorysupport java at org springframework data repository core support repositoryfactorysupport getrepository repositoryfactorysupport java at org springframework data repository core support repositoryfactorybeansupport lambda afterpropertiesset repositoryfactorybeansupport java at org springframework data util lazy getnullable lazy java at org springframework data util lazy get lazy java	1
10,486	2,622,167,569	IssuesEvent	2015-03-04 00:13:04	byzhang/rapidjson	https://api.github.com/repos/byzhang/rapidjson	closed	Does not compile on Embarcadero tools.	auto-migrated Priority-Medium Type-Defect	``` What steps will reproduce the problem? 1. Include the headers in a cpp file. 2. Try to compile it with the Embarcadero command line compiler. What is the expected output? What do you see instead? Expecting to see it compile. Instead, it failed to compile giving several error messages. ... Error E2450 include\rapidjson/document.h 30: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 30: Size of 'name' is unknown or zero Error E2450 include\rapidjson/document.h 31: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 31: Size of 'value' is unknown or zero ... What version of the product are you using? On what operating system? Version 0.1 on Windows 7 Please provide any additional information below. I've tried in the ancient 5.5 version of the compiler by Borland and the new one from Embarcadero. ``` Original issue reported on code.google.com by `odhinnsr...@gmail.com` on 29 Mar 2012 at 5:14	1.0	Does not compile on Embarcadero tools. - ``` What steps will reproduce the problem? 1. Include the headers in a cpp file. 2. Try to compile it with the Embarcadero command line compiler. What is the expected output? What do you see instead? Expecting to see it compile. Instead, it failed to compile giving several error messages. ... Error E2450 include\rapidjson/document.h 30: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 30: Size of 'name' is unknown or zero Error E2450 include\rapidjson/document.h 31: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 31: Size of 'value' is unknown or zero ... What version of the product are you using? On what operating system? Version 0.1 on Windows 7 Please provide any additional information below. I've tried in the ancient 5.5 version of the compiler by Borland and the new one from Embarcadero. ``` Original issue reported on code.google.com by `odhinnsr...@gmail.com` on 29 Mar 2012 at 5:14	defect	does not compile on embarcadero tools what steps will reproduce the problem include the headers in a cpp file try to compile it with the embarcadero command line compiler what is the expected output what do you see instead expecting to see it compile instead it failed to compile giving several error messages error include rapidjson document h undefined structure genericvalue error include rapidjson document h size of name is unknown or zero error include rapidjson document h undefined structure genericvalue error include rapidjson document h size of value is unknown or zero what version of the product are you using on what operating system version on windows please provide any additional information below i ve tried in the ancient version of the compiler by borland and the new one from embarcadero original issue reported on code google com by odhinnsr gmail com on mar at	1
48,001	13,067,375,743	IssuesEvent	2020-07-31 00:15:34	icecube-trac/tix2	https://api.github.com/repos/icecube-trac/tix2	closed	icerec, simulation - remove dst-extractor from meta-projects (Trac #1614)	Migrated from Trac cmake defect	according to #1571 `dst-extractor` is no more Migrated from https://code.icecube.wisc.edu/ticket/1614 ```json { "status": "closed", "changetime": "2019-02-13T14:11:42", "description": "according to #1579 `dst-extractor` is no more", "reporter": "nega", "cc": "olivas", "resolution": "fixed", "_ts": "1550067102580394", "component": "cmake", "summary": "icerec, simulation - remove dst-extractor from meta-projects", "priority": "normal", "keywords": "", "time": "2016-03-30T21:00:35", "milestone": "", "owner": "nega", "type": "defect" } ```	1.0	icerec, simulation - remove dst-extractor from meta-projects (Trac #1614) - according to #1571 `dst-extractor` is no more Migrated from https://code.icecube.wisc.edu/ticket/1614 ```json { "status": "closed", "changetime": "2019-02-13T14:11:42", "description": "according to #1579 `dst-extractor` is no more", "reporter": "nega", "cc": "olivas", "resolution": "fixed", "_ts": "1550067102580394", "component": "cmake", "summary": "icerec, simulation - remove dst-extractor from meta-projects", "priority": "normal", "keywords": "", "time": "2016-03-30T21:00:35", "milestone": "", "owner": "nega", "type": "defect" } ```	defect	icerec simulation remove dst extractor from meta projects trac according to dst extractor is no more migrated from json status closed changetime description according to dst extractor is no more reporter nega cc olivas resolution fixed ts component cmake summary icerec simulation remove dst extractor from meta projects priority normal keywords time milestone owner nega type defect	1
2,889	2,607,964,661	IssuesEvent	2015-02-26 00:41:47	chrsmithdemos/leveldb	https://api.github.com/repos/chrsmithdemos/leveldb	closed	Lots of zero-size files in ENOSP situation	auto-migrated Priority-Medium Type-Defect	``` This is just a FYI. We've seen this odd behavior, when running out of disk space. In this particular LevelDB instance, we had ~500.000 files, of which ~386.000 were zero-length. Let me know if you want more info for further investigation if you find this relevant. Kresten ^count ^byte size 8986 2100454 8986 2099630 8988 2097214 3 2031616 8986 1141855 8986 817817 8987 796603 8987 786279 8988 679909 8986 675593 8986 622029 8987 549499 8986 545361 8988 543867 8986 483052 2 458752 8987 270322 2 196608 8987 173884 5 65536 386412 0 ``` ----- Original issue reported on code.google.com by `kresten....@gmail.com` on 22 Dec 2011 at 4:39	1.0	Lots of zero-size files in ENOSP situation - ``` This is just a FYI. We've seen this odd behavior, when running out of disk space. In this particular LevelDB instance, we had ~500.000 files, of which ~386.000 were zero-length. Let me know if you want more info for further investigation if you find this relevant. Kresten ^count ^byte size 8986 2100454 8986 2099630 8988 2097214 3 2031616 8986 1141855 8986 817817 8987 796603 8987 786279 8988 679909 8986 675593 8986 622029 8987 549499 8986 545361 8988 543867 8986 483052 2 458752 8987 270322 2 196608 8987 173884 5 65536 386412 0 ``` ----- Original issue reported on code.google.com by `kresten....@gmail.com` on 22 Dec 2011 at 4:39	defect	lots of zero size files in enosp situation this is just a fyi we ve seen this odd behavior when running out of disk space in this particular leveldb instance we had files of which were zero length let me know if you want more info for further investigation if you find this relevant kresten count byte size original issue reported on code google com by kresten gmail com on dec at	1
225,665	24,881,083,849	IssuesEvent	2022-10-28 01:11:34	mgh3326/createandread	https://api.github.com/repos/mgh3326/createandread	closed	WS-2022-0334 (Medium) detected in nokogiri-1.10.7.gem - autoclosed	security vulnerability	## WS-2022-0334 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nokogiri-1.10.7.gem</b></p></summary> <p>Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri's many features is the ability to search documents via XPath or CSS3 selectors.</p> <p>Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.7.gem">https://rubygems.org/gems/nokogiri-1.10.7.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /var/lib/gems/2.3.0/cache/nokogiri-1.10.7-x64-mingw32.gem</p> <p> Dependency Hierarchy: - rails-6.0.1.gem (Root Library) - actiontext-6.0.1.gem - :x: nokogiri-1.10.7.gem (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> nokogiri up to and including 1.13.8 is affected by several vulnerabilities (CVE-2022-40303, CVE-2022-40304 and CVE-2022-2309) in the dependency bundled libxml2 library. Version 1.13.9 of nokogiri contains a patch where the dependency is upgraded with the patches as well. <p>Publish Date: 2022-10-18 <p>URL: <a href=https://github.com/sparklemotion/nokogiri/commit/e8cfe13953c63099f879d8a25ca70a909e19fb96>WS-2022-0334</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-2qc6-mcvw-92cw">https://github.com/advisories/GHSA-2qc6-mcvw-92cw</a></p> <p>Release Date: 2022-10-18</p> <p>Fix Resolution: nokogiri - 1.13.9</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	True	WS-2022-0334 (Medium) detected in nokogiri-1.10.7.gem - autoclosed - ## WS-2022-0334 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nokogiri-1.10.7.gem</b></p></summary> <p>Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri's many features is the ability to search documents via XPath or CSS3 selectors.</p> <p>Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.7.gem">https://rubygems.org/gems/nokogiri-1.10.7.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /var/lib/gems/2.3.0/cache/nokogiri-1.10.7-x64-mingw32.gem</p> <p> Dependency Hierarchy: - rails-6.0.1.gem (Root Library) - actiontext-6.0.1.gem - :x: nokogiri-1.10.7.gem (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> nokogiri up to and including 1.13.8 is affected by several vulnerabilities (CVE-2022-40303, CVE-2022-40304 and CVE-2022-2309) in the dependency bundled libxml2 library. Version 1.13.9 of nokogiri contains a patch where the dependency is upgraded with the patches as well. <p>Publish Date: 2022-10-18 <p>URL: <a href=https://github.com/sparklemotion/nokogiri/commit/e8cfe13953c63099f879d8a25ca70a909e19fb96>WS-2022-0334</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-2qc6-mcvw-92cw">https://github.com/advisories/GHSA-2qc6-mcvw-92cw</a></p> <p>Release Date: 2022-10-18</p> <p>Fix Resolution: nokogiri - 1.13.9</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_defect	ws medium detected in nokogiri gem autoclosed ws medium severity vulnerability vulnerable library nokogiri gem nokogiri 鋸 is an html xml sax and reader parser among nokogiri s many features is the ability to search documents via xpath or selectors library home page a href path to dependency file gemfile lock path to vulnerable library var lib gems cache nokogiri gem dependency hierarchy rails gem root library actiontext gem x nokogiri gem vulnerable library found in base branch master vulnerability details nokogiri up to and including is affected by several vulnerabilities cve cve and cve in the dependency bundled library version of nokogiri contains a patch where the dependency is upgraded with the patches as well publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nokogiri step up your open source security game with mend	0
40,533	10,036,131,737	IssuesEvent	2019-07-18 09:55:21	ShaikASK/Testing	https://api.github.com/repos/ShaikASK/Testing	opened	Candidate : Dashboard : Double space is observed in between words of last Step in the last line	Candidate Dashboard Candidate Module Defect P3	Steps To Replicate : 1.Launch the URL 2.Sign in as Candidate 3.Click on “Get Started” button 4.Sign the Offer Letter 5.fill the common details webform 6.fill the required documents and navigate to “dashboard Screen 7.Check the alignment of step description displayed at candidate dashboard Experienced Behavior : Observed that Candidate : Dashboard : Double space is observed in between words of last Step in the last line (Refer Screen Shot) Expected Behavior : Ensure that it should not display double spacing between words of last Step in the last line ![UI issue](https://user-images.githubusercontent.com/31955617/61448239-26915200-a970-11e9-8256-8ed4a0668701.jpg)	1.0	Candidate : Dashboard : Double space is observed in between words of last Step in the last line - Steps To Replicate : 1.Launch the URL 2.Sign in as Candidate 3.Click on “Get Started” button 4.Sign the Offer Letter 5.fill the common details webform 6.fill the required documents and navigate to “dashboard Screen 7.Check the alignment of step description displayed at candidate dashboard Experienced Behavior : Observed that Candidate : Dashboard : Double space is observed in between words of last Step in the last line (Refer Screen Shot) Expected Behavior : Ensure that it should not display double spacing between words of last Step in the last line ![UI issue](https://user-images.githubusercontent.com/31955617/61448239-26915200-a970-11e9-8256-8ed4a0668701.jpg)	defect	candidate dashboard double space is observed in between words of last step in the last line steps to replicate launch the url sign in as candidate click on “get started” button sign the offer letter fill the common details webform fill the required documents and navigate to “dashboard screen check the alignment of step description displayed at candidate dashboard experienced behavior observed that candidate dashboard double space is observed in between words of last step in the last line refer screen shot expected behavior ensure that it should not display double spacing between words of last step in the last line	1

22,539

4,817,559,919

IssuesEvent

2016-11-04 14:04:36

outcobra/outstanding-cobra

https://api.github.com/repos/outcobra/outstanding-cobra

opened

contributing guidelines are off

administration/documentation bug

The section [here](https://github.com/outcobra/outstanding-cobra/blob/develop/CONTRIBUTING.md#branches) is not quite right. I think the branches should be called by their actual names (as in `master`, `develop` and `feature/your-feature`).

1.0

contributing guidelines are off - The section [here](https://github.com/outcobra/outstanding-cobra/blob/develop/CONTRIBUTING.md#branches) is not quite right. I think the branches should be called by their actual names (as in `master`, `develop` and `feature/your-feature`).

non_defect

contributing guidelines are off the section is not quite right i think the branches should be called by their actual names as in master develop and feature your feature

0

20,774

3,413,990,381

IssuesEvent

2015-12-07 01:45:22

bounswe/bounswe2015group8

https://api.github.com/repos/bounswe/bounswe2015group8

closed

Post-Heritage Linking

Priority-Medium Type-Defect

Right now, we can relate a post to only one heritage. The users shall be able to link posts with other heritages. Implement a basic system in which they can accomplish that.

1.0

Post-Heritage Linking - Right now, we can relate a post to only one heritage. The users shall be able to link posts with other heritages. Implement a basic system in which they can accomplish that.

defect

post heritage linking right now we can relate a post to only one heritage the users shall be able to link posts with other heritages implement a basic system in which they can accomplish that

1

302,321

26,139,371,862

IssuesEvent

2022-12-29 16:11:24

DMTF/libspdm

https://api.github.com/repos/DMTF/libspdm

opened

Testing should be opt in

enhancement test

Now that there appears to be a class of Integrators who will be using libspdm as a real library and who don't care about running its unit and fuzz testing (for example https://github.com/altera-opensource/verifier), we should make testing opt in when CMake is invoked; ie `-DTEST=On`.

1.0

Testing should be opt in - Now that there appears to be a class of Integrators who will be using libspdm as a real library and who don't care about running its unit and fuzz testing (for example https://github.com/altera-opensource/verifier), we should make testing opt in when CMake is invoked; ie `-DTEST=On`.

non_defect

testing should be opt in now that there appears to be a class of integrators who will be using libspdm as a real library and who don t care about running its unit and fuzz testing for example we should make testing opt in when cmake is invoked ie dtest on

0

27,366

4,974,227,299

IssuesEvent

2016-12-06 05:19:39

rbei-etas/busmaster

https://api.github.com/repos/rbei-etas/busmaster

opened

Trace window shows unexpected messages while enabling node simulation after disabling it

1.3 patch (defect) 3.3 low priority (EC3)

1. Add a node and message hanlder to it And trace some messages inside the handler for LIN 2.Add the same frame and response in tx wnd 3.Transmit the messahe by disabling the nodes 4.Enable the nodes and and connect 5.Trace window is printing the trace messages which was added in the message handler [Issue is reproducible in V2.6.4]

1.0

Trace window shows unexpected messages while enabling node simulation after disabling it - 1. Add a node and message hanlder to it And trace some messages inside the handler for LIN 2.Add the same frame and response in tx wnd 3.Transmit the messahe by disabling the nodes 4.Enable the nodes and and connect 5.Trace window is printing the trace messages which was added in the message handler [Issue is reproducible in V2.6.4]

defect

trace window shows unexpected messages while enabling node simulation after disabling it add a node and message hanlder to it and trace some messages inside the handler for lin add the same frame and response in tx wnd transmit the messahe by disabling the nodes enable the nodes and and connect trace window is printing the trace messages which was added in the message handler

1

5,162

2,610,182,230

IssuesEvent

2015-02-26 18:58:06

chrsmith/quchuseban

https://api.github.com/repos/chrsmith/quchuseban

opened

剖析怎么去除脸上的色斑

auto-migrated Priority-Medium Type-Defect

``` 《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。 　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� ��购了2套黛芙薇尔。 　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊! 阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐�� 去掉吗? 　　答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新�� 客都是通过老顾客介绍而来，口碑由此而来! 　　2，服用黛芙薇尔美白，会伤身体吗?有副作用吗? 　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技�� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖! 　　3，去除黄褐斑之后，会反弹吗? 　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌!我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗? 　　4，你们的价格有点贵，能不能便宜一点? 　　答：如果您使用西药最少需要2000元，煎服的药最少需要3 000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　5，我适合用黛芙薇尔精华液吗? 　　答：黛芙薇尔适用人群：　　1、生理紊乱引起的黄褐斑人群　　2、生育引起的妊娠斑人群　　3、年纪增长引起的老年斑人群　　4、化妆品色素沉积、辐射斑人群　　5、长期日照引起的日晒斑人群　　6、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法 1、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。 2、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素A、B12、E，还含� ��、镁等23种矿物质，可调节人体的新陈代谢，止血止痛，消� ��安神。 ``` ----- Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 2:45

1.0

剖析怎么去除脸上的色斑 - ``` 《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。 　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� ��购了2套黛芙薇尔。 　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊! 阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐�� 去掉吗? 　　答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新�� 客都是通过老顾客介绍而来，口碑由此而来! 　　2，服用黛芙薇尔美白，会伤身体吗?有副作用吗? 　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技�� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖! 　　3，去除黄褐斑之后，会反弹吗? 　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌!我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗? 　　4，你们的价格有点贵，能不能便宜一点? 　　答：如果您使用西药最少需要2000元，煎服的药最少需要3 000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　5，我适合用黛芙薇尔精华液吗? 　　答：黛芙薇尔适用人群：　　1、生理紊乱引起的黄褐斑人群　　2、生育引起的妊娠斑人群　　3、年纪增长引起的老年斑人群　　4、化妆品色素沉积、辐射斑人群　　5、长期日照引起的日晒斑人群　　6、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法 1、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。 2、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素A、B12、E，还含� ��、镁等23种矿物质，可调节人体的新陈代谢，止血止痛，消� ��安神。 ``` ----- Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 2:45

defect

剖析怎么去除脸上的色斑《摘要》有时候，希望时间为自己停下，就这样和喜欢的人地老天荒�� 有时候，发现身边的人都不了解自己，面对着身边的人，突� ��觉得说不出话；有时候，在自己脆弱的时候，想一个人躲起来，不愿别人看到自己的伤口；有时候，突然很想逃离现在�� 生活，想不顾一切收拾自己简单的行李去流浪。很多美女对� ��如何祛斑都比较关注，毕竟谁也不想脸上长很多难看的斑，那么到底吃什么可以祛斑那怎么去除脸上的色斑，《客户案例》　　刚开始我祛斑的时候还真是费了不少劲，刚开始朋友介�� 的祛斑产品，开始是挺好用的，没想到后来还会反弹，真是� ��瞎我的激情啦。后来我才知道，原来脸上的斑单纯的去掉外面的表皮是没有用的，要从内部解决，但是说真的，虽然说�� 要祛斑，但是我对长斑这一片的只是，还真是不怎么了解，� ��道的一些也是从网上看到的，但是知道了也没用，没有好的产品，脸上的斑是怎么也去不干净的，去掉也会在长。　　黛芙薇尔是我一个同事介绍给我的，说真话当时我也是�� 怎么相信，毕竟以前这方面的东西，我也不是没用过，但是� ��没有什么效果。但同事就说，他用的效果还是可以的，以前他的脸上也是有斑，但是现在她使用不过两个多月，就把脸�� 的黄褐斑淡化了，而且她皮肤还变白了不少，我看着效果确� ��听明显的，就跟她要了黛芙薇尔的官网地址，里面的介绍都很详细，我也大致知道了黛芙薇尔的远离，再说还是天然精华的，对�� 体没什么影响，试试就试试把，价格也不是太贵，于是就先� �� 。　　从一开始的抱着试试的心态订的一个周期到后来又订的�� 个周期，用到现在也算蛮久的了，我脸上的黄褐斑淡化的很� ��了，不认真看几乎就看不出来了，平时再画个妆，就根本就看不出来了，这个黛芙薇尔刚开始使用还不怎么信任，现在�� 用下来，没想到效果真的那么好，而且使用了这么久，皮肤� ��越来越好了，效果好就应该拿出来分享，还在为斑斑烦恼的友友们，别忘了找黛芙薇尔为你排忧解难啊阅读了怎么去除脸上的色斑，再看脸上容易长斑的原因：《色斑形成原因》　　内部因素　　一、压力　　当人受到压力时，就会分泌肾上腺素，为对付压力而做�� 备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃。　　二、荷尔蒙分泌失调　　避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� 分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕中因女性荷尔蒙雌激素的增加， — 现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� 谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所以需要更加注意。　　三、新陈代谢缓慢　　肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� 因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� 时候，紫外线的照射也会加速斑的形成。　　四、错误的使用化妆品　　使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� 疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的问题。　　外部因素　　一、紫外线　　照射紫外线的时候，人体为了保护皮肤，会在基底层产�� 很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，还会引起黑斑、雀斑等色素沉着的皮肤疾患。　　二、不良的清洁习惯　　因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� 皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的问题。　　三、遗传基因　　父母中有长斑的，则本人长斑的概率就很高，这种情况�� 一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外线照射，这是预防斑必须注意的。《有疑问帮你解决》　　黛芙薇尔精华液真的有效果吗真的可以把脸上的黄褐�� 去掉吗　　答：黛芙薇尔精华液dna精华能够有效的修复周围难以触�� 的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� ，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显而易见。自产品上市以来，老顾客纷纷介绍新顾客，的新�� 客都是通过老顾客介绍而来，口碑由此而来　　，服用黛芙薇尔美白，会伤身体吗有副作用吗　　答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� 斑科技，并将“dna美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� 地的专家通力协作， �� ，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然之美。专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� 百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖　　，去除黄褐斑之后，会反弹吗　　答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� 白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。树立权威品牌我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗　　，你们的价格有点贵，能不能便宜一点　　答：，，，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助一分价钱，一份价值，我们现在做的�� 是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗你还会再去花那么多冤枉�� ，不但斑没去掉，还把自己的皮肤弄的越来越糟吗　　，我适合用黛芙薇尔精华液吗　　答：黛芙薇尔适用人群：　　、生理紊乱引起的黄褐斑人群　　、生育引起的妊娠斑人群　　、年纪增长引起的老年斑人群　　、化妆品色素沉积、辐射斑人群　　、长期日照引起的日晒斑人群　　、肌肤暗淡急需美白的人群《祛斑小方法》怎么去除脸上的色斑，同时为您分享祛斑小方法、曲酸、熊果苷：抑制黑色素生成，使皮肤变得白净，美白� ��。、当归：入心脾经，补称作皮肤、毛发、五官的“建筑材料� ��，能使人容貌焕发，皮肤细嫩，富含维生素a、、e，还含� ��、，可调节人体的新陈代谢，止血止痛，消� ��安神。 original issue reported on code google com by additive gmail com on jul at

1

53,987

13,282,190,302

IssuesEvent

2020-08-23 21:24:27

Cockatrice/Cockatrice

https://api.github.com/repos/Cockatrice/Cockatrice

closed

tappedout.net deck analysis not working

Bug Defect - Basic

System Information: Client Version: 2.7.4 (2020-03-20) Client Operating System: Windows 10 (10.0) Build Architecture: 64-bit Qt Version: 5.12.6 System Locale: en_US Install Mode: Standard _______________________________________________________________________________________ Sending a deck to tappedout.net for analysis results in an invalid URL in the browser: `http://www.tappedout.nethttps//tappedout.net/mtg-decks/paste/` Tested with Firefox and Edge, and multiple decks. Relevant debug log entry: `Tappedout: good reply, http status 301 location "https://tappedout.net/mtg-decks/paste/"` Perhaps an issue with the redirection from http to https?

1.0

tappedout.net deck analysis not working - System Information: Client Version: 2.7.4 (2020-03-20) Client Operating System: Windows 10 (10.0) Build Architecture: 64-bit Qt Version: 5.12.6 System Locale: en_US Install Mode: Standard _______________________________________________________________________________________ Sending a deck to tappedout.net for analysis results in an invalid URL in the browser: `http://www.tappedout.nethttps//tappedout.net/mtg-decks/paste/` Tested with Firefox and Edge, and multiple decks. Relevant debug log entry: `Tappedout: good reply, http status 301 location "https://tappedout.net/mtg-decks/paste/"` Perhaps an issue with the redirection from http to https?

defect

tappedout net deck analysis not working system information client version client operating system windows build architecture bit qt version system locale en us install mode standard sending a deck to tappedout net for analysis results in an invalid url in the browser tested with firefox and edge and multiple decks relevant debug log entry tappedout good reply http status location perhaps an issue with the redirection from http to https

1

182,151

6,667,515,267

IssuesEvent

2017-10-03 12:53:48

spring-projects/spring-boot

https://api.github.com/repos/spring-projects/spring-boot

closed

Using multiple embedded databases requires a lot of manual configuration exclusions

priority: normal theme: datasource type: enhancement

If multiple embedded `DataSources` are declared, one needs to explicitly disable the `DataSourceAutoConfiguration` and `DataSourceTransactionManagerAutoConfiguration` as can be seen [here](https://github.com/spring-projects/spring-data-examples/blob/master/jpa/multiple-datasources/src/main/java/example/springdata/jpa/multipleds/Application.java#L41). They fail as they rely on unique `DataSource` instances to be present. Can we let the simply opt out of being applied if multiple `DataSource`s are present?

1.0

Using multiple embedded databases requires a lot of manual configuration exclusions -  If multiple embedded `DataSources` are declared, one needs to explicitly disable the `DataSourceAutoConfiguration` and `DataSourceTransactionManagerAutoConfiguration` as can be seen [here](https://github.com/spring-projects/spring-data-examples/blob/master/jpa/multiple-datasources/src/main/java/example/springdata/jpa/multipleds/Application.java#L41). They fail as they rely on unique `DataSource` instances to be present. Can we let the simply opt out of being applied if multiple `DataSource`s are present?

non_defect

using multiple embedded databases requires a lot of manual configuration exclusions thanks for raising a spring boot issue please provide a brief description of your problem along with the version of spring boot that you are using if possible please also consider putting together a sample application that reproduces the issue if multiple embedded datasources are declared one needs to explicitly disable the datasourceautoconfiguration and datasourcetransactionmanagerautoconfiguration as can be seen they fail as they rely on unique datasource instances to be present can we let the simply opt out of being applied if multiple datasource s are present

0

74,058

24,922,623,189

IssuesEvent

2022-10-31 02:44:42

matrix-org/matrix-public-archive

https://api.github.com/repos/matrix-org/matrix-public-archive

opened

Don't change the URL as you scroll around

T-Defect A-archive-room-view

Even if we had https://github.com/matrix-org/matrix-public-archive/issues/72 to page-load the room with a stable URL, it still probably doesn't make sense to change the URL around as you scroll. The content on the page should be consistent with the URL. > ## UX problems > > ### One person's link will not look like the other once they start scrolling > > Because we change the URL as you scroll around. Someone may link a page expecting all the same messages to be there but it will actually only be the current day they're scrolled to plus whatever is above it. It will probably also affect how search engines index the site attributing messages with a certain URL that when visiting will be missing. --- I think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you're currently viewing in the surrounding context.

1.0

Don't change the URL as you scroll around - Even if we had https://github.com/matrix-org/matrix-public-archive/issues/72 to page-load the room with a stable URL, it still probably doesn't make sense to change the URL around as you scroll. The content on the page should be consistent with the URL. > ## UX problems > > ### One person's link will not look like the other once they start scrolling > > Because we change the URL as you scroll around. Someone may link a page expecting all the same messages to be there but it will actually only be the current day they're scrolled to plus whatever is above it. It will probably also affect how search engines index the site attributing messages with a certain URL that when visiting will be missing. --- I think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you're currently viewing in the surrounding context.

defect

don t change the url as you scroll around even if we had to page load the room with a stable url it still probably doesn t make sense to change the url around as you scroll the content on the page should be consistent with the url ux problems one person s link will not look like the other once they start scrolling because we change the url as you scroll around someone may link a page expecting all the same messages to be there but it will actually only be the current day they re scrolled to plus whatever is above it it will probably also affect how search engines index the site attributing messages with a certain url that when visiting will be missing i think it does make sense to still change the calendar and text around to make it easy to jump to another day from where you re currently viewing in the surrounding context

1

44,439

12,157,618,061

IssuesEvent

2020-04-25 23:00:04

SarahAbigayle/SE310SE420FinalProjectNonGUI

https://api.github.com/repos/SarahAbigayle/SE310SE420FinalProjectNonGUI

closed

Remove “No journals. Create a journal?”

defect

File: MainActivity.java Line #: 31 This is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the GUI

1.0

Remove “No journals. Create a journal?” - File: MainActivity.java Line #: 31 This is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the GUI

defect

remove “no journals create a journal ” file mainactivity java line this is an unnecessary text prompt and should be removed because it doesn’t actually simulate the experience of the gui

1

3,146

2,607,985,572

IssuesEvent

2015-02-26 00:51:32

chrsmithdemos/zen-coding

https://api.github.com/repos/chrsmithdemos/zen-coding

closed

Direct shortcut for "wrap with abbreviation"

auto-migrated Priority-Medium Type-Defect

``` I use zen-coding with Eclipse. I really dislike the "wrap with abbreviation..." pop-up. 99% of the time I just want to wrap, requiring an additional keypress. There should be a separate shortcut for the pop-up, and one for directly wrapping the selected text block. ``` ----- Original issue reported on code.google.com by `poisonborz` on 20 Mar 2012 at 10:55

1.0

Direct shortcut for "wrap with abbreviation" - ``` I use zen-coding with Eclipse. I really dislike the "wrap with abbreviation..." pop-up. 99% of the time I just want to wrap, requiring an additional keypress. There should be a separate shortcut for the pop-up, and one for directly wrapping the selected text block. ``` ----- Original issue reported on code.google.com by `poisonborz` on 20 Mar 2012 at 10:55

defect

direct shortcut for wrap with abbreviation i use zen coding with eclipse i really dislike the wrap with abbreviation pop up of the time i just want to wrap requiring an additional keypress there should be a separate shortcut for the pop up and one for directly wrapping the selected text block original issue reported on code google com by poisonborz on mar at

1

4,238

2,610,089,902

IssuesEvent

2015-02-26 18:27:13

chrsmith/dsdsdaadf

https://api.github.com/repos/chrsmith/dsdsdaadf

opened

深圳痘痘在哪祛除

auto-migrated Priority-Medium Type-Defect

``` 深圳痘痘在哪祛除【深圳韩方科颜全国热线400-869-1818，24小时 QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:38

1.0

深圳痘痘在哪祛除 - ``` 深圳痘痘在哪祛除【深圳韩方科颜全国热线400-869-1818，24小时 QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:38

defect

深圳痘痘在哪祛除深圳痘痘在哪祛除【，】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘�� ——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方� ��颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业�� 疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘� ��。 original issue reported on code google com by szft com on may at

1

37,808

8,365,389,070

IssuesEvent

2018-10-04 04:49:09

SkygearIO/features

https://api.github.com/repos/SkygearIO/features

opened

Support activity logging in server side

require/code require/spec vote/1

# Description Currently if user want to do activity logging for analytics, they can do in the lambda or handlers. But there is not way to log the skygear server build in functions like login, signup... etc. We need a feature to combine the logs for custom actions and skygear server build in functions. #### Possible approaches 1. Have events to plugins for skygear server build in functions, e.g. login, signup, reset password events...etc 2. Skygear server support logging, and have logging functions in cloud SDK. ## Scenario **Put list of Scenario how developers will use this API** # Portal Design **Remove this section if the feature have no Portal** # API Design **Remove this section if the feature have no API** # Open Questions **Put a list of open questions here before a complete design / specification is decided** # Related Issues - Server Issues - Client Issues - Guides Issues

1.0

Support activity logging in server side - # Description Currently if user want to do activity logging for analytics, they can do in the lambda or handlers. But there is not way to log the skygear server build in functions like login, signup... etc. We need a feature to combine the logs for custom actions and skygear server build in functions. #### Possible approaches 1. Have events to plugins for skygear server build in functions, e.g. login, signup, reset password events...etc 2. Skygear server support logging, and have logging functions in cloud SDK. ## Scenario **Put list of Scenario how developers will use this API** # Portal Design **Remove this section if the feature have no Portal** # API Design **Remove this section if the feature have no API** # Open Questions **Put a list of open questions here before a complete design / specification is decided** # Related Issues - Server Issues - Client Issues - Guides Issues

non_defect

support activity logging in server side description currently if user want to do activity logging for analytics they can do in the lambda or handlers but there is not way to log the skygear server build in functions like login signup etc we need a feature to combine the logs for custom actions and skygear server build in functions possible approaches have events to plugins for skygear server build in functions e g login signup reset password events etc skygear server support logging and have logging functions in cloud sdk scenario put list of scenario how developers will use this api portal design remove this section if the feature have no portal api design remove this section if the feature have no api open questions put a list of open questions here before a complete design specification is decided related issues server issues client issues guides issues

0

718,985

24,740,406,875

IssuesEvent

2022-10-21 04:16:06

brave/brave-browser

https://api.github.com/repos/brave/brave-browser

opened

Support ENS wildcard resolution Android implementation of #24430

priority/P3 QA/Yes release-notes/include feature/wallet OS/Android

Android version of #24430 > To complete support of ENS L2 https://github.com/brave/brave-browser/issues/22930 we also need support of wildcard resolution for ENS https://docs.ens.domains/ens-improvement-proposals/ensip-10-wildcard-resolution Associated PR: https://github.com/brave/brave-core/pull/15317 cc: @jamesmudgett @supermassive @Pavneet-Sing @SergeyZhukovsky

1.0

Support ENS wildcard resolution Android implementation of #24430 - Android version of #24430 > To complete support of ENS L2 https://github.com/brave/brave-browser/issues/22930 we also need support of wildcard resolution for ENS https://docs.ens.domains/ens-improvement-proposals/ensip-10-wildcard-resolution Associated PR: https://github.com/brave/brave-core/pull/15317 cc: @jamesmudgett @supermassive @Pavneet-Sing @SergeyZhukovsky

non_defect

support ens wildcard resolution android implementation of android version of to complete support of ens we also need support of wildcard resolution for ens associated pr cc jamesmudgett supermassive pavneet sing sergeyzhukovsky

0

16,156

9,696,244,529

IssuesEvent

2019-05-25 05:28:50

manusa/isotope-mail

https://api.github.com/repos/manusa/isotope-mail

reopened

Security alert: tar v2.2.1 (node-sass)

security technical

Node-sass v4.9.3 depends on tar v2.2.0 which has a security vulnerability ``` +-- node-sass@4.9.3 `-- node-gyp@3.8.0 `-- tar@2.2.1 ``` > CVE-2018-20834 More information > high severity > Vulnerable versions: < 4.4.2 > Patched version: 4.4.2 > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. Blocked by [sass/node-sass#2625]

True

Security alert: tar v2.2.1 (node-sass) - Node-sass v4.9.3 depends on tar v2.2.0 which has a security vulnerability ``` +-- node-sass@4.9.3 `-- node-gyp@3.8.0 `-- tar@2.2.1 ``` > CVE-2018-20834 More information > high severity > Vulnerable versions: < 4.4.2 > Patched version: 4.4.2 > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. Blocked by [sass/node-sass#2625]

non_defect

security alert tar node sass node sass depends on tar which has a security vulnerability node sass node gyp tar cve more information high severity vulnerable versions patched version a vulnerability was found in node tar before version an arbitrary file overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system in conjunction with a later plain file with the same name as the hardlink this plain file content replaces the existing file content blocked by

0

131,153

12,476,459,560

IssuesEvent

2020-05-29 13:30:58

F5Networks/k8s-bigip-ctlr

https://api.github.com/repos/F5Networks/k8s-bigip-ctlr

closed

Self-signed BIG-IP certificate resulted in as3 agent internal error

Awaiting response documentation

#### Setup Details CIS Version : 2.0 Build: f5networks/k8s-bigip-ctlr:latest BIGIP Version: Big IP 15.1.0.3 AS3 Version: 3.19.1 Agent Mode: AS3 Orchestration: K8S Orchestration Version: 1.18.2 Pool Mode: Cluster Additional Setup details: bare metal / flannel #### Description BIG-IP has self signed certificate. Unable to get the controller pod up and running. #### Steps To Reproduce Just deploy CIS version 2.0 and see the controller pod fails. Ensure that BIG-IP device certificate is self-signed. #### Expected Result Controller pod up and running regardless of whether BIG-IP device certificate is self-signed or not. #### Actual Result Logs are as follows: [root@km143 ~]# kn logs k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 2020/05/29 08:20:48 [INFO] [INIT] Starting: Container Ingress Services - Version: 2.0.0, BuildInfo: cloud-user-efcab9e-20200522033624 2020/05/29 08:20:48 [INFO] ConfigWriter started: 0xc00031e570 2020/05/29 08:20:48 [INFO] Started config driver sub-process at pid: 17 2020/05/29 08:20:48 [INFO] [INIT] Creating Agent for as3 2020/05/29 08:20:48 [INFO] [AS3] Initializing AS3 Agent 2020/05/29 08:20:48 [ERROR] [AS3] REST call error: Get https://172.28.22.148/mgmt/shared/appsvcs/info: x509: certificate signed by unknown authority 2020/05/29 08:20:48 [ERROR] [AS3] Internal Error 2020/05/29 08:20:48 [CRITICAL] [INIT] Failed to initialize as3 agent, Internal Error [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 0/1 CrashLoopBackOff 1 8s <snip> In an act of desperation, I downgraded to CIS to version 1.14: [root@km143 ~]# kn logs k8s-bigip-ctlr-669559c7d7-ph2bh 2020/05/29 08:52:04 [INFO] Starting: Version: 1.14.0, BuildInfo: n2285-661543171 2020/05/29 08:52:04 [INFO] ConfigWriter started: 0xc0003401b0 2020/05/29 08:52:04 [INFO] Started config driver sub-process at pid: 13 2020/05/29 08:52:06 [INFO] [2020-05-29 08:52:06,181 __main__ INFO] entering inotify loop to watch /tmp/k8s-bigip-ctlr.config589230808/config.json 2020/05/29 08:52:07 [INFO] Wrote 0 Virtual Server and 0 IApp configs 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3400 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3470 2020/05/29 08:52:07 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:52:07 [INFO] ProcessNodeUpdate: Change in Node state detected 2020/05/29 08:52:07 [INFO] NodePoller started: (0xc0009bf680) 2020/05/29 08:52:07 [INFO] Watching Ingress resources. 2020/05/29 08:52:07 [INFO] Watching ConfigMap resources. 2020/05/29 08:52:07 [INFO] Handling ConfigMap resource events. 2020/05/29 08:52:07 [INFO] Handling Ingress resource events. 2020/05/29 08:52:07 [INFO] Registered BigIP Metrics 2020/05/29 08:52:10 [INFO] [2020-05-29 08:52:10,996 f5_cccl.resource.resource INFO] Updating ApiFDBTunnel: /Common/flannel_ingress 2020/05/29 08:52:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:57:08 [ERROR] [AS3] REST call error: Post [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-669559c7d7-ph2bh 1/1 Running 0 10m <snip> #### Diagnostic Information #### Observations (if any)

1.0

Self-signed BIG-IP certificate resulted in as3 agent internal error - #### Setup Details CIS Version : 2.0 Build: f5networks/k8s-bigip-ctlr:latest BIGIP Version: Big IP 15.1.0.3 AS3 Version: 3.19.1 Agent Mode: AS3 Orchestration: K8S Orchestration Version: 1.18.2 Pool Mode: Cluster Additional Setup details: bare metal / flannel #### Description BIG-IP has self signed certificate. Unable to get the controller pod up and running. #### Steps To Reproduce Just deploy CIS version 2.0 and see the controller pod fails. Ensure that BIG-IP device certificate is self-signed. #### Expected Result Controller pod up and running regardless of whether BIG-IP device certificate is self-signed or not. #### Actual Result Logs are as follows: [root@km143 ~]# kn logs k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 2020/05/29 08:20:48 [INFO] [INIT] Starting: Container Ingress Services - Version: 2.0.0, BuildInfo: cloud-user-efcab9e-20200522033624 2020/05/29 08:20:48 [INFO] ConfigWriter started: 0xc00031e570 2020/05/29 08:20:48 [INFO] Started config driver sub-process at pid: 17 2020/05/29 08:20:48 [INFO] [INIT] Creating Agent for as3 2020/05/29 08:20:48 [INFO] [AS3] Initializing AS3 Agent 2020/05/29 08:20:48 [ERROR] [AS3] REST call error: Get https://172.28.22.148/mgmt/shared/appsvcs/info: x509: certificate signed by unknown authority 2020/05/29 08:20:48 [ERROR] [AS3] Internal Error 2020/05/29 08:20:48 [CRITICAL] [INIT] Failed to initialize as3 agent, Internal Error [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-5cb6f6f7b9-8lqgd 0/1 CrashLoopBackOff 1 8s <snip> In an act of desperation, I downgraded to CIS to version 1.14: [root@km143 ~]# kn logs k8s-bigip-ctlr-669559c7d7-ph2bh 2020/05/29 08:52:04 [INFO] Starting: Version: 1.14.0, BuildInfo: n2285-661543171 2020/05/29 08:52:04 [INFO] ConfigWriter started: 0xc0003401b0 2020/05/29 08:52:04 [INFO] Started config driver sub-process at pid: 13 2020/05/29 08:52:06 [INFO] [2020-05-29 08:52:06,181 __main__ INFO] entering inotify loop to watch /tmp/k8s-bigip-ctlr.config589230808/config.json 2020/05/29 08:52:07 [INFO] Wrote 0 Virtual Server and 0 IApp configs 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3400 2020/05/29 08:52:07 [INFO] NodePoller (0xc0009bf680) registering new listener: 0x11c3470 2020/05/29 08:52:07 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:52:07 [INFO] ProcessNodeUpdate: Change in Node state detected 2020/05/29 08:52:07 [INFO] NodePoller started: (0xc0009bf680) 2020/05/29 08:52:07 [INFO] Watching Ingress resources. 2020/05/29 08:52:07 [INFO] Watching ConfigMap resources. 2020/05/29 08:52:07 [INFO] Handling ConfigMap resource events. 2020/05/29 08:52:07 [INFO] Handling Ingress resource events. 2020/05/29 08:52:07 [INFO] Registered BigIP Metrics 2020/05/29 08:52:10 [INFO] [2020-05-29 08:52:10,996 f5_cccl.resource.resource INFO] Updating ApiFDBTunnel: /Common/flannel_ingress 2020/05/29 08:52:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:53:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:54:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:55:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:08 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:56:38 [ERROR] [AS3] REST call error: Post https://172.28.22.148/mgmt/shared/appsvcs/declare/: x509: certificate signed by unknown authority 2020/05/29 08:57:08 [ERROR] [AS3] REST call error: Post [root@km143 ~]# kn get pods NAME READY STATUS RESTARTS AGE <snip> k8s-bigip-ctlr-669559c7d7-ph2bh 1/1 Running 0 10m <snip> #### Diagnostic Information #### Observations (if any)

non_defect

self signed big ip certificate resulted in agent internal error setup details cis version build bigip ctlr latest bigip version big ip version agent mode orchestration orchestration version pool mode cluster additional setup details bare metal flannel description big ip has self signed certificate unable to get the controller pod up and running steps to reproduce just deploy cis version and see the controller pod fails ensure that big ip device certificate is self signed expected result controller pod up and running regardless of whether big ip device certificate is self signed or not actual result logs are as follows kn logs bigip ctlr starting container ingress services version buildinfo cloud user configwriter started started config driver sub process at pid creating agent for initializing agent rest call error get certificate signed by unknown authority internal error failed to initialize agent internal error kn get pods name ready status restarts age bigip ctlr crashloopbackoff in an act of desperation i downgraded to cis to version kn logs bigip ctlr starting version buildinfo configwriter started started config driver sub process at pid entering inotify loop to watch tmp bigip ctlr config json wrote virtual server and iapp configs nodepoller registering new listener nodepoller registering new listener rest call error post certificate signed by unknown authority processnodeupdate change in node state detected nodepoller started watching ingress resources watching configmap resources handling configmap resource events handling ingress resource events registered bigip metrics updating apifdbtunnel common flannel ingress rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post certificate signed by unknown authority rest call error post kn get pods name ready status restarts age bigip ctlr running diagnostic information observations if any

0

53,253

13,261,260,070

IssuesEvent

2020-08-20 19:34:07

icecube-trac/tix4

https://api.github.com/repos/icecube-trac/tix4

closed

[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk (Trac #1049)

Migrated from Trac cmake defect

Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary <details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1049">https://code.icecube.wisc.edu/projects/icecube/ticket/1049</a>, reported by mamdayand owned by nega</summary> ```json { "status": "closed", "changetime": "2019-01-11T23:56:01", "_ts": "1547250961636294", "description": "Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary", "reporter": "mamday", "cc": "david.schultz", "resolution": "fixed", "time": "2015-07-14T18:46:13", "component": "cmake", "summary": "[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk", "priority": "normal", "keywords": "tarball cmake simprod-scripts", "milestone": "", "owner": "nega", "type": "defect" } ``` </details>

1.0

[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk (Trac #1049) - Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary <details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1049">https://code.icecube.wisc.edu/projects/icecube/ticket/1049</a>, reported by mamdayand owned by nega</summary> ```json { "status": "closed", "changetime": "2019-01-11T23:56:01", "_ts": "1547250961636294", "description": "Tested this a couple times with trunk of simulation. Running make install_tool_libs will install it, but shouldn't be necessary", "reporter": "mamday", "cc": "david.schultz", "resolution": "fixed", "time": "2015-07-14T18:46:13", "component": "cmake", "summary": "[cmake / simprod-scripts] Running make production-tarball; make tarball doesn't make libgsl.so in simulation trunk", "priority": "normal", "keywords": "tarball cmake simprod-scripts", "milestone": "", "owner": "nega", "type": "defect" } ``` </details>

defect

running make production tarball make tarball doesn t make libgsl so in simulation trunk trac tested this a couple times with trunk of simulation running make install tool libs will install it but shouldn t be necessary migrated from json status closed changetime ts description tested this a couple times with trunk of simulation running make install tool libs will install it but shouldn t be necessary reporter mamday cc david schultz resolution fixed time component cmake summary running make production tarball make tarball doesn t make libgsl so in simulation trunk priority normal keywords tarball cmake simprod scripts milestone owner nega type defect

1

6,454

6,422,667,041

IssuesEvent

2017-08-09 09:03:22

openshiftio/appdev-documentation

https://api.github.com/repos/openshiftio/appdev-documentation

opened

cico_build_deploy.sh is undocumented

Bug Infrastructure

There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.

1.0

cico_build_deploy.sh is undocumented - There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.

non_defect

cico build deploy sh is undocumented there is currently no documentation of the cico build deploy sh script which can be used for running the server locally

0

79,290

28,086,294,891

IssuesEvent

2023-03-30 09:59:39

vector-im/element-android

https://api.github.com/repos/vector-im/element-android

closed

Maunium sticker picker loads indefinitely on new update

T-Defect A-Stickers S-Minor O-Occasional

### Steps to reproduce 1. Where are you starting? What can you see? Chat view 2. What do you click? Sticker button 3. More steps… N/A ### Outcome #### What did you expect? Sticker picker view loads and i can pick a sticker to send #### What happened instead? Indefinite loading of the sticker picker view. Works fine after downgrading to 1.5.11. Also, unrelated but I don't want to make another PR for this and it's technically not a bug: can you revert the image viewer to the pre-1.5.18 behaviour? What I mean is that when I open an image if I slide down on the image a little I used to be able to see the chat window and messages behind it but now it's blank and this means that whenever I view a video or photo file if I'm scrolled up in the chat after exiting the photo/video I'll immediately be jumped to the bottom and lose my position in the chat ### Your phone model Pixel 5a ### Operating system version Android 13.0 ### Application version and app store Element version 1.5.20, F-Droid ### Homeserver Synapse 1.75.0 ### Will you send logs? No ### Are you willing to provide a PR? No

1.0

Maunium sticker picker loads indefinitely on new update - ### Steps to reproduce 1. Where are you starting? What can you see? Chat view 2. What do you click? Sticker button 3. More steps… N/A ### Outcome #### What did you expect? Sticker picker view loads and i can pick a sticker to send #### What happened instead? Indefinite loading of the sticker picker view. Works fine after downgrading to 1.5.11. Also, unrelated but I don't want to make another PR for this and it's technically not a bug: can you revert the image viewer to the pre-1.5.18 behaviour? What I mean is that when I open an image if I slide down on the image a little I used to be able to see the chat window and messages behind it but now it's blank and this means that whenever I view a video or photo file if I'm scrolled up in the chat after exiting the photo/video I'll immediately be jumped to the bottom and lose my position in the chat ### Your phone model Pixel 5a ### Operating system version Android 13.0 ### Application version and app store Element version 1.5.20, F-Droid ### Homeserver Synapse 1.75.0 ### Will you send logs? No ### Are you willing to provide a PR? No

defect

maunium sticker picker loads indefinitely on new update steps to reproduce where are you starting what can you see chat view what do you click sticker button more steps… n a outcome what did you expect sticker picker view loads and i can pick a sticker to send what happened instead indefinite loading of the sticker picker view works fine after downgrading to also unrelated but i don t want to make another pr for this and it s technically not a bug can you revert the image viewer to the pre behaviour what i mean is that when i open an image if i slide down on the image a little i used to be able to see the chat window and messages behind it but now it s blank and this means that whenever i view a video or photo file if i m scrolled up in the chat after exiting the photo video i ll immediately be jumped to the bottom and lose my position in the chat your phone model pixel operating system version android application version and app store element version f droid homeserver synapse will you send logs no are you willing to provide a pr no

1

622,907

19,658,613,618

IssuesEvent

2022-01-10 14:57:11

threefoldtech/tfchain

https://api.github.com/repos/threefoldtech/tfchain

closed

Move pallets from tfchain_pallets to this repo

priority_major type_feature

Currently issue and releasemgmt is a mess. While almost all functionality resides in tfchain_pallets, they are combined and released in tfchain resulting in git commit history with "chore: bump dependencies and spec version".

1.0

Move pallets from tfchain_pallets to this repo - Currently issue and releasemgmt is a mess. While almost all functionality resides in tfchain_pallets, they are combined and released in tfchain resulting in git commit history with "chore: bump dependencies and spec version".

non_defect

move pallets from tfchain pallets to this repo currently issue and releasemgmt is a mess while almost all functionality resides in tfchain pallets they are combined and released in tfchain resulting in git commit history with chore bump dependencies and spec version

0

52,890

13,225,206,072

IssuesEvent

2020-08-17 20:42:16

icecube-trac/tix4

https://api.github.com/repos/icecube-trac/tix4

closed

make tarball copying error in install_shlib.pl (Trac #535)

Migrated from Trac cmake defect

When running 'make tarball' errors like this one appear: "Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74" The reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute. <details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/535">https://code.icecube.wisc.edu/projects/icecube/ticket/535</a>, reported by henjoh@physto.seand owned by troy</summary> ```json { "status": "closed", "changetime": "2009-07-23T13:45:14", "_ts": "1248356714000000", "description": "When running 'make tarball' errors like this one appear:\n\"Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74\"\n\nThe reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute.\n", "reporter": "henjoh@physto.se", "cc": "", "resolution": "duplicate", "time": "2009-02-16T20:06:18", "component": "cmake", "summary": "make tarball copying error in install_shlib.pl", "priority": "normal", "keywords": "install_shlib.pl", "milestone": "", "owner": "troy", "type": "defect" } ``` </details>

1.0

make tarball copying error in install_shlib.pl (Trac #535) - When running 'make tarball' errors like this one appear: "Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74" The reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute. <details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/535">https://code.icecube.wisc.edu/projects/icecube/ticket/535</a>, reported by henjoh@physto.seand owned by troy</summary> ```json { "status": "closed", "changetime": "2009-07-23T13:45:14", "_ts": "1248356714000000", "description": "When running 'make tarball' errors like this one appear:\n\"Couldn't copy /lap/i3_ports/1.0/root-v5.18.00/lib//lap/i3_ports/1.0/var/db/dports/software/root_5.18.00/5.18.00_3/lap/i3_ports/1.0/root-v5.18.00/lib/libCore.so.5.18 to simulation.candidates.V02-03-01RC.Linux-x86_64.gcc-4.2.4/lib/tools: No such file or directory at /scratch/597612344576472117827348/scratch/meta-project/src/cmake/install_shlib.pl line 74\"\n\nThe reason seems to be that if the $src variable in install_shlib.pl is a symbolic link, it is assumed to be a relative link, while it might be absolute.\n", "reporter": "henjoh@physto.se", "cc": "", "resolution": "duplicate", "time": "2009-02-16T20:06:18", "component": "cmake", "summary": "make tarball copying error in install_shlib.pl", "priority": "normal", "keywords": "install_shlib.pl", "milestone": "", "owner": "troy", "type": "defect" } ``` </details>

defect

make tarball copying error in install shlib pl trac when running make tarball errors like this one appear couldn t copy lap ports root lib lap ports var db dports software root lap ports root lib libcore so to simulation candidates linux gcc lib tools no such file or directory at scratch scratch meta project src cmake install shlib pl line the reason seems to be that if the src variable in install shlib pl is a symbolic link it is assumed to be a relative link while it might be absolute migrated from json status closed changetime ts description when running make tarball errors like this one appear n couldn t copy lap ports root lib lap ports var db dports software root lap ports root lib libcore so to simulation candidates linux gcc lib tools no such file or directory at scratch scratch meta project src cmake install shlib pl line n nthe reason seems to be that if the src variable in install shlib pl is a symbolic link it is assumed to be a relative link while it might be absolute n reporter henjoh physto se cc resolution duplicate time component cmake summary make tarball copying error in install shlib pl priority normal keywords install shlib pl milestone owner troy type defect

1

74,810

25,339,080,007

IssuesEvent

2022-11-18 19:38:39

openzfs/zfs

https://api.github.com/repos/openzfs/zfs

closed

per dataset large_block feature detection not reliable when sending raw encrypted large block ds

Type: Defect Component: Send/Recv Component: Encryption

Tests for https://github.com/openzfs/zfs/pull/9372 have revealed what seems to be a bug (race ?) with the `large_blocks` zpool feature. If we have a raw send of an encrypted dataset with large blocks present the send often fails with `warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported` message even though the dataset in question has large block and has the feature active. This behavior is not consistent and re-running the same test sometimes does pass and sometimes does not. ### System information This is seen on the tip of master ### Describe the problem you're observing Sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn't. A failure looks like: ``` 20:49:46.93 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:47.28 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:47.31 warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported 20:49:47.31 ERROR: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup exited 1 ``` When the same test succeeds it looks like: ``` 20:49:57.12 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:57.48 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:57.51 SUCCESS: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup ``` I spend a little time debugging this and noticed that https://github.com/openzfs/zfs/blob/master/module/zfs/dmu_send.c#L1019-L1020 doesn't always have `dsc_featureflags` set correctly. If you run with this patch ``` diff --git a/module/zfs/dmu_send.c b/module/zfs/dmu_send.c index 5e6ced2bb..b70002361 100644 --- a/module/zfs/dmu_send.c +++ b/module/zfs/dmu_send.c @@ -1965,8 +1965,9 @@ setup_featureflags(struct dmu_send_params *dspp, objset_t *os, #endif /* raw sends imply large_block_ok */ - if ((dspp->rawok || dspp->large_block_ok) && - dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) { + if (dspp->rawok || dspp->large_block_ok) { + zfs_dbgmsg("%d",(dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS))); + if (dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) *featureflags |= DMU_BACKUP_FEATURE_LARGE_BLOCKS; } ``` You can see that `dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)` is not reliable and will sometime return 0 and other times return 1. I also noticed that the dataset object passed to `load_zfeature()` seems to be different for passing vs not passing tests. ### Describe how to reproduce the problem Here is the minimal zfs-test I used to recreate the problem: ``` #!/bin/ksh -p . $STF_SUITE/include/libtest.shlib verify_runnable "both" DISK=${DISKS%% *} backup=$TEST_BASE_DIR/backup raw_backup=$TEST_BASE_DIR/raw_backup function cleanup { log_must rm -f $backup $raw_backup $ibackup $unc_backup log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f $TESTPOOL $DISK } log_onexit cleanup typeset passphrase="password" typeset file="/$TESTPOOL/$TESTFS1/$TESTFILE0" log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f -o feature@head_errlog=disabled \ -o feature@large_blocks=enabled $TESTPOOL $DISK log_must eval "echo $passphrase > /$TESTPOOL/pwd" log_must zfs create -o recordsize=1m -o primarycache=none \ -o atime=off -o compression=lz4 $TESTPOOL/$TESTFS1 log_must dd if=/dev/urandom of=$file bs=1024 count=1024 oflag=sync log_must zfs snapshot $TESTPOOL/$TESTFS1@snap1 log_must eval "zfs send -L $TESTPOOL/$TESTFS1@snap1 > $backup" log_must eval "zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase \ -o keylocation=file:///$TESTPOOL/pwd -o primarycache=none \ -o recordsize=1m $TESTPOOL/testfs5 < $backup" log_must eval "zfs send --raw $TESTPOOL/testfs5@snap1 > $raw_backup" ```

1.0

per dataset large_block feature detection not reliable when sending raw encrypted large block ds - Tests for https://github.com/openzfs/zfs/pull/9372 have revealed what seems to be a bug (race ?) with the `large_blocks` zpool feature. If we have a raw send of an encrypted dataset with large blocks present the send often fails with `warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported` message even though the dataset in question has large block and has the feature active. This behavior is not consistent and re-running the same test sometimes does pass and sometimes does not. ### System information This is seen on the tip of master ### Describe the problem you're observing Sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn't. A failure looks like: ``` 20:49:46.93 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:47.28 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:47.31 warning: cannot send 'testpool/testfs5@snap1': large blocks detected but large_blocks feature is inactive; raw send unsupported 20:49:47.31 ERROR: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup exited 1 ``` When the same test succeeds it looks like: ``` 20:49:57.12 SUCCESS: eval zfs send -L testpool/testfs1@snap1 > /var/tmp/backup 20:49:57.48 SUCCESS: eval zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase -o keylocation=file:///testpool/pwd -o primarycache=none -o recordsize=1m testpool/testfs5 < /var/tmp/backup 20:49:57.51 SUCCESS: eval zfs send --raw testpool/testfs5@snap1 > /var/tmp/raw_backup ``` I spend a little time debugging this and noticed that https://github.com/openzfs/zfs/blob/master/module/zfs/dmu_send.c#L1019-L1020 doesn't always have `dsc_featureflags` set correctly. If you run with this patch ``` diff --git a/module/zfs/dmu_send.c b/module/zfs/dmu_send.c index 5e6ced2bb..b70002361 100644 --- a/module/zfs/dmu_send.c +++ b/module/zfs/dmu_send.c @@ -1965,8 +1965,9 @@ setup_featureflags(struct dmu_send_params *dspp, objset_t *os, #endif /* raw sends imply large_block_ok */ - if ((dspp->rawok || dspp->large_block_ok) && - dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) { + if (dspp->rawok || dspp->large_block_ok) { + zfs_dbgmsg("%d",(dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS))); + if (dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)) *featureflags |= DMU_BACKUP_FEATURE_LARGE_BLOCKS; } ``` You can see that `dsl_dataset_feature_is_active(to_ds, SPA_FEATURE_LARGE_BLOCKS)` is not reliable and will sometime return 0 and other times return 1. I also noticed that the dataset object passed to `load_zfeature()` seems to be different for passing vs not passing tests. ### Describe how to reproduce the problem Here is the minimal zfs-test I used to recreate the problem: ``` #!/bin/ksh -p . $STF_SUITE/include/libtest.shlib verify_runnable "both" DISK=${DISKS%% *} backup=$TEST_BASE_DIR/backup raw_backup=$TEST_BASE_DIR/raw_backup function cleanup { log_must rm -f $backup $raw_backup $ibackup $unc_backup log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f $TESTPOOL $DISK } log_onexit cleanup typeset passphrase="password" typeset file="/$TESTPOOL/$TESTFS1/$TESTFILE0" log_must eval "poolexists $TESTPOOL && destroy_pool $TESTPOOL" log_must zpool create -f -o feature@head_errlog=disabled \ -o feature@large_blocks=enabled $TESTPOOL $DISK log_must eval "echo $passphrase > /$TESTPOOL/pwd" log_must zfs create -o recordsize=1m -o primarycache=none \ -o atime=off -o compression=lz4 $TESTPOOL/$TESTFS1 log_must dd if=/dev/urandom of=$file bs=1024 count=1024 oflag=sync log_must zfs snapshot $TESTPOOL/$TESTFS1@snap1 log_must eval "zfs send -L $TESTPOOL/$TESTFS1@snap1 > $backup" log_must eval "zfs recv -o encryption=aes-256-ccm -o keyformat=passphrase \ -o keylocation=file:///$TESTPOOL/pwd -o primarycache=none \ -o recordsize=1m $TESTPOOL/testfs5 < $backup" log_must eval "zfs send --raw $TESTPOOL/testfs5@snap1 > $raw_backup" ```

defect

per dataset large block feature detection not reliable when sending raw encrypted large block ds tests for have revealed what seems to be a bug race with the large blocks zpool feature if we have a raw send of an encrypted dataset with large blocks present the send often fails with warning cannot send testpool large blocks detected but large blocks feature is inactive raw send unsupported message even though the dataset in question has large block and has the feature active this behavior is not consistent and re running the same test sometimes does pass and sometimes does not system information this is seen on the tip of master describe the problem you re observing sometimes the code fails to detect that the dataset has support for large blocks and sometimes it doesn t a failure looks like success eval zfs send l testpool var tmp backup success eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool var tmp backup warning cannot send testpool large blocks detected but large blocks feature is inactive raw send unsupported error eval zfs send raw testpool var tmp raw backup exited when the same test succeeds it looks like success eval zfs send l testpool var tmp backup success eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool var tmp backup success eval zfs send raw testpool var tmp raw backup i spend a little time debugging this and noticed that doesn t always have dsc featureflags set correctly if you run with this patch diff git a module zfs dmu send c b module zfs dmu send c index a module zfs dmu send c b module zfs dmu send c setup featureflags struct dmu send params dspp objset t os endif raw sends imply large block ok if dspp rawok dspp large block ok dsl dataset feature is active to ds spa feature large blocks if dspp rawok dspp large block ok zfs dbgmsg d dsl dataset feature is active to ds spa feature large blocks if dsl dataset feature is active to ds spa feature large blocks featureflags dmu backup feature large blocks you can see that dsl dataset feature is active to ds spa feature large blocks is not reliable and will sometime return and other times return i also noticed that the dataset object passed to load zfeature seems to be different for passing vs not passing tests describe how to reproduce the problem here is the minimal zfs test i used to recreate the problem bin ksh p stf suite include libtest shlib verify runnable both disk disks backup test base dir backup raw backup test base dir raw backup function cleanup log must rm f backup raw backup ibackup unc backup log must eval poolexists testpool destroy pool testpool log must zpool create f testpool disk log onexit cleanup typeset passphrase password typeset file testpool log must eval poolexists testpool destroy pool testpool log must zpool create f o feature head errlog disabled o feature large blocks enabled testpool disk log must eval echo passphrase testpool pwd log must zfs create o recordsize o primarycache none o atime off o compression testpool log must dd if dev urandom of file bs count oflag sync log must zfs snapshot testpool log must eval zfs send l testpool backup log must eval zfs recv o encryption aes ccm o keyformat passphrase o keylocation file testpool pwd o primarycache none o recordsize testpool backup log must eval zfs send raw testpool raw backup

1

30,259

8,507,451,633

IssuesEvent

2018-10-30 19:06:32

hashicorp/packer

https://api.github.com/repos/hashicorp/packer

closed

Remote ESXi builder failing on retrieving VM ip. ESXi 6.0, packer 1.0

builder/vmware-esxi question waiting-reply

I'm using a ESXi 6.0 host for testing packer and I've been trying to get the vmware-iso remote ESXi builder to work. With packer 1.0. I get to the point where packer tries to retrieve the guest IP with "esxcli --formatter csv network vm port list -w #######" but errors out saying it cannot find the ip. Packer log: ``` 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Using internal plugin for vmware-vmx 2017/06/15 08:41:00 Using internal plugin for hyperv-iso 2017/06/15 08:41:00 Using internal plugin for virtualbox-iso 2017/06/15 08:41:00 Using internal plugin for amazon-instance 2017/06/15 08:41:00 Using internal plugin for digitalocean 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for oneandone 2017/06/15 08:41:00 Using internal plugin for openstack 2017/06/15 08:41:00 Using internal plugin for parallels-iso 2017/06/15 08:41:00 Using internal plugin for amazon-ebs 2017/06/15 08:41:00 Using internal plugin for amazon-ebsvolume 2017/06/15 08:41:00 Using internal plugin for null 2017/06/15 08:41:00 Using internal plugin for profitbricks 2017/06/15 08:41:00 Using internal plugin for cloudstack 2017/06/15 08:41:00 Using internal plugin for googlecompute 2017/06/15 08:41:00 Using internal plugin for azure-arm 2017/06/15 08:41:00 Using internal plugin for docker 2017/06/15 08:41:00 Using internal plugin for parallels-pvm 2017/06/15 08:41:00 Using internal plugin for qemu 2017/06/15 08:41:00 Using internal plugin for triton 2017/06/15 08:41:00 Using internal plugin for virtualbox-ovf 2017/06/15 08:41:00 Using internal plugin for amazon-chroot 2017/06/15 08:41:00 Using internal plugin for amazon-ebssurrogate 2017/06/15 08:41:00 Using internal plugin for vmware-iso 2017/06/15 08:41:00 Using internal plugin for converge 2017/06/15 08:41:00 Using internal plugin for salt-masterless 2017/06/15 08:41:00 Using internal plugin for chef-client 2017/06/15 08:41:00 Using internal plugin for chef-solo 2017/06/15 08:41:00 Using internal plugin for shell 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for ansible-local 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for puppet-masterless 2017/06/15 08:41:00 Using internal plugin for puppet-server 2017/06/15 08:41:00 Using internal plugin for ansible 2017/06/15 08:41:00 Using internal plugin for powershell 2017/06/15 08:41:00 Using internal plugin for windows-restart 2017/06/15 08:41:00 Using internal plugin for windows-shell 2017/06/15 08:41:00 Using internal plugin for checksum 2017/06/15 08:41:00 Using internal plugin for docker-save 2017/06/15 08:41:00 Using internal plugin for docker-tag 2017/06/15 08:41:00 Using internal plugin for atlas 2017/06/15 08:41:00 Using internal plugin for manifest 2017/06/15 08:41:00 Using internal plugin for compress 2017/06/15 08:41:00 Using internal plugin for googlecompute-export 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for vagrant-cloud 2017/06/15 08:41:00 Using internal plugin for vsphere 2017/06/15 08:41:00 Using internal plugin for docker-import 2017/06/15 08:41:00 Using internal plugin for artifice 2017/06/15 08:41:00 Using internal plugin for docker-push 2017/06/15 08:41:00 Using internal plugin for vagrant 2017/06/15 08:41:00 Using internal plugin for amazon-import 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[null:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null googlecompute:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute qemu:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu virtualbox-ovf:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf amazon-chroot:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot vmware-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso amazon-ebsvolume:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume digitalocean:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file oneandone:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone parallels-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso amazon-ebs:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs cloudstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack parallels-pvm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm vmware-vmx:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx virtualbox-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-instance:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance azure-arm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm triton:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton amazon-ebssurrogate:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate hyperv-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso profitbricks:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks docker:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker openstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack] PostProcessors:map[docker-save:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save docker-tag:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag atlas:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-atlas manifest:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local vagrant-cloud:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud checksum:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum artifice:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice vagrant:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant amazon-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import compress:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress vsphere:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere docker-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import docker-push:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push googlecompute-export:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export] Provisioners:map[ansible:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible powershell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell converge:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local puppet-server:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server chef-solo:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file windows-restart:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart puppet-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless salt-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-client:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client ansible-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local]} 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 Loading builder: vmware-iso 2017/06/15 08:41:00 Plugin could not be found. Checking same directory as executable. 2017/06/15 08:41:00 Current exe path: /usr/local/bin/packer 2017/06/15 08:41:00 Creating plugin client for path: /usr/local/bin/packer 2017/06/15 08:41:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-builder-vmware-iso"} 2017/06/15 08:41:00 Waiting for RPC address for: /usr/local/bin/packer 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 args: []string{"packer-builder-vmware-iso"} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin minimum port: 10000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin maximum port: 25000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin address: unix /tmp/packer-plugin255655097 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Waiting for connection... 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Serving a plugin connection... 2017/06/15 08:41:00 ui: [1;32mvmware-iso output will be in this color.[0m 2017/06/15 08:41:00 ui: 2017/06/15 08:41:00 Build debug mode: false 2017/06/15 08:41:00 Force build: false 2017/06/15 08:41:00 On error: 2017/06/15 08:41:00 Preparing build: vmware-iso 2017/06/15 08:41:00 Waiting on builds to complete... 2017/06/15 08:41:00 Starting build run: vmware-iso 2017/06/15 08:41:00 Running builder: vmware-iso 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 reconnecting to TCP connection for SSH 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 handshaking with SSH 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Question 1: Password: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 handshake complete! 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 [INFO] no local agent socket, will not connect agent 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system version get 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Connected to VMware ESXi 6.0.0 Releasebuild-3620759 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system settings advanced list -o /Net/GuestIPHack 2017/06/15 08:41:02 ui: [1;32m==> vmware-iso: Downloading or copying ISO[0m 2017/06/15 08:41:02 ui: [0;32m vmware-iso: Downloading or copying: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso[0m 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Acquiring lock to download: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Verifying checksum of /home/git/chief-masterhost/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 [DEBUG] Initial checksum matched, no download needed. 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: test -e /vmfs/volumes/***/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote command exited with '1': test -e /vmfs/volumes/***/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/***GB/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 No floppy files specified. Floppy disk will not be made. 2017/06/15 08:41:14 ui: [1;32m==> vmware-iso: Uploading ISO to remote machine...[0m 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote uploading: /home/git/***/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/***GB/packer_cache 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Verifying checksum of /vmfs/volumes/***GB/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: sha256sum -c 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 Initial checksum matched, no upload needed. 2017/06/15 08:41:50 ui: [1;32m==> vmware-iso: Creating virtual machine disk[0m 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 opening new ssh session 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 starting remote command: vmkfstools -c 7000M -d zeroedthick -a lsilogic /vmfs/volumes/***GB/ubuntu/output-vmware-iso/disk.vmdk 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Building and writing VMX file[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'memsize' = '512' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'cpuid.coresPerSocket' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.present' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.startConnected' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.virtualDev' = 'e1000' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'RemoteDisplay.vnc.webSocket.port' = '5900' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.networkName' = '***' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'numvcpus' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Suppressing messages in VMX 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying port: 8446 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Starting HTTP server on port 8446[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Looking for available port between 5900 and 6000 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 starting remote command: esxcli --formatter csv network ip connection list 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5989, port 5989 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:8889, port 8889 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address fe80:2::207:e9ff:fe5a:7c5f:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ***:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8000, port 8000 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8100, port 8100 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8300, port 8300 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:2233, port 2233 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5900 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5901 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying address: ***... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Found available VNC port: 5902 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Registering remote VM...[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Starting remote scp process: scp -vt /vmfs/volumes/***GB/ubuntu/output-vmware-iso 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Started SCP session, beginning transfers... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Copying input data into temporary file so we can read the length 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 [DEBUG] scp: Uploading ubuntu.vmx: perms=C0644 size=2501 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 SCP session complete, closing stdin pipe. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 Waiting for SSH session to complete. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 scp stderr (length 28): Sink: C0644 2501 ubuntu.vmx 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd solo/registervm /vmfs/volumes/***GB/ubuntu/output-vmware-iso/ubuntu.vmx 2017/06/15 08:41:52 ui: [1;32m==> vmware-iso: Starting virtual machine...[0m 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd vmsvc/power.on 77 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 opening new ssh session 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 starting remote command: vim-cmd vmsvc/power.getstate 77 2017/06/15 08:41:54 ui: [1;32m==> vmware-iso: Waiting 10s for boot...[0m 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Connecting to VM via VNC[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Connected to VNC desktop: ubuntu 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Host IP for the VMware machine: *** 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Typing the boot command over VNC...[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:05 packer: 2017/06/15 08:42:05 Special code '<f6>' found, replacing with: 65475 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<esc>' found, replacing with: 65307 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:22 packer: 2017/06/15 08:42:22 Sending char '/', code 47, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'i', code 105, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'n', code 110, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 's', code 115, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 't', code 116, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'a', code 97, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char '/', code 47, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'v', code 118, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'm', code 109, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'l', code 108, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'i', code 105, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'n', code 110, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'u', code 117, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'z', code 122, shift false 2017/06/15 08:42:26 packer: 2017/06/15 08:42:26 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char ' ', code 32, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'a', code 97, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'u', code 117, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 't', code 116, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'o', code 111, shift false 2017/06/15 08:42:28 packer: 2017/06/15 08:42:28 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char ' ', code 32, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'c', code 99, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'o', code 111, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'n', code 110, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 's', code 115, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'o', code 111, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'l', code 108, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'e', code 101, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char '-', code 45, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 's', code 115, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'e', code 101, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 't', code 116, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'u', code 117, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'p', code 112, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char '/', code 47, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'a', code 97, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 's', code 115, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'k', code 107, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char '_', code 95, shift true 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'd', code 100, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 't', code 116, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'c', code 99, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 't', code 116, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char '=', code 61, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'f', code 102, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'a', code 97, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'l', code 108, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 's', code 115, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 'e', code 101, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char ' ', code 32, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'c', code 99, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'n', code 110, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 's', code 115, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'l', code 108, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char '-', code 45, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 's', code 115, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 't', code 116, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'u', code 117, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'p', code 112, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char '/', code 47, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'l', code 108, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'a', code 97, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'y', code 121, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'u', code 117, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 't', code 116, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'c', code 99, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'd', code 100, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'e', code 101, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char '=', code 61, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'u', code 117, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 's', code 115, shift false 2017/06/15 08:42:42 packer: 2017/06/15 08:42:42 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char ' ', code 32, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'c', code 99, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'o', code 111, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'n', code 110, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 's', code 115, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'o', code 111, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'l', code 108, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'e', code 101, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char '-', code 45, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 's', code 115, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'e', code 101, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 't', code 116, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'u', code 117, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'p', code 112, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char '/', code 47, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'm', code 109, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'o', code 111, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'd', code 100, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'e', code 101, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'l', code 108, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'c', code 99, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'o', code 111, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'd', code 100, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'e', code 101, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char '=', code 61, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'p', code 112, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'c', code 99, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '1', code 49, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '0', code 48, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '5', code 53, shift false 2017/06/15 08:42:49 packer: 2017/06/15 08:42:49 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char ' ', code 32, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'd', code 100, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'e', code 101, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'b', code 98, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'c', code 99, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'o', code 111, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'n', code 110, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char '/', code 47, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'r', code 114, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'o', code 111, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'n', code 110, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 't', code 116, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'e', code 101, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'd', code 100, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char '=', code 61, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'o', code 111, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'i', code 105, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 't', code 116, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'e', code 101, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'r', code 114, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'a', code 97, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'c', code 99, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 't', code 116, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'i', code 105, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'v', code 118, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'e', code 101, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char ' ', code 32, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'd', code 100, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'e', code 101, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'b', code 98, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'i', code 105, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'a', code 97, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'n', code 110, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char '-', code 45, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'i', code 105, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'n', code 110, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 's', code 115, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 't', code 116, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'a', code 97, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'e', code 101, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'r', code 114, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char '=', code 61, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'e', code 101, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'n', code 110, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char '_', code 95, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'U', code 85, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'S', code 83, shift true 2017/06/15 08:43:02 packer: 2017/06/15 08:43:02 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char ' ', code 32, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'b', code 98, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char '=', code 61, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'a', code 97, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'l', code 108, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 's', code 115, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'e', code 101, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:05 packer: 2017/06/15 08:43:05 Sending char ' ', code 32, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'n', code 110, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 't', code 116, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'r', code 114, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'd', code 100, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '=', code 61, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '/', code 47, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'i', code 105, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'n', code 110, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 's', code 115, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 't', code 116, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'a', code 97, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char '/', code 47, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'n', code 110, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 't', code 116, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'r', code 114, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'd', code 100, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char '.', code 46, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'g', code 103, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'z', code 122, shift false 2017/06/15 08:43:11 packer: 2017/06/15 08:43:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char ' ', code 32, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'k', code 107, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'b', code 98, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'd', code 100, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char '-', code 45, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'c', code 99, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'h', code 104, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 's', code 115, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'r', code 114, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char '/', code 47, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'm', code 109, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 't', code 116, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'h', code 104, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'o', code 111, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'd', code 100, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char '=', code 61, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 'u', code 117, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 's', code 115, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char ' ', code 32, shift false 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char 'k', code 107, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'e', code 101, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'y', code 121, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'b', code 98, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'o', code 111, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'a', code 97, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'r', code 114, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'd', code 100, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char '-', code 45, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'c', code 99, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'o', code 111, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'n', code 110, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'f', code 102, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'i', code 105, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'g', code 103, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'u', code 117, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'r', code 114, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'a', code 97, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 't', code 116, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'i', code 105, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'o', code 111, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'n', code 110, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char '/', code 47, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'l', code 108, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'a', code 97, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'y', code 121, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'o', code 111, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'u', code 117, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 't', code 116, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char '=', code 61, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'U', code 85, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'S', code 83, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'A', code 65, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char ' ', code 32, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'k', code 107, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'e', code 101, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'y', code 121, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'b', code 98, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'o', code 111, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'a', code 97, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'r', code 114, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'd', code 100, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char '-', code 45, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'c', code 99, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'o', code 111, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'n', code 110, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'f', code 102, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'i', code 105, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'g', code 103, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'u', code 117, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'r', code 114, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'a', code 97, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 't', code 116, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'i', code 105, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'o', code 111, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'n', code 110, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char '/', code 47, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'v', code 118, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'a', code 97, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'r', code 114, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'i', code 105, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'a', code 97, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'n', code 110, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 't', code 116, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char '=', code 61, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'U', code 85, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'S', code 83, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'A', code 65, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char ' ', code 32, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'l', code 108, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'o', code 111, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'c', code 99, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'a', code 97, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'l', code 108, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'e', code 101, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char '=', code 61, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'e', code 101, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'n', code 110, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char '_', code 95, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'U', code 85, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'S', code 83, shift true 2017/06/15 08:43:36 packer: 2017/06/15 08:43:36 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char ' ', code 32, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'n', code 110, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'e', code 101, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 't', code 116, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'c', code 99, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'f', code 102, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char '/', code 47, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'e', code 101, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 't', code 116, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char '_', code 95, shift true 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'd', code 100, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'o', code 111, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'm', code 109, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'a', code 97, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'i', code 105, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'n', code 110, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char '=', code 61, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'v', code 118, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Sending char 'm', code 109, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char ' ', code 32, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'n', code 110, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'e', code 101, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 't', code 116, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'c', code 99, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'f', code 102, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char '/', code 47, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'e', code 101, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 't', code 116, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char '_', code 95, shift true 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'h', code 104, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'o', code 111, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 's', code 115, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 't', code 116, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'n', code 110, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'a', code 97, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'm', code 109, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'e', code 101, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char '=', code 61, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'v', code 118, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'a', code 97, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'g', code 103, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'r', code 114, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'a', code 97, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'n', code 110, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 't', code 116, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:48 packer: 2017/06/15 08:43:48 Sending char ' ', code 32, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'g', code 103, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'r', code 114, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'u', code 117, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'b', code 98, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char '-', code 45, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'i', code 105, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'n', code 110, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 's', code 115, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 't', code 116, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'a', code 97, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'e', code 101, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'r', code 114, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char '/', code 47, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'b', code 98, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 't', code 116, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'd', code 100, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'e', code 101, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'v', code 118, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '=', code 61, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '/', code 47, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'd', code 100, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'e', code 101, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'v', code 118, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char '/', code 47, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 's', code 115, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'd', code 100, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Sending char 'a', code 97, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char ' ', code 32, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'n', code 110, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'o', code 111, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'a', code 97, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'p', code 112, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'i', code 105, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'c', code 99, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char ' ', code 32, shift false 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char 'p', code 112, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'r', code 114, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 's', code 115, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'd', code 100, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char '/', code 47, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'u', code 117, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'r', code 114, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'l', code 108, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char '=', code 61, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'h', code 104, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'p', code 112, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char ':', code 58, shift true 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '*', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 55, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 50, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '.', code 46, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 55, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 50, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 52, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 49, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 50, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 53, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 48, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char ':', code 58, shift true 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '8', code 56, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '6', code 54, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '/', code 47, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char 'p', code 112, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'r', code 114, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 's', code 115, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'd', code 100, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char '.', code 46, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'c', code 99, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'f', code 102, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'g', code 103, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:10 packer: 2017/06/15 08:44:10 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:44:11 packer: 2017/06/15 08:44:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 [INFO] Waiting for SSH, up to timeout: 2h46m40s 2017/06/15 08:44:12 ui: [1;32m==> vmware-iso: Waiting for SSH to become available...[0m 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:13 packer: 2017/06/15 08:44:13 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:19 packer: 2017/06/15 08:44:19 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:25 packer: 2017/06/15 08:44:25 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:31 packer: 2017/06/15 08:44:31 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:37 packer: 2017/06/15 08:44:37 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready ```

1.0

Remote ESXi builder failing on retrieving VM ip. ESXi 6.0, packer 1.0 - I'm using a ESXi 6.0 host for testing packer and I've been trying to get the vmware-iso remote ESXi builder to work. With packer 1.0. I get to the point where packer tries to retrieve the guest IP with "esxcli --formatter csv network vm port list -w #######" but errors out saying it cannot find the ip. Packer log: ``` 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Using internal plugin for vmware-vmx 2017/06/15 08:41:00 Using internal plugin for hyperv-iso 2017/06/15 08:41:00 Using internal plugin for virtualbox-iso 2017/06/15 08:41:00 Using internal plugin for amazon-instance 2017/06/15 08:41:00 Using internal plugin for digitalocean 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for oneandone 2017/06/15 08:41:00 Using internal plugin for openstack 2017/06/15 08:41:00 Using internal plugin for parallels-iso 2017/06/15 08:41:00 Using internal plugin for amazon-ebs 2017/06/15 08:41:00 Using internal plugin for amazon-ebsvolume 2017/06/15 08:41:00 Using internal plugin for null 2017/06/15 08:41:00 Using internal plugin for profitbricks 2017/06/15 08:41:00 Using internal plugin for cloudstack 2017/06/15 08:41:00 Using internal plugin for googlecompute 2017/06/15 08:41:00 Using internal plugin for azure-arm 2017/06/15 08:41:00 Using internal plugin for docker 2017/06/15 08:41:00 Using internal plugin for parallels-pvm 2017/06/15 08:41:00 Using internal plugin for qemu 2017/06/15 08:41:00 Using internal plugin for triton 2017/06/15 08:41:00 Using internal plugin for virtualbox-ovf 2017/06/15 08:41:00 Using internal plugin for amazon-chroot 2017/06/15 08:41:00 Using internal plugin for amazon-ebssurrogate 2017/06/15 08:41:00 Using internal plugin for vmware-iso 2017/06/15 08:41:00 Using internal plugin for converge 2017/06/15 08:41:00 Using internal plugin for salt-masterless 2017/06/15 08:41:00 Using internal plugin for chef-client 2017/06/15 08:41:00 Using internal plugin for chef-solo 2017/06/15 08:41:00 Using internal plugin for shell 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for ansible-local 2017/06/15 08:41:00 Using internal plugin for file 2017/06/15 08:41:00 Using internal plugin for puppet-masterless 2017/06/15 08:41:00 Using internal plugin for puppet-server 2017/06/15 08:41:00 Using internal plugin for ansible 2017/06/15 08:41:00 Using internal plugin for powershell 2017/06/15 08:41:00 Using internal plugin for windows-restart 2017/06/15 08:41:00 Using internal plugin for windows-shell 2017/06/15 08:41:00 Using internal plugin for checksum 2017/06/15 08:41:00 Using internal plugin for docker-save 2017/06/15 08:41:00 Using internal plugin for docker-tag 2017/06/15 08:41:00 Using internal plugin for atlas 2017/06/15 08:41:00 Using internal plugin for manifest 2017/06/15 08:41:00 Using internal plugin for compress 2017/06/15 08:41:00 Using internal plugin for googlecompute-export 2017/06/15 08:41:00 Using internal plugin for shell-local 2017/06/15 08:41:00 Using internal plugin for vagrant-cloud 2017/06/15 08:41:00 Using internal plugin for vsphere 2017/06/15 08:41:00 Using internal plugin for docker-import 2017/06/15 08:41:00 Using internal plugin for artifice 2017/06/15 08:41:00 Using internal plugin for docker-push 2017/06/15 08:41:00 Using internal plugin for vagrant 2017/06/15 08:41:00 Using internal plugin for amazon-import 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[null:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null googlecompute:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute qemu:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu virtualbox-ovf:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf amazon-chroot:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot vmware-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso amazon-ebsvolume:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume digitalocean:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file oneandone:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone parallels-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso amazon-ebs:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs cloudstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack parallels-pvm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm vmware-vmx:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx virtualbox-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-instance:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance azure-arm:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm triton:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton amazon-ebssurrogate:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate hyperv-iso:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso profitbricks:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks docker:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker openstack:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack] PostProcessors:map[docker-save:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save docker-tag:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag atlas:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-atlas manifest:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local vagrant-cloud:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud checksum:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum artifice:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice vagrant:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant amazon-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import compress:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress vsphere:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere docker-import:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import docker-push:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push googlecompute-export:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export] Provisioners:map[ansible:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible powershell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell converge:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge shell:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell shell-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local puppet-server:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server chef-solo:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo file:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file windows-restart:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart puppet-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless salt-masterless:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-client:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client ansible-local:/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local]} 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 Loading builder: vmware-iso 2017/06/15 08:41:00 Plugin could not be found. Checking same directory as executable. 2017/06/15 08:41:00 Current exe path: /usr/local/bin/packer 2017/06/15 08:41:00 Creating plugin client for path: /usr/local/bin/packer 2017/06/15 08:41:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-builder-vmware-iso"} 2017/06/15 08:41:00 Waiting for RPC address for: /usr/local/bin/packer 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [INFO] Packer version: 1.0.0 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer Target OS/Arch: linux amd64 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Built with Go Version: go1.8 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Attempting to open config file: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 [WARN] Config file doesn't exist: /root/.packerconfig 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Setting cache directory: /home/git/chief-masterhost/ubuntu/packer_cache 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 args: []string{"packer-builder-vmware-iso"} 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin minimum port: 10000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin maximum port: 25000 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Plugin address: unix /tmp/packer-plugin255655097 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Waiting for connection... 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Detected home directory from env var: /root 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 Serving a plugin connection... 2017/06/15 08:41:00 ui: [1;32mvmware-iso output will be in this color.[0m 2017/06/15 08:41:00 ui: 2017/06/15 08:41:00 Build debug mode: false 2017/06/15 08:41:00 Force build: false 2017/06/15 08:41:00 On error: 2017/06/15 08:41:00 Preparing build: vmware-iso 2017/06/15 08:41:00 Waiting on builds to complete... 2017/06/15 08:41:00 Starting build run: vmware-iso 2017/06/15 08:41:00 Running builder: vmware-iso 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 reconnecting to TCP connection for SSH 2017/06/15 08:41:00 packer: 2017/06/15 08:41:00 handshaking with SSH 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Question 1: Password: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Keyboard interactive challenge: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- User: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 -- Instructions: 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 handshake complete! 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 [INFO] no local agent socket, will not connect agent 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system version get 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 Connected to VMware ESXi 6.0.0 Releasebuild-3620759 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 opening new ssh session 2017/06/15 08:41:01 packer: 2017/06/15 08:41:01 starting remote command: esxcli --formatter csv system settings advanced list -o /Net/GuestIPHack 2017/06/15 08:41:02 ui: [1;32m==> vmware-iso: Downloading or copying ISO[0m 2017/06/15 08:41:02 ui: [0;32m vmware-iso: Downloading or copying: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso[0m 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Acquiring lock to download: http://mirror.yandex.ru/ubuntu-releases/16.04.2/ubuntu-16.04.2-server-amd64.iso 2017/06/15 08:41:02 packer: 2017/06/15 08:41:02 Verifying checksum of /home/git/chief-masterhost/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 [DEBUG] Initial checksum matched, no download needed. 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: test -e /vmfs/volumes/***/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote command exited with '1': test -e /vmfs/volumes/***/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/***GB/ubuntu/output-vmware-iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 No floppy files specified. Floppy disk will not be made. 2017/06/15 08:41:14 ui: [1;32m==> vmware-iso: Uploading ISO to remote machine...[0m 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Remote uploading: /home/git/***/ubuntu/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: mkdir -p /vmfs/volumes/***GB/packer_cache 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 Verifying checksum of /vmfs/volumes/***GB/packer_cache/8f9277189b126f4f3175bf43485c63857ae18125022979fc9858bff0937f33ff.iso 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 opening new ssh session 2017/06/15 08:41:14 packer: 2017/06/15 08:41:14 starting remote command: sha256sum -c 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 Initial checksum matched, no upload needed. 2017/06/15 08:41:50 ui: [1;32m==> vmware-iso: Creating virtual machine disk[0m 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 opening new ssh session 2017/06/15 08:41:50 packer: 2017/06/15 08:41:50 starting remote command: vmkfstools -c 7000M -d zeroedthick -a lsilogic /vmfs/volumes/***GB/ubuntu/output-vmware-iso/disk.vmdk 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Building and writing VMX file[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'memsize' = '512' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'cpuid.coresPerSocket' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.present' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.startConnected' = 'true' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.virtualDev' = 'e1000' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'RemoteDisplay.vnc.webSocket.port' = '5900' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'ethernet0.networkName' = '***' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Setting VMX: 'numvcpus' = '1' 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Suppressing messages in VMX 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying port: 8446 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Starting HTTP server on port 8446[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Looking for available port between 5900 and 6000 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 starting remote command: esxcli --formatter csv network ip connection list 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5904, port 5904 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5903, port 5903 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5901, port 5901 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5900, port 5900 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::5989, port 5989 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:8889, port 8889 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address fe80:2::207:e9ff:fe5a:7c5f:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ***:427, port 427 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::443, port 443 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::80, port 80 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:22, port 22 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address 0.0.0.0:902, port 902 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8000, port 8000 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8100, port 8100 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address :::8300, port 8300 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 ESXi listening on address ::1:2233, port 2233 unavailable for VNC 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5900 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Port 5901 in use 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Trying address: ***... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Found available VNC port: 5902 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Writing VMX to: /tmp/packer-vmx789051076/ubuntu.vmx 2017/06/15 08:41:51 ui: [1;32m==> vmware-iso: Registering remote VM...[0m 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 opening new ssh session 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Starting remote scp process: scp -vt /vmfs/volumes/***GB/ubuntu/output-vmware-iso 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Started SCP session, beginning transfers... 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 Copying input data into temporary file so we can read the length 2017/06/15 08:41:51 packer: 2017/06/15 08:41:51 [DEBUG] scp: Uploading ubuntu.vmx: perms=C0644 size=2501 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 SCP session complete, closing stdin pipe. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 Waiting for SSH session to complete. 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 scp stderr (length 28): Sink: C0644 2501 ubuntu.vmx 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd solo/registervm /vmfs/volumes/***GB/ubuntu/output-vmware-iso/ubuntu.vmx 2017/06/15 08:41:52 ui: [1;32m==> vmware-iso: Starting virtual machine...[0m 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 opening new ssh session 2017/06/15 08:41:52 packer: 2017/06/15 08:41:52 starting remote command: vim-cmd vmsvc/power.on 77 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 opening new ssh session 2017/06/15 08:41:54 packer: 2017/06/15 08:41:54 starting remote command: vim-cmd vmsvc/power.getstate 77 2017/06/15 08:41:54 ui: [1;32m==> vmware-iso: Waiting 10s for boot...[0m 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Connecting to VM via VNC[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Connected to VNC desktop: ubuntu 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Host IP for the VMware machine: *** 2017/06/15 08:42:04 ui: [1;32m==> vmware-iso: Typing the boot command over VNC...[0m 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:42:04 packer: 2017/06/15 08:42:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:05 packer: 2017/06/15 08:42:05 Special code '<f6>' found, replacing with: 65475 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<esc>' found, replacing with: 65307 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:06 packer: 2017/06/15 08:42:06 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:12 packer: 2017/06/15 08:42:12 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:13 packer: 2017/06/15 08:42:13 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:14 packer: 2017/06/15 08:42:14 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:15 packer: 2017/06/15 08:42:15 Special code '<bs>' found, replacing with: 65288 2017/06/15 08:42:22 packer: 2017/06/15 08:42:22 Sending char '/', code 47, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'i', code 105, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'n', code 110, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 's', code 115, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 't', code 116, shift false 2017/06/15 08:42:23 packer: 2017/06/15 08:42:23 Sending char 'a', code 97, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'l', code 108, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char '/', code 47, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'v', code 118, shift false 2017/06/15 08:42:24 packer: 2017/06/15 08:42:24 Sending char 'm', code 109, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'l', code 108, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'i', code 105, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'n', code 110, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'u', code 117, shift false 2017/06/15 08:42:25 packer: 2017/06/15 08:42:25 Sending char 'z', code 122, shift false 2017/06/15 08:42:26 packer: 2017/06/15 08:42:26 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char ' ', code 32, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'a', code 97, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'u', code 117, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 't', code 116, shift false 2017/06/15 08:42:27 packer: 2017/06/15 08:42:27 Sending char 'o', code 111, shift false 2017/06/15 08:42:28 packer: 2017/06/15 08:42:28 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char ' ', code 32, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'c', code 99, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'o', code 111, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 'n', code 110, shift false 2017/06/15 08:42:29 packer: 2017/06/15 08:42:29 Sending char 's', code 115, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'o', code 111, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'l', code 108, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 'e', code 101, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char '-', code 45, shift false 2017/06/15 08:42:30 packer: 2017/06/15 08:42:30 Sending char 's', code 115, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'e', code 101, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 't', code 116, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'u', code 117, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char 'p', code 112, shift false 2017/06/15 08:42:31 packer: 2017/06/15 08:42:31 Sending char '/', code 47, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'a', code 97, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 's', code 115, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'k', code 107, shift false 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char '_', code 95, shift true 2017/06/15 08:42:32 packer: 2017/06/15 08:42:32 Sending char 'd', code 100, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 't', code 116, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'e', code 101, shift false 2017/06/15 08:42:33 packer: 2017/06/15 08:42:33 Sending char 'c', code 99, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 't', code 116, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char '=', code 61, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'f', code 102, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'a', code 97, shift false 2017/06/15 08:42:34 packer: 2017/06/15 08:42:34 Sending char 'l', code 108, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 's', code 115, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Sending char 'e', code 101, shift false 2017/06/15 08:42:35 packer: 2017/06/15 08:42:35 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char ' ', code 32, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'c', code 99, shift false 2017/06/15 08:42:36 packer: 2017/06/15 08:42:36 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'n', code 110, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 's', code 115, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'o', code 111, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'l', code 108, shift false 2017/06/15 08:42:37 packer: 2017/06/15 08:42:37 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char '-', code 45, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 's', code 115, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'e', code 101, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 't', code 116, shift false 2017/06/15 08:42:38 packer: 2017/06/15 08:42:38 Sending char 'u', code 117, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'p', code 112, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char '/', code 47, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'l', code 108, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'a', code 97, shift false 2017/06/15 08:42:39 packer: 2017/06/15 08:42:39 Sending char 'y', code 121, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'u', code 117, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 't', code 116, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'c', code 99, shift false 2017/06/15 08:42:40 packer: 2017/06/15 08:42:40 Sending char 'o', code 111, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'd', code 100, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'e', code 101, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char '=', code 61, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 'u', code 117, shift false 2017/06/15 08:42:41 packer: 2017/06/15 08:42:41 Sending char 's', code 115, shift false 2017/06/15 08:42:42 packer: 2017/06/15 08:42:42 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char ' ', code 32, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'c', code 99, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'o', code 111, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 'n', code 110, shift false 2017/06/15 08:42:43 packer: 2017/06/15 08:42:43 Sending char 's', code 115, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'o', code 111, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'l', code 108, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 'e', code 101, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char '-', code 45, shift false 2017/06/15 08:42:44 packer: 2017/06/15 08:42:44 Sending char 's', code 115, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'e', code 101, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 't', code 116, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'u', code 117, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char 'p', code 112, shift false 2017/06/15 08:42:45 packer: 2017/06/15 08:42:45 Sending char '/', code 47, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'm', code 109, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'o', code 111, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'd', code 100, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'e', code 101, shift false 2017/06/15 08:42:46 packer: 2017/06/15 08:42:46 Sending char 'l', code 108, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'c', code 99, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'o', code 111, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'd', code 100, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char 'e', code 101, shift false 2017/06/15 08:42:47 packer: 2017/06/15 08:42:47 Sending char '=', code 61, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'p', code 112, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char 'c', code 99, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '1', code 49, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '0', code 48, shift false 2017/06/15 08:42:48 packer: 2017/06/15 08:42:48 Sending char '5', code 53, shift false 2017/06/15 08:42:49 packer: 2017/06/15 08:42:49 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char ' ', code 32, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'd', code 100, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'e', code 101, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'b', code 98, shift false 2017/06/15 08:42:50 packer: 2017/06/15 08:42:50 Sending char 'c', code 99, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'o', code 111, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'n', code 110, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char '/', code 47, shift false 2017/06/15 08:42:51 packer: 2017/06/15 08:42:51 Sending char 'f', code 102, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'r', code 114, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'o', code 111, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'n', code 110, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 't', code 116, shift false 2017/06/15 08:42:52 packer: 2017/06/15 08:42:52 Sending char 'e', code 101, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'd', code 100, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char '=', code 61, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'n', code 110, shift false 2017/06/15 08:42:53 packer: 2017/06/15 08:42:53 Sending char 'o', code 111, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'i', code 105, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'n', code 110, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 't', code 116, shift false 2017/06/15 08:42:54 packer: 2017/06/15 08:42:54 Sending char 'e', code 101, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'r', code 114, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'a', code 97, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'c', code 99, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 't', code 116, shift false 2017/06/15 08:42:55 packer: 2017/06/15 08:42:55 Sending char 'i', code 105, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'v', code 118, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Sending char 'e', code 101, shift false 2017/06/15 08:42:56 packer: 2017/06/15 08:42:56 Special code '<wait>' found, sleeping one second 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char ' ', code 32, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'd', code 100, shift false 2017/06/15 08:42:57 packer: 2017/06/15 08:42:57 Sending char 'e', code 101, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'b', code 98, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'i', code 105, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'a', code 97, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char 'n', code 110, shift false 2017/06/15 08:42:58 packer: 2017/06/15 08:42:58 Sending char '-', code 45, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'i', code 105, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'n', code 110, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 's', code 115, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 't', code 116, shift false 2017/06/15 08:42:59 packer: 2017/06/15 08:42:59 Sending char 'a', code 97, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'l', code 108, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'e', code 101, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char 'r', code 114, shift false 2017/06/15 08:43:00 packer: 2017/06/15 08:43:00 Sending char '=', code 61, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'e', code 101, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'n', code 110, shift false 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char '_', code 95, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'U', code 85, shift true 2017/06/15 08:43:01 packer: 2017/06/15 08:43:01 Sending char 'S', code 83, shift true 2017/06/15 08:43:02 packer: 2017/06/15 08:43:02 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char ' ', code 32, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'b', code 98, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char '=', code 61, shift false 2017/06/15 08:43:03 packer: 2017/06/15 08:43:03 Sending char 'f', code 102, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'a', code 97, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'l', code 108, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 's', code 115, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Sending char 'e', code 101, shift false 2017/06/15 08:43:04 packer: 2017/06/15 08:43:04 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:05 packer: 2017/06/15 08:43:05 Sending char ' ', code 32, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'n', code 110, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'i', code 105, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 't', code 116, shift false 2017/06/15 08:43:06 packer: 2017/06/15 08:43:06 Sending char 'r', code 114, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'd', code 100, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '=', code 61, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char '/', code 47, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'i', code 105, shift false 2017/06/15 08:43:07 packer: 2017/06/15 08:43:07 Sending char 'n', code 110, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 's', code 115, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 't', code 116, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'a', code 97, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:08 packer: 2017/06/15 08:43:08 Sending char 'l', code 108, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char '/', code 47, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'n', code 110, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 'i', code 105, shift false 2017/06/15 08:43:09 packer: 2017/06/15 08:43:09 Sending char 't', code 116, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'r', code 114, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'd', code 100, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char '.', code 46, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'g', code 103, shift false 2017/06/15 08:43:10 packer: 2017/06/15 08:43:10 Sending char 'z', code 122, shift false 2017/06/15 08:43:11 packer: 2017/06/15 08:43:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char ' ', code 32, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'k', code 107, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'b', code 98, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char 'd', code 100, shift false 2017/06/15 08:43:12 packer: 2017/06/15 08:43:12 Sending char '-', code 45, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'c', code 99, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'h', code 104, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 'o', code 111, shift false 2017/06/15 08:43:13 packer: 2017/06/15 08:43:13 Sending char 's', code 115, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'r', code 114, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char '/', code 47, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'm', code 109, shift false 2017/06/15 08:43:14 packer: 2017/06/15 08:43:14 Sending char 'e', code 101, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 't', code 116, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'h', code 104, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'o', code 111, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char 'd', code 100, shift false 2017/06/15 08:43:15 packer: 2017/06/15 08:43:15 Sending char '=', code 61, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 'u', code 117, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Sending char 's', code 115, shift false 2017/06/15 08:43:16 packer: 2017/06/15 08:43:16 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char ' ', code 32, shift false 2017/06/15 08:43:17 packer: 2017/06/15 08:43:17 Sending char 'k', code 107, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'e', code 101, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'y', code 121, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'b', code 98, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'o', code 111, shift false 2017/06/15 08:43:18 packer: 2017/06/15 08:43:18 Sending char 'a', code 97, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'r', code 114, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'd', code 100, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char '-', code 45, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'c', code 99, shift false 2017/06/15 08:43:19 packer: 2017/06/15 08:43:19 Sending char 'o', code 111, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'n', code 110, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'f', code 102, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'i', code 105, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'g', code 103, shift false 2017/06/15 08:43:20 packer: 2017/06/15 08:43:20 Sending char 'u', code 117, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'r', code 114, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'a', code 97, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 't', code 116, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'i', code 105, shift false 2017/06/15 08:43:21 packer: 2017/06/15 08:43:21 Sending char 'o', code 111, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'n', code 110, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char '/', code 47, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'l', code 108, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'a', code 97, shift false 2017/06/15 08:43:22 packer: 2017/06/15 08:43:22 Sending char 'y', code 121, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'o', code 111, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'u', code 117, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 't', code 116, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char '=', code 61, shift false 2017/06/15 08:43:23 packer: 2017/06/15 08:43:23 Sending char 'U', code 85, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'S', code 83, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Sending char 'A', code 65, shift true 2017/06/15 08:43:24 packer: 2017/06/15 08:43:24 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char ' ', code 32, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'k', code 107, shift false 2017/06/15 08:43:25 packer: 2017/06/15 08:43:25 Sending char 'e', code 101, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'y', code 121, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'b', code 98, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'o', code 111, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'a', code 97, shift false 2017/06/15 08:43:26 packer: 2017/06/15 08:43:26 Sending char 'r', code 114, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'd', code 100, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char '-', code 45, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'c', code 99, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'o', code 111, shift false 2017/06/15 08:43:27 packer: 2017/06/15 08:43:27 Sending char 'n', code 110, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'f', code 102, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'i', code 105, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'g', code 103, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'u', code 117, shift false 2017/06/15 08:43:28 packer: 2017/06/15 08:43:28 Sending char 'r', code 114, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'a', code 97, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 't', code 116, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'i', code 105, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'o', code 111, shift false 2017/06/15 08:43:29 packer: 2017/06/15 08:43:29 Sending char 'n', code 110, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char '/', code 47, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'v', code 118, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'a', code 97, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'r', code 114, shift false 2017/06/15 08:43:30 packer: 2017/06/15 08:43:30 Sending char 'i', code 105, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'a', code 97, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'n', code 110, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 't', code 116, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char '=', code 61, shift false 2017/06/15 08:43:31 packer: 2017/06/15 08:43:31 Sending char 'U', code 85, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'S', code 83, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Sending char 'A', code 65, shift true 2017/06/15 08:43:32 packer: 2017/06/15 08:43:32 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char ' ', code 32, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'l', code 108, shift false 2017/06/15 08:43:33 packer: 2017/06/15 08:43:33 Sending char 'o', code 111, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'c', code 99, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'a', code 97, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'l', code 108, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char 'e', code 101, shift false 2017/06/15 08:43:34 packer: 2017/06/15 08:43:34 Sending char '=', code 61, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'e', code 101, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'n', code 110, shift false 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char '_', code 95, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'U', code 85, shift true 2017/06/15 08:43:35 packer: 2017/06/15 08:43:35 Sending char 'S', code 83, shift true 2017/06/15 08:43:36 packer: 2017/06/15 08:43:36 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char ' ', code 32, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'n', code 110, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'e', code 101, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 't', code 116, shift false 2017/06/15 08:43:37 packer: 2017/06/15 08:43:37 Sending char 'c', code 99, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'f', code 102, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char '/', code 47, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'g', code 103, shift false 2017/06/15 08:43:38 packer: 2017/06/15 08:43:38 Sending char 'e', code 101, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 't', code 116, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char '_', code 95, shift true 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'd', code 100, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'o', code 111, shift false 2017/06/15 08:43:39 packer: 2017/06/15 08:43:39 Sending char 'm', code 109, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'a', code 97, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'i', code 105, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'n', code 110, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char '=', code 61, shift false 2017/06/15 08:43:40 packer: 2017/06/15 08:43:40 Sending char 'v', code 118, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Sending char 'm', code 109, shift false 2017/06/15 08:43:41 packer: 2017/06/15 08:43:41 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char ' ', code 32, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'n', code 110, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 'e', code 101, shift false 2017/06/15 08:43:42 packer: 2017/06/15 08:43:42 Sending char 't', code 116, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'c', code 99, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'f', code 102, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char '/', code 47, shift false 2017/06/15 08:43:43 packer: 2017/06/15 08:43:43 Sending char 'g', code 103, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'e', code 101, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 't', code 116, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char '_', code 95, shift true 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'h', code 104, shift false 2017/06/15 08:43:44 packer: 2017/06/15 08:43:44 Sending char 'o', code 111, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 's', code 115, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 't', code 116, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'n', code 110, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'a', code 97, shift false 2017/06/15 08:43:45 packer: 2017/06/15 08:43:45 Sending char 'm', code 109, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'e', code 101, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char '=', code 61, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'v', code 118, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'a', code 97, shift false 2017/06/15 08:43:46 packer: 2017/06/15 08:43:46 Sending char 'g', code 103, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'r', code 114, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'a', code 97, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 'n', code 110, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Sending char 't', code 116, shift false 2017/06/15 08:43:47 packer: 2017/06/15 08:43:47 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:48 packer: 2017/06/15 08:43:48 Sending char ' ', code 32, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'g', code 103, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'r', code 114, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'u', code 117, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char 'b', code 98, shift false 2017/06/15 08:43:49 packer: 2017/06/15 08:43:49 Sending char '-', code 45, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'i', code 105, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'n', code 110, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 's', code 115, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 't', code 116, shift false 2017/06/15 08:43:50 packer: 2017/06/15 08:43:50 Sending char 'a', code 97, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'l', code 108, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'e', code 101, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char 'r', code 114, shift false 2017/06/15 08:43:51 packer: 2017/06/15 08:43:51 Sending char '/', code 47, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'b', code 98, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'o', code 111, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 't', code 116, shift false 2017/06/15 08:43:52 packer: 2017/06/15 08:43:52 Sending char 'd', code 100, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'e', code 101, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'v', code 118, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '=', code 61, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char '/', code 47, shift false 2017/06/15 08:43:53 packer: 2017/06/15 08:43:53 Sending char 'd', code 100, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'e', code 101, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'v', code 118, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char '/', code 47, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 's', code 115, shift false 2017/06/15 08:43:54 packer: 2017/06/15 08:43:54 Sending char 'd', code 100, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Sending char 'a', code 97, shift false 2017/06/15 08:43:55 packer: 2017/06/15 08:43:55 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char ' ', code 32, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'n', code 110, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'o', code 111, shift false 2017/06/15 08:43:56 packer: 2017/06/15 08:43:56 Sending char 'a', code 97, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'p', code 112, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'i', code 105, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Sending char 'c', code 99, shift false 2017/06/15 08:43:57 packer: 2017/06/15 08:43:57 Special code '<wait>' found, sleeping one second 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char ' ', code 32, shift false 2017/06/15 08:43:58 packer: 2017/06/15 08:43:58 Sending char 'p', code 112, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'r', code 114, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 's', code 115, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:43:59 packer: 2017/06/15 08:43:59 Sending char 'e', code 101, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'd', code 100, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char '/', code 47, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'u', code 117, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'r', code 114, shift false 2017/06/15 08:44:00 packer: 2017/06/15 08:44:00 Sending char 'l', code 108, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char '=', code 61, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'h', code 104, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 't', code 116, shift false 2017/06/15 08:44:01 packer: 2017/06/15 08:44:01 Sending char 'p', code 112, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char ':', code 58, shift true 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '/', code 47, shift false 2017/06/15 08:44:02 packer: 2017/06/15 08:44:02 Sending char '*', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 55, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 50, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '.', code 46, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 49, shift false 2017/06/15 08:44:03 packer: 2017/06/15 08:44:03 Sending char '*', code 55, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 50, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 52, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '*', code 49, shift false 2017/06/15 08:44:04 packer: 2017/06/15 08:44:04 Sending char '.', code 46, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 50, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 53, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '*', code 48, shift false 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char ':', code 58, shift true 2017/06/15 08:44:05 packer: 2017/06/15 08:44:05 Sending char '8', code 56, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '4', code 52, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '6', code 54, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char '/', code 47, shift false 2017/06/15 08:44:06 packer: 2017/06/15 08:44:06 Sending char 'p', code 112, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'r', code 114, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 's', code 115, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:07 packer: 2017/06/15 08:44:07 Sending char 'e', code 101, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'd', code 100, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char '.', code 46, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'c', code 99, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'f', code 102, shift false 2017/06/15 08:44:08 packer: 2017/06/15 08:44:08 Sending char 'g', code 103, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char '-', code 45, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Sending char ' ', code 32, shift false 2017/06/15 08:44:09 packer: 2017/06/15 08:44:09 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:10 packer: 2017/06/15 08:44:10 Special code '<enter>' found, replacing with: 65293 2017/06/15 08:44:11 packer: 2017/06/15 08:44:11 Special code '<wait>' found, sleeping one second 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 [INFO] Waiting for SSH, up to timeout: 2h46m40s 2017/06/15 08:44:12 ui: [1;32m==> vmware-iso: Waiting for SSH to become available...[0m 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 opening new ssh session 2017/06/15 08:44:12 packer: 2017/06/15 08:44:12 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:13 packer: 2017/06/15 08:44:13 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 opening new ssh session 2017/06/15 08:44:18 packer: 2017/06/15 08:44:18 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:19 packer: 2017/06/15 08:44:19 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 opening new ssh session 2017/06/15 08:44:24 packer: 2017/06/15 08:44:24 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:25 packer: 2017/06/15 08:44:25 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 opening new ssh session 2017/06/15 08:44:30 packer: 2017/06/15 08:44:30 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:31 packer: 2017/06/15 08:44:31 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm list 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 opening new ssh session 2017/06/15 08:44:36 packer: 2017/06/15 08:44:36 starting remote command: esxcli --formatter csv network vm port list -w 1437275 2017/06/15 08:44:37 packer: 2017/06/15 08:44:37 [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready ```

non_defect

remote esxi builder failing on retrieving vm ip esxi packer i m using a esxi host for testing packer and i ve been trying to get the vmware iso remote esxi builder to work with packer i get to the point where packer tries to retrieve the guest ip with esxcli formatter csv network vm port list w but errors out saying it cannot find the ip packer log packer version packer target os arch linux built with go version detected home directory from env var root using internal plugin for vmware vmx using internal plugin for hyperv iso using internal plugin for virtualbox iso using internal plugin for amazon instance using internal plugin for digitalocean using internal plugin for file using internal plugin for oneandone using internal plugin for openstack using internal plugin for parallels iso using internal plugin for amazon ebs using internal plugin for amazon ebsvolume using internal plugin for null using internal plugin for profitbricks using internal plugin for cloudstack using internal plugin for googlecompute using internal plugin for azure arm using internal plugin for docker using internal plugin for parallels pvm using internal plugin for qemu using internal plugin for triton using internal plugin for virtualbox ovf using internal plugin for amazon chroot using internal plugin for amazon ebssurrogate using internal plugin for vmware iso using internal plugin for converge using internal plugin for salt masterless using internal plugin for chef client using internal plugin for chef solo using internal plugin for shell using internal plugin for shell local using internal plugin for ansible local using internal plugin for file using internal plugin for puppet masterless using internal plugin for puppet server using internal plugin for ansible using internal plugin for powershell using internal plugin for windows restart using internal plugin for windows shell using internal plugin for checksum using internal plugin for docker save using internal plugin for docker tag using internal plugin for atlas using internal plugin for manifest using internal plugin for compress using internal plugin for googlecompute export using internal plugin for shell local using internal plugin for vagrant cloud using internal plugin for vsphere using internal plugin for docker import using internal plugin for artifice using internal plugin for docker push using internal plugin for vagrant using internal plugin for amazon import detected home directory from env var root attempting to open config file root packerconfig config file doesn t exist root packerconfig packer config disablecheckpoint false disablecheckpointsignature false pluginminport pluginmaxport builders map postprocessors map provisioners map setting cache directory home git chief masterhost ubuntu packer cache loading builder vmware iso plugin could not be found checking same directory as executable current exe path usr local bin packer creating plugin client for path usr local bin packer starting plugin usr local bin packer string usr local bin packer plugin packer builder vmware iso waiting for rpc address for usr local bin packer detected home directory from env var root packer packer version packer packer target os arch linux packer built with go version packer detected home directory from env var root packer attempting to open config file root packerconfig packer config file doesn t exist root packerconfig packer packer config disablecheckpoint false disablecheckpointsignature false pluginminport pluginmaxport builders map postprocessors map provisioners map packer setting cache directory home git chief masterhost ubuntu packer cache packer args string packer builder vmware iso packer plugin minimum port packer plugin maximum port packer plugin address unix tmp packer packer waiting for connection packer detected home directory from env var root packer serving a plugin connection ui iso output will be in this color ui build debug mode false force build false on error preparing build vmware iso waiting on builds to complete starting build run vmware iso running builder vmware iso packer reconnecting to tcp connection for ssh packer handshaking with ssh packer keyboard interactive challenge packer user packer instructions packer question password packer keyboard interactive challenge packer user packer instructions packer handshake complete packer no local agent socket will not connect agent packer opening new ssh session packer starting remote command esxcli formatter csv system version get packer connected to vmware esxi releasebuild packer opening new ssh session packer starting remote command esxcli formatter csv system settings advanced list o net guestiphack ui vmware iso downloading or copying iso ui vmware iso downloading or copying packer acquiring lock to download packer verifying checksum of home git chief masterhost ubuntu packer cache iso packer initial checksum matched no download needed packer opening new ssh session packer starting remote command test e vmfs volumes ubuntu output vmware iso packer remote command exited with test e vmfs volumes ubuntu output vmware iso packer opening new ssh session packer starting remote command mkdir p vmfs volumes gb ubuntu output vmware iso packer no floppy files specified floppy disk will not be made ui vmware iso uploading iso to remote machine packer remote uploading home git ubuntu packer cache iso packer opening new ssh session packer starting remote command mkdir p vmfs volumes gb packer cache packer verifying checksum of vmfs volumes gb packer cache iso packer opening new ssh session packer starting remote command c packer initial checksum matched no upload needed ui vmware iso creating virtual machine disk packer opening new ssh session packer starting remote command vmkfstools c d zeroedthick a lsilogic vmfs volumes gb ubuntu output vmware iso disk vmdk ui vmware iso building and writing vmx file packer writing vmx to tmp packer ubuntu vmx packer setting vmx memsize packer setting vmx cpuid corespersocket packer setting vmx present true packer setting vmx startconnected true packer setting vmx virtualdev packer setting vmx remotedisplay vnc websocket port packer setting vmx networkname packer setting vmx numvcpus packer writing vmx to tmp packer ubuntu vmx packer suppressing messages in vmx packer trying port ui vmware iso starting http server on port packer looking for available port between and packer opening new ssh session packer starting remote command esxcli formatter csv network ip connection list packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer esxi listening on address port unavailable for vnc packer port in use packer port in use packer trying address packer found available vnc port packer writing vmx to tmp packer ubuntu vmx ui vmware iso registering remote vm packer opening new ssh session packer starting remote scp process scp vt vmfs volumes gb ubuntu output vmware iso packer started scp session beginning transfers packer copying input data into temporary file so we can read the length packer scp uploading ubuntu vmx perms size packer scp session complete closing stdin pipe packer waiting for ssh session to complete packer scp stderr length sink ubuntu vmx packer opening new ssh session packer starting remote command vim cmd solo registervm vmfs volumes gb ubuntu output vmware iso ubuntu vmx ui vmware iso starting virtual machine packer opening new ssh session packer starting remote command vim cmd vmsvc power on packer opening new ssh session packer starting remote command vim cmd vmsvc power getstate ui vmware iso waiting for boot ui vmware iso connecting to vm via vnc packer connected to vnc desktop ubuntu packer host ip for the vmware machine ui vmware iso typing the boot command over vnc packer special code found replacing with packer special code found sleeping one second packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer special code found replacing with packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char code shift false packer sending char v code shift false packer sending char m code shift false packer sending char l code shift false packer sending char i code shift false packer sending char n code shift false packer sending char u code shift false packer sending char z code shift false packer special code found sleeping one second packer sending char code shift false packer sending char a code shift false packer sending char u code shift false packer sending char t code shift false packer sending char o code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char a code shift false packer sending char s code shift false packer sending char k code shift false packer sending char code shift true packer sending char d code shift false packer sending char e code shift false packer sending char t code shift false packer sending char e code shift false packer sending char c code shift false packer sending char t code shift false packer sending char code shift false packer sending char f code shift false packer sending char a code shift false packer sending char l code shift false packer sending char s code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char l code shift false packer sending char a code shift false packer sending char y code shift false packer sending char o code shift false packer sending char u code shift false packer sending char t code shift false packer sending char c code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char code shift false packer sending char u code shift false packer sending char s code shift false packer special code found sleeping one second packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char s code shift false packer sending char o code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char s code shift false packer sending char e code shift false packer sending char t code shift false packer sending char u code shift false packer sending char p code shift false packer sending char code shift false packer sending char m code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char l code shift false packer sending char c code shift false packer sending char o code shift false packer sending char d code shift false packer sending char e code shift false packer sending char code shift false packer sending char p code shift false packer sending char c code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer special code found sleeping one second packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char b code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char code shift false packer sending char f code shift false packer sending char r code shift false packer sending char o code shift false packer sending char n code shift false packer sending char t code shift false packer sending char e code shift false packer sending char n code shift false packer sending char d code shift false packer sending char code shift false packer sending char n code shift false packer sending char o code shift false packer sending char n code shift false packer sending char i code shift false packer sending char n code shift false packer sending char t code shift false packer sending char e code shift false packer sending char r code shift false packer sending char a code shift false packer sending char c code shift false packer sending char t code shift false packer sending char i code shift false packer sending char v code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char b code shift false packer sending char i code shift false packer sending char a code shift false packer sending char n code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char e code shift false packer sending char n code shift false packer sending char code shift true packer sending char u code shift true packer sending char s code shift true packer special code found sleeping one second packer sending char code shift false packer sending char f code shift false packer sending char b code shift false packer sending char code shift false packer sending char f code shift false packer sending char a code shift false packer sending char l code shift false packer sending char s code shift false packer sending char e code shift false packer special code found sleeping one second packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char i code shift false packer sending char t code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char i code shift false packer sending char t code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char g code shift false packer sending char z code shift false packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char b code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char h code shift false packer sending char o code shift false packer sending char o code shift false packer sending char s code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char m code shift false packer sending char e code shift false packer sending char t code shift false packer sending char h code shift false packer sending char o code shift false packer sending char d code shift false packer sending char code shift false packer sending char u code shift false packer sending char s code shift false packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char e code shift false packer sending char y code shift false packer sending char b code shift false packer sending char o code shift false packer sending char a code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char i code shift false packer sending char g code shift false packer sending char u code shift false packer sending char r code shift false packer sending char a code shift false packer sending char t code shift false packer sending char i code shift false packer sending char o code shift false packer sending char n code shift false packer sending char code shift false packer sending char l code shift false packer sending char a code shift false packer sending char y code shift false packer sending char o code shift false packer sending char u code shift false packer sending char t code shift false packer sending char code shift false packer sending char u code shift true packer sending char s code shift true packer sending char a code shift true packer special code found sleeping one second packer sending char code shift false packer sending char k code shift false packer sending char e code shift false packer sending char y code shift false packer sending char b code shift false packer sending char o code shift false packer sending char a code shift false packer sending char r code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char o code shift false packer sending char n code shift false packer sending char f code shift false packer sending char i code shift false packer sending char g code shift false packer sending char u code shift false packer sending char r code shift false packer sending char a code shift false packer sending char t code shift false packer sending char i code shift false packer sending char o code shift false packer sending char n code shift false packer sending char code shift false packer sending char v code shift false packer sending char a code shift false packer sending char r code shift false packer sending char i code shift false packer sending char a code shift false packer sending char n code shift false packer sending char t code shift false packer sending char code shift false packer sending char u code shift true packer sending char s code shift true packer sending char a code shift true packer special code found sleeping one second packer sending char code shift false packer sending char l code shift false packer sending char o code shift false packer sending char c code shift false packer sending char a code shift false packer sending char l code shift false packer sending char e code shift false packer sending char code shift false packer sending char e code shift false packer sending char n code shift false packer sending char code shift true packer sending char u code shift true packer sending char s code shift true packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char e code shift false packer sending char t code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char g code shift false packer sending char e code shift false packer sending char t code shift false packer sending char code shift true packer sending char d code shift false packer sending char o code shift false packer sending char m code shift false packer sending char a code shift false packer sending char i code shift false packer sending char n code shift false packer sending char code shift false packer sending char v code shift false packer sending char m code shift false packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char e code shift false packer sending char t code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char g code shift false packer sending char e code shift false packer sending char t code shift false packer sending char code shift true packer sending char h code shift false packer sending char o code shift false packer sending char s code shift false packer sending char t code shift false packer sending char n code shift false packer sending char a code shift false packer sending char m code shift false packer sending char e code shift false packer sending char code shift false packer sending char v code shift false packer sending char a code shift false packer sending char g code shift false packer sending char r code shift false packer sending char a code shift false packer sending char n code shift false packer sending char t code shift false packer special code found sleeping one second packer sending char code shift false packer sending char g code shift false packer sending char r code shift false packer sending char u code shift false packer sending char b code shift false packer sending char code shift false packer sending char i code shift false packer sending char n code shift false packer sending char s code shift false packer sending char t code shift false packer sending char a code shift false packer sending char l code shift false packer sending char l code shift false packer sending char e code shift false packer sending char r code shift false packer sending char code shift false packer sending char b code shift false packer sending char o code shift false packer sending char o code shift false packer sending char t code shift false packer sending char d code shift false packer sending char e code shift false packer sending char v code shift false packer sending char code shift false packer sending char code shift false packer sending char d code shift false packer sending char e code shift false packer sending char v code shift false packer sending char code shift false packer sending char s code shift false packer sending char d code shift false packer sending char a code shift false packer special code found sleeping one second packer sending char code shift false packer sending char n code shift false packer sending char o code shift false packer sending char a code shift false packer sending char p code shift false packer sending char i code shift false packer sending char c code shift false packer special code found sleeping one second packer sending char code shift false packer sending char p code shift false packer sending char r code shift false packer sending char e code shift false packer sending char s code shift false packer sending char e code shift false packer sending char e code shift false packer sending char d code shift false packer sending char code shift false packer sending char u code shift false packer sending char r code shift false packer sending char l code shift false packer sending char code shift false packer sending char h code shift false packer sending char t code shift false packer sending char t code shift false packer sending char p code shift false packer sending char code shift true packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift true packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char p code shift false packer sending char r code shift false packer sending char e code shift false packer sending char s code shift false packer sending char e code shift false packer sending char e code shift false packer sending char d code shift false packer sending char code shift false packer sending char c code shift false packer sending char f code shift false packer sending char g code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer sending char code shift false packer special code found sleeping one second packer special code found replacing with packer special code found sleeping one second packer waiting for ssh up to timeout ui vmware iso waiting for ssh to become available packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready packer opening new ssh session packer starting remote command esxcli formatter csv network vm list packer opening new ssh session packer starting remote command esxcli formatter csv network vm port list w packer error getting ssh address no interface on the vm has an ip address ready

0

9,329

2,615,144,893

IssuesEvent

2015-03-01 06:20:37

chrsmith/html5rocks

https://api.github.com/repos/chrsmith/html5rocks

closed

add fileAPI example

auto-migrated Milestone-2 playground Priority-Medium Type-Defect

``` corey hart submitted a fileapi example for the playground. let's add it in! ``` Original issue reported on code.google.com by `paulir...@google.com` on 28 Jul 2010 at 10:00

1.0

add fileAPI example - ``` corey hart submitted a fileapi example for the playground. let's add it in! ``` Original issue reported on code.google.com by `paulir...@google.com` on 28 Jul 2010 at 10:00

defect

add fileapi example corey hart submitted a fileapi example for the playground let s add it in original issue reported on code google com by paulir google com on jul at

1

24,106

3,917,070,253

IssuesEvent

2016-04-21 06:23:36

irnawansuprapti/openbiz-cubi

https://api.github.com/repos/irnawansuprapti/openbiz-cubi

closed

muscles 56

auto-migrated Priority-Medium spam Type-Defect

``` To avoid such fate, start working on a good plan. You are not told to go out and buy a long term care insurance (LTCI) policy or a hybrid life insurance policy with LTC rider this very instant. You are simply advised to be more conscious of your health. You may have an hourglass figure or muscles in the right places but how are your internal organs? Take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle. http://www.skinphysiciantips.com/rapid-repair-eye-serum/ ``` Original issue reported on code.google.com by `OliverV...@gmail.com` on 16 Apr 2015 at 10:08

1.0

muscles 56 - ``` To avoid such fate, start working on a good plan. You are not told to go out and buy a long term care insurance (LTCI) policy or a hybrid life insurance policy with LTC rider this very instant. You are simply advised to be more conscious of your health. You may have an hourglass figure or muscles in the right places but how are your internal organs? Take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle. http://www.skinphysiciantips.com/rapid-repair-eye-serum/ ``` Original issue reported on code.google.com by `OliverV...@gmail.com` on 16 Apr 2015 at 10:08

defect

muscles to avoid such fate start working on a good plan you are not told to go out and buy a long term care insurance ltci policy or a hybrid life insurance policy with ltc rider this very instant you are simply advised to be more conscious of your health you may have an hourglass figure or muscles in the right places but how are your internal organs take time to visit your doctor and change what needs to be changed in your diet and overall lifestyle original issue reported on code google com by oliverv gmail com on apr at

1

81,574

7,786,660,956

IssuesEvent

2018-06-06 19:42:17

gomods/athens

https://api.github.com/repos/gomods/athens

closed

Tests don't run locally

athens good first issue olympus testing

A few things: - I run `docker-compose -p athenstest up -d` to launch all services that tests depend on - I run `make test` and it runs `go test ./...` - it should instead run `buffalo test` on the buffalo apps (`cmd/proxy` and `cmd/olympus`) - I get this error: ```console [~/gocode/src/github.com/gomods/athens] aaschles $ make test cd cmd/proxy && buffalo test [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF Usage: buffalo test [flags] Flags: -h, --help help for test ERRO[0000] Error: error creating MySQL database olympusdb: driver: bad connection make: *** [test] Error 255 ``` I think there will be other errors that come up after this one gets fixed

1.0

Tests don't run locally - A few things: - I run `docker-compose -p athenstest up -d` to launch all services that tests depend on - I run `make test` and it runs `go test ./...` - it should instead run `buffalo test` on the buffalo apps (`cmd/proxy` and `cmd/olympus`) - I get this error: ```console [~/gocode/src/github.com/gomods/athens] aaschles $ make test cd cmd/proxy && buffalo test [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF [mysql] 2018/06/06 11:27:43 packets.go:36: unexpected EOF Usage: buffalo test [flags] Flags: -h, --help help for test ERRO[0000] Error: error creating MySQL database olympusdb: driver: bad connection make: *** [test] Error 255 ``` I think there will be other errors that come up after this one gets fixed

non_defect

tests don t run locally a few things i run docker compose p athenstest up d to launch all services that tests depend on i run make test and it runs go test it should instead run buffalo test on the buffalo apps cmd proxy and cmd olympus i get this error console aaschles make test cd cmd proxy buffalo test packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof packets go unexpected eof usage buffalo test flags h help help for test erro error error creating mysql database olympusdb driver bad connection make error i think there will be other errors that come up after this one gets fixed

0

346,777

10,419,705,196

IssuesEvent

2019-09-15 18:31:50

LunarWatcher/AdventureLandCpp

https://api.github.com/repos/LunarWatcher/AdventureLandCpp

closed

Critical: replace Poco

priority:high

Poco works like a charm on Linux, but on Windows with MinGW, it's a different story. It injects incompatible libraries (attempts to link `-lCrypt32.lib` - `-lcrypt32` (used by a different library) is fine, but the `.lib` ending breaks it), and I can't fix it. It probably works fine on full-native Windows, My current plan is to switch over to [whoshuu/cpr](https://github.com/whoshuu/cpr) (through [conan-cpr](https://github.com/DEGoodmanWilson/conan-cpr)), which relies on cURL (fortunately available through Conan). One major advantage with changing, beyond potentially better support for Windows, is that cURL and CPR is **considerably** lighter than Poco. This is especially noticeable on devices with little resources available (such as the Raspberry Pi)

1.0

Critical: replace Poco - Poco works like a charm on Linux, but on Windows with MinGW, it's a different story. It injects incompatible libraries (attempts to link `-lCrypt32.lib` - `-lcrypt32` (used by a different library) is fine, but the `.lib` ending breaks it), and I can't fix it. It probably works fine on full-native Windows, My current plan is to switch over to [whoshuu/cpr](https://github.com/whoshuu/cpr) (through [conan-cpr](https://github.com/DEGoodmanWilson/conan-cpr)), which relies on cURL (fortunately available through Conan). One major advantage with changing, beyond potentially better support for Windows, is that cURL and CPR is **considerably** lighter than Poco. This is especially noticeable on devices with little resources available (such as the Raspberry Pi)

non_defect

critical replace poco poco works like a charm on linux but on windows with mingw it s a different story it injects incompatible libraries attempts to link lib used by a different library is fine but the lib ending breaks it and i can t fix it it probably works fine on full native windows my current plan is to switch over to through which relies on curl fortunately available through conan one major advantage with changing beyond potentially better support for windows is that curl and cpr is considerably lighter than poco this is especially noticeable on devices with little resources available such as the raspberry pi

0

32,733

6,905,571,158

IssuesEvent

2017-11-27 07:49:50

hazelcast/hazelcast-jet

https://api.github.com/repos/hazelcast/hazelcast-jet

closed

PeekWrappedP obscures actual class of the processor

core defect

When logging using PeekWrappedP it obscures the class of the actual processor: ```16:05:29,650 INFO || - [com.hazelcast.jet.impl.processor.PeekWrappedP.groupByKey.cd6373be.stage2#0] hz._hzInstance_1_jet.jet.cooperative.thread-1 - [10.0.1.3]:5701 [jet] [0.6-SNAPSHOT] Output to 0: accusers=6```

1.0

PeekWrappedP obscures actual class of the processor - When logging using PeekWrappedP it obscures the class of the actual processor: ```16:05:29,650 INFO || - [com.hazelcast.jet.impl.processor.PeekWrappedP.groupByKey.cd6373be.stage2#0] hz._hzInstance_1_jet.jet.cooperative.thread-1 - [10.0.1.3]:5701 [jet] [0.6-SNAPSHOT] Output to 0: accusers=6```

defect

peekwrappedp obscures actual class of the processor when logging using peekwrappedp it obscures the class of the actual processor info hz hzinstance jet jet cooperative thread output to accusers

1

330,266

24,253,503,008

IssuesEvent

2022-09-27 15:49:39

nebari-dev/nebari-docs

https://api.github.com/repos/nebari-dev/nebari-docs

opened

[DOC] - Security Overview and best practices

area: documentation 📖

### Preliminary Checks - [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions ### Summary [Notion Page](https://www.notion.so/quansightlabs/Security-overview-and-best-practices-86376fd95d5f4395b6648647ad51dedb) ### Steps to Resolve this Issue 1. 2. 3. ...

1.0

[DOC] - Security Overview and best practices - ### Preliminary Checks - [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions ### Summary [Notion Page](https://www.notion.so/quansightlabs/Security-overview-and-best-practices-86376fd95d5f4395b6648647ad51dedb) ### Steps to Resolve this Issue 1. 2. 3. ...

non_defect

security overview and best practices preliminary checks this issue is not a question feature request rfc or anything other than a bug report please post those things in github discussions summary steps to resolve this issue

0

22,234

3,619,269,925

IssuesEvent

2016-02-08 15:26:05

pavva94/snake-os

https://api.github.com/repos/pavva94/snake-os

closed

SNAKE OS does NOT have OPKG at all!

auto-migrated Priority-Medium Type-Defect

``` When i log into SNAKE, and go to services, i can see: DDNS FTP Samba SFTP/SSH Swapfile Syslog telnet transmission webserver that's it! and there is no OPKG there! what can i do? I use: SNAKE OS V1.3.2 (20101130) Kernel version: 2.6.16-gazineu thanks ``` Original issue reported on code.google.com by `ez2...@gmail.com` on 26 Jun 2013 at 11:13 Attachments: * [snake.jpg](https://storage.googleapis.com/google-code-attachments/snake-os/issue-364/comment-0/snake.jpg)

1.0

SNAKE OS does NOT have OPKG at all! - ``` When i log into SNAKE, and go to services, i can see: DDNS FTP Samba SFTP/SSH Swapfile Syslog telnet transmission webserver that's it! and there is no OPKG there! what can i do? I use: SNAKE OS V1.3.2 (20101130) Kernel version: 2.6.16-gazineu thanks ``` Original issue reported on code.google.com by `ez2...@gmail.com` on 26 Jun 2013 at 11:13 Attachments: * [snake.jpg](https://storage.googleapis.com/google-code-attachments/snake-os/issue-364/comment-0/snake.jpg)

defect

snake os does not have opkg at all when i log into snake and go to services i can see ddns ftp samba sftp ssh swapfile syslog telnet transmission webserver that s it and there is no opkg there what can i do i use snake os kernel version gazineu thanks original issue reported on code google com by gmail com on jun at attachments

1

224,447

17,188,607,933

IssuesEvent

2021-07-16 07:42:24

numpy/numpy

https://api.github.com/repos/numpy/numpy

closed

DOC: There is no easy way to find the NumPy PDF docs.

04 - Documentation

They are located at `https://numpy.org/doc/`, but there is no visible link to that page.

1.0

DOC: There is no easy way to find the NumPy PDF docs. - They are located at `https://numpy.org/doc/`, but there is no visible link to that page.

non_defect

doc there is no easy way to find the numpy pdf docs they are located at but there is no visible link to that page

0

62,278

17,023,888,031

IssuesEvent

2021-07-03 04:22:58

tomhughes/trac-tickets

https://api.github.com/repos/tomhughes/trac-tickets

closed

Website does not show the location of the note being viewed.

Component: website Priority: minor Resolution: fixed Type: defect

**[Submitted to the original trac issue database at 12.06pm, Sunday, 1st December 2013]** Since the website redesign the map component no longer focuses on the location of the note when opened from an RSS feed. This bug makes it difficult for mappers who monitor their local area and triage note reports. Steps to reproduce: 1. Generate a notes RSS feed (e.g. http://api.openstreetmap.org/api/0.6/notes/feed?bbox=-1.717,50.772,-0.748,51.236 ) 2. Click on one of the feed entries (e.g. http://api.openstreetmap.org/note/81260#c158974 ) Expected results: Webpage loads showing a sidebar containing note details and the map focused on the location of the note. Actual results: Webpage shows sidebar containing note detail and the map component is focused on the last viewed location.

1.0

Website does not show the location of the note being viewed. - **[Submitted to the original trac issue database at 12.06pm, Sunday, 1st December 2013]** Since the website redesign the map component no longer focuses on the location of the note when opened from an RSS feed. This bug makes it difficult for mappers who monitor their local area and triage note reports. Steps to reproduce: 1. Generate a notes RSS feed (e.g. http://api.openstreetmap.org/api/0.6/notes/feed?bbox=-1.717,50.772,-0.748,51.236 ) 2. Click on one of the feed entries (e.g. http://api.openstreetmap.org/note/81260#c158974 ) Expected results: Webpage loads showing a sidebar containing note details and the map focused on the location of the note. Actual results: Webpage shows sidebar containing note detail and the map component is focused on the last viewed location.

defect

website does not show the location of the note being viewed since the website redesign the map component no longer focuses on the location of the note when opened from an rss feed this bug makes it difficult for mappers who monitor their local area and triage note reports steps to reproduce generate a notes rss feed e g click on one of the feed entries e g expected results webpage loads showing a sidebar containing note details and the map focused on the location of the note actual results webpage shows sidebar containing note detail and the map component is focused on the last viewed location

1

132,615

10,760,532,335

IssuesEvent

2019-10-31 18:47:56

PulpQE/pulp-smash

https://api.github.com/repos/PulpQE/pulp-smash

closed

Verify that duplicate userid is not allowed

Issue Type: Test Case pulp 2 - closed - wontfix

https://pulp.plan.io/issues/2957 Assert user create does not allow creation of duplicate userid.

1.0

Verify that duplicate userid is not allowed - https://pulp.plan.io/issues/2957 Assert user create does not allow creation of duplicate userid.

non_defect

verify that duplicate userid is not allowed assert user create does not allow creation of duplicate userid

0

95,006

16,064,579,031

IssuesEvent

2021-04-23 17:00:47

NixOS/nixpkgs

https://api.github.com/repos/NixOS/nixpkgs

opened

Vulnerability roundup 101: gitlab-13.8.6: 6 advisories [7.5]

1.severity: security

[search](https://search.nix.gsc.io/?q=gitlab&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gitlab+in%3Apath&type=Code) * [ ] [CVE-2021-22200](https://nvd.nist.gov/vuln/detail/CVE-2021-22200) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22203](https://nvd.nist.gov/vuln/detail/CVE-2021-22203) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22196](https://nvd.nist.gov/vuln/detail/CVE-2021-22196) CVSSv3=5.4 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22197](https://nvd.nist.gov/vuln/detail/CVE-2021-22197) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22198](https://nvd.nist.gov/vuln/detail/CVE-2021-22198) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22202](https://nvd.nist.gov/vuln/detail/CVE-2021-22202) CVSSv3=4.3 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: c7e905b6a97; nixos-unstable: f5e8bdd07d1. Cc @fpletz Cc @globin Cc @krav Cc @talyz

True

Vulnerability roundup 101: gitlab-13.8.6: 6 advisories [7.5] - [search](https://search.nix.gsc.io/?q=gitlab&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gitlab+in%3Apath&type=Code) * [ ] [CVE-2021-22200](https://nvd.nist.gov/vuln/detail/CVE-2021-22200) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22203](https://nvd.nist.gov/vuln/detail/CVE-2021-22203) CVSSv3=7.5 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22196](https://nvd.nist.gov/vuln/detail/CVE-2021-22196) CVSSv3=5.4 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22197](https://nvd.nist.gov/vuln/detail/CVE-2021-22197) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22198](https://nvd.nist.gov/vuln/detail/CVE-2021-22198) CVSSv3=4.3 (nixos-20.09, nixos-unstable) * [ ] [CVE-2021-22202](https://nvd.nist.gov/vuln/detail/CVE-2021-22202) CVSSv3=4.3 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: c7e905b6a97; nixos-unstable: f5e8bdd07d1. Cc @fpletz Cc @globin Cc @krav Cc @talyz

non_defect

vulnerability roundup gitlab advisories nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable nixos nixos unstable scanned versions nixos nixos unstable cc fpletz cc globin cc krav cc talyz

0

37,987

8,628,279,534

IssuesEvent

2018-11-21 16:58:00

vrapper/vrapper

https://api.github.com/repos/vrapper/vrapper

closed

Commands (: and /) trigger file corruption through macros

Defect

In Eclipse 4.9 (latest release currently) pressing the colon key in the default Eclipse editor to run a command behaves strangely by inserting (random?) text into the file but not showing the command popup. The slash key to search for text is also showing the popup only on second press. Especially the first one makes Vrapper unusable.

1.0

Commands (: and /) trigger file corruption through macros - In Eclipse 4.9 (latest release currently) pressing the colon key in the default Eclipse editor to run a command behaves strangely by inserting (random?) text into the file but not showing the command popup. The slash key to search for text is also showing the popup only on second press. Especially the first one makes Vrapper unusable.

defect

commands and trigger file corruption through macros in eclipse latest release currently pressing the colon key in the default eclipse editor to run a command behaves strangely by inserting random text into the file but not showing the command popup the slash key to search for text is also showing the popup only on second press especially the first one makes vrapper unusable

1

23,269

3,785,178,165

IssuesEvent

2016-03-20 10:21:48

pearu/pyvtk

https://api.github.com/repos/pearu/pyvtk

closed

Non integer mesh points

auto-migrated Priority-Medium Type-Defect

``` What steps will reproduce the problem? 1. Write a mesh ( in my case unstructured) with 'float' mesh points 2. Output VTK file will state that the data is still of type 'int' Looking at the source I see that 'int' is hard coded in UnstructuredGrid.py in line 100 I recommend placing a switch that detects whether the mesh coordinates are of type 'int' or 'float' then write the correct string. I've attached a sample VTK written by pyvtk where the issue may be seen (I left it in ASCII format). The error is on line 5 of the sample newTest.vtk ``` Original issue reported on code.google.com by `komperda...@gmail.com` on 25 Aug 2012 at 9:48 Attachments: * [newTest.vtk](https://storage.googleapis.com/google-code-attachments/pyvtk/issue-2/comment-0/newTest.vtk)

1.0

Non integer mesh points - ``` What steps will reproduce the problem? 1. Write a mesh ( in my case unstructured) with 'float' mesh points 2. Output VTK file will state that the data is still of type 'int' Looking at the source I see that 'int' is hard coded in UnstructuredGrid.py in line 100 I recommend placing a switch that detects whether the mesh coordinates are of type 'int' or 'float' then write the correct string. I've attached a sample VTK written by pyvtk where the issue may be seen (I left it in ASCII format). The error is on line 5 of the sample newTest.vtk ``` Original issue reported on code.google.com by `komperda...@gmail.com` on 25 Aug 2012 at 9:48 Attachments: * [newTest.vtk](https://storage.googleapis.com/google-code-attachments/pyvtk/issue-2/comment-0/newTest.vtk)

defect

non integer mesh points what steps will reproduce the problem write a mesh in my case unstructured with float mesh points output vtk file will state that the data is still of type int looking at the source i see that int is hard coded in unstructuredgrid py in line i recommend placing a switch that detects whether the mesh coordinates are of type int or float then write the correct string i ve attached a sample vtk written by pyvtk where the issue may be seen i left it in ascii format the error is on line of the sample newtest vtk original issue reported on code google com by komperda gmail com on aug at attachments

1

46,497

13,055,921,526

IssuesEvent

2020-07-30 03:07:38

icecube-trac/tix2

https://api.github.com/repos/icecube-trac/tix2

opened

paraboloid - coverage of private interfaces is weak (Trac #1305)

Incomplete Migration Migrated from Trac combo reconstruction defect

Migrated from https://code.icecube.wisc.edu/ticket/1305 ```json { "status": "closed", "changetime": "2016-02-10T10:59:05", "description": "a serialization and a \"known failure\" test will quickly bump coverage", "reporter": "nega", "cc": "", "resolution": "fixed", "_ts": "1455101945934200", "component": "combo reconstruction", "summary": "paraboloid - coverage of private interfaces is weak", "priority": "normal", "keywords": "", "time": "2015-08-28T23:07:43", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```

1.0

paraboloid - coverage of private interfaces is weak (Trac #1305) - Migrated from https://code.icecube.wisc.edu/ticket/1305 ```json { "status": "closed", "changetime": "2016-02-10T10:59:05", "description": "a serialization and a \"known failure\" test will quickly bump coverage", "reporter": "nega", "cc": "", "resolution": "fixed", "_ts": "1455101945934200", "component": "combo reconstruction", "summary": "paraboloid - coverage of private interfaces is weak", "priority": "normal", "keywords": "", "time": "2015-08-28T23:07:43", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```

defect

paraboloid coverage of private interfaces is weak trac migrated from json status closed changetime description a serialization and a known failure test will quickly bump coverage reporter nega cc resolution fixed ts component combo reconstruction summary paraboloid coverage of private interfaces is weak priority normal keywords time milestone owner kjmeagher type defect

1

130,951

18,214,175,323

IssuesEvent

2021-09-30 00:39:35

ghc-dev/Brenda-Jacobs

https://api.github.com/repos/ghc-dev/Brenda-Jacobs

closed

CVE-2017-16119 (High) detected in fresh-0.2.4.tgz - autoclosed

security vulnerability

## CVE-2017-16119 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - fresh-0.2.4.tgz</summary> HTTP response freshness testing Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz">https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz</a> Path to dependency file: Brenda-Jacobs/package.json Path to vulnerable library: Brenda-Jacobs/node_modules/fresh/package.json Dependency Hierarchy: - send-0.11.1.tgz (Root Library) - :x: **fresh-0.2.4.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/ghc-dev/Brenda-Jacobs/commit/8b710e312525a6b8c5c2de0698af2c35e0a6c1f7">8b710e312525a6b8c5c2de0698af2c35e0a6c1f7</a> Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119>CVE-2017-16119</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (7.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a> Release Date: 2018-06-07 Fix Resolution: fresh - 0.5.2 </details>

True

CVE-2017-16119 (High) detected in fresh-0.2.4.tgz - autoclosed - ## CVE-2017-16119 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - fresh-0.2.4.tgz</summary> HTTP response freshness testing Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz">https://registry.npmjs.org/fresh/-/fresh-0.2.4.tgz</a> Path to dependency file: Brenda-Jacobs/package.json Path to vulnerable library: Brenda-Jacobs/node_modules/fresh/package.json Dependency Hierarchy: - send-0.11.1.tgz (Root Library) - :x: **fresh-0.2.4.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/ghc-dev/Brenda-Jacobs/commit/8b710e312525a6b8c5c2de0698af2c35e0a6c1f7">8b710e312525a6b8c5c2de0698af2c35e0a6c1f7</a> Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16119>CVE-2017-16119</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (7.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a> Release Date: 2018-06-07 Fix Resolution: fresh - 0.5.2 </details>

non_defect

cve high detected in fresh tgz autoclosed cve high severity vulnerability vulnerable library fresh tgz http response freshness testing library home page a href path to dependency file brenda jacobs package json path to vulnerable library brenda jacobs node modules fresh package json dependency hierarchy send tgz root library x fresh tgz vulnerable library found in head commit a href found in base branch master vulnerability details fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution fresh isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree send fresh isminimumfixversionavailable true minimumfixversion fresh basebranches vulnerabilityidentifier cve vulnerabilitydetails fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition vulnerabilityurl

0

27,546

5,047,520,154

IssuesEvent

2016-12-20 09:42:27

JohnAustinDev/osis-converters

https://api.github.com/repos/JohnAustinDev/osis-converters

closed

.conf Feature settings

auto-migrated Priority-High Type-Defect

``` Some .conf Feature settings (such as Glossary and Images) need to be added when appropriate. ``` Original issue reported on code.google.com by `gpl.prog...@gmail.com` on 2 Aug 2013 at 5:44

1.0

.conf Feature settings - ``` Some .conf Feature settings (such as Glossary and Images) need to be added when appropriate. ``` Original issue reported on code.google.com by `gpl.prog...@gmail.com` on 2 Aug 2013 at 5:44

defect

conf feature settings some conf feature settings such as glossary and images need to be added when appropriate original issue reported on code google com by gpl prog gmail com on aug at

1

98,237

20,622,864,988

IssuesEvent

2022-03-07 19:13:10

withfig/fig

https://api.github.com/repos/withfig/fig

opened

CLI not working

bug codebase:cli placeholder

Most of the time this is really an issue with something else If the Fig CLI isn't working, please comment relevant info here! * Run `fig diagnostic` if you can * Run `fig doctor` if you can * Share your $PATH * Anything else that might help

1.0

CLI not working - Most of the time this is really an issue with something else If the Fig CLI isn't working, please comment relevant info here! * Run `fig diagnostic` if you can * Run `fig doctor` if you can * Share your $PATH * Anything else that might help

non_defect

cli not working most of the time this is really an issue with something else if the fig cli isn t working please comment relevant info here run fig diagnostic if you can run fig doctor if you can share your path anything else that might help

0

33,190

27,292,763,665

IssuesEvent

2023-02-23 17:47:06

google/site-kit-wp

https://api.github.com/repos/google/site-kit-wp

closed

Add support for Site Kit Service's playground environment

P0 Type: Infrastructure

Site Kit supports overriding the Site Kit Service base URL to use via the `GOOGLESITEKIT_PROXY_URL` (only used for internal debugging and testing). However that constant only works with an allowlist of URLs. Since Site Kit Service now has a new "playground" environment called `site-kit-local`, we will need to add support for it as well, in addition to the existing staging environment called `site-kit-dev`. --------------- _Do not alter or remove anything below. The following sections will be managed by moderators only._ ## Acceptance criteria * It should be possible to use the value `https://site-kit-local.appspot.com` in the `GOOGLESITEKIT_PROXY_URL` constant. ## Implementation Brief * Add new `DEVELOPMENT_BASE_URL` constant to `Google_Proxy` class with the URL from the ACs. * Modify `Google_Proxy::url()` to also allow that value when provided in the `GOOGLESITEKIT_PROXY_URL` constant. ### Test Coverage * N/A ## QA Brief * With Site Kit currently not being set up (e.g. after a reset), set the constant `GOOGLESITEKIT_PROXY_URL` to `https://site-kit-local.appspot.com`, e.g. in your `wp-config.php`. * Verify that when starting the setup flow, you land on a URL that starts with `https://site-kit-local.appspot.com`. * It is not necessary for QA of this issue to complete the setup flow. There is a chance that that environment is not fully working yet, which is okay for the scope of this issue. ## Changelog entry * N/A

1.0

Add support for Site Kit Service's playground environment - Site Kit supports overriding the Site Kit Service base URL to use via the `GOOGLESITEKIT_PROXY_URL` (only used for internal debugging and testing). However that constant only works with an allowlist of URLs. Since Site Kit Service now has a new "playground" environment called `site-kit-local`, we will need to add support for it as well, in addition to the existing staging environment called `site-kit-dev`. --------------- _Do not alter or remove anything below. The following sections will be managed by moderators only._ ## Acceptance criteria * It should be possible to use the value `https://site-kit-local.appspot.com` in the `GOOGLESITEKIT_PROXY_URL` constant. ## Implementation Brief * Add new `DEVELOPMENT_BASE_URL` constant to `Google_Proxy` class with the URL from the ACs. * Modify `Google_Proxy::url()` to also allow that value when provided in the `GOOGLESITEKIT_PROXY_URL` constant. ### Test Coverage * N/A ## QA Brief * With Site Kit currently not being set up (e.g. after a reset), set the constant `GOOGLESITEKIT_PROXY_URL` to `https://site-kit-local.appspot.com`, e.g. in your `wp-config.php`. * Verify that when starting the setup flow, you land on a URL that starts with `https://site-kit-local.appspot.com`. * It is not necessary for QA of this issue to complete the setup flow. There is a chance that that environment is not fully working yet, which is okay for the scope of this issue. ## Changelog entry * N/A

non_defect

add support for site kit service s playground environment site kit supports overriding the site kit service base url to use via the googlesitekit proxy url only used for internal debugging and testing however that constant only works with an allowlist of urls since site kit service now has a new playground environment called site kit local we will need to add support for it as well in addition to the existing staging environment called site kit dev do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria it should be possible to use the value in the googlesitekit proxy url constant implementation brief add new development base url constant to google proxy class with the url from the acs modify google proxy url to also allow that value when provided in the googlesitekit proxy url constant test coverage n a qa brief with site kit currently not being set up e g after a reset set the constant googlesitekit proxy url to e g in your wp config php verify that when starting the setup flow you land on a url that starts with it is not necessary for qa of this issue to complete the setup flow there is a chance that that environment is not fully working yet which is okay for the scope of this issue changelog entry n a

0

230,953

7,621,829,576

IssuesEvent

2018-05-03 09:54:35

InFact-coop/infactcoop.com

https://api.github.com/repos/InFact-coop/infactcoop.com

opened

Our Story section

Priority-2 Section T4h

In which we talk a bit about us and how we came to fruition, and the kind of projects (charity, small business, public sector) we like to work on, and then link to a different view outlining these things in more detail.

1.0

Our Story section - In which we talk a bit about us and how we came to fruition, and the kind of projects (charity, small business, public sector) we like to work on, and then link to a different view outlining these things in more detail.

non_defect

our story section in which we talk a bit about us and how we came to fruition and the kind of projects charity small business public sector we like to work on and then link to a different view outlining these things in more detail

0

52,293

13,218,998,762

IssuesEvent

2020-08-17 09:42:18

hazelcast/hazelcast

https://api.github.com/repos/hazelcast/hazelcast

opened

Near Cache is not controlled by Split Brain Protection

Type: Defect

**Describe the bug** When split brain isn't happened, near cache caches correct data for service. Then split brain happens, the service which caches by near cache is still returning correct response. **Expected behavior** when split brain has happened, all service shuold be forbidden. **To Reproduce** Steps to reproduce the behavior: 1. split brain not happens 2. near cache caches the correct response to service 3. split brain happens 4. try to request the service on step 2 **Additional context** - in spring boot project，use embed hazelcast 4.0.1 - set Near Cache - set Split Brain Protection - set SplitBrainProtectionOn.READ_WRITE - use MemberCountSpitBrainProtectionFuntion - JDK 8

1.0

Near Cache is not controlled by Split Brain Protection -  **Describe the bug** When split brain isn't happened, near cache caches correct data for service. Then split brain happens, the service which caches by near cache is still returning correct response. **Expected behavior** when split brain has happened, all service shuold be forbidden. **To Reproduce** Steps to reproduce the behavior: 1. split brain not happens 2. near cache caches the correct response to service 3. split brain happens 4. try to request the service on step 2 **Additional context** - in spring boot project，use embed hazelcast 4.0.1 - set Near Cache - set Split Brain Protection - set SplitBrainProtectionOn.READ_WRITE - use MemberCountSpitBrainProtectionFuntion - JDK 8

defect

near cache is not controlled by split brain protection thanks for reporting your issue please share with us the following information to help us resolve your issue quickly and efficiently describe the bug when split brain isn t happened near cache caches correct data for service then split brain happens the service which caches by near cache is still returning correct response expected behavior when split brain has happened all service shuold be forbidden to reproduce steps to reproduce the behavior split brain not happens near cache caches the correct response to service split brain happens try to request the service on step additional context in spring boot project，use embed hazelcast set near cache set split brain protection set splitbrainprotectionon read write use membercountspitbrainprotectionfuntion jdk add any other context about the problem here common details that we re often interested in detailed description of the steps to reproduce your issue logs and stack traces if available hazelcast version that you use e g also specify whether it is a minor release or the latest snapshot if available integration module versions e g tomcat jetty spring hibernate also include their detailed configuration information such as web xml hibernate configuration and context xml for spring cluster size i e the number of hazelcast cluster members number of the clients version of java it is also helpful to mention the jvm parameters operating system if it is linux kernel version is helpful unit test with the hazelcast xml file if you could include a unit test which reproduces your issue we would be grateful

1

1,529

2,603,967,017

IssuesEvent

2015-02-24 18:59:17

chrsmith/nishazi6

https://api.github.com/repos/chrsmith/nishazi6

opened

沈阳龟头上长有白色疙瘩

auto-migrated Priority-Medium Type-Defect

``` 沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓TEL：02 4-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治療� ��位于沈陽市沈河區二緯路32號。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 ``` ----- Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:08

1.0

沈阳龟头上长有白色疙瘩 - ``` 沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓TEL：02 4-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治療� ��位于沈陽市沈河區二緯路32號。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 ``` ----- Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:08

defect

沈阳龟头上长有白色疙瘩沈阳龟头上长有白色疙瘩〓沈陽軍區政治部醫院性病〓tel：〓， � �� 。是一所與新中國同建立共輝� ��的歷史悠久、設備精良、技術權威、專家云集，是預防、保健、醫療、科研康復為一體的綜合性醫院。是國家首批公立�� 等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大學� ��東南大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立集�� 二等功。 original issue reported on code google com by gmail com on jun at

1

18,440

3,061,246,092

IssuesEvent

2015-08-15 10:04:17

google/mozc

https://api.github.com/repos/google/mozc

closed

Preedit and candidate changes buffer modification flag.

auto-migrated Priority-Medium Type-Defect

``` What steps will reproduce the problem? 1. setup mozc.el under emacs. 2. activate mozc, and input something in preedit on unmodified buffer. 3. push ESC for clear preedit string. What is the expected output? The buffer modification flag isn't changed. (keep unmodified) What do you see instead? The buffer modification flag is turned on. What version of the product are you using? On what operating system? 2.16.1924.102 Please provide any additional information below. A propose patch is attached. ``` Original issue reported on code.google.com by `d588...@gmail.com` on 24 Nov 2014 at 11:14 Attachments: * [mozc-el-diff](https://storage.googleapis.com/google-code-attachments/mozc/issue-254/comment-0/mozc-el-diff)

1.0

Preedit and candidate changes buffer modification flag. - ``` What steps will reproduce the problem? 1. setup mozc.el under emacs. 2. activate mozc, and input something in preedit on unmodified buffer. 3. push ESC for clear preedit string. What is the expected output? The buffer modification flag isn't changed. (keep unmodified) What do you see instead? The buffer modification flag is turned on. What version of the product are you using? On what operating system? 2.16.1924.102 Please provide any additional information below. A propose patch is attached. ``` Original issue reported on code.google.com by `d588...@gmail.com` on 24 Nov 2014 at 11:14 Attachments: * [mozc-el-diff](https://storage.googleapis.com/google-code-attachments/mozc/issue-254/comment-0/mozc-el-diff)

defect

preedit and candidate changes buffer modification flag what steps will reproduce the problem setup mozc el under emacs activate mozc and input something in preedit on unmodified buffer push esc for clear preedit string what is the expected output the buffer modification flag isn t changed keep unmodified what do you see instead the buffer modification flag is turned on what version of the product are you using on what operating system please provide any additional information below a propose patch is attached original issue reported on code google com by gmail com on nov at attachments

1

325,976

27,971,796,196

IssuesEvent

2023-03-25 04:54:39

cockroachdb/cockroach

https://api.github.com/repos/cockroachdb/cockroach

opened

pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test: TestLogic_propagate_input_ordering failed

C-test-failure O-robot branch-master

pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test.TestLogic_propagate_input_ordering [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=artifacts#/) on master @ [9a0d4932cd634034070a7e5ca91559e8d67d8fbe](https://github.com/cockroachdb/cockroach/commits/9a0d4932cd634034070a7e5ca91559e8d67d8fbe): Fatal error: ``` panic: test timed out after 59m55s ``` Stack: ``` goroutine 46816 [running]: testing.(*M).startAlarm.func1() GOROOT/src/testing/testing.go:2036 +0x88 created by time.goFunc GOROOT/src/time/sleep.go:176 +0x38 ``` <details><summary>Log preceding fatal error</summary> ``` * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x40041386c0?, 0x5d59440?}}, 0x40019c1f98) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4697fc0?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38570 [select, 2 minutes]: * github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue.func2() * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:388 +0x7c * created by github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:385 +0x30c * * goroutine 39107 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x4005a2e510}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4000729500?, 0x0?}}, 0x400001a798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x400001a758?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38610 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x400974e030}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4007d7cae6?, 0x100000000000000?}}, 0x4001398798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4002c5b330?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 41560 [select, 2 minutes]: * database/sql.(*DB).connectionOpener(0x4003f58750, {0x5d59398, 0x40050e8300}) * GOROOT/src/database/sql/sql.go:1224 +0x80 * created by database/sql.OpenDB * GOROOT/src/database/sql/sql.go:792 +0x184 * * goroutine 38630 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x4002f5aa50}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x5d59401?, 0x0?}}, 0x40013e4798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4006cb1380?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * ``` </details> <details><summary>Help</summary> See also: [How To Investigate a Go Test Failure $internal$](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </details> /cc @cockroachdb/sql-queries [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestLogic_propagate_input_ordering.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)

1.0

pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test: TestLogic_propagate_input_ordering failed - pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test.TestLogic_propagate_input_ordering [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/9243838?buildTab=artifacts#/) on master @ [9a0d4932cd634034070a7e5ca91559e8d67d8fbe](https://github.com/cockroachdb/cockroach/commits/9a0d4932cd634034070a7e5ca91559e8d67d8fbe): Fatal error: ``` panic: test timed out after 59m55s ``` Stack: ``` goroutine 46816 [running]: testing.(*M).startAlarm.func1() GOROOT/src/testing/testing.go:2036 +0x88 created by time.goFunc GOROOT/src/time/sleep.go:176 +0x38 ``` <details><summary>Log preceding fatal error</summary> ``` * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x40041386c0?, 0x5d59440?}}, 0x40019c1f98) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4697fc0?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38570 [select, 2 minutes]: * github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue.func2() * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:388 +0x7c * created by github.com/cockroachdb/cockroach/pkg/util/admission.initWorkQueue * github.com/cockroachdb/cockroach/pkg/util/admission/work_queue.go:385 +0x30c * * goroutine 39107 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x4005a2e510}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4000729500?, 0x0?}}, 0x400001a798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x400001a758?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 38610 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x400974e030}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x4007d7cae6?, 0x100000000000000?}}, 0x4001398798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4002c5b330?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * goroutine 41560 [select, 2 minutes]: * database/sql.(*DB).connectionOpener(0x4003f58750, {0x5d59398, 0x40050e8300}) * GOROOT/src/database/sql/sql.go:1224 +0x80 * created by database/sql.OpenDB * GOROOT/src/database/sql/sql.go:792 +0x184 * * goroutine 38630 [chan receive, 2 minutes]: * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop.func1({0x5d59440, 0x4002f5aa50}) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:324 +0x80 * runtime/pprof.Do({0x5d593d0?, 0x4000232000?}, {{0x40004ba180?, 0x5d59401?, 0x0?}}, 0x40013e4798) * GOROOT/src/runtime/pprof/runtime.go:40 +0x80 * github.com/cockroachdb/pebble.(*tableCacheShard).releaseLoop(0x4006cb1380?) * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:322 +0x6c * created by github.com/cockroachdb/pebble.(*tableCacheShard).init * github.com/cockroachdb/pebble/external/com_github_cockroachdb_pebble/table_cache.go:314 +0xf0 * * ``` </details> <details><summary>Help</summary> See also: [How To Investigate a Go Test Failure $internal$](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </details> /cc @cockroachdb/sql-queries [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestLogic_propagate_input_ordering.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)

non_defect

pkg sql logictest tests fakedist vec off fakedist vec off test testlogic propagate input ordering failed pkg sql logictest tests fakedist vec off fakedist vec off test testlogic propagate input ordering with on master fatal error panic test timed out after stack goroutine testing m startalarm goroot src testing testing go created by time gofunc goroot src time sleep go log preceding fatal error runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine github com cockroachdb cockroach pkg util admission initworkqueue github com cockroachdb cockroach pkg util admission work queue go created by github com cockroachdb cockroach pkg util admission initworkqueue github com cockroachdb cockroach pkg util admission work queue go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go goroutine database sql db connectionopener goroot src database sql sql go created by database sql opendb goroot src database sql sql go goroutine github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go runtime pprof do goroot src runtime pprof runtime go github com cockroachdb pebble tablecacheshard releaseloop github com cockroachdb pebble external com github cockroachdb pebble table cache go created by github com cockroachdb pebble tablecacheshard init github com cockroachdb pebble external com github cockroachdb pebble table cache go help see also cc cockroachdb sql queries

0

69,557

22,494,962,494

IssuesEvent

2022-06-23 06:39:28

ankitpokhrel/jira-cli

https://api.github.com/repos/ankitpokhrel/jira-cli

closed

Assigning issue to self doesn't assign it

defect help wanted jira server

**Describe the bug**  Running the following command doesn't assign the issue to me, instead the user search opens up, in which I'm unfindable as well. ```sh jira issue assign "TICKET-CODE" "$(jira me)" ``` **Please provide following details** 1. JiraCLI Version: ``` (Version="0.1.1", GitCommit="6663763b44a2e5d328b551ae7d2f1a37d1e232ae", GoVersion="go1.17.2", BuildDate="2021-11-03"", Compiler="gc", Platform="darwin/amd64") ``` 2. Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation. ``` Jira Server v8.20.0 ``` 3. What operating system are you using? Also mention version. ``` macOS 12.0.1 ``` 4. What terminal are you using? Also mention version. ``` alacritty 0.9.0 (fed349a) ``` **To Reproduce** Steps to reproduce the behavior: 1. Run `jira issue assign "TICKET-CODE" "$(jira me)"` 2. Issue isn't assigned to you, user search is opened up 3. Probably a separate issue but no names past the initial cropped list are findable **Expected behavior**  The issue would be assigned to me. **Additional context**  Not that it's relevant here but I'm using the line in the following function: ```sh # Move an issue back to progress jmbk() { jira issue transition "$1" "Back To Progress" jira issue assign "$1" "$(jira me)" } ```

1.0

Assigning issue to self doesn't assign it - **Describe the bug**  Running the following command doesn't assign the issue to me, instead the user search opens up, in which I'm unfindable as well. ```sh jira issue assign "TICKET-CODE" "$(jira me)" ``` **Please provide following details** 1. JiraCLI Version: ``` (Version="0.1.1", GitCommit="6663763b44a2e5d328b551ae7d2f1a37d1e232ae", GoVersion="go1.17.2", BuildDate="2021-11-03"", Compiler="gc", Platform="darwin/amd64") ``` 2. Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation. ``` Jira Server v8.20.0 ``` 3. What operating system are you using? Also mention version. ``` macOS 12.0.1 ``` 4. What terminal are you using? Also mention version. ``` alacritty 0.9.0 (fed349a) ``` **To Reproduce** Steps to reproduce the behavior: 1. Run `jira issue assign "TICKET-CODE" "$(jira me)"` 2. Issue isn't assigned to you, user search is opened up 3. Probably a separate issue but no names past the initial cropped list are findable **Expected behavior**  The issue would be assigned to me. **Additional context**  Not that it's relevant here but I'm using the line in the following function: ```sh # Move an issue back to progress jmbk() { jira issue transition "$1" "Back To Progress" jira issue assign "$1" "$(jira me)" } ```

defect

assigning issue to self doesn t assign it describe the bug running the following command doesn t assign the issue to me instead the user search opens up in which i m unfindable as well sh jira issue assign ticket code jira me please provide following details jiracli version version gitcommit goversion builddate compiler gc platform darwin are you using jira cloud or on premise jira server also mention the version for on premise installation jira server what operating system are you using also mention version macos what terminal are you using also mention version alacritty to reproduce steps to reproduce the behavior run jira issue assign ticket code jira me issue isn t assigned to you user search is opened up probably a separate issue but no names past the initial cropped list are findable expected behavior the issue would be assigned to me additional context not that it s relevant here but i m using the line in the following function sh move an issue back to progress jmbk jira issue transition back to progress jira issue assign jira me

1

711,050

24,448,849,107

IssuesEvent

2022-10-06 20:33:47

pytorch/pytorch

https://api.github.com/repos/pytorch/pytorch

closed

Investigate binary validation failure nightly linux 3.9 cuda 11.6

high priority module: ci triaged

### 🐛 Describe the bug Failure: https://github.com/pytorch/builder/actions/runs/3018052016/jobs/4939894670 ``` done + conda run -p conda-env-3018052016 python3 ./test/smoke_test/smoke_test.py ERROR conda.cli.main_run:execute(41): `conda run python3 ./test/smoke_test/smoke_test.py` failed. (See above for error) Traceback (most recent call last): File "/root/work/builder/builder/./test/smoke_test/smoke_test.py", line 5, in <module> import torchaudio File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/__init__.py", line 1, in <module> from torchaudio import ( # noqa: F401 File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 103, in <module> _init_extension() File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 88, in _init_extension _load_lib("libtorchaudio") File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 51, in _load_lib torch.ops.load_library(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torch/_ops.py", line 481, in load_library ctypes.CDLL(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/ctypes/__init__.py", line 382, in __init__ self._handle = _dlopen(self._name, mode) OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory ``` ### Versions nightly 1.13 cc @ezyang @gchanan @zou3519 @seemethere @malfet @pytorch/pytorch-dev-infra @weiwangmeta

1.0

Investigate binary validation failure nightly linux 3.9 cuda 11.6 - ### 🐛 Describe the bug Failure: https://github.com/pytorch/builder/actions/runs/3018052016/jobs/4939894670 ``` done + conda run -p conda-env-3018052016 python3 ./test/smoke_test/smoke_test.py ERROR conda.cli.main_run:execute(41): `conda run python3 ./test/smoke_test/smoke_test.py` failed. (See above for error) Traceback (most recent call last): File "/root/work/builder/builder/./test/smoke_test/smoke_test.py", line 5, in <module> import torchaudio File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/__init__.py", line 1, in <module> from torchaudio import ( # noqa: F401 File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 103, in <module> _init_extension() File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 88, in _init_extension _load_lib("libtorchaudio") File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torchaudio/_extension.py", line 51, in _load_lib torch.ops.load_library(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/site-packages/torch/_ops.py", line 481, in load_library ctypes.CDLL(path) File "/root/work/builder/builder/conda-env-3018052016/lib/python3.9/ctypes/__init__.py", line 382, in __init__ self._handle = _dlopen(self._name, mode) OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory ``` ### Versions nightly 1.13 cc @ezyang @gchanan @zou3519 @seemethere @malfet @pytorch/pytorch-dev-infra @weiwangmeta

non_defect

investigate binary validation failure nightly linux cuda 🐛 describe the bug failure done conda run p conda env test smoke test smoke test py error conda cli main run execute conda run test smoke test smoke test py failed see above for error traceback most recent call last file root work builder builder test smoke test smoke test py line in import torchaudio file root work builder builder conda env lib site packages torchaudio init py line in from torchaudio import noqa file root work builder builder conda env lib site packages torchaudio extension py line in init extension file root work builder builder conda env lib site packages torchaudio extension py line in init extension load lib libtorchaudio file root work builder builder conda env lib site packages torchaudio extension py line in load lib torch ops load library path file root work builder builder conda env lib site packages torch ops py line in load library ctypes cdll path file root work builder builder conda env lib ctypes init py line in init self handle dlopen self name mode oserror libtorch cuda cpp so cannot open shared object file no such file or directory versions nightly cc ezyang gchanan seemethere malfet pytorch pytorch dev infra weiwangmeta

0

107,829

13,524,195,118

IssuesEvent

2020-09-15 11:09:18

nextcloud/desktop

https://api.github.com/repos/nextcloud/desktop

closed

3.0.1 new activity feed does not show filenames

design enhancement feature: :cloud: system tray feature: :zap: activity and :bell: notification

### Expected behaviour If I read an entry in the activity feed, I want to know which file caused the entry. ### Actual behaviour The feed does not show the file name. It displays the file name including the path (with sync folder as root), but the path is cut as it is to long for the feed. As it is cut at the end, the file name is not readable at all. There is also no baloon tooltip that shows the full path. ### Steps to reproduce 1. Open activity feed (click once on the task bar/info bar icon) 2. Look at any activity entry ### Client configuration Client version: 3.0.1 Operating system: Windows 10 OS language: German Installation path of client: C:\Program FIles\Nextcloud ### Logs As this is a design issue, logs do not make sense.

1.0

3.0.1 new activity feed does not show filenames - ### Expected behaviour If I read an entry in the activity feed, I want to know which file caused the entry. ### Actual behaviour The feed does not show the file name. It displays the file name including the path (with sync folder as root), but the path is cut as it is to long for the feed. As it is cut at the end, the file name is not readable at all. There is also no baloon tooltip that shows the full path. ### Steps to reproduce 1. Open activity feed (click once on the task bar/info bar icon) 2. Look at any activity entry ### Client configuration Client version: 3.0.1 Operating system: Windows 10 OS language: German Installation path of client: C:\Program FIles\Nextcloud ### Logs As this is a design issue, logs do not make sense.

non_defect

new activity feed does not show filenames expected behaviour if i read an entry in the activity feed i want to know which file caused the entry actual behaviour the feed does not show the file name it displays the file name including the path with sync folder as root but the path is cut as it is to long for the feed as it is cut at the end the file name is not readable at all there is also no baloon tooltip that shows the full path steps to reproduce open activity feed click once on the task bar info bar icon look at any activity entry client configuration client version operating system windows os language german installation path of client c program files nextcloud logs as this is a design issue logs do not make sense

0

72,108

23,947,307,632

IssuesEvent

2022-09-12 08:30:58

vector-im/element-android

https://api.github.com/repos/vector-im/element-android

closed

Push notification not working (Google Play variant)

T-Defect A-Notifications S-Critical O-Occasional

### Steps to reproduce Trouble shooting Notification is stuck on "Test Push". Self hosted synapse homeserver is on 1.65, and Android client is 1.4.32 ![image](https://user-images.githubusercontent.com/379266/185794099-3986846d-2131-4ffb-9d82-7e73410321bc.png) ### Outcome Push notification is not received. ### Your phone model Samsung Note 9 ### Operating system version Android 10 ### Application version and app store Element Android 1.4.32 ### Homeserver 1.65.0 ### Will you send logs? Yes ### Are you willing to provide a PR? No

1.0

Push notification not working (Google Play variant) - ### Steps to reproduce Trouble shooting Notification is stuck on "Test Push". Self hosted synapse homeserver is on 1.65, and Android client is 1.4.32 ![image](https://user-images.githubusercontent.com/379266/185794099-3986846d-2131-4ffb-9d82-7e73410321bc.png) ### Outcome Push notification is not received. ### Your phone model Samsung Note 9 ### Operating system version Android 10 ### Application version and app store Element Android 1.4.32 ### Homeserver 1.65.0 ### Will you send logs? Yes ### Are you willing to provide a PR? No

defect

push notification not working google play variant steps to reproduce trouble shooting notification is stuck on test push self hosted synapse homeserver is on and android client is outcome push notification is not received your phone model samsung note operating system version android application version and app store element android homeserver will you send logs yes are you willing to provide a pr no

1

40,819

10,168,548,788

IssuesEvent

2019-08-07 21:06:49

scipy/scipy

https://api.github.com/repos/scipy/scipy

closed

Strictly increasing requirement in UnivariateSpline

Documentation defect scipy.interpolate

I am trying to describe a large dataset using an Univariate spline. With a previous Scipy 0.19 version this worked nicely, now the same data gives with a current Scipy 1.0 the error message > x must be strictly increasing According to the current documentation at https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.UnivariateSpline.html it is enough if x is increasing. The error message is caused by the commit https://github.com/scipy/scipy/commit/8b37277f721eb0f69b2aa4644a961ba0b84e665c which adds a checks for strictly increasing x. On the other hand in the issue https://github.com/scipy/scipy/issues/1753 it is mentioned that the strictly increasing requirement has been lifted already. So does the current documentation need to be updated to include the "strictly" requirement or would a test for increasing x be sufficient? I am not familiar with the underlying routines and maybe overlooking some detail here.

1.0

Strictly increasing requirement in UnivariateSpline - I am trying to describe a large dataset using an Univariate spline. With a previous Scipy 0.19 version this worked nicely, now the same data gives with a current Scipy 1.0 the error message > x must be strictly increasing According to the current documentation at https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.UnivariateSpline.html it is enough if x is increasing. The error message is caused by the commit https://github.com/scipy/scipy/commit/8b37277f721eb0f69b2aa4644a961ba0b84e665c which adds a checks for strictly increasing x. On the other hand in the issue https://github.com/scipy/scipy/issues/1753 it is mentioned that the strictly increasing requirement has been lifted already. So does the current documentation need to be updated to include the "strictly" requirement or would a test for increasing x be sufficient? I am not familiar with the underlying routines and maybe overlooking some detail here.

defect

strictly increasing requirement in univariatespline i am trying to describe a large dataset using an univariate spline with a previous scipy version this worked nicely now the same data gives with a current scipy the error message x must be strictly increasing according to the current documentation at it is enough if x is increasing the error message is caused by the commit which adds a checks for strictly increasing x on the other hand in the issue it is mentioned that the strictly increasing requirement has been lifted already so does the current documentation need to be updated to include the strictly requirement or would a test for increasing x be sufficient i am not familiar with the underlying routines and maybe overlooking some detail here

1

13,152

8,816,084,743

IssuesEvent

2018-12-30 04:52:13

pixelfed/pixelfed

https://api.github.com/repos/pixelfed/pixelfed

closed

Please add support for Blind Key Rotation (privacy feature)

activitypub security work in progress

### Background Blind Key Rotation is a mitigation for the problem that JSON-LD Linked Data Signatures are irrevocable. It is also useful (albeit less so) in the context of HTTP Signatures, since HTTP Signatures only sign headers and not the object itself, and are also detached from the object. ### Implementation - receiving objects Supporting Blind Key Rotation in the validation pipeline is simple enough: if a signature validation fails, refetch the remote actor and recheck the signature accordingly. ### Implementation - deleting objects Supporting Blind Key Rotation to enhance the deniability of deleted objects is also simple enough: send the `Delete` signed with the original key and then silently replace the keypair. The new keys will be fetched when the user publishes new content. ### Questions? Contact me on fediverse: https://pleroma.site/kaniini

True

Please add support for Blind Key Rotation (privacy feature) - ### Background Blind Key Rotation is a mitigation for the problem that JSON-LD Linked Data Signatures are irrevocable. It is also useful (albeit less so) in the context of HTTP Signatures, since HTTP Signatures only sign headers and not the object itself, and are also detached from the object. ### Implementation - receiving objects Supporting Blind Key Rotation in the validation pipeline is simple enough: if a signature validation fails, refetch the remote actor and recheck the signature accordingly. ### Implementation - deleting objects Supporting Blind Key Rotation to enhance the deniability of deleted objects is also simple enough: send the `Delete` signed with the original key and then silently replace the keypair. The new keys will be fetched when the user publishes new content. ### Questions? Contact me on fediverse: https://pleroma.site/kaniini

non_defect

please add support for blind key rotation privacy feature background blind key rotation is a mitigation for the problem that json ld linked data signatures are irrevocable it is also useful albeit less so in the context of http signatures since http signatures only sign headers and not the object itself and are also detached from the object implementation receiving objects supporting blind key rotation in the validation pipeline is simple enough if a signature validation fails refetch the remote actor and recheck the signature accordingly implementation deleting objects supporting blind key rotation to enhance the deniability of deleted objects is also simple enough send the delete signed with the original key and then silently replace the keypair the new keys will be fetched when the user publishes new content questions contact me on fediverse

0

32,065

26,398,389,436

IssuesEvent

2023-01-12 21:48:43

woocommerce/woocommerce

https://api.github.com/repos/woocommerce/woocommerce

closed

Code Freeze: Automation broken

status: prioritization tool: monorepo infrastructure

**Prerequisites (mark completed items with an [x]):** - [x] I have checked that my issue type is not listed here https://github.com/woocommerce/woocommerce/issues/new/choose - [x] My issue is not a security issue, support request, bug report, enhancement or feature request (Please use the link above if it is). **Issue Description:** Code Freeze action doesn't complete. This causes the release lead to have to make manual PRs introducing the potential for errors. First, a `pnpm-lock.yaml` change caused a failure https://github.com/woocommerce/woocommerce/actions/runs/3738934217/jobs/6345560765 I solved this in just the branch with a `git checkout pnpm-lock.yaml` and ran into the next error https://github.com/woocommerce/woocommerce/actions/runs/3739098586/jobs/6345912026 I'm not sure why there was a conflict

1.0

Code Freeze: Automation broken -  **Prerequisites (mark completed items with an [x]):** - [x] I have checked that my issue type is not listed here https://github.com/woocommerce/woocommerce/issues/new/choose - [x] My issue is not a security issue, support request, bug report, enhancement or feature request (Please use the link above if it is). **Issue Description:** Code Freeze action doesn't complete. This causes the release lead to have to make manual PRs introducing the potential for errors. First, a `pnpm-lock.yaml` change caused a failure https://github.com/woocommerce/woocommerce/actions/runs/3738934217/jobs/6345560765 I solved this in just the branch with a `git checkout pnpm-lock.yaml` and ran into the next error https://github.com/woocommerce/woocommerce/actions/runs/3739098586/jobs/6345912026 I'm not sure why there was a conflict

non_defect

code freeze automation broken prerequisites mark completed items with an i have checked that my issue type is not listed here my issue is not a security issue support request bug report enhancement or feature request please use the link above if it is issue description code freeze action doesn t complete this causes the release lead to have to make manual prs introducing the potential for errors first a pnpm lock yaml change caused a failure i solved this in just the branch with a git checkout pnpm lock yaml and ran into the next error i m not sure why there was a conflict

0

220,461

16,960,107,833

IssuesEvent

2021-06-29 01:44:31

RaRe-Technologies/gensim

https://api.github.com/repos/RaRe-Technologies/gensim

closed

Documentation of strip_punctuation vs strip_punctuation2 in gensim.parsing.preprocessing

documentation

Thanks for all the hard work on this fantastic library. I found a small quirk today, not really a bug, just a bit of a rough edge: In `gensim.parsing` [preprocessing.py ](https://github.com/RaRe-Technologies/gensim/blob/e210f73c42c5df5a511ca27166cbc7d10970eab2/gensim/parsing/preprocessing.py#L121) `strip_punctuation2` is defined: `strip_punctuation2 = strip_punctuation`. In the [documentation](https://radimrehurek.com/gensim/parsing/preprocessing.html) the description of [`strip_punctuation2`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation2) is a duplication of [`strip_punctuation`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation) rather than a statement of equality. I noticed this while reading the documentation and, assuming I was missing an obvious distinction, attempting to hand diff the the docs for the two functions. When I gave up and flipped to the source it became obvious how the two functions are related.

1.0

Documentation of strip_punctuation vs strip_punctuation2 in gensim.parsing.preprocessing - Thanks for all the hard work on this fantastic library. I found a small quirk today, not really a bug, just a bit of a rough edge: In `gensim.parsing` [preprocessing.py ](https://github.com/RaRe-Technologies/gensim/blob/e210f73c42c5df5a511ca27166cbc7d10970eab2/gensim/parsing/preprocessing.py#L121) `strip_punctuation2` is defined: `strip_punctuation2 = strip_punctuation`. In the [documentation](https://radimrehurek.com/gensim/parsing/preprocessing.html) the description of [`strip_punctuation2`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation2) is a duplication of [`strip_punctuation`](https://radimrehurek.com/gensim/parsing/preprocessing.html#gensim.parsing.preprocessing.strip_punctuation) rather than a statement of equality. I noticed this while reading the documentation and, assuming I was missing an obvious distinction, attempting to hand diff the the docs for the two functions. When I gave up and flipped to the source it became obvious how the two functions are related.

non_defect

documentation of strip punctuation vs strip in gensim parsing preprocessing thanks for all the hard work on this fantastic library i found a small quirk today not really a bug just a bit of a rough edge in gensim parsing strip is defined strip strip punctuation in the the description of is a duplication of rather than a statement of equality i noticed this while reading the documentation and assuming i was missing an obvious distinction attempting to hand diff the the docs for the two functions when i gave up and flipped to the source it became obvious how the two functions are related

0

6,652

2,610,258,440

IssuesEvent

2015-02-26 19:22:26

chrsmith/dsdsdaadf

https://api.github.com/repos/chrsmith/dsdsdaadf

opened

深圳激光治痘痘

auto-migrated Priority-Medium Type-Defect

``` 深圳激光治痘痘【深圳韩方科颜全国热线400-869-1818，24小时QQ4 008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:51

1.0

深圳激光治痘痘 - ``` 深圳激光治痘痘【深圳韩方科颜全国热线400-869-1818，24小时QQ4 008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� ``` ----- Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:51

defect

深圳激光治痘痘深圳激光治痘痘【，】深圳韩方科颜专业祛痘连锁机构，机构以韩国秘方�� —韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩方科� ��专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专业治�� 粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的痘痘� �� original issue reported on code google com by szft com on may at

1

121,362

15,893,811,257

IssuesEvent

2021-04-11 07:42:45

lopis/job-board

https://api.github.com/repos/lopis/job-board

closed

Create Job Listing Page

⚛️ React 🎨 Design

Create new Page component under `pages/` for displaying a single job listing. This requires creating a new API call to fetch a single job listing in full detail (as well as adapting the mocks)

1.0

Create Job Listing Page - Create new Page component under `pages/` for displaying a single job listing. This requires creating a new API call to fetch a single job listing in full detail (as well as adapting the mocks)

non_defect

create job listing page create new page component under pages for displaying a single job listing this requires creating a new api call to fetch a single job listing in full detail as well as adapting the mocks

0

173,013

21,094,381,199

IssuesEvent

2022-04-04 08:56:16

lukebroganws/NodeGoat

https://api.github.com/repos/lukebroganws/NodeGoat

closed

zaproxy-0.2.0.tgz: 18 vulnerabilities (highest severity is: 9.8) - autoclosed

security vulnerability

<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - zaproxy-0.2.0.tgz</summary> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | --- | --- | | [CVE-2018-1000620](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | cryptiles-0.2.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2019-10744](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.1 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2018-3728](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | hoek-0.9.1.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [WS-2014-0005](https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2016-2515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | hawk-1.0.0.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2021-44907](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | N/A | ❌ | | [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.2.11.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2014-10064](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2020-8203](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2021-23337](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2019-1010266](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2018-3721](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2017-16026](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | request-2.36.0.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2018-16487](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2020-28500](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2014-7191](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [WS-2017-0266](https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.5 | http-signature-0.10.1.tgz | Transitive | 0.3.0 | ✅ | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000620</summary> ### Vulnerable Library - cryptiles-0.2.2.tgz General purpose crypto utilities Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/cryptiles/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: **cryptiles-0.2.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2. Publish Date: 2018-07-09 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</a> ### CVSS 3 Score Details (9.8) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620</a> Release Date: 2018-07-09 Fix Resolution (cryptiles): 4.1.2 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. Publish Date: 2019-07-26 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744>CVE-2019-10744</a> ### CVSS 3 Score Details (9.1) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a> Release Date: 2019-07-26 Fix Resolution (lodash): 4.17.12 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-3728</summary> ### Vulnerable Library - hoek-0.9.1.tgz General purpose node utilities Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz">https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/hoek/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: **hoek-0.9.1.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. Publish Date: 2018-03-30 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</a> ### CVSS 3 Score Details (8.8) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a> Release Date: 2018-03-30 Fix Resolution (hoek): 4.2.0 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0005</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time Publish Date: 2014-07-31 URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2014-0005">https://nvd.nist.gov/vuln/detail/WS-2014-0005</a> Release Date: 2014-07-31 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2515</summary> ### Vulnerable Library - hawk-1.0.0.tgz HTTP Hawk Authentication Scheme Library home page: <a href="https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz">https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/hawk/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **hawk-1.0.0.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression. Publish Date: 2016-04-13 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515>CVE-2016-2515</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2515">https://nvd.nist.gov/vuln/detail/CVE-2016-2515</a> Release Date: 2016-04-13 Fix Resolution (hawk): 3.1.3 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44907</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior. Publish Date: 2022-03-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907>CVE-2021-44907</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907</a> Release Date: 2022-03-17 Fix Resolution: qs - 6.8.1 </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - mime-1.2.11.tgz A comprehensive library for mime-type mapping Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.11.tgz">https://registry.npmjs.org/mime/-/mime-1.2.11.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/mime/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **mime-1.2.11.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a> Release Date: 2018-06-07 Fix Resolution (mime): 1.4.1 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10064</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring. Publish Date: 2018-05-31 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064>CVE-2014-10064</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10064">https://nvd.nist.gov/vuln/detail/CVE-2014-10064</a> Release Date: 2018-05-31 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. Publish Date: 2020-07-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a> ### CVSS 3 Score Details (7.4) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a> Release Date: 2020-07-15 Fix Resolution (lodash): 4.17.9 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. Publish Date: 2021-02-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a> ### CVSS 3 Score Details (7.2) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a> Release Date: 2021-02-15 Fix Resolution (lodash): 4.17.21 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. Publish Date: 2019-07-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a> ### CVSS 3 Score Details (6.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a> Release Date: 2020-09-30 Fix Resolution (lodash): 4.17.11 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a> ### CVSS 3 Score Details (6.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a> Release Date: 2018-06-07 Fix Resolution (lodash): 4.17.5 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-16026</summary> ### Vulnerable Library - request-2.36.0.tgz Simplified HTTP request client. Library home page: <a href="https://registry.npmjs.org/request/-/request-2.36.0.tgz">https://registry.npmjs.org/request/-/request-2.36.0.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/request/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **request-2.36.0.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 || >2.51.0 <=2.67.0. Publish Date: 2018-06-04 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026>CVE-2017-16026</a> ### CVSS 3 Score Details (5.9) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-16026">https://nvd.nist.gov/vuln/detail/CVE-2017-16026</a> Release Date: 2018-06-04 Fix Resolution (request): 2.68.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype. Publish Date: 2019-02-01 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</a> ### CVSS 3 Score Details (5.6) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a> Release Date: 2019-02-01 Fix Resolution (lodash): 4.17.11 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash. Publish Date: 2021-02-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a> Release Date: 2021-02-15 Fix Resolution (lodash): 4.17.21 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-1000048</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash. Publish Date: 2017-07-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a> Release Date: 2017-07-17 Fix Resolution (qs): 6.0.4 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. Publish Date: 2014-10-19 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191>CVE-2014-7191</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a> Release Date: 2014-10-19 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> WS-2017-0266</summary> ### Vulnerable Library - http-signature-0.10.1.tgz Reference implementation of Joyent's HTTP Signature scheme. Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **http-signature-0.10.1.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure. Publish Date: 2015-01-22 URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</a> ### CVSS 3 Score Details (3.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a> Release Date: 2015-01-22 Fix Resolution (http-signature): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 In order to enable automatic remediation, please create <a target="_blank" href="https://whitesource.atlassian.net/wiki/spaces/WD/pages/697696422/WhiteSource+for+GitHub.com#Remediate-Settings-(remediateSettings)">workflow rules</a> </details> *** :rescue_worker_helmet: Automatic Remediation is available for this issue.

True

zaproxy-0.2.0.tgz: 18 vulnerabilities (highest severity is: 9.8) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - zaproxy-0.2.0.tgz</summary> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | --- | --- | | [CVE-2018-1000620](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | cryptiles-0.2.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2019-10744](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.1 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2018-3728](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | hoek-0.9.1.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [WS-2014-0005](https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2016-2515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | hawk-1.0.0.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2021-44907](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | N/A | ❌ | | [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.2.11.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2014-10064](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2020-8203](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2021-23337](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2019-1010266](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2018-3721](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2017-16026](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | request-2.36.0.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2018-16487](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2020-28500](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-2.4.2.tgz | Transitive | 1.0.0-rc.1 | ✅ | | [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [CVE-2014-7191](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.6.6.tgz | Transitive | 0.3.0 | ✅ | | [WS-2017-0266](https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.5 | http-signature-0.10.1.tgz | Transitive | 0.3.0 | ✅ | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000620</summary> ### Vulnerable Library - cryptiles-0.2.2.tgz General purpose crypto utilities Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/cryptiles/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: **cryptiles-0.2.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2. Publish Date: 2018-07-09 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</a> ### CVSS 3 Score Details (9.8) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000620</a> Release Date: 2018-07-09 Fix Resolution (cryptiles): 4.1.2 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. Publish Date: 2019-07-26 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10744>CVE-2019-10744</a> ### CVSS 3 Score Details (9.1) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a> Release Date: 2019-07-26 Fix Resolution (lodash): 4.17.12 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-3728</summary> ### Vulnerable Library - hoek-0.9.1.tgz General purpose node utilities Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz">https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/hoek/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - hawk-1.0.0.tgz - :x: **hoek-0.9.1.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. Publish Date: 2018-03-30 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</a> ### CVSS 3 Score Details (8.8) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a> Release Date: 2018-03-30 Fix Resolution (hoek): 4.2.0 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0005</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time Publish Date: 2014-07-31 URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2014-0005">https://nvd.nist.gov/vuln/detail/WS-2014-0005</a> Release Date: 2014-07-31 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2515</summary> ### Vulnerable Library - hawk-1.0.0.tgz HTTP Hawk Authentication Scheme Library home page: <a href="https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz">https://registry.npmjs.org/hawk/-/hawk-1.0.0.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/hawk/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **hawk-1.0.0.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Hawk before 3.1.3 and 4.x before 4.1.1 allow remote attackers to cause a denial of service (CPU consumption or partial outage) via a long (1) header or (2) URI that is matched against an improper regular expression. Publish Date: 2016-04-13 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2515>CVE-2016-2515</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2515">https://nvd.nist.gov/vuln/detail/CVE-2016-2515</a> Release Date: 2016-04-13 Fix Resolution (hawk): 3.1.3 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44907</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details A Denial of Service vulnerability exists in qs up to 6.8.0 due to insufficient sanitization of property in the gs.parse function. The merge() function allows the assignment of properties on an array in the query. For any property being assigned, a value in the array is converted to an object containing these properties. Essentially, this means that the property whose expected type is Array always has to be checked with Array.isArray() by the user. This may not be obvious to the user and can cause unexpected behavior. Publish Date: 2022-03-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44907>CVE-2021-44907</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44907</a> Release Date: 2022-03-17 Fix Resolution: qs - 6.8.1 </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - mime-1.2.11.tgz A comprehensive library for mime-type mapping Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.11.tgz">https://registry.npmjs.org/mime/-/mime-1.2.11.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/mime/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **mime-1.2.11.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a> Release Date: 2018-06-07 Fix Resolution (mime): 1.4.1 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10064</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring. Publish Date: 2018-05-31 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10064>CVE-2014-10064</a> ### CVSS 3 Score Details (7.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10064">https://nvd.nist.gov/vuln/detail/CVE-2014-10064</a> Release Date: 2018-05-31 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. Publish Date: 2020-07-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a> ### CVSS 3 Score Details (7.4) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a> Release Date: 2020-07-15 Fix Resolution (lodash): 4.17.9 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. Publish Date: 2021-02-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a> ### CVSS 3 Score Details (7.2) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a> Release Date: 2021-02-15 Fix Resolution (lodash): 4.17.21 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. Publish Date: 2019-07-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a> ### CVSS 3 Score Details (6.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a> Release Date: 2020-09-30 Fix Resolution (lodash): 4.17.11 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. Publish Date: 2018-06-07 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a> ### CVSS 3 Score Details (6.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a> Release Date: 2018-06-07 Fix Resolution (lodash): 4.17.5 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-16026</summary> ### Vulnerable Library - request-2.36.0.tgz Simplified HTTP request client. Library home page: <a href="https://registry.npmjs.org/request/-/request-2.36.0.tgz">https://registry.npmjs.org/request/-/request-2.36.0.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/request/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **request-2.36.0.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Request is an http client. If a request is made using ```multipart```, and the body type is a ```number```, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 || >2.51.0 <=2.67.0. Publish Date: 2018-06-04 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16026>CVE-2017-16026</a> ### CVSS 3 Score Details (5.9) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-16026">https://nvd.nist.gov/vuln/detail/CVE-2017-16026</a> Release Date: 2018-06-04 Fix Resolution (request): 2.68.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype. Publish Date: 2019-02-01 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</a> ### CVSS 3 Score Details (5.6) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a> Release Date: 2019-02-01 Fix Resolution (lodash): 4.17.11 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary> ### Vulnerable Library - lodash-2.4.2.tgz A utility library delivering consistency, customization, performance, & extras. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/lodash/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash. Publish Date: 2021-02-15 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a> Release Date: 2021-02-15 Fix Resolution (lodash): 4.17.21 Direct dependency fix Resolution (zaproxy): 1.0.0-rc.1 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-1000048</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash. Publish Date: 2017-07-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a> Release Date: 2017-07-17 Fix Resolution (qs): 6.0.4 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - qs-0.6.6.tgz querystring parser Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.6.tgz">https://registry.npmjs.org/qs/-/qs-0.6.6.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/qs/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **qs-0.6.6.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. Publish Date: 2014-10-19 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-7191>CVE-2014-7191</a> ### CVSS 3 Score Details (5.3) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a> Release Date: 2014-10-19 Fix Resolution (qs): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> WS-2017-0266</summary> ### Vulnerable Library - http-signature-0.10.1.tgz Reference implementation of Joyent's HTTP Signature scheme. Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz</a> Path to dependency file: /package.json Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - request-2.36.0.tgz - :x: **http-signature-0.10.1.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/lukebroganws/NodeGoat/commit/87ddac411e57ea4967b0d6435a454aa503b72ae5">87ddac411e57ea4967b0d6435a454aa503b72ae5</a> Found in base branch: master ### Vulnerability Details http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure. Publish Date: 2015-01-22 URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</a> ### CVSS 3 Score Details (3.5) Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. ### Suggested Fix Type: Upgrade version Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a> Release Date: 2015-01-22 Fix Resolution (http-signature): 1.0.0 Direct dependency fix Resolution (zaproxy): 0.3.0 In order to enable automatic remediation, please create <a target="_blank" href="https://whitesource.atlassian.net/wiki/spaces/WD/pages/697696422/WhiteSource+for+GitHub.com#Remediate-Settings-(remediateSettings)">workflow rules</a> </details> *** :rescue_worker_helmet: Automatic Remediation is available for this issue.

non_defect

zaproxy tgz vulnerabilities highest severity is autoclosed vulnerable library zaproxy tgz path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high cryptiles tgz transitive rc high lodash tgz transitive rc high hoek tgz transitive rc high qs tgz transitive high hawk tgz transitive high qs tgz transitive n a high mime tgz transitive high qs tgz transitive high lodash tgz transitive rc high lodash tgz transitive rc medium lodash tgz transitive rc medium lodash tgz transitive rc medium request tgz transitive medium lodash tgz transitive rc medium lodash tgz transitive rc medium qs tgz transitive medium qs tgz transitive low http signature tgz transitive details cve vulnerable library cryptiles tgz general purpose crypto utilities library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules cryptiles package json dependency hierarchy zaproxy tgz root library request tgz hawk tgz x cryptiles tgz vulnerable library found in head commit a href found in base branch master vulnerability details eran hammer cryptiles version earlier contains a cwe insufficient entropy vulnerability in randomdigits method that can result in an attacker is more likely to be able to brute force something that was supposed to be random this attack appear to be exploitable via depends upon the calling application this vulnerability appears to have been fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cryptiles direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of lodash lower than are vulnerable to prototype pollution the function defaultsdeep could be tricked into adding or modifying properties of object prototype using a constructor payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library hoek tgz general purpose node utilities library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules hoek package json dependency hierarchy zaproxy tgz root library request tgz hawk tgz x hoek tgz vulnerable library found in head commit a href found in base branch master vulnerability details hoek node module before and x before suffers from a modification of assumed immutable data maid vulnerability via merge and applytodefaults functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hoek direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue ws vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details denial of service extended event loop blocking the qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library hawk tgz http hawk authentication scheme library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules hawk package json dependency hierarchy zaproxy tgz root library request tgz x hawk tgz vulnerable library found in head commit a href found in base branch master vulnerability details hawk before and x before allow remote attackers to cause a denial of service cpu consumption or partial outage via a long header or uri that is matched against an improper regular expression publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hawk direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details a denial of service vulnerability exists in qs up to due to insufficient sanitization of property in the gs parse function the merge function allows the assignment of properties on an array in the query for any property being assigned a value in the array is converted to an object containing these properties essentially this means that the property whose expected type is array always has to be checked with array isarray by the user this may not be obvious to the user and can cause unexpected behavior publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs cve vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules mime package json dependency hierarchy zaproxy tgz root library request tgz x mime tgz vulnerable library found in head commit a href found in base branch master vulnerability details the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution mime direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the qs module before does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time an attacker could leverage this to cause a temporary denial of service condition for example in a web application other requests would not be processed while this blocking is occurring publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution attack when using zipobjectdeep in lodash before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules request package json dependency hierarchy zaproxy tgz root library x request tgz vulnerable library found in head commit a href found in base branch master vulnerability details request is an http client if a request is made using multipart and the body type is a number then the specified number of non zero memory is passed in the body this affects request publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution request direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions whitesource note after conducting further research whitesource has determined that cve only affects environments with versions to of lodash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution zaproxy rc rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the web framework using ljharb s qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules qs package json dependency hierarchy zaproxy tgz root library request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the qs module before in node js does not call the compact function for array data which allows remote attackers to cause a denial of service memory consumption by using a large index value to create a sparse array publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution zaproxy rescue worker helmet automatic remediation is available for this issue ws vulnerable library http signature tgz reference implementation of joyent s http signature scheme library home page a href path to dependency file package json path to vulnerable library node modules zaproxy node modules http signature package json dependency hierarchy zaproxy tgz root library request tgz x http signature tgz vulnerable library found in head commit a href found in base branch master vulnerability details http signature before version are vulnerable to timing attack which may lead to information disclosure publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution http signature direct dependency fix resolution zaproxy in order to enable automatic remediation please create rescue worker helmet automatic remediation is available for this issue istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails eran hammer cryptiles version earlier contains a cwe insufficient entropy vulnerability in randomdigits method that can result in an attacker is more likely to be able to brute force something that was supposed to be random this attack appear to be exploitable via depends upon the calling application this vulnerability appears to have been fixed in vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of lodash lower than are vulnerable to prototype pollution the function defaultsdeep could be tricked into adding or modifying properties of object prototype using a constructor payload vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails hoek node module before and x before suffers from a modification of assumed immutable data maid vulnerability via and functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails denial of service extended event loop blocking the qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails hawk before and x before allow remote attackers to cause a denial of service cpu consumption or partial outage via a long header or uri that is matched against an improper regular expression vulnerabilityurl istransitivedependency true dependencytree zaproxy request qs isminimumfixversionavailable true minimumfixversion qs isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a denial of service vulnerability exists in qs up to due to insufficient sanitization of property in the gs parse function the merge function allows the assignment of properties on an array in the query for any property being assigned a value in the array is converted to an object containing these properties essentially this means that the property whose expected type is array always has to be checked with array isarray by the user this may not be obvious to the user and can cause unexpected behavior vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the qs module before does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time an attacker could leverage this to cause a temporary denial of service condition for example in a web application other requests would not be processed while this blocking is occurring vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails prototype pollution attack when using zipobjectdeep in lodash before vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to command injection via the template function vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails request is an http client if a request is made using multipart and the body type is a number then the specified number of non zero memory is passed in the body this affects request vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion rc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions n whitesource note after conducting further research whitesource has determined that cve only affects environments with versions to of lodash vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the web framework using ljharb qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the qs module before in node js does not call the compact function for array data which allows remote attackers to cause a denial of service memory consumption by using a large index value to create a sparse array vulnerabilityurl istransitivedependency false dependencytree zaproxy isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails http signature before version are vulnerable to timing attack which may lead to information disclosure vulnerabilityurl

0

212,904

16,487,071,335

IssuesEvent

2021-05-24 19:41:49

E3SM-Project/zppy

https://api.github.com/repos/E3SM-Project/zppy

closed

Add testing

for next version testing

Add a unit test that runs on Chrysalis or another machine (not on GitHub Actions Linux machine).

1.0

Add testing - Add a unit test that runs on Chrysalis or another machine (not on GitHub Actions Linux machine).

non_defect

add testing add a unit test that runs on chrysalis or another machine not on github actions linux machine

0

840

2,644,777,690

IssuesEvent

2015-03-12 18:45:00

Homebrew/homebrew-science

https://api.github.com/repos/Homebrew/homebrew-science

closed

Infernal 1.1.1 - Make Error 2 with fresh install of Linuxbrew

Bioinformatics build-error Linux

Got this unexpected error on _Red Hat Enterprise Linux Server release 7.1 (Maipo)_ ``` ==> Installing prokka dependency: infernal ==> Downloading http://selab.janelia.org/software/infernal/infernal-1.1.1.tar.gz ######################################################################## 100.0% ==> ./configure --prefix=/home/linuxbrew/Cellar/infernal/1.1.1 ==> make make[2]: *** [hmmpgmd] Error 1 make[2]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer' make: *** [all] Error 2 ```

1.0

Infernal 1.1.1 - Make Error 2 with fresh install of Linuxbrew - Got this unexpected error on _Red Hat Enterprise Linux Server release 7.1 (Maipo)_ ``` ==> Installing prokka dependency: infernal ==> Downloading http://selab.janelia.org/software/infernal/infernal-1.1.1.tar.gz ######################################################################## 100.0% ==> ./configure --prefix=/home/linuxbrew/Cellar/infernal/1.1.1 ==> make make[2]: *** [hmmpgmd] Error 1 make[2]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/infernal-Vq2IGg/infernal-1.1.1/hmmer' make: *** [all] Error 2 ```

non_defect

infernal make error with fresh install of linuxbrew got this unexpected error on red hat enterprise linux server release maipo installing prokka dependency infernal downloading configure prefix home linuxbrew cellar infernal make make error make leaving directory tmp infernal infernal hmmer src make error make leaving directory tmp infernal infernal hmmer make error

0

41,200

12,831,755,528

IssuesEvent

2020-07-07 06:14:07

rvvergara/todolist-api-igaku

https://api.github.com/repos/rvvergara/todolist-api-igaku

closed

WS-2020-0070 (High) detected in lodash-4.17.15.tgz

security vulnerability

## WS-2020-0070 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - lodash-4.17.15.tgz</summary> Lodash modular utilities. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a> Path to dependency file: /tmp/ws-scm/todolist-api-igaku/package.json Path to vulnerable library: /tmp/ws-scm/todolist-api-igaku/node_modules/lodash/package.json Dependency Hierarchy: - eslint-6.6.0.tgz (Root Library) - :x: **lodash-4.17.15.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/rvvergara/todolist-api-igaku/commit/e74ac424f4412547afcf733f031f27227a0f28e9">e74ac424f4412547afcf733f031f27227a0f28e9</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> All versions of lodash are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays. This vulnerability may lead to Denial of Service or Code Execution. Publish Date: 2020-04-28 URL: <a href=https://hackerone.com/reports/712065>WS-2020-0070</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (8.1)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

WS-2020-0070 (High) detected in lodash-4.17.15.tgz - ## WS-2020-0070 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - lodash-4.17.15.tgz</summary> Lodash modular utilities. Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a> Path to dependency file: /tmp/ws-scm/todolist-api-igaku/package.json Path to vulnerable library: /tmp/ws-scm/todolist-api-igaku/node_modules/lodash/package.json Dependency Hierarchy: - eslint-6.6.0.tgz (Root Library) - :x: **lodash-4.17.15.tgz** (Vulnerable Library) Found in HEAD commit: <a href="https://github.com/rvvergara/todolist-api-igaku/commit/e74ac424f4412547afcf733f031f27227a0f28e9">e74ac424f4412547afcf733f031f27227a0f28e9</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> All versions of lodash are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays. This vulnerability may lead to Denial of Service or Code Execution. Publish Date: 2020-04-28 URL: <a href=https://hackerone.com/reports/712065>WS-2020-0070</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (8.1)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

non_defect

ws high detected in lodash tgz ws high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file tmp ws scm todolist api igaku package json path to vulnerable library tmp ws scm todolist api igaku node modules lodash package json dependency hierarchy eslint tgz root library x lodash tgz vulnerable library found in head commit a href vulnerability details all versions of lodash are vulnerable to prototype pollution the function zipobjectdeep allows a malicious user to modify the prototype of object if the property identifiers are user supplied being affected by this issue requires zipping objects based on user provided property arrays this vulnerability may lead to denial of service or code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with whitesource

0

61,717

17,023,763,360

IssuesEvent

2021-07-03 03:43:09

tomhughes/trac-tickets

https://api.github.com/repos/tomhughes/trac-tickets

closed

Item name not updated on different zoomlevel

Component: mapnik Priority: minor Resolution: invalid Type: defect

**[Submitted to the original trac issue database at 8.39pm, Saturday, 10th December 2011]** I just updated an item. When zooming in to the maximum, the new name shows up nicely, but when I zoom out one level, the old name shows up again. This happened on a different browser from where I am making the changes (also not logged in). I tried to find if such a ticket already exists but it's hard to find a correct search term, so I didn't find any similar reports.

1.0

Item name not updated on different zoomlevel - **[Submitted to the original trac issue database at 8.39pm, Saturday, 10th December 2011]** I just updated an item. When zooming in to the maximum, the new name shows up nicely, but when I zoom out one level, the old name shows up again. This happened on a different browser from where I am making the changes (also not logged in). I tried to find if such a ticket already exists but it's hard to find a correct search term, so I didn't find any similar reports.

defect

item name not updated on different zoomlevel i just updated an item when zooming in to the maximum the new name shows up nicely but when i zoom out one level the old name shows up again this happened on a different browser from where i am making the changes also not logged in i tried to find if such a ticket already exists but it s hard to find a correct search term so i didn t find any similar reports

1

101,248

4,111,218,737

IssuesEvent

2016-06-07 04:31:36

rdunlop/unicycling-registration

https://api.github.com/repos/rdunlop/unicycling-registration

opened

Deleting the last member in a competitor, site crashes

High Priority

If I remove the last member of a competitor, I get persistent 500 errors.

1.0

Deleting the last member in a competitor, site crashes - If I remove the last member of a competitor, I get persistent 500 errors.

non_defect

deleting the last member in a competitor site crashes if i remove the last member of a competitor i get persistent errors

0

55,085

7,954,596,897

IssuesEvent

2018-07-12 08:05:32

ppy/osu-framework

https://api.github.com/repos/ppy/osu-framework

opened

Update wiki page for the loading process of a Drawable

documentation

The loading process was adjusted in #1670. The following connection doesn't exist anymore: ![screen shot 2018-07-12 at 5 02 28 pm](https://user-images.githubusercontent.com/1329837/42620347-aeba3272-85f5-11e8-8b38-ec2d65d6e2c1.png)

1.0

Update wiki page for the loading process of a Drawable - The loading process was adjusted in #1670. The following connection doesn't exist anymore: ![screen shot 2018-07-12 at 5 02 28 pm](https://user-images.githubusercontent.com/1329837/42620347-aeba3272-85f5-11e8-8b38-ec2d65d6e2c1.png)

non_defect

update wiki page for the loading process of a drawable the loading process was adjusted in the following connection doesn t exist anymore

0

80,241

30,182,204,491

IssuesEvent

2023-07-04 09:37:15

jOOQ/jOOQ

https://api.github.com/repos/jOOQ/jOOQ

closed

Parser error when using SET new.x = y syntax in triggers

T: Defect P: Medium R: Fixed E: Professional Edition E: Enterprise Edition C: Parser

The following is a valid trigger definition, e.g. in Db2: ```sql CREATE TRIGGER trg_triggers_before_i BEFORE INSERT ON t_triggers_before REFERENCING NEW AS new FOR EACH ROW BEGIN SET new.c = 1; END; ``` However, we can't parse it: ``` org.jooq.impl.ParserException: Assignment expected: [53:3] ...efore REFERENCING NEW AS new FOR EACH ROW BEGIN [*]SET new.c = 1; END; CREATE TRIGGER trg_triggers_before_u BEFORE UPDATE ON t_tri... at org.jooq.impl.DefaultParseContext.expected (ParserImpl.java:14775) at org.jooq.impl.DefaultParseContext.parseAssignment (ParserImpl.java:4035) at org.jooq.impl.DefaultParseContext.parseStatement (ParserImpl.java:3671) at org.jooq.impl.DefaultParseContext.parseStatements (ParserImpl.java:3392) at org.jooq.impl.DefaultParseContext.parseStatementsAndPeek (ParserImpl.java:3410) at org.jooq.impl.DefaultParseContext.parseBlock (ParserImpl.java:3339) at org.jooq.impl.DefaultParseContext.parseCreateTrigger (ParserImpl.java:5893) at org.jooq.impl.DefaultParseContext.parseCreate (ParserImpl.java:2937) at org.jooq.impl.DefaultParseContext.parseQuery (ParserImpl.java:1133) at org.jooq.impl.DefaultParseContext.lambda$parse$0 (ParserImpl.java:903) at org.jooq.impl.DefaultParseContext.wrap (ParserImpl.java:15002) at org.jooq.impl.DefaultParseContext.parse (ParserImpl.java:891) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:769) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:764) ``` This issue just handles the parser error for now. There might be more follow-up issues handling the emulation of the feature, in case the `REFERENCING` clause isn't supported.

1.0

Parser error when using SET new.x = y syntax in triggers - The following is a valid trigger definition, e.g. in Db2: ```sql CREATE TRIGGER trg_triggers_before_i BEFORE INSERT ON t_triggers_before REFERENCING NEW AS new FOR EACH ROW BEGIN SET new.c = 1; END; ``` However, we can't parse it: ``` org.jooq.impl.ParserException: Assignment expected: [53:3] ...efore REFERENCING NEW AS new FOR EACH ROW BEGIN [*]SET new.c = 1; END; CREATE TRIGGER trg_triggers_before_u BEFORE UPDATE ON t_tri... at org.jooq.impl.DefaultParseContext.expected (ParserImpl.java:14775) at org.jooq.impl.DefaultParseContext.parseAssignment (ParserImpl.java:4035) at org.jooq.impl.DefaultParseContext.parseStatement (ParserImpl.java:3671) at org.jooq.impl.DefaultParseContext.parseStatements (ParserImpl.java:3392) at org.jooq.impl.DefaultParseContext.parseStatementsAndPeek (ParserImpl.java:3410) at org.jooq.impl.DefaultParseContext.parseBlock (ParserImpl.java:3339) at org.jooq.impl.DefaultParseContext.parseCreateTrigger (ParserImpl.java:5893) at org.jooq.impl.DefaultParseContext.parseCreate (ParserImpl.java:2937) at org.jooq.impl.DefaultParseContext.parseQuery (ParserImpl.java:1133) at org.jooq.impl.DefaultParseContext.lambda$parse$0 (ParserImpl.java:903) at org.jooq.impl.DefaultParseContext.wrap (ParserImpl.java:15002) at org.jooq.impl.DefaultParseContext.parse (ParserImpl.java:891) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:769) at org.jooq.impl.ParserImpl.parse (ParserImpl.java:764) ``` This issue just handles the parser error for now. There might be more follow-up issues handling the emulation of the feature, in case the `REFERENCING` clause isn't supported.

defect

parser error when using set new x y syntax in triggers the following is a valid trigger definition e g in sql create trigger trg triggers before i before insert on t triggers before referencing new as new for each row begin set new c end however we can t parse it org jooq impl parserexception assignment expected efore referencing new as new for each row begin set new c end create trigger trg triggers before u before update on t tri at org jooq impl defaultparsecontext expected parserimpl java at org jooq impl defaultparsecontext parseassignment parserimpl java at org jooq impl defaultparsecontext parsestatement parserimpl java at org jooq impl defaultparsecontext parsestatements parserimpl java at org jooq impl defaultparsecontext parsestatementsandpeek parserimpl java at org jooq impl defaultparsecontext parseblock parserimpl java at org jooq impl defaultparsecontext parsecreatetrigger parserimpl java at org jooq impl defaultparsecontext parsecreate parserimpl java at org jooq impl defaultparsecontext parsequery parserimpl java at org jooq impl defaultparsecontext lambda parse parserimpl java at org jooq impl defaultparsecontext wrap parserimpl java at org jooq impl defaultparsecontext parse parserimpl java at org jooq impl parserimpl parse parserimpl java at org jooq impl parserimpl parse parserimpl java this issue just handles the parser error for now there might be more follow up issues handling the emulation of the feature in case the referencing clause isn t supported

1

39,611

9,562,138,550

IssuesEvent

2019-05-04 06:00:54

catmaid/CATMAID

https://api.github.com/repos/catmaid/CATMAID

opened

Issue with Neuron Similarity Widget on dev

type: defect

Hi! I'm trying to setup NBLAST/Neuron Similarity Widget being on `dev` branch. R and its dependencies are setup and Celery is working. When I open the Neuron Similarity Widget, I get a JSON parsing error, caused by the request `http://localhost:8000/catmaid/3/similarity/queries/?with_objects=false&with_scoring=false` which returns None. Any pointer how to fix this? Also, when I try to setup a configuration, in the Configuration Tab of the widget, when I press "Create Similarity Matrix", a message is shown, "No matching transformed skeletons selected" even though I have selected an active skeletons. Thanks for help.

1.0

Issue with Neuron Similarity Widget on dev - Hi! I'm trying to setup NBLAST/Neuron Similarity Widget being on `dev` branch. R and its dependencies are setup and Celery is working. When I open the Neuron Similarity Widget, I get a JSON parsing error, caused by the request `http://localhost:8000/catmaid/3/similarity/queries/?with_objects=false&with_scoring=false` which returns None. Any pointer how to fix this? Also, when I try to setup a configuration, in the Configuration Tab of the widget, when I press "Create Similarity Matrix", a message is shown, "No matching transformed skeletons selected" even though I have selected an active skeletons. Thanks for help.

defect

issue with neuron similarity widget on dev hi i m trying to setup nblast neuron similarity widget being on dev branch r and its dependencies are setup and celery is working when i open the neuron similarity widget i get a json parsing error caused by the request which returns none any pointer how to fix this also when i try to setup a configuration in the configuration tab of the widget when i press create similarity matrix a message is shown no matching transformed skeletons selected even though i have selected an active skeletons thanks for help

1

39,252

9,358,111,648

IssuesEvent

2019-04-02 00:53:43

jOOQ/jOOQ

https://api.github.com/repos/jOOQ/jOOQ

opened

WHERE caluse missing when using INSERT ... ON DUPLICATE

T: Defect

Using jooq 3.11.9, the following query prints: `` public static void main(String[] args) throws SQLException { String sql = DSL.using(SQLDialect.MYSQL_5_7).renderInlined( insertInto(table("tableA")) .columns(field("colA"), field("colB")) .values("val1", "val2") .onDuplicateKeyUpdate() .set(field("colA"), "something") .where(field("colC").eq("other"))); System.out.println(sql); } `` `insert into tableA (colA, colB) values ('val1', 'val2') on duplicate key update colA = 'something'` The WHERE clause and "colC" are never mentioned in the query. I'm might be inexperienced with SQL but I would expect and exception or at least a warning would be thrown if I'm doing something invalid or unsupported.

1.0

WHERE caluse missing when using INSERT ... ON DUPLICATE - Using jooq 3.11.9, the following query prints: `` public static void main(String[] args) throws SQLException { String sql = DSL.using(SQLDialect.MYSQL_5_7).renderInlined( insertInto(table("tableA")) .columns(field("colA"), field("colB")) .values("val1", "val2") .onDuplicateKeyUpdate() .set(field("colA"), "something") .where(field("colC").eq("other"))); System.out.println(sql); } `` `insert into tableA (colA, colB) values ('val1', 'val2') on duplicate key update colA = 'something'` The WHERE clause and "colC" are never mentioned in the query. I'm might be inexperienced with SQL but I would expect and exception or at least a warning would be thrown if I'm doing something invalid or unsupported.

defect

where caluse missing when using insert on duplicate using jooq the following query prints public static void main string args throws sqlexception string sql dsl using sqldialect mysql renderinlined insertinto table tablea columns field cola field colb values onduplicatekeyupdate set field cola something where field colc eq other system out println sql insert into tablea cola colb values on duplicate key update cola something the where clause and colc are never mentioned in the query i m might be inexperienced with sql but i would expect and exception or at least a warning would be thrown if i m doing something invalid or unsupported

1

80,209

30,115,919,308

IssuesEvent

2023-06-30 11:30:13

vector-im/element-desktop

https://api.github.com/repos/vector-im/element-desktop

opened

CMD-plus does not increase the size of the text

T-Defect

### Steps to reproduce I wrongly reduced the size of the text by cmd-minus I tried to revert it by cmd-plus but does not work cmd-zero works to reset ### Outcome #### What did you expect? cmd-plus increase the size as opposite operation to cmd-minus #### What happened instead? nothing ### Operating system macOSX ### Application version Element Nightly version: 2023063001 Olm version: 3.2.14 ### How did you install the app? _No response_ ### Homeserver _No response_ ### Will you send logs? No

1.0

CMD-plus does not increase the size of the text - ### Steps to reproduce I wrongly reduced the size of the text by cmd-minus I tried to revert it by cmd-plus but does not work cmd-zero works to reset ### Outcome #### What did you expect? cmd-plus increase the size as opposite operation to cmd-minus #### What happened instead? nothing ### Operating system macOSX ### Application version Element Nightly version: 2023063001 Olm version: 3.2.14 ### How did you install the app? _No response_ ### Homeserver _No response_ ### Will you send logs? No

defect

cmd plus does not increase the size of the text steps to reproduce i wrongly reduced the size of the text by cmd minus i tried to revert it by cmd plus but does not work cmd zero works to reset outcome what did you expect cmd plus increase the size as opposite operation to cmd minus what happened instead nothing operating system macosx application version element nightly version olm version how did you install the app no response homeserver no response will you send logs no

1

18,431

3,060,510,995

IssuesEvent

2015-08-14 21:08:32

prettydiff/prettydiff

https://api.github.com/repos/prettydiff/prettydiff

closed

Nested rules not indented in SCSS

Defect Underway

Nested rules aren't indented in SCSS if the option to insert new lines between rules is checked. This only effects the nested rules that aren't the first on that level. Original: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Expected: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Actual: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ```

1.0

Nested rules not indented in SCSS - Nested rules aren't indented in SCSS if the option to insert new lines between rules is checked. This only effects the nested rules that aren't the first on that level. Original: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Expected: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ``` Actual: ```scss header .navbar-nav { float: none; } footer { .navbar { min-height: 25px; } .other-class { min-height: 25px; } .other-class-2 { min-height: 25px; } } ```

defect

nested rules not indented in scss nested rules aren t indented in scss if the option to insert new lines between rules is checked this only effects the nested rules that aren t the first on that level original scss header navbar nav float none footer navbar min height other class min height other class min height expected scss header navbar nav float none footer navbar min height other class min height other class min height actual scss header navbar nav float none footer navbar min height other class min height other class min height

1

328,036

28,099,353,456

IssuesEvent

2023-03-30 18:11:46

cockroachdb/cockroach

https://api.github.com/repos/cockroachdb/cockroach

closed

roachtest: sqlsmith/setup=seed/setting=no-ddl failed

C-test-failure O-robot O-roachtest T-sql-queries branch-release-23.1

roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on release-23.1 @ [aec78f33d45a8376a0ecec885688bae60dbfb85c](https://github.com/cockroachdb/cockroach/commits/aec78f33d45a8376a0ecec885688bae60dbfb85c): ``` test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1 (sqlsmith.go:244).func3: error: pq: internal error: regproc(): ResolveFunction unimplemented stmt: WITH "w'\\U00035ED1ith381" (col2573) AS (SELECT tab1110._bool AS col2573 FROM defaultdb.public.seed@[0] AS tab1110), "?wi%03th382" (col2574) AS ( SELECT 2990964997:::OID AS col2574 FROM defaultdb.public.seed@[0] AS "tab""1111", defaultdb.public.seed@seed__int8__float8__date_idx AS tab1112, "w'\\U00035ED1ith381" AS ".cte_ref102" ) SELECT regproc(e'z\\a).+A':::STRING::STRING)::REGPROC AS "cOl2575" FROM "?wi%03th382" AS "cte_r""ef103" ORDER BY "cte_r""ef103".col2574 DESC NULLS LAST, "cte_r""ef103".col2574, "cte_r""ef103".col2574 ASC NULLS FIRST LIMIT 23:::INT8; ``` Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=4</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> <details><summary>Help</summary> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </details> /cc @cockroachdb/sql-queries [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) Jira issue: CRDB-26184

2.0

roachtest: sqlsmith/setup=seed/setting=no-ddl failed - roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329923?buildTab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on release-23.1 @ [aec78f33d45a8376a0ecec885688bae60dbfb85c](https://github.com/cockroachdb/cockroach/commits/aec78f33d45a8376a0ecec885688bae60dbfb85c): ``` test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1 (sqlsmith.go:244).func3: error: pq: internal error: regproc(): ResolveFunction unimplemented stmt: WITH "w'\\U00035ED1ith381" (col2573) AS (SELECT tab1110._bool AS col2573 FROM defaultdb.public.seed@[0] AS tab1110), "?wi%03th382" (col2574) AS ( SELECT 2990964997:::OID AS col2574 FROM defaultdb.public.seed@[0] AS "tab""1111", defaultdb.public.seed@seed__int8__float8__date_idx AS tab1112, "w'\\U00035ED1ith381" AS ".cte_ref102" ) SELECT regproc(e'z\\a).+A':::STRING::STRING)::REGPROC AS "cOl2575" FROM "?wi%03th382" AS "cte_r""ef103" ORDER BY "cte_r""ef103".col2574 DESC NULLS LAST, "cte_r""ef103".col2574, "cte_r""ef103".col2574 ASC NULLS FIRST LIMIT 23:::INT8; ``` Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=4</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> <details><summary>Help</summary> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </details> /cc @cockroachdb/sql-queries [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) Jira issue: CRDB-26184

non_defect

roachtest sqlsmith setup seed setting no ddl failed roachtest sqlsmith setup seed setting no ddl with on release test artifacts and logs in artifacts sqlsmith setup seed setting no ddl run sqlsmith go error pq internal error regproc resolvefunction unimplemented stmt with w as select bool as from defaultdb public seed as wi as select oid as from defaultdb public seed as tab defaultdb public seed seed date idx as w as cte select regproc e z a a string string regproc as from wi as cte r order by cte r desc nulls last cte r cte r asc nulls first limit parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb sql queries jira issue crdb

0

621,596

19,592,558,646

IssuesEvent

2022-01-05 14:29:57

GameFreedomGG/Sindragosa

https://api.github.com/repos/GameFreedomGG/Sindragosa

closed

[Raid][NPC][Spell] Naxxramas - Gluth - Decimate

Raid Priority: High NPC Spell Status: Closed- Resolved Status: Confirmed Bug (Awaiting Development)

Decription: Gluthʼs decimate can one shot you. How it works: Gluthʼs decimate can deal more dmg to you then your actual HP. How it should work: Decimate: Reduce the current health of all nearby units (friendly or enemy) to 5% of their maximum health. Affects both players and zombies. Used approximately every 90 seconds. Source (you should point out proofs of your report, please give us some source): It occured during 10man Naxx. Screenshot from recount death recap: ![image](https://user-images.githubusercontent.com/95646548/144896325-a111aa6c-7fbf-428e-8a69-15bd3db79425.png)

1.0

[Raid][NPC][Spell] Naxxramas - Gluth - Decimate - Decription: Gluthʼs decimate can one shot you. How it works: Gluthʼs decimate can deal more dmg to you then your actual HP. How it should work: Decimate: Reduce the current health of all nearby units (friendly or enemy) to 5% of their maximum health. Affects both players and zombies. Used approximately every 90 seconds. Source (you should point out proofs of your report, please give us some source): It occured during 10man Naxx. Screenshot from recount death recap: ![image](https://user-images.githubusercontent.com/95646548/144896325-a111aa6c-7fbf-428e-8a69-15bd3db79425.png)

non_defect

naxxramas gluth decimate decription gluthʼs decimate can one shot you how it works gluthʼs decimate can deal more dmg to you then your actual hp how it should work decimate reduce the current health of all nearby units friendly or enemy to of their maximum health affects both players and zombies used approximately every seconds source you should point out proofs of your report please give us some source it occured during naxx screenshot from recount death recap

0

744,970

25,963,432,124

IssuesEvent

2022-12-19 03:15:58

FlutterFlow/flutterflow-issues

https://api.github.com/repos/FlutterFlow/flutterflow-issues

closed

Set value List<String> into a Custom Function

type: bug status: needs information priority: low

## Expected behavior (required) You can't click Confirm, because it says Available Options - List Contains Item. You should get "No further changes". ## Current behavior (required) You can't click Confirm nothing is happening and the value is not saved. ## To Reproduce (required) Steps to reproduce the behavior: 1. Create a Custom Function which has only one argument List<String> and it is returning the same List<String> value. 2. Create a Local State variable List<String> as well 3. Go to a Page - Click on a Text Widget and Click on Actions 4. Update Local State, Select the Local State that you just create, Set Value, From Variable 5. Choose the Custom Function you just created and then click on Confirm ## Context (required) You can't use this when using Custom Function with an argument of a List<String>. ## Screenshots / recordings  ## Your environment  * Version of FlutterFlow used: 3.0.5 * Platform (e.g. Web, MacOS Desktop): Web * Browser name and version: Chrome 106 * Operating system and version (desktop or mobile): desktop

1.0

Set value List<String> into a Custom Function - ## Expected behavior (required) You can't click Confirm, because it says Available Options - List Contains Item. You should get "No further changes". ## Current behavior (required) You can't click Confirm nothing is happening and the value is not saved. ## To Reproduce (required) Steps to reproduce the behavior: 1. Create a Custom Function which has only one argument List<String> and it is returning the same List<String> value. 2. Create a Local State variable List<String> as well 3. Go to a Page - Click on a Text Widget and Click on Actions 4. Update Local State, Select the Local State that you just create, Set Value, From Variable 5. Choose the Custom Function you just created and then click on Confirm ## Context (required) You can't use this when using Custom Function with an argument of a List<String>. ## Screenshots / recordings  ## Your environment  * Version of FlutterFlow used: 3.0.5 * Platform (e.g. Web, MacOS Desktop): Web * Browser name and version: Chrome 106 * Operating system and version (desktop or mobile): desktop

non_defect

set value list into a custom function expected behavior required you can t click confirm because it says available options list contains item you should get no further changes current behavior required you can t click confirm nothing is happening and the value is not saved to reproduce required steps to reproduce the behavior create a custom function which has only one argument list and it is returning the same list value create a local state variable list as well go to a page click on a text widget and click on actions update local state select the local state that you just create set value from variable choose the custom function you just created and then click on confirm context required you can t use this when using custom function with an argument of a list screenshots recordings your environment version of flutterflow used platform e g web macos desktop web browser name and version chrome operating system and version desktop or mobile desktop

0

72,276

24,031,687,948

IssuesEvent

2022-09-15 15:29:30

SeleniumHQ/selenium

https://api.github.com/repos/SeleniumHQ/selenium

closed

[🐛 Bug]: JS firefox driver crashes on setting a profile.

C-nodejs I-defect

### What happened? I want to use a custom firefox profile, so I set it according the [documentation](https://www.selenium.dev/selenium/docs/api/javascript/module/selenium-webdriver/firefox.html). However then my code crashes with the provided error. When I investigated why it is unable to serialize the object to JSON, I found `httpRequest.data` contains content of the specified firefox profile which is about 200MB in size and it reaches the maximum length of the string. However, the profile should be used for the browser, not be attached to the request body. Is it a bug, or I'm doing something wrong ? In python, using the custom profile works without problems. ### How can we reproduce the issue? ```shell const {By,Key,Builder} = require("selenium-webdriver"); const firefox = require('selenium-webdriver/firefox'); async function example(){ let profile = '/home/kabell/.mozilla/firefox/4rmepnvo.default-release'; let options = new firefox.Options().setProfile(profile); //To wait for browser to build and launch properly let driver = await new Builder().forBrowser("firefox").setFirefoxOptions(options).build(); //To fetch http://google.com from the browser with our code. await driver.get("http://google.com"); //It is always a safe practice to quit the browser after execution await driver.quit(); } example() ``` ### Relevant log output ```shell /home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132 data = JSON.stringify(httpRequest.data) ^ RangeError: Invalid string length at JSON.stringify (<anonymous>) at HttpClient.send (/home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132:19) at Executor.execute (/home/kabell/selenium/node_modules/selenium-webdriver/lib/http.js:470:33) ``` ``` ### Operating System Ubuntu ### Selenium version Javascript 4.1.1 ### What are the browser(s) and version(s) where you see this issue? Firefox 97 ### What are the browser driver(s) and version(s) where you see this issue? Geckodriver 0.30.0 ### Are you using Selenium Grid? _No response_

1.0

[🐛 Bug]: JS firefox driver crashes on setting a profile. - ### What happened? I want to use a custom firefox profile, so I set it according the [documentation](https://www.selenium.dev/selenium/docs/api/javascript/module/selenium-webdriver/firefox.html). However then my code crashes with the provided error. When I investigated why it is unable to serialize the object to JSON, I found `httpRequest.data` contains content of the specified firefox profile which is about 200MB in size and it reaches the maximum length of the string. However, the profile should be used for the browser, not be attached to the request body. Is it a bug, or I'm doing something wrong ? In python, using the custom profile works without problems. ### How can we reproduce the issue? ```shell const {By,Key,Builder} = require("selenium-webdriver"); const firefox = require('selenium-webdriver/firefox'); async function example(){ let profile = '/home/kabell/.mozilla/firefox/4rmepnvo.default-release'; let options = new firefox.Options().setProfile(profile); //To wait for browser to build and launch properly let driver = await new Builder().forBrowser("firefox").setFirefoxOptions(options).build(); //To fetch http://google.com from the browser with our code. await driver.get("http://google.com"); //It is always a safe practice to quit the browser after execution await driver.quit(); } example() ``` ### Relevant log output ```shell /home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132 data = JSON.stringify(httpRequest.data) ^ RangeError: Invalid string length at JSON.stringify (<anonymous>) at HttpClient.send (/home/kabell/selenium/node_modules/selenium-webdriver/http/index.js:132:19) at Executor.execute (/home/kabell/selenium/node_modules/selenium-webdriver/lib/http.js:470:33) ``` ``` ### Operating System Ubuntu ### Selenium version Javascript 4.1.1 ### What are the browser(s) and version(s) where you see this issue? Firefox 97 ### What are the browser driver(s) and version(s) where you see this issue? Geckodriver 0.30.0 ### Are you using Selenium Grid? _No response_

defect

js firefox driver crashes on setting a profile what happened i want to use a custom firefox profile so i set it according the however then my code crashes with the provided error when i investigated why it is unable to serialize the object to json i found httprequest data contains content of the specified firefox profile which is about in size and it reaches the maximum length of the string however the profile should be used for the browser not be attached to the request body is it a bug or i m doing something wrong in python using the custom profile works without problems how can we reproduce the issue shell const by key builder require selenium webdriver const firefox require selenium webdriver firefox async function example let profile home kabell mozilla firefox default release let options new firefox options setprofile profile to wait for browser to build and launch properly let driver await new builder forbrowser firefox setfirefoxoptions options build to fetch from the browser with our code await driver get it is always a safe practice to quit the browser after execution await driver quit example relevant log output shell home kabell selenium node modules selenium webdriver http index js data json stringify httprequest data rangeerror invalid string length at json stringify at httpclient send home kabell selenium node modules selenium webdriver http index js at executor execute home kabell selenium node modules selenium webdriver lib http js operating system ubuntu selenium version javascript what are the browser s and version s where you see this issue firefox what are the browser driver s and version s where you see this issue geckodriver are you using selenium grid no response

1

58,900

16,888,832,809

IssuesEvent

2021-06-23 06:31:38

openzfs/zfs

https://api.github.com/repos/openzfs/zfs

opened

#12145 breaks support for x32

Status: Triage Needed Type: Defect

### System information  Type | Version/Name --- | --- Distribution Name | N/A Distribution Version | N/A Linux Kernel | 5.12.12 Architecture | x86_64 (x32) ZFS Version | 2.1.0-rc7 SPL Version |  ### Describe the problem you're observing ``` make[3]: Entering directory '/home/harald/zfs/lib/libzpool' CCLD libzpool.la ld.lld: error: undefined symbol: atomic_load_64 >>> referenced by aggsum.c:119 (../../module/zfs/aggsum.c:119) >>> .libs/aggsum.o:(aggsum_lower_bound) >>> referenced by aggsum.c:125 (../../module/zfs/aggsum.c:125) >>> .libs/aggsum.o:(aggsum_upper_bound) >>> referenced by aggsum.c:218 (../../module/zfs/aggsum.c:218) >>> .libs/aggsum.o:(aggsum_compare) >>> referenced 1 more times ld.lld: error: undefined symbol: atomic_store_64 >>> referenced by aggsum.c:157 (../../module/zfs/aggsum.c:157) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:158 (../../module/zfs/aggsum.c:158) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:199 (../../module/zfs/aggsum.c:199) >>> .libs/aggsum.o:(aggsum_add) >>> referenced 3 more times clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [Makefile:1115: libzpool.la] Error 1 make[3]: Leaving directory '/home/harald/zfs/lib/libzpool' make[2]: *** [Makefile:701: all-recursive] Error 1 make[2]: Leaving directory '/home/harald/zfs/lib' make[1]: *** [Makefile:906: all-recursive] Error 1 make[1]: Leaving directory '/home/harald/zfs' make: *** [Makefile:767: all] Error 2 ``` ### Describe how to reproduce the problem Build with plain `./configure && make` on an x32 system. ### Include any warning/errors/backtraces from the system logs  N/A The problem is that on x32, `_LP64` is not defined so `atomic_load_64` gets declared as a function, but `atomic.c` does not get to define that function because x32 is still x86_64, so the assembly version `lib/libspl/asm-x86_64/atomic.S` is picked over `lib/libspl/asm-generic/atomic.c`. For x32, it should be fine to use the same macro using `volatile` that also gets defined for LP64 mode.

1.0

#12145 breaks support for x32 -   ### System information  Type | Version/Name --- | --- Distribution Name | N/A Distribution Version | N/A Linux Kernel | 5.12.12 Architecture | x86_64 (x32) ZFS Version | 2.1.0-rc7 SPL Version |  ### Describe the problem you're observing ``` make[3]: Entering directory '/home/harald/zfs/lib/libzpool' CCLD libzpool.la ld.lld: error: undefined symbol: atomic_load_64 >>> referenced by aggsum.c:119 (../../module/zfs/aggsum.c:119) >>> .libs/aggsum.o:(aggsum_lower_bound) >>> referenced by aggsum.c:125 (../../module/zfs/aggsum.c:125) >>> .libs/aggsum.o:(aggsum_upper_bound) >>> referenced by aggsum.c:218 (../../module/zfs/aggsum.c:218) >>> .libs/aggsum.o:(aggsum_compare) >>> referenced 1 more times ld.lld: error: undefined symbol: atomic_store_64 >>> referenced by aggsum.c:157 (../../module/zfs/aggsum.c:157) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:158 (../../module/zfs/aggsum.c:158) >>> .libs/aggsum.o:(aggsum_value) >>> referenced by aggsum.c:199 (../../module/zfs/aggsum.c:199) >>> .libs/aggsum.o:(aggsum_add) >>> referenced 3 more times clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [Makefile:1115: libzpool.la] Error 1 make[3]: Leaving directory '/home/harald/zfs/lib/libzpool' make[2]: *** [Makefile:701: all-recursive] Error 1 make[2]: Leaving directory '/home/harald/zfs/lib' make[1]: *** [Makefile:906: all-recursive] Error 1 make[1]: Leaving directory '/home/harald/zfs' make: *** [Makefile:767: all] Error 2 ``` ### Describe how to reproduce the problem Build with plain `./configure && make` on an x32 system. ### Include any warning/errors/backtraces from the system logs  N/A The problem is that on x32, `_LP64` is not defined so `atomic_load_64` gets declared as a function, but `atomic.c` does not get to define that function because x32 is still x86_64, so the assembly version `lib/libspl/asm-x86_64/atomic.S` is picked over `lib/libspl/asm-generic/atomic.c`. For x32, it should be fine to use the same macro using `volatile` that also gets defined for LP64 mode.

defect

breaks support for thank you for reporting an issue important please check our issue tracker before opening a new issue additional valuable information can be found in the openzfs documentation and mailing list archives please fill in as much of the template as possible system information type version name distribution name n a distribution version n a linux kernel architecture zfs version spl version commands to find zfs spl versions modinfo zfs grep iw version modinfo spl grep iw version describe the problem you re observing make entering directory home harald zfs lib libzpool ccld libzpool la ld lld error undefined symbol atomic load referenced by aggsum c module zfs aggsum c libs aggsum o aggsum lower bound referenced by aggsum c module zfs aggsum c libs aggsum o aggsum upper bound referenced by aggsum c module zfs aggsum c libs aggsum o aggsum compare referenced more times ld lld error undefined symbol atomic store referenced by aggsum c module zfs aggsum c libs aggsum o aggsum value referenced by aggsum c module zfs aggsum c libs aggsum o aggsum value referenced by aggsum c module zfs aggsum c libs aggsum o aggsum add referenced more times clang error linker command failed with exit code use v to see invocation make error make leaving directory home harald zfs lib libzpool make error make leaving directory home harald zfs lib make error make leaving directory home harald zfs make error describe how to reproduce the problem build with plain configure make on an system include any warning errors backtraces from the system logs important please mark logs and text output from terminal commands or else github will not display them correctly an example is provided below example this is an example how log text should be marked wrap it with n a the problem is that on is not defined so atomic load gets declared as a function but atomic c does not get to define that function because is still so the assembly version lib libspl asm atomic s is picked over lib libspl asm generic atomic c for it should be fine to use the same macro using volatile that also gets defined for mode

1

168,961

20,827,983,070

IssuesEvent

2022-03-19 01:11:41

snowdensb/caseflow

https://api.github.com/repos/snowdensb/caseflow

opened

CVE-2021-44906 (Medium) detected in multiple libraries

security vulnerability

## CVE-2021-44906 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - minimist-0.0.8.tgz, minimist-0.0.10.tgz, minimist-1.2.5.tgz, minimist-1.2.0.tgz</summary> <details><summary>minimist-0.0.8.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/mocha/node_modules/minimist/package.json Dependency Hierarchy: - mocha-5.2.0.tgz (Root Library) - mkdirp-0.5.1.tgz - :x: **minimist-0.0.8.tgz** (Vulnerable Library) </details> <details><summary>minimist-0.0.10.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/optimist/node_modules/minimist/package.json Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - optimist-0.6.1.tgz - :x: **minimist-0.0.10.tgz** (Vulnerable Library) </details> <details><summary>minimist-1.2.5.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/minimist/package.json Dependency Hierarchy: - core-7.13.15.tgz (Root Library) - json5-2.2.0.tgz - :x: **minimist-1.2.5.tgz** (Vulnerable Library) </details> <details><summary>minimist-1.2.0.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/karma-mocha/node_modules/minimist/package.json Dependency Hierarchy: - karma-mocha-1.3.0.tgz (Root Library) - :x: **minimist-1.2.0.tgz** (Vulnerable Library) </details> Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95). Publish Date: 2022-03-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (5.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a> Release Date: 2022-03-17 Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105 </details>

True

CVE-2021-44906 (Medium) detected in multiple libraries - ## CVE-2021-44906 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - minimist-0.0.8.tgz, minimist-0.0.10.tgz, minimist-1.2.5.tgz, minimist-1.2.0.tgz</summary> <details><summary>minimist-0.0.8.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/mocha/node_modules/minimist/package.json Dependency Hierarchy: - mocha-5.2.0.tgz (Root Library) - mkdirp-0.5.1.tgz - :x: **minimist-0.0.8.tgz** (Vulnerable Library) </details> <details><summary>minimist-0.0.10.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/optimist/node_modules/minimist/package.json Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - optimist-0.6.1.tgz - :x: **minimist-0.0.10.tgz** (Vulnerable Library) </details> <details><summary>minimist-1.2.5.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/minimist/package.json Dependency Hierarchy: - core-7.13.15.tgz (Root Library) - json5-2.2.0.tgz - :x: **minimist-1.2.5.tgz** (Vulnerable Library) </details> <details><summary>minimist-1.2.0.tgz</summary> parse argument options Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a> Path to dependency file: /client/package.json Path to vulnerable library: /client/node_modules/karma-mocha/node_modules/minimist/package.json Dependency Hierarchy: - karma-mocha-1.3.0.tgz (Root Library) - :x: **minimist-1.2.0.tgz** (Vulnerable Library) </details> Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95). Publish Date: 2022-03-17 URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (5.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a> Release Date: 2022-03-17 Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105 </details>

non_defect

cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries minimist tgz minimist tgz minimist tgz minimist tgz minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules mocha node modules minimist package json dependency hierarchy mocha tgz root library mkdirp tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules optimist node modules minimist package json dependency hierarchy karma tgz root library optimist tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules minimist package json dependency hierarchy core tgz root library tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file client package json path to vulnerable library client node modules karma mocha node modules minimist package json dependency hierarchy karma mocha tgz root library x minimist tgz vulnerable library found in base branch master vulnerability details minimist is vulnerable to prototype pollution via file index js function setkey lines publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree mocha mkdirp minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree karma optimist minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree babel core minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree karma mocha minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails minimist is vulnerable to prototype pollution via file index js function setkey lines vulnerabilityurl

0

48,711

13,184,722,926

IssuesEvent

2020-08-12 19:58:35

icecube-trac/tix3

https://api.github.com/repos/icecube-trac/tix3

opened

Python on Mac defaulting to system (Trac #90)

IceTray Incomplete Migration Migrated from Trac defect

<details> <summary>_Migrated from https://code.icecube.wisc.edu/ticket/90 , reported by cgils and owned by cgils_</summary> ```json { "status": "closed", "changetime": "2007-09-07T17:14:11", "description": "15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% ./examples/resources/scripts/pass1.py\n\n15:47 < blaufuss@> Fatal Python error: Interpreter not initialized (version mismatch?)\n\n15:47 < blaufuss@> Abort trap\n\n15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% which python\n\n15:47 < blaufuss@> /Users/blaufuss/icework/i3tools/bin/python\n\n15:47 < blaufuss@> I reproduce Georges error on teufel\n\n15:49 < gekolu > OK so I'm not totally mad :-)\n\n15:49 < drool@> hrm\n\n15:50 < blaufuss@> otool -L libithon.so\n\n15:50 < blaufuss@> /System/Library/Frameworks/Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current version 2.3.5)", "reporter": "cgils", "cc": "", "resolution": "fixed", "_ts": "1189185251000000", "component": "IceTray", "summary": "Python on Mac defaulting to system", "priority": "normal", "keywords": "", "time": "2007-08-13T19:58:05", "milestone": "", "owner": "cgils", "type": "defect" } ``` </details>

1.0

Python on Mac defaulting to system (Trac #90) - <details> <summary>_Migrated from https://code.icecube.wisc.edu/ticket/90 , reported by cgils and owned by cgils_</summary> ```json { "status": "closed", "changetime": "2007-09-07T17:14:11", "description": "15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% ./examples/resources/scripts/pass1.py\n\n15:47 < blaufuss@> Fatal Python error: Interpreter not initialized (version mismatch?)\n\n15:47 < blaufuss@> Abort trap\n\n15:47 < blaufuss@> blaufuss@teufel[~/..cework/offline/build](I3)% which python\n\n15:47 < blaufuss@> /Users/blaufuss/icework/i3tools/bin/python\n\n15:47 < blaufuss@> I reproduce Georges error on teufel\n\n15:49 < gekolu > OK so I'm not totally mad :-)\n\n15:49 < drool@> hrm\n\n15:50 < blaufuss@> otool -L libithon.so\n\n15:50 < blaufuss@> /System/Library/Frameworks/Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current version 2.3.5)", "reporter": "cgils", "cc": "", "resolution": "fixed", "_ts": "1189185251000000", "component": "IceTray", "summary": "Python on Mac defaulting to system", "priority": "normal", "keywords": "", "time": "2007-08-13T19:58:05", "milestone": "", "owner": "cgils", "type": "defect" } ``` </details>

defect

python on mac defaulting to system trac migrated from reported by cgils and owned by cgils json status closed changetime description blaufuss teufel examples resources scripts py n fatal python error interpreter not initialized version mismatch n abort trap n blaufuss teufel which python n users blaufuss icework bin python n i reproduce georges error on teufel n ok so i m not totally mad n hrm n otool l libithon so n system library frameworks python framework versions python compatibility version current version reporter cgils cc resolution fixed ts component icetray summary python on mac defaulting to system priority normal keywords time milestone owner cgils type defect

1

27,351

4,970,017,694

IssuesEvent

2016-12-05 15:00:11

cakephp/cakephp

https://api.github.com/repos/cakephp/cakephp

closed

"HTTP/1.1 400" is not valid header name

Defect On hold

This is a (multiple allowed): * [x] bug * [ ] enhancement * [ ] feature-discussion (RFC) * CakePHP Version: 3.3.8 * Platform and Target: nginx, postgres, phpleague/oauth2-server v.4, uafrica/oauth-server ### What you did GET request to a Cake controller which is declined by the OAuth server w/ 400 HTTP code. ### What happened The header returned by phpleague/oauth2-server HTTP/1.1 400 is invalidated by Zend\Diactoros I see "HTTP/1.1 400" is not valid header name ### What you expected to happen The header should not be invalidated and the regular 400 response should be returned.

1.0

"HTTP/1.1 400" is not valid header name - This is a (multiple allowed): * [x] bug * [ ] enhancement * [ ] feature-discussion (RFC) * CakePHP Version: 3.3.8 * Platform and Target: nginx, postgres, phpleague/oauth2-server v.4, uafrica/oauth-server ### What you did GET request to a Cake controller which is declined by the OAuth server w/ 400 HTTP code. ### What happened The header returned by phpleague/oauth2-server HTTP/1.1 400 is invalidated by Zend\Diactoros I see "HTTP/1.1 400" is not valid header name ### What you expected to happen The header should not be invalidated and the regular 400 response should be returned.

defect

http is not valid header name this is a multiple allowed bug enhancement feature discussion rfc cakephp version platform and target nginx postgres phpleague server v uafrica oauth server what you did get request to a cake controller which is declined by the oauth server w http code what happened the header returned by phpleague server http is invalidated by zend diactoros i see http is not valid header name what you expected to happen the header should not be invalidated and the regular response should be returned

1

51,781

13,211,305,868

IssuesEvent

2020-08-15 22:11:13

icecube-trac/tix4

https://api.github.com/repos/icecube-trac/tix4

opened

steamshovel - link errors on OSX (Trac #1036)

Incomplete Migration Migrated from Trac combo core defect

<details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1036">https://code.icecube.wisc.edu/projects/icecube/ticket/1036</a>, reported by negaand owned by nega</summary> ```json { "status": "closed", "changetime": "2015-06-29T19:43:17", "_ts": "1435606997623274", "description": "On OSX Mavericks+, `steamshovel` fails to build because `libshovelart` fails to link.\n\n{{{\nLinking CXX shared module ../lib/icecube/shovelart.so\nUndefined symbols for architecture x86_64:\n \"boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter>::dispose()\", referenced from:\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in PyArtist.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in Scenario.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in SceneObject.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in SceneVariant.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in Types.cpp.o\nld: symbol(s) not found for architecture x86_64\nclang: error: linker command failed with exit code 1 (use -v to see invocation)\nmake[2]: *** [lib/icecube/shovelart.so] Error 1\nmake[1]: *** [steamshovel/CMakeFiles/shovelart-pybindings.dir/all] Error 2\nmake: *** [all] Error 2\n}}}\n\n`::dispose()` is in pycompat.cpp which was remove from the build in r134357/IceCube.\nCombining diff:IceCube/projects/steamshovel/branches/new_shovelio/CMakeLists.txt@134353:134357 with diff:IceCube@134185:134188 demonstrates this fix.\n\nThis should be checked to ensure that re-including `pycompat.cpp` doesn't break something in recent commits.", "reporter": "nega", "cc": "hdembinski", "resolution": "fixed", "time": "2015-06-29T19:43:07", "component": "combo core", "summary": "steamshovel - link errors on OSX", "priority": "normal", "keywords": "", "milestone": "", "owner": "nega", "type": "defect" } ``` </details>

1.0

steamshovel - link errors on OSX (Trac #1036) - <details> <summary>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1036">https://code.icecube.wisc.edu/projects/icecube/ticket/1036</a>, reported by negaand owned by nega</summary> ```json { "status": "closed", "changetime": "2015-06-29T19:43:17", "_ts": "1435606997623274", "description": "On OSX Mavericks+, `steamshovel` fails to build because `libshovelart` fails to link.\n\n{{{\nLinking CXX shared module ../lib/icecube/shovelart.so\nUndefined symbols for architecture x86_64:\n \"boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter>::dispose()\", referenced from:\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in PyArtist.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in Scenario.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in SceneObject.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in SceneVariant.cpp.o\n vtable for boost::detail::sp_counted_impl_pd<void*, boost::python::converter::shared_ptr_deleter> in Types.cpp.o\nld: symbol(s) not found for architecture x86_64\nclang: error: linker command failed with exit code 1 (use -v to see invocation)\nmake[2]: *** [lib/icecube/shovelart.so] Error 1\nmake[1]: *** [steamshovel/CMakeFiles/shovelart-pybindings.dir/all] Error 2\nmake: *** [all] Error 2\n}}}\n\n`::dispose()` is in pycompat.cpp which was remove from the build in r134357/IceCube.\nCombining diff:IceCube/projects/steamshovel/branches/new_shovelio/CMakeLists.txt@134353:134357 with diff:IceCube@134185:134188 demonstrates this fix.\n\nThis should be checked to ensure that re-including `pycompat.cpp` doesn't break something in recent commits.", "reporter": "nega", "cc": "hdembinski", "resolution": "fixed", "time": "2015-06-29T19:43:07", "component": "combo core", "summary": "steamshovel - link errors on OSX", "priority": "normal", "keywords": "", "milestone": "", "owner": "nega", "type": "defect" } ``` </details>

defect

steamshovel link errors on osx trac migrated from json status closed changetime ts description on osx mavericks steamshovel fails to build because libshovelart fails to link n n nlinking cxx shared module lib icecube shovelart so nundefined symbols for architecture n boost detail sp counted impl pd dispose referenced from n vtable for boost detail sp counted impl pd in pyartist cpp o n vtable for boost detail sp counted impl pd in scenario cpp o n vtable for boost detail sp counted impl pd in sceneobject cpp o n vtable for boost detail sp counted impl pd in scenevariant cpp o n vtable for boost detail sp counted impl pd in types cpp o nld symbol s not found for architecture nclang error linker command failed with exit code use v to see invocation nmake error nmake error nmake error n n n dispose is in pycompat cpp which was remove from the build in icecube ncombining diff icecube projects steamshovel branches new shovelio cmakelists txt with diff icecube demonstrates this fix n nthis should be checked to ensure that re including pycompat cpp doesn t break something in recent commits reporter nega cc hdembinski resolution fixed time component combo core summary steamshovel link errors on osx priority normal keywords milestone owner nega type defect

1

9,380

8,616,060,374

IssuesEvent

2018-11-19 22:35:20

kyma-project/kyma

https://api.github.com/repos/kyma-project/kyma

closed

Service Binding failing for GCP service

area/service-catalog bug

**Description** Creating a service binding for a GCP service (Spanner) fails. Cluster version is 0.5 rc **Expected result** Service binding + usage is successfully created with using both the CLI and UI. **Actual result** Creating fails. The error message on the binding is the following: `Failed - ServiceBroker returned failure; bind operation will not be retried: Status: 422; ErrorMessage: <nil>; Description: This request requires client support for asynchronous service operations.; ResponseError: <nil> @ 2018-11-15 23:03:53 +0000 UTC ` **Steps to reproduce** 1. Provision an instance of the Spanner using kubectl ([spanner-instance.txt](https://github.com/kyma-project/kyma/files/2588582/spanner-instance.txt)) or svcat 2. Create a binding using the UI to a lambda function The binding will immediately fail. See screenshot below... ![service-binding-failure](https://user-images.githubusercontent.com/5688693/48611847-1a876780-e97f-11e8-939e-d6e66074acd1.png) **Troubleshooting**

1.0

Service Binding failing for GCP service -  **Description** Creating a service binding for a GCP service (Spanner) fails. Cluster version is 0.5 rc **Expected result** Service binding + usage is successfully created with using both the CLI and UI. **Actual result** Creating fails. The error message on the binding is the following: `Failed - ServiceBroker returned failure; bind operation will not be retried: Status: 422; ErrorMessage: <nil>; Description: This request requires client support for asynchronous service operations.; ResponseError: <nil> @ 2018-11-15 23:03:53 +0000 UTC ` **Steps to reproduce** 1. Provision an instance of the Spanner using kubectl ([spanner-instance.txt](https://github.com/kyma-project/kyma/files/2588582/spanner-instance.txt)) or svcat 2. Create a binding using the UI to a lambda function The binding will immediately fail. See screenshot below... ![service-binding-failure](https://user-images.githubusercontent.com/5688693/48611847-1a876780-e97f-11e8-939e-d6e66074acd1.png) **Troubleshooting**

non_defect

service binding failing for gcp service thank you for your contribution before you submit the issue search open and closed issues for duplicates read the contributing guidelines description creating a service binding for a gcp service spanner fails cluster version is rc expected result service binding usage is successfully created with using both the cli and ui actual result creating fails the error message on the binding is the following failed servicebroker returned failure bind operation will not be retried status errormessage description this request requires client support for asynchronous service operations responseerror utc steps to reproduce provision an instance of the spanner using kubectl or svcat create a binding using the ui to a lambda function the binding will immediately fail see screenshot below troubleshooting

0

580,210

17,212,941,959

IssuesEvent

2021-07-19 07:52:56

nextcloud/calendar

https://api.github.com/repos/nextcloud/calendar

opened

Attendees can move and change scheduling object copies in their calendars

1 - to develop bug priority

https://datatracker.ietf.org/doc/html/rfc6638#section-3.2.2.1 shows which actions a client should be able to take on a scheduling object. We're currently allowing an attendee to edit calendar scheduling objects for their own private calendars - i. e., they can move and edit an event they are invited to. This does not propagate to the server, which is correct. The UI should reflect this.

1.0

Attendees can move and change scheduling object copies in their calendars - https://datatracker.ietf.org/doc/html/rfc6638#section-3.2.2.1 shows which actions a client should be able to take on a scheduling object. We're currently allowing an attendee to edit calendar scheduling objects for their own private calendars - i. e., they can move and edit an event they are invited to. This does not propagate to the server, which is correct. The UI should reflect this.

non_defect

attendees can move and change scheduling object copies in their calendars shows which actions a client should be able to take on a scheduling object we re currently allowing an attendee to edit calendar scheduling objects for their own private calendars i e they can move and edit an event they are invited to this does not propagate to the server which is correct the ui should reflect this

0

10,021

2,618,931,292

IssuesEvent

2015-03-03 00:00:22

chrsmith/open-ig

https://api.github.com/repos/chrsmith/open-ig

closed

Garthogs seem to be too strong even on easy difficulty

auto-migrated Balance Milestone-0.95.200 Priority-High Type-Defect

``` Reported by sailorshark, Nov 25, 2012 "7. Mire eljutottam oda, hogy neki támadjak (2427 dec.) egy Garthog bolygónak igencsak nagy meglepetés ért, hiszen 3 űrállomással 4 2-es szintű löveggel és bolygópajzsal kerültem szembe, ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet. Néztem végigjáttszás videót eredetiről és abban a Garthogok nem voltak ennyire legyőzhetetlenek. Bolgyóbajzs nem is volt és katonai űrállomás sem." Apparently, the Garthogs deploy defenses too quickly. I need to observe what the AI does. ``` Original issue reported on code.google.com by `akarn...@gmail.com` on 4 Dec 2012 at 2:51

1.0

Garthogs seem to be too strong even on easy difficulty - ``` Reported by sailorshark, Nov 25, 2012 "7. Mire eljutottam oda, hogy neki támadjak (2427 dec.) egy Garthog bolygónak igencsak nagy meglepetés ért, hiszen 3 űrállomással 4 2-es szintű löveggel és bolygópajzsal kerültem szembe, ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet. Néztem végigjáttszás videót eredetiről és abban a Garthogok nem voltak ennyire legyőzhetetlenek. Bolgyóbajzs nem is volt és katonai űrállomás sem." Apparently, the Garthogs deploy defenses too quickly. I need to observe what the AI does. ``` Original issue reported on code.google.com by `akarn...@gmail.com` on 4 Dec 2012 at 2:51

defect

garthogs seem to be too strong even on easy difficulty reported by sailorshark nov mire eljutottam oda hogy neki támadjak dec egy garthog bolygónak igencsak nagy meglepetés ért hiszen űrállomással es szintű löveggel és bolygópajzsal kerültem szembe ami az adott szinten elérhető legjobb fejlesztésekkel felszerelt maxra húzott flottával is igen kétséges kimetelű lehet néztem végigjáttszás videót eredetiről és abban a garthogok nem voltak ennyire legyőzhetetlenek bolgyóbajzs nem is volt és katonai űrállomás sem apparently the garthogs deploy defenses too quickly i need to observe what the ai does original issue reported on code google com by akarn gmail com on dec at

1

4,843

2,610,158,109

IssuesEvent

2015-02-26 18:50:11

chrsmith/republic-at-war

https://api.github.com/repos/chrsmith/republic-at-war

closed

Map Issue

auto-migrated Priority-Medium Type-Defect

``` Fix passability on Tatooine ``` ----- Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:58

1.0

Map Issue - ``` Fix passability on Tatooine ``` ----- Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:58

defect

map issue fix passability on tatooine original issue reported on code google com by gmail com on jan at

1

36,598

8,028,957,574

IssuesEvent

2018-07-27 14:33:28

catmaid/CATMAID

https://api.github.com/repos/catmaid/CATMAID

closed

3D viewer: serialized node scaling is not properly reloaded

context: 3d-viewer difficulty: low status: done type: defect

Node scaling is serialized and deserialized into the controls correctly, but is not applied (i.e., is still default) until modifying the control field.

1.0

3D viewer: serialized node scaling is not properly reloaded - Node scaling is serialized and deserialized into the controls correctly, but is not applied (i.e., is still default) until modifying the control field.

defect

viewer serialized node scaling is not properly reloaded node scaling is serialized and deserialized into the controls correctly but is not applied i e is still default until modifying the control field

1

431,668

12,484,732,944

IssuesEvent

2020-05-30 16:10:29

spectrochempy/test_issues_migration_from_redmine

https://api.github.com/repos/spectrochempy/test_issues_migration_from_redmine

opened

Maker a Docker build, for an easy an portable installation.

Category: Deployment Priority: Minor Project: SpectroChemPy Status: In Progress Tracker: Task

Author: Christian Fernandez (Christian Fernandez ) Redmine Issue: 7, https://redmine.spectrochempy.fr/issues/7 --- Pytest ne s.execute pas. Pas trouve encore pourquoi warning pytest tests/ ============================= test session starts ============================== platform linux -- Python 3.7.1, pytest-4.0.2, py-1.7.0, pluggy-0.8.0 -- /opt/conda/bin/python cachedir: .pytest_cache rootdir: /opt/atlassian/pipelines/agent/build/tests, inifile: pytest.ini plugins: console-scripts-0.1.5 collecting ... Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4 Finished scanning for test reports. Found 0 test report files. Merged test suites, total number tests is 0, with 0 failures and 0 errors.

1.0

Maker a Docker build, for an easy an portable installation. - Author: Christian Fernandez (Christian Fernandez ) Redmine Issue: 7, https://redmine.spectrochempy.fr/issues/7 --- Pytest ne s.execute pas. Pas trouve encore pourquoi warning pytest tests/ ============================= test session starts ============================== platform linux -- Python 3.7.1, pytest-4.0.2, py-1.7.0, pluggy-0.8.0 -- /opt/conda/bin/python cachedir: .pytest_cache rootdir: /opt/atlassian/pipelines/agent/build/tests, inifile: pytest.ini plugins: console-scripts-0.1.5 collecting ... Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4 Finished scanning for test reports. Found 0 test report files. Merged test suites, total number tests is 0, with 0 failures and 0 errors.

non_defect

maker a docker build for an easy an portable installation author christian fernandez christian fernandez redmine issue pytest ne s execute pas pas trouve encore pourquoi warning pytest tests test session starts platform linux python pytest py pluggy opt conda bin python cachedir pytest cache rootdir opt atlassian pipelines agent build tests inifile pytest ini plugins console scripts collecting searching for test report files in directories named down to a depth of finished scanning for test reports found test report files merged test suites total number tests is with failures and errors

0

79,621

28,485,027,214

IssuesEvent

2023-04-18 07:14:12

hazelcast/hazelcast

https://api.github.com/repos/hazelcast/hazelcast

closed

No backup flag is passed to getRecordOrNull method in lock interceptor operation [HZ-2287]

Type: Defect Team: Core Module: IMap Module: Lock to-jira

Issue makes itself visible by publishing multiple events for expiration of a single key, normally it must be 1. With this defect, number of events for a single key is same with number of replicas(owner+backup) in this case. **Workaround:** Using cp-subsystem locking instead of imap locking fixes the issue.

1.0

No backup flag is passed to getRecordOrNull method in lock interceptor operation [HZ-2287] - Issue makes itself visible by publishing multiple events for expiration of a single key, normally it must be 1. With this defect, number of events for a single key is same with number of replicas(owner+backup) in this case. **Workaround:** Using cp-subsystem locking instead of imap locking fixes the issue.

defect

no backup flag is passed to getrecordornull method in lock interceptor operation issue makes itself visible by publishing multiple events for expiration of a single key normally it must be with this defect number of events for a single key is same with number of replicas owner backup in this case workaround using cp subsystem locking instead of imap locking fixes the issue

1

12,041

14,214,351,298

IssuesEvent

2020-11-17 05:00:58

ice1000/jimgui

https://api.github.com/repos/ice1000/jimgui

closed

Ubuntu 16.04 support?

compatibility

I've tried jimgui on windows 10 64bit and everything worked perfectly, today I tried on Ubuntu 16.04 64bit but I can't run it. I get the error: > java.lang.UnsupportedOperationException: java.lang.UnsatisfiedLinkError: /tmp/jimgui1605317730496/libjimgui.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/jimgui1605317730496/libjimgui.so) I think it's because on ubuntu 16.04 glibc version 2.23 is used. Does this mean jimgui only supports >=Ubuntu18?

True

Ubuntu 16.04 support? - I've tried jimgui on windows 10 64bit and everything worked perfectly, today I tried on Ubuntu 16.04 64bit but I can't run it. I get the error: > java.lang.UnsupportedOperationException: java.lang.UnsatisfiedLinkError: /tmp/jimgui1605317730496/libjimgui.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/jimgui1605317730496/libjimgui.so) I think it's because on ubuntu 16.04 glibc version 2.23 is used. Does this mean jimgui only supports >=Ubuntu18?

non_defect

ubuntu support i ve tried jimgui on windows and everything worked perfectly today i tried on ubuntu but i can t run it i get the error java lang unsupportedoperationexception java lang unsatisfiedlinkerror tmp libjimgui so lib linux gnu libm so version glibc not found required by tmp libjimgui so i think it s because on ubuntu glibc version is used does this mean jimgui only supports

0

48,832

12,247,361,308

IssuesEvent

2020-05-05 15:46:45

GoogleCloudPlatform/python-docs-samples

https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples

closed

iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed

api: cloudiot buildcop: flaky buildcop: issue priority: p2 type: bug

iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed buildID: 48f7af782874d6a51ce4b361ccde2da3bc075ffa buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31 status: failed

2.0

iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed - iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed buildID: 48f7af782874d6a51ce4b361ccde2da3bc075ffa buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31 status: failed

non_defect

iot api client mqtt example cloudiot mqtt example test test gateway send data for device failed iot api client mqtt example cloudiot mqtt example test test gateway send data for device failed buildid buildurl status failed

0

27,231

4,939,525,681

IssuesEvent

2016-11-29 14:37:49

jfabry/LiveRobotProgramming

https://api.github.com/repos/jfabry/LiveRobotProgramming

closed

Import of a program that does not parse crashes the interpreter

Component-Parser Priority-High Type-Defect

We should check in LRPProgram>>exportedMachines and loadImports if the current ast is not a failure

1.0

Import of a program that does not parse crashes the interpreter - We should check in LRPProgram>>exportedMachines and loadImports if the current ast is not a failure

defect

import of a program that does not parse crashes the interpreter we should check in lrpprogram exportedmachines and loadimports if the current ast is not a failure

1

64,214

18,280,374,863

IssuesEvent

2021-10-05 01:58:30

microsoft/STL

https://api.github.com/repos/microsoft/STL

opened

P2432R1 Fix `istream_view`

cxx20 ranges defect report

[P2432R1](https://wg21.link/P2432R1) Fix `istream_view` This paper intentionally does not provide a feature-test macro.

1.0

P2432R1 Fix `istream_view` - [P2432R1](https://wg21.link/P2432R1) Fix `istream_view` This paper intentionally does not provide a feature-test macro.

defect

fix istream view fix istream view this paper intentionally does not provide a feature test macro

1

57,025

15,595,420,550

IssuesEvent

2021-03-18 14:52:35

department-of-veterans-affairs/va.gov-cms

https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms

closed

field_office on Vet Center Locations List should only allow vet_center content type, not MVC, OS, or CAP

Content model Defect Vet Center

**Describe the defect** Vet Center entity reference on Locations List should only allow _Vet Center_ content type. **To Reproduce** Steps to reproduce the behavior: 1. Go to /node/16478/edit 2. In the Vet Center entity reference field, you will see Outstations and Mobile Vet Centers **Expected behavior** Only Vet Centers should be visible (no outstations or mobile vet centers or CAPs) **Implementation** Config at /admin/structure/types/manage/vet_center_locations_list/fields/node.vet_center_locations_list.field_office

1.0

field_office on Vet Center Locations List should only allow vet_center content type, not MVC, OS, or CAP - **Describe the defect** Vet Center entity reference on Locations List should only allow _Vet Center_ content type. **To Reproduce** Steps to reproduce the behavior: 1. Go to /node/16478/edit 2. In the Vet Center entity reference field, you will see Outstations and Mobile Vet Centers **Expected behavior** Only Vet Centers should be visible (no outstations or mobile vet centers or CAPs) **Implementation** Config at /admin/structure/types/manage/vet_center_locations_list/fields/node.vet_center_locations_list.field_office

defect

field office on vet center locations list should only allow vet center content type not mvc os or cap describe the defect vet center entity reference on locations list should only allow vet center content type to reproduce steps to reproduce the behavior go to node edit in the vet center entity reference field you will see outstations and mobile vet centers expected behavior only vet centers should be visible no outstations or mobile vet centers or caps implementation config at admin structure types manage vet center locations list fields node vet center locations list field office

1

76,900

21,609,252,350

IssuesEvent

2022-05-04 08:23:22

cryspen/hacl-packages

https://api.github.com/repos/cryspen/hacl-packages

closed

Feature parity with upstream dist

build 🔨

Tracking build feature parity with the upstream hacl* dist directory.

1.0

Feature parity with upstream dist - Tracking build feature parity with the upstream hacl* dist directory.

non_defect

feature parity with upstream dist tracking build feature parity with the upstream hacl dist directory

0

48,741

25,787,899,596

IssuesEvent

2022-12-09 22:46:37

model-checking/kani

https://api.github.com/repos/model-checking/kani

closed

Memory reallocation with `Vec` kills performance

[C] Bug [E] Performance T-CBMC

This example is from #1651, implemented using a vector:  ```rust const N: usize = 4; const M: usize = N+1; trait T { fn foo(&self) -> i32; } struct A { x: i32, } impl T for A { fn foo(&self) -> i32 { self.x } } struct B { x: i32, } impl T for B { fn foo(&self) -> i32 { self.x } } #[kani::proof] #[kani::unwind(6)] fn main() { //let mut a: Vec<Box<dyn T>> = Vec::with_capacity(N); let mut a: Vec<Box<dyn T>> = Vec::new(); a.push(Box::new(A { x: 5 })); for i in 1..N { a.push(Box::new(B { x: 9 })); } let mut val: i32 = 0; for _i in 0..M { let index: usize = kani::any(); kani::assume(index < a.len()); let x = a[index].as_mut().foo(); val += x; } } ``` with Kani version: d53296ac3fb When the vector is created with `Vec::with_capacity` to pre-allocate memory, verification time is 3.2 seconds, and consumes less than 1 GB of memory. But when using `Vec::new()`, verification takes 160 seconds, and consumes more than 14 GB of memory. If I bump `N` to 5 (and the unwind value to 7), the `Vec::with_capacity` version finishes in 7 seconds, and consumes less than 1 GB, and the `Vec::new` version runs out of memory (>32 GB) after running for about 3 minutes.

True

Memory reallocation with `Vec` kills performance -   This example is from #1651, implemented using a vector:  ```rust const N: usize = 4; const M: usize = N+1; trait T { fn foo(&self) -> i32; } struct A { x: i32, } impl T for A { fn foo(&self) -> i32 { self.x } } struct B { x: i32, } impl T for B { fn foo(&self) -> i32 { self.x } } #[kani::proof] #[kani::unwind(6)] fn main() { //let mut a: Vec<Box<dyn T>> = Vec::with_capacity(N); let mut a: Vec<Box<dyn T>> = Vec::new(); a.push(Box::new(A { x: 5 })); for i in 1..N { a.push(Box::new(B { x: 9 })); } let mut val: i32 = 0; for _i in 0..M { let index: usize = kani::any(); kani::assume(index < a.len()); let x = a[index].as_mut().foo(); val += x; } } ``` with Kani version: d53296ac3fb When the vector is created with `Vec::with_capacity` to pre-allocate memory, verification time is 3.2 seconds, and consumes less than 1 GB of memory. But when using `Vec::new()`, verification takes 160 seconds, and consumes more than 14 GB of memory. If I bump `N` to 5 (and the unwind value to 7), the `Vec::with_capacity` version finishes in 7 seconds, and consumes less than 1 GB, and the `Vec::new` version runs out of memory (>32 GB) after running for about 3 minutes.

non_defect

memory reallocation with vec kills performance if this is a security issue please report it following the thank you for filing a bug report 🐛 please provide a short summary of the issue along with the information necessary to replicate this example is from implemented using a vector if the reproducing code is small please post it here otherwise please attach the relevant files to this issue alternatively post a link to the repository and branch that exposes the issue rust const n usize const m usize n trait t fn foo self struct a x impl t for a fn foo self self x struct b x impl t for b fn foo self self x fn main let mut a vec vec with capacity n let mut a vec vec new a push box new a x for i in n a push box new b x let mut val for i in m let index usize kani any kani assume index a len let x a as mut foo val x with kani version when the vector is created with vec with capacity to pre allocate memory verification time is seconds and consumes less than gb of memory but when using vec new verification takes seconds and consumes more than gb of memory if i bump n to and the unwind value to the vec with capacity version finishes in seconds and consumes less than gb and the vec new version runs out of memory gb after running for about minutes

0

224,457

17,188,988,531

IssuesEvent

2021-07-16 08:14:06

capactio/capact

https://api.github.com/repos/capactio/capact

closed

Add quality badges to the repository README

area/community area/documentation enhancement size/XS

## Description - Generate quality badges: - [Github Actions](https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge) - https://goreportcard.com/ - https://bestpractices.coreinfrastructure.org/en - Consider Snyk and CodeClimate badges - Check our score and fix detected issues Timeboxed task, we do as much as we can in a given time. ## Reason Show that we follow best practices during Capact development and that we do care about the quality of the project.

1.0

Add quality badges to the repository README - ## Description - Generate quality badges: - [Github Actions](https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge) - https://goreportcard.com/ - https://bestpractices.coreinfrastructure.org/en - Consider Snyk and CodeClimate badges - Check our score and fix detected issues Timeboxed task, we do as much as we can in a given time. ## Reason Show that we follow best practices during Capact development and that we do care about the quality of the project.

non_defect

add quality badges to the repository readme description generate quality badges consider snyk and codeclimate badges check our score and fix detected issues timeboxed task we do as much as we can in a given time reason show that we follow best practices during capact development and that we do care about the quality of the project

0

69,902

22,744,619,423

IssuesEvent

2022-07-07 08:04:47

melink14/rikaikun

https://api.github.com/repos/melink14/rikaikun

closed

Error message

Type-Defect auto-migrated P2 obsolete

``` I've been trying to save words into file using Rikaichan, but seem to always get this error: Error while saving: [Exception..."Component returned failure code 0x800040005" (NS_ERROR_FAILURE) [nslFileOutputStream.init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: Chrome://rikaichan/content/ricaichan.js :: anonymous :: line 697" data:no] Any idea what might be wrong? ``` Original issue reported on code.google.com by `joshuagi...@yahoo.co.uk` on 16 Aug 2013 at 4:33

1.0

Error message - ``` I've been trying to save words into file using Rikaichan, but seem to always get this error: Error while saving: [Exception..."Component returned failure code 0x800040005" (NS_ERROR_FAILURE) [nslFileOutputStream.init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: Chrome://rikaichan/content/ricaichan.js :: anonymous :: line 697" data:no] Any idea what might be wrong? ``` Original issue reported on code.google.com by `joshuagi...@yahoo.co.uk` on 16 Aug 2013 at 4:33

defect

error message i ve been trying to save words into file using rikaichan but seem to always get this error error while saving exception component returned failure code ns error failure nsresult ns error failure location js frame chrome rikaichan content ricaichan js anonymous line data no any idea what might be wrong original issue reported on code google com by joshuagi yahoo co uk on aug at

1

79,218

28,045,877,127

IssuesEvent

2023-03-28 22:50:29

cliffparnitzky/ApparelManager

https://api.github.com/repos/cliffparnitzky/ApparelManager

closed

Using a visibility toggle without a "data-state" attribute is deprecated.

Defect ✓ - Accepted

Using a visibility toggle without a "data-state" attribute is deprecated. Please adjust your Contao DCA file.

1.0

Using a visibility toggle without a "data-state" attribute is deprecated. - Using a visibility toggle without a "data-state" attribute is deprecated. Please adjust your Contao DCA file.

defect

using a visibility toggle without a data state attribute is deprecated using a visibility toggle without a data state attribute is deprecated please adjust your contao dca file

1

10,915

2,622,847,876

IssuesEvent

2015-03-04 08:03:33

max99x/pagemon-chrome-ext

https://api.github.com/repos/max99x/pagemon-chrome-ext

closed

Still detecting change

auto-migrated Priority-Medium Type-Defect

``` Extension is still reporting changed page, even if there is only minor changes. http://wmmania.cz/clanky/android/ On bottom of page is time and number of queries, that is different on every reload. So I use Custom-mode - selector functionality with #article_list>div.article:nth-child(1)>div.heading>h3 On test button, it gives me only name of first article. But after a hour or two it mark page as changed. But only highlighted change, is time on page bottom. Thanks for help ``` Original issue reported on code.google.com by `hund...@gmail.com` on 22 Dec 2010 at 1:04

1.0

Still detecting change - ``` Extension is still reporting changed page, even if there is only minor changes. http://wmmania.cz/clanky/android/ On bottom of page is time and number of queries, that is different on every reload. So I use Custom-mode - selector functionality with #article_list>div.article:nth-child(1)>div.heading>h3 On test button, it gives me only name of first article. But after a hour or two it mark page as changed. But only highlighted change, is time on page bottom. Thanks for help ``` Original issue reported on code.google.com by `hund...@gmail.com` on 22 Dec 2010 at 1:04

defect

still detecting change extension is still reporting changed page even if there is only minor changes on bottom of page is time and number of queries that is different on every reload so i use custom mode selector functionality with article list div article nth child div heading on test button it gives me only name of first article but after a hour or two it mark page as changed but only highlighted change is time on page bottom thanks for help original issue reported on code google com by hund gmail com on dec at

1

38,610

8,933,332,043

IssuesEvent

2019-01-23 01:32:28

Microsoft/spring-data-cosmosdb

https://api.github.com/repos/Microsoft/spring-data-cosmosdb

closed

exception when integrate with spring data commons 2.1.x

Defect

``` Caused by: java.lang.IllegalStateException: You have defined query method in the repository but you don't have any query lookup strategy defined. The infrastructure apparently does not support query methods! at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.<init>(RepositoryFactorySupport.java:545) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.getNullable(Lazy.java:211) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.get(Lazy.java:94) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] ```

1.0

exception when integrate with spring data commons 2.1.x - ``` Caused by: java.lang.IllegalStateException: You have defined query method in the repository but you don't have any query lookup strategy defined. The infrastructure apparently does not support query methods! at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.<init>(RepositoryFactorySupport.java:545) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.getNullable(Lazy.java:211) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] at org.springframework.data.util.Lazy.get(Lazy.java:94) ~[spring-data-commons-2.1.2.RELEASE.jar!/:2.1.2.RELEASE] ```

defect

exception when integrate with spring data commons x caused by java lang illegalstateexception you have defined query method in the repository but you don t have any query lookup strategy defined the infrastructure apparently does not support query methods at org springframework data repository core support repositoryfactorysupport queryexecutormethodinterceptor repositoryfactorysupport java at org springframework data repository core support repositoryfactorysupport getrepository repositoryfactorysupport java at org springframework data repository core support repositoryfactorybeansupport lambda afterpropertiesset repositoryfactorybeansupport java at org springframework data util lazy getnullable lazy java at org springframework data util lazy get lazy java

1

10,486

2,622,167,569

IssuesEvent

2015-03-04 00:13:04

byzhang/rapidjson

https://api.github.com/repos/byzhang/rapidjson

closed

Does not compile on Embarcadero tools.

auto-migrated Priority-Medium Type-Defect

``` What steps will reproduce the problem? 1. Include the headers in a cpp file. 2. Try to compile it with the Embarcadero command line compiler. What is the expected output? What do you see instead? Expecting to see it compile. Instead, it failed to compile giving several error messages. ... Error E2450 include\rapidjson/document.h 30: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 30: Size of 'name' is unknown or zero Error E2450 include\rapidjson/document.h 31: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 31: Size of 'value' is unknown or zero ... What version of the product are you using? On what operating system? Version 0.1 on Windows 7 Please provide any additional information below. I've tried in the ancient 5.5 version of the compiler by Borland and the new one from Embarcadero. ``` Original issue reported on code.google.com by `odhinnsr...@gmail.com` on 29 Mar 2012 at 5:14

1.0

Does not compile on Embarcadero tools. - ``` What steps will reproduce the problem? 1. Include the headers in a cpp file. 2. Try to compile it with the Embarcadero command line compiler. What is the expected output? What do you see instead? Expecting to see it compile. Instead, it failed to compile giving several error messages. ... Error E2450 include\rapidjson/document.h 30: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 30: Size of 'name' is unknown or zero Error E2450 include\rapidjson/document.h 31: Undefined structure 'GenericValue<Encoding,Allocator>' Error E2449 include\rapidjson/document.h 31: Size of 'value' is unknown or zero ... What version of the product are you using? On what operating system? Version 0.1 on Windows 7 Please provide any additional information below. I've tried in the ancient 5.5 version of the compiler by Borland and the new one from Embarcadero. ``` Original issue reported on code.google.com by `odhinnsr...@gmail.com` on 29 Mar 2012 at 5:14

defect

does not compile on embarcadero tools what steps will reproduce the problem include the headers in a cpp file try to compile it with the embarcadero command line compiler what is the expected output what do you see instead expecting to see it compile instead it failed to compile giving several error messages error include rapidjson document h undefined structure genericvalue error include rapidjson document h size of name is unknown or zero error include rapidjson document h undefined structure genericvalue error include rapidjson document h size of value is unknown or zero what version of the product are you using on what operating system version on windows please provide any additional information below i ve tried in the ancient version of the compiler by borland and the new one from embarcadero original issue reported on code google com by odhinnsr gmail com on mar at

1

48,001

13,067,375,743

IssuesEvent

2020-07-31 00:15:34

icecube-trac/tix2

https://api.github.com/repos/icecube-trac/tix2

closed

icerec, simulation - remove dst-extractor from meta-projects (Trac #1614)

Migrated from Trac cmake defect

according to #1571 `dst-extractor` is no more Migrated from https://code.icecube.wisc.edu/ticket/1614 ```json { "status": "closed", "changetime": "2019-02-13T14:11:42", "description": "according to #1579 `dst-extractor` is no more", "reporter": "nega", "cc": "olivas", "resolution": "fixed", "_ts": "1550067102580394", "component": "cmake", "summary": "icerec, simulation - remove dst-extractor from meta-projects", "priority": "normal", "keywords": "", "time": "2016-03-30T21:00:35", "milestone": "", "owner": "nega", "type": "defect" } ```

1.0

icerec, simulation - remove dst-extractor from meta-projects (Trac #1614) - according to #1571 `dst-extractor` is no more Migrated from https://code.icecube.wisc.edu/ticket/1614 ```json { "status": "closed", "changetime": "2019-02-13T14:11:42", "description": "according to #1579 `dst-extractor` is no more", "reporter": "nega", "cc": "olivas", "resolution": "fixed", "_ts": "1550067102580394", "component": "cmake", "summary": "icerec, simulation - remove dst-extractor from meta-projects", "priority": "normal", "keywords": "", "time": "2016-03-30T21:00:35", "milestone": "", "owner": "nega", "type": "defect" } ```

defect

icerec simulation remove dst extractor from meta projects trac according to dst extractor is no more migrated from json status closed changetime description according to dst extractor is no more reporter nega cc olivas resolution fixed ts component cmake summary icerec simulation remove dst extractor from meta projects priority normal keywords time milestone owner nega type defect

1

2,889

2,607,964,661

IssuesEvent

2015-02-26 00:41:47

chrsmithdemos/leveldb

https://api.github.com/repos/chrsmithdemos/leveldb

closed

Lots of zero-size files in ENOSP situation

auto-migrated Priority-Medium Type-Defect

``` This is just a FYI. We've seen this odd behavior, when running out of disk space. In this particular LevelDB instance, we had ~500.000 files, of which ~386.000 were zero-length. Let me know if you want more info for further investigation if you find this relevant. Kresten ^count ^byte size 8986 2100454 8986 2099630 8988 2097214 3 2031616 8986 1141855 8986 817817 8987 796603 8987 786279 8988 679909 8986 675593 8986 622029 8987 549499 8986 545361 8988 543867 8986 483052 2 458752 8987 270322 2 196608 8987 173884 5 65536 386412 0 ``` ----- Original issue reported on code.google.com by `kresten....@gmail.com` on 22 Dec 2011 at 4:39

1.0

Lots of zero-size files in ENOSP situation - ``` This is just a FYI. We've seen this odd behavior, when running out of disk space. In this particular LevelDB instance, we had ~500.000 files, of which ~386.000 were zero-length. Let me know if you want more info for further investigation if you find this relevant. Kresten ^count ^byte size 8986 2100454 8986 2099630 8988 2097214 3 2031616 8986 1141855 8986 817817 8987 796603 8987 786279 8988 679909 8986 675593 8986 622029 8987 549499 8986 545361 8988 543867 8986 483052 2 458752 8987 270322 2 196608 8987 173884 5 65536 386412 0 ``` ----- Original issue reported on code.google.com by `kresten....@gmail.com` on 22 Dec 2011 at 4:39

defect

lots of zero size files in enosp situation this is just a fyi we ve seen this odd behavior when running out of disk space in this particular leveldb instance we had files of which were zero length let me know if you want more info for further investigation if you find this relevant kresten count byte size original issue reported on code google com by kresten gmail com on dec at

1

225,665

24,881,083,849

IssuesEvent

2022-10-28 01:11:34

mgh3326/createandread

https://api.github.com/repos/mgh3326/createandread

closed

WS-2022-0334 (Medium) detected in nokogiri-1.10.7.gem - autoclosed

security vulnerability

## WS-2022-0334 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - nokogiri-1.10.7.gem</summary> Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri's many features is the ability to search documents via XPath or CSS3 selectors. Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.7.gem">https://rubygems.org/gems/nokogiri-1.10.7.gem</a> Path to dependency file: /Gemfile.lock Path to vulnerable library: /var/lib/gems/2.3.0/cache/nokogiri-1.10.7-x64-mingw32.gem Dependency Hierarchy: - rails-6.0.1.gem (Root Library) - actiontext-6.0.1.gem - :x: **nokogiri-1.10.7.gem** (Vulnerable Library) Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> nokogiri up to and including 1.13.8 is affected by several vulnerabilities (CVE-2022-40303, CVE-2022-40304 and CVE-2022-2309) in the dependency bundled libxml2 library. Version 1.13.9 of nokogiri contains a patch where the dependency is upgraded with the patches as well. Publish Date: 2022-10-18 URL: <a href=https://github.com/sparklemotion/nokogiri/commit/e8cfe13953c63099f879d8a25ca70a909e19fb96>WS-2022-0334</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (5.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://github.com/advisories/GHSA-2qc6-mcvw-92cw">https://github.com/advisories/GHSA-2qc6-mcvw-92cw</a> Release Date: 2022-10-18 Fix Resolution: nokogiri - 1.13.9 </details> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

WS-2022-0334 (Medium) detected in nokogiri-1.10.7.gem - autoclosed - ## WS-2022-0334 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - nokogiri-1.10.7.gem</summary> Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri's many features is the ability to search documents via XPath or CSS3 selectors. Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.7.gem">https://rubygems.org/gems/nokogiri-1.10.7.gem</a> Path to dependency file: /Gemfile.lock Path to vulnerable library: /var/lib/gems/2.3.0/cache/nokogiri-1.10.7-x64-mingw32.gem Dependency Hierarchy: - rails-6.0.1.gem (Root Library) - actiontext-6.0.1.gem - :x: **nokogiri-1.10.7.gem** (Vulnerable Library) Found in base branch: master </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> nokogiri up to and including 1.13.8 is affected by several vulnerabilities (CVE-2022-40303, CVE-2022-40304 and CVE-2022-2309) in the dependency bundled libxml2 library. Version 1.13.9 of nokogiri contains a patch where the dependency is upgraded with the patches as well. Publish Date: 2022-10-18 URL: <a href=https://github.com/sparklemotion/nokogiri/commit/e8cfe13953c63099f879d8a25ca70a909e19fb96>WS-2022-0334</a> </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (5.5)</summary> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </details> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> Type: Upgrade version Origin: <a href="https://github.com/advisories/GHSA-2qc6-mcvw-92cw">https://github.com/advisories/GHSA-2qc6-mcvw-92cw</a> Release Date: 2022-10-18 Fix Resolution: nokogiri - 1.13.9 </details> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

non_defect

ws medium detected in nokogiri gem autoclosed ws medium severity vulnerability vulnerable library nokogiri gem nokogiri 鋸 is an html xml sax and reader parser among nokogiri s many features is the ability to search documents via xpath or selectors library home page a href path to dependency file gemfile lock path to vulnerable library var lib gems cache nokogiri gem dependency hierarchy rails gem root library actiontext gem x nokogiri gem vulnerable library found in base branch master vulnerability details nokogiri up to and including is affected by several vulnerabilities cve cve and cve in the dependency bundled library version of nokogiri contains a patch where the dependency is upgraded with the patches as well publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nokogiri step up your open source security game with mend

0

40,533

10,036,131,737

IssuesEvent

2019-07-18 09:55:21

ShaikASK/Testing

https://api.github.com/repos/ShaikASK/Testing

opened

Candidate : Dashboard : Double space is observed in between words of last Step in the last line

Candidate Dashboard Candidate Module Defect P3

Steps To Replicate : 1.Launch the URL 2.Sign in as Candidate 3.Click on “Get Started” button 4.Sign the Offer Letter 5.fill the common details webform 6.fill the required documents and navigate to “dashboard Screen 7.Check the alignment of step description displayed at candidate dashboard Experienced Behavior : Observed that Candidate : Dashboard : Double space is observed in between words of last Step in the last line (Refer Screen Shot) Expected Behavior : Ensure that it should not display double spacing between words of last Step in the last line ![UI issue](https://user-images.githubusercontent.com/31955617/61448239-26915200-a970-11e9-8256-8ed4a0668701.jpg)

1.0

Candidate : Dashboard : Double space is observed in between words of last Step in the last line - Steps To Replicate : 1.Launch the URL 2.Sign in as Candidate 3.Click on “Get Started” button 4.Sign the Offer Letter 5.fill the common details webform 6.fill the required documents and navigate to “dashboard Screen 7.Check the alignment of step description displayed at candidate dashboard Experienced Behavior : Observed that Candidate : Dashboard : Double space is observed in between words of last Step in the last line (Refer Screen Shot) Expected Behavior : Ensure that it should not display double spacing between words of last Step in the last line ![UI issue](https://user-images.githubusercontent.com/31955617/61448239-26915200-a970-11e9-8256-8ed4a0668701.jpg)

defect

candidate dashboard double space is observed in between words of last step in the last line steps to replicate launch the url sign in as candidate click on “get started” button sign the offer letter fill the common details webform fill the required documents and navigate to “dashboard screen check the alignment of step description displayed at candidate dashboard experienced behavior observed that candidate dashboard double space is observed in between words of last step in the last line refer screen shot expected behavior ensure that it should not display double spacing between words of last step in the last line

1