Fix wrong base_url

[trungleduc]

Close #992

[trungleduc]

@jtpio can we re-release 0.3.0a0 with this pass?

[jtpio]

@jtpio can we re-release 0.3.0a0 with this pass?

We can release 0.3.0a1 it's fine 👍

[jtpio]

Looks like there is an ongoing issue with GitHub Actions at the moment (checks are not triggered):

[github-actions]

Benchmark report

The execution time (in milliseconds) are grouped by test file, test type and browser.
For each case, the following values are computed: min <- [1st quartile - median - 3rd quartile] -> max.

Results table

Test file	basics.ipynb	bqplot.ipynb	dashboard.ipynb	gridspecLayout.ipynb	interactive.ipynb	ipympl.ipynb	ipyvolume.ipynb	multiple_widgets.ipynb	query-strings.ipynb
Render
chromium
actual	4817 <- [5048 - 5580 - 6664] -> 9974	4074 <- [4252 - 4501 - 5127] -> 6724	3938 <- [4070 - 4272 - 4532] -> 5282	3760 <- [4108 - 4133 - 4185] -> 4367	2701 <- [2752 - 2785 - 2976] -> 3227	15714 <- [18651 - 23581 - 33360] -> 62539	11747 <- [13906 - 16094 - 16146] -> 16388	14118 <- [14242 - 14363 - 14409] -> 14500	1725 <- [1764 - 1853 - 1917] -> 2033
expected	3379 <- [3442 - 3517 - 3701] -> 3876	2976 <- [3227 - 3321 - 3421] -> 3604	3608 <- [3623 - 3709 - 3793] -> 3825	4453 <- [4453 - 4523 - 4661] -> 4748	2559 <- [2655 - 2656 - 2660] -> 2674	3982 <- [4079 - 4213 - 4356] -> 4743	12183 <- [18509 - 19553 - 20811] -> 21515	15319 <- [15660 - 15796 - 15912] -> 16056	1517 <- [1920 - 1997 - 2103] -> 2113

❗ Test metadata have changed

--- /dev/fd/63	2021-10-05 15:32:26.468263698 +0000
+++ /dev/fd/62	2021-10-05 15:32:26.468263698 +0000
@@ -8,27 +8,27 @@
   },
   "systemInformation": {
     "cpu": {
-      "brand": "Xeon® E5-2673 v4",
+      "brand": "Xeon® E5-2673 v3",
       "cache": {
         "l1d": 65536,
         "l1i": 65536,
         "l2": 524288,
-        "l3": 52428800
+        "l3": 31457280
       },
       "cores": 2,
       "family": "6",
-      "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt md_clear",
+      "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single pti fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt md_clear",
       "governor": "",
       "manufacturer": "Intel®",
-      "model": "79",
+      "model": "63",
       "physicalCores": 2,
       "processors": 1,
       "revision": "",
       "socket": "",
-      "speed": 2.3,
+      "speed": 2.4,
       "speedMax": null,
       "speedMin": null,
-      "stepping": "1",
+      "stepping": "2",
       "vendor": "GenuineIntel",
       "virtualization": false,
       "voltage": ""
@@ -42,11 +42,11 @@
       "codename": "Focal Fossa",
       "codepage": "UTF-8",
       "distro": "Ubuntu",
-      "kernel": "5.8.0-1042-azure",
+      "kernel": "5.8.0-1040-azure",
       "logofile": "ubuntu",
       "platform": "linux",
       "release": "20.04.3 LTS",
-      "serial": "487dcaac68944409a00596acdb9a6fc0",
+      "serial": "cfc067bfcb844f35865e279a1b0e66c5",
       "servicepack": "",
       "uefi": false
     }

[trungleduc]

It works now on Binder

bug.mp4

[jtpio]

Nice.

I was wondering why we didn't have the Binder link posted on new PRs anymore, but that is because the benchmark workflow overwrites it:

[jtpio]

I was wondering why we didn't have the Binder link posted on new PRs anymore, but that is because the benchmark workflow overwrites it:

I was wondering why we didn't have the Binder link posted on new PRs anymore, but that is because the benchmark workflow overwrites it:

Tracked in #994

[jtpio]

Thanks!

[jtpio]

Looks like there is an ongoing issue with GitHub Actions at the moment (checks are not triggered):

Let's wait a bit before making the release as there still seems to be issues on GitHub side.

[trungleduc]

@jtpio it looks like GHA returned to normal now, we can cut a new alpha ?

[jtpio]

Sure. Was waiting for #996 but a couple of tests seem to be failing (probably flaky)

[trungleduc]

I think there is some real problems with my tests, I drafted #996 to fix it.

[jtpio]

@trungleduc https://github.com/voila-dashboards/voila/releases/tag/v0.3.0a1