tag:open-radar.lighthouseapp.com,2008-11-16:/projects/20008-openradar/eventsopen-radar / OpenRadar Events2008-11-17T00:34:27Ztag:open-radar.lighthouseapp.com,2008-11-16:Event/397516842023-07-07T06:44:00-10:002023-07-07T06:43:43-10:00CalionOpenRadar: “A server error occurred. Please contact the administrator.” [#24]<div><p>OpenRadar no longer seems to be working. When I try to submit a
report, I get “A server error occurred. Please contact the
administrator.”</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/268096982013-11-11T08:54:06-10:002013-11-11T08:54:05-10:00Scott CunninghamOpenRadar: Google Chrome, Spotify and MS Office is broken [#23]<div><p>I tried to install an extension to Google Chrome (here: <a href=
"https://chrome.google.com/webstore/detail/scraper/mbigbapnjcgaffohmbkdlecaccepngjd?hl=en">
https://chrome.google.com/webstore/detail/scraper/mbigbapnjcgaffohm...</a>)
on Friday. Mid-way through the install, Chrome froze up. I hard
quit and when I tried to reopen Chrome, I got the following error
(below and attached screenshot). The same error shows up for
Spotify, too, but not LaTeX, OmniFocus or a few other things. When
I try to open Word or Excel, I get a different error (the errors
associated with their particular bug-tracking) in appearance, but
is otherwise the same thing as I cannot use Word or Excel either.
Any help would be much appreciated.</p>
<p>Process: Google Chrome <a href="/projects/20008/changesets/5381"
title="Changeset [5381]">[5381]</a><br>
Path: /Applications/Google Chrome.app/Contents/MacOS/Google
Chrome<br>
Identifier: com.google.Chrome<br>
Version: 30.0.1599.101 (1599.101)<br>
Code Type: X86 (Native)<br>
Parent Process: launchd <a href="/projects/20008/changesets/243"
title="Changeset [243]">[243]</a><br>
User ID: 1263807072</p>
<p>Date/Time: 2013-11-11 12:13:46.182 -0600<br>
OS Version: Mac OS X 10.8.5 (12F45)<br>
Report Version: 10</p>
<p>Interval Since Last Report: 4892 sec<br>
Crashes Since Last Report: 14<br>
Per-App Interval Since Last Report: 1 sec<br>
Per-App Crashes Since Last Report: 1<br>
Anonymous UUID: ABE5642E-F996-439E-0F64-6DF36F6893DE</p>
<p>Crashed Thread: 0 CrBrowserMain Dispatch queue:
com.apple.main-thread</p>
<p>Exception Type: EXC_CRASH (SIGABRT)<br>
Exception Codes: 0x0000000000000000, 0x0000000000000000</p>
<p>Application Specific Information:<br>
Assertion failed: (0 && "You have encountered
<a>rdar://problem/11260511</a>. " "Please run the gather_files.sh
command that's attached to the radar:" "sudo gather_files.sh" "Then
attach the following file to the radar:" "/tmp/crash_files.tz"
"Thanks!"), function cvms_element_hack_check_for_zero_contents,
file /SourceCache/CVMS/CVMS-32.5/coreVMClient.c, line 1552.</p>
<p>Thread 0 Crashed:: CrBrowserMain Dispatch queue:
com.apple.main-thread<br>
0 libsystem_kernel.dylib 0x94651a6a __pthread_kill + 10<br>
1 libsystem_c.dylib 0x92c27b2f pthread_kill + 101<br>
2 libsystem_c.dylib 0x92c5e631 abort + 168<br>
3 libsystem_c.dylib 0x92c6c4f6 __assert_rtn + 326<br>
4 libCoreVMClient.dylib 0x92f88113 cvms_element_get_content +
1113<br>
5 libcldcpuengine.dylib 0x0900699f 0x9000000 + 27039<br>
6 libcldcpuengine.dylib 0x090046c9 glrCompBuildProgram + 95<br>
7 com.apple.opencl 0x92fb6948 0x92f8d000 + 170312<br>
8 com.apple.opencl 0x92f9dffb clBuildProgram + 882<br>
9 com.apple.CoreImage 0x995975cc -[FEOpenCLContext
<em>loadKernel:target:testOnly:] + 1183<br>
10 com.apple.CoreImage 0x996a7e3c -[FEContext(Kernel)
loadKernel:target:] + 84<br>
11 com.apple.CoreImage 0x995d4b39
FEApplyTreeNode::render1(FETreeContext*, FEShape const&,
fe_kernel_target_struct*, int, float*, FETreeTexture*) + 85<br>
12 com.apple.CoreImage 0x995d5b83
FEApplyTreeNode::render2(FETreeContext*, FEShape const*, void
(*)(FEContext*, void*, FEFormat), void (*)(FEContext*, void*),
void*) + 1621<br>
13 com.apple.CoreImage 0x995d2deb
FETreeNode::render</em>(FETreeContext*, FEShape const*, void
(*)(FEContext*, void*, FEFormat), void (*)(FEContext*, void*),
void*) + 151<br>
14 com.apple.CoreImage 0x995d2fb3 FETreeNode::renderTexture(void*,
CGRect, FEFormat, void (*)(FEContext*, void*, FEFormat), void
(*)(FEContext*, void*), void*) + 69<br>
15 com.apple.CoreImage 0x995cd793
FETexture::retainTextureObject(FETextureCache*, FEContext*,
unsigned int, void*, void (*)(void*, CGRect, FEFormat, void
(*)(FEContext*, void*, FEFormat), void (*)(FEContext*, void*),
void*), CGRect const*, bool, fe_texture_object_struct**) + 749</p>
<p>< SNIP ></p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/134731052011-05-17T21:02:50-10:002011-05-17T21:02:50-10:00WilsonLaidlawOpenRadar: Cannot edit TIFF's from iPhoto 11 in Photoshop due to iPhoto adding JPEG file tag [#22]<div><p>Please see Bug submitted to Apple. Apple advises this known bug
and now being worked on. Quickly I hope, as I am having to use
Media Pro for an image library at the moment. iPhoto no longer
works for me, as I work 100% in TIFF files and cannot edit any
files stored in iPhoto since iPhoto 11 update.</p>
<p>Summary:iPhoto 9.1.3 is exporting TIFF files to external editor
e.g Photoshop but changing file tag to JPEG suffix</p>
<p>Steps to Reproduce:Set Photoshop CS5 as external editor. Select
TIFF image stored in iPhoto event after iPhoto 11 upgrade and click
on Edit button. Image will not open in Photoshop, as iPhoto has
appended a JPEG file tag to TIFF file. This results in JPEG read
error in Photoshop. Not surprising as it is a TIFF file not a JPEG
one.</p>
<p>Expected Results: TIFF file should open in Photoshop CS5</p>
<p>Actual Results:JPEG read error - see screenshot attached</p>
<p>Regression:If you drill down to originals of image in iPhoto
library the same image that will not open via iPhoto editor, can be
opened from Finder.</p>
<p>Notes:This is consistent across both my 2009 2.53 GHz 13" MBP
and my 2007 2.16GHz 20" iMac. Using Photoshop CS5, V 12.0.4, so not
a configuration issue. It makes no difference if you use iPhoto as
imported or referenced library.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/57856202010-01-10T13:10:34-10:002010-01-10T13:10:34-10:00Allister BanksOpenRadar: Dates seem to be screwy [#20]<div><p>This was created yesterday, and instead shows an open date of
12/9/2010<br>
<a href=
"http://openradar.appspot.com/7527256">http://openradar.appspot.com/7527256</a><br>
Thanks</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/52757202009-11-18T12:51:27-10:002009-11-18T12:55:00-10:00jumOpenRadar: can't show next page after page 26 [#19]<div><p>Go to page 26 of the openradar problem list <a href=
"http://www.openradar.me/page/26">http://www.openradar.me/page/26</a>.<br>
Click the "Next" button and you'll get the following error
messages:</p>
<pre>
<code>Traceback (most recent call last):
File "/base/python_lib/versions/1/google/appengine/ext/webapp/__init__.py", line 507, in __call__
handler.get(*groups)
File "/base/data/home/apps/openradar/1.336484497024750836/main.py", line 46, in get
radars = db.GqlQuery("select * from Radar order by number desc").fetch(PAGESIZE,(int(number)-1)*PAGESIZE)
File "/base/python_lib/versions/1/google/appengine/ext/db/__init__.py", line 1579, in fetch
raw = raw_query.Get(limit, offset)
File "/base/python_lib/versions/1/google/appengine/api/datastore.py", line 1063, in Get
prefetch_count=limit)._Get(limit)
File "/base/python_lib/versions/1/google/appengine/api/datastore.py", line 1000, in _Run
raise _ToDatastoreError(err)
BadRequestError: offset may not be above 1000</code>
</pre></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/29596232009-04-01T08:53:36-10:002009-04-01T08:53:36-10:00SidneySMOpenRadar: Handler for rdar:// URLs [#18]<div><p>Looks like Dave Dribin has already put this together.</p>
<p><a href="http://www.dribin.org/dave/software/#radarforwarder">http://www.dribin.org/dave/softw...</a></p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/28392132009-03-20T12:05:11-10:002009-03-20T12:05:11-10:00SidneySMOpenRadar: Handler for rdar:// URLs [#18]<div><p>I remember reading early on that a utility was going to be
created that catches <code>rdar://xxxxxx</code> and
<code>rdar://problem/xxxxxx</code> and sends them to OpenRadar.</p>
<p>Has there been any progress on this front? If not, I'd be happy
to whip one up.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/26069622009-02-26T12:18:03-10:002009-02-26T12:18:03-10:00Jonathan SaggauOpenRadar: APIAddRadarAction broken [#16]<div><p>Erg. So the markup messed-up the patch. I think it's clear
enough what changes need to be made. Looks like the model was
changed at some point and not the upload api.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/26069182009-02-26T12:15:44-10:002009-02-26T12:15:44-10:00Jonathan SaggauOpenRadar: Can't re-upload all data from backup [#17]<div><p>I'm trying to get a local copy of the data on the live appspot
application loaded into the dev_appserver environment on my local
machine.</p>
<p>I've downloaded the entire contents of openradar using the
included nukefile (nu rocks) and stored the resulting json to disk.
I've added api in main.py based on the already present uploading of
radars code to allow the upload of comments and written a little
python to upload the radars and comments into the locally running
dev server. All is working except threaded comments and
users.<br></p>
<p>One can't really get around the users problem on the local
machine as the set of users google is using is, well, the set of
users that google is using. That's not such a big deal for local
development (though I think I <em>might</em> have a way around that
brewing).</p>
<p>The comment.is_reply_to.key().id() that is exported when
downloading the json is the read-only unique ID of the unique key
that is assigned by app engine when the comment is created. It's
not possible as far as I can tell, without modifying the model, to
recreate comment threads when re-uploading data.</p>
<p>Possible solution: I can re-upload radars because they are
referenced by apple's radar numbers in the number attribute and not
by the google app engine unique ID. Perhaps we could create an
identifying unique (UUID perhaps?) attribute on comments that is
independent of comment.is_reply_to.key().id() so that threaded
comments can be downloaded and then re-uploaded with the threaded
is_reply_to relationships intact.</p>
<p>This will improve portability and make it easier for those who
wish to hack locally on some "real" data.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/25822832009-02-24T20:15:58-10:002009-02-24T20:15:58-10:00Jonathan SaggauOpenRadar: APIAddRadarAction broken [#16]<div><p>Hi Tim</p>
<p>Been poking at API and found the radar addition nonfunctional.
The patch below <em>seems</em> to fit the Radar model and follow
the conventions of your post method.</p>
<p>diff --git a/main.py b/main.py index e6f62a4..dec27c5 100755 ---
a/main.py +++ b/main.py @@ -312,9 +312,10 @@ class
APIAddRadarAction(Handler):</p>
<pre>
<code> description = self.request.get("description")
product = self.request.get("product")
classification = self.request.get("classification")
</code>
</pre>
<ul>
<li>reproducible = int(self.request.get("reproducible"))</li>
<li>reproducible = self.request.get("reproducible") product_version
= self.request.get("product_version") originated =
self.request.get("originated")</li>
<li>resolved = self.request.get("resolved") radar =
Radar(title=title,
<pre>
<code> number=number,
user=user,
</code>
</pre></li>
</ul>
<p>Jonathan Saggau</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/22241042009-01-20T04:21:03-10:002009-01-20T04:21:03-10:00Patrick McCarronOpenRadar: Odd Error On OpenRadar [#15]<div><p>It may just be a problem with Google, but when poking around on
OpenRadar this morning I got the following error (attached) when
opening this URL off of the main OpenRadar page.</p>
<p><a href="http://openradar.appspot.com/6500090">http://openradar.appspot.com/650...</a></p>
<p>I wasn't doing anything fancy, so it may just be a Google system
issue. I refreshed and it went away. I was also not signed into my
OpenRadar account, if that makes a difference.<br></p>
<p>Also since I didn't know where to post bugs, maybe there is a
way to add a link to this LighthouseApp page to report problems
when OpenRadar produces a bug?</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/21422812009-01-10T09:21:43-10:002009-01-10T09:21:43-10:00Joachim BengtssonOpenRadar: The OpenRadar site should link to this bug tracker. [#14]<div><p>^^^^</p>
<p>Right now the user needs to first click through to the wiki to
even realize we have a bug tracker.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/18082672008-11-24T20:47:02-10:002008-11-24T20:47:02-10:00tim+openradar (at neontology)OpenRadar: Support full text search [#13]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
<li>Assigned user set to <em class="change">“tim+openradar (at neontology)”</em></li>
<div><p>I updated Radars to use SearchableModel, made a one-term search
index, and added a search box to the top right of all OpenRadar
pages. The results aren't perfect, but they work for lots of cases,
and I put a google custom search engine widget on the search
results page as a backup.</p>
<p>Let's see how well this works.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/18041462008-11-24T09:45:10-10:002008-11-24T09:45:10-10:00Dave DribinOpenRadar: Support full text search [#13]<div><p>It is currently not possible to search existing bugs. Google App
Engine does not support full text search out of the box, so we're
kinda SOL. There does appear to be some support via the
SearchableModel, but I don't know how stable/public it is.</p>
<p><a href="http://appengineguy.com/2008/06/how-to-full-text-search-in-google-app.html">
http://appengineguy.com/2008/06/...</a></p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17859682008-11-21T06:20:33-10:002008-11-21T06:20:33-10:00Joachim BengtssonOpenRadar: Email notification on comment reply [#12]<div><p>When someone replies to a comment you have written, an email
should be sent to your email. This also goes for new comments on
bugs you have filed.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17418372008-11-17T04:34:09-10:002008-11-17T04:34:09-10:00MoOpenRadar: Placeholders/duplicate tracking [#11]<div><p>(Related to ticket <a href="/projects/20008/tickets/4" title="Ticket #4">#4</a>)</p>
<p>All the duplicates of a particular Radar should be listed
against the entry for that Radar.</p>
<p>If the Radar doesn't exist when it's the
“target” of a dupe, the ideal would be to create a
placeholder for it (i.e., “Details of this Radar have not
been submitted yet, however the following Radars are marked as
being duplicates of it:”)</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17418222008-11-17T04:30:35-10:002008-11-17T04:30:35-10:00MoOpenRadar: Detect and link duplicates [#4]<div><p>Having slept on it, I think you're right about focus,
there—links should generally be to OpenRadar, rather than
rdar://.</p>
<p>I quite like the [R] idea. You could possibly misappropriate the
registered-trademark symbol to indicate “this is a rdar:///
link for the aforementioned item”.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17418072008-11-17T04:28:50-10:002008-11-17T04:28:50-10:00MoOpenRadar: radar # vs. openradar id # [#10]<div><p>For what it's worth, you can do:</p>
<p><a href="http://openradar.appspot.com/rdar?number=6376302">http://openradar.appspot.com/rda...</a></p>
<p>However, my opinion is that it'd be good if OpenRadar supported
URLs in the form:</p>
<p><a href="http://openradar.appspot.com/6376302">http://openradar.appspot.com/637...</a></p>
<p>though some geeks might prefer:</p>
<p><a href="http://openradar.appspot.com/problem/6376302">http://openradar.appspot.com/pro...</a></p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17396042008-11-16T21:28:15-10:002008-11-16T21:30:00-10:00silencioOpenRadar: radar # vs. openradar id # [#10]<div><p>I have yet to come up with a good argument for or against this,
but the openradar ID number is different from the corresponding
radar number. Until there's some way to search the rapidly growing
list by the radar number, it would be pretty nice to have it so I
can go to <a href="http://openradar.appspot.com/radar?id=6376302">http://openradar.appspot.com/rad...</a>
instead of <a href="http://openradar.appspot.com/radar?id=298">http://openradar.appspot.com/rad...</a>
for rdar://problem/6376302</p>
<p>This would also make it a lot easier to deal with ticket
<a href="/projects/20008/tickets/4" title="Ticket #4">#4</a>, where
you can just then detect all numbers similarly formatted to radar
numbers and link them appropriately, and possibly by color to show
whether or not the radar details are available in open radar (a la
wikipedia).</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17392802008-11-16T19:29:38-10:002008-11-16T19:29:38-10:00tim+openradar (at neontology)OpenRadar: Twitter feed too verbose [#9]<li>State changed from <em class="change">“new”</em> to <em class="change">“resolved”</em></li>
<div><p>OK, done!</p>
<p>The full feed is now directed to @openradarstream. @openradar
will be used for everything else.</p>
<p>Originally the only reason I picked up @openradar was to provide
the stream; I didn't anticipate people wanting to talk so much
about it.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17391862008-11-16T19:03:48-10:002008-11-16T19:03:49-10:00SidneySMOpenRadar: Detect and link duplicates [#4]<li>Assigned user set to <em class="change">“tim+openradar (at neontology)”</em></li>
<div><p>I support (c), linking to OpenRadar, as a significant chunk of
users will be outside Apple and unable to use the rdar:// links
without RadarForwarder.</p>
<p>We should tailor it to casual visitors who just want to browse
the bugs.</p>
<p>Alternately (at the expense of a clean list), we could format
statuses as "Duplicate /XXXXXXX [R]" with both internal and rdar://
links.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17391622008-11-16T18:55:50-10:002008-11-16T18:55:50-10:00SidneySMOpenRadar: Twitter feed too verbose [#9]<div><p>If our goal with Open Radar/OpenRadar is to keep track of every
Apple bug we can get our hands on, that's gonna result in one
monstrous Twitter feed.</p>
<p>Can we reduce it to just site updates? I've seen a few DMs pop
up already from users who started following @openradar and then
stopped because their feeds were being flooded.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17391252008-11-16T18:42:41-10:002008-11-16T18:42:41-10:00Mike AkersOpenRadar: Each bug should have a public comment thread [#8]<div><p>Each bug report should have a public comment thread associated
with it. This way we can share workarounds and if Apple's looking
at Open Radar it may help them figure out what's wrong.</p>
<p>Bugs marked duplicate should have commenting disabled I
guess.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17391232008-11-16T18:42:00-10:002008-11-16T18:42:00-10:00Nello LucchesiOpenRadar: Unicode Characters Supported? [#7]<div><p>I tried entering some Chinese characters and got the error
below.</p>
<p>Don't you guys support Unicode?!?</p>
<ul>
<li>nello</li>
</ul>
<p>Traceback (most recent call last): File
"/base/python_lib/versions/1/google/appengine/ext/webapp/<strong>init</strong>.py",
line 501, in <strong>call</strong></p>
<pre>
<code>handler.post(*groups)
</code>
</pre>
<p>File
"/base/data/home/apps/openradar/1.329335884027771980/main.py", line
56, in post</p>
<pre>
<code>form_data = urllib.urlencode(form_fields)
</code>
</pre>
<p>File "/base/python_dist/lib/python2.5/urllib.py", line 1250, in
urlencode</p>
<pre>
<code>v = quote_plus(str(v))
</code>
</pre>
<p>UnicodeEncodeError: 'ascii' codec can't encode character
u'\u5e8a' in position 48: ordinal not in range(128)</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17390202008-11-16T17:59:44-10:002008-11-16T17:59:44-10:00tim+openradar (at neontology)OpenRadar: Wrong escaping of +/' in Twitter feed [#6]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
<li>Assigned user set to <em class="change">“tim+openradar (at neontology)”</em></li>
tag:open-radar.lighthouseapp.com,2008-11-16:Event/17390172008-11-16T17:59:08-10:002008-11-16T17:59:08-10:00tim+openradar (at neontology)OpenRadar: Add user profiles [#2]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
tag:open-radar.lighthouseapp.com,2008-11-16:Event/17390152008-11-16T17:58:38-10:002008-11-16T17:58:38-10:00tim+openradar (at neontology)OpenRadar: Download links for OpenRadar.app and RadarForwarder.app [#5]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
tag:open-radar.lighthouseapp.com,2008-11-16:Event/17390142008-11-16T17:58:28-10:002008-11-16T17:58:28-10:00tim+openradar (at neontology)OpenRadar: Download links for OpenRadar.app and RadarForwarder.app [#5]<li>Assigned user set to <em class="change">“tim+openradar (at neontology)”</em></li>
tag:open-radar.lighthouseapp.com,2008-11-16:Event/17388172008-11-16T16:52:33-10:002008-11-16T16:52:56-10:00astrangeOpenRadar: Wrong escaping of +/' in Twitter feed [#6]<div><p>These bug titles:</p>
<p><a href="http://openradar.appspot.com/radar?id=71">http://openradar.appspot.com/rad...</a>
Calculator: Help Does Not Mention Programmer View's Truncation of
Decimals</p>
<p><a href="http://openradar.appspot.com/radar?id=78">http://openradar.appspot.com/rad...</a>
as/i386 compiles 4+(%esp) to 0(%esp)</p>
<p>got Twittered as:</p>
<p>[rdar://4515866] lemnar: Calculator: Help Does Not Mention
Programmer View's Truncation of Decimals</p>
<p>[rdar://5828463] astrange: as/i386 compiles 4 (%esp) to
0(%esp)</p>
<p>with the ' getting escaped to ' and the + not getting escaped
and disappearing.</p></div>tag:open-radar.lighthouseapp.com,2008-11-16:Event/17383912008-11-16T14:34:27-10:002008-11-16T14:34:27-10:00MoOpenRadar: Download links for OpenRadar.app and RadarForwarder.app [#5]<div><p>Links to OpenRadar.app and RadarForwarder.app should probably be
added to the FAQ.</p>
<p>…well, once binary downloads of the both of them are
available, of course.</p></div>