Giter Club home page Giter Club logo

Comments (4)

oscarngncc avatar oscarngncc commented on June 11, 2024

BTW the timezone is actually wrong. It presents 6:35 when the time is either 2:35 or 14:35. However, it doesn't really affect the 2-minutes time limit thing according to specification.

So I am leaving it here just as a warning.

from comp4111_project.

Camerash avatar Camerash commented on June 11, 2024

Would like to argue that validation of putting transactional statements are not documented in the project spec as well as the detailed test cases

In a perfect world, an invalid transaction would be catched in the put action and rejected. We are fully aware of this. However it is not mentioned specs, that's why it make sense to catch them when it is time to commit and rollback the transaction (which is documented and we forgot to implement and is now a standalone issue #13)

My argument here is if the where the validation of statement should be handled is unclear in the spec. Since the requirement of catching invalid statement is not present in the spec, and the rollback action is detailed in the spec if any statement error is encountered, we did not implement invalid statement handling (for non existing book id) in put action.

And since the failure of rolling back a transaction is already documented in #13, I do not agree this is a valid bug.

Again I will let @comp4111ta for the decision.

Cheers.

from comp4111_project.

oscarngncc avatar oscarngncc commented on June 11, 2024

Sorry if something is a bit unclear. Indeed, the specification is unclear and it's perfectly fine in my opinion to do the checking in either the put action or commit action.

The problem here is that the validation itself is wrong. It will always return SC_OK for both put action and commit action. Depending on the implementation, one would expect a 400 bad request in one of the two actions, in which the current program fails to achieve.

And since the validation always return true, rollback behavior in #13 seems to be inaccessible, if not actually implemented incorrectly. I think we can let @comp4111ta to decide it as either a single issue or two different issues.

Thanks!

from comp4111_project.

comp4111ta avatar comp4111ta commented on June 11, 2024

TA Verified: This is not considered as a bug.

from comp4111_project.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.