this is when hitting "continue" in the initial pre...
# dev-frontendc
charles
02/12/2021, 6:07 PM
this is when hitting "continue" in the initial preferences page.
a
Artem Astapenko
02/12/2021, 6:14 PMHm I tested it based on Chris branch. Are you sure you have rebuilt everything?
Artem Astapenko
02/12/2021, 6:15 PMBecause I haven’t got any errors at all
c
charles
02/12/2021, 6:15 PM
I will try again!
a
Artem Astapenko
02/12/2021, 6:16 PMAlso as for workspace it was not changed. I actually did not change endpoints at all. Could you please also try to update node_modules in webapp. It’s possible that you are running old version of ‘rest-hooks’
c
charles
02/12/2021, 6:20 PM
rebuilt from scratch and still getting the same problem.
charles
02/12/2021, 6:20 PM
it looks like there were some changes to the workspace resthook in PR https://github.com/airbytehq/airbyte/pull/2047/files
charles
02/12/2021, 6:20 PM
in Workspace.ts
a
Artem Astapenko
02/12/2021, 6:20 PMSorry but I can’t check it right now as am I not at pc
c
charles
02/12/2021, 6:20 PM
ok
a
Artem Astapenko
02/12/2021, 6:21 PMAs for changes - yes, but I tested them together with those changes
Artem Astapenko
02/12/2021, 6:21 PMIf that’s urgent I suppose you can checkout to some commit as those changes was just small update. Hope that will help
Artem Astapenko
02/12/2021, 6:22 PM1 more thing are you running it as part of docker-compose or manually with npm run?
c
charles
02/12/2021, 6:22 PM
docker-compose.
charles
02/12/2021, 6:23 PM
reverting out the workspace.ts changes get me passed the first page successfully.
🤞 1
charles
02/12/2021, 6:24 PM
ah. now same thing for source definitions resource.
a
Artem Astapenko
02/12/2021, 6:26 PMCould you please try to disable compose and run it from webapp for with npm run start ( and maybe npm run install before that )? I am almost 100% sure that’s because you dont have last deps. I was working all day today based on those branch with no issues.
c
charles
02/12/2021, 6:32 PM
i will try.
a
Artem Astapenko
02/12/2021, 6:33 PMLet me know if you still have a problem and that’s urgent.
c
charles
02/12/2021, 6:38 PM
kk. @Chris (deprecated profile) tried it just now and said it was working, so i will try to figure out if this is something with my environment. going to start by nuking all of my node modules first. then will do what you suggested if that still doesn't work.
charles
02/12/2021, 7:25 PM
well still not sure what's going on. reverting the last commit on the PR seems to get rid of the issue, but since there is other business logic changes in there, i don't think that's safe to do. seems to work well for chris, so maybe it's just a problem for my machine?
charles
02/12/2021, 7:26 PM
things i tried:
• remove all node modules and starting from scratch (making sure all caches were busted)
• reisntalling node
• running the webapp using npm run start
charles
02/12/2021, 7:26 PM
i will keep trying to debug what is going on later, but got to switch gears for now.
charles
02/12/2021, 7:27 PM
as it seems to be just my machine, i think it's fair that i just try to debug it. if i can't figure it out today i will ask for help on monday.
charles
02/13/2021, 12:52 AM
i dunno. just spent some more time on this and i'm stuck. maybe we can take a look together on monday during the sync.
charles
02/13/2021, 12:52 AM
weird stuff.