Posted by jpluimers on 2021/04/13
Depending on the issue type, a workflow might be different.
Since for Software projects, the default workflow Story might not be appropriate during the workflow, it makes sense to convert it.
For issue types other than sub-task, the dropdown only has one conversion entry: “convert to sub-task” (a sub-task has only “Convert to Issue”).
In order to convert to other issue types, use the “Move” option. There in the first step, you can change the issue type.
Related:
Posted in Development, Issue/Bug tracking, JIRA, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/13
Just so I remember this did not compile in Delphi XE8 a while ago:
[dcc32 Fatal Error] DisableAlignPropertyEditor.dpr(15): E2213 Bad packaged unit format: c:\program files (x86)\embarcadero\studio\16.0\lib\Win32\release\rtl.dcp.System.SysUtils - Expected version: 29.0, Windows Unicode(x86) Found version: 32.0, Windows Ansi(x86)
Possible starting point: “E2213 Bad packaged unit format” “Expected version” “Found version” “Windows Unicode” “Windows Ansi” – Google Search
–jeroen
Posted in Delphi, Delphi XE8, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/08
Some links for my archive:
–jeroen
Posted in .NET, Database Development, Development, PostgreSQL, Software Development, SQL Server | Leave a Comment »
Posted by jpluimers on 2021/04/08
Interesting idea by Cesar Romero (who has some interesting repositories at [WayBack] cesarliws (Cesar Romero) · GitHub and [WayBack] cesarliws — Bitbucket) when using TestInsight for Delphi: first test if TestInsight is running at all: [WayBack] foundation-4-delphi/Foundation.Test.Utils.pas at master · cesarliws/foundation-4-delphi · GitHub.
function IsTestInsightRunning: Boolean; {$IFDEF TESTINSIGHT} var TestInsightClient: ITestInsightClient; begin TestInsightClient := TTestInsightRestClient.Create; TestInsightClient.StartedTesting(0); Result := not TestInsightClient.HasError; end; {$ELSE} begin Result := False; end; {$ENDIF} procedure RunRegisteredTests; begin ReportMemoryLeaksOnShutdown := True; {$IFDEF TESTINSIGHT} if IsTestInsightRunning then TestInsight.DUnit.RunRegisteredTests else {$ENDIF} DUnitTestRunner.RunRegisteredTests; end;
Another interesting bit from the same library is the deferer pattern (which is different from the promise pattern!) in [WayBack] foundation-4-delphi/Foundation.System.pas at master · cesarliws/foundation-4-delphi · GitHub with the below code examples.
I think a better name might be DeferExecutionToEndOfScopeFor.
procedure ProcessFile (const FileName: string); var File: TFile; begin File: = TFile.Open (FileName); Defer (File.Close); while not File.EOF begin // ... process file end; end; // Defer will be executed here [File.Close] procedure ExecSql (const ConnectionString, Sql: string); var Database: TDatabase; Exec: IDeferred; Query: TQuery; begin Database: = TDatabase.Create (ConnectionString); Exec: = Defer (Database.Free); Database.Open; Exec.Defer (Database.Close); Query: = Database.Query (SQL); Exec.Defer (Query.Free); Exec.Defer (Query.Close); if Query.IsEmpty then Exit; while not Query.EOF begin // ... process query end; Exec.Defer ( procedure begin Writeln ('Finished ExecSql'); end ); end; // Defer will be executed here [Writeln, Query.Close, Database.Close, Database.Free]
–jeroen
Posted in Delphi, Development, Software Development, Spring4D, TestInsight | Leave a Comment »
Posted by jpluimers on 2021/04/07
compact-directory-recursively.bat:
if [%1]==[] goto :eof call compact /s /c %1 %1\*.*
Example usage:
compact-directory-recursively.bat C:\ProgramData\{51D553F1-B483-41C2-B35E-6D461D9E0F9C} compact-directory-recursively.bat "C:\ProgramData\Package Cache" @for /d %d in (*.*) do @call compact-directory-recursively.bat "%d"
The @ signs are to get less output clutter.
–jeroen
Posted in Batch-Files, Development, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/07
For past timestamps (or date-times), as long as you know the associated location, you always know the time zone rule that applies, no matter if you store them in UTC or local time zone.
For future dates, UTC might not be the best option, as you have no knowledge on future time zone rules. There you need to have at least three fields:
Posted in .NET, Algorithms, Development, Jon Skeet, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/07
From a check-in a while ago, when some Delphi versions complained about CallerAddr having been replaced by ReturnAddress and other versions not understanding ReturnAddress, but having CallerAddr.
The code in the [WayBack] gist and on [WayBack] BitBucket:
ReturnAddressUnitto provideReturnAddressto Delphi versions not supporting it, and preventCallerAddrwarnings for Delphi versions havingReturnAddress. See https://bitbucket.org/jeroenp/wiert.me/src/…/Native/Delphi/Library/RTL/ReturnAddressUnit.pas
Basically the code maps a variable having a variable ReturnAddress that is a function reference returning a pointer to a function and redirects to CallerAddr when there is no ReturnAddress available. This is the case for anything below Delphi XE2, and avoids W1000 Symbol 'CallerAddr' is deprecated: 'Use ReturnAddress' for Delphi XE2 and up
It is an extract from [WayBack] dunit-extension/TestCaseExtension.pas at master · fabriciocolombo/dunit-extension · GitHub.
There is more interesting code in [WayBack] GitHub – fabriciocolombo/dunit-extension: Extended DUnit TestCase provides assertions to the types Date, Enumerator, Double, and other types, and a class to help run tests with output as XML, text and GUI mode and even more in [WayBack] fabriciocolombo (Fabricio Colombo) · GitHub , which are on my list of things to play with in the future.
Some more [WayBack] commits are at [WayBack] GitHub – cesarliws/dunit-extension (more on [WayBack] Cesar Romero tomorrow).
I think the code from Fabricio is inspired by [WayBack] ZeosLib/TestFrameWork.pas at master · svn2github/ZeosLib · GitHub as it uses the same HAS_BUILTIN_RETURNADDRESS define.
The code by Fabricio is smarter though.
Via: “Delphi” “CallerAddr” “ReturnAddress” – Google Search
–jeroen
Posted in Delphi, Development, DUnit, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/06
[WayBack] LeanEssays: What If Your Team Wrote the Code for the 737 MCAS System?.
When involved in writing systems, I always ask the question “Is a large crisis possible because of this system?”. When yes, such a system needs engineering mode, resulting much more vigorously asking questions on the things that can wrong and how to prevent anything that can go wrong.
So I wholeheartedly agree with Mary Poppendieck making these statements in the above article:
- One thing we knew for sure – we were responsible for designing safe systems, and we were not going to delegate that responsibility to anyone else. Another thing we knew for sure was that anything that could go wrong would eventually go wrong – so every element of our systems had to be designed to fail safely; every input to our system was suspect; and no output could be guaranteed to reach its destination. And because my seasoned engineering colleagues were suspicious of automation, they added manual (and very visible) emergency stop systems that could easily and quickly override my automated controls.
- would you write the code as specified, or would you ask some questions – such as “What if the stall signal is wrong, and there really isn’t a stall?” Or “Under what conditions do we NOT send an adjustment signal?” Or “When and how can the system be disabled?”
Software engineers need to understand what civil engineers learn as undergraduates – safety is not someone else’s job; it is the responsibility of every engineer involved in the design and implementation of a system whose failure might cause harm. If your team is not ready to accept this responsibility, then call yourselves developers or programmers or technicians – but not engineers.
Proper engineers can do this, even in an agile environment.
–jeroen
Via [WayBack] Mary Poppendieck on Twitter: “It was not a software malfunction that caused two 737 MAX airplanes to crash – the software did exactly what it was supposed to do. But does this mean that software engineers have no responsibility for safety? My 2 cents: …”
Posted in Agile, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/06
Last week, I wrote about msbuild verbosity levels. The post was both for my own documentation, but also out of need as I wanted to have way more verbose logging for a Delphi build process involving search path configurations.
When using my Delphi build script you can both pass msbuild options and Delphi compiler options:
Run-Dependend-rsvars-From-Path.bat 5 msbuild -verbosity:detailed "/p:DCC_OutputDependencies=true" MyProject.dproj
The bold one is the msbuild parameter, the italic one the Delphi compiler parameter for unit dependencies. They are directly passed to msbuild:
...\msbuild.exe /target:build /p:DCC_BuildAllUnits=true /p:config=Debug -verbosity:detailed "/p:DCC_OutputDependencies=true" MyProject.dproj
You can multiple options too:
Run-Dependend-rsvars-From-Path.bat 5 msbuild -verbosity:detailed "/p:DCC_OutputDependencies=true" "/p:DCC_Quiet=false" MyProject.dproj
In addition to unit dependencies, you can also get an overview of .dfm and other resource file dependencies by passing /p:DCC_OutputDRCFile=true on the command-line this will generate a DRC file that not just has all the resource string constants in it, but also a comment section specifying all resource files including these file types:
.dfm (form files).drf (which seems to be a temporary file having to do with package reference dependencies: [WayBack] What is a DRF file? Why is there a problem creating it?, [WayBack] packages – Delphi “E2161 Error: RLINK32: Error opening file ________.drf ” during Build All – Stack Overflow).res (resource files)Both DCC_OutputDependencies and DCC_OutputDRCFile can also be set to true in a .dproj file and are configurable under two different project option paths:
DCC_OutputDependencies: “Project Options” -> “Delphi Compiler” -> “Compiling” -> “Output unit dependency information”DCC_OutputDRCFile: “Project Options” -> “” -> “Delphi Compiler” -> “Linking” -> “Ouput resource string .drc file”The -verbosity:detailed however, is not passed to the various Delphi DCC compilers, as somewhere along the line, the CodeGear.Delphi.Targets got changed to Quiet="true" somewhere in-between Delphi 2007 and Delphi 2010.
Delphi 2007 had from
Borland.Delphi.Targetsfiles containing fromQuiet="$(DCC_Quiet)"; the file got renamed and changes likely in Delphi 2009. See these related posts:
- [WayBack] QualityCentral 56289: MSBuild does not pass the quiet option to DCC32
- [WayBack] delphi – Is there a way to turn off the quiet mode in DCC32 called by MSBuild? – Stack Overflow
- [WayBack] How can I get MSBuild to do a full build of a Delphi project equivalent to dcc32 -b? – Stack Overflow
- [WayBack] 2018-03-31 – twm’s blog: Specifying the msbuild configuration for a Delphi project on the commandline
- [WayBack] What are the MSBuild project level properties for Delphi? – Stack Overflow
- [WayBack] Delphi MSBuild Build Configurations From Command Line – Stack Overflow
- [WayBack] Command line build questions : MSBUILD console output is either wickedly verbose (compiling delphi .dprojs) or completely off. – delphi
This means as of then on, the DCC commandline compilers will always output non-verbose logging. Even specifying "/p:DCC_AdditionalSwitches=-Q-" will not help: you will just get blank lines.
In the past, one of the things the verbose DCC logging would help you to see which files where accessed using the actual build. This was a tremendous help when figuring out search path problems that kick in every now and then.
For units, there is a little trick you can use here: it’s the /p:DCC_OutputDependencies=true" option you see above.
It will output an additional file with the .d extension that:
That file is relatively easy to scan or parse for path problems.
I am not sure at which Delphi version the depends feature became a project setting, but it is. The odd thing: it does not always work, at least not in the Delphi 102. Tokyo installations I have used.
In a .dproj file, it is inside this element: <DCC_OutputDependencies>true</DCC_OutputDependencies> just like the msbuild name.
In the UI, you can find it here:
DCC_AdditionalSwitches and /p:DCC_AdditionalSwitches
msbuild %1 /t:Build /p:config=%2 /p:DCC_AdditionalSwitches="-W^"
and
msbuild %1 /t:Build /p:config=%2 /p:DCC_Warnings=error="-W^"
DCC_OutputDependencies and and p:/DCC_OutputDependencies
–jeroen
Posted in Continuous Integration, Delphi, Development, msbuild, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/06
If you want to run both DUnitX and DUnit tests in a test project using TestInsight as runner encapsulation, then you need to be aware that when there are no DUnitX tests, it will raise an exception.
So use this code to prevent that:
try TestInsight.DUnitX.RunRegisteredTests; finally TestInsight.DUnit.RunRegisteredTests; end;
–jeroen
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 