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

Handle case where num_query_groups is set to null for LoRA config setup #9075

Merged
merged 1 commit into from
May 1, 2024

Conversation

vysarge
Copy link
Contributor

@vysarge vysarge commented May 1, 2024

What does this PR do ?

Currently, LoRA setup uses either the num_query_groups setting (if set) or the num_attention_heads setting, if not. However, if num_query_groups is set explicitly to null, this line evaluates to None instead of the num_attention_heads value, resulting in TypeError: unsupported operand type(s) for *: 'int' and 'NoneType'. This tiny change just adds an additional check to account for this situation.

Collection: nlp

Changelog

  • Adds an additional check to LoRA config setup, setting num_query_groups to num_attention_heads if None.

Usage

  • You can potentially add a usage example below
# Add a code snippet demonstrating how to use this 

Jenkins CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

There's no need to comment jenkins on the PR to trigger Jenkins CI.
The GitHub Actions CI will run automatically when the PR is opened.
To run CI on an untrusted fork, a NeMo user with write access must click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests?
  • Did you add or update any necessary documentation?
  • Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
    • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

  • Related to # (issue)

Signed-off-by: Valerie Sarge <vsarge@nvidia.com>
@vysarge vysarge force-pushed the vsarge/lora_num_query_groups branch from 4b7c71e to 6fc4033 Compare May 1, 2024 05:28
@github-actions github-actions bot added the NLP label May 1, 2024
@vysarge
Copy link
Contributor Author

vysarge commented May 1, 2024

@cuichenx / @ericharper, can you review this one? Thanks!

@arendu arendu self-requested a review May 1, 2024 06:13
Copy link
Collaborator

@arendu arendu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM!

@ericharper
Copy link
Collaborator

Merging this because it's only failing on a problematic test which is being commented out in #9085

@ericharper ericharper merged commit 9e2325d into NVIDIA:main May 1, 2024
130 of 131 checks passed
suiyoubi pushed a commit that referenced this pull request May 2, 2024
…up (#9075)

Signed-off-by: Valerie Sarge <vsarge@nvidia.com>
Signed-off-by: Ao Tang <aot@nvidia.com>
@vysarge vysarge deleted the vsarge/lora_num_query_groups branch May 21, 2024 23:39
rohitrango pushed a commit to rohitrango/NeMo that referenced this pull request Jun 25, 2024
…up (NVIDIA#9075)

Signed-off-by: Valerie Sarge <vsarge@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants