profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/filipnavara/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Filip Navara filipnavara eM Client, Inc. Prague Some say I am a bot, others already know it.

1hub/springburg 4

OpenPGP for .NET

filipnavara/core 1

Home repository for .NET Core

filipnavara/coreclr 1

This repo contains the .NET Core runtime, called CoreCLR, and the base library, called System.Private.Corelib (or mscorlib). It includes the garbage collector, JIT compiler, base .NET data types and many low-level classes. We welcome contributions.

filipnavara/corefx 1

This repo contains the .NET Core foundational libraries, called CoreFX. It includes classes for collections, file systems, console, XML, async and many others. We welcome contributions.

filipnavara/corert 1

This repo contains CoreRT, a .NET Core runtime optimized for AOT (ahead of time compilation) scenarios, with the accompanying .NET native compiler toolchain.

filipnavara/gcfg 1

read INI-style configuration files into Go structs; supports user-defined types and subsections

filipnavara/go-git 1

A highly extensible Git implementation in pure Go.

emclient/bc-csharp 0

Bouncy Castle C# Distribution (Mirror)

issue commentdotnet/runtime

OperatingSystem.IsWindowsVersionAtLeast and SupportedOSPlatformAttribute using different version numbers for older Windows

On second thought lot of the docs (https://github.com/dotnet/docs/blob/main/docs/standard/analyzers/platform-compat-analyzer.md) still use the marketing version numbers. I suppose it should be fixed and clarified.

mikestek

comment created time in 6 hours

issue commentdotnet/runtime

OperatingSystem.IsWindowsVersionAtLeast and SupportedOSPlatformAttribute using different version numbers for older Windows

Both of them should use the version numbers reported by the system (ie. 6.x). Some of the annotations were incorrect and fixed recently.

mikestek

comment created time in 6 hours

pull request commentxamarin/Xamarin.Legacy.Sdk

Add macOS support

🎉

filipnavara

comment created time in 14 hours

startedqmfrederik/darling-arm64

started time in 18 hours

startedtusdotnet/tusdotnet

started time in 18 hours

startedmicrosoft/MSBuildLocator

started time in 19 hours

push eventfilipnavara/xf-dependabot

Filip Navara

commit sha f6f35a70752e9576972daae0c2f28add4f3c8a35

Create dependabot.yml

view details

push time in a day

create barnchfilipnavara/xf-dependabot

branch : master

created branch time in a day

created repositoryfilipnavara/xf-dependabot

created time in a day

issue commentNuGet/NuGetGallery

[NuGet.org Bug]: Search endpoint returns old versions

Thanks for the detailed reply. I forwarded link to it to the support ticket for GitHub Dependabot.

filipnavara

comment created time in a day

pull request commentxamarin/Xamarin.Legacy.Sdk

Add macOS support

Looks like a new macOS 11 image went live around ~8 hours ago. Hopefully the Xcode step should succeed now.

filipnavara

comment created time in a day

startedjonathanpeppers/CustomResourceDesigner

started time in a day

issue openedNuGet/NuGetGallery

[NuGet.org Bug]: Search endpoint returns old versions

Impact

I'm unable to use NuGet.org

Describe the bug

Search endpoint fail to return newest versions of the Xamarin.Forms package. This breaks dependency updates through GitHub Dependabot.

Repro Steps

Hit any of the search endpoints with the following query:

  • https://api-v2v3search-0.nuget.org/query?q=xamarin.forms
  • https://azuresearch-usnc.nuget.org/query?q=xamarin.forms

Notice that the latest returned package versions are 4.3.

When looking at https://www.nuget.org/packages/Xamarin.Forms/ you can see the latest version is 5.0.0.2125.

Expected Behavior

Version 5.0.xxxx should be returned.

Screenshots

No response

Additional Context and logs

No response

created time in a day

push eventfilipnavara/Xamarin.Legacy.Sdk

Filip Navara

commit sha 2e5cc5bd511a624a3ccea6c723b134958796f73b

Switch to Xcode 13 beta

view details

push time in 2 days

pull request commentxamarin/Xamarin.Legacy.Sdk

Add macOS support

Looks like there's some attempt to bring back Xcode 13 beta 5 back into the images. Not sure if it's deployed already.

filipnavara

comment created time in 2 days

pull request commentxamarin/Xamarin.Legacy.Sdk

Add macOS support

Thanks for the merge. Looks like the macOS image was updated with Xcode 13 RC already (which dropped macOS 12 SDK at last minute) :-(

filipnavara

comment created time in 2 days

startedreportportal/reportportal

started time in 2 days

pull request commentxamarin/Xamarin.Legacy.Sdk

Add macOS support

I wanted to re-run the GitHub Actions / Azure Pipelines but apparently I don't have enough rights to do so.

filipnavara

comment created time in 3 days

push eventfilipnavara/Xamarin.Legacy.Sdk

Filip Navara

commit sha 5ed46a896e4e52483dd29ad659a5437eb998d104

Empty commit

view details

push time in 3 days

startedNivNavick/trxer

started time in 3 days

issue commentxamarin/xamarin-macios

Xamarin.iOS 15 download link?

Apple made a last minute change by removing the macOS 12 SDK in the Xcode 13 RC. At the moment there's no release with the appropriate support.

amirvenus

comment created time in 5 days

create barnchemclient/cef

branch : em-3770

created branch time in 5 days

create barnchemclient/cef

branch : em-3683

created branch time in 5 days

create barnchemclient/cef

branch : em-3578

created branch time in 5 days

create barnchemclient/cef

branch : em-3538

created branch time in 5 days

create barnchemclient/cef

branch : em-2623

created branch time in 5 days

push eventemclient/cef-mirror

Marshall Greenblatt

commit sha 4a44e16a090c5a19d858d80f7f012786acd05a7a

views: Add support for absolute positioned overlay views. To test: Run `cefclient.exe --use-views --hide-frame --hide-controls` Add `--enable-chrome-runtime` for the same behavior using the Chrome location bar instead of a text field.

view details

Marshall Greenblatt

commit sha b3f5d7dd59fce6f9ab496d445023f9d189853540

alloy: Enable BackForwardCache support (see issue #2421) BackForwardCache is currently being tested via field trials (see https://crbug.com/1171298) and can be explicitly disabled using the `--disable-back-forward-cache` or `--disable-features=BackForwardCache` command-line flags. The default behavior now matches the Chrome runtime.

view details

Marshall Greenblatt

commit sha 7a56371b84fb67f3ac0dad1a0dadc604fe584e54

Fix draggable region update with BackForwardCache enabled (see issue #2421) When BackForwardCache is enabled and the user navigates the main frame back/forward a new RFH may be created for an existing main frame GlobalId value and CefFrameHostImpl (e.g. an object that was previously Detach()ed after main frame navigation called SetMainFrame, but for which RenderFrameDeleted was not subsequently called due to insertion in the BackForwardCache). In this case we can re-attach the new RFH to the existing main frame CefFrameHostImpl in RenderFrameHostStateChanged and resume processing of messages. Swapping back/forward to an existing (already loaded) renderer does not trigger new notifications for draggable regions (e.g. RenderFrameObserver:: DraggableRegionsChanged is not called by default). We therefore explicitly request an update of draggable regions by sending the DidStopLoading message to the renderer. A new |reattached| parameter is added to CefFrameHandler::OnFrameAttached to support identification of BackForwardCache usage by the client. To test with unit tests: Run `ceftests --gtest_filter=DraggableRegionsTest.DraggableRegionsCrossOrigin --enable-features=BackForwardCache` To test manually: 1. Run `cefclient --enable-features=BackForwardCache --use-views --url=http://tests/draggable`, note that draggable regions work. 2. Load https://www.google.com via the address bar, note that draggable regions are removed. 3. Go back to http://tests/draggable, note that draggable regions work. 4. Go forward to https://www.google.com, note that draggable regions are removed.

view details

Marshall Greenblatt

commit sha db807e804a0bcb23d3b137da4cba5ea8d8234632

alloy: Fix FrameHandlerTest failures with BackForwardCache enabled (see issue #2421) To test: Run `ceftests --gtest_filter=FrameHandlerTest.OrderSub* --enable-features=BackForwardCache`

view details

Marshall Greenblatt

commit sha 84117f2d1be1ce54513290d835c4dcb79da750d4

Don't use NotificationStateLock for GetMainFrame (see issue #2421) This causes a race related to |notification_state_lock_| assignment when GetMainFrame is called from multiple threads. GetMainFrame doesn't trigger any notifications so it shouldn't need that lock. Instead, only use NotificationStateLock on the UI thread.

view details

push time in 5 days

issue commentdotnet/linker

Unable to resolve some types from System.Runtime.dll in custom linker step

Now, I cannot answer that so hopefully @rolfbjarne will chime in. On the Xamarin tracking issue it's listed as P1, or "something we can't go to stable with".

The original issue was tracked as https://github.com/xamarin/xamarin-macios/issues/12275, which split off from on-device tests.

rolfbjarne

comment created time in 5 days

issue commentdotnet/linker

Unable to resolve some types from System.Runtime.dll in custom linker step

@agocke It was tracked in the issues for quite a while as failed builds so it was likely always happening after the .NET 6 shift. It took time to track down the root cause though.

rolfbjarne

comment created time in 5 days