Add ability to supply an XDC file to Vivado analysis.

There are some unknown bits discovered after fasm2bels in the minilitex design:
+# In frame 0x00000f1b 32 bits were not converted.
+{ unknown_bit = "00000f1b_5_19", unknown_segment = "0x00000f00", unknown_segbit = "27_179" }
+{ unknown_bit = "00000f1b_5_20", unknown_segment = "0x00000f00", unknown_segbit = "27_180" }
+{ unknown_bit = "00000f1b_5_21", unknown_segment = "0x00000f00", unknown_segbit = "27_181" }
+{ unknown_bit = "00000f1b_5_24", unknown_segment = "0x00000f00", unknown_segbit = "27_184" }
+{ unknown_bit = "00000f1b_15_19", unknown_segment = "0x00000f00", unknown_segbit = "27_499" }
+{ unknown_bit = "00000f1b_15_20", unknown_segment = "0x00000f00", unknown_segbit = "27_500" }
+{ unknown_bit = "00000f1b_15_21", unknown_segment = "0x00000f00", unknown_segbit = "27_501" }
+{ unknown_bit = "00000f1b_15_24", unknown_segment = "0x00000f00", unknown_segbit = "27_504" }
+{ unknown_bit = "00000f1b_25_19", unknown_segment = "0x00000f00", unknown_segbit = "27_819" }
+{ unknown_bit = "00000f1b_25_20", unknown_segment = "0x00000f00", unknown_segbit = "27_820" }
+{ unknown_bit = "00000f1b_25_21", unknown_segment = "0x00000f00", unknown_segbit = "27_821" }
+{ unknown_bit = "00000f1b_25_24", unknown_segment = "0x00000f00", unknown_segbit = "27_824" }
+{ unknown_bit = "00000f1b_45_19", unknown_segment = "0x00000f00", unknown_segbit = "27_1459" }
+{ unknown_bit = "00000f1b_45_20", unknown_segment = "0x00000f00", unknown_segbit = "27_1460" }
+{ unknown_bit = "00000f1b_45_21", unknown_segment = "0x00000f00", unknown_segbit = "27_1461" }
+{ unknown_bit = "00000f1b_45_24", unknown_segment = "0x00000f00", unknown_segbit = "27_1464" }
+{ unknown_bit = "00000f1b_66_19", unknown_segment = "0x00000f00", unknown_segbit = "27_2131" }
+{ unknown_bit = "00000f1b_66_20", unknown_segment = "0x00000f00", unknown_segbit = "27_2132" }
+{ unknown_bit = "00000f1b_66_21", unknown_segment = "0x00000f00", unknown_segbit = "27_2133" }
+{ unknown_bit = "00000f1b_66_24", unknown_segment = "0x00000f00", unknown_segbit = "27_2136" }
+{ unknown_bit = "00000f1b_76_19", unknown_segment = "0x00000f00", unknown_segbit = "27_2451" }
+{ unknown_bit = "00000f1b_76_20", unknown_segment = "0x00000f00", unknown_segbit = "27_2452" }
+{ unknown_bit = "00000f1b_76_21", unknown_segment = "0x00000f00", unknown_segbit = "27_2453" }
+{ unknown_bit = "00000f1b_76_24", unknown_segment = "0x00000f00", unknown_segbit = "27_2456" }
+{ unknown_bit = "00000f1b_86_19", unknown_segment = "0x00000f00", unknown_segbit = "27_2771" }
+{ unknown_bit = "00000f1b_86_20", unknown_segment = "0x00000f00", unknown_segbit = "27_2772" }
+{ unknown_bit = "00000f1b_86_21", unknown_segment = "0x00000f00", unknown_segbit = "27_2773" }
+{ unknown_bit = "00000f1b_86_24", unknown_segment = "0x00000f00", unknown_segbit = "27_2776" }
+{ unknown_bit = "00000f1b_96_19", unknown_segment = "0x00000f00", unknown_segbit = "27_3091" }
+{ unknown_bit = "00000f1b_96_20", unknown_segment = "0x00000f00", unknown_segbit = "27_3092" }
+{ unknown_bit = "00000f1b_96_21", unknown_segment = "0x00000f00", unknown_segbit = "27_3093" }
+{ unknown_bit = "00000f1b_96_24", unknown_segment = "0x00000f00", unknown_segbit = "27_3096" }
+
+# In frame 0x00020f1b 8 bits were not converted.
+{ unknown_bit = "00020f1b_66_19", unknown_segment = "0x00020f00", unknown_segbit = "27_2131" }
+{ unknown_bit = "00020f1b_66_20", unknown_segment = "0x00020f00", unknown_segbit = "27_2132" }
+{ unknown_bit = "00020f1b_66_21", unknown_segment = "0x00020f00", unknown_segbit = "27_2133" }
+{ unknown_bit = "00020f1b_66_24", unknown_segment = "0x00020f00", unknown_segbit = "27_2136" }
+{ unknown_bit = "00020f1b_56_19", unknown_segment = "0x00020f00", unknown_segbit = "27_1811" }
+{ unknown_bit = "00020f1b_56_20", unknown_segment = "0x00020f00", unknown_segbit = "27_1812" }
+{ unknown_bit = "00020f1b_56_21", unknown_segment = "0x00020f00", unknown_segbit = "27_1813" }
+{ unknown_bit = "00020f1b_56_24", unknown_segment = "0x00020f00", unknown_segbit = "27_1816" }
+
+# In frame 0x00400f1b 24 bits were not converted.
+{ unknown_bit = "00400f1b_76_19", unknown_segment = "0x00400f00", unknown_segbit = "27_2451" }
+{ unknown_bit = "00400f1b_76_20", unknown_segment = "0x00400f00", unknown_segbit = "27_2452" }
+{ unknown_bit = "00400f1b_76_21", unknown_segment = "0x00400f00", unknown_segbit = "27_2453" }
+{ unknown_bit = "00400f1b_96_19", unknown_segment = "0x00400f00", unknown_segbit = "27_3091" }
+{ unknown_bit = "00400f1b_96_20", unknown_segment = "0x00400f00", unknown_segbit = "27_3092" }
+{ unknown_bit = "00400f1b_76_24", unknown_segment = "0x00400f00", unknown_segbit = "27_2456" }
+{ unknown_bit = "00400f1b_96_21", unknown_segment = "0x00400f00", unknown_segbit = "27_3093" }
+{ unknown_bit = "00400f1b_96_24", unknown_segment = "0x00400f00", unknown_segbit = "27_3096" }
+{ unknown_bit = "00400f1b_56_19", unknown_segment = "0x00400f00", unknown_segbit = "27_1811" }
+{ unknown_bit = "00400f1b_56_20", unknown_segment = "0x00400f00", unknown_segbit = "27_1812" }
+{ unknown_bit = "00400f1b_56_21", unknown_segment = "0x00400f00", unknown_segbit = "27_1813" }
+{ unknown_bit = "00400f1b_56_24", unknown_segment = "0x00400f00", unknown_segbit = "27_1816" }
+{ unknown_bit = "00400f1b_45_19", unknown_segment = "0x00400f00", unknown_segbit = "27_1459" }
+{ unknown_bit = "00400f1b_45_20", unknown_segment = "0x00400f00", unknown_segbit = "27_1460" }
+{ unknown_bit = "00400f1b_45_21", unknown_segment = "0x00400f00", unknown_segbit = "27_1461" }
+{ unknown_bit = "00400f1b_45_24", unknown_segment = "0x00400f00", unknown_segbit = "27_1464" }
+{ unknown_bit = "00400f1b_66_19", unknown_segment = "0x00400f00", unknown_segbit = "27_2131" }
+{ unknown_bit = "00400f1b_66_20", unknown_segment = "0x00400f00", unknown_segbit = "27_2132" }
+{ unknown_bit = "00400f1b_66_21", unknown_segment = "0x00400f00", unknown_segbit = "27_2133" }
+{ unknown_bit = "00400f1b_86_19", unknown_segment = "0x00400f00", unknown_segbit = "27_2771" }
+{ unknown_bit = "00400f1b_86_20", unknown_segment = "0x00400f00", unknown_segbit = "27_2772" }
+{ unknown_bit = "00400f1b_66_24", unknown_segment = "0x00400f00", unknown_segbit = "27_2136" }
+{ unknown_bit = "00400f1b_86_21", unknown_segment = "0x00400f00", unknown_segbit = "27_2773" }
+{ unknown_bit = "00400f1b_86_24", unknown_segment = "0x00400f00", unknown_segbit = "27_2776" }

There is also a failure which now is usually more uncommon than before with the iobuf_i2c test, about the clock through general interconnect:
ERROR: [Place 30-176] Unroutable Placement! The following clock source instance is driving the following locked load instances. The clock source instance is placed too far away from its load instance to be routable.
	CLK_HROW_TOP_R_X60Y78_BUFHCE_X1Y20_BUFHCE (BUFHCE.O) is locked to BUFHCE_X1Y20
	The loads are distributed to 1 user pblock constraints. In addition, there are 20 loads not in user pblock constraints.

	Displaying only the first 20 or fewer instances under each constraint as list of loads is too long

	Displaying first 20 loads not in user pblock constraint:
	$auto$simplemap.cc:442:simplemap_dffe$7081CLBLL_L_X28Y40_SLICE_X44Y40_B_FDRE (FDRE.C) is locked to SLICE_X44Y40
	$auto$simplemap.cc:442:simplemap_dffe$7082CLBLL_L_X28Y40_SLICE_X44Y40_A_FDRE (FDRE.C) is locked to SLICE_X44Y40
	$auto$simplemap.cc:442:simplemap_dffe$7477CLBLM_R_X27Y42_SLICE_X43Y42_A_FDRE (FDRE.C) is locked to SLICE_X43Y42
	$auto$simplemap.cc:442:simplemap_dffe$7083CLBLL_L_X28Y43_SLICE_X44Y43_B_FDRE (FDRE.C) is locked to SLICE_X44Y43
	$auto$simplemap.cc:442:simplemap_dffe$7479CLBLM_R_X27Y42_SLICE_X43Y42_B_FDRE (FDRE.C) is locked to SLICE_X43Y42
...

This somewhat strange at I start to believe that the penalty cost is not effective when routing. Now the cost of going through the wrong edge is 10e-6, which should definitely let the router discard the edge when routing.

This somewhat strange at I start to believe that the penalty cost is not effective when routing. Now the cost of going through the wrong edge is 10e-6, which should definitely let the router discard the edge when routing.

Only in the absence of congestion.  Once other paths are congested, their costs will rise :(  The right solution for this problem is to mark these nodes as occupied, per https://github.com/SymbiFlow/symbiflow-arch-defs/issues/1019#issuecomment-550438945

I've removed the --verbose for now, I'll file an issue tracking the minilitex behavior.


Introduce a pylint test for coding standards and docstring enforcement

Dask is an amazing project, but it's relatively hard to contribute because there appears to be absolutely no coding standards, nor an enforcement of any kind of docstring. It might be helpful to add a pylint test (e.g. something like this). For example scheduler.py it suggests the following:
\distributed\dashboard\components\scheduler.py:708:0: C0301: Line too long (103/100) (line-too-long)
\distributed\dashboard\components\scheduler.py:862:0: C0301: Line too long (104/100) (line-too-long)
\distributed\dashboard\components\scheduler.py:911:0: C0301: Line too long (109/100) (line-too-long)
\distributed\dashboard\components\scheduler.py:914:22: C0326: No space allowed before bracket
                print (gap_to_previous)
                      ^ (bad-whitespace)
\distributed\dashboard\components\scheduler.py:916:0: C0301: Line too long (127/100) (line-too-long)
\distributed\dashboard\components\scheduler.py:1600:0: C0330: Wrong hanging indentation before block (add 4 spaces).
            sorted(self.scheduler.workers.items(), key=lambda kv: kv[1].name)
            ^   | (bad-continuation)
\distributed\dashboard\components\scheduler.py:1:0: C0302: Too many lines in module (1882/1000) (too-many-lines)
\distributed\dashboard\components\scheduler.py:1:0: C0111: Missing module docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:70:4: W0622: Redefining built-in 'map' (redefined-builtin)
\distributed\dashboard\components\scheduler.py:34:0: E0611: No name 'Viridis11' in module 'bokeh.palettes' (no-name-in-module)
\distributed\dashboard\components\scheduler.py:39:0: E0611: No name 'format_bytes' in module 'dask.utils' (no-name-in-module)
\distributed\dashboard\components\scheduler.py:77:4: C0103: Constant name "ExportTool" doesn't conform to UPPER_CASE naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:79:0: C0103: Constant name "logger" doesn't conform to UPPER_CASE naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:81:0: C0413: Import "from jinja2 import Environment, FileSystemLoader" should be placed at the top of the module (wrong-import-position)
\distributed\dashboard\components\scheduler.py:83:0: C0103: Constant name "env" doesn't conform to UPPER_CASE naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:89:0: C0103: Constant name "nan" doesn't conform to UPPER_CASE naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:90:0: C0103: Constant name "inf" doesn't conform to UPPER_CASE naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:96:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:139:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:143:12: C0103: Variable name "y" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:145:12: C0103: Variable name "ms" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:146:12: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:149:16: C0103: Variable name "ws" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:93:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:182:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:216:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:217:8: C0103: Variable name "L" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:218:16: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:219:8: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:179:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:225:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:262:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:264:16: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:265:8: C0103: Variable name "d" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:266:8: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:222:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:274:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:321:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:323:12: C0103: Variable name "bw" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:271:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:339:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:370:12: W0612: Unused variable 'rect' (unused-variable)
\distributed\dashboard\components\scheduler.py:411:18: W0621: Redefining name 'value' from outer scope (line 8) (redefined-outer-name)
\distributed\dashboard\components\scheduler.py:406:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:408:12: C0103: Variable name "bw" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:411:12: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:411:15: C0103: Variable name "y" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:336:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:434:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:560:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:560:4: R0914: Too many local variables (16/15) (too-many-locals)
\distributed\dashboard\components\scheduler.py:564:12: C0103: Variable name "y" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:570:16: C0103: Variable name "ws" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:582:16: C0103: Variable name "ws" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:582:20: C0103: Variable name "nb" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:431:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:624:0: C0111: Missing class docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:625:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:653:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:624:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:668:0: C0111: Missing class docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:669:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:724:12: W0621: Redefining name 'time' from outer scope (line 62) (redefined-outer-name)
\distributed\dashboard\components\scheduler.py:720:4: R0914: Too many local variables (16/15) (too-many-locals)
\distributed\dashboard\components\scheduler.py:734:8: C0103: Variable name "d" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:724:25: W0612: Unused variable 'key' (unused-variable)
\distributed\dashboard\components\scheduler.py:724:40: W0612: Unused variable 'sat' (unused-variable)
\distributed\dashboard\components\scheduler.py:724:45: W0612: Unused variable 'occ_sat' (unused-variable)
\distributed\dashboard\components\scheduler.py:724:54: W0612: Unused variable 'idl' (unused-variable)
\distributed\dashboard\components\scheduler.py:724:59: W0612: Unused variable 'occ_idl' (unused-variable)
\distributed\dashboard\components\scheduler.py:747:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:750:12: C0103: Variable name "n" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:772:0: C0111: Missing class docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:773:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:819:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:822:12: C0103: Variable name "n" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:831:16: C0103: Variable name "ys" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:772:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:861:0: C0111: Missing class docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:861:0: R0902: Too many instance attributes (12/7) (too-many-instance-attributes)
\distributed\dashboard\components\scheduler.py:862:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:865:8: C0103: Variable name "es" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:884:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:888:30: C1801: Do not use `len(SEQUENCE)` to determine if a sequence is empty (len-as-condition)
\distributed\dashboard\components\scheduler.py:888:34: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:889:28: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:890:31: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:897:12: C0103: Variable name "n" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:911:34: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:911:66: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:912:53: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:918:20: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:924:23: C0103: Variable name "v" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:861:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:1028:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:1091:16: W0621: Redefining name 'update' from outer scope (line 55) (redefined-outer-name)
\distributed\dashboard\components\scheduler.py:1085:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:1088:42: E1136: Value 'self.node_source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1104:4: C0111: Missing method docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1104:50: W0621: Redefining name 'update' from outer scope (line 55) (redefined-outer-name)
\distributed\dashboard\components\scheduler.py:1104:4: R0914: Too many local variables (23/15) (too-many-locals)
\distributed\dashboard\components\scheduler.py:1114:12: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1115:12: C0103: Variable name "y" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1123:16: C0103: Variable name "xx" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1124:16: C0103: Variable name "yy" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1131:16: C0103: Variable name "a" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1131:19: C0103: Variable name "b" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1148:25: C1801: Do not use `len(SEQUENCE)` to determine if a sequence is empty (len-as-condition)
\distributed\dashboard\components\scheduler.py:1148:33: E1136: Value 'self.node_source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1150:16: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:1151:16: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:1161:8: C0103: Variable name "n" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1161:16: E1136: Value 'self.node_source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1162:8: C0103: Variable name "m" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1162:16: E1136: Value 'self.edge_source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1173:12: W0201: Attribute 'visible_updates' defined outside __init__ (attribute-defined-outside-init)
\distributed\dashboard\components\scheduler.py:1180:12: W0201: Attribute 'visible_updates' defined outside __init__ (attribute-defined-outside-init)
\distributed\dashboard\components\scheduler.py:1190:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:1192:8: C0103: Variable name "ps" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1322:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:1327:36: C1801: Do not use `len(SEQUENCE)` to determine if a sequence is empty (len-as-condition)
\distributed\dashboard\components\scheduler.py:1327:44: E1136: Value 'self.source.data' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1330:12: C0103: Variable name "d" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1187:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:1353:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:1355:8: C0103: Variable name "ps" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1418:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)
\distributed\dashboard\components\scheduler.py:1420:12: C0103: Variable name "nb" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1350:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:1436:4: W0231: __init__ method from base class 'DashboardComponent' is not called (super-init-not-called)
\distributed\dashboard\components\scheduler.py:1436:4: R0914: Too many local variables (20/15) (too-many-locals)
\distributed\dashboard\components\scheduler.py:1509:16: E1136: Value 'table.columns' is unsubscriptable (unsubscriptable-object)
\distributed\dashboard\components\scheduler.py:1597:4: W0221: Parameters differ from overridden 'update' method (arguments-differ)

\distributed\dashboard\components\scheduler.py:1599:22: C0103: Variable name "ws" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1615:8: E1101: Instance of 'ColumnData' has no 'update' member (no-member)
\distributed\dashboard\components\scheduler.py:1599:16: W0612: Unused variable 'addr' (unused-variable)
\distributed\dashboard\components\scheduler.py:1427:0: R0903: Too few public methods (1/2) (too-few-public-methods)
\distributed\dashboard\components\scheduler.py:1618:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1624:22: E1133: Non-iterable value sysmon.root.children is used in an iterating context (not-an-iterable)
\distributed\dashboard\components\scheduler.py:1631:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1656:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1668:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1680:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1682:8: C0103: Variable name "ts" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1699:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1712:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1742:12: W0612: Unused variable 'current_load_fig' (unused-variable)
\distributed\dashboard\components\scheduler.py:1758:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1758:42: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1768:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1768:37: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1776:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1776:41: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1784:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1784:34: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1792:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1792:42: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1800:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1800:39: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1808:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1808:36: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1818:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1818:38: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1826:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1826:45: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1834:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1834:38: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1843:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1845:8: C0103: Variable name "bw" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1843:46: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1852:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1854:8: C0103: Variable name "bw" doesn't conform to snake_case naming style (invalid-name)
\distributed\dashboard\components\scheduler.py:1852:48: W0613: Unused argument 'extra' (unused-argument)
\distributed\dashboard\components\scheduler.py:1861:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:1873:0: C0111: Missing function docstring (missing-docstring)
\distributed\dashboard\components\scheduler.py:81:0: C0411: third party import "from jinja2 import Environment, FileSystemLoader" should be placed before "from distributed.dashboard.components import add_periodic_callback" (wrong-import-order)
\distributed\dashboard\components\scheduler.py:72:4: C0412: Imports from package toolz are not grouped (ungrouped-imports)
\distributed\dashboard\components\scheduler.py:75:4: C0412: Imports from package distributed are not grouped (ungrouped-imports)

Moving this to dask/dask
@dickreuter , you may want to look at https://docs.dask.org/en/latest/develop.html#code-formatting for our current linting.

but it's relatively hard to contribute because there appears to be absolutely no coding standards

Please be aware that negative comments like these regularly lead to maintainer burnout.  I encourage you to try to keep a positive tone.

Dask is an amazing project

Thanks!  That helps!

Don't want to cause any burnout. Will help where I can ;) Keep up the good work!

To be clear, suggesting that Dask about pylint is perfectly reasonable.  My
concern was just about tone, which often we forget about when communicating
with people through text on the internet.
On Mon, Nov 4, 2019, 6:06 PM Nicolas Dickreuter<EMAIL_ADDRESS>wrote:

Don't want to cause any burnout. Will help where I can ;) Keep up the good
work!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5560?email_source=notifications&email_token=AACKZTGCD3NACU3G2MZGJRDQSDIJBA5CNFSM4JI4O2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDBLHFA#issuecomment-549630868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTF6VAURYD4SDKLS4I3QSDIJBANCNFSM4JI4O2ZQ
.

Yes that makes totally sense.

On 5 Nov 2019, at 02:31, Matthew Rocklin<EMAIL_ADDRESS>wrote:
To be clear, suggesting that Dask about pylint is perfectly reasonable. My
concern was just about tone, which often we forget about when communicating
with people through text on the internet.
On Mon, Nov 4, 2019, 6:06 PM Nicolas Dickreuter<EMAIL_ADDRESS>wrote:

Don't want to cause any burnout. Will help where I can ;) Keep up the good
work!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5560?email_source=notifications&email_token=AACKZTGCD3NACU3G2MZGJRDQSDIJBA5CNFSM4JI4O2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDBLHFA#issuecomment-549630868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTF6VAURYD4SDKLS4I3QSDIJBANCNFSM4JI4O2ZQ
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


Failed to Verify Bitcode

While exporting the export failed to verify the bitcode.
Expected behavior
Successfully archive a build.
Actual behavior
Error Domain=IDEFoundationErrorDomain Code=1 "Failed to verify bitcode in TwitterKit.framework/TwitterKit:
error: Linker option verification failed for bundle /var/folders/mx/3800rps92kd6jw5mygd5t1880000gn/T/TwitterKit1LwIBZ/TwitterKit.arm64.xar (unrecognized arguments: -platform_version iOS 9.0.0 13.0.0)

" UserInfo={NSLocalizedDescription=Failed to verify bitcode in TwitterKit.framework/TwitterKit:
error: Linker option verification failed for bundle /var/folders/mx/3800rps92kd6jw5mygd5t1880000gn/T/TwitterKit1LwIBZ/TwitterKit.arm64.xar (unrecognized arguments: -platform_version iOS 9.0.0 13.0.0)

}

Steps to reproduce the behavior
Happened during fastlane build & deploy
xcodebuild -exportArchive -exportOptionsPlist /var/folders/mx/3800rps92kd6jw5mygd5t1880000gn/T/gym_config20191021-61705-ab5grj.plist -archivePath '/Users/panda/Library/Developer/Xcode/Archives/2019-10-21/FanX 2019-10-21 09.55.09.xcarchive' -exportPath /var/folders/mx/3800rps92kd6jw5mygd5t1880000gn/T/gym_output20191021-61705-wepi6m

Have you tried setting Enable Bitcode to NO under Build Settings?

I have Bitcode disabled for my project.

@zmeriksen have you tried this solution?

I will try that! Give me a moment to try and build...

@aliozinan I am getting this error now after adding the Run Script...
[Transporter Error Output]: ERROR ITMS-90085: "No architectures in the binary. Lipo failed to detect any architectures in the bundle executable."

Any ideas?

I had come across the very same error before. The errors you get are obviously pointing an architecture support problem for the build settings :
...TwitterKit.arm64.xar (unrecognized arguments: -platform_version iOS 9.0.0 13.0.0)
[Transporter Error Output]: ERROR ITMS-90085: "No architectures in the binary. Lipo failed to detect any architectures in the bundle executable."
As applying the script causes a similar conflict, revert back the solution on stackoverflow. The first error was thrown at TwitterKit build phase, so try setting BITCODE_GENERATION_MODE to NO under TwitterKit's build settings (and all other targets of the libraries you're using for your project).

a PR that fixes build errors on XCode's latest versions is waiting for approval as a side note. You can test the dev branch and provide feedback here.

@aliozinan I am using CocoaPods so I can't just change the project settings or pull in your PR changes that easy. I will test once your PR gets merged into dev 👍
@touren Ping

you can also try removing tvOS targets as the original error is related with arm64

@aliozinan could this be an issue with Xcode 10.3 vs Xcode 11?

WatchOS is fine, the problem arises at TvOS builds which is unnecessary imo as this is a mobile app development kit. Regarding your question, yes there are issues with XCode 11.x versions, especially when TwitterKit is migrated to the recommended settings.
You can download the awaiting version here and try to build on your XCode to check the results.

Alright I will try your version later. I expect I will have issues with 5.0.1 and 5.1 compiler for my project. I'm still in 10.3 land :(

It's interesting that in my project (which is React Native based) Enable Bitcode is set to Yes and I'm still able to get successful build (I'm on XCode 11.1). The only detail is i had removed all TvOS references under build settings. I also do have SafariServices.framework and WebKit.framework added under General > Frameworks, Libraries and Embedded Content.
I had fixed the XCode 11 compatibility issues by myself.
The current version of TwitterKit5 you install via CocoaPods is compatible and bug free with XCode 10.x so I still beleive that the errors you're getting are about different device support in your targets' build settings. It might be of other pods as well.
Also do not forget using empty Build Cache methods :
rm -rf ~/Library/Developer/Xcode/DerivedData/
Hope this helps & good luck


[ZT] DLP file type control

How do these new selectors relate to https://developers.cloudflare.com/cloudflare-one/policies/filtering/http-policies/#download-and-upload-mime-type?

Should we add these selectors to https://developers.cloudflare.com/cloudflare-one/policies/filtering/http-policies/? What's the difference between the new ones and https://developers.cloudflare.com/cloudflare-one/policies/filtering/http-policies/#download-and-upload-mime-type?

Oh wow, I didnt realize we listed every Selector value there, that's totally on me. Yes, we should then.
The upload and download MIME type are assessed using the MIME type provided in the HTTP header. Upload and Download file type are assessed based on the file signatures in the HTTP body. This can be done even when the MIME type is not present in the HTTP header.


segfault when using mod_audio_stream api

Hello ,
I'm on Centos 7 .
running a node server that is connected to freeswitch .
when i try to use your api it fs_cli crashes and module gets unloaded .
getting this error : freeswitch kernel: freeswitch[6234]: segfault at 0 ip 00007fb0bd2dac58 sp 00007fb10ba439c0 error 4 in mod_audio_stream.so[7fb0bd2c1000+5c000 .
i tried to use other apis and all working properly .

Yes, I managed to reproduce this on Centos 7.9. Issue comes from GCC compiler on Centos and a regex method which doesn't work well on Centos. Try to rebuild the module with updated changes. Regex method is replaced which will fix building and running on centos 7, and won't affect other distros.


Dialog payment

Explore how to display payment information/invoices in a unified way, to enable people to easily understand what needs to be payed, when it's due, etc.
### Tasks
- [ ] Payment statuses (deadline, notices, unpaid, paid, etc)
- [ ] Invoice (Amount, account no, KID, etc)
- [ ] Payment history/table

First sketch


time-consuming inference on image generation

Hi,
I run run_scripts/image_gen/image_gen_example.py to generate some images by inputting a query. However, it takes 140s per query. I use 3090 for inference. Do you know how to accelerate inference?
Thanks!

I  try to modify the following setting:

task.cfg.sampling_times = 1
beam=10
Remove the clip sort
The inference time still needs 47s per image.

It's a known issue, as our image generation method needs to generate 1024 tokens autoregressively (for 256*256 resolution). As you have already found, reducing beam_size can accelerate the inference, but according to our previous experiments, the larger the number of samples, the higher the quality of top1 selected by the clip. I think this requires you to make a trade-off according to your needs.


MAINT/DOC: remove outdated note about NumPy imports

The following note is not true anymore, but it is still in the docs: https://scipy.github.io/devdocs/reference/index.html#guidelines-for-importing-functions-from-scipy

The lines to be removed are: https://github.com/scipy/scipy/blob/cb3ac11209444f9b56454e41abc6a95b63c7ef4b/doc/source/reference/index.rst?plain=1#L87-L92

I'll help with this issue


Use polyline for tiled polygons to account for convex shapes

Fixes #65, more context on the issue.
Tiled polygons seem to require at least 3 points to create as far as I can tell, since 2 points would end up being a polyline.

Thanks for the fix! 👍


Unify custom error codes?

The question came up again about whether we needed to introduce new error codes.

https://github.com/nodejs/node/pull/42675/files/2cea86bbb88ef205f24011176dd4ec127dc503af#r854115222

(As I said in reply, paraphrased) I think fine grained error codes are potentially useful for the author to build custom behaviour, but I also somewhat expect heavy customisation is more likely on top of strict:false where we (largely) don't throw anyway.
(As @bakkot said in reply, paraphrased) we do want rich messages to help the end user.
We could perhaps use a single custom error code so we can still supply rich message for end user, and so author can be confident it was a parsing error and not some completely unexpected error.
So instead of ERR_PARSE_ARGS_INVALID_OPTION_VALUE and ERR_PARSE_ARGS_UNKNOWN_OPTION and ERR_PARSE_ARGS_UNEXPECTED_POSITIONAL, we could use single (say) ERR_PARSE_ARGS_INVALID_ARG.

(I accidentally added this issue without a description. Now updated. This comment so some clue on email!)

The program as well as the human needs to discern, so we absolutely shouldn't just use a single error code.
Error codes should generally map to messages 1:1, and a program should never have to parse a message to figure anything out.

That raises an interesting point though, the error code is not enough alone for author to do much with. We might want to add some properties (in future).
An example would be an author catching ERR_PARSE_ARGS_UNKNOWN_OPTION and adding a message suggesting the most similar option.
$ util --hepl
Unknown option `--hepl` <--- error.message thrown by parseArgs
Did you mean `--help`?   <--- added by author, but how did they know it was `--hepl`?

For comparison, SystemError has a bunch of extra optional properties:
https://nodejs.org/dist/latest-v16.x/docs/api/errors.html#class-systemerror

There isn't a driver to do this from the upstream PR. Closing.

https://github.com/nodejs/node/pull/42675#discussion_r857768064


Minion able to do more then one action

I was told that the minion is able to join two different trips at once when involed with the pumpkinhead mass. It works by joining the ph mass while it’s waiting to be sent you send before the mass is trip begins another command it sends the minion on that trip and then when the mass sends your minion also is sent with the mass.

as you can see here one trip ends and then 6 min later another trip also ends as well showing the minion performed both actions.
I don’t know if this works with other masses.

Thank you for reporting.


Windows support

We've been running turbo_tests in RubyGems with a monkeypatch to make Windows support work. A unified solution would be better but I guess getting things at least working should take priority so maybe there's interest in the raw patch.
Windows tests don't really catch any issues (they pass without this patch), although turbo_tests does not really work on Windows. In any case, as a minimal improvement over what we have, I added Windows to CI.
Finally, I dropped support for Ruby 2.7 since it reached its End of Life and also started testing with Ruby 3.3.
Happy to extract any of these changes to separate PRs!

I see, let me remove the commit dropping support for Ruby 2.7 then!

Thanks for that! I will give this patch a try and confirm it works for us!

I tried this branch through https://github.com/rubygems/rubygems/commit/a4e301244d3a3b2bfc7771edceb50d453e20cd1b and Windows CI is cool with it.
I also tried it locally on Linux and found no issues either, so this seems good!
Unfortunately we're having an unrelated issue, and we had to pin to 2.2.0 for now, but this seems good to me regardless!

@deivid-rodriguez @ilyazub I created #53 to resolve the OpenStruct issue (from #49) by replacing it with a Struct instead. I believe with that change, the json gem dependency could be removed since it was added in #49 along with OpenStruct.

Thank you! Hopefully we'll be able to upgrade and remove our monkeypatches soon!

I reverted #49 in https://github.com/serpapi/turbo_tests/pull/54 and am preparing the PR to fix the Ruby-core tests failure in commands/pristine_spec.rb.

Yeah, that should workaround the issue for us, thank you!
In any case, I think the ruby-core issue reveals some problem in bundler or ruby-core test setup, and I believe it's better to explicitly list dependencies as they are gemified.
I think this change is good for us since it unblock us from upgrading but if I manage to figure out the problem, I'll make sure to get back here and try to add back the explicit json dependency.

@deivid-rodriguez bundle pristine failed in the Ruby-core tests (ref: https://github.com/ruby/ruby/pull/10496#issuecomment-2059313556)
Cannot pristine baz (1.0.0). Gem is sourced from local path.
The installation path is insecure. Bundler cannot continue.
/omitted/path/ruby/tmp/1/gems/system/extensions/x86_64-linux/3.4.0+0-static is world-writable (without sticky bit).
Bundler cannot safely replace gems in world-writeable directories due to potential vulnerabilities.
Please change the permissions of this directory or choose a different install path.

What does the The installation path is insecure error means?

We try to explain it below. Basically means that the previous installation path has insecure world-writable permissions, and since Bundler needs to delete it for bundle pristine, if a malicious user, for example, symlinked a file in that folder to some other important file, Bundler could end up deleting it.
That all said, I don't know how or why the error is being triggered here :open_mouth:.


Enable multi-os on Travis

I am going to email Travis support to request multi-os support is enabled for this repo (http://docs.travis-ci.com/user/multi-os/). This will allow osx and linux to be tested each commit and will avoid the need to create a separate branch with language: objective-c (like I am doing now).

[x] Hear back from travis on enabling the repo
[x] Refactor the .travis.yml to be cross platform

Okay, travis support has enabled multi-os support so now we can add:
os:
  - linux
  - osx

And a single commit to master will build on both platforms. However the .travis.yml will need refactored to work on OSX, so that is the next step.

Done in 33d479d.


Additional small performance improvements

Additional small performance improvements

Can one of the admins verify this patch?

Build not working obviously due to Jenkins/Travis misconfiguration.

Codecov Report

Merging #651 into master will increase coverage by 0.09%.
The diff coverage is 6.25%.

@@             Coverage Diff              @@
##             master     #651      +/-   ##
============================================
+ Coverage      25.7%   25.79%   +0.09%
- Complexity     5976     6009      +33
============================================
  Files          1382     1382
  Lines         82144    82152       +8
  Branches      11509    11508       -1
============================================
+ Hits          21112    21195      +83
+ Misses        58985    58910      -75
  Partials       2047     2047

Impacted Files
Coverage Δ
Complexity Δ

...kylin/stream/core/query/StreamingQueryProfile.java
35.95% <0%> (-0.41%)
12 <0> (ø)

...org/apache/kylin/engine/spark/SparkExecutable.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ache/kylin/measure/topn/TopNCounterSerializer.java
65.21% <0%> (ø)
5 <0> (ø)
:arrow_down:

.../kylin/stream/core/storage/columnar/RawRecord.java
62.5% <0%> (+4.8%)
7 <0> (ø)
:arrow_down:

...rg/apache/kylin/stream/server/StreamingServer.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...a/org/apache/kylin/dict/global/AppendDictNode.java
83.08% <0%> (ø)
32 <0> (ø)
:arrow_down:

...e/kylin/rest/controller/StreamingV2Controller.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...pache/kylin/stream/server/rest/util/QueryUtil.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/org/apache/kylin/jdbc/KylinResultSet.java
87.5% <0%> (ø)
9 <0> (ø)
:arrow_down:

.../org/apache/kylin/metadata/model/TableExtDesc.java
60.86% <0%> (ø)
14 <0> (ø)
:arrow_down:

... and 22 more

Continue to review full report at Codecov.

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


Update Gradle Lastest Version

Description (required)
Fixes #{GitHub issue number} {Github issue title}
What changes did you make and why?
Tests performed (required)
Tested {build variant, e.g. ProdDebug} on {name of device or emulator} with API level {API level}.
Screenshots showing what changed (optional - for UI changes)
Need help? See https://support.google.com/android/answer/9075928

Note: Please ensure that you have read CONTRIBUTING.md if this is your first pull request.

@Cuncis Why are we updating the gradle version?

Closing stale PR for now, reopen if more work happening on it.


fix: add Goutam Nath

Changes proposed
Added new profile : Goutam Nath
Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[X] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

@nathgoutam93 There is some indentation issue too.
Go through Eddie Jaude and change accordingly. :)

i don't think these small changes really matters at all, its just seed data not real code and also going to be minified . 🙄

i don't think these small changes really matters at all, its just seed data not real code and also going to be minified . 🙄

If there are indentation issues, please fix them, they are important. Let us know if you need any help! 😃

i don't think these small changes really matters at all, its just seed data not real code and also going to be minified . 🙄

If there are indentation issues, please fix them, they are important. Let us know if you need any help! 😃

Is it good, looks like my prettier was set to tab width 4


Investigate use of Google Application Integration

See https://cloud.google.com/application-integration/docs/overview

This may be a more visual way to use in future rather than Python

Not sure if this will be a goer. We gain a lot of value from pyinaturalist, e.g. rate limiting, date transformations so would really need to call pyinaturalist as a data source.


Home Page Refinements

Description
Continue work on home page so that it includes features panel and screenshots of our website.

this should come last since everything besides the home page is not final final yet. things will change.

that is true, we will need to showcase parts that are quite solid


Navigation bar is always visible when I use ApplicationChrome

Whenever I set anything about the status bar in ApplicationChrome, the navigation bar also becomes visible. I found out that this line was doing it, removing it solved the problem:
if (Screen.fullScreen) Screen.fullScreen = false;
Is there a reason for this fullScreen to be always set "false"? Is it because of older APIs?
My modified source is attached.
ApplicationChrome.zip

I am curious about this too, any response would be appreciated


minio cant access

My minio s3 endpoint urls is https://abc.myhost.com instead of  https://s3.myhost.com.
its must be s3?
abc is not work.

not supported yet, you are the first one to request it.  I haven't done it yet because I personally don't have a non-s3 provider to develop and test against, but I will put it in the backlog

https://github.com/jvsteiner/s3-image-uploader/pull/3

There is a pull request about non-AWS s3,This may had solved this problem, but it is not work for me to use Minio's S3 settings.

You are right - I was just remembering that I already accepted such a PR.  What is the error or problem that you are experiencing?  I will need some more detailed information.

I have set it,but its not work,the follows is my set.

when I  pasted a picture to the obsidian,the plug-in not work.

is the plugin enabled?  What does the javascript console say?  you should paste any errors you find there

Plugin enabled,

It says that the region is missing - that is part of the S3 api, which minio should be compatible with, but the error says you didnt enter it.  Maybe you need to enter your region for minio.

I add the region,there still have error

I confirm that the key I  type in is right.
its work on Picgo

It can work on Picgo

I have created a testing account:The minio is build on Synology docker
adminurl:https://abc.210814.xyz:19001/
user:s3test
password:s3tests3test

What about the region?

us-north-1

but did you put it in the settings?

yes,I have send you a test account.You can make a try.

what bucket?

This is Minio Backend management
You can fnd any information you want abou S3-api
visit:https://abc.210814.xyz:19001/
user:s3test
password:s3tests3test
S3 date url is https://abc.210814.xyz:19000

can you set Access-Control-Allow-Origin  for the test bucket, please?

ok

I allready set the bucket to public. anyone will be able to upload, download and delete files from this Bucket

It doesn't matter.  The bucket will allow it, but my browser wont make the request, because the Access-Control-Allow-Origin  is not set during the preflight check (OPTIONS) call.  The value of this header should be set to *.  I mentioned this in the README.

access to the test bucket is removed, I am assuming you solved the problem?

I made a release for a different issue (I think) worth trying to update before reporting back

Im trying to solve this problem,To set the CORS policy for the bucket I rebuild the Minio service.

I still not solve this problem.I had created an admin account for you to test it.
user:test
passwd:testtest
May be its the problem of Minio,I think!
https://github.com/minio/minio/issues/11111

I'm going to leave this issue open for now, in case you get any additional information to help, however, as things stand now, I don't have time to do any more trouble shooting on your specific minio instance.

I used Synology own reverse proxy server. I tried a lot, but it still not work. Even s3broswer it can connect to my own minio service. Although it did not solve the problem, thank you for your help.
At last,it still have error.

What is the error you are still getting?
I have been using minio without any issue, and also tested with the public minio test server using these settings:
  "accessKey": "Q3AM3UQ867SPQQA43P2F",
  "secretKey": "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG",
  "region": "us-east-1",
  "bucket": "bucket",
  "useCustomEndpoint": true,
  "customEndpoint": "https://play.min.io/",
  "forcePathStyle": true

@nicksmith53
The same error

This is my config

@nicksmith53
https://play.min.io:9443/     its not work
https://play.min.io/   its work

Also backblaze.com S3 API got the same error.

I'm not able to replicate this issue.
Checking the network tab of my obsidian debug console I see requests that do have the header in your error message:

Could there be another plugin that is interfeering?
Can you create a new empty obsidian vault with only this s3-iamge plugin to test again?

Set endpoint https://play.min.io,Its work!But my self build Minio on Synology,Still not work.
And,I try backblaze.com
B2 S3 api,I got the same error.
Can this plugin support backblaze B2?

Thats will be great!

made a new release.  you might have to restart obsidian after making the settings change

made a new release. you might have to restart obsidian after making the settings change

No cors error,but there got new error

The error only appear on my self build Minio(on my Synology),And its work well on backblaze B2.Thank you for your work!


spring-cloud-starter-ribbon rxjava dependency is old

RxJava dependency is
<dependency>
            <groupId>com.netflix.rxjava</groupId>
            <artifactId>rxjava-core</artifactId>
        </dependency>

Should not this be:
 <dependency>
   <groupId>io.reactivex</groupId>
    <artifactId>rxjava</artifactId>
</dependency>

Because of this, its resulting in compile time error with ambiguous dependency, which makes one to manually exclude.

Netflix artifacts declare dependencies to {{io.reacyivex:rxjava}} (the "old" one).
But {{org.sprigframework.cloud:spring-cloud-starter-ribbon}} explicitly add {{com.netflix.rxjava:rxjava-core}}
This pulls both dependencies together. Since they have overlapping content, it may produce weird issues... Hence the additional question "why is {{org.sprigframework.cloud:spring-cloud-starter-ribbon}} using a different artificat than what Netflix uses?"

newer version of ribbon is bringing in the new io.reactivex:rxjava, looking to see if there are any deps on the old


bluetooth controllers on Android support?

Probably not quite the most common use, but there are some nice Bluetooth gamepad adapters that work fine on Android but are a pain to get working on anything other. Any chance they might be made to work as inputs for this?

Quite a good change actually. This project supports the Gamepad API. So if the browser you are using support this API, external controllers should work fine.


Uberzug backend dosen't work in xfce4-terminal

my specs are
OS: Fedora Linux 39 (Thirty Nine) x86_64
Terminal: xfce4-terminal
CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 4.464GHz
GPU: NVIDIA Geforce RTX 3050
NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1713484068
lazy.nvim version: 11.14.1
ueberzugpp 2.9.6
Lua 5.1  Copyright (C) 1994-2006 Lua.org, PUC-Rio

my config is:
return {
  "3rd/image.nvim",
  dependencies = {
    "leafo/magick",
    "nvim-treesitter/nvim-treesitter",
    {
      "vhyrro/luarocks.nvim",
      config = function()
        require("image").setup({
          backend = "ueberzug",
          kitty_method = "normal",
          integrations = {
            markdown = {
              enabled = true,
              clear_in_insert_mode = false,
              download_remote_images = true,
              only_render_image_at_cursor = false,
              filetypes = { "markdown", "vimwiki" }, -- markdown extensions (ie. quarto) can go here
            },
            neorg = {
              enabled = true,
              clear_in_insert_mode = false,
              download_remote_images = true,
              only_render_image_at_cursor = false,
              filetypes = { "norg" },
            },
            html = {
              enabled = false,
            },
            css = {
              enabled = false,
            },
          },
          max_width = nil,
          max_height = nil,
          max_width_window_percentage = nil,
          max_height_window_percentage = 50,
          window_overlap_clear_enabled = false, -- toggles images when windows are overlapped
          window_overlap_clear_ft_ignore = { "cmp_menu", "cmp_docs", "" },
          editor_only_render_when_focused = false, -- auto show/hide images when the editor gains/looses focus
          tmux_show_only_in_active_window = false, -- auto show/hide images in the correct Tmux window (needs visual-activity off)
          hijack_file_patterns = { "*.png", "*.jpg", "*.jpeg", "*.gif", "*.webp", "*.avif" }, -- render image files as images when opened
        })
      end,
      opts = {
        rocks = {
          hererocks = true,
        },
      },
    },
  },
}

It works well in kitty, but kitty has wierd font bugs on my system so i want to use other terminal (xfce4-terminal in my case), but when i open image there i get just an empty buffer.
xfce4-terminal

kitty

i also noticed when plugin try to render image in markdown it throws this error
 Error executing vim.schedule lua callback: Vim:E474: Unable to represent NaN value in JSON
stack traceback:
	[C]: in function 'json_encode'
	...are/nvim/lazy/image.nvim/lua/image/backends/ueberzug.lua:29: in function 'write'
	...are/nvim/lazy/image.nvim/lua/image/backends/ueberzug.lua:67: in function 'render'
	....local/share/nvim/lazy/image.nvim/lua/image/renderer.lua:462: in function 'render'
	...ek/.local/share/nvim/lazy/image.nvim/lua/image/image.lua:55: in function 'render'
	.../share/nvim/lazy/image.nvim/lua/image/utils/document.lua:88: in function 'render_image'
	.../share/nvim/lazy/image.nvim/lua/image/utils/document.lua:121: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

The JSON issue is an interesting bug, are you rendering a SVG by any chance?
The ueberzugpp issue might be related, but unsure how to reproduce it.
Kitty's performance is much better, what issues do you have with font rendering?

when i try to open jpg/png i am getting this json error, when i open svg file it opens as plain text

about wierd bugs in kitty: i have  same font in kitty and xfce4-terminal, but in kitty some of the icons in neovim are not displayed correctly
here is my kitty.conf:
font_family 	FiraCode Nerd Font Regular
bold_font        auto
italic_font      auto
bold_italic_font auto
font_size 18.0

background_opacity 0.85

map ctrl+shift+t new_tab_with_cwd

window_padding_width 15

tab_bar_style custom

shell_integration no-cursor

# BEGIN_KITTY_THEME
# Rosé Pine
include current-theme.conf
# END_KITTY_THEME

Either:

Kitty doesn't find the fallback font your other terminal does, and that one contains the icons.
Kitty doesn't load FiraCode Nerd Font Regular because it's not a monospace font.

To debug what happens run kitty --debug-font-fallback and it will print out which font is using for which glyphs, as they are renderer (open nvim in the debug terminal).
It's probably because the font is not monospaced: https://github.com/ryanoasis/nerd-fonts/discussions/1039

yeah i was setting the font in a wrong way. i am sorry to bother you with it. So i configured kitty and moved there. works fine exept svgs. they're rendered as text

No worries, I spent a lot of time debugging fonts as well.
If you want SVGs to work you need to add "*.svg" to hijack_file_patterns in the options, it's disabled by default because people might want to edit them.


fix README grammar

:smiley:

:D npm say NO to me with initial name, so I was need to change name, now all should be fine

(you closed, but didn't merge?)


Visual sprite bug (again)

This was after re-importing from a fresh repo clone and duplicating from fresh repo clone to setting it up again and both times it was the same error. I am not sure what is going on but now I'm concerned that this might be a reoccurring error that might affect not just my local computer but future builds on more people's computers.
This is after multiple builds having the same issue. Now I'm wondering if the repo is able to copy and paste properly or if there are consistency issues like in rocket engineering where it works 4/5 time but that 1/5 times is unknown why it does not work or it works on the test stand but not in field tests which is puzzling a lot.
Either way it would be a long shot of after 3 rigorous tests where it was repo cloned and fresh copy and paste and trying my best to isolate and make these versions unique and quarantined that there are these reoccurring visual sprite issues. Strange either way this is should be put into a known issues area or to watch again. The fact this has happened 3 times in the same spot across multiple clean new builds is cause for concern but it can be fixed.
I'm wondering if the build is being corrupted or there are a lack of clean files or something is not right with the build cleanliness going on (like over patched source files). If my pc is having issues with what should be easy copy and paste / extraction then how many other people will have the same or worse issues? Clean patching is tricky business indeed. I'm wondering if the knight visual sprite animation file is bugged or if there are re-importing issues going on?
I'll have a look at the sprites and try to isolate this issue again. It is strange and I think it can be fixed but I wonder if this will grow in scale if this kind of thing keeps happening if the project gets bigger naturally. Good data storage and build isolation is very useful to isolate bugs and protect builds from being too interdependent if bugs go unnoticed.
Back up local builds save from potential issues with github and other zip / sharing inconsistencies vs. solely relying upon github / an cloud server to be dependable forever which is rare so its best to have local backups in case the zips or sharing becomes problematic like what happened with Flare or other game dev projects that use tons of interdependent files hosted on Github. I would recommend doing a robust build and test local file storage system to isolate builds and have master builds hosted locally that can be tinkered with as need be to ensure the Github zip and other cloudfile hosting websites have a proper backup / to future proof.

I use a NATO military and WoW hybrid hybrid patch / iteration system where I have 'Version 000.000.000' being Release.Prototype.Experiment or like 'Version 003.012.421' being 003 Release, 012 Prototype, 421 Experiment. I also have M.M.O.A.R.P.G. Version which is based upon the overall project / initiative and then the engine build / system used for the project / initiative. For example as in if there was a 'Main Battle Tank project / initiative' of say '003' and then the system of say Detroit 008 build version vs. Berlin 006 build version vs. Stockholm 010 build version. These are all competing different systems on the same project / initiative. This is sort of how western arms acquisitions can work in say 'Main Battle Tank 003 project / initiative' where there are multiple bids that may or may not be collaborative in nature. Many complex arms systems came about through this competitive / collaborative method and if it works for trillion+ dollar acquisitions programs then its good enough for keeping the build fields in line lol. Its compacts and works well for keeping complex things simple enough to read on one line.
Archiving and keeping clean records and isolating master builds helps when things get very complex and there are big problems. Backup backup backup everything. I had this what seems over kill archiving really save my self and others when big problems with deep rooted bugs that happened and were unnoticed until compounding problems led the team to be forced to tear into the core systems and rebuild after the 'rot' / bug section was cut out and rebuilt after a lot of effort. A way of going back to just before the bug is super great in saving a lot of work that is at risk of corruption. Or in Github's case bad zip or copy and paste or straight up missing public build files that are missing or corrupted but look the same on github but are not working in practice. Its data consuming to copy and paste the build for every iteration but if you get into really deep issues it save the day many times and the 'back up insurance' of disciplined and thorough backup builds pays for it self.  Yet this can be rare but it has happened to myself multiple times enough to learn to backup backup backup lol. This is going well and things should be getting better bit by bit. Art is one thing but code is another lol. I'll try to keep this easier to read but depth of experience is important too for long term success. So is fun and good moral:-D!

I fixed the issue locally on my computer by deleting the knight animation sprites and redoing the animation frames. I'll try to make a pull request if that helps.

Its 3 AM and I have a fix but its not patching correctly. It keeps not working after going through github and repo zipping its not amazing to use Github when it's wearing thin my patience.
knight.zip
Either way if that file is copy and paste into \common\resources\builtin\sprite_frames_collection to replace the old file added last where in the merge it works every time locally on my end. Yet once that file is patched then uploaded to github it just for what ever reason will not patch properly and Im not feeling like wrestling with github any more tonight.

I started at 11:30 PM ish and now its ~3:00 am and its been a struggle to patch 1 file to just function correctly after going through github.

I wish this was done in a pretty fashion but here we are.

It works as run the demo as usual. Then open the knight.zip into \common\resources\builtin\sprite_frames_collection to replace the old knight.tres file and then the knight character animation should work.

This seems a bit off. Just to be safe, I renamed most of the resource files to snake_case to avoid any case sensitivity issues.

This seems a bit off. Just to be safe, I renamed most of the resource files to snake_case to avoid any case sensitivity issues.

It works well. The visual bug seems to be fixed for now. Good job too! I wonder what the underlying cause was? Either way its nice it works better now.


inconsistent of single width rounding mode description

According to rounding mode, rounded result is (v >> d) + r.
However, I notice most of single width instructions is (v + r) >> d.
E.g., averaging add.
# result = (src1 + src2 + round) >> 1;

I think it should be
# result = ((src1 + src2) >> 1) + round;

?

I agree. Also note that the expression:
    ((src1 + src2) >> 1)
must be evaluated with operands sign-extended to SEW+1 bits for the result to be correct, and this is not made clear. For example, with SEW=8, an averaging add of -128 and -128 (i.e. 0x80 and 0x80) should produce a result 0x80, not 0x00 (which would be the case if not extended).
See also issue #277.

Rounding description issues fixed in commit db4c604.

#256 discusses unsigned average add/sub instructions so closing this issue here.


[BUG]Driver name not found in the list of registered CSI drivers

What is your environment(Kubernetes version, Fluid version, etc.)
K8S: 1.14
Describe the bug
When creating a demo app following this example: https://github.com/fluid-cloudnative/fluid/blob/master/docs/en/samples/accelerate_data_accessing.md
Pod/nginx stuck in pending status. The alluxio-master log shows:
Warning  FailedMount  10m (x45 over 85m)    kubelet, <IP_ADDRESS>  MountVolume.MountDevice failed for volume "hbase" : driver name fuse.csi.fluid.io not found in the list of registered CSI drivers
  Warning  FailedMount  5m26s (x39 over 83m)  kubelet, <IP_ADDRESS>  Unable to mount volumes for pod "nginx_default(bda07d70-0846-11eb-ba61-b8599fb51ea8)": timeout expired waiting for volumes to attach or mount for pod "default"/"nginx". list of unmounted volumes=[hbase-vol]. list of unattached volumes=[hbase-vol default-token-ntghn]

The csidriver:
kubectl get csidriver
NAME                                  CREATED AT
fuse.csi.fluid.io                     2020-10-06T04:15:14Z
kubectl  logs csidriver/fuse.csi.fluid.io
error: cannot get the logs from *v1beta1.CSIDriver: selector for *v1beta1.CSIDriver not implemented

The csi-plugin on the same node with the pod/nginx:
kubectl logs pod/csi-nodeplugin-fluid-j4dkl -n fluid-system -c plugins
I1006 12:15:22.749832 2304931 driver.go:56] Driver: fuse.csi.fluid.io version: 1.0.0
I1006 12:15:22.749906 2304931 driver.go:59] protocol: unix addr: var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock
I1006 12:15:22.749975 2304931 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I1006 12:15:22.749981 2304931 driver.go:93] Enabling volume access mode: MULTI_NODE_MULTI_WRITER
I1006 12:15:22.750115 2304931 server.go:108] Listening for connections on address: &net.UnixAddr{Name:"/var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock", Net:"unix"}
I1006 12:15:23.430501 2304931 utils.go:97] GRPC call: /csi.v1.Identity/GetPluginInfo
I1006 12:15:23.430518 2304931 utils.go:98] GRPC request: {}
I1006 12:15:23.431200 2304931 identityserver-default.go:32] Using default GetPluginInfo
I1006 12:15:23.431205 2304931 utils.go:103] GRPC response: {"name":"fuse.csi.fluid.io","vendor_version":"1.0.0"}

kubectl logs pod/csi-nodeplugin-fluid-j4dkl -n fluid-system -c node-driver-registrar

I1006 04:15:16.117383 2303707 main.go:110] Version: v1.2.0-0-g6ef000ae
I1006 04:15:16.117427 2303707 main.go:120] Attempting to open a gRPC connection with: "/var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock"
I1006 04:15:16.117437 2303707 connection.go:151] Connecting to unix:///var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock
I1006 04:15:23.422345 2303707 main.go:127] Calling CSI driver to discover driver name
I1006 04:15:23.422362 2303707 connection.go:180] GRPC call: /csi.v1.Identity/GetPluginInfo
I1006 04:15:23.422366 2303707 connection.go:181] GRPC request: {}
I1006 04:15:23.431780 2303707 connection.go:183] GRPC response: {"name":"fuse.csi.fluid.io","vendor_version":"1.0.0"}
I1006 04:15:23.432206 2303707 connection.go:184] GRPC error: <nil>
I1006 04:15:23.432212 2303707 main.go:137] CSI driver name: "fuse.csi.fluid.io"
I1006 04:15:23.432232 2303707 node_register.go:58] Starting Registration Server at: /registration/fuse.csi.fluid.io-reg.sock
I1006 04:15:23.432319 2303707 node_register.go:67] Registration Server started at: /registration/fuse.csi.fluid.io-reg.sock

What you expect to happen:
Demo app could run
How to reproduce it
Following example at https://github.com/fluid-cloudnative/fluid/blob/master/docs/en/samples/accelerate_data_accessing.md
Additional Information

Could you try to use https://github.com/fluid-cloudnative/fluid/blob/master/tools/diagnose-fluid.sh which is the latest version? I tried this, it can work fine.
./diagnose-fluid.sh collect --name hbase
Start collecting, runtime-name=hbase, runtime-namespace=default
tar: 从成员名中删除开头的“/”
/tmp/diagnose_fluid_1602052804/
/tmp/diagnose_fluid_1602052804/pods-fluid-system/
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-w96r4-node-driver-registrar.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-gl4qw-plugins.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-hjkwj-plugins.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-t9qrl-plugins.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-w96r4-plugins.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/controller-manager-9b84f87b9-k59zd-manager.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-hjkwj-node-driver-registrar.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-gl4qw-node-driver-registrar.log
/tmp/diagnose_fluid_1602052804/pods-fluid-system/csi-nodeplugin-fluid-t9qrl-node-driver-registrar.log
/tmp/diagnose_fluid_1602052804/fluid-system.log
/tmp/diagnose_fluid_1602052804/default.log
/tmp/diagnose_fluid_1602052804/hbase.yaml
/tmp/diagnose_fluid_1602052804/pods-default/
/tmp/diagnose_fluid_1602052804/pods-default/hbase-worker-64xks-alluxio-job-worker.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-fuse-bh8gj-alluxio-fuse.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-worker-97dsz-alluxio-worker.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-fuse-fm588-alluxio-fuse.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-master-0-alluxio-master.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-worker-97dsz-alluxio-job-worker.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-worker-64xks-alluxio-worker.log
/tmp/diagnose_fluid_1602052804/pods-default/hbase-master-0-alluxio-job-master.log
/tmp/diagnose_fluid_1602052804/fluid.yaml
please get diagnose_fluid_1602052804.tar.gz for diagnostics

And could you also collect the runtime and dataset status by using
kubectl get dataset -oyaml
kubectl get alluxioruntime -oyaml

diagnose_fluid.sh still not working for me.

For diagnose script, I think the reason is that there are some illegal characters. like https://blog.csdn.net/qq_43075039/article/details/98475964
Could you try download by using
wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid.sh

diagnose_fluid.sh still not working for me. Same error:
./diagnose-fluid1.sh collect --name hbase
getopt: illegal option -- o

For diagnose script, I think the reason is that there are some illegal characters. like https://blog.csdn.net/qq_43075039/article/details/98475964
Could you try to download the script by using
wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid.sh

No, I didn't use Helm to install, I used helm template to convert everything into one yaml, and used kubectl to deploy fuild.

we recommend to use helm, because it's good for managing the lifecycle and the diagnose tool are based on assumption of the deployment of fluid comments is helm.

What is your environment(Kubernetes version, Fluid version, etc.)
K8S: 1.14
Describe the bug
When creating a demo app following this example: https://github.com/fluid-cloudnative/fluid/blob/master/docs/en/samples/accelerate_data_accessing.md
Pod/nginx stuck in pending status. The alluxio-master log shows:
Warning  FailedMount  10m (x45 over 85m)    kubelet, <IP_ADDRESS>  MountVolume.MountDevice failed for volume "hbase" : driver name fuse.csi.fluid.io not found in the list of registered CSI drivers
  Warning  FailedMount  5m26s (x39 over 83m)  kubelet, <IP_ADDRESS>  Unable to mount volumes for pod "nginx_default(bda07d70-0846-11eb-ba61-b8599fb51ea8)": timeout expired waiting for volumes to attach or mount for pod "default"/"nginx". list of unmounted volumes=[hbase-vol]. list of unattached volumes=[hbase-vol default-token-ntghn]

The csidriver:
kubectl get csidriver
NAME                                  CREATED AT
fuse.csi.fluid.io                     2020-10-06T04:15:14Z
kubectl  logs csidriver/fuse.csi.fluid.io
error: cannot get the logs from *v1beta1.CSIDriver: selector for *v1beta1.CSIDriver not implemented

The csi-plugin on the same node with the pod/nginx:
kubectl logs pod/csi-nodeplugin-fluid-j4dkl -n fluid-system -c plugins
I1006 12:15:22.749832 2304931 driver.go:56] Driver: fuse.csi.fluid.io version: 1.0.0
I1006 12:15:22.749906 2304931 driver.go:59] protocol: unix addr: var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock
I1006 12:15:22.749975 2304931 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I1006 12:15:22.749981 2304931 driver.go:93] Enabling volume access mode: MULTI_NODE_MULTI_WRITER
I1006 12:15:22.750115 2304931 server.go:108] Listening for connections on address: &net.UnixAddr{Name:"/var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock", Net:"unix"}
I1006 12:15:23.430501 2304931 utils.go:97] GRPC call: /csi.v1.Identity/GetPluginInfo
I1006 12:15:23.430518 2304931 utils.go:98] GRPC request: {}
I1006 12:15:23.431200 2304931 identityserver-default.go:32] Using default GetPluginInfo
I1006 12:15:23.431205 2304931 utils.go:103] GRPC response: {"name":"fuse.csi.fluid.io","vendor_version":"1.0.0"}

kubectl logs pod/csi-nodeplugin-fluid-j4dkl -n fluid-system -c node-driver-registrar

I1006 04:15:16.117383 2303707 main.go:110] Version: v1.2.0-0-g6ef000ae
I1006 04:15:16.117427 2303707 main.go:120] Attempting to open a gRPC connection with: "/var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock"
I1006 04:15:16.117437 2303707 connection.go:151] Connecting to unix:///var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock
I1006 04:15:23.422345 2303707 main.go:127] Calling CSI driver to discover driver name
I1006 04:15:23.422362 2303707 connection.go:180] GRPC call: /csi.v1.Identity/GetPluginInfo
I1006 04:15:23.422366 2303707 connection.go:181] GRPC request: {}
I1006 04:15:23.431780 2303707 connection.go:183] GRPC response: {"name":"fuse.csi.fluid.io","vendor_version":"1.0.0"}
I1006 04:15:23.432206 2303707 connection.go:184] GRPC error: <nil>
I1006 04:15:23.432212 2303707 main.go:137] CSI driver name: "fuse.csi.fluid.io"
I1006 04:15:23.432232 2303707 node_register.go:58] Starting Registration Server at: /registration/fuse.csi.fluid.io-reg.sock
I1006 04:15:23.432319 2303707 node_register.go:67] Registration Server started at: /registration/fuse.csi.fluid.io-reg.sock

What you expect to happen:
Demo app could run
How to reproduce it
Following example at https://github.com/fluid-cloudnative/fluid/blob/master/docs/en/samples/accelerate_data_accessing.md
Additional Information

Could you please provide the node logs of the error pod;
/var/log/messages

Here is /var/log/messages:
root@n147-160-077:~# cat /var/log/messages
Oct  4 06:25:01 n147-160-077 liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="5656" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
For the kubelet.log, it's a 1.8G file, I have no idea which to look for, could you give me some hint? @cheyang @fredkan

I think the logging of common CSI is not  so good, It just show there is an error, but the error is  . you can check the source code of logging: https://github.com/kubernetes-csi/drivers/blob/master/pkg/csi-common/utils.go#L97-L105
I1006 04:15:23.422345 2303707 main.go:127] Calling CSI driver to discover driver name
I1006 04:15:23.422362 2303707 connection.go:180] GRPC call: /csi.v1.Identity/GetPluginInfo
I1006 04:15:23.422366 2303707 connection.go:181] GRPC request: {}
I1006 04:15:23.431780 2303707 connection.go:183] GRPC response: {"name":"fuse.csi.fluid.io","vendor_version":"1.0.0"}
I1006 04:15:23.432206 2303707 connection.go:184] GRPC error: <nil>

So I do some enhancement in the this PR: https://github.com/fluid-cloudnative/fluid/pull/221/files#diff-fd5c9704d91d666649fa10e53f1deaf8R102-R103, especially in https://github.com/fluid-cloudnative/fluid/blob/9aabaeb34283fcf3555d4e176075df663287fde7/vendor/github.com/kubernetes-csi/drivers/pkg/csi-common/utils.go#L101-L106 . You can update the docker image of csi-plugin to registry.cn-hangzhou.aliyuncs.com/fluid/fluid-csi:v0.4.0-1083b6a. And check the logs again.
And from the kubelet log, you can search something like below. But it works fine
10月 09 18:49:19 iZ2ze0pget2kzaquo2thb5Z kubelet[2638]: I1009 18:49:19.571550    2638 csi_plugin.go:101] kubernetes.io/csi: Trying to validate a new CSI Driver with name: fuse.csi.fluid.io endpoint: /var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock versions: 1.0.0, foundInDeprecatedDir: false
10月 09 18:49:19 iZ2ze0pget2kzaquo2thb5Z kubelet[2638]: I1009 18:49:19.571595    2638 csi_plugin.go:120] kubernetes.io/csi: Register new plugin with name: fuse.csi.fluid.io at endpoint: /var/lib/kubelet/csi-plugins/fuse.csi.fluid.io/csi.sock

I suggest you should take a look at the kubelet log which has csi_plugin.go
grep csi_plugin.go kubelet.log

And you can also check the issue: /github.com/kubernetes/kubernetes/issues/68688

@valiantljk The node’s kubelet root_dir is /var/lib/kubelet?

Any update on this? Why is this closed? The older issue 68688 was not resolving this error while deploying an alluxio trial nginix pod.