Redmine: Issueshttps://redmine.auroville.org.in/https://redmine.auroville.org.in/favicon.ico2023-09-29T10:10:07ZRedmine
Redmine Gisaf - Bug #15204 (Resolved): Bad request message while entering newwell level datahttps://redmine.auroville.org.in/issues/152042023-09-29T10:10:07ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>While trying to enter new well level, an error message pops up saying "Network error: Bad request" (see attached screenshot)</p> Tree Trail - Bug #14473 (New): Data not refreshedhttps://redmine.auroville.org.in/issues/144732022-09-10T10:32:45ZPhilippe MayGisaf - Bug #10819 (Resolved): Evergreen well : popup showing "null" instead of location, status,...https://redmine.auroville.org.in/issues/108192020-08-21T06:53:02ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>While hovering over Evergreen well, the usual info on Location, status and type are not showing. Only a dull "null" and the coordinates are showing...<br />Screenshot attached</p> Gisaf - Bug #10740 (Resolved): Change status: issue with projection systemhttps://redmine.auroville.org.in/issues/107402020-08-06T10:23:53ZPhilippe MayGisaf - Bug #10728 (Resolved): Cannot download CSV for valueshttps://redmine.auroville.org.in/issues/107282020-08-03T10:02:34ZPhilippe May
<p>This is a common issue for all features with values/readings (wells, weather stations, etc)</p> Gisaf - Bug #10360 (Resolved): Cannot import survey: accuracy issuehttps://redmine.auroville.org.in/issues/103602020-06-16T19:58:19ZPhilippe May
<p>Reported by Giulio</p> Gisaf - Bug #10337 (Resolved): Custom layers with a "status" column not displayed on the maphttps://redmine.auroville.org.in/issues/103372020-06-13T12:04:04ZPhilippe May
<p>Reported by AVSST for the cadastral layer</p> Gisaf - Bug #10180 (Resolved): Error importing Johan's shapefilehttps://redmine.auroville.org.in/issues/101802020-05-25T11:15:13ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>While importing Johan's shapefile of Optic Fibers, this error is displayed:<br />"Error: Unexpected import error: duplicate key value violates unique constraint "optical_fiber_pkey" DETAIL: Key (id)=(2) already exists."</p> Gisaf - Bug #10140 (New): Admin: sort out manager rolehttps://redmine.auroville.org.in/issues/101402020-05-19T10:49:25ZPhilippe May
<p>"manager" role is needed to access anything under the "Manage" section of the admin.</p>
<p>This is mixed up with the same "manager" role, which was defined earlier as the role for managing users and permissions.</p> Gisaf - Bug #10125 (Resolved): Feature with Status other than existing, not showing in the map (e...https://redmine.auroville.org.in/issues/101252020-05-18T11:19:52ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Feature with Status other than existing, not showing in the map</p> Gisaf - Bug #10123 (Resolved): Basket Upload: store not savedhttps://redmine.auroville.org.in/issues/101232020-05-18T11:09:31ZGiulio Di Anastasiogiulioenrica@gmail.comGisaf - Bug #9465 (Resolved): Export plots to PNG missing axis labelshttps://redmine.auroville.org.in/issues/94652019-12-19T09:48:19ZPhilippe May
<p>Ex: export from Dashboard/Wells: some names of the wells are missing</p> Gisaf - Bug #9036 (Resolved): Fix login indicatorhttps://redmine.auroville.org.in/issues/90362019-09-25T04:25:31ZPhilippe May
<p>Implement a validation of the logged in state displayed in UI, by querying the user session on the server.</p>
<p>The same mechanism would also provide the roles of the logged in user, for making the UI more relevant to the users's permissions (eg. hide buttons)</p> Gisaf - Bug #8231 (Resolved): Fix status in table definition of new categorieshttps://redmine.auroville.org.in/issues/82312019-05-03T11:17:55ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>V46 VEGE MIEL ----- E Mimusops elengi * Point Mimusops elengi<br />V47 VEGE RAIN ----- E Rain Tree * Point Albizia saman<br />V48 VEGE ELPH ----- E Elephant Ear Tree * Point Enterolobium cyclocarpum<br />V49 VEGE PAMY ----- E Palmyra Tree * Point Borassus flabellifer<br />V50 VEGE KAYA ----- E Khaya Tree * Point Khaya senegalensis<br />V51 VEGE SILK ----- E Silk Cotton Tree * Point Ceiba pentandra<br />V52 VEGE ODIA ----- E Odiamaram Tree * Point Lannea coromandelica<br />V53 VEGE SAUS ----- E Sausage Tree * Point Kigelia africana<br />V54 VEGE KODU ----- E Kodukkapuli * Point Pithecellobium dulce<br />V55 VEGE SISE ----- E Siamese Senna * Point Senna siamea<br />V56 VEGE REDS ----- E Red sandalwood * Point Pterocarpus santalinus<br />V57 VEGE PTSU ----- E Pterospermum * Point Pterospermum suberifolium<br />V58 VEGE MAHA ----- E Mahagony * Point Swietenia mahagoni<br />V59 VEGE TEBE ----- E Beach Almond * Point Terminalia bellerica <br />V60 VEGE ALLE ----- E Integral wisdom * Point Albizia lebbeck<br />V61 VEGE DERE ----- E Flame tree * Point Delonix regia</p> Gisaf - Bug #7584 (In Progress): Error with large integers (graphql)https://redmine.auroville.org.in/issues/75842019-02-06T10:35:09ZPhilippe May
<p>Eg: when the id of a feature is more than 2147483647 (graphene.types.scalars.MAX_INT), the information isn't displayed.</p>
<p>See <a class="external" href="https://docs.graphene-python.org/en/latest/types/scalars/">https://docs.graphene-python.org/en/latest/types/scalars/</a> for a discussion: there's a confusion between the graphql Int specs (max: 2**32 - 1) and the IEEE Int spec (2**53 - 1)</p>