0.4.x grunt branch breaks all builds
Bug #1129464 reported by
Jeff Pihach
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Fix Released
|
Critical
|
Jeff Pihach | ||
Bug Description
The 0.4.x version of grunt was released which breaks all of our builds.
We need to specify the highest of the 0.3.x branch in our package.json or fix the offending section of the build script.
Related branches
lp:~hatch/juju-gui/1129464-grunt-version
- Juju GUI Hackers: Pending requested
-
Diff: 41 lines (+19/-1)2 files modifiedHACKING (+18/-0)
package.json (+1/-1)
| Changed in juju-gui: | |
| status: | New → Triaged |
Revision history for this message
| Benjamin Saller (bcsaller) wrote | #1 |
| Changed in juju-gui: | |
| assignee: | nobody → Jeff Pihach (hatch) |
| Changed in juju-gui: | |
| status: | Triaged → Fix Committed |
| Changed in juju-gui: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
While we should pin the version of grunt (the .3/.4 APIs are different) the error that you posted to IRC seemed to be related to an issue with a known work-around.
Adding a file/line to sysctl to expand the inotify watch limit will mask the issue with node.
cat /etc/sysctl.
# expand inotify limit
fs.inotify.