You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
console.log(`Got result for ${engine.short_name}`,result,index);
125
-
setState(prevResult=>{
126
-
console.log("Setting state: before",prevResult);
127
-
constnewResult=[...prevResult];
128
-
newResult[index]=result;
129
-
console.log("Setting state: after",newResult);
130
-
returnnewResult;
131
-
});
132
-
});
133
-
});
134
-
},[]);
135
-
136
-
React.useEffect(()=>{
137
-
console.log("useEffect");
138
-
fetchAllResults();
139
-
},[fetchAllResults]);
140
-
141
-
constonRefresh=()=>{
142
-
console.log("Refreshing");
143
-
setState([]);
144
-
fetchAllResults();
145
-
};
146
-
147
-
console.log("Rendering",JSON.stringify(results));
148
11
return(
149
12
<>
150
13
<h1>Current Status</h1>
@@ -153,32 +16,9 @@ export default function Page() {
153
16
Each engine is running in a separate instance. The table below shows the current status of each engine.
154
17
</p>
155
18
<p>
156
-
The engines should be very responsive: they do not hit a database or do anything but calculate regexes. They should never take longer than a 1 second (1,000 ms in the table above) unless there is a problem with the regex (or the host). Response times of less than 0.1 second (100 ms) are very good.
19
+
The engines should be very responsive: they do not hit a database or do anything but calculate regexes. They should never take longer than a second (1,000 ms in the table above) unless there is a problem with the regex (or the host). Response times of less than 0.1 second (100 ms) are very good.
0 commit comments