floh96

floh96

Member Since 2 years ago

@Nix-wie-weg, Bavaria, Germany

Experience Points
1
follower
Lessons Completed
7
follow
Lessons Completed
42
stars
Best Reply Awards
19
repos

70 contributions in the last year

Pinned
⚡ The Microsoft community Windows Package Manager manifest repository
⚡ Download ScriptAnalyzer from PowerShellGallery
⚡ Windows Templates for Packer: Win10, Server 2016, 1709, 1803, 1809, 2019, 1903, 1909, 2004, Insider with Docker
⚡ Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale
⚡ Development repository for the apache2 cookbook
⚡ Prevent cloud misconfigurations during build-time for Terraform, Cloudformation, Kubernetes, Serverless framework and other infrastructure-as-code-languages with Checkov by Bridgecrew.
Activity
Jan
16
18 hours ago
started
started time in 4 hours ago
started
started time in 4 hours ago
Jan
15
1 day ago
pull request

floh96 pull request sitespeedio/sitespeed.io

floh96
floh96

Fix Gitlab link

Your checklist for a pull request to sitespeed.io

Please review the guidelines for contributing to this repository.

  • I'm making a big change or adding functionality so I've already opened an issue proposing the change to other contributors, so I got feedback on the idea before took the time to write precious code
  • Check that your change/fix has corresponding unit tests (if applicable)
  • Squash commits so it looks sane
  • Update the documentation https://github.com/sitespeedio/sitespeed.io/tree/main/docs in another PR
  • Verify that the test works by running npm test and test linting by npm run lint

Description

Fixes the link to gitlab.

Thank you for making sitespeed.io even better!

Activity icon
fork

floh96 forked sitespeedio/sitespeed.io

⚡ Sitespeed.io is an open source tool that helps you monitor, analyze and optimize your website speed and performance, based on performance best practices advices from the coach and collecting browser metrics using the Navigation Timing API, User Timings and Visual Metrics (FirstVisualChange, SpeedIndex & LastVisualChange).
floh96 MIT License Updated
fork time in 20 hours ago
Jan
14
2 days ago
Activity icon
issue

floh96 issue comment PowerShell/PowerShell

floh96
floh96

Add lock and null check to remoting internals (#16542)

PR Summary

Lock and null check of the PrioritySendDataCollection.cs members to avoid race condition.

PR Context

Copy-Item cmdlet can throw unhandled exception that terminates the process. The issue occures in WSManTransportManager internals. The PrioritySendDataCollection class is used by 2 threads: first thread calls ReadOrRegisterCallback method, that gets _dataToBeSent field, when second thread calls Clear method, where _dataToBeSent member is disposed.

PR Checklist

floh96
floh96

@PaulHigin this was merged without the cla signed

Jan
4
1 week ago
Activity icon
issue

floh96 issue comment microsoft/terminal

floh96
floh96

Updates to Terminal repo milestones, 2022 edition

The Terminal repo right now consists of a collection of various different "milestones" that have evolved organically over the years. We've got Console milestones, we've got Terminal milestones, we have milestones that vaguely align with OS releases, and then we've got like, four different milestones that are all the "backlog" in one way or another ("Console Backlog", "Terminal Backlog", "Windows vNext", and "Icebox"). All together, they don't create a very clear picture of what's going on in the Terminal land. To try and clear this up, we're going to de-duplicate some of these, and try something new for 2022.

  • The "Console Backlog" and the "Terminal Backlog" are both getting deprecated. They'll be collectively replaced with just a unified "Backlog" milestone, which will track things we'd like to get to, but we don't have any time planned for.
  • "Windows vNext" is also being deprecated. Originally, it was a rolling milestone to track things that should be in "the next version of Windows". Unfortunately, it wasn't tracked super well, so it's effectively become a second Console Backlog.
  • We're going to use four milestones for tracking bits of the next year of planning. These are separated into two "release" milestones, and two "semester" milestones.
    • "Terminal v1.{n}" (as of when this was written, this is v1.13): Shots we're calling for the upcoming release. Features & tasks we expect to land, blocking bugfixes, or other high-pri fixes
    • "Terminal v1.{n+1}" (currently, v1.14): Same as above, for the following release. With two 6-week release milestones, this is about 3 months of planning. This is a useful buffer for "we really should do this SOON, but not ASAP.
    • "22H1" will represent the first 6 months of 2022. This will help align internally with the OS release cadence.
      • If there are conhost bugs that need to get fixed in the upcoming release of Windows, then they go here.
      • Accessibility bugs will also go here, or into the current semester.
    • "22H2" is the same idea. A planning buffer for the second half of 2022. This includes Terminal features we expect to land in the second half.
      • Terminal P2+ bugs will go here.
  • Terminal v2, Console Backlog, Terminal Backlog, Windows vNext are all going to be emptied into "22H1", "22H2", and the "Backlog", based on current priority labels.
  • We're also going to rename "Terminal v3" to Up Next". This is for features, we think are highest on the backlog. The next big set of features we want to work on. Things that should be at the top of our list to fill up the upcoming semester.
  • We're leaving the ""Icebox" as-is right now, albeit, possibly workshopping the name in the near future. This will remain for features that we think are cool, valid feature requests for the Console&Terminal. However, we'll admit we're never going get to these features. We'd likely accept PRs from the community for things in here.
  • We had a really successful "Engineering Improvements" milestone over the last few weeks, so we'll probably try that again next year. At the end of each year, I'll just move the closed issues in the EIM milestone to a specific "Engineering Improvements {current_year}" milestone.

We're intentionally not planning out more specifically that 1.n and 1.n+1 - we're generally a fairly responsive team, where priorities can shift quickly during the course of the year. Trying to lick cookies for specific milestones more than 3 months out has generally been an exercise in futility.

As always, as priorities shift, and resourcing changes, issues can move between these milestones fluidly.

Hopefully, by grouping bugs into semester-sized milestones, we can address some of them in a timelier fashion. Currently, they just get stuck into "Terminal v2", which we've been pulling features and tasks into as well, which has only created a longer bug backlog 😄.

I'll be going through and moving our issues into this new structure likely sometime early in 2022.

If this doesn't end up working, we'll take our learnings and try something else for 2023 😄

Dec
28
2 weeks ago
Activity icon
delete

floh96 in floh96/winget-cli delete branch patch-1

deleted time in 2 weeks ago
Dec
27
2 weeks ago
pull request

floh96 pull request microsoft/winget-cli

floh96
floh96

Fix Typo in upgrade.md


Activity icon
fork

floh96 forked microsoft/winget-cli

⚡ Windows Package Manager CLI (aka winget)
floh96 MIT License Updated
fork time in 2 weeks ago
Dec
22
3 weeks ago
Activity icon
issue

floh96 issue tarecord/sign-in-with-google

floh96
floh96

release request

@tarecord could you publish a new release with #73 included? thanks

Dec
21
3 weeks ago
started
started time in 3 weeks ago
Dec
20
3 weeks ago
Activity icon
issue

floh96 issue comment microsoft/terminal

floh96
floh96

After upgrade to 1.12.3472.0 startingDirectory with forward slashes does not work for WSL any more

Windows Terminal version

1.12.3472.0

Windows build number

10.0.19043.0

Other Software

I have both WSL2 and WSL1 with Ubuntu 20.04 images. For both of them after Windows Terminal upgraded form 1.11 preview to 1.12 preview my session starts in the Ubuntu's root directory instead of the directory set in the Terminal's profile:

            {
                "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
                "hidden": false,
                "name": "Ubuntu",
                "source": "Windows.Terminal.Wsl",
                "startingDirectory": "//wsl$/Ubuntu/home/vbrozik/"
            },
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl",
                "startingDirectory": "//wsl$/Ubuntu-20.04/home/vbrozik/"
            },

The directories exist:

PS C:\Users\vaclav.brozik> cd //wsl$/Ubuntu/home/vbrozik/
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Ubuntu\home\vbrozik> cd //wsl$/Ubuntu-20.04/home/vbrozik/
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Ubuntu-20.04\home\vbrozik>

The same bug is in the wsl utility itself as I noticed that the --cd switch fails to process the path with forward slashes while backslashes work fine:

PS C:\Users\vaclav.brozik> wsl --cd //wsl$/Ubuntu/home/vbrozik/
[email protected]:/$ pwd
/
[email protected]:/$ logout
PS C:\Users\vaclav.brozik> wsl --cd \\wsl$\Ubuntu\home\vbrozik\
[email protected]:~$ pwd
/home/vbrozik

So if Windows Terminal uses this buggy functionality of the wsl tool the bug propagates to Windows Terminal.

Workaround

After I replaced the slashes with backslashes everything works as expected:

            {
                "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
                "hidden": false,
                "name": "Ubuntu",
                "source": "Windows.Terminal.Wsl",
                "startingDirectory": "\\\\wsl$\\Ubuntu\\home\\vbrozik\\"
            },
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl",
                "startingDirectory": "\\\\wsl$\\Ubuntu-20.04\\home\\vbrozik\\"
            },

Steps to reproduce

Use forward slashes in the startingDirectory property of a WSL profile in Windows Terminal - for example //wsl$/Ubuntu/home/username/.

Expected Behavior

The interactive shell running in WSL should have the working directory as configured in the startingDirectory property.

Actual Behavior

The interactive shell running in WSL has the root directory as the working directory.

Dec
17
4 weeks ago
Activity icon
fork

floh96 forked chocolatey/boxstarter

⚡ Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages
floh96 Apache License 2.0 Updated
fork time in 4 weeks ago
Dec
15
1 month ago
Activity icon
issue

floh96 issue comment MicrosoftDocs/terminal

floh96
floh96

Adding oh-my-posh to new-tab-same-directory.md

floh96
floh96

@xuwaters you don't need to change your profile like that with oh-my-posh. oh-my-posh supports emitting OSC9;9; it is just disabled by default because it is triggering a notification in iterm2.... you can enable it in your prompt settings see https://ohmyposh.dev/docs/config-overview#general-settings

Activity icon
issue

floh96 issue MicrosoftDocs/terminal

floh96
floh96

Gifs are not rendered

The gifs at the bottom are not rendered


Document Details

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

Dec
10
1 month ago
Activity icon
issue

floh96 issue dfinke/Tiny-PowerShell-Projects

floh96
floh96

Dockerfile broken

The following command in the Dockerfile is failing https://github.com/dfinke/Tiny-PowerShell-Projects/blob/master/Dockerfile#L64 Log from Binder:

Step 19/24 : RUN dotnet tool install -g Microsoft.dotnet-interactive --version 1.0.140401 --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json"
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
 ---> Running in cddd4eabb666
/usr/share/dotnet/sdk/3.1.301/NuGet.targets(128,5): error : Unable to load the service index for source https://dotnet.myget.org/F/dotnet-try/api/v3/index.json. [/tmp/g1pulogo.tty/restore.csproj]
/usr/share/dotnet/sdk/3.1.301/NuGet.targets(128,5): error :   The SSL connection could not be established, see inner exception. [/tmp/g1pulogo.tty/restore.csproj]
/usr/share/dotnet/sdk/3.1.301/NuGet.targets(128,5): error :   The remote certificate is invalid according to the validation procedure. [/tmp/g1pulogo.tty/restore.csproj]
The tool package could not be restored.
Tool 'microsoft.dotnet-interactive' failed to install. This failure may have been caused by:

* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET Core tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.

For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
Removing intermediate container cddd4eabb666
The command '/bin/bash -o pipefail -c dotnet tool install -g Microsoft.dotnet-interactive --version 1.0.140401 --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json"' returned a non-zero code: 1Built image, launching...
Failed to connect to event stream
Dec
7
1 month ago
Activity icon
issue

floh96 issue d4rken/sdmaid-public

floh96
floh96

Unable to open settings

Describe the bug Unable to open settings

To Reproduce See screen recording

https://user-images.githubusercontent.com/49693964/145032946-5205a0e8-ea71-446c-82e7-e1592f275633.mp4

Expected behavior settings open

Debug log

sdmaid_logfile_1638881102322.txt.zip

Smartphone (please complete the following information):

  • Device: Pixel 5
  • OS: Android 12
Activity icon
issue

floh96 issue comment d4rken/sdmaid-public

floh96
floh96

Unable to open settings

Describe the bug Unable to open settings

To Reproduce See screen recording

https://user-images.githubusercontent.com/49693964/145032946-5205a0e8-ea71-446c-82e7-e1592f275633.mp4

Expected behavior settings open

Debug log

sdmaid_logfile_1638881102322.txt.zip

Smartphone (please complete the following information):

  • Device: Pixel 5
  • OS: Android 12
floh96
floh96

i cleared the cache of the app and got prompted again to grant the accessibility rights and now it's working... :facepalm: sry for the noise

Activity icon
issue

floh96 issue d4rken/sdmaid-public

floh96
floh96

Unable to open settings

Describe the bug Unable to open settings

To Reproduce See screen recording

https://user-images.githubusercontent.com/49693964/145032946-5205a0e8-ea71-446c-82e7-e1592f275633.mp4

Expected behavior settings open

Debug log

sdmaid_logfile_1638881102322.txt.zip

Smartphone (please complete the following information):

  • Device: Pixel 5
  • OS: Android 12
Dec
6
1 month ago
push

floh96 push floh96/terraform-provider-gitlab

floh96
floh96
floh96
floh96

Merge pull request #601 from floh96/patch-1

Fix links in CHANGELOG.md

floh96
floh96

Fix documentation to show up on terraform registry

floh96
floh96

update reference to master branch to main

Tested to confirm that it does create a main branch by default

floh96
floh96

Add support for importing Pipeline Schedules and Triggers

floh96
floh96

Also wait for import_status when a project template is configured

Signed-off-by: Sune Keller [email protected]

floh96
floh96

Merge pull request #612 from dan-hill2802/patch-1

update reference to master branch to main

floh96
floh96

Merge pull request #621 from sirlatrom/fix-620

gitlab_project: Wait for template projects to be cloned/imported

floh96
floh96

Merge pull request #618 from pdecat/support_pipeline_schedule_import

Add support for importing Pipeline Schedules and Triggers

floh96
floh96

Update dependencies

Signed-off-by: Julien Pivotto [email protected]

floh96
floh96

Merge pull request #633 from roidelapluie/update-deps

Update dependencies

floh96
floh96

Merge pull request #602 from thuck/master

Missing documentation for gitlab_instance_variable

floh96
floh96

Add most Premium features for gitlab_branch_protection (#556)

  • Rebase and update go.mod

Signed-off-by: Sune Keller [email protected]

  • Add most Premium features for gitlab_branch_protection

Signed-off-by: Sune Keller [email protected]

  • Re-work modified schema for gitlab_branch_protection, and update docs

Signed-off-by: Sune Keller [email protected]

  • Accommodate to name changes from library maintainer

Signed-off-by: Sune Keller [email protected]

  • Remove invalid check for CE

Signed-off-by: Sune Keller [email protected]

  • Revert back how merge_access_level and push_access_level are created

Signed-off-by: Sune Keller [email protected]

  • Simplify expansion of arguments

Signed-off-by: Sune Keller [email protected]

  • Remove several obsolete functions and make acceptance tests independent of implementation functions

Signed-off-by: Sune Keller [email protected]

floh96
floh96

fix: update default_branch to "main" for gitlab_project tests

floh96
floh96

Merge pull request #643 from gitlabhq/mattkasa-fix-default-branch-name

fix: update default branch name to "main"

floh96
floh96

chore: add error handling to resourceGitlabProjectSetToState

floh96
floh96

Merge pull request #649 from gitlabhq/mattkasa-handle-errors-in-project-set-to-state

chore: add error handling to resourceGitlabProjectSetToState

floh96
floh96

Documentation improvements (#642)

  • Documentation improvements

  • More Markdown lint fixes

  • Add golangci-lint to the pipeline

Fixes #361

floh96
floh96

Add protected_branch_ids to gitlab_project_approval_rule (#542)

Signed-off-by: Sune Keller [email protected]

floh96
floh96

chore: remove incomplete gitlab_project_repository_file resource (#650)

This file was part of #556 but did not include a test, docs, or an entry in gitlab/provider.go, so we are removing it until it can be completed.

commit sha: 76764869680cb8dc31899333ecec8003f6727b8a

push time in 1 month ago
Dec
3
1 month ago
Activity icon
issue

floh96 issue comment chef/chef

floh96
floh96

Unable to install gem using the chef-infra-client v17.6.18

Unable to install gem using the chef-infra-client v17.6.18

I am trying to install this gem below with the latest version of chef-client v17.6.18 using the below code block in my recipe. But getting error while installing the gem. Since my VM doesn't have internet connection, I have to update my gem source to my local repo in artifactory instead of the default rubygems URL (https://rubygems.org). But while deployment it is still trying to look in the rubygems URL which it shouldn't. Infact older version of chef-client (v15.13.8) did work fine i.e., it installs the gem from my artifactory repo.

I tried to use clear_sources true and source https://local-artifactory-gem-repo as well with chef_gem resource. But still the same error. This time I could see the artifactory-local-gem-repo as my source repo.

chef_gem 'tiny_tds' do
  action :install
end

Software Version

chef-infra-client v17.6.18 OS Win2019

Stacktrace

[2021-10-07T13:09:37-04:00] FATAL: Stacktrace dumped to C:/chef/cache/chef-stacktrace.out
[2021-10-07T13:09:37-04:00] FATAL: ---------------------------------------------------------------------------------------
[2021-10-07T13:09:37-04:00] FATAL: PLEASE PROVIDE THE CONTENTS OF THE stacktrace.out FILE (above) IF YOU FILE A BUG REPORT
[2021-10-07T13:09:37-04:00] FATAL: ---------------------------------------------------------------------------------------
[2021-10-07T13:09:37-04:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: chef_gem[tiny_tds] (COOKBOOK_NAME::RECIPE_NAME line 16) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of C:/opscode/chef/embedded/bin/gem install tiny_tds -q --no-document -v "2.1.5" --source=https://rubygems.org ----
STDOUT: Building native extensions. This could take a while...
STDERR: ERROR:  Error installing tiny_tds:
        ERROR: Failed to build gem native extension.

    current directory: C:/opscode/chef/embedded/lib/ruby/gems/3.0.0/gems/tiny_tds-2.1.5/ext/tiny_tds
C:/opscode/chef/embedded/bin/ruby.exe -I C:/opscode/chef/embedded/lib/ruby/3.0.0 -r ./siteconf20211007-356-j4rum4.rb extconf.rb
looking for freetds headers in the following directories:
 - /opt/local/include
 - /opt/local/include/freetds
 - /usr/local/include
 - /usr/local/include/freetds
looking for freetds library in the following directories:
 - /opt/local/lib
 - /opt/local/lib/freetds
 - /usr/local/lib
 - /usr/local/lib/freetds
checking for sybfront.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=C:/opscode/chef/embedded/bin/$(RUBY_BASE_NAME)
        --help
        --with-freetds-dir
        --without-freetds-dir
        --with-freetds-include
        --without-freetds-include=${freetds-dir}/include
        --with-freetds-lib
        --without-freetds-lib=${freetds-dir}/lib
C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:482:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:624:in `try_cpp'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:1188:in `block in find_header'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:982:in `block in checking_for'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:361:in `block (2 levels) in postpone'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:331:in `open'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:361:in `block in postpone'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:331:in `open'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:357:in `postpone'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:981:in `checking_for'
        from C:/opscode/chef/embedded/lib/ruby/3.0.0/mkmf.rb:1187:in `find_header'
        from extconf.rb:59:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  C:/opscode/chef/embedded/lib/ruby/gems/3.0.0/extensions/x64-mingw32/3.0.0/tiny_tds-2.1.5/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in C:/opscode/chef/embedded/lib/ruby/gems/3.0.0/gems/tiny_tds-2.1.5 for inspection.
Results logged to C:/opscode/chef/embedded/lib/ruby/gems/3.0.0/extensions/x64-mingw32/3.0.0/tiny_tds-2.1.5/gem_make.out
---- End output of C:/opscode/chef/embedded/bin/gem install tiny_tds -q --no-document -v "2.1.5" --source=https://rubygems.org ----
Ran C:/opscode/chef/embedded/bin/gem install tiny_tds -q --no-document -v "2.1.5" --source=https://rubygems.org returned 1

floh96
floh96

@marcparadise @lamont-granquist I'm also having this problem with chef 17 when I'm trying to install airbrake-ruby. I tested chef version 16.17.18 and there it is working. I get the following error in the mkmf.log in chef 17:

"gcc -o conftest.exe -IC:/opscode/chef/embedded/include/ruby-3.0.0/x64-mingw32 -IC:/opscode/chef/embedded/include/ruby-3.0.0/ruby/backward -IC:/opscode/chef/embedded/include/ruby-3.0.0 -I. -IC:/opscode/chef/embedded/include -DFD_SETSIZE=2048 -m64 -march=x86-64 -O3 -D_WIN32_WINNT=0x0602 -D__MINGW_USE_VC2005_COMPAT -D_FILE_OFFSET_BITS=64  -IC:/opscode/chef/embedded/include -DFD_SETSIZE=2048 -march=x86-64 -O3 conftest.c  -L. -LC:/opscode/chef/embedded/lib -L. -LC:/opscode/chef/embedded/lib -fno-lto  -m64   -lx64-msvcrt-ruby300  -lshell32 -lws2_32 -liphlpapi -limagehlp -lshlwapi  "
In file included from C:/opscode/chef/embedded/include/ruby-3.0.0/ruby/missing.h:38:0,
                 from C:/opscode/chef/embedded/include/ruby-3.0.0/ruby/defines.h:80,
                 from C:/opscode/chef/embedded/include/ruby-3.0.0/ruby/ruby.h:23,
                 from C:/opscode/chef/embedded/include/ruby-3.0.0/ruby.h:38,
                 from conftest.c:1:
c:\opscode\chef\embedded\mingw\bin\../lib/gcc/x86_64-w64-mingw32/4.7.2/../../../../x86_64-w64-mingw32/include/ieeefp.h:6:22: fatal error: ansidecl.h: No such file or directory
compilation terminated.
checked program was:
/* begin */
1: #include "ruby.h"
2: 
3: #include <winsock2.h>
4: #include <windows.h>
5: int main(int argc, char **argv)
6: {
7:   return !!argv[argc];
8: }
/* end */

i checked the c:\opscode\chef\embedded\mingw\bin\../lib/gcc/x86_64-w64-mingw32/4.7.2/../../../../x86_64-w64-mingw32/include/ path in the explorer and the ansidecl.h file is missing which is causing the error

push

floh96 push floh96/airbrake-ruby

floh96
floh96

Problematische Gem Dependency entfernt

commit sha: 6aba69c792e95aff380d893e74fde8a5af26ec2e

push time in 1 month ago
Activity icon
fork

floh96 forked airbrake/airbrake-ruby

⚡ A plain Ruby Airbrake notifier
floh96 MIT License Updated
fork time in 1 month ago
Dec
2
1 month ago
started
started time in 1 month ago
Activity icon
issue

floh96 issue comment microsoft/winget-cli

floh96
floh96

PowerShell cmdlets


#674

Microsoft Reviewers: Open in CodeFlow
floh96
floh96

@denelon why did you not merge the spec pr?

Nov
30
1 month ago
Activity icon
issue

floh96 issue comment PowerShell/openssh-portable

floh96
floh96

Initial MSI authoring for Previews

floh96
floh96

@heaths could you rebase and resolve the merge conflict please? Because of the merge conflict the ci build did not start.

Nov
28
1 month ago
Activity icon
issue

floh96 issue comment PowerShell/openssh-portable

floh96
floh96

Agent Forwarding Windows client to Windows host not working?

Is agent forwarding supported when connecting from a windows client to a windows host machine ?

I tried all of the things below, but had no luck and stumbled across this comment https://github.com/PowerShell/Win32-OpenSSH/issues/1136#issuecomment-500549297 which says Agent forwarding is not supported on the server yet, but you should be able to use the client to forward agent to a non-Windows target.

Was following these instructions from github : https://docs.github.com/en/developers/overview/using-ssh-agent-forwarding

  1. used keygen to generate public/private keys and added public to github.com
  2. ssh-add "location of private key". Can see them on client machine through ssh-add -l
  3. Test using agent
PS C:\Users\monil> ssh -T [email protected]
Hi monil-patel! You've successfully authenticated, but GitHub does not provide shell access.
  1. Specified ForwardAgent in the ssh config
Host my-pc
  HostName host...
  User username
  IdentityFile C:\Users\user\.ssh\id_rsa
  ForwardAgent yes

  1. ssh to my-pc, and run ssh -T [email protected] again

expected

# ssh session
PS C:\Users\monil> ssh -T [email protected]
Hi monil-patel! You've successfully authenticated, but GitHub does not provide shell access.

received

# ssh session
[email protected]: Permission denied (publickey).

Cant list any keys under the ssh session

# ssh session
C:\Users\monil>ssh-add -l
Error connecting to agent: No such file or directory
floh96
floh96
Previous