Posted by jpluimers on 2021/05/13
Gisteren was er een (hopelijk tijdelijk) afscheid door [Archive.is] Haagse Insider🕵🏻♂️ (@HaagseInsider) | Twitter.
De indrukwekkende draad is helaas niet beschikbaar op Archive.is, maar wel beschikbaar op het web archief.
Sowieso wens ik meer rust en afstand voor HaagseInsider. Daarnaast duim ik dat het een weerzien wordt.
—jeroen
Posted in Power User, SocialMedia, Twitter | Leave a Comment »
Posted by jpluimers on 2021/05/13
Quite some time ago, I was researching spurious exceptions in a Delphi application, then finally replicated them in a unit test suite.
One of them was occurring almost all of the time: EInvalidOp.
It is one of the floating point exceptions (incidentally exampled at [WayBack] Exceptions: Declaring Exception Types) all inheriting from the [WayBack] EMathError Class:
EMathErroris the base class for floating-point math exception classes.EMathErroritself is never raised.The following exceptions descend from
EMathError:
Run-time exception information is saved in fields provided by [WayBack]
EExternal.
In my first case (which I described in delphi – Invalid floating point operation calling Trunc()), not all input scenarios had been tested in a certain scenario. In a production environment, one of the inputs was really high.
In a later case, the actual cause was not a floating point problem at all, but a use-after-free scenario that overwrite a floating point value with something not so compatible also causing a simple Trunc statement to fail in the same way.
In that case, the production data could never reach the big numbers that failed, so no new tests were needed.
–jeroen
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | Leave a Comment »
Posted by jpluimers on 2021/05/12
[WayBack] dutchdelphidude on Twitter: “ik doe nu dit ermee nefertiti-tradebot.com … “
–jeroen
Posted in Development, Go (golang), Software Development | Leave a Comment »
Posted by jpluimers on 2021/05/12
Quite a while back, @NS_Online (Dutch railroads) did not accept plus signs in email addresses. I verified a few times over the years and not much progress.
This is a reminder to myself to re-check.
Edit 20230418: it has started working, see further below.
Below the fold the Twitter thread that started with [WayBack] Jeroen Pluimers on Twitter: “Toch jammer dat @NS_online valide email adressen met een plus-teken erin weigert.… “
Hopefully by now they retraced themselves from the bad company of many other parties failing to adhere to clear and long existing internet standards: [WayBack] User:Me at work/plushaters | Mozilla Community | FANDOM powered by Wikia.
Their web care team and their developers made some very inexcusable assumptions there:
Some links on email addresses and their validity:
Posted in Development, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/05/12
(Tagged FastMM4 as that’s the first code I saw these warnings to be turned off)
Delphi 7 introduced introduced warnings for unsafe constructs like W1047 and W1048 so you could prepare your code for the first Delphi .NET compilers .
The oldest online documentation on this is in Delphi 2007:
{$UNSAFECODE ON}or
{$UNSAFECODE OFF}{$UNSAFECODE OFF}
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. In a secured execution environment such as .NET, such code is assumed to be unsafe and a potential security risk.
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. In a secured execution environment such as .NET, such code is assumed to be unsafe and a potential security risk.
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. In a secured execution environment such as .NET, such code is assumed to be unsafe and a potential security risk.
After Delphi 2007, the .NET compiler got shelved, but the errors and warning stayed as they serve a good purpose for native code as well.
Delphi 2007 did not document any of the other directives.
Unlike the D2007 documentation, however, the UNSAFECODE should be written UNSAFE_CODE as with using {$WARN UNSAFECODE ON}, you will get this error:
E1030 Invalid compiler directive: 'UNSAFECODE'
Looking at the library code and example code that ships with Delphi, these are the valid $WARN compiler directives having to do with UNSAFE:
UNSAFE_CAST (since Delphi 7, but only used in Vcl.WinXPanels.pas introduced in Delphi 10.2 Tokyo and up)UNSAFE_CODE (since Delphi 7, but still documented as UNSAFECODE)UNSAFE_TYPE (since Delphi 7)UNSAFE_VOID_POINTER (since Delphi XE3, as precursor to the NEXTGEN compilers)The ultimate source for these is the file DCCStrs.pas that has shipped since Delphi 2009: [WayBack] warnings – Identifiers for Delphi’s $WARN compiler directive – Stack Overflow.
A problem is that current documentation still lists the wrong name in many places:
- UNSAFE_TYPE
- UNSAFE_CODE
- UNSAFE_CAST
This one finally got it right: [WayBack] Warning messages (Delphi) – RAD Studio
UNSAFE_TYPEW1046 UNSAFE_CODEW1047 UNSAFE_CASTW1048
Note it also documented UNSAFE_VOID_POINTER:
UNSAFE_VOID_POINTERW1070 [WayBack] W1070 Use of untype pointer can disrupt instance reference counts (Delphi) – RAD Studio
And these warning messages still do not contain the directives, but do explain the underlying code construct better:
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. For example, you might receive this warning if you declare something as absolute. Such code can be considered a security risk.
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. Such code can be considered a security risk.For example, using GetMem can elicit this warning because a block of memory has no associated type.
You have used a data type or operation for which static code analysis cannot prove that it does not overwrite memory. For example, you might have cased one record to another or one instance to another.
You have to use these directives:
// Get rid of "W1047 Unsafe code 'ASM'", "W1047 Unsafe code '^ operator'", "W1047 Unsafe code '@ operator'" and similar {$WARN UNSAFE_CODE OFF} // Get rid of "W1048 Unsafe typecast of 'TFreedObject' to 'PByte'" and similar {$WARN UNSAFE_CAST OFF}
Back in the days, some people were not amused and disabled the warnings, for instance in [Archive.is] Re: How can I eliminate these warnings in Delphi 7 which did not appear in Delphi 5. – Google Groups:
Dennis Passmore:I have one include file that I usually include in all projects as follows—– WarningsOff.inc —————-
{$IFDEF CONDITIONALEXPRESSIONS}
{$IF CompilerVersion >= 14}
{$WARN SYMBOL_PLATFORM OFF}
{$WARN SYMBOL_DEPRECATED OFF}
{$WARN SYMBOL_LIBRARY OFF}
{$WARN UNIT_DEPRECATED OFF}
{$WARN UNIT_LIBRARY OFF}
{$WARN UNIT_PLATFORM OFF}{$WARN UNSAFE_TYPE OFF}
{$WARN UNSAFE_CODE OFF}
{$WARN UNSAFE_CAST OFF}
{$IFEND}
{$ENDIF}
———————and it gets ride of all unwanted warnings in the IDE or even DCC32.exe when compiling the project
from the command line.I just add the following line to the project .dpr file and do not worry about the rest.
{$I WarningsOff.inc}
Dennis Passmore
“If you cannot conceive the idea you
will never achieve the desired results”
I disagree with such an approach, as those warnings have their purpose.
Knowing how to selectively disable/enable them however, is important.
–jeroen
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | Leave a Comment »
Posted by jpluimers on 2021/05/11
Via [WayBack] Building a lab with ESXI and Vagrant – DarthSidious while researching the possibility of running Vagrant (software) – Wikipedia on VMware ESXi – Wikipedia for building and distributing development environments:
[WayBack] Solved: Very slow speed on SSD |VMware Communities “solution” that seems to work for ESXi 6.5 and 6.7:
ESXi 6.5 includes a new native driver (
vmw_ahci) for SATA AHCI controllers, but that introduces performance problems with a lot of controllers and/or disks.Try to disable the native driver and revert to the older
sata-ahcidriver by runningesxcli system module set --enabled=false --module=vmw_ahciin an ESXi shell.
Reboot the host to make the change effective.
which solves it for some who now get much faster results:
Your suggestion worked for me, now i am getting avg speed 250Mbps from SATA III SSD .
Hope will get the full I/Ops from SSD.
However:
One issue I still have is that my 4 port Syba PCIe controller card now vanishes after disabling vmw_ahci and I am restricted to using the SATA ports on the motherboard.
and you need backups:
WARNING: Doing this at least for me erases all the VMs on the aforementioned drive. Migrate as needed.
There was no response for a more permanent fix:
What is the permanent fix for this issue, should we expect a corrected native driver from VMware, or will this require a firmware upgrade on the part of the drive vendors?
and there seem to be other bottle-necks:
tried the command on a 6.7.
Deploying an OVA and I am getting 22.82….
I have a Samsung 860 EVO mSATA 1Tb SSD.
i re-enabled it, I got max 11.81.
Kind of crappy either way. Not SSD speeds IMO.
–jeroen
Posted in Development, ESXi6.5, ESXi6.7, Power User, Software Development, Testing, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2021/05/11
De buurt was tot laat afgesloten (veiligheid, onderzoek, genoeg redenen), dus voor nachtopvang van mijn verstandelijk beperkte broer moeten zorgen omdat Wlz zorginstelling geen crisiszorg kon leveren en op WSW werk geen leidinggevende beschikbaar was om zorg af te stemmen.
Voor mijn off-line geheugen (bijna allemaal via [Archive.is] #sassenheim hashtag on Twitter):
5/10/2021 3:08:20 PM
A1 (MMT) (DIA) 13991 Rit 42131 Westerstraat Sassenheim regio 16
In een woning aan de Westerstraat in Sassenheim is maandagmiddag een explosie geweest waardoor er brand is uitgebroken in twee portiekwoningen. Meerdere woningen zijn daarbij beschadigd, niemand gewond geraakt. Wel heeft de politie heeft een 43-jarige aangehouden, hij wordt verdacht van brandstichting.
…
In de Burgernet oproep stond dat de gezochte verdachte een 33-jarige man is, dat blijkt niet correct. Het gaat om een 43-jarige verdachte.
…
Forensisch brandonderzoekers van de politie onderzoeken de oorzaak van de brand in de portiekwoning in de Westerstraat. Maandag gingen daar na een explosie twee woningen in vlammen op. Zes woningen zijn voorlopig onbewoonbaar verklaard.
Omstanders die met de hulpdiensten belden, vertelden dat ze voordat er brand uitbrak ze een harde knal hadden gehoord. Later op de middag hielden agenten een 43-jarige man uit Sassenheim aan voor betrokkenheid. Hij is bewoner van een van de uitgebrande portiekwoningen.
De politie vermoedt brandstichting. Daarom onderzoeken forensisch brandonderzoekers de oorzaak van deze brand. Die kan technisch van aard zijn, bijvoorbeeld een kapot apparaat, maar de brand kan ook het gevolg zijn van menselijk handelen. De onderzoekers zoeken naar sporen tussen de brandresten en lezen zo het brandbeeld.
De politie vraagt mensen met informatie die nog niet met de politie hebben gesproken contact op te nemen Dat kan op telefoonnummer 0900-8844. Liever anoniem? Bel dan met 0800-7000.
Maandagmiddag rond 15.00 uur is in een woning aan de Westerstraat een zeer heftige brand ontstaan. De hulpdiensten hebben opgeschaald naar GRIP1, waarbij er meerdere eenheden paraat staan.
De brand volgde na een heftige explosie in een van de benedenwoningen. Door de heftige klap, werd de voorgevel uit het pand geblazen en kwamen kozijnen aan de overkant van de straat terecht.
De brandweer is met veel materieel uitgerukt. Een lifeliner is geland bij het gemeentehuis, maar inmiddels ook alweer vertrokken zonder inzet. Voor zover bekend zijn er nog geen slachtoffers door de hulpdiensten aangetroffen.
De bewoner van het huis waar de explosie is ontstaan zou nog in de omgeving rondlopen, het gaat om een verward persoon die de explosie vermoedelijk zelf heeft veroorzaakt. De bewoner was voortvluchtig en werd via een Burgernet melding gezocht door de politie. Om even over 16.30 is hij aangehouden.
Een uur na de eerste explosie zijn drie woningen in de portiekflat uitgebrand. Brandweer zet nu in om de naastgelegen woningen te behouden en brandoverslag te voorkomen. Er komt nog steeds veel rook vrij. Blijf uit de rook en sluit ramen en deuren.
De politie doet onderzoek naar de oorzaak van de explosie en de brand in de Westerstraat en is opzoek naar getuigen.
In portiekwoningen aan de Westerstraat brak maandagmiddag 10 mei rond 15.00 uur brand uit. Omstanders die met de hulpdiensten belden, vertelden dat voordat er brand uitbrak ze een harde knal hadden gehoord. Later op de middag hielden agenten een 43-jarige man uit Sassenheim aan voor betrokkenheid.
Bij de brand raakte niemand gewond. De politie vermoedt brandstichting. Daarom onderzoeken forensisch brandonderzoekers de oorzaak van deze brand. Die kan technisch van aard zijn, bijvoorbeeld een kapot apparaat, maar de brand kan ook het gevolg zijn van menselijk handelen.
De onderzoekers zoeken naar sporen tussen de brandresten en lezen zo het brandbeeld. Heb je informatie over de brand en nog niet met de politie gesproken? Neem dan contact om met 0900-8844. Liever anoniem? Bel dan met 0800-7000.
- Start actie: 10/05/2021 16:17
- Einde actie: 10/05/2021 16:38
- Status van deze actie: Afgeronde actie
- Locatie: TEYLINGEN
2171CG Sassenheim Westerstraat: ivm verdachte situatie: man, 33 jr, blank, mager, d blond haar, piercings in gezicht, crème/bruine hond.
Sassenheim – In portiekwoningen aan de Westerstraat brak maandagmiddag 10 mei rond 15.00 uur brand uit. Omstanders die met de hulpdiensten belden, vertelden dat ze voordat er brand uitbrak ze een harde knal hadden gehoord.
–jeroen
Posted in About, Personal | Leave a Comment »
Posted by jpluimers on 2021/05/11
I wonder how you can programmatically open a Hangouts link from Chrome?
These dit not help:
So did some more digging.
TL;DR: did not find a solution; so any help is appreciated.
I found the IDs of then in [WayBack] extensions/common/constants.cc – chromium/src.git – Git at Google
namespace extension_misc { const char kPdfExtensionId[] = "mhjfbmdgcfjbbpaeojofohoefgiehjai"; const char kQuickOfficeComponentExtensionId[] = "bpmcpldpdmajfigpchkicefoigmkfalc"; const char kQuickOfficeInternalExtensionId[] = "ehibbfinohgbchlgdbfpikodjaojhccn"; const char kQuickOfficeExtensionId[] = "gbkeegbaiigmenfmjfclcdgdpimamgkj"; const char kMimeHandlerPrivateTestExtensionId[] = "oickdpebdnfbgkcaoklfcdhjniefkcji"; const char kProdHangoutsExtensionId[] = "nckgahadagoaajjgafhacjanaoiihapd"; const char* const kHangoutsExtensionIds[6] = { kProdHangoutsExtensionId, "ljclpkphhpbpinifbeabbhlfddcpfdde", // Debug. "ppleadejekpmccmnpjdimmlfljlkdfej", // Alpha. "eggnbpckecmjlblplehfpjjdhhidfdoj", // Beta. "jfjjdfefebklmdbmenmlehlopoocnoeh", // Packaged App Debug. "knipolnnllmklapflnccelgolnpehhpl" // Packaged App Prod. // Keep in sync with _api_features.json and _manifest_features.json. }; // Error returned when scripting of a page is denied due to enterprise policy. const char kPolicyBlockedScripting[] = "This page cannot be scripted due to an ExtensionsSettings policy."; } // namespace extension_misc
The odd thing is that the source does not match the Chrome web store designation:
Hangouts ExtensionId Source name Web store name nckgahadagoaajjgafhacjanaoiihapdkProdHangoutsExtensionIdGoogle Hangouts ljclpkphhpbpinifbeabbhlfddcpfddeDebugGoogle Hangouts (Extension, Beta); GOOGLE CONFIDENTIAL – FOR INTERNAL USE ONLY ppleadejekpmccmnpjdimmlfljlkdfejAlphaGoogle Hangouts (Extension, Debug) eggnbpckecmjlblplehfpjjdhhidfdojBetaGoogle Hangouts (Extension, Alpha) jfjjdfefebklmdbmenmlehlopoocnoehPackaged App Debug404 error knipolnnllmklapflnccelgolnpehhplPackaged App ProdGoogle Hangouts; Hangouts Chrome App is deprecated. Please switch to the Hangouts Chrome Extension.
You can not start the extensions in a tab; they need to start their view through the extension.
So these links do not work:
chrome-extension://nckgahadagoaajjgafhacjanaoiihapd/mainapp.html?uv_main_windowchrome-extension://ljclpkphhpbpinifbeabbhlfddcpfdde/mainapp.html?uv_main_windowchrome-extension://ppleadejekpmccmnpjdimmlfljlkdfej/mainapp.html?uv_main_windowchrome-extension://eggnbpckecmjlblplehfpjjdhhidfdoj/mainapp.html?uv_main_windowchrome-extension://jfjjdfefebklmdbmenmlehlopoocnoeh/mainapp.html?uv_main_windowchrome-extension://knipolnnllmklapflnccelgolnpehhpl/mainapp.html?uv_main_window–jeroen
Posted in Chrome, Development, Google, GoogleHangouts, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/05/11
Cool Format feature from [WayBack] file – String format procedure similar to writeln – Stack Overflow:
The cool thing about using
Formatis that you use for Format Strings not only to parameterize things likewidthandprecisioninside thatFormat String, but also as parameters like you normally would provide values.You can get very close to using a
widthof 8 and aprecisionof 2, like the example in your question.For instance, to quote the documentation:
Format ('%*.*f', [8, 2, 123.456]);is equivalent to:
Format ('%8.2f', [123.456]);That is a much overlooked feature of
FormatandFormat Strings.
Edit 20250910:
This was part of my answer¹ there to mimic WriteLn formatting behaviour which was not even documented at the now deleted [Wayback/Archive] Standard Routines and I/O.
Normally deleted information like above results in worse information at their current documentation site.
This time however was an exception: the current documentation is better².
¹ the start of my answer:
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development, Undocumented Delphi | Leave a Comment »
Posted by jpluimers on 2021/05/10
Since I always get confused with SAS and SATA connectors, some tables from Wikipedia:
Codename Other names Ext./int. Pins No of devices / lanes Comment Image SFF-8086 Internal mini-SAS, internal mSAS Internal 26 4 This is a less common implementation of SFF-8087 than the 36-circuit version. The fewer positions is enabled by it not supporting sidebands. SFF-8087 Internal mini-SAS, internal mSAS, internal iSAS, internal iPass Internal 36 4 Unshielded 36-circuit implementation of SFF-8086. Molex iPass reduced width internal 4× connector, 12 Gbit/s capability. SFF-8088 External mini-SAS, external mSAS, external iSAS, external iPass External 26 4 Shielded 26-circuit implementation of SFF-8086. Molex iPass reduced width external 4× connector, 12 Gbit/s capability. SFF-8470 InfiniBandCX4 connector, Molex LaneLink External 34 4 High-density external connector (also used as an internal connector). SFF-8482 Internal 29 2 lanes This form factor is designed for compatibility with SATA but can drive a SAS device. A SAS controller can control SATA drives, but a SATA controller cannot control SAS drives. SFF-8484 Internal 32 or 19 4 or 2 High-density internal connector, 2 and 4 lane versions are defined by the SFF standard. SFF-8485 Defines SGPIO (extension of SFF 8484), a serial link protocol used usually for LED indicators. SFF-8613 (SFF-8643) Internal 36 4 or 8 with dual connector Mini-SAS HD (introduced with SAS 12 Gbit/s) SFF-8614 (SFF-8644) External 4 or 8 with dual connector Mini-SAS HD (introduced with SAS 12 Gbit/s) Sideband connector Internal Often seen with 1× SFF-8643 or 1× SFF-8087 on the other end – internal fan-out for 4× SATA drives. Connects the controller to drives without backplane or to the (SATA) backplane and optionally, to the status LEDs. SFF-8680 Internal
- 1
- (2 ports)
SAS 12 Gbit/s backplane connector SFF-8639 Internal 68
- 1
- (2 ports)
- SAS 12 Gbit/s backplane connector;
- revision of the SFF-8680.
- Also known as “U.2”.[17]
SFF-8638
- Four 1x ports at up to 24 Gb/s each;
- two 2x ports at up to 48 Gb/s each;
- one 4x port at up to 96 Gb/s.
SFF-8640
- Four 1x ports at up to 24 Gb/s each;
- two 2x ports at up to 48 Gb/s each;
- one 4x port at up to 96 Gb/s.[18]
SFF-8681
- Two 1x ports at up to 24 Gb/s each;
- one 2x ports at up to 48 Gb/s each.
Data
Standard connector, data segment[42] Pin # Mating Function 1 1st Ground 2 2nd A+ (transmit) 3 2nd A− (transmit) 4 1st Ground 5 2nd B− (receive) 6 2nd B+ (receive) 7 1st Ground — Coding notch
A seven-pin SATA data cable (left-angled version of the connector)
SATA connector on a 3.5-inch hard drive, with data pins on the left and power pins on the right. The two different pin lengths ensure a specific mating order; the longer lengths are ground pins and make contact first.
Power
Standard
Standard connector, power segment Pin # Mating Function — Coding notch 1 3rd 3.3 V Power 2 3rd 3 2nd Enter/exit Power Disable (PWDIS) mode
(3.3 V Power, Pre-charge prior to SATA 3.3)4 1st Ground 5 2nd 6 2nd 7 2nd 5 V Power, Pre-charge 8 3rd 5 V Power 9 3rd 10 2nd Ground 11 3rd Staggered spinup/activity 12 1st Ground 13 2nd 12 V Power, Pre-charge 14 3rd 12 V Power 15 3rd 
A fifteen-pin SATA power connector (this particular connector is missing the orange 3.3 V wire)
Slimline
Slimline connector, power segment Pin # Mating Function — Coding notch 1 3rd Device presence 2 2nd 5 V Power 3 2nd 4 2nd Manufacturing diagnostic 5 1st Ground 6 1st
A six-pin slimline SATA power connector
The back of a SATA-based slimline optical drive
Micro
Micro connector, power segment Pin # Mating Function 1 3rd 3.3 V Power 2 2nd 3 1st Ground 4 1st 5 2nd 5 V Power 6 3rd 7 3rd Reserved — Coding notch 8 3rd Vendor specific 9 2nd 
A 1.8-inch (46 mm) micro SATA hard drive with numbered data and power pins on the connector.
–jeroen
Posted in Hardware, Power User, SAS/SATA, SFF-8087 | Leave a Comment »
The Wiert Corner - irregular stream of stuff 