Duga

Stack Overflow questions should be individually narrow and specific -- we don't generally do design advice here but stick to solutions to well-defined problems amenable to objectively provable solutions. For high level design, consider Software Engineering; for solutions to tactical issues, ask a separate question here for each such issue not already in our knowledge base. — Charles Duffy 58 secs ago

This question should be asked to LearnPress plugin authors on their support pages as it's not about a specific programming problem, a software algorithm, or software tools primarily used by programmers. Note that stack overflow doesn't handle any software support. We mainly help people on their real provided code attempt(s) when they are clear and detailed. — LoicTheAztec 58 secs ago

(If you're taking this as a class: please be aware of Open letter to students with homework problems & ensure that you're following your class's collaboration policy.) — Kaia 16 secs ago

Time to take the tour. This question is 100% off-topic, as 1) it's not a programming question; and 2) it's soliciting programmers for hire. So basically spam. — David Makogon 35 secs ago

The warning message is fairly clear: if you expect that your join will have a many-to-many relationship, add relationship="many-to-many" as an argument to the join. You have several calls to left_join in your function, try it in any or all of them. The reason that is there because many newer programmers do not recognize what will happen when there is not a clear 1-to-1 or 1-to-many relationship, and are really really confused when the number of rows in the results multiplies a lot. This is a safeguard, a warning. — r2evans 49 secs ago

The process of obtaining legal documentation is not a programming problem. It is very very very tangentially related, but you should be talking to legal experts not programmers about it. (That or seeing if Huawei has any documentation about it themselves, since it is their requirement.) — Quentin 11 secs ago

@Kaiido I've updated the answer with a list of differences and an explanation of how these might be used. If you want to ask why people might program like this, that's opinion-based. It might be a reasonable question at Software Engineering. — Barmar 52 secs ago

Stack Overflow questions should be individually narrow and specific -- we don't generally do design advice here but stick to solutions to well-defined problems amenable to objectively provable solutions. For high level design, consider Software Engineering; for solutions to tactical issues, ask a separate question here for each such issue not already in our knowledge base. — Charles Duffy 57 secs ago

(If you're taking this as a class: please be aware of Open letter to students with homework problems & ensure that you're following your class's collaboration policy.) — Kaia 16 secs ago

@FPGAguru2015: I'm glad you were able to get your code working. If if you are interested in getting feedback on the working version of your code, including the testbench, consider posting on Code Review. I have more advice to offer, which is outside the scope of Stack Overflow. — toolic 50 secs ago

For getting feedback on working code, the Code Review Stack Exchange is probably the better address. Make sure to read their How to ask first though. — paleonix 2 mins ago