Closed
Bug 1423069
Opened 8 years ago
Closed 8 years ago
Put js/src/jit-test/tests/typedobject/bug-1415313.js into js/src/jit-test/tests/TypedObject.
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla59
| Tracking | Status | |
|---|---|---|
| firefox59 | --- | fixed |
People
(Reporter: JamesCheng, Assigned: JamesCheng)
References
Details
Attachments
(1 file)
|
1.16 KB,
patch
|
jorendorff
:
review+
|
Details | Diff | Splinter Review |
I don't have the permission to look into Bug 1415313.
https://hg.mozilla.org/mozilla-central/rev/2d8ec1c6eb16
It seems "bug-141531.js" is located in a "typedobject" folder instead of the "/js/src/jit-test/tests/TypedObject/"
Is it possible to merge into "TypedObject"?
It makes my "case-insensitive" disk (Mac) with a strange behavior using git...
After rebasing to central,
$ git status
On branch master
Untracked files: (use "git add ..." to include in what will be committed) js/src/jit-test/tests/TypedObject/bug-1415313.js
I cannot erase this record by any operation....
Does anyone meet this issue?
| Assignee | ||
Updated•8 years ago
|
Group: mozilla-employee-confidential
| Assignee | ||
Comment 1•8 years ago
|
||
Does the patch make sense?
Thanks
Attachment #8934389 -
Flags: review?(kvijayan)
Comment 2•8 years ago
|
||
Why is this bug marked mozilla-employee-confidential?
I wonder if our prevent_case_only_renames Mercurial hook will allow this kind of change.
Flags: needinfo?(gps)
| Assignee | ||
Comment 3•8 years ago
|
||
Because Bug 1415313 is a security bug...
I'm afraid of revealing any information.
Feel free to unset the "mozilla-employee-confidential" if you think it's not necessary!
Comment 4•8 years ago
|
||
Ah I see. This bug does not reveal any extra information so it's fine to unhide it :)
Group: mozilla-employee-confidential
Comment 5•8 years ago
|
||
We actually don't have the hook to prevent case-only renames enabled. There's an old bug tracking that. It slipped off my radar because badness happens so rarely.
Renaming the directory will cause issues for people with case insensitive filesystems. So my preference is to avoid the rename.
The issue only occurs when doing an incremental working directory update. So if you want to perform a case-only rename with minimal disruption, you can do an initial non-case-only rename. Wait a few weeks. Then rename to the case-colliding name.
Flags: needinfo?(gps)
| Assignee | ||
Comment 6•8 years ago
|
||
Hi kvijayan,
Are you able to review the patch?
If you are busy right now, would you please transfer the review request to an appropriate one?
Thanks
Flags: needinfo?(kvijayan)
Comment 7•8 years ago
|
||
Comment on attachment 8934389 [details] [diff] [review]
0001-Move-file-into-TypedObject.patch
Thanks!
Flags: needinfo?(kvijayan)
Attachment #8934389 -
Flags: review?(kvijayan) → review+
Updated•8 years ago
|
status-firefox59:
--- → fix-optional
Priority: -- → P3
| Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jacheng
Keywords: checkin-needed
Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7c1f6b71b705
Move file into TypedObject. r=jorendorff
Keywords: checkin-needed
Comment 9•8 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in
before you can comment on or make changes to this bug.
Description
•