Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Check your recent bugs (was: [] Infra update)


Thanks for the update.  I noticed that there might be some data loss with bugzilla.  I've got an email in my inbox for a bug that was posted.  When I click on the link, a different bug exists there with the same id.  

I've included the content of the email for your information below.


Product/Component: Mylyn / WikiText
          Summary: [patch] Support Confluence key-only options and
          Product: Mylyn
          Version: unspecified
         Platform: All
       OS/Version: All
           Status: NEW
         Severity: enhancement
         Priority: P3
        Component: WikiText
       AssignedTo: dgreen99@xxxxxxxxx
       ReportedBy: Bart.Schuller@xxxxxxxxx

In a Confluence {code} block, you can specify the syntax using {code:html}.

It looks like wikitext ParameterizedBlock only supports {block:key=value} at
the moment, so I changed this to record {block:option} as an Option with value

To actually make use of this, I also changed CodeBlock to record any options
besides title as a new "syntax" field, which is copied to the block's
attribute's cssClass when rendering.

The net result is that {code:html} becomes <code class="html">, which is
excellent if you then add to the page, which will
add syntax highlighting.

I'll illustrate the above using a patch.

Background: We are heavy users of syntax-highlighted code blocks in both
Confluence and Jira. I am writing my own issue tracker which I'd like to
support the same syntax, so textile-j/wikitext (as a standalone library) is
very useful to me. But when I find differences between it and Confluence
itself, I'll try to patch my way to feature parity.

On Sun, Feb 15, 2009 at 1:16 PM, Eclipse Webmaster (Denis Roy) <webmaster@xxxxxxxxxxx> wrote:

Some server maintenance we have performed over the weekend didn't go as smoothly as planned; as a result, we are currently only running one file/database server instead of the usual two.

Although database data (bugzilla, wiki pages, etc) is synced in realtime, file sync is not realtime, and therefore the current CVS/SVN/download data being used may be a few hours behind the failed server's data.  I recommend you sync your workspaces and downloads area as soon as you can.

We'll be working on restoring our secondary file/database server this week, but expect a noticeable performance degradation across all our services (especially bugzilla) while we're only running a single storage server.

On a related note, disk space has reached a critical level of 94% used, with only 54G of free disk space for CVS, SVN and the downloads/archives area.  Although we have a few terabytes of new storage, the current server failure is interfering with our efforts to put it into production.  Anything you can do to free up disk space in the download/archives areas will definitely help us avoid a "No more space left on device" error.

I suspect everything should be back to normal towards the end of the week.

Thanks for your cooperation,

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top