Closed ydshieh closed 11 months ago
I'd like to work on this; I'll start with YOLOS and open a PR :)
I'll take on Whisper!
I'll work on Beit!
FYI Bart #19524 and Albert #19541 are already done :)
I'll take on GPT2 next!
I can take imageGPT
i'll work on yoso
I'll work on
and open up PR soon :)
Also will raise for Transformer-XL !
I'll work on bloom
I'll work on ctrl
Hi @ydshieh, I am new here and want to contribute to this issue. Can you please help me to find the remaining files? Thanks,
Hi @ydshieh, I am new here and want to contribute to this issue. Can you please help me to find the remaining files? Thanks,
Hi @SD-13 You can check the latest file https://github.com/IzicTemi/transformers/blob/main/utils/documentation_tests.txt
Any configuration file that is not on that list (on main
branch) and [not claimed here yet, no PR opened yet] are all welcome :-)
Hey @ydshieh, could I fix multiple models in a single PR, or do I have to open a single PR for each fix?
I will be taking blenderbots as well
Hey @ydshieh, could I fix multiple models in a single PR, or do I have to open a single PR for each fix?
2 or 3 might be good. But don't take more in a single PR - the sprint is for everyone to contribute, so leave some to others :-)
Hi @ydshieh, I am new here and want to contribute to this issue. Can you please help me to find the remaining files? Thanks,
Hi @SD-13 You can check the latest file https://github.com/IzicTemi/transformers/blob/main/utils/documentation_tests.txt
Any configuration file that is not on that list (on
main
branch) and [not claimed here yet, no PR opened yet] are all welcome :-)
Thanks @ydshieh , that was helpful. I can take vision_text_dual_encoder.py
Hey @ydshieh, I am getting this error
can you please help me to understand the reason and fix it? Thanks,
@SD-13 Could you open a PR (even if it is not complete yet), and post the command you run and the complete error message in that PR? Using image is not very convivence to search and debug π
@SD-13 Could you open a PR (even if it is not complete yet), and post the command you run and the complete error message in that PR? Using image is not very convivence to search and debug pray
Yeah true. I created this PR and let's leave those errors since all checks are passing. Thanks,
I will also take time_series_transformer.py
, vision_encoder_decoder.py
, and trajectory_transformer.py
. Thanks,
took up blenderbot_small too.
I'll take on
and will open up PR :)
Hi @ydshieh , I want to contribute to this issue. Can you please help me to find the remaining files?
Hi @ydshieh , I want to contribute to this issue. Can you please help me to find the remaining files?
Hey @SaurabhBudhwani26 , please check this. I hope it will be helpful. Thanks,
I'll work on configuration_visual_bert.py
I will work on:
big_bird
bigbird_pegasus
I will work on
configuration_xlm_roberta.py
configuration_xlm_roberta_xl.py
Can I work on this? @ydshieh
I will work on flava
Now, I will work on Longformer
, Pegasus
and VisualBERT
.
@AShreyam You didn't open a PR, and you merged your branch into your own main branch.
I am really sorry for the inconvenience.
Here is the actual pull request. Thank You :)
Work on configuration_big_bird.py
I'll take on
and open up PR :)
I'll take on CodeGen
I'll take on Data2Vec ones :)
I'll take on conditional_detr
I'll take on realm
I'll take on convbert
I'll take on CLIP =)
I'll take XLNet
I can take the wav2vec2 ones if that is ok, is someone else working on those?
I'll take XLM
I'll take cvt
I'll take pegasus
and pegasus_x
I will take fnet
and flava
.
@ydshieh Added config files for convnext
Oh it will close this ...?
The previous merged PRs didn't close this issue. Strange!
This sprint is similar to #16292 - but for model configuration files, i.e.
configuration_[model_name].py
. For example,src/transformers/models/bert/configuration_bert.py
The expected changes
The changes we expect could be find #19485:
(with random weights)
in the comment before model initialization lineconfiguration_[model_name].py
toutils/documentation_tests.txt
(respecting the order)Please do step 3. only after Running the doctest and make sure all tests pass (see below) π
How to run doctests
Suppose you are working on
src/transformers/models/bert/configuration_bert.py
. The steps to run the test are:Stage your changes
Prepare the files to be tested
or if you prefer to be more specific
This will change some files (doc-testing needs to add additional lines that we don't include in the doc source files).
to clean up the changes in step 1.
Ready (or not)?
If all tests pass, you can commit, push and open a PR π₯ π , otherwise iterate the above steps π― !