/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.h:7:45: error: no type or protocol     named 'FlutterPlugin'     @interface FLTURLLauncherPlugin : NSObject

#ask help how to fix this error when flutter build ios :'(
Problem with:
url_launcher-5.4.2
Cronology:
The apps is works fine in Android (device and simulator) and iOS (simulator).
Build APK release in Android Studio works fine.
Build ios release with XCode v11.3.1 (11C504) FAILED WITH 20 ERRORs.
Flutter Doctor:
`Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Mac OS X 10.15.2 19C57, locale en-GB)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[✓] Android Studio (version 3.6)
[✓] VS Code (version 1.43.1)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.
`

Error Log:
`
Xcode build done.                                           99.7s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    In file included from /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:7:
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.h:7:45: error: no type or protocol
    named 'FlutterPlugin'
    @interface FLTURLLauncherPlugin : NSObject <FlutterPlugin>
                                                ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:12:28: error: unknown type name
    'FlutterResult'
    @property(copy, nonatomic) FlutterResult flutterResult;
                               ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:12:1: error: property with 'copy'
    attribute must be of object type
    @property(copy, nonatomic) FlutterResult flutterResult;
    ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:25:24: warning: incompatible
    pointer to integer conversion assigning to 'int' from '__strong id' [-Wint-conversion]
        self.flutterResult = result;
                           ^ ~~~~~~
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:37:23: error: called object type
    'int' is not a function or function pointer
        self.flutterResult(nil);
        ~~~~~~~~~~~~~~~~~~^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:39:25: error: use of undeclared
    identifier 'FlutterError'
        self.flutterResult([FlutterError
                            ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:66:41: error: no type or protocol
    named 'FlutterPluginRegistrar'
    + (void)registerWithRegistrar:(NSObject<FlutterPluginRegistrar> *)registrar {
                                            ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:74:27: error: expected a type
    - (void)handleMethodCall:(FlutterMethodCall *)call result:(FlutterResult)result {
                              ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:74:60: error: expected a type
    - (void)handleMethodCall:(FlutterMethodCall *)call result:(FlutterResult)result {
                                                               ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:110:20: error: expected a type
                 call:(FlutterMethodCall *)call
                       ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:111:20: error: expected a type
               result:(FlutterResult)result {
                       ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:132:53: error: expected a type
    - (void)launchURLInVC:(NSString *)urlString result:(FlutterResult)result API_AVAILABLE(ios(9.0)) {
                                                        ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:144:33: error: expected a type
    - (void)closeWebViewWithResult:(FlutterResult)result API_AVAILABLE(ios(9.0)) {
                                    ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:67:3: error: use of undeclared
    identifier 'FlutterMethodChannel'
      FlutterMethodChannel *channel =
      ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:67:25: error: use of undeclared
    identifier 'channel'
      FlutterMethodChannel *channel =
                            ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:68:8: error: use of undeclared
    identifier 'FlutterMethodChannel'
          [FlutterMethodChannel<EMAIL_ADDRESS>           ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:71:14: error: no visible
    @interface for 'NSObject' declares the selector 'addMethodCallDelegate:channel:'
      [registrar addMethodCallDelegate:plugin channel:channel];
       ~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:75:24: error: property 'arguments'
    not found on object of type '__strong id'
      NSString *url = call.arguments[@"url"];
                           ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:76:42: error: property 'method'
    not found on object of type '__strong id'
      if ([@"canLaunch" isEqualToString:call.method]) {
                                             ^
    /direktori/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/ios/Classes/FLTURLLauncherPlugin.m:77:11: error: called object type
    'id' is not a function or function pointer
        result(@([self canLaunchURL:url]));
        ~~~~~~^
    fatal error: too many errors emitted, stopping now [-ferror-limit=]
    1 warning and 20 errors generated.
`

Hi @azhar-rafiq
can you please provide your full flutter build ios --verbose
and your pubspec.yaml
or if possible a reproducible minimal code sample.
Thank you

pubspec.yaml:
name: app_name
description: A new Flutter application.

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# Read more about versioning at semver.org.
version: 0.9.1+912

environment:
  sdk: ">=2.0.0-dev.68.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.2
  firebase_core: ^0.4.0+1
  cloud_firestore: ^0.13.0+1

  google_sign_in: ^4.0.1+3
  firebase_auth: ^0.11.1
  firebase_database:
  http:
  intl:
  url_launcher: ^5.4.2
  share: 0.6.0+1

  audioplayers: ^0.14.2

  package_info: 0.4.0+13
  flutter_html: 0.11.1
  intro_views_flutter: '^2.8.0'
  lottie: 0.3.2
  flutter_youtube: "^2.0.0"
  shared_preferences: 0.5.6+3
  tutorial_coach_mark: 0.3.0

dev_dependencies:
  flutter_test:
    sdk: flutter

# For information on the generic Dart part of this file, see the
# following page: https://www.dartlang.org/tools/pub/pubspec

# The following section is specific to Flutter.
flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - images/logo
  #  - images/a_dot_ham.jpeg

Hi @azhar-rafiq
can you please provide your full flutter build ios --verbose
and your pubspec.yaml
or if possible a reproducible minimal code sample.
Thank you

Hi @azhar-rafiq
can you please provide your full flutter build ios --verbose
and your pubspec.yaml
or if possible a reproducible minimal code sample.
Thank you

the verbose are really long, I think I can't copy all of them, but here is the end of the result:

[+6192 ms] "flutter ios" took 179,751ms.
Encountered error while building for device.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      BuildIOSCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:90:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#3      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#4      _rootRunUnary (dart:async/zone.dart:1134:38)
#5      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#9      Future._completeWithValue (dart:async/future_impl.dart:524:5)
#10     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#11     _rootRun (dart:async/zone.dart:1126:13)
#12     _CustomZone.run (dart:async/zone.dart:1023:19)
#13     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#14     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#15     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#16     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#17     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#18     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

or if possible a reproducible minimal code sample.

I think I don't have any errors regarding my codes, because I can run my app smoothly on Android and iOS Simulators.
I do also success building APK for android.
But it only error when I try to build for iOS.
Here is what it shown if using XCode when I try to archive the app:

Nothing works... I really do not understand how could error "No type or protocol named 'FlutterPlugin'" happened.
Does someone know :(

In the end, I reset branch 3 times and now the problems are gone.

In the end, I reset branch 3 times and now the problems are gone.

Hi azhar.. I am facing exactly the same issue.. SharedPreferences thing was working fine on android and ios simulators. But while creating ios release build, i am getting the same issues. No problem with android/ release apk..No path or protocol found for FlutterPlugin for ios build.. Can you please specify exact steps to get this resolve. Thank you..

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


Support format option in docker app ls

- What I did
Introduced --format experimental option for docker app ls
Can either pass a Go template (jist like most docker CLI commands) or just "json" to enable json output.
- How I did it
with love
- How to verify it
docker app ls --format "{{(index . 0).Reference}}"
docker app ls --format "json"
- Description for the changelog
Introduced --format experimental option for docker app ls
- A picture of a cute animal (not mandatory)

Could we add a test for this?


Make RedisRateLimiter omit headers if property is set

Fixes #855

Codecov Report

Merging #856 into 2.0.x will decrease coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             2.0.x     #856      +/-   ##
===========================================
- Coverage       71%   70.98%   -0.02%
  Complexity     969      969
===========================================
  Files          131      131
  Lines         3787     3788       +1
  Branches       273      274       +1
===========================================
  Hits          2689     2689
- Misses         954      955       +1
  Partials       144      144

Impacted Files
Coverage Δ
Complexity Δ

...oud/gateway/filter/ratelimit/RedisRateLimiter.java
43.03% <0%> (-0.56%)
5 <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 9f9454b...eb0b10c. Read the comment docs.

Codecov Report

Merging #856 into 2.0.x will decrease coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             2.0.x     #856      +/-   ##
===========================================
- Coverage       71%   70.98%   -0.02%
  Complexity     969      969
===========================================
  Files          131      131
  Lines         3787     3788       +1
  Branches       273      274       +1
===========================================
  Hits          2689     2689
- Misses         954      955       +1
  Partials       144      144

Impacted Files
Coverage Δ
Complexity Δ

...oud/gateway/filter/ratelimit/RedisRateLimiter.java
43.03% <0%> (-0.56%)
5 <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 9f9454b...eb0b10c. Read the comment docs.

Is the coverage tool working correctly? It shows that getHeaders in RedisRateLimiter is not covered but it is.


World of Final Fantasy Offset issue

Rendering in game seems to have some issue, the screen is splitted by multiple horizontal bands with offset.

Software information
Name : World of Final Fantasy
Setting doesn't have influence on the result, only full screen is required in order to launch the game.
System information

GPU: NVIDIA GeForce GTX 1080 Ti
Driver: nvidia 435.21
Wine version: 4.17 & Proton 4.11-6
DXVK version: 1.4.2

Apitrace file(s)
No result, the game crashes without DXVK enabled :
wine apitrace.exe trace -a dxgi /run/media/jeux/WindowsSteamLibrary/steamapps/common/WOFF/WOFF.exe
apitrace: loaded into Z:\run\media\jeux\WindowsSteamLibrary\steamapps\common\WOFF\WOFF.exe
0031:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,<PHONE_NUMBER>22FCD0
002f:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,<PHONE_NUMBER>22FCD0
Log files

d3d11.log:
WOFF_d3d11.log
dxgi.log:
WOFF_dxgi.log
Proton log :
steam-552700.log

Yes, this is a known game bug and cannot easily be fixed inside DXVK.

Thanks for your hard work @doitsujin. Just keep this in the current state. It's better to maintain DXVK stability and performance.

Do you know if this works with wined3d?
I'd be surprised if it did to be honest because of how texture binding works there, but it would be interesting regardless.

I managed once to launch this game using wined3d. The result is a black screen in game, only maps and sub are rendered. I'll try to clean my prefix and make a apitrace with wined3d.

wrt apitrace, you can try copying the dxgi.dll, dxgitrace.dll and d3d11.dll from the x86/lib/wrappers directory (or x64/lib/wrappers if this is a 64-bit game) and launch the game; it's usually more reliable than using the command line app.
There's also no need to use wined3d to record a trace in this particular case.

I tried many time to make an apitrace without success. With Proton, the game crashes at the begin with a dx11 error. With wine, there is no .trace file generated.
I tried both command line and putting wrappers files directly into the game folder (with the executable) as you suggested.
Some screenshot without DXVK :

I'm probably making something wrong, even it seems to be not that difficult...

An apitrace is coming soon...

Okay, here is the apitrace : https://drive.google.com/file/d/110U3qR09wmSSHaBs1tIb-nLSpvwwXtiy/view?usp=sharing

Hi, I tried to launch this game using my Intel iGPU and the game works without any issue. It's seems to be a Nvidia specific problem.

Yes, but this is still technically a problem caused by invalid behaviour cause the game does invalid stuff.

@kust2708  Did it work without problems with DXVK or was it with WineD3D?

It's because that just works on Intel.

@iWeaker4you It was with DXVK, but as Joshua-Ashton said, it's because that just works on Intel (and AMD according to some youtube videos I saw). I can give another try with WineD3D.

So, Here is the result with WineD3D :

i think wined3d suffers from more or less the same problem because GL wants you to bind multisampled textures as GL_TEXTURE_2D_MULTISAMPLE rather than GL_TEXTURE_2D, but doing that would obviously result in the same undefined behaviour that breaks DXVK.
But yeah I don't really see a sane way to work around this problem.

I confirm it works on Intel iGPU and AMD GPU (Tested on Radeon RX 580 and RX5500) it is an NVIDIA issue.


Is this Bullet Point Correct or Even Needed?

To configure FastPath, the virtual network gateway must be either:

Ultra Performance
ErGw3AZ

Because in the following link your team points out that they are the same thing.  But the bulletpoints seem to imply that they are two different things and either can be used.
https://learn.microsoft.com/en-us/azure/expressroute/expressroute-about-virtual-network-gateways#gatewayfeaturesupport
[Enter feedback here]

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

ID: 3ef08cf3-dc22-6ef6-e6fe-c17b1f7cfe69
Version Independent ID: dbe4d186-129a-d76f-a5eb-7257226b5b78
Content: About Azure ExpressRoute FastPath
Content Source: articles/expressroute/about-fastpath.md
Service: expressroute
GitHub Login: @duongau
Microsoft Alias: duau

@D-Moonesinghe
Thanks for your feedback! We will investigate and update as appropriate.

@D-Moonesinghe ,
There is no difference in performance between Ultra Performance SKU and ErGw3AZ SKU. The difference between these SKU is zone redundancy ErGw3AZ is zone redundant whereas Ultraperformance is not. This information is currently documented here.
Hope this answers your question. Thank you!


Add configuration_script_sources.last_update_stdout

Add new last_update_stdout column to configuration_script_sources table. This allows to store last update stdout to display more information about why its refresh failed.
Fetching and presenting this information is a workaround for cloning repositories from HTTPS servers with untrusted SSL certificates. Tower API does not offer an option to disable SSL check, so with the stdout user can at least see, why the cloning actually failed.
https://bugzilla.redhat.com/show_bug.cgi?id=1513616
Prior merging this PR, folowing PRs require to be merged:

[ ] manageiq/manageiq-schema#187 migration
[x] ansible/ansible_tower_client_ruby#103 version release

/cc @jameswnl for review

ansible/ansible_tower_client_ruby v0.14.0 declared as Gemfile dependency in this PR has been released. Currently only the schema update dependency remains for this PR.

LGTM

Rebased on current master. Extracted the Gemfile edit to a new PR as it is more related to https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/84 than it is a part of the BZ.

@Fryguy Hey, I’d like to get this PR merged. Prior to that, https://github.com/ManageIQ/manageiq-schema/pull/187 must be merged first. May I ask you to have a look?

Ok, I see the confusion.  We told Ansible Tower to update (git pull) a repo (ConfigurationScriptSource) and something went wrong (bad credentials / bad url / git server down / etc.).  In Tower, that action is implemented as a playbook.  So, the idea was to get the standard out of the playbook as part of our provider refresh so that we can display it to ManageIQ users when something goes wrong.
I also don't like the name last_update_stdout because it's too Ansible Tower implementation detail specific.

Maybe source_sync_details?

@Glutexo How much data is this?  I know playbook output can get large, should we use a BinaryBlob?

I see now.  I think it would be best to do it in a similar matter to how we store the last error for things on the ext_management_system.  For example, an ems refresh occurs and if anything fails in the middle, we set last_refresh_error and last_refresh_date, but when we are successful we set that last_refresh_error to nil.  In this way, the UI knows when it's good or bad and can show icons or whatever accordingly.
I do understand that this is slightly different in that in the "return" from the ansible playbook is just some stdout.  However, do we also know if it was a success/failure case?  If so, then I would name these possibly last_sync_error and last_sync_date, and on failure populate with the error, and on success populate last_sync_error column with nil.

@Fryguy It already has a status which is storing the update's status coming from the Tower.  It is normally 'success' or 'failure'.

@bdunne  It only store when there's a failure in update and the logs I checked are all <2KB. Also configuration_script_source normally would not come in great number.

@Fryguy @jameswnl @bdunne Actually we store the stdout every time, even on a success. Just as we store the status and a timestamp.
As @jameswnl said, they are usually about 2 KB of size, success results are smaller than failed ones. The stdout is actually text, not binary data, do I see TEXT field more appropriate than BINARY BLOB. TEXT fields are limited to about 1 GB, which I guess is enough here.
As for the column name, I am not sure. The new column last_update_stdout is updated at the same time as last_update_on and status from the same source. In Tower, both last update timestamp and status propagate to the project itself, the stdout is accessible only by getting its own separate resource. I have no objections to use details or result instead of stdout. We are still using last_update though, so renaming to last_sync or source_sync would increase the naming entropy.

Guys, @Fryguy, @bdunne, @jameswnl, may I ask you for your opinion?
As I stated in my previous comment, there is already a naming discrepancy in the table. By introducing a new last_update_stdout column, the entropy is not increased.
Questioning the stdout part is more valid in my eyes. I agree that result might be a good option. Maybe output would work too, I used this term in the UI. https://github.com/ManageIQ/manageiq-ui-classic/pull/3762/files#diff-9b524579bdd0b54c65c5c3c0c778d2efR106

The stdout is actually text, not binary data, so I see TEXT field more appropriate than BINARY BLOB

What @bdunne is referring to is our binary_blobs model, not a literal BINARY BLOB type.  The binary_blobs model is designed to take large strings, chop it up into 1MB chunks and store them in a separate table.  While named binary_blobs, it can store anything.  Putting them into a separate table also has the advantage of allowing select * on the parent table without accidentally returning giant payloads.
That being said, I'm fine with storing the stdout in the column directly since the 99% case is reasonably sized.  I would however ensure that we truncate to some large, but reasonable, size, like 100KB or 50KB or something, just in case.

This allows to store last update stdout to display more information about why its refresh failed.
-----------
Actually we store the stdout every time, even on a success.

I'm arguing we should not store the stdout on success, because it's useless.  The purpose of storing stdout is to present failure strings when there is a failure.  Since we know the status, then on failure, we should store the error in last_update_error, and on success, set last_update_error to nil.  This matches how we store similar information on the EMS with respect to the last EMS Refresh.
If it wasn't clear there, we should name the column last_update_error.  I would argue for sync over update as the middle word, but since last_update_on already exists, I'd rather latch on to the existing name.  update was an unfortunate choice previously because it's so general, and is confused with updated_on, but since it already exists, I agree on keeping that part.  In fact, adding another column named last_update_error should end up giving more clarity to last_update_on.

Great! That means that I can rename the column and these simple PRs can get merged:

[ ] https://github.com/ManageIQ/manageiq/pull/17290
[ ] https://github.com/ManageIQ/manageiq-schema/pull/187

Renaming those last_update_* columns to last_sync_*, possibly along with the status column, can be done in a separate issue. Saving the stdout only on error and truncating it if it’s too big belongs to https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/72.
Also thanks for the clarification of binary blobs!

@Fryguy Renamed to last_update_error. Ready to merge?

Only the migration seems to be pending to get merged now. We should be ready to move on with this.
@miq-bot remove_label dependencies
@miq-bot add_label enhancement, providers/ansible_tower


Automated Package Upgrade

:tada: This PR is included in version 25.3.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG] test_read_region_cuda_memleak failing (GPUtil does not support Python 3.12)

Describe the bug
Python 3.12 support is rolling out across RAPIDS (https://github.com/rapidsai/build-planning/issues/40), and was added in this project in #773.
After merge, one nightly performance test failed like this:
________________________ test_read_region_cuda_memleak _________________________
[gw6] linux -- Python 3.12.5 /pyenv/versions/3.12.5/bin/python
python/cucim/tests/performance/clara/test_read_region_memory_usage.py:25: in test_read_region_cuda_memleak
    import GPUtil
/pyenv/versions/3.12.5/lib/python3.12/site-packages/GPUtil/__init__.py:33: in <module>
    from .GPUtil import GPU, getGPUs, getAvailable, getAvailability, getFirstAvailable, showUtilization, __version__
/pyenv/versions/3.12.5/lib/python3.12/site-packages/GPUtil/GPUtil.py:34: in <module>
    from distutils import spawn
E   ModuleNotFoundError: No module named 'distutils'

(build link)
Steps/Code to reproduce bug
Run this test:
https://github.com/rapidsai/cucim/blob/1584885a0e6447ded28f78a59e3f303a25c7c0f6/python/cucim/tests/performance/clara/test_read_region_memory_usage.py#L24
Expected behavior
N/A
Additional context
distutils was removed from the Python standard library in Python 3.12: https://peps.python.org/pep-0632/
GPUtil has not been updated since August 2019 (commit history), and it unconditionally runs import distutils (code link).
Options to fix this:

remove that performance test
refactor that performance test to not use GPUtil
modify GPUtil to make it compatible with Python 3.12 (and either contribute that upstream or patch/vendor it here)

I was wondering why, in the failing build linked above, the wheel tests for Python 3.12 were failing in this way but the conda tests were not.
Think I found it... setuptools provides distutils, and setuptools was making it into some but not all CI environments here.
docker run \
    --rm \
    -it rapidsai/ci-conda:cuda12.5.1-rockylinux8-py3.12 \
    python --version
# Python 3.12.5

docker run \
    --rm \
    -it rapidsai/ci-conda:cuda12.5.1-rockylinux8-py3.12 \
    python -c "import distutils; print(distutils.__file__)"
# /opt/conda/lib/python3.12/site-packages/setuptools/_distutils/__init__.py

docker run \
    --rm \
    -it rapidsai/citestwheel:cuda12.5.1-ubuntu22.04-py3.12 \
    python --version
# Python 3.12.5

docker run \
    --rm \
    -it rapidsai/citestwheel:cuda12.5.1-ubuntu22.04-py3.12 \
    python -c "import distutils; print(distutils.__file__)"
# ModuleNotFoundError: No module named 'distutils'

So another approach for now could be to take on setuptools as a test-time dependency, which would allow continuing to use GPUtil unconditionally.
But that will also eventually stop working, as setuptools is trying to whittle down how much of distutils it exposes and may eventually remove distutils entirely:

https://github.com/pypa/setuptools/issues/2372#issuecomment-686832461
https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html


Automatically remove stale remote jobs (7.x)

Codecov Report

Merging #943 (d3064a5) into 7.x (311c96e) will increase coverage by 0.02%.
The diff coverage is 87.09%.

@@             Coverage Diff              @@
##                7.x     #943      +/-   ##
============================================
+ Coverage     62.23%   62.25%   +0.02%
- Complexity    11400    11406       +6
============================================
  Files          1611     1612       +1
  Lines         55225    55246      +21
  Branches       5476     5476
============================================
+ Hits          34368    34395      +27
+ Misses        18634    18633       -1
+ Partials       2223     2218       -5

Impacted Files
Coverage Δ

...national/snowowl/core/config/JobConfiguration.java
63.63% <63.63%> (ø)

...nternational/snowowl/core/jobs/RemoteJobEntry.java
60.44% <100.00%> (+0.59%)
:arrow_up:

...ernational/snowowl/core/jobs/RemoteJobTracker.java
88.88% <100.00%> (+0.33%)
:arrow_up:

...onal/snowowl/core/repository/RepositoryPlugin.java
94.39% <100.00%> (+0.16%)
:arrow_up:

.../snomed/core/ecl/SnomedEclRefinementEvaluator.java
88.79% <0.00%> (-0.22%)
:arrow_down:

.../b2international/index/es/client/EsClientBase.java
66.66% <0.00%> (+1.19%)
:arrow_up:

...onal/snowowl/snomed/core/tree/TerminologyTree.java
82.69% <0.00%> (+1.92%)
:arrow_up:

...national/snowowl/core/locks/OperationLockInfo.java
46.66% <0.00%> (+3.33%)
:arrow_up:

.../snowowl/core/branch/review/ReviewManagerImpl.java
89.30% <0.00%> (+5.03%)
:arrow_up:

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 311c96e...d3064a5. Read the comment docs.

The 8.x counterpart of this PR is https://github.com/b2ihealthcare/snow-owl/pull/942.


New project importer for headless mode

Description of changes made

New project importer for headless mode that fixes the main issues with unresolved projects.
Some headless mode fixes from pderakhshanfar/bug-fix/nullsdk, mainly an option to use default JDK if the IJ was not able to resolve the project JDK
An option to turn off the coverage computation in the headless mode, mainly because of sometimes IJ cannot resolve project modules and fails with null pointer on

ProjectFileIndex.getInstance(project).getModuleForFile(targetPsiClass.containingFile.virtualFile)

Why is merge request needed
Fix headless mode
Other notes
With the new project import, our previous issues with test generation seem to be resolved.
There are still some issues with the project resolve:

Sometimes project SDK is not resolved
Sometimes IJ cannot resolve a module of a file

However, I have implemented workarounds for those issues that seem to be working.
What is missing?
Please mention if anything is missing for this merge request, e.g you have decided to move something to the next merge request

[x] I have checked that I am merging into correct branch

I have started the pipeline to check for correctness.
I had the following exception (see log file). It did not stop the generation, but I've never seen it before: testspark.log
Also, in the TestSparkStarter the classPath is created using ToolUtils.sep; for some reason, it breaks the compilation on the VM (this ToolUtils.sep renders either as an empty string or a slash (I did not figure which one exactly but not a colon :), therefore I manually need to replace it with ::

Perhaps ToolUtils.sep is defined incorrectly.

@Vladislav0Art thank you for noticing that.

Yes, this exception occurs for me as well. As far as I understand, it is an exception thrown by some of the IJ modules during project resolve. It does not affect the test generation for me too.
Yes, that was an error in TestSparkStarter/ToolUtils, as ToolUtils.sep is defined as File.separatorChar, while we need File.pathSeparatorChar. I have added new property in ToolUtils and used in in starter class.


Fix Spotify API

I fixed the Spotify api

From what I remember $duration should be in seconds, also since we'll have seconds directly if (count($duration) == 2) { block and its else part are not necessary.
Can you fix this?
Otherwise LGTM, nice to see that Spotify have convenient API for this finally, did you test it yourself?

Hi,
I fixed the duration. I did test the script and it works. VK api still works :+1: .

Awesome, thanks man!

Thank you also... Very useful script :notes:


Issue with the preprocessing

Hello after trying to perform the preprocessing step, I obtain an error and the step is not able to finish. More precisely, my ubuntu terminal gives me:
`(IBMGNN) aserres@WS-5CG3134FXZ:~/Multi-GNN$ python format_kaggle_files.py kaggle-files/HI-Small_Trans.csv
100% |██████████████████████████████████████████████████| Reading data DatatableWarning: Duplicate column name found, and was assigned a unique name: 'Account' -> 'Account.0'
100% |██████████████████████████████████████████████████| Reading data [done]
Traceback (most recent call last):
File "/home/aserres/Multi-GNN/format_kaggle_files.py", line 71, in
line = '%d,%d,%d,%d,%f,%d,%f,%d,%d,%d\n' %
TypeError: must be real number, not str
(IBMGNN) aserres@WS-5CG3134FXZ:~/Multi-GNN$`
By any chance do you know this error and how to solve it ?
PS: I had to install datatable by myself as it wasn't in the env file.
Many thanks by advance.
Best,
Arthur

For some reason some variables are in the wrong format. Modifying format_kaggle_files.py as follow solve the problem:
`       amountReceivedOrig = float(raw[i,"Amount Received"])
amountPaidOrig = float(raw[i,"Amount Paid"])
    isl = int(raw[i,"Is Laundering"]`)


Fix libaarhusxyz.export.vtk to be concistent with libaarhusxyz.normalizer

libaarhusxyz.export.vtk.dump()  does not understand all the flightline column names renamed by libaarhusxyz.normalizer

fixed with commit: https://github.com/emerald-geomodelling/libaarhusxyz/commit/fa28c7b66c9ee3fcd9db06a6cde0bcef9b67d6d4


*: Provide simple example to be run by CI

This commits adds a simple example (examples/example.rs) as well as
a Testground manifest (./manifest.toml) to run a single Testground
instance, using sdk-rust, connecting to the sync service and signaling
success.
Can be run via:
testground plan import --from sdk-rust

testground run single \
         --plan=sdk-rust \
         --testcase=example \
         --builder=docker:generic \
         --runner=local:docker \
         --instances=1 \
         --wait

@galargh as discussed out of band, could you take care of GitHub Actions side? I don't have an opinion on the process, I guess it is easiest if you just push to this branch?
Also any suggestions / changes / ...  to the logic provided thus far here would be very much appreciated.

I added a step to CI which runs the example you provided. Here's an example run: https://github.com/testground/sdk-rust/runs/5659084888?check_suite_focus=true
TLDR it works! Installing testground takes quite a long time though. I think it might be time to start distributing testground binaries. I created an issue for this in testground repo - https://github.com/testground/testground/issues/1300

Perfect. Thanks @galargh. This is exactly what we need here.

Installing testground takes quite a long time though

4m 10s should be fine for us for now.

(How did you succeed on the first try / commit? :exploding_head:  Asking for a friend.)

(How did you succeed on the first try / commit? 🤯 Asking for a friend.)

I did the work on a different branch and only pushed to yours once it was working. Surprisingly though, I only did one tiny mistake the first time around - I tried the last run without | in: https://github.com/testground/sdk-rust/blob/5c3bc8b81ccf431d6f847d9d8a25967523298071/.github/workflows/ci.yml#L107
That might be because I also use https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml which checks for me if my GitHub Actions ymls are correct.


[Issue] Twitch API helix/users/follows Endpoint Deprecation

Deprecated API: https://dev.twitch.tv/docs/api/reference/#get-users-follows
Currently TwitchLib has not officially support the new API endpoints GET https://api.twitch.tv/helix/channels/followers
TwitchLib Issue: https://github.com/TwitchLib/TwitchLib/issues/1112
Impacted projects:

FetchTwitchRecord: https://github.com/TaiwanVtuberData/VTuberTrackingDataProject/blob/808d7e848ac93fc21a79213e425f0df7e9a3cd4d/FetchTwitchRecord/Fetcher.cs#L53C1-L57C27

FetchBasicData: https://github.com/TaiwanVtuberData/VTuberTrackingDataProject/blob/808d7e848ac93fc21a79213e425f0df7e9a3cd4d/FetchBasicData/Program.cs#L169C1-L173C31

Possible solutions:

Wait for TwitchLib to add the feature
Calling the API on my own

resolved


TURN connection breaks when the backend pod enters graceful shutdown

Description
Client's TURN connections should remain alive after the baxckend pod they are talking to via STUNner enters graceful shutdown. However, currently connections break as soon as the backend pod status becomes Terminating.
Steps to Reproduce

Fire up the UDP greeter example and add a sleep to the preStop hook to simulate graceful shutdown:
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
  labels:
    app: media-plane
  name: media-plane
spec:
  replicas: 1
  selector:
    matchLabels:
      app: media-plane
  template:
    metadata:
      labels:
        app: media-plane
    spec:
      containers:
      - args:
        - -d
        - -d
        - udp-l:9001,fork
        - EXEC:"echo Greetings from STUNner!"
        command:
        - /usr/bin/socat
        image: l7mp/net-debug:0.5.3
        lifecycle:
          preStop:
            exec:
              command:
              - sleep
              - "300"
        name: net-debug
      terminationGracePeriodSeconds: 300

Create a client connection:
export IPERF_ADDR=$(kubectl get pod -l app=media-plane -o jsonpath="{.items[0].status.podIP}")
turncat --log=all:TRACE - 'k8s://stunner/udp-gateway:udp-listener' udp://$IPERF_ADDR:9001
Hi
Greetings from STUNner!
...

Kill the udp-greeter pod but make sure to keep turncat open:
kubectl scale deployment media-plane --replicas=0

Sending anything on the turncat connection silently fails.

Expected behavior: The turncat connection should remain functional until the the backend pod finishes graceful shutdown.
Actual behavior: The connection breaks and the stunnerd logs show the below:
server.go:39: turn DEBUG: Received 8 bytes of udp from <IP_ADDRESS>:6078 on [::]:3478
server.go:49: turn DEBUG: Received DataPacket from <IP_ADDRESS>:6078
turn.go:356: turn DEBUG: Received ChannelData from <IP_ADDRESS>:6078
cluster.go:180: stunner-cluster-stunner/media-plane TRACE: Match: cluster "stunner/media-plane" of type STATIC, peer IP: <IP_ADDRESS>
cluster.go:186: stunner-cluster-stunner/media-plane TRACE: route: STATIC cluster with 1 endpoints
cluster.go:189: stunner-cluster-stunner/media-plane TRACE: considering endpoint "<IP_ADDRESS>"
server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:6078: failed writing to socket: peer port administratively prohibited

Versions
Latest master. The regression must have appeared during the stunnerd media routing rewrite.

Further investigations: turns out the problem is that we're still using the old Endpoints API for backend pod discovery, which does not consider terminating pods, instead of the modern EndpointSlice API, which does.
By default, Kubernetes removes all pod IPs from the Endpoints object that belong to "Terminating" backend pods. For the above example, after graceful shutdown starts we get and empty Endpoints resource:
apiVersion: v1
kind: Endpoints
metadata:
  name: media-plane
  namespace: default
  labels:
    app: media-plane

Since we use the endpoint IPs in this object for permission request handlers and for port-range filtering, we immediately break all existing connections to "Terminating" pods.
The EndpointSlice API, however, returns all the pod IPs, containing the Terminating ones as well:
apiVersion: discovery.k8s.io/v1
kind: EndpointSlice
metadata:
  name: media-plane-qzbrt
  namespace: default
  labels:
    app: media-plane
    kubernetes.io/service-name: media-plane
addressType: IPv4
ports:
- name: ""
  port: 9001
  protocol: UDP
endpoints:
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: false
    serving: true
    terminating: true
  nodeName: stunner

Observe the endpoint IP <IP_ADDRESS> with terminating: true: that's our terminating backend pod.
So the solution is to rewrite the gateway operator from the Endpoints API to the EndpointSlice API and then add the pod IPs for terminating pods to the list of permitted endpoints.

Addendum: with 2 "ready" and one "terminating" pods:
media-plane-55658cb4f5-hdw6c   1/1     Running       0          <IP_ADDRESS>
media-plane-55658cb4f5-pjp9c   1/1     Terminating   0          <IP_ADDRESS>
media-plane-55658cb4f5-vjvnz   1/1     Running       0          <IP_ADDRESS>

We get this EndpointSlice:
apiVersion: discovery.k8s.io/v1
kind: EndpointSlice
metadata:
  name: media-plane-qzbrt
  namespace: default
  labels:
    app: media-plane
    kubernetes.io/service-name: media-plane
ports:
- name: ""
  port: 9001
  protocol: UDP
addressType: IPv4
endpoints:
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: false
    serving: true
    terminating: true
  nodeName: stunner
  targetRef:
    kind: Pod
    name: media-plane-55658cb4f5-pjp9c
    namespace: default
    uid: 277d19b4-f5ab-4616-8024-4deebca8f7e9
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: true
    serving: true
    terminating: false
  nodeName: stunner
  targetRef:
    kind: Pod
    name: media-plane-55658cb4f5-vjvnz
    namespace: default
    uid: 965ae9b0-13c8-4145-a850-533b857876af
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: true
    serving: true
    terminating: false
  nodeName: stunner
  targetRef:
    kind: Pod
    name: media-plane-55658cb4f5-hdw6c
    namespace: default
    uid: 02a3e3e2-b83c-442c-afe4-4a7ad647bf19

I've tested this and the issue can no longer be reproduced with the new STUNner dev version that uses the EndpointSlice controller.

Fire up the UDP greeter example again but set terminationGracePeriodSeconds: 300 in the media-plane deployment.

Create a turncat tunnel and create a TURN allocation:
export IPERF_ADDR=$(kubectl get pod -l app=media-plane -o jsonpath="{.items[0].status.podIP}")
turncat --log=all:TRACE - 'k8s://stunner/udp-gateway:udp-listener' udp://$IPERF_ADDR:9001
Hi
Greetings from STUNner!
...

Scale the media-plane deployment down to 0 pods:
kubectl scale deployment media-plane --replicas=0

This will trigger the UDP greeter pod to enter into a TERMINATING state:
kubectl get pods
NAME                           READY   STATUS        RESTARTS   AGE
media-plane-55658cb4f5-d7h2l   1/1     Terminating   0          91s

And the turncat tunnel stays open:
...
Hi again after terminate
Greetings from STUNner!
And the connection remains open, isn't it?
Greetings from STUNner!
...

I am facing the same issue using the latest dev image (stunnerd:dev)
I am using stunner in AWS with netbird to manage a network mesh.
When I delete one of the pods there is some downtime. I am running a simple ping test, and some connections are lost.
Would it be possible to add lifecycle prestop policy in the gateway pods created via the dataplane template?
apiVersion: stunner.l7mp.io/v1
kind: Dataplane
metadata:
  annotations:
    meta.helm.sh/release-name: stunner-gateway-operator
    meta.helm.sh/release-namespace: stunner-system
  labels:
    app.kubernetes.io/managed-by: Helm
  name: default
spec:
  args:
  - -w
  - --udp-thread-num=16
  command:
  - stunnerd
  enableMetricsEndpoint: false
  hostNetwork: false
  image: docker.io/l7mp/stunnerd:dev
  imagePullPolicy: Always
  replicas: 2
  resources:
    limits:
      cpu: 2
      memory: 512Mi
    requests:
      cpu: 500m
      memory: 128Mi
  terminationGracePeriodSeconds: 3600
-----
  lifecycle:
     preStop:
        exec:
          command: ["/bin/busybox","sleep","5"]
----

Not sure if this is the cause, but in EKS endpoints are not renewed fast enough and this causes downtime on services.
I usually fix this by adding a prestop sleep of 5 seconds.
I am aware that stunnerd image does not have a sleep command, but this is easy to fix.
Meanwhile I will try kyverno to mutate pods at creation time to check if adding a lifecycle has a benefit.

I'm not hundred percent sure I get the problem right. Do you terminate a backend pod and this makes your connections break, or do you terminate a stunnerd pod and then this is what causes your connections to break?
My understanding is that it's case (2). Now, the question is, why are you killing your stunnerd pods? You're scaling down a STUNner Gateway? If you're doing this right then this should never make STUNner disconnect any live connections: stunnerd implements the graceful shutdown pattern so as long as there are live TURN allocations it should just keep running, at least for an hour as per terminationGracePeriodSeconds: 3600 setting. If stunnerd goes away before that and this breaks active connections, then that's a bug. If you're force-killing stunnerd for another reason then we'd like to know why before adding support for your use case.
NB: In retrospect it was a poor decision to limit the Dataplane spec to a few semi-random params we thought were important at that time. We're spending too much time adding stuff back from the Deployment spec to support specific use cases. We should have supported the full Deployment spec as is and then call it a day...

Thanks for fast response.
I have 3 replicas running of udp gateway to be in HA mode.
To simulate a k8s node downscale or pod rescheduling, I manually run a kubectl delete pod of one of the running replicas.
I do not execute a force delete, just a standard kubectl delete pod name.
I was able to add a mutation policy to add lifecycle prestop hook:
spec:
  containers:
  - args:
    - -w
    - --udp-thread-num=16
    command:
    - stunnerd
    env:
    - name: STUNNER_ADDR
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: status.podIP
    - name: STUNNER_NAME
      value: udp-gateway
    - name: STUNNER_NAMESPACE
      value: stunner
    - name: STUNNER_CONFIG_ORIGIN
      value: http://<IP_ADDRESS>:13478
    image:<PHONE_NUMBER>04.dkr.ecr.eu-west-1.amazonaws.com/docker-hub/marcportabellaclotet/stunner-sleep:latest
    imagePullPolicy: Always
    lifecycle:
      preStop:
        exec:
          command:
          - /bin/busybox
          - sleep
          - "5"

After adding the lifecycle, I am able to kubectl delete the pod, and the connection does not break,
ping output without lifecyle:
64 bytes from <IP_ADDRESS>: icmp_seq=921 ttl=63 time=202 ms
64 bytes from <IP_ADDRESS>: icmp_seq=922 ttl=63 time=110 ms
From <IP_ADDRESS> icmp_seq=930 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=931 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=933 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=934 Destination Host Unreachable
64 bytes from <IP_ADDRESS>: icmp_seq=935 ttl=63 time=4656 ms
64 bytes from <IP_ADDRESS>: icmp_seq=936 ttl=63 time=3651 ms

Adding the 5 second sleep avoids the downtime.
Note that I am using AWS NLB, which may take some little time to reconfigure the endpoints.
This is the config I am using:
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: udp-gateway
  namespace: stunner
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"  # For NLB
    service.beta.kubernetes.io/aws-load-balancer-subnets: "subnet-yyy,subnet-xxx,subnet-zzz"  # Replace with your subnet IDs
    service.beta.kubernetes.io/aws-load-balancer-internal: "false"  # Optional: For internal load balancer
    service.beta.kubernetes.io/aws-load-balancer-healthcheck-protocol: HTTP
    service.beta.kubernetes.io/aws-load-balancer-healthcheck-path: "/live"
    service.beta.kubernetes.io/aws-load-balancer-healthcheck-port: "8086"
spec:
  gatewayClassName: stunner-gatewayclass
  listeners:
    - name: udp-listener
      port: 3478
      protocol: TURN-UDP
---
apiVersion: stunner.l7mp.io/v1
kind: UDPRoute
metadata:
  name: stunner-headless
  namespace: stunner
spec:
  parentRefs:
    - name: udp-gateway
  rules:
    - backendRefs:
        - name: udp-gateway
          namespace: stunner

I'm afraid you're using graceful shutdown incorrectly. The idea is that as long as there are active TURN allocations STUNner will refuse to shut down even if the stunnerd pod is deleted (at least until the terminationGracePeriod passes). If, however, there are no active allocations, there is no harm in removing a stunnerd  pod so it will terminate immediately on being deleted.  You should see your connection remaining open, despite the stunnerd pod entering the TERMINATE state. In this case, there's no reason to add a preStop hook. If this is not what's happening, please file an issue because that's a serious bug we have to investigate and fix.

Now we're talking!...:-) Interesting. Is this AWS/EKS?
Anyway, by design STUNner does accept new connections during graceful shutdown exactly to address buggy/slow load balancers. This makes the prestop hook unnecessary. Do you have actual tests where this fails?

Thanks for looking into this.
I am not able to reproduce the issue any more.
Even grace-deleting all the running stunnerd pods, the connection persists stable.

We're so grateful you tested this! Graceful shutdown is one of the most critical features a cloud-native software must provide but getting this right, especially for gateways, is quite difficult. STUNner's graceful shutdown codepath was broken for a long time and I'm so happy we could finally restore this useful feature before v1!

We will perform some intensive testing in the next days. I will share feedback.
Thanks


[FEATURE REQUEST]  RVC 2.0 48k Sample rate?

There are now 48k v2 models and a fork with a hybrid training feature. Are they any better?
https://github.com/Mangio621/Mangio-RVC-Fork
Files from YT are generally 48k. The only issue is the demucs models mainly do 44.1, although demucs can supposedly support 24bit.
https://github.com/facebookresearch/demucs/issues/288
Am unsure how upsample vs downsample works out for final output.

They might be better, i'll implement it. Not immediately though, i'm currently making an improved install system.

No worries. For install I actually reused my nvida environment and added the handful of extra packages so I always bypass the venv entirely.

I'd like to request adding the option of using the "mango-crepe" algorithm too for training and generating

While adding v2 48k i realized v1 48k doesn't work, i have some fixing to do

Yea.. you're right. I had tried V1 48k and assumed something was wrong with my system instead.

Yeah, once i fix that, v2 48k should also work

I will try to re-run some datasets and see if the quality is higher. If only any demucs supported 48k. With already clean samples or self-recorded audio it will probably be a nice improvement.

48k failed for me on training. I got the d/s converted. The 2nd wav folder doesn't generate files. The one where the # of items would be double. All the other ones happen but training goes down on tensor shape/size.

48k failed for me on training. I got the d/s converted. The 2nd wav folder doesn't generate files. The one where the # of items would be double. All the other ones happen but training goes down on tensor shape/size.

That message above was one message not 2, it said once i fix that, v2 48k should also work, but i haven't worked on fixing it yet.

Fair, I'm just saying how far I got testing it.

48k failed for me on training. I got the d/s converted. The 2nd wav folder doesn't generate files. The one where the # of items would be double. All the other ones happen but training goes down on tensor shape/size.

That message above was one message not 2, it said once i fix that, v2 48k should also work, but i haven't worked on fixing it yet.

Hi Mylo!, is v2 48k working currently or shall we wait?

48k failed for me on training. I got the d/s converted. The 2nd wav folder doesn't generate files. The one where the # of items would be double. All the other ones happen but training goes down on tensor shape/size.

That message above was one message not 2, it said once i fix that, v2 48k should also work, but i haven't worked on fixing it yet.

Hi Mylo!, is v2 48k working currently or shall we wait?

Not yet, i haven't really been working on it, 48k works in inference by the way, just not during training.


UDP support for Astra K protocol

As described on received manual, the protocol is the same for TCP and UDP.

Added one comment. Please fix it and I'll merge the changes.

Merged, thanks for pull request.


Open Folder Button for Backups

As per open folder button for logs. Would be good and consistent to have one for backups too.

@amitnndn looks like another perfect one for you :)

I've created the button, pushing a commit now

Had a lot of IRL stuff happen recently, but I’ll try to pick this back up 🙂
On Tue, Sep 18, 2018 at 12:22 PM Thomas Zarebczan<EMAIL_ADDRESS>wrote:

@Grayyyyy https://github.com/Grayyyyy planning to pick your PR back up?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/issues/1601#issuecomment-422477531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkCIiPABgjSPl-9kJaoeGntoij32rgQyks5ucSvVgaJpZM4Upjb0
.

This is implemented in the latest app along with a way to zip a backup.


chore: Adds TLS team as code owners

Description
Adds the TLS team as a code owner here to automatically assign PR's to the team.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Duplicate of PR #6


[Feature Request]: Auto unit test after commit

Is there an existing issue for the feature request?

[X] I have checked the existing issues.

Feature Description
Create a git workflow which will be triggered every time when a new commit is submitted and an auto run test will be run to cover every major function of mo_ctl standalone, such as deploy, start, status, upgrade, ... , etc.
Feature Implementation
see above
Additional information
see above

done, closing it


Trying to fix notebook download issue

It may be because I did not apply my fix to every request

Change Description

[ ] My PR includes a link to the issue that I am addressing

Solution Description

Code Quality

[ ] I have read the Contribution Guide
[ ] My code follows the code style of this project
[ ] My code builds (or compiles) cleanly without any errors or warnings
[ ] My code contains relevant comments and necessary documentation

Project-Specific Pull Request Checklists

Bug Fix Checklist

[ ] My fix includes a new test that breaks as a result of the bug (if possible)
[ ] My change includes a breaking change

[ ] My change includes backwards compatibility and deprecation warnings (if possible)

New Feature Checklist

[ ] I have added or updated the docstrings associated with my feature using the NumPy docstring format
[ ] I have updated the tutorial to highlight my new feature (if appropriate)
[ ] I have added unit/End-to-End (E2E) test cases to cover my new feature
[ ] My change includes a breaking change

[ ] My change includes backwards compatibility and deprecation warnings (if possible)

Documentation Change Checklist

[ ] Any updated docstrings use the NumPy docstring format

Build/CI Change Checklist

[ ] If required or optional dependencies have changed (including version numbers), I have updated the README to reflect this
[ ] If this is a new CI setup, I have added the associated badge to the README

Other Change Checklist

[ ] Any new or updated docstrings use the NumPy docstring format.
[ ] I have updated the tutorial to highlight my new feature (if appropriate)
[ ] I have added unit/End-to-End (E2E) test cases to cover any changes
[ ] My change includes a breaking change

[ ] My change includes backwards compatibility and deprecation warnings (if possible)

I think I needed to make a pull request to get readthedocs to attempt a build.

Ok I think this has done it:
https://readthedocs.org/projects/lephare/builds/26475119/
@olivierilbert or @johannct Can I get an approval?


Getting offchain-worker 'canonicalize elem' error on Rococo fork

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
I am getting the error message below on custom relay chain, forked from Rococo wich custom chain specs, runtime is rococo/9310.
The error happens at every block imported, on both archive and full nodes.
The error is non blocking, the node is still syncing fine.

Changing offchain indexing as suggested in #12531 doesn't make error disapear.
Only disabling offchain worker makes the message disapear.

offchain-worker runtime::mmr::offchain: Could not canonicalize elem at pos 1571016 using key [12, 109, 109, 114, 200, 248, 23, 0, 0, 0, 0, 0, 205, 224, 155, 51, 228, 136, 22, 253, 163, 126, 202, 74, 161, 246, 254, 237, 111, 67, 51, 108, 127, 168, 102, 5, 104, 222, 99, 72, 216, 169, 63, 75]

Below is a larger debug log of the node
2023-01-03 08:44:18.033 DEBUG tokio-runtime-worker wasm_overrides: No WASM override available for block BlockId::Hash(0x02c32c12ea7b2509a1b0b6afe7d5f81d236ab6644ad30fe33622e6528b771d31), using onchain code
2023-01-03 08:44:18.032 DEBUG      offchain-worker wasm-heap: allocator dropped: AllocationStats { bytes_allocated: 520, bytes_allocated_peak: 2160, bytes_allocated_sum: 13632, address_space_used: 2848 }
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Clear kind=StorageKind::PERSISTENT key="0c6d6d72caf8170000000000700ba95688504ac51c508e4e8f7ecdabf71981b179051abcbd1c126c234ffe52"
2023-01-03 08:44:18.032 DEBUG      offchain-worker runtime::mmr::offchain: Clear elem at pos 1571018 with key [12, 109, 109, 114, 202, 248, 23, 0, 0, 0, 0, 0, 112, 11, 169, 86, 136, 80, 74, 197, 28, 80, 142, 78, 143, 126, 205, 171, 247, 25, 129, 177, 121, 5, 26, 188, 189, 28, 18, 108, 35, 79, 254, 82]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Clear kind=StorageKind::PERSISTENT key="0c6d6d72c9f8170000000000700ba95688504ac51c508e4e8f7ecdabf71981b179051abcbd1c126c234ffe52"
2023-01-03 08:44:18.032 DEBUG      offchain-worker runtime::mmr::offchain: Clear elem at pos 1571017 with key [12, 109, 109, 114, 201, 248, 23, 0, 0, 0, 0, 0, 112, 11, 169, 86, 136, 80, 74, 197, 28, 80, 142, 78, 143, 126, 205, 171, 247, 25, 129, 177, 121, 5, 26, 188, 189, 28, 18, 108, 35, 79, 254, 82]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Clear kind=StorageKind::PERSISTENT key="0c6d6d72c8f8170000000000700ba95688504ac51c508e4e8f7ecdabf71981b179051abcbd1c126c234ffe52"
2023-01-03 08:44:18.032 DEBUG      offchain-worker runtime::mmr::offchain: Clear elem at pos 1571016 with key [12, 109, 109, 114, 200, 248, 23, 0, 0, 0, 0, 0, 112, 11, 169, 86, 136, 80, 74, 197, 28, 80, 142, 78, 143, 126, 205, 171, 247, 25, 129, 177, 121, 5, 26, 188, 189, 28, 18, 108, 35, 79, 254, 82]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Clear kind=StorageKind::PERSISTENT key="0c6d6d726bfc0b002c7072756e696e675f6d6170"
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Read kind=StorageKind::PERSISTENT key="0c6d6d726bfc0b002c7072756e696e675f6d6170" result=Some("04700ba95688504ac51c508e4e8f7ecdabf71981b179051abcbd1c126c234ffe52")
2023-01-03 08:44:18.032 ERROR      offchain-worker runtime::mmr::offchain: Could not canonicalize elem at pos 1571018 using key [12, 109, 109, 114, 202, 248, 23, 0, 0, 0, 0, 0, 205, 224, 155, 51, 228, 136, 22, 253, 163, 126, 202, 74, 161, 246, 254, 237, 111, 67, 51, 108, 127, 168, 102, 5, 104, 222, 99, 72, 216, 169, 63, 75]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Read kind=StorageKind::PERSISTENT key="0c6d6d72caf8170000000000cde09b33e48816fda37eca4aa1f6feed6f43336c7fa8660568de6348d8a93f4b" result=None
2023-01-03 08:44:18.032 ERROR      offchain-worker runtime::mmr::offchain: Could not canonicalize elem at pos 1571017 using key [12, 109, 109, 114, 201, 248, 23, 0, 0, 0, 0, 0, 205, 224, 155, 51, 228, 136, 22, 253, 163, 126, 202, 74, 161, 246, 254, 237, 111, 67, 51, 108, 127, 168, 102, 5, 104, 222, 99, 72, 216, 169, 63, 75]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Read kind=StorageKind::PERSISTENT key="0c6d6d72c9f8170000000000cde09b33e48816fda37eca4aa1f6feed6f43336c7fa8660568de6348d8a93f4b" result=None
2023-01-03 08:44:18.032 ERROR      offchain-worker runtime::mmr::offchain: Could not canonicalize elem at pos 1571016 using key [12, 109, 109, 114, 200, 248, 23, 0, 0, 0, 0, 0, 205, 224, 155, 51, 228, 136, 22, 253, 163, 126, 202, 74, 161, 246, 254, 237, 111, 67, 51, 108, 127, 168, 102, 5, 104, 222, 99, 72, 216, 169, 63, 75]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Read kind=StorageKind::PERSISTENT key="0c6d6d72c8f8170000000000cde09b33e48816fda37eca4aa1f6feed6f43336c7fa8660568de6348d8a93f4b" result=None
2023-01-03 08:44:18.032 DEBUG      offchain-worker runtime::mmr::offchain: Nodes to canon for leaf 785515: [1571016, 1571017, 1571018]
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Write kind=StorageKind::PERSISTENT key="0c6d6d726a0c0c002c7072756e696e675f6d6170" value="042fb7b2bfc5f81290725a546c77a6b0fc8248cf3a0ad7f7dbc95b041269cd85c6"
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker::storage: Read kind=StorageKind::PERSISTENT key="0c6d6d726a0c0c002c7072756e696e675f6d6170" result=None
2023-01-03 08:44:18.032 DEBUG      offchain-worker wasm_overrides: No WASM override available for block BlockId::Hash(0x02c32c12ea7b2509a1b0b6afe7d5f81d236ab6644ad30fe33622e6528b771d31), using onchain code
2023-01-03 08:44:18.032 DEBUG      offchain-worker offchain-worker: Running offchain workers at BlockId::Hash(0x02c32c12ea7b2509a1b0b6afe7d5f81d236ab6644ad30fe33622e6528b771d31)

Steps to reproduce

Download Tokyo network custom chain specs
Spin up a Polkadot node using Tokyo chain specs

CC @acatangiu

The issue is fixed starting with runtime rococo/9340.
(fixed in https://github.com/paritytech/polkadot/commit/3f288d36554fb49715eabfe880b5c19e5c59e235)

Thanks for the heads up, we'll just have to upgrade runtime then.


refactor(netlify): rename temporary versioned presets

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
"v1" and "v2", introduced in https://github.com/unjs/nitro/pull/2406, are loaded terms that add unnecessary confusion here.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks. It will be applied to the new structure as mentioned in previous PR , merge was to allow quickly iterating and not having your work stalled


[feature] Polymath.connect() to accept private key or mnemonics

Otherwise, the SDK could only be used either with Metamask, or a local, permenantly unlocked geth or parity nodes.

This is already implemented. The connect method has an overload which requires a provider url and a privateKey.
This way let us use it as you said, with any other remote node.
The providers logic on our contract-wrappers allow us to offer different more alternatives in the future but currently both you mentioned are working.

Thanks @VictorVicente. I have no idea how I overlooked that.


Project-scoped feeds need project permissions too

@jmyersmsft Thank you for your contribution! #sign-off


Call home ssh does not get hello from netopeer2

Hi,
I have managed to setup a connection with trilead ssh2 ( with modifications in the library)
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
SLF4J: Defaulting to no-operation MDCAdapter implementation.
SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Datastore copied from <startup> to <running>.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Connection 1 created.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Listening on <IP_ADDRESS>:830 for SSH connections.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-keystore" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-truststore" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
Oct 18, 2024 10:15:36 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of NACM file imported into docker.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of NACM file executed in docker.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of SSH Auth method file imported into docker.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0'  of SSH Auth method file executed.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of SSH Call Home file imported into docker.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Call Home client "default-client" endpoint "ssh-default" connecting...
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: getsockopt() error (Connection refused).
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv6 to ::1:4334.
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINEST: [ERR]: LN: connect() failed (Cannot assign requested address).
Oct 18, 2024 10:15:37 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of SSH Call Home file executed.
Oct 18, 2024 10:15:38 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0' of Enable SSH Call Home Query file imported into docker.
Oct 18, 2024 10:15:38 AM com.trilead.ssh2.log.Logger log
FINER: Message '' and result '0'  of Enable SSH Call Home Query file sent.

Oct 18, 2024 10:15:42 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
Oct 18, 2024 10:15:42 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: getsockopt() error (Connection refused).
Oct 18, 2024 10:15:42 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv6 to ::1:4334.
Oct 18, 2024 10:15:42 AM com.trilead.ssh2.log.Logger log
FINEST: [ERR]: LN: connect() failed (Cannot assign requested address).
Oct 18, 2024 10:15:47 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
Oct 18, 2024 10:15:47 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
Oct 18, 2024 10:15:47 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: getsockopt() error (Connection refused).
Oct 18, 2024 10:15:47 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv6 to ::1:4334.
Oct 18, 2024 10:15:47 AM com.trilead.ssh2.log.Logger log
FINEST: [ERR]: LN: connect() failed (Cannot assign requested address).
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: Call Home SSH accepted connection on host <IP_ADDRESS> on port 4334
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Call Home client "default-client" endpoint "ssh-default" failed connection attempt limit 3 reached.
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Call Home client "default-client" endpoint "default-ssh" connecting...
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
Oct 18, 2024 10:15:53 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Successfully connected to host.testcontainers.internal:4334 over IPv4.

Oct 18, 2024 10:15:58 AM com.trilead.ssh2.log.Logger log
FINEST: Received SSH_MSG_SERVICE_ACCEPT 17 bytes payload
Oct 18, 2024 10:15:58 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Received an SSH message "request-auth" of subtype "none".

Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: User "netconf" authenticated.
Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINER: Sending SSH_MSG_CHANNEL_OPEN (Channel 100)
Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINEST: Sent SSH_MSG_CHANNEL_OPEN 24 bytes payload
Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINEST: Received SSH_MSG_CHANNEL_OPEN_CONFIRMATION 17 bytes payload
Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINEST: [INF]: LN: Received an SSH message "request-channel-open" of subtype "session".
Oct 18, 2024 10:16:04 AM com.trilead.ssh2.log.Logger log
FINER: Got SSH_MSG_CHANNEL_OPEN_CONFIRMATION (channel 100 / remote: 43)
Oct 18, 2024 10:20:20 AM com.trilead.ssh2.log.Logger log
FINEST: Sent SSH_MSG_CHANNEL_DATA 178 bytes payload

I can see that the client sends a message
INEST: Sent SSH_MSG_CHANNEL_DATA 178 bytes payload
The hello message we send is:
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>
]]>]]>

Any ideas why I don't see a response from the Netopeer2 when sending.
Are we missing anything before we send the hello?
br,
//mike

I do not see the request for netconf SSH subsystem, which is the last SSH task preceding NETCONF communication.

My bad! Thx


login email missing button

@ethanneff looks like there might be an issue with your email client, as there should be a sign in button below the Maestro Cloud title like below:


Feedback system choices are incomplete

So the feedback system choices of "Documentation Problem", or "Uservoice feedback" are incomplete.
We need a choice that goes to the forum to log bugs.
-thanks
-e

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

ID: 4d9d4670-d8f7-2c1a-b93c-2d260f32ab84
Version Independent ID: 6756005b-8c21-9dac-3837-340b30565078
Content: Copy data from HubSpot using Azure Data Factory (Preview)
Content Source: articles/data-factory/connector-hubspot.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@ericleigh007 We appreciate your feedback! The "Product Feedback"  button on the docs pages takes you to the UserVoice website. Currently you can send us feedback but also report bugs via UserVoice website or in the portal using the feedback button (smile) in the top bar in the portal. If you have any more  suggestions or if you would like to provide more details on what you are thinking we would love to hear them. Thank you.

@ericleigh007 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Fix FUGUE bug

Closes #752.
Changes proposed in this pull request

Add test using multi-shell DWI data with a GRE field map, using data from https://openneuro.org/datasets/ds005299/versions/1.0.0.
Add single-shell + GRE test, using data from https://openneuro.org/datasets/ds000113/versions/1.3.0.
Copy over FUGUEvsm2ANTSwarp interface from old version of QSIPrep.

We'll probably want to replace the overall workflow with SDCFlows at some point.

The maternal brain project test succeeds, but doesn't produce any outputs.

Codecov Report
Attention: Patch coverage is 17.02128% with 78 lines in your changes missing coverage. Please review.

Project coverage is 29.84%. Comparing base (555556c) to head (57105e4).

Files
Patch %
Lines

qsiprep/interfaces/niworkflows.py
16.30%
77 Missing :warning:

qsiprep/workflows/fieldmap/unwarp.py
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #769      +/-   ##
==========================================
+ Coverage   29.77%   29.84%   +0.06%
==========================================
  Files          97       97
  Lines       14577    14668      +91
  Branches     1885     1898      +13
==========================================
+ Hits         4341     4377      +36
- Misses      10110    10163      +53
- Partials      126      128       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@mattcieslak it's working! Can you review when you have some time?


Support for vite 3.0.0 ?

Support for vite 3.0.0?

What's the problem?
I just adopt my plugin vite-plugin-wasm to Vite 3 and found this plugin worked out of the box.

What I mean is that when I install it with pnpm this is what I got:
vite-plugin-top-level-await
  └── ✕ unmet peer<EMAIL_ADDRESS>found 3.0.0

It seems you already fixed it in last release. So thank you!!! Closing it then. I do not see this warning anymore

I just edited the peerDependencies version.


Replace tools/deploy.py with directions for apigeetool

https://github.com/apigee/api-platform-tools

I added a note about apigeetool with a link to it's documentation in the README. For now, samples will continue to use the python deploy tool, but we may switch to apigeetool in the future.


MSC3394: New auth rule that only allows someone to post a message in relation to another message

Rendered

Also, please wrap your lines after ~120 characters

This will 100% need sign off so il just point that out.

MSCs need to spell out the details for how they will achieve their goals.  e.g. in this case, what property is used in what state event to indicate who is allowed to post replies, how you determine what's top-level vs. a reply, etc.  I'm going to mark this as a draft for now.


file manager is not working

I tried to re-install the package and nothing changed :( help please!

first you go to you Application and go back to public folder and then remove storage file
then run command php artisan storage:link
then solve your problem

thank you !

I have the same issue as the images above, I have removed storage folder and then run command php artisan storage:link but it just created the folder storage/files/1 in public folder with no images.

even i have the same issue, i did remove the storage file and tried but I still have the same issue.

@dkklimo Fixed this issue please pull latest code.
https://github.com/Prajwal100/Advance-Ecommerce-in-laravel-7/issues/57


Work around SNI error: unrecognized_name

Fix the issue that was introduced in Java 1.7. The issue is discussed here:
http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0
Servers that have a misconfigured SNI may return a SSL error response: "handshake alert: unrecognized_name". This triggers an exception in the Java SSL machinery which is not caught by HttpClient by default, causing the request to fail. However, all common browsers ignore this alert and do not indicate it to the user in any way. Therefore, a crawler should preferably also ignore this error.
This patch implements a work-around that catches this exception, logs it and retries the same connection without a hostname, effectively disabling SNI for that host. It is strongly based on the fix provided by Ivan Shcheklein, available on:
http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0/28571582#28571582
Main difference to that code is that this version extends PoolingHttpClientConnectionManager rather than HttpClientConnectionOperator, which has been deprecated in HttpClient 4.3.
Optionally, this could become a setting in the CrawlConfiguration if you feel that is more appropriate. If you think so, let me know and I'll modify it that way.

Can you share a website that has this issue?

Certainly, I've got plenty of examples from the logfiles of my crawler, each of which open perfectly fine in my browser (both Firefox and Chrome).
https://us.energetix.tv
https://nieuws.mijndomein.nl
https://shop.cloudwise.nl
https://www.inqdo.com
https://access.caltech.edu
https://amersfoort.groenlinks.nl
The SSL test at https://www.ssllabs.com/ssltest/ also identifies whether a website would result in this error on Java7 or Java8.

@MadEgg Do you know, if this is still a problem in Java 8 ?

I'm pretty sure it is - like I said, the SSLLabs test shows that it will occur. For example, trying the first URL I mentioned:
https://www.ssllabs.com/ssltest/analyze.html?d=us.energetix.tv
Shows the following:
Java 7u25 	Client aborts on SNI unrecognized_name warning
Java 8u31 	Client aborts on SNI unrecognized_name warning
I've had this patch in place ever since so I can't be sure. I can rebuild without this patch and try one of these sites, I'll get back as soon as I find the time to conduct that experiment, in the next couple of days.

Merged in 9653c47


Modal closes on file input select, breaks UI flow

when User clicks browse in file input then modal closes and error is thrown in js console:

Fixed in 7cf3df702f54de289d2ca1d53886d5f4baaa4d92


Alertmanager with class E IP addresses

This could be considered a bug / edge case or a feature request, it's somewhere in between. Some enterprises use private networks outside of RFC 1918, for example Class E networks. These are necessary for enterprises that have exhausted or otherwise allocated all RFC 1918 address space. I would like for alertmanager to accept IP addressed like these.
What did you do?
Provision alertmanager on GKE using Class E, private pod IP addresses https://cloud.google.com/vpc/docs/vpc#valid-ranges
What did you expect to see?
Normal alertmanager, same as using RFC 1918 address space.
What did you see instead? Under which circumstances?
"No private IP address found, and explicit IP not provided"
Environment
GKE, host network using a normal, private subnet and pods and services using Class E. Using these IPs is the source of the issue.

Alertmanager version 0.20.0
k get pods -o wide | grep alert
astro-alertmanager-0                                  0/1     CrashLoopBackOff   61         4h49m   <IP_ADDRESS>   gke-steven-active-steven-default-node-eba56e82-11nc   <none>           <none>

Logs:

level=info ts=2020-12-21T19:41:02.158Z caller=main.go:231 msg="Starting Alertmanager" version="(version=0.20.0, branch=HEAD, revision=f74be0400a6243d10bb53812d6fa408ad71ff32d)"
level=info ts=2020-12-21T19:41:02.159Z caller=main.go:232 build_context="(go=go1.13.5, user=root@00c3106655f8, date=20191211-14:13:14)"
level=warn ts=2020-12-21T19:41:02.159Z caller=cluster.go:154 component=cluster err="couldn't deduce an advertise address: no private IP found, explicit advertise addr not provided"
level=error ts=2020-12-21T19:41:02.160Z caller=main.go:256 msg="unable to initialize gossip mesh" err="create memberlist: Failed to get final advertise address: No private IP address found, and explicit IP not provided"

For now, Alertmanager mandates that you specify the advertised address if it can't deduce an address in a range covered by RFC 6890 (as mentioned in the README.md). You should be able to resolve this by getting the pod's IP address from the downward API and binding the cluster listener to this address explicitly (e.g. --cluster.advertise-address=$(POD_IP):9094).

Hi @simonpasquier thank you for your help, I will give this a shot.

@simonpasquier , I am following up for @sjmiller609 . I have tried this and it works. Thank you.

@simonpasquier Thanks for your tip. If I understand correctly, the point of checking if it's in RFC 6890 is in order to prevent users from accidentally serving on a public network. Unless you think that adding class E is reasonable and beneficial to add into accepted range (since they are not public IPs), I am fine with having this issue closed because there is an option that works. Thanks again for your help.


Is the mlip dependency really necessary?

Comment:
We are running a custom build executable for the mlip package on our cluster, but are still running the conda lammps as well.  Since this package forces the install of mlip, this causes some issues, as there's two binaries in the PATH of users the conda one seems to take precedence over it sometimes.
Therefore the question: Is it really necessary to include mlip in the dependencies or could it also be an optional dependency or be removed completely.  Since this package only needs the mlip library interface and not the executable to fit potentials, I would guess that the dependency can be safely dropped.  Or does the library interface reference a shared library from the mlip conda package?

We are running a custom build executable for the mlip package on our cluster, but are still running the conda lammps as well. Since this package forces the install of mlip, this causes some issues, as there's two binaries in the PATH of users the conda one seems to take precedence over it sometimes.

The precedence only depends on the order of the entries in your PATH, so I do not understand why you cannot overwrite it.

Therefore the question: Is it really necessary to include mlip in the dependencies or could it also be an optional dependency or be removed completely. Since this package only needs the mlip library interface and not the executable to fit potentials, I would guess that the dependency can be safely dropped. Or does the library interface reference a shared library from the mlip conda package?

I guess there are users who might want to use the conda package to try the mlip potential fitting so I am a bit reluctant to remove the executables. What could be possible is splitting the library and the executable into separate packages inside https://github.com/conda-forge/mlip-feedstock/

We are running a custom build executable for the mlip package on our cluster, but are still running the conda lammps as well. Since this package forces the install of mlip, this causes some issues, as there's two binaries in the PATH of users the conda one seems to take precedence over it sometimes.

The precedence only depends on the order of the entries in your PATH, so I do not understand why you cannot overwrite it.

We can overwrite it and we do now.  But it is annoying to have to work around a package that we didn't install and don't need.

Therefore the question: Is it really necessary to include mlip in the dependencies or could it also be an optional dependency or be removed completely. Since this package only needs the mlip library interface and not the executable to fit potentials, I would guess that the dependency can be safely dropped. Or does the library interface reference a shared library from the mlip conda package?

I guess there are users who might want to use the conda package to try the mlip potential fitting so I am a bit reluctant to remove the executables. What could be possible is splitting the library and the executable into separate packages inside https://github.com/conda-forge/mlip-feedstock/

I don't see why those users cannot easily install the mlip package from conda into their environment.  pyiron users who want to do so cannot use the old mlip binary anyway.  I did a ldd lmp_mpi and cannot make out any dynamic library dependence between the lammps binary and the mlip conda package.  I guess the mlip library is linked statically into the lammps executable (that's at least also how it is done for the newer mlip versions).  Therefore the mlip dependency could be dropped without any change in the binary or splitting the mlip package up.


Incorrect breadcrumb type

The commandStartingHandler, queueJobProcessingHandler, messageLoggedHandler and queryExecutedHandler use the User breadcrumb type, which does not make a sense, because none of those are related to a user. Especially in a cli environment.
Current behavior

All logs and all other type of laravel framework events that are handled by this package use the user breadcrumb type by default.
Expected behavior

Default breadcrumb type should be the default type. If someone wants to add a breadcrumb that is related to a user, use the sentry facade or service directly or extend the event handler to add additional functionality.

I’d be happy accepting a PR fixing this if you’re up for that?

One question, where should I write the issue about missing highlighting of the FATAL level?
I mean we have some orange highlighting for warnings, red for error, but the most severe level looks like default. :)

Let me check with the team what types are supported in the UI and what they are supposed to mean to the user. I think “user” level events might mean something else depending on who you ask. I’ll get back to you with that!

@TheLevti just a quick follow up, are you on 1.4.x or 1.5.x of sentry/sentry-laravel?

Can you let me know a bit more what code you used to generate those breadcrumbs since I thought #296 was supposed to fix this issue actually.

It was fixed. 1.5 I am using. The correct breadcrumb level is sent to sentry. Even the css classes are applied (fatal), but there is no styling for it. Its more of a frontend issue.

The problem is not the SDK side. The problem is that the frontend has no styling for the FATAL breadcrumb level.

Route::get('/debug-sentry', function () {
    Log::debug('Debug log {debug_context}', ['debug_context' => 1]);
    Log::info('Info log {debug_context}', ['debug_context' => 2]);
    Log::notice('Notice log {debug_context}', ['debug_context' => 3]);
    Log::warning('Warning log {debug_context}', ['debug_context' => 4]);
    Log::error('Error log {debug_context}', ['debug_context' => 5]);
    Log::critical('Critical log {debug_context}', ['debug_context' => 6]);
    Log::alert('Alert log {debug_context}', ['debug_context' => 7]);
    Log::emergency('Emergency log {debug_context}', ['debug_context' => 8]);

    throw new Exception('My first Sentry error!');
});

Is what I used for my example.

If you inspect with the browser the elements, you can see that critical, alert and emergency correctly got the crumb-fatal css class assigned. I inspected the CSS file, but no style is defined for this level.

Any news on this? Pull request for this issue is already provided.


csi.trident pluginregistration.Registration errors in kubelet logs

Describe the bug
On Kubernetes versions 1.15 and greater, kubelet has a dynamic plugin registration mechanism that discovers all sockets in /var/lib/kubelet/plugin using grpc GetInfo calls.  But, trident-csi node-driver-registrar container already registers the plugin.  So, the Kubelet's default discovery leads to lot of noise in kubelet logs like below:
Can you please confirm this is harmless in case of trident csi also ?
kubelet: I0121 13:40:31.450593   36037 reconciler.go:156] operationExecutor.RegisterPlugin started for plugin at "/var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock" (plugin details: &{/var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock true 2020-01-21 13:05:48.192444146 -0800 PST m=+3.508661885})
kubelet: I0121 13:40:31.450638   36037 operation_generator.go:193] parsed scheme: ""
kubelet: I0121 13:40:31.450667   36037 operation_generator.go:193] scheme "" not registered, fallback to default scheme
kubelet: I0121 13:40:31.450706   36037 asm_amd64.s:1337] ccResolverWrapper: sending new addresses to cc: [{/var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock 0  <nil>}]
kubelet: I0121 13:40:31.450720   36037 clientconn.go:796] ClientConn switching balancer to "pick_first"
kubelet: I0121 13:40:31.450766   36037 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000d73140, CONNECTING
kubelet: I0121 13:40:31.450904   36037 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000d73140, READY
kubelet: E0121 13:40:31.451325   36037 goroutinemap.go:150] Operation for "/var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock" failed. No retries permitted until 2020-01-21 13:42:33.451301322 -0800 PST m=+2208.767519081 (durationBeforeRetry 2m2s). Error: "RegisterPlugin error -- failed to get plugin info using RPC GetInfo at socket /var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock, err: rpc error: code = Unimplemented desc = unknown service pluginregistration.Registration"
kubelet: I0121 13:40:31.451328   36037 controlbuf.go:382] transport: loopyWriter.run returning. connection error: desc = "transport is closing"

Environment
Provide accurate information about the environment to help us reproduce the issue.

Trident version: 19.10
Container runtime: Docker 18.09.9-CE
Kubernetes version: [e.g. 1.15.9

To Reproduce
Install trident-csi on Kubernetes > v1.14.x
Expected behavior
See https://github.com/kubernetes/kubernetes/issues/70485#issuecomment-434711753.  Trident should either move the registration path outside of /var/lib/kubelet/plugin/  or name the file not ending with .sock.
Additional context
See https://github.com/kubernetes/kubernetes/issues/70485#issuecomment-434711753
Can you please confirm this is harmless in case of trident csi also ?  If so, can we move the registration path outside of /var/lib/kubelet/plugin/ ?

I am getting those errors and the specific nodes are not comming back to "Ready" after the upgrade, they stay at Ready,SchedulingDisabled

Still getting these errors even with trident v21.01.1, k8s v1.16.   Any updates?

Closing this issue as the reported log message was harmless and has been fixed in Kubernetes.


URI for go "shorthand" annotation is not resolving.

Its my understanding that all URI's associated with ontology terms should resolve?  But
http://www.geneontology.org/formats/oboInOwl%23shorthand breaks, and\

http://www.geneontology.org/formats/oboInOwl#shorthand

yields an RDF file that has no mention of "shorthand" in it. I see file is dated from 2012.  Was a past decision made to phase out "shorthand" in favour of "hasSynonym" ? I want to hold onto semantics that things like MIC and LASER as abbreviations (if not acronyms).
Secondly I wanted to know if shorthand is an annotation that also covers abbreviation annotations.  Currently there is http://purl.obolibrary.org/obo/HP_0045077 which I was going to use, but I see GO shorthand seems much more common.

Hi Damion,
This isn't really in scope for GO, the oboInOwl vocabulary is housed with us for historic reasons, but it is used by multiple applications.
The shorthand property has nothing to do with synonyms. You can find a technical description of it here http://owlcollab.github.io/oboformat/doc/obo-syntax.html (TL;DR - you don't need to worry about it if you aren't using obo format).
We don't indicate abbreviations in any systematic way in GO. You may want to look at how Uberon annotates a synonym as being an abbreviation: https://github.com/obophenotype/uberon/wiki/Using-uberon-for-text-mining
Follow up any Qs on https://github.com/information-artifact-ontology/ontology-metadata/issues
Thanks!


Remove use of str2octs from pyasn1

pyasn1 has been removing all Python 2 code from its codebase, and the octets module has been removed from 0.6.1 onwards. Since we only support Python 3.8, we can remove it and just encode to bytes.

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


MUMUP-2163 Add events search as a recover option

Adds "Search for events instead" as another no-search-results recovery option.
This tweak is intended to be responsive to a request around content in MyUW supporting the AAU Survey Student Engagement Sessions without committing MyUW to adding a portlet-definition, widget, entry in the directory of apps, notification, etc., supporting these three point-in-time events.
The specific zero-search-results search that raised the concern was a search for "sexual assault" and concern that this yields no search results. The compromise initial response is "we're not able to immediately make that search term directly yield useful content, but if people were searching for this event, they'll see a search recovery option that looks like a next step for looking for an event."

:+1:


All php files have to access credentials from the newly created .env file

Description
db credentials are hardcoded in each file , now .env file exists
Expected Behavior
All php files have to access credentials from .env file

Thanks for assigning this to me :)


ember-rfc176-data

@ynnoj Is there any ongoing work for ember-rfc176-data?

Closed by #195. Thanks @davidbilling 🎉


Authentication Version 1

I'll provide more info on what they need but essentially it only has to work for 1 email address.

Get the correct rules on the database
Figure out how to get auth token and make authenticated request to firebase


handle wq job estimation failure

fixes #8035

Although all the WQ element has to have more than 0 jobs. There is a case job count update fails. (I guess some network problem)  Since there is no retry mechanism and it is handled by LQ even though estimate is off, we should handle this in state transition as well. (I think)


Can I configure how long the suggestions appear?

I find that the amount of time the popup is shown is a bit too short for me to read and assimilate.
Is there a setting in the plugin to make the duration the popup is shown a bit longer?

Not yet, although it shouldn't be difficult to add one.

Okay, you should be able to change g:pf_popup_time, which is in milliseconds. (default 3000)

Thank you


fix(dist): generate doc & exit script when upload files failed

NOTE: DON'T DELETE THIS BRANCH (afer merge it)

rebase & merge this PR, so as other release-1.0.0 -> master


Version  <IP_ADDRESS>105160657 table field name auto completion not working

I am using dbeaver for almost 6 month and its a beautiful utility. Yesterday it updated to version <IP_ADDRESS>105160657 and after that it stop suggestion after table alias name. It keeps suggesting after schema name, but after table it shows no proposal when I expect field name. The database is a remote one. I attach here one screenshot for  clearing the situation.

Hello @ayan84
Thanks for the bug report!
I see that the problem is with schema name - this is special word.

As workaround for now you can quoted schema name:

Thanks, it actually solves the issue.

Hey @ayan84, hope it solved your issue. If it did, please mark it as closed.

Nope, sorry @hrushi8888
I gave workaround, not fixed the problem. Using special schema name without quotes in statement - it works for PostgreSQL. So autocomplete must work in this case either.

Ohh. Ok. I didnt get that.
I'm new here, just trying to start from somewhere.

@hrushi8888 we have many unanswered discussions https://github.com/dbeaver/dbeaver/discussions :grin:

Well, though adding a qoute around admin works, it has some problems also. For schema name with quotes stop giving suggestion on table name, like this,

If I use it without quotes, then table name suggestion appears but field suggestion stops,

I urge Dbeaver Dev team to fix these in next update.

this case already here https://github.com/dbeaver/dbeaver/issues/12159

Verified


Create Sprite for Gas Mask

Please see CONTRIBUTING.md first.
Happy Hacking! :smiley:

Hey, I can work on this one :smile:

Hi @oyvindjam! That would be great. :)

Hey! @doficia
There is already a sprite for gasmask under sprites/armors/.
Should I replace the exsisting one or should I create a new file for my attempt?
Since mine has quite a different style it might be useful to keep both.

Hi @oyvindjam! Gas Masks are going to be very iconic items, so more alternatives are fine! Keeping both would be great. Thank you!