Bug 1077735
| Summary: | Squashed commits when saving project files | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> |
| Component: | Business Central | Assignee: | Alexandre Porcelli <porcelli> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Zuzana Krejčová <zkrejcov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | etirelli, jlocker, kverlaen, lpetrovi |
| Target Milestone: | ER1 | ||
| Target Release: | 6.0.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 19:53:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Zuzana Krejčová
2014-03-18 13:54:11 UTC
Alexandre, The problem appears to be if the first file in the batch written with IOService doesn't contain any changes then the batch operation squashes the commits into the prior commit. For example:- Write 1 (commit 1) : /path/file1.txt == "hello" Write 2 (commit 2) : /path/file2.txt == "world" [start batch] Write 3 (p/o commit 3) : /path/file1.txt == "hello" Write 4 (p/o commit 3) : /path/file2.txt == "world!!!!!" [end batch] Commit 3 is squashed into commit 2. If however the first file in the batch contains a change things are OK. For example:- Write 1 (commit 1) : /path/file1.txt == "hello" Write 2 (commit 2) : /path/file2.txt == "world" [start batch] Write 3 (p/o commit 3) : /path/file1.txt == "hello!!!!!" Write 4 (p/o commit 3) : /path/file2.txt == "world!!!!!" [end batch] Using the reported scenario, we save pom.xml, kmodule.xml and then project.imports. If I always make sure pom.xml contains a change then the commits are not squashed. If however pom.xml contains no changes the commits for the batch are squashed into the prior commit as reported. Thank you Michael for your research and perfect description of the problem. So here is the fix: (master) http://github.com/uberfire/uberfire/commit/3f80417bb (0.3.x) http://github.com/uberfire/uberfire/commit/7ce45bc68 Verified with ER2. |