Add Missing XML Comments for Public Members

Currently, the codebase contains public members without corresponding XML comments (CS1591 warning). This issue is created to track and ensure the addition of proper documentation for these elements.

[ ] PublicKeyCredentialRpEntity needs an actual description

I suggest the one from the WebAuthn spec, even though it doesn't really include the possibility for a FIDO2 implementation in a native app:

The entity whose web application utilizes the Web Authentication API to register and authenticate users

[ ] Fido2User needs a description

As the spec only has use case specific descriptions, I suggest something like this:

Represents a user account for usage with the WebAuthn API.

[ ] AssertionOptions.Create has no description, but it's basically just a static method calling the constructor

This can be changed to just be a normal constructor. Either way this can get a simple description like:

Creates a new AssertionOptions object.

[ ] AuthenticatorAssertionRawResponse is just a DTO generated by the browser, but I think the members do deserve descriptions

I can't find this in the spec, but I do like the MDN descriptions, even though they have to be adapted for our strict public-key use case.
Id

base64url encoding of RawId

That should be a <see... link to the RawId member.
RawId

Globally unique identifier for this credential. This identifier can be used to look up credentials.

Response

The signed response data from the authenticator.

Really unsure about this one since that could also be the description of the AssertionResponse type itself.
Type

Type of this credential. Always public-key.

ClientExtensionResults

If any extensions were requested, this contains the results of processing those extensions

I did find the AssertionResponse in the spec:
AssertionResponse.AuthenticatorData

Contains the authenticator data returned by the authenticator.

Although maybe that is a bit too redundant, so we could expand it slightly:

Contains the authenticator data returned by the authenticator, describing it to the relying party in order to make trust decisions.

AssertionResponse.Signature

Contains the raw signature returned from the authenticator.

Maybe with a link to https://www.w3.org/TR/webauthn-2/#sctn-op-get-assertion
AssertionResponse.ClientDataJson

Contains the JSON-compatible serialization of client data (see § 5.8.1 Client Data Used in WebAuthn Signatures (dictionary CollectedClientData)) passed to the authenticator by the client in order to generate this assertion. The exact JSON serialization MUST be preserved, as the hash of the serialized client data has been computed over it.

AssertionResponse.UserHandle

Contains the user handle returned from the authenticator, or null if the authenticator did not return a user handle.


example for Generic Concrete Ultimate Profile in materials.rst

Hi @robbievanleeuwen
In going through implementing #80, I've noted the following doesn't seem consistent in the numbers utilised.
The example in material.rst implies a variable youngs modulus E for the strain calculations, and stresses provided max out at 40MPa but compressive strength is defined as only 32 MPa so inputs don't seem consistent with one another. Maybe I'm missing something here though, but it seems like this needs to be modified to a constant E consistent with the specified compressive strength and the maximum compressive strength and max stress aligned so they are the same value?
from concreteproperties.stress_strain_profile import ConcreteUltimateProfile

ConcreteUltimateProfile(
  strains=[-20 / 30e3, 0, 20 / 30e3, 30 / 25e3, 40 / 20e3, 0.003],
  stresses=[0, 0, 20, 30, 40, 40],
  compressive_strength=32,
).plot_stress_strain()

I think this is a case where ultimate_strain (don't think this is even initiated for this generic profile or parent class which would presumably cause some issues if it was used for a design_code check) and possibly compressive_strength should possibly just be populated from the user input at the end of the __post_init__ method and not initiate compressive_strength as an input:-
i.e. self.ultimate_strain = max(self.strains), and similar for the concrete_strength variable.

Hi @Agent6-6-6, this example is inconsistent, the compressive strength should be modified compressive_strength=40. I'll update this once this discussion is closed out.
As far as I'm aware, no other modules access the ultimate_strain or compressive_strength variables. Instead they use the get_ultimate_compressive_strain() and get_compressive_strength() methods.
I believe the get_ultimate_compressive_strain() method is consistent with the inputs.
The get_compressive_strength() allows for a different 'compressive strength' to that in a profile which may be useful in some cases (the only time I use it in AS3600 is to compute the squash load). This is a 'generic' profile so the user can really do what they want with it. The other abstracted profiles generate the stress-strain profile from the compressive strength so do not allow for inconsistency.
Does this answer the question?

Hi @robbievanleeuwen, hopefully, the following makes sense!
In the NZS3101 class, I was directly accessing these ultimate_strain and compressive_strength variables when creating the different sections for the various types of analysis. The reason for doing this was the outcome of issue #47.
I guess what is required to populate these variables so they can be accessed is to simply run these get_xxxx methods at the end of the creation of the profiles if the user did not provide them (i..e don't initiate them but populate with the correct value anyway so it can be accessed directly if required):-

do this before adding any horizontal portions of the curve required for interpolation (which would mean the max(strain) would not return the true specified or intended ultimate_strain value,
and before applying any alpha factor reductions that might apply to get from the max strength being the characteristic value specified and the final design value for the compressive_strength. (similar to how ultimate_strain was initiated in the modified mander profile as an example).

As it stands for some of the profiles if I'm interpreting it correctly the ultimate_strain is equal to None as it is never initiated if not specifically required to generate the profile. But for completeness, I'm saying it probably should be initiated with the correct value so all profiles have valid values irrespectively if that makes sense. Some analyses may require it (as per NZS3101 class implementation as noted above, and other future codes may require it also). Sure you can get the value using the get_ultimate_compressive_strain but that value would include any extra bits added on for interpolation purposes. For example, in EC2 service profile you have a 1.01 x factor which could throw a max permissible strain returned out by 1% if used or others are following the same logic (note that I've yet to update this profile with the calculations for the ultimate_strain).
Also for the EC2 profiles that are being worked on in #80, they will have to work in a similar way populating the values at the end because there is no input ultimate_strain as that is calculated in accordance with the equations in table 3.1 of EC2 for example.
The idea is if I have not already done it would be to populate this value at the end of the generation of the profile so it can be returned and isn't equal to None as it has never been populated otherwise if I'm following how some profiles are working?
I have always been interpreting the compressive_strength for ultimate analyses as being the specified characteristic value, and for a design, value to be returned which has been factored down by whatever equivalent alpha factor might apply based on the analysis code or analysis being undertaken.


Localization fixes for deploy in non-English default tenants

These fixes allow deployment on a Spanish default SharePoint Online tenant that sets the default LCID of new Communication sites to a value other than 1033.  Further RESX files have to be added for other language support.
Category

[x] Bug Fix
[ ] New Feature
Related issues: fixes #17

What's in this Pull Request?

Resource folder with two localized RESX files for the en-us and es-es locales. More RESX files would need to be added to support additional languages.
Changes to deploy.ps1 to detect the LCID of the newly created Communication site and call the provisioning template with the proper LCID.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: larslynch sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

thank you Lars!


CP2102 OSX drivers? [solved: make sure your USB cable is OK]

Where do I find working drivers for OSX 10.10 (Yosemite)?

I have OSX 10.10.3 on MBP11,2
I downloaded OSX drivers from the vendor website (direct zip download)
Unpacked the ZIP, mounted DMG file, installed using the PKG installer.
Restarted computer
I connected NodeMcu devkit v1.0 through USB 3.0 port

There is a file/folder /Library/Extensions/SiLabsUSBDriver.kext, but no serial port available for the device.
$ ls -lah /dev/cu*
crw-rw-rw-  1 root  wheel   18,   1 Jul  8 13:32 /dev/cu.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   3 Jul  8 13:32 /dev/cu.Bluetooth-Modem
crw-rw-rw-  1 root  wheel   18,   5 Jul  8 13:32 /dev/cu.DadaFon4-WirelessiAP

$ ls -lah /dev/tty.*
crw-rw-rw-  1 root  wheel   18,   0 Jul  8 13:32 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   2 Jul  8 13:32 /dev/tty.Bluetooth-Modem
crw-rw-rw-  1 root  wheel   18,   4 Jul  8 13:32 /dev/tty.DadaFon4-WirelessiAP

No success with ESPlorer and Arduino IDE.

EDIT 1
Apparently it works for some people (?), but not for me: http://blog.squix.ch/2015/05/esp8266-flashing-nodemcu-v10-on-mac-os.html

EDIT 2:
It looks like the kext isn't loaded?
$ kextstat
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
    1   92 0xffffff7f80a3e000 0x8c50     0x8c50     com.apple.kpi.bsd (14.3.0)
    2    7 0xffffff7f80f9c000 0x28c0     0x28c0     com.apple.kpi.dsep (14.3.0)
    3  118 0xffffff7f80a03000 0x20500    0x20500    com.apple.kpi.iokit (14.3.0)
    4  125 0xffffff7f80a24000 0xbf50     0xbf50     com.apple.kpi.libkern (14.3.0)
    5  108 0xffffff7f80a00000 0x2d50     0x2d50     com.apple.kpi.mach (14.3.0)
    6   53 0xffffff7f80a30000 0x8590     0x8590     com.apple.kpi.private (14.3.0)
    7   71 0xffffff7f80a39000 0x4900     0x4900     com.apple.kpi.unsupported (14.3.0)
    8    4 0xffffff7f80da3000 0x9c000    0x9c000    com.apple.kec.corecrypto (1.0) <7 6 5 4 3 1>
    9    0 0xffffff7f80ea4000 0xc000     0xc000     com.apple.kec.pthread (1) <7 6 5 4 1>
   10    1 0xffffff7f80fd5000 0x9000     0x9000     com.apple.kec.Libm (1) <4>
   11   23 0xffffff7f813b7000 0x9000     0x9000     com.apple.iokit.IOACPIFamily (1.4) <7 6 4 3>
   12   31 0xffffff7f80b24000 0x2f000    0x2f000    com.apple.iokit.IOPCIFamily (2.9) <7 6 5 4 3>
   13    2 0xffffff7f82956000 0x5f000    0x5f000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>
   14    1 0xffffff7f810a5000 0xb000     0xb000     com.apple.driver.AppleFDEKeyStore (28.30) <8 7 6 5 4 3 1>
   15    2 0xffffff7f813b0000 0x7000     0x7000     com.apple.iokit.IOReportFamily (31) <5 4 3>
   16   10 0xffffff7f80a47000 0x26000    0x26000    com.apple.iokit.IOStorageFamily (2.0) <7 6 5 4 3 1>
   17    0 0xffffff7f814a7000 0x19000    0x19000    com.apple.driver.DiskImages (396) <16 7 6 5 4 3 1>
   18    1 0xffffff7f822ce000 0xf000     0xf000     com.apple.driver.AppleCredentialManager (1.0) <7 5 4 3 1>
   19    2 0xffffff7f80fa2000 0xd000     0xd000     com.apple.driver.AppleMobileFileIntegrity (1.0.5) <7 6 5 4 3 2 1>
   20    0 0xffffff7f822dd000 0x23000    0x23000    com.apple.driver.AppleKeyStore (2) <19 18 8 7 6 5 4 3 1>
   21    0 0xffffff7f80f9f000 0x2000     0x2000     com.apple.security.TMSafetyNet (8) <7 6 5 4 2 1>
   22    2 0xffffff7f80faf000 0x5000     0x5000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
   23    1 0xffffff7f80fb4000 0x17000    0x17000    com.apple.security.sandbox (300.0) <22 19 7 6 5 4 3 2 1>
   24    0 0xffffff7f80fcb000 0x9000     0x9000     com.apple.security.quarantine (3) <23 22 7 6 5 4 2 1>
   25    0 0xffffff7f829cc000 0x8000     0x8000     com.apple.nke.applicationfirewall (161) <7 6 5 4 3 1>
   26    0 0xffffff7f82929000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.7) <4 3>
   27    3 0xffffff7f81358000 0x4000     0x4000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
   28    0 0xffffff7f829bb000 0x7000     0x7000     com.apple.driver.AppleACPIEC (3.1) <27 13 11 5 4 3>
   29    0 0xffffff7f821e9000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (2.1) <7 4 3>
   30    0 0xffffff7f82546000 0x3000     0x3000     com.apple.driver.AppleHPET (1.8) <11 7 5 4 3>
   31    6 0xffffff7f810b0000 0x76000    0x76000    com.apple.iokit.IOHIDFamily (2.0.0) <14 7 6 5 4 3 2 1>
   32    0 0xffffff7f829c5000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (3.1) <31 13 11 7 6 5 4 3 1>
   33    0 0xffffff7f8220a000 0x8000     0x8000     com.apple.driver.AppleRTC (2.0) <11 5 4 3 1>
   34    1 0xffffff7f825bb000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (2.0) <7 6 5 4 3>
   35    0 0xffffff7f821d1000 0x8000     0x8000     com.apple.driver.AppleSmartBatteryManager (161.0.0) <27 11 5 4 3 1>
   36    1 0xffffff7f825c0000 0xb000     0xb000     com.apple.driver.AppleEFINVRAM (2.0) <34 7 6 5 4 3 1>
   37   16 0xffffff7f8101d000 0x65000    0x65000    com.apple.iokit.IOUSBFamily (720.4.4) <12 7 5 4 3 1>
   38    0 0xffffff7f81158000 0x22000    0x22000    com.apple.driver.AppleUSBXHCI (710.4.11) <37 12 7 5 4 3 1>
   39    5 0xffffff7f80fde000 0x2c000    0x2c000    com.apple.iokit.IONetworkingFamily (3.2) <7 6 5 4 3 1>
   40    1 0xffffff7f816de000 0x7000     0x7000     com.apple.driver.mDNSOffloadUserClient (1.0.1b8) <39 4 3 1>
   41    1 0xffffff7f816e5000 0xab000    0xab000    com.apple.iokit.IO80211Family (730.60) <39 8 7 6 5 4 3 1>
   42    0 0xffffff7f81798000 0x5e6000   0x5e6000   com.apple.driver.AirPort.Brcm4360 (930.37.3) <41 40 39 12 7 6 5 4 3 1>
   43    7 0xffffff7f8123f000 0xde000    0xde000    com.apple.iokit.IOThunderboltFamily (4.2.2) <5 4 3 1>
   44    0 0xffffff7f820f1000 0x1b000    0x1b000    com.apple.driver.AppleThunderboltNHI (3.1.7) <43 12 11 5 4 3 1>
   45    0 0xffffff7f820df000 0x5000     0x5000     com.apple.driver.AppleThunderboltPCIDownAdapter (2.0.2) <43 12 5 4 3 1>
   46    3 0xffffff7f82133000 0xf000     0xf000     com.apple.driver.AppleThunderboltDPAdapterFamily (4.0.6) <43 11 5 4 3 1>
   47    0 0xffffff7f8215d000 0x6000     0x6000     com.apple.driver.AppleThunderboltDPInAdapter (4.0.6) <46 43 5 4 3 1>
   48    3 0xffffff7f81686000 0x16000    0x16000    com.apple.iokit.IOAHCIFamily (2.7.5) <5 4 3 1>
   49    0 0xffffff7f8292e000 0x1b000    0x1b000    com.apple.driver.AppleAHCIPort (3.1.2) <48 12 5 4 3 1>
   50    0 0xffffff7f816ac000 0x9000     0x9000     com.apple.iokit.IOAHCIPassThrough (1.0.3) <48 5 4 3 1>
   51    0 0xffffff7f816b9000 0x18000    0x18000    com.apple.iokit.IOAHCIBlockStorage (2.7.1) <48 16 6 5 4 3 1>
   52    0 0xffffff7f81fb9000 0x3000     0x3000     com.apple.driver.XsanFilter (404) <16 5 4 3 1>
   53    0 0xffffff7f811bd000 0x1c000    0x1c000    com.apple.driver.AppleUSBHub (705.4.2) <37 5 4 3 1>
   54    0 0xffffff7f81ef5000 0xa000     0xa000     com.apple.BootCache (36) <7 6 5 4 3 1>
   55    0 0xffffff7f8284c000 0x2000     0x2000     com.apple.driver.AppleFileSystemDriver (3.0.1) <16 4 3>
   56    0 0xffffff7f82850000 0x5000     0x5000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
   57    0 0xffffff7f82857000 0x3000     0x3000     com.apple.AppleFSCompression.AppleFSCompressionTypeDataless (1.0.0d1) <7 6 4 3 2 1>
   58    1 0xffffff7f81df7000 0xde000    0xde000    com.apple.driver.CoreStorage (471.20.7) <16 7 6 5 4 3 1>
   59    0 0xffffff7f81edb000 0x16000    0x16000    com.apple.driver.CoreStorageFsck (471.20.7) <58 16 7 6 5 4 3 1>
   60    1 0xffffff7f8114e000 0xa000     0xa000     com.apple.driver.AppleUSBComposite (705.4.9) <37 4 3 1>
   61    0 0xffffff7f811b6000 0x7000     0x7000     com.apple.driver.AppleUSBMergeNub (705.4.0) <60 37 4 3 1>
   62    4 0xffffff7f80ae2000 0x2b000    0x2b000    com.apple.iokit.IOSCSIArchitectureModelFamily (3.7.5) <5 4 3 1>
   63    1 0xffffff7f8108e000 0x11000    0x11000    com.apple.iokit.IOUSBMassStorageClass (3.7.2) <62 37 16 5 4 3 1>
   64    1 0xffffff7f80eb0000 0x18000    0x18000    com.apple.iokit.IOSCSIBlockCommandsDevice (3.7.5) <62 16 5 4 3 1>
   65    0 0xffffff7f821b6000 0x8000     0x8000     com.apple.driver.AppleUSBCardReader (3.5.5) <64 63 62 37 16 5 4 3 1>
   66    0 0xffffff7f8135c000 0x7000     0x7000     com.apple.iokit.SCSITaskUserClient (3.7.5) <62 16 5 4 3 1>
   67    3 0xffffff7f81144000 0xa000     0xa000     com.apple.iokit.IOUSBHIDDriver (705.4.0) <37 31 5 4 3 1>
   68    0 0xffffff7f81ff2000 0x4000     0x4000     com.apple.driver.AppleUSBTCKeyboard (240.2) <67 37 31 7 6 5 4 3 1>
   69    0 0xffffff7f81ff8000 0x2000     0x2000     com.apple.driver.AppleUSBTCKeyEventDriver (240.2) <31 5 4 3>
   70    0 0xffffff7f82001000 0x13000    0x13000    com.apple.driver.AppleUSBMultitouch (245.2) <67 37 31 6 5 4 3 1>
   71    0 0xffffff7f81ffc000 0x3000     0x3000     com.apple.driver.AppleUSBTCButtons (240.2) <67 37 31 7 6 5 4 3 1>
   72   16 0xffffff7f81450000 0x3b000    0x3b000    com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1>
   73    1 0xffffff7f8227b000 0xe000     0xe000     com.apple.driver.AppleSMBusController (1.0.13d1) <27 12 11 5 4 3>
   74    0 0xffffff7f8228c000 0xe000     0xe000     com.apple.driver.AppleMCCSControl (1.2.11) <73 72 12 11 7 5 4 3 1>
   75    4 0xffffff7f81497000 0x10000    0x10000    com.apple.iokit.IONDRVSupport (2.4.1) <72 12 7 5 4 3>
   76    6 0xffffff7f813ca000 0x1a000    0x1a000    com.apple.driver.AppleSMC (3.1.9) <11 7 5 4 3 1>
   77    2 0xffffff7f82820000 0x5000     0x5000     com.apple.driver.AppleBacklightExpert (1.1.0) <75 72 12 5 4 3>
   78    0 0xffffff7f82921000 0x5000     0x5000     com.apple.driver.AppleBacklight (170.7.4) <77 76 75 72 12 5 4 3>
   79    2 0xffffff7f8281d000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.10.22) <72 12 11 7 5 4 3 1>
   80    0 0xffffff7f82825000 0x14000    0x14000    com.apple.driver.AppleMuxControl (3.10.22) <79 77 72 12 11 7 6 5 4 3 1>
   81    1 0xffffff7f82142000 0xe000     0xe000     com.apple.driver.AppleThunderboltDPOutAdapter (4.0.6) <46 43 5 4 3 1>
   82    0 0xffffff7f82150000 0xd000     0xd000     com.apple.driver.AppleThunderboltEDMSink (4.0.2) <81 46 43 5 4 3 1>
   83    6 0xffffff7f813c0000 0xa000     0xa000     com.apple.driver.IOPlatformPluginFamily (5.9.1d7) <11 7 6 5 4 3>
   84    1 0xffffff7f813e6000 0x17000    0x17000    com.apple.driver.X86PlatformPlugin (1.0.0) <83 76 37 11 7 6 5 4 3 1>
   85    1 0xffffff7f81406000 0x12000    0x12000    com.apple.driver.IOPlatformPluginLegacy (1.0.0) <83 11 7 6 5 4 3>
   86    0 0xffffff7f8141a000 0x10000    0x10000    com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) <85 83 76 12 11 7 6 5 4 3>
   87    1 0xffffff7f8134e000 0x5000     0x5000     com.apple.iokit.IOSlowAdaptiveClockingFamily (1.0.0) <7 6 5 4 3 1>
   88    0 0xffffff7f82300000 0x2000     0x2000     com.apple.driver.AppleIntelSlowAdaptiveClocking (4.0.0) <87 4 3>
   89    2 0xffffff7f8234f000 0x6f000    0x6f000    com.apple.iokit.IOAcceleratorFamily2 (156.14) <72 12 7 6 5 4 3 1>
   90    3 0xffffff7f82456000 0x6000     0x6000     com.apple.AppleGraphicsDeviceControl (3.10.22) <7 6 5 4 3 1>
   91    0 0xffffff7f8245c000 0x4b000    0x4b000    com.apple.driver.AppleIntelFramebufferAzul (10.0.6) <90 89 72 15 12 11 7 6 5 4 3 1>
   92    0 0xffffff7f82860000 0xa8000    0xa8000    com.apple.driver.AppleCameraInterface (5.33.0) <12 7 6 5 4 3 1>
   93    0 0xffffff7f821de000 0x5000     0x5000     com.apple.driver.AppleSMCLMU (2.0.7d0) <76 72 5 4 3>
   94    1 0xffffff7f810a2000 0x3000     0x3000     com.apple.iokit.IOUSBUserClient (705.4.0) <37 7 5 4 3 1>
   95    0 0xffffff7f821e6000 0x3000     0x3000     com.apple.driver.AppleSMBusPCI (1.0.12d1) <12 5 4 3>
   96    2 0xffffff7f81f01000 0x78000    0x78000    com.apple.vecLib.kext (1.2.0) <10 6 5 4 3>
   97    4 0xffffff7f81f79000 0x30000    0x30000    com.apple.iokit.IOAudioFamily (203.3) <96 5 4 3 1>
   98    2 0xffffff7f82579000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (272.18) <5 4 3 1>
   99    1 0xffffff7f8258c000 0x1c000    0x1c000    com.apple.driver.AppleHDAController (272.18) <98 97 72 12 7 6 5 4 3 1>
  100    0 0xffffff7f822c6000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <83 12 5 4 3>
  101    0 0xffffff7f82111000 0x17000    0x17000    com.apple.driver.AppleThunderboltIP (2.0.2) <43 39 12 5 4 3 1>
  102    0 0xffffff7f8285b000 0x3000     0x3000     com.apple.driver.AppleFIVRDriver (4.1.0) <4 3>
  103    0 0xffffff7f82508000 0xb000     0xb000     com.apple.driver.AppleHV (1) <7 6 5 4 3 1>
  104    0 0xffffff7f82503000 0x3000     0x3000     com.apple.driver.AppleHWAccess (1) <7 5 4 3>
  105    1 0xffffff7f81339000 0x13000    0x13000    com.apple.iokit.IOSurface (97.4) <7 5 4 3 1>
  106    0 0xffffff7f823cc000 0x60000    0x60000    com.apple.driver.AppleIntelHD5000Graphics (10.0.6) <105 89 72 12 7 6 5 4 3 1>
  107    0 0xffffff7f81df1000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <76 7 4 3 1>
  108    2 0xffffff7f8154a000 0xab000    0xab000    com.apple.iokit.IOBluetoothFamily (4.3.4f4) <15 7 5 4 3 1>
  109    0 0xffffff7f81011000 0x6000     0x6000     com.apple.iokit.IOUserEthernet (1.0.1) <39 6 5 4 3 1>
  110    1 0xffffff7f81605000 0x23000    0x23000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (4.3.4f4) <108 37 12 11 7 5 4 3 1>
  111    0 0xffffff7f81628000 0x9000     0x9000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (4.3.4f4) <110 108 37 12 11 7 5 4 3>
  112    0 0xffffff7f81533000 0x2000     0x2000     com.apple.iokit.IOBluetoothUSBDFU (4.3.4f4) <37 4 3>
  113    0 0xffffff7f81fc2000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.6.1) <72 12 11 7 5 4 3 1>
  114    1 0xffffff7f825a8000 0x13000    0x13000    com.apple.kext.OSvKernDSPLib (1.15) <5 4>
  115    1 0xffffff7f825cb000 0x131000   0x131000   com.apple.driver.DspFuncLib (272.18) <114 97 96 36 6 5 4 3 1>
  116    0 0xffffff7f82706000 0xab000    0xab000    com.apple.driver.AppleHDA (272.18) <115 99 98 97 75 72 6 5 4 3 1>
  117    0 0xffffff7f82841000 0x7000     0x7000     com.apple.driver.AppleGraphicsDevicePolicy (3.7.7) <90 79 72 12 11 7 6 5 4 3 1>
  118    0 0xffffff7f82269000 0x4000     0x4000     com.apple.driver.AppleOSXWatchdog (1) <12 7 6 5 4 3 1>
  119    0 0xffffff7f82588000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (272.18) <4 3>
  120    1 0xffffff7f813fd000 0x7000     0x7000     com.apple.driver.X86PlatformShim (1.0.0) <84 83 76 7 4 3>
  121    0 0xffffff7f82800000 0x14000    0x14000    com.apple.driver.AGPM (110.19.5) <90 83 75 72 12 5 4 3>
  122    0 0xffffff7f82262000 0x4000     0x4000     com.apple.driver.ApplePlatformEnabler (2.2.0d4) <7 5 4 3>
  123    1 0xffffff7f8120b000 0xe000     0xe000     com.apple.iokit.IOSerialFamily (11) <7 6 5 4 3 1>
  124    0 0xffffff7f81536000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (4.3.4f4) <123 7 5 4 3 1>
  125    2 0xffffff7f80e3f000 0x5000     0x5000     com.apple.kext.triggers (1.0) <7 6 5 4 3 1>
  126    0 0xffffff7f80f91000 0x9000     0x9000     com.apple.filesystems.autofs (3.0) <125 7 6 5 4 3 1>
  127    0 0xffffff7f81fb1000 0x5000     0x5000     com.apple.driver.AudioAUUC (1.70) <97 72 12 11 7 5 4 3 1>
  128    3 0xffffff7f829d6000 0x58000    0x58000    org.virtualbox.kext.VBoxDrv (4.3.28) <7 5 4 3 1>
  129    0 0xffffff7f82a2e000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (4.3.28) <128 94 37 7 5 4 3 1>
  130    0 0xffffff7f82a36000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (4.3.28) <128 7 5 4 3 1>
  131    0 0xffffff7f82a3b000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (4.3.28) <128 5 4 1>
  132    0 0xffffff7f80e44000 0x59000    0x59000    com.apple.filesystems.smbfs (3.0.1) <125 8 7 6 5 4 3 1>

Edit 3:
$ kextutil -tn /Library/Extensions/SiLabsUSBDriver.kext
/Library/Extensions/SiLabsUSBDriver.kext appears to be loadable (including linkage for on-disk libraries).

Edit 4:
The device does work, as I can join its network and ping it.

@squix78 Apparently you've got this working – any details?
Did it just work OOTB? What OSX version? What model of Mac?
Do you see the kext being loaded in kextstat? (not sure if this should show it…)

SiLabs' drivers worked out of the box for me (OS X Yosemite). They are signed so there's no need to turn off checks in the OS.
There's some issues I've had and I cannot say for sure if they are due to the drivers: I can use NodeMCU devkit 1.0 with screen and ESPlorer in general but I was not able to make it work with mini-com nor have I been able to flash it with esptool. These things worked for me onESP01 and different USB-serial adapter.

@marcoskirsch Could you please paste what kextstat shows you? Is the driver listed there? What's your exact OSX/Mac?

OS X Yosemite 10.10.4 (14E46)
MacBook Pro (Retina, 13-inch, Early 2015) 3.1 GHz Intel Core i7
kextstat (scroll to the bottom):
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
    1   89 0xffffff7f80a0f000 0x8c50     0x8c50     com.apple.kpi.bsd (14.4.0)
    2    7 0xffffff7f80e66000 0x28c0     0x28c0     com.apple.kpi.dsep (14.4.0)
    3  112 0xffffff7f80a1d000 0x20500    0x20500    com.apple.kpi.iokit (14.4.0)
    4  120 0xffffff7f80a03000 0xbf50     0xbf50     com.apple.kpi.libkern (14.4.0)
    5  103 0xffffff7f80a00000 0x2d50     0x2d50     com.apple.kpi.mach (14.4.0)
    6   49 0xffffff7f80a3e000 0x8590     0x8590     com.apple.kpi.private (14.4.0)
    7   68 0xffffff7f80a18000 0x4900     0x4900     com.apple.kpi.unsupported (14.4.0)
    8    4 0xffffff7f80e6c000 0xa0000    0xa0000    com.apple.kec.corecrypto (1.0) <7 6 5 4 3 1>
    9    0 0xffffff7f80fa4000 0xc000     0xc000     com.apple.kec.pthread (1) <7 6 5 4 1>
   10    1 0xffffff7f80fd4000 0x9000     0x9000     com.apple.kec.Libm (1) <4>
   11   24 0xffffff7f8140f000 0x9000     0x9000     com.apple.iokit.IOACPIFamily (1.4) <7 6 4 3>
   12   30 0xffffff7f80a47000 0x2f000    0x2f000    com.apple.iokit.IOPCIFamily (2.9) <7 6 5 4 3>
   13    2 0xffffff7f829e5000 0x5f000    0x5f000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>
   14    1 0xffffff7f81125000 0xb000     0xb000     com.apple.driver.AppleFDEKeyStore (28.30) <8 7 6 5 4 3 1>
   15    2 0xffffff7f81408000 0x7000     0x7000     com.apple.iokit.IOReportFamily (31) <5 4 3>
   16    7 0xffffff7f80b2d000 0x26000    0x26000    com.apple.iokit.IOStorageFamily (2.0) <7 6 5 4 3 1>
   17    0 0xffffff7f8150f000 0x19000    0x19000    com.apple.driver.DiskImages (397) <16 7 6 5 4 3 1>
   18    1 0xffffff7f8232c000 0xf000     0xf000     com.apple.driver.AppleCredentialManager (1.0) <7 5 4 3 1>
   19    2 0xffffff7f80f71000 0xd000     0xd000     com.apple.driver.AppleMobileFileIntegrity (1.0.5) <7 6 5 4 3 2 1>
   20    0 0xffffff7f8233b000 0x23000    0x23000    com.apple.driver.AppleKeyStore (2) <19 18 8 7 6 5 4 3 1>
   21    0 0xffffff7f80e69000 0x2000     0x2000     com.apple.security.TMSafetyNet (8) <7 6 5 4 2 1>
   22    2 0xffffff7f80f7e000 0x5000     0x5000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
   23    1 0xffffff7f80f83000 0x17000    0x17000    com.apple.security.sandbox (300.0) <22 19 7 6 5 4 3 2 1>
   24    0 0xffffff7f80f9a000 0x9000     0x9000     com.apple.security.quarantine (3) <23 22 7 6 5 4 2 1>
   25    0 0xffffff7f82a5b000 0x8000     0x8000     com.apple.nke.applicationfirewall (161) <7 6 5 4 3 1>
   26    0 0xffffff7f829b8000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.7) <4 3>
   27    3 0xffffff7f81395000 0x4000     0x4000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
   28    0 0xffffff7f82a4a000 0x7000     0x7000     com.apple.driver.AppleACPIEC (3.1) <27 13 11 5 4 3>
   29    0 0xffffff7f8223f000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (2.1) <7 4 3>
   30    0 0xffffff7f825e8000 0x3000     0x3000     com.apple.driver.AppleHPET (1.8) <11 7 5 4 3>
   31    0 0xffffff7f8226d000 0x8000     0x8000     com.apple.driver.AppleRTC (2.0) <11 5 4 3 1>
   32    5 0xffffff7f81130000 0x76000    0x76000    com.apple.iokit.IOHIDFamily (2.0.0) <14 7 6 5 4 3 2 1>
   33    0 0xffffff7f82a54000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (3.1) <32 13 11 7 6 5 4 3 1>
   34    0 0xffffff7f82245000 0x8000     0x8000     com.apple.driver.AppleSmartBatteryManager (161.0.0) <27 11 5 4 3 1>
   35    1 0xffffff7f82649000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (2.0) <7 6 5 4 3>
   36    1 0xffffff7f8264e000 0xb000     0xb000     com.apple.driver.AppleEFINVRAM (2.0) <35 7 6 5 4 3 1>
   37    1 0xffffff7f82388000 0xa000     0xa000     com.apple.driver.AppleIntelLpssGspi (2.0.57) <12 11 7 5 4 3>
   39    1 0xffffff7f82369000 0x8000     0x8000     com.apple.driver.AppleIntelLpssDmac (2.0.57) <12 11 5 4 3>
   40   14 0xffffff7f80a7b000 0x65000    0x65000    com.apple.iokit.IOUSBFamily (720.4.4) <12 7 5 4 3 1>
   41    0 0xffffff7f811ce000 0x22000    0x22000    com.apple.driver.AppleUSBXHCI (710.4.11) <40 12 7 5 4 3 1>
   42    1 0xffffff7f82392000 0x14000    0x14000    com.apple.driver.AppleIntelLpssSpiController (2.0.57) <39 37 11 5 4 3>
   43    1 0xffffff7f825bb000 0x17000    0x17000    com.apple.driver.AppleHSSPISupport (41.3) <42 11 5 4 3 1>
   44    6 0xffffff7f810d2000 0x2c000    0x2c000    com.apple.iokit.IONetworkingFamily (3.2) <7 6 5 4 3 1>
   45    1 0xffffff7f8173e000 0x7000     0x7000     com.apple.driver.mDNSOffloadUserClient (1.0.1b8) <44 4 3 1>
   46    1 0xffffff7f81745000 0xab000    0xab000    com.apple.iokit.IO80211Family (730.60) <44 8 7 6 5 4 3 1>
   47    0 0xffffff7f817f8000 0x5e6000   0x5e6000   com.apple.driver.AirPort.Brcm4360 (930.37.3) <46 45 44 12 7 6 5 4 3 1>
   48    5 0xffffff7f81286000 0xde000    0xde000    com.apple.iokit.IOThunderboltFamily (4.2.2) <5 4 3 1>
   49    0 0xffffff7f82154000 0x1b000    0x1b000    com.apple.driver.AppleThunderboltNHI (3.1.7) <48 12 11 5 4 3 1>
   50    2 0xffffff7f820db000 0x24000    0x24000    com.apple.driver.AppleMultitouchDriver (264.6) <32 5 4 3 1>
   51    0 0xffffff7f825d5000 0x9000     0x9000     com.apple.driver.AppleHSSPIHIDDriver (41.3) <50 43 32 5 4 3 1>
   52    0 0xffffff7f82116000 0x6000     0x6000     com.apple.driver.AppleTopCaseHIDEventDriver (67) <50 32 6 5 4 3 1>
   53    0 0xffffff7f82105000 0x8000     0x8000     com.apple.driver.AppleHIDKeyboard (176.2) <32 4 3>
   54    0 0xffffff7f82142000 0x5000     0x5000     com.apple.driver.AppleThunderboltPCIDownAdapter (2.0.2) <48 12 5 4 3 1>
   55    1 0xffffff7f82196000 0xf000     0xf000     com.apple.driver.AppleThunderboltDPAdapterFamily (4.0.6) <48 11 5 4 3 1>
   56    0 0xffffff7f821c0000 0x6000     0x6000     com.apple.driver.AppleThunderboltDPInAdapter (4.0.6) <55 48 5 4 3 1>
   57    2 0xffffff7f816e6000 0x16000    0x16000    com.apple.iokit.IOAHCIFamily (2.7.5) <5 4 3 1>
   58    0 0xffffff7f829bd000 0x1b000    0x1b000    com.apple.driver.AppleAHCIPort (3.1.2) <57 12 5 4 3 1>
   60    0 0xffffff7f81719000 0x18000    0x18000    com.apple.iokit.IOAHCIBlockStorage (2.7.1) <57 16 6 5 4 3 1>
   61    0 0xffffff7f82024000 0x3000     0x3000     com.apple.driver.XsanFilter (404) <16 5 4 3 1>
   62    0 0xffffff7f81f55000 0xa000     0xa000     com.apple.BootCache (36) <7 6 5 4 3 1>
   63    0 0xffffff7f828da000 0x6000     0x6000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0) <6 4 3 2 1>
   64    0 0xffffff7f828e2000 0x3000     0x3000     com.apple.AppleFSCompression.AppleFSCompressionTypeDataless (1.0.0d1) <7 6 4 3 2 1>
   66    0 0xffffff7f81e57000 0xde000    0xde000    com.apple.driver.CoreStorage (471.30.1) <16 7 6 5 4 3 1>
   68    0 0xffffff7f8122c000 0x1c000    0x1c000    com.apple.driver.AppleUSBHub (705.4.2) <40 5 4 3 1>
   69    0 0xffffff7f814a8000 0xc000     0xc000     com.apple.driver.AppleUSBEthernet (2.4.13) <44 40 7 5 4 3 1>
   70    1 0xffffff7f80c1d000 0xa000     0xa000     com.apple.driver.AppleUSBComposite (705.4.9) <40 4 3 1>
   72    0 0xffffff7f80c27000 0x7000     0x7000     com.apple.driver.AppleUSBMergeNub (705.4.0) <70 40 4 3 1>
   73    3 0xffffff7f80bc8000 0x2b000    0x2b000    com.apple.iokit.IOSCSIArchitectureModelFamily (3.7.5) <5 4 3 1>
   74    1 0xffffff7f81111000 0x11000    0x11000    com.apple.iokit.IOUSBMassStorageClass (3.7.2) <73 40 16 5 4 3 1>
   75    1 0xffffff7f80fb0000 0x18000    0x18000    com.apple.iokit.IOSCSIBlockCommandsDevice (3.7.5) <73 16 5 4 3 1>
   76    0 0xffffff7f82219000 0x8000     0x8000     com.apple.driver.AppleUSBCardReader (3.5.5) <75 74 73 40 16 5 4 3 1>
   78   15 0xffffff7f814b8000 0x3b000    0x3b000    com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1>
   79    2 0xffffff7f82403000 0x6f000    0x6f000    com.apple.iokit.IOAcceleratorFamily2 (156.16) <78 12 7 6 5 4 3 1>
   80    3 0xffffff7f82480000 0x7000     0x7000     com.apple.AppleGraphicsDeviceControl (3.10.24) <7 6 5 4 3 1>
   81    0 0xffffff7f82487000 0x54000    0x54000    com.apple.driver.AppleIntelBDWGraphicsFramebuffer (10.0.6) <80 79 78 15 12 11 7 6 5 4 3 1>
   82    4 0xffffff7f814ff000 0x10000    0x10000    com.apple.iokit.IONDRVSupport (2.4.1) <78 12 7 5 4 3>
   83    1 0xffffff7f81380000 0x13000    0x13000    com.apple.iokit.IOSurface (97.4) <7 5 4 3 1>
   84    0 0xffffff7f824fa000 0x79000    0x79000    com.apple.driver.AppleIntelBDWGraphics (10.0.6) <83 79 78 12 7 6 5 4 3 1>
   85    1 0xffffff7f81399000 0x5000     0x5000     com.apple.iokit.IOSlowAdaptiveClockingFamily (1.0.0) <7 6 5 4 3 1>
   86    0 0xffffff7f82365000 0x2000     0x2000     com.apple.driver.AppleIntelSlowAdaptiveClocking (4.0.0) <85 4 3>
   87    0 0xffffff7f825aa000 0xb000     0xb000     com.apple.driver.AppleHV (1) <7 6 5 4 3 1>
   88    0 0xffffff7f825a5000 0x3000     0x3000     com.apple.driver.AppleHWAccess (1) <7 5 4 3>
   89    5 0xffffff7f81422000 0x1a000    0x1a000    com.apple.driver.AppleSMC (3.1.9) <11 7 5 4 3 1>
   90    0 0xffffff7f81e51000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <89 7 4 3 1>
   91    2 0xffffff7f8159b000 0xad000    0xad000    com.apple.iokit.IOBluetoothFamily (4.3.5f8) <15 7 5 4 3 1>
   92    0 0xffffff7f81105000 0x6000     0x6000     com.apple.iokit.IOUserEthernet (1.0.1) <44 6 5 4 3 1>
   95    0 0xffffff7f82174000 0x17000    0x17000    com.apple.driver.AppleThunderboltIP (2.0.2) <48 44 12 5 4 3 1>
   96    4 0xffffff7f81418000 0xa000     0xa000     com.apple.driver.IOPlatformPluginFamily (5.9.1d7) <11 7 6 5 4 3>
   97    1 0xffffff7f8143e000 0x17000    0x17000    com.apple.driver.X86PlatformPlugin (1.0.0) <96 89 40 11 7 6 5 4 3 1>
  100    0 0xffffff7f828ef000 0xa8000    0xa8000    com.apple.driver.AppleCameraInterface (5.36.0) <12 7 6 5 4 3 1>
  101    2 0xffffff7f813a3000 0xe000     0xe000     com.apple.iokit.IOSerialFamily (11) <7 6 5 4 3 1>
  103    2 0xffffff7f81f6c000 0x78000    0x78000    com.apple.vecLib.kext (1.2.0) <10 6 5 4 3>
  104    4 0xffffff7f81fe4000 0x30000    0x30000    com.apple.iokit.IOAudioFamily (203.3) <103 5 4 3 1>
  105    2 0xffffff7f82607000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (272.18.1) <5 4 3 1>
  106    1 0xffffff7f8261a000 0x1c000    0x1c000    com.apple.driver.AppleHDAController (272.18.1) <105 104 78 12 7 6 5 4 3 1>
  109    0 0xffffff7f82324000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <96 12 5 4 3>
  110    0 0xffffff7f82234000 0x5000     0x5000     com.apple.driver.AppleSMCLMU (2.0.7d0) <89 78 5 4 3>
  111    1 0xffffff7f822d9000 0xe000     0xe000     com.apple.driver.AppleSMBusController (1.0.13d1) <27 12 11 5 4 3>
  112    0 0xffffff7f822ea000 0xe000     0xe000     com.apple.driver.AppleMCCSControl (1.2.12) <111 78 12 11 7 5 4 3 1>
  113    1 0xffffff7f828ae000 0x5000     0x5000     com.apple.driver.AppleBacklightExpert (1.1.0) <82 78 12 5 4 3>
  114    0 0xffffff7f829b0000 0x5000     0x5000     com.apple.driver.AppleBacklight (170.7.4) <113 89 82 78 12 5 4 3>
  115    1 0xffffff7f828ab000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.10.24) <78 12 11 7 5 4 3 1>
  117    1 0xffffff7f80aec000 0x3000     0x3000     com.apple.iokit.IOUSBUserClient (705.4.0) <40 7 5 4 3 1>
  118    1 0xffffff7f82636000 0x13000    0x13000    com.apple.kext.OSvKernDSPLib (1.15) <5 4>
  119    1 0xffffff7f82659000 0x131000   0x131000   com.apple.driver.DspFuncLib (272.18.1) <118 104 103 36 6 5 4 3 1>
  120    0 0xffffff7f82794000 0xab000    0xab000    com.apple.driver.AppleHDA (272.18.1) <119 106 105 104 82 78 6 5 4 3 1>
  121    1 0xffffff7f81683000 0x23000    0x23000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (4.3.5f8) <91 40 12 11 7 5 4 3 1>
  122    0 0xffffff7f816a6000 0x9000     0x9000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (4.3.5f8) <121 91 40 12 11 7 5 4 3>
  124    0 0xffffff7f820d2000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.6.1) <78 12 11 7 5 4 3 1>
  125    0 0xffffff7f828cf000 0x7000     0x7000     com.apple.driver.AppleGraphicsDevicePolicy (3.7.7) <115 80 78 12 11 7 6 5 4 3 1>
  126    0 0xffffff7f822cc000 0x4000     0x4000     com.apple.driver.AppleOSXWatchdog (1) <12 7 6 5 4 3 1>
  127    0 0xffffff7f8166f000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (4.3.5f8) <101 7 5 4 3 1>
  128    0 0xffffff7f82a65000 0x2000     0x2000     com.radiosilenceapp.nke.PrivateEye (1) <4 1>
  129    1 0xffffff7f80aef000 0x3c000    0x3c000    org.virtualbox.kext.VBoxDrv (3.1.4) <7 5 4 3 1>
  130    0 0xffffff7f82a67000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (3.1.4) <129 117 40 7 5 4 3 1>
  131    1 0xffffff7f81455000 0x7000     0x7000     com.apple.driver.X86PlatformShim (1.0.0) <97 96 89 7 4 3>
  132    0 0xffffff7f822c5000 0x4000     0x4000     com.apple.driver.ApplePlatformEnabler (2.2.0d4) <7 5 4 3>
  133    0 0xffffff7f8288e000 0x14000    0x14000    com.apple.driver.AGPM (110.19.6) <96 82 80 78 12 5 4 3>
  136    0 0xffffff7f8201c000 0x5000     0x5000     com.apple.driver.AudioAUUC (1.70) <104 78 12 11 7 5 4 3 1>
  137    2 0xffffff7f80f0c000 0x5000     0x5000     com.apple.kext.triggers (1.0) <7 6 5 4 3 1>
  138    0 0xffffff7f81f61000 0x9000     0x9000     com.apple.filesystems.autofs (3.0) <137 7 6 5 4 3 1>
  142    0 0xffffff7f82a6f000 0x59000    0x59000    com.apple.filesystems.smbfs (3.0.1) <137 8 7 6 5 4 3 1>
  143    0 0xffffff7f82ac8000 0xe000     0xe000     com.apple.nke.asp-tcp (8.0.0) <7 6 5 4 3 1>
  144    1 0xffffff7f82ad6000 0x11000    0x11000    com.apple.security.SecureRemotePassword (1.0) <5 4 1>
  145    0 0xffffff7f82ae7000 0x53000    0x53000    com.apple.filesystems.afpfs (11.0) <144 7 6 5 4 3 1>
  191    0 0xffffff7f82b3a000 0x4000     0x4000     com.apple.driver.AppleUSBCDC (4.3.3b1) <40 4 3>
  192    0 0xffffff7f82b3e000 0x6000     0x6000     com.silabs.driver.CP210xVCPDriver (4.1.1) <101 40 4 3>

@marcoskirsch Thx, you do have the kext loaded… com.silabs.driver.CP210xVCPDriver (4.1.1)
The question is: why is it not my case? How do I debug this?

http://community.silabs.com/t5/Interface/OS-X-10-10-CP210x-VCP-Driver-Release-Candidate/td-p/138472
$ codesign -vvvvd /Library/Extensions/SiLabsUSBDriver.kext/
Executable=/Library/Extensions/SiLabsUSBDriver.kext/Contents/MacOS/SiLabsUSBDriver
Identifier=com.silabs.driver.CP210xVCPDriver
Format=bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=497 flags=0x0(none) hashes=17+3 location=embedded
Hash type=sha1 size=20
CDHash=8cc52c4b61556244b230f7e6eed6b18dce4b763d
Signature size=8584
Authority=Developer ID Application: Silicon Laboratories Inc (52444FG85C)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=23 Jun 2015 21:34:41
Info.plist entries=18
TeamIdentifier=52444FG85C
Sealed Resources version=2 rules=12 files=2
Internal requirements count=1 size=228

$ kextutil -tn /Library/Extensions/SiLabsUSBDriver.kext
/Library/Extensions/SiLabsUSBDriver.kext appears to be loadable (including linkage for on-disk libraries).

But it doesn't tell me anything…

Does /dev/cu.SLAB_USBtoUART exist? I'm not sure it creates a tty.
Try the following:
# Unplug your NodeMCU
ioreg -w 0 > ~/no-device.txt
# Plug your NodeMCU in
ioreg -w 0 > ~/with-device.txt
diff ~/with-device.txt ~/no-device.txt > ~/diff-device.txt

and upload diff-device.txt as a gist?
There's also a ~known issue with some serial bridges where they have trouble on USB3 - the workaround is to plug in a USB1/USB2 hub in to the USB3 port and then plug your device in to the hub.

Does /dev/cu.SLAB_USBtoUART exist?
@abl It did not.

Anyway, it works. I just had a bad cable (3 of them o.O). After I plugged in a borrowed Samsung phone cable it started working o.O
I guess it's true that same USB cables are only for the power and not every USB cable can exchange data…

$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port	/dev/tty.DadaFon4-WirelessiAP
/dev/tty.Bluetooth-Modem		/dev/tty.SLAB_USBtoUART

:D

Exact same problem here. I tried 2 cables already but no SiLabs com port yet..
Any way to quickly validate if the cable is the issue or not?

I'm having the same problem on OSX 10.11.3. The cable is definitely good because it works perfectly fine in a Windows VM on the same machine.

Not working in el capitan 10.11.3 !! :/ works perfectly on windows machine though

I am also facing the exact same issue. It gets detected for the first time and then "error: cannot access /dev/cu.SLAB_USBtoUART" appears. After restart then it again detects and same issue.

Hi Guys,
It looks like this is because the official driver is not signed and in 10.10 & 10.11 they have kext signing :-(
The solution which worked for me is to install this driver from another vendor which is signed, but works just fine!
http://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/

I am experiencing the same issue on OS X 10.11.5 (MacBook Pro (Retina, 15-inch, Mid 2014)), using a Wemos D1 Mini and an Amazon USB Cable.
The kernel extension is loaded:
> kextstat | grep -i silabs
  151    0 0xffffff7f832ab000 0x6000     0x6000     com.silabs.driver.CP210xVCPDriver (4.10.11) CF83A369-EA70-3E24-B8FE-7351DCF03430 <123 39 4 3>

But there is no /dev/tty.SLAB_USBtoUART:
> ls tty.*
tty.Bluetooth-Incoming-Port

Under System Information the USB device (when attached) shows up as USB2.0-Serial  under the USB 3.0 Bus  tree:
USB 3.0 Bus:

  Host Controller Driver:	AppleUSBXHCILPTH
  PCI Device ID:	0x8c31
  PCI Revision ID:	0x0005
  PCI Vendor ID:	0x8086

...

USB2.0-Serial:

  Product ID:	0x7523
  Vendor ID:	0x1a86
  Version:	2.54
  Speed:	Up to 12 Mb/sec
  Location ID:	0x14200000 / 12
  Current Available (mA):	1000
  Extra Operating Current (mA):	0

I have diff'd the results of ioreg as suggested above at gist'd at
https://gist.github.com/fadushin/d4c17e73be26cece8e8cddb6edd704bb
I am disinclined to install an unsigned kernel extension or otherwise not readily downloadable from a reputable vendor, particularly if it is reported to cause kernel panics.
And, hi, @bosschaert !

I installed the Arduino IDE with the ESP8266 addon (as described here https://learn.sparkfun.com/tutorials/esp8266-thing-hookup-guide/installing-the-esp8266-arduino-addon ) and the /dev/cu.SLAB_USBtoUART magically appeared for me. I'm unsure whether it came with the Arduino IDE or with the addon, but its now just working for me.
PS hi @fadushin !

Silly me.  My Wemos D1 Mini uses a CH340G chip, not the CP2102 (my son's magnifying glass comes in handy).  Of course that driver won't work.  Using the driver with the right chip actually works.
> kextstat | grep -i silabs
  158    0 0xffffff7f83281000 0x6000     0x6000     com.silabs.driver.CP210xVCPDriver (4.10.11) CF83A369-EA70-3E24-B8FE-7351DCF03430 <123 39 4 3>

> ls tty.*
tty.Bluetooth-Incoming-Port	tty.SLAB_USBtoUART

NB.  The CH340G driver can be found at
http://www.wemos.cc/downloads/
And instructions are at
http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html

If someone runs into such an issue, really DO check many cables.
I run into the exact same steps than @MacDada and nothing worked.
I have 2 Mac running Sierra and my ESP8266 works in one and not the other. I could validate a cable to be working on my iMac but it would not on my MBP2016.
I tested randomly many cables, some work, some don´t. Most of those cables usually work fine.
Conclusion: do test many cables....

Try to use a USB hub with a power source, like this one: https://i.stack.imgur.com/pzG2u.gif
I had issues when I was trying to use a Presonus Audiobox USB - I've bought this hub, plugged it at the power source and plugged the hardware at the hub and then the USB hub at the Mac book Air's USB port.

Guys, can you help me. I've just got my NODEMCU ESP-12e with CP2102 (1.0), I'm using a MAC AIR, but the device doesn't appear on the PORT list, as some of the guys above. I'be tried different cables as well a USB interface that allows me to input an extra 5V DC PSU to feed the NODEMCU, no response at all. The Blink sketch compiles OK, the board is correctly set for NODEMCU 1.0 (ESP-12e Module), but no way to make it works. I heard that I should download a driver for CP2102, is it right? If so, where can I find it? Any help? Thanks!

I just experienced this exact same issue.  It ended up taking me a couple hours to figure it out, but I established a highly technical definition of the problem:
My cable was bad
🤦♂

TL;DR: Use a short fat cable
I'm going to go ahead and say it is a cable problem, but not a bad cable. I had to try every single one of the dozen or so that I have and I'm not throwing any of them away after this. Consistent with  @chevdor, the short, fat cable did the trick, which would seem to suggest that for some reason the tiny voltage drop across a longer or thinner cable makes the signal from the CP2102 just too weak for the chipset on a mac to interpret, which is an absurd explanation. I suppose I could pull out the old oscilloscope to validate that but....
Anyways, I had to steal the cable from my wife so I'm ordering this one (https://www.amazon.com/gp/product/B013G4EAEI) off amazon. If it doesn't work I'm sure I'll be back with some oscilloscope tracings.
Happy cable hunting!

Same issues.
Ended up here.
Tried better cable.
Showed up right away!
Thank you, all!

What kind of cables are you guys using that are working? I'm having this issue right now, and the ~18 anker powerline cable (along with 3 or 4 others) are all not showing the device. Seems ridiculous that it could be this sensitive to which cable is needed

@jacobtarter
Well, depending on the issue, it might not be your cable.
After all the troubleshooting steps I followed, the cable ended up being the issue for me.
And it's because not all cables are equal.

Some only do power, some do data but poorly.
I can tell you with certainty that this is by FAAAAAAAR not the only tech that's picky about which cable you use.

In the first place you should avoid using Anker cables made for CHARGING.
There is no reason why charging cables would be good with data
(unfortunately). Just buy 1 good quality cable that is also not too long.
Good luck. Those issues are annoying...
On Mon, Sep 11, 2017, 12:44 Simon<EMAIL_ADDRESS>wrote:

@jacobtarter https://github.com/jacobtarter
Well, depending on the issue, it might not be your cable.
After all the troubleshooting steps I followed, the cable ended up being
the issue for me.
And it's because not all cables are equal.

Some only do power, some do data but poorly.
I can tell you with certainty that this is by FAAAAAAAR not the only tech
that's picky about which cable you use.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodemcu/nodemcu-devkit-v1.0/issues/2#issuecomment-328492426,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtFpI1yclYEfciwdzXpP1WnThiYsbswks5shQ77gaJpZM4FUW90
.

The cable I was using wasn't a power only cable, although anker does make those (power line + I think theyre called).
Anyway, I hooked it up to an older desktop running elementary os and it detected it immediately.

Thanks @fadushin !!  I have an esp32 by Wemos and it's the same chip as you ....
Doing this and restart did it:
brew tap mengbo/ch340g-ch34g-ch34x-mac-os-x-driver https://github.com/mengbo/ch340g-ch34g-ch34x-mac-os-x-driver
brew cask install wch-ch34x-usb-serial-driver

So to be clear, NodeMCU ESP12E devkit boards come with different Serial chips.
Some have a SiLabs CP210x.
Some have a WCH (Winchiphead) CH340.
You can tell which you have by plugging the board into your Mac and then opening System Information. Go to Hardware -> USB. Find the There'll be a USB2.0-Serial device.
A CH340 will have Vendor ID: 0x1a86 and Product ID: 0x7523.
SiLabs website says their Vendor ID is 0x10C4 and the Product ID is 0xEA60,  0xEA70 or 0xEA71.
The latest Mac drivers for the CH340 can be found here direct from WCH (version 1.4 released Jan 2017):
http://www.wch.cn/download/CH341SER_MAC_ZIP.html
The works with my MacOSX Sierra 10.12.6.
Most documentation seems to assume you have a SiLabs CP210x chip, so if you end up here because your serial driver isn't working (like I did), hopefully you'll find this useful.

Thank you guys, solved this problem by reinstalling the driver.

For what it is worth I will add some information regarding this issue.
Short story nodeMCU 1.0 devkit on mpb from 2013. Could not see any drivers in /dev folder. Only did see bluetooth entry in /dev/ from esplorer.
So, the drivers from silabs was the problem. When you install something on high sierra (and before?) there is a security measure that won't allow unsigned drivers to install. Looking into it i found that
MBP:Extensions user$ sudo kextutil -tn /Library/Extensions/SiLabsUSBDriver.kext
Password:
Kext rejected due to system policy: <OSKext 0x7ffbc27082c0 [0x7fff9d917980]> { URL = "file:///Library/StagedExtensions/Library/Extensions/SiLabsUSBDriver.kext/", ID = "com.silabs.driver.CP210xVCPDriver" }
Kext rejected due to system policy: <OSKext 0x7ffbc27082c0 [0x7fff9d917980]> { URL = "file:///Library/StagedExtensions/Library/Extensions/SiLabsUSBDriver.kext/", ID = "com.silabs.driver.CP210xVCPDriver" }
Diagnostics for /Library/Extensions/SiLabsUSBDriver.kext:
Warnings:
    Dependency lacks appropriate value for OSBundleRequired and may not be available during early boot:
        com.apple.iokit.IOSerialFamily - Safe Boot

I did not see any error when running the installer from silabs. But if you go to
System preferences -> Security & Drivers
there will be some information at the bottom of the screen regarding this. So, what I did was that I clicked on the link that is supplied in Security & Drivers to allow the driver to be installed (or if it is the installer that is allowed to run). THEN reinstalled the silabs driver but using the legacy drivers. Now, I had seen somewhere that you might had to run the installer twice. So I did that and that was it. Communication to the nodeMCU did work from inside esplorer.

@ericssonanders comment is spot-on. I'm on High-Sierra and after manually attempting a kext load via sudo kextutil -tn /Library/Extensions/SiLabsUSBDriver.kext I got the warning prompt in Security & Privacy in Systems Preferences. Allowing the driver load there fixed the issue and /dev/tty.SLAB_USBtoUART shows up.
Here's the note from Apple describing why only some users are hitting this - if you had the driver installed from before upgrading to High Sierra it would have continued to work transparently for you
https://developer.apple.com/library/content/technotes/tn2459/_index.html

Hello, I would like to share my experience. I went trought all recommendations no success. The result is wrong USB-C to USB 3.0 reduction. Interesting is that USB-C reduction is working for external HDD. Strange behaviour, do you have same experience?

If you are having trouble on macOS...
I wrestled with this issue for a couple days on and off.  I finally fixed my issue, so I figured recounting my steps for all the other unfortunate sufferers would be worthwhile (even tho I am sure you have read 100 versions of solutions by now).
First off, I followed most of the general recommendations and installed this SiLabs Driver - no luck.  Then installed this CH34 driver - no luck (I didn't check to determine which chip I had, just kept trying solutions).  When installing the driver(s), I saw the Security many have described, warning for a 3rd party developer trying to access some settings.  I did what most suggested and went to  System Preferences ➜ Security & Privacy ➜ General and made sure my allowing apps to be downloaded from "Mac App Store and identified developers" - which it was.  Still - no luck.  Then, after hitting issue after issue, I resorted to assuming I had bad Micro USB cables (charge only) - so I ordered a new USB Sync cable to remove that variable.
I could never get my ESP8266 NodeMCU LUA CP2102 ESP-12E (made by HiLetgo) to show up under Tools > Port in the Arduino IDE (should see "/dev/cu.SLAB_USBtoUART").
After banging my head on it over and over, I tried re-installing the CH34 driver - which popped the security warning again (as described above). This time I clicked the "Goto Settings" button - which simply took me back tot the same System Prefs Security dialog I checked for the "allow apps" setting before.  However, this time I noticed there was a subtle macOS option next to those "allow" settings which said "Some system software was blocked from loading." and here was an "Allow" button.  When I tapped the "Allow" button, it popped a dialog that showed both the SiLabs and Ch34 drivers unchecked, which I fixed.  After that, voila!  It all worked (and on all my USB cables no less).
I cannot say which driver was my solution, but thought the important thing to point out to anyone struggling was to look for the Allow button in Security - I didnt notice it because all solutions I read just called out the "Mac App Store and identified developers" setting in that panel.  I had that set before installing the driver and it DID NOT stop the drivers from being blocked, so check for that.  Hopefully this helps someone else, what a pain...

Thank @haukeg for the new information.  Do you happen to know the type of Mac used?  I've seen slightly different problems between the 2016+ Macbook Pro laptops "with touchbar" versus "without", even when they're supposedly running the same version of MacOS.

@haukeg had exactly the same problem, same solution. Allow your driver to run!
MBR 15 touchbar 10.14.1

tried several times , normal, legacy cp2101, ch34, alert in security don't show, also disabled spctl kext-consent, tried several cables
@haukeg very similar as you... but did't see:

"However, this time I noticed there was a subtle macOS option next to those "Allow apps downloaded from" section which said "Some system software was blocked from loading." and here was an "Allow" button"

GUYS, REMEMBER TO TURN ON YOUR BOARD
😱 🤯 😭


Not taking a screenshot for external monitor

I found this package useful but it is unable to take a whole screenshot when I connect my external monitor to my laptop. It is taking only the screenshot of the laptop, not the monitor.
How to get the whole screenshot of both devices?

library needs to know how many montitors are connected and in use and expose an api so we can list them in the UI and select any or all of them but this functionality is not present in the code but its possible
I am going to implement this feature and send a merge request in a month.
Meanwhile if your job has a deadline you are free to hack it fast and share with us here

any news on this @edex96

any news on this one

Good!  Is it possible to select wich monitor to take the shot?

same issue

same issue

any solution ?


After switchcamera() is called, black screen when calling getUserMedia()

No call MediaStreamTacker._switchCamera(), no problem.
At first call MediaStreamTacker._switchCamera(), no problem.
Once call MediaStreamTracker._switchCamera(), Black screen is shown in RTCView when next calling of mediaDevices.getUserMedia().
What's wrong?

React Native version:0.55.4
RN Webrtc version:1.69.0
OS: Android
OS version: 8.1

Did you release the first stream? Why are you doing a second getUserMedia?

I released the first stream and then got the second stream by calling mediaDevices.getUserMedia()

get stream
mediaDevices.enumerateDevices().then(sourceInfos => { ... mediaDevices.getUserMedia({ ... }); });
release stream and connection
         this.peerconnection.close();           this.localStream.release();
switch camera
localStream.getVideoTracks().forEach(track => { track._switchCamera(); });

Can you share the code youa re running? I don't see how _switchCamera could affect anything, it's just one api call...

Here is the snapshot.
import {
    RTCPeerConnection,
    RTCMediaStream,
    RTCIceCandidate,
    RTCSessionDescription,
    RTCView,
    MediaStreamTrack,
    mediaDevices,
} from 'react-native-webrtc';
import InCallManager from 'react-native-incall-manager';
import {Platform} from 'react-native';

const configuration = {"iceServers": [{"url": "stun:stun.l.google.com:19302"}]};

export default class CallManager {
    socket = null;
    curCallInfo = {
        type: "none",
        to: -1,
        localStream: null,
        remoteStream: null,
        peerconnection: null,
        reqData: {},
    }

    constructor() {
        this.reset();
    }

    reset() {
        if (this.curCallInfo.peerconnection)
            this.curCallInfo.peerconnection.close();
        if (this.curCallInfo.localStream)
            this.curCallInfo.localStream.release();

        this.curCallInfo = {
            type: "none",
            localStream: null,
            remoteStream: null,
            peerconnection :null,
            reqData : null,
        }
    }

    getLocalStream(data, callback) {
        let vm = this;
        let videoSourceId;

        if (data.type == 'video') {
            let facingMode = "user";
            let isFront = true;
            mediaDevices.enumerateDevices().then(sourceInfos => {

                let videoSourceId;
                for (let i = 0; i < sourceInfos.length; i++) {
                    const sourceInfo = sourceInfos[i];
                    if(sourceInfo.kind == "video" && sourceInfo.facing == (isFront ? "front" : "back")) {
                        videoSourceId = sourceInfo.id;
                    }
                }
                mediaDevices.getUserMedia({
                    audio: true,
                    video: {
                        mandatory: {
                            minWidth: VIDEO_MIN_WIDTH,
                            minHeight: VIDEO_MIN_HEIGHT,
                            minFrameRate: VIDEO_MIN_FRAMERATE,
                        },
                        facingMode: facingMode,
                        optional: (videoSourceId ? [{sourceId: videoSourceId}] : [])
                    }
                })
                .then(stream => {
                    vm.curCallInfo.localStream = stream;
                    callback(stream);
                })
                .catch(error => {
                    vm.onError(error);
                });
            });
        }
    }

    switchLocalCamera() {
        this.curCallInfo.localStream.getVideoTracks().forEach(track => { track._switchCamera(); });
    }

    onError(error) {}

    endCall() {
        this.reset();
        InCallManager.stop();
    }

    ...

    createConnection(isOffer = false) {
        let vm = this;

        if (!vm.socket)
            return;

        const pc = new RTCPeerConnection(configuration);
        vm.curCallInfo.peerconnection = pc;

        pc.onicecandidate = function (event) {
            if (event.candidate) {
                vm.socket.emit('socket_call_info',
                    {
                        'to': to,
                        'from': me,
                        'candidate': event.candidate
                    });
            }
        };

        function createOffer(pc) {
            pc.createOffer(function (desc) {
                pc.setLocalDescription(desc, function () {
                    vm.socket.emit('socket_call_info',
                        {
                            'to': to,
                            'from': me,
                            'sdp': pc.localDescription
                        });
                }, vm.onError);
            }, vm.onError);
        }

        pc.onnegotiationneeded = function () {
            if (isOffer) {
                createOffer(pc);
            }
        }

        pc.oniceconnectionstatechange = function (event) {
            if (event.target.iceConnectionState === 'completed') {
                setTimeout(() => {
                    // getStats();
                }, 1000);
            }
            if (event.target.iceConnectionState === 'connected') {
                createDataChannel(pc);
            }
        };
        pc.onsignalingstatechange = function (event) {
        };

        pc.onaddstream = function (event) {
            vm.curCallInfo.remoteStream = event.stream;
            vm.changeCallStatus(CONST.CALL_STATUS_SAYING);
        };

        pc.onremovestream = function (event) {
        };

        pc.addStream(vm.curCallInfo.localStream);

        function createDataChannel(pc) {
            if (pc.textDataChannel) {
                return;
            }
            const dataChannel = pc.createDataChannel("text");

            dataChannel.onerror = function (error) { };

            dataChannel.onmessage = function (event) { };

            dataChannel.onopen = function () { };

            dataChannel.onclose = function () { };

            pc.textDataChannel = dataChannel;
        }

        return pc;
    }

    on_sock_call_info(data) {
        let vm = this;
        let pc = null;

        if (!vm.curCallInfo.peerconnection) {
            vm.curCallInfo.peerconnection = vm.createConnection(false);
        }

        pc = vm.curCallInfo.peerconnection;

        if (data.sdp) {
            pc.setRemoteDescription(new RTCSessionDescription(data.sdp), function () {
                if (pc.remoteDescription.type == "offer")
                    pc.createAnswer(function(desc) {
                        pc.setLocalDescription(desc, function () {
                            vm.socket.emit('socket_call_info',
                                {   'to': to,
                                    'from' : me,
                                    'sdp': pc.localDescription
                                });
                        }, vm.onError);
                    }, vm.onError);
            }, vm.onError);

        } else if (data.endCall) {
            vm.endCall();

        } else {
            pc.addIceCandidate(new RTCIceCandidate(data.candidate));
        }
    }

}

View
import {
    RTCPeerConnection,
    RTCMediaStream,
    RTCIceCandidate,
    RTCSessionDescription,
    RTCView,
    MediaStreamTrack
} from 'react-native-webrtc';

export default class CallVideoScene extends Component {

    constructor(props) {
        super(props);
    }

    componentDidMount() {
        this.getLocalStream();
    }

    componentWillUnmount() {
        callManager.endCall();
    }

    getLocalStream() {
        let vm = this;
        callManager.getLocalStream(
            {type: 'video'},
            function (stream) {
                vm.setState({localStream: stream.toURL()});
            }
        );
    }

    onEndCall() {
        callManager.endCall();
    }

    toggleFrontBack() {
        callManager.switchLocalCamera();
    }

    render() {
        return (
            <View style={styles.container}>
                <RTCView streamURL={this.state.currentStatus == CONST.CALL_STATUS_SAYING?
                            callManager.curCallInfo.remoteStream.toURL():this.state.localStream}
                    style={styles.mainView}
                    objectFit={'cover'} mirror={true}/>
            </View>
        );
    }
};

Sorry for long explanation.

I took a quick look but I don't see how that call to switchCamera is related to getting a blank stream afterwards. Do you see anything in the logs?

Let me ask you some questions.

Do I need to do additional operations at the end of the connection besides RTCPeerConnection.close() and RTCMediaStream.release()?
How do I handle mediaDevices when releasing a local stream?
(In the current version, it seems that the mediaDevices is the default manager for the local stream. _switchCamera() didn't work on streams obtained with getUserMedia(), which described in WebRTCDemo)
What are the common causes of a view being blacked out? Where should I look on the native side?

Thank you for your support.

* Do I need to do additional operations at the end of the connection besides RTCPeerConnection.close() and RTCMediaStream.release()?

Not really.

* How do I handle mediaDevices when releasing a local stream?

What do you mean? mediaDevices.getUserMedia is supposed to give you a new stream every time you ask for it. You can, however, not release the stream and keep using it on subsequent peer connections.

* _switchCamera() didn't work on streams obtained with getUserMedia(), which described in WebRTCDemo)

I don't know what this is about.

* What are the common causes of a view being blacked out? Where should I look on the native side?

Having a dead stream would be a possible cause.

You have an inactive stream URL linked to your RTCView, could you explain the context? to use the api switchCamera () you don't need a second call to getUserMedia ()

There was no follow up, I’m closing this.

I leave sample code to apply switchCamera ()
localStream.getTracks().forEach((t) => {
    if (t.kind === 'video') t._switchCamera();
});


Class 'Swift_MailTransport' not found

Q
A

Bug report?
yes/

Feature request?
no

RFC?
no

How used?
Standalone

Swiftmailer version
6.1.0

PHP version
5.6.36

Observed behaviour
The Script dies with the following error:
Fatal error: Class 'Swift_MailTransport' not found in /php/test_mailer.php on line 5

What are the required steps to reproduce the issue that you experience?

I think I found a solution: Composer is not installed on the server, I just manually copied the files from the repository to it.

I've installed swiftmailer via composer:
$ composer require "swiftmailer/swiftmailer:^6.0"
On my vendor directory i have the directory swiftmailer
but when i try to use swiftmailer to send an email i receive the error:
Slim Application Error
The application could not run because of the following error:
Details
Type: Error
Message: Class 'Swift_MailTransport' not found
File: /var/www/html/api-dev/src/routes/backendcron.php
Line: 41

I've installed swiftmailer via composer:
$ composer require "swiftmailer/swiftmailer:^6.0"
On my vendor directory i have the directory swiftmailer
but when i try to use swiftmailer to send an email
` // Create Transport
$transport = Swift_MailTransport::newInstance();
// Create Mailer with our Transport.
$mailer = Swift_Mailer::newInstance($transport);
try {
// Setting all needed info and passing in my email template.
$message = Swift_Message::newInstance('ECOplay shop')`

(...)
i receive the error on the first line:
Slim Application Error
The application could not run because of the following error:
Details
Type: Error
Message: Class 'Swift_MailTransport' not found
File: /var/www/html/api-dev/src/routes/backendcron.php
Line: 41


Missing media query when last rule is empty

A media query with last rule being empty strips out the whole media query.
  /* The below media query will be stripped out since the last rule is empty. */

  @media screen and (min-width: 960px) {
    .padded-text {
      padding: 0 10px;
    }
    .an-empty-style-rule {
    }
  }

  /* However, this one won't since it has something in the last rule. */
  @media screen and (min-width: 1200px) {
    .example-with-padding {
      padding: 0 10px;
    }
    .example-1 {
      color: white;
    }
  }

Is incorrectly minified to this starting with the version 3.2.0.  The 'min-width: 960px' media query is missing.
  @media screen and (min-width:1200px){.example-with-padding{padding:0 10px}.example-1{color:#fff}}

@jkenlooper good catch - I'll fix it later today!

Fixed in 3.2.10! :+1:

I saw a similar issue with keyframes being removed... did this fix cover that as well?  I'm running 3.2.9 from within a lib I don't have control over, so I don't have a quick means of testing.  In my example, this was being stripped out entirely:
@keyframes blur-in {
    0% {
        transform: scale(.85, .85);
        -webkit-filter: blur(1em);
    }
    100% {
    }
}

@keithjgrant you can remove the lib from node_modules and run npm install once again - this will bring you the clean-css 3.2.10 unless the lib pinned to clean-css 3.2.9 (highly unlikely).

Ah, right. For some reason I thought my date of original installation was after this 3.2.10 was released, but I guess I was off by a day or two.
I can confirm this fixed my issue with the keyframes. Thanks!

No worries, that's great! :+1:


[1.19.2] Player model is invisible in 1st person view with Better Combat mode

Basically the title. I don't know if it's a bug or feature, but player's dragon model is invisible in any state in 1st person view (flying/running/standing/fighting/etc). Player is visible in 3rd person view, including in inventory window.
This only occurs when you have compatibility mod AND Better Combat.
Logs seemingly show no anomalies, but I'll attach them just in case they do.
latest.log
Mods (all latest versions):
Dragon Survival
Dragon Survival Compatibility
GeckoLib
Better Combat
playerAnimator
Cloth Config API

It's intentional but you shouldn't really see it anyway other than when you look down with renderFirstPerson enabled to my understanding (the model should be visible in all GUIs though)
I changed it here so that it should only happen when you attack and the animation is playing
Not sure if it works correctly for all cases
dragonsurvival_compatibility-1.19.2-1.1.8-all.zip

Yes, everything works correctly. Thank you.

fixed in latest release


Adds TWTGradient files and updates podspec

@prachigauriar @jnjosh @macdrevx

👍 Squash before merging.

Let’s get another review, since I wrote the original code :-)

@dfowjtm @prachigauriar I'd love to see some unit tests.

But in lieu of unit tests, 👍

@dfowjtm Let’s get this merged.


Open to new collaborators

If you want to collaborate in the project you are more than welcome, feel free to join the Discord https://discord.com/invite/U967mp5qbQ and tell us what you are interested in doing and we will help you to be able to help on it 🎉 👍

Would it be helpful to start copying the old issues from gqless into this repo? Perhaps a chance to reevaluate the state and mark which issues are good first issues?

My idea was to simply start fixing them in the gqty repo and then simply notifying that the fix was released in gqty instead of gqless, there are some issues that were already fixed and did exactly that, if you feel like some issues should be copied before, no problem 👍

I think there shouldn't be two repositories for the same library. Makes things complicated to track.

It's something out of our control, we don't have ownership rights over the gqless org / repo, which is why this "fork" was made

Got it!
Could you please point me to a document explaining the reason for this fork?

Got it!
Could you please point me to a document/article/issue explaining the reason for this fork, if there is such a thing?

There isn't one, I just made a quick announcement in the old discord

It would be nice to have some information as to why there's a split, and why should or shouldn't one switch from GQless to GQTY.
I think it would be great if you could please write an explanation at the top of the readme file so that people would know why the change and how we should proceed.
Thanks!

I'm thinking that some kind of roadmap or what's missing can be helpful for new collaborators. If someone wants some feature which can be found on a roadmap - it's easier to start collaboration. I'm big fan of comparison that URQL client has made. Maybe we can decide what of those features are needed or nice to have


Ensure we don't clobber update times

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 28.864%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
902

Relevant Lines:
3125

💛  - Coveralls


Add datamill-co variant of target-postgres

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2433
Originally created by @DouweM on 2020-11-05 23:30:36

It would be nice to add out-of-the-box support for https://github.com/datamill-co/target-postgres, for users who already started using it before finding Meltano, or who may prefer it over our own variant.
We can consider making it the default like we did with https://github.com/datamill-co/target-snowflake.

View 4 previous comments from the original issue on GitLab


Lifetime deposit cap issue

The Chore
I am getting a lifetime deposit blockage on testnet

Which is surprising given this is a brand new key created from ethereum connection.
And I am also not being offered to approve new limits by metamask.
So it is a little broken. Its unclear whether this will be a problem on mainnet or not, given the differing setups, but I am raising it.
This is testnet key : 4eced663723f8464095d6b3442c9baf83e02650f717ebc2c2c52dfa4dcaa3e9b
Tasks

[ ]
[ ]

Additional details / background info

This is configured on the asset on the network .... so its testnet specific and not MM / WAGMI.
Ignore


v0.6.16

#906  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


WIP implementation of NewFromFloat32

Hi Alexander,
Thanks for starting to work on the binary128 implementation! Let me know if you'd like to continue work on this PR (as you've marked it with WIP).
We can also merge it as is now, and continue with further PR to implement the other missing pieces, add test cases, etc.
Cheers,
Robin

Hi Robin! yes it would be great tomerge it now

Hi Robin! yes it would be great tomerge it now

Done. Thanks for the PR Alex!

you are always welcome!


[doc] Query datasets from Datasets Server: split into one page per library?

i.e. having a specific page for DuckDB would be very cool i think

maybe cc @stevhliu

I think at the moment it might be cleaner to keep it all on one page since there's not too much content for each of the libraries (for example, the Pandas section is super short and not really worth adding another section to the toctree imo) and because the content is so similar I think it'd make more sense to me to keep it together for now.
If we get more content for each library (plus highlighting the unique aspects of each library), then I'd be more compelled to create a separate page for each one. What do you think @mariosasko @lhoestq @severo?

There is potential to add quite a lot of content for duckdb, so yea having a separate page at one point makes sense imo

also makes it way easier to share with DuckDB or Pandas authors and motivate them to write content about it when it's a single page focused on their tool

done


Add width and height attributes to images to reduce CLS

Cumulative Layout Shift happens when a page has to repaint things, and then all of a sudden things shift around the page. This can be very distracting and happens a lot on the docs site due to images not having any set dimensions and therefore no aspect ratios to adhere to.
Some good references:

https://web.dev/optimize-cls/
https://www.smashingmagazine.com/2021/06/how-to-fix-cumulative-layout-shift-issues/
https://jakearchibald.com/2022/img-aspect-ratio/

Actual Behavior
Take https://developers.cloudflare.com/analytics/graphql-api/tutorials/build-your-own-analytics/ for example. This is a page with an image at the top, and the CLS is 0.128- WAY higher than the desired 0.
Here's a quick video demonstrating this: https://up.jross.me/r15pv1c4
Notice how the "Code" section is bumped down the page as the image loads in? That's the layout shift occurring and is very jarring especially if the image takes a while to load and I'm already reading the doc.
This impacts every page on the docs site that has images above the fold.
Expected Behavior
Images should have a set width and height so that the browser can reserve space for them when rendering. Setting these values won't prevent the images from being downsized when needed either, it'll simply hint the browser of the image's aspect ratio so it can reserve the space needed to render it.
Additional information
I started work on this a bit, but my lack of experience with Hugo is making it more difficult than I'd like.
Hugo offers Render Hooks though, which should make this very possible. I started with a layouts/_default/markup/render-image.html file with this:
{{- $src := (.Destination | safeURL) -}}
{{- $alt := .Text -}}
{{- $title := .Title -}}
{{ $resource := .Page.Resources.GetMatch .Destination }}
<!-- handle external links -->
{{- if strings.HasPrefix $src "http" -}}
	<img
		src="{{ .Destination | safeURL }}"
		alt="{{ .Text }}"
		{{ with .Title}} title="{{ . }}"{{ end }}
	/>
<!-- handle absolute URLs-->
{{- else if not (strings.HasPrefix $src "..") -}}
  {{ $imageurl := print "content/" $src }}
  {{ $imageurl }}

  {{- $img := imageConfig $imageurl -}}

  {{ with $img}}
    <img
      src="{{ $src }}"
      alt="{{ $alt }}"
      {{ with $title}} title="{{ . }}"{{ end }}
      {{ with .Width}} width="{{ . }}"{{ end }}
      {{ with .Height}} height="{{ . }}"{{ end }}
    />
  {{ end }}
<!-- handle images with relative pathing -->
{{- else -}}
  {{ $url := urls.Parse .Destination }}
  {{ $combinedpath := (path.Join .Page.File.Dir .Destination)}}
  {{$combinedpath}}

  {{ $imageurl := print "content/" $combinedpath }}
  {{ $imageurl }}

  {{- $img := imageConfig $imageurl -}}

  {{ with $img}}
    <img
      src="{{ $src }}"
      alt="{{ $alt }}"
      {{ with $title}} title="{{ . }}"{{ end }}
      {{ with .Width}} width="{{ . }}"{{ end }}
      {{ with .Height}} height="{{ . }}"{{ end }}
    />
  {{ end }}
{{- end -}}

It mostly works, but errors on a couple of edge-cases and needs some more thought (handling remote http urls, other relative paths like ../, etc.). It should be very possible with the Resources and/or imageConfig stuff though, for someone more familiar with Hugo than me.
I also tweaked the .DocsMarkdown img css rule to include height: auto, and with both the height and width attributes set on images, it reduces the CLS on pages to zero, resulting in a much nicer reading experience for any image-heavy pages as the content loads.

Feels like something @brycewray may know more about

@WalshyDev I appreciate the compliment. But @Cherry is exactly right — about both the importance of using aspect-ratio to reduce CLS and the proposed method of implementing it in Hugo. Nicely done.

@WalshyDev @Cherry In case it would help, I have a somewhat related article:
https://www.brycewray.com/posts/2022/06/responsive-optimized-images-hugo/

Also, thanks to @brycewray for even getting me this far. We're not looking for responsive images, exactly, but the approach + detailed notes in the article were incredibly helpful.

@kodster28 Thanks for the kind words! Glad the info was useful to you.

Yeah, think so as well. Just wanted to exclude them for the time being.


openstack-ardana-heat: fix resource deps (SCRD-5204)

We're still seeing problems with the way heat handles the
implicit dependencies between its resources during stack
deletion. This causes occasional failures while deleting
heat stacks, which leave behind zombie heat stacks, such as:
Conflict: resources.controller_0001_hed7_trunk: Trunk
d33c49a7-9b7e-4712-adf7-1ecd4d73fd57 is currently in use.
Neutron server returns request_ids: ['req-c261c7c7-4636-4110-8dfb-b71fbf677679']

There are two resources dependencies that don't seem to be
respected by heat during stack deletion:

volumes are deleted before the server deletion is complete
trunk ports are deleted before the server deletion is complete

This comit enforces these dependencies using explicit depends_on
values in the generated heat stacks, configuring all volumes and
trunk ports belonging to a server as prerequisites for that server.

Tested with: https://ci.suse.de/job/openstack-ardana-vcloud/2585/
With these changes applied, I can confirm that the heat resources are created in the proper order -
first the volumes and ports, then the servers - then deleted in reverse order.


[PIRK-44]: Tachyon FS Error

Added a filter for org.tachyonproject to the shade plugin configuration to fix the issue.

running an mvn dependency:tree on the project shows that the tachyon plugins are being pulled in with hadoop-mapreduce-client-core jar.
You can exclude tachyon while pulling in the jar as a dependency (similar to how we r excluding storm dependencies being pulled in now by Elasticsearch).

Looking at the maven dependency tree, Tachyon client is being pulled in as a dependency via hadoop-mapreduce-core-client, spark-core, elasticsearch-spark-core.
We could either individually exclude tachyon-client in the each of the above 3 dependencies OR go with the suggested solution in this PR.

Oops - look like we crossed paths with you posting a comment to the PR while I was merging/closing the PR. I went with the current solution as Walter gave a +1 on the dev list earlier. We can reopen if folks would like...

Did u try running on a Spark cluster with this fix? If it works fine on a spark cluster, then we can go ahead with this fix; else we should reopen.

Yes, tested successfully on a Spark cluster


Accuracy criterion should be accessed from Estimation API

Currently, the Estimation API gives access only to maximum number of iterations, but not to other stopping criteria affecting the accuracy. These parameters should be exposed as optional parameters.

Feature added in https://github.com/sdu-cfei/modest-py/commit/2ef6ee2f089401fe4659957f1f4a6c312756d74b


CSS sticky footer breaks angular-scroll

Using http://ryanfait.com/resources/footer-stick-to-bottom-of-page
The scroll delta is always zero because duScrollTop() is always zero. I found this to be caused by body,html with height:100% (css sticky footer implementation)
The offending LoC:
if(isDocument(el)) {
  return $window.scrollY || document.documentElement.scrollTop || document.body.scrollTop;
}

angular scroll version 0.6.5 and 0.7.x

PR is welcome! :-)

Closing due to inactivity.


switching to state _state_default GameKill raised a exception

Splatted an enemy! (2 streak)
<ikalog.scenes.game.special_weapon.GameSpecialWeapon object at 0x10c0a9518>: switching to state _state_default
GameKill raised a exception >>>>
Traceback (most recent call last):
  File "/Users/ykws/Workspace/IkaLog/ikalog/engine.py", line 275, in process_scene
    scene.match(context)
  File "/Users/ykws/Workspace/IkaLog/ikalog/scenes/scene.py", line 111, in match
    self._matched = self.match_no_cache(context)
  File "/Users/ykws/Workspace/IkaLog/ikalog/scenes/game/kill.py", line 125, in match_no_cache
    current_kills = self.find_kill_messages(context)
  File "/Users/ykws/Workspace/IkaLog/ikalog/scenes/game/kill.py", line 75, in find_kill_messages
    img_name_left = np.min(img_name_x_hist)
  File "/usr/local/lib/python3.5/site-packages/numpy/core/fromnumeric.py", line 2350, in amin
    out=out, keepdims=keepdims)
  File "/usr/local/lib/python3.5/site-packages/numpy/core/_methods.py", line 29, in _amin
    return umr_minimum(a, axis, None, out, keepdims)
ValueError: zero-size array to reduction operation minimum which has no identity

<<<<<

Not reproduce.


Add $var:unquote modifier

I'd like to propose a new modifier for variable conversion named unquote. When applied to a string literal variable, it should remove the quotes, producing tokens.
Example:
fn foo() {}

macro_rules! bar {
    ($literal:literal) => {
        paste!([<$literal:unquote>]());
    };
}

bar!("foo"); // - expands to foo().

Use case:
I have a macro_rules derive macro, implemented using https://crates.io/crates/macro_rules_attribute. User input is expected to contain an attribute, #[foo(some_attr = "path::to::func")]. Since it is impossible to specify paths in Rust meta, a common pattern is to ask users to provide a string literal instead, the proc macro then parses it as expected token type. One example of a crate that uses this pattern is serde: https://serde.rs/container-attrs.html#default--path.
Since the purpose of paste is to enable macro_rules to do what normally only proc macros can do, I think this would be a nice addition.

I think [<$literal>] already works for this.


[SUGGESTION] Farmer's Delight / BWM Compat

The knife in Farmer's Delight has the same recipe for its knife as BWM, and it gets overwritten by BWM when both are installed. Could it be possible to allow the BWM knife to do the things that it does or allow the FD Knife to replace it if it is installed?

I wouldn't really like to give knives even more abilities. Rather, I suggest to install a mod like Polymorph, which will also "fix" every other possible recipe conflict, automatically.
For versions below 1.15.2, there were various mods that did the same thing

That is understandable, can you at least make it so that it's called something else if FD is detected? Maybe have it be called a dagger if FD is installed.

Changing item names might confuse players even more since "daggers" are an extra weapon I plan to add (or port from Reforged) at some point.
With a mod like WAILA, HWYLA, or WTHIT, the item tooltips show which mod adds the hovered item, so it is very easy to tell which item is which, I believe.


[Fix] Handler kytos/core.openflow.raw.in crashed when trying to log an OFPT_ERROR

Fixes #61
Now it correctly logs and then publishes the OFPT_ERROR message, I removed the hex f-string format, it was there primarily for convenience.
This branch is on top of #60 to facilitate local development and managing in-flight branches.
Release notes

OFPT_ERROR message could crash when logging it.

Running it locally
2022-05-19 16:01:02,889 - ERROR [kytos.napps.kytos/of_core] (thread_pool_sb_7) OFPT_ERROR: type ErrorType.OFPET_BAD_MATCH, error code 7, from switch 00:00:00:00:00:00:00:01, xid 130177
2539
2022-05-19 16:01:02,894 - WARNING [kytos.napps.kytos/flow_manager] (thread_pool_sb_7) Deleting flow: {'switch': '00:00:00:00:00:00:00:01', 'table_id': 0, 'match': {'dl_vlan': 10000}, '
priority': 32768, 'idle_timeout': 0, 'hard_timeout': 0, 'cookie': 0, 'id': '502866b8912c0eee9e98345b01013524', 'stats': {}, 'cookie_mask': 0, 'instructions': [{'instruction_type': 'app
ly_actions', 'actions': [{'port': 2, 'action_type': 'output'}]}]}, xid:<PHONE_NUMBER>, cookie: 0, error: {'error_command': 'add', 'error_type': UBInt16(<ErrorType.OFPET_BAD_MATCH: 4>), 'e
rror_code': <BadMatchCode.OFPBMC_BAD_VALUE: 7>}
kytos $>

Very nice that you get this error! I've commented on the issue that this hex conversion indeed was done for convenience in the past when we have to troubleshoot log entries from physical switches and Kytos log. Relying on the external transformations on the log message although possible would speed down the tshoot process, and that is why we request the hex version of the XID (IMHO, we don't actually need the int format, only hex format would be enough).
With that in mind, I made a comment/suggestion with another strategy to fix the problem.

Got it. I've just applied the commit, I think we can consider implementing the dunder __format__  method in the future, this patch solves for now. Thanks @italovalcy, I'm glad you recalled about this original requirement.


Json Schema Slow and Throwing error with intellisense and validation

Monaco Editor Playground Link
https://t.ly/5IdiK
Reproduction Steps
We are trying to use intellisense and validation with our schema in VSCode. However, after a few nested json children, intellisense and validation slows down leading to high CPU usage and then no suggestion in VSCode editor when schema is added in settings for json files.
Like:
"json.schemas": [     {       "fileMatch": [         "*.json"       ],       "url": "file:/../schema.json"     }   ]
Also, monca editor is giving the error shown as below, added for more context
Add this schema and try to create a nested json
schema.json

Actual (Problematic) Behavior
Intellisense is slowing down and not recommending anymore

Expected Behavior
It should behave always the same, as fast as the initial code sensing and validation
Additional Context
We are using the intellisense and json validation for our users to create a correct json file

You have a recursive schema that goes across resources. The current code can not handle that and I don't think we will look at that any time soon.
If that's an option for you, I recommend you to move all in one file.

Using definitions in a single file and referring to them in the can' t be also handled because attached json file is in that structure same file

But now, with the updated schema (all in one file) thing seem to work:

What's not working for you?

As the children increase it gets slower. And when trying to type 4th nested children it crashes with the callstack error

Ah I see, I take it back, I see the same problem....


Underperforming RGArray implementation

I've taken a look at the rga implementation and I've noticed that it has been implemented using Erlang list. Example implementation of add_element can recreate the entire list on every insert. Finding an element is potentially O(N) operation (however I understand that in most obvious use cases elements will be appended to the end, making it optimistically O(1)).
Also I've noticed that rga is not mentioned in official AntidoteDB docs. Therefore my question is: what's the status of this data structure?

I totally: The implementation of RGA has quite a few flaws. This is also why we didn't include it into the documentation, yet, as we rather not have people using it in production.
We have been working on some alternative designs for sequence CRDTs. @peterzeller has more information on that.

That's interesting. Also I've seen that rga has cleaning method, but it's essentially removing all tombstoned elements, which makes quite hard to find a correct point in time to actually call it from different replica sets. I'm working over RG array implementation on another platform, which implements tombstones as vector clocks - to allow pruning of elements before given point in time (ideally the lowest stable version vector).
But since you've said that you're working on other design, may I ask which structure will it be? Are you working on implementing existing CRDT like lseq or something totally new?

Please reopen if still valid at https://github.com/AntidoteDB/antidote


Replace @marshallofsound/webpack-asset-relocator-loader to @vercel/webpack-asset-relocator-loader

Describe the bug
@marshallofsound/webpack-asset-relocator-loader is not an official package, and it seems to have certain risks (its repo link on npmjs.com is not its repo)
used in: https://github.com/Leopold-V/Reactirator/blob/735f080036b4951fbc7db3b09232eb80b7d5baf3/webpack.rules.js#L11
So I suggest switching the related dependencies to @vercel/webpack-asset-relocator-loader, which is also the official package of vercel

Hi, thanks for the information, I will have a look at this.

#51


[KeyVault] Addressed feedback on samples

Jonathan found that some of the samples have issues. Here's a PR fixing them.
Since this is only in the samples, perhaps this doesn't affect the current release build?
Fixes #5444

Feels like we should land these, though I noticed a couple related issues that aren't addressed quite yet.  I let a comment about one.
backupAndRestore for certificates also gave me this error:
error code:  Conflict
error message:  Conflict while restoring certificate https://joturner-keyvault4.vault.azure.net/certificates/MyCertificate2336/322018317dd541f793d6fbf3a6d0f15d - certificate already exists or concurrent access
error stack:  Error: Conflict while restoring certificate https://joturner-keyvault4.vault.azure.net/certificates/MyCertificate2336/322018317dd541f793d6fbf3a6d0f15d - certificate already exists or concurrent access
    at new RestError (C:\Source\preview4\certs\node_modules\@azure\core-http\dist\coreHttp.node.js:1698:28)
    at C:\Source\preview4\certs\node_modules\@azure\core-http\dist\coreHttp.node.js:2915:37
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

In my version I changed it to:
  await client.deleteCertificate("MyCertificate2338");

  // It might take less time, or more, depending on your location, internet speed and other factors.
  await delay(30000);

  await client.purgeDeletedCertificate("MyCertificate2338");
  await delay(30000);


CSP violation

Error loading webview: Error: Could not register service worker: SecurityError: Failed to register a ServiceWorker: The provided scriptURL ('https://0e667eqavdhf9u965fg8hb3th5tb61rmqg6kmq8c74h51rhj8amf.assets.github.dev/stable/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/contrib/webview/browser/pre/service-worker.js?v=4&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&remoteAuthority=codespaces+super-duper-acorn-wr74qj9w5p94f99w7') violates the Content Security Policy..

Closing as there's not enough context to investigate

Hello.
Sorry for the late reply.
The problem I am experiencing with my VS Code is that I am unable to
load/open any kind of images because of the error attached. I also not able
to open the CS50 Duck Debugger because of the same issue.
It says: The provided scriptURL violates Content Security  Policy.
On Thu, 16 Nov 2023, 01:47 Matt Bierner, @.***> wrote:

Closed #196108 https://github.com/microsoft/vscode/issues/196108 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/196108#event-10973194263, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCL6S46OZUV6KZMVKO6OUJDYEVA67AVCNFSM6AAAAAA6JN3VKKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHE3TGMJZGQZDMMY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please follow this guide to provide additional information: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions
You can use the new issue template on GitHub to save time


Add Main class to start framework on Mini-Mesos

@mwl do you know what this means? I don't know what this means.

I think it has been solved already.


Articulate criteria for inclusion or non-inclusion of BFO classes

Carried on from #11
OBO-Core will consist of:

classes from upper levels of domain ontologies
some subset of BFO
subClassOf axioms connecting the two (which ideally come from the domain ontologies, but may may inject at first)

One of the use cases (presumably, but this should be explicitly stated somewhere) is that domain ontologies should only need to import obo-core and not BFO in their release version. This provides a more usable upper level.
What are the criteria for deciding on the subset of 2? We may have different implicit ideas, see #11. For example, a usability criteria is to remove as much abstraction as possible and make it user friendly.
However, an engineering consideration is that any class that is required for reasoning must be present in the domain ontology. This often entails including the superclass closure (or more formally, the SLME module) of any referenced BFO class. i.e. we end up pulling in everything in bfo above a certain level.
The alternative is to use the BFO "bokeh" pattern https://github.com/BFO-ontology/BFO/issues/221. This adds additional complexity to the build process but has good usability outcomes
Are we all aware of these tradeoffs, should we discuss further on a call? @bpeters42 @jamesaoverton @rctauber @dosumis ?

I like the approach in  BFO-ontology/BFO#221
https://github.com/BFO-ontology/BFO/issues/221, and in particular the use
of data properties.
On Fri, Mar 1, 2019 at 5:45 PM Chris Mungall<EMAIL_ADDRESS>wrote:

Carried on from #11
https://github.com/OBOFoundry/Experimental-OBO-Core/issues/11
OBO-Core will consist of:

classes from upper levels of domain ontologies
some subset of BFO
subClassOf axioms connecting the two (which ideally come from the
domain ontologies, but may may inject at first)

One of the use cases (presumably, but this should be explicitly stated
somewhere) is that domain ontologies should only need to import obo-core
and not BFO in their release version. This provides a more usable upper
level.
What are the criteria for deciding on the subset of 2? We may have
different implicit ideas, see #11
https://github.com/OBOFoundry/Experimental-OBO-Core/issues/11. For
example, a usability criteria is to remove as much abstraction as possible
and make it user friendly.
However, an engineering consideration is that any class that is required
for reasoning must be present in the domain ontology. This often entails
including the superclass closure (or more formally, the SLME module) of any
referenced BFO class. i.e. we end up pulling in everything in bfo above a
certain level.
The alternative is to use the BFO "bokeh" pattern BFO-ontology/BFO#221
https://github.com/BFO-ontology/BFO/issues/221. This adds additional
complexity to the build process but has good usability outcomes
Are we all aware of these tradeoffs, should we discuss further on a call?
@bpeters42 https://github.com/bpeters42 @jamesaoverton
https://github.com/jamesaoverton @rctauber https://github.com/rctauber
@dosumis https://github.com/dosumis ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OBOFoundry/Experimental-OBO-Core/issues/13, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANN9IuYzCTzMBDiLQg4reFzySA01YAJjks5vSdfVgaJpZM4baGFJ
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters