#

### ** This page is awaiting replacement with an automated tracking system. **

## Reporting bugs

First please search the tables below to make sure the bug isn't already known. Second check the documentation and ensure that you're running on a supported version of Java, have the right environment variables set and so on. Third, consider joining the gate-discuss mailing list and getting help there. Finally, if all else fails, send us a bug report as described below.

Please send us a table entry like the following, giving details such as: GATE version and build number; whether you built from source or used a binary; what OS you're using, and which JDK; on UNIX, which windowing system.

      <TR>
        <TD>Number</TD>
        <TD>Subsystem<BR>(core, jape, creole or gui)</TD>
        <TD>Reported by</TD>
        <TD>Adopted by</TD>
        <TD>Reported on<BR>(date/OS/JDK and<BR>GATE versions)</TD>
        <TD>Fixed on<BR>(date/GATE version)</TD>
        <TD>Description</TD>
        <TD>Test method</TD>
        <TD>Supporting materials</TD>
      </TR>

Along with any supporting materials like input files needed to duplicate the bug. Please provide as much information as possible.

## Fixing bugs

- Adopt the bug by filling in the "Adopted by" column and checking in this file.
- Duplicate the bug; if you cannot, mail the person who submitted it and ask them to clarify. If it was fixed in the current version just add "Fixed on..." column.
- Add any necessary supporting materials in the bugs directory under the bug number.
- Add a test to the test suite that reproduces the bug and add the name of the test to the "Test method" column. If the bug can ONLY be reproduced by the GUI, then say "GUI only" in this column.
- Fix the bug; run all the tests.
- Fill in the rest of the table, move the entry to the "fixed" table and check in.

## Known Bugs

Number | Subsystem (core, jape, creole or gui) | Reported by | Adopted by | Reported on (date/OS/JDK and GATE versions) | Fixed on (date/GATE version) | Description | Test method | Supporting materials
--- | --- | --- | --- | --- | --- | --- | --- | ---

0006

core

Valentin

___adopted_by

16/5/1 NT4 1.3.1 a2build499

___fixed_on ___date ___Gversion

AnnotationSetImpl:
Various get() methods return the actual set stored in the indexes internal to AnnotationSetImpl. If such a set obtained from a get() operation is then modified, the modification will be reflected by the results of all the further calls to the same get() method although the base AnnotationSet is not actually modified, hence invalid results.
Probably the desired behaviour is for the returned annotation sets to be backed by the base annotation set so that modifications on the returned sets will reflect in the base set. That could cause a lot of ConcurrentModificationExceptions in the client code but that's their problem. {@see List.subList(start, end).clear(); }

-

-

0008 | core | Valentin | ___adopted_by | 16/5/1 NT4 1.3.1 a2build499 | ___fixed_on ___date ___Gversion | gate.initCreoleRegister is looking in resources/gau for creole.xml when gate.Main starts up - it shouldn't, as this is only for testing | - | -

0011

jape

Valentin

___adopted_by

12 June 01 ALL:ALL Alpha3

___fixed_on ___date ___Gversion

Jape grammars don't have direct access to the input annotation set. They only receive the list of matched annotations. This makes it impossible to reliably remove some of the matched annotations from the input AS. All the grammars that do this are assuming that the input AS is the same as the output one (which is not guaranteed).

___test_method

___supporting_materials

0013 | gui | Diana | ___adopted_by | 27 July 01 Linux 1.3.1 Alpha3 | ___fixed_on ___date ___Gversion | annotation types which are empty do not get automatically removed from the GUI, nor is it possible to remove them manually (with the Delete key) |  |
0015 | gui | Diana | ___adopted_by | 06 Aug 01 Linux 1.3.1 Alpha3 | ___fixed_on ___date ___Gversion | If you manage to create 2 different processing errors/warnings simultaneously (of the type that create pop-up messages), neither pop-up window lets you close it, and nothing can be done until the messages are closed. | ___test_method | ___supporting_materials

00017

gui

Valentin

___adopted_by

01/12/2001 All platforms All JDKs All versions

___fixed_on ___date ___Gversion

The GUI doesn't block while operations are being executed. This allows for multiple threads to be run at the same time which could lead to dangerous situations as the gate API is not thread safe. Although runing things that not affect each other is many times safe it is sometimes difficult to tell whether two certain operations are interfering with each other so the GUI should lock itself not allowing the user to start a new operation before the current one finished.

Workaround: Until the gate developers get their act together and implement some mechanism for locking, the users are advised to show patience and allow each operation to finish before starting a new one. This is particularly important for operations involving datastores and executions of applications.

___test_method

___supporting_materials

## Fixed Bugs

Number | Subsystem (core, jape, creole or gui) | Reported by | Adopted by | Reported on (date/OS/JDK and GATE versions) | Fixed on (date/GATE version) | Description | Test method | Supporting materials
--- | --- | --- | --- | --- | --- | --- | --- | ---
0001 | jape | Horacio | Valentin | April-01 NT4 JDK 1.3 alpha1 | 30th May 2001 Alpha3 build 512 | Infinite loop in jape processing Jape now detects infinite loops and recovers from them by forcing an advance of the input. This might loose some possible matches but it's better than waiting forever. A warning message is displayed on the Err output. |  | directory bugs/0001
0002 | gui | Hamish | Valentin | 16/5/1 linux6.2/solaris7 1.3.1 a2-build499 | 30th May 2001 Alpha3 build 512 | When a datastore is openned, and double-clicked on, before any other resources are created, the resources tree resizes to near zero size | - | -
0003 | gui | Hamish | Cristi | 16/5/1 NT4 1.3.1 a2build499 | Fixed on 18 May 2001 from alpha2 Build 501 | when using larger-than-normal fonts, the annotation diff results at the bottom of the screen sometimes disappear outside the window | - | -
0004 | gui | Hamish | Valentin | 16/5/1 NT4 1.3.1 a2build499 | 16/Oct/2001/alpha 3 | the applications edit component needs some work - it resizes in a strange fashion e.g. when you select a component to add. in general components shouldn't resize when you're clicking in them methinks The component has been fully redesigned | - | -
0005 | gui | Hamish | Valentin | 16/5/1 NT4 1.3.1 a2build499 | 30th May 2001 Alpha3 build 512 | it would be nice if double click on a document in the datastore display tree loaded the document, in line with double clicking in the resource tree | - | -
0007 | core | Valentin | Valentin | 16/5/1 NT4 1.3.1 a2build499 | 1st June 2001 Alpha3 build 517 | when it looks for creole.xml in the file system it downcases the whole path (because it comes from a URL?) | - | -
0009 | creole | Kalina | Oana | 18/May OS:NT Gate a2build499 | 1st June 2001 Alpha3 build 517 | Move the list loading from run to the init method, because they are meant to be read only when the NM is initialised, not every time it's run. | - | -

0010

creole/namematcher

Kalina

Oana

18/May OS:NT Gate a2build499

1st June 2001
Alpha3 build 517

I added BT Cellnet and BT Wireless as spurious matches in the spur_match.lst file. However if you the NM on the file which I created for testing \resources\gate\texts\namematcher-test.txt, then the NM still matches them to BT, when it should not.

just run in GUI, after the NE recogniser, on file namematcher-test from \resources\gate\texts

-

0012 | core | Valentin | Valentin | 13 July 01 ALL:ALL Alpha3 | 1st June 2001 Alpha3 ALL builds | when it looks for creole.xml for an external Gate resource in the file system it downcases the whole path (because it comes from a URL?) | - | -
0014 | gui | Diana | Valentin | 02 Aug 01 Linux 1.3.1 Alpha3 | Oct/2001/ beta1 | When adding new annotations, the popup window which should appear to allow you to select an annotation type etc doesn't always appear. Nothing happens at all, except an error message in the command window of the type "Exception occurred during event dispatching:" | ___test_method | ___supporting_materials
0016 | gui | Oana | Valentin | Oct 2001 Solaris 1.3.X Alpha 3 | Nov 28 2001 Beta1 | The file open dialog on solaris opens with a very large size and displays nothing. | Try to open a file on solaris | ___supporting_materials