flutter pub run flutter_flavorizr error

After I add the flavorizr in pubspec.yaml, I run flutter pub run flutter_flavorizr in terminal.
I got error
Executing task android:buildGradle
Unhandled exception:
The following resource contains existing flavor dimensions:
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 33
    ndkVersion flutter.ndkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = '1.8'
    }

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.xrspace.xrexpo.mobile.xspoclient"
        // You can update the following values to match your application needs.
        // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-build-configuration.
        minSdkVersion 24
        targetSdkVersion flutter.targetSdkVersion
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        multiDexEnabled true
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }

    flavorDimensions "app"
    productFlavors {
        dev {
            applicationIdSuffix ".dev"
        }
        prod {
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

. Please delete the whole section before running flutter_flavorizr again.
#.0      AndroidBuildGradleProcessor.execute (package:flutter_flavorizr/processors/android/android_build_gradle_processor.dart:67:7)
#.1      AbstractFileStringProcessor.execute (package:flutter_flavorizr/processors/commons/abstract_file_string_processor.dart:41:31)
#.2      Processor.execute (package:flutter_flavorizr/processors/processor.dart:116:24)
pub finished with exit code 255
Is someone has the same error?
How do I fix this?
Thanks.

Delete the section below, reopen terminal and run flutter pub run flutter_flavorizr again.
    flavorDimensions "app"
    productFlavors {
        dev {
            applicationIdSuffix ".dev"
        }
        prod {
        }
    }

Thanks for replying.
After I delete the section.
I got another error
Executing task flutter:targets
Running FlutterTargetFileProcessor
Running Copying file from .tmp/flutter/main_target.dart to lib/main_dev.dart
Running FileProcessor: creating file lib/main_dev.dart with nested ReplaceStringProcessor: replacing [[FLAVOR_NAME]] with dev
Running FlutterTargetFileProcessor
Running Copying file from .tmp/flutter/main_target.dart to lib/main_prod.dart
Running FileProcessor: creating file lib/main_prod.dart with nested ReplaceStringProcessor: replacing [[FLAVOR_NAME]] with prod

Executing task ios:xcconfig
Running IOSXCConfigFileProcessor
Running IOSXCConfigModeFileProcessor
Running FileProcessor: writing file ios/Flutter/devDebug.xcconfig with nested IOSXCConfigProcessor
Running ShellProcessor: Running script 'ruby' with arguments .tmp/scripts/darwin/add_file.rb, ios/Runner.xcodeproj, Flutter/devDebug.xcconfig, Flutter
Unhandled exception:
ProcessException: 系統找不到指定的檔案。

  Command: ruby .tmp/scripts/darwin/add_file.rb ios/Runner.xcodeproj Flutter/devDebug.xcconfig Flutter
#0      _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:487:7)
#1      _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:632:18)
#2      Process.runSync (dart:io-patch/process_patch.dart:68:12)
#3      ShellProcessor.execute (package:flutter_flavorizr/src/processors/commons/shell_processor.dart:45:36)
#4      QueueProcessor.execute (package:flutter_flavorizr/src/processors/commons/queue_processor.dart:44:17)
#5      QueueProcessor.execute (package:flutter_flavorizr/src/processors/commons/queue_processor.dart:44:17)
#6      QueueProcessor.execute (package:flutter_flavorizr/src/processors/commons/queue_processor.dart:44:17)
#7      Processor.execute (package:flutter_flavorizr/src/processors/processor.dart:139:24)

The android part seems success and ios is fail.
How do I fix the error?
Thanks.


ExternalForce/Impulse not working as expected

Since updating to 0.26, ExternalForce and ExternalImpulse do not seem to work correctly for me.
I've tried the same code with 0.25 and it works fine there.
As far as I can tell, it has to do with the unit conversion between game and physics world but I'm pretty new here so I don't know for certain.
Oddly enough, gravity still works as expected.
The setup I tested with uses 100 pixels per meter and applies a force to a 100x100 cube.
In 0.25, an impulse of 100 resulted in a velocity of 100 (this seems reasonable, as it should always be game world units being written to impulses/read from velocity from what I understand).
In 0.26, an impulse of 1000000 resulted in a Velocity of 100.
Relevant code snippets:
Adding the plugin and ppm:
.add_plugins(RapierPhysicsPlugin::<NoUserData>::pixels_per_meter(100.0))

Spawning the rigidbody:
commands
        .spawn(RigidBody::Dynamic)
        .insert(GravityScale(0.0))
        .insert(Collider::round_cuboid(50.0, 50.0, 0.1))
        .insert(Velocity::default())
        .insert(ExternalImpulse {
                  impulse: Vec2 { x: 0.0, y: 100.0 },
                  ..Default::default()
        })
        .insert(TransformBundle::from(Transform::from_xyz(0.0, 400.0, 0.0)));

Reading the velocity:
fn print_velocity(q: Query<(&Velocity)>) {
    for q in q.iter() {
        println!("V: {}", q.linvel);
    }
}

If this is a mistake on my end, I would appreciate any help on understanding what I was doing wrong :)

Hey! This was a bug in 0.25. The version 0.26 is being correct here. Since you cube is 100x100 with the default density of 1, it has a mass of 10_000. So in order to obtain a velocity of 100 from an impulse, you need 100 * mass = 100 * 10_000 = 1_000_000.
The reason why gravity remained the the same is because gravity is specified as an acceleration (instead of an actual force). So it is independent from mass.

Thanks a lot for the clarification!
I wrongly used the mass of the cuboid in physics world units, resulting in a value of 1(which is wrong, since it mixes the physics/game world units).
It all makes sense now that I read your explanation.
I'm not sure if this is the right place to ask, but it may be nice to add this to the CHANGELOG.md and update the docs with more realistic values relative to the getting started section to avoid confusing new users and those who migrate to 0.26.

update the docs with more realistic values relative to the getting started section to avoid confusing new users and those who migrate to 0.26.

The getting started uses Collider::ball(0.5), which is reasonable and should work fine with an impulse of 100 ; I imagine you changed the floor and went from there.
The fix should be visible in the changelog indeed though.


Optical interference of L515

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ L515 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (10)

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{matlab }

Segment
{others }

Issue Description
<Describe your issue / question / feature request / etc..>
When multiple l515 cameras shoot at the same time, optical interference will occur in the overlapping part.
I have learned the settings of l515 multi camera configuration in the official document：
Multi-Camera configurations with the Intel® RealSense™ LiDAR Camera L515
Authors: Ofir Mulla, Anders Grunnet-Jepsen
Revision 1.3, April 2021
But my application scenario requires multiple l515 cameras to shoot at the same time, so the methods in the document cannot solve my problem.
I would like to ask whether there are other ways to solve this problem.

Hi @liyuan1a  You could try reducing the value of the Laser Power option from its default value of '100' down to '50' to see whether it makes a positive difference to reducing optical interference.  Reducing the Laser Power value will result in a slight darkening of the infrared image and the loss of some detail from the depth image.

Hi @liyuan1a  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


feat: block network processor when processing current slot block

Motivation

We want to process current slot block asap
Right now we do that by limiting maxGossipTopicConcurrency to 512 which is not really necessary because the "hot" time is only ~600ms to process block while we applied for the whole slot

Description

When processing current slot block, block network processor. Most of the gossip messages at this time are attestations with unknown block root so should not be an issue
Remove the default value of maxGossipTopicConcurrency
Add "reason" to "lodestar_network_processor_can_not_accept_work_total" metric

part of #5413
Closes #5441
Testing

[x] Initial test on test mainnet passed
[x] Test for 1 more day with latest version

metrics look good compared to beta:

feat2: shorter block processs time

vs beta

Blocked messages per slot due to processing current block slot

Almost no dropped attestations (vs 30% - 40 in beta)

:tada: This PR is included in v1.9.0 :tada:


Quick links

Add quick links near the top (besides theme switch buttons)
These will simply look like icons and could be used for websites that are visited almost daily.
They should be configurable via the Options page (#4), with a few being added by default upon installation.

Closed by #22


api.err.LoginRequired

I get this error when adding unifi-wifi to configuration.yaml:
Logger: custom_components.unifi_wifi.coordinator
Source: helpers/update_coordinator.py:353
Integration: Unifi Wifi (documentation, issues)
First occurred: 10:52:00 (1 occurrences)
Last logged: 10:52:00

Authentication failed while fetching klubben319 data: {'meta': {'rc': 'error', 'msg': 'api.err.LoginRequired'}, 'data': []}

unifi-wifi installed via HACS. Running latest stable version of HAOS and Home Assistant.
configuration.yaml:
unifi_wifi:
  - name: klubben319
    host: wifi.klubben319.se
    port: 443
    username: REDACTED
    password: REDACTED

The unifi controller can be accessed at the adress stated in host. I have double and triple checked username and password.

When I entered your host:port in a browser the login screen was available. That login screen indicates your controller is not using UniFi OS. If this is the case, try including unifi_os: false in your YAML.
Is the controller supposed to be widely accessible on the internet?

When I entered your host:port in a browser the login screen was available. That login screen indicates your controller is not using UniFi OS. If this is the case, try including unifi_os: false in your YAML.
Is the controller supposed to be widely accessible on the internet?

Thanks, that was the problem.
Running the services doesn't change anything. Nothing to be found in homeassistant logs. Is there relevant logs somewhere else?
service: unifi_wifi.random_password
data:
  target:
    entity_id: image.klubben319_guest_qr_code
  method: xkcd

That's intriguing. Are you accessing the controller from outside your own network? I wonder if something in your firewall / setup may be blocking the HTTP PUT method used when attempting to change the wireless password. Maybe try using the IP address of the controller from within your network.

That's intriguing. Are you accessing the controller from outside your own network? I wonder if something in your firewall / setup may be blocking the HTTP PUT method used when attempting to change the wireless password. Maybe try using the IP address of the controller from within your network.

I´ve tried accessing it using the local ip. Login seems to work but I still can't change password nor enable/disable WLANs. Is it possible to set debug log or access log some kind of logile?

That's intriguing. Are you accessing the controller from outside your own network? I wonder if something in your firewall / setup may be blocking the HTTP PUT method used when attempting to change the wireless password. Maybe try using the IP address of the controller from within your network.

I´ve tried accessing it using the local ip. Login seems to work but I still can't change password nor enable/disable WLANs. Is it possible to set debug log or access log some kind of logile?

Add this to your configuration.yaml
logger:
  default: info
  logs:
    custom_components.unifi_wifi: debug
If you need more verbose log open the file /homeassistant/custom_components/unifi_wifi/coordinator.py and set the DEBUG varriable to True (line 65)

That's intriguing. Are you accessing the controller from outside your own network? I wonder if something in your firewall / setup may be blocking the HTTP PUT method used when attempting to change the wireless password. Maybe try using the IP address of the controller from within your network.

I´ve tried accessing it using the local ip. Login seems to work but I still can't change password nor enable/disable WLANs. Is it possible to set debug log or access log some kind of logile?

Add this to your configuration.yaml logger:  default: info  logs:  custom_components.unifi_wifi: debug
If you need more verbose log open the file /homeassistant/custom_components/unifi_wifi/coordinator.py and set the DEBUG varriable to True (line 65)
EDIT: After the changes you need to restart home assistant.

Thanks. Maybe one step closer to the solution:
2024-01-03 22:22:32.580 DEBUG (MainThread) [custom_components.unifi_wifi.services] Entity ID image.klubben319_guest_qr_code does not belong to platform unifi_wifi
image.klubben319_guest_qr_code is the entity created by the unifi integration.

2024-01-03 22:22:32.580 DEBUG (MainThread) [custom_components.unifi_wifi.services] Entity ID image.klubben319_guest_qr_code does not belong to platform unifi_wifi
image.klubben319_guest_qr_code is the entity created by the unifi integration.

That is unexpected. I noticed the entity ID being different that what the component generates, however when I made similar changes on my test system, the entity continued belonging to the unifi_wifi platform. I'm not sure how that would have happened. Could you try one of the following:

delete the entity and restart
remove the component from your install (comment out the yaml), restart, remove any lingering image entities, restart, uncomment the yaml, and then restart one last time

2024-01-03 22:22:32.580 DEBUG (MainThread) [custom_components.unifi_wifi.services] Entity ID image.klubben319_guest_qr_code does not belong to platform unifi_wifi
image.klubben319_guest_qr_code is the entity created by the unifi integration.

That is unexpected. I noticed the entity ID being different that what the component generates, however when I made similar changes on my test system, the entity continued belonging to the unifi_wifi platform. I'm not sure how that would have happened. Could you try one of the following:

delete the entity and restart
remove the component from your install (comment out the yaml), restart, remove any lingering image entities, restart, uncomment the yaml, and then restart one last time

I've solved this. I was using the image from the native Unifi integration, not this custome component. Changed this and now everything works. Thanks for support! Great component!

2024-01-03 22:22:32.580 DEBUG (MainThread) [custom_components.unifi_wifi.services] Entity ID image.klubben319_guest_qr_code does not belong to platform unifi_wifi
image.klubben319_guest_qr_code is the entity created by the unifi integration.

That is unexpected. I noticed the entity ID being different that what the component generates, however when I made similar changes on my test system, the entity continued belonging to the unifi_wifi platform. I'm not sure how that would have happened. Could you try one of the following:

delete the entity and restart
remove the component from your install (comment out the yaml), restart, remove any lingering image entities, restart, uncomment the yaml, and then restart one last time

I've solved this. I was using the image from the native Unifi integration, not this custome component. Changed this and now everything works. Thanks for support! Great component!

Great. :)
Can you check whether the service that turns a given network on and off works from your home assistant? It doesn't work for me.

2024-01-03 22:22:32.580 DEBUG (MainThread) [custom_components.unifi_wifi.services] Entity ID image.klubben319_guest_qr_code does not belong to platform unifi_wifi
image.klubben319_guest_qr_code is the entity created by the unifi integration.

That is unexpected. I noticed the entity ID being different that what the component generates, however when I made similar changes on my test system, the entity continued belonging to the unifi_wifi platform. I'm not sure how that would have happened. Could you try one of the following:

delete the entity and restart
remove the component from your install (comment out the yaml), restart, remove any lingering image entities, restart, uncomment the yaml, and then restart one last time

I've solved this. I was using the image from the native Unifi integration, not this custome component. Changed this and now everything works. Thanks for support! Great component!

Great. :)
Can you check whether the service that turns a given network on and off works from your home assistant? It doesn't work for me.

Checked and it doesn't work for me either. Change password works like a charm now.


Support l1 security fee

Support l1 security fee

Codecov Report

Merging #280 (45bca98) into develop (a9f542c) will increase coverage by 17.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #280       +/-   ##
============================================
+ Coverage    71.73%   89.52%   +17.79%
============================================
  Files           68       33       -35
  Lines         2257     1079     -1178
  Branches       335      150      -185
============================================
- Hits          1619      966      -653
+ Misses         638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.52% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ckages/data-transport-layer/src/utils/constants.ts

packages/message-relayer/hardhat.config.ts

.../batch-submitter/src/transaction-chain-contract.ts

...itter/src/batch-submitter/state-batch-submitter.ts

packages/core-utils/src/coders/index.ts

...ackages/batch-submitter/src/utils/tx-submission.ts

...h-submitter/src/batch-submitter/batch-submitter.ts

packages/message-relayer/src/relay-tx.ts

packages/core-utils/src/common/hex-strings.ts

packages/core-utils/src/index.ts

... and 25 more

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 a9f542c...45bca98. Read the comment docs.


Skip "/api/status/model"?

Hi,
I send request  by using image_client example to TRTIS.
The image_client example always sends "/api/status/model" and then sends "/api/infer/model" to TRTIS.
Is it a simple way of skipping "api/status/model" step?

@JungukCho I believe the ServerStatus is called each time to get the model config.
This isn't best practice or anything, but if you want to avoid the serverstatus calls and are sure that your model config won't be changing at all in between your Infer calls, you can just save the config and replace the ServerStatus code with one of these:

hard-code config as a map/dictionary (keys are model_name/version or something)
read config from a local file

@rmccorm4  Thank you for response.

As a simple workaround, I just use a loop to send sequential requests after performing only one "ServerStatus" request.


Issues after Collection Structure stuff

A user reported an issue where whenever they tried to duplicate an entry, they'd get Undefined offset: 0. I talked with the user and they shared their collection's yaml file.
title: Pages
revisions: false
route: '{parent_uri}/{slug}'
structure:
  root: true
  tree:
    -
      entry: home
    -
      entry: 3f9e0dbd-9b99-42ac-b1af-4bced9f8c513
    -
      entry: e6151e9b-170c-4415-8c81-1cb6f5e26bd0
    -
      entry: 569f0065-37f9-4692-8c0a-1cb2dd4a68cf
    -
      entry: 867c58a1-d4c5-4ee7-9189-46f1dfad12b0
    -
      entry: cd93e21c-106e-40f8-a25b-dc34b61c0fee

Steps to reproduce

With a structure, similar to the one above, attempt to duplicate an entry.
Be presented with the error.

Expected behaviour
I expected the entry to be duplicated.
Environment information
Statamic version: 3.0.32

Hey @damcclean
I've hit the same issue with this collection structure:
title: Pages
template: default
layout: layout
revisions: true
route: '{parent_uri}/{slug}'
sort_dir: asc
structure:
  root: true
  tree:
    -
      entry: home
    -
      entry: dde41cc8-b657-42c8-98d1-cc67bf1f5022
      children:
        -
          entry: 510cbbd9-e2ae-4359-b97a-376a302bbd6f
        -
          entry: fa89a1aa-1e79-42bc-9960-a50169939e00
    -
      entry: 117bfda5-c05e-4749-8788-f75f0a1fcfbf
    -
      entry: a36f09b3-a4b2-4dc1-8201-bfe37c187d98
    -
      entry: 7fa79475-41c0-46aa-893f-040037ba3ba0
    -
      entry: d7d3b285-2a7e-4edd-9ea2-8ed9d9213be8
    -
      entry: c75e7fa3-a57f-4be4-8e06-6369af576353
    -
      entry: 56d70357-3602-4592-a41d-1f27db1f9b6a
      children:
        -
          entry: 38914e71-2717-4475-ac74-83dd5b7905cd
        -
          entry: 8f681f24-e2a9-49de-84ee-29614c6bb52f
    -
      entry: cb1e412b-2aa9-40c8-969b-bd5408532307
    -
      entry: 42998498-f271-4210-8b0c-03d8f257cccc
    -
      entry: 264ed03a-b45f-4a2d-bf18-bdc398f091ae
    -
      entry: 4631cfb1-550c-4932-b7b2-6f7b1bb8910a
    -
      entry: 13f2533a-ee47-4817-845a-9e6692ee6634
    -
      entry: db87b28f-2d6a-43be-86d1-09fac3be36aa
    -
      entry: d3a8eb5c-e5a6-4171-b043-9fca5c1cb11d
    -
      entry: 52285f1c-f97f-47d9-9cb0-e0e935a339ef
    -
      entry: 5b71cbd3-6ea9-4307-925c-9cd69c9b4d3a

Hey @damcclean
Quick follow up. I've removed all pages from the collection leave only 2 entries. 'Home' and another page.
I can duplicate the homepage but the other page results in the offset error.
Pages.yaml:
title: Pages
template: default
layout: layout
revisions: true
route: '{parent_uri}/{slug}'
sort_dir: asc
structure:
  root: true
  tree:
    -
      entry: home
    -
      entry: 846d504a-517d-4974-9715-34d32233312b

Sleeping-tips.md content (results in error when duplocated)
---
title: 'Download Your Sleeping Tips PDF Now!'
id: 846d504a-517d-4974-9715-34d32233312b
---

Thanks for bringing this back up! I almost forgot entirely about this issue. I'll see to it today.

This issue should be fixed in v1.2.2.


Please establish lossless and secure compression as the primary idea

As an svg compressor, I think it is most important not to change the display effect of the svg itself, which means that the compressed result cannot change the shape, position, size, color, etc. (svgcleaner has a detailed description). As svgo is adopted by more and more non-browser terminals (Sketch, Adobe Illustrator, other back-end languages), this will become more and more difficult, because each side implements svg differently. So we urgently need to introduce Correctness test like svgcleaner to help svgo become the best svg compressor.
The following work is a good start:

[x]  The noSpaceAfterFlags option is disabled by default @yisibl
[x] Test regressions with W3C SVG 1.1 Test Suite @TrySound
[ ] Add sample documents and compatibility instructions for each option of svgo, Similar to:

cc @deepsweet

May I add that we should change the default options to only include those plugins known/supposed to be lossless. For example convertPathData probably should not be a default plugin unless the default options are safe. I've also seen that gradients are usually changed.

Or we should make it safe.

Another case here is cleanupIds, which is generally good, unless you use something like <use xlink:href="square.svg#square" x="20" fill="white" stroke="red"/> where removing the IDs inside square.svg isn't safe.

Closing this as we're now actively striving for this, but the issue isn't presented in a way that we can track progress and know when it's complete.
If you have concrete suggestions, you're encouraged to open another issue with what we can specifically do better. Meanwhile, I'm not at all dismissing the issue.
All future development is done with lossless compression in mind. We're investing a lot of time and effort in fixing bugs, improving testing, and having more complete documentation to clarify potential quirks. I'm also working on new sections to include in the documentation to clarify what we optimize, and in what cases we may deem something more important than reducing bytes.
In recent released, I believe we've already made good progress, and will continue to do so. 👍🏽


kubeflow pipeline execution causes Invalid input error: Job has no experiment

Problem
{"error":"Invalid input error: Job has no experiment.","code":3,"message":"Invalid input error: Job has no experiment.","details":[{"@type":"type.googleapis.com/api.Error","error_message":"Job has no experiment.","error_details":"Invalid input error: Job has no experiment."}]}

Reproduction
Open the kubeflow pipeline default sample and run.

Not kfctl issue.


I'm waiting for Get the Green Light

I translate your swift source to objc.
https://github.com/mifanj/JElasticPullToRefresh
If ok I want to send it to bbs
you can contact me<EMAIL_ADDRESS>I'm waiting for Get the Green Light with you.
I'll not send it untill you answer me.

sorry my English is very poor...


Fix issue-5684 Renaming Box on Grid View is Broken

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes https://github.com/files-community/Files/issues/5684

Details of Changes
Add details of changes here.

Fix: Renaming Box on Grid View is Broken

Validation
How did you test these changes?

[x] Built and ran the app

Screenshots (optional)
Add screenshots here.

Renaming popup, and thumbnail will not overflow the selection ractangle. Thumbnail will also stretch when stretching items.

Before
After

https://user-images.githubusercontent.com/45145954/128486374-b3a55315-60fd-4df3-8f95-d8ae14cf8585.mp4

lgtm


perf(freespace_planning_algorithms): update the astar search algorithm

Description
The current A start implementation does not account for exploring opened nodes and only explores those with node status: None. Open nodes need to be explored based on a lower move_cost (gc+hc) than the gc cost of next node. A cost for turning move_cost_is_turn is also introduced to penalize turning over going straight in addition to cost for reversing.
A Priority Queue is used to store open nodes in the algorithm, but std::priority_queue does not give you the ability to update node parameters and it automatically resorts the queue. Queue resorting only happens on queue.push(node), when a new node is pushed into the queue. So as a work around instead of updating nodes (when algo wants to revisit open nodes), a new reference to the same node is instead pushed into the queue. This new reference pushed will always get popped out of the queue first due to its lesser cost, here its NodeStatus will be set to Closed. When the algorithm pops the old duplicate node left in the queue, a flag check whether its NodeStatus is Closed or not. If closed the node is discarded without processing.
Tests performed
The freespace_planning_algorithms/test/src/test_freespace_planning_algorithms.cpp tests were run to gauge the new astar trajectories generated. The new trajectories are found to be shorter, uses less fwd, back segments and were more smoother than previous ones. The algorithm now explores all open nodes, this leads to increased computation time but optimal paths are generated.
It was further found that by using curve weights, the amount of explored nodes drastically increases. But a smoother and much straighter optimal path is generated. To allow user to switch between using curve weights or not, also to switch between new complete astar and the old astar that only uses unexplored nodes, the following search configurations are introduced in freespace_planner.param.yaml:
use_curve_weight: true
use_complete_astar: true

The user can modify these parameters to balance path optimality and run time.
Comparison images between different configs are shown below for the tests:

Effects on system behavior
The astart search takes longer but finds the optimal path.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@takayuki5168 @mkquda hello,
@NorahXiong from AutoCore will take over this task, do you have anything to share on this PR?

@xmfcx @takayuki5168
This PR is already obsolete and irrelevant since we already did entire refactoring / improvements for freespace planning algorithm in multiple PRs. I will share the relevant PRs below:

https://github.com/autowarefoundation/autoware.universe/pull/8068
https://github.com/autowarefoundation/autoware.universe/pull/8089
https://github.com/autowarefoundation/autoware.universe/pull/8091
https://github.com/autowarefoundation/autoware.universe/pull/8091
https://github.com/autowarefoundation/autoware.universe/pull/8092

@mkquda thanks for letting us know, I will close this PR then ✅


eberg_cooly_c35hd doesn't get detected as this device, instead is detected as becool_heatpump and 2 others

As in title, I've got the Eberg Cooly C35HD air conditioner, and when configuring, I can select type from 3 devices, but in this list the eberg_cooly_c35hd is missing. (The file is present in the custom_components\tuya_local\devices folder )
To Reproduce
Try to add Eberg Cooly C35HD air conditioner - the correct device type is not present to choose
Expected behavior
When adding  Eberg Cooly C35HD the correct device type is present to choose
I did a temporal workaround by copping settings from custom_components\tuya_local\devices\eberg_cooly_c35hd.yaml to custom_components\tuya_local\devices\becool_heatpump.yaml and using becool_heatpump as a type for this device. But any update to tuya local will override my local changes.

There is insufficient information here to act on.  It is quite common for manufacturers to make different versions of the same model which are not compatible with each other, and it is quite common for the same device to be sold under different brands, so entirely possible that your device is not the same as the eberg_cooly_c35hd that was already added, but is the same as one of the other devices.

After reviewing the two configs, the only substantial difference is in the mapping of the hvac_modes.
BeCool has the set_temp_f dp marked as optional, so I assume that would be the reason for the non-match of Eberg.  I have made that change for the Eberg config.

I can confirm that this fixed the issue.


Refactor parse_data

Introduce DataParser class as handler for data conversion
Break up and remove old implementation of parse_data

Nice work, this refactor looks great!


Fix a bug that deliver fails to find version

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
deliver fails to select version for app submission when:

You set 'latest' to build_number and set a specific version to app_version parameters
There is newer version available on App Store Connect

Description
This was happening because wait_for_build in submit_for_review always looks for the latest version.
Testing Steps
n/a

@googlebot I fixed it.


got an error message with finding chromosomes in ldpred

Hi, recently I'm working on ldpred but I got an error message with coordinating data.
The error message is like this..
" Note: For maximal accuracy all SNPs with LDpred weights should be included in the validation data set.
If they are a subset of the validation data set, then we suggest recalculate LDpred for the overlapping SNPs.
You can coordinate across the three data sets by either using the same LD reference and the validation data, or using
the --vbim argument, and supply the validation data set PLINK formatted bim file.
Preparing to parse summary statistics
Parsing SNP list
Parsing bim file: /data1/ahminji/prs/ldpred/1kg.phase3.auto.snp.qc.eur.bim
11929993
Parsing the file: /data1/ahminji/prs/ldpred/ldpredsummarystat1
chr     pos     ref     alt     reffrq  rs      pval    effalt
SS file loaded, now sorting and storing in HDF5 file.
0 SNPs parsed from summary statistics file.
Unable to find phenotype values.
Genotype dictionary filled
Working on chromsome: chrom_1
"Unable to open object (object 'chrom_1' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_2
"Unable to open object (object 'chrom_2' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_3
"Unable to open object (object 'chrom_3' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_4
"Unable to open object (object 'chrom_4' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_5
"Unable to open object (object 'chrom_5' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_6
"Unable to open object (object 'chrom_6' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_7
"Unable to open object (object 'chrom_7' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_8
"Unable to open object (object 'chrom_8' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_9
"Unable to open object (object 'chrom_9' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_10
"Unable to open object (object 'chrom_10' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_11
"Unable to open object (object 'chrom_11' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_12
"Unable to open object (object 'chrom_12' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_13
"Unable to open object (object 'chrom_13' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_14
"Unable to open object (object 'chrom_14' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_15
"Unable to open object (object 'chrom_15' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_16
"Unable to open object (object 'chrom_16' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_17
"Unable to open object (object 'chrom_17' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_18
"Unable to open object (object 'chrom_18' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_19
"Unable to open object (object 'chrom_19' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_20
"Unable to open object (object 'chrom_20' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_21
"Unable to open object (object 'chrom_21' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
Working on chromsome: chrom_22
"Unable to open object (object 'chrom_22' doesn't exist)"
Did not find chromsome in SS dataset.
Continuing.
There were 0 SNPs in common
In all, 0 SNPs were excluded due to nucleotide issues.
Done coordinating genotypes and summary statistics datasets."
I guess this is system-related problem, but not sure about why this is happened.
Could you look over my error message and give any advice?
Thanks in advance.

I apologize the slow reply on this. Try the latest version of LDpred, and then I think it should work.

I think the issue that you’re observing is because it can’t match the SNPs across datasets properly.  LDpred matches the SNPs using the rsIDs, hence please ensure they match between datasets before using LDpred.


Extra defensive programming for pub modification time assert

Let's see if this helps us track down this issue...

I'll write a test and update this PR once https://github.com/flutter/flutter/pull/42369 lands.

I made the change suggested by @jmagman and also added a test for that branch, which I'd missed before.
Thanks for the reviews, will land on green.

The last several failures have been this issue on the devicelab host. Landing to get the tree back to green

Looks like this got out of sync somehow


make SolutionInspector work without config files

I just tested your SolutionInspector against a mid-sized MSVC 2013 Solution with mostly C++ and some Python, Qt and custom-batch projects.
It failed to run due to several NULL access exceptions. I'm not a C-Sharpie, but figured out how to work around it.
I managed to make SolutionInspector run without requiring me to write XML config files for all my (45) projects.
If you think these are good changes, then please accept this PR.
Thanks,
Peter

Thank you for the contribution!


Vagrant nfs mounts break installation of dlite machine

TL;DR: Dlite won't install If I'm using vagrant with nfs mount simultaneously with dlite.
Steps to reproduce

Start vagrant box with nfs mount
Install and start dlite machine
Notice that dlite isn't mounting /var/run/docker.sock
Notice that It doesn't return ip address with: $ dlite ip

Conflicting settings in /etc/exports
For example vagrant creates these in my /etc/exports:
# VAGRANT-BEGIN:<PHONE_NUMBER>9-bc2f-4df1-aee0-3f4addf71ed9
"/Users/onnimonni/dev-root/wpbox/nginx/sites-available" <IP_ADDRESS> -alldirs -mapall=501:20
"/Users/onnimonni/dev-root/wpbox/www" <IP_ADDRESS> -alldirs -mapall=501:20
# VAGRANT-END:<PHONE_NUMBER>9-bc2f-4df1-aee0-3f4addf71ed9

If I shutdown vagrant and remove those lines from /etc/exports dlite will start correctly and then dlite adds these lines:
# BEGIN: dlite
/Users -network <IP_ADDRESS> -mask <IP_ADDRESS> -alldirs -maproot=root:wheel
# END: dlite

If I install dlite first and then start vagrant both will work correctly and I will have settings like this:
$ cat /etc/exports
# BEGIN: dlite
/Users -network <IP_ADDRESS> -mask <IP_ADDRESS> -alldirs -maproot=root:wheel
# END: dlite
# VAGRANT-BEGIN:<PHONE_NUMBER>9-bc2f-4df1-aee0-3f4addf71ed9
"/Users/onnimonni/dev-root/wpbox/nginx/sites-available" <IP_ADDRESS> -alldirs -mapall=501:20
"/Users/onnimonni/dev-root/wpbox/www" <IP_ADDRESS> -alldirs -mapall=501:20
# VAGRANT-END:<PHONE_NUMBER>9-bc2f-4df1-aee0-3f4addf71ed9

Is it possible to use other nfs mounts when using dlite? Anything I could look for?
This is problematic because many of our employees are using vagrant at the moment and we want to shift into docker and dlite but still we would need to use older dev tools simultaneously for a while.

yup, known issue, see https://github.com/nlf/dlite#troubleshooting
it's on my radar to see if i can determine if there are conflicts but i'm pretty limited in what action i can take if there are. printing a warning is better than nothing though.
good tip that starting dlite first seems to work, i'll see if adding the export for dlite to the top of the file works more reliably

Actually just to note it here:
I noticed that even when starting dlite first doesn't work consistently. So as a workaround we just moved our vagrant development outside of /Users/ path to /opt/vagrant so now nfs doesn't have colliding paths for us anymore and it works correctly.


feature: added generate_pdf_from_html string alternative

This PR derived from a need that came about from a project I am currently building, through which I desired to generate a pdf from a html string, without accessing the disk. I only took the generate_pdf function and exchanged the html_path for the string that can come from an AWS S3 download or something in the liking.
I would like to get your input, @Massimiliano-solutiontech, whether you feel the idea makes sense to this package :)

@pecampelo thanks for the PR. I'll review it on the weekend
cheers

Putting it in draft since I would like to add some tests to it

Putting it as draft since I would like to add more tests to it.

I have made a fully functional application using it, it has proven to be a good alternative opposite to reading from disk. Making it ready for review, would appreciate your input

Ok then I hope to find some time today to review it.
I keep you posted

I added the comments, feel free to reach me out (even via email<EMAIL_ADDRESS>if you need to discuss more the changes


Update docs for dev

Ⅰ. Describe what this PR does

Add description on how to run unit tests
Fix CRDDirectoryPaths in controller tests

Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
@cheyang  @biubiu-biub

Codecov Report

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

@@           Coverage Diff           @@
##           master     #131   +/-   ##
=======================================
  Coverage   20.66%   20.66%
=======================================
  Files          16       16
  Lines         329      329
=======================================
  Hits           68       68
  Misses        241      241
  Partials       20       20

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 a414d79...371d064. Read the comment docs.


Bump NodeJS to version 20

🗣 Description

This bumps the NodeJS version to 20.
💭 Motivation and context

Version 20 of NodeJS has been approved by the FoundryVTT developers.
There is evidence that v20 may also mitigate some of the glibc issues people are having with embedded database binaries.
See:

#697

🧪 Testing

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] All new and existing tests pass.

It's been over a year since npm started hanging on NodeJS.  It does not look a resolution is forthcoming.  FoundryVTT v13 will require at least Node 20.  The best way forward seems to convert the image base from Alpine to Debian.  I will start this work in a new branch, and PR.
See:

https://github.com/felddy/npm-hang-test/issues/2
https://foundryvtt.com/releases/13.332


Hotfixes/jittering scroll treebeard

Purpose
Fixes the issue #1661 . Scrolling by dragging the scrollbar with mouse should not cause jitters
Changes
Replaces the commit sha reference for treebeard in bower.json so the treebeard changes can be installed.
Side effects
Does not effect scrolling otherwise. Tested in Chrome, Safari, Firefox and IE 11.  Safari has still a tiny jitter but that should not hold up the fix.

Closing this, will redo with another sha code

This one should be good to go but it will be overwritten with the next PR I make, the newest one is the correct one.


Modify some of the Japanese translation.

r? @sinkuu, @KeenS or @chikoski.

I think review has done by the ba0785d commit

Great! Thanks all! ❤


Windows images absent from the shared tags 3.7 and 3.8

The shared tags 3.9 and 3.10 include Linux and Windows images for amd64 and aarch64, but 3.7 and 3.8 do not include the Windows images at all.  Could this be made consistent?

Thanks for the explanation, @yosifkit


docs(Getting started): Suggest code snippets that work without changes

The "Quick start" page of the docs is confusing when starting a project from scratch. I was trying to experiment quickly with Yoga so I started a new project, installed graphql-yoga and graphql and created schema.js and index.js with the code from the snippets on the page.
Running this did not work as expected
$ node index.js

(node:5106) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
/..../yoga-graphql/index.js:1
import { createServer } from 'node:http'
^^^^^^

SyntaxError: Cannot use import statement outside a module

Sure, I can add type: "module" to my package.json, but then I get an error about it not finding schema:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/.../yoga-graphql/schema' imported from /..../yoga-graphql/index.js
Did you mean to import "./schema.js"?

Patching the schema import line to import { schema } from './schema.js' works, and the server is able to start. 🎉

A Carefully crafted "Getting started" page makes a good first impression. While these issues can be common, I think the page could be updated to mention these tricks and make the first contact more pleasant.
I see two ways to fix this:

switch the code snippets to the (old and terrible) require() syntax.
Mention that code snippets use the module standard, suggest to set "type":"module" in the package.json file, and fix the schema.js path.

I'll happily submit a PR going whichever way you prefer, thanks!

Hi @TPXP, Thank you for reaching out about this!
We are in the course of improving our docs, and any feedback or help is very appreciated!
If you're willing to make a PR for this, I'm more in favor of making using the ESM standard. It's supposed to be the way to go for new project, so let's push this instead of pushing back to CJS syntax.
I think we are too TS minded in our docs, we should be more careful when we write JS snippets, because imports are slightly different than we are used to.


Domain name and refresh external IP

Background
I have a LND node running 24*7. It has a no-ip hostname associated with his external ip, in the configuration file (lnd.conf) I have this:
externalip=jocheminlnd1.ddns.net

If I launch a getinfo it returns the node public IP.

This public IP changes from time to time, lnd node continues working but active channels and peers drop and I have to stop client and launch again.
Is there a way to refer to the domain name and not the IP? or refresh the ip automatically on change?
Your environment

LND 0.4.1
Linux srv1 4.4.0-119-generic #143-Ubuntu
Bitcoin Core 0.16

Steps to reproduce
Start your node with domain name in config file (lnd.conf) and change external IP.
Expected behaviour
Refer to the node by his domain name to avoid fails on public ip changing.
Actual behaviour
This public IP changes from time to time, lnd node continues working but active channels and peers drop and I have to stop client and launch again.

In the weekend, I experimented with creating an "lncli addexternalip" command, so that you could wrap this in script. I have it almost working, the only problem is that I don't get a new node announcement sent out - hopefully it's just a small misunderstanding from my side. Once that is done, I will continue with making an "lncli deleteexternalip" command. This would help some, right?
Other than that - would it be possible to add a lncli gracefulrestart - where wallet is kept open, and everything else is reinitialized? If there is no fundamental things stopping this, I could put it on my working list for future contributions.

This public IP changes from time to time, lnd node continues working but active channels and peers drop and I have to stop client and launch again.

We'll automatically establish outbound connections to any peers that we have channels open with.

In the weekend, I experimented with creating an "lncli addexternalip" command, so that you could wrap this in script.

I don't think this is the best solution, as you'll need to have a secondary script just to monitor IP address changes and then tell lnd to use the latest one. Instead, if you're attempting to run a routing node it's desired that you have a stable IP address, otherwise peers will have trouble connecting out to you in the case that they don't even store any new NodeAnnouncements.

Well. There are different versions of stable. I am running on a dynamic IP that only rarely changes. But in the offshoot that it should change, I'm for example running a script to update DNS.
I think it's a valid use case. But I can code it myself and test it :)

Well - since you can have a  domain name in the config file (resolved at startup time) - couldn't this also be solved if we created an "lncli reload" command?
lncli reload would do everything an lncli stop does, but stopping short of closing the wallet - and then opening/initializing everything again, except not having to reopen the wallet?

I think it would be better to refer to domain name if it's in the config file, but reload option is interesting.

I can confirm that changing external ip addresses are the single most asked questdion in combination with my RaspiBolt guide. @Roasbeef, I don't think the requirement to have a fixed ip address to be able to route payments should just be assumed. At least in Europe fixed ip addresses are only available with business ISP contracts that are quite expensive. I think this goes directly against the goal to have a decentralized mesh network by raising the barriers to entry for non-business participants. And at least in my case, I do not have a fixed ip, but the address changes every few weeks, if not months.
I think the lncli reload command would be a good solution as opposed to manually updating ip external addresses. Monitoring ip address changes with a script is trivial and if a routing node is connected with a dyndns fqdn, a graceful restart would solve these issues.
On the other hand, the need to use a dyndns fqdn may not suit everybody, and as the whole Lightning specification works on bare ip addresses, this abstraction layer may not be welcomed.
Thanks @vegardengen for working on this after our Slack discussion. I would appreciate a broader discourse how to best enable this valid requirement.

@Stadicus I have most of the addexternalip stuff coded, only thing is that it's not currently gossiped before something else triggers the gossiping. I think I might code it as addexternalip and deleteexternalip, and not updateexternalip, though. Only thing, I guess, is that you don't want to trigger gossiping twice if you are doing an add/delete combination.

I also belief there is proof in working code. I am fully aware that @Roasbeef doesn't think it makes sense. My generating working code is an argument, not a protest. And being an LND newbie, it's useful training anyhow, whether or not it is merged in the end.

@vegardengen Is it the intent to allow multiple externalip addresses? This is what it seems to imply by add... and delete.... ip addresses and this is why I phrased it as update.... But any functionality to make LND usable with dynamic ips is fine with me.
Let me know if I can help in any way, eg. testing or documenting. I'm not much of a programmer, unfortunately... :-)

Multiple externalip is already supported - so I think add/delete is a more general solution than update. deleteexternalip is also a way of stopping your node from getting new connections, should you want that for a period.

Ah, did't consider that. It makes more sense now. 👍

At least in Europe fixed ip addresses are only available with business ISP contracts that are quite expensive.
And at least in my case, I do not have a fixed ip, but the address changes every few weeks, if not months.

Time to IPv6? Heh, only partially kidding...
I certainly see the use case, so seems the option is: restarting every few weeks, or adding a command to allow scripts to update the current set of advertised IPs for a node.

An external script to do that would definitely help, as a restart of lnd always forces unlocking the wallet again.
Any pointers how that could work? I coud work on the details given the knowledge where to start and how a good design could work on an abstract level.

I think a good aproach would be 'announce' option.  I assume a domain name in the config file.
Launching lncli announce will refresh only the ip in the "uris". The user could make a script to track his public ip and if changes send the announce option automatically.

What about creating a command:
updatenodeinfo
Here you can:
--addexternalip (to add)
--deleteexternalip (delete)
--setexternalip (to set the (list of) ip-adresses, disregarding the ones there before
--setalias
Would it also make sense to create an --announce true/false options, where you specify whether or not you want to gossip it now or wait till next change of node announcement?
@jochemin approach could also work, not sure what I prefer.

@Roasbeef I value your opinion here. My choice is between:

Adding separate addexternalip, deleteexternalip (and possibly later setalias)
Adding an updatenodeannouncement that will change all of these, with parameters :)

It's also a question whether or not we should gossip immediately or just wait until next time nodeannouncement is going to change anyhow. The first will actually make it easier to spam the network with unwanted info.

Related PR: https://github.com/lightningnetwork/lnd/pull/518

So we're reviving #518 now. The new version of the PR will have a background goroutine that'll detect IP address changes and send out new announcements to update the network for reachability.
I think this addresses all the desired features detailed in this issue? The process would be automatic, and just all the setup guides would direct users to set the appropriate flag. This should work for the general case, but not for anything beyond a double NAT.

Fixed by #1109.

I am continuing to have issues with a dynamic IP over UPnP. The broadcast URI does not update unless I do a full restart of my node.

One problem is that when router is restarted, then the UPnP ports are lost and not reestablished by lnd.
Second problem is that it looks like changed IP isn't reannounced after it changes. All block explorers show the old IP address unless lnd is restarted.


Add doc for mapping of OMERO.web light admin UI to back end permissions

This doc maps the checkboxes in the OMERO.web admin UI for the creation of the light admins to the back-end permissions, as defined by @mtbc .
To test:

check logic, spelling, etc.
check crosslinking with other docs

Also see OmeroWebGateway.setConfigRoles

@mtbc Yes, maybe @will-moore would be the ideal reviewer here. (added to Standup for tomorrow)

commit cherry-picked into https://github.com/openmicroscopy/ome-documentation/pull/1726 in order to get rid of conflicts. Closing.


domain_template_record schema definition

Hello,
We are using DomainKeys to sign emails and hold the public key in dns.
Please modify the column data in domain_template_record to varchar(65535) because large public key text does not fit.
I recommend 65535 inherited from PowerDNS table structure.
Thanks

Thanks for your suggestion. I changed data type to TEXT to support longer record data. See commit 8b7653ad4a95f20487886916328bb0745e07e3da.
Tested on MySQL and Postgres latest stable version.


BSON deserialization

[x ] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[ x] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I have a question!

[ x] I searched the Wiki, open and closed issues for an answer. I tried my best to find the answer by myself without success. I believe that the discussion we will have in this issue, and the solutions we might find, will help me, and likely other community members who have a similar problem.

Here is my question:
Hi everybody,
I have been looking for a way to use BSON with RosSharp to reduce latency. I have read #136 which is marked as a new feature but I don't think it is. When using BSon_only_mode in RosBridge, it says 'Exception in deserialization of BSON. So I have tried to deserialize the recieved Messages in RosSocket:
MemoryStream ms = new MemoryStream(buffer);
using (BsonReader reader = new BsonReader(ms)){
    JsonSerializer serializer = new JsonSerializer();
    T e = serializer.Deserialize<T>(reader);
    return e;
}
I followed this template
How can I fix the deserialization?
Thank you in advance.

Solved, I had to modify the serialization as well although I did only recieve messages and I didnt send any.

Issue has been addressed in commit https://github.com/siemens/ros-sharp/commit/2bcb2666a5af3222da840fd4e87b0a99700fb068 .


How to check product was not found using stripe::Product::retrieve

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
let stripe_product = match stripe::Product::retrieve(
    &state.stripe,
    &stripe::ProductId::from_str(&product.id)?,
    &[],
)
.await
{
    Ok(stripe_product) => Some(stripe_product),
    Err(error) => {
         // what error type should be used here to know if it was found or not
    }
};

I have searched through the docs, but I don't know what the error is named.
Describe alternatives you've considered
No response
Additional context
No response

Considering that this is the response from Stripe on this case:
{
    "error": {
        "code": "resource_missing",
        "doc_url": "https://stripe.com/docs/error-codes/resource-missing",
        "message": "No such product: 'prod_***'",
        "param": "id",
        "request_log_url": "https://dashboard.stripe.com/test/logs/req_***",
        "type": "invalid_request_error"
    }
}

Something like this probably works for you:
match Product::retrieve(
    &state.stripe,
    &stripe::ProductId::from_str(&product.id)?,
    &[],
) {
    Ok(_) => todo!("Handle found"),
    Err(StripeError::Stripe(err)) if err.code == Some(ErrorCode::ResourceMissing) => {
        todo!("Handle missing product");
    }
    Err(other_error) => todo!("Handle other errors"),
}


Upgrade jQuery UI and correct some color contrast warnings (CO-2469)

This PR updates jQuery UI's package.json to reference a more up-to-date version of Grunt

This PR has been rebased against the latest develop.


[core] Code restructure failed

Describe error

Class: c.m.b.a.f.a.D
Method: public final java.lang.String a(byte[] r6, java.io.File r7)
provide full java stacktrace:

  /* JADX WARNING: Code restructure failed: missing block: B:10:0x001c, code lost:
       r3 = r1;
       r1 = null;
    */
   /* JADX WARNING: Code restructure failed: missing block: B:14:0x0021, code lost:
       r3 = th;
    */
   /* JADX WARNING: Code restructure failed: missing block: B:9:0x001b, code lost:
       r1 = move-exception;
    */
   /* JADX WARNING: Removed duplicated region for block: B:22:0x002d  */
   /* Code decompiled incorrectly, please refer to instructions dump. */

APK:

https://play.google.com/store/apps/details?id=com.yandex.mobile.drive&hl=ru

A duplicate of https://github.com/skylot/jadx/issues/411


Revert "Run simulated hosts with unique UUID"

Reverts fleetdm/osquery-in-a-box#12
We found that this strategy caused errors on Windows (https://github.com/fleetdm/fleet/issues/3710), and per discussion in (https://github.com/fleetdm/fleet/issues/3201#issuecomment-1014952765) it seems no longer necessary.

Just reinstated those, thank you!

Tested with fleetctl preview --tag main --preview-config revert-12-containers-with-unique-uuid on macOS and Windows and result filtering seems to work as expected. The simulated hosts also start without error on Windows.


Synchronize the cross-analysis filter to other pages

Hi team,
I moved this from here: https://github.com/MicrosoftDocs/powerbi-docs.zh-tw/issues/15
the comments below were machine-translated
@myyt0523 commented 19 hours ago — with docs.microsoft.com
Is this synchronization function of cross analysis filter available on the dashboard?
I use this function in power bi desktop to synchronize, but after the power BI service is pinned to the dashboard, this synchronization function is invalid

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

ID: 2f177d47-9600-eab6-a282-09d40d5c2dff
Version Independent ID: 792909b9-e2fa-8a31-1da9-2223307e799d
Content: Slicers in Power BI - Power BI
Content Source: powerbi-docs/visuals/power-bi-visualization-slicers.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks @myyt0523 for the question. I'm assigning this issue to the author to take a look. They'll follow up soon.

Hi, @myyt0523 -- thanks for asking! If I understand your question correctly, no filters don't apply to dashboards. Please clarify, if that was not your question.

Hi , @maggiesMSFT ,
Is this synchronization function of cross analysis filter available on different dashboards?
Or it only works on report?
Thanks for your reply~

Hi @CeciAc , @myyt0523 ,
I see that this Git issue is a bit old, so I'm going to close it. From what I can tell, maggieMSFT answered your question about filters -- that they cannot be used on dashboards, only on reports.  If you still have questions, please let us know.
All the best,
the DOCS team


graceful shutdown period is being ignored sporadically

Describe the bug
When stopping hornet via systemd the graceful shutdown period, mentioned in the journal, is being ignored sporadically.
Jan 05 23:38:40 hornet-4 hornet[5948]: 2020/01/05 23:38:40 [ WARNING ] Graceful Shutdown: Received shutdown request - waiting (max 120 seconds) to finish processing ...

In some cases it takes more than 10 minutes to stop processing and initiating the shutdown protocol including the persisting tasks.
To Reproduce
Steps to reproduce the behavior:

Start hornet
Wait until instance is synced
Shutdown hornet via systemd

Expected behavior
Maybe I'm misinterpreting the journal entry but I expect the shutdown to start within 120 seconds at the latest after SIGTERM is sent.
Environment information:

OS: Ubuntu 18.04 (Kernel 5.0.0-37-generic via HWE)
RAM: 4 GB (+ 4 GB SWAP)
Cores: 2 Cores
Type: Hetzner CX21 (mainnetdb stored on attached volume)
HORNET version 0.2.12

Additional context
Maybe this is related to #115 but the log attached there is too short to verify this and as a brief issue search reveals there were already totally different root causes for shutdown delays.
Here is the journal excerpt, config.json and systemd service file
journalctl -e -u hornet.service
Jan 05 22:59:19 hornet-2 hornet[18362]: reqQ: 00000, reqQMs: 0, processor: 00000, LSMI/LMI: 1300548/1300548, addrsMarked: 6394, bndlsValidated: 102701, txReqs(Tx/Rx): 4725/708338, newTxs: 109141, TPS: 68 (in) / 12 (new) / 34 (out)
Jan 05 22:59:20 hornet-2 hornet[18362]: reqQ: 00000, reqQMs: 0, processor: 00000, LSMI/LMI: 1300548/1300548, addrsMarked: 6396, bndlsValidated: 102713, txReqs(Tx/Rx): 4725/708338, newTxs: 109153, TPS: 64 (in) / 12 (new) / 33 (out)
Jan 05 22:59:21 hornet-2 hornet[18362]: reqQ: 00000, reqQMs: 0, processor: 00000, LSMI/LMI: 1300548/1300548, addrsMarked: 6396, bndlsValidated: 102723, txReqs(Tx/Rx): 4725/708338, newTxs: 109163, TPS: 40 (in) / 10 (new) / 32 (out)
Jan 05 22:59:22 hornet-2 systemd[1]: Stopping Hornet Fullnode...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ WARNING ] Graceful Shutdown: Received shutdown request - waiting (max 120 seconds) to finish processing ...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] WebAPI: Stopping WebAPI server ...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] WebAPI: Stopping WebAPI server ... done
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[TipSelMetricUpdater] ...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[TipSelMetricUpdater] ... done
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] WebAPI: Stopping WebAPI server ... done
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[WSSend] ...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[WSSend] ... done
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[TxUpdater] ...
Jan 05 22:59:22 hornet-2 hornet[18362]: 2020/01/05 22:59:22 [ INFO ] SPA: Stopping SPA[TxUpdater] ... done
Jan 05 22:59:33 hornet-2 hornet[18362]: 2020/01/05 22:59:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:60978...
Jan 05 22:59:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 22:59:33 hornet-2 hornet[18362]: 2020/01/05 22:59:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:60978: use of closed network connection
Jan 05 22:59:33 hornet-2 hornet[18362]: 2020/01/05 22:59:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: Valid milestone detected! Index: 1300549, Hash: BOAZVWF9AFJN9RCLEVDBOOZKCDKIBG9QTDRBYTEKOLAZFNALTZCXCLISSJXBXEJQVYHAJBGBXWYZZ9999
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: Invalid milestone detected! Err: Exists already, Index: 1300549: invalid milestone
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: Run solidity check for Milestone (1300549)...
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: Solidifier finished (4): passed: true, tx: 4, collect: 42.543µs, total: 382.508µs, entryTx: 0
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: Milestone confirmed (1300549): txsToConfirm: 635, collect: 14.115955ms, total: 28.393021ms
Jan 05 23:00:01 hornet-2 hornet[18362]: 2020/01/05 23:00:01 [ INFO ] Tangle: New solid milestone: 1300549
Jan 05 23:00:33 hornet-2 hornet[18362]: 2020/01/05 23:00:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32780...
Jan 05 23:00:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:00:33 hornet-2 hornet[18362]: 2020/01/05 23:00:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32780: use of closed network connection
Jan 05 23:00:33 hornet-2 hornet[18362]: 2020/01/05 23:00:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:01:10 hornet-2 hornet[18362]: 2020/01/05 23:01:10 [ INFO ] Tangle: Valid milestone detected! Index: 1300550, Hash: NSXUWCKBXJXTIVXQIBFVWB9HSNACVXFEBQLHSF9BHWTGFBFFMIARNNXOQODYIREAYICIDXWDCRVDZ9999
Jan 05 23:01:10 hornet-2 hornet[18362]: 2020/01/05 23:01:10 [ INFO ] Tangle: Run solidity check for Milestone (1300550)...
Jan 05 23:01:10 hornet-2 hornet[18362]: 2020/01/05 23:01:10 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 3, collect: 20.545µs, total: 38.998µs, entryTx: 0
Jan 05 23:01:10 hornet-2 hornet[18362]: 2020/01/05 23:01:10 [ INFO ] Tangle: Milestone confirmed (1300550): txsToConfirm: 686, collect: 9.78333ms, total: 19.673444ms
Jan 05 23:01:10 hornet-2 hornet[18362]: 2020/01/05 23:01:10 [ INFO ] Tangle: New solid milestone: 1300550
Jan 05 23:01:33 hornet-2 hornet[18362]: 2020/01/05 23:01:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32782...
Jan 05 23:01:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:01:33 hornet-2 hornet[18362]: 2020/01/05 23:01:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32782: use of closed network connection
Jan 05 23:01:33 hornet-2 hornet[18362]: 2020/01/05 23:01:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: Valid milestone detected! Index: 1300551, Hash: XDXFSRNRAHSNRPORQPHLCKPDHRCLQEFMKNGCW9QTAMWYONOPIEZCJHPCNRS9Q9GIGKEVVOVEMBOVA9999
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: Invalid milestone detected! Err: Exists already, Index: 1300551: invalid milestone
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: Run solidity check for Milestone (1300551)...
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 2, collect: 19.101µs, total: 21.563µs, entryTx: 0
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: Milestone confirmed (1300551): txsToConfirm: 696, collect: 6.303904ms, total: 25.532561ms
Jan 05 23:02:20 hornet-2 hornet[18362]: 2020/01/05 23:02:20 [ INFO ] Tangle: New solid milestone: 1300551
Jan 05 23:02:33 hornet-2 hornet[18362]: 2020/01/05 23:02:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32786...
Jan 05 23:02:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:02:33 hornet-2 hornet[18362]: 2020/01/05 23:02:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32786: use of closed network connection
Jan 05 23:02:33 hornet-2 hornet[18362]: 2020/01/05 23:02:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:03:33 hornet-2 hornet[18362]: 2020/01/05 23:03:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32788...
Jan 05 23:03:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:03:33 hornet-2 hornet[18362]: 2020/01/05 23:03:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32788: use of closed network connection
Jan 05 23:03:33 hornet-2 hornet[18362]: 2020/01/05 23:03:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:04:30 hornet-2 hornet[18362]: 2020/01/05 23:04:30 [ INFO ] Tangle: Valid milestone detected! Index: 1300552, Hash: HNVPYH99SEVWTOQYPMCRWEVDKYRVMVMLKVWATJIBYSQP9HMYMPFXFNSLPJQWYLZSGMIJFTAUKECO99999
Jan 05 23:04:30 hornet-2 hornet[18362]: 2020/01/05 23:04:30 [ INFO ] Tangle: Run solidity check for Milestone (1300552)...
Jan 05 23:04:30 hornet-2 hornet[18362]: 2020/01/05 23:04:30 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 2, collect: 30.303µs, total: 36.126µs, entryTx: 0
Jan 05 23:04:30 hornet-2 hornet[18362]: 2020/01/05 23:04:30 [ INFO ] Tangle: Milestone confirmed (1300552): txsToConfirm: 623, collect: 5.570706ms, total: 17.502393ms
Jan 05 23:04:30 hornet-2 hornet[18362]: 2020/01/05 23:04:30 [ INFO ] Tangle: New solid milestone: 1300552
Jan 05 23:04:33 hornet-2 hornet[18362]: 2020/01/05 23:04:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32792...
Jan 05 23:04:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:04:33 hornet-2 hornet[18362]: 2020/01/05 23:04:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32792: use of closed network connection
Jan 05 23:04:33 hornet-2 hornet[18362]: 2020/01/05 23:04:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:05:33 hornet-2 hornet[18362]: 2020/01/05 23:05:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32794...
Jan 05 23:05:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:05:33 hornet-2 hornet[18362]: 2020/01/05 23:05:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32794: use of closed network connection
Jan 05 23:05:33 hornet-2 hornet[18362]: 2020/01/05 23:05:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:05:51 hornet-2 hornet[18362]: 2020/01/05 23:05:51 [ INFO ] Tangle: Valid milestone detected! Index: 1300553, Hash: QFNQWPMQVDM9TPVEAAHYDGRXOJXK9MPP9ZYEAXMDSVVIAUHZLGEGAWXVDXHXUTBVVBQ99ZGPNYGQZ9999
Jan 05 23:05:51 hornet-2 hornet[18362]: 2020/01/05 23:05:51 [ INFO ] Tangle: Run solidity check for Milestone (1300553)...
Jan 05 23:05:51 hornet-2 hornet[18362]: 2020/01/05 23:05:51 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 2, collect: 7.751µs, total: 9.948µs, entryTx: 0
Jan 05 23:05:51 hornet-2 hornet[18362]: 2020/01/05 23:05:51 [ INFO ] Tangle: Milestone confirmed (1300553): txsToConfirm: 1262, collect: 16.232003ms, total: 32.760971ms
Jan 05 23:05:51 hornet-2 hornet[18362]: 2020/01/05 23:05:51 [ INFO ] Tangle: New solid milestone: 1300553
Jan 05 23:06:33 hornet-2 hornet[18362]: 2020/01/05 23:06:33 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32798...
Jan 05 23:06:33 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:06:33 hornet-2 hornet[18362]: 2020/01/05 23:06:33 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32798: use of closed network connection
Jan 05 23:06:33 hornet-2 hornet[18362]: 2020/01/05 23:06:33 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:07:08 hornet-2 hornet[18362]: 2020/01/05 23:07:08 [ INFO ] Tangle: Run solidity check for Milestone (1300554)...
Jan 05 23:07:08 hornet-2 hornet[18362]: 2020/01/05 23:07:08 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 2, collect: 19.624µs, total: 23.114µs, entryTx: 0
Jan 05 23:07:08 hornet-2 hornet[18362]: 2020/01/05 23:07:08 [ INFO ] Tangle: Valid milestone detected! Index: 1300554, Hash: UWUOAIYC9FLVNYAIOHFQFDMWZBQTJAC9TGGYWFGMZFWMJUZEMEDXRLQUOTWZXVJZKCBICJAMZCXIA9999
Jan 05 23:07:08 hornet-2 hornet[18362]: 2020/01/05 23:07:08 [ INFO ] Tangle: Milestone confirmed (1300554): txsToConfirm: 685, collect: 8.982384ms, total: 19.275403ms
Jan 05 23:07:08 hornet-2 hornet[18362]: 2020/01/05 23:07:08 [ INFO ] Tangle: New solid milestone: 1300554
Jan 05 23:07:34 hornet-2 hornet[18362]: 2020/01/05 23:07:34 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32800...
Jan 05 23:07:34 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:07:34 hornet-2 hornet[18362]: 2020/01/05 23:07:34 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32800: use of closed network connection
Jan 05 23:07:34 hornet-2 hornet[18362]: 2020/01/05 23:07:34 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:08:34 hornet-2 hornet[18362]: 2020/01/05 23:08:34 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32804...
Jan 05 23:08:34 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:08:34 hornet-2 hornet[18362]: 2020/01/05 23:08:34 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32804: use of closed network connection
Jan 05 23:08:34 hornet-2 hornet[18362]: 2020/01/05 23:08:34 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:09:34 hornet-2 hornet[18362]: 2020/01/05 23:09:34 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32806...
Jan 05 23:09:34 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:09:34 hornet-2 hornet[18362]: 2020/01/05 23:09:34 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:09:34 hornet-2 hornet[18362]: 2020/01/05 23:09:34 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32806: use of closed network connection
Jan 05 23:10:34 hornet-2 hornet[18362]: 2020/01/05 23:10:34 [ INFO ] Gossip: handling incoming connection from [REDACTED]:32810...
Jan 05 23:10:34 hornet-2 hornet[18362]: ReceivingState error: handshake failed: couldn't handshake properly: neighbors slots filled
Jan 05 23:10:34 hornet-2 hornet[18362]: 2020/01/05 23:10:34 [ ERROR ] Gossip: connection error on neighbor [REDACTED]: close tcp [REDACTED]:15600->[REDACTED]:32810: use of closed network connection
Jan 05 23:10:34 hornet-2 hornet[18362]: 2020/01/05 23:10:34 [ INFO ] Gossip: connection closed to [REDACTED]
Jan 05 23:10:52 hornet-2 hornet[18362]: 2020/01/05 23:10:52 [ INFO ] Tangle: Valid milestone detected! Index: 1300555, Hash: XDAIOD9AQPLZ9RGVZZVTFIUWLNAEOHPNEBAVDORKSIHOCF99BHBCIGYAPIGUQVLTXCWKJXPMLCOEA9999
Jan 05 23:10:52 hornet-2 hornet[18362]: 2020/01/05 23:10:52 [ INFO ] Tangle: Run solidity check for Milestone (1300555)...
Jan 05 23:10:52 hornet-2 hornet[18362]: 2020/01/05 23:10:52 [ INFO ] Tangle: Solidifier finished (2): passed: true, tx: 2, collect: 8.853µs, total: 11.173µs, entryTx: 0
Jan 05 23:10:52 hornet-2 hornet[18362]: 2020/01/05 23:10:52 [ INFO ] Tangle: Milestone confirmed (1300555): txsToConfirm: 704, collect: 7.327477ms, total: 17.088226ms
Jan 05 23:10:52 hornet-2 hornet[18362]: 2020/01/05 23:10:52 [ INFO ] Tangle: New solid milestone: 1300555
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Reconnecter
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Reconnecter ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping TCP Server ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping TCP Server ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Closing neighbor connections ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: read tcp [REDACTED]:38574->[REDACTED]:15600: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: close tcp [REDACTED]:38574->[REDACTED]:15600: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: read tcp [REDACTED]:34374->[REDACTED]:15600: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: close tcp [REDACTED]:34374->[REDACTED]:15600: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: connection closed to [REDACTED]:15600
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15601: read tcp [REDACTED]:56220->[REDACTED]:15601: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15601: close tcp [REDACTED]:56220->[REDACTED]:15601: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: connection closed to [REDACTED]:15600
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: connection closed to [REDACTED]:15601
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15602: read tcp [REDACTED]:54994->[REDACTED]:15602: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15602: close tcp [REDACTED]:54994->[REDACTED]:15602: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: connection closed to [REDACTED]:15602
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: read tcp [REDACTED]:15600->[REDACTED]:53408: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: close tcp [REDACTED]:15600->[REDACTED]:53408: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: connection closed to [REDACTED]:15600
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ ERROR ] Gossip: connection error on neighbor [REDACTED]:15600: close tcp [REDACTED]:53292->[REDACTED]:15600: use of closed network connection
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Closing neighbor connections ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Gossip Send Queue Dispatcher ([REDACTED]:15600) ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Gossip Send Queue Dispatcher ([REDACTED]:15600) ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping PacketProcessor ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping PacketProcessor ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Broadcast Queue Dispatcher ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping Broadcast Queue Dispatcher ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping ReplyProcessor ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping ReplyProcessor ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[ReceiveTx] ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[ReceiveTx] ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping Solidifier ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping Solidifier ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[CheckForMilestone] ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[CheckForMilestone] ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[MilestoneSolidifier] ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping TangleProcessor[MilestoneSolidifier] ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping STINGRequestsProcessor ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Gossip: Stopping STINGRequestsProcessor ... done
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping UnconfirmedTxPersister ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping AddressPersister ...
Jan 05 23:11:18 hornet-2 hornet[18362]: 2020/01/05 23:11:18 [ INFO ] Tangle: Stopping AddressPersister ... done
Jan 05 23:11:19 hornet-2 hornet[18362]: 2020/01/05 23:11:19 [ INFO ] Tangle: Stopping UnconfirmedTxPersister ... done
Jan 05 23:11:19 hornet-2 hornet[18362]: 2020/01/05 23:11:19 [ INFO ] Tangle: Flushing caches to database...
Jan 05 23:14:22 hornet-2 systemd[1]: hornet.service: State 'stop-sigterm' timed out. Killing.
Jan 05 23:14:22 hornet-2 systemd[1]: hornet.service: Killing process 18362 (hornet) with signal SIGKILL.
Jan 05 23:14:22 hornet-2 systemd[1]: hornet.service: Main process exited, code=killed, status=9/KILL
Jan 05 23:14:22 hornet-2 systemd[1]: hornet.service: Failed with result 'timeout'.

config.json
{
    "api": {
        "auth": {
            "password": "",
            "username": ""
        },
        "host": "<IP_ADDRESS>",
        "maxbodylength": 1000000,
        "maxfindtransactions": 100000,
        "maxgettrytes": 1000,
        "maxrequestslist": 1000,
        "permitRemoteAccess": [
            "getNodeInfo",
            "getBalances",
            "checkConsistency",
            "getTransactionsToApprove",
            "getInclusionStates",
            "getNodeAPIConfiguration",
            "wereAddressesSpentFrom",
            "broadcastTransactions",
            "findTransactions",
            "storeTransactions",
            "getTrytes"
        ],
        "port": 14265,
        "remoteauth": ""
    },
    "compass": {
        "loadLSMIAsLMI": false
    },
    "dashboard": {
        "basic_auth": {
            "enabled": false,
            "password": "hornet",
            "username": "hornet"
        },
        "dev": false,
        "host": "<IP_ADDRESS>",
        "port": 8081
    },
    "db": {
        "path": "/mnt/mainnet/mainnetdb"
    },
    "localsnapshots": {
        "path": "/mnt/mainnet/2019-12-26_113404_UTC-export.gz.bin"
    },
    "milestones": {
        "coordinator": "EQSAUZXULTTYZCLNJNTXQTQHOMOFZERHTCGTXOLTVAHKSA9OGAZDEKECURBRIXIJWNPFCQIOVFVVXJVD9",
        "coordinatorsecuritylevel": 2,
        "numberofkeysinamilestone": 23
    },
    "monitor": {
        "apiPort": 4433,
        "domain": "",
        "host": "<IP_ADDRESS>",
        "port": 4434,
        "tanglemonitorpath": "tanglemonitor/frontend"
    },
    "network": {
        "address": "<IP_ADDRESS>",
        "port": 15600,
        "preferIPv6": false,
        "reconnectattemptintervalseconds": 60
    },
    "node": {
        "disableplugins": [

        ],
        "enableplugins": [

        ],
        "loglevel": 127
    },
    "profiles": {
        "custom": {
            "badger": {
                "ZSTDCompressionLevel": 10,
                "blockSize": 4096,
                "bloomFalsePositive": 0.01,
                "compactLevel0OnClose": false,
                "eventLogging": false,
                "keepL0InMemory": false,
                "levelOneSize": 268435456,
                "levelSizeMultiplier": 10,
                "logRotatesToFlush": 2,
                "maxCacheSize": 50000000,
                "maxLevels": 7,
                "maxTableSize": 67108864,
                "numCompactors": 2,
                "numLevelZeroTables": 5,
                "numLevelZeroTablesStall": 10,
                "numMemtables": 5,
                "numVersionsToKeep": 1,
                "syncWrites": false,
                "tableLoadingMode": 2,
                "valueLogFileSize":<PHONE_NUMBER>,
                "valueLogLoadingMode": 2,
                "valueLogMaxEntries": 1000000,
                "valueThreshold": 32,
                "verifyValueChecksum": false,
                "withTruncate": false
            },
            "caches": {
                "approvers": {
                    "evictionSize": 1000,
                    "size": 100000
                },
                "bundles": {
                    "evictionSize": 1000,
                    "size": 20000
                },
                "incomingTransactionFilter": {
                    "size": 5000
                },
                "milestones": {
                    "evictionSize": 100,
                    "size": 1000
                },
                "refsInvalidBundle": {
                    "size": 10000
                },
                "requestQueue": {
                    "size": 100000
                },
                "spentAddresses": {
                    "evictionSize": 1000,
                    "size": 5000
                },
                "transactions": {
                    "evictionSize": 1000,
                    "size": 50000
                }
            }
        }
    },
    "protocol": {
        "mwm": 14
    },
    "spammer": {
        "address": "HORNET99INTEGRATED99SPAMMER999999999999999999999999999999999999999999999999999999",
        "depth": 3,
        "message": "Spamming with HORNET tipselect",
        "tag": "HORNET99INTEGRATED99SPAMMER",
        "tpsratelimit": 0.1,
        "workers": 1
    },
    "tipsel": {
        "belowmaxdepthtransactionlimit": 20000,
        "maxdepth": 15
    },
    "useProfile": "2gb",
    "zmq": {
        "host": "<IP_ADDRESS>",
        "port": 5556
    }
}

hornet.service
[Unit]
Description=Hornet Fullnode
After=network.target

[Service]
TimeoutStopSec=900
User=hornet
Group=hornet
ExecStart=/usr/local/bin/hornet \
  --config-dir /etc/hornet
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
LimitNOFILE=131072

[Install]
WantedBy=multi-user.target

Should be solved with #199


Publish module

Hello.
Please, publish the module on npmjs.org.

I can't install it by command in README.md
npm install js-yaml-js-types

Done. Thanks.

Done. Thanks.


RAC-5253 delete install web ui from zip

delete the web ui installation  from zip file.
We support 3 ways to install web-ui

apt-get install, work with apt-get install rackhd.
docker images, work with docker-compose up rackhd
if users installed rackhd with src, they should clone web-ui src and build statics manually.

test this please

Can you please elaborate the way #3 ?
if people run RackHD from src code, and do npm install.
which document can people follow to build/copy on-web-ui.

@panpan0000
I'll add some docs in on-http README!

As what we talk, the concern is
if people using Node4 to install rackhd from src, but you request them to build on-web-ui by themselves, which requires Node6...
Let's keep -1 👎   until this gets clarified.
@iceiilin

BUILD peter-test » on-dhcp-proxy-test #13 : FAILURE

BUILD on-http #640 : FAILURE


parser: implement Restore for DropTableStmt

implement Restore for DropTableStmt#Restore
add ddl_test.go#TestDropTableRestore

Issue: pingcap/tidb#8532

Thanks for the contribution, however the same feature has already been submitted as #107, so I'm closing this as duplicate. Sorry for inconvenience.


[6.x] Introduce StrProxy for collection like string manipulation

Right now if we want to do any manipulation with strings we face same problem like with an array before collections where we have to read the code inside out.
use Illuminate\Support\Str;

$title = Str::title(Str::replaceArray('_', [' '], Str::snake('fooBar')));

Also Str object in Laravel does not accept the string that is being manipulated as the first argument across all methods like replaceArray().
It would be great to bring that kind of power and functionality to Laravel and surpass current language limitations.
use Illuminate\Support\StrProxy;

$title = (new StrProxy('fooBar'))->snake()->replaceArray('_', [' '])->title()->get();

Also str helper function or Str::make to make it even cleaner.
use Illuminate\Support\Str;

$title = Str::make('fooBar')->snake()->replaceArray('_', [' '])->title()->get();
$title = str('fooBar')->snake()->replaceArray('_', [' '])->title()->get();

Having dd() on that object is a must :D
$title = str('fooBar')->snake()->replaceArray('_', [' '])->dd()->title()->get();

:-1: for the global helper.

I think this would be a cool package.


Support interactive elements

@liarco here is what I've come up with based on our conversation. I opted for using a CSS class instead of a new data-attribute since it's really a simple boolean (it's either visible or not) and it's tied directly to CSS styling.
I added it to the main documentation page so if you pull this branch and start it up you should see the clickable link on your localhost.

Merging this improvement in with some other dependency bumps and fixes this morning. Thanks again for your help! Please let me know if you notice any other issues.


Travis fix and improve

Remove HHVM and PHP7 from allowed failure (it works!)
Remove unsupported HHVM nightly: https://travis-ci.org/escapestudios/Symfony2-coding-standard/jobs/93497660#L70

Thanks for your contribution @Soullivaneuh - I've left the hhvm allowed failure in place though...
Kind regards,
David

I've left the hhvm allowed failure in place though...

Can you please elaborate why? This is working with HHVM.

If at some point the build were to fail, that failure should be allowed...
Hope this helps!

I would say that if at some points the build is going to fail, we should fix it. :-)

...gave this some more thought and decided not to treat HHVM as a second class citizen any longer :-)

:+1:


Set up GitHub actions

Follows: https://github.com/appsignal/docs-nextjs/issues/147

[x] Tests
[x] Formatting
[x] Lint fix

Closed, since already implemented.


Migrated codebase to work as an action

Updated codebase to run as an action instead of a application.
This PR mainly removes most of the boilerplate and code unrelated to the action itself and adapts everything to work in a more organized and abstract way.
It splits the architecture into an object oriented dependency injection system, having the class Synchronizer handling all the business logic and the classes ProjectKit,IssueKit and CoreLogger handling specific subtasks.
To be able to fine-grain the project permissions and keep the highest level of security possible while maintaining a sane codebase, the action of each token has been split into its own class:

ProjectKit uses a PAT with organization access as it needs to interact with the project API (which is part of an organization instead of a repository).
IssueKit uses the autogenerated GitHub token to fetch information from the issues API available in the repository.

ProjectKit is still in development, as it's missing the ability to update custom fields (#44) and it's using a deprecated API (#46) so it's prone to changes in the following PRs.
This PR is aimed at a feature branch and not at the master branch. The reason for this is because this task does not contemplate all the necessary features to launch this action. This is the first task of many which can be found in the milestone: GitHub Action port. Once all this tasks have been completed, the feature branch will be merged into master replacing the current functionality.
This PR also removes the ability to use custom labeling and custom fields. This will be added later to the feature branch.
The action was ported to work as a Docker image instead of a JavaScript image. This is because the docker image allows to build the action on demand (currently ~45 seconds). A more efficient method will be proposed later but for the current development process this satisfies the requirements.
This PR resolves #43.

This PR is aimed at a feature branch and not at the master branch. The reason for this is because this task does not contemplate all the necessary features to launch this action. This is the first task of many which can be found in the milestone: GitHub Action port. Once all this tasks have been completed, the feature branch will be merged into master replacing the current functionality.

Soo, should we also review the code in the feature branch then? Or was it reviewed already?

Soo, should we also review the code in the feature branch then? Or was it reviewed already?

No, as there are no changes. The feature branch has just been created for this PR. It's currently up to date with master so there isn't anything new in it.

Ah, I was probably looking at the head branch, thinking it's the base...

Other than that looks good

@mutantcornholio I'm planning on adding the linting rules again but in a different issue #47.
Can we wait until that PR?

@mutantcornholio I'm planning on adding the linting rules again but in a different issue #47.
Can we wait until that PR?

Doesn't feel like something out of scope, but sure