You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/07/29 05:52:15 UTC
[jira] Created: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Tool to look at HLogs -- parse and tail -f
------------------------------------------
Key: HBASE-2889
URL: https://issues.apache.org/jira/browse/HBASE-2889
Project: HBase
Issue Type: Bug
Components: wal
Reporter: stack
Assignee: stack
Fix For: 0.90.0
We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
>From Kannan:
{code}20:45 <kannan> WALEdit already has a toString().
20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-2889:
-------------------------
Attachment: 2889.txt
Add to hlog main:
+ Emission of filename, position, and edit count if issue. We used to do this:
{code}
$ ./bin/hbase org.apache.hadoop.hbase.regionserver.wal.HLog --dump ~/Downloads/10.10.21.18%3A60020.1283907407862 > /dev/null
java.io.IOException: File is corrupt!
at org.apache.hadoop.io.SequenceFile$Reader.readRecordLength(SequenceFile.java:1907)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1932)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1837)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1883)
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:121)
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:113)
at org.apache.hadoop.hbase.regionserver.wal.HLog.dump(HLog.java:1817)
at org.apache.hadoop.hbase.regionserver.wal.HLog.main(HLog.java:1867)
{code}
... now we do this:
{code}
$ ./bin/hbase org.apache.hadoop.hbase.regionserver.wal.HLog --dump ~/Downloads/10.10.21.18%3A60020.1283907407862 > /dev/nulljava.io.IOException: /Users/Stack/Downloads/10.10.21.18%3A60020.1283907407862, pos=20076465, edit=6928
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.addFileInfoToException(SequenceFileLogReader.java:165)
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:137)
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:122)
at org.apache.hadoop.hbase.regionserver.wal.HLog.dump(HLog.java:1817)
at org.apache.hadoop.hbase.regionserver.wal.HLog.main(HLog.java:1867)
Caused by: java.io.IOException: File is corrupt!
at org.apache.hadoop.io.SequenceFile$Reader.readRecordLength(SequenceFile.java:1907)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1932)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1837)
at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:1883)
at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:135)
{code}
+ Made it so if an error, the program returns non-zero exit value.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907532#action_12907532 ]
Jeff Hammerbacher commented on HBASE-2889:
------------------------------------------
FWIW, if the WAL were serialized as Avro records, tools in many languages would be available for looking at the logs. There may be other drawbacks, of course.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918327#action_12918327 ]
stack commented on HBASE-2889:
------------------------------
There is another piece to do, the bit Kannan wanted where you could tail a live WAL and see the edits stream by. Thats the piece that is keeping this issue open and that won't be done for 0.90 (sorry, this issue got a bit messy with two commits against it).
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-2889:
-------------------------
Fix Version/s: (was: 0.90.0)
Moving out. Don't need to finish this 'feature' for 0.90.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907829#action_12907829 ]
Andrew Purtell commented on HBASE-2889:
---------------------------------------
@Jeff: HBASE-2055 is open for that. It's been a while, perhaps we can circle back to it soon.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918325#action_12918325 ]
Nicolas Spiegelberg commented on HBASE-2889:
--------------------------------------------
Is this not already committed in 0.90? We have these patches applied internally and have been running the tool without problem.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914274#action_12914274 ]
Nicolas Spiegelberg commented on HBASE-2889:
--------------------------------------------
FYI: the current patch downgrades all derived classes to an IOE. e.g. any code to detect EOFExceptions will not be triggered. The general problem we seem to have is that we need to differentiate between a Network IOE and a File Format IOE.
Network = we need to fail and let another server try to take over
FileFormat = our file was written or parsed incorrectly. retrying won't fix anything. We need to just open what we have and store the original file away for later analysis.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907102#action_12907102 ]
stack commented on HBASE-2889:
------------------------------
There is already
{code}
$ hbase/bin/hbase org.apache.hadoop.hbase.regionserver.wal.HLog --dump hdfs://example.com:9000/hbase/10.10.21.18%3A60020.1283907407862
{code}
Need to make it tail...
Also, need to add this to the dump command:
{code}
Index: src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java
===================================================================
--- src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java (revision 993076)
+++ src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java (working copy)
@@ -1830,9 +1830,12 @@
}
Reader log = getReader(fs, logPath, conf);
try {
+ int count = 0;
HLog.Entry entry;
while ((entry = log.next()) != null) {
- System.out.println(entry.toString());
+ System.out.println("#" + count + ", pos=" + log.getPosition() +
+ " " + entry.toString());
+ count++;
}
} finally {
log.close();
{code}
... so can see where emitted edit is in file.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914323#action_12914323 ]
stack commented on HBASE-2889:
------------------------------
@Nicolas Committed your HBASE-2889_2.patch. Thanks for fixing my booboo.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Spiegelberg updated HBASE-2889:
---------------------------------------
Attachment: HBASE-2889_2.patch
generalized the fix on trunk, using reflection. also added a couple variables that I've found helpful while dealing with EOF problems. should be able to apply this against trunk (r1000684)
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914280#action_12914280 ]
stack commented on HBASE-2889:
------------------------------
@Nicolas You referring to this method: addFileInfoToException? Should I open issue to fix?
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907369#action_12907369 ]
Kannan Muthukkaruppan commented on HBASE-2889:
----------------------------------------------
Thanks for the update on this Stack.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2889) Tool to look at HLogs -- parse and
tail -f
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907356#action_12907356 ]
stack commented on HBASE-2889:
------------------------------
I commtted the 2889.txt patch for now to branch and trunk. There is still tailing of hlogs to add before can close this issue.
> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
> Key: HBASE-2889
> URL: https://issues.apache.org/jira/browse/HBASE-2889
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> We need a tool for looking at wals. A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.