text:
[sc] enable nebula_meta_ssl, after add hosts, balance in zone report error

as title
(root@nebula) [uuu33]>  add hosts "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779 into zone `us-east-2c`
Execution succeeded (time spent 1.152ms/2.318545ms)

Thu, 07 Sep 2023 20:47:27 CST

(root@nebula) [uuu33]> balance in zone
+------------+
| New Job Id |
+------------+
| 10         |
+------------+
Got 1 rows (time spent 1.237ms/2.184208ms)

Thu, 07 Sep 2023 20:47:31 CST

(root@nebula) [uuu33]> show job 10
+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+----------------------------+----------------------------+-------------------+
| Job Id(spaceId:partId) | Command(src->dst)                                                                                | Status     | Start Time                 | Stop Time                  | State             |
+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+----------------------------+----------------------------+-------------------+
| 10                     | "DATA_BALANCE"                                                                                | "FAILED"   | 2023-09-07T12:47:26.000000 | 2023-09-07T12:47:26.000000 | "E_JOB_SUBMITTED" |
| "10, 1:1"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:2"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:3"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:4"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:5"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:6"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "10, 1:7"              | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "FAILED"   | 2023-09-07T12:47:25.000000 | 2023-09-07T12:47:25.000000 | ""                |
| "Total:7"              | "Succeeded:0"                                                                                | "Failed:7" | "In Progress:0"            | "Invalid:0"                | ""                |
+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+----------------------------+----------------------------+-------------------+
Got 9 rows (time spent 1.098ms/2.467175ms)

Thu, 07 Sep 2023 20:47:33 CST

(root@nebula) [uuu33]> show parts
+--------------+---------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+
| Partition ID | Leader                                                                                | Peers                                                                                | Losts |
+--------------+---------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+
| 1            | "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-4.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 2            | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 3            | "nebulazcert-storaged-7.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-7.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 4            | "nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-10.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | ""    |
| 5            | "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 6            | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-4.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 7            | "nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-7.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 8            | "nebulazcert-storaged-10.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-10.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779" | ""    |
| 9            | "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
| 10           | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | "nebulazcert-storaged-4.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779, nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779"  | ""    |
+--------------+---------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+
Got 10 rows (time spent 1.269ms/2.303291ms)

Thu, 07 Sep 2023 20:48:01 CST

(root@nebula) [uuu33]> show zones
+--------------+----------------------------------------------------------------------------------+------+
| Name         | Host                                                                             | Port |
+--------------+----------------------------------------------------------------------------------+------+
| "us-east-2a" | "nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2a" | "nebulazcert-storaged-4.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2a" | "nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2a" | "nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2b" | "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2b" | "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2b" | "nebulazcert-storaged-7.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2b" | "nebulazcert-storaged-10.nebulazcert-storaged-headless.nebula.svc.cluster.local" | 9779 |
| "us-east-2c" | "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local" | 9779 |
| "us-east-2c" | "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2c" | "nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
| "us-east-2c" | "nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 |
+--------------+----------------------------------------------------------------------------------+------+
Got 12 rows (time spent 1.874ms/3.725131ms)

Thu, 07 Sep 2023 20:51:21 CST

(root@nebula) [uuu33]> show hosts storage
+----------------------------------------------------------------------------------+------+----------+-----------+--------------+----------------+
| Host                                                                             | Port | Status   | Role      | Git Info Sha | Version        |
+----------------------------------------------------------------------------------+------+----------+-----------+--------------+----------------+
| "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-4.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-7.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local"  | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-10.nebulazcert-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
| "nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | "STORAGE" | "b10a112"    | "3.5.0-sc-ent" |
+----------------------------------------------------------------------------------+------+----------+-----------+--------------+----------------+
Got 12 rows (time spent 1.427ms/2.550591ms)

Thu, 07 Sep 2023 20:51:28 CST

balane in zone report error
[root@nebulazcert-metad-0 nebula]# grep job logs/nebula-metad.INFO
I20230907 12:47:26.193697   121 JobManager.cpp:570] Add job successfully, job id=10, job type=DATA_BALANCE
I20230907 12:47:26.204830   198 JobManager.cpp:311] Trying to end job, spaceId=1, jobId=10, target phase status=FAILED
[root@nebulazcert-metad-0 nebula]# grep "I20230907 12:47:26.193697" -A100 logs/nebula-metad.INFO
I20230907 12:47:26.193697   121 JobManager.cpp:570] Add job successfully, job id=10, job type=DATA_BALANCE
I20230907 12:47:26.196938   110 BalancePlan.cpp:141] bucketSize: 7, concurrency: 7
I20230907 12:47:26.196962   110 BalanceTask.cpp:47] 10, 1:7,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.196979   110 BalanceTask.cpp:52] 10, 1:7 Start to move part, check the peers firstly!
I20230907 12:47:26.198477   110 BalanceTask.cpp:47] 10, 1:6,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.198496   110 BalanceTask.cpp:52] 10, 1:6 Start to move part, check the peers firstly!
I20230907 12:47:26.200115   110 BalanceTask.cpp:47] 10, 1:2,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.200132   110 BalanceTask.cpp:52] 10, 1:2 Start to move part, check the peers firstly!
I20230907 12:47:26.201504   110 BalanceTask.cpp:47] 10, 1:1,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.201521   110 BalanceTask.cpp:52] 10, 1:1 Start to move part, check the peers firstly!
I20230907 12:47:26.201825   192 BalanceTask.cpp:58] 10, 1:7,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.0.112:9778, local=10.244.3.65:59568), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.201838   194 BalanceTask.cpp:58] 10, 1:6,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.3.59:9778, local=10.244.3.65:44574), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.202085   194 BalanceTask.cpp:42] 10, 1:6,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.202098   194 BalancePlan.cpp:98] Balance 10 has completed 1 task
I20230907 12:47:26.202136   192 BalanceTask.cpp:42] 10, 1:7,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.202155   192 BalancePlan.cpp:98] Balance 10 has completed 2 task
I20230907 12:47:26.202227   110 BalanceTask.cpp:47] 10, 1:3,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.202239   110 BalanceTask.cpp:52] 10, 1:3 Start to move part, check the peers firstly!
I20230907 12:47:26.202576   110 BalanceTask.cpp:47] 10, 1:4,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.202592   110 BalanceTask.cpp:52] 10, 1:4 Start to move part, check the peers firstly!
I20230907 12:47:26.202883   110 BalanceTask.cpp:47] 10, 1:5,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 still in processing
I20230907 12:47:26.202909   110 BalanceTask.cpp:52] 10, 1:5 Start to move part, check the peers firstly!
I20230907 12:47:26.203729   193 BalanceTask.cpp:58] 10, 1:3,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-6.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.0.112:9778, local=10.244.3.65:59584), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.203833   193 BalanceTask.cpp:42] 10, 1:3,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.203842   193 BalancePlan.cpp:98] Balance 10 has completed 3 task
I20230907 12:47:26.204187   198 BalanceTask.cpp:58] 10, 1:2,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-5.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.3.59:9778, local=10.244.3.65:44582), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.204269   198 BalanceTask.cpp:42] 10, 1:2,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.204277   198 BalancePlan.cpp:98] Balance 10 has completed 4 task
I20230907 12:47:26.204324   195 BalanceTask.cpp:58] 10, 1:4,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.0.115:9778, local=10.244.3.65:47550), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.204412   195 BalanceTask.cpp:42] 10, 1:4,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.204429   195 BalancePlan.cpp:98] Balance 10 has completed 5 task
I20230907 12:47:26.204517   199 BalanceTask.cpp:58] 10, 1:1,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-2.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.3.54:9778, local=10.244.3.65:50506), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.204591   199 BalanceTask.cpp:42] 10, 1:1,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.204599   199 BalancePlan.cpp:98] Balance 10 has completed 6 task
I20230907 12:47:26.204674   198 BalanceTask.cpp:58] 10, 1:5,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Check the peers failed, status ["nebulazcert-storaged-1.nebulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: AsyncSocketException: recv() failed (peer=10.244.0.105:9778, local=10.244.3.65:35712), type = Internal error, errno = 104 (Connection reset by peer): Connection reset by peer
I20230907 12:47:26.204753   198 BalanceTask.cpp:42] 10, 1:5,nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Task failed, status 1
I20230907 12:47:26.204761   198 BalancePlan.cpp:98] Balance 10 has completed 7 task
I20230907 12:47:26.204766   198 BalancePlan.cpp:102] Balance 10 failed!
I20230907 12:47:26.204830   198 JobManager.cpp:311] Trying to end job, spaceId=1, jobId=10, target phase status=FAILED
I20230907 12:47:26.204887   198 JobManager.cpp:295] cleanJob 10

errors in operator:
E0907 12:56:23.250556       1 storage_client.go:89] TransLeader failed: read tcp 10.244.1.253:34752->10.244.3.64:9778: read: connection reset by peer
E0907 12:56:23.250668       1 nebula_cluster_control.go:119] reconcile storaged cluster failed: read tcp 10.244.1.253:34752->10.244.3.64:9778: read: connection reset by peer

Your Environments (required)
operator:reg.vesoft-inc.com/cloud-dev/nebula-operator:snap-1.12
nebula-ent-sc:  reg.vesoft-inc.com/rc/nebula-metad-ent pushed time 9/7/23, 4:49 PM
How To Reproduce(required)
Steps to reproduce the behavior:
1. with nebula_meta_ssl on ,3 graph , 12storage,1meta.
2. balance in zone remove "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779
3. drop hosts "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779
4. add hosts "nebulazcert-storaged-0.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-3.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779,"nebulazcert-storaged-8.nebulazcert-storaged-headless.nebula.svc.cluster.local":9779 into zone `us-east-2a`
5. balance in zone

Expected behavior
success

经过沟通，operator会做自动扩缩容，修改配置即可，不应该再通过console做手动运维，因此，测试范围超纲；请产品 @MuYiYong 考虑长远统一设计。

上面的报错是 add hosts后很快执行 balance 时出现的； 等了一段时间再来重试，没复现。今日重试，也没复现
当host是offline的时候，执行balance ，有数据需要移动到这个offline的节点时，也会报和上面相同的错：

20230908 04:01:27.414680   197 BalanceTask.cpp:103] 21, 13:8,nebulazcert-storaged-9.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779->nebulazcert-storaged-11.nebulazcert-storaged-headless.nebula.svc.cluster.local:9779 Open part failed, status ["nebulazcert-storaged-11.ne
bulazcert-storaged-headless.nebula.svc.cluster.local":9778] RPC failure in AdminClient: apache::thrift::transport::TTransportException: Failed to write to remote endpoint. Wrote 0 bytes. AsyncSocketException: AsyncSocketException: connect failed, type = Socket not open, errno = 111
(Connection refused)

repo: vesoft-inc/nebula-operator


text:
Simplify calculating delay after config failures

When there are several subscribers to a config and 1 JRTConfiguRequester
the counter for failures might quickly increase, so back-off based
on these numbers will not be useful. Simplify by using boolean
for failures instead. Max delay for configured subscriptions will
now be 30 seconds instead of 150 seconds (which is way too much)

More to be done here, but I think this fixes the important issue.

source: gharchive/pull-request

repo: vespa-engine/vespa

license_type: permissive

license_source: github-api


text:
JWT Token Authentication from Header

This PR adds the ability to read the JWT token from the Authorization header as default behavior.

Codecov Report

Merging #47 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #47   +/-   ##
======================================
  Coverage    91.7%   91.7%
======================================
  Files           5       5
  Lines         217     217
======================================
  Hits          199     199
  Misses         12      12
  Partials        6       6

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b0787f...41a775e. Read the comment docs.

authors: codecov-io larkmullins

repo: vetbase/husky

license: mit

license_source: bigquery


text:
(Feature request) Allow channels to exclude "unplayed content" from Plex

Hi,
This feature request, in short, is an option to have dizqueTV to exclude unplayed media when creating TV channels. This is a parity request that actually comes from Kodi's PseudoTV, where it would ignore unplayed media on channel scheduling.
Unsure of the exact difficulty to implement here as I don't know whether dizqueTV requests this type of information from Plex today.

When you say "ignore unplayed media" do you mean that it would only build and play channels of media thats already been previously viewed?

Hi Jon. You are interpreting my request correctly, yes.

source: gharchive/issue

authors: jonHuffman mstan

repo: vexorian/dizquetv

license: Zlib


text:
Enable loongarch64-linux-muslsf

https://github.com/vezel-dev/kruco/blob/f25c8241c3df0b6910bc9534e5233881230a9a29/tgt/riscv32imafc-linux-musl.mk.todo#L3

https://www.openwall.com/lists/musl/2024/06/29/1

repo: vezel-dev/kruco


text:
The server project has no  source file

The server project has no  source file.
“..\XcapServer\XcapServer\AuidHandlers\BaseAuidHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\BaseGenericAuidHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\BasePidfManipulationHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\BaseResourceListsHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\IAuidHandlerContext.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\IAuidHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\IGenericAuidHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\IUsersAuidHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\RlsServicesHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\AuidHandlers\XcapCapsHandler.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\Http\IHttpServer.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\Http\IHttpServerAgent.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\Http\IHttpServerAgentRegistrar.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\XcapErrors.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\XcapMessageWriter.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\XcapServer.cs”	D:sipserver\Server\CSC	Server
“..\XcapServer\XcapServer\XcapUriParser.cs”	D:sipserver\Server\CSC	Server

Sorry,I didn't see  " XcapServer @ 79ea342  "
Yes,the code is complete.


text:
Change Money currency property to currency_code

The currency_code field seems to be missing from GogoKit::Money objects, this change fixes the issue.
> listings.items.first.ticket_price
=> #<GogoKit::Money amount=900.0, currency_code="DKK", display="DKK900">
> listings.items.first.ticket_price.currency_code
=> "DKK"

I'm still having an issue with the display property, however:
> listings.items.first.ticket_price.display
#<GogoKit::Money amount=900.0, currency_code="DKK", display="DKK900">=> nil

Good catch. Thanks!

@thrillcall FYI we've released your pull request and a fix for the display property issue in gogokit.0.4.1

authors: akilb chriskallen thrillcall


text:
如何通过docker-compose启动

雷猴大佬，请问一下怎么通过docker-compose的形式启动呢

感谢大佬

repo: vicanso/pingap


text:
Multiplayer Server Doc Removed

The Google Doc containing multiplayer server addresses returns 410, and Google Docs says it has been deleted.

The Google Doc containing multiplayer server addresses returns 410, and Google Docs says it has been deleted.

Done! It was easier than I thought, I just needed to use the Wayback Machine.

authors: owenwestman vidio-boy

license: MIT


text:
Create database structure

Need to create database interface and sqlite implementation

Sqlite database structure created!
Need to add:

[ ] Dinamic creation of tables
[ ] pid to users model instead of emails
[ ] Know how to encrypt the pid of user

repo: vieirafrancisco/expense-record


text:
Update forms.css

Line 163 in .radio-field contained a typo. Corrected paddign-bottom to padding-bottom.

I actually newer saw the problems with radio-field layout. Ex http://forms.viewflow.io/demo/bank/ looks fine.
I think that code should be removed.

authors: kmmbvnr tufelkinder

repo: viewflow/django-material


text:
Add configuration into settings.py

#184
You can define the favicon, title and logo  adding this lines into settings.py file:
...
ADMIN_CONFIG = {
    'ADMIN_NAME': 'My Site Admin',
    'ADMIN_HEADER': '<img class="responsive-img" src="'+MEDIA_URL+'images/logo.png">',
    'FAVICON': MEDIA_URL+'images/favicon.ico',
}

Sorry, I don't think that it's required

Let me give a more detailed explanation why this pull request was rejected.
The first, and the main reason that the overriding templates and static files  is the desired way to modify admin or other 3d party apps. That's listed in the django docs - https://docs.djangoproject.com/en/1.10/ref/contrib/admin/#adminsite-attributes
So your initial solution posted at https://github.com/viewflow/django-material/issues/184 mostly correct.
The second issue that the logo is going to be removed from a sidebar since the new version of MaterializeCSS and Google material design guidelines suggest having user pic here.
Here is screen of the new django-material frontend and admin going to have the same layout

The third issue is the inconsistent settings name. Material-admin already have MATERIAL_ADMIN_SITE, so the new one settings definitely should have a name started with MATERIAL_ADMIN to be consistent with existing and not to accidently collide with some settings from other packages.
The fourth issue is the new template tag library for the admin misplaced into the root material package and ignored the existing material_admin tag library.
I'm also not ok with the idea of injecting settings value into the template with template filter. To be more django-like it should be implemented as assignment tag.

Thanks for your answer.
I will wait for the new layout admin frontend.


text:
Implement a new Mathematics Library based from Stride/SlimDX

This PR creates a new experimental mathematics library ported from Stride and SlimDX as a solution to System.Numerics's limitation.

Will need the tests ported as well, which I'll do later on.

repo: vignetteapp/sekai


text:
[FEATURE] Incorporate weather from now-discontinued Calendar/Weather module

Would love to see my favorite feature of Calendar/Weather ported over to Simple Calendar, now that the former is no longer maintained.

Yup this is planned to be added. Just working on some other features first.

I would commission this feature if you're interested, wrote an e-mail to your address given on your homepage but got no feedback.

oh, which email? I'm not seeing anything in my spam folders or inbox.

i send it to vig@vig.vg, can i reach you somewhere else?

oh wait i did send an email to @vigoren not you. Sorry for the confusion

@Nordiii hey sorry I'm out camping at the moment (don't have reliable service) I'll get back to you as soon as I'm back in civilization lol

Hi @ctbritt, I picked up development of Calendar/Weather a few weeks ago so the module is still alive!
@vigoren this might interest you, there are a few changes that will happen soon on our side and we will partially switch date management from About-Time to Simple Calendar.
We will still take care of events, season and weather so you don't have to worry about this ;) I am still trying to figure out what the new responsibilities of Calendar/Weather will be, but my main goal is to avoid duplicating efforts on features across modules.
I have an open discussion thread on my repo if anyone wants to stay up to date with the discussions we have on our side: https://gitlab.com/jstebenne/foundryvtt-calendar-weather/-/issues/37

I am going to close this issue as the calendar/weather module is being repurposed to add weather support to Simple Calendar. This move names not sense to me as the weather module can then be added if people want. Make sure to keep tabs on their progress for when it is ready 😁

authors: Nordiii TheBird956 ctbritt vigoren

repo: vigoren/foundryvtt-simple-calendar


text:
Add more meta tags to the HTML page

PR Activity ref: #8
Links to get started

https://www.searchenginejournal.com/important-tags-seo/156440/

Hi, if you can clarify more about what tags you want, I would like to work on this,
Thanks

Hi @ATiwari2000 , thanks for taking this up!
A good place to start would be this checklist: Accessibility Checklist - Minnesota Department of Health https://www.health.state.mn.us/about/tools/allychecklist.pdf

closed via https://github.com/vijay-jaisankar/pandemonium/pull/23

repo: vijay-jaisankar/pandemonium


text:
0000-01-03-vijaychenthil.md

Commits 101

Added

repo: vijaychenthil/github-slideshow


text:
Fix Could not load virtual:vike:pageConfigValuesAll

I'm not sure what extractAssetsRemoveQuery() functions should do exactly, but this fixes the problem reported in #1419 for me.
Fixes #1419

Thanks for opening a PR for it, neat. I improved your fix a bit. It's pre-relased as 0.4.156-commit-f4c1d32.
Let me know if you stumble upon any (other) issue. Also, in case your company is up for it: https://github.com/vikejs/vike/issues/1350.

repo: vikejs/vike


text:
Add Topic

Kindly add the topic hacktoberfest  in about section of the repository, and accept PRs.
Reference: https://hacktoberfest.digitalocean.com/hacktoberfest-update

Hacktoberfest has added a new update , due to spammy PR's going on a huge number .
https://hacktoberfest.digitalocean.com/hacktoberfest-update
For the PR's to be valid for the hacktoberfest they need to merged or added the label : accepted for hacktoberfest
There is a typo in the topic you've added
Please Look into this @vikhyatsingh123

@vikhyatsingh123 please add hacktoberfest label in the repo to make the PRs count

ok

@vikhyatsingh123 the pr's still didn't count. You spelled the label wrong.


text:
docs: add badges

Continuation of #2.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (master@d7648e5). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   97.67%
=========================================
  Files             ?        3
  Lines             ?       43
  Branches          ?        6
=========================================
  Hits              ?       42
  Misses            ?        0
  Partials          ?        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
🛑 Booking is down

In 0c8095f, Booking ($SITE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Booking is back up in 8c1dc59.

repo: villekulla-nma/monitor-booking


text:
🛑 Booking is down

In fc67270, Booking (https://booking.villekulla-nma.de/api/_health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Booking is back up in 74ac7db.


text:
Added example, added better init for egui editor

This PR adds two things:

A new example showing the usage of the inspector-egui
added encompassing_curve which initialized the viewport of a LookupCurveEguiEditor to encompass the curve

Awesome contributions! Thanks ❤
As a follow up, I think we should make encompass_curve a method taking &self as param. That way we can call it again if we need to "re-fit" the curve. Could even add a button to do so in the editor.
Merged!

authors: ArneCJacobs villor


text:
Function keys print , , etc in insert and command modes

When I press a function key in insert or command modes <F2>, <F3>, etc. is printed. I tested with vim 8.1 on MacOS and vim 8.0 on Ubuntu with vim -u NONE -N. If I set compatible, it prints terminal sequences to the screen. vim 7.4 does not experience either of these behaviors and acts as expected- pressing a non-mapped function key does not print anything.

sounds like a configuration issue.
Please ask user questions on the vim_use mailinglist or use vi.stackexchange.com. This here is a bug tracker for problems with Vim. We cannot provide individual help here. Closing.

How is this a configuration problem -u NONE was used and it occurs on different vim versions on different os's on different machines with different keyboard types?

what keys like <f1> or <alt> send, is very much dependent on your system, the terminal/gui being used and probably other factors I do not know about. So you would have to first figure out, how those factors differ between your systems and then try to understand how that differs between Vim versions. You did not mention much details here, so I expect a configuration issue. Nevertheless, I would expect, that if a key like <f1> is typed, it also inserts <f1> into the buffer instead of behaving like no keypress. But we are much guessing here, we need more details to decide whether this is a bug or a configuration issue.

If you have a non-mapped function key the expected behavior is to insert whatever byte sequence that key produces.  Vim doesn't know what key you pressed, thus will insert whatever it got.
If Vim does recognize a function key (or another key that doesn't have a predefined meaning) it will insert a standard code, instead of the terminal-dependent escape sequence.  That's all working as intended.

To make sure that, let's say, the F5 key sends nothing (and in particular not <F5>) in Insert, Replace or Command-line modes, make it explicitly do nothing, e.g.
:map! <F5> <Nop>

OTOH, using Ctrl-V F5 in Insert mode will give you <F5> in gvim and whatever termcap codes your terminal uses for F5 when running in console mode. All this is normal and expected.
Best regards,
Tony.

If you have a non-mapped function key the expected behavior is to insert whatever byte sequence that key produces. Vim doesn't know what key you pressed, thus will insert whatever it got.
If Vim does recognize a function key (or another key that doesn't have a predefined meaning) it will insert a standard code, instead of the terminal-dependent escape sequence. That's all working as intended.

Is this new behavior? I tested vim 7.4 on macOS and Linux and they don't exhibit the behavior. It's just annoying when accidentally hitting a single function key and it produces four characters that must be backspaced over to undo. I have now mapped FN 2-12 to <Nop>, but if this is expected behavior now, are all users are expected to add this to their vimrc? Or is there some benefit to having vim insert these codes?

Even if you haven't mapped them, you might still want to talk about them; or if you hit them by mistake, to know what Vim saw.
Myself, I don't have this problem because almost all my F and Shift-F keys are mapped in most modes to do something useful to me. (I added those mappings a few at a time ever since I've been using Vim.) I'm even starting to get to the point where I might have to use ² ³ ù µ £ é § è ç à (provided natively as standard or shifted keys by my Belgian AZERTY keyboard) as {lhs} for my next Normal-mode mappings.
Of course, YMMV.
Best regards,
Tony.

I tried this with Vim 7.3.1314 on Windows (both GUI and CUI).
When I pressed F2 key, the four characters <, F, 2 and > were inserted literally (on command mode and insert mode). So this behavior is not changed at least on Windows.
I haven't checked on other platforms.

When I press a function key in insert or command modes <F2>, <F3>, etc. is printed. I tested with vim 8.1 on MacOS and vim 8.0 on Ubuntu with vim -u NONE -N. If I set compatible, it prints terminal sequences to the screen. vim 7.4 does not experience either of these behaviors and acts as expected- pressing a non-mapped function key does not print anything.

I am having exactly the same problem.
(keyboard : happy hacking keyboard hybrid type-s)
(Oracle cloud server, Ubuntu 20.04, vim 8.1, ssh remote access environment)
fn+h supposed to print *, but print .
fn+j supposed to print /, but print .
fn+n supposed to print +, but add a new line above the cursor and print l.
fn+m supposed to print -, but print .
I formatted linux but that didn't solve it. Thanks for the vim version information regarding this error. I am considering using vim 7.4 version.

authors: brammool chrisbra elgar328 grr k-takata tonymec

repo: vim/vim

license: Vim


text:
Option argument --clean isn't in vim.man

I didn't find --clean in the output of man vim.
But I found it with :h --clean.
Vim 8.2.2730

There are a lot of options available on the command line for vim that are not mentioned in man vim. See :help starting while in vim and you'll see quite a few.

Oh, OK. I didn't realize that. I just checked a couple other options (the ones listed above and below :h --clean) and saw that they were mentioned in man vim. But now I see that, like you said, other options are also missing from man vim, such as --ttyfail.

Matthew Mario Di Pasquale wrote:

I didn't find --clean in the output of man vim.

Indeed.  I'll add it, it's quite useful.
--
In a world without walls and borders, who needs windows and gates?
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

OK, sounds good. Thanks, @brammool.

Fixed by https://github.com/vim/vim/commit/56994d215815139207f3c5ce02a1720e44e93c09

authors: brammool cecamp lacygoill ma11hew28


text:
~/.aws/ files are not recognized

~/.aws/config and ~/.aws/credentials are INI conf files.

~/.aws/config and ~/.aws/credentials are INI conf files.

Please add an entry in the test file: src/testdir/test_filetype.vim.
The autocmd line might as well added separately, just to make it easier
to read.
--
SOLDIER: What?  Ridden on a horse?
ARTHUR:  Yes!
SOLDIER: You're using coconuts!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

authors: brammool justinmk


text:
filetype: r history files cannot be recognized

Problem: r history files cannot be recognized.
Solution: Add a pattern for r history files.

thanks!

authors: Freed-Wu chrisbra


text:
runtime(doc): fix invalid link to Open Publication License

The link in https://opencontent.org/openpub is actually invalid too:
Copyright (c) <year> by <author’s name or designee>.
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at https://www.opencontent.org/openpub/).

But since the text here doesn't exactly match that anyway (doesn't have the parentheses), it's probably fine to fix it.

thanks, I include this together with some more fixes of invalid links.

authors: chrisbra zeertzjq


text:
Expose valueToColor4 as constructor option

👋 this package has been very handy! Was looking to write a custom valueToColor4 function as mentioned in the README, though it looks like this isn't customizable via the constructor options (though valueToColor is). Is there any reason this can't / shouldn't be updated?
If not, I'm happy to open a PR and update this. Thanks!

👋 this package has been very handy! Was looking to write a custom valueToColor4 function as mentioned in the README, though it looks like this isn't customizable via the constructor options (though valueToColor is). Is there any reason this can't / shouldn't be updated?
If not, I'm happy to open a PR and update this. Thanks!

This is already exposed – https://github.com/vinayakkulkarni/mapbox-gl-interpolate-heatmap/blob/main/src/layer.ts#L20-L24

Perhaps I'm misunderstanding - the constructor type seems to accept valueToColor4 but doesn't actually use it to update the default class field:
https://github.com/vinayakkulkarni/mapbox-gl-interpolate-heatmap/blob/4eb77bdf5c7e6f13ddacf943d8326d29dc22cbd5/src/layer.ts#L67-L85
I think this would just require a small addition to the constructor:
  constructor(options: HeatmapLayer) {
    this.id = options.id || '';
    this.data = options.data || [];
    this.aoi = options.aoi || [];
    this.valueToColor =
      options.valueToColor ||
      `
      vec3 valueToColor(float value) {
          return vec3(max((value-0.5)*2.0, 0.0), 1.0 - 2.0*abs(value - 0.5), max((0.5-value)*2.0, 0.0));
      }
  `;
+    this.valueToColor4 =
+      options.valueToColor4 ||
+      `
+      vec4 valueToColor4(float value, float defaultOpacity) {
+          return vec4(valueToColor(value), defaultOpacity);
+      }
+  `;
    this.opacity = options.opacity || 0.5;
    this.minValue = options.minValue || Infinity;
    this.maxValue = options.maxValue || -Infinity;
    this.p = options.p || 3;
    this.framebufferFactor = options.framebufferFactor || 0.3;
    // Having a framebufferFactor < 1 and a texture that don't cover the entire map results in visual artifacts, so we prevent this situation
    this.textureCoverSameAreaAsROI = this.framebufferFactor === 1;
  }

Perhaps I'm misunderstanding - the constructor type seems to accept valueToColor4 but doesn't actually use it to update the default class field:
https://github.com/vinayakkulkarni/mapbox-gl-interpolate-heatmap/blob/4eb77bdf5c7e6f13ddacf943d8326d29dc22cbd5/src/layer.ts#L67-L85
I think this would just require a small addition to the constructor:

  constructor(options: HeatmapLayer) {

    this.id = options.id || '';

    this.data = options.data || [];

    this.aoi = options.aoi || [];

    this.valueToColor =

      options.valueToColor ||

      `

      vec3 valueToColor(float value) {

          return vec3(max((value-0.5)*2.0, 0.0), 1.0 - 2.0*abs(value - 0.5), max((0.5-value)*2.0, 0.0));

      }

  `;

+    this.valueToColor4 =

+      options.valueToColor4 ||

+      `

+      vec4 valueToColor4(float value, float defaultOpacity) {

+          return vec4(valueToColor(value), defaultOpacity);

+      }

+  `;

    this.opacity = options.opacity || 0.5;

    this.minValue = options.minValue || Infinity;

    this.maxValue = options.maxValue || -Infinity;

    this.p = options.p || 3;

    this.framebufferFactor = options.framebufferFactor || 0.3;

    // Having a framebufferFactor < 1 and a texture that don't cover the entire map results in visual artifacts, so we prevent this situation

    this.textureCoverSameAreaAsROI = this.framebufferFactor === 1;

  }

Feel free to open an PR ;)

authors: chrissantamaria vinayakkulkarni


text:
Broken keycloak url

https://vinbigdata-medical.github.io/vindr-lab/getting-started/KEYCLOAK.md

Thanks for your issue. I had fixed the url

repo: vinbigdata-medical/vindr-lab-deployment


text:
removing unknown PMD rules after gradle version upgrade

Closes #14

The rule <rule ref="rulesets/java/android.xml" /> must stay. Just remove the inner rules.

Perfect, thanks for the PR !

authors: rafaeltoledo sewerk vincentbrison

repo: vincentbrison/vb-android-app-quality


text:
Using data directly from a store

Hi, I was wondering what's the solution for directly using data that exists in a store?
I'm trying to build a favorites list, which would need to dynamically add/remove items from the data array and auto update the table

Here are the relevant pieces of code:
Datatable component
<div>
<Datatable {settings} {$data} bind:dataRows={rows}>
(...)
</Datatable>
</div>

Store + data:
import { writable } from 'svelte/store';

export const data = writable([
	{ id: 1, first_name: 'Tobie', last_name: 'Vint', email: 'tvint0@fotki.com' },
	{ id: 2, first_name: 'Zacharias', last_name: 'Cerman', email: 'zcerman1@sciencedirect.com' },
	{ id: 3, first_name: 'Gerianna', last_name: 'Bunn', email: 'gbunn2@foxnews.com' },
	{ id: 4, first_name: 'Bee', last_name: 'Saurin', email: 'bsaurin3@live.com' },
	{ id: 5, first_name: 'Meyer', last_name: 'Garnul', email: 'mgarnul4@yellowbook.com' },
	{ id: 6, first_name: 'Frederich', last_name: 'Benley', email: 'fbenley5@ameblo.jp' },
	{ id: 7, first_name: 'Becki', last_name: 'Criag', email: 'bcriag6@washingtonpost.com' },
	{ id: 8, first_name: 'Nichols', last_name: 'Risom', email: 'nrisom7@google.com.br' },
	{ id: 9, first_name: 'Ron', last_name: 'Menendes', email: 'rmenendes8@prnewswire.com' },
	{ id: 10, first_name: 'Thane', last_name: 'Gammill', email: 'tgammill9@com.com' },
	{ id: 11, first_name: 'Ramonda', last_name: 'Yakobowitch', email: 'ryakobowitcha@hibu.com' }
]);

Trying this gives the following errors:
<Datatable> was created with unknown prop '$data':

Thank you :)

Hi,
There's no reason it can't work.
Maybe the problem is there :
<Datatable data={$data} ... >

That… is exactly the solution. Thank you so much 🌹

authors: mr-islam vincjo

repo: vincjo/svelte-simple-datatables


text:
Name pronunciation feature

BEFORE

NOW 👇

Is this project participating in 2021?
If yes, Kindly assign me this issue 🙂

repo: vinitshahdeo/SimpleBio


text:
redisClusterCommand run "scan 0"  get an error!!

msg:Parse command error. Cmd type: 0, state: 5, break position: 12

Can you please provide more details ?

repo: vipshop/hiredis-vip


text:
Madee the README a little nicer

In my opinion this:
In [1]: mid = MIDIParser('sample.mid', track=0)

In [2]: mid.notes_played()
Out[2]:
[{'note': 'C#5', 'time': 18},
 {'note': 'C#5', 'time': 30},
 {'note': 'B4', 'time': 26},
 {'note': 'C5', 'time': 0},
 {'note': 'C5', 'time': 28},
 {'note': 'C#5', 'time': 28},
 {'note': 'C#5', 'time': 30}]

can be a little confusing for new users because they might be wondering what In [1]: is.
Keeping the standard prompt can prevent confusion.
>>> mid = MIDIParser('sample.mid', track=0)
>>> mid.notes_played()
[{'note': 'C#5', 'time': 18},
 {'note': 'C#5', 'time': 30},
 {'note': 'B4', 'time': 26},
 {'note': 'C5', 'time': 0},
 {'note': 'C5', 'time': 28},
 {'note': 'C#5', 'time': 28},
 {'note': 'C#5', 'time': 30}]

Hey @sdushantha,
Thanks for pointing this out and submitting a pull request for this. I thought of doing the same but completely forgot to make a note of it. Thanks.
🍰

Oooo yummy! I liked the cake 😊


text:
[Feature Request] Add support for alpha video

Add support for alpha video in Viro and be able to specify the chroma key color to use (e.g. green, blue, or other).

This is now fixed and included in our latest Viro React release.

repo: viromedia/viro


text:
Video 360 background not playing in ARScene

[x] Review the documentation: https://virocore.viromedia.com/
[x] Search for existing issues: https://github.com/viromedia/virocore/issues
[x] Use the latest ViroCore release: https://virocore.viromedia.com/docs/releases
[x] Turn off Instant Run in Android Studio

Environment
Please provide the following information about your environment:

OS: Windows
Version: 1.14.0
Device(s): Samsung Galaxy S9+

Description
I'm starting to use ViroCore and I'm tryng to create a AR app with a 360 video as background, I follow the documentation and the video is painting as background but no playing at all.
Reproducible Demo
VideoTexture videoTexture = new VideoTexture(mViroView.getViroContext(),
    Uri.parse("file:///android_asset/prueba_s_santa_alpha.mp4"));
mScene.setBackgroundTexture(videoTexture);
videoTexture.play();
mViroView.setScene(mScene);

Hi @dpr10, this should work. I've tried both setting the background texture directly and using a sphere as the background - and both works. Have you tried testing with different videos?

repo: viromedia/virocore


text:
feat(Transport): Adding method that users can call to check for new messages

This allows user to call CheckForMessages when they want incase their game want to call it multiple times per frame or from a different update loop.

adding CheckForMessages
adding LateUpdate that calls CheckForMessages
adding bool to disable the LateUpdate call
removes Empty Update method

BREAKING CHANGE: Transports now need to implement CheckForMessages
If we want to do a change like this it is worth doing it at the same time as https://github.com/vis2k/Mirror/pull/2482 so transport owners dont need to update multiple times.

can you elaborate?
why should the game worry about transport?
transport should decide the best way to check messages :)

can you elaborate?
why should the game worry about transport?
transport should decide the best way to check messages :)

Some users want to check for new message right before process things, for example CheckForMessage then use inputs to run physics ticks.
One downside of LateUpdate is that it processing message at the end of the frame, before waitForTargetFps, so any message that arrive during that wont be processed till next frame. If you want to min/max for latency then being able to call CheckForMessage right before you need it is very useful.
For the average user this wont change anything, the transports will still call it themselves in LateUpdate, there would just be a way to override that if needed

Some users want to check for new message right before process things, for example CheckForMessage then use inputs to run physics ticks.

I don't get it,   why would a user want to do that?
I am also not sure why we use LateUpdate at all.

I don't get it, why would a user want to do that?

if you are running a server at 60fps, 16ms per frame, and your update loops only take 5ms, then LateUpdate runs then waitForTargetFps will pause for 10ms, adding 10ms of latency to your game. 10ms isn't much for a slow paced mmo, but for a fast paced game where a developer might want to minimize latency as much as possible 10ms matters.

I am also not sure why we use LateUpdate at all.

LateUpdate seems like it works for a lot of cases so it got forced on everyone. This PR just gives the option for people to call it elsewhere if they think it is better for their use case.

I am also not sure why we use LateUpdate at all.

That's a Vis decision back in whoopwhoop days. Seriously, so long ago I can't even remember. He blocked Update in the Transport loop because he encountered some deadlock/race condition with it in one of his assets, causing us all to use LateUpdate. As you can tell, it's a bad idea for many reasons including the critics' own. Fholm even agrees.
James also did a good job explaining why above, since we're literally waiting for VSync to finish before getting data out the door. Data that needs to be sent needs to go out the door ASAP, not taking a stroll for a little bit until VSync has finished.
Basically, allowing more control over the processing part will turn heads as it gives the developer another power tool to master. If they break it, the problem's on their side. If you don't want to use manual transport pumping by your own code, no problem - just let Mirror do it instead.

Basically, allowing more control over the processing part will turn heads as it gives the developer another power tool to master. If they break it, the problem's on their side. If you don't want to use manual transport pumping by your own code, no problem - just let Mirror do it instead.

options + documentation = happy power users

options + documentation = happy power users

This.

Here is timings from 2 frames.
Methods Called, StopWatch Time, Time since last LateUpdate

Because we process stuff in LateUpdate we artificially add up to 16ms of latency to all projects because some have race conditions

@vis2k I need the go ahead on this feature before I can update the transport classes so I am not wasting me time.

Because we process stuff in LateUpdate we artificially add up to 16ms of latency to all projects because some have race conditions

Ok,  so that's the problem we are trying to solve,  eliminate that 16ms latency.
If we polled the transport in Update(),  would that solve the problem?

Because we process stuff in LateUpdate we artificially add up to 16ms of latency to all projects because some have race conditions

Ok, so that's the problem we are trying to solve, eliminate that 16ms latency.
If we polled the transport in Update(), would that solve the problem?

The problem is that we can not know the best time to poll for all game types.
The Solution I see is to allow users to poll extra times or when they want.

I think should just be dedicated thread push data out. Network code should not be depended on when unity updates. There are going to be lota of different data being sent and polled. Some will be health stuff some ia movement code. There will be mo right or wrong spot if using dedicated thread. Soon as data ready to go send it. Power users have full control over the data when using network behaviours they can override the serialize and deserialize functions and can queue or doing whatever they want through there. I think data needs just be pushed fast as possible and users can do there own thing through those functions

I think should just be dedicated thread push data out. Network code should not be depended on when unity updates. There are going to be lots of different data being sent and polled. Some will be health stuff some ia movement code. There will be no right or wrong spot if using dedicated thread. Soon as data ready to go send it.
Power users have full control over the data when using network behaviours they can override the serialize and deserialize functions and can queue or doing whatever they want through there. I think data needs just be pushed fast as possible and users can do there own thing through those functions

This is for processing received data, which has to be done on main thread incase it effects any of unity methods (eg settings transport position)
Data can be sent at anytime using conn.Send as it sends it to the transport right away, and then it is up to the transport how it sends it (for example telepathy does it on a side thread asap)

I think should just be dedicated thread push data out. Network code should not be depended on when unity updates. There are going to be lots of different data being sent and polled. Some will be health stuff some ia movement code. There will be no right or wrong spot if using dedicated thread. Soon as data ready to go send it.
Power users have full control over the data when using network behaviours they can override the serialize and deserialize functions and can queue or doing whatever they want through there. I think data needs just be pushed fast as possible and users can do there own thing through those functions

This is for processing received data, which has to be done on main thread incase it effects any of unity methods (eg settings transport position)
Data can be sent at anytime using conn.Send as it sends it to the transport right away, and then it is up to the transport how it sends it (for example telepathy does it on a side thread asap)

I know what its for and it can be done in dedicated thread. It will be more complex but will be alot better in the end for mirror to run on its own and not worry about what unity is doing or not doing. This is just my opinion tho.

I know what its for and it can be done in dedicated thread. It will be more complex but will be alot better in the end for mirror to run on its own and not worry about what unity is doing or not doing. This is just my opinion tho.

It should be done on the main thread as it can call unity functions.
But if someone knows in their project they will never be calling Unity functions from network message then they could call this new method from a side thread if they wanted to.

I know what its for and it can be done in dedicated thread. It will be more complex but will be alot better in the end for mirror to run on its own and not worry about what unity is doing or not doing. This is just my opinion tho.

It should be done on the main thread as it can call unity functions.
But if someone knows in their project they will never be calling Unity functions from network message then they could call this new method from a side thread if they wanted to.

Ia this not transport specific. How is someon3 going to call this at there end if transports are the one who have and can only override this? Would it not need to be an event that passes the data and people can listen to it do things with it if its for end users and not transports?

Someone would call Transport.activeTransport.CheckForMessages() which would tell the transport to invoke the DataReceived callback.

We'd have to be extra careful when dealing with threads - if we call functions that are not thread safe like spawning objects into the Scene and whatnot, then we can potentially get an Access Violation and bye bye Unity.
We're getting there. I honestly think we should empower the user with this feature as it solves the LateUpdate issue that I've barked about countless times.

I dont think we need to worry about the extra thread stuff, if a user wants to do new Thread and then call out function it could fail, in the same way if they do that for unity code. Even if the transport is thread safe, some of the deserializing or the message handler code might not be thread safe because it can call unity stuff.

I don't think threads will work here @dragonslaya84,
See,  these messages end up calling rpcs and message handlers,  which may call unity api's.  Unity very much forces us to invoke the rpc and handlers in the main thread.   Of course,  transports can receive data in a background thread, but we have to switch to the main thread at some point before dispatching it to the handlers,  and this is where the 16 ms latency is being introduced.
But by all means,  if you have another idea,  maybe you can put together a POC for what you mean?

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

yeah,  that's fine,  the transports can use threads internally for doing some of the heavy liftings,  telepathy already does that.  But at some point, they need to switch to the main thread before they dispatch the message to mirror,  and that is what is causing that latency.

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

yeah,  that's fine,  the transports can use threads internally for doing some of the heavy liftings,  telepathy already does that.  But at some point, they need to switch to the main thread before they dispatch the message to mirror,  and that is what is causing that latency.

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

yeah, that's fine, the transports can use threads internally for doing some of the heavy liftings, telepathy already does that. But at some point, they need to switch to the main thread before they dispatch the message to mirror, and that is what is causing that latency.

Thats why the CheckForMessages function is nice as it can reduce that latency

@paulpach
Depending on the transport threads might be useful, they can handle reassembly of messages and encryption before the main thread polls them. But its so transport specific that this probably belongs to the transport and not into Mirro, but for that we would need such a CheckForMessages() function.
Additionally it would allow the epic and steam transport to check for new messages right after ticking the platform, so I am definitly in favor of this change.

yeah, that's fine, the transports can use threads internally for doing some of the heavy liftings, telepathy already does that. But at some point, they need to switch to the main thread before they dispatch the message to mirror, and that is what is causing that latency.

Thats why the CheckForMessages function is nice as it can reduce that latency

Thats why the CheckForMessages function is nice as it can reduce that latency

Ok,  we are going in circles now.   I fully understand the motivation: get rid of the extra latency.  My comment was replying to the suggestion of using threads.
Back to the PR: CheckForMessages may work, but it is not an elegant solution.  It breaks abstraction,  the user should not have to deal with transports at all, rather mirror should do the right thing and work in a way that does not have this latency.

Thats why the CheckForMessages function is nice as it can reduce that latency

Ok,  we are going in circles now.   I fully understand the motivation: get rid of the extra latency.  My comment was replying to the suggestion of using threads.
Back to the PR: CheckForMessages may work, but it is not an elegant solution.  It breaks abstraction,  the user should not have to deal with transports at all, rather mirror should do the right thing and work in a way that does not have this latency.

Back to the PR: CheckForMessages may work, but it is not an elegant solution. It breaks abstraction, the user should not have to deal with transports at all, rather mirror should do the right thing and work in a way that does not have this latency.

there is no "right thing" for all games. I social game is fine getting updates once every 100ms, but a shooter needs updates asap
In order to minimize latency you'll need to run the "transport update" in an "early update" method before Update and FixedUpdate unity has an internal loop called  "early update"  but I dont know of a way to use it. One work around is to create a custom FixedUpdate, then you can call "transport update" then "custom fixedUpdate" from a Update which is early in execution order. Doing a custom FixedUpdate is not feasible or needed for all projects using mirror.

Back to the PR: CheckForMessages may work, but it is not an elegant solution. It breaks abstraction, the user should not have to deal with transports at all, rather mirror should do the right thing and work in a way that does not have this latency.

there is no "right thing" for all games. I social game is fine getting updates once every 100ms, but a shooter needs updates asap
In order to minimize latency you'll need to run the "transport update" in an "early update" method before Update and FixedUpdate unity has an internal loop called  "early update"  but I dont know of a way to use it. One work around is to create a custom FixedUpdate, then you can call "transport update" then "custom fixedUpdate" from a Update which is early in execution order. Doing a custom FixedUpdate is not feasible or needed for all projects using mirror.

maybe CheckForMessages is a bad name, what is is truely doing is "Invoke Message handlers on main thread"

maybe CheckForMessages is a bad name, what is is truely doing is "Invoke Message handlers on main thread"

authors: FakeByte James-Frowen SoftwareGuy dragonslaya84 paulpach vis2k


text:
fix(weaver): fix #706 find system dlls

fixes #706
while this does fix all known bad states from #706 there may be additional side effects. am still testing in windows, then will test osx/lin and confirm here

@c6burns can we merge yet?

I think we are good

:tada: This PR is included in version 3.4.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
KCP support

as the title indicates

It's a good idea, why not make it yourself? The transport interface is pretty simple to learn, just find a networking library to do the KCP part.

Telepathy will always use TCP.
I do have a work in progress KCP transport on my hard drive, maybe I will release it at some point.

authors: Katori sekkit vis2k


text:
Update index.html

Fixes #146

onsistent Labeling: Clear and uniform button labels.
Enhanced Usability: Easier for users to understand button functions.
Improved Aesthetics: A more professional and polished look.
Better Accessibility: Easier identification and use for all users.
Easier Maintenance: Simplified updates and modifications in the future.
Increased User Satisfaction: Higher likelihood of user engagement and retention.

Please mention your issue no.

#146

this is the issue number

Thank you.

Your welcome 😁

authors: AyushiTaralkar vishanurag

repo: vishanurag/Canvas-Editor


text:
几个代码问题：encoder和label

1、请问一下，我感觉这里self.gamma*weight*x 应该不用再乘以x吧？否则跟论文里面不太一样，就是Cattention模块，也就是论文中的modulation layer
https://github.com/vision4robotics/HiFT/blob/7f560e9ca1506f4b275f73e8c9ca4d34bec945ce/pysot/models/utile/tran.py#L32
2、这个标签生成方法是不是和SiamAPN用的是同一个？

非常感谢您的关注，我们的工作正在逐步更新中，我们仍在校对尚没有完全结束。
生成方式并不相同。APN目的是生成自适应锚框，并不是最终结果而HiFT是Anchor-free的方法，因此导致了标签生成方式的不同，APN关注区域更大。


text:
Responsive

Is this grid component responsive?

Hey Jerry,
 I'm thinking the answer is no but honestly I'm not sure what you're

asking there.  Do you mean can the columns be resized dynamically?  If so
there's nothing in it to do that.  It's really just css to easily make rows
and columns and it's in an element so that it can be put included in other
elements easily.  By all means let me know if there's something I can do to
make it better and I'll see what I can do.
Take Care,
Dustin
On Sat, Dec 5, 2015 at 8:08 PM, jerryf196 notifications@github.com wrote:

Is this grid component responsive?
—
Reply to this email directly or view it on GitHub
https://github.com/vision89/lazy-grid-style/issues/1.

Hey,
If you look at bootstrap or foundation's grid they have columns that you can specify for screens for ex:
In your component you have
col-6
Other grid systems options are like: col-s-6 (for small screens) (col-m-6) for medium screen
for example this: https://github.com/The5heepDev/iron-grid

I see, okay I think I can handle an update like that :-)  Just so you know
it is probably going to be over a week before I can update it.  I'm going
to be on the road all next week for work, and well, it's just a busy time
of year all together.  It's on my list though!
Thanks!
Dustin
On Sun, Dec 6, 2015 at 2:10 PM, jerryf196 notifications@github.com wrote:

Hey,
If you look at bootstrap or foundation's grid they have columns that you
can specify for screens for ex:
In your component you have
col-6
Other grid systems options are like: col-s-6 (for small screens) (col-m-6)
for medium screen
for example this: https://github.com/The5heepDev/iron-grid
—
Reply to this email directly or view it on GitHub
https://github.com/vision89/lazy-grid-style/issues/1#issuecomment-162337584
.

Maybe don't even bother with this component unless there is something or idea that is really different.
I found this one that is pretty good and tested quickly
https://customelements.io/vguillou/g-r-i-d/
Also this:
https://customelements.io/myfreeweb/mason-ry/

Okay, yes both of those look like they have more features you must need.
Good luck with the project you're using it for!
Take Care,
Dustin
On Mon, Dec 7, 2015 at 10:24 AM, jerryf196 notifications@github.com wrote:

Maybe don't even bother with this component unless there is something or
idea that is really different.
I found this one that is pretty good and tested quickly
https://customelements.io/vguillou/g-r-i-d/
Also this:
https://customelements.io/myfreeweb/mason-ry/
—
Reply to this email directly or view it on GitHub
https://github.com/vision89/lazy-grid-style/issues/1#issuecomment-162556412
.

I'm closing this since it does all I need it to do at the moment, and since Jerry is moving to a different grid system.


text:
Expect Status with done() isn't working

.expect(404, done) doesn't seem to be failing if the response is actually 200. Not sure if I'm doing something wrong, or if I've found a bug?
http://stackoverflow.com/questions/37729206/supertest-expect-not-asserting-status-codes-correctly

Works for me as expected. Simple test with an empty express app
    it('should handle an 404 response in expect callback', function (done) {
      var app = express();

      request(app)
      .get('/')
      .timeout(1)
      .expect(404, function (err) {
        err.should.be.an.instanceof(Error);
        done();
      });
    });

Thx for the reply @saintedlama yes your code seems to work, but the test passes if I add an expect(200,done). Like this:
		it('should handle an 404 response in expect callback', function (done) {
			request(app)
			.get('/doesntExist')
			.timeout(1)
			.expect(404, function (err) {
				console.log("yep")
				done();
			});
		});

		it('should handle an 404 response in expect callback', function (done) {
			request(app)
				.get('/doesntExist')
				.timeout(1)
				.expect(200, done);
		});

What does the timeout function do? Never saw that in supertest :dizzy_face:
Could you try to remove the timeout function calls and see what happens? Works on my machine (windows) like a charm without timeout calls

Lol sorry ill take it out! not sure what it does either, copied it from your example there :)
        it('should handle an 404 response in expect callback', function (done) {
            request(app)
            .get('/doesntExist')
            .expect(404, function (err) {
                console.log("yep")
                done();
            });
        });

        it('should handle an 404 response in expect callback', function (done) {
            request(app)
                .get('/doesntExist')
                .expect(200, done);
        });

So on windows, the second unit test produces an error?

This code
  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(404, function (err) {
        console.log("yep")
        done();
      });
  });

  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(200, done);
  });

produces that error
  1) request(app) should handle an 404 response in expect callback:
     Error: expected 200 "OK", got 404 "Not Found"
      at Test._assertStatus (C:\p\supertest\lib\test.js:259:12)
      at Test._assertFunction (C:\p\supertest\lib\test.js:274:11)
      at Test.assert (C:\p\supertest\lib\test.js:157:18)
      at Server.assert (C:\p\supertest\lib\test.js:131:12)
      at emitCloseNT (net.js:1549:8)
      at _combinedTickCallback (internal/process/next_tick.js:71:11)
      at process._tickCallback (internal/process/next_tick.js:98:9)

Btw: I'm using supertest 1.2

Thats the behavior I would expect!
From my package json
"supertest": "^1.2.0"

I'm on a mac, not sure exactly why this is happening :(

@dmolineuxcb  I just tested the above code on a mac and I am also getting the correct behavior, first test passes and second fails.
Please run this code snippet
var express = require('express');
var request = require('supertest');

describe('Test expect status code with done param', function() {
  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(404, function (err) {
        console.log("yep")
        done();
      });
  });

  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(200, done);
  });
});

var express = require('express');
var request = require('supertest');

fdescribe('Test expect status code with done param', function() {
  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(404, function (err) {
        console.log("yep")
        done();
      });
  });

  it('should handle an 404 response in expect callback', function (done) {
    var app = express();
    request(app)
      .get('/doesntExist')
      .expect(200, done);
  });
});
Dougs-MacBook-Pro:new-api dougmolineux$ npm test

> node-api@1.0.0 test /Users/dougmolineux/dev/new-api
> jasmine

Started
yep
.Connected correctly to database, listening to post 3000
.

Ran 2 of 243 specs
2 specs, 0 failures
Finished in 0.096 seconds
Dougs-MacBook-Pro:new-api dougmolineux$ ```

"Connected correctly to database, listening to post 3000" is coming from my app.js file.
I think it must be related to a version of something that I'm using, node v6.1.0 jasmine,
"jasmine": "^2.4.1",
"express": "^4.13.4",

Not a huge deal, I'll just refactor all the tests and add an end with a done() inside it. It will probably come up again I suspect :)

I'm running supertest 2.0.0 and copying the exact code pasted here: https://github.com/visionmedia/supertest/issues/345#issuecomment-229496425
Both tests pass, so it seems like a breaking change was introduced in 2.0.0, maybe i'm missing something in the docs, but i'm not sure what to do to test the status code

I have the same problem:
This doesn't fail:
request(app)
				.get('/labels')
				.expect(202, [validLabel, anotherValidLabel], done);

while this fails:
request(app)
				.get('/labels')
				.expect(202, [validLabel, anotherValidLabel])
				.end(err => err ? done.fail(err) : done());

Same here.

authors: bradwbradw dmolineuxcb mikelax pbalan rpadovani saintedlama

repo: visionmedia/supertest


text:
upgrade to node 10?

Should we upgrade to node 10?
i'm gladly to submit PR

Why not newest LTS version 12?

some of us still use node 10 :-) because of Node 8's End of Life

authors: ndabAP ryanhs


text:
Make Windows distro Qt/PuTTY (e.g qtssh) client independently releasable.

Is your feature request related to a problem?
I don't know how much effort this is or how often we might encounter the need for it but having the tiny qtssh.exe tool we use in the Windows distro independently releaseable would enable us to offer a quick download solution to problems like #18437 without having to cut a whole new VisIt release.

We use our qtssh on unix too, would you want that version separated as well?

We use our qtssh on unix too, would you want that version separated as well?

I think that could make some sense. Again, it depends on effort involved to accomodate (which I would rely upon you or others to guesstimate) and likelihood of need.
I'll note that @cyrush believes we may have encountered a similar situation with ALCF at ANL within the last few years too. So, that may be at least one other example of a case where this happened.
Another option could be to update PuTTY in VisIt at a higher frequency than we currently do...maybe every minor release (e.g. 3.2.0, 3.3.0, etc.). The downsides of that is that we won't necessarily have the confidence of its connectivity everywhere that we do with something we've used successfully for several years.

We use our qtssh on unix too, would you want that version separated as well?

Now that I think about it...are you saying all our unix/linux users are going to be hitting this issue as well?

Now that I think about it...are you saying all our unix/linux users are going to be hitting this issue as well?

Oh, I bet we're not using PuTTY on unix/linux, right. Just vanilla ssh there.

I don't recall the situations where qtssh is needed/used on unix. @brugger1 probably remembers.

I propose also we should keep VisIt's PuTTY version in sync with whatever version LLNL's LanDesk is using. That way, when LC tests connectivity with LanDesk supported tools, what VisIt is using will be included.

repo: visit-dav/visit


text:
Task/maguire7/triangle strip normals dev

Description
Resolves #3711
There are 4 significant changes. 3 of these changes take place in vtkVisItPolyDataNormalsFilter, and the other is within avtVertexNormalsFilter:

vtkVisItPolyDataNormalsFilter:

Computing point normals with and without splitting completely ignored (and therefore removed) triangle strips. I've added in logic to decompose the strips into triangles and compute normals for them. This is similar to how strips are handled in the original vtk filter, but we're still handling cases differently.

Computing cell normals had previously just set all triangle strip normals to (0, 0, 1). I've added in logic to decompose strips and compute proper normals here as well.

vtkVertexNormalsFilter:

I removed old logic that prevented polys with triangle strips from having their normals computed.

Type of change

[x] Bug fix
[ ] New feature
[ ] New Documentation
[ ] Other (please describe below)

How Has This Been Tested?
I've manually tested several datasets and looked at all normals cases. I've re-run the test suite, and I've added a new test and dataset (from Kathleen; thanks for providing that!).
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added any new baselines to the repo
[x] I have assigned reviewers (see VisIt's PR procedures for more information).

There's seems to be an issue with picking from a vector plot after these changes (which is very specific); I'm investigating this now.
I also think I need to tell VisIt that zones have been split after decomposing triangle strips.

It looks like screen picking a vector plot uses a different path than usual, which seems odd. It still relies on avtPickByNode/Zone, but it doesn't appear to cast a ray through the dataset to find it's zone/node ID (at least not through the avtLocateQuery like picking other plots). @biagas does this ring any bells to you?

Is the intersection being determined by VisWindow::Pick?

Is the intersection being determined by VisWindow::Pick?

That's a great question (I forgot all about that pathway). I'll look more into this next week. Thanks!

Okay, I've spent some time tracing down this funky Pick error with vector plots, and I'm convinced that we're doing something odd with these glyphs (maybe some kind of optimization?) that doesn't play nice if you deep copy the dataset of the glyphs. Even using VTK's standard PolyDataNormalsFilter results in the same odd behavior with Picking. At any rate, removing the normals filter from the vector glyphs produces no noticeable changes (but there are some very minor pixel diffs), so I've just removed it rather than venturing further down this rabbit hole. It might also be worth noting that our tensor plot doesn't use the normals filter either.
Noteworthy changes:

Removed normals filter from vector plot (explained above).
Rebased several tests using vector plots (all very minor pixel diffs).
Added logic to tell VisIt when cells have been split due to decomposing triangle strips.


text:
Custom class breaks html tag

the pre-tag will be torn apart like this, when adding custom classes to pre and p:

How it should look like:

Markdown config:
 'styles' => [         'default' => [             'pre' => 'border overflow-auto p-3',             'p' => 'mb-4',         ],     ],

Good catch!
It's related, as we don't check for any allowed characters after the classname.
Right now, the class replacement does work via a simple str_replace. It will be solved, by using a stable regex expression, as this can resolve #10 .

authors: jonassiewertsen juliawarnke

repo: visuellverstehen/markdown-to-html


text:
Inserting a new record: Row gets created in database but values do not get submitted

So after I click the submit button a new row is created in my database with a userID but the username does not get submitted to the database. Currently my loginInfo table I am submitting two has 3 columns: userID (auto generated and incremented), username, and password. I believe my error is in the newuser.php file I am unsure of what to do in it.
Empty

Also in the same file under scripts
    $.fn.editable.defaults.mode = 'inline';

//init editables
$('.myeditable').editable({
    url: 'post.php' //this url will not be used for creating new user, it is only for update
});

//make username required
$('#new_username').editable('option', 'validate', function(v) {
    if(!v) return 'Required field name!';
});

//automatically show next editable
$('.myeditable').on('save.newuser', function(){
    var that = this;
    setTimeout(function() {
        $(that).closest('tr').next().find('.myeditable').editable('show');
    }, 200);
});

$('#save-btn').click(function() {
    $('.myeditable').editable('submit', {
        url: 'newuser.php',
        ajaxOptions: {
            type: 'POST',
            dataType: 'json' //assuming json response
        },
        success: function(data, config) {
            if(data && data.id) {  //record created, response like {"id": 2}
                //set pk
                $(this).editable('option', 'pk', data.id);
                //remove unsaved class
                $(this).removeClass('editable-unsaved');
                //show messages
                var msg = 'New user created! Now editables submit individually.';
                $('#msg').addClass('alert-success').removeClass('alert-error').html(msg).show();
                $('#save-btn').hide();
                $(this).off('save.newuser');
            } else if(data && data.errors){
                //server-side validation error, response like {"errors": {"username": "username already exist"} }
                config.error.call(this, data.errors);
            }
        },
        error: function(errors) {
            var msg = '';
            if(errors && errors.responseText) { //ajax error, errors = xhr object
                msg = errors.responseText;
            } else { //validation error (client-side or server-side)
                $.each(errors, function(k, v) { msg += k+": "+v+"
"; });
            }
            $('#msg').removeClass('alert-success').addClass('alert-error').html(msg).show();
        }
    });
});

Post.php
include('connect.php);
sleep(1);
$pk = $_post['pk'];
$un=$_POST['name'];
$value1 = $_POST['value'];

if(!empty($value1)) {

    $sql =("UPDATE loginInfo
            SET $un=$value1
            WHERE userID='$pk'");
    mysqli_query($con, $sql);

    //here, for debug reason we just return dump of $_POST, you will see result in browser console
    print_r($_POST);
}
else {
    header('HTTP/1.0 400 Bad Request', true, 400);
    echo "This field is required!";
}

newuser.php
 $pk = $_post['pk'];
$un=$_POST['name'];
$value1 = $_POST['value'];

try {

    $sql =("INSERT INTO loginInfo(username,password)
            VALUES ('a','b')");
    mysqli_query($con, $sql);

}     catch (Exception $e) {
    print($e->__toString());
}

?>
In my firefox under the net console I see this output which is the value I entered into the name textbox
Parameters
name
testing

Source
name=testing

Unfortunately, due to this project being supported by volunteers we cannot provide user support at this time. Please try a site like Stack Overflow:  http://stackoverflow.com/questions/tagged/x-editable
Thank you.

repo: vitalets/x-editable


text:
Added protobuf payload converter tests

Changes being made
Added protobuf payload converter tests. They should simplify work on #117

Codecov Report

Merging #119 (19db3ba) into main (0015457) will increase coverage by 1.33%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #119      +/-   ##
==========================================
+ Coverage   36.32%   37.65%   +1.33%
==========================================
  Files         116      116
  Lines        4127     4127
==========================================
+ Hits         1499     1554      +55
+ Misses       2628     2573      -55

Files Changed
Coverage Δ

...io/temporal/protobuf/ScalapbPayloadConverter.scala
45.45% <100.00%> (+45.45%)
:arrow_up:

authors: codecov-commenter vitaliihonta

repo: vitaliihonta/zio-temporal


text:
Astro 2.0.x has not been supported yet?

Hi, developers. Thank you for this awesome astro integration.
I tried to configure my project that depends on astro@2.0.6 to integrate this pwa plugin , but the following error was occurred.
02:47:00 PM [astro] Unable to load /workspaces/takpedia/astro.config.mjs

 error   Cannot read properties of undefined (reading 'default')
  File:
    /workspaces/takpedia/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52400:9
  Code:
    52399 |         const initModule = new AsyncFunction(`global`, ssrModuleExportsKey, ssrImportMetaKey, ssrImportKey, ssrDynamicImportKey, ssrExportAllKey, '"use strict";' + result.code + `\n//# sourceURL=${mod.url}`);
    > 52400 |         await initModule(context.global, ssrModule, ssrImportMeta, ssrImport, ssrDynamicImport, ssrExportAll);
            |         ^
      52401 |     }
      52402 |     catch (e) {
      52403 |         mod.ssrError = e;
  Stacktrace:
TypeError: Cannot read properties of undefined (reading 'default')
    at eval (/workspaces/takpedia/astro.config.mjs:21:172)
    at async instantiateModule (file:///workspaces/takpedia/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52400:9)

After that, I also tried to reproduce it with creating new clean project with npm create astro command.  Same error was occurred at the project too.
The clean project's astro.config.mjs is simply the below.  (They were generated by create astro and were added only configurations for  pwa integration.)
{
	"name": "nebulous-neutron",
	"type": "module",
	"version": "0.0.1",
	"scripts": {
		"dev": "astro dev",
		"start": "astro dev",
		"build": "astro build",
		"preview": "astro preview",
		"astro": "astro"
	},
	"dependencies": {
		"astro": "^2.0.14"
	},
	"devDependencies": {
		"@vite-pwa/astro": "^0.0.1"
	}
}

import AstroPWA from "@vite-pwa/astro"

// https://astro.build/config
export default defineConfig({
    integrations: [
        AstroPWA()
    ]
});

Sorry for my hasty...  #5 will solve this.
Thank you.

@NewGyu released v0.0.2

authors: NewGyu userquin

repo: vite-pwa/astro


text:
vite fails with https dependencies installed with pnpm9

Describe the bug
Since pnpm upgrade from v8 to v9, dependencies files can have # in their name, and vite fails to compile them in some cases. It seems to occurs when a dependency is declared with the repo url (neither official npm package nor github project) and this dependency import another one also declared with its repo url.
Here is the same issue as #16597, but with a minimal repo to reproduce the pb.
Reproduction
https://github.com/dcaillibaud/bug-vite-pnpm9
Steps to reproduce
git clone https://github.com/dcaillibaud/bug-vite-pnpm9.git
cd bug-vite-pnpm9
npx pnpm@9 install
vite build

You can test the build with ./test.sh 8 or ./test.sh 9, or just install dependencies with pnpm 8 (./install.sh 8) or pnpm 9 (./install.sh 9) then try vite build --debug or vite
System Info
System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 14.33 GB / 31.09 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.5.1 - /usr/bin/node
    npm: 10.7.0 - /usr/bin/npm
    pnpm: 8.15.8 - /usr/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.88
    Chromium: 126.0.6478.182
  npmPackages:
    vite: ^5.3.5 => 5.3.5

### Used Package Manager

pnpm

### Logs

<details>
<summary>main branch with pnpm 9, build KO</summary>

```shell
error during build:
[vite]: Rollup failed to resolve import "sesajstools/dom" from "/home/sesamath/projets/git/bug-vite-pnpm9/node_modules/.pnpm/instrumenpoche@git+https+++git.sesamath.net+sesamath+instrumenpoche.git#26796a8b1fab14a77a463309abdb887baf3678bd/node_modules/instrumenpoche/src/iepLoadPromise.js".

It's ok with pnpm 8 (try ./test.sh 8) or in branch sampleOk
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It looks like a duplicate of https://github.com/vitejs/vite/issues/17459

authors: dcaillibaud hi-ogawa

repo: vitejs/vite


text:
Error when build after upgrade

Describe the bug
I'm trying to migrate from "vite 2.0.0-beta.15" to "vite v2.0.1". Before everything is work fine but after upgrade vite is throwing error when build but not when development. And seems this issues is related to this issues.
System Info

vite version: 2.0.1
Operating System: Windows 10
Node version: v14.15.5
Package manager (npm/yarn/pnpm) and version: yarn 1.22.10

Logs (Optional if provided reproduction)
https://pastebin.com/Dz2vFq5e

There are many many changes between beta.15 and 2.0.1 so this is not enough information for us to do anything.

Here the minimal repository. Mainly the issues just come from "@ant-design/charts"

I'm not sure why it was even working in beta.15, since @antv seems to have a LOT of non-existent imports from empty files, e.g. line 34 here is importing ISystem from this empty file.
This is expected to fail since it's just broken code.