Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (10 - 12 of 116)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#123 wontfix Parser just holds on syntax error ymipsl ssenesi
Description

When reading an xml construct such as

<field field_ref="albs" default_value="1.e+20"/>/>

which shows a syntax error near to the end of line, Xios parser just holds

If the xml file is quite long, you may spend some tens of minutes searching for the error (assuming you suspect it is a syntax error, and you are not beginning your search elsewhere ....)

#63 invalid Complementing field definition by sourcing from an alternate file does not work ymipsl ssenesi
Description

When wanting to add some field definition by sourcing an alternate file, you should be able to write :

<field_definition> <field id="default_field"domain_ref="FULL"></field_definition> <field_definition id="field_definition" src="./surfex_base.xml" />

where the content of surfex_base.xml is e.g. : <field_definition > <field id="LE" name="leprime" /> </field_definition>

This crashes XIOS with "MPI_ERR_COMM: invalid communicator" (while putting the equivalent content at the same place in the master xml file works fine)

#89 invalid Error in node/domain.cpp on ChecKDomainData ymipsl ssenesi
Description

It reads on line 792 as

      if (data_ni.isEmpty())
      {
        data_ni.setValue((data_dim == 1) ? (ni.getValue() * nj.getValue()) : ni.getValue());
      }

which is obviously wrong (set values should be reversed). This actually causes segmentation violation when nj is not set and data_dim==1; and this should lead to underestimated allocation when data_dim==2

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Note: See TracQuery for help on using queries.