-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
added unflatten (incomplete) #25975
added unflatten (incomplete) #25975
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Conventional Commit PR Title
In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:
- docs: correct typo in README
- feat: implement dark mode"
- fix: correct remove button behavior
Linting Errors
- Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
- No subject found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congrats on making your first Pull Request and thanks for supporting Ivy! 🎉
Join the conversation in our Discord
Here are some notes to understand our tests:
- We have merged all the tests in one file called `display_test_results` job. 👀 It contains the following two sections:
- Combined Test Results: This shows the results of all the ivy tests that ran on the PR. ✔️
- New Failures Introduced: This lists the tests that fails on this PR.
Please make sure they are passing. 💪
Keep in mind that we will assign an engineer for this task and they will look at it based on the workload that they have, kindly be patient 😄.
🤔 Seems like you have pushed a wrong commit for docs submodule |
@HaiderSultanArc I only modified three files but I see now that the commit modified also |
I think you can check what commit docs/demos submodule is on main branch. Then go to demos and checkout to that commit and then commit that 🤔 cd docs/demos
git checkout <COMMIT_HASH_ON_MAIN>
cd ../../
git add -A
git commit -m "update: demos submodule"
git push |
@HaiderSultanArc I just did that, I hope things are good now. |
Yep it's good now. There are some failing tests. I think you need to implement backend implementations as well right? 🤔 |
@HaiderSultanArc thank you for always replying, I don't think I should implement the backend implementation as well (The task is called: Add Instance methods to Pytorch Frontend) I guess now I should implement the tests, can you please guide on where I can learn how to do that? |
@HaoES If you are working on a frontend task and the backend is not implemented then you will have to implement that before the frontend 😄 |
@HaiderSultanArc the task I am working on is Add Instance Methods to PyTorch Frontend so it's only concerned with Pytorch (the only framework I know). |
Hey @HaoES you can use the |
@HaiderSultanArc I am very thankful for your constant feedback, I totally understand you, but what I understood is that my task focuses only on Pytorch Add Instance Methods to PyTorch Frontend. So I am only working on adding |
@HaoES PyTorch Frontend works with every backend. You can run PyTorch frontend with TensorFlow backend as well. So backend is a requirement for frontend functions, and all of them need to be implemented before frontend. |
@HaiderSultanArc I understand, I don't know how to implement |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, seems like you have changed docs/demos
which you might have done by mistake. Can you revert that change because we can't merge with that change in place?
Hello @KareemMAX thank you for your review, can you please help me figure out how to do it?
|
Sounds good to me 😄. Take your time! |
It's fixed now. Pull the new changes and try these commands again |
@handle_out_argument | ||
@to_native_arrays_and_back | ||
@handle_array_function | ||
@handle_device_shifting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be undefined 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
honestly I don't have any idea what these decorators do XD I just copied them from the reshape
function because I assumed that unflatten
has the same behavior as reshape
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also have to import them. You can copy the import as well from where you picked this up 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current demos submodule commit on main branch of ivy is: 7c99cb5
Use the following commands:
git fetch upstream
cd docs/demos
git checkout 7c99cb5
cd ../../
git add -A
git commit -m "update: demos submodule"
git push origin PR
PR Description
added unflatten
Related Issue
Can you please check the implementation and guide me on how to write and run tests?
Close #25905
Checklist
Socials: