wesabe / mesabe Goto Github PK

Hi there,

Great job getting this out there. Have got a server set up now and just starting to play about with it a bit. One thing I noticed is that attempting to retrieve http://localhost:3000/accounts.xml just bails with a 500 error whereas on Wesabe's server it correctly returns the account details.

Are there some extra packages/setup required to get this working? If so, could you point me in the right direction?

ta,

Martin

I keep getting this:
Your Gemfile.lock is corrupt. The following gems are missing from the DEPENDENCIES section: 'archive-tar-minitar' 'nokogiri' 'rcov'
Please advise.

I somehow missed the instruction to use "changeme!" as my password for logging in after installing everything, and now I'm being told my account is disabled for too many login attempts. It says this is temporary, but I've waited a couple of days with no luck. The terminal window says my email username is being throttled. I'd really appreciate any tips on how to get around this -- the snapshot associated with this email is for an account I had for a long time. Thanks!

On MacOS X (10.6.4), the mvn commands gave me build errors, telling me I was missing group, artifact, version or packaging information.

I managed to get it installed with:
mvn install:install-file -Dfile=xmlson-1.5.2.jar -DpomFile=xmlson-1.5.2.pom -Dversion=1.5.2 -DgroupId=com.wesabe -Dpackaging=jar -DartifactId=xmlson

and:
mvn install:install-file -Dfile=shore-0.2-SNAPSHOT.jar -DpomFile=shore-0.2-SNAPSHOT.pom -Dversion=0.2-SNAPSHOT -DgroupId=com.codahale -DartifactId=shore -Dpackaging=jar

Hope those are the correct parameters, and that it can maybe help others ^^

Does anybody know where can get this plugin from. Is it part of the open source repository ?

I was stuck on the bundle install step of the PFC instructions. I ended up installing libmysqlclient-dev to get past it. I'm not sure if that was right or not, but it seemed to work. I'm running a clean install of Ubuntu 10.04.

sudo aptitude install libmysqlclient-dev

Original output from bundle install:

Installing mysql (2.8.1) from .gem files at /home/mesabeadmin/.bundle/ruby/1.8/cache with native extensions /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:483:in `build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)

/usr/bin/ruby1.8 extconf.rb
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lm... yes
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lz... yes
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lsocket... no
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lnsl... yes
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lmygcc... no
checking for mysql_query() in -lmysqlclient... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers.  Check the mkmf.log file for more details.  You may need configuration options.

From ~/.bundle/ruby/1.8/gems/mysql-2.8.1/ext/mysql_api/mkmf.log:

/usr/bin/ld: cannot find -lmysqlclient

Reading through the install instructions for PFC, I thought that I was supposed to install Bundler when it was listed in the "Requires" section. Instead of listing the gem command for Bundler there, just leave it out to make it more clear that there are more complete instructions later.

Also, it's not clear when it's OK to exit from su.

Hi,

I'm trying to install wesabe and got the strange Mysql::Error first.
After reinstalling the mysql gem (sudo env ARCHFLAGS="-arch x86_64" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config) I'm getting another error at rake db:setup

maci:pfc ydbondt$ rake db:setup
(in /Users/ydbondt/Software/wesabe/pfc)
DEPRECATION WARNING: Calling a method in Rails::Application is deprecated, please call it directly in your application constant Pfc::Application. (called from method_missing at /Library/Ruby/Gems/1.8/gems/railties-3.0.0.rc/lib/rails/application.rb:77)
dyld: lazy symbol binding failed: Symbol not found: _mysql_init
Referenced from: /Library/Ruby/Gems/1.8/gems/mysql-2.8.1/lib/mysql_api.bundle
Expected in: flat namespace

dyld: Symbol not found: _mysql_init
Referenced from: /Library/Ruby/Gems/1.8/gems/mysql-2.8.1/lib/mysql_api.bundle
Expected in: flat namespace

Trace/BPT trap

I have no idea what is wrong. I'm using mysql version: mysql-5.1.50-osx10.6-x86
Do you guys have any idea what's wrong here ?

I have Mesabe running under OS X 10.6.4 (Snow Leopard) and had to make some changes to the procedure in the Mesabe DIY wiki. Other Mac OS installers may possibly benefit from my experiences.

As I was not familiar with UNIX I got a lot of general help from the tutorials at OSXFAQ http://osxfaq.com/Tutorials/LearningCenter/

The following comments relate to the different sections within Mesabe DIY

Get the Source

OS X users should type
$ brew install git

MySQL

For my second attempt to install this software I downloaded the 64 bit DMG Archive from http://www.mysql.com/downloads/mysql/

The procedure was so straightforward that I wished I had chosen this route from the start.

I added /usr/local/mysql-5.1.52-osx10.6-x86_64/bin to the PATH environment variable
$ export PATH=$PATH:/usr/local/mysql-5.1.52-osx10.6-x86_64/bin

To check that this has worked type
echo $PATH

(It is possible to add the export command to a .profile file which Terminal will execute each time it starts up.)

BRCM

Java, Maven and Rake were already installed.

After following the BRCM installation instructions I typed
$ ~/wesabe/brcm-accounts-api
$ rake test

I did see a bunch of passing tests, with 1 failure.

Running com.wesabe.api.accounts.resources.tests.AccountResourceTest
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec <<< FAILURE!

Hopefully this does not matter.

PFC

As instructed type
$ brew install oniguruma

I already had Ruby 1.8.7 but the RubyGems version was 1.3.5. To check version numbers type
$ gem env

To upgrade RubyGems type
$ sudo gem update --system

We are back on track and can type
$ gem install bundler --pre

A blog explaining how to install the mysql gem is now essential reading http://www.tatvartha.com/2010/10/installing-mysql-gem-with-bundler-on-snow-leopard/

The location used for MySQL in my installation meant that I had to change the command to
$ bundle config build.mysql --with-mysql-config=/usr/local/mysql-5.1.52-osx10.6-x86_64/bin/mysql_config

To check the path to mysql_config the following should work
$ find /usr -iname "*mysql_config"

For the rest of this section follow the standard instructions.

Upload Support

No problems. Python already installed.

Currency Support

My accounts are all in pounds sterling but I guessed I could ignore this section.

Get This Thing Online Already

I found it easier to follow the instructions in the Pre-built Virtual Machine section (Option 2).

To open a second terminal window just ctrl-click on the Terminal icon which you will surely have installed in the dock by now.

As a simple way to upload my snapshot I copied the file I had downloaded from Wesabe into the ~/wesabe/pfc directory and then ~/path/to/snapshot.zip was just the filename.

While carrying out filer operations I created a tmp directory inside ~/wesabe/pfc/private/wesabe/uploads to avoid the bug described in issue 11 in PFC issues.

I'm not quite confident enough to edit the wiki.

Problem:
In the PFC section, $bundle install does not successfully create the mysql 2.8.1 gem

Solution:
Apparently the ruby mysql dev library doesn't contain everything necessary. Add the following package:
$sudo apt-get install libmysql++-dev

When running the rake test, I get a series of failures such as

Tests run: 31, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.199 sec <<< FAILURE!
itComputesTheBalanceByAddingSubsequentTransactionAmountsToTheStaleBalance(com.wesabe.api.accounts.entities.tests.AccountTest$A_Manual_Account_With_A_Stale_Balance) Time elapsed: 0.033 sec <<< FAILURE!
java.lang.AssertionError: expected:<US$8.50> but was:<$8.50>

itHasABalanceEqualToTheLastAccountBalance(com.wesabe.api.accounts.entities.tests.AccountTest$A_Manual_Account_Without_A_Cached_Balance) Time elapsed: 0.001 sec <<< FAILURE!
java.lang.AssertionError: expected:<US$10.00> but was:<$10.00>

itIsInUSD(com.wesabe.api.accounts.entities.tests.AccountTest$A_New_Account) Time elapsed: 0.002 sec <<< FAILURE!
java.lang.AssertionError: expected: but was:

I am running this on the latest version of Ubuntu as a fresh install. I am located in Australia.

Perhaps it would make it less difficult if there were separate OS X and Linux installation instructions for the DIY version. Or if it at least mentioned that the very first instruction won't work using a Mac.

I have been using the importer script to get Mesabe up and running, but stalled at importing our snapshot with the above error.

The command I attempted (from /opt/wesabe/pfc) was: thor snapshot:import /mnt/wesabedata/username.zip (where wesabedata was a mounted shared folder on our Ubuntu Server virtual machine)

To resolve this I had to add the following method to the Wesabe class:

def returning(value)
yield(value)
value
end

Any idea why? Has something not installed correctly?

I installed mesabe on virtual PC - ubuntu 10.04 desktop. got to the signup page.
then i imported the snapshot. when i want to login with my email i am getting:

terminal windows:
http://dl.dropbox.com/u/1183736/pfc_terminal.txt
http://dl.dropbox.com/u/1183736/brcm_terminal.txt

browser:
Errno::ECONNREFUSED in Dashboard#index

Showing /home/mesabe/wesabe/pfc/app/views/dashboard/index.html.erb where line #21 raised:

Connection refused - connect(2)
Extracted source (around line #21):

18: jQuery(function(){ page = new wesabe.views.pages.dashboard() });
19: </script>
20:
21:
22: <% preload_accounts; preload_credentials; preload_tags %>
Rails.root: /home/mesabe/wesabe/pfc

Application Trace | Framework Trace | Full Trace
lib/service.rb:93:in get_without_error_handling' lib/service.rb:72:inget'
lib/service.rb:25:in get' lib/data_preloading.rb:23:in_preload_url_into'
lib/data_preloading.rb:4:in `preload_accounts'
app/views/dashboard/index.html.erb:21
Request

Parameters:

None
Show session dump

Show env dump

Response

Headers:

None

It says it's a prereq for OSX, but I think it might be easier if after install libcharguess, the instructions explicitly say "gem install bundler".

To set archflags, you could write "At the prompt, type export ARCHFLAGS=-arch=X86". Currently it looks like you append it to the bundle command.

Also, most of these commands should probably run sudo.

I am thinking this is a memory issue... I am running VirtualBox on a MBP with 4GB ram. The box has 4.5GB free HD space, and is allocated 512MB ram and 128MB ram. (The box would not start with the default value of VRAM.)

Thanks!

Errno::ENOMEM in UploadsController#create

Cannot allocate memory - /usr/bin/ruby1.8 /tmp/systemu_mesabe_1423_1552_0.624356313704616_1/program
Rails.root: /home/mesabe/wesabe/pfc

Application Trace | Framework Trace | Full Trace
lib/makeofx2.rb:46:in convert' app/models/upload.rb:186:inconvert_to_ofx2'
app/models/upload.rb:115:in generate' app/controllers/uploads_controller.rb:120:increate'
Request

Parameters:

{"authenticity_token"=>"GianI/H+DgWSl8679uebx5YrCU3dfsvd3XZjkXhq6Tk=",
"statement"=>#File:/tmp/RackMultipart20110219-1552-1vq26hp-0}
Show session dump

Show env dump

Response

Headers:

None

Hi, folks.
I recently downloaded the pre-built virtual machine image available and it works fine.
However, while I was trying to write down my transactions, I noted an annoying charcode issue.

I was writing down a tag called ' alimentação ' ( portuguese word for feeding ), my tag was stored ' alimentação ' in the database. Can it be fixed it someway ?

It's a pretty confusing section, because I think libcharguess needs sudo but meanwhile
$bundle install should not be run under sudo.

(But I'm not sure this time, so I didn't edit the wiki.)

Thanks for creating the nice wiki guide. I did run into some problems (read: RubyGems and Bundler) while setting it up on my Ubuntu 10.0.4 Desktop VM image. But I was able to resolve them and I got Wesabe running at around 3:00 in the night. Imagine my happiness. I went ahead and signed up on the local Wesabe with the same email address as my original Wesabe account, which gave me problems while restoring the snapshot and I had to manually delete the account from the db but that's another story.

After restoring the snapshot, I logged in again. The My Accounts and the Dashboard pages kept trying to load but never finished. Since it was very late, I called it a night. Today, I still have the same issue. The targets are being displayed correctly so I am sure Wesabe is installed properly. The log has this error:

Jul 31, 2010 9:05:24 AM org.eclipse.jetty.util.log.Slf4jLog warn
SEVERE: /v2/accounts/analytics/summaries/monthly/20090801/20100801/USD
com.wesabe.api.util.money.ExchangeRateNotFoundException: Unable to find usable currency exchange rate from INR to USD on 2010-07-29

As you can tell, I have some foreign investment accounts. It seems that Wesabe uses an exchange rate service which is not accessible from my machine. Will appreciate any help with this. If you do not immediately know the solution, please let me know so I can download a snapshot from Wesabe after deleting the investment accounts. Sorry for my long rambling, I just wanted to include all the details :)

By the way, I am going to try and update the Wiki with my findings.

If you get the following error on Debian/Linux:

[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-install-plugin:pom:2.3' from repository central (http://repo1.maven.transferring file: Network is unreachable

Add the following parameter to your command: This can be worked around by running maven with the argument "-Djava.net.preferIPv4Stack=true"

Just wanted to help anyone that had the same issue.

When starting brcm-accounts-api, it can't find the wesabe repo in any of the repos... is there an update repo for maven wesabe?

When I browse there manually in my browser I can't locate it either.

[INFO] Unable to find resource 'com.wesabe:xmlson:jar:1.5.2' in repository central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:

1. com.wesabe:xmlson:jar:1.5.2

Try downloading the file manually from the project website.

Hello All,
I have installed a local copy of wesabe and cannot get past the signup page....I click sign-up multiple times with no response...

I may be wrong, but when I did an apt-cache search, only libonig-dev (no "2") showed up as a package. The title of the package is "Development files for libonig2" so I'm assuming there's a typo/updated name in the PFC section of the documentation.

https://gist.github.com/lifehome/f84997b952292297bd7a

Is there any chance that is because of my java version problem?

It appears that the files hosted on the wesabe / mesabe dropbox are no longer accessible. There are several requirements specified in the Mesabe DIY wiki:

https://github.com/wesabe/mesabe/wiki/Mesabe-DIY

Under this section:

In your wesabe directory, create a mvn directory, and copy shore-0.2-SNAPSHOT.jar, shore-0.2-SNAPSHOT.pom, xmlson-1.5.2.jar, and xmlson-1.5.2.pom to that directory. Then cd to the mvn directory and install those files with Maven 2 by running:

Example:
http://dl.dropbox.com/u/40652/shore-0.2-SNAPSHOT.jar

These all return a 404 error. Some google-fu hasn't been able to find these anywhere else on the internet either.

Is there somewhere else I can download these?

Hi everyone,

I'm just wondering if anyone would know why the backend (in "checkbox") is using 94%+ (high) CPU for extended periods of time on my Virtualbox setup?

Thanks!

In the PFC section,
$ aptitude install g++ libruby1.8 libopenssl-ruby libxslt-dev libxml2-dev libonig-dev

needs to have ruby1.8-dev package added, or the compile fails looking for mkmf.

(Sorry, I don't know if I should be brave enough to edit the wiki myself...)