Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] package grayed out #129

Open
1 of 4 tasks
nirera opened this issue Dec 23, 2024 · 6 comments
Open
1 of 4 tasks

[Bug] package grayed out #129

nirera opened this issue Dec 23, 2024 · 6 comments
Labels
type:bug Something is broken or incorrect

Comments

@nirera
Copy link

nirera commented Dec 23, 2024 •
edited by fivetran-joemarkiewicz
Loading

Is there an existing issue for this?

  • I have searched the existing issues

Describe the issue

We are using dbt Cloud, and after updating to the latest package version, we encountered some dependency issues. We resolved these issues by removing all dependency packages from the packages.yml file. After doing this, we successfully ran dbt deps . However, the package library is now grayed out. While the files are visible when clicked, the jobs that rely on these packages are failing. we already tried , dbt clean and and deleting partial_parse.msgpack

Relevant error log or model output

No response

Expected behavior

non grayed working package...

Possible solution

No response

dbt Project configurations

# Name your project! Project names should contain only lowercase characters
# and underscores. A good package name should reflect your organization's
# name or the intended use of these models
name: 'walnut_dbt'
version: '1.0.0'
config-version: 2

# This setting configures which "profile" dbt uses for this project.
profile: 'walnut_dbt'

# These configurations specify where dbt should look for different types of files.
# The `model-paths` config, for example, states that models in this project can be
# found in the "models/" directory. You probably won't need to change these!
model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_packages"


# Configuring models
# Full documentation: https://docs.getdbt.com/docs/configuring-models

# In this example config, we tell dbt to build all models in the example/ directory
# as tables. These settings can be overridden in the individual model files
# using the `{{ config(...) }}` macro.
models:
  walnut_dbt:
    # Config indicated by + and applies to all files under models/example/
    example:
      +materialized: view

  ad_reporting:
    +schema: dbt_ad_reporting

  facebook_ads:
    +schema: dbt_facebook_ads
  facebook_ads_source:
    +schema: dbt_facebook_ads_source
  
  google_ads:
    +schema: dbt_google_ads
  google_ads_source:
    +schema: dbt_google_ads_source

  linkedin:
    +schema: dbt_linkedin
  linkedin_source:
    +schema: dbt_linkedin_source

  hubspot:
    +schema: dbt_hubspot
  hubspot_source:
    +schema: dbt_hubspot_source

  salesforce:
    +schema: dbt_salesforce
  salesforce_source:
    +schema: dbt_salesforce_source
  
  zendesk:
    +schema: dbt_zendesk

vars:

  ad_reporting__amazon_ads_enabled: False # by default this is assumed to be True
  ad_reporting__apple_search_ads_enabled: False # by default this is assumed to be True
  ad_reporting__pinterest_ads_enabled: False # by default this is assumed to be True
  ad_reporting__twitter_ads_enabled: False # by default this is assumed to be True
  ad_reporting__snapchat_ads_enabled: False # by default this is assumed to be True
  ad_reporting__tiktok_ads_enabled: False # by default this is assumed to be True
  ad_reporting__reddit_ads_enabled: False 
  hubspot_email_event_enabled: false   # Disables all email_event models and functionality

  surrogate_key_treat_nulls_as_empty_strings: True

Package versions

packages:
  # - package: dbt-labs/dbt_utils
  #   version: 1.1.1
 # - package: fivetran/hubspot
 #   version: [">=0.20.0", "<0.21.0"]
 # - package: fivetran/google_ads
 #   version: [">=0.11.0", "<0.12.0"]
 # - package: fivetran/salesforce
 #   version: [">=1.1.0", "<1.2.0"]
  # - package: fivetran/facebook_ads
  #   version: [">=0.5.0", "<0.6.0"]
  # - package: fivetran/linkedin
  #   version: [">=0.5.0", "<0.6.0"]
  - package: fivetran/ad_reporting
    version: [">=1.11.0", "<1.12.0"]
  #- package: fivetran/zendesk
  #  version: [">=0.19.0", "<0.20.0"]

What database are you using dbt with?

redshift

How are you running this dbt package?

dbt Cloud™

dbt Version

latest

Additional Context

No response

Are you willing to open a PR to help address this issue?

  • Yes.
  • Yes, but I will need assistance.
  • No.
@nirera nirera added the type:bug Something is broken or incorrect label Dec 23, 2024
@nirera nirera changed the title [Bug] <title> package grayed out [Bug] package grayed out Dec 23, 2024
@fivetran-joemarkiewicz
Copy link
Contributor

Thanks for opening this issue @nirera and sorry to see you're running into some issues after upgrading.

Unfortunately, I'm not as familiar with how dbt Cloud handles the package library. Can you provide a screenshot of what you mean by "greyed out" in this context. Also, it make sense that some of the jobs are now failing after commenting out all the package dependencies with the exception of Ad Reporting. Looking at your packages.yml, you only need to remove the Google Ads, LinkedIn Ads, and Facebook Ads dependencies since they're already included in the Ad Reporting dependency. This likely is what was causing the issue you were seeing previously.

For example, see the below code link for the Facebook Ads, Google Ads, and LinkedIn Ads versions in the most recent Ad Reporting package udpate.

dbt_ad_reporting/packages.yml

Lines 8 to 14 in e3cc112

- package: fivetran/facebook_ads
version: [">=0.8.0", "<0.9.0"]
- package: fivetran/google_ads
version: [">=0.11.0", "<0.12.0"]
- package: fivetran/linkedin
version: [">=0.10.0", "<0.11.0"]

Compared to the versions you had previously (per this issue description), I can see that Facebook Ads and LinkedIn Ads are out of sync with the versions required by the package. This likely was the cause of your initial error.

Would you be able to remove the Facebook Ads, Google Ads, and LinkedIn Ads packages from your packages.yml (Ad Reporting will install the proper versions for you) and then comment back in the other packages. I believe this should address your issue.

@nirera
Copy link
Author

nirera commented Dec 23, 2024 via email

@fivetran-joemarkiewicz
Copy link
Contributor

@nirera unfortunately I'm unable to see the images you shared. Would you be able to elaborate on what the issue is that you're seeing?

@nirera
Copy link
Author

nirera commented Dec 24, 2024 via email

@fivetran-joemarkiewicz
Copy link
Contributor

@nirera I unfortunately cannot see these attachments. It may be that they are not sending properly via email. Would you be able to attach them directly through GitHub so we may better see and understand this issue.

@fivetran-joemarkiewicz
Copy link
Contributor

@nirera following up if you're able to share the screenshots directly through GitHub or if this is still an issue on your end?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:bug Something is broken or incorrect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fivetran-joemarkiewicz @nirera