dvankley / firefly-plaid-connector-2

Connector to pull Plaid financial data into the Firefly finance tool
GNU General Public License v3.0
98 stars 15 forks source link

Parameter 0 of constructor in net.djvk.fireflyPlaidConnector2.FireflyPlaidConnector2Application required a bean of type 'net.djvk.fireflyPlaidConnector2.sync.Runner' that could not be found. #40

Closed markwoodward86 closed 1 year ago

markwoodward86 commented 1 year ago

I'm sorry, ive tried investigating this for a while now and i cant seem to get my polling docker file to run. This is the log. Hopefully this is something simple that I am overlooking on my part.

firefly-plaid-connector-2-app-1  | 2023-11-15T01:24:03.020Z  INFO 1 --- [           main] .d.f.FireflyPlaidConnector2ApplicationKt : Starting FireflyPlaidConnector2ApplicationKt v1.0.8 using Java 17.0.7 with PID 1 (/workspace/BOOT-INF/classes started by cnb in /workspace)
firefly-plaid-connector-2-app-1  | 2023-11-15T01:24:03.029Z  INFO 1 --- [           main] .d.f.FireflyPlaidConnector2ApplicationKt : No active profile set, falling back to 1 default profile: "default"
firefly-plaid-connector-2-app-1  | 2023-11-15T01:24:05.144Z  WARN 1 --- [           main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'fireflyPlaidConnector2Application': Unsatisfied dependency expressed through constructor parameter 0: No qualifying bean of type 'net.djvk.fireflyPlaidConnector2.sync.Runner' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
firefly-plaid-connector-2-app-1  | 2023-11-15T01:24:05.196Z  INFO 1 --- [           main] .s.b.a.l.ConditionEvaluationReportLogger : 
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
firefly-plaid-connector-2-app-1  | 2023-11-15T01:24:05.229Z ERROR 1 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   : 
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | ***************************
firefly-plaid-connector-2-app-1  | APPLICATION FAILED TO START
firefly-plaid-connector-2-app-1  | ***************************
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | Description:
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | Parameter 0 of constructor in net.djvk.fireflyPlaidConnector2.FireflyPlaidConnector2Application required a bean of type 'net.djvk.fireflyPlaidConnector2.sync.Runner' that could not be found.
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | Action:
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | Consider defining a bean of type 'net.djvk.fireflyPlaidConnector2.sync.Runner' in your configuration.
firefly-plaid-connector-2-app-1  | 
firefly-plaid-connector-2-app-1  | 
markwoodward86 commented 1 year ago

Closing this out as I was able to figure it out after a nights rest away from my computer!

smoores-dev commented 8 months ago

@markwoodward86 would you be willing to share what you figured out here? I just ran into the same issue, trying to run the batch process for the first time

markwoodward86 commented 8 months ago

Yeesh, this was a while back. I'll try and rack my brain and let you know if I am able to recall. I should have known better and documented my findings.

dvankley commented 8 months ago

@smoores-dev please feel free to open a new issue with your full stack trace (although you probably want to redact your access tokens) and I can take a look. The trace posted here only has the top level error, which is a very generic "application failed to start" and doesn't dig into why it failed to start.

Also if you're feeling feisty you can do what I do and trace the exception chain down to the lowest "caused by," which in this case I would guess is probably a missing parameter in the configuration file.

markwoodward86 commented 8 months ago

I am pretty sure it was a missing parameter in the config that I traced it back to when i originally got this too so that checks out.

smoores-dev commented 8 months ago

Hey, thanks folks! Yeah this was a bit silly, I had been mounting my application.yaml to the wrong path in the container. It's been a while since I've worked with the JVM; always takes me a minute to remember to look at the Caused by!