-
Right now it's hard coded in the application-specific location. This means that every instance of launched PhantomJS will share the same cache, which may cause problems in some use cases.
ariya updated
8 years ago
-
Jira issue originally created by user dlsniper:
In UnitOfWork::commit() it seems that a transaction is done like this:
- will send separate queries for transaction start
- compute the queries/send th…
-
by **efekty**:
What steps will reproduce the problem?
package main
import(
"unsafe"
"fmt"
)
type ZZZ struct { a uint8; b uint16; c uint8; d uint8; e uint16 }
//unsafe …
-
```
Take a look at CloseWatcher line 101 (v.1.3.166). Code adds to the
unsynchronized set new closeWatcher. That is not nice. Pls wrap static refs
variable with synchronized set. Additionally, there…
-
```
Take a look at CloseWatcher line 101 (v.1.3.166). Code adds to the
unsynchronized set new closeWatcher. That is not nice. Pls wrap static refs
variable with synchronized set. Additionally, there…
-
During test run update test is failing:
```
:plugin:test
com.github.ksoichiro.web.resource.WebResourceInstallBowerDependenciesTaskSpec > update FAILED
org.spockframework.runtime.UnallowedExcept…
-
we have basically 2 options IMHO:
1) stop tank, saving chunks to disk, update tank, start it, which means it has to decode from disk, and work through a backlog of data. this is AFAIK why we did #40
…
-
```
Take a look at CloseWatcher line 101 (v.1.3.166). Code adds to the
unsynchronized set new closeWatcher. That is not nice. Pls wrap static refs
variable with synchronized set. Additionally, there…
-
```
Take a look at CloseWatcher line 101 (v.1.3.166). Code adds to the
unsynchronized set new closeWatcher. That is not nice. Pls wrap static refs
variable with synchronized set. Additionally, there…
-
```
Take a look at CloseWatcher line 101 (v.1.3.166). Code adds to the
unsynchronized set new closeWatcher. That is not nice. Pls wrap static refs
variable with synchronized set. Additionally, there…