{
	"id": "170395",
	"key": "DAEMON-173",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "12519",
			"key": "DAEMON",
			"name": "Appcelerator Daemon"
		},
		"fixVersions": [
			{
				"id": "18407",
				"description": "",
				"name": "Appc Daemon 1.0.0",
				"archived": false,
				"released": true,
				"releaseDate": "2017-12-05"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2017-11-21T20:02:48.000+0000",
		"created": "2017-11-20T16:51:08.000+0000",
		"priority": {
			"name": "Critical",
			"id": "1"
		},
		"labels": [],
		"versions": [
			{
				"id": "18407",
				"description": "",
				"name": "Appc Daemon 1.0.0",
				"archived": false,
				"released": true,
				"releaseDate": "2017-12-05"
			}
		],
		"issuelinks": [],
		"assignee": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"updated": "2017-11-21T20:02:48.000+0000",
		"status": {
			"description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.",
			"name": "Resolved",
			"id": "5",
			"statusCategory": {
				"id": 3,
				"key": "done",
				"colorName": "green",
				"name": "Done"
			}
		},
		"components": [
			{
				"id": "15625",
				"name": "appcd-plugin-windows"
			}
		],
		"description": "h5.Description\r\n\r\nWhen running appcd exec /system-info/1.x/info/ it seemed to be taking longer than usual to return, checking the logs I saw the below, I think it's possible that two detect processes are attempting to build wptool at the same time. We apparently deal with this inside windowslib but it seems to be flaky, it might be wise to stagger the detects to allow one to build before the other runs\r\n\r\nI've had trouble reproducing this in an appc cli build fwiw\r\n\r\n{code}\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error Caught exception: Error: EBUSY: resource busy or locked, open 'C:\\Users\\ewan\\Documents\\git\\appc-daemon\\node_modules\\windowslib\\bin\\wptool.exe'\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at Object.fs.openSync (fs.js:646:18)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at Object.fs.writeFileSync (fs.js:1291:33)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at Object.callback (C:\\Users\\ewan\\Documents\\git\\appc-daemon\\node_modules\\windowslib\\lib\\wptool.js:596:7)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at C:\\Users\\ewan\\Documents\\git\\appc-daemon\\node_modules\\windowslib\\lib\\visualstudio.js:423:9\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at Array.forEach (<anonymous>)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at ChildProcess.<anonymous> (C:\\Users\\ewan\\Documents\\git\\appc-daemon\\node_modules\\windowslib\\lib\\visualstudio.js:415:11)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at emitTwo (events.js:126:13)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at ChildProcess.emit (events.js:214:7)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at maybeClose (internal/child_process.js:925:16)\r\n2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)\r\n{code}\r\n\r\nh5.Steps to reproduce\r\n\r\n# Remove wptool.exe from windowslib/bin folder\r\n# Start the daemon {{[appc] appcd start}}\r\n# Query system info {{[appc] appcd exec /system-info/1.x/info/}}\r\n\r\nh5.Actual\r\n\r\nPlugin hangs, windows error above shown in logs\r\n\r\nh5.Expected\r\n\r\nNo hang",
		"attachment": [],
		"flagged": false,
		"summary": "windowslib: EBUSY error on wptool executable",
		"creator": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"subtasks": [],
		"reporter": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"environment": null,
		"closedSprints": [
			{
				"id": 976,
				"state": "closed",
				"name": "2017 Sprint 24 Tooling",
				"startDate": "2017-11-19T19:00:51.738Z",
				"endDate": "2017-12-03T19:00:00.000Z",
				"completeDate": "2017-12-04T23:20:34.438Z",
				"originBoardId": 219
			}
		],
		"comment": {
			"comments": [
				{
					"id": "431058",
					"author": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "FYI, I ran into a similar problem on Linux with invoking a freshly download Node.js executable where I was getting an {{EBUSY}} error. I worked around it by implementing a try again loop: https://github.com/appcelerator/appc-daemon/blob/master/packages/appcd-nodejs/src/nodejs.js#L440.",
					"updateAuthor": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2017-11-20T21:18:33.000+0000",
					"updated": "2017-11-20T21:18:33.000+0000"
				}
			],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}