Not able to log in to rancher server setup after a while.

Rancher server version - 2.0 Build from master
Steps that lead to the problem:
Had a setup with 2 clusters.
Both clusters had few workloads deployed in them.
After a while of having the setup running , now I am not able to log in to the setup at all.
Following is the last set of logs:
2018-03-20 21:19:33.810228 I | mvcc: finished scheduled compaction at 29975 (took 1.941819ms)
E0320 21:21:29.468719       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
E0320 21:21:44.399156       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
2018-03-20 21:24:33.811933 I | mvcc: store.index: compact 30503
2018-03-20 21:24:33.815752 I | mvcc: finished scheduled compaction at 30503 (took 2.09759ms)
E0320 21:26:40.779623       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-03-20 21:29:33.817066 I | mvcc: store.index: compact 31033
2018-03-20 21:29:33.820454 I | mvcc: finished scheduled compaction at 31033 (took 1.758251ms)
2018-03-20 21:34:33.822058 I | mvcc: store.index: compact 31568
2018-03-20 21:34:33.825408 I | mvcc: finished scheduled compaction at 31568 (took 1.799657ms)
E0320 21:35:20.473402       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-03-20 21:39:33.827000 I | mvcc: store.index: compact 32100
2018-03-20 21:39:33.830463 I | mvcc: finished scheduled compaction at 32100 (took 1.820407ms)
E0320 21:40:21.783697       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-03-20 21:44:33.831809 I | mvcc: store.index: compact 32633
2018-03-20 21:44:33.835282 I | mvcc: finished scheduled compaction at 32633 (took 1.744703ms)

E0320 21:48:52.027489       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
E0320 21:48:59.453243       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
E0320 21:49:15.014216       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
E0320 21:49:15.020315       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018-03-20 21:49:33.836993 I | mvcc: store.index: compact 33156
2018-03-20 21:49:33.840389 I | mvcc: finished scheduled compaction at 33156 (took 1.695351ms)
2018/03/20 21:49:52 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:50:23 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:23 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:24 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:24 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:25 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:25 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:26 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:26 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:27 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:27 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:27 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:27 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:28 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:28 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:28 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:28 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:29 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:29 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:30 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:30 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:31 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:31 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:32 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:32 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:33 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:33 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:33 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:33 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:34 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:34 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:35 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:35 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:36 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:36 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:37 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:37 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:38 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:38 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:38 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:38 [ERROR] Unknown error: websocket: close sent
2018/03/20 21:50:39 [ERROR] Error during subscribe websocket: close sent
2018/03/20 21:50:39 [ERROR] Unknown error: websocket: close sent
E0320 21:50:40.017690       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46c7af9a0), encoder:(*versioning.codec)(0xc425608510), buf:(*bytes.Buffer)(0xc466e1caf0)})
E0320 21:50:40.029511       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4571eb260), encoder:(*versioning.codec)(0xc436bfc480), buf:(*bytes.Buffer)(0xc45fdeaa80)})
E0320 21:50:40.033345       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46c7afb30), encoder:(*versioning.codec)(0xc425608ea0), buf:(*bytes.Buffer)(0xc466e1de30)})
E0320 21:50:40.037475       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46c7afb50), encoder:(*versioning.codec)(0xc4256090e0), buf:(*bytes.Buffer)(0xc45cfd80e0)})
E0320 21:50:40.042728       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46c7afb70), encoder:(*versioning.codec)(0xc425609290), buf:(*bytes.Buffer)(0xc45cfd8380)})
E0320 21:50:40.045835       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4571eb4f0), encoder:(*versioning.codec)(0xc436bfcb40), buf:(*bytes.Buffer)(0xc4576d0150)})
E0320 21:50:40.050534       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4571eb510), encoder:(*versioning.codec)(0xc436bfccf0), buf:(*bytes.Buffer)(0xc4576d0380)})
E0320 21:50:40.062067       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4571eb5f0), encoder:(*versioning.codec)(0xc436bfd200), buf:(*bytes.Buffer)(0xc4576d0d90)})
E0320 21:50:40.572256       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45d6eab30), encoder:(*versioning.codec)(0xc4492e1b90), buf:(*bytes.Buffer)(0xc46439f2d0)})
E0320 21:50:40.573970       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc466865498), encoder:(*versioning.codec)(0xc451738870), buf:(*bytes.Buffer)(0xc46496dc00)})
E0320 21:50:40.583122       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45d6eab80), encoder:(*versioning.codec)(0xc4492e1dd0), buf:(*bytes.Buffer)(0xc46439f730)})
E0320 21:50:40.609956       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45d6eac28), encoder:(*versioning.codec)(0xc4657a2630), buf:(*bytes.Buffer)(0xc4664562a0)})
E0320 21:50:40.617099       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45d6eac40), encoder:(*versioning.codec)(0xc4657a27e0), buf:(*bytes.Buffer)(0xc466456540)})
E0320 21:50:42.998336       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9c900), encoder:(*versioning.codec)(0xc43f43d440), buf:(*bytes.Buffer)(0xc455755c00)})
E0320 21:50:43.001217       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9c920), encoder:(*versioning.codec)(0xc43f43d680), buf:(*bytes.Buffer)(0xc455755ea0)})
E0320 21:50:43.004030       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dba8), encoder:(*versioning.codec)(0xc44956b440), buf:(*bytes.Buffer)(0xc461f7c460)})
E0320 21:50:43.005229       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dbc0), encoder:(*versioning.codec)(0xc44956b5f0), buf:(*bytes.Buffer)(0xc461f7c700)})
E0320 21:50:43.006589       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9c970), encoder:(*versioning.codec)(0xc43f43d8c0), buf:(*bytes.Buffer)(0xc45d9242a0)})
E0320 21:50:43.008315       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dbe8), encoder:(*versioning.codec)(0xc44956b8c0), buf:(*bytes.Buffer)(0xc461f7ca80)})
E0320 21:50:43.009662       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dc00), encoder:(*versioning.codec)(0xc44956ba70), buf:(*bytes.Buffer)(0xc461f7cd20)})
E0320 21:50:43.023830       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9ca08), encoder:(*versioning.codec)(0xc43f43def0), buf:(*bytes.Buffer)(0xc45d924b60)})
E0320 21:50:43.024829       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9ca28), encoder:(*versioning.codec)(0xc45ae6e1b0), buf:(*bytes.Buffer)(0xc45d924e00)})
E0320 21:50:43.026184       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9ca48), encoder:(*versioning.codec)(0xc45ae6e3f0), buf:(*bytes.Buffer)(0xc45d925110)})
E0320 21:50:43.028228       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9ca68), encoder:(*versioning.codec)(0xc45ae6e630), buf:(*bytes.Buffer)(0xc45d9253b0)})
E0320 21:50:43.038713       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dc80), encoder:(*versioning.codec)(0xc44b3f4000), buf:(*bytes.Buffer)(0xc461f7d2d0)})
E0320 21:50:43.041177       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9cb08), encoder:(*versioning.codec)(0xc45ae6ee10), buf:(*bytes.Buffer)(0xc45d925ab0)})
E0320 21:50:43.042417       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9cb28), encoder:(*versioning.codec)(0xc45ae6f050), buf:(*bytes.Buffer)(0xc45d925d50)})
E0320 21:50:43.045722       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9cb60), encoder:(*versioning.codec)(0xc45ae6f5f0), buf:(*bytes.Buffer)(0xc464aee5b0)})
E0320 21:50:43.046924       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc45cd9cb78), encoder:(*versioning.codec)(0xc45ae6f7a0), buf:(*bytes.Buffer)(0xc464aee850)})
E0320 21:50:43.052841       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc469e4dcb0), encoder:(*versioning.codec)(0xc44b3f45a0), buf:(*bytes.Buffer)(0xc461f7d880)})
E0320 21:50:56.448213       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4698ca0d0), encoder:(*versioning.codec)(0xc4698de1b0), buf:(*bytes.Buffer)(0xc45b8a5f80)})
E0320 21:50:56.449828       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4698ca0f0), encoder:(*versioning.codec)(0xc4698de360), buf:(*bytes.Buffer)(0xc4698f61c0)})
E0320 21:50:56.451660       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46f0c5100), encoder:(*versioning.codec)(0xc43df7bcb0), buf:(*bytes.Buffer)(0xc45b8828c0)})
E0320 21:50:56.453924       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46f0c5118), encoder:(*versioning.codec)(0xc43df7be60), buf:(*bytes.Buffer)(0xc45b882b60)})
E0320 21:50:56.455627       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc46f0c5168), encoder:(*versioning.codec)(0xc4611e4120), buf:(*bytes.Buffer)(0xc45b882e70)})
E0320 21:50:57.900154       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d220d8), encoder:(*versioning.codec)(0xc4491d8480), buf:(*bytes.Buffer)(0xc46bbcebd0)})
E0320 21:50:57.902835       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba80a8), encoder:(*versioning.codec)(0xc45e35e120), buf:(*bytes.Buffer)(0xc46bc74690)})
E0320 21:51:03.021437       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba9130), encoder:(*versioning.codec)(0xc45a6d8e10), buf:(*bytes.Buffer)(0xc46ad013b0)})
E0320 21:51:03.027855       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba9150), encoder:(*versioning.codec)(0xc45a6d9050), buf:(*bytes.Buffer)(0xc46ad01650)})
E0320 21:51:03.031081       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d22fb0), encoder:(*versioning.codec)(0xc42f926fc0), buf:(*bytes.Buffer)(0xc46f0416c0)})
E0320 21:51:03.032516       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d22fd0), encoder:(*versioning.codec)(0xc42f927200), buf:(*bytes.Buffer)(0xc46f041960)})
E0320 21:51:09.445586       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d23f88), encoder:(*versioning.codec)(0xc45f83b170), buf:(*bytes.Buffer)(0xc46213fab0)})
E0320 21:51:09.447995       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba9f00), encoder:(*versioning.codec)(0xc467712ea0), buf:(*bytes.Buffer)(0xc452f38bd0)})
E0320 21:51:09.453245       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba9f20), encoder:(*versioning.codec)(0xc467713050), buf:(*bytes.Buffer)(0xc452f39030)})
E0320 21:51:09.460244       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d23ff8), encoder:(*versioning.codec)(0xc45f83b950), buf:(*bytes.Buffer)(0xc449bf4770)})
E0320 21:51:09.462517       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4517860c8), encoder:(*versioning.codec)(0xc45cf322d0), buf:(*bytes.Buffer)(0xc449bf4d90)})
E0320 21:51:09.466251       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc459ba9fe8), encoder:(*versioning.codec)(0xc467713710), buf:(*bytes.Buffer)(0xc452f39810)})
E0320 21:51:09.467564       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d70020), encoder:(*versioning.codec)(0xc467713950), buf:(*bytes.Buffer)(0xc452f39ab0)})
E0320 21:51:09.468760       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d70048), encoder:(*versioning.codec)(0xc467713b90), buf:(*bytes.Buffer)(0xc452f39dc0)})
E0320 21:51:09.470000       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d70068), encoder:(*versioning.codec)(0xc467713dd0), buf:(*bytes.Buffer)(0xc451b3e070)})
E0320 21:51:09.471475       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d70088), encoder:(*versioning.codec)(0xc45f516360), buf:(*bytes.Buffer)(0xc451b3e310)})
E0320 21:51:09.472565       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d700a8), encoder:(*versioning.codec)(0xc45f516750), buf:(*bytes.Buffer)(0xc451b3e690)})
E0320 21:51:09.474605       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc451786188), encoder:(*versioning.codec)(0xc45cf32870), buf:(*bytes.Buffer)(0xc449bf57a0)})
E0320 21:51:09.478197       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc427d70128), encoder:(*versioning.codec)(0xc45f516990), buf:(*bytes.Buffer)(0xc451b3ea80)})
E0320 21:51:30.988075       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4264d1d38), encoder:(*versioning.codec)(0xc423931c20), buf:(*bytes.Buffer)(0xc43a64d420)})
E0320 21:51:49.428718       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc440c9ded8), encoder:(*versioning.codec)(0xc4605719e0), buf:(*bytes.Buffer)(0xc44218c460)})
E0320 21:51:49.430836       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc440c9def8), encoder:(*versioning.codec)(0xc4545f0090), buf:(*bytes.Buffer)(0xc44218c770)})
E0320 21:51:49.433079       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc440c9df20), encoder:(*versioning.codec)(0xc4545f0630), buf:(*bytes.Buffer)(0xc44218ca10)})
E0320 21:51:49.434356       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc440c9df40), encoder:(*versioning.codec)(0xc4545f0990), buf:(*bytes.Buffer)(0xc44218ccb0)})
E0320 21:52:13.035678       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc452d53b50), encoder:(*versioning.codec)(0xc453dabe60), buf:(*bytes.Buffer)(0xc44d70b730)})
E0320 21:52:13.895205       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489162a0), encoder:(*versioning.codec)(0xc42608c870), buf:(*bytes.Buffer)(0xc431b2b420)})
E0320 21:52:13.897401       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489162c0), encoder:(*versioning.codec)(0xc42608cbd0), buf:(*bytes.Buffer)(0xc431b2b730)})
E0320 21:52:13.924783       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc455717550), encoder:(*versioning.codec)(0xc445786630), buf:(*bytes.Buffer)(0xc450043dc0)})
E0320 21:52:20.610740       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c530), encoder:(*versioning.codec)(0xc44b04d3b0), buf:(*bytes.Buffer)(0xc4479905b0)})
2018/03/20 21:52:20 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
E0320 21:52:20.711703       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c890), encoder:(*versioning.codec)(0xc43e169560), buf:(*bytes.Buffer)(0xc43453c1c0)})
E0320 21:52:20.713867       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c8e0), encoder:(*versioning.codec)(0xc43e1697a0), buf:(*bytes.Buffer)(0xc43453c4d0)})
E0320 21:52:20.714020       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917420), encoder:(*versioning.codec)(0xc43e1698c0), buf:(*bytes.Buffer)(0xc43453c700)})
E0320 21:52:20.716494       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917440), encoder:(*versioning.codec)(0xc44d693dd0), buf:(*bytes.Buffer)(0xc4465151f0)})
E0320 21:52:20.730880       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c8f8), encoder:(*versioning.codec)(0xc43e169a70), buf:(*bytes.Buffer)(0xc43453c9a0)})
E0320 21:52:20.734826       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489174c0), encoder:(*versioning.codec)(0xc448976870), buf:(*bytes.Buffer)(0xc4465158f0)})
E0320 21:52:20.735646       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57ca48), encoder:(*versioning.codec)(0xc43ec685a0), buf:(*bytes.Buffer)(0xc44f7a4540)})
E0320 21:52:20.735711       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489175f8), encoder:(*versioning.codec)(0xc448977ef0), buf:(*bytes.Buffer)(0xc4327191f0)})
E0320 21:52:20.736706       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917700), encoder:(*versioning.codec)(0xc436e581b0), buf:(*bytes.Buffer)(0xc45103e460)})
E0320 21:52:20.736904       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cc78), encoder:(*versioning.codec)(0xc4308fd200), buf:(*bytes.Buffer)(0xc42c814380)})
E0320 21:52:20.737120       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cbc0), encoder:(*versioning.codec)(0xc4308fcb40), buf:(*bytes.Buffer)(0xc44f7a5b20)})
E0320 21:52:20.737392       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cb68), encoder:(*versioning.codec)(0xc43d317dd0), buf:(*bytes.Buffer)(0xc44f7a55e0)})
E0320 21:52:20.738214       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917618), encoder:(*versioning.codec)(0xc437d44990), buf:(*bytes.Buffer)(0xc432719420)})
E0320 21:52:20.738246       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57ccc8), encoder:(*versioning.codec)(0xc45057a750), buf:(*bytes.Buffer)(0xc42c8145b0)})
E0320 21:52:20.738615       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cac0), encoder:(*versioning.codec)(0xc43d316480), buf:(*bytes.Buffer)(0xc44f7a4d90)})
E0320 21:52:20.738758       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489175d0), encoder:(*versioning.codec)(0xc448977d40), buf:(*bytes.Buffer)(0xc432718fc0)})
E0320 21:52:20.739062       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57ca90), encoder:(*versioning.codec)(0xc43ec687e0), buf:(*bytes.Buffer)(0xc44f7a47e0)})
E0320 21:52:20.739250       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57ca20), encoder:(*versioning.codec)(0xc43ec683f0), buf:(*bytes.Buffer)(0xc44f7a4310)})
E0320 21:52:20.739463       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917550), encoder:(*versioning.codec)(0xc4489777a0), buf:(*bytes.Buffer)(0xc4327189a0)})
E0320 21:52:20.739597       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c9e8), encoder:(*versioning.codec)(0xc43ec68090), buf:(*bytes.Buffer)(0xc43453ddc0)})
E0320 21:52:20.739998       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917520), encoder:(*versioning.codec)(0xc448977200), buf:(*bytes.Buffer)(0xc4327184d0)})
E0320 21:52:20.740067       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c9c8), encoder:(*versioning.codec)(0xc44f273b90), buf:(*bytes.Buffer)(0xc43453db20)})
E0320 21:52:20.740268       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c9a0), encoder:(*versioning.codec)(0xc44f2738c0), buf:(*bytes.Buffer)(0xc43453d8f0)})
E0320 21:52:20.740594       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489174a0), encoder:(*versioning.codec)(0xc4489766c0), buf:(*bytes.Buffer)(0xc4465156c0)})
E0320 21:52:20.740654       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4489174e0), encoder:(*versioning.codec)(0xc448976a20), buf:(*bytes.Buffer)(0xc446515b90)})
E0320 21:52:20.740895       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917460), encoder:(*versioning.codec)(0xc448976510), buf:(*bytes.Buffer)(0xc446515490)})
E0320 21:52:20.741205       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c968), encoder:(*versioning.codec)(0xc44f273320), buf:(*bytes.Buffer)(0xc43453d2d0)})
E0320 21:52:20.741480       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c948), encoder:(*versioning.codec)(0xc43e169dd0), buf:(*bytes.Buffer)(0xc43453ce00)})
E0320 21:52:20.741811       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57c928), encoder:(*versioning.codec)(0xc43e169c20), buf:(*bytes.Buffer)(0xc43453cbd0)})
E0320 21:52:20.759294       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917900), encoder:(*versioning.codec)(0xc44e6d3680), buf:(*bytes.Buffer)(0xc4559ef110)})
E0320 21:52:20.760497       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cdd8), encoder:(*versioning.codec)(0xc45057bc20), buf:(*bytes.Buffer)(0xc4586b2690)})
E0320 21:52:20.760600       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc448917960), encoder:(*versioning.codec)(0xc438960090), buf:(*bytes.Buffer)(0xc4559efc70)})
E0320 21:52:20.760685       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cda0), encoder:(*versioning.codec)(0xc45057b680), buf:(*bytes.Buffer)(0xc4586b20e0)})
E0320 21:52:20.761414       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc42c57cd78), encoder:(*versioning.codec)(0xc45057b3b0), buf:(*bytes.Buffer)(0xc42c815ea0)})
E0320 21:52:20.762071       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
2018-03-20 21:54:33.843535 I | mvcc: store.index: compact 33605
2018-03-20 21:54:33.847010 I | mvcc: finished scheduled compaction at 33605 (took 1.708607ms)
2018/03/20 21:54:54 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:55:10 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:55:57 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:56:41 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
E0320 21:57:29.429595       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:57:45 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 21:57:45 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
E0320 21:59:17.003221       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018-03-20 21:59:33.848800 I | mvcc: store.index: compact 33919
2018-03-20 21:59:33.851990 I | mvcc: finished scheduled compaction at 33919 (took 1.384585ms)
2018/03/20 21:59:45 [INFO] Running cluster events cleanup
2018/03/20 21:59:45 [INFO] Done running cluster events cleanup
E0320 22:01:20.998024       1 generic_controller.go:200] ClusterController cluster-hs2pl [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
E0320 22:01:38.032587       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:01:57 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
E0320 22:03:00.747707       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-03-20 22:04:33.854344 I | mvcc: store.index: compact 34233
2018-03-20 22:04:33.857778 I | mvcc: finished scheduled compaction at 34233 (took 1.727848ms)
E0320 22:04:53.716594       1 generic_controller.go:200] ClusterController cluster-hs2pl [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
E0320 22:05:14.708093       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw3]: Operation cannot be fulfilled on nodes.management.cattle.io "m-qch72": the object has been modified; please apply your changes to the latest version and try again
E0320 22:05:21.861439       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:05:21 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again

2018/03/20 22:05:47 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
E0320 22:06:13.703610       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again

E0320 22:06:57.714571       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw2]: Operation cannot be fulfilled on nodes.management.cattle.io "m-b5l8j": the object has been modified; please apply your changes to the latest version and try again

2018-03-20 22:09:33.859586 I | mvcc: store.index: compact 34539
2018-03-20 22:09:33.862635 I | mvcc: finished scheduled compaction at 34539 (took 1.419204ms)
E0320 22:11:37.466149       1 generic_controller.go:200] ClusterController cluster-hs2pl [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:12:26 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:13:58 [INFO] Failed to update cluster [cluster-hs2pl] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-hs2pl": the object has been modified; please apply your changes to the latest version and try again
E0320 22:13:58.067101       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:13:58 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
E0320 22:13:58.070436       1 generic_controller.go:200] NodeController cluster-vdcrx/_machine_all_ [machinesSyncer] failed with : Failed to update machine for node [sanw2]: Operation cannot be fulfilled on nodes.management.cattle.io "m-b5l8j": the object has been modified; please apply your changes to the latest version and try again
E0320 22:13:58.100526       1 generic_controller.go:200] ClusterController cluster-vdcrx [cluster-stats] failed with : Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018/03/20 22:14:29 [INFO] Failed to update cluster [cluster-vdcrx] Operation cannot be fulfilled on clusters.management.cattle.io "cluster-vdcrx": the object has been modified; please apply your changes to the latest version and try again
2018-03-20 22:14:33.864985 I | mvcc: store.index: compact 34846
2018-03-20 22:14:33.868016 I | mvcc: finished scheduled compaction at 34846 (took 1.490009ms)

@cjellick mentioned that he had debugged a similar issue on one of the demo instances
His analysis:
specfically, when you tried to log in, the request to login would hang. obviously, suspected some deadlock in the auth code. i got a goroutine dump and started investigating.
Ultimately traced it back to a number of goroutines stuck on `github.com/rancher/rancher/vendor/golang.org/x/net/http2.(*ClientConn).awaitOpenSlotForRequest(0xc4369ee820, 0xc458c9eb00, 0x0, 0x0)` *- inclduing the request to login.
Dug deeper and here is what i think is happening: the connection the k8s go-client makes to k8s seems to be  a _single shared_ HTTP2 connection, which it then multiplexes "streams" on. the net/http2 library appears to default to this single-http2-conn paradigm for all HTTPS connections and to connection pooling and http1.1 for all non-http connections.
so, we are HTTPS, which appears to mean a SINGLE connection for all of the requests from rancher code to k8s by way of the k8s client. (see https://github.com/golang/net/blob/master/http2/configure_transport.go#L74-L80 for the logic that enforces a single connection when using http2)
when a request is made while that limit has been reached, the request just _waits forever_.
I think we are hitting that limit by doing ~1000 watches. and then all further requests hang or are extremely delayed as they contend for just a few open streams
I was able to reproduce this behavior by spinning up rancher/server:preview and opening 7 or 8 browser windows to it
If in order to do `/subscribe`, you are doing a watch per type and a watch == 1 long lived request to k8s, its ~conceivable~ very likely that we are doing 1000 watches once about 8-10 browsers are pointed at rancher/server, right?
I then discover an env var in the net/http library called `DISABLE_HTTP2` that does what its name implies. when i did `docker run -d -p 443:443 -p 80:80 -e DISABLE_HTTP2=true rancher/server:preview`, i easily got past the 7-8 browser window limit that i previously hit

Tried to stop and start the rancher-server to see if it would recover from this state.
This did not help either.
Even after this , not able to log into the server.

taking myself off this one


Direct Card Payments API Update

Feature Request
We've changed the API for direct card payments, which must be reflected across SDKs. The documentation can be found here:
https://38fb25f8.api-docs-182.pages.dev/deposit/1.0/#card-payment-integration-2
Also in swagger format:
https://38fb25f8.api-docs-182.pages.dev/swagger/1.0/
@atanasantonov, please contact me at<EMAIL_ADDRESS>so I can provide you test credentials and setup for this, also if you have any questions.
@alexbhr please confirm, thanks.

@Kantonov could you give some hint please if possible what is changed?

@atanasantonov yes. Up until now there was one card request containing card data. This changes as follows:

There is one normal deposit request, without card data, send to a new endpoint, new path.
The responded URL is the one where another request must be sent containing only card data.

To the SDK users this should be implemented seamlessly. So they can provide one payload (set of parameters), and we make those 2 requests happen in the background. At the end just returning the final result, the response from the second request, given everything went smoothly without errors.

@atanasantonov can this be merged?

@alexbhr i have dropped an email on 27.07 becasue there was issues and as per your email from 06.08 waiting for @Kantonov to be back from vacation to bring light.  The email as follows:
Notes to mention:

There is little mismatch between the documentation and Swagger for Deposit Card - In Swagger the Deposit Card Flow body contains the card data.
No matter what card is used (Test Cards V1 / V2) without 3D secure the response is some HTML with the message We're sorry but payment-page doesn't work properly without JavaScript enabled. Please enable it to continue.
We can login as SDKexplorer in https://dashboard.zota-sandbox.com/ but we cant see the test orders there.

Questions:

What it means the response We're sorry but payment-page doesn't work properly without JavaScript enabled. Please enable it to continue.?
Is it a way we can see the orders in the Sandbox dashboard?

@atanasantonov sorry for the delay, I've responded via email, let me know if everything is answered 🙏

@Kantonov ok, thanks. I haven't received anything and the reply it's probably to Milen. @gonzomir can you confirm please?

@atanasantonov That comment above is from Aug 30, my email is from Sep 5 and I haven't received anything yet.

@gonzomir ouch for some reason there was an unread email in my Github folder and I clicked the link to the issue. And because we are expecting an answer totally missed the date.. Anyway it will be notification to others.

@gonzomir @atanasantonov, hope you received my email from today (3 Oct) regarding the 400 bad request issue 🙏


Report bug from toolbar context menu causes toolbar icon to become unresponsive and crashes PowerToys

Microsoft PowerToys version
0.55.0
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce
Right click on the toolbar entry, choose Report bug. The entry should become unresponsive and the app crashes in a few seconds.
Generated crash report
✔ Expected Behavior
The context menu option to bring me here
❌ Actual Behavior
The option does nothing and causes PowerToys to crash.
Other Software
No response

This has been worked on for the 0.74.0 release. Please update PowerToys to the latest version. 😉
https://github.com/microsoft/PowerToys/releases


Real AI models used in AVs

Hello,
Does anyone know whether any automotive OEM has open-sourced the pre-trained AI models used in their self-driving car projects? What's the state of the art on open-sourced models? I know there are lots of different models, each for a different ADAS function, involved in the operation of a normal AV. For now, any would suffice really.
I'm checking Apollo.auto at the moment, but I'm not sure it's applicable to real self-driving scenarios.
Best regards,

Yes, they can actually be used. Yes, I think the conditions of use are speed and accuracy, of course deep learning has its own flaws, but we don't have a better way


Target-specific AST post-processing

The compiler works in several stages at the moment:

lexing & parsing
post-processing of the AST (e.g. concatenating sections)
type-checking
post-processing of the typed AST (simplifying some instructions)
compiling the typed AST into opcodes

For now, post-processing the typed AST is the same for all platforms (which surely works, but introduces some performance drawbacks for some platforms).
As an example, consider this:
section data {
x: u64
  4
}

section code {
main: forall (s: Ts). { %sp: sptr *{ %sp: sptr s }::s }
  mov x, %r0
  mov 0, %r1

unsafe {
  mov %r1(%r0), %r0
}

  ret
}

We can see that we are offsetting a register with another one.
On x64 (amd64), this is possible to do in one opcode (using the SIB byte). But this is not possible in MIPS, where you first have to load the address of x, then add the content of the register to it, and then load the value at the address in the register.
Because of this, it would be a huge performance penalty for x64 to post-process the unsafe instruction into a sequence of 3 to 4 instructions.

This stage has been moved to a target-specific codegen preprocessor. :tada:

This stage has been moved to a target-specific codegen preprocessor. :tada:


where clause

is any where clause to search in database? i can't find any solution or documentation about this feature

@MahdiPishguy you can do box.values.where((obj) => conditions(obj)), as objects are stored in memory

@frank06 thanks so much, is any document or demo for that to understand how can i get more information? like where,orderby,groupBy,like`

Sure! https://api.dart.dev/stable/2.7.1/dart-core/Iterable-class.html


documentation

We should have full-blown Documenter.jl documentation.  I will help, I just wanted to open this issue to track.
Anyway, thanks so much for taking this whole thing over!  I must admit I feel a pang of regret for not carrying it all the way through myself, especially when I was so close, but as I was doing on it entirely in my free time, and the feared nightmares in which it would be absolutely crucial for me to have a full robust arrow package in order to even use Julia at work never materialized, it was incredibly hard for me to stay motivated, especially when I hit major obstacles (like the flatbuffers issues).  Let this be a lesson not to take on major projects during playtime that are frankly just no goddamn fun 😆

Done in #54


Add Service Request to API to get consent request from URI

The URI will have a consentId onboard which must be sent to the API in order to retrieve the ConsentRequest and Schema

[x] Add Endpoint on Server to request a ConsentRequestModel and ConsentDataSchema from a given ConsentId with statuses CREATED
[x] Add User Authenticated Endpoint on Server to request ConsentRequestModel and ConsentDataSchema for a given UserId and ConsentId with status of WAITING
[ ] Add api code in NextJs to handle these endpoints
[ ] Documentation

Add api code in NextJs to handle these endpoints is no longer required. Simply use the fetch api in getServerSideProps to handle this behaviour


test: fix build on windows

Enable long paths on windows, otherwise git checkout of tough will fail.
Once merged, I'll tag a new release and propagate that to policy-evaluator. Otherwise kwctl will not build on windows

The fix is working fine


Register request display form fields on load of page

now, these fields appear after first login attempt, when user input does not match object.

now displays on load as well, need to work on layout though!

On layout do you mean html? I worked on login and register.html they should look good now

clarified


Write FYP Proposal by dividing headings between group member. Every one complete their assigned headings from the proposal and commit a file named 'yourname_proposal.doc' inside the documentation folder in project repo.

Started woking on the diagrams that needed to be added to the proposal i.e. Gantt chart, and flow chart etc.

I have completed my assign Task

CONGRATS Team!
The proposal is submitted successfully.....!
Now we are officially registered for FYP at COMSATS.
Move forward to other issues.


[ENH] Logistic distribution

Reference Issues/PRs

https://github.com/sktime/skpro/issues/22
What does this implement/fix? Explain your changes.

Logistic probability distribution
Does your contribution introduce a new dependency? If yes, which one?

no
What should a reviewer concentrate their feedback on?

[ ] Energy formula for logistic distribution

Did you add any tests for the change?

Yes, I try to install this library locally using pip install --editable .[dev,test] and create simple driver program to use this new distribution

Any other comments?

I use the formula from Wikipedia, which can be accessed here
For log_pdf, I use wolfram alpha to derive the formula, here is the screenshot

PR checklist

For all contributions

[ ] I've added myself to the list of contributors with any new badges I've earned :-)
How to: add yourself to the all-contributors file in the skpro root directory (not the CONTRIBUTORS.md). Common badges: code - fixing a bug, or adding code logic. doc - writing or improving documentation or docstrings. bug - reporting or diagnosing a bug (get this plus code if you also fixed the bug in the PR).maintenance - CI, test framework, release.
See here for full badge reference
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG]. [BUG] - bugfix, [MNT] - CI, test framework, [ENH] - adding or improving code, [DOC] - writing or improving documentation or docstrings.

For new estimators

[ ] I've added the estimator to the API reference - in docs/source/api_reference/taskname.rst, follow the pattern.
[ ] I've added one or more illustrative usage examples to the docstring, in a pydocstyle compliant Examples section.
[ ] If the estimator relies on a soft dependency, I've set the python_dependencies tag and ensured
dependency isolation, see the estimator dependencies guide.

For log_pdf, I use wolfram alpha to derive the formula

Interesting - I would just have used the standard logarithm rules to cancel exps etc.
Do you have an opinion on which representation is more stable, numerically?
Intuitively, at least, I would think cancelling as many exps as possible is better.

PS: no need to close PR and reopen, if you update your branch on your fork, the PR automatically gets updated.

PS: no need to close PR and reopen, if you update your branch on your fork, the PR automatically gets updated.

Previously, I incorrectly named the branch, it should be logistic, but I named the branch as weibull, sorry about that 😅😅

Interesting - I would just have used the standard logarithm rules to cancel exps etc.

Thank you so much on your thoughts about this! Based on my manual calculation it should be
$(-\frac{x-\mu}{s}) - ln(s) - 2ln(1+e^{-\frac{x-\mu}{s}})$

Do you have an opinion on which representation is more stable, numerically?

I'm uncertain myself about which representation is numerically more stable 😅😅
Previously I leaned towards the result from Wolfram Alpha as it offered a relatively simpler equation, but I am also not really sure whether it is the best solution
After some careful consideration, I think using the standard logarithm rule would be more intuitive to use and to be read. I will change it accordingly 😅😅

Thank you so much on your thoughts about this! Based on my manual calculation it should be

Looks correct to me. I'd use numpy logaddexp (or the scipy distribution directly)

I'd use numpy logaddexp
Sure, I have adjusted the code to use the function

could you kindly add the distribution to the api reference in docs?
Sure, I have added the new class to the API reference

not blocking, but could you kindly look at the comment re logs and cancellation?
I am not sure I understand this, what does comment re logs and cancellation mean? Thank you!

Please let me know if there is any concern or feedback, thank you so much!

Interesting - I would just have used the standard logarithm rules to cancel exps etc.

The above is what I meant, yes

I'm assuming you're no longer working on this, so I'm wrapping this up now.

Hi @fkiraly,  I very much apologize for the delay in completing the PR without notifying you further. Thank you so much for wrapping this PR up. Please kindly let me know if there's anything I can assist with or if there are any adjustments needed 🙏🙏

no worries - a message would have been helpful, but it is not unusual that PRs do not get completed, and we wrap those up that are close to the finish line.
Thanks for your contibutions with the scipy adapter, these are really nice!


Support to PHP 8.4, Arm64 and updated Alpine version

Hey @lorisleiva,
I'm sending this pull request to add support to PHP 8.4 and Arm64. #139
Thanks.

This is great, thanks! Could you just remove PHP version 8.1? This repo aims to supports the last 3 PHP versions only.

Hey @lorisleiva, I just removed the 8.1. Thanks.


[index.html]: fix some mobile css

Hide widescreen and display inputs for mobile screens.

[story]: Hide widescreen checkbox input
[story]: make buttons 1 line each
[index]: make each input at top of the screen 1 line
[index]: remove display type option

Only for mobile. It was nice having it for the ipad


Add pointer to latest API ref

Fixes #4775
cc/ @bfirsh

Yay! ✨

@bfirsh It was temporarily reverted as there was an issue, but  I saw a new PR is being worked on

Oh yes, haha. Glad to see it's on it's way though. ;)


⚠ Samsung has degraded performance

In d265941, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 6815 ms

Resolved: Samsung performance has improved in 9dbe4cc.


cloud_firestore crashes on failed Query

Example:
Firestore.instance.collection("jobs")
         .where("location", isEqualTo: locationReference)
         .orderBy("datetime")

When using a complex query with multiple fields checked, as above, the underlying library will kick back with the below error, if an Index has not been created in the Firebase Console.
I/System.out(32065): com.google.firebase.firestore.FirebaseFirestoreException: FAILED_PRECONDITION: The query requires an index. You can create it here: [link omitted]
But because errors are not caught, only printed to system.out, it leads to more problems down the line followed by a hard crash:
D/AndroidRuntime(32065): Shutting down VM
E/AndroidRuntime(32065): FATAL EXCEPTION: main
E/AndroidRuntime(32065): java.lang.NullPointerException: Attempt to invoke virtual method 'java.util.List com.google.firebase.firestore.QuerySnapshot.getDocuments()' on a null object reference
E/AndroidRuntime(32065): 	at io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$EventObserver.onEvent(CloudFirestorePlugin.java:140)
E/AndroidRuntime(32065): 	at io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$EventObserver.onEvent(CloudFirestorePlugin.java:122)
E/AndroidRuntime(32065): 	at com.google.firebase.firestore.zzi.onEvent(Unknown Source)

cc @collinjackson

Can confirm Firestore does not crash anymore in case of a missing index. There is clear error description in the logs.
I would, however, expect the AsyncSnapshot to have the error field clearly set.
Sample code:
StreamBuilder<QuerySnapshot>(
  stream: state.myQuery,
  builder: (BuildContext context, AsyncSnapshot<QuerySnapshot> snapshot) {
    if (snapshot.hasError) {
      return Text('Error: ${snapshot.error}');
    }
    print('snapshot: ${snapshot.connectionState}');
    switch (snapshot.connectionState) {
      case ConnectionState.done:
      case ConnectionState.waiting:
        return Container(
          child: const Center(child: CircularProgressIndicator()),
        );

      default:
        if (snapshot.data.documents.isEmpty) {
          return _buildEmptyPage();
        }

        return _buildListView(snapshot, context);
    }
  },
),

snapshot.error & snapshot.hasErro really should be set in that case.

@Skylled
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/918. Any further collaboration will be done there.


Retro update 2.12

Description
Retroactively update 2.12 release notes for security plugin with JWT library change
Issues Resolved
Closes: https://github.com/opensearch-project/security/issues/4617
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @derek-ho Can you please rebase with main? The link-checker should be fixed.

1a4b876

Done in: 1a4b876

Hi @derek-ho Can you please rebase with main? The link-checker should be fixed.

Done in: 1a4b876

Unrelated whitesource failure. Merging this PR.


Add Vagrantfile

[ ] Decide on Ubuntu vs. Fedora
[ ] Update the README on how to use it

Trying this branch:
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device

Solved with:
diff --git a/Vagrantfile b/Vagrantfile
index 7bb225d..0a52228 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -25,6 +25,10 @@ Vagrant.configure("2") do |config|
       vb.customize ["modifyvm", :id, "--cpus", "1"]
   end

+  # Prevent TTY Errors (copied from laravel/homestead: "homestead.rb" file)... By default this is "bash -l".
+  # https://stackoverflow.com/questions/40815349/vagrant-ubuntu-box-inline-scripts-emitting-mesg-ttyname-failed-inappropriate-io/42397127#42397127
+  config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'"
+
   config.vm.provision "shell", inline: <<HERE
 profile=/home/ubuntu/.bash_profile
 if [ ! -e $profile ]; then touch $profile; fi

After that, the VM starts fine for me.

The user "ubuntu" should be added in the group "docker". Otherwise, the build of Kubernetes in the vagrant VM will fail:
ubuntu@ubuntu-zesty:/go/src/k8s.io/kubernetes$ build/run.sh make
+++ [0614 15:22:10] Verifying Prerequisites....
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ docker-machine: run `docker-machine ls` and `docker-machine start <name>`
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ docker-machine: run `eval "$(docker-machine env <name>)"`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
!!! Error in build/run.sh:28
  Error in build/run.sh:28. 'return 1' exited with status 1
Call stack:
  1: build/run.sh:28 main(...)
Exiting with status 1

I have tried with passing the full GOPATH directory to the vagrant VM:
diff --git a/Vagrantfile b/Vagrantfile
index 7bb225d..0da8b65 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -2,7 +2,6 @@
 # vi: set ft=ruby :

 ENV["TERM"] = "xterm-256color"
-ENV["GOPATH"] = "/go"
 ENV["LC_ALL"] = "en_US.UTF-8"

 Vagrant.configure("2") do |config|
@@ -13,8 +12,7 @@ Vagrant.configure("2") do |config|

   # config.vbguest.auto_update = true

-  config.vm.synced_folder ".", "/vagrant", disabled: true
-  config.vm.synced_folder ".", "/go/src/github.com/kinvolk/kubeadm-nspawn", create: true
+  config.vm.synced_folder "#{ENV['GOPATH']}", "/go", create: true
   # config.vm.provider :virtualbox do |vbox|
   #     vbox.check_guest_additions = false
   #     vbox.functional_vboxsf = false

AFAICT most of the comments for the PR are already out-of-date, because the whole Vagrantfile has been rewritten for Fedora 26 instead of Ubuntu.
The only remaining valid issue here is about the out-of-memory failure despite of 4GiB memory. I have not seen such an error, and I'm not sure either how to prevent it.
So I'd say, let's merge this PR for now, especially as other pending fixes depend on the changes in Vagrantfile.
/cc @robertgzr @alban

@dongsupark If I remember correctly the memory issue came up when building kubernetes (which is what we did originally)
I am not sure how to do that, if we need to be able to do this in the vagrant box?

@robertgzr Yeah, I already have done several complete k8s rebuilds in the Vagrant box, but haven't seen such a failure. Maybe more tight memory constraints are necessary for reproducing it.
Anyway as discussed with @blixtra, I'm going to merge this PR.


doc: Fixed typos in installation document.

It is trivial. This commit is to fix typos in installation document.
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

:memo: Version: 1.20180820. Thank you for submitting PR #238. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://invain.mooo.com/.

Info: You can read if there are misspelled characters at our misspelling check report. Please read http://invain.mooo.com/TAOS-CI/ci/repo-workers/pr-format/201809081837060.83738088607788-238-377e05da302a9bc6b1149d704e79c7ca6b257eac/report/misspelling_result.txt.

We generate a report if there are dangerous coding constructs in your code. Please read http://invain.mooo.com/TAOS-CI/ci/repo-workers/pr-format/201809101112070.74837708473206-238-155d91e1bc4b59eb3125a82bc4725d27897b2f94/report/.

Info: You can read if there are misspelled characters at our misspelling check report. Please read http://invain.mooo.com/TAOS-CI/ci/repo-workers/pr-format/201809101112070.74837708473206-238-155d91e1bc4b59eb3125a82bc4725d27897b2f94/report/.


Error while importing python-graph-tool "ImportError: cannot import name specfun"

I have installed Python graph tool from
When I try to import the package, its giving error
Command:
python ImportError: cannot import name specfun
Error:
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-5-100bbe2bc9d9> in <module>()
----> 1 from graph_tool.all import *

/usr/lib/python2.7/dist-packages/graph_tool/__init__.py in <module>()
     99 import numpy.ma
    100 import scipy
--> 101 import scipy.stats
    102
    103

/usr/lib/python2.7/dist-packages/scipy/stats/__init__.py in <module>()
    336 from __future__ import division, print_function, absolute_import
    337
--> 338 from .stats import *
    339 from .distributions import *
    340 from .morestats import *

/usr/lib/python2.7/dist-packages/scipy/stats/stats.py in <module>()
    178 from scipy._lib.six import callable, string_types
    179 from numpy import array, asarray, ma, zeros
--> 180 import scipy.special as special
    181 import scipy.linalg as linalg
    182 import numpy as np

/usr/lib/python2.7/dist-packages/scipy/special/__init__.py in <module>()
    627 from ._ufuncs import *
    628
--> 629 from .basic import *
    630 from . import specfun
    631 from . import orthogonal

/usr/lib/python2.7/dist-packages/scipy/special/basic.py in <module>()
     15                       hankel1, hankel2, yv, kv, gammaln, ndtri, errprint, poch,
     16                       binom)
---> 17 from . import specfun
     18 from . import orthogonal

Hi @vineeshvs, that means that your installed scipy is messed up. Try reinstalling it. If the problem persists, we're going to need details on how you installed it to be able to help you further.


Offline erc20 tokens wont load

Hi,
I've a problem and don't know how to fix it.. I've created a offline wallet and that works perfect but when i want to add different tokens and press: "load token" it keeps "loading". Is that normal or does that take ages to load? Or can i download other tokens on a different way? Or can i just send erc20 tokens to my eth address?
Sorry for the noob questions but if someone can help me, that would be awesome.
Thanks anyways

Hi when you say offline, do you mean  your computer is not connected to internet? In order to load token balances you have to be connected. I would use https://www.myetherwallet.com/#view-wallet-info and view with address only option to see the token balance as it is the most secure approach


Investigation: Support for Faraday 2

A first look into issue #488, throw-away investigation.

This was just an investigation. A separate PR that is working better here: https://github.com/zendesk/zendesk_api_client_rb/issues/488


site: move to one install page

waiting -- secondary nav

deployed to prod.  Used inline links as secondary nav.  It feels sufficient.


"hack" to fix AzureOpenAI configuration problem

Explanation:
Unfortunately, while all other LLM providers require only MODELNAME and APIKEY, Azure requires also a MODELDEPLOYMENT.
Since each model has its own deployment, when we use smart_model and fast_model, we need deployments for each.
The fix works, but only if the model name and deployment name are identical.
TODO: I did not test the embeddings model yet, as I cannot test it due to a throttled Azure Subscription at home (free trial tier)

and maybe https://github.com/assafelovic/gpt-researcher/pull/918 fixes the Embeddings model to work with Azure, as well.

confirmed: #918 fixes the embeddings with Azure.


Added a note on obtaining the ATLAS_TOKEN

Again, not big, but useful for the noob.

Sweet, Thanks!


[5.8] Fix issue with is() and unpersisted models

This fixes an issue with is() as described in #28172 where it would return true when given model instances that weren't actually persisted in the database. I think the expected functionality would be that it only returns true when comparing persisted database records.
I had to set exists = true for the test cases here to keep them valid - I did attempt to set it on the EloquentModelStub but it broke other tests, so felt it was more appropriate to be explicit on the relevant tests instead. Let me know if you'd prefer another approach.

Had to make some adjustments to some other tests that relied on the old behaviour of is(). I still think this change fixes the intended outcome of the method so the changes to the tests are worthwhile.

This change makes sense but I'd prefer to see it go to master.
The simple use-cases below will no longer work:
$user = new App\User;
$post = new App\Post;
$user->is($post); //false

$comment = new App\Comment;
$comment2 = new App\Comment;
$comment2->is($comment); //true

Although I doubt the method was intended to be used this way, and despite the fact that it only compares the associated table names, after 3 years, there's a good chance this is littered throughout codebases.

I did consider that but was hopeful it might be considered a bug fix. Happy to reopen against master if that makes more sense.

$this->exists && $model->exists may be replaced with $this->exists === $model->exists.
It fixes this use case:
$comment = new App\Comment;
$comment2 = new App\Comment;
$comment2->is($comment); //true

That would be an easier fix if we're happy with that use-case being supported.

Maybe will be better to put it to 5.9? Since as for me for someone it can be breaking changes

Cool, I'll re-open against master.


Include Windows client support

Can you include official guidance or statement for Windows client, such as Win10 to Win11 in-place upgrade? it includes Gen1 to Gen2 convert as well. There are a lot of demands especially AVD/CtrixVDI users questioning the same.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 780935e4-9fdd-d41a-c4ae-69e1cf118653
Version Independent ID: 7d156aed-66b7-e010-0647-6064aa54f58b
Content: Windows in-place upgrade - Azure Virtual Machines
Content Source: articles/virtual-machines/windows-in-place-upgrade.md
Service: virtual-machines
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@uonie
Thanks for your feedback! We will investigate and update as appropriate.

@uonie
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)


Vm analysis doesn'start

Hello.
Today i deside to know, how Vm Analysis works in Manageiq-darga. My Provider -Vmware.
But Vm analysis on two VMs is in state 'waiting_to_start'  for a hour. I think, it isn't normally.
Tnx.

There is no errors in log files.

Hi,
Is the smart_state role enable on the appliance?

@arnikasky

@roliveri Hi, yes, this role is enabled.

@roliveri Hello. After update(today) it works. I'll close issue


Mouse cursor still visible when crosshair is enabled

Describe the bug
When the crosshair is enabled, the default cursor is still visible on top of the crosshair. The idea with a crosshair is to provide a clear visual reference point for aiming. The visible mouse cursor defeats the purpose of the crosshair and should be hidden to provide a clear view of the current target.
Additionally, if hovering over an active annotated area while pressing "backspace" to delete the annotation, the mouse cursor changes to a fixed mouse-pointer cursor (this behavior is the same even without crosshair enabled).
To Reproduce
Steps to reproduce the behavior:

Go to "Settings" -> "Labeling Interface" and click on "Code"
Enable the crosshair by adding crosshair="true" to the image tag, eg:
<Image name="image" value="$image" crosshair="true"/>
Select an image to annotate. The default cursor now follows the crosshair on the screen.
Create an annotation and mark it for editing. While hovering over the active annotation, press "backspace" do delete the annotation. The cursor has now been stuck on a fixed pointer-cursor.

Expected behavior
The crosshair should be clear from any cursors, providing the user a clear view with only the guidlines visible  while creating new annotations.
If the user hovers over an existing annotation or marks an annotation for editing, the mouse-cursors should be visible to the user as the annotation is now in "edit"-mode as is the current state.
When the user moves the mouse out of an existing annotaion, the mouse-cursor should be hidden, leaving only the crosshair visible again.
Screenshots
Cursor is visible when crosshair is enabled

Cursor is stuck on pointer after deleting an active annotation by pressing "backspace". This behaviour is the same with or without the crosshair enabled.

Environment (please complete the following information):

OS: Wiindows
Label Studio Version: 1.12.0

Additional context
PR submited here: https://github.com/HumanSignal/label-studio/pull/5878

I know it's been a while but thanks for the issue and the PR @NickSwardh, we'll have an update on this soon. We appreciate your time and effort 🙏


Tuya 4 button remote TS0044 / _TZ3000_ee8nrt2l doesn‘t work with deCONZ

Tuya/Loratap 4 button remote doesn‘t work properly with deCONZ.
Please see here:
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5836
On the web page it is shown as compatible.
Maybe also my understanding on what the page means is wrong?
The device is able to be paired, but without functionality.

Which web page?

Hi, this one:
https://zigbee.blakadder.com/LoraTap_SS6400ZB.html

Hi again, just would like to give feedback that meanwhile the switch is working in my deCONZ environment.
There seems having been issues while the first pairing, which I meanwhile could tackle with some nice support here on Git.


[backport] Clean up DeviceInternals

Backport of #6827

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit eb53020fdff2d86f0bd9ecf05a12d1b055e88ba9, target branch v6) failed with status FAILURE.

LGTM!


NOJIRA: Pin version of Error Prone core used

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included

Description of change

error prone core 2.1 is throwing
java.lang.ClassCastException: com.sun.tools.javac.tree.JCTree$JCExpressionStatement cannot be cast to com.sun.source.tree.BlockTree

https://travis-ci.org/Jasig/uPortal/jobs/267344574#L1023-L1032
reverting back to previous minor release resolves the issue

cc @cbeach47

Thanks @ChristianMurphy .


Lingoly README update

Adding LingOly to the list of tasks in the README

The PR seems to think that the yamls are new even when they've been merged. Could you try pulling from main to update your branch?


Using '/' as delimiter on a new line

Which version and edition of Flyway are you using?
6.2.4
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
Oracle DB
Which operating system are you using?
Windows
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
I tried to make some migrations using the '/' on a line alone as delimiter.
For example, just a "CREATE TABLE" statement, that works on Oracle SQL Developer but not using flyway command line
What did you expect to see?
I expected that the migration would be successful and the table would be created
What did you see instead?
The migration failed with an error "ORA-00922: missing or invalid option"

Could you please provide an example script that flyway fails to execute?

UPDATE company SET name = 'COOL' WHERE record# = 1234567 /

I made a script containing only that line and it parsed fine. Is there maybe other stuff in the file that could be causing the actual failure?

That is weird, there is nothing else. I tried with an other statement:

It didn't work as well.

So on investigation the sql as written is invalid, as it has to end with a semicolon to be 'properly ended'. Im guessing that sql developer is adding the semicolons onto the end of statements without one before it executes the sql.

I am not sure about Oracle SQL Developer adding semicolons.
According to Oracle documentation:

Link of the documentation:
https://docs.oracle.com/cd/E11882_01/server.112/e16604/ch_four.htm#SQPUG014
I also tried the following statement on Oracle SQL Developer:
SELECT record# from company /
According to the SQL history:

It has been executed without adding a semicolon.

Here is another example. This script works fine in sqlplus and SQL developer against my Oracle 18c database. But it fails in flyway.
create table temp_migr(c1 number)
/
insert into temp_migr values(1)
/
insert into temp_migr values(2);
insert into temp_migr values(3);
commit;
drop table temp_migr
/
The flyway migrate output is:
Flyway Community Edition 6.0.7 by Redgate
Database: jdbc:oracle:thin:@//dev08.intacct.com:1521/dbacct (Oracle 18.0)
Successfully validated 3 migrations (execution time 00:00.179s)
Current version of schema "MIGR_OWNER_01": 0.2
WARNING: outOfOrder mode is active. Migration of schema "MIGR_OWNER_01" may not be reproducible.
Migrating schema "MIGR_OWNER_01" to version 0.3 - delimiter test
ERROR: Migration of schema "MIGR_OWNER_01" to version 0.3 - delimiter test failed! Please restore backups and roll back database and code!
ERROR:
Migration V0.3__delimiter_test.sql failed
SQL State  : 42000
Error Code : 922
Message    : ORA-00922: missing or invalid option
Location   : ./V0.3__delimiter_test.sql (/u02/home/vcrisan/projects/db/app/migr_simple/./V0.3__delimiter_test.sql)
Line       : 1
Statement  : create table temp_migr(c1 number)
/
insert into temp_migr values(1)
/
insert into temp_migr values(2)


Run new simulation didn't reset the region

We did a couple runs using the "run from previous configs" button, and then tried to run from "run new simulations" but the region button is still disabled.

fixed


Restricting the rotation.x

With rotation.c limit -90 / + 90 if you look straight at the bottom or up the application hangs and blocks do not break.

So don't set rotation to 90, simple


Update GitHub Actions CI

The following updates are performed:

update actions/checkout to v4
update actions/setup-python to v5

Still using the outdated / unmaintained actions will generate several warnings in CI runs, for example in https://github.com/duncaneddy/brahe/actions/runs/7457261161:

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The PR will get rid of those warnings.

@duncaneddy: Updated / Rebased to solve merge conflicts, so it can be cleanly merged again.

Appreciate the PR!


Add a Gitter chat badge to README.md

go-gem/gem now has a Chat Room on Gitter
@ruishengyang has just created a chat room. You can visit it here: https://gitter.im/go-gem/gem.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 86.6% when pulling 949d50a3613f15983bc595d3631109ac795828d1 on gitter-badger:gitter-badge into 2a5fc10f715dadff566f8c97b096625782f47d15 on go-gem:master.


Prompt configuration

Hi, I would like to use oh and having a configurable prompt is a must to me. What do you think?
I did some changes to the code and added the current directory to the "prompt":
oh > cd ~
bpinto > cd ~/src/
src >

Ideally, this would be configurable and colourful. :)

Thanks for trying oh. I would welcome a pull request that adds a configurable prompt. Ideally this would be done by calling an oh method that the user can override.

I am new to go and to oh, could you give me a top-level overview of the changes that would be necessary?

Sure. You will need to modify ui.go to pass a prompt other than '> '. From
your last message it looks like you are comfortable doing that. What you
will want to do is add a function to task.go that evaluates a method in the
context of the foreground task and returns a string that can be used as the
prompt.
On Thu, Jan 21, 2016 at 9:44 AM, Bruno<EMAIL_ADDRESS>wrote:

I am new to go and to oh, could you give me a top-level overview of the
changes that would be necessary?
—
Reply to this email directly or view it on GitHub
https://github.com/michaelmacinnis/oh/issues/19#issuecomment-173591450.

The user can now define a prompt method (see lib/boot.oh for the default prompt method) to return a custom prompt.

:+1:


[doc, site] Mdbook init deployment

[Only consider final 3 commits, the rest are the content of #17323 and will be rebased on-top of those changes before merging]
These changes add a new script util/site/deploy.sh, which replaces a number of deploy.sh scripts scattered through the project. The new script, plus other accompanying changes, builds and deploys the Gcloud infrastructure that will be used to host the new site structure proposed in #17323.
These changes need to be merged at the same time as #17323 , and some manual changes to the Gcloud will be required to move the production site across at the time (changing routing to new buckets etc.). Therefore, DO NOT MERGE until we can coordinate with those steps.

Cherry-picked into #17323 hence closing.


Add example for C26402

@JordanMaples : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@corob-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Mainnet bug - refresh button counter

Hi there! I don't suppose the bug bounty is still in effect? :) Or if this bug even qualifies...
Anyway here is what I found in case you aren't already aware of it... I was just playing around on the site, and hit the refresh button to the left of the counter under "CURRENT ERA". It messed up the countdown timer, and I recorded it which is attached.
I'm using Brave browser on Linux. Let me know if you need any other info. Thank you!

Thanks will address this now


Add new OpenAI model versions on ModelInfo.cs

It's necessary to update the ModelInfo.cs class dictionary for new Azure OpenAI models.

It's necessary to modify the ModelInfo.cs to include versions of models and differences between input tokens and output tokens. This is the current GPT-4 model tokens by version:

This is the ENMARCHA model information for get MaxTokens:


Fix HashBuild unspilling stuck

Summary:
When the input of HashBuild is from spilling, they all come from the
same partition.  That means the spill partition bits are all same for the hashes
from these rows.  In case the hash table is large, there could be overlap between the hash bits
we use to calculate bucket index and the bits for spill partitioning.  These
bits are fixed for all rows and because they are higher bits, we end up
restricting ourselves to a smaller region of the hash table.  This results in
heavy hash collision and the hash build will take super long time and block
driver threads.
Fix this by adding a check to make sure that there will be no overlap between
the spill partitioning bits and the bits used for bucket indexing, and increase
the default spill start partition bit to 48.
Differential Revision: D53589502

@Yuhta : Thanks for this fix. We noticed this slowdown internally as well. Will retry. Appreciate it.
@mbasmanova


[FEA] Support z-ordering acceleration

This is another idea of something that we could try for performance.
z-ordering can really help improve the performance and reduce the data load for a large number of queries.  It is explained rather well in the Wikipedia article, but the performance benefits are really shown in this blog post from Cloudera about Apache Impala support for it.  In addition to Impala, Delta lake in Databricks supports it.
It would be really interesting to see what performance impact z-order on different columns can have to the performance of NDS runs. It also sounds like it would be something that we could accelerate on the GPU fairly easily.
As such the first steps for this task would be

Create a prototype on the CPU that would let us do some basic z-order experiments with NDS queries.
If the query performance is good, then prototype this same thing on the GPU and see what the speedup is for writes over the CPU.

After that we then would need to look at how would we turn this into a product that our users could take advantage of. Do we just wait for Databricks to open source it through deltalake and fit it into that? Do we write a custom UDF that will output binary data that we can sort on and then throw away? Something else?

I took a look at the impala code and mode of it exists here.
https://github.com/apache/impala/blob/da14fdcf35da28d2ff86c6ca9413a95cc3f8f346/be/src/util/tuple-row-compare.h
https://github.com/apache/impala/blob/b28da054f3595bb92873433211438306fc22fbc7/be/src/util/tuple-row-compare.cc
They don't manifest the zorder byte array. The number of bytes used for each type is determined by the largest type being ordered by. The sizes are set here
https://github.com/apache/impala/blob/51126259bea2491316decef63d584f713d02a9a6/be/src/runtime/types.h#L312-L352
But from the comments it looks like they only support up to 128 bits.
 It also looks like they normalize the number values to be unsigned values. It also looks like they play similar games with float and double, but slightly differently.
We should also think about how we want to handle padding. Normally with zordering for two columns A and B we would have something like.
[A-0, B-0, A-1, B-2, ... A-N, B-N], but if the length of A and B differ, i.e. A-int and B-byte can we get away with.
[A-0, B-0, A-1, A-2, A-3], or should we pad out B with zeros? [A-0, B-0, A-1, 0, A-2, 0, A-3, 0]. What about if it is a String instead of a byte?
Also we might want to think about the size of the comparison that we are doing, and what is the most efficient for the GPU. Is a list of bytes as fast as a list of ints?
Other questions:
How do we handle arrays or other nested types?
How do we handle nulls?
Do we want to make this flexible so we can adapt it to deltalake, or are we just going to concentrate on something with NDS to start out with?

It looks like deltalake has released zorder support to open source in versions 2.0 and above. The algorithm appears to be more complex than impala's, and very different.
Delta will map the columns to integers using the RangePartitioner code. This means that for each column that you want to partition by, you will run the final stage of that query N + 2 times, where N is the number of columns in the zorder.  The first N queries will use the RangePartitioner code from Spark to get range cutoffs for up to M partitions per column.  M is set by a config a deltalake. Then it will generate a new expression that extracts the partition ID for each item in the corresponding column, and finally interleave the bits to produce what the data will be ordered by. It will then range partition the data based off of this new String of interleaved bits (This requires running the query twice. Once to get the ranges and another to actually do the partitioning)
Be aware that there is a config to add a random byte as a second column to range partition by so that it can help spread out some data skew issues.
The configs in question are here
https://github.com/delta-io/delta/blob/91051df45f573a9dcdeaf9173aff6ba18314c82e/core/src/main/scala/org/apache/spark/sql/delta/sources/DeltaSQLConf.scala#L611-L625
The code is here
https://github.com/delta-io/delta/blob/91051df45f573a9dcdeaf9173aff6ba18314c82e/core/src/main/scala/org/apache/spark/sql/delta/skipping/MultiDimClustering.scala#L82-L88
https://github.com/delta-io/delta/blob/56e1b9b417e8815cd7003eaf1796988c670b8b0d/core/src/main/scala/org/apache/spark/sql/delta/expressions/InterleaveBits.scala
This is all really complicated, so here is an example.
Lets say we have a dataset that has 5 columns, but we are going to order by just two of them (A: Integer and B: Long). For this example we are going to have a relatively small amount of data (10 rows).

A
B

100
100

200
100

300
100

400
200

500
700

600
0

700
800

800
900

900
0

0
0

Now Delta will try to get a partition ranges for each column. We are only going to use 3 ranges to make this simpler. It uses the RangePartitioner to do this that does sub-sampling/etc, but I am just manually going to do this.
For A
Partition 0 is A < 300
Partition 1 is 300 <= A < 600
Partition 2 is 600 <= A
For B
Partition 0 is  B < 100
Partition 1 is 100 <= B < 200
Partition 2 is 200 <= B
We then end up with the partition IDs for each column along with the original data

A
B
A-PART
B-PART

100
100
0
1

200
100
0
1

300
100
1
1

400
200
1
2

500
700
1
2

600
0
2
0

700
800
2
2

800
900
2
2

900
0
2
0

0
0
0
0

Then it will interleave the bits of the partitions to get the actual z-order field (as a string) and possibly include a random byte column at the end when it does the range partitioning.
Then it is done. There is no sorting done (as far as I can tell). It is just what file the data is written to so you would not get any wins for row groups within a file.  As far as I can tell.


Adds support for uWSGI/nginx deployment.

@oceanzus Who is the person to check this... @FBRTMaka ??

@DanielJMaher Sure, Matt can be the reviewer.

Yes.

Word


HREF Issue

I was trying to format a hyperlink column with the following JSON.  The goal was for the icon and link to only show if there was a link provided but for some reason i am always getting a Failure: FieldRenderer Error:invalidProtocol.  If I remove the HREF portion it shows the icon correctly.
{
"$schema": "https://gist.githubusercontent.com/thechriskent/2e09be14a4b491cfae256220cfca6310/raw/eb9f675bf523208eb840c462d4f716fa92ce14c2/columnFormattingSchema.json",
"debugMode": true,
"elmType": "a",
"attributes": {
"target": "_blank",
"iconName": {
"operator": "?",
"operands": [
{
"operator": "!=",
"operands": [
"@currentField",
""
]
},
"ProjectCollection",
""
]
},
"href": {
"operator": "?",
"operands": [
{
"operator": "!=",
"operands": [
"@currentField",
""
]
},
"@currentField",
""
]
}
}
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f60068c3-4534-a400-350b-fdbcefd684b6
Version Independent ID: 228accdb-a7de-0671-34ad-60a37866c380
Content: Use column formatting to customize SharePoint
Content Source: docs/declarative-customization/column-formatting.md
Service: unspecified
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

A couple of things with your format:

@currentField is case sensitive ("@currentfield" will be treated as a string with that value - not a dynamic value)
Only http, https, and mailto links are supported. So, if you're link values are using any other protocol they won't render and you'll see an error instead (the error only shows when "debugMode": true)

So here's your format with the case sensitivity adjusted and debugMode removed:
{
  "$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json",
  "elmType": "a",
  "attributes": {
    "target": "_blank",
    "iconName": {
      "operator": "?",
      "operands": [
        {
          "operator": "!=",
          "operands": [
            "@currentField",
            ""
          ]
        },
        "ProjectCollection",
        ""
      ]
    },
    "href": {
      "operator": "?",
      "operands": [
        {
          "operator": "!=",
          "operands": [
            "@currentField",
            ""
          ]
        },
        "@currentField",
        ""
      ]
    }
  }
}

This JSON script for hyperlink work only with modern UI, and when we navigate to Classic UI it is back to normal text. Anything can be done to fix this or this article applies only to Modern UI. If yes, please keep the note accordingly .


Longest Common Substring using Dynamic Programming

I would like to write a code for the Longest Common Substring  Problem. In this problem we have to determine the length of longest common substring between two given strings. I will implement it using Dynamic Programming in C++ with proper comments and explanation of the code.
I am a participant of GSSOC'21.
I request the mentors to assign me this question.
@tarun26091999 @anubhavitis @dheerajkotwani @todi-2000 @geekquad @plazzy99

issue already present at #21

@VibhuRajput specify the language.


Merge releases/v3 into releases/v2

Merging e675ced7a into releases/v2.
Conductor for this PR is @dbartol.
Contains the following pull requests:

#2105 (@angelapwen)
#2110 (@jsoref)
#2114 (@henrymercer)
#2116 (@henrymercer)
#2118 (@dependabot[bot])
#2120 (@henrymercer)
#2121 (@aeisenberg)
#2122 (@jsoref)
#2123 (@angelapwen)
#2124 (@dbartol)
#2128 (@dependabot[bot])
#2131 (@dbartol)

Please do the following:

[x] Ensure package.json file contains the correct version.
[ ] Add commits to this branch to resolve the merge conflicts in the following files:

[ ] package-lock.json
[ ] package.json

[ ] Ensure another maintainer has reviewed the additional commits you added to this branch to resolve the merge conflicts.
[x] Ensure the CHANGELOG displays the correct version and date.
[x] Ensure the CHANGELOG includes all relevant, user-facing changes since the last release.
[x] Check that there are not any unexpected commits being merged into the releases/v2 branch.
[x] Ensure the docs team is aware of any documentation changes that need to be released.
[x] Remove and re-add the "Update dependencies" label to the PR to trigger just this workflow.
[x] Wait for the "Update dependencies" workflow to push a commit updating the dependencies.
[x] Mark the PR as ready for review to trigger the full set of PR checks.
[ ] Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.

Inadvertently checked in the release script change I used to perform the release manually.  Forced push to address.

Merge conflicts in package.json resolved manually, package-lock.json conflicts should be solved by Update dependencies workflow.


Use WatchObject instead of Retry+Validate

Update most e2e usages for Retry & Valdiate to use Watch functions
instead. This should make tests less flakey, slightly faster, and
easier to debug.
Use 30s as a minimum timeout to account for occationally slow CI.
Refactor a few tests to wait in parallel with a TaskGroup
Update more Predicates to support nil object as NotFound

/lgtm
/approve


New Feature: add new report formats other than HTML

It would be great to have machine readable formats like xml, json, ...at least one of these to be able to use the versions information for example during CI pipelines

What about providing a pull request ?

Sorry for the long silence, I just saw #112 and for my use case this is working perfectly. Many thanks!


[EAGLE-503]Refactor DynamicPolicyLoader to use MapComparator

EAGLE-503 Refactor DynamicPolicyLoader to use MapComparator

Refactor DynamicPolicyLoader to use MapComparator to get add/modify/remove keys
Move MapComparator.java to alert-common/utils
Add methods in MapComparator to support return add/modify/remove keys

https://issues.apache.org/jira/browse/EAGLE-503

@RalphSu could you pls. help spend some time in reviewing this pr?


Fixes code example colour contrast

Description

Addresses a colour contrast issue reported in #2693
Expressive Code performs colour contrast correction automatically, but we had misconfigured a background colour setting, so Starlight’s default theme was not being properly taken into account in these calculations.
This PR fixes that and ensures code blocks have sufficient text contrast.
Shout out to @hippotastic for helping with the solution.

size-limit report 📦

Path
Size

/index.html
6.93 KB (0%)

/_astro/*.js
21.19 KB (0%)

/_astro/*.css
13.76 KB (+0.07% 🔺)

Just a heads up: The code block styles on this page seem to be broken for me on iOS Safari in the deploy preview, not sure why that is the case:
https://deploy-preview-2708--astro-starlight.netlify.app/environmental-impact/#caching
The live site looks good. I can't imagine this one-line change causing this, so there might be something else going on.

Just a heads up: The code block styles on this page seem to be broken for me on iOS Safari in the deploy preview, not sure why that is the case:
deploy-preview-2708--astro-starlight.netlify.app/environmental-impact#caching

Oh that’s very odd… and I can reproduce the exact same behaviour in the dev server too. It appears that the Expressive Code styles are not loaded at all on that page.

Figured out this was a caching issue due to how the Astro 5 content collection implementation caches Markdown across builds. Rebuilding on Netlify with a clear cache fixed it.
This does make this change a bit riskier than it appears. Users might need to astro sync --force or manually remove the cache (e.g. via UI in deployment environments) to avoid issues when upgrading.


Upgrade JLine

The problem should be fixed by https://github.com/fusesource/jansi/commit/b9348fc702a6800f47c072f80abc757a0496495f