kicker | flexible file-change watcher

I am trying to append every column from one row into another row, I want to do this for every row, but some row will not have any values, take a look at my code it will be more clear:

Here is my data

I am troubleshooting an issue that just came up while using Gorm. I had everything working great with my sqlite3 database and Go data models, but then when I had some issues with dependencies not 'go get'ing in the build environment, so I tried copying/deleting some packages from the vendor folder, re 'go get'ing until I got the build working... But now when I compile and run in my own machine, Im getting issues I never had before.

When I attempt something like this (configID is already checked to ensure it has a valid entry):

I have a scatterplot that consists of multiple subplots using seaborn's "col" and "row" feature, e.g.

Pulling my hair here, trying to use jq to parse and extend a JSON file and adding an element at a specific position based on a certain condition. Here is a sample file (also at https://jqplay.org/s/6cjmbnvrqu)

I have two models Pick and GamePick. GamePick has a ForeignKey relation to Pick, which is accessible on Pick.game_picks.

I have setup GamePick with a custom queryset and manger so that when ever I retrieve a GamePick with the manager objects is is annotated with a field is_correct based on the values of other fields.

Now what I want to be able to do is count the how many correct GamePicks are pointing to a specific Pick.

One simple way is doing this with a method in Python:

Over a year ago I began writing a .NET Framework 4.6.1 app using Windows Forms. At the time I knew about WPF, yet was familiar with Windows Forms and it had most of the controls I needed. For the missing controls, I wrote two in Windows Forms and one in WPF. All of these coexisted fine, with the WPF control containerized within an element host.

This week I began the migration process to .NET Core 3.1. My tests with a copy of the project were positive, as well as initial results with the actual migration. After minor refactoring, the solution built and ran without issue. Then the gremlin appeared after opening the main UI form in the WinForms Designer. Back in .NET Framework, all of my custom controls appeared inside the Designer's Toolbox, providing easy drag-and-drop onto the form. In .NET Core, only my WinForms controls appeared in the Toolbox, not my WPF control. Because the Designer could not see that control, it stripped it from the Form's designer code, leaving an empty element host behind.

Here's the kicker. After reverting the Designer's changes, any direct manual edits to the Form's designer code is accepted, and building the project succeeds and runs fine. So for some reason the Designer does not like WPF controls in WinForms.

Things I've tried:

• During my testing I discovered that the main WinForms UI needed both "UseWindowsForms" and "UseWPF" set to "true" for the project to compile. I then added the "UseWindowsForms" parameter to the WPF user control library. This caused the control to appear in the Designer's Toolbox, yet attempting to add the control resulted in this error: "Failed to create component ... Microsoft.DotNet.DesignTools.Client.DesignToolsServerException ... Make sure the type implements IComponent and provides an appropriate public constructor. Appropriate constructors either take no parameters or take a single IContainer parameter." And the existing WPF control in the code was still removed.
• I copied the WPF control from the library to the main UI project, edited the namespace, and removed the library project reference. Same result as above.
• Created a new Windows Forms User Control library, added "UseWPF" to the project, and copied the WPF control to this library. Same result as above.
• Back to the test copy of my project, I followed Microsoft's guides for "try-convert" and "upgrade-assistant". The latter seemed promising at first, as it replaced, modified, or removed outdated referenced and packages. But, no success.
• Tried the above migration steps with both .NET Core 3.1 and .NET 5. Same results.

The point I'm at now is to keep manually editing the Form's designer code. Not ideal for large changes, and also not sustainable if/when this project is passed to another developer. Any thoughts? Should I attempt porting the Windows Forms UI to WPF? Or is this simply a maturity issue with the still relatively new .NET Core Windows Forms Designer?

Visual Studio version: Community 2019 16.9.3

Screenshot of IComponent error: enter image description here

I have a table (example below)

When using io.Copy with an invalid writer, I get a panic - that's expected. However I can't recover when this is the case. My deferred recover is completely bypassed. Here is the code:

In short: I am unable to run my app in the iPhone Simulator. There is no "Play button" (the triangle), only a Debugger button (hammer):

As you can see above I have "Generic Simulator". When I click on it, there is no list of various iPhones/iPads to choose from:

If I choose Android, I am able to run the app:

I have XCode installed. I ran XCode once. I also installed the Command Line tools.

I created a new Xamarin Forms App: Here are my iOS build options:

I am able to run the Simulator separately:

Creating an App in XCode and running in the Simulator works:

info.plist:

Prefrences -> SDK Locations -> Apple

Build -> Configurations:

Here is the kicker though. If I run a Xamarin App on my Windows machine using the iPhone Simulator on the Mac, it works! What do I need to do so I can run my app inside the Simulator vis Visual Studio for Mac?