pvandervelde / nanicitus

nAnicitus is a windows service that acts as a gatekeeper for the SymStore application.

Welcome to Patrick's corner

I've been a software engineer for 15 years. I've worked in a range of industries, from emergency services to the cinema, and on projects where software shipped directly customers or to internal development teams.

I'm interested in designing and building autonomous mobile robots with four-wheel independent steering (also known as a swerve drive). The prototype has ROS2 code for robot description, the Gazebo world and the steering controller. I've also contributed a significant amount of the ROS code for the SCUTTLE robot.

Other interests include:

• All kinds of autonomous mobile robots
• Electronics
• Computer Aided Design (Rhino3d, Fusion360, AutoCAD)
• Rock climbing
• Gardening
• Woodworking

Latest

• Swerve drive - Motor limitations
• Four wheel steering simulation - 0 degree linear to rotation - velocity limited
• Swerve drive - Using Nav2
• Robotics - Making URDF models
• Four wheel steering robot - Omnidirectional drive
• Swerve drive - Motion profiles
• Swerve drive - Control animations
• Swerve drive - Better movement by controlling the body motions
• Swerve drive - Verification of the kinematics solution
• Four wheel steering model with ROS2 controllers - Ignition Gazebo first movement

Github stats

nanicitus's Issues

Created embedded stream from template

Allow users to specify a 'template' of what needs to be embedded so that the user can specify UNC or HTTP streams and the format in which the files are laid out on the disk.

Verify correctness of embedded symbol server streams

The process of embedding the symbol server stream is currently not verified. It is therefore possible that the process failed (for some reason) without reporting an error. This problem won't be found until the symbols are required for a debugging session, at which point it is too late to fix the issue, so it would be good to have some kind of way to verify that the symbol stream has been embedded correctly and that the source files are in the correct location etc. etc.

Service should be able to stream metrics to a metrics server

The service should be able to provide information about it's state and what it has processed to a metrics server

Update the build scripts to the latest version of nBuildKit

Provide re-processing option

To re-process all symbols. This is useful if the embedded stream needs to change

Set up build server on AppVeyor

Verify hashes of the source files when compared to the PDB values

The PDB embeds the (MD5?) hashes of the source files that were used for the current PDB. nAnicitus should verify that the sources that are provided match those hashes and error out if not.

Symbol processing stops processing new packages

After an amount of time the symbol processor stops processing new symbol packages. The log files indicate that the new packages are detected and that a new processing Task is started but the packages are never processed.

Service should write logs to a central log server

Update to .NET core

Provide validation option

This option should just validate that the symbol package could be processed.

Make service a self-hosted HTTP service

So allow users to push symbols to the http service which then drops the files in the queue to be processed

Service should register with service discovery system

At first only support Consul but keep it open enough to add other systems.

Before processing a symbol package verify that that package has not already been processed

Processing of symbol packages should be done only after it has been verified that there is not already an existing version of that package.

Provide docker container

Should be deployed to a windows docker container (or multiple if we split the service)

Provide tools to enable source indexing during the build process

The symbol and source indexing could be done on the build server, which means it would be possible to fail the build if the indexing fails for some reason. This would provide more visibility.

Obviously this also requires the ability to verify the indexing, but without exposing the indexed files to the outside world.