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

In-framework deployment NeMo 2.0 nemo_export.py test #11749

Merged
merged 11 commits into from
Jan 10, 2025

Conversation

janekl
Copy link
Collaborator

@janekl janekl commented Jan 3, 2025

What does this PR do ?

Adding nemo_export.py --in-framework True [...] test in Github Actions. This also includes:

  • adding NeMo 2.0 support in this script
  • adding generate method for MegatronLLMDeployableNemo2 for parity with NeMo 1.0 generate for MegatronLLMDeployable
  • script to generate a Lambada-like dataset (5 samples) plus several minor bugfixes

Collection: NLP/ LLM

Usage

See edits in .github/workflows/cicd-main.yml.

GitHub Actions CI

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

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first 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)

@@ -141,7 +141,7 @@ def query_llm(
"object": "text_completion",
"created": int(time.time()),
"model": self.model_name,
"choices": [{"text": str(sentences)}],
"choices": [{"text": sentences}],
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Projecting NumPy array to string makes it hard to recover it later for further processing (note missing comma "," after the first element):

str(np.array([["a"], ["b"]])) == "[['a']\n ['b']]"

@janekl janekl force-pushed the jlasek/nemo_export_in_framework_test branch from 6010096 to be30d89 Compare January 8, 2025 12:54
@github-actions github-actions bot added the CI label Jan 8, 2025
@janekl janekl marked this pull request as ready for review January 8, 2025 15:38
Signed-off-by: Jan Lasek <[email protected]>
Dockerfile.ci Outdated
@@ -72,6 +72,7 @@ pip install --no-cache-dir --no-build-isolation --extra-index-url https://pypi.n
"llama-index==0.10.43" \
"onnxscript @ git+https://github.com/microsoft/onnxscript" \
-r tools/ctc_segmentation/requirements.txt \
-r requirements/requirements_infer.txt \
Copy link
Collaborator

Choose a reason for hiding this comment

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

Would it make sense to embed this into setup.py? What reasons may speak against it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good idea. I can offer sth like 398b0e7

from megatron.core.inference.common_inference_params import CommonInferenceParams
from pytorch_lightning.trainer.trainer import Trainer
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This Trainer was deprecated. Using it now leads to the error like:

ValueError: You selected an invalid strategy name: `strategy=<nemo.collections.nlp.parts.nlp_overrides.NLPDDPStrategy object at 0x7f7030512c20>`.
It must be either a string or an instance of `pytorch_lightning.strategies.Strategy`. Example choices: auto, ddp, ddp_spawn, deepspeed, ...
Find a complete list of options in our documentation at https://lightning.ai

@oyilmaz-nvidia oyilmaz-nvidia enabled auto-merge (squash) January 10, 2025 15:18
Copy link
Contributor

beep boop 🤖: 🙏 The following files have warnings. In case you are familiar with these, please try helping us to improve the code base.


Your code was analyzed with PyLint. The following annotations have been identified:

************* Module nemo.deploy.nlp.megatronllm_deployable
nemo/deploy/nlp/megatronllm_deployable.py:53:0: C0116: Missing function or method docstring (missing-function-docstring)
nemo/deploy/nlp/megatronllm_deployable.py:103:4: C0116: Missing function or method docstring (missing-function-docstring)
nemo/deploy/nlp/megatronllm_deployable.py:446:4: C0116: Missing function or method docstring (missing-function-docstring)
************* Module nemo.deploy.nlp.query_llm
nemo/deploy/nlp/query_llm.py:29:0: C0115: Missing class docstring (missing-class-docstring)
************* Module setup
setup.py:57:0: C0116: Missing function or method docstring (missing-function-docstring)
setup.py:131:0: C0115: Missing class docstring (missing-class-docstring)
setup.py:20:0: W0611: Unused import codecs (unused-import)

-----------------------------------
Your code has been rated at 9.83/10

Mitigation guide:

  • Add sensible and useful docstrings to functions and methods
  • For trivial methods like getter/setters, consider adding # pylint: disable=C0116 inside the function itself
  • To disable multiple functions/methods at once, put a # pylint: disable=C0116 before the first and a # pylint: enable=C0116 after the last.

By applying these rules, we reduce the occurance of this message in future.

Thank you for improving NeMo's documentation!

Copy link
Collaborator

@ko3n1g ko3n1g left a comment

Choose a reason for hiding this comment

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

Thanks a lot for moving requirements! One QQ and then we're good to go

requirements/requirements_infer.txt Show resolved Hide resolved
Copy link
Contributor

[🤖]: Hi @janekl 👋,

We wanted to let you know that a CICD pipeline for this PR just finished successfully

So it might be time to merge this PR or get some approvals

I'm just a bot so I'll leave it you what to do next.

//cc @pablo-garay @ko3n1g

@oyilmaz-nvidia oyilmaz-nvidia merged commit 1ab22d1 into main Jan 10, 2025
199 of 202 checks passed
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.

3 participants