00:34 <_whitenotifier-9> [sphinx_materialdesign_theme] mithro opened issue #2: Fix the rendering of line numbers - https://git.io/JfqJu

00:39 <_whitenotifier-9> [sphinx_materialdesign_theme] mithro opened issue #3: Make little link icons appear near headers in the documentation - https://git.io/JfqJK

00:40 <_whitenotifier-9> [sphinx_materialdesign_theme] mithro opened issue #4: Make sure the docs are still usable when javascript is disabled - https://git.io/JfqJi

00:41 <_whitenotifier-9> [sphinx_symbiflow_theme] mithro opened issue #4: Figure out if we can delete this repository - https://git.io/JfqJM

00:52 <_whitenotifier-9> [ideas] mithro opened issue #49: Create a symbiflow-sphinx-docs-common repository - https://git.io/JfqJF

03:41 <mithro> @daniellimws It looks like you have ended up with both a `README.md` and `README.rst`file in https://github.com/SymbiFlow/python-symbiflow-v2x/pull/42/files which is what is confusing us :-P

03:41 <tpb> Title: Update documentation for clock examples by daniellimws · Pull Request #42 · SymbiFlow/python-symbiflow-v2x · GitHub (at github.com)

03:41 <daniellimws> mithro: Haha yes I forgot we changed it in another pull request

04:00 <mithro> I think I'm going to call it a night shortly...

08:10 <_whitenotifier-9> [fpga-tool-perf] acomodi opened issue #83: Manage conda packages that need specific versions - https://git.io/JfqO6

16:21 <daniellimws> mithro: Have an exam in the morning so going to sleep now. Not sure if there is a setting that you need to change on the readthedocs website for that error.

16:25 <mithro> daniellimws: Please do!

16:25 <mithro> daniellimws: (Go to sleep and do well in your exam!)

16:48 <sf-slack> <timo.callahan> Hi all, I have a FUZZING question -- I'm working on Artix7 *100T* parts. In PrjXray, I added a new setting file and adjusted the Makefile, and made target "db-part-only-artix7_100t". For fuzzer 074-dump-all, I ran analyze_errors.pl to generate the new ignored wires file, which looked good, and checked it in at 074-dump_all/ignored_wires/artix7/xc7a100tfgg676-1_ignored_wires.txt. After this, the make

16:48 <sf-slack> finished successfully (fuzzers 000, 001, 005, and 074). THE QUESTION is -- what is the next step?

17:20 <litghost> Make a PR?

18:07 <sf-slack> <timo.callahan> So it's ready for some testing? Are there any sanity checks / small tests I can run? One thing I was concerned about is that the new tileconn.json for the 100T is smaller than the file for 50T. Although there's not much difference between the 50T and 200T, so maybe it's not something that scales with the number of tiles: `12272 -rw-rw-r-- 1 tcal tcal 12565618 Apr 24 19:07 xc7a200tffg1156-1/tileconn.json

18:07 <sf-slack> 12272 -rw-rw-r-- 1 tcal tcal 12565618 Apr 24 19:07 xc7a200tsbg484-1/tileconn.json 11604 -rw-rw-r-- 1 tcal tcal 11881775 Apr 24 19:07 xc7a35tcpg236-1/tileconn.json 11604 -rw-rw-r-- 1 tcal tcal 11881775 Apr 24 19:07 xc7a35tcsg324-1/tileconn.json 11604 -rw-rw-r-- 1 tcal tcal 11881775 Apr 24 19:07 xc7a35tftg256-1/tileconn.json 11604 -rw-rw-r-- 1 tcal tcal 11881775 Apr 24 19:07 xc7a50tfgg484-1/tileconn.json 8404 -rw-rw-r-- 1 tcal

18:07 <sf-slack> tcal 8601612 Apr 27 01:21 xc7a100tfgg676-1/tileconn.json`

18:09 <litghost> 074 does a verifcation check, and if the check passes, and the ignored wire list seems reasonable, then it might be right

18:10 <litghost> tileconn can be very small if the graph is very very regular

18:24 <sf-slack> <timo.callahan> Is the usual process to just send a PR on prjxray, and let CI rebuild the database, or to also fork prjxray-db and make a PR with the updates there as well?

18:25 <litghost> Always start with a PR on prjxray

18:26 <sf-slack> <timo.callahan> Ok thanks

18:26 <litghost> Once that is merged, the CI will rebuild, and mithro will update prjxray-db when you ask

20:00 <hackerfoo> Could I please get a review for a very short PR? https://github.com/SymbiFlow/uxsdcxx/pull/51

20:00 <tpb> Title: Add conditional mach/error.h include for compatibility by HackerFoo · Pull Request #51 · SymbiFlow/uxsdcxx · GitHub (at github.com)

20:34 <sf-slack> <timo.callahan> Hi Dusty, LGTM, but I don't know if my comment or approval does you any good.. let me know if it's useful.

20:36 <hackerfoo> Thanks. litghost?