fix(tor-shield): Handle RPC expect unwrapping in circuits API
The RPC expect clause unwraps the response, so circuits data may be an array directly rather than an object with circuits property. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
0c54940010
commit
134736a0e9
@ -203,9 +203,13 @@ return baseclass.extend({
|
|||||||
callCircuits(),
|
callCircuits(),
|
||||||
callBandwidth()
|
callBandwidth()
|
||||||
]).then(function(results) {
|
]).then(function(results) {
|
||||||
|
// Handle RPC expect unwrapping - results[1] may be array or object
|
||||||
|
var circuitsData = results[1] || [];
|
||||||
|
var circuits = Array.isArray(circuitsData) ? circuitsData : (circuitsData.circuits || []);
|
||||||
|
|
||||||
return {
|
return {
|
||||||
status: results[0] || {},
|
status: results[0] || {},
|
||||||
circuits: (results[1] || {}).circuits || [],
|
circuits: circuits,
|
||||||
bandwidth: results[2] || {}
|
bandwidth: results[2] || {}
|
||||||
};
|
};
|
||||||
});
|
});
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user