Wish list for features?
by Yaakov Nemoy
Hey List,
I've been going through EKG's grapher finding ways to optimize some of
the SQL queries, but it seems that no matter how many bench marks i
run, i can't make it inherently faster. So now it's time to work on
phase two (my phase two.)
What features do you guys want. Namely, what reports do you want to
see? What do you want quantifiable? Give me features to implement.
-Yaakov
15 years, 4 months
Another patch
by Yaakov Nemoy
Here's something else that was sitting in my queue.
-Yaakov
15 years, 6 months
A short optimisation
by Yaakov Nemoy
Hi List,
I spent most of the day working on this, only because i'm a sucker for
distraction, and i was learning my way around Ruby. Anyways, this
should remove some SQL queries from grapher.
The messiness is due to some retabbing and removal of extraneous
whitespace (which i also figured out how to do in emacs, so go emacs.)
Emacs seems to insist on using two spaces for tabs. What are
everyone's feelings on this?
-Yaakov
15 years, 6 months
limit_months
by Max Spevack
Michael,
Can you explain what the limit_months variable means?
I created a settings file that specifically listed only the months that
represent FY08 (March 2007 - February 2008).
>From this settings file, I ran ekg and allowed it to create a new
database.
However, when I graph the results, the pie charts show data that goes
beyond that range all the way to the present.
How do I get ekg to focus only on a specific slice of time, and nothing
else? Obviously I'm doing something wrong.
I want to modularize my results so that I can have separate databases
for separate quarters or years.
Thanks,
Max
15 years, 6 months
FYI: offtrac
by Michael DeHaan
A possible next-evolution of EKG would be to scan source control and
project tracker sites. This may or may not involve interleaving the
statistics.
Anyway, I noticed on Fedora Planet that Jesse Keating started something
to manipulate Trac and this may prove useful in the future.
https://fedorahosted.org/offtrac/
--Michael
15 years, 6 months
db creation bug
by Max Spevack
I'm trying to do a fresh run of ekg -- without a pre-existing database,
and I think I found a bug, but I don't know how to fix it.
I don't really understand how it figures out if a database exists or not
(it's looking for the sqlite3.db file, I suppose. Regardless, if you
run an ekg --scan w/ no db existing, the "foo" is printed, but the "bar"
never is, meaning that the database is never properly initialized.
Something in the line in between is triggering the exception, and then
the "using existing database" code path tries to execute, leading to the
program crashing when it tries to do stuff with a database that was
never fully set up.
[spevack@localhost v2]$ git diff db.rb
diff --git a/v2/db.rb b/v2/db.rb
index b172cb0..81e519a 100644
--- a/v2/db.rb
+++ b/v2/db.rb
@@ -22,7 +22,9 @@ class Db
begin
ActiveRecord::Schema.define do
create_table :scans do |table|
+ puts "foo"
table.column :url
+ puts "bar"
end
create_table :posts do |table|
table.column :url, :string
table.column :subject, :string
table.column :list_id, :string
table.column :from_domain, :string
table.column :from_addr, :string
table.column :sent_date, :date
end
end
rescue
puts "using existing database"
end
end
15 years, 6 months