```[Metrics] Warning: no metrics will be recorded....
# orm-help
d
Copy code
[Metrics] Warning: no metrics will be recorded.
java.lang.RuntimeException: ProjectHelper: Could not resolve project with id: graphql$default
        at scala.sys.package$.error(package.scala:27)
        at com.prisma.subscriptions.helpers.ProjectHelper$.$anonfun$resolveProject$1(ProjectHelper.scala:13)
        at scala.util.Success.$anonfun$map$1(Try.scala:251)
        at scala.util.Success.map(Try.scala:209)
        at scala.concurrent.Future.$anonfun$map$1(Future.scala:287)
        at scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:29)
        at scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:29)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
        at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
        at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
        at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:81)
        at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:91)
        at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:43)
        at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Anyone know what this means ? I'm guessing it's something I may have initiliazed wrong but I just can't seem to find what.
n
you are tring to access the route
<http://your-server.com/graphql|your-server.com/graphql>
, but there is no
graphql
project with
default
stage deployed to your server.
run
prisma info
to find out the service endpoint
d
Thanks, finally got around to actually coding my project 🙂. Looks like I'll be using prisma for most of my database needs. Hoping to see more connectors soon, it would make life easier in connecting client datasources. Particularly interested in mongodb for it's timeseries pattern which could come in handy in industrial projects.
💯 1