Assistant Windows application, the latest version has two errors that occur:
Uncaught SyntaxError: missing ) after argument list index.html:1
Uncaught TypeError: Cannot read properties of undefined (reading ‘name’)
at remoteRunPackage (renderer.ts:103:30)
at :1:1
so at line 103 it is trying to parse the package you want to run.
There is no check if the package was found ( sorry, my bad, that needs to be added ) but the error comes from the package not existing or the agent does not have permission to see it …
My guess is, you are trying to run a package, that the agent does not have permission to ?
Yes, I’m trying to run package on assistant by scheduling it in OpenCore, even if I can’t see it in my Assistant.
Not sure why packages are not shown in assistant. I’m trying with python and nodejs package examples that you have. My assistant has python, nodejs, chromium shown in the assistant app.
It should show your username in the UI. Is that the correct user? Does that user have access to the packages?
In OpenCore, if you go to Database → Agents → Edit the agent, what languages did it report to OpenCore it supports?
The list of packages in the assistant UI is based on packages it has access to and is a supported language. It detects languages by calling whereis for the command-line CLI used for each language, i.e., they need to be in the PATH environment variable.
Yes, with my Username in the UI. Don’t see packages, but not sure about access.
Here is from the Database:
But no packages visible in the application Assistant!
Is there a way to share/give access to packages manually to the Agents?
If you click clear cache, it should delete all packages and temp files and try getting a fresh list of packages.
Also, keep in mind, you can change who the agent is running as from the agent page, please ensure user you see in the agent matches the “run as” field on the agent. Also please validate that this user can actually see the packages ( sign in to opencore as that user and look under agent->packages )
Also, please keep in mind, nodejs 16 is not supported anymore, you need to be using 18 or higher, preferably 20 or 22
Also, please make sure persist_user_impersonation under config, has the default value of false .. if you have ever used impersonation, on a user, used by an agent, that can have fatal consequences, so if this value is, or have ever been, enabled, please ensure “impersonating” field is cleared or deleted from the user’s object on the database.
Answers:
Running user is ok, it’s the same for both (Agent and see Packages).
Will install newer version of nodejs.
I haven’t found the persist_user_impersonation. Where should be this value. Could not find the config.
I think I found the issue:
One of the packages that I have published has in it’s description " ‘some word’ " which cause error when listing packages. So, I removed it (single quotation mark) from the package description and now I can see all the packages.
Also, I had some error with Conda version, now updated to the latest 25.5.1
Also, typo in OpenCore app in Agents details: ‘Runas’ instead of ‘Run as:’.
Best regards, and thanks for help!
Only question here is:
When I try to run packages to the assistant through OpenCore ‘Run Package’ i got this error info:
‘Error while running
No instances available’
Which means I am not able to run it through OpenCore.
Can you post a screenshot of that error ?
If i search OpenCore NodeAgent and Assistant for either Error while running or No instances available i get no hit’s … that feels a little odd. If something WAS started and the error came from a process you should still see something like Child process started as pid # so everything point’s to an error before that
Here is the screenshot with running package:
Here is the screenshot without running any package in the background.
This is the Assistant User.
I just select the package and click Run Package. Only for the Assistant or NodeAgent user.
That is odd .
If you run the package from inside the assistent, does it show up inside the webpage ?
Can you open the developer tools and see if you get any errors ? maybe more details
If you run the package from inside the assistent, does it show up inside the webpage ?
From inside the assistant it does not show in the webpage.
Can you open the developer tools and see if you get any errors ? maybe more details
Errors:
1.
command error BLAHBLAH {message: 'no such type: openiap.queueeventreply', code: 0, stack: 'Error: no such type: openiap.queueeventreply\n a…jections (node:internal/process/task_queues:95:5)'}code: 0message: "no such type: openiap.queueeventreply"stack: "Error: no such type: openiap.queueeventreply\n at Root.lookupType (/app/node_modules/protobufjs/src/namespace.js:382:15)\n at protowrap.pack (/app/node_modules/@openiap/nodeapi/lib/protowrap.js:164:39)\n at flowclient.onMessage (file:///app/dist/WebServer.js:881:40)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()__proto__: (...)get __proto__: ƒ __proto__()set __proto__: ƒ __proto__() reply {command: 'error', rid: 'o4uknxflo', data: {…}}
A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.
1 resource
Violating node
The label's for attribute doesn't match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
To fix this issue, make sure the label's for attribute references the correct id of a form field.
2 resources
Violating node
Violating node
https://raw.githubusercontent.com/Bon-Appetit/porn-domains/refs/heads/master/block.txt 404 (Not Found)
68403a0…:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Version of selfhosted OpenCore: 1.5.12.9 (4981e0a3)
but where is this error from ? can you show a screenshot ?
I don’t see any others than “queueeventreply,” and this was fixed a while ago. However, you write that you are using the latest build we have (1.5.12.9), so that confuses me a little.
(The other errors seem to come from your browser extensions and are not related to OpenCore.)
Either way, that “error” is not a real error. Basically, some clients send a reply back when they receive a “queueevent,” and they were not supposed to. So the “fix” was to just “eat” the error and ignore it.
But this also tells me there is some communication between OpenCore and the assistant.
I guess we need to figure out what is wrong with the assistant on your machine.
You told me earlier in the thread you found a solution to make packages appear in the assistant, but now you are saying nothing shows up in the assistant… so did it break completely now? If so, what changed?
Yes, in the assistant now i can see packages and run it.
What i thought is that running package from Assistant i do not get the popup error show in Webpage like when running package from Webpage.
Sure, we can check the assistant. Maybe, i can delete assistant and then install it again.
I have downloaded again Assistant, and get the error when trying to run the package from inside Webpage ‘Agent’:
So when you click a package name INSIDE the assistant, you get the same error Error while running No instances available ?
No, only when I click from Webpage.
could you try using app.openiap.io instead … and see if that makes any difference ?
