About #7728 - do you watch closed requests for new posts?

Request #7728 was closed as obsolete for R# 201, I just experienced the same
exception it in 205 so it obviously still there. I see there posts from 201,
203, 204 and 205.
Do you watch this posts?

My regards,
-


Ariel Popovsky


5 comments
Comment actions Permalink

Hello Ariel,

yes, you're right, the problem causing this exception is still in 205. At
the time
#7728 was set to 'Obsolete' it was not yet known that this problem may occur
under different circumstances. In particular, it happens when you change
externally
an assembly referenced in your solution (this matches your description, since
you
wrote that you had switched back to VS there, and ReSharper synchronizes
external changes
when you activate VS). Unfortunately, our bug tracker is full of various
instances of this
problem, and we simply don't manage to set status for all those requests
correctly.

The good news is that in 206 we've made a change that appears to (hopefully)
fix this issue.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Request #7728 was closed as obsolete for R# 201, I just experienced
the same
exception it in 205 so it obviously still there. I see there posts
from 201,
203, 204 and 205.
Do you watch this posts?
My regards,
-----
Ariel Popovsky



0
Comment actions Permalink

Why doesn't your tracker simply reopen them if the version they are
submitted from is larger or equal to the one they were supposedly fixed in?

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a894d96d9ad8c7776e4d0489b7@news.intellij.net...

Hello Ariel,

>

yes, you're right, the problem causing this exception is still in 205. At
the time
#7728 was set to 'Obsolete' it was not yet known that this problem may
occur
under different circumstances. In particular, it happens when you change
externally
an assembly referenced in your solution (this matches your description,
since you
wrote that you had switched back to VS there, and ReSharper synchronizes
external changes
when you activate VS). Unfortunately, our bug tracker is full of various
instances of this
problem, and we simply don't manage to set status for all those requests
correctly.

>

The good news is that in 206 we've made a change that appears to
(hopefully) fix this issue.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Request #7728 was closed as obsolete for R# 201, I just experienced
>> the same
>> exception it in 205 so it obviously still there. I see there posts
>> from 201,
>> 203, 204 and 205.
>> Do you watch this posts?
>> My regards,
>> -


>> Ariel Popovsky
>



0
Comment actions Permalink

Hello Amir,

some time ago I was also interested in learning the answer to this question
:)
Unfortunately, it looks like the tracker does not currently implement such
policies,
the reason for this is beyond my knowledge.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Why doesn't your tracker simply reopen them if the version they are
submitted from is larger or equal to the one they were supposedly
fixed in?

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a894d96d9ad8c7776e4d0489b7@news.intellij.net...

>> Hello Ariel,
>>
>> yes, you're right, the problem causing this exception is still in
>> 205. At
>> the time
>> #7728 was set to 'Obsolete' it was not yet known that this problem
>> may
>> occur
>> under different circumstances. In particular, it happens when you
>> change
>> externally
>> an assembly referenced in your solution (this matches your
>> description,
>> since you
>> wrote that you had switched back to VS there, and ReSharper
>> synchronizes
>> external changes
>> when you activate VS). Unfortunately, our bug tracker is full of
>> various
>> instances of this
>> problem, and we simply don't manage to set status for all those
>> requests
>> correctly.
>> The good news is that in 206 we've made a change that appears to
>> (hopefully) fix this issue.
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Request #7728 was closed as obsolete for R# 201, I just experienced
>>> the same
>>> exception it in 205 so it obviously still there. I see there posts
>>> from 201,
>>> 203, 204 and 205.
>>> Do you watch this posts?
>>> My regards,
>>> -


>>> Ariel Popovsky


0
Comment actions Permalink

Hello Dmitry,

My original question stills remains unanswered, do you watch those supposedly
fixed requests for new entries or should I also post a message here to alert
you. I had like four exceptions like that one working with my web project.
I had to switch back to 165.

-


Ariel Popovsky

Hello Amir,

some time ago I was also interested in learning the answer to this
question :) Unfortunately, it looks like the tracker does not
currently implement such policies, the reason for this is beyond my
knowledge.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Why doesn't your tracker simply reopen them if the version they are
>> submitted from is larger or equal to the one they were supposedly
>> fixed in?
>>
>> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
>> news:c8a894d96d9ad8c7776e4d0489b7@news.intellij.net...
>>
>>> Hello Ariel,
>>>
>>> yes, you're right, the problem causing this exception is still in
>>> 205. At
>>> the time
>>> #7728 was set to 'Obsolete' it was not yet known that this problem
>>> may
>>> occur
>>> under different circumstances. In particular, it happens when you
>>> change
>>> externally
>>> an assembly referenced in your solution (this matches your
>>> description,
>>> since you
>>> wrote that you had switched back to VS there, and ReSharper
>>> synchronizes
>>> external changes
>>> when you activate VS). Unfortunately, our bug tracker is full of
>>> various
>>> instances of this
>>> problem, and we simply don't manage to set status for all those
>>> requests
>>> correctly.
>>> The good news is that in 206 we've made a change that appears to
>>> (hopefully) fix this issue.
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> Request #7728 was closed as obsolete for R# 201, I just experienced
>>>> the same
>>>> exception it in 205 so it obviously still there. I see there posts
>>>> from 201,
>>>> 203, 204 and 205.
>>>> Do you watch this posts?
>>>> My regards,
>>>> -


>>>> Ariel Popovsky


0
Comment actions Permalink

Hello Ariel,

I don't unsubscribe from fixed requests, so I get a notification whenever
someone
updates a fixed request. There are two problems, however:

1) I get too many notifications to look at all of them closely.
2) The notification message does not contain any information about the state
of the request being updated.
That is, I have to follow the link in the message to navigate to the request
and check it status.

So you see that it is easy to overlook an update of a fixed request. It seems
we should improve automated
processing of requests by e.g. incorporating more server-side policies like
special warning to the developer
on update of a fixed request. In my opinion, the current situation with submitted
exceptions is not satisfactory,
and not only because of problems mentioned above. Another important issue
is that there are tons of redundant
requests, and it is virtually not feasible to set 'Duplicate' status for
all of them correctly.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Dmitry,

My original question stills remains unanswered, do you watch those
supposedly fixed requests for new entries or should I also post a
message here to alert you. I had like four exceptions like that one
working with my web project. I had to switch back to 165.

-----
Ariel Popovsky

>> Hello Amir,
>>
>> some time ago I was also interested in learning the answer to this
>> question :) Unfortunately, it looks like the tracker does not
>> currently implement such policies, the reason for this is beyond my
>> knowledge.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Why doesn't your tracker simply reopen them if the version they are
>>> submitted from is larger or equal to the one they were supposedly
>>> fixed in?
>>>
>>> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
>>> news:c8a894d96d9ad8c7776e4d0489b7@news.intellij.net...
>>>
>>>> Hello Ariel,
>>>>
>>>> yes, you're right, the problem causing this exception is still in
>>>> 205. At
>>>> the time
>>>> #7728 was set to 'Obsolete' it was not yet known that this problem
>>>> may
>>>> occur
>>>> under different circumstances. In particular, it happens when you
>>>> change
>>>> externally
>>>> an assembly referenced in your solution (this matches your
>>>> description,
>>>> since you
>>>> wrote that you had switched back to VS there, and ReSharper
>>>> synchronizes
>>>> external changes
>>>> when you activate VS). Unfortunately, our bug tracker is full of
>>>> various
>>>> instances of this
>>>> problem, and we simply don't manage to set status for all those
>>>> requests
>>>> correctly.
>>>> The good news is that in 206 we've made a change that appears to
>>>> (hopefully) fix this issue.
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> Request #7728 was closed as obsolete for R# 201, I just
>>>>> experienced
>>>>> the same
>>>>> exception it in 205 so it obviously still there. I see there posts
>>>>> from 201,
>>>>> 203, 204 and 205.
>>>>> Do you watch this posts?
>>>>> My regards,
>>>>> -


>>>>> Ariel Popovsky


0

Please sign in to leave a comment.