Neil Crow
Neil Crow
The problem is that the Oracle jdbc driver uses varying url formats depending on how the database has been set up. Two variants of the thin driver use the following...
Your jdbc url format looks ok. The error indicates that the jvm can't find the oracle jdbc class files in the classpath.
You should ensure that the oracle jar file is available on the classpath.
That gives a different error: ✔ Merge done! git diff --name-only --diff-filter=U package.json force .yo-rc-global.json force .yo-rc.json Installing dependencies, please wait... info Removing the node_modules directory info Removing C:\org\APP-2.0.2\apptmp2\node_modules info...
As @cdlliuy says, this can be resolved by rolling coredns back from v1.10.1 to v1.10.0 here's the patch command: ```shell kubectl patch deployment coredns -n kube-system -p '{"spec":{"template":{"spec":{"containers":[{"name":"coredns","image":"registry.k8s.io/coredns/coredns:v1.10.0"}]}}}}' ```
I'm running it from VS Code using Edge (Web) as the target device
The solution from @compadrejunior worked for a new installation that was failing for my colleague on Win-11 using docker v4.28.0 However it's notable that I don't encounter the same issue...
@rphlmr thanks that looks like the dependency issue is fixed, however there is a new error when running the remix.init script. ```shell > npx create-remix --template rphlmr/supa-fly-stack remix v2.4.0 💿...
if I run npx remix init inside the app directory I see this: ```shell > npx remix init 🚀 Making something cool with this template ... Error: 🚨 Oops, remix.init...
I have read the CLA Document and I hereby sign the CLA