-
-
Notifications
You must be signed in to change notification settings - Fork 987
Proof of concept for #614 resolving #615
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
base: master
Are you sure you want to change the base?
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.
Also ideally we can add a test 👍
@dougwilson done |
anybody?) |
Sorry, I will take a look today. |
So I threw this PR into a couple of apps this morning and one of them threw an error. I reduced it down to the following test case: var express = require('express')
var expressSession = require('./index')
var app = express()
app.use(expressSession({
saveUninitialized: false,
secret: 'keyboard cat',
resave: false
}))
app.get('/', function (req, res) {
req.session.visitor = new String('username')
res.end()
})
app.listen(3000)
This same app works in the current versions of But this now has me a bit worried. I wonder what other types will have this issue? |
@dougwilson, finally I got my PR fixing this issue merged in |
@dougwilson ?) |
Hi @skarbovskiy I apologize, I thought I responded. I used a fuzzer and found that library has false positives, as in it will falsely think two different objects are the same. Ideally it should never have a false positive, only maybe false negatives. It's always better to accidentally resave the same thing to the database than to accidentally not save an actual change that was made. Here is a simplified version of two objects that
|
9d2e29b
to
408229e
Compare
No description provided.