https://forge-allura.apache.org/p/allura/tickets/You searched for assigned_to:"vansteenburgh"enThu, 20 Aug 2015 22:07:55 -0000https://forge-allura.apache.org/p/allura/tickets/7267/In `TroveCategoryMapperExtension`, pass `trove_cat_id` to triggered events instead of `_id`. (Completed in [#7015])Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7267/https://forge-allura.apache.org/p/allura/tickets/7263/It exists but 404s. https://forge-allura.apache.org/p/allura/activity/Dave BrondsemaThu, 20 Aug 2015 22:07:55 -0000https://forge-allura.apache.org/p/allura/tickets/7263/https://forge-allura.apache.org/p/allura/tickets/7252/Write more docs about Activity Streams, both the library and how it works with Allura. Think high-level and make sure we cover a view of the whole system. Perhaps make a guide section in here http://allura.sourceforge.net/docs/#developing-alluraDave BrondsemaFri, 07 Mar 2014 19:22:16 -0000https://forge-allura.apache.org/p/allura/tickets/7252/https://forge-allura.apache.org/p/allura/tickets/7205/Split out from [#7097]: Remove redundant data from user activity stream (icon & username), and add project name.Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7205/https://forge-allura.apache.org/p/allura/tickets/7163/"...menu problem is that ForgeActivityApp doesn't define any permissions or set them in install(), so app.is_visible_to(c.user) fails due to lack of read perm" Since we have lots of activity apps installed with no acls, let's delete them all and let them be reinstalled as anchored tools.Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7163/https://forge-allura.apache.org/p/allura/tickets/7154/allura.lib.plugin.AdminExtension adds project-admin controllers and menu items already. We'd like to expand it to support adding site-admin controllers and menu items that would show up at /nf/admin Perhaps as a POC/example we can move the the /nf/admin Home content into its own "Neighborhood Stats" AdminExtension. Having it as its own page instead of the /nf/admin landing page will alleviate [#6489]Dave BrondsemaThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7154/https://forge-allura.apache.org/p/allura/tickets/7135/Our docs are currently published to http://allura.sourceforge.net/docs/ via a post-commit job on a SourceForge internal jenkins instance. We should publish the docs on our Apache site, perhaps at a URL like https://forge-allura.apache.org/p/allura/docs/ (currently a redirect). We could do this by configuring that particular URL in Apache to serve from a directory instead of go to the allura wsgi app. We should move the post-commit publish to the Apache Jenkins job at https://builds.apache.org/job/Allura/ or perhaps to the updating cron on the allura-vm host. Lastly, we'll want http://allura.sourceforge.net/docs/* to redirect to the new locations.Dave BrondsemaThu, 20 Aug 2015 22:07:54 -0000https://forge-allura.apache.org/p/allura/tickets/7135/https://forge-allura.apache.org/p/allura/tickets/7114/Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7114/https://forge-allura.apache.org/p/allura/tickets/7111/By using the App from g.entry_points instead of hard-coding the App class name in the importer, we can make the default importers use custom, subclassed Apps w/o needing to subclass the importer also.Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7111/https://forge-allura.apache.org/p/allura/tickets/7110/Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/7110/https://forge-allura.apache.org/p/allura/tickets/7099/~~~~ [Fri Jan 24 17:45:03 2014] [error] [client 127.0.0.1] File '/var/local/allura/ForgeImporters/forgeimporters/base.py', line 511 in index [Fri Jan 24 17:45:03 2014] [error] [client 127.0.0.1] tools_with_importers.add(tool.tool_label) [Fri Jan 24 17:45:03 2014] [error] [client 127.0.0.1] AttributeError: 'property' object has no attribute 'tool_label' ~~~~Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/7099/https://forge-allura.apache.org/p/allura/tickets/7096/Here's the trace, and one of the email headers is `Content-Type: text/plain; charset=ISO-8859-1; format=flowed` and certainly there was some non-utf8 in the mail body. ~~~~ Traceback (most recent call last): File "/var/local/allura/Allura/allura/command/smtp_server.py", line 57, in process_message peer=peer, mailfrom=mailfrom, rcpttos=rcpttos, data=data) File "/var/local/allura/Allura/allura/lib/decorators.py", line 62, in post return M.MonQTask.post(func, args, kwargs, delay=delay) File "/var/local/allura/Allura/allura/model/monq_model.py", line 173, in post session(obj).flush(obj) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/base.py", line 29, in inner result = func(obj, *args, **kwargs) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/odmsession.py", line 59, in flush self.insert_now(obj, st) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/base.py", line 29, in inner result = func(obj, *args, **kwargs) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/odmsession.py", line 67, in insert_now mapper(obj).insert(obj, st, self, **kwargs) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/base.py", line 29, in inner result = func(obj, *args, **kwargs) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/odm/mapper.py", line 55, in insert session.impl.insert(doc, validate=False) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/session.py", line 22, in wrapper return func(self, doc, *args, **kwargs) File "/var/local/env-allura/lib/python2.7/site-packages/Ming-0.4.2-py2.7.egg/ming/session.py", line 160, in insert bson = self._impl(doc).insert(data, safe=kwargs.get('safe', True)) File "/var/local/env-allura/lib/python2.7/site-packages/pymongo-2.4.2-py2.7-linux-x86_64.egg/pymongo/collection.py", line 359, in insert continue_on_error, self.__uuid_subtype), safe) InvalidStringData: ('strings in documents must be valid UTF-8', 'doc: ~~~~Dave BrondsemaThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/7096/https://forge-allura.apache.org/p/allura/tickets/7081/Sometimes we use an eye and sometimes we use a star for activity streams. I think we should be consistent.Dave BrondsemaThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/7081/https://forge-allura.apache.org/p/allura/tickets/7059/If you go to e.g. https://sourceforge.net/p/konfidi/code/499/tarball it says its generating (but its not) and it takes a long time (could know instantly) to figure out that there's not a running job. If there's no file, and no busy/ready task to make one, we know that right away and can just prompt the user to resubmit w/o any delay. In this case, we also should not show a "Generating snapshot..." message when the page loads.Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/7059/https://forge-allura.apache.org/p/allura/tickets/7051/[forge:site-support:#6347] >Another followup from the cygwin-ports upgrade: >/p/cygwin-ports/admin/tools and (intermittently) other pages under /p/cygwin-ports/ are showing the 500 error page, where the same pages for fedora-cygwin display correctly. I suspect that there is a bottleneck in the code triggered by the sheer number of git repos in cygwin-ports. It's showing a timeout style 500, not a code error one. Also, in case you have any workarounds, the primary goals they have right now are re-organizing repo order, and changing the external link target for the "donate" tool.Chris TsaiThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7051/https://forge-allura.apache.org/p/allura/tickets/7027//nf/tool_icon_css is a dynamically created CSS file. It is currently cached via etag headers, but that means a request still goes to the server and it has to respond with a 304. So this is a lot of extra requests (on sf.net, ~35% of /nf/tool_icon_css requests are 304s) We should set a future expires header, and then do cache-busting with a unique URL by appending `?{{config.build_key}}` (build_key is already used for this purpose for all our other static resources)Dave BrondsemaThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7027/https://forge-allura.apache.org/p/allura/tickets/6994/Identify and implement at least two speedups (preferably) or other improvements to our test suite.Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6994/https://forge-allura.apache.org/p/allura/tickets/6971/If you try to submit a task at /nf/admin/task_manager/new it doesn't let you set c.project to a user-project. E.g. if you enter `/u/brondsem` you get `Invalid project: brondsem`. I suspect this is because of the "u/" prefix on user-project's shortnames. Dave BrondsemaThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6971/https://forge-allura.apache.org/p/allura/tickets/6964/Right now we only create a commit activity if we can look up an Allura user for the commit author's email address. Instead, we should create an activity regardless.Tim Van SteenburghThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/6964/https://forge-allura.apache.org/p/allura/tickets/6963/Also, create an activity for the import itself, once it finishes.Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6963/https://forge-allura.apache.org/p/allura/tickets/6947/One activity is created for the ticket update, and one for the comment that is automatically created when a ticket is updated. Should consolidate this down to just one activity per ticket update.Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6947/https://forge-allura.apache.org/p/allura/tickets/6942/There is currently no way for an external tool to provide a custom icon for the top nav bar. https://sourceforge.net/p/allura/chat/2013/02/27/ provides a thorough explanation of the problem. Fix this so that a custom tool can provide it's own icons without needing to modify the theme (which is impractical).Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6942/https://forge-allura.apache.org/p/allura/tickets/6941/Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6941/https://forge-allura.apache.org/p/allura/tickets/6930/[forge:site-support:#6084] >When I renamed a blog post, I got a notification that states it was renamed from the *new* name to the *old* name. It is confusing. Confirmed.Chris TsaiThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/6930/https://forge-allura.apache.org/p/allura/tickets/6917/See [#6904] for back story.Tim Van SteenburghThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6917/