'Use parent process directory' not being respected for new Tabs

Windows Terminal version
1.16.10262.0
Windows build number
10.0.2621.1105
Other Software
No response
Steps to reproduce
I have my WT setup so my default profile is lauch as admin and with the 'Use parent process directory' checked for starting directory. I then have all my other profiles set to 'Use parent process directory' for starting directory as well.

Use the context menu to launch Windows Terminal from a folder.
WT will launch default profile in the directory of the folder it was launch
Opening a new Tab launches the new profile to the 'C:\Windows\System32' folder

Expected Behavior
Each new tab opened with different profiles should open in the same directory that WT was launched from
Actual Behavior
Each new tab is launch to the 'C:\Windows\System32' folder.

Huh. I guess that makes sense, we're probably not passing the initial CWD of the Terminal to the elevate-shim to forward that to the elevated terminal instance.
Probably wouldn't be terribly difficult to pass the original terminal's CWD to elevate-shim. I'd look at TerminalPage::_maybeElevate - that's where the handoff from an unelevated -> elevated process happens.

There's maybe an equal and opposite here - maybe the Terminal should have it's CWD set to system32 when it's run elevated. That seems like pseudo-security, but there's some precedent here discussed in #7062.
I don't think that's incompatible with #7062. I just wonder if there's perhaps a reason why it shouldn't be automatic. Is there a vector for malicious.exe to get elevated when the CWD is set to something other than system32, that it wouldn't otherwise be able to do just by inserting itself into the profile? I doubt it, but I'm no security expert.

Hmmmmmm.
This almost looks like a dupe of #15173, but subtly different.
With #15173, it's sufficient to just pass -d <path> to elevate-shim, to open the new tab in the requested directory.
This however, requests that elevate-shim somehow communicates that the Terminal itself should set it's CWD. In this case, the auto-self-elevate case, we need to pass the current virtual directory of the terminal to the elevate shim, to pass to the new one. Ew. Almost like #4637
I dunno if this regressed in 1.16 or was always broken.

This did work in previous versions. It broke with the latest. Been tough dealing with it not working. Was just so used to the workflow being able to switch to different consoles for the same directory.

I am also experiencing this bug on Windows 11 version 10.0.22621.1702. I believe this still works on my other PC which probably uses an older version. Will verify soon.

FWIW I'm pretty confident this isn't a OS version issue, this is a Terminal version issue. Terminal 1.16 includes the change that regressed this, regardless of OS version


flutter run -d macos error: Oops; flutter has exited unexpectedly: "Null check operator used on a null value".

Steps to reproduce
 flutter run -d macos

Expected results
Trying to run my app on macos for first time, I expect I'll need to edit some plugins without macos support, however I'm running into this error which does not seem related to my code.
Actual results
error: Oops; flutter has exited unexpectedly: "Null check operator used on a null value".
A crash report has been written to /Users/myname/Work/myproject/flutter_03.log
Failed to package /Users/myname/Work/myproject.

flutter_03.log
Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.

## command

flutter assemble --no-version-check --output=/Users/myname/Work/myproject/build/macos/Build/Products/Debug/ -dTargetPlatform=ios -dTargetFile=/Users/myname/Work/myproject/lib/main_.dart -dBuildMode=debug -dFlavor= -dIosArchs=x86_64 -dSdkRoot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk -dSplitDebugInfo= -dTreeShakeIcons=false -dTrackWidgetCreation=true -dDartObfuscation=false -dAction=build -dFrontendServerStarterPath= --ExtraGenSnapshotOptions= --DartDefines=<removed, let me know if needed>==,<removed, let me know if needed==,<removed, let me know if needed>= --ExtraFrontEndOptions= -dCodesignIdentity=<removed, let me know if needed> debug_ios_bundle_flutter_assets

## exception

_TypeError: Null check operator used on a null value

#0      NativeAssets._buildIOS (package:flutter_tools/src/build_system/targets/native_assets.dart:290:68)
#1      NativeAssets.build (package:flutter_tools/src/build_system/targets/native_assets.dart:85:32)
<asynchronous suspension>
#2      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:861:9)
<asynchronous suspension>
#3      Future.wait.<anonymous closure> (dart:async/future.dart:518:21)
<asynchronous suspension>
#4      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:799:32)
<asynchronous suspension>
#5      Future.wait.<anonymous closure> (dart:async/future.dart:518:21)
<asynchronous suspension>
#6      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:799:32)
<asynchronous suspension>
#7      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:628:16)
<asynchronous suspension>
#8      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:318:32)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1389:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#17     main (package:flutter_tools/executable.dart:90:3)
<asynchronous suspension>

## flutter doctor

[✓] Flutter (Channel stable, 3.19.1, on macOS 14.2.1 23C71 darwin-x64, locale en-US)
    • Flutter version 3.19.1 on channel stable at /Users/myname/Work/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision abb292a07e (3 days ago), 2024-02-20 14:35:05 -0800
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/myname/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.86.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.82.0

[✓] Connected device (3 available)
    • My iPhone (mobile) • <XXX> • ios            • iOS 17.2.1 21C66
    • macOS (desktop)       • macos                     • darwin-x64     • macOS 14.2.1 23C71 darwin-x64
    • Chrome (web)          • chrome                    • web-javascript • Google Chrome 122.0.6261.69

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Code sample
Code sample
It's my full flutter project at the moment, trying to run on macos for first time, sorry cannot share particular code related to this issue.

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.1, on macOS 14.2.1 23C71 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.2)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Thanks for filing this @kenle.
I tried reproducing this with a new flutter project but can't seem to reproduce it.
I see you are currently getting this error with an existing project. Can you try running this on a new project to verify this issue still persists with a new project?
This might be similar/related to https://github.com/flutter/flutter/issues/136754 from the logs as well.

Have Same Problem But in A 7 month old project

Thanks for filing this @kenle. I tried reproducing this with a new flutter project but can't seem to reproduce it. I see you are currently getting this error with an existing project. Can you try running this on a new project to verify this issue still persists with a new project? This might be similar/related to #136754 from the logs as well.

Thanks for your reply @dam-ease
Yes, with a new Flutter project I do not have this issue.
The Flutter project I'm having an issue with has been maintained for 3 years, I've finally decided to migrate to Dart 3 and the latest Flutter.  I was able to migrate successfully and everything is running fine on iOS and Android.  MacOS has the issue as described.
The error seems related to the "flutter_tools" package, which when I lookup is not Dart 3 compatible?  This flutter_tools package is being referenced in the Podfile of the new Flutter project created with the latest version of Flutter, and my old Flutter project.  Ironically when I look up this package it says it is not Dart 3 compatible. https://pub.dev/packages/flutter_tools/versions I'm not sure if this has any relation to this issue.
Here is the Podfile from my old project in case it has any relation to this error:
platform :osx, '10.15'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'ephemeral', 'Flutter-Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure \"flutter pub get\" is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Flutter-Generated.xcconfig, then run \"flutter pub get\""
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_macos_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_macos_pods File.dirname(File.realpath(__FILE__))
  #target 'RunnerTests' do
  #  inherit! :search_paths
  #end
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_macos_build_settings(target)
    target.build_configurations.each do |config|
      # Here are some configurations automatically generated by flutter
      # You can enable the permissions needed here. For example to enable camera
      # permission, just remove the `#` character in front so it looks like this:
      #
      # ## dart: PermissionGroup.camera
      # 'PERMISSION_CAMERA=1'
      #
      #  Preprocessor definitions can be found in: https://github.com/Baseflow/flutter-permission-handler/blob/master/permission_handler/ios/Classes/PermissionHandlerEnums.h
      config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
        '$(inherited)',

        ## dart: PermissionGroup.calendar
        # 'PERMISSION_EVENTS=1',

        ## dart: PermissionGroup.reminders
        # 'PERMISSION_REMINDERS=1',

        ## dart: PermissionGroup.contacts
        # 'PERMISSION_CONTACTS=1',

        ## dart: PermissionGroup.camera
        'PERMISSION_CAMERA=1',

        ## dart: PermissionGroup.microphone
        'PERMISSION_MICROPHONE=1',

        ## dart: PermissionGroup.speech
        # 'PERMISSION_SPEECH_RECOGNIZER=1',

        ## dart: PermissionGroup.photos
        'PERMISSION_PHOTOS=1',

        ## dart: [PermissionGroup.location, PermissionGroup.locationAlways, PermissionGroup.locationWhenInUse]
        'PERMISSION_LOCATION=1',

        ## dart: PermissionGroup.notification
        # 'PERMISSION_NOTIFICATIONS=1',

        ## dart: PermissionGroup.mediaLibrary
        # 'PERMISSION_MEDIA_LIBRARY=1',

        ## dart: PermissionGroup.sensors
        # 'PERMISSION_SENSORS=1',

        ## dart: PermissionGroup.bluetooth
        'PERMISSION_BLUETOOTH=1',

        ## dart: PermissionGroup.appTrackingTransparency
        # 'PERMISSION_APP_TRACKING_TRANSPARENCY=1',

        ## dart: PermissionGroup.criticalAlerts
        # 'PERMISSION_CRITICAL_ALERTS=1'
      ]

    end

  end
end

I will also look at the #136754 that you mentioned, thank you.

Thanks for your response @kenle
The flutter_tools package isn’t a flutter package. Can you take out the package to see if the issue still persists?
Also, seeing that it exists only on your existing project, this might not be an issue with flutter itself.

Hi @dam-ease
The "flutter_tools" package seems to be referenced in Podfile for new projects created with recent Flutter as well.  For example, with Flutter version 3.19.1 if I do
flutter create -a java -i swift test_app

Then inside of pubspec.yaml if I add a package, for example:
dependencies:
  flutter:
    sdk: flutter
  camerawesome: ^2.0.1

Then I run on macos
flutter run -d macos

It will automatically create a Podfile that references flutter_tools and looks like:
platform :osx, '10.14'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'ephemeral', 'Flutter-Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure \"flutter pub get\" is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Flutter-Generated.xcconfig, then run \"flutter pub get\""
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_macos_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_macos_pods File.dirname(File.realpath(__FILE__))
  target 'RunnerTests' do
    inherit! :search_paths
  end
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_macos_build_settings(target)
  end
end

With the Podfile in the new project it runs fine even though it references "flutter_tools".
There seems to be some other dependencies causing some issues, I can't wrap my head around it yet.

Thanks for your response @kenle
Seeing that this doesn’t occur with new projects, this could be with some packages in your existing project.
Can you check in with the third party packages in your project??


Fix rubocop offenses

Use named references in printf.
Set LineLength to 80 in rubocop config to match project convention and prevent IfUnlessModifier offenses.
Specify required_ruby_version >= 2.4 in gemspec

Thanks for fixing CI!


Issues with python syntax in main.py on line 31, 79, 88, 157

It seems that there is something wrong with the syntax in the following lines.
031: def get_message(self, message_id) -> Message:
079: def new_email(self, body='', subject='', to: List[Contact] = list):
088: def send_email(self, body=None, subject=None, to: List[Contact] = list, cc=None, bcc=None, send_as=None, attachments=None):
157: def _get_messages_from_folder_name(self, folder_name: str):

Are you on Python 3?

Ahh. Im sorry about that. Just remove my issue :)

You're not the first to bring up something related to Python 2, I opened an issue in the GitLab repo about supporting Python 2 in the next release :)

Python 2 support added - https://pypi.org/project/pyOutlook/4.1.0.dev1/

Ah  cool! Thanks!


Realtime delete events are not sent

delete event created after OnRecordAfterDeleteRequest in apis/realtime.go is not sent.
I tried to track down where the problem is:
apis/realtime.go#L265
	foundRecord, err := api.app.Dao().FindRecordById(record.Collection(), record.Id, ruleFunc)
	if err == nil && foundRecord != nil {
		return true
	}

	return false

Before the event is sent to a client, canAccessRecord checks whether the record exists in the database and if it can be accessed according to rules. It always returns false and the event is not sent because the record is already deleted.

Since this may be a blocker for someone, I've released a hotfix for this in v0.2.7 release.
I'll revisit the realtime integration tests this weekend.


Remove textContentType annotations (Addresses #3159)

Description
This PR reverts https://github.com/corona-warn-app/cwa-app-ios/commit/427c7b205cd4a61cd473904d3b1353128643686a, because it doesn't work anymore.
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-8484
Screenshots
n/a
More information can be found in #3159. I know this is not the perfect solution, it would be better if the textContentType fields would work. But for the user this is the best solution (that I can contribute).

Closing in favor of #3285.


new STT citrinet server

https://citrinetstt.ziggyai.online/status should be added
this replaces neon nemo stt plugin, it uses it internally, but replaces default models (catalan only currently)

Done


Update and add a test to make sure after submission a respondent is redirect to thank you

What is the context of this PR?
When we stopped deleting QuestionnaireState, we created an issue when a survey was submitted, it could be submitted again, if by the same respondent or another. Work on other stories has corrected the issue, however we still had a test mark as failing that needed updating and could do with another test adding
How to review
Make sure the tests make sense. You can also test the behaviour by taking note of the Response ID on launcher, completing and submitting, then launching again with the same Response ID. It should take you to thank you page the 2nd time.
For multiple users I used 2 different browsers. I took note of the Response ID, launched the questionnaire in one browser and answered the first question, I then launched the same questionnaire with the same Response ID in a different browser and completed the questionnaire and submitted. At this point I reverted back to the first browser and tried to submit, it should take you to the thank you page
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

While we are here, we should also look to refactor the get_questionnaire_store method as per https://github.com/ONSdigital/eq-questionnaire-runner/pull/639#discussion_r690497241


"Sun and Environment Settings" Popup no longer receives Key Input Events

Godot version
v4.0.alpha.custom_build [74ff5921d]
System information
Linux, Debain 11, Xfce, Nvidia, Vulkan
Issue description
The "Sun and Environment Settings" Popup no longer receives key input events. It is no longer possible to change parameters by keyboard.
Bisecting this issue shows that it was introduced in #58490
Fixing this issue by making the popup focused, will likely hide the issue, that causes #59722 or maybe it is the same.
https://user-images.githubusercontent.com/6299227/161280206-249e19f9-4b9e-43a4-b7b3-62ee38eaaec4.mp4
Steps to reproduce

Open Editor
Create Node3D
Open Sun and Environment Settings
Select Sky Energy entryfield
Push number-buttons on keyboard

Minimal reproduction project
Editor issue

cc @bruvzg


fix: cli test build

Problem
cli test build fail on install

Codecov Report

Merging #1021 (60f8793) into main (1fbf44d) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #1021   +/-   ##
=======================================
  Coverage   93.71%   93.71%
=======================================
  Files         122      122
  Lines        5428     5428
  Branches     1620     1620
=======================================
  Hits         5087     5087
  Misses        323      323
  Partials       18       18

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1fbf44d...60f8793. Read the comment docs.


Recorder: Add support for PV

Allows capture of both PV / RM streams from the Recorder app, by creating 2 distinct frame source groups / sensor frame recorders (one for PV, one for RM).
A Boolean (_isPV) checks if the FrameRecorder instance is used for RM or PV streams. This is then used to save data in 2 distinct archives and avoid overwriting between streams. At the end of the recording, the app saves 2 archives with 2 different file names (one with suffix "0" for RM recorded data, one with suffix "1" for PV recorded data).
It is possible to choose which streams to capture by modifying the enabledSensorTypes vector and the enablePV bool in Recorder/AppMain.h.
There are inconsistencies in recording when the app is launched for the first time on the device -- since the airtap given to enable access to the camera is detected also to start capture. The problem seems to affects also the Recorder app prior to this PR.

The features in this pull request are integrated into another pull request, which makes this one obsolete. The master branch should contain all the changes from here.


Markers arrow are not working on v10

Describe the Bug
Arrows are not working, getMarkerEnd works but arrows are not showed.
Your Example Website or App
https://reactflow.dev/docs/examples/edges/
Steps to Reproduce the Bug or Issue
Simple use arrows.
Expected behavior
Arrows are not working, also in your examples, I can't see them also if they are on the edges settings.
Check also here:
https://reactflow.dev/docs/examples/edges/
Screenshots or Videos

Platform

OS: macOS
Browser: Chrome
Version: 99.0.4844.74

Additional context
No response

Try it
{
   markerEnd: { type: 'arrow', color: '#f00' }
}

Refer to this link
https://reactflow.dev/docs/guides/migrate-to-v10/#8-arrowheadtype-markerendid---markerstart--markerend
The example on the documentation was probably forgotten to be updated.

Thanks @IgorZanellaDev. If you find bugs in the docs, you can open an issue in this repo: https://github.com/wbkd/react-flow-docs


realtime: on_* event handlers should take bevy SystemIDs

Allows for much greater access to the bevy world on receipt of data with a cohesive API
Should make setting channels up simpler, may remove the need for channel forwarders and associated code

Repo moved: https://github.com/bytemunch/bevy-realtime/issues/1


Why does this gem create cypress examples?

I've noticed that, after I run bin/rails g cypress_on_rails:install, I got a lot of cypress-only examples (not related to cypress-on-rails gem).
At first I thought these were somehow related to added functionality of cypress-on-rails and spent some time trying to find out what's added. But it turns out that that's not the case. As far as I can tell, these are just examples of how to use cypress API.
If that's the case, I'd suggest focusing on keeping the cypress-on-rails-specific examples, which would make it easier for user (developer) to get the hang of cypress-of-rails added functionality.
Cypress-only examples could be suggested to be added to the main cypress repo. Or you could simply have a link in README to where these examples are already located.
This is the commit that originally added these examples:
https://github.com/shakacode/cypress-on-rails/commit/fc8451123936e53751bc7de3106b16e9a8cab17e
Maybe it made sense back then, but now I'd remove it and simplify the gem by also being able to remove --no-install-cypress-examples.
I think with v2.0.0 around the corner, this would be a perfect time to remove it.
What do you think?

I agree, the examples of cypress ships with are pretty useless and very half-stack. We should get rid of them and replace them with cypress-on-rails specific examples instead.

The reason is comes with the Cypress examples is to make it more friendly to newbies of Cypress. Basically Cypress is still pretty new and this gem can be someones first introduction to it, thus both sets of examples are needed.

I agree. It would be good to be able to have/generate (not necessarily automatically) both sets of examples.
I've replied in more detail here: https://github.com/shakacode/cypress-on-rails/issues/24

I guess we could ask the question in the generator on whether or not they want the examples. Should  cater for both the newbie and pro.

@grantspeelman I propose we do get rid of examples that are not rails specific. I've spent a few days digging into rails generators in general to improve workflow on my team. I essentially overwrote the rails generators and extended them so that running
rails scaffold Widget name:string number:integer
# of if the model already exists
rails scaffold_controller Widget name:string number:integer

This create much more useful generators. It does require something like
# application.rb
    config.generators do |g|
      g.test_framework :cypress_and_rspec
   end

I'll try to wrap it all up in an article about generators and a PR for this specific generator as I think people would find it really useful.

I still learning towards making it easier for beginners of cypress.
You can disable the cypress examples with a flag --no-install-cypress-examples.
If we add that to the README.md would that be good enough?

Basically Cypress is still pretty new and this gem can be someones first introduction to it, thus both sets of examples are needed.

First version (v0.1.0) of Cypress is 5 years old and v1 is 3 years old. In JS world, I'd call that old, not new. It also has 6.5M downloads a month. It's pretty well established.
On the other hand, in Rails world, many people will add Cypress on existing project. And although many of those people will be new to Cypress, I don't believe I've seen many other packages add examples that you'd later remove. Ruby gems don't tend to do this. (Please correct me if I'm wrong.)
I've seen config files with examples/defaults commented out, but code examples...that seems more like something we can use Rails generators for, at least in Rails world.
Anyway, it's not that big of a deal. It's your call and I already said I'd do it differently (but it's not that important). I guess the best solution is to decide on one of the three options (mentioned below) and focus on more important features.
I think these are the only three steps forward:

"WON'T FIX" - close this issue, it won't be changed
Add the --no-install-cypress-examples to README
By default skip generating Cypress examples
3.a) Skip generating Cypress examples and document it in README

even though old in JS world terms, it's not old in people terms.
That said, think I'll make it optional and add to the README telling people how to generate the examples if they are new to cypress.


False positive for numpy

safety version: 1.10.3
Python version: 3.8.12
Operating System: Ubuntu 20.04.3 LTS

Description
Ran safety against the latest update and got a report of a failure on numpy, despite being on 1.22.1.
In the free safety DB, the values for numpy are expressed as:
"numpy": [
        "<1.13.2",
        "<1.16.3",
        "<1.21.0",
        "<1.22.0",
        "<1.8.1",
        ">0"
    ],

I'm not sure why >0 was added in the February release, but it seems to be causing this problem
What I Did
2022-02-01T15:10:46.7671452Z +==============================================================================+
2022-02-01T15:10:46.7677519Z |                                                                              |
2022-02-01T15:10:46.7726508Z |                               /$$$$$$            /$$                         |
2022-02-01T15:10:46.7726760Z |                              /$$__  $$          | $$                         |
2022-02-01T15:10:46.7727062Z |           /$$$$$$$  /$$$$$$ | $$  \__//$$$$$$  /$$$$$$   /$$   /$$           |
2022-02-01T15:10:46.7727279Z |          /$$_____/ |____  $$| $$$$   /$$__  $$|_  $$_/  | $$  | $$           |
2022-02-01T15:10:46.7727504Z |         |  $$$$$$   /$$$$$$$| $$_/  | $$$$$$$$  | $$    | $$  | $$           |
2022-02-01T15:10:46.7727745Z |          \____  $$ /$$__  $$| $$    | $$_____/  | $$ /$$| $$  | $$           |
2022-02-01T15:10:46.7727979Z |          /$$$$$$$/|  $$$$$$$| $$    |  $$$$$$$  |  $$$$/|  $$$$$$$           |
2022-02-01T15:10:46.7728200Z |         |_______/  \_______/|__/     \_______/   \___/   \____  $$           |
2022-02-01T15:10:46.7728430Z |                                                          /$$  | $$           |
2022-02-01T15:10:46.7728651Z |                                                         |  $$$$$$/           |
2022-02-01T15:10:46.7728876Z |  by pyup.io                                              \______/            |
2022-02-01T15:10:46.7729111Z |                                                                              |
2022-02-01T15:10:46.7729338Z +==============================================================================+
2022-02-01T15:10:46.7729569Z | REPORT                                                                       |
2022-02-01T15:10:46.7729828Z | checked 147 packages, using free DB (updated once a month)                   |
2022-02-01T15:10:46.7730086Z +============================+===========+==========================+==========+
2022-02-01T15:10:46.7730332Z | package                    | installed | affected                 | ID       |
2022-02-01T15:10:46.7730578Z +============================+===========+==========================+==========+
2022-02-01T15:10:46.7730786Z | numpy                      | 1.22.1    | >0                       | 44715    |
2022-02-01T15:10:46.7731010Z +==============================================================================+

Thanks for reporting this. Ran into the same issue this morning.

Good day!
CVE-2021-41495 for NumPy haven't been fixed yet in any release. See here: https://github.com/numpy/numpy/issues/19038
Note that in the same thread, NumPy devs argue about the validity and correct severity of this issue.
To be on the security side, we chose to report this as a possible vulnerability so users of NumPy can take the best informed decision considering their use-case.

@SCH227 Unfortunately, the only thing users of Numpy can really do here is ignore safety.
Am I missing something here?  numpy is a python package; if the attacker can run arbitrary python code, then they have much better attacks available than causing a null pointer dereference inside numpy.

Why do you think it is a false positive and how do you plan to proceed? Ignore this safety warning?

Hi people, I was looking for the same issue. I'm coming from java/android word where use OWASP checks also. There is a mechanism to check all project dependencies and instruct it to ignore or lower the severity of the issue for specific dependency with a specific version. Would it be a good feature request for the safety?

@emartynov safety has the option -i --ignore: https://github.com/pyupio/safety/#--ignore--i. So I decided to use --ignore 44715 to acknowledge the issue until a fixed numpy version is released in my case.

We are also working on some bigger updates to Safety, including an optional local policy file where one can set thresholds for severity that get surfaced, as well as ignore certain vulnerabilities or even allow-list a package version.

@emartynov came to me with a nice suggestion. What if safety could have the ignores specified in a separate file?
That way you wouldn't have to put the --ignore in your GitHub workflows (which in my opinion should be agnostic to this, if possible). So a suggestion from me would be to support specifying the ignores in pyproject.toml.

So, numpy 1.22.2 is out and mentions "Deal with https://github.com/advisories/GHSA-5545-2q6w-2gh6 complaint.". However, I still get a problem reported by safety. Is this expected?
The >0 comparison looks weird.
$ poetry run safety check --full-report

+==============================================================================+
|                                                                              |
|                               /$$$$$$            /$$                         |
|                              /$$__  $$          | $$                         |
|           /$$$$$$$  /$$$$$$ | $$  \__//$$$$$$  /$$$$$$   /$$   /$$           |
|          /$$_____/ |____  $$| $$$$   /$$__  $$|_  $$_/  | $$  | $$           |
|         |  $$$$$$   /$$$$$$$| $$_/  | $$$$$$$$  | $$    | $$  | $$           |
|          \____  $$ /$$__  $$| $$    | $$_____/  | $$ /$$| $$  | $$           |
|          /$$$$$$$/|  $$$$$$$| $$    |  $$$$$$$  |  $$$$/|  $$$$$$$           |
|         |_______/  \_______/|__/     \_______/   \___/   \____  $$           |
|                                                          /$$  | $$           |
|                                                         |  $$$$$$/           |
|  by pyup.io                                              \______/            |
|                                                                              |
+==============================================================================+
| REPORT                                                                       |
| checked 95 packages, using free DB (updated once a month)                    |
+============================+===========+==========================+==========+
| package                    | installed | affected                 | ID       |
+============================+===========+==========================+==========+
| numpy                      | 1.22.2    | >0                       | 44715    |
+==============================================================================+
| All versions of Numpy are affected by CVE-2021-41495: A null Pointer         |
| Dereference vulnerability exists in numpy.sort, in the PyArray_DescrNew      |
| function due to missing return-value validation, which allows attackers to   |
| conduct DoS attacks by repetitively creating sort arrays.                    |
| https://github.com/numpy/numpy/issues/19038                                  |
+==============================================================================+

@fredrikaverpil Yes, that is expected. The error in safety check will not go away until the safety-db is updated to remove the >0 version from the list of vulnerable versions

@fredrikaverpil @vinayvaddiparthi our db has been already updated and now the specs for CVE-2021-41495 are <1.22.2.
You will see this immediately in the safety db paid version, and in the next monthly update of the free db (in March).


Enable Travis CI cache to speed up CI checks

While there are a lot of dependencies need to be downloaded from maven central enable Travis CI cache maven dependencies helps speed up the CI process.
See http://docs.travis-ci.com/user/caching/

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Thanks @ian4hu . LGTM.


Support --output-hashing for serve command

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Desired functionality

build supports --prod and --output-hashing flags. It would be great if we could use the same flags for serve.
E.g.
ng serve --prod --output-hashing none
Also see issue.

ng serve --prod is already supported, and uses the production configuration in this target:
        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "latest-project:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "latest-project:build:production"
            }
          }
        },

The production configuration here says "use the production build options", which already includes all the production settings like output hashing.
If you have a custom configuration of options you need to use for building, you can add it as a new configuration inside the build target, then point at it from your serve target.


NOT ABLE TO INSTALL NPM DEPENDENCIES

Describe the bug
I don't know what is the problem
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-1pmnva
Steps to reproduce
I don't know
Expected behavior
I want to see a preview
Screen Recording / Screenshot
No response
Platform
Browser name = Safari
Full version = 18.0.1
Major version = 18
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0.1 Safari/605.1.15
performance.memory = undefined
Username = Zizou066
Chat ID = e1e0ff8d8e3c

Additional context
No response

Bolt is not compatible with Safari as described here: #2796. Continue developing in Chrome for best performance.


Update query params forwarding behavior for redirects.json file

For custom redirects, Ghost currently overwrites query params in to url as they are in from. This means if to url has any query params, they will get overridden to be empty instead if from url has no query params. This is leading to unexpected behavior, specially in cases where to url has explicit query params. Suggested update to behavior -

Merge from and to query params, with from overwriting to
Add option to not include any params from from

This covers most scenarios in which query params override can be used.

query params in the "from" field should be matched to the "from url"
query params in the "to" field should always be kept (ie, take precedence over incoming query params)
all other query params are passed through

This issue also applies to a redirect like this:
[{
"from": "^/media/(.*)$",
"to": "https://storage.googleapis.com/files.domain.com/media/$1",
"permanent": true
}]

In this case the URL works, but not for the $1 part, which is what I would expect and also our docs are describing.

Is there any workaround for this?

Hey @Louvki o/
No workaround that I'm aware of I'm afraid!
We'd welcome a PR if you find the time :ghost:

@Louvki 👋, if you create a topic on our forum I might be able to help you with a workaround https://forum.ghost.org

Hello, @stale. I'm working on this.

Todo

[x] to take precedence. URL query params pass through => #12333.
[ ] Allow matching query params in the from field.
[ ] Add option to ignore URL query params.


[Feature] Exclude Folders

Please add the ability to exclude folders in the hierarchy from the namespace.
Having a visual indicator would be nice too.
Example: Right click folder and have Adjust Namespace and Exclude Folder. Selecting Exclude Folder changes the color of the folder Icon. (My preference would be a light blue color). Adjust Namespace would skip these folders when building the namespace.

@Randy-Buchholz could you share a real use case for this? such feature can be implemented in various ways with different complexity, and I want to understand where such thing is useful specifically.

A main use is grouping. Say I have a large number of GUI Widgets. I want them available for users in the Gui.Widgets namespace.  They have some basic groupings - Buttons, Text, Image, etc.
Widgets Folder-
  - Buttons Folder (excluded)
     - W1.cs
     - W2.cs
  - Text Folder (excluded)
     - W3.cs
     - W4.cs

If I tag folders Buttons and Text for exclude, they turn blue so I know that "adjust" will produce
WIdgets.W1, not Widgets.Buttons.W1.
Similar is sub-grouping
Folder Outer -
    MainClassifier.cs
    Folder Main Details (ns-exclude)
       IMainClassifier.cs
       ImpMainClassifier.cs
    SecondClassifier.cs
    Folder Second Details (ns-exclude)
       ISecondClassifier.cs
       ImpMainClassifier.cs

Here I can keep my primary files at a higher level and stash the others below.
It doesn't affect the namespace, but makes it easier to navigate my project files

@Randy-Buchholz let's start from small steps.
I think that's good to store skipped folders in the special file, that can be pushed to git and shared between the whole team.
So, please

take the current version of this VSIX from this repository (NOT from a VS marketplace). Compile it and install into your VS.
create a file with name adjust_namespaces_settings.xml in the folder of your SLN.
put the following onto that file (utf8):

<?xml version="1.0"?>
<AdjustNamespaceSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SkippedFolderSuffixes>
<!--
here is a list of skipped folders
you can add an item with its full path like these:
    <string>C:\projects\github\AdjustNamespace\Tests\Subject\TestProject\A\B\C\</string>
    <string>C:\projects\github\AdjustNamespace\Tests\Subject\TestProject\A\B\C</string>
or you can add only a RELATIVE path from THIS folder like these:
    <string>TestProject\A\B</string>
    <string>TestProject\A\B\</string>
-->
  </SkippedFolderSuffixes>
</AdjustNamespaceSettings>

Perform the appropriate setup of the file (add skipped folders).
Give it a try, and lemme know your feedback.

I'm not sure I want to fight with the custom folder icons (but who knows...), but some custom widow to deal with skipped folders would be useful at the step 2.
Examples you can see into Tests\Standard folder.

I like the xml file approach and the popup window.
Some quick feedback:
I did a quick build and install but it's (seemingly) not working correctly.
It's only removes the ProjectName from the front no matter what path I use.
"C:\Temp\A\B\Class1.cs" with <>\Temp\A</> produces "namespace A.B" - It should be "namespace Temp.B".
The scan detects folders in matching ns paths for processing. Orphans (not in folder/ns) are not detected. So, a workflow is Sync (built-in), Adjust (yours) to do the whole thing.
This is just some quick FYI - I'll spend some time with this later and give you some better info.

@Randy-Buchholz try to remove a first slash <>\Temp\A</> -> <>Temp\A</>;
for me <string>TestProject\A</string> is working fine, but <string>\TestProject\A</string> is not.

@Randy-Buchholz fyi the window has been added in 0.1.14

Close as completed, as no feedback has come.


Autotools iOS packages must patch unrelocatable text files before being merged with lipo

The toolchain for iOS is failing for Autotools packages with unrelocatable text files. They need to be patched in all architectures. The patch must remove the architecture information which is present as the build directory in the text files.
Such examples of text files include *.la and *.pc.
Example of log of failure from https://travis-ci.org/ingenue/hunter/jobs/116995545#L2742
CMake Error at autotools-merge-lipo.cmake:234 (message):
  lipo execution failed: fatal error: lipo: can't figure out the architecture
  type of:
  /Users/travis/build/ingenue/hunter/_testing/Hunter/_Base/e53f669/58e7826/a239ac9/Build/odb/Build/multi-arch/armv7/lib/pkgconfig/libodb.pc

Today libtool *.la are being removed, so this behaviour should also be changed and the *.la files must be patched as per above.
A naive approach would be to use PACKAGE_UNRELOCATABLE_TEXT_FILES as the list of files to be patched, although I cannot guarantee that it will be enough.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36429166-autotools-ios-packages-must-patch-unrelocatable-text-files-before-being-merged-with-lipo?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

We already discussed it, no?

https://github.com/ruslo/hunter/issues/218
https://github.com/ruslo/hunter/issues/207

Sheesh, my bad, completely forgot about it. Let's close this and continue discussion on https://github.com/ruslo/hunter/issues/218


Add PDF converter

For file with extensions other that '.pdf' , add optional button to get converted book.

Added Converter using ConvertAPI in commit aab37b0


az webapp up failed with an unexpected error

Describe the bug
Everything worked fine, but my Azure for Students subscription was deactivated, so I upgraded to Pay-as-you-go and since then I can't deploy the app even though the az login works and app is ready. Location is West Europe.
Failed with an unexpected error.
Command Name
az webapp up
Errors:
Traceback (most recent call last):
cli\Lib\site-packages\knack\cli.py, ln 233, in invoke
azure\cli\core\commands\__init__.py, ln 660, in execute
azure\cli\core\commands\__init__.py, ln 723, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 715, in _run_job
azure\cli\command_modules\appservice\commands.py, ln 37, in _ex_handler
azure\cli\core\commands\__init__.py, ln 694, in _run_job
azure\cli\core\commands\__init__.py, ln 331, in __call__
site-packages\azure\cli\core\__init__.py, ln 811, in default_command_handler
azure\cli\command_modules\appservice\custom.py, ln 3878, in webapp_up
azure\cli\command_modules\appservice\custom.py, ln 422, in enable_zip_deploy
MemoryError

To Reproduce:
Steps to reproduce the behavior.

az login
az webapp up

Expected Behavior
Deploy code from a local workspace to the app.
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.21.0

Extensions:
db-up 0.2.1

Additional Context

[Solved] App memory was smaller than my deploy.


Space filled by borders isn't updated instantly when changing their properties

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit 6cea710ac8e966366763b9609895dcef7fdb5bcb  ().
Date: 2024-04-06
Tag: , commits: @COMMITS@

flags: (if any)

Bug or Regression?
Bug
Description
When borders are enabled, disabled, or have their sizes changed, the space occupied by them isn't updated instantly, only when an update happens, like when you switch to another workspace.
How to reproduce

Enable, disable, or change the size of borders using workspace rules
Notice that the space isn't updated until an update happens

Crash reports, logs, images, videos
https://github.com/hyprwm/Hyprland/assets/55629891/695b8a99-679b-46e2-8e0b-51f9358f11f1
https://github.com/hyprwm/Hyprland/assets/55629891/6a364dae-fc53-40e3-a6ff-a9cc69d06dd9

As far as I can tell, this is fixed, closing.


feat: batch large factory_deps

Motivation
When deploying a contract, if the size of factory_deps is too large, the tx may fail with out of gas (OOG) error.

Solution
Split a single CREATE with large number of factory deps into multiple transactions where only the last one is the actual CREATE, and earlier are empty transactions that merely deploy the batched factory_deps.
Note
In the provided test we have 4 factory deps, which are batched on the max size of 100000 bytes into 3 transactions:
INFO optimizing factory_deps count=4 total=216384 sizes=[416, 106976, 106208, 2784]
INFO optimized factory_deps into batches count=3 total=216384 sizes=[3200, 106208, 106976] batched_sizes=[[416, 2784], [106208], [106976]]

Closing in favor of https://github.com/matter-labs/foundry-zksync/pull/412


Return on empty NTS header

This prevents throwing an exception when doing headers.NTS.toLowerCase()

This is the same fix as https://github.com/diversario/node-ssdp/pull/44 -- pick the fix you like better, and reject the other PR

Thanks, @mnkhouri!


Sample and description updates for demo

The introduction and input samples need to be updated to reflect the changes in the service.

Implemented, approved and deployed.


Imported tspans all get an added top padding (dy)

When I import a text with tspan like this:
<text
 xml:space="preserve"
 style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans;-inkscape-font-specification:Sans"
 x="290.01382"
 y="382.73099"
 id="09.1-text"
 sodipodi:linespacing="125%"
 inkscape:label="#text3554">
<tspan
   sodipodi:role="line"
   id="tspan3556-7-2-2-9-2-5"
   x="290.01382"
   y="382.73099">09.1</tspan></text>

The resulting object after import is this:
<text id="09.1-text" font-family="Helvetica, Arial, sans-serif" inkscape:label="#text3554" sodipodi:linespacing="125%" y="382.73099" x="290.01382" xml:space="preserve" style="font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; text-align: start; line-height: 125%; letter-spacing: 0px; word-spacing: 0px; writing-mode: lr-tb; text-anchor: start; fill: rgb(0, 0, 0); fill-opacity: 1; stroke: none; font-family: Sans;">
<tspan id="SvgjsTspan1621"
            dy="20.8"
            x="290.01382">09.1</tspan></text>

The y attribute for the tspan is removed and replaced by the dy attribute with the calculated content of 1.3 * 16 = 20.8.
This makes every text i have space 20.8 pixels down the place they actually should be.
I currently fix this by looping through all those elements in my own code and removing the dy, which fixes the problem, but of course that is not a situation i want to be in.

As much as I can follow your changes you basically add plain text when only one line is given but that doesn't fix this problem since the tspan is removed

This bug is fixed in svg.js v2


Cyphers/opsetcheck

Won't this create an opset which includes all ops, including the ones removed in opset3, such as Reverse?
// Moved out of opset2, it was added to opset1 by mistake
// NGRAPH_OP(Reverse, ngraph::op::v1)

Why would we want this?

What we really want is the set of ops IE will execute; ones in opsets 1-3. I refactored to just get the set of those type infos and not call it an opset.


Alive method

Proposal: Method to know if the thing is alive or not
Methods Types

Name
Description
MSCB::ID
MSCB::PATH
LSCB::METHOD
LSCB::HEADER
LSCB::BODY
BODY::LENGTH
Minimum Total Length

Signal
Ligthweight signals like events
0
0/1
0b000001
0/1
0/1
up to 255 bytes
2 bytes

Request
Request that needs response
1
0/1
0b000010
0/1
0/1
up to 65535 bytes
4 bytes

Response
Request's response
1
0
0b000011
0/1
0/1
up to 65535 bytes
4 bytes

Streaming
Streaming data
1
0/1
0b000100
0/1
0/1
up to (2^32 -1) bytes
6 bytes

Alive's Request
Request Alive. Heartbeat mechanism to determine if the connection is still alive or if it has been closed
0
0
0b000101
0
0
0 bytes
2 bytes

Alive's Response
Response the alive's request
0
0
0b000110
0
0
0 bytes
2 bytes

merged on #9


Port notify package

Ports the notify package from a product. This code was ported verbatim with the one exception that the notify package was renamed to rsnotify.

Merged with #33.


Need clarification

You might sometimes want to create a Kubernetes secret to mirror the mounted content.

When would I want to do this? Is this how I get a secret to eventually be set on an environment variable for my application? Is creating a Kubernetes secret getting me back to using k8s secrets which has "security concerns".

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

ID: 409a3be9-4831-9401-0bb3-c65209bb3f42
Version Independent ID: 4cf81213-5989-f36c-7456-70accfe452c2
Content: Use the Azure Key Vault Provider for Secrets Store CSI Driver for Azure Kubernetes Service secrets - Azure Kubernetes Service
Content Source: articles/aks/csi-secrets-store-driver.md
Service: container-service
GitHub Login: @Nickomang
Microsoft Alias: nickoman

@knunery
Thanks for your Question! We are currently investigating and will get back on this.

Hi @knunery, thanks for the question. You're correct in identifying that mirroring the mounted content as a K8s Secret object can be used to set the content as an ENV variable, although this isn't the only reason why one might do so (configuring an imagePullSecret, for example).  You're also right that using K8s Secret objects requires certain security considerations, so it may not be viable for a given set of business requirements.
I hope this helped, please let me know if there's further clarification required.

@Nickomang Thanks for clarifying this.


Build error

Hi, thanks for the dockerfile.
When I use this to build my ionic3 project on gitlab, I get this error in the console:
No installed build tools found. Install the Android build tools version 19.1.0 or higher.
Seems it cant find build tools. From googling around, looks like a problem with the android_home env variable, but I can see its being set in the dockerfile.
Any idea how to proceed with this?
Many thanks
Mark

@MarkySparky
Hi,
I've pushed an updated version of Dockerfile. Please try to build it against that one and, please, let me know whether you face the same issue or not.
Cheers,
Artyom.

Will do. On train, wifi slow, but fingers crossed. Thanks
On 27 November 2017 at 10:46, applicazza<EMAIL_ADDRESS>wrote:

@MarkySparky https://github.com/markysparky
Hi,
I've pushed an updated version of Dockerfile. Please try to build it
against that one and, please, let me know whether you face the same issue
or not.
Cheers,
Artyom.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/applicazza/docker-ionic3/issues/1#issuecomment-347145239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA9Py6rtz6jfRkIFSk0fxMa7yylkFEFfks5s6pMZgaJpZM4Qrbw_
.

Just realised I didn't get back to you. Really sorry about that.
Yes, it worked. Thanks very much indeed.


Interest in Additional LIbrary Features

There are a couple of features that I am going to be developing for my personal project on a fork of this library, and I want to know if you would be interested in me upstreaming any/all of the features I'm planning on making. I'm not quite sure what you want the scope of this project to be. All of these would add on to the functionality, not replace it.

A type safe interface built on std::function.
A shared mutex.
A separate threadpool for IO blocking operations with api to call it.
Optional instrumentation of the fiber pool.

@martty This is meant as an internal implementation, so it isn't fully polished, but I have a working interface here: https://github.com/BVE-Reborn/fiber-tasking-library/tree/type-safe-interface. If you have a better idea for the interface, I might rewrite this perfect forwarding wrapper on top of your interface.

That sounds great!
For the blocking IO threadpool, is that like in the GDC talk, where they had a few threads to handle blocking IO, so-as to not tie up the main workers?
What kind of instrumentation are you thinking?

I feel bad for the poor souls watching this repo :stuck_out_tongue:
Yeah my plans are similar to the talk. I would have a pool of say... thread_count * 4 (by default) threads to do blocking IO in. There would be a call similar to my thread-safe-interface which would send off the data to be processed and have it wait on a counter that would be decremented by the worker thread.
The instrumentation would be similar to the talk as well. Not sure exactly what it would entail, but information about timings, task dependency stacks etc. I haven't really thought about it at this point.

That sounds good to me.
For the instrumentation, it would be really cool to have something like Remotery / Microprofile that understood fibers and task waiting / resuming. Perhaps we could add optional callback registering? So user / third party code would be notified when tasks are added, suspended, resumed, etc.

Seems feasible. I'll take a look at those librarys and see what I can do.

@cwfitzgerald Please check #69 for a preliminary implementation of the type safe interface.

@RichieSams  ive used remotery a bit with this lib in my project https://github.com/vblanco20-1/Rasterizer . There are huge flaws with remotery, as it can "choke" really, really hard. Even like that, i just added the logging inside the task function.  It ends up looking like this. (one frame of the rasterizer)

Another issue with remotery is that this library completely breaks it on the "wait for counter" function, due to the fiber switching.
What you comment with the callback sounds great maybe i could help with that. It could work great if you can just send the "name" of the task in the AddTasks/RunTasks function.
taskScheduler->AddTasks(numTasks, tasks, &taskEnd->counter, "rasterize_tile");


Feature request for MapDB/ crawled data

One of the database systems that HTTP Collector uses to store information about crawled documents is MapDB. It seems that when HTTP Collector upgrades MapDB to a new version, the existing crawled data is not longer accessible, getting the error: storage has invalid header. So, suddenly, HTTP Collector can't access its crawled data so the crawling system doesn't work anymore.
The first feature request for HTTP Collector is to implement a function that upgrades the existing crawled data to the new MapDB version, so HTTP Collector can keep working with its crawled data.
Furthermore, since it is expected that the crawling system based on HTTP Collector will evolve and need more resources, presumably will need to use any of the other databases systems that HTTP Collector supports.
The second feature request  for HTTP Collector is to implement a function that migrates the existing crawled data from one database system to another (among the database systems supported by HTTP Collector) so HTTP Collector can keep working with its crawled data.

This has been implemented in version 3.  While MapDB is no longer used, you can now export the storage engine content in a neutral format and re-import it in the same or another storage engine (e.g., from MVStore to MongoDB, or to JDBC database).
Sample usage (Linux):
collector-http.sh storeexport -config=/path/to/collector-config.xml


Add tests for batch validator

Signed-off-by: Igor Egorov<EMAIL_ADDRESS>Description of the Change
Add tests for the new logic inside batch validator.
Relates to #27
Benefits
Increased tests coverage.
Possible Drawbacks
Not known
Usage Examples or Tests
batch_validator_test

Replaced by #45


python update.py detaches head

PS C:\IBL_root> python update.py
Getting info on remote branches from origin
Fetching origin

Current version: 1.0.0

Available versions: ['1.0.0', 'basicChoiceWorld_v0.1.0']

Newest version |basicChoiceWorld_v0.1.0| type:

python update.py basicChoiceWorld_v0.1.0

Done

Then,
PS C:\IBL_root> python update.py basicChoiceWorld_v0.1.0

Available versions: ['1.0.0', 'basicChoiceWorld_v0.1.0']

Checking out basicChoiceWorld_v0.1.0
Note: checking out 'tags/basicChoiceWorld_v0.1.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 030300d... pybpod_updated to master
M       pybpod
M       pybpod_projects
Running: git submodule update
Done

which detaches the head and disables further updates
PS C:\IBL_root> python update.py basicChoiceWorld_v0.1.0
C:\Users\IBL\AppData\Local\Continuum\anaconda3\envs\pybpod-environment\python.exe: can't open file 'update.py': [Errno 2] No such file or directory

I can fix this by git checkout master, but not sure whether this behavior is intentional

Yes, its intentional. v0.1.0 has no update.py so when you check it out it deletes that file and you are not able to use it any more...
I maybe should remove the possibility of reverting to that version.
The versions people should use start with 1.0.0 and greater.


Revert "Update Game Instructions"

Reverts Nima21/reviewing-a-pull-request#2

git fetch origin
git checkout -b revert-2-game-instructions origin/revert-2-game-instructions
git merge main


It looks cut off on Android.

Hi,
I know this issue has been reported, we just want to know if you will fix it.
Thanks,

same problem


Update docs for Text allowFontScaling

Explain the motivation for making this change. What existing problem does the pull request solve?

The documentation was slightly out of date. Following https://github.com/facebook/react-native/pull/10898, which removed the @platform ios tag, this updates the inner documentation to remove the reference to iOS.

Thanks!


Throw tool exit on malformed yaml in flutter manifest

The loadYaml call here:
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/flutter_manifest.dart#L38
can thrown an exception when the yaml is invalid. We should catch it and throwToolExit instead with a helpful error message.

This is possible the result of folks editing pubspec.yaml files that were auto-generated by an IDE as here.


Remove reference to nonexistent workload identity functionality

The Google connector docs' reference to relying on GKE Workload Identity, instead of hardcoding service account credentials, was merged as part of PR 138. One of the PRs it documents, 2989, implements that functionality, but has been open for ten months.
I would prefer to see PR 2989 merged without delay, and that functionality promptly released, after which this PR could be closed without merging. Failing that, this PR should be merged to remove the inaccurate claim of support for Workload Identity from the Google connector docs. There are several people in the 2989 discussion who've been misled by it, as was I.
Thanks for your time.

@irons @nabokihms seems like this PR can be reverted because the Google Workload Identity functionality was merged in https://github.com/dexidp/dex/pull/2989

@StepanKuksenko This can be reverted, indeed. I've just tested it out and it works when not providing the JSON


Get test suite hooked up to CI (CircleCI)

Looks like CI isn't running tests (maybe just because it's from a fork) on #11

The test suite is running on master, but apparently not on PRs?

This is fixed now (Migrated to GitHub Actions)


Ignore files when exporting package

This commit is part of a campaign to reduce the amount of data transferred to save global bandwidth and reduce the amount of CO2. See https://github.com/Codeception/Codeception/pull/5527 for more info.

@simonschaufi Thanks for filing this PR, I agree that these changes make perfect sense!
I've just merged #34 by your namesake. It's somewhat similar to your changeset and also adds a .gitattribute file.
Thank you both!


Feature/fire animation proto

Reviewer: Francesco
Asana: https://app.asana.com/0/inbox/361428290920650/351540654508048/367256361004223
Description:
A flat prototype of the fire animation. Note this is a quick prototype with no mask. An external organisation is designing the official version as per https://app.asana.com/0/inbox/361428290920650/275938474052467/367256361004223 after which this will be reimplemented
Steps to test this PR:
Press the burn button to match the fire animation
Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR DRI Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications (Database connections, Grafana stats, CPU)

@subsymbolic do you want me to merge or review? (since I'm listed as an assignee not a reviewer)

@fgei, just a review would be great. I'll merge it afterwards.


LUA Error Cannot find a library instance of "LibDBIcon-1.0"

Heya! CraftSim isn't loading. Getting this error on launch, even if CraftSim is the only addon enabled.
Message: Interface/AddOns/CraftSim/Main/CraftSim.lua:6: Cannot find a library instance of "LibDBIcon-1.0".
Time: Wed Jan 10 09:23:50 2024
Count: 1
Stack: Interface/AddOns/CraftSim/Main/CraftSim.lua:6: Cannot find a library instance of "LibDBIcon-1.0".
[string "=[C]"]: in function `error'
[string "@Interface/AddOns/Auctionator/Libs/LibStub/LibStub.lua"]:23: in function `LibStub'
[string "@Interface/AddOns/CraftSim/Main/CraftSim.lua"]:6: in main chunk

Locals: (*temporary) = "Cannot find a library instance of "LibDBIcon-1.0"."

Seems to be occuring when CraftSim is the only addon using this library!
Fixed and soon to be released in 12.4.1


Add operator <~

There is already an operator ~> what bind observable to observer.
How about add an operator <~ what bind observer by observable?

I am not sure what you want to implement.
You mean
a <~ b == b.bind(to: a) ??

a <~ b == b.bind(to: a)
Correct! It's what I want to say.

No nessary.

I think adding the operator <~ makes the operators confused to understand.
Because we have a two-way binding operator <~>.
Even it is a two-way binding operator, we have to use it according to order, just like:
BehaviorRealy <~> ControlValue

You can confirm the implementation of the two way binding method.
The operator <~ makes it possible to reverse the binder and observable object.
However, I do not hope to reverse for the operator <~>.
For this reason, close this issue.


Admins can now see pending users

#225
Seems like we were checking for active users even though the users in question were not yet active.

HI @NolanChan, thanks for taking care of this. Be aware though that non-active members should not be shown in most contexts. Did you check, in which places the changed #current_member helper method is used?

Btw. cool GIF! How did you make that?

@phillipoertel I didn't realize that current_member is used in a lot of places. I'll look into some other solutions, and will need some feedback on them.

After talking with @phil-monroe , it seems that the current_member method is confined to the relevant show.slim file, and there doesn't seem to be an privacy issues. All other privacy considersations are taken care of in the ability.rb file

LGTM, thanks @NolanChan!


Don't crash on flutter create . on Windows

Fixes #9828
Work-around for https://github.com/dart-lang/path/issues/24.

LGTM modulo Chris' comment


fix(keyvaluestorage): ensures localStorage is accessed safely

Description

Towards fixing: https://github.com/WalletConnect/walletconnect-monorepo/issues/1658
Ironically the only open issue on that localStorage lib is someone raising exactly this issue: https://git.coolaj86.com/coolaj86/local-storage.js/issues/1
Based on the dates of the last updates to that lib, it doesn't seem like this will get patched there anytime soon. Since this is a single file with code that basically never needs to change, I decided it's simpler for us to just manage this via an internal lib/ folder and bundle it.
Here's the actual fix commit: https://github.com/WalletConnect/walletconnect-utils/commit/da3e3073f7f5ab48f35266a8dc349f1b763a9e93

How has this been tested

Built and symlinked into the repro branch provided in https://github.com/WalletConnect/walletconnect-monorepo/issues/1658

Followups

[ ] Publish patch for @walletconnect/keyvaluestorage

Looks like one of the jsonrpc-ws-connection tests I added broke/is 401'ing when trying to connect to the staging relay. Probably needs a dynamic approach instead of the static wss: string.
Will patch in a separate PR since unrelated to this change.


pac org fetch --xmlFile seems to ignore order attribute

When executing pac org fetch --xmlFile "MyFilter.xml" the order attribute <order attribute="modifiedon" descending="true" /> seems to be ignored.
Here is the entire FetchXML
<fetch>   <entity name="contact">     <attribute name="fullname" />     <attribute name="modifiedon" />     <order attribute="modifiedon" descending="true" />   </entity> </fetch>

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 10bda820-3ad2-29d7-9cb2-bc87afbd1f7b
Version Independent ID: 10bda820-3ad2-29d7-9cb2-bc87afbd1f7b
Content: Microsoft Power Platform CLI org command group - Power Platform
Content Source: power-platform/developer/cli/reference/org.md
Service: power-platform
Sub-service: developer
GitHub Login: @snizar007
Microsoft Alias: snizar

Thanks for your comment, @alx-kpk. This issue has been assigned to the doc author for review.

@alx-kpk
Sorry for the delay in responding.
Issues in this repo are for the documentation.  Nothing actionable to document here.
Use github.com/microsoft/powerplatform-build-tools/discussions to view and submit feedback for PAC CLI.


Files in node_modules are parsed on build

🐛 Bug Report
When running the command npm run build, files in the node_modules folder are checked by the engine.
This creates a lot of unnecessary overhead and logs many errors in the console like so:

[WARN] unresolved links in file 'website/node_modules/mixin-deep/node_modules/is-extendable/README.md' > [ '.verb.md' ]
[WARN] unresolved links in file 'website/node_modules/mixin-deep/README.md' > [ '.verb.md' ]
[WARN] unresolved links in file 'website/node_modules/nanomatch/README.md' > [ '.github/contributing.md', '.verb.md' ]

There also are some errors logged from the fixture files for the tests:

Header field "unlisted" in /home/jeahel/dev/the-hive/documentation/website/node_modules/docusaurus/lib/core/__tests__/__fixtures__/blog-post-with-draft.md is not supported.
Header field "authorTwitter" in /home/jeahel/dev/the-hive/documentation/website/node_modules/docusaurus/lib/server/__tests__/__fixtures__/2018-08-17-docusaurus.md is not supported.

And some errors with BABEL, still in the node_modules folder:

[BABEL] Note: The code generator has deoptimised the styling of /home/jeahel/dev/the-hive/documentation/website/node_modules/docusaurus/lib/core/metadata.js as it exceeds the max of 500KB.

Have you read the Contributing Guidelines on issues?
I have.
To Reproduce

Create a new Docusaurus project with docusaurus-init
Build the website with cd website && npm run build
Look at the console output

Expected behavior
I expect the engine not to go through the node_modules/ folder not to waste time, and no log errors about files I am not supposed/required to know about (errors about the fixtures and BABEL).
Actual Behavior
The opposite: all files from the dependencies in node_modules/ are parsed, and errors about unknown files are printed out.
Reproducible Demo
No need to clone a repo, juste create a new Docusaurus project with npx docusaurus-init.

I realized this is due to the .gitignore file so I updated the bug description.

Hi @glecetre, are you still seeing this issue? This is what I'm seeing:

I'm sorry I did not come back sooner but I understood the problem.
In my config file, I had changed the customDocsPath setting to avoid having a /docs folder, so I used the value ./. So of course there was the website folder, containing node_modules, and it was parsed by the engine.
Maybe you would want to change that behaviour to prevent parsing the website folder, but my bug in itself can be closed.
Thanks


How to replace and call a function if I know the address of the target?

I successfully injected the dll, but I don't know how to replace the function with my version based on the address (module offset) and call it.
The table decompiled by others shows relative addresses, but rust calls seem to be based on raw addresses.
In almost all cases, an error (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION) will be reported
unsafe {
    let f: extern "fastcall" fn() -> bool = unsafe { std::mem::transmute(0x4E as *const ()) };
    f() // (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
}

Take a look at my other repository BurntSushi, where i do just that to block ads in Spotify.

dumpbin /exports <dll> + GetProcAddress + retour is indeed a good method.
But a game I encountered needs to hook functions in exe. In this case, there is no export name, only an offset table compiled by others.


Pad after setting width in text input

This fixes an issue where using Length::Units and Padding with a text input causes it to be bigger than Length::Units by Padding.
We need to apply pad to Limits AFTER width, otherwise width will set Limits back to a fixed width if Length::Units is used, overwriting padding.

Good catch 👍🏻


Reusing dispatching functions with React

Is there any way to use reusable functions for dispatch calls, to avoid repeated rendering of buttons etc.? (https://github.com/japgolly/scalajs-react/blob/master/doc/PERFORMANCE.md)
Currently I've defined a singleton for the action functions, and passing that object for every component that needs to dispatch actions. This leaves the dispatcher in the ModelProxy unused.
case class Actions(dispatcher: Dispatcher) {
  val increase: ReusableFn0[Unit] = ReusableFn0(() => dispatcher(Increase(2)))
  val decrease: ReusableFn0[Unit] = ReusableFn0(() => dispatcher(Decrease(1)))
  val reset: ReusableFn0[Unit] = ReusableFn0(() => dispatcher(Reset))
}

  val actions = Actions(AppCircuit)

  val routerConfig: RouterConfig[Page] = RouterConfigDsl[Page].buildConfig { dsl =>
      ...
      | staticRoute(root, HomePage) ~> renderR { router =>
        AppCircuit.connect { model => model } { proxy =>
          HomeView.Component(HomeView.Props("Home", proxy, actions, router))
        }
      }
      ...

And finally in the component:
  class Backend(scope: BackendScope[Props, Unit]) {
    def render(props: Props) = {
      <.div(
        <.p("Value = ", <.b(props.proxy.value.counter)),
        ButtonGroup.Component(
          Button(Button.Props(props.actions.increase), "Increase"),
          Button(Button.Props(props.actions.decrease), "Decrease"),
          Button(Button.Props(props.actions.reset), "Reset")))
    }
  }

(In case you are wondering where ReusableFn0, I defined a custom 0-arity ReusableFn. As such type does not exist in scalajs-react, I might be doing something wrong there.)

Would you get the same result by just declaring the callbacks as vals in the Backend class?
  class Backend(scope: BackendScope[Props, Unit]) {
    val incCB = scope.props.flatMap(_.proxy.dispatch(Increase(2)))
    val decCB = scope.props.flatMap(_.proxy.dispatch(Decrease(1)))
    val resetCB = scope.props.flatMap(_.proxy.dispatch(Reset))

    def render(props: Props) = {
      <.div(
        <.p("Value = ", <.b(props.proxy.value.counter)),
        ButtonGroup.Component(
          Button(Button.Props(incCB), "Increase"),
          Button(Button.Props(decCB), "Decrease"),
          Button(Button.Props(resetCB), "Reset")))
    }
  }

Also your Button would have to have shouldComponentUpdate defined for any of this to make any difference.
In general, you don't need the Reusability tricks with Diode, since the model is immutable and any change is automatically an indication to re-render. That's the whole point of the connect method :)
Of course you should not pass the whole model around to components, as that will trigger render on any change anywhere in the model. The passed model should be scoped correctly to avoid that.

Thanks, using callbacks that way does seem to work. I defined reusability in the Button component as
implicit val functionReuse = Reusability.by_==[CallbackTo[Unit]]

Diode being inspired by Redux, I was following Redux's principle of having the connector only at the topmost component (http://rackt.org/redux/docs/basics/UsageWithReact.html: "Try to only do this for a top-level component, ..."). Earlier I was calling connect in the router. Based on your comments, I'm now passing my AppCircuit (actually just trait ReactCircuit extends Circuit[RootModel] with diode.react.ReactConnector[RootModel]) to the active top-level view.  The top-level view then connects sub-components to subset of the state. Does this make sense?

Redux doesn't have fine-grained listener model, so it makes sense to have only the top components "connected" but with Diode it's a different situation.
You should wrap components that do not actively need to be told about changes (many top-level components are like this, because they only contain other components) and then use connect on the next level components that do need to be notified when the model changes. This will minimize re-renderings when the model is updated.
For example from the SPA tutorial:
    (staticRoute(root, DashboardLoc) ~> renderR(ctl => SPACircuit.wrap(_.motd)(proxy => Dashboard(ctl, proxy)))
      | staticRoute("#todo", TodoLoc) ~> renderR(ctl => SPACircuit.connect(_.todos)(Todo(_)))
      ).notFound(redirectToPage(DashboardLoc)(Redirect.Replace))

  def layout(c: RouterCtl[Loc], r: Resolution[Loc]) = {
    <.div(
      // here we use plain Bootstrap class names as these are specific to the top level layout defined here
      <.nav(^.className := "navbar navbar-inverse navbar-fixed-top",
        <.div(^.className := "container",
          <.div(^.className := "navbar-header", <.span(^.className := "navbar-brand", "SPA Tutorial")),
          <.div(^.className := "collapse navbar-collapse",
            // connect menu to model, because it needs to update when the number of open todos changes
            SPACircuit.connect(_.todos.map(_.items.count(!_.completed)).toOption)(proxy => MainMenu(c, r.page, proxy))
          )
        )
      ),
      // currently active module is shown in this container
      <.div(^.className := "container", r.render())
    )
  }

It wraps the MOTD module as it's just a container, but uses connect for the Todos and the menu, as they need update notifications.

Actually the SPA example has a problem with the menu connect since it uses a calculated value, which will always resolve in a new reference and therefore force re-rendering. It should just use _.items and do the counting in the component itself. This will be fixed in the next SPA release.

Thanks again. I now see that wrap vs connect is explained in the documentation. Sorry I didn't read the docs well enough. :) My code is much cleaner now, based on your suggestions.
Overall, I am very impressed by the quality of Diode, and how well you have thought it out. Thank you for contributing it.


Document source of .gitignores

It'd be great if https://github.com/github/gitignore was identified as one of the sources of .gitigore files.

Where would you like to see that identified?

Just somewhere in the README and on the docs section of the website. Perhaps in a section about how to contribute to the .gitignore templates.

That has been in CONTRIBUTING.md since September of 2014 which is the same time I added GitHub's ignore as a submodule.  This is also inline with GitHub's Contributing Guidelines.  That being said, maybe I should add it somewhere else because a lot of people don't immediately seem to realize that there is a submodule.

Glad to see it in CONTRIBUTING.md. My main thing was that I skimmed the README and couldn't find the source of the gitignore's nor where they were located in the repo. Additionally CONTRIBUTING.md says to PR to files to /data/gitignore/Custom. I think the community would be better off it they supported them to https://github.com/github/gitignore and as a backup submitted them to your repo if gitignore does not want to accept.

I think the community would be better off it they submitted them to https://github.com/github/gitignore and as a backup submitted them to your repo if gitignore does not want to accept.

That is how it works.

I think a bullet under Adding/Updating Templates in CONTRIBUTING would make that a bit more clear.

:+1: go ahead and add what you think.  I'll merge it.

So @bbodenmiller I'm actually going to close this because I just went back though some history and remembered why I created his project.  The whole reason this project was created was because GitHub wasn't actually merging any PRs for months.  I actually went though manually, commented on and merged a lot of PR's into my library at the time.  So while GitHub has a good source, I'm still not going to recommend that people contribute there first as the original vision of this project is to become the authoritative source (which is also stated in the CONTRIBUTING.md).

@bbodenmiller this is a perfect example of why I made this site: https://github.com/joeblau/gitignore.io/commit/59cc5a506a68280d52d9e36098405cf54fe53537


lint: use typos as precommit's hook

Reference Issues/PRs
reaction to #19 #45 #55 #133 #155 #212 #254 #255
What does this implement/fix? Explain your changes.
adding typo check as pre-commit hook
Any other comments?
🧡 Thanks for contributing!
cc: @klieret

@klieret, I believe this could prevent many issues in future :)


[v12] Refactor fetch route - fix for when there's an underscore in the field name

This was discussed in #2905
I still think we should do it, there is no need for us to have this inconsistency in the code.
It's a breaking change, but if we don't do it now, we would be carrying this bug for the next version.
The BC in developer perspective does not change much, if they were using data_source to overcome the problem of using camelEntity it's just a matter of deleting the data_source from the field and let Backpack automatically pick it.

I still agree to doing this, but... we have enough breaking changes in 4.2 already... Since there's a reasonable and documented workaround for people who encounter this... I'm going to either postpone merging this until the next major version... or find a way to do this in a non-breaking way.
I've:

fixed the merge conflicts, so that it's easier for future-us to merge it;
run through the docs to fix typos and such;
found an alternative (non-breaking) fix in https://github.com/Laravel-Backpack/CRUD/pull/3995

A few notes for future-us:

What I like about this solution:

super-simple, elegant, easy to understand - the method is the route;

What I don't like about this solution:

the route itself looks odd and doesn't follow the Backpack & Laravel conventions: menu-item/fetch/PersonalItem
it's a breaking change for everybody who's defined data_source on their field;
it's a breaking change for everybody who's used the select2_ajax filter with the Fetch Operation; and there they actually have to pass the route menu-item/fetch/PersonalItem so... they see it 👀 feels a bit like they're seeing my underwear and it's dirty 😅

It's possible you've been thinking about this the wrong way @pxpm :

if problem is when a FIELD has a name with an underscore, then the FIELD is the problem, not the FetchOperation;
then the fix should be inside that FIELD, not the FetchOperation;

Please see https://github.com/Laravel-Backpack/CRUD/pull/3995 - it's a quick PR I did that should solve the problem.

Closing in favour of #3995


fix bug template

@Crazypersonalph So it looks like the merge did not complete successfully before. It has been fixed in this pull request.

Looks like the merge was successful, there were just some incorrect details.
Rectifying now.

perfect


Problem on userLogin function at Zabbix 2.4

At Zabbix 2.4 I've found the error message: 'API error -32602: The "user.login" method must be called without the "auth" parameter.' on executing userLogin.
to resolve this, I've changed the line 215
from:
'auth'    => ($auth ? $this->auth : ''),
to:
'auth'    => ($auth ? $this->auth : NULL),

Hi
First of all, thank you for your bug report. I'm kinda busy and it's always a pleasure when people help to debug stuff :)
I think there's something wrong with the logic right there. IMO $auth is always true on line 215, because it was already checked in the if clause we're currently in :)
So I think it should be referenced to $this->auth (instance variable) instead of $auth (local variable).
diff --git a/templates/abstract.tpl.php b/templates/abstract.tpl.php
index eaaf7ae..98ec1f9 100644
--- a/templates/abstract.tpl.php
+++ b/templates/abstract.tpl.php
@@ -212,7 +212,7 @@ abstract class <CLASSNAME_ABSTRACT>
                 'jsonrpc' => '2.0',
                 'method'  => $method,
                 'params'  => $params,
-                'auth'    => ($auth ? $this->auth : ''),
+                'auth'    => ($this->auth ? $this->auth : NULL),
                 'id'      => $this->id
             );
         }

I'll commit the fix asap, can you try it again?
Cheers
Domi


kong and 302 redirects

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: test-springbootzipkin
namespace: test
annotations:
konghq.com/strip-path: "true"
kubernetes.io/ingress.class: kong
spec:
rules:

http:
paths:

path: /springbootzipkin
backend:
serviceName: springbootzipkin
servicePort: 3000

I test it with:
wget http://${GATEWAY_URL}/springbootzipkin
--2018-12-21 12:56:30--  http://<IP_ADDRESS>/springbootzipkin
Connecting to <IP_ADDRESS>:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: ./zipkin/ [following]
--2018-12-21 12:56:31--  http://<IP_ADDRESS>/zipkin/
Reusing existing connection to <IP_ADDRESS>:80.
HTTP request sent, awaiting response... 404 Not Found
2018-12-21 12:56:31 ERROR 404: Not Found.

@huangkaiyan10,
The 302 redirect tells the user agent (here: wget) to make another request to the specified location.
It appears that you have defined an Ingress path for /springbootzipkin but not for /zipkin/. The ingress backend makes a redirect to /zipkin/ for which Kong does not have a route defined.
This is most likely misconfiguration of your application - it makes redirects to an (absolute) URL outside of the context path /springbootzipkin. The best way to fix this would be to configure redirects in your application as relative.
If the backend is zipkin, this might be helpful: https://github.com/openzipkin/zipkin/issues/1452
HTH,
Michal


Inconsistent substitute $123

The below code basically means, that NumberFound will be true for any $1 to $89
But not for $90 and up.
That seems are strange choice.
  RegexMaxGroups = 90;
    GrpIndexes: array [0 .. RegexMaxGroups - 1] of integer; // map global group index to _capturing_ group index

  procedure FindSubstGroupIndex(var p: PRegExprChar; var Idx: integer; var NumberFound: boolean);
  begin
    Idx := ParseVarName(p);
    NumberFound := (Idx >= 0) and (Idx <= High(GrpIndexes));

The test asserts, that a number not present is ignored. But that works only up to 89.
And then behaviour changes.
    // 70
    (
    expression: '(b)';
    inputText: 'abc';
    substitutionText: '$1$2$9';
    expectedResult: 'abc';
    matchStart: 1
    ),

Changing that test to $1$2$90  leads to a result of ab$c
IMHO, any $123 ... that does not have a group should be "".

@Alexey-T

IMHO, any $123 ... that does not have a group should be "".

Good catch. Agree with that.

Is included in https://github.com/User4martin/TRegExpr/commits/group-idx


bump version in package.json to v2.16.5

release version v2.16.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


instance manager for debugging

To print debug log for something, simply select that thing in default tool (vehicle/building) or in TMPE no subtool mode (node/segment)
selecting segment in TMPE no tool mode already selects the instance ID in instance manager. I made modification to do the same to node.
for stat/end segment/building, TMPE_GlobalConfict.xml can be used to select one and instance manager can be used to select the other.
TrafficManager.zip

on way of doing managing start/end instance is simply to add a button to debug panel to set start Instance to the current instance. end instance can be selected using instance manager afterwards.
also I can add an deselect instance button too.


Customize color of green horizontal line

Issue
The color of the Green horizontal line (spearation) is very similar to kitty terminal panel separation color, which create confusion.
Any way to customize this color ?

Version and model info
No response

Thanks for trying aider and filing this issue. This doc may be helpful:
https://aider.chat/docs/config/options.html#output-settings

Just a suggestion... could creating an LLM friendly version of the docs and making a custom GPT available to answer questions like this reduce the question volume?

https://aider.chat/docs/troubleshooting/support.html

Bump.

Thanks for trying aider and filing this issue. This doc may be helpful:

https://aider.chat/docs/config/options.html#output-settings

Excuse me but what option in this doc changes green horizontal line color?

@joihn Hi, did you successfully change the color?

Sorry for my lack of response in the past few weeks.
No, I did not manage, I also did not find it in the doc.

@joihn  It's a shame but thanks for your reply.

--user-input-color controls the line color.

@paul-gauthier Nice! I finally could change the line color. Thank you so much👍


App gets messed up with Dark Mode enabled devices.

@istiakshihab please may i fix this issue?

@tanvi2508


Status of this project

Hi,
I see there is no new update for 9 months. Will it be continue in near future ?

Would be nice to have some update for sure. Do you need any help, guys?

We will pick up work again on this in early 2019. Currently focused in on Cosmos-SDK and Tendermint so we can launch the Cosmos Hub.

Great, let me know if you need testers or any kind of help.

The repo is being revived by Swishlabs, see this announcement and this PR. Stay tuned for an updated README and more information


.find NFT detail page

.find NFT detail page.
Grant category
Developer tools / services
Description
If you want to .find information about an NFT #OnFlow right now you have some options.

The origin site of that NFT
A Block explorer like flowscan/flow-view-source
View the item in BloctoApp/Lilico. If you use that wallet and if the NFT is supported

Many origin sites mix off-chain data in their display and it is hard for a user to know if an asset they have purchased has truly been minted.
This grant aims to make such a page that will have a content addressable URL that is easy to remember and link.
The url would be something like:
find.xyz/0x886f3aeaf848c535/Flovatar/95
find.xyz/address or find name/<nft alias from Alchemy/nft registry>/
Problem statement
A block explorer is a technical tool for tech-savvy users that will give them a detailed overview of what is going on in a language that is not comfortable to many people.
Displaying NFTs inside your own wallet has some merit, but what if others want to verify what you have/own?
For a normal user, there are no good options for independent verification and display of an NFT.
Proposed solution
At .find each NFT will have its own page that can be reached in a content addressable/shareable way. No login will be required and no .find name is needed. Although the link would be prettier/easier to remember if you have a .find name.
The page will show information about this NFT from as many sources as possible and package this up into a "normie" readable way.
Information displayed:

Any known View that is exposed from this resource using the Metadata Standard will be displayed
Any not-known view will be shown in an expandable way as pure JSON
Any scrapable history of that NFT.

Verification:
.find will try to judge the authenticity and strength of the NFT and the origin project it comes from using

number of transactions
age
flowverse metrics
other factors as they become clearer

Fetching information:
We will try to fetch the information using the onChain NFT/Alchemy registry
We will fall back to alchemy API for TopShot and some assets that needs to be enriched. Or use the graphql api to fetch those.
Use flowgraph to show NFT purchase history for this NFT
Integrations:
.find will strive to integrate as many other service-level solutions #OnFlow as possible. At this moment these include

allow sending this NFT as a gift to another user: this feature will let the user know if there are royalties attached to the NFT and prompt the user to compensate the royalty holder if the user wants to.
schwap.io: create a schwap with this item in it
flowty.io:  create a loan with this NFT as collateral
display if this NFT is listed in flowty
allow listing the NFT for sale/auction at the .find market
ist all known marketplaces that sell this NFT, for blocto/rarible it is very hard to know where it is listed because of the nature of NFTStorefront

Impact
In our eyes, this offers a huge benefit to the flow ecosystem. There will be a place where everybody can view all the data about an NFT that is stored #OnChain and verify its authenticity. The web3 space on ETH is haunted by scams and this is a tool that could inform users in a simple and trusted way to help avoid that.
We are committed to develop tools and feature sets that will enable and equip end-users to make informed decisions and improve user experience across all projects that engage.
Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - Discovery
- Agree approach with the projects below. - Review other available services/projects #onFlow. - create report of viable integrations
1 week
-
2,000

2 - Integration
As a minimum we will integrate: - schwap.io: create a schwap with this item in it - flowty.io:  create a loan with this NFT as collateral - display if this NFT is listed in flowt - allow listing the NFT for sale/auction at the .find market- List all known marketplaces that sell this NFT, for blocto/rarible it is very hard to know where it is listed because of the nature of NFTStorefront
2 weeks
-
10,000

3 - Front end design
Develop the front end to show this information in a user friendly way. In addition to the current available information on .find. We will add:  - Any known View that is exposed from this resource using the Metadata Standard will be displayed - Any not-known view will be shown in an expandable way as pure JSON - Any scrapable history of that NFT.
2 weeks
-
8,000

4 - Ungate access
Make the changes needed to the find site to enable users without a find address to become searchable
1 day
-
1,000

Team

Name
Role
Bio
Contact

Bjarte Karlsen
CTO
Making sure that the humans at .find understand the machine way
<EMAIL_ADDRESS>

Christian Miles
CEO
Making sure the humans at .find talk to each other and make things happen
<EMAIL_ADDRESS>

Milestone completion

[ ] Discovery (ongoing)
[ ] Integration
[ ] Front end design
[ ] Ungate access

Hey @Christian-findonflow - we're excited about this proposal. Could you please add a few more details and break out the work into more milestones? If there are any integrations, we'd suggest we cover these in an "adoption milestone".
Feel free to reach out to me on discord if you have further questions (alx-flw.find#6198)

Hey @alxflw thanks for the feedback. I have been off the last couple of days and heading to NYC Saturday but will endeavour to get these changes made. This proposal excites us too, a lot. We feel there are a lot of possibilities here both now and in the future.

thanks @Christian-findonflow! please let me know when you finished the updates on the milestones, so we can review 🙏

@alxflw please see latest updates. Let me know if you needed anything else?

hey @Christian-findonflow, this grant was accepted! 🚀
There will also be an NFT catalog soon (self service NFT collection listing) and it would be great if you could integrate with that.
I'll follow up with you with next steps!

Thanks alex, this is great news! The team are onto this already. 🔥

What's the status on this one @Christian-findonflow?


267 update telemetry proto

This PR introduces testing for gRPC streams, which is a bit more tricky than unary RPC. In order to test streams, I am creating an in-process grpc server and use a mock to capture the position_callback_t callback called when the user subscribes to the position data.
Fixes #267.

@julianoes @shakthi-prashanth-m: I am not sure what I should change more in this PR? :-)