Bug Advisory: Leading BFC Statements

[Orion Pobursky]

A bug in the Parts Tracker is stripping any BFC statements that are the first line of the part body.

Example

Code:

<part header>

0 BFC INVERTNEXT
1 0 0 0 0 1 0 0 0 1 0 0 0 1 2-4cyli.dat

In the above case the "BFC INVERTNEXT" statement would be removed.

To mitigate this issue, have at least one non-BFC line as the start of the body

Example:

Code:

<part header>

1 0 0 20 0 1 0 0 0 1 0 0 0 1 stud.dat
0 BFC INVERTNEXT
1 0 0 0 0 1 0 0 0 1 0 0 0 1 2-4cyli.dat

The above BFC statement will not be affected.

This bug has the potential to affect all parts submitted, released, or header edited since approximately Julyl 16.

[Travis Cobbs]

A bug in the Parts Tracker is stripping any BFC statements that are the first line of the part body.

Does the BFC CERTIFY/NOTCERTIFY statement count as part of the header, so it is not impacted by this? Because if not, then I think it would be impossible to have any parts that don't violate the specs.

[Orion Pobursky]

Does the BFC CERTIFY/NOTCERTIFY statement count as part of the header, so it is not impacted by this? Because if not, then I think it would be impossible to have any parts that don't violate the specs.

The header and the body are parsed separately. The header is unaffected by the bug.

[Orion Pobursky]

The bug is fixed. All potentially affected files have not been checked