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.

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

Dependabot is not creating PRs and there are no logs #10096

Closed
1 task done
cahrens opened this issue Jun 27, 2024 · 6 comments
Closed
1 task done

Dependabot is not creating PRs and there are no logs #10096

cahrens opened this issue Jun 27, 2024 · 6 comments
Labels
L: java:gradle Maven packages via Gradle T: bug 🐞 Something isn't working

Comments

@cahrens
Copy link

cahrens commented Jun 27, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Package ecosystem

Gradle

Package manager version

No response

Language version

Java 17

Manifest location and content before the Dependabot update

No response

dependabot.yml content

https://github.com/DataBiosphere/terra-resource-buffer/blob/master/.github/dependabot.yml

Updated dependency

No response

What you expected to see, versus what you actually saw

I am enabling dependabot on the repository, using the same dependabot.yml file that works for us in other repositories. No PRs have been opened, and I see the following message in Insights, but the logs are empty.

Version update 848295178
Errored with the message "Dependabot encountered an unknown error"
No PRs affected 9 minutes ago view logs

Dependabot encountered an unknown error
Dependabot failed to update your dependencies because an unexpected error occurred. See the logs for more details. (But there aren't any)

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response

@cahrens cahrens added the T: bug 🐞 Something isn't working label Jun 27, 2024
@github-actions github-actions bot added L: git:submodules Git submodules L: go:modules Golang modules labels Jun 27, 2024
@jakecoffman jakecoffman added L: java:gradle Maven packages via Gradle and removed L: go:modules Golang modules L: git:submodules Git submodules labels Jun 27, 2024
@rujutaghanekar
Copy link

I think I am experiencing similar issue. In my case, I am using the gomod environment.
And logs exist mentioning PR creation:

updater | 2024/06/28 04:46:06 INFO <job_848580854> Creating a pull request for 'dependencies'
...
updater | 2024/06/28 04:54:06 INFO <job_848580854> Finished job processing
updater | 2024/06/28 04:54:06 INFO Results:
updater | +------------------------------------------------------------------------------------------------------------------------------------+
updater | |                                                Changes to Dependabot Pull Requests                                                 |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | | created | github.com/**** ( from 1.56.1 to 1.57.0 ), github.com/aws/aws-sdk-go-v2 ( from 1.26.1 to 1.30... |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+

However, no PR is actually created. It was working fine till yesterday.
Dependabot configuration:

version: 2
updates:
- package-ecosystem: "gomod"
  directory: "/"
  schedule:
    interval: "daily"
    time: "09:00"
    timezone: "Asia/Kolkata"
  groups:
    dependencies:
      patterns:
        - "*"
  commit-message:
    prefix: "gomod"
    include: "scope"
  labels:
  - "dependencies"

@cahrens
Copy link
Author

cahrens commented Jun 28, 2024

I think I am experiencing similar issue. In my case, I am using the gomod environment. And logs exist mentioning PR creation:

updater | 2024/06/28 04:46:06 INFO <job_848580854> Creating a pull request for 'dependencies'
...
updater | 2024/06/28 04:54:06 INFO <job_848580854> Finished job processing
updater | 2024/06/28 04:54:06 INFO Results:
updater | +------------------------------------------------------------------------------------------------------------------------------------+
updater | |                                                Changes to Dependabot Pull Requests                                                 |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | | created | github.com/**** ( from 1.56.1 to 1.57.0 ), github.com/aws/aws-sdk-go-v2 ( from 1.26.1 to 1.30... |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+

However, no PR is actually created. It was working fine till yesterday. Dependabot configuration:

version: 2
updates:
- package-ecosystem: "gomod"
  directory: "/"
  schedule:
    interval: "daily"
    time: "09:00"
    timezone: "Asia/Kolkata"
  groups:
    dependencies:
      patterns:
        - "*"
  commit-message:
    prefix: "gomod"
    include: "scope"
  labels:
  - "dependencies"

This probably isn't the same issue, as I don't even get any logs (and I'm using Java/gradle).

I am wondering if possibly it could be related to the fact that I didn't have admin rights on the repo when I submitted the dependabot.yml file? I have wondered if I should try deleting it and recreating it, now that I am an admin.

@Nishnha
Copy link
Member

Nishnha commented Jun 28, 2024

Hi @cahrens can you update the target branch to point to an existing branch or create a develop branch? https://github.com/DataBiosphere/terra-resource-buffer/blob/master/.github/dependabot.yml#L17

@cahrens
Copy link
Author

cahrens commented Jun 28, 2024

@cahrens
Copy link
Author

cahrens commented Jun 28, 2024

@Nishnha ooops, I now see what you mean! Yes, let me fix that.

@cahrens
Copy link
Author

cahrens commented Jun 28, 2024

Thanks, that was the issue! Unfortunately we are inconsistent about our main branch names across our repositories, and I didn't notice that. Thank you for the help!

@cahrens cahrens closed this as completed Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: java:gradle Maven packages via Gradle T: bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants