1. 26 8月, 2019 3 次提交
  2. 24 8月, 2019 14 次提交
  3. 23 8月, 2019 4 次提交
  4. 22 8月, 2019 8 次提交
  5. 21 8月, 2019 2 次提交
  6. 19 8月, 2019 1 次提交
  7. 18 8月, 2019 1 次提交
    • weixin_48148422's avatar
      fix & enhancement for udp connection handling · 01bb110b
      weixin_48148422 提交于
      1. potential data race in `taosProcessMonitorTimer`:
      the issue does not exist at present because there's only one scheduler
      thread, which means there's no cocurrent calls to this function for a
      same `pMonitor`. but if more scheduler threads are created later,
      there's a data race issue in rare case. as threads number can be
      easily increased by increase the value of `taosTmrThreads`, it is very
      unlikely that the developer could realize this function need to be
      revised together. that's why i say it is a 'potential' issue.
      
      this issue happens in below scenario:
      a. scheduler thread1: `if (pSet)` is true and new timer is installed by
      `taosTmrReset`;
      b. scheduler thread1: `if (pMonitor->pSet == NULL)` is true but
      `taosTmrStopA` is blocked, either by the mutex of the timer or os thread
      scheduler.
      c. timer thread: 200ms elapse, new call to `taosProcessMonitorTimer` is
      initialized in scheduler thread2;
      d. scheduler thread2: `if (pMonitor->pTimer != tmrId)` is false;
      e. scheduler thread1: unblocked, stops timer and frees `pMonitor`;
      f. scheduler thread2: unexpected behavior because `pMonitor` is not
      valid any more.
      
      because the result of this issue is crash or worse, i suggest to fix it
      though the possibility of all the conditions are met is very very low.
      
      2. `pthread_attr_t` related issues: per manual, an initialized
      `pthread_attr_t` can be reused, should be destroyed, and the behavior of
      re-init it is undefined. this issue exist in other modules also.
      
      3. memory leaks;
      
      4. improve failure case handling of `taosInitUdpConnection`;
      
      5. typo
      01bb110b
  8. 17 8月, 2019 3 次提交
  9. 16 8月, 2019 3 次提交
    • F
      2aa6c666
    • P
      Merge pull request #373 from satng/patch-1 · 4a644da7
      plum-lihui 提交于
      Update taosSqlCgo.go
      4a644da7
    • L
      Update taosSqlCgo.go · 0129a04a
      liuliang 提交于
      这个dbname都没有传进行,在连接池的情况下,每个连接都在选 use db.
      
      当连接池切换连接时,就会出现 invalid DB。
      ```
      8/16 12:44:46 dsn.go:59: input dsn: root:taosdata@/tcp(127.0.0.1)/sensors_test
      TAOS DRIVER 2019/08/16 12:44:46 dsn.go:130: cfg info: &{user:root passwd:taosdata net:/tcp addr:127.0.0.1 port:0 dbName:sensors_test params:map[] loc:0xed6be0 columnsWithAlias:false interpolateParams:true parseTime:true}
      TAOS DRIVER 2019/08/16 12:44:46 taosSqlCgo.go:52: taosQuery() input sql:INSERT INTO d_BDCF682B78F44364AA551B0F5E6BD1F6_acc USING acc_data TAGS ('BDCF682B78F44364AA551B0F5E6BD1F6','20190816-
      TAOS DRIVER 2019/08/16 12:44:46 taosSqlCgo.go:61: taos_query() failed: invalid DB
      ```
      0129a04a
  10. 15 8月, 2019 1 次提交