Reminder to self: check the entries referenced in [WayBack] Judging from recent QP bug resolutions, current status of Delphi compiler is “Leaks all the way” or “Broken by design”. Take your pick… – Dalija Prasnikar – Google+
–jeroen
Reminder to self – check some of the Delphi bug reports to see of they are solved
Posted by jpluimers on 2018/08/22
Posted in Delphi, Development, Software Development | Leave a Comment »
Marvin the Paranoid Android moans about requests for missing pages
Posted by jpluimers on 2018/08/22
A great 404-page: [WayBack] Marvin the Paranoid Android moans about requests for missing pages.
The fun about the WayBack link is that it fills the first memo field it finds (:
–jeroen
via: [WayBack] Ruurd Pels on Twitter: “@jpluimers https://t.co/TKFlzTmQLW”
Share this:
Posted in Development, Fun, Software Development, Web Development | Leave a Comment »
Nick Craver on Twitter: “This is worth repeating: We’re migrating Stack Overflow to .NET Core. **It’s not because of performance**. There are enough major wins without even factoring performance for us to move. Any performance gains are 100% in the bonus category. We’d migrate with a 0% perf improvement.…”
Posted by jpluimers on 2018/08/21
If you are on .NET, migrate to .NET Core. If you start with .NET, start with .NET Core.
Based on:
- [WayBack] Nick Craver on Twitter: “This is worth repeating: We’re migrating Stack Overflow to .NET Core. **It’s not because of performance**. There are enough major wins without even factoring performance for us to move. Any performance gains are 100% in the bonus category. We’d migrate with a 0% perf improvement.”
- [WayBack] Nick Craver on Twitter: “No clue! Honestly. There are enough wins from us in a .NET Core migration (e.g. maintenance, open source/fixes, SDK projects, running in a container or appliance, etc.) that performance literally isn’t on my list. We know it’s better, but really don’t care by how much.… https://t.co/p5TdJdxeVJ”
–jeroen
Edit: nice comment on [WayBack] If you are on .NET, migrate to .NET Core. If you start with .NET, start with .NET Core. Based on: [WayBack] Nick Craver on Twitter: “This is worth repea… – Jeroen Wiert Pluimers – Google+:
We are porting Continua CI to .net core 2.1, I’ve been working on it for a few months now (along with other things of course), I had to contribute to a few open source projects to help get all our dependencies onto .net core, and for the most part it’s been pretty easy. I did have to change the windows service stuff, and since there is no WCF server stuff in .net core we have to find a replacement for that for server to agent communications (still exploring options, but probably going with halibut).What hasn’t (and still isn’t) easy is porting MVC4/5 stuff to asp.net core. So many little changes that drive me absolutely potty. I was getting so frustrated that I had to put it aside for a while and work on other things, just to get my sanity back!
Share this:
Posted in .NET, .NET Core, Development, Software Development | Leave a Comment »
Delphi SOAP service: only publish WSDL in RELEASE mode
Posted by jpluimers on 2018/08/21
If you want to restrict the WSDL publishing so it only is published in DEBUG mode, then add a [WayBack] TWSDLHTMLPublish to your [WayBack] TWebModule descendant, then add this in the [WayBack] OnCreate event handler of that TWebModule descendant:
// Enable/disable handling of "/wsdl*" requests during DEBUG/RELEASE mode. Enabling sends them via
// Handled := WSDLHTMLPublish1.DispatchRequest(Sender, Request, Response);
{$ifdef DEBUG}
WSDLHTMLPublish1.WebDispatch.Enabled := True;
{$endif DEBUG}
{$ifdef RELEASE}
WSDLHTMLPublish1.WebDispatch.Enabled := False;
{$endif DEBUG}
end;
I have limited this because there are so many hard coded strings in the TWSDLHTMLPublish, see the thread by [WayBack] Marjan Venema at [WayBack] Hide WSDL document in SOAP app – delphi
–jeroen
Share this:
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | Leave a Comment »
Full Duplex Asynchronous Read/Write with Named Pipes – CodeProject
Posted by jpluimers on 2018/08/21
When you run on Windows: [WayBack] Full Duplex Asynchronous Read/Write with Named Pipes – CodeProject
via:
- [WayBack] Best C# Article of March 2017 Marc Clifton – Full Duplex Asynchronous Read/Write with Named PipesRunner UpMarco-Hans Van Der Willik – Threading -Under the Hood http://buff.ly/2qEtG8o – CodeProject – Google+
- [WayBack] Best C# Article of March 2017 Marc Clifton – Full Duplex Asynchronous Read/Write with Named Pipes – Jeroen Wiert Pluimers – Google+
–jeroen
Share this:
Posted in .NET, C#, Development, Software Development, WinForms | Leave a Comment »
For my research list: Delphi and ZeroMQ
Posted by jpluimers on 2018/08/21
Last year, ZeroMQ – of late Pieter Hintjens ancestry – got a decent support library for Delphi https://github.com/grijjy/DelphiZeroMQ.
While writing, there is a reasonable chance I need to do message queue work and ZeroMQ is excellent. I’ve done MQ already in other environments with various projects involving Wintel/iSeries, WebSphere MQ (now IBM MQ, formerly MQSeries), Oracle AQ and Microsofts MSMQ stacks so I’m anxious to see if and how this works out.
via:
- [WayBack] Roll your own lightweight, scalable backend using ZeroMQ – grijjy blog
- [WayBack] Roll your own lightweight, scalable backend using ZeroMQ with our Majordomo protocol implementation for Delphi – Allen Drennan – Google+
–jeroen
Share this:
Posted in Delphi, Development, Software Development | 2 Comments »
Plastic SCM compare versus Beyond Compare; guess which screenshot I like most
Posted by jpluimers on 2018/08/20
Same difference; two tools.
Plastic SCM compare: lots of clutter
Beyond Compare: just the things that are different.
–jeroen
Share this:
Posted in Beyond Compare, Development, PlasticSCM, Power User, Source Code Management | 3 Comments »
Drone no-fly zones | ministerie van Infrastructuur en Milieu
Posted by jpluimers on 2018/08/20
If you ever want to fly a drone without a license in The Netherlands, be prepared that the flying zones are very limited, especially in : [Archive.is] Drone no-fly zones | ministerie van Infrastructuur en Milieu
The text isn’t very clear, even to Dutch people, so there is some discussion and explanation in these links:
- [WayBack] Tips voor de staatssecretaris voor veilig vliegen met drones in Nederland
- [WayBack] Drone Regels & Regelgeving Nederland 2017 | Online uitleg
- [WayBack] Ministerie geeft toelichting op regelgeving drones | Dronewatch
More temporary airspace restrictions are here:
–jeroen
Share this:
Posted in LifeHacker, Power User | Leave a Comment »
when bind named service hasn’t started after OpenSuSE Tumbleweed boots
Posted by jpluimers on 2018/08/20
A while ago, named would not start any more after I rebooted my Tumbleweed systems.
I had this behaviour on multiple systems, each installed quite a while ago and kept up-to-date with zypper dist-upgrade so it looked like a systematic issue.
Below are steps in researching the problem together with the helpful people on the IRC channel opensuse-factory.
Background reading for some of the commands: [WayBack] How To Use Systemctl to Manage Systemd Services and Units | DigitalOcean.
Both systemctl status named.service and systemctl status named would show the same output:
# systemctl status named
● named.service - LSB: Domain Name System (DNS) server, named
Loaded: loaded (/etc/init.d/named; generated; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
Getting the log from events around a reboot would show a successful shutdown, but no start:
# journalctl --unit named --catalog --pager-endApr 28 13:19:27 laurel systemd[1]: Stopping LSB: Domain Name System (DNS) server, named... -- Subject: Unit named.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has begun shutting down. Apr 28 13:19:28 laurel named[20360]: no longer listening on 192.168.124.27#53 Apr 28 13:19:28 laurel named[20360]: no longer listening on 192.168.124.27#53 Apr 28 13:19:32 laurel named[20360]: received control channel command 'stop' Apr 28 13:19:32 laurel named[20360]: shutting down: flushing changes Apr 28 13:19:32 laurel named[20360]: stopping command channel on 127.0.0.1#953 Apr 28 13:19:32 laurel named[20360]: no longer listening on ::#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on ::#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on 127.0.0.1#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on 127.0.0.1#53 Apr 28 13:19:32 laurel named[20360]: exiting Apr 28 13:19:34 laurel named[30705]: Shutting down name server BIND waiting for named to shut down ..done Apr 28 13:19:34 laurel systemd[1]: Stopped LSB: Domain Name System (DNS) server, named. -- Subject: Unit named.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has finished shutting down.
Similar results in these files:
/var/lib/named/log/general.log
28-Apr-2017 13:19:32.465 general: shutting down: flushing changes
28-Apr-2017 13:19:32.468 general: stopping command channel on 127.0.0.1#953
28-Apr-2017 13:19:32.622 general: exiting
/var/lib/named/log/named.log
28-Apr-2017 13:19:32.489 network: no longer listening on ::#53
28-Apr-2017 13:19:32.489 network: no longer listening on 127.0.0.1#53
With systemctl, I got this:
# systemctl is-enabled named named.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named enabled # systemctl is-active named inactive # systemctl is-failed named inactive
After this, I was out of systemd and sysv knowledge, so I asked for help on the #openSUSE-factory IRC channel, where ismail was of great help.
Share this:
Posted in *nix, *nix-tools, bind-named, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
On Windows Control Flow Guard effects: 24-core CPU and I can’t type an email (part one) | Random ASCII
Posted by jpluimers on 2018/08/19
So many interesting bits on Windows process behaviour investigations: https://randomascii.wordpress.com/2018/08/16/24-core-cpu-and-i-cant-type-an-email-part-one/
Via Check out @BruceDawson0xB’s Tweet:
Share this:
Posted in Uncategorized | Leave a Comment »
The Wiert Corner - irregular stream of stuff 