profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Danielku15/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.

Danielku15/BetterStartPage 49

A Visual Studio like start page which replaces the news section by a custom project dashboard.

Danielku15/java2haxe 25

A utility to convert Java source to Haxe source using a modified version of Sharpen

Danielku15/OpenApiQuery 23

OData based query language for your ASP.net core APIs

Danielku15/GhostAWT 12

Run Java Swing/AWT applications on headless environments

Danielku15/aspnet-url-versioning 3

Extends aspnet-api-versioning with URL focused versioning features

Danielku15/FhvRoomSearch 2

This application allows searching unoccupied rooms in the FHV.

Danielku15/aspnet-api-versioning 1

Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core.

Danielku15/haxeumlgen 1

Dynamically generates UML diagrams for haXe projects

Danielku15/heatmap.js 1

JavaScript Library for HTML5 canvas based heatmaps

Danielku15/hxWiki 1

haXe Wiki/Blog/Forum CMS, used by haxe.org

startedmicrosoft/reverse-proxy

started time in a day

issue commentmicrosoft/TypeScript

Compiled JavaScript import is missing file extension

I also just stumbled over this issue and as usual I find the justifications of "working as intended" as really questionable. There are various settings in the compiler which steer the module system. If I set "module": "commonjs" my typescript import statements are rewritten to require. There is also esModuleInterop which adds some extensions around the module imports.

While I agree that maybe the default behavior should be in the way that TypeScript leaves everything untouched, I also would say that it should/must be a TypeScript compiler setting to handle the mentioned use cases. I wanted to use TypeScript to create a small command line tool, which I can use in my GitHub Actions Workflow (without really making a reusable action) and it just does not work because the TypeScript output is not compatible with Node.js. Node.js seems to be usually a first class citizen in TS and here some very high level rules on the design goals (which IMO only partially apply here) prevent many people to use TS in such an obvious chain as running the compiled output in Node.js.

Maybe we have better chances with the Node.js guys to extend the module resolution algorithm.

jameshfisher

comment created time in 4 days

pull request commentprotocolbuffers/protobuf

Skip exports if not available by CommonJS

@lukesandberg @acozzette Any chance this will get reviewed and integrated in the near future. Otherwise I we will need likely to either patch locally the library or fully replace it with some other lib. 😢

Danielku15

comment created time in 12 days

issue openeddotnet/docs

Official Support Lifecycle of .net 4.8 for Server 2022 and Win11

Hello there.

I am always struggling a bit to aggregate all the dates and policies related to the .net 4.8 Framework support. I know that the .net Framework Support is coupled the policy of the parent OS. But this is where it gets a bit fuzzy regarding the lately released Server 2022 and announced Windows 11.

On this page, we see the policy definition that .net Framework 4.8 is following the parent OS policy. Windows Server 2022 and Windows 11 are not listed there. I am not sure if this really means Server 2022 does not have official support, or the docs were not updated.

Here we can read that .net Framework 4.8 will be distributed with future releases of Windows which is quite vague.

The version guide here also does not list yet which OSs are fully supported. Also the icon just indicates whether it can be installed, but might not give good indication about the support.

Hence I opened this issue in request in the hope that we can improve the dotnet docs page regarding the .net 4.8 support lifecycle. I am thinking of changing the icon legend to be more precise regarding the official support on the OS. Maybe icons in a hierarchy like: ✔️ Pre-Installed and officially Supported ➕ Not Pre-Installed but officially supported when installed ⚠️ Not Pre-Installed, Installation might work but not officially supported 🛑 Not Pre-installed and it is known that installation will not work.

Also beside that the OS names could link to the corresponding entry in the Microsoft Lifecycle Information.

Having this information is important for us to prioritize the porting of our applications to .net 5 (or higher)


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

created time in 19 days

push eventCoderLine/alphaTab

Danielku15

commit sha 917f90f21f287c29ae9379d6adf7ba3adb29df66

Activate bug form [skip ci]

view details

push time in a month

push eventCoderLine/alphaTab

Danielku15

commit sha f7baa4d0588ade28911b0d219c21297daa0c8be7

Activate bug form [skip ci]

view details

push time in a month

push eventCoderLine/alphaTab

Danielku15

commit sha 2b3739830d8b76c528d3f3ae8fda5cb5d8397779

Bug form test [skip ci]

view details

push time in a month

push eventCoderLine/alphaTab

Danielku15

commit sha e6affb8603ab15af789a8b5eb1deaac8f28b6f63

Try out issue forms

view details

push time in a month

issue commentCoderLine/alphaTab

Playback of the audioworklets version doesn't work in Safari 14.1

Found the issue and was able to fix it. Looks like Safari missed some parts when implementing AudioWorklets and I was able to work around it. Was quite nasty to find because they did not add any proper support for debugging or logging to Safari. All errors are swallowed and no custom logs are displayed. This made it really hard to find out why things are not working.

Reiji777

comment created time in a month

push eventCoderLine/alphaTab

Daniel Kuschny

commit sha 639c56f083ac39b8d3789995cac767e65fadb4b5

Fix audio worklets in safari (#652)

view details

push time in a month

delete branch CoderLine/alphaTab

delete branch : feature/safari-worklet

delete time in a month

PR merged CoderLine/alphaTab

Fix audio worklets in safari

Issues

Fixes #646

Proposed changes

Safari does not allow accessing the members of AudioWorkletGlobalScope through globalThis even though it provides it. It results in errors to do so. Therefore we need to ensure in alphaTab to not use globalThis to access the sampleRate and registerProcessor.

Using globalThis results in errors like:

TypeError: Can only call AudioWorkletGlobalScope.registerProcessor on instances of AudioWorkletGlobalScope

Checklist

  • [x] I consent that this change becomes part of alphaTab under it's current or any future open source license
  • [x] Changes are implemented
  • [x] Existing builds tests pass
  • [ ] New tests were added

Further details

  • [ ] This is a breaking change
  • [ ] This change will require update of the documentation/website
+23 -3

0 comment

1 changed file

Danielku15

pr closed time in a month

issue closedCoderLine/alphaTab

Playback of the audioworklets version doesn't work in Safari 14.1

<!-- ❗❗ The issue templates provided here are mandatory to be used and filled out ❗❗ Issues not filling out the provided structure and details will be closed -->

Expected Results

<!-- Explain here what is your expected behavior of alphaTab. --> Playback works for all devices

Observed Results

<!-- Explain here how alphaTab is behaving currently. --> As I am testing the latest audioworklets implementation, the playback function is not working in Safari 14.1 on iPhone or Mac. When clicking on the play button, the playback won't occur; instead it returns an error:

unhandled Promise Rejection: InvalidStateError: No ScriptProcessor was registered with this name

The error is pointing to alphaTab.js:26188, which is the following code in the AlphaSynthAudioWorkletOutput class

this._worklet = new AudioWorkletNode(ctx, 'alphatab');

On other devices I have tested so far (Android phone, Safari Preview 15.0 / Chrome on Mac), the playback works with no problem

Steps to Reproduce

<!-- Explain here the exact steps how to reproduce the problem. Try to provide a running sample showing the issue. If you have problem with a dedicated input file, please provide a download link or attach it to the issue. -->

Link to jsFiddle, CodePen, Project etc.: https://jsbin.com/budozuf/

  1. Open the link in Safari on iPhone or Mac
  2. Click on the play button

Further details

<!-- Provide any further valuable details here, feel free to leave this empty if you do not have more details or an idea how to solve it -->

Your environment

Version

  • [ ] 1.0
  • [ ] 1.1
  • [ ] 1.2
  • [x] 1.3-alpha.127 <!-- Add your exact version here -->

Flavor

  • [x] JavaScript
  • [ ] .net

System <!-- Any details about your test environment like Browser name and version, .net version, operating system etc. --> iPhone X (iOS 14.6); Safari 14.1.1 Macbook (Big Sur 11.4); Safari 14.1.1

closed time in a month

Reiji777

pull request commentCoderLine/alphaTab

Fix incorrect symbol for 256th note flag glyph

Ping @lukephills do you still plan to update the PR according to my request? otherwise I will need to close it.

lukephills

comment created time in a month

push eventCoderLine/alphaTab

Daniel Kuschny

commit sha 2a9da209ca5b598e52022f1c7106ee9cad542e6b

Fixed flickering of beat cursor in firefox (#651)

view details

push time in a month

delete branch CoderLine/alphaTab

delete branch : feature/ff-flickering

delete time in a month

PR merged CoderLine/alphaTab

Fixed flickering of beat cursor in firefox

Issues

Fixes #648

Proposed changes

Fixes a newly introduced issue where in FireFox the cursor was flickering back sometimes. This was due to some animation timing issue. One of the previously introduced optimizations does not play well with these animations so I had to remove it again.

Checklist

  • [x] I consent that this change becomes part of alphaTab under it's current or any future open source license
  • [x] Changes are implemented
  • [x] Existing builds tests pass
  • [ ] New tests were added

Further details

  • [ ] This is a breaking change
  • [ ] This change will require update of the documentation/website
+11 -93

0 comment

5 changed files

Danielku15

pr closed time in a month

PR opened CoderLine/alphaTab

Fix audio worklets in safari

Issues

Fixes #646

Proposed changes

Safari does not allow accessing the members of AudioWorkletGlobalScope through globalThis even though it provides it. It results in errors to do so. Therefore we need to ensure in alphaTab to not use globalThis to access the sampleRate and registerProcessor.

Using globalThis results in errors like:

TypeError: Can only call AudioWorkletGlobalScope.registerProcessor on instances of AudioWorkletGlobalScope

Checklist

  • [x] I consent that this change becomes part of alphaTab under it's current or any future open source license
  • [x] Changes are implemented
  • [x] Existing builds tests pass
  • [ ] New tests were added

Further details

  • [ ] This is a breaking change
  • [ ] This change will require update of the documentation/website
+23 -3

0 comment

1 changed file

pr created time in a month

create barnchCoderLine/alphaTab

branch : feature/safari-worklet

created branch time in a month

issue commentCoderLine/alphaTab

Last note of the tab is not properly played

I had a look at the provided links and for me it works fine. Unfortunately I cannot test audio on browserstack for mobile devices, they don't support it.

Can you test this on other devices? TBH: We know already that this phone is for some reason causing various issues with alphaTab. If it works for other devices I would like not to invest too much effort anymore into getting things running and performing well on this model/device.

Reiji777

comment created time in a month

push eventCoderLine/alphaTab

Danielku15

commit sha 5fdd03539c1bf209ecdc51017bc18e6e52638870

Code style

view details

push time in a month

PR opened CoderLine/alphaTab

Fixed flickering of beat cursor in firefox

Issues

Fixes #648

Proposed changes

Fixes a newly introduced issue where in FireFox the cursor was flickering back sometimes. This was due to some animation timing issue. One of the previously introduced optimizations does not play well with these animations so I had to remove it again.

Checklist

  • [x] I consent that this change becomes part of alphaTab under it's current or any future open source license
  • [x] Changes are implemented
  • [x] Existing builds tests pass
  • [ ] New tests were added

Further details

  • [ ] This is a breaking change
  • [ ] This change will require update of the documentation/website
+11 -92

0 comment

5 changed files

pr created time in a month

create barnchCoderLine/alphaTab

branch : feature/ff-flickering

created branch time in a month

startedcaos/zitadel

started time in a month

pull request commentCoreWCF/CoreWCF

Introduce new AsyncLock and use it to await channel open

@birojnayak Your client seems to be lacking a bit the insights and measurements that allow judging whether things are fine. I see it as quite some significant effort to still add the right metrics to do a before/after comparison. But you're concerns are legit and the current test suite does not give full indication about the impact of the change.

I am not sure if there are good test suites already available and the current suite was also suitable for releasing a 0.1 and 0.2 releases. https://github.com/CoreWCF/CoreWCF/pull/273 seems also a good start.

Danielku15

comment created time in a month

delete branch Danielku15/CoreWCF

delete branch : feature/duplex-channels

delete time in a month

Pull request review commentCoreWCF/CoreWCF

Introduce new AsyncLock and use it to await channel open

+// Licensed to the .NET Foundation under one or more agreements.+// The .NET Foundation licenses this file to you under the MIT license.++using System;+using System.Threading;+using System.Threading.Tasks;++namespace CoreWCF.Runtime+{+    /// <summary>+    /// This class provides a locking mechanism compatible with task async patterns.+    /// </summary>+    /// <remarks>+    /// Unlike the <see cref="ReentrantAsyncLock"/> it does not provide a reentrant (aka. recursive) locking+    /// and can therefore only be used in scenarios where we have clear control over the execution path.+    /// </remarks>+    internal sealed class NonReentrantAsyncLock+    {+        // based of the ideas in https://devblogs.microsoft.com/pfxteam/building-async-coordination-primitives-part-6-asynclock/+        private readonly SemaphoreSlim _semaphore = new SemaphoreSlim(1);+        private readonly Task<IDisposable> _releaser;+#if DEBUG+        private static readonly AsyncLocal<bool> s_reentranceFlag = new AsyncLocal<bool>();+#endif++        public NonReentrantAsyncLock()+        {+            _releaser = Task.FromResult<IDisposable>(new ReusableReleaser(this));+        }++        public Task<IDisposable> TakeLockAsync()+        {+#if DEBUG+            Fx.Assert(!s_reentranceFlag.Value, "Usage of lock is reentrant but this class does not support it!");+            s_reentranceFlag.Value = true;+#endif+            // we avoid allocation of new releaser instances if task does not need awaiting+            // SemaphoreSlim might return a completed task if no actual waiting needed to be done.+            var wait = _semaphore.WaitAsync();+            return wait.IsCompleted+                ? _releaser+                : wait.ContinueWith(+                    (_, state) => (IDisposable)new OneTimeReleaser((NonReentrantAsyncLock)state),+                    this,+                    CancellationToken.None,+                    TaskContinuationOptions.ExecuteSynchronously,+                    TaskScheduler.Default);+        }++        /// <summary>+        /// This releaser does a release on every dispose.+        /// </summary>+        private readonly struct ReusableReleaser : IDisposable

I am a bit unsure about which path is best to follow. The remark of @StevenBonePgh to avoid allocations somehow requires us to have a disposable which does a release every time because this instance is reused for multiple unlocks.

This opens again the path that some outside caller could also make a mistake and do too many releases which was raised as concern by @mconnew . The OneTimeReleaser would handle the single release for cases where we really did wait, but I guess it will not be used most of the time.

I think the mix we have right now is not good and we should clean this to one of the following options:

a) We keep the "ResusableReleaser" and use it everywhere. We neglect the risk that somebody misuses the lock, and by this gain the benefit that we can provide the same releaser instance in case no wait was done.

b) We keep the "OneTimeReleaser" and use it everywhere. We always create new releaser instances and by this remove the benefit of saving some struct allocations. By this we keep the benefit that we prevent wrong usage of the Releasers.

Danielku15

comment created time in a month

PullRequestReviewEvent

push eventDanielku15/CoreWCF

KUSCHNY Daniel

commit sha a291dfbded7940eeca66c38dee694eae49b00b2c

Adjust linked file path

view details

push time in a month

pull request commentCoreWCF/CoreWCF

Introduce new AsyncLock and use it to await channel open

Updates added:

  1. Lock classes were renamed and docs updated
  2. NonReentrantAsyncLock was optimized not to allocate any new tasks or releasers if no wait was done. (remark of @StevenBonePgh)
  3. NonReentrantAsyncLock was simplified to the actually needed cases to avoid handling all the complexity of cancellation token and timeout paths. Can be gratually added again once required.
  4. NonReentrantAsyncLock releaser was made secured against wrong usage scenarios (double release, concurrent releases).
Danielku15

comment created time in a month