vignshwarar / AI-Employe

Create browser automation as if you were teaching a human using GPT-4 Vision.
GNU Affero General Public License v3.0
558 stars 51 forks source link

Failed to run the program locally #2

Open hargup opened 9 months ago

hargup commented 9 months ago

Getting following error on localhost:3000

Screenshot 2023-12-27 at 4 11 56 PM
vignshwarar commented 9 months ago

I just downloaded the repo and checked on my system, it is working. Could you please try these steps:

It appears to be a transpiling issue. Could you confirm the version of Next.js that is installed?

hargup commented 9 months ago

Okay

Current behavior:

Ideally, local development shouldn't require signups. Will see, if I feel motivated enough, might make a PR to make the local development entirely local.

vignshwarar commented 9 months ago

Ideally, local development shouldn't require signups

True, will try to make a PR

Seeing the sign-up page, but the signup is not happening

Could you please post the error message from the Chrome console or the server log?

hargup commented 9 months ago

Still not working, console error

vendor-a1b7b07f-59a0e76009756a5473ca.js:15 No storage available for session. We will not send any data.
(anonymous) @ vendor-a1b7b07f-59a0e76009756a5473ca.js:15
chrome-extension://invalid/:1 

       Failed to load resource: net::ERR_FAILED
vendor-a1b7b07f-59a0e76009756a5473ca.js:15 Shaka Player's internal Manifest structure is NOT covered by semantic versioning compatibility guarantees.  It may change at any time!  Please consider filing a feature request for whatever you use getManifest() for.
(anonymous) @ vendor-a1b7b07f-59a0e76009756a5473ca.js:15
vendor-9ebd23ae-97bc16e20d0d6d0d326d.js:1 WebSocket connection to 'wss://www.loom.com/graphql' failed: WebSocket is closed before the connection is established.
e.close @ vendor-9ebd23ae-97bc16e20d0d6d0d326d.js:1
identitytoolkit.googleapis.com/v1/projects?key=<key>:1 

       Failed to load resource: the server responded with a status of 400 ()
SignIn.tsx:97 FirebaseError: Firebase: Error (auth/configuration-not-found).
    at createErrorInternal (index-dd468b12.js:615:41)
    at _fail (index-dd468b12.js:586:11)
    at _performFetchWithErrorHandling (index-dd468b12.js:1051:17)
    at async _validateOrigin (index-dd468b12.js:9648:35)
www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=<key>&cb=1704665619402:1 

       Failed to load resource: the server responded with a status of 400 ()
Screenshot 2024-01-08 at 3 45 27 AM
hargup commented 9 months ago

using the latest commit here

vignshwarar commented 9 months ago

Thank you for the screenshot.

I created a branch without an auth: https://github.com/vignshwarar/AI-Employe/tree/remove_auth

This is a bit annoying, but it will make it easier.

Regarding your Firebase error, I think you have to turn on Google auth or Email auth option: https://stackoverflow.com/a/70738662/5947166

rothnic commented 9 months ago

@vignshwarar Trying to get this working locally as well. It is hard to tell which entries in the .env.development file are required or not when running in dev mode. In dev mode it still seems to require all these:

  apiKey: process.env.NEXT_PUBLIC_API_KEY,
  authDomain: process.env.NEXT_PUBLIC_AUTH_DOMAIN,
  projectId: process.env.NEXT_PUBLIC_PROJECT_ID,
  storageBucket: process.env.NEXT_PUBLIC_STORAGE_BUCKET,
  messagingSenderId: process.env.NEXT_PUBLIC_MESSAGING_SENDER_ID,
  appId: process.env.NEXT_PUBLIC_APP_ID,

From the readme and the discussion above, i got the impression they weren't required if using the open-source and dev mode. These all look firebase-like, but not sure exactly what they are mapped to.

image
rothnic commented 9 months ago

Well, I got it kind of working after doing the following:

I'm able to get into the app, but it just points me to installing the extension. I installed the extension from the build folder, but it doesn't seem to do anything. I also don't see any output when inspecting the service worker. Any ideas for getting the extension to work?

Edit: noticed an error in the console of the page (rather than the service worker):

share-modal.js:1 Uncaught TypeError: Cannot read properties of null (reading 'addEventListener')
    at share-modal.js:1:135
incrementCounter = void setTimeout((function() {
    document.querySelector(".tui-image-editor-main-container .tui-image-editor-download-btn").addEventListener("click", (t=>{
        t.preventDefault(),
        chrome.storage.local.get(["openTimes", "rateClicked"], (function(t) {
            let {openTimes: n, rateClicked: o} = t;
            n ? n += 1 : n = 1,
...

Having a hard time finding where that is coming from.

vignshwarar commented 9 months ago

The console error does not seem to be related to AI Employe, and the .tui-image-editor-main-container appears to be an image editor library.

2 things:

rothnic commented 9 months ago

Ah ok, yeah didn't look to see if it was another extension. Yeah, I built it and installed and it doesn't do anything when clicked.

vignshwarar commented 9 months ago

Could you please check the service worker logs after clicking the extension?

Reference image:

Screenshot 2024-01-18 at 5 00 35 PM
rothnic commented 9 months ago

Could you please check the service worker logs after clicking the extension?

Yeah that was what I first mentioned looking at. There isn't a single bit of activity I see associated with the service worker.

rothnic commented 9 months ago

Here is the extension if you want to try it: roth_extension_build.zip

vignshwarar commented 9 months ago

This is weird. Could you please open the sidebar and check whether the 'AI employee' icon is on the list or not? I will check your zip file when I get back to my system.

Reference image for sidebar:

Screenshot 2024-01-18 at 6 23 25 PM
rothnic commented 9 months ago

Interesting... so I have been using the Arc browser, which I haven't had any extension issues with. I see the icon and it does nothing in Arc, but tried it in Chrome and got it to pop up on the right on click. Sorry for the confusion. Didn't realize that could be a potential issue.

I did have a list of other things I had to work through and fix to get this working locally and I'll share that once I verify I get it working completely. Mainly it was working through errors related to dependencies that weren't managed explicitly in the readme.

Edit: Here is what I'm seeing at the moment

image
rothnic commented 9 months ago

Here is the output from the console for the service worker and ui.html, respectively:

image image