Issue in index type inference with lookup type

TypeScript Version:  2.1.4
Code
function func<T>() {
  const key: { [key: string]: number}[keyof T] = 1;
  return key;
}

Expected behavior:
This should be correct typescript code.
{ [key: string]: number}[keyof T] type should be infered to number.
Actual behavior:
error TS2322: Type '1' is not assignable to type '{ [key: string]: number; }[keyof T]'.

This was my misunderstanding.
Sorry.


Is there a working autopictureinpicture sample?

There's a Auto Picture-in-Picture Sample page but it's not currently working (I'm on Chrome 81.0.4044.129 (Official Build) (64-bit)). Was this feature removed or am I missing something?

Tried on Chromium 96.0.4661.0. Still not working.

@guest271314 Did you enable chrome://flags/#enable-experimental-web-platform-features?

And you installed it as a PWA?

Yes. Even included the new id that was warned about at console. The PiP window does not automatically launch. I tried pictureInPicture as the specification uses and the pictureinpicture attribute already in this repository. Does the code do what it is supposed to on your machine? If so, can you create a screen capture video of it working as intended?

It works great for me on macOS. I've installed the PWA, launched it, saw my camera feed, minimized the PWA window, and the PiP window auto magically opened.
See https://developer.chrome.com/blog/media-updates-in-chrome-73/#auto-pip

Not working on Linux. Even when

minimized the PWA window

happens.

Full code used and screen capture video
autopip.zip

Same result. PiP window does not auto launch. This warning appears at DevTools
manifest.json:1 Manifest: property 'scope' ignored. Start url should be within scope of scope URL.

It looks like your PWA window is not minimized from the screen capture you've shared. Can you try again?

I am not sure what you mean by

minimized the PWA window

and

It looks like your PWA window is not minimized

?
I tried that, too, on my own.
How is a minimized window relevant to PiP window launching automatically?

Clicking the minimize [_] window button forces the page visibility event to fire. That's what's PiP autopicture uses.
In your screenshot, the window is not minimized. It is small ;)
Click the [_] button on the left of the [+] button.

Clicking the minimize [_] window button forces the page visibility event to fire. That's what's PiP autopicture uses.
In your screenshot, the window is not minimized. It is small ;) Click the [_] button on the left of the [+] button.

Well, that is not "automatic". That is in response to user action. What you wrote needs to be in the specification and instructions here. And, again, there is nothing "automatic" about that, just substituting one click for another. I might as well just click the PiP control.

I suspect this is a Linux specific issue as it works great on macOS for me. Maybe the "screen occlusion" feature did not launch on Linux. I'm not sure.
See the video on https://developer.chrome.com/blog/media-updates-in-chrome-73/#auto-pip It still works like that for me.
Alt-tab, screen occlusion, minimized windows are actions that force page visibility to change.
Spec says: https://www.w3.org/TR/picture-in-picture/#auto-pip

Some pages may want to automatically enter and leave Picture-in-Picture for a video element; for example, video meeting web apps would benefit from some automatic Picture-in-Picture behavior when the user switches back and forth between the web app and other applications/tabs.

I think we're good don't you think?

I think we're good don't you think?

No.
You supplied specific instructions for user action, where without those instructions I would not have learned that on my own without testing hundreds if not thousands of times.
And as I said, that is by no means "automatic". That attribute name needs to be changed or actually be automatic, without user action, to avoid false advertising.

You supplied specific instructions for user action, where without those instructions I would not have learned that on my own without testing hundreds if not thousands of times.

Like I said, this issue seems specific to Linux. On working platforms, it works out of the box, without minimizing the window. Window simply has to be occluded.

And as I said, that is by no means "automatic". That attribute name needs to be changed or actually be automatic, without user action, to avoid false advertising.

How would you call it?

On working platforms, it works out of the box, without minimizing the window. Window simply has to be occluded.

All of those details need to be clearly documented in the specification.

How would you call it?

From my perspective it is definitely not "automatic" by any stretch. I is no different from clicking the PiP control on the media element or calling requestPictureInPicture() based on user action.
I expected literal "automatic", not conditional changes based on further user gestures.
The procedure needs to be explained, preferably in the specification, definitely here, else there is no way for users to divine the specific instructions you posted.

On working platforms, it works out of the box, without minimizing the window. Window simply has to be occluded.

All of those details need to be clearly documented in the specification.

I kindly disagree.
Specification text looks good to me. It uses page visibility API events.

How would you call it?

From my perspective it is definitely not "automatic" by any stretch. I is no different from clicking the PiP control on the media element or calling requestPictureInPicture() based on user action.

It's not true. Switching from a PWA window to another app may is not a user gesture in the spec world.
Do you mind filing a bug at crbug.com/new to explain that page visibility event is not fired when page becomes hidden?

Well, you asked, and I gave my perspective.
It is definitely not "automatic".
What I expect by the naming convention is very simple: I get link to a site where PiP window is literally automatically launched, without any further action.

Do you mind filing a bug at crbug.com/new to explain that page visibility event is not fired when page becomes hidden?

I have filed issues re PiP in the past and been banned from the specification issue, re maximum PiP window size, which is certainly Chromium-specific.
I will file the issue anyway explaining what I consider should occur.
This is not "automatic", no matter how it is trying to be massaged or colored as such.

User gesture meaning what you advised for PiP to happen, minimize the PWA window. I am not sure how you can color that "automatic"?

It is not special or even needed. It does not do anything requestPictureInPicture() does not do, so I am not sure why it is even being specified - since it is not "automatic". If you actually make it automatic then keep the name. Else, it can actually be removed from the specification, again, to avoid false advertising.

Perhaps 'minimizedPictureInPicture'?

Or 'minimizedWindowPictureInPicture', 'occludedWindowPictureInPicture'. 'automatic' on its own is not what is occurring and should cease and desist being advertised as such.

@beaufortfrancois  https://bugs.chromium.org/p/chromium/issues/detail?id=1256603

Thank you really much @guest271314!
I've pinged some folks at https://bugs.chromium.org/p/chromium/issues/detail?id=1256603#c3 and was able to reproduce with a small test case.


wp_calculate_image_srcset fails to rewrite default image

Since the processing in foreach ($image_meta['sizes'] as $key => $meta) only uses the sizes array for replacement, if the default (unsized) image is in the source array, it remains un-replaced.
https://github.com/wpCloud/wp-stateless/blob/v2.1/lib/classes/class-bootstrap.php#L232
Some debug of the $sources array before and after replacement:
Before wp_calculate_image_srcset
784 "https://site.com/wp-content/uploads/..../image.png" "w" 784
300 "https://site.com/wp-content/uploads/..../image-300x113.png" "w" 300
768 "https://site.com/wp-content/uploads/..../image-768x289.png" "w" 768
140 "https://site.com/wp-content/uploads/..../image-140x53.png" "w" 140
340 "https://site.com/wp-content/uploads/..../image-340x128.png" "w" 340
170 "https://site.com/wp-content/uploads/..../image-170x64.png" "w" 170

After wp_calculate_image_srcset
784 "https://site.com/wp-content/uploads/..../image.png" "w" 784
300 "https://storage.googleapis.com/..../image-300x170.png" "w" 300
768 "https://storage.googleapis.com/..../image-768x289.png" "w" 768
140 "https://storage.googleapis.com/..../image-140x53.png" "w" 140
340 "https://storage.googleapis.com/..../image-340x128.png" "w" 340
170 "https://storage.googleapis.com/..../image-170x64.png" "w" 170

@aschmoe thanks for investigating. We'll take a look!

@aschmoe @ewsopp Now wp_calculate_image_srcset will rewrite default image also.

@aschmoe would you mind testing this with the v2.1 branch? You can download it directly from https://github.com/wpCloud/wp-stateless/archive/v2.1.zip
Please let us know! :)

@ewsopp thank you, issue appears to be fixed... as you already know ;)
Sorry about the tardy response.


[Cloud Firestore] doesn't work with IOS (get stuck on pod install gRPC-Core)

Describe the bug
The issue is that the pod install process gets stuck on Installing gRPC-Core (1.28.0)
I have tried to isolate the problem and found out that cloud_firestore: ^0.13.5 is the problem
To Reproduce
Steps to reproduce the behavior:

run flutter run
got stuck on Running pod install...
cd ios/
run pod install got stuck on Installing gRPC-Core (1.28.0)

Expected behavior
To run the project with the firebase plugin
Additional context
This the pubscpec.yaml
name: homemanagement
description: A new Flutter application.

publish_to: 'none'

version: 1.0.0+1

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  firebase_analytics: ^5.0.2
  cloud_firestore: ^0.13.5
  firebase_storage: ^3.1.5
  firebase: ^7.3.0
  rxdart: ^0.24.0

  cupertino_icons: ^0.1.3

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

Podfile:
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

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

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

def parse_KV_file(file, separator='=')
  file_abs_path = File.expand_path(file)
  if !File.exists? file_abs_path
    return [];
  end
  generated_key_values = {}
  skip_line_start_symbols = ["#", "/"]
  File.foreach(file_abs_path) do |line|
    next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
    plugin = line.split(pattern=separator)
    if plugin.length == 2
      podname = plugin[0].strip()
      path = plugin[1].strip()
      podpath = File.expand_path("#{path}", file_abs_path)
      generated_key_values[podname] = podpath
    else
      puts "Invalid plugin specification: #{line}"
    end
  end
  generated_key_values
end

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  # Flutter Pod

  copied_flutter_dir = File.join(__dir__, 'Flutter')
  copied_framework_path = File.join(copied_flutter_dir, 'Flutter.framework')
  copied_podspec_path = File.join(copied_flutter_dir, 'Flutter.podspec')
  unless File.exist?(copied_framework_path) && File.exist?(copied_podspec_path)
    # Copy Flutter.framework and Flutter.podspec to Flutter/ to have something to link against if the xcode backend script has not run yet.
    # That script will copy the correct debug/profile/release version of the framework based on the currently selected Xcode configuration.
    # CocoaPods will not embed the framework on pod install (before any build phases can generate) if the dylib does not exist.

    generated_xcode_build_settings_path = File.join(copied_flutter_dir, 'Generated.xcconfig')
    unless File.exist?(generated_xcode_build_settings_path)
      raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"
    end
    generated_xcode_build_settings = parse_KV_file(generated_xcode_build_settings_path)
    cached_framework_dir = generated_xcode_build_settings['FLUTTER_FRAMEWORK_DIR'];

    unless File.exist?(copied_framework_path)
      FileUtils.cp_r(File.join(cached_framework_dir, 'Flutter.framework'), copied_flutter_dir)
    end
    unless File.exist?(copied_podspec_path)
      FileUtils.cp(File.join(cached_framework_dir, 'Flutter.podspec'), copied_flutter_dir)
    end
  end

  # Keep pod path relative so it can be checked into Podfile.lock.
  pod 'Flutter', :path => 'Flutter'

  # Plugin Pods

  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.each do |name, path|
    symlink = File.join('.symlinks', 'plugins', name)
    File.symlink(path, symlink)
    pod name, :path => File.join(symlink, 'ios')
  end
end

# Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

Flutter doctor
Run flutter doctor and paste the output below:
[✓] Flutter (Channel stable, v1.17.0, on Mac OS X 10.15.4 19E266, locale en-IL)
    • Flutter version 1.17.0 at /Users/yuri.abramov/Flutter/flutter
    • Framework revision e6b34c2b5c (9 days ago), 2020-05-02 11:39:18 -0700
    • Engine revision 540786dd51
    • Dart version 2.8.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/yuri.abramov/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Users/yuri.abramov/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/192.6392135/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Android Studio (version 3.6)
    • Android Studio at /Users/yuri.abramov/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/192.6392135/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.1.1)
    • IntelliJ at /Users/yuri.abramov/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 44.0.3
    • Dart plugin version 193.6911.31

[✓] Connected device (1 available)
    • iPhone 11 Pro Max • 192CA87B-1416-449E-9569-91BC1FB0325F • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)

• No issues found!
Process finished with exit code 0

Already tried:
flutter pub cache repair   and pod install
pod update Firebase/Firestore

Hi @yuriGett
Not able to reproduce this issue on pod version 1.9.1
Can you please try some packages in a new project?
Thank you

Hi @TahaTesser just tried on a new project and facing the same issue..

same here, any solution?

any solutions?

After couple hours of pod installation, it finally worked. I guess we have to be very very patient...

My solution was to download the Pod gRPC-Core from another project on Github and manually to add it to my Pods directory and then to run pod upgrade and pod install in ios directory

the cloning of the repositories when installing gRCP-Core seems to be endless but when running the Pod install verbose it is actually getting somewhere. This really is dependency hell.
Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/abseil-cpp'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/benchmark'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/bloaty'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/boringssl-with-bazel'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/cares/cares'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/envoy-api'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/gflags'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/googleapis'...       Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/googletest'...      Cloning into '/private/var/folders/0g/_zjqscqx6cl5ggymnnstyhkh0000gn/T/d20200524-50567-g2gos8/third_party/libuv'...

Okay got it to work by downgrading to an older version and now being able to build. But I am getting build times like 210.6s or 218.6s! This is seriously very bad.

Facing same issue. @KrystofM which version did you use.

I was having the same issue on a new project. But after getting stuck on gRPC-Core install I waited around 5-10 minutes and then it proceed with pod install. Probably it's a server issue.

I've waited and still am waiting it's been more than half an hour its still stuck on Run POD

IT WORKED LOL. BUT IT ONLY TOOK 69.7 MINUTES :D
Imagine 1hr and 9 minutes for a single POD install. They need to fix it!!

I had a similar issue where pod install would fail on gRPC-C++ because it couldn't include openssl. Adding the below to the Podfile to manually lock the version of BoringSSL_GRPC seemed to fix things up for me for the time being. Having other issues building right now, so if it turns out everything crashes and burns when running in-app, I'll amend this.
# lock the version of `BoringSSL-GRPC` so installing gRPC-C++ via cloud_firestore doesn't fail
pod 'BoringSSL-GRPC', '0.0.3'

This issue led me in the right direction: https://github.com/grpc/grpc/issues/16821

I had the same issue and this article helped.
Also be patient in the pod install as it could take like 15mins or more sometimes when you come across this issue.

Hey all, as part of our on-going work for #2582, the project structure/setup for iOS & MacOS in our Firebase Firestore rework (#2913) has been improved which should help with this along with using the new pre-compiled Firestore binaries ti improve build times.
The rework has now been merged into master. We'll look at publishing some prereleases in the next few days. Thank you


[web] Flutter Web appears frequently, Error: Bad state: Future already completed

I'm using an Mac computer, Chrome doesn't have any plugins, and the computer doesn't have any firewall, how can we solve this problem.
Now this error occurs every time I debug, how to shield this error.

Hi @Aaron009
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Adding navigation bar to Error 404 page.

@wrussell1999 right now, the error 404 page looks like a dead end. Once you end up on the 404 page, you have to click on the back button in your browser which is inefficient.
Current 404 page:

Adding a navbar kind of thing to the 404 page will allow the user to travel back to some other existing page.

or we can add a timed redirect to the homepage?

That can be implemented too I guess. My team is already working on a navbar thing and we just have to include it in the 404 page


Actually install the package inside the Dockerfile so the UI works

I saw a Dockerfile and assumed that would be the easiest way to get up-and-running with development, but it turns out there was more work involved.  This PR actually installs the dependencies and the package and compiles the js so the UI works.

@andrewmchen No worries on the nit.  Better now?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@624ea79). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #17   +/-   ##
========================================
  Coverage          ?   69.6%
========================================
  Files             ?      44
  Lines             ?    2527
  Branches          ?       0
========================================
  Hits              ?    1759
  Misses            ?     768
  Partials          ?       0

Continue to review full report at Codecov.

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

LGTM now :) thanks for your contribution.


Removed BlueGene Toolchain files

Toolchain files could be removed, because Todd pushed them upstream to CMake 3.2

As the minimum required CMake version is 2.8 and the files have been included in 3.2, the files should be kept in the repository, until the CMake minimum required version gets increased.


Feature Request - Update Catalogs automatically on a git commit

Rancher versions:
rancher/server: 1.6.2
rancher/agent: 1.2.2
Problem:
At the moment, we need to refresh the catalogs manually whenever we update our git repo

Workaround (have not checked yet):
Have a git hook which makes a curl call to refresh the catalog.

It updates every five minutes.

@vincent99 Can we tweak the parameter which does that?


⚠ Secret Website 3 has degraded performance

In 067d0bd, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3954 ms

Resolved: Secret Website 3 performance has improved in 23ffafc.


Simple slide and fade animation

Hello,
First of all, thanks for this fantastic library, I really love how easy to use it is.
However, I have noted that the documentation is a bit targeted on people that is already familiar with velocity (which is not my case).
It took me a while before I figured out how to create a simple slide and fade animation. This means, at the same time something is sliding down to its full height, it fades from opacity 0 to one.
At te end I found that the easiest solution is to use a VelocityComponent to wrap a VelocityTransitionGroup
<VelocityComponent animation={{ opacity: this.state.showForm ? 1 : 0 }} duration={500}>
            <VelocityTransitionGroup component="div"
                enter={{animation: 'slideDown', duration:500}}
                leave={{animation: 'slideUp', duration:500}}>
                { this.state.showForm && <CreateUser onSubmit={this.props.createUser}/> }
              </VelocityTransitionGroup>
            </VelocityComponent>

I was looking at the crossfade example, but it is too complex for my simple usage scenario.  I tried to emulate something similar putting two transition group components together, but that didn't worked.
If there is a better way to accomplish this , by registering a velocity animation for example, I would love to hear about it.
Again, many thanks.

Yeah, this is a bit complicated because slideDown / slideUp are custom animations in Velocity (in order to handle the height issue) so they can't be easily composed with the CSS animations.
I think what you have is reasonable.


wrong date show

It gives me previous data like if i lick on 6/6/2017 it gives me 6/5/2017 date.

https://github.com/wdullaer/MaterialDateTimePicker#why-does-the-datepickerdialog-return-the-selected-month--1


Configure cache backend for verifier

Allow user to pass in a requests-cache backend to verify function as an optional argument.

Merged.


03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "<IP_ADDRESS>/32",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::3/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::4/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::5/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::6/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::7/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::8/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::9/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::10/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::11/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::12/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::13/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::14/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::15/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::16/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::17/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::18/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::19/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::20/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::21/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::22/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::23/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::24/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::25/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::26/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::27/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::28/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::29/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::30/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::31/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::32/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::33/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::34/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::35/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::36/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::37/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::38/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::39/128",
03:03:53.212 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::40/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::41/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::42/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::43/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::44/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::45/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::46/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::47/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::48/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::49/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::50/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::51/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::52/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::53/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::54/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::55/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::56/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::57/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::58/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::59/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::60/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::61/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2607:ff68:107::62/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:2:d0::fa3:e001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:1:d0::e54:a001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2604:a880:800:10::4e6:f001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2604:a880:cad:d0::122:7001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:3:d0::33e:4001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f16:775:3a01:70d6:601a:1eb5:dbb9/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f11:56a:9000:23:651b:dac0:9be4/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:3:d0::44:f001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:0:1010::2b:b001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a03:b0c0:1:d0::22:5001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2604:a880:400:d0::4f:3001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2400:6180:0:d0::16:d001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2604:a880:cad:d0::18:f001/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f18:179:f900:88b2:b3d:e487:e2f4/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f18:179:f900:1977:916:ee3d:711e/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2a05:d014:1815:3400:588a:ee17:65c3:3b09/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f16:775:3a00:b729:c226:2737:fe49/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f1c:edf:1401:2124:652e:c5df:f89b/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f16:775:3a00:acb7:ec84:11f2:2bf4/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f16:775:3a00:66b2:530c:e48:573e/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f18:179:f900:803:c81e:6059:b78f/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:               + "2600:1f18:179:f900:473d:7e21:19be:3b9d/128",
03:03:53.213 STDOUT [cloudflare/access] tofu:             ]
03:03:53.213 STDOUT [cloudflare/access] tofu:         }
03:03:53.213 STDOUT [cloudflare/access] tofu:     }
03:03:53.215 STDOUT [cloudflare/access] tofu: Plan: 5 to add, 0 to change, 5 to destroy.
03:03:53.215 STDOUT [cloudflare/access] tofu:
03:03:53.414 STDOUT [uptime-robot/otaru] tofu: No changes.  Your infrastructure matches the configuration.
03:03:54.785 STDOUT [aws/jung2bot/dynamodb] tofu:
03:03:54.785 STDOUT [aws/jung2bot/dynamodb] tofu: OpenTofu has compared your real infrastructure against your configuration and
03:03:54.785 STDOUT [aws/jung2bot/dynamodb] tofu: found no differences, so no changes are needed.
03:03:54.812 STDOUT [aws/jung2bot-dev/sqs] tofu: No changes. Your infrastructure matches the configuration.
03:03:54.812 STDOUT [aws/jung2bot-dev/sqs] tofu:
03:03:54.812 STDOUT [aws/jung2bot-dev/sqs] tofu: OpenTofu has compared your real infrastructure against your configuration and
03:03:54.812 STDOUT [aws/jung2bot-dev/sqs] tofu: found no differences, so no changes are needed.
03:03:54.930 STDOUT [aws/jung2bot-dev/dynamodb] tofu: No changes. Your infrastructure matches the configuration.
03:03:54.930 STDOUT [aws/jung2bot-dev/dynamodb] tofu:
03:03:54.930 STDOUT [aws/jung2bot-dev/dynamodb] tofu: OpenTofu has compared your real infrastructure against your configuration and
03:03:54.930 STDOUT [aws/jung2bot-dev/dynamodb] tofu: found no differences, so no changes are needed.
03:03:55.002 STDOUT [aws/jung2bot/sqs] tofu: No changes. Your infrastructure matches the configuration.
03:03:55.002 STDOUT [aws/jung2bot/sqs] tofu: OpenTofu has compared your real infrastructure against your configuration and
03:03:55.002 STDOUT [aws/jung2bot/sqs] tofu: found no differences, so no changes are needed.
03:03:55.332 STDOUT [cloudflare/dns] tofu:
03:03:55.332 STDOUT [cloudflare/dns] tofu: Successfully configured the backend "s3"! OpenTofu will automatically
03:03:55.332 STDOUT [cloudflare/dns] tofu: use this backend unless the backend configuration changes.
03:03:55.630 STDOUT [cloudflare/dns] tofu: Initializing provider plugins...
03:03:55.630 STDOUT [cloudflare/dns] tofu: - Reusing previous version of hashicorp/aws from the dependency lock file
03:03:55.712 STDOUT [cloudflare/dns] tofu: - Reusing previous version of backblaze/b2 from the dependency lock file
03:03:55.744 STDOUT [cloudflare/dns] tofu: - Reusing previous version of cloudflare/cloudflare from the dependency lock file
03:03:55.777 STDOUT [cloudflare/dns] tofu: - Reusing previous version of integrations../../.. from the dependency lock file
03:03:55.804 STDOUT [cloudflare/dns] tofu: - Reusing previous version of vexxhost/uptimerobot from the dependency lock file
03:03:56.146 STDOUT [cloudflare/dns] tofu: - Installing hashicorp/aws v5.67.0...
03:03:56.288 STDOUT [b2/bucket] tofu: No changes. Your infrastructure matches the configuration.
03:03:56.288 STDOUT [b2/bucket] tofu: OpenTofu has compared your real infrastructure against your configuration and
03:03:56.288 STDOUT [b2/bucket] tofu: found no differences, so no changes are needed.
03:04:02.266 STDOUT [cloudflare/dns] tofu: - Installed hashicorp/aws v5.67.0 (signed, key ID 0C0AF313E5FD9F80)
03:04:02.576 STDOUT [cloudflare/dns] tofu: - Installing backblaze/b2 v0.8.12...
03:04:03.633 STDOUT [cloudflare/dns] tofu: - Installed backblaze/b2 v0.8.12. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:04:03.938 STDOUT [cloudflare/dns] tofu: - Installing cloudflare/cloudflare v4.42.0...
03:04:04.643 STDOUT [cloudflare/dns] tofu: - Installed cloudflare/cloudflare v4.42.0 (signed, key ID C76001609EE3B136)
03:04:04.922 STDOUT [cloudflare/dns] tofu: - Installing integrations../../.. v6.2.2...
03:04:05.390 STDOUT [cloudflare/dns] tofu: - Installed integrations../../.. v6.2.2 (signed, key ID 38027F80D7FD5FB2)
03:04:05.698 STDOUT [cloudflare/dns] tofu: - Installing vexxhost/uptimerobot v0.8.2...
03:04:06.083 STDOUT [cloudflare/dns] tofu: - Installed vexxhost/uptimerobot v0.8.2. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:04:06.083 STDOUT [cloudflare/dns] tofu: Providers are signed by their developers.
03:04:06.083 STDOUT [cloudflare/dns] tofu: If you'd like to know more about provider signing, you can read about it here:
03:04:06.083 STDOUT [cloudflare/dns] tofu: https://opentofu.org/docs/cli/plugins/signing/
03:04:06.083 STDOUT [cloudflare/dns] tofu: OpenTofu has made some changes to the provider dependency selections recorded
03:04:06.083 STDOUT [cloudflare/dns] tofu: in the .terraform.lock.hcl file. Review those changes and commit them to your
03:04:06.083 STDOUT [cloudflare/dns] tofu: version control system if they represent changes you intended to make.
03:04:06.084 STDOUT [cloudflare/dns] tofu: OpenTofu has been successfully initialized!
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["longhorn_internal"]: Refreshing state... [id=9d9e7849509ddd1ca1420bfb93085ddb]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["projectsend_internal"]: Refreshing state... [id=06419344d002dd09405e9ef062afae8d]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["adguard_internal"]: Refreshing state... [id=5803590e9218027a34aae666383f8211]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["kiali_internal"]: Refreshing state... [id=3e29d0bc6567b4c0fecd6db58e432160]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["home_assistant_internal"]: Refreshing state... [id=0450593da9fcf9f32802e5152f53c349]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["jellyfin_internal"]: Refreshing state... [id=62786f77078b02d784342427605ba9e9]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.public_record: Refreshing state... [id=82e3f3e0f604222d51b67e5306616889]
03:04:09.435 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["cyberchef_internal"]: Refreshing state... [id=0efbeb64c2b70ae3ac725f886bab27dc]
03:04:09.437 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["argocd_internal"]: Refreshing state... [id=ad2633b9ce86a1786416dd851cb5c4d3]
03:04:09.438 STDOUT [cloudflare/dns] tofu: cloudflare_record.internal_record["sftpgo_internal"]: Refreshing state... [id=d53e66b848b3967bd5a9885eb2c8e08c]
03:04:12.021 STDOUT [cloudflare/dns] tofu: OpenTofu used the selected providers to generate the following execution
03:04:12.021 STDOUT [cloudflare/dns] tofu: plan. Resource actions are indicated with the following symbols:
03:04:12.021 STDOUT [cloudflare/dns] tofu:   + create
03:04:12.021 STDOUT [cloudflare/dns] tofu:   ~ update in-place
03:04:12.021 STDOUT [cloudflare/dns] tofu:   - destroy
03:04:12.022 STDOUT [cloudflare/dns] tofu: OpenTofu will perform the following actions:
03:04:12.022 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["adguard_internal"] will be destroyed
03:04:12.022 STDOUT [cloudflare/dns] tofu:   # (because key ["adguard_internal"] is not in for_each map)
03:04:12.022 STDOUT [cloudflare/dns] tofu:   - resource "cloudflare_record" "internal_record" {
03:04:12.022 STDOUT [cloudflare/dns] tofu:       - allow_overwrite = false -> null
03:04:12.022 STDOUT [cloudflare/dns] tofu:       - created_on      = "2023-10-14T19:43:52.723504Z" -> null
03:04:12.022 STDOUT [cloudflare/dns] tofu:       - hostname        = "adguard.internal.siutsin.com" -> null
03:04:12.022 STDOUT [cloudflare/dns] tofu:       - id              = "5803590e9218027a34aae666383f8211" -> null
03:04:12.022 STDOUT [cloudflare/dns] tofu:       - metadata        = {
03:04:12.022 STDOUT [cloudflare/dns] tofu:           - "auto_added"             = "false"
03:04:12.023 STDOUT [cloudflare/dns] tofu:           - "managed_by_apps"        = "false"
03:04:12.023 STDOUT [cloudflare/dns] tofu:           - "managed_by_argo_tunnel" = "false"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         } -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - modified_on     = "2023-10-14T19:43:52.723504Z" -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - name            = "adguard.internal" -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - proxiable       = false -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - proxied         = false -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - tags            = [] -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - ttl             = 1 -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - type            = "A" -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:       - zone_id         = (sensitive value) -> null
03:04:12.023 STDOUT [cloudflare/dns] tofu:     }
03:04:12.023 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["argocd_internal"] will be updated in-place
03:04:12.023 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.023 STDOUT [cloudflare/dns] tofu:         id              = "ad2633b9ce86a1786416dd851cb5c4d3"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         name            = "argocd.internal"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.023 STDOUT [cloudflare/dns] tofu:     }
03:04:12.023 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["cyberchef_internal"] will be updated in-place
03:04:12.023 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.023 STDOUT [cloudflare/dns] tofu:         id              = "0efbeb64c2b70ae3ac725f886bab27dc"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         name            = "cyberchef.internal"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.023 STDOUT [cloudflare/dns] tofu:     }
03:04:12.023 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["home_assistant_internal"] will be updated in-place
03:04:12.023 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.023 STDOUT [cloudflare/dns] tofu:         id              = "0450593da9fcf9f32802e5152f53c349"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         name            = "home-assistant.internal"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.023 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.023 STDOUT [cloudflare/dns] tofu:     }
03:04:12.023 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["hubble_ui_internal"] will be created
03:04:12.023 STDOUT [cloudflare/dns] tofu:   + resource "cloudflare_record" "internal_record" {
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + allow_overwrite = false
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + content         = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + created_on      = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + hostname        = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + id              = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + metadata        = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + modified_on     = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + name            = "hubble-ui.internal"
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + proxiable       = (known after apply)
03:04:12.023 STDOUT [cloudflare/dns] tofu:       + proxied         = false
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + ttl             = 1
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + type            = "A"
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + zone_id         = (sensitive value)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["jellyfin_internal"] will be updated in-place
03:04:12.024 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:         id              = "62786f77078b02d784342427605ba9e9"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         name            = "jellyfin.internal"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["kiali_internal"] will be destroyed
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # (because key ["kiali_internal"] is not in for_each map)
03:04:12.024 STDOUT [cloudflare/dns] tofu:   - resource "cloudflare_record" "internal_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - allow_overwrite = false -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - created_on      = "2023-10-14T19:43:52.95512Z" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - hostname        = "kiali.internal.siutsin.com" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - id              = "3e29d0bc6567b4c0fecd6db58e432160" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - metadata        = {
03:04:12.024 STDOUT [cloudflare/dns] tofu:           - "auto_added"             = "false"
03:04:12.024 STDOUT [cloudflare/dns] tofu:           - "managed_by_apps"        = "false"
03:04:12.024 STDOUT [cloudflare/dns] tofu:           - "managed_by_argo_tunnel" = "false"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         } -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - modified_on     = "2023-10-14T19:43:52.95512Z" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - name            = "kiali.internal" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - proxiable       = false -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - proxied         = false -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - tags            = [] -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - ttl             = 1 -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - type            = "A" -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:       - zone_id         = (sensitive value) -> null
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["longhorn_internal"] will be updated in-place
03:04:12.024 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:         id              = "9d9e7849509ddd1ca1420bfb93085ddb"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         name            = "longhorn.internal"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["projectsend_internal"] will be updated in-place
03:04:12.024 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:         id              = "06419344d002dd09405e9ef062afae8d"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         name            = "projectsend.internal"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.internal_record["sftpgo_internal"] will be updated in-place
03:04:12.024 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "internal_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:         id              = "d53e66b848b3967bd5a9885eb2c8e08c"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         name            = "sftpgo.internal"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = "<IP_ADDRESS>"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         # (10 unchanged attributes hidden)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu:   # cloudflare_record.public_record will be updated in-place
03:04:12.024 STDOUT [cloudflare/dns] tofu:   ~ resource "cloudflare_record" "public_record" {
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + allow_overwrite = false
03:04:12.024 STDOUT [cloudflare/dns] tofu:         id              = "82e3f3e0f604222d51b67e5306616889"
03:04:12.024 STDOUT [cloudflare/dns] tofu:         name            = (sensitive value)
03:04:12.024 STDOUT [cloudflare/dns] tofu:         tags            = []
03:04:12.024 STDOUT [cloudflare/dns] tofu:       + value           = (sensitive value)
03:04:12.024 STDOUT [cloudflare/dns] tofu:         # (9 unchanged attributes hidden)
03:04:12.024 STDOUT [cloudflare/dns] tofu:     }
03:04:12.024 STDOUT [cloudflare/dns] tofu: Plan: 1 to add, 8 to change, 2 to destroy.
03:04:12.024 STDOUT [cloudflare/dns] tofu: ╷
03:04:12.024 STDOUT [cloudflare/dns] tofu: │ Warning: Argument is deprecated
03:04:12.024 STDOUT [cloudflare/dns] tofu: │
03:04:12.024 STDOUT [cloudflare/dns] tofu: │   with cloudflare_record.internal_record["argocd_internal"],
03:04:12.024 STDOUT [cloudflare/dns] tofu: │   on 01-record.tf line 8, in resource "cloudflare_record" "internal_record":
03:04:12.024 STDOUT [cloudflare/dns] tofu: │    8:   value   = each.value["value"]
03:04:12.024 STDOUT [cloudflare/dns] tofu: │
03:04:12.024 STDOUT [cloudflare/dns] tofu: │ `value` is deprecated in favour of `content` and will be removed in the
03:04:12.024 STDOUT [cloudflare/dns] tofu: │ next major release.
03:04:12.024 STDOUT [cloudflare/dns] tofu: │
03:04:12.024 STDOUT [cloudflare/dns] tofu: │ (and 8 more similar warnings elsewhere)
03:04:12.024 STDOUT [cloudflare/dns] tofu: ╵


Feature request - Add Energy Saving to functions

Hi!
Thank you for all your work on this plugin, I do however have a feature request :)
Is it possible to expose the 6 different Energy Saving options (Auto, Off, Minimum, Medium, Maximum, Screen Off) as a button or switch to Homekit? I use the Energy Saving function to dim the (OLED) backlight to accommodate the ambient light in the living room. I rather use this option rather than dimming the backlight manually for a couple of reasons:

I've calibrated the TV and I would love to just turn Energy Saving off and get back to the fully calibrated brightness with one button.
When enabled, Energy Saving dims all of the picture modes (SDR, HDR, DV) as opposed to dimming the backlight which only changes the value of the current picture mode.

I currently use a Logitec Harmony with macros to enable/disable Energy Saving, but I would rather user a direct Homekit solution.
Thanks for reading, I do hope it's possible!
Rob
https://user-images.githubusercontent.com/8589665/204784594-60a5cf26-11c6-4e75-88c0-7a8692b34d10.mov

Hi,
unfortunately as far as i know it is not possible to control the Energy Saving options, at least i am not aware of any API endpoints on the TV which control that.
But i think you could use the remoteSequenceButtons to achieve that, you would just need to enter the sequence of remote buttons which needs to be execute to accomplish that.


vtk mesh with boundary patches

I have a conformal mesh consisting of two materials that I can convert to VTK (originally in openFOAM format). I have a vtk file with the 3D mesh (mixed hex and tets) and a vtk file with the boundaries.

I want to be able to use the boundary patches selected and do a similar problem than the one shown in the example 2: linear elasticity on a beam.
Is this supported?
Many thanks!

Hi @XuliaDS, yes I think this should work.
Could you send us this mesh?
Thanks,
Vladimir

Hi !
I've attached the files. I think I could also create a vtm file if needed.
mesh.tar.gz
Thanks !!!

Hi @XuliaDS,
These are binary mesh files -- for VTK MFEM currently supports only VTK (ASCII) and VTU (XML) unstructured meshes. See https://mfem.org/mesh-formats/.

apologies...I tried attaching in ascii but the tarball folder is too big.  ( > 25Mb)
Can I send it to you via email ?
Thanks

@XuliaDS
I was able to open it in VisIt and then convert to Legacy ASCII, but no luck, our VTK readers hit some topology errors:
 --> Invalid mesh topology.  Interior quadrilateral face found connecting elements 1116, 106033 and 106182.
 --> Invalid mesh topology.  Interior triangular face found connecting elements 210424, 210429 and 210443.
I tried to comment these verifications out and was able to visualize it in GLVis, but then trying to solve anything simple (ex1) led to segfaults.
Mark @mlstowell added these checks in 2021 and might know exactly what's happening. But otherwise at this point the 3D volumetric mesh is invalid for MFEM.
If you have another mesh or somehow get this fixed, your first test should be to solve ex1 on it, to verify its validity in the MFEM readers. When that works, ex2 is likely will work as well, as long as the boundary attributes are correct.

Ah, thanks for the heads up. The mesh was computed with cfMesh+. If I run the checkMesh utility in openFOAM, I get a pass both in geometry and topology so I presumed it was fine. Obviously it depends on what we define as "PASS"...
I have tried other meshers (tetwild mainly). With tetWild I can edit and give it physical groups directly. Then I run MFEM successfully modifying slightly ex2.py.
If you are interested in adding this option (merging a vtk file with interior elements + boundary patches) into a single mesh file to use with MFEM, I can provide a suitable vtk-mesh split into patches. I'll do it with tetwild and then convert it.
Otherwise, feel free to close this issue and mark as solved.
Again, many thanks!

Sure, If you have it as a valid MFEM mesh I'd be interested to have it. You can upload it here after the issue is closed. Thanks and good luck.

Just to clarify about the error messages: these messages indicate that in the mesh there are more than 2 elements that have the same common face -- this is considered invalid since it mean that at least 2 elements overlap.

In case you are interested, I have created a rather simple mesh: a box split into two materials  and four boundary patches.
box_2mat.tar.gz
Thank you !
Xulia


Invoke-Build with Set-StrictMode -Version [123] Results in Exception

Running
Invoke-Build -Task . -File build.ps1
Results in:
InvokeBuild\5.8.5\Invoke-Build.ps1 : The variable '$_' cannot be retrieved because it has not been set.
When the build file contains:
Set-StrictMode -Version 1
I think the problem is here:
https://github.com/nightroman/Invoke-Build/blob/b4e12f0c8711572ce5b4c063d9ea711d0ff6f401/Invoke-Build.ps1#L63
At this point, there is no session state for Invoke-Build so inevitably, the value of $_ is $null
If I use an alternative variable name for the session state, e.g...
$ROFL = if ($ROFL = $PSCmdlet.SessionState.PSVariable.Get('*')) {if ($ROFL.Description -eq 'IB') {$ROFL.Value}}
New-Variable * -Description IB ([PSCustomObject]@{
	All = [System.Collections.Specialized.OrderedDictionary]([System.StringComparer]::OrdinalIgnoreCase)
	Tasks = [System.Collections.Generic.List[object]]@()
	Errors = [System.Collections.Generic.List[object]]@()
	Warnings = [System.Collections.Generic.List[object]]@()
	Redefined = @()
	Doubles = @()
	Started = [DateTime]::Now
	Elapsed = $null
	Error = 'Invalid arguments.'
	Task = $null
	File = $BuildFile = $PSBoundParameters['File']
	Safe = $PSBoundParameters['Safe']
	Summary = $PSBoundParameters['Summary']
	CD = $OriginalLocation = *Path
	DP = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary
	SP = @{}
	P = $ROFL
	A = 1
	B = 0
	Q = 0
	H = @{}
	EnterBuild = $null
	ExitBuild = $null
	EnterTask = $null
	ExitTask = $null
	EnterJob = $null
	ExitJob = $null
	Header = if ($ROFL) {$ROFL.Header} else {{Write-Build 11 "Task $($args[0])"}}
	Footer = if ($ROFL) {$ROFL.Footer} else {{Write-Build 11 "Done $($args[0]) $($Task.Elapsed)"}}
	Data = @{}
	XBuild = $null
	XCheck = $null
})

... the exception is not thrown.
Simple script to demonstrate:
function test {
    [cmdletbinding()]
    param ()

    $_ = if ($_ = $PSCmdlet.SessionState.PSVariable.Get('*')) {if ($_.Description -eq 'TEST') {$_.Value}}
    $someVar = $_
    return "BrokenWithStrictMode"
}

Set-StrictMode -Version 3
test

"Fixed" script:
function test {
    [cmdletbinding()]
    param ()

    $SomeVar = if ($SomeVar = $PSCmdlet.SessionState.PSVariable.Get('*')) {if ($SomeVar.Description -eq 'TEST') {$SomeVar.Value}}
    return "WORKS"
}

Set-StrictMode -Version 3
test

(1) what is 3 in Set-StrictMode -Version 3? Is this a documented value?
(2) I cannot reproduce the problem. Your script works and prints "BrokenWithStrictMode" as expected.

$_ is assigned in here:
https://github.com/nightroman/Invoke-Build/blob/b4e12f0c8711572ce5b4c063d9ea711d0ff6f401/Invoke-Build.ps1#L45
In this expression $_ is always assigned first, then read.
IB is tested with the Latest strict mode:
https://github.com/nightroman/Invoke-Build/blob/b4e12f0c8711572ce5b4c063d9ea711d0ff6f401/.build.ps1#L27

Some info about the environment I'm testing in
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.19041.1320
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1320
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

I've raised a PR: https://github.com/nightroman/Invoke-Build/pull/191
Yours to do with as you wish, especially given my low level of familiarity with this project. Must admit I'm curious about assigning to $PSItem; is there a reason for using it like this?
Thanks and Happy New Year.

Happy New Year!
I would like to understand what is going on on your side.
When you get this error, what is the full error text?
Could you please also dump the whole $error and see some hints to a different location of the error?

I'm curious about assigning to $PSItem; is there a reason for using it like this?

(1) Yes. We avoid noise variables in IB as much as possible. Some would find this not important, we find this important.
(2) Is there a reason not to use it? It's just a variable.

My PS version is 5.1.19041.610, a bit lower.
What is you Windows version?

PS C:\Users\user\projects\uw\corp-dsc-build> C:\Users\user\projects\uw\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1 : The variable '$_' cannot be retrieved because it has not been set.
At C:\Users\user\projects\uw\corp-dsc-build\build.ps1:145 char:9
+         Invoke-Build @PSBoundParameters -Task $Tasks -File $MyInvocat ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Build.ps1], Exception
    + FullyQualifiedErrorId : Invoke-Build.ps1

(1) Yes. We avoid noise variables in IB as much as possible. Some would find this not important, we find this important.
Fair enough

(2) Is there a reason not to use it? It's just a variable.
PSScriptAnalyser advises against it:
https://docs.microsoft.com/en-us/powershell/utility-modules/psscriptanalyzer/rules/AvoidAssignmentToAutomaticVariable?view=ps-modules

It was only curiosity that I queried it. I'm not suggesting it's changed.

Thank you for the report, I appreciate it a lot. Do not get me wrong, we should first understand what's happening and why.

PSScriptAnalyser advises against it:

And there is another long discussion among PS community on why this does not apply to $_.
TL;DR (1) It is automatic only in a particular context; (2) It is useful for assigning in scripts in many cases.

This is an excerpt from the build.ps1 script this is running from.
It's something I've inherited and I'm in the throes of cleaning it up.
I've had to omit parts, I'm sorry I'm limited on how helpful I can be.
I can take a freshly built Windows Desktop, and test with a simple build script and then add Set-StrictMode -Version (1|2|3|Latest) and see what happens, but that won't be today.
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSAvoidUsingCmdletAliases', 'task')]
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseDeclaredVarsMoreThanAssignments', 'PSDependTarget')]

[CmdletBinding()]
param
(
    [Parameter(Position = 0)]
    [ValidateSet('?', 'Clean', 'ModuleBuilder', 'TestModules', 'TestQA', 'PublishDSCResourceModules')]
    [string[]]$Tasks = '.',
)

BEGIN {

    Set-StrictMode -Version 3
    $ErrorActionPreference = [System.Management.Automation.ActionPreference]::Stop

    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
		// Do Stuff
        Write-Host -ForegroundColor Green '[pre-build] Starting Build Init'
        Push-Location $PSScriptRoot -StackName BuildModule
    }

    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
        Invoke-Build @PSBoundParameters -Task $Tasks -File $MyInvocation.MyCommand.Path
        Pop-Location -StackName BuildModule
        return
    }

}

PROCESS {

    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
        # Only run the process block through InvokeBuild (Look at the Begin block at the bottom of this script)
        return
    }

	task ModuleBuilder -Before TestQA {

        $DSCConfigurationModules = (Get-ChildItem -Path "$PSScriptRoot\*Config" -Directory | Where-Object { $_.Name -ne 'tpDSCBuildConfig' })
        $DSCConfigurationModules = ($DSCConfigurationModules | Select-Object -Unique)

        # add list of utility related modules that are also part of the project.
        $utilityFunctions = @(
            'DscLcmSetup'
            'DscUtility'
            'tpDSCBuildConfig'
        )

        forEach ($utilityFunction in $utilityFunctions)
        {
            $ModulePath = (Join-Path -Path $PSScriptRoot -ChildPath $utilityFunction)
            Write-Build -Color Yellow -Text "Processing DSC Utility Module '$utilityFunction'."
            PublishDscConfigurationModule -ModulePath $ModulePath -ModuleType 'Utility'
        }

        forEach ($dscConfigurationModule in $DSCConfigurationModules)
        {
            Write-Build -Color Yellow -Text "Processing DSC Configuration Module '$dscConfigurationModule'."
            PublishDscConfigurationModule -ModulePath $dscConfigurationModule
        }

        # install any dscresource modules which are required by the configuration modules
        if ($DSCConfigurationModules.count -gt 0)
        {
            InstallDscResourceModule -DSCConfigurationModules $DSCConfigurationModules
        }
    }
}

Thank you for taking the time to understand.

What are these in your case:

When you get this error, what is the full error text, including the location?
Could you please also dump the whole $error and see some hints to a different location of the error?

This is your script "cleaned" which works and prints "Happy to run"
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSAvoidUsingCmdletAliases', 'task')]
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseDeclaredVarsMoreThanAssignments', 'PSDependTarget')]

[CmdletBinding()]
param
(
    [Parameter(Position = 0)]
    [ValidateSet('?', 'Clean', 'ModuleBuilder', 'TestModules', 'TestQA', 'PublishDSCResourceModules')]
    [string[]]$Tasks = '.'
)

BEGIN {
    Set-StrictMode -Version 3
    $ErrorActionPreference = [System.Management.Automation.ActionPreference]::Stop

    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
		# Do Stuff
        Write-Host -ForegroundColor Green '[pre-build] Starting Build Init'
        Push-Location $PSScriptRoot -StackName BuildModule
    }

    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
        Invoke-Build @PSBoundParameters -Task $Tasks -File $MyInvocation.MyCommand.Path
        Pop-Location -StackName BuildModule
        return
    }
}

PROCESS {
    if ($MyInvocation.ScriptName -notLike '*Invoke-Build.ps1')
    {
        # Only run the process block through InvokeBuild (Look at the Begin block at the bottom of this script)
        return
    }

	task ModuleBuilder {
		"Happy to run"
    }
}

BTW BEGIN and PROCESS are redundant in IB scripts. They only make sense when designed for pipeline input, not the case.

ScriptStackTrace:
[DBG]: PS C:\Users\user\projects\corp-dsc-build> $_.ScriptStackTrace

at *Die, C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1: line 31
at <ScriptBlock><DynamicParam><trap>, C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1: line 43
at <ScriptBlock><DynamicParam>, C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1: line 61
at <ScriptBlock><Begin>, C:\Users\user\projects\corp-dsc-build\build.ps1: line 247

InvocationInfo:
Line                  :             Invoke-Build -Task $Tasks -File $MyInvocation.MyCommand.Path

PositionMessage       : At C:\Users\user\projects\corp-dsc-build\build.ps1:247 char:13
                        +             Invoke-Build -Task $Tasks -File $MyInv ...
                        +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PSScriptRoot          : C:\Users\user\projects\corp-dsc-build
PSCommandPath         : C:\Users\user\projects\corp-dsc-build\build.ps1
InvocationName        : Invoke-Build
PipelineLength        : 0
PipelinePosition      : 0
ExpectingInput        : False
CommandOrigin         : Internal
DisplayScriptPosition :
ParameterValues       : {}

so it fails here:
at <ScriptBlock><DynamicParam>, C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1: line 61

	DP = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary

BTW BEGIN and PROCESS are redundant in IB scripts. They only make sense when scripts are designed for pipeline input, not the case for IB build scripts.

I'm guessing the original author's intent was being able to "run the build" without calling Invoke-Build for some reason.
FYI it looks like to be based on this:
https://github.com/gaelcolas/Sampler/blob/main/Sampler/Templates/Build/build.ps1

What is the full error message with location info included?

Is how it's reported:
C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1 : Cannot retrieve the dynamic parameters for the cmdlet. System error.
At C:\Users\user\projects\corp-dsc-build\build.ps1:247 char:13
+             Invoke-Build @PSBoundParameters -Task $Tasks -File $MyInv ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Build.ps1], ParameterBindingException
    + FullyQualifiedErrorId : GetDynamicParametersException,Invoke-Build.ps1

That gives the location in which the exception was returned to the calling script, hence including the ScriptStackTrace
if there's something more you think I can tease out, please feel to advise!

Dump this after error:
ps> $Error

I agree entirely that the exception is thrown here:
Line 61:   DP = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary

I can see with the debugger that this is the last line executed before the The variable '$_' cannot be retrieved because it has not been set. exception is thrown.
I would agree that doesn't not make a great deal of sense to me right now.
Adding either:
Set-StrictMode -Off or amending IB as per the PR stops it from occuring. Turn strict mode back on or revert the change from the PR and it re-occurs.
To further confuse the situation,
I've been running this simultaneously from VS Code and from the PowerShell CLI.
I've seen the problem in both environments, reproduced in the exact same way.
I've killed and restarted VSCode. And started a new PowerShell CLI session.
That put me in a situation where I can reproduce with VSCode, but not with the CLI.
I killed and restarted the PS Terminal within VS Code, in order to get a clean "dump" of $Error and now I can't reproduce.
I can't reproduce it with the test function I wrote, even though I tested that and reproduced the same exception in a clean Powershell CLI session.

Tricky... I'll keep thinking.
Another tip: Push-Location and Pop-Location are redundant because IB takes care of restoring the current location.
All in all, try to remove bit by bit from the script to get the minimal reproducible variant (even not stable).
And Happy New Year once again! And happy building, too :)

Before winding up in the situation where I could not re-produce the problem, I did put the call to Invoke-Build into a try...catch and wrote $error to a file:
error.txt
At C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1:63 char:6
+     P = $_

^^ Not line 61 !!!
I'm happy to close this and re-raise if and when I manage to more reliably reproduce the problem.
This is maddening. Not sure I trust/believe anything any more.

Another tip: Push-Location and Pop-Location are redundant because IB takes care of restoring the current location.

Thank you.
I'm planning to rip those out. This was over 1000 lines of code at the start :/

Good. But how is it possible? This should not be possible per the code we have in IB.
Do you have anything else running, say, in parallel and potentially killing $_ somewhere in the middle?

I'm hoping as a carry on re-factoring this build script I'll break it again in the same way.
Fankly I'm baffled right now.

Reproduced
But no idea what gave rise to it.
I'm not re-opening the issue until I have more concrete information/evidence as to what is happening.
The variable '$_' cannot be retrieved because it has not been set.
C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1 : The variable '$_' cannot be retrieved because it has not been set.
At C:\Users\user\projects\corp-dsc-build\build.ps1:192 char:5
+     Invoke-Build -Task $Tasks -File $MyInvocation.MyCommand.Path
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Build.ps1], Exception
    + FullyQualifiedErrorId : Invoke-Build.ps1

The variable '$_' cannot be retrieved because it has not been set.
At C:\Users\user\projects\corp-dsc-build\output\RequiredModules\InvokeBuild\5.8.5\Invoke-Build.ps1:63 char:6
+     P = $_
+         ~~
    + CategoryInfo          : InvalidOperation: (_:String) [], RuntimeException
    + FullyQualifiedErrorId : VariableIsUndefined

@uw-dc I am going to make the change similar to your suggested. I still cannot reproduce. But I believe you, i.e. in some environments use of $_ may introduce potential strict mode issues.

@uw-dc I am going to make the change similar to your suggested. I still cannot reproduce. But I believe you, i.e. in some environments use of $_ may introduce potential strict mode issues.

"Fixed" (?) in v5.8.8

"Fixed" (?) in v5.8.8


ccache: disable flaky test

test.trim_dir has transient failures, currently assumed to be filesystem-specific as it fails on Linux systems using ZFS and on macOS (HFS+).
See discussion in https://github.com/NixOS/nixpkgs/pull/137387#issuecomment-917725240

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137936 at f38d014b run on aarch64-linux 1

2 packages built successfully:

ccache
ccacheStdenv

Result of nixpkgs-review pr 137936 run on x86_64-linux 1

3 packages built:

ccache
ccacheStdenv
ccacheWrapper


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

This was a great experience.


Support both old and new diffusers import path

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Note the lazy import has been added in 0.21.0 and the latest version before that is 0.20.2
https://github.com/huggingface/diffusers/releases/tag/v0.21.0


/tmp is assumed to be of tmpfs

While generally it is true, /tmp is not guaranteed to be of type tmpfs (it could be ext2 for example). In such cases, this daemon will still work, but likely without any benefits. One solution to this is (as described in https://github.com/graysky2/anything-sync-daemon/issues/3) to use mount and bind to create a separate tmpfs partition, however at the very least a check should be done on /tmp before starting up, and either fail, or leave a warning message.

Agreed.  Will cook up something as time permits.

I am not aware of a command that will return a clean value of the fstype.  Closest thing I could find is df -T /tmp but that output would need to post-processed for the comparison.  Is there something that just returns the fstype?

Please reopen if you can think of a slicker way.

If you were to use df -Tt tmpfs /tmp, this command will succeed if the file-system is of type tmpfs. Otherwise it will fail. Seems elegant enough without having to pipe it into something else.

Hi,
Is this still being maintained ? Do you mind also allow /dev/zram devices or a way to force?

Hi,
Is this still being maintained ?
Seeing as the last commit was in 2017, I'm guessing no. You also commented on an issue closed a year before that. You may want to explore the various forks of this project since some appear to have newer commits.

Hi All. I need to revisit this codebase to get it in line with that of psd but haven't yet had time to do it.

Sorry @CubeTheThird , I was confused, seeing this with last commit from 2017, but I was checking psd and it has (very) recent commits, so I just thought it was better to ask. ( and what I am putting on the zram isn't a browser profile )
@graysky2 I worked around the issue on the code, so so far things are working for me. so don't worry if you decided to unmantain this code.
Thanks for the project!


Is there any free alternative to ngrok?

I find ngrok bandwidth limit fills up quickly.

https://zrok.io/


Add android support

This PR adds Android support to devenv.
This integration works with the latest channel, but creating an AVD through android studio is not possible (Use CLI for this). To try out this PR, you need to change the devenv input to github:k3yss/work/keys/android-support?dir=src/modules  in  your devenv.yaml file.
devenv.yaml
inputs:
  devenv:
    url: path: github:k3yss/work/keys/android-support?dir=src/modules
allowUnfree: true

After enabling the input, you can add android.enable=true in your devenv.nix file.
devenv.nix
{ ... }:

{
  android.enable = true;
}

You should have an base working Android environment ready.
Below are a few working screenshots:
Android Emulator working:

React Native working:

Flutter working:

TODO

[x] Test with React Native
[x]  Test with flutter
[x] Add example
[x] Make options modular
[x] Make sure emulator works

Fixes #310

Ready for review : )
cc @domenkozar @sandydoo

We are about to get better AVD support with android studio: https://github.com/NixOS/nixpkgs/pull/315233

Hey @numinit , thanks for the information, I have been patiently following the PR. One issue that users currently face is the creation of an emulator from Android Studio, I tried playing around with various env variables to come up with a potential fix for it but was unsuccessful. Did you manage to come up with a solution for it or do we expect the user to create emulators via avdmanager tool?

@k3yss The trick I've found is twofold: the wrapper makes new projects default their sdk.dir to the androidenv composition, but you still need the sdk.dir (and possibly ndk.dir) in your local.properties. Any new AVDs created with Android Studio work fine if this is true.

@numinit What worked for me is:
1: Create a AVD using the CLI command.
2: Open the project in android studio.
3: Run the start command.

In case of react-native I did npm run android from the terminal which worked!

What I wanted to ask if it was possible to do step 1 using android studio.

It is possible to do step 1 in Android Studio. It's a little counterintuitive though, you need a project open with sdk.dir set properly for it to work right.

@numinit I think I already have that configured, let's do a merge in the current state and wait for reviews.

@domenkozar can you try the flutter configuration. I have some configuration issues with home manager.

flutter seems to be broken, investigating.

Everything works as expected for now, hope I didn't miss something 🤞


fix: use crictl to pull images and supports mirrors

What problem does this PR solve?:
Reported in Slack https://mesosphere.slack.com/archives/C01MPKVBB5E/p1646197247844029
ctr does not use the same Containerd mirror configuration, lets go back to using crictl to pull the images which will use Containerd mirrors.
This is basically the command we had before https://github.com/mesosphere/konvoy-image-builder/pull/162/files#diff-14c84fc26cc68826bdd8c9ee2ba0b29f31537fc6fec4f03028d38b024d7b9d6cL12
Which issue(s) does this PR fix?:

https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

(This fixed https://jira.d2iq.com/browse/D2IQ-85887)


GH-1062 - Stratagem duratiion models should be bigint

Fixes #1062.
Since milleseconds will be used for duration and it's possible that a
number of years could be specified, the fields should be of the
BigInteger type instead of Integer. This patch will ensure that:

The duration fields on the models use BigInteger
The API will handle hydrating and dehydrating data from String to
BigInteger such that data is stored as a u64 in the database and
retrieved as a long instead of a string (Tastypie does not support
BigInteger in resources so it must be converted to a long)
Validation is added to ensure that no value > MAX_SAFE_INTEGER<PHONE_NUMBER>740991)
can be used for either duration.

Signed-off-by: Will Johnson<EMAIL_ADDRESS>

[root@adm vagrant]#  iml stratagem scan --filesystem fs -r9007199254740991s
✗ Report duration cannot be larger than<PHONE_NUMBER>740991.

Codecov Report

Merging #1066 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1066   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

Continue to review full report at Codecov.

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


Send data to Printer

i want to print file on printer with popup printer window?

This is another plugin request.
Duplicate of: https://github.com/go-flutter-desktop/go-flutter/issues/224
The go-flutter doesn't have an implementation for that plugin. You may create one yourself and open a PR on https://github.com/go-flutter-desktop/plugins
The go-flutter team doesn't have the resource to implement all plugins, PLEASE help us.
Wiki:

https://github.com/go-flutter-desktop/go-flutter/wiki/Plugin-info
https://github.com/go-flutter-desktop/go-flutter/wiki/Create-a-hover-compatible-plugin
https://github.com/go-flutter-desktop/go-flutter/wiki/Implement-a-plugin
https://github.com/go-flutter-desktop/go-flutter/wiki/GLFW-Plugin-example

Examples:

https://github.com/go-flutter-desktop/plugins

Tutorial example:

https://github.com/go-flutter-desktop/examples/tree/master/plugin_tutorial

Closing this issue because the go-flutter team will not work on such plugin.
Still,
You can report your advancement/questions in this issue.
We also have a gitter chat: https://gitter.im/go-flutter-desktop/go-flutter .


CI18-175 - Fixing migration issues for carbon production deployment

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@jumba2010 what's the effect of these modifications on existing deployments? Have you tested this?

Yes, I have tested them on an existing DB and on a blank DB. They run fine


Missing PHP GD LIbrary Extension

Hello,
I'm using your docker image of koel and I'm unable to get the images of the albums and artists to appear.
After some troubleshooting, it seems that that feature need the PHP GD extension to work.
It seems to be missing from this image last release.
Laravel log:
[2020-07-05 16:03:26] production.ERROR: Intervention\Image\Exception\NotSupportedException: GD Library extension not available with this PHP installation. in /var/www/html/vendor/intervention/image/src/Inter
vention/Image/Gd/Driver.php:19
I tried to modify the Dockerfile to get it installed but I was unable to do so.
Regards,
Pierre-Yves Bouvier

Hi, thanks for the report.
There is a pending contribution at #25 to add GD as a dependency. When I've tested it and it's merged, a new docker image will be pushed including it.

#25 has been merged and the new image has been pushed. From the tests I've made, it looks like the covers appear correctly. Could you confirm if the problem is fixed on your side after pulling the new image ?

The problem is fixed.
It works perfectly now. Thank you.

Glad to hear it :smile:. Thanks to @bastidest for the fix !


component-macro: normalize the path parameter in component bindgen

I encountered a file path issue while using the wasmtime::component::bindgen! macro, I used a relative file path (e.g., ../wit) in the path parameter, and then I received an error message:
failed to read path for WIT [/Users/code/test-component/examples/../wit]

The file path in the error message was quite confusing, in reality, the path that was not found should be /Users/code/test-component/wit. The relative file path in the error message made it hard for me to immediately understand which directory wasmtime::component::bindgen! was using to look for WIT files. Therefore, this patch normalizes the path before resolving WIT files.
Error message before:
failed to read path for WIT [/Users/code/test-component/examples/../wit]

after:
failed to read path for WIT [/Users/code/test-component/wit]

The wit_bindgen::generate! macro has the same issue. If this patch is reasonable, I will make the same changes to wit_bindgen::generate! afterward.

Thanks for the PR! Personally though I find path manipulation very tricky/subtle. For example in the presence of symlinks I'm not sure that this implementation is correct. In lieu of that perhaps std::fs::canonicalize could be used instead? If that returns Ok then the resulting path can be used and if it returns Err then the original path can be used as-is to probably return an error somewhere else.

Thanks for the review, I agree that path manipulation is tricky, std::fs::canonicalize is more of a compromise solution. It can handle some scenarios (such as when the path itself exists but the wit file does not). However, if the path itself does not exist, the error message will still be the same as it is now. But I believe this is acceptable because we would rather not incorrectly normalize the path in some corner cases.


Pre release with react native 0.73

:tada: This PR is included in version 2.7.0-test.1 :tada:
The release is available on:

npm package (@test dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ada support?

The config.mak.dist states that the only languages supported are C and C++, and indeed Ada is broken as-is.
However I've been able to build GCC 9.4.0 targeting x86_64-linux-musl with Ada support by applying a subset of patches from the Alpine Linux GCC port. I don't know how stable it is, but I've been able to build several well-known Ada projects with this toolchain (XmlAda, GPRBuild, GNATColl and Alire), and they all seem to work.
Are you interested in these patches?

Yes, I am. It's hard to bootstrap (you need a host compiler that supports Ada to begin with) which means you can't use an existing lineage of MCM toolchains to build it, but it would still be worthwhile to have.


train.py code

Hi！ How can I modify the code of ‘train.py’ to get the loss of 5 stages？ Thank you

Hi! Just pass --num_stages 5 to train a model with 5 refinement stages.

Hi! Just pass --num_stages 5 to train a model with 5 refinement stages.


adds numerous defines and uses notation: *_BASE_ADDR *_OFFSET for add…

…ress offsets, *_BIT for bit positions and *_Pos for bit positions (multiple bits), *_Msk for very common bit masks, NO suffix for a direct value, e.g., (1 << *_BIT)
This still has the SPI0 reset/enable degeneracy but currently all examples assemble with it.

Good additions! The only things I'd change would be to keep the names all caps (the _Pos and _Msk suffixes to _POS and _MASK, respectively) and spell out "mask" (since it only adds a single char).

Looks good to me! Thanks for getting these added.


My psych engine is not working

Describe your bug here.
When I try to open Psych Engine, it opens up with a black screen and nothing else. No matter how much time I wait for it to work, it doesn't. I downloaded a fresh, new version, and it still doesn't work. Even older versions of Psych Engine don't work. I need help.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I was messing with menu stuff in my mod in the mod folder. Idk how it could stop working because of that.

maybe the engine cannot take it or maybe u did smt wrong and straight of broke the engine idk

Your PC sucks

Yes, I was messing with menu stuff in my mod in the mod folder. Idk how it could stop working because of that.

What exactly did you do? If you messed with the engine enough to break it, you should probably explain what you did to cause it.

Just press enter
Got the same problem for my mod and pressing Enter lets you to the title screen


Connection with the server was terminated abnormally

I am using the SignalR console application client and sometimes, due to the Hub website being updated the signalR .NET client will throw this error.
The connection with the server was terminated abnormally
Stack
 at System.Net.WebSockets.WinHttpWebSocket.SendAsync(ArraySegment`1 buffer, WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken cancellationToken)
   at System.Net.WebSockets.WebSocketHandle.SendAsync(ArraySegment`1 buffer, WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Sockets.Client.WebSocketsTransport.<SendMessages>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Sockets.Client.HttpConnection.<SendAsyncCore>d__51.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Sockets.Client.HttpConnection.<SendAsync>d__50.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.<SendInvocation>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.<InvokeAsyncCore>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.<InvokeAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnectionExtensions.<InvokeAsync>d__33`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at POEUtility.Workers.SignalRChangeHubWorker.<DoWorkAsync>d__8.MoveNext() in C:\Projects\Other\POEUtility\POEUtility.Workers\SignalRChangeHubWorker.cs:line 90
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at POEUtility.Console.Program.<WorkerLoop>d__5.MoveNext() in C:\Projects\Other\POEUtility\POEUtility.Console\Program.cs:line 77
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at POEUtility.Console.Program.<MainAsync>d__4.MoveNext() in

When this happens, the Closed event does NOT fire. So the connection variable still thinks it is connected and the next time I send a message I get the following infamous error.
Object reference not set to an instance of an object.
stack
at Microsoft.AspNetCore.SignalR.Client.HubConnection.<SendInvocation>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.<InvokeAsyncCore>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.<InvokeAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Client.HubConnectionExtensions.<InvokeAsync>d__33`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at POEUtility.Workers.SignalRChangeHubWorker.<DoWorkAsync>d__8.MoveNext() in C:\Projects\Other\POEUtility\POEUtility.Workers\SignalRChangeHubWorker.cs:line 90
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at POEUtility.Console.Program.<WorkerLoop>d__5.MoveNext() in C:\Projects\Other\POEUtility\POEUtility.Console\Program.cs:line 80
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at POEUtility.Console.Program.<MainAsync>d__4.MoveNext() in

At this point I do not know if the connection is active or not active? There are no properties available to tell me what state the connection is in.
Workaround:
I suppose I can catch all exceptions, dump the connection and try to recreate it for next use.

Are you running behind IIS or you are using just Kestrel?
Can you turn on logging at the .Trace level and paste logs here?
Generally the closed event should be invoked. Also the NullReferenceException should not happen.

The webSocket should get disconnected if sending fails, which should result in closing the connection. Without repro steps and/or logs it's hard to tell why it is not happening. Likely, KeepAlive feature (https://github.com/aspnet/SignalR/issues/282) should help with the first issue.
The NullReferenceException could have been fixed in https://github.com/aspnet/SignalR/commit/06475270ec845b5be95c46857d33599e41585e86 - impossible to confirm though since the stack trace for NRE was not included.


Updated image_ops_impl.py

Fix for #58703 and please find the gist here for  reference.

Hi @cantonios Can you please review this PR ? Thank you!

@wangpengmit do you have any more context here?  I seem to remember seeing such errors/descriptions elsewhere in the codebase.

Hi @wangpengmit Can you please check @cantonios's comments and keep us posted ? Thank you!

Hi @wangpengmit Any update on this PR? Please. Thank you!

I checked today and found that int64 seeds are still unsupported by the TF2XLA bridge. If you use int64 seeds, the higher 32bit will just be ignored because of https://github.com/tensorflow/tensorflow/blob/754b3df1dd4d928063e9399a86a3e6209d79e9ff/tensorflow/compiler/tf2xla/kernels/stateless_random_ops_v2.cc#L563
But @mihaimaruseac said we shouldn't document this missing TF2XLA coverage. I don't have a strong opinion on this documentation question.


Automatic PR from RestAPI-PR704

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/704

Doc only