Changes to correctly propagate errors in IVOA TAP queries

The queryMap object was not correctly propagating the status and results for a query that returned a message containing an "ERROR". This change contains a fix to correctly identify this, and propagate it correctly.

src/components/query/QueryIVOARegistry.js

@@ -111,7 +111,6 @@ export default function QueryIVOARegistry() {
       queries = parseQueryForm(gui, formData, regPage);
     }
 
-
     queryMap.clear();
     queries.forEach((query) => {
       queryMap.set(query.catalog, {
@@ -126,12 +125,14 @@ export default function QueryIVOARegistry() {
         .get(url)
         .then((queryResponse) => {
           if(queryStep === "run-query") {
+              let vo_table_schema = queryResponse.data.results ? queryResponse.data.results[0] : null;
+              let status = queryResponse.data.results ? "fetched" : "error";
               queryMap.set(query.catalog, {
                   catalog: query.catalog,
                   service_type: query.service_type,
-                  vo_table_schema: queryResponse.data.results[0],
+                  vo_table_schema: vo_table_schema,
                   esapquery: query.esapquery,
-                  status: "fetched",
+                  status: status,
                   results: queryResponse.data,
               });
 
@@ -145,14 +146,14 @@ export default function QueryIVOARegistry() {
               results: queryResponse.data,
           })};
         })
-        .catch(() => {
+        .catch((error) => {
           queryMap.set(query.catalog, {
             catalog: query.catalog,
             service_type: query.service_type,
             vo_table_schema:"",
             esapquery: query.esapquery,
             status: "error",
-            results: null,
+            results: [error.message],
           });
         });
     });