Stuck indexing metadata

[jbro-io]

After updating to the latest release whenever I attempt to deploy to server the "Indexing your Salesforce.com metatada. This operation could take a while depending on the size of your org." dialog appears and does not disappear. No error occurs, the dialog just stays open indefinitely.

[joeferraro]

it may actually be indexing your org. does your org have a significant amount of metadata?

[jbro-io]

Well it's been indexing for over an hour now. It has never taken more than a minute in the past.

[joeferraro]

You can roll back to 1.4.7 until i get a chance to look into this (run this command from ~/Library/Application Support/Sublime Text 2/Packages/MavensMate):

$ git checkout tags/v1.4.7

[jasonsims]

I was seeing this issue as well. I rolled back to v1.4.7 but now I'm running into Ruby errors (ruby 1.9.2p320).

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in gem_original_require': no such file to load -- json (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:inrequire' from /Users/jsims/Library/Application Support/Sublime Text 2/Packages/MavensMate/support/lib/mavensmate.rb:4 from /Users/jsims/Library/Application Support/Sublime Text 2/Packages/MavensMate/support/app/controllers/project_controller.rb:2:in require' from /Users/jsims/Library/Application Support/Sublime Text 2/Packages/MavensMate/support/app/controllers/project_controller.rb:2 from /Users/jsims/Library/Application Support/Sublime Text 2/Packages/MavensMate/commands/edit_project.rb:5:inrequire' from /Users/jsims/Library/Application Support/Sublime Text 2/Packages/MavensMate/commands/edit_project.rb:5

[jasonsims]

Something was up with my ruby install. A refresh of the environment fixed those errors. Running on 1.4.7 has fixed the indexing issue for now. Thanks for posting a workaround.

[joeferraro]

@jasonsims @jbroquist to help me debug this issue, would you guys mind providing me the following info:

• OS X version
• ruby version
• are you using rvm?

[jbro-io]

• OSX 10.8.2
• ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.1.0]
• I am using rvm

[jasonsims]

• OSX 10.7.5
• ruby 1.9.2p320 (2012-04-20 revision 35421) [x86_64-darwin11.4.2]
• Using RVM

I had trouble when upgrading to 1.9.3 of ruby so I reverted

[kylethornton]

was experiencing this as well, but it seems to now have gone away. The org I was hanging has a massive amount of metadata so I suspect that Salesforce is puking somewhere along the way (Eclipse also has issues with this org)

[joeferraro]

if tested this across 5 different machines and have been unable to reproduce

[jasonsims]

I'll upgrade to the latest version and try again. Is there any debugging info I can pull for you if the issue continues?

[joeferraro]

In order to debug the MavensMate UI, you must run the following command in terminal:

 $ defaults write org.mavens.MavensMate WebKitDeveloperExtras -bool true

Then, whenever you right click on the MavensMate UI, you'll see an option to "inspect" which will open the WebKit inspector. Here, you should see valuable debug info in the console.

[jasonsims]

I upgraded to 1.5.1 again and now everything is working. Pretty strange...Yesterday I let it run for over an hour with multiple cancel/retries and indexing never completed. Now it's completing in <5min. @jbroquist has this started working for you as well?

I'll let you know if anything changes. Thanks for quick attention to this bug!

[joeferraro]

interesting. i'll keep an eye on this one. thanks guys

[jbro-io]

I just updated to 1.5.1 and tried again and am still experiencing the same results. I'll run the debug console later tonight and report back.

Going to revert back to 1.4.7 for the time being.

[joeferraro]

@jbroquist may sound crazy but try restarting your machine before testing 1.5.1 again. trying to determine whether there's a hanging ruby process in there which may be causing your issue

[jbro-io]

Ok I updated to 1.5.1 and then restarted. Now when I attempt to deploy to server the deployment window doesn't get stuck indexing metadata. Instead, no metadata is returned at all. I pressed the "Refresh Metadata" button as well and nothing was returned.

[joeferraro]

very interesting. can you be more specific about the org you're working with? is it a dev org? production org? sandbox? isv org? anything unique about the org?

[jbro-io]

I'm developing in a developer sandbox and attempting to deploy to our production org. The org is on the Unlimited edition of SFDC.

Nothing really unique about our org I can think of... Let me know if there something in specific I can answer though.

[jbro-io]

Reinstalled the Thin gem and updated to 1.5.5 and all appears to be working perfectly with my deployments now.