Sitemap: An Extension to Allow Search Engine Indexing of Bugzilla

	Hello hello folks. I just finished writing a new Extension, called
Sitemap. This makes Bugzilla indexable by Google, Yahoo, Bing, and Ask.
It's also very careful about security bugs. This is all described on the
home page for the project, here:

	http://code.google.com/p/bugzilla-sitemap/

	However, you will notice that there aren't any Downloads there yet!
That's because I was hoping that before I do an official release, you
guys would help me out by doing some informal code review, asking some
questions, and doing some testing! The code is available in bzr, at:

	bzr://bzr.mozilla.org/bugzilla/extensions/sitemap/trunk

	Or you could just browse it at:

	http://bzr.mozilla.org/bugzilla/extensions/sitemap/

	Anyhow, let me know what you think! If you find any bugs, you can
report them on the Google Code tracker there, or just send them to me by
email.

	-Max
--

-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>

Re: New Search Test, Question

On 28/06/10 02:01, Max Kanat-Alexander wrote:
> 	Given that these safeguards are in place, do you guys think it's safe
> and OK to have the test in Bugzilla's codebase itself, instead of in the
> QA tests?

Definitely.

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla@...
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>

Bugzilla::Leak - A simple memory examiner for Perl

	Attached (if this list supports attachments--I forget) is a file called
Leak.pm. This is a tool I've developed over the last day or so to debug
memory usage in Perl. So far it's helped me quite a bit to figure out
two serious memory-usage issues. There is a comment at the top
explaining basically how it works.

	It's more of a hack that you can hack into your code than a polished
product. It probably won't handle every situation, but I suspect that it
will work pretty well for Bugzilla code, given the sort of stuff that we
usually have in memory.

	Oh, also, it only works on relatively modern versions of Linux. (RHEL5
or more recent.)

	-Max
--

-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

package Bugzilla::Leak;
use strict;

# Brief instructions: call Bugzilla::Leak::size() every so often.
# Don't call size() too often, though--it's slow.
# When your process is too big, call Bugzilla::Leak::dump_memory()
# and then exit. dump_memory will print out a lot of stuff to
# STDERR that will probably help you figure out what's using RAM.
#
# Warning: dump_memory seems to take quite a bit of RAM itself--

ADULT CLASSIFIEDS

.

Click Here to Enter:

 >>> http://better-web-777.com/15/adult-classifieds <<<

.

.

.

.

.

.

.

.

.

.

.

.

Re: Bugzilla::Leak - A simple memory examiner for Perl

You mention modern versions of linux. How about Win or threaded apache instances (which also includes
win). Also mod perl?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Max Kanat-Alexander <mkanat <at> bugzilla.org>
Sender: developers-owner <at> bugzilla.org
Date: Sun, 04 Jul 2010 03:19:26 
To: <developers <at> bugzilla.org>
Reply-To: developers <at> bugzilla.orgSubject: Bugzilla::Leak - A simple memory examiner for Perl

	Attached (if this list supports attachments--I forget) is a file called
Leak.pm. This is a tool I've developed over the last day or so to debug
memory usage in Perl. So far it's helped me quite a bit to figure out
two serious memory-usage issues. There is a comment at the top
explaining basically how it works.

	It's more of a hack that you can hack into your code than a polished
product. It probably won't handle every situation, but I suspect that it
will work pretty well for Bugzilla code, given the sort of stuff that we
usually have in memory.

	Oh, also, it only works on relatively modern versions of Linux. (RHEL5
or more recent.)

	-Max
-- 
http://www.everythingsolved.com/

Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

Re: Bugzilla::Leak - A simple memory examiner for Perl

On 07/04/2010 08:40 PM, mockodin@... wrote:
> You mention modern versions of linux. How about Win or threaded apache instances (which also includes
win). Also mod perl?

	Devel::Gladiator probably works, but Linux::Smaps doesn't work. So
you'd have to come up with your own way of doing size().

	-Max
--

-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>

Re: Bugzilla::Leak - A simple memory examiner for Perl

On 07/04/2010 11:06 PM, Max Kanat-Alexander wrote:
> 	Devel::Gladiator probably works, but Linux::Smaps doesn't work. So
> you'd have to come up with your own way of doing size().

	Oh, or you could make dump_memory() a signal handler, like say, for
SIGINT, and just interrupt the process when it was too large. No idea if
signals work on Windows though.

	-Max
--

-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>

The First Bugzilla Users & Administrators Group Meeting!

	Hey Bugzilla users and developers! The WikiMedia Foundation in San
Francisco has offered to host a meet-up for Bugzilla Users,
Administrators, and Developers at their office! Pretty neat. We're
hoping to do this once a quarter. The first meeting is on Wednesday,
August 4, at 7pm.

	This is a group for anybody who uses or administers Bugzilla. I will be
in attendance and talking about what's up with Bugzilla development,
demoing new features of 4.0, and generally answering any questions you
may have about Bugzilla. Then we're going to have a general group
discussion.

	At our first meeting, the group discussion is going to focus on project
management--how do you do project management with Bugzilla? Are there
other tools that you use? Are there features that you'd like to see in
Bugzilla that would help with Project Management? We may even work out a
group of developers to start working on some project management
extensions for Bugzilla, if there's an interest.

	In addition to all of this, we're hoping to have free food and drinks,
and there will be time to generally socialize, etc. Everybody is
welcome, and attendance is free, but limited to 20 people. (However, if
we're at the limit and you still want to come, email me directly and
I'll see if I can get you on the guest list.) It's at the Wikimedia
Foundation in San Francisco, right in SoMa, so there's a lot to do
afterward. If there's interest, we may even all go do something or other
afterward, based on the suggestions of the folks at Wikimedia who are
familiar with the area.

	You can RSVP for the group here:

Branched for 4.0

	Hey folks. So, we've branched for 4.0 now. The 4.0 branch is at:

	bzr://bzr.mozilla.org/bugzilla/4.0

	It is not yet mirrored to CVS.

	There are a few enhancements that will still go on the branch--they are
marked blocking4.0 right now. Also, we may accept additional WebServices
enhancements almost up to Release Candidate time, since "more complete
Bug WebServices" is intended to be one of the flagship features of 4.0,
and we have a full test suite for the WebServices that gets updated
before we do an RC.

	Checkins on the 4.0 branch require the approval4.0 flag to be set by
mkanat or LpSolit.

	-Max
--

-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>

Re: Branched for 4.0

Le 08. 07. 10 08:22, Max Kanat-Alexander a écrit :
> 	Hey folks. So, we've branched for 4.0 now.
> 	It is not yet mirrored to CVS.

Do we need to wait for the CVS 4.0 branch to exist, or can we already
start committing patches for 4.2?

Do not forget to also bump the Bugzilla version to 4.1 on trunk. ;)

LpSolit
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg <at> public.gmane.org>