Custom Query (1067 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 1067)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#1355 fixed CID 200497: Incorrect expression (UNINTENDED_INTEGER_DIVISION) KaZeR kazer
Description Reported by coverity, following the merge of https://github.com/navit-gps/navit/pull/359

{{{
** CID 200497: Incorrect expression (UNINTENDED_INTEGER_DIVISION)
/navit/gui/gtk/gui_gtk_statusbar.c: 166 in statusbar_route_update()


________________________________________________________________________________________________________
*** CID 200497: Incorrect expression (UNINTENDED_INTEGER_DIVISION)
/navit/gui/gtk/gui_gtk_statusbar.c: 166 in statusbar_route_update()
160 sprintf(this->gps_text,"GPS:%s %02d/%02d HD:%02.2f %s %4.0f%s %3.0f%-2s %3.1f%s",
161 status_fix2str(status),
162 sats, qual, hdop, buffer,
163 imperial ? height * FEET_PER_METER : height,
164 imperial == TRUE ? "\'" : "m",
165 direction, dir,
>>> CID 200497: Incorrect expression (UNINTENDED_INTEGER_DIVISION)
>>> Dividing integer expressions "1609" and "1000", and then converting the integer quotient to type "double". Any remainder, or fractional part of the quotient, is ignored.
166 imperial == TRUE ? speed / (METERS_PER_MILE / 1000) : speed, /* hard-coded. Ugly */
167 imperial == TRUE ? " mph" : "km/h"
168 );
169
170 gtk_label_set_text(GTK_LABEL(this->gps), this->gps_text);
171 }
}}}
#1354 fixed Android build on the CI is broken cp15 kazer
Description Android builds have been failing for a couple of days.

Rebuilding a previously successful build will fail in the `make apkg` phase:

`/opt/android-sdk-linux/tools/ant/build.xml:396: SDK Platform Tools component is missing. Please install it with the SDK Manager (tools/android)`

The most recent successful build is https://circleci.com/gh/navit-gps/navit/3425

Rebuilding it will fail as per https://circleci.com/gh/navit-gps/navit/3660
#1351 fixed revisit tagging system kazer kazer
Description Currently we have to tag releases with tags such as R7165 because we use that to keep track of the versions we push to Google PlayStore (this is a requirement as each new apk pushed to the store must have a version number higher than the previous one).

But using tags for that clutters our release page.

Jkoan has suggested that we switch to using YYYYMMDDHHMM as a version tag for the PlayStore. This does not require permanent storage, is guaranteed to generate a higher version number for each build and should be fairly easy to implement.
1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.