StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGrunt watch tasks seem to take a very long time
primarykey
Id
20121361
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-11-21T12:44:55.433
FavoriteCount
0
LastActivityDate
2015-11-26T09:57:43.037
LastEditDate
LastEditorUserId
0
OwnerUserId
92148
ParentId
0
PostTypeId
1
Score
8
ViewCount
5180
LastEditorDisplayName
text
Body
I'm running two simple tasks that run for <100ms each but when run under the watch command the two combined tasks are taking ~8 seconds in total (there seems to be an overhead of 3.5 seconds per task). I'm using it with live-reload for development and I'm finding it very frustrating. I tried setting <code>spawn</code> to <code>false</code> but this seemed to break it and none of the associated tasks were run. Here's sample output from when a sass file is changed. <pre><code>>> File "app/styles/main.scss" changed. File "app/styles/main.css" created. Done, without errors. Elapsed time loading tasks 4ms ▇▇▇▇▇ 9% sass 1ms ▇▇ 2% sass:dist 39ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 89% Total 44ms Completed in 3.862s at Mon Nov 18 2013 17:05:57 GMT+0000 (GMT) - Waiting... OK >> File "app/styles/main.css" changed. Running "copy:styles" (copy) task Copied 1 files Done, without errors. Elapsed time loading tasks 4ms ▇▇▇▇▇▇▇▇▇▇▇▇ 24% copy:styles 13ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 76% Total 17ms Completed in 3.704s at Mon Nov 18 2013 17:06:01 GMT+0000 (GMT) - Waiting... OK >> File ".tmp/styles/main.css" changed. ... Reload .tmp/styles/main.css ... ... Reload .tmp/styles/main.css ... Completed in 0.000s at Mon Nov 18 2013 17:06:01 GMT+0000 (GMT) - Waiting... </code></pre> Using grunt 0.4.1 (and grunt-cli 0.1.11) on node.js 0.10.20. Running on 2012 Macbook Air (OS X 10.8.5)
Tags
<node.js><gruntjs><yeoman><grunt-contrib-watch>
Title
Grunt watch tasks seem to take a very long time
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDaveJ
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGrunt watch tasks seem to take a very long time
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COFor the sass task, are you using grunt-contrib-sass?
 singulars
 PostPostId
 POGrunt watch tasks seem to take a very long time
 UserUserId
 USBen
2. CO@Ben No, I'm using grunt-sass (written in Node instead of Ruby).
 singulars
 PostPostId
 POGrunt watch tasks seem to take a very long time
 UserUserId
 USDaveJ

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.