MacOS Big Sur dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found (ESPTOOL-82) #540

jeksys · 2020-06-25T05:12:09Z

Operating system: MacOS Big Sur
Python version: Python 3.8.1

Full esptool.py command line as run:

esptool.py chip_id

Full output from esptool.py

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/bin/esptool.py", line 57, in <module>
    import serial.tools.list_ports as list_ports
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/serial/tools/list_ports.py", line 29, in <module>
    from serial.tools.list_ports_posix import comports
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/serial/tools/list_ports_posix.py", line 31, in <module>
    from serial.tools.list_ports_osx import comports
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/serial/tools/list_ports_osx.py", line 32, in <module>
    kIOMasterPortDefault = ctypes.c_void_p.in_dll(iokit, "kIOMasterPortDefault")
ValueError: dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found

What is the expected behaviour?

Connected device info

Do you have any other information from investigating this?

I worked before the MacOS upgrade

Is there any other information you can think of which will help us reproduce this problem?

The text was updated successfully, but these errors were encountered:

VladislavSmolyanoy · 2020-06-25T20:51:40Z

Same issue here!

projectgus · 2020-06-26T05:32:22Z

Hi @jeksys @SwiftySquirrel ,

Thanks for letting us know about this.

esptool relies on pyserial for serial port functionality, and this is where the exception is coming from. Ultimately whatever fix is required for MacOS Big Sur support will need to be applied there and then esptool will hopefully start working again.

Until then, the best we can do in esptool is apply a workaround so it's still possible to use esptool with a specific port specified on the command line, in the case that importing this utility function fails.

jeksys · 2020-06-26T06:31:42Z

@projectgus
Thank you for the suggestion. I think the additional parameter will work for some cases.
Though I think Arduio studio will still fail.
When do you think it is possible to make a release with a fix?

I reported the issue to pyserial
Though I think Arduio studio will still fail.

ehagerty · 2020-06-26T14:34:09Z

same issue here. forgive me if I'm being thick, but just putting --port /dev/tty.usbserial-xxxxxxxx flash-id for example gives the same error. did I misunderstand the suggestion of forcing the port parameter? Thanks so much, I should know better than to upgrade my primary machine!

projectgus · 2020-06-27T06:42:45Z

Yes, sorry I didn't explain clearly. The workaround is a potential one, it still involves a code change in esptool.

As a very quick hack you can try commenting this line in esptool.py:

  File "/Library/Frameworks/Python.framework/Versions/3.8/bin/esptool.py", line 57, in <module>
    import serial.tools.list_ports as list_ports

... and then always use the --port argument

...

I'm trying to get my hands on a Big Sur Preview install to do some more debugging.

xrolfex · 2020-06-27T20:16:23Z

@projectgus I can confirm that if you comment out the try: import block per your suggestion above it does work on Big Sur.

VladislavSmolyanoy · 2020-06-28T09:55:45Z

@xrolfex It doesn't for me...

XNinety9 · 2020-06-28T12:12:53Z

Same issue here when using esptool through PlatformIO:

xrolfex · 2020-06-28T13:11:47Z

@p-vernaeckt Are you explicitly using the —port option after commenting out the four lines?

ehagerty · 2020-06-30T12:37:23Z

Hi, sorry for the delay, can confirm:

OS11 Beta (20A4299v)
pyenv 1.2.19
pyenv-virtualenv 1.1.5
python 3.8.2
micropython esp32-idf4-20191220-v1.12.bin
esp32 (huzzah32 esp32-wroom32)

commenting out lines 56-61 of esptool.py and using the explicit --port works. Thank you!

JuanEL0 · 2020-07-04T02:03:07Z

Hi, I have the same issue on my mac with BigSur.

I'm using Arduino IDE and when I try to verify my code, it shows the same message.

I am totally new in this world and don't know how to configure the port from the Arduino IDE so I can not verify and load my code into my ESP8266.

If somebody has any idea about how to do it, I would appreciate it.

jeksys · 2020-07-08T06:50:59Z

The suggested fix worked for me.

Comment below lines in the file "/Library/Frameworks/Python.framework/Versions/3.8/bin/esptool.py"

#try:
#    import serial.tools.list_ports as list_ports
#except ImportError:
#    print("The installed version (%s) of pyserial appears to be too old for esptool.py (Python interpreter %s). "
#          "Check the README for installation instructions." % (sys.VERSION, sys.executable))
#    raise

List all available ports
ls /dev/tty.*
Use esptool.py with --port command
esptool.py --port /dev/tty.usbserial-01EED907 --baud 921600 erase_flash
Update esptool.py or env variable with a default port so esptool.py can be called without a parameter.
TODO

hpwit · 2020-07-26T12:44:19Z

A have a question which is linked to that I have python 3.7.7 installed and that is my current python but esptools via Arduino keep on trying to get to 2.7
File "esptool.py", line 57, in
File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
how to change that
i have reinstalled Arduino and also es-tools

ehagerty · 2020-08-20T17:31:47Z

NB, in case anyone is interested, this works for the v3.0-dev version of esptool.py in case you are using that with your s2 modules...

shurshun · 2020-08-22T10:11:58Z

NB, in case anyone is interested, this works for the v3.0-dev version of esptool.py in case you are using that with your s2 modules...

I guess we just have to find v3.0-dev version of esptool.py... Could you provide a link to this version, please?

acmdorio · 2020-08-25T16:37:31Z

Yes, sorry I didn't explain clearly. The workaround is a potential one, it still involves a code change in esptool.

As a very quick hack you can try commenting this line in esptool.py:
  File "/Library/Frameworks/Python.framework/Versions/3.8/bin/esptool.py", line 57, in <module>
    import serial.tools.list_ports as list_ports
... and then always use the --port argument

...

I'm trying to get my hands on a Big Sur Preview install to do some more debugging.

@projectgus Thanks, it works for me on BS 11.0 Beta (20A5354i)! By the way, a big thanks for your teamwork on this tool!
Maybe you should put this in esptool.py code as a test plus a warning before using the line 57, so other users barely note this issue. And brew update, then upgrade keep things working flawlessly. Just a humble idea. ;)

…view References: #540 pyserial/pyserial#509 The fix will probably come in a Python update before the Big Sur final release, there is a bundle of PRs including an apparent fix for the underlying issue here: https://bugs.python.org/issue41100

projectgus · 2020-08-27T10:25:15Z

Commit cb2060c is a workaround for this issue, so that esptool.py can run (without being able to detect the port). If you pull the latest master branch version of esptool.py (or follow the instructions in the README to install in "Development Mode" via GitHub) then no more modifications of the code should be required

It looks like the actual fix will come in a Python update once this issue is resolved: https://bugs.python.org/issue41100

Will keep this issue open, at least until the upstream issue is resolved.

R0dri · 2020-08-27T23:04:33Z

@projectgus Thankyou for the workaround. I can confirm esptool.py chip_id now catches the error instead of an abrupt termination of the process.

I've been trying to implement this to use arduino-cli or Arduinos own IDE with no luck. Inspecting the JSON board definition files i found arduino tries to compile the code not with python+esptool.py but with a binary stored in $arduino_packages/esp32/esptool_py/2.6.1/esptool which I guess its a compilation out of esptool.py.

I have never used esptool standalone and I don't know where to go next. Of course, I know I could wait for the actual python fix and keep using my raspberry pi for now. But I would love to learn a little more in the area. What would you recommend?

projectgus · 2020-08-27T23:30:56Z

@R0dri I'm not actually familiar with arduino-esp32 enough to give you an exact answer. However if you can get esptool.py master to run locally (by following the steps in the README for a development install) then you can probably update the Arduino platform.txt file here to specify a new path and command to run:
https://github.com/espressif/arduino-esp32/blob/ed96d2a1b70ea02d925435d06b71617bd451ffec/platform.txt#L6

exrector · 2020-09-04T18:32:43Z

Hey. I tried to apply a workaround and I got an error. What advice can you give? 😭

bash-3.2$ git clone https://github.com/espressif/esptool.git xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun bash-3.2$

petykowski · 2020-09-04T18:58:01Z

Hey. I tried to apply a workaround and I got an error. What advice can you give? 😭

`bash-3.2$ git clone https://github.com/espressif/esptool.git

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

bash-3.2$ `

This message is unrelated to the fix provided by Expressif. This error indicates that you need to update to the latest Xcode developer tools build.

exrector · 2020-09-04T20:58:38Z

Xcode
Thank you. But I have checked the versions and I have the latest 11.7.
Big Sur beta 11.0 (20A5364e)
Any variants? 😇
PS
I will try to install and update additional tools and Command Line Tools

petykowski · 2020-09-05T09:06:48Z

@exrector I am running the same configuration as described in your comment. Funny enough, I was experiencing error when attempting to commit to an unrelated repo. To resolve the issue, you should download the Apple Command Line Tools via the Developer Downloads portal, or via the direct link to the latest Xcode 12 tools here.

AndreasRavn · 2020-09-08T07:54:42Z

I've been trying to implement this to use arduino-cli or Arduinos own IDE with no luck. Inspecting the JSON board definition files i found arduino tries to compile the code not with python+esptool.py but with a binary stored in $arduino_packages/esp32/esptool_py/2.6.1/esptool which I guess its a compilation out of esptool.py.

I have never used esptool standalone and I don't know where to go next. Of course, I know I could wait for the actual python fix and keep using my raspberry pi for now. But I would love to learn a little more in the area. What would you recommend?

I changed line 6 and 7 in platform.txt from

tools.esptool_py.path={runtime.platform.path}/tools/esptool
tools.esptool_py.cmd=esptool

to

tools.esptool_py.path={runtime.platform.path}/tools
tools.esptool_py.cmd=esptool.py

that did the trick for me, the arduino IDE is now using esptool.py instead of the compiled binary in the subfolder.

dobairoland · 2020-12-07T10:56:46Z

@evoegelin All of your issues are Arduino related, right? You don't experience these with ESP-IDF directly?

The Big Sur workaround is available in the esptool's release/v2 branch as well.

evoegelin · 2020-12-07T11:18:36Z

@evoegelin All of your issues are Arduino related, right? You don't experience these with ESP-IDF directly?

The Big Sur workaround is available in the esptool's release/v2 branch as well.

Yes this all is only Arduino IDE related on a Mac after update to Big Sur.
With the exception of the SiLabs 210x USB-UART Driver, this is a general bug to Big Sur.

dobairoland · 2020-12-07T11:43:36Z

Yes this all is only Arduino IDE related on a Mac after update to Big Sur.

In this case I recommend to raise an issue there (if there isn't one already) and request to update to newer esptool.

With the exception of the SiLabs 210x USB-UART Driver, this is a general bug to Big Sur.

Unfortunately, we need to wait with this for a solution in Big Sur.

me-no-dev · 2020-12-07T12:46:55Z

I released 1.0.5-rc4 today that includes a rebuilt esptool for Mac. Make sure you uninstall the core first (esptool version is the same so it needs to first wipe all)

dobairoland · 2020-12-07T15:13:36Z

Great! Thank you @me-no-dev.

Elijahg · 2020-12-07T18:32:37Z

With the exception of the SiLabs 210x USB-UART Driver, this is a general bug to Big Sur.

I have a Heltec ESP32 dev board and it has a CP2102 UART which works fine with Big Sur. Installing the Silicon Labs drier may well break loading of the Apple SILabs driver as it did with a FTDI FT2232 I was using. So probably best to uninstall all traces of the SILabs kexts (could be in /Library/StagedExtensions or /Library/Extensions) and only use the Apple driver.

evoegelin · 2020-12-08T04:51:10Z

Thank you @me-no-dev.

I erased Arduino from my Mac and installed it new from the scratch. It's working properly. Thank you.
And using the Apple Driver for Hellten boards works fine too.

Thank you all.

omski · 2020-12-08T22:50:28Z

If anyone is still struggling to get pyserial updated on platformio. I found that I need to update it within the platformio python env itself (hint as per Arduino comments above). Once that was done it compiled again.
$ cd /Users/qoda/.platformio/
$ . penv/bin/activate
(penv) $ which pip
/Users/qoda/.platformio/penv/bin/pip
(penv) $ /Users/qoda/.platformio/penv/bin/pip install -U --pre pyserial
Collecting pyserial
  Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
Installing collected packages: pyserial
  Attempting uninstall: pyserial
    Found existing installation: pyserial 3.4
    Uninstalling pyserial-3.4:
      Successfully uninstalled pyserial-3.4
Successfully installed pyserial-3.5

This solved it for me on MacOs Big Sur with VSCode and Platform.io. No need to edit any line of python code anymore.

dobairoland · 2020-12-09T08:52:46Z

Thank you all for the responses. I'm closing this now because I consider it solved as I described before. Feel free to ping me if you disagree.

chris-schmitz · 2020-12-17T03:44:11Z

Thanks @me-no-dev, the 1.0.5-rc4 update got this working for my mac running big sur 🙇🏽

Something worth mentioning for other people that run into this issue is that to get this update (as of the typing of this comment) you need to use the Development Release json file instead of the Stable Release json. You can find details in the install readme.

https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json

I was super confused at firwst b/c I only saw 1.0.4. A bit of searching/reading set me straight :)

tenapier · 2020-12-19T17:44:35Z

Thank you Christopher Schmitz! First time in weeks now, that I can once again connect with my ESP32 and Mac, using Big Sur! I had tried a number of code workaround solutions, and nothing was working, until you put out the Board Manager Solution: Thanks so much, it's great to get reconnected again! https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json

…

On Wed, Dec 16, 2020 at 9:44 PM Christopher Schmitz < ***@***.***> wrote: Thanks @me-no-dev <https://github.com/me-no-dev>, the 1.0.5-rc4 update got this working for my mac running big sur 🙇🏽 Something worth mentioning for other people that run into this issue is that to get this update (as of the typing of this comment) you need to use the *Development Release* json file instead of the Stable Release json. You can find details in the install readme <https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/boards_manager.md> . https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json I was super confused at firwst b/c I only saw 1.0.4. A bit of searching/reading set me straight :) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#540 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJO4L5KPUVANJDNOK2J7U7DSVF5BZANCNFSM4OH3QGIA> .

Lilanga · 2021-01-04T13:09:54Z

Thank you @chris-schmitz. Dev channel board worked. still having the 1.0.5-rc4 as the latest.

chris-schmitz · 2021-01-04T13:45:06Z

Thank you Christopher Schmitz! First time in weeks now, that I can once
again connect with my ESP32 and Mac, using Big Sur! I had tried a number of
code workaround solutions, and nothing was working, until you put out the
Board Manager Solution:
Thanks so much, it's great to get reconnected again!

https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json

On Wed, Dec 16, 2020 at 9:44 PM Christopher Schmitz <
notifications@github.com> wrote:

Thanks @me-no-dev https://github.com/me-no-dev, the 1.0.5-rc4 update
got this working for my mac running big sur 🙇🏽

Something worth mentioning for other people that run into this issue is
that to get this update (as of the typing of this comment) you need to use
the Development Release json file instead of the Stable Release json.
You can find details in the install readme
https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/boards_manager.md
.

https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json

I was super confused at firwst b/c I only saw 1.0.4. A bit of
searching/reading set me straight :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#540 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJO4L5KPUVANJDNOK2J7U7DSVF5BZANCNFSM4OH3QGIA
.

No prob :) I didn't put out the release, just linked to it after I found it.

philolo1 · 2021-01-29T12:53:27Z

For everyone still reading this issue, this worked for me

pip install --upgrade  pyserial

kurosh-z · 2021-03-21T16:42:01Z

For everyone still reading this issue, this worked for me
pip install --upgrade  pyserial 

Hi
I have still problem although I have upgraded the pyserial. I'm still getting this error:

Traceback (most recent call last):
  File "esptool.py", line 57, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports.py", line 29, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_posix.py", line 31, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_osx.py", line 32, in <module>
ValueError: dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found
Failed to execute script esptool
exit status 255
/Applications/Arduino.app/Contents/Java/arduino-builder returned 255
Error compiling for board Wireless Stick.

any idea what could be causing this?

electronic-cosmos · 2021-03-24T09:36:48Z

WEMos and M5 is working but for DOIT and a lot of other boards bring folloing Massage:

esptool.py v2.9-dev
Serial port /dev/cu.usbserial-0001
Connecting......................................____Beim Hochladen des Sketches ist ein Fehler aufgetreten
_

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header

does anybody can tell me what is going wrong?

bfaliszek · 2021-03-24T11:28:30Z

@electronic-cosmos it looks like a physical connection error. Check that everything is properly connected

josmanperez · 2021-04-08T19:51:16Z

For everyone still reading this issue, this worked for me
pip install --upgrade  pyserial 

Hi
I have still problem although I have upgraded the pyserial. I'm still getting this error:

Traceback (most recent call last):
  File "esptool.py", line 57, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports.py", line 29, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_posix.py", line 31, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_osx.py", line 32, in <module>
ValueError: dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found
Failed to execute script esptool
exit status 255
/Applications/Arduino.app/Contents/Java/arduino-builder returned 255
Error compiling for board Wireless Stick.

any idea what could be causing this?

This is happening for me as well, I haven't solved it yet
@kurosh-z , have you managed to solve it?

Thanks

Elijahg · 2021-04-08T19:54:22Z

For everyone still reading this issue, this worked for me
pip install --upgrade  pyserial 

Hi
I have still problem although I have upgraded the pyserial. I'm still getting this error:

Traceback (most recent call last):
  File "esptool.py", line 57, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports.py", line 29, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_posix.py", line 31, in <module>
  File "/Library/Python/2.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "serial/tools/list_ports_osx.py", line 32, in <module>
ValueError: dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found
Failed to execute script esptool
exit status 255
/Applications/Arduino.app/Contents/Java/arduino-builder returned 255
Error compiling for board Wireless Stick.

any idea what could be causing this?

This is happening for me as well, I haven't solved it yet
@kurosh-z , have you managed to solve it?

Thanks

Try this. You can probably just follow the replace esptool part.

josmanperez · 2021-04-09T18:22:30Z

Thanks @Elijahg . It worked!

Imikbel · 2021-11-12T05:51:28Z

https://docs.python-guide.org/starting/install3/osx/
After that: pip install --upgrade pyserial
Problem solved ;)

jeksys added the bug label Jun 25, 2020

jeksys mentioned this issue Jun 26, 2020

esptool fails on MacOS Big Sur preview: Failure to import serial.tools.list_ports pyserial/pyserial#509

Open

sumanthratna mentioned this issue Jun 30, 2020

Unable to import on macOS Big Sur vispy/vispy#1885

Closed

dobairoland mentioned this issue Sep 4, 2020

endless mistakes (IDFGH-3930) espressif/esp-idf#5820

Closed

exrector mentioned this issue Sep 6, 2020

Add wiki errors list kistanovdev/esp-idf-macos-setup#1

Closed

github-actions bot changed the title ~~MacOS Big Sur dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found~~ MacOS Big Sur dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found (ESPTOOL-82) Dec 8, 2020

dobairoland closed this as completed Dec 9, 2020

pmirabel mentioned this issue Feb 1, 2021

Floower Flasher crash MacOS jpraus/floower#6

Closed

dependabot bot mentioned this issue Mar 7, 2021

Bump esptool from 2.8 to 3.0 Y0rk-code/esphome#1

Closed

dependabot bot mentioned this issue Mar 14, 2021

Bump esptool from 2.8 to 3.0 sashao/esphome#4

Closed

dobairoland mentioned this issue Jun 27, 2021

Problem with compiling with Arduino and Big Sur and esptool.py (ESPTOOL-261) #636

Closed

This was referenced Jun 19, 2022

idf.py monitor doesn't connect ctag-fh-kiel/ctag-tbd#62

Closed

httpd_txrx errors, timeouts ctag-fh-kiel/ctag-tbd#63

Closed

nitin710 mentioned this issue Apr 20, 2023

Updating esptool shipped with EmotiBit firmware installer EmotiBit/ofxEmotiBit#200

Merged

MacOS Big Sur dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found (ESPTOOL-82) #540

MacOS Big Sur dlsym(RTLD_DEFAULT, kIOMasterPortDefault): symbol not found (ESPTOOL-82) #540

Comments

jeksys commented Jun 25, 2020

Full esptool.py command line as run:

Full output from esptool.py

What is the expected behaviour?

Do you have any other information from investigating this?

Is there any other information you can think of which will help us reproduce this problem?

VladislavSmolyanoy commented Jun 25, 2020

projectgus commented Jun 26, 2020

jeksys commented Jun 26, 2020

ehagerty commented Jun 26, 2020

projectgus commented Jun 27, 2020

xrolfex commented Jun 27, 2020

VladislavSmolyanoy commented Jun 28, 2020

XNinety9 commented Jun 28, 2020

xrolfex commented Jun 28, 2020 • edited

ehagerty commented Jun 30, 2020 • edited

JuanEL0 commented Jul 4, 2020

jeksys commented Jul 8, 2020

hpwit commented Jul 26, 2020

ehagerty commented Aug 20, 2020

shurshun commented Aug 22, 2020

acmdorio commented Aug 25, 2020

projectgus commented Aug 27, 2020 • edited

R0dri commented Aug 27, 2020

projectgus commented Aug 27, 2020 • edited

exrector commented Sep 4, 2020

petykowski commented Sep 4, 2020

exrector commented Sep 4, 2020 • edited

petykowski commented Sep 5, 2020 • edited

AndreasRavn commented Sep 8, 2020 • edited

dobairoland commented Dec 7, 2020

evoegelin commented Dec 7, 2020 • edited

dobairoland commented Dec 7, 2020

me-no-dev commented Dec 7, 2020

dobairoland commented Dec 7, 2020

Elijahg commented Dec 7, 2020

evoegelin commented Dec 8, 2020 • edited

omski commented Dec 8, 2020

dobairoland commented Dec 9, 2020

chris-schmitz commented Dec 17, 2020

tenapier commented Dec 19, 2020 via email

Lilanga commented Jan 4, 2021

chris-schmitz commented Jan 4, 2021

philolo1 commented Jan 29, 2021

kurosh-z commented Mar 21, 2021

electronic-cosmos commented Mar 24, 2021

bfaliszek commented Mar 24, 2021

josmanperez commented Apr 8, 2021

Elijahg commented Apr 8, 2021 • edited

josmanperez commented Apr 9, 2021

Imikbel commented Nov 12, 2021

xrolfex commented Jun 28, 2020 •

edited

ehagerty commented Jun 30, 2020 •

edited

projectgus commented Aug 27, 2020 •

edited

projectgus commented Aug 27, 2020 •

edited

exrector commented Sep 4, 2020 •

edited

petykowski commented Sep 5, 2020 •

edited

AndreasRavn commented Sep 8, 2020 •

edited

evoegelin commented Dec 7, 2020 •

edited

evoegelin commented Dec 8, 2020 •

edited

Elijahg commented Apr 8, 2021 •

edited