Firehose web front-end presentation
by Matthieu Caneill
Hi!
I've been working on a generic implementation of a Firehose front-end;
it's a Flask app designed to publish Firehose results on the web. I'd
also be happy to contribute it to the official Firehose base, if you
find interest in it.
I have several questions/remarks about this, I'll email them separately to
have different threads.
You can see a running instance of 'Firewose', the Firehose front-end
web app, on [1]. This is only a draft yet, but I'd be very happy if
you could give me feedback about this.
[1] http://firewose.uspilon.cc
Cheers.
Matthieu Caneill
10 years, 9 months
Firehose __hash__ functions
by Matthieu Caneill
Hi,
Are you interested by having real __hash__ functions (that use an
external library like hashlib) instead of the current ones?
Because currently:
>>> hash(Point(0, 1)) == hash(Point(2, 3))
True
Cheers.
Matthieu
10 years, 9 months
__slots__ in Firehose objetcs
by Matthieu Caneill
Every Firehose object uses __slots__ for memory optimization, but it
blocks tools like SQLAlchemy to add attributes dynamically; could we
remove this feature or render it optional?
--
Matthieu
10 years, 10 months
"error-type" element needed in grammar
by Matthieu Caneill
I use the Coccinelle [1] static analyzer (which I've instrumented to
support Firehose output), and it can process different kind of
(possibly user-defined) tests. It could be useful to add a variable in
the issue element to categorize more precisely the type of error; and
any other tool which supports different kind of tests would benefit
from such an extension. Such an element could be called "error-type"
or "check-name". What do you think about this? I can submit a pull
request if you agree with this.
--
Matthieu
10 years, 10 months
Firehose objects unicity on database side
by Matthieu Caneill
How is one supposed to deal with unicity of Firehose elements in an
SQL database? I mean, in xml files we don't avoid repetitions, but we
should on the database side. A simplified example of this problem
could be:
<analysis>
<metadata>
<sut name="python-ethtool" />
<generator name="coccinelle" />
</metadata
<results>
<issue />
</results>
</analysis>
<analysis>
<metadata>
<sut name="python-ethtool" />
<generator name="cpychecker" />
</metadata
<results>
<issue />
</results>
</analysis>
Both metadatas should point to the same SUT, in the db.
Do you have something in mind like a Firehose 'unicity' module?
--
Matthieu
10 years, 10 months
