Hi there. Do I have too many source freshness chec...
# community-support
a
Hi there. Do I have too many source freshness checks for elementary to handle?! Also why does --project-dir=. need passing when the cli help docs say that it defaults to current directory?
@Noa Dagan (or anyone else from elementary team), please can you help with this? is there a known workaround? is the bug acknowledged? is there an eta for a fix? also, curious re. the help message / mandatory-ness of the --project-dir param, thanks.
n
Hey @Adam Cunnington I’m taking a look Can you please share you
edr.log
and
dbt.log
if you have them Regarding the project dir - what happens when you don’t have the project_dir flag? Do you get a different error?
a
@Noa Dagan FYI that there is a bug on your issue tracker about this already; https://github.com/elementary-data/elementary/issues/1353 Clean dbt.log and edr.log are attached.
--project-dir
is just a regular mandatory CI parameter but the description suggests it shouldn't be - and indeed, given one will almost always pass
.
to it, it shouldn't be manadatory. See screenshot:
n
Ok so the
--project-dir
being mandatory is only relevant to the
upload-source-freshness
command, you’re saying “the description suggests it shouldn’t be” - though in the docs you can see it is mentioned that it’s mandatory (shared a print screen) About the overflow - I asked for your logs to make sure it’s the same known issue and not anything else, I’ll go over them and get back to you (unless you’re sure it’s the same issue? if so - are you just asking for a workaround?)
a
@Noa Dagan I don't understand your response. I have screenshot the help message for the upload-source-freshness command where it says it defaults to current working directory. I'm not disputing that it is mandatory, I can see that it is but: • the description says it is not • it plainly shouldn't be because of the fact that everyone just passes
.
to it and the description even says this is the default
I also don't understand what you are saying about the logs. You asked for dbt.log and edr.log - both of which I attached. What more did I give you?
I'm asking: • For clarification that the issue is known - and whether there is an ETA for a fix • What the workaround is in the meantime • For the incorrect help text / mandatory param to be fixed
n
I just meant I want to go over the logs to make sure 🙂 But you seems certain enough so: • The issue, as you sent here, is known. • There’s a fix on the way - https://github.com/elementary-data/elementary/pull/1379/files ◦ It’s already merged and will be out in the next version upgrade. ◦ As of a workaround, I don’t have anything out of the box right now to give you sorry • Regarding the incorrect help text - can you share where you saw this incorrect help text? So we can fix it if necessary. Because as I sent in the previous message you can see the docs are mentioning this flag is mandatory when running
upload-source-freshness
a
@Noa Dagan thanks for answers. To your last question, it was in my screenshot. Again:
I know it's explained as mandatory in the docs but CLI helptext is much more usable as a reference for this info than online docs. So i think important that it is consistent/correct.
n
Got you thanks for bringing that up. We’ll see how we can explain it better in the cli as well Actually best would be if you could open an issue here about it, asking to change it and we’ll get to it 👍
s
a
Ok, will do. I'll also suggest that this should not just be a docs fix but a behaviour change
I still don't understand why this parameter is mandatory.
P.s. for posterity on this thread - the fix for upload-source-freshness is live in 0.14.0