id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
4 |
DAEMON-18
|
02/04/2016 00:45:27
|
@appcd/plugin-amplify: AMPLIFY platform daemon plugin
|
The AMPLIFY Platform appcd plugin (@appcd/plugin-amplify) is responsible for authentication. It contains services authenticating against Axway ID and retrieving, refreshing, and invalidating access tokens. This plugin eventually will also contain the entitlements service.
| 13 |
5 |
DAEMON-28
|
02/04/2016 03:36:23
|
@appcd/plugin-amplify: Authentication service
|
The AMPLIFY platform appcd plugin will use the amplify-platform-sdk to perform authentication. This service will also automatically refresh access tokens.
| 13 |
6 |
DAEMON-10
|
02/04/2016 07:42:44
|
jdklib v2
|
jdklib is responsible for detecting the installed Java development environment. jdklib needs to expose the new detect friendly interface, namely separating the search paths from the actual detection code.
| 5 |
7 |
DAEMON-11
|
02/04/2016 08:31:14
|
appcd: Support for --config and --config-file options
|
It would be useful if the appcd cli supported a {{\-\-config}} and {{\-\-config\-file}} options for the "start" and "restart" commands.
| 8 |
8 |
DAEMON-13
|
05/05/2016 08:29:39
|
appcd: Fix source/user agent support
|
For analytics, the daemon records the client's "user agent". This feature is currently implemented, but it's named "userAgent" which was determined to be misleading. We need a better term to describe this feature and a way to describe a client type, description, and version, possibly as a string instead of an object. NPM has a user agent string that looks like {{npm/2.15.1 node/v4.4.3 darwin x64}}.
| 3 |
9 |
DAEMON-3
|
05/05/2016 08:59:36
|
node-ios-device: Re-run node-pre-gyp if binding doesn't exist
|
node-ios-device v0.9.0 uses node-pre-gyp. When it is npm installed, node-pre-gyp downloads the pre-compiled binary. However, if the system Node.js version is changed, then node-pre-gyp needs to be re-run. In order for this to work, node-pre-gyp must be executed synchronously.
| 8 |
10 |
DAEMON-6
|
05/07/2016 07:27:59
|
appcd: Filesystem watcher
|
androidlib, ioslib, jdklib, and windowslib need a filesystem monitoring library that can be notified when a specific path changes. Node has a built-in {{fs.watch()}} function which works fine on Linux and Windows, but doesn't work well on OS X where it doesn't report the correct file path. This can be fixed by using the {{fsevents}} module. The {{chokidar}} module comes close to solving this need, but I discovered two blocking bugs: one with watching paths that do not exist and one with nested paths. It also currently has 39 open issues, some of which are a little scary sounding. Additionally, {{chokidar}} uses {{readdirp}} which apparently has performance issues due to all of the file stating.
| 13 |
11 |
DAEMON-32
|
08/30/2016 01:53:30
|
Windows: jdklib v2 - If you move your JDK while running jdklib.watch(), then "TypeError: Path must be a string" error is returned
|
*Details:* On Windows, if you move your JDK while running jdklib.watch(), then {{TypeError: Path must be a string}} error is returned. *Notes:* This is not reproducible with JDK on Mac. *Steps to reproduce:* # Make sure you are using Node 4.X.X on Windows # Clone and run {{npm install}} on https://github.com/appcelerator/jdklib # Symlink to the above built jdklib v2 # Run this Node script: {code} 'use strict'; const jdklib = require('jdklib'); jdklib .watch() .on('results', results => { console.log(JSON.stringify(results, null, 4)); }); {code} # Find your JDK and move it *Actual:* {{TypeError: Path must be a string}} error is returned: {code} TypeError: Path must be a string. Received null at assertPath (path.js:8:11) at Object.win32.join (path.js:221:5) at Watcher.onChange (C:\Users\qe\Desktop\something\node_modules\jdklib\node_modules\node-appc\dist\fs.js:270:19) at emitTwo (events.js:87:13) at FSWatcher.emit (events.js:172:7) at FSEvent.FSWatcher._handle.onchange (fs.js:1221:12) {code} *Expected:* No errors should be returned while watching the JDK.
| 1 |
12 |
DAEMON-33
|
08/31/2016 00:47:08
|
Windows: androidlib v2 - If you call androidlib.detect(), then an empty array is returned for the results
|
*Details:* If you make a androidlib.detect(), then an empty array is returned for the results. *Notes:* * This does not appear on Mac. * ANDROID_SDK environment variable is set. * Android SDK tools and platform-tools are set in the PATH. *Steps to reproduce:* # Make sure you are using Node 4.X.X # Clone and run {{npm install}} on https://github.com/appcelerator/androidlib/tree/v2; make sure it's v2 branch # Symlink to the above built androidlib v2 # Run this Node script: {code} 'use strict'; // NOTE: currently, symlinked node_modules/androidlib folder to a built local copy of https://github.com/appcelerator/androidlib/tree/v2 const androidlib = require('androidlib').androidlib; androidlib .detect() .then(results => { console.log(JSON.stringify(results, null, 4)); }) .catch('error', err => { console.log(err.stack); }); {code} *Actual:* An empty array appears for SDK. {code} C:\Users\qe\Desktop\libautomator>node test.js { "home": "C:\\Users\\qe\\.android\\avd", "sdk": [], "ndk": [] } {code} *Expected:* There should not be an empty array for SDK.
| 1 |
13 |
DAEMON-29
|
10/21/2016 23:38:00
|
appcd status: Add support for --json option
|
The {{appcd status}} command needs to support outputting the status in a human readable "report" format as well as JSON format. Currently only the JSON output is supported.
| 5 |
14 |
DAEMON-30
|
10/21/2016 23:47:16
|
appcd status: Display the correct status if the daemon is not running
|
If the Appc Daemon is not running and you run {{appcd status}}, it outputs: {code} Error: connect ECONNREFUSED 127.0.0.1:1732 {code} It should output a more readable error for both "report" and "json" output modes.
| 5 |
15 |
DAEMON-31
|
10/25/2016 22:48:41
|
Allow for multiple requests over the same WebSocket connection
|
Currently the Appc Daemon only allows a single request over a single WebSocket connection. This encourages clients to establish multiple simultaneous connections. This is technically unnecessary. The Appc Daemon should not close the socket when a request ends, but rather send a "request closed" message and let the client determine if it should close the connection. Be sure to update the wiki page under the "Node.js Client" section: https://wiki.appcelerator.org/display/Daemon/Appcd+Client.
| 5 |
16 |
DAEMON-35
|
10/31/2016 17:23:53
|
appcd-core: Replace "pidusage" with "process.cpuUsage()"
|
The daemon uses a NPM module called "pidusage" to monitor the CPU usage, but this is no longer necessary since Node 6 includes a built-in {{process.cpuUsage()}} function. https://nodejs.org/dist/latest-v6.x/docs/api/process.html#process_process_cpuusage_previousvalue Aside from removing a dependency, it's going to be more efficient to use Node's built-in {{process.cpuUsage()}} because "pidusage" relies on file I/O and spawning {{ps}} and {{wmic}}.
| 5 |
17 |
DAEMON-36
|
12/05/2016 20:03:04
|
node-appc: fs watch doesn't properly handle symlinks
|
The filesystem watch function doesn't properly handle symlinks. It doesn't check if a file/directory is a symlink. The problem is when there's a symlinked directory to a parent directory or a directory that is being watched. The fs watcher needs to detect a symlinked directory, then watch the real path, not the symlink. We still need to track the symlink directory, but it needs to make sure that changes to the real path are propagated to the watcher of the original path.
| 13 |
18 |
DAEMON-39
|
02/14/2017 04:04:30
|
appcd: Create 'package' task for top-level gulp file
|
The appcd daemon is made up of the bootstrap, core, a bunch of micro packages, and a bunch of plugins. While each of these can be published individually to NPM, it might be better to generate a pseudo "appcd" package that combines all of the appcd-* {{package.json}} files together. This would save hundreds of MB of hard drive space. Furthermore, we may want to take it a step further and declare the bootstrap, core, micro packages, and plugins as "bundledDependencies" and include them in the package. This would allow us to only publish "appcd" to npm instead of dozens of modules every release. This would also make locking down versions much easier.
| 13 |
19 |
DAEMON-40
|
02/17/2017 02:02:57
|
appcd-nodejs: Need to download signed node executable on macOS
|
Downloading the node executable in the tarball is not signed and shows a dialog if the firewall is enabled, which is going to be often. Instead, we need to download the pkg installer and manually extract the node executable.
| 5 |
20 |
DAEMON-41
|
02/17/2017 05:07:43
|
appcd-nodejs: Add unit tests
|
Need to create unit tests for appcd-nodejs.
| 8 |
21 |
DAEMON-42
|
02/17/2017 05:09:22
|
appcd-http: Add default served root
|
appcd-http needs a default served root just in case one is not specified when a web server is started.
| 2 |
22 |
DAEMON-43
|
02/17/2017 05:20:13
|
Create CI script
|
The Appc Daemon needs a Jenkinsfile script that: * Installs Node 7.6.0 or newer * Installs NPM * Installs Yarn * Clone appc-daemon repo * Runs: {{yarn}} * Runs: {{gulp check}} * Runs: {{gulp coverage}} * Runs: {{gulp package}} * Generates report from "check" output, "coverage" output, and package output and also includes build information * Stores the report in some cloud-based data store See https://github.com/appcelerator/client-generator/blob/master/Jenkinsfile for an example. Also see https://github.com/appcelerator/jenkins_dsl/blob/master/jobs/appc_cli.groovy. -To build the bundled distribution which includes all NPM dependencies, we will need to kick off a Jenkins job on multiple slave Jenkins machines to bundle platform specific bundles. Each Jenkins slave would run {{gulp package-bundle}} instead of {{gulp-package}}, then upload the resulting tarball to Axway's Artifactory server (and possibly also S3 as a backup). We need 5 Jenkins slaves: OS X (64-bit), 64-bit Windows, 32-bit Windows, 64-bit Linux, and 32-bit Linux.- The platform specific bundling has been moved to DAEMON-77. The report generation has been moved to DAEMON-78.
| 5 |
23 |
DAEMON-44
|
02/17/2017 05:26:18
|
appcd-http: Port implementation from prototype
|
Add the webserver and router from prototype to the appcd-http library.
| 8 |
24 |
DAEMON-45
|
02/17/2017 05:31:28
|
appcd-http: Add unit tests
|
The appcd-http package has some unit tests, but code coverage is lacking.
| 8 |
25 |
DAEMON-46
|
02/17/2017 05:35:25
|
appcd-*: Replace use of 'temp' module with 'tmp'
|
In an attempt to standardize on a temp directory/file library, ensure we are using the tmp (https://www.npmjs.com/package/tmp) module.
| 2 |
26 |
DAEMON-47
|
02/17/2017 05:44:43
|
Remove dependency on 'optional-dev-dependency'
|
As a way to deal with dependency management, appcd uses "optional-dev-dependency", specifically when the plan was to publish each micro-package as a separate NPM module. However, with the introduction of the {{gulp package}} task and the use of yarn links, there's no need for the "optional-dev-dependency" module anymore.
| 2 |
27 |
DAEMON-50
|
02/17/2017 23:37:05
|
appcd-response: Add i18n system
|
The Appc Daemon currently does not have any sort of i18n facilities unlike the Titanium CLI. This should be solvable using a logger middleware and a gulp task to generate the i18n files.
| 5 |
28 |
DAEMON-51
|
02/22/2017 00:33:41
|
appcd-dispatcher: Add Koa middleware function
|
Instead of having the daemon patch web requests into the dispatcher, just have the dispatcher return a Koa middleware that allows appcd-dispatcher to just do the routing.
| 5 |
29 |
DAEMON-52
|
02/22/2017 00:37:23
|
Start/restart daemon when watching in dev mode
|
To speed up development, it would be nice if the gulp watch task would restart the daemon when it detects a file has changed and has rebuilt the packages.
| 3 |
30 |
DAEMON-53
|
02/22/2017 00:51:14
|
Root coverage task should not stop on failures
|
When running {{gulp coverage}} in the root, we should run each package's coverage tests and continue even if one or more fail, then at the very end do the {{process.exit(1)}}.
| 2 |
31 |
DAEMON-55
|
02/23/2017 19:43:54
|
appcd: Add Retire.js to the 'gulp check' task
|
The {{gulp check}} currently only checks NSP for security issues. It is also desired to use Retire.js (https://retirejs.github.io/retire.js/). We need to add Retire.js to the {{gulp check}} task and update the JSON results. It is preferred to use Retire.js programmatically instead of subprocessing it, though I'm not sure if that's feasible. Also note that Retire.js and NSP overlap and it would be ideal to unify the results and eliminate duplicates.
| 8 |
32 |
DAEMON-57
|
02/27/2017 17:05:22
|
appcd: Add support to config handler to change settings at runtime
|
The config handler currently only returns the config. The handler should also support a "data" payload to change the daemon's config at runtime. Note that only a single config setting can be changed per call. Use the path to determine what is being changed. HTTP methods can be used to determine how the key should be changed. The handler returns the new value. Use the status code to determine if successful. The appcd CLI is responsible for persisting the settings to the user's config file {{~/.appcelerator/appcd/config.json}}. The daemon does not modify the config file. The appcd CLI will validate the config change, then persist it to disk. After that, it will check if the daemon is running and attempt to change it at runtime. If the daemon is not running or it is running and the setting is changeable during runtime, then everything succeeds. If the daemon is running and the change is rejected, then the CLI will alert the user that the daemon must be restarted for the setting to take effect. If the CLI as a TTY, it can prompt to restart the daemon. Note that the CLI should also support a {{\-\-no\-prompt}} flag and a {{\-\-auto\-restart}} flag. h4. Examples: h5. Getting a value: {code} appcd exec /appcd/config/analytics/enabled appcd exec /appcd/config/analytics/enabled '{ "action": "get" }' appcd exec /appcd/config '{ "action": "get", "key": "/analytics/enabled" }' appcd exec /appcd/config '{ "action": "get", "key": "analytics.enabled" }' {code} h5. Setting a value: {code} appcd exec /appcd/config '{ "action": "set", "key": "analytics.enabled", "value": true }' appcd exec /appcd/config/analytics/enabled '{ "action": "set", "value": true }' {code} h5. Deleting a value: {code} appcd exec /appcd/config '{ "action": "delete", "key": "analytics.enabled" }' appcd exec /appcd/config/analytics/enabled '{ "action": "delete" }' {code} h5. Array examples: {code} appcd exec /appcd/config '{ "action": "set", "key": "foo", "value": ["bar", "baz"] }' {code} Delete will remove the entire value. {code} appcd exec /appcd/config '{ "action": "delete", "key": "foo" }' {code}
| 5 |
33 |
DAEMON-58
|
02/27/2017 20:37:02
|
appcd-core: Bump Node version to 8.x (when it is released)
|
We want to bump the Node.js version of appcd-core's {{package.json}} to the latest v8.x LTS release once it ships in October 2017. In addition, the following dependencies must also be updated to take advantage of the new features of Node 8: * appcd-http: [email protected]
| 2 |
34 |
DAEMON-60
|
03/10/2017 23:27:33
|
appcd-dispatcher: Add ServiceDispatcher unit tests
|
The {{ServiceDispatcher}} needs some unit test love.
| 8 |
35 |
DAEMON-61
|
03/18/2017 00:55:06
|
appcd-response: Create unified message and code library
|
With error codes all over the place, we need a central place to store them. We also have a need for i18n. So, appcd-response can fulfill both requirements.
| 13 |
36 |
DAEMON-62
|
03/18/2017 00:58:06
|
appcd-response: Create base error object with messages integration
|
There are several errors being thrown around inside the Appc Daemon and we need a unified error object that can pull i18n strings by code or by message.
| 13 |
37 |
DAEMON-63
|
03/18/2017 01:02:16
|
Move dependency-map.json into each package's package.json
|
The {{dependency-map.json}} is a file that maps micro-package dependencies together so they can be linked with yarn. The problem is this file is becoming exceedingly large. It's time to break it up and put each package's dependencies in their {{package.json}}. Note that this is not the same as NPM dependencies, so we may need a {{appcd-depenedencies}} property in the {{package.json}}.
| 3 |
38 |
DAEMON-64
|
03/18/2017 01:11:18
|
appcd-http: Need a unified response object
|
Right now HTTP responses require a status and body. However we will want to specify a response using a code that looks up the appropriate message and sets the actual response status and body. We also want this response object to handle the content type. This does not apply to requests for data. This only applies to requests like subscribing or registering something where we have a real message that can be internationalized.
| 13 |
39 |
DAEMON-65
|
03/22/2017 18:47:00
|
appcd-response: Improve i18n API
|
appcd-response handles single strings only. It will probably be handy to create {{\_\_()}} and {{\_\_n()}} functions to expose the i18n engine for single strings and pluralized strings. Strings are stored in a {{messages/<locale>/strings.json}} file where the key is the English text and the value is the translated text. We should just follow https://github.com/mashpie/i18n-node and allow the value to be an array where the first element is the singular string and the second element is the plural string.
| 3 |
40 |
DAEMON-67
|
03/23/2017 06:21:36
|
appcd: Logcat crashes daemon
|
Running {{appcd logcat}} causes the daemon to have a bad day.
| 5 |
41 |
DAEMON-69
|
03/29/2017 20:25:05
|
appcd: Implement subscription requests from appcd CLI
|
{{appcd exec}} currently only supports dispatching "call" requests. It does not support "subscribe" requests. {{appcd exec}} needs a {{\-\-subscribe}} flag. When the {{\-\-subscribe}} flag is set, it will pass a "type" of "subscribe" with the request, then the {{appcd exec}} command will need to properly not exit until the connection is closed or the {{fin}} event is emitted.
| 5 |
42 |
DAEMON-70
|
04/10/2017 20:42:32
|
appcd-core: Drop priviledges and set uid/gid if root
|
In Node, you can only change the user id if Node is launched as root. If the user launching the daemon is root, it would be essential that root privileges be dropped as soon as possible during the daemon initialization. To check if the daemon is being run as root, check if {{process.getuid() === 0}}. If the uid is zero, then get the uid/gid from in the config and call {{process.setuid()}} and/or {{process.setgid()}}. If there is no uid/gid in the config or the uid/gid is invalid, then the daemon should fatal error and exit. Note that this only applies to macOS and Linux.
| 2 |
43 |
DAEMON-72
|
04/11/2017 22:51:13
|
appcd-core: Support for user-defined config file
|
The daemon needs to support a user-defined config file. This file should live at {{~/.appcelerator/appcd/config.json}}. This user-defined config file overrides the default config defined by the Appc Daemon. This user-defined config file is written whenever a setting is changed via {{appcd config}} or a request to {{/appcd/config}}.
| 5 |
44 |
DAEMON-77
|
05/04/2017 21:49:47
|
appcd: Extend CI process to create platform-specific bundles
|
The current Jenkinsfile introduced by DAEMON-43 runs check and coverage tasks, then bundles the daemon distribution without NPM dependencies. DAEMON-56 introduces a {{gulp package-bundle}} that will run {{npm install}} and re-package the daemon distribution tgz file. This ticket is to add the {{gulp package-bundle}} to the CI process where it is executed on the following 5 Jenkins slave machines: * macOS * 64-bit Windows * 32-bit Windows * 64-bit Linux * 32-bit Linux The resulting tgz file is to be uploaded as an artifact of the CI job.
| 1 |
45 |
DAEMON-79
|
05/08/2017 21:35:23
|
appcd-subprocess: Add IPC support
|
We need the ability to set up an IPC channel with a spawned process. The way this will work starts by passing a {{ipc: true}} in the dispatcher request payload. This will cause the spawn to force the connection use file descriptor 3 as an IPC channel. The caller receives the subprocess descriptor: {{ctx.proc}}. It extends an event emitter, so you can listen for {{"message"}} and send using {{ctx.proc.send()}}.
| 5 |
46 |
DAEMON-80
|
05/09/2017 05:31:06
|
appcd-agent: Implement processing monitoring
|
We need to extract the CPU and memory monitoring from the appcd-core and move it into a new appcd-monitor package. The {{StatusMonitor}} along with the plugin host will be able to use appcd-monitor to retrieve process stats. The goal is to feed these stats into appcd status and telemetry payloads.
| 5 |
47 |
DAEMON-82
|
05/10/2017 16:36:39
|
appcd-fswatcher: Add "depth" support for recursive watching
|
Recursive fs watching works good... perhaps a little too good. When it recursively watches a directory, it has to walk the directory and watch every single descendant. This takes a bunch of resources and slow to initialize. Sometimes the only thing you are interested in is just a couple directories deep. It would best if the FSWatcher could watch only to a certain depth.
| 8 |
48 |
DAEMON-84
|
05/11/2017 06:34:34
|
appcd-request: Add http request library
|
The daemon core needs an http client service. This will tie directly into the dispatcher and use the appcd config for determining proxy settings.
| 8 |
49 |
DAEMON-85
|
05/15/2017 14:30:04
|
appcd-request: Implement request service
|
The daemon needs a centralized network library that exposes a service for making HTTP requests and takes into account network settings such as proxy settings.
| 8 |
50 |
DAEMON-86
|
05/15/2017 14:32:22
|
appcd-nodejs: Update to use appcd-request for HTTP requests
|
When appcd-nodejs downloads Node.js, it needs to take into account proxies and other network settings. Instead of using {{request()}}, it instead should use the provided request service in {{appcd-request}}.
| 3 |
51 |
DAEMON-87
|
05/15/2017 22:34:57
|
Generate yarn.lock in distribution tarball
|
When the distribution tarball is packaged, it consolidates all NPM dependencies into the top-level package.json and removes devDependencies from ALL appcd package.json files. All of the appcd-* packages are included in the tarball in the {{node_modules}} directory and declared as {{bundledDependencies}}. This ticket is to generate a {{yarn.lock}} file for all non-appcd-* dependencies and their dependencies. There are many ways to do this, but the best for ease and performance is to simply merge the {{yarn.lock}} files from every appcd-* directory.
| 1 |
52 |
DAEMON-88
|
05/23/2017 21:32:02
|
appcd-core: Add heartbeat to WebsocketSession
|
Currently there is no mechanism to detect if the Websocket client is borked. This can be accomplished using a ping/pong heartbeat. Clients opt-in by setting the {{x-heartbeat}} HTTP header. When set, the {{WebsocketSession}} will send a {{"ping"}} event every 30 seconds to the client. The client has 5 seconds to respond with a {{"pong"}}, otherwise the connection is closed by the server.
| 1 |
53 |
DAEMON-89
|
06/09/2017 16:14:50
|
Migrate to Lerna.js
|
I've been resisting the urge to jump to Lerna.js fearing it won't handle some of the edge cases, but once the daemon is released, managing and coordinating all the package releases is going to become more complicated. Need to understand Lerna's support for Yarn since we depend on {{yarn check}}. npm 5 does not yet support {{node_module}} integrity checks. Need to figure how to use Lerna.js and configure package dependencies. We will also probably ditch {{gulp}} (which isn't a bad thing) in favor of NPM scripts and a {{scripts}} directory. Everything in {{appcd-gulp}} will be moved to the {{scripts}} directory. The hope is this will give us a more manageable repo, faster builds, coordinated publishing, and removes the dependency on a globally installed {{gulp}}.
| 8 |
54 |
DAEMON-92
|
08/08/2017 19:33:05
|
appcd-logger: Implement default logger
|
The Appc Daemon uses {{snooplogg}} for logging, but {{snooplogg}} contains a pretty large 19MB file. To reduce the amount of disk space needed (around 270MB) and to consolidate default logger config settings, it makes sense to introduce an {{appcd-logger}} package.
| 5 |
55 |
DAEMON-93
|
08/11/2017 22:57:06
|
Persist logs to disk
|
The daemon needs to persist the log to disk. We can do this pretty easily by introducing a listener to the logger and writing the data to a log file. Every time the daemon is started, a fresh log file is created in {{~/.appcelerator/appcd/log}}. We still need to determine a few things: * Should we rotate old logs? Keep last 5 logs? gzip older logs? * How should we handle log files that could potentially be huge? The log messages should be streamed as objects containing metadata such as timestamps, etc. This structure should be preserved when written to disk.
| 5 |
56 |
DAEMON-94
|
08/11/2017 23:00:04
|
appcd-telemetry: Switch over to appc-platform-sdk analtyics
|
The Appc Daemon uses its own analytics code in {{appcd-telemetry}}. {{appc-platform-sdk}} also has an analytics library. It makes sense that there should be a single analytics library, however {{appc-platform-sdk}}'s implementation is not used by any other product (e.g. not battle tested) and is missing a few key features that {{appcd-telemetry}} supports such as sending telemetry at set intervals instead of at the end of the process. So, we need to determine if this ticket should even be worked on in the first place. If yes, then update {{appc-platform-sdk}} to be daemon friendly and update {{appcd-telemetry}} to use {{appc-platform-sdk}}.
| 1 |
57 |
DAEMON-95
|
08/14/2017 22:14:58
|
appcd-plugin-jdk: Implement JDK service
|
The {{appcd-plugin-jdk}} needs to expose a service that detects the JDK, via {{jdklib}}. The {{jdklib}} specifics are to be implemented by DAEMON-10.
| 13 |
58 |
DAEMON-96
|
08/21/2017 23:34:24
|
appcd-detect: Port over detect engine from node-appc v2
|
The amazing detect engine lives in node-appc v2 and needs to be ported over to an appcd-detect package. The major change involves using the {{/appcd/fswatch}} instead of the old (buggy/incomplete) fs watcher.
| 13 |
59 |
DAEMON-97
|
08/22/2017 22:25:05
|
appcd-detect: Wire up Windows Registry library
|
The {{DetectEngine}} has the necessary plumbing to poll the Windows Registry for paths to watch, however the actual call to query the registry is commented out until a solution is dropped in. We need to select a library that allows us to query the registry. In the past, we've used {{winreg}}, but it requires a bit of abstraction to make it nicer to work with. Need to investigate the offerings in NPM and perhaps find a solution that allows us to listen to registry changes.
| 8 |
60 |
DAEMON-98
|
10/10/2017 18:50:20
|
appcd-detect: watch tests do not exit
|
h5.Description On Windows running the unit tests they appear to 'hang' in a certain place, namely the appcd-detect unit tests and the {{watch()}} describe and the {{should redetect after initial detection}}. skipping that test allows the suite to run through and the process exit fine
| 5 |
61 |
DAEMON-99
|
10/12/2017 16:10:34
|
appcd-plugin: Plugin host spawns a new console window on Windows
|
h5.Description On Windows when calling to a plugin (for example appcd exec /jdk/latest/info) a new node console window is spawned. This window then stays open until it's either killed by a user or the daemon is stopped. This could be problematic as it means that spawned plugins can pretty much die at the whim of a user. I'm not sure whether it's fully possible to suppress the window however, recent PR into node might add that behaviour though https://github.com/nodejs/node/pull/15380
| 5 |
62 |
DAEMON-100
|
10/12/2017 17:23:11
|
appcd-plugin-jdk: JDK 9 is not detected
|
h5.Description JDK 9 has changed the registry key of Windows to {{HLKM\Software\JavaSoft\JDK}}. This needs to be added to [here|https://github.com/appcelerator/appc-daemon/blob/7d3c1dcb3766b7c8157fd68bcd07c1e51f658909/plugins/appcd-plugin-jdk/src/jdk-info-service.js#L158-L159] Couple notes - CurrentVersion returns 9, for JDK 8 it was 1.8 - jdklib currently fails to recognise JDK 9, it errors due to a missing JVM library, the jre folder no longer exists it seems. Will file a separate ticket for that - There is no 32-bit JDK distributed https://stackoverflow.com/questions/46356345/can-java-9-run-on-a-32-bit-os but it can be built, we might not need to support detecting 32-bit if it is not distributed officially
| 8 |
63 |
DAEMON-101
|
10/17/2017 06:16:30
|
appcd-plugin: Active request counter not decrementing for reloaded external plugin
|
Somehow it's possible to make a request to an external plugin using {{appcd exec /<path>}}, then modify the plugin so that it is stopped, yet the active requests counter is not decremented. It's unlikely, but possible, that the request is actually still active after the plugin is stopped.
| 2 |
64 |
DAEMON-102
|
10/17/2017 15:49:19
|
appcd exec --subscribe is not printing data payloads
|
When running {{appcd exec /appcd/status --subscribe}}, it doesn't display any of the events despite there being a ton in the daemon log.
| 2 |
65 |
DAEMON-103
|
10/18/2017 20:23:03
|
"appcd start" should not exit until the daemon has actually finished starting
|
When running {{appcd start}}, it will spawn the appcd-core, but then exits with a success code. It doesn't wait for the daemon to actually initialize and load the plugins. We need the start functionality to listen for an IPC message signalling the daemon is ready to go.
| 5 |
66 |
DAEMON-105
|
10/24/2017 14:02:20
|
config: Able to set a sub-key for keys that should not allow subkeys
|
h5.Description Calling something like the below will set a key on the property even though the key is a boolean in the JSDoc, this occurs on master and my appcd config PR branch {code} appc config set telemetry.enabled.bar x {code} {code} ws.send(JSON.stringify({ version: '1.0', path: '/appcd/config', id: Date.now(), data: { "action": "set", "key": "telemetry.enabled.bar", "value": "x" } })); {code}
| 5 |
67 |
DAEMON-106
|
10/26/2017 04:19:41
|
appcd-dispatcher: Create a DataServiceDispatcher class
|
There are several services that have very similar functionality where there's a single observable data store that is exposed via a {{ServiceDispatcher}} that supports filtered results and subscriptions. It would super handy (and ingenious) to introduce a {{DataServiceDispatcher}} that takes care of all this boilerplate.
| 5 |
68 |
DAEMON-109
|
10/26/2017 13:59:14
|
appcd-plugin: Calling <plugin-name>/latest does not return the expected info
|
h5.Description When calling {{appcd exec /jdk/latest}} it returns {{404 [object Object]}} it should print the plugin info to the console. It looks like the call is going through the error handler of the request made in the exec command {code} const ws = new WebSocket('ws://127.0.0.1:1732', { headers: { 'User-Agent': __filename } }) .on('message', (msg, flags) => { console.log(msgpack.decode(msg)); console.log(flags); // console.log(util.inspect(flags.binary ? msgpack.decode(msg) : JSON.parse(msg), false, null, true)); // process.exit(0); }) .on('close', () => console.log('CLOSED')) .on('open', () => ws.send(JSON.stringify({ version: '1.0', path: '/jdk/latest/', id: Date.now(), type: 'subscribe' }))); {code}
| 2 |
69 |
DAEMON-116
|
10/31/2017 16:22:05
|
appcd-default-plugins: Create a pseudo package
|
We need a package that the appcd-core can look at to load all the default appcd plugins such as the android, ios, jdk, and windows plugins.
| 2 |
70 |
DAEMON-117
|
11/03/2017 11:59:01
|
appcd-detect: Improve code coverage
|
Since the appcd-detect refactor, code coverage dropped mainly due to the improved error handling and advanced path watching.
| 5 |
71 |
DAEMON-119
|
11/06/2017 19:14:02
|
appcd-plugin-windows: Allow time interval for detections to be set by user
|
h5.Description Currently the intervals in the Windows plugin are hard-coded, it would be nice to allow a user to specify these themselves if they need to. Something like {{appcd config set appcd-windows-plugin.intervals.devices 5000}} for example. Then the plugin would need to also query the config to see if this is set More context here https://github.com/appcelerator/appc-daemon/pull/111#discussion_r149122916
| 3 |
72 |
DAEMON-122
|
11/07/2017 13:37:10
|
appcd-plugin: Prerelease versions are not loaded by version ranges
|
h5.Description *This is expected imo but filing for discussion* If I version my plugin as {{0.1.0-0}} then executing {{appcd exec /myplugin/0.1.X/}} or {{appcd exec /myplugin/^0.1.0/}} will not find my plugin. Executing {appcd exec /myplugin/^0.1.0-0/}} will. This is because semver will never view a prerelease as valid in a non-prerelease version range. /latest will work, and will load the prerelease version {code} $node > const semver = require('semver'); > const versions =['1.0.0', '1.1.0-0', '1.1.0-1']; > versions.sort(semver.rcompare); [ '1.1.0-1', '1.1.0-0', '1.0.0' ] {code} This is important as it makes how we version things problematic. If we do prereleases then if consumers decide to call with 0.1.X or similar, then they will never get prereleases plugins, and we don't want them calling latest as that will just lead to problems
| 3 |
73 |
DAEMON-123
|
11/08/2017 13:01:47
|
appcd-plugin-windows: Only wireup lookups when certain condition are met
|
h5.Description As Chris pointed out, it doesn't make much sense to do the detection of devices, emulators etc. if we don't have any visualstudios. We should probably do a VS detection, and then wireup everything else if we find some. We should also probably only do this if we're actually on Windows too
| 2 |
74 |
DAEMON-124
|
11/09/2017 05:40:22
|
"gulp check" no longer works properly since switching to workspaces
|
Since Yarn workspaces have been enabled, {{gulp check}} is no longer working properly. It checks to see what is installed in the package's {{node_modules}} instead of the top-level workspace {{node_modules}}. Since it doesn't find a particular dependency installed, it says every package is not installed. While fixing this, we should also make it more parallel so that it can compute the security and package update checks at the same time. We may also need/want to come up with a more robust way of checking integrity. {{yarn check --integrity}} doesn't work well with Lerna.
| 8 |
75 |
DAEMON-125
|
11/10/2017 03:23:52
|
WebSocketSession: Allow msgpack to be disabled
|
We should add the ability per connection to disable msgpack responses.
| 1 |
76 |
DAEMON-126
|
11/10/2017 12:22:47
|
appcd-plugin-genymotion: Add support for custom deployed directory path
|
h5.Description As it is possible to support changing the deployed genymotion directory we should look into making the lookup of the deployed directory consider this path. On Windows we can query the registry for it (under HCKU\Software\Genymobile\Genymotion), I'm not sure how to find it on OSX and linux. we should also add a config setting called genymotion.deployed just incase it is not possible to find on non-Windows
| 5 |
77 |
DAEMON-127
|
11/10/2017 16:55:46
|
appcd-plugin: Show more plugin system details
|
We need to add more information to the plugin system's status object that is returned when we run {{appcd status --json}} such as the plugin scan paths.
| 1 |
78 |
DAEMON-128
|
11/13/2017 11:55:24
|
appcd-fswatch: Recursive watching does not appear to work
|
In all of my recent testing, recursive filesystem watching does not appear to work regardless of whether a depth is set.
| 8 |
79 |
DAEMON-129
|
11/13/2017 11:58:46
|
Android Plugin: Populate emulator target, api level, and sdk using default Android SDK
|
To get the Android emulator's target, api level, and sdk name, we need to pass in an SDK for it to pull those bits of info. The problem is there could be more than one SDK. The Android plugin needs to select the best SDK starting with the one in specified in the config, then pass it into {{getEmulators()}}.
| 13 |
80 |
DAEMON-130
|
11/13/2017 12:32:22
|
appcd dump: Dump config, status, and log to file or stdout
|
It would be helpful to introduce an {{appcd dump}} command that dumps the config, status, and log to a file. This would make bug reporting much, much easier.
| 5 |
81 |
DAEMON-131
|
11/13/2017 12:34:20
|
appcd logcat: Add support for --save <file>
|
It would useful if the {{appcd logcat}} command supported a {{--save <file>}} option to save the contents of the log buffer to a file.
| 1 |
82 |
DAEMON-132
|
11/13/2017 12:35:26
|
appcd logcat: Add support for a filter
|
It would be useful to allow a filter to be passed into {{appcd logcat}} that would only display messages where the message namespace matched the specified filter.
| 8 |
83 |
DAEMON-133
|
11/13/2017 13:03:22
|
Android Plugin: Sort SDKs and assign default
|
Currently the list of detected Android SDKs is not ordered and no default SDK is selected. This is only an issue if you have more than one SDK.
| 3 |
84 |
DAEMON-134
|
11/13/2017 13:04:18
|
Android Plugin: Sort NDKs and assign default
|
Currently the list of detected Android NDKs is not ordered and no default NDK is selected. This is only an issue if you have more than one NDK.
| 3 |
85 |
DAEMON-135
|
11/13/2017 23:27:50
|
appcd-detect: First change rescan emits new event eventhough nothing changed
|
When the detect engine is watching a folder where something changes, it triggers a rescan. The first time the rescan is done, the results are merged into the observable model and even though nothing has changed, it will emits an event. It should only emit an event when A) something of interest happens and B) the result has actually changed.
| 8 |
86 |
DAEMON-137
|
11/14/2017 15:17:52
|
appcd-gulp: Local directories are baked into source maps
|
The build system uses babel to transpile and generate the source maps. One of the args is the {{sourceRoot}} which is set to an absolute path. This absolute path gets baked into the generated files which is undesirable. Need to see if we can do relative paths. If that doesn't work, perhaps we need rewrite all of the generated source maps.
| 3 |
87 |
DAEMON-138
|
11/14/2017 17:25:21
|
appcd-gulp: Coverage tests blow up when --trace-deprecation is set
|
When trying to get a bit more info about unhandled rejections, Node.js has a flag that can be passed in called {{\-\-trace\-deprecation}}. The idea would be to add this to the {{gulp test/coverage}} task and then we'd see it in the CI logs. However, when this flag is set, for some reason {{nyc}} blows up because it can't load {{mocha-jenkins-reporter}}. But the rub is {{nyc}} is not supposed to load it. The {{mocha-jenkins-reporter}} is an argument to {{mocha}}, not {{nyc}}. When adding {{\-\-trace\-deprecation}} and running {{gulp coverage}}, we get the following error: {code} Error: Cannot find module '/Users/chris/appc/appc-daemon/node_modules/nyc/node_modules/istanbul-reports/lib/Users/chris/appc/appc-daemon/node_modules/mocha-jenkins-reporter' at Function.Module._resolveFilename (module.js:536:15) at Function.Module._load (module.js:466:25) at Module.require (module.js:579:17) at require (internal/module.js:11:18) at Object.create (/Users/chris/appc/appc-daemon/node_modules/nyc/node_modules/istanbul-reports/index.js:10:20) at /Users/chris/appc/appc-daemon/node_modules/nyc/index.js:451:24 at Array.forEach (<anonymous>) at NYC.report (/Users/chris/appc/appc-daemon/node_modules/nyc/index.js:450:17) at report (/Users/chris/appc/appc-daemon/node_modules/nyc/bin/nyc.js:89:7) at /Users/chris/appc/appc-daemon/node_modules/nyc/bin/nyc.js:76:25 {code} We can fix that by applying the following patch: {code} +++ b/packages/appcd-gulp/src/templates/standard.js @@ -159,6 +159,7 @@ module.exports = (opts) => { function runTests(cover) { const args = []; let { execPath } = process; + let jenkinsReporter = resolveModule('mocha-jenkins-reporter'); // add nyc if (cover) { @@ -178,7 +179,15 @@ module.exports = (opts) => { '--reporter=html', '--reporter=json', '--reporter=text', - '--reporter=text-summary', + '--reporter=text-summary' + ); + if (jenkinsReporter) { + args.push('--reporter=' + path.relative( + resolveModule('istanbul-reports', resolveModule('nyc')), + jenkinsReporter + )); + } + args.push( '--require', path.resolve(__dirname, '../test-transpile.js'), '--show-process-tree', process.execPath // need to specify node here so that spawn-wrap works @@ -188,6 +197,8 @@ module.exports = (opts) => { process.env.APPCD_COVERAGE = 1; } + args.push('--trace-deprecation'); + // add mocha const mocha = resolveModule('mocha'); if (!mocha) { @@ -201,8 +212,7 @@ module.exports = (opts) => { args.push('--inspect-brk'); } - const jenkinsReporter = resolveModule('mocha-jenkins-reporter'); - if (jenkinsReporter) { + if (!cover && jenkinsReporter) { args.push(`--reporter=${jenkinsReporter}`); } @@ -241,13 +251,16 @@ module.exports = (opts) => { } } - function resolveModule(name) { + function resolveModule(name, rel) { let dir = path.join(appcdGulpNodeModulesPath, name); if (fs.existsSync(dir)) { return dir; } try { + if (rel) { + return require.resolve(name, { paths: [ path.join(rel, 'node_modules') ] }); + } return path.dirname(require.resolve(name)); } catch (e) { return null; {code} But then we run into a problem where {{mocha-jenkins-reporter}} is expecting a {{mocha}} runner object and {{nyc}} doesn't pass one in. {code} /Users/chris/appc/appc-daemon/node_modules/mocha-jenkins-reporter/node_modules/mocha/lib/reporters/base.js:252 runner.on('start', function () { ^ TypeError: runner.on is not a function at Jenkins.Base (/Users/chris/appc/appc-daemon/node_modules/mocha-jenkins-reporter/node_modules/mocha/lib/reporters/base.js:252:10) at new Jenkins (/Users/chris/appc/appc-daemon/node_modules/mocha-jenkins-reporter/lib/jenkins.js:40:8) at Object.create (/Users/chris/appc/appc-daemon/node_modules/nyc/node_modules/istanbul-reports/index.js:12:16) at /Users/chris/appc/appc-daemon/node_modules/nyc/index.js:451:24 at Array.forEach (<anonymous>) at NYC.report (/Users/chris/appc/appc-daemon/node_modules/nyc/index.js:450:17) at report (/Users/chris/appc/appc-daemon/node_modules/nyc/bin/nyc.js:89:7) at /Users/chris/appc/appc-daemon/node_modules/nyc/bin/nyc.js:76:25 at ChildProcess.<anonymous> (/Users/chris/appc/appc-daemon/node_modules/nyc/node_modules/foreground-child/index.js:52:5) at emitTwo (events.js:126:13) {code} I believe that {{mocha-jenkins-reporter}} should remain an argument to {{mocha}} and not {{nyc}} and that we need to figure out why {{nyc}} is sniping the {{\-\-reporter}} arg to mocha. Maybe it's doing a blind scrap on {{process.argv}}?
| 3 |
88 |
DAEMON-140
|
11/14/2017 23:17:45
|
system-info doesn't return ios information
|
Start daemon, load http://localhost:1732/system-info/1.x/info. {{ios}} is {{null}}. Plugin status: {code} ios 1.0.0-2 external /Users/feonsua/.appcelerator/install/7.0.0-master.11/package/node_modules/appcd-plugin-ios 8.9.1 Cannot read property 'value' of null 0 / 0 {code} appcd exec /ios/latest/info returns {{Cannot read property 'value' of null}} appcd --debug: {code} 2017-11-14T23:21:45.867Z appcd:plugin:external:parent error Failed to activate plugin: [email protected] 2017-11-14T23:21:45.869Z appcd:core:websocket-session [0] 127.0.0.1:58202 /ios/latest/info 400 Cannot read property 'value' of null 836ms 2017-11-14T23:21:45.888Z appcd:core:websocket-session error { TypeError: Cannot read property 'value' of null 2017-11-14T23:21:45.888Z appcd:core:websocket-session error at then (/Users/chris/appc/ioslib/src/certs.js:46:9) 2017-11-14T23:21:45.888Z appcd:core:websocket-session error at <anonymous> 2017-11-14T23:21:45.888Z appcd:core:websocket-session error at process._tickCallback (internal/process/next_tick.js:188:7) id: 'cd35e68c-cdb7-45e9-89bf-3e5e3d31bba5' } {code}
| 2 |
89 |
DAEMON-141
|
11/15/2017 02:36:24
|
Appc Daemon is crashing the terminal and studio
|
*Problem Description:* MacOS terminal is getting crashed If you start a daemon from a terminal and leave for some time. And, I can't even start a studio due to resource unavailability - it just crashes while launching it. {code:java} [forkpty: Resource temporarily unavailable] [Could not create a new process and open a pseudo-tty.] {code} {code:java} ITEM-AX40113:~ kkolipaka$ ps aux | wc -l 241 ITEM-AX40113:~ kkolipaka$ ps aux | grep appcd | wc -l 5 ITEM-AX40113:~ kkolipaka$ ps aux | grep gulp | wc -l {code} Studio crash log: https://gist.github.com/kolipakakondal/904a50e1031a500e74ee526ec54ea423
| 5 |
90 |
DAEMON-142
|
11/15/2017 02:52:43
|
system-info doesn't show android info
|
I'm using appcd 1.0.0-2 and can't see the android info when I execute {{appc exec /system-info/1.x/info}} Please find the attached appcd status and system_info files
| 2 |
91 |
DAEMON-143
|
11/15/2017 03:50:47
|
iOS simulators are missing in the system-info - intermittent issue
|
*Problem Description:* Can't find the simulators in the /system-info/1.x/info. However, it's an intermittent issue. *To reproduce:* # Run sudo npm install [email protected] -g # Run appc use 7.0.0-master.11 # Run appcd appcd start # Run appc appcd exec /system-info/1.x/info *Versions:* Appcelerator Daemon, version 1.0.0-2 CLI 7.0.0-master.11 Please find the attached system-info [^system_info2.txt] and [^appcd_status_1.0.0-2.txt]
| 1 |
92 |
DAEMON-145
|
11/15/2017 23:39:01
|
Subscribe on /system-info/1.x/info doesn't work
|
*Problem Description:* When we subscribe on {{/system-info/1.x/info}} changes - Appcd should publish the changes if any changes in iOS devices, Android devices, Xcode changes, etc. *To Reproduce:* # appc appcd exec /system-info/1.x/info/ --subscribe # Now connect iOS device *Actual:* No changes *Expected:* Return system-info with the iOS device Note: {{appc appcd exec /system-info/1.x/info/ios/devices --subscribe}} is working fine
| 1 |
93 |
DAEMON-147
|
11/16/2017 06:33:14
|
appc status: Hide windows-Plugin for unix / macOS machines
|
When running {{appcd status}}, the following (red) line occurs: {code} windows 1.0.0-6 external /usr/local/lib/node_modules/appcd/node_modules/appcd-plugin-windows 8.9.1 Unsupported platform "darwin" 0 / 0 {code} It's not an issue because I am not running on Windows, but it would be "UX friendly" to either hide it on the mac or just say "Not available" like Studio does for the Windows SDK.
| 2 |
94 |
DAEMON-148
|
11/16/2017 08:06:05
|
Android emulators missing target, api-level and sdk-version information
|
*Problem Description:* Android emulators are missing target, api-level and sdk-version information - which is available in the ti info and also used in the studio And also, it doesn't have SDK, NDK and targets information *To reproduce:* # appc use 7.0.0-master.19 # appc appcd exec /system-info/1.x/info/android # Verify android emulator information *Actual:* No api-level,sdk-version and target in the emulator *Expected:* We should have all the information which is provided in the ti info Please find the attached android info file [^android_info.json]
| 1 |
95 |
DAEMON-151
|
11/16/2017 12:03:58
|
Spawning the ios plugin through appc cli errors with cannot find module plist
|
h5.Description ioslib has a missing dependency which causes an error when distributed in the cli due to the legacy bundling style used. h5.Steps to reproduce # {{appc use 7.0.0-master.23}} # {{appc appcd start && appc exec /ios/latest/info}} h5.Actual Error cannot find plist h5.Expected No error, environment info returned
| 1 |
96 |
DAEMON-153
|
11/16/2017 15:01:41
|
appcd: appcd start --debug should respect a --no-colors flag
|
h5.Description Writing up a guide on how to provide information when reporting issues. Noticed that appcd start --debug --no-colors still logs in colour, would be nice if the debug logs provided by people didnt have the escape codes. h5.Steps to repro # appcd start --debug --no-colors h5.Actual Colours h5.Expect No colours
| 2 |
97 |
DAEMON-154
|
11/16/2017 18:06:14
|
JSON Strings should be wrapped in double quotes
|
json strings are coming in single quotes but it should be in double quotes. *To reproduce* # Run {{appc appcd exec /system-info/1.x/info --json --no-banner}} # Valdiate the output here https://jsonformatter.curiousconcept.com Studio json parser validation is failing due to this.
| 2 |
98 |
DAEMON-155
|
11/16/2017 18:28:01
|
ios info is null due to "Failed to load plugin: Cannot find module 'plist' "
|
I can't see ios info in the {{appc appcd exec /system-info/1.x/info --json}} *To reproduce:* # Run appc use 7.0.0-master.22 # appc appcd exec /system-info/1.x/info --json # Verify ios info - it's null Please find the attached appcd dump file.
| 1 |
99 |
DAEMON-156
|
11/16/2017 19:01:16
|
appcd: Auto import config settings from Titanium CLI
|
It would great to be able to import the Titanium CLI config into the appcd user's config in {{~/.appcelerator/appcd/config.json}}. Mappings would be as such: * {{android.adb.port}} (Number) -> {{android.adb.port}} (Number) * {{android.executables.aapt}} (String) -> {{android.executables.aapt}} (String) * {{android.ndkPath}} (String) -> {{android.ndk.searchPaths}} (Array<String>) * {{android.sdkPath}} (String) -> {{android.sdk.searchPaths}} (Array<String>) The list goes on and on... https://wiki.appcelerator.org/display/guides2/Titanium+CLI+Options. Here's the unmaintained list: https://wiki.appcelerator.org/display/CLI/CLI+Config+Settings.
| 3 |
100 |
DAEMON-157
|
11/16/2017 21:46:18
|
appcd: Suppress banner when run through appc
|
h5.Description It was raised that the double banner when running {{appc appcd}} shouldn't happen, we should suppress this, I think we can use the APPC_ENV environment variable to do so, alternatively we could have the CLI push a {{--no-banner}} flag but I prefer the former
| 1 |
101 |
DAEMON-158
|
11/16/2017 22:29:19
|
Querying iOS devices results with "Cannot find module 'plist' "
|
*Description* Running the command "appc appcd exec /ios/latest/info/devices" errors out with a message cannot find plist *Steps to reproduce* 1. Install CLI 7.0.0-master.23 2. Start the daemon with "appc appcd start" 3. Connect an iOS devices and check that it's recognized eg. appc ti info 4. Run the command "appc appcd exec /ios/latest/info/devices" *Actual result* This result is seen: Failed to load plugin: Cannot find module 'plist' *Expected Result* An output showing some details about the iOS device that is connected. No errors should be seen.
| 1 |
102 |
DAEMON-159
|
11/16/2017 22:49:52
|
appcd-plugin: Can't [force] stop a plugin that's starting
|
It's possible for a plugin to be started, but activate() to be hung waiting for an unresolved promise. In this case, you can't stop the plugin until it starts. We should allow plugins to be stopped if the plugin is started, but not activated. We should allow plugins to be force stopped regardless if it's started, starting, or stopping.
| 3 |
103 |
DAEMON-160
|
11/17/2017 01:10:40
|
ioslib: Versioning of package on npm is causing issues
|
h5.Description *I know this isn't really a proper ticket but I needed somewhere to dump this* Currently the ioslib version being pulled in is [email protected] based off the version range of ^2.0.0-8. This (surprisingly to me) is correct in semver land and 2.0.0-beta.3 is considered to be greater than 2.0.0.-10 https://runkit.com/ewanharris/5a0e34d8e7d5da001228faf7 So currently we're borked and need a way out, here's the possible solutions, in no order. # Bump ioslib to become [email protected], replacing 2.0.0.-10 # Change the appcd-plugin-ios dependency to next, stay like this # Change the appcd-plugin-ios dependency to next, ask npm nicely to remove [email protected] (I dont see why they wouldnt), then eventually move back to ^2.0.0-10 version ranges. # Release [email protected], move appcd-plugin-ios to ^2.0.1-0 I vote for 3 or 4 with an added sprinkle of promising to never do -beta.X on npm packages again :)
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.