text:
Set DNS-SD service name/type for the directory

A service type for the directory service is not yet registered at IANA. But it is worth some improvements in our implementation.
Currently the the type is set to: _linksmart-td._tcp
Other works related to this:
https://github.com/w3c/wot-discovery/tree/18820a3f31f191f3e3689158672decf6c906bbf6/prior-work/fujitsu
https://github.com/w3c/wot-discovery/issues/5

Proposal:
<instance-name>._directory._sub._wot._tcp where instance is configurable defaulting to linksmart. The instance name should be made unique in each environment.
The <Instance> portion of the Service Instance Name is a user-
   friendly name consisting of arbitrary Net-Unicode text [RFC5198].  It
   MUST NOT contain ASCII control characters (byte values 0x00-0x1F and
   0x7F) [RFC20] but otherwise is allowed to contain any characters,
   without restriction, including spaces, uppercase, lowercase,
   punctuation -- including dots -- accented characters, non-Roman text,
   and anything else that may be represented using Net-Unicode.  For
   discussion of why the <Instance> name should be a user-visible, user-
   friendly name rather than an invisible machine-generated opaque
   identifier, see Appendix C, "What You See Is What You Get".

The <Instance> portion of the name of a service being offered on the
   network SHOULD be configurable by the user setting up the service, so
   that he or she may give it an informative name.  However, the device
   or service SHOULD NOT require the user to configure a name before it
   can be used.  A sensible choice of default name can in many cases
   allow the device or service to be accessed without any manual
   configuration at all.  The default name should be short and
   descriptive, and SHOULD NOT include the device's Media Access Control
   (MAC) address, serial number, or any similar incomprehensible
   hexadecimal string in an attempt to make the name globally unique.

https://tools.ietf.org/html/rfc6763#section-4.1.1
When a DNS-SD service is advertised using Multicast DNS [RFC6762], if
   there is already another service of the same type advertising with
   the same name then automatic name conflict resolution will occur.  As
   described in the Multicast DNS specification [RFC6762], upon
   detecting a conflict, the service should:

   1.  Automatically select a new name (typically by appending or
       incrementing a digit at the end of the name),
   2.  Try advertising with the new name, and
   3.  Upon success, record the new name in persistent storage.

   This renaming behavior is very important, because it is key to
   providing user-friendly instance names in the out-of-the-box factory-
   default configuration.

https://tools.ietf.org/html/rfc6763#appendix-D

Service registration with subtype fails using several tested clients.
CLI registration:
macOS:
$ dns-sd -R "thing directory" _directory._sub._wot._tcp local. 8081
Registering Service thing directory._directory._sub._wot._tcp.local. port 8081
DNSService call failed -65540

Debian:
$ avahi-publish -s "thing directory" "_directory._sub._wot._tcp" 8081
Failed to add service: Invalid service type

Implemented with _wot._tcp type and _directory subtype. Instance name is configurable.

repo: linksmart/thing-directory


text:
[Do Not Merge] LKE Beta Endpoints

Adds LKE Beta endpoints:

/lke/clusters
/lke/clusters/{clusterId}
/lke/clusters/{clusterId}/pools
/lke/clusters/{clusterId}/pools/{poolId}
/lke/clusters/{clusterId}/kubeconfig
/lke/versions
/lke/versions/{version}

Note: This work was started by @asauber and @jfrederickson in bits repo. This adds latest updates to that worki.

please add:
lke:read_only
lke:read_write
to the oauth schema section and to the front information section

A general note for beta - LKE is available in us-central and with Kubernetes version 1.16, these should be updated in the examples.

Additionally we want to add a link to the beta sign up page with the beta note.

source: gharchive/pull-request

authors: hzoppetti leslitagordita

repo: linode/linode-api-docs

license_type: permissive

license_source: github-api


text:
upcoming: [M3-7972] - Invalidate PG queries on Linode create/delete

Description 📝
Now that the POST & DELETE linode/instances Alpha endpoint have been updated to work with placement groups, we need to invalidate the related PG if:

on POST (create linode) we assign a placement group
on DELETE (delete linode) we delete a linode assigned to a placement group

Changes  🔄

Invalidate PG queries on Linode create & delete mutations

Preview 📷

Create Linode (and assign to PG)
Delete Linode (and unassign from PG)

How to test 🧪
Prerequisites

Using alpha environment and having the "Placement Group" feature flag enabled, either:

use your account (need the placement-group customer tag
use the pg-user-1 (see creds in 1Password vault)

Have at least one Placement Group created

Verification steps

See the video above:

Create a linode and assign to a PG: confirm UI updates accordingly in the placement group section
Delete a linode that has a linode assigned: confirm UI updates accordingly in the placement group section

As an Author I have considered 🤔
Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

I was able to verify that create and delete/unassign operations worked as expected by the changes. The linode count updated in the UI accordingly and did not observe any regressions.

authors: abailly-akamai carrillo-erik

repo: linode/manager


text:
M3-6044: Create Button "Create Using Command Line" and show modal

Description 📝

This story is part of feature API-CLI.
Team, guide me incase I miss setting any process oriented things before kicking off feature development. (feature flag, etc..)
Note: ga events are in my radar, if need following PR's will cover that.

What does this PR do?

Shows API-CLI awareness modal upon clicking "Create Create Using Command Line"

Preview 📷

How to test 🧪

Navigate to create Linode page
Scroll to bottom and click ""Create Create Using Command Line"" button.
Should show the modal.

Work in progress...
How do I run relevant unit or e2e tests?
yarn test ApiAwarenessModal

As a thought, if the intent is to bring awareness about the command line options to other entities as well in the future, maybe ApiAwarenessModal can be made a little more generic now by passing the modal copy/contents in as a child.
It'd look something like:
<Dialog>
     {children}
     <ActionsPanel>
          ...
     </ActionsPanel>
</Dialog>

the JSX for this specific modal would be defined in LinodeCreate.tsx and then passed as a children/render prop to <ApiAwarenessModal />.
If we take this approach, the component and its test should be moved from the /LinodesCreate directory too

Good call @dwiley-akamai! That was one of the reason for decoupling ApiAwarenessModal from LinodeCreate in this iteration. But, we could definitely make it as more generic considering future wireframes it will be more clearer to convert ApiAwarenessModal as reusable.


text:
Scanse Sweep compatibility

Hi,
I'm using linorobot with Jetson Nano (Ubuntu 18.04), Arduino Mega and Sweep Lidar.
I configured the linobase module and the minimal.launch is working fine.
In order to be able to use Sweep Lidar I added it's package into the linorobot directory and catkin_make it. After that, I changed the linorobot launch files to run the sweep lidar launch file.
When I launch the bringup.launch file, I receive those error.
My question is: What else would need to be done in order to use the Sweep Lidar?
started roslaunch server http://192.168.43.50:34635/

SUMMARY
========

PARAMETERS
 * /apply_calib/calib_file: /home/jetson/lino...
 * /apply_calib/calibrate_gyros: True
 * /ekf_localization/base_link_frame: base_footprint
 * /ekf_localization/diagnostics_agg: True
 * /ekf_localization/frequency: 50
 * /ekf_localization/imu0: /imu/data
 * /ekf_localization/imu0_config: [False, False, Fa...
 * /ekf_localization/imu0_differential: True
 * /ekf_localization/imu0_relative: True
 * /ekf_localization/odom0: /raw_odom
 * /ekf_localization/odom0_config: [False, False, Fa...
 * /ekf_localization/odom0_differential: True
 * /ekf_localization/odom0_relative: False
 * /ekf_localization/odom_frame: odom
 * /ekf_localization/two_d_mode: True
 * /ekf_localization/world_frame: odom
 * /imu_filter_madgwick/fixed_frame: base_footprint
 * /imu_filter_madgwick/orientation_stddev: 0.05
 * /imu_filter_madgwick/publish_tf: False
 * /imu_filter_madgwick/use_mag: True
 * /imu_filter_madgwick/use_magnetic_field_msg: True
 * /imu_filter_madgwick/world_frame: enu
 * /pointcloud_to_laserscan/angle_increment: 0.0174533
 * /pointcloud_to_laserscan/angle_max: 3.14
 * /pointcloud_to_laserscan/angle_min: -3.14
 * /pointcloud_to_laserscan/concurrency_level: 1
 * /pointcloud_to_laserscan/max_height: 1.0
 * /pointcloud_to_laserscan/min_height: -1.0
 * /pointcloud_to_laserscan/range_max: 40.0
 * /pointcloud_to_laserscan/range_min: 0.0
 * /pointcloud_to_laserscan/scan_time: 0.1
 * /pointcloud_to_laserscan/target_frame: laser
 * /pointcloud_to_laserscan/transform_tolerance: 0.001
 * /pointcloud_to_laserscan/use_inf: True
 * /rosdistro: melodic
 * /rosserial_lino/baud: 57600
 * /rosserial_lino/port: /dev/linobase
 * /rosversion: 1.14.5
 * /sweep_node/frame_id: laser
 * /sweep_node/serial_baudrate: 115200
 * /sweep_node/serial_port: /dev/linolidar

NODES
  /
    apply_calib (imu_calib/apply_calib)
    base_footprint_to_base_link (tf2_ros/static_transform_publisher)
    base_footprint_to_imu_link (tf2_ros/static_transform_publisher)
    base_link_to_laser (tf2_ros/static_transform_publisher)
    ekf_localization (robot_localization/ekf_localization_node)
    imu_filter_madgwick (imu_filter_madgwick/imu_filter_node)
    lino_base_node (linorobot/lino_base_node)
    pointcloud_to_laserscan (pointcloud_to_laserscan/pointcloud_to_laserscan_node)
    rosserial_lino (rosserial_python/serial_node.py)
    sweep_node (sweep_ros/sweep_node)

auto-starting new master
process[master]: started with pid [26933]
ROS_MASTER_URI=http://192.168.43.50:11311

setting /run_id to 11079158-8627-11ea-ad52-12ed0dd4ce4d
process[rosout-1]: started with pid [26944]
started core service [/rosout]
process[rosserial_lino-2]: started with pid [26951]
process[apply_calib-3]: started with pid [26952]
process[imu_filter_madgwick-4]: started with pid [26953]
process[base_footprint_to_imu_link-5]: started with pid [26954]
[ INFO] [1587731298.663476387]: Starting ImuFilter
[ INFO] [1587731298.677961559]: Using dt computed from message headers
[ INFO] [1587731298.724266254]: Imu filter gain set to 0.100000
[ INFO] [1587731298.724941426]: Gyro drift bias set to 0.000000
[ INFO] [1587731298.725399145]: Magnetometer bias values: 0.000000 0.000000 0.000000
process[lino_base_node-6]: started with pid [26965]
process[base_footprint_to_base_link-7]: started with pid [26971]
process[ekf_localization-8]: started with pid [26972]
process[sweep_node-9]: started with pid [26983]
process[pointcloud_to_laserscan-10]: started with pid [26985]
process[base_link_to_laser-11]: started with pid [26987]
[ WARN] [1587731299.346980673]: Both imu0_differential and imu0_relative were set to true. Using differential mode.
[INFO] [1587731300.024167]: ROS Serial Python Node
[INFO] [1587731300.042407]: Connecting to /dev/linobase at 57600 baud
[INFO] [1587731302.160059]: Requesting topics...
Error: invalid response header checksum
[INFO] [1587731302.361959]: Note: publish buffer size is 512 bytes
[INFO] [1587731302.367370]: Setup publisher on raw_imu [lino_msgs/Imu]
[INFO] [1587731302.380240]: Note: subscribe buffer size is 512 bytes
[INFO] [1587731302.384288]: Setup subscriber on pid [lino_msgs/PID]
[INFO] [1587731302.396869]: Setup subscriber on cmd_vel [geometry_msgs/Twist]
[INFO] [1587731302.403159]: LINOBASE CONNECTED
[ERROR] [1587731302.409229]: Tried to publish before configured, topic id 125
[INFO] [1587731302.413351]: Requesting topics...
[ERROR] [1587731302.429750]: Tried to publish before configured, topic id 125
[INFO] [1587731302.433974]: Requesting topics...
[sweep_node-9] process has finished cleanly
log file: /home/jetson/.ros/log/11079158-8627-11ea-ad52-12ed0dd4ce4d/sweep_node-9*.log
[INFO] [1587731302.457929]: Setup publisher on raw_imu [lino_msgs/Imu]
[ERROR] [1587731302.488946]: Tried to publish before configured, topic id 125
[INFO] [1587731302.493745]: Requesting topics...
[INFO] [1587731302.538571]: Setup publisher on raw_vel [lino_msgs/Velocities]
[INFO] [1587731302.549725]: Setup publisher on raw_imu [lino_msgs/Imu]
[INFO] [1587731302.622646]: Setup publisher on raw_vel [lino_msgs/Velocities]
[INFO] [1587731302.638786]: Setup publisher on raw_imu [lino_msgs/Imu]
[ INFO] [1587731302.693795733]: Calibrating gyros; do not move the IMU
[ WARN] [1587731308.828438073]: Still waiting for data on topics /imu/data_raw and /imu/mag...
[ INFO] [1587731310.355790401]: Gyro calibration complete! (bias = [-0.056, 0.037, -0.012])
[ INFO] [1587731310.508411130]: First pair of IMU and magnetometer messages received.

Hi,
Can you share your launch files please? Thanks

Hi,
Sorry for late response. I configured the environment as you said but the error still occurs.
These are the launch files.
../linorobot/launch/include/laser.launch
<launch>
    <!-- Run Linorobot compatible laser drivers. Takes reference from env var LINOLIDAR. ie. export LINOLIDAR=xv11 -->
    <include file="$(find linorobot)/launch/include/lidar/sweep.launch" />
    <!-- Publish static transform of the laser. Define your sensor offset here -->
    <node pkg="tf2_ros" type="static_transform_publisher" name="base_link_to_laser" args="0.065 0 0.098 0 0 0  /base_link /laser"/>
</launch>

../linorobot/launch/include/lidar/sweep.launch (here I added the conversion between pc2 and laserscan)
<launch>
    <!-- run sweep_node node -->
    <node name="sweep_node"          pkg="sweep_ros"  type="sweep_node" output="screen">
            <param name="serial_port"         type="string" value="/dev/linolidar"/>
            <param name="serial_baudrate"     type="int"    value="115200"/>
            <param name="frame_id"            type="string" value="laser"/>
    </node>

    <!-- run pointcloud_to_laserscan node -->
    <node pkg="pointcloud_to_laserscan" type="pointcloud_to_laserscan_node" name="pointcloud_to_laserscan">

        <remap from="cloud_in" to="pc2"/>
        <rosparam>
            target_frame: laser # Leave disabled to output scan in pointcloud frame
            transform_tolerance: 0.001
            min_height: -1.0
            max_height: 1.0

            angle_min: -3.14 # -M_PI/2
            angle_max: 3.14 # M_PI/2
            angle_increment: 0.0174533 # M_PI/360.0
            scan_time: 0.1
            range_min: 0.0
            range_max: 40.0
            use_inf: true

            # Concurrency level, affects number of pointclouds queued for processing and number of threads used
            # 0 : Detect number of cores
            # 1 : Single threaded
            # 2->inf : Parallelism level
            concurrency_level: 1
        </rosparam>
    </node>
</launch>

Your launch files looks good. Just omit the pointcloud_to_laserscan.
Also make sure that sweep publishes that data in "laser" frame. Otherwise, you have to rename "laser" in static_transform_publisher to the correct frame the LIDAR is using.

The problem was not the lidar itself, it worked well, but the udev rules that i've manually created. I observed that each time when I plugged in a new lino device (LiDAR / Arduino Mega) each device was bound on the same ttyUSB* port.
So, I followed the https://github.com/linorobot/linorobot/issues/31#issuecomment-602075774 instructions to configure the libgudev on my ubuntu 18.04, and after the port configurations provided by the lino_udev script, I still had to manually configure the port for Arduino Mega.
But it works now, thank you!

source: gharchive/issue

authors: Valentinkvn grassjelly

repo: linorobot/linorobot


text:
Update default threading behavior

If a message was sent in a thread, answer in a thread per default.

Hey! Looks good, how about adding a test for this? That would help merging it faster. Thanks!

Hey @jsargiot, thanks for the response. I won't make it to create a custom testing instance of Slack nor configure Travis. It would be way easier for me (and everybody else who wants to contribute), if you could setup your Travis to run all the tests. If you are concerned about user that are not that familiar with git and that add several commits to fix test errors, you could automatically squash all commits of a PR.

Have you read https://docs.travis-ci.com/user/pull-requests/?

authors: jonas-schulze jsargiot

license: mit

license_source: bigquery


text:
fix: Enable PostgreSQL stream selection for c9s and RHEL9

c9s/RHEL9 provides PostgreSQL 13 as the default system version as a classic RPM package. Alternative versions are provided as modular content. So, it requires a different installation procedure.
Issue Tracker Tickets (Jira or BZ if any): RHEL-5274

[citest]

lgtm - I can confirm that using postgresql_version: "16" correctly installs version 16 on centos-9.
Once the ci tests pass, we can merge

repo: linux-system-roles/postgresql

license: MIT


text:
Increase healthcheck retries

Signed-off-by: Mohamed Abokammer mahmednabil109@gmail.com

Codecov Report

Merging #151 (b815f94) into main (a091455) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   63.18%   63.18%
=======================================
  Files         165      165
  Lines       10383    10383
=======================================
+ Hits         6560     6561    +1
+ Misses       3096     3094    -2
- Partials      727      728    +1

Flag
Coverage Δ

e2e
48.95% <ø> (+0.02%)
:arrow_up:

integration
54.39% <ø> (+0.05%)
:arrow_up:

unittests
48.89% <ø> (-0.08%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/runner/step_runner.go
88.84% <0.00%> (-0.40%)
:arrow_down:

pkg/jobmanager/jobmanager.go
78.02% <0.00%> (+1.09%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

repo: linuxboot/contest


text:
New Twitter Update : Tweet with Multi Media

Hello
In the new update, people can share a tweet with multi media(For example photo, video and gif);
Tweets.GetTweetAsync gives the first media in tweet and doesn't show another media in Media Property.
Can I fix it? or you should correct it?
Thanks a lot.

Please see #1198

Please see #1198

Thanks;but there isn's Variants property in the TweetsV2.GetTweetAsync method.
How can I fix it?
Thank you.

My pull request hasn't been merged yet.
What I did was to clone the repo / make the fix the variants, and the the fixed dll and not the nuget one.

My pull request hasn't been merged yet.
What I did was to clone the repo / make the fix the variants, and the the fixed dll and not the nuget one.

Ok.
Thanks🙏🏼

My pull request hasn't been merged yet.
What I did was to clone the repo / make the fix the variants, and the the fixed dll and not the nuget one.

Hello
I want to know, can I have the dll that you fix it before merging pull request?
Thank you

My pull request hasn't been merged yet. What I did was to clone the repo / make the fix the variants, and the the fixed dll and not the nuget one.

I cloned the repo and changed the files(your commits), but the variates is null;
Do you know how to fix it?
Thanks.

repo: linvi/tweetinvi


text:
Make Geospatial Data Lake repo public

There are organisations outside of LINZ that are interested in what we are doing. We should make the repo public as soon as possible. I think it's fine to do this while it's a work in progress as long as we indicate that somehow.
Tasks

[x] LGTM
[x] check source code for non public content
[x] open and close tickets

Thanks @SPlanzer. Closing this issue as done.

repo: linz/geospatial-data-lake


text:
Theft of Vitae

text: If both combatants strike with Theft of Vitae while one of the vampires are at 0 blood, no blood is stolen from the empty vampire (but blood would still move to the empty vampire).
link: https://groups.google.com/g/rec.games.trading-cards.jyhad/c/BHeGvhd4yEA/m/SdKih5fV34wJ

Keeping it for after refactoring, will ne to be applied on all blood stealing cards:

Form of the Cobra [pro]
Theft of Vitae
Donnybrook [ser]
Call the Lamprey
Tongue of the Serpent
Veiled Sight [CHI]
Hunger of Marduk
Drain Essence
Diversion [tha]
Absorb the mind [myt], [MYT]
Kraken's Kiss [VIC]
200078|Anastasz di Zagreb (G3)
200528|Goratrix (G2)
200976|Menele (G3 ADV) [MERGED]
201345|Tariq, The Silent (G2 ADV)
201517|Lord Leopold Valdemar (G5)

authors: codex-krcg lionel-panhaleux

repo: lionel-panhaleux/krcg


text:
Prevent spurious SET SEARCH_PATH SQL statements for Postgres during update-sql command. Fixes #5316

Impact

[X] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Prevent resetting the search path in Postgres after a rollback if we are running in a mode that does not update the database to avoid spurious SET SEARCH_PATH SQL statements.
The logic in DatabaseUtils.initializeDatabase for Postgres expects changes to the SEARCH_PATH to be persisted to detect when the SEARCH_PATH is already correct(ed). However in update-sql mode these changes are not executed, causing the detection mechanism to fail and resulting in extra SET SEARCH_PATH statements.

Things to be aware of
I'm aware of the other change in review that will fix this issue, but that is a bigger change and might take a long time to be merged. This could be a quick win.

Things to worry about

Additional Context

Hi @mpvvliet ! Your PR handles the same as https://github.com/liquibase/liquibase/pull/5444 and also fixes https://github.com/liquibase/liquibase/issues/5316  just aiming at update-sql and does not modifies the user database settings using alter database session. What do you think about the solution proposed in the other PR?

@filipelautert I like the solution in the PR #5444 because it avoids the need to re-apply the SEARCH_PATH changes. However since that PR is bigger and seems stuck, I proposed this smaller one.
Happy to close this one if the other one has a shot of getting finalised soon.

AS PR #5444 still pending some tests let's move this one ahead, and if it gets merged we can revert this one here. Thanks @mpvvliet !

@filipelautert @MalloD12 should be merged functional test fix with https://github.com/liquibase/liquibase-pro-tests/pull/1445

authors: filipelautert mpvvliet rberezen

repo: liquibase/liquibase


text:
Simplify command titles to just the command (rather than the whole signature)

Overview
Right now we have command seciton headers like 'executable command ', etc. This is pretty wordy and we want to swap that so the section header is just the command name, which is followed by the full signature as text (but not heading). We do, however, want to retain the full command sig in the anchor ID in order to avoid ambiguation in a case like 'exec foo' and 'exec bar foo', which would have the same headins, but in a different context.

Work for this issue will begin begin on branch work-liquid-labs/command-line-documentation/9.

repo: liquid-labs/command-line-documentation


text:
Brian Neff added MCC clock divider example to basic package

Ben, I just wanted to try a very simple example to get this started.  If this all works, I'll start pushing more.

Merged in a new PR #10

repo: liquidinstruments/moku-examples


text:
[bugs] top level await + optional chaining (?.) will build product syntax error

// main.ts
// bugs reproduction
// top level await
console.log(await window?.fetch(`/`));
export {};

// test-top-level-await.user.js
// ==UserScript==
// @name       test-top-level-await
// @namespace  vite-plugin-monkey
// @version    0.0.0
// @author     monkey
// @match      https://songe.li
// ==/UserScript==

(async function () {
	'use strict';

	console.log((await fetch == null ? void 0 : fetch(`/`))));
        // An extra parenthesis
})();

fixed by v3.4.1

repo: lisonge/vite-plugin-monkey


text:
[New/Revise] improve parameter estimation performance with constant liar and shorter timeout_iteration

Summary of this new feature
Improve performance (estimation score and runtime) of parameter estimation with the following solutions.

improve estmation score with constant liar
optuna provides new option constant_liar of TPESampler at version 2.8.0. Constant Liar heuristic reduces search effort, avoiding trials which trys similar parameter sets. Please refer to their detailed explanations and discussions with Optuna version 2.8.0 release note. It will be great for CovsirPhy users to use constant_liar=True if Optuna version 2.8.0 is available in our environments.
Improve runtime with shorter time_iteration
At version 2.20.3, Scenario.estimate(timeout_iteration=5) is the default value. Estimation score (RMSLE as default) is calculated every five seconds and the socre was not changed for tail_n=4 iterations, estimation will be stopped and best parameter set will be returned. However, with my tests, timeout_iteration appears to be a bottleneck. Many phases runs 5 seconds. (i.e. when timeout_iteration is shorter, runtime may be shorter.)

Note regarding constant liar:
constant_liar argument cannot be applied with Optuna version 2.7.0 or older.
https://gist.github.com/lisphilar/6440b5d69c4984bb0b34ede8c8ebcca3
TypeError means we use Optuna version 2.7.0 or older. When ``covsirphygetTypeErrorwithconstant_liarargument, it should remove the arument and retry creatingTPESampler`.

At version CovsirPhy 2.3.0 with Italy data (as of 18Jun2021), example/scenario_analysis.py and 8 CPUs at my local environment, parameter estimation completed with RMSLE=0.0795 in 2 min 22 sec.
(Please ignore accuracy of the last phase of Forecast scenario because this is a forecasted future phase.)

.

I compared the performances, changing constant_liar and timeout_iteration with Italy data as of 18Jun2021, my local environment and CovsirPhy version 2.20.3-theta. I used only 1 CPU with n_jobs=1 to get robust values of runtime as total value of all phases. Parameter estimation of each phase was done seaquencially. Code are as follows.
import covsirphy as cs
loader = cs.DataLoader()
jhu_data = loader.jhu()
snl = cs.Scenario(country="Italy")
snl.register(jhu_data)
snl.trend()
snl.estimate(cs.SIRF, n_jobs=1)
print(f"RMSLE: {snl.score(metric='RMSLE')}")

Results are here.

RMSLE (runtime)
constant_liar=False
constant_liar=True

timeout_iteration=5
0.06810 (13 min 22 sec)
0.06868 (17 min 42 sec)

timeout_iteration=4
0.06812 (14 min 03 sec)
0.06869 (14 min 07 sec)

timeout_iteration=3
0.06808 (10 min 10 sec)
0.06871 (10 min 31 sec)

timeout_iteration=2
0.06811 (07 min 55 sec)
0.06865 (07 min 11 sec)

timeout_iteration=1
0.06806 (03 min 21 sec)
0.06901 (03 min 53 sec)

I expected constant_liar=True and timeout_iteration=1 would show the best performance, but these results indicated constant_liar=False and timeout_iteration=1. I will create a pull request for constant_liar=False and timeout_iteration=1. These default values may be changed later if we get different results with the other countries' data.

With #833, timeout_iteration=1 will be default value for Scenario.esitmate(). constant_liar=False as-is explicitly.
Later, I will add constant_liar=False as an argument of Scenario.estimate(), if necessary.

WIth #835, user can select whether use constant liar or not with Scenario.esitmate(<model>, constant_liar=False) (default).

I compared RMSLE scores and runtime of constant_liar=False (default at this time) and constant_liar=True with some countries' datasets. I used example/scenario_analysis.py with 8 CPUs.
Results are here.

iso3
Country
constant_liar=False
constant_liar=True
Better RMSLE
Better runtime
Winner

ita
Italy
0.07642 (27 sec)
0.07686 (29 sec)
FALSE
FALSE
FALSE

jpn
Japan
0.06103 (39 sec)
0.06200 (44 sec)
FALSE
FALSE
FALSE

grc
Greece
0.05472 (37 sec)
0.05107 (44 sec)
TRUE
FALSE
NA

nld
Netherlands
0.03719 (37 sec)
0.03706 (28 sec)
TRUE
TRUE
TRUE

usa
USA
0.23073 (33 sec)
0.24186 (22 sec)
FALSE
TRUE
NA

ind
India
0.21665 (36 sec)
0.21871 (50 sec)
FALSE
FALSE
FALSE

bra
Brazil
0.06754 (53 sec)
0.06634 (63 sec)
TRUE
FALSE
NA

rus
Russia
0.61374 (38 sec)
0.61293 (28 sec)
TRUE
TRUE
TRUE

Because there was no significant difference, we continue to use constant_liar=False as default. For Netherlands and Russia, it will be better to use Scenario.estimate(cs.SIRF, constant_liar=True).

Runtime of parameter estimation will be quite shorter with timeout_iteration=1 (default). Version 2.21.0 release was planed in Jul2021, but this should be moved up to Jun2021. Tomorrow or within some days.


text:
歌曲排序

加入歌单的歌曲都是后加的在最上面，建议加入手动排序，以及根据歌曲名，歌手等自动排序。

+10086 排序功能太重要啦~~~ :)


text:
修复全局隐藏TopBar只在Tab布局下生效的问题

sorry，之前提交的PR[#228 ]只在Tab布局发现会自动隐藏，刚刚发现stack布局还是有topbar的，在这里修复了。
另外我们这个库是否支持tablet设备上横屏状态下TabBar改变位置？就是类似于很多iPad应用，将TabBar放到了左侧，我自己现在通过findViewById硬改实现了，想问一下有没有优雅点的方案呢？

刚刚测试了下，全局设置 topBarHidden: true, iOS 也是无法隐藏的

刚刚测试了下，全局设置 topBarHidden: true, iOS 也是无法隐藏的

我不太会iOS :joy:

刚刚测试了下，全局设置 topBarHidden: true, iOS 也是无法隐藏的

我不太会iOS 😂

我来处理下

计划通过以下方式支持：
// 开始注册组件，即基本页面单元
ReactRegistry.startRegisterComponent(withNavigationItem({ topBarHidden: true }))

计划通过以下方式支持：
// 开始注册组件，即基本页面单元
ReactRegistry.startRegisterComponent(withNavigationItem({ topBarHidden: true }))

嗯嗯，这个也是一种解决思路👍🏻

已实现 hybrid-navigation@2.9.0

authors: NiuGuohui listenzz

repo: listenzz/hybrid-navigation


text:
Can't run lit.dev on windows

When trying to run build the script fails when running the fonts:manrope script

rm (does not exist on windows)
cp (does not exist on windows)
mkdir -p (invalid syntax on windows)

I fixed those by changing the command by node scripts/fonts.js
After that some error with samples (D:\Workspace\lit\lit.dev\packages\lit-dev-content\samples\js_check-code-helpers.ts) is in a wrong path or the scipt is searching the wrong one

Thank you for filing this issue! Could _check-code-helpers.js not have been built into its expected location?
I only have occasional access to a Windows machine, but would happily review PRs that move us towards building on Windows.

Hi @AndrewJakubowicz, thanks!
I'm back to windows all the time for a long time now, spilled monster on the MBP 😢
The _check-code-helpers.js file is in the samples dir while the script expects it to be in samples/js
But in generate-js-samples.ts I can see that the js folder should not be included into the glob to pass to TS so maybe that is the problem.
https://github.com/lit/lit.dev/pull/1255

Hmm, now I'm getting a rollup error

Nobody else is getting that?

No clue

Thank you for raising this! We definitely should try and make this repo buildable in Windows.
In the meantime, I have found WSL2 to be quite good as a dev environment on Windows.

@augustjk
True WSL is great, but also a hassle plus somehow breaks from time to time imo WSL i awesome when your cross compiling etc,but for a node project it's quite simple to get it working the issues are really small like using the correct separator for paths.
Only issue is with eleventy now all the other stuff I already fixed (if Mac and Linux isn't broken now).

WSL doesn't work also, just installed new distro & think it tries to use npm installed on the windows side.


text:
ipc

(open in new tab instead of new window)

I was looking for this funcion, but must ask on discord.
Not obvious from README.md...

The README is generated from manifest.json so that's the one that needs to be updated.
I think something like Adds inter-process communication support, single-instance mode and tab drag and drop between instances. would be more explanatory.

repo: lite-xl/lite-xl-plugins


text:
iCloud backup Wallet seed

As Loaf/Bread Wallet uses something on the device as a seed for the wallet creation, do you know if replacing the processor in the phone will maintain whatever is used for this seed (Device ID/IMEI/serial number)?
I've had a phone die on me, and don't have the recovery phrase for the wallet. The phone is currently stuck in recovery mode and is returning an error that is consistent with a processor failure. I can get the processor replaced which would allow the phone to boot and for me to recover from iCloud but if it's not going to rebuild the same wallet, then I won't go ahead with it.
Any help is appreciated.

Do you have the 12 word seed (passphrase) that was generated when you first
used LoafWallet. With that 12 word seed, you can restore your wallet.
If you are able to get someone to replace your iPhone's processor and
unlock your phone without restoring, then there would be a somewhat high
chance that you are able to recover your wallet. At any point, if you end
up restoring your device, you will loose all of your coins, as LoafWallet
does not back up your seed/private keys to iCloud (for obvious reasons).
If you do end up recovering your wallet, please make sure that you go into
settings and then copy down your 12 word seed, just in case anything like
this happens in the future.
On 28 April 2017 at 00:49, Robbie Andrews notifications@github.com wrote:

As Loaf/Bread Wallet uses something on the device as a seed for the wallet
creation, do you know if replacing the processor in the phone will maintain
whatever is used for this seed (Device ID/IMEI/serial number)?
I've had a phone die on me, and don't have the recovery phrase for the
wallet. The phone is currently stuck in recovery mode and is returning an
error that is consistent with a processor failure. I can get the processor
replaced which would allow the phone to boot and for me to recover from
iCloud but if it's not going to rebuild the same wallet, then I won't go
ahead with it.
Any help is appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/litecoin-association/LoafWallet/issues/23, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfNukf1gkynnP3dYnbh2jZ4Rh7kSzjzks5r0SmMgaJpZM4NK5fD
.

Hi losh11,
Thanks for the quick reply.
I'd assumed that the iCloud backups would work in a similar way to Bread wallets method (as stated here ).

repo: litecoin-association/LoafWallet


text:
🚀[ Release v.2.8.4] Merge into Main

Overview
This is the last major release prior to work on Newborn, the refactored Litewallet Android. While there are many requests to improve the current codebase, it is actually 7 years of patching and rework and the cost / time of maintenance is no longer worth it.
We looked at the most important features needed and addressed them in this release.
They are:

Bech32 support for sending to 1ltc addresses
Allow user to see their 12 words / seed phrase
User preferences for sync vs anonymity (false positives rate)

Clips
Note some views

Show seed phrase

Add user preference False Positives

Wow, looks nice! @kcw-grunt Why is inside onClick empty for below code?
if (BuildConfig.VERSION_NAME == "v2.8.4") {
            Snackbar.make(parentLayout,
                            R.string.release_notes,
                            Snackbar.LENGTH_INDEFINITE).setAction(R.string.Webview_dismiss, new View.OnClickListener() {
                        @Override
                        public void onClick(View view) {

                        }
                    })
                    .setActionTextColor(getResources().getColor(android.R.color.holo_red_light ))
                    .show();
 }

The comment said to show, what 'false' does on items.add on code line 130-134 file SettingsActivity.java?
Why do we need to clear DB table to enable Bech32 features?

Thanks @josikie ...you are too kind.

Why do we need to clear DB table to enable Bech32 features?:

The legacy db used a different schema for ltc addresses. So, adding new addresses (ltc1) would fail in that old db.  One of the steps @vsima added was to have the device wipe the existing the db and add transactions to the new schema so now sending of L, M and ltc1 addresses is readable by the new schema.

The comment said to show, what 'false' does on items.add on code line 130-134 file SettingsActivity.java?

This is just a implementation detail in Android/Java Settings tables. So, it distinguishes a table item (section: false) to  a table section (section: true). Truth is I just used the existing design and added the item for Show my seed

Thank you for the explanation! @kcw-grunt

authors: josikie kcw-grunt

repo: litecoin-foundation/litewallet-android


text:
Replace deploy:service/deploy:process command with deploy

Dependency: https://github.com/liteflow-labs/liteflow-js/pull/38
Add liteflow deploy command that deploys all processes in a directory based on the liteflow framework structure.
All process-related services will automatically be deployed and started

Closing in favor of #42 that already includes these changes

repo: liteflow-labs/liteflow-js


text:
Signal AWS when applications are deployed

We currently can't do rolling upgrades of the galaxy image because the apps often take longer to deploy than the instances.
Galaxy needs to lookup all applications that should be running on a host, and notify the ASG when deployment is complete.
The ASG can have an UpdatePolicy, or the stack can contain a CreationPolicy to define when an instance is ready. Galaxy can use the API or the cfn-signal script for notification.

Since we've removed the cloudformation dependency from galaxy, this should be implemented in such a way that it's not coupled to AWS.
A callback command when the host is up should suffice.

repo: litl/galaxy


text:
添加 enableCmdQR 参数以解决登录异常

当pillow没有安装时，本来应该使用备用的函数提示用户手动扫码，但由于缺少enableCmdQR参数，触发了client.py中的except，并出现莫名其妙的报错 “Failed to get QR Code, please restart the program”

@xmcp 是我疏忽了，多谢！

authors: littlecodersh xmcp

repo: littlecodersh/ItChat


text:
🛑 USTC Mirrors (IPv4) is down

In 41f09e6, USTC Mirrors (IPv4) (https://ipv4.mirrors.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC Mirrors (IPv4) is back up in 5fa02b3.

repo: littlekud/sites-status


text:
Compile error on Termux (Android)

OS: Android (Termux)
vim-clap version: Latest from main.

Describe the bug
I get a compilation error when trying to upgrade:
error[E0282]: type annotations needed for `Box<_>`
  --> /data/data/com.termux/files/home/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.34/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
help: consider giving `items` an explicit type, where the placeholders `_` are specified
   |
83 |     let items: Box<_> = format_items
   |              ++++++++

   Compiling utils v0.1.54 (/data/data/com.termux/files/home/.vim/bundle/vim-clap/crates/utils)
For more information about this error, try `rustc --explain E0282`.
error: could not compile `time` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...

To Reproduce
Steps to reproduce the behavior:
Just ran Plugupdate, also tried cargo build --release --target aarch64-linux-android

running cargo update -p time seems to solve the issue.

repo: liuchengxu/vim-clap


text:
pip install -r requirements.txt报错

请问是故意的还是不小心的←_←为什么会有googleads

Collecting googleads==3.8.0
  Using cached https://mirrors.aliyun.com/pypi/packages/fa/f8/f84ad483afaa29bfc807ab6e8a06b6712ee494a2aad7db545865655bdf99/googleads-3.8.0.tar.gz (23 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      error in googleads setup command: use_2to3 is invalid.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

删除googleads之后
Collecting ruamel-yaml-conda
  Using cached https://mirrors.aliyun.com/pypi/packages/94/ef/31bfa8456e01ff1  Preparing metadata (setup.py) ... error                                      error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [19 lines of output]
      Traceback (most recent call last):
        File "/tmp/pip-install-26tjscuc/ruamel-yaml-conda_ca1bc85899634c92a2eb8c802d6396b0/ruamel_yaml/__init__.py", line 21, in <module>
          from .main import *                               # NOQA                   File "/tmp/pip-install-26tjscuc/ruamel-yaml-conda_ca1bc85899634c92a2eb8c802d6396b0/ruamel_yaml/main.py", line 12, in <module>
          import ruamel.yaml                                                       ModuleNotFoundError: No module named 'ruamel'

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-26tjscuc/ruamel-yaml-conda_ca1bc85899634c92a2eb8c802d6396b0/setup.py", line 14, in <module>
          import ruamel_yaml  # NOQA                                                 File "/tmp/pip-install-26tjscuc/ruamel-yaml-conda_ca1bc85899634c92a2eb8c802d6396b0/ruamel_yaml/__init__.py", line 23, in <module>
          from ruamel_yaml.main import *                               # NOQA        File "/tmp/pip-install-26tjscuc/ruamel-yaml-conda_ca1bc85899634c92a2eb8c802d6396b0/ruamel_yaml/main.py", line 12, in <module>                               import ruamel.yaml                                                       ModuleNotFoundError: No module named 'ruamel'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

手动运行了pip install ruamel.yaml和conda install ruamel.yaml（两个指令都是Google搜的）之后
我搞不定了，救命
Collecting ruamel-yaml-conda                                                   Using cached https://mirrors.aliyun.com/pypi/packages/94/ef/31bfa8456e01ff13d8d98bdbc80ab2e592c830e52ccaff62c35d5f890357/ruamel_yaml_conda-0.15.80.tar.gz (202 kB)
  Preparing metadata (setup.py) ... error                                      error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-nsnxrkh6/ruamel-yaml-conda_cfce9d13e9ae4a85b8c11d278dffd58b/setup.py", line 35, in <module>
          ext_modules=cythonize(extensions),                                         File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 970, in cythonize
          module_list, module_metadata = create_extension_list(                      File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 816, in create_extension_list
          for file in nonempty(sorted(extended_iglob(filepattern)), "'%s' doesn't match any files" % filepattern):
        File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 114, in nonempty
          raise ValueError(error_msg)                                              ValueError: 'ruamel_yaml/ext/_ruamel_yaml.pyx' doesn't match any files
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

总之希望能有个手动配置环境的说明，或者至少把需要的python版本一类的写清楚吧，不是所有用户都是程序员，也不是所有程序员都懂ai（比如我。。。）

ruamel yaml在conda里装可以试试 conda install -c conda-forge ruamel_yaml

手动运行了pip install ruamel.yaml和conda install ruamel.yaml（两个指令都是Google搜的）之后
我搞不定了，救命
Collecting ruamel-yaml-conda                                                   Using cached https://mirrors.aliyun.com/pypi/packages/94/ef/31bfa8456e01ff13d8d98bdbc80ab2e592c830e52ccaff62c35d5f890357/ruamel_yaml_conda-0.15.80.tar.gz (202 kB)
  Preparing metadata (setup.py) ... error                                      error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-nsnxrkh6/ruamel-yaml-conda_cfce9d13e9ae4a85b8c11d278dffd58b/setup.py", line 35, in <module>
          ext_modules=cythonize(extensions),                                         File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 970, in cythonize
          module_list, module_metadata = create_extension_list(                      File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 816, in create_extension_list
          for file in nonempty(sorted(extended_iglob(filepattern)), "'%s' doesn't match any files" % filepattern):
        File "/usr/local/lib/python3.8/dist-packages/Cython/Build/Dependencies.py", line 114, in nonempty
          raise ValueError(error_msg)                                              ValueError: 'ruamel_yaml/ext/_ruamel_yaml.pyx' doesn't match any files
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

ruamel yaml在conda里装可以试试 conda install -c conda-forge ruamel_yaml

我把报错的依赖都先跳过去不装，最后给我报了个找不到torch2.0.0，我彻底不知道我环境什么东西版本有问题了，我租的云服务器（本地没显卡是这样的）
我先用那个colab一键包对付下吧，colab404还随时可能被掐毕竟还是不方便

我把报错的依赖都先跳过去不装，最后给我报了个找不到torch2.0.0，我彻底不知道我环境什么东西版本有问题了，我租的云服务器（本地没显卡是这样的） 我先用那个colab一键包对付下吧，colab404还随时可能被掐毕竟还是不方便

Windows可以参考diff-svc的部署教程，因为我就是参考这个部署的，装不上的包能删就删了。
https://diff-svc.gitbook.io/the-beginners-guide-to-diff-svc/setting-up/setting-up-the-environment

我把报错的依赖都先跳过去不装，最后给我报了个找不到torch2.0.0，我彻底不知道我环境什么东西版本有问题了，我租的云服务器（本地没显卡是这样的） 我先用那个colab一键包对付下吧，colab404还随时可能被掐毕竟还是不方便

Windows可以参考diff-svc的部署教程，因为我就是参考这个部署的，装不上的包能删就删了。 https://diff-svc.gitbook.io/the-beginners-guide-to-diff-svc/setting-up/setting-up-the-environment

Linux。。。

我的锅，req是在3.8环境下导出的，因此存在一些奇怪的依赖错误
晚点我根据windows版一键包试着在3.9下重新配一遍吧

我把报错的依赖都先跳过去不装，最后给我报了个找不到torch2.0.0，我彻底不知道我环境什么东西版本有问题了，我租的云服务器（本地没显卡是这样的） 我先用那个colab一键包对付下吧，colab404还随时可能被掐毕竟还是不方便

我试了用 pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu118 来装 torch 2.0，后面能启动，但是不停报错 FileNotFoundError: [Errno 2] No such file or directory: 'weights/[]'，其它的

均已修复。

Hello @NijiharaTsubasa  @Gillwindy  @chenxvb @ricecakey06
I have spent 3 entire weeks trying to find a way to clone correclty voices and I still did not get good results, I am so tired of it. I am contacting you because I saw you had old comments under old issues, you haev probably found better ways since then? Could you save me from my misery and direct me towards a method, a repo, a tutorial or anything that helps get to the point where I can actually clone a voice thats looks similar to the cloned voice please?  Help my soul lol. Really.

authors: AIhasArrived Gillwindy NijiharaTsubasa chenxvb gak123 liujing04


text:
An easy interface to add custom accelerators / backends?

There should be some easy framework, so that i can easily add my ops for custom accelerator / framework.
I wanted to see if i can add easily port it to a proprietary chip aiming to outcompete M1 GPU.
I really like TFs framework for adding custom backends but its too big.

If you can sigh NDAs and stuff, can share more details.

Thanks for the offering! Sorry I didn't sign NDAs without knowing more details. (i.e. if NDA is about custom accelerators alone, we can discuss more in private channels).

Also, you can check out tinygrad: https://github.com/geohot/tinygrad which supposedly should be easy to add custom backends.

authors: brappier liuliu


text:
🛑 clans.korabli.su is down

In 537d4ac, clans.korabli.su (https://clans.korabli.su) was down:

HTTP code: 0
Response time: 0 ms

Resolved: clans.korabli.su is back up in 59c36b7.


text:
Working version of tvp to stored proc

Updated dependencies, merged with dizzy:masters and confirmed working.
confirmed working to sqlserver 2019 windows env

Updated version of #49

repo: livehelpnow/tds


text:
How to type rpm packets

Due to the requirements of the business scenario, we need to package this component as rpm

sorry, we do not currently offer official RPM distributions. You can use GoReleaser to build your own

authors: davidzhao zuyou-alt

repo: livekit/livekit


text:
Explorer round count sometimes shows up negative

Describe the bug (required)
The "rounds remaining" indicator displays incorrect data while the data is still loading from Infura. I believe I introduced this with https://github.com/livepeer/livepeerjs/pull/333, as that switched up the render logic on some of the GraphQL data.

Expected behavior (required)

This seems to show up after a few seconds.
To Reproduce (required)
Steps to reproduce the behavior:

Boot up the explorer.
Immediately click on the "round" thing in the upper left.
That'll show up.

Closing since the classic explorer was sunsetted.

Closing since the classic explorer was sunsetted.

authors: adamsoffer iameli

repo: livepeer/livepeerjs


text:
Modifier -> SwiftUI -> Documents: renameAction(_:)

Doc:
https://developer.apple.com/documentation/swiftui/view/renameaction(_:)-6lghl

[x] Swift implementation
[x] Elixir implementation

https://developer.apple.com/documentation/swiftui/view/renameaction(_:)-324yw

[x] Swift implementation
[x] Elixir implementation

Implemented in #326

authors: AZholtkevych carson-katri

repo: liveview-native/liveview-client-swiftui


text:
RegisterCommandIf Not working

` public function boot()
{
   Spotlight::registerCommandIf(Auth::check() && Auth::user()->role == 'A',Logout::class);
}`

@sandy15d please use the shouldBeShown method on the command when working with dependencies that need to be resolved:
    public function shouldBeShown(Request $request): bool
    {
        return $request->user()->role == 'A;
    }

More info: https://github.com/livewire-ui/spotlight#register-commands

repo: livewire-ui/spotlight


text:
按照文档执行报错

npm install  nestscript
npx nsc compile main.js main 到这步直接报错

拉去master分支，将/nsc/bin/run文件中的#!/usr/bin/env ts-node修改为#!/usr/bin/env node，然后在nestscript-master目录下执行npx nsc compile main.js main npx nsc run main，正常输出了，注意需要安装Oclif环境，参考http://semlinker.com/oclif-node-cli/，楼主的命令使用了oclif框架，本人逆向工作者，遇到了个网站使用了这个项目进行了JS加密，一摸一样，使用其他方式破解了，还是想学习下虚拟机解密二进制这块。

想了解一下是哪个网站

这个网站目前还原到以前的版本了，没有用虚拟机加载JS了，网站不方便透漏，实在不好意思。

repo: livoras/nestscript


text:
update ICASSP'24 info

Source of information on the number of accepted papers: https://cmsworkshops.com/ICASSP2024/papers/accepted_papers.php
Source of information on paper acceptance rate and number of valid submissions: official notification email.
The numbers from different channels are slightly different.

Thanks.


text:
Use IP.SB's HTTPS API

Use IP.SB's HTTPS API

该api是属于个人搭建，考虑稳定性、信息收集和兼容性（兼容其他有更多输出内容的api），不使用该api作为默认预设，可加入readme中推荐。

authors: HamJin lixuy

repo: lixuy/CloudXNS-DDNS-with-BashShell


text:
NODE_ENV=production egg-bin dev Instead of nuxt build

use NODE_ENV=production egg-bin dev to run server.
it has two steps.

nuxt build
egg start

Done.

repo: liyanlong/nuxt-egg


text:
🛑 Personal Home is down

In 3a25125, Personal Home (https://liyaodong.com) was down:

HTTP code: 403
Response time: 37 ms

Resolved: Personal Home is back up in 256e0ef.

repo: liyaodong/uptime


text:
没有第二块屏幕的时候，main函数也会执行两次

普通单屏平板或者虚拟机调试的时候，发现会执行两次main函数。
其中一次 window.defaultRouteName 是 /
一次 window.defaultRouteName 是 subMain
而且执行顺序不固定
这个是正常的么？

你好，问题已修复，之前为了适配应用使用过程中手机投屏电视，默认加载app就初始化了副屏engine。修复后只有检测到第二块屏幕后才会初始化副屏engine。

谢谢

authors: cwangfr liyufengrex


text:
dw [delete word] at last word of line should not shift a line below

I faced a problem when I use command 'dw' [delete word] at last word of line. A below line will be shifted to current line.
[example document]
line1,col2,col3
line2,col2,col3
line3,col2,col3
[after dw at 'col3' on line1]
line1,col2,line2,col2,col3
line3,col2,col3
[expected result]
line1,col2,
line2,col2,col3
line3,col2,col3

Oh sorry. I think I should post this issue to vim-mode.

repo: lloeki/ex-mode


text:
Cannot get Peer-Tweet running

Everything's in the title.
I followed the instructions on installing. I ran
npm install
npm install --save-dev electron-rebuild
./node_modules/.bin/electron-rebuild

After launching with 2 separate instance of terminal with these commands
npm run hot-server
npm run start-hot

When I start the second command line, I get this output
> PeerTweet@0.1.1 start-hot /home/l4p1n/peer-tweet
> cross-env HOT=1 NODE_ENV=development electron ./

(electron) companyName is now a required option to crashReporter.start
Error opening app
The app provided is not a valid Electron app, please read the docs on how to write one:
https://github.com/atom/electron/tree/v0.36.12/docs

Error: Cannot find module 'electron-debug'

npm ERR! Linux 4.2.0-36-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "start-hot"
npm ERR! node v4.4.4
npm ERR! npm  v3.8.9
npm ERR! code ELIFECYCLE
npm ERR! PeerTweet@0.1.1 start-hot: `cross-env HOT=1 NODE_ENV=development electron ./`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the PeerTweet@0.1.1 start-hot script 'cross-env HOT=1 NODE_ENV=development electron ./'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the PeerTweet package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env HOT=1 NODE_ENV=development electron ./
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs PeerTweet
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls PeerTweet
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/l4p1n/peer-tweet/npm-debug.log

And here is the content of /home/l4p1n/peer-tweet/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'start-hot' ]
2 info using npm@3.8.9
3 info using node@v4.4.4
4 verbose run-script [ 'prestart-hot', 'start-hot', 'poststart-hot' ]
5 info lifecycle PeerTweet@0.1.1~prestart-hot: PeerTweet@0.1.1
6 silly lifecycle PeerTweet@0.1.1~prestart-hot: no script for prestart-hot, continuing
7 info lifecycle PeerTweet@0.1.1~start-hot: PeerTweet@0.1.1
8 verbose lifecycle PeerTweet@0.1.1~start-hot: unsafe-perm in lifecycle true
9 verbose lifecycle PeerTweet@0.1.1~start-hot: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/l4p1n/peer-tweet/node_modules/.bin:/usr/bin:/home/l4p1n/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
10 verbose lifecycle PeerTweet@0.1.1~start-hot: CWD: /home/l4p1n/peer-tweet
11 silly lifecycle PeerTweet@0.1.1~start-hot: Args: [ '-c', 'cross-env HOT=1 NODE_ENV=development electron ./' ]
12 silly lifecycle PeerTweet@0.1.1~start-hot: Returned: code: 1  signal: null
13 info lifecycle PeerTweet@0.1.1~start-hot: Failed to exec start-hot script
14 verbose stack Error: PeerTweet@0.1.1 start-hot: `cross-env HOT=1 NODE_ENV=development electron ./`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:245:16)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at EventEmitter.emit (events.js:172:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at ChildProcess.emit (events.js:172:7)
14 verbose stack     at maybeClose (internal/child_process.js:827:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid PeerTweet@0.1.1
16 verbose cwd /home/l4p1n/peer-tweet
17 error Linux 4.2.0-36-generic
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "start-hot"
19 error node v4.4.4
20 error npm  v3.8.9
21 error code ELIFECYCLE
22 error PeerTweet@0.1.1 start-hot: `cross-env HOT=1 NODE_ENV=development electron ./`
22 error Exit status 1
23 error Failed at the PeerTweet@0.1.1 start-hot script 'cross-env HOT=1 NODE_ENV=development electron ./'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the PeerTweet package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     cross-env HOT=1 NODE_ENV=development electron ./
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs PeerTweet
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls PeerTweet
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

I guess I have to run npm install --dev but I prefer to ask to make sure.

Did it work with --dev? I don't have a linux distro to test this on.

So. I cloned a fresh copy of the repo, ran
npm install --dev
npm install electron-debug

Then started the server with npm run hot-server and started the client npm run start-hot. Until there everything is fine.
I've got another problem with the client saying in the devtools
Error: Module version mismatch. Expected 47, got 46.

I've got no idea of what going on.

The problem is that you need to install the native modules: https://github.com/lmatteis/peer-tweet#installing-native-modules
I'm not sure how to do that in linux.

Everything work. It works better if I read properly the README.md :joy:

authors: lapin-b lmatteis

repo: lmatteis/peer-tweet


text:
Formatting the LNBits Frontpage Description

Issue:
When entering the LNBits Frontpage there is a description like you can see in the following Screenshot:

This lines have no formating rules. So the lines set just next to next. It would be lovely for reading and serve informaion in a well formatted architecture.
Solution:
My solution would be Rich Text Editors oder WYSIWYG-Editors (What You See Is What You Get). That would allow also the dumpest presumed user to edit the text.
Output:
A well arranged/readable start page with important information about the server

this can be set in the manage server section

in the manage server section i´am able to edit the text. But it´s not displayed like that on the LNBits frontpage.
see screenshots:

Try it with :
<h2Family Bank

Playground

For testing extensions and other stuff

**************************************

Do not store large amounts here

Try it with :
<h2Family Bank

Playground

For testing extensions and other stuff

**************************************

Do not store large amounts here

Ok, this is not nice :) Could it also allow paragraphs ?

**Family Bank
Playground
For testing extensions and other stuff
**************************************
Do not store large amounts here
If it would work this way it would be a solution for me and a bunch of people.
On the other hand everybody is well known with simple formatting rules in common programs like gmail, telegram and also here on Github. In my opinion the aim should be to reduce every not needed effort to present a well arranged/readable start page with important information about the server.

It's a simple HTML syntax! Github uses Markdown...

Maybe adding Markdown support in the future is an option
https://markdoc.dev/

I did it here: https://github.com/lnbits/events/pull/10
@arcbtc worth doing it for the frontpage description also?

i think it worth it, it going to be useful for other extensions aswell

Really ? People need to know markdown or html to put in a description ?

Thanks for your work. Its now working with ease.
pls close this issue.

authors: DoktorShift arbadacarbaYK bitkarrot dni talvasconcelos

repo: lnbits/lnbits


text:
possible to support https://github.com/bytedance/terarkdb

pls support this as storage backend
https://github.com/bytedance/terarkdb

No, it will not be supported.
First, it is a RocksDB based KV store, storing Raft logs in KV stores is always wasteful. We have a much better storage engine for the logs, it is available at -
https://github.com/lni/dragonboat/tree/master/internal/tan
This engine, called tan, doesn't force you to have keys, why would you need to touch or construct trillions of keys when the leader just want to stream continuous entries to followers. It doesn't do compactions, as the log entries in raft are mostly append only. You also avoid some write amplification when you stop writing logs twice - you don't need to log your log. Its memtable is another redundant component when we already have an in memory log storage inside the raft implementation - inserting into that skiplist based memtable eats a huge chunk of your CPU cycles when you have millions of entries per second.
I'd be willing to be bet that tan is at least 20-30% faster than your suggested library when used for storing raft logs.
Secondly, that suggested library is C++ based.

Think @kolinfluence you should add it.

authors: dioptre lni ultperf

repo: lni/dragonboat


text:
Support external node registry functions

This PR allows clients to provide a NodeRegistryFactory function in the Expert config section which will be used to resolve nodes.
This is useful for clients who want to create and manage a node discovery service externally (so it can be used for other things) but still have the dragonboat library use it for dynamic node discovery.
Also adds a test for this new functionality.
Fixes: https://github.com/lni/dragonboat/issues/326

Codecov Report
Patch coverage is 50.00% of modified lines.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files Changed
Coverage

node.go
ø

nodehost.go
50.00%

:loudspeaker: Thoughts on this report? Let us know!.

Thanks for the PR.
Could you please have a look at the review comments above. There is also some data race errors when running the new test, log pasted below.
=== RUN   TestExternalNodeRegistryFunction
2023-09-19 08:31:38.652923 I | dragonboat: go version: go1.19.13, linux/amd64
2023-09-19 08:31:38.652958 I | dragonboat: dragonboat version: 4.0.0 (Dev)
2023-09-19 08:31:38.653001 W | config: mutual TLS disabled, communication is insecure
2023-09-19 08:31:38.653134 I | config: using default EngineConfig
2023-09-19 08:31:38.653166 I | config: using default LogDBConfig
2023-09-19 08:31:38.653248 I | dragonboat: DeploymentID set to 1
2023-09-19 08:31:38.660302 I | dragonboat: LogDB info received, shard 0, busy false
2023-09-19 08:31:38.665674 I | dragonboat: LogDB info received, shard 1, busy false
2023-09-19 08:31:38.669765 I | dragonboat: LogDB info received, shard 2, busy false
2023-09-19 08:31:38.674620 I | dragonboat: LogDB info received, shard 3, busy false
2023-09-19 08:31:38.677094 W | gossip: memberlist: Was able to connect to 123e4567-e89b-12d3-a456-426614174000 but other probes failed, network may be misconfigured
2023-09-19 08:31:38.679718 I | dragonboat: LogDB info received, shard 4, busy false
2023-09-19 08:31:38.684090 I | dragonboat: LogDB info received, shard 5, busy false
2023-09-19 08:31:38.689280 I | dragonboat: LogDB info received, shard 6, busy false
2023-09-19 08:31:38.693791 I | dragonboat: LogDB info received, shard 7, busy false
2023-09-19 08:31:38.699416 I | dragonboat: LogDB info received, shard 8, busy false
2023-09-19 08:31:38.704158 I | dragonboat: LogDB info received, shard 9, busy false
2023-09-19 08:31:38.709267 I | dragonboat: LogDB info received, shard 10, busy false
2023-09-19 08:31:38.713627 I | dragonboat: LogDB info received, shard 11, busy false
2023-09-19 08:31:38.718071 I | dragonboat: LogDB info received, shard 12, busy false
2023-09-19 08:31:38.722903 I | dragonboat: LogDB info received, shard 13, busy false
2023-09-19 08:31:38.728906 I | dragonboat: LogDB info received, shard 14, busy false
2023-09-19 08:31:38.733055 I | dragonboat: LogDB info received, shard 15, busy false
2023-09-19 08:31:38.733422 I | logdb: using plain logdb
2023-09-19 08:31:38.734863 I | dragonboat: logdb memory limit: 8192 MBytes
2023-09-19 08:31:38.735371 I | dragonboat: NodeHost ID: 123e4567-e89b-12d3-a456-426614174000
2023-09-19 08:31:38.735401 I | dragonboat: Expert.NodeRegistryFactory was set: using custom registry
2023-09-19 08:31:38.735440 I | dragonboat: filesystem error injection mode enabled: false
2023-09-19 08:31:38.736034 I | transport: transport type: go-tcp-transport
2023-09-19 08:31:38.737214 I | dragonboat: transport type: go-tcp-transport
2023-09-19 08:31:38.737253 I | dragonboat: logdb type: sharded-pebble
2023-09-19 08:31:38.737296 I | dragonboat: nodehost address: localhost:26001
2023-09-19 08:31:38.737322 I | dragonboat: go version: go1.19.13, linux/amd64
2023-09-19 08:31:38.737372 I | dragonboat: dragonboat version: 4.0.0 (Dev)
2023-09-19 08:31:38.737395 W | config: mutual TLS disabled, communication is insecure
2023-09-19 08:31:38.737490 I | config: using default EngineConfig
2023-09-19 08:31:38.737533 I | config: using default LogDBConfig
2023-09-19 08:31:38.737617 I | dragonboat: DeploymentID set to 1
2023-09-19 08:31:38.743690 I | dragonboat: LogDB info received, shard 0, busy false
2023-09-19 08:31:38.748062 I | dragonboat: LogDB info received, shard 1, busy false
2023-09-19 08:31:38.752225 I | dragonboat: LogDB info received, shard 2, busy false
2023-09-19 08:31:38.757578 I | dragonboat: LogDB info received, shard 3, busy false
2023-09-19 08:31:38.762896 I | dragonboat: LogDB info received, shard 4, busy false
2023-09-19 08:31:38.767749 I | dragonboat: LogDB info received, shard 5, busy false
2023-09-19 08:31:38.772257 I | dragonboat: LogDB info received, shard 6, busy false
2023-09-19 08:31:38.777120 I | dragonboat: LogDB info received, shard 7, busy false
2023-09-19 08:31:38.784119 I | dragonboat: LogDB info received, shard 8, busy false
2023-09-19 08:31:38.788517 I | dragonboat: LogDB info received, shard 9, busy false
2023-09-19 08:31:38.793300 I | dragonboat: LogDB info received, shard 10, busy false
2023-09-19 08:31:38.799423 I | dragonboat: LogDB info received, shard 11, busy false
2023-09-19 08:31:38.803587 I | dragonboat: LogDB info received, shard 12, busy false
2023-09-19 08:31:38.808046 I | dragonboat: LogDB info received, shard 13, busy false
2023-09-19 08:31:38.812889 I | dragonboat: LogDB info received, shard 14, busy false
2023-09-19 08:31:38.818779 I | dragonboat: LogDB info received, shard 15, busy false
2023-09-19 08:31:38.819076 I | logdb: using plain logdb
2023-09-19 08:31:38.820205 I | dragonboat: logdb memory limit: 8192 MBytes
2023-09-19 08:31:38.820907 I | dragonboat: NodeHost ID: 123e4567-e89b-12d3-a456-426614174001
2023-09-19 08:31:38.820938 I | dragonboat: Expert.NodeRegistryFactory was set: using custom registry
2023-09-19 08:31:38.820980 I | dragonboat: filesystem error injection mode enabled: false
2023-09-19 08:31:38.821880 I | transport: transport type: go-tcp-transport
2023-09-19 08:31:38.822814 I | dragonboat: transport type: go-tcp-transport
2023-09-19 08:31:38.822883 I | dragonboat: logdb type: sharded-pebble
2023-09-19 08:31:38.822919 I | dragonboat: nodehost address: localhost:26002
2023-09-19 08:31:38.826387 I | dragonboat: [00001:00001] replaying raft logs
2023-09-19 08:31:38.826569 I | raft: [00001:00001] created, initial: true, new: true
2023-09-19 08:31:38.826615 W | config: ElectionRTT is not a magnitude larger than HeartbeatRTT
2023-09-19 08:31:38.826656 I | raft: [00001:00001] raft log rate limit enabled: false, 0
2023-09-19 08:31:38.826715 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00001] t0 became follower
2023-09-19 08:31:38.826801 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00001] t1 became follower
2023-09-19 08:31:38.826860 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00001] t1 added bootstrap ConfigChangeAddNode, 1, 123e4567-e89b-12d3-a456-426614174000
2023-09-19 08:31:38.826919 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00001] t1 added bootstrap ConfigChangeAddNode, 2, 123e4567-e89b-12d3-a456-426614174001
2023-09-19 08:31:38.827428 I | rsm: [00001:00001] no snapshot available during launch
2023-09-19 08:31:38.827563 I | dragonboat: [00001:00001] initialized using <00001:00001:0>
2023-09-19 08:31:38.827605 I | dragonboat: [00001:00001] initial index set to 0
2023-09-19 08:31:38.830797 I | dragonboat: [00001:00002] replaying raft logs
2023-09-19 08:31:38.831038 I | raft: [00001:00002] created, initial: true, new: true
2023-09-19 08:31:38.831088 W | config: ElectionRTT is not a magnitude larger than HeartbeatRTT
2023-09-19 08:31:38.831138 I | raft: [00001:00002] raft log rate limit enabled: false, 0
2023-09-19 08:31:38.831323 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00002] t0 became follower
2023-09-19 08:31:38.831408 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00002] t1 became follower
2023-09-19 08:31:38.831480 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00002] t1 added bootstrap ConfigChangeAddNode, 1, 123e4567-e89b-12d3-a456-426614174000
2023-09-19 08:31:38.831546 I | raft: [f:1,l:0,t:0,c:0,a:0] [00001:00002] t1 added bootstrap ConfigChangeAddNode, 2, 123e4567-e89b-12d3-a456-426614174001
2023-09-19 08:31:38.833185 I | rsm: [00001:00002] no snapshot available during launch
2023-09-19 08:31:38.833398 I | dragonboat: [00001:00002] initialized using <00001:00002:0>
2023-09-19 08:31:38.833461 I | dragonboat: [00001:00002] initial index set to 0
2023-09-19 08:31:38.834893 I | rsm: [00001:00002] applied ADD ccid 0 (1), n00001 (123e4567-e89b-12d3-a456-426614174000)
2023-09-19 08:31:38.835034 I | rsm: [00001:00002] applied ADD ccid 0 (2), n00002 (123e4567-e89b-12d3-a456-426614174001)
2023-09-19 08:31:38.837618 W | dragonboat: [00001:00001] had 2 LocalTick msgs in one batch
2023-09-19 08:31:38.838604 I | rsm: [00001:00001] applied ADD ccid 0 (1), n00001 (123e4567-e89b-12d3-a456-426614174000)
2023-09-19 08:31:38.838684 I | rsm: [00001:00001] applied ADD ccid 0 (2), n00002 (123e4567-e89b-12d3-a456-426614174001)
2023-09-19 08:31:38.853533 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 became candidate
2023-09-19 08:31:38.853619 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 received RequestVoteResp from n00002
2023-09-19 08:31:38.853673 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 sent RequestVote to n00001
2023-09-19 08:31:38.857429 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00001] t1 received RequestVote with higher term (2) from n00002
2023-09-19 08:31:38.857485 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00001] t1 become followerKE after receiving higher term from n00002
2023-09-19 08:31:38.857671 I | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00001] t2 became follower
2023-09-19 08:31:38.857779 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00001] t2 cast vote from n00002 index 2 term 2, log term: 1
2023-09-19 08:31:38.860333 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 received RequestVoteResp from n00001
2023-09-19 08:31:38.860407 W | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 received 2 votes and 0 rejections, quorum is 2
2023-09-19 08:31:38.860478 I | raft: [f:1,l:2,t:1,c:2,a:2] [00001:00002] t2 became leader
2023-09-19 08:31:38.935478 E | transport: send batch failed, target localhost:26002 (write tcp 127.0.0.1:37262->127.0.0.1:26002: write: connection reset by peer), 2
2023-09-19 08:31:38.935607 W | transport: breaker 123e4567-e89b-12d3-a456-426614174000 to localhost:26002 failed, connect and process failed: write tcp 127.0.0.1:37262->127.0.0.1:26002: write: connection reset by peer
2023-09-19 08:31:38.935682 W | transport: localhost:26002 became unreachable, affected 1 nodes
==================
WARNING: DATA RACE
Write at 0x00c0000eb110 by goroutine 6651:
  runtime.mapassign_faststr()
      /opt/hostedtoolcache/go/1.19.13/x64/src/runtime/map_faststr.go:203 +0x0
  github.com/lni/dragonboat/v4.TestExternalNodeRegistryFunction()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1320 +0xef7
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.(*T).Run.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x47

Previous read at 0x00c0000eb110 by goroutine 6961:
  runtime.mapaccess1_faststr()
      /opt/hostedtoolcache/go/1.19.13/x64/src/runtime/map_faststr.go:13 +0x0
  github.com/lni/dragonboat/v4.(*testRegistry).Resolve()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1208 +0xe4
  github.com/lni/dragonboat/v4/internal/transport.(*Transport).send()
      /home/runner/work/dragonboat/dragonboat/internal/transport/transport.go:361 +0xba
  github.com/lni/dragonboat/v4/internal/transport.(*Transport).Send()
      /home/runner/work/dragonboat/dragonboat/internal/transport/transport.go:347 +0x68
  github.com/lni/dragonboat/v4.(*NodeHost).sendMessage()
      /home/runner/work/dragonboat/dragonboat/nodehost.go:1881 +0xf4
  github.com/lni/dragonboat/v4.(*NodeHost).sendMessage-fm()
      <autogenerated>:1 +0x84
  github.com/lni/dragonboat/v4.(*node).sendMessages()
      /home/runner/work/dragonboat/dragonboat/node.go:1011 +0x1b6
  github.com/lni/dragonboat/v4.(*node).processRaftUpdate()
      /home/runner/work/dragonboat/dragonboat/node.go:1108 +0xb3
  github.com/lni/dragonboat/v4.(*engine).processSteps()
      /home/runner/work/dragonboat/dragonboat/engine.go:1353 +0x804
  github.com/lni/dragonboat/v4.(*engine).stepWorkerMain()
      /home/runner/work/dragonboat/dragonboat/engine.go:1254 +0x5e6
  github.com/lni/dragonboat/v4.newExecEngine.func1()
      /home/runner/work/dragonboat/dragonboat/engine.go:1047 +0x98
  github.com/lni/goutils/syncutil.(*Stopper).runWorker.func1()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:79 +0x12e

Goroutine 6651 (running) created at:
  testing.(*T).Run()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x75d
  testing.runTests.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1846 +0x99
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.runTests()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1844 +0x7ec
  testing.(*M).Run()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1726 +0xa84
  main.main()
      _testmain.go:675 +0x2e9

Goroutine 6961 (running) created at:
  github.com/lni/goutils/syncutil.(*Stopper).runWorker()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:74 +0x19a
  github.com/lni/goutils/syncutil.(*Stopper).RunWorker()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:68 +0xef
  github.com/lni/dragonboat/v4.newExecEngine()
      /home/runner/work/dragonboat/dragonboat/engine.go:1037 +0xa19
  github.com/lni/dragonboat/v4.NewNodeHost()
      /home/runner/work/dragonboat/dragonboat/nodehost.go:366 +0x1486
  github.com/lni/dragonboat/v4.TestExternalNodeRegistryFunction()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1266 +0x8f7
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.(*T).Run.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x47
==================
==================
WARNING: DATA RACE
Write at 0x00c00048d178 by goroutine 6651:
  github.com/lni/dragonboat/v4.TestExternalNodeRegistryFunction()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1320 +0xf38
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.(*T).Run.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x47

Previous read at 0x00c00048d178 by goroutine 6961:
  github.com/lni/dragonboat/v4.(*testRegistry).Resolve()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1208 +0xee
  github.com/lni/dragonboat/v4/internal/transport.(*Transport).send()
      /home/runner/work/dragonboat/dragonboat/internal/transport/transport.go:361 +0xba
  github.com/lni/dragonboat/v4/internal/transport.(*Transport).Send()
      /home/runner/work/dragonboat/dragonboat/internal/transport/transport.go:347 +0x68
  github.com/lni/dragonboat/v4.(*NodeHost).sendMessage()
      /home/runner/work/dragonboat/dragonboat/nodehost.go:1881 +0xf4
  github.com/lni/dragonboat/v4.(*NodeHost).sendMessage-fm()
      <autogenerated>:1 +0x84
  github.com/lni/dragonboat/v4.(*node).sendMessages()
      /home/runner/work/dragonboat/dragonboat/node.go:1011 +0x1b6
  github.com/lni/dragonboat/v4.(*node).processRaftUpdate()
      /home/runner/work/dragonboat/dragonboat/node.go:1108 +0xb3
  github.com/lni/dragonboat/v4.(*engine).processSteps()
      /home/runner/work/dragonboat/dragonboat/engine.go:1353 +0x804
  github.com/lni/dragonboat/v4.(*engine).stepWorkerMain()
      /home/runner/work/dragonboat/dragonboat/engine.go:1254 +0x5e6
  github.com/lni/dragonboat/v4.newExecEngine.func1()
      /home/runner/work/dragonboat/dragonboat/engine.go:1047 +0x98
  github.com/lni/goutils/syncutil.(*Stopper).runWorker.func1()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:79 +0x12e

Goroutine 6651 (running) created at:
  testing.(*T).Run()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x75d
  testing.runTests.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1846 +0x99
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.runTests()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1844 +0x7ec
  testing.(*M).Run()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1726 +0xa84
  main.main()
      _testmain.go:675 +0x2e9

Goroutine 6961 (running) created at:
  github.com/lni/goutils/syncutil.(*Stopper).runWorker()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:74 +0x19a
  github.com/lni/goutils/syncutil.(*Stopper).RunWorker()
      /home/runner/go/pkg/mod/github.com/lni/goutils@v1.3.1-0.20220604063047-388d67b4dbc4/syncutil/stopper.go:68 +0xef
  github.com/lni/dragonboat/v4.newExecEngine()
      /home/runner/work/dragonboat/dragonboat/engine.go:1037 +0xa19
  github.com/lni/dragonboat/v4.NewNodeHost()
      /home/runner/work/dragonboat/dragonboat/nodehost.go:366 +0x1486
  github.com/lni/dragonboat/v4.TestExternalNodeRegistryFunction()
      /home/runner/work/dragonboat/dragonboat/nodehost_test.go:1266 +0x8f7
  testing.tRunner()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x216
  testing.(*T).Run.func1()
      /opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1493 +0x47
==================

Oh missed the data race one -- taking a look at that now.

OK, fixed the data race too.

Cool, thanks.

authors: codecov-commenter lni tylerwilliams


text:
Is --keep-until-expiring needed?

The renew command only generates new certificates if they are near expiry. See https://certbot.eff.org/docs/using.html#command-line-options

Thanks for all your fixes! :D

repo: lnicola/certbot-systemd-nginx


text:
handle multiple events

the site is currently showing info for the Feb event, which is cool but people probably still want to know what is going to be happening tonight at the January event.

Can we switch it back to Jan? I've checked my phone so many times on the way to the event to remind myself what the talks are going to be (and where it is!)

https://github.com/lnug/lnug.github.io/pull/104/files
On 27 January 2016 at 16:19, lnugbot notifications@github.com wrote:

Yerp,
Agreed. Will take a look ASAP
I'm on a train into London atm. Will take a look when I can find somewhere
dry.
Sent from my iPhone

On 27 Jan 2016, at 15:57, Clarkie notifications@github.com wrote:
Can we switch it back to Jan? I've checked my phone so many times on the
way to the event to remind myself what the talks are going to be (and where
it is!)
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/lnug/lnug.github.io/issues/103#issuecomment-175719869
.

--
Simon McManus
DotJS Ltd - Node Consultancy

authors: clarkie simonmcmanus


text:
[Error: no commits found]

I'm getting the following error on a mac system:
[Error: no commits found]
There were 3 commits in the repo when I first saw the issue, and I added two more commits to test, but itt still wouldn't work.

Hmm that's odd. Could you let me know what version of git you're using? Also, when you run the following command, what is outputted?
git log -E --format=%H%n%s%n%b%n===END===

I realized the issue was with that particular developer not pushing with --tags, causing local tags to not be pushed into remote.

repo: lob/generate-changelog


text:
SELF-302: IconButton Variant

JIRA

SELF-343

Description

Adds IconButton text variant
Add Skeleton component

Screenshots

Reviewer Checklist
This section is to be filled out by reviewers
Testing

[ ] This code was tested by somebody other than the developer. Do not merge until this has been done.

Hey Nate! I'd like to make one suggestion - can we call this something more generic since we plan to build on this? Maybe like stylized button or something like that? This saves us having to change it in the dashboard later

Hey Nate! I'd like to make one suggestion - can we call this something more generic since we plan to build on this? Maybe like stylized button or something like that? This saves us having to change it in the dashboard later

Hey!
Are you referring to the name IconButton?

authors: NateWaldschmidt shannamurry

repo: lob/ui-components


text:
Is isRunning method works fine?

I try to make a simple e2e test (Java + Spring Framework) which check our API by stopping Localstack instance, sending message to broker instance and finally asserting HTTP error response code. This test is part of bigger test suite with DirtiesContext annotation (with after each method mode).
Out Localstack bean is customized. In Spring Configuration we defined a bean with custom init and destroy methods. Init method will be posted below, destroy method just send purge requests into all queues. We don't want to stop Localstack instance - time optimization.
Init method:
        if (!localstack.isRunning()) {
            localstack.startup(LOCALSTACK_CONFIGURATION);
            Runtime.getRuntime().addShutdownHook(new Thread(localstack::stop));
        }

After localstack.stop(); - our init method will never work because isRunning method returns always true even when docker doesn't have running containers (docker ps return empty list).
If Localstack object (unfortunately a static object) has non-null instance of localStackContainer - isRunning method return true response (with empty list of available ports underneath). Seems like stop method do not unset localStackContainer field?
Container.isRunning method:
try {
            new PortCommand(containerId).execute();
            return true;
        } catch(Exception e) {
            return false;
        }

Could you allow to unset localStackContainer field or just unset this instance inner stop method? We just want to find out (using isRunning method) that docker image is running or not to avoid unnecessary Localstack restart between single test (using DirtiesContext annotation).

This will be unit test for this fix:
localstack.start();
localstack.stop();
assertFalse(localstack.isRunning());

Could you upload following changes:

In logic: cloud.localstack.Locastack:

    public void stop() {
        if (localStackContainer != null) {
            localStackContainer.stop();
            localStackContainer = null;
        }
        locked = false;
    }

Unit test in cloud.localstack.dockerLocalstackDockerTest:

    @Test
    public void restart() {
        Localstack.INSTANCE.startup(DOCKER_CONFIG);
        Localstack.INSTANCE.stop();
        assertFalse(Localstack.INSTANCE.isRunning());
    }

@whummer

Thanks for reporting @wojciechszymski , and apologies for the long delay. This is potentially related to #82 . We believe that this should be fixed in the meantime - a new version 0.2.20 has been pushed to Maven Central. Can you please give it a try with that version? Please keep us posted if the problem persists.. Thanks!

Hi! We just wanted to follow up on our last message to see whether your issue has been resolved. Were you able to get it working with the latest version of LocalStack? We would appreciate your feedback!

authors: lakkeger whummer wojciechszymski

repo: localstack/localstack-java-utils


text:
Back button, close button, buttons size, getValue

backButton - Back button component prop (optional).
closeButton - Close button component prop (optional).
backCloseSize - sets the size of back button & close button (default 20).
getValue - returns the current value.

Solves #6

Changes accepted, please re-review.

repo: localz/react-native-searchbar


text:
GEOMESA-2386 Adding WPS module to FileSystem gs-plugin

Signed-off-by: Emilio Lahr-Vivaz elahrvivaz@ccri.com

I haven't been able to re-create the original issue, but bundles the jars needed for WPS in with the FSDS gs-plugin (where previously you had to also install the e.g. accumulo gs-plugin, or manually copy the correct jars)

repo: locationtech/geomesa


text:
link opening without clicking it

Here I'm trying to append to the bullet point "door opening procedure" I want to press enter and ultimately write "fixed". So I click on the blank space after, we can discuss the capture behavior here but opening this link is def not my intention and I didn't tap the link.
https://github.com/user-attachments/assets/6a0e8b30-cbf7-48ef-b4a6-6e447496065e

@Parth are you still able to produce this? I'm unable to reproduce so far

authors: Parth tvanderstad

repo: lockbook/lockbook

license: Unlicense


text:
Added model saving

It looks like the code to save the models was missing, I've added these three lines to main.py:
    if args.save:
        model.save_pretrained(args.save)
        tokenizer.save_pretrained(args.save)

Thanks for the interest in our work! I have updated the repository to add support for this feature, which used a separate argument --save_model to allow custom demand of saving pruned models.

repo: locuslab/wanda


text:
SocketIOUser not support send BINARY data

Prerequisites

[X] I am using the latest version of Locust
[X] I am suggesting a new feature, not asking a question

Description

in this function, it prevent user to send data in OPCODE_BINARY, so I suggest to export websocket  'opcode'  param to user as bellow。
    # def send(self, body, name=None, context={}, opcode=websocket.ABNF.OPCODE_TEXT)
    def send(self, body, name=None, context={}):
        if not name:
            if body == "2":
                name = "2 heartbeat"
            else:
                # hoping this is a subscribe type message, try to detect name
                m = re.search(r'(\d*)\["([a-z]*)"', body)
                assert m is not None
                code = m.group(1)
                action = m.group(2)
                url_part = re.search(r'"url": *"([^"]*)"', body)
                assert url_part is not None
                url = re.sub(r"/[0-9_]*/", "/:id/", url_part.group(1))
                name = f"{code} {action} url: {url}"

        self.environment.events.request.fire(
            request_type="WSS",
            name=name,
            response_time=None,
            response_length=len(body),
            exception=None,
            context={**self.context(), **context},
        )
        logging.debug(f"WSS: {body}")
        # self.ws.send(body, opcode)
        self.ws.send(body)

👍 PR welcome!

👍 PR welcome! (technically this issue should be in locust-plugins but its ok :)

a PR is created in locust-plugins.pr-151

Merged!

authors: cyberw luis-allan

repo: locustio/locust


text:
Feature chart sync

This PR improves the charts of the index and the report page with the following changes:

Prevent to continue reporting stats to the history of stats when the runner is stopped
Usage of shared template to build stats_history data to reload to charts data in the index.html and report.html templates
Fix Report Charts tooltips user count values

Fixes #1677

Awesome!

Awesome!

@cyberw Sorry, I need to add a new way to pass the data from python to the js without need to generate the instructions. I will make another PR

@cyberw Sorry, I need to add a new way to pass the data from python to the js without need to generate the instructions. I will make another PR

authors: aek cyberw


text:
[BUG] Can't add new role

After adding the first role, when second role is added, role-already-exists is displayed in the chat box, and the role cannot be added.
Incidentally, when checking the lectern at this point, the first role name is blank.
After restarting the server, the roles “permissions” and “players” appear on this screen.
In this state, after allowing role-editor-edit-manage-roles in permissions and assigning a player, the same operation cannot add a role.

I cannot reproduce it. Could you explain more specifically the steps to do it? Thanks!

What's the name of the role you want to create?

for example, I tried to name three times: "test", "税務官", and "aaaa".

I tried to name three times: "test", "税務官", and "aaaa".
On all three times, the server had been started by deleting the plugin data and installing the plugin each time.

Still cannot reproduce it. Both "test" and "aaaa" work fine, and "税務官" just gives the only-alphanumeric error and the role is not created. I'll take a deeper look into it and see if I find the issue.

In my environment, both CJK and alphabetic characters are logged as shown in the image.
Nothing is displayed in the console.

Oh, I found a conflict with a certain chat related plugin. It appears that the plugin is preventing the chat data from being passed to this plugin.
I will ask the author of the plugin that caused the problem.

authors: DrJekyllH lofi-enjoyer

repo: lofi-enjoyer/NubladaTowns


text:
No way to disband parties?

I cannot seem to find a way to disband parties, as you cannot leave a party if you are the leader and there doesn't appear to be a party disband command

I am also having this issue.

repo: lofi-enjoyer/TownyElections


text:
Use stable rbac.authorization.k8s.io/v1 API

RBAC mode is stable since k8s v1.8.
We should also update the helm charts.

oh, new helm charts already use rbac.authorization.k8s.io/v1 💪


text:
Pypi install

@StephenHynes7 @eflanagan-r7 please review

+1

repo: logentries/lecli


text:
Reloading standalone page fails with 500 error

When reloading the standalone page (e.g. /chat/{address}/object/{objectId}/new) a 500 Internal Error is reported. On the console log there is a message 'no wallet`.

Since this PR the problem can be traced back to the check for having wallet defined in src/lib/objects/ui.svelte. The problem is when the app is restarted the state stores are reinitialized and while they are in their initial phases (e.g. loading = true) their content is not available.
It would be better to create a generic mechanism for waiting for all the stores to be loaded, otherwise all the pages has to implement a check for their dependent stores to be loaded and display a loading screen, which makes it fragile against introducing bugs on reload.